diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2010-12-15 13:26:13 -0800 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-12-21 12:49:43 +0000 |
| commit | b3b9476dc5a2886130893523bd7b00635c9139b6 (patch) | |
| tree | febc3edcfd7eb8072f62be6f0d730b180ff97a98 /documentation/bsp-guide/bsp.xml | |
| parent | e71027eaf2636dd94e4f09c86264589511f0ccd6 (diff) | |
| download | openembedded-core-b3b9476dc5a2886130893523bd7b00635c9139b6.tar.gz openembedded-core-b3b9476dc5a2886130893523bd7b00635c9139b6.tar.bz2 openembedded-core-b3b9476dc5a2886130893523bd7b00635c9139b6.zip | |
documentation/bsp-guide/bsp.xml: Updated the Pre-built User Binaries section.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Diffstat (limited to 'documentation/bsp-guide/bsp.xml')
| -rw-r--r-- | documentation/bsp-guide/bsp.xml | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index fcf10a6715..397ef85e77 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -157,7 +157,10 @@ meta-<bsp_name>/README </section> <section id="bsp-filelayout-binary"> - <title>Pre-built User Binaries (meta-<bsp_name>/binary/*)</title> + <title>Pre-built User Binaries</title> + <programlisting> +meta-<bsp_name>/binary/<bootable_images> + </programlisting> <para> This optional area contains useful pre-built kernels and userspace filesystem @@ -165,10 +168,13 @@ meta-<bsp_name>/README This directory contains the Application Development Toolkit (ADT) and minimal live images when the BSP is has been "tar-balled" and placed on the Yocto Project website. You can use these kernels and images to get a system running and quickly get started - on development tasks. + on development tasks. + </para> + + <para> The exact types of binaries present are highly hardware-dependent. - However, a README file should be present that explains how to use the kernels and - images with the target hardware. + However, a README file should be present in the BSP file structure that explains how to use + the kernels and images with the target hardware. If pre-built binaries are present, source code to meet licensing requirements must also be provided in some form. </para> |