From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CPUfreq
Date: 7 Mar 2003 13:51:10 -0800 [thread overview]
Message-ID: <b4b48e$c93$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.51.0303072042270.26259@dns.toxicfilms.tv
Followup to: <Pine.LNX.4.51.0303072042270.26259@dns.toxicfilms.tv>
By author: Maciej Soltysiak <solt@dns.toxicfilms.tv>
In newsgroup: linux.dev.kernel
>
> short question: why is CPU Frequency scaling under Power management
> options? Not in a more obvious place.
>
Because it's a mechanism for power management?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-03-07 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 19:44 CPUfreq Maciej Soltysiak
2003-03-07 21:51 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 21:43 CPUfreq Grover, Andrew
2003-03-07 21:55 ` CPUfreq Chris Friesen
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='b4b48e$c93$1@cesium.transmeta.com' \
--to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox