linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Hurst <jhurst2@austin.rr.com>
To: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx Microcode patch
Date: Sun, 29 Jun 2003 02:27:32 -0500	[thread overview]
Message-ID: <3EFE94E4.90905@austin.rr.com> (raw)
In-Reply-To: 30C145E544071F4FB8B627789F7910BD328FF3@csy-exchange1.giat.intra


ARIBAUD Albert wrote:
> Hi,
>
> Is there a synthetic resource on microcode patches across 8xx models?
 > What patches exist, which models need it, what they do.
 > I am especially interested in the MPC855T (IMMR says mask version 0502),
 > and reading the Motorola web page I see nothing about it needing microcode.
>
> Thanks in advance
> --
> Albert.

On the MPC860 page (the MPC855T is a family member) at Motorola web site:
MPC860MC04  MPC860 Microcode Patch for Relocating I2C/SPI Parameters
(03/06/2002)  contains a pdf.  It says 0502 is the last mask needing
the microcode.

--
Jeff Hurst


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-29  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27 15:47 8xx Microcode patch ARIBAUD Albert
2003-06-29  7:27 ` Jeff Hurst [this message]
2003-06-29  8:53   ` Albert ARIBAUD

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=3EFE94E4.90905@austin.rr.com \
    --to=jhurst2@austin.rr.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).