On a legacy BIOS system the firmware-OS hand-off happened in 16-bit real mode, and the OS was expected to transition to 32/64-bit protected mode. This is reflected in firmware provided for 32/64-bit platforms (ex: MinnowBoard MAX*) or 32-bit platforms (ex: Intel® Galileo & MinnowBoard*). Because most Intel platforms support both 32-bit & 64-bit architecture, along with old school Intel 8086/80286 16-bit instructions, the UEFI firmware on these platforms can be compiled in IA32 or 圆4 mode. The "x86 compatible" processor is a bit different, and can switch into various 16/32/64 bit modes for application compatibility. For most non-Intel processors, this isn't a big deal since they only have one architecture. The main thing we need to understand is a core concept of the UEFI Specification: the OS and firmware architecture need to match. ![]() ![]() Why would a system with a 64-bit Intel processor ship with 32-bit UEFI? Why can't I get Linux* on a 32-bit UEFI system? The answer, as with many things, involves money. For years I've been getting questions about the UEFI implementation found on many low-cost tablets and 2-in-1 platforms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |