Questions and Answers

Included on this page:

back to top

What is the Intel Platform Innovation Framework for UEFI?

The Intel Platform Innovation Framework for UEFI is new software code that allows BIOS vendors to replace the obsolete PC BIOS. It implements the EFI 1.1 interface. It provides the ability to add new features to the pre-boot environment, such as improved platform manageability, serviceability and recovery and improved administrative interfaces, which previously could not operate in the pre-boot environment. The framework is a product-strength implementation of EFI that is an all-new firmware implementation for platforms all the way down to silicon. The Intel Platform Innovation Framework for UEFI, the name of the product, is now the Intel recommended implementation of the EFI Specification across all Intel Architectures.

back to top

What is Intel's intent in creating the framework?

Intel's intent in producing the framework is to enable Intel, BIOS vendors, OS vendors, competitive silicon suppliers, and OEMs to move compatibly beyond the strictures of conventional BIOS implementation. Intel believes that the framework will improve development and deployment of new silicon and platform features into the industry.

The technical foundation of the BIOS in PCs is over 20 years old. Unlike the processor, chipset, system bus, memory subsystem, operating system or applications, the BIOS is constructed largely as it was years ago. The BIOS inhibits the pace of hardware evolution and contributes to higher cost by perpetuating dependence on legacy HW interfaces. EFI makes possible a new, modular, firmware implementation. The framework based on foundation code is one such implementation.

back to top

How can customers obtain the framework?

Customers who wish to obtain the Intel Platform Innovation Framework for UEFI should contact a participating vendor. Announced participating vendors include American Megatrends, Inc.*, Insyde Software Corp.* and Phoenix Technologies Ltd.*.

Participating vendors offer products and services based on the framework, for both Intel® and non-Intel silicon. The framework is not generally available directly from Intel. Intel has licensed participating vendors to provide the framework and related products and services to the industry.

Hardware drivers and modules for Intel silicon are being created by Intel and by participating vendors. Participating vendors will be offering drivers for non-Intel silicon as well as working with suppliers of non-Intel silicon to provide OEM support for the framework on non-Intel systems.

back to top

Is the framework compatible with traditional BIOS?

Yes. The framework provides the capability to support legacy BIOS interfaces through the Compatibility Support Module (CSM), allowing the system vendors to continue using the operating systems and tools they use today as they make a gradual and managed transition to EFI. A typical CSM is approximately 60 KB (38 KB compressed) of firmware that is specific to each participating BIOS vendor and is based on that vendor's latest BIOS code base.

back to top

Is the framework just for servers?

The framework was designed for multiple architectures, including IA-32, Intel® Itanium® processor family and Xscale™ technology based processors, and to support different system configuration, ranging from high-end servers, through desktop, mobile, and handhelds.

back to top

What is EFI and UEFI?

EFI is 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 system, such as Microsoft Windows* or Linux*. It provides a clean interface between operating systems and the platform firmware at boot time, and supports an architecture-independent mechanism for initializing add-in cards. EFI is supported by the most popular 64-bit OS implementations and platforms, and is an emerging interface for 32-bit systems.

During 2005, leading technology companies, including Intel, formed the Unified EFI forum. The forum is assuming responsibility from Intel for the evolution and promotion of the EFI Specification. For more details on Unified EFI forum go to http://www.uefi.org.

back to top

Will other silicon vendors (such as AMD, Via and others) be able to
use the framework?

Participating vendors offer products and services based on the framework, for both Intel and non-Intel silicon. Participating vendors will be offering drivers for non-Intel silicon as well as working with suppliers of non-Intel silicon to provide OEM support for the framework on non-Intel systems.

back to top

What is the expected timeframe when we will see products using this technology in the market place?

Intel expects that the framework will be the Intel primary vehicle for enabling firmware for new silicon in the 2007-2008 timeframe. Intel systems and silicon product divisions began offering selected SKUs of customer reference boards, motherboards, and systems based on the framework, with the support of participating vendors, in 2004. The first example of a complete end-user PC that was sold by a major OEM incorporating the framework was released in the second half of 2003.

back to top

What was Intel® Open Source announcement with the framework's foundation code about?

Intel announced that the foundation code for the framework would be released under an open source license. That release can be found at www.tianocore.org.

