cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: shane@bogomip.com
To: Eric Altendorf <EricAltendorf@orst.edu>
Cc: cpufreq@www.linux.org.uk
Subject: Re: CPU-freq for 2.4.21 kernels
Date: Tue, 29 Jul 2003 07:47:16 -0600	[thread overview]
Message-ID: <20030729134716.GA27983@bogomip.com> (raw)
In-Reply-To: <200307281216.58545.EricAltendorf@orst.edu>

patch with 2.4.21-ac4, or follow the directinos for patching with -ck1

either one patches in cpufreq support

On Mon, Jul 28, 2003 at 12:16:58PM -0700, Eric Altendorf wrote:
> 
> Is there a patch for CPU-freq for 2.4.21 vanilla kernels?  I haven't 
> been able to find one.
> 
> To get working swsusp I had to move back from 2.5 to 2.4 but I miss 
> scaling for my crusoe laptop....
> 
> Please reply direct as I am not on this list.  Thanks much!
> 
> Eric
> 
> _______________________________________________
> Cpufreq mailing list
> Cpufreq@www.linux.org.uk
> http://www.linux.org.uk/mailman/listinfo/cpufreq
> 

      reply	other threads:[~2003-07-29 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 19:16 CPU-freq for 2.4.21 kernels Eric Altendorf
2003-07-29 13:47 ` shane [this message]

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=20030729134716.GA27983@bogomip.com \
    --to=shane@bogomip.com \
    --cc=EricAltendorf@orst.edu \
    --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