IEEE 1394 Streaming Filter Driver Use From an Application (Windows CE 5.0)
An application begins to communicate with a subunit driver, and must simply be aware that there are two sets of IOCTL commands that it may send to the subunit driver. The first set is the subunit driver specific set, designed to actually control whatever functionality that subunit is designated as providing. The second set is the streaming set, provided by the streaming filter driver.
An application merely is required to use the IOCTL commands, and functionality should be transparent.
An application makes the decision about what device it is communicating with by how it locates and opens an individual subunit. Subunits register themselves according to the API they export, their device Interfaces are registered, so an application can use Setupapi.dll calls to obtain a list of all subunits currently on the bus that conform to a known API standard. One of which might be VCRs, another might be tuners, and so on.
After locating and opening the subunit driver by passing the textual device name obtained from Setupapi.dll functions to CreateFile to obtain a file handle, the application will have the ability to send IOCTL commands that specifically affect the targeted device and only the targeted device.
See Also
Plug Finding | Application Session Starting | Application Session Stopping | Application Session Data Transfer | Application Session Buffers | IEEE 1394 Streaming Filter Driver Differences in Media Types
Send Feedback on this topic to the authors