#
✕ nick:jannau
#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 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-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: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:22
jannautesting 13.5
#asahi-dev · 2026-01-19 20:20
jannauno updateCableParameters
#asahi-dev · 2026-01-19 20:13
jannauthat's always 0x00000000
#asahi-dev · 2026-01-19 20:03
jannauyes, that did it. "AppleThunderboltHALType5(1)::getCableState - data_status = 0x16c00011"
#asahi-dev · 2026-01-19 19:53
jannauno getCableState in the syslog
#asahi-dev · 2026-01-19 19:42
jannauack
#asahi-dev · 2026-01-19 19:38
jannausven: atc + cd321x trace is sufficient for the optical cable
#asahi-dev · 2026-01-19 14:58
jannausee a8000096874b using "select" because other KMS driver use it
#asahi-dev · 2026-01-19 14:54
jannaunoopwafel: I think I added that dependency (or select) in the last days
#asahi-dev · 2026-01-18 23:25
jannaudoesn't really explain any issues in linux though as the base m3 boots fine. m1n1 handles it automatically
#asahi-dev · 2026-01-18 23:23
jannaufor the base m3 as well, I haven't noticed that before
#asahi-dev · 2026-01-18 23:22
jannaufl0_id___: it's expected for m3 pro/max. dram starts at 0x10000000000 as noopwafel said
#asahi-dev · 2026-01-18 16:34
jannauthe initial baudrate is 115200. if the proxyclent doesn't receive a reply it assumes it has already switched to 1.5 Mb
#asahi-dev · 2026-01-18 16:07
jannauit is still 0xc on m3 so ~24 MHz
#asahi-dev · 2026-01-18 16:04
jannauI doubt that t8132 is too slow for 1.5M baud
#asahi-dev · 2026-01-18 16:03
jannauyuka: https://paste.centos.org/view/4dc54de9 disables the baud rate switch
#asahi-dev · 2026-01-18 15:39
jannauthat sounds if there is nothing on the uart. either m1n1 is broken or it fails to switch the remote port to debug
#asahi-dev · 2026-01-18 15:38
jannauyuka: what does fail? a proxy noop command or the baud rate switch?
#asahi-dev · 2026-01-18 14:26
jannaunvme coproc crashes on m3/14.8.3
#asahi-dev · 2026-01-18 12:17
jannaunickchan: I guess the point is moot if we do dynamic properties anyway. I was my assumption
#asahi-dev · 2026-01-18 12:16
jannauyes, it switches by default to 1.5M
#asahi-dev · 2026-01-18 12:07
jannauextending the list static array would be possible. I doubt the property list needs to be sorted in a particular way. also there is another end. Not serious about this. at this point the dynamic list is preferable
#asahi-dev · 2026-01-18 12:05
jannaudynamic allocation is ok, I was only looking at the code in the patch where it's not necessry
#asahi-dev · 2026-01-18 12:02
jannauintegralpilot: ack. take your time. it took v3 for me to actually looking at it so no hurry
#asahi-dev · 2026-01-18 10:46
jannauwith m1n1 but might be an m3 issue as it does work with a m1 device. possibly different uart clock
#asahi-dev · 2026-01-18 10:34
jannaulooks like switching the baudrate to 1.5M on the hw uart broke. this is likely broken with CS anyway
#asahi-dev · 2026-01-17 20:21
jannauit broke while updating from a linux 6.13 based branch to 6.18 / 6.19-rc / linux-next? are tipd and atc-phy are identical? any relevant changes in dart?
#asahi-dev · 2026-01-17 19:56
jannauyes, installer went through
#asahi-dev · 2026-01-17 19:49
jannauinstall seems to work now after upgrading the main os to 15.7. I suspect the installer wanted newer system firmware/recovery and was not able install it itself
#asahi-dev · 2026-01-17 19:00
jannauyes, please do. that was the main objective. I just realized that macvdmtool and the i2c userspace tuxvdmtool would do mostly the same
#asahi-dev · 2026-01-17 18:49
jannau14.8.3, ventura 13.5 failed as well, I'll update the main os from 15.0
#asahi-dev · 2026-01-17 18:31
jannauI'm installing ventura now and see if I can upgrade
#asahi-dev · 2026-01-17 18:30
jannauthis is during the install. creating the install media works fine and the same usb stick worked on m3. the installer writes quite a bit onto the volume
#asahi-dev · 2026-01-17 18:26
jannausigh, did apple break installing Sonoma on M2 devices? usb install media installer fails aftyer a while with "failed to download insteller asset (SFR)" and ask to check the internet connection. once with wifi, once with lan
#asahi-dev · 2026-01-17 17:09
jannaunot that many changes in v6.12..v6.18 ignoring new intel platforms documentation and debugfs changes
#asahi-dev · 2026-01-17 16:56
jannauno, unifying receiver survived on the non-DP port as well
#asahi-dev · 2026-01-17 16:53
jannaubehaviour on 6.18 might be explained by the additional always on power-domain for the DP enabled port
#asahi-dev · 2026-01-17 16:52
jannaume too but a logitech unifying receiver dongle survives on both 6.17/6.18, the usb 2.0 hub of my usb3/dp-alt hub survives on 6.17 but not 6.18
#asahi-dev · 2026-01-17 16:40
jannauoh, usb 1.1/2.0 devices sometimes survived suspend/resume. I wasn't aware and I replugged my yubikey always over suspend/resume
#asahi-dev · 2026-01-17 13:12
jannauthe main issue is that you can't map disjoint 4k pages continuously. 4k aligned start/end is supported via the unused sub page protection flags. devices/iommu's would need a flag only use 16k folios for me
#asahi-dev · 2026-01-17 12:39
jannauyuka: it does not. the interactive control and printing breaks it. someone wanted to rewrite cs firmware so that it offers a transparent serial as well but I don't remember why and haven't heard of it again
#asahi-dev · 2026-01-17 09:14
jannaunoopwafel: I think nvme should work with 14.x. the breaking isssue is 15.x

plus ›