From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ibai.erkiaga-elorza@amd.com, arnout@mind.be,
brandon.maier@collins.com, ju.o@free.fr,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org,
fabio.caccamo@amd.com, romain.naour@smile.fr,
michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v2 1/2] package/xilinx-fpgautil: new package
Date: Wed, 30 Apr 2025 15:05:57 +0200 [thread overview]
Message-ID: <20250430150557.4f8e7efe@booty> (raw)
In-Reply-To: <20250424063619.789456-1-neal.frager@amd.com>
Hello Neal,
On Thu, 24 Apr 2025 07:36:18 +0100
Neal Frager <neal.frager@amd.com> wrote:
> Add a new package to Buildroot called xilinx-fpgautil which builds the Xilinx
> fpgautil script which can be used for loading FPGA bitstreams on zynq, zynqmp
> and versal products at run-time. This is a handy application for loading
> FPGA bitstreams and their corresponding device tree overlays.
>
> An explanation of how this script can be used for each type of product can be
> found on the wiki pages below.
>
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841645/Solution+Zynq+PL+Programming+With+FPGA+Manager
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841847/Solution+ZynqMP+PL+Programming
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1188397412/Solution+Versal+PL+Programming
>
> In addition, the source code for xilinx-fpgautil can be found here:
> https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-core/recipes-bsp/fpga-manager-script/files/fpgautil.c
>
> The Xilinx fpgautil script can be used hand in hand with the Versal Segmented
> Configuration with the following example command for programming the pld.pdi
> file to the Versal FPGA:
>
> fpgautil -b /lib/firmware/xilinx/<design-name>_pld.pdi -o /lib/firmware/xilinx/<dtbo-name>.dtbo
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
[...]
> --- /dev/null
> +++ b/package/xilinx-fpgautil/xilinx-fpgautil.mk
> @@ -0,0 +1,22 @@
> +################################################################################
> +#
> +# xilinx-fpgautil
> +#
> +################################################################################
> +
> +XILINX_FPGAUTIL_VERSION = xlnx-rel-v2024.2_update3
> +XILINX_FPGAUTIL_SITE = $(call github,Xilinx,meta-xilinx,$(XILINX_FPGAUTIL_VERSION))
> +XILINX_FPGAUTIL_LICENSE = MIT
> +XILINX_FPGAUTIL_LICENSE_FILES = COPYING.MIT
> +
> +define XILINX_FPGAUTIL_BUILD_CMDS
> + $(TARGET_MAKE_ENV) $(TARGET_CC) $(TARGET_LDFLAGS) \
> + $(@D)/meta-xilinx-core/recipes-bsp/fpga-manager-script/files/fpgautil.c \
> + -o $(@D)/fpgautil
> +endef
> +
> +define XILINX_FPGAUTIL_INSTALL_TARGET_CMDS
> + $(INSTALL) -m 0755 -D $(@D)/fpgautil $(TARGET_DIR)/bin/fpgautil
^^^^
Are you installing in /bin for some reason? /usr/bin seems the right
place.
Otherwise looks good, so in case you send v3 with only the /usr/bin
change, you can add:
[build-tested only]
Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
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-04-30 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 6:36 [Buildroot] [PATCH v2 1/2] package/xilinx-fpgautil: new package Neal Frager via buildroot
2025-04-24 6:36 ` [Buildroot] [PATCH v2 2/2] configs/xilinx: add xilinx-fpgautil to xilinx defconfigs Neal Frager via buildroot
2025-04-30 13:06 ` Luca Ceresoli via buildroot
2025-04-30 13:05 ` Luca Ceresoli via buildroot [this message]
2025-05-02 7:33 ` [Buildroot] [PATCH v2 1/2] package/xilinx-fpgautil: new package 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=20250430150557.4f8e7efe@booty \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=brandon.maier@collins.com \
--cc=fabio.caccamo@amd.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@smile.fr \
--cc=thomas.petazzoni@bootlin.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