797c243ecc
Include fixes for CVE-2023-45288 Upgrade to latest 1.22.x release [1]: $ git --no-pager log --oneline go1.22.1..go1.22.2 dddf0ae40f (tag: go1.22.2) [release-branch.go1.22] go1.22.2 e55d7cf843 [release-branch.go1.22] net/http: update bundled golang.org/x/net/http2 4edf4bb2c6 [release-branch.go1.22] all: update golang.org/x/net 2c6d106541 [release-branch.go1.22] cmd/compile: don't assume args are always zero-extended 46587483e3 [release-branch.go1.22] cmd/compile: fix sign/zero-extension removal 0a5b33a883 [release-branch.go1.22] encoding/gob: make x509.Certificate marshalable again 0c53f93faa [release-branch.go1.22] cmd/go/internal/modfetch: pass "-c" arguments to git before subcommands abfd578156 [release-branch.go1.22] runtime: fix EvFrequency event value on Windows in the new tracer 7fb7acb82d [release-branch.go1.22] cmd/link/internal/riscv64: generate local text symbols for R_RISCV_CALL e23707b59c [release-branch.go1.22] go/types, types2: handle Alias types in substitution 3826650c99 [release-branch.go1.22] cmd/compile: fix early deadcode with label statement e71b0b1fee [release-branch.go1.22] cmd/compile: fix copying SSA-able variables optimization 9508eae5d1 [release-branch.go1.22] cmd/internal/obj/ppc64: don't modify runtime.elf_* symbols 35b1a146d9 [release-branch.go1.22] cmd/go: respect -coverpkg for unselected no-test packages [1] https://github.com/golang/go/compare/go1.22.1...go1.22.2 (From OE-Core rev: 348e676046159b00a6f06f68336aa5443919c139) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> 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.