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: Wed, 27 Feb 2013 09:33:53 +0100	[thread overview]
Message-ID: <20130227093353.03e63046@skate> (raw)
In-Reply-To: <20130227070333.GK17242@lunn.ch>

Dear Andrew Lunn,

On Wed, 27 Feb 2013 08:03:33 +0100, Andrew Lunn wrote:

> > 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?
> 
> Hi Thomas
> 
> My machine is an A0.

Hum, ok, so that doesn't explain the problem.

> I know you recently found some issue with windows. Could that explain
> something?

No, the issue with the window was only that devices can only access the
first 32 bits of the physical address space, so if there is a DRAM CS
configured with a base address higher than 4 GB, then devices shouldn't
configure a window to access this part of the DRAM, because it creates
two overlapping windows (both starting at base 0x0, since in the device
address decoding window registers, the base only has 32 bits, while it
has 35 bits for the SDRAM address decoding registers). And the issue
with window was that the devices were really not working at all. What
we're seeing with the OpenBlocks is some instability: sometimes it
boots, sometimes not.

We're going to discuss this issue further with PlatHome.

Thanks for reporting!

Best regards,

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

  reply	other threads:[~2013-02-27  8:33 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
2013-02-27  7:03                         ` Andrew Lunn
2013-02-27  8:33                           ` Thomas Petazzoni [this message]
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=20130227093353.03e63046@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