cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Francesco Poli <frx@firenze.linux.it>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Mon, 5 Apr 2004 23:11:31 +0200	[thread overview]
Message-ID: <20040405211131.GA7586@dominikbrodowski.de> (raw)
In-Reply-To: <20040405222015.4a560be1.frx@firenze.linux.it>


[-- Attachment #1.1: Type: text/plain, Size: 1794 bytes --]

On Mon, Apr 05, 2004 at 10:20:15PM +0200, Francesco Poli wrote:
> On Sun, 4 Apr 2004 23:11:44 +0200 Dominik Brodowski wrote:
> 
> > Well, it might be usefull for you and others if someone (you?) could
> > provide such up-to-date patches, and keeps 2.4. cpufreq up-to-date
> > with recent 2.6. developments, as far as the latter is possible.
> > However, none of the people currently active in cpufreq development
> > seem to have sufficient time to do so. In case _you_ want to do it [as
> > you said, it shouldn't be so difficult], please do so.
> 
> Perhaps it would be useful to setup a little script that
> 
> 1) downloads the latest 2.4.x kernel (maybe via rsync)
> 2) modifies it using latest cpufreq from
>    http://ftp.linux.org.uk/pub/linux/cpufreq/
> 3) creates the patch against the unmodified kernel
> 4) gzips it and moves the resulting file in the right place

IMHO, such a script can only work well if it is "being watched", e.g.
someone (you?) verifies the results equal what you expect. Also, differences
in the base kernel need to be tracked which might make adjustments of the
cpufreq files / patch necessary.

> Such a script should be run daily (via cron) on ftp.linux.org.uk
> 
> This could perhaps work and provide up-to-date patches, as long as 2.4.x
> cpufreq at http://ftp.linux.org.uk/pub/linux/cpufreq/ is kept up-to-date
> with 2.6.x

But assuming that this CVS export is up-to-date [which it isn't], why is
your script necessary?

> Perhaps patchin.sh should be modified in order to use cp (or mv) rather
> than ln -s

Modifying the patchin.sh script to become more user friendly is something
which can be done -- but _please_ be aware that 2.4. cpufreq is, at best, in
"beta" state and not as up to date as 2.6.

	Dominik

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  parent reply	other threads:[~2004-04-05 21:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 13:42 Help with Installation Ozeki San
2004-04-03 14:50 ` Bruno Ducrot
2004-04-03 15:16   ` Francesco Poli
2004-04-03 16:22     ` Russell King
2004-04-04 17:57       ` Francesco Poli
2004-04-04 21:11         ` Dominik Brodowski
2004-04-05 20:20           ` Francesco Poli
2004-04-05 21:06             ` Russell King
2004-04-06 21:01               ` Francesco Poli
2004-04-07  7:11                 ` Russell King
2004-04-07 20:26                   ` Francesco Poli
2004-04-05 21:11             ` Dominik Brodowski [this message]
2004-04-06  8:25               ` Bruno Ducrot
2004-04-06  8:47                 ` Bruno Ducrot
2004-04-06 21:50                   ` Francesco Poli
2004-04-07 16:18                     ` Bruno Ducrot
2004-04-06 21:48               ` Francesco Poli
2004-04-06 22:00                 ` Dominik Brodowski

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=20040405211131.GA7586@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=frx@firenze.linux.it \
    /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