[meta-ti] building Yocto for Pandaboard

[Denys Dmytriyenko]

On Thu, Feb 09, 2012 at 11:54:37AM -0500, Brian Hutchinson wrote:
> On Thu, Feb 9, 2012 at 11:36 AM, Denys Dmytriyenko <denis at denix.org> wrote:
> > Arago/meta-arago is still going to be the official platform distribution for
> > TI SDK products. But, a separate meta-ti layer was created early in the
> > process to detach and unify the BSP layer and allow people to use TI hardware
> > with different distributions. And that's actually part of the problem, as
> > distributions like religions conflict with each other in a single layer... :)
> 
> Hey Denys, good to hear from you again!

Brian, nice to talk to you again!

> Sorry for totally hi-jacking this thread .... so what should be the
> roadmap for someone like me who works on TI products and has to
> generate images now?  Do I use Yocto with meta-ti and in the future
> when the dust settles use Yocto with meta-arago?

First, meta-arago is not meant to replace meta-ti, it's meant to complement 
it. Yocto Project makes heavy use of layers and there are different types of 
layers - base, BSP, apps and distro. There used to be a visual diagram of how 
layers stack on top of one another, but I can't find it now. There is a nice 
comprehesive list of known layers, grouped by their type:
http://www.openembedded.org/wiki/LayerIndex

With that in mind, meta-ti is meant to be a pure BSP layer, while meta-arago 
is shaping up to contain 2 sub-layers - distro one and extra sw apps one.

You'd be able to use meta-ti in different combinations of layers with 
different distro layers - none, angstrom, arago and poky/yocto. When meta-ti 
is used together with meta-arago distro, it should provide the same features 
and same functionality as old Arago.

All this is within realms of the Yocto Project. Sometimes it's confusing when 
one refers to Yocto as a wider framework and the build sytem, vs. Yocto/Poky 
as a distribution layer and/or reference release... Please refer to Richard's 
earlier email in this thread for further clarification.

> I've heard bits and pieces of things changing but I guess I never knew
> enough of the TI roadmap to know for sure what I should be doing so
> that I steer our team/company in the right direction for all these
> changes.  I'm currently using Arago to generate our images (separate
> CSL toolchain (old), and the generated packages are old too).

The old Arago, which is based on the Classic OpenEmbedded, is used by several 
TI SDK products. Mostly due to the continuing support and maintenance of the 
existing products, the new development had constrained resources and slow 
progress.

-- 
Denys