Overview

The Unified EFI Forum is a non-profit collaborative trade organization formed to

promote and manage the UEFI standard. As an evolving standard, the UEFI specification
is driven by contributions and support from member companies of the UEFI Forum.

The UEFI Forum board of directors include representatives from the following eleven
leading companies:

• AMD
• Insyde
• American Megatrends Inc.
• Intel
• Apple Computer, Inc.
• Lenovo
• Dell
• Microsoft
• Hewlett Packard
• Phoenix Technologies
• IBM

With support and innovation from all UEFI Forum member companies, work is being
done continually to evolve the UEFI specification to meet industry needs.

For more information about making a direct contribution to development of the UEFI
specification, learn more about becoming a UEFI member.

FAQs
Q: What is UEFI?
UEFI (Unified Extensible Firmware Interface) will be a specification detailing an
interface that helps hand off control of the system for the pre-boot environment (i.e.:
after the system is powered on, but before the operating system starts) to an operating
A:
system, such as Windows* or Linux*. UEFI will provide a clean interface between
operating systems and platform firmware at boot time, and will support an
architecture-independent mechanism for initializing add-in cards.

Q: What is the relationship between EFI and UEFI?

The UEFI specification will be based on the EFI 1.10 specification published by Intel
with corrections and changes managed by the Unified EFI Forum. Intel still holds the
copyright on the EFI 1.10 specification, but has contributed it to the Forum so that the
A:
Forum can evolve it. There will not be any future versions of the EFI specification, but
customers who license it can still use it under the terms of their license from Intel. The
license to the Unified EFI Specification will come from the Forum, not from Intel.

Q: Is there a charge to use the specification?

A: Not for the specification itself. The Promoters of UEFI have agreed that any IP needed
 to implement the specification will be made available on reasonable and non-
discriminatory terms.

Q: Can anyone build their own Unified EFI implementations?

Yes. UEFI expect BIOS vendors, OS vendors and add-in card vendors to all
A:
implement products based on the Unified EFI Specification.

Q: What is the BIOS? What does it do?

The BIOS (basic input/output system) is the program originally conceived to get a PC
started after power-on. The BIOS also manages pre-boot data flow between the
computer's operating system and attached devices such as the hard disk, video adapter,
A: keyboard, and mouse. When the BIOS starts up your computer, it first determines
whether all of the attachments are in place and operational and then it loads the
operating system (or key parts of it) into the computer's memory from local storage
(floppy, hard disk, CD-ROM, USB) or network.

Q: How does UEFI differ from BIOS?

The Basic Input/Output System (BIOS) served as the OS-firmware interface for the
original PC-XT and PC-AT computers. This interface has been expanded over the
years as the "PC clone" market has grown, but was never fully modernized as the
A: market grew. UEFI defines a similar OS-firmware interface, known as "boot services"
and "runtime services", but is not specific to any processor architecture. BIOS is
specific to the Intel x86 processor architecture, as it relies on the 16-bit "real mode"
interface supported by x86 processors.

Q: Does UEFI completely replace a PC BIOS?

No. While UEFI uses a different interface for "boot services" and "runtime services",
some platform firmware must perform the functions BIOS uses for system
A:
configuration (a.k.a. "Power On Self Test" or "POST") and Setup. UEFI does not
specify how POST & Setup are implemented.

Q: How is UEFI implemented on a computer system?

UEFI is an interface. It can be implemented on top of a traditional BIOS (in which
A: case it supplants the traditional "INT" entry points into BIOS) or on top of non-BIOS
implementations.

Q: What problem is the Forum trying to solve?

Interest in EFI has been growing steadily, and the Promoter companies believe that
A:
broad adoption requires industry management and control.

How will the Forum ensure compatibility between different implementations of

Q:
UEFI?
UEFI member companies will make compatibility test code available. Information will
A:
be available at www.uefi.org.
Q: When will products using UEFI technology be available in the market place?
Platforms using the existing EFI 1.10 specification are already in the market place.
A: Platforms using the UEFI specification will enter the market as the specification is
developed by the Forum.

Q: Does UEFI increase security risks from viruses and the like?
Any firmware implementation has to take care to address security. UEFI does not
A:
change that for better or worse.

Q: How do I get more information on UEFI or the UEFI Forum?

A: Contact UEFI Administration for any additional questions.

