Re: [Cpia2-development] cpia2 Unexpected error: -71 using qx5view

[Steven L. M. <ste...@st...>]

Anthony Tekatch wrote:
> On Wed, 04 Apr 2007 12:27:13 -0700, "Steven L. MILLER" <ste...@st...> wrote:
>> It looks like you might be missing either (or both) of videodev.h or 
>> videodev2.h. Both should be in /usr/src/linux/include/linux. Or they may 
>> have changed in the 2 years since we've updated the driver. I would 
>> suspect the latter, and this may be what breaks qx5view. From here you 
>> should probably look at the Debian source, and you'll probably have to 
>> make some minor changes to qx5 view for whatever changes in v4l2 there 
>> has been. You might get away with just looking at the v4l header files - 
>> there shouldn't be too many places where they're filled in.
> 
> I compiled the cpia2 driver (from cvs) and installed it, qx5view (also
> from cvs) did not work in the same fashion as before where setting the
> lights causes /dev/video0 to be destroyed.
> 
> Just some notes on my findings so far in the difference between the old
> cvs files and the newer files that come with updated kernels (like 2.6.18):
>  - The cpia2.h (in cvs) was missing #include<media/v4l2-common.h>.
>  - Also many references to an older kernel have been removed in the new kernel supplied cpia2 module code.
>  - cpia2_usb.c requires .owner to be commented out on line 83 (this property does not exist in the kernel anymore).
> 
> 
> Does anyone know where I can find the information about how the lights
> are set, i.e. spec sheets or whatever, specifically, how did code like
> the following code get into cpia2_v4l.c:
> 
> static struct control_menu_info lights_controls[] =
> {
> 	{ 0,   "Off" },
> 	{ 64,  "Top" },
> 	{ 128, "Bottom"  },
> 	{ 192, "Both"  },
> 
> 
> Cheers,
> Anthony

Those differences are not surprising. I think the kernel version when 
this work was done was around 2.6.12 or so. We have not kept the cvs 
version up to date since it is being maintained in the kernel now.  The 
qx5view author seems to have disappeared. The light controls were 
reverse engineered by playing with the gpios to see what they did. The 
manufacturer (Sonic Blue? - I'm not sure I'm remembering that correctly) 
refused to provide any info, so the person who added this experimented 
until he got it to work.

If you'd like to keep this (app and/or driver), I can add you to the 
developer access. For that matter, I wouldn't object if you wanted to 
take over maintainership, as I simply don't have the time to keep it going.

Cheers,
Steve

-- 
Steve Miller
Staff Software Engineer
STMicroelectronics
North American Mobile Platforms Applications Lab
phone (602) 485-2014