1394.h header
This header is used by ieee. For more information, see:
1394.h contains the following programming interfaces:
IOCTLs
| IOCTL_1394_CLASS An IEEE 1394 driver uses the IRP_MJ_INTERNAL_DEVICE_CONTROL IRP, with IoControlCode IOCTL_1394_CLASS, to communicate with the bus driver. The driver has access to all operations provided by the IEEE 1394 bus and its host controller through this request. |
Structures
| ADDRESS_FIFO 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. |
| ADDRESS_OFFSET The ADDRESS_OFFSET structure specifies the 48-bit address within a device's IEEE 1394 address space. |
| ADDRESS_RANGE The ADDRESS_RANGE structure describes a range in a IEEE 1394 device's address space. |
| BUS_RESET_DATA The BUS_RESET_DATA structure specifies the context for the extended bus reset notification routine. |
| CONFIG_ROM The CONFIG_ROM structure is used to contain the first 24 bytes of an IEEE 1394 device's configuration ROM. |
| CYCLE_TIME The CYCLE_TIME structure contains the IEEE 1394 isochronous cycle time. |
| GET_LOCAL_HOST_INFO1 The GET_LOCAL_HOST_INFO1 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel GET_HOST_UNIQUE_ID. |
| GET_LOCAL_HOST_INFO2 The GET_LOCAL_HOST_INFO2 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel GET_HOST_CAPABILITIES. |
| GET_LOCAL_HOST_INFO3 The GET_LOCAL_HOST_INFO3 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_POWER_SUPPLIED. |
| GET_LOCAL_HOST_INFO4 The GET_LOCAL_HOST_INFO4 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_PHYS_ADDR_ROUTINE. |
| GET_LOCAL_HOST_INFO5 The GET_LOCAL_HOST_INFO5 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_HOST_CONFIG_ROM. |
| GET_LOCAL_HOST_INFO6 The GET_LOCAL_HOST_INFO6 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_HOST_CSR_CONTENTS. |
| GET_LOCAL_HOST_INFO7_W2K The GET_LOCAL_HOST_INFO7_W2K structure is returned by a REQUEST_GET_LOCAL_HOST_INFO request with u.GetLocalHostInformation.nLevel set to GET_HOST_DMA_CAPABILITIES. |
| GET_LOCAL_HOST_INFO7_WXP The GET_LOCAL_HOST_INFO7_WXP structure is returned by a REQUEST_GET_LOCAL_HOST_INFO request with u.GetLocalHostInformation.nLevel set to GET_HOST_DMA_CAPABILITIES. |
| GET_LOCAL_HOST_INFO8 The GET_LOCAL_HOST_INFO8 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request with u.GetLocalHostInformation.nLevel set to GET_HOST_DDI_VERSION. |
| IO_ADDRESS The IO_ADDRESS structure specifies the 1394 64-bit destination address for read, write and lock operations. |
| IRB Drivers use this structure to pass most requests to IEEE 1394 bus driver. |
| IRB_REQ_ALLOCATE_ADDRESS_RANGE This structure contains the fields necessary for the 1394 stack to carry out a request to allocate an address range. |
| IRB_REQ_ASYNC_LOCK This structure contains the fields necessary for the 1394 stack to carry out an asynchronous lock request. |
| IRB_REQ_ASYNC_READ This structure contains the fields necessary for the 1394 stack to carry out an asynchronous read request. |
| IRB_REQ_ASYNC_STREAM This structure contains the fields necessary for the 1394 bus driver to carry out an asynchronous write request. |
| IRB_REQ_ASYNC_WRITE This structure contains the fields necessary for the 1394 stack to carry out an asynchronous write request. |
| IRB_REQ_BUS_RESET This structure contains the fields necessary for the 1394 bus driver to create a bus reset request. |
| IRB_REQ_BUS_RESET_NOTIFICATION This structure contains the fields necessary for the 1394 bus driver to carry out a bus reset notification request. |
| IRB_REQ_CONTROL This structure contains the fields necessary for the 1394 bus driver to carry out a control request. |
| IRB_REQ_FREE_ADDRESS_RANGE This structure contains the fields necessary for the 1394 stack to carry out a free address range request. |
| IRB_REQ_GET_1394_ADDRESS_FROM_DEVICE_OBJECT This structure contains the fields necessary to carry out a Get1394AddressFromDeviceObject request. |
| IRB_REQ_GET_CONFIG_ROM This structure contains the fields necessary for the bus driver to carry out a GetConfigRom request. |
| IRB_REQ_GET_CONFIGURATION_INFORMATION This structure contains the fields necessary for the 1394 bus driver to carry out a GetConfigurationInformation request. |
| IRB_REQ_GET_GENERATION_COUNT This structure contains the fields necessary for the 1394 bus driver to carry out a GetGenerationCount request. |
| IRB_REQ_GET_LOCAL_HOST_INFORMATION This structure contains the fields necessary for the 1394 bus driver to carry out a GetLocalHostInformation request. |
| IRB_REQ_GET_MAX_SPEED_BETWEEN_DEVICES This structure contains the fields necessary in order for the Bus driver to carry out a GetMaxSpeedBetweenDevices request. |
| IRB_REQ_GET_SPEED_TOPOLOGY_MAPS This structure contains the fields necessary for the 1394 bus driver to carry out a GetSpeedTopologyMaps request. |
| IRB_REQ_ISOCH_ALLOCATE_BANDWIDTH This structure contains the fields necessary in order for the Bus driver to carry out an IsochAllocateBandwidth request. |
| IRB_REQ_ISOCH_ALLOCATE_CHANNEL This structure contains the fields necessary in order for the 1394 bus driver to carry out an IsochAllocateChannel request. |
| IRB_REQ_ISOCH_ALLOCATE_RESOURCES_W2K The IRB_REQ_ISOCH_ALLOCATE_RESOURCES_W2K structure contains the fields necessary for the 1394 bus driver to carry out an IsochAllocateResources request. |
| IRB_REQ_ISOCH_ALLOCATE_RESOURCES_WXP The IRB_REQ_ISOCH_ALLOCATE_RESOURCES_WXP structure contains the fields necessary for the 1394 bus driver to carry out an IsochAllocateResources request. |
| IRB_REQ_ISOCH_ATTACH_BUFFERS This structure contains the fields required for the 1394 bus driver to carry out a IsochAttachBuffers request. |
| IRB_REQ_ISOCH_DETACH_BUFFERS This structure contains the fields required to carry out a IsochDetachBuffers request. |
| IRB_REQ_ISOCH_FREE_BANDWIDTH This structure contains the fields necessary in order for the Bus driver to carry out an IsochFreeBandwidth request. |
| IRB_REQ_ISOCH_FREE_CHANNEL This structure contains the fields required to carry out a IsochFreeChannel request. |
| IRB_REQ_ISOCH_FREE_RESOURCES This structure contains the fields necessary to carry out a IsochFreeResources request. |
| IRB_REQ_ISOCH_LISTEN This structure contains the fields necessary to carry out a ReqIsochListen request. |
| IRB_REQ_ISOCH_MODIFY_STREAM_PROPERTIES This structure contains the fields necessary for the Bus driver to carry out an IsochModifyStreamProperties request. |
| IRB_REQ_ISOCH_QUERY_CURRENT_CYCLE_TIME This structure contains the fields necessary for the Bus driver to carry out an IsochQueryCurrentCycleTime request. |
| IRB_REQ_ISOCH_QUERY_RESOURCES This structure contains the fields necessary to carry out a IsochQueryResources request. |
| IRB_REQ_ISOCH_SET_CHANNEL_BANDWIDTH This structure contains the fields necessary for the Bus driver to carry out an IsochSetChannelBandwidth request. |
| IRB_REQ_ISOCH_STOP This structure contains the field necessary to carry out a IsochStop request. |
| IRB_REQ_ISOCH_TALK This structure contains the field necessary to carry out a IsochTalk request. |
| IRB_REQ_RECEIVE_PHY_PACKETS This structure contains the fields necessary to carry out a ReceivePhyPackets request. |
| IRB_REQ_SEND_PHY_CONFIGURATION_PACKET This structure contains the fields necessary to carry out a SendPhyConfigurationPacket request. |
| IRB_REQ_SEND_PHY_PACKET This structure contains the fields necessary to carry out a SendPhyPacket request. |
| IRB_REQ_SET_DEVICE_XMIT_PROPERTIES This structure contains the fields necessary to carry out a SetDeviceXmitProperties request. |
| IRB_REQ_SET_LOCAL_HOST_PROPERTIES This structure contains the fields required to carry out a SetLocalHostProperties request. |
| ISOCH_DESCRIPTOR The ISOCH_DESCRIPTOR structure describes a buffer to be attached or detailed from a resource handle, using the REQUEST_ISOCH_ATTACH_BUFFERS and REQUEST_ISOCH_DETACH_BUFFERS requests. |
| NODE_ADDRESS The NODE_ADDRESS structure specifies the 10-bit bus number and 6-bit node number that serve as the node address for a 1394 node. |
| NOTIFICATION_INFO_W2K The bus driver passes NOTIFICATION_INFO_W2K to the driver-provided notification routine for a driver-allocated address range in an IEEE 1394 address space. |
| NOTIFICATION_INFO_WXP The bus driver passes NOTIFICATION_INFO_WXP to the driver-provided notification routine for a driver-allocated address range in an IEEE 1394 address space. |
| PHY_CONFIGURATION_PACKET The PHY_CONFIGURATION_PACKET structure contains a raw PHY configuration packet. |
| SELF_ID The SELF_ID structure contains a raw packet zero self-ID packet. See the IEEE 1394 Trade Association specification website for details. |
| SELF_ID_MORE The SELF_ID_MORE structure contains a raw packet one, two, or three self-ID packet. See the IEEE 1394 specification for details. |
| SET_LOCAL_HOST_PROPS2 SET_LOCAL_HOST_PROPS2 sets a lower bound on the value the bus will use for its gap count. |
| SET_LOCAL_HOST_PROPS3 SET_LOCAL_HOST_PROPS3 contains the data necessary for defining or identifying one or more unit directories in the Configuration ROM of a 1394 Host Controller. |
| SPEED_MAP The SPEED_MAP structure is stores an IEEE 1394 bus speed map. |
| TEXTUAL_LEAF The TEXTUAL_LEAF structure describes the device description that can be stored in the Configuration ROM of devices that satisfy the PC 98 or PC 99 specifications. |
| TOPOLOGY_MAP The TOPOLOGY_MAP structure is used to store an IEEE 1394 bus topology map. The relations between devices are found in the port members of the entries in TOP_Self_ID_Array. |
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for