From: yehuda80 <yehuda80@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Avoiding reload on ARM U-BOOT
Date: Thu, 2 Feb 2012 07:03:18 -0800 (PST) [thread overview]
Message-ID: <33250726.post@talk.nabble.com> (raw)
Hello everyone
im trying to port u-boot 2011-09 to a new board with an arm based SOC
i found that u-boot will always relocate the code even if it is placed
already in DDR which is the case with my SOC.
is there any clean way to avoid relocating the u-boot ? does the various SPL
configs have something to do with that ?
if yes which one should i define ?
Thanks in advance
Yehuda
--
View this message in context: http://old.nabble.com/Avoiding-reload-on-ARM-U-BOOT-tp33250726p33250726.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2012-02-02 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 15:03 yehuda80 [this message]
2012-02-02 19:34 ` [U-Boot] Avoiding reload on ARM U-BOOT Marek Vasut
[not found] ` <CAN2=dsw9rAkzKftow5Opo5vpXFiUz90i7941+WfViwN_BwqAkA@mail.gmail.com>
2012-02-03 8:15 ` Marek Vasut
2012-02-05 14:08 ` yehuda yitchak
2012-02-05 14:22 ` Marek Vasut
2012-02-05 15:09 ` Stefano Babic
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=33250726.post@talk.nabble.com \
--to=yehuda80@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