linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org, John Reiser <jreiser@BitWagon.com>
Subject: Re: 2GB address space limit on 32-bit PowerPC Macintosh
Date: Mon, 16 May 2005 11:04:50 -0400	[thread overview]
Message-ID: <c58d28ab50872f95d4c4a751d1768513@embeddededge.com> (raw)
In-Reply-To: <7d5cfed0ee1edade8050d2c4da94b3f1@freescale.com>


On May 16, 2005, at 2:21 AM, Kumar Gala wrote:

>
> On May 16, 2005, at 12:52 AM, Benjamin Herrenschmidt wrote:
>> Agreed. I'll fix PReP/CHRP/pmac & defconfig. Every embedded board
>>  vendor/maintainer will be responsible for fixing his/her boards 
>> support.
>
> Agreed.  We should probably send an email to linuxppc-embedded with a 
> more proper subject line to let people know.

There isn't any reason to break everything and force updates.  If 
someone wants
a 3G task size, then just configure that with the advanced options.   
All of that
grew out of the embedded board support, so just make PMac support it 
too.
In particular, I don't want to force the 8xx to a 3G task space, 
because it adds
more instructions to the TLB handlers, on a system that has never 
required
such application space.  We are 12 releases in 2.6, and it still seems 
like
a development kernel :-)  I think if someone wants this feature on a 
board
port that doesn't support it, then just fix that one board port instead 
of breaking
everything.

Thanks.

	-- Dan

  parent reply	other threads:[~2005-05-16 15:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 22:36 2GB address space limit on 32-bit PowerPC Macintosh John Reiser
2005-05-15 23:01 ` Benjamin Herrenschmidt
2005-05-15 23:29   ` Paul Mackerras
2005-05-15 23:34     ` Benjamin Herrenschmidt
2005-05-16  5:51       ` Kumar Gala
2005-05-16  5:52         ` Benjamin Herrenschmidt
2005-05-16  6:21           ` Kumar Gala
2005-05-16  6:22             ` Benjamin Herrenschmidt
2005-05-16 15:04             ` Dan Malek [this message]
2005-05-16 15:05               ` Benjamin Herrenschmidt
2005-05-16 15:52                 ` Dan Malek
2005-05-16 16:42                   ` Benjamin Herrenschmidt
2005-05-16 17:11                     ` Dan Malek
2005-05-17  0:54                       ` Benjamin Herrenschmidt
2005-05-16 18:00                     ` Mark A. Greer
2005-05-16 18:06                       ` Mark A. Greer
2005-05-16 20:31                         ` Dan Malek
2005-05-16 20:43                           ` Mark A. Greer
2005-05-16 21:02                             ` Dan Malek
2005-05-17  3:14                           ` Benjamin Herrenschmidt
2005-05-17  0:56                       ` Benjamin Herrenschmidt
2005-05-16 16:11                 ` Wolfgang Denk
2005-05-16 16:22                   ` Eugene Surovegin

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=c58d28ab50872f95d4c4a751d1768513@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=jreiser@BitWagon.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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).