All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Chris MacGregor <chris@cybermato.com>,
	linux-media@vger.kernel.org, Liu Ying <Ying.liu@freescale.com>,
	"Hans J. Koch" <hjk@linutronix.de>,
	Daniel Mack <daniel@zonque.org>
Subject: Re: hacking MT9P031 for i.mx
Date: Fri, 12 Oct 2012 14:10:43 +0200	[thread overview]
Message-ID: <1350043843.3730.32.camel@mars> (raw)
In-Reply-To: <4301383.IPfSC38GGz@avalon>

Hi

On Mon, 2012-07-02 at 14:48 +0200, Laurent Pinchart wrote:
> On Thursday 28 June 2012 21:41:16 Chris MacGregor wrote:

> > > Where did you get the Aptina board code patch from ?
> > 
> >  From here: https://github.com/Aptina/BeagleBoard-xM
> 
> That's definitely outdated, the code is based on a very old OMAP3 ISP driver 
> that was more or less broken by design. Nowadays anything other than the 
> mainline version isn't supported by the community.

Is there a current (kernel ~3.6) git tree which shows how to add mt9p031
to platform code?

I'm also curious if it's possible to glue mt9p031 to a freescale i.mx35
platform. As far as I can see,
drivers/media/platform/soc_camera/mx3_camera.c would need v4l2_subdev
support?

Thanks
 -- Christoph


  reply	other threads:[~2012-10-12 12:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ade8080d-dbbf-4b60-804c-333d7340c01e@googlegroups.com>
2012-06-21 16:38 ` hacking MT9P031 (LI-5M03) driver in Ubuntu 12.04 on BeagleBoard xM? Chris MacGregor
2012-06-24 22:02   ` Chris MacGregor
2012-06-27  9:30   ` Laurent Pinchart
2012-06-29  4:41     ` Chris MacGregor
2012-07-02 12:48       ` Laurent Pinchart
2012-10-12 12:10         ` Christoph Fritz [this message]
2012-10-12 13:11           ` hacking MT9P031 for i.mx Laurent Pinchart
2012-10-16 20:04           ` Laurent Pinchart
2012-10-16 21:04             ` Benoît Thébaudeau
2012-10-17  9:14               ` Christoph Fritz
2012-10-17 12:34                 ` Benoît Thébaudeau
2012-10-19 14:02                 ` Laurent Pinchart
2013-01-22  1:41             ` Richardson Leao

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=1350043843.3730.32.camel@mars \
    --to=chf.fritz@googlemail.com \
    --cc=Ying.liu@freescale.com \
    --cc=chris@cybermato.com \
    --cc=daniel@zonque.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=hjk@linutronix.de \
    --cc=laurent.pinchart@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.