From: Trevor Woerner <twoerner@gmail.com>
To: Nicolas Aguirre <aguirre.nicolas@gmail.com>,
Andrei Gherzan <andrei@gherzan.ro>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-chip] Yocto on the 9$ computer
Date: Sat, 24 Oct 2015 18:14:06 -0400 [thread overview]
Message-ID: <562C02AE.9030609@gmail.com> (raw)
In-Reply-To: <CAHTvVMc7DBOLGvOU7X5YuO+O6FKSEaXW0aUsBd_VHsKQrEhqcg@mail.gmail.com>
On 10/24/15 15:58, Nicolas Aguirre wrote:
> 2015-10-24 19:26 GMT+02:00 Andrei Gherzan <andrei@gherzan.ro>:
>
>> Have a C.H.I.P. 9$ computer? It works with Yocto now.
>>
>> http://layers.openembedded.org/layerindex/branch/master/layer/meta-chip/
>>
> Good job.
> IMO it make sense to add C.H.I.P support in meta-sunxi, don't you think ?
Interesting: I had the exact same thought, had started to compose a
reply, but then thought about layers such as meta-beagleboard and
meta-raspberrypi :-)
Unfortunately there isn't much oversight/guidance in BSP-land. It's
entirely understandable (the work involved would be monstrous, and the
existing infrastructure can barely keep up with the tiny handful of BSPs
that are currently used for validation) but can be a bit frustrating
nonetheless.
Do we create layers for every board (meta-chip, meta-raspberrypi,
meta-beagleboard) or do we create layers for SoCs themselves
(meta-sunxi, meta-atmel, meta-rockchip)[1]? Currently there is no
"correct" answer. Unfortunately the distinction between SoCs, boards,
MACHINEs, DEFAULTTUNEs, and DISTROs isn't as clear and as clean as one
would like.
:-)
Trevor
[1] and let's not forget layers such as meta-ettus and meta-gumstix:
companies who make various boards with various SoCs!
next prev parent reply other threads:[~2015-10-24 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 17:26 [meta-chip] Yocto on the 9$ computer Andrei Gherzan
2015-10-24 19:58 ` Nicolas Aguirre
2015-10-24 20:13 ` Andrei Gherzan
2015-10-24 20:46 ` Alex J Lennon
2015-10-24 21:06 ` Andrei Gherzan
2015-10-26 9:36 ` Alex J Lennon
2015-10-31 0:52 ` Khem Raj
2015-10-24 22:14 ` Trevor Woerner [this message]
2015-10-24 22:17 ` Trevor Woerner
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=562C02AE.9030609@gmail.com \
--to=twoerner@gmail.com \
--cc=aguirre.nicolas@gmail.com \
--cc=andrei@gherzan.ro \
--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.