OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
Go to file
Richard Purdie ebb42af282 poky: Update version to 2.3.4
(From meta-yocto rev: 17b7a75b22b2ca1a19d0a8656c0183b738932189)

Signed-off-by: Richard Purdie <>
2018-05-16 14:27:50 +01:00
bitbake bitbake: providers: Fix determinism issue 2018-03-09 06:12:09 -08:00
documentation documentation: Updated manual revision table for 2.3.4 release date 2018-02-14 15:24:54 +00:00
meta ruby: Update to 2.4.4 2018-05-07 15:57:44 +01:00
meta-poky poky: Update version to 2.3.4 2018-05-16 14:27:50 +01:00
meta-selftest wic-image-minimal: stop using core-image-minimal 2017-04-12 15:09:58 +01:00
meta-skeleton useradd-example: exclude from world 2017-01-09 13:39:11 +00:00
meta-yocto/conf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
meta-yocto-bsp linux-yocto/4.1: generix86* bsp fix perf issue with gcc >=7 2017-09-21 17:19:25 +01:00
scripts scripts/ remove 2018-05-07 15:57:44 +01:00
.gitignore add !meta-poky to .gitignore file 2016-03-26 08:06:58 +00:00
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
README meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
README.hardware README.hardware: update MPC8315E-RDB section 2017-01-16 18:08:20 +00:00
oe-init-build-env oe-init-build-env*: Make them actually return failures 2016-03-20 23:12:30 +00:00
oe-init-build-env-memres oe-init-build-env*: Make them actually return failures 2016-03-20 23:12:30 +00:00



Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with IDE integration.

Additional information on the specifics of hardware that Poky supports
is available in README.hardware. Further hardware support can easily be added
in the form of layers which extend the systems capabilities in a modular way.

As an integration layer Poky consists of several upstream projects such as 
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information 
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.

The Yocto Project has extensive documentation about the system including a 
reference manual which can be found at:

OpenEmbedded-Core is a layer containing the core metadata for current versions
of OpenEmbedded. It is distro-less (can build a functional image with
DISTRO = "nodistro") and contains only emulated machine support.

For information about OpenEmbedded, see the OpenEmbedded website:

Where to Send Patches

As Poky is an integration repository (built using a tool called combo-layer),
patches against the various components should be sent to their respective

    Git repository:
    Mailing list:

    Git repository:
    Mailing list:

meta-poky, meta-yocto-bsp:
    Git repository:
    Mailing list:

Everything else should be sent to the OpenEmbedded Core mailing list.  If in
doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git

    Git repository:
    Mailing list:

Note: The scripts directory should be treated with extra care as it is a mix of
oe-core and poky-specific files.