From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Josh Boyer <jwboyer@linux.vnet.ibm.com>,
linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@gmail.com>
Subject: Re: deprecating fix->mmio_start and smem_start
Date: Wed, 23 Apr 2008 15:21:46 +1000 [thread overview]
Message-ID: <1208928106.9060.20.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0804221433120.30966@anakin>
On Tue, 2008-04-22 at 14:38 +0200, Geert Uytterhoeven wrote:
> > though. Which is why I wonder if we should -also- make the new
> kernel
> > structure user-visible with a new ioctl, so that user space can
> migrate
> > and the day we have such monsters, we aren't totally broken ?
>
> Hmm, that definitely means a new fb_fix_screeninfo, as smem_len is
> currently u32, even on 64-bit.
Yup, I think that's the way to go.
I'll cook up a patch one of these days.
Cheers,
Ben.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-23 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 1:17 deprecating fix->mmio_start and smem_start Benjamin Herrenschmidt
2008-04-22 8:00 ` Geert Uytterhoeven
2008-04-22 8:48 ` Benjamin Herrenschmidt
2008-04-22 12:38 ` Geert Uytterhoeven
2008-04-23 5:21 ` Benjamin Herrenschmidt [this message]
2008-04-22 16:03 ` Scott D. Davilla
2008-04-22 18:11 ` Geert Uytterhoeven
2008-04-22 18:28 ` Scott D. Davilla
2008-04-22 18:44 ` Geert Uytterhoeven
2008-04-22 18:52 ` Scott D. Davilla
2008-04-22 18:41 ` Ville Syrjälä
2008-04-22 22:23 ` Benjamin Herrenschmidt
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=1208928106.9060.20.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=adaplas@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).