summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-bsp-appendix.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-bsp-appendix.xml')
-rw-r--r--documentation/dev-manual/dev-manual-bsp-appendix.xml20
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index fef07e5797..25f74763b1 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -43,7 +43,7 @@
43 $ git clone git://git.yoctoproject.org/poky 43 $ git clone git://git.yoctoproject.org/poky
44 $ cd poky 44 $ cd poky
45 </literallayout> 45 </literallayout>
46 Alternatively, you can start with the downloaded Poky "edison" tarball. 46 Alternatively, you can start with the downloaded Poky "&DISTRO_NAME;" tarball.
47 These commands unpack the tarball into a Yocto Project File directory structure. 47 These commands unpack the tarball into a Yocto Project File directory structure.
48 By default, the top-level directory of the file structure is named 48 By default, the top-level directory of the file structure is named
49 <filename>poky-&YOCTO_POKY;</filename>: 49 <filename>poky-&YOCTO_POKY;</filename>:
@@ -54,7 +54,7 @@
54 <note><para>If you're using the tarball method, you can ignore all the following steps that 54 <note><para>If you're using the tarball method, you can ignore all the following steps that
55 ask you to carry out Git operations. 55 ask you to carry out Git operations.
56 You already have the results of those operations 56 You already have the results of those operations
57 in the form of the edison release tarballs. 57 in the form of the &DISTRO_NAME; release tarballs.
58 Consequently, there is nothing left to do other than extract those tarballs into the 58 Consequently, there is nothing left to do other than extract those tarballs into the
59 proper locations.</para> 59 proper locations.</para>
60 60
@@ -160,7 +160,7 @@
160 $ cd meta-intel 160 $ cd meta-intel
161 </literallayout> 161 </literallayout>
162 Alternatively, you can start with the downloaded Crown Bay tarball. 162 Alternatively, you can start with the downloaded Crown Bay tarball.
163 You can download the edison version of the BSP tarball from the 163 You can download the &DISTRO_NAME; version of the BSP tarball from the
164 <ulink url='&YOCTO_HOME_URL;/download'>Download</ulink> page of the 164 <ulink url='&YOCTO_HOME_URL;/download'>Download</ulink> page of the
165 Yocto Project website. 165 Yocto Project website.
166 Here is the specific link for the tarball needed for this example: 166 Here is the specific link for the tarball needed for this example:
@@ -177,7 +177,7 @@
177 The <filename>meta-intel</filename> directory contains all the metadata 177 The <filename>meta-intel</filename> directory contains all the metadata
178 that supports BSP creation. 178 that supports BSP creation.
179 If you're using the Git method, the following 179 If you're using the Git method, the following
180 step will switch to the edison metadata. 180 step will switch to the &DISTRO_NAME; metadata.
181 If you're using the tarball method, you already have the correct metadata and can 181 If you're using the tarball method, you already have the correct metadata and can
182 skip to the next step. 182 skip to the next step.
183 Because <filename>meta-intel</filename> is its own Git repository, you will want 183 Because <filename>meta-intel</filename> is its own Git repository, you will want
@@ -445,11 +445,11 @@
445 and insert the commit identifiers to identify the kernel in which we 445 and insert the commit identifiers to identify the kernel in which we
446 are interested, which will be based on the <filename>atom-pc-standard</filename> 446 are interested, which will be based on the <filename>atom-pc-standard</filename>
447 kernel. 447 kernel.
448 In this case, because we're working with the edison branch of everything, we 448 In this case, because we're working with the &DISTRO_NAME; branch of everything, we
449 need to use the <filename>SRCREV</filename> values for the atom-pc branch 449 need to use the <filename>SRCREV</filename> values for the atom-pc branch
450 that are associated with the edison release. 450 that are associated with the &DISTRO_NAME; release.
451 To find those values, we need to find the <filename>SRCREV</filename> 451 To find those values, we need to find the <filename>SRCREV</filename>
452 values that edison uses for the atom-pc branch, which we find in the 452 values that &DISTRO_NAME; uses for the atom-pc branch, which we find in the
453 <filename>poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend</filename> 453 <filename>poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend</filename>
454 file. 454 file.
455 </para> 455 </para>
@@ -474,8 +474,8 @@
474 474
475 <para> 475 <para>
476 In this example, we're using the <filename>SRCREV</filename> values we 476 In this example, we're using the <filename>SRCREV</filename> values we
477 found already captured in the edison release because we're creating a BSP based on 477 found already captured in the &DISTRO_NAME; release because we're creating a BSP based on
478 edison. 478 &DISTRO_NAME;.
479 If, instead, we had based our BSP on the master branches, we would want to use 479 If, instead, we had based our BSP on the master branches, we would want to use
480 the most recent <filename>SRCREV</filename> values taken directly from the kernel repo. 480 the most recent <filename>SRCREV</filename> values taken directly from the kernel repo.
481 We will not be doing that for this example. 481 We will not be doing that for this example.
@@ -682,7 +682,7 @@
682 </para> 682 </para>
683 683
684 <para> 684 <para>
685 For reference, the sato image produced by the previous steps for edison 685 For reference, the sato image produced by the previous steps for &DISTRO_NAME;
686 should look like the following in terms of size. 686 should look like the following in terms of size.
687 If your sato image is much different from this, 687 If your sato image is much different from this,
688 you probably made a mistake in one of the above steps: 688 you probably made a mistake in one of the above steps: