linux/poky.git/meta/classes/qemu.bbclass, branch master-uninative

Revert "qemu.bbclass: drop OLDEST_KERNEL reference"

2022-01-07T23:10:26+00:00

This patch was merged on the basis that it wasn't needed with recent versions of qemu. That isn't true and has been showen to cause failures for aarch64 on centos7 hosts. Revert the patch as we'll need a different solution. This reverts commit 94b371e1c9e3cea787d70d6d7a09f7d3d69a30aa. Signed-off-by: Richard Purdie

qemu.bbclass: drop OLDEST_KERNEL reference

2021-12-20T15:29:01+00:00

which is introducing task hash changes for some allarch package builds, and should no longer be needed with recent versions of qemu. (From OE-Core rev: 3a3cfb5f48fc92e548333e5856f3d3fcce27da46) Signed-off-by: Matt Madison Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

qemu: Enable ppc64le support for qemu-usermode

2020-01-22T15:56:14+00:00

glibc defines minimum kernel needed to be 3.10.0 for LE ppc64 (From OE-Core rev: c1c296a42920af6725706bdea8e61b8c4f5f14a8) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

meta/scripts: Various getVar/getVarFlag expansion parameter fixes

2017-01-09T13:39:11+00:00

There were a few straggling expansion parameter removals left for getVar/getVarFlag where the odd whitespace meant they were missed on previous passes. There were also some plain broken ussages such as: d.getVar('ALTERNATIVE_TARGET', old_name, True) path = d.getVar('PATH', d, True) d.getVar('IMAGE_ROOTFS', 'True') which I've corrected (they happend to work by luck). (From OE-Core rev: 688f7a64917a5ce5cbe12f8e5da4d47e265d240f) Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

qemu.bbclass: Allow use different QEMU binary depending of target

2016-09-24T06:30:10+00:00

There are architectures which support running in 32 and 64 bit flavours however the simulation is provided in a specific QEMU setting, requiring us to use a different binary. This patch allow this to be done using, for example: QEMU_TARGET_BINARY_ppce5500 = "qemu-ppc64abi32" (From OE-Core rev: 9b6d414fd27932ed1325de54e8e867c75b340e3d) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

meta/classes/qemu.bbclass: set -cpu of ppce5500/ppce6500 to e500mc

2016-04-15T05:59:43+00:00

The e5500 and e6500 cpu types are not supported by native qemu, set the value of -cpu to e500mc. Without this change, build will fail for packages which use qemuwrapper in compile phase due to the following error. | Unable to find CPU definition e.g. gobject-introspection (From OE-Core rev: e06c5c5447350049ebd1a6245fc2dd2608b265e5) Signed-off-by: Zhenhua Luo Signed-off-by: Richard Purdie

qemu.bbclass: add qemu_wrapper_cmdline()

2016-03-09T17:00:28+00:00

The class had qemu_run_binary() which was not suitable for gobject-introspection, as it required the name of the binary to run. qemu_wrapper_cmdline() returns just the command line string needed to run binaries, and does not require the binary name. (From OE-Core rev: 0b68f0632312392cbd20bfcb9ed4895cfc9883ff) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

qemu.bbclass: clarify QEMU_EXTRAOPTIONS

2016-01-30T11:37:01+00:00

QEMU_EXTRAOPTIONS is a way to add PACKAGE_ARCH specific options to the qemu_run_binary qemu commandline. The base QEMU_EXTRAOPTIONS variable (ie without a PACKAGE_ARCH suffix) is not used, so defining it, either directly or via an over-ride has no effect. Although previously an over-ride for _armv7a was used, it did nothing for most armv7a builds, which typically use PACKAGE_ARCH values such as "cortexa9hf-neon". In practice this worked OK since without a -cpu option, qemu-arm will default to emulating a CPU which supports all required architecture levels. qemu-arm (v2.5.0) with no -cpu option has been confirmed to successfully run binaries built for armv7ve. (From OE-Core rev: 62b25b3489b44969e4adad657daebfaffdb4de56) Signed-off-by: Andre McCurdy Signed-off-by: Ross Burton Signed-off-by: Richard Purdie