From: Philippe De Muyter <phdm@macq.eu>
To: linux-media@vger.kernel.org
Subject: Re: i.mx6 camera interface (CSI) and mainline kernel
Date: Tue, 23 Feb 2016 15:12:58 +0100 [thread overview]
Message-ID: <20160223141258.GA5097@frolo.macqel> (raw)
In-Reply-To: <20160223114943.GA10944@frolo.macqel>
Update.
On Tue, Feb 23, 2016 at 12:49:43PM +0100, Philippe De Muyter wrote:
> Hello,
>
> We use a custom imx6 based board with a canera sensor on it.
> I have written the driver for the camera sensor, based on
> the freescale so-called "3.10" and even "3.14" linux versions.
>
> The camera works perfectly, but we would like to switch to
> a mainline kernel for all the usual reasons (including being
> able to contribute our fixes).
>
> >From an old mail thread (*), I have found two git repositories
> that used to contain not-yet-approved versions of mainline
> imx6 ipu-v3 drivers :
>
> git://git.pengutronix.de/git/pza/linux.git test/nitrogen6x-ipu-media
> https://github.com:slongerbeam/mediatree.git, mx6-camera-staging
>
> I have tried to compile them with the imx_v6_v7_defconfig, but both
> fail directly at compile time. because of later changes in the
> v4l2_subdev infrastructure, not ported to the those branches.
What I wrote is true for Steve Longerbeam's branch, but for Philipp Zabel's
branch the problem (so far) was only that CONFIG_MEDIA_CONTROLLER
is not defined in imx_v6_v7_defconfig, but is required for a succesfull
compilation of Philipp's tree.
> Can someone point me to compilable versions (either not rebased
> versions of those branches, or updated versions of those branches,
> or yet another place to look at). ?
>
> Thanks in advance
>
> Philippe
>
> (*) http://linux-media.vger.kernel.narkive.com/cZQ8NrZ2/i-mx6-status-for-ipu-vpu-gpu
>
> --
> Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles
next prev parent reply other threads:[~2016-02-23 14:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 11:49 i.mx6 camera interface (CSI) and mainline kernel Philippe De Muyter
2016-02-23 14:12 ` Philippe De Muyter [this message]
2016-02-25 22:05 ` Laurent Pinchart
2016-03-03 2:02 ` Steve Longerbeam
2016-03-03 7:19 ` Hans Verkuil
2016-03-03 8:36 ` Philippe De Muyter
2016-03-03 17:45 ` Steve Longerbeam
2016-03-03 17:52 ` Philippe De Muyter
2016-03-07 16:19 ` Tim Harvey
2016-03-09 2:06 ` Steve Longerbeam
2016-03-09 22:44 ` Tim Harvey
2016-03-10 0:12 ` Steve Longerbeam
2016-03-10 7:30 ` Hans Verkuil
2016-03-14 14:55 ` Philippe De Muyter
2016-03-15 20:54 ` Tim Harvey
2016-06-02 13:29 ` Tim Harvey
2016-06-02 13:55 ` Hans Verkuil
2016-06-02 16:50 ` Steve Longerbeam
2016-06-06 16:48 ` Steve Longerbeam
2016-06-10 15:58 ` Jack Mitchell
2016-06-10 16:34 ` Steve Longerbeam
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=20160223141258.GA5097@frolo.macqel \
--to=phdm@macq.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox