From: Cort Dougan <cort@fsmlabs.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Dominik Brodowski <devel@brodo.de>,
cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5.32] CPU frequency and voltage scaling (0/4)
Date: Wed, 28 Aug 2002 12:48:39 -0600 [thread overview]
Message-ID: <20020828124839.F5492@host110.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0208281140030.4507-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Wed, Aug 28, 2002 at 11:47:54AM -0700
It's even worse for some of the very new P4's that don't have their
heatsink seated properly. They heat up every few minutes and then throttle
themselves due to thermal overload. I think this situation is going to
become more and more common, now. We're at the mercy of every BIOS and
micro-code programmer now-a-days. That situation needs to be improved
upon, as well.
} The interface needs to be improved upon. It is simply _not_ valid to say
} "run at this speed" as the primary policy.
next prev parent reply other threads:[~2002-08-28 18:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 11:46 [PATCH][2.5.32] CPU frequency and voltage scaling (0/4) Dominik Brodowski
2002-08-28 18:47 ` Linus Torvalds
2002-08-28 18:48 ` Cort Dougan [this message]
2002-08-28 19:25 ` Alan Cox
2002-08-28 19:32 ` Cort Dougan
2002-08-29 10:26 ` Zwane Mwaikambo
2002-08-28 19:41 ` Peter Riocreux
2002-08-28 19:58 ` Linus Torvalds
2002-08-29 9:51 ` Padraig Brady
2002-08-29 10:23 ` Zwane Mwaikambo
2002-08-28 19:21 ` Alan Cox
2002-08-28 19:49 ` Linus Torvalds
2002-08-28 20:25 ` Alan Cox
2002-08-28 20:29 ` Linus Torvalds
2002-08-28 23:26 ` Alan Cox
2002-08-28 23:49 ` Linus Torvalds
2002-08-30 0:39 ` jw schultz
2002-08-29 7:01 ` Dominik Brodowski
2002-08-28 20:39 ` Dominik Brodowski
2002-08-28 21:05 ` Linus Torvalds
2002-09-06 11:31 ` Pavel Machek
2002-08-28 20:27 ` Dominik Brodowski
2002-08-28 20:19 ` Dominik Brodowski
2002-08-28 20:43 ` Linus Torvalds
2002-08-28 20:53 ` Dominik Brodowski
2002-08-28 21:08 ` Linus Torvalds
2002-08-28 23:00 ` george anzinger
2002-08-28 23:30 ` Alan Cox
2002-08-29 0:08 ` Linus Torvalds
2002-08-29 7:07 ` Dominik Brodowski
2002-08-29 10:02 ` Padraig Brady
2002-08-29 10:53 ` Alan Cox
2002-08-29 13:38 ` Dave Jones
2002-08-29 18:47 ` Linus Torvalds
2002-08-29 19:24 ` Alan Cox
2002-08-29 21:22 ` george anzinger
2002-08-30 6:46 ` David Gibson
2002-08-30 7:54 ` Helge Hafting
2002-08-30 3:21 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 20:25 Grover, Andrew
2002-08-28 20:46 ` Linus Torvalds
2002-08-29 15:07 Pering, Trevor
2002-08-30 8:04 ` Helge Hafting
2002-08-30 11:53 ` Dave Jones
2002-08-30 12:36 ` Helge Hafting
2002-08-30 22:43 ` george anzinger
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=20020828124839.F5492@host110.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=cpufreq@www.linux.org.uk \
--cc=devel@brodo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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