Unified Extensible Firmware Interface

UEFI Logo

Extensible Firmware Interface's position in the software stack.

The Unified Extensible Firmware Interface (UEFI) is a specification that defines a

software interface between an operating system and platform firmware. UEFI is a
replacement for the older BIOS firmware interface present in all IBM PC-compatible
personal computers.[1]

The original EFI (Extensible Firmware Interface) specification was developed by Intel.
From 2005 development of the EFI specification ceased in favour of UEFI, which was
evolved from EFI 1.10. The UEFI spec is being developed by the Unified EFI Forum, an
industry-wide organization. Computer literature commonly uses "EFI" to refer to "UEFI".

UEFI is not restricted to any specific processor architecture, and can run on top of or
instead of traditional BIOS implementations.[2]
Contents

• 1 History
• 2 Contents
o 2.1 Disk support
o 2.2 Processor support
o 2.3 Services
o 2.4 Protocols
o 2.5 Device drivers
o 2.6 Boot manager
o 2.7 The EFI shell
o 2.8 Extensions
• 3 Implementation and adoption
o 3.1 Intel EFI
o 3.2 Platforms using EFI/UEFI
o 3.3 Operating systems
o 3.4 Virtualization support
o 3.5 Consumer market
• 4 Graphics features
• 5 Criticisms and risks
• 6 See also
• 7 References

• 8 External links

History

The original motivation for EFI came during early development of the first Intel–HP
Itanium systems in the mid-1990s. PC BIOS limitations (16-bit processor mode, 1 MB
addressable space, PC AT hardware dependencies, etc.) were seen as unacceptable for the
larger server platforms Itanium was targeting.[3] The effort to address these concerns was
initially called Intel Boot Initiative, which began in 1998[4] and was later renamed to EFI.
[5][6]

In July 2005, Intel ceased development of the EFI spec at version 1.10, and contributed it
to the Unified EFI Forum, which has evolved the specification as the Unified Extensible
Firmware Interface (UEFI). The original EFI spec remains owned by Intel, which
exclusively provides licenses for EFI-based products, but the UEFI specification is
owned by the Forum, not Intel.[3][7]

Version 2.1 of the UEFI (Unified Extensible Firmware Interface) specification was
released on January 7, 2007. It added cryptography, network authentication, and the User
Interface Architecture (Human Interface Infrastructure in UEFI). The current UEFI
specification is 2.3.1 was approved in April 2011.
Contents

Interaction between the EFI boot manager and EFI drivers

The interface defined by the EFI specification includes data tables that contain platform
information, and boot and runtime services that are available to the OS loader and OS.
UEFI firmware provides several technical advantages:[8]

• Ability to boot from large disks (over 2 TiB)

• Faster boot-up
• CPU-independent architecture
• CPU-independent drivers
• Flexible pre-OS environment, including networking support
• Modular design

Some existing enhancements to PC BIOS, such as the Advanced Configuration and

Power Interface (ACPI) and System Management BIOS (SMBIOS), are also present in
EFI, as they do not rely on a 16-bit runtime interface.

Disk support

In addition to the standard PC disk partition scheme, which uses a master boot record
(MBR), EFI adds support for a new partitioning scheme: GUID Partition Table (GPT).
GPT does not suffer from many of the limitations of MBR. In particular, the MBR limits
on the number and size of disk partitions (up to 4 partitions per disk, up to 2.2 TB (2.2 ×
1012 bytes) per disk) are relaxed.[9] GPT allows for a maximum disk and partition size of
9.4 ZB (9.4 × 1021 bytes).[9][10] The EFI specification does not prescribe any particular file
system. The only Microsoft Windows versions that can boot from disks larger than
2.2 TB, are 64-bit Windows Vista/7, Windows Server 2008 and later, as well as the
Itanium versions of Windows Server 2003 and Windows XP.

Processor support

As of version 2.3, processor bindings exist for Itanium, x86, x86-64, and ARM.

The BIOS is limited to a 16-bit processor mode and 1 MB of addressable space due to the
design being based on the IBM 5150 which used the 16-bit Intel 8088.[3][11] In
comparison, the UEFI processor mode can be either 32-bit (x86-32, ARM) or 64-bit
(x86-64 and Itanium).[3][12] 64-bit UEFI supports long mode which allows applications in
the pre-boot execution environment to have direct access to all of the memory using 64-
bit addressing.[13]

