summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/bsp-guide/bsp.xml13
1 files changed, 5 insertions, 8 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index d467ceb8fa..e9143a159a 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -48,7 +48,7 @@
48 This root is what you add to the 48 This root is what you add to the
49 <ulink url='&YOCTO_DOCS_REF_URL;#var-BBLAYERS'><filename>BBLAYERS</filename></ulink> 49 <ulink url='&YOCTO_DOCS_REF_URL;#var-BBLAYERS'><filename>BBLAYERS</filename></ulink>
50 variable in the <filename>conf/bblayers.conf</filename> file found in the 50 variable in the <filename>conf/bblayers.conf</filename> file found in the
51 <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-build-directory'>Yocto Project Build Directory</ulink>. 51 Yocto Project Build Directory.
52 Adding the root allows the Yocto Project build system to recognize the BSP 52 Adding the root allows the Yocto Project build system to recognize the BSP
53 definition and from it build an image. 53 definition and from it build an image.
54 Here is an example: 54 Here is an example:
@@ -614,8 +614,7 @@
614 The configuration options will likely end up in that location anyway if the BSP gets 614 The configuration options will likely end up in that location anyway if the BSP gets
615 added to the Yocto Project. 615 added to the Yocto Project.
616 For information on how to add these configurations directly, see 616 For information on how to add these configurations directly, see
617 <ulink url='http://yoctoproject.org/docs/1.1.1/kernel-manual/kernel-manual.html'> 617 <ulink url='&YOCTO_DOCS_KERNEL_URL;'>The Yocto Project Kernel Architecture and Use Manual</ulink>.</para>
618 The Yocto Project Kernel Architecture and Use Manual</ulink>.</para>
619 <para> 618 <para>
620 In general, however, the Yocto Project maintainers take care of moving the 619 In general, however, the Yocto Project maintainers take care of moving the
621 <filename>SRC_URI</filename>-specified 620 <filename>SRC_URI</filename>-specified
@@ -695,8 +694,7 @@
695 <filename>recipe-*</filename> subdirectory. 694 <filename>recipe-*</filename> subdirectory.
696 You can find <filename>recipes.txt</filename> in the 695 You can find <filename>recipes.txt</filename> in the
697 <filename>meta</filename> directory of the 696 <filename>meta</filename> directory of the
698 <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-files'>Yocto 697 Yocto Project Files, or in the OpenEmbedded Core Layer
699 Project Files</ulink>, or in the OpenEmbedded Core Layer
700 (<filename>openembedded-core</filename>) found at 698 (<filename>openembedded-core</filename>) found at
701 <ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>. 699 <ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>.
702 </para> 700 </para>
@@ -835,7 +833,7 @@
835 Basing your recipes on these kernels reduces the costs for maintaining 833 Basing your recipes on these kernels reduces the costs for maintaining
836 the BSP and increases its scalability. 834 the BSP and increases its scalability.
837 See the <filename>Yocto Linux Kernel</filename> category in the 835 See the <filename>Yocto Linux Kernel</filename> category in the
838 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'><filename>Yocto Source Repositories</filename></ulink> 836 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'>Yocto Source Repositories</ulink>
839 for these kernels.</para></listitem> 837 for these kernels.</para></listitem>
840 </itemizedlist> 838 </itemizedlist>
841 </para> 839 </para>
@@ -1027,8 +1025,7 @@
1027 1025
1028 <para> 1026 <para>
1029 Both tools reside in the <filename>scripts/</filename> subdirectory 1027 Both tools reside in the <filename>scripts/</filename> subdirectory
1030 of the <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-files'>Yocto Project 1028 of the Yocto Project Files.
1031 Files</ulink>.
1032 Consequently, to use the scripts, you must <filename>source</filename> the 1029 Consequently, to use the scripts, you must <filename>source</filename> the
1033 environment just as you would when invoking a build: 1030 environment just as you would when invoking a build:
1034 <literallayout class='monospaced'> 1031 <literallayout class='monospaced'>