From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Introducing the HidaV layer
Date: Fri, 18 May 2012 17:39:50 -0400 [thread overview]
Message-ID: <20120518213950.GA4208@denix.org> (raw)
In-Reply-To: <CADZ6=avSzGXb3h1BunDQqqojA7tv-gO2VRicC6nt9KzAuNOcUg@mail.gmail.com>
On Fri, May 18, 2012 at 10:09:42AM +0200, Thilo Fromm wrote:
> Hello *.*,
>
> There's a new layer in town. HidaV will provide a common platform
> layer, development support, and firmware for our yet-to-come ti8148
> based systems. The layer poses a symbiosis of a "board support" and a
> "distribution" layer. HidaV integrates meta-ti, meta-openembedded,
> meta-angstrom, and openembedded-core to a well-tailored distribution.
> Although HidaV therefore heavily focuses on our own devices/boards we
> hope to provide useful bug fixes and recipes for other projects/layers
> as well.
>
> The code is here: <https://github.com/DFE/HidaV>
> Some initial documentation: <https://github.com/DFE/HidaV/wiki>
>
> Finally, I would like to add HidaV to the openembedded layer index[1].
> Is there some formality involved in this, or do I just create a wiki
> account and then edit it in?
Just couple questions - wouldn't it be better to send fixes to the underlying
layers that you integrate, instead of holding them in your own integration
layer? And if it's for your unique ti8148-based board, then it's fine, it may
warrant a separate BSP layer for that. But why did you chose to pre-integrate
other layers into yours? Although you seem to be using sub-modules, but it's
still pre-integration, a-la Yocto/Poky releases...
Ah, and BTW, I think your layer ordering and priorities[1] are slightly wrong,
as usually BSP layers reside lower than Software layers (i.e. meta-oe), but
Distro layers (i.e. angstrom) should probably be on top...
--
Denys
next prev parent reply other threads:[~2012-05-18 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 8:09 Introducing the HidaV layer Thilo Fromm
2012-05-18 8:45 ` Paul Eggleton
2012-05-18 9:11 ` Thilo Fromm
2012-05-18 21:39 ` Denys Dmytriyenko [this message]
2012-05-21 7:43 ` Thilo Fromm
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=20120518213950.GA4208@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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.