A1.1.4.5 Support boot-drive determination in multiple-drive systems via CIP BIOS Boot of EFI boot manager

Mobile PC Note
See A3.4.2 for mobile BIOS PXE requirement.
A1.1.4.5 Support boot-drive determination in multiple-drive systems via CIP BIOS Boot of EFI boot manager
The BIOS must comply with the implementation of boot-drive determination in multiple-drive systems as defined in Section 5.0 of the Compaq-Intel-Phoenix BIOS Boot Specification, Version 1.01. Windows uses this format for determining the boot drive when new bootable devices are introduced to a PC. Itanium-based systems must use EFI boot manager capabilities.
A1.1.4.7 DELETED A1.1.4.8 DELETED A1.1.4.9 x86-based: Support Int13h Extensions on BIOS boot-based system for correct support of high-capacity hard drives.
BIOS and option ROMs support Int 13h Extensions as defined in the “Layered Block Device Drivers” section of the Windows DDK. This requirement also applies for redundant array of inexpensive disks (RAID) controllers when implemented, to support booting from Int 13h Extension devices.
Support for drives with capacities greater than 8.4 GB must be provided through the extended services (functions 4xh and greater) of the Int 13h Extensions as defined in Enhanced BIOS Services for Disk Drives [T13-1226DT], Revision 7.
A1.1.4.10 DELETED A1.1.4.11 Provide PCI interrupt routing information
Use a _PRT object per ACPI 1.0b Section 6.2.3 for x86-based systems or ACPI 2.0 Section 6.2.8 for Itanium-based systems.
A1.1.4.12 x86-based: Support logical block addressing (LBA) for ATA disks (if present in the system).
The system BIOS must support the use of logical block addressing (LBA) for drives with LBA addressable area greater than 16,515,072 sectors, and the system BIOS must use LBA for all read and write operations to the device. The ATA 1226 technical report defines the proper implementation of LBA.
A1.1.4.13 Provide boot support for USB keyboards and hubs
For USB host controllers that provide only internally-accessible USB ports and that are not connected to a keyboard or hub: such controllers are not required to provide boot support for keyboards and hubs. If a downstream keyboard is attached to such a host controller, the keyboard and any intermediate hubs must be supported at boot time.
See “Server Note” at A1.4.3 for systems that provide headless server support.
A1.1.4.13.1 BIOS handles long descriptors read from USB device attached at boot time. When a USB host requests the configuration descriptor for a device, the device returns the configuration descriptor, all interface descriptors, and endpoint descriptors for all interfaces in a single request (see section 9.4.3 of the USB 1.1 specification). The maximum size of the returned data is 64 KB.
To enumerate the USB and configure boot devices, the BIOS must make a configuration request to every device encountered. Therefore, the BIOS must be capable of handling a maximum length descriptor if such a descriptor is returned. However, the BIOS is required to configure only boot devices. Nonboot devices can be left in the addressed USB-visible device state.
A1.1.4.13.2 BIOS provides boot support for USB keyboards and hubs. This BIOS support, as defined in Universal Serial Bus (USB) Device Class Definition for Human Interface Devices (HID), Version 1.1, with particular attention to the Keyboard Boot Protocol, must provide the ability for the user to enter the BIOS setup utility and also provide enough functionality to install and boot an operating system that recognizes USB peripherals. USB keyboards built as stand-alone devices, part of a composite device, or part of a compound device must all be recognized and usable. The BIOS is required to support keyboards behind at least two levels of external hubs.
A1.1.4.13.3 For systems with multiple USB host controllers, BIOS support for USB keyboards and hubs is required for all host controllers that are integrated on the system board (that is, not add-on cards).
A1.1.4.13.4 Keyboard and pointing devices must be functional for all modes of the operating system, including booting, loading, safe mode, and operating system setup and installation.
A1.1.4.13.5 USB external connectors and USB input device support must be enabled by default in the BIOS, and the BIOS must make USB input devices, such as keyboards and pointing devices, available at boot time.
A1.1.4.14 If bootable ATAPI devices are included in the system, firmware support complies with ATAPI Removable Media Device BIOS Specification 1.0 and ATA/ATAPI-5
ATA BIOS or option ROM must provide boot support for the primary ATA Packet Interface (ATAPI) bootable floppy disk drive in compliance with ATAPI Removable Media Device BIOS Specification, Version 1.0. Complying with this specification provides Int 13h and Int 40h support for bootable floppy drives as the primary or secondary floppy disk device.
The system BIOS must configure the drive and host controller so they are optimized for ATA operation. The programmed I/O mode must continue to work. The ATA/ATAPI device driver must also support restoration of these settings using the ACPI control methods _GTM, _STM, and _GTF when the ATA controller is power managed across a suspend and resume cycle.
The AT Attachment with Packet Interface – 5 (ATA/ATAPI-5) standard defines the enumeration process for all ATAPI devices.
A1.1.4.16 x86-based client: For a system board that supports a riser card, provide a unique identifier for the riser
The BIOS for a system board that supports any type of enumerable riser card, such as AMR, Advanced Communications Riser (ACR), and Communications and Networking Riser (CNR), must include the following support:
-
Detecting and enumerating each function on that type of riser device.
Representing each function on that device so the relevant Windows bus enumerator (such as a PCI bus enumerator) can detect it, and then locate and install appropriate drivers.
The system BIOS must provide a unique PCI SID for any riser card, assigned by the codec manufacturer. This is identical to current Logo Program requirements for audio and modem devices on a PCI add-on card—except these are system-board devices, so the PCI SID must reflect that of the system-board manufacturer.
If an OEM chooses a riser card and driver from any riser card driver manufacturer, the BIOS must populate the fields as follows:
-
The PCI SVID must reflect the Vendor ID assigned by the PCI Special Interest Group (SIG) to that OEM.
-
The SID must be unique for each AC ‘97 device configuration. For example, for a modem-on-motherboard (MoM), modem riser (MR), or audio modem riser (AMR) device, each SID must be unique.
If an OEM chooses a system board from a manufacturer that works with one or more codecs, the following applies:
-
The SVID must reflect the Vendor ID assigned by the PCI SIG to that system-board manufacturer.
-
The SID must be unique for each AC ‘97 codec/device configuration. For example, for a MoM, MR, or AMR device, each SID must be unique.
-
For an AMR riser, the system BIOS must properly implement the detection algorithm from Intel to verify that the hardware on an AMR/MR riser extension is actually present. The detection algorithm is available at ftp://download.intel.com/ial/scalableplatforms/audio/ac97bios.pdf.
Similar provisions exist in the CNR and ACR specifications.
See also AC ‘97 and AMR Plug and Play Design (http://www.microsoft.com/hwdev/tech/audio/AMR.asp)
A1.1.4.17 DELETED A1.1.4.18; A1.1.4.6 If system is PXE-capable, firmware supports remote boot via CIP BIOS Boot or EFI boot manager
PXE-capable systems must support booting from network per Compaq-Intel-Phoenix BIOS Boot Specification, Version 1.01, Appendix C (x86-based systems) or EFI boot manager (Itanium-based systems).
|