Searched +full:frame +full:- +full:buffer (Results 1 – 25 of 165) sorted by relevance
1234567
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
8 .. _compressed-formats:
18 .. flat-table:: Compressed Image Formats
19 :header-rows: 1
20 :stub-columns: 0
23 * - Identifier
24 - Code
25 - Details
26 * .. _V4L2-PIX-FMT-JPEG:
28 - ``V4L2_PIX_FMT_JPEG``
[all …]
|
| D | dev-stateless-decoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Memory-to-memory Stateless Video Decoder Interface
10 between processed frames. This means that each frame is decoded independently
18 This section describes how user-space ("the client") is expected to communicate
24 Stateless decoders make use of the :ref:`media-request-api`. A stateless
30 frame may be the result of several decode requests (for instance, H.264 streams
31 with multiple slices per frame). Decoders that support such formats must also
45 codec-specific capability controls (such as H.264 profiles) to the set
55 formats may depend on the value of some codec-dependent controls.
110 frame buffer resolution for the decoded frames.
[all …]
|
| D | func-read.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-read:
13 v4l2-read - Read from a V4L2 device
18 .. code-block:: c
31 Buffer to be filled
40 descriptor ``fd`` into the buffer starting at ``buf``. The layout of the
41 data in the buffer is discussed in the respective device interface
45 :c:func:`read()` call will provide at most one frame (two fields)
61 :c:func:`read()` never returns a "snapshot" of a buffer being filled.
62 Using a single buffer the driver will stop capturing when the
[all …]
|
| D | dev-encoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
6 Memory-to-Memory Stateful Video Encoder Interface
12 further post-processing by the client.
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
35 used interchangeably with multi-planar API, unless specified otherwise,
41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
42 queue containing data that resulted from processing buffer A.
47 Refer to :ref:`decoder-glossary`.
52 .. kernel-render:: DOT
65 qi -> Initialization [ label = "open()" ];
[all …]
|
| D | buffer.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 A buffer contains data exchanged by application and driver using one of
11 the Streaming I/O methods. In the multi-planar API, the data is held in
12 planes, while the buffer structure acts as a container for the planes.
14 copied. These pointers, together with meta-information like timestamps
18 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,
19 some plane-specific members of struct :c:type:`v4l2_buffer`,
25 part of the frame and with which clock the timestamp is taken. Please
27 ``V4L2_BUF_FLAG_TSTAMP_SRC_MASK`` in :ref:`buffer-flags`. These flags
33 mem-to-mem devices is an exception to the rule: the timestamp source
[all …]
|
| D | dev-overlay.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
11 Video overlay devices have the ability to genlock (TV-)video into the
12 (VGA-)video signal of a graphics card, or to store captured images
30 frame rate of the video standard is not guaranteed. Frames may be
62 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
72 frame buffer parameters, namely the address and size of the frame buffer
79 superuser can change the frame buffer address and size. Users are not
85 card. In this case the frame buffer is not modified by the video device,
86 and the frame buffer address and pixel format are not needed by the
93 1. Chroma-keying displays the overlaid image only where pixels in the
[all …]
|
| D | dev-decoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Memory-to-Memory Stateful Video Decoder Interface
9 A stateful video decoder takes complete chunks of the bytestream (e.g. Annex-B
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
35 used interchangeably with multi-planar API, unless specified otherwise,
41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
42 queue containing data that resulted from processing buffer A.
44 .. _decoder-glossary:
50 the destination buffer queue; for decoders, the queue of buffers containing
79 Good at sub-partitioning the picture into variable sized structures.
[all …]
|
| D | planar-apis.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _planar-apis:
6 Single- and multi-planar APIs
9 Some devices require data for each input or output video frame to be
10 placed in discontiguous memory buffers. In such cases, one video frame
12 per "plane". A plane is a sub-buffer of the current frame. For examples
15 Initially, V4L2 API did not support multi-planar buffers and a set of
17 constitute what is being referred to as the "multi-planar API".
20 depending on whether single- or multi-planar API is being used. An
22 corresponding buffer type to its ioctl calls. Multi-planar versions of
[all …]
|
| D | ext-ctrls-codec.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _codec-controls:
24 .. _mpeg-control-id:
27 -----------------
35 .. _v4l2-mpeg-stream-type:
40 enum v4l2_mpeg_stream_type -
41 The MPEG-1, -2 or -4 output stream type. One cannot assume anything
48 .. flat-table::
49 :header-rows: 0
50 :stub-columns: 0
[all …]
|
| D | func-write.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-write:
13 v4l2-write - Write to a V4L2 device
18 .. code-block:: c
31 Buffer with data to be written
34 Number of bytes at the buffer
40 referenced by the file descriptor ``fd`` from the buffer starting at
46 video frame, raw VBI image, sliced VPS or WSS data is displayed again.
54 nothing was written. On error, -1 is returned, and the ``errno``
56 the beginning of a new frame. Possible error codes are:
[all …]
|
| /Documentation/driver-api/ |
| D | frame-buffer.rst | 1 Frame Buffer Library
4 The frame buffer drivers depend heavily on four data structures. These
20 otherwise. A good example of this is the start of the frame buffer
21 memory. This "locks" the address of the frame buffer memory, so that it
31 Frame Buffer Memory
32 -------------------
34 .. kernel-doc:: drivers/video/fbdev/core/fbmem.c
37 Frame Buffer Colormap
38 ---------------------
40 .. kernel-doc:: drivers/video/fbdev/core/fbcmap.c
[all …]
|
| /Documentation/fb/ |
| D | framebuffer.rst | 2 The Frame Buffer Device
9 ---------------
11 The frame buffer device provides an abstraction for the graphics hardware. It
12 represents the frame buffer of some video hardware and allows application
13 software to access the graphics hardware through a well-defined interface, so
14 the software doesn't need to know anything about the low-level (hardware
22 --------------------------
24 From the user's point of view, the frame buffer device looks just like any
26 specifies the frame buffer number.
31 0 = /dev/fb0 First frame buffer
[all …]
|
| D | internals.rst | 2 Frame Buffer device internals
5 This is a first start for some documentation about frame buffer device
10 - Geert Uytterhoeven <geert@linux-m68k.org>, 21 July 1998
11 - James Simmons <jsimmons@user.sf.net>, Nov 26 2002
13 --------------------------------------------------------------------------------
15 Structures used by the frame buffer device API
18 The following structures play a role in the game of frame buffer devices. They
23 - struct fb_fix_screeninfo
25 Device independent unchangeable information about a frame buffer device and
29 - struct fb_var_screeninfo
[all …]
|
| D | modedb.rst | 6 Currently all frame buffer device drivers have their own video mode databases,
9 - one routine to probe for video modes, which can be used by all frame buffer
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
14 needs non-standard modes, like amifb and Mac frame buffer drivers (which
17 When a frame buffer device receives a video= option it doesn't know, it should
18 consider that to be a video mode option. If no frame buffer device is specified
23 <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
24 <name>[-<bpp>][@<refresh>]
31 - NSTC: 480i output, with the CCIR System-M TV mode and NTSC color encoding
[all …]
|
| D | api.rst | 2 The Frame Buffer Device API
9 ---------------
11 This document describes the frame buffer API used by applications to interact
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
13 buffer core are not described.
15 Due to a lack of documentation in the original frame buffer API, drivers
22 ---------------
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
[all …]
|
| D | sstfb.rst | 8 This is a frame buffer device driver for 3dfx' Voodoo Graphics
33 You can apply the patches found in `sstfb/kernel/*-2.{2|4}.x.patch`,
35 `sstfb/patch-2.{2|4}.x-sstfb-yymmdd` to your linux source tree.
58 ----------------
64 white rectangle. why? the function's name is self-explanatory:
71 bind a tty to the new frame buffer. if you already have a frame
72 buffer driver, the voodoo fb will likely be /dev/fb1. if not,
80 --------------
84 bind the tty to the old frame buffer so the module can be removed.
91 ----------------------
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | npcm-video.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 capture a frame from digital video input and compare two frames in memory, and
11 the ECE can compress the frame data into HEXTILE format.
13 Driver-specific Controls
14 ------------------------
21 - COMPLETE mode:
23 Capture the next complete frame into memory.
25 - DIFF mode:
27 Compare the incoming frame with the frame stored in memory, and updates the
28 differentiated frame in memory.
[all …]
|
| /Documentation/networking/ |
| D | packet_mmap.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 - Ulisses Alonso Camaró <uaca@i.hate.spam.alumni.uv.es>
23 - Johann Baudy
34 configurable circular buffer mapped in user space that can be used to either
38 highest bandwidth. By using a shared buffer between the kernel and the user
67 [setup] socket() -------> creation of the capture socket
68 setsockopt() ---> allocation of the circular buffer (ring)
70 mmap() ---------> mapping of the allocated buffer to the
73 [capture] poll() ---------> to wait for incoming packets
75 [shutdown] close() --------> destruction of the capture socket and
[all …]
|
| /Documentation/networking/device_drivers/can/ |
| D | can327.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
7 --------
14 -----------
26 -------------
33 order to fake full-duplex operation.
36 enough to implement simple request-response protocols (such as OBD II),
50 -----------
59 ----------------------------------
68 --debug \
69 --speed 38400 \
[all …]
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | dpaa.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Madalin Bucur <madalin.bucur@nxp.com>
9 - Camelia Groza <camelia.groza@nxp.com>
13 - DPAA Ethernet Overview
14 - DPAA Ethernet Supported SoCs
15 - Configuring DPAA Ethernet in your kernel
16 - DPAA Ethernet Frame Processing
17 - DPAA Ethernet Features
18 - DPAA IRQ Affinity and Receive Side Scaling
19 - Debugging
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _media-request-api:
12 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
16 While the initial use-case was V4L2, it can be extended to other subsystems
20 it is, it is terribly inefficient: user-space would have to flush all activity
21 on the media pipeline, reconfigure it for the next frame, queue the buffers to
23 dequeuing before considering the next frame. This defeats the purpose of having
24 buffer queues since in practice only one buffer would be queued at a time.
28 specific buffers. This allows user-space to schedule several tasks ("requests")
[all …]
|
| /Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
10 ------------------------
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
20 and Intel Cyclone V 5CSEMA4U23C6 based DE0-Nano-SoC Terasic board
21 `QSys integration <https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd>`_
23 `PCIe integration <https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd>`_ of the core.
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
38 ---------------
59 it allows for device hot-plug.
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-glossary.rst | 7 'Documentation/gpu/amdgpu/amdgpu-glossary.rst'; if you cannot find it anywhere,
19 Application-Specific Integrated Circuit
49 Cathode Ray Tube Controller - commonly called "Controller" - Generates
108 Display Micro-Controller Unit
111 Display Micro-Controller Unit, version B
126 Frame Buffer
129 Frame Buffer Compression
156 Line Buffer
225 Transition-Minimized Differential Signaling
|
| /Documentation/driver-api/usb/ |
| D | URB.rst | 1 .. _usb-urb:
6 :Revised: 2000-Dec-05
7 :Again: 2002-Jul-06
8 :Again: 2005-Sep-19
9 :Again: 2017-Mar-29
14 The USB subsystem now has a substantial section at :ref:`usb-hostside-api`
26 - An URB consists of all relevant information to execute any USB transaction
29 - Execution of an URB is inherently an asynchronous operation, i.e. the
33 - Transfers for one URB can be canceled with :c:func:`usb_unlink_urb`
36 - Each URB has a completion handler, which is called after the action
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | pxa_camera.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 PXA-Camera Host Driver
9 -----------
18 ---------------------
22 When a buffer is queued, start_streaming is called and the QCI starts.
27 smoothly captured one frame after the other.
29 Once a buffer is filled in the QCI interface, it is marked as "DONE" and
33 Once the last buffer is filled in, the QCI interface stops.
37 .. code-block:: none
39 +----+ +---+ +----+
[all …]
|
1234567