From: Michael Jones <michael.jones@matrix-vision.de>
To: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
Cc: Bastian Hecht <hechtb@googlemail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
laurent.pinchart@ideasonboard.com
Subject: Re: OMAP 3530 camera ISP forks and new media framework
Date: Fri, 22 Oct 2010 15:54:59 +0200 [thread overview]
Message-ID: <4CC197B3.3040208@matrix-vision.de> (raw)
In-Reply-To: <4CADA7ED.5020604@maxwell.research.nokia.com>
Sakari Ailus wrote:
> Bastian Hecht wrote:
>> Hello media team,
>
> Hi Bastian,
>
>> I want to write a sensor driver for the mt9p031 (not mt9t031) camera
>> chip and start getting confused about the different kernel forks and
>> architectural changes that happen in V4L2.
>> A similar problem was discussed in this mailing list at
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg19084.html.
>>
>> Currently I don't know which branch to follow. Either
>> http://gitorious.org/omap3camera from Sakari Ailus or the branch
>> media-0004-omap3isp at http://git.linuxtv.org/pinchartl/media.git from
>> Laurent Pinchart. Both have an folder drivers/media/video/isp and are
>> written for the new media controller architecture if I am right.
>
> Take Laurent's branch it has all the current patches in it. My gitorious
> tree isn't updated anymore. (I just had forgotten to add a note, it's
> there now.)
>
Will Laurent's media-0004-omap3isp branch at linuxtv.org then continue to get updated? Or will the existing commits be rebased at some point? I'm trying to understand/decide what the best approach is with git if I continue doing development on top of the media controller and want to stay up to date.
<snip>
thanks,
--
Michael Jones
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
next prev parent reply other threads:[~2010-10-22 14:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 9:42 OMAP 3530 camera ISP forks and new media framework Bastian Hecht
2010-10-07 10:58 ` Sakari Ailus
2010-10-07 13:27 ` Laurent Pinchart
2010-10-07 13:52 ` Hiremath, Vaibhav
2010-10-07 18:15 ` Guennadi Liakhovetski
2010-10-08 10:46 ` Bastian Hecht
2010-10-11 12:59 ` Bastian Hecht
2010-10-11 13:14 ` Laurent Pinchart
2010-10-11 14:58 ` Bastian Hecht
2010-10-11 15:07 ` Laurent Pinchart
2010-10-12 12:10 ` Bastian Hecht
2010-10-12 12:58 ` Laurent Pinchart
2010-10-14 13:10 ` Bastian Hecht
2010-10-14 13:28 ` Laurent Pinchart
2010-10-12 13:02 ` Bastian Hecht
2010-10-13 22:03 ` Eino-Ville Talvala
2010-10-13 22:58 ` Laurent Pinchart
2010-10-14 5:18 ` Eino-Ville Talvala
2010-10-14 23:08 ` Laurent Pinchart
2010-10-28 10:28 ` Michael Jones
2010-10-28 13:24 ` Laurent Pinchart
2010-10-11 15:26 ` Guennadi Liakhovetski
2010-10-11 16:13 ` Bastian Hecht
2010-10-22 13:54 ` Michael Jones [this message]
2010-10-22 14:13 ` Laurent Pinchart
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=4CC197B3.3040208@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=hechtb@googlemail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.com \
/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