public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Jean-Francois Moine <moinejf@free.fr>
Subject: Re: RFC: Move the deprecated et61x251 and sn9c102 to staging
Date: Sun, 09 Jan 2011 23:33:13 -0200	[thread overview]
Message-ID: <4D2A61D9.1090807@redhat.com> (raw)
In-Reply-To: <4D29A3D6.6060307@redhat.com>

Em 09-01-2011 10:02, Hans de Goede escreveu:
> Hi,
> 
> On 01/02/2011 09:13 PM, Hans Verkuil wrote:
>> Hi Hans,
>>
>> On Sunday, January 02, 2011 19:33:31 Hans de Goede wrote:
> 
> <snip>
> 
>>> So only 3 raw bayer + custom compression models supported by
>>> sn9c102 are not supported by gspca_sonixb, and all jpeg models
>>> are supported by gspca_sonixj. Porting the 3 remaining models
>>> over should be relatively easy, but I (I more or less maintain
>>> the sonixb driver) really need hardware access to ensure things
>>> stay working.
>>>
>>> Second correction, I was looking at an old tree and failed to
>>> notice that the zc0301 driver has already bitten the dust
>>> (good!).
>>
>> Thank you for your very helpful answer.
>>
>> Can you make a patch removing all the bogus usb IDs from these drivers?
> 
> I've managed to make some time to also sort out the sn9c1xx usb ids
> situation.  I've just send a pull request which includes patches cleaning
> things up. After this there are only 5 usb-ids left which will default to
> sn9c102 when both are compiled in, and only 3 of those are not supported
> by gspca.

Good!
> 
> So if we move the sn9c102 driver to staging we will loose support for
> only 3 usb-ids. IOW I think it is time to move it to staging :)

This would be a regression.

> Note I can write a patch to add untested support for these 3 to the
> sonixb driver, given my experience with adding support for the hv7131d
> based on the sn9c102 code, that should be doable. But it will be
> completely untested :(

I think that the better would be to add support for it at gspca, but wait for
some feedback before considering it working.

Cheers,
Mauro

  reply	other threads:[~2011-01-10  1:33 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
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 [this message]
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=4D2A61D9.1090807@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    /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