#
…

2023-01-13

00:11hertz has quit [Ping timeout: 480 seconds]
00:12hertz has joined #asahi-dev
01:06capta1nt0ad has joined #asahi-dev
01:06bps2 has quit [Ping timeout: 480 seconds]
01:39yumasi_ has joined #asahi-dev
01:47capta1nt0ad has quit [Quit: Konversation terminated!]
01:47yumasi_ has quit [Ping timeout: 480 seconds]
01:47capta1nt0ad has joined #asahi-dev
02:47amarioguy has quit [Remote host closed the connection]
03:04capta1nt0ad has quit [Ping timeout: 480 seconds]
03:21kh has quit [Ping timeout: 480 seconds]
03:45yumasi_ has joined #asahi-dev
03:53yumasi_ has quit [Ping timeout: 480 seconds]
03:54mini0n has joined #asahi-dev
04:04derzahl has quit [Quit: auf wiedersehen]
04:04derzahl has joined #asahi-dev
04:25capta1nt0ad has joined #asahi-dev
04:34pthariensflame has joined #asahi-dev
04:38mini0n has quit []
04:55marcanjannau: 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?
04:56marcan(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)
05:02pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
05:04capta1nt0ad has quit [Ping timeout: 480 seconds]
05:17capta1nt0ad has joined #asahi-dev
06:04SSJ_GZ has joined #asahi-dev
06:15yumasi_ has joined #asahi-dev
06:23yumasi_ has quit [Ping timeout: 480 seconds]
06:25marcantagged another kernel with the nvme fix hopefully, pushed to asahi-dev
06:35cylm has quit [Ping timeout: 480 seconds]
06:45yumasi_ has joined #asahi-dev
06:52jannaumarcan: sure, I'll do it tonight
06:56jannaumarcan: 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
06:56marcanright, need to take a look at that
06:58yumasi_ has quit [Remote host closed the connection]
07:07yumasi_ has joined #asahi-dev
07:15yumasi_ has quit [Ping timeout: 480 seconds]
07:15capta1nt0ad has quit [Ping timeout: 480 seconds]
07:20rkjnsn_ has joined #asahi-dev
07:21rkjnsn_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.
07:27svenI don’t have the official apple adapter fwiw, fingers crossed that mine passed power
07:28sven*passes
07:35rkjnsn_🤞🏻 I'd also be happy to contribute a piece of hardware to the cause if needed.
07:37capta1nt0ad has joined #asahi-dev
07:40sventhanks. that ethernet adapter is already out for delivery so i'll know in a few hours if it'll work out :)
07:40svenit's kinda the perfect first device anyway since it's so simple
07:44yumasi_ has joined #asahi-dev
07:44marcanrkjnsn_: wait what, I thought you could use it with the FireWire adapter (which obviously needs power)?
07:45sven"This adapter is not compatible with Thunderbolt 4 computers" but "Provides power for devices powered by bus" hrm..
07:45sven50:50 chance I guess
07:46marcan"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
07:47marcan"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
07:47svenoh... yeah, that makes sense
07:47marcanisn't TB4 just USB4 anyway?
07:47svenI think so
07:47svenbut as i said, i have some StarTech adapter which was cheaper when I bought it years ago
07:47svenand they claim to only support TB3 so who knows what they messed up
07:49rkjnsn_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.
07:50rkjnsn_Very possible I'm just mistaken.
07:50marcanapparently TB4 is just extra spec requirements
07:51marcanwhich hilariously means M1/M2 devices aren't TB4 compliant... because TB4 requires being able to drive two monitors
07:51marcanthat's it. that's the reason they aren't.
07:51svenyeah, as far as I udnerstand TB4 is USB4 + some extra requirements
07:51sven(plus paying $$$ for certification I think)
07:53svenapparently the thunderbolt display works with the official apple adapter but doesn't with the startech one I have *sigh*
07:53svenso it looks like they might've done something dumb that breaks with usb4
07:56svenurgh... 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 :(
07:58yumasi_ has quit [Ping timeout: 480 seconds]
08:03cy8aer has quit [Remote host closed the connection]
08:05CyrinuxHi 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.
08:07Cyrinux(i try several time to confirm)
09:17MajorBiscuit has joined #asahi-dev
09:23bps2 has joined #asahi-dev
09:49ChaosPrincess has quit [Quit: WeeChat 3.7.1]
09:49ChaosPrincess has joined #asahi-dev
10:16bps2 has quit [Ping timeout: 480 seconds]
10:18cylm has joined #asahi-dev
10:18leitao has joined #asahi-dev
10:37bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:43jluthra has quit [Remote host closed the connection]
10:43jluthra has joined #asahi-dev
11:14arndmarcan, sven: regarding tb4 spec compliance, it sounds to me like Intel intentionally picked VT-D as a requirement in order to exclude AMD cpus
11:15arndBut I think that also rules out M1 because of DART, unless they actually made that compatible with Intel's IOMMU
11:20mazcheeky...
11:28cylm has quit [Ping timeout: 480 seconds]
11:28chadmed_arnd: iiuc they don't mandate specifically vt-d specifically, but support for dma virt/directed io in general
11:31chadmed_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...
11:33chadmed_plus intel isnt really in a strategic position to be making enemies out of anyone atm
11:43mpschadmed_: latest 6.2-rc3 tag 1 kernel still have distorted audio on m1pro macbook. I guess you know but just to remind you
11:43chadmed_mps: on the headphone jack?
11:46bps2 has joined #asahi-dev
11:54chadmed_there's a few commits it _might_ be
12:02marcanarnd: I think Apple claims TB4 compliance for t600x though? I saw that somewhere
12:07chadmed_Video Support: Thunderbolt 4 digital video output
12:08chadmed_the spec page for the mac studio mentions TB4 explicitly a few times, and they sell TB4 cables
12:09arndmarcan: I think for all practical purposes the requirement is being either Intel or Apple.
12:09arndhttps://www.thunderbolttechnology.net/sites/default/files/intel-thunderbolt4-announcement-press-deck.pdf seems very explicit about requiring "Intel® Virtualization Technology for Directed I/O" rather than any other way of doing the same thing
12:09chadmed_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
12:12sventhe tbt->ethernet adapter just arrived and it shows up in macos on this m1 :)
12:12chadmed_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"
12:13chadmed_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 ;)
12:15chadmed_“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.”
12:25arndchadmed_: it would help to have the actual specification, but the thing I can tell for sure is that at the moment every Intel Socket1700 mainboard advertises TB4, while the AMD AM5 boards only advertise USB4, see https://www.asus.com/motherboards-components/motherboards/proart/proart-x670e-creator-wifi/techspec/
12:26chadmed_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)
12:27MajorBiscuit has quit [Quit: WeeChat 3.6]
12:28svenmac studio seems to claim thunderbolt 4 support fwiw
12:28chadmed_yeah the studio spec page mentions it a few times
12:29chadmed_i believe its "real" TB4 because the spec pages for t8103 and t8112 products make a note of saying "Thunderbolt 3/USB4" instead
12:29svenso maybe it really is that dual display support in the end :D
12:31chadmed_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
12:46zalyx has quit [Quit: later alligator]
12:47zalyx has joined #asahi-dev
12:47zalyx has quit []
12:49zalyx has joined #asahi-dev
12:54tim has joined #asahi-dev
12:55tim is now known as Guest1251
13:24StupidYui has quit [Ping timeout: 480 seconds]
13:24nico_32 has quit [Ping timeout: 480 seconds]
13:27eiln has joined #asahi-dev
13:29leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:34nico_32 has joined #asahi-dev
13:42leitao has joined #asahi-dev
13:48bisko has joined #asahi-dev
13:50chadmed_ has quit [Remote host closed the connection]
14:00eiln has quit [Quit: Page closed]
14:00mofux has joined #asahi-dev
14:01mofux has quit [Remote host closed the connection]
14:15balor has joined #asahi-dev
14:19hightower2 has quit [Ping timeout: 480 seconds]
14:35flokli has joined #asahi-dev
15:04hightower2 has joined #asahi-dev
15:08nicolas17 has joined #asahi-dev
15:29hightower2 has quit []
16:11balor has quit [Quit: balor]
16:12bcrumb has joined #asahi-dev
16:29derzahl has quit [Remote host closed the connection]
16:29mps has quit [Quit: Lost terminal]
16:31mps has joined #asahi-dev
16:40derzahl has joined #asahi-dev
16:44bcrumb has quit [Quit: WeeChat 3.7.1]
16:58bcrumb has joined #asahi-dev
16:58bcrumb has quit []
17:07amarioguy has joined #asahi-dev
17:31nicolas17 has quit [Ping timeout: 480 seconds]
17:58landscape15 has joined #asahi-dev
18:00landscape15Are you planning to upstream u-boot changes in the future?
18:00j`eylandscape15: what do you mean? upstream already has some m1 support
18:01j`eymore to be upstreamed still, yes
18:03landscape15_ has joined #asahi-dev
18:03leftas has joined #asahi-dev
18:03landscape15_Thank you. I ask because it seems to lack some features.
18:06landscape15_ has quit []
18:06j`eyupstream is missing m2 keyboard support and a dummy atc driver
18:10landscape15 has quit [Ping timeout: 480 seconds]
18:13kettenisand in both those cases I'm waiting until the bindings have been upstreamed on the linux side before pushing these upstream
18:18svenwhich is probably a good idea for at least atc. I hope I won’t have to change much for thunderbolt but who knows
18:25DarkShadow4444 has joined #asahi-dev
18:26DarkShadow4444 has quit [Remote host closed the connection]
18:26DarkShadow4444 has joined #asahi-dev
18:32DarkShadow44 has quit [Ping timeout: 480 seconds]
18:33hertz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:40sethbrasile has joined #asahi-dev
18:41sethbrasile is now known as SethTheGreat
18:42SethTheGreat is now known as seeeath
19:04abby has quit [Ping timeout: 480 seconds]
19:10abby has joined #asahi-dev
19:18leitao has quit [Quit: Textual IRC Client: www.textualapp.com]
19:24seeeath has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:24nicolas17 has joined #asahi-dev
19:24sethbrasile has joined #asahi-dev
19:32rkjnsn_ has quit [Remote host closed the connection]
19:44balor has joined #asahi-dev
19:46balrog has quit [Quit: Bye]
19:50balrog has joined #asahi-dev
19:57pthariensflame has joined #asahi-dev
20:04pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
20:11eric_engestrommarcan: did you forget to push a commit to the linux-asahi PKGBUILD? -rc2 vs -rc3
20:15eric_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?)
20:17j`eybits/110-smc probably?
20:17j`eyIm not sure if markan even pulls via github anyway, he seems to cherry-pick onto the right branch locally
20:36leftas has quit [Quit: Bye!]
20:36leftas has joined #asahi-dev
20:36leftas has quit []
20:37leftas has joined #asahi-dev
21:10tim has joined #asahi-dev
21:10leitao has joined #asahi-dev
21:10tim is now known as Guest1286
21:12leitao has quit [Read error: Connection reset by peer]
21:17Guest1251 has quit [Ping timeout: 480 seconds]
21:19Guest1286 has quit [Ping timeout: 480 seconds]
21:47ayke has joined #asahi-dev
22:20sethbrasile has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:22seeeath has joined #asahi-dev
22:40axboe has quit [Quit: Lost terminal]
22:40SSJ_GZ has quit [Ping timeout: 480 seconds]
22:40chadmed_ has joined #asahi-dev
22:42axboe has joined #asahi-dev
23:48capta1nt0ad has quit [Remote host closed the connection]
…