This section describes additional requirements or exceptions to the requirements defined earlier in Section A1.0.
For desktop systems, all applicable requirements in A2.0 are included by reference.
For server systems, all applicable requirements in A6.0 are included by reference.
A5.1 Itanium-based System - Windows Compatibility
A5.1.1 Windows DDK: “64-Bit Issues”
A5.1.2 "Porting Your Driver to 64-Bit Windows" and other 64-bit implementation guidelines for Windows
All Error Records passed by the System Abstraction Layer (SAL) to the operating system for all fatal and corrected CPU and Platform Machine Check Architecture (MCA) Events must be, at a minimum, compliant with the Itanium Processor Family System Abstraction Layer Specification (SAL 3.0). The SAL must maintain the Error Records in non-volatile storage across system reboots and power cycles. See Appendix B, “Error Record Structures,” in SAL 3.0 specification, dated January 2001.
Microsoft Extensible Firmware Interface FAT32 File System Specification
Microsoft Extensible Firmware Interface Long File Name Specification
Microsoft Portable Executable and Common Object File Format Specification
A5.2.4 Intel Itanium Processor Family System Abstraction Layer Specification (SAL 3.0)
A5.3 Itanium-based System - Quality
WHQL Test Specification References: Chapter 2: EFI Test Specification;
Plus technology-specific test specifications
A5.3.1 Pass Windows Logo Program testing for Itanium-based products
Product is submitted to the appropriate WHQL test program and passes all testing for the Windows Logo Program for hardware as described in detail in the WHQL Test Specification and the Microsoft Windows Hardware Compatibility Test Kit 10.0 documentation.
A5.4 Itanium-based System - Windows Experience
A5.4.1 Comply with ACPI 2.0
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:
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 22.214.171.124 in ACPI 2.0). The EFI GUID for the ACPI 2.0 RSDP Structure pointer is:
Future wakeup requirements for Itanium-based systems are defined at A5.R.1.
Note: Windows XP and Windows Whistler Server are not fully ACPI 2.0-compliant operating systems. The ACPI 2.0 Specification was written to be fully backward compatible with ACPI 1.0b.
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 Hardware Design Guide guidelines
See also: A1.1.4 - Support booting from CD or DVD device per El Torito v. 1.0 No Emulation mode.
A5.4.3 Provide serial port to use as debug port, using either 2F8h or 3F8h
A1.1.4 Provide PCI interrupt routing information per ACPI 2.0 Section 6.2.8.
B126.96.36.199 Adapters address full physical address space on a 64-bit platform; 32-bit PCI adapters used on the primary data path support the PCI DAC command, with the exception of 10/100 Ethernet devices.
Note: 64-bit Windows (Professional and Server) does not currently support power management; power management may be added in a future operating system release.
A5.R.2 Future version of Windows Professional 64-bit Edition: Standard Error Record Format passed by the SAL to the operating system
All Error Records passed by the SAL to the operating system for all fatal and corrected, CPU and Platform MCA Events must be, at a minimum, compliant with SAL 3.0. The SAL must maintain the Error Records in non-volatile storage across system reboots and power cycles.