EFI

EFI
Name	EFI
Developer	Intel Corporation
Initial release	1998
Operating system	Microsoft Windows, macOS, Linux, FreeBSD
Genre	Firmware, bootloader, runtime services

EFI EFI is a modern firmware interface specification that defines a software environment between an operating system and platform firmware. It was designed to replace legacy interfaces provided by IBM PC/AT architecture BIOS implementations and to support advanced features required by contemporary Microsoft Windows and macOS platforms. Major industry vendors and standards bodies adopted the specification to enable richer pre-boot environments for Intel Corporation-based systems, server platforms such as Dell EMC and Hewlett-Packard, and open-source operating systems like Linux.

Overview

The specification provides standardized boot services, runtime services, and a modular driver model to initialize platform hardware for operating systems such as Microsoft Windows, macOS, and Linux. EFI supports device discovery, executable formats, and a persistent configuration database used by vendors including Intel Corporation, American Megatrends, Phoenix Technologies, and Dell EMC. The interface enables graphical boot managers used by projects such as rEFInd and by vendors including Apple Inc. on Macintosh hardware.

History and Development

Work on the specification began at Intel Corporation in the mid-1990s to supersede the legacy firmware used on IBM PC/AT architecture systems. The original specification, often associated with the Intel Architecture, evolved through collaborations between Intel Corporation, Microsoft Corporation, and platform vendors including Compaq and Hewlett-Packard. The specification was later published and extended under the auspices of consortia that included hardware manufacturers such as Dell EMC and firmware vendors like Phoenix Technologies. Subsequent revisions influenced the development of the Unified standard adopted by many server and client vendors and shaped boot processes used by Apple Inc. for Macintosh transitions.

Technical Architecture

The architecture defines boot services for loading and starting application images and runtime services available after an operating system has taken control. It specifies an executable image format compatible with Intel 64 and x86 processors and mandates a table-driven configuration visible to pre-boot applications and operating systems. Modular driver models allow vendors such as American Megatrends to provide platform-specific drivers, while boot managers like rEFInd implement user interfaces and filesystem drivers for formats including FAT used by removable media. The specification interoperates with secure boot components, cryptographic services, and platform configuration registers supported on systems from Dell EMC, Hewlett-Packard, and Apple Inc..

Implementations and Platforms

Major firmware vendors implemented the specification across product lines: American Megatrends integrated it into desktop and server BIOS replacements; Phoenix Technologies provided implementations for laptops sold by HP Inc. and Lenovo; Intel Corporation included reference firmware for development platforms; and Apple Inc. shipped tightly integrated firmware on Macintosh systems. Open-source implementations such as Tianocore (EDK II) offered a reference codebase used by projects including Coreboot to support platforms from ASUS, Gigabyte Technology, and Supermicro. Server platforms from Dell EMC and Hewlett-Packard used certified firmware stacks to meet enterprise deployment requirements.

Configuration and Usage

Configuration interfaces include vendor-supplied setup utilities and EFI shell environments used by system administrators and integrators. Administrators on systems from Dell EMC, Hewlett-Packard, and Lenovo interact with firmware variables and boot order entries to control startup behavior for Microsoft Windows Server or Linux distributions. Boot managers from rEFInd and projects derived from Tianocore are used by enthusiasts and OEMs to present graphical menus, manage kernel parameters for Linux distributions, and chainload legacy loaders from vendors such as Microsoft Corporation.

Security and Vulnerabilities

The specification includes mechanisms for authenticated boot chains and key management used by Microsoft Corporation's signed boot model and by OEM implementations on Apple Inc. systems. Vulnerabilities have been discovered and patched in vendor firmware from American Megatrends, Phoenix Technologies, and platform vendors including Dell EMC and Hewlett-Packard; these include privilege escalation and persistent bootkit techniques documented by independent researchers and remediation via signed firmware updates. Security features such as Secure Boot, measured boot, and cryptographic validation depend on platform key provisioning practices used by vendors like Microsoft Corporation and Apple Inc..

Compatibility and Migration

Migration from legacy IBM PC/AT architecture firmware required coordination among OS vendors, hardware manufacturers, and firmware suppliers such as Intel Corporation and American Megatrends. Operating systems including Microsoft Windows, Linux, and FreeBSD implemented support for the interface to enable features like native GUID Partition Table handling and driver load at boot time. Transitional tools and boot managers like rEFInd and projects derived from Tianocore assist deployments when moving from legacy BIOS-based systems produced by Dell EMC, Hewlett-Packard, and Lenovo to modern platforms from Apple Inc. and mainstream PC vendors.

Category:Firmware