[yocto] [PATCH] bsp-guide: replace meta-intel with meta-xilinx as container layer

[akuster]

On 5/2/19 6:19 AM, Robert P. J. Day wrote:
> As meta-intel is no longer a container layer, use meta-xilinx as
> an example instead.

I thought "meta-virtualization" was a container layer?

IMHO, a BSP should only deal with getting a MACHINE booted.

- armin
>
> Signed-off-by: Robert P. J. Day <rpjday at crashcourse.ca>
>
> ---
>
> diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
> index 0bb0b68ab..a53ff6bce 100644
> --- a/documentation/bsp-guide/bsp.xml
> +++ b/documentation/bsp-guide/bsp.xml
> @@ -146,18 +146,15 @@
>
>      <para>
>          Some layers function as a layer to hold other BSP layers.
> -        These layers are knows as
> +        These layers are known as
>          "<ulink url='&YOCTO_DOCS_REF_URL;#term-container-layer'>container layers</ulink>".
>          An example of this type of layer is the
> -        <filename>meta-intel</filename> layer.
> -        This layer contains BSP layers for the Intel-core2-32
> -        <trademark class='registered'>Intel</trademark> Common Core
> -        (Intel-core2-32) and the Intel-corei7-64
> -        <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.
> +        <filename>meta-xilinx</filename> layer.
> +        This container layer contains some basic top-level information,
> +        as well as three actual Xilinx-related BSP layers,
> +        <filename>meta-xilinx-bsp</filename>,
> +        <filename>meta-xilinx-contrib</filename>, and
> +        <filename>meta-xilinx-standalone</filename>.
>      </para>
>
>      <para>
>