From: Auke Kok <auke@foo-projects.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: moinejf@free.fr, rossi.f@inwind.it, linux-media@vger.kernel.org
Subject: Re: zc3xx: "Creative Webcam Live!" never worked with in-tree driver
Date: Wed, 25 Feb 2009 10:38:44 -0800 [thread overview]
Message-ID: <49A59034.30104@foo-projects.org> (raw)
In-Reply-To: <20090224211916.249e15cf@pedra.chehab.org>
Mauro Carvalho Chehab wrote:
> On Tue, 24 Feb 2009 16:00:59 -0800
> Auke Kok <auke@foo-projects.org> wrote:
>
>> Auke Kok wrote:
>>> All,
>>>
>>> I have a "Creative Technology, Ltd Webcam Live!/Live! Pro" that until
>>> recently worked fine with the out-of-tree gspcav1 driver
>>> (gspcav1-20071224.tar.gz is the latest version I used unti 2.6.26).
>>>
>>> Since this driver (basically) got merged in the kernel I got my hopes up
>>> that the in-kernel gspca_zc3xx drivers would work. However, that does
>>> not provide a usable video0 device - mplayer tv:// crashes with 'No
>>> stream found.' for instance:
<snip>
>> seems I just found the v4lcompat.so stuff, which (apart from being a
>> pain in the rear) makes the webcam work again...
>
> This seems to be a very common error. IMO, we should write message when loading
> a gspca that would require libv4l in order to work.
it would be wonderful if the v4l stack itself can warn when an
application uses the wrong method on the device node... would such a
thing be possible?
Auke
next prev parent reply other threads:[~2009-02-25 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 21:06 zc3xx: "Creative Webcam Live!" never worked with in-tree driver Auke Kok
2009-02-25 0:00 ` Auke Kok
2009-02-25 0:19 ` Mauro Carvalho Chehab
2009-02-25 18:38 ` Auke Kok [this message]
2009-02-26 8:20 ` Jean-Francois Moine
2009-02-26 8:51 ` Auke Kok
2009-02-26 9:16 ` Catimimi
2009-02-26 11:01 ` Jean-Francois Moine
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=49A59034.30104@foo-projects.org \
--to=auke@foo-projects.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=moinejf@free.fr \
--cc=rossi.f@inwind.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox