From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: michal.simek@amd.com, thomas.petazzoni@bootlin.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: bump to xilinx-v2023.1
Date: Tue, 16 May 2023 14:30:25 +0200 [thread overview]
Message-ID: <20230516143025.3efbe264@booty> (raw)
In-Reply-To: <20230516054053.22133-1-neal.frager@amd.com>
Hi Neal,
On Tue, 16 May 2023 06:40:51 +0100
Neal Frager <neal.frager@amd.com> wrote:
> This patch bumps the zynq_zc706_defconfig to xilinx-v2023.1 which includes
> the following updates:
>
> - Linux v6.1.5
> - U-Boot v2023.01
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> configs/zynq_zc706_defconfig | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/configs/zynq_zc706_defconfig b/configs/zynq_zc706_defconfig
> index 3ad8cbafe3..55e4d8ea23 100644
> --- a/configs/zynq_zc706_defconfig
> +++ b/configs/zynq_zc706_defconfig
> @@ -2,12 +2,12 @@ BR2_arm=y
> BR2_cortex_a9=y
> BR2_ARM_ENABLE_NEON=y
> BR2_ARM_ENABLE_VFP=y
> -BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_15=y
> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y
> BR2_ROOTFS_POST_BUILD_SCRIPT="board/zynq/post-build.sh"
> BR2_ROOTFS_POST_IMAGE_SCRIPT="board/zynq/post-image.sh"
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,Xilinx,linux-xlnx,xlnx_rebase_v5.15_LTS_2022.2)/xlnx_rebase_v5.15_LTS_2022.2.tar.gz"
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,Xilinx,linux-xlnx,xlnx_rebase_v6.1_LTS_2023.1)/xlnx_rebase_v6.1_LTS_2023.1.tar.gz"
Booting a mainline kernel and/or U-Boot on is still far away in the
future? :-/
--
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:[~2023-05-16 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 5:40 [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: bump to xilinx-v2023.1 Neal Frager via buildroot
2023-05-16 5:40 ` [Buildroot] [PATCH v1 2/3] configs/zynq_microzed_defconfig: " Neal Frager via buildroot
2023-05-16 14:57 ` Peter Korsgaard
2023-05-16 5:40 ` [Buildroot] [PATCH v1 3/3] configs/zynq_zed_defconfig: " Neal Frager via buildroot
2023-05-16 14:57 ` Peter Korsgaard
2023-05-16 12:30 ` Luca Ceresoli via buildroot [this message]
2023-05-16 13:01 ` [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: " Frager, Neal via buildroot
2023-05-16 14:57 ` Peter Korsgaard
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=20230516143025.3efbe264@booty \
--to=buildroot@buildroot.org \
--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 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.