From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: some multiboot2 comments
Date: Sat, 28 Oct 2006 16:06:35 +0200 [thread overview]
Message-ID: <200610281606.35234.okuji@enbug.org> (raw)
In-Reply-To: <1161927455.10997.2.camel@diesel>
On Friday 27 October 2006 07:37, Hollis Blanchard wrote:
> > Some platform may need it. On EFI the OS can't get the memmap from EFI
> > because it is too late.
>
> OK. In that case we're still keeping with the philosophy of only passing
> information to the kernel that it can't obtain itself.
However, the definition of a memory map varies from architecture to
architecture, so it might be better to put this tag to architecture-specific
sections, so that we can redefine the format per architecture.
Okuji
next prev parent reply other threads:[~2006-10-28 14:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 19:58 some multiboot2 comments Hollis Blanchard
2006-10-27 4:09 ` Tristan Gingold
2006-10-27 5:37 ` Hollis Blanchard
2006-10-28 14:06 ` Yoshinori K. Okuji [this message]
2006-10-29 16:38 ` Tristan Gingold
2006-10-30 19:20 ` Yoshinori K. Okuji
2006-10-30 20:24 ` Tristan Gingold
2006-11-02 19:52 ` Yoshinori K. Okuji
2006-11-04 14:40 ` Tristan Gingold
2006-12-09 0:02 ` identifying module types Hollis Blanchard
2006-12-09 5:31 ` Tristan Gingold
2006-12-12 20:56 ` Hollis Blanchard
2006-12-12 22:54 ` Yoshinori K. Okuji
2006-12-13 4:14 ` Hollis Blanchard
2006-12-16 5:09 ` Tristan Gingold
2006-12-16 5:04 ` Tristan Gingold
2006-12-12 21:48 ` Hollis Blanchard
2006-12-16 5:06 ` Tristan Gingold
2006-12-12 22:28 ` Yoshinori K. Okuji
2006-12-13 0:07 ` Hollis Blanchard
2006-12-13 20:47 ` Yoshinori K. Okuji
2006-10-28 14:11 ` some multiboot2 comments Yoshinori K. Okuji
2006-10-28 18:32 ` Hollis Blanchard
2006-10-30 19:15 ` Yoshinori K. Okuji
2006-10-31 1:43 ` Hollis Blanchard
2006-11-02 19:53 ` Yoshinori K. Okuji
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=200610281606.35234.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.