From: Dominik Brodowski <linux@dominikbrodowski.de>
To: paul.devriendt@amd.com
Cc: davej@redhat.com, mark.langsdorf@amd.com,
cpufreq@www.linux.org.uk, pavel@ucw.cz,
linux-kernel@vger.kernel.org
Subject: Re: Cleanups for powernow-k8
Date: Wed, 14 Jan 2004 16:08:06 +0100 [thread overview]
Message-ID: <20040114150806.GA5137@dominikbrodowski.de> (raw)
In-Reply-To: <99F2150714F93F448942F9A9F112634C080EF3A4@txexmtae.amd.com>
[-- Attachment #1.1: Type: text/plain, Size: 1128 bytes --]
On Wed, Jan 14, 2004 at 08:49:18AM -0600, paul.devriendt@amd.com wrote:
> Absolutely. I am planning on using them also in the new ACPI based driver,
> along with your acpi-perflib.
Excellent.
> What is your progress on getting acpi-perflib merged into the kernel so that
> an additional patch is not needed ?
Unfortunately, it seems to be too invasive in the form it was proposed at
first. However, I'm currently in the process of getting the same
infrastructure[*] in place by doing small, logical, incremental changes to
drivers/acpi/processor.c. The first three patches are submitted to Len Brown
[1][2][3]; I haven't received a reply from him about these patches yet.
What helps in developing this is that I finally own a notebook
which supports ACPI P-States....
Dominik
[*] or almost the same infrastructure. The first two core patches assure
that
_PPC and passive cooling work.
[1] http://marc.theaimsgroup.com/?l=acpi4linux&m=107398569012495&w=2
[2] http://marc.theaimsgroup.com/?l=acpi4linux&m=107398568612489&w=2
[3] http://marc.theaimsgroup.com/?l=acpi4linux&m=107407671712989&w=2
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2004-01-14 15:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 14:49 Cleanups for powernow-k8 paul.devriendt
2004-01-14 15:08 ` Dominik Brodowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 3:39 paul.devriendt
2004-01-14 3:42 ` Dave Jones
2004-01-14 9:01 ` Pavel Machek
2004-01-14 9:25 ` Dominik Brodowski
2004-01-14 9:11 ` Dominik Brodowski
2004-01-14 2:49 paul.devriendt
2004-01-14 3:33 ` Dave Jones
2004-01-14 10:24 ` Dominik Brodowski
2004-01-13 22:37 paul.devriendt
2004-01-13 23:06 ` Dave Jones
2004-01-14 9:33 ` Ducrot Bruno
2004-01-14 10:10 ` Dominik Brodowski
2004-01-14 15:21 ` Dave Jones
2004-01-14 0:03 ` Pavel Machek
2004-01-14 9:17 ` Ducrot Bruno
2004-01-13 21:51 Pavel Machek
2004-01-13 21:59 ` Dave Jones
2004-01-13 23:59 ` Pavel Machek
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=20040114150806.GA5137@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=paul.devriendt@amd.com \
--cc=pavel@ucw.cz \
/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