From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ibai.erkiaga-elorza@amd.com, brandon.maier@collins.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org,
michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: bump to xilinx-v2024.1
Date: Mon, 3 Jun 2024 18:19:09 +0200 [thread overview]
Message-ID: <20240603181909.50291720@booty> (raw)
In-Reply-To: <20240603115212.184529-1-neal.frager@amd.com>
Hello Neal,
On Mon, 3 Jun 2024 12:52:10 +0100
Neal Frager <neal.frager@amd.com> wrote:
> This patch bumps the zynqmp_zcu102_defconfig to xilinx-v2024.1 which includes
> the following updates:
>
> - Linux v6.6.10
> - U-Boot v2024.01
> - ATF v2.10
> - PMUFW xilinx-v2024.1
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> -BR2_GLOBAL_PATCH_DIR="board/zynqmp/patches"
Along with the Kria KV260 + KR260 series you sent in the same day
today, this patch dir will become used only by KD260. Do you have such
an upgrade for KD260 in your pipeline?
If you do, then it's fine, we can keep this directory until then.
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:[~2024-06-03 16:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 11:52 [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: bump to xilinx-v2024.1 Neal Frager via buildroot
2024-06-03 11:52 ` [Buildroot] [PATCH v1 2/3] configs/zynqmp_zcu104_defconfig: " Neal Frager via buildroot
2024-06-03 16:19 ` Luca Ceresoli via buildroot
2024-06-03 11:52 ` [Buildroot] [PATCH v1 3/3] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2024-06-03 16:19 ` Luca Ceresoli via buildroot
2024-06-03 16:19 ` Luca Ceresoli via buildroot [this message]
2024-06-03 17:32 ` [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: " Frager, Neal via buildroot
2024-06-06 13:59 ` Frager, Neal via buildroot
2024-06-06 15:25 ` Yann E. MORIN
2024-06-06 15:56 ` Frager, Neal via buildroot
2024-06-06 16:02 ` Frager, Neal via buildroot
2024-06-06 16:15 ` Yann E. MORIN
2024-06-06 18:09 ` Arnout Vandecappelle via buildroot
2024-06-06 18:34 ` [Buildroot] [External] " Maier, Brandon L Collins via buildroot
2024-06-07 6:34 ` Frager, Neal via buildroot
2024-06-11 15:08 ` [Buildroot] " Luca Ceresoli via buildroot
2024-06-11 18:06 ` 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=20240603181909.50291720@booty \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox