public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa•com>
To: Becky Bruce <becky.bruce@freescale•com>
Cc: "linuxppc-dev list" <linuxppc-dev@ozlabs•org>,
	Odeyé <regis.odeye@kontron•com>
Subject: Re: Extended Addressing Mode
Date: Wed, 22 Oct 2008 17:18:48 -0500	[thread overview]
Message-ID: <48FFA6C8.9020606@genesi-usa.com> (raw)
In-Reply-To: <20EAA623-DD71-46E0-A47C-658DCEA7E607@freescale.com>



Becky Bruce wrote:
> 
> On Oct 22, 2008, at 1:11 PM, Matt Sealey wrote:
> 
>> 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.
> 
> Huh?  I have one mail from you, on Sep 1, to which I responded on Sep 
> 2.  Was there another mail I missed, or did you not see my response?  
> Freescale's mail server is unreliable, and since I'm not in the habit of 
> ignoring emails, feel free to nag me anytime if you send me something 
> and don't get a response.

Between Freescale's mail server and the trouble we're having 
with Google right now (along with thousands of others), I am 
NOT surprised it got lost somewhere along the way.

I wasn't bitching :)

>> 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?
> 
> PPC64 has SPARSEMEM support, IIRC. It's non-trivial to add for 32-bit, 
> although I haven't scoped it out in any detail.

Okay, non-trivial was pretty much what I was looking for, I 
was just trying to weigh up how much effort is required..

If you actually scope it out in any detail or someone has some 
10% time and decides this would be an awesome project, give me 
a nudge? My MPC8641D is itching to actually do something 
besides build packages. Actually having 8GB of memory would 
REALLY help run SUSE Build Service :]

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

  reply	other threads:[~2008-10-22 22:18 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 [this message]
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=48FFA6C8.9020606@genesi-usa.com \
    --to=matt@genesi-usa$(echo .)com \
    --cc=becky.bruce@freescale$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=regis.odeye@kontron$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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