From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spl: Allow settings malloc_f base address
Date: Wed, 25 May 2016 14:16:02 +0200 [thread overview]
Message-ID: <57459782.6090604@denx.de> (raw)
In-Reply-To: <CAPnjgZ11xDMfu9Qae9YRk7H4yLWFi=hg8AVPtSOD+x0pN7E5nA@mail.gmail.com>
On 05/25/2016 05:30 AM, Simon Glass wrote:
> Hi Marek,
Hi!
> On 24 May 2016 at 18:14, Marek Vasut <marex@denx.de> wrote:
>> Allow configuring the begining of the malloc_f area in SPL.
>> This patch uses the same CONFIG_MALLOC_F_ADDR established by
>> the sandbox.
>
> What is this used for? Is the existing scheme (using the stack space)
> not suitable? I think it should move to Kconfig before being used more
> widely.
In case your stack is waaay too constrained, then this is not suitable,
yep :(
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Tom Rini <trini@konsulko.com>
>> Cc: Simon Glass <sjg@chromium.org>
>> ---
>> common/spl/spl.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/common/spl/spl.c b/common/spl/spl.c
>> index 93f9bd1..56c64d1 100644
>> --- a/common/spl/spl.c
>> +++ b/common/spl/spl.c
>> @@ -160,6 +160,9 @@ int spl_init(void)
>>
>> debug("spl_init()\n");
>> #if defined(CONFIG_SYS_MALLOC_F_LEN)
>> +#ifdef CONFIG_MALLOC_F_ADDR
>> + gd->malloc_base = CONFIG_MALLOC_F_ADDR;
>> +#endif
>> gd->malloc_limit = CONFIG_SYS_MALLOC_F_LEN;
>> gd->malloc_ptr = 0;
>> #endif
>> --
>> 2.7.0
>>
>
> Regards,
> Simon
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-05-25 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 0:14 [U-Boot] [PATCH] spl: Allow settings malloc_f base address Marek Vasut
2016-05-25 3:30 ` Simon Glass
2016-05-25 12:16 ` Marek Vasut [this message]
2016-06-03 13:59 ` [U-Boot] " Tom Rini
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=57459782.6090604@denx.de \
--to=marex@denx.de \
--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