From: Jack Mitchell <ml@communistcode.co.uk>
To: meta-ti@yoctoproject.org
Subject: Re: Introducing meta-beagleboard
Date: Fri, 12 Oct 2012 11:24:35 +0100 [thread overview]
Message-ID: <5077EFE3.7000603@communistcode.co.uk> (raw)
In-Reply-To: <CA+T6QPnq1dZOJ-D+C-FFodCBjxN5AOE_qC3dFj_Vtz86rdk0bg@mail.gmail.com>
On 11/10/12 16:46, Jason Kridner wrote:
> To help foster fast development, future releases of the Angstrom
> Distribution that ships with BeagleBoard.org platforms (such as
> BeagleBone and BeagleBoard-xM) will be built using meta-beagleboard,
> rather than meta-ti. While this produces the seemingly undesirable
> effect of providing yet-another-BSP for BeagleBoard.org platforms,
> collaboration in the mainline kernel and bootloaders that are the key
> elements for the BSPs has made this possible and multiple goals for
> the various BSPs has made it desirable.
>
> The objectives for meta-beagleboard are:
> 1) Provide the best possible out-of-box-experience for BeagleBoard.org platforms
> 2) Enable as much add-on hardware as possible
> 3) Enable public contributions to extend the experience and hardware support
> 4) Deliver information to the BeagleBoard.org community regarding the
> development status
>
> The repository will be hosted at:
> https://github.com/beagleboard/meta-beagleboard
Great news! Will the kernel in this BSP be attempting to follow mainline
+ public patches? I'm chomping at the bit for an easy way to build a
tested DT kernel with recent patches.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-10-12 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:46 Introducing meta-beagleboard Jason Kridner
2012-10-11 16:11 ` Denys Dmytriyenko
2012-10-12 10:24 ` Jack Mitchell [this message]
2012-10-12 14:04 ` Denys Dmytriyenko
2012-10-12 14:43 ` Jack Mitchell
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=5077EFE3.7000603@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.