public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Troller <patrol@sinus.cz>
To: Erik Slagter <erik@slagter.name>
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Fri, 3 Feb 2006 11:31:27 +0100	[thread overview]
Message-ID: <20060203103127.GA17072@tangens.sinus.cz> (raw)
In-Reply-To: <1138959312.18273.14.camel@localhost.localdomain>

> > Certainly the BIOS writer also had access to that document, plus
> > documents we do not see, yet they decided NOT to enable C2/C3.
> 
> You are probably right, but I remain suspicious that the BIOS writers
> simply didn't want to go through the trouble of implementing and testing
> the whole thing, presumable because:
>...
> If I remember correctly there was some sort of windows driver supplied
> with the board to enable power saving. This would suggest that in
> principle there is no reason it cannot work.
> 
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 :-((( ).
  I have EXACTLY the same problem with my Clevo D610SU notebook. It's a SIS
chipset with Intel P4/2G4. In Linux, it's surface is always warm, the fan
is starting every moment even in the full idle. 6000 mAh accu can power it
for 45 mins. The same hardware on windoze with a driver supplied on the CD
which came with the notebook is cold all the time (ok, in idle), the fans
start on a heavy load only, and the battery is enough for 2.5 - 3 hours.
  And yes, in RSDT, L2_LAT is 101 and L3_LAT is 1001, just for being disabled.
  I even patched Linux to accept them. It is not fatal. C2 is used, C3 isn't
because of lack of BM capabilities, but there is NO CHANGE in the power
consumption :-(. I even use dyntick to maximize the power saving. 
  Does anybody a clue, what to do in this case ? 
                                          With regards, Pavel Troller

  reply	other threads:[~2006-02-03 10:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  8:45 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Brown, Len
2006-02-03  9:35 ` Erik Slagter
2006-02-03 10:31   ` Pavel Troller [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:40 Brown, Len
2006-02-04 10:31 ` Erik Slagter
2006-02-04 10:49   ` Pavel Troller
2006-02-03 18:28 Brown, Len
2006-02-03 18:20 Brown, Len
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=20060203103127.GA17072@tangens.sinus.cz \
    --to=patrol@sinus.cz \
    --cc=erik@slagter.name \
    /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