Sony Manufacturing 1394 Driver Download



The current official release of the driver is 6.4.6, released on September 26, 2011 by Christopher R. Bakercbaker+iwan1394@cs.cmu.edu.

Sony 1394 CCM-DS250 Desktop Camera - Driver Download. Vendor: Generic. Product: Sony 1394 CCM-DS250 Desktop Camera. Hardware Class: Image. Step 2, ieee 1394 firewire driver switching now that the camcorder is connected, you will need to verify that the proper ieee 1394 driver has been selected by windows 7. View online specifications for sony pcg-sr33k vaio laptop or simply click download button to examine the sony pcg-sr33k vaio guidelines offline on your desktop or laptop computer.

Sony
After more than a year of wrestling with the nuances of Microsoft's 64-bit operating systems, and with no small quantity of assistance from a few brave testers (you know who you are!), I am proud to officially release this next version of the CMU 1394 Digital Camera Driver, which includes:
  • Support for all present 64-bit versions of Microsoft Windows XP, Vista and 7, allowing both native (64-bit) and emulated (32-bit) applications to access camera data via a single driver interface.
  • A completely new demo application, written from the ground up to support both 32-bit and 64-bit Windows.
  • A litany of bugfixes, many of which were contributed by individual users (for which I am grateful!), including:
    • Squashment of the nefarious BSOD on resume-from-suspend bug
    • A closer-to-correct implementation of the Serial I/O functionality described in the IIDC 1.31 standard (closer = still a little quirky, but the quirks may be in the camera I am testing with)
    • Verified Strobe and Parallel I/O functionality (Strobe controls are also now integrated into the same dialog as Gain, Zoom, Focus, etc.)
    • .. and many others
  • New since the public beta:
    • Fully automated driver installation on 64-bit systems
    • Several minor bugfixes and documentation updates, but nothing that alters the API/ABI

Update: digital signatures for all kernel-mode software

All 64-bit versions of windows require a digital signature via an AuthentiCode certificate in order to run kernel-mode software. I would like to thank MathWorks for providing the funding for this certificate and allowing this driver set to continue to be published freely to the general public. MathWorks provides an adapter to the CMU 1394 Digital Camera driver as part of their Image Acquisition Toolkit to allow developers quick and easy access to images from firewire cameras within the MATLAB environment.

Known issues and limitations

  • Large-block asynchronous transfers. I have received several requests and offerance of patches that restore the ability to issue large asychronous I/O (i.e., larger than a single quadlet/register) requests to cameras. I am evaluating these and trying to fold them into the driver in a manner that supports 64-bit platforms.
  • Mysterious BSOD when using multiple 1394b cameras on the same bus under Windows 7. In experimenting with various configurations of cameras, 1394b host controllers, and driver settings, I have occasionally triggered inexplicable kernel panics while performing comparatively simple operations. Whether this is a quirk of the new Microsoft 1394 bus driver, of some particular host controller, of the 1394 camera driver's innards, or, most likely, of some combination thereof, remains to be seen. Using a single 1394b camera on a single bus is quite stable, however, and the circumstances where multiple cameras trigger this problem seem rare.
  • The usual assortment of bugs and quirks. Much of the frame-handling logic had to be altered to accommodate the curious limitations of DMA transfers on 64-bit systems. Although I have been unit-testing this code to the greatest extent possible, my experience is that no new code is completely bug-free. My thanks go out to the many beta testers who have helped me to this point, and further comments/questions/bug reports/etc. are especially welcome on this front.
Sony manufacturing 1394 driver download 64-bit-->

Windows 7 includes 1394ohci.sys, a new IEEE 1394 bus driver that supports faster speeds and alternative media as defined in the IEEE-1394b specification. The 1394ohci.sys bus driver is a single (monolithic) device driver, implemented by using the kernel-mode driver framework (KMDF). The legacy 1394 bus driver (available in earlier versions of Windows) includes multiple device drivers that were implemented by using the Windows Driver Model (WDM) in a port/miniport configuration. The 1394ohci.sys bus driver replaces the legacy port driver, 1394bus.sys, and the primary miniport driver, ochi1394.sys.

