diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 63963d5bbd..8223954f04 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -516,22 +516,22 @@
the meta-<bsp_name>/recipes-kernel/linux directory).
- Suppose the BSP uses the linux-yocto_3.0.bb kernel,
- which is the preferred kernel to use for developing a new BSP using the Yocto Project.
+ Suppose you are using the linux-yocto_3.2.bb recipe to build
+ the kernel.
In other words, you have selected the kernel in your
<bsp_name>.conf file by adding the following statements:
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
- PREFERRED_VERSION_linux-yocto = "3.0%"
+ PREFERRED_VERSION_linux-yocto = "3.2%"
- You would use the linux-yocto_3.0.bbappend file to append
+ You would use the linux-yocto_3.2.bbappend file to append
specific BSP settings to the kernel, thus configuring the kernel for your particular BSP.
As an example, look at the existing Crown Bay BSP.
The append file used is:
- meta-crownbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
+ meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
The following listing shows the file.
Be aware that the actual commit ID strings in this example listing might be different
@@ -541,34 +541,34 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_crownbay = "crownbay"
- KMACHINE_crownbay = "yocto/standard/crownbay"
- KERNEL_FEATURES_append_crownbay += " cfg/smp.scc"
+ KMACHINE_crownbay = "crownbay"
+ KBRANCH_crownbay = "standard/default/crownbay"
COMPATIBLE_MACHINE_crownbay-noemgd = "crownbay-noemgd"
- KMACHINE_crownbay-noemgd = "yocto/standard/crownbay"
- KERNEL_FEATURES_append_crownbay-noemgd += " cfg/smp.scc"
+ KMACHINE_crownbay-noemgd = "crownbay"
+ KBRANCH_crownbay-noemgd = "standard/default/crownbay"
- SRCREV_machine_pn-linux-yocto_crownbay ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"
- SRCREV_meta_pn-linux-yocto_crownbay ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
+ SRCREV_machine_pn-linux-yocto_crownbay ?= "48101e609711fcfe8d5e737a37a5a69f4bd57d9a"
+ SRCREV_meta_pn-linux-yocto_crownbay ?= "5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b"
- SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"
- SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
+ SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "48101e609711fcfe8d5e737a37a5a69f4bd57d9a"
+ SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b"
This append file contains statements used to support the Crown Bay BSP for both
Intel EMGD and the VESA graphics.
The build process, in this case, recognizes and uses only the statements that
apply to the defined machine name - crownbay in this case.
- So, the applicable statements in the linux-yocto_3.0.bbappend
+ So, the applicable statements in the linux-yocto_3.2.bbappend
file are follows:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_crownbay = "crownbay"
- KMACHINE_crownbay = "yocto/standard/crownbay"
- KERNEL_FEATURES_append_crownbay += " cfg/smp.scc"
+ KMACHINE_crownbay = "crownbay"
+ KBRANCH_crownbay = "standard/default/crownbay"
- SRCREV_machine_pn-linux-yocto_crownbay ?= "63c65842a3a74e4bd3128004ac29b5639f16433f"
- SRCREV_meta_pn-linux-yocto_crownbay ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
+ SRCREV_machine_pn-linux-yocto_crownbay ?= "48101e609711fcfe8d5e737a37a5a69f4bd57d9a"
+ SRCREV_meta_pn-linux-yocto_crownbay ?= "5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b"
The append file defines crownbay as the compatible machine and
defines the KMACHINE.