<yuni>
That leaves A14 (H13P), M1 Pro (H13J), M1 Max (H13J), and H13J (M1 Ultra) within the 13 family
<yuni>
So maybe Pro/Max are G13X and Ultra is G13S or something like that?
<yuni>
...Wait. Those were the Metal drivers.
<yuni>
For the kernel driers, I see G131G, G13G, and G13X only.
<yuni>
*G11G
<yuni>
Maybe M1 Pro, M1 Max, and M1 Ultra are all G13X where X denotes "some letter other than P or G"
<yuni>
All three share a kernel driver, AGXG13X.kext
<yuni>
And ordinarily all three share a userspace driver, AGXMetalG13X
<yuni>
Except some early stepping of one of them (the "A0" stepping of "G13S") had some hardware bug requiring a workaround in userspace, and the workaround was invasive enough to compile a separate variant of the driver?
<yuni>
That would imply that the H13J names in the wiki are wrong
<yuni>
$ ls /System/Library/Extensions/AGXMetal*.bundle/Contents/Resources/*Statistics*derived.js | cat
<yuni>
reveals that 13_3 is 13_3, A12 is both A12 *and* A12X, G13S_A0 is A14X, and G13X is also A14X
<yuni>
not super illumintating
<yuni>
I'm pretty sure the H13J names on the wiki are wrong, I don't see where they came form
<yuni>
Looks like @woachk added those names
<jannau>
yuni: adt has in iop-aop-nub "firmware-name = mac13jaop" for m1 max/ultra, m1/m2 have mac13gaop / mac14gaop
<jannau>
m1 pro has "mac13jaop" as well
nicolas17 has joined #asahi-dev
zzywysm has quit [Remote host closed the connection]
zzywysm has joined #asahi-dev
Catyre has joined #asahi-dev
the_lanetly_052___ has quit [Ping timeout: 480 seconds]
Catyre has quit [Ping timeout: 480 seconds]
<marcan>
I think the graphics core has its own naming scheme. apple loves to have random inconsistent naming schemes.
Catyre has joined #asahi-dev
Catyre has quit [Read error: Connection reset by peer]
Catyre has joined #asahi-dev
zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]