#
#asahi-dev · 2025-08-04 08:14
chaos_princessyea, let's just keep your branch
#asahi-dev · 2025-08-04 08:06
jannaudiff is a little noisy since I did cleanup/refactoring in some branches. I think my conflict resolution for wifi is less likely to cause problems for other brcmfmac chipsets
#asahi-dev · 2025-08-04 08:05
chaos_princessunintentional, i think i've started from the wrong-ish branch
#asahi-dev · 2025-08-04 08:02
jannauchaos_princess: there was some delta between your 6.16 bits branches and mine. It looked like you undid some of aop probe changes. was that intentional? please check
#asahi-dev · 2025-08-03 18:48
sveni think we just need to continue upstreaming the current backlog and ideally then start working upstream first for new hardware support
#asahi-dev · 2025-08-03 18:43
jannauI think it's a bad idea because it'll end in madness because you end up with implementing thin in 5 to 10 bootloaders then
#asahi-dev · 2025-08-03 18:42
jannausven: u-boot / grub have code to select the matching dt based on the kernel version
#asahi-dev · 2025-08-03 18:06
svenwhich sucks, but that shouldn't happen for anything that's upstream
#asahi-dev · 2025-08-03 18:05
svenI don't see how that's caused by the kboot.c surgery. that usually happens because the downstream bindings change while we're upstreaming them
#asahi-dev · 2025-08-03 18:01
tpw_rulesit means things can break if you need to use an older kernel cause the device trees don't match anymore
#asahi-dev · 2025-08-03 17:47
sven*been
#asahi-dev · 2025-08-03 17:47
svenit’s bern working fine for us so far
#asahi-dev · 2025-08-03 17:47
svenagree to disagree I guess
#asahi-dev · 2025-08-03 16:41
tpw_ruleshaving it do so much surgery on embedded device trees is not great
#asahi-dev · 2025-08-03 16:41
tpw_rulesi guess m1n1 does not want its own extlinux loader
#asahi-dev · 2025-08-03 16:37
nickchannothing to worry about for upstream then other than the everything compiled for armv8.2-a which is not even the reason things are breaking
#asahi-dev · 2025-08-03 16:36
nickchanuart doesn't have that issue so it's an iodev issue after all I will see
#asahi-dev · 2025-08-03 16:35
chaos_princessalso, this https://github.com/AsahiLinux/m1n1/pull/466 will happen at some point in the future
#asahi-dev · 2025-08-03 16:34
jannautons of stuff. `git log -- 'src/kboot*'`
#asahi-dev · 2025-08-03 16:34
tpw_ruleswhat has changed in the past?
#asahi-dev · 2025-08-03 16:33
jannauso now you have two things you have to update if something changes
#asahi-dev · 2025-08-03 16:33
tpw_rulesi think that's the latest version of my patch to do that
#asahi-dev · 2025-08-03 16:33
tpw_ruleshttps://github.com/nix-community/nixos-apple-silicon/blob/b9e89a2b2580d5239bf8b2ca9efc1af0e313ab22/nix/u-boot/0001-m1n1-fdt-compat.patch
#asahi-dev · 2025-08-03 16:33
jannauu-boot would need to copy all the dynamic information m1n1 fills in kboot to the dtb
#asahi-dev · 2025-08-03 16:33
chaos_princessok, and how is that related? The per-device data is calculated in m1n1
#asahi-dev · 2025-08-03 16:32
nickchanunforunately that does not fix the issue so I need to look further, probably good idea to keep the change in makefile though
#asahi-dev · 2025-08-03 16:32
tpw_rulesit has hooks to patch up a loaded device tree
#asahi-dev · 2025-08-03 16:31
chaos_princessi am not sure how u-boot is involved in that?
#asahi-dev · 2025-08-03 16:29
tpw_ruleshi i'm being bothered by device tree differences again. is it possible to have u-boot copy the per-boot/per-device DT stuff to a device tree it loads itself so they can be kept with the kernel instead of m1n1? i made a patch several years ago but the plan was not accepted. maybe things have changed now?
#asahi-dev · 2025-08-03 16:27
nickchangot it, add .arch armv8.2-a to all the inline asms and it is fine (the critical ones happen via the sysreg wrapper so it really is just 2)
#asahi-dev · 2025-08-03 16:24
nickchanfix the issues here
#asahi-dev · 2025-08-03 16:24
nickchanlinux uses -Wa,-march=armv8.4-a -DARM64_ASM_ARCH="armv8.4-a" but that still doesn't fix the
#asahi-dev · 2025-08-03 16:18
nickchannah there's also a bunch in src/exception.c but linux must be somehow dealing with all of this
#asahi-dev · 2025-08-03 16:13
nickchanugh there's also PAN register but I suppose I could move that to asm files
#asahi-dev · 2025-08-03 16:09
nickchanthat makes it a bit easier to deal with
#asahi-dev · 2025-08-03 16:08
nickchanokay all the inline sysreg accesses that causes issues when compiled with -march=armv8-a is within the hv files
#asahi-dev · 2025-08-03 16:05
nickchanthis could become an issue down the line for macs too if some newer arm msr needed to be accessed
#asahi-dev · 2025-08-03 15:58
nickchanand there's inline asm everywhere
#asahi-dev · 2025-08-03 15:55
nickchanokay now that's fun because I have to instruct the compiler to not emit lse atomics while still allowing all those sysreg accesses to happen
#asahi-dev · 2025-08-03 15:54
nickchanit was never changed
#asahi-dev · 2025-08-03 15:49
jannauwe're building with "-march=armv8.2-a". did you change that already? not sure what could blow but LSE atomics certainly would
#asahi-dev · 2025-08-03 15:46
nickchanand it was not like this
#asahi-dev · 2025-08-03 15:46
nickchanit's truly weird
#asahi-dev · 2025-08-03 15:46
nickchanjannau: im looking into the behaivor because I cannot reproduce the behaivor on a8 and a11 but can on a7 and a10
#asahi-dev · 2025-08-03 15:44
svenand then once tbt + pcie hotplug is there it's maybe finally time to buy a m3 or m4 for me ;)
#asahi-dev · 2025-08-03 15:44
sven:D
#asahi-dev · 2025-08-03 15:43
chaos_princessyea, a certain someone decided to write a rust driver, and well... :P
#asahi-dev · 2025-08-03 15:43
svenso i'm gonna try and upstream it step by step
#asahi-dev · 2025-08-03 15:42
svenessentially i just don't want to create another situation where there are 30+ downstream patches for tbt again
#asahi-dev · 2025-08-03 15:42
svenchaos_princess: yup, and maybe usb4 tunneling since that's easy

plus ›