f77735ffae
Changelog: ========= Bug fixes --------- radv: CullDistance fail i965: Segmentation fault during glinfo context destruction, regression in 21.3.x Vulkan Wayland WSI returns empty surface formats [REGRESSION][BISECTED] iris: Qutebrowser/QtWebEngine sporadically flashes the window in white Flickering Intel Uhd 620 Graphics Broken Terraria & Glitches in Forza Horizon 4 Changes ------- Revert "nir/algebraic: distribute fmul(fadd(a, b), c) when b and c are constants" anv: Fix subgroupSupportedStages physical property Revert "zink: handle vertex buffer offset overflows" ir3: Fix copy-paste mistakes in ir3_block_remove_physical_predecessor() ir3/cp: ir3: Prevent propagating shared regs out of loops harder ir3: opt_deref in opt loop to remove unnecessary tex casts crocus: find correct relocation target for the bo. vulkan: Fix leak of error messages pick_status.json: Update to cb781fc350108584116280fc597c695d2f476c68 pick_status.json: Mark 15e77504461a30038a054c87cc53a694171c9cf4 as denominated pick_status.json: Mark 960e72417f3e8885699cf384f690853e14ba44da as denominated intel/fs: Take into account region strides during SIMD lowering decision of SHUFFLE. vulkan/wsi/wayland: Fix add_wl_shm_format alpha/opaqueness. vulkan/wsi/wayland: Convert missing vulkan formats to shm formats. vulkan/wsi/wayland: Add modifiers for RGB formats. vulkan/wsi/wayland: Fix add_drm_format_modifier aplha/opaqueness. anv/pass: Don't set first_subpass_layout for stencil-only attachments vulkan/wsi: Set MUTABLE_FORMAT_BIT in the prime path i965: Avoid NULL drawbuffer in brw_flush_front intel/fs: don't set allow_sample_mask for CS intrinsics intel/nir: fix shader call lowering panvk: Fix pointer corruption in panvk_add_wait_event_syncobjs zink: never use SpvOpImageQuerySizeLod for texel buffers zink: reorder fbfetch flag-setting to avoid null deref zink: fix vertex buffer mask computation for null buffers zink: clamp tbo creation to maxTexelBufferElements zink: add vertex shader pipeline bit for generated barrier construction zink: fix waiting on current batch id zink: cast image atomic op params/results based on image type zink: use SpvScopeDevice over SpvScopeWorkgroup for atomic shader ops zink: disable PIPE_SHADER_CAP_FP16_CONST_BUFFERS llvmpipe: disable PIPE_SHADER_CAP_FP16_CONST_BUFFERS llvmpipe: ci updates zink: add VK_BUFFER_USAGE_CONDITIONAL_RENDERING_BIT_EXT for query binds zink: fix PIPE_CAP_TGSI_BALLOT export conditional zink: reject invalid draws zink: min/max blit region in coverage functions anv: Disable CCS_E for some 8/16bpp copies on TGL+ anv: Use ANV_FAST_CLEAR_DEFAULT_VALUE for CCS on TGL+ anv: Re-enable CCS_E on TGL+ iris: implement inter-context busy-tracking aco: fix neg(abs(mul(a, b))) if the mul is not VOP3 aco: don't encode src2 for v_writelane_b32_e64 radv: fix R_02881C_PA_CL_VS_OUT_CNTL with mixed cull/clip distances radv/winsys: fix missing buffer_make_resident() for the null winsys tu: VkExternalImageFormatProperties is optional (From OE-Core rev: 05e45cb04e72d369aa6db1793cd010096db3cc09) Signed-off-by: Wang Mingyu <wangmy@fujitsu.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.