#asahi-dev · 2022-03-15 17:32
marcanDcow[m]1: this answers your question, it's USB4, because that setting in that mux is precisely what USB4 is (that TB isn't)#asahi-dev · 2022-03-15 17:31
marcanso that's the digital mux in front of the USB3 host/device core#asahi-dev · 2022-03-15 17:31
marcanyup#asahi-dev · 2022-03-15 17:30
marcanthat would make sense for a "pipe mux"#asahi-dev · 2022-03-15 17:29
marcanwhich basically means, as far as PIPE is concerned, usb2 means "null", usb3 means "usb3 PHY", and usb4 means "tunnel through TB"#asahi-dev · 2022-03-15 17:29
marcanmaybe usb2 is just 2-only, usb3 is both, and usb4 is 2+4-over-thunderbolt?#asahi-dev · 2022-03-15 17:28
marcanotherwise hubs wouldn't work#asahi-dev · 2022-03-15 17:28
marcanbut both need to work at the same time...#asahi-dev · 2022-03-15 17:27
marcanit's a dedicated lane...#asahi-dev · 2022-03-15 17:27
marcanhow does that work?#asahi-dev · 2022-03-15 17:27
marcanwait usb*2* is muxed?#asahi-dev · 2022-03-15 17:27
marcanheh, right#asahi-dev · 2022-03-15 17:26
marcanit's like that ULPI thing for USB2#asahi-dev · 2022-03-15 17:26
marcanPIPE is the term for the back end of the USB3 PHY IIRC#asahi-dev · 2022-03-15 17:26
marcanyeah#asahi-dev · 2022-03-15 17:26
marcanoh you mean 3#asahi-dev · 2022-03-15 17:25
marcanyou mean for usb4 comms?#asahi-dev · 2022-03-15 17:25
marcandwc3?#asahi-dev · 2022-03-15 17:22
marcansince for some reason all the code to do it without DCP is also there#asahi-dev · 2022-03-15 17:21
marcankeep in mind there are kexts that are dupes of DCP functionality#asahi-dev · 2022-03-15 17:21
marcanlike the training etc#asahi-dev · 2022-03-15 17:21
marcansven: all the actual DP PHY stuff should be done by DCP#asahi-dev · 2022-03-15 17:17
marcanhttps://www.youtube.com/watch?v=q5xvwPa3r7M#asahi-dev · 2022-03-15 17:17
marcanwhy not a long, fat wire?#asahi-dev · 2022-03-15 17:16
marcanand you think atcphy will be easier? :p#asahi-dev · 2022-03-15 17:16
marcanmaz: TB *includes* display!#asahi-dev · 2022-03-15 17:16
marcan(being nice here)#asahi-dev · 2022-03-15 17:16
marcansven: displayport first#asahi-dev · 2022-03-15 17:11
marcantpw_rules: pushed new installer & m1n1#asahi-dev · 2022-03-15 17:00
marcanif you are on t6000 and you did not upgrade back when the AIC2 binding changed then yes#asahi-dev · 2022-03-15 16:56
marcanthanks for catching this :)#asahi-dev · 2022-03-15 16:55
marcanworkaroundable downstream though#asahi-dev · 2022-03-15 16:55
marcanthat's actually kinda bad so yeah#asahi-dev · 2022-03-15 16:55
marcanI wasn't reserving memory for bootargs/etc#asahi-dev · 2022-03-15 16:55
marcanyeah found it#asahi-dev · 2022-03-15 16:53
marcanlikely something clobbers the bootargs between when m1n1 loads and the python stuff loads#asahi-dev · 2022-03-15 16:53
marcanI think I have an idea of what it must be#asahi-dev · 2022-03-15 16:51
marcanhmm#asahi-dev · 2022-03-15 16:51
marcannot that#asahi-dev · 2022-03-15 16:51
marcanno#asahi-dev · 2022-03-15 16:51
marcanohhh wait#asahi-dev · 2022-03-15 16:51
marcanwhich is weird#asahi-dev · 2022-03-15 16:51
marcanthat looks like bootargs isn't properly passed through#asahi-dev · 2022-03-15 16:49
marcantpw_rules: do you have logs?#asahi-dev · 2022-03-15 16:48
marcanthat's very weird though because obviously the ADT gets passed through or everything would explode#asahi-dev · 2022-03-15 16:47
marcan*hm#asahi-dev · 2022-03-15 16:47
marcantm#asahi-dev · 2022-03-15 16:47
marcanmps: ah yeah, need to fix that#asahi-dev · 2022-03-15 16:47
marcantpw_rules: you mean kmutil m1n1 -> gpt m1n1 -> hv?#asahi-dev · 2022-03-15 16:44
marcanah sorry, not m1n1 per se, just the installer