From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB_MOD_GAP for non-ieee1275 ELF platforms
Date: Thu, 31 Jan 2008 11:47:59 +0100 [thread overview]
Message-ID: <20080131104759.GA10889@thorin> (raw)
In-Reply-To: <1201733294.8103.67.camel@dv>
On Wed, Jan 30, 2008 at 05:48:14PM -0500, Pavel Roskin wrote:
> On Wed, 2008-01-30 at 23:26 +0100, Robert Millan wrote:
> > > I only said "I assume" because there is a subtle difference between a
> > > "valid ELF file" and "indistinguishable for kernel.elf". It should be
> > > valid and acceptable to the OpenFirmware, and the later is a black box
> > > to me.
> >
> > Uhm.. I wonder what'd happen if you pre-link all the stuff into kernel.elf.
>
> I tried to prelink "apple" and "hfs" by changing the makefiles. The
> functionality wasn't available. It makes sense, because the core
> doesn't know that the modules are linked. The modules are never
> registered with the core.
You can easily work around that by removing the GRUB_MOD_INIT() wrap and
calling the functions manually.
However, to determine if the "CLAIM failed" problem also affects "sane" elven,
you don't need to initialize these modules, just link them in.
> It would be nice to have some linker trick to tell the code about the
> prelinked modules. That could make grub-mkimage a very thin wrapper
> around "ld -r", perhaps written as a shell script.
Sure it would. Shouldn't be too hard, geninit.sh does half of what you want
already.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-01-31 10:50 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
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 [this message]
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=20080131104759.GA10889@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.