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	  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) 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).config FB_MATROX_MULTIHEAD	bool "Multihead support"	depends on FB_MATROX	---help---	  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.config FB_RADEON	tristate "ATI Radeon display support"	depends on FB && PCI	select FB_BACKLIGHT if FB_RADEON_BACKLIGHT	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_MACMODES if PPC_OF	help	  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/config FB_RADEON_I2C	bool "DDC/I2C for ATI Radeon support"	depends on FB_RADEON	select FB_DDC	default y	help	  Say Y here if you want DDC/I2C support for your Radeon board. config FB_RADEON_BACKLIGHT	bool "Support for backlight control"	depends on FB_RADEON	default y	help	  Say Y here if you want to control the backlight of your display.config FB_RADEON_DEBUG	bool "Lots of debug output from Radeon driver"	depends on FB_RADEON	default n	help	  Say Y here if you want the Radeon driver to output all sorts	  of debugging information to provide to the maintainer when	  something goes wrong.config FB_ATY128	tristate "ATI Rage128 display support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_BACKLIGHT if FB_ATY128_BACKLIGHT	select FB_MACMODES if PPC_PMAC	help	  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.config FB_ATY128_BACKLIGHT	bool "Support for backlight control"	depends on FB_ATY128	default y	help	  Say Y here if you want to control the backlight of your display.config FB_ATY	tristate "ATI Mach64 display support" if PCI || ATARI	depends on FB && !SPARC32	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_BACKLIGHT if FB_ATY_BACKLIGHT	select FB_MACMODES if PPC	help	  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.config FB_ATY_CT	bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"	depends on PCI && FB_ATY	default y if SPARC64 && PCI	help	  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/>.config FB_ATY_GENERIC_LCD	bool "Mach64 generic LCD support (EXPERIMENTAL)"	depends on FB_ATY_CT	help	  Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,	  Rage XC, or Rage XL chipset.config FB_ATY_GX	bool "Mach64 GX support" if PCI	depends on FB_ATY	default y if ATARI	help	  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>.config FB_ATY_BACKLIGHT	bool "Support for backlight control"	depends on FB_ATY	default y	help	  Say Y here if you want to control the backlight of your display.config FB_S3	tristate "S3 Trio/Virge support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_TILEBLITTING	select FB_SVGALIB	select VGASTATE	select FONT_8x16 if FRAMEBUFFER_CONSOLE	---help---	  Driver for graphics boards with S3 Trio / S3 Virge chip.config FB_SAVAGE	tristate "S3 Savage support"	depends on FB && PCI && EXPERIMENTAL	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select VGASTATE	help	  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.config FB_SAVAGE_I2C       bool "Enable DDC2 Support"       depends on FB_SAVAGE       select FB_DDC       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.config FB_SAVAGE_ACCEL       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.config FB_SIS	tristate "SiS/XGI display support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_BOOT_VESA_SUPPORT	help	  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.config FB_SIS_300	bool "SiS 300 series support"	depends on FB_SIS	help	  Say Y here to support use of the SiS 300/305, 540, 630 and 730.config FB_SIS_315	bool "SiS 315/330/340 series and XGI support"	depends on FB_SIS	help	  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.config FB_VIA       tristate "VIA UniChrome (Pro) and Chrome9 display support"       depends on FB && PCI       select FB_CFB_FILLRECT       select FB_CFB_COPYAREA       select FB_CFB_IMAGEBLIT       select FB_SOFT_CURSOR       select I2C_ALGOBIT       select I2C       help	  This is the frame buffer device driver for Graphics chips of VIA	  UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/	  CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896 	  /P4M900,VX800)	  Say Y if you have a VIA UniChrome graphics board.	  To compile this driver as a module, choose M here: the	  module will be called viafb.config FB_NEOMAGIC	tristate "NeoMagic display support"	depends on FB && PCI	select FB_MODE_HELPERS	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select VGASTATE	help	  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.config FB_KYRO	tristate "IMG Kyro support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.config FB_3DFX	tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"	depends on FB && PCI	select FB_CFB_IMAGEBLIT	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	help	  This driver supports graphics boards with the 3Dfx Banshee,	  Voodoo3 or VSA-100 (aka Voodoo4/5) 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.config FB_3DFX_ACCEL	bool "3Dfx Acceleration functions (EXPERIMENTAL)"	depends on FB_3DFX && EXPERIMENTAL	---help---	This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer	device driver with acceleration functions.config FB_VOODOO1	tristate "3Dfx Voodoo Graphics (sst1) support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	---help---	  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/sstfb.txt> for supported	  options and other important info  support.config FB_VT8623	tristate "VIA VT8623 support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_TILEBLITTING	select FB_SVGALIB	select VGASTATE	select FONT_8x16 if FRAMEBUFFER_CONSOLE	---help---	  Driver for CastleRock integrated graphics core in the	  VIA VT8623 [Apollo CLE266] chipset.config FB_CYBLA	tristate "Cyberblade/i1 support"	depends on FB && PCI && X86_32 && !64BIT	select FB_CFB_IMAGEBLIT	---help---	  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.config FB_TRIDENT	tristate "Trident support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	---help---	  This is the frame buffer device driver for Trident PCI/AGP chipsets.	  Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D	  and Blade XP.	  There are also integrated versions of these chips called CyberXXXX,	  CyberImage or CyberBlade. These chips are mostly found in laptops	  but also on some motherboards. For more information, read	  <file:Documentation/fb/tridentfb.txt>	  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.config FB_TRIDENT_ACCEL	bool "Trident Acceleration functions (EXPERIMENTAL)"	depends on FB_TRIDENT && EXPERIMENTAL	---help---	This will compile the Trident frame buffer device with	acceleration functions.config FB_ARK	tristate "ARK 2000PV support"	depends on FB && PCI	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	select FB_TILEBLITTING	select FB_SVGALIB	select VGASTATE	select FONT_8x16 if FRAMEBUFFER_CONSOLE	---help---	  Driver for PCI graphics boards with ARK 2000PV chip	  and ICS 5342 RAMDAC.config FB_PM3	tristate "Permedia3 support (EXPERIMENTAL)"	depends on FB && PCI && EXPERIMENTAL	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.config FB_CARMINE	tristate "Fujitsu carmine frame buffer support"	depends on FB && PCI	select FB_CFB_FILLRECT