From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Thu, 06 Sep 2012 06:39:02 +0100 [thread overview]
Message-ID: <504836F6.2080303@r-finger.com> (raw)
In-Reply-To: <1346881616.21985.100.camel@ted>
On 05/09/12 22:46, Richard Purdie wrote:
> On Tue, 2012-09-04 at 09:58 +0100, Tomas Frydrych wrote:
>> Hi Bruce,
>>
>> On 03/09/12 22:08, Bruce Ashfield wrote:
>>> That being said, taking a step back, what are you trying to get out of
>>> meta-yocto in this scenario ?
>>
>> a) I am targeting multiple chips, including TI Omap and Intel Atom.
>> meta-yocto is a prerequisite for the various machines in meta-intel, so
>> I have to include meta-yocto if I want to build images for an Intel
>> chip. Nothing unusual here.
>
> Is that really true? What in meta-intel depends on meta-yocto?
No, it is not true; I corrected that erroneous statement earlier in this
thread.
> Effectively this is what we've now done and was always the intention
> (see the Yocto Project compatible criteria).
Yes, that looks like it solves the problem neatly. Now I should be able
to include both meta-yocto and meta-yocto-bsb if I want to.
Tomas
prev parent reply other threads:[~2012-09-06 5:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 20:06 yocto beagleboard.conf -- should it not go away? Tomas Frydrych
2012-09-03 20:15 ` Bruce Ashfield
2012-09-03 20:55 ` Tomas Frydrych
2012-09-03 21:08 ` Bruce Ashfield
2012-09-04 8:21 ` Jack Mitchell
2012-09-04 12:24 ` Bruce Ashfield
2012-09-05 22:03 ` Richard Purdie
2012-09-04 8:58 ` Tomas Frydrych
2012-09-04 12:20 ` Bruce Ashfield
2012-09-04 17:18 ` Darren Hart
2012-09-04 20:25 ` William Mills
2012-09-04 23:23 ` Darren Hart
2012-09-05 14:20 ` William Mills
2012-09-05 14:42 ` Darren Hart
2012-09-05 15:16 ` Bruce Ashfield
2012-09-05 21:52 ` Richard Purdie
2012-09-05 8:49 ` Tomas Frydrych
2012-09-05 9:15 ` Paul Eggleton
2012-09-05 9:43 ` Tomas Frydrych
2012-09-05 12:48 ` Richard Purdie
2012-09-05 14:45 ` William Mills
2012-09-05 15:06 ` Tomas Frydrych
2012-09-05 15:44 ` Richard Purdie
2012-09-05 19:34 ` Martin Jansa
2012-09-05 21:43 ` Richard Purdie
2012-09-05 14:39 ` Darren Hart
2012-09-08 7:18 ` Khem Raj
2012-09-05 21:46 ` Richard Purdie
2012-09-06 5:39 ` Tomas Frydrych [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=504836F6.2080303@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--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.