#asahi-dev · 2026-01-20 07:50
jannauI stripped and restructured the dt quite a bit from the last version I pushed#asahi-dev · 2026-01-20 07:50
noopwafelthanks! just that information helps a lot :)#asahi-dev · 2026-01-20 07:49
jannauthat works, all 8 cores are up and receive irqs#asahi-dev · 2026-01-20 07:49
noopwafeland thanks, I indeed based my dts on yours#asahi-dev · 2026-01-20 07:49
noopwafelsmt meaning bringing up more than one core.. :)#asahi-dev · 2026-01-20 07:48
jannaunot sure what smt refers to and I have no idea if the cpuidle driver is used#asahi-dev · 2026-01-20 07:47
jannaunoopwafel: https://github.com/jannau/m1n1/tree/t8122_bringup + https://github.com/jannau/linux/tree/t8122-j504 does work for the limited hw enabled / present in the device tree#asahi-dev · 2026-01-20 07:41
noopwafelmy tree is also full of hacks for other things, so this _entirely_ might be my fault, but if anyone has tips to avoid me reinventing the wheel, let me know#asahi-dev · 2026-01-20 07:38
noopwafelmy linux boot on the m3 air is still pretty broken, I had to sabotage smt and chicken bits and the cpuidle driver#asahi-dev · 2026-01-20 06:57
jannaufl0_id: the 16 core variant is t6031. the possible issues I saw are with the 14-core variant (t6034)#asahi-dev · 2026-01-20 06:04
LarstiQsven: how large is your .zsh_history that you still have that? :)#asahi-dev · 2026-01-20 00:34
fl0_idjannau 16 core. I thought it was referred to as t6031 as well... but yeah I'll try to check that#asahi-dev · 2026-01-19 22:43
jannaumcc has some spicy changes, breakage on t6034 could be possible when pretending it is a t6031#asahi-dev · 2026-01-19 22:39
jannaufl0_id: do you have the 14 or 16 core M3 max (t6034 or t6031). Those are distinct chips for m3#asahi-dev · 2026-01-19 20:47
jannauI'll give you the full log+trace once I sorted out the let's encrypt issues on my web server (they seem to require A/AAAA records now)#asahi-dev · 2026-01-19 20:45
sven*then#asahi-dev · 2026-01-19 20:45
sventhe once I fix the atcphy issue those will just work as well on Linux #asahi-dev · 2026-01-19 20:44
svenok nice #asahi-dev · 2026-01-19 20:41
jannauit's identical between optical and electric cables#asahi-dev · 2026-01-19 20:40
jannauIOThunderboltSwitchType5(1@0)::updateCableParameters - offset = 0x36 value = 0x00000011 current = 0x00000000 cached = 0x00000000#asahi-dev · 2026-01-19 20:38
jannauthat works, not sure what's different#asahi-dev · 2026-01-19 20:23
sventhose were my bootargs in that old log#asahi-dev · 2026-01-19 20:23
svenAppleTypeCPhyInterface-debug=0xffff AppleTypeCPhyUSBInterface-debug=0xffff AppleUSBHostResourcesTypeC-debug=0xffff tbdebug=0xffff tblog=1#asahi-dev · 2026-01-19 20:23
sven<Notice>: boot-args = debug=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#asahi-dev · 2026-01-19 20:22
jannautesting 13.5#asahi-dev · 2026-01-19 20:21
svenmaybe they removed that print in later macos versions :/#asahi-dev · 2026-01-19 20:21
sventhat's strange#asahi-dev · 2026-01-19 20:20
jannauno updateCableParameters#asahi-dev · 2026-01-19 20:18
svenand that changes depending on the cable type#asahi-dev · 2026-01-19 20:18
sventhat thing, the value there is what gets written to the vendor specific reg#asahi-dev · 2026-01-19 20:18
svenIOThunderboltSwitchType5(1@0)::updateCableParameters - offset = 0x36 value = 0x00000601 current = 0x00000000 cached = 0x00000000#asahi-dev · 2026-01-19 20:17
svenIOThunderboltSwitchType5(1@0)::updateCableParameters#asahi-dev · 2026-01-19 20:17
svenah, wrong log#asahi-dev · 2026-01-19 20:14
svenhuh#asahi-dev · 2026-01-19 20:13
jannauthat's always 0x00000000#asahi-dev · 2026-01-19 20:08
svendata_status comes from their TI-driver iirc#asahi-dev · 2026-01-19 20:07
svenis there also some status =?#asahi-dev · 2026-01-19 20:03
jannauyes, that did it. "AppleThunderboltHALType5(1)::getCableState - data_status = 0x16c00011"#asahi-dev · 2026-01-19 19:57
sveni should've taken notes instead of relying on .zsh_history from years ago :D#asahi-dev · 2026-01-19 19:56
svenmaybe tbdebug=0xffff tblog=0xffff tblogmode=0xffff #asahi-dev · 2026-01-19 19:56
svenhrm, then it's missing some debug flag. let me check again#asahi-dev · 2026-01-19 19:53
jannauno getCableState in the syslog#asahi-dev · 2026-01-19 19:50
sven"....::getCableState - status = 0x????????" that's the serial output i'm looking for#asahi-dev · 2026-01-19 19:45
sventhat's my default debug commandline, can't remember if the VSE write was part of that though#asahi-dev · 2026-01-19 19:44
svenleTypeCPhyCIOInterface-debug=0xffff AppleTypeCPhyDisplayPortInterface-debug=0xffffffff AppleTypeCPhyInterface-debug=0xffff AppleTypeCPhyUSBInterface-debug=0xffff AppleUSBHostResourcesTypeC-debug=0xffff#asahi-dev · 2026-01-19 19:44
svendebug=0x14e serial=3 apcie=0xfffffffe wdt=-1 AppleSynopsysDRDUSBXHCI-debug=0xffff AppleT8103TypeCPhy-debug=0xffff AppleT8103USB40XHCITypeCPort-debug=0xffff AppleT8103USBXDCI-debug=0xffff AppleTypeCPhy-debug=0xffff App#asahi-dev · 2026-01-19 19:44
svenAppleTypeCPhyCIOInterface-debug maybe#asahi-dev · 2026-01-19 19:42
jannauack#asahi-dev · 2026-01-19 19:40
svenit will print that magic value in there #asahi-dev · 2026-01-19 19:39
svenI need the write to the thunderbolt vendor specific area as well, I’d also need xnu output with some debug flag I’ll have to look up