summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-07-27 09:06:05 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-04 15:06:46 +0100
commit0dbc9ba6119384a6fad8c0b33035b7e5bf483e07 (patch)
tree5a04a9aeca04bea86252bf2f38fec7cc3c6a0c77
parent9709d1315d510f53e14f0bd19a875ebba3107b8f (diff)
downloadpoky-0dbc9ba6119384a6fad8c0b33035b7e5bf483e07.tar.gz
documentation/dev-manual/dev-manual-bsp-appendix.xml: re-wrote the Base BSP
I re-wrote the Getting your Base BSP section to reflect the example only. Previously, there was a lot of information in there about getting BSP files that was deemed universal and was moved to the getting started chapter. (From yocto-docs rev: addcbca37e3dfad27b388245a4085cd0a2747177) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-bsp-appendix.xml44
1 files changed, 6 insertions, 38 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index 84fb541598..e9f4cb022a 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -90,51 +90,19 @@
90 download the BSP tarball and extract it, or set up a local Git repository that 90 download the BSP tarball and extract it, or set up a local Git repository that
91 has the Yocto Project BSP layers. 91 has the Yocto Project BSP layers.
92 You should use the same method that you used to get the local Yocto Project files earlier. 92 You should use the same method that you used to get the local Yocto Project files earlier.
93 See the <xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual
94 for information on how to get the BSP files.
93 </para> 95 </para>
94 96
95 <para>
96 If you are using tarball extraction, simply download the tarball for the base
97 BSP you chose in the previous step and then extract it into any directory
98 you choose using the tar command.
99 Upon extraction, the BSP source directory (layer) will be named
100 <filename>meta-&lt;BSP_name&gt;</filename>.
101 The following command extracts the Crown Bay BSP into the current directory and names it
102 <filename>meta-crownbay</filename>:
103 <literallayout class='monospaced'>
104 $ tar xjf crownbay-noemgd-1.1.tar.bz2
105 </literallayout>
106 </para>
107
108 <para> 97 <para>
109 If you cloned a <filename>poky</filename> Git repository 98 This example assumes a local <filename>meta-intel</filename> Git repository
110 then you need to set up a different local Git repository 99 inside the local <filename>poky</filename> Git repository.
111 (<filename>meta-intel</filename>) for the BSP.
112 The <filename>meta-intel</filename> Git repository contains all the metadata 100 The <filename>meta-intel</filename> Git repository contains all the metadata
113 that supports BSP creation. 101 that supports BSP creation.
114 When you set up the <filename>meta-intel</filename> Git repository you can
115 set it up anywhere you want.
116 We will set up the repository inside the
117 <filename>poky</filename> Git repository in this example.
118 </para>
119
120 <para>
121 The following transcript shows the steps to clone the <filename>meta-intel</filename>
122 Git repository inside the <filename>poky</filename> Git repository created earlier in this
123 example.
124 <literallayout class='monospaced'>
125 $cd poky
126 $ git clone git://git.yoctoproject.org/meta-intel.git
127 Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/
128 remote: Counting objects: 1325, done.
129 remote: Compressing objects: 100% (1078/1078), done.
130 remote: Total 1325 (delta 546), reused 85 (delta 27)
131 Receiving objects: 100% (1325/1325), 1.56 MiB | 330 KiB/s, done.
132 Resolving deltas: 100% (546/546), done.
133 </literallayout>
134 </para> 102 </para>
135 103
136 <para> 104 <para>
137 Because <filename>meta-intel</filename> is its own Git repository you will want 105 Because <filename>meta-intel</filename> is its own Git repository, you will want
138 to be sure you are in the appropriate branch for your work. 106 to be sure you are in the appropriate branch for your work.
139 For this example we are going to use the <filename>1.1</filename> branch. 107 For this example we are going to use the <filename>1.1</filename> branch.
140 <literallayout class='monospaced'> 108 <literallayout class='monospaced'>