#
✕ nick:marcan
#asahi-dev · 2022-09-29 17:44
marcanit's fine if it goes in separately
#asahi-dev · 2022-09-29 17:38
marcanEighth_Doctor: no? also lol HN was already bad but it sure sounds like all the kiwifarmers ended up there recently.
#asahi-dev · 2022-09-29 17:37
marcanjannau: ack
#asahi-dev · 2022-09-29 11:12
marcanI'm basically doing it ad-hoc with a couple shell scripts, so anything would be an improvement over that :)
#asahi-dev · 2022-09-29 11:09
marcanin what sense?
#asahi-dev · 2022-09-29 10:38
marcanargh, crazy week with the Akademy talk I need to record... let me get that sent tonight, sorry :(
#asahi-dev · 2022-09-27 16:27
marcanah :)
#asahi-dev · 2022-09-27 16:26
marcantoo late, merged :p
#asahi-dev · 2022-09-27 16:08
marcanso barring some horrible hackery with /sys/foo/bind, if you want asmedia support and usb boot support, you need an initramfs
#asahi-dev · 2022-09-27 16:08
marcan(and if you don't provide firmware before the driver loads, it will fail to probe, and those machines will be stuck without USB on those ports)
#asahi-dev · 2022-09-27 16:06
marcanbecause that needs firmware
#asahi-dev · 2022-09-27 16:06
marcanand it never will
#asahi-dev · 2022-09-27 16:06
marcanno you don't, not with asmedia ports
#asahi-dev · 2022-09-27 16:05
marcanif that's a problem for you, get an initramfs ;)
#asahi-dev · 2022-09-27 16:05
marcanif you don't have an initramfs then you absolutely need to ensure that e.g. xhci-pci is not built in, which therefore implies that your distro can't support USB keyboards (or USB anything) until the rootfs loads at least udev, and obviously can't support root-on-USB either with the same kernel
#asahi-dev · 2022-09-27 16:03
marcanthe advantage of the initramfs is you don't have to play games with driver load order
#asahi-dev · 2022-09-27 16:03
marcanmps: shrug? then do it the same way you do it now with the tar
#asahi-dev · 2022-09-27 16:02
marcanand different distros might want to use /lib/firmware or /lib/firmware/vendor or something else and this gives them that choice
#asahi-dev · 2022-09-27 16:02
marcanI'm leaning towards (/)vendorfw/, since then we could symlink /lib/firmware/vendor to /vendorfw and add that to the kernel load list as I discussed (and it's nice and neutral)
#asahi-dev · 2022-09-27 16:01
marcanit's implicitly absolute as loaded by Linux
#asahi-dev · 2022-09-27 16:01
marcannot absolute, just adding at least one extra directory level
#asahi-dev · 2022-09-27 15:59
marcan(could also go with something generic like vendorfw/ and put a symlink in the initramfs; just something other than the current tarbomb)
#asahi-dev · 2022-09-27 15:58
marcankettenis: btw, for the cpio version, we'd use the /lib/firmware prefix since it gets loaded directly by the kernel (so filenames as lib/firmware/foo). would that be a significant issue for you?
#asahi-dev · 2022-09-27 15:57
marcan:(
#asahi-dev · 2022-09-27 15:53
marcanof course that's preconditioned on you getting PCIe xHCI support in first ;)
#asahi-dev · 2022-09-27 15:53
marcanone nice thing is that cpio is mildly less annoying to parse than tar, so if u-boot needs to grow support for this to pull xHCI firmware (for full USB port support on those Macs that have asmedia controllers) it could do that, instead of having to extract that separately.
#asahi-dev · 2022-09-27 15:52
marcanyeah, I can keep it as long as necessary, no problem
#asahi-dev · 2022-09-27 15:50
marcanand I would also have both versions for a while so as to not break your current installers of course, we have enough ESP space for that
#asahi-dev · 2022-09-27 15:48
marcanfor the OS-independent portion the only change is the switch to cpio
#asahi-dev · 2022-09-27 15:48
marcanthe firmware is just a CPIO archive in the ESP; linux bootloaders would load it as an additional initramfs and the main initramfs would handle the copying to a tmpfs mount. for BSD, up to you what you do :)
#asahi-dev · 2022-09-27 15:47
marcanthat would be a OS-specific thing
#asahi-dev · 2022-09-27 15:47
marcanyeah, I meant moving the initramfs firmware into a tmpfs instead of the real rootfs
#asahi-dev · 2022-09-27 15:40
marcanI don't think it can be done fully compliant with both formats by spec, but probably with actual implementations
#asahi-dev · 2022-09-27 15:39
marcankettenis: I suspect a polyglot ustar+cpio archive (that doesn't duplicate the data) can be done that would be accepted by both bsdtar and linux's cpio code, though I'm not sure if we want to push for such an abomination :D
#asahi-dev · 2022-09-27 15:38
marcancould just keep the firmware in RAM too, and never put it in the rootfs (which also helps avoid accidental re-distribution by users)
#asahi-dev · 2022-09-27 15:24
marcanI don't think that will be necessary for ARM64 ;)
#asahi-dev · 2022-09-27 15:21
marcankettenis: interesting, I thought cpio was pretty universal (and it's very simple)
#asahi-dev · 2022-09-27 15:06
marcansven: please feel free to clean up / hack on that as much as you want
#asahi-dev · 2022-09-27 14:39
marcanI think I got them either from the advertisement messages or from some rtkit ep name thing? I can't remember...
#asahi-dev · 2022-09-27 14:30
marcanthe inheritance hierarchy is a bit confusing
#asahi-dev · 2022-09-27 14:30
marcanor something like that
#asahi-dev · 2022-09-27 14:30
marcanas in, mcdp29xx is one implementation of dcpav
#asahi-dev · 2022-09-27 14:29
marcansven: I think it's mcdp29xx in some devices, but also more generally the dcpav stuff?
#asahi-dev · 2022-09-27 13:28
marcancool! the last pending thing we had in the prior submission was the cpu->perf domain binding, which was nonstandard, so I think fixing that plus breaking up clusters will solve all remaining issues.
#asahi-dev · 2022-09-27 13:27
marcanrobher: does that make sense? if so, I can do that I think, for v3 (I think it was v3 :))
#asahi-dev · 2022-09-27 13:25
marcanso we'd just have our driver match on apple,arm-platform and then look for the cluster nodes (and bail if it finds none that it can handle, which is what would happen on as-yet unsupported platforms, or if it sees mixed compatibles since that'd be weird)
#asahi-dev · 2022-09-27 13:25
marcanhuh, didn't know that was the recommended approach
#asahi-dev · 2022-09-27 13:24
marcanof_machine_is_compatible, as in looking for apple stuff?
#asahi-dev · 2022-09-27 13:23
marcancpufreq-mediatek-hw.yaml is basically what we do today, other than not using that generic binding (which I wasn't aware of)
#asahi-dev · 2022-09-27 13:22
marcanok, so then that just leaves the question of how to break this up into multiple cluster nodes as it ought to be represented, instead of one magic single device

plus ›