From: "bibo,mao" <bibo.mao@intel.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub for ia64
Date: Fri, 13 Oct 2006 16:02:37 +0800 [thread overview]
Message-ID: <452F481D.2090902@intel.com> (raw)
In-Reply-To: <20061013052230.GA2490@saphi>
Tristan Gingold wrote:
> On Thu, Oct 12, 2006 at 05:32:00PM +0200, Johan Rydberg wrote:
> > Tristan Gingold <tgingold@free.fr> writes:
> >
> > > On Thu, Oct 12, 2006 at 02:11:57PM +0200, Johan Rydberg wrote:
> > >> Tristan Gingold <tgingold@free.fr> writes:
> > >>
> > >> >> You're telling me that EFI on your IA-64 system does not relocate the
> > >> >> program before start executing it? That sounds strange.
> > >> >
> > >> > It does relocate EFI PEI images. Unfortunatly there is no tools to create
> > >> > EFI PEI objects on Linux. The gnu efi tools are kludgy: they use standard
> > >> > gcc and ld, create an ELF image and convert it to a PEI image. But the
> > >> > relocations are not converted, they are simply put into the data section.
> > >>
> > >> How hard would it be to write a converter ourselves, starting with
> > >> util/i386/efi/grub-mkimage.c?
> > > Not that hard, but
> > > * we'd better to have one grub-mkimage.c for all EFI targets
> >
> > I agree.
> >
> > > * working on binutils is even better.
> >
> > The key problem with this as I see it is that it would force people to
> > have a cross-compiler suite installed, at least for i386 hosts. Unless
> > we can magically get the default installation to include PE-support.
> On my debian system, objdump -i:
> efi-app-ia32
>
> It's already here!
> The binutils issue is mainly for ia64. For i386, grub-mkimage.c works.
>
> Tristan.
>
>
On i386 objcopy in binutils can convert ELF format into PE32, but application need
dynamically relocate itself so that PE32 image can be loaded to any place to execute.
For grub-mkimage.c application need not because grub-mkimage will generate dynamic
relocate segment.
Two methods is ok for me, I prefer the easier one :)
thanks
bibo,mao
next prev parent reply other threads:[~2006-10-13 8:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 11:43 Grub for ia64 Mao, Bibo
2006-10-12 8:21 ` Tristan Gingold
2006-10-12 11:30 ` Johan Rydberg
2006-10-12 11:35 ` Tristan Gingold
2006-10-12 12:11 ` Johan Rydberg
2006-10-12 14:14 ` Tristan Gingold
2006-10-12 15:32 ` Johan Rydberg
2006-10-13 5:22 ` Tristan Gingold
2006-10-13 8:02 ` bibo,mao [this message]
2006-10-13 18:48 ` Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2006-10-12 12:50 Mao, Bibo
2006-09-28 11:41 tgingold
2006-09-28 13:06 ` bibo,mao
2006-09-28 13:12 ` tgingold
2006-09-28 13:33 ` Marco Gerards
2006-09-28 13:45 ` tgingold
2006-09-28 14:29 ` Marco Gerards
2006-09-28 14:49 ` tgingold
2006-09-28 13:47 ` Johan Rydberg
2006-09-28 13:35 ` tgingold
2006-09-28 14:15 ` Johan Rydberg
2006-09-28 13:38 ` Marco Gerards
2006-10-10 18:15 ` Johan Rydberg
2006-10-10 22:03 ` Jeff Bailey
2006-10-11 11:19 ` Johan Rydberg
2006-10-11 10:50 ` 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=452F481D.2090902@intel.com \
--to=bibo.mao@intel.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.