All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 3/3] boot/xilinx-prebuilt: install pld.pdi to target
Date: Fri, 16 May 2025 10:13:30 +0200	[thread overview]
Message-ID: <20250516101330.3de79c77@booty> (raw)
In-Reply-To: <20250409110455.3850790-3-neal.frager@amd.com>

On Wed, 9 Apr 2025 12:04:55 +0100
Neal Frager <neal.frager@amd.com> wrote:

> With the Versal Segmented Configuration, it is possible to load a PL bitstream
> at run-time using the Linux fpgautil application.  Whenever Segmented
> Configuration is used, both the boot.pdi and pld.pdi files will be available
> to Buildroot.  For this reason, this patch improves the user experience by
> installing the pld.pdi file to the target file system for run-time loading
> whenever Versal Segemented Configuration is used.
> 
> If the fpgautil application is available in the target file system, it can
> be used for loading the pld.pdi using the target command below.
> 
> fpgautil -b /lib/firmware/xilinx/*_pld.pdi
> 
> The source code for the fpgautil application can be found here:
> https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-core/recipes-bsp/fpga-manager-script/files/fpgautil.c
> 
> Along with usage details:
> https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1188397412/Solution+Versal+PL+Programming
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

You are proposing to install this file unconditionally. Aren't there
use cases where this is not desired? Also, how large can this file be
for a complex FPGA design?

I think a Kconfig boolean to enable this installation (defaulting no
'n') should be added.

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

  reply	other threads:[~2025-05-16  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 11:04 [Buildroot] [PATCH v3 1/3] boot/xilinx-prebuilt: add segmented config support Neal Frager via buildroot
2025-04-09 11:04 ` [Buildroot] [PATCH v3 2/3] board/versal: change pdi filename to boot.pdi Neal Frager via buildroot
2025-05-16  8:13   ` Luca Ceresoli via buildroot
2025-04-09 11:04 ` [Buildroot] [PATCH v3 3/3] boot/xilinx-prebuilt: install pld.pdi to target Neal Frager via buildroot
2025-05-16  8:13   ` Luca Ceresoli via buildroot [this message]
2025-05-17  9:56     ` Frager, Neal via buildroot
2025-05-13 10:32 ` [Buildroot] [PATCH v3 1/3] boot/xilinx-prebuilt: add segmented config support Frager, Neal via buildroot
2025-05-16  8:13 ` Luca Ceresoli 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=20250516101330.3de79c77@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 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.