From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Intel Core voltage monitoring
Date: Mon, 10 Dec 2007 14:44:12 +0000 [thread overview]
Message-ID: <20071210154412.7cc4e04f@hyperion.delvare> (raw)
In-Reply-To: <475BDA45.70400@googlemail.com>
Hi Rudolf,
On Mon, 10 Dec 2007 14:43:13 +0100, Rudolf Marek wrote:
> Hi Peter,
>
> IMHO the CPU-Z reads the VID code from CPU, so the voltage is not the real
> voltage, but the voltage that the CPU wants (not what it is actually getting).
>
> The driver could be extended to show the voltage, but that would not be a real
> voltage, but just voltage it wants... Don't know if it is benefit for user?
>
> What others think?
Well, that's what other hardware monitoring drivers export as cpu0_vid.
If you can read the value from the CPU directly, that would be
interesting, as this means that we can get the value even if the VID
lines aren't (properly) wired to the hardware monitoring chip. So, yes,
I'd say it's worth exporting from the coretemp driver if that can be
done easily and reliably.
Thanks,
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-12-10 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 12:06 [lm-sensors] Intel Core voltage monitoring Peter Ganzhorn
2007-12-10 13:43 ` Rudolf Marek
2007-12-10 14:44 ` Jean Delvare [this message]
2007-12-10 14:50 ` Jean Delvare
2007-12-10 15:01 ` Jean Delvare
2007-12-10 18:12 ` Peter Ganzhorn
2007-12-10 18:22 ` Jean Delvare
2007-12-12 6:39 ` linux
2007-12-12 11:17 ` Jean Delvare
2007-12-12 12:05 ` Peter Ganzhorn
2007-12-12 12:07 ` linux
2007-12-12 12:22 ` Jean Delvare
2007-12-12 12:39 ` 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=20071210154412.7cc4e04f@hyperion.delvare \
--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.