#asahi-dev · 2024-02-15 16:52
tobheright, a year has passed since and I don't think they listened#asahi-dev · 2024-02-15 16:47
zzywysmlooks like Hector gave a good explanation at https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/merge_requests/117#note_1672824#asahi-dev · 2024-02-15 16:34
tobheit isn't clear to me if that makes any sense. As I understand it the cpufreq implementation should be fairly generic and not require any special handling#asahi-dev · 2024-02-15 16:32
tobhehey, someone from the gnome team asked me what they should do with https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/merge_requests/117#asahi-dev · 2024-02-14 04:11
nicolas17...actually I think the Linux brcm driver doesn't properly understand capabilities either? :|#asahi-dev · 2024-02-14 03:44
nicolas17looks 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"#asahi-dev · 2024-02-14 03:05
nicolas17like if there's a MMIO write and ctx is None there, does it mean it was written by other hardware and not the CPU?#asahi-dev · 2024-02-14 03:02
nicolas17what does it mean when ctx is None in the proxyclient?#asahi-dev · 2024-02-14 01:35
nicolas17https://paste.rs/rErgc.txt this is the crash; but I'll just turn the touchbar back off and move on >.>#asahi-dev · 2024-02-14 01:34
nicolas17then 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)#asahi-dev · 2024-02-14 01:33
nicolas17I enabled CONFIG_TOUCHSCREEN_APPLE_Z2 and now it crashes when tiny-dfr starts#asahi-dev · 2024-02-14 01:25
nicolas17so that's a good idea#asahi-dev · 2024-02-14 01:25
nicolas17I think the brcm firmware is in fact the biggest thing in the initramfs#asahi-dev · 2024-02-14 01:24
zzywysmfor 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#asahi-dev · 2024-02-14 01:23
zzywysmif you're that low on memory, you might want to only copy the brcm drivers that correspond to your silicon#asahi-dev · 2024-02-14 01:22
nicolas17(that was mainly out of curiosity, I don't *need* touchbar for what I plan to test under the hv :p)#asahi-dev · 2024-02-14 01:21
zzywysmhttps://github.com/AsahiLinux/docs/wiki/Kernel-config-notes-for-distros#asahi-dev · 2024-02-14 01:20
zzywysmyes#asahi-dev · 2024-02-14 01:20
nicolas17CONFIG_DRM_ADP + CONFIG_TOUCHSCREEN_APPLE_Z2#asahi-dev · 2024-02-14 01:20
zzywysmCONFIG_TOUCHSCREEN_APPLE_Z2=m#asahi-dev · 2024-02-14 01:20
nicolas17found it#asahi-dev · 2024-02-14 01:15
nicolas17zzywysm: what kernel config do I need for the touchbar btw?#asahi-dev · 2024-02-14 01:15
nicolas17I think I need marcan_ to look into this and see if it's a documentation issue, a code issue, or a me-doing-it-wrong issue#asahi-dev · 2024-02-14 01:14
nicolas17brcm in /lib/firmware makes Wi-Fi work, apple in /vendorfw makes trackpad work#asahi-dev · 2024-02-14 01:11
nicolas17putting the brcm firmware in both /vendorfw and /lib/firmware makes m1n1 run out of memory (initramfs too big?)#asahi-dev · 2024-02-14 01:11
nicolas17lol#asahi-dev · 2024-02-14 01:09
nicolas17hmm that fixed trackpad but not brcm#asahi-dev · 2024-02-14 01:08
nicolas17because then the dracut script copied it to the tmpfs in the final root too#asahi-dev · 2024-02-14 01:07
nicolas17putting it in the initramfs in /vendorfw worked#asahi-dev · 2024-02-14 01:06
nicolas17welp#asahi-dev · 2024-02-14 00:56
zzywysmthat's the Asahi official spot#asahi-dev · 2024-02-14 00:56
zzywysmyou can try putting them in /lib/firmware/vendor instead#asahi-dev · 2024-02-14 00:55
nicolas17I must be putting them in the wrong place ._.#asahi-dev · 2024-02-14 00:55
zzywysmputting them in the initramfs should work#asahi-dev · 2024-02-14 00:55
nicolas17the 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"#asahi-dev · 2024-02-14 00:54
nicolas17zzywysm: why does putting them in the initramfs not work though?#asahi-dev · 2024-02-14 00:31
nicolas17it 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#asahi-dev · 2024-02-14 00:31
zzywysmyou have to list the paths to the firmware images in CONFIG_EXTRA_FIRMWARE#asahi-dev · 2024-02-14 00:31
zzywysmwhat you can do is load in firmware directly into the kernel image itself, instead of relying on it being in the initramfs#asahi-dev · 2024-02-14 00:30
zzywysmnicolas17: try https://github.com/AsahiLinux/docs/wiki/Reference-Asahi-kernel-config#asahi-dev · 2024-02-14 00:30
nicolas17it's failing to load *any* firmware though#asahi-dev · 2024-02-14 00:30
zzywysmnicolas17: that kernel config you're using doesn't have touchbar enabled, it's pretty old#asahi-dev · 2024-02-13 23:55
nicolas17"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"#asahi-dev · 2024-02-13 23:54
nicolas17and no touchbar or wireless... must be firmware then#asahi-dev · 2024-02-13 23:40
nicolas17hm I have keyboard but not trackpad#asahi-dev · 2024-02-13 23:39
nicolas17so everything is built in and the incompatible modules in the initramfs are ignored#asahi-dev · 2024-02-13 23:39
nicolas17except with kernel modules disabled#asahi-dev · 2024-02-13 23:38
nicolas17I built my own kernel with this https://github.com/AsahiLinux/PKGBUILDs/blob/main/linux-asahi/config#asahi-dev · 2024-02-13 23:38
j`eyyeah, I had run similar files with m1n1#asahi-dev · 2024-02-13 23:38
nicolas17ok you know what does work