All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <erik@bcode.com>
To: linux-media@vger.kernel.org
Cc: "Erik Andrén" <erik.andren@gmail.com>
Subject: Re: Creating a V4L driver for a USB camera
Date: Thu, 4 Jun 2009 10:01:10 +1000	[thread overview]
Message-ID: <20090604100110.c837c3df.erik@bcode.com> (raw)
In-Reply-To: <62e5edd40906022318l230992b7n34e5178b7e1a7d46@mail.gmail.com>

On Wed, 3 Jun 2009 16:18:33 +1000
Erik Andrén <erik.andren@gmail.com> wrote:

> Do you have any datasheet available on what usb bridge / sensor that is used?

The USB device itself comes up as :

    Bus 001 Device 011: ID 0547:8031 Anchor Chips, Inc

The sensor is a Micron MT9T001P12STC and I have the data sheet for it.

I've asked the manufacturer for source code to the windows driver
and docs/source/whatever for the USB interface.

> If the chipsets are undocumented and some proprietary image
> compression technique is used, the time to reverse-engineer them can
> be quite lengthy.

I happen to know that the sensor/camera (via the windows driver) can
provide raw bayer data which is what I'm after (our application is
machine vision and bayer works best).

Cheers,
Erik
-- 
=======================
erik de castro lopo
senior design engineer

bCODE
level 2, 2a glen street
milsons point
sydney nsw 2061
australia

tel +61 (0)2 9954 4411
fax +61 (0)2 9954 4422
www.bcode.com

  reply	other threads:[~2009-06-04  0:01 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 [this message]
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

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=20090604100110.c837c3df.erik@bcode.com \
    --to=erik@bcode.com \
    --cc=erik.andren@gmail.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 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.