From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Arjunan, Srinu (FT FDS CES LX PBU 2)" <srinuvasan.a@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "K L,
Shivaschandra (FT FDS CES LX PBU 1)"
<shivaschandra.k-l@siemens.com>
Subject: Re: [PATCH] rootfs: run kernel-install after update-initramfs
Date: Fri, 17 Apr 2026 09:27:33 +0200 [thread overview]
Message-ID: <9eca3e44-bb16-4904-9aed-e71fecf2b6e6@siemens.com> (raw)
In-Reply-To: <PUZPR06MB57475ADF58813411880F623488202@PUZPR06MB5747.apcprd06.prod.outlook.com>
On 17.04.26 06:55, Arjunan, Srinu (FT FDS CES LX PBU 2) wrote:
>> Err, where/how do you define "primary" and "secondary" EFI bootloaders?
>> Note that EBG is isar-cip-core, and there we definitely do not have such a concept. Can you
>> elaborate what you want to achieve?
>
> In our downstream project, we use a combination of EBG and systemd-boot, along with UKI (ukify) images.
>
> EBG acts as the primary bootloader to enable watchdog support during early boot,
> while systemd-boot is used as a secondary bootloader to select the appropriate Btrfs snapshot along with its corresponding UKI image.
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commits/wip/abvar?ref_type=heads
Please contribute/continue so that we can find a standard and robust
version is CIP. Last version I saw internally was just broken.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/9eca3e44-bb16-4904-9aed-e71fecf2b6e6%40siemens.com.
next prev parent reply other threads:[~2026-04-17 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 12:55 srinuvasan.a via isar-users
2026-04-15 13:05 ` 'Jan Kiszka' via isar-users
2026-04-16 12:16 ` Srinuvasan Arjunan
2026-04-20 9:33 ` Srinuvasan Arjunan
2026-04-17 4:55 ` 'Arjunan, Srinu' via isar-users
2026-04-17 7:27 ` 'Jan Kiszka' via isar-users [this message]
2026-04-17 7:35 ` 'Quirin Gylstorff' via isar-users
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=9eca3e44-bb16-4904-9aed-e71fecf2b6e6@siemens.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=shivaschandra.k-l@siemens.com \
--cc=srinuvasan.a@siemens.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