mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kevin Du Huanpeng <u74147@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: How much ram is needed to run barebox by default config?
Date: Mon, 9 Dec 2013 08:24:39 +0100	[thread overview]
Message-ID: <20131209072438.GH24559@pengutronix.de> (raw)
In-Reply-To: <002501cef29e$f44aa410$dcdfec30$@gmail.com>

On Sat, Dec 07, 2013 at 12:19:31AM +0800, Kevin Du Huanpeng wrote:
> I am porting barebox to my router, ar9331 MIPS 24kc 400MHz, 32MB RAM, 4MB Flash.
> I don't know what is the proper size to set the stack and malloc.

8MiB for malloc space should be fine.

> - - -
> initcall-> 0x80068168
> INITCALL->
> initcall-> 0x80063f0c
> malloc space: 0x80020000 -> 0x8005ffff (size 2147876864.134217718 EiB)
> INITCALL->
> initcall-> 0x800640d8
> INITCALL->
> - - -
> Look at the LINE 4, it's strange.

This is indeed strange. size_human_readable takes an unsigned long long
argument, but it is passed an unsigned long argument. It looks like you
have garbage in the upper 32bits. I have no idea what happens there,
this should normally work.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-12-09  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 15:41 Kevin Du Huanpeng
2013-12-06 15:46 ` Alexander Shiyan
2013-12-06 16:19   ` Kevin Du Huanpeng
2013-12-09  7:24     ` Sascha Hauer [this message]
2013-12-09  7:32       ` Alexander Aring

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=20131209072438.GH24559@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=u74147@gmail.com \
    /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