vh/forgefirm
1
0
Fork 0
mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-27 16:51:12 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs: build p32, image 20260903011655, the campaign's image

Browse Source 
BRINGUP item 9: items 10 and 11 are on image 20260903011655; owed is the
flash, the fresh-boot baseline, and the full campaign, then the push and
the pin bumps. CAMPAIGN-LOG: the p32 build and its checks.
This commit is contained in:
ScottW514
2026-09-02 21:22:35 -04:00
parent 92c69f23fa
commit cf7490de78
2 changed files with 20 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BRINGUP.md
+1 -1
View File
@@ -1386,7 +1386,7 @@ feature requests, enhancements) will eventually be tracked as GitHub issues.
change, and is not the image the campaign runs on: the campaign waits change, and is not the image the campaign runs on: the campaign waits
until every audit finding, the deferred ones included, is on one image until every audit finding, the deferred ones included, is on one image
(the operator's rule). That batch is done (items 10 and 11) and is on (the operator's rule). That batch is done (items 10 and 11) and is on
the local image 20260903003213 (release and dev; the module built from the local image 20260903011655 (release and dev; the module built from
its local commit at 0.0.3, the kernel from the edited patches, its local commit at 0.0.3, the kernel from the edited patches,
everything else from the pushed pins), which is the campaign's image. everything else from the pushed pins), which is the campaign's image.
Owed now: flash the dev image, take a fresh-boot baseline, run the full Owed now: flash the dev image, take a fresh-boot baseline, run the full
docs/CAMPAIGN-LOG.md
+19
View File
@@ -7562,6 +7562,25 @@ the coolant-reading tests. Rare excursions of 10 to 20 counts appear in
every regime at a few samples per hundred and are a separate matter the every regime at a few samples per hundred and are a separate matter the
diagnostic's interquartile means already drop. diagnostic's interquartile means already drop.
## 2026-09-03: build p32, the campaign's image with item 10 redone
Build p32 replaces p31 as the campaign's image: the same batch with the
PIC settle in place of the sleep-based gap, the module from its local
commit at 0.0.3 (pinned for this build only, its mirror primed), the
kernel from the edited patches, everything else from the pushed pins.
Fetch-verify green; the kernel and the module cleaned together; both
images built clean, release and dev `20260903011655`. The checks: the kernel and
the module both name `6.12.20-fslc-fslc-g649f0f50c451`; the dev manifest records the module at its
commit and 0.0.3 and every other component at its pushed pin; the module
in the dev image carries the inhibit, the mailbox and the `pic_settle_us`
strings, with a vermagic that matches the kernel; the patched tree carries
the dmaengine claim and the word_delay source; the suite in the image
carries the new drills; `WATCHDOG_SYSFS`, `IMX2_WDT` and `STRICT_DEVMEM`
are set; no gfui-client; `nofail` factory slots; no mmap or ctypes in the
release image; no QA warnings. Owed: the operator flashes the dev image,
takes a fresh-boot baseline, and runs the full campaign; then the push in
CI order and the pin bumps.
## Reference notes ## Reference notes
### Head-IRQ source validation — the beam-emission hypothesis ### Head-IRQ source validation — the beam-emission hypothesis