From: Gabriel C <crazy@frugalware.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Asus atk0110 driver
Date: Sun, 22 Jun 2008 16:15:51 +0000 [thread overview]
Message-ID: <485E7AB7.5070003@frugalware.org> (raw)
In-Reply-To: <20080618212629.GA7917@dreamland.darkstar.lan>
Jean Delvare wrote:
Hi Jean , Luca ,
> On Wed, 18 Jun 2008 23:26:29 +0200, Luca Tettamanti wrote:
>> Il Mon, Jun 16, 2008 at 09:32:27AM +0200, Jean Delvare ha scritto:
>>> Apparently your post was not archived on acpi4asus-user. Can you please
>>> post your driver again, on the lm-sensors list this time? I'd like it
>>> to be archived publicly so that we can point users to it and it doesn't
>>> get lost.
>> Sure. This is the patch for in-kernel ACPI (diff against vanilla
>> 952f4a0a, somewhere after 2.6.26-rc6):
>> (...)
>> The source of the driver is attached (text/plain).
>
> Thanks Luca. I've added a link to your post on wiki/Devices so that
> interested users and developers can find it easily.
>
I've tested the driver with linux-next on my P5E-VM DO motherboard.
The driver seems to work , the values / data in /sys/class/hwmon/hwmon0/device/*
seems to be the same like what the BIOS reports.
However how do I get sensors to display the data from atk driver ?
I guess I have to patch lm-sensors ?
Luca what do you think about creating a proper patch for the driver too and send it over to
Greg to be included in his linux-staging tree ? I think that way it will get more testing.
Best Regards ,
Gabriel
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-06-22 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 21:26 [lm-sensors] Asus atk0110 driver Luca Tettamanti
2008-06-19 7:16 ` Jean Delvare
2008-06-22 16:15 ` Gabriel C [this message]
2008-06-23 9:06 ` Jean Delvare
2008-06-23 12:41 ` Gabriel C
2008-06-23 13:48 ` Jean Delvare
2008-06-30 19:58 ` Luca Tettamanti
2008-06-30 22:20 ` Gabriel C
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=485E7AB7.5070003@frugalware.org \
--to=crazy@frugalware.org \
--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.