From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Gigabyte GA-P35-DS3P - VID Zero value
Date: Tue, 20 Oct 2009 11:48:48 +0000 [thread overview]
Message-ID: <20091020134848.2c3188bc@hyperion.delvare> (raw)
In-Reply-To: <20091019164516.701032uxlen5ai2k@mail.simonandkate.net>
Hi Adam,
On Tue, 20 Oct 2009 21:03:50 +1000, Adam Nielsen wrote:
> It's a shame there's no "passthrough" vrm version that disables the formula
> and shows the raw vid value, as that would probably be quite helpful. Maybe
> it's worth adding a patch to do just that?
This is an interesting idea, however there is a technical problem:
different CPU models have a different number of VID pins. If you need
the pass-through mode, it means the kernel doesn't know about your CPU
model, so it doesn't know how many bits should be read from the chip
and exported.
Another problem is the voltage levels. Different VRM standards use
different voltage levels. Some chips support different modes through
configuration, and the right mode depends on the CPU family. In a
perfect world the BIOS would set it up properly, but experience as
shown this isn't always the case, and as a result some of our drivers
change the mode based on the CPU model. This can't be done if VID
decoding is done in user-space.
So I'm not saying pass-through VID values are a bad idea... but if you
want to implement this, it's not a one-hour hack. It will take some
thoughts and time.
--
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:[~2009-10-20 11:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 6:45 [lm-sensors] Gigabyte GA-P35-DS3P - VID Zero value Simon Wilson
2009-10-19 10:51 ` Justin Piszcz
2009-10-19 11:07 ` Adam Nielsen
2009-10-19 23:35 ` Simon Wilson
2009-10-19 23:59 ` Adam Nielsen
2009-10-20 1:12 ` Simon Wilson
2009-10-20 1:43 ` Adam Nielsen
2009-10-20 2:05 ` Simon Wilson
2009-10-20 11:03 ` Adam Nielsen
2009-10-20 11:23 ` Simon Wilson
2009-10-20 11:38 ` Jean Delvare
2009-10-20 11:48 ` Jean Delvare [this message]
2009-10-20 11:50 ` Adam Nielsen
2009-10-20 11:57 ` Jean Delvare
2009-10-20 12:02 ` Jean Delvare
2009-10-20 12:15 ` Adam Nielsen
2009-10-20 14:15 ` Jean Delvare
2009-10-21 12:15 ` Simon Wilson
2009-10-21 12:30 ` Simon Wilson
2009-10-21 12:51 ` Jean Delvare
2009-10-21 12:53 ` Jean Delvare
2009-10-21 12:57 ` Simon Wilson
2009-10-21 13:06 ` Jean Delvare
2009-10-21 13:28 ` Adam Nielsen
2009-10-21 13:41 ` Jean Delvare
2009-10-22 12:28 ` Jean Delvare
2009-10-22 23:20 ` Adam Nielsen
2009-10-23 7:13 ` 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=20091020134848.2c3188bc@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.