From: Goran <gkoruga@siol.net>
To: cpufreq@lists.linux.org.uk
Subject: cpufreq and modular build
Date: Mon, 5 May 2008 17:58:17 +0200 [thread overview]
Message-ID: <20080505175817.3ee17fb6@cornholio.confused.org> (raw)
Hello.
I have a question regarding cpufreq and modular build.
Looking in Kconfig file for 2.6.24.5 kernel version I see this:
---------------------------------------------------------------------------
config CPU_FREQ
bool "CPU Frequency scaling"
help
CPU Frequency scaling allows you to change the clock speed of
CPUs on the fly. This is a nice method to save power, because
the lower the CPU clock speed, the less power the CPU consumes.
Note that this driver doesn't automatically change the CPU
clock speed, you need to either enable a dynamic cpufreq governor
(see below) after boot, or use a userspace tool.
To compile this driver as a module, choose M here: the
module will be called cpufreq.
For details, take a look at <file:Documentation/cpu-freq>.
If in doubt, say N.
---------------------------------------------------------------------------
So there's a discrepancy between the way this setting is added in the
Kconfig file and the help text. Help text suggests this can be built as a
module, and there is also (some?) support for that in the source code,
but Kconfig file does not allow one to build it as a module.
Which bit needs fixing - help text or the "bool" setting?
Please cc: me on replies as I am not subscribed to the list.
Regards,
Goran
next reply other threads:[~2008-05-05 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 15:58 Goran [this message]
2008-05-06 15:12 ` cpufreq and modular build Thomas Renninger
2008-05-11 13:48 ` Goran
-- strict thread matches above, loose matches on Subject: below --
2008-05-11 16:18 Dave Jones
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=20080505175817.3ee17fb6@cornholio.confused.org \
--to=gkoruga@siol.net \
--cc=cpufreq@lists.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 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.