From: Bruno Ducrot <ducrot@poupinou.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq@lists.linux.org.uk, Ben Kevan <ben.kevan@gmail.com>,
linux@brodo.de
Subject: Re: 2.6.16.x CPUFREQ / SpeedStep-Centrino: couldn't enable Enchanced SpeedStep
Date: Wed, 21 Jun 2006 12:01:36 +0200 [thread overview]
Message-ID: <20060621100136.GF3700@poupinou.org> (raw)
In-Reply-To: <4498394B.3080909@goop.org>
On Tue, Jun 20, 2006 at 11:07:07AM -0700, Jeremy Fitzhardinge wrote:
> Bruno Ducrot wrote:
> >That's strange. Even if there is no processor object declared onto ACPI
> >tables it should work with CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE set since
> >it's a bania.
> >
>
> This message specifically means that the CPU isn't allowing EST to be
> enabled, even though the CPU has the capability. I think the BIOS can
> lock this down, like VT on later processors. Though I can't imagine
> why, unless the machine is being sold as a cheaper/slower system than
> the CPU they put in it...
>
> What does the SMM patch do?
>
I should have been more specific. The patch won't fix anything but
add a warning if the BIOS do not allow the OS to take control of
performances stuff.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
prev parent reply other threads:[~2006-06-21 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 23:10 2.6.16.x CPUFREQ / SpeedStep-Centrino: couldn't enable Enchanced SpeedStep Ben Kevan
2006-06-19 23:13 ` Dave Jones
2006-06-20 1:07 ` Ben Kevan
2006-06-20 5:24 ` Ben Kevan
2006-06-20 5:33 ` Dave Jones
2006-06-20 9:43 ` Bruno Ducrot
2006-06-20 10:16 ` Bruno Ducrot
2006-06-20 18:07 ` Jeremy Fitzhardinge
2006-06-20 20:32 ` Ben Kevan
2006-06-20 20:37 ` Jeremy Fitzhardinge
2006-06-20 21:09 ` Ben Kevan
2006-06-22 17:59 ` Dominik Brodowski
2006-06-24 18:03 ` Ben Kevan
2006-06-21 10:01 ` Bruno Ducrot [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=20060621100136.GF3700@poupinou.org \
--to=ducrot@poupinou.org \
--cc=ben.kevan@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=jeremy@goop.org \
--cc=linux@brodo.de \
/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