All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] RE: vt8231.c
Date: Tue, 15 Nov 2005 08:33:52 +0000	[thread overview]
Message-ID: <20051115081327.4b3437b4.khali@linux-fr.org> (raw)
In-Reply-To: <20051102092453.47B1712E9E@bluewhale.planbit.co.uk>

Hi Roger,

Once again, sorry for the delay... :(

> > temp3 is a bit special, it is diode-based. The conversion which is
> > currently done in userspace should be moved into the driver, so that the
> > exported value is a temperature rather than a random register value.
> > Other temps are thermistor based, a part of the conversion has to be
> > moved into the driver so that we export the voltage value at the chip
> > pin. The thermistor bridge computation (voltag -> temperature) belongs
> > to userspace because different thermistors can be used on different
> > motherboards. The same is done for the PC87366 temp4-6 already.
> 
> We know what the datasheet and porting guide say about the temperatures, but
> I am not sure that this matches reality.  On my VIA EPIA 500 motherboard,
> the CPU is a VIA EPIA 5000 and not an Intel CPU.  I don't doubt that the
> sensor scale is correct for an Intel CPU, but the VIA EPIA CPU is different.
> If I use the scaling values in the porting guide then my temperatures are
> over 30C off.
> 
> For reference, 
> 	VIA's equation:  REG = TEMP * 0.9686 + 65
> 	My EPIA Mobo:    REG = TEMP * 0.7809 + 45

Good point. Do these constant have any kind of physical meaning? Is the
information publicly available? How did you come up with the correct
one for your VIA CPU?

What would the formula required for VIA CPUs look like if the Intel one
was integrated into the driver as I first proposed?

> We can put the VIA official Intel scaling into the driver, but this would be
> very misleading as the VT8231 is used on the VIA EPIA platform which is in
> widespread use, and all users of that board would therefore need to know
> that additional scaling was required.  If they didn't then they would be
> panicking when they see the CPU temperature (since the motherboard is only
> passively cooled).

Well, whatever we do, the VIA CPU users will have an incorrect reading
at first and will have to edit some lines in their configuration file
to get the proper reading. So this point doesn't really weight in
either direction. All it really means is that we will have to improve
the vt8231's sensors.conf.eg section to make the point clear.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2005-11-15  8:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 10:25 [lm-sensors] RE: vt8231.c Roger Lucas
2005-11-02 14:24 ` Jean Delvare
2005-11-02 15:17 ` Roger Lucas
2005-11-02 19:47 ` Knut Petersen
2005-11-02 20:15 ` Roger Lucas
2005-11-02 20:26 ` Jean Delvare
2005-11-02 21:50 ` Grant Coady
2005-11-02 21:56 ` Jean Delvare
2005-11-03  0:28 ` Roger Lucas
2005-11-03  4:26 ` Mark M. Hoffman
2005-11-03  6:11 ` Grant Coady
2005-11-06 17:00 ` Jean Delvare
2005-11-06 20:22 ` Roger Lucas
2005-11-07 10:37 ` Jean Delvare
2005-11-07 20:56 ` Roger Lucas
2005-11-09 13:03 ` Jean Delvare
2005-11-09 15:43 ` Roger Lucas
2005-11-15  8:33 ` Jean Delvare [this message]
2005-11-15 12:14 ` Roger Lucas
2005-11-15 13:15 ` Jean Delvare
2005-11-15 13:46 ` Roger Lucas
2005-11-15 20:17 ` Jean Delvare

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=20051115081327.4b3437b4.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.