From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/2] mvebu: make more RAM available from malloc
Date: Fri, 10 Feb 2017 16:50:58 +0100 [thread overview]
Message-ID: <20170210155100.16463-1-u.kleine-koenig@pengutronix.de> (raw)
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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-02-10 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:50 Uwe Kleine-König [this message]
2017-02-10 15:50 ` [PATCH 1/2] mvebu: make boards pass initial memory size Uwe Kleine-König
2017-02-13 8:06 ` Sascha Hauer
2017-02-10 15:51 ` [PATCH 2/2] netgear-rn2120: use complete memory from the start Uwe Kleine-König
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=20170210155100.16463-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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