From: "J.A. Magallón" <jamagallon@ono.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Useless thermal acpi driver ?
Date: Tue, 15 Dec 2009 23:46:19 +0100 [thread overview]
Message-ID: <20091215234619.62d0ebc1@werewolf.home> (raw)
In-Reply-To: <alpine.LFD.2.00.0912142159540.9446@localhost.localdomain>
On Mon, 14 Dec 2009 22:00:25 -0500 (EST), Len Brown <lenb@kernel.org> wrote:
> this DSDT returns a constant temperature, always:
>
> Method (_TMP, 0, NotSerialized)
> {
> Return (0x0BB8)
> }
>
>
> so in this case, Linux is just reporting the (lack of) news:-)
>
So, lets see...:
- Someone decided ACPI is the only-real-good-way
- Only a few devices are ported to ACPI
- The old way is unusable
- We can not return to the old way
So, any solution ? Thermal ACPI info in this boards (and I suspect in many
others) is useless. We can not disable that part of ACPI, we can not enable
sensors. So no thermal monitoring.
Nice.
Ayways, as in this case the ACPI part does not any real work, is still
present the problem of two drivers poking the same hardware or could I use
that 'lax' trick ?
And second, can the traditional sensor drivers be ported to offer an ACPI
device replacing the default one, or is that a stupid question ?
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2010.0 (Cooker) for x86_64
Linux 2.6.29.3-desktop-1mnb (gcc 4.3.2 (GCC) #1 Wed May
next prev parent reply other threads:[~2009-12-15 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 22:26 J.A. Magallón
2009-12-10 1:00 ` Robert Hancock
2009-12-11 6:25 ` Len Brown
2009-12-11 8:45 ` J.A. Magallón
2009-12-15 3:00 ` Len Brown
2009-12-15 22:46 ` J.A. Magallón [this message]
2009-12-16 5:21 ` Len Brown
2009-12-22 1:06 ` Robert Hancock
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=20091215234619.62d0ebc1@werewolf.home \
--to=jamagallon@ono.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®