Comment on Hyundai car requires $2000, app & internet access to fix your brakes - what the actual f
user224@lemmy.sdf.org 1 week agoBiggest issue is whatever is going on with mobile devices compared to desktop. I don’t know what you call it here, drivers? But each device is just so closed down, you can’t “just run” another software on it. I imagine if desktops also each required custom images based on model, people would only be using unmodified pre-installed Windows.
ApertureUA@lemmy.today 1 week ago
Oh, see, unlike on x86 where you have the ACPI to detect hardware with minimal device quirks (still a lot of them), everything else doesn’t have that. Well, except some Qualcomm chips, but their implementation sucks and basically only works reasonably with Windows and Windows Phone. So you need a device tree blob (DTB) to tell the kernel where everything is. But enabling all of the drivers in a single kernel build makes it not fit (the partition for that is traditionally quite tight), so you make different kernels per device.
AND, on Android in particular, lots of features need device specific configuration for all of the small stuff like the proximity sensor and the cameras (a LOT more complex than webcams). There’s GSI, which basically forces the OEM to write drivers and all of that with a stable-ish API to make universal images possible, but it results in a system with lots of tint inexplicable problems that slowly make you loose your sanity in my experience.
How postmarketOS handles it is that there are basically meta packages per device that depends on the kernel package appropriate to the device (sometimes for a whole platform or SoC, having multiple DTBs inside for each device) that flashes itself to the appropriate partition via a post installation hook, as well as all of the config files for apps that need device specific stuff and don’t already have it upstream (like camera apps).