From: hendrik <hendrik.vastech@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC8548 CPU v2 errata
Date: Tue, 17 Feb 2009 09:29:41 +0200 [thread overview]
Message-ID: <499A6765.2040005@gmail.com> (raw)
In-Reply-To: <49998F3C.4030304@tqs.de>
Jens Gehrlein wrote:
> Hi hendrik,
>
> hendrik schrieb:
>> Hi all
>>
>> could someone pls point me to where i can find documentation
>> regarding changes and the implications there of between die Freescale
>> mpc8548 v1 and v2 silicone CPUs. I have searched Freescales website
>> but only turned up errata concerning the reference manual:
>> Errata to MPC8548E PowerQUICC? III Integrated Host Processor Family
>> Reference Manual, Rev. 2
>
> There is also an errata sheet "MPC8458ECE Rev. 2" for the processor.
> See Tab "Documentation" of MPC8548E.
> On page 2 you will find a table of errata considering CPU 1.1 to 2.1
>
> Kind regards,
> Jens
>
Thank you Jens, I found "MPC8458ECE Rev. 2" but can not find a page 2 or
errata considering CPU 1.1 to 2.1 is there another link to the document?
thanks hendrik
next prev parent reply other threads:[~2009-02-17 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 13:56 [U-Boot] MPC8548 CPU v2 errata hendrik
2009-02-16 16:07 ` Jens Gehrlein
2009-02-17 7:29 ` hendrik [this message]
2009-02-17 8:23 ` Jens Gehrlein
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=499A6765.2040005@gmail.com \
--to=hendrik.vastech@gmail.com \
--cc=u-boot@lists.denx.de \
/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