ChanServ changed the topic of #asahi-re to: Asahi Linux: porting Linux to Apple Silicon macs | Hardware / boot process / firmware interface reverse engineering | WARNING: this channel (only) may contain binary reverse engineering discussion | RE policy: https://alx.sh/re (MANDATORY READ) | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-re
Emantor_ has quit []
Emantor has joined #asahi-re
phiologe has joined #asahi-re
PhilippvK has quit [Ping timeout: 480 seconds]
robinp__ has quit [Read error: Connection reset by peer]
robinp has joined #asahi-re
<sven>
so it looks like the IOVA range 0...4208000 (phys addr 9e62f0000...9e62ec000) pre-mapped in the dcp DART is part of the DCP firmware data section
sirn has joined #asahi-re
<alyssa>
lovely
<alyssa>
sven: Are you saying this for driver purposes or exploitation purposes? :-p
<sven>
uh... i think my lawyer would suggest to say it's for driver purposes only!
<sven>
seriously though, i just wanted to understand what exactly is mapped there
yuyichao has joined #asahi-re
zopieux has quit [Ping timeout: 480 seconds]
zopieux has joined #asahi-re
<alyssa>
:)
<marcan>
sven: is it an interesting part of the data section? :)
<marcan>
hopefully read-only? if you can map its own locked-down area with its own DART and have it write there, that's... kind of a big hole in the entire carveout system
<sven>
i can write to it
<sven>
and that section seems to contain functions pointers i think