From: Ducrot Bruno <ducrot@poupinou.org>
To: AthlonRob <AthlonRob@axpr.net>
Cc: cpufreq@www.linux.org.uk
Subject: Re: sysfs cpufreq missing in 2.6.0
Date: Sat, 10 Jan 2004 00:09:04 +0100 [thread overview]
Message-ID: <20040109230904.GW14031@poupinou.org> (raw)
In-Reply-To: <1072202064.6531.13.camel@dell.linux.box>
On Tue, Dec 23, 2003 at 09:54:24AM -0800, AthlonRob wrote:
> On Tue, 2003-12-23 at 09:01, Nirmal Govind wrote:
>
> > Aah.. thank you! Read it and also found the cpufreq after I mounted
> > sysfs. I changed the frequency too - one question: how does one know
> > if it's actually working? I see the new frequency in the
> > scaling_setspeed file but are there any user tools that show the
> > real-time frequency of the processor?
>
> cat /proc/cpuinfo ....
>
No. /proc/cpuinfo will only show what 'think' cpufreq internals.
Use bogomips instead for example, or eventually x86info.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-09 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 16:38 sysfs cpufreq missing in 2.6.0 Nirmal Govind
2003-12-23 16:49 ` Mattia Dongili
2003-12-23 17:01 ` Nirmal Govind
2003-12-23 17:54 ` AthlonRob
2003-12-23 18:01 ` Nirmal Govind
2004-01-09 23:09 ` Ducrot Bruno [this message]
2003-12-23 18:05 ` Jan De Luyck
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=20040109230904.GW14031@poupinou.org \
--to=ducrot@poupinou.org \
--cc=AthlonRob@axpr.net \
--cc=cpufreq@www.linux.org.uk \
/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