Lines Matching +full:set +full:- +full:top
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
48 Devices supporting the video overlay interface set the
62 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
75 set these parameters, respectively. The :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` ioctl is
76 privileged because it allows to set up DMA into physical memory,
79 supposed to run TV applications as root or with SUID bit set. A small
92 1. Chroma-keying displays the overlaid image only where pixels in the
96 the overlaid image. When the bit is set, the corresponding video
128 To get the current parameters applications set the ``type`` field of a
135 To program the overlay window applications set the ``type`` field of a
159 ------------------
162 Size and position of the window relative to the top, left corner of
171 Applications set this field to determine which video field shall be
178 When chroma-keying has been negotiated with
179 :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` applications set this field
184 :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR32>` the value should
188 When chroma-keying has *not* been negotiated and
190 applications can set this field to point to an array of clipping
194 relative to the top, left corner of the frame buffer. However
198 x-y or y-x bands, or the order of rectangles, is not defined. When
204 When the application set the ``clips`` field, this field must
208 supported but no clipping is desired this field must be set to zero.
211 When chroma-keying has *not* been negotiated and
213 applications can set this field to point to a clipping bit mask.
217 displayed only when the bit is *set*. Pixel coordinates translate to
221 .. code-block:: c
230 field must be set to ``NULL``.
233 both, or despite negotiating chroma-keying, the results are undefined.
243 :ref:`framebuffer-flags`).
256 -----------------------
259 Coordinates of the clipping rectangle, relative to the top, left
272 ----------------
275 Horizontal offset of the top, left corner of the rectangle, in
278 ``__s32 top``
279 Vertical offset of the top, left corner of the rectangle, in pixels.
304 Hence as a complexity trade-off drivers *must* support two file
319 BoxRec { short x1, y1, x2, y2; }`` with ``width = x2 - x1`` and
320 ``height = y2 - y1``, so one cannot pass X11 clip lists directly.