diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-04-04 15:16:38 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-04-10 13:32:45 +0100 |
commit | ec33e21004c773df60ad0dc5e0a2d04ff9414d62 (patch) | |
tree | 3701f1644ca32a1a82788c858ef97b77eb348771 /documentation/bsp-guide | |
parent | 273e05bb0db2d3723429e47523deee1c8b302471 (diff) | |
download | openembedded-core-contrib-ec33e21004c773df60ad0dc5e0a2d04ff9414d62.tar.gz |
documentation/bsp-guide/bsp.xml: Edits to intro sections
Adding the new section "Customizing a Recipe for a BSP" has added
enough sections to this book such that the introductory area needed
some attention. I pared down the intro text to basically just
cover the manual's organization and a bit about BSPs. I moved
all the introductory common form stuff into the section that
just addresses the BSP form. This is better organization for the
manual as it is evolving.
(From yocto-docs rev: 9aec4ce47fb090ae2f6c5bed93da03e77ae49a4c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r-- | documentation/bsp-guide/bsp.xml | 68 |
1 files changed, 34 insertions, 34 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index d15abe027d..f12db850fc 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -19,44 +19,15 @@ </para> <para> - This chapter (or document if you are reading the BSP Developer's Guide) defines - a structure for these components - so that BSPs follow a commonly understood layout. - The information here also shows how you can create and manage a + This chapter (or document if you are reading the BSP Developer's Guide) + talks about BSP Layers, defines a structure for components + so that BSPs follow a commonly understood layout, discusses how to customize + a recipe for a BSP, addresses BSP licensing, and provides information that + shows you how to create and manage a <link linkend='bsp-layers'>BSP Layer</link> using two Yocto Project <link linkend='using-the-yocto-projects-bsp-tools'>BSP Tools</link>. </para> - <para> - Providing a common form allows end-users to understand and become familiar - with the layout. - A common form also encourages standardization - of software support of hardware. - </para> - - <para> - The proposed format does have elements that are specific to the Yocto Project and - OpenEmbedded build systems. - It is intended that this information can be - used by other systems besides Yocto Project and OpenEmbedded and that it will be simple - to extract information and convert it to other formats if required. - Yocto Project, through its standard layers mechanism, can directly accept the format - described as a layer. - The BSP captures all - the hardware-specific details in one place in a standard format, which is - useful for any person wishing to use the hardware platform regardless of - the build system they are using. - </para> - - <para> - The BSP specification does not include a build system or other tools - - it is concerned with the hardware-specific components only. - At the end-distribution point, you can ship the BSP combined with a build system - and other tools. - However, it is important to maintain the distinction that these - are separate components that happen to be combined in certain end products. - </para> - <section id='bsp-layers'> <title>BSP Layers</title> @@ -116,6 +87,35 @@ <title>Example Filesystem Layout</title> <para> + Providing a common form allows end-users to understand and become familiar + with the layout. + A common format also encourages standardization of software support of hardware. + </para> + + <para> + The proposed form does have elements that are specific to the Yocto Project and + OpenEmbedded build systems. + It is intended that this information can be + used by other systems besides Yocto Project and OpenEmbedded and that it will be simple + to extract information and convert it to other formats if required. + Yocto Project, through its standard layers mechanism, can directly accept the format + described as a layer. + The BSP captures all + the hardware-specific details in one place in a standard format, which is + useful for any person wishing to use the hardware platform regardless of + the build system they are using. + </para> + + <para> + The BSP specification does not include a build system or other tools - + it is concerned with the hardware-specific components only. + At the end-distribution point, you can ship the BSP combined with a build system + and other tools. + However, it is important to maintain the distinction that these + are separate components that happen to be combined in certain end products. + </para> + + <para> Below is the common form for the file structure inside a BSP Layer. While you can use this basic form for the standard, realize that the actual structures for specific BSPs could differ. |