Re: [docs] [PATCH 2/2] migration-guides: cover FIT_UBOOT_ENV

["Antonin Godard" <antonin.godard@bootlin.com>]

Hi Adrian,

On Thu Feb 13, 2025 at 11:04 PM CET, Adrian Freihofer via lists.yoctoproject.org wrote:
> Add a hint for users using the UBOOT_ENV variable and the
> kernel-fitimage.bbclass.
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---
>  documentation/migration-guides/migration-5.2.rst | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
> index de2ea773e55..e945e17a9df 100644
> --- a/documentation/migration-guides/migration-5.2.rst
> +++ b/documentation/migration-guides/migration-5.2.rst
> @@ -182,3 +182,7 @@ Miscellaneous changes
>  
>  -  :term:`ZSTD_COMPRESSION_LEVEL` is now a plain integer number instead of a dash-prefixed
>     command-line option (e.g. it should be set to ``3`` rather than ``-3``).
> +
> +-  :term:`UBOOT_ENV` is no longer handled by the ``kernel-fitimage.bbclass``.
> +   There is a new variable :term:`FIT_UBOOT_ENV` which is supposed to be used
> +   for adding a U-Boot script to a ``fitImage``.

I'm confused. If UBOOT_ENV is no longer used/handled, why did you document it in
your previous patch? :)

If I understand this correctly, UBOOT_ENV is only handled in the u-boot recipe,
whereas FIT_UBOOT_ENV is handled in the kernel-fitimage class? Maybe rephrase
your sentence, so it doesn't seem like UBOOT_ENV is deprecated

Thanks,
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com