All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: meta-ti@yoctoproject.org
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: meta-ti layer confusion
Date: Fri, 20 Apr 2012 09:20:47 +0200	[thread overview]
Message-ID: <4F910E4F.9000800@dresearch-fe.de> (raw)

Our company is working on a new TI DM814x based hardware currently.

That's a really hard job, because the TI linux support is not really "optimal". But that's not the primary cause for my message.

[1] lists two TI BSP layers [2],[3] each one claiming to be "The official OpenEmbedded/Yocto BSP layer for Texas Instruments platforms.".

A look into them shows that they are not identically. At the moment they differ in two commits ([3] is ahead of [2]). In the last days these differences where much bigger.

So what is the intention for these two "offical" layers?

Which one should we use? And why?

BTW: Is anyone else out there working on a TI DM814x/DM816x hardware?

Regards,
Steffen

[1] <http://www.openembedded.org/wiki/LayerIndex>
[2] <http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/>
[3] <https://github.com/Angstrom-distribution/meta-ti>

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


             reply	other threads:[~2012-04-20  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20  7:20 Steffen Sledz [this message]
2012-04-20 13:20 ` meta-ti layer confusion Denys Dmytriyenko
2012-04-20 13:47   ` Steffen Sledz
2012-04-25  6:08     ` Steffen Sledz
2012-04-25  6:19       ` Koen Kooi
2012-04-25  7:49         ` Steffen Sledz
2012-05-04 12:53           ` Steffen Sledz

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=4F910E4F.9000800@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=denys@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.