linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: mvebu: Fix the memory size on the Mirabox
Date: Wed, 3 Apr 2013 12:46:08 +0200	[thread overview]
Message-ID: <20130403124608.5de971f1@skate> (raw)
In-Reply-To: <20130329193716.GA7127@localhost>

Dear Ezequiel Garcia,

On Fri, 29 Mar 2013 16:37:17 -0300, Ezequiel Garcia wrote:

> As far as I can remember, Gregory has a Mirabox with only 512 MiB,
> which means some boards were shipped with 512 MiB and some with 1 GiB.
> Moreover, apparently nothing can distinguish one from the other.

I do confirm that some Mirabox only have 512 MB of RAM, at least
according to U-Boot:

U-Boot 2009.08 (May 23 2012 - 16:35:03)Marvell version: 1.1.0 NQ
U-Boot Addressing:
       Code:		00600000:006AFFF0
       BSS:		006F8E40
       Stack:		0x5fff70
       PageTable:	0x8e0000
       Heap address:	0x900000:0xe00000
Board: DB-88F6710-BP
SoC:   MV6710 Z1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       DDR @ 600Mhz, TClock @ 200Mhz
       DDR 16Bit Width, FastPath Memory Access
PEX 0: Root Complex Interface, Detected Link X1
PEX 1: Root Complex Interface, Detected Link X1
DRAM:  512 MB
       CS 0: base 0x00000000 size 512 MB
       Addresses 14M - 0M are saved for the U-Boot usage.

The mvebu_defconfig contains CONFIG_ARM_ATAG_DTB_COMPAT=y, so it should
automatically pick up the amount of memory defined by U-Boot in the
ATAGS.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-04-03 10:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 17:51 [PATCH] arm: mvebu: Fix the memory size on the Mirabox Ryan Press
2013-03-29 18:04 ` Jason Cooper
2013-03-29 18:09   ` Ryan Press
2013-03-29 19:37     ` Ezequiel Garcia
2013-03-29 19:44       ` Jason Cooper
2013-03-30  3:30         ` Ryan Press
2013-03-30 19:20           ` Jason Cooper
2013-03-30 19:28             ` Jason Cooper
2013-03-30 19:40             ` Ryan Press
2013-03-30 20:12               ` Jason Cooper
2013-04-03 10:46       ` Thomas Petazzoni [this message]
2013-04-04 13:55       ` Gregory CLEMENT

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=20130403124608.5de971f1@skate \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).