On 07/16/2012 04:31 PM, Sascha Hauer wrote: > On Mon, Jul 16, 2012 at 11:53:59AM +0200, Christian Kapeller wrote: >> >> diff --git a/arch/arm/configs/tx51stk5_defconfig b/arch/arm/configs/tx51stk5_defconfig >> index 7fff0f0..e1796b9 100644 >> --- a/arch/arm/configs/tx51stk5_defconfig >> +++ b/arch/arm/configs/tx51stk5_defconfig >> @@ -32,7 +32,6 @@ CONFIG_HAVE_CONFIGURABLE_TEXT_BASE=y >> CONFIG_HAVE_CONFIGURABLE_MEMORY_LAYOUT=y >> CONFIG_MEMORY_LAYOUT_DEFAULT=y >> CONFIG_MALLOC_TLSF=y >> -CONFIG_KALLSYMS=y > > Of course I rather would like to fix the underlying issue. Does this > happen on a second stage barebox aswell? I hear you. My intend was to have at least a booting board, rather than a brick. I just flashed tx51 barebox without CONFIG_KALLSYMS, and could successfully start a barebox binary with CONFIG_KALLSYMS set using bootm. _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
