From: Jan Rychter <jan@rychter.com>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: cpufreq and P-IIIM
Date: Mon, 18 Aug 2003 10:02:29 -0700 [thread overview]
Message-ID: <m2vfsux5ju.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <20030818112943.GD18032@poupinou.org> (Ducrot Bruno's message of "Mon, 18 Aug 2003 13:29:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
>>>>> "Ducrot" == Ducrot Bruno <ducrot@poupinou.org>:
Ducrot> On Sat, Aug 16, 2003 at 01:28:11PM -0700, Jan Rychter wrote:
>> Hi,
>>
>> I've just tried the latest 2.4 snapshot of cpufreq. Unfortunately,
>> it doesn't seem to work on my hardware. It says:
>>
>> cpufreq: Intel(R) SpeedStep(TM) support $Revision: 1.7.2.6 $
>> cpufreq: Intel(R) SpeedStep(TM) for this chipset not (yet)
>> available.
Ducrot> That version is way too old anyway.
Huh? That was the latest 2.4 snapshot that I was able to pull from
ftp.linux.org.uk: cpufreq-LINUX_2_4-20030816.tar.bz2.
If these are not the 'official' archives and the snapshots are outdated,
I'd humbly suggest pulling them off the net, because it confuses
people. I was pointed there to get my cpufreq for 2.4, after being
referred to www.codemonkey.org.uk which has never worked for me in the
last 3 weeks of trying.
[...]
Ducrot> Take a look at www.poupinou.org/cpufreq/
Thanks for the pointer.
--J.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-08-18 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 20:28 cpufreq and P-IIIM Jan Rychter
2003-08-18 11:29 ` Ducrot Bruno
2003-08-18 17:02 ` Jan Rychter [this message]
2003-08-18 18:07 ` Russell King
2003-08-18 18:21 ` cpufreq CVS [Was: Re: cpufreq and P-IIIM] Dominik Brodowski
2003-08-18 18:33 ` Russell King
2003-08-20 11:25 ` Ducrot Bruno
2003-08-20 17:30 ` Benjamin Herrenschmidt
2003-08-19 14:57 ` Bas Mevissen
2003-08-18 17:18 ` cpufreq and P-IIIM Jan Rychter
2003-08-19 8:03 ` 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=m2vfsux5ju.fsf@tnuctip.rychter.com \
--to=jan@rychter.com \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox