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
hertz has quit [Ping timeout: 480 seconds]
hertz has joined #asahi-dev
capta1nt0ad has joined #asahi-dev
bps2 has quit [Ping timeout: 480 seconds]
yumasi_ has joined #asahi-dev
capta1nt0ad has quit [Quit: Konversation terminated!]
yumasi_ has quit [Ping timeout: 480 seconds]
capta1nt0ad has joined #asahi-dev
amarioguy has quit [Remote host closed the connection]
capta1nt0ad has quit [Ping timeout: 480 seconds]
kh has quit [Ping timeout: 480 seconds]
yumasi_ has joined #asahi-dev
yumasi_ has quit [Ping timeout: 480 seconds]
mini0n has joined #asahi-dev
derzahl has quit [Quit: auf wiedersehen]
derzahl has joined #asahi-dev
capta1nt0ad has joined #asahi-dev
pthariensflame has joined #asahi-dev
mini0n has quit []
<marcan>
jannau: do you want to resubmit your original NVMe fixup with a big comment about how the spec requires disabling the controller in order to enable it later, and on Apple controllers it makes more sense to do it right after shutdown to simplify the resume codepath?
<marcan>
(I still don't fully agree that this is specifically an Apple thing, the generic code seems brittle right now, but whatever, let's just get it fixed)
<marcan>
tagged another kernel with the nvme fix hopefully, pushed to asahi-dev
cylm has quit [Ping timeout: 480 seconds]
yumasi_ has joined #asahi-dev
<jannau>
marcan: sure, I'll do it tonight
<jannau>
marcan: we still have a cs42l84 playback regression in 6.2-rc2. looks like a regression caused by an incompatibility of the cs42l84 driver with 6.2-rc2
<marcan>
right, need to take a look at that
yumasi_ has quit [Remote host closed the connection]
yumasi_ has joined #asahi-dev
yumasi_ has quit [Ping timeout: 480 seconds]
capta1nt0ad has quit [Ping timeout: 480 seconds]
rkjnsn_ has joined #asahi-dev
<rkjnsn_>
sven: I don't think the Thunderbolt 3-to-2 adapter passes power, so the Ethernet adapter probably won't work without daisy chaining through a self-powered device, first.
<sven>
:/
<sven>
I don’t have the official apple adapter fwiw, fingers crossed that mine passed power
<sven>
*passes
<rkjnsn_>
🤞🏻 I'd also be happy to contribute a piece of hardware to the cause if needed.
capta1nt0ad has joined #asahi-dev
<sven>
thanks. that ethernet adapter is already out for delivery so i'll know in a few hours if it'll work out :)
<sven>
it's kinda the perfect first device anyway since it's so simple
yumasi_ has joined #asahi-dev
<marcan>
rkjnsn_: wait what, I thought you could use it with the FireWire adapter (which obviously needs power)?
<sven>
"This adapter is not compatible with Thunderbolt 4 computers" but "Provides power for devices powered by bus" hrm..
<marcan>
"However, using this adapter with an Apple Thunderbolt Display requires a power source, because the display does not provide power through the adapter." that makes sense - it doesn't do *reverse* power
<marcan>
"In addition, it can be used to connect Thunderbolt-enabled displays — such as the Apple Thunderbolt Display and LG Thunderbolt 2 displays — to any of the Thunderbolt 3 (USB-C) / USB 4 ports on your Mac." claims USB4 works
<sven>
oh... yeah, that makes sense
<marcan>
isn't TB4 just USB4 anyway?
<sven>
I think so
<sven>
but as i said, i have some StarTech adapter which was cheaper when I bought it years ago
<sven>
and they claim to only support TB3 so who knows what they messed up
<marcan>
heh
<rkjnsn_>
Admittedly I've only used it to connect a Thunderbolt 3 device to a Thunderbolt 2 computer, and it *definitely* doesn't pass power that way. I thought I read it didn't pass power in either direction, but I have not way to test at the moment.
<rkjnsn_>
Very possible I'm just mistaken.
<rkjnsn_>
no way*
<marcan>
apparently TB4 is just extra spec requirements
<marcan>
which hilariously means M1/M2 devices aren't TB4 compliant... because TB4 requires being able to drive two monitors
<marcan>
that's it. that's the reason they aren't.
<sven>
yeah, as far as I udnerstand TB4 is USB4 + some extra requirements
<sven>
(plus paying $$$ for certification I think)
<marcan>
yeah
<sven>
apparently the thunderbolt display works with the official apple adapter but doesn't with the startech one I have *sigh*
<sven>
so it looks like they might've done something dumb that breaks with usb4
<sven>
urgh... I also just realized the thunderbolt DART for a port only seems to come up *after* that pcie port is initialized. getting that supported is going to be quite a hack as well :(
yumasi_ has quit [Ping timeout: 480 seconds]
cy8aer has quit [Remote host closed the connection]
<Cyrinux>
Hi marcan, with edge rc3, I just test resume on m2 air, and sorry to say that nvme on resume looks still off, I have to force reboot with staying press on power then to wake it up.
<Cyrinux>
(i try several time to confirm)
MajorBiscuit has joined #asahi-dev
bps2 has joined #asahi-dev
ChaosPrincess has quit [Quit: WeeChat 3.7.1]
ChaosPrincess has joined #asahi-dev
bps2 has quit [Ping timeout: 480 seconds]
cylm has joined #asahi-dev
leitao has joined #asahi-dev
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
<arnd>
marcan, sven: regarding tb4 spec compliance, it sounds to me like Intel intentionally picked VT-D as a requirement in order to exclude AMD cpus
<arnd>
But I think that also rules out M1 because of DART, unless they actually made that compatible with Intel's IOMMU
<maz>
cheeky...
<sven>
hah
cylm has quit [Ping timeout: 480 seconds]
<chadmed_>
arnd: iiuc they don't mandate specifically vt-d specifically, but support for dma virt/directed io in general
<chadmed_>
which wouldnt stop amd, and theyd be braindead to try and thwart apple given the co-designed the spec out of what was left of lightpeak...
<chadmed_>
plus intel isnt really in a strategic position to be making enemies out of anyone atm
<mps>
chadmed_: latest 6.2-rc3 tag 1 kernel still have distorted audio on m1pro macbook. I guess you know but just to remind you
<chadmed_>
mps: on the headphone jack?
<mps>
yes
bps2 has joined #asahi-dev
<chadmed_>
there's a few commits it _might_ be
<marcan>
arnd: I think Apple claims TB4 compliance for t600x though? I saw that somewhere
<chadmed_>
Video Support: Thunderbolt 4 digital video output
<chadmed_>
the spec page for the mac studio mentions TB4 explicitly a few times, and they sell TB4 cables
<arnd>
marcan: I think for all practical purposes the requirement is being either Intel or Apple.
<chadmed_>
theres an intel "paper" floating around somewhere where they use the terms VT-d/AMD IOMMU/ARM SMMU interchangeably when talking about dma hardening in the uefi env
<sven>
the tbt->ethernet adapter just arrived and it shows up in macos on this m1 :)
<chadmed_>
arnd: being that it's a press deck id read any reference to "Intel VT-d" as being "some implementation of DMA remapping and virtualisation"
<chadmed_>
a company we work with tries to sell MS SQL Server 2019 as their own branded solution... until the implementers install it on client servers of course ;)
<chadmed_>
“I wouldn’t read it as it’s only Intel, because of VT-d,” Ziller said. “If [at AMD] there was an equivalent technology that supports DMA protection, that supports prevention against physical attacks, then that would be the requirement.”
<chadmed_>
intel integrate thunderbolt controllers on their socs whereas board vendors have to chuck an intel controller on the pcie bus for amd (expensive and takes away pcie lanes from things people actually use like nvme)
MajorBiscuit has quit [Quit: WeeChat 3.6]
<sven>
mac studio seems to claim thunderbolt 4 support fwiw
<chadmed_>
yeah the studio spec page mentions it a few times
<chadmed_>
i believe its "real" TB4 because the spec pages for t8103 and t8112 products make a note of saying "Thunderbolt 3/USB4" instead
<sven>
so maybe it really is that dual display support in the end :D
<chadmed_>
yeah i dont think intel would be stupid enough to try to say "oh btw to use tb4 you have to have vt-d which we dont license lol soz" and if they were that stupid theyd get immediately ground into a fine paste by competition watchdogs the world over
zalyx has quit [Quit: later alligator]
zalyx has joined #asahi-dev
zalyx has quit []
zalyx has joined #asahi-dev
tim has joined #asahi-dev
tim is now known as Guest1251
StupidYui has quit [Ping timeout: 480 seconds]
nico_32 has quit [Ping timeout: 480 seconds]
eiln has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nico_32 has joined #asahi-dev
leitao has joined #asahi-dev
bisko has joined #asahi-dev
chadmed_ has quit [Remote host closed the connection]
eiln has quit [Quit: Page closed]
mofux has joined #asahi-dev
mofux has quit [Remote host closed the connection]
balor has joined #asahi-dev
hightower2 has quit [Ping timeout: 480 seconds]
flokli has joined #asahi-dev
hightower2 has joined #asahi-dev
nicolas17 has joined #asahi-dev
hightower2 has quit []
balor has quit [Quit: balor]
bcrumb has joined #asahi-dev
derzahl has quit [Remote host closed the connection]
mps has quit [Quit: Lost terminal]
mps has joined #asahi-dev
derzahl has joined #asahi-dev
bcrumb has quit [Quit: WeeChat 3.7.1]
bcrumb has joined #asahi-dev
bcrumb has quit []
amarioguy has joined #asahi-dev
nicolas17 has quit [Ping timeout: 480 seconds]
landscape15 has joined #asahi-dev
<landscape15>
Are you planning to upstream u-boot changes in the future?
<j`ey>
landscape15: what do you mean? upstream already has some m1 support
<j`ey>
more to be upstreamed still, yes
landscape15_ has joined #asahi-dev
leftas has joined #asahi-dev
<landscape15_>
Thank you. I ask because it seems to lack some features.
landscape15_ has quit []
<j`ey>
upstream is missing m2 keyboard support and a dummy atc driver
landscape15 has quit [Ping timeout: 480 seconds]
<kettenis>
and in both those cases I'm waiting until the bindings have been upstreamed on the linux side before pushing these upstream
<sven>
which is probably a good idea for at least atc. I hope I won’t have to change much for thunderbolt but who knows
DarkShadow4444 has joined #asahi-dev
DarkShadow4444 has quit [Remote host closed the connection]
DarkShadow4444 has joined #asahi-dev
DarkShadow44 has quit [Ping timeout: 480 seconds]
hertz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<eric_engestrom>
marcan: did you forget to push a commit to the linux-asahi PKGBUILD? -rc2 vs -rc3
<eric_engestrom>
(also, totally unrelated obviously, but I have a macsmc patch that I still need to test, but if/when it's good to go, against what branch should I post the PR on github?)
<j`ey>
bits/110-smc probably?
<eric_engestrom>
thx :)
<j`ey>
Im not sure if markan even pulls via github anyway, he seems to cherry-pick onto the right branch locally
leftas has quit [Quit: Bye!]
leftas has joined #asahi-dev
leftas has quit []
leftas has joined #asahi-dev
tim has joined #asahi-dev
leitao has joined #asahi-dev
tim is now known as Guest1286
leitao has quit [Read error: Connection reset by peer]
Guest1251 has quit [Ping timeout: 480 seconds]
Guest1286 has quit [Ping timeout: 480 seconds]
ayke has joined #asahi-dev
sethbrasile has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seeeath has joined #asahi-dev
axboe has quit [Quit: Lost terminal]
SSJ_GZ has quit [Ping timeout: 480 seconds]
chadmed_ has joined #asahi-dev
axboe has joined #asahi-dev
capta1nt0ad has quit [Remote host closed the connection]