f7accf6941
configure.patch refreshed for 3.11.1 Changelog: =========== * Fixed wrong API version in lib/pci.h. * Updated README.Windows. * Fix compilation on Windows. * update-pciids now supports XZ compression. If libpci is configured with support for compression, all downloaded files are recompressed as gzip. Otherwise they are stored as plain text. * update-pciids now sends itself as the User-Agent. * Added a pcilmr utility for PCIe lane margining. * Re-factored access to i386 ports on all relevant platforms. * Added i386 port access on OpenBSD. * Back-ends for Windows received many bug fixes and improvements. * ECAM back-end now scans ACPI and BIOS memory faster. * Linux systems without pread/pwrite are no longer supported as they are hopefully long gone. This helps avoid the tricky check for presence of pread which was found to fail on musl libc. * Improved decoding of PCIe control and status registers. * Decoding of CXL capabilities now supports up to CXL 3.0. * lspci now displays interrupt message numbers consistently across different capabilities. * Cache of IDs resolved via DNS, which was located in ~/.pci-ids by default, is now stored according to the XDG base directory specification in $XDG_CACHE_HOME/pci-ids. * All source files now have SPDX license identifiers. * Internal: The "aux" fields of structs pci_access and pci_dev reserved for use by back-ends were renamed to backend_data to better reflect their meaning. * As usually, various minor bug fixes and updated pci.ids. (From OE-Core rev: bbda388857284612190b58abe8d73c93e39d1574) 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.