linux/poky.git, branch yocto-4.1Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=yocto-4.12022-09-30T09:39:16+00:00build-appliance-image: Update to master head revision2022-09-30T09:39:16+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-30T09:39:13+00:00urn:sha1:5200799866b92259e855051112520006e1aaaac0
(From OE-Core rev: 744a2277844ec9a384a9ca7dae2a634d5a0d3590)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
go: Fix reproducibility failures2022-09-30T09:32:21+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-30T09:16:23+00:00urn:sha1:4f942c272d4417b5b719df25b80a6a6b54669a73
We're seeing "cmd" static libs being sometimes present and sometimes not.
The issue depends whether BUILD == TARGET so they're present for qemux86-64
on x86-64 hosts but not for qemux86-64 on an aarch64 system.
Add an extra deletion to make the files consistent between the different
hosts.
(From OE-Core rev: 6e652835814c389a826ad2d262ee26c14dfb48b5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
build-appliance-image: Update to master head revision2022-09-29T20:57:53+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-29T20:57:48+00:00urn:sha1:bfb8626cc073b2b368ae7286fe6b0361398e4c7d
(From OE-Core rev: 032cffb4a6011fbe55790c18df4dfcedd9911698)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake: Bump to version 2.2.02022-09-29T20:56:55+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-29T20:56:31+00:00urn:sha1:1b014677b7bd1af9c9bb064dfcceefd2223ce13e
(Bitbake rev: 074da4c469d1f4177a1c5be72b9f3ccdfd379d67)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
poky: Update to match poky version numbers2022-09-29T20:54:34+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-29T20:54:25+00:00urn:sha1:0084c6704be8f3473a8f9cc474faa0369d548c17
(From meta-yocto rev: 913bd8ba4dd1d5d2a38261bde985b64a36e36281)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
poky: Update to 4.1 version2022-09-29T20:54:34+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-29T20:50:49+00:00urn:sha1:0e2698b0a88113e7a095d1c54070d2af69d26748
(From meta-yocto rev: 152d88fa34debb664c7a31b8e733b3de6fbb5561)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
layer.conf: Update to use langdale as the core layer name2022-09-29T20:54:34+00:00Richard Purdierichard.purdie@linuxfoundation.org2022-09-29T20:52:56+00:00urn:sha1:d094d3025f691376f7060a3cb0e49ca0be56c7c7
(From OE-Core rev: f5516b5cdaece26e6873b3b1c9371f44bd1db5f1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: utils: Add enable_loopback_networking()2022-09-29T20:26:09+00:00Mattias Jernbergmattiasj@axis.com2022-09-29T16:37:13+00:00urn:sha1:74877d2dc267c958d02342d16cebeaeded23df8c
It can be used to enable the loopback interface, typically after calling
disable_network().
Also correct a typo in a debug message.
(Bitbake rev: 0d317209d4234c5f05a9fcdc13c52f502f104018)
Signed-off-by: Mattias Jernberg <mattias.jernberg@axis.com>
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: doc: bitbake-user-manual: Add definition for BB_PRESSURE_MAX variables2022-09-29T20:24:29+00:00Aryaman Guptaaryaman.gupta@windriver.com2022-09-19T14:58:12+00:00urn:sha1:764bbf2a9b001f7bf78b689613d8993a66b87430
Add the definitions for the BB_PRESSURE_MAX{CPU|IO|MEMORY} variables in the
bitbake varibales glossary. Further information on how to determine a good
threshold will be added to the Yocto reference manual in a later commit.
(Bitbake rev: c014281f72f4f54ec8e681ef2b8e1080de9ab5cf)
Signed-off-by: Aryaman Gupta <aryaman.gupta@windriver.com>
Signed-off-by: Randy Macleod <Randy.Macleod@windriver.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Quentin Schulz <foss+yocto@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2/ssh.py: fix checkstatus2022-09-29T20:24:29+00:00Pascal Bachpascal.bach@siemens.com2022-09-28T20:25:54+00:00urn:sha1:f76140955183259878df7425774aa18d0032b397
The output of runfetchcmd is always empty in this case, as
the test doesn't produce any output.
SSH either returns 0 or 1, which is handled via exceptions.
This means the current check is not only unnecessary but prevents the
function from working.
We can just assume that if we reach the end of the function that the
file exists and return True.
(Bitbake rev: d599af48635fab587e5b913591b95daf87b40080)
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>