public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: atmel: cpux9k2: increase malloc space to fix crash on start u-boot
Date: Wed, 18 Sep 2013 16:44:29 +0200	[thread overview]
Message-ID: <5239BC4D.805@gmail.com> (raw)
In-Reply-To: <1379513592-5470-1-git-send-email-esw@bus-elektronik.de>

Dear Jens Scharsig,

On 09/18/2013 04:13 PM, Jens Scharsig (BuS Elektronik) wrote:
> From: "Jens Scharsig (BuS Elektronik)" <esw@bus-elektronik.de>
> 
> Since UBIFS is enabled for cpux9k2, more malloc space is needed.
> For the current uboot 2013.10-rcX the size is to small, this will fix the
> startup problems by increasing the mallog space.
> 
> Signed-off-by: Jens Scharsig (BuS Elektronik) <esw@bus-elektronik.de>
> ---
>  include/configs/eb_cpux9k2.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/configs/eb_cpux9k2.h b/include/configs/eb_cpux9k2.h
> index ccc7bd0..7aca74b 100644
> --- a/include/configs/eb_cpux9k2.h
> +++ b/include/configs/eb_cpux9k2.h
> @@ -83,7 +83,7 @@
>   * Size of malloc() pool
>   */
>  
> -#define CONFIG_SYS_MALLOC_LEN		(CONFIG_ENV_SIZE + 520*1024)
> +#define CONFIG_SYS_MALLOC_LEN		(1024 * 1024)

are you sure 1MiB is enough? We had from time to time problems
initializing an unsafe closed UBI (about 512MiB). With 4MiB malloc arena
however we never had these problems.

Best regards

Andreas Bie?mann

  reply	other threads:[~2013-09-18 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 14:13 [U-Boot] [PATCH] arm: atmel: cpux9k2: increase malloc space to fix crash on start u-boot Jens Scharsig
2013-09-18 14:44 ` Andreas Bießmann [this message]
2013-09-18 15:56   ` Jens Scharsig

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=5239BC4D.805@gmail.com \
    --to=andreas.devel@googlemail.com \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox