

The CIP_FRAME structure describes a frame to be attached to an input or output plug. This structure is a CIP data format which is used by CMP_CONNECT_VER2. A frame can be canceled while the stream is running. The request cancels an attached frame buffer. This structure is used in an attach frame request. This structure is used to register or deregister the PBUS_RESET_ROUTINE callback. The BUS_RESET_DATA structure specifies the context for the extended bus reset notification routine. The BUS_GENERATION_NODE structure is used in conjunction with the Av61883_GetUnitInfo request to retrieve bus characteristics. The AV_PCR structure specifies settings for an input or output plug. The AV_61883_REQUEST structure is used to pass requests to the IEC-61883 protocol driver. The ADDRESS_RANGE structure describes a range in a IEEE 1394 device's address space. The ADDRESS_OFFSET structure specifies the 48-bit address within a device's IEEE 1394 address space. The ADDRESS_FIFO structure is an entry in a singly-linked list of MDLs that the REQUEST_ALLOCATE_ADDRESS_RANGE IEEE 1394 bus request uses. This routine is called for plug notification. This routine is called for plug monitoring.
#Microsoft 1394 legacy driver driver
This is a caller-supplied function to be called by the protocol driver when the 1394 bus is reset. This enumeration specifies the type of a plug.

This enumeration specifies the location of a plug. This enumeration specifies a connection type. The driver has access to all operations provided by the IEEE 1394 bus and its host controller through this request.Īn IEC-61883 client driver uses the IRP_MJ_INTERNAL_DEVICE_CONTROL IRP with IoControlCode IOCTL_61883_CLASS to communicate with 1394 driver stack using the IEC-61883 protocol. IOCTLsĪn IEEE 1394 driver uses the IRP_MJ_INTERNAL_DEVICE_CONTROL IRP, with IoControlCode IOCTL_1394_CLASS, to communicate with the bus driver. To develop IEEE 1394 bus, you need these headers:įor the programming guide, see IEEE 1394 bus. Overview of the IEEE 1394 bus technology.
