From: William Mills <wmills@ti.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Integrating 3rd Party BSP Layers
Date: Thu, 5 Jan 2012 17:19:07 -0500 [thread overview]
Message-ID: <4F0621DB.7030201@ti.com> (raw)
In-Reply-To: <4F058D02.2050707@communistcode.co.uk>
On 01/05/2012 06:44 AM, Jack Mitchell wrote:
> Good morning everyone,
>
> I am currently trying to figure out the best way to integrate the
> meta-texasinstruments layer with the Yocto provided layers. According to
> the meta-texasinstruments readme, it requires the meta-oe, meta-angstrom
> and meta-oe-core. Now Yocto provides the stable meta-oe-core (correct?),
> so I would clone the meta-oe and meta-angstrom, add them and the
> meta-texasinstruments layer to my bblayers.conf then build away, yes?
>
> However, what implications does adding these new layers bring when using
> them in the Yocto environment?
>
> Any thoughts would be greatly appreciated on the consequences and/or my
> methodology!
>
> The main aim of the game is trying to build an image for the beagleboard
> using the meta-texasinstruments layer as to get the latest and greatest
> support - with the possibility of using it later in the day when the
> beaglebones start appearing but with the stability and additional
> support that is acquired through the Yocto umbrella.
Yes, all good goals and within the scope of the plans for meta-ti (aka
meta-texasinstruments). However meta-ti is still a work in progress.
By the yocto 1.2 release time frame we plan to support and show the
following layer combinations:
core stack: oe-core + meta-ti
yocto stack: poky layer set + meta-ti
angstrom stack: oe-core + meta-oe + meta-ti + meta-angstrom
arago stack: oe-core + meta-oe + meta-ti + meta-arago
However at this time the only stack being built is the angstrom
configuration.
prev parent reply other threads:[~2012-01-05 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 11:44 Integrating 3rd Party BSP Layers Jack Mitchell
2012-01-05 22:19 ` William Mills [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=4F0621DB.7030201@ti.com \
--to=wmills@ti.com \
--cc=ml@communistcode.co.uk \
--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.