ea7d581b13
23.0.1 changes New features None Bug fixes radv: A Plague Tale: Requiem black “flash” on 7900XTX 7900 XTX: Graphical corruption / artifacts in Cyberpunk radv: CmdCopyQueryPoolResults broken for VK_QUERY_TYPE_PRIMITIVES_GENERATED_EXT with queryCount > 1 radeonsi draws spurious values to depth buffer rusticl over llvmpipe + ffmpeg’s Opencl filter = error -51 rusticl over llvmpipe + ffmpeg’s Opencl filter = error -51 OpenGL crashes in X-Plane 11 [Bisected] Regression: Project Zomboid renders black hasvk: Black pixels with 8xMSAA and fast clears on Intel(R) HD Graphics 4400 (HSW GT2) radv: GTA IV graphical artifacts on 7900XTX radv: Resident Evil Revelations 2 artifacts on 7900XTX with DCC radv: Prototype 2 black textures on RDNA 3 when DCC is enabled Mesa 23.0.0 crashes immediately with indirect rendering [RADV] Returnal - pistol muzzle flash fills whole screen (graphical artifact) ACO: dEQP-VK.binding_model.descriptor_buffer.multiple.graphics_geom_buffers1_sets3_imm_samplers hangs on NAVI10 Build failures with recent lld r600,regression: Glitches on terrain with the NIR backend on Transport Fever 2 r600/TURKS: Crash of the game “A Hat in Time” with Gallium Nine and NIR path (third report) [gen9atom] Vulkan tests cause gpu hang: dEQP-VK.memory_model.* GL_SHADER_BINARY_FORMAT_SPIR_V is not added to the list of GL_SHADER_BINARY_FORMATS even if GL_ARB_gl_spirv is supported. [ANV/DG2] Vertex explosion in nvpro-samples/vk_raytracing_tutorial_KHR/ray_tracing_gltf CUEtools FLACCL hit assert in rusticl Assertion Failed on Intel HD 5500 with Linux / Mesa 22.3.1 / OpenGL 23.0.2 changes New features None Bug fixes allwinner a64: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory after some time of apps usage mesa: index buffer leaking RadeonSI: null dereference in amdgpu_cs_add_buffer, potential refcount mismatch, running BeyondAllReason eglCreateImageKHR, error: EGL_BAD_ALLOC (0x3003), message: “createImageFromDmaBufs failed” on AMD multi-gpu with explicit format modifiers libgrl.a installed but not used? radv: crash compiling UE5 lumen hardware RT shader aco: unused vtmp_in_loop radv,nir: dEQP-VK.ray_query.builtin.rayqueryterminate.* failures glsl compiled error when the RHS of operator `>>` is int64_t by enabling GL_ARB_gpu_shader_int64 extension QPainter fails to render multiple shapes with a brush set since Mesa 23.0 eglSwapBuffers blocks in wayland when it’s wl_surface_frame event is stolen. plasmashell sometimes hangs with mesa_glthread pps_device.h:23:11: error: ‘uint32_t’ does not name a type (From OE-Core rev: 66f67e43e25dc58a07a49bb8e12699f1a6ce06f4) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> (cherry picked from commit f7f483f90ba17342a83fdfe7c7dccf5a3f7bf624) 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.