Lines Matching +full:frame +full:- +full:number

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
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
48 frame buffer memory in the format expected by the hardware.
50 Formats are described by frame buffer types and visuals. Some visuals require
58 - FB_TYPE_PACKED_PIXELS
60 Macropixels are stored contiguously in a single plane. If the number of bits
67 - FB_TYPE_PLANES
69 Macropixels are split across multiple planes. The number of planes is equal to
70 the number of bits per macropixel, with plane i'th storing i'th bit from all
75 - FB_TYPE_INTERLEAVED_PLANES
77 Macropixels are split across multiple planes. The number of planes is equal to
78 the number of bits per macropixel, with plane i'th storing i'th bit from all
86 - FB_TYPE_FOURCC
91 - FB_VISUAL_MONO01
93 Pixels are black or white and stored on a number of bits (typically one)
97 set to 0. When the number of bits per pixel is smaller than 8, several pixels
102 - FB_VISUAL_MONO10
104 Pixels are black or white and stored on a number of bits (typically one)
108 set to 1. When the number of bits per pixel is smaller than 8, several pixels
113 - FB_VISUAL_TRUECOLOR
116 indexes a read-only lookup table for the corresponding value. Lookup tables
117 are device-dependent, and provide linear or non-linear ramps.
122 - FB_VISUAL_PSEUDOCOLOR and FB_VISUAL_STATIC_PSEUDOCOLOR
125 blue components. The colormap is read-only for FB_VISUAL_STATIC_PSEUDOCOLOR
126 and read-write for FB_VISUAL_PSEUDOCOLOR.
128 Each pixel value is stored in the number of bits reported by the variable
131 - FB_VISUAL_DIRECTCOLOR
139 - FB_VISUAL_FOURCC
146 ---------------------
153 about the frame buffer device and the current format. Those information can't
159 unsigned long smem_start; /* Start of frame buffer mem */
161 __u32 smem_len; /* Length of frame buffer mem */
179 about a frame buffer device, its current format and video mode, as well as
218 __u32 colorspace; /* colorspace for FOURCC-based modes */
232 -----------------------
234 Frame buffer devices offer two ways to configure the frame buffer format: the
235 legacy API and the FOURCC-based API.
238 The legacy API has been the only frame buffer format configuration API for a
241 non-standard formats.
244 to the desired frame buffer depth. Values up to 8 will usually map to
247 - For grayscale formats, applications set the grayscale field to one. The red,
252 - For pseudocolor formats, applications set the grayscale field to zero. The
257 - For truecolor and directcolor formats, applications set the grayscale field
268 Pixel values are bits_per_pixel wide and are split in non-overlapping red,
273 Pixels are always stored in an integer number of bytes. If the number of
281 The FOURCC-based API replaces format descriptions by four character codes
284 formats. Drivers are also encouraged to implement the FOURCC-based API for RGB
287 Drivers that support the FOURCC-based API report this capability by setting
293 available in Documentation/userspace-api/media/v4l/pixfmt.rst.
298 documented in Documentation/userspace-api/media/v4l/colorspaces.rst.
300 The red, green, blue and transp fields are not used with the FOURCC-based API.