From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>,
Hollis Blanchard <hollisb@us.ibm.com>
Cc: Manoel <mrabran@linux.vnet.ibm.com>,
Carlos Roberto do Nascimento Costa <crncosta@linux.vnet.ibm.com>
Subject: Re: PPC64
Date: Tue, 21 Oct 2008 18:04:57 -0400 [thread overview]
Message-ID: <1224626697.3267.19.camel@dv> (raw)
In-Reply-To: <1224622323.31194.81.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]
Hello!
I just want to post some PowerPC related information in this thread
without delving deep into this discussion.
GRUB_MOD_GAP is needed to work around a bug on PowerMac G3 (Blue&White).
Without the gap, images created by grub-mkimage would not load.
OpenFirmware would report: "CLAIM failed".
I believe grub-mkimage doesn't generate valid ELF files, but they are
"good enough" for OpenFirmware. But only with the gap.
I have never tried compiling GRUB on 64-bit PowerPC. However, I tried
cross-compiling it on x86_64 for PowerPC and found a bug in
grub-mkimage, which I fixed. Look for GRUB_TARGET_SIZEOF_LONG in
ChangeLog.
Once this bug is fixed, it should be safe to remove all references
host_m32 from configure.ac. However, I left it in place because I
didn't have a 64-bit PowerPC to test.
util/ieee1275/grub-install.in is not suitable for PowerPC. It assumes
that /boot is on the HFS boot partition. It's not the case for Fedora
and perhaps any distro. The HFS boot partition is not mounted and
should be accessed by hfstools. The modules should be installed
under /boot/grub. The path to /boot/grub should be embedded into the
core image. We have support for embedding the default module path now.
We need a better script that would not put all modules on the short HFS
boot partition. Considering that the SPARC port is defunct, I would
just rewrite util/ieee1275/grub-install.in.
I'm attaching two scripts I'm using to test PowerPC grub on x86_64. One
is building the tools for the host architecture, the other builds them
for PowerPC and uses qemu to run them. The paths should be adjusted,
obviously.
--
Regards,
Pavel Roskin
[-- Attachment #2: grub-ppc --]
[-- Type: application/x-shellscript, Size: 307 bytes --]
[-- Attachment #3: grub-ppc-native --]
[-- Type: application/x-shellscript, Size: 432 bytes --]
next prev parent reply other threads:[~2008-10-21 22:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 20:52 PPC64 Hollis Blanchard
2008-10-21 22:04 ` Pavel Roskin [this message]
2008-10-21 22:40 ` PPC64 Hollis Blanchard
2008-10-23 5:25 ` PPC64 Pavel Roskin
2008-10-23 15:06 ` PPC64 Hollis Blanchard
2008-10-23 16:52 ` PPC64 Pavel Roskin
2008-10-23 18:00 ` PPC64 Manoel
2008-10-23 19:08 ` PPC64 Hollis Blanchard
2008-10-24 12:10 ` PPC64 Manoel
2008-10-24 14:51 ` PPC64 Hollis Blanchard
2008-10-24 21:53 ` PPC64 Manoel
2008-10-27 17:19 ` PPC64 Pavel Roskin
2008-11-04 16:05 ` PPC64 Manoel
2008-11-04 16:12 ` PPC64 Hollis Blanchard
2008-11-04 18:18 ` PPC64 mlongcall gcc flag Manoel
2008-11-04 18:21 ` Manoel
2008-11-04 19:16 ` Robert Millan
2008-11-04 23:48 ` Pavel Roskin
2008-11-05 9:43 ` Robert Millan
2008-11-05 15:35 ` Pavel Roskin
2008-11-05 17:25 ` Hollis Blanchard
2008-11-05 19:27 ` Manoel
2008-11-06 15:12 ` Robert Millan
2008-11-06 17:42 ` Manoel
-- strict thread matches above, loose matches on Subject: below --
2008-10-27 8:04 PPC64 rubisher
2008-10-20 19:18 PPC64 Manoel
2008-10-20 19:32 ` PPC64 Hollis Blanchard
2008-10-21 16:43 ` PPC64 Manoel
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=1224626697.3267.19.camel@dv \
--to=proski@gnu.org \
--cc=crncosta@linux.vnet.ibm.com \
--cc=grub-devel@gnu.org \
--cc=hollisb@us.ibm.com \
--cc=mrabran@linux.vnet.ibm.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.