From: Krzysztof Halasa <khc@pm.waw.pl>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Implement ALTERNATE memory layout.
Date: Sat, 30 Mar 2013 20:57:13 +0100 [thread overview]
Message-ID: <m3k3oopso6.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1364649788.298722850@f238.mail.ru> (Alexander Shiyan's message of "Sat, 30 Mar 2013 17:23:09 +0400")
Alexander Shiyan <shc_work@mail.ru> writes:
>> >> +config MEMORY_LAYOUT_ALTERNATE
>> >> + bool "use alternate memory layout"
>> >> + help
>> >> + select this option to use barebox's alternate memory layout:
>> >> +
>> >> + TEXT_BASE
>> >> + -----
>> >> + malloc heap
>> >> + -----
>> >> + stack
>> >> +
>> >
>> > This should be described better.
>>
>> Well... I did it after the default layout. What do you propose?
>
> I cannot say more.
> Since this option globally for all barebox targets, it is necessary to
> describe all aspects of its application.
But what "aspects" are you thinking about? This simply swaps the order
in which text (+data/bss) and heap appear in memory.
OTOH I think I should probably restrict its use to ARM, since the code
is ARM-only.
--
Krzysztof Halasa
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-03-30 19:57 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 [this message]
2013-03-30 18:45 ` Antony Pavlov
2013-04-01 18:04 ` Sascha Hauer
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=m3k3oopso6.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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