From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] armv7: start.S: Fix relocation address caculation
Date: Thu, 16 Dec 2010 10:04:01 +0100 [thread overview]
Message-ID: <4D09D601.7010702@free.fr> (raw)
In-Reply-To: <AANLkTimMct8TKe7k-0LA4Gob1mJZnCw0f9xbbp9VKMoz@mail.gmail.com>
Le 16/12/2010 04:04, Jason Liu a ?crit :
> Hi, Albert,
>
> 2010/12/16 Albert ARIBAUD<albert.aribaud@free.fr>:
>> Hi Jason,
>>
>> Le 15/12/2010 14:57, Jason Liu a ?crit :
>>> There will have issue if the _start not equal TEXT_BASE
>>> when enable relocation.
>>
>> In what case does this happen?
>
> Some ARM SOC ROM need run the plug-in code first in IRAM and the
> plugin-in code need appear at the beginning of the u-boot. ROM will
> check the plugin-in header to do security check and run the plug-in
> code to init the DDR etc. In this case the _start will be not the same
> as TEXT_BASE.
I still don't see why u-boot would not end up where specified.
The fact that there is a "plug-in" (I assume it's what I would call an
IPL) does not change the fact that its payload (u-boot) can and will be
loaded where specified, i.e. at TEXT_BASE -- and if it is loaded
elsewhere, it is at a fixed address, so TEXT_BASE can be adjusted) All
IPLs that I know of put their payload where specified.
> Thanks for your comments. Cheers,
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-12-16 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 13:57 [U-Boot] [PATCH 1/1] armv7: start.S: Fix relocation address caculation Jason Liu
2010-12-15 17:06 ` Albert ARIBAUD
2010-12-16 3:04 ` Jason Liu
2010-12-16 9:04 ` Albert ARIBAUD [this message]
2010-12-16 9:18 ` Jason Liu
2010-12-16 9:58 ` Albert ARIBAUD
2010-12-16 10:09 ` Wolfgang Denk
2010-12-16 10:22 ` Jason Liu
2010-12-16 12:20 ` Wolfgang Denk
2010-12-16 9:53 ` Wolfgang Denk
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=4D09D601.7010702@free.fr \
--to=albert.aribaud@free.fr \
--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