From: Johan Rydberg <jrydberg@night.trouble.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: make multiboot header optional
Date: Wed, 15 Nov 2006 09:57:08 +0100 [thread overview]
Message-ID: <87psbphyu3.fsf@night.trouble.net> (raw)
In-Reply-To: <1163545104.12931.49.camel@basalt> (Hollis Blanchard's message of "Tue, 14 Nov 2006 16:58:24 -0600")
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hollis Blanchard <hollis@penguinppc.org> writes:
> For kernels that need to communicate information to GRUB (e.g.
> "vga_mode" from my previous email, or a.out load addresses), the
> multiboot header would be needed for GRUB to locate the parameter area
> within the executable.
My two cents;
In MB2 we remove the possibility to communicate options from the
kernel to the boot loader. The loader has one task; loading the
kernel and leave control to it, and possible pass information about
the environment. Nothing more.
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.
~j
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-11-15 8:53 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 [this message]
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
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=87psbphyu3.fsf@night.trouble.net \
--to=jrydberg@night.trouble.net \
--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.