From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] FPGA relocation/C environment
Date: Thu, 29 Oct 2009 09:21:13 +0100 [thread overview]
Message-ID: <20091029082113.GE3216@leila.ping.de> (raw)
Hi,
I am using U-Boot on a Coldfire to load FPGA code (Xilinx Spartan3
and Altera Cyclone2, currently) and am just trying to update my code
base to current U-Boot for finally sending patches.
Now I recognized that commit 6385b28116f775da4771b768ba9bf93c3aaaf26e
removed FPGA relocation, which of course breaks FPGA code for my
Coldfire board.
What is the "proper relocation for PPC boards" that is mentioned
by Peter in his commit log? I found this test patch by him:
http://lists.denx.de/pipermail/u-boot/2009-September/060582.html
which leads me to the assumption that for PPC, newer compilers
do the right thing (TM) when given -mrelocatable, but
- my m68k-elf-gcc (Sourcery G++ Lite 4.3-208) 4.3.3 (that was the
newest one I could get my hands on that is able to compile U-Boot
at all) does not know -mrelocatable
- I do not understand how the compiler could know about the
relocation for the FPGA (and possibly other) functions when the
actual relocation is done during U-Boot run time?
Can anybody give some hints where I have to look at or where my
misunderstanding occurs?
Thank you,
Wolfgang
next reply other threads:[~2009-10-29 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 8:21 Wolfgang Wegner [this message]
2009-10-29 11:00 ` [U-Boot] FPGA relocation/C environment Wolfgang Denk
2009-10-29 12:04 ` Wolfgang Wegner
2009-10-29 13:08 ` Joakim Tjernlund
2009-10-29 13:41 ` Wolfgang Wegner
2009-10-29 14:22 ` Joakim Tjernlund
2009-10-29 15:00 ` Wolfgang Wegner
2009-10-29 15:44 ` Wolfgang Wegner
2009-10-29 16:39 ` Joakim Tjernlund
2009-10-30 13:11 ` Wolfgang Wegner
2009-10-30 23:16 ` Graeme Russ
2009-10-29 15:47 ` 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=20091029082113.GE3216@leila.ping.de \
--to=wolfgang@leila.ping.de \
--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