From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Video mode fixes in linux loader
Date: Mon, 13 Apr 2009 11:16:46 -0400 [thread overview]
Message-ID: <1239635806.18804.8.camel@mj> (raw)
In-Reply-To: <20090413141657.GE12170@thorin>
On Mon, 2009-04-13 at 16:16 +0200, Robert Millan wrote:
> Hi Pavel,
>
> On Mon, Apr 06, 2009 at 11:34:03AM -0400, Pavel Roskin wrote:
> > Hello!
> >
> > This is an attempt to fix all issues with the video mode handling in the
> > new Linux loader.
>
> Please, in general, when you modify code that has been actively worked on
> by someone, try to get that person involved.
I tried, but probably not hard enough. Sorry.
> > The default VGA mode is now GRUB_LINUX_VID_MODE_NORMAL, not the mode of
> > the kernel we tried to load before.
>
> Ok, BUT if we're already in vesa mode, and we know it works (since we're using
> it), there's no point in wasting time only to get a worse mode.
Maybe we should introduce another macro, e.g.
GRUB_LINUX_VID_MODE_CURRENT, recognize it in the loader and default to
it.
> We should just make sure subsequent calls to "linux" command override the
> previous one.
Yes, failed loading of one kernel should not affect loading of another
kernel. That was the most annoying bug, and I hope it's fixed now.
> > Finally, "vga=ask" is now recognized.
>
> With the new loader, Linux' 16-bit entry code is no longer responsible for
> setting vesa modes, therefore vga=ask can't work. There's no point in
> recognizing it (except to warn the user).
I agree. Generally, "vga=random_string" causes an error now. Perhaps
any unrecognized values of "vga" should cause a warning, not an error.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-04-13 15:17 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
2009-04-13 15:16 ` Pavel Roskin [this message]
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=1239635806.18804.8.camel@mj \
--to=proski@gnu.org \
--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.