From: Matt Sealey <matt@genesi-usa•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Mon, 23 Oct 2006 16:47:49 +0200 [thread overview]
Message-ID: <453CD615.4050401@genesi-usa.com> (raw)
In-Reply-To: <1161585371.10524.444.camel@localhost.localdomain>
Curious question.
What are you guys going to do when the PowerPC name is defunct?
Like, last month :)
Power Architecture is where it is at. The trademark is even going to
lapse. 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 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?
Just flexing my marketing exec muscles, see if they work, never done
it before. Oh... *crack*.. that wasn't a good noise :]
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
Benjamin Herrenschmidt wrote:
> Ok, here's a batch of comments. They go on top of the comments I sent
> about your device-tree, which you might want to make public.
>
> Also note that the size of the patch is partially due to stale ##
> and .orig files :)
>
> In general, one big thing is: Don't bother with re-using the arch/ppc
> code, API, .h etc... There is not enough re-use there to justify it (FEC
> driver is new, serial can easily be changed, as for USB).
>
> * /proc/ppc64/rtas changes: we need to continue that discussion
> separately and ask for paulus point of view. I prefer /proc/powerpc
> personally with a /proc/ppc64->/proc/powerpc symlink on 64 bits machines
> only.
>
[snip]
next prev parent reply other threads:[~2006-10-23 14:47 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 [this message]
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
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=453CD615.4050401@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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