<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Well, somewhat.</div><div class=""><br class=""></div><div class="">The main reason that UEFI32 and UEFI64 firmware exists is because when Bay Trail processors debuted, there were bugs in Windows 8.1 that caused Bay Trail SoC to bug out, particularly in the new “InstaGo” sleep states built by Microsoft that bypassed ACPI standards.</div><div class=""><br class=""></div><div class=""><div class="">Those were later fixed in Windows 8.1 Update. However, since systems had to be built/planned long before 8.1 Update, they debuted with UEFI32. Most Bay Trail tablets today still ship with UEFI32 as a result.</div></div><div class=""><br class=""></div><div class="">GRUB2 has broken the 64-bit barrier with UEFI32. You often can also run 32-bit UEFI binaries from UEFI64 firmware too. However, you will be limited to 32-bit mode.</div><div class=""><br class=""></div><div class="">My team, for example, supports MinnowMax only with UEFI64 firmware on Console OS. I’m testing our RTM Developer Release 1 build on one this hour. However, we are still actively planning to support UEFI32 for other devices, hopefully by year’s end.</div><div class=""><br class=""></div><div class="">GRUB2 was the first Linux bootloader that successfully loaded up 64-bit operating systems using UEFI32 firmware. This functionality made its most major debut in Ubuntu 14.10 in tandem with improvements in Kernel 3.16 that facilitated this state changing. </div><br class=""><div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div><div style="font-size: 12px; text-align: -webkit-auto;" class="">Christopher Price</div><div style="font-size: 12px; text-align: -webkit-auto;" class=""><a href="http://ConsoleOS.com" class="">ConsoleOS.com</a> - iConsole.tv</div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Nov 8, 2014, at 7:26 AM, Peter Ogden <<a href="mailto:peter.j.ogden@gmail.com" class="">peter.j.ogden@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">UEFI can
only work when the OS and Firmware are matched on what the architecture
is. This means a 32-bit OS cannot be run from a 64-bit Firmware, and
vice versa: </div></div></div></blockquote></div><br class=""></body></html>