From e04e02cd4671848e481328c6443cf0f89ca75cfe Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 11 Aug 2011 10:29:20 -0700 Subject: documentation/dev-manual: Changed 2.6.37 to 3.0 for 1.1 release. Bruce Ashfield's review comments indicated that we will be using linux-yocto-3.0 and not linux-yocto-2.6.37. So I am putting these changes in to anticipate the 1.1 release. (From yocto-docs rev: ecbe1c90c5aa65b2dde77ba6094b5956e37d061d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-bsp-appendix.xml | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) (limited to 'documentation/dev-manual/dev-manual-bsp-appendix.xml') diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index 6a3598543f..97ceb12744 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -173,7 +173,7 @@ PREFERRED_PROVIDER_virtual/kernel statement. This statement identifies the kernel that the BSP is going to use. In this case the BSP is using linux-yocto, which is the - current Linux Yocto kernel based on the Linux 2.6.37 release. + current Linux Yocto kernel based on the Linux 3.0 release. @@ -300,7 +300,7 @@ The recipe for that kernel is not located in the BSP layer but rather in the local Yocto Project files at meta/recipes-kernel/linux and is - named linux-yocto_2.6.37.bb. + named linux-yocto_3.0.bb. The SRCREV_machine and SRCREV_meta statements point to the exact commits used by the Yocto Project development team in their source repositories that identify the right kernel for our hardware. @@ -309,7 +309,7 @@ However, in the meta-mymachine layer in recipes-kernel/linux resides a .bbappend - file named linux-yocto_2.6.37.bbappend that + file named linux-yocto_3.0.bbappend that is appended to the recipe of the same name in meta/recipes-kernel/link. Thus, the SRCREV statements in the "append" file override the more general statements found in meta. @@ -343,7 +343,7 @@ - To fix this situation in linux-yocto_2.6.37.bbappend + To fix this situation in linux-yocto_3.0.bbappend we delete the two SRCREV statements that support EMGD (the top pair). We also change the remaining pair to specify mymachine @@ -364,8 +364,9 @@ exact commit strings in the Yocto Project source repositories you need to change the SRCREV statements. You can find all the machine and meta - branch points (commits) for the linux-yocto-2.6.37 kernel - here. + branch points (commits) for the linux-yocto-3.0 kernel + here + [WRITER's NOTE: Need new link to the 3.0 source repo area when it is available]. @@ -376,7 +377,7 @@ branch Click on the commit column header to view the top commit Copy the commit string for use in the - linux-yocto_2.6.37.bbappend file + linux-yocto_3.0.bbappend file @@ -387,14 +388,14 @@ - Also in the linux-yocto_2.6.37.bbappend file are + Also in the linux-yocto_3.0.bbappend file are COMPATIBLE_MACHINE, KMACHINE, and KERNEL_FEATURES statements. Two sets of these exist: one set supports EMGD and one set does not. Because we are not interested in supporting EMGD those three can be deleted. The remaining three must be changed so that mymachine replaces crownbay-noemgd and crownbay. - Here is the final linux-yocto_2.6.37.bbappend file after all + Here is the final linux-yocto_3.0.bbappend file after all the edits: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" -- cgit v1.2.3-54-g00ecf