public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kaiser <linux-dvb@kaiser-linux.li>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] v4l-dvb gspca modules conflict with	standalone	gspca module
Date: Mon, 20 Oct 2008 22:28:53 +0200	[thread overview]
Message-ID: <48FCEA05.7060600@kaiser-linux.li> (raw)
In-Reply-To: <20081020193632.GA5685@geppetto>

Stefano Sabatini wrote:
> On date Sunday 2008-10-19 22:25:29 +0200, Román wrote:
>> 2008/10/19 Stefano Sabatini <stefano.sabatini-lala@poste.it>:
>>> BTW I wonder why v4l-dvb includes the gspca modules, which seem to be
>>> related more to the gspca cameras than to DVB devices
> [...]
>> I wonder as well. The standalone driver works with my webcam, but the
>> v4l-dvb one provokes a kernel panic on my system, after a short period
>> of using it (or it used to; admittedly it's been quite a while -a few
>> months- since I last tried).
> 
> For the archive: gspca based cameras finally stopped to work with the
> v4l-dvb modules on linux-2.6.26, reinstalling the kernel and the
> standalone module fixed it.
> 
> Please could the core devs clarify the situation for what regards
> gscpa modules in v4l-dvb?
> 
> Thanks, regards.
> 
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hello Stefano

The gspca module V1 was developed outside of the kernel tree. Therefor, 
it was possible to add "in kernel" video decompression/decoding, which 
is not allowed and not good to do in kernel space. But this was a great 
success to add more than 220 webcams to the Linux World.

Now, gspca V1 is moving to gspca V2 to support V4L2. Jean-Francois Moine 
(moinejf@free.fr) did a rewrite to support V4L2 with gspca. Thus, its 
called gspca V2. He removed all the not allowed decoding process which 
was done in kernel space with the old gspca.

Now, gspca V2 got included into the kernel! (Big step forward)

Hans de Goede (j.w.r.degoede@hhs.nl) is writing a user space lib to 
convert/decode all the stuff which was done in the old gspca in kernel 
space, his lib does it now in user space. That's the way to go!

The development of this is rather new and I think it is not included in 
any distro at the moment. But it will be soon.

So, please drop the the old gspca V1 and help testing gspca V2!

BTW: gspca is in v4l-dvb because v4l is for analogue deceives and dvb is 
for digital devices. gspca fits perfect into v4l!

Thomas

PS: Pixart, but now free time to do more, sorry.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-10-20 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 19:09 [linux-dvb] kernel sources location and gspca module version Stefano Sabatini
2008-10-19 14:20 ` [linux-dvb] v4l-dvb gspca modules conflict with standalone gspca module Stefano Sabatini
2008-10-19 20:25   ` Román
2008-10-20 19:36     ` Stefano Sabatini
2008-10-20 20:28       ` Thomas Kaiser [this message]
2008-10-21  7:28         ` Matthias Schwarzott
  -- strict thread matches above, loose matches on Subject: below --
2008-10-21 10:16 Eduard Huguet

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=48FCEA05.7060600@kaiser-linux.li \
    --to=linux-dvb@kaiser-linux.li \
    --cc=linux-dvb@linuxtv.org \
    /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