The 64-bit editions of the Microsoft Windows operating system support both workstation and server computers. Implementing hardware and firmware support for a 64-bit system requires special considerations that differ from 32-bit platform design. This paper describes the special considerations for firmware, hard disk partitions, and device drivers. This paper does not address processor-related issues.
ACPI Support for 64-bit Windows
Advanced Configuration and Power Interface (ACPI) Specification defines the system board, firmware, and operating system requirements for operating system control of configuration.
ACPI Revision 2.0 defines expanded interfaces to support 64-bit systems through extended Table definitions, new ACPI Source Language (ASL), and ACPI Machine Language(AML) 64-bit functions.
Advanced Configuration and Power Interface (ACPI) Specification defines the system board, firmware, and operating system requirements for operating system control of configuration.
ACPI Revision 2.0 defines expanded interfaces to support 64-bit systems through extended Table definitions, new ACPI Source Language (ASL), and ACPI Machine Language(AML) 64-bit functions.
Firmware for 64-bit Systems
Firmware provides boot support for initializing the hardware before the operating system is started. In x86-based (32-bit) systems, this capability is provided by the BIOS. Because traditional BIOS-based boot will not work with 64-bit Windows, other firmware boot solutions must be implemented.
EFIExtensible Firmware Interface
EFI is a new standard for the interface provided by the firmware that boots PCs, based on the Extensible Firmware Interface Specification, Version 1.02 (Intel Corporation). Microsoft supports EFI as the only firmware interface for booting 64-bit Windows operating systems.
Because 64-bit Windows will not boot with BIOS or with System Abstraction Layer alone, EFI is a requirement for all Intel Itanium-based systems.
In addition to protocols required in the EFI specification, Microsoft recommends that the firmware also support PXE_BC (remote/network boot), SERIAL_IO, and SIMPLE_NETWORK protocols as defined in the EFI specification. Support for these protocols is required by the "Designed for Windows" logo program for 64-bit systems.
Firmware provides boot support for initializing the hardware before the operating system is started. In x86-based (32-bit) systems, this capability is provided by the BIOS. Because traditional BIOS-based boot will not work with 64-bit Windows, other firmware boot solutions must be implemented.
EFIExtensible Firmware Interface
EFI is a new standard for the interface provided by the firmware that boots PCs, based on the Extensible Firmware Interface Specification, Version 1.02 (Intel Corporation). Microsoft supports EFI as the only firmware interface for booting 64-bit Windows operating systems.
Because 64-bit Windows will not boot with BIOS or with System Abstraction Layer alone, EFI is a requirement for all Intel Itanium-based systems.
In addition to protocols required in the EFI specification, Microsoft recommends that the firmware also support PXE_BC (remote/network boot), SERIAL_IO, and SIMPLE_NETWORK protocols as defined in the EFI specification. Support for these protocols is required by the "Designed for Windows" logo program for 64-bit systems.
The ESP contains the OS Loader, EFI drivers, and other files necessary to boot the system. MBR disks can also have an ESP, identified by partition type 0xEF. Although EFI specifies booting from either the GPT or MBR, 64-bit Windows does not support booting EFI from MBR disks or 0xEF partitions.
Information From
http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx
No comments:
Post a Comment