Lines Matching refs:by

10 This document describes the frame buffer API used by applications to interact
47 frame buffer memory in the format expected by the hardware.
49 Formats are described by frame buffer types and visuals. Some visuals require
87 Macropixels are stored in memory as described by the format FOURCC identifier
93 specified by the variable screen information bpp field.
95 Black pixels are represented by all bits set to 1 and white pixels by all bits
104 specified by the variable screen information bpp field.
106 Black pixels are represented by all bits set to 0 and white pixels by all bits
127 Each pixel value is stored in the number of bits reported by the variable
140 Pixels are encoded and  interpreted as described by the format FOURCC
147 Screen information are queried by applications using the FBIOGET_FSCREENINFO
153 be directly modified by applications, but can be changed by the driver when an
238 long time and is thus widely used by application. It is the recommended API
247   blue, green and transp fields must be set to 0 by applications and ignored by
252   red, blue, green and transp fields must be set to 0 by applications and
253   ignored by drivers. Drivers must fill the red, blue and green offsets to 0
269   component in the pixel value are described by the fb_bitfield offset and
280 The FOURCC-based API replaces format descriptions by four character codes
286 Drivers that support the FOURCC-based API report this capability by setting
295 For YUV formats, they should also select the appropriate colorspace by setting