From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: powernow-k8-acpi driver Date: Wed, 3 Mar 2004 22:48:41 +0000 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <20040303224841.GB16874@redhat.com> References: <20040303215435.GA467@elf.ucw.cz> <20040303222712.GA16874@redhat.com> <20040303223510.GE222@elf.ucw.cz> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20040303223510.GE222@elf.ucw.cz> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Pavel Machek Cc: Cpufreq mailing list , kernel list , davej@codemonkey.ork.uk, paul.devriendt@amd.com On Wed, Mar 03, 2004 at 11:35:10PM +0100, Pavel Machek wrote: > We could make that functionality depend on CONFIG_ACPI, and allow > runtime selection only if its defined... But those two drivers are > pretty different just now and acpi-dependend chunk is pretty big. (It > does funny stuff like polling for AC plug removal if we are in > high-power state and battery would not handle that. Old driver simply > refused to use high-power states on such machines.) you're aware of Dominik/Bruno's work on the 'acpilib'[1] stuff in this area right ? We'll need that anyway for Powernow-k7 and maybe longhaul too and its senseless duplicating this code. One thing is bugging me though. Whats wrong with the ACPI P-state cpufreq driver ? Does that not work these days ? It's been a long time since I even looked at it. Dave