![]() Changelog: ========== * fix: __atomic_always_lock_free() not a constant expression on g++ < 5.1 * fix: urcu assert fallback for pre-C11 builds * doc: update uatomic-api for static assert * Add uatomic size static assert for 's390' * Add uatomic size static assert for 'sparc64' * Add uatomic size static assert for 'ppc' * Add uatomic size static assert for 'x86' * Add uatomic size static assert for 'generic' * Add uatomic size static assert * Use UATOMIC_HAS_ATOMIC_INT/LLONG in generic implementation * Add UATOMIC_HAS_ATOMIC_INT/LLONG for x86 * Add UATOMIC_HAS_ATOMIC_INT/LLONG for tile * Add UATOMIC_HAS_ATOMIC_INT/LLONG for sparc64 * Add UATOMIC_HAS_ATOMIC_INT/LLONG for s390 * Add UATOMIC_HAS_ATOMIC_INT/LLONG for riscv * Add UATOMIC_HAS_ATOMIC_INT/LLONG for ppc * Add UATOMIC_HAS_ATOMIC_INT/LLONG for nios2 * Add UATOMIC_HAS_ATOMIC_INT/LLONG for mips * Add UATOMIC_HAS_ATOMIC_INT/LLONG for m68k * Add UATOMIC_HAS_ATOMIC_INT/LLONG for loongarch * Add UATOMIC_HAS_ATOMIC_INT/LLONG for ia64 * Add UATOMIC_HAS_ATOMIC_INT/LLONG for hppa * Add UATOMIC_HAS_ATOMIC_INT/LLONG for 'gcc' arch * Add UATOMIC_HAS_ATOMIC_INT/LLONG for arm * Add UATOMIC_HAS_ATOMIC_INT/LLONG for alpha * Add UATOMIC_HAS_ATOMIC_INT/LLONG for aarch64 * Add UATOMIC_HAS_ATOMIC_INT/LLONG for atomic builtins * Add builtin atomics size static asserts * cleanup: use URCU_GCC_VERSION from compiler.h * fix: atomic builtins defines for type support * Move back CMM_LOAD/STORE_SHARED to volatile access * Add cmm_annotate_mem_acquire() to URCU_DEREFERENCE_USE_VOLATILE rcu_dereference * Use uatomic_load CMM_RELAXED in URCU_DEREFERENCE_USE_VOLATILE * Fix: Re-introduce URCU_DEREFERENCE_USE_VOLATILE read barrier depends for alpha * Tree-wide: Rename to uatomic_load/uatomic_store * src: Use __*__ for attribute names * API: Use __*__ for attribute names * Fix Changelog 0.15.1 date (From OE-Core rev: e9b7585ca81d72962f4e7d57b3d0ff3524e5762b) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
---|---|---|
bitbake | ||
contrib | ||
documentation | ||
meta | ||
meta-poky | ||
meta-selftest | ||
meta-skeleton | ||
meta-yocto-bsp | ||
scripts | ||
.b4-config | ||
.gitignore | ||
.templateconf | ||
LICENSE | ||
LICENSE.GPL-2.0-only | ||
LICENSE.MIT | ||
MAINTAINERS.md | ||
MEMORIAM | ||
oe-init-build-env | ||
README.hardware.md | ||
README.md | ||
README.OE-Core.md | ||
README.poky.md | ||
README.qemu.md | ||
SECURITY.md |
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for 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 BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
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:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.