* [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image
@ 2023-08-16 20:42 Sandeep Gundlupet Raju
2023-08-17 20:03 ` Bruce Ashfield
0 siblings, 1 reply; 2+ messages in thread
From: Sandeep Gundlupet Raju @ 2023-08-16 20:42 UTC (permalink / raw)
To: meta-virtualization, bruce.ashfield, christopher.w.clark; +Cc: mark.hatle
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>
---
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"
--
2.34.1
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image
2023-08-16 20:42 [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image Sandeep Gundlupet Raju
@ 2023-08-17 20:03 ` Bruce Ashfield
0 siblings, 0 replies; 2+ messages in thread
From: Bruce Ashfield @ 2023-08-17 20:03 UTC (permalink / raw)
To: Sandeep Gundlupet Raju
Cc: meta-virtualization, christopher.w.clark, mark.hatle
merged.
Bruce
In message: [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image
on 16/08/2023 Sandeep Gundlupet Raju wrote:
> 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>
> ---
> 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"
> --
> 2.34.1
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-08-17 20:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-16 20:42 [meta-virtualization][master][PATCH] xen-boot-cmd: Remove hard assigment for ramdisk image Sandeep Gundlupet Raju
2023-08-17 20:03 ` Bruce Ashfield
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.