summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq
diff options
context:
space:
mode:
authorMarti Raudsepp <marti@juffo.org>2010-01-20 19:19:33 +0200
committerDave Jones <davej@redhat.com>2010-08-03 13:47:04 -0400
commit298decfbc44e9a4cb7862ae1b7dfc4e1ba3551b9 (patch)
treeceef739864c02e85c99922834d566e3686177f7c /drivers/cpufreq
parentc2f4a2c6e08c7635316dfd25ef706e9104384c56 (diff)
[CPUFREQ] powernow-k8: On load failure, remind the user to enable support in BIOS setup
On Wed, 2010-01-20 at 16:56 +0100, Thomas Renninger wrote: > But most often this happens if people upgrade their CPU and do not > update their BIOS. > Or the vendor does not recognise the new CPU even if the BIOS got > updated. Maybe some of those people just didn't realize it was disabled in BIOS? If you tell users that it's a firmware bug then they'll probably just give up. > The itself message might be an enhancment, IMO it's not worth a patch. Why do you think so? I spent an hour on hunting down the BIOS upgrade, only to find that it didn't improve anything. It was a day later that I realized that it might be a BIOS option; and the option was literally the _last_ option in the whole BIOS setup. :) This message would have saved the day. > But do not revert the FW_BUG part! Sure, you have a point here. How about this patch?
Diffstat (limited to 'drivers/cpufreq')
0 files changed, 0 insertions, 0 deletions