cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Niko Ehrenfeuchter <ehrenfeu@informatik.uni-freiburg.de>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: ondemand and p3-m
Date: Sat, 21 Jan 2006 00:15:04 +0100	[thread overview]
Message-ID: <43D16EF8.3070502@tremplin-utc.net> (raw)
In-Reply-To: <1137795365.28411.30.camel@littledragon>

20.01.2006 23:16, Niko Ehrenfeuchter wrote/a écrit:
> Hi all,
> 
> I'm currently trying to get the ondemand-governor working with my PIII-M
> (1133 MHz). The system is a ThinkPad X24 using the Intel 830 chipset,
> kernel 2.6.15.1 with the corresponding (stable) acpi-patch.
> 
> While using the speedstep-ich module works for userspace stuff, echoing
> "ondemand" into scaling_governor simply yields an invalid argument
> error. Latency issue, I assume...? Turning on cpufreq's debug mode
> doesn't tell anything why it won't use the ondemand gov.
> 
> Looked through the archive for that issue, but I haven't been _that_
> successful, since it lacks some kind of search function... The only
> thing I've discovered was a thread in october where Eric Piel posted a
> patch for the first-generation 440BX speedstep. Is this patch included
> in the current kernel? Should it work for me too?
> 
> Any hints?
Hi!

Which driver do you use? Is it speedstep-ich? If so, it's now available 
in vanilla kernel since... 2.6.16-rc1, slightly too bleding edge for 
common mortals but it means it's coming soon!

If you don't want to wait, you can just apply the 2 patches of Mattia 
Dongili on a 2.6.15. ("Move PMBASE..." and "Measure transition latency 
at driver initialization" _updated_)

c u
Eric

  reply	other threads:[~2006-01-20 23:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 22:16 ondemand and p3-m Niko Ehrenfeuchter
2006-01-20 23:15 ` Eric Piel [this message]
2006-01-21  0:20   ` Niko Ehrenfeuchter
2006-01-21  8:09     ` Mattia Dongili
2006-01-20 23:59 ` Gunter Ohrner

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=43D16EF8.3070502@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=ehrenfeu@informatik.uni-freiburg.de \
    /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