X hits on this document





76 / 174

Microsoft Windows Logo Program System and Device Requirements  —  76

B2.5.R.2 Functions in a multifunction PCI device do not share writable PCI Configuration Space bit.

Windows treats each function of a multifunction PCI device as an independent device. As such, there can be no sharing between functions of writable PCI configuration space bits (such as the Command register).

B2.5.R.3 Hot-Plug PCI supported via compatible driver solutions or ACPI

Windows Longhorn supports dynamic enumeration, installation, and removal of PCI devices if the implementation strictly complies with the PCI Standard Hot-Plug Controller and Subsystem Specification (SHPC), Revision 1.0, and the Windows Logo Program requirements for the SHPC driver.

SHPCs that have been designed to meet these requirements do not need any ACPI implementations or vendor-supplied filter drivers. SHPCs will be required for systems running Windows "Longhorn" that provide Hot-Plug PCI support. Other hot-plug implementations will work under Windows only if there is a supported hardware insert/remove notification mechanism, such as a bus standard. An example of an implementation based on an appropriate standards-based notification mechanism is a CardBus bus controller.

For more information about Windows and PCI Hot Plug, see   "Hot-Plug PCI and Windows" at http://www.microsoft.com/hwdev/bus/pci/hotplugpci.asp.

B2.5.R.4 PCI 2.3 Interrupt Disable

PCI 2.3 Interrupt Disable is required for Longhorn logo for all devices that are first submitted for logo after January 1st, 2004. All devices being submitted for logo testing must include this capability by January 1st, 2006. See section 6.2 of the PCI Local Bus Specification Revision 2.3.

B2.6 USB Controllers and Devices

All general requirements in B1.0 are included by reference.

Note that related BIOS and system-level requirements are included with the Windows Logo Program requirements for systems, as defined in Appendix A.

B2.6.1 USB Controllers/Devices - Windows Compatibility

B2.6.1.1 WDM support for devices that use the USB bus: "Introduction to USB Drivers" in the Windows DDK

Any device that is connected (externally or internally) to a USB port is tested as a USB device—that is, the device provides the capabilities of one or more functions, a hub to the host, or both. As a result, these requirements apply for any device that is connected to a USB port: the USB specification and any related USB device class specification, plus the Windows Logo Program requirements for USB and the related device class.

B2.6.1.2 Windows compatibility and implementation notes (general)


Note: This is a general reference, not a requirement.

B2.6.1.3 USB Plug and Play IDs and Selecting Device Drivers to Load


Note: This is a general reference, not a requirement.

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views295
Page views295
Page last viewedTue Oct 25 13:07:21 UTC 2016