From: Hans Verkuil <hansverk@cisco.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Linus Walleij <linus.walleij@linaro.org>,
Edward Hervey <bilboed@gmail.com>,
johan.mossberg.lml@gmail.com,
Discussion of the development of and with GStreamer
<gstreamer-devel@lists.freedesktop.org>,
"linaro-dev@lists.linaro.org" <linaro-dev@lists.linaro.org>,
Harald Gustafsson <harald.gustafsson@ericsson.com>,
"ST-Ericsson LT Mailing List" <st-ericsson@lists.linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [st-ericsson] v4l2 vs omx for camera
Date: Mon, 28 Feb 2011 11:21:52 +0100 [thread overview]
Message-ID: <201102281121.52906.hansverk@cisco.com> (raw)
In-Reply-To: <201102281111.47666.laurent.pinchart@ideasonboard.com>
On Monday, February 28, 2011 11:11:47 Laurent Pinchart wrote:
> On Saturday 26 February 2011 13:12:42 Hans Verkuil wrote:
> > On Friday, February 25, 2011 18:22:51 Linus Walleij wrote:
> > > 2011/2/24 Edward Hervey <bilboed@gmail.com>:
> > > > What *needs* to be solved is an API for data allocation/passing at
the
> > > >
> > > > kernel level which v4l2,omx,X,GL,vdpau,vaapi,... can use and that
> > > > userspace (like GStreamer) can pass around, monitor and know about.
> > >
> > > I think the patches sent out from ST-Ericsson's Johan Mossberg to
> > > linux-mm for "HWMEM" (hardware memory) deals exactly with buffer
> > > passing, pinning of buffers and so on. The CMA (Contigous Memory
> > > Allocator) has been slightly modified to fit hand-in-glove with HWMEM,
> > > so CMA provides buffers, HWMEM pass them around.
> > >
> > > Johan, when you re-spin the HWMEM patchset, can you include
> > > linaro-dev and linux-media in the CC?
> >
> > Yes, please. This sounds promising and we at linux-media would very much
> > like to take a look at this. I hope that the CMA + HWMEM combination is
> > exactly what we need.
>
> Once again let me restate what I've been telling for some time: CMA must be
> *optional*. Not all hardware need contiguous memory. I'll have a look at the
> next HWMEM version.
Yes, it is optional when you look at specific hardware. On a kernel level
however it is functionality that is required in order to support all the
hardware. There is little point in solving one issue and not the other.
Regards,
Hans
next prev parent reply other threads:[~2011-02-28 10:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik=Yc9cb9r7Ro=evRoxd61KVE=8m7Z5+dNwDzVd@mail.gmail.com>
[not found] ` <AANLkTinDFMMDD-F-FsccCTvUvp6K3zewYsGT1BH9VP1F@mail.gmail.com>
[not found] ` <201102100847.15212.hverkuil@xs4all.nl>
[not found] ` <201102171448.09063.laurent.pinchart@ideasonboard.com>
[not found] ` <AANLkTikg0Oj6nq6h_1-d7AQ4NQr2UyMuSemyniYZBLu3@mail.gmail.com>
2011-02-22 2:44 ` [st-ericsson] v4l2 vs omx for camera Clark, Rob
[not found] ` <AANLkTin0GZxLqtPjNx9AEOPQKRkJ6hf2mXMOqp+LvNw0@mail.gmail.com>
2011-02-24 12:29 ` Linus Walleij
2011-02-24 13:04 ` Hans Verkuil
2011-02-24 13:10 ` Laurent Pinchart
2011-02-25 6:10 ` Clark, Rob
2011-02-26 13:26 ` Felipe Contreras
2011-02-24 13:17 ` Hans Verkuil
2011-02-24 13:30 ` Laurent Pinchart
2011-02-24 14:48 ` Kyungmin Park
2011-02-24 14:51 ` Laurent Pinchart
2011-02-25 6:48 ` Clark, Rob
2011-02-24 13:27 ` Laurent Pinchart
2011-02-26 13:38 ` Felipe Contreras
2011-02-26 13:47 ` Hans Verkuil
2011-02-26 15:26 ` Edward Hervey
2011-02-27 19:49 ` Arnd Bergmann
2011-02-28 10:14 ` Hans Verkuil
2011-02-28 10:15 ` Laurent Pinchart
2011-02-24 20:19 ` Edward Hervey
2011-02-24 21:36 ` Edward Hervey
2011-02-25 6:33 ` Clark, Rob
2011-02-25 17:22 ` Linus Walleij
2011-02-26 12:12 ` Hans Verkuil
2011-02-28 10:11 ` Laurent Pinchart
2011-02-28 10:21 ` Hans Verkuil [this message]
2011-02-28 10:33 ` Laurent Pinchart
2011-02-26 14:14 ` Kyungmin Park
2011-02-26 19:20 ` Nicolas Pitre
2011-02-28 8:50 ` Marek Szyprowski
2011-03-01 10:25 ` Edward Hervey
2011-03-01 10:51 ` Marek Szyprowski
2011-02-26 13:13 ` Felipe Contreras
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=201102281121.52906.hansverk@cisco.com \
--to=hansverk@cisco.com \
--cc=bilboed@gmail.com \
--cc=gstreamer-devel@lists.freedesktop.org \
--cc=harald.gustafsson@ericsson.com \
--cc=hverkuil@xs4all.nl \
--cc=johan.mossberg.lml@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=st-ericsson@lists.linaro.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 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.