From: Txema Lopez <tlopez@aotek.es>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fixup relocation patch.]
Date: Tue, 13 Feb 2007 17:21:33 +0100 [thread overview]
Message-ID: <45D1E58D.6030905@aotek.es> (raw)
In-Reply-To: <45D1DB7D.7050403@fagorautomation.es>
Grant Likely wrote:
>I needed to add the -mrelocatable flag to the linker flags in cpu/ppc4xx/config.mk (I did not remove the -fPIC flag when I did this). Without -mrelocatable, the .fixup section would remain empty.
>
>
It's not the case of the MPC5200. It's enough with the -fPIC flag. It
could be a problem with the gcc cross compiler/linker for the ppc4xx.
>However, -mrelocatable is a powerpc-only flag. I don't know what the magic flag is to do the same on arm/mips/etc.
>
It should be the -fPIC flag. But I think that the main problem is the
existence or not of a piece of code that copy the fixup section elements
from flash to ram and adjust it as the powerpc code does it. I think we
need the help of other architectures experts to resolve this doubt.
>It would be great if this can get sorted out for all u-boot targets. It's an invasive change though. I think your right that having it wrapped in a conditional is the right way to start, but I would start with a patchset that fixes up all powerpc targets first and get it out for comments/testing before it gets merged to mainline. Once powerpc is proven, then turn to look at the other architectures.
>
I agree.
> I'll happily help you with this task.
>
>
I'm sorry but I've got not time to do this task by now. I'm not sure if
this work must be done by only one persone or by the people who have the
equipment to test it. Anway, if you are a volunteer for me is OK.
BR,
Txema
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tlopez.vcf
Type: text/x-vcard
Size: 324 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070213/4a2f2edd/attachment.vcf
next parent reply other threads:[~2007-02-13 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45D1DB7D.7050403@fagorautomation.es>
2007-02-13 16:21 ` Txema Lopez [this message]
2007-02-13 16:40 ` [U-Boot-Users] [PATCH] Fixup relocation patch.] Joakim Tjernlund
2007-02-13 16:48 ` Grant Likely
2007-02-13 16:51 ` Grant Likely
2007-02-13 18:23 ` J. William Campbell
2007-02-14 6:50 ` Grant Likely
2007-02-13 18:37 ` Joakim Tjernlund
2007-02-14 8:01 ` Txema Lopez
2007-02-14 7:30 ` Txema Lopez
2007-02-14 9:24 Joakim Tjernlund
2007-02-14 11:27 ` Txema Lopez
2007-02-14 12:07 ` Joakim Tjernlund
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=45D1E58D.6030905@aotek.es \
--to=tlopez@aotek.es \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox