Searched +full:frame +full:- +full:buffer (Results 1 – 25 of 134) sorted by relevance
123456
| /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/media/uapi/v4l/ |
| D | pixfmt-compressed.rst | 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
15 .. _compressed-formats:
19 .. flat-table:: Compressed Image Formats
20 :header-rows: 1
21 :stub-columns: 0
24 * - Identifier
25 - Code
[all …]
|
| D | func-read.rst | 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
10 .. _func-read:
19 v4l2-read - Read from a V4L2 device
25 .. code-block:: c
31 :name: v4l2-read
37 File descriptor returned by :ref:`open() <func-open>`.
40 Buffer to be filled
[all …]
|
| D | buffer.rst | 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
16 A buffer contains data exchanged by application and driver using one of
17 the Streaming I/O methods. In the multi-planar API, the data is held in
18 planes, while the buffer structure acts as a container for the planes.
20 copied. These pointers, together with meta-information like timestamps
24 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,
25 some plane-specific members of struct :c:type:`v4l2_buffer`,
[all …]
|
| D | dev-overlay.rst | 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
[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
77 coded format includes a feature of frame reordering; for decoders,
[all …]
|
| D | ext-ctrls-codec.rst | 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
10 .. _mpeg-controls:
31 .. _mpeg-control-id:
34 -----------------
42 .. _v4l2-mpeg-stream-type:
47 enum v4l2_mpeg_stream_type -
48 The MPEG-1, -2 or -4 output stream type. One cannot assume anything
[all …]
|
| D | planar-apis.rst | 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
10 .. _planar-apis:
13 Single- and multi-planar APIs
16 Some devices require data for each input or output video frame to be
17 placed in discontiguous memory buffers. In such cases, one video frame
19 per "plane". A plane is a sub-buffer of the current frame. For examples
22 Initially, V4L2 API did not support multi-planar buffers and a set of
[all …]
|
| D | func-write.rst | 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
10 .. _func-write:
19 v4l2-write - Write to a V4L2 device
25 .. code-block:: c
31 :name: v4l2-write
37 File descriptor returned by :ref:`open() <func-open>`.
40 Buffer with data to be written
[all …]
|
| D | pixfmt-meta-d4xx.rst | 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
10 .. _v4l2-meta-fmt-d4xx:
22 Intel D4xx (D435 and other) cameras include per-frame metadata in their UVC
31 V4L2_META_FMT_D4XX buffers follow the metadata buffer layout of
34 per frame, therefore their headers cannot be larger than 255 bytes.
42 .. flat-table:: D4xx metadata
44 :header-rows: 1
[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>]
37 Sample usage: 1024x768M@60m - CVT timing with margins
[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 …]
|
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Frame Buffer
17 ep93xx-fb
|
| /Documentation/networking/ |
| D | packet_mmap.txt | 1 --------------------------------------------------------------------------------
3 --------------------------------------------------------------------------------
17 -------------------------------------------------------------------------------
19 --------------------------------------------------------------------------------
27 configurable circular buffer mapped in user space that can be used to either
31 highest bandwidth. By using a shared buffer between the kernel and the user
43 --------------------------------------------------------------------------------
45 --------------------------------------------------------------------------------
54 --------------------------------------------------------------------------------
56 --------------------------------------------------------------------------------
[all …]
|
| /Documentation/networking/device_drivers/freescale/ |
| D | dpaa.txt | 11 - DPAA Ethernet Overview
12 - DPAA Ethernet Supported SoCs
13 - Configuring DPAA Ethernet in your kernel
14 - DPAA Ethernet Frame Processing
15 - DPAA Ethernet Features
16 - DPAA IRQ Affinity and Receive Side Scaling
17 - Debugging
30 - Peripheral Access Memory Unit (PAMU) (* needed only for PPC platforms)
32 - Frame Manager (FMan)
34 - Queue Manager (QMan), Buffer Manager (BMan)
[all …]
|
| /Documentation/media/uapi/mediactl/ |
| D | request-api.rst | 1 .. This file is dual-licensed: you can use it either under the terms
21 .. Foundation, with no Invariant Sections, no Front-Cover Texts
22 .. and no Back-Cover Texts. A copy of the license is included at
23 .. Documentation/media/uapi/fdl-appendix.rst.
25 .. TODO: replace it to GPL-2.0 OR GFDL-1.1-or-later WITH no-invariant-sections
27 .. _media-request-api:
35 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
37 to specific frames (aka 'per-frame controls') in order to be used efficiently.
39 While the initial use-case was V4L2, it can be extended to other subsystems
43 it is, it is terribly inefficient: user-space would have to flush all activity
[all …]
|
| /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/media/v4l-drivers/ |
| D | cpia2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
28 --------
30 - Supports cameras with the Vision stv6410 (CIF) and stv6500 (VGA) cmos
32 - Image formats: VGA, QVGA, CIF, QCIF, and a number of sizes in between.
35 - Palette: YCrCb, compressed with MJPEG.
36 - Some compression parameters are settable.
37 - Sensor framerate is adjustable (up to 30 fps CIF, 15 fps VGA).
38 - Adjust brightness, color, contrast while streaming.
39 - Flicker control settable for 50 or 60 Hz mains frequency.
[all …]
|
| D | pxa_camera.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 PXA-Camera Host Driver
9 -----------
18 ---------------------
22 When a buffer is queued (pxa_videobuf_ops->buf_queue), 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 …]
|
| D | omap3isp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 ------------
26 - 3430
27 - 3530
28 - 3630
36 ----------------
42 - OMAP3 ISP CCP2
43 - OMAP3 ISP CSI2a
44 - OMAP3 ISP CCDC
45 - OMAP3 ISP preview
[all …]
|
| /Documentation/ia64/ |
| D | aliasing.rst | 2 Memory Attribute Aliasing on IA-64
19 WB Write-back (cacheable)
21 WC Write-coalescing
25 used for memory-mapped I/O devices. The WC attribute is uncacheable
27 performance for things like frame buffers.
41 supported attributes for each region. At boot-time, the kernel uses
62 boot-time information is required for kexec.
75 Therefore, kern_memmap contains only full granule-sized regions that
97 ----------------
112 -----------------------------------------
[all …]
|
| /Documentation/gpu/ |
| D | vkms.rst | 7 .. kernel-doc:: drivers/gpu/drm/vkms/vkms_drv.c
14 --------------------
16 - Optimize CRC computation ``compute_crc()`` and plane blending ``blend()``
18 - Use the alpha value to blend vaddr_src with vaddr_dst instead of
21 - Add igt test to check cleared alpha value for XRGB plane format.
23 - Add igt test to check extreme alpha values i.e. fully opaque and fully
24 transparent (intermediate values are affected by hw-specific rounding modes).
27 ---------------------
30 module. Use/Test-cases:
32 - Hotplug/hotremove connectors on the fly (to be able to test DP MST handling of
[all …]
|
123456