Hi Yannick, On 08/07/15 19:51, Yannick GICQUEL wrote:
Even if SRAM is not used, this is required to avoid inconsistency at runtime. Otherwise, an assertion failed in ld.so during init process execution: Inconsistency detected by ld.so: rtld.c: 1290: dl_main: Assertion `_rtld_local._dl_rtld_map.l_libname' failed!
Can you explain further? Is this really the underlying problem? Surely the presence of the SRAM block mapped in shouldn't have any impact on running applications. Where does CONFIG_SRAM_BASE come from? I didn't see in this series anywhere. Regards Greg
Signed-off-by: Yannick GICQUEL <yannick.gicquel@xxxxxxxxx> --- arch/m68k/coldfire/head.S | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/arch/m68k/coldfire/head.S b/arch/m68k/coldfire/head.S index fa31be2..bf39885 100644 --- a/arch/m68k/coldfire/head.S +++ b/arch/m68k/coldfire/head.S @@ -151,6 +151,15 @@ _start0: _start: nop /* filler */ +#if defined(CONFIG_M5441x) +#if defined(CONFIG_SRAM_BASE) + movel #(CONFIG_SRAM_BASE+0x221), %d0 +#else + movel #(0x8ff00000+0x221), %d0 +#endif + movec %d0, %rambar1 +#endif + movew #0x2700, %sr /* no interrupts */ movel #CACHE_INIT,%d0 /* disable cache */ movec %d0,%CACR
-- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
