From: "Mark A. Greer" <mgreer@mvista.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:00:43 -0700 [thread overview]
Message-ID: <4288DFCB.2080208@mvista.com> (raw)
In-Reply-To: <1116261725.5095.139.camel@gaston>
Benjamin Herrenschmidt wrote:
>
>series are by no mean stable. Embedded code has been rather frozen in
>the rock, I don't think it's much to ask from the appropriate maintainer
>to have a quick look at possibly upgrading their board support as well.
>
Seems reasonable to me.
>And it isn't a difficult change for most 6xx/7xx/7xxx based boards
>anyway.
>
From a quick grep, it looks like apus, gemini, k2, lopec, pplus, prep,
and prpmc800 are the offenders in the 6xx/7xx/74xx world. Does anyone
even care about the lopec and k2 anymore?
> What I'm worried about is that without some "pressure" (like
>breaking them), it will simply never be fixed...
>
Probably true...
Mark
next prev parent reply other threads:[~2005-05-16 18:00 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
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 [this message]
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=4288DFCB.2080208@mvista.com \
--to=mgreer@mvista.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 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.