UEFI requires the firmware and operating system to be size-matched, e.g. a 64-bit UEFI
implementation can only boot a 64-bit UEFI operating system.

Services

EFI defines two types of services: boot services and runtime services. Boot services are
only available while the firmware owns the platform, i.e. before the "ExitBootServices"
call. Boot services include text and graphical console support on various devices, bus,
block, and file services. Runtime services are still accessible while the operating system
is running; they include services such as date, time, and NVRAM access.

Protocols

EFI defines protocols as set of software interfaces used for communication between two
binary modules. All EFI drivers must provide services to others via protocols.

Device drivers

In addition to standard architecture-specific device drivers, the EFI specification provides

for a processor-independent device driver environment, called EFI Byte Code or EBC.
System firmware is required by the UEFI specification to carry an interpreter for any
EBC images that reside in or are loaded into the environment. In that sense, EBC is
similar to Open Firmware, the hardware-independent firmware used in PowerPC-based
Apple Macintosh and Sun Microsystems SPARC computers, amongst others.

Some architecture-specific (non-EBC) EFI device driver types can have interfaces for use
from the operating system. This allows the OS to rely on EFI for basic graphics and
network support until OS specific drivers are loaded.
[Boot manager

An EFI boot manager is also used to select and load the operating system, removing the
need for a dedicated boot loader mechanism (the OS boot loader is an EFI application).

The EFI shell

EFI supports a shell environment.[14] The shell can be used to execute other EFI
applications.

Extensions

Extensions to EFI can be loaded from virtually any non-volatile storage device attached
to the computer. For example, an original equipment manufacturer (OEM) can distribute
systems with an EFI partition on the hard drive, which would add additional functions to
the standard EFI firmware stored on the motherboard's ROM.

Implementation and adoption

Intel EFI

Intel's implementation of EFI is the Intel Platform Innovation Framework, code named
"Tiano". Tiano runs on Intel's XScale, Itanium and IA-32 processors, and is proprietary
software, although a portion of the code has been released under the BSD license or
Eclipse Public License (EPL) as the "TianoCore project". TianoCore can be used as a
payload for coreboot.

Phoenix Technologies, currently sells Phoenix SecureCore Tiano and Phoenix MicroCore
Bios supporting UEFI.[15]

Aptio or Aptio 4 is American Megatrend's next-generation BIOS firmware based on

UEFI and the Intel Platform Innovation Framework for UEFI/EFI.[16]

InsydeH2O is Insyde Software's implementation of the Intel Platform Innovation

Framework for UEFI/EFI.[17]

Platforms using EFI/UEFI

Intel's first Itanium workstations and servers, released in 2000, supported EFI 1.02.

Hewlett-Packard's first Itanium 2 systems, released in 2002, supported EFI 1.10; they
were able to boot Windows, Linux, FreeBSD and HP-UX; OpenVMS added support in
June, 2003.

In January 2006, Apple Inc. shipped its first Intel-based Macintosh computers. These
systems used EFI instead of Open Firmware, which had been used on its previous
PowerPC-based systems.[18] On April 5, 2006, Apple first released Boot Camp, which
produces a Windows drivers disk and a non-destructive partitioning tool to allow the
installation of Windows XP or Vista without requiring a reinstallation of Mac OS X. A
firmware update was also released that added BIOS support to its EFI implementation.
Subsequent Macintosh models shipped with the newer firmware.

During 2005, more than one million Intel systems shipped with the Framework.[19] New
mobile, desktop and server products, using the Framework, started shipping in 2006. For
instance, boards that use the Intel 945 chipset series use the Framework.

Since 2005, EFI has also been implemented on non-PC architectures, such as embedded
systems based on XScale cores.[19]

The EDK includes an NT32 target, which allows EFI firmware and EFI applications to
run within a Windows application. But no direct hardware access is allowed by EDK
NT32. This means only a subset of EFI application and drivers can be executed at the
EDK NT32 target.

In 2008, more x86-64 systems have adopted UEFI. While many of these systems still
only support booting the BIOS-based OSes via the Compatibility Support Module (CSM)
(thus does not appear to the user that the system is UEFI-based), other systems started to
support booting UEFI-based OSes. For example, IBM x3450 server, MSI motherboards
with ClickBIOS, all HP EliteBook Notebook and Tablet PCs, newer HP Compaq
Notebook PCs (e.g., 6730b, 6735b, etc.).

In 2009, IBM shipped System x machines (x3550 M2, x3650 M2, iDataPlex dx360 M2)
and BladeCenter HS22 with UEFI support. Dell shipped PowerEdge T610, R610, R710,
M610 and M710 servers with UEFI support. More commercially available systems are
mentioned in a UEFI whitepaper.[20] Many Sandy Bridge PC platforms use UEFI.

Operating systems

An operating system that supports being booted from a (U)EFI is called a (U)EFI-aware
OS, defined by (U)EFI specification. Here the term booted from a (U)EFI means
directly booting the system using a (U)EFI OS loader stored on any storage device. The
default location for the OS loader is \EFI\BOOT\boot[architecture name].efi,
where the architecture name can be e.g. IA32, X64 or IA64. Some OS vendors may have
their own OS loader. They may also change the default boot location.

• Linux has been able to use EFI at boot time since early 2000, using the elilo EFI
boot loader or, more recently, EFI versions of GRUB.[21]
• HP-UX has used (U)EFI as its boot mechanism on IA-64 systems since 2002.
• HP OpenVMS has used (U)EFI on IA-64 since its initial evaluation release in
December 2003, and for production releases since January 2005.[22]
 • Apple uses EFI for its line of Intel-based Macs. Mac OS X v10.4 Tiger for Intel
and Mac OS X v10.5 Leopard support EFI v1.10 in 32-bit mode, even on 64-bit
CPUs (newer Macs have 64-bit EFI).[23]
• The Itanium versions of Windows 2000 (Advanced Server Limited Edition and
Datacenter Server Limited Edition) supported EFI 1.10 in 2002. MS Windows
Server 2003 for IA-64, MS Windows XP 64-bit Edition, and Windows 2000
Advanced Server Limited Edition, all of which are for the Intel Itanium family of
processors, support EFI, a requirement of the platform through the DIG64
specification.[24]
• Microsoft introduced UEFI support for x86-64 Windows operating systems with
Windows Server 2008 and Windows Vista Service Pack 1, so the 64-bit versions
of Windows 7 are compatible with EFI. Microsoft does not offer support for 32-
bit UEFI since vendors did not have any interest in producing native 32-bit UEFI
firmware because of the mainstream status of 64-bit computing.[25] Microsoft has
released a video with Andrew Ritz and Jamie Schwartz explaining Pre-OS
support involving UEFI on Windows Vista and Windows Server 2008.[26]

Virtualization support

• HP Integrity Virtual Machines supports UEFI boot on HP Integrity Servers. It

also provides a virtualized UEFI environment for the guest UEFI-aware OSes.
• Intel hosts an Open Virtual Machine Firmware project on Sourceforge[27].
• VMware Fusion 3 software for Mac OS X supports booting Mac OS X Server
virtual machines using EFI.
• VirtualBox has had support for UEFI since 3.1[28], but limited to Unix/Linux
operating systems (missing support for Windows Vista x64 and Windows 7 x64).

Consumer market

In 2011 Asus and MSI launched several consumer-based motherboards using the Intel
LGA 1155 chipset with EFI.

Graphics features

EFI supports graphical menus and features, such as is implemented on Aptio or Great
Wall UEFI.

There are two graphics output protocols defined by EFI specifications. The first one is
UGA, which stands for Universal Graphic Adapters. The second one is GOP, which
stands for Graphic Output Protocol. The two are similar. UGA is only supported at EFI
1.1 or older specs. EFI does not define a user interface. This depends fully on the
implementation by BIOS vendors. Currently most EFI-enabled machines only have a
legacy BIOS-like text mode UI.
Criticisms and risks

EFI was criticized by coreboot creator Ronald G. Minnich as an attempt to preserve

intellectual property.[33] It does not solve any of the BIOS’ long standing problems of
requiring two different drivers — one for the firmware and one for the operating system
— for most hardware.[34]

TianoCore[35] is an open-source project which provides the tools to make a fully-free

firmware based on UEFI, but it lacks the specialized drivers that initialize chipset
functions, thus requiring additional support from the chipset vendor. Tianocore is a
payload option for Coreboot, which includes chipset initialization code.

Because UEFI can allow for more flexible remote network booting than current BIOS
technology, there are concerns over the security provisions in the standard[36].

See also

• Platform Initialization Specification

• Advanced Configuration and Power Interface (ACPI)
• Basic Input/Output System (BIOS)
• Booting
• Coreboot
• Functional specification
• Open Firmware
• OpenBIOS
• System Management BIOS (SMBIOS)
• System Management Mode (SMM)
• Unified EFI Forum

References

1. ^ Michael Kinney (2000-09-01). "Solving BIOS Boot Issues with EFI"

(PDF). pp. 47–50.
http://systems.cs.colorado.edu/Documentation/IntelDataSheets/xscalemagazine.pd
f. Retrieved 2010-09-14.
2. ^ About, http://www.uefi.org/about/.
3. ^ a b c d "Emulex UEFI Implementation Delivers Industry-leading Features
for IBM Systems" (PDF). Emulex. http://www.emulex.com/artifacts/757d23e7-
8acb-41a7-872a-afb733ab0688/elx_tb_all_uefi_ibm.pdf. Retrieved 2010-09-14.
4. ^ Extensible Firmware Interface (EFI) and Unified EFI (UEFI), Intel,
http://www.intel.com/technology/efi/.
5. ^ Wei, Dong (2006), "foreword", Beyond BIOS, Intel Press, ISBN 978-0-
9743649-0-2.
6. ^ "1.10 Specification overview", Extensible Firmware Interface, Intel,
http://www.intel.com/technology/efi/main_specification.htm.
7. ^ About, Unified EFI Forum, http://www.uefi.org/about/, "Q: What is the
relationship between EFI and UEFI? A: The UEFI specification will be based on
the EFI 1.10 specification published by Intel with corrections and changes
managed by the Unified EFI Forum. Intel still holds the copyright on the EFI 1.10
specification, but has contributed it to the Forum so that the Forum can evolve it.
There will not be any future versions of the EFI specification, but customers who
license it can still use it under the terms of their license from Intel. The license to
the Unified EFI Specification will come from the Forum, not from Intel"
8. ^ "UEFI and Windows". Microsoft. 2009-09-15.
http://www.microsoft.com/whdc/system/platform/firmware/UEFI_Windows.msp
x. Retrieved 2010-09-14.
9. ^ a b "FAQ: Drive Partition Limits" (PDF). UEFI Forum.
http://www.uefi.org/learning_center/UEFI_MBR_Limits_v2.pdf. Retrieved 2010-
06-09.
10. ^ Bill Boswell (2002-07-01). "FAQ: Drive Partition Limits". Redmond
Mag. http://redmondmag.com/Articles/2002/07/01/The-64Bit-Question.aspx.
Retrieved 2010-06-09. "GPT disks also support very large partitions thanks to a
64-bit Logical Block Address scheme. A logical block corresponds to one sector,
or 512 bytes, yielding a maximum theoretical capacity of eight zettabytes,"
11. ^ Ben Hardwidge (2010-06-01). "LBA explained — Solving the 3TB
Problem?". bit-tech. http://www.bit-tech.net/hardware/storage/2010/06/01/are-we-
ready-for-3tb-hard-disks/2. Retrieved 2010-06-18.
12. ^ Brian Richardson (2010-05-10). "Ask a BIOS Guy: "Why UEFI"". Intel
Architecture Blog. http://community.edc.intel.com/t5/New-to-Intel-Architecture-
Blog/Ask-a-BIOS-Guy-quot-Why-UEFI-quot/ba-p/2781. Retrieved 2010-06-18.
13. ^ Gary Simpson. "UEFI Momentum — The AMD perspective" (PPTX).
AMD. http://download.microsoft.com/download/5/e/6/5e66b27b-988b-4f50-af3a-
c2ff1e62180f/cor-t605_wh08.pptx. Retrieved 2010-06-18.
14. ^ Efi-shell.tianocore.org for EFI shell information
15. ^ "SecureCore Tiano™". Phoenix Technologies, LTD.
http://www.phoenix.com/pages/phoenix-securecore-tiano-tm. Retrieved 2010-09-
14.
16. ^ "Aptio®: The Complete UEFI Product Solution" (PDF). American
Megatrends, Inc.
http://www.ami.com/support/doc/AMI_Aptio_4.x_Datasheet_PUB_2009-09-
14.pdf. Retrieved 2011-01-08.
17. ^ "InsydeH2O UEFI Framework". Insyde Software Corp.
http://www.insydesw.com/products/products-efi-h2o.htm. Retrieved 2011-01-08.
18. ^ Apple Computer. “Universal Binary Programming Guidelines, Second
Edition: Extensible Firmware Interface (EFI)"
19. ^ a b "Intel® Platform Innovation Framework for UEFI Overview". Intel.
http://www.intel.com/technology/framework/overview1.htm. Retrieved 2010-09-
14.
20. ^ (PDF) Evaluating UEFI using Commercially Available Platforms and
Solutions, UEFI, 2011‐5,
http://www.uefi.org/news/uefi_industry/UEFIEvaluationPlatforms_2011_05.pdf.
 21. ^ EFI version of Grub, Debian GNU/Linux,
http://packages.debian.org/sid/grub-efi, retrieved 1 May 2008.
22. ^ OpenVMS Release History, HP,
http://h71000.www7.hp.com/openvms/os/openvms-release-history.html, retrieved
16 September 2008.
23. ^ rEFIt — Windows Vista and EFI, SourceForge,
http://refit.sourceforge.net/info/vista.html.
24. ^ "Extensible Firmware Interface", Windows Server TechCenter,
Microsoft, http://technet2.microsoft.com/WindowsServer/en/Library/6b03fad7-
665e-49f3-8e7d-e1a6a5be9cf01033.mspx.
25. ^ "Unified Extended Firmware Interface support in Windows Vista".
Microsoft. 2006-10-26. http://support.microsoft.com/kb/930061. Retrieved 2010-
06-12. "Microsoft determined that vendors would not have any interest in
producing native UEFI 32-bit firmware because of the current status of
mainstream 64-bit computing and platform costs. Therefore, Microsoft has chosen
not to ship support for 32-bit UEFI implementations."
26. ^ "Pre-OS Video", MS Developers Network Channel 9, Microsoft,
http://channel9.msdn.com/showpost.aspx?postid=292774.
27. ^ Open Virtual Machine Firmware, SourceForge,
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF.
28. ^ 3.1 Changelog, VirtualBox, http://www.virtualbox.org/wiki/Changelog-
3.1.
29. ^ Ticket 7702, VirtualBox, http://www.virtualbox.org/ticket/7702.
30. ^ "Statement by sr. software engineer at Oracle", Forum, VirtualBox,
http://forums.virtualbox.org/viewtopic.php?f=1&p=183022#p114765.
31. ^ Asus P67 Motherboard Preview, .
32. ^ Intel shows PC booting Windows with UEFI firmware
33. ^ "Interview: Ronald G Minnich". Fosdem. 2007-2-6.
http://archive.fosdem.org/2007/interview/ronald+g+minnich. Retrieved 2010-9-
14.
34. ^ "coreboot (aka LinuxBIOS): The Free/Open-Source x86 Firmware".
YouTube. 2008-10-31. http://www.youtube.com/watch?v=X72LgcMpM9k.
Retrieved 2010-09-14.
35. ^ "Welcome", TianoCore, SourceForge,
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Welcome.
36. ^ Risks, UK: NCL, http://catless.ncl.ac.uk/Risks/26.18.html#subj13.

External links

• UEFI Homepage
• EFI Architecture Dr. Dobbs Portal Article
• EFI Linux gnu toolchain (gnu-efi)
• EFI Linux Loader project (ELILO)
• rEFIt, a boot menu and maintenance toolkit for EFI-based machines.
• Intel’s EFI page
• Intel’s Framework page
 • Intel List of commands
• Intel-sponsored open-source EFI Framework initiative
• EFI/Framework overview
• Book - Beyond BIOS
• Book - Harnessing the UEFI Shell
• Book Chapter - UEFI: From Reset Vector to Operating System
• A forum post describing steps to modify existing Windows x64 BIOS-MBR
based installations to boot from UEFI-GPT
• UEFI Howto documents(Chinese)
• Book - Beyond BIOS, 2nd edition, updated with UEFI2.3 and PI1.2

Retrieved from "http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface"

Categories: BIOS | Macintosh firmware