From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Tue, 04 Sep 2012 09:21:58 +0100 [thread overview]
Message-ID: <5045BA26.9030104@communistcode.co.uk> (raw)
In-Reply-To: <CADkTA4PX-ZAhhPi0OppbT4y4e5jiwDwgNFHONjebPimF8U21Yg@mail.gmail.com>
On 03/09/12 22:08, Bruce Ashfield wrote:
> On Mon, Sep 3, 2012 at 4:55 PM, Tomas Frydrych
> <tf+lists.yocto@r-finger.com> wrote:
>> snip...
>>
>>
>>
>> That being said, taking a step back, what are you trying to get out of
>> meta-yocto in this scenario ? oe-core + meta-ti is probably what you
>> should be using.
>>
Sorry to jump in here, but this is actually a very interesting point.
From coming to OpenEmbedded through Yocto and subsequently learning
about the ecosystem as a whole, I have always considered meta-yocto to
be providing a sane distro configuration. This implies that I believe
the oe-core default distro configuration, even though it will build, the
result won't be very satisfying - or maybe a bit disjointed.
You seem to be saying above that the meta-yocto layer is only any good
for providing the kernel framework, and as he is not using the framework
(i.e. using meta-ti) then there is no point in using the meta-yocto
layer? So does the Poky distro config only really slap a name on the
oe-core default distro policy - or does it have some added value?
I'm not trying to rile anyone up here, just trying to put the jigsaw
together as the picture looks different every time I revisit it!!
Regards,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-09-04 8:20 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 [this message]
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
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=5045BA26.9030104@communistcode.co.uk \
--to=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.