From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: P Jackson <pej02@yahoo.co.uk>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: mt9t031 driver support on OMAP3 system
Date: Mon, 24 Sep 2012 14:24:19 +0200 [thread overview]
Message-ID: <6813233.sAgYNN8Ius@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1209230001390.26787@axis700.grange>
Hi Pete,
On Sunday 23 September 2012 00:04:20 Guennadi Liakhovetski wrote:
> On Sat, 22 Sep 2012, P Jackson wrote:
> > I'm trying to incorporate an MT9T031-based sensor into a commercial
> > small form-factor OMAP3 DM3730-based system which is supplied with
> > sources for a 2.6.37 kernel and is somewhat out-dated.The application
> > I'm working on requires a single image to be acquired from the sensor
> > every once in a while which is then processed off-line by another
> > algorithm on the OMAP3
> >
> > I'd appreciate any advice from the list as to what the most suitable up
> > to-date compatible kernel I should use would be and what other work I
> > need to do in order to get things sorted.
>
> I would certainly advise to use a current kernel (e.g., 3.5). As for
> "how," I know, that Laurent has worked on a similar tasks, you can find
> his posts in mailing list archives, or maybe he'll be able to advise you
> more specifically.
You can have a look at
http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
sensors-board to see how I've modified the ov772x driver to make it usable
with the OMAP3 ISP. The patches are not upstreamable as such, I still need to
work on them. I've explained the issues in detail on the mailing list.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-09-24 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 17:42 mt9t031 driver support on OMAP3 system P Jackson
2012-09-22 22:04 ` Guennadi Liakhovetski
2012-09-24 12:24 ` Laurent Pinchart [this message]
2012-09-24 15:36 ` John Weber
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=6813233.sAgYNN8Ius@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=pej02@yahoo.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).