diff options
authorScott Rifenbark <>2012-06-26 21:27:35 (GMT)
committerRichard Purdie <>2012-06-29 14:54:26 (GMT)
commit73cdebf60df225ee10f2eb215935be3b61e1b831 (patch)
parent6b06a4fa1b99768516ac5bee9e70922af811d285 (diff)
documentation/dev-manual/dev-manual-kernel-appendix.xml: Add note about conflictdenzil-7.0.1_rc2denzil-7.0.1
Added a note to the part of the example where you bitbake the kernel after turning off CONFIG_SMP. The warnings you get can cause confusion. the note explains they are normal. (From yocto-docs rev: 08ed090f0b8b6970832242a52827ae2957918cf3) Signed-off-by: Scott Rifenbark <> Signed-off-by: Richard Purdie <>
1 files changed, 11 insertions, 0 deletions
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml
index da74721..2901384 100644
--- a/documentation/dev-manual/dev-manual-kernel-appendix.xml
+++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml
@@ -775,6 +775,17 @@
775 $ bitbake linux-yocto 775 $ bitbake linux-yocto
776 </literallayout> 776 </literallayout>
777 </para> 777 </para>
779 <note>
780 Manually turning off a kernel configuration setting such as
781 <filename>CONFIG_SMP</filename> can cause the kernel configuration audit
782 to issue warnings during the build.
783 In this example, warnings appear telling you that the expected value
784 <filename>CONFIG_SMP</filename> does not appear in the <filename>.config</filename>
785 file.
786 Because in this example you specifically turned off <filename>CONFIG_SMP</filename>,
787 you can safely ignore the apparent conflict.
788 </note>
778 789
779 <para> 790 <para>
780 Now run the QEMU emulator and pass it the same multi-processor option as before: 791 Now run the QEMU emulator and pass it the same multi-processor option as before: