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

documentation: bsp-guide - minor edits. 

One change resulted in changing out "include" for "require"
in code from the Crown Bay example.

(From yocto-docs rev: 69b21d5f62ad9020646a26ce13d349af50aee419)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Robert P. J. Day 2012-10-16 07:48:00 -07:00 committed by Richard Purdie
parent fc76b3e43a
commit ca144a6abe
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
documentation/bsp-guide/bsp.xml
View File

@ -400,8 +400,8 @@
For example, the Crown Bay BSP <filename>crownbay.conf</filename> has the
following statements:
<literallayout class='monospaced'>
include conf/machine/include/tune-atom.inc
include conf/machine/include/ia32-base.inc
require conf/machine/include/tune-atom.inc
require conf/machine/include/ia32-base.inc
</literallayout>
</para>
</section>
@ -739,7 +739,7 @@
<itemizedlist>
<listitem><para>A brief description about the hardware the BSP
targets.</para></listitem>
<listitem><para>A list of all the dependencies a
<listitem><para>A list of all the dependencies
on which a BSP layer depends.
These dependencies are typically a list of required layers needed
to build the BSP.
@ -787,14 +787,13 @@
using the BSP layer.
Multiple machine configuration files define variations of machine
configurations that are supported by the BSP.
If a BSP supports more multiple machine variations, you need to
If a BSP supports multiple machine variations, you need to
adequately describe each variation in the BSP
<filename>README</filename> file.
Do not use multiple machine configuration files to describe disparate
hardware.
Multiple machine configuration files should describe very similar targets.
If you do have very different targets, you should create a separate
BSP.
If you do have very different targets, you should create separate
BSP layers for each target.
<note>It is completely possible for a developer to structure the
working repository as a conglomeration of unrelated BSP
files, and to possibly generate specifically targeted 'release' BSPs