This section summarizes command protocol requirements for integration and interoperability of the IEEE 1394 bus with IEEE 1394 peripherals such as consumer electronics devices.
10. Device command protocols conform to Win32 Device Class Interfaces
| Required |
Support in the Windows operating systems for new device classes (for example, Digital VCR) will leverage the Win32 Driver Model (WDM) so that a single device class driver binary will support the same devices on both Windows and Windows NT.
New Win32 device driver interfaces are based on available industry standards. Areas of standardization include generic command and protocol standards for Audio, Imaging, and Storage class interfaces, spanning multiple device types in each category. Win32 class drivers provide hardware-independent, class-specific interfaces that can be extended by hardware-specific device minidrivers.
Devices that comply with interface standards such as HCI for IEEE 1394 eliminate the need for developing and testing third-party device drivers. Other devices will require implementation of a simple minidriver to extend Microsoft-supplied generic class interfaces to support a specific device. In limited, but special cases, it might be necessary for a third party to implement both a class and a minidriver to support a new device.
11. Consumer A/V device interfaces comply with industry standards
| Required |
These standards include Digital Interface for Consumer Electronic Audio/Video Equipment (Draft 2.1 or later) by Philips Electronics N.V., Matsushita Electric Ind. Co., Ltd, Thomson Multimedia, Sony Corporation, October, 1995 (also available from IEEE 1394 Trade Association).
This specification outlines implementation requirements for interoperability of consumer audio/video equipment over IEEE 1394. It includes a clarifying sample of a device configuration ROM and CSRs. Specific areas for compliance are summarized here:
Devices capable of isochronous data handling must support the CIP format to ensure interoperability of isochronous data between consumer A/V nodes on an IEEE 1394 bus.
CMP is Required to enable management of isochronous connections including swift allocation and deallocation of channels following a bus reset. Plug Control Registers (PCRs) are Required to facilitate CMP necessary for isochronous data flow management.
FCP is Required for compatibility with Microsoft-supplied consumer-A/V class device drivers. (for example, digital cameras and camcorders).
Part 1 defines command packet formats for the simple command-response FCP protocol for asynchronous control of digital A/V devices. Parts 2 and 3 specify packet format and transmission timing for Standard Definition (SD) and High Definition (HD) digital VCR data respectively.
12. Imaging devices support interface standards
| Recommended |
The Win32 Imaging Class drivers (for cameras, camcorders, printers, scanners, and so on) will be based on one or more of the following standards:
For more information, see the Microsoft Win32 Driver Model DDK.
13. Audio devices support interface standards
| Recommended |
The Win32 Audio Class driver (for component audio, musical instruments, and so on) will be implemented based on one or more of the following:
For more information, see the Microsoft Win32 Driver Model DDK.
14. Support for SCSI-3 protocol
| Recommended |
Where feasible, designs should leverage common command protocols defined for SCSI-3. Storage devices in particular can take advantage of common commands and protocols based on Command Descriptor Blocks (CDBs):
SCSI-3 SBP specifies a command delivery protocol developed to extend existing parallel SCSI protocol to support new features (for example, isochronous data streaming) provided by the IEEE 1394 bus. The SCSI-3 SBP is intended for use with SCSI-3 primary commands for block I/O and multimedia devices.