Sadly, no dice using the other init. No rush either. I tried using the live CD that has pyro installed, but it doesn't support my hardware well enough to find my webcam (EeePC 901).
Thanks for all the help. Brad On Mon, Oct 20, 2008 at 9:31 PM, Douglas S. Blank <[EMAIL PROTECTED]>wrote: > Bradford Barr wrote: > >> Excuse my ignorance, but I'm not exactly sure what you mean by using the >> other init. >> >> Do I just throw a #define DUMMY_VIDIOC_QUERYCAP at the top of V4L.cpp and >> recompile? >> > > You'll probably need to make sure that both of the V4L::init methods are > not defined. There is one for V4L1 and one for V4L2, and you should make > sure only one gets evaluated. > > Obviously we need a way of testing which V4L a user has, and then using > that version. I'm not sure Pyro has been tested with V4L2, so there very > well may be other issues. > > Of course, I'm only guessing that this is the problem to begin with... > > -Doug > > Brad >> >> On Mon, Oct 20, 2008 at 11:43 AM, Douglas S. Blank <[EMAIL PROTECTED]<mailto: >> [EMAIL PROTECTED]>> wrote: >> >> Bradford Barr wrote: >> >> Hey all, >> >> I'm new to Pyro, and I'm having some issues with the V4LCamera. >> When I run a Test robot with a V4LCamera device it asks me for >> the device, width, height and channel. I leave all of those >> default and get an error: >> >> V4L constructor '/dev/video0' (160 x 120) x 3 ch = 0 >> Initializing Video4Linux /dev/video0..Error: with >> Videochannelioctl VIDIOCGCHAN: Invalid argument >> >> lsmod shows that I have v4l1_compat installed, and I've used the >> camera with other programs (mplayer and opencv). I'm runnning >> Archlinux, kernel 2.6.27. <http://2.6.27.> <http://2.6.27.> Any >> help would be greatly appreciated. >> >> Thanks in advance, >> Brad >> >> >> Brad, >> >> I don't have time to dig into this this week, but I would suspect it >> might be a V4L1 vs V4L2 issue. Take a look at: >> >> pyrobot/camera/v4l/V4L.cpp >> >> it looks like there is a section of code marked with >> DUMMY_VIDIOC_QUERYCAP that might work for you. You could use that >> init rather than the other, and re-make the file. >> >> Let us know if that helps (or if you solve the problem). Thanks, >> >> -Doug >> >> >> >
_______________________________________________ Pyro-users mailing list [email protected] http://emergent.brynmawr.edu/mailman/listinfo/pyro-users
