From: Adam Nielsen <a.nielsen@shikadi.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Gigabyte GA-P35-DS3P - VID Zero value
Date: Tue, 20 Oct 2009 01:43:46 +0000 [thread overview]
Message-ID: <4ADD15D2.8090001@shikadi.net> (raw)
In-Reply-To: <20091019164516.701032uxlen5ai2k@mail.simonandkate.net>
> The file is dated Sept 20 2006. I suspect this may be the issue... there
> is nothing in there for VRM 10 or 11. It would appear that I need a
> later hwmon-vid driver? Or am I completely on the wrong track there LOL...
That's only your installed header file. It would only affect userspace
programs doing the conversion themselves. The latest code from the
kernel module is at:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/hwmon/hwmon-vid.c;hb=HEAD
And all the VID revisions are defined in there.
> As you say, the info is definitely there to be read - according to
> http://lists.lm-sensors.org/pipermail/lm-sensors/2008-October/024581.html
> the IT8718F does have VID info, but it is stored differently:
>
> "The IT8718F and IT8720F also features VID inputs (up to 8 pins) but the
> value is stored in the Super-I/O configuration space. Due to technical
> limitations, this value can currently only be read once at
> initialization time, so the driver won't notice and report changes in
> the VID value. The two upper VID bits share their pins with voltage
> inputs (in5 and in6) so you can't have both on a given board."
Well it looks like the value isn't being read properly during chip
initialisation. Perhaps a bug in the it87 hwmon driver?
The VID seems to get read in around line 1037:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/hwmon/it87.c#l1035
Probably more research required to figure out why that value is zero on
our motherboards.
Cheers,
Adam.
_______________________________________________
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 1:43 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 [this message]
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
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=4ADD15D2.8090001@shikadi.net \
--to=a.nielsen@shikadi.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.