linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: iBook G3 owners
Date: Sun, 10 Apr 2005 09:28:22 +0100	[thread overview]
Message-ID: <1113121703.12012.70.camel@baythorne.infradead.org> (raw)
In-Reply-To: <1113091621.9518.450.camel@gaston>

On Sun, 2005-04-10 at 10:07 +1000, Benjamin Herrenschmidt wrote:
> Can you check that you have the very latest versions of these
> patches ?
> I updated them a couple of time since I posted the message...

The md5sums of the patches I have precisely match the md5sums of the
patches which are currently up for download:

fc63b0d57d26f2dec44d0ba1667eb263  linux-2.6.11-ppc32-pmac-sleep-fix.patch
29792fdd1970b9447d06a2bb044e48e0  linux-2.6.11-cpufreq-add-suspend.patch
dcdb468b9325c1835e9992034b7d8a28  linux-2.6.11-ppc32-750-erratum-fix.patch
689353b33f3bdc7759692a4cccdb24fa  linux-2.6.11-ppc32-cpufreq-gpio-off.patch

A kernel without _any_ of these patches survived an overnight sleep, and
in fact cpufreq was working again too. I'll try with just the cpufreq
patches.

-- 
dwmw2

      reply	other threads:[~2005-04-10  8:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  6:06 iBook G3 owners Benjamin Herrenschmidt
2005-04-04 12:06 ` 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 [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=1113121703.12012.70.camel@baythorne.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=benh@kernel.crashing.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).