All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kapeller <christian.kapeller@cmotion.eu>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] tx51: Disable kallsyms. It prevents the board from booting.
Date: Mon, 16 Jul 2012 16:41:45 +0200	[thread overview]
Message-ID: <50042829.4000606@cmotion.eu> (raw)
In-Reply-To: <20120716143147.GO30009@pengutronix.de>

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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-07-16 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  9:53 [PATCH 0/2] Misc Karo TX51 fixes Christian Kapeller
2012-07-16  9:53 ` [PATCH 1/2] tx51: ensure eth phy resets properly by driving reset pin explicitly Christian Kapeller
2012-07-16 14:25   ` Sascha Hauer
2012-07-16 14:31     ` Christian Kapeller
2012-07-16  9:53 ` [PATCH 2/2] tx51: Disable kallsyms. It prevents the board from booting Christian Kapeller
2012-07-16 14:31   ` Sascha Hauer
2012-07-16 14:41     ` Christian Kapeller [this message]
2012-07-16 15:16       ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50042829.4000606@cmotion.eu \
    --to=christian.kapeller@cmotion.eu \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.