Re: Does ACPI conflict also happen on MS/Windows?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 1, 2012 at 4:07 PM, Ian Pilcher <arequipeno@xxxxxxxxx> wrote:
> On 04/30/2012 09:55 AM, Jean Delvare wrote:
>> Most likely they would "work", because they simply do not check the
>> ACPI conflict in the first place. So they run but not reliably, exactly
>> the same as running Linux with acpi_enforce_resources=lax.
>
> On a slightly related note, I've always been a bit bemused by the this
> message:
>
>  If an ACPI driver is available for this device, you should use it
>  instead of the native driver
>
> What is an "ACPI driver"?

It means a driver that uses the interface exposed by ACPI.

> Is there any hardware for which ACPI actually provides the same level of
> information that "legacy" access does?  Every system I've dealt with
> over the last few years provides a single temperature reading via ACPI
> (generally CPU surface temperature) -- no other temperatures, no fans,
> no voltages.

A single TZ is common, yes. Asus motherboards provide the so called
ATK0110 interface for reading temps, fans and voltages.

L

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux