All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ibai.erkiaga-elorza@amd.com, arnout@mind.be,
	brandon.maier@collins.com, ju.o@free.fr,
	thomas.petazzoni@bootlin.com, buildroot@buildroot.org,
	romain.naour@smile.fr, michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v4 1/3] boot/xilinx-embeddedsw: rename toolchain vendor to buildroot
Date: Tue, 8 Apr 2025 08:35:05 +0200	[thread overview]
Message-ID: <20250408083505.0a7ecfda@booty> (raw)
In-Reply-To: <20250327111645.1430919-1-neal.frager@amd.com>

Hi Neal,

On Thu, 27 Mar 2025 11:16:43 +0000
Neal Frager <neal.frager@amd.com> wrote:

> This patch renames the bare-metal toolchain vendor used by the
> xilinx-embeddedsw package from Xilinx to Buildroot to be consistent with all
> other toolchains built by Buildroot.
> 
> To build the Microblaze applications available with the xilinx-embeddedsw
> package, the following config is now needed:
> 
> BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH="microblazeel-buildroot-elf"
> 
> This change keeps backwards compatibility for users already using the
> following architecture tuple:
> 
> BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH="microblazeel-xilinx-elf"
> 
> Either vendor name is now valid, but the documentation will describe using
> the Buildroot vendor name.
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

I don't have a strong opinion about this series. Definitely the
"buildroot" vendor name is more appropriate than "xilinx", and the
patches look clean enough, but I'll let the maintainers decide whether
it's worth the extra effort.

If this is accepted, however, I think we should remove the "xilinx"
vendor support after 1y~1.5y and not carry the maintenance burden
indefinitely. Do you think this can be handled by Config.in.legacy, so
in the transition phase users of the old tuple are notified?

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

  parent reply	other threads:[~2025-04-08  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 11:16 [Buildroot] [PATCH v4 1/3] boot/xilinx-embeddedsw: rename toolchain vendor to buildroot Neal Frager via buildroot
2025-03-27 11:16 ` [Buildroot] [PATCH v4 2/3] toolchain/toolchain-bare-metal-buildroot: rename example " Neal Frager via buildroot
2025-03-27 11:16 ` [Buildroot] [PATCH v4 3/3] configs/versal|zynqmp: migrate to microblazeel-buildroot-elf tuple Neal Frager via buildroot
2025-04-08  6:35 ` Luca Ceresoli via buildroot [this message]
2025-04-08  6:40   ` [Buildroot] [PATCH v4 1/3] boot/xilinx-embeddedsw: rename toolchain vendor to buildroot Frager, Neal via buildroot
2025-04-08 10:09     ` Luca Ceresoli via buildroot
2025-04-08 12:19       ` 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=20250408083505.0a7ecfda@booty \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --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 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.