From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Odroid-xu3 support
Date: Thu, 07 May 2015 20:41:09 -0400 [thread overview]
Message-ID: <554C0625.9000304@gmail.com> (raw)
In-Reply-To: <CAALGJZaMCx0-daBCjkP_NrmnheTJQYLW2hU2bSpTW1ij0pMb8w@mail.gmail.com>
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).
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.
WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [oe] Odroid-xu3 support
Date: Thu, 07 May 2015 20:41:09 -0400 [thread overview]
Message-ID: <554C0625.9000304@gmail.com> (raw)
In-Reply-To: <CAALGJZaMCx0-daBCjkP_NrmnheTJQYLW2hU2bSpTW1ij0pMb8w@mail.gmail.com>
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).
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.
next prev parent reply other threads:[~2015-05-08 0:41 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 [this message]
2015-05-08 0:41 ` [oe] " Trevor Woerner
2015-05-08 22:02 ` Christian Ege
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=554C0625.9000304@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@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.