From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: iBook G3 owners
Date: Mon, 04 Apr 2005 16:06:23 +1000 [thread overview]
Message-ID: <1112594783.26086.22.camel@gaston> (raw)
Hi !
There have been various reports of issues with sleep among others on
iBook G3 equiped with the 750FX processor. Also, the cpufreq code on
these so far didn't change the CPU voltage, which limited the actual
power saving at low frequency.
I have uploaded various patches that should help fix these issues. Those
patches are all against current linus bk and they should be all applied
in the order below.
I would really appreciate some tests as I don't have access to any of
these machines. I need to know if cpufreq works reliably with those
patches and if the new voltage control makes any differnece on battery
life (check power consumption in /proc/pmu/battery_*/current when
running on battery) and I need to know if the patches are improving
reliability of sleep/wakeup.
The 4 patches can be found at these URLs. If you had earlier versions of
some of these, those patches replace them:
http://gate.crahsing.org/~benh/ppc32-750-errata-fix.diff
http://gate.crahsing.org/~benh/ppc32-pmac-sleep-fix.diff
http://gate.crahsing.org/~benh/cpufreq-add-suspend.diff
http://gate.crahsing.org/~benh/ppc32-cpufreq-gpio-off.diff
Please, let me know asap,
Ben.
next reply other threads:[~2005-04-04 6:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 6:06 Benjamin Herrenschmidt [this message]
2005-04-04 12:06 ` iBook G3 owners Benjamin Herrenschmidt
2005-04-07 22:05 ` Andreas Schwab
2005-04-07 22:38 ` Benjamin Herrenschmidt
2005-04-07 23:20 ` Andreas Schwab
2005-04-07 23:42 ` Benjamin Herrenschmidt
2005-04-09 16:36 ` David Woodhouse
2005-04-09 23:37 ` Benjamin Herrenschmidt
2005-04-09 23:48 ` David Woodhouse
2005-04-10 0:07 ` Benjamin Herrenschmidt
2005-04-10 8:28 ` David Woodhouse
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=1112594783.26086.22.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).