From: James Simmons <jsimmons@infradead.org>
To: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Paul Mundt <lethal@linux-sh.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [Linux-fbdev-devel] [PATCH 2.6.20 1/1] fbdev, mm: hecuba/E-Ink fbdev driver
Date: Wed, 28 Feb 2007 16:50:05 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0702281648510.14127@pentafluge.infradead.org> (raw)
In-Reply-To: <45a44e480702211522q6225d4fbx3f7d99fcef5fe93c@mail.gmail.com>
> I'm not sure I understand. What the current implementation does is to
> use host based framebuffer memory. Apps mmap that memory and draw to
> that. Then after the delay, that framebuffer is written to the
> device's memory. That's the scenario for hecubafb where the Apollo
> controller maintains it's own internal framebuffer.
>
> When you say without the framebuffer, if you meant without the host
> memory, then this method doesn't work. If you mean without the
> device's internal memory, then yes, I think we can do that, because it
> would be up to the driver to use the touched pagelist to then perform
> IO as suitable for its device.
I meant for it to work for non framebuffer devices. I realized that not
such a great idea.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-28 16:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 10:42 [PATCH 2.6.20 1/1] fbdev,mm: " Jaya Kumar
2007-02-17 12:34 ` Peter Zijlstra
2007-02-17 13:25 ` Jaya Kumar
2007-02-17 13:59 ` Paul Mundt
2007-02-18 11:31 ` Jaya Kumar
2007-02-18 23:57 ` Paul Mundt
2007-02-20 4:13 ` Jaya Kumar
2007-02-20 4:38 ` Paul Mundt
2007-02-20 6:11 ` Jaya Kumar
2007-02-21 16:46 ` Jaya Kumar
2007-02-20 8:07 ` Geert Uytterhoeven
2007-02-21 16:55 ` Jaya Kumar
2007-02-21 21:52 ` James Simmons
2007-02-21 23:22 ` Jaya Kumar
2007-02-28 16:50 ` James Simmons [this message]
2007-02-21 23:43 ` [Linux-fbdev-devel] [PATCH 2.6.20 1/1] fbdev, mm: " Antonino A. Daplas
2007-02-21 23:47 ` Jaya Kumar
2007-02-21 23:43 ` Antonino A. Daplas
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=Pine.LNX.4.64.0702281648510.14127@pentafluge.infradead.org \
--to=jsimmons@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=geert@linux-m68k.org \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox