Re: Problems in 3.3.x with via VT6315
Brought to you by:
aeb,
bencollins
From: Stefan R. <st...@s5...> - 2012-05-08 18:13:56
|
On May 08 Clemens Ladisch wrote: > Lluís Batlle i Rossell wrote: > > Another thing I could not find anywhere is that in the 2.6.35 computer, I get > > /dev/raw1394 and /dev/video1394-0. In the 3.3.x computer, I don't get any such > > device node, and I don't have any modules named raw1394 or video1394. > > The FireWire stack was completely rewritten. Check that your libraw1394 package > is recent enough (current is 2.0.8, but 2.0.6 or newer should work). In any > case, this library could not cause the kernel to lock up. On the older kernel stack, libdc1394 per default uses direct video1394 accesses for video capture but raw1394 accesses via libraw1394 for discovery, control and status I/O. (It also had a mode in which it used libraw1394 + raw1394 also for video capture, but support for that mode was removed in kernel 2.6.23 and libraw1394 2.0. I don't know if it was removed from the libdc1394 v2 codebase too; could be.) On the newer kernel stack, libdc1394 uses /dev/fw* for everything, without assistance by libraw1394. libdc1394 v2.1.2 (06/2009) is recommended as the minimum version to use together with the newer kernel stack; v2.2.0 (03/2012) is current. I don't know if the libdc1394 version could have an impact on the kind of behavior here, nor am I familiar with how well the VT6315 works for IIDC applications. I only have a VT6306 and two low-end IIDC cameras; it's been a while that I tested the VT6306 with these cameras. However, VT6306 is known to behave differently from (buggier than) VT6307/08/15. -- Stefan Richter -=====-===-- -=-= -=--- http://arcgraph.de/sr/ |