Asahi Linux for M1 Macs: progress report for September 2021
&gt; <i>The NVMe hardware in the M1 is quite peculiar: it breaks the spec in multiple ways, requiring patches to the core NVMe support in Linux, and it also is exposed as a platform device instead of PCIe. In addition, it is managed by an ASC, the “ANS”, which needs to be brought up before NVMe can work, and that also relies on a companion “SART” driver, which is like a minimal IOMMU.</i><p>Stuff like this makes me wonder: why does Apple do this?  If I try to give them the benefit of the doubt, I can assume that these changes are done for performance, cost, power-saving, or maybe even security reasons.  Otherwise it just seems like Apple does these things in order to make it harder for other OSes to run on their hardware.  Which is certainly their prerogative, but it just makes me think less of them.<p>On the other hand, this is really cool:<p>&gt; <i>However, Apple is unique in putting emphasis in keeping hardware interfaces compatible across SoC generations – the UART hardware in the M1 dates back to the original iPhone! This means we are in a unique position to be able to try writing drivers that will not only work for the M1, but may work –unchanged– on future chips as well.</i><p>... but cynically (or perhaps just <i>realistically</i>), I can easily believe that this isn&#x27;t done for reasons of openness, but because this makes maintenance of macOS itself easier for Apple.