Lines Matching refs:in

14 Due to a lack of documentation in the original frame buffer API, drivers
15 behaviours differ in subtle (and not so subtle) ways. This document describes
23 Device and driver capabilities are reported in the fixed screen information
45 Pixels are stored in memory in hardware-dependent formats. Applications need
46 to be aware of the pixel storage format in order to write image data to the
47 frame buffer memory in the format expected by the hardware.
50 additional information, which are stored in the variable screen information
54 macropixels. Types describe how macropixels are stored in memory. The following
59 Macropixels are stored contiguously in a single plane. If the number of bits
72 Planes are located contiguously in memory.
80 Planes are interleaved in memory. The interleave factor, defined as the
81 distance in bytes between the beginning of two consecutive interleaved blocks
82 belonging to different planes, is stored in the fixed screen information
87 Macropixels are stored in memory as described by the format FOURCC identifier
88 stored in the variable screen information grayscale field.
97 are packed together in a byte.
108 are packed together in a byte.
118 Each component is stored in a macropixel according to the variable screen
127 Each pixel value is stored in the number of bits reported by the variable
135 Each component is stored in a macropixel according to the variable screen
141 identifier stored in the variable screen information grayscale field.
167 	__u32 line_length;		/* length of a line in bytes    */
192 	struct fb_bitfield red;		/* bitfield in fb mem if true color, */
201 	__u32 height;			/* height of picture in mm    */
202 	__u32 width;			/* width of picture in mm     */
206 	/* Timing: All values in pixclocks, except pixclock (of course) */
207 	__u32 pixclock;			/* pixel clock in ps (pico seconds) */
258   color components in memory.
267   Pixel values are bits_per_pixel wide and are split in non-overlapping red,
269   component in the pixel value are described by the fb_bitfield offset and
272   Pixels are always stored in an integer number of bytes. If the number of
287 the FB_CAP_FOURCC bit in the fb_fix_screeninfo capabilities field.
289 FOURCC definitions are located in the linux/videodev2.h header. However, and
292 available in Documentation/DocBook/v4l/pixfmt.xml.
296 the colorspace field to one of the colorspaces listed in linux/videodev2.h and
297 documented in Documentation/DocBook/v4l/colorspaces.xml.
301 drivers must ignore them. Values other than 0 may get a meaning in future