public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: paul.devriendt@amd.com
Cc: pavel@ucw.cz, cpufreq@www.linux.org.uk, linux@brodo.de,
	linux-kernel@vger.kernel.org
Subject: Re: Cleanups for powernow-k8
Date: Tue, 13 Jan 2004 23:06:05 +0000	[thread overview]
Message-ID: <20040113230605.GM14674@redhat.com> (raw)
In-Reply-To: <99F2150714F93F448942F9A9F112634C080EF392@txexmtae.amd.com>

On Tue, Jan 13, 2004 at 04:37:13PM -0600, paul.devriendt@amd.com wrote:

 > 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,

I've seen a ridiculous amount of broken PST's from folks running the K7 driver
too. Given the complete lack of help from some vendors[1], I think I might
add a minimal ACPI parser there too when I get time, as an alternative
source of info when the PST is obviously crap.

 > 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 ?

Part of the justification for cpufreq (at least on x86) was an alternative
for when ACPI just doesn't work, or for when folks either don't want to,
or can't run ACPI (through various other AML bugs for eg).

For minimal parsing of the ACPI P state tables, we shouldn't need the
full-blown interpretor IMO.

		Dave


  reply	other threads:[~2004-01-13 23:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 22:37 Cleanups for powernow-k8 paul.devriendt
2004-01-13 23:06 ` Dave Jones [this message]
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
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=20040113230605.GM14674@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=paul.devriendt@amd.com \
    --cc=pavel@ucw.cz \
    /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