From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Neal Frager" <neal.frager@amd.com>, <buildroot@buildroot.org>
Cc: ibai.erkiaga-elorza@amd.com, yann.morin@orange.com,
brandon.maier@collins.com, ju.o@free.fr,
thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
michal.simek@amd.com, romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v1 1/1] boot/xilinx-prebuilt: add local versal xsa support
Date: Mon, 27 Oct 2025 10:25:17 +0100 [thread overview]
Message-ID: <DDSZVS4QNIJ7.3TPH8C5KHSOF2@bootlin.com> (raw)
In-Reply-To: <20251025134655.1068839-1-neal.frager@amd.com>
Hello Neal,
On Sat Oct 25, 2025 at 3:46 PM CEST, Neal Frager wrote:
> Most of the time, users will be running Vivado on their local host machine,
> and will generate a XSA (Xilinx Shell Archive) locally.
>
> Instead of requiring users to create a https:// location for their XSA file,
> this patch improves ease of use by allowing users to work directly with the
> XSA file on their local machine.
>
> BR2_TARGET_XILINX_PREBUILT_VERSAL_XSA_LOCATION can thus be defined as either
> a local location or a https:// location for the XSA file.
>
> In either case, a hash for the XSA file needs to be added to the
> boot/xilinx-prebuilt/xilinx-prebuilt.hash when using this option.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> boot/xilinx-prebuilt/xilinx-prebuilt.mk | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/boot/xilinx-prebuilt/xilinx-prebuilt.mk b/boot/xilinx-prebuilt/xilinx-prebuilt.mk
> index 95b656cdde..a7ec9abff5 100644
> --- a/boot/xilinx-prebuilt/xilinx-prebuilt.mk
> +++ b/boot/xilinx-prebuilt/xilinx-prebuilt.mk
> @@ -10,6 +10,9 @@ ifeq ($(BR2_TARGET_XILINX_PREBUILT_VERSAL_XSA),y)
> XILINX_PREBUILT_FILE = $(call qstrip,$(BR2_TARGET_XILINX_PREBUILT_VERSAL_XSA_LOCATION))
> XILINX_PREBUILT_SITE = $(patsubst %/,%,$(dir $(XILINX_PREBUILT_FILE)))
> XILINX_PREBUILT_SOURCE = $(notdir $(XILINX_PREBUILT_FILE))
> +ifeq ($(findstring ://,$(XILINX_PREBUILT_FILE)),)
> +XILINX_PREBUILT_SITE_METHOD = file
> +endif
According to the BR2_TARGET_XILINX_PREBUILT_VERSAL_XSA_LOCATION help text,
using a local file is already supported by using the file:// URL prefix.
Can you elaborate on which use case you are adding now? I think you are
just making it a bit easier and cleaner to do the same thing as before by
using a path instead of a URL, but I may be wrong.
Also, updating the Config.in help text should part of this patch.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-10-27 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 13:46 [Buildroot] [PATCH v1 1/1] boot/xilinx-prebuilt: add local versal xsa support Neal Frager via buildroot
2025-10-27 9:25 ` Luca Ceresoli via buildroot [this message]
2025-10-27 11:45 ` Frager, Neal via buildroot
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=DDSZVS4QNIJ7.3TPH8C5KHSOF2@bootlin.com \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox