Luca Tettamanti wrote:
On Mon, Oct 5, 2009 at 6:42 PM, Michael Tokarev <mjt@xxxxxxxxxx> 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@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
