From: Colin Watson <cjwatson@ubuntu.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 21:16:55 +0100 [thread overview]
Message-ID: <20090810201655.GG11691@riva.ucam.org> (raw)
In-Reply-To: <d7ead6de0908101301y67a36190r9f826f6abfe6d40f@mail.gmail.com>
On Mon, Aug 10, 2009 at 10:01:06PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> If these numbers are still needed it needs to be uniform between
> gfxpayload=1024x768 or gfxpayload=keep + gfxmode=1024x768. Derive the
> number from video mode information if you really need it
I couldn't find terribly clear documentation of "keep". Isn't the point
that if you say "keep" then the mode is carried over to the booted
kernel, and if you don't then it isn't? If my understanding is correct
then that would mean that there's no point setting up vid_mode to match
gfxpayload unless "keep" is given.
--
Colin Watson [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2009-08-10 20:17 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
2009-08-10 16:18 ` Colin Watson
2009-08-10 20:01 ` Vladimir 'phcoder' Serbinenko
2009-08-10 20:16 ` Colin Watson [this message]
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=20090810201655.GG11691@riva.ucam.org \
--to=cjwatson@ubuntu.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.