#
#asahi-dev · 2026-08-14 15:22
yukathe cache_enable part seems quite easy to figure out given a trace, but the tz start/end/enable not so much. I don't understand this part: "by looking at region-id-2 and region-id-4 on a booted macos, in the /chosen/carveout-memory-map DT node"
#asahi-dev · 2026-08-14 15:20
JPeisachok yep not me
#asahi-dev · 2026-08-14 15:20
svenalso needs a thunderbolt device or another machine with tbt support and a tbt cable
#asahi-dev · 2026-08-14 15:19
sveni'm sure chaos or j_anne will get to it
#asahi-dev · 2026-08-14 15:19
JPeisachI could, do I need to install m1n1 on macOS though
#asahi-dev · 2026-08-14 15:04
svenshould give a line like this for ever plug: VSE WRITE [0x36] = 0x00000407 | hpm1: STATUS=fd820210 DATA_STATUS=03000304 USB4_STATUS=? INTEL_VID_STATUS=030000000002010100 DP_SID_STATUS=? CF_VID_STATUS=?
#asahi-dev · 2026-08-14 15:04
svencan someone try that with a pro/max machine?
#asahi-dev · 2026-08-14 15:03
svenhttps://f.svpe.de/1e082eb1b38c8d840f4f1daf53f88ca5ecf68fb350381d9fe37f9fc5c1d85e99_trace_tbt_cable.py.txt okay, that should give us the cd3217 regs mac os read + what it wrote to that cable VSE, only tested on t8103
#asahi-dev · 2026-08-14 13:52
yukaand you derive it from a trace by recognizing the same patterns that were written on m1?
#asahi-dev · 2026-08-14 13:52
jannauit's not used. I supposed it's derived for newer gens becasue it was in the adt for m1
#asahi-dev · 2026-08-14 13:51
yukaand can't find any docs on the mcc
#asahi-dev · 2026-08-14 13:51
yukaWhat is the dcs_* for in mcc.c? I don't see it being used anywhere
#asahi-dev · 2026-08-14 13:17
svenmaybe it's time to write a tracer for tipd + the VSE write and just collect a bunch of data
#asahi-dev · 2026-08-14 13:17
svenffs.. the cable vse thing is still somehow wrong it seems *sigh*
#asahi-dev · 2026-08-14 12:14
chadmedare swaps even slower with interchange? theres no way....
#asahi-dev · 2026-08-14 12:14
chadmedwhat are we even getting wedged on here
#asahi-dev · 2026-08-14 12:14
chadmedapple-dcp 231c00000.dcp: RTKit: Message (id=1): pcc firmware: mprintf_pcc2d_ltm.c:370 isr_inbox0_not_empty() --
#asahi-dev · 2026-08-14 12:01
svenack
#asahi-dev · 2026-08-14 12:01
jannauI'll trace t8103 linux to linux later and add it to the gist
#asahi-dev · 2026-08-14 12:01
sveni wanted a 20gbps vs. a 40 gbps from the linux side :D
#asahi-dev · 2026-08-14 12:01
jannauso the 40gbps connection
#asahi-dev · 2026-08-14 12:01
svenoh lol, that explains it :D
#asahi-dev · 2026-08-14 12:00
jannausven: I guess I misunderstood what you wanted to have traced. I traced both sides of a linux/macos connection
#asahi-dev · 2026-08-14 11:59
svengonna take a closer look this evening
#asahi-dev · 2026-08-14 11:58
svenjannau: and we're back to "those traces look very similar" :(
#asahi-dev · 2026-08-14 10:41
chadmednothing else will make it crash
#asahi-dev · 2026-08-14 10:41
chadmedon t8112 i can get it to reliably crash when glmark2-wayland is on surface 1 and kwin clears the cursor surface
#asahi-dev · 2026-08-14 10:40
chadmedthis may still be something to do with mesa. the frequency of crashes can be influenced by when we allow interchange in agx_pipe
#asahi-dev · 2026-08-14 10:15
chadmedwas anyone able to test the interchange stuff with mutter? im still getting occasional dcp crashes with certain things when all three surfaces are in use (they do not happen when interchange is disabled)
#asahi-dev · 2026-08-14 10:00
jannausven: traces https://gist.github.com/jannau/f61db27f1ab831d8b4db7d77821eeceb
#asahi-dev · 2026-08-14 09:38
svenso it should've been linux initiating the thing but i also saw macos trying to start that state machine
#asahi-dev · 2026-08-14 09:38
svenand macos had the correct uuid
#asahi-dev · 2026-08-14 09:38
svenjannau: no, with macos/linux that happened
#asahi-dev · 2026-08-14 09:38
jannausven: aren't the uuids on both sides identical so both are lower (and not)
#asahi-dev · 2026-08-14 09:37
chaos_princessok
#asahi-dev · 2026-08-14 09:37
jannauchaos_princess: "USB4 cable: eudo 0x2667e000, orientation 2 -> cable info 0x7"
#asahi-dev · 2026-08-14 09:36
sventhe weird thing i saw in chaos's trace is that linux uses "lower uuid initiates lane bonding" but both sides tried to do that which is weird
#asahi-dev · 2026-08-14 09:35
svenhttps://f.svenpeter.dev/f9237287e3af548f79fb0d8ceaa85c49b7f8f6ed27a36d07d15d6f86d1292b21_trace_acio.py.txt
#asahi-dev · 2026-08-14 09:35
svencan you trace both with trace_acio.py?
#asahi-dev · 2026-08-14 09:35
svenhuh, interesting
#asahi-dev · 2026-08-14 09:34
jannauwith macos as partner lane bonding works: "Speed (Rx/Tx): 40/40 Gb/s"
#asahi-dev · 2026-08-14 09:34
sveni'd like to get the uid correct though
#asahi-dev · 2026-08-14 09:34
sventhough even single lane would be fine for v1 imho
#asahi-dev · 2026-08-14 09:34
chaos_princessjannau: what is eudo on that cable
#asahi-dev · 2026-08-14 09:33
svengotta figure out why it doesn't want to bond lanes then
#asahi-dev · 2026-08-14 09:32
sventhen chaos' ~20 Gb/s is quite amazing
#asahi-dev · 2026-08-14 09:31
jannau`tblist -vA` reports "Speed (Rx/Tx): 20/20 Gb/s" so I guess not
#asahi-dev · 2026-08-14 09:28
jannauunclear
#asahi-dev · 2026-08-14 09:19
svendoes it show if lane bonding works? that's still unclear
#asahi-dev · 2026-08-14 09:18
svennope, didn't know about that. looks useful

plus ›