From: Dave Jones <davej@redhat.com>
To: Roberto Gordo Saez <roberto.gordo@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Voltage tweaking in powernow_k8
Date: Fri, 20 Apr 2007 17:57:57 -0400 [thread overview]
Message-ID: <20070420215757.GJ20566@redhat.com> (raw)
In-Reply-To: <46292aa8.20f70c71.2add.ffffa105@mx.google.com>
On Fri, Apr 20, 2007 at 11:03:33PM +0200, Roberto Gordo Saez wrote:
> On Fri, Apr 20, 2007 at 02:55:33PM -0400, Dave Jones wrote:
> > I'm not enthusiastic about merging this code at all.
> > The big problem I see is that a lot of the reasons people want
> > to do this is "The bios say xyz, but the datasheet says it can do xyz+-1"
>
> Yes, I must admit so. It seems that many people just want to do heavy
> overclock. And it can be difficult to detect a broken BIOS... though
> I've discovered an interesting method: when the customer support tells
> you to install crystalcpuid (a Windows utility) and then they reply that
> Linux is not a supported OS, then there are high chance that their BIOS
> is broken :-)
>
> There seems to be some comments on certain laptops giving overpower to
> Turions, but I can't confirm how many of them are real BIOS bugs. I will
> probably continue with this as an unofficial patch. Thank you anyway
> for looking into this.
What I wouldn't object to however, if we do find tables that are *clearly*
broken, and we can't convince the manufacturer to do a fixed BIOS release,
adding override tables in the driver matching on DMI of the broken
systems would be fine by me.
But as you say, knowing whether the BIOS is broken, or if the manufacturer
had good reason to configure the tables that way is very hard to determine.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-04-20 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 17:18 Voltage tweaking in powernow_k8 Roberto Gordo Saez
2007-04-16 13:55 ` Langsdorf, Mark
2007-04-16 15:25 ` Roberto Gordo Saez
2007-04-20 18:35 ` Langsdorf, Mark
2007-04-20 18:55 ` Dave Jones
2007-04-20 21:03 ` Roberto Gordo Saez
2007-04-20 21:57 ` Dave Jones [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=20070420215757.GJ20566@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=roberto.gordo@gmail.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.