From: Voluspa <lista1@telia.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference
Date: Tue, 26 Jul 2005 16:53:32 +0200 [thread overview]
Message-ID: <20050726165332.022f5a02.lista1@telia.com> (raw)
In-Reply-To: <20050726131439.GB2134@ucw.cz>
On Tue, 26 Jul 2005 15:14:39 +0200 Vojtech Pavlik wrote:
> This almost looks like a regular Athlon 64, not even the mobile
> version. I wouldn't expect very big deep sleep capabilities on that
> one. You can check the
>
> /proc/acpi/processor/CPU1/power
>
> file for the list of C states. A normal Athlon64 will likely have only
> C0. Mobile chips can go up to C4, which is really deep sleep.
You've probably already seen that /proc/acpi/processor/CPU1/power lists
C1 only here. Ok, with your input regarding normal CPUs I'm inclined
to believe ACPI is correct in my case. Still, I'll learn/read the code.
Always have had a need to finish those long marches.
Mvh
Mats Johannesson
--
next prev parent reply other threads:[~2005-07-26 14:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 18:04 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference Voluspa
2005-07-21 18:14 ` Jesper Juhl
2005-07-21 18:33 ` Voluspa
2005-07-22 14:48 ` Pavel Machek
2005-07-22 17:15 ` Voluspa
2005-07-22 18:02 ` Pavel Machek
2005-07-22 18:28 ` Voluspa
2005-07-22 18:44 ` Voluspa
2005-07-25 10:21 ` Tony Lindgren
2005-07-25 18:30 ` Bill Davidsen
2005-07-21 18:49 ` Guillaume Chazarain
2005-07-21 19:01 ` Voluspa
2005-07-26 13:14 ` Vojtech Pavlik
2005-07-26 14:53 ` Voluspa [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 5:23 Brown, Len
2005-07-26 14:52 ` Bill Davidsen
2005-07-26 6:29 Voluspa
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=20050726165332.022f5a02.lista1@telia.com \
--to=lista1@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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