#asahi-dev · 2026-05-05 06:29
svenprobably some wrong sequence in atcphy#asahi-dev · 2026-05-05 06:29
svenhttps://github.com/AsahiLinux/linux/commits/sven/tbt-wip/ that's 95% of tbt bringup, there's "just" some bug in there that prevents the NHI to see the connection#asahi-dev · 2026-05-04 11:47
svenyes#asahi-dev · 2026-05-04 07:05
sventhe reboot is weird though #asahi-dev · 2026-05-04 07:05
sven*sound#asahi-dev · 2026-05-04 07:05
svenserror does sounds like the block isn’t powered on #asahi-dev · 2026-05-03 21:11
svenand maybe even patches for tipd, don't remember#asahi-dev · 2026-05-03 21:10
svenyeah, there's some initial spmi driver somewhere#asahi-dev · 2026-05-03 17:18
svenand maybe we need to specifically handle that#asahi-dev · 2026-05-03 17:17
svenoh... endpoint 0 probably has a max packet size of 64 bytes though#asahi-dev · 2026-05-03 17:16
sven*thought#asahi-dev · 2026-05-03 17:16
sven(i.e. request 64 bytes, notice it's longer, request >64 bytes again and we don't handle that correctly)#asahi-dev · 2026-05-03 17:16
svenmight just be the host stack doing something unexpected like only requesting 64 bytes because i through that those descriptors could be longer#asahi-dev · 2026-05-03 17:08
svenor maybe it has to be split into two requests and our dwc3 code just doesn't do that correctly? :D#asahi-dev · 2026-05-03 17:07
svenmaybe there's some limit in either the usb spec or in the usb host stack? but that's weird..#asahi-dev · 2026-05-03 17:07
svenhuh#asahi-dev · 2026-05-03 09:44
svenBut using another macOS with 26+ works #asahi-dev · 2026-05-03 09:44
svenI’ve been too busy with $work :(#asahi-dev · 2026-05-03 08:34
svenread it again then#asahi-dev · 2026-05-03 08:34
svenwhy not?#asahi-dev · 2026-05-03 08:33
svenbut it's not fully understood yet#asahi-dev · 2026-05-03 08:33
sveni think there was some initial work#asahi-dev · 2026-05-03 08:33
svensame for macbook neo, that also needs the new pmgr#asahi-dev · 2026-05-03 08:32
svenbut the next step is essentially pmgr since most HW is still turned off at this point#asahi-dev · 2026-05-03 08:32
svensure#asahi-dev · 2026-05-03 08:31
svenand yeah, pmgr is the most important step for m4 bringup#asahi-dev · 2026-05-03 08:31
sventhere's some issues with sleep/wfi maybe and you need to carry a temporary patch in aic until that one sysreg becomes rw again#asahi-dev · 2026-05-03 08:30
sven~everything#asahi-dev · 2026-05-03 08:30
svenbut good enough to do bringup#asahi-dev · 2026-05-03 08:29
svenand it's still somewhat broken in 26 :D#asahi-dev · 2026-05-03 08:29
svenyeah, the raw boot mode was broken until 26#asahi-dev · 2026-05-03 07:37
svenWill take a look later #asahi-dev · 2026-05-03 07:37
svenah nice #asahi-dev · 2026-05-02 15:40
svendevice mode used to work on m1 without the port controller#asahi-dev · 2026-05-02 09:57
svenfine with me#asahi-dev · 2026-05-01 09:46
svenlike that "fabric firewall" thunderbolt crap which in reality is just them getting the power on sequence wrong or someone else who was fully convinced by claude that the 180s timeout was something with exclaves and needing to talk to them from m1n1 when in reality they don't exist on m4 and certainly aren't running in the non-entitled boot mode#asahi-dev · 2026-05-01 09:44
svenyeah, the biggest issues usually happen when people outsource all the actual hard work to some LLM without any understanding and then come to us with pages long issues or summaries that are just all wrong#asahi-dev · 2026-04-30 15:00
sveniirc you have like 30 days after purchase#asahi-dev · 2026-04-30 14:59
sventhat's not gonna work retroactively for obvious reasons#asahi-dev · 2026-04-25 12:42
svenfrom bputil, that needs to be set and then every bootarg should be allowed#asahi-dev · 2026-04-25 12:41
sven-a, --disable-boot-args-restriction#asahi-dev · 2026-04-25 12:40
svenyou need a way to confirm whatever bootarg you set was actually not filtered fwiw#asahi-dev · 2026-04-25 12:16
svenbut still, setting bootargs from 1TR should work unless they disabled that as well#asahi-dev · 2026-04-25 12:15
svenoh wait... on m4 you obviously can't chainload xnu#asahi-dev · 2026-04-25 12:14
svenbut iirc if you downgrade security and pass some extra flag you can set whatever bootargs you want from 1TR anyway#asahi-dev · 2026-04-25 12:14
sveni think there's some way to disable bootarg filtering, but otherwise just chainload xnu from m1n1 with the args (or even patches) you want#asahi-dev · 2026-04-25 12:03
sveni'm also still convinced that m4 and a18 can be brought up without hv tracing but with educated guessing and enabling xnu debug output (with the exception of complex coprocs like dcp or gpu)#asahi-dev · 2026-04-25 12:01
svenmaybe that's what i remember then#asahi-dev · 2026-04-25 12:00
svenweren't the hv crashes fixed at some point?