Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Dannenberg via buildroot <buildroot@buildroot.org>
Cc: Bryan Brattlof <bb@ti.com>, Xuanhao Shi <X15000177@gmail.com>,
	Romain Naour <romain.naour@smile.fr>,
	Andreas Dannenberg <dannenberg@ti.com>,
	Etienne Carriere <etienne.carriere@foss.st.com>,
	Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [Buildroot] [PATCH RESEND v2 02/11] boot/uboot: bump to version v2024.04
Date: Mon, 6 May 2024 22:09:48 +0200	[thread overview]
Message-ID: <20240506220948.7baeea19@windsurf> (raw)
In-Reply-To: <20240506085315.lb4frefetaffps6i@dasso>

Hello Andreas,

On Mon, 6 May 2024 03:53:15 -0500
Andreas Dannenberg via buildroot <buildroot@buildroot.org> wrote:

> Similar to your other patch ("boot/optee-os: bump to release v4.2.0")
> changing the global default will affect other platforms so there's some
> risk for breakage I suppose. Why not keeping those specific changes to
> the AM62/AM64 platforms?

What Bryan did is totally fine and in line with how we handle things in
Buildroot. For packages that are close the hardware (OP-TEE, TF-A,
U-Boot, Linux), Buildroot offers:

- Using a "latest" version, which is regularly updated to the latest
  upstream version, which means that if you change Buildroot version,
  this version changes, like for any other package.

- Using a "custom" version, which is provided as an URL to a custom
  tarball, a tag/commit in a Git repo, etc. In this case, the version
  is explicitly specified in the user's .config file, and doesn't
  change when Buildroot is updated.

So, what Bryan did is update the "latest" version, and this is
perfectly correct.

All our defconfigs use a "custom" version for all of Linux, U-Boot,
OP-TEE, TF-A, specifically to ensure that despite the update in
Buildroot, our defconfig keep on using the versions that were tested by
the developer who submitted the defconfig.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-05-06 20:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 16:26 [Buildroot] [PATCH RESEND v2 00/11] update bsp binaries for TI SoCs Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 01/11] boot/optee-os: bump to release v4.2.0 Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 02/11] boot/uboot: bump to version v2024.04 Bryan Brattlof via buildroot
2024-05-06  8:53   ` Andreas Dannenberg via buildroot
2024-05-06 14:45     ` Bryan Brattlof via buildroot
2024-05-06 20:09     ` Thomas Petazzoni via buildroot [this message]
2024-05-07  6:17       ` Andreas Dannenberg via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 03/11] boot/ti-k3-r5-loader: " Bryan Brattlof via buildroot
2024-05-06 20:11   ` Thomas Petazzoni via buildroot
2024-05-08 12:04     ` Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 04/11] boot/ti-k3-boot-firmware: bump to version 09.02.00.009 Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 05/11] configs/ti_am62x_sk_defconfig: update TFA to v2.10 Bryan Brattlof via buildroot
2024-05-06 20:10   ` Thomas Petazzoni via buildroot
2024-05-08 12:05     ` Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 06/11] configs/ti_am64x_sk_defconfig: " Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 07/11] configs/ti_am62x_sk_defconfig: update U-Boot to v2024.04 Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 08/11] configs/ti_am64x_sk_defconfig: " Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 09/11] configs/ti_am62x_sk_defconfig: bump kernel to v6.8.8 Bryan Brattlof via buildroot
2024-05-06 20:11   ` Thomas Petazzoni via buildroot
2024-05-02 16:27 ` [Buildroot] [PATCH RESEND v2 10/11] configs/ti_am64x_sk_defconfig: update " Bryan Brattlof via buildroot
2024-05-02 16:27 ` [Buildroot] [PATCH RESEND v2 11/11] DEVELOPERS: add myself to TI's packages and reference boards Bryan Brattlof via buildroot
2024-05-06  8:48 ` [Buildroot] [PATCH RESEND v2 00/11] update bsp binaries for TI SoCs Andreas Dannenberg via buildroot
2024-05-06 14:42   ` Bryan Brattlof via buildroot
2024-05-06 20:07 ` Thomas Petazzoni 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=20240506220948.7baeea19@windsurf \
    --to=buildroot@buildroot.org \
    --cc=X15000177@gmail.com \
    --cc=bb@ti.com \
    --cc=dannenberg@ti.com \
    --cc=etienne.carriere@foss.st.com \
    --cc=gadiyar@ti.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