mirror of
https://github.com/AsahiLinux/u-boot
synced 2025-02-17 22:49:02 +00:00
board_f: fix calculation of reloc_off
relocate_code() calculates the relocation offset wrt. the symbol __image_copy_start which happens to have the same value as CONFIG_TEXT_BASE on most systems. When creating an i.MX boot image with an integrated IVT it is convenient to have CONFIG_TEXT_BASE point to the start of the IVT that is prepended to the actual code. Thus CONFIG_TEXT_BASE will differ from __image_copy_start, while the calculation 'gd->relocaddr - __image_copy_start' still gives the right relocation offset. Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de>
This commit is contained in:
parent
69c5d76f2f
commit
53207bfd70
1 changed files with 5 additions and 2 deletions
|
@ -644,13 +644,16 @@ static int setup_reloc(void)
|
|||
}
|
||||
|
||||
#ifdef CONFIG_SYS_TEXT_BASE
|
||||
gd->reloc_off = gd->relocaddr - CONFIG_SYS_TEXT_BASE;
|
||||
#ifdef CONFIG_M68K
|
||||
#ifdef ARM
|
||||
gd->reloc_off = gd->relocaddr - (unsigned long)__image_copy_start;
|
||||
#elif defined(CONFIG_M68K)
|
||||
/*
|
||||
* On all ColdFire arch cpu, monitor code starts always
|
||||
* just after the default vector table location, so at 0x400
|
||||
*/
|
||||
gd->reloc_off = gd->relocaddr - (CONFIG_SYS_TEXT_BASE + 0x400);
|
||||
#else
|
||||
gd->reloc_off = gd->relocaddr - CONFIG_SYS_TEXT_BASE;
|
||||
#endif
|
||||
#endif
|
||||
memcpy(gd->new_gd, (char *)gd, sizeof(gd_t));
|
||||
|
|
Loading…
Add table
Reference in a new issue