4 ms·
This doesn't make any sense. AFAICT, the only widespread ARM OS to require UEFI -- Windows RT -- is also Microsoft's biggest lead balloon since Bob. And UEFI do
by bitwize 13y ago
This doesn't make any sense. AFAICT, the only widespread ARM OS to require UEFI -- Windows RT -- is also Microsoft's biggest lead balloon since Bob. And UEFI doesn't really fix the problem that ARM has for distros: there's no well-understood, standard way to go from power on to starting a kernel. It doesn't fix it because the same is true for UEFI. Each implementation is slightly different, and can do different things.
- mjg59 13y agoAll UEFI implementations have a minimal level of functionality, and a well defined way of passing control off to the OS. You're guaranteed that it can read a FAT filesystem, and you're guaranteed that if you put the path to a UEFI executable in the default boot variable that that executable will be run on boot.
- wmf 13y agoBoot variables are kind of a PITA, especially if you're not used to them because they didn't exist in the BIOS world.
- mjg59 13y agoYou've got two choices as far as bootloader design goes. You can put the bootloader in a well-known location (such as in the first 512 bytes of a drive), or you can tell the firmware where to look. UEFI actually supports both, but the problem with using a well-defined location is that you inevitably have conflicts between different OSes wanting to use the same location. Boot variables are well-defined and work just fine, except in the small number of cases of vendors who have implemented something that's not actually UEFI.