wangmy 80e7b3d1dc libva: upgrade 2.15.0 -> 2.16.0
Changelog:
===========
    add: Add HierarchicalFlag & hierarchical_level_plus1 for AV1e.
    dep: Update README.md to remove badge links
    dep: Removed waffle-io badge from README to fix broken link
    dep: Drop mailing list, IRC and Slack
    autotools: use wayland-scanner private-code
    autotools: use the wayland-scanner.pc to locate the prog
    meson: use wayland-scanner private-code
    meson: request native wayland-scanner
    meson: use the wayland-scanner.pc to locate the prog
    meson: set HAVE_VA_X11 when applicable
    style:Correct slight coding style in several new commits
    trace: add Linux ftrace mode for va trace
    trace: Add missing pthread_mutex_destroy
    drm: remove no-longer needed X == X mappings
    drm: fallback to drm driver name == va driver name
    drm: simplify the mapping table
    x11: simplify the mapping table
    android: open() with O_CLOEXEC for device fd
    android: remove convoluted open_device() helper
    android: drop va_fool references
    ci: strengthen ci with -Werror
    ci: va/x11/nvctl: fix Wdeprecated-non-prototype on close_display
    ci: add clang-15 coverage and rearrange runners
    ci: upgrade FreeBSD to 13.1

(From OE-Core rev: ccf646a933fb0274a5fe6ab1055cbfc556351ef2)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-10-26 12:28:38 +01:00
2022-10-25 13:58:49 +01:00
2022-10-26 12:28:38 +01:00
2022-10-25 13:41:36 +01: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