Hello, I have a board here that needs more than the currently available malloc space. The size of the malloc space depends on memory size. On mvebu there is an initial assumption of 64 MiB RAM that is later corrected. When the malloc memory is set aside (half of the available RAM) the number isn't corrected yet. So this patch set makes it necessary to let the board define the available amount of RAM. As before just saying 64 MiB works fine. And if a board wants more malloc space, it can specify the actual size. The first patch the initial memory size is just pushed to the board files with no change in functionality. The second patch changes a board to the really available RAM. Uwe Kleine-König (2): mvebu: make boards pass initial memory size netgear-rn2120: use complete memory from the start arch/arm/boards/globalscale-guruplug/lowlevel.c | 2 +- arch/arm/boards/globalscale-mirabox/lowlevel.c | 2 +- arch/arm/boards/lenovo-ix4-300d/lowlevel.c | 2 +- arch/arm/boards/marvell-armada-xp-gp/lowlevel.c | 2 +- arch/arm/boards/netgear-rn104/lowlevel.c | 2 +- arch/arm/boards/netgear-rn2120/lowlevel.c | 2 +- arch/arm/boards/plathome-openblocks-a6/lowlevel.c | 2 +- arch/arm/boards/plathome-openblocks-ax3/lowlevel.c | 2 +- arch/arm/boards/solidrun-cubox/lowlevel.c | 2 +- arch/arm/boards/usi-topkick/lowlevel.c | 2 +- arch/arm/mach-mvebu/include/mach/lowlevel.h | 2 +- arch/arm/mach-mvebu/lowlevel.c | 15 +++++++-------- 12 files changed, 18 insertions(+), 19 deletions(-) -- 2.11.0 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
