path: root/documentation
diff options
authorScott Rifenbark <>2018-11-15 14:30:15 -0800
committerRichard Purdie <>2018-12-27 22:54:55 +0000
commit8271ca3968b50ce4347fa49e42581e603640dfbf (patch)
treeed18303ebeb27e5ef6eef1f2b18af64e93954b18 /documentation
parent94a6cd1c2f40a43ddf517ea0894e351d52219604 (diff)
kernel-dev: Updated phrasing for what a "defconfig" file is.
It was over simplistic. (From yocto-docs rev: 8c66db6f2a35e9e57423690976a16d6a815ccbc9) Signed-off-by: Scott Rifenbark <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'documentation')
1 files changed, 5 insertions, 2 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 83b02b1c18..9052876122 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -1603,8 +1603,11 @@
<title>Creating a&nbsp;&nbsp;<filename>defconfig</filename> File</title>
- A <filename>defconfig</filename> file is simply a
- <filename>.config</filename> renamed to "defconfig".
+ A <filename>defconfig</filename> file in the context of
+ the Yocto Project is often a <filename>.config</filename>
+ file that is copied from a build or a
+ <filename>defconfig</filename> taken from the kernel tree
+ and moved into recipe space.
You can use a <filename>defconfig</filename> file
to retain a known set of kernel configurations from which the
OpenEmbedded build system can draw to create the final