From: Gerd Hoffmann <kraxel@redhat.com>
To: Natalia Portillo <claunia@claunia.com>
Cc: "Peter Baitz" <ussenterprisencc1701@rocketmail.com>,
"Andreas Färber" <andreas.faerber@web.de>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Webcams under KVM and Linux
Date: Mon, 30 May 2011 16:56:32 +0200 [thread overview]
Message-ID: <4DE3B020.2010904@redhat.com> (raw)
In-Reply-To: <C8412FC2-0F66-46A7-86DF-E751D2983010@claunia.com>
On 05/30/11 14:50, Natalia Portillo wrote:
> Exactly what my webcam does is:
>
> Takes a frame from ANY available V4L2 device (/dev/video0), caches it,
> and sends it completely to the guest before requesting any other frame.
I think you can double-buffer (i.e. let the host driver fill one buffer
while sending the other one to the guest). Probably gives a slightly
higher frame rate, but maybe at cost of added latencies.
> The guest sees a common USB Video Class Device webcam with no controls
> (this can be enhanced easily), so basically you cannot change any parameter.
> However all the webcams I tested automatically managed that in the
> firmware with no intervention from any of the drivers (host or guest),
> changing white balance and brightness to the adequate values.
Nice. Patches are waiting for EHCI being merged I guess?
cheers,
Gerd
next prev parent reply other threads:[~2011-05-30 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 13:01 [Qemu-devel] Webcams under KVM and Linux Peter Baitz
2011-05-29 13:37 ` Andreas Färber
2011-05-29 13:53 ` Natalia Portillo
2011-05-29 14:03 ` Peter Baitz
2011-05-30 12:50 ` Natalia Portillo
2011-05-30 14:56 ` Gerd Hoffmann [this message]
2011-05-30 18:19 ` Natalia Portillo
2011-05-31 7:01 ` Gerd Hoffmann
2011-05-30 16:34 ` Peter Baitz
2011-05-30 10:38 ` Gerd Hoffmann
2011-05-30 20:47 ` Brad Hards
2011-05-30 23:39 ` Natalia Portillo
2011-05-31 0:41 ` Brad Hards
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=4DE3B020.2010904@redhat.com \
--to=kraxel@redhat.com \
--cc=andreas.faerber@web.de \
--cc=claunia@claunia.com \
--cc=qemu-devel@nongnu.org \
--cc=ussenterprisencc1701@rocketmail.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.