From: Johan Rydberg <jrydberg@night.trouble.net>
To: Marco Gerards <metgerards@student.han.nl>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [ppc patch] grub-mkimage
Date: Fri, 03 Dec 2004 17:04:20 +0100 [thread overview]
Message-ID: <87r7m7s70b.fsf@night.trouble.net> (raw)
In-Reply-To: <87653jl86n.fsf@marco.marco-g.com> (Marco Gerards's message of "Fri, 03 Dec 2004 15:20:48 +0000")
Marco Gerards <metgerards@student.han.nl> writes:
> Isn't that impossible because GRUB has its own GOT? I mean: GRUB has
> to lookup all symbols itself, etc. If I am wrong, I have no idea how
> to do it.
As I said to you off-line, the GOT-track might not be worth even
exploring. Instead, at least in my opinion, move the modules within
the calling range of the "b" insn ; thus eliminating chances of
overflows.
> I hope to finish module loading so it at least works this weekend
> using the method that can still cause overflows. Can you have a look
> at the code when I send it in and explain it using the GRUB code?
I could take a look at it, Yes.
~j
next prev parent reply other threads:[~2004-12-03 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 5:36 [ppc patch] grub-mkimage Hollis Blanchard
2004-12-03 12:50 ` Marco Gerards
2004-12-03 13:49 ` Johan Rydberg
2004-12-03 14:14 ` Marco Gerards
2004-12-03 15:13 ` Johan Rydberg
2004-12-03 15:20 ` Marco Gerards
2004-12-03 16:04 ` Johan Rydberg [this message]
2004-12-03 16:13 ` Marco Gerards
2004-12-03 15:18 ` Hollis Blanchard
2004-12-03 16:10 ` Marco Gerards
2004-12-03 16:45 ` Hollis Blanchard
2004-12-03 16:58 ` Marco Gerards
2004-12-03 17:12 ` Yoshinori K. Okuji
2004-12-03 17:18 ` Yoshinori K. Okuji
2005-01-01 22:42 ` [ppc patch] grub-mkimage and module loading Hollis Blanchard
2005-01-02 13:47 ` Marco Gerards
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=87r7m7s70b.fsf@night.trouble.net \
--to=jrydberg@night.trouble.net \
--cc=grub-devel@gnu.org \
--cc=metgerards@student.han.nl \
/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.