From: Tom Rini <trini@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benjamin.herrenschmidt@wanadoo.fr>,
Cort Dougan <cort@fsmlabs.com>,
linuxppc-commit@fsmlabs.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: CPU features again
Date: Wed, 18 Apr 2001 09:39:41 -0700 [thread overview]
Message-ID: <20010418093941.C13403@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.05.10104181835150.5185-100000@callisto.of.borg>; from geert@linux-m68k.org on Wed, Apr 18, 2001 at 06:36:05PM +0200
On Wed, Apr 18, 2001 at 06:36:05PM +0200, Geert Uytterhoeven wrote:
> On Wed, 18 Apr 2001, Benjamin Herrenschmidt wrote:
> > Those feature bits have to be common accross the entire PPC range (and
> > possibly common with ppc64 too since ppc64 is supposed to run ppc32
> > binaries, except that ppc64 has 32 more bits to stuff it's own features
> > for 64 bits binaries).
>
> BTW, we don't take the sparc64/mips64 approach and create arch/ppc64/?
> Sparc64/mips64 run 32-bit binaries as well.
That's a 2.5 planned thing, I believe.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-18 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010417140515.A17204@ftsoj.fsmlabs.com>
2001-04-18 16:03 ` CPU features again Benjamin Herrenschmidt
2001-04-18 16:36 ` Geert Uytterhoeven
2001-04-18 16:39 ` Tom Rini [this message]
2001-04-18 16:47 ` Benjamin Herrenschmidt
2001-04-19 18:24 ` Peter Bergner
2001-04-22 3:03 ` Anton Blanchard
2001-04-18 17:55 ` Dan Malek
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=20010418093941.C13403@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=benjamin.herrenschmidt@wanadoo.fr \
--cc=cort@fsmlabs.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-commit@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.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).