Go to file
Scott Rifenbark 7e613928fe documentation: Updated title page notes
Fixed the title page notes to help the user get the exact
set of documentation for the appropriate YP release.

(From yocto-docs rev: 09bcec491f9edf5a4e7dac8b6818ce22b5df163f)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-10 20:43:22 +00:00
bitbake bitbake: lib/bs4: Fix imports from html5lib >= 0.9999999/1.0b8 2018-03-28 12:56:43 +01:00
documentation documentation: Updated title page notes 2018-12-10 20:43:22 +00:00
meta wpa_supplicant: fix WPA2 key replay security bug 2017-11-03 12:28:27 +00:00
meta-selftest oeqa/selftest: verify that devtool can use plugins in other layers 2015-10-21 22:56:06 +01:00
meta-skeleton linux-yocto-custom: fix typo in Upstream-Status tag 2015-10-19 17:57:58 +01:00
meta-yocto poky.conf: Bump version for 2.0.3 jethro release 2016-12-06 22:48:22 +00:00
meta-yocto-bsp linux-yocto: Update SRCREV for genericx86* for 4.1, fixes CVE-2016-0728 2016-02-04 23:20:18 +00:00
scripts wic: fix path parsing, use last occurrence 2016-07-27 09:00:53 +01:00
.gitignore bitbake: toaster tests: gitignore and use absolute path for log file 2015-08-01 11:27:52 +01:00
.templateconf .templateconf: New file for customized template defaults 2014-03-11 08:14:27 -07:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
oe-init-build-env oe-init-build-env: fix for build dirs that have spaces in their path 2015-04-13 22:33:24 +01:00
oe-init-build-env-memres oe-init-build-env-memres: Fix source check 2015-03-20 10:56:03 +00:00
README README: expand the Where To Send Patches section 2015-03-04 17:07:37 +00:00
README.hardware README.hardware: drop mention of binary-only drivers 2015-08-25 10:47:19 +01:00

Poky

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: http://yoctoproject.org/documentation

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: http://www.openembedded.org/

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 upstreams:

bitbake: Git repository: http://git.openembedded.org/bitbake/ Mailing list: bitbake-devel@lists.openembedded.org

documentation: Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/ Mailing list: yocto@yoctoproject.org

meta-yocto(-bsp): Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp) Mailing list: poky@yoctoproject.org

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 repository.

Git repository: http://git.openembedded.org/openembedded-core/
Mailing list: openembedded-core@lists.openembedded.org

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