From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [PATCH] powernow-k8 max speed sanity check
Date: Thu, 5 Feb 2004 10:17:05 -0800 [thread overview]
Message-ID: <20040205181704.GC7658@atomide.com> (raw)
In-Reply-To: <20040203131432.GE550@openzaurus.ucw.cz>
* Pavel Machek <pavel@ucw.cz> [040205 06:03]:
> Hi!
>
> > Following is a little patch to do a sanity check on the max speed and
> > voltage values provided by the bios.
> >
> > Some buggy bioses provide bad values if the cpu changes, for example, in
> > my case the bios claims the max cpu speed is 1600MHz, while it's running at
> > 1800MHz. (Cheapo Emachines m6805 you know...) This could also happen on
> > machines where the cpu is upgraded.
> >
> > These checks should be safe, as they only change things if the machine is
> > already running at a higher speed than the bios claims.
> >
>
> Someone should really bug them to fix their BIOS. (BTW does keyboard work
> ok for you?)
No problems with keyboard, and the cpufreq works fine with the patch, but
not at all without the patch.
There are some ACPI related issues though, such as: via-rhine gets wrong
irq with ACPI on, system hangs with yenta_socket loaded if I
connect/disconnect the power cord... So for now, I don't use the PCMCIA.
> Going though ACPI solves this, and I have perhaps better
> patch to hardcode right values...
Still, the max speed check should be safe. Maybe pass values as module
options too? I would not trust on ACPI working right on this machine :)
Tony
next prev parent reply other threads:[~2004-02-05 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 20:35 [PATCH] powernow-k8 max speed sanity check Tony Lindgren
2004-01-31 23:19 ` Dave Jones
2004-02-03 13:14 ` Pavel Machek
2004-02-05 18:17 ` Tony Lindgren [this message]
2004-02-05 18:48 ` Pavel Machek
2004-02-05 19:36 ` Tony Lindgren
2004-02-05 21:33 ` Tony Lindgren
2004-02-05 21:38 ` Pavel Machek
2004-02-05 21:56 ` Tony Lindgren
2004-02-06 0:28 ` Pavel Machek
2004-02-06 1:15 ` Tony Lindgren
2004-02-06 12:56 ` Pavel Machek
2004-02-06 17:28 ` Tony Lindgren
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=20040205181704.GC7658@atomide.com \
--to=tony@atomide.com \
--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