From: Bruno Ducrot <ducrot@poupinou.org>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH 2.6] powernow-k7 acpi support.
Date: Tue, 10 Feb 2004 21:05:26 +0100 [thread overview]
Message-ID: <20040210200526.GI13262@poupinou.org> (raw)
In-Reply-To: <20040210180812.GA12634@redhat.com>
On Tue, Feb 10, 2004 at 06:08:12PM +0000, Dave Jones wrote:
> On Tue, Feb 10, 2004 at 10:03:20AM +0100, Dominik Brodowski wrote:
> > On Mon, Feb 09, 2004 at 07:58:31PM +0100, Bruno Ducrot wrote:
> > > Ok, you win. That one is ok ?
> >
> > Looks good as well. All we have to decide is where to call these functions,
> > though... and Davej has to decide whether he likes it, too :-)
>
> Looks good to me, though I'm missing the part where you wire this up
> to the rest of the code. I see two possibilities.
Well, that need to be decided at first. I'm acually testing it by
calling that function in powernow_decode_bios() with something like
that:
--- linux-2.6.3-bk-acpi/arch/i386/kernel/cpu/cpufreq/powernow-k7.c 2004/02/10 20:04:05 1.2
+++ linux-2.6.3-bk-acpi/arch/i386/kernel/cpu/cpufreq/powernow-k7.c 2004/02/10 20:05:12
@@ -426,6 +426,9 @@
unsigned int etuple;
unsigned int ret;
+ if (powernow_acpi_init() == 0)
+ return 0;
+
etuple = cpuid_eax(0x80000001);
etuple &= 0xf00;
etuple |= (c->x86_model<<4)|(c->x86_mask);
but I guess this is not what people want probably, especially if there
are good PST's.
> - fallback to acpi when we detect bad PST's.
That sound good.
> - module parameter to force usage of acpi (override PST)
Yes, or check if the laptop is blacklisted.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
prev parent reply other threads:[~2004-02-10 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 13:26 [PATCH 2.6] powernow-k7 acpi support Bruno Ducrot
2004-02-09 15:05 ` Dominik Brodowski
2004-02-09 15:20 ` Bruno Ducrot
2004-02-09 17:37 ` Bruno Ducrot
2004-02-09 17:50 ` Bruno Ducrot
2004-02-09 18:05 ` Dominik Brodowski
2004-02-09 18:29 ` Bruno Ducrot
2004-02-09 18:58 ` Bruno Ducrot
2004-02-10 9:03 ` Dominik Brodowski
2004-02-10 18:08 ` Dave Jones
2004-02-10 20:05 ` Bruno Ducrot [this message]
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=20040210200526.GI13262@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
/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.