From: Carl Karsten <carl@personnelware.com>
To: video4linux-list@redhat.com
Subject: Re: Testing Requested: Python Bindings for Video4linux2
Date: Thu, 06 Nov 2008 22:30:13 -0600 [thread overview]
Message-ID: <4913C455.3030501@personnelware.com> (raw)
In-Reply-To: <26aa882f0811061612r1419b6a1p9dd8f17333be09ba@mail.gmail.com>
Jackson Yee wrote:
> Lauren,
>
> On Wed, Nov 5, 2008 at 7:42 PM, Laurent Pinchart
> <laurent.pinchart@skynet.be> wrote:
>> The uvcvideo driver doesn't implement the standard ioctls. This should not be
>> fatal (and you probably want to define FindKeyas well).
>
> The standard ioctls are, unfortunately, all I have to go by since I'm
> testing on my amd64 box with a bttv card.
and vivi. I wish more people would test against vivi. although right now I
would hold off, cuz there is a nasty memory leak in one of vivi.c, capture.c or
the newer capture_example.c - details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294951 - I am guessing vivi.
> If a function does not
> succeed though, it should throw an exception and let the user code
> sort things out. Do you have a link for the uncvideo driver so I could
> add support for it?
>
> FindKey looks to be Carl's code. ;-) I've added the function now.
I'll take responsibility for that, cuz it make it look like I am doing something
kinda useful :)
Carl K
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-11-07 4:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 14:14 Testing Requested: Python Bindings for Video4linux2 Jackson Yee
2008-11-06 0:42 ` Laurent Pinchart
2008-11-07 0:12 ` Jackson Yee
2008-11-07 4:30 ` Carl Karsten [this message]
2008-11-09 22:07 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2008-11-24 8:21 Jens Bongartz
2008-12-31 16:17 Jens Bongartz
2008-12-31 18:12 ` Testing " Jackson Yee
2009-01-04 0:02 ` Laurent Pinchart
2009-01-04 23:22 ` Jens Bongartz
2009-01-05 18:20 ` Paul Thomas
2009-01-05 20:42 ` Jens Bongartz
2009-01-06 16:37 ` Laurent Pinchart
2009-01-06 21:43 ` Jens Bongartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4913C455.3030501@personnelware.com \
--to=carl@personnelware.com \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.