All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Subject: [cip-dev][isar-cip-core][PATCH v3 4/4] doc/README.swupdate.md: Add documentation for hardware compatibility
Date: Fri, 16 Feb 2024 16:30:05 +0100	[thread overview]
Message-ID: <20240216153024.260416-5-Quirin.Gylstorff@siemens.com> (raw)
In-Reply-To: <20240216153024.260416-1-Quirin.Gylstorff@siemens.com>

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
 doc/README.swupdate.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md
index 1c94699..0f179c4 100644
--- a/doc/README.swupdate.md
+++ b/doc/README.swupdate.md
@@ -21,6 +21,16 @@ window is still possible.
 If the variable `SWU_EBG_UPDATE` is set to `"1"` the update is also stored in
 the `*.swu` file.
 
+## SWUpdate Hardware compatibility
+
+The variable `SWU_HW_COMPAT` contains a space separate list of
+compatible hardware revisions.
+SWUpdate checks the compatibility against `/etc/hwrevision`, see
+[hardware-compatibility in the SWUpdate documentation.](https://sbabic.github.io/swupdate/sw-description.html#hardware-compatibility)
+
+For testing purpose the content of `/etc/hwrevision` can be set with
+the variable `MACHINE_HW_VERSION`.
+
 # Building and testing the CIP Core image
 
 Set up `kas-container` as described in the [top-level README](../README.md).
-- 
2.43.0



  parent reply	other threads:[~2024-02-16 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 15:30 [cip-dev][isar-cip-core][PATCH v3 0/4] Reduce difference to debian Quirin Gylstorff
2024-02-16 15:30 ` [cip-dev][isar-cip-core][PATCH v3 1/4] swupdate-config: move swupdate.cfg from customizations to own recipe Quirin Gylstorff
2024-02-16 15:30 ` [cip-dev][isar-cip-core][PATCH v3 2/4] swupdate: set SWU_HW_COMPAT Quirin Gylstorff
2024-02-16 15:30 ` [cip-dev][isar-cip-core][PATCH v3 3/4] swupdate.bbclass: weak default assignment for SWU_HW_COMPAT Quirin Gylstorff
2024-02-16 15:30 ` Quirin Gylstorff [this message]
2024-02-16 15:39   ` [cip-dev][isar-cip-core][PATCH v3 4/4] doc/README.swupdate.md: Add documentation for hardware compatibility Jan Kiszka
2024-02-16 16:50     ` Gylstorff Quirin

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=20240216153024.260416-5-Quirin.Gylstorff@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@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 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.