From 78cecf7a20580e75306b1f80474e6d6b5a909606 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 6 Mar 2015 10:50:56 -0800 Subject: 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 (From yocto-docs rev: 477c62877f5882538176d0f9c8a10fc4cf878628) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-advanced.xml | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) (limited to 'documentation/kernel-dev') 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 MACHINE variable, which is used by - BitBake - (e.g. "edgerouter" or "emenlow"). + BitBake. + However, in some cases, the variable might instead refer to the + underlying platform of the MACHINE. + + + Multiple BSPs can reuse the same KMACHINE name if they are built using the same BSP description. - The "emenlow" and "emenlow-noemgd" BSP combination - in the meta-intel + The "ep108-zynqmp" and "qemuzynqmp" BSP combination + in the meta-xilinx layer is a good example of two BSPs using the same - KMACHINE value (i.e. "emenlow"). + KMACHINE value (i.e. "zynqmp"). See the BSP Descriptions section for more information. @@ -67,9 +71,10 @@ variable must be set to indicate the branch. You can use the KBRANCH 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 meta-emenlow layer: - KBRANCH_emenlow ?= "standard/emenlow" + KBRANCH_emenlow-noemgd = "standard/base" -- cgit v1.2.3-54-g00ecf