From: Bas Mevissen <ml@basmevissen.nl>
To: Dominik Brodowski <linux@brodo.de>
Cc: Jan Rychter <jan@rychter.com>, Ducrot Bruno <ducrot@poupinou.org>,
cpufreq@www.linux.org.uk
Subject: Re: cpufreq CVS [Was: Re: cpufreq and P-IIIM]
Date: Tue, 19 Aug 2003 16:57:53 +0200 [thread overview]
Message-ID: <3F423AF1.90607@basmevissen.nl> (raw)
In-Reply-To: <20030818182137.GA2296@brodo.de>
Dominik Brodowski wrote:
>
Ah, I forgot about this information. Hence my misinterpretation of
Duncrot's submits.
> AFAICS,
> a) the 2.6. branch development is done in Dave's BK tree.
> b) 2.4-new [== backport of 2.6. to 2.4.] was never done in CVS,
> c) 2.4-ac tags exist, but because of b) are not kept up to date,
> d) depending on the outcome of the ARM and cpufreq-2.4. issue,
> 2.4-stable [which is CVS LINUX_2_4] is going to be deprecated soon.
>
> Also, it is my impression that an external CVS tree is used far less if a
> feature is merged into a mainline kernel. If it's not in the kernel, keeping
> track of a project without something like CVS is impossible. So I'm really
> glad about having had cpufreq-CVS and FTP-archives available. But, for the
> future, I don't see such a strong reason for keeping it.
>
Agree. Can you put the 2.4 backport in CVS? Then Duncrot's changes can
be merged in a structured manner.
Russell, can you update the documentation on
<http://www.arm.linux.org.uk/cvs/> for cpufreq when things have settled?
(this is just a proposal, please comment)
CPU clock frequency and voltage scaling for Linux, for x86 and ARM based
processors. This module provides a user-space and standard kernel-space
interface to these features, allowing ARM system-on-a-chip devices and
x86 platforms to cope with processor clock speed and cpu voltage
changes. Because not all combinations of clock speed and cpu voltage
changes are allowed, tables with valid combinations are included for
certain processors are included with the module.
Since the power consumed by a processor is directly related to the speed
and voltage at which it is running, keeping the clock speed and voltage
as low as possible allows you to get more run-time out of your battery
and lower the dissipation (heat) of your computer. Some people use this
to adjust their clock speed many times a second to optimise performance
vs battery life.
Most up to date documentation is included in the module directory
linux/Documentation/cpufreq
The following branches are available:
LINUX_2_4 - Stable older implementation for 2.4 kernels.
(might die soon)
LINUX_2_4_BACKPORT - Backport of 2.5/2.6 implementation
LINUX_2_5 - for 2.5 and upcoming 2.6 kernels. (main branch???)
(we could reuse LINUX_2_4 for the backport if the ARM guys don't need
the old implementation any more).
Regards,
Bas.
next prev parent reply other threads:[~2003-08-19 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 20:28 cpufreq and P-IIIM Jan Rychter
2003-08-18 11:29 ` Ducrot Bruno
2003-08-18 17:02 ` Jan Rychter
2003-08-18 18:07 ` Russell King
2003-08-18 18:21 ` cpufreq CVS [Was: Re: cpufreq and P-IIIM] Dominik Brodowski
2003-08-18 18:33 ` Russell King
2003-08-20 11:25 ` Ducrot Bruno
2003-08-20 17:30 ` Benjamin Herrenschmidt
2003-08-19 14:57 ` Bas Mevissen [this message]
2003-08-18 17:18 ` cpufreq and P-IIIM Jan Rychter
2003-08-19 8:03 ` Ducrot Bruno
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=3F423AF1.90607@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=jan@rychter.com \
--cc=linux@brodo.de \
/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.