runtime · what we run on top once it boots

gpu-validation

Provide an opt-in validation path for GPU prerequisites while preserving the working shell and the live display owner's control of the panel.

0 of 3 requirements here are not proven.

grounded

Optional bounded GPU validation package

grounding

docs/evidence/gpu-validation/README.md records the source-built package and optional deployment; docs/evidence/gpu-validation/initial-format-failure.txt records nonzero pixel assertion failures.

The system SHALL expose a source-built, optional GPU validation package outside the default system closure. Its board invocation MUST report each probe's completion and sampled color results, and MUST return nonzero if a required GPU operation or its explicit pixel assertion fails.

evidence in this repository
scenarios

Host build of the validation package

- WHEN an integrator builds the package with the pinned cross toolchain - THEN the build produces the validation executable without rebuilding or changing the system image.

Board validation failure

- WHEN a GPU operation, explicit completion, or asserted sample fails - THEN the executable reports the failed probe and exits nonzero without making a modeset or a framebuffer commit.

grounded

Non-invasive DRM dma-buf validation

grounding

docs/evidence/gpu-validation/cpu-timing-pass.txt records private dumb-buffer import, full CPU pixel checks, and unchanged service invocation IDs; docs/evidence/gpu-validation/README.md records the bounded DRM API review.

The GPU validation path SHALL create and export a private RGB565 DRM dumb buffer, import that dma-buf into VG-Lite, and verify the resulting buffer through its CPU mapping. It MUST NOT acquire DRM master, set a CRTC, create a framebuffer, or select a plane.

evidence in this repository
scenarios

Shell owns the live display

- WHEN the shell and its DRM owner are active during the validation - THEN the validation reports whether dumb-buffer export/import succeeds while leaving the current scanout configuration untouched.

grounded

Evidence-bounded renderer decision

grounding

docs/evidence/gpu-validation/README.md distinguishes the four measured results, process-CPU and wall-time costs, and remaining compositor/scanout gates while retaining Pixman.

The project SHALL record RGB565, alpha/color, dma-buf, and timing outcomes separately. A passing private-buffer or dma-buf probe MUST NOT be described as an accelerated compositor, display scanout, or video pipeline.

evidence in this repository
scenarios

Board evidence is incomplete

- WHEN any prerequisite probe has not run successfully on the physical board - THEN the integration recommendation identifies that missing prerequisite and does not enable a GPU renderer in the system.