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 13:11:59 -0500 [thread overview]
Message-ID: <48FF6CEF.8050607@genesi-usa.com> (raw)
In-Reply-To: <EF781CC4-B321-4E6A-A376-ADDDC1BB2E7B@kernel.crashing.org>
Kumar Gala wrote:
>
> On Oct 22, 2008, at 9:19 AM, Matt Sealey wrote:
>
>>
>>
>> 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 :)
>
> The "XAEN" is specific to e600. e500 has its own ability to do 36-bit
> physical (not called XAEN).
You have to forgive me I was only half awake when I started :D
Yeah so I saw BookE and e500 stuff go past but nothing
specific for e600/XAEN. I mailed Becky and got no response.
I'm glad to know it's in there though, somewhere.
Just so it has been asked, do you know in a broad sense what
it would take to add the non-contiguous memory mapping
support? Doesn't ppc64 already have this?
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2008-10-22 18: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 [this message]
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=48FF6CEF.8050607@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.