diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-04-26 08:01:25 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-05-01 20:50:47 +0100 |
commit | 2ffb797a713c3ea37a381bedc8b7acf34caba590 (patch) | |
tree | 8db85586ed6bdf735ecfb9cabb6cd108fb1bcaa1 /documentation/dev-manual | |
parent | 2329826dce2b04f20dee4657829ed0b9e8747b89 (diff) | |
download | poky-2ffb797a713c3ea37a381bedc8b7acf34caba590.tar.gz |
documentation/dev-manual/dev-manual-model.xml: BSP Layer step updated
Several things out-of-date for step five of the BSP Creation overview.
(From yocto-docs rev: 6bf1c93315c2fe604dbe468a29d9e2159bf7aceb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r-- | documentation/dev-manual/dev-manual-model.xml | 20 |
1 files changed, 14 insertions, 6 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 22e68dae1e..e1e5fb92f4 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml | |||
@@ -125,8 +125,10 @@ | |||
125 | website and click on “BSP Downloads.”</para></listitem> | 125 | website and click on “BSP Downloads.”</para></listitem> |
126 | <listitem><para><emphasis>Create your own BSP layer</emphasis>: Layers are ideal for | 126 | <listitem><para><emphasis>Create your own BSP layer</emphasis>: Layers are ideal for |
127 | isolating and storing work for a given piece of hardware. | 127 | isolating and storing work for a given piece of hardware. |
128 | A layer is really just a location or area in which you place the recipes for your BSP. | 128 | A layer is really just a location or area in which you place the recipes for your BSP. |
129 | In fact, a BSP is, in itself, a special type of layer. | 129 | In fact, a BSP is, in itself, a special type of layer. |
130 | </para> | ||
131 | <para> | ||
130 | Another example that illustrates a layer is an application. | 132 | Another example that illustrates a layer is an application. |
131 | Suppose you are creating an application that has library or other dependencies in | 133 | Suppose you are creating an application that has library or other dependencies in |
132 | order for it to compile and run. | 134 | order for it to compile and run. |
@@ -134,16 +136,22 @@ | |||
134 | are kept. | 136 | are kept. |
135 | The key point for a layer is that it is an isolated area that contains | 137 | The key point for a layer is that it is an isolated area that contains |
136 | all the relevant information for the project that the Yocto Project build | 138 | all the relevant information for the project that the Yocto Project build |
137 | system knows about.</para> | 139 | system knows about. |
140 | For more information on layers, see the | ||
141 | "<link linkend='understanding-and-creating-layers'>Understanding and Creating Layers</link>" | ||
142 | section. | ||
143 | For more information on BSP layers, see the | ||
144 | "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>" section in the | ||
145 | Yocto Project Board Support Package (BSP) Developer's Guide.</para> | ||
138 | <note>The Yocto Project supports four BSPs that are part of the | 146 | <note>The Yocto Project supports four BSPs that are part of the |
139 | Yocto Project release: <filename>atom-pc</filename>, <filename>beagleboard</filename>, | 147 | Yocto Project release: <filename>atom-pc</filename>, <filename>beagleboard</filename>, |
140 | <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>. | 148 | <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>. |
141 | The recipes and configurations for these four BSPs are located and dispersed | 149 | The recipes and configurations for these four BSPs are located and dispersed |
142 | within the local Yocto Project files. | 150 | within the <link linkend='yocto-project-files'>Yocto Project Files</link>. |
143 | Consequently, they are not totally isolated in the spirit of layers unless you think | ||
144 | of <filename>meta-yocto</filename> as a layer itself. | ||
145 | On the other hand, BSP layers for Crown Bay, Emenlow, Jasper Forest, | 151 | On the other hand, BSP layers for Crown Bay, Emenlow, Jasper Forest, |
146 | N450, and Sugar Bay are isolated.</note> | 152 | N450, Cedar Trail, Fish River, Fish River Island II, Romley, sys940x, tlk, |
153 | and Sugar Bay exist in their own separate layers within the larger | ||
154 | <filename>meta-intel</filename> layer.</note> | ||
147 | <para>When you set up a layer for a new BSP, you should follow a standard layout. | 155 | <para>When you set up a layer for a new BSP, you should follow a standard layout. |
148 | This layout is described in the section | 156 | This layout is described in the section |
149 | "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout'>Example Filesystem Layout</ulink>" | 157 | "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout'>Example Filesystem Layout</ulink>" |