Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Maier via buildroot <buildroot@buildroot.org>
To: "Neal Frager" <neal.frager@amd.com>, <buildroot@buildroot.org>
Cc: <luca.ceresoli@bootlin.com>, <ju.o@free.fr>,
	<thomas.petazzoni@bootlin.com>, <romain.naour@smile.fr>,
	<michal.simek@amd.com>, <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v1 1/2] configs/versal: re-adding xilinx-prebuilt version
Date: Mon, 04 Nov 2024 18:18:33 +0000	[thread overview]
Message-ID: <D5DLNL4HEWDF.2UFA0CCJBT02F@collins.com> (raw)
In-Reply-To: <20241104081453.430619-1-neal.frager@amd.com>

Hi Neal,

On Mon Nov 4, 2024 at 8:14 AM UTC, Neal Frager via buildroot wrote:
> The regenerate all defconfigs commit removed the xilinx-prebuilt version from
> the versal defconfigs.  If the version is not defined in the defconfig, then
> it is not possible to change the xilinx-prebuilt default version number
> independently of the board configs.  For this reason, this patch re-adds
> the xilinx-prebuilt version to the versal defconfigs.
>
> Also, the vck190 board name has been added to the versal_vck190_defconfig in
> case the default versal board name ever changes.
>
> https://github.com/buildroot/buildroot/commit/edc0a6b1a43689fb832bc024b5997312e0770e99

This commit refers to the new "Rules for defconfigs"[1]. Those say that
defconfigs should now be formatted by `make savedefconfig`. So setting
these options manually wouldn't be consistent.

Yann had a similar problem for the Linux package which they fixed by
setting the default version to the oldest supported[2]. So we could set
the xilinx-prebuilt default to "xilinx_v2023.1" and then set it
in each config to 2024.1.

I don't know of a solution for the board name, but the default shouldn't
be changing normally.

[1] https://elinux.org/Buildroot:DeveloperDaysELCE2024#Rules_for_defconfigs
[2] https://github.com/buildroot/buildroot/commit/b2fdc16c47

Thanks,
Brandon Maier

>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
>  configs/versal_vck190_defconfig | 2 ++
>  configs/versal_vpk180_defconfig | 1 +
>  2 files changed, 3 insertions(+)
>
> diff --git a/configs/versal_vck190_defconfig b/configs/versal_vck190_defconfig
> index 697b6c5169..448195d6ac 100644
> --- a/configs/versal_vck190_defconfig
> +++ b/configs/versal_vck190_defconfig
> @@ -35,7 +35,9 @@ BR2_TARGET_UBOOT_FORMAT_DTB=y
>  BR2_TARGET_UBOOT_FORMAT_REMAKE_ELF=y
>  BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=versal-vck190-rev1.1"
>  BR2_TARGET_XILINX_PREBUILT=y
> +BR2_TARGET_XILINX_PREBUILT_VERSION="xilinx_v2024.1"
>  BR2_TARGET_XILINX_PREBUILT_VERSAL=y
> +BR2_TARGET_XILINX_PREBUILT_BOARD="vck190"
>  BR2_PACKAGE_HOST_BOOTGEN=y
>  BR2_PACKAGE_HOST_DOSFSTOOLS=y
>  BR2_PACKAGE_HOST_GENIMAGE=y
> diff --git a/configs/versal_vpk180_defconfig b/configs/versal_vpk180_defconfig
> index 9fc694a898..a4a6ed98ff 100644
> --- a/configs/versal_vpk180_defconfig
> +++ b/configs/versal_vpk180_defconfig
> @@ -35,6 +35,7 @@ BR2_TARGET_UBOOT_FORMAT_DTB=y
>  BR2_TARGET_UBOOT_FORMAT_REMAKE_ELF=y
>  BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=versal-vpk180-revA"
>  BR2_TARGET_XILINX_PREBUILT=y
> +BR2_TARGET_XILINX_PREBUILT_VERSION="xilinx_v2024.1"
>  BR2_TARGET_XILINX_PREBUILT_VERSAL=y
>  BR2_TARGET_XILINX_PREBUILT_BOARD="vpk180"
>  BR2_PACKAGE_HOST_BOOTGEN=y
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-11-04 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  8:14 [Buildroot] [PATCH v1 1/2] configs/versal: re-adding xilinx-prebuilt version Neal Frager via buildroot
2024-11-04  8:14 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp: " Neal Frager via buildroot
2024-11-04 11:12   ` Luca Ceresoli via buildroot
2024-11-04 11:12 ` [Buildroot] [PATCH v1 1/2] configs/versal: " Luca Ceresoli via buildroot
2024-11-04 18:18 ` Brandon Maier via buildroot [this message]
2024-11-05  6:35   ` 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=D5DLNL4HEWDF.2UFA0CCJBT02F@collins.com \
    --to=buildroot@buildroot.org \
    --cc=brandon.maier@collins.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 \
    --cc=yann.morin.1998@free.fr \
    /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