#
#asahi-gpu · 2026-07-09 10:47
noopwafelhttps://github.com/TellowKrinkle/applegpu/tree/M3 has .. maybe not up-to-date, but some stuff
#asahi-gpu · 2026-07-09 10:47
noopwafeland I can see from backscroll that you did get pointed at me quite a while ago :D sorry for not seeing your message above
#asahi-gpu · 2026-07-09 10:46
StanfordAppliedCyber[m]ack
#asahi-gpu · 2026-07-09 10:46
noopwafelyeah, for m3. I don't know if it's all pushed tbh, but it's just using the drm stub that the original bringup was also done using (via python)
#asahi-gpu · 2026-07-09 10:45
StanfordAppliedCyber[m]also where is the m3 disassembler?
#asahi-gpu · 2026-07-09 10:45
StanfordAppliedCyber[m]so you're saying m1n1 already has enough support to actually test mesa? at least to some limited extent
#asahi-gpu · 2026-07-09 10:44
noopwafelsure
#asahi-gpu · 2026-07-09 10:44
StanfordAppliedCyber[m]wdym, you need a way to actually alloate buffers and submit work to the gpu, does m1n1 already have enough support for that?
#asahi-gpu · 2026-07-09 10:44
noopwafelvia m1n1?
#asahi-gpu · 2026-07-09 10:43
StanfordAppliedCyber[m]how can you develop mesa without a working kernel driver?
#asahi-gpu · 2026-07-09 10:43
noopwafelwe have shaders working, not much in mesa yet
#asahi-gpu · 2026-07-09 10:43
StanfordAppliedCyber[m]i asked for resources a few times and no one pointed me to anything
#asahi-gpu · 2026-07-09 10:43
StanfordAppliedCyber[m]noopwafel: nah from scratch, i don't know how much work was done on the m3
#asahi-gpu · 2026-07-09 10:42
StanfordAppliedCyber[m]i bought a m5 also and will repeat the probing there
#asahi-gpu · 2026-07-09 10:42
noopwafelso based on the m3 disassembler..?
#asahi-gpu · 2026-07-09 10:42
StanfordAppliedCyber[m]probably the same
#asahi-gpu · 2026-07-09 10:42
StanfordAppliedCyber[m]noopwafel: i havent checked but all my probing is against m4
#asahi-gpu · 2026-07-09 10:42
StanfordAppliedCyber[m]tbh ik the devs here want me to work on stuff like pcie, speakers, etc first, but i really just want to jump straight into the gpu
#asahi-gpu · 2026-07-09 10:42
noopwafelbased on the existing m3 one? or is the isa totally different for m4 again?
#asahi-gpu · 2026-07-09 10:42
StanfordAppliedCyber[m]and a bunch of information on other userspace bits
#asahi-gpu · 2026-07-09 10:42
StanfordAppliedCyber[m]i have a disassembler with around 200 instructions understood
#asahi-gpu · 2026-07-09 10:41
StanfordAppliedCyber[m]oh yeah i did some extensive userspace re work
#asahi-gpu · 2026-07-09 10:30
noopwafelwould be amazing to be able to test on the m4 too.
#asahi-gpu · 2026-07-09 10:29
noopwafelwe've been super busy with other stuff but started to look at the kernel/mesa stack again the last few days..
#asahi-gpu · 2026-07-09 10:28
Sobek[m](The important thing is that he got a SPTM emulator working, however, his implementation of that is tainted, so he'll be writing spec of that part and someone else (yuka has volunteered iirc) will be writing a clean-room implemenation of that. In any case, that is still a huge breakthrough).
#asahi-gpu · 2026-07-09 10:27
noopwafelfor the record https://noopwafel.net/asahi/gpu_notes.txt has high-level notes and some pointers to the tree etc
#asahi-gpu · 2026-07-09 10:27
noopwafelthe M4 is pretty close gpu-wise I think! but good to know, I was worried my lack of attention led to wasted effort
#asahi-gpu · 2026-07-09 10:26
yukayep
#asahi-gpu · 2026-07-09 10:26
Sobek[m]I believe he is working on A18 Pro / M4, so different generation from M3 too.
#asahi-gpu · 2026-07-09 10:26
noopwafelah cool
#asahi-gpu · 2026-07-09 10:26
yukaso not gpu specific bits
#asahi-gpu · 2026-07-09 10:26
yukahe got macOS running in the m1n1 hv, and is trying to get the changes for that into an upstreamable shape
#asahi-gpu · 2026-07-09 10:25
noopwafelI do have the whole m1n1 stack for M3 GPU
#asahi-gpu · 2026-07-09 10:25
noopwafelStanfordAppliedCyber[m]: what're you refactoring?
#asahi-gpu · 2026-07-08 21:30
StanfordAppliedCyber[m]think yuka volunteered to get the sptm emulation working
#asahi-gpu · 2026-07-08 21:30
StanfordAppliedCyber[m]yep, i have traces from a18 pro, working on refactoring the clean (non sptm) side of the HV right now
#asahi-gpu · 2026-07-08 14:13
alyssaIntel indeed
#asahi-gpu · 2026-07-08 14:11
Dcow[m]if you*
#asahi-gpu · 2026-07-08 14:11
Dcow[m]alyssa: I am not sure if read other chat snow being busy wizard at Intel, but Stanford is working on HV support for never devices
#asahi-gpu · 2026-07-08 14:08
alyssaNeat
#asahi-gpu · 2026-07-08 14:05
Dcow[m]alyssa: I think Stanford already have the traces of GPU initdata with their HV
#asahi-gpu · 2026-07-08 11:35
alyssaI'd think until the hv issues are sorted looking into m4/a18 is kinda futile?
#asahi-gpu · 2026-07-08 00:03
StanfordAppliedCyber[m]my {dis}assembler i'm building works very well on both
#asahi-gpu · 2026-07-08 00:02
StanfordAppliedCyber[m]this isn't a surprising result, but good to confirm
#asahi-gpu · 2026-07-08 00:02
StanfordAppliedCyber[m]can confirm that the a18 pro userspace is at least very close to if not identical to the m4 userspace
#asahi-gpu · 2026-07-01 08:59
chadmedM3 progress, Apple bugs, and more! https://asahilinux.org/2026/06/progress-report-7-1/
#asahi-gpu · 2026-05-31 17:58
leio(to find some motivation for it one day perhaps)
#asahi-gpu · 2026-05-31 17:58
leioCould that explain some short frame freezes occasionally with some web video players in firefox too? Some players have the issues, others apparently not
#asahi-gpu · 2026-05-31 15:20
chnoblouch[m]Unfortunately, I only have access to an M3 MBA at the moment, so I can't contribute anything here
#asahi-gpu · 2026-05-31 15:06
karolherbstI don't have the time atm myself

plus ›