summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-05-17 11:28:25 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-05-17 18:14:06 +0100
commita106f4145c5a9d98a288311042372290a7ffdbea (patch)
treeb7a7084fa752eb22fabb2e56744ba49ef983e90f
parentcf3d261f3ef8bb81477cb873df59bdb7b07fd7b7 (diff)
downloadpoky-a106f4145c5a9d98a288311042372290a7ffdbea.tar.gz
documentation/bsp-guide/bsp.xml: Updated /binary explanation
In the '1.1.3 Pre-built User Binaries' section it said that the ADT and minimal images were kept in the optional meta-<bsp_name>/binary directory. Jianjun Xu pointed out that in fact it is just the minimal and sato images here. I also confirmed with Tom as well. I re-wrote this sentence to be clearer and more accurate. (From yocto-docs rev: 6757abff52841b5d1e1991ab22314fa7a243a87d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/bsp-guide/bsp.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 885e952de7..443d4427c6 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -162,8 +162,8 @@ meta-&lt;bsp_name&gt;/binary/&lt;bootable_images&gt;
162 <para> 162 <para>
163 This optional area contains useful pre-built kernels and user-space filesystem 163 This optional area contains useful pre-built kernels and user-space filesystem
164 images appropriate to the target system. 164 images appropriate to the target system.
165 This directory contains the Application Development Toolkit (ADT) and minimal 165 This directory typically contains graphical (e.g. sato) and minimal live images
166 live images when the BSP tarball has been created and made available in the Yocto Project website. 166 when the BSP tarball has been created and made available in the Yocto Project website.
167 You can use these kernels and images to get a system running and quickly get started 167 You can use these kernels and images to get a system running and quickly get started
168 on development tasks. 168 on development tasks.
169 </para> 169 </para>