linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Thu, 23 Oct 2008 09:11:46 +1100	[thread overview]
Message-ID: <1224713506.7654.353.camel@pasglop> (raw)
In-Reply-To: <88C8EDEB-C9A5-4876-AF7D-55CBABBE111D@kernel.crashing.org>

On Wed, 2008-10-22 at 08:08 -0500, Kumar Gala wrote:
> > We are developing a board based on Freescale 8641D which can get
> 4GB  
> > of ram. So I need 4GB+IOs (~1GB) of physical addressing space.
> > My plan is to put a part of this ram above of 4GB to keep accesses  
> > to the IOs below the 4GB limit. It means non-contiguous ram  
> > addressing and XAEN features to be working.

Why would you put the IOs below the 4G point ? It's actually easier
to have the IOs up above, like a lot of 4xx do.

Cheers,
Ben.

  parent reply	other threads:[~2008-10-22 22:12 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
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 [this message]
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=1224713506.7654.353.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --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 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).