From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Dave Jones <davej@redhat.com>,
paul.devriendt@amd.com, pavel@ucw.cz, cpufreq@www.linux.org.uk,
linux-kernel@vger.kernel.org, mark.langsdorf@amd.com
Subject: Re: Cleanups for powernow-k8
Date: Wed, 14 Jan 2004 10:11:28 +0100 [thread overview]
Message-ID: <20040114091128.GA11159@dominikbrodowski.de> (raw)
In-Reply-To: <20040114034237.GT14674@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On Wed, Jan 14, 2004 at 03:42:37AM +0000, Dave Jones wrote:
> On Tue, Jan 13, 2004 at 09:39:53PM -0600, paul.devriendt@amd.com wrote:
> > >> Dave had a good idea of a minimal ACPI parser for trying to retrieve the
> > >> table of p-states from an ACPI BIOS without needing the full AML interpreter.
> > >> I will see if I can get that to work in powernow-k8-acpi
> > >
> > > If done properly, that parsing code could be shared by the K7
> > > driver too.
> >
> > Agreed. Function in a header file? Don't want the drivers attempting to
> > call each other at runtime.
>
> Works for me, or shove it out into its own .c file, and have both drivers link against it.
Guys, do you remember my acpi-perflib?[1] Currently, I'm rewriting it so that
it isn't so invasive and can be merged more easily during 2.x.[2] It's exactly
what you want as base for powernow-k7-acpi and powernow-k8-acpi driver.
However, as it relies on CONFIG_ACPI, an acpi-perflib-no-acpi module which
exports the same functions, but includes a minimal parser could be added.
But let's do the easy part (CONFIG_ACPI) first.
[1] http://marc.theaimsgroup.com/?l=acpi4linux&m=106547064228222&w=2
[patches are taken down from the website, though...]
[2] http://marc.theaimsgroup.com/?l=acpi4linux&m=107398568612489&w=2 is a
first step, another one will be sent out later today.
Dominik
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-14 9:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 14:49 paul.devriendt
2004-01-14 15:08 ` 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=20040114091128.GA11159@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
all inboxes | Powered by JetHome®