public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: ruud koendering
	<ruud.koendering-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RE: Presario DANGER
Date: Thu, 7 Nov 2002 18:10:17 +0100	[thread overview]
Message-ID: <20021107171017.GA157@elf.ucw.cz> (raw)
In-Reply-To: <200211041130.44371.ruud.koendering-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>

Hi!

> All the Compaq Presario's are in danger without ACPI. This is confirmed by new 

Do you have some details?

If they are in danger, they are not ACPI compliant, because ACPI
states machine must actually power off on overheat.
									Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2002-11-07 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 10:30 Presario DANGER ruud koendering
     [not found] ` <200211041130.44371.ruud.koendering-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2002-11-04 10:45   ` Markus Gaugusch
2002-11-04 12:55   ` Alan Cox
     [not found]     ` <1036414528.1113.8.camel-MMxVpc8zpTQVh3rx8e9g/fyykp6/JSeS3vcXtXqGYxw@public.gmane.org>
2002-11-07 17:13       ` Pavel Machek
2002-11-04 17:40   ` Ruud Koendering
     [not found]     ` <200211041840.59356.ruud.koendering-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2002-11-04 18:41       ` Ducrot Bruno
2002-11-07 17:10   ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04 20:10 Cagle, John (ISS-Houston)

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=20021107171017.GA157@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ruud.koendering-EIBgga6/0yRmR6Xm/wNWPw@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