d7906b39ef
Adresses CVE-2024-2961 Changes: 36280d1ce5 iconv: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence (CVE-2024-2961) 4a7de5e215 powerpc: Fix ld.so address determination for PCREL mode (bug 31640) f4a45af368 AArch64: Check kernel version for SVE ifuncs 7f3c143381 aarch64: fix check for SVE support in assembler 9112cda4c6 aarch64: correct CFI in rawmemchr (bug 31113) 153012dda2 AArch64: Remove Falkor memcpy 90b03336d9 AArch64: Add memset_zva64 d166309459 AArch64: Cleanup emag memset 650300d233 AArch64: Cleanup ifuncs 5bfa9f4369 AArch64: Add support for MOPS memcpy/memmove/memset c4e222334b Add HWCAP2_MOPS from Linux 6.5 to AArch64 bits/hwcap.h b9e93c5ff7 AArch64: Improve SVE memcpy and memmove 115c2c7717 AArch64: Improve strrchr 06fad28274 AArch64: Optimize strnlen 3a1557efef AArch64: Optimize strlen 6f2ca6aab9 AArch64: Optimize strcpy 249fff42a8 AArch64: Improve strchrnul 1c1313dbdd AArch64: Optimize strchr 80ad6cd302 AArch64: Improve strlen_asimd 65c4bb41b6 AArch64: Optimize memrchr 23be6f897e AArch64: Optimize memchr 28e40b3909 aarch64: Use memcpy_simd as the default memcpy c503e2206e aarch64: Cleanup memset ifunc 577bd1e049 AArch64: Fix typo in sve configure check (BZ# 29394) ea25fe5599 aarch64: Optimize string functions with shrn instruction 2c4ae9faa5 AArch64: Sort makefile entries 2c92d94407 AArch64: Add SVE memcpy d6d295a95b linux: Use rseq area unconditionally in sched_getcpu (bug 31479) dda5faa65e Include sys/rseq.h in tst-rseq-disable.c c9ee9cc8b8 nptl: Unconditionally use a 32-byte rseq area 3cd02612e8 make ‘struct pthread’ a complete type a24adf3572 support: use 64-bit time_t (bug 30111) d47c5e4db7 malloc: Use __get_nprocs on arena_get2 (BZ 30945) 1a3326df93 x86_64: Optimize ffsll function code size. 914af4fcca NEWS: Mention bug fixes for 29039/30745/30843 5d1fe26b49 x86-64: Fix the tcb field load for x32 [BZ #31185] 2d87262c1c x86-64: Fix the dtv field load for x32 [BZ #31184] 5f08ec08d0 elf: Fix TLS modid reuse generation assignment (BZ 29039) 01ea8d9dde Revert "elf: Move l_init_called_next to old place of l_text_end in link map" 0222f2392d Revert "elf: Always call destructors in reverse constructor order (bug 30785)" 6aa8380cf5 Revert "elf: Remove unused l_text_end field from struct link_map" (From OE-Core rev: 016387557c036efb700b01ab915d69a2e46a5740) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.