public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] Using spi_alloc_slave() from SPL
Date: Thu, 13 Aug 2015 15:37:45 +0300	[thread overview]
Message-ID: <55CC8F99.4050604@mail.bg> (raw)
In-Reply-To: <CAOMZO5AK2XHYvaG3TyoQ-UWqN4=m9a24DkKrw9mhh+fqvSwApA@mail.gmail.com>

Hi Fabio, guys,

On 08/07/2015 01:13 AM, Fabio Estevam wrote:
> Hi Simon,
>
> On Thu, Aug 6, 2015 at 4:31 PM, Simon Glass <sjg@chromium.org> wrote:
>
>> Please check the README about the SPL flow. From what I can see
>> malloc() is not available before board_init_r() in SPL.
>>
>> However, if you add a call to spl_init() from your board_init_f(),
>> then early malloc would be available. Enable this with
>> CONFIG_SYS_MALLOC_F_... as people explained.
>
> Cool, calling spl_init() from board_init_f() allows malloc to work fine.
>
> Thanks a lot!
>
> Fabio Estevam

Thanks for sharing this info, it seems it will solve a similar problem
of mine on the latest U-Boot code (SPI slave malloc not working during
SPL boot from SPI NOR).

Regards,
Nikolay

  reply	other threads:[~2015-08-13 12:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 13:25 [U-Boot] Using spi_alloc_slave() from SPL Fabio Estevam
2015-08-06 13:33 ` Marek Vasut
2015-08-06 13:38 ` Stefano Babic
2015-08-06 14:14   ` Fabio Estevam
2015-08-06 14:28     ` Marek Vasut
2015-08-06 16:44       ` Fabio Estevam
2015-08-06 17:03       ` Stefano Babic
2015-08-06 18:24         ` Fabio Estevam
2015-08-06 19:29           ` Fabio Estevam
2015-08-06 19:31           ` Simon Glass
2015-08-06 22:13             ` Fabio Estevam
2015-08-13 12:37               ` Nikolay Dimitrov [this message]
2015-11-10  0:05                 ` Fabio Estevam
2015-11-10 14:41                   ` Fabio Estevam
2015-11-09 23:28               ` Fabio Estevam
2015-08-06 22:22         ` Marek Vasut

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=55CC8F99.4050604@mail.bg \
    --to=picmaster@mail.bg \
    --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