From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: Starting the arch/powerpc merge
Date: Wed, 28 Sep 2005 10:05:14 +1000 [thread overview]
Message-ID: <1127865914.6102.0.camel@gaston> (raw)
In-Reply-To: <17209.817.732159.375607@cargo.ozlabs.ibm.com>
On Tue, 2005-09-27 at 18:30 +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > What about just dropping POWER3/4 support in 32bit mode?
>
> Yes... I'm getting very close to deciding to do that. In fact POWER3
> isn't too bad, since it still has BATs, but POWER4/PPC970 would be
> tricky.
>
> Does anyone on these lists have any major objections if we drop
> support for 32-bit kernels on POWER3 and POWER4/PPC970?
I've stopped supporting G5 on 32 bits kernel for some time now, I have
absolutely no problem just dropping the POWER4 support in 32 bits kernel
in the merged tree.
Ben.
next prev parent reply other threads:[~2005-09-28 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 0:25 Starting the arch/powerpc merge Paul Mackerras
2005-09-27 3:39 ` Kumar Gala
2005-09-27 5:38 ` Stephen Rothwell
2005-09-27 9:56 ` Paul Mackerras
2005-09-27 8:23 ` Christoph Hellwig
2005-09-27 8:30 ` Paul Mackerras
2005-09-27 9:16 ` Heikki Lindholm
2005-09-27 9:26 ` Pantelis Antoniou
2005-09-27 9:55 ` Paul Mackerras
2005-09-27 9:51 ` Pantelis Antoniou
2005-09-28 0:05 ` Benjamin Herrenschmidt [this message]
2005-09-29 7:20 ` Giuliano Pochini
2005-10-06 23:24 ` Paul Mackerras
2005-10-20 23:01 ` Paul Mackerras
2005-10-21 7:19 ` Giuliano Pochini
-- strict thread matches above, loose matches on Subject: below --
2005-09-27 15:43 Daniel Ostrow
2005-09-27 16:43 ` Christopher Friesen
2005-09-27 17:29 ` Daniel Ostrow
2005-09-28 0:07 ` 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=1127865914.6102.0.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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).