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: kas README is build procedure; status moves to BRINGUP and the log

Browse Source 
kas/README.md keeps the build, lockfile, pin and release procedure and a
short build-time facts list; its push/release checklist and Scarthgap
migration backlog are archived verbatim in CAMPAIGN-LOG ("Superseded
status notes"). The real-time argument (PREEMPT, why PREEMPT_RT is not
selectable or needed) joins the BRINGUP hardware facts bank next to the
ring measurements it rests on; the camera pointers go to the 0011-0013
patch headers; the image recipe's gfui-client comment drops its README
pointer.

Docs and a recipe comment only; no catalog consequence.
This commit is contained in:
ScottW514
2026-08-24 14:58:09 -04:00
parent 1e059bb90c
commit dd6f459d7b
5 changed files with 299 additions and 203 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -95,8 +95,9 @@ The control board is common to Glowforge Basic, Plus, and Pro. The 5 MP
(OV5648) camera modules are fully supported and hardware-validated. The 8 MP
(OV8856) modules found in "HD" units have a complete capture path — the kernel
patches, device tree and sensor-aware capture profile they need are all in the
build — but it has never run on an 8 MP machine, so treat it as untested; see
the camera note in [kas/README.md](kas/README.md).
build, but it has never run on an 8 MP machine, so treat it as untested; see
`docs/BRINGUP.md` (Next work, cameras) and the headers of kernel patches
0011-0013 in `meta-glowforge-bsp`.
## Safety