From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] sensors.conf for supermicro x7dbe+
Date: Thu, 11 Jan 2007 09:35:04 +0000 [thread overview]
Message-ID: <20070111103504.40eeb866.khali@linux-fr.org> (raw)
In-Reply-To: <200701031701.08165.nromer@arcmailtech.com>
Hi Rudolf,
On Wed, 10 Jan 2007 23:34:50 +0100, Rudolf Marek wrote:
> > 1* We display the sensor type in "sensors". This is what we do for the
> > IT87xxF devices. When the sensor type is "disabled", the user should
> > realize that the reading is meaningless.
> >
> > 2* We change sensors to not even display tempN if that sensor is
> > disabled. This is probably even more user-friendly.
>
> You mean during init phase?
I mean that the sensors tool would first read temp1_type, if it's 0
skip temp1 altogether, else read and display all temp1 attributes as
before. Same for temp2 etc.
> > 3* We change the w83793 driver to not present the temperature value
> > when the sensor is disabled. A bit more difficult, but doable. There's
> > something of this kind done in the f71805f hardware monitoring driver.
>
> Yes but we need to keep the control file for that.
Depends on how we implement it. We may decide that the BIOS must have
set the types properly, make tempN_type read-only (the f71805f driver
does that), and simply not create any file for disabled temperature
channels. Or indeed we can let the user override what the BIOS has set,
in which case we must create and delete the tempN_input files
dynamically (or change their permissions dynamically, that works too).
This second option is more complex, but seems to have your preference.
As for me, I'm fine with both, as I'm not the one writing the code ;)
--
Jean Delvare
next prev parent reply other threads:[~2007-01-11 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 1:01 [lm-sensors] sensors.conf for supermicro x7dbe+ Noah Romer
2007-01-05 22:19 ` Rudolf Marek
2007-01-06 2:14 ` Noah Romer
2007-01-07 11:08 ` Rudolf Marek
2007-01-07 12:05 ` Rudolf Marek
2007-01-08 8:49 ` JGong at winbond.com
2007-01-08 23:52 ` Noah Romer
2007-01-09 6:18 ` JGong at winbond.com
2007-01-09 18:15 ` Noah Romer
2007-01-10 8:59 ` JGong at winbond.com
2007-01-10 9:49 ` Jean Delvare
2007-01-10 22:34 ` Rudolf Marek
2007-01-11 9:35 ` Jean Delvare [this message]
2007-01-14 18:50 ` Rudolf Marek
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=20070111103504.40eeb866.khali@linux-fr.org \
--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.