From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Can set all but active[2] temperature via trip_points
Date: Mon, 26 Apr 2004 13:25:50 +0200 [thread overview]
Message-ID: <20040426112550.GB23616@fuchi> (raw)
In-Reply-To: <20040425055737.GA7358-OcF6MH9IheHrhBy7cqgyXA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
hello hugo...
* Hugo Haas <hugo-rQR7RsZM/uVeoWH0uzbU5w@public.gmane.org> [2004-04-26 09:25 +0200]:
>
> I have found a weird problem: using
> /proc/acpi/thermal_zone/TZ1/trip_points, I can set all but the
> active[2] temperature.
i had a little discussion with pavel machek about that a couple of weeks
ago. as written in 12.3.1, the acpi spec defines 10 active states.
the current implementation in linux is implemented for only 2 active
states, because pavel had not seen more than that before. he also told
me that it should not be too hard to expand this to more active states.
so you could either nag him to do that or do it yourself and send the
patch to this list. :)
hth,
sebastian
--
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-26 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 5:57 Can set all but active[2] temperature via trip_points Hugo Haas
[not found] ` <20040425055737.GA7358-OcF6MH9IheHrhBy7cqgyXA@public.gmane.org>
2004-04-26 11:25 ` Sebastian Henschel [this message]
[not found] ` <20040426112550.GB23616-5sK/Rx+du8M@public.gmane.org>
2004-04-26 21:42 ` Stefan Seyfried
[not found] ` <20040426214213.GA10794-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-04-27 9:08 ` Stefan Seyfried
2004-04-28 13:50 ` Pavel Machek
2004-04-30 14:16 ` [PATCH] " Stefan Seyfried
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=20040426112550.GB23616@fuchi \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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