public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Jones <michael.jones@matrix-vision.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Eino-Ville Talvala <talvala@stanford.edu>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Sung Hee Park <shpark7@stanford.edu>,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
Subject: Re: OMAP 3530 camera ISP forks and new media framework
Date: Thu, 28 Oct 2010 12:28:46 +0200	[thread overview]
Message-ID: <4CC9505E.8020004@matrix-vision.de> (raw)
In-Reply-To: <201010140058.47236.laurent.pinchart@ideasonboard.com>

Hi Laurent,

Laurent Pinchart wrote:

> 
> First of all, you need to get the latest OMAP3 ISP driver sources.
> 
> The most recent OMAP3 ISP driver for the N900 can be found in the omap3isp-
> rx51 git tree on gitorious.org (devel branch from 
> http://meego.gitorious.org/maemo-multimedia/omap3isp-rx51). This is the tree 
> used by MeeGo for the OMAP3 ISP camera driver. The driver has been ported to 
> the media controller framework, but the latest changes to the framework are 
> not present in that tree as they break the driver ABI and API. This should be 
> fixed in the future, but I can't give you any time estimate at the moment.
> 
> The most recent OMAP3 ISP driver and media controller framework can be found 
> in the pinchartl/media git tree on linuxtv.org (media-0004-omap3isp branch 
> from http://git.linuxtv.org/pinchartl/media.git). This is the tree used for 
> upstream submission of the media controller and OMAP3 ISP driver. The OMAP3 
> ISP driver implements the latest media controller API, but the tree doesn't 
> contain RX51 camera support.
>

You say "the most recent OMAP3 ISP driver for the N900" is on gitorious but "the most recent OMAP3 ISP driver and media controller framework" is your branch.  I'm confused about where I find "the most recent OMAP3 ISP driver".  To take a concrete example, in media-0004-omap3isp, media_device_register() WARNs if mdev doesn't have a model name (I get the warning).  On the Meego branch, it WARNs only if it's missing both a model name and a parent dev pointer.  If I understood you correctly above, media-0004-omap3isp has the newer framework, so the newer framework requires a model name?

I don't need RX51 camera support, but I would like to have a reasonably up-to-date OMAP3 ISP driver.  Laurent said before that media-0004-omap3isp will be updated regularly.  Do these updates come from a cherry-pick of the gitorious branch?  I anticipate sending a patch based on media-0004-omap3isp someday (like one addressing my WARN_ON issue) and getting as a reply, "yeah, we already did that on meego.gitorious.org".

I appreciate your help so far.

-- 
Michael Jones

MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

  parent reply	other threads:[~2010-10-28 10:28 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 [this message]
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
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=4CC9505E.8020004@matrix-vision.de \
    --to=michael.jones@matrix-vision.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=shpark7@stanford.edu \
    --cc=talvala@stanford.edu \
    /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