All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB_MOD_GAP for non-ieee1275 ELF platforms
Date: Wed, 30 Jan 2008 16:42:25 -0500	[thread overview]
Message-ID: <1201729345.8103.36.camel@dv> (raw)
In-Reply-To: <877ihtc9h4.fsf@xs4all.nl>


On Tue, 2008-01-29 at 09:38 +0100, Marco Gerards wrote:
> Robert Millan <rmh@aybabtu.com> writes:
> 
> > On Mon, Jan 28, 2008 at 08:44:51AM -0500, Pavel Roskin wrote:
> >> > What do you suggest?
> >> 
> >> I would prefer to have GRUB_MOD_GAP is all headers.  Once it's not
> >> needed, it could be removed across the board.
> >
> > Ok, does this seem fine?
> 
> Am I missing something, or didn't you explain what GRUB_MOD_GAP is
> supposed to do...?  To be honest, I do not know what it is about.

If it's not there, PowerMac OpenFirmware would not load the grub image
made by grub-mkimage.  Instead, it will report "CLAIM failed".

The modules use to be loaded at 3 Mb.  Then they were moved directly
after the core (kernel.elf), which created the problem.  Search for the
shortest gap that doesn't result in "CLAIM failed" indicated that it's
0x8000 (32k).  I tried adding more code to kernel.elf, and the gap of
32k was still sufficient.

I assume that if the result of grub-mkimage is a valid ELF file, like
kernel.elf, "CLAIM failed" would not happen.

-- 
Regards,
Pavel Roskin



  parent reply	other threads:[~2008-01-30 21:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  3:25 Redefining GRUB_MOD_GAP in init.c Pavel Roskin
2008-01-28  9:09 ` Robert Millan
2008-01-28  9:30   ` GRUB_MOD_GAP for non-ieee1275 ELF platforms Robert Millan
2008-01-28 13:44     ` Pavel Roskin
2008-01-28 16:29       ` Robert Millan
2008-01-28 16:34         ` Pavel Roskin
2008-01-28 16:57           ` Robert Millan
2008-01-29  8:38         ` Marco Gerards
2008-01-29  9:06           ` Robert Millan
2008-01-29  9:32             ` Marco Gerards
2008-01-29 10:04               ` Robert Millan
2008-01-30 21:42           ` Pavel Roskin [this message]
2008-01-30 22:03             ` Robert Millan
2008-01-30 22:15               ` Pavel Roskin
2008-01-30 22:26                 ` Robert Millan
2008-01-30 22:48                   ` Pavel Roskin
2008-01-31  8:48                     ` Marco Gerards
2008-01-31 10:47                     ` Robert Millan
2008-01-31 11:38                       ` Yoshinori K. Okuji
2008-01-31 12:47                         ` Robert Millan
2008-01-31 13:30                           ` Yoshinori K. Okuji
2008-01-29  8:36   ` Redefining GRUB_MOD_GAP in init.c Marco Gerards
2008-01-29  9:05     ` Robert Millan
2008-01-29  9:21       ` Marco Gerards
2008-01-29  9:27         ` CVS (Re: Redefining GRUB_MOD_GAP in init.c) Robert Millan
2008-01-29 11:15           ` Marco Gerards
2008-01-29 11:42             ` Yoshinori K. Okuji
2008-01-29 11:25           ` Marco Gerards
2008-01-30 21:35             ` Pavel Roskin

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=1201729345.8103.36.camel@dv \
    --to=proski@gnu.org \
    --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.