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:19:49 -0500 [thread overview]
Message-ID: <48FF3685.5020504@genesi-usa.com> (raw)
In-Reply-To: <DC24FCF5-F410-47AB-8FC0-592EA0906568@kernel.crashing.org>
Kumar Gala wrote:
>
> On Oct 22, 2008, at 8:42 AM, Matt Sealey wrote:
>> So to confirm, XAEN support through Becky's patches does support the
>> MPC8641D/e600 cores?
>
> Yes, its the only part that has XAEN.
Okay I saw a lot of e500/BookE support go past but nothing
specific :)
>> NOT supported because of the way the LAWs work, and also the alignment
>> of the LAWs means it is not fine enough granularity to map between 2GB
>> and 4GB into a window (you can have 2GB or 4GB but not some more
>> arbitrary value?)
>
> You can overlap LAWs because they have priority encoding. The lower the
> LAW # the higher the priority.
Hmm :)
> Your bigger issue is if you can setup the DDR controller for the hole
> you want.
Hmmmmm :)
Okay good to know. I'll go back to reading the docs.
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2008-10-22 14:20 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 [this message]
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
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=48FF3685.5020504@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.