public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, luca.risolia@linux-projects.org
Cc: linux-media@vger.kernel.org, Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [RFC PATCH 1/2] sn9c102: prepare for removal by moving it to staging.
Date: Sun, 15 Dec 2013 15:44:54 +0100	[thread overview]
Message-ID: <52ADC066.9080402@redhat.com> (raw)
In-Reply-To: <52AD8FF9.2020901@xs4all.nl>

Hi,

On 12/15/2013 12:18 PM, Hans Verkuil wrote:

<snip>

> 4) Send the webcams that are not (or not correctly) supported by gscpa to Hans
>     de Goede, and let him add support for them to gspca. I don't know if he
>     wants to, though. He may well decide that it is not worth it, although I
>     assume he would be willing to at least fix gspca for webcams that are not
>     correctly supported.

Or alternatively simply send patches to add support for those not supported
to gspca. This should be easy.

I've even added support for some a sensor not supported by gspca when a user
reported to me he wanted to use his webcam with gspca. Porting over the sn9c102
sensor init code to gspca is pretty easy, the only thing which has stopped me
from doing so is not having hardware access. Since in this case I had a user
willing to test I added the support.

> Note that AFAIK HdG has some of the webcams supported by both
> gspca and sn9c102, I'm assuming those are working fine with gspca.

Correct I've the following sn9c10x bayer chipset cams I use for testing:

Sweex WC001                     0c45:6005       sn9c101 tas5110c        ok
Hewi                            0c45:6007       sn9c101 tas5110d        ok
Trust spacecam 120              0c45:600d       sn9c101 pas106          ok
Sweex WC004                     0c45:6011       sn9c101 ov6650          ok
Qware EasyCam WB-001            0c45:6028       sn9c102 pas202          ok

Also note that there are 0 bug-reports from users having issues with the
gspca_sonixb driver.

Regards,

Hans

      parent reply	other threads:[~2013-12-15 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 12:20 [RFC PATCH 0/2] Move sn9c102 and omap24xx/tcm825x to staging Hans Verkuil
2013-12-12 12:20 ` [RFC PATCH 2/2] omap24xx/tcm825x: move to staging for future removal Hans Verkuil
     [not found] ` <1386850822-3487-2-git-send-email-hverkuil@xs4all.nl>
2013-12-14 17:13   ` [RFC PATCH 1/2] sn9c102: prepare for removal by moving it to staging Luca Risolia
2013-12-15 11:18     ` Hans Verkuil
2013-12-15 13:55       ` Luca Risolia
2013-12-16  9:11         ` Hans Verkuil
2013-12-15 14:44       ` Hans de Goede [this message]

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=52ADC066.9080402@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=luca.risolia@linux-projects.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