#asahi-dev · 2026-11-07 06:31
chadmedevery single time#asahi-dev · 2026-11-07 06:30
nicolas17>push, remember about signed-off-by requirement, add that, push, find another typo#asahi-dev · 2026-11-07 06:20
chadmedthe initial implementation of the firmware effectively just used the m3 as an interrupt forwarder, and the linux driver programs the actual codec hardware directly#asahi-dev · 2026-11-07 06:20
nicolas17it sounded like you meant to say "we made a working driver for the AVD hardware, to decode AVC video" and typoed the first, but I understand now#asahi-dev · 2026-11-07 06:20
nicolas17I see#asahi-dev · 2026-11-07 06:19
chadmedyeah avd is a bunch of hw codec implementations wearing a cortex-m3 shaped trenchcoat#asahi-dev · 2026-11-07 06:19
nicolas17are the other codecs different hardware?#asahi-dev · 2026-11-07 06:17
chadmedthe other codecs came later#asahi-dev · 2026-11-07 06:17
chadmedas in, h.264#asahi-dev · 2026-11-07 06:17
chadmedno, it is supposed to be AVC#asahi-dev · 2026-11-07 06:17
nicolas17I'm fixing other typos and will send a PR, just wanted to confirm this one#asahi-dev · 2026-11-07 06:17
nicolas17I assume "AVC hardware" should be "AVD hardware"?#asahi-dev · 2026-11-07 06:17
nicolas17"With a blob of custom AVD firmware that simply installs interrupt handlers and applies each variant's set of tunables, he was able to write a working V4L2 driver for the AVC hardware! The hardware can decode 10-bit AVC-encoded video"#asahi-dev · 2026-11-07 06:17
nicolas17an older post says:#asahi-dev · 2026-11-07 05:47
MichaelReeves[m]very well written as always, great job!#asahi-dev · 2026-11-07 05:17
chadmedhttps://asahilinux.org/2026/11/progress-report-7-3/#asahi-dev · 2026-11-07 00:05
svenwe should add if that's actually EL0 or fake-GL0-running-in-EL0#asahi-dev · 2026-11-07 00:04
sven== Exception taken from EL0t == <-- huh, it's from EL0?!#asahi-dev · 2026-11-07 00:04
svenyeah. 'night!#asahi-dev · 2026-11-07 00:03
yukatomorrow is another day#asahi-dev · 2026-11-07 00:03
yukasame though#asahi-dev · 2026-11-07 00:03
yukahttps://termbin.com/yr69o#asahi-dev · 2026-11-07 00:03
svenugh... 1am.. I should go to bed instead :d#asahi-dev · 2026-11-07 00:02
svensometimes it's easy to see wtf is going on#asahi-dev · 2026-11-07 00:02
svenwhat instruction did it fault on? can you paste context() and bt() somewhere?#asahi-dev · 2026-11-07 00:02
yukalet me add them#asahi-dev · 2026-11-07 00:02
yukaI guess symbols for the release kernel are in the kdk#asahi-dev · 2026-11-07 00:02
yukadid we figure out where to get symbols?#asahi-dev · 2026-11-07 00:02
svenbut usually only once you're past the login screen#asahi-dev · 2026-11-07 00:02
yukaI don't have symbols#asahi-dev · 2026-11-07 00:01
svenxnu will complain about UNEXP_RT_HIT_DIR otherwise at some point#asahi-dev · 2026-11-07 00:01
sventhe AMCC hook just prevents panics #asahi-dev · 2026-11-07 00:01
yukayes#asahi-dev · 2026-11-07 00:01
svendoes unmapped IPA drop you to a hv shell? could try context and bt then#asahi-dev · 2026-11-07 00:01
yukafyi I also commented out the amcc hook#asahi-dev · 2026-11-07 00:00
svenhrm#asahi-dev · 2026-11-07 00:00
yukasingle cpu die yea#asahi-dev · 2026-11-07 00:00
svenm5 pro is still single die, isn't it?#asahi-dev · 2026-11-06 23:59
sventhat would mean shadow pageable corruption but I think I still map those as r/o to the guest#asahi-dev · 2026-11-06 23:59
svenhuh, I assume that address is just invalid?#asahi-dev · 2026-11-06 23:58
yukadid not have the serial open (only the vuart). I just retried and got HV: Unmapped IPA 0x5c1800bdc#asahi-dev · 2026-11-06 23:56
svenno SError or anything similar?#asahi-dev · 2026-11-06 23:56
sventhat's odd#asahi-dev · 2026-11-06 23:56
svenhuh#asahi-dev · 2026-11-06 23:56
yukaand then just rebooted#asahi-dev · 2026-11-06 23:56
svenyup :D#asahi-dev · 2026-11-06 23:55
yukait got way further \o/#asahi-dev · 2026-11-06 23:48
svenand then just add them to the vreg list in the .c and .py file and see if that's enough to get it to boot :D#asahi-dev · 2026-11-06 23:48
svenand then see if they are impdef