X hits on this document





27 / 174

Microsoft Windows Logo Program System and Device Requirements  —  27

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).

Mobile PC Note These requirements only apply to mobile PC systems that include either a system board network adapter or a preinstalled mini-PCI LAN adapter.

See A5.0 for complete Itanium-based firmware requirements.

A1.1.5 Multiprocessor system compatibility requirements
A1.1.5.1 Comply with ACPI specification for multiprocessor support

x86-based: Comply with ACPI 1.0b.

Itanium-based: Comply with Multiple APIC Description Table (MADT) in ACPI 2.0, Section

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views338
Page views338
Page last viewedThu Oct 27 11:07:26 UTC 2016