All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: Simon <simon@highlyillogical.org>
Cc: cpufreq@lists.arm.linux.org.uk
Subject: Re: newbie: Patch Confusion, P4 not supported?
Date: Wed, 18 Jun 2003 16:24:09 +0200	[thread overview]
Message-ID: <20030618142409.GI19556@poupinou.org> (raw)
In-Reply-To: <200306181245.07941.simon@highlyillogical.org>

On Wed, Jun 18, 2003 at 12:45:07PM +0100, Simon wrote:
> Hi,
> 
> Sorry about the dumb newbie question. Can't find any docs on this.
> 
> I just upgraded to a vanilla 2.4.21 kernel, and want to add cpufreq support 
> back for my Intel P4, in my Thinkpad A31p.
> 
> I had this working with 2.4.20, using the 'advanced' patch from 
> http://www.brodo.de/cpufreq/, and controlling it by echo-ing stuff to 
> /proc/cpufreq
> 
> I couldn't make any of the patches on www.brodo.de/cpufreq_old apply to my 
> kernel cleanly. They look rather old, and the page is no longer in use. So I 
> donloaded the latest patch from ftp://ftp.linux.org.uk/pub/linux/cpufreq/ 
> (ftp://ftp.linux.org.uk/pub/linux/cpufreq/cpufreq-LINUX_2_4-20030617.tar.bz2) 
> and applied this.

This is even more older than the one you downloaded from Dominik
site...  Try the latest ac in the meantime.

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  parent reply	other threads:[~2003-06-18 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 11:45 newbie: Patch Confusion, P4 not supported? Simon
2003-06-18 14:13 ` Dominik Brodowski
2003-06-18 17:36   ` Simon
2003-06-18 14:24 ` Ducrot Bruno [this message]
2003-06-18 14:22   ` Simon

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=20030618142409.GI19556@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@lists.arm.linux.org.uk \
    --cc=simon@highlyillogical.org \
    /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.