d0d6a5b196
Changelog: =========== - sof-soundwire: fix missing MultiCodec1 initialization and Empty condition - UCM2: Intel: sof-hda-dsp: Control SOF processing from UCM - UCM2: SOF: Add example blobs customization for AAEON - UCM2: Add sample SOF processing configuration blobs - codecs: qcom-lpass/tx-macro: Move TX1 MODE ctrl to - ucm2: codecs: wcd937x: add codec sequences - ucm2: soundwire: add rt722 SDCA device - ucm2: Qualcomm: x1e80100: add recording via DMIC01 - ucm2: sof-soundwire: Create ALSA config file for hdmi: - ucm2: Intel/sof-hda-dsp: Create ALSA config file for - ucm2: common: pcm: Add hdmi.conf to handle the creation - sof-soundwire: Add basic support for cs42l43's speaker - qcom: sdm845: MM1: enable jack detection - qcom: sdm845: MM1: use analog volume controls instead of - ucm2: Qualcomm: x1e80100: correct headphones - ucm2: Qualcomm: x1e80100: add number of channels - Add support for Coachz with HDMI disabled - USB-Audio: ALC4080: Add support for MSI MEG Z790 Ace - ucm2: MediaTek: mt8195-sof: Add support for Tomato RT5682s - sof-soundwire: rt1316/rt1318 - fix channel selection for one amp - sof-soundwire: rt1308: Fix single amp configuration - sof-soundwire: fix rt1318 config copy-n-paste error in rt1318spk macro - sof-soundwire: fix rt1318 config typo in rt1318spk macro - USB-Audio: ALC4080: add 0b05:1af1 ASUS ROG Strix Z790-A Gaming Wifi II (From OE-Core rev: 66e53b40f6ecb66916c46fbed17a1eb25f4e4eb5) 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>
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
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
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.