linux/poky.git/meta, branch yocto-2.7

build-appliance-image: Update to warrior head revision

2019-04-14T20:29:15+00:00

(From OE-Core rev: f571b188177788d8ed0a7f3efe3569f153b1b0d3) Signed-off-by: Richard Purdie

Revert "nettle: fix ptest failure"

2019-04-12T22:01:22+00:00

This reverts commit 83faaf7b2a5f4fc4ae504b300134409e90389770. This should never have merged as the change was rejected upstream and adding a library to the ptest package resulted in it providing that SONAME which led to being included in images like core-image-sato. This in turn led to a ton of ptest failures in the 2.7 r1 QA report. (From OE-Core rev: 039e7b25f0018e6923d14b40c35252f99e1d3ea3) Signed-off-by: Richard Purdie

build-appliance-image: Update to warrior head revision

2019-04-12T12:52:35+00:00

(From OE-Core rev: b5f493078335a77dea2f229d36629399d897a528) Signed-off-by: Richard Purdie

kernel-fitimage: support RISC-V

2019-04-12T12:40:21+00:00

Support RISC-V kernel image, using the "Image" target. This change allows RISC-V support for fitImage via the following flow: OpenSBI -> u-boot (as payload) -> Linux kernel (as fitImage with ramdisk and dtb). This was tested using QEMU RISC-V 64-bit. (From OE-Core rev: 35d0842c637b7d7ce0ab01f43b594c19a964872f) Signed-off-by: Michael Scott Signed-off-by: Richard Purdie

nettle: fix ptest failure

2019-04-12T12:40:21+00:00

Remove dlopen-test.patch which originally used to fix the test dlopen-test, but autually the patch didn't resolve the issue as dlopen-test.patch supposes the file /usr/lib/libnettle.so exists. Instead deploy ${D}${PTEST_PATH}/libnettle.so to fix the dlopen-test failure. Update the initialization for the salt to fix below Segmentation fault and also nettle-pbkdf2-test failure. # echo -n passwd| nettle-pbkdf2 -i 1 -l 16 salt [65534.886509] nettle-pbkdf2[708]: segfault at 1f594260 ip 00007f3332256998 sp 00007fff60d44410 error 4 in libnettle.so.6.5[7f3332244000+1d00] [65534.887525] Code: e8 6d db fe ff 44 01 6d 68 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 2e 0f 1f 84 00 00 00 00 00 49 89 dc e9 68 ff f Segmentation fault (From OE-Core rev: 83faaf7b2a5f4fc4ae504b300134409e90389770) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie

gcc-cross-canadian: Make baremetal specific code generic

2019-04-12T12:40:21+00:00

baremetal override is not valid for cross-canadian anymore therefore use the TARGET_OS overrides Fixes e.g. https://github.com/riscv/meta-riscv/issues/117 (From OE-Core rev: 1bc122a044de280d17525c8e5ee66e81775a7d8b) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

image_types.bbclass: fix a race between the ubi and ubifs FSTYPES

2019-04-12T12:32:48+00:00

The ubi, ubifs and multiubi FSTYPES calls `mkfs.ubifs' to create UBIFS images. In do_image_ubi, $vname is empty, the name of UBIFS image conflicts with the one in do_image_ubifs, and it's a race risk. [do_image_ubi] mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${IMGDEPLOYDIR}/${IMAGE_NAME}${vname}${IMAGE_NAME_SUFFIX}.ubifs ${mkubifs_args} [do_image_ubi] [do_image_ubifs] mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.ubifs ${MKUBIFS_ARGS} [do_image_ubifs] In do_image_multiubi, $vname is not empty, the UBIFS image name does not conflict with others. So do not call mkfs.ubifs in do_image_ubi and depend on do_image_ubifs to create UBIFS images. The fix does not affect do_image_multiubi which still call mkfs.ubifs to create multiple UBIFS images and symlinks. [YOCTO #13272] (From OE-Core rev: 3e5f075184d91dd99cf25cfe84bba1c946ed0c7c) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

e2fsprogs: Skip slow ptest tests

2019-04-12T08:29:06+00:00

The slow tests run unreliably with our current setup/infrsstructure/timeouts. There are only five slow ones and having the other ~250 run reliably without timeouts is the priority right now. We can revisit the slow tests at some later date if wanted. (From OE-Core rev: 7469c2a5595337fc4407fa7a2ad06b5bf2347545) Signed-off-by: Richard Purdie

goarch.bbclass: Simplify logic

2019-04-12T08:29:06+00:00

Further simplification of the go_map_arm() function. (From OE-Core rev: 9c333505897b2bf0d80737c855af31785d23435a) Signed-off-by: Mark Asselstine Signed-off-by: Richard Purdie

go.bbclass: Remove unused override

2019-04-12T08:29:06+00:00

The x86 override means the i586 one isn't necessary. (From OE-Core rev: 1658bf2dbdfe1a5b38efcc03359c9937506c120c) Signed-off-by: Mark Asselstine Signed-off-by: Richard Purdie