Alexey Brodkin 7395398ad2 board_r - fixup functions table after relocation
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.

Cc: Tom Rini <trini@ti.com>
Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: Doug Anderson <dianders@chromium.org>
Cc: Thomas Langer <thomas.langer@lantiq.com>
Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
Acked-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
2014-01-27 08:28:13 -05:00
..
2013-04-01 16:33:52 -04:00
2013-04-01 16:33:52 -04:00
2011-04-08 00:44:27 -04:00
2013-08-16 13:45:15 -04:00
2014-01-09 11:47:51 +02:00
2013-11-08 15:25:14 -05:00
2013-05-31 17:12:03 -05:00
2014-01-09 16:08:11 +01:00
2012-08-09 23:39:18 +02:00
2013-04-01 16:33:52 -04:00
2013-04-01 16:33:52 -04:00
2014-01-14 09:01:06 -05:00
2014-01-14 09:01:06 -05:00
2013-08-06 23:58:43 +05:30
2011-12-07 08:41:22 +01:00
2013-09-20 10:30:54 -04:00
2013-09-20 10:30:54 -04:00
2010-01-18 00:23:00 +01:00
2013-11-12 09:35:17 +01:00
2011-10-22 01:13:35 +02:00