From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] arm: mvebu: limit OpenBlocks AX3-4 to 1 GB of RAM
Date: Fri, 04 Jan 2013 18:26:35 +0100 [thread overview]
Message-ID: <50E710CB.8070007@lunn.ch> (raw)
In-Reply-To: <1357315498-4570-2-git-send-email-thomas.petazzoni@free-electrons.com>
On 04/01/13 17:04, Thomas Petazzoni wrote:
> Signed-off-by: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
> ---
> This is a fix for 3.8, should be pushed for some 3.8-rc.
> ---
> arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts b/arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts
> index 72a9dd0..3e9ee1b 100644
> --- a/arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts
> +++ b/arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts
> @@ -23,7 +23,13 @@
>
> memory {
> device_type = "memory";
> - reg =<0x00000000 0xC0000000>; /* 3 GB */
> + /*
> + * The board has an additional 2 GB DRAM chip in an
> + * expansion slot, but using it makes the system very
> + * unstable: it even doesn't boot reliably. So we use
> + * only the soldered 1 GB chip for now.
> + */
> + reg =<0x00000000 0x40000000>; /* 1 GB */
> };
>
> soc {
Hi Thomas
How many different boards have you tried?
I've not had problems with the board i have. Using the plathome supplied
kernel, i've rebuilt the kernel, which is a good memory test. Using
mainline, i've booted a number of times when developing the thermal
driver and not had problems.
I would hate to disable 2GB of RAM just because your board has a fault.
Andrew
next prev parent reply other threads:[~2013-01-04 17:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 16:04 arm: mvebu: DT fixes for 3.8 Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 1/4] arm: mvebu: limit OpenBlocks AX3-4 to 1 GB of RAM Thomas Petazzoni
2013-01-04 17:26 ` Andrew Lunn [this message]
2013-01-04 17:31 ` Thomas Petazzoni
2013-01-04 17:37 ` Andrew Lunn
2013-01-04 18:03 ` Thomas Petazzoni
2013-01-06 21:36 ` Gregory CLEMENT
2013-01-06 22:53 ` Thomas Petazzoni
2013-01-07 9:47 ` Andrew Lunn
2013-01-07 11:07 ` Andrew Lunn
2013-01-07 11:26 ` Thomas Petazzoni
2013-01-07 11:34 ` Andrew Lunn
2013-01-07 12:27 ` Gregory CLEMENT
2013-01-07 13:22 ` Andrew Lunn
2013-02-26 15:20 ` Thomas Petazzoni
2013-02-27 7:03 ` Andrew Lunn
2013-02-27 8:33 ` Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 2/4] arm: mvebu: Armada XP MV78230 has two cores, not one Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 3/4] arm: mvebu: Armada XP MV78230 has only three Ethernet interfaces Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 4/4] arm: mvebu: indentation fixes for Armada 370/XP .dtsi files Thomas Petazzoni
2013-01-06 9:03 ` Andrew Lunn
2013-01-07 16:53 ` Thomas Petazzoni
2013-01-07 16:55 ` Jason Cooper
2013-01-07 17:04 ` Thomas Petazzoni
2013-01-07 17:08 ` Jason Cooper
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=50E710CB.8070007@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@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