dc1394_vloopback seems to have exactly the same results
as with coriander. Neitehr has yet worked for me with
the vloopback v4l module.
dc1394_vloopback built fine after I added a
#include <linux/compiler.h>
as my build env does is not doing so automatically
as seems to be expected by the 2.6 includes, but that
seems to have worked fine (is this suspicious?)
dc1394_vloopback finds the camera, and if the vloopback
module is not installed it then exits, and all is still
well. If the vloopback module is installed, v4l-info
reports things fine, as long as dc1394_vloopback is not
yet running, but once it is running then v4l-info hangs
and stays hung even after dc1394_vloopback exits (and it
remains killable).
I don't have /proc/video setup so I just use
--vloopback=/dev/video0, is this suspicious? do I need
/proc/video/vloopback/vloopbacks ?)
The system is still operational at this point and top shows
dc1394_vloopback using no cpu time. Once a v4l-info is hung
then even after dcl1394_vloopback exits, new v4l-info commands
will aslo hang (as will xawtv).
Suggestions?
kernel 2.6.8.1
vloopback.ko 0.91-patch (from Damien which works for him it seems)
libdc1394 1.0.0
Dell 4600 P4 2.6hz
Apple iSight Camera
Belkin/lucent 1394 board
On Oct 3, 2004, at 9:27 AM, Dan Dennedy wrote:
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
Received on Mon Oct 4 23:38:02 2004
This archive was generated by hypermail 2.1.8 : Mon 02 May 2005 - 09:16:50 CEST