From: Erik Slagter <erik@slagter.name>
To: "Brown, Len" <len.brown@intel.com>
Cc: Pavel Troller <patrol@sinus.cz>, linux-acpi@vger.kernel.org
Subject: RE: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Sat, 04 Feb 2006 11:31:36 +0100 [thread overview]
Message-ID: <1139049096.23009.17.camel@localhost.localdomain> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005F343AE@hdsmsx401.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Fri, 2006-02-03 at 13:40 -0500, Brown, Len wrote:
> >> If I remember correctly there was some sort of windows
> >>driver supplied
>
> >>
> >EXACTLY. It is the main problem. I'm afraid that BIOS writers
> >are writing just the basic part, and they hope that the rest will be done by the OS
> >driver (which they eventually also supply, but just for the "majority"
> >OS :-((( ).
>
> Please measure the A/C power running Windows and measure the power
> running Linux and report back if they are different.
That would really be interesting. And I do have a power meter, it says
that putting the processors in C2 really does save ~70 watts, running
linux. I cannot test it for windows though, I do not have a license, nor
the install CD's nor any spare room on the disks to put it on :-(. So I
hope somebody else does...
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]
next prev parent reply other threads:[~2006-02-04 10:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 18:40 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Brown, Len
2006-02-04 10:31 ` Erik Slagter [this message]
2006-02-04 10:49 ` Pavel Troller
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:28 Brown, Len
2006-02-03 18:20 Brown, Len
2006-02-03 8:45 Brown, Len
2006-02-03 9:35 ` Erik Slagter
2006-02-03 10:31 ` Pavel Troller
2006-02-03 14:16 ` Joerg Sommrey
2006-02-03 15:59 ` Juhani Rautiainen
2006-02-03 17:02 ` Erik Slagter
2006-02-08 20:10 ` Pavel Machek
2006-02-02 22:24 Joerg Sommrey
2006-02-02 22:37 ` Andrew Morton
2006-02-03 7:03 ` Joerg Sommrey
2006-02-02 22:43 ` Dave Jones
2006-02-02 1:35 Brown, Len
2006-02-02 1:50 ` Alan Cox
2006-02-02 9:50 ` Erik Slagter
2006-02-02 19:38 ` Tony Lindgren
2006-02-03 9:21 ` Erik Slagter
2006-02-03 9:33 ` Pavel Troller
2006-02-03 9:39 ` Erik Slagter
2006-02-03 10:14 ` Pavel Troller
2006-02-03 10:28 ` Erik Slagter
2006-02-01 18:11 Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40 ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey
2006-01-31 18:55 Joerg Sommrey
2006-02-01 3:34 ` Andrew Morton
2006-02-01 10:25 ` Erik Slagter
2006-02-01 17:20 ` Tony Lindgren
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=1139049096.23009.17.camel@localhost.localdomain \
--to=erik@slagter.name \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=patrol@sinus.cz \
/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