From: Jean-Francois Moine <moinejf@free.fr>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: RFC: Move the deprecated et61x251 and sn9c102 to staging
Date: Sun, 2 Jan 2011 13:02:55 +0100 [thread overview]
Message-ID: <20110102130255.3ac018b0@tele> (raw)
In-Reply-To: <201101021225.22104.hverkuil@xs4all.nl>
On Sun, 2 Jan 2011 12:25:21 +0100
Hans Verkuil <hverkuil@xs4all.nl> wrote:
> > It seems to me that et61x251 will also stay there for a long time,
> > as there are just two devices supported by gspca driver, while
> > et61x251 supports 25.
> >
> > Btw, we currently have a conflict with this USB ID:
> > USB_DEVICE(0x102c, 0x6151),
> >
> > Both etoms and et61x251 support it, and there's no #if to disable
> > it on one driver, if both drivers are compiled. We need to disable
> > it either at gspca_etoms or at et61x251, in order to avoid users of
> > having a random experience with this device.
>
> Surely such devices should be removed from et61x251 or sn9c102 as
> soon as they are added to gspca?
The et61x251 wants to manage all etoms webcams, but only the 102c:6251
is handled (sensor tas5130d1b - the 102c:6151 contains a pas106).
The other USB ID's should be removed from this driver.
About sn9c102, some people say that the sn9c102 is working better than
gspca. Also, both drivers et61x251 and sn9c102 support cropping while
gspca does not.
Regards.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2011-01-02 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 19:53 RFC: Move the deprecated et61x251 and sn9c102 to staging Hans Verkuil
2011-01-02 10:41 ` Mauro Carvalho Chehab
2011-01-02 11:25 ` Hans Verkuil
2011-01-02 12:02 ` Jean-Francois Moine [this message]
2011-01-02 16:34 ` Hans de Goede
2011-01-02 18:33 ` Hans de Goede
2011-01-02 20:13 ` Hans Verkuil
2011-01-03 16:20 ` Hans de Goede
2011-01-09 12:02 ` Hans de Goede
2011-01-10 1:33 ` Mauro Carvalho Chehab
2011-01-10 10:28 ` Hans de Goede
2011-01-10 10:46 ` Mauro Carvalho Chehab
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=20110102130255.3ac018b0@tele \
--to=moinejf@free.fr \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox