0aa9d253b8
Updating linux-yocto/5.14 to the latest korg -stable release that comprises
the following commits:
a0265dd8262d Linux 5.14.18
1379769b0b46 rsi: fix control-message timeout
eda57a310234 media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init
5013f2aaf959 staging: rtl8192u: fix control-message timeouts
f3422d1fceba staging: r8712u: fix control-message timeout
373ac8c59414 comedi: vmk80xx: fix bulk and interrupt message timeouts
7b0e35618932 comedi: vmk80xx: fix bulk-buffer overflow
278484ae9329 comedi: vmk80xx: fix transfer-buffer overflows
4a9d43cb5d5f comedi: ni_usb6501: fix NULL-deref in command paths
3ac273d154d6 comedi: dt9812: fix DMA buffers on stack
b2fa1f52d22c isofs: Fix out of bound access for corrupted isofs image
befd23bd3b17 staging: rtl8712: fix use-after-free in rtl8712_dl_fw
bec32c40e438 binder: don't detect sender/target during buffer cleanup
68abe9aefc40 binder: use cred instead of task for getsecid
46088365bab7 binder: use cred instead of task for selinux checks
fbb106e79524 binder: use euid from cred instead of using task
f9b4ef2504bb Revert "proc/wchan: use printk format instead of lookup_symbol_name()"
4674de4e2734 usb-storage: Add compatibility quirk flags for iODD 2531/2541
6be11f54f5d4 usb: musb: Balance list entry in musb_gadget_queue
d7f4ffba71d0 usb: gadget: Mark USB_FSL_QE broken on 64-bit
d3c7daab289d usb: ehci: handshake CMD_RUN instead of STS_HALT
a4cdb4c9c453 Revert "x86/kvm: fix vcpu-id indexed array sizes"
2f63111ab86f KVM: x86: avoid warning with -Wbitwise-instead-of-logical
f468cbedb2a7 ALSA: pci: cs46xx: Fix set up buffer type properly
186155ac272e ALSA: pcm: Check mmap capability of runtime dma buffer at first
(From OE-Core rev: 7f09947f9fc12f7b548f18573ffbc452837527bd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
||
|---|---|---|
| bitbake | ||
| contrib | ||
| documentation | ||
| meta | ||
| meta-poky | ||
| meta-selftest | ||
| meta-skeleton | ||
| meta-yocto-bsp | ||
| scripts | ||
| .gitignore | ||
| .templateconf | ||
| LICENSE | ||
| LICENSE.GPL-2.0-only | ||
| LICENSE.MIT | ||
| MAINTAINERS.md | ||
| Makefile | ||
| MEMORIAM | ||
| oe-init-build-env | ||
| README.hardware.md | ||
| README.md | ||
| README.OE-Core.md | ||
| README.poky.md | ||
| README.qemu.md | ||
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.