To register compliance for use of the Yocto Project Compatible logo/text:

  1. Complete this web form. Please indicate in the comments how you are using the Yocto Project, and how your organization is visibly participating in the project.
  2. Email will be sent to the Yocto Project Advisory Board and you will receive a confirmation.
  3. When you have received approval from the Advisory Board, you may use the logo / text treatment
Contact information
Provide the first and last name of the contact person.
Which version of the Yocto Project is your project compatible with?
YesNo (explain below)
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.
Promoting the OpenEmbedded architecture, layer model, and BSP format.
Making visible contributions in the OpenEmbedded and component projects of the Yocto Project. Please describe your participation in the comments section below.
Are all your publicly accessible layers listed in the OpenEmbedded Layers index (
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.
If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components?
If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components?
Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community?
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?
Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file?
(For BSPs) Does the layer follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide?
Are hardware support, configuration (distro) policy, and recipe metadata separated into different layers which do not depend on each other?
Is a test report document included showing which combinations of layers, recipes, and machines have been tested?
If any item in the "Yocto Project Compatible Compliance Recommendations" list is not true, is this documented in the testing report?
YesNo (explain below)
Linux kernels are either based around LTSI kernel versions or a Yocto Project kernel version.
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.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.