From b214cdc7e8105c59c806042d5d994216de409025 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 31 Aug 2011 12:28:54 -0700 Subject: documentation/bsp-guide/bsp.xml: Edits for Crownbay example in kernel recipes Because the Crownbay uses both EMGD and non-EMGD statments in the linux-yocto_3.0.bbappend file I had to do some explaining. It turns out you don't really need to just delete or comment out the non-applicable statements. I also adjusted some wording around the tuning file example. This file I assumed was in the conf directory of the meta-crownbay directory. It is really in the meta/conf/machine/include directory. (From yocto-docs rev: 3f82656f7ffb392333f8cf59abf1414af5da512b) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/bsp-guide/bsp.xml | 44 ++++++++++++++++++----------------------- 1 file changed, 19 insertions(+), 25 deletions(-) diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 0dcb4737e9..bd2ef8bba3 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -320,29 +320,23 @@ - This directory could also contain shared hardware "tuning" definitions that are commonly used to - pass specific optimization flags to the compiler. - An example is tune-atom.inc: + This crownbay.conf file could also include + a hardware "tuning" file that is commonly used to + define the the package architecture and specify + optimization flags, which are carefully chosen to give best + performance on a given processor. + + Tuning files are found in the meta/conf/machine/include + directory. + To use them, you simply include them in the machine configuration file. + For example, the Crown Bay BSP crownbay.conf has the + following statement: - BASE_PACKAGE_ARCH = "core2" - TARGET_CC_ARCH = "-m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse" + include conf/machine/include/tune-atom.inc - - This example defines a new package architecture called "core2" and uses the - specified optimization flags, which are carefully chosen to give best - performance on atom processors. - - - The tune file would be included by the machine definition and can be - contained in the BSP or referenced from one of the standard core set of - files included with the Yocto Project. - - - Both the base package architecture file and the tune file are optional for a BSP layer. -
@@ -457,12 +451,12 @@ SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "6b4b9acde5fb0ff66ae58fa98274bfe631501499" SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "5b535279e61197cb194bb2dfceb8b7a04128387c" - This append file contains statements used to support the Crown Bay BSP that both - supports and does not support the Intel EMGD. - If, for example, you were going to build the BSP that did not support Intel EMGD, - you would simply comment out or delete the statements that support building - Crown Bay with Intel EMGD support. - So, the linux-yocto_3.0.bbappend could be as follows: + This append file contains statements used to support the Crown Bay BSP for both + Intel EMGD and non-EMGD. + 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 + file are follows: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" @@ -473,7 +467,7 @@ SRCREV_machine_pn-linux-yocto_crownbay ?= "6b4b9acde5fb0ff66ae58fa98274bfe631501499" SRCREV_meta_pn-linux-yocto_crownbay ?= "5b535279e61197cb194bb2dfceb8b7a04128387c" - The append file defines "crownbay" as the compatible machine, + The append file defines crownbay as the compatible machine, defines the KMACHINE, points to some configuration fragments to use by setting the KERNEL_FEATURES variable, and then points to the specific commits in the Yocto Project files Git repository and the -- cgit v1.2.3-54-g00ecf