~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/driver-api/frame-buffer.rst

Version: ~ [ linux-6.11.5 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.58 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.114 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.169 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.228 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.284 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.322 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.9 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 Frame Buffer Library
  2 ====================
  3 
  4 The frame buffer drivers depend heavily on four data structures. These
  5 structures are declared in include/linux/fb.h. They are fb_info,
  6 fb_var_screeninfo, fb_fix_screeninfo and fb_monospecs. The last
  7 three can be made available to and from userland.
  8 
  9 fb_info defines the current state of a particular video card. Inside
 10 fb_info, there exists a fb_ops structure which is a collection of
 11 needed functions to make fbdev and fbcon work. fb_info is only visible
 12 to the kernel.
 13 
 14 fb_var_screeninfo is used to describe the features of a video card
 15 that are user defined. With fb_var_screeninfo, things such as depth
 16 and the resolution may be defined.
 17 
 18 The next structure is fb_fix_screeninfo. This defines the properties
 19 of a card that are created when a mode is set and can't be changed
 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
 22 cannot be changed or moved.
 23 
 24 The last structure is fb_monospecs. In the old API, there was little
 25 importance for fb_monospecs. This allowed for forbidden things such as
 26 setting a mode of 800x600 on a fix frequency monitor. With the new API,
 27 fb_monospecs prevents such things, and if used correctly, can prevent a
 28 monitor from being cooked. fb_monospecs will not be useful until
 29 kernels 2.5.x.
 30 
 31 Frame Buffer Memory
 32 -------------------
 33 
 34 .. kernel-doc:: drivers/video/fbdev/core/fbmem.c
 35    :export:
 36 
 37 Frame Buffer Colormap
 38 ---------------------
 39 
 40 .. kernel-doc:: drivers/video/fbdev/core/fbcmap.c
 41    :export:
 42 
 43 Frame Buffer Video Mode Database
 44 --------------------------------
 45 
 46 .. kernel-doc:: drivers/video/fbdev/core/modedb.c
 47    :internal:
 48 
 49 .. kernel-doc:: drivers/video/fbdev/core/modedb.c
 50    :export:
 51 
 52 Frame Buffer Macintosh Video Mode Database
 53 ------------------------------------------
 54 
 55 .. kernel-doc:: drivers/video/fbdev/macmodes.c
 56    :export:
 57 
 58 Frame Buffer Fonts
 59 ------------------
 60 
 61 Refer to the file lib/fonts/fonts.c for more information.
 62 

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php