From: Pavel Machek <pavel@ucw.cz>
To: paul.devriendt@amd.com
Cc: davej@redhat.com, pavel@ucw.cz, cpufreq@www.linux.org.uk,
linux@brodo.de, linux-kernel@vger.kernel.org
Subject: Re: Cleanups for powernow-k8
Date: Wed, 14 Jan 2004 01:03:52 +0100 [thread overview]
Message-ID: <20040114000352.GB25158@elf.ucw.cz> (raw)
In-Reply-To: <99F2150714F93F448942F9A9F112634C080EF392@txexmtae.amd.com>
Hi!
> I have a totally new driver, that I am hoping to release within about
> a month. (I did target the end of the year, but I got distracted on
> some other stuff). The new driver :
> - uses ACPI to figure out the available p-states. I have seen a *lot*
> of buggy BIOSs where the PSB/PST info is wrong or missing,
> - uses ACPI to handle battery / mains power transitions,
> and some other clean ups.
>
> I would appreciate some advice on a question ... should I leave the old
> non-ACPI capability there for those people who do not want to enable ACPI
> in the kernel ? If so, is this a big ifdef, or is there a better way to do
> it ? Or should I just say that it is dependent on ACPI, got to have
> ACPI ?
I have strange notebook here, and that one only works reasonably with
APM (with ACPI: no network IRQs, random mouse problems, random
shutdowns due to bad temperature readings).
I'd suggest to leave old driver there (possibly let me clean it up
;-)))), and create new powernow-k8-acpi, or powernow-acpi or something
like that.
Pavel
--
When do you have heart between your knees?
next prev parent reply other threads:[~2004-01-14 0:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 22:37 paul.devriendt
2004-01-13 23:06 ` Dave Jones
2004-01-14 9:33 ` Ducrot Bruno
2004-01-14 10:10 ` Dominik Brodowski
2004-01-14 15:21 ` Dave Jones
2004-01-14 0:03 ` Pavel Machek [this message]
2004-01-14 9:17 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 14:49 paul.devriendt
2004-01-14 15:08 ` Dominik Brodowski
2004-01-14 3:39 paul.devriendt
2004-01-14 3:42 ` Dave Jones
2004-01-14 9:01 ` Pavel Machek
2004-01-14 9:25 ` Dominik Brodowski
2004-01-14 9:11 ` Dominik Brodowski
2004-01-14 2:49 paul.devriendt
2004-01-14 3:33 ` Dave Jones
2004-01-14 10:24 ` Dominik Brodowski
2004-01-13 21:51 Pavel Machek
2004-01-13 21:59 ` Dave Jones
2004-01-13 23:59 ` Pavel Machek
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=20040114000352.GB25158@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=paul.devriendt@amd.com \
/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®