From: Ed Vance <EdV@macrolink.com>
To: "'Ed Sweetman'" <ed.sweetman@wmich.edu>
Cc: Corvus Corax <corvusvcorax@gemia.de>, linux-kernel@vger.kernel.org
Subject: RE: Linux vs Windows temperature anomaly
Date: Thu, 6 Mar 2003 09:29:24 -0800 [thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D1A33DCD@EXCHANGE> (raw)
On Thu, March 06, 2003 at 12:58 AM, Ed Sweetman wrote:
>
> I believe the originator of the thread went back to check and
> see if he can find out exactly what his Windows drivers are
> enabling. the rest of the thread has been arguing over if
> linux can load hardware more than windows can and what puts
> off heat and what doesn't which is stupid.
>
> i think the topic of the thread is a bunch of BS because
> unless he has a driver that is for some reason changing the
> frequency of something or the voltage then linux is not going
> to stress the system more than windows. The whole thing wreaks
> of FUD whether intentional or not.
>
Well, here's _my_ stupid BS and (intentional) FUD question: 8)
Does anybody know if XP actively performs progressive power
management actions as the CPU temperature increases inside the
normal operating range? If this were done somewhat linearly
starting at "medium rare", instead of only at "well done" to
save the hardware, wouldn't it look like the reported anomaly?
Always suspicious ;)
Ed
----------------------------------------------------------------
Ed Vance edv (at) macrolink (dot) com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------
next reply other threads:[~2003-03-06 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 17:29 Ed Vance [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 12:30 SWSUSP Discontiguous pagedir patch Pavel Machek
2003-03-04 20:36 ` Patrick Mochel
2003-03-05 20:50 ` Pavel Machek
2003-03-05 21:52 ` Linux vs Windows temperature anomaly Jonathan Lundell
2003-03-05 23:11 ` Herman Oosthuysen
2003-03-05 23:38 ` Con Kolivas
2003-03-05 23:50 ` Russell King
2003-03-06 0:29 ` Ed Sweetman
2003-03-06 0:47 ` Trever L. Adams
2003-03-06 9:45 ` Russell King
2003-03-06 1:58 ` Jonathan Lundell
2003-03-06 7:18 ` Corvus Corax
2003-03-06 7:57 ` Ed Sweetman
2003-03-06 8:18 ` Corvus Corax
2003-03-06 8:58 ` Ed Sweetman
2003-03-06 15:41 ` Jesse Pollard
2003-03-06 14:27 ` Jesse Pollard
2003-03-06 2:57 ` David Rees
2003-03-06 6:12 ` Matthias Schniedermeyer
2003-03-06 16:07 ` Jonathan Lundell
2003-03-07 0:40 ` Horst von Brand
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=11E89240C407D311958800A0C9ACF7D1A33DCD@EXCHANGE \
--to=edv@macrolink.com \
--cc=corvusvcorax@gemia.de \
--cc=ed.sweetman@wmich.edu \
--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
all inboxes | Powered by JetHome®