From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: Layer input
Date: Tue, 25 Jun 2013 08:42:01 -0400 [thread overview]
Message-ID: <51C99019.1080506@windriver.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF5182B@ORSMSX101.amr.corp.intel.com>
On 13-06-25 08:35 AM, Rifenbark, Scott M 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.
I realize you are documenting the Yocto reference builds, so the
explicit reference to linux-yocto*.bbappend makes sense (and I obviously
like it), but a quick tweak might be to just use <name>.bbappend or
<name>.bb (since not all BSP layers must bbappend a kernel, they may
have something very custom) for the kernel recipe reference.
You've already used that notation in the distro layer for the kernel-
headers, so it logically flows.
Cheers,
Bruce
>
> Thanks,
> Scott
>
> Scott Rifenbark
> Intel Corporation
> Yocto Project Documentation
> 503.712.2702
> 503.341.0418 (cell)
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-06-25 12:42 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 [this message]
2013-06-25 12:43 ` Rifenbark, Scott M
2013-06-25 18:06 ` Jerrod Peach
2013-06-27 7:41 ` Rifenbark, Scott M
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=51C99019.1080506@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=paul.eggleton@linux.intel.com \
--cc=scott.m.rifenbark@intel.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.