Lines Matching +full:frame +full:- +full:buffer

4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
18 Video overlay devices have the ability to genlock (TV-)video into the
19 (VGA-)video signal of a graphics card, or to store captured images
37 frame rate of the video standard is not guaranteed. Frames may be
65 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
74 frame buffer parameters, namely the address and size of the frame buffer
81 superuser can change the frame buffer address and size. Users are not
87 card. In this case the frame buffer is not modified by the video device,
88 and the frame buffer address and pixel format are not needed by the
95 1. Chroma-keying displays the overlaid image only where pixels in the
112 prohibits different image and frame buffer formats, the format requested
162 ------------------
166     the frame buffer defined with
168     frame buffer width and height, the ``x`` and ``y`` coordinates can
169     be negative, and it can lie completely outside the frame buffer. The
181     When chroma-keying has been negotiated with
187     :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR32>` the value should
191     When chroma-keying has *not* been negotiated and
197     relative to the top, left corner of the frame buffer. However
198     clipping rectangles must not extend the frame buffer width and
201     x-y or y-x bands, or the order of rectangles, is not defined. When
214     When chroma-keying has *not* been negotiated and
224 .. code-block:: c
236 both, or despite negotiating chroma-keying, the results are undefined.
246     :ref:`framebuffer-flags`).
259 -----------------------
263     corner of the frame buffer. Only window pixels *outside* all
275 ----------------
295 To start or stop the frame buffer overlay applications call the
312    Hence as a complexity trade-off drivers *must* support two file
319    When the image is written into frame buffer memory it will be
327    BoxRec { short x1, y1, x2, y2; }`` with ``width = x2 - x1`` and
328    ``height = y2 - y1``, so one cannot pass X11 clip lists directly.