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

BRINGUP: coda JPEG capture-buffer sizing fact (noise frames overflow the default)

Browse Source
This commit is contained in:
ScottW514
2026-08-03 15:21:20 -04:00
parent b422887ca5
commit f201f95c73
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BRINGUP.md
+6
View File
@@ -195,6 +195,12 @@ encode 7 ms**. Two hard-won facts:
bounce copy. bounce copy.
- The VPU encoder accepts 1296×972 exactly (no MCU-alignment padding - The VPU encoder accepts 1296×972 exactly (no MCU-alignment padding
needed) with quality via V4L2_CID_JPEG_COMPRESSION_QUALITY. needed) with quality via V4L2_CID_JPEG_COMPRESSION_QUALITY.
- **A CSI noise/glitch frame can out-size the coda driver's default
~2 B/px JPEG capture buffer** (kernel logs "JPEG too large for
capture buffer" + a vb2 WARN; observed once under streaming+motion
load). forgectrl requests 3 B/px and drops error-flagged dequeues as
single bad frames — hardware encode stays active; software fallback
engages only on repeated consecutive hard failures.
libjpeg remains the automatic fallback (`FORGECTRL_NO_VPU=1` forces libjpeg remains the automatic fallback (`FORGECTRL_NO_VPU=1` forces
it) and the snapshot path; `/cam/status` reports `"encoder"`. it) and the snapshot path; `/cam/status` reports `"encoder"`.