#
✕ nick:sven
#asahi-dev · 2026-04-16 14:34
svenbut if you could overwrite the reconfig sequence and then trigger a sleep->wake you could skip CTRR, etc. and just have it directly jump to your own code
#asahi-dev · 2026-04-16 14:34
svenwell, maybe not huge given the entire defense in depth they have
#asahi-dev · 2026-04-16 14:33
sven*issue
#asahi-dev · 2026-04-16 14:33
svenyeah, iboot setups up the reconfig engine and locks it because that would be a huge security issues otherwise
#asahi-dev · 2026-04-15 08:13
svenmuch of the s3_0_c11_c smells like CTRR stuff to me
#asahi-dev · 2026-04-15 07:44
svenbut maybe it just moved to a different place for the secondaries
#asahi-dev · 2026-04-15 07:44
sveni dont think i saw any chicken setup in either SPTM or XNU for m4
#asahi-dev · 2026-04-15 07:16
svensure, I’m curious about the differences
#asahi-dev · 2026-04-14 21:01
svenyeah, this sounds like it’s configurable
#asahi-dev · 2026-04-14 20:46
svenand, uh, isn't the kernel running in EL2? how would that trap hack even work there?
#asahi-dev · 2026-04-14 20:41
svenhave you found all wfi calls yet? i don't think there are that many. iirc there's also some framework for boot-time patching alternative instructions to work around errata already
#asahi-dev · 2026-04-14 20:29
sventhat doesn't sound like a proper solution at all
#asahi-dev · 2026-04-14 19:16
svenbut against our policy, so please stop this crap
#asahi-dev · 2026-04-14 17:57
svenalso, why would uart be powered down by a wfi sequence? that just makes no sense
#asahi-dev · 2026-04-14 17:47
svenwrites to powered down devices (what you call clock-gated) cause an SError and don't hang indefinitely
#asahi-dev · 2026-04-14 14:40
svenboot cpu vs. secondaries also shouldn't make a difference, so diffing sysregs like chaos_princess suggested is also a good idea
#asahi-dev · 2026-04-14 14:39
svenoh yes, absolutely
#asahi-dev · 2026-04-14 14:39
svenotherwise i guess we'll have to add a quirk and patch out all wfis very early in the boot sequence :/
#asahi-dev · 2026-04-14 14:38
svenso if it does that on m4 i'll file a cheeky radar and see what happens :D
#asahi-dev · 2026-04-14 14:38
svenyeah, that's my reading as well
#asahi-dev · 2026-04-14 14:38
sven*lose
#asahi-dev · 2026-04-14 14:38
sven"If the system is configured such that the WFI or WFIT instruction can be completed, then the architecture requires that the architectural state is not lost." so that very much sounds to me like wfi isn't allowed to use state if the expectation is that execution will resume afterwards at next next instruction
#asahi-dev · 2026-04-14 14:36
sven\o/
#asahi-dev · 2026-04-14 14:35
sventhat doesn't quite sound like normal wfi to me
#asahi-dev · 2026-04-14 14:35
svenhave been saved by software as part of the powerdown sequence before the WFI." that's the full quote
#asahi-dev · 2026-04-14 14:35
sven"In some implementations, based on the configuration of system specific registers, WFI can be used as part of a powerdown sequence where no interrupts will cause WFI wakeup events, and restoration of power involves resetting of the PE. In those cases, the WFI is permitted to cause a loss of architectural state, as it is assumed that this state will
#asahi-dev · 2026-04-14 14:35
svenhmmm true
#asahi-dev · 2026-04-14 14:35
svenalso surprised how fast you found that! i was looking as well
#asahi-dev · 2026-04-14 14:34
svenoh well
#asahi-dev · 2026-04-14 14:34
sven" In those cases, the WFI is permitted to cause a loss of architectural state" :(
#asahi-dev · 2026-04-14 14:30
sveni mean something along the lines of "so you took away our toys (SPRR/GXF) to make this thing look like an architectural ARM machine, how about you also make wfi work correctly?" ;)
#asahi-dev · 2026-04-14 14:28
sven*allowed
#asahi-dev · 2026-04-14 14:28
svenis wfi allows to lose state according to the ARM ARM? if that's not allowed and we can confirm it does on m4 i'm gonna file a cheeky feedback assistant report / radar :D
#asahi-dev · 2026-04-13 19:42
svenack, will prepare and send it tomorrow
#asahi-dev · 2026-04-13 19:39
svenarnd: 20260411-mailmap-v1-0-5a519f7b00b5@chaosmail.tech (https://lore.kernel.org/asahi/20260411-mailmap-v1-0-5a519f7b00b5@chaosmail.tech/) updates email addresses but the merge window is already open. can i still pick that up and send a PR to soc@ or should we just wait until -rc1 and send it as fixes then?
#asahi-dev · 2026-03-17 08:16
sveniirc pmgr somehow changed but someone did some re work, should be in the Asahi-re logs
#asahi-dev · 2026-03-17 08:15
svensounds like a plan :)
#asahi-dev · 2026-03-17 08:14
svennice!
#asahi-dev · 2026-03-16 08:44
svennice! 🎉
#asahi-dev · 2026-03-15 12:39
svenkaazoo: probably outdated m1n1
#asahi-dev · 2026-03-15 12:39
svenjannau: yeah, i was just thinking that both should probably use the same dt binding and interface to dockchannel
#asahi-dev · 2026-03-15 12:29
sventhough I guess it needs coordination with that mtp dockchannel thing
#asahi-dev · 2026-03-15 12:29
svenand yeah, could be a good yak to shave
#asahi-dev · 2026-03-15 12:29
svenNot yet
#asahi-dev · 2026-03-15 12:14
svenalso really needs to finish that asahi-kisd thing so that we can use this from linux as well
#asahi-dev · 2026-03-15 12:14
svennice!
#asahi-dev · 2026-03-14 18:59
sven😱😱
#asahi-dev · 2026-03-14 18:58
sven:<
#asahi-dev · 2026-03-14 18:58
sven(where we means "someone who isn't sven")
#asahi-dev · 2026-03-14 18:57
svenand at least in theory we could always implement usb3 device mode

plus ›