From: Sascha Hauer <s.hauer@pengutronix.de>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Implement ALTERNATE memory layout.
Date: Mon, 1 Apr 2013 20:04:38 +0200 [thread overview]
Message-ID: <20130401180438.GZ1906@pengutronix.de> (raw)
In-Reply-To: <m3ip49gmds.fsf@intrepid.localdomain>
On Sat, Mar 30, 2013 at 12:25:35PM +0100, Krzysztof Halasa wrote:
> Signed-off-by: Krzysztof Hałasa <khc@pm.waw.pl>
>
> --- a/arch/arm/cpu/start.c
> +++ b/arch/arm/cpu/start.c
> @@ -58,7 +58,6 @@ static noinline __noreturn void __start(uint32_t membase, uint32_t memsize,
> endmem -= STACK_SIZE; /* Stack */
>
> if (IS_ENABLED(CONFIG_MMU_EARLY)) {
> -
> endmem &= ~0x3fff;
> endmem -= SZ_16K; /* ttb */
>
> @@ -66,6 +65,9 @@ static noinline __noreturn void __start(uint32_t membase, uint32_t memsize,
> mmu_early_enable(membase, memsize, endmem);
> }
>
> +#ifdef CONFIG_MEMORY_LAYOUT_ALTERNATE
> + malloc_end = endmem;
> +#else
We should not need a kconfig option for this. Why not just use the
biggest memory region we find? Whether this is below or above the
barebox binary doesn't need to be known at compile time.
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
next prev parent reply other threads:[~2013-04-01 18:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 11:19 IXP4xx again Krzysztof Halasa
2013-03-30 11:24 ` [PATCH] ARM: XScale processors don't support "clean+invalidate D entry" operation Krzysztof Halasa
2013-03-30 11:25 ` [PATCH] Implement ALTERNATE memory layout Krzysztof Halasa
2013-03-30 12:01 ` Alexander Shiyan
2013-03-30 13:15 ` Krzysztof Halasa
2013-03-30 13:23 ` Re[2]: " Alexander Shiyan
2013-03-30 19:57 ` Krzysztof Halasa
2013-03-30 18:45 ` Antony Pavlov
2013-04-01 18:04 ` Sascha Hauer [this message]
2013-04-02 7:20 ` Sascha Hauer
2013-03-30 11:26 ` [PATCH] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform Krzysztof Halasa
2013-04-02 6:52 ` Sascha Hauer
2013-04-07 11:42 ` Krzysztof Halasa
2013-04-07 19:54 ` [PATCH] ARM: Support for IXP4xx CPU Krzysztof Halasa
2013-04-08 7:27 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-14 10:30 ` Krzysztof Halasa
2013-04-14 11:51 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-07 19:55 ` [PATCH] ARM: Support for IXP4xx hardware Queue Manager Krzysztof Halasa
2013-04-08 7:31 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-07 19:57 ` [PATCH] ARM: Support for IXP4xx Network Processor Engines (NPEs) Krzysztof Halasa
2013-04-08 7:30 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-07 19:58 ` [PATCH] ARM: Support for IXP4xx built-in Ethernet interfaces Krzysztof Halasa
2013-04-08 7:29 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:56 ` [PATCH] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform 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=20130401180438.GZ1906@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=khc@pm.waw.pl \
/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