Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: Neal Frager <neal.frager@amd.com>,
	ibai.erkiaga-elorza@amd.com, luca.ceresoli@bootlin.com,
	brandon.maier@collins.com, ju.o@free.fr, fabio.caccamo@amd.com,
	romain.naour@smile.fr, michal.simek@amd.com, arnout@mind.be
Subject: Re: [Buildroot] [PATCH v1 1/2] package/fpgautil: new package
Date: Tue, 22 Apr 2025 22:36:01 +0200	[thread overview]
Message-ID: <20250422223601.1ca5077b@windsurf> (raw)
In-Reply-To: <20250408114834.733285-1-neal.frager@amd.com>

Hello Neal,

On Tue, 8 Apr 2025 12:48:33 +0100
Neal Frager via buildroot <buildroot@buildroot.org> wrote:

> Add a new package to Buildroot called 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 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 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/<design-name>_pld.pdi -o /lib/firmware/<dtbo-name>.dtbo
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

Thanks for this new package.

I think we should probably name this xilinx-fpgautil, because it's
really very specific to Xilinx platforms if I understand correctly.


> diff --git a/package/fpgautil/Config.in b/package/fpgautil/Config.in
> new file mode 100644
> index 0000000000..8a1f557f7e
> --- /dev/null
> +++ b/package/fpgautil/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_FPGAUTIL
> +	bool "fpgautil script"

This should only contain the package name, i.e "fpgautil", or if we
rename it "xilinx-fpgautil".

> +FPGAUTIL_VERSION = xlnx-rel-v2024.2_update3
> +FPGAUTIL_SITE = $(call github,Xilinx,meta-xilinx,$(FPGAUTIL_VERSION))

I was going to suggest that we download only the source file, but that
doesn't work because it doesn't contain the version in its file name.
So we have to download the whole Yocto layer just to grab one source
file. Sigh.

What about using the vendor-agnostic OpenFPGALoader instead, packaged
as package/openfpgaloader/ ?

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2025-04-22 20:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 11:48 [Buildroot] [PATCH v1 1/2] package/fpgautil: new package Neal Frager via buildroot
2025-04-08 11:48 ` [Buildroot] [PATCH v1 2/2] configs/xilinx: add fpgautil to xilinx defconfigs Neal Frager via buildroot
2025-04-22 20:36 ` Thomas Petazzoni via buildroot [this message]
2025-04-24  5:31   ` [Buildroot] [PATCH v1 1/2] package/fpgautil: new package Frager, Neal via buildroot
2025-04-24 19:39     ` Thomas Petazzoni via buildroot
2025-04-24 20:14       ` 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=20250422223601.1ca5077b@windsurf \
    --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