All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] GRUB_GFXMODE_LINUX user variable
Date: Wed, 1 Apr 2009 23:01:47 +0900	[thread overview]
Message-ID: <200904012301.47634.okuji@enbug.org> (raw)
In-Reply-To: <20090401130557.GC27958@thorin>

On Wednesday 01 April 2009 22:05:57 Robert Millan wrote:
> On Sun, Mar 29, 2009 at 05:39:36PM +0900, Yoshinori K. Okuji wrote:
> > On Sunday 29 March 2009 11:31:29 Robert Millan wrote:
> > > This patch adds GRUB_GFXMODE_LINUX user variable to make it easy for
> > > users to set graphical mode before booting Linux.
> >
> > Is this really Linux-specific? It look somehow coincidental to me that
> > this is used only for Linux. If other operating systems, such as FreeBSD,
> > support that way of switching a video mode, I think you would want to
> > reuse the same variable.
>
> Agreed.  Also, perhaps we should define an env variable like gfxmode, so
> that loaders can switch mode themselves and "terminal_output gfxterm"
> doesn't have to be used.

Not bad. ;)

> I like the terms "payload" and "loadee" because they don't imply what we're
> loading is a kernel (Linux) or a standalone OS (invaders/memtest86).  How
> about using "gfxmode_payload=WIDTHxHEIGHT[xDEPTH]" ?

I am more used to Multiboot's terminology, so I prefer "OS Image".

Regards,
Okuji



      reply	other threads:[~2009-04-01 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29  2:31 [PATCH] GRUB_GFXMODE_LINUX user variable Robert Millan
2009-03-29  8:39 ` Yoshinori K. Okuji
2009-04-01 13:05   ` Robert Millan
2009-04-01 14:01     ` Yoshinori K. Okuji [this message]

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=200904012301.47634.okuji@enbug.org \
    --to=okuji@enbug.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.