OK confirmed... Core 1 is sitting exactly in the wait handler I expected it to be.
Core 0 is in another function that I've started reversing and is just in a while(1){wfi} loop.
So I'm not sure how I'm supposed to break out of that part. It would be hilarious if I just gave up and booted only core 1 because I couldn't get core 0 to do what I wanted.
To Mozillas new handlers: Good fucking luck trying to turn a browser with the *GECKO ENGINE* as its base into an agentic AI browser, we have problems with getting 10 year old CSS standards on boarded, you think we can handle an AI that can browse the internet??????
#Sigh - The abject terror the #OrangeToddler and his handlers (manipulators?) have of losing their "special" position as #ubermensch is
#Sigh - The abject terror the #OrangeToddler and his handlers (manipulators?) have of losing their "special" position as #ubermensch is