#
#asahi-dev · 2026-04-16 14:16
wilfredorchaos_princess: so the missing piece is programming the reconfig engine before sleep, i already have an HV trace script ready to capture macOS sleep sequence, that should show the MMIO writes that program it. Also have the kernelcache extracted. Should I focus on the HV trace first, or is there a faster way, do you know where the reconfig engine registers live on T8103?
#asahi-dev · 2026-04-16 14:16
chaos_princessprobably not
#asahi-dev · 2026-04-16 14:14
wilfredorreconfig engine needs to be programmed with register write sequences BEFORE sleep and that code is likely in AppleARMPlatform.kext (btw not open-source XNU)
#asahi-dev · 2026-04-16 14:12
wilfredorM1 wakes directly to RVBAR via reconfig engine
#asahi-dev · 2026-04-16 14:11
wilfredorI found it in cpu.c, you are absolutely right
#asahi-dev · 2026-04-16 14:07
chaos_princesshttps://github.com/apple-oss-distributions/xnu/blob/rel/xnu-8792/osfmk/arm64/machine_routines_asm.s
#asahi-dev · 2026-04-16 14:06
wilfredorany specific file or subsyystem i should start with, or just grep for "reconfig"?
#asahi-dev · 2026-04-16 14:05
chaos_princessit is mentioned once or twice in the opensource xnu code.
#asahi-dev · 2026-04-16 14:05
wilfredorsorry i'm tired
#asahi-dev · 2026-04-16 14:04
wilfredorisn't a normal ARM
#asahi-dev · 2026-04-16 14:04
wilfredori didn't look into the reconfig engine at all. So what I observed was probably not a real wake, just a reset that I mistook for wake. Do you know where the reconfig engine is documented or where to find its registers on T8103? i need to understand what state it needs before sleep entry so cores actually resume at RVBAR, i spent severals hours tracing this assuming standard ARM wake behavior and Apple keeps #$@$# me, this
#asahi-dev · 2026-04-16 13:59
chaos_princessthat is x86 behavior, on arm, there is something called a "reconfig engine" that should dump you directly to rvbar
#asahi-dev · 2026-04-16 13:58
wilfredorjannau: DRAM does stay powered in my tests (framebuffer survived across wake), so it is sleep, not hibernate, the issue is iBoot still runs full cold boot init on wake even though DRAM is preserved. macOS must signal iBoot somehow to take a resume path instead of reinit
#asahi-dev · 2026-04-16 13:58
chaos_princessit is not signalling iboot
#asahi-dev · 2026-04-16 13:58
jannauis DRAM preserved or not? "DRAM overwritten" sound like not
#asahi-dev · 2026-04-16 13:56
jannauI don't think anyone would call something which does not preserve DRAM as sleep. that's hibernate
#asahi-dev · 2026-04-16 13:56
wilfredoryes you're right, it's effectively a reset, iBoot does full cold boot on wake, but DRAM does stay powered (framebuffer survived), so the hardware can preserve state, but without telling iBoot to resume instead of cold boot, it just reinits everything, that's why I want to HV-trace macOS sleep, to see how it signals iBoot to take the resume path instead of cold boot
#asahi-dev · 2026-04-16 13:55
chaos_princessofc they are, the memory layout is completely different
#asahi-dev · 2026-04-16 13:54
chaos_princesswell, yes
#asahi-dev · 2026-04-16 13:54
wilfredorT8103 addresses ARE different from T600x (M1 Pro/Max)
#asahi-dev · 2026-04-16 13:53
chaos_princessso, that is not a sleep, you just reset the machine
#asahi-dev · 2026-04-16 13:53
wilfredortested deep sleep on T8103. Key finding, wake doesn't go through RVBAR. iBoot runs full cold boot reinit on power button wake, DRAM overwritten, all scratch cleared, PMGR state identical to cold boot. So trampoline approach can't work. Wake path has to go through iBoot, like macOS does with hibernate image. Planning to HV-trace macOS sleep to understand how iBoot detects wake vs cold boot internally
#asahi-dev · 2026-04-16 13:51
wilfredorchaos_princess: one concrete T8103 difference — those wake event mask registers you write at 0x292004008-0x29200401c on T600x don't exist on T8103. Scanned full PMGR range, found 70 events but all performance/thermal counters, none writable as wake masks. Wake source filtering on T8103 seems entirely internal to SMC. Working on HV-tracing macOS sleep to confirm
#asahi-dev · 2026-04-16 09:03
fl0_idpsych if you check logs, you could help test my work on m3 max device trees. basics worked, more advanced things are not working yet. mainly also b/c I haven't had much time to work on it recently
#asahi-dev · 2026-04-16 09:02
fl0_idchadmed yeah I know but not all ppl know about them
#asahi-dev · 2026-04-16 09:01
chadmedfl0_id: there are logs of course
#asahi-dev · 2026-04-16 07:32
fl0_idhere was excited to have someone else test my m3 max DTs, but they left already..
#asahi-dev · 2026-04-16 05:34
psychHey folks, I'm a software dev out of NY. I have a M3 Ultra Max Studio that I'm willing to fk with. I was wondering if I could help test or help in the development of any of the M3 work that y'all are doing for M3 Asahi.
#asahi-dev · 2026-04-15 21:40
jannausolving a mostly cosmetic issue in Linux
#asahi-dev · 2026-04-15 21:39
jannau"Booting Linux on physical CPU 0x0000000000 [0x612f0420]" on M3, switching the boot CPU to the first efficiency core works
#asahi-dev · 2026-04-15 19:29
chaos_princessand the fact that these days a gpu is basically a second computer that is flying in close formation, and has a completely proprietary instruction set that changes with every generation
#asahi-dev · 2026-04-15 19:27
chaos_princessefi and architecture are irrelevant, the hard bits are the lack of documentation and the fact that computers do a lot more these days
#asahi-dev · 2026-04-15 19:21
cyberheadi heard one could emulate a mac on an amiga, though
#asahi-dev · 2026-04-15 19:21
cyberheadthere were so many m68k-based machines that were completely incompatible
#asahi-dev · 2026-04-15 19:21
cy8aerright
#asahi-dev · 2026-04-15 19:20
cyberheadcy8aer: proprietary stuff as well
#asahi-dev · 2026-04-15 19:14
tpw_rulesand computers are more advanced 40 years later
#asahi-dev · 2026-04-15 19:12
cy8aerAnd the arm architecture is quite different and nothing is known about the communication from the OS to the Hardware out-of-the-box
#asahi-dev · 2026-04-15 19:11
cy8aerIt does not have efi
#asahi-dev · 2026-04-15 19:07
cyberheadwhat makes asahi linux so much more difficult than linux/mac68k ever was?
#asahi-dev · 2026-04-15 17:01
freetolgasorry
#asahi-dev · 2026-04-15 17:01
freetolga
#asahi-dev · 2026-04-15 16:11
tryhard[m]what is the usual power usage in m1 air? and how you check it?
#asahi-dev · 2026-04-15 14:00
tryhard[m]i don't know how it uses drvdata exactly, but i'm sure there some place
#asahi-dev · 2026-04-15 14:00
chaos_princesswhatever
#asahi-dev · 2026-04-15 13:59
tryhard[m]to my driver struct?
#asahi-dev · 2026-04-15 13:59
chaos_princessit's own field where?
#asahi-dev · 2026-04-15 13:59
tryhard[m]and get_drvdata will be adjusted
#asahi-dev · 2026-04-15 13:58
chaos_princesswell, more like it needs to store your driver struct somewhere and it picked drvdata
#asahi-dev · 2026-04-15 13:58
tryhard[m]it could copy the data to its own field

plus ›