All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: does a meta-intel (sub)layer require adding the meta-intel layer to bblayers.conf?
Date: Sun, 25 Mar 2012 17:09:11 -0500	[thread overview]
Message-ID: <1332713351.23802.57.camel@elmorro> (raw)
In-Reply-To: <alpine.DEB.2.02.1203251602500.9832@oneiric>

On Sun, 2012-03-25 at 16:05 -0400, Robert P. J. Day wrote:
> On Sun, 25 Mar 2012, Tom Zanussi wrote:
> 
> > On Sun, 2012-03-25 at 13:23 -0400, Robert P. J. Day wrote:
> > > again, a discrepancy between the docs and the source files.  i
> > > checked out the entire meta-intel layer, and below that the file
> > > meta-crownbay/README clearly states:
> > >
> > > "Having done that, and assuming you extracted the BSP tarball contents
> > > at the top-level of your yocto build tree, you can build a crownbay
> > > image by adding the location of the meta-crownbay layer to
> > > bblayers.conf, along with the meta-intel layer itself (to access
> > > common metadata shared between BSPs) e.g.:
> > >
> > >   yocto/meta-intel \
> > >   yocto/meta-intel/meta-crownbay \"
> > >
> > >   however, the ref manual, Section 4.1, "BSP Layers", suggests only:
> > >
> > >      BBLAYERS = " \
> > >         /usr/local/src/yocto/meta \
> > >         /usr/local/src/yocto/meta-yocto \
> > >         /usr/local/src/yocto/meta-<bsp_name> \
> > >         "
> > >
> > > note no mention of including "meta-intel" layer.  clarification?
> > >
> >
> > Yes, I think that's as it should be - the general-purpose documentation
> > shouldn't mention specific layers.  meta-intel has its own layering
> > requirements as mentioned in the READMEs for those BSPs.  Also I think
> > the text mentions it's an example, but I guess I'm a bit confused since
> > I'm finding that in section 5.1. Example Filesystem Layout here:
> >
> > http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html
> >
> > Am I looking at the wrong thing?
> 
>   ah, yes, i'm looking at the *newer* version of that doc as cloned
> from yocto-docs where Section 4.1 of that manual is called "BSP
> Layers" and really emphasizes meta-intel and related layers and,
> because of that, has some awkward wording that might mislead the
> reader.  if you want to check the yocto-docs version of the same
> manual, you might see what i'm talking about.
> 

Yeah, I do see... I think all the examples in that section should be
removed - some of them aren't even BSP layers, and at any rate we really
don't need specific examples in a generic section like that.

Posting an update to that section now...

Tom

> rday
> 




      reply	other threads:[~2012-03-25 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 17:23 does a meta-intel (sub)layer require adding the meta-intel layer to bblayers.conf? Robert P. J. Day
2012-03-25 17:40 ` Tom Zanussi
2012-03-25 17:46   ` Robert P. J. Day
2012-03-25 19:06     ` Tom Zanussi
2012-03-25 20:05   ` Robert P. J. Day
2012-03-25 22:09     ` Tom Zanussi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1332713351.23802.57.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.