All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Greg KH <greg@kroah.com>,
	arve@android.com, swetland@google.com,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 3/6] add pmem driver
Date: Tue, 15 Sep 2009 00:26:06 +0200	[thread overview]
Message-ID: <20090914222605.GK10398@elf.ucw.cz> (raw)
In-Reply-To: <1252966985.11643.273.camel@desktop>

On Mon 2009-09-14 15:23:05, Daniel Walker wrote:
> On Tue, 2009-09-15 at 00:08 +0200, Pavel Machek wrote:
> > On Mon 2009-09-14 15:06:20, Daniel Walker 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..
> > 
> > Well, without it, it does not link. If you can provide better patch,
> > please go ahead. (But please let me fix the compilation in the meantime).
> 
> Now that I think about it, maybe just the frame buffer driver can work
> without it.. If it's really needed for the camera then the agenda should
> be removing pmem from the camera ..
> 
> > Plus... why do you think this is completely unacceptable? We may need
> > to strip the userland interface, but the rest..
> 
> The userland interface is the core of the driver tho .. According to the
> android developers (my understanding anyway), this driver just allows
> large blocks of memory to be allocated then shared between userspace and
> kernel space .. Brian can explain it better, but from the sound of it
> they are likely replicating interfaces that we already have ..

AFAICT, pmem exports functionality that is required by the other
part. I agree that new userland interface is probably no-go, but I
also believe that it should be easy enough to remove (or maybe change)
in followup patch.

It will be worked on, eventually. For now, we'd like dream support to
compile and link, and then maybe to boot.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-09-14 22:26 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 [this message]
2009-09-14 22:19   ` Brian Swetland
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=20090914222605.GK10398@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arve@android.com \
    --cc=dwalker@fifo99.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swetland@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 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.