public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>,
	Thomas Renninger <trenn@suse.de>,
	linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: Allow userspace do something special on overtemp
Date: Thu, 12 Aug 2004 17:50:17 +0200	[thread overview]
Message-ID: <411B91B9.6020200@suse.de> (raw)
In-Reply-To: <20040812081634.532e3fc7.rddunlap@osdl.org>

Randy.Dunlap wrote:
> On 12 Aug 2004 11:19:05 -0400 Len Brown wrote:
> 
> | Simpler to delete the usermode call and rely on the (flexible)
> | acpid event, yes?
> | 
> |  thermal.c |   29 +----------------------------
> |  1 files changed, 1 insertion(+), 28 deletions(-)
> 
> a.  Yes, it should be more flexible than just 'overtemp'.
> 
> b.  For userspace, there are:
> 
> acpid -  http://sourceforge.net/projects/acpid/
> 
> acpi tools, like ospmd (by Andy Grover) - in CVS at
>   http://sourceforge.net/projects/acpi/
> 
> What others are there?

powersaved - http://forge.novell.com/modules/xfmod/project/?powersave
handles APM, ACPI and cpufreq
-- 
seife

"Any ideas, John?"
"Well, surrounding thems out."

  reply	other threads:[~2004-08-12 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040811085326.GA11765@elf.ucw.cz>
2004-08-12 15:19 ` Allow userspace do something special on overtemp Len Brown
2004-08-12 15:16   ` Randy.Dunlap
2004-08-12 15:50     ` Stefan Seyfried [this message]
2004-08-12 17:27   ` [ACPI] " Stefan Dösinger
     [not found]     ` <200408121927.11277.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-12 22:53       ` Len Brown

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=411B91B9.6020200@suse.de \
    --to=seife@suse.de \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rddunlap@osdl.org \
    --cc=trenn@suse.de \
    /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