User:ZyMOS/Howto configure the linux kernel/drivers/video

User:ZyMOS/Howto configure the linux kernel / drivers / video


 * Video configuration
 * Video configuration

Graphics support

 * Option: FB
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Support for frame buffer devices"
 * The frame buffer device provides an abstraction for the graphics hardware. It represents the frame buffer of some video hardware and allows application software to access the graphics hardware through a well-defined interface, so the software doesn't need to know anything about the low-level (hardware register) stuff.
 * Frame buffer devices work identically across the different architectures supported by Linux and make the implementation of application programs easier and more portable; at this point, an X server exists which uses the frame buffer device exclusively. On several non-X86 architectures, the frame buffer device is the only way to use the graphics hardware.
 * The device is accessed through special device nodes, usually located in the /dev directory, i.e. /dev/fb*.
 * You need an utility program called fbset to make full use of frame buffer devices. Please read  and the Framebuffer-HOWTO at  for more information.
 * Say Y here and to the driver for your graphics board below if you are compiling a kernel for a non-x86 architecture.
 * If you are compiling for the x86 architecture, you can say Y if you want to play with it, but it is not essential. Please note that running graphical applications that directly touch the hardware (e.g. an accelerated X server) and that are not frame buffer device-aware may cause unexpected results. If unsure, say N.


 * Option: FB_CFB_FILLRECT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module)
 * depends on FB
 * default n
 * Include the cfb_fillrect function for generic software rectangle filling. This is used by drivers that don't provide their own (accelerated) version.


 * Option: FB_CFB_COPYAREA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module)
 * depends on FB
 * default n
 * Include the cfb_copyarea function for generic software area copying. This is used by drivers that don't provide their own (accelerated) version.


 * Option: FB_CFB_IMAGEBLIT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module)
 * depends on FB
 * default n
 * Include the cfb_imageblit function for generic software image blitting. This is used by drivers that don't provide their own (accelerated) version.


 * Option: FB_MACMODES
 * Kernel Versions: 2.6.15.6 ...     tristate      depends on FB      default n


 * Option: FB_MODE_HELPERS
 * Kernel Versions: 2.6.15.6 ...      bool "Enable Video Mode Handling Helpers"       depends on FB
 * default n
 * This enables functions for handling video modes using the Generalized Timing Formula and the EDID parser. A few drivers rely        on this feature such as the radeonfb, rivafb, and the i810fb. If your driver does not take advantage of this feature, choosing Y will just increase the kernel size by about 5K.

is particularly important to one driver, matroxfb. Ifunsure, say N.
 * Option: FB_TILEBLITTING
 * Kernel Versions: 2.6.15.6 ...     bool "Enable Tile Blitting Support"      depends on FB      default n      ---help---        This enables tile blitting.  Tile blitting is a drawing techniquewhere the screen is divided into rectangular sections (tiles), whereasthe standard blitting divides the screen into pixels. Because thedefault drawing element is a tile, drawing functions will be passedparameters in terms of number of tiles instead of number of pixels.For example, to draw a single character, instead of using bitmaps,an index to an array of bitmaps will be used.  To clear or move arectangular section of a screen, the rectangle will be described interms of number of tiles in the x- and y-axis.


 * Option: FB_CIRRUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Cirrus Logic support"
 * depends on FB && (ZORRO || PCI)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This enables support for Cirrus Logic GD542x/543x based boards on Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
 * If you have a PCI-based system, this enables support for these chips: GD-543x, GD-544x, GD-5480.
 * Please read the file .
 * Say N unless you have such a graphics board or plan to get one before you next recompile the kernel.


 * Option: FB_PM2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Permedia2 support"
 * depends on FB && ((AMIGA && BROKEN) || PCI)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the Permedia2 AGP frame buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a product page at .


 * Option: FB_PM2_FIFO_DISCONNECT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "enable FIFO disconnect feature"
 * depends on FB_PM2 && PCI
 * Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).


 * Option: FB_ARMCLCD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "ARM PrimeCell PL110 support"
 * depends on FB && ARM && ARM_AMBA
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This framebuffer device driver is for the ARM PrimeCell PL110 Colour LCD controller. ARM PrimeCells provide the building blocks for System on a Chip devices.
 * If you want to compile this as a module (=code which can be inserted into and removed from the running kernel), say M here and read . The module will be called amba-clcd.


 * Option: FB_ACORN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Acorn VIDC support"
 * depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the Acorn VIDC graphics hardware found in Acorn RISC PCs and other ARM-based machines. If unsure, say N.


 * Option: FB_CLPS711X
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "CLPS711X LCD support"
 * depends on (FB = y) && ARM && ARCH_CLPS711X
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Say Y to enable the Framebuffer driver for the CLPS7111 and EP7212 processors.


 * Option: FB_SA1100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SA-1100 LCD support"
 * depends on (FB = y) && ARM && ARCH_SA1100
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is a framebuffer device for the SA-1100 LCD Controller. See  for information on framebuffer devices.
 * If you plan to use the LCD display with your SA-1100 system, say Y here.


 * Option: FB_IMX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Motorola i.MX LCD support"
 * depends on FB && ARM && ARCH_IMX
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT


 * Option: FB_CYBER2000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "CyberPro 2000/2010/5000 support"
 * depends on FB && PCI && (BROKEN || !SPARC64)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This enables support for the Integraphics CyberPro 20x0 and 5000 VGA chips used in the Rebel.com Netwinder and other machines. Say Y if you have a NetWinder or a graphics card containing this device, otherwise say N.


 * Option: FB_APOLLO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on (FB = y) && APOLLO
 * default y
 * select FB_CFB_FILLRECT
 * select FB_CFB_IMAGEBLIT


 * Option: FB_Q40
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on (FB = y) && Q40
 * default y
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT


 * Option: FB_AMIGA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Amiga native chipset support"
 * depends on FB && AMIGA
 * This is the frame buffer device driver for the builtin graphics chipset found in Amigas.
 * To compile this driver as a module, choose M here: the module will be called amifb.


 * Option: FB_AMIGA_OCS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Amiga OCS chipset support"
 * depends on FB_AMIGA
 * This enables support for the original Agnus and Denise video chips, found in the Amiga 1000 and most A500's and A2000's. If you intend to run Linux on any of these systems, say Y; otherwise say N.


 * Option: FB_AMIGA_ECS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Amiga ECS chipset support"
 * depends on FB_AMIGA
 * This enables support for the Enhanced Chip Set, found in later A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If you intend to run Linux on any of these systems, say Y; otherwise say N.


 * Option: FB_AMIGA_AGA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Amiga AGA chipset support"
 * depends on FB_AMIGA
 * This enables support for the Advanced Graphics Architecture (also known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T and CD32. If you intend to run Linux on any of these systems, say Y; otherwise say N.


 * Option: FB_CYBER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Amiga CyberVision 64 support"
 * depends on FB && ZORRO && BROKEN
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This enables support for the Cybervision 64 graphics card from Phase5. Please note that its use is not all that intuitive (i.e. if you have any questions, be sure to ask!). Say N unless you have a Cybervision 64 or plan to get one before you next recompile the kernel. Please note that this driver DOES NOT support the Cybervision 64/3D card, as they use incompatible video chips.


 * Option: FB_VIRGE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Amiga CyberVision 64/3D support "
 * depends on (FB = y) && ZORRO && BROKEN
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This enables support for the Cybervision 64/3D graphics card from Phase5. Please note that its use is not all that intuitive (i.e. if you have any questions, be sure to ask!). Say N unless you have a Cybervision 64/3D or plan to get one before you next recompile the kernel. Please note that this driver DOES NOT support the older Cybervision 64 card, as they use incompatible video chips.


 * Option: FB_RETINAZ3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Amiga Retina Z3 support"
 * depends on (FB = y) && ZORRO && BROKEN
 * This enables support for the Retina Z3 graphics card. Say N unless you have a Retina Z3 or plan to get one before you next recompile the kernel.


 * Option: FB_FM2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Amiga FrameMaster II/Rainbow II support"
 * depends on (FB = y) && ZORRO
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the Amiga FrameMaster card from BSC (exhibited 1992 but not shipped as a CBM product).


 * Option: FB_ARC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Arc Monochrome LCD board support"
 * depends on FB && X86
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This enables support for the Arc Monochrome LCD board. The board is based on the KS-108 lcd controller and is typically a matrix of 2*n chips. This driver was tested with a 128x64 panel. This driver supports it for use with x86 SBCs through a 16 bit GPIO interface (8 bit data, 8 bit control). If you anticpate using this driver, say Y or M; otherwise say N. You must specify the GPIO IO address to be used for setting control and data.


 * Option: FB_ATARI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Atari native chipset support"
 * depends on (FB = y) && ATARI && BROKEN
 * This is the frame buffer device driver for the builtin graphics chipset found in Ataris.


 * Option: FB_OF
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Open Firmware frame buffer device support"
 * depends on (FB = y) && (PPC64 || PPC_OF)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES
 * Say Y if you want support with Open Firmware for your graphics board.


 * Option: FB_CONTROL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Apple \"control\" display support"
 * depends on (FB = y) && PPC_PMAC
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES
 * This driver supports a frame buffer for the graphics adapter in the Power Macintosh 7300 and others.


 * Option: FB_PLATINUM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Apple \"platinum\" display support"
 * depends on (FB = y) && PPC_PMAC
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES
 * This driver supports a frame buffer for the "platinum" graphics adapter in some Power Macintoshes.


 * Option: FB_VALKYRIE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Apple \"valkyrie\" display support"
 * depends on (FB = y) && (MAC || PPC_PMAC)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES
 * This driver supports a frame buffer for the "valkyrie" graphics adapter in some Power Macintoshes.


 * Option: FB_CT65550
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Chips 65550 display support"
 * depends on (FB = y) && PPC
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the Chips & Technologies 65550 graphics chip in PowerBooks.


 * Option: FB_ASILIANT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Asiliant (Chips) 69000 display support"
 * depends on (FB = y) && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT


 * Option: FB_IMSTT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IMS Twin Turbo display support"
 * depends on (FB = y) && PCI
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES if PPC
 * The IMS Twin Turbo is a PCI-based frame buffer card bundled with many Macintosh and compatible computers.


 * Option: FB_VGA16
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "VGA 16-color graphics support"
 * depends on FB && (X86 || PPC)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for VGA 16 color graphic cards. Say Y if you have such a card.
 * To compile this driver as a module, choose M here: the module will be called vga16fb.


 * Option: FB_STI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "HP STI frame buffer device support"
 * depends on FB && PARISC
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * default y
 * STI refers to the HP "Standard Text Interface" which is a set of BIOS routines contained in a ROM chip in HP PA-RISC based machines. Enabling this option will implement the linux framebuffer device using calls to the STI BIOS routines for initialisation.
 * If you enable this option, you will get a planar framebuffer device /dev/fb which will work on the most common HP graphic cards of the NGLE family, including the artist chips (in the 7xx and Bxxx series), HCRX, HCRX24, CRX, CRX24 and VisEG series.
 * It is safe to enable this option, so you should probably say "Y".


 * Option: FB_MAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Generic Macintosh display support"
 * depends on (FB = y) && MAC
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES


 * bool ' Apple DAFB display support' CONFIG_FB_DAFB


 * Option: FB_HP300
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on (FB = y) && HP300
 * select FB_CFB_FILLRECT
 * select FB_CFB_IMAGEBLIT
 * default y


 * Option: FB_TGA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "TGA framebuffer support"
 * depends on FB && ALPHA
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for generic TGA graphic cards. Say Y if you have one of those.


 * Option: FB_VESA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "VESA VGA graphics support"
 * depends on (FB = y) && X86
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for generic VESA 2.0 compliant graphic cards. The older VESA 1.2 cards are not supported. You will get a boot time penguin logo at no additional cost. Please read . If unsure, say Y.


 * Option: VIDEO_SELECT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on FB_VESA
 * default y


 * Option: FB_HGA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Hercules mono graphics support"
 * depends on FB && X86
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Say Y here if you have a Hercules mono graphics card.
 * To compile this driver as a module, choose M here: the module will be called hgafb.
 * As this card technology is 15 years old, most people will answer N here.

will compile the Hercules mono graphics with functions.
 * Option: FB_HGA_ACCEL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Hercules mono Acceleration functions (EXPERIMENTAL)"
 * depends on FB_HGA && EXPERIMENTAL


 * Option: VIDEO_SELECT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on (FB = y) && X86
 * default y


 * Option: FB_SGIVW
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SGI Visual Workstation framebuffer support"
 * depends on FB && X86_VISWS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * SGI Visual Workstation support for framebuffer graphics.


 * Option: FB_GBE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SGI Graphics Backend frame buffer support"
 * depends on (FB = y) && (SGI_IP32 || X86_VISWS)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIThelp This is the frame buffer device driver for SGI Graphics Backend. This chip is used in SGI O2 and Visual Workstation 320/540.

"Video memory size in MB"
 * Option: FB_GBE_MEM
 * Kernel Versions: 2.6.15.6 ...
 * depends on FB_GBE
 * default 4
 * This is the amount of memory reserved for the framebuffer, which can be any value between 1MB and 8MB.


 * Option: BUS_I2C
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on (FB = y) && VISWS
 * default y


 * Option: FB_SUN3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Sun3 framebuffer support"
 * depends on (FB = y) && (SUN3 || SUN3X) && BROKEN


 * Option: FB_SBUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SBUS and UPA framebuffers"
 * depends on (FB = y) && SPARC
 * Say Y if you want support for SBUS or UPA based frame buffer device.


 * Option: FB_BW2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "BWtwo support"
 * depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the BWtwo frame buffer.


 * Option: FB_CG3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "CGthree support"
 * depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the CGthree frame buffer.


 * Option: FB_CG6
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "CGsix (GX,TurboGX) support"
 * depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the CGsix (GX, TurboGX) frame buffer.


 * Option: FB_PVR2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NEC PowerVR 2 display support"
 * depends on FB && SH_DREAMCAST
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * 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 (). Please see the file .


 * Option: FB_EPSON1355
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Epson 1355 framebuffer support"
 * depends on (FB = y) && (SUPERH || ARCH_CEIVA)
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Build in support for the SED1355 Epson Research Embedded RAMDAC LCD/CRT Controller (since redesignated as the S1D13505) as a framebuffer. Product specs at .


 * Option: FB_S1D13XXX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Epson S1D13XXX framebuffer support"
 * depends on FB
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Support for S1D13XXX framebuffer device family (currently only working with S1D13806). Product specs at 


 * Option: FB_NVIDIA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "nVidia Framebuffer Support"
 * depends on FB && PCI
 * select I2C_ALGOBIT if FB_NVIDIA_I2C
 * select I2C if FB_NVIDIA_I2C
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * 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.


 * Option: FB_NVIDIA_I2C
 * Kernel Versions: 2.6.15.6 ...     bool "Enable DDC Support"      depends on FB_NVIDIA      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.


 * Option: FB_RIVA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "nVidia Riva support"
 * depends on FB && PCI
 * select I2C_ALGOBIT if FB_RIVA_I2C
 * select I2C if FB_RIVA_I2C
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * 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.


 * Option: FB_RIVA_I2C
 * Kernel Versions: 2.6.15.6 ...     bool "Enable DDC Support"      depends on FB_RIVA      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.


 * Option: FB_RIVA_DEBUG
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Lots of debug output from Riva(nVidia) driver"
 * depends on FB_RIVA
 * default n
 * Say Y here if you want the Riva driver to output all sorts of debugging informations to provide to the maintainer when something goes wrong.


 * Option: FB_I810
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Intel 810/815 support (EXPERIMENTAL)"
 * depends on FB && EXPERIMENTAL && PCI && X86_32
 * select AGP
 * select AGP_INTEL
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * 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 


 * Option: FB_I810_GTF
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "use VESA Generalized Timing Formula"
 * depends on FB_I810
 * 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.


 * Option: FB_I810_I2C
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Enable DDC Support"
 * depends on FB_I810 && FB_I810_GTF
 * select I2C
 * select I2C_ALGOBIT


 * Option: FB_INTEL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
 * depends on FB && EXPERIMENTAL && PCI && X86_32
 * select AGP
 * select AGP_INTEL
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This driver supports the on-board graphics built in to the Intel        830M/845G/852GM/855GM/865G 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 intelfb.


 * Option: FB_INTEL_DEBUG
 * Kernel Versions: 2.6.15.6 ...      bool "Intel driver Debug Messages"
 * depends on FB_INTEL
 * Say Y here if you want the Intel driver to output all sorts of debugging informations to provide to the maintainer when something goes wrong.


 * Option: FB_MATROX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "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
 * 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 .


 * Option: FB_MATROX_MILLENIUM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Millennium I/II support"
 * depends on FB_MATROX
 * 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.


 * Option: FB_MATROX_MYSTIQUE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Mystique support"
 * depends on FB_MATROX
 * 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.


 * Option: FB_MATROX_G
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "G100/G200/G400/G450/G550 support"
 * depends on FB_MATROX
 * 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 ) 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.


 * Option: FB_MATROX_I2C
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Matrox I2C support"
 * depends on FB_MATROX && I2C
 * select I2C_ALGOBIT
 * 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.


 * Option: FB_MATROX_MAVEN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "G400 second head support"
 * depends on FB_MATROX_G && FB_MATROX_I2C
 * 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.
 * If you compile it as module, two modules are created, matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for both G200 and G400, matroxfb_crtc2 is needed only by G400. You must also load i2c-matroxfb to get it to run.
 * The driver starts in monitor mode and you must use the matroxset tool (available at ) to switch it to PAL or NTSC or to swap primary and secondary head outputs. Secondary head driver also always start in 640x480 resolution, you must use fbset to change it.
 * Also 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).


 * Option: FB_MATROX_MULTIHEAD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Multihead support"
 * depends on FB_MATROX
 * Say Y here if you have more than one (supported) Matrox device in your computer and you want to use all of them for different monitors ("multihead"). If you have only one device, you should say N because the driver compiled with Y is larger and a bit slower, especially on ia32 (ix86).
 * If you said M to "Matrox unified accelerated driver" and N here, you will still be able to use several Matrox devices simultaneously: insert several instances of the module matroxfb into the kernel with insmod, supplying the parameter "dev=N" where N is 0, 1, etc. for the different Matrox devices. This method is slightly faster but uses 40 KB of kernel memory per Matrox card.
 * There is no need for enabling 'Matrox multihead support' if you have only one Matrox card in the box.


 * Option: FB_RADEON_OLD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "ATI Radeon display support (Old driver)"
 * depends on FB && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES if PPC
 * Choose this option if you want to use an ATI Radeon graphics card as a framebuffer device. There are both PCI and AGP versions.  You don't need to choose this to run the Radeon in plain VGA mode. There is a product page at .


 * Option: FB_RADEON
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "ATI Radeon display support"
 * depends on FB && PCI
 * select I2C_ALGOBIT if FB_RADEON_I2C
 * select I2C if FB_RADEON_I2C
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES if PPC_OF
 * Choose this option if you want to use an ATI Radeon graphics card as a framebuffer device. There are both PCI and AGP versions.  You don't need to choose this to run the Radeon in plain VGA mode.
 * 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.
 * There is a product page at http://apps.ati.com/ATIcompare/


 * Option: FB_RADEON_I2C
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "DDC/I2C for ATI Radeon support"
 * depends on FB_RADEON
 * default y
 * Say Y here if you want DDC/I2C support for your Radeon board.


 * Option: FB_RADEON_DEBUG
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Lots of debug output from Radeon driver"
 * depends on FB_RADEON
 * default n
 * Say Y here if you want the Radeon driver to output all sorts of debugging informations to provide to the maintainer when something goes wrong.


 * Option: FB_ATY128
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "ATI Rage128 display support"
 * depends on FB && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES if PPC_PMAC
 * This driver supports graphics boards with the ATI Rage128 chips. Say Y if you have such a graphics board and read <file:Documentation/fb/aty128fb.txt>.
 * To compile this driver as a module, choose M here: the module will be called aty128fb.


 * Option: FB_ATY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "ATI Mach64 display support" if PCI || ATARI
 * depends on FB
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * select FB_MACMODES if PPC
 * This driver supports graphics boards with the ATI Mach64 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 atyfb.


 * Option: FB_ATY_CT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
 * depends on PCI && FB_ATY
 * default y if SPARC64 && FB_PCI
 * Say Y here to support use of ATI's 64-bit Rage boards (or other boards based on the Mach64 CT, VT, GT, and LT chipsets) as a framebuffer device. The ATI product support page for these boards is at <http://support.ati.com/products/pc/mach64/>.


 * Option: FB_ATY_GENERIC_LCD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Mach64 generic LCD support (EXPERIMENTAL)"
 * depends on FB_ATY_CT
 * Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility, Rage XC, or Rage XL chipset.


 * Option: FB_ATY_XL_INIT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Rage XL No-BIOS Init support"
 * depends on FB_ATY_CT
 * Say Y here to support booting a Rage XL without BIOS support.


 * Option: FB_ATY_GX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Mach64 GX support" if PCI
 * depends on FB_ATY
 * default y if ATARI
 * Say Y here to support use of the ATI Mach64 Graphics Expression board (or other boards based on the Mach64 GX chipset) as a framebuffer device. The ATI product support page for these boards is at <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.


 * Option: FB_S3TRIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "S3 Trio display support"
 * depends on (FB = y) && PPC && BROKEN
 * If you have a S3 Trio say Y. Say N for S3 Virge.


 * Option: FB_SAVAGE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "S3 Savage support"
 * depends on FB && PCI && EXPERIMENTAL
 * select I2C_ALGOBIT if FB_SAVAGE_I2C
 * select I2C if FB_SAVAGE_I2C
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This driver supports notebooks and computers with S3 Savage PCI/AGP chips.
 * Say Y if you have such a graphics card.
 * To compile this driver as a module, choose M here; the module will be called savagefb.


 * Option: FB_SAVAGE_I2C
 * Kernel Versions: 2.6.15.6 ...     bool "Enable DDC2 Support"      depends on FB_SAVAGE      help This enables I2C support for S3 Savage 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.


 * Option: FB_SAVAGE_ACCEL
 * Kernel Versions: 2.6.15.6 ...     bool "Enable Console Acceleration"      depends on FB_SAVAGE      default n      help         This option will compile in console acceleration support. If         the resulting framebuffer console has bothersome glitches, then         choose N here.


 * Option: FB_SIS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SiS/XGI display support"
 * depends on FB && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the SiS 300, 315, 330 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets. Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
 * To compile this driver as a module, choose M here; the module will be called sisfb.


 * Option: FB_SIS_300
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SiS 300 series support"
 * depends on FB_SIS
 * Say Y here to support use of the SiS 300/305, 540, 630 and 730.


 * Option: FB_SIS_315
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SiS 315/330/340 series and XGI support"
 * depends on FB_SIS
 * Say Y here to support use of the SiS 315, 330 and 340 series (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well as XGI V3XT, V5, V8 and Z7.


 * Option: FB_NEOMAGIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NeoMagic display support"
 * depends on FB && PCI
 * select FB_MODE_HELPERS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This driver supports notebooks with NeoMagic PCI chips. Say Y if you have such a graphics card.
 * To compile this driver as a module, choose M here: the module will be called neofb.


 * Option: FB_KYRO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "IMG Kyro support"
 * depends on FB && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Say Y here if you have a STG4000 / Kyro / PowerVR 3 based graphics board.
 * To compile this driver as a module, choose M here: the module will be called kyrofb.


 * Option: FB_3DFX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3Dfx Banshee/Voodoo3 display support"
 * depends on FB && PCI
 * select FB_CFB_IMAGEBLIT
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 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 tdfxfb.

will compile the 3Dfx Banshee/Voodoo3 frame buffer device acceleration functions.
 * Option: FB_3DFX_ACCEL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
 * depends on FB_3DFX && EXPERIMENTAL


 * Option: FB_VOODOO1
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3Dfx Voodoo Graphics (sst1) support"
 * depends on FB && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or Voodoo2 (cvg) based graphics card.
 * To compile this driver as a module, choose M here: the module will be called sstfb.
 * WARNING: Do not use any application that uses the 3D engine (namely glide) while using this driver. Please read the <file:Documentation/fb/README-sstfb.txt> for supported options and other important info support.


 * Option: FB_CYBLA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Cyberblade/i1 support"
 * depends on FB && PCI
 * select FB_CFB_IMAGEBLIT
 * select VIDEO_SELECT
 * This driver is supposed to support the Trident Cyberblade/i1 graphics core integrated in the VIA VT8601A North Bridge, also known as VIA Apollo PLE133.
 * Status: - Developed, tested and working on EPIA 5000 and EPIA 800.  - Does work reliable on all systems with CRT/LCD connected to    normal VGA ports.  - Should work on systems that do use the internal LCD port, but    this is absolutely not tested.
 * Character imageblit, copyarea and rectangle fill are hw accelerated, ypan scrolling is used by default.
 * Please do read <file:Documentation/fb/cyblafb/*>.
 * To compile this driver as a module, choose M here: the module will be called cyblafb.


 * Option: FB_TRIDENT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Trident support"
 * depends on FB && PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This driver is supposed to support graphics boards with the Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops but also on some motherboards. For more information, read <file:Documentation/fb/tridentfb.txt>
 * Cyberblade/i1 support will be removed soon, use the cyblafb driver instead.
 * Say Y if you have such a graphics board.


 * To compile this driver as a module, choose M here: the module will be called tridentfb.

will compile the Trident frame buffer device with functions.
 * Option: FB_TRIDENT_ACCEL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Trident Acceleration functions (EXPERIMENTAL)"
 * depends on FB_TRIDENT && EXPERIMENTAL


 * Option: FB_PM3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Permedia3 support"
 * depends on FB && PCI && BROKEN
 * This is the frame buffer device driver for the 3DLabs Permedia3 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000 and maybe other boards.


 * Option: FB_AU1100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Au1100 LCD Driver"
 * depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/video/geode


 * Option: FB_FFB
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Creator/Creator3D/Elite3D support"
 * depends on FB_SBUS && SPARC64
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the Creator, Creator3D, and Elite3D graphics boards.


 * Option: FB_TCX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "TCX (SS4/SS5 only) support"
 * depends on FB_SBUS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the TCX 24/8bit frame buffer.


 * Option: FB_CG14
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "CGfourteen (SX) support"
 * depends on FB_SBUS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the CGfourteen frame buffer on Desktop SPARCsystems with the SX graphics option.


 * Option: FB_P9100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "P9100 (Sparcbook 3 only) support"
 * depends on FB_SBUS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the P9100 card supported on Sparcbook 3 machines.


 * Option: FB_LEO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Leo (ZX) support"
 * depends on FB_SBUS
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the SBUS-based Sun ZX (leo) frame buffer cards.


 * Option: FB_PCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PCI framebuffers"
 * depends on (FB = y) && PCI && SPARC


 * Option: FB_IGA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IGA 168x display support"
 * depends on SPARC32 && FB_PCI
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the framebuffer device for the INTERGRAPHICS 1680 and successor frame buffer cards.


 * Option: FB_HIT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "HD64461 Frame Buffer support"
 * depends on FB && HD64461
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is the frame buffer device driver for the Hitachi HD64461 LCD frame buffer card.


 * Option: FB_PMAG_AA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PMAG-AA TURBOchannel framebuffer support"
 * depends on (FB = y) && TCselect FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1) used mainly in the MIPS-based DECstation series.


 * Option: FB_PMAG_BA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PMAG-BA TURBOchannel framebuffer support"
 * depends on (FB = y) && TCselect FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) used mainly in the MIPS-based DECstation series.


 * Option: FB_PMAGB_B
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PMAGB-B TURBOchannel framebuffer support"
 * depends on (FB = y) && TCselect FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * Support for the PMAGB-B TURBOchannel framebuffer card used mainly in the MIPS-based DECstation series. The card is currently only supported in 1280x1024x8 mode.


 * Option: FB_MAXINE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Maxine (Personal DECstation) onboard framebuffer support"
 * depends on (FB = y) && MACH_DECSTATIONselect FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * Support for the onboard framebuffer (1024x768x8) in the Personal DECstation series (Personal DECstation 5000/20, /25, /33, /50, Codename "Maxine").


 * Option: FB_TX3912
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "TMPTX3912/PR31700 frame buffer support"
 * depends on (FB = y) && NINO
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
 * Say Y here to enable kernel support for the on-board framebuffer.


 * Option: FB_G364
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "G364 frame buffer support"
 * depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)select FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * The G364 driver is the framebuffer used in MIPS Magnum 4000 and Olivetti M700-10 systems.


 * Option: FB_68328
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Motorola 68328 native frame buffer support"
 * depends on FB && (M68328 || M68EZ328 || M68VZ328)select FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * Say Y here if you want to support the built-in frame buffer of the Motorola 68328 CPU family.


 * Option: FB_PXA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PXA LCD framebuffer support"
 * depends on FB && ARCH_PXA
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Frame buffer driver for the built-in LCD controller in the Intel PXA2x0 processor.
 * This driver is also available as a module ( = code which can be inserted and removed from the running kernel whenever you want). The module will be called vfb. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>.
 * If unsure, say N.


 * Option: FB_PXA_PARAMETERS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PXA LCD command line parameters"
 * default n
 * depends on FB_PXA
 * Enable the use of kernel command line or module parameters to configure the physical properties of the LCD panel when using the PXA LCD driver.
 * This option allows you to override the panel parameters supplied by the platform in order to support multiple different models of flatpanel. If you will only be using a single model of flatpanel then you can safely leave this option disabled.
 * <file:Documentation/fb/pxafb.txt> describes the available parameters.


 * Option: FB_W100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "W100 frame buffer support"
 * depends on FB && PXA_SHARPSLselect FB_CFB_FILLRECTselect FB_CFB_COPYAREAselect FB_CFB_IMAGEBLIT
 * Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
 * This driver is also available as a module ( = code which can be inserted and removed from the running kernel whenever you want). The module will be called vfb. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>.
 * If unsure, say N.


 * Option: FB_S3C2410
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "S3C2410 LCD framebuffer support"
 * depends on FB && ARCH_S3C2410
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * Frame buffer driver for the built-in LCD controller in the Samsung S3C2410 processor.
 * This driver is also available as a module ( = code which can be inserted and removed from the running kernel whenever you want). The module will be called s3c2410fb. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>.
 * If unsure, say N.


 * Option: FB_S3C2410_DEBUG
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "S3C2410 lcd debug messages"
 * depends on FB_S3C2410
 * Turn on debugging messages. Note that you can set/unset at run time through sysfs

VT
 * Option: FB_VIRTUAL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Virtual Frame Buffer support (ONLY FOR TESTING!)"
 * depends on FB
 * select FB_CFB_FILLRECT
 * select FB_CFB_COPYAREA
 * select FB_CFB_IMAGEBLIT
 * This is a `virtual' frame buffer device. It operates on a chunk of unswappable kernel memory instead of on the memory of a graphics board. This means you cannot see any output sent to this frame buffer device, while it does consume precious memory. The main use of this frame buffer device is testing and debugging the frame buffer subsystem. Do NOT enable it for normal systems! To protect the innocent, it has to be enabled explicitly at boot time using the kernel option `video=vfb:'.
 * To compile this driver as a module, choose M here: the module will be called vfb.
 * If unsure, say N.


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/video/console

FB || SGI_NEWPORT_CONSOLE


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/video/logo

FB && SYSFS


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/video/backlight