From IEEE 1394 FireWire Wiki
Revision as of 22:36, 9 September 2010 by Stefanr (Talk | contribs)

Jump to: navigation, search

FAQ 1.5 How do I setup udev rules to create the device nodes for the various drivers?

Under Debian Lenny with kernel 2.6.26-2-686 the instructions for udev rules allow Coriander to operate. Debian Squeeze with kernel 2.6.32-5-686 is different. The raw1394 module is absent as are /dev/raw1394 and /dev/video1394/0. From a comment in a bug report, I have the impression that the raw1394 module has been replaced by the libraw1394 library. A citation to a document which describes this revision would be helpful. The FAQ needs additional instructions to cover the revised arrangement. Thanks, ... Peter E.

Perhaps the Debian Squeeze kernel and/or modprobe were set up to use firewire-ohci + firewire-core instead of ohci1394 + ieee1394 + (raw1394, video1394). firewire-core exposes different character device files, named /dev/fw0, /dev/fw1 and so on (one file for each device with active FireWire link layer, including the so-called local node i.e. the PC itself). Coriander accesses the kernel through libraw1394 and libdc1394. Since major version 2 of each of these libraries, they are able to transparently work with either /dev/raw1394 and /dev/video1394/* or with /dev/fw*, as they discover them at runtime. With most types of FireWire devices, there should be no administrator intervention required to make /dev/fw* accessible; recent udev versions already contain appropriate rules to set useful ownership or ACLs to /dev/fw*. Have a look at Juju_Migration for more information on required and recommended software versions. I agree that the FAQ is severely out of date in this regard. — Stefan Richter 22:36, 9 September 2010 (UTC)
Personal tools