From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 15:52:00 +1000 [thread overview]
Message-ID: <1116222720.5095.86.camel@gaston> (raw)
In-Reply-To: <5833cd030098e5fc4600f691cab4f36c@freescale.com>
> >
> > We need to fix that too :) Though I suppose we can just switch that to
> > page tables, I don't really see the point of using a BAT here...
>
> Are the embedded board ports broken because of similar
> io_block_mapping() calls or for some other reason?
Mostly because of the above, though some embedded ports may do even more
horrible things for what i know :) The problem with io_block_mapping()
is that 1) it lets you put those BARs or mappings where you want, and 2)
you end up with plenty of code hard-coding this virtual address here or
there that need to be fixed.
> I'm in agreement that we should bump TASK_SIZE to 3GB and fix things,
> how about after 2.6.12 is out?
Agreed. I'll fix PReP/CHRP/pmac & defconfig. Every embedded board
vendor/maintainer will be responsible for fixing his/her boards support.
Ben.
next prev parent reply other threads:[~2005-05-16 5:54 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 [this message]
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
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=1116222720.5095.86.camel@gaston \
--to=benh@kernel.crashing.org \
--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).