From aade93f503a313217dcaf117b1ba43be473bfe3f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?N=C3=ADcolas=20F=2E=20R=2E=20A=2E=20Prado?= Date: Wed, 17 Mar 2021 16:28:31 -0300 Subject: Documentation: guides: pipeline-handler: Fix capture flag usage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The number of frames passed to the -C flag of cam should come right after it, without a space, otherwise the value is discarded. The log below already showed the correct usage, but the command in the code-block was wrong, so fix it. Signed-off-by: Nícolas F. R. A. Prado Reviewed-by: Sebastian Fricke Reviewed-by: Laurent Pinchart Signed-off-by: Laurent Pinchart --- Documentation/guides/pipeline-handler.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Documentation') diff --git a/Documentation/guides/pipeline-handler.rst b/Documentation/guides/pipeline-handler.rst index 288f572c..3047e006 100644 --- a/Documentation/guides/pipeline-handler.rst +++ b/Documentation/guides/pipeline-handler.rst @@ -1434,7 +1434,7 @@ capture through the pipeline through both of the cam and qcam utilities. .. code-block:: shell ninja -C build - ./build/src/cam/cam -c vivid -C 5 + ./build/src/cam/cam -c vivid -C5 To test that the pipeline handler can detect a device, and capture input. -- cgit v1.2.1