All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Grover, Andrew" <andrew.grover@intel.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Lid support for ACPI
Date: Thu, 26 Apr 2001 00:13:23 +0200	[thread overview]
Message-ID: <20010426001323.B351@bug.ucw.cz> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDDDC9@orsmsx35.jf.intel.com>
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDDDC9@orsmsx35.jf.intel.com>; from Grover, Andrew on Wed, Apr 25, 2001 at 10:23:12AM -0700

Hi!

> We already have lid support in the latest ACPI versions (not in the official
> kernel yet.) You can download this code from
> http://developer.intel.com/technology/iapc/acpi/downloads.htm .
> 
> It'd be great if you could focus your testing and patches on this code base
> -- I think it's a lot better but it's still a work in progress.

I was just browsing its sources:

+       if (tz->policy.temperature >=
+               tz->policy.critical.threshold->temperature) {
+               DEBUG_PRINT(ACPI_WARN, ("Critical threshold reached - shutting down system.\n"));
+               /* TODO: 'halt' */
+       }

Are you sure that kill(init, SIGTERM) is not right answer here?

								Pavel
PS: This seems very strange. What if machine is so crashed so that it
can no longer shutdown properly. Will that mean that its CPU will
damage itself?
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-04-27 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-25 17:23 Lid support for ACPI Grover, Andrew
2001-04-25 20:22 ` Pavel Machek
2001-04-25 22:13 ` Pavel Machek [this message]
2001-04-27 17:08 ` Michael K. Johnson
2001-04-29  1:42   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2001-04-30  5:00 Grover, Andrew
2001-04-25 20:54 Grover, Andrew
2001-04-23  8:45 Pavel Machek

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=20010426001323.B351@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=andrew.grover@intel.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 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.