From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:45129) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QQgaW-00079H-9h for qemu-devel@nongnu.org; Sun, 29 May 2011 10:03:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QQgaU-0003uw-JN for qemu-devel@nongnu.org; Sun, 29 May 2011 10:03:28 -0400 Received: from nm10-vm0.bullet.mail.ac4.yahoo.com ([98.139.53.194]:29495) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QQgaU-0003us-Bk for qemu-devel@nongnu.org; Sun, 29 May 2011 10:03:26 -0400 Message-ID: <654825.49014.qm@web65303.mail.ac2.yahoo.com> Date: Sun, 29 May 2011 07:03:25 -0700 (PDT) From: Peter Baitz In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1540096199-1306677805=:49014" Subject: Re: [Qemu-devel] Webcams under KVM and Linux List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?iso-8859-1?Q?Andreas_F=E4rber?= , Natalia Portillo Cc: QEMU Developers --0-1540096199-1306677805=:49014 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello Natalia and Andreas, Thank you for the replies and suggestions.=A0 I will lookup V4L.=A0=20 Natalia, So your patch creates a generic webcam under KVM/Qemu to allow many webcams= to work? My only concern is the following:=A0=A0 I use specific Philips webcams, and= one in particular has a long exposure modification that the PWC driver (Fe= dora 11 guest on Fedora 15 host) coupled with Qastrocam-G2 (v4.9) allows th= e "shutter" to remain open through USB control of the LED.=A0 If the guest = restorts to using a generic webcam driver, I think this would preclude func= tionality that the native driver supports ?=A0=20 Also, can you tell me - when KVM is running my guest, should the PWC webcam= driver be loaded and/or the /dev/video0 on the HOST (F15), versus the gues= t (F11) ?=A0=A0 I am confused as to which components are supposed to be ena= bled or disabled while running the guest webcam. =A0 What I see is when I e= nable the webcam USB device in KVM, it appears to disable the /dev/video0 o= n the host an brings it up in the guest. =A0 And the pwc driver loads and r= emains on both host and guest.=A0=20 Peter --- On Sun, 5/29/11, Natalia Portillo wrote: From: Natalia Portillo Subject: Re: [Qemu-devel] Webcams under KVM and Linux To: "Andreas F=E4rber" Cc: "Peter Baitz" , "QEMU Developers" = Date: Sunday, May 29, 2011, 1:53 PM -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 More concretely search for patches sent by me. Even when EHCI is finished still is the problem of isochronous transfer not= working well because of timing issues on QEMU. My patches overcome the need for ISO transfer and EHCI controllers complete= ly, as well as providing an universal device to the guest that works with e= very Windows >XP, every Linux and even Mac OS X. El 29/05/2011, a las 14:37, Andreas F=E4rber escribi=F3: > Hello, >=20 > Am 29.05.2011 um 15:01 schrieb Peter Baitz: >=20 >>=20 >>> [...] You should notice that it is not just adding >>> ISOC and USB 2.0 support, but also to prioritize the processing of isoc >>> packets on a virtual environment, and to provide enough throughput for >>> video streams >>=20 >> [...] Please check the qemu-devel mailing list archive, specifically reg= arding recent discussions about EHCI (USB 2.0). Some of those threads addre= ss isochronous transfer as well. >>=20 >> In the meantime, you could also try to assign a complete host controller= to the guest to get a webcam working. I tried this a while ago, though the= result was only moderately well working here. >=20 >> [...] I would indeed like to hear more about what the project is adding = to KVM - Qemu to allow video to work with webcams > [...] >> I was told I could try to add a complete host controller to the guest, b= ut am not entirely sure I understand what that means?=A0 Looking for specif= ics?=A0 Is there a suggestion for doing this during install of the KVM gues= t, or can this be done while the guest is running, or otherwise? >=20 > Independent of the ongoing EHCI work, I remember a patch specifically for= webcams a while ago, try searching the archives for V4L. >=20 > Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iF4EAREIAAYFAk3iT+QACgkQv/wfOsykIRTtxQD+KCTGZhuzrZMzmYDvY5NFO0+F QQwdE0aYVntQWpHMG5YBAJsFT5wd7/8FxOIt3aL1lwFqXtKc9y9TrrNog95gnoVh =3Dn0hn -----END PGP SIGNATURE----- --0-1540096199-1306677805=:49014 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =
Hello Natalia and Andreas,

