#asahi-dev · 2026-06-05 15:36
svenwould be very annoying if that also changed on m1/2/3 with that fw#asahi-dev · 2026-06-05 15:32
svenugh#asahi-dev · 2026-06-05 15:31
svenwhat kind of errors?#asahi-dev · 2026-06-05 15:30
svenwhat makes you think that? does changing the two register offsets not make them work?#asahi-dev · 2026-06-05 15:29
sveneven more annoying :(#asahi-dev · 2026-06-05 15:27
svendo we know at which version they changes this? 26.0?#asahi-dev · 2026-06-05 15:26
svenespecially cause we don't know what they'll change next time#asahi-dev · 2026-06-05 15:26
svenagreed#asahi-dev · 2026-06-05 15:23
svendon't really care though, both options kinda suck i think#asahi-dev · 2026-06-05 15:22
sveni was thinking about adding the minimal fw verison where it changes to the compatible string#asahi-dev · 2026-06-05 15:19
svenor maybe just add a new compatible without the apple,firmware-version that only works for the new fw version, dunno what's better#asahi-dev · 2026-06-05 15:12
svenand patch the device trees to the new compatible on m1/m2 if we are running on a newer version *sigh*#asahi-dev · 2026-06-05 15:11
svenso i guess for linux we need to introduce a new compatible with a required apple,firmware-version property and use that for m3+#asahi-dev · 2026-06-05 14:59
svencmd.cdw12 is just a bug i think because i read the nvme spec wrong and the controller on m1/m2 didn't mind#asahi-dev · 2026-06-05 14:59
svenso really just two registers + SART needs a bigger allowed region apparently#asahi-dev · 2026-06-05 14:59
svenhttps://gist.github.com/Artingl/c5e7f9fbb0307f7c236e29e4f1fc1f8e those are the nvme differences#asahi-dev · 2026-06-05 08:53
svenif that works maybe just send that as a RFC to the spmi maintianers with our usecase and see what they think#asahi-dev · 2026-06-05 08:52
svenlooks like that should be enough to directly talk to the tipd chip#asahi-dev · 2026-06-05 08:52
svenhah, https://cyberchaos.dev/yuka/linux/-/commit/88b7ece864c3a05342a10fa3b82260b18e3271ad is the interface you could use, isn't it? :D#asahi-dev · 2026-06-05 08:51
sventhere are also some old commit by jannau somewhere that directly add some sysfs or debugfs or whatever thing to tipd iirc#asahi-dev · 2026-06-05 08:50
svenmight be a good idea to ask the spmi maintainers what they think about a generic i2c-style userspace interface#asahi-dev · 2026-06-05 08:50
sveneither that or create a /dev node like the i2c interface. but i guess sysfs might be easier#asahi-dev · 2026-06-05 08:48
svenif that's accepted upstream, yeah. otherwise add a userspace interface to tipd to send commands#asahi-dev · 2026-06-05 08:47
sveni2c was convenient because you can just send commands from userspace, dunno if that's possible with spmi but i don't think so#asahi-dev · 2026-06-05 08:47
svenyes#asahi-dev · 2026-06-05 08:44
svenpresumably with a fixed firmware stored in ROM since i haven't seen anything in the ipsws#asahi-dev · 2026-06-05 08:44
sveni'm pretty sure that microcontroller is yet another core part of the main SoC fwiw. it also exposes SWD/JTAG via that debugusb protocol on development-fused devices#asahi-dev · 2026-06-05 08:35
svenyeah, it's the two or so registers that moved to a new location then#asahi-dev · 2026-06-05 08:35
svenand as long as there are no further changes to the usb2 phy device mode should mostly just work if you manage to bypass the hub#asahi-dev · 2026-06-05 08:34
sveniirc it was just that two registers moved to a new place#asahi-dev · 2026-06-05 08:34
svendidn't someone already reverse engineer the nvme changes for that newer firmware? or have they changed even more for the neo now?#asahi-dev · 2026-06-04 19:12
svenjust had to create it to send it to someone i know#asahi-dev · 2026-06-04 19:12
sventhat's it essentially :D#asahi-dev · 2026-06-04 19:12
svenFB21831949 / Write access to sys_reg(3, 5, 15, 1, 3) / APL_INTENABLE_EL2 faults in non-Apple-entitled boot mode#asahi-dev · 2026-06-04 19:11
sveneh.. it wants my google account to login. i'd rather not#asahi-dev · 2026-06-04 15:12
sventhere’s some dynamic debug thing that only enabled dev_dbg for a single file iirc #asahi-dev · 2026-06-04 14:50
svendo you have your full code somewhere?#asahi-dev · 2026-06-04 14:48
sveni think there's also some kernel commandline arg to enable debug for some files but i just can't be bothered to remember that one#asahi-dev · 2026-06-04 14:48
sven#define dev_dbg dev_err at the very top should definitely work#asahi-dev · 2026-06-04 09:23
sveni don't have high hopes but it's worth a try#asahi-dev · 2026-06-04 09:23
svenyeah#asahi-dev · 2026-06-04 09:23
svencould try to file a radar about that as well if it's confirmed and see what happens :D#asahi-dev · 2026-06-04 09:11
svenand their internal process for un-restricting sysregs in iboot is apparently especially annoying #asahi-dev · 2026-06-04 09:11
svenunfortunately we are their QA and have to wait months until the bugs are fixed then :(#asahi-dev · 2026-06-04 09:10
svenStanfordAppliedCyber[m]: yeah, i know. i got it from people at apple as well#asahi-dev · 2026-06-04 09:06
svenand likely missed quite a bunch of stuff#asahi-dev · 2026-06-04 09:05
svenSobek[m]: don't assume any intention for raw boot mode, it's just very untested and they probably started with "everything disabled" and just put in a few exceptions#asahi-dev · 2026-06-04 09:05
sventhat one: #define SYS_IMP_APL_VM_TMR_FIQ_ENA_EL2 sys_reg(3, 5, 15, 1, 3)#asahi-dev · 2026-06-04 09:05
svenSYS_IMP_APL_VM_TMR_FIQ_ENA_EL2#asahi-dev · 2026-06-04 09:04
svenit's just that fiq virt mask thingy used in the aic driver