From: Tom Rini <trini@kernel.crashing.org>
To: valvoline <valvoline@vrlteam.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: temp.c and cputable.c issues
Date: Wed, 14 Jan 2004 15:38:40 -0700 [thread overview]
Message-ID: <20040114223840.GD983@stop.crashing.org> (raw)
In-Reply-To: <20040114201153.GO2658@adapter.n0skillz.org>
On Wed, Jan 14, 2004 at 09:11:53PM +0100, valvoline wrote:
> On Wed, Jan 14, 2004 at 03:10:18PM -0700, Tom Rini wrote:
>
> > There are errata documents from Motorola that tell you not to use the
> > TAU on any 745x CPU. The omission of this flag is intentional.
>
> what's about this documents ?, if TAU is disabled what's the right way
> to fetch thermal infos for 745x based CPUs ?, any workaround or suggested
> url to start from ?
There are no workarounds or planned fixes for this errata (it varries
slightly in number from 7450/1 to 7455 to 7457 documents I think). All
errata can be gotten from Motorolas website.
7450:
http://e-www.motorola.com/webapp/sps/site/prod_summary.jsp?code=MPC7450_ARCHIVED
7451:
http://e-www.motorola.com/webapp/sps/site/prod_summary.jsp?code=MPC7451
7455:
http://e-www.motorola.com/webapp/sps/site/prod_summary.jsp?code=MPC7455
7457:
http://e-www.motorola.com/webapp/sps/site/prod_summary.jsp?code=MPC7457
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-14 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 19:39 temp.c and cputable.c issues valvoline
2004-01-14 22:10 ` Tom Rini
2004-01-14 20:11 ` valvoline
2004-01-14 22:38 ` Tom Rini [this message]
2004-01-15 8:19 ` Colin Leroy
2004-01-15 7:03 ` valvoline
2004-01-15 7:16 ` valvoline
2004-01-15 9:32 ` Colin Leroy
2004-01-16 7:02 ` valvoline
2004-01-16 10:21 ` Colin Leroy
2004-01-16 11:10 ` Geert Uytterhoeven
2004-01-16 11:26 ` Colin Leroy
2004-01-15 7:20 ` valvoline
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 9:38 Colin Leroy
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=20040114223840.GD983@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=valvoline@vrlteam.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).