[meta-intel] Getting Edison BSP added to meta-intel
Is there a process to get the Edison BSP (1) imported into meta-intel
(2) to give developers a place to discuss and interact with Intel
outside of the Edison community forum (3)? I've keep looking in the
wrong places (4)
For those who don't subscribe to Yocto email lists the discussion that isn't routed here might be seen at [meta-intel] Getting Edison BSP added to meta-intel and Re: [linux-yocto] Getting Edison BSP added to meta-intel.
I'll just point out that when I asked about this in meta-edison layers as git repos? the response wasn't particularly encouraging.
I'd like to get public feedback from the yocto community.
I'm tagging folks who where part of your layers discussion to make sure they have an opportunity to comment here:
Intel_Peter I think the major concern is that Edison seems to be treated differently than other platforms from Intel based on yocto...
If Edison is to be treated differently we'd like a public statement on linux-yocto and meta-intel as to Intel's official stance (and possible reasoning) one way or another to publicly refer to.
It's important to the yocto and Edison community that Intel maintain the 'Criteria of being a Yocto Project Participant'  as Intel has a gold seat on the Yocto Administrative Leadership and Technical Leadership of the Intel BSPs and I believe is an essential part of Intel collaboration and diversity it desires.
To be explicit: Should we expect Intel to follow the criteria set forth for a 'Yocto Project Participant'' for the Edison BSP layer and patches to linux-yocto?
Are all your publicly accessible layers listed in the OpenEmbedded Layers index (http://layers.openembedded.org)?
Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other Yocto Project layers.
I'm not quite willing to join your party.
As far as I can tell the Edison is a way cool device and I was excited to get one. But as soon as I found out the Intel Edison folks weren't providing the BSP in a usable format I chucked in a drawer and went back to the BeagleBone Black. I don't know Intel's marketing concept for Edison; maybe they don't want advanced developers to use the thing. I do think it's short-sighted and arguably inconsiderate to depend on Yocto/OE and not fully participate in its ecosystem. While putting out mega-bundles of sources meets the open source licensing requirements, it's certainly not the behavior expected of a team player. So I'm sympathetic in principle.
Nonetheless, linux-yocto is IMO not an appropriate list to discuss this. meta-intel might be appropriate, but if it's like meta-ti then still no. Nor am I convinced that Intel Corporate cares, nor that they're technically obligated to do it. I suspect they can argue that meta-edison isn't a publicly accessible layer, because they don't make it available as a layer. Posts on these forums might attract the attention of somebody who has the authority to make it happen, though.
In the meantime I'm hoping that the BeagleBoard-X15 that's been hiding deep in meta-ti for the last couple months will be the development platform for 2015. Kinda the opposite of Edison: the source is fully available, but the hardware isn't released yet.
David Stewart started the Yocto Project  four years ago and still maintains the Intel Gold Member seat on the Yocto Advisory Board 
 https://www.youtube.com/watch?v=orkU2WxItTE#t=24 (:24 seconds in)
David obviously has a great appreciation for the value of upstreaming and maintaining an active yocto community.
I am emailing him this thread in hopes get he might join the discussion and share his views with us.
I've posted everything from them so far. I might try reaching out again this week.
Other folks are looking for updates on twitter and the meta-intel yocto mailing lists:
Short question: Will meta-intel support Intel Edison any time in the near
Koen Kooi created a repo for meta-edison:
It seems that it only generates images to be flashed on usb stick or micro sdcards. The layer basically contains the kernel and u-boot. But it is a starting point.
I'm hoping for Intel to upstream all meta-edison* layers, because the actual BSP doesn't follows Yocto Project best practices.