linux/meta-virtualization.git/conf/distro, branch easyjson

global: overrides conversion pass 2

2021-08-02T21:18:08+00:00

Signed-off-by: Bruce Ashfield

global: overrides syntax conversion

2021-08-02T21:17:53+00:00

OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

qemuboot, xen-image-minimal: enable runqemu for qemuarm64 Xen images

2021-07-29T14:55:56+00:00

The Xen hypervisor built for Arm 64-bit targets can be launched with runqemu by providing a Device Tree binary and configuration for Qemu, which enables interactive testing of Xen images. Add qemuboot-xen-dtb.bbclass to add a new bitbake task for generating the dtb file by using lopper on a device tree produced by Qemu. Add qemuboot-xen-defaults.bbclass to supply working default parameters for the qemuarm64 machine and general support for qemuboot for Xen, and adjust the defaults as needed to boot successfully in testing. Development aided by this script by Stewart Hildebrand of DornerWorks: https://gist.github.com/stewdk/110f43e0cc1d905fc6ed4c7e10d8d35e Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, rpi4: move rpi4-machine+xen-distro cfg into dynamic layer

2021-04-30T03:05:11+00:00

Improve meta-virt-xen.inc by moving all the Raspberry Pi 4 config settings to a new xen-raspberrypi4-64.inc file in the raspberrypi dynamic layer. The new .inc file is included only for the raspberrypi4-64 MACHINE, so the config settings no longer need to be applied using overrides. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, rpi4: switch Xen-on-Rpi4 kernel preference to linux-yocto

2021-04-30T03:05:11+00:00

The 5.10 version of the Linux Yocto kernel supports running Xen on the Raspberry Pi 4, so the previous preference for linux-yocto-dev can be replaced. Use the ?= operator to set the kernel preference now since meta-raspberrypi commit e0b4b8c5d introduced use of the weak default for kernel preference in that layer to allow this here. KERNEL_DEVICETREE needs to be set to match the build outputs of the selected kernel, in this case: "broadcom/bcm2711-rpi-4-b.dtb" Tested with kernel version: SRCREV_machine = "cf5b0320cf4544d3db9ce3ddd6ddb7553a610651" SRCREV_meta="031f6c76e488a3563f35258c72ff1de3e25a512e" Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen: bump default version to 4.15-stable

2021-04-19T03:05:30+00:00

Signed-off-by: Bruce Ashfield

xen, xen-tools: add recipes for new stable Xen 4.15 release

2021-04-19T00:19:22+00:00

The recipes are introduced as the non-default version by adding an expressed PREFERRED_VERSION for 4.14 in: conf/distro/include/meta-virt-default-versions.inc to keep the Xen 4.14 recipes as default for the Hardknott release. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, raspi4, linux-yocto-dev: Enable Xen on Raspberry Pi 4

2020-08-11T19:58:37+00:00

Enable linux-yocto-dev as the Linux kernel for Xen on the Raspberry Pi 4, with the bcm-2xxx-rpi4 KMACHINE and KBRANCH. Set a Raspberry Pi SD card variable to increase the size of the boot partition to accommodate both the kernel and the Xen hypervisor. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, linux-raspberrypi4: remove linux-raspberrypi bbappends and patches

2020-08-11T19:58:37+00:00

Retiring use of the downstream vendor kernel for use with Xen. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, rpi4: use RPI_EXTRA_CONFIG and drop the rpi-config_git.bbappend

2020-08-11T19:58:37+00:00

The GIC that is needed by Xen can be enabled via the rpi-config recipe variable. Fixes the build after the upstream recipe changed recently. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield