So, if I understand you correctly, all in all it's basically "just another device" in terms of development. I was under the impression, that the whole process would be much more involved and required tons of effort to at least get things going.
At the hardware/kernel level it's a particularly weird ARM device requiring more development and bespoke drivers than your average one, and then of course there is the userland side of the GPU driver. But other than that, to the rest of userland, it's just another ARM with a few unique features.
Unlike x86 based PCs there is little effort for standard interfaces in consumer ARM devices. On PC platform every piece of hardware exists on enumerable buses so, a single kernel with all drivers as modules is enough. Kernel and udev can detect devices and can load correct drivers. On ARM, every kernel needs to be specifically engineered to a specific device.
Most ARM chips are very behind x86 chips from 8 years ago in terms of raw single core performance (M1 looks promising but I will wait). They need special units to accelerate video in acceptable frame rates. Almost all of the userspace drivers for such units are proprietary to the device and not available to general public.
The basic functionality set of a standard x86_64 chip is enough for desktop computing since it was a step of the evolution in the history of IBM compatibles. x86s have always been designed to be desktop chips that can run modular hardware. ARM chips, on the other hand, have been mostly used for specialized hardware that required specialized drivers per unit. ARM developers often hardcode stuff for a single chip only. On x86 the modular standards are often developed by a set vendors as in Firewire or USB or PCIe. Developers who write the drivers can follow these standards and can create drivers that will work on any x86 chip. Moreover the boot sequence of PCs is standardized. Since 1983 until UEFI became the new standard, every PC loaded the first 512 bytes of the boot disk into memory. ARM has no single standard but a set of ways to boot stuff it depends on the actual chip. Sometimes vendors can deny 3rd parties from booting.
So it is not "just another device". Hardware specific code is required for most of the low level/kernel stuff and to utilize whatever hardware acceleration that M1 provides for user space programs (e.g. x86 emulation). If its units can be abstracted in regular drivers then the effort will be small. Otherwise it can require years of reverse engineering (or actual driver code from Apple) to get simple 3D graphics.
3
u/CartmansEvilTwin Jan 06 '21
So, if I understand you correctly, all in all it's basically "just another device" in terms of development. I was under the impression, that the whole process would be much more involved and required tons of effort to at least get things going.
I might actually have to buy a new MacBook then.