From: Nigel Cunningham <ncunningham@linuxmail.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>,
Dominik Brodowski <linux@dominikbrodowski.de>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: cpufreq problem wrt suspend/resume on Athlon64
Date: Fri, 04 Feb 2005 10:34:04 +1100 [thread overview]
Message-ID: <1107473644.5727.6.camel@desktop.cunninghams> (raw)
In-Reply-To: <200502040015.22457.rjw@sisk.pl>
Hi.
On Fri, 2005-02-04 at 10:15, Rafael J. Wysocki wrote:
> Instead of trying to blow up the battery I used the patch that forces the CPU
> to 800 MHz and it apparently survives resuming on batteries - at least 3
> times out of 3 attempts (I'll try some times more tomorrow).
>
> It seems to boot at 1800 MHz, though, every time, according to
> cpufreq_resume().
Sounds like some good work. Is 800 the minimum for your laptop? I'm just
wondering how you know what speed to choose on other systems.
Regards,
Nigel
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574
next prev parent reply other threads:[~2005-02-03 23:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 13:28 cpufreq problem wrt suspend/resume on Athlon64 Rafael J. Wysocki
2005-02-02 13:31 ` Pavel Machek
2005-02-03 0:08 ` Rafael J. Wysocki
2005-02-03 10:41 ` Pavel Machek
2005-02-03 10:56 ` Dominik Brodowski
2005-02-03 10:58 ` Pavel Machek
2005-02-03 11:01 ` Dominik Brodowski
2005-02-03 11:30 ` Rafael J. Wysocki
2005-02-03 12:40 ` Dominik Brodowski
2005-02-03 13:20 ` Rafael J. Wysocki
2005-02-03 14:22 ` Pavel Machek
2005-02-03 23:15 ` Rafael J. Wysocki
2005-02-03 23:34 ` Nigel Cunningham [this message]
2005-02-03 23:52 ` Rafael J. Wysocki
2005-02-07 12:38 ` cpufreq problem wrt suspend/resume on Athlon64 [update] Rafael J. Wysocki
2005-02-03 14:20 ` cpufreq problem wrt suspend/resume on Athlon64 Pavel Machek
2005-02-03 21:46 ` Rafael J. Wysocki
2005-02-03 22:00 ` Pavel Machek
2005-02-03 23:37 ` Rafael J. Wysocki
2005-02-03 22:01 ` Pavel Machek
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=1107473644.5727.6.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.de \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.