#asahi-re · 2025-11-13 08:15
graphine27do you know the sequence to disable the quircks?#asahi-re · 2025-11-12 21:46
graphine27I will try to trace what T2 does, if m1n1 can work correctly when booted via pongo I should be able to fully trace it#asahi-re · 2025-11-12 21:44
graphine27It would be an option yes, but I was interested if the T2 way would work for bare metal functionality#asahi-re · 2025-11-12 21:40
graphine27Yes. Although I suspect T2 could have done it over thunderbolt, like when using the target disk mode you could see the ssd name #asahi-re · 2025-11-12 21:38
graphine27Being able to use NVMe in the standard way would make things much easier#asahi-re · 2025-11-12 21:37
graphine27Trying to enable the hardware on a different platform where the driver framework is not as flexible as linux#asahi-re · 2025-11-12 21:36
graphine27I'm guessing the quircks also can't be disabled on M1#asahi-re · 2025-11-12 21:35
graphine27In the first NVMe patch I read this about T2: disable some quirks (the NVMMU and the weird submission array) and then exposes it over a PCIe interface. #asahi-re · 2025-11-12 21:31
graphine27I was hoping this would be possible sice T2 can do it, but chances are pretty low.#asahi-re · 2025-11-12 21:30
graphine27From what I've seen CreatePCIeUPDARTMapping is one of the functions used and it's present in M1 kexts as well. But some other things are missing from dt like mapper-pup-ans2 or apcieup-fn-nub-ans2#asahi-re · 2025-11-12 21:28
graphine27nickchan: do you know if it would be possible for M1 chips to make the ANS controller available over PCIe like T2?