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/bsp.xml | |
parent | fc76b3e43a54d0effe30bcb780287c0f05e9a01d (diff) | |
download | poky-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/bsp.xml')
-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 @@ | |||
400 | For example, the Crown Bay BSP <filename>crownbay.conf</filename> has the | 400 | For example, the Crown Bay BSP <filename>crownbay.conf</filename> has the |
401 | following statements: | 401 | following statements: |
402 | <literallayout class='monospaced'> | 402 | <literallayout class='monospaced'> |
403 | include conf/machine/include/tune-atom.inc | 403 | require conf/machine/include/tune-atom.inc |
404 | include conf/machine/include/ia32-base.inc | 404 | require conf/machine/include/ia32-base.inc |
405 | </literallayout> | 405 | </literallayout> |
406 | </para> | 406 | </para> |
407 | </section> | 407 | </section> |
@@ -739,7 +739,7 @@ | |||
739 | <itemizedlist> | 739 | <itemizedlist> |
740 | <listitem><para>A brief description about the hardware the BSP | 740 | <listitem><para>A brief description about the hardware the BSP |
741 | targets.</para></listitem> | 741 | targets.</para></listitem> |
742 | <listitem><para>A list of all the dependencies a | 742 | <listitem><para>A list of all the dependencies |
743 | on which a BSP layer depends. | 743 | on which a BSP layer depends. |
744 | These dependencies are typically a list of required layers needed | 744 | These dependencies are typically a list of required layers needed |
745 | to build the BSP. | 745 | to build the BSP. |
@@ -787,14 +787,13 @@ | |||
787 | using the BSP layer. | 787 | using the BSP layer. |
788 | Multiple machine configuration files define variations of machine | 788 | Multiple machine configuration files define variations of machine |
789 | configurations that are supported by the BSP. | 789 | configurations that are supported by the BSP. |
790 | If a BSP supports more multiple machine variations, you need to | 790 | If a BSP supports multiple machine variations, you need to |
791 | adequately describe each variation in the BSP | 791 | adequately describe each variation in the BSP |
792 | <filename>README</filename> file. | 792 | <filename>README</filename> file. |
793 | Do not use multiple machine configuration files to describe disparate | 793 | Do not use multiple machine configuration files to describe disparate |
794 | hardware. | 794 | hardware. |
795 | Multiple machine configuration files should describe very similar targets. | 795 | If you do have very different targets, you should create separate |
796 | If you do have very different targets, you should create a separate | 796 | BSP layers for each target. |
797 | BSP. | ||
798 | <note>It is completely possible for a developer to structure the | 797 | <note>It is completely possible for a developer to structure the |
799 | working repository as a conglomeration of unrelated BSP | 798 | working repository as a conglomeration of unrelated BSP |
800 | files, and to possibly generate specifically targeted 'release' BSPs | 799 | files, and to possibly generate specifically targeted 'release' BSPs |