Re: powernow-k8-acpi driver

[Bruno Ducrot <poup@poupinou.org>]

On Thu, Mar 04, 2004 at 01:07:54AM +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

Ahem, that's more Dominik work, not mine.

> >  > > 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..
> 
> Ahha. Unfortunately, cpufreq mailing lists are only available to list
> subscribers. Ouch.
> 

Yes.  But that a pretty low traffic mailing list anyway, and if really
you have to touch to cpufreq, even only for a single driver, you should
subscribe so that you know already of changes of cpufreq core which may
impact your driver.

For example, you may have a trouble with the new 'sticky bit' feature
with powernow-k8, especially if you want ACPI perflib included in your
driver.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.