From: Matt Sealey <matt@genesi-usa•com>
To: Paul Mackerras <paulus@samba•org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Wed, 25 Oct 2006 16:44:02 +0200 [thread overview]
Message-ID: <453F7832.2020305@genesi-usa.com> (raw)
In-Reply-To: <17726.39780.732843.150044@cargo.ozlabs.ibm.com>
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).
If a processor is not supported it was probably designed and
end-of-lined well before they made the original "Book" specs :D
Have you even looked at it? Even the dumb 'evolution' picture
on Power.org's site makes this quite, quite clear. Most of the
spec is identical, to the letter, over vast amounts of pages.
There are change bars in front of everything that changed and
those that have; it seems they are just lifted and reworked
from Freescale's AltiVec/SPE documentation, reworded in Book E
so you can have a Book E with AltiVec, or has it's own new
book (VLE, which is an IBM-ified copy of the e200 Core
Reference Manual Addendum)
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
Paul Mackerras wrote:
> Matt Sealey writes:
>
>> http://www.power.org/news/articles/new_brand/#isa
>>
>> I'm talking about the one they consolidated from all the different specs
>> Freescale, AMCC and IBM had about what makes a PowerPC processor. Since
>> POWER is part of it and it's all Power.org now.. they seem to have changed
>> the name.
>
> So, are you proposing we drop support for all the PowerPC processors
> that don't conform to the recently-published V2.03 ISA? You don't
> want 6xx, 7xx, 7xxx, 52xx, etc. supported any more? :) (joke :)
>
> Seriously, the v2.03 ISA covers only IBM's latest POWER processors
> (i.e. not POWER3, POWER4, or even POWER5), and Book E processors. We
> support a lot more than that.
>
> Paul.
next prev parent reply other threads:[~2006-10-25 14:44 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 [this message]
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=453F7832.2020305@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(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