Sony Manufacturing 1394 Driver Download Windows 10

The new 1394ohci.sys bus driver is fully backward compatible with the legacy bus driver. This topic describes some of the known differences in behavior between the new and the legacy 1394 bus driver.

Note

The 1394ohci.sys driver is a system driver that is included in Windows. It is automatically loaded when you install a 1394 controller. This is not a redistributable driver that you can download separately.

I/O Request Completion

All I/O requests that are sent to the new 1394 bus driver return STATUS_PENDING because the 1394ohci.sys bus driver is implemented by using KMDF instead of WDM. This behavior differs from that of the legacy 1394 bus driver, in which certain I/O requests complete immediately.

A client driver must wait until I/O requests sent to the new 1394 bus driver are complete. You can provide an I/O completion routine that is called after the request is complete. The status of the completed I/O request is in the IRP.

Configuration ROM Retrieval

The new 1394 bus driver tries to use asynchronous block transactions at faster bus speeds to retrieve the contents of a node's configuration ROM. The legacy 1394 bus driver uses asynchronous quadlet reads at S100 speed—or 100 megabits per second (Mbps). The 1394ohci.sys bus driver also uses the values that are specified in generation and max_rom entries of the node's configuration ROM header to improve the retrieval of the remaining content of the configuration ROM. For more information about how the new 1394 bus driver retrieves the contents of a node's configuration ROM, see Retrieving the Contents of a IEEE 1394 Node's Configuration ROM.

IEEE-1394-1995 PHY Support

The 1394ohci.sys bus driver requires a physical layer (PHY) that supports IEEE-1394a or IEEE-1394b. It does not support a PHY that supports IEEE-1394-1995. This requirement is due to the 1394ohci.sys bus driver's exclusive use of short (arbitrated) bus resets.

NODE_DEVICE_EXTENSION Structure Usage

A client driver can reference the device extension in the 1394 bus driver associated with the physical device object (PDO) for the device that the client driver controls. This device extension is described by the NODE_DEVICE_EXTENSION structure. In 1394ohci.sys, this structure remains at the same location as in the legacy 1394 bus driver, but the nonstatic members of the structure might not be valid. When a client driver uses the new 1394 bus driver, they must make sure that the data accessed in NODE_DEVICE_EXTENSION is valid. The static members of NODE_DEVICE_EXTENSION that contain valid data are Tag, DeviceObject, and PortDeviceObject. All other members NODE_DEVICE_EXTENSION are nonstatic, which the client driver must not reference.

Gap Count Optimization

The default behavior of the 1394ohci.sys bus driver is to optimize the gap count when it finds only IEEE 1394a devices on the 1394 bus, excluding the local node. For example, if the system that is running 1394ohci.sys has a host controller that complies with IEEE 1394b but all devices on the bus comply with IEEE 1394a, then the new 1394 bus driver tries to optimize the gap count.

Gap count optimization occurs only if the 1394ohci.sys bus driver determines that the local node is the bus manager.

The 1394ohci.sys bus driver determines whether a device complies with IEEE-1394a by the speed setting in the node's self-id packet. If a node sets both of the bits in the speed (sp) field in the self-id packet, then 1394ohci.sys considers the node to comply with IEEE-1394b. If the speed field contains any other value, then 1394ohci.sys considers the node to comply with IEEE-1394a. The gap count value that is used is based on table E-1 in the IEEE-1394a specification, which provides the gap count as a function of hops. The 1394ohci.sys bus driver does not compute the gap count. You can change the default gap count behavior by using a registry value. For more information, see Modifying the Default Behavior of the IEEE 1394 Bus Driver.

Device Driver Interface (DDI) Changes

In Windows 7, the 1394 DDIs were changed to support faster speeds as defined by the 1394b specification and improved to simplify the development of 1394 client drivers. For more information about the general DDI changes that the new 1394 bus driver supports, see Device Driver Interface (DDI) Changes in Windows 7.

Related topics

Sony Manufacturing 1394 Driver Download 64-bit

The IEEE 1394 Driver Stack
Retrieving the Contents of a IEEE 1394 Node's Configuration ROM