From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Nils Faerber
<nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Kernel 2.4.23 passive cooling
Date: Tue, 2 Dec 2003 13:42:40 +0100 [thread overview]
Message-ID: <20031202124240.GC6024@hell.org.pl> (raw)
In-Reply-To: <20031202122644.GA6024-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
Thus wrote Karol Kozimor:
> What I suspect is that there are some semi-obscure things going on in the
> AML and it would take me at least two or three cups of coffee to trace it.
> I'll see what I can do.
Oh, and it would *very much* help me if I knew how to make _all_ thermal
events visible and reported (be it through /proc/acpi/event or at least
through a debug switch), and not only the 0x81 ones (hint hint!).
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-02 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 18:02 Kernel 2.4.23 passive cooling Nils Faerber
[not found] ` <1070301739.1353.6.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2003-12-02 12:26 ` Karol Kozimor
[not found] ` <20031202122644.GA6024-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-12-02 12:42 ` Karol Kozimor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 3:29 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720BEE-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-12 19:04 ` Karol Kozimor
2004-01-13 6:47 Yu, Luming
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=20031202124240.GC6024@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@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