kernel-dev: fix explanation of KBUILD_DEFCONFIG

KBUILD_DEFCONFIG is meant to refer to an *in-tree* defconfig file, not
an external one.

(From yocto-docs rev: 34202eee3fc2bb4e0b92374822bff87fd3af1ebc)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
rpjday@crashcourse.ca
2020-02-21 15:43:47 -05:00
committed by Richard Purdie
parent 0096b10efe
commit 284af91476

View File

@@ -948,12 +948,14 @@
<literallayout class='monospaced'>
KBUILD_DEFCONFIG_<replaceable>KMACHINE</replaceable> ?= <replaceable>defconfig_file</replaceable>
</literallayout>
Here is an example that appends the
<filename>KBUILD_DEFCONFIG</filename> variable with
"common-pc" and provides the path to the "in-tree"
<filename>defconfig</filename> file:
Here is an example that assigns the
<filename>KBUILD_DEFCONFIG</filename> variable based on
"raspberrypi2" and provides the path to the "in-tree"
<filename>defconfig</filename> file
to be used for a Raspberry Pi 2,
which is based on the Broadcom 2708/2709 chipset:
<literallayout class='monospaced'>
KBUILD_DEFCONFIG_common-pc ?= "/home/scottrif/configfiles/my_defconfig_file"
KBUILD_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
</literallayout>
</para>