ce55294b63
Bug fix release: av1parse: Fix several issues about the colorimetry. av1parse: fix up various possible logic errors dashsink: fix missing mutex unlock in error code path when failing to get content d3d11videosink: Fix for unhandled mouse double click events interlace: Also handle a missing "interlace-mode" field as progressive msdk: fix build with MSVC mxfdemux: Fix issues at EOS mxfdemux: Handle empty VANC packets nvh264dec, nvh265dec: Fix broken key-unit trick and reverse playback nvvp9sldec: Increase DPB size to cover render delay rvsg: fix cairo include tsdemux: Fix AC-4 detection in MPEG-TS tsdemux: Handle "empty" PMT gracefully va: pool: don't advertise the GST_BUFFER_POOL_OPTION_VIDEO_ALIGNMENT option any more v4l2codecs: Fix memory leak v4l2videodec: set frame duration according to framerate webrtcbin: Update documentation of 'get-stats' action signal webrtcbin: Check data channel transport for notifying 'ice-gathering-state' webrtcbin: Avoid access of freed memory wpe: Reintroduce persistent WebContext Build: use CMake to find some openssl and exr deps Fix multiple "unused-but-set variable" compiler warnings (From OE-Core rev: 8dca7bae0b16c7db820f0d7d60592a7d1d868a8d) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 70ff1c8f54bfb47307cce4d2cb731cc775cd7e21) Signed-off-by: Steve Sakoman <steve@sakoman.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.