From 7f1662ef01b383c9fecb2b30ade50de97f17529a Mon Sep 17 00:00:00 2001 From: Tom Zanussi Date: Sun, 13 Mar 2011 00:01:51 -0600 Subject: documentation: BSP Developer's Guide fixes - use linux-yocto instead of linux-yocto-stable in examples - change branch names to match linux-yocto usage - remove outdated 'wrs' where it appears Signed-off-by: Tom Zanussi --- documentation/bsp-guide/bsp.xml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'documentation') diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index ea9b0017f..ba6ad744a 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -83,7 +83,7 @@ meta-<bsp_name>/conf/layer.conf meta-<bsp_name>/conf/machine/*.conf meta-<bsp_name>/recipes-bsp/* meta-<bsp_name>/recipes-graphics/* -meta-<bsp_name>/recipes-kernel/linux/linux-yocto-stable.bbappend +meta-<bsp_name>/recipes-kernel/linux/linux-yocto_git.bbappend @@ -107,7 +107,7 @@ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/fix_open_max_prepr meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/macro_tweak.patch meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd/nodolt.patch meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb -meta-crownbay/recipes-kernel/linux/linux-wrs_git.bbappend +meta-crownbay/recipes-kernel/linux/linux-yocto_git.bbappend @@ -315,7 +315,7 @@ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd_1.7.99.2.bb
Linux Kernel Configuration -meta-<bsp_name>/recipes-kernel/linux/linux-yocto-stable.bbappend +meta-<bsp_name>/recipes-kernel/linux/linux-yocto_git.bbappend @@ -330,27 +330,27 @@ meta-<bsp_name>/recipes-kernel/linux/linux-yocto-stable.bbappend directory. - Suppose you use a BSP that uses the linux-yocto-stable_git.bb kernel, + Suppose you use a BSP that uses the linux-yocto_git.bb kernel, which is the preferred kernel to use for developing a new BSP using the Yocto Project. In other words, you have selected the kernel in your <bsp_name>.conf file by adding the following statement: -PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-stable" +PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" - You would use the linux-yocto-stable_git.bbappend file to append + You would use the linux-yocto_git.bbappend file to append specific BSP settings to the kernel, thus configuring the kernel for your particular BSP. Now take a look at the existing "crownbay" BSP. The append file used is: -meta-crownbay/recipes-kernel/linux/linux-yocto-stable_git.bbappend +meta-crownbay/recipes-kernel/linux/linux-yocto_git.bbappend The file contains the following: FILESEXTRAPATHS := "${THISDIR}/${PN}" COMPATIBLE_MACHINE_crownbay = "crownbay" -KMACHINE_crownbay = "crownbay" +KMACHINE_crownbay = "yocto/standard/crownbay" This append file adds "crownbay" as a compatible machine, and additionally sets a Yocto Kernel-specific variable that identifies the name of the @@ -371,7 +371,7 @@ KMACHINE_crownbay = "crownbay" For example, suppose you had a set of configuration options in a file called defconfig. If you put that file inside a directory named - /linux-yocto-stable and then added + /linux-yocto and then added a SRC_URI statement such as the following to the append file, those configuration options will be picked up and applied when the kernel is built. @@ -397,7 +397,7 @@ SRC_URI += "file://defconfig \ Other methods exist to accomplish grouping and defining configuration options. For example, you could directly add configuration options to the Yocto kernel - wrs_meta branch for your BSP. + meta branch for your BSP. The configuration options will likely end up in that location anyway if the BSP gets added to the Yocto Project. For information on how to add these configurations directly, see the @@ -407,7 +407,7 @@ SRC_URI += "file://defconfig \ In general, however, the Yocto Project maintainers take care of moving the SRC_URI-specified - configuration options to the wrs_meta branch. + configuration options to the meta branch. Not only is it easier for BSP developers to not have to worry about putting those configurations in the branch, but having the maintainers do it allows them to apply 'global' knowledge about the kinds of common configuration options multiple BSPs in -- cgit v1.2.3