00:02 <chadmed> phire: i had a go at dumping AGXG13X in ghidra a few days ago. its full of hard offsets and random jumps to data and generally quite well obfuscated from what i could tell. youll also need to pull in and poke around in a whole bunch of IOKit kexts that it seems to depend on

00:03 <phire> part of the reason I'm really not wanting to go down that route

00:03 <phire> that, and I shouldn't need to

00:05 <phire> I think my next step is to list out every IO range that gets mapped into the UAT iommu, and see if the CPU is writing to any of them

00:58 <alyssa> marcan: ^^

00:59 <alyssa> can it be worse than the DCP firmware? ;)

01:03 <phire> I've seen no reason to suspect that (yet). Other than the fact I can't find out how it's communicating

01:49 <marcan> chadmed: kexts aren't obfuscated, they're just like that the way iokit works

01:50 <marcan> also reminder that looking at kext code disqualifies you from working on the linux driver / etc unless I personally know I can trust your reversing hygiene

01:50 <marcan> see the policy

01:51 <marcan> this is *especially* true for big unknown subsystems like graphics

02:38 <chadmed> im not fit to write a driver that blinks an LED let alone one to submit work to a GPU so you dont need to worry about me pinching code from apple or anyone else. this is a relatively new interest for me and ive no professional compsci or software design background so its mostly just out of curiosity for the workflow that i did it.