All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Bjoern Schmidt <lucky21@uni-paderborn.de>, linux-kernel@vger.kernel.org
Subject: Re: fsb of older cpu
Date: Mon, 08 Mar 2004 22:14:48 +0100	[thread overview]
Message-ID: <404CE248.4050002@stesmi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0403081545200.29087@montezuma.fsmlabs.com>

Zwane Mwaikambo wrote:

> On Mon, 8 Mar 2004, Bjoern Schmidt wrote:
> 
> 
>>Hello and thank you for your answer. I determined that this cpu has a fsb of
>>66MHz. The reason for my question was that i want to underclock the cpu.
>>I think it would be better to change the multiplier instead of changing the fsb.
>>Therefore i read the msr register 0x02ah, tilted bit 27 and wrote it back, but
>>the cpu clock is still the same. Why does that not work? Is it possible to
>>change the multiplier at runtime at all?
> 
> 
> No, the multiplier is locked, you'll have more luck fiddling with the
> front side bus.

That would be the first P2/233 with a locked multiplier I've come
across. My P2's ranging from 233 to 350 were never multiplier locked
anyway. Celerons and P3's were multiplier locked however, maybe that's
what you're thinking about.

// Stefan

  reply	other threads:[~2004-03-08 21:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 10:38 fsb of older cpu Bjoern Schmidt
2004-03-08 16:14 ` Bernd Schubert
2004-03-08 20:17   ` Bjoern Schmidt
2004-03-08 20:46     ` Zwane Mwaikambo
2004-03-08 21:14       ` Stefan Smietanowski [this message]
2004-03-08 23:06         ` Zwane Mwaikambo
2004-03-08 21:09     ` Stefan Smietanowski
2004-03-08 21:53       ` Bjoern Schmidt
     [not found] <A6974D8E5F98D511BB910002A50A6647615F47CB@hdsmsx402.hd.intel.com>
2004-03-09  6:58 ` Len Brown
2004-03-09 11:16   ` Bjoern Schmidt
2004-03-09 11:35     ` Stefan Smietanowski
2004-03-09 12:07       ` Bjoern Schmidt
2004-03-10  4:17     ` Len Brown

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=404CE248.4050002@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucky21@uni-paderborn.de \
    --cc=zwane@linuxpower.ca \
    /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.