The Windows Logo Program Newsletter provides up to date information about the Windows Logo Program. Did you get this newsletter from a friend? Subscribe to the Windows Logo Program Newsletter.
Windows Logo Program Requirement Updates
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
BUSPORT-0001 - HD Audio controller implements additional requirements not specified in the Intel HD Audio specification: Added Server Device form factor
BUSPORT-0002 - HD Audio bus controllers follow applicable Plug and Play guidelines: Added Server Device form factor
BUSPORT-0006 - CardBus controller complies with industry standards and Windows-compatible configuration: Added Server Device form factor
BUSPORT-0008 - Open HCI controller support IEEE 1394a -1999: Added Server Device form factor
BUSPORT-0011 - Secure Digital I/O (SDIO) host controllers comply with industry standards and Windows KMDF requirements: Added Server Device form factor
BUSPORT-0013 - USB host controller that supports USB functionality complies with the appropriate specification: Added Server Device form factor
BUSPORT-0014 - USB host controller successfully enumerates new devices upon resume from suspend: Added Server Device form factor
BUSPORT-0017 - USB host controller maintains device state on resume from S1 or S3: Added Server Device form factor
BUSPORT-0027 - 1394b host controllers must provide at least one customer accessible nine pin 'bilingual' port: Added Server Device form factor
BUSPORT-0033 - 1394 host controllers pass all required 1394 Trade Assocation compliance tests: Added Server Device form factor
BUSPORT-0034 - USB Host Controller is USB IF certified: Added Server Device form factor
CONNECT-0012 - CardBus card is configured correctly: Added Server Device form factor
CONNECT-0017 - A single ExpressCard module that supports both USB and PCI Express interfaces implements a common serial number: Added Server Device form factor
CONNECT-0020 - Descriptors are implemented for Vendor_ID and Model_ID entries in the configuration status register (CSR) space: Added Server Device form factor
CONNECT-0021 - 1394 device configuration ROM is correctly implemented: Added Server Device form factor
CONNECT-0023 - Vendor and model leaf supports textual descriptor leaf format for 1394 devices: Added Server Device form factor
CONNECT-0024 - SBP-2-capable 1394 device complies with SBP-2-related requirements: Added Server Device form factor
CONNECT-0033 - Configuration space for PCI device is correctly populated: Added Server Device form factor
CONNECT-0034 - PCI Express requirement: Added Server Device form factor
CONNECT-0037 - PCI and PCI-X devices, that are PCI 2.3 compliant, support the interrupt-disable bit: Added Server Device form factor
CONNECT-0038 - PCI-X and PCI Express devices that use prefetchable memory BARs, implement 64-bit prefetchable memory base address registers (BARs): Added Server Device form factor
CONNECT-0042 - PCI device that reports PCI-X capability in the PCI configuration space and that generates interrupts may support MSI or MSI-X but is not required to do so: Added Server Device form factor
CONNECT-0044 - USB device complies with implementation details from the USB specification: Added Server Device form factor
CONNECT-0045 - USB serial numbers are implemented for specific device classes and are unique across specific device models: Added Server Device form factor
CONNECT-0046 - USB hub correctly identifies and reports the number of ports that the user can access: Added Server Device form factor
CONNECT-0048 - Isochronous USB device and driver requirement: Added Server Device form factor
CONNECT-0049 - USB hub or device that implements USB functionality complies with the related specification: Added Server Device form factor
CONNECT-0050 - USB hub with exposed ports is self-powered: Added Server Device form factor
CONNECT-0052 - USB device can be configured to any USB address: Added Server Device form factor
CONNECT-0054 - USB device responds to all string requests that the host sends to indexes: Added Server Device form factor
CONNECT-0056 - USB peripheral operates in function mode when connected to a computer host controller: Added Server Device form factor
CONNECT-0058 - Third-party INF files include the class “USB” only if the device is a USB host controller, a root, or an external hub: Added Server Device form factor
CONNECT-0059 - USB device responses to host requests are limited in size by the wLength field: Added Server Device form factor
CONNECT-0061 - USB device that uses the iSerialNumber field ensures unique serial numbers across devices of the same model: Added Server Device form factor
CONNECT-0062 - USB device that implements manufacturer-defined serial numbers contains valid characters: Added Server Device form factor
CONNECT-0069 - PCI and PCI-X devices, at a minimum, are PCI 2.1 compliant: Added Server Device form factor
CONNECT-0071 - USB Transfer Cable requirements: Added Server Device form factor
CONNECT-0093 - USB device is USB IF certified: Added Server Device form factor
CONNECT-0094 - All Bus powered USB devices support USB Selective Suspend after periods of inactivity: Added Server Device form factor
CONNECT-0104 - USB device that signals device-attach responds after at least 100 ms: Added Server Device form factor
CONNECT-0109 - Attached USB devices must be functional after resuming from system power states: Added Server Device form factor
CONNECT-0121 - IEEE 1394 devices meet Industry requirements: Added Server Device form factor
INPUT-0001 - Digitizers provide a high quality input experience: Added Server Device form factor
INPUT-0002 - Input gaming device are HID-compliant and use Direct Input APIs: Added Server Device form factor
INPUT-0008 - All HIDs meet USB HID specifications: Added Server Device form factor
INPUT-0016 - Windows Logo flag key is implemented on all keyboards supporting more than 50 keys, the Windows Vista Start Button design is required after June 30th 2007: Added Server Device form factor
INPUT-0018 - Smart card driver does not stop the system if required resources are not available: Added Server Device form factor
INPUT-0019 - Smart card driver can support multiple instances of the same device on a system: Added Server Device form factor
INPUT-0020 - Reader supports direct and inverse-convention smart cards: Added Server Device form factor
INPUT-0021 - Reader supports 258-byte packets in T=0 and 259-byte packets in T=1: Added Server Device form factor
INPUT-0022 - Reader supports smart card insertion and removal monitor: Added Server Device form factor
INPUT-0023 - Reader supports negotiable and specific modes according to the ISO/IEC specification: Added Server Device form factor
INPUT-0024 - Reader supports 3.5795-MHz minimum clock frequency: Added Server Device form factor
INPUT-0025 - Reader supports minimum data rate of 9600 bps: Added Server Device form factor
INPUT-0026 - Reader supports Reset command: Added Server Device form factor
INPUT-0027 - USB smart card CCID reader complies with USB Device Class Specification for USB Chip/Smart Card Interface Devices: Added Server Device form factor
INPUT-0028 - USB CCID reader issues NAK on interrupt pipe if device has no interrupt data to transmit: Added Server Device form factor
INPUT-0029 - Input device that implements a PIN data-entry keyboard complies with ISO: Added Server Device form factor
INPUT-0030 - Windows Smart Card Minidrivers meet Windows Smart Card Minidriver Version 5 Specifications and Certification Criteria: Added Server Device form factor
INPUT-0036 - Windows Smart Card Minidrivers meet Windows Smart Card Minidriver Version 6 Specifications and Certification Criteria: Added Server Device form factor
INPUT-0037 - Dynamic Keyboards meet the requirements listed here: Added Server Device form factor
Storage-0013 - Optical Drives meet Industry and Microsoft standards: Deleted "(Future Requirement)" from title and changed from factor from Future Requirement to Required.
The following are new requirements and policies that we are proposing. Please provide any feedback on these new requirements by October 14, 2008.
SYSFUND-0211 - Display adapter or Chipset for graphics solution on Server is based on WDDM: New
GRAPHICS-0075 - Graphics driver components comply with Application Verifier test criteria: New
GRAPHICS-0071 - Display adapter or Chipset complies with WDDM v1.1 required feature set: New
GRAPHICS-0072 - If the Display adapter or chipset implements the optional WDDM v1.1 video playback features they must follow the respective specifications: New
GRAPHICS-0073 - Display Driver designed for Display adaptor or chipset that contains an HD Audio interface supporting multi-channel HDMI or DisplayPort audio consistent with HD Audio must comply with HD Audio HDMI & DisplayPort DCN's: New
GRAPHICS-0075 - Graphics driver components comply with Application Verifier test criteria: New
Mobile Broadband Network Logo Program
Staying connected has become increasingly important to mobile computer users. Native support for mobile broadband network (MBN) will be introduced to allow mobile computer users to stay connected all the time. In response to this introduction, the Windows Logo Program will include a new section that applies to MBN devices. These requirements will be a part of the "Network Devices" group and will have a title that begins with "MBN". For more details on this new logo program, see LogoPoint.
MBN Requirements
NETWORK-0137 - MBN (mobile broadband network) devices must conform to NDIS and Microsoft WWAN Driver Model Specification requirements in the Windows Driver Kit (WDK).
NETWORK-0139 - MBN devices must work above the 4-GB address space.
NETWORK-0140 - MBN devices must support multiple device instances.
NETWORK-0195 - MBN devices must comply with power management specifications.
NETWORK-0196 - MBN devices must safeguard drivers against implementation of any vendor-specific advanced properties.
NETWORK-0197 - MBN devices must support unattended installation to enable Windows Update distribution.
NETWORK-0201 - MBN devices must meet performance criteria for data rate, uplink, downlink, and throughput.
NETWORK-0205 - MBN devices must work without any third-party Connection Manager.
NETWORK-0207 - MBN devices must meet the performance target for various operations specified in the WWAN Driver Model Specification. (MBN is known as WWAN in the WDK.)
NETWORK-0208 - MBN devices must implement the NDIS 6.20 Media Extensibility Model and support IP packet-handling capability as defined in the Microsoft WWAN Driver Model Specification. (MBN is known as WWAN in the WDK.)
NETWORK-0209 - MBN devices must implement all SMS functionality as defined in the Microsoft WWAN Driver Model Specification.
NETWORK-0210 - MBN devices must support provisioning of connectivity information.
NETWORK-0277 - MBN devices must support Teredo, 6To4, and VPN tunneling technologies.
WLAN Change in WLK Coming
The current Windows Logo Kit (WLK), version 1.2, supports wireless LAN (WLAN) testing by using a software-based access point that runs on both Atheros and Realtek WLAN NICs. The next version of the WLK will support testing WLAN drivers only by using the Atheros WLAN NICs. You will not be required to use the next kit for submissions until June 2009, but we wanted to provide early notice of this change to help your planning activities. If you have further questions, send us an e-mail at wlanndt@microsoft.com.
WDK Survey: Help Improve the Documentation in the Kit and on MSDN
The Windows Driver Kit (WDK) documentation group would like your feedback on the documentation that is provided with the kit and on MSDN. We know your schedule is busy, so we developed a survey that is significantly shorter than previous surveys. Click here to complete this survey, which should take just a few minutes and will be available for your feedback until October 10, 2008.
As you may have noticed in previous years, we do take your feedback very seriously and look forward to improving our product based on your input. Please watch this newsletter for details on survey results coming in November.
|
