Changelog: =========== - Added gcc warns: dangling-pointer, int-conversion - More guidelines in CONTRIBUTING. - Reorganized Tests: Moved all vendor specific tests to their own dir - Fix musl/uclibc build - New KMS framebuffer stress benchmark. - Added basic Xe support in gem_wsim. - Add documentation about cross-builds. - Improve tests documentation. - Add Battlemage (BMG) support in xe_pciids.h - Add amdgpu GFX1152, GFX1150 and gfx12. - Added inline support for iga64 assembly in GPGPU shader. - Improved KUnit support. - Enable igt run on security enhanced distros - Use blitter as a default for all KMS tests. - Increased MAX supported pipes to 16 (Pipe-A to Pipe-P) - Added generic way to reset sysfs/debugfs attrs to default values upon exit. - Added hook scripts to igt_runner. - Added support for Xe in KMS tests. - Added new subtests and improvements to VRR. - Added new subtests to force joiner. - Added fbdev tests to Xe. - Added amdgpu fuzzing tests. - Added syncobj_eventfd test. - Added basic Single-Root IO Virtualization (SRIOV) test. - Added prime test for vmwgfx. - Improved core_getversion. - Improved kms_atomic on non-mutable planes. - Added and improved Xe tests. - New Xe perf/OA tools. - New intel_tiling_detect tool. - New option in lsgpu for printing GPU on PCI bus, working also in case when no gpu driver is loaded. - Added sysfs profiling knob to gputop. - Support for Xe in gputop. - Improved generating test lists at compilation time. - Improved code coverage. - Improved intel_vbt_decode and other intel tools. (From OE-Core rev: 2c369fcbe7ee3353cf5c2bcbe06fe0767a85074e) Signed-off-by: Wang Mingyu <wangmy@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.