wangmy 6eb37d895f mesa: upgrade 21.3.3 -> 21.3.4
Changelog:
==========
Bug fixes
---------
i965: gen5 exposes EXT_texture_integer incorrectly
[radeonsi, regression, bisected]: Rendering issues with Factorio
mesa >= 21.x (with llvmpipe) will break the game JVGS
Panfrost - RK3399 - FACTORIO - glitches everywhere
Baldurs Gate 3 (Patch 6) - ribbon-like artifacts on textures
Game Starsector crashes under certain circumstances with mesa 21.3.+
FreeSpace models incorrectly rendered on Polaris cards, causing system freeze
Incomplete evaluation of nested DEFINE macros
[r300g, bisected] piglit glsl-fs-discard-04 fails
Panfrost G52 Firefox terrible glitches on youtube playback

Changes
-------
pan/bi: Fix load_const of 1-bit booleans
gallium/util: Add pixel->blocks box helper
lima,panfrost: Correct pixel vs block mismatches
radv: Set optimal copy alignment to 1.
microsoft/compiler: Fix dxil_nir_create_bare_samplers()
ir3/ra: Fix logic bug in compress_regs_left
ir3: Bump type mismatch penalty to 3
aco: don't allow SDWA on VOP3P instructions
aco: validate VOP3P opsel correctly
tu: fix workaround for depth bounds test without depth test
intel/genxml/gen4-5: fix more Raster Operation in BLT to be a uint
crocus: fail resource allocation properly.
freedreno/afuc: Disable the disassembler on 32-bit builds.
i915g: Turn off FP16 in the vertex shaders.
r300: Fix omod failing to increase the number of channels stored.
nir_to_tgsi: Fix a bug in TXP detection after backend lowering.
pick_status.json: Update to 8a78706643ecad8a1f303cc9358873abc29978b4
pick_status.json: Mark 00bea38242d97e7ace1954f1bc7d32cbf0ce3ee0 as denominated
pick_status.json: Mark 2a0253b9b5d21c7571555abe3a1d851468a18740 as denominated
r300: fix handling swizzle in transform_source_conflicts
intel/compiler/test: Fix build with GCC 7
i965: Disable EXT_texture_integer on Gfx4 and Gfx5
Revert "anv: Stop doing too much per-sample shading"
anv: don't leave anv_batch fields undefined
anv: limit compiler valid color outputs using NIR variables
intel/dev: fixup chv workaround
etnaviv: initialize vertex attributes on context reset
etnaviv: drm: fix size limit in etna_cmd_stream_realloc
etnaviv: drm: properly handle reviving BOs via a lookup
zink: fix -Warray-bounds warning
radv: fix xfb query copy param ordering
zink: always unset vertex shader variant key data when changing last vertex stage
zink: add extra synchronization for buffer descriptor binds
zink: use device-local heap for sparse backing allocations
r300: Remove broken optimization in rc_transform_KILL
radeonsi/gfx8: use the proper dcc clear size
vbo/dlist: fix loopback crash
vbo/dlist: add vertices to incomplete primitives
radeonsi/gfx10: fix si_texture_get_offset for mipmapped tex
glapi: should not add alias function to static_data.py
aco: remove pack_half_2x16(a, 0) optimization
intel/fs: OpImageQueryLod does not support arrayed images as an operand
v3dv: Hotfix: Rename remaining V3DV_HAS_SURFACE->V3DV_USE_WSI_PLATFORM
radv: add drirc radv_disable_htile_layers and enable it for F1 2021
iris: unref syncobjs and free r/w dependencies array for slab entries
mesa: free idalloc storage for display lists
mesa: free vbo_save_vertex_list store prims
glsl/glcpp: make sure to expand new token after concatenation
venus: subtract appended header size in vn_CreatePipelineCache
Fix compilation on armv7l with gcc 11.2.0

(From OE-Core rev: 3cdb743ec048aa06c10e0da0fb3feb1ca740b6e2)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-01-18 10:53:54 +00:00
2022-01-18 10:53:54 +00:00
2022-01-11 10:53:44 +00:00
2021-07-19 18:07:21 +01:00

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

Description
No description provided
Readme 251 MiB