public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] arm: mvebu: limit OpenBlocks AX3-4 to 1 GB of RAM
Date: Tue, 26 Feb 2013 16:20:23 +0100	[thread overview]
Message-ID: <20130226162023.3d7b2ffc@skate> (raw)
In-Reply-To: <20130107113411.GV3392@lunn.ch>

Dear Andrew Lunn,

On Mon, 7 Jan 2013 12:34:11 +0100, Andrew Lunn wrote:
> > Image is also with an initramfs + appended DTB. My boot command is:
> > 
> > tftp 1000000 192.168.0.14:uImage.armada-xp-openblocks-ax3-4; bootm
> > 
> > So I'm loading to a different address than you.
> 
> Hi Thomas
> 
> Uboot tells me:
> 
> DRAM:   3 GB
>        CS 0: base 0x00000000 size  1 GB
>        CS 2: base 0x40000000 size  1 GB
>        CS 3: base 0x80000000 size  1 GB
>        Addresses 14M - 0M are saved for the U-Boot usage.
> 
> 1000000 would be towards the beginning of this area reserved for uboot.
> 
> Could you try moving to somewhere outside of the first 14Mbytes and
> see if that helps.

Jumping back on this old topic of the OpenBlocks AX3 not being stable
with 3 GB of RAM for Gr?gory and me, but being stable for you. Could
you check which revision of the Armada XP you have? Is it A0 or B0?

I.e, check the message:

 SoC:   MV78460 B0

in U-Boot. Gr?gory and I are using OpenBlocks AX3 based on the A0
version of the silicon (so the message I copy/pasted above is *not*
from our OpenBlocks, but a different Armada XP board). However,
PlatHome has been shipping since some time B0 revisions. Maybe it could
explain the difference we're seeing?

Thanks,

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-02-26 15:20 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
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 [this message]
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=20130226162023.3d7b2ffc@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