From 7fee614060705a64ea512e4035f650352f115bad Mon Sep 17 00:00:00 2001 From: Sandeep Gundlupet Raju Date: Wed, 16 Aug 2023 14:42:55 -0600 Subject: xen-boot-cmd: Remove hard assigment for ramdisk image 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 Signed-off-by: Bruce Ashfield --- dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc b/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc index 38f6f267..b2b76120 100644 --- a/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc +++ b/dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc @@ -18,7 +18,7 @@ XEN_LOAD_ADDRESS ?= "${@append_baseaddr(d,d.getVar('XEN_OFFSET'))}" # If dom0-ramdisk is used for Xen boot then set RAMDISK image to cpio.gz XEN_IMAGE_NAME ?= "xen" -RAMDISK_IMAGE = "rootfs.cpio.gz" +RAMDISK_IMAGE ?= "rootfs.cpio.gz" # Set the amount of memory for dom0 depending on total available memory size(DDR). DOM0_MEM ?= "1500M" -- cgit v1.2.3-54-g00ecf