All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Thilo Fromm <fromm@dresearch-fe.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Introducing the HidaV layer
Date: Fri, 18 May 2012 09:45:26 +0100	[thread overview]
Message-ID: <6434146.9hc03uN0UM@helios> (raw)
In-Reply-To: <CADZ6=avSzGXb3h1BunDQqqojA7tv-gO2VRicC6nt9KzAuNOcUg@mail.gmail.com>

On Friday 18 May 2012 10:09:42 Thilo Fromm wrote:
> 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>

Great stuff!

> 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?

No formality in particular. I think you should be able to add it, or I'm more 
than happy to add it right now - in fact I was about to, but I'm not entirely 
sure where this fits. Does it belong in "Miscellaneous" or "Board / device 
support layers"?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-05-18  8:55 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 [this message]
2012-05-18  9:11   ` Thilo Fromm
2012-05-18 21:39 ` Denys Dmytriyenko
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=6434146.9hc03uN0UM@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=fromm@dresearch-fe.de \
    --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.