From: "Jim Belesiu" <belesiu@panmed.com>
To: <ecos-discuss@cygnus.com>
Subject: Embedded PowerPC Differing Families
Date: Fri, 06 Nov 1998 22:26:00 -0000 [thread overview]
Message-ID: <000601be0a17$7c554080$1701a8c0@belesiu-home> (raw)
In-Reply-To: < 199811070017.TAA18139@hil-img-ims-4.compuserve.com >
For the MPC8xx series, the cores are the same with the processors differing
with the number and types of peripherals and I/O associated with the CPM
(Communications Processor Module).
For example, my current design uses the MPC823 (a very cool processor: video
controller, three serial channels, I2C, SPI, quad timers, real-time clock and
microcoded DSP filter blocks) but I've successfully used SW components from
'821 and '860 designs.
I am looking forward to plugging eCos into my board. I'm curious to see how
it does compared to my current commercial OS. I don't expect much trouble in
porting it.
Jim Belesiu / Sr. Engineer / Pangea Medical, Inc
Newberg, Oregon USA
>-----Original Message-----
>From: owner-ecos-discuss@cygnus.com
>[ mailto:owner-ecos-discuss@cygnus.com]On Behalf Of Kenneth Porter
>Sent: Friday, 06 November, 1998 01:17
>To: eCos Discuss
>Subject: Embedded PowerPC
>
>
>How different are the embedded PPC chips? For example, I'm considering
>the MPC850 for a new design. Would I be able to use the MPC860 eCos for
>that? What if I choose an MPC555, or an IBM MPC403?
>
>
>Kenneth Porter
>Kensington Laboratories, Inc.
> mailto:kenneth_porter@kensingtonlabs.com
> http://www.kensingtonlabs.com
>
>
>
>
>
prev parent reply other threads:[~1998-11-06 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-06 16:18 Embedded PowerPC Kenneth Porter
[not found] ` < 199811070017.TAA18139@hil-img-ims-4.compuserve.com >
1998-11-06 22:26 ` Jim Belesiu [this message]
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='000601be0a17$7c554080$1701a8c0@belesiu-home' \
--to=belesiu@panmed.com \
--cc=ecos-discuss@cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).