From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: mx6q csi driver ?
Date: Thu, 6 Mar 2014 20:26:17 +0100 [thread overview]
Message-ID: <20140306192617.GK24339@pengutronix.de> (raw)
In-Reply-To: <20140305223753.GA28522@frolo.macqel>
Hi,
On Wed, Mar 05, 2014 at 11:37:53PM +0100, Philippe De Muyter wrote:
> I try to write a linux driver for a cmos sensor connected to a sabresd
> board, but I wonder where to continue.
>
> I first considered using the freescale 3.10.17 beta kernel,
> which has already a csi v4l2 driver (but using deprecated v4l2 internals).
We already have patches for the CSI, for 3.14-rc+ and based on all the
latest and greatest v4l2 stuff.
Before posting those, we'd like to get the current move-ipu-out-of-
staging effort patch series resolved, then the video part will be one of
the next topics we'll address.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2014-03-06 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 22:37 mx6q csi driver ? Philippe De Muyter
2014-03-06 19:26 ` Robert Schwebel [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=20140306192617.GK24339@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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