#
…

2026-08-11

00:06jsk has quit [Read error: No route to host]
00:06jsk has joined #asahi-dev
00:18Rafay has quit [Remote host closed the connection]
01:19jsk_ has joined #asahi-dev
01:24jsk has quit [Ping timeout: 480 seconds]
01:28jsk_ is now known as jsk
01:40catred has quit [Remote host closed the connection]
01:45pb17 has quit [Ping timeout: 480 seconds]
01:50pb17 has joined #asahi-dev
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
03:43pthariensflame has joined #asahi-dev
03:54pthariensflame has quit [Remote host closed the connection]
03:57nora has joined #asahi-dev
03:59nora_ has quit [Ping timeout: 480 seconds]
04:29eluks has quit [Remote host closed the connection]
04:30eluks has joined #asahi-dev
05:03WindowPain9 has joined #asahi-dev
05:07WindowPain has quit [Ping timeout: 480 seconds]
05:11WindowPain9 has quit [Ping timeout: 480 seconds]
05:27pb17 has quit [Ping timeout: 480 seconds]
05:33pb17 has joined #asahi-dev
06:18svencan you show me dmesg output?
06:47svenchaos_princess: can you try modprobe thunderbolt_net e2e=0 ?
06:48sveneverything looks identical and i'm really running out of ideas :(
07:00hdbngr has joined #asahi-dev
07:08hdbngr has quit [Ping timeout: 480 seconds]
07:27chadmedis there a better way to test local mesa builds than meson devenv? it's kinda flakey inside muvm
07:27chadmed(other than the nuclear option of smushing the system version of course)
07:43Pokemod9773620847128183300 has quit [Ping timeout: 480 seconds]
07:59mixiyou should be able to set a --prefix in your home with meson, install mesa there, and then manually use a LD_LIBRARY_PATH pointing to that prefix
08:01hdbngr has joined #asahi-dev
08:03mixiyou might also need to set VK_DRIVER_FILES to your prefix vulkan icd location
08:06sven~ # ping -c20 fe80::ce7:432b:f03f:970
08:06svenPING fe80::ce7:432b:f03f:970 (fe80::ce7:432b:f03f:970): 56 data bytes
08:06sven64 bytes from fe80::ce7:432b:f03f:970: seq=1 ttl=64 time=0.503 ms
08:06sven64 bytes from fe80::ce7:432b:f03f:970: seq=0 ttl=64 time=0.430 ms
08:06svenso i think that's over usb4net now
08:06sventurns out i can test it from busybox :D
08:07sventhe e2e stuff is just broken for some reason i think
08:07svenstill need to figure out why
08:09hdbngr has quit [Ping timeout: 480 seconds]
08:10nickchannvme fix is first try 🎉
08:11svenoh, it was merged? nice
08:16BrandiWhite[m] has joined #asahi-dev
08:26picnoir has quit [Quit: WeeChat 4.10.0]
08:27picnoir has joined #asahi-dev
08:39xal has quit []
08:41hdbngr has joined #asahi-dev
08:41xal has joined #asahi-dev
08:43chaos_princesssven: are both ends of your connection on linux
08:43svenno, one is macos, the other linux
08:43chaos_princessno worky here
08:43sveneven with e2e=0? :/
08:43chaos_princessalso checked via `cat /sys/module/thunderbolt_net/parameters/e2e`
08:44chaos_princesswhich side is the ping "source"
08:44svenand it doesn't have wifi or ethernet so it shouldn't be able to use anything else
08:44chaos_princessare both devices on ethernet
08:44sventhe linux side is a busybox shell
08:44sventhere's not even dhcp :D
08:45sventhat's also the reason i use the link local ipv6 addr
08:46svenlinux does two writes to the ring options, first one setting the enable bit and the second one then setting the e2e bit. let me merge that and see if that also works here
08:46sventhen i can push my exact tree
08:55BrandiWhite[m]Get in touch with this platform for greatness you’ll definitely thank me later
ℹ️❤️
👇🏻👇🏻👇🏻
08:55BrandiWhite[m]Get in touch with this platform for greatness you’ll definitely thank me later
ℹ️❤️
👇🏻👇🏻👇🏻
08:55BrandiWhite[m] has left #asahi-dev [Kicked by @svenpeter:matrix.org : spam]
09:00sventhat's on top of the tbt-reset-wip branch (with some churn from yesterday)
09:01chaos_princessok, will test in a bit, i will probably need to re-merge it on top of asahi-wip
09:03svenok, pushed it as a WIP commit to github as well
09:04svenif that still doesn't work please trace it again
09:07hdbngr has quit [Ping timeout: 480 seconds]
09:17svenalso pushed the dts changes for that single m2 port if anyone with base m2 wants to test
09:25chaos_princessstill does not work
09:28svenweird, can you trace it again?
09:29sventhe other machine isn't connected to ethernet or wifi
09:29svenand this one is connected to ethernet but as no ip, etc.
09:36sri has joined #asahi-dev
09:36Rafay has joined #asahi-dev
09:38svenmacos -> linux ping seems to work too for me now
09:41Rafaysven: These are the logs, just tbt-reset-wip at commit 98588460927272c731c6018af25463986fdf9e0e and the patch you gave me. I didn't add the later patch you sent here and I tried with e2e=0 with no luck. https://pastebin.com/JxrwH0wK
09:42hdbngr has joined #asahi-dev
09:43svenso that seems to never establish the host2host connection i think
09:46svencan you trace the acio nodes on both macos and linux?
09:47RafayLemme do that.
09:51hdbngr has quit [Ping timeout: 480 seconds]
09:55ansg191 has quit [Remote host closed the connection]
09:55svenchaos_princess: last difference i see, but that's related to interrupts and i'd be surprised if this makes a difference: https://f.svpe.de/52ff3d5be413a43da7d17b374a2f6cd5625844b8ce6f276043395437a034db77_hack.patch
10:04ansg191 has joined #asahi-dev
10:06svenso it's either that macos/linux works for some reason and linux/linux doesn't or the non-base M1 machines do something very weird that i don't see in the mmio traces
10:07jannauI can test M1 <-> M1 later
10:07sventhat would be great!
10:08svenif M1/M1 works the initial series will be M1 only and the pro/max/etc. variants are going to be someone else's problem. ideally someone who actually has that hardware :D
10:08chaos_princessdoes that look suspicious?
10:16svenit doesn't look good i think
10:16svenwhich machine is this again? t6001?
10:21yuka has quit [Remote host closed the connection]
10:21svenchaos_princess: can you read32 0x701fd0000 and 0x701f1401c after you started the ping from the hv?
10:30yuka has joined #asahi-dev
10:32yukawhat is the plan for M3* nvme (new compatibles and device tree nodes) upstreaming?
10:34yukait seems pretty trivial now with the 15.x fw figured out
10:35yukajannau: do you want to send that out eventually?
10:35chaos_princesssven: both zero
10:35chaos_princessyuka: just send it, m3 does not need 15
10:36mazyuka: are you planning to resend your PCIe power control patch?
10:36svenchaos_princess: okay, so that means ring 1 is being ignored completely i have no idea why
10:37chaos_princesswe haven't tried the stream 15 nonsense again, right?
10:37svendon't think so
10:37svenmight be worth a try at this point
10:38jannauI plan to send more M3 hw enabled patches once 7.3-rc1 is out. I haven't done anything yet with adding missing dt-binding patches and separating device tree modifications
10:38yukajannau: sounds good, then I'll wait for that
10:38WindowPain has joined #asahi-dev
10:39svenchaos_princess: also, which firmware is that? already the one where acio is a bit more talkative over its syslog?
10:40chaos_princessyes, whatever comes with latest 27 beta
10:40svenokay, same here
10:40svenpity.. i was hoping the 27+ might complain over syslog and tell me what i'm doing wrong
10:41jannaustill not sure how to send it. I guess for keeping every ones mailbox clear I should send a series for each hw with dt-binding change and dts changes. They probably need to depend on each other for the dts changes to apply
10:43chaos_princessanything suspicious there?
10:43jannaumaz: I need to check how the PCIe power control changes fir in with the mac pro PCIe support with the big PCIe switch in the middle
10:43svenchaos_princess: no, that looks just like mine does i think
10:43yukamaz: I prepared a new version of PCIe power control, but it's gotten very messy and I don't feel too good about sending it out like this. I can send it if you really want, but I don't expect it to go anywhere.
10:44mazjannau: ah, that one... :-/
10:44svenhuh, actually, i think mine looks different. not sure that's suspicious though
10:45mazyuka: no point in sending something you're not confident about. once you have something that is in a reviewable state, I'll have a look. in the meantime, I'll stop tracking this in my inbox.
10:46chaos_princessmine is from later, once it actually sees another host and starts to negotiate usb4net
10:46svenwait, i have to be confident about the patches i sent out? :P
10:46mazsven: moderately ;-)
10:46svenphew :)
10:46svenchaos_princess: ugh, wait, copy paste error. wanted to paste a bit more than that
10:47svenbut yeah.. the end actually looks similar
10:57svendunno... guess i either need to give up on non-M1 for now or write a tracer for the ring 0 traffic
10:58chaos_princesslet's see if m1 can talk to other m1 first
10:58hdbngr has joined #asahi-dev
10:59yukajannau: if you send the M3 nvme stuff through the soc tree, then I can only do M4 nvme in 7.4, or it will result in merge conflicts. any idea how to deal with this?
11:00svenmaybe it's time to write dt-bindings. or look at the horror that lurk inside pcie hotplug again
11:00sven*horrors
11:07hdbngr has quit [Ping timeout: 480 seconds]
11:10jannauyuka: you can either depend on change or trust that linux maintainers are able to resolve simple one-line conflicts in dt-binding changes
11:11svenit's kinda close to the 7.3 merge window anyway, not sure if anything will still be picked up
11:12jannauI wasn't planning to send anything before 7.3-rc1
11:13yukadepend on change means the nvme tree would pick up the M3 dt-bindings change too?
11:14yukathe main point being that my change has actual driver changes, so it with its accompanying dt-bindings change would go through the nvme tree
11:15yukasven: ah yes, then I'd have to wait until 7.5 to fully work around conflicts
11:19jannauif you add a new base compatible for M4 nvme I don't expect conflicts at all
11:20yukathere will be conflicts
11:20yukait changes the indentation of the if: block
11:21yukawhich you will add t603x to
11:21yukaor not?
11:21yukaI guess apple,t6020-nvme-ans2 and apple,t6000-nvme-ans2 are only explicitly listed because one of them is in the old base compatible
11:22yukayes, you'll need to add t603x to require 3 power-domains
11:31ieyasu_ has quit [Read error: Connection reset by peer]
11:32ieyasu has joined #asahi-dev
11:34hdbngr has joined #asahi-dev
11:46hdbngr has quit [Ping timeout: 480 seconds]
11:50yukaI'm not in a hurry, waiting for 7.5 is a fine workaround for me
11:59hdbngr has joined #asahi-dev
12:02yukaconfirmed linux-next + https://termbin.com/8dyl + "idle=nop arm64.nowfxt" can boot on M4 smp
12:02yukaI'll send that idreg-override.c thing out late
12:02yuka*later
12:07hdbngr has quit [Ping timeout: 480 seconds]
12:15hdbngr has joined #asahi-dev
12:16___nick___ has joined #asahi-dev
12:19mripard has quit [Remote host closed the connection]
12:22liv[m]i have an OWC Thunderbolt Pro Dock and HP Thunderbolt Dock G2, I think the HP does ethernet over USB but the OWC does it over something more complicated than that because of 10G capabilities, so would it be useful if I compiled a few patches and dropped a dmesg every once in a while?
12:23svenno, not yet
12:23svenright now the only thing that works ist host2host
12:23liv[m]ah alright :)
12:23liv[m]i have other tb hosts though... but they're x86_64 (thinkpad p14s g5)
12:23liv[m]* i have other tb hosts though... but they're x86\_64 (thinkpad p14s g5 running linux)
12:24sventhat's fine, that should work as well
12:24mripard has joined #asahi-dev
12:24svenwhich apple machine do you have?
12:24liv[m]m2 max 14
12:24liv[m]* m2 max 14"
12:24svenah, too early. i haven't worked out the dts changes for that one yet
12:26___nick___ has quit []
12:28___nick___ has joined #asahi-dev
12:29___nick___ has quit []
12:31___nick___ has joined #asahi-dev
12:32hdbngr has quit [Ping timeout: 480 seconds]
12:34hdbngr has joined #asahi-dev
12:36liv[m]i'm running nixos so i can easily - if i have kernel patches - rebuild and boot a new kernel once the time is there :)
12:37svensure, will let you know once i have the dts nodes for m2 pro/max ready
12:42hdbngr has quit [Ping timeout: 480 seconds]
12:48fl0_idoh caldigit makes a "cheap" tb hub now...
12:49jannauchadmed: has KDE stopped using overlays for the cursor?
12:49hdbngr has joined #asahi-dev
12:49LarstiQ has quit [Ping timeout: 480 seconds]
12:49chadmednope, working fine on 6.7.4 here
12:49chadmeddo you have KWIN_FORCE_SW_CURSOR=1 set somewhere
12:54jannauno KWIN environment set. testing your surface / plane PR (modified) but drm_info looks as expected
12:54jannautesting on 13-inch m2 macbook pro
12:55chadmedim using it right now on this machine
12:56chadmedplane 2 gets the cursor, plane 1 gets nothing without KWIN_USE_OVERLAYS, plane 0 gets the desktop
12:56chadmedactually try set KWIN_USE_OVERLAYS=1
12:57jannauonly plane 0 is used here
12:57sri has quit [Quit: Leaving]
13:00jannauyes, that did the trick
13:01jannaushall we create a PR to enable overlays in kwin for apple?
13:01chadmedhm yes since that is technically a regression
13:03mripard has quit [Remote host closed the connection]
13:04mripard has joined #asahi-dev
13:04chadmed8076 got merged so i think we should be okay from a kwin perspective to enable overlays unconditionally no
13:05chadmedi need to look at colour pipelines again soon, we do hit the colour bug mentioned in the comments on that MR under certain conditions
13:09hdbngr has quit [Ping timeout: 480 seconds]
13:11jannauwhy would we hit that bug without supported colour pipelines? It would be either a kwin bug/weirdness or some additional blending restrictions in DCP which we don't understand
13:12chadmednot sure, all ive noticed is that colours change slightly on some content between compositing and scanout
13:17chadmed has quit [Quit: Konversation terminated!]
13:17hdbngr has joined #asahi-dev
13:21chadmed has joined #asahi-dev
13:21svenoh ffs, there's some weird race condition that appears and claims that "port is locked" when i remove the debug prints in apple.c
13:21svenmaybe it's time for that tracer after all now *sigh*
13:26hdbngr has quit [Ping timeout: 480 seconds]
13:34hdbngr has joined #asahi-dev
13:34jannaurebase on v7.1.8 with some changes merged pushed to asahi-wip, not tagged
13:44bgb_ has joined #asahi-dev
13:44bgb has quit [Remote host closed the connection]
13:48hdbngr has quit [Ping timeout: 480 seconds]
13:55bgb_ has quit [Remote host closed the connection]
13:59bgb has joined #asahi-dev
14:14your_nick has joined #asahi-dev
14:16your_nick has quit [Remote host closed the connection]
14:16thequantumnargle has joined #asahi-dev
14:26Rakshit[m] has joined #asahi-dev
14:33bennofs30 has joined #asahi-dev
14:35bennofs3 has quit [Ping timeout: 480 seconds]
14:35bennofs30 is now known as bennofs3
14:37jannauI get "high_speed_lane.c:289: Gen2/3 link error. lane=[01], error=" spam. I guess I'll try different cables
14:37svenprobably wrong VSE cable thing then
14:38svenif you get me the EUDO or VDO from the dbg print and then what macos writes i can fix it
14:38jannauis it expected that the hypervisor doesn't disable its port
14:38svenmacos puts it into its uart output with the right flags
14:38jannaucable is a passive thunderbolt4 cable
14:39svendoes it go through the eudo or pd vdo path?
14:43sveni suspect half of the bit descriptions are wrong but the only way to fix them is to have enough (PDVDO or EUDO),(what macos writes) pairs
14:44jannaulink errors with a fully connected usb3.2 / DP cable
14:44svenyeah, that happens if the VSE cable info is wrong
14:46jannauthunderbolt 3 cable (according to vendor markings) somewhat works but I don't see any devices in boltctl list. dmesg: https://paste.debian.net/hidden/91917d40
14:49chaos_princesshost to host?
14:49svenis that the tbt-reset-wip branch? there should be a TBT cable: or "USB4 cable: message
14:50jannauthis is 05c751713a28 from tbt-reset-wip
14:52svenah, maybe that print is just outside of the stuff you pasted
14:52jannauthe messages are there: just not included in my partial dmesg
14:53hdbngr has joined #asahi-dev
14:53sveni think that's correct because it gets far enough, but can you check what macos would write? let me find the debug arguments you need to get the print
14:53jannauany non-obvious kconfig option to enable?
14:54svenit already gets far enough, it should find whatever is connected. is that a device or another host
14:54svendebug=0x14e serial=3 apcie=0xfffffffe wdt=-1 AppleSynopsysDRDUSBXHCI-debug=0xffff AppleT8103TypeCPhy-debug=0xffff AppleT8103USB40XHCITypeCPort-debug=0xffff AppleT8103USBXDCI-debug=0xffff AppleTypeCPhy-debug=0xffff AppleTypeCPhyCIOInterface-debug=0xffff AppleTypeCPhyDisplayPortInterface-debug=0xffffffff AppleTypeCPhyInterface-debug=0xffff
14:54svenAppleTypeCPhyUSBInterface-debug=0xffff AppleUSBHostResourcesTypeC-debug=0xffff
14:54sveni *think* that is enough
14:54svenbut let me double check
14:55jannauone of the devices froze
14:55svenuh.. that's not good
15:02jannauI think it's mostly my fault by trying to use the HV on 2 targets from the same system
15:04jannaugot further along this time but boltctl list is still empty. I see the othewr device announced in dmesg though
15:05svenis this host2host? not sure that will even show up in boltctl
15:05svendo you have USB4NET enabled?
15:05svenCONFIG_USB4_NET i think
15:06chadmed has quit [Quit: Konversation terminated!]
15:06sventhat looks good
15:06svendo you see a thunderbolt0 intefcace?
15:06sven*interface
15:07jannauyes, thunderbolt0 net interface is there. I was expecting to see something in boltctl for host2host
15:07chadmed has joined #asahi-dev
15:08svendunno if it'll show up there, i don't have that on my busybox shell :D
15:08svennow for the interesting part: does ping work?
15:08chadmed has quit [Read error: Connection reset by peer]
15:08chadmed has joined #asahi-dev
15:09chadmed has quit [Read error: Connection reset by peer]
15:09chadmed has joined #asahi-dev
15:09Moderation[m] has joined #asahi-dev
15:12chaos_princessit didn't for me either
15:13thequantumnargle has quit [Remote host closed the connection]
15:22jannauyes, ping works
15:23svenso then something breaks on the non-base M1 chips
15:24sventblog=0xffffffff tblogmode=3 tbdp=0xffffffff tbip=0xffffffff are the relevant bootargs I used to enable all verbose debug spam I think
15:24sventhat's at least in my bash_history
15:24sventhat should tell you what macos sets for VSE cable info for the cables that don't work
15:26sveni wonder if there's some way to get to that info from macos when not running under the hv
15:31hdbngr has quit [Ping timeout: 480 seconds]
15:33jannauiperf3 doesn't work (seem setwork related), flood ping reports 2gbps throughput
15:34sveni accidentally added a two or three level indirect pointer lookup plus jump to the hot path so it's not surprising we don't get the full speed, but 2gbps seems low
15:36sventhere's also that magic 0x186 write next to irq enable which might just be some tweaking to when that irq fires
15:37jannauerr, I typoed the size resulting in fragmentation. `ping -s 1472 -f IP` is now at ~28 gbps
15:37svennow that's much better :-)
15:43maztiny difference... :D
15:44jannauthis seems to be already faster than the benchmarks I found intel/amd usb4_net
15:45jannautime to debug why iperf3 doesn't work
15:45svenhah :D
15:50sven"In our tests, 13.6 Gbps is within a realistic range. Although this may seem below the raw capacity, real-world factors (including half-duplex operation) usually limit effective throughput." lol
15:57nickchanIs that statement slop or something
15:58jannauargh!, ping probably doesn not work. both devices have the same link local ipv4 address
15:58rany has quit [Remote host closed the connection]
16:00bgb has quit [Remote host closed the connection]
16:00bgb has joined #asahi-dev
16:01rany has joined #asahi-dev
16:01jannauthe ipv6 link local addresses work, iperf3 reports 7.15 Gbits/sec
16:05svenbut good to know this works on M1/M1
16:05sventhen there's just something wrong / new with the Pro/Max variants
16:06sveni'm writing a tracer for traffic on ring 0 anyway due track down that weird race where some ports are locked and then xdomain doesn't work at all if i remove enough debug prints in apple.c
16:06Rafaysven: Here's the trace under linux. https://gist.github.com/rafayahmed317/d7d8768cec63178c0c15a8983af7d553 . Just to remind you, on my setup, thunderbolt_net doesn't create a device and xdomain doesn't initialize. You already have the mac trace: https://gist.github.com/rafayahmed317/e083de8e478830dc37969ca0b36750e7
16:06svennice, thanks!
16:06sventhat's base M2, right?
16:07Rafayt8112-j473
16:14qyliss has quit [Quit: bye]
16:16rany has quit [Remote host closed the connection]
16:16qyliss has joined #asahi-dev
16:16Guest15226 has quit [Quit: Bridge terminating on SIGTERM]
16:16rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:17rany has joined #asahi-dev
16:21chaos_princessyuka: is m4 smp reliable w/ that, or still a dice roll?
16:22qyliss has quit [Quit: bye]
16:22qyliss has joined #asahi-dev
16:25WindowPain has quit [Ping timeout: 480 seconds]
16:28pb17 has quit [Ping timeout: 480 seconds]
16:32yukadice roll
16:37bgb has quit [Remote host closed the connection]
16:38nnym has quit [Ping timeout: 480 seconds]
16:43bgb has joined #asahi-dev
16:45pb17 has joined #asahi-dev
16:48rany has quit [Remote host closed the connection]
16:48rany has joined #asahi-dev
16:53__nick__ has joined #asahi-dev
16:53Rafaysven: Is this lspcie output expected? I think some nodes are missing. https://pastebin.com/PeSMcLTQ
16:54svenmy kernel branch does not contain much of the asahi-wip stuff
16:54svenso probably
16:55RafayOh, got it.
16:56___nick___ has quit [Ping timeout: 480 seconds]
16:57rhysmdnz has joined #asahi-dev
16:57svenchaos_princess: can you run https://f.svpe.de/f9237287e3af548f79fb0d8ceaa85c49b7f8f6ed27a36d07d15d6f86d1292b21_trace_acio.py.txt under the hv up until the point where you run ping and the packets then disappear?
16:58Guest15459 has joined #asahi-dev
16:59chaos_princessack, give me a bit
17:02Carlos has quit [Ping timeout: 480 seconds]
17:03Carlos has joined #asahi-dev
17:03svenideally both on macos and on linux once
17:05rany has quit [Remote host closed the connection]
17:05rany has joined #asahi-dev
17:05rany has quit [Remote host closed the connection]
17:06rany has joined #asahi-dev
17:08Guest15459 has quit [Quit: Bridge terminating on SIGTERM]
17:08rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
17:09nnym has joined #asahi-dev
17:15apc has quit [Quit: Ping timeout (120 seconds)]
17:15apc has joined #asahi-dev
17:15ralim89 has joined #asahi-dev
17:15msimonelli has quit [Read error: Connection reset by peer]
17:15msimonelli has joined #asahi-dev
17:15rhysmdnz has joined #asahi-dev
17:16Jamie1 has joined #asahi-dev
17:16ralim8 has quit [Read error: Connection reset by peer]
17:16ralim89 is now known as ralim8
17:18Rafaysven: here's your tracer on my machine if it helps. Linux: https://pastebin.com/V8kfgXPH Mac: https://pastebin.com/rGZNU87Y
17:37hdbngr has joined #asahi-dev
17:45hdbngr has quit [Ping timeout: 480 seconds]
17:55sventhanks! let me look at chaos' traces first and then yours
18:00svenchaos_princess: is that still with e2e enabled or disabled?
18:00chaos_princessshould be disabled unless i did sth wrong
18:02sven[cpu1] [ACIOTracer@/arm-io/acio1] TX ring 1 flags = 0x80000000 (ENABLE=1, RAW=0, NO_SNOOP=0, E2E_FLOW_CONTROL=0, ISOCH_ENABLE=0)
18:02sveni think it's still disabled
18:03sventhat should still work ofc, but that makes the traces hard to compare
18:03chaos_princessshould i make one w/ e2e enabled?
18:04sventhere has to be some difference somewhere and the closer the trace are the easier it will be to stop
18:15svenRafay: are you running the latest commits from the tbt-reset-wip branch? if yes, do you see a "TBT cable: cable_mode " entry in dmesg?
18:15sventhe issue there is just that the apple cable VSE is wrong
18:16sven[cpu4] [ACIOTracer@/arm-io/acio1] CTL TX WRITE route=0x0 port=0 space=SWITCH offset=0x36 len=1 seq=0 data=[0x00000603] <-- that's the VSE being written and after that nothing happens
18:16svenand macos writes [cpu2] [ACIOTracer@/arm-io/acio1] CTL TX WRITE route=0x0 port=0 space=SWITCH offset=0x36 len=1 seq=2 data=[0x00000413]
18:16svenso 0x413 is correct and 0x603 wrong
18:17hdbngr has joined #asahi-dev
18:22rany has quit [Remote host closed the connection]
18:23msimonelli5 has joined #asahi-dev
18:23msimonelli has quit [Read error: Connection reset by peer]
18:23rany has joined #asahi-dev
18:23msimonelli5 is now known as msimonelli
18:26hdbngr has quit [Ping timeout: 480 seconds]
18:32Rafay[ 193.553395] thunderbolt-apple-acio 501ac0000.nhi: TBT cable: cable_mode 0x0, device_mode 0x0, enter_vdo 0x3, orientation 2 -> cable info 0x603
18:32RafayI am not running the latest commit, let me fetch that.
18:33svenprobably won't make a difference, there's something wrong with the cable mode
18:34sventhat actually looks like either a bug in the tipd driver or my tbt-switch thing because those modes don't make sense
18:57svenchaos_princess: i dunno, this all looks very identical to me :-(
19:00svenfor some reason it just triggers no interrupts for ring1
19:04hdbngr has joined #asahi-dev
19:07svenlol, and ofc now i see a difference
19:07svensame story every time :D
19:07rany has quit [Ping timeout: 480 seconds]
19:08rany has joined #asahi-dev
19:12hdbngr has quit [Ping timeout: 480 seconds]
19:16chaos_princessshould i try this w/ or w/o e2e?
19:16svenshouldn't matter, but just with e2e
19:17blazra has quit [Quit: The Lounge - https://thelounge.chat]
19:17blazra6 has joined #asahi-dev
19:18hdbngr has joined #asahi-dev
19:20jsk has quit [Remote host closed the connection]
19:20jsk has joined #asahi-dev
19:27hdbngr has quit [Ping timeout: 480 seconds]
19:34svenchaos_princess: now this really shouldn't make a difference, but i'm kinda out of idea at this point: https://f.svpe.de/99fe30ff297fe3d18e7d347080279f27036bffe01b4f1bfc0500fc57bfa187f9_0002-HACK.patch
19:41hdbngr has joined #asahi-dev
19:51sventhis must be the fabric firewall the slop generators always talk about /s
19:51sveni'll get some sleep and stare at it again tomorrow
19:51sveni just must be missing something dumb somewhere
19:55hdbngr has quit [Ping timeout: 480 seconds]
19:55svenare you running linux on both machines?
19:55chaos_princessno, one is macos
19:56svenhrm... okay
19:56jannausven: cables are all working now. the issues before were probably caused by smc's charging handling breaking things when running HV and connecting a power source into the other port
19:56vup has quit []
19:57sveni think everything that doesn't use EUDO is very broken right now though. there's a bug somewhere in tipd that i'll have to figure out
19:57jannauincluding an optical usb4 cable
19:57svenhahaha, nice!
19:57svenso you not only have ~every mac out there, you also have ~every usb4 cable out there :D
20:00vup has joined #asahi-dev
20:07__nick__ has quit [Remote host closed the connection]
20:09svenchaos_princess: can you add return -ENODEV or whatever at the beginning of tb_xdomain_lane_bonding_enable in xdomain.c?
20:18rany has quit [Ping timeout: 480 seconds]
20:19chaos_princessgets stuck in connect/disconnect loop
20:19hdbngr has joined #asahi-dev
20:19chaos_princess"failed to add NVM devices: -19"
20:20rany has joined #asahi-dev
20:22svenugh, sorry. should've tested that first locally but i already shut down my test rig. anyway, maybe lane bonding is somehow broken because i don't see that with my m1 setup but i think yours tries to do that
20:22svenanyway, will take another look tomorrow
20:22svenprobably just need to move that return further down i guess
20:28hdbngr has quit [Ping timeout: 480 seconds]
20:32hdbngr has joined #asahi-dev
20:41hdbngr has quit [Ping timeout: 480 seconds]
20:42bgb has quit [Remote host closed the connection]
20:42bgb has joined #asahi-dev
20:44hdbngr has joined #asahi-dev
20:54hdbngr has quit [Ping timeout: 480 seconds]
20:56hdbngr has joined #asahi-dev
21:05hdbngr has quit [Ping timeout: 480 seconds]
21:12Yushi has quit [Remote host closed the connection]
21:14jole_ has quit [Remote host closed the connection]
21:15Yushi has joined #asahi-dev
21:15jole has joined #asahi-dev
21:19hdbngr has joined #asahi-dev
21:31hdbngr has quit [Ping timeout: 480 seconds]
21:34hdbngr has joined #asahi-dev
21:46hdbngr has quit [Ping timeout: 480 seconds]
21:59hdbngr has joined #asahi-dev
22:16hdbngr has quit [Ping timeout: 480 seconds]
22:19rany has quit [Remote host closed the connection]
22:19rany has joined #asahi-dev
22:31rany has quit [Remote host closed the connection]
22:33rany has joined #asahi-dev
23:24Rafaysven: I forced 0x413 in apple.c and now I am able to ping and nc.
23:26RafayThe other host is x86.
23:37hdbngr has joined #asahi-dev
23:38pb17 has quit [Ping timeout: 480 seconds]
23:45hdbngr has quit [Ping timeout: 480 seconds]
23:53pb17 has joined #asahi-dev
23:54hdbngr has joined #asahi-dev
…