Re: [PATCH 2/2] configs: qcom: ignore OsIndications for capsule-on-disk

"Ilias Apalodimas" <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <[email protected]>
Hi Balaji,

On Thu Aug 13, 2026 at 8:56 AM EEST, Balaji Selvanathan wrote:
> Qualcomm boards apply capsule-on-disk updates from U-Boot without the
> OS first setting the OsIndications EFI variable that the capsule
> runtime normally checks. EFI_IGNORE_OSINDICATIONS makes U-Boot skip
> that check so an on-disk capsule is applied at boot.
>
> Set it once in the shared qcom_defconfig so the boards that include it
> (qcm6490, qcs615, qcs8300, qcs9100) all pick it up.
>
> Signed-off-by: Balaji Selvanathan <[email protected]>
> ---
> The option defaults to y only while EFI_RT_VOLATILE_STORE is off. This
> series depends on "configs: qcom_defconfig: Enable EFI variable runtime
> storage" [1], which turns EFI_RT_VOLATILE_STORE on, so the default no
> longer applies and it has to be set explicitly. Apply that patch first.
>
> [1] https://lore.kernel.org/u-boot/[email protected]/
> ---
>  configs/qcom_defconfig | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/configs/qcom_defconfig b/configs/qcom_defconfig
> index c52f619850d..960c44b1f70 100644
> --- a/configs/qcom_defconfig
> +++ b/configs/qcom_defconfig
> @@ -9,6 +9,7 @@ CONFIG_SYS_LOAD_ADDR=0xA0000000
>  # CONFIG_EFI_HAVE_RUNTIME_RESET is not set
>  CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
>  CONFIG_EFI_CAPSULE_ON_DISK=y
> +CONFIG_EFI_IGNORE_OSINDICATIONS=y

You don't want to enable this. First of all that Kconfig option is set to 'y' by default.
Looking at our Kconfig again it should only be allowed if EFI_RT_VOLATILE_STORE is not enabled as
well since it breaks the EFI spec. That option was added years ago when we had no variable
runtime support. If your Kconfig enables EFI_RT_VOLATILE_STORE, you should writethat variable
on capsule updates.

Thanks
/Ilias
>  CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
>  CONFIG_BUTTON_CMD=y
>  CONFIG_FIT=y
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.