From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Tue, 24 Oct 2006 07:38:32 +1000 [thread overview]
Message-ID: <1161639512.10524.485.camel@localhost.localdomain> (raw)
In-Reply-To: <453CD615.4050401@genesi-usa.com>
On Mon, 2006-10-23 at 16:47 +0200, Matt Sealey wrote:
> Curious question.
>
> What are you guys going to do when the PowerPC name is defunct?
It's not really, is it ? I don't care anyway, it will stay PowerPC in
linux of course :)
> Like, last month :)
>
> Power Architecture is where it is at. The trademark is even going to
> lapse
Who cares ? Besides, while PAPR says "Power architecture", the processor
architecture specification says PowerPC :)
> . It's a bit too late for the ppc->powerpc tree breakout now,
> but wouldn't it just confuse people to be using a "Power Architecture"
> processor or SoC of some type, using collections of definitions from
> the Power ISA 2.03 and have this "powerpc" thing pop up?
It's PowerPC ISA :)
> It confused me even before, because ppc and ppc64 have also been
> used to support real POWER (with a capital P, O, W, E and R) processors,
> and now these are lumped in with powerpc which is no better than
> ppc64 in these terms?
Historically, POWER means something else ... then with POWER3, POWER
processors became compatible with the PowerPC architecture, then IBM
played name changing game a couple of times and nobody knows what's up
anymore :)
> Just flexing my marketing exec muscles, see if they work, never done
> it before. Oh... *crack*.. that wasn't a good noise :]
AFAIK, the processor instruction set architecture is PowerPC an that
will not change.
Ben.
next prev parent reply other threads:[~2006-10-23 21:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 12:39 [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment Nicolas DET
2006-10-19 14:12 ` Jon Loeliger
2006-10-19 16:18 ` Linas Vepstas
2006-10-19 16:26 ` Grant Likely
2006-10-19 23:41 ` Benjamin Herrenschmidt
2006-10-20 5:55 ` Kumar Gala
2006-10-19 17:43 ` Olof Johansson
2006-10-20 6:06 ` Kumar Gala
2006-10-20 6:29 ` Sven Luther
2006-10-20 6:29 ` Benjamin Herrenschmidt
2006-10-20 8:12 ` Nicolas DET
2006-10-20 14:18 ` Kumar Gala
2006-10-20 14:24 ` Nicolas DET
2006-10-20 14:34 ` Kumar Gala
2006-10-21 23:25 ` Benjamin Herrenschmidt
2006-10-22 12:56 ` Nicolas DET
2006-10-23 6:36 ` Benjamin Herrenschmidt
2006-10-23 14:47 ` Matt Sealey
2006-10-23 15:52 ` Christoph Hellwig
2006-10-23 16:25 ` Matt Sealey
2006-10-23 16:40 ` Segher Boessenkool
2006-10-23 21:38 ` Benjamin Herrenschmidt [this message]
2006-10-23 22:57 ` Paul Mackerras
2006-10-24 15:44 ` Matt Sealey
2006-10-24 16:01 ` Becky Bruce
2006-10-24 23:01 ` Paul Mackerras
2006-10-25 14:44 ` Matt Sealey
2006-10-25 14:50 ` Kumar Gala
2006-10-25 14:56 ` Matt Sealey
2006-10-25 14:57 ` Grant Likely
2006-10-25 16:18 ` Matt Sealey
2006-10-25 17:08 ` Olof Johansson
2006-10-25 21:29 ` Paul Mackerras
2006-10-25 21:22 ` Paul Mackerras
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=1161639512.10524.485.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
/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).