From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question about relocation
Date: Sun, 17 Apr 2011 19:57:05 +0200 [thread overview]
Message-ID: <20110417175705.GA28484@mail.gnudd.com> (raw)
In-Reply-To: <4DAB1D92.3080907@aribaud.net>
> beginning-to-end copy or an end-to-beginning copy depending on the
> source and destination addresses and size.
Ori, simply, end-to-beginning when moving up. Or always
end-to-beginning since we are expected to always move up (upper than
the target address it can't run).
It is safer, but not safe. Also, it's difficult to accomplish bcause
copying and fixing addresses is done ina single run, so the relocation
tables are read from the old area. Possibly relocatng first and
copying then.
Or, easier: if we are already high enough to overlap, don't relocate
at all. If it's acceptable, I'll patch for taht.
thanks
/alessandro
next prev parent reply other threads:[~2011-04-17 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 1:19 [U-Boot] Question about relocation Alessandro Rubini
2011-04-17 17:04 ` Albert ARIBAUD
2011-04-17 17:57 ` Alessandro Rubini [this message]
2011-04-17 18:23 ` Albert ARIBAUD
2011-04-17 19:30 ` Alessandro Rubini
2011-04-17 19:47 ` Albert ARIBAUD
2011-04-18 9:16 ` Alessandro Rubini
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=20110417175705.GA28484@mail.gnudd.com \
--to=rubini-list@gnudd.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