From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johnathan Hicks Subject: Re: CX > 1 support for Athlon SMP systems Date: Wed, 24 Jul 2002 22:39:07 -0400 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <3D3F64CB.80005@folkwolf.net> References: <3D3B879A.5020401@folkwolf.net> <1027351350.3d3c23363ea3d@carlthompson.net> <3D3CBF78.4010007@folkwolf.net> <1027461971.3d3dd353462e8@carlthompson.net> <3D3E14D9.50009@folkwolf.net> <1027536051.3d3ef4b31fef6@carlthompson.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: acpi-devel List-Id: linux-acpi@vger.kernel.org Carl Thompson wrote: > What I mean is I know the loop is executing, but how do I know the > processor is _really_ in C2? I was expecting a significant change in > batterly life and CPU temp vs. the C1 state that ACPI put my CPU in. > I haven't run definitive tests, but at best I'm only at most 15-20 > minutes more battery life (if any at all). What I would do is grab the data sheet(s) for the chipset in the laptop and compare what the code is doing with what you see in the docs. That's about as far as I can help you here, I'm rather busy unfortunately. :-( --John ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim