cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot@poupinou.org>
To: Alex Simonov <a_simonov@yahoo.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Custom powerstates table in powernow-K7 ?
Date: Mon, 20 Dec 2004 13:50:09 +0100	[thread overview]
Message-ID: <20041220125009.GN2140@poupinou.org> (raw)
In-Reply-To: <20041219105743.31456.qmail@web53908.mail.yahoo.com>

On Sun, Dec 19, 2004 at 02:57:43AM -0800, Alex Simonov wrote:
> Hi all,
> 
> Is there any simple way to use the powernow-k7
> driver with custom PST? Until now (kernel 2.6.3)
> I've always used to patch the module, hardwiring
> my own PST table for my Mobile Athlon XP 1900+,
> but with 2.6.8 kernels it seems more complex,
> with all this ACPI stuff added to it. It is not
> enough anymore to patch the 
> powernow_decode_bios (int maxfid, int startvid)
> function any more ..:(

At first, are you sure going with ACPI didn't help?  If that is the
case, I don't see the difficulty to do what you ask, especially if you
have already done such hack (ACPI is a fallback, so unless your laptop
is in a DMI blacklist, hacking powernow_decode_bios() should work).

> Could you give me some hints please? May be there
> is opportunity to pass it as a parameter to the
> cpufreq module? Or a way to integrate it in the
> initrd.img?

I'm afraid nobody will integrate that in mainline.

Cheers,

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2004-12-20 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 22:50 [ANNOUNCE] cpufrequtils-0.1 released Dominik Brodowski
2004-12-18 21:24 ` Harald Milz
2004-12-19 10:57   ` Custom powerstates table in powernow-K7 ? Alex Simonov
2004-12-20 12:50     ` Bruno Ducrot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-20 15:05 Nebojsa Trpkovic

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=20041220125009.GN2140@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=a_simonov@yahoo.com \
    --cc=cpufreq@www.linux.org.uk \
    /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