dev-manual: Some minor tweaks to ch 4, development manual:

* is it technically correct to say there are now 5 BSPs? as in, does
  genericx86-64 count as a new BSP distinct from genericx86? [aside: are
  there any plans for a MIPS64 BSP?] - rpjday

  MIPS64 is under development. - scottrif

* if scott is up for it, a couple more variables for the variable
  glossary might be BASE_WORKDIR and TARGET_VENDOR, which i would have
  added to that variable list but they don't appear in the glossary
  - rpjday

  Noted. - scottrif

(From yocto-docs rev: 45876209fd94a6800176381518f008890da646ee)

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-11-11 10:55:21 -08:00 committed by Richard Purdie
parent e3e0d40704
commit 3736d5c8e4
1 changed files with 10 additions and 8 deletions

View File

@ -155,10 +155,11 @@
For more information on BSP layers, see the For more information on BSP layers, see the
"<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>" section in the "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>" section in the
Yocto Project Board Support Package (BSP) Developer's Guide.</para> Yocto Project Board Support Package (BSP) Developer's Guide.</para>
<note>Four BSPs exist that are part of the <note>Five BSPs exist that are part of the
Yocto Project release: <filename>genericx86</filename>, <filename>beagleboard</filename>, Yocto Project release: <filename>genericx86</filename>, <filename>genericx86-64</filename>,
<filename>beagleboard</filename>,
<filename>mpc8315e</filename>, and <filename>routerstationpro</filename>. <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>.
The recipes and configurations for these four BSPs are located and dispersed The recipes and configurations for these five BSPs are located and dispersed
within the <link linkend='source-directory'>Source Directory</link>. within the <link linkend='source-directory'>Source Directory</link>.
On the other hand, BSP layers for Chief River, Crown Bay, On the other hand, BSP layers for Chief River, Crown Bay,
Crystal Forest, Emenlow, Fish River Island 2, Jasper Forest, N450, NUC DC3217IYE, Crystal Forest, Emenlow, Fish River Island 2, Jasper Forest, N450, NUC DC3217IYE,
@ -218,10 +219,10 @@
<para> <para>
You can view a video presentation on "Building Custom Embedded Images with Yocto" You can view a video presentation on "Building Custom Embedded Images with Yocto"
at <ulink url='http://free-electrons.com/blog/elc-2011-videos'>Free Electrons</ulink>. at <ulink url='http://free-electrons.com/blog/elc-2011-videos'>Free Electrons</ulink>.
You can also find supplemental information in You can also find supplemental information in the
<ulink url='&YOCTO_DOCS_BSP_URL;'> <ulink url='&YOCTO_DOCS_BSP_URL;'>
The Board Support Package (BSP) Development Guide</ulink>. Yocto Project Board Support Package (BSP) Developer's Guide</ulink>.
Finally, there is wiki page write up of the example also located Finally, there is a wiki page write up of the example also located
<ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'> <ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'>
here</ulink> that you might find helpful. here</ulink> that you might find helpful.
</para> </para>
@ -1643,7 +1644,7 @@
<filename>meta/conf/bitbake.conf</filename> configuration file in the <filename>meta/conf/bitbake.conf</filename> configuration file in the
<link linkend='source-directory'>Source Directory</link>: <link linkend='source-directory'>Source Directory</link>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
S = ${WORKDIR}/${BP} S = "${WORKDIR}/${BP}"
</literallayout> </literallayout>
You should be aware that many recipes override the <filename>S</filename> variable. You should be aware that many recipes override the <filename>S</filename> variable.
For example, recipes that fetch their source from Git usually set For example, recipes that fetch their source from Git usually set
@ -1653,7 +1654,7 @@
<ulink url='&YOCTO_DOCS_REF_URL;#var-BP'><filename>BP</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-BP'><filename>BP</filename></ulink>
represents the base recipe name, which consists of the name and version: represents the base recipe name, which consists of the name and version:
<literallayout class='monospaced'> <literallayout class='monospaced'>
BP = ${BPN}-${PV} BP = "${BPN}-${PV}"
</literallayout> </literallayout>
</note> </note>
</para> </para>
@ -1702,6 +1703,7 @@
<ulink url='&YOCTO_DOCS_REF_URL;#var-TMPDIR'><filename>TMPDIR</filename></ulink>, <ulink url='&YOCTO_DOCS_REF_URL;#var-TMPDIR'><filename>TMPDIR</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-TOPDIR'><filename>TOPDIR</filename></ulink>, <ulink url='&YOCTO_DOCS_REF_URL;#var-TOPDIR'><filename>TOPDIR</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink>, <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-MULTIMACH_TARGET_SYS'><filename>MULTIMACH_TARGET_SYS</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-TARGET_OS'><filename>TARGET_OS</filename></ulink>, <ulink url='&YOCTO_DOCS_REF_URL;#var-TARGET_OS'><filename>TARGET_OS</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink>, <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink>, <ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink>,