linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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:52:38 -0400	[thread overview]
Message-ID: <fe487e7a8a89e65cfefd4f5dd39a982d@embeddededge.com> (raw)
In-Reply-To: <1116255938.5095.133.camel@gaston>


On May 16, 2005, at 11:05 AM, Benjamin Herrenschmidt wrote:

> I suppose it would add about ... 1 instruction :)

It's a little more than that :-)

> But I agree that we don't abolutely _need_ to break everybody. Maybe a
> better compromise would be to have the default beeing per CPU family ?
> 6xx/7xx/7xxx could default to 3G and 8xx stay at 2G...

That's still going to break nearly every embedded board.  My point is
that is all configurable for each individual board, so if you want that 
to
be the default for a board, then just update the defconfig for that 
board.
The PMac is only one "board" out of many we support, and I don't think
it should be considered the default or generic configuration any more
than any other board.  The PMac is the easiest to update because it's
a single configuration file.  If you want that to have a 3G default task
space, then update that one configuration file.  As we have time we
will update all of the others, and when we get to the point where most
boards are of that configuration, we'll make it the default and the
minority of boards become the special cases.

Thanks.


	-- Dan

  reply	other threads:[~2005-05-16 15:52 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
2005-05-16 15:05               ` Benjamin Herrenschmidt
2005-05-16 15:52                 ` Dan Malek [this message]
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=fe487e7a8a89e65cfefd4f5dd39a982d@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=benh@kernel.crashing.org \
    --cc=jreiser@BitWagon.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).