#asahi-dev · 2026-06-04 04:00
StanfordAppliedCyber[m]the kernel works fine and my emulation is good#asahi-dev · 2026-06-04 04:00
StanfordAppliedCyber[m]fwiw i'm not super worried about most of userspace#asahi-dev · 2026-06-04 03:59
StanfordAppliedCyber[m]launchd#asahi-dev · 2026-06-04 03:59
nicolas17StanfordAppliedCyber[m]: any idea what process? or are you not even getting past launchd yet?#asahi-dev · 2026-06-04 03:37
StanfordAppliedCyber[m]i'll figure out how the regular arm fallback paths work, hoping it's just some sysctls#asahi-dev · 2026-06-04 03:37
StanfordAppliedCyber[m]userspace is currently dying on SIGILL#asahi-dev · 2026-06-04 03:37
StanfordAppliedCyber[m]the kernel hasn't required any patching other than genter --> hvc#asahi-dev · 2026-06-04 03:37
StanfordAppliedCyber[m]i can confirm btw that there's some apple custom funkiness in userspace and is NOT in the kernel#asahi-dev · 2026-06-03 22:03
jannauand the recently "fixed" chainload.py#asahi-dev · 2026-06-03 22:01
yukaWorks with kisd#asahi-dev · 2026-06-03 21:50
StanfordAppliedCyber[m]or is it still messed up#asahi-dev · 2026-06-03 21:50
StanfordAppliedCyber[m]also hows chainload on the neo working? does it work yet?#asahi-dev · 2026-06-03 21:45
yukaTrue#asahi-dev · 2026-06-03 21:45
yukaOhhh right#asahi-dev · 2026-06-03 21:44
jannauit wasn't intended to switch the cpu core and keep using m1n1 but only for kboot#asahi-dev · 2026-06-03 21:43
jannauit's possible that there is still code checking cpuX.state == "running" to determine the boot cpu#asahi-dev · 2026-06-03 21:42
StanfordAppliedCyber[m]like check the clockspeed?#asahi-dev · 2026-06-03 21:42
StanfordAppliedCyber[m]what do you mean "measure the first pcore"?#asahi-dev · 2026-06-03 21:42
yukaSo I can not measure latencies of the boot core after switching away from it#asahi-dev · 2026-06-03 21:41
yukaI think smp call is somehow broken after switch_boot_core#asahi-dev · 2026-06-03 21:40
yukapresumably because the boot core is configure not to go to deep sleep#asahi-dev · 2026-06-03 21:39
yukaBut not the second pcore#asahi-dev · 2026-06-03 21:39
yukaI can measure the first pcore (boot core) of the Neo at the highest expected clock#asahi-dev · 2026-06-03 21:23
StanfordAppliedCyber[m]i'll move over to the re channel as a precaution here though i think it's unnecessary#asahi-dev · 2026-06-03 21:22
StanfordAppliedCyber[m]"write your own struct based on apsl source", so there's a few things there, there's the data types which i can just use primitive types for instead of the apple named ones, but the names themselves mostly describe hardware facts#asahi-dev · 2026-06-03 21:21
cy8aerjannau: reverting 30fcc498ff7c and applying f5cd0acdc21d works for me. Complete different behavior: the phones connect by themselves and sound.#asahi-dev · 2026-06-03 21:19
chaos_princessyou write your own struct based on the apsl source#asahi-dev · 2026-06-03 21:19
StanfordAppliedCyber[m]from looking at the code, I think this is safe to include in clean room docs, but i wanted to ask your thoughts here to confirm, and if you think it's overly risky then to ask for alternative paths forward#asahi-dev · 2026-06-03 21:16
StanfordAppliedCyber[m]the fields of the struct are all in the public xnu source but the offsets need to be found either by REing apple's compiled kernel or from the kdk (how i found it)#asahi-dev · 2026-06-03 21:16
StanfordAppliedCyber[m]this struct is contained in the KDK and APSL2 licensed#asahi-dev · 2026-06-03 21:15
StanfordAppliedCyber[m]also wanted to ask about a specific edge case-- we have to pass a big struct to xnu containing information about sptm, memory mappings, a bunch of other stuff#asahi-dev · 2026-06-03 21:10
cy8aerjannau: Compiling, stay tuned!#asahi-dev · 2026-06-03 21:06
StanfordAppliedCyber[m]not to mention i figured the risk is extremely low-- even if the traces end up just confirming what we know about dart, it's functionally just the same as looking at an m1n1 hv trace and doesn't taint the people working on it#asahi-dev · 2026-06-03 21:03
StanfordAppliedCyber[m]this may be a theoretical barrier, maybe yuka or others are just better devs than me and can get it working just with the high level overview, but my expectation is that with a runtime trace resolving some of these edge cases will be extremely difficult if not impossible#asahi-dev · 2026-06-03 21:03
jannaubluetooth audio issues confirmed on 7.0.11, bt trackball works though#asahi-dev · 2026-06-03 21:02
jannaucy8aer: I switched brcmext patch from v2 to v3. can you try to revert 30fcc498ff7c and apply f5cd0acdc21d#asahi-dev · 2026-06-03 21:02
StanfordAppliedCyber[m]there's a reason i'm not using the m1n1 code as it is currently#asahi-dev · 2026-06-03 21:01
StanfordAppliedCyber[m]re: traces, the thing that concerns me is that there's a lot of edge case behavior that in some cases took me days/weeks to get to the bottom of because the failure symptoms were so far removed from the actual root cause#asahi-dev · 2026-06-03 21:01
StanfordAppliedCyber[m]sven: thanks for the advice here!#asahi-dev · 2026-06-03 20:59
cy8aerThese wireplumber messages are around 22:43:14#asahi-dev · 2026-06-03 20:58
cy8aerDisabling bluetooth and enabling again does crash the system sometimes (!). I do not have any of these efects with asahi-7.0.10-2 or before.#asahi-dev · 2026-06-03 20:56
cy8aerI do not see anything in dmesg, but I can offer a journalctl of the session: https://nc.g3la.de/index.php/s/6r4Le3kFzCdLxgT#asahi-dev · 2026-06-03 20:56
cy8aerHi there, I somehow have problems with the bluetooth stack and asahi-7.0.11-1. I connect some Linkbuds S via Bluetooth but no sounds. The only thing I can see there are some wireplumber "firmware bug" messages. I disconnected the phones and tried to reconnect but this was not possible anymore. #asahi-dev · 2026-06-03 20:20
jannaunot too late to change that#asahi-dev · 2026-06-03 20:13
chaos_princesskinda regretting putting pdm coefficients in driver, m3 has 2046 instead of 120#asahi-dev · 2026-06-03 19:43
yukabut we are not allowed to do that :(#asahi-dev · 2026-06-03 19:43
yukaReading xnu code, it should configure sleep through ACC_OVRD like on other devices#asahi-dev · 2026-06-03 19:42
yukaBecause of the cpufreq things, I started looking into sleep behavior on M4 again#asahi-dev · 2026-06-03 19:31
tryhard[m]i thought that's what causes my new crash executing from non-executable memory after gpu init#asahi-dev · 2026-06-03 19:30
tryhard[m]how do they know pmp is booting?