public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Ram <vshrirama@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: camera isp driver status?
Date: Fri, 27 Jun 2008 09:58:39 +0300	[thread overview]
Message-ID: <48648F9F.3010005@mm-sol.com> (raw)
In-Reply-To: <8bf247760806260739t36c2df75sc7fe7be74dd034@mail.gmail.com>

Ram wrote:
> Hi,
>   What is the current status of the camera isp driver on OMAP3 processor?
>   I am using the linux-2.6.22 kernel on linux.omap.com. I am using the
> camera isp driver
>   that exists on 0.9.8 release. I have also tried 0.9.7 release.
> 
>   Has anybody tested it on ISP sensor  (ISP is within the sensor)
> connected through
>   parallel interface working? that is i am not using the ISP that
> exists on OMAP3.
> 
>   I am routing all the cam data to Memory through CCDC. Right now i am
>   using YUV422 format.
> 
>  I do see some  hsync issues. the image appears split at one the end.
>  some frames are good. On some frames the image is split at one of the edges.
> 
>  I also do notice that the first 5-6 frames are green.
>  I do notice that  the data is all jumbled up.
>  i notice only green lines in the images captured.
> 
> 
>  has anyone faced similar issues?
> 
> please do advice.
> 
> Regards,
> sriram
> --
> 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


You can check in V4L mailing list there is new ISP driver from TI in RFC 
status.

I.Ivanov

      reply	other threads:[~2008-06-27  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 14:39 camera isp driver status? Ram
2008-06-27  6:58 ` Ivan T. Ivanov [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=48648F9F.3010005@mm-sol.com \
    --to=iivanov@mm-sol.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vshrirama@gmail.com \
    /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