3 ms·
For what it's worth, Apple's UEFI firmware is likely not compliant because they began using EFI before it was standardized. You can blame them for not updating
by Wowfunhappy 8mo ago
For what it's worth, Apple's UEFI firmware is likely not compliant because they began using EFI before it was standardized. You can blame them for not updating it later, but I can understand why they didn't; it was working.
- DiabloD3 8mo agoThey were using OpenFirmware, the standard that EFI is built on, but their first x86 CPU was a Core 1 iirc, which had shipped with a UEFI on real PCs.
- LargoLasskhyfv 8mo agoAre you sure their early EFI contained anything from OpenFirmware, except for conceptual inspiration, maybe?
- DiabloD3 8mo agoIntel wanted to rip OpenFirmware off and wanted to EEE it without paying lip service to Sun et al. It isn't an accident that both, for example, use Forth.
- LargoLasskhyfv 8mo agoThat's why I've asked? Where is the FORTH in EFI, or any UEFI, for that matter?
- DiabloD3 8mo agoLook up "UEFI shell" for your vendor. Sometimes this is an unlisted F key, sometimes its as simple as selecting it as which OS you want to boot, sometimes it will happen automatically if no boot device is discovered, sometimes you must supply it as a bootx64.efi from the vendor (or from Tianocore). Just because UEFI is a standard doesn't mean all the vendors don't smoke crack.
- LargoLasskhyfv 8mo agoThat's only a shell/repl, implementing a DSL for boot-related stuff. It isn't implemented in FORTH, it does not execute or understand FORTH, or use it for anything. It's not there. It just occupies a similar role in a similar place, of what some FORTHs on some systems once did. Mainly OpenBoot on SUNs and some PPC Apples, while having nothing from their internals. Having the ability to type some commands in your firmware/BIOS/UEFI, like it has been the case on Sparcs by SUN, PPC Macintosh by Apple, or the OLPC doesn't make it a FORTH. https://en.wikipedia.org/wiki/Open_Firmware https://en.wikipedia.org/wiki/Open_Firmware