From: Tony Lindgren <tony@atomide.com>
To: Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, pavel@ucw.cz
Cc: cpufreq@www.linux.org.uk
Subject: Re: [tony@atomide.com: [PATCH] Powernow-k8 buggy BIOS override for 2.6.6]
Date: Thu, 13 May 2004 08:34:01 -0700 [thread overview]
Message-ID: <20040513153401.GB8480@atomide.com> (raw)
In-Reply-To: <20040513140501.GG16687@redhat.com>
* Dave Jones <davej@redhat.com> [040513 07:06]:
> On Wed, May 12, 2004 at 05:16:28PM -0700, Tony Lindgren wrote:
>
> > Following is the updated patch to make the powernow-k8 driver work on
> > machines with buggy BIOS, such as emachines m6805.
> >
> > The patch overrides the PST table only if check_pst_table() fails.
> >
> > The minimum value for the override is 800MHz, which is the lowest value
> > on all x86_64 systems AFAIK. The max value is the current running value.
> >
> > This patch should be safe to apply, even if Pavel's ACPI table check is
> > added to the driver. Or does anybody see a problem with it?
>
> Does the ACPI fallback not do the right thing ?
Does not work for me. But looks like that's because I had to turn off
ACPI processor module since 2.6.6 since it would hang my system. It could
also be that the hang is caused by the powernow-k8. I will check that.
> I don't really see the point of limping along with a 2-state PST
> if we can derive the proper info from the ACPI table.
Sure if the ACPI table check works properly. But even with 2-state PST,
being able to change from 1800MHz to 800MHz on battery increases the
battery life quite a bit. And it does not necessarily require ACPI :)
Regards,
Tony
prev parent reply other threads:[~2004-05-13 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040513001628.GA9388@atomide.com>
2004-05-13 14:05 ` [tony@atomide.com: [PATCH] Powernow-k8 buggy BIOS override for 2.6.6] Dave Jones
2004-05-13 15:34 ` Tony Lindgren [this message]
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=20040513153401.GB8480@atomide.com \
--to=tony@atomide.com \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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