public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: hpa@transmeta.com, linux-kernel@vger.kernel.org,
	cpufreq@www.linux.org.uk
Subject: cpufreq for 2.5.36 now available
Date: Thu, 19 Sep 2002 10:58:41 +0200	[thread overview]
Message-ID: <20020919105841.A1586@brodo.de> (raw)

Hi!

Updated patches for CPU frequency and voltage scaling support are now
available at

http://www.brodo.de/cpufreq/

Changes since the version submitted on lkml for 2.5.35:
- Documentation fixes (Hollis Blanchard, Xavier Bestel)
- longrun.c 0% performance does not mean 0 MHz but lowest available frequency


complete patch for kernel 2.5.36:
http://www.brodo.de/cpufreq/cpufreq-2.5.36-1.gz

step-by-step patches for kernel 2.5.36:
http://www.brodo.de/cpufreq/cpufreq-2.5.36-core-1
http://www.brodo.de/cpufreq/cpufreq-2.5.36-i386-core-1
http://www.brodo.de/cpufreq/cpufreq-2.5.36-i386-drivers-1
http://www.brodo.de/cpufreq/cpufreq-2.5.36-doc-1
http://www.brodo.de/cpufreq/cpufreq-2.5.36-24api-1

backport to kernel 2.4.19/2.4.20-pre7:
http://www.brodo.de/cpufreq/cpufreq-2.4.19-3.gz
http://www.brodo.de/cpufreq/cpufreq-2.4.20-pre7-3.gz

This cpufreq version is included in 2.4.-ac patchsets since
2.4.20-pre7-ac1, a few updates for -ac2 can be found here:
http://www.brodo.de/cpufreq/cpufreq-2.4.20-pre7-ac2-1

Comments welcome; please ensure that the cpufreq development list at
cpufreq@www.linux.org.uk receives a copy of all comments.


	Dominik

                 reply	other threads:[~2002-09-19  8:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020919105841.A1586@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=hpa@transmeta.com \
    --cc=linux-kernel@vger.kernel.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