Vladimir Zapolskiy 9c141b2bd7 sh4: fix start.S by calling board_init_f() after first code relocation ... Like on ARM platform keep the first code relocation from a U-boot image storage to RAM at CONFIG_SYS_TEXT_BASE, then pass execution to a generic board_init_f() with empty GD flags. If CONFIG_SYS_TEXT_BASE is equal to a calculated by board_init_f() relocation address there will be no more code and data copy, however it's worth to mention that the first copy happens even if $pc on _start is the same as CONFIG_SYS_TEXT_BASE, on practice this works without a problem. Also note that _sh_start is renamed back to _start to correct gd->mon_len calculation by setup_mon_len(), the opposite rename was done in pre-generic board commit 2024b968ee ("sh: Fix build in start.S"). Signed-off-by: Vladimir Zapolskiy <vz@mleia.com> Reviewed-by: Simon Glass <sjg@chromium.org>		2016-12-02 21:32:53 -05:00
..
sh2	sh: add shared relocate_code() function and call board_init_r()	2016-12-02 21:32:52 -05:00
sh3	sh: add shared relocate_code() function and call board_init_r()	2016-12-02 21:32:52 -05:00
sh4	sh4: fix start.S by calling board_init_f() after first code relocation	2016-12-02 21:32:53 -05:00
u-boot.lds	sh: add MEMORY command to a shared linker script	2016-12-02 21:32:48 -05:00