From: Ed Sweetman <safemode2@comcast.net>
To: Joshua Hoblitt <jhoblitt@ifa.hawaii.edu>
Cc: Dave Jones <davej@redhat.com>, Duane Griffin <duaneg@dghda.com>,
Prakash Punnoor <prakash@punnoor.de>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Drake <dsd@gentoo.org>
Subject: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
Date: Fri, 18 May 2007 00:09:38 -0400 [thread overview]
Message-ID: <464D2702.1060001@comcast.net> (raw)
In-Reply-To: <20070518030436.GB20793@ifa.hawaii.edu>
the previous post i keep referring you to has a patch that was mangled
...here is the non-mangled version
--- ./linux-backup/arch/x86_64/kernel/cpufreq/Kconfig 2007-02-04
13:44:54.000000000 -0500
+++ ./linux-2.6.21-rc5-mm2/arch/x86_64/kernel/cpufreq/Kconfig
2007-05-17 18:13:07.000000000 -0400
@@ -10,20 +10,27 @@
comment "CPUFreq processor drivers"
-config X86_POWERNOW_K8
+config X86_POWERNOW_K8
tristate "AMD Opteron/Athlon64 PowerNow!"
select CPU_FREQ_TABLE
help
This adds the CPUFreq driver for mobile AMD Opteron/Athlon64
processors.
+ An acpi interface is available if acpi support has been selected.
+ This is required for multi-socket and other systems but not
necessarily required for UP single socket systems.
For details, take a look at <file:Documentation/cpu-freq/>.
If in doubt, say N.
config X86_POWERNOW_K8_ACPI
- bool
- depends on X86_POWERNOW_K8 && ACPI_PROCESSOR
- depends on !(X86_POWERNOW_K8 = y && ACPI_PROCESSOR = m)
+ bool "ACPI Support"
+ select ACPI_PROCESSOR
+ depends on X86_POWERNOW_K8
+ help
+ This provides access to the acpi tables for full p-state
functionality. This driver is also required
+ for cpufreq to work with multi-socket and other smp systems.
+
+ It is safe to say Y here.
default y
config X86_SPEEDSTEP_CENTRINO
next prev parent reply other threads:[~2007-05-18 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 1:17 [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver Joshua Hoblitt
2007-05-16 14:55 ` Chuck Ebbert
2007-05-16 16:24 ` Dave Jones
2007-05-16 18:38 ` Prakash Punnoor
2007-05-16 19:53 ` Duane Griffin
2007-05-16 20:04 ` Daniel Drake
2007-05-16 21:27 ` Joshua Hoblitt
2007-05-16 22:39 ` Ed Sweetman
2007-05-16 23:18 ` Daniel Drake
2007-05-16 23:37 ` Ed Sweetman
2007-05-16 20:48 ` Dave Jones
2007-05-18 3:04 ` Joshua Hoblitt
2007-05-18 4:07 ` Ed Sweetman
2007-05-18 4:09 ` Ed Sweetman [this message]
2007-05-18 16:01 ` Dave Jones
2007-05-22 2:47 ` Joshua Hoblitt
2007-05-29 20:51 ` Dave Jones
2007-05-29 23:35 ` Daniel Drake
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=464D2702.1060001@comcast.net \
--to=safemode2@comcast.net \
--cc=davej@redhat.com \
--cc=dsd@gentoo.org \
--cc=duaneg@dghda.com \
--cc=jhoblitt@ifa.hawaii.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
/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.