cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Hiroshi Miura <miura@da-cha.org>,
	Ducrot Bruno <ducrot@arm.linux.org.uk>,
	cpufreq@www.linux.org.uk
Subject: Re: SpeedStep New Driver for Pentium III (-M) using SMI interface
Date: Tue, 2 Sep 2003 16:54:52 +0200	[thread overview]
Message-ID: <20030902145452.GA8512@brodo.de> (raw)
In-Reply-To: <20030902123538.GR4401@poupinou.org>

Fantastic, speedstep finally works on my notebook!!! Wow... Congratulations
to Bruno Ducrot and Hiroshi Miura. 

On Tue, Sep 02, 2003 at 02:35:38PM +0200, Ducrot Bruno wrote:
> On Tue, Sep 02, 2003 at 10:31:50AM +0200, Dominik Brodowski wrote:
> > Thanks for this very interesting work. Unfortunately, it doesn't work on my
> > aged notebook, but well, the GPO driver didn't work either....
> > 
> 
> Dominik, the command is 0x80 for you, but actually it should be 0x82.
> I do have the exact same trouble with my toshiba.  Try then to pass
> the correct option in order to overide that value.  Unfortunately, I
> don't have my toshiba handy (even though it is ICH based, it
> may be usefull to play with).

0x82 was one part of the story...
 
> The flags stuff is not actually exploited.
> For mine (and for Dominik) it is 0x07d00100
> whereas Miura-san is 0x0x07d00000
> 
> When I receive report from speedstep-detect (and also send
> something called speedtep-bios privatly), if bit 8 == 1, then it do not
> work, but I don't have the ownership stuff, though.  When that
> bit is 0, it may or may not work.  I think it is related to 
> state on battery.
> 
> More related to the driver: I don't see any special reason to disable
> interrupts in-between the smi call when setting the state.  Also,
> you don't use the speedstep_get_freqs, but use a SMI function for
> that (which is probably more usefull), therefore, there is no
> need to do the notification stuff (it was done only at _init stage,
> and to avoid duplicating codes).

the other part of the story is here: the speedstep_smi_get_freqs call does
not work on my system -- it returns the ist_info.signature as result, and
"0" and "4" as high and low frequency which is obviously bogus. Replacing it
with hard-coded values for testing made it go -- BTW, GPO 0 did indeed
change again, but changing GPO _alone_ [which is what the speedstep-piix4
module does] did not work.

	Dominik

  reply	other threads:[~2003-09-02 14:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02  4:36 SpeedStep New Driver for Pentium III (-M) using SMI interface Hiroshi Miura
2003-09-02  5:35 ` Norbert Preining
2003-09-03  4:02   ` Hiroshi Miura
2003-09-03  5:58     ` Norbert Preining
2003-09-03  7:31     ` Ducrot Bruno
2003-09-02  8:18 ` Ducrot Bruno
2003-09-02  8:31 ` Dominik Brodowski
2003-09-02  8:42   ` Ducrot Bruno
2003-09-02 12:35   ` Ducrot Bruno
2003-09-02 14:54     ` Dominik Brodowski [this message]
2003-09-02 17:02       ` Ducrot Bruno
2003-09-03  7:57       ` Ducrot Bruno
2003-09-03  9:06         ` Dominik Brodowski
2003-09-03  7:33   ` Ducrot Bruno
2003-09-02 15:13 ` Dominik Brodowski
2003-09-04 12:42 ` Ducrot Bruno
2003-09-04 13:13   ` Hiroshi Miura
2003-09-04 15:34     ` 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=20030902145452.GA8512@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@arm.linux.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=miura@da-cha.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