All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
To: Jerrod Peach <peachj@lexmark.com>,
	Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: Layer input
Date: Thu, 27 Jun 2013 07:41:22 +0000	[thread overview]
Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF51E45@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <CA+QkY1BKJqnLcbJq786d3LjA6D7gDLLQifccMA4m9m0cKOXj+g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2835 bytes --]

Hi,

I have tweaked this figure some based on Bruce and Jerrod's input.  To help me figure out some of the basics, I ran the yocto-layer and bsp-layer scripts to create a general and BSP layer, respectively.  Please look over the contents of these layers and comment.  General comments on the whole concept of how I am presenting the layers are welcome along with any other observations.

Thanks,
Scott

From: Jerrod Peach [mailto:peachj@lexmark.com]
Sent: Tuesday, June 25, 2013 11:07 AM
To: Rifenbark, Scott M
Cc: yocto@yoctoproject.org; Paul Eggleton
Subject: Re: [yocto] Layer input

Scott,

  *   Distro Layer

     *   I'm unclear on what <name> is.  Is that supposed to be <distro>?  <recipe>?  It probably shouldn't just be <name>, should it?

  *   Software Layer

     *   Should COPYING.MIT just be COPYING to be more generically applicable?
     *   conf/<layer_name>.conf should be just layer.conf, right?

  *   BSP Layer

     *   COPYING.MIT file again.
     *   machine/<name>.conf should probably be machine/<machine*>.conf.  You can probably drop the non-asterisk version, since an asterisk implies, "There might be more stuff, there might not."
     *   recipes-bsp/formfactor shouldn't also have another formfactor directory, should it?  Or is the "files" directory in 1.4 replaced with another formfactor-named directory?  Also, <name> should be <machine> again.
     *   What's everything from recipes-core down?  I can buy recipes-kernel being in a bsp, but are any other directories really necessary?
Kind regards,

Jerrod

On Tue, Jun 25, 2013 at 8:35 AM, Rifenbark, Scott M <scott.m.rifenbark@intel.com<mailto:scott.m.rifenbark@intel.com>> wrote:
Hi,

This next illustration attempting to dive deeper in the YP Development Process takes the remaining left-side input from that figure in the Quick Start (metadata, Machine, and Policy).  Note that when the original figure was created that appears in the QS, the layer stuff had not yet been established.  This figure I am attaching is rough.  I am unsure as to the contents of these layers.  Right now it is detailed but with generic names.  The idea is that individual layers are preferred to do things such as provide software, configure policy, and configure machines.  I am including some notes at the bottom of the figure that would not be part of the figure but might help to get across what I am trying to accomplish here.

Any suggestions and feedback is really appreciated.

Thanks,
Scott

Scott Rifenbark
Intel Corporation
Yocto Project Documentation
503.712.2702<tel:503.712.2702>
503.341.0418<tel:503.341.0418> (cell)



_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #1.2: Type: text/html, Size: 8927 bytes --]

[-- Attachment #2: layer-input.png --]
[-- Type: image/png, Size: 78223 bytes --]

  reply	other threads:[~2013-06-27  7:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 12:35 Layer input Rifenbark, Scott M
2013-06-25 12:42 ` Bruce Ashfield
2013-06-25 12:43   ` Rifenbark, Scott M
2013-06-25 18:06 ` Jerrod Peach
2013-06-27  7:41   ` Rifenbark, Scott M [this message]
2013-06-27 12:56     ` Jerrod Peach
2013-06-27 13:34       ` Rifenbark, Scott M
2013-06-27 21:02     ` Philip Balister
2013-06-28  6:13       ` Rifenbark, Scott M
2013-06-28 10:50         ` Rifenbark, Scott M
2013-06-28 11:07           ` Paul Eggleton
2013-06-28 11:22             ` Rifenbark, Scott M
2013-06-28 21:36               ` Khem Raj
2013-07-08 15:16                 ` Paul Eggleton
2013-07-09  1:36                   ` Bruce Ashfield

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=41DEA4B02DBDEF40A0F3B6D0DDB123797FF51E45@ORSMSX101.amr.corp.intel.com \
    --to=scott.m.rifenbark@intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=peachj@lexmark.com \
    --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.