From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ibai.erkiaga-elorza@amd.com, buildroot@buildroot.org,
brandon.maier@collins.com, ju.o@free.fr,
thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v1 1/5] board/xilinx: add xilinx_v2025.1 support
Date: Mon, 2 Jun 2025 17:14:33 +0200 [thread overview]
Message-ID: <20250602171433.11d81e6b@booty> (raw)
In-Reply-To: <20250602135056.404165-1-neal.frager@amd.com>
On Mon, 2 Jun 2025 14:50:52 +0100
Neal Frager <neal.frager@amd.com> wrote:
> Add hashes for xilinx_v2025.1 release.
>
> xilinx_v2025.1 release includes:
> - atf 2.12
> - linux 6.12.10
> - uboot 2025.01
>
> In addition, the xilinx_v2025.1 linux kernel release tag has a Kconfig leak
> of the CONFIG_XILINX_AIE option. This patch adds a patch that is specific to
> the Xilinx Linux 6.12.10 release which fixes the problem by moving the changes
> implemented by the CONFIG_XILINX_AIE option from the exposed uapi header file
> to the Linux internal header file.
>
> The patch has been added to the board/xilinx/linux_6.12/patches directory, so
> that it will only be applied when a user specifies they wish to build the
> xilinx_v2025.1 release or they use a defconfig that has migrated to this
> release.
>
> Since the header file that causes the issue is not yet mainline, this patch
> has been "upstreamed" to the Xilinx linux-xlnx repo via the AMD internal jira
> process.
>
> Upstream: internal AMD jira process
>
> 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
next prev parent reply other threads:[~2025-06-02 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:50 [Buildroot] [PATCH v1 1/5] board/xilinx: add xilinx_v2025.1 support Neal Frager via buildroot
2025-06-02 13:50 ` [Buildroot] [PATCH v1 2/5] configs/zynq_zc702_defconfig: bump to xilinx-v2025.1 Neal Frager via buildroot
2025-06-02 15:14 ` Luca Ceresoli via buildroot
2025-06-02 13:50 ` [Buildroot] [PATCH v1 3/5] configs/zynq_zc706_defconfig: " Neal Frager via buildroot
2025-06-02 15:15 ` Luca Ceresoli via buildroot
2025-06-02 13:50 ` [Buildroot] [PATCH v1 4/5] configs/zynq_microzed_defconfig: " Neal Frager via buildroot
2025-06-02 15:15 ` Luca Ceresoli via buildroot
2025-06-02 13:50 ` [Buildroot] [PATCH v1 5/5] configs/zynq_zed_defconfig: " Neal Frager via buildroot
2025-06-02 15:15 ` Luca Ceresoli via buildroot
2025-06-02 15:14 ` Luca Ceresoli via buildroot [this message]
[not found] ` <DAEMB4X6YG5B.1PCG33D01DPSS@collins.com>
2025-06-05 13:42 ` [Buildroot] [PATCH v1 1/5] board/xilinx: add xilinx_v2025.1 support Frager, Neal via buildroot
2025-06-09 21:36 ` Julien Olivain
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=20250602171433.11d81e6b@booty \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.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