From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: fix RAM size for Armada XP board DB-MV784MP-GP
Date: Wed, 13 Mar 2013 11:35:59 -0600 [thread overview]
Message-ID: <20130313173559.GD24042@obsidianresearch.com> (raw)
In-Reply-To: <51408F0C.2010408@free-electrons.com>
On Wed, Mar 13, 2013 at 03:37:00PM +0100, Gregory CLEMENT wrote:
> >> + * size of the module actually plugged
> >> */
> >> - reg = <0x00000000 0xC0000000>;
> >> + reg = <0x00000000 0xD0000000>;
> >
> > But this is not 4G?
>
> You're totally right!
> It should be reg = <0x00000000 0xF0000000>;
Isn't it 'right' as it is? The various included DT's put devices at
address 0xd0008000 for instance, memory shouldn't overlap that..
Ie you loose the address space 0xD0000000 -> 0x100000000 due to
internal registers.
If the HW supports > 32 bit physical addressing then you'd want to
program the DDR mapping to put some of the DDR above the 4G limit.
Cheers,
Jason
next prev parent reply other threads:[~2013-03-13 17:35 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 [this message]
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
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=20130313173559.GD24042@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.