Date
1 - 9 of 9
[PATCH] bsp-guide: replace meta-intel with meta-xilinx as container layer
|
Robert P. J. Day
As meta-intel is no longer a container layer, use meta-xilinx as
an example instead. Signed-off-by: Robert P. J. Day <rpjday@...> --- 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> -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
|
|
|
|
On 5/2/19 6:19 AM, Robert P. J. Day wrote:
As meta-intel is no longer a container layer, use meta-xilinx asI thought "meta-virtualization" was a container layer? IMHO, a BSP should only deal with getting a MACHINE booted. - armin
|
|
|
|
Scott Rifenbark <srifenbark@...>
The term "Container Layer" was put in the ref-manual by me to describe a "meta-*" layer that had other "meta-*" layers (see https://www.yoctoproject.org/docs/2.7/ref-manual/ref-manual.html#term-container-layer and the term "Container Layer"). Maybe this was never a good term? I don't know. Nobody has said anything about that term for many releases. The problem Robert points out needs to be fixed in the BSP manual as "meta-intel" is not longer qualifying by my definition. I can fix that. Is "Container Layer" ok as I have defined it? Thanks, Scott
On Thu, May 2, 2019 at 10:21 AM akuster <akuster@...> wrote:
|
|
|
|
On 5/2/19 10:45 AM, Scott Rifenbark
wrote:
in those terms above, yes its fine. thanks for clarifying. Armin
|
|
|
|
Scott Rifenbark <srifenbark@...>
Great, thanks!
On Thu, May 2, 2019 at 11:21 AM akuster <akuster@...> wrote:
|
|
|
|
Robert P. J. Day
much snipping ...
On Thu, 2 May 2019, Scott Rifenbark wrote: On Thu, May 2, 2019 at 10:21 AM akuster <akuster@...> wrote:uh, i'm looking at meta-virtualization right now: https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/ and that looks like a regular BSP layer, not a container layer. am i misunderstanding some fundamental point here? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
|
|
|
|
Robert P. J. Day
On Thu, 2 May 2019, Scott Rifenbark wrote:
Great, thanks!as a followup, i would think that "meta-openembedded" is the canonical example of a container layer, no? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
|
|
|
|
Robert P. J. Day
On Thu, 2 May 2019, Scott Rifenbark wrote:
Great, thanks!the more i think about it, the more i'm nervous about the phrase "container layer", as it suggests a "layer" of some kind in the context of OE. the one distinction i think worth making is that a "BSP layer" is a layer expressly designed to support identified target systems (eg., meta-xilinx-bsp), while a non-BSP layer simply packages functionality (recipes, classes) -- a good example is meta-virtualization. in either case, the trivial property of an OE layer is something that can be specified in a bblayers.conf file. so i'm not sure *how* you would describe, for example, meta-openembedded. i'm sure i'm overthinking this. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
|
|
|
|
Andrea Galbusera
On Fri, May 3, 2019 at 12:56 PM Robert P. J. Day <rpjday@...> wrote:
Maybe just as a "metadata collection repo"? IMHO from a OE perspective, a "layer" is a metadata set which provides its own layer.conf file (which, as you say, means you can add it to your project's bblayers.conf). Bundling more than one layer within the same git repository (or whatever archive format use to distribute them) does not qualify this metadata collection as anything otherwise meaningful for bitbake. That said, meta-openembedded is definitely the most evident example of such a "concept". I agree the term "container layer" can be either confused with a OE layer, which technically is not, or something having to do with containers (as I suspect from Armin's reply), which is completely unrelated to. Maybe rewording a little bit the manual here could reduce potential confusion to new users. Moreover whatever term we choose to explain this concept, we should make clear that it is orthogonal to any other layer classification by content (i.e. BSP, distro, ...). i'm sure i'm overthinking this.
|
|
|