Camera RDI capture: dynamic media graph config + robust yavta fallbacks #198
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
[run.sh](http://run.sh/)
fully dynamic: parse media graph at runtime (no hardcoded nodes), per-pipeline capture, multi-format support, PASS/FAIL/SKIP summary +.res
.[functestlib.sh](http://functestlib.sh/)
: keep MBUS on pads (strip trailingP
), PIXEL fmt on video node, update onlyWxH
, and link reliably.capture
↔capture-mplane
), packed↔unpacked fallback (SRGGB10
↔SRGGB10P
), and clear exit codes.Why
Manual
media-ctl
(pads=SRGGB10
) +yavta
(video=SRGGB10P
) succeeded while the script pushed*P
to pads and failed. This fixes pad/video fmt split, quoting, and timing/race sensitivities.How to debug
PRINT_PLANNED=1 ./[run.sh](http://run.sh/)
(logs the exactmedia-ctl
/yavta
sequence).ALLOW_SENSOR_CTRL=1
to enable pre/postyavta --no-query -w ...
.Usage
./[run.sh](http://run.sh/) --format SRGGB10P --frames 10
media-ctl -r
.Compatibility / Notes