From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Improve handling of "keep" in gfxpayload
Date: Mon, 10 Aug 2009 17:27:25 +0200 [thread overview]
Message-ID: <20090810152725.GC11134@thorin> (raw)
In-Reply-To: <d7ead6de0908100505w2e3f38b9o151db8fbc0c5870d@mail.gmail.com>
On Mon, Aug 10, 2009 at 02:05:15PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> What is the linux behaviour with 0x0F04? Does it just keep the mode?
> What if the same mode is passed as a value? Does linux redoes the
> modesetting? If 0x0F04 works ok I would prefer to always pass it when
> kernel is booted in graphical mode. VESA mode numbers are an artifact
> and when grub2 has its own graphical drivers it won't correspond to
> anything.
I might be missing something, but AFAICT VESA mode numbers are only passed
by the user in the "vga=" option.
There's also the `vid_mode' parameter in Linux header, but it's only used by
legacy code, and with the 32-bit boot protocol Linux doesn't read it.
Does 0x0F04 really do something when used in combination with Linux' vesafb?
--
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."
next prev parent reply other threads:[~2009-08-10 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 11:01 [PATCH] Improve handling of "keep" in gfxpayload Colin Watson
2009-08-10 11:49 ` Robert Millan
2009-08-10 11:58 ` Colin Watson
2009-08-10 15:15 ` Robert Millan
2009-08-10 15:49 ` Colin Watson
2009-08-10 16:27 ` Vladimir 'phcoder' Serbinenko
2009-08-10 16:41 ` Colin Watson
2009-08-24 14:26 ` Vladimir 'phcoder' Serbinenko
2009-08-24 16:38 ` Colin Watson
2009-08-24 17:14 ` Vladimir 'phcoder' Serbinenko
2009-08-10 12:08 ` Vladimir 'phcoder' Serbinenko
2009-08-10 12:05 ` Vladimir 'phcoder' Serbinenko
2009-08-10 12:21 ` Colin Watson
2009-08-10 12:38 ` Vladimir 'phcoder' Serbinenko
2009-08-10 13:02 ` Colin Watson
2009-08-10 15:27 ` Robert Millan [this message]
2009-08-10 16:18 ` Colin Watson
2009-08-10 20:01 ` Vladimir 'phcoder' Serbinenko
2009-08-10 20:16 ` Colin Watson
2009-08-10 20:24 ` Vladimir 'phcoder' Serbinenko
2009-08-12 0:30 ` Robert Millan
2009-11-09 17:18 ` Robert Millan
2009-11-09 17:53 ` Colin Watson
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=20090810152725.GC11134@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.