public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: 2.4.19-pre10-ac1: Hardcoded cpu_khz in powernow-k6.c
Date: Wed, 5 Jun 2002 03:02:23 +0200	[thread overview]
Message-ID: <20020605030223.A5277@suse.de> (raw)
In-Reply-To: <Pine.NEB.4.44.0206050236260.9994-100000@mimas.fachschaften.tu-muenchen.de>

On Wed, Jun 05, 2002 at 02:52:15AM +0200, Adrian Bunk wrote:
 > Hi Dave,
 > 
 > while reading through powernow-k6.c in 2.4.19-pre10-ac1 I found the
 > following that seems to be a bug:
 > 
 >   static unsigned long cpu_khz=350000;
 > 
 > Not every K6-2/3 runs at 350 MHz...

iirc, there aren't any MSRs[*] on the K6-2 where we can read
the current FSB.  I think 350MHz was used as it was probably
the slowest K6-2 to be found at the time.  You can override
it with boot time arguments.

    Dave.

[*] The K6 style powernow was reverse engineered, as there were
no publically available documents explaining it. All we can
do is scale multipliers. No voltage scaling, no FSB decoding.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-06-05  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  0:52 2.4.19-pre10-ac1: Hardcoded cpu_khz in powernow-k6.c Adrian Bunk
2002-06-05  1:02 ` Dave Jones [this message]
2002-06-05  6:04   ` Adrian Bunk

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=20020605030223.A5277@suse.de \
    --to=davej@suse.de \
    --cc=arjanv@redhat.com \
    --cc=bunk@fs.tum.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