From: Dave Jones <davej@redhat.com>
To: Ralf Meyer <ranfyy@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Mobile Celeron
Date: Tue, 13 Mar 2007 15:01:21 -0400 [thread overview]
Message-ID: <20070313190121.GD27471@redhat.com> (raw)
In-Reply-To: <50df9eb80703131114wcff0a56g1d93499531eee9a@mail.gmail.com>
On Tue, Mar 13, 2007 at 07:14:16PM +0100, Ralf Meyer wrote:
> On 3/13/07, markus reichelt <ml@mareichelt.de> wrote:
> > * Ralf Meyer <ranfyy@gmail.com> wrote:
> >
> > > is a Mobile Celeron supposed to be able to do CPU frequency
> > > scaling?
> >
> > run cpuid and check for something like Enhanced Intel SpeedStep
> > Technology
> >
> > cpuid @ http://www.etallen.com/cpuid.html
>
> Thanks. I didn't know this tool.
>
> $ cpuid | grep -i speed # gave me:
> ---
> Enhanced Intel SpeedStep Technology = false
> ---
>
> Its man page led me to the Datasheet (29851706.pdf). In the Power
> Management chapter there is no mention of speedstep or enhanced
> speedstep but something called Quickstart. I never heard about this
> before.
>
> Does Quickstart work all by itself?
iirc, quickstart is just a c-state, that (providing your BIOS has
an ACPI implementation that works) should 'just work'.
> My original question should have been clearer in that I wanted to know
> if the hardware is capable of frequency scaling of some sort.
I don't recall any celerons having frequency scaling.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-13 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 20:20 Mobile Celeron Ralf Meyer
2007-03-13 1:38 ` markus reichelt
2007-03-13 18:14 ` Ralf Meyer
2007-03-13 19:01 ` Dave Jones [this message]
2007-03-13 19:33 ` Ralf Meyer
2007-03-13 19:37 ` Ralf Meyer
2007-03-13 19:42 ` Dave Jones
2007-03-13 19:47 ` Ralf Meyer
2007-03-13 20:27 ` Dave Jones
2007-03-13 20:46 ` Ralf Meyer
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=20070313190121.GD27471@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=ranfyy@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.