From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: powernow-k8-acpi driver Date: Wed, 3 Mar 2004 23:36:04 +0000 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <20040303233603.GA18722@redhat.com> References: <20040303215435.GA467@elf.ucw.cz> <20040303222712.GA16874@redhat.com> <20040303223510.GE222@elf.ucw.cz> <20040303224841.GB16874@redhat.com> <20040303225405.GF222@elf.ucw.cz> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20040303225405.GF222@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:54:05PM +0100, Pavel Machek wrote: > Hi! > > > > 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. > > That [1] looks like promise of url, but I don't see that url. Hmm, cpufreq mailing list archives are your best bet. What I meant to add was.. [1] acpilib is a made up name I just came up with, I've no idea what the guys who wrote it are referring to it as. Dave