back to top

Why is Intel putting the foundation code under an open source license?

BIOS is the last legacy technology in a PC platform and is over 20 years old. Intel and many others believe that the framework, which will enable new pre-boot features, is the right way to replace it. By moving its foundation code into a vendor-neutral collaborative software development project, Intel is inviting the entire PC industry to use it, secure in the knowledge that changes to the code can be made by anyone, and that those changes will be visible to all.

back to top

What's the difference between the foundation and the framework?

The foundation code represents the core interoperability interfaces between modules and in the framework. The PEI Foundation supports silicon-support modules that are required at power-on, and DXE Foundation supports drivers, including drivers that implement portions of the framework like PCI and USB, and drivers for various devices on boards. The foundation code is "the green H" that Intel has shown at multiple IDFs. The framework, on the other hand, is the foundation code plus drivers for common bus architectures.

back to top

Why are you putting the foundation code out under an open source
license and not the whole framework?

The objective of releasing the foundation code from the framework is not to create a "free BIOS". The objective is to provide hardware vendors with an environment that will enable them to develop and validate drivers to support their products as the industry moves forward with the framework, and to show that the foundation code for the framework will be maintained in public view.

back to top

Does Intel give up the IP on the foundation code when it is released to collaborative software development?

The code is released under the BSD license. This license doesn't "give up IP", it allows others to use the code under the terms of the license.

back to top

Does this mean framework-based BIOS from AMI, Insyde or Phoenix will be free?

No. BIOS companies offer tested, supported, royalty-bearing products based on the framework. There is nothing in BSD license that forces these products to be free.

back to top

When Intel first released the framework, you said customers should
work through BIOS vendors to obtain a solution. What has changed to make you change the distribution model?

Nothing. We still believe this.

back to top

Since the foundation is under BSD, does this mean BIOS will be based on Linux?

No. The framework has no Linux code in it, and does not have the same license terms as Linux.

back to top

Won't this process fragment the foundation code with many splinter versions?

That certainly is a concern with BSD-licensed code. The Intel Platform Innovation for UEFI architecture specification remains the touchstone for insuring interoperability. Intel also plans to release tests for use with the framework later this year. Customers can insist that their vendors pass these tests.

back to top

I download the open source code...what will it do?

As posted, the code will provide running foundation code with a kit for creating and integrating many boot time drivers on a Microsoft Windows PC using industry-standard compilers and debuggers.

back to top

I download the code and I buy all my silicon from Intel. Can't I make a free BIOS replacement?

No more easily than you could write a complete one from scratch now. Intel is making drivers generally available to the PC community available through AMI, Insyde or Phoenix as part of their complete product offerings. These offerings include required functionality, backward compatibility, testing and support and will continue to be royalty-bearing. An example of this is the CSM that is available from participating BIOS vendors that provides legacy support.

back to top

Why isn't Intel releasing its chipset drivers too?

A primary purpose of this collaborative project is to ensure that changes to infrastructure code, code that is shared by all vendors' framework implementations, are transparent. This will ensure that the infrastructure code will remain common over time even as it is enhanced and maintained which will preserve the interoperability for third party components over time. The low level details of specific silicon components are often considered proprietary information. Vendors will be able to take advantage of a stable interoperability surface offered by transparent, shared Foundation code to support development of commercial strength code modules for their silicon products while preserving their confidential information. Framework-ready modules for Intel platforms are part of the participating BIOS vendors' offerings.

back to top

Why is there one module being released that isn't BSD-licensed?

http://www.microsoft.com/whdc/system/platform/firmware/fatgen.mspx

back to top

Why do you still need BIOS vendors?

The industry needs BIOS vendors. They are the commercial foundation that customers depend on to get vendor-neutral support of system initialization. BIOS vendors also are experts in the use of the framework, and supply hardware specific bus and device driver components along with backward compatibility through custom Compatibility Support Modules. Intel is releasing foundation code in a driver development environment, but BIOS vendors supply a firmware product based on that foundation, and other software not available under the BSD.

back to top

Who are the real customers for the driver development kit?

The real customers here are other silicon vendors, PC OEMs, board manufacturers and BIOS companies who want to be able to write boot-time drivers for their products without having to be dependent on Intel.