All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: proper recipe for building for beagle xM? meta-ti?
Date: Tue, 28 Feb 2012 17:12:23 -0500	[thread overview]
Message-ID: <4F4D5147.1070202@windriver.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1202281651040.8024@oneiric>

On 12-02-28 4:55 PM, Robert P. J. Day wrote:
> On Tue, 28 Feb 2012, Bruce Ashfield wrote:
>
>> It is true that the beagleboard is a hardware reference board in the
>> yocto consolidated kernel tree and meta-yocto layers. That means
>> that it gets the yocto standard QA builds and boot testing.
>>
>> That being said, if you are looking for the latest + specific
>> features then you've been pointed in a good direction .. meta-ti
>> will meet your needs.
>>
>> As for disentangling and reducing questions in this area .. rest
>> assured, we are working on it.
>
>    ok, that's perfectly reasonable -- meta-yocto provides a generic,
> well-tested product, while the meta-ti layer provides more
> leading-edge content, correct?  which is a perfectly respectable
> answer.
>
>    but the impression i got from koen is that this wasn't even the
> right forum to ask such a question.  so i'm a bit confused -- can i
> just use the combination of yocto + meta-ti to build a fairly
> up-to-date image for my beagle xM or not?

I'm not 100% up on the progress on the TI layers, but as far as
I know, your description above is a goal.  meta-ti works on top of
oe-core and with other layers (i.e. angstrom) to produce what you
describe. I've also heard that there's a variant that works with
(just) oe-core (I'm not recalling all the details and can't look
them up right now) to produce an image. The READMEs in the various
layers should spell out the dependencies.

If you are still working on this, and it isn't making sense, drop
another email and someone can help translate!

Cheers,

Bruce

>
> rday
>



      parent reply	other threads:[~2012-02-28 22:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 18:51 proper recipe for building for beagle xM? meta-ti? Robert P. J. Day
2012-02-28 21:22 ` Bruce Ashfield
2012-02-28 21:55   ` Robert P. J. Day
2012-02-28 22:09     ` Koen Kooi
2012-02-28 22:28       ` Robert P. J. Day
2012-03-02 10:06         ` Koen Kooi
2012-03-02 16:45           ` Stewart, David C
2012-03-02 16:51             ` Robert P. J. Day
2012-03-02 17:15             ` Koen Kooi
2012-03-02 22:22         ` William Mills
2012-03-02 22:33           ` Robert P. J. Day
2012-03-02 22:50             ` William Mills
2012-03-02 23:18               ` Gary Thomas
2012-03-03  0:07                 ` William Mills
2012-03-04  6:18                 ` Denys Dmytriyenko
2012-03-04 12:19                   ` Robert P. J. Day
2012-03-04 12:36                     ` Gary Thomas
2012-03-04 12:54                       ` Robert P. J. Day
2012-03-04 17:01                         ` Koen Kooi
2012-03-04 18:14                       ` Robert P. J. Day
2012-03-04 19:27                         ` Denys Dmytriyenko
2012-03-04 19:43                           ` Robert P. J. Day
2012-03-04 19:45                           ` Gary Thomas
2012-03-04 20:01                             ` Brian Hutchinson
2012-03-04 20:04                             ` Denys Dmytriyenko
2012-03-04 21:18                               ` Robert P. J. Day
2012-03-05  5:12                                 ` [yocto] " Denys Dmytriyenko
2012-03-05 11:00                                   ` Robert P. J. Day
2012-03-04 21:38                             ` Robert P. J. Day
2012-03-05  4:26                               ` Denys Dmytriyenko
2012-03-05  9:52                               ` Jack Mitchell
2012-03-04  6:08           ` Denys Dmytriyenko
2012-02-28 22:12     ` Bruce Ashfield [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=4F4D5147.1070202@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=rpjday@crashcourse.ca \
    --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.