bsp-guide: Removed inaccurate "container layer" references.

I left only the single mention of "container layers" and changed
the example from "meta-intel" to OpenEmbedded's meta-openembedded
layer.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 8aa4de2be19c001f19cc540e2f7b33ca71f6be60)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2019-05-03 10:48:48 -07:00 committed by Richard Purdie
parent 3693f075c4
commit 69aa458db2

View File

@ -148,16 +148,11 @@
Some layers function as a layer to hold other BSP layers. Some layers function as a layer to hold other BSP layers.
These layers are knows as These layers are knows as
"<ulink url='&YOCTO_DOCS_REF_URL;#term-container-layer'>container layers</ulink>". "<ulink url='&YOCTO_DOCS_REF_URL;#term-container-layer'>container layers</ulink>".
An example of this type of layer is the An example of this type of layer is OpenEmbedded's
<filename>meta-intel</filename> layer. <ulink url='https://github.com/openembedded/meta-openembedded'><filename>meta-openembedded</filename></ulink>
This layer contains BSP layers for the Intel-core2-32 layer.
<trademark class='registered'>Intel</trademark> Common Core The <filename>meta-openembedded</filename> layer contains
(Intel-core2-32) and the Intel-corei7-64 many <filename>meta-*</filename> layers.
<trademark class='registered'>Intel</trademark> Common Core
(Intel-corei7-64).
the <filename>meta-intel</filename> layer also contains
the <filename>common/</filename> directory, which contains
common content across those layers.
</para> </para>
<para> <para>
@ -1817,9 +1812,8 @@
The remainder of this section provides a description of The remainder of this section provides a description of
the Yocto Project reference BSP for Beaglebone, which the Yocto Project reference BSP for Beaglebone, which
resides in the resides in the
<ulink url='&YOCTO_DOCS_REF_URL;#term-container-layer'>Container Layer</ulink> <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta-yocto-bsp'><filename>meta-yocto-bsp</filename></ulink>
(i.e. layer.
<ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta-yocto-bsp'><filename>meta-yocto-bsp</filename></ulink>).
</para> </para>
<section id='bsp-layer-configuration-example'> <section id='bsp-layer-configuration-example'>
@ -1882,7 +1876,7 @@
</literallayout> </literallayout>
For example, the machine configuration file for the For example, the machine configuration file for the
<ulink url='http://beagleboard.org/bone'>BeagleBone and BeagleBone Black development boards</ulink> <ulink url='http://beagleboard.org/bone'>BeagleBone and BeagleBone Black development boards</ulink>
is located in the container layer is located in the layer
<filename>poky/meta-yocto-bsp/conf/machine</filename> <filename>poky/meta-yocto-bsp/conf/machine</filename>
and is named <filename>beaglebone-yocto.conf</filename>: and is named <filename>beaglebone-yocto.conf</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
@ -2216,8 +2210,7 @@
</literallayout> </literallayout>
This particular append file works for all the This particular append file works for all the
machines that are part of the machines that are part of the
<filename>meta-yocto-bsp</filename> container <filename>meta-yocto-bsp</filename> layer.
layer.
The relevant statements are appended with The relevant statements are appended with
the "beaglebone-yocto" string. the "beaglebone-yocto" string.
The OpenEmbedded build system uses these The OpenEmbedded build system uses these