3 ms·
That's not what makes a PC. A PC has a bunch of standard hardware, a VGA/VESA interface, a console, a legacy BIOS or newer UEFI. Android phones have NONE of th
by djsumdog 10y ago
That's not what makes a PC. A PC has a bunch of standard hardware, a VGA/VESA interface, a console, a legacy BIOS or newer UEFI.
Android phones have NONE of this. Google could force this. Their "Open Handset Alliance" is not at all open. It's a closed lock in system to keep all their manufactures from ever making Amazon phones.
Google has a vested interested in selling more phones. They could easily require standardization. They could ban binary blobs. They could require all manufactures to make their kernel patches and drivers upstreamable and meet Linux kernel standards. But they don't.
You can take a 32-bit x86 Linux distro from today and run it on an old Pentium. You can take a really old 32-bit distro from years ago and run it on a modern machine (of course very little of the hardware will work, but it should boot in legacy mode...okay, okay it might not boot, but if it does boot you will get a console I/O).
It has nothing to do with the phone and has to do with the fact that ARM is not an architecture. It's a SoC sold to tons of manufactures who all connect whatever they want to onto whatever pins they want to. Yes yes, there are things like Device Tree configs, but name a phone that supports them (no seriously, I'm asking. Are there any? Like I would want to buy/experiment with them if they exist).
Every ARM device seems to have a totally different base image and this isn't maintainable. We need a standard device/IO configuration system so that you can install standard AOSP + drivers onto any phone just like we can with Windows:
http://penguindreams.org/blog/android-fragmentation/ http://penguindreams.org/blog/android-fragmentation/