Alexander Kanavin
1b98b19017
Mesa 22.0.1 is a bug fix release which fixes bugs found since the 22.0.0 release: freedreno: crash in PUBG MSVC: Build failure in libmesa_util when targeting x86 32-bit A crash in radeonsi driver freedreno: deqp cts fails Mesa 22.0.2 is a bug fix release which fixes bugs found since the 22.0.1 release: Vulkan::Calling vkWaitForFences Timeout Intel (CHT) - Uplink text rendering bugged out in Mesa 22.0 gen9atom gpu hang on dEQP-VK.spirv_assembly.instruction.graphics.float16.arithmetic_1 bad memory managment on panfrost RK3399 - cannot alocate more ram - fury unleashed Broken rendering in Ryujinx on Tigerlake intel: integer_mad_hi / integer_mad_sat / integer_mul_hi produce invalid results Textures colors distortion in “Black Geyser: Couriers of Darkness” with radeonsi ShaderStorageBlocksWriteAccess not set for spir-v shaders? radeonsi dEQP-GLES3.functional.buffer.map.write.explicit_flush.* flake crashes radv: nir validation error with invalid array access Intel Iris Xe Geometry Flickering/Assets Disappearing Rendering artifacts when playing Outer Wilds [Reproducible with latest ANV driver built from main] Vulkan wsi leaks vk_sync object on every wsi_AcquireNextImageKHR call panfrost(RK3399/T860): Emulationstation: broken, black or missing menus with v22.0.0 Plasma/KDE settings menus disappear on daily build Square Artifacts Dragons Dogma r300: Anmesia the dark descent corruption Error compiling with LLVM-git/15 (From OE-Core rev: 34f6d4763fc3bad1382551fd863f96e556b5f6cc) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit f3e9444968fd47b3c8e0b2ee7b1b17f43a6bd56b) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.