mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-04 02:00:04 +00:00
Code Issues Projects Releases Wiki Activity

kernel-dev: Edits to the "Configuration" section.

Browse Source 
First real re-write of this original text.

(From yocto-docs rev: a6d16b61057df8ed811cf1f5f27c5f9e08be1108)

Signed-off-by: scott-lenovo <scott-lenovo@ubuntu.(none)>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
scott-lenovo
2013-01-08 09:21:49 -08:00
committed by Richard Purdie
parent d176d86a4c
commit 76f1ffe77a
1 changed files with 19 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/kernel-dev/kernel-dev-advanced.xml
+19 -14
View File
@@ -699,14 +699,17 @@ meta/cfg/kernel-cache/ if you are creating meta-data in-tree (see 3.2.2).
<title>Configuration</title> <title>Configuration</title>
<para> <para>
The simplest unit of metadata is the configuration-only feature. The simplest unit of kernel Metadata is the configuration-only
It consists of one or more Linux kernel configuration parameters feature.
in a configuration fragment file (<filename>.cfg</filename>) This feature consists of one or more Linux kernel configuration
and an <filename>scc</filename> file describing the fragment. parameters in a configuration fragment file
(<filename>.cfg</filename>) and an <filename>.scc</filename> file
that describes the fragment.
</para> </para>
<para> <para>
The SMP fragment included in the linux-yocto-3.4 Git repository The Symmetric Multi-Processing (SMP) fragment included in the
<filename>linux-yocto-3.4</filename> Git repository
consists of the following two files: consists of the following two files:
<literallayout class='monospaced'> <literallayout class='monospaced'>
cfg/smp.scc: cfg/smp.scc:
@@ -718,7 +721,7 @@ meta/cfg/kernel-cache/ if you are creating meta-data in-tree (see 3.2.2).
CONFIG_SCHED_SMT=y CONFIG_SCHED_SMT=y
</literallayout> </literallayout>
You can find information on configuration fragment files in the You can find information on configuration fragment files in the
"<ulink url='&YOCTO_DOCS_REF_URL;#creating-config-fragments'>Creating Configuration Fragments</ulink>" "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-config-fragments'>Creating Configuration Fragments</ulink>"
section of the Yocto Project Development Manual and in section of the Yocto Project Development Manual and in
the "<link linkend='generating-configuration-files'>Generating Configuration Files</link>" the "<link linkend='generating-configuration-files'>Generating Configuration Files</link>"
section earlier in this manual. section earlier in this manual.
@@ -726,31 +729,33 @@ meta/cfg/kernel-cache/ if you are creating meta-data in-tree (see 3.2.2).
<para> <para>
<filename>KFEATURE_DESCRIPTION</filename> provides a short <filename>KFEATURE_DESCRIPTION</filename> provides a short
description of the fragment, the primary use is for higher level description of the fragment.
tooling, such as the Yocto Project BSP Tools (TODO:Citation). Higher level kernel tools use this description.
</para> </para>
<para> <para>
The <filename>kconf</filename> command is used to include the The <filename>kconf</filename> command is used to include the
actual configuration fragment in an <filename>scc</filename> actual configuration fragment in an <filename>.scc</filename>
file, and the "hardware" keyword identifies the fragment as file, and the "hardware" keyword identifies the fragment as
being hardware enabling, as opposed to general policy, being hardware enabling, as opposed to general policy,
which would use the keyword "non-hardware". which would use the "non-hardware" keyword.
The distinction is made for the benefit of the configuration The distinction is made for the benefit of the configuration
validation tools, which will warn you if a hardware fragment validation tools, which warn you if a hardware fragment
overrides a policy set by a non-hardware fragment. overrides a policy set by a non-hardware fragment.
<note>
The description file can include multiple
<filename>kconf</filename> statements, one per fragment.
</note>
</para> </para>
<para> <para>
As described in the As described in the
"<link linkend='generating-configuration-files'>Generating Configuration Files</link>" "<link linkend='generating-configuration-files'>Generating Configuration Files</link>"
section, the following BitBake command can be used to audit your section, you can use the following BitBake command to audit your
configuration: configuration:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake linux-yocto -c kernel_configcheck -f $ bitbake linux-yocto -c kernel_configcheck -f
</literallayout> </literallayout>
The description file can include multiple <filename>kconf</filename>
statements, one per fragment.
</para> </para>
<para> <para>