From: Michael Tokarev <mjt@tls.msk.ru>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: Brad Campbell <brad@wasp.net.au>,
lm-sensors@lm-sensors.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] it87 sensors need an ACPI driver (2.6.31)
Date: Tue, 06 Oct 2009 15:22:15 +0000 [thread overview]
Message-ID: <4ACB60A7.307@msgid.tls.msk.ru> (raw)
In-Reply-To: <68676e00910060800h4cb84dcl9f610f6b23a88e5c@mail.gmail.com>
Luca Tettamanti wrote:
> On Mon, Oct 5, 2009 at 6:42 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
[]
>> Well, I just tried it here and it works here too, on 3 different
>> asus motherboards. But asus_atk0110 is far less useful than the
>> it87 variant. Yes atk0110 shows correct labels for various sensors,
>> but for one there's no way to control fan speeds using it, at least
>> not currently, -- something which is done by it87 easily.
[]
> The main reason for using atk0110 is correctness: the resources are
> claimed by ACPI, it might not be safe to touch them (for the same
> reason two drivers are not allowed to map e.g. the same PCI BAR).
> On newer boards the risk of collision is pretty high, since the hwmon
> chip is used by an EC that works in background... on other boards the
> risk is much lower since the hwmon chip doesn't seem to be probed
> actively.
> Anyway, as user you can override this decision with
> "acpi_enforce_resources=lax", but _I_ wouldn't recommend it.
If there's a choice between "does not work but correct" and
"incorrect but works", i'd prefer the latter, and I'd say any
sane person agrees.
I spent quite some time choosing a motherboard that is able
to control fan speeds. Now if know that it does that "incorrectly".
So I should either throw it away because one of the most
important criterias (ability to control noise level) does
not satisfy me anymore, or use it the "wrong" way as I did
for whole last year. Ditto for 4 other asus motherboards
that have exactly the same problem.
Yes I know about acpi_enforce_resources.
Ok. Now a pure technical question, finally. Is there a
way to made asus_atk0110 to be able to *set* fan speeds
too, in a way as it's done by it87?
Because that's mostly the only issue with this driver,
and for me at least it's a show-stopper.
Thanks!
/mjt
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: Brad Campbell <brad@wasp.net.au>,
lm-sensors@lm-sensors.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] it87 sensors need an ACPI driver (2.6.31)
Date: Tue, 06 Oct 2009 19:22:15 +0400 [thread overview]
Message-ID: <4ACB60A7.307@msgid.tls.msk.ru> (raw)
In-Reply-To: <68676e00910060800h4cb84dcl9f610f6b23a88e5c@mail.gmail.com>
Luca Tettamanti wrote:
> On Mon, Oct 5, 2009 at 6:42 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
[]
>> Well, I just tried it here and it works here too, on 3 different
>> asus motherboards. But asus_atk0110 is far less useful than the
>> it87 variant. Yes atk0110 shows correct labels for various sensors,
>> but for one there's no way to control fan speeds using it, at least
>> not currently, -- something which is done by it87 easily.
[]
> The main reason for using atk0110 is correctness: the resources are
> claimed by ACPI, it might not be safe to touch them (for the same
> reason two drivers are not allowed to map e.g. the same PCI BAR).
> On newer boards the risk of collision is pretty high, since the hwmon
> chip is used by an EC that works in background... on other boards the
> risk is much lower since the hwmon chip doesn't seem to be probed
> actively.
> Anyway, as user you can override this decision with
> "acpi_enforce_resources=lax", but _I_ wouldn't recommend it.
If there's a choice between "does not work but correct" and
"incorrect but works", i'd prefer the latter, and I'd say any
sane person agrees.
I spent quite some time choosing a motherboard that is able
to control fan speeds. Now if know that it does that "incorrectly".
So I should either throw it away because one of the most
important criterias (ability to control noise level) does
not satisfy me anymore, or use it the "wrong" way as I did
for whole last year. Ditto for 4 other asus motherboards
that have exactly the same problem.
Yes I know about acpi_enforce_resources.
Ok. Now a pure technical question, finally. Is there a
way to made asus_atk0110 to be able to *set* fan speeds
too, in a way as it's done by it87?
Because that's mostly the only issue with this driver,
and for me at least it's a show-stopper.
Thanks!
/mjt
next prev parent reply other threads:[~2009-10-06 15:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 8:20 [lm-sensors] it87 sensors need an ACPI driver (2.6.31) wixor
2009-09-20 8:20 ` wixor
2009-09-20 9:10 ` [lm-sensors] " Holger Hoffstaette
2009-09-20 9:10 ` Holger Hoffstaette
2009-09-20 9:17 ` Alan Jenkins
2009-09-20 9:17 ` [lm-sensors] " Alan Jenkins
2009-09-20 12:20 ` Luca Tettamanti
2009-09-20 12:20 ` Luca Tettamanti
2009-09-20 12:46 ` wixor
2009-09-20 12:46 ` wixor
2009-09-20 20:37 ` Gene Heskett
2009-09-20 20:37 ` Gene Heskett
2009-09-20 21:31 ` Luca Tettamanti
2009-09-20 21:31 ` Luca Tettamanti
2009-09-21 0:35 ` Gene Heskett
2009-09-21 9:43 ` Luca Tettamanti
2009-09-21 15:02 ` Gene Heskett
2009-09-21 15:07 ` Luca Tettamanti
2009-10-05 0:11 ` Brad Campbell
2009-10-05 0:11 ` Brad Campbell
2009-10-05 9:12 ` Michael Tokarev
2009-10-05 9:12 ` Michael Tokarev
2009-10-05 13:48 ` Brad Campbell
2009-10-05 13:48 ` Brad Campbell
2009-10-05 15:37 ` Luca Tettamanti
2009-10-05 15:37 ` Luca Tettamanti
2009-10-05 16:40 ` Jean Delvare
2009-10-05 16:40 ` Jean Delvare
2009-10-05 16:42 ` Michael Tokarev
2009-10-05 16:42 ` Michael Tokarev
2009-10-06 15:00 ` Luca Tettamanti
2009-10-06 15:00 ` Luca Tettamanti
2009-10-06 15:22 ` Michael Tokarev [this message]
2009-10-06 15:22 ` Michael Tokarev
2009-10-06 15:34 ` Luca Tettamanti
2009-10-06 15:34 ` Luca Tettamanti
2009-10-06 15:41 ` Michael Tokarev
2009-10-06 15:41 ` Michael Tokarev
2009-10-06 16:00 ` Jean Delvare
2009-10-06 16:00 ` Jean Delvare
2009-10-06 16:10 ` Luca Tettamanti
2009-10-06 16:10 ` Luca Tettamanti
2009-10-06 16:04 ` Alan Jenkins
2009-10-06 16:04 ` Alan Jenkins
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=4ACB60A7.307@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=brad@wasp.net.au \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.