All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org, "Dmytriyenko, Denys" <denys@ti.com>
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Tue, 4 Sep 2012 16:25:36 -0400	[thread overview]
Message-ID: <504663C0.6050907@ti.com> (raw)
In-Reply-To: <504637F5.8090603@linux.intel.com>

On 09/04/2012 01:18 PM, Darren Hart wrote:
>
>
> On 09/04/2012 05:20 AM, Bruce Ashfield wrote:
>> On Tue, Sep 4, 2012 at 4:58 AM, Tomas Frydrych
>> <tf+lists.yocto@r-finger.com>  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.
>>>
>>> b) meta-yocto is the Poky distro layer; if you want to use Poky, then
>>> you need meta-yocto.
>>>
>>>> see above. I misspoke. I don't think there's an intent to make meta-yocto
>>>> and meta-ti work together, but oe-core + meta-ti, that's the combo that
>>>> makes sense.

oe-core + meta-ti should work or it needs to get fixed.
poky + meta-ti should work or it needs to get fixed.

However I suspect the 2nd is not in the nightly builds yet.

Denys is out for the next few days.  He can comment more when he gets back.

It has been our assumption that there is enough functionality in the 
layer mechanisms that any of the "light weight" BSPs in yocto layer 
could be completely overridden by a more complete layer (meta-ti in this 
example).  In addition the end system integrator should be able to 
override definitions in any BSP layer.

I suspect the current issue is just growing pains for a case that has 
not been tested.  Lets prove that false before taking more drastic action.

>>>
>>> The basic problem with meta-yocto is that it combines BSP stuff
>>> (meta-intel prerequisite, Atom&  Beagle config) with distro stuff (Poky,
>>> Yocto branding). That's convenient for doing QA on a limited set of HW,
>>> but suboptimal for real use; BSP layers simply should not be dependent
>>> on distro layers, it largely defeats the purpose of having layers.

Darren: Is it true you can't get @ the Intel BSP's w/o also getting the 
poky distro defs?  That does seem to mixing things a bit.  (I am not 
claiming meta-ti is clean yet but I want to understand the Intel examples.)



  reply	other threads:[~2012-09-04 20:25 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 [this message]
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=504663C0.6050907@ti.com \
    --to=wmills@ti.com \
    --cc=denys@ti.com \
    --cc=dvhart@linux.intel.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.