Some versions of python/bitbake appear to allow 'true' and 'false',
but this is incorrect, True and False are the correct boolean variables.
Fixes:
ERROR: ExpansionError during parsing .../meta-xilinx/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx-scr.bb
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Xen related boot script offset was override from
meta-virtualization for non xen builds.
ERROR: RD image overlaps OS image (OS=0xe00000..0x2610000)
Add to include xen boot script only if ENABLE_XEN_UBOOT_SCR variable
set from the configuration file and xen enabled in DISTRO_FEATURES to
avoid override.
Signed-off-by: John Vicky Vykuntapu <johnvicky.vykuntapu@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Due to increase in 6.6 kernel image size xen ramdisk offset was
overlapping with kernel image. This causes xen randisk image boot
failures. Hence increase the ramdisk offset to fix initrd boot
issue.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Remove device_type device tree nodes as these nodes are no longer
required for Xen qemu boot.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Setting hard assignment for RAMDISK_IMAGE will take precedence during
variable pre-expansion. Hence set RAMDISK_IMAGE variable with soft
assignment.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Add new boot.cmd.xen to u-boot-xlnx-scr bbappend to enable
Xen support for ZynqMP and Versal devices.
User can enable xen u-boot script by adding below variable from
configuration file.
BOOTMODE = "xen"
This u-boot script also supports to configure below Xen params from
configuration file
params variable assignment
------ -------------------
duart XEN_SERIAL_CONSOLES = "serial0"
dom0_mem DOM0_MEM = "1500M"
dom0_max_vcpus DOM0_MAX_VCPUS = "1"
extra params XEN_CMDLINE_APPEND = "loglvl=all"
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Add device-tree files for Xen support, Earlier all these files
were in meta-petalinux layer, Hence move these files to this layer
so that users can build Xen without including meta-petalinux.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Move the xilinx specific bbappend to a wildcard append.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
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 <richard.purdie@linuxfoundation.org>
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 <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
As of the gatesgarth you are no longer allowed to remove setscene tasks
as the eSDK generation expects for tasks to actually be executed.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Although this dynamic layer currently only adds Xen support, it will
eventually hold other board and platform specific tweaks to core
meta-virt recipes.
Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
