cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: AthlonRob <AthlonRob@axpr.net>
To: cpufreq@www.linux.org.uk
Subject: Re: 2.4.21 Isn't working for me....
Date: 26 Aug 2003 12:43:47 -0700	[thread overview]
Message-ID: <1061927026.14523.9.camel@localhost> (raw)
In-Reply-To: <20030826064747.GE10585@poupinou.org>

On Mon, 2003-08-25 at 23:47, Ducrot Bruno wrote:

> The latest is again 2.4.22, _not_ 2.4.21.

That's the latest from the kernel.org repository, right?  the ones with
filenames like cpufreq-LINUX_2_4-20030825.tar.gz?

The codemonkeys ones, with filenames like cpufreq-2.4.21-1.gz are
against 2.4.21... right?  :-)

I would go ahead and just upgrade to 2.4.22, except I really need (ok, I
don't need, I just really want) preempt, low-latency scheduling, and the
latest NTFS drivers in this kernel... and 2.4.22 is still too new for
any of those to be available.  :-(

I suppose I could survive without cpu frequency scaling... but the
project looks *way super cool* to me.  :-)

Rob

  parent reply	other threads:[~2003-08-26 19:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26  4:36 2.4.21 Isn't working for me AthlonRob
2003-08-26  6:47 ` Ducrot Bruno
2003-08-26  9:26   ` Toula Michael
2003-08-26  9:53     ` Bas Mevissen
2003-08-26 11:29       ` Ducrot Bruno
2003-08-26 19:43   ` AthlonRob [this message]
2003-08-26 22:47     ` Luciano Miguel Ferreira Rocha
2003-08-27 11:11       ` Ducrot Bruno
2003-08-27 14:29         ` Luciano Miguel Ferreira Rocha
2003-08-27 14:39           ` Ducrot Bruno
2003-08-26 19:41 ` AthlonRob
2003-08-27 12:31   ` Ducrot Bruno
2003-08-27 15:55   ` Ducrot Bruno
2003-08-27 20:30     ` AthlonRob
2003-08-28  9:34       ` 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=1061927026.14523.9.camel@localhost \
    --to=athlonrob@axpr.net \
    --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