6fe601b0cf
version 5.1.2: - avcodec/dstdec: Check for overflow in build_filter() - avformat/spdifdec: Use 64bit to compute bit rate - avformat/rpl: Use 64bit for duration computation - avformat/xwma: Use av_rescale() for duration computation - avformat/sdsdec: Use av_rescale() to avoid intermediate overflow in duration calculation - avformat/sbgdec: Check ts_int in genrate_intervals - avformat/sbgdec: clamp end_ts - avformat/rmdec: check tag_size - avformat/nutdec: Check fields - avformat/flvdec: Use 64bit for sum_flv_tag_size - avformat/jacosubdec: Fix overflow in get_shift() - avformat/genh: Check nb_channels for IMA ADPCM - avformat/dxa: avoid bpc overflows - avformat/dhav: Use 64bit seek_back - avformat/cafdec: Check that nb_frasmes fits within 64bit - avformat/asfdec_o: Limit packet offset - avformat/apm: Use 64bit for bit_rate computation - avformat/ape: Check frames size - avformat/icodec: Check nb_pal - avformat/aiffdec: Use 64bit for block_duration use - avformat/aiffdec: Check block_duration - avformat/mxfdec: only probe max run in - avformat/mxfdec: Check run_in is within 65536 - avcodec/mjpegdec: Check for unsupported bayer case - avcodec/apedec: Fix integer overflow in filter_3800() - avcodec/tta: Check 24bit scaling for overflow - avcodec/mobiclip: Check quantizer for overflow - avcodec/exr: Check preview psize - avcodec/tiff: Fix loop detection - libavformat/hls: Free keys - avcodec/fmvc: Move frame allocation to a later stage - avfilter/vf_showinfo: remove backspaces - avcodec/speedhq: Check width - avcodec/bink: disallow odd positioned scaled blocks - avformat/cafenc: derive Opus frame size from the relevant stream parameters - avformat/dashdec: Fix crash on invalid input/ENOMEM, fix leak - lavc/videotoolbox: do not pass AVCodecContext to decoder output callback - lavc/pthread_frame: always transfer stashed hwaccel state - avcodec/arm/sbcenc: avoid callee preserved vfp registers - avformat/riffdec: don't unconditionally overwrite WAVEFORMATEXTENSIBLE layout - avfilter/vf_scale: overwrite the width and height expressions with the original values - lavc/pthread_frame: avoid leaving stale hwaccel state in worker threads - avutil/tests/.gitignore: Add channel_layout testtool (From OE-Core rev: c893aa4d621de7505fca1bc4b9af22eb503c549c) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> (cherry picked from commit 32da2113e553a3f81f4dcc5834e3fe30f48e4709) 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.