Hi Luca,
On Wed, 5 Jan 2011 15:08:44 +0100, Luca Tettamanti wrote:
> On Wed, Jan 5, 2011 at 2:45 PM, Joris Creyghton <jorisctn@xxxxxxxxx> wrote:
> > The MCH temp. is always 0 en never jumps.
> >
> > Attached you'll find the file /sys/firmware/acpi/tables/DSDT
>
> Hum, it appears to be a bug in the ACPI code, the method that reads
> the temperature does not know how to read the MCH temperature which
> would be HWT2 (the entry is present in the enumeration though):
>
> Method (TGET, 1, NotSerialized)
> {
> If (LEqual (Arg0, Zero))
> {
> Return (^^SIOR.HWT1 ())
> }
>
> If (LEqual (Arg0, One))
> {
> Return (^^SIOR.HWT0 ())
> }
> }
>
> To complicate things the firmware provides both the old and the new
> ATK0110 interfaces, and the driver selects the old one. The new one
> seems to have the code to read all the sensors. I'll see what I can
> do.
Would it make sense to add a module parameter to asus_atk0110 to let
the user force the interface when both are present? So that the user
can test the other one and report easily.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
