X hits on this document





63 / 174

Microsoft Windows Logo Program System and Device Requirements  —  63

For vendors using serialized IRQ mode, the above is not relevant because they only need to connect the serial IRQ pin, and the ISA IRQ information will be sent to the PCI chip set serially; the ISA IRQ information can specify any of IRQ 0-15.

B2.1.4.4 See A3.4.4.5
B2.1.4.5 See A3.4.4.5
B2.1.4.2 CardBus cards are configured correctly

Required tuples are defined in PCCard-14 through PCCard-16 in "Design Guidelines for PC Card and CardBus, Version 1.1"

B2.1.4.3 16-bit PC Cards are configured correctly; driver supports sharing of level-mode interrupts

For complete requirements, see PCCard-11 through PCCard-13 in "Design Guidelines for PC Card and CardBus, Version 1.1"

CardBus systems support both 16-bit PC Card cards and CardBus cards. In this environment, interrupt sharing becomes an issue because CardBus controllers can use PCI interrupts, which are level-sensitive and sharable. To help alleviate interrupt limitations in CardBus systems, Windows can take advantage of PCI interrupt-sharing capabilities.

In cases where no ISA IRQs are available to a 16-bit PC Card card in a CardBus controller, the operating system will assign a PCI interrupt to the card. All 16-bit PC Card card drivers must "hook" the interrupt, whether it is sharable or not, before its hardware generates any interrupts.

B2.1.4.4 No user intervention; no system restart occurs when installing devices, except when required by the operating system

See PCCard-11 through PCCard-20 and 21 in "Design Guidelines for PC Card and CardBus, Version 1.1"PCCard-20, 21

B2.1.4.5 ZV-compatible 16-bit PC Cards comply with ZV standard definitions, and driver uses DirectDraw VPE

ZV-compatible PC Card drivers must use software interfaces based on 32-bit Microsoft DirectDraw® Video Port Extensions (VPE) in order to configure the graphics controller to receive video input using the ZV port. This includes programming the graphics controller to configure the format of the video data, its location on screen, and so on. VPE is part of Microsoft DirectX® APIs.

ZV card device drivers must handle dynamic graphics state changes, such as resolution changes, color depth changes, and switching to and from full-screen MS-DOS®–based applications.

B2.1.4.6 CardBus controller designed to support wake-from-D3cold supports PME# assertion from D3cold, and socket supplies Vaux power to cards in D3cold state

CardBus cards (which are by definition PCI devices) must comply with PCI Bus Power Management Interface Specification, Revision 1.1 or later, in order for power management to be implemented properly under Windows, which uses PME# as the wake-up signal. This is the only industry specification that ensures compatibility with the power management capabilities of Windows.

The CardBus card must use the CSTSCHG pin to signal wake-up events. This is because there is no PME# pin on the CardBus interface, and the CardBus card must use PME_EN in the card’s Configuration Space to enable wake-up events. Specifically, setting the PME_EN bit in the card’s Configuration Space must provide the same behavior as setting both the GWAK and WKUP bits in the card’s Function Event Mask register.

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views563
Page views563
Page last viewedTue Jan 17 13:03:43 UTC 2017