From: Peter Clifton <pcjc2@cam.ac.uk>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: davej@redhat.com, cpufreq@lists.linux.org.uk, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] allow the highest frequency if bios think so.
Date: Tue, 21 Nov 2006 11:04:36 +0000 [thread overview]
Message-ID: <1164107076.5516.33.camel@pcjc2lap> (raw)
In-Reply-To: <20061121103042.GI4945@poupinou.org>
On Tue, 2006-11-21 at 11:30 +0100, Bruno Ducrot wrote:
> Hi all,
>
> processor_perflib.c::acpi_processor_ppc_notifier() check if the value
> returned by the processor's _PPC method is 0 and return failed if so.
> This is wrong since 0 indicate that the bios think the processor can
go
> to the highest frequency. This patch for example fix the HP NX 6125
to
> allow its highest frequency to be available.
I don't know about the HP NX 6125, but on my nc 6320, you have to rmmod
psmouse before you shutdown or reboot the computer, otherwise something
upsets the BIOS and it won't run at full speed on next boot up.
Can't hurt to give it a try. The other method to get it working again is
to remove the AC adaptor and the battery for a few seconds, then
re-insert and power up.
Bootup time is also much faster if the psmouse was rmmod'd before
shutdown, or the power was completely removed as above.
Weired indeed!
Peter Clifton
next prev parent reply other threads:[~2006-11-21 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 10:30 [PATCH] allow the highest frequency if bios think so Bruno Ducrot
2006-11-21 11:04 ` Peter Clifton [this message]
2006-11-21 11:11 ` Bruno Ducrot
2006-11-29 7:25 ` Maciej Rutecki
2006-11-21 13:51 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2006-11-21 15:08 Pallipadi, Venkatesh
2006-11-21 16:35 ` Bruno Ducrot
2006-11-21 17:03 ` Dave Jones
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=1164107076.5516.33.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=ducrot@poupinou.org \
--cc=linux-acpi@vger.kernel.org \
/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