From: Jean Delvare <khali@linux-fr.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard
Date: Thu, 11 Jul 2013 10:47:01 +0200 [thread overview]
Message-ID: <20130711104701.1f1c5fda@endymion.delvare> (raw)
In-Reply-To: <20130703144201.GA10323@roeck-us.net>
Hi Guenter, Justin,
On Wed, 3 Jul 2013 07:42:01 -0700, Guenter Roeck wrote:
> On Wed, Jul 03, 2013 at 08:35:59AM -0400, Justin Piszcz wrote:
> > I also found:
> > http://www.lm-sensors.org/wiki/Configurations/SuperMicro/X9SRA
> >
> > Does Super Micro also have such a config file for the X9SRL-F?
> > This board uses a NCT6776F.
>
> Supermicro does not provide configuration files. You can take the above file,
> test and update it, and let us know so we can add it to the wiki.
Actually they do provide configuration information. They have their own
tool names SuperDoctor, which can be downloaded from:
ftp://ftp.supermicro.com/utility/SuperDoctor_II/Linux/Release/
If you look at file AllSuperD.ini, you'll find per-board entries
describing the input mapping. It is very helpful when writing a custom
libsensors configuration file for the board in question. It takes some
knowledge of the monitoring chip or its driver though, as the ini file
references register addresses ("Offset" in the file.)
A gave a quick look and at least the voltage input mapping (and
presumably the voltage scaling factors as well) is similar to the
X9SRA so you can reuse this part of the X9SRA configuration file.
Hope that helps,
--
Jean Delvare
next prev parent reply other threads:[~2013-07-11 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 12:35 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard Justin Piszcz
2013-07-03 14:42 ` [lm-sensors] " Guenter Roeck
2013-07-03 16:08 ` Justin Piszcz
2013-07-03 16:33 ` Guenter Roeck
2013-07-03 16:47 ` Justin Piszcz
2013-07-03 17:17 ` Guenter Roeck
2013-07-03 17:21 ` Justin Piszcz
2013-07-03 20:56 ` Guenter Roeck
[not found] ` <00ad01ce7830$3b135890$b13a09b0$@lucidpixels.com>
2013-07-03 21:00 ` Justin Piszcz
2013-07-03 22:28 ` Guenter Roeck
2013-07-11 8:47 ` Jean Delvare [this message]
2013-07-11 13:57 ` Justin Piszcz
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=20130711104701.1f1c5fda@endymion.delvare \
--to=khali@linux-fr.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox