https://en.wikipedia.org/wiki/Server_Base_System_Architectur...
There's an effort to make even the Raspberry Pi support this standard: https://rpi4-uefi.dev/
Reading my way through the specification at the moment, and I'm failing to see how UEFI does anything user-friendly at all. It seems to only be useful to entrenched business interests (read Big *) and to a lesser extent maybe OEM implementers. Whereas all the cryptographic subsystem utilization by industry seems to be being used against users in the interests of fortifying market position.
Wish I'd have added my voice to the din back when I was first reading about it back in the oughts. Didn't realize how much of a pain in the rear it was about to make my computing life.
Too late to turn back the clock now. I just wish I understood what was so wrong with the old BIOS POST->handoff process.
Probably need to sit down with an Old HP or Dell XP box and try to figure that out. Besides the Rootkit issue (which frankly, it feels like there are less intrusive and user-abuse enabling approaches to dealing with) I don't buy that the end-user got a single blessed thing out of UEFI; only lost.
They didn't really follow the specifications so there were a lot of differences, but it was definitely UEFI. Actually, one of the reasons Hackintosh bootloaders have gotten so much better recently is they don't need to deal with BIOS ==> EFI translation.
So clearly Apple saw something in it.
>The Unified Extensible Firmware Interface Forum or UEFI Forum is an alliance between several leading technology companies to modernize the booting process. The board of directors includes representatives from thirteen "Promoter" companies: AMD, American Megatrends, ARM, Apple, Dell, Hewlett Packard Enterprise, HP Inc., IBM, Insyde Software, Intel, Lenovo, Microsoft, and Phoenix Technologies.
https://en.wikipedia.org/wiki/Unified_EFI_Forum
Apple started their adoption of EFI before the UEFI was a thing.