From: Wolfgang Denk <wd@denx.de>
To: Nick Barendt <nbarendt@vxitech.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200 Rev. B
Date: Mon, 11 Jul 2005 21:46:31 +0200 [thread overview]
Message-ID: <20050711194631.C30EB3539FE@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 11 Jul 2005 13:41:26 EDT." <42D2AF46.9000200@vxitech.com>
In message <42D2AF46.9000200@vxitech.com> you wrote:
>
> I can confirm that there are engineering samples of at least the first
> mask set of the Rev. B part floating around. A friend sent me one:
...
> We have had very limited success with the Rev B engineering part,
We, too, have some problems with hardware which uses the currently
available negineering samples. It's not completely clear if these are
board or processor or software issues yet.
> We do know that there are still errata on the first mask rev and that a
> second mask rev is in process.
>
> Anyone else have anything to report?
If you got samples, you should also have access to the updated errata
sheet (MPC5200B_Customer_Info_addendum_errata). Read it. Also note
that you have to use BAPI v2.2 with Rev. B processors.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Every program has at least one bug and can be shortened by at least
one instruction -- from which, by induction, one can deduce that
every program can be reduced to one instruction which doesn't work.
next prev parent reply other threads:[~2005-07-11 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 15:39 MPC5200 Rev. B mgberry
2005-07-11 16:43 ` Eric N. Johnson (ACD)
2005-07-11 17:41 ` Nick Barendt
2005-07-11 19:46 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-11 18:13 mgberry
2005-07-12 13:25 Matt_Berry
2005-07-12 20:37 ` Wolfgang Denk
2005-07-13 14:30 Matt_Berry
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=20050711194631.C30EB3539FE@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=nbarendt@vxitech.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 NNTP newsgroup(s).