From: Nico Golde <nico@ngolde.de>
To: linux-kernel@vger.kernel.org
Subject: Getting cpu frequency
Date: Sat, 11 Feb 2006 21:47:34 +0100 [thread overview]
Message-ID: <20060211204733.GA7813@ngolde.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
Hi,
at the moment I try to get the current cpu frequency via
using the cpufreq_get() function defined in linux/cpufreq.h.
Can someone point me to the headers I have to include to let
this work because just doing #include <linux/cpufreq.h>
results in a bunch of errors:
[...]
In file included from /usr/include/linux/cpu.h:22,
from cpu.c:2:
/usr/include/linux/sysdev.h:31: error: field 'drivers' has incomplete type
/usr/include/linux/sysdev.h:35: error: syntax error before 'pm_message_t'
/usr/include/linux/sysdev.h:37: error: field 'kset' has incomplete type
/usr/include/linux/sysdev.h:50: error: field 'entry' has incomplete type
/usr/include/linux/sysdev.h:54: error: syntax error before 'pm_message_t'
/usr/include/linux/sysdev.h:69: error: syntax error before 'u32'
/usr/include/linux/sysdev.h:72: error: syntax error before '}' token
/usr/include/linux/sysdev.h:79: error: field 'attr' has incomplete type
/usr/include/linux/sysdev.h:80: error: syntax error before 'ssize_
[...]
Using 2.6.14.
Regards Nico
P.S. Please CC me, I am not subsribed, thanks
--
Nico Golde - JAB: nion@jabber.ccc.de | GPG: 0x73647CFF
http://www.ngolde.de | http://www.muttng.org | http://grml.org
Forget about that mouse with 3/4/5 buttons -
gimme a keyboard with 103/104/105 keys!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-02-11 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 20:47 Nico Golde [this message]
2006-02-11 21:37 ` Getting cpu frequency Dave Jones
2006-02-11 21:42 ` Nico Golde
2006-02-11 22:13 ` Dave Jones
2006-02-11 22:16 ` Nico Golde
2006-02-12 8:46 ` Mattia Dongili
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=20060211204733.GA7813@ngolde.de \
--to=nico@ngolde.de \
--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.