From: Malte Thoma <thoma-iYtK5bfT9M8b1SvskN2V4Q@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>,
ACPI-Devel
<Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: heatload 0.4 now with throttling support
Date: Wed, 18 Dec 2002 17:13:41 +0100 [thread overview]
Message-ID: <3E009EB5.7010109@muenster.de> (raw)
In-Reply-To: <20021218153355.GK347-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
Ducrot Bruno wrote:
>After dpkg and heatload, get
> Sorry can't open any of the following files:
> /proc/acpi/thermal_zone/THRM/temperature
> /proc/acpi/thermal/0/status
>
>But
># ls /proc/acpi/thermal_zone/
>THM0
>
>
>Please fix by parsing the entry of /proc/acpi/thermal_zone,
>
can you please send me
cat /proc/acpi/thermal_zone/THM0
... it seems to me that there are a LOT of different
proc/acpi-structures :-(
/proc/acpi/thermal/0/status
/proc/acpi/thermal_zone
/proc/acpi/thermal_zone/THRM/temperature
and now:
/proc/acpi/thermal_zone/THM0
hope that the ACPI-group stabilize this ;-)
>and
>do not forget that you can have more than one thermal zone.
>
>
>
until now heatload workes only for one CPU (i suppose the thermal_zone
is coherent to the counting of CPUs?)
I won't be hard to improve it to more than one, but doing THAT for
recurrent changing directory structs does not make fun.
If you can tell me more about the future (and present) of the
proc/acpi-structure depending on the numers of CPU I will start
implementing this feature between christmas and new years eve ;-)
Greetings,
Malte
>
>
-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
next prev parent reply other threads:[~2002-12-18 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 14:07 heatload 0.4 now with throttling support Malte Thoma
[not found] ` <20021218153355.GK347@poup.poupinou.org>
[not found] ` <20021218153355.GK347-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-12-18 16:13 ` Malte Thoma [this message]
[not found] ` <3E009EB5.7010109-iYtK5bfT9M8b1SvskN2V4Q@public.gmane.org>
2002-12-18 17:08 ` Faye Pearson
[not found] ` <20021218170828.GA9127-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2002-12-18 17:22 ` Malte Thoma
[not found] ` <3E00AEC8.9050906-iYtK5bfT9M8b1SvskN2V4Q@public.gmane.org>
2002-12-18 18:03 ` Faye Pearson
[not found] ` <20021218180329.GA9439-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2002-12-19 13:23 ` Ducrot Bruno
[not found] ` <20021219132303.GH4257-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-12-19 15:27 ` Faye Pearson
[not found] ` <20021219152724.GA14703-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2002-12-19 15:39 ` Ducrot Bruno
2002-12-19 12:09 ` Ducrot Bruno
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=3E009EB5.7010109@muenster.de \
--to=thoma-iytk5bft9m8b1svskn2v4q@public.gmane.org \
--cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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