Windows Logo Program

B2.2 IEEE 1394 Controllers and Devices

B2.2.1 1394 Controllers/Devices - Windows Compatibility

B2.2.1.1 WDM support for devices that use the IEEE 1394 bus

B2.2.1.2 Windows compatibility and implementation notes (general)

B2.2.1.3 Plug and Play Specification for IEEE 1394

B2.2.1.4 IEEE 1394 Support in Windows 98 and Windows XP/Windows 2000

B2.2.2 1394 Controllers/Devices - Industry Standards

B2.2.2.1 Windows 98/Me/Windows XP: 1394 Open Host Controller Interface Specification, Revision 1.0

B2.2.2.2 1394 Trade Association Power Specification, Part 1: Cable Power Distribution; 1394 Trade Association Power Specification, Part 3: Power State Management

B2.2.2.3 IEEE 1394 Standards

• 
  IEEE 1394-1995 or later standards, and IEEE 1394a.
  
• 
  IEEE 1212-1991 and function discovery in IEEE 1212r
  Global Engineering Documents at http://global.ihs.com/.
  

B2.2.2.4 IEEE 1394 devices comply with appropriate industry-recognized transport and command standards

• 
  IEC 61883 Parts 1-6, including CIP (common isochronous packet) headers, CMP (connection management protocol), and FCP (function control protocol).
  
• 
  1394TA AV/C 3.0 and the AV/C subunit family of specifications, including AV/C Digital Interface Command Set VCR Subunit Specification, V. 2.0.1.
  
• 
  National Committee for Information Technology Standards (NCITS) Serial Bus Protocol (SBP-2) transport protocols (ANSI NCITS 3.25-1998 [SBP-2).]
  
• 
  National Committee for Information Technology Standards (NCITS) T10, Reduced Block Commands (RBC).
  
• 
  National Committee for Information Technology Standards (NCITS) T10 Multimedia Command Set 2 (MMC-2).
  
• 
  Storage class devices must conform to the ANSI standards for SBP-2 with the appropriate command set: RBC or MMC-2.
  
• 
  Printing devices using the SBP-2 protocol must conform to the guidelines set in "SBP-2 Support and Windows 2000," available at http://www.microsoft.com/hwdev/print/sbp2_w2000.htm.
  

B2.2.3 1394 Controllers/Devices - Quality

B2.2.3.1 Pass WHQL tests

Specifically see “IEEE 1394 Controllers” and device-specific topics in the HCT documentation.

B2.2.4 1394 Controllers/Devices - Windows Experience

B2.2.4.1 Windows 98/Me: Open HCI controllers and devices support advances defined in IEEE 1394a-1999

Including peak data rate requirements for Open Host Controller Interface.

B2.2.4.2 Device configuration ROM is correctly implemented

B2.2.4.3 Devices demonstrate interoperability with other devices

B2.2.4.4 Devices that initiate peer-to-peer communications support remote programming

B2.2.4.5 Devices use approved IEEE 1394 connectors and cables

B2.2.4.6 Self-powered devices propagate the power bus through each connector

B2.2.4.7 Vendor and model leafs support textual descriptor leaf format

B2.2.4.8 DELETED

B2.2.4.9 IEEE 1394-enabled system provides cable power source compliant with IEEE 1394a-1999

B2.2.4.10 Support remote programming through a remote control interface

B2.2.4.11 A system with externally accessible sockets provides a method for connecting to devices that only support IEEE 1394-1995 or IEEE 1394a-2000

There must not be a mixture of IEEE 1394-like media socket types on the back panel.

B2.2.4.12 Descriptors are required for Vendor_ID and Model_ID entries in the Configuration Status Register (CSR) space

B2.2.5 1394 Controllers/Devices - FAQs

B2.2.5.1 Current IEEE 1394 FAQs

B2.2.5.2 Power management requirements [Logo clarification]

Devices and controllers are not required to comply with 1394 Trade Association Power Specification, Part 3: Power State Management. This standard version is required with the release of a future operating system.

B2.2.5.3 DELETED

B2.2.R 1394 Controllers/Devices - Future Requirements

B2.2.R.1 Open HCI 1.1

B2.2.R.2 OHCI 1.1; host controller’s PHY supports data rates of S100 Mb/s, S200 Mb/s and S400 Mb/s

As specified in IEEE 1394-1995 and IEEE 1394a-2000.

B2.2.R.3:Networking adapters must support Remote NDIS over SBP-2

B2.3 Infrared/Wireless

B2.3.1 Infrared/Wireless - Windows Compatibility

B2.3.1.1 Windows XP/Windows 2000, Windows 98/Me: "IrDA Miniport NIC Drivers” and “Wireless WAN Objects" in the Windows DDK

B2.3.1.2 Windows compatibility and implementation notes (general)

B2.3.1.3 Windows XP/Windows 2000: IrDA Plug and Play Issues and Windows 2000

B2.3.1.4 Windows XP/Windows 2000: IrTran-P, IrLPT, and IrDA Networking Support under Windows 2000

B2.3.2 Infrared/Wireless - Industry Standards

B2.3.2.1 IrDA documents - Serial Infrared Physical Layer Specification; Control IR Specification

B2.3.3 Infrared/Wireless - Quality

B2.3.3.1 Pass WHQL tests

B2.3.4 Infrared/Wireless - Windows Experience

B2.3.4.1 Infrared (IR) device meets USB class specification for interfacing with IrDA Data and IrDA Control devices

See also IrDA Bridge Device Definition, 1.0 at http://www.usb.org/developers.

B2.3.4.2 System supports standard input speeds of 4 Mb/s

B2.3.4.3 System provides a separate, physically-isolated transceiver for each IR protocol supported

B2.3.4.4 Windows XP: Mobile PC IR devices, if implemented, support D0 and D3 states 

B2.3.4.5 Windows XP: Bluetooth wireless host controllers (radios with HCI) meet requirements

• 
  Support Plug and Play on the applicable bus (for example, USB).
  
• 
  Support the Bluetooth H:1 specification for host controllers, including the mechanism for reporting the version supported.
  
• 
  Support the bus-specific transport class extensions (for example, H:2-H:4) where applicable.
  

B2.3.4.6 Windows XP: Bluetooth-connected peripherals meet requirements

• 
  Meet all device class-specific Windows Logo requirements (for example, Section B3.0 for audio, Section B5.1 for HID, Section B6.1 for modem, and so on).
  
• 
  Comply with all applicable Bluetooth specifications, including design-applicable usage profiles.
  
• 
  Support Bluetooth Simple Discovery Protocol (SDP) and the PnPInformation Service Class.
  

B2.3.5 Infrared/Wireless - FAQs

B2.3.5.1 For systems that include Bluetooth, support Version 1.1 [Clarification]

The driver and firmware requirements in B2.3.4.5.and B2.3.4.6 will not be enforced until three months after release of the Microsoft’s standard Version 1.1 Bluetooth stack. After this three-month transition period, Bluetooth driver submissions must use the standard Microsoft Version 1.1 stack.

B2.3.R Infrared/Wireless - Future Requirements