Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422913AbWBIRG2 (ORCPT ); Thu, 9 Feb 2006 12:06:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965242AbWBIRG1 (ORCPT ); Thu, 9 Feb 2006 12:06:27 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:37643 "EHLO spitz.ucw.cz") by vger.kernel.org with ESMTP id S965239AbWBIRG0 (ORCPT ); Thu, 9 Feb 2006 12:06:26 -0500 Date: Wed, 8 Feb 2006 20:10:51 +0000 From: Pavel Machek To: Juhani Rautiainen Cc: "Brown, Len" , Joerg Sommrey , Andrew Morton , 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 Message-ID: <20060208201050.GA2353@ucw.cz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1097 Lines: 30 On Fri 03-02-06 17:59:38, Juhani Rautiainen wrote: > On 2/3/06, Brown, Len 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! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/