forgefirm-app: bump to 37854f0 (0.1.8+git) - the park clears the ring first; cloud.lid-abort checks the kernel counters

cloud.lid-abort now proves the park with the machine's own counters
(cloud clears them at every job start, so a completed park reads back
at (0,0)); stale ring bytes replayed ahead of the park would not.
This commit is contained in:
ScottW514
2026-08-16 20:59:54 -04:00
parent 95c8cc8f54
commit 7bf8e3d4ed
2 changed files with 12 additions and 2 deletions
@@ -4,9 +4,9 @@
# because the component entry already identifies the pinned source
# (forgefirm-image-manifest.bbclass). The python3-gfhardware recipe in
# meta-glowforge-bsp pins the same repository; move both together.
SRCREV = "f7e591baa6097adaa839103a255c39e92adf8254"
SRCREV = "37854f020dfe7d2ff5541de63cc546a2eb5751d1"
# Bump PV with every SRCREV move: the hash-derived package version is not
# monotonic on its own and buildhistory QA fails the build when it sorts
# backwards.
PV = "0.1.7+git"
PV = "0.1.8+git"