public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Erik de Castro Lopo <erik@bcode.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Creating a V4L driver for a USB camera
Date: Wed, 03 Jun 2009 10:58:42 +0200	[thread overview]
Message-ID: <4A263B42.1010006@redhat.com> (raw)
In-Reply-To: <20090603141350.04cde59b.erik@bcode.com>

Hi,

On 06/03/2009 06:13 AM, Erik de Castro Lopo wrote:
> Hi all,
>
> I'm a senior software engineer [0] with a small startup. Our product
> is Linux based and makes use of a 3M pixel camera. Unfortunately, the
> camera we have been using for the last 3 years is no longer being
> produced.
>
> We have found two candidate replacement cameras, one with a binary
> only driver and user space library and one with a windows driver
> but no Linux driver.
>
> My questions:
>
>   - How difficult is it to create a GPL V4L driver for a USB camera
>     by snooping the USB traffic of the device when connected to
>     a windows machine? The intention is to merge this work into
>     the V4L mainline and ultimately the kernel.
>

That depends mainly on the format of the image data by the cam,
if the cam sends raw bayer data, or raw yuv / rgb then this is doable,
if it uses plain JPEG it is also doable. If it uses some custom
compression then you need a wizzkid to crack the code. I've tried
this myself, and I failed, you really need someone with the right
mindset to reverse engineer a compression algorithm. Merely being
a good programmer is not enough.

>   - How much work is involved in the above for someone experienced
>     in writing V4L drivers?

This can vary wildly, assuming the video data format is a known one,
a wild estimate would be that this takes 2 fulltime weeks (with hands
on hardware access). But it could be that it takes much longer if
somehow the cam is strange (or worse, like buggy).

>   - Are there people involved with the V4L project that would be
>     willing to undertake this project under contract?
>

Your welcome to send me a couple of cams, that is usually all the
payment I expect, I also don't make any promises (I do this on top
of my dayjob). But first things first, what are the usb-id's of
the cams, can you send me (offlist) the windows drivers ? Chances are
the chipset used is already supported.

Regards,

Hans

      parent reply	other threads:[~2009-06-03  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03  4:13 Creating a V4L driver for a USB camera Erik de Castro Lopo
2009-06-03  6:18 ` Erik Andrén
2009-06-04  0:01   ` Erik de Castro Lopo
2009-06-04  1:28     ` Theodore Kilgore
2009-06-04  1:52       ` Erik de Castro Lopo
2009-06-04  4:02         ` Theodore Kilgore
2009-06-04  5:33           ` Erik de Castro Lopo
2009-06-04 17:50             ` Theodore Kilgore
2009-06-03  8:58 ` 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=4A263B42.1010006@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=erik@bcode.com \
    --cc=linux-media@vger.kernel.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