From: forest@alittletooquiet.net (Forest Bond)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] VT1211 sensors.conf: other CPUs?
Date: Thu, 08 Feb 2007 19:49:10 +0000 [thread overview]
Message-ID: <20070208194910.GE18906@storm.local.network> (raw)
Hello,
There appears to be some fresh new material with regard to the VT1211 in
sensors.conf now that this chip is officially supported. I'll quote from
sensors.conf:
--------------------------------------------------------------------------------
# The temperature calculations are of the form
# compute tempX (@ - Offset) / Gain, (@ * Gain) + Offset
#
# The following are the gain and offset values as recommended by VIA
# Diode Type Gain Offset
# ---------- ---- ------
# Intel CPU 0.9528 88.638
# 0.9686 65.000 *)
# VIA C3 Ezra 0.9528 83.869
# VIA C3 Ezra-T 0.9528 73.869
#
# *) These are the values from the previous sensors.conf. I don't know
# where they came from or how they got derived.
#
# The VT1211 internal temperature (temp2) is scaled by the driver
# and doesn't need to be adjusted here.
compute temp1 (@ - 73.869) / 0.9528, (@ * 0.9528) + 73.869
--------------------------------------------------------------------------------
So, it appears that the gain factor is a property of the VT1211, and that the
offset is a property of the CPU. On to my question...
What is the preferred method for adding support for other CPUs? The Ezra cores
aren't shipping anymore, so most EPIA boards (i.e., most boards using this Super
I/O chip) have Nehemiah cores of one kind or another. It would seem there are
two options:
1. Get the appropriate CPU documentation from VIA, if available.
2. Try to measure the die temperature by approximation from some surface
temperature. Take some data points, and estimate the offset.
3. Really wing it, and take a trial-and-error approach, nudging the offset
iteratively until the resulting temperature results look reasonable.
I am not inclined to belive that the documentation mentioned in (1) is widely
available, or that it exists at all. Is (2) feasible? (3) is obviously not a
great way to go, but if anyone has suggestions for increasing accuracy I'm all
ears.
Any assistance would be appreciated; I have access to a variety of boards
utilizing this chip. I would be more than happy to contribute information I am
able to pick up.
thanks,
Forest
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070208/3887f90f/attachment.bin
next reply other threads:[~2007-02-08 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 19:49 Forest Bond [this message]
2007-02-09 17:06 ` [lm-sensors] VT1211 sensors.conf: other CPUs? Juerg Haefliger
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=20070208194910.GE18906@storm.local.network \
--to=forest@alittletooquiet.net \
--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.