From 1ea2c63bf53d25892f407e341c77cf13927f9329 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 3 Oct 2011 11:41:12 -0700 Subject: [PATCH] documentation/dev-manual/dev-manual-bsp-appendix.xml: scrubbed example I changed several small things in the example as I worked through it once again. The commit IDs changed for using the atom-pc kernel. Also the command to build the sato image can no longer use 'live'. (From yocto-docs rev: faff1e7f21b5059dfe708c6a3d83116c7349fe55) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-bsp-appendix.xml | 67 ++++++++++--------- 1 file changed, 34 insertions(+), 33 deletions(-) diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index 9c7d5b6a72..86f6f20164 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml @@ -40,14 +40,14 @@ $ git branch -a $ git tag -l - For this example we are going to use the Yocto Project 1.1 Release, - which maps to the 1.1 branch in the repository. - These commands create a local branch named 1.1 + For this example we are going to use the Yocto Project 1.1 Release, which is code + named "edison". + These commands create a local branch named edison that tracks the remote branch of the same name. $ cd poky - $ git checkout -b 1.1 origin/1.1 - Switched to a new branch '1.1' + $ git checkout -b edison origin/edison + Switched to a new branch 'edison' @@ -56,7 +56,8 @@ Choosing a Base BSP - For this example, the base BSP is the Intel Atom Processor E660 with Intel Platform + For this example, the base BSP is the Intel + Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit, which is otherwise referred to as "Crown Bay." The BSP layer is meta-crownbay. @@ -73,7 +74,7 @@ You need to have the base BSP layer on your development system. - Like the local Yocto Project files, you can get the BSP + Similar to the local Yocto Project files, you can get the BSP layer one of two ways: download the BSP tarball and extract it, or set up a local Git repository that has the Yocto Project BSP layers. @@ -83,7 +84,7 @@ - This example assumes a local meta-intel Git repository + This example assumes the local meta-intel Git repository is inside the local poky Git repository. The meta-intel Git repository contains all the metadata that supports BSP creation. @@ -92,11 +93,11 @@ Because meta-intel is its own Git repository, you will want to be sure you are in the appropriate branch for your work. - For this example we are going to use the 1.1 branch. + For this example we are going to use the edison branch. $ cd meta-intel - $ git checkout -b 1.1 origin/1.1 - Switched to a new branch 'bernard' + $ git checkout -b edison origin/edison + Switched to a new branch 'edison' @@ -105,14 +106,14 @@ Making a Copy of the Base BSP to Create Your New BSP Layer - Now that you have the local Yocto Project files and the base BSP files you need to create a + Now that you have the local Yocto Project files and the base BSP files, you need to create a new layer for your BSP. - To create your BSP layer you simply copy the meta-crownbay + To create your BSP layer, you simply copy the meta-crownbay layer to a new layer. - For this example the new layer will be named meta-mymachine. + For this example, the new layer will be named meta-mymachine. The name must follow the BSP layer naming convention, which is meta-<name>. The following example assumes your working directory is meta-intel @@ -148,7 +149,7 @@ - First, since in this example the new BSP will not support EMGD we will get rid of the + First, since in this example the new BSP will not support EMGD, we will get rid of the crownbay.conf file and then rename the crownbay-noemgd.conf file to mymachine.conf. Much of what we do in the configuration directory is designed to help the Yocto Project @@ -172,7 +173,7 @@ Note that inside the mymachine.conf is the 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 + In this case, the BSP is using linux-yocto, which is the current Linux Yocto kernel based on the Linux 3.0 release. @@ -180,8 +181,9 @@ The next configuration file in the new BSP layer we need to edit is layer.conf. This file identifies build information needed for the new layer. You can see the - - Layer Configuration File section in the Board Support Packages (BSP) Development Guide + "Layer Configuration File" section in + The Board + Support Packages (BSP) Development Guide for more information on this configuration file. Basically, we are changing the existing statements to work with our BSP. @@ -212,10 +214,10 @@ Now we will take a look at the recipes in your new layer. The standard BSP structure has areas for BSP, graphics, core, and kernel recipes. - When you create a BSP you use these areas for appropriate recipes and append files. + When you create a BSP, you use these areas for appropriate recipes and append files. Recipes take the form of .bb files. If you want to leverage the existing recipes the Yocto Project build system uses - but change those recipes you can use .bbappend files. + but change those recipes, you can use .bbappend files. All new recipes and append files for your layer must go in the layer’s recipes-bsp, recipes-kernel, recipes-core, and @@ -321,14 +323,14 @@ Here are the statements: SRCREV_machine_pn-linux-yocto_crownbay ?= \ - "372c0ab135978bd8ca3a77c88816a25c5ed8f303" + "2247da9131ea7e46ed4766a69bb1353dba22f873" SRCREV_meta_pn-linux-yocto_crownbay ?= \ - "d5d3c6480d61f83503ccef7fbcd765f7aca8b71b" + "67a46a608f47c19f16995be7de7b272025864b1b" SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= \ - "372c0ab135978bd8ca3a77c88816a25c5ed8f303" + "2247da9131ea7e46ed4766a69bb1353dba22f873" SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= \ - "d5d3c6480d61f83503ccef7fbcd765f7aca8b71b" + "67a46a608f47c19f16995be7de7b272025864b1b" @@ -345,7 +347,7 @@ To fix this situation in linux-yocto_3.0.bbappend we delete the two SRCREV statements that support - EMGD (the top pair). + EMGD (the top pair). We also change the remaining pair to specify mymachine and insert the commit identifiers to identify the kernel in which we are interested, which will be based on the atom-pc-standard @@ -353,9 +355,9 @@ Here are the final SRCREV statements: SRCREV_machine_pn-linux-yocto_mymachine ?= \ - "fce17f046d3756045e4dfb49221d1cf60fcae329" + "06c798f25a19281d7fa944b14366dd75820ba009" SRCREV_meta_pn-linux-yocto_mymachine ?= \ - "84f1a422d7e21fbc23a687035bdf9d42471f19e0" + "67a46a608f47c19f16995be7de7b272025864b1b" @@ -364,9 +366,8 @@ 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-3.0 kernel - here - [WRITER's NOTE: Need new link to the 3.0 source repo area when it is available]. + branch points (commits) for the linux-yocto-3.0 kernel at + . @@ -405,9 +406,9 @@ KERNEL_FEATURES_append_mymachine += " cfg/smp.scc" SRCREV_machine_pn-linux-yocto_mymachine ?= \ - "fce17f046d3756045e4dfb49221d1cf60fcae329" + "06c798f25a19281d7fa944b14366dd75820ba009" SRCREV_meta_pn-linux-yocto_mymachine ?= \ - "84f1a422d7e21fbc23a687035bdf9d42471f19e0" + "67a46a608f47c19f16995be7de7b272025864b1b" @@ -502,7 +503,7 @@ For example, moving your working directory around could cause problems. Here is the command for this example: - $ bitbake –k core-image-sato-live + $ bitbake -k core-image-sato