ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
<marcan>
jannau: ha (but also ew, means we need to map it at a fixed address on reload?)
drubrkletern has quit [Remote host closed the connection]
greguu has quit [Quit: WeeChat 3.0]
tobhe_ has joined #asahi-dev
tobhe has quit [Ping timeout: 480 seconds]
timokrgr has joined #asahi-dev
drubrkletern has joined #asahi-dev
mini0n has quit []
<jannau>
marcan: there's a misunderstanding. DCP updates its shared mem pointer on second SetShmem message. it just doesn't acknowledge the message like it does on the initial SetShmem message
drubrkletern has quit [Quit: Leaving]
<jannau>
so it is mostly an annoyance since we have to assume it's safe to start sending messages using shmem after the SetShmem message and we have to start it on our own instead of after receiving the initialized mbox message
hightower2 has quit [Remote host closed the connection]
minecrell has quit [Quit: Ping timeout (120 seconds)]
hightower2 has quit [Remote host closed the connection]
minecrell has quit [Quit: Ping timeout (120 seconds)]
hightower2 has joined #asahi-dev
minecrell has joined #asahi-dev
SSJ_GZ has joined #asahi-dev
bps2 has joined #asahi-dev
kujeger has quit [Remote host closed the connection]
chadmed_ has joined #asahi-dev
chadmed_ has quit [Remote host closed the connection]
chadmed_ has joined #asahi-dev
<cyrozap>
Quick question about the IOMMU behavior under macOS--will macOS log IOMMU faults somewhere? Like, if I have a PCIe device plugged in over Thunderbolt, and the PCIe device tries accessing memory it doesn't have permission to access, will that be logged somewhere I can see it?
<sven>
at least for the non-thunderbolt iommus macOS kernel panics on any fault
<sven>
wouldn’t surprise me if it does the same for the thunderbolt iommus as well
<dottedmag>
Sounds like a way to make a simple "killmac" device
chadmed_ has quit [Remote host closed the connection]
<maz>
dottedmag: there are simpler ways to do this rather than dealing with PCIe TLPs to force a fault. USB-C VDMs, for example.
chadmed_ has joined #asahi-dev
regalramp has joined #asahi-dev
kujeger has joined #asahi-dev
chadmed_ has quit [Remote host closed the connection]
j`ey has quit [Remote host closed the connection]
j`ey has joined #asahi-dev
chadmed_ has joined #asahi-dev
Cyrinux has quit []
Cyrinux has joined #asahi-dev
Cyrinux has quit []
Cyrinux has joined #asahi-dev
flying_sausages has joined #asahi-dev
chadmed_ has quit [Remote host closed the connection]
chadmed_ has joined #asahi-dev
cylm_ has joined #asahi-dev
<kettenis>
just pull out the power cord?
<maz>
too easy?
<kettenis>
admittedly not instant on a laptop with a full battery...
<_jannau_>
press the power butten for ~10 seconds
as400 has quit [Remote host closed the connection]
as400 has joined #asahi-dev
chadmed_ has quit [Remote host closed the connection]
hertz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
MajorBiscuit has joined #asahi-dev
flying_sausages has joined #asahi-dev
Cyrinux has quit [Remote host closed the connection]
hightower2 has quit [Ping timeout: 480 seconds]
Cyrinux has joined #asahi-dev
<marcan>
jannau: stupid idea, does setting it to 0 make it acknowledge it again next time?
<marcan>
chadmed_: nice!
<sven>
hah, I think I can access some of the thunderbolt pciec regs. I guess the rest just needs some additional init on the pciec side before they stop reading as 0xffffffff
<_jannau_>
marcan: unfortunately not. That's how I discovered that it reports the current dva. it crashes immediately with .dva = 0 and .flag = 4. if .flag is not set to 4 it just reports the current dva with 0x...0140
MajorBiscuit has quit [Quit: WeeChat 3.6]
<_jannau_>
not sure what the additional set bit signifies
<_jannau_>
marcan: iomfb has A400/A402 free_signal/stop_signal which sound promising but I couldn't figure out what I have to do to prevent dcp from crashing when I use them. stop_signal issues a few callbacks before it crashes. free_signal crashes immediately
hightower2 has joined #asahi-dev
hampus has joined #asahi-dev
<marcan>
_jannau_: try sending it msg type 1 (the initcomplete msg)
bcrumb has joined #asahi-dev
bcrumb has quit []
r0ni has joined #asahi-dev
kaal has joined #asahi-dev
kaal has quit [Quit: Konversation terminated!]
bcrumb has joined #asahi-dev
<marcan>
_jannau_: I think that "ack" is more like a state report, and it only gets sent on first init (but you can request another one)
bcrumb has quit [Quit: WeeChat 3.7.1]
roxfan2 has joined #asahi-dev
<_jannau_>
not sure if that buys me much. I still need to determine when to request that
jluthra has quit [Remote host closed the connection]