From: Jaccon Bastiaansen <jaccon.bastiaansen@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, festevam@gmail.com, gfm@funxed.com
Subject: Re: [PATCH] Increase heapsize for i.MX21ADS board again.
Date: Fri, 27 Apr 2012 13:00:20 +0200 [thread overview]
Message-ID: <CAGzjT4eZr_K7UuGxsQ0vbSjc3d5JrOwB8t3mbY-aqMUk5PNc-g@mail.gmail.com> (raw)
In-Reply-To: <20120427074753.GU17184@pengutronix.de>
Hello Sascha
Op 27 april 2012 09:47 heeft Sascha Hauer <s.hauer@pengutronix.de> het
volgende geschreven:
> On Thu, Apr 26, 2012 at 09:03:59PM +0200, Jaccon Bastiaansen wrote:
>> Barebox cannot boot the recent mainline Linux kernels for the
>> i.MX21ADS board anymore when using TFTP, because the heap is too
>> small.
>>
>> This is solved by increasing the heapsize to 8Mbyte.
>
> This board has 64M of SDRAM, why don't you simply increase it to say
> 32MB? It's not that you need the memory for something else in barebox.
>
Ok, I will do that.
> BTW could you test the i.MX clock framework patches I posted to ARM
> Linux Kernel? I have no i.MX21 hardware, so I ported the i.MX21
> completely blind. It would be good to test this before we break
> mainline
>
I'm currently working on getting the mainline kernel to run again on
the iMX21ADS board. The current mainline kernel crashes very early in
the boot sequence without showing anything on the terminal. I already
solved that crash (the same virtual address range was used twice when
statically mapping I/O memory), but the ethernet driver (cs89x0) still
crashes because of an invalid memory access. You can expect some
patches in the coming days.
When I have the mainline working again, I will test the clock framework patches.
> Thanks
> Sascha
>
>>
>> Signed-off-by: Jaccon Bastiaansen <jaccon.bastiaansen@gmail.com>
>> ---
>> arch/arm/configs/mx21ads_defconfig | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/configs/mx21ads_defconfig b/arch/arm/configs/mx21ads_defconfig
>> index 175c229..6726d8c 100644
>> --- a/arch/arm/configs/mx21ads_defconfig
>> +++ b/arch/arm/configs/mx21ads_defconfig
>> @@ -3,7 +3,7 @@ CONFIG_ARCH_IMX21=y
>> CONFIG_IMX_CLKO=y
>> CONFIG_ARM_OPTIMZED_STRING_FUNCTIONS=y
>> CONFIG_TEXT_BASE=0xc1000000
>> -CONFIG_MALLOC_SIZE=0x500000
>> +CONFIG_MALLOC_SIZE=0x800000
>> CONFIG_LONGHELP=y
>> CONFIG_CMDLINE_EDITING=y
>> CONFIG_AUTO_COMPLETE=y
>> --
>> 1.7.1
>>
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>>
>
> --
> 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 |
Regards,
Jaccon
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-04-27 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:03 Jaccon Bastiaansen
2012-04-27 7:47 ` Sascha Hauer
2012-04-27 11:00 ` Jaccon Bastiaansen [this message]
2012-04-28 16:03 Jaccon Bastiaansen
2012-04-30 11:43 ` 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=CAGzjT4eZr_K7UuGxsQ0vbSjc3d5JrOwB8t3mbY-aqMUk5PNc-g@mail.gmail.com \
--to=jaccon.bastiaansen@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=festevam@gmail.com \
--cc=gfm@funxed.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox