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: multiboot2: make multiboot header optional
Date: Sat, 2 Dec 2006 18:19:33 +0100	[thread overview]
Message-ID: <200612021819.33479.okuji@enbug.org> (raw)
In-Reply-To: <87bqmm2s1k.fsf@xs4all.nl>

On Saturday 02 December 2006 17:15, Marco Gerards wrote:
> "Yoshinori K. Okuji" <okuji@enbug.org> writes:
> > On Wednesday 15 November 2006 19:42, Hollis Blanchard wrote:
> >> > If the operating system kernel is stupid enough to require as special
> >> > video mode the user should be aware of that and setup the bootloader
> >> > so that it is in that mode before the kernel is started.
> >>
> >> The only information in the multiboot header is a) the load addresses
> >> for a.out and "other" formats, and b) the VGA info.
> >>
> >> We could certainly drop the VGA info.
> >
> > No. The problem is that a kernel cannot initialize VESA in protected mode
> > in some BIOSes. If you need more info, please dig into the archive of
> > bug-grub.
>
> Right, but now the kernel tells the user while video mode to use.  So
> either it is hardcoded in the kernel, or the user has to change the
> kernel to change video modes.  I think this is weird and this was
> never implemented this way.
>
> What I prefer is making it possible for the user to select the video
> mode.  In that case the kernel will become a bit more complex, because
> it has to deal with more situations, but I do not really see this as a
> problem.

Please read the spec carefully. It only specifies what an OS image prefers. 
Since this is a spec, it does not define what happens when the user specifies 
something else in a config file or interactively, but it recommends 
overriding the preference by the user's input.

Why this is useful has been discussed in bug-grub a long, long time ago, and 
I'm not willing to repeat the same discussion again. So, if you don't agree, 
first dig into the archive. If you think it's too boring, just trust me.

Okuji



  reply	other threads:[~2006-12-02 17:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 22:58 multiboot2: make multiboot header optional Hollis Blanchard
2006-11-15  8:57 ` Johan Rydberg
2006-11-15 18:42   ` Hollis Blanchard
2006-11-15 20:42     ` Yoshinori K. Okuji
2006-11-15 21:39       ` Hollis Blanchard
2006-11-15 23:38         ` tgingold
2006-11-25  2:59           ` Yoshinori K. Okuji
2006-11-25  3:35             ` Hollis Blanchard
2006-11-25  4:25               ` Yoshinori K. Okuji
2006-12-02 16:18                 ` Marco Gerards
2006-12-02 17:27                   ` Yoshinori K. Okuji
2006-12-04 16:43                     ` Hollis Blanchard
2006-12-05 20:23                       ` Yoshinori K. Okuji
2006-12-07 23:07                         ` multiboot2: using tags in the multiboot header Hollis Blanchard
2006-12-12 22:23                           ` Yoshinori K. Okuji
2006-12-04 20:35                     ` multiboot2: make multiboot header optional Marco Gerards
2006-12-05 19:09                       ` Hollis Blanchard
2006-12-05 20:04                         ` Yoshinori K. Okuji
2006-12-07 22:39                           ` Hollis Blanchard
2006-12-12 22:08                             ` Yoshinori K. Okuji
2006-12-13  4:18                               ` Hollis Blanchard
2006-12-13 20:56                                 ` Yoshinori K. Okuji
2006-12-13 12:28                         ` Marco Gerards
2006-12-02 16:15       ` Marco Gerards
2006-12-02 17:19         ` Yoshinori K. Okuji [this message]
2006-11-15 20:37 ` Yoshinori K. Okuji
2006-11-15 23:41   ` tgingold
2006-11-21 16:18     ` Hollis Blanchard
2006-11-21 17:35       ` tgingold
2006-11-25  3:05         ` Yoshinori K. Okuji
2006-11-25  3:00     ` Yoshinori K. Okuji
2006-11-25  6:12       ` Tristan Gingold

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=200612021819.33479.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.