sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation/dev-manual/dev-manual-model.xml: Minor edits. 

(From yocto-docs rev: 64525f6a751d23d2d8ae1d799b4f661e986b5e83)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2011-07-28 05:57:17 -07:00 committed by Richard Purdie
parent fe51c0d7ce
commit a246c304de
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/dev-manual/dev-manual-model.xml
View File

@ -42,7 +42,7 @@
<title>Developing a Board Support Package (BSP)</title>
<para>
A BSP is a package of recipes that when applied while building an image results in
A BSP is a package of recipes that when applied during a build results in
an image you can run on a particular board.
Thus, the package, when compiled into the new image, supports the operation of the board.
</para>
@ -55,21 +55,19 @@
<para>
The remainder of this section presents the basic steps to create a BSP basing it on an
existing BSP that ships with the Yocto Project.
You can reference <xref linkend='dev-manual-bsp-appendix'>BSP Development Case</xref>
You can reference <xref linkend='dev-manual-bsp-appendix'>BSP Development Example</xref>
for a detailed example that uses the Crown Bay BSP as a base BSP from which to start.
</para>
<para>
The following illustration shows the general workflow to create a BSP.
In the figure....
This illustration and the following list summarizes the BSP creation general workflow.
</para>
<para>
<imagedata fileref="figures/bsp-dev-flow.png" width="6in" depth="7in" align="center" scale="100" />
<imagedata fileref="figures/bsp-dev-flow.png" width="6in" depth="7in" align="left" scale="100" />
</para>
<para>
Here are the basic steps involved in creating a BSP:
<orderedlist>
<listitem><para><emphasis>Set up your host development system to support
development using the Yocto Project</emphasis>: See