diff options
| author | Simon Glass <sjg@chromium.org> | 2019-10-22 02:26:50 +0300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2019-10-27 19:56:51 +0300 |
| commit | ac9cd4805c8b11f529b508921c2275b889265313 (patch) | |
| tree | 9e5e40ea153b77ad4c2977d5694c88d0ee76b851 /common/board_f.c | |
| parent | 65b2d96f4c5e3f9084bc04cf5a5d7fc7a2285a72 (diff) | |
| download | u-boot-ac9cd4805c8b11f529b508921c2275b889265313.tar.xz | |
bootstage: Correct relocation algorithm
At present bootstage relocation assumes that it is possible to point back
to memory available before relocation, so it does not relocate the
strings. However this is not the case on some platforms, such as x86 which
uses the cache as RAM and loses access to this when the cache is enabled.
Move the relocation step to before U-Boot relocates, expand the allocated
region to include space for the strings and relocate the strings at the
same time as the bootstage records.
This ensures that bootstage data can remain accessible from TPL through
SPL to U-Boot before/after relocation.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'common/board_f.c')
| -rw-r--r-- | common/board_f.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/common/board_f.c b/common/board_f.c index 4852a3b0d8..e3591cbaeb 100644 --- a/common/board_f.c +++ b/common/board_f.c @@ -696,6 +696,7 @@ static int reloc_bootstage(void) gd->bootstage, gd->new_bootstage, size); memcpy(gd->new_bootstage, gd->bootstage, size); gd->bootstage = gd->new_bootstage; + bootstage_relocate(); } #endif |