#asahi-dev · 2026-02-06 11:03
mazarryn: in my modest experience, code is far less ambiguous then English. but if you think this is useful, go forth and write things up!#asahi-dev · 2026-02-06 11:03
noopwafelthe one relevant mention in irc logs is someone in 2022 asking "what does the "apcie=0xfffffffe" boot arg exactly do?"#asahi-dev · 2026-02-06 11:03
svenno idea, that commandline has just been growing from when we did the initial bringup years ago#asahi-dev · 2026-02-06 11:02
noopwafeldid anyone work out what apcie=0xfffffffe does#asahi-dev · 2026-02-06 11:00
svennot sure what's actually required there but that should give you very verbose usb debug output#asahi-dev · 2026-02-06 10:59
noopwafelsven: <3#asahi-dev · 2026-02-06 10:59
svennoopwafel: ^--#asahi-dev · 2026-02-06 10:59
svenAppleTypeCPhyUSBInterface-debug=0xffff AppleUSBHostResourcesTypeC-debug=0xffff#asahi-dev · 2026-02-06 10:59
svendebug=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#asahi-dev · 2026-02-06 10:59
arrynalso because reading linux driver code is not really easy for me haha#asahi-dev · 2026-02-06 10:59
sven*it#asahi-dev · 2026-02-06 10:59
svenit's definitely can't hurt and if you think it helps other people out go for it#asahi-dev · 2026-02-06 10:58
arrynI'm wondering would it be beneficial to document the hardware in text? (like the link noopwafel sent) Maybe I can try to do that a little and then contribute like that for now? I'm sure it would help other people that are like me out#asahi-dev · 2026-02-06 10:56
sventhat’s all the documentation there is #asahi-dev · 2026-02-06 10:56
arrynyeah I saw those#asahi-dev · 2026-02-06 10:56
svenyeah #asahi-dev · 2026-02-06 10:55
arrynsven: you mean the ones in m1n1/proxytool/experiments and such?#asahi-dev · 2026-02-06 10:55
arrynnoopwafel: I am not reaaally looking for anything in particular. What I'm curious about is currently "How does the keyboard work? What devices does it need to function?" etc sort of questions. Basically information gathering stage so that I can understand how more things work beyond what the devicetree shows me#asahi-dev · 2026-02-06 10:54
svenNot really, there’s usually some python scripts but that’s a similar level of documentation as the drivers #asahi-dev · 2026-02-06 10:53
arrynmaz: I am mostly talking about M1/M2 things right now that already have drivers the (asahi) linux repos. I was just wondering if someone took the time to document stuff somewhere without people needing to read the driver. #asahi-dev · 2026-02-06 10:51
noopwafelif you're looking for particular pieces then often the irc logs can be helpful.#asahi-dev · 2026-02-06 10:51
mazarryn: incomplete because things need to be reverse engineered?#asahi-dev · 2026-02-06 10:48
arrynnoopwafel: I saw this but it seems veeeeery incomplete#asahi-dev · 2026-02-06 10:48
svenbut other than tunables it’s the same driver essentially #asahi-dev · 2026-02-06 10:48
svenyeah, that’s what I assumed from looking at the adt ages ago #asahi-dev · 2026-02-06 10:47
noopwafeloh nice! for now I tried to add the new tunables (they changed all the naaames) to m1n1..#asahi-dev · 2026-02-06 10:47
svenIt’ll tell you which tunables it applies #asahi-dev · 2026-02-06 10:47
svenI can send you xnu bootargs later #asahi-dev · 2026-02-06 10:46
svenMaybe #asahi-dev · 2026-02-06 10:46
svenbut then it’s gonna work once #asahi-dev · 2026-02-06 10:46
svenyou could also use the generic snps,dwc3 or whatever compatible in the dwc3 node and remove all tipd and phy references #asahi-dev · 2026-02-06 10:45
noopwafeltracing the likely devices seems to only show _one_ tunable being applied#asahi-dev · 2026-02-06 10:45
svenlol :D#asahi-dev · 2026-02-06 10:45
noopwafelaha :D so "don't". thanks!#asahi-dev · 2026-02-06 10:44
sveneasiest way is to add empty tunables, it should fall back to usb2 only then #asahi-dev · 2026-02-06 10:43
noopwafelsven/whoever, how do I make usb do usb things without atcphy, what am I missing#asahi-dev · 2026-02-06 10:42
noopwafelhttps://github.com/AsahiLinux/docs/tree/main/docs/hw if you didn't find that :)#asahi-dev · 2026-02-06 10:41
arrynHello everyone! Besides the drivers and the device tree is there any documentation on the devices, their registers and so on? I'm currently poking around a little, writing my own code for testing, trying to poke at the platform a little so that down the line I can maybe help reverse engineering a little.#asahi-dev · 2026-02-05 21:34
getzbad depends on the context#asahi-dev · 2026-02-05 21:30
jannauI wouldn't call usb 2.0 or charge only cables bad. what's bad is that you need a cable tester to identify cable capabilities#asahi-dev · 2026-02-05 21:24
getzwell that was fun, in total 8 bad usb-c cables! Thanks for the help and see you again tomorrow! :)#asahi-dev · 2026-02-05 21:08
getznone#asahi-dev · 2026-02-05 21:08
chaos_princessno connection?#asahi-dev · 2026-02-05 21:08
getzlooks like im going cable shopping tomorrow, thanks chaos_princess!#asahi-dev · 2026-02-05 21:05
chaos_princessconnect them, go to network settings, see if the "Thunderbolt Bridge" is up, and both sides have ips#asahi-dev · 2026-02-05 21:04
getzchaos_princess: how do i let them talk to eachother over thunderbolt, both on macos now#asahi-dev · 2026-02-05 21:04
getzi might just have to#asahi-dev · 2026-02-05 21:03
ellyqwgetz: I would strongly suggest getting a cable tester for ~10eur and labeling/tossing away some of them, it made my life much easier#asahi-dev · 2026-02-05 21:02
getzbut theyre thick so i figured they wouldnt be the crappy kind#asahi-dev · 2026-02-05 21:02
getzjannau: 5th cable from my bin of usb-c to usb-c cables, theyre not labeled