From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] arm926ejs: fix jump to RAM nand_boot
Date: Tue, 02 Nov 2010 10:42:22 +0100 [thread overview]
Message-ID: <4CCFDCFE.6010502@free.fr> (raw)
In-Reply-To: <4CCFDB14.3060809@emk-elektronik.de>
Le 02/11/2010 10:34, Reinhard Meyer a ?crit :
> My original message was: "please to not give people the idea that they can
> avoid relocation by loading u-boot at the exact address the relocation would
> calculate. That is bound to *really* break at the slightest change to u-boot."
Oh, I see. What you mean is "if people force the loading of u-boot at a
fixed address which happens to be its current relocated address, a
change of size in u-boot will break because the relocated address will
change but the forced address won't.
I was talking about a different thing, which is "if u-boot finds that
the address at which it runs now is the address at which it should run,
then it can skip relocation (copy and fixups)".
> Best Regards,
> Reinhard
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-11-02 9:42 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 17:43 [U-Boot] [RFC] arm926ejs: fix linker file for newer ld support Albert Aribaud
2010-10-31 18:11 ` Alexander Holler
2010-10-31 18:12 ` Wolfgang Denk
2010-10-31 18:31 ` Albert ARIBAUD
2010-10-31 18:36 ` Wolfgang Denk
2010-10-31 18:38 ` Alexander Holler
2010-10-31 19:01 ` Wolfgang Denk
2010-10-31 19:07 ` Albert ARIBAUD
2010-10-31 19:22 ` Wolfgang Denk
2010-10-31 19:40 ` Albert ARIBAUD
2010-10-31 19:59 ` Wolfgang Denk
2010-10-31 20:23 ` Albert ARIBAUD
2010-10-31 20:32 ` Wolfgang Denk
2010-10-31 21:20 ` [U-Boot] [RFC] arm926ejs: fix jump to RAM nand_boot Albert Aribaud
2010-10-31 21:51 ` Wolfgang Denk
2010-10-31 21:55 ` Albert ARIBAUD
2010-10-31 22:28 ` Alexander Holler
2010-10-31 23:04 ` Albert ARIBAUD
2010-11-01 5:13 ` sughosh ganu
2010-11-01 8:12 ` Albert ARIBAUD
2010-11-01 9:13 ` Wolfgang Denk
2010-11-01 9:15 ` Wolfgang Denk
2010-11-01 17:03 ` Albert ARIBAUD
2010-11-01 19:23 ` Wolfgang Denk
2010-11-01 19:30 ` Albert ARIBAUD
2010-11-01 19:35 ` Wolfgang Denk
2010-11-01 20:04 ` Albert ARIBAUD
2010-11-01 19:44 ` Graeme Russ
2010-11-01 19:53 ` Albert ARIBAUD
2010-11-01 20:01 ` Wolfgang Denk
2010-11-01 20:19 ` Scott Wood
2010-11-02 6:29 ` Heiko Schocher
2010-11-02 6:54 ` Albert ARIBAUD
2010-11-02 7:10 ` Heiko Schocher
2010-11-02 8:33 ` Wolfgang Denk
2010-11-02 8:55 ` Heiko Schocher
2010-11-02 9:17 ` Stefan Roese
2010-11-09 19:19 ` Scott Wood
2010-11-02 9:21 ` Sughosh Ganu
2010-11-02 8:57 ` Reinhard Meyer
2010-11-02 9:11 ` Albert ARIBAUD
2010-11-02 9:34 ` Reinhard Meyer
2010-11-02 9:42 ` Albert ARIBAUD [this message]
2010-11-03 6:37 ` V, Aneesh
2010-11-03 8:02 ` Wolfgang Denk
2010-11-03 10:39 ` V, Aneesh
2010-11-03 11:27 ` Wolfgang Denk
2010-11-03 12:03 ` V, Aneesh
2010-11-03 12:08 ` Albert ARIBAUD
2010-11-03 12:20 ` V, Aneesh
2010-11-03 13:00 ` Wolfgang Denk
2010-11-03 14:07 ` V, Aneesh
2010-11-03 18:25 ` Wolfgang Denk
2010-11-02 9:38 ` Wolfgang Denk
2010-11-02 9:47 ` Albert ARIBAUD
2010-11-02 9:56 ` Sughosh Ganu
2010-11-02 11:16 ` Albert ARIBAUD
2010-11-02 11:32 ` Sughosh Ganu
2010-11-02 13:28 ` Wolfgang Denk
2010-10-31 19:01 ` [U-Boot] [RFC] arm926ejs: fix linker file for newer ld support Albert ARIBAUD
2010-10-31 18:35 ` Darius Augulis
2010-10-31 18:53 ` Albert ARIBAUD
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=4CCFDCFE.6010502@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