mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerald Britton <gbritton@alum.mit.edu>
To: Dave Jones <davej@suse.de>, Alan Cox <alan@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre9-ac3
Date: Fri, 31 May 2002 21:51:44 -0400	[thread overview]
Message-ID: <20020531215144.A4358@light-brigade.mit.edu> (raw)
In-Reply-To: <200205302322.g4UNMne06371@devserv.devel.redhat.com> <20020531014935.D9282@suse.de>

>  > Linux 2.4.19pre9-ac3
>  > o	Cpufreq updates			(Dominik Brodowski, Dave Jones0
>  > 	| Now includes some reverse engineered speedstep support 
> 
> Two points worth mentioning in regard to this.
> 1. The first type of speedstep (found in systems with BX chipsets)
>    isn't supported. Only the later type found in systems with ICH
>    chipsets will work with this driver..
> 2. Dominik did 99.9% of the Spudstop work, so all offers of free moneyi
>    should be directed to him.

This is on an IBM Thinkpad T23:

cpufreq: Intel(R) SpeedStep(TM) support $Revision: 1.7.2.2 $
cpufreq: chipset 0x3 - processor 0x2
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x0
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x0
cpufreq: writing 0x1 to pmbase 0x1000 + 0x50
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x1
cpufreq: change to 0 MHz succeded
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x1
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x1
cpufreq: writing 0x0 to pmbase 0x1000 + 0x50
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x0
cpufreq: change to 598 MHz succeded
cpufreq: read at pmbase 0x1000 + 0x50 returned 0x0
cpufreq: currently at high speed setting - 598 MHz
CPU clock: 598.500 MHz (731.500-598.500 MHz)

The low speed setting looks ok, but the high one is obviously wrong.
It's a 1.13Ghz CPU, /proc/cpuinfo lists it as this:

vendor_id	: GenuineIntel
cpu family	: 6
model		: 11
model name	: Intel(R) Pentium(R) III Mobile CPU      1133MHz
stepping	: 1
cpu MHz		: 1132.406
cache size	: 512 KB

The chipset in this machine is an Intel i830 chipset.  Let me know if
there's anything else useful I could do to provide further info.

				-- Gerald


  parent reply	other threads:[~2002-06-01  1:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30 23:22 Alan Cox
2002-05-30 23:49 ` Dave Jones
2002-05-31  8:31   ` Marcus Sundberg
     [not found]   ` <21223.1022847561@www56.gmx.net>
2002-05-31 12:26     ` Dominik Brodowski
2002-06-01  1:51   ` Gerald Britton [this message]
     [not found]   ` <10830.1022935054@www2.gmx.net>
2002-06-01 13:06     ` [PATCH] " Dominik Brodowski
2002-05-31  0:13 ` Robinson Maureira Castillo
     [not found] <200205310040.g4V0eZb25262@devserv.devel.redhat.com>
2002-05-31  0:57 ` Robinson Maureira Castillo
2002-05-31 13:37 Faisal Malallah
2002-05-31 15:47 ` Robert Love

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=20020531215144.A4358@light-brigade.mit.edu \
    --to=gbritton@alum.mit.edu \
    --cc=alan@redhat.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®