All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Michael Jones <michael.jones@matrix-vision.de>
Cc: "Aguirre, Sergio" <saaguirre@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: omap3camera and linux-omap
Date: Mon, 09 Aug 2010 20:35:05 +0300	[thread overview]
Message-ID: <4C603C49.8090607@maxwell.research.nokia.com> (raw)
In-Reply-To: <4C6021AF.5010104@matrix-vision.de>

Hi Michael and Sergio,

Michael Jones wrote:
> Aguirre, Sergio wrote:
>> Hi Michael,
>> 
>> 
>>> -----Original Message----- From: linux-omap-owner@vger.kernel.org
>>> [mailto:linux-omap- owner@vger.kernel.org] On Behalf Of Michael
>>> Jones Sent: Friday, August 06, 2010 8:48 AM To:
>>> linux-omap@vger.kernel.org Cc:
>>> sakari.ailus@maxwell.research.nokia.com Subject: omap3camera and
>>> linux-omap
>>> 
>>> I am currently using Sakari's omap3camera repository (branch
>>> 'devel'). 'git merge-base linux-omap omap3camera' tells me that
>>> the last commit omap3camera has in common with linux-omap is
>>> 40a0c47, from July 7 2010. But there are >1000 commits which are
>>> only in omap3camera, dating back to 2008.
>>> 
>>> Is this destined to stay this way?
>> 
>> This is because devel branch keeps a detailed development history
>> since we started working on the camera driver. At the end, the
>> patches submitted will be a consolidated set, which should end in
>> something around ~12 patches or so..
>> 
>>> Or will the omap3camera tree be merged into linux-omap at some
>>> point?
>> 
>> The omap3camera submission is on hold, because the camera driver is
>> dependant on Media controller framework, which is holding for merge
>> in linux-media mailing list.
>> 
>>> When proposing a patch for the omap3camera tree, should it be
>>> sent to this list?
>> 
>> You should preferably send the patches to linux-media (at)
>> vger.kernel.org mailing with cc to Sakari Ailus and Laurent
>> Pinchart.
>> 
>> So far we have been keeping patch review internally, because we
>> didn't want to pollute the mailing list with patches to unsubmitted
>> code.
>> 
>> Regards, Sergio
>> 
>>> Thanks, Michael
>>> 
> 
> Hi Sergio,
> 
> Thanks for the helpful reply.  Can you also clarify for me the
> difference between omap3camera and your linux-omap-camera
> (http://dev.omapzoom.org/?p=saaguirre/linux-omap-camera.git;a=summary)
> repositories?
> 
> I assume this development has mainly happened on the "board-rx51*"
> platform?

As Sergio noted, this is a tree for N900. The main point for the tree,
however, is the OMAP 3 ISP driver, which can be tested on N900 as the
tree also contains N900 sensor, lens and flash drivers.

> Ultimately I want to get raw sensor data to memory.  Do you foresee
> any problems doing that with the current state of omap3camera?  Might
> I be better off going with a kernel with v4l2_int_device at first?

Please don't. It's basically obsolete.

Go with v4l2_subdev instead. If you have a sensor driver to write, the
et8ek8 driver in the omap3camera tree can be used as an example on what
ops the sensor driver should implement.

Regards,

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

      parent reply	other threads:[~2010-08-09 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 13:48 omap3camera and linux-omap Michael Jones
2010-08-06 14:06 ` Patches Xf86-video-omapfb Henk Geraads
2010-08-25  7:05   ` gpmc_cs_request behaviour Henk Geraads
2010-08-06 15:32 ` omap3camera and linux-omap Aguirre, Sergio
2010-08-09 15:41   ` Michael Jones
2010-08-09 16:51     ` Aguirre, Sergio
2010-08-09 17:35     ` Sakari Ailus [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=4C603C49.8090607@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=michael.jones@matrix-vision.de \
    --cc=saaguirre@ti.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 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.