public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: MK <halfcountplus@intergate.com>
Cc: "Erik Andrén" <erik.andren@gmail.com>,
	video4linux-list@redhat.com, linux-media@vger.kernel.org
Subject: Re: working on webcam driver
Date: Thu, 14 May 2009 19:26:39 +0200	[thread overview]
Message-ID: <4A0C544F.1030801@hhs.nl> (raw)
In-Reply-To: <1242316804.1759.1@lhost.ldomain>

On 05/14/2009 06:00 PM, MK wrote:
> Since I'm cross-posting this (as advised) I should introduce myself by
> saying I am a neophyte C programmer getting into kernel programming by
> trying to write a driver for an unsupported webcam.  So far I've gotten
> the device to register and have enumerated the various interfaces.
>
> On 05/11/2009 02:50:00 PM, Erik Andrén wrote:
>> First of all, this list is deprecated. Send mails to
>> linux-media@vger.kernel.org if you want to reach the kernel community.
>>
>> Secondly, have you researched that there is no existing driver for
>> your camera? A good way to start would perhaps to search for the usb
>> id and linux in google to see if it generates some hits.
>
> I've done this last bit already, and I just checked out gspca.  There
> is a lot of listing for the vendor id, but not the product id, so I
> imagine there is no point in trying any of the drivers (unless I hack
> the source to accept the id string).
>
> However, a rather unhelpful person at the linux driver backport group
> informs me "not all USB video drivers are under
> drivers/media/video/usbvideo/  In fact, the majority of them are not."
> but then tells me I should take off and go find them myself "with a web
> browser" (very nice).
>
> Does anyone know where these drivers are located?

Most non yvc (see below) usb webcams are driven through the gspca usb
webcam driver framework. This is a v4l driver which consists of gspca-core
+ various subdrivers for a lot of bridges, see drivers/media/video/gspca


   The same person also
> claims that the kernel now has support "for all devices that
> follow the USB video class specification, and [sic] that the additional
> 23 device specific drivers in the tree* are just for non-conforming
> devices".

This is correct recently the USB consortium (or whatever they are called)
have created a new spec called UVC, this is one standard protocol for all
webcams to follow. All *newer* webcams use this, but a lot of cams still
in the stores predate UVC (which stands for USB Video Class).

The first thing to find out to get your webcam supported is what kind of
bridge chip it is using, try looking at the windows driver .inf file,
typical bridges are the sonix series (often refenced to as sn9c10x or
sn9c20x), spca5xx series, zc3xx, vc032x, etc. If you see a reference
to anything like this in the windows driver .inf file (or inside dll's)
that would be good to know. Also it would be very helpful to have the usb
id of your camera.

Regards,

Hans

  reply	other threads:[~2009-05-14 17:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 14:45 working on webcam driver MK
2009-05-11 18:50 ` Erik Andrén
2009-05-14 16:00   ` MK
2009-05-14 17:26     ` Hans de Goede [this message]
2009-05-14 19:57       ` Theodore Kilgore
2009-05-17 16:08         ` MK
2009-05-17 22:31           ` leandro Costantino
2009-05-19 20:35         ` What is libv4lconvert/sn9c202x.c for? Theodore Kilgore
2009-05-20 18:38           ` Hans de Goede
2009-05-20 19:53             ` Theodore Kilgore
2009-05-23 22:12             ` [PATCH] to libv4lconvert, to do decompression for sn9c2028 cameras Theodore Kilgore
2009-05-24  9:49               ` Hans de Goede
2009-05-24 17:22                 ` Theodore Kilgore
2009-05-24 17:32                   ` Hans de Goede
2009-05-24 22:26                     ` Theodore Kilgore

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=4A0C544F.1030801@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=erik.andren@gmail.com \
    --cc=halfcountplus@intergate.com \
    --cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox