All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Q. Gylstorff" <Quirin.Gylstorff@siemens.com>,
	<cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev][isar-cip-core][PATCH] Make read-only rootfs a inc file
Date: Fri, 17 Dec 2021 15:49:48 +0100	[thread overview]
Message-ID: <12bda5b2-4bc4-2a93-ae1a-9d7fd5e42cdd@siemens.com> (raw)
In-Reply-To: <6066ea89-53fb-98b6-9e4f-7e27486b6d97@siemens.com>

On 17.12.21 15:19, Jan Kiszka wrote:
> On 17.12.21 14:50, Q. Gylstorff wrote:
>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>
>> This allows downstream recipes to include the kas option
>> and use the include as base without recreating some parts
>> of the recipes.
>>
>> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>> ---
>>  kas/opt/ebg-secure-boot-snakeoil.yml                  |  4 ++--
>>  recipes-core/images/cip-core-image.bb                 |  3 ++-
>>  .../{cip-core-image-read-only.bb => read-only.inc}    | 11 ++++++++++-
>>  .../initramfs-verity-hook_0.1.bb                      |  2 +-
>>  start-qemu.sh                                         |  3 ---
>>  5 files changed, 15 insertions(+), 8 deletions(-)
>>  rename recipes-core/images/{cip-core-image-read-only.bb => read-only.inc} (78%)
>>
>> diff --git a/kas/opt/ebg-secure-boot-snakeoil.yml b/kas/opt/ebg-secure-boot-snakeoil.yml
>> index 1cfbacc..807b0d7 100644
>> --- a/kas/opt/ebg-secure-boot-snakeoil.yml
>> +++ b/kas/opt/ebg-secure-boot-snakeoil.yml
>> @@ -14,16 +14,16 @@ header:
>>    includes:
>>     - kas/opt/ebg-secure-boot-base.yml
>>  
>> -target: cip-core-image-read-only
>>  
>>  local_conf_header:
>> +  image-options: |
>> +    CIP_IMAGE_OPTIONS += "read-only.inc"
>>    swupdate: |
>>      IMAGE_INSTALL_append = " swupdate"
>>      IMAGE_INSTALL_append = " swupdate-handler-roundrobin"
>>  
>>    verity-img: |
>>      SECURE_IMAGE_FSTYPE = "squashfs"
>> -    VERITY_IMAGE_RECIPE = "cip-core-image-read-only"
>>      IMAGE_TYPE = "secure-swupdate-img"
>>      WKS_FILE = "${MACHINE}-efibootguard-secureboot.wks.in"
>>  
>> diff --git a/recipes-core/images/cip-core-image.bb b/recipes-core/images/cip-core-image.bb
>> index 2cecde3..9bf21ff 100644
>> --- a/recipes-core/images/cip-core-image.bb
>> +++ b/recipes-core/images/cip-core-image.bb
>> @@ -18,4 +18,5 @@ IMAGE_INSTALL += "customizations"
>>  
>>  # for swupdate
>>  SWU_DESCRIPTION ??= "swupdate"
>> -include ${SWU_DESCRIPTION}.inc
>> +CIP_IMAGE_OPTIONS ?= "${SWU_DESCRIPTION}.inc"
>> +include ${CIP_IMAGE_OPTIONS}
>> diff --git a/recipes-core/images/cip-core-image-read-only.bb b/recipes-core/images/read-only.inc
>> similarity index 78%
>> rename from recipes-core/images/cip-core-image-read-only.bb
>> rename to recipes-core/images/read-only.inc
>> index 79cd6bf..604caa0 100644
>> --- a/recipes-core/images/cip-core-image-read-only.bb
>> +++ b/recipes-core/images/read-only.inc
>> @@ -1,4 +1,13 @@
>> -require cip-core-image.bb
>> +#
>> +# CIP Core, generic profile
>> +#
>> +# Copyright (c) Siemens AG, 2021
>> +#
>> +# Authors:
>> +#  Quirin Gylstorff <Quriin.Gylstorff@siemens.com>
>> +#
>> +# SPDX-License-Identifier: MIT
>> +#
>>  
>>  SQUASHFS_EXCLUDE_DIRS += "home var"
>>  
>> diff --git a/recipes-initramfs/initramfs-verity-hook/initramfs-verity-hook_0.1.bb b/recipes-initramfs/initramfs-verity-hook/initramfs-verity-hook_0.1.bb
>> index a7fbf5a..f0d2d68 100644
>> --- a/recipes-initramfs/initramfs-verity-hook/initramfs-verity-hook_0.1.bb
>> +++ b/recipes-initramfs/initramfs-verity-hook/initramfs-verity-hook_0.1.bb
>> @@ -24,7 +24,7 @@ TEMPLATE_VARS += "VERITY_BEHAVIOR_ON_CORRUPTION"
>>  
>>  DEBIAN_DEPENDS = "initramfs-tools, cryptsetup"
>>  
>> -VERITY_IMAGE_RECIPE ?= "cip-core-image-read-only"
>> +VERITY_IMAGE_RECIPE ?= "cip-core-image"
>>  
>>  VERITY_ENV_FILE = "${DEPLOY_DIR_IMAGE}/${VERITY_IMAGE_RECIPE}-${DISTRO}-${MACHINE}.verity.env"
>>  
>> diff --git a/start-qemu.sh b/start-qemu.sh
>> index 4ab3861..24df490 100755
>> --- a/start-qemu.sh
>> +++ b/start-qemu.sh
>> @@ -45,9 +45,6 @@ if [ -z "${TARGET_IMAGE}" ];then
>>  	if grep -s -q "IMAGE_SECURITY: true" .config.yaml; then
>>  		TARGET_IMAGE="cip-core-image-security"
>>  	fi
>> -	if [ -n "${SECURE_BOOT}" ]; then
>> -		TARGET_IMAGE="cip-core-image-read-only"
>> -	fi
>>  fi
>>  
>>  case "$1" in
>>
> 
> Thanks, applied to next.
> 

We have a regression, you already saw it. Dropping this, waiting for v2.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-12-17 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 13:50 [cip-dev][isar-cip-core][PATCH] Make read-only rootfs a inc file Q. Gylstorff
2021-12-17 13:53 ` Jan Kiszka
2021-12-17 14:08   ` Gylstorff Quirin
2021-12-17 14:19 ` Jan Kiszka
2021-12-17 14:49   ` Jan Kiszka [this message]
2021-12-17 14:51 ` 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=12bda5b2-4bc4-2a93-ae1a-9d7fd5e42cdd@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 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.