From: Matt Porter <porter@cox.net>
To: Mark Hatle <fray@mvista.com>
Cc: Bret Indrelee <Bret.Indrelee@qlogic.com>,
Linux PPC Embedded mailing list
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Binary Compatibility of various flavors of PPC
Date: Mon, 14 Oct 2002 11:15:47 -0700 [thread overview]
Message-ID: <20021014111547.A11259@home.com> (raw)
In-Reply-To: <3DAAFB50.9090509@mvista.com>; from fray@mvista.com on Mon, Oct 14, 2002 at 12:13:52PM -0500
On Mon, Oct 14, 2002 at 12:13:52PM -0500, Mark Hatle wrote:
>
> Bret Indrelee wrote:
> > We are trying to wade our way through the various processor choices and
> > options available for PPC on Linux.
> >
> > One of our requirements is to be able to run the same binary image across
> > a range of systems. The image can not change just because the processor
> > does.
> >
> > We are currently looking at the 405GPX, 8250, 8245, and PowerQUIC III.
>
> (I am ONLY speaking of userspace! .. each system will require a custom kernel)
>
> The 7xx (as well as 74xx if you avoid altivec) and 82xx are all compatable in
> userspace. Those CPU families floating point units, the same cache line size
> and other commonalities.
>
> The 405 does not have an FPU.. If you enable the in kernel floating point
> emulator it will then be capable of running the same binaries as above.. but do
> to performance, personal preferance and other reasons I do not recommend running
> a non FPU machine with FPU emulation unless you need to.
Working 40x libraries have some errata fixups in them IIRC, so running
a complete classic PPC binary chain would have the possibility of
exhibiting problems.
> (Since we're on the topic) the PowerPC 403, and 8xx lines are binary compatable
> with each other. Similar to the 405 they lack an FPU, but they also use only
> half the cacheline size of the above CPUs. This (potentially) makes the libc
> incompatable, and many optimizations may not work as intended.
>
> There is still a question on wether or not the Book E stuff will be user space
> compatable with the current 7xx style binaries. I wouldn't hold my breath.. :P
Oh good, another chance to point out that Book E isn't a unifying standard.
The current IBM Book E implementation (PPC440) is binary compatible
with PPC405. Since 40x was a bastard hybrid of classic and Book E
PPC, the 440 looks like a superset as far as userspace instructions.
The Mot Book E implementation (e500) could be binary compatible
with classic PPCs (perhaps Kumar will speak up on the direction here)
except that it doesn't handle FP in a green book manner...well it's
a more versatile SIMD implementation anyway. One public mention of
some pertinent e500 characteristics is here:
http://gcc.gnu.org/ml/gcc/2002-07/msg01060.html
In theory, one could use kernel FP emulation on e500 when not using
SIMD instructions and run classic PPC binaries. In practice, this may
not be wise.
> If I was building a range of systems that required varying PowerPC CPUs with a
> common userspace I would stick to the 82xx/7xx/74xx families today.
I'd have to agree with that. Classic PPC core implementations currently
offer the broadest selection of userspace binary compatible processors.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-14 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 16:46 Binary Compatibility of various flavors of PPC Bret Indrelee
2002-10-14 16:55 ` Wolfgang Denk
2002-10-14 18:17 ` Bret Indrelee
2002-10-14 18:22 ` Wolfgang Denk
2002-10-14 17:13 ` Mark Hatle
2002-10-14 18:15 ` Matt Porter [this message]
2002-10-14 19:59 ` Kumar Gala
2002-10-14 20:29 ` Mark Hatle
2002-10-14 20:48 ` Wolfgang Denk
2002-10-14 20:54 ` Mark Hatle
2002-10-14 22:14 ` Magnus Damm
2002-10-14 21:37 ` Bret Indrelee
2002-10-14 22:26 ` Andrew May
[not found] <005AF3F9.C21188@qlogic.com>
2002-10-14 22:30 ` Jerry Van Baren
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=20021014111547.A11259@home.com \
--to=porter@cox.net \
--cc=Bret.Indrelee@qlogic.com \
--cc=fray@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.