From: "Matt Sealey" <matt@genesi-usa.com>
To: "'Jon Loeliger'" <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: RE: cpu power "management" for non-dfs chips with no pmu (for instance, 750cxe and mpc7447 in pegasos)
Date: Fri, 23 Jun 2006 09:31:47 -0500 [thread overview]
Message-ID: <01cb01c696d1$c5192ad0$99dfdfdf@bakuhatsu.net> (raw)
In-Reply-To: <E1Ftmcb-0007rG-QS@jdl.com>
> You could start here:
> https://lists.osdl.org/mailman/listinfo/linux-pm
Hmm it says the certificate isn't valid :3
Maybe on Monday..
--
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
next prev parent reply other threads:[~2006-06-23 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 10:43 cpu power "management" for non-dfs chips with no pmu (for instance, 750cxe and mpc7447 in pegasos) Matt Sealey
2006-06-23 13:33 ` Jon Loeliger
2006-06-23 13:58 ` Matt Sealey
2006-06-23 14:26 ` Jon Loeliger
2006-06-23 14:31 ` Matt Sealey [this message]
2006-06-23 14:38 ` Raquel Velasco and Bill Buck
2006-06-23 23:49 ` Guennadi Liakhovetski
2006-06-24 16:16 ` Jon Loeliger
2006-06-24 17:29 ` Guennadi Liakhovetski
2006-06-27 22:47 ` Benjamin Herrenschmidt
2006-06-27 22:43 ` Benjamin Herrenschmidt
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='01cb01c696d1$c5192ad0$99dfdfdf@bakuhatsu.net' \
--to=matt@genesi-usa.com \
--cc=jdl@jdl.com \
--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).