From: Johan Rydberg <jrydberg@night.trouble.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: jan.setje-eilers@sun.com
Subject: Re: OpenSolaris and multiboot
Date: Wed, 22 Nov 2006 10:41:39 +0100 [thread overview]
Message-ID: <87u00rhl7w.fsf@night.trouble.net> (raw)
In-Reply-To: <45638ACC.3030000@sun.com> (Joe Bonasera's message of "Tue, 21 Nov 2006 15:25:00 -0800")
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
Joe Bonasera <joe.bonasera@sun.com> writes:
> Hollis Blanchard wrote:
>
>> GRUB2's 'multiboot' command will load ELF64 files, so the "a.out
>> hack"
>> shouldn't be necessary for you in the future.
>
> That's fine and will let us delete a small amount of code from both
> the kernel startup sequence and the tools used to build kernel.
>
> Just to be clear. For grub2 on x86, will it be true that there is only
> a single grub2 binary that understands both elf32 and elf64?
Yes.
> Would the different tags i86-pc vs x86_64 (if any) be determined by
> knowing if which type elf gets loaded?
My personal opinion is that we should not pass any information to the
kernel about what format it is provided in.
If the image is an ELF64, it will be loaded as an ELF64. So in your
case, for x86_64 hosts, provide the kernel as an ELF64 image. For
IA-32, provide an ELF32 image.
~j
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-11-22 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1163802029.20484.53.camel@basalt>
[not found] ` <456252C2.1060101@sun.com>
2006-11-21 16:01 ` OpenSolaris and multiboot Hollis Blanchard
2006-11-21 23:25 ` Joe Bonasera
2006-11-22 9:41 ` Johan Rydberg [this message]
2006-11-22 18:58 ` Hollis Blanchard
2006-11-25 3:08 ` 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=87u00rhl7w.fsf@night.trouble.net \
--to=jrydberg@night.trouble.net \
--cc=grub-devel@gnu.org \
--cc=jan.setje-eilers@sun.com \
/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.