All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, "Régis Odeyé" <regis.odeye@kontron.com>
Subject: Re: Extended Addressing Mode
Date: Wed, 22 Oct 2008 09:22:59 -0500	[thread overview]
Message-ID: <48FF3743.1000007@genesi-usa.com> (raw)
In-Reply-To: <DC24FCF5-F410-47AB-8FC0-592EA0906568@kernel.crashing.org>



Kumar Gala wrote:
> 
> 
> Your bigger issue is if you can setup the DDR controller for the hole 
> you want.

I just remembered;;

~~
The CCSR window always takes precedence over all local access 
windows. However, the CCSR window must not overlap an LAW that 
maps to the DDR controller. Otherwise, undefined behavior occurs.
~~

So, it's not really possible to map 4GB of RAM in the lower 
32-bit area, without interacting badly with the CCSR. This 
means you're forced to select a 2GB LAW for DDR, then leave 
2GB free, then map the rest above.. using more than 2Gb 
therefore absolutely requires non-contiguous memory..?

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

  parent reply	other threads:[~2008-10-22 14:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  8:59 Extended Addressing Mode Régis Odeyé
2008-10-22 12:31 ` Kumar Gala
2008-10-22 12:59   ` Régis Odeyé
2008-10-22 13:08     ` Kumar Gala
2008-10-22 13:40       ` Régis Odeyé
2008-10-22 13:42       ` Matt Sealey
2008-10-22 14:06         ` Kumar Gala
2008-10-22 14:19           ` Matt Sealey
2008-10-22 14:58             ` Kumar Gala
2008-10-22 18:11               ` Matt Sealey
2008-10-22 19:59                 ` Becky Bruce
2008-10-22 22:18                   ` Matt Sealey
2008-10-22 14:22           ` Matt Sealey [this message]
2008-10-22 14:59             ` Kumar Gala
2008-10-22 18:25               ` Matt Sealey
2008-10-22 14:18         ` Régis Odeyé
2008-10-22 22:11       ` Benjamin Herrenschmidt
2008-10-22 22:21         ` Matt Sealey
2008-10-22 22:48           ` Benjamin Herrenschmidt

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=48FF3743.1000007@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=regis.odeye@kontron.com \
    /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.