linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Matt Sealey" <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Wed, 25 Oct 2006 08:57:19 -0600	[thread overview]
Message-ID: <528646bc0610250757i3754fc96uccddd8109f3a712@mail.gmail.com> (raw)
In-Reply-To: <453F7832.2020305@genesi-usa.com>

On 10/25/06, Matt Sealey <matt@genesi-usa.com> wrote:
> It supports the original processors, G3, G4 etc. as well. Maybe not
> the 601? I'm not sure. All the PowerPC ISA Books are in there and
> information only seems to have been ADDED (or moved to another
> book or been given a new book).

Why are we still talking about this?  None of it matters.

Who cares if the new ISA spec incorporates all of the old ones?  The
old specs cannot be unpublished.  powerpc is a sufficient name for
kernel source purposes and it will continue to have meaning in the
minds of developers.  Marketing glossies can (and do) use the name de
jour, but we don't have to.

As a side note; The move from ppc/ppc64->powerpc was a *technical*
decision, not a marketing one.  It was done so there would be only one
code base.  The choice of arch/powerpc was almost arbitrary.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  parent reply	other threads:[~2006-10-25 14:57 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
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 [this message]
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=528646bc0610250757i3754fc96uccddd8109f3a712@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    --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).