#asahi-dev · 2026-06-16 14:15
sven:-)#asahi-dev · 2026-06-16 14:15
mazholy crap. now I need to pry the M4 from the SO's hands...#asahi-dev · 2026-06-16 13:40
jannauSYS_IMP_APL_VM_TMR_FIQ_ENA_EL2 access is fixed in 26.6 beta 2 (only tested M4/t8132)#asahi-dev · 2026-06-16 13:38
chaos_princessyes, i have the t6031#asahi-dev · 2026-06-16 13:36
yukat6030 specifically?#asahi-dev · 2026-06-16 13:33
chaos_princessthere are now 4 fields instead of 3#asahi-dev · 2026-06-16 13:33
chaos_princesswell, not unchanged, but rather not changed in a way that affects the driver#asahi-dev · 2026-06-16 13:32
chaos_princessalso, pmgr misc seems to be unchanged from t602x, will send that once someone sends me the t6030 xnu logs, as i am not sure how to figure out which specific pmgr mmio is responsible for it w/o that#asahi-dev · 2026-06-16 13:30
yukaI don't think I'll find time to do that today#asahi-dev · 2026-06-16 13:30
yukaAhh, I did not run the pmp specific tracer yet. Just have an older full trace lying around.#asahi-dev · 2026-06-16 13:29
chaos_princessjust run macos under the tracer, it will be obvious as to what is needed#asahi-dev · 2026-06-16 13:28
chaos_princessalso, change dev.flags.notify_pmp to dev.id1 !=0, there is some random stuff like the afnc bits that need to be always-on, but aren't marked as such#asahi-dev · 2026-06-16 13:27
chaos_princessi actually thought of doing it later today :P#asahi-dev · 2026-06-16 13:26
yukanice#asahi-dev · 2026-06-16 13:26
chaos_princesshttps://github.com/asahilinux/m1n1/blob/main/proxyclient/tools/pmp_assist.py - just use this#asahi-dev · 2026-06-16 13:26
yukaI think the t6031 pmp-report offsets might be unchanged from t6020, at least they appear a lot in my trace#asahi-dev · 2026-06-16 13:26
yukaI'm looking into it, yeah#asahi-dev · 2026-06-16 13:26
chaos_princessare you trying to add pmp support to t603x?#asahi-dev · 2026-06-16 13:25
yukachaos_princess: is the report-entry reg unk1_2 in the adt pmgr devices?#asahi-dev · 2026-06-16 13:06
chadmedyou can (and sometimes need to) disassemble your own shaders to poke at the ISA etc#asahi-dev · 2026-06-16 13:05
fl0id_oftcthis from alyssa might be helpful, though seems to more of a disassembler... https://github.com/AsahiLinux/gpu#asahi-dev · 2026-06-16 13:03
yukahttps://www.youtube.com/watch?v=SDJCzJ1ETsM#asahi-dev · 2026-06-16 13:02
yukahttps://www.youtube.com/watch?v=ObS6sdfus2w#asahi-dev · 2026-06-16 13:02
yukaTo get some idea of what you're getting yourself into, I can also recommend watching the XDC conference talks on the previous Apple GPU work#asahi-dev · 2026-06-16 13:01
chaos_princessstart here https://developer.apple.com/metal/#asahi-dev · 2026-06-16 13:01
JailbreakHat[m]Is there any sample shader program I can look at to get an idea?#asahi-dev · 2026-06-16 13:00
chaos_princesswell, the harness is objc(++), shader itself is msl#asahi-dev · 2026-06-16 13:00
chadmedor yeah objc#asahi-dev · 2026-06-16 13:00
chadmedyoull have to write them in MSL which much like other shader languages is just spicy c++#asahi-dev · 2026-06-16 13:00
chaos_princessobjc or objc++. Metal supports those#asahi-dev · 2026-06-16 12:59
JailbreakHat[m]fl0id_oftc: I am already doing that.#asahi-dev · 2026-06-16 12:59
JailbreakHat[m]chadmed: Do I need to write them in Swift, or is there any way to write them on C++ or Rust?#asahi-dev · 2026-06-16 12:59
fl0id_oftcyou can ofc look at the existing linux drivers to see how they work - but that will not show what is new in m3/m4 but should give you an idea maybe?#asahi-dev · 2026-06-16 12:56
chadmedyou write your own shaders that target specific parts of the render pipeline and see how those end up programming the gpu #asahi-dev · 2026-06-16 12:56
chaos_princess14:49:07 <chaos_princess> you don't RE by throwing stuff into ghidra, rather you run macos under a hypervisor and look at what it does#asahi-dev · 2026-06-16 12:56
chaos_princessideally nothing#asahi-dev · 2026-06-16 12:56
yukaYou poke at the driver by writing a simple shader program, letting the driver compile it and disassemble the compiled result#asahi-dev · 2026-06-16 12:56
JailbreakHat[m]chaos_princess: What should I disassemble instead?#asahi-dev · 2026-06-16 12:56
chaos_princessby not disassembling the driver#asahi-dev · 2026-06-16 12:55
JailbreakHat[m]yuka: Oh sorry, I read the documentation. But I just couldn't get how can I disassemble GPU hardware without breaching copyright policy?#asahi-dev · 2026-06-16 12:55
yukaplease read the copyright policy#asahi-dev · 2026-06-16 12:54
yukaif you are trying to find them in your system, this means you will probably disregard the copyright policy in the next step :(#asahi-dev · 2026-06-16 12:53
yukaon the page I linked: contributors must not disassemble or decompile userspace graphics driver binaries#asahi-dev · 2026-06-16 12:53
chaos_princessthis is the question that shows that you are going in the wrong direction#asahi-dev · 2026-06-16 12:52
JailbreakHat[m]s/?/./#asahi-dev · 2026-06-16 12:52
JailbreakHat[m]yuka: Where can I find the macos drivers? That was my confusion?#asahi-dev · 2026-06-16 12:51
yukaJailbreakHat: The way Asahi drivers are usually written is by poking at the macos drivers, poking at the hardware, in order to find out and understand how it works. Then, with that knowledge, you write your own thing.#asahi-dev · 2026-06-16 12:51
JailbreakHat[m]chaos_princess: Ok, if I have any questions, I will let you know#asahi-dev · 2026-06-16 12:51
chaos_princessthat should answer the questions on how to get started