public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Darius Augulis <augulis.darius@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] soc-camera: ov7670 merged multiple drivers and moved over to v4l2-subdev
Date: Tue, 16 Jun 2009 17:23:53 +0000	[thread overview]
Message-ID: <4A37D529.8010905@cam.ac.uk> (raw)
In-Reply-To: <4A37BBB4.1070301@gmail.com>

Darius Augulis wrote:
> On 06/16/2009 05:45 PM, Jonathan Cameron wrote:
>> Guennadi Liakhovetski wrote:
>>> On Mon, 15 Jun 2009, Jonathan Cameron wrote:
>>>
>>>> From: Jonathan Cameron <jic23@cam.ac.uk>
>>>>
>>>> OV7670 soc-camera driver. Merge of drivers from Jonathan Corbet,
>>>> Darius Augulis and Jonathan Cameron 
>>> Could you please, describe in more detail how you merged them? 
>> Mostly by combining the various register sets and then adding pretty much
>> all the functionality in each of them, testing pretty much everything.
>>
>> Note that a lot of what was in those drivers (usually labeled as
>> untested)
>> simply doesn't work and is based on 'magic' register sets provided by
>> omnivision.
>>
>>> However, I am not sure this is the best way to go. I think, a better
>>> approach would be to take a driver currently in the mainline, perhaps,
>>> the most feature-complete one if there are several of them there, 
>> That is more or less what I've done (it's based on Jonathan Corbet's
>> driver).
>> Darius' driver and mine have never been in mainline. Darius' was a
>> complete
>> rewrite based on doc's he has under NDA. Mine was based on Jonathan
>> Corbet's one with a few bits leveraged from a working tinyos driver
>> for the
>> platform I'm using (principally because Omnivision are ignoring both
>> myself
>> and the board supplier). 
> 
> It's very difficult to write 'normal' driver for it.
> Omnivision does not provide useful documentation,
> only long constant arrays with few strange comments.
> Beside documentation is poor, there are lot of errors in register
> description.
> Many things are mistery, not documented and seems Omnivision does not
> have such documentation.
> I thing this sensor isn't perfect for embedded projects. It's 'designed'
> for webcams, where reliability and quality are not needed.
> With ov7720 similar situation...
Agreed.  Though random discussions with others suggest lots of these
chips turn up in things like pedestrian avoidance systems in cars
and similar.  (not generally running linux and tend to have fairly
fixed settings I guess).

Jonathan


  reply	other threads:[~2009-06-16 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 14:22 [PATCH] soc-camera: ov7670 merged multiple drivers and moved over to v4l2-subdev Jonathan Cameron
2009-06-16 13:59 ` Guennadi Liakhovetski
2009-06-16 14:45   ` Jonathan Cameron
2009-06-16 15:35     ` Darius Augulis
2009-06-16 17:23       ` Jonathan Cameron [this message]
2009-06-17  6:44     ` Hans Verkuil
2009-06-17  9:26       ` Jonathan Cameron

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=4A37D529.8010905@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=augulis.darius@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox