From: David Edelsohn <dje@watson.ibm.com>
To: Ralph Blach <rcblach@raleigh.ibm.com>
Cc: Dan Malek <dan@mvista.com>,
linuxppc-dev@lists.linuxppc.org,
Holger Bettag <hobold@Informatik.Uni-Bremen.DE>,
Mark Salisbury <mbs@mc.com>,
"Timothy A. Seufert" <tas@mindspring.com>
Subject: Re: ppc LE questions (seeking help hand info pointers)
Date: Fri, 21 Sep 2001 14:58:23 -0400 [thread overview]
Message-ID: <200109211858.OAA22552@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Ralph Blach <rcblach@raleigh.ibm.com> of "Fri, 21 Sep 2001 13:01:49 EDT." <3BAB727D.C85E5CB@raleigh.ibm.com>
>>>>> Ralph Blach writes:
Ralph> Although my knowledge of powerpc is
Ralph> far from complete, I can tell everybody that from my experience that the
Ralph> Book E architecture is superior.
Ralph> I believe that Book E processor which have been announced by both
Ralph> Motorola and IBM will be VERY successful.
Let me clarify a point in my previous reply: the PowerPC Book E
changes to the PowerPC Book I UISA affect 64-bit PowerPC only. The 32-bit
subset of PowerPC Book E is compatible with the rest of the PowerPC
architecture family. IBM's PowerPC 440GP implements the 32-bit PowerPC
Book E architecture.
As I said in my original message, the supervisor and non-UISA
changes are very useful and have a lot of support from the embedded
PowerPC developer community. The IBM PowerPC 440GP and other 32-bit
PowerPC Book E chips implement the areas of agreement and compatibility
which create broad support for the PPC 440GP chip and the PowerPC
architecture. I am happy when the various chip implementations in the
PowerPC architecture family complement and reinforce each other.
David
P.S. The above comments are my own opinion and are not intended to
imply that they represent any company or organization.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-21 18:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 15:42 ppc LE questions (seeking help hand info pointers) Mark Salisbury
2001-09-20 15:58 ` Tom Rini
2001-09-20 16:07 ` Geert Uytterhoeven
2001-09-20 16:12 ` Tom Rini
2001-09-20 17:10 ` Brad Boyer
2001-09-20 18:32 ` Mark Salisbury
2001-09-20 19:29 ` Holger Bettag
2001-09-20 19:35 ` David Edelsohn
2001-09-20 20:19 ` Mark Salisbury
2001-09-21 1:46 ` Timothy A. Seufert
2001-09-21 3:54 ` Dan Malek
2001-09-21 7:24 ` Geert Uytterhoeven
2001-09-21 7:47 ` Dan Malek
2001-09-21 7:50 ` Geert Uytterhoeven
2001-09-21 8:19 ` Dan Malek
2001-09-21 17:01 ` Ralph Blach
2001-09-21 17:35 ` David Edelsohn
2001-09-21 18:58 ` David Edelsohn [this message]
2001-09-21 20:22 ` Dan Malek
2001-09-21 20:29 ` Benjamin Herrenschmidt
2001-09-21 20:42 ` Benjamin Herrenschmidt
2001-09-21 7:22 ` Geert Uytterhoeven
2001-09-21 9:26 ` keyb Giuliano Pochini
2001-09-21 10:38 ` ppc LE questions (seeking help hand info pointers) Ralph Blach
2001-09-20 20:01 ` Tony Mantler
2001-09-20 18:28 ` Mark Salisbury
2001-09-20 19:12 ` Tom Rini
2001-09-20 22:22 ` Dan Malek
2001-09-21 5:45 ` Troy Benjegerdes
2001-09-28 6:37 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2001-09-21 5:28 Albert D. Cahalan
2001-09-21 6:10 ` Dan Malek
2001-09-21 10:59 ` Ralph Blach
2001-09-21 18:48 Albert D. Cahalan
2001-09-22 0:22 ` Timothy A. Seufert
2001-09-22 20:06 ` Albert D. Cahalan
2001-09-24 17:10 ` Mark Salisbury
2001-09-22 14:23 ` Holger Bettag
2001-09-22 20:26 ` Timothy A. Seufert
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=200109211858.OAA22552@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=dan@mvista.com \
--cc=hobold@Informatik.Uni-Bremen.DE \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mbs@mc.com \
--cc=rcblach@raleigh.ibm.com \
--cc=tas@mindspring.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).