From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: mvebu: fix RAM size for Armada XP board DB-MV784MP-GP
Date: Thu, 14 Mar 2013 10:22:36 -0600 [thread overview]
Message-ID: <20130314162236.GA19701@obsidianresearch.com> (raw)
In-Reply-To: <1363276674-24172-1-git-send-email-jason@lakedaemon.net>
On Thu, Mar 14, 2013 at 03:57:54PM +0000, Jason Cooper wrote:
> The board is supplied with a 4GB RAM module. This value can be
> overridden by the bootloader based on probed memory size. We set it to
> a reasonable value here.
>
> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
> Changes from v1:
> - grammatical fix suggested by Sergei Shtylyov
> - correct size suggested by several folks (within 32bit, 1 dword)
>
> As promised, catching this fix in the -rc cycle.
>
> For those not familiar, earlier versions of the patch adding this board listed
> 3GB because that is all that was visible. I mistaken applied v3 of the patch
> instead of v4 which properly listed 4GB. This patch cleans up my error.
What happens when the kernel tries to treat 0xD0000000 and above as
memory? Lots of internal register blocks overlap 0 -> 4GB - won't this
cause resource conflicts on boot? I'm actually very surprised it boots
at all - what does /proc/iomem say?
Jason
next prev parent reply other threads:[~2013-03-14 16:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 17:21 [PATCH v4 0/2] Adding support for the new Armada XP development board from Marvell Gregory CLEMENT
2013-02-04 17:21 ` Gregory CLEMENT
2013-02-04 17:21 ` [PATCH v4 1/2] arm: mvebu: update defconfig with ATAG support when using DT Gregory CLEMENT
2013-02-04 17:21 ` Gregory CLEMENT
2013-02-16 16:48 ` Jason Cooper
2013-02-16 16:48 ` Jason Cooper
2013-02-04 17:21 ` [PATCH v4 2/2] arm: mvebu: support for the new Armada XP development board(DB-MV784MP-GP) Gregory CLEMENT
2013-02-04 17:21 ` Gregory CLEMENT
2013-02-16 16:44 ` Jason Cooper
2013-02-16 16:44 ` Jason Cooper
2013-03-12 15:12 ` [PATCH] ARM: mvebu: fix RAM size for Armada XP board DB-MV784MP-GP Jason Cooper
2013-03-13 14:30 ` Sergei Shtylyov
2013-03-13 14:37 ` Gregory CLEMENT
2013-03-13 14:50 ` Jason Cooper
2013-03-13 17:35 ` Jason Gunthorpe
2013-03-13 17:43 ` Andrew Lunn
2013-03-13 18:30 ` Jason Gunthorpe
2013-03-13 14:39 ` Jason Cooper
2013-03-13 14:42 ` Gregory CLEMENT
2013-03-13 14:54 ` Jason Cooper
2013-03-13 17:13 ` Jason Gunthorpe
2013-03-14 15:39 ` Jason Cooper
2013-03-14 15:57 ` [PATCH V2] " Jason Cooper
2013-03-14 16:22 ` Jason Gunthorpe [this message]
2013-03-14 16:56 ` Jason Cooper
2013-03-14 17:22 ` Gregory CLEMENT
2013-03-14 17:30 ` Jason Cooper
2013-03-14 17:46 ` [PATCH V3] " Jason Cooper
2013-03-21 18:49 ` 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=20130314162236.GA19701@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.