Thank you f= or the replies and suggestions.  I will lookup V4L. 

Nata= lia,

So your patch creates a generic webcam under KVM/Qemu to allow = many webcams to work?

My only concern is the following:   = I use specific Philips webcams, and one in particular has a long exposure m= odification that the PWC driver (Fedora 11 guest on Fedora 15 host) coupled= with Qastrocam-G2 (v4.9) allows the "shutter" to remain open through USB c= ontrol of the LED.  If the guest restorts to using a generic webcam dr= iver, I think this would preclude functionality that the native driver supp= orts ? 

Also, can you tell me - when KVM is running my guest, = should the PWC webcam driver be loaded and/or the /dev/video0 on the HOST (= F15), versus the guest (F11) ?   I am confused as to which components are supposed to be enabled or disabled while running the guest = webcam.   What I see is when I enable the webcam USB device in KVM, it= appears to disable the /dev/video0 on the host an brings it up in the gues= t.   And the pwc driver loads and remains on both host and guest. = ;

Peter


--- On Sun, 5/29/11, Natalia Portillo <= claunia@claunia.com> wrote:

From= : Natalia Portillo <claunia@claunia.com>
Subject: Re: [Qemu-devel]= Webcams under KVM and Linux
To: "Andreas F=E4rber" <andreas.faerber@= web.de>
Cc: "Peter Baitz" <ussenterprisencc1701@rocketmail.com>= , "QEMU Developers" <qemu-devel@nongnu.org>
Date: Sunday, May 29, = 2011, 1:53 PM

-----BEGIN PGP SIGNED MESSAGE= -----
Hash: SHA256

More concretely search for patches sent by me.

Even when EHCI is finished still is the problem of isochronous = transfer not working well because of timing issues on QEMU.

My patch= es overcome the need for ISO transfer and EHCI controllers completely, as w= ell as providing an universal device to the guest that works with every Win= dows >XP, every Linux and even Mac OS X.

El 29/05/2011, a las 14:= 37, Andreas F=E4rber escribi=F3:

> Hello,
>
> Am 29.= 05.2011 um 15:01 schrieb Peter Baitz:
>
>>
>>>= [...] You should notice that it is not just adding
>>> ISOC an= d USB 2.0 support, but also to prioritize the processing of isoc
>>= ;> packets on a virtual environment, and to provide enough throughput fo= r
>>> video streams
>>
>> [...] Please check= the qemu-devel mailing list archive, specifically regarding recent discuss= ions about EHCI (USB 2.0). Some of those threads address isochronous transfer as well.
>>
>> In the meantime, you could also= try to assign a complete host controller to the guest to get a webcam work= ing. I tried this a while ago, though the result was only moderately well w= orking here.
>
>> [...] I would indeed like to hear more ab= out what the project is adding to KVM - Qemu to allow video to work with we= bcams
> [...]
>> I was told I could try to add a complete ho= st controller to the guest, but am not entirely sure I understand what that= means?  Looking for specifics?  Is there a suggestion for doing = this during install of the KVM guest, or can this be done while the guest i= s running, or otherwise?
>
> Independent of the ongoing EHCI w= ork, I remember a patch specifically for webcams a while ago, try searching= the archives for V4L.
>
> Andreas

-----BEGIN PGP SIGNA= TURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtoo= ls.org

iF4EAREIAAYFAk3iT+QACgkQv/wfOsykIRTtxQD+KCTGZhuzrZMzmYDvY= 5NFO0+F
QQwdE0aYVntQWpHMG5YBAJsFT5wd7/8FxOIt3aL1lwFqXtKc9y9TrrNog95gnoVh=
=3Dn0hn
-----END PGP SIGNATURE-----
--0-1540096199-1306677805=:49014--