From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <reatmon@ti.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v2] uboot: Deprecate legacy UBOOT_CONFIG flow
Date: Wed, 28 Jan 2026 11:30:23 +0100 [thread overview]
Message-ID: <DG05IA8FS2FN.2EVV3XH9J40UG@bootlin.com> (raw)
In-Reply-To: <20260127223433.23270-1-reatmon@ti.com>
Hi,
On Tue Jan 27, 2026 at 11:34 PM CET, Ryan Eatmon via lists.openembedded.org wrote:
> Mark the legacy flow for settings the UBOOT_CONFIG options in a comma
> separated list. This code will still work through wrynose, but will be
> removed once wrynose is released.
>
> Add warnings to point people in the right direction for fixing their
> configs:
>
> WARNING: Legacy use of UBOOT_CONFIG[foo] = "foo_config,foo_image,foo_binary" is deprecated. Please move to using UBOOT_CONFIG_* variables:
> WARNING: UBOOT_CONFIG[foo] = "foo_config"
> WARNING: UBOOT_CONFIG_IMAGE_FSTYPES[foo] = "foo_image"
> WARNING: UBOOT_CONFIG_BINARY[foo] = "foo_binary"
> WARNING: Legacy use of UBOOT_CONFIG[bar] = "bar_config,bar_image" is deprecated. Please move to using UBOOT_CONFIG_* variables:
> WARNING: UBOOT_CONFIG[bar] = "bar_config"
> WARNING: UBOOT_CONFIG_IMAGE_FSTYPES[bar] = "bar_image"
> WARNING: Legacy use of UBOOT_CONFIG[bing] = "bing_config,,bing_binary" is deprecated. Please move to using UBOOT_CONFIG_* variables:
> WARNING: UBOOT_CONFIG[bing] = "bing_config"
> WARNING: UBOOT_CONFIG_BINARY[bing] = "bing_binary"
Will you please add a note for that in
https://docs.yoctoproject.org/dev/migration-guides/migration-6.0.html?
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> v2: Fix spelling error in comment.
>
> meta/classes-recipe/uboot-config.bbclass | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/meta/classes-recipe/uboot-config.bbclass b/meta/classes-recipe/uboot-config.bbclass
> index 823a66157a..112fea2de4 100644
> --- a/meta/classes-recipe/uboot-config.bbclass
> +++ b/meta/classes-recipe/uboot-config.bbclass
> @@ -27,6 +27,9 @@
> # deemed to be limiting in terms of expanding support to more and more knobs
> # that might need to be turned to customize a config build.
> #
> +# NOTE: Suport for this legacy flow is now deprecated and will be removed from
Typo: Suport
> +# master after the wrynose LTS release.
> +#
> # UBOOT_MACHINE = ""
> # UBOOT_CONFIG ??= <default>
> # UBOOT_CONFIG[foo] = "foo_config,images,binary"
> @@ -181,14 +184,19 @@ python () {
> if config == f:
> found = True
> items = v.split(',')
> + if items[0] and len(items) > 1:
> + bb.warn('Legacy use of UBOOT_CONFIG[%s] = "%s" is deprecated. Please move to using UBOOT_CONFIG_* variables:' % (f, v))
Add a link to the migration guide here?
I'm anticipating, but that will be
https://docs.yoctoproject.org/migration-guides/migration-6.0.html
(without the /dev, but when the release will be out the link will be valid)
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-01-28 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 22:34 [OE-core][PATCH v2] uboot: Deprecate legacy UBOOT_CONFIG flow Ryan Eatmon
2026-01-28 10:30 ` Antonin Godard [this message]
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=DG05IA8FS2FN.2EVV3XH9J40UG@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=reatmon@ti.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