#
…

2026-07-26

00:39madmatt067 has quit [Quit: .]
00:42madmatt0677 has joined #asahi-alt
01:48ipatch_ has quit [Read error: No route to host]
01:48ipatch has joined #asahi-alt
02:19chadmed has quit [Quit: Konversation terminated!]
02:31chadmed has joined #asahi-alt
03:31chadmed has quit [Quit: Konversation terminated!]
03:35chadmed has joined #asahi-alt
04:08kode54 has quit [Quit: The Lounge - https://thelounge.chat]
04:12kode54 has joined #asahi-alt
06:35chadmed has quit [Quit: Konversation terminated!]
06:38chadmed has joined #asahi-alt
07:19MichaelLong has quit []
07:41MichaelLong has joined #asahi-alt
08:19chadmedjannau: our diff is ~3 mib and we have to regen the manifest anyway, what is the point of doing the inter tag thing? it just means the ebuild needs manual handling between tag bumps on top of everything else
08:19chadmedif it helps with your workflow then im fine to use it, i just dont think there is an obvious case for it
08:21jannauyes, our diff is 3M. that's the point
08:22chadmedif you consider that too large then sure i dont have a problem doing it
08:24jannauI consider that large, especially that since we can't compress it. I assume diffing two very close tags causes less load on github's side
08:26jannauI think with the current state it should be possible to avoid manual changes in the ebuild although I'm fine with (un)commenting a few lines
08:29chadmedi gues we could do something like if [[ -z $ASAHI_BASE ]]; then SRC_URI+="..."; fi
08:30chadmedor, yknow, the opposite of that condition :P
08:30chadmedor check if its the same as MY_TAG actually
08:35chaos_princess has quit [Quit: chaos_princess]
08:35chaos_princess has joined #asahi-alt
08:40chadmedtheres something up with kernel.org. the signature file has changed yet again
08:49chadmedoh i see whats happened
09:05JamesCalligeros[m]Is it supposed to come from your fork?
09:06j`eyhow does that get loaded?
09:06jannauit needs to come from my fork until https://github.com/AsahiLinux/avd-fw/pull/4 is merged
09:06JamesCalligeros[m]normal fw load mechanism
09:06j`ey is it in /lib/firmware etc, ok!
09:07JamesCalligeros[m]Yeah it gets installed to /lib/firmware/apple
09:07JamesCalligeros[m]But we need to put it somewhere else temporarily so as not to cause file collisions once we submit it to linux-firmware
09:08jannau/usr/lib/firmware/updates/apple (usr-merge and to avoid conflicts when it lands in linux-firmware)
10:22chadmed has quit [Quit: Konversation terminated!]
10:22chadmed has joined #asahi-alt
13:57chadmed has quit [Remote host closed the connection]
13:57fugi5 has quit [Quit: bye]
13:57fugi5 has joined #asahi-alt
13:59chadmed has joined #asahi-alt
14:54sofuswhen its added to linux-firmware i suppose the fw path in the driver should also change
14:55sofusjannau: thanks i merged the firmwaredir changes
14:57jannausofus: no need to change anything. the ebuild installs into to ".../firmware/updates/" to avoid conflicts with linux firmware which will use ".../firmware/". Both paths are used by linux' firmware loader. no need to change anything in the driver
15:00elisaadoseems like `/sys/class/power_supply/macsmc-battery/charge_control_end_threshold` disappeared on the latest tagged kernel (7.1.5-1), is this a known issue?
15:00jannauit's fixed in (7.1.5-2
15:01elisaadothanks for the quick answer
15:03sofusjannau: i meant in regards to using 'apple/*', but i guess its mostly a style thing
15:04jannauah, yes, that should list the actual firmware files
15:10jannausofus: I'm not sure what you refer to
15:10jannauwhat's missing from the driver though are MODULE_FIRMWARE(""); definitions
15:13sofussorry that was not very clear. I was only talking about using the "apple" prefix
15:14sofusi will add the MODULE_FIRMWARE, thanks
15:14jannauI think we want to keep it. maybe even use "apple/avd/" as prefix
16:43elisaadolol, interesting how this random website detects h265 as hardware accelerated but not vp9
17:00jannauelisaado: which browser? did this change with avd present? I suspect it is a misdetection of the website
17:27cy8aerI have the same as above on ff 153. about:support tells: HARDWARE_VIDEO_DECODING: FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED
17:27cy8aerI can see the modules for avd loaded.
17:29sofusfirefox does not support v4l2-request
17:29sofus(which is what avd uses)
17:32sofusnp, i plan on adding some support until then you could use mpv (with a patched ffmpeg)
17:36elisaadojannau: firefox on 7.5.1-2, never tested without avd
17:44sofuselisaado: firefox does not support avd yet, another time look at 'about:support' instead
17:44elisaadoah that makes sense
20:45seb_ has joined #asahi-alt
20:46seb_ has quit []
20:53chadmed has quit [Remote host closed the connection]
20:54chadmed has joined #asahi-alt
21:02enverbalalic has joined #asahi-alt
21:33enverbalalic has quit [Ping timeout: 480 seconds]
21:56enverbalalic has joined #asahi-alt
22:35craftyguyasahi.config has "CONFIG_CHARGER_MACSMC=m" but that option doesn't seem to exist anymore.. should it be "CONFIG_MACSMC_POWER=m" now?
23:15Ardu0us has quit [Quit: %Reality broken: (I)gnore, (R)etry, (A)bort%]
23:16Ardu0us has joined #asahi-alt
…