From: E Robertson <e.robertson.svg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] reloacting uboot
Date: Tue, 25 Aug 2009 14:28:55 -0500 [thread overview]
Message-ID: <200908251428.55255.e.robertson.svg@gmail.com> (raw)
In-Reply-To: <20090825191136.55EAD833DBD2@gemini.denx.de>
On Tuesday 25 August 2009 02:11:36 pm Wolfgang Denk wrote:
> Dear E Robertson,
>
> In message <200908251403.20809.e.robertson.svg@gmail.com> you wrote:
> > I am using the at91sam9263 device from which the bootstrap code load
> > u-boot to the desired ram address. However, I would like to re-relocate
> > this at the different address based on memory availability. Can / or
> > should this be done?
>
> Yes, it can be done, and it should be done. The fact that we don't do
> it so far is due to the fact that the guys who did the original ARM
> code found this too complicated (even though they had a working
> example in the PowerPC code) and not worth the effort. We're suffering
> since from this misconception.
>
> But there is no reason why you would have to copy the code again -
> just copy it to the correct address right from the beginning, like we
> do in PowerPC.
I don't follow: Yes, but no reason to do so?
On the 9263, it's copied once to ram at boot. Are you saying their is no
reason to copy it again? If so, yes, in most cases that would be true but I
would like to move it again after that initial relocation. Since I've already
specified my start address, I wasn't sure about.
next prev parent reply other threads:[~2009-08-25 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 19:03 [U-Boot] reloacting uboot E Robertson
2009-08-25 19:11 ` Wolfgang Denk
2009-08-25 19:28 ` E Robertson [this message]
2009-08-25 20:39 ` Wolfgang Denk
2009-09-06 22:01 ` Ulf Samuelsson
2009-08-25 19:42 ` E Robertson
2009-08-25 20:43 ` 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=200908251428.55255.e.robertson.svg@gmail.com \
--to=e.robertson.svg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.