- The layers are non-yocto-compliant in a number of ways: parsing issues, signature changes, etc
- A number of yocto conventions are violated with varying consequences. For example, machine specifics in layer.conf.
- Cross-layer dependencies without state LAYERDEPENDS, i.e. meta-bsp on meta-sdk, though only for certain recipes.
- Exceeding the purpose of the individual layers, both relating to yocto compliance and not. BSPs should not make changes that aren’t specific to that which is needed for the machine, and should avoid altering core components, such as busybox.
As a quick summary of the meaning of Yocto Project Compatible, "Yocto Project Compatible status is appropriate for products, BSPs and other OE-compatible layers, and related open-source projects. These components must be maintained and submitted by an open source project, non-profit, or Yocto Project member organization."
Regarding Yocto compatible/compliant, the ones I see as being an issue for meta-imx follow: