From: "Eric Bénard" <eric@eukrea.com>
To: Ashwin Kirpalani <akcooper8@gmail.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: MT9T111/MT9T112 aptina camera driver in linux-imx
Date: Wed, 20 Mar 2013 17:43:34 +0100 [thread overview]
Message-ID: <20130320174334.26f90b46@e6520eb> (raw)
In-Reply-To: <CALmQvZR1HEo-d0jQ-dY83Vhw1M9=6R6JM-hp0HYEFFjU1hBZ=A@mail.gmail.com>
Hi Ashwin,
Le Wed, 20 Mar 2013 12:36:19 -0400,
Ashwin Kirpalani <akcooper8@gmail.com> a écrit :
> ahhh...ok so I think I will have to port the mt9t112 driver to freescale's
> way of doing things, namely in the drivers/media/video/mxc/capture since
> freescale is not using soc_camera.
>
True.
> On a somewhat related question, what is this "imx-devel" branch about?:
> https://github.com/RobertCNelson/imx-devel/branches
> I see all kinds of references to imx-devel and v3.x.y.imx-devel here. How
> come this is all the way up to 3.8 while Freescale is still on 3.0.35.
> Something doesn't seem right!
>
Freescale's official kernel is based on 3.0.35 (and oyu are lucky,
i.MX53 is stuck at 2.6.35 ;-( , but community and Linaro's people are
working on mainline (which doesn't have all the drivers the official
kernel has), so depending on the peripherals you need, you could run a
mainline kernel on your i.MX CPU.
Eric
next prev parent reply other threads:[~2013-03-20 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 13:24 MT9T111/MT9T112 aptina camera driver in linux-imx Ashwin Kirpalani
2013-03-20 13:35 ` John Weber
2013-03-20 14:53 ` Ashwin Kirpalani
2013-03-20 15:17 ` John Weber
2013-03-20 15:24 ` Eric Bénard
2013-03-20 16:36 ` Ashwin Kirpalani
2013-03-20 16:43 ` Eric Bénard [this message]
2013-03-20 16:46 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2013-03-19 23:55 Ashwin Kirpalani
2013-03-20 12:08 ` Otavio Salvador
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=20130320174334.26f90b46@e6520eb \
--to=eric@eukrea.com \
--cc=akcooper8@gmail.com \
--cc=meta-freescale@yoctoproject.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.