Documentation/fb/api.rst

9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
58 - FB_TYPE_PACKED_PIXELS
67 - FB_TYPE_PLANES
75 - FB_TYPE_INTERLEAVED_PLANES
86 - FB_TYPE_FOURCC
91 - FB_VISUAL_MONO01
102 - FB_VISUAL_MONO10
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.
131 - FB_VISUAL_DIRECTCOLOR
139 - FB_VISUAL_FOURCC
146 ---------------------
208 	__u32 pixclock;			/* pixel clock in ps (pico seconds) */
218 	__u32 colorspace;		/* colorspace for FOURCC-based modes */
232 -----------------------
235 legacy API and the FOURCC-based API.
241 non-standard formats.
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,
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.