From: Pavel Machek <pavel@ucw.cz>
To: Juhani Rautiainen <juhani.rautiainen@gmail.com>
Cc: "Brown, Len" <len.brown@intel.com>, Joerg Sommrey <jo@sommrey.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
tony@atomide.com, erik@slagter.name, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Wed, 8 Feb 2006 20:10:51 +0000 [thread overview]
Message-ID: <20060208201050.GA2353@ucw.cz> (raw)
In-Reply-To: <fad2c7740602030759i65e45a6as29964b8e90aeecd7@mail.gmail.com>
On Fri 03-02-06 17:59:38, Juhani Rautiainen wrote:
> On 2/3/06, Brown, Len <len.brown@intel.com> wrote:
> >
> >
> > Certainly the BIOS writer also had access to that document, plus
> > documents we do not see, yet they decided NOT to enable C2/C3.
>
> This comes from AMD-768 reveision guide. In product errata there there
> is errata number
> 24 which seems to suggest that you can't enable POS, C2 or C3 states
> in single processor
> environments. This at the end of errata:
> ----- snip ----
> This workaround will not work for awaking from the C2/C3 state, since
> the operating
> system has full control.
As far as I read this: they suggest to disable it in BIOS because
workaround is needed during wakeup and Windows do not have that
workaround. IOW the patch is safe, as long as workaround is
included. Good.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-02-09 17:06 UTC|newest]
Thread overview: 22+ 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 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:28 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-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=20060208201050.GA2353@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=erik@slagter.name \
--cc=jo@sommrey.de \
--cc=juhani.rautiainen@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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