From 93947027ff337611c8ee0ae2cb7908937a23f00e Mon Sep 17 00:00:00 2001 From: Zygmunt Krynicki <zygmunt.krynicki@huawei.com> Date: Wed, 16 Feb 2022 12:15:20 +0100 Subject: [PATCH] rauc: adjust compatible string for Raspberry Pi 4 In retrospective I think I've misunderstood the compatible string to mean "what is the image we expect" vs "what is the hardware we expect". By setting the compatible string to describe the hardware, we get the ability to restrict images for genuinely incompatible hardware without locking down ability to move to other software images. Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com> --- .../recipes-core/rauc/files/raspberrypi4/system.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oniro-core/recipes-core/rauc/files/raspberrypi4/system.conf b/meta-oniro-core/recipes-core/rauc/files/raspberrypi4/system.conf index 3e733553..86fb8fa6 100644 --- a/meta-oniro-core/recipes-core/rauc/files/raspberrypi4/system.conf +++ b/meta-oniro-core/recipes-core/rauc/files/raspberrypi4/system.conf @@ -3,7 +3,7 @@ # SPDX-License-Identifier: Apache-2.0 [system] -compatible=Oniro Reference Image for Raspberry Pi 4 +compatible=Raspberry Pi 4 # Use the custom boot loader backend. The handler program is set in the # [handlers] section below. This loops in SystemOTA into the update process and # delegates slot status and slot active flag responsibilities to it. -- GitLab