All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ege <k4230r6@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Odroid-xu3 support
Date: Sat, 09 May 2015 00:02:59 +0200	[thread overview]
Message-ID: <554D3293.2090503@gmail.com> (raw)
In-Reply-To: <554C0625.9000304@gmail.com>

Hi,
On 08.05.2015 02:41, Trevor Woerner wrote:
> On 15-05-07 02:56 AM, Christian Ege wrote:
>>  From the ODROID family I do only own a ODROID-C1. If there will be a
>> combined Layer for all odroid devices I will  port my recipes to this
>> and can help on supporting it.
>> I am mostly interested in Multimedia stuff and I do plan to setup a
>> separate layer for Kodi/XBMC on amlogic based devices.
>>
>> So how should we proceed with the layer jungle?
> 
> Ideally meta-amlogic provides things specific to the chip itself (vendor
> kernel? vendor u-boot?) and meta-odroid contains things related to the
> various boards themselves (tweaks specific to each board).
This would be in an ideal world. In the real world each vendor like
hardkernel or wetek is maintaining their own kernel tree derived from
Amlogic.

Amlogic itself maintains a buildroot based BSP for their
boards. My Idea was at least merging u-Boot and Kernel of both vendors
into one tree.

> Maybe the beaglebone provides a good example to follow? (meta-ti,
> meta-beagleboard) Although I'm not sure how clean the separation is in
> those layers.

Yes this is the way to go, the manufacturer maintains its own layer. I
can try to get in contact with Amlogic if they are interested in
creating such a layer or at least supporting it.

regards,
Christian


      reply	other threads:[~2015-05-08 22:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  3:56 Odroid-xu3 support akuster808
2015-05-06 20:17 ` Trevor Woerner
2015-05-06 20:17   ` [oe] " Trevor Woerner
2015-05-06 20:24   ` akuster808
2015-05-06 20:24     ` [oe] " akuster808
2015-05-06 21:41     ` Trevor Woerner
2015-05-06 21:41       ` [oe] " Trevor Woerner
2015-05-06 21:43       ` akuster808
2015-05-06 21:43         ` [oe] " akuster808
2015-05-07  6:56       ` Christian Ege
2015-05-08  0:41         ` Trevor Woerner
2015-05-08  0:41           ` [oe] " Trevor Woerner
2015-05-08 22:02           ` Christian Ege [this message]

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=554D3293.2090503@gmail.com \
    --to=k4230r6@gmail.com \
    --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.