[U-Boot] [U-Boot, RESEND, 21/24] sh4: fix start.S by calling board_init_f() after first code relocation

Tom Rini
2016-12-04T00:42:41Z

On Mon, Nov 28, 2016 at 12:15:33AM +0200, Vladimir Zapolskiy wrote:

> 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 2024b968ee9 ("sh: Fix build in start.S").
>
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>

Applied to u-boot/master, thanks!

--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161203/00c2890d/attachment.sig>