summaryrefslogtreecommitdiffstats
path: root/documentation/bsp-guide
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-10-03 13:14:08 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-04 13:08:16 (GMT)
commit81ce4a9015d5f06c23f807860c3a95dbf9448d69 (patch)
treee3e5d2a5b0506c7b154e67f2ff747aced07ba282 /documentation/bsp-guide
parent1eb01b66614912aa8fad63349953c3a7da6da4cc (diff)
downloadpoky-81ce4a9015d5f06c23f807860c3a95dbf9448d69.tar.gz
documentation: bsp-guide - Changed Source Directory capitalization.
The term should be initially capitalized. (From yocto-docs rev: 38a11d512bfe675319fb76da9d7618315af91c47) 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.xml18
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 91b1be0..3cb65c2 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -388,7 +388,7 @@
388 <para> 388 <para>
389 Tuning files are found in the <filename>meta/conf/machine/include</filename> 389 Tuning files are found in the <filename>meta/conf/machine/include</filename>
390 directory within the 390 directory within the
391 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. 391 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
392 Tuning files can also reside in the BSP Layer itself. 392 Tuning files can also reside in the BSP Layer itself.
393 For example, the <filename>ia32-base.inc</filename> file resides in the 393 For example, the <filename>ia32-base.inc</filename> file resides in the
394 <filename>meta-intel</filename> BSP Layer in <filename>conf/machine/include</filename>. 394 <filename>meta-intel</filename> BSP Layer in <filename>conf/machine/include</filename>.
@@ -440,7 +440,7 @@
440 formfactor recipe 440 formfactor recipe
441 <filename>meta/recipes-bsp/formfactor/formfactor_0.0.bb</filename>, 441 <filename>meta/recipes-bsp/formfactor/formfactor_0.0.bb</filename>,
442 which is found in the 442 which is found in the
443 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. 443 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
444 </para></note> 444 </para></note>
445 </section> 445 </section>
446 446
@@ -485,7 +485,7 @@
485 </para> 485 </para>
486 <para> 486 <para>
487 For your BSP, you typically want to use an existing Yocto Project kernel recipe found in the 487 For your BSP, you typically want to use an existing Yocto Project kernel recipe found in the
488 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink> 488 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
489 at <filename>meta/recipes-kernel/linux</filename>. 489 at <filename>meta/recipes-kernel/linux</filename>.
490 You can append your specific changes to the kernel recipe by using a 490 You can append your specific changes to the kernel recipe by using a
491 similarly named append file, which is located in the BSP Layer (e.g. 491 similarly named append file, which is located in the BSP Layer (e.g.
@@ -557,7 +557,7 @@
557 to ensure the build process uses the <filename>standard/default/crownbay</filename> 557 to ensure the build process uses the <filename>standard/default/crownbay</filename>
558 kernel branch. 558 kernel branch.
559 Finally, the append file points to the specific top commits in the 559 Finally, the append file points to the specific top commits in the
560 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink> Git 560 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> Git
561 repository and the <filename>meta</filename> Git repository branches to identify the 561 repository and the <filename>meta</filename> Git repository branches to identify the
562 exact kernel needed to build the Crown Bay BSP. 562 exact kernel needed to build the Crown Bay BSP.
563 </para> 563 </para>
@@ -706,7 +706,7 @@
706 <filename>recipe-*</filename> subdirectory. 706 <filename>recipe-*</filename> subdirectory.
707 You can find <filename>recipes.txt</filename> in the 707 You can find <filename>recipes.txt</filename> in the
708 <filename>meta</filename> directory of the 708 <filename>meta</filename> directory of the
709 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>, 709 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
710 or in the OpenEmbedded Core Layer 710 or in the OpenEmbedded Core Layer
711 (<filename>openembedded-core</filename>) found at 711 (<filename>openembedded-core</filename>) found at
712 <ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>. 712 <ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>.
@@ -714,7 +714,7 @@
714 <para>Within any particular <filename>recipes-*</filename> category, the layout 714 <para>Within any particular <filename>recipes-*</filename> category, the layout
715 should match what is found in the OpenEmbedded Core 715 should match what is found in the OpenEmbedded Core
716 Git repository (<filename>openembedded-core</filename>) 716 Git repository (<filename>openembedded-core</filename>)
717 or the source directory (<filename>poky</filename>). 717 or the Source Directory (<filename>poky</filename>).
718 In other words, make sure you place related files in appropriately 718 In other words, make sure you place related files in appropriately
719 related <filename>recipes-*</filename> subdirectories specific to the 719 related <filename>recipes-*</filename> subdirectories specific to the
720 recipe's function, or within a subdirectory containing a set of closely-related 720 recipe's function, or within a subdirectory containing a set of closely-related
@@ -1017,8 +1017,8 @@
1017 1017
1018 <para> 1018 <para>
1019 The following sections describe the common location and help features as well 1019 The following sections describe the common location and help features as well
1020 as details for the <filename>yocto-bsp</filename> and <filename>yocto-kernel</filename> 1020 as provides details for the
1021 tools. 1021 <filename>yocto-bsp</filename> and <filename>yocto-kernel</filename> tools.
1022 </para> 1022 </para>
1023 1023
1024 <section id='common-features'> 1024 <section id='common-features'>
@@ -1037,7 +1037,7 @@
1037 1037
1038 <para> 1038 <para>
1039 Both tools reside in the <filename>scripts/</filename> subdirectory 1039 Both tools reside in the <filename>scripts/</filename> subdirectory
1040 of the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. 1040 of the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
1041 Consequently, to use the scripts, you must <filename>source</filename> the 1041 Consequently, to use the scripts, you must <filename>source</filename> the
1042 environment just as you would when invoking a build: 1042 environment just as you would when invoking a build:
1043 <literallayout class='monospaced'> 1043 <literallayout class='monospaced'>