diff options
| author |   Robert P. J. Day <rpjday@crashcourse.ca> | 2012-10-16 07:48:00 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-10-17 17:32:46 +0100 |
| commit | ca144a6abeac2073f49d8fe42af67d5cab4c6a98 (patch) | |
| tree | 8b8aa1dd67084a7adc8dfae1e700ae1e122b0496 /documentation/bsp-guide | |
| parent | fc76b3e43a54d0effe30bcb780287c0f05e9a01d (diff) | |
| download | openembedded-core-contrib-ca144a6abeac2073f49d8fe42af67d5cab4c6a98.tar.gz | |
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>
Diffstat (limited to 'documentation/bsp-guide')
| -rw-r--r-- | documentation/bsp-guide/bsp.xml | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 1f1667114c..3732498873 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -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 |