kernel-dev: Updates to the "Using Kernel Metadata in a Recipe" section.

Changed out the example to use some bits from the meta-xilinx layer
instead of the emenlow layer.

Reported-by: Robert P. J. Day <crashcourse.ca>
(From yocto-docs rev: 477c62877f5882538176d0f9c8a10fc4cf878628)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 12 insertions, 7 deletions

diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index dc5d9ba3dd..1b19f74073 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -48,14 +48,18 @@
         This variable is typically set to the same value as the
         <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
         variable, which is used by
-        <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
-        (e.g. "edgerouter" or "emenlow").
+        <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>.
+        However, in some cases, the variable might instead refer to the
+        underlying platform of the <filename>MACHINE</filename>.
+    </para>
+
+    <para>
         Multiple BSPs can reuse the same <filename>KMACHINE</filename>
         name if they are built using the same BSP description.
-        The "emenlow" and "emenlow-noemgd" BSP combination
-        in the <filename>meta-intel</filename>
+        The "ep108-zynqmp" and "qemuzynqmp" BSP combination
+        in the <filename>meta-xilinx</filename>
         layer is a good example of two BSPs using the same
-        <filename>KMACHINE</filename> value (i.e. "emenlow").
+        <filename>KMACHINE</filename> value (i.e. "zynqmp").
         See the <link linkend='bsp-descriptions'>BSP Descriptions</link> section
         for more information.
     </para>
@@ -67,9 +71,10 @@
         variable must be set to indicate the branch.
         <note>
             You can use the <filename>KBRANCH</filename> value to define an
-            alternate branch typically with a machine override as follows:
+            alternate branch typically with a machine override as shown here
+            from the <filename>meta-emenlow</filename> layer:
             <literallayout class='monospaced'>
-     KBRANCH_emenlow ?= "standard/emenlow"
+     KBRANCH_emenlow-noemgd = "standard/base"
             </literallayout>
         </note>
     </para>