#asahi-dev · 2026-08-02 20:06
yukaCan someone with a t8103 test this on 26.6 FW: https://github.com/AsahiLinux/m1n1/pull/648#asahi-dev · 2026-08-02 14:28
yukasince we changed cwd12 = 1 -> cwd12 = 0, nvme_read() works fine without APPLE_ANS_PRP_NULL_CHECK on old and new firmware. which does not make sense with the comment in the kernel driver?#asahi-dev · 2026-08-02 14:07
yukaand if not having it is strictly a problem#asahi-dev · 2026-08-02 14:06
yukabut what APPLE_ANS_PRP_NULL_CHECK _actually_ does is still a mystery to me#asahi-dev · 2026-08-02 14:05
yukaEverything points to 15.x+ fw being simply missing APPLE_ANS_UNKNOWN_CTRL and behaving as 14.x without clearing APPLE_ANS_PRP_NULL_CHECK#asahi-dev · 2026-08-02 14:04
yukanvme is annoying too. The comment on APPLE_ANS_UNKNOWN_CTRL in the kernel driver is very confusing, and does not match what I can observe anywhere.#asahi-dev · 2026-08-02 14:03
yukasomehow b4 sent out an old version of the cover letter. the changes probably lost when doing the patch dependencies things.#asahi-dev · 2026-08-02 10:50
yukaMaybe because the heat wave is over, the quantum effects have come down to a level that is favorable (/s)#asahi-dev · 2026-08-02 10:43
yukasven: I haven't seen the "trying to write to read-only [...]" since a few weeks now, but it depends very much on the kernel config used. I guess I would need to try some kernel with fedora config to make a definite statement#asahi-dev · 2026-08-02 09:49
yukahttps://github.com/yuyuyureka/m1n1/commit/fd8832414172cf62b1396c73eacbf6ec08524192#diff-c4e733aec75a764a3a50d6181197db87e4c846891af23dec962b9592e96c858cR4-R352#asahi-dev · 2026-08-02 09:48
yukaI read somewhere that the nvme stuff changed starting from 15.x, so I was about to check if the changes I made for 26.6 also work on 15.x so that I can use the correct conditional#asahi-dev · 2026-08-02 09:47
yuka26.6 is good on M4* and A18 Pro. 27.x will probably be required for M5*#asahi-dev · 2026-08-02 09:46
yukaAh ok#asahi-dev · 2026-08-02 09:45
yukaWhich 15.x version would we attempt to use for M3 Ultra?#asahi-dev · 2026-08-01 23:09
yukaT8132/T6040 pcie is super annoying. On T8132 the ethernet no longer wants to show up at all, while on T6040 it appears followed by "link down" and failed to change from D3hot to D0? I still didn't try if port 0 actually works for wifi. I now have a trace for T8132 too and identified some differences but adapting for those didn't help.#asahi-dev · 2026-08-01 22:01
yukaSent one remaining design question regarding it to the ML. If you have any thoughts on it, please reply there to keep the context on list: https://lore.kernel.org/asahi/03eb4c22-045e-470e-8259-ebf9b1cfe2ed@cyberchaos.dev/T/#u#asahi-dev · 2026-08-01 21:59
yukaI communicated with IntegralPilot that I will try to send out the next version of the mtp keyboard series, since he is short on time#asahi-dev · 2026-08-01 21:42
yukasent#asahi-dev · 2026-08-01 21:13
yukaack#asahi-dev · 2026-08-01 21:12
yukabut that's really the question. my change touches the same file as the m3 pro/max one which was already appplied in pinctrl, and I can make my patch either depend on that, or conflict with that.#asahi-dev · 2026-08-01 21:11
yukaOr that#asahi-dev · 2026-08-01 21:07
yukaAnd then, whoever merges apple-soc will have to resolve conflicts with pinctrl#asahi-dev · 2026-08-01 20:57
yukaThe alternatives would be linux-next as base-commit and only the M3 Pro/Max v3 as additional dependency, or apple-soc as base and the two dt-bindings commits as dependencies#asahi-dev · 2026-08-01 20:55
yukaSo I use 7.2-rc5 as base-commit and then add the two dt-bindings and M3 Pro/Max v3 as additional dependencies?#asahi-dev · 2026-08-01 20:38
yukaI will look into that, thanks#asahi-dev · 2026-08-01 20:31
yukashould I base apple-m4-initial-devicetrees v2 on linux-next or apple-soc?#asahi-dev · 2026-08-01 16:58
yuka"u.cpu_features.apple_sysregs_unlocked"#asahi-dev · 2026-08-01 16:57
yukaAnd that's also integrated into the proxyclient utils#asahi-dev · 2026-08-01 16:57
yukaisn't that just cpu_features->apple_sysregs_unlocked?#asahi-dev · 2026-07-31 21:50
yukareally nice how far you got!#asahi-dev · 2026-07-31 21:50
yukanight#asahi-dev · 2026-07-31 20:47
yukais this with hardware gxf or emulated gxf?#asahi-dev · 2026-07-29 16:45
yukaalso conditional to t602x#asahi-dev · 2026-07-29 16:45
yuka0x594004080 (apcie[10], offset 0x80) = 0x1#asahi-dev · 2026-07-29 16:45
yuka0x59400c020 (apcie[7], offset 0x4020) = 0x3#asahi-dev · 2026-07-29 16:45
yukaand these:#asahi-dev · 2026-07-29 16:42
yukaat least the ltssm stuff which is conditional to t602x#asahi-dev · 2026-07-29 16:41
yukaI believe there is a part of pcie init missing on t8122, judging by this trace: https://noopwafel.net/asahi/pcie_m3_trace_notes.txt#asahi-dev · 2026-07-29 16:41
yukaor was that just a pwren thing#asahi-dev · 2026-07-29 16:41
yukajannau: the sd card reader was not working for you on t8122/t6030, right?#asahi-dev · 2026-07-28 22:02
yuka~all?#asahi-dev · 2026-07-28 22:02
yuka> And that are wanted?#asahi-dev · 2026-07-28 21:48
yukaso 26.6 has it unlocked on all M4* :)#asahi-dev · 2026-07-28 18:34
yukaI think it's just not upstreamable because of the offset is hardcoded and might change#asahi-dev · 2026-07-28 18:34
yukaah yes that should work as well#asahi-dev · 2026-07-28 18:30
yukarecount_base is still required, but init_base and config_base are now integrated into m1n1#asahi-dev · 2026-07-28 18:28
yukaiirc 1/3 of the manual patches are still required#asahi-dev · 2026-07-28 18:25
yukais remote access to one helpful to get started?#asahi-dev · 2026-07-27 09:20
yukasome tweets indeed state that t600x was moved in 26.4, while t8103 is moved in 27.0#asahi-dev · 2026-07-26 22:38
yukamake sure you get the one with "fix cdw12 value to read 1 block", I just pushed it