mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Pavel Machek <pavel@suse.cz>
Cc: patches@x86-64.org, kernel list <linux-kernel@vger.kernel.org>,
	Cpufreq mailing list <cpufreq@www.linux.org.uk>,
	davej@redhat.com, paul.devriendt@amd.com
Subject: Re: powernow-k8 updates
Date: Sun, 14 Mar 2004 17:32:56 +0100	[thread overview]
Message-ID: <20040314163256.GA24433@dominikbrodowski.de> (raw)
In-Reply-To: <20040309214830.GA1240@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

On Wed, Mar 03, 2004 at 01:07:20PM +0100, Pavel Machek wrote:
> [Is it okay to post it to the lists for more testing and/or
> inclusion?]
                                                                                
I prefer patches to files to comment on.
                                                                                
> +config X86_POWERNOW_K8_ACPI
> +     tristate "AMD Opteron/Athlon64 PowerNow! using ACPI"
> +     depends on CPU_FREQ && EXPERIMENTAL
depends on ... && ACPI ?
                                                                                
See also the other mail discussing how to handle the two methods to detect
speed.
                                                                                
Unfortunately, I consider this new ACPI driver to be in an "unmergeable"
state, as the extra "polling" is unneccessary if the ACPI perflib is used,
the extra parsing of ACPI tables can fail much too easily, and the whole
driver is too fragile with regard to ACPI interaction.

	Dominik

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-03-14 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 21:48 Pavel Machek
2004-03-10 11:09 ` Bruno Ducrot
2004-03-10 11:32   ` Pavel Machek
2004-03-10 13:48     ` Bruno Ducrot
2004-03-14 16:33       ` Dominik Brodowski
2004-03-14 16:32 ` Dominik Brodowski [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=20040314163256.GA24433@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@x86-64.org \
    --cc=paul.devriendt@amd.com \
    --cc=pavel@suse.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®