All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefano.sabatini-lala@poste.it>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] v4l-dvb gspca modules conflict with standalone	gspca module
Date: Mon, 20 Oct 2008 21:36:32 +0200	[thread overview]
Message-ID: <20081020193632.GA5685@geppetto> (raw)
In-Reply-To: <28a25ce0810191325r7b1e3903jae703a79477e2758@mail.gmail.com>

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

  reply	other threads:[~2008-10-20 19:37 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 [this message]
2008-10-20 20:28       ` Thomas Kaiser
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=20081020193632.GA5685@geppetto \
    --to=stefano.sabatini-lala@poste.it \
    --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 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.