linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ralph Blach <rcblach@raleigh.ibm.com>
To: Dan Malek <dan@mvista.com>,
	Embedded Linux list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: New Linux PowerPC development
Date: Wed, 25 Jul 2001 13:14:55 -0400	[thread overview]
Message-ID: <3B5EFE8F.CFB340A4@raleigh.ibm.com> (raw)
In-Reply-To: 3B5DAFC9.414B4788@mvista.com

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

Dan,

You forgot to mention the internal full duplex PLB on the 405.  ON the
405GP,
the Ethernet, PCI, EBC and memory are connected with a full duplex PLB
64 bit bus.

Its not a performance slouch either.

Chip
Dan Malek wrote:
>
> Cindy Peters wrote:
>
> > The MPC823, however, does not have an IDE or PCI interface for a hard disk.
>
> Sure it does.  Just use the PCMCIA.
>
> > We feel we would have to design an interface into an FPGA.
>
> This is also a solution many people use.  Lots less expensive and
> less complex than a PCI adapter.
>
> > .... It doesn't
> > support 100BaseT either.
>
> So, the 832 loses here :-).
>
> > ..... We are also looking at using either the
> > MPC8260/MPC8265 or the IBM 405GP.
>
> Wow.  The 823, 405, 8260 span a huge range in performance and features
> (and price).  You need to consider some other requirements to make this
> decision.  If the 823 would be enough performance, you can step up to
> the 860(D/T/P) and get more performance.  Depending upon the application,
> the 860P can be higher performance than the 405 because it will offload
> the integrated peripherals to the CPM.  The highest performance of the
> bunch is the 82xx, which also includes hardware floating point, if that
> is important.
>
> > .... I would like some feedback from people that have experience in using
> > these processors with Linux and what recommendations they have.
>
> I've used them all, and they all have advantages and disadvantages.
> You didn't list many requirements that would clearly show one is better
> suited for your application.  Based on what you said, and past experience
> with the 823, I would choose something from the 855/860 family.
>
>         -- Dan
>

[-- Attachment #2: Card for Ralph Blach --]
[-- Type: text/x-vcard, Size: 247 bytes --]

begin:vcard
n:Blach;Ralph
tel;work:919-543-1207
x-mozilla-html:TRUE
url:www.ibm.com
org:IBM MicroElectronics
adr:;;3039 Cornwallis		;RTP;NC;27709;USA
version:2.1
email;internet:rcblach@raleigh.ibm.com
x-mozilla-cpt:;15936
fn:Ralph Blach
end:vcard

  reply	other threads:[~2001-07-25 17:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 14:56 New Linux PowerPC development Cindy Peters
2001-07-24 15:26 ` AW: " Stefan Roese
2001-07-24 15:35   ` David Updegraff
2001-07-24 15:44 ` Grant Erickson
2001-07-24 17:26 ` Dan Malek
2001-07-25 17:14   ` Ralph Blach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-31 21:39 Cindy Peters
2001-07-31 21:52 ` Grant Erickson
2001-07-31 23:32   ` Matthew Locke
2001-07-31 23:41     ` Cort Dougan
2001-07-31 23:56       ` Mark Hatle
2001-08-01  3:09         ` Cort Dougan
2001-07-31 23:56       ` Tom Rini
2001-07-31 23:54   ` Mark Hatle
2001-07-31 23:55 ` Matthew Locke
2001-08-01  4:22 James F Dougherty

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=3B5EFE8F.CFB340A4@raleigh.ibm.com \
    --to=rcblach@raleigh.ibm.com \
    --cc=dan@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 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).