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
76 set these parameters, respectively. The :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` ioctl is
77 privileged because it allows to set up DMA into physical memory,
80 supposed to run TV applications as root or with SUID bit set. A small
93 1. Chroma-keying displays the overlaid image only where pixels in the
98    the overlaid image. When the bit is set, the corresponding video
131 To get the current parameters applications set the ``type`` field of a
138 To program the overlay window applications set the ``type`` field of a
162 ------------------
165     Size and position of the window relative to the top, left corner of
174     Applications set this field to determine which video field shall be
181     When chroma-keying has been negotiated with
182     :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` applications set this field
187     :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR32>` the value should
192     When chroma-keying has *not* been negotiated and
194     applications can set this field to point to an array of clipping
198     relative to the top, left corner of the frame buffer. However
202     x-y or y-x bands, or the order of rectangles, is not defined. When
209     When the application set the ``clips`` field, this field must
213     supported but no clipping is desired this field must be set to zero.
217     When chroma-keying has *not* been negotiated and
219     applications can set this field to point to a clipping bit mask.
223 displayed only when the bit is *set*. Pixel coordinates translate to
227 .. code-block:: c
236 field must be set to ``NULL``.
239 both, or despite negotiating chroma-keying, the results are undefined.
249     :ref:`framebuffer-flags`).
262 -----------------------
265     Coordinates of the clipping rectangle, relative to the top, left
278 ----------------
281     Horizontal offset of the top, left corner of the rectangle, in
284 ``__s32 top``
285     Vertical offset of the top, left corner of the rectangle, in pixels.
310    Hence as a complexity trade-off drivers *must* support two file
325    BoxRec { short x1, y1, x2, y2; }`` with ``width = x2 - x1`` and
326    ``height = y2 - y1``, so one cannot pass X11 clip lists directly.