From: DarkNovaNick@gmail.com
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Sandy Bridge support?
Date: Tue, 18 Jan 2011 16:47:44 +0000 [thread overview]
Message-ID: <00221532c430e339f1049a21a826@google.com> (raw)
In-Reply-To: <0022152d6d71d9f528049a109a02@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1764 bytes --]
On Jan 18, 2011 10:32am, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Nick,
> On Tue, 18 Jan 2011 10:03:23 -0600, Nick Hall wrote:
> > Thanks, I checked and my motherboard did indeed have that chip. The only
> > difference, if it matters, is that under the "IT8728F" mine
> had "1039-CXS"
> > and "ZC46FBGB".
> OK, thanks. If you feel lucky, you may try to load the it87 driver with
> parameter force_id, to force the driver to consider your chip as one it
> supports. Given the name of your device, the first values to try would
> be 0x8721 and 0x8720 (the two most recent chips) or 0x8718 (in case the
> IT8728F is an evolution of the IT8718F - I remember the IT8716F and
> IT8726F were compatible.) If you give this a try, please let us know
> the results.
> Or you can wait for us to get a datasheet for the IT8728F. We currently
> don't have it. The device isnt' even listed on ITE's website.
> > And regarding the sensors-detect script, I understand now. If anyone is
> > interested, my Sandy Bridge processor would be model "0x2A" according
> to how
> > that script does things.
> This is an option, yes, but it would be better if we could implement
> the same detection logic as the coretemp driver has. For one thing, this
> would guarantee that the two are always in sync. For another, it would
> lower the maintenance effort from our side, as the new detection logic
> is universal and doesn't need to be updated with every new CPU model.
> I'm looking into it but this is non-trivial.
> --
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
Thanks very much for your help, I was able to load the it87 driver with
0x8720 and now running "sensors" gives data that at first glance makes
sense.
Nick
[-- Attachment #1.2: Type: text/html, Size: 2463 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-01-18 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 20:26 [lm-sensors] Sandy Bridge support? DarkNovaNick
2011-01-17 21:54 ` Guenter Roeck
2011-01-17 22:26 ` Anish Patel
2011-01-17 22:53 ` Guenter Roeck
2011-01-17 23:26 ` DarkNovaNick
2011-01-18 8:46 ` Jean Delvare
2011-01-18 12:59 ` Jean Delvare
2011-01-18 16:03 ` Nick Hall
2011-01-18 16:32 ` Jean Delvare
2011-01-18 16:47 ` DarkNovaNick [this message]
2011-01-18 22:35 ` Jean Delvare
2011-01-18 23:24 ` Guenter Roeck
2011-01-19 3:22 ` DarkNovaNick
2011-01-19 5:50 ` Jeff Rickman
2011-01-19 10:01 ` Jean Delvare
2011-11-22 10:14 ` 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=00221532c430e339f1049a21a826@google.com \
--to=darknovanick@gmail.com \
--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.