All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 5/6] swupdate: Drop u-boot-script from EFI Boot Guard images
Date: Wed, 31 Aug 2022 09:31:20 +0200	[thread overview]
Message-ID: <d552cf4cff74bb9c3b1948c70643797daa18ca4c.1661931081.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1661931081.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

This package is used for legacy distro boot via U-Boot, but that is not
needed/used when UEFI is activated. Make sure the package is not
installed, even if a machine config pulled it in.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 kas/opt/ebg-swu.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kas/opt/ebg-swu.yml b/kas/opt/ebg-swu.yml
index e0bbe2e..8b3ffec 100644
--- a/kas/opt/ebg-swu.yml
+++ b/kas/opt/ebg-swu.yml
@@ -18,6 +18,7 @@ local_conf_header:
   ebg_swu_bootloader: |
     WKS_FILE ?= "${MACHINE}-efibootguard.wks.in"
     SWUPDATE_BOOTLOADER = "efibootguard"
+    IMAGE_INSTALL_remove = "u-boot-script"
   ebg_swu_image_options: |
     CIP_IMAGE_OPTIONS_append = " efibootguard.inc image-uuid.inc"
   initramfs: |
-- 
2.35.3



  parent reply	other threads:[~2022-08-31  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  7:31 [isar-cip-core][PATCH 0/6] Enable SWUpdate support for bbb, update Isar Jan Kiszka
2022-08-31  7:31 ` [isar-cip-core][PATCH 1/6] swupdate: Use cpio from buildchroot Jan Kiszka
2022-08-31  7:31 ` [isar-cip-core][PATCH 2/6] Update Isar revision Jan Kiszka
2022-08-31  7:31 ` [isar-cip-core][PATCH 3/6] linux-cip: Update cip-kernel-config revision Jan Kiszka
2022-08-31  7:31 ` [isar-cip-core][PATCH 4/6] u-boot-bbb: Switch BeagleBone Black to self-built U-Boot Jan Kiszka
2022-08-31  7:31 ` Jan Kiszka [this message]
2022-08-31  7:31 ` [isar-cip-core][PATCH 6/6] Enable BeagleBone Black images with A/B SWUpdate support 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=d552cf4cff74bb9c3b1948c70643797daa18ca4c.1661931081.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.