public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Johnathan Hicks <thetech-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
To: acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: CX > 1 support for Athlon SMP systems
Date: Wed, 24 Jul 2002 22:39:07 -0400	[thread overview]
Message-ID: <3D3F64CB.80005@folkwolf.net> (raw)
In-Reply-To: 1027536051.3d3ef4b31fef6@carlthompson.net

Carl Thompson wrote:
<SNIP>
> 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

      reply	other threads:[~2002-07-25  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D3B879A.5020401@folkwolf.net>
     [not found] ` <1027351350.3d3c23363ea3d@carlthompson.net>
     [not found]   ` <3D3CBF78.4010007@folkwolf.net>
     [not found]     ` <3D3CBF78.4010007-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-07-23 22:06       ` CX > 1 support for Athlon SMP systems Carl Thompson
2002-07-24  2:45         ` Johnathan Hicks
     [not found]           ` <3D3E14D9.50009-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-07-24 18:40             ` Carl Thompson
2002-07-25  2:39               ` Johnathan Hicks [this message]

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=3D3F64CB.80005@folkwolf.net \
    --to=thetech-pn2jtpibvork1umjsbkqmq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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