Guidelines for contributing to meta-intel layer: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 19: Line 19:
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer
** [[Expectations for up-streaming a BSP in meta-intel layer]]
 
== Expectations for up-streaming a BSP in meta-intel layer ==
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.
 
===1 Make sure the BSP is functioning well at all the times ===
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.
 
Check this link showing status of the various meta-intel BSPs kept up to date:
[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]
 
===2 Prepare the BSP for release with every meta-intel release ===
This involves these things:
* git tag the commit of the release
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area


== Review process for sending commits and BSPs to meta-intel layer ==
== Review process for sending commits and BSPs to meta-intel layer ==

Revision as of 15:50, 28 October 2013

meta-intel Layer Information

git repository location:

Mailing List:

Guidelines for sending commits to meta-intel

Please follow general guidelines for contributing to Yocto Project. Here are some of the links.

Guidelines for submitting BSPs to meta-intel

1st follow these general BSP developer's guides:

Expectations for up-streaming a BSP in meta-intel layer

To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

1 Make sure the BSP is functioning well at all the times

Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Check this link showing status of the various meta-intel BSPs kept up to date:

Last Known Good Commits for meta-intel

2 Prepare the BSP for release with every meta-intel release

This involves these things:

  • git tag the commit of the release
  • Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
  • Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
  • Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

Review process for sending commits and BSPs to meta-intel layer

Guidelines for releasing BSPs