From: j.w.r.degoede@hhs.nl (Hans de Goede)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Answer Epox - EPoX EP1308 sensor-chip
Date: Wed, 04 Oct 2006 14:01:49 +0000 [thread overview]
Message-ID: <4523BECD.5080603@hhs.nl> (raw)
In-Reply-To: <450B14DB.2090505@sh.cvut.cz>
Jean Delvare wrote:
> Note that I am unlikely to accept undocumented fan control functions in
> the mainline kernel anyway. I don't want to put the user's system at
> risk, and I don't want to encourage manufacturers to keep their
> documentation secret.
>
Define undocumented, if undocumented means the chip can do it, but the
motherboard manufacturer didn't implement this in its drivers for other
OS and BIOS, then I agree with you. However here the settings can be
controlled through the bios, thus I believe we should allow modifying
them from lm-sensors too (to the limits the bios allows and no more).
This ofcourse assumes we manage to find out exactly how these work, to
the point where we can say this setting in the BIOs matches that and
that byte in X increment units. If it stays as vague as this setting
influences those bytes, then I fully agree with you.
Regards,
Hans
next prev parent reply other threads:[~2006-10-04 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 21:02 [lm-sensors] Answer Epox - EPoX EP1308 sensor-chip Rudolf Marek
2006-09-28 10:06 ` Hans Edgington
2006-09-28 16:21 ` Hans de Goede
2006-09-28 21:20 ` Rudolf Marek
2006-09-28 21:39 ` Jean Delvare
2006-09-28 21:43 ` Jean Delvare
2006-09-28 23:42 ` Hans Edgington
2006-09-29 7:37 ` Jean Delvare
2006-09-29 7:45 ` Hans de Goede
2006-09-29 7:50 ` Jean Delvare
2006-09-29 8:03 ` Jean Delvare
2006-09-29 10:32 ` Hans Edgington
2006-09-29 11:27 ` Jean Delvare
2006-10-02 20:46 ` Hans Edgington
2006-10-04 12:08 ` Jean Delvare
2006-10-04 14:01 ` Hans de Goede [this message]
2006-10-04 14:43 ` 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=4523BECD.5080603@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.