On 19/04/07, Ranjan Grover <[EMAIL PROTECTED]> wrote:
> I have this camera with FC5 and the uvc driver and it works like a charm
> with luvcview and ekiga.
I also have this camera running fine in Debian/sid using ekiga. It
doesn't work with Kopete yet because of a broken v4l2 interface in
kopet
> I have this camera with FC5 and the uvc driver and it works like a charm
> with luvcview and ekiga.
I also have this camera running fine in Debian/sid using ekiga. It
doesn't work with Kopete yet because of a broken v4l2 interface in
kopete. If you're running Debian or ubuntu you can get the
lin
> Please also try this small patch.
>
> It fixes an issue where the driver does not read the correct number of
> input pins.
Applied. Thanks.
Laurent Pinchart
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mai
Please also try this small patch.
It fixes an issue where the driver does not read the correct number of
input pins.
/Arne
On Tue, 2007-04-17 at 22:40 +0200, Laurent Pinchart wrote:
> > I did what you suggested. Attached is the resulting dmesg output with
> > trace raised to 65535.
>
> Oops,
Hello,
I see in the driver that the exposure property got a CID in the private
range ( V4L2_CID_PRIVATE_BASE+11 ) instead of V4L2_CID_EXPOSURE. Can
anyone tell me the reasoning behind this?
This way applications need to know of the private properties just to
change exposure. Unaware application
Hi Aaron,
> Hi Aaron,
>
> > > > Udev created a /dev/video and /dev/video0, but camorama says "could not
> > > > connect to video device (/dev/video0)." Is there a simple way to fix
> > > > this, or is the support simply unwritten?
> > >
> > > Camorama is at fault. It only supports the deprecated
