From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Tony Breeds <tbreeds@au1.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Problem with framebuffer mmap on platforms with large addressing
Date: Thu, 22 Mar 2012 07:49:18 +1100 [thread overview]
Message-ID: <1332362958.2982.41.camel@pasglop> (raw)
In-Reply-To: <4F6A2FEC.6040003@gmx.de>
On Wed, 2012-03-21 at 19:45 +0000, Florian Tobias Schandinat wrote:
> I finally found where we started to discuss this issue, for reference
> "sm501fb.c: support mmap on PPC440SPe/PPC440EPx" back in May 2010.
>
> The thing I don't remember is why we consider exporting the physical
> address to userspace desirable (or even necessary). Fixing the generic
> mmap would be trivial without breaking or adding any userspace ABI, I
> think. Just adding those things to fb_info and adjusting fb_mmap
> should
> do the trick, shouldn't it?
For historical reasons, things like X or directfb used it. Modern X
drivers shouldn't any more, but heh...
Cheers,
Ben.
prev parent reply other threads:[~2012-03-21 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 16:04 Problem with framebuffer mmap on platforms with large addressing Dmitry Eremin-Solenikov
2012-03-18 0:46 ` Benjamin Herrenschmidt
2012-03-18 14:04 ` Dmitry Eremin-Solenikov
2012-03-18 20:49 ` Benjamin Herrenschmidt
2012-03-19 14:42 ` Dmitry Eremin-Solenikov
2012-03-20 5:40 ` Benjamin Herrenschmidt
2012-04-09 16:18 ` Dmitry Eremin-Solenikov
2012-04-09 21:37 ` Benjamin Herrenschmidt
2012-03-21 19:45 ` Florian Tobias Schandinat
2012-03-21 20:49 ` Benjamin Herrenschmidt [this message]
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=1332362958.2982.41.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=FlorianSchandinat@gmx.de \
--cc=dbaryshkov@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tbreeds@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).