Thanks Bruce. I will implement that. >-----Original Message----- >From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] >Sent: Tuesday, June 25, 2013 5:42 AM >To: Rifenbark, Scott M >Cc: yocto@yoctoproject.org; Paul Eggleton >Subject: Re: [yocto] Layer input > >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 >>
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
