cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Tue, 6 Apr 2004 23:48:43 +0200	[thread overview]
Message-ID: <20040406234843.6104733f.frx@firenze.linux.it> (raw)
In-Reply-To: <20040405211131.GA7586@dominikbrodowski.de>


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

On Mon, 5 Apr 2004 23:11:31 +0200 Dominik Brodowski wrote:

> 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.

OK, it's quite clear I misunderstood the role of
http://ftp.linux.org.uk/pub/linux/cpufreq/ tar archives...  :-(
I thought that these archives were there to provide the latest cpufreq
backport for 2.4.x kernels, and that one (following Bruno Ducrot's
instructions) would be able to use them to modify a 2.4.x kernel (and be
happy).
That is why I said that a kernel patch would be easier to apply.

If those archives are online for completely different purposes (which
ones?), I apologize for all the noise.

Now the question is: I would like to run the latest 2.4.x kernel with
cpufreq support, what do I do? 

> 
> > 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?

It would generate a kernel patch whose application is straightforward...
right?

> 
> > 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.

Of course, cpufreq cannot be backported from 2.6.x to 2.4.x by an
automatic script. That's a manual operation in any case. And one in
which I cannot help much[1], I'm afraid...

Notes:
[1] IANAKH: I am not a kernel hacker  :-( 

-- 
             |  GnuPG Key ID = DD6DFCF4 | You're compiling a program
  Francesco  |        Key fingerprint = | and, all of a sudden, boom!
     Poli    | C979 F34B 27CE 5CD8 DC12 |         -- from APT HOWTO,
             | 31B5 78F4 279B DD6D FCF4 |             version 1.8.0

[-- 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-06 21:48 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
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 [this message]
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=20040406234843.6104733f.frx@firenze.linux.it \
    --to=frx@firenze.linux.it \
    --cc=cpufreq@www.linux.org.uk \
    /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