From: Magnus Damm <damm@kieraypc01.p.y.ki.era.ericsson.se>
To: Heinz Blaettner <heinz@bintec.de>
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: MPC8xx: wrong zimage_start
Date: Thu, 03 Jun 1999 11:22:58 +0200 [thread overview]
Message-ID: <37564972.5D564597@switchboard.ericsson.se> (raw)
In-Reply-To: XFMail.990602185116.heinz@bintec.de
> Hi Magnus
Hi there!
> Please give me a hint where to find the errata sheets ?.
You can find the 860 errata at motorolas website:
http://www.mot.com/netcomm/aesop/mpc8XX/860/860err.pdf
It contains a 860T specific part.
When I got my 860T didn't this errata contain any 860T specific
information at all.
> What problems about the 860T ? Because we choose that device :-(
First of all, the B revision contains the serious bug that makes it
impossible to use the
fec and the cpm at the same time. great.
They don't mention the B revision in that errata. My FADS860T had that
chip when I got it.
I've got a B3 and that one still contains the CPU7 bug that makes
datacache corruption
when writing to sprs.
I've got a workaround from Dan that I've applied to my embedded-2.2.5
head.S.
The workaround works fine, now I'm stuck with some minor fec.c problem.
Hope this helps! /
Magnus
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-06-03 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-02 12:06 MPC8xx: wrong zimage_start Wolfgang Denk
1999-06-02 13:49 ` Magnus Damm
1999-06-02 16:51 ` Heinz Blaettner
1999-06-03 9:22 ` Magnus Damm [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-02 15:06 kd
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=37564972.5D564597@switchboard.ericsson.se \
--to=damm@kieraypc01.p.y.ki.era.ericsson.se \
--cc=heinz@bintec.de \
--cc=linuxppc-dev@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.