All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ODROID-C1 support
Date: Fri, 22 May 2015 19:15:37 -0400	[thread overview]
Message-ID: <555FB899.9040301@gmail.com> (raw)
In-Reply-To: <8824256D-28B9-48F4-8155-2185F236B4F2@gmail.com>

On 05/21/15 17:18, Khem Raj wrote:
>> On May 21, 2015, at 11:26 AM, Trevor Woerner <twoerner@gmail.com> wrote:
>>
>>
>> Why would someone include your layer and not build for odroidc1 or
>> wetekplay? Sometimes that's what people do ;-) (look at Angstrom, for
>> example). Besides, a BSP layer should be able to play nicely with other
>> layers even when its machines aren't being used :-)
> This is very much desirable, in todays times. In angstrom e.g. we want to generalize feeds across
> many machines for arm especially, so we can share common feeds across multiple armv7a machines
> so BSP maintainers have to start thinking that their BSP layer will be put along with other BSP layers
> and they not change common components mindlessly to fit for just one given machine.
>
> secondly more and more end users especially big companies have more than 1 machine tied into their useless
> so its desirable for them to use one distro across all the product lines and hence a requirement to have
> BSP layers play well with each others.

Shouldn't this be true of distro layers as well?

Simply included meta-angstrom in conf/bblayers.conf causes one's DISTRO
to be set to angstrom, even if they select poky in conf/local.conf.


  reply	other threads:[~2015-05-22 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 15:40 ODROID-C1 support Christian Ege
2015-05-08 13:44 ` Trevor Woerner
2015-05-21 18:26 ` Trevor Woerner
2015-05-21 20:55   ` Christian Ege
2015-05-21 21:18   ` Khem Raj
2015-05-22 23:15     ` Trevor Woerner [this message]
2015-05-23  0:30       ` Khem Raj

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=555FB899.9040301@gmail.com \
    --to=twoerner@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.