From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] arm: provide a CONFIG flag for disabling relocation
Date: Fri, 25 Mar 2011 15:12:31 +0100 [thread overview]
Message-ID: <20110325141231.C3684151F80@gemini.denx.de> (raw)
In-Reply-To: <1301058732-30898-1-git-send-email-aneesh@ti.com>
Dear Aneesh V,
In message <1301058732-30898-1-git-send-email-aneesh@ti.com> you wrote:
> Relocation may not be needed and desirable in many cases:
> * For many boards the amount of SDRAM is fixed.
> So relocation is not needed.
This is plain wrong. This has been explained a couple of times
before. Please read the archives.
> * Relocation adds un-necessary additional overhead when
> it's not needed. This delay is singificant on slower
> platforms such as FPGA
Do you have numbers? How much delay do you see caused by the
relocation of U-Boot?
> * Many boards have ample memory. So reserving enough memory
> for Linux in the first half is not a challenge even without
> relocation
You appear not to understand what relocation is needed for.
I tend to reject your patch, unless you can come up with really
convincing arguments. Also, your patch should then work for all
boards - not only ARM, but also PowerPC (one of the arguments for
relocation was that we want to unify the code).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Beware of bugs in the above code; I have only proved it correct, not
tried it." - Donald Knuth
next prev parent reply other threads:[~2011-03-25 14:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 13:12 [U-Boot] [RFC PATCH] arm: provide a CONFIG flag for disabling relocation Aneesh V
2011-03-25 13:27 ` Aneesh V
2011-03-25 14:12 ` Wolfgang Denk [this message]
2011-03-25 16:12 ` Aneesh V
2011-03-25 18:35 ` Albert ARIBAUD
2011-04-20 18:34 ` Simon Glass
2011-04-21 6:56 ` Aneesh V
2011-04-21 15:18 ` Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2011-09-20 14:22 GROYER, Anthony
2011-09-20 18:09 ` Wolfgang Denk
2011-09-20 19:13 ` Albert ARIBAUD
2011-09-21 9:29 ` GROYER, Anthony
2011-09-21 10:45 ` Wolfgang Denk
2011-09-21 11:44 ` Albert ARIBAUD
2011-09-21 10:51 ` Albert ARIBAUD
2011-09-21 11:20 ` Andreas Bießmann
2011-09-21 12:03 ` Albert ARIBAUD
2011-09-21 12:31 ` Andreas Bießmann
2011-09-21 14:23 ` Albert ARIBAUD
2011-09-22 7:10 ` Andreas Bießmann
2011-09-29 16:14 ` Andreas Bießmann
2011-09-30 7:21 ` Simon Schwarz
2011-10-01 6:48 ` Albert ARIBAUD
2011-09-20 21:34 ` Simon Glass
2011-09-21 14:21 ` Aneesh V
2011-09-23 16:04 ` Simon Glass
2011-10-01 7:01 ` Albert ARIBAUD
2011-10-03 3:34 ` Simon Glass
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=20110325141231.C3684151F80@gemini.denx.de \
--to=wd@denx.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