cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmal Govind <nirmalg@psu.edu>
To: dongili@supereva.it
Cc: cpufreq@www.linux.org.uk
Subject: Re: sysfs cpufreq missing in 2.6.0
Date: Tue, 23 Dec 2003 12:01:09 -0500	[thread overview]
Message-ID: <3FE874D5.4020107@psu.edu> (raw)
In-Reply-To: <20031223164953.GN951@inferi.kami.home>

> sysfs is not procfs :)
> take look at Documentation/filesystems/sysfs.txt in your kernel tree
> 
> bye

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?

Thanks,
nirmal

  reply	other threads:[~2003-12-23 17:01 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 [this message]
2003-12-23 17:54     ` AthlonRob
2003-12-23 18:01       ` Nirmal Govind
2004-01-09 23:09       ` Ducrot Bruno
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=3FE874D5.4020107@psu.edu \
    --to=nirmalg@psu.edu \
    --cc=cpufreq@www.linux.org.uk \
    --cc=dongili@supereva.it \
    /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