Microsoft Windows Logo Program System and Device Requirements — 126
All resource settings must be viewable in the Device Manager and in the adapter properties dialog boxes. All resource settings that can be changed by the user must be changed using the standard Windows user interface, not through the use of INI files or other setting files.
This requirement implies that all device resources must be set and read through the standard interfaces provided by the bus on which the device resides. For PCI devices, this interface is the PCI configuration space. Also, device parameter settings must be stored in the registry.
B188.8.131.52 Wireless networking requirements
B184.108.40.206.1 Wireless network media adapters must meet all requirements for network adapters except where noted.
B220.127.116.11.2 IEEE 802.11 wireless networking adapters support 11 Mb/s signaling using Direct Sequence Spread Spectrum.
B18.104.22.168.3 Bluetooth Host Controllers (HCI)
Windows uses Bluetooth Wireless technology as a wireless local bus and cable replacement. Therefore, Bluetooth HCI (radios with PC interface) do not need NDIS miniports. Requirements for Bluetooth HCI are listed in B22.214.171.124.
B126.96.36.199.3 Wireless networking media adapters support wireless extensions to NDIS
Wireless extensions to NDIS are documented in “Network-Dependent Wireless Objects” in Network Drivers in the Windows DDK. These extensions are based on the work of the Portable Computer and Communications Association.
B188.8.131.52.4 Wireless network media adapters must meet all requirements for network adapters
IEEE 802.11 devices must support the appropriate OIDs.
IEEE 802.11 devices must be compatible with Wi-Fi
Information on Wi-Fi can be found at http://www.wi-fi.org
Flash based firmware drivers must update without user intervention.
B184.108.40.206 IEEE 802.x network adapter and driver that implement QoS support priority for IEEE 802-style networks.
Windows Quality of Service (QOS) components provide link layer priority information to NDIS 5.0 miniport drivers in each transmitted packet’s NDIS_PER_PACKET_INFO structure.
Priority values are derived by mapping Internet Engineering Task Force (IETF) Integrated Services (IntServ, RFC 1663) service typed to IEEE 802.1p priority values, referred to as the user priority object. Current IETF references include:
The Subnet Bandwidth Manager.
Framework for integrated services over 802 networks.
Mapping integrated services to 802.1p.
The IntServ service type used for the mapping is determined by QOS-aware applications or, on behalf of the application, by QOS-aware operating system components. Driver support for link layer priority information must adhere to IEEE 802.lp priority values.
IEEE 802.1p/q-capable Ethernet drivers must use the priority level indicated in the NDIS_PER_PACKET_INFO structure to generate the corresponding field in the IEEE 802.1p/q MAC headers of transmitted packets. Similarly, these drivers must extract the appropriate information
© 1999-2002 Microsoft Corporation. All rights reserved.