UEFI Specification
Every modern x86-64 and AArch64 server, workstation, and PC uses UEFI. Required for OS development, bootloader work (GRUB, systemd-boot, shim), Secure Boot policy, and firmware engineering.
What It Defines
Defines the firmware interface between platform firmware and OS boot loaders on x86-64, AArch64, RISC-V, and other architectures. Covers boot services (EFI protocols, memory map, device path, GOP graphics output), runtime services (UEFI variable store, GetTime, ResetSystem), Secure Boot (image authentication via PE/COFF signatures and the Secure Boot key hierarchy: PK, KEK, db, dbx), the UEFI Shell, and the UEFI driver model for platform initialization.
Canonical (Normative)
Related References
Industry consortium (Intel, AMD, ARM, Apple, Microsoft, HP, Dell, AMI, Phoenix) that owns and maintains the UEFI Specification and ACPI Specification. UEFI replaces legacy BIOS as the firmware interface for all modern x86-64, AArch64, and RISC-V platforms. ACPI defines OS-directed power management and hardware configuration via descriptor tables and AML bytecode.
Related Specs
ACPI is how every OS discovers hardware topology, manages CPU power states, handles thermal throttling, and receives platform events. Required for kernel, power management, and firmware development on all modern x86/Arm platforms.
SMBIOS is how software reads hardware inventory: CPU model, RAM config, system UUID, and BIOS version. Cloud hypervisors inject SMBIOS tables to identify instance type; asset management tools harvest them for CMDB population.
TPM 2.0 is the hardware root of trust for modern Secure Boot, disk encryption, remote attestation, and zero-trust device health verification. Understanding it is essential for enterprise security architecture and cloud confidential computing.