From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: daniel.bovensiepen@siemens.com, jan.kiszka@siemens.com,
quirin.gylstorff@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [isar-cip-core][PATCH v4 1/8] make reason for disabling wdog on arm more precise
Date: Fri, 3 Mar 2023 12:48:13 +0000 [thread overview]
Message-ID: <20230303124820.2209954-2-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20230303124820.2209954-1-felix.moessbauer@siemens.com>
This patch reworks the comment describing why the watchdog is disabled
for arm and arm64. Previously it was stated that the watchdog is armed
by u-boot, but technically it simply never was supported to have a
watchdog on these platforms when using the start-qemu script.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
conf/machine/qemu-arm.conf | 2 +-
conf/machine/qemu-arm64.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/conf/machine/qemu-arm.conf b/conf/machine/qemu-arm.conf
index aa3a6b4..d2dd81f 100644
--- a/conf/machine/qemu-arm.conf
+++ b/conf/machine/qemu-arm.conf
@@ -13,7 +13,7 @@ IMAGE_FSTYPES ?= "ext4"
USE_CIP_KERNEL_CONFIG = "1"
KERNEL_DEFCONFIG ?= "cip-kernel-config/${KERNEL_DEFCONFIG_VERSION}/arm/qemu_arm_defconfig"
-# for SWUpdate setups: watchdog is configured in U-Boot
+# watchdog is not yet supported in our QEMU executor for this platform, disable it
WDOG_TIMEOUT = "0"
PREFERRED_PROVIDER_u-boot-${MACHINE} = "u-boot-qemu-arm"
diff --git a/conf/machine/qemu-arm64.conf b/conf/machine/qemu-arm64.conf
index 7f42369..7acf107 100644
--- a/conf/machine/qemu-arm64.conf
+++ b/conf/machine/qemu-arm64.conf
@@ -12,7 +12,7 @@ IMAGE_FSTYPES ?= "ext4"
USE_CIP_KERNEL_CONFIG = "1"
KERNEL_DEFCONFIG ?= "cip-kernel-config/${KERNEL_DEFCONFIG_VERSION}/arm64/qemu_arm64_defconfig"
-# for SWUpdate setups: watchdog is configured in U-Boot
+# watchdog is not yet supported in our QEMU executor for this platform, disable it
WDOG_TIMEOUT = "0"
PREFERRED_PROVIDER_u-boot-${MACHINE} = "u-boot-qemu-arm64"
--
2.34.1
next prev parent reply other threads:[~2023-03-03 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 12:48 [isar-cip-core][PATCH v4 0/8] Add swupdate support for riscv64 Felix Moessbauer
2023-03-03 12:48 ` Felix Moessbauer [this message]
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 2/8] fix efibootguard " Felix Moessbauer
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 3/8] wic(ebg): add support " Felix Moessbauer
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 4/8] add opensbi with u-boot payload " Felix Moessbauer
2023-03-04 8:35 ` Jan Kiszka
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 5/8] enhance qemu-riscv64 machine to be testable Felix Moessbauer
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 6/8] add linux 6.1 mainline kernel Felix Moessbauer
2023-03-04 8:12 ` Jan Kiszka
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 7/8] add swupdate support for qemu-riscv64 Felix Moessbauer
2023-03-03 12:48 ` [isar-cip-core][PATCH v4 8/8] start-qemu: add support for swupdate on RISC-V Felix Moessbauer
2023-03-06 6:10 ` [isar-cip-core][PATCH v4 0/8] Add swupdate support for riscv64 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=20230303124820.2209954-2-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.bovensiepen@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@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;
as well as URLs for NNTP newsgroup(s).