From: Samuel Rydh <samuel@ibrium.se>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [.config] CONFIG_THERM_WINDTUNNEL
Date: Fri, 26 Mar 2004 19:30:20 +0100 [thread overview]
Message-ID: <20040326183020.GA19610@ibrium.se> (raw)
In-Reply-To: <20040324001828.GB238@elf.ucw.cz>
On Wed, Mar 24, 2004 at 01:18:28AM +0100, Pavel Machek wrote:
> Is it actually possible to set that hardware to self-destruct?
>
> [ACPI notebooks have very simple hardware failsafe: if temperature
> exceeds some hard limit, power is simply cut.]
Well, I'm not sure.
I know that the hardware which controls the fan (a separate temperature
sensor and a combined sensor/controller) is not connected to any death
switch; the available overheat pin serves as a 100% fan override. There
might very well be a safety mechanism in the UniNorth bridge though.
Something like a forced power off if interrupts are not handled in
a timely manner. I'm pretty sure I have seen references to this behavior
in conjunction with the PowerBook G4. The dual G4 architecture is not all
that different...
It would be interesting to see what happens if one disables the overheat
protection and stops the fan. Anybody volunteering? At least one
has an excellent reason why one need one of those new G5 machines
if things start to smoke :-).
/Samuel
next prev parent reply other threads:[~2004-03-26 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 7:21 [.config] CONFIG_THERM_WINDTUNNEL Michał Roszka
2004-03-18 9:16 ` Giuliano Pochini
2004-03-18 11:20 ` Samuel Rydh
2004-03-18 11:27 ` Giuliano Pochini
2004-03-18 11:36 ` Michał Roszka
2004-03-18 12:03 ` Samuel Rydh
2004-03-24 0:18 ` Pavel Machek
2004-03-26 18:30 ` Samuel Rydh [this message]
2004-03-26 22:32 ` Pavel Machek
2004-03-18 16:17 ` Michał Roszka
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=20040326183020.GA19610@ibrium.se \
--to=samuel@ibrium.se \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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