ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
wrender has quit [Ping timeout: 480 seconds]
mariogrip has quit [Ping timeout: 480 seconds]
<zzywysm>
nicolas17: that kernel config you're using doesn't have touchbar enabled, it's pretty old
<nicolas17>
it's failing to load *any* firmware though
<zzywysm>
what you can do is load in firmware directly into the kernel image itself, instead of relying on it being in the initramfs
<zzywysm>
you have to list the paths to the firmware images in CONFIG_EXTRA_FIRMWARE
<nicolas17>
it seems /lib/dracut/hooks/{pre-udev/10-load-asahi-firmware.sh,cleanup/99-install-asahi-firmware.sh} expect to find a firmware tarball in EFI
<nicolas17>
zzywysm: why does putting them in the initramfs not work though?
<nicolas17>
the wiki says "for tethered boot we recommend a kernel with modules disabled (all built-in). You can ignore the Arch Linux initramfs, but you should instead provide an initramfs with /lib/firmware/{brcm/apple} to make sure the built-in modules can find their firmware early"
<zzywysm>
putting them in the initramfs should work
<nicolas17>
I must be putting them in the wrong place ._.
<zzywysm>
you can try putting them in /lib/firmware/vendor instead
<nicolas17>
(that was mainly out of curiosity, I don't *need* touchbar for what I plan to test under the hv :p)
<zzywysm>
if you're that low on memory, you might want to only copy the brcm drivers that correspond to your silicon
<zzywysm>
for example, on my M1 MacBook Air, i only need the brcm drivers that contain "shikoku". you can find the string that corresponds to your silicon in the devicetrees
jeisom has quit [Read error: Connection reset by peer]
jeisom has joined #asahi-dev
<nicolas17>
I think the brcm firmware is in fact the biggest thing in the initramfs
<nicolas17>
so that's a good idea
jeisom has quit [Remote host closed the connection]
jeisom has joined #asahi-dev
<nicolas17>
I enabled CONFIG_TOUCHSCREEN_APPLE_Z2 and now it crashes when tiny-dfr starts
<nicolas17>
then proxyclient runs objdump to get the disassembly or something, objdump outputs some unicode, and proxyclient crashes... why are computers like this /o\ (LANG=C fixes that)
<nicolas17>
https://paste.rs/rErgc.txt this is the crash; but I'll just turn the touchbar back off and move on >.>
KxCORP has quit [Quit: Bye!]
KxCORP has joined #asahi-dev
Bertrand___ has quit [Ping timeout: 480 seconds]
jeisom has quit [Ping timeout: 480 seconds]
Bertrand___ has joined #asahi-dev
<nicolas17>
what does it mean when ctx is None in the proxyclient?
<nicolas17>
like if there's a MMIO write and ctx is None there, does it mean it was written by other hardware and not the CPU?
john-cabaj1 has joined #asahi-dev
john-cabaj has quit [Read error: Connection reset by peer]
john-cabaj1 is now known as john-cabaj
john-cabaj has quit [Ping timeout: 480 seconds]
<nicolas17>
looks like trace/pcie.py doesn't understand PCI capabilities, that may be useful to add, at the very least so that we can see the MMIO accesses in the log and say "oh it's caps I can ignore that"
Bertrand___ has quit [Remote host closed the connection]
Bertrand___ has joined #asahi-dev
<nicolas17>
...actually I think the Linux brcm driver doesn't properly understand capabilities either? :|