All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Video mode fixes in linux loader
Date: Sun, 3 May 2009 17:50:41 +0200	[thread overview]
Message-ID: <20090503155041.GA21659@thorin> (raw)
In-Reply-To: <200905030918.02859.ml@isaac.cedarswampstudios.org>

On Sun, May 03, 2009 at 09:18:02AM -0400, Isaac Dupree wrote:
> Robert Millan wrote:
> > > > > Some
> > > > > kernels may not support VESA modes at all.
> > > >
> > > > I don't think this is applicable;  all modern versions of Linux include
> > > > vesa modesetting in its 16-bit entry code, and older versions are
> > > > already detected by the new loader (user is prompted to use linux16).
> > >
> > > I can disable CONFIG_FB, and then the screen remains blank until X
> > > starts.  It's entirely possible that some distros don't enable CONFIG_FB
> > > to save memory, and I don't always enable it in the kernels I configure
> > > myself.
> >
> > Makes sense for official GRUB.
> >
> > However, I'd still like to add a macro check that can be enabled on distros
> > that ship Linux builds with CONFIG_FB and want to enable seamless mode
> > transition (this will be the case for e.g. Debian).
> 
> Can we have GRUB2 not be distro-dependent,

We aren't talking about making GRUB distro-dependant, only about what is the
default behaviour when user didn't specify any.

Official GRUB, as discussed, will default to text mode.  I don't see why
downstream distributors would need to do the same, since it's so easy to
override in case a user needs that.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-05-03 15:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 15:34 [PATCH] Video mode fixes in linux loader Pavel Roskin
2009-04-07  0:31 ` Yoshinori K. Okuji
2009-04-07  0:49   ` Pavel Roskin
2009-04-07  7:31     ` phcoder
2009-04-07 22:04       ` Pavel Roskin
2009-04-12 19:11         ` phcoder
2009-04-12 20:43           ` Pavel Roskin
2009-04-13 14:16 ` Robert Millan
2009-04-13 14:45   ` Robert Millan
2009-04-13 15:41     ` Pavel Roskin
2009-04-13 19:05       ` Robert Millan
2009-04-13 23:20         ` Pavel Roskin
2009-04-14  0:02           ` phcoder
2009-05-02 11:38             ` Robert Millan
2009-05-02 11:31           ` Robert Millan
2009-05-02 15:32             ` Robert Millan
2009-05-03  0:03               ` BandiPat
2009-05-03 15:53                 ` Robert Millan
2009-05-04 15:15                   ` BandiPat
2009-05-04 16:01                     ` Robert Millan
2009-05-04 18:16                       ` BandiPat
2009-05-04 18:16                         ` Felix Zielcke
2009-05-04 20:30                   ` Robert Millan
2009-05-04 21:59                     ` BandiPat
2009-05-13 20:47                       ` Robert Millan
2009-05-04 18:04               ` Robert Millan
2009-05-03 13:18             ` Isaac Dupree
2009-05-03 15:50               ` Robert Millan [this message]
2009-04-13 15:16   ` Pavel Roskin
2009-04-13 18:59     ` Robert Millan

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=20090503155041.GA21659@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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 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.