From: Jan Kiszka <jan.kiszka@siemens.com>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
cip-dev@lists.cip-project.org
Subject: Re: [cip-dev][isar-cip-core][PATCH] fix: Disable bootloader interaction in case of ebg only updates
Date: Thu, 19 Feb 2026 13:50:24 +0100 [thread overview]
Message-ID: <3bd31e51-cdb7-41b7-9c7a-c65146d28cb2@siemens.com> (raw)
In-Reply-To: <20260219123726.922484-1-Quirin.Gylstorff@siemens.com>
On 19.02.26 13:36, Quirin Gylstorff wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> During an update of the efibootguard binary the boot entries should
> not be changed. Therefore disable the boot-loader state and transition
> update.
>
> This was found during testing for issue #149.
>
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
> recipes-core/images/swu/sw-description-ebg.tmpl | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-core/images/swu/sw-description-ebg.tmpl b/recipes-core/images/swu/sw-description-ebg.tmpl
> index c19157c..a63e38a 100644
> --- a/recipes-core/images/swu/sw-description-ebg.tmpl
> +++ b/recipes-core/images/swu/sw-description-ebg.tmpl
> @@ -12,6 +12,8 @@ software =
> {
> version = "${SWU_VERSION}";
> name = "${SWU_NAME}";
> + bootloader_transaction_marker = false;
> + bootloader_state_marker = false;
So we need to set both to false to avoid the SWUpdate talks to EBG, and
one does not influence the other (although there is only one state in EBG)?
Jan
> ${SWU_HW_COMPAT_NODE}
> files: (${SWU_BOOTLOADER_FILE_NODE});
> }
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2026-02-19 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 12:36 [cip-dev][isar-cip-core][PATCH] fix: Disable bootloader interaction in case of ebg only updates Quirin Gylstorff
2026-02-19 12:50 ` Jan Kiszka [this message]
2026-02-19 13:20 ` Quirin Gylstorff
2026-02-19 14:13 ` Jan Kiszka
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=3bd31e51-cdb7-41b7-9c7a-c65146d28cb2@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Quirin.Gylstorff@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/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