#asahi-dev · 2026-07-03 22:39
yukaenverbalalic: the part which isn't fully documented yet: you need to build m1n1 with USE_DEBUG_USB (comment in the line in config.h) and install this as custom boot object (like described in the m1n1 user guide)#asahi-dev · 2026-07-03 22:26
yukajannau: and now, after the rebase, I have your enter_kis code and can confirm it works over the existing spmi transport code of the PR#594#asahi-dev · 2026-07-03 22:23
yukajannau: my own code had weird failure modes, LOCK didn't error, but also didn't work properly, possibly what you are now solving with the "... and soft reset if it fails"#asahi-dev · 2026-07-03 22:22
yukajannau: when I last tried this, the entire code for enter_kis didn't exist, and I came up with my own#asahi-dev · 2026-07-03 21:40
yukahttps://github.com/AsahiLinux/m1n1/pull/594#issuecomment-4879423855#asahi-dev · 2026-07-03 21:40
yukaStanfordAppliedCyber: this might be interesting for you too, the Neo can now self-enter debugusb and as such you don't need a second mac#asahi-dev · 2026-07-03 21:27
yukaWhatever jannau did for the i2c version of "tps6598x: Add compile time config to enable debugusb", it also fixes it for spmi#asahi-dev · 2026-07-03 19:51
yukanow I got "Unable to handle kernel write to read-only memory at virtual address" for the first time on the Neo :(#asahi-dev · 2026-07-03 19:51
yukaOh wow#asahi-dev · 2026-07-03 19:27
yukaso for now no pmgr#asahi-dev · 2026-07-03 19:27
yukaI will have to confirm this on 26.5.1 on monday when I'm back home and have physical access to the machine#asahi-dev · 2026-07-03 18:49
yukaI commented out arch_counter_enforce_ordering and disabled the "Enhanced Counter Virtualization" feature, to simplify the code even further#asahi-dev · 2026-07-03 18:48
yukahttps://x0.at/t32Y.txt#asahi-dev · 2026-07-03 18:47
yukathe pc is at "mrs x0, cntpct_el0" but m1n1 can read CNTPCT_EL0 just fine#asahi-dev · 2026-07-03 18:34
yukaarch_counter_get_cntpct seems to be quite simple#asahi-dev · 2026-07-03 18:33
yukaI think this might be caused by iBoot updates/changes, but not 100% sure#asahi-dev · 2026-07-03 18:28
yukabut now I crash at arch_counter_get_cntpct+0xc/0x28#asahi-dev · 2026-07-03 18:28
yukaI'm quite sure I had pmgr on t8140 working before#asahi-dev · 2026-07-03 14:50
yukabut have different midr part numbers#asahi-dev · 2026-07-03 14:49
yukaM5 Pro and M5 Max are both t6050#asahi-dev · 2026-07-03 14:49
yukat6000 vs t6001, t6020 vs t6021, t6040 vs t6041#asahi-dev · 2026-07-03 14:49
yukabut on M1/M2/M4, Pro and Max were still different SoC ids#asahi-dev · 2026-07-03 14:48
yukagood to know#asahi-dev · 2026-07-03 14:48
yukaokayy#asahi-dev · 2026-07-03 14:48
yukaso they use the same device tree, and then m1n1 detects the disabled cores?#asahi-dev · 2026-07-03 14:47
yukaand were they both j314s too?#asahi-dev · 2026-07-03 14:46
yukaAs counter-example, M3 Max (14-core) is t6034 while M3 Max (16-core) is t6031#asahi-dev · 2026-07-03 14:46
yukaWas there any machine with different variants (cpu core count) but using the same SoC designation?#asahi-dev · 2026-07-03 14:32
yuka* on the other end#asahi-dev · 2026-07-03 14:32
yukathey are semi broken, don't work with high baudrates, or even at all depending on which other macbook or serial chip you have on the other devices#asahi-dev · 2026-07-03 14:31
yukaand these quirks are the reason I believe we should no longer consider debuguart the main serial console for those devices#asahi-dev · 2026-07-03 14:31
yukawith M2 <-> M4 Pro#asahi-dev · 2026-07-03 14:31
yukaflokli had the same#asahi-dev · 2026-07-03 14:31
yukaM5 Pro <-> M1 Pro also wasn't able to get any trace of serial#asahi-dev · 2026-07-03 14:30
yukanot all debuguarts work with all debuguarts#asahi-dev · 2026-07-03 14:30
yukaenverbalalic yes, you were using an M2 Macbook on the other end I believe?#asahi-dev · 2026-07-03 14:27
yukaI might send some very minimal M4* and A18 Pro device trees soon then. I would wait longer for M5 since there are still devices being released with that and I'm getting headaches from the M5 Pro / M5 Max. Iirc the M5 Max I had on hands a few months ago advertised as t6050, same as my M5 Pro.#asahi-dev · 2026-07-03 14:22
yukaeven it's not in the device tree#asahi-dev · 2026-07-03 14:22
yukawell you can always add an earlycon=#asahi-dev · 2026-07-03 14:20
yukawhat do you run on those devices anyways? pmOS?#asahi-dev · 2026-07-03 14:16
yukathere's no need to hurry any of this, but the path towards it would be dockchannel merged upstream -> dockchannel-uart proposed -> initial A18 Pro / M5* dts with dockchannel-uart#asahi-dev · 2026-07-03 14:14
yukaExactly#asahi-dev · 2026-07-03 14:14
yukaAnd I don't think we should use it anymore#asahi-dev · 2026-07-03 14:14
yukait needs at least a new compatible#asahi-dev · 2026-07-03 14:13
yukaThe samsung serial is very weird on A18 Pro / M5*#asahi-dev · 2026-07-03 14:13
yukaThat's the thing#asahi-dev · 2026-07-03 14:13
yukano?#asahi-dev · 2026-07-03 14:13
yukawell it's in upstream#asahi-dev · 2026-07-03 14:11
yuka(as in, for each device: this boots / does not boot in single core / smp, ...)