From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH] xen-boot-cmd.inc: Fix initrd boot issue with 6.6 kernel
Date: Thu, 22 Feb 2024 17:15:44 +0000 [thread overview]
Message-ID: <ZdeBQFvet94Jb6Kv@gmail.com> (raw)
In-Reply-To: <20240222013230.1183593-1-sandeep.gundlupet-raju@amd.com>
merged.
Bruce
In message: [meta-virtualization][PATCH] xen-boot-cmd.inc: Fix initrd boot issue with 6.6 kernel
on 21/02/2024 Sandeep Gundlupet Raju wrote:
> 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>
> ---
> dynamic-layers/xilinx/recipes-bsp/u-boot/xen-boot-cmd.inc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> 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 b2b76120..7a4e41a6 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
> @@ -9,8 +9,8 @@ KERNEL_OFFSET:versal ?= "0xE00000"
> DEVICETREE_OFFSET:zynqmp ?= "0xC000000"
> DEVICETREE_OFFSET:versal ?= "0xC000000"
>
> -RAMDISK_OFFSET:zynqmp ?= "0x2400000"
> -RAMDISK_OFFSET:versal ?= "0x2400000"
> +RAMDISK_OFFSET:zynqmp ?= "0x2600000"
> +RAMDISK_OFFSET:versal ?= "0x2600000"
>
> XEN_OFFSET:zynqmp ?= "0xBA00000"
> XEN_OFFSET:versal ?= "0xBA00000"
> --
> 2.34.1
>
prev parent reply other threads:[~2024-02-22 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 1:32 [meta-virtualization][PATCH] xen-boot-cmd.inc: Fix initrd boot issue with 6.6 kernel Sandeep Gundlupet Raju
2024-02-22 17:15 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZdeBQFvet94Jb6Kv@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=sandeep.gundlupet-raju@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.