diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 0159f48848..05094ca77d 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -596,22 +596,22 @@
- For example, suppose you had a set of configuration options in a file called
- myconfig.cfg.
- If you put that file inside a directory named /linux-yocto and then added
- a SRC_URI statement such as the following to the append file,
- those configuration options will be picked up and applied when the kernel is built.
+ For example, suppose you had a some configuration options in a file called
+ network_configs.cfg.
+ You can place that file inside a directory named /linux-yocto and then add
+ a SRC_URI statement such as the following to the append file.
+ When the OpenEmbedded build system builds the kernel, the configuration options are
+ picked up and applied.
- SRC_URI += "file://myconfig.cfg"
+ SRC_URI += "file://network_configs.cfg"
- As mentioned earlier, you can group related configurations into multiple files and
- name them all in the SRC_URI statement as well.
- For example, you could group separate configurations specifically for Ethernet and graphics
- into their own files and add those by using a SRC_URI statement like the
- following in your append file:
+ To group related configurations into multiple files, you perform a similar procedure.
+ Here is an example that groups separate configurations specifically for Ethernet and graphics
+ into their own files and adds the configurations
+ by using a SRC_URI statement like the following in your append file:
SRC_URI += "file://myconfig.cfg \
file://eth.cfg \
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index d96d78d49e..b8708ff19f 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1362,18 +1362,29 @@
- Creating Config Fragments
+ Creating Configuration Fragments
- Configuration fragments are simply kernel options that appear in a file.
+ Configuration fragments are simply kernel options that appear in a file
+ placed where the OpenEmbedded build system can find and apply them.
Syntactically, the configuration statement is identical to what would appear
- in the .config.
- For example, issuing the following from the shell would create a config fragment
+ in the .config file, which is in the
+ build directory in
+ tmp/work/<arch>-poky-linux/linux-yocto-<release-specific-string>/linux-<arch>-<build-type>.
+
+
+
+ It is simple to create a configuration fragment.
+ For example, issuing the following from the shell creates a configuration fragment
file named my_smp.cfg that enables multi-processor support
within the kernel:
$ echo "CONFIG_SMP=y" >> my_smp.cfg
+
+ All configuration files must use the .cfg extension in order
+ for the OpenEmbedded build system to recognize them as a configuration fragment.
+
@@ -1382,15 +1393,28 @@
SRC_URI.
The OpenEmbedded build system will pick up the configuration and add it to the
kernel's configuration.
- For example, assume you add the following to your
- linux-yocto_3.0.bbappend file:
+ For example, suppose you had a set of configuration options in a file called
+ myconfig.cfg.
+ If you put that file inside a directory named /linux-yocto
+ that resides in the same directory as the kernel's append file and then add
+ a SRC_URI statement such as the following to the kernel's append file,
+ those configuration options will be picked up and applied when the kernel is built.
- file://my_smp.cfg
+ SRC_URI += "file://myconfig.cfg"
+
+
+
+
+ As mentioned earlier, you can group related configurations into multiple files and
+ name them all in the SRC_URI statement as well.
+ For example, you could group separate configurations specifically for Ethernet and graphics
+ into their own files and add those by using a SRC_URI statement like the
+ following in your append file:
+
+ SRC_URI += "file://myconfig.cfg \
+ file://eth.cfg \
+ file://gfx.cfg"
- You would put the config fragment file my_smp.cfg in a
- sub-directory with the same root name (linux-yocto)
- beneath the directory that contains your linux-yocto_3.0.bbappend
- file and the build system will pick up and apply the fragment.