What UEFI Can Do For You





EFI is a software interface that operates between the operating system and the platform firmware, allowing it to be capable of replacing the BIOS. As a matter of fact, EFI is complex enough to be called “OS-like.” It not only offers driver support, interfaces, and services, but it also has a shell that allows users to execute applications on a command line interface.


EFI contains system information organized into tables, and it offers boot and runtime services to the operating system. Boot services include initialization, file services, and textual and graphical user consoles. Runtime services include date, time, and NVRAM services. To enable or facilitate inter-device communication, all EFI drivers and components communicate through specified protocols. Drivers are also important, since the EFI device driver environment, the EFI Byte Code (EBC), is a processor-independent environment that allows for both device initialization and operation (with the exception of OS-specific hardware with specific feature and driver support requirements, such as high-end graphics cards).




Gone are the days when you needed boot manager software to start different operating systems. EFI implements its own boot manager to take care of this job. System builders have new opportunities as well, because EFI extensions may be added from various, non-volatile locations. This means that a PC maker could use the customer’s desired motherboard and platform while adding additional system features via EFI through a partition of the system hard drive or, eventually, even through Internet downloads.


Apple’s Boot Camp, which allows users to install a Windows version next to an existing Mac OS installation in a non-destructive manner, actually utilizes Intel’s EFI implementation on Intel-powered Macs instead of Open Firmware. This has been available since April of 2005 and is not nearly as easily to pull off on x86 PC platforms.




Since EFI’s Platform Initialization (PI) feature offers a Compatibility Support Mode (CSM) through which it can publish additional interfaces, it’s also possible to provide a legacy BIOS runtime. Given the benefits, this makes it very appealing for manufacturers to adopt UEFI quickly. However, today’s broad support exists mostly on paper.

do you still have to flash?

if so then I don't see why the extra layer

I mean it's already possible to dual boot

I'm not trying to criticize I just don't understand a whole about what happens before the os loads - boot loader

but the system does already do the things u r talking about the software doing as far a communication with OS or else it wouldn't load
and u can use a command line in DOS or command prompt already-

then, with the point being replacing the bios - why do I want to do that?

I know what you mean ..

But it is the industry making the changes.

Partly because newer hardware (hard drives 3 terabyte and up) will not

be recognized by older versions of BIOS.

New hardware , new Versions of BIOS.

Faster start ups..

so - changes that can't be flashed?

so - changes that can't be flashed?

To flash is to update a BIOS version.

The new BIOS uses a different platform.

The new BIOS will have it's own set of flash/updates not

compatible with the old .

it won't be visiting my house then - doesn't make any sense dude - but I will defintely check at work about what ur saying -

these changes will not affect most people

for some time. To learn more or become certified

go here : http://www.uefi.org/specs/agreement

An extra layer to facilitate 'copyrights'? Surprised it took em this long.
I agree- what's wrong with letting your board boot itself then let the OS take the wheel?