#asahi-dev · 2026-07-06 19:05
sventhe end of .text / beginning of .data is only 16 KiB aligned and what i care about here#asahi-dev · 2026-07-06 19:04
jannauwe might have aligned a few bits to 64k for u-boot#asahi-dev · 2026-07-06 19:04
svenah, good#asahi-dev · 2026-07-06 19:04
chaos_princessdon't worry too much about it, it just prints a warning and proceeds anyway#asahi-dev · 2026-07-06 19:04
svengetting all this into u-boot or other 2nd stage loaders is going to be more fun#asahi-dev · 2026-07-06 19:04
sventhe efi table i build will only work for directly chainloaded kernels anyway#asahi-dev · 2026-07-06 19:03
chaos_princessi think sd-boot whines about it#asahi-dev · 2026-07-06 19:03
chaos_princessabout that#asahi-dev · 2026-07-06 19:03
sven*adjust#asahi-dev · 2026-07-06 19:03
svenokay, good. UEFI technically requires all memory descriptors to be 64KiB aligned but i guess we can get away with 16 KiB then and I don't have to just the ld scripts :)#asahi-dev · 2026-07-06 19:01
jannauI don't think so#asahi-dev · 2026-07-06 19:00
sven is there any M-series chip that support 64 KiB pages?#asahi-dev · 2026-07-06 19:00
jannauwe don't care about bridge or device node for the normal devices. we might for mac pro. let me check#asahi-dev · 2026-07-06 18:58
jannauI misread pcie bridge for pcie controller node#asahi-dev · 2026-07-06 18:58
yukaso one pwren gpio per port#asahi-dev · 2026-07-06 18:58
yukaso different ports#asahi-dev · 2026-07-06 18:57
yukabut they are on different pcie-bridges?#asahi-dev · 2026-07-06 18:55
jannauit's not much of a problem since those gpios are active on m1n1 start#asahi-dev · 2026-07-06 18:54
jannau14/16-inch macbook pros and imacs, mac studios and possibly m2* mac minis#asahi-dev · 2026-07-06 18:53
yukawhich mac device/model?#asahi-dev · 2026-07-06 18:52
jannausd-card and usb-pcie xhci have separate ones#asahi-dev · 2026-07-06 18:52
yukais there any case of two pwren-gpios for the same slot?#asahi-dev · 2026-07-06 18:52
yukawifi and bluetooth have the same pwren-gpio#asahi-dev · 2026-07-06 18:52
yukain our case they don't?#asahi-dev · 2026-07-06 18:51
jannauyuka: wouldn't the regulator need to be per-device since devices have distinct pwren-gpios#asahi-dev · 2026-07-06 18:51
yukaI think I'll need to ask the pci people about some things anyways, so I'm preparing a minimal RFC with something that works but I know isn't good (and then some questions regarding how to make it good)#asahi-dev · 2026-07-06 18:50
jannauflokli: using lib/firmware/vendor in firmware.cpio isn't compatible with usr-merge#asahi-dev · 2026-07-06 18:26
flokliOr well, initrd would only need to bind-mount / copy it to the rootfs before switch_root. So initializing hardware requiring vendorfw with kernel modules only in the real rootfs stays possible.#asahi-dev · 2026-07-06 18:19
flokliWould it make sense to change the layout inside the cpios though? Right now it contains a vendorfw/ directory, but maybe it should be lib/firmware/vendor, so we don't need to do any silly copying around where the bootloader appends it as an additional initrd.#asahi-dev · 2026-07-06 18:17
flokli<sven> probably better in #asahi-dev, but neal has an updated version and wanted to submit that patch#asahi-dev · 2026-07-06 18:16
svenpeter[m]from #asahi-re:matrix.org #asahi-dev · 2026-07-06 18:16
svenpeter[m]20:13:24 <flokli> The section starts with "we propose", but I don't see if it's only proposed in the docs, or with upstream.#asahi-dev · 2026-07-06 18:16
svenpeter[m]Neal Gompa (Fedora): 20:12:50 <flokli> Has there been any discussion with upstream about the /lib/firmware/vendor additional path, as per https://asahilinux.org/docs/platform/open-os-interop/#linux-specific ?#asahi-dev · 2026-07-06 17:27
yukaokay, so people back then weren't sure if the regulator should go into the pcie bridge node or in the device node beneath it#asahi-dev · 2026-07-06 17:15
yukagoes to read old mailing list threads#asahi-dev · 2026-07-06 17:04
yukabesides powering it on and then off again#asahi-dev · 2026-07-06 17:03
yukaI'm not sure there is an equivalent to this in the pci-pwrctrl api :(#asahi-dev · 2026-07-06 17:02
yukadownstream we avoid this: "check whether the GPPIO pin exists but leave it as is" before we even start initializing anything else#asahi-dev · 2026-07-06 17:00
yukathe other pcie drivers which support pci-pwrctrl don't have special handling for this, so they start initializing, fail and get retried#asahi-dev · 2026-07-06 16:59
yukaalso console spam#asahi-dev · 2026-07-06 16:57
yukathat might cause problems if the resources are not fully cleaned up each time#asahi-dev · 2026-07-06 16:57
yukaHuh, it seems the power on fails with -EPROBE_DEFER multiple times, and because I pass through the error code our entire probe gets called again at a later point?#asahi-dev · 2026-07-06 16:42
yukait works!#asahi-dev · 2026-07-06 15:57
yukaYes, I found a good summary here: https://lwn.net/Articles/1052333/#asahi-dev · 2026-07-06 15:52
jannauyuka: my understanding was that it now requires changes in pcie-apple. change in v7.0 (or maybe v6.19)#asahi-dev · 2026-07-06 15:49
yukaOr it needs changes to pcie-apple?#asahi-dev · 2026-07-06 15:47
yukaOr maybe I misunderstood that pci-pwrctrl-generic could be used for this#asahi-dev · 2026-07-06 15:36
yukabut could not yet make pci-pwrctrl-generic actually enable the gpios through the regulator#asahi-dev · 2026-07-06 15:35
yukaI can make it "work" by adding a regulator which is always-on and enables those gpios#asahi-dev · 2026-07-06 15:34
yukaI wanted to give the pci-pwrctrl-generic a try for the pcie pwren gpios