Telvana has quit [Read error: Connection reset by peer]
PhilippvK has joined #asahi-dev
phiologe has quit [Ping timeout: 480 seconds]
Telvana has joined #asahi-dev
yuyichao has joined #asahi-dev
kov has quit [Quit: Coyote finally caught me]
ricekot has joined #asahi-dev
nicolas17 has quit [Ping timeout: 480 seconds]
chadmed_ has joined #asahi-dev
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
amw has quit [Read error: No route to host]
amw has joined #asahi-dev
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
the_lanetly_052___ has joined #asahi-dev
the_lanetly_052 has joined #asahi-dev
the_lanetly_052__ has joined #asahi-dev
the_lanetly_052___ has quit [Ping timeout: 480 seconds]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
the_lanetly_052___ has joined #asahi-dev
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
the_lanetly_052___ has quit [Remote host closed the connection]
chadmed_ has quit [Remote host closed the connection]
jabashque has quit [Quit: Connection closed for inactivity]
<maz>
sven: re ATCPHY: the DT changes are making u-boot pretty unhappy ("Bus usb@702280000: Port not available."). I'll try and have a look.
<maz>
sven: duh, resets. I've bodged it.
V has quit [Remote host closed the connection]
<maz>
sven: we're in business. I have the feeling that there is some odd orientation issues (flipping cables made things work...)
<j`ey>
run the debian test!
V has joined #asahi-dev
<maz>
j`ey: it *is* running!
<maz>
j`ey: about 30 second *slower* than the Mini.
<j`ey>
huh
farzit has joined #asahi-dev
<maz>
I can gain *some* performance back by pinning the guest to a single cluster, but this is still about 22 seconds behind at best (about 15% slower).
<maz>
this is still bloody fast, but I guess physics gets in the way of absolute performance.
bisko has joined #asahi-dev
<sven>
huh, the orientation should be correct. i know about two other issues though: sometimes it won't find the device when it's connected during boot; and it takes ~5 seconds to find newly connected devices
<sven>
676748389f5 should also already be in torvald's tree, without that it won't be able to tell the orientation
<maz>
sven: yeah, I've seen the delay, but there definitely was something with one of my USB/SATA adapter. it wasn't detected, and I was trying to understand why it was failing. in the end, I flipped the cable and the device showed up.
<sven>
weird
<sven>
which adapter is that? all my usb 3 devices work in both orientations
<sven>
hrm, i guess it could also be some difference they introduced in the max/pro/ultra
<maz>
Bus 012 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
<maz>
I'll try and reproduce it once I'm done doing silly thing with the new toy...
<maz>
I'll push the DT patches somewhere so that you and jannau can merge them into what you already have.
<maz>
ah, it could also be that the fuse values are not entirely correct for Ultra (I lifted the Max settings).
<sven>
sounds good, i found an adapter with that chip for like 10 eur on amazon. if you can reproduce it i'll just buy that one and see what happens here
<sven>
true, i don't really know what half of these fuses do anyway
<maz>
sven: don't buy anything until I've confirmed it... (and worse case, I can send it to you).
<sven>
sure :)
<maz>
sven: it's more subtle than that. it depends on the *cable*. one of them (rumoured to be a USB-3.2 Gen-2 cable) triggers the problem.
<maz>
another (non-descript) cable works just fine.
<sven>
oh fun
<maz>
and I got the enclosure wrong. the one I trigger this on is:
<maz>
Bus 006 Device 002: ID 174c:235c ASMedia Technology Inc. Ugreen Storage Device
<maz>
(too many storage devices)
nicolas17 has joined #asahi-dev
farzit has quit [Ping timeout: 480 seconds]
<kettenis>
jannau, sven: regarding that u-boot patch that's still missing upstream; we could work around the issue in the DT by dropping the dr_mode property (since 'otg' is the default for the Linux kernel
<kettenis>
but hopefully it will be picked up soon