All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powernow-k8 max speed sanity check
Date: Sat, 31 Jan 2004 23:19:18 +0000	[thread overview]
Message-ID: <20040131231918.GL20622@redhat.com> (raw)
In-Reply-To: <20040131203512.GA21909@atomide.com>

On Sat, Jan 31, 2004 at 12:35:12PM -0800, Tony Lindgren wrote:
 > Hi all,
 > 
 > 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.

ye gads, yet another problem with eMachines PST tables.
Conclusive proof I think that we need the 'read from ACPI P state tables
when PST contains garbage' patch.

		Dave


  reply	other threads:[~2004-01-31 23:21 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 [this message]
2004-02-03 13:14 ` Pavel Machek
2004-02-05 18:17   ` Tony Lindgren
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=20040131231918.GL20622@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.