On Mon, Jan 20, 2014 at 02:30:39PM +0400, Alexey Brodkin wrote:

> This is only required for "PIC" relocation and doesn't apply to modern
> "PIE" relocation which does data relocation as well as code.
> 
> "init_sequence_r" is just an array that consists of compile-time
> adresses of init functions. Since this is basically an array of integers
> (pointers to "void" to be more precise) it won't be modified during
> relocation - it will be just copied to new location as it is.
> 
> As a consequence on execution after relocation "initcall_run_list" will
> be jumping to pre-relocation addresses. As long as we don't overwrite
> pre-relocation memory area init calls are executed correctly. But still
> it is dangerous because after relocation we don't expect initially used
> memory to stay untouched.
> 
> Signed-off-by: Alexey Brodkin <abrod...@synopsys.com>
> 
> Cc: Tom Rini <tr...@ti.com>
> Cc: Simon Glass <s...@chromium.org>
> Cc: Masahiro Yamada <yamad...@jp.panasonic.com>
> Cc: Doug Anderson <diand...@chromium.org>
> Cc: Thomas Langer <thomas.lan...@lantiq.com>
> Cc: Albert ARIBAUD <albert.u.b...@aribaud.net>

Applied to u-boot/master, thanks!

-- 
Tom

Attachment: signature.asc
Description: Digital signature

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to