Changelog: =========== General changes: - New meson options xe_eudebug and vmtb. Library changes: - Added PantherLake (PTL) support, unified PCI IDs into one common header pciids.h - Added BMG support for OA (Observability Architecture) for Xe driver. - Added support for Xe3 platforms in GPGPU shader. - Added 6k resolution support for a single CRTC. - Added support for MTL platform in GPGPU compute. Runner changes: - Set option PRUNE_KEEP_ALL as default. - Allow to dynamically ignore dmesg warn messages when generating results, usefull when driver is using kernel fault injection. Test changes: - Added sanity checks for KMS properties. - Improved GPGPU tests for i915 and Xe. - New SRIOV test for Functional Level Reset (FLR) for Xe. - Added test that draws triangle without using 3d commands for vmwgfx. - Added subtest for fallback for DP connector. - Added async flips suspend resume subtest. - New test for error handling of Xe at probe time. - Added testing SIZE_HINTS property in KMS cursor test. - Added KMS testing for ultrajoiner. - New test for TLB invalidation in Xe. - New test for timeslice duration in Xe. - Display brightness test during DPMS on and off. - New tests for EU debugging for Xe. Tools changes: - New power tool for power/energy measurement. - New VM Testbench (VMTB) - SR-IOV Virtual Machine testing tool. - Fixes in amd_hdmi_compliance. - Fixes in intel_reg. (From OE-Core rev: dbec508d17f7ab18efe757cbfc30b81ad5bca7b0) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.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.