3a9e6f8194
Changelog: ========= Bug fixes --------- lavapipe: dEQP-VK.spirv_assembly.instruction.compute.float16.arithmetic_3.step fails ANV: Bad output from TransformFeedback . Regression from Mesa 21. Something to do with VB+XFB -> VB+XFB dependency? Changes ------- pan/bi: Avoid *FADD.v2f16 hazard in optimizer pan/bi: Avoid *FADD.v2f16 hazard in scheduler pan/bi: Lower swizzles on CSEL.i32/MUX.i32 panvk: Use more reliable assert for UBO pushing radv: Fix preamble argument order. ir3/spill: Fix simplify_phi_nodes with multiple loop nesting lavapipe: fix sampler + sampler view leaks. lavapipe: reference gallium fences correctly. crocus: fix leak on gen4/5 stencil fallback blit path. i915g: Initialize the rest of the "from_nir" temporary VS struct. pick_status.json: Update to dabba7d7263be6ffb6f3676465e92c65952fa824 pick_status.json: Mark b07372312d7053f2ef5c858ceb1fbf9ade5e7c52 as denominated gallivm/nir: Call nir_lower_bool_to_int32 after nir_opt_algebraic_late nir: All set-on-comparison opcodes can take all float types intel/fs: Don't optimize out 1.0*x and -1.0*x spriv: Produce correct result for GLSLstd450Step with NaN spirv: Produce correct result for GLSLstd450Modf with Inf spirv: Produce correct result for GLSLstd450Tanh with NaN nir: Properly handle various exceptional values in frexp nir: Produce correct results for atan with NaN nir: Add missing dependency on nir_opcodes.py anv: Call vk_command_buffer_finish if create fails dri: avoid NULL deref of DrawBuffer on flush nir: fix lower_memcpy anv/genxml/intel/fs: fix binding shader record entry anv: don't set color state when input state was requested ac/surface: add more elements to meta equations because HTILE can use them lavapipe: use util_pack_color_union() for generating clear colors aux/draw: fix llvm tcs lane vec generation zink: always set VkPipelineMultisampleStateCreateInfo::pSampleMask zink: always invalidate streamout counter buffer if not resuming iris: Don't fast clear with the view format r300: fix transformation of abs modifiers with negate radeonsi: workaround Specviewperf13 Catia hang on GFX9 radeonsi: fix depth stencil multi sample texture blit glx: fix pbuffer refcount init radv/winsys: fix initializing debug/perftest options if multiple instances intel/genxml: add PIPE_CONTROL field for L3 read only cache invalidation anv: invalidate L3 read only cache when VF cache is invalidated iris: invalidate L3 read only cache when VF cache is invalidated iris: fix a leak on surface states mesa/st: always use DXT5 when transcoding ASTC format tegra: Use private reference count for sampler views tegra: Use private reference count for resources radv: Disable IB2 on compute queues. venus: properly destroy deferred ahb image before real image creation (From OE-Core rev: 31daf916d218d5e6e95bac857cbeb0d44901e4b3) 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.