From: Dan Malek <dan@mvista.com>
To: Elan Feingold <elan@nxnetworks.com>
Cc: "Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC8255 vs MPC8260?
Date: Fri, 10 Aug 2001 23:50:00 -0400 [thread overview]
Message-ID: <3B74AB68.DEA5B56E@mvista.com> (raw)
In-Reply-To: NDBBLJKOJGKDOFBHNPGEKEGMCEAA.elan@nxnetworks.com
Elan Feingold wrote:
> We're going to be using an MPC8255 processor, and I know there are a few
> differences between that CPU and the 8260 (e.g. less clock speed, less SCCs,
> etc.).
I haven't noticed any differences that would affect Linux.
> Has anyone run Linux/PPC on an 8255?
no reports.
> What needed to change from the standard 8260 port?
Just don't configure the devices that don't exist.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-08-11 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 21:22 MPC8255 vs MPC8260? Elan Feingold
2001-08-10 8:57 ` Michael Fischer
2001-08-11 3:50 ` Dan Malek [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=3B74AB68.DEA5B56E@mvista.com \
--to=dan@mvista.com \
--cc=elan@nxnetworks.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).