From: William Mills <wmills@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 1/3] matrix-gui-browser: port from arago overlay
Date: Fri, 27 Jan 2012 16:52:32 -0500 [thread overview]
Message-ID: <4F231CA0.1000800@ti.com> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1010BF9DB56@DLEE12.ent.ti.com>
On 01/27/2012 03:55 PM, Maupin, Chase wrote:
>> Op 27 jan. 2012, om 21:21 heeft Denys Dmytriyenko het volgende
>> geschreven:
>>> On Fri, Jan 27, 2012 at 08:17:42PM +0000, Maupin, Chase wrote:
>>> How about splitting meta-ti into:
>>> * BSP only
>>> * SGX graphics
>>> * DSP tools
>> Since sgx and dsp are built into the SoC, why isn't it considered
>> BSP? I must really start warming about getting overzealous with
>> layers and breeding a silo mentality. I'm not saying we only need
>> one layer, but not a gazillion like the base proposal.
> I did not read the above as making a bunch of layers in meta-ti. At the risk of getting this all started again, I really hope meta-ti is one layer with BSP, SGX, DSP, WiFi support for our devices.
>
Well that was the proposal and why I figured you would barf all over
it. I am OK with all the above in one layer (but separate dirs) if it
all works with all the layer stack combinations we are targeting. The
issue is we have no meta-ti+oe-core builds going on so we don't know
where the dependencies will be hard to break.
We all know the DSP support can get involved. If we got to the point
where BSP and graphics worked with oe-core but DSP support needed
meta-oe or something else, then I would want the DSP stuff in a separate
layer so people that did not need it could opt out.
Likewise people using TI WIFI on non-TI processors should be able to get
that in any layer stack. If that all works with all the above in one
layer thats fine. We just don't know yet. We can be optimistic and put
it all in one layer or pessamistic and seperate them. In this example I
am more inclined to believe that the other TI stuff would not cause
problems.
Koen: having a number of layers in on repo is a bad thing? You should
tell the meta-oe maintainer because that guys has a good number of
layers in there. :) Are you saying that was the wrong thing to do for
meta-oe? Is there a leason learned?
next prev parent reply other threads:[~2012-01-27 21:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 18:46 [PATCH 1/3] matrix-gui-browser: port from arago overlay Chase Maupin
2012-01-26 18:46 ` [PATCH 2/3] refresh-screen: add package from arago Chase Maupin
2012-01-26 18:46 ` [PATCH 3/3] matrix-gui: update to latest version Chase Maupin
2012-01-26 22:44 ` [PATCH 1/3] matrix-gui-browser: port from arago overlay William Mills
2012-01-27 11:50 ` Koen Kooi
2012-01-27 12:09 ` Andreas Müller
2012-01-27 12:24 ` Koen Kooi
2012-01-27 17:38 ` William Mills
2012-01-27 19:39 ` Denys Dmytriyenko
2012-01-27 19:47 ` Koen Kooi
2012-01-27 20:09 ` Denys Dmytriyenko
2012-01-27 13:50 ` Maupin, Chase
2012-01-27 14:54 ` Philip Balister
2012-01-27 15:19 ` Maupin, Chase
2012-01-27 17:51 ` William Mills
2012-01-27 19:46 ` Maupin, Chase
2012-01-27 20:03 ` William Mills
2012-01-27 20:05 ` William Mills
2012-01-27 20:10 ` Tom Rini
2012-01-27 20:11 ` Denys Dmytriyenko
2012-01-27 20:19 ` Philip Balister
2012-01-27 20:24 ` Denys Dmytriyenko
2012-01-27 20:20 ` William Mills
2012-01-27 20:11 ` William Mills
2012-01-27 20:17 ` Maupin, Chase
2012-01-27 20:21 ` Denys Dmytriyenko
2012-01-27 20:24 ` William Mills
2012-01-27 20:29 ` Maupin, Chase
2012-01-27 20:34 ` Denys Dmytriyenko
2012-01-27 20:39 ` Maupin, Chase
2012-01-27 20:42 ` William Mills
2012-01-27 20:44 ` Maupin, Chase
2012-01-27 20:48 ` William Mills
2012-01-27 20:34 ` William Mills
2012-01-27 20:50 ` Philip Balister
2012-01-27 20:54 ` Koen Kooi
2012-01-27 20:57 ` Denys Dmytriyenko
2012-01-27 22:40 ` Philip Balister
2012-01-27 23:39 ` Denys Dmytriyenko
2012-01-27 20:53 ` Koen Kooi
2012-01-27 20:55 ` Maupin, Chase
2012-01-27 21:52 ` William Mills [this message]
2012-01-27 23:04 ` Koen Kooi
2012-01-28 3:23 ` Philip Balister
2012-01-27 17:30 ` William Mills
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=4F231CA0.1000800@ti.com \
--to=wmills@ti.com \
--cc=chase.maupin@ti.com \
--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.