cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Alex Simonov <a_simonov@yahoo.com>
Cc: Ducrot Bruno <ducrot@poupinou.org>, cpufreq@www.linux.org.uk
Subject: Re: Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !
Date: Mon, 6 Oct 2003 21:00:57 +0100	[thread overview]
Message-ID: <20031006200057.GC1621@redhat.com> (raw)
In-Reply-To: <20031006153729.32725.qmail@web20806.mail.yahoo.com>

On Mon, Oct 06, 2003 at 08:37:29AM -0700, Alex Simonov wrote:

 > Thank you very much for the advice. I took the
 > powernow-k7.c from the CVS, and compiled it with
 > my "fake" PST. I had to fix only the missing
 > define for the wrmsrl and rdmsrl symbols. So far
 > the powernow scaling for my XP 1900+ seems to
 > work. 
 > Just one question-the x86info utility displays
 > either "Voltage changes wont happen" or Frequency
 > changes wont happen" depending on that if you're
 > changing the speed up or down, because of the
 > CVID and CFID bits set to 0 in each change_fid or
 > change_vid function? Does this mean that VID/FID
 > is not changing? The MSR register values are set
 > anyway, is there any definitive way to make sure
 > if I have the correct voltage output?

Add printk's to change_VID() ?

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

  reply	other threads:[~2003-10-06 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031001174844.GH11391@poupinou.org>
2003-10-06 15:37 ` Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed ! Alex Simonov
2003-10-06 20:00   ` Dave Jones [this message]
2003-10-07  9:31   ` Ducrot Bruno
2003-09-26 11:47 Release 1.00.08 of the AMD64 Frequency Driver paul.devriendt
2003-09-29 10:10 ` Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed ! Alex Simonov
2003-09-30  8:50   ` 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=20031006200057.GC1621@redhat.com \
    --to=davej@redhat.com \
    --cc=a_simonov@yahoo.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