From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: terry.oneal@amd.com, kris.chaplin@amd.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org,
michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v4 1/2] package/versal-firmware: new package
Date: Wed, 9 Nov 2022 15:42:42 +0100 [thread overview]
Message-ID: <20221109154242.082e2709@booty> (raw)
In-Reply-To: <20221109091214.65185-1-neal.frager@amd.com>
Hi Neal,
On Wed, 9 Nov 2022 02:12:13 -0700
Neal Frager <neal.frager@amd.com> wrote:
> This patch adds support for downloading versal microblaze firmware binaries.
> These are necessary for booting Xilinx versal devices.
>
> The location of these binaries is temporary, and will soon be added to the
> Xilinx firmware repository. The temporary location is using the same free
> distribution license as the Xilinx firmware repository.
>
> Once these files are available on the Xilinx repository, this package will
> be updated to the new location.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-09 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 9:12 [Buildroot] [PATCH v4 1/2] package/versal-firmware: new package Neal Frager via buildroot
2022-11-09 9:12 ` [Buildroot] [PATCH v4 2/2] configs/versal_vck190: new defconfig Neal Frager via buildroot
2022-11-09 14:56 ` Luca Ceresoli via buildroot
2022-11-09 15:10 ` Frager, Neal via buildroot
2022-11-09 15:48 ` Luca Ceresoli via buildroot
2022-11-10 8:56 ` Frager, Neal via buildroot
2022-11-21 9:13 ` Frager, Neal via buildroot
2022-11-09 14:42 ` Luca Ceresoli via buildroot [this message]
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=20221109154242.082e2709@booty \
--to=buildroot@buildroot.org \
--cc=kris.chaplin@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=terry.oneal@amd.com \
--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.