All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: Neal Frager via buildroot <buildroot@buildroot.org>,
	"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
	"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
	"brandon.maier@collins.com" <brandon.maier@collins.com>,
	"ju.o@free.fr" <ju.o@free.fr>,
	"Caccamo, Fabio" <fabio.caccamo@amd.com>,
	"romain.naour@smile.fr" <romain.naour@smile.fr>,
	"Simek, Michal" <michal.simek@amd.com>,
	"arnout@mind.be" <arnout@mind.be>
Subject: Re: [Buildroot] [PATCH v1 1/2] package/fpgautil: new package
Date: Thu, 24 Apr 2025 21:39:19 +0200	[thread overview]
Message-ID: <20250424213919.2e40c109@windsurf> (raw)
In-Reply-To: <SA1PR12MB561566BC39D926C9E2AE0D64F0852@SA1PR12MB5615.namprd12.prod.outlook.com>

Hello Neal,

On Thu, 24 Apr 2025 05:31:57 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:

> > This should only contain the package name, i.e "fpgautil", or if we
> > rename it "xilinx-fpgautil".  
> 
> Ok, I will change this.

Thanks, I've seen your v2. Much appreciated.

> > +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.  
> 
> I had the exact same thought, but could not come up with a better solution.
> At least the meta-xilinx repo is still <1MB in size, so the download and
> extraction time is still in the noise for the overall build process.

Ah, it's only 1 MB, then fair enough.

> > What about using the vendor-agnostic OpenFPGALoader instead, packaged
> > as package/openfpgaloader/ ?  
> 
> I was not aware of this package.  Do you know how well it is maintained?

The Buildroot package I don't know, but the upstream OpenFPGALoader
package is very active, and well maintained. It is becoming the
de-facto open-source standard for FPGA programming.

> At the moment, I have two reasons for wanting to still support the
> xilinx-fpgautil package.
> 
> 1) The OpenFPGALoader does not seem to support Versal PDI files yet, so it
> would be incomplete for our needs.

Correct. My point was not to claim that it was right now a drop-in
replacement, but that it was another area where Xilinx could try to
leverage existing vendor-neutral projects rather than inventing
yet-another-vendor-specific-non-standard tool like vendors like to
usually do :-)

> 2) All the Xilinx documentation talks about the fpgautil program.  And on top
> of this, I had a discussion with one of my customers regarding the use of
> Buildroot vs Yocto, and their primary reason for why they felt they "had" to
> use Yocto is because it included this fpgautil program.  This is what
> triggered me to want to add it to Buildroot.  Especially since adding it is
> quite simple to do.

Understood.

> Perhaps we could create both packages, xilinx-fpgautil and the OpenFPGALoader?

OpenFPGALoader is already packaged in Buildroot. But yes, there's no
problem with having packages for both.

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

  reply	other threads:[~2025-04-24 19:39 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 ` [Buildroot] [PATCH v1 1/2] package/fpgautil: new package Thomas Petazzoni via buildroot
2025-04-24  5:31   ` Frager, Neal via buildroot
2025-04-24 19:39     ` Thomas Petazzoni via buildroot [this message]
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=20250424213919.2e40c109@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 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.