All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: lm75 compute
Date: Thu, 19 May 2005 06:24:22 +0000	[thread overview]
Message-ID: <20031028225159.7c65c941.khali@linux-fr.org> (raw)
In-Reply-To: <3F9C884D.93E32BDA@paradyne.com>


> ----------------------------
> revision 1.77
> date: 2002/11/08 12:06:53;  author: khali;  state: Exp;  lines: +119
> -94(Khali) Add section for lm75 in sensors.conf.eg
>         Complete the lm78 section in sensors.conf.eg
> ----------------------------

BTW, note that the change was almost one year old and this is the first
person complaining AFAIK. It might be that the LM75 is so old that it's
not used anymore. But it could as well mean that I am not the only one
needing that scaling.

> I wouldn't have changed an existing configuration, but it happens that
> the LM75 had no section at that time, so I simply made one based on
> the only board I had with a LM75 on it - an Asus TX97-E.
> 
> Now I admit that what's said on ticket 1423 is plain right. The LM75
> cannot be configured in any way, so I hardly can understand how the
> reported temperature could require scaling. On the other hand, which
> chip would it be on my TX97-E, if not a LM75? There's also a LM78 on
> that board, so it sound rather logical that the other monitoring chip
> would be from National Semiconductor too.
> 
> I'll open the case and take a look, in case I'm able to see the
> monitoring chips.

I did that and could see the chips. There *is* a real LM75 right under
the CPU socket. My guess is that the LM75 is not designed to accurately
measure a CPU's temperature, so Asus placed it in such a location that
multiplying the original value by two would give a correct approximation
of the CPU's temperature. This means that I should not trust the
reported value too much - although it *is* related to how much heat the
CPU generates, whatever the actual value is.

Whatever, the LM75's value *needs* to be scaled by 2 on my system to
match what the BIOS screen reports. This is why I changed the
configuration file the way I did. Sorry for the trouble, had I read the
LM75 datasheet before doing that, I'd have understand it wasn't making
sense at all.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

  reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 lm75 compute Mark Studebaker
2005-05-19  6:24 ` Jean Delvare [this message]
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Denis Leroy
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Mark Studebaker

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=20031028225159.7c65c941.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.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.