From: Brian Swetland <swetland@google.com>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Pavel Machek <pavel@ucw.cz>, Greg KH <greg@kroah.com>,
arve@android.com, kernel list <linux-kernel@vger.kernel.org>,
Iliyan Malchev <malchev@google.com>,
Petri Gynther <pgynther@google.com>
Subject: Re: [patch 3/6] add pmem driver
Date: Mon, 14 Sep 2009 15:19:11 -0700 [thread overview]
Message-ID: <a55d774e0909141519i752eca3dp7ab848e1c1154530@mail.gmail.com> (raw)
In-Reply-To: <1252965980.11643.261.camel@desktop>
On Mon, Sep 14, 2009 at 3:06 PM, Daniel Walker <dwalker@fifo99.com> wrote:
> On Mon, 2009-09-14 at 23:58 +0200, Pavel Machek wrote:
>>
>> This adds android pmem driver, one of dependencies of camera driver.
>
> I wouldn't even both with this one .. There's no way it could ever go
> into mainline .. According to the android developers the camera , and
> the frame buffer driver should work without it anyway..
The latest camera driver should work without pmem (or be fixable to do
so -- I forget if that's done yet).
The framebuffer itself does not need pmem, but pmem is used heavily by
the android userspace on dream/magic for hardware compositable
surfaces (since the 2d compositor requires physically contiguous
memory).
Is there a general linux kernel solution for managing large (1-8MB+)
chunks of physically contiguous memory that needs to be shared between
kernel and userspace for media operations? This is a very common
problem with these SoCs -- the a/v subsystem and/or GPU don't have
scatter/gather or MMU support and as a result we need to carve out
memory for their use and provide some way for userspace to manipulate
it.
Brian
next prev parent reply other threads:[~2009-09-14 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 21:58 [patch 3/6] add pmem driver Pavel Machek
2009-09-14 22:06 ` Daniel Walker
2009-09-14 22:08 ` Pavel Machek
2009-09-14 22:23 ` Daniel Walker
2009-09-14 22:26 ` Pavel Machek
2009-09-14 22:19 ` Brian Swetland [this message]
2009-09-14 22:55 ` Daniel Walker
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=a55d774e0909141519i752eca3dp7ab848e1c1154530@mail.gmail.com \
--to=swetland@google.com \
--cc=arve@android.com \
--cc=dwalker@fifo99.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malchev@google.com \
--cc=pavel@ucw.cz \
--cc=pgynther@google.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