From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: my plan for Multiboot 2
Date: Wed, 9 Dec 2009 22:50:36 +0100 [thread overview]
Message-ID: <20091209215036.GG7093@thorin> (raw)
In-Reply-To: <20091207165329.GE5040@const.bordeaux.inria.fr>
On Mon, Dec 07, 2009 at 05:53:29PM +0100, Samuel Thibault wrote:
> Robert Millan, le Mon 07 Dec 2009 16:08:31 +0100, a écrit :
> > - Release a new revision of Multiboot 1, with only modifications that don't
> > alter the spec. I.e. GRUB Legacy continues to be compliant, and we don't
> > change the signature. These modifications would basically cope with the
> > fact that Multiboot 1 is also usable on non-BIOS platforms, take advantage
> > of modern 64-bit types to define equivalent structures, resolve some
> > ambiguities, etc.
>
> I'm wondering about the multiboot_mod_list structure & 64bits: would
> mod_start/end, cmdline and pad become 64bits?
I think long-term we should treat ia64 and amd64 as separate architectures.
Short-term we don't really support them, except to recognize and load amd64
ELF files.
--
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."
next prev parent reply other threads:[~2009-12-09 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 15:08 my plan for Multiboot 2 Robert Millan
2009-12-07 16:53 ` Samuel Thibault
2009-12-09 21:50 ` Robert Millan [this message]
2009-12-09 21:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-09 22:03 ` Robert Millan
2009-12-09 22:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-10 1:01 ` Robert Millan
2009-12-10 7:06 ` BVK Chaitanya
2009-12-13 8:13 ` Bogdan
2009-12-13 22:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-24 21:07 ` Robert Millan
2009-12-24 21:11 ` Robert Millan
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=20091209215036.GG7093@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.