From: Jack Mitchell <ml@communistcode.co.uk>
To: meta-ti@yoctoproject.org
Subject: Re: meta-ti layer split
Date: Tue, 31 Jan 2012 10:36:26 +0000 [thread overview]
Message-ID: <4F27C42A.9090409@communistcode.co.uk> (raw)
In-Reply-To: <20120131004439.GF2032@denix.org>
On 31/01/12 00:44, Denys Dmytriyenko wrote:
> All,
>
> After much debate and further considerations ;) we've decided to split meta-ti
> repository into 2 layers to ease up on inter-layer dependencies and to enable
> additional use cases of building basic BSP images with a very small set of
> layers, only requiring oe-core as a dependency. The proposed split is the
> following:
>
> 1. meta-ti-bsp-core - is the ultra portable layer. Starting out it will
> contain only recipes-kernel and recipes-bootloader plus necessary machine
> configurations. Depending on the platform, can be as little as basic board
> support.
>
> 2. meta-ti-bsp-extras - provides the full chip functions with perhaps some
> extra constraints. Initialy this will contian support for DSP, Graphics, and
> Wifi. Provides additional board support for peripherals that may require
> software components like DSPBIOS, CodecEngine, gst-ti, firmware etc. Depends
> on meta-ti-bsp-core. In the future, if certain technologies prove themselves
> well portable, we may move them from meta-ti-bsp-extras to meta-ti-bsp-core.
>
> I'll be starting the initial work on this in a separate branch, calling for
> wider review once ready.
>
> Please provide feedback. Thanks.
>
This sounds fantastic. I am looking forward to being able to use an
officially supported BSP with the Yocto tools (particularly the
beaglebone!). Will the changes initially go into the meta-ti repo on the
yocto git or will development start internally and released when deemed
'ready'?
Regards,
Jack.
next prev parent reply other threads:[~2012-01-31 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 0:44 meta-ti layer split Denys Dmytriyenko
2012-01-31 10:36 ` Jack Mitchell [this message]
2012-01-31 12:15 ` Otavio Salvador
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=4F27C42A.9090409@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=meta-ti@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.