[yocto-ab] Form submission from: Yocto Project Compatible Registration

[David Nyström]

Yes from Enea,

Br,
David


On 2014-01-28 03:28, Yocto Project wrote:
> Submitted on Monday, January 27, 2014 - 18:28
> Submitted by anonymous user: [192.198.147.165]
> Submitted values are:
>
>    --Contact information--
>      Organization: Intel Corporation
>      Project name: Valley Island (Baytrail) Yocto BSP
>      Contact name: Rebecca Chang Swee Fun
>      Contact email address: rebecca.swee.fun.chang at intel.com
>      URL to organization or product link:
>
> http://www.intel.com/content/www/us/en/intelligent-systems/bay-trail/atom-processor-e3800-family-overview.html 
>
>      Registration date: 2014-01-28
>      Compliance Agreement revision: 1.0
>      Yocto Project Compatible Version: 1.4
>
>
> Acceptance Criteria:
>   - Working towards and supporting the aims and objectives of the Yocto
> Project. These include decreasing the fragmentation of embedded 
> ecosystem and
> focus around a common shared set of tools, formats and best practices. We
> want to avoid multiple groups of people repeating the same work and 
> have one
> set of great tools rather than multiple tools with drawbacks.: Yes
>   - Promoting the OpenEmbedded architecture, layer model, and BSP 
> format.: Yes
>   - Making visible contributions in the OpenEmbedded and component 
> projects of
> the Yocto Project.: Yes
>   - Be a non-profit, or member of the Yocto Project working group, 
> regardless
> of organization size, or if the project's parent organization is an
> open-source project.: Yes
>   - If the project includes build system functionality, are BitBake and
> OpenEmbedded-Core included as components?: Yes
>   - If present, can the directories containing BitBake and 
> OpenEmbedded-Core
> be clearly identified within the system and only contain those 
> components?:
> Yes
>   - Have all patches applied to BitBake and OpenEmbedded-Core (if 
> present)
> been submitted to the open source community?: No (explain below)
>   - Do all layers contain a README file which details the origin of 
> the layer,
> its maintainer, where to submit changes, and any dependencies or version
> requirements?: Yes
>   - Do all layers build without errors against OpenEmbedded-Core with 
> only the
> dependencies/requirements listed in their README file?: Yes
>   - (For BSPs) Does the layer follow the format defined in the Yocto 
> Project
> Board Support Package (BSP) Developers Guide?: Yes
>   - Are hardware support, configuration (distro) policy, and recipe 
> metadata
> separated into different layers which do not depend on each other?: Yes
>   - Is a test report document included showing which combinations of 
> layers,
> recipes, and machines have been tested?: Yes
>   - If any item in the "Yocto Project Compatible Compliance 
> Recommendations"
> list is not true, is this documented in the testing report?: Yes
> Recommendations:
>   - Linux kernels are either based around LTSI kernel versions or a Yocto
> Project kernel version.: Yes
>   - Everything builds successfully with the standard toolchain from 
> OE-Core,
> where the architecture is one supported by OE-Core as standard. This 
> is to
> ensure that your layers are compatible with OE-Core. It is not 
> required that
> the OE-Core toolchain be provided to customers or any downstream 
> projects.:
> Yes
> Explanation: All development done on Linux Kernel are in progress of
> submitting to the Open Source Community. Review session are also in 
> progress
> before the patches get pull into linux-yocto branch.
>
>
> The results of this submission may be viewed at:
> https://www.yoctoproject.org/node/351547/submission/84
>
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab