All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: JoJo jojo <onetwojojo@gmail.com>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
	v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>
Subject: Re: gspca-sonixb and sn9c102 produce incompatible V4L2_PIX_FMT_SN9C10X
Date: Mon, 01 Sep 2008 23:08:24 +0200	[thread overview]
Message-ID: <48BC59C8.9050101@hhs.nl> (raw)
In-Reply-To: <226dee610809011219h4088a062k77a2d0ac1acbc047@mail.gmail.com>

JoJo jojo wrote:
> On Fri, Aug 29, 2008 at 4:08 PM, Hans de Goede <j.w.r.degoede@hhs.nl> wrote:
>> Hi all,
>> 1) Fix the gspca driver and libv4l to produce / expect BGGR bayer inside the
>> V4L2_PIX_FMT_SN9C10X data, making gspca compatible with the already released
>> in an official kernel sn9c102 driver. The downside of this is that we loose
>> all the testing done with gspca (both v1 and v2) with the current gspca
>> settings but given that windows uses the sn9c102 settings I don't expect
>> much
>> of a problem from this (and I can test the new settings for 3 of the 7
>> supported sensors).
>>
> 
> 
> What are the other 4 USB ids of sensors that you can't test yourself?
> Maybe we can help.
> 

We could use testing for the following usb-id's:

         {USB_DEVICE(0x0c45, 0x6007), SB(TAS5110, 101)}, /* TAS5110D */
         {USB_DEVICE(0x0c45, 0x6009), SB(PAS106, 101)},
         {USB_DEVICE(0x0c45, 0x600d), SB(PAS106, 101)},
         {USB_DEVICE(0x0c45, 0x6019), SB(OV7630, 101)},
         {USB_DEVICE(0x0c45, 0x6024), SB(TAS5130CXX, 102)},
         {USB_DEVICE(0x0c45, 0x6025), SB(TAS5130CXX, 102)},
         {USB_DEVICE(0x0c45, 0x6028), SB(PAS202, 102)},
         {USB_DEVICE(0x0c45, 0x6029), SB(PAS106, 102)},
         {USB_DEVICE(0x0c45, 0x602c), SB(OV7630, 102)},
         {USB_DEVICE(0x0c45, 0x602d), SB(HV7131R, 102)},
         {USB_DEVICE(0x0c45, 0x602e), SB(OV7630, 102)},
         {USB_DEVICE(0x0c45, 0x60af), SB(PAS202, 103)},

Which should currently be supported, we are also interested in any cams with a 
usb-id matching: 0c45:60?? or 0c45:61??, some may just need to right entry 
added to the usb-id table, while others may require adding some code.

Thanks & Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-09-01 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 10:38 gspca-sonixb and sn9c102 produce incompatible V4L2_PIX_FMT_SN9C10X Hans de Goede
2008-08-29 11:05 ` [v4l-dvb-maintainer] " Hans Verkuil
2008-09-01 19:19 ` JoJo jojo
2008-09-01 21:08   ` 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=48BC59C8.9050101@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=onetwojojo@gmail.com \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    --cc=video4linux-list@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 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.