summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKieran Bingham <kieran.bingham@ideasonboard.com>2021-08-23 20:26:14 +0100
committerKieran Bingham <kieran.bingham@ideasonboard.com>2021-08-25 21:35:03 +0100
commit6b9645d89421d0415dfa2296a6a264125a322422 (patch)
tree6c7788e1f83e0a4758f9ee7a771c2184cdbaa409
parente590ca3004b354588f45facab7989b59cf9d9309 (diff)
Documentation: application-developer: Fix reference to cam BufferWriter
The BufferWriter class has been replaced by the FileSink. Adapt the reference, to match the source code. Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
-rw-r--r--Documentation/guides/application-developer.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/guides/application-developer.rst b/Documentation/guides/application-developer.rst
index ce093cbe..11447643 100644
--- a/Documentation/guides/application-developer.rst
+++ b/Documentation/guides/application-developer.rst
@@ -466,10 +466,10 @@ and the bytes used by planes.
A completed buffer contains of course image data which can be accessed through
the per-plane dma-buf file descriptor transported by the ``FrameBuffer``
instance. An example of how to write image data to disk is available in the
-`BufferWriter class`_ which is a part of the ``cam`` utility application in the
+`FileSink class`_ which is a part of the ``cam`` utility application in the
libcamera repository.
-.. _BufferWriter class: https://git.linuxtv.org/libcamera.git/tree/src/cam/buffer_writer.cpp
+.. _FileSink class: https://git.linuxtv.org/libcamera.git/tree/src/cam/file_sink.cpp
With the handling of this request completed, it is possible to re-use the
buffers by adding them to a new ``Request`` instance with their matching