You are on page 1of 1

Here are features and advantages of the Yocto Project:

Widely Adopted Across the Industry: Many semiconductor, operating system, software,
and service vendors adopt and support the Yocto Project in their products and
services. For a look at the Yocto Project community and the companies involved with
the Yocto Project, see the “COMMUNITY” and “ECOSYSTEM” tabs on the Yocto Project
home page.

Architecture Agnostic: Yocto Project supports Intel, ARM, MIPS, AMD, PPC and other
architectures. Most ODMs, OSVs, and chip vendors create and supply BSPs that
support their hardware. If you have custom silicon, you can create a BSP that
supports that architecture.

Aside from broad architecture support, the Yocto Project fully supports a wide
range of devices emulated by the Quick EMUlator (QEMU).

Images and Code Transfer Easily: Yocto Project output can easily move between
architectures without moving to new development environments. Additionally, if you
have used the Yocto Project to create an image or application and you find yourself
not able to support it, commercial Linux vendors such as Wind River, Mentor
Graphics, Timesys, and ENEA could take it and provide ongoing support. These
vendors have offerings that are built using the Yocto Project.

Flexibility: Corporations use the Yocto Project many different ways. One example is
to create an internal Linux distribution as a code base the corporation can use
across multiple product groups. Through customization and layering, a project group
can leverage the base Linux distribution to create a distribution that works for
their product needs.

Mechanism Rules Over Policy: Focusing on mechanism rather than policy ensures that
you are free to set policies based on the needs of your design instead of adopting
decisions enforced by some system software provider.

Uses a Layer Model: The Yocto Project layer infrastructure groups related
functionality into separate bundles. You can incrementally add these grouped
functionalities to your project as needed. Using layers to isolate and group
functionality reduces project complexity and redundancy, allows you to easily
extend the system, make customizations, and keep functionality organized.

You might also like