summaryrefslogtreecommitdiffstats
path: root/documentation/bsp-guide
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-08-31 12:28:54 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-09-02 23:38:51 +0100
commitb214cdc7e8105c59c806042d5d994216de409025 (patch)
tree6606b0a1adb595e1fd808f881f24a74fc02df2ab /documentation/bsp-guide
parent4884e38a6c96bd7176911e4d5fcf7c10dd4c5a6c (diff)
downloadpoky-b214cdc7e8105c59c806042d5d994216de409025.tar.gz
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 <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r--documentation/bsp-guide/bsp.xml44
1 files 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 @@
320 </para> 320 </para>
321 321
322 <para> 322 <para>
323 This directory could also contain shared hardware "tuning" definitions that are commonly used to 323 This <filename>crownbay.conf</filename> file could also include
324 pass specific optimization flags to the compiler. 324 a hardware "tuning" file that is commonly used to
325 An example is <filename>tune-atom.inc</filename>: 325 define the the package architecture and specify
326 optimization flags, which are carefully chosen to give best
327 performance on a given processor.
326 </para> 328 </para>
329
327 <para> 330 <para>
331 Tuning files are found in the <filename>meta/conf/machine/include</filename>
332 directory.
333 To use them, you simply include them in the machine configuration file.
334 For example, the Crown Bay BSP <filename>crownbay.conf</filename> has the
335 following statement:
328 <literallayout class='monospaced'> 336 <literallayout class='monospaced'>
329 BASE_PACKAGE_ARCH = "core2" 337 include conf/machine/include/tune-atom.inc
330 TARGET_CC_ARCH = "-m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse"
331 </literallayout> 338 </literallayout>
332 </para> 339 </para>
333 <para>
334 This example defines a new package architecture called "core2" and uses the
335 specified optimization flags, which are carefully chosen to give best
336 performance on atom processors.
337 </para>
338 <para>
339 The tune file would be included by the machine definition and can be
340 contained in the BSP or referenced from one of the standard core set of
341 files included with the Yocto Project.
342 </para>
343 <para>
344 Both the base package architecture file and the tune file are optional for a BSP layer.
345 </para>
346 </section> 340 </section>
347 341
348 <section id='bsp-filelayout-misc-recipes'> 342 <section id='bsp-filelayout-misc-recipes'>
@@ -457,12 +451,12 @@
457 SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "6b4b9acde5fb0ff66ae58fa98274bfe631501499" 451 SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "6b4b9acde5fb0ff66ae58fa98274bfe631501499"
458 SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "5b535279e61197cb194bb2dfceb8b7a04128387c" 452 SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "5b535279e61197cb194bb2dfceb8b7a04128387c"
459 </literallayout> 453 </literallayout>
460 This append file contains statements used to support the Crown Bay BSP that both 454 This append file contains statements used to support the Crown Bay BSP for both
461 supports and does not support the Intel EMGD. 455 Intel EMGD and non-EMGD.
462 If, for example, you were going to build the BSP that did not support Intel EMGD, 456 The build process, in this case, recognizes and uses only the statements that
463 you would simply comment out or delete the statements that support building 457 apply to the defined machine name - <filename>crownbay</filename> in this case.
464 Crown Bay with Intel EMGD support. 458 So, the applicable statements in the <filename>linux-yocto_3.0.bbappend</filename>
465 So, the <filename>linux-yocto_3.0.bbappend</filename> could be as follows: 459 file are follows:
466 <literallayout class='monospaced'> 460 <literallayout class='monospaced'>
467 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" 461 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
468 462
@@ -473,7 +467,7 @@
473 SRCREV_machine_pn-linux-yocto_crownbay ?= "6b4b9acde5fb0ff66ae58fa98274bfe631501499" 467 SRCREV_machine_pn-linux-yocto_crownbay ?= "6b4b9acde5fb0ff66ae58fa98274bfe631501499"
474 SRCREV_meta_pn-linux-yocto_crownbay ?= "5b535279e61197cb194bb2dfceb8b7a04128387c" 468 SRCREV_meta_pn-linux-yocto_crownbay ?= "5b535279e61197cb194bb2dfceb8b7a04128387c"
475 </literallayout> 469 </literallayout>
476 The append file defines "crownbay" as the compatible machine, 470 The append file defines <filename>crownbay</filename> as the compatible machine,
477 defines the <filename>KMACHINE</filename>, points to some configuration fragments 471 defines the <filename>KMACHINE</filename>, points to some configuration fragments
478 to use by setting the <filename>KERNEL_FEATURES</filename> variable, and then points 472 to use by setting the <filename>KERNEL_FEATURES</filename> variable, and then points
479 to the specific commits in the Yocto Project files Git repository and the 473 to the specific commits in the Yocto Project files Git repository and the