path: root/documentation/kernel-manual
diff options
authorScott Rifenbark <>2012-01-26 17:08:17 -0600
committerRichard Purdie <>2012-03-08 12:07:45 -0800
commit8f9dc14e28a2adac6bd1389c1ef1f9b17ce5fa41 (patch)
treee1c5f2e72d1b45dbd39347ab94d7a4c86c0c69a8 /documentation/kernel-manual
parent4baaf11e40f3baecf6b026dd17ca9878db8dc3e1 (diff)
documentation/kernel-manual/kernel-concepts.xml: new section starting
This is the start of a new section on configuration. It is mostly writer's notes at this point. More to be added later. (From yocto-docs rev: db41de4ebd7040f507c5a43739f1a25d7e1d9623) Signed-off-by: Scott Rifenbark <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'documentation/kernel-manual')
1 files changed, 70 insertions, 0 deletions
diff --git a/documentation/kernel-manual/kernel-concepts.xml b/documentation/kernel-manual/kernel-concepts.xml
index 830042a495..922f9b312d 100644
--- a/documentation/kernel-manual/kernel-concepts.xml
+++ b/documentation/kernel-manual/kernel-concepts.xml
@@ -303,6 +303,76 @@
+ <section id='kernel-configuration'>
+ <title>Kernel Configuration</title>
+ <para>
+ Kernel configuration, along with kernel features, defines how a kernel image is
+ built.
+ Through configuration settings, you can customize a Linux Yocto kernel to be
+ specific to particular hardware.
+ For example, you can specify sound support or networking support.
+ This section describes basic concepts behind Kernel configuration within the
+ Yocto Project.
+ </para>
+ <para>
+ </para>
+ <para>
+ Explain how <filename>.config</filename> is used when the kernel image is built.
+ Describe the role of <filename>menuconfig</filename> regarding the
+ <filename>.config</filename>.
+ Locate the <filename>.config</filename> for the user.
+ Not recommended to edit the <filename>.config</filename> file directly.
+ You can use BitBake to build and invoke the <filename>menuconfig</filename>
+ tool.
+ </para>
+ <para>
+ Introduce the configuration fragment.
+ Step through the life of a configuration fragment from idea or need to
+ change something in the kernel to how it is used when the kernel image is built.
+ Describe how configuration fragments are created and where they live.
+ Make sure the syntax of configuration fragments is understood.
+ </para>
+ <para>
+ Talk in general how the user creates a configuration fragment.
+ Point to example B.2 of the YP Development Manual as a way to use
+ <filename>menuconfig</filename>.
+ </para>
+ <para>
+ The tool <filename>menuconfig</filename> allows you to choose the features of the
+ Linux Yocto kernel that will be compiled.
+ This tool is a convenient method to alter the <filename>.config</filename> file.
+ You can use a simple interface to scroll through kernel features and disable
+ and enable configruation variables.
+ When you save your changes, the contents of the <filename>.config</filename>
+ are altered.
+ You can get general information on <filename>menuconfig</filename> at
+ <ulink url=''></ulink>.
+ </para>
+ <para>
+ The Yocto Project employs <filename>menuconfig</filename> by invoking it through
+ BitBake as follows after making sure the environment setup script has been sourced:
+ <literallayout class='monospaced'>
+ $ bitbake linux-yocto -c menuconfig
+ </literallayout>
+ You can see how <filename>menuconfig</filename> is used to change a simple
+ kernel configuration in the
+ "<ulink url=''>Changing the&nbsp;&nbsp;<filename>CONFIG_SMP</filename>
+ Configuration Using&nbsp;&nbsp;<filename>menuconfig</filename></ulink>" section of
+ The Yocto Project Development Manual.
+ </para>
+ <para>
+ </para>
+ </section>
<section id='kernel-tools'>
<title>Kernel Tools</title>