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

bsp-guide: Fixed some grammar and some filenames. 

* A couple grammatical fixes.
* A couple filename corrections.

(From yocto-docs rev: 1bad0049c57d47aaa785b8825a9a702c16e4cb69)

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 2013-10-11 07:16:55 -07:00 committed by Richard Purdie
parent 029b0fef50
commit 891786ee7d
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -394,12 +394,13 @@
<para> <para>
To use an include file, you simply include them in the machine configuration file. To use an include file, you simply include them in the machine configuration file.
For example, the Crown Bay BSP <filename>crownbay.conf</filename> has the For example, the Crown Bay BSP <filename>crownbay.conf</filename> contains the
following statements: following statements:
<literallayout class='monospaced'> <literallayout class='monospaced'>
require conf/machine/include/tune-atom.inc require conf/machine/include/tune-atom.inc
require conf/machine/include/ia32-base.inc require conf/machine/include/ia32-base.inc
require conf/machine/include/meta-intel.inc require conf/machine/include/meta-intel.inc
require conf/machine/include/meta-intel-emgd.inc
</literallayout> </literallayout>
</para> </para>
</section> </section>
@ -420,7 +421,7 @@
<filename>formfactor_0.0.bbappend</filename> file, which is an <filename>formfactor_0.0.bbappend</filename> file, which is an
append file used to augment the recipe that starts the build. append file used to augment the recipe that starts the build.
Furthermore, there are machine-specific settings used during the Furthermore, there are machine-specific settings used during the
build that are defined by the <filename>machconfig</filename>. build that are defined by the <filename>machconfig</filename> file.
In the Crown Bay example, two <filename>machconfig</filename> files In the Crown Bay example, two <filename>machconfig</filename> files
exist: one that supports the Intel® Embedded Media and Graphics exist: one that supports the Intel® Embedded Media and Graphics
Driver (Intel® EMGD) and one that does not: Driver (Intel® EMGD) and one that does not:
@ -460,7 +461,7 @@
(VESA) graphics): (VESA) graphics):
<literallayout class='monospaced'> <literallayout class='monospaced'>
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay-noemgd/xorg.conf meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xorg.conf
</literallayout> </literallayout>
</para> </para>
</section> </section>