Ieee 1394 legacy driver windows 7 drivers#
Ieee 1394 legacy driver windows 7 code#
Ieee 1394 legacy driver windows 7 windows 7#

Ieee 1394 legacy driver windows 7 code#

The following table describes the speed code values for each newly supported speed. The following table describes the speed flags for each newly supported speed.

The following table describes the maximum asynchronous payload size for each newly supported speed. This section describes these new flags and values.

Ieee 1394 legacy driver windows 7 windows 7#

The 1394 header file, 1394.h, in the Windows 7 Windows Driver Kit defines new flags for faster speeds and larger payloads. The USE_LOCAL_NODE flag must be set in the u.GetMaxSpeedBetweenDevices.fulFlags parameter. Sending the REQUEST_GET_SPEED_BETWEEN_DEVICES request to 1394ohci.sys retrieves the speed between the local node and the device. Sending this request to 1394ohci.sys returns STATUS_INVALID_PARAMETER. REQUEST_GET_SPEED_TOPOLOGY_MAPS has been deprecated in Windows 2000 and later versions of the operating system. The speed map is obsolete in the IEEE-1394a specification. The 1394ohci.sys bus driver does not support setting nLevel to GET_HOST_CSR_CONTENTS and specifying the SPEED_MAP_LOCATION as CsrBaseAddress. The following table describes the changes in functional behavior of the DDIs exposed by the new 1394 bus driver and the legacy 1394 bus driver: Device Driver Interface The 1394ohci.sys bus driver supports only 1 KB configuration ROMs, which is the same as the legacy 1394 bus driver. The new IOCTL, REQUEST_GET_CONFIG_ROM, returns the contents of a node's configuration ROM, up to a maximum size of 1 kilobyte (KB). The latter I/O request does not allow for specifying the generation count, which could result in a PHY packet being sent to the wrong generation of the 1394 bus. You should use the new REQUEST_SEND_PHY_PACKET I/O request instead of REQUEST_SEND_PHY_CONFIG_PACKET. The 1394ohci.sys bus driver exposes the following new DDIs for sending and receiving PHY packets, as defined in the IEEE-1394a specification.

When the EXTENDED_NOTIFICATION_ROUTINE flag is specified, the u.BusResetNotification.ResetContext parameter points to a BUS_RESET_DATA structure. To register for extended bus reset notifications, a client driver uses the existing REQUEST_BUS_RESET_NOTIFICATION I/O request and specifies the new EXTENDED_NOTIFICATION_ROUTINE flag in the u.BusResetNotification.fulFlags parameter. This information can eliminate the need for a 1394 client driver to synchronize the retrieval of the generation count, node ids, and other information, with its bus reset notification handler.

Ieee 1394 legacy driver windows 7 drivers#

This notification returns information about the current generation of the bus (such as the generation count and node ids) to 1394 client drivers in the context of the bus reset notification. The 1394ohci.sys bus driver supports an extended bus reset notification.

New IOCTL to Retrieve Configuration ROM.

This topic summarizes the general DDI changes that support the new 1394 bus driver.

In addition, certain 1394 DDIs were changed to support greater speeds as defined by the 1394b specification and improved to simplify the development of 1394 client drivers. New DDIs were added to the new features supported by 1394ohci.sys.

The new 1394 bus driver replaces the legacy IEEE bus drivers in port/miniport configuration-1394bus.sys and ochi1394.sys. WindowsВ 7 includes 1394ohci.sys, a new IEEE 1394 bus driver that is implemented by using the kernel-mode driver framework (KMDF).