All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	laurent.pinchart@ideasonboard.com,
	Hans Verkuil <hansverk@cisco.com>, Rob Clark <rob@ti.com>
Subject: Re: [ANNOUNCE] New OMAP4 V4L2 Camera Project started
Date: Sat, 14 May 2011 02:01:26 +0300	[thread overview]
Message-ID: <4DCDB846.1010204@iki.fi> (raw)
In-Reply-To: <BANLkTi=RVE0zk83K0hn89H3S6CKEmKSj2A@mail.gmail.com>

Aguirre, Sergio wrote:
> Hi all,

Hi, Sergio!

> Just to let you know that I've just officially registered for a new
> project in the Pandaboard.org portal for OMAP4 v4l2 camera support.
> 
> You can find it here:
> 
> http://omiio.org/content/omap4-v4l2-camera
> 
> And also, you can find the actual Gitorious project with the code here:
> 
> https://www.gitorious.org/omap4-v4l2-camera
> 
> If anyone is interested in contributing for this project, please let
> me know, so I can add you as a contributor to the project.

I'm very, very happy to see a project to start implementing V4L2 support
for the OMAP 4 ISS!! Thanks, Sergio!

A few comments:


- The driver is using videobuf. I wonder if the driver would benefit
more from videobuf2.


- As far as I understand, the OMAP 4 ISS is partially similar to the
OMAP 3 one in design --- it has a hardware pipeline, that is. Fitting
the bus receivers and the ISP under an Media controller graph looks
relatively straightforward. The same might apply to SIMCOP, but then the
question is: what kind of interface should the SIMCOP have?

Being familiar with the history of the OMAP 3 ISP driver, I know this is
not a small project. Still, starting to use the Media controller in an
early phase would benefit the project in long run since the conversion
can be avoided later.


Which parts of the ISS require regular attention from the M3s? Is it the
whole ISS or just the SIMCOP, for example?

Kind regards,
Sakari Ailus

Ps. I have nothing against SoC camera, but when I look at the ISS
overview diagram (section 8.1 in my TRM) I can't avoid thinking that
this is exactly what the Media controller was created for. :-)

-- 
Sakari Ailus
sakari.ailus@iki.fi

  parent reply	other threads:[~2011-05-13 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 23:30 [ANNOUNCE] New OMAP4 V4L2 Camera Project started Aguirre, Sergio
2011-05-13 18:30 ` Guennadi Liakhovetski
2011-05-13 23:01 ` Sakari Ailus [this message]
2011-05-13 23:23   ` Aguirre, Sergio
2011-05-16  6:46     ` 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=4DCDB846.1010204@iki.fi \
    --to=sakari.ailus@iki.fi \
    --cc=hansverk@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=rob@ti.com \
    --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.