From: Opel Fahrer <opelfahrer79@yahoo.de>
To: linux-omap@vger.kernel.org
Subject: CAM / V4L2: OMAP3 camera issues
Date: Thu, 19 Mar 2009 07:23:43 -0700 (PDT) [thread overview]
Message-ID: <341895.54098.qm@web24704.mail.ird.yahoo.com> (raw)
Hi everybody,
I just wanted to ask if someone of you recently had a look at the camera driver for the ov3640 sensor included in the omap zoom 1 platform. As I'm a total noob in writing drivers I'm searching for someone to help me to get this device to work the right way because currently it's really a mess. Unfortunately our future work with the omap zoom heavily relies on having camera images in reasonable resolutions and reasonable quality, so for us there is no way around fixing at least some of these points:
As far as I have seen there are several issues. The main problem is that it is only possible to use a very restricted number of image formats. One can use Bayer images in 1024x768 up to 2048x1536 pixels, and using the Bayer format is the only way to get RGB images actually. The much more appreciated YUYV and YVYU formats seem to be broken somehow, so nobody is known to me who was able to decode such an image into a reasonable color image yet. Lastly, a problem is that there is no way to control the exposure of the sensor, such that the images are all heavily over-exposed and there is no way known to me to change any setting to use auto-exposure (the feature is reported to be not available by v4l2).
I'd be happy if someone could help me in fixing some of these problems.
Regards
Clemens
next reply other threads:[~2009-03-19 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 14:23 Opel Fahrer [this message]
2009-03-19 15:02 ` CAM / V4L2: OMAP3 camera issues Aguirre Rodriguez, Sergio Alberto
2009-03-19 16:20 ` AW: " Opel Fahrer
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=341895.54098.qm@web24704.mail.ird.yahoo.com \
--to=opelfahrer79@yahoo.de \
--cc=linux-omap@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