CAM / V4L2: OMAP3 camera issues

CAM / V4L2: OMAP3 camera issues

[Opel Fahrer]

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



      

RE: CAM / V4L2: OMAP3 camera issues

[Aguirre Rodriguez, Sergio Alberto]

Hi Clemens,

I'm the one responsible for this driver, and the features that are added by now are pretty basical.

Currently I'm a bit absorbed by other higher priority tasks, so I haven’t been able to update the driver as fast as I would want.

We are working towards enhancing the driver so most of the features be available, but if you have some enhancement suggestion, I'll invite you to do so.

I appreciate your time.

Regards,
Sergio

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Opel Fahrer
> Sent: Thursday, March 19, 2009 8:24 AM
> To: linux-omap@vger.kernel.org
> Subject: CAM / V4L2: OMAP3 camera issues
> 
> 
> 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
> 
> 
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

AW: CAM / V4L2: OMAP3 camera issues

[Opel Fahrer]

Hi Sergio,

thanks for your fast reply, it's good to hear that someone already has the issues in mind that I'm talking of. As I mentioned before I haven't done any driver development by now, but maybe it's also a good chance to get a little bit into that now. Currently the one and only real problem with the driver at this time is that the YUYV and YVYU support seems to be broken - it's hard to say because of the heavy over-exposure, but I guess there is something wrong in a conversion or something simple like that. Fixing only this issue (and maybe the auto-exposure) would give us everything we need. However, as soon as you have some time to take a look at that feel free to contact me such that we can further talk about these things.

Regards
Clemens



----- Ursprüngliche Mail ----
Von: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>
An: Opel Fahrer <opelfahrer79@yahoo.de>; "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Gesendet: Donnerstag, den 19. März 2009, 16:02:48 Uhr
Betreff: RE: CAM / V4L2: OMAP3 camera issues

Hi Clemens,

I'm the one responsible for this driver, and the features that are added by now are pretty basical.

Currently I'm a bit absorbed by other higher priority tasks, so I haven’t been able to update the driver as fast as I would want.

We are working towards enhancing the driver so most of the features be available, but if you have some enhancement suggestion, I'll invite you to do so.

I appreciate your time.

Regards,
Sergio

> -----Original Message-----
> From: linux-omap-owner@vger.kernel..org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Opel Fahrer
> Sent: Thursday, March 19, 2009 8:24 AM
> To: linux-omap@vger.kernel..org
> Subject: CAM / V4L2: OMAP3 camera issues
> 
> 
> 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
> 
> 
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html 

N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±¢f©Š{ayºÊ‡Ú™ë,j­¢f£¢·hš‹àz¹®w¥¢¸¢·¦j:+v‰¨ŠwèjØm¶Ÿÿ¾«‘êçzZ+ƒùšŽŠÝ¢j"�ú!¶i


      

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html