linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Scott D. Davilla" <davilla@4pi.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: deprecating fix->mmio_start and smem_start
Date: Tue, 22 Apr 2008 20:44:20 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0804222043110.9710@anakin> (raw)
In-Reply-To: <p0623091dc433dce76d94@[192.168.2.55]>

On Tue, 22 Apr 2008, Scott D. Davilla wrote:
> > On Tue, 22 Apr 2008, Scott D. Davilla wrote:
> > >  >On Tue, 22 Apr 2008, Benjamin Herrenschmidt wrote:
> > >  >>  We currently have a problem with those two members of struct
> > >  >>  fb_fix_screeninfo. The struct contains an "unsigned long" which means
> > >  >>  that:
> > >  >>
> > >  >>  - 64 bits kernels with 32 bits userspace can't pass a complete
> > > address
> > >  >>  - 32 bits machines with 64 bits resource_size_t can't pass a complete
> > >  >>  address
> > >  >>  - The structure isn't even properly padded to be 32/64 bits neutral
> > > in
> > >  >>  the first place.
> > >  >>
> > >  >  > We could define new versions of the struct with new get/set ioctls,
> > >  >>  or we could try to just deprecate those fields. What do you guys
> > > think ?
> > >  >
> > >  >As userspace doesn't really need those fields[1], we can easily
> > >  >deprecate them.
> > > 
> >  > kexec uses FBIOGET_FSCREENINFO and FBIOGET_VSCREENINFO. So if these
> >  > ioctls changes, it will possibly break kexec under vesafb and efifb.
> > 
> > Does kexec use the smem_start and mmio_start fields of
> > fb_fix_screeninfo?
> > 
> 
> In "kexec/arch/i386/x86-linux-setup.c", the routine "setup_linux_vesafb" uses
> smem_start, smem_len, and line_length.
> 
> This is used for vesafb and efifb framebuffer kernel boot param setup. This is
> required for PC hardware that do not contain a PC-BIOS and need the bootloader
> to setup the kernel video boot params.

OK, but the problem doesn't show up on x86-32 (no >32-bit physical
addresses yet), as x86_linux_param_header.lfb_base is uint32_t and there's no
way it's gonna change.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
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

  reply	other threads:[~2008-04-22 18:44 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
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 [this message]
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=Pine.LNX.4.64.0804222043110.9710@anakin \
    --to=geert@linux-m68k.org \
    --cc=davilla@4pi.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).