From 61030da69b789495bb0f0433e15eee2d83b66498 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Wed, 9 Sep 2026 14:42:00 -0400 Subject: [PATCH] Pin forgectrl on the disabled-is-idle fix A machine out of the box sat in the module's power-on state, disabled, for the whole of its first run, and every idle gate read that as busy: the setup's sensors check refused to start, settings writes answered 409, and the cooling engine held cooldown airflow from boot. forgectrl now reads disabled as idle (the state means no program in progress), with fault and underrun still busy until acknowledged and an unreadable state still failing closed. --- meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc index f3a1105..750fac9 100644 --- a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc @@ -2,5 +2,5 @@ # only SRCREV and PV here - the image manifest leaves *-pin.inc out of the # layer content hash because the component entry already identifies the # pinned source (forgefirm-image-manifest.bbclass). -SRCREV = "7e03073863c63b93da6281d318eb25dc3e822f2c" -PV = "0.1.10" +SRCREV = "439a8889ce0edb8ca8ab83f02bd3c3e0f09dd91a" +PV = "0.1.11"