This is the frame buffer device driver for the P9100 card	  supported on Sparcbook 3 machines.config FB_LEO	bool "Leo (ZX) support"	depends on FB_SBUS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  This is the frame buffer device driver for the SBUS-based Sun ZX	  (leo) frame buffer cards.config FB_IGA	bool "IGA 168x display support"	depends on (FB = y) && SPARC32	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  This is the framebuffer device for the INTERGRAPHICS 1680 and	  successor frame buffer cards.config FB_XVR500	bool "Sun XVR-500 3DLABS Wildcat support"	depends on (FB = y) && PCI && SPARC64	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  This is the framebuffer device for the Sun XVR-500 and similar	  graphics cards based upon the 3DLABS Wildcat chipset.  The driver	  only works on sparc64 systems where the system firmware has	  mostly initialized the card already.  It is treated as a	  completely dumb framebuffer device.config FB_XVR2500	bool "Sun XVR-2500 3DLABS Wildcat support"	depends on (FB = y) && PCI && SPARC64	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  This is the framebuffer device for the Sun XVR-2500 and similar	  graphics cards based upon the 3DLABS Wildcat chipset.  The driver	  only works on sparc64 systems where the system firmware has	  mostly initialized the card already.  It is treated as a	  completely dumb framebuffer device.config FB_PVR2	tristate "NEC PowerVR 2 display support"	depends on FB && SH_DREAMCAST	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	---help---	  Say Y here if you have a PowerVR 2 card in your box.  If you plan to	  run linux on your Dreamcast, you will have to say Y here.	  This driver may or may not work on other PowerVR 2 cards, but is	  totally untested.  Use at your own risk.  If unsure, say N.	  To compile this driver as a module, choose M here: the	  module will be called pvr2fb.	  You can pass several parameters to the driver at boot time or at	  module load time.  The parameters look like "video=pvr2:XXX", where	  the meaning of XXX can be found at the end of the main source file	  (<file:drivers/video/pvr2fb.c>). Please see the file	  <file:Documentation/fb/pvr2fb.txt>.config FB_EPSON1355	bool "Epson 1355 framebuffer support"	depends on (FB = y) && ARCH_CEIVA	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  Build in support for the SED1355 Epson Research Embedded RAMDAC	  LCD/CRT Controller (since redesignated as the S1D13505) as a	  framebuffer.  Product specs at	  <http://www.erd.epson.com/vdc/html/products.htm>.config FB_S1D13XXX	tristate "Epson S1D13XXX framebuffer support"	depends on FB	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  Support for S1D13XXX framebuffer device family (currently only	  working with S1D13806). Product specs at	  <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>config FB_ATMEL	tristate "AT91/AT32 LCD Controller support"	depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  This enables support for the AT91/AT32 LCD Controller.config FB_INTSRAM	bool "Frame Buffer in internal SRAM"	depends on FB_ATMEL && ARCH_AT91SAM9261	help	  Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want	  to let frame buffer in external SDRAM.config FB_ATMEL_STN	bool "Use a STN display with AT91/AT32 LCD Controller"	depends on FB_ATMEL && MACH_AT91SAM9261EK	default n	help	  Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD	  Controller. Say N if you want to connect a TFT.	  If unsure, say N.config FB_NVIDIA	tristate "nVidia Framebuffer Support"	depends on FB && PCI	select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select BITREVERSE	select VGASTATE	help	  This driver supports graphics boards with the nVidia chips, TNT	  and newer. For very old chipsets, such as the RIVA128, then use	  the rivafb.	  Say Y if you have such a graphics board.	  To compile this driver as a module, choose M here: the	  module will be called nvidiafb.config FB_NVIDIA_I2C       bool "Enable DDC Support"       depends on FB_NVIDIA       select FB_DDC       help	  This enables I2C support for nVidia Chipsets.  This is used	  only for getting EDID information from the attached display	  allowing for robust video mode handling and switching.	  Because fbdev-2.6 requires that drivers must be able to	  independently validate video mode parameters, you should say Y	  here.config FB_NVIDIA_DEBUG	bool "Lots of debug output"	depends on FB_NVIDIA	default n	help	  Say Y here if you want the nVidia driver to output all sorts	  of debugging information to provide to the maintainer when	  something goes wrong.config FB_NVIDIA_BACKLIGHT	bool "Support for backlight control"	depends on FB_NVIDIA	default y	help	  Say Y here if you want to control the backlight of your display.config FB_RIVA	tristate "nVidia Riva support"	depends on FB && PCI	select FB_BACKLIGHT if FB_RIVA_BACKLIGHT	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select BITREVERSE	select VGASTATE	help	  This driver supports graphics boards with the nVidia Riva/Geforce	  chips.	  Say Y if you have such a graphics board.	  To compile this driver as a module, choose M here: the	  module will be called rivafb.config FB_RIVA_I2C       bool "Enable DDC Support"       depends on FB_RIVA       select FB_DDC       help	  This enables I2C support for nVidia Chipsets.  This is used	  only for getting EDID information from the attached display	  allowing for robust video mode handling and switching.	  Because fbdev-2.6 requires that drivers must be able to	  independently validate video mode parameters, you should say Y	  here.config FB_RIVA_DEBUG	bool "Lots of debug output"	depends on FB_RIVA	default n	help	  Say Y here if you want the Riva driver to output all sorts	  of debugging information to provide to the maintainer when	  something goes wrong.config FB_RIVA_BACKLIGHT	bool "Support for backlight control"	depends on FB_RIVA	default y	help	  Say Y here if you want to control the backlight of your display.config FB_I810	tristate "Intel 810/815 support (EXPERIMENTAL)"	depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select VGASTATE	help	  This driver supports the on-board graphics built in to the Intel 810           and 815 chipsets.  Say Y if you have and plan to use such a board.          To compile this driver as a module, choose M here: the	  module will be called i810fb.          For more information, please read 	  <file:Documentation/fb/intel810.txt>config FB_I810_GTF	bool "use VESA Generalized Timing Formula"	depends on FB_I810	help	  If you say Y, then the VESA standard, Generalized Timing Formula           or GTF, will be used to calculate the required video timing values	  per video mode.  Since the GTF allows nondiscrete timings           (nondiscrete being a range of values as opposed to discrete being a          set of values), you'll be able to use any combination of horizontal 	  and vertical resolutions, and vertical refresh rates without having	  to specify your own timing parameters.  This is especially useful	  to maximize the performance of an aging display, or if you just           have a display with nonstandard dimensions. A VESA compliant 	  monitor is recommended, but can still work with non-compliant ones.	  If you need or want this, then select this option. The timings may 	  not be compliant with Intel's recommended values. Use at your own 	  risk.          If you say N, the driver will revert to discrete video timings 	  using a set recommended by Intel in their documentation.            If unsure, say N.config FB_I810_I2C	bool "Enable DDC Support"	depends on FB_I810 && FB_I810_GTF	select FB_DDC	helpconfig FB_LE80578	tristate "Intel LE80578 (Vermilion) support"	depends on FB && PCI && X86	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  This driver supports the LE80578 (Vermilion Range) chipsetconfig FB_CARILLO_RANCH	tristate "Intel Carillo Ranch support"	depends on FB_LE80578 && FB && PCI && X86	help	  This driver supports the LE80578 (Carillo Ranch) boardconfig FB_INTEL	tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"	depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_BOOT_VESA_SUPPORT	help	  This driver supports the on-board graphics built in to the Intel          830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.          Say Y if you have and plan to use such a board.	  If you say Y here and want DDC/I2C support you must first say Y to	  "I2C support" and "I2C bit-banging support" in the character devices	  section.	  If you say M here then "I2C support" and "I2C bit-banging support"	  can be build either as modules or built-in.	  To compile this driver as a module, choose M here: the	  module will be called intelfb.	  For more information, please read <file:Documentation/fb/intelfb.txt>config FB_INTEL_DEBUG	bool "Intel driver Debug Messages"	depends on FB_INTEL	---help---	  Say Y here if you want the Intel driver to output all sorts	  of debugging information to provide to the maintainer when	  something goes wrong.config FB_INTEL_I2C	bool "DDC/I2C for Intel framebuffer support"	depends on FB_INTEL	select FB_DDC	default y	help	  Say Y here if you want DDC/I2C support for your on-board Intel graphics.config FB_MATROX	tristate "Matrox acceleration"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_TILEBLITTING	select FB_MACMODES if PPC_PMAC	---help---	  Say Y here if you have a Matrox Millennium, Matrox Millennium II,	  Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox	  Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,	  Matrox G400, G450 or G550 card in your box.	  To compile this driver as a module, choose M here: the	  module will be called matroxfb.	  You can pass several parameters to the driver at boot time or at	  module load time. The parameters look like "video=matrox:XXX", and	  are described in <file:Documentation/fb/matroxfb.txt>.config FB_MATROX_MILLENIUM	bool "Millennium I/II support"	depends on FB_MATROX	help	  Say Y here if you have a Matrox Millennium or Matrox Millennium II	  video card. If you select "Advanced lowlevel driver options" below,	  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp	  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can	  also use font widths different from 8.config FB_MATROX_MYSTIQUE	bool "Mystique support"	depends on FB_MATROX	help	  Say Y here if you have a Matrox Mystique or Matrox Mystique 220	  video card. If you select "Advanced lowlevel driver options" below,	  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp	  packed pixel and 32 bpp packed pixel. You can also use font widths	  different from 8.config FB_MATROX_G	bool "G100/G200/G400/G450/G550 support"	depends on FB_MATROX	---help---	  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based	  video card. If you select "Advanced lowlevel driver options", you	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed	  pixel and 32 bpp packed pixel. You can also use font widths	  different from 8.	  If you need support for G400 secondary head, you must first say Y to	  "I2C support" in the character devices section, and then to	  "Matrox I2C support" and "G400 second head support" here in the	  framebuffer section. G450/G550 secondary head and digital output	  are supported without additional modules.	  The driver starts in monitor mode. You must use the matroxset tool 	  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 	  swap primary and secondary head outputs, or to change output mode.  	  Secondary head driver always start in 640x480 resolution and you 	  must use fbset to change it.	  Do not forget that second head supports only 16 and 32 bpp	  packed pixels, so it is a good idea to compile them into the kernel	  too. You can use only some font widths, as the driver uses generic	  painting procedures (the secondary head does not use acceleration	  engine).	  G450/G550 hardware can display TV picture only from secondary CRTC,	  and it performs no scaling, so picture must have 525 or 625 lines.config FB_MATROX_I2C	tristate "Matrox I2C support"	depends on FB_MATROX	select FB_DDC	---help---	  This drivers creates I2C buses which are needed for accessing the	  DDC (I2C) bus present on all Matroxes, an I2C bus which	  interconnects Matrox optional devices, like MGA-TVO on G200 and	  G400, and the secondary head DDC bus, present on G400 only.	  You can say Y or M here if you want to experiment with monitor	  detection code. You must say Y or M here if you want to use either	  second head of G400 or MGA-TVO on G200 or G400.	  If you compile it as module, it will create a module named	  i2c-matroxfb.config FB_MATROX_MAVEN	tristate "G400 second head support"	depends on FB_MATROX_G && FB_MATROX_I2C	---help---	  WARNING !!! This support does not work with G450 !!!	  Say Y or M here if you want to use a secondary head (meaning two	  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary	  head is not compatible with accelerated XFree 3.3.x SVGA servers -	  secondary head output is blanked while you are in X. With XFree	  3.9.17 preview you can use both heads if you use SVGA over fbdev or	  the fbdev driver on first head and the fbdev driver on second head.