From: "Timothy A. Seufert" <tas@mindspring.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
<brad@turbolinux.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: powerbook doubles as a frying pan
Date: Tue, 30 Jan 2001 21:36:35 -0800 [thread overview]
Message-ID: <v04220800b69d5088a9c4@[10.0.0.42]> (raw)
In-Reply-To: <19341224043310.26390@mailhost.mipsys.com>
At 12:01 PM +0100 1/29/01, Benjamin Herrenschmidt wrote:
>Troy have some code that allow to read the temp from /proc. However, it
>looks like a lot of CPUs are so badly calibrated that the information
>returned is almost useless... Maybe that's not the case in CPUs used in
>portables, that's the case in some of the G4s used in dual G4s.
G3s generally have a useful temperature sensor, but you have to know
the correction formula specific to the die revision you're using.
The raw data is not good for much other than deltas (i.e. if the raw
value changes by 12 C, you know that it really did change by about 12
C, even if you don't know what the real starting and ending temps
were).
However, from what I've heard the G4 sensor is essentially useless.
On my own dual processor 500, a MacOS temperature readout utility
consistently tells me that one processor is 24 degC (or more) cooler
than the other. Both CPUs are the same die revision of course.
There is just no way for this to be correct; the CPUs are thermally
coupled by a nice thick chunk of aluminum (1" x 0.5" cross section at
least), due to the design of the heatsink. Both are getting good
contact (I checked).
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-31 5:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 0:27 powerbook doubles as a frying pan Brad Midgley
2001-01-29 11:01 ` Benjamin Herrenschmidt
2001-01-29 15:15 ` Michael Schmitz
2001-01-29 15:30 ` Chas Williams
2001-01-29 21:54 ` Troy Benjegerdes
2001-02-03 3:15 ` Dan Bethe
2001-01-31 5:36 ` Timothy A. Seufert [this message]
2001-02-03 3:03 ` Dan Bethe
2001-02-03 23:24 ` Timothy A. Seufert
2001-02-05 12:46 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 1:09 Iain Sandoe
2001-01-29 15:27 Iain Sandoe
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='v04220800b69d5088a9c4@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=benh@kernel.crashing.org \
--cc=brad@turbolinux.com \
--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 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).