path: root/README
diff options
authorFabio Estevam <>2015-11-12 12:30:19 -0200
committerTom Rini <>2015-11-12 20:34:07 -0500
commit9ac4fc82071ce346e3885118242ff45d22f69b82 (patch)
tree1faf780ca9c79168f1eecc7dacefed02df1900d4 /README
parentbc80109b117abe4ed2cd4d12c8dc188561bc298e (diff)
board_init: Change the logic to setup malloc_base
Prior to commit 5ba534d247d418 ("arm: Switch 32-bit ARM to using generic global_data setup") we used to have assembly code that configured the malloc_base address. Since this commit we use the board_init_f_mem() function in C to setup malloc_base address. In board_init_f_mem() there was a deliberate choice to support only early malloc() or full malloc() in SPL, but not both. Adapt this logic to allow both to be used, one after the other, in SPL. This issue has been observed in a Congatec board, where we need to retrieve the manufacturing information from the SPI NOR (the SPI API calls malloc) prior to configuring the DRAM. In this case as malloc_base was not configured we always see malloc to fail. With this change we are able to use malloc in SPL prior to DRAM gets initialized. Also update the CONFIG_SYS_SPL_MALLOC_START entry in the README file. Signed-off-by: Fabio Estevam <> Reviewed-by: Simon Glass <>
Diffstat (limited to 'README')
1 files changed, 3 insertions, 0 deletions
diff --git a/README b/README
index e98c49b6b7..32c5ea6653 100644
--- a/README
+++ b/README
@@ -3577,6 +3577,9 @@ FIT uImage format:
Starting address of the malloc pool used in SPL.
+ When this option is set the full malloc is used in SPL and
+ it is set up by spl_init() and before that, the simple malloc()
+ can be used if CONFIG_SYS_MALLOC_F is defined.
The size of the malloc pool used in SPL.
OpenPOWER on IntegriCloud