<marcan>
sven: the interesting thing is that since iBoot shuts down ANS2 (entirely it seems, it powers it down), the .data thing can't be a problem
<marcan>
so surely there is *some* way to reset these things?
<sven>
iboot does this 0xb…10 followed by 0x6…1 dance
<sven>
it didnt work previously for me because I thought it also send 0xb…1
the_lanetly_052__ has joined #asahi-dev
<sven>
So dunno. I’d expect some way to reset them as well but I’m out of ideas at this point
<marcan>
the other bits in the cpu control reg do nothing?
<sven>
no
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
<marcan>
sven: heh, I've been testing stuff and sometimes it gets into a state where after a successful boot, it will send the first message with the versions, then get stuck
<marcan>
seems to be kind of random
<marcan>
I mean after a subsequent reset
<sven>
huh
Dcow_ has quit [Read error: Connection reset by peer]
Dcow has joined #asahi-dev
riker77 has quit [Quit: Quitting IRC - gone for good...]
the_lanetly_052__ has joined #asahi-dev
<sven>
maybe it’s time to reverse that power thread in the rtkit firmware and see what exactly happens when 0x6 and 0xb is sent.
gwyef has joined #asahi-dev
gwyef has quit [Remote host closed the connection]
riker77 has joined #asahi-dev
the_lanetly_052___ has joined #asahi-dev
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has joined #asahi-dev
the_lanetly_052___ has quit [Ping timeout: 480 seconds]
sikkiladho[m] has joined #asahi-dev
Gaspare has joined #asahi-dev
steve has joined #asahi-dev
steve is now known as Guest7639
the_lanetly_052 has joined #asahi-dev
the_lanetly_052__ has quit [Ping timeout: 480 seconds]