Ana səhifə

Windows Logo Program


Yüklə 1.03 Mb.
səhifə18/37
tarix18.07.2016
ölçüsü1.03 Mb.
1   ...   14   15   16   17   18   19   20   21   ...   37

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: "Supporting USB Devices" in the Windows DDK
B2.6.1.2 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/usb/
B2.6.1.3 USB Plug and Play IDs and Selecting Device Drivers to Load

http://www.microsoft.com/hwdev/busbios/usbpnp.htm

B2.6.2 USB Controllers/Devices - Industry Standards

B2.6.2.1 OpenHCI: Open Host Controller Interface Specification for USB, Release 1.0a

[USB-0081]
http://www.microsoft.com/hwdev/respec/busspecs.htm
Universal HCI specification is also accepted.
B2.6.2.2 USB class specifications

[USB-0088; SDG3:60]
http://www.usb.org/developers/devclass.html
B2.6.2.3 USB 1.1 Specification (or later)

[USB-0081; SDG3:57]
http://www.usb.org/developers/docs.html

B2.6.3 USB Controllers/Devices - Quality


WHQL Test Specification References:
Chapter 9: USB Test Specification

See B1.3.


B2.6.3.1 Pass all applicable WHQL tests

This includes USB 1.1 Chapter 9 and Chapter 11 tests:

  • Device or hub has unique VID/Program ID (PID) combination.

  • Serial number, if implemented, is unique.

  • Hub correctly reports the number of ports accessible by the user.


Windows XP: See “USB Controllers,” “USB Hubs,” and device-specific and system-specific topics in the HCT documentation.
B2.6.3.2 SEE B2.6.3.1



B2.6.4 USB Controllers/Devices - Windows Experience


Design Guideline References:
PC 2001 System Design Guide, Chapter 6, "Buses and Interfaces"
Hardware Design Guide Version 3.0 for Microsoft Windows 2000 Server, Chapter 2
B2.6.4.1 Devices comply with USB power management requirements

[USB-0087; SDG3:59]
B2.6.4.2 Connections use USB icon, per USB 1.1 specification
B2.6.4.3 USB host controller can wake the system

[USB-0085]
B2.6.4.4 Devices and drivers support maximum flexibility of hardware interface options

[USB-0084; SDG3:58]
B2.6.4.5 Devices meet requirements in related USB device class specifications

[USB-0088; SDG3:60; see also FAQ B2.6.5.2]
B2.6.4.6 Hub or device that supports USB 2.0 complies with USB 2.0 Specification

[USB-0081]
B2.6.4.7 USB devices install and perform at least some functions expected by end users for that class of device, without preloading software

[USB-0089; SDG3:62]

Without loading a specific driver, USB devices having native operating system class driver support provide the typical functions supported by devices within each class, as defined in the USB device class specifications. After device specific driver installation, the device must be fully functional.

Driver packages can force re-enumeration by pointing to their INF file; see UpdateDriverForPlugAndPlayDevices in the Windows DDK for information.

B2.6.4.8 USB hubs are self-powered

[USB-0086; SDG3:61]

This requirement does not apply for hubs integrated into USB keyboards.



Mobile PC Note: This requirement does not apply for hubs integrated into mobile systems.

B2.6.5 USB Controllers/Devices - FAQs

B2.6.5.1 Current USB-related FAQs

See http://www.microsoft.com/winlogo/hardware/usb/.
B2.6.5.2 USB device definition [Logo Program clarification]

[USB-0088; SDG3:46]

Any device that plugs into 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 result, these requirements apply for any device that plugs into 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.


FAQ Date: October 7, 1998

B2.6.R USB Controllers/Devices - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/usb/.
B2.6.R.1 USB isochronous devices do not request more than 25 percent of the total bandwidth at any time

B3.0 Audio Devices

B3.1 General Audio


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.

B3.1.1 General Audio - Windows Compatibility

B3.1.1.1 WDM device driver support for audio

[AUD-0326; AUD-0337]

Device driver conforms to the WDM implementation guidelines and “Audio Drivers” reference in the Windows DDK.

See FAQ B3.1.5.8.

B3.1.1.2 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/audio/
B3.1.1.3 Audio Codec (AC) '97 and AMR Plug and Play Design

See FAQ B3.1.5.2.
http://www.microsoft.com/hwdev/audio/AMR.htm.
B3.1.1.4 WDM Audio Drivers for Windows XP/Windows 2000

http://www.microsoft.com/hwdev/devdes/wdmaudio.htm
DirectSound® driver support: see “DirectSound DDK” in the Windows DDK.
B3.1.1.5 Windows Me: USB MIDI takes advantage of built-in operating system support

See “Audio Drivers” in the Windows DDK.

B3.1.2 General Audio - Industry Standards

B3.1.2.1 AC ’97 Component Specification

http://developer.intel.com/ial/scalableplatforms/audio/index.htm
B3.1.2.2 Audio Device Class Power Management Reference Specification, V. 2.0

[AUD-0336; see also see FAQ B3.1.5.7]
http://www.microsoft.com/hwdev/specs/pmref/pmaudio.htm
B3.1.2.3 DLS Specification, V. 1.0 or later

[AUD-0328]
http://www.midi.org/
B3.1.2.4 Personal Computer Audio Quality Measurements

http://www.cirrus.com/products/papers/meas/meas.html
B3.1.2.5 USB Device Class Definition for Audio Devices, V. 0.9 or later

[AUD-0335]
http://www.usb.org/developers/docs.html
B3.1.2.6 USB Device Class Definition for MIDI Devices, V. 0.9 or later

http://www.usb.org/developers/docs.html

See B5.1.5 for HID control requirements.


B3.1.3 General Audio - Quality


WHQL Test Specification References:
Chapter 16: Audio Test Specification
B3.1.3.1 Pass WHQL tests

See B1.3.
Windows XP: See “Audio” in the HCT documentation.
B3.1.3.2 SEE B1.3



B3.1.4 General Audio - Windows Experience


Design Guideline References:
PC 2001 System Design Guide, Chapter 11, "Audio"
B3.1.4.1 No legacy audio components

[SYS-0041; AUD-0322]

No ISA; no legacy hardware interfaces for MS-DOS-based applications.


B3.1.4.2 Full Duplex—Internet Telephony

[AUD-0324; AUD-0325; see also FAQ B3.1.5.9]
B3.1.4.3 Plays sounds before and after Suspend/Resume

[SYS-0003.4]
B3.1.4.4 Record and Playback works properly—WHQL Audio test: Audio performance

[AUD-0329; see also FAQ B3.1.5.3]

Mobile PC Note: Exceptions for mobile PCs are defined in the following table, “Minimum Performance Requirements.”

Advances on previous requirements:



  • Full duplex operation is supported for all sampling rates; sampling rates are time synchronized. [AUD-0325]

  • Digital playback and recording values are increased from 20 Hz to 30 Hz Full-scale input voltage changed from 2.0 to 1.0. [AUD-0329]

Minimum Performance Requirements

Requirement

Value

Full-scale input voltage:




FSIV (A-D-PC) line input

1.0 Vrms

FSIV (A-D-PC) microphone input

100 mVrms

Full-scale output voltage:




FSOV (PC-D-A) line output

1.0 Vrms [note 1]

Digital playback (PC-D-A) for line output:

Frequency response (-3 dB)
    48.0 kHz source material

20 Hz to 19.2 kHz [note 4]

Dynamic range (DR)

80 dB FS A [note 3, 4]

THD+N (-3 dB FS)

-65 dB FS [note 4]

Digital playback (PC-D-A) for speaker output with 8-ohm load:

Frequency response (-3 dB)
    48.0 kHz source material

100 Hz to 19.2 kHz [note 4]

Dynamic range (DR)

80 dB FS A [note 3, 4]

THD+N (-3 dB FS)

-65 dB FS [note 4]

Digital recording (A-D-PC) for line input: [note 2]

Frequency response
    48.0 kHz destination

20 Hz to 19.2 kHz [note 4]

Passband ripple

<+/-0.5 dB

Dynamic range (DR)

70 dB FS A [note 4]

THD+N (-3 dB FS)

-60 dB FS (input referenced) [note 4]

Digital recording (A-D-PC) for microphone input:

Frequency response (-3 dB)
    22.05 kHz destination

100 Hz to 8.8 kHz

Passband ripple

<+/-0.5 dB

Dynamic range (DR)

70 dB FS A [note 4]

THD+N (-3 dB FS)

-60 dB FS (input referenced) [note 4]

Line output cross-talk:

Channel separation
between left and right line-out channels
(measured at 10 kHz)

60 dB [note 4]

Sampling frequency accuracy:

Playback

0.1%

Record

0.1%

Notes:

Note 1: For 3.3 V audio codec, the required Full Scale Output Voltage for line output is 0.7 Vrms.

Note 2: Line input to speaker output is a requirement only if a line output is not supported.

Note 3: Decibels relative to full scale (FS), measured using "A weighting" filters.

Note 4 - Mobile PC Notes:

  • The dynamic range requirements are relaxed from previous requirements by 10 dB FS.

  • The THD+N requirements are relaxed by 10 dB FS.

  • The required frequency response is 30 Hz to 15 kHz, measured using 3 dB corners.

  • The cross-talk requirements are relaxed by 10 dB FS.
B3.1.4.5 Audio subsystem supports full-duplex operation at independent sampling rates

[AUD-0325]
B3.1.4.6 Analog microphone input meets jack and circuit specifications

[AUD-0331]
B3.1.4.7 Audio driver reports sample position for stream synchronization

[AUD-0326, AUD-0334]

Maximum allowable latency is 1 ms.


B3.1.4.8 PCI audio device meets minimum requirements

  • Supports initiator, target, and block transfer. [AUD-0333]

  • PCI device supports efficient audio buffer management. [AUD-0334

  • Does not use ISA-based resources. [AUD-0322]

  • Is digital ready. [AUD-0323]
B3.1.4.9 USB audio device uses HID controls

[AUD-0335]
B3.1.4.10 Support required for DirectX functions as specified in the DirectX DDK

Windows XP: Support Microsoft DirectX® 8 (DirectX DDK is included in the Windows DDK).
B3.1.4.11 Windows XP: Device implements DRM support as defined in Windows DDK

"Digital Rights Management Reference” in the Windows DDK.

[see FAQ B3.1.5.10]



Windows Me: If this support is implemented, see also http://www.microsoft.com/hwdev/audio/DRM.htm.
B3.1.4.12 Audio subsystem requirements

[AUD-0330, 0339]

  • Supports acoustic echo cancellation reference inputs. [AUD-0330]

  • Does not rely on analog mixing. [AUD-0339]
B3.1.4.13 Headset microphone used for speech recognition meets performance requirements

[AUD-0332]

B3.1.5 General Audio - FAQs

B3.1.5.1 Current related Audio FAQs

See http://www.microsoft.com/winlogo/hardware/audio/.
B3.1.5.2 AC ‘97 devices on riser cards [Logo Program clarification]

[SYS-0034]

AC ‘97 devices on riser cards such as AMR, CNR, and MR can be tested and receive the "Designed for Windows" Logo based on the following requirements:



  • 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 SIG to that OEM.

  • The SID must be unique for each AC ‘97 device configuration. For example, for a MoM, MR, or 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.

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

For more information about WHQL testing for riser cards, see the WHQL web site at http://www.microsoft.com/hwtest/.

See AC '97 and AMR Plug and Play Design at http://www.microsoft.com/hwdev/audio/AMR.htm.


FAQ Date: June 2, 1999
B3.1.5.3 Audio Minimum Performance Requirements [Revision]

[AUD-0325-0329]

Data formats and performance requirements are defined at B3.1.4.4.


B3.1.5.4 Basic data formats for audio hardware [Revision]

[AUD-0325-0329]

Data formats and performance requirements are defined at B3.1.4.4.


B3.1.5.5 Analog microphone input [Revision]

[AUD-0331]

Requirements are now defined at B3.1.4.6.


B3.1.5.6 PCI device supports non-DWORD-aligned audio buffers [Clarification]

[AUD-0334]

This is a recommendation, not a requirement. Replaced in B3.1.4.8.


FAQ Date: December 22, 1998; June 16, 2000
B3.1.5.7 PCI power management requirements [Clarification]

[AUD-0336]

PCI Bus Power Management Interface Specification, Revision 1.1 or later, is the only industry specification that ensures compatibility with the power management capabilities of Windows 2000 and Windows XP.
FAQ Date: November 12, 1999
B3.1.5.8 WDM Audio Driver Requirements [Logo Program Clarification]

[AUD-0337]

WDM audio driver requirements apply based on the preinstalled operating system:



  • Windows XP/Windows 2000 and Windows Me Audio Drivers: All devices are required to use WDM drivers.

  • Audio drivers for Windows 98 Second Edition: All audio devices are required to use WDM, with the exceptions noted below. There will be an operating system update released early next year that will address the technical deficiencies. As of July 1, 2000, devices in either of the following two categories cannot use VxD drivers:

  • Exception #1: Audio devices that also contain a game port: Windows 98 Second Edition does not support WDM game ports. Audio devices that use WDM drivers must provide a VxD module for the game port. Windows 98 Second Edition has known issues with the interconnection between WDM audio devices and the VxD game port services. The operating system update will address these issues.

  • Exception #2: Audio devices that use WavePCI and provide hardware acceleration of Microsoft DirectSound: There are two classes of WDM audio drivers, WaveCyclic and WavePCI. The former is intended for those devices that utilize looping memory buffers to transfer audio to the device. The latter is geared towards PCI devices that use scatter-gather to transfer data. Windows 98 Second Edition has known issues with WavePCI and DirectSound hardware acceleration. These issues have been addressed in later operating systems.

  • Audio drivers for the initial release of Windows 98: Systems that ship with Windows 98 may use VxD audio drivers indefinitely (due to WDM audio issues in Windows 98). This does not apply to Windows 98 Second Edition.

  • Audio drivers for Windows NT 4.0: Because Windows NT 4.0 does not support WDM, the WDM requirement does not apply for testing systems under Windows NT 4.0.
    FAQ Date: November 29, 1999
B3.1.5.9 Audio subsystem supports basic data formats [Revision]

[AUD-0324]

Hardware sample rate conversion (SRC) is not required when the Microsoft software SRC is used. Windows 98/Me and Windows 2000 provide software mixing and SRC, which eliminate the need for hardware to support any sampling rate other than 48 kHz.


FAQ date: February 28, 2001
B3.1.5.10 DRM legacy function calls [Clarification]

Windows XP: to pass Windows Logo testing for Secure Audio Path for Digital Rights Management as DRM compliant with DRM Level = 1200 (which is the security level for Windows XP), audio drivers for Windows XP must not call DrmForwardContentToFileObject. If an audio driver calls DrmForwardContentToFileObject, it will be qualified as DRM compliant with DRM Level = 1100, which is the security level for Windows Me.

B3.1.R General Audio - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/audio/.
1   ...   14   15   16   17   18   19   20   21   ...   37

Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət