From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [multiboot2] Tagged multiboot2 header
Date: Mon, 25 Jan 2010 08:46:01 +0100 [thread overview]
Message-ID: <20100125074601.GD13584@thorin> (raw)
In-Reply-To: <4B5796A3.80009@gmail.com>
On Thu, Jan 21, 2010 at 12:49:55AM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> +@item architecture
> +The field @samp{architecture} specifies the Central Processing Unit
> +Instruction Set Architecture. Since @samp{magic} isn't a palindrome
> +it already specifies the endianness ISAs differing only in endianness
> +recieve the same ID. @samp{0} means 32-bit (protected) mode of i386.
ELF specifies architecture and endianess; can we use that?
We already rely on ELF header for other things, but they have counterparts
in aout-kludge fields. So I guess this opens the question on whether we want
to continue supporting aout-kludge for Multiboot 2 or ditch it entirely.
Thoughts?
Btw, would be better if the addition of tagged fields itself would be separate
from other things. It speeds up the process and helps understanding the
changes (both now and afterwards when looking at Bazaar history).
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2010-01-25 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 23:49 [multiboot2] Tagged multiboot2 header Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-25 7:46 ` Robert Millan [this message]
2010-01-29 21:52 ` Robert Millan
2010-01-30 22:42 ` demetrioussharpe
2010-02-01 23:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20100125074601.GD13584@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.