summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/bsp-guide/bsp.xml30
1 files changed, 15 insertions, 15 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 5ff80da773..4ea3b130ec 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -28,12 +28,12 @@
28 </para> 28 </para>
29 29
30 <para> 30 <para>
31 The proposed format does have elements that are specific to the Poky and 31 The proposed format does have elements that are specific to the Yocto Project and
32 OpenEmbedded build systems. 32 OpenEmbedded build systems.
33 It is intended that this information can be 33 It is intended that this information can be
34 used by other systems besides Poky and OpenEmbedded and that it will be simple 34 used by other systems besides Yocto Project and OpenEmbedded and that it will be simple
35 to extract information and convert it to other formats if required. 35 to extract information and convert it to other formats if required.
36 Poky, through its standard layers mechanism, can directly accept the format 36 Yocto Project, through its standard layers mechanism, can directly accept the format
37 described as a layer. 37 described as a layer.
38 The BSP captures all 38 The BSP captures all
39 the hardware-specific details in one place in a standard format, which is 39 the hardware-specific details in one place in a standard format, which is
@@ -86,7 +86,7 @@
86 </literallayout> 86 </literallayout>
87 For more detailed information on layers, see the 87 For more detailed information on layers, see the
88 <ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-changes-layers'> 88 <ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-changes-layers'>
89 BitBake Layers</ulink> section of the Poky Reference Manual. 89 BitBake Layers</ulink> section of the Yocto Project Reference Manual.
90 </para> 90 </para>
91 91
92 <para> 92 <para>
@@ -204,8 +204,8 @@ meta-&lt;bsp_name&gt;/conf/layer.conf
204 </programlisting> 204 </programlisting>
205 205
206 <para> 206 <para>
207 This file identifies the structure as a Poky layer, identifies the 207 This file identifies the structure as a Yocto Project layer, identifies the
208 contents of the layer, and contains information about how Poky should use it. 208 contents of the layer, and contains information about how Yocto Project should use it.
209 Generally, a standard boilerplate file such as the following works. 209 Generally, a standard boilerplate file such as the following works.
210 In the following example you would replace "bsp" and "_bsp" with the actual name 210 In the following example you would replace "bsp" and "_bsp" with the actual name
211 of the BSP (i.e. &lt;bsp_name&gt; from the example template). 211 of the BSP (i.e. &lt;bsp_name&gt; from the example template).
@@ -228,7 +228,7 @@ BBFILE_PRIORITY_bsp = "5"
228 228
229 <para> 229 <para>
230 This file simply makes BitBake aware of the recipes and configuration directories. 230 This file simply makes BitBake aware of the recipes and configuration directories.
231 This file must exist so that Poky can recognize the BSP. 231 This file must exist so that the Yocto Project build system can recognize the BSP.
232 </para> 232 </para>
233 </section> 233 </section>
234 234
@@ -240,7 +240,7 @@ meta-&lt;bsp_name&gt;/conf/machine/*.conf
240 240
241 <para> 241 <para>
242 The machine files bind together all the information contained elsewhere 242 The machine files bind together all the information contained elsewhere
243 in the BSP into a format that Poky can understand. 243 in the BSP into a format that the Yocto Project build system can understand.
244 If the BSP supports multiple machines, multiple machine configuration files 244 If the BSP supports multiple machines, multiple machine configuration files
245 can be present. 245 can be present.
246 These filenames correspond to the values to which users have set the MACHINE variable. 246 These filenames correspond to the values to which users have set the MACHINE variable.
@@ -278,10 +278,10 @@ TARGET_CC_ARCH = "-m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse"
278 <para> 278 <para>
279 The tune file would be included by the machine definition and can be 279 The tune file would be included by the machine definition and can be
280 contained in the BSP or referenced from one of the standard core set of 280 contained in the BSP or referenced from one of the standard core set of
281 files included with Poky itself. 281 files included with the Yocto Project.
282 </para> 282 </para>
283 <para> 283 <para>
284 Both the base package architecture file and the tune file are optional for a Poky BSP layer. 284 Both the base package architecture file and the tune file are optional for a BSP layer.
285 </para> 285 </para>
286 </section> 286 </section>
287 287
@@ -343,8 +343,8 @@ meta-&lt;bsp_name&gt;/recipes-kernel/linux/linux-yocto_git.bbappend
343 This file appends your specific changes to the kernel you are using. 343 This file appends your specific changes to the kernel you are using.
344 </para> 344 </para>
345 <para> 345 <para>
346 For your BSP you typically want to use an existing Poky kernel found in the 346 For your BSP you typically want to use an existing Yocto Project kernel found in the
347 Poky repository at <filename class='directory'>meta/recipes-kernel/kernel</filename>. 347 Yocto Project repository at <filename class='directory'>meta/recipes-kernel/kernel</filename>.
348 You can append your specific changes to the kernel recipe by using an append file, 348 You can append your specific changes to the kernel recipe by using an append file,
349 which is located in the 349 which is located in the
350 <filename class='directory'>meta-&lt;bsp_name&gt;/recipes-kernel/linux</filename> 350 <filename class='directory'>meta-&lt;bsp_name&gt;/recipes-kernel/linux</filename>
@@ -542,7 +542,7 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}"
542 upon the user a requirement to accept the terms of a 542 upon the user a requirement to accept the terms of a
543 'click-through' license. 543 'click-through' license.
544 Once the license is accepted the 544 Once the license is accepted the
545 Poky build system can then build and include the 545 Yocto Project build system can then build and include the
546 corresponding component in the final BSP image. 546 corresponding component in the final BSP image.
547 Some affected components might be essential to the normal 547 Some affected components might be essential to the normal
548 functioning of the system and have no 'free' replacement 548 functioning of the system and have no 'free' replacement
@@ -574,7 +574,7 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}"
574 </para> 574 </para>
575 575
576 <para> 576 <para>
577 Several methods exist within the Poky build system to satisfy the licensing 577 Several methods exist within the Yocto Project build system to satisfy the licensing
578 requirements for an encumbered BSP. 578 requirements for an encumbered BSP.
579 The following list describes them in preferential order: 579 The following list describes them in preferential order:
580 </para> 580 </para>
@@ -644,7 +644,7 @@ FILESEXTRAPATHS := "${THISDIR}/${PN}"
644 These prompts usually take the form of instructions 644 These prompts usually take the form of instructions
645 needed to manually fetch the encumbered package(s) 645 needed to manually fetch the encumbered package(s)
646 and md5 sums into the required directory 646 and md5 sums into the required directory
647 (e.g. the <filename>poky/build/downloads</filename>). 647 (e.g. the <filename>yocto/build/downloads</filename>).
648 Once the manual package fetch has been 648 Once the manual package fetch has been
649 completed, restart the build to continue where 649 completed, restart the build to continue where
650 it left off. 650 it left off.