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] Improve handling of "keep" in gfxpayload
Date: Mon, 10 Aug 2009 17:15:41 +0200	[thread overview]
Message-ID: <20090810151541.GB11134@thorin> (raw)
In-Reply-To: <20090810115835.GU11691@riva.ucam.org>

On Mon, Aug 10, 2009 at 12:58:35PM +0100, Colin Watson wrote:
> On Mon, Aug 10, 2009 at 01:49:40PM +0200, Robert Millan wrote:
> > On Mon, Aug 10, 2009 at 12:01:02PM +0100, Colin Watson wrote:
> > > If the user set "keep" in gfxpayload, as I understand it, that indicates
> > > that they want the graphical mode set by GRUB to persist through to the
> > > kernel. In order for this to actually work with Linux, we need to set up
> > > the vid_mode boot parameter to indicate that it should keep the current
> > > video mode, otherwise it'll just reset the mode to text at boot and
> > > nothing much is gained. This patch fixes that.
> > 
> > Nice catch, I wasn't aware an extra flag was needed.
> 
> It also seems that doing this right is tricky on the kernel side (see
> https://lists.ubuntu.com/archives/kernel-team/2009-August/006773.html
> and thread), so I probably won't be turning this on by default yet in
> our configuration - but of course if you explicitly say "keep" then you
> should get what you asked for.

I read that thread.  Note that in the future, GRUB will include video
drivers, and when those are ready we don't have to use vesa, so I wouldn't
spend a lot of effort with this vesa->other video driver transition that
according to Matthew can be complicated.

-- 
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-08-10 15:15 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 [this message]
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
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=20090810151541.GB11134@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.