From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 'Relocation' for sc520 (i386) based boards
Date: Mon, 22 Sep 2008 22:52:45 +1000 [thread overview]
Message-ID: <48D7951D.9020401@gmail.com> (raw)
In-Reply-To: <48D6848B.3000900@gmail.com>
I seem to be getting into a habit of (partially) answering my own
questions, but I figure these self answered questions may help
someone in the future...
Firstly, the i386 port definitely does not relocate - Two sources of
proof -1) /cpu/i386/start.S is where bss and data get initialised in
RAM with no copy of .text and 2) the startup banner gives it all away
U-Boot code: 38040000 -> 3805158F data: 00400000 -> 00400A57
^^^^^^^^^^^^^^^^^^^^
BSS: 00400A58 -> 00404463 stack: 00404464 -> 0040C463
start.S sets up the stack, copies .data & .got to 0x400000, and
clears .bss
next prev parent reply other threads:[~2008-09-22 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 8:08 [U-Boot] 'Relocation' for sc520 (i386) based boards Graeme Russ
2008-09-21 17:29 ` Jerry Van Baren
2008-09-21 23:18 ` Graeme Russ
2008-09-22 12:51 ` Graeme Russ
2008-09-22 12:52 ` Graeme Russ [this message]
2008-09-22 12:57 ` Graeme Russ
-- strict thread matches above, loose matches on Subject: below --
2008-09-23 6:58 yusuf khan
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=48D7951D.9020401@gmail.com \
--to=graeme.russ@gmail.com \
--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