X hits on this document





45 / 174

Microsoft Windows Logo Program System and Device Requirements  —  45

To comply with this requirement, implement the ACPI 1.0b backward-compatible portion of ACPI 2.0, plus the 64-bit fixed tables. The fixed tables that must be supported include:

RSDP Structure

Extended System Description Table (XSDT)

Fixed ACPI Description Table (FADT)

Firmware ACPI Control Structure (FACS)

Multiple APIC Description Table (MADT)

Itanium-based platforms must use the new Extensible Firmware Interface (EFI) GUID for the ACPI 2.0 RSDP Structure (see Section in ACPI 2.0).

The EFI GUID for the ACPI 2.0 RSDP Structure pointer is:


A5.4.2 Comply with EFI 1.0, with support for USB boot devices, firmware update, and PXE_BC, SERIAL_IO, and SIMPLE_NETWORK protocols, plus additional guidelines

Itanium-based system must comply with EFI 1.0 or later, with support for USB boot devices, firmware update, and PXE_BC, SERIAL_IO, and SIMPLE_NETWORK protocols.

The only boot mechanism supported for platforms running 64-bit Windows is defined in EFI 1.0 or later. BIOS-based boot is not supported and will not work with 64-bit Windows.

Note: Although the PXE_BC (remote/network boot), SERIAL_IO, and SIMPLE_NETWORK protocols are defined as optional implementation elements in the EFI specification, in this guideline they are requirements for EFI systems.

A5.4.2.1 System supports network-based boot via EFI boot manager

EFI systems must provide support for booting systems from the network as defined in EFI 1.0 or later. This support includes the capability, via the EFI boot manager, to configure boot devices in order of preference by the administrator of the server, plus a method for forcing a network-based boot. These mechanisms must be available to the administrator in the pre-boot state of the system.

A5.4.2.2 System provides boot support for USB keyboard and bus

The system firmware must provide EFI boot support for USB keyboards, pointing devices, and hubs.

The system firmware must also support the keyboard behind at least one level of external hub. This support must provide the ability for the user to enter the system’s firmware-based configuration utilities and provide sufficient functionality to get EFI-aware versions of Windows installed and booted. USB keyboards built as standalone devices, part of a composite device, or part of a compound device must be recognized and usable.

For systems with multiple USB host controllers, firmware support for USB keyboards, pointing devices, and hubs is required for all host controllers that are integrated on the system board (that is, firmware support is not required for add-on cards).

Keyboard and pointing devices must be functional for all modes of the operating system, including booting, loading, recovery console, and operating system installation.

USB external connectors and USB input device support must be enabled by default in the firmware, and the firmware must make USB input devices such as keyboards and pointing devices available at boot time.

A5.4.2.3 System implements SAL, including firmware update method

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views583
Page views583
Page last viewedWed Jan 18 07:07:35 UTC 2017