f6e2a22000
Changes from version 1.20.2: androidmedia: Add H.265 encoder mapping avfvideosrc: fix wrong framerate selected for caps d3d11decoder: Fix for alternate interlacing signalling d3d11decoder: Do not preallocate texture using downstream d3d11 buffer pool d3d11decoder: Copy HDR10 related caps field manually d3d11decoder: Work around Intel DXVA driver crash d3d11screencapture: Set viewport when drawing mouse cursor d3d11screencapture: Fix missing/outdated cursor shape d3d11screencapturesrc: Fix crash when d3d11 device is different from owned one h264decoder: Fix for unhandled low-delay decoding case matroskademux, qtdemux: Fix integer overflows in zlib/bz2/etc decompression code (Security fix) mpegtsmux: Make sure to set srcpad caps under all conditions before outputting the first buffer mpegtsmux: sends segment before caps mxfdemux: Handle files produced by legacy FFmpeg nvh264dec,nvh265dec: Don't realloc bitstream buffer per slice nvcodec: cuda-converter: fix nvrtc compilation on non-English locale systems opencv: Allow building against 4.6.x pcapparse: Set timestamp in DTS, not PTS rtmp2: fix allocation of GstRtmpMeta which caused crashes on 32-bit platforms rtmp2sink crash on Android arm 32 - cerbero 1.20.2.0 sdpdemux: Release request pads from rtpbin when freeing a stream va: Add O_CLOEXEC flag at opening drm device (so subprocesses won't have access to it) webrtcbin: Reject answers that don't contain the same number of m-line as offer webrtc: datachannel: Notify low buffered amount according to spec (From OE-Core rev: 0ead6c03c2594158200ee2c490ec683570310036) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 200c8b77e86e6bd23954c3b4e48d4d069cb16f37) 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.