From: Daniel Pittman <daniel@rimspace.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPUFreq sysfs interface MIA?
Date: Thu, 08 May 2003 12:02:43 +1000 [thread overview]
Message-ID: <87r87akxfg.fsf@enki.rimspace.net> (raw)
In-Reply-To: <20030508003223.GA5051@kroah.com> (Greg KH's message of "Wed, 7 May 2003 17:32:23 -0700")
On Wed, 7 May 2003, Greg KH wrote:
> On Thu, May 08, 2003 at 10:23:33AM +1000, Daniel Pittman wrote:
>> On Wed, 7 May 2003, Greg KH wrote:
>> > On Wed, May 07, 2003 at 10:36:09AM +1000, Daniel Pittman wrote:
>> >> On Tue, 6 May 2003, Greg KH wrote:
>> >> > On Tue, May 06, 2003 at 05:29:15PM +1000, Daniel Pittman wrote:
>> >> >>
>> >> >> The content of /sys/devices/sys/cpu0 is:
>> >> >> /sys/devices/sys/cpu0
>> >> >> |-- name
>> >> >> `-- power
>> >> >
>> >> > What does /sys/class/cpu show?
>> >>
>> >> /sys/class/cpu
>> >> `-- cpu0
>> >> `-- device -> ../../../devices/sys/cpu0
>> >
>> > Oops, forgot to hook up stuff... Does the following patch from
>> > Jonathan Corbet fix this?
>>
>> I tested this patch earlier and, no, it does not resolve the issue.
>> I have exactly the same issue with it applied as before.
>
> Hm, I just applied this patch, and dug up some hardware that will work
> with cpufreq, and it shows up just fine for me. I don't know what's
> wrong, sorry.
Sorry, the cpufreq interface changed location and I didn't look closely
enough into it. With the patch applied, the cpufreq support is
available and works correctly.
So, this was a fault on my part and the patch works. Sorry.
Daniel
--
I have never seen a bad television program, because I refuse to.
God gave me a mind, and a wrist that turns things off.
-- Jack Paar
prev parent reply other threads:[~2003-05-08 1:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 7:29 CPUFreq sysfs interface MIA? Daniel Pittman
2003-05-06 21:12 ` Greg KH
2003-05-07 0:36 ` Daniel Pittman
2003-05-07 23:32 ` Greg KH
2003-05-08 0:23 ` Daniel Pittman
2003-05-08 0:32 ` Greg KH
2003-05-08 2:02 ` Daniel Pittman [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=87r87akxfg.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--cc=greg@kroah.com \
--cc=linux-kernel@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 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.