ia64/xen-unstable

changeset 8941:834e209cec9f

Add drivers/video/Kconfig to sparse tree.

Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
author cl349@firebug.cl.cam.ac.uk
date Mon Feb 20 18:02:55 2006 +0000 (2006-02-20)
parents 57af6b1cfa3a
children 9fa969af72cd
files linux-2.6-xen-sparse/drivers/video/Kconfig
line diff
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/linux-2.6-xen-sparse/drivers/video/Kconfig	Mon Feb 20 18:02:55 2006 +0000
     1.3 @@ -0,0 +1,1462 @@
     1.4 +#
     1.5 +# Video configuration
     1.6 +#
     1.7 +
     1.8 +menu "Graphics support"
     1.9 +
    1.10 +config FB
    1.11 +	tristate "Support for frame buffer devices"
    1.12 +	---help---
    1.13 +	  The frame buffer device provides an abstraction for the graphics
    1.14 +	  hardware. It represents the frame buffer of some video hardware and
    1.15 +	  allows application software to access the graphics hardware through
    1.16 +	  a well-defined interface, so the software doesn't need to know
    1.17 +	  anything about the low-level (hardware register) stuff.
    1.18 +
    1.19 +	  Frame buffer devices work identically across the different
    1.20 +	  architectures supported by Linux and make the implementation of
    1.21 +	  application programs easier and more portable; at this point, an X
    1.22 +	  server exists which uses the frame buffer device exclusively.
    1.23 +	  On several non-X86 architectures, the frame buffer device is the
    1.24 +	  only way to use the graphics hardware.
    1.25 +
    1.26 +	  The device is accessed through special device nodes, usually located
    1.27 +	  in the /dev directory, i.e. /dev/fb*.
    1.28 +
    1.29 +	  You need an utility program called fbset to make full use of frame
    1.30 +	  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
    1.31 +	  and the Framebuffer-HOWTO at
    1.32 +	  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
    1.33 +	  information.
    1.34 +
    1.35 +	  Say Y here and to the driver for your graphics board below if you
    1.36 +	  are compiling a kernel for a non-x86 architecture.
    1.37 +
    1.38 +	  If you are compiling for the x86 architecture, you can say Y if you
    1.39 +	  want to play with it, but it is not essential. Please note that
    1.40 +	  running graphical applications that directly touch the hardware
    1.41 +	  (e.g. an accelerated X server) and that are not frame buffer
    1.42 +	  device-aware may cause unexpected results. If unsure, say N.
    1.43 +
    1.44 +config FB_CFB_FILLRECT
    1.45 +	tristate
    1.46 +	depends on FB
    1.47 +	default n
    1.48 +	---help---
    1.49 +	  Include the cfb_fillrect function for generic software rectangle
    1.50 +	  filling. This is used by drivers that don't provide their own
    1.51 +	  (accelerated) version.
    1.52 +
    1.53 +config FB_CFB_COPYAREA
    1.54 +	tristate
    1.55 +	depends on FB
    1.56 +	default n
    1.57 +	---help---
    1.58 +	  Include the cfb_copyarea function for generic software area copying.
    1.59 +	  This is used by drivers that don't provide their own (accelerated)
    1.60 +	  version.
    1.61 +
    1.62 +config FB_CFB_IMAGEBLIT
    1.63 +	tristate
    1.64 +	depends on FB
    1.65 +	default n
    1.66 +	---help---
    1.67 +	  Include the cfb_imageblit function for generic software image
    1.68 +	  blitting. This is used by drivers that don't provide their own
    1.69 +	  (accelerated) version.
    1.70 +
    1.71 +config FB_MACMODES
    1.72 +       tristate
    1.73 +       depends on FB
    1.74 +       default n
    1.75 +
    1.76 +config FB_MODE_HELPERS
    1.77 +        bool "Enable Video Mode Handling Helpers"
    1.78 +        depends on FB
    1.79 +	default n
    1.80 +	---help---
    1.81 +	  This enables functions for handling video modes using the
    1.82 +	  Generalized Timing Formula and the EDID parser. A few drivers rely
    1.83 +          on this feature such as the radeonfb, rivafb, and the i810fb. If
    1.84 +	  your driver does not take advantage of this feature, choosing Y will
    1.85 +	  just increase the kernel size by about 5K.
    1.86 +
    1.87 +config FB_TILEBLITTING
    1.88 +       bool "Enable Tile Blitting Support"
    1.89 +       depends on FB
    1.90 +       default n
    1.91 +       ---help---
    1.92 +         This enables tile blitting.  Tile blitting is a drawing technique
    1.93 +	 where the screen is divided into rectangular sections (tiles), whereas
    1.94 +	 the standard blitting divides the screen into pixels. Because the
    1.95 +	 default drawing element is a tile, drawing functions will be passed
    1.96 +	 parameters in terms of number of tiles instead of number of pixels.
    1.97 +	 For example, to draw a single character, instead of using bitmaps,
    1.98 +	 an index to an array of bitmaps will be used.  To clear or move a
    1.99 +	 rectangular section of a screen, the rectangle will be described in
   1.100 +	 terms of number of tiles in the x- and y-axis.
   1.101 +
   1.102 +	 This is particularly important to one driver, matroxfb.  If
   1.103 +	 unsure, say N.
   1.104 +
   1.105 +config FB_CIRRUS
   1.106 +	tristate "Cirrus Logic support"
   1.107 +	depends on FB && (ZORRO || PCI)
   1.108 +	select FB_CFB_FILLRECT
   1.109 +	select FB_CFB_COPYAREA
   1.110 +	select FB_CFB_IMAGEBLIT
   1.111 +	---help---
   1.112 +	  This enables support for Cirrus Logic GD542x/543x based boards on
   1.113 +	  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
   1.114 +
   1.115 +	  If you have a PCI-based system, this enables support for these
   1.116 +	  chips: GD-543x, GD-544x, GD-5480.
   1.117 +
   1.118 +	  Please read the file <file:Documentation/fb/cirrusfb.txt>.
   1.119 +
   1.120 +	  Say N unless you have such a graphics board or plan to get one
   1.121 +	  before you next recompile the kernel.
   1.122 +
   1.123 +config FB_PM2
   1.124 +	tristate "Permedia2 support"
   1.125 +	depends on FB && ((AMIGA && BROKEN) || PCI)
   1.126 +	select FB_CFB_FILLRECT
   1.127 +	select FB_CFB_COPYAREA
   1.128 +	select FB_CFB_IMAGEBLIT
   1.129 +	help
   1.130 +	  This is the frame buffer device driver for the Permedia2 AGP frame
   1.131 +	  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
   1.132 +	  product page at
   1.133 +	  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
   1.134 +
   1.135 +config FB_PM2_FIFO_DISCONNECT
   1.136 +	bool "enable FIFO disconnect feature"
   1.137 +	depends on FB_PM2 && PCI
   1.138 +	help
   1.139 +	  Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
   1.140 +
   1.141 +config FB_ARMCLCD
   1.142 +	tristate "ARM PrimeCell PL110 support"
   1.143 +	depends on FB && ARM && ARM_AMBA
   1.144 +	select FB_CFB_FILLRECT
   1.145 +	select FB_CFB_COPYAREA
   1.146 +	select FB_CFB_IMAGEBLIT
   1.147 +	help
   1.148 +	  This framebuffer device driver is for the ARM PrimeCell PL110
   1.149 +	  Colour LCD controller.  ARM PrimeCells provide the building
   1.150 +	  blocks for System on a Chip devices.
   1.151 +
   1.152 +	  If you want to compile this as a module (=code which can be
   1.153 +	  inserted into and removed from the running kernel), say M
   1.154 +	  here and read <file:Documentation/modules.txt>.  The module
   1.155 +	  will be called amba-clcd.
   1.156 +
   1.157 +config FB_ACORN
   1.158 +	bool "Acorn VIDC support"
   1.159 +	depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
   1.160 +	select FB_CFB_FILLRECT
   1.161 +	select FB_CFB_COPYAREA
   1.162 +	select FB_CFB_IMAGEBLIT
   1.163 +	help
   1.164 +	  This is the frame buffer device driver for the Acorn VIDC graphics
   1.165 +	  hardware found in Acorn RISC PCs and other ARM-based machines.  If
   1.166 +	  unsure, say N.
   1.167 +
   1.168 +config FB_CLPS711X
   1.169 +	bool "CLPS711X LCD support"
   1.170 +	depends on (FB = y) && ARM && ARCH_CLPS711X
   1.171 +	select FB_CFB_FILLRECT
   1.172 +	select FB_CFB_COPYAREA
   1.173 +	select FB_CFB_IMAGEBLIT
   1.174 +	help
   1.175 +	  Say Y to enable the Framebuffer driver for the CLPS7111 and
   1.176 +	  EP7212 processors.
   1.177 +
   1.178 +config FB_SA1100
   1.179 +	bool "SA-1100 LCD support"
   1.180 +	depends on (FB = y) && ARM && ARCH_SA1100
   1.181 +	select FB_CFB_FILLRECT
   1.182 +	select FB_CFB_COPYAREA
   1.183 +	select FB_CFB_IMAGEBLIT
   1.184 +	help
   1.185 +	  This is a framebuffer device for the SA-1100 LCD Controller.
   1.186 +	  See <http://www.linux-fbdev.org/> for information on framebuffer
   1.187 +	  devices.
   1.188 +
   1.189 +	  If you plan to use the LCD display with your SA-1100 system, say
   1.190 +	  Y here.
   1.191 +
   1.192 +config FB_IMX
   1.193 +	tristate "Motorola i.MX LCD support"
   1.194 +	depends on FB && ARM && ARCH_IMX
   1.195 +	select FB_CFB_FILLRECT
   1.196 +	select FB_CFB_COPYAREA
   1.197 +	select FB_CFB_IMAGEBLIT
   1.198 +
   1.199 +config FB_CYBER2000
   1.200 +	tristate "CyberPro 2000/2010/5000 support"
   1.201 +	depends on FB && PCI && (BROKEN || !SPARC64)
   1.202 +	select FB_CFB_FILLRECT
   1.203 +	select FB_CFB_COPYAREA
   1.204 +	select FB_CFB_IMAGEBLIT
   1.205 +	help
   1.206 +	  This enables support for the Integraphics CyberPro 20x0 and 5000
   1.207 +	  VGA chips used in the Rebel.com Netwinder and other machines.
   1.208 +	  Say Y if you have a NetWinder or a graphics card containing this
   1.209 +	  device, otherwise say N.
   1.210 +
   1.211 +config FB_APOLLO
   1.212 +	bool
   1.213 +	depends on (FB = y) && APOLLO
   1.214 +	default y
   1.215 +	select FB_CFB_FILLRECT
   1.216 +	select FB_CFB_IMAGEBLIT
   1.217 +
   1.218 +config FB_Q40
   1.219 +	bool
   1.220 +	depends on (FB = y) && Q40
   1.221 +	default y
   1.222 +	select FB_CFB_FILLRECT
   1.223 +	select FB_CFB_COPYAREA
   1.224 +	select FB_CFB_IMAGEBLIT
   1.225 +
   1.226 +config FB_AMIGA
   1.227 +	tristate "Amiga native chipset support"
   1.228 +	depends on FB && AMIGA
   1.229 +	help
   1.230 +	  This is the frame buffer device driver for the builtin graphics
   1.231 +	  chipset found in Amigas.
   1.232 +
   1.233 +	  To compile this driver as a module, choose M here: the
   1.234 +	  module will be called amifb.
   1.235 +
   1.236 +config FB_AMIGA_OCS
   1.237 +	bool "Amiga OCS chipset support"
   1.238 +	depends on FB_AMIGA
   1.239 +	help
   1.240 +	  This enables support for the original Agnus and Denise video chips,
   1.241 +	  found in the Amiga 1000 and most A500's and A2000's. If you intend
   1.242 +	  to run Linux on any of these systems, say Y; otherwise say N.
   1.243 +
   1.244 +config FB_AMIGA_ECS
   1.245 +	bool "Amiga ECS chipset support"
   1.246 +	depends on FB_AMIGA
   1.247 +	help
   1.248 +	  This enables support for the Enhanced Chip Set, found in later
   1.249 +	  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
   1.250 +	  you intend to run Linux on any of these systems, say Y; otherwise
   1.251 +	  say N.
   1.252 +
   1.253 +config FB_AMIGA_AGA
   1.254 +	bool "Amiga AGA chipset support"
   1.255 +	depends on FB_AMIGA
   1.256 +	help
   1.257 +	  This enables support for the Advanced Graphics Architecture (also
   1.258 +	  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
   1.259 +	  and CD32. If you intend to run Linux on any of these systems, say Y;
   1.260 +	  otherwise say N.
   1.261 +
   1.262 +config FB_CYBER
   1.263 +	tristate "Amiga CyberVision 64 support"
   1.264 +	depends on FB && ZORRO && BROKEN
   1.265 +	select FB_CFB_FILLRECT
   1.266 +	select FB_CFB_COPYAREA
   1.267 +	select FB_CFB_IMAGEBLIT
   1.268 +	help
   1.269 +	  This enables support for the Cybervision 64 graphics card from
   1.270 +	  Phase5. Please note that its use is not all that intuitive (i.e. if
   1.271 +	  you have any questions, be sure to ask!). Say N unless you have a
   1.272 +	  Cybervision 64 or plan to get one before you next recompile the
   1.273 +	  kernel. Please note that this driver DOES NOT support the
   1.274 +	  Cybervision 64/3D card, as they use incompatible video chips.
   1.275 +
   1.276 +config FB_VIRGE
   1.277 +	bool "Amiga CyberVision 64/3D support "
   1.278 +	depends on (FB = y) && ZORRO && BROKEN
   1.279 +	select FB_CFB_FILLRECT
   1.280 +	select FB_CFB_COPYAREA
   1.281 +	select FB_CFB_IMAGEBLIT
   1.282 +	help
   1.283 +	  This enables support for the Cybervision 64/3D graphics card from
   1.284 +	  Phase5. Please note that its use is not all that intuitive (i.e. if
   1.285 +	  you have any questions, be sure to ask!). Say N unless you have a
   1.286 +	  Cybervision 64/3D or plan to get one before you next recompile the
   1.287 +	  kernel. Please note that this driver DOES NOT support the older
   1.288 +	  Cybervision 64 card, as they use incompatible video chips.
   1.289 +
   1.290 +config FB_RETINAZ3
   1.291 +	tristate "Amiga Retina Z3 support"
   1.292 +	depends on (FB = y) && ZORRO && BROKEN
   1.293 +	help
   1.294 +	  This enables support for the Retina Z3 graphics card. Say N unless
   1.295 +	  you have a Retina Z3 or plan to get one before you next recompile
   1.296 +	  the kernel.
   1.297 +
   1.298 +config FB_FM2
   1.299 +	bool "Amiga FrameMaster II/Rainbow II support"
   1.300 +	depends on (FB = y) && ZORRO
   1.301 +	select FB_CFB_FILLRECT
   1.302 +	select FB_CFB_COPYAREA
   1.303 +	select FB_CFB_IMAGEBLIT
   1.304 +	help
   1.305 +	  This is the frame buffer device driver for the Amiga FrameMaster
   1.306 +	  card from BSC (exhibited 1992 but not shipped as a CBM product).
   1.307 +
   1.308 +config FB_ARC
   1.309 +	tristate "Arc Monochrome LCD board support"
   1.310 +	depends on FB && X86
   1.311 +	select FB_CFB_FILLRECT
   1.312 +	select FB_CFB_COPYAREA
   1.313 +	select FB_CFB_IMAGEBLIT
   1.314 +	help
   1.315 +	  This enables support for the Arc Monochrome LCD board. The board
   1.316 +	  is based on the KS-108 lcd controller and is typically a matrix
   1.317 +	  of 2*n chips. This driver was tested with a 128x64 panel. This
   1.318 +	  driver supports it for use with x86 SBCs through a 16 bit GPIO
   1.319 +	  interface (8 bit data, 8 bit control). If you anticpate using
   1.320 +	  this driver, say Y or M; otherwise say N. You must specify the
   1.321 +	  GPIO IO address to be used for setting control and data.
   1.322 +
   1.323 +config FB_ATARI
   1.324 +	bool "Atari native chipset support"
   1.325 +	depends on (FB = y) && ATARI && BROKEN
   1.326 +	help
   1.327 +	  This is the frame buffer device driver for the builtin graphics
   1.328 +	  chipset found in Ataris.
   1.329 +
   1.330 +config FB_OF
   1.331 +	bool "Open Firmware frame buffer device support"
   1.332 +	depends on (FB = y) && (PPC64 || PPC_OF)
   1.333 +	select FB_CFB_FILLRECT
   1.334 +	select FB_CFB_COPYAREA
   1.335 +	select FB_CFB_IMAGEBLIT
   1.336 +	select FB_MACMODES
   1.337 +	help
   1.338 +	  Say Y if you want support with Open Firmware for your graphics
   1.339 +	  board.
   1.340 +
   1.341 +config FB_CONTROL
   1.342 +	bool "Apple \"control\" display support"
   1.343 +	depends on (FB = y) && PPC_PMAC
   1.344 +	select FB_CFB_FILLRECT
   1.345 +	select FB_CFB_COPYAREA
   1.346 +	select FB_CFB_IMAGEBLIT
   1.347 +	select FB_MACMODES
   1.348 +	help
   1.349 +	  This driver supports a frame buffer for the graphics adapter in the
   1.350 +	  Power Macintosh 7300 and others.
   1.351 +
   1.352 +config FB_PLATINUM
   1.353 +	bool "Apple \"platinum\" display support"
   1.354 +	depends on (FB = y) && PPC_PMAC
   1.355 +	select FB_CFB_FILLRECT
   1.356 +	select FB_CFB_COPYAREA
   1.357 +	select FB_CFB_IMAGEBLIT
   1.358 +	select FB_MACMODES
   1.359 +	help
   1.360 +	  This driver supports a frame buffer for the "platinum" graphics
   1.361 +	  adapter in some Power Macintoshes.
   1.362 +
   1.363 +config FB_VALKYRIE
   1.364 +	bool "Apple \"valkyrie\" display support"
   1.365 +	depends on (FB = y) && (MAC || PPC_PMAC)
   1.366 +	select FB_CFB_FILLRECT
   1.367 +	select FB_CFB_COPYAREA
   1.368 +	select FB_CFB_IMAGEBLIT
   1.369 +	select FB_MACMODES
   1.370 +	help
   1.371 +	  This driver supports a frame buffer for the "valkyrie" graphics
   1.372 +	  adapter in some Power Macintoshes.
   1.373 +
   1.374 +config FB_CT65550
   1.375 +	bool "Chips 65550 display support"
   1.376 +	depends on (FB = y) && PPC
   1.377 +	select FB_CFB_FILLRECT
   1.378 +	select FB_CFB_COPYAREA
   1.379 +	select FB_CFB_IMAGEBLIT
   1.380 +	help
   1.381 +	  This is the frame buffer device driver for the Chips & Technologies
   1.382 +	  65550 graphics chip in PowerBooks.
   1.383 +
   1.384 +config FB_ASILIANT
   1.385 +	bool "Asiliant (Chips) 69000 display support"
   1.386 +	depends on (FB = y) && PCI
   1.387 +	select FB_CFB_FILLRECT
   1.388 +	select FB_CFB_COPYAREA
   1.389 +	select FB_CFB_IMAGEBLIT
   1.390 +
   1.391 +config FB_IMSTT
   1.392 +	bool "IMS Twin Turbo display support"
   1.393 +	depends on (FB = y) && PCI
   1.394 +	select FB_CFB_IMAGEBLIT
   1.395 +	select FB_MACMODES if PPC
   1.396 +	help
   1.397 +	  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
   1.398 +	  many Macintosh and compatible computers.
   1.399 +
   1.400 +config FB_VGA16
   1.401 +	tristate "VGA 16-color graphics support"
   1.402 +	depends on FB && (X86 || PPC)
   1.403 +	select FB_CFB_FILLRECT
   1.404 +	select FB_CFB_COPYAREA
   1.405 +	select FB_CFB_IMAGEBLIT
   1.406 +	help
   1.407 +	  This is the frame buffer device driver for VGA 16 color graphic
   1.408 +	  cards. Say Y if you have such a card.
   1.409 +
   1.410 +	  To compile this driver as a module, choose M here: the
   1.411 +	  module will be called vga16fb.
   1.412 +
   1.413 +config FB_STI
   1.414 +	tristate "HP STI frame buffer device support"
   1.415 +	depends on FB && PARISC
   1.416 +	select FB_CFB_FILLRECT
   1.417 +	select FB_CFB_COPYAREA
   1.418 +	select FB_CFB_IMAGEBLIT
   1.419 +	default y
   1.420 +	---help---
   1.421 +	  STI refers to the HP "Standard Text Interface" which is a set of
   1.422 +	  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
   1.423 +	  Enabling this option will implement the linux framebuffer device
   1.424 +	  using calls to the STI BIOS routines for initialisation.
   1.425 +	
   1.426 +	  If you enable this option, you will get a planar framebuffer device
   1.427 +	  /dev/fb which will work on the most common HP graphic cards of the
   1.428 +	  NGLE family, including the artist chips (in the 7xx and Bxxx series),
   1.429 +	  HCRX, HCRX24, CRX, CRX24 and VisEG series.
   1.430 +
   1.431 +	  It is safe to enable this option, so you should probably say "Y".
   1.432 +
   1.433 +config FB_MAC
   1.434 +	bool "Generic Macintosh display support"
   1.435 +	depends on (FB = y) && MAC
   1.436 +	select FB_CFB_FILLRECT
   1.437 +	select FB_CFB_COPYAREA
   1.438 +	select FB_CFB_IMAGEBLIT
   1.439 +	select FB_MACMODES
   1.440 +
   1.441 +#      bool '  Apple DAFB display support' CONFIG_FB_DAFB
   1.442 +config FB_HP300
   1.443 +	bool
   1.444 +	depends on (FB = y) && HP300
   1.445 +	select FB_CFB_FILLRECT
   1.446 +	select FB_CFB_IMAGEBLIT
   1.447 +	default y
   1.448 +
   1.449 +config FB_TGA
   1.450 +	tristate "TGA framebuffer support"
   1.451 +	depends on FB && ALPHA
   1.452 +	select FB_CFB_FILLRECT
   1.453 +	select FB_CFB_COPYAREA
   1.454 +	select FB_CFB_IMAGEBLIT
   1.455 +	help
   1.456 +	  This is the frame buffer device driver for generic TGA graphic
   1.457 +	  cards. Say Y if you have one of those.
   1.458 +
   1.459 +config FB_VESA
   1.460 +	bool "VESA VGA graphics support"
   1.461 +	depends on (FB = y) && X86
   1.462 +	select FB_CFB_FILLRECT
   1.463 +	select FB_CFB_COPYAREA
   1.464 +	select FB_CFB_IMAGEBLIT
   1.465 +	help
   1.466 +	  This is the frame buffer device driver for generic VESA 2.0
   1.467 +	  compliant graphic cards. The older VESA 1.2 cards are not supported.
   1.468 +	  You will get a boot time penguin logo at no additional cost. Please
   1.469 +	  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
   1.470 +
   1.471 +config VIDEO_SELECT
   1.472 +	bool
   1.473 +	depends on FB_VESA
   1.474 +	default y
   1.475 +
   1.476 +config FB_HGA
   1.477 +	tristate "Hercules mono graphics support"
   1.478 +	depends on FB && X86
   1.479 +	select FB_CFB_FILLRECT
   1.480 +	select FB_CFB_COPYAREA
   1.481 +	select FB_CFB_IMAGEBLIT
   1.482 +	help
   1.483 +	  Say Y here if you have a Hercules mono graphics card.
   1.484 +
   1.485 +	  To compile this driver as a module, choose M here: the
   1.486 +	  module will be called hgafb.
   1.487 +
   1.488 +	  As this card technology is 15 years old, most people will answer N
   1.489 +	  here.
   1.490 +
   1.491 +config FB_HGA_ACCEL
   1.492 +	bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
   1.493 +	depends on FB_HGA && EXPERIMENTAL
   1.494 +	---help---
   1.495 +	This will compile the Hercules mono graphics with
   1.496 +	acceleration functions.
   1.497 +
   1.498 +
   1.499 +config VIDEO_SELECT
   1.500 +	bool
   1.501 +	depends on (FB = y) && X86
   1.502 +	default y
   1.503 +
   1.504 +config FB_SGIVW
   1.505 +	tristate "SGI Visual Workstation framebuffer support"
   1.506 +	depends on FB && X86_VISWS
   1.507 +	select FB_CFB_FILLRECT
   1.508 +	select FB_CFB_COPYAREA
   1.509 +	select FB_CFB_IMAGEBLIT
   1.510 +	help
   1.511 +	  SGI Visual Workstation support for framebuffer graphics.
   1.512 +
   1.513 +config FB_GBE
   1.514 +	bool "SGI Graphics Backend frame buffer support"
   1.515 +	depends on (FB = y) && (SGI_IP32 || X86_VISWS)
   1.516 +	select FB_CFB_FILLRECT
   1.517 +	select FB_CFB_COPYAREA
   1.518 +	select FB_CFB_IMAGEBLIT
   1.519 + 	help
   1.520 +	  This is the frame buffer device driver for SGI Graphics Backend.
   1.521 +	  This chip is used in SGI O2 and Visual Workstation 320/540.
   1.522 +
   1.523 +config FB_GBE_MEM
   1.524 +	int "Video memory size in MB"
   1.525 +	depends on FB_GBE
   1.526 +	default 8
   1.527 +	help
   1.528 +	  This is the amount of memory reserved for the framebuffer,
   1.529 +	  which can be any value between 1MB and 8MB.
   1.530 +
   1.531 +config FB_SUN3
   1.532 +	bool "Sun3 framebuffer support"
   1.533 +	depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
   1.534 +
   1.535 +config FB_SBUS
   1.536 +	bool "SBUS and UPA framebuffers"
   1.537 +	depends on (FB = y) && SPARC
   1.538 +	help
   1.539 +	  Say Y if you want support for SBUS or UPA based frame buffer device.
   1.540 +
   1.541 +config FB_BW2
   1.542 +	bool "BWtwo support"
   1.543 +	depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
   1.544 +	select FB_CFB_FILLRECT
   1.545 +	select FB_CFB_COPYAREA
   1.546 +	select FB_CFB_IMAGEBLIT
   1.547 +	help
   1.548 +	  This is the frame buffer device driver for the BWtwo frame buffer.
   1.549 +
   1.550 +config FB_CG3
   1.551 +	bool "CGthree support"
   1.552 +	depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
   1.553 +	select FB_CFB_FILLRECT
   1.554 +	select FB_CFB_COPYAREA
   1.555 +	select FB_CFB_IMAGEBLIT
   1.556 +	help
   1.557 +	  This is the frame buffer device driver for the CGthree frame buffer.
   1.558 +
   1.559 +config FB_CG6
   1.560 +	bool "CGsix (GX,TurboGX) support"
   1.561 +	depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
   1.562 +	select FB_CFB_COPYAREA
   1.563 +	select FB_CFB_IMAGEBLIT
   1.564 +	help
   1.565 +	  This is the frame buffer device driver for the CGsix (GX, TurboGX)
   1.566 +	  frame buffer.
   1.567 +
   1.568 +config FB_PVR2
   1.569 +	tristate "NEC PowerVR 2 display support"
   1.570 +	depends on FB && SH_DREAMCAST
   1.571 +	select FB_CFB_FILLRECT
   1.572 +	select FB_CFB_COPYAREA
   1.573 +	select FB_CFB_IMAGEBLIT
   1.574 +	---help---
   1.575 +	  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
   1.576 +	  run linux on your Dreamcast, you will have to say Y here.
   1.577 +	  This driver may or may not work on other PowerVR 2 cards, but is
   1.578 +	  totally untested.  Use at your own risk.  If unsure, say N.
   1.579 +
   1.580 +	  To compile this driver as a module, choose M here: the
   1.581 +	  module will be called pvr2fb.
   1.582 +
   1.583 +	  You can pass several parameters to the driver at boot time or at
   1.584 +	  module load time.  The parameters look like "video=pvr2:XXX", where
   1.585 +	  the meaning of XXX can be found at the end of the main source file
   1.586 +	  (<file:drivers/video/pvr2fb.c>). Please see the file
   1.587 +	  <file:Documentation/fb/pvr2fb.txt>.
   1.588 +
   1.589 +config FB_EPSON1355
   1.590 +	bool "Epson 1355 framebuffer support"
   1.591 +	depends on (FB = y) && (SUPERH || ARCH_CEIVA)
   1.592 +	select FB_CFB_FILLRECT
   1.593 +	select FB_CFB_COPYAREA
   1.594 +	select FB_CFB_IMAGEBLIT
   1.595 +	help
   1.596 +	  Build in support for the SED1355 Epson Research Embedded RAMDAC
   1.597 +	  LCD/CRT Controller (since redesignated as the S1D13505) as a
   1.598 +	  framebuffer.  Product specs at
   1.599 +	  <http://www.erd.epson.com/vdc/html/products.htm>.
   1.600 +
   1.601 +config FB_S1D13XXX
   1.602 +	tristate "Epson S1D13XXX framebuffer support"
   1.603 +	depends on FB
   1.604 +	select FB_CFB_FILLRECT
   1.605 +	select FB_CFB_COPYAREA
   1.606 +	select FB_CFB_IMAGEBLIT
   1.607 +	help
   1.608 +	  Support for S1D13XXX framebuffer device family (currently only
   1.609 +	  working with S1D13806). Product specs at
   1.610 +	  <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
   1.611 +
   1.612 +config FB_NVIDIA
   1.613 +	tristate "nVidia Framebuffer Support"
   1.614 +	depends on FB && PCI
   1.615 +	select I2C_ALGOBIT if FB_NVIDIA_I2C
   1.616 +	select I2C if FB_NVIDIA_I2C
   1.617 +	select FB_MODE_HELPERS
   1.618 +	select FB_CFB_FILLRECT
   1.619 +	select FB_CFB_COPYAREA
   1.620 +	select FB_CFB_IMAGEBLIT
   1.621 +	help
   1.622 +	  This driver supports graphics boards with the nVidia chips, TNT
   1.623 +	  and newer. For very old chipsets, such as the RIVA128, then use
   1.624 +	  the rivafb.
   1.625 +	  Say Y if you have such a graphics board.
   1.626 +
   1.627 +	  To compile this driver as a module, choose M here: the
   1.628 +	  module will be called nvidiafb.
   1.629 +
   1.630 +config FB_NVIDIA_I2C
   1.631 +       bool "Enable DDC Support"
   1.632 +       depends on FB_NVIDIA
   1.633 +       help
   1.634 +	  This enables I2C support for nVidia Chipsets.  This is used
   1.635 +	  only for getting EDID information from the attached display
   1.636 +	  allowing for robust video mode handling and switching.
   1.637 +
   1.638 +	  Because fbdev-2.6 requires that drivers must be able to
   1.639 +	  independently validate video mode parameters, you should say Y
   1.640 +	  here.
   1.641 +
   1.642 +config FB_RIVA
   1.643 +	tristate "nVidia Riva support"
   1.644 +	depends on FB && PCI
   1.645 +	select I2C_ALGOBIT if FB_RIVA_I2C
   1.646 +	select I2C if FB_RIVA_I2C
   1.647 +	select FB_MODE_HELPERS
   1.648 +	select FB_CFB_FILLRECT
   1.649 +	select FB_CFB_COPYAREA
   1.650 +	select FB_CFB_IMAGEBLIT
   1.651 +	help
   1.652 +	  This driver supports graphics boards with the nVidia Riva/Geforce
   1.653 +	  chips.
   1.654 +	  Say Y if you have such a graphics board.
   1.655 +
   1.656 +	  To compile this driver as a module, choose M here: the
   1.657 +	  module will be called rivafb.
   1.658 +
   1.659 +config FB_RIVA_I2C
   1.660 +       bool "Enable DDC Support"
   1.661 +       depends on FB_RIVA
   1.662 +       help
   1.663 +	  This enables I2C support for nVidia Chipsets.  This is used
   1.664 +	  only for getting EDID information from the attached display
   1.665 +	  allowing for robust video mode handling and switching.
   1.666 +
   1.667 +	  Because fbdev-2.6 requires that drivers must be able to
   1.668 +	  independently validate video mode parameters, you should say Y
   1.669 +	  here.
   1.670 +
   1.671 +config FB_RIVA_DEBUG
   1.672 +	bool "Lots of debug output from Riva(nVidia) driver"
   1.673 +	depends on FB_RIVA
   1.674 +	default n
   1.675 +	help
   1.676 +	  Say Y here if you want the Riva driver to output all sorts
   1.677 +	  of debugging informations to provide to the maintainer when
   1.678 +	  something goes wrong.
   1.679 +
   1.680 +config FB_I810
   1.681 +	tristate "Intel 810/815 support (EXPERIMENTAL)"
   1.682 +	depends on FB && EXPERIMENTAL && PCI && X86_32
   1.683 +	select AGP
   1.684 +	select AGP_INTEL
   1.685 +	select FB_MODE_HELPERS
   1.686 +	select FB_CFB_FILLRECT
   1.687 +	select FB_CFB_COPYAREA
   1.688 +	select FB_CFB_IMAGEBLIT
   1.689 +	help
   1.690 +	  This driver supports the on-board graphics built in to the Intel 810 
   1.691 +          and 815 chipsets.  Say Y if you have and plan to use such a board.
   1.692 +
   1.693 +          To compile this driver as a module, choose M here: the
   1.694 +	  module will be called i810fb.
   1.695 +
   1.696 +          For more information, please read 
   1.697 +	  <file:Documentation/fb/intel810.txt>
   1.698 +
   1.699 +config FB_I810_GTF
   1.700 +	bool "use VESA Generalized Timing Formula"
   1.701 +	depends on FB_I810
   1.702 +	help
   1.703 +	  If you say Y, then the VESA standard, Generalized Timing Formula 
   1.704 +          or GTF, will be used to calculate the required video timing values
   1.705 +	  per video mode.  Since the GTF allows nondiscrete timings 
   1.706 +          (nondiscrete being a range of values as opposed to discrete being a
   1.707 +          set of values), you'll be able to use any combination of horizontal 
   1.708 +	  and vertical resolutions, and vertical refresh rates without having
   1.709 +	  to specify your own timing parameters.  This is especially useful
   1.710 +	  to maximize the performance of an aging display, or if you just 
   1.711 +          have a display with nonstandard dimensions. A VESA compliant 
   1.712 +	  monitor is recommended, but can still work with non-compliant ones.
   1.713 +	  If you need or want this, then select this option. The timings may 
   1.714 +	  not be compliant with Intel's recommended values. Use at your own 
   1.715 +	  risk.
   1.716 +
   1.717 +          If you say N, the driver will revert to discrete video timings 
   1.718 +	  using a set recommended by Intel in their documentation.
   1.719 +  
   1.720 +          If unsure, say N.
   1.721 +
   1.722 +config FB_I810_I2C
   1.723 +	bool "Enable DDC Support"
   1.724 +	depends on FB_I810 && FB_I810_GTF
   1.725 +	select I2C
   1.726 +	select I2C_ALGOBIT
   1.727 +	help
   1.728 +
   1.729 +config FB_INTEL
   1.730 +	tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
   1.731 +	depends on FB && EXPERIMENTAL && PCI && X86_32
   1.732 +	select AGP
   1.733 +	select AGP_INTEL
   1.734 +	select FB_MODE_HELPERS
   1.735 +	select FB_CFB_FILLRECT
   1.736 +	select FB_CFB_COPYAREA
   1.737 +	select FB_CFB_IMAGEBLIT
   1.738 +	help
   1.739 +	  This driver supports the on-board graphics built in to the Intel
   1.740 +          830M/845G/852GM/855GM/865G chipsets.
   1.741 +          Say Y if you have and plan to use such a board.
   1.742 +
   1.743 +          To compile this driver as a module, choose M here: the
   1.744 +	  module will be called intelfb.
   1.745 +
   1.746 +config FB_INTEL_DEBUG
   1.747 +        bool "Intel driver Debug Messages"
   1.748 +	depends on FB_INTEL
   1.749 +	---help---
   1.750 +	  Say Y here if you want the Intel driver to output all sorts
   1.751 +	  of debugging informations to provide to the maintainer when
   1.752 +	  something goes wrong.
   1.753 +
   1.754 +config FB_MATROX
   1.755 +	tristate "Matrox acceleration"
   1.756 +	depends on FB && PCI
   1.757 +	select FB_CFB_FILLRECT
   1.758 +	select FB_CFB_COPYAREA
   1.759 +	select FB_CFB_IMAGEBLIT
   1.760 +	select FB_TILEBLITTING
   1.761 +	select FB_MACMODES if PPC_PMAC
   1.762 +	---help---
   1.763 +	  Say Y here if you have a Matrox Millennium, Matrox Millennium II,
   1.764 +	  Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
   1.765 +	  Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
   1.766 +	  Matrox G400, G450 or G550 card in your box.
   1.767 +
   1.768 +	  To compile this driver as a module, choose M here: the
   1.769 +	  module will be called matroxfb.
   1.770 +
   1.771 +	  You can pass several parameters to the driver at boot time or at
   1.772 +	  module load time. The parameters look like "video=matrox:XXX", and
   1.773 +	  are described in <file:Documentation/fb/matroxfb.txt>.
   1.774 +
   1.775 +config FB_MATROX_MILLENIUM
   1.776 +	bool "Millennium I/II support"
   1.777 +	depends on FB_MATROX
   1.778 +	help
   1.779 +	  Say Y here if you have a Matrox Millennium or Matrox Millennium II
   1.780 +	  video card. If you select "Advanced lowlevel driver options" below,
   1.781 +	  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
   1.782 +	  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
   1.783 +	  also use font widths different from 8.
   1.784 +
   1.785 +config FB_MATROX_MYSTIQUE
   1.786 +	bool "Mystique support"
   1.787 +	depends on FB_MATROX
   1.788 +	help
   1.789 +	  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
   1.790 +	  video card. If you select "Advanced lowlevel driver options" below,
   1.791 +	  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
   1.792 +	  packed pixel and 32 bpp packed pixel. You can also use font widths
   1.793 +	  different from 8.
   1.794 +
   1.795 +config FB_MATROX_G
   1.796 +	bool "G100/G200/G400/G450/G550 support"
   1.797 +	depends on FB_MATROX
   1.798 +	---help---
   1.799 +	  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
   1.800 +	  video card. If you select "Advanced lowlevel driver options", you
   1.801 +	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
   1.802 +	  pixel and 32 bpp packed pixel. You can also use font widths
   1.803 +	  different from 8.
   1.804 +
   1.805 +	  If you need support for G400 secondary head, you must first say Y to
   1.806 +	  "I2C support" in the character devices section, and then to
   1.807 +	  "Matrox I2C support" and "G400 second head support" here in the
   1.808 +	  framebuffer section. G450/G550 secondary head and digital output
   1.809 +	  are supported without additional modules.
   1.810 +
   1.811 +	  The driver starts in monitor mode. You must use the matroxset tool 
   1.812 +	  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 
   1.813 +	  swap primary and secondary head outputs, or to change output mode.  
   1.814 +	  Secondary head driver always start in 640x480 resolution and you 
   1.815 +	  must use fbset to change it.
   1.816 +
   1.817 +	  Do not forget that second head supports only 16 and 32 bpp
   1.818 +	  packed pixels, so it is a good idea to compile them into the kernel
   1.819 +	  too. You can use only some font widths, as the driver uses generic
   1.820 +	  painting procedures (the secondary head does not use acceleration
   1.821 +	  engine).
   1.822 +
   1.823 +	  G450/G550 hardware can display TV picture only from secondary CRTC,
   1.824 +	  and it performs no scaling, so picture must have 525 or 625 lines.
   1.825 +
   1.826 +config FB_MATROX_I2C
   1.827 +	tristate "Matrox I2C support"
   1.828 +	depends on FB_MATROX && I2C
   1.829 +	select I2C_ALGOBIT
   1.830 +	---help---
   1.831 +	  This drivers creates I2C buses which are needed for accessing the
   1.832 +	  DDC (I2C) bus present on all Matroxes, an I2C bus which
   1.833 +	  interconnects Matrox optional devices, like MGA-TVO on G200 and
   1.834 +	  G400, and the secondary head DDC bus, present on G400 only.
   1.835 +
   1.836 +	  You can say Y or M here if you want to experiment with monitor
   1.837 +	  detection code. You must say Y or M here if you want to use either
   1.838 +	  second head of G400 or MGA-TVO on G200 or G400.
   1.839 +
   1.840 +	  If you compile it as module, it will create a module named
   1.841 +	  i2c-matroxfb.
   1.842 +
   1.843 +config FB_MATROX_MAVEN
   1.844 +	tristate "G400 second head support"
   1.845 +	depends on FB_MATROX_G && FB_MATROX_I2C
   1.846 +	---help---
   1.847 +	  WARNING !!! This support does not work with G450 !!!
   1.848 +
   1.849 +	  Say Y or M here if you want to use a secondary head (meaning two
   1.850 +	  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
   1.851 +	  head is not compatible with accelerated XFree 3.3.x SVGA servers -
   1.852 +	  secondary head output is blanked while you are in X. With XFree
   1.853 +	  3.9.17 preview you can use both heads if you use SVGA over fbdev or
   1.854 +	  the fbdev driver on first head and the fbdev driver on second head.
   1.855 +
   1.856 +	  If you compile it as module, two modules are created,
   1.857 +	  matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
   1.858 +	  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
   1.859 +	  also load i2c-matroxfb to get it to run.
   1.860 +
   1.861 +	  The driver starts in monitor mode and you must use the matroxset
   1.862 +	  tool (available at
   1.863 +	  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
   1.864 +	  PAL or NTSC or to swap primary and secondary head outputs.
   1.865 +	  Secondary head driver also always start in 640x480 resolution, you
   1.866 +	  must use fbset to change it.
   1.867 +
   1.868 +	  Also do not forget that second head supports only 16 and 32 bpp
   1.869 +	  packed pixels, so it is a good idea to compile them into the kernel
   1.870 +	  too.  You can use only some font widths, as the driver uses generic
   1.871 +	  painting procedures (the secondary head does not use acceleration
   1.872 +	  engine).
   1.873 +
   1.874 +config FB_MATROX_MULTIHEAD
   1.875 +	bool "Multihead support"
   1.876 +	depends on FB_MATROX
   1.877 +	---help---
   1.878 +	  Say Y here if you have more than one (supported) Matrox device in
   1.879 +	  your computer and you want to use all of them for different monitors
   1.880 +	  ("multihead"). If you have only one device, you should say N because
   1.881 +	  the driver compiled with Y is larger and a bit slower, especially on
   1.882 +	  ia32 (ix86).
   1.883 +
   1.884 +	  If you said M to "Matrox unified accelerated driver" and N here, you
   1.885 +	  will still be able to use several Matrox devices simultaneously:
   1.886 +	  insert several instances of the module matroxfb into the kernel
   1.887 +	  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
   1.888 +	  for the different Matrox devices. This method is slightly faster but
   1.889 +	  uses 40 KB of kernel memory per Matrox card.
   1.890 +
   1.891 +	  There is no need for enabling 'Matrox multihead support' if you have
   1.892 +	  only one Matrox card in the box.
   1.893 +
   1.894 +config FB_RADEON_OLD
   1.895 +	tristate "ATI Radeon display support (Old driver)"
   1.896 +	depends on FB && PCI
   1.897 +	select FB_CFB_FILLRECT
   1.898 +	select FB_CFB_COPYAREA
   1.899 +	select FB_CFB_IMAGEBLIT
   1.900 +	select FB_MACMODES if PPC
   1.901 +	help
   1.902 +	  Choose this option if you want to use an ATI Radeon graphics card as
   1.903 +	  a framebuffer device.  There are both PCI and AGP versions.  You
   1.904 +	  don't need to choose this to run the Radeon in plain VGA mode.
   1.905 +	  There is a product page at
   1.906 +	  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
   1.907 +
   1.908 +config FB_RADEON
   1.909 +	tristate "ATI Radeon display support"
   1.910 +	depends on FB && PCI
   1.911 +	select I2C_ALGOBIT if FB_RADEON_I2C
   1.912 +	select I2C if FB_RADEON_I2C
   1.913 +	select FB_MODE_HELPERS
   1.914 +	select FB_CFB_FILLRECT
   1.915 +	select FB_CFB_COPYAREA
   1.916 +	select FB_CFB_IMAGEBLIT
   1.917 +	select FB_MACMODES if PPC_OF
   1.918 +	help
   1.919 +	  Choose this option if you want to use an ATI Radeon graphics card as
   1.920 +	  a framebuffer device.  There are both PCI and AGP versions.  You
   1.921 +	  don't need to choose this to run the Radeon in plain VGA mode.
   1.922 +
   1.923 +	  If you say Y here and want DDC/I2C support you must first say Y to
   1.924 +	  "I2C support" and "I2C bit-banging support" in the character devices
   1.925 +	  section.
   1.926 +
   1.927 +	  If you say M here then "I2C support" and "I2C bit-banging support" 
   1.928 +	  can be build either as modules or built-in.
   1.929 +
   1.930 +	  There is a product page at
   1.931 +	  http://apps.ati.com/ATIcompare/
   1.932 +config FB_RADEON_I2C
   1.933 +	bool "DDC/I2C for ATI Radeon support"
   1.934 +	depends on FB_RADEON
   1.935 +	default y
   1.936 +	help
   1.937 +	  Say Y here if you want DDC/I2C support for your Radeon board. 
   1.938 +
   1.939 +config FB_RADEON_DEBUG
   1.940 +	bool "Lots of debug output from Radeon driver"
   1.941 +	depends on FB_RADEON
   1.942 +	default n
   1.943 +	help
   1.944 +	  Say Y here if you want the Radeon driver to output all sorts
   1.945 +	  of debugging informations to provide to the maintainer when
   1.946 +	  something goes wrong.
   1.947 +
   1.948 +config FB_ATY128
   1.949 +	tristate "ATI Rage128 display support"
   1.950 +	depends on FB && PCI
   1.951 +	select FB_CFB_FILLRECT
   1.952 +	select FB_CFB_COPYAREA
   1.953 +	select FB_CFB_IMAGEBLIT
   1.954 +	select FB_MACMODES if PPC_PMAC
   1.955 +	help
   1.956 +	  This driver supports graphics boards with the ATI Rage128 chips.
   1.957 +	  Say Y if you have such a graphics board and read
   1.958 +	  <file:Documentation/fb/aty128fb.txt>.
   1.959 +
   1.960 +	  To compile this driver as a module, choose M here: the
   1.961 +	  module will be called aty128fb.
   1.962 +
   1.963 +config FB_ATY
   1.964 +	tristate "ATI Mach64 display support" if PCI || ATARI
   1.965 +	depends on FB
   1.966 +	select FB_CFB_FILLRECT
   1.967 +	select FB_CFB_COPYAREA
   1.968 +	select FB_CFB_IMAGEBLIT
   1.969 +	select FB_MACMODES if PPC
   1.970 +	help
   1.971 +	  This driver supports graphics boards with the ATI Mach64 chips.
   1.972 +	  Say Y if you have such a graphics board.
   1.973 +
   1.974 +	  To compile this driver as a module, choose M here: the
   1.975 +	  module will be called atyfb.
   1.976 +
   1.977 +config FB_ATY_CT
   1.978 +	bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
   1.979 +	depends on PCI && FB_ATY
   1.980 +	default y if SPARC64 && FB_PCI
   1.981 +	help
   1.982 +	  Say Y here to support use of ATI's 64-bit Rage boards (or other
   1.983 +	  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
   1.984 +	  framebuffer device.  The ATI product support page for these boards
   1.985 +	  is at <http://support.ati.com/products/pc/mach64/>.
   1.986 +
   1.987 +config FB_ATY_GENERIC_LCD
   1.988 +	bool "Mach64 generic LCD support (EXPERIMENTAL)"
   1.989 +	depends on FB_ATY_CT
   1.990 +	help
   1.991 +	  Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
   1.992 +	  Rage XC, or Rage XL chipset.
   1.993 +
   1.994 +config FB_ATY_GX
   1.995 +	bool "Mach64 GX support" if PCI
   1.996 +	depends on FB_ATY
   1.997 +	default y if ATARI
   1.998 +	help
   1.999 +	  Say Y here to support use of the ATI Mach64 Graphics Expression
  1.1000 +	  board (or other boards based on the Mach64 GX chipset) as a
  1.1001 +	  framebuffer device.  The ATI product support page for these boards
  1.1002 +	  is at
  1.1003 +	  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
  1.1004 +
  1.1005 +config FB_S3TRIO
  1.1006 +	bool "S3 Trio display support"
  1.1007 +	depends on (FB = y) && PPC && BROKEN
  1.1008 +	help
  1.1009 +	  If you have a S3 Trio say Y. Say N for S3 Virge.
  1.1010 +
  1.1011 +config FB_SAVAGE
  1.1012 +	tristate "S3 Savage support"
  1.1013 +	depends on FB && PCI && EXPERIMENTAL
  1.1014 +	select I2C_ALGOBIT if FB_SAVAGE_I2C
  1.1015 +	select I2C if FB_SAVAGE_I2C
  1.1016 +	select FB_MODE_HELPERS
  1.1017 +	select FB_CFB_FILLRECT
  1.1018 +	select FB_CFB_COPYAREA
  1.1019 +	select FB_CFB_IMAGEBLIT
  1.1020 +	help
  1.1021 +	  This driver supports notebooks and computers with S3 Savage PCI/AGP
  1.1022 +	  chips.
  1.1023 +
  1.1024 +	  Say Y if you have such a graphics card.
  1.1025 +
  1.1026 +	  To compile this driver as a module, choose M here; the module
  1.1027 +	  will be called savagefb.
  1.1028 +
  1.1029 +config FB_SAVAGE_I2C
  1.1030 +       bool "Enable DDC2 Support"
  1.1031 +       depends on FB_SAVAGE
  1.1032 +       help
  1.1033 +	  This enables I2C support for S3 Savage Chipsets.  This is used
  1.1034 +	  only for getting EDID information from the attached display
  1.1035 +	  allowing for robust video mode handling and switching.
  1.1036 +
  1.1037 +	  Because fbdev-2.6 requires that drivers must be able to
  1.1038 +	  independently validate video mode parameters, you should say Y
  1.1039 +	  here.
  1.1040 +
  1.1041 +config FB_SAVAGE_ACCEL
  1.1042 +       bool "Enable Console Acceleration"
  1.1043 +       depends on FB_SAVAGE
  1.1044 +       default n
  1.1045 +       help
  1.1046 +          This option will compile in console acceleration support. If
  1.1047 +          the resulting framebuffer console has bothersome glitches, then
  1.1048 +          choose N here.
  1.1049 +
  1.1050 +config FB_SIS
  1.1051 +	tristate "SiS/XGI display support"
  1.1052 +	depends on FB && PCI
  1.1053 +	select FB_CFB_FILLRECT
  1.1054 +	select FB_CFB_COPYAREA
  1.1055 +	select FB_CFB_IMAGEBLIT
  1.1056 +	help
  1.1057 +	  This is the frame buffer device driver for the SiS 300, 315, 330
  1.1058 +	  and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
  1.1059 +	  Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
  1.1060 +
  1.1061 +	  To compile this driver as a module, choose M here; the module
  1.1062 +	  will be called sisfb.
  1.1063 +
  1.1064 +config FB_SIS_300
  1.1065 +	bool "SiS 300 series support"
  1.1066 +	depends on FB_SIS
  1.1067 +	help
  1.1068 +	  Say Y here to support use of the SiS 300/305, 540, 630 and 730.
  1.1069 +
  1.1070 +config FB_SIS_315
  1.1071 +	bool "SiS 315/330/340 series and XGI support"
  1.1072 +	depends on FB_SIS
  1.1073 +	help
  1.1074 +	  Say Y here to support use of the SiS 315, 330 and 340 series
  1.1075 +	  (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
  1.1076 +	  as XGI V3XT, V5, V8 and Z7.
  1.1077 +
  1.1078 +config FB_NEOMAGIC
  1.1079 +	tristate "NeoMagic display support"
  1.1080 +	depends on FB && PCI
  1.1081 +	select FB_MODE_HELPERS
  1.1082 +	select FB_CFB_FILLRECT
  1.1083 +	select FB_CFB_COPYAREA
  1.1084 +	select FB_CFB_IMAGEBLIT
  1.1085 +	help
  1.1086 +	  This driver supports notebooks with NeoMagic PCI chips.
  1.1087 +	  Say Y if you have such a graphics card. 
  1.1088 +
  1.1089 +	  To compile this driver as a module, choose M here: the
  1.1090 +	  module will be called neofb.
  1.1091 +
  1.1092 +config FB_KYRO
  1.1093 +	tristate "IMG Kyro support"
  1.1094 +	depends on FB && PCI
  1.1095 +	select FB_CFB_FILLRECT
  1.1096 +	select FB_CFB_COPYAREA
  1.1097 +	select FB_CFB_IMAGEBLIT
  1.1098 +	help
  1.1099 +	  Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
  1.1100 +	  graphics board.
  1.1101 +
  1.1102 +	  To compile this driver as a module, choose M here: the
  1.1103 +	  module will be called kyrofb.
  1.1104 +
  1.1105 +config FB_3DFX
  1.1106 +	tristate "3Dfx Banshee/Voodoo3 display support"
  1.1107 +	depends on FB && PCI
  1.1108 +	select FB_CFB_IMAGEBLIT
  1.1109 +	select FB_CFB_FILLRECT
  1.1110 +	select FB_CFB_COPYAREA
  1.1111 +	help
  1.1112 +	  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
  1.1113 +	  chips. Say Y if you have such a graphics board.
  1.1114 +
  1.1115 +	  To compile this driver as a module, choose M here: the
  1.1116 +	  module will be called tdfxfb.
  1.1117 +
  1.1118 +config FB_3DFX_ACCEL
  1.1119 +	bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
  1.1120 +	depends on FB_3DFX && EXPERIMENTAL
  1.1121 +	---help---
  1.1122 +	This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
  1.1123 +	with acceleration functions.
  1.1124 +
  1.1125 +
  1.1126 +config FB_VOODOO1
  1.1127 +	tristate "3Dfx Voodoo Graphics (sst1) support"
  1.1128 +	depends on FB && PCI
  1.1129 +	select FB_CFB_FILLRECT
  1.1130 +	select FB_CFB_COPYAREA
  1.1131 +	select FB_CFB_IMAGEBLIT
  1.1132 +	---help---
  1.1133 +	  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
  1.1134 +	  Voodoo2 (cvg) based graphics card.
  1.1135 +
  1.1136 +	  To compile this driver as a module, choose M here: the
  1.1137 +	  module will be called sstfb.
  1.1138 +
  1.1139 +	  WARNING: Do not use any application that uses the 3D engine
  1.1140 +	  (namely glide) while using this driver.
  1.1141 +	  Please read the <file:Documentation/fb/README-sstfb.txt> for supported
  1.1142 +	  options and other important info  support.
  1.1143 +
  1.1144 +config FB_CYBLA
  1.1145 +	tristate "Cyberblade/i1 support"
  1.1146 +	depends on FB && PCI && X86_32 && !64BIT
  1.1147 +	select FB_CFB_IMAGEBLIT
  1.1148 +	select VIDEO_SELECT
  1.1149 +	---help---
  1.1150 +	  This driver is supposed to support the Trident Cyberblade/i1
  1.1151 +	  graphics core integrated in the VIA VT8601A North Bridge,
  1.1152 +	  also known as VIA Apollo PLE133.
  1.1153 +
  1.1154 +	  Status:
  1.1155 +	   - Developed, tested and working on EPIA 5000 and EPIA 800.
  1.1156 +	   - Does work reliable on all systems with CRT/LCD connected to
  1.1157 +	     normal VGA ports.
  1.1158 +	   - Should work on systems that do use the internal LCD port, but
  1.1159 +	     this is absolutely not tested.
  1.1160 +
  1.1161 +	  Character imageblit, copyarea and rectangle fill are hw accelerated,
  1.1162 +	  ypan scrolling is used by default.
  1.1163 +
  1.1164 +	  Please do read <file:Documentation/fb/cyblafb/*>.
  1.1165 +
  1.1166 +	  To compile this driver as a module, choose M here: the
  1.1167 +	  module will be called cyblafb.
  1.1168 +
  1.1169 +config FB_TRIDENT
  1.1170 +	tristate "Trident support"
  1.1171 +	depends on FB && PCI
  1.1172 +	select FB_CFB_FILLRECT
  1.1173 +	select FB_CFB_COPYAREA
  1.1174 +	select FB_CFB_IMAGEBLIT
  1.1175 +	---help---
  1.1176 +	  This driver is supposed to support graphics boards with the
  1.1177 +	  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
  1.1178 +	  but also on some motherboards. For more information, read
  1.1179 +	  <file:Documentation/fb/tridentfb.txt>
  1.1180 +
  1.1181 +	  Cyberblade/i1 support will be removed soon, use the cyblafb driver
  1.1182 +	  instead.
  1.1183 +
  1.1184 +	  Say Y if you have such a graphics board.
  1.1185 +
  1.1186 +
  1.1187 +	  To compile this driver as a module, choose M here: the
  1.1188 +	  module will be called tridentfb.
  1.1189 +
  1.1190 +config FB_TRIDENT_ACCEL
  1.1191 +	bool "Trident Acceleration functions (EXPERIMENTAL)"
  1.1192 +	depends on FB_TRIDENT && EXPERIMENTAL
  1.1193 +	---help---
  1.1194 +	This will compile the Trident frame buffer device with
  1.1195 +	acceleration functions.
  1.1196 +
  1.1197 +config FB_PM3
  1.1198 +	tristate "Permedia3 support"
  1.1199 +	depends on FB && PCI && BROKEN
  1.1200 +	help
  1.1201 +	  This is the frame buffer device driver for the 3DLabs Permedia3
  1.1202 +	  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
  1.1203 +	  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
  1.1204 +	  and maybe other boards.
  1.1205 +
  1.1206 +config FB_AU1100
  1.1207 +	bool "Au1100 LCD Driver"
  1.1208 +	depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
  1.1209 +
  1.1210 +source "drivers/video/geode/Kconfig"
  1.1211 +
  1.1212 +config FB_FFB
  1.1213 +	bool "Creator/Creator3D/Elite3D support"
  1.1214 +	depends on FB_SBUS && SPARC64
  1.1215 +	select FB_CFB_COPYAREA
  1.1216 +	select FB_CFB_IMAGEBLIT
  1.1217 +	help
  1.1218 +	  This is the frame buffer device driver for the Creator, Creator3D,
  1.1219 +	  and Elite3D graphics boards.
  1.1220 +
  1.1221 +config FB_TCX
  1.1222 +	bool "TCX (SS4/SS5 only) support"
  1.1223 +	depends on FB_SBUS
  1.1224 +	select FB_CFB_FILLRECT
  1.1225 +	select FB_CFB_COPYAREA
  1.1226 +	select FB_CFB_IMAGEBLIT
  1.1227 +	help
  1.1228 +	  This is the frame buffer device driver for the TCX 24/8bit frame
  1.1229 +	  buffer.
  1.1230 +
  1.1231 +config FB_CG14
  1.1232 +	bool "CGfourteen (SX) support"
  1.1233 +	depends on FB_SBUS
  1.1234 +	select FB_CFB_FILLRECT
  1.1235 +	select FB_CFB_COPYAREA
  1.1236 +	select FB_CFB_IMAGEBLIT
  1.1237 +	help
  1.1238 +	  This is the frame buffer device driver for the CGfourteen frame
  1.1239 +	  buffer on Desktop SPARCsystems with the SX graphics option.
  1.1240 +
  1.1241 +config FB_P9100
  1.1242 +	bool "P9100 (Sparcbook 3 only) support"
  1.1243 +	depends on FB_SBUS
  1.1244 +	select FB_CFB_FILLRECT
  1.1245 +	select FB_CFB_COPYAREA
  1.1246 +	select FB_CFB_IMAGEBLIT
  1.1247 +	help
  1.1248 +	  This is the frame buffer device driver for the P9100 card
  1.1249 +	  supported on Sparcbook 3 machines.
  1.1250 +
  1.1251 +config FB_LEO
  1.1252 +	bool "Leo (ZX) support"
  1.1253 +	depends on FB_SBUS
  1.1254 +	select FB_CFB_FILLRECT
  1.1255 +	select FB_CFB_COPYAREA
  1.1256 +	select FB_CFB_IMAGEBLIT
  1.1257 +	help
  1.1258 +	  This is the frame buffer device driver for the SBUS-based Sun ZX
  1.1259 +	  (leo) frame buffer cards.
  1.1260 +
  1.1261 +config FB_PCI
  1.1262 +	bool "PCI framebuffers"
  1.1263 +	depends on (FB = y) && PCI && SPARC
  1.1264 +
  1.1265 +config FB_IGA
  1.1266 +	bool "IGA 168x display support"
  1.1267 +	depends on SPARC32 && FB_PCI
  1.1268 +	select FB_CFB_FILLRECT
  1.1269 +	select FB_CFB_COPYAREA
  1.1270 +	select FB_CFB_IMAGEBLIT
  1.1271 +	help
  1.1272 +	  This is the framebuffer device for the INTERGRAPHICS 1680 and
  1.1273 +	  successor frame buffer cards.
  1.1274 +
  1.1275 +config FB_HIT
  1.1276 +	tristate "HD64461 Frame Buffer support"
  1.1277 +	depends on FB && HD64461
  1.1278 +	select FB_CFB_FILLRECT
  1.1279 +	select FB_CFB_COPYAREA
  1.1280 +	select FB_CFB_IMAGEBLIT
  1.1281 +	help
  1.1282 +	  This is the frame buffer device driver for the Hitachi HD64461 LCD
  1.1283 +	  frame buffer card.
  1.1284 +
  1.1285 +config FB_PMAG_AA
  1.1286 +	bool "PMAG-AA TURBOchannel framebuffer support"
  1.1287 +	depends on (FB = y) && TC
  1.1288 + 	select FB_CFB_FILLRECT
  1.1289 + 	select FB_CFB_COPYAREA
  1.1290 + 	select FB_CFB_IMAGEBLIT
  1.1291 +	help
  1.1292 +	  Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
  1.1293 +	  used mainly in the MIPS-based DECstation series.
  1.1294 +
  1.1295 +config FB_PMAG_BA
  1.1296 +	bool "PMAG-BA TURBOchannel framebuffer support"
  1.1297 +	depends on (FB = y) && TC
  1.1298 + 	select FB_CFB_FILLRECT
  1.1299 + 	select FB_CFB_COPYAREA
  1.1300 + 	select FB_CFB_IMAGEBLIT
  1.1301 +	help
  1.1302 +	  Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
  1.1303 +	  used mainly in the MIPS-based DECstation series.
  1.1304 +
  1.1305 +config FB_PMAGB_B
  1.1306 +	bool "PMAGB-B TURBOchannel framebuffer support"
  1.1307 +	depends on (FB = y) && TC
  1.1308 + 	select FB_CFB_FILLRECT
  1.1309 + 	select FB_CFB_COPYAREA
  1.1310 + 	select FB_CFB_IMAGEBLIT
  1.1311 +	help
  1.1312 +	  Support for the PMAGB-B TURBOchannel framebuffer card used mainly
  1.1313 +	  in the MIPS-based DECstation series. The card is currently only
  1.1314 +	  supported in 1280x1024x8 mode.
  1.1315 +
  1.1316 +config FB_MAXINE
  1.1317 +	bool "Maxine (Personal DECstation) onboard framebuffer support"
  1.1318 +	depends on (FB = y) && MACH_DECSTATION
  1.1319 + 	select FB_CFB_FILLRECT
  1.1320 + 	select FB_CFB_COPYAREA
  1.1321 + 	select FB_CFB_IMAGEBLIT
  1.1322 +	help
  1.1323 +	  Support for the onboard framebuffer (1024x768x8) in the Personal
  1.1324 +	  DECstation series (Personal DECstation 5000/20, /25, /33, /50,
  1.1325 +	  Codename "Maxine").
  1.1326 +
  1.1327 +config FB_TX3912
  1.1328 +	bool "TMPTX3912/PR31700 frame buffer support"
  1.1329 +	depends on (FB = y) && NINO
  1.1330 +	select FB_CFB_FILLRECT
  1.1331 +	select FB_CFB_COPYAREA
  1.1332 +	select FB_CFB_IMAGEBLIT
  1.1333 +	help
  1.1334 +	  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
  1.1335 +	  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
  1.1336 +
  1.1337 +	  Say Y here to enable kernel support for the on-board framebuffer.
  1.1338 +
  1.1339 +config FB_G364
  1.1340 +	bool "G364 frame buffer support"
  1.1341 +	depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
  1.1342 + 	select FB_CFB_FILLRECT
  1.1343 + 	select FB_CFB_COPYAREA
  1.1344 + 	select FB_CFB_IMAGEBLIT
  1.1345 +	help
  1.1346 +	  The G364 driver is the framebuffer used in MIPS Magnum 4000 and
  1.1347 +	  Olivetti M700-10 systems.
  1.1348 +
  1.1349 +config FB_68328
  1.1350 +	bool "Motorola 68328 native frame buffer support"
  1.1351 +	depends on FB && (M68328 || M68EZ328 || M68VZ328)
  1.1352 + 	select FB_CFB_FILLRECT
  1.1353 + 	select FB_CFB_COPYAREA
  1.1354 + 	select FB_CFB_IMAGEBLIT
  1.1355 +	help
  1.1356 +	  Say Y here if you want to support the built-in frame buffer of
  1.1357 +	  the Motorola 68328 CPU family.
  1.1358 +
  1.1359 +config FB_PXA
  1.1360 +	tristate "PXA LCD framebuffer support"
  1.1361 +	depends on FB && ARCH_PXA
  1.1362 +	select FB_CFB_FILLRECT
  1.1363 +	select FB_CFB_COPYAREA
  1.1364 +	select FB_CFB_IMAGEBLIT
  1.1365 +	---help---
  1.1366 +	  Frame buffer driver for the built-in LCD controller in the Intel
  1.1367 +	  PXA2x0 processor.
  1.1368 +
  1.1369 +	  This driver is also available as a module ( = code which can be
  1.1370 +	  inserted and removed from the running kernel whenever you want). The
  1.1371 +	  module will be called pxafb. If you want to compile it as a module,
  1.1372 +	  say M here and read <file:Documentation/modules.txt>.
  1.1373 +
  1.1374 +	  If unsure, say N.
  1.1375 +
  1.1376 +config FB_PXA_PARAMETERS
  1.1377 +	bool "PXA LCD command line parameters"
  1.1378 +	default n
  1.1379 +	depends on FB_PXA
  1.1380 +	---help---
  1.1381 +	  Enable the use of kernel command line or module parameters
  1.1382 +	  to configure the physical properties of the LCD panel when
  1.1383 +	  using the PXA LCD driver.
  1.1384 +
  1.1385 +	  This option allows you to override the panel parameters
  1.1386 +	  supplied by the platform in order to support multiple
  1.1387 +	  different models of flatpanel. If you will only be using a
  1.1388 +	  single model of flatpanel then you can safely leave this
  1.1389 +	  option disabled.
  1.1390 +
  1.1391 +	  <file:Documentation/fb/pxafb.txt> describes the available parameters.
  1.1392 +
  1.1393 +config FB_W100
  1.1394 +	tristate "W100 frame buffer support"
  1.1395 +	depends on FB && PXA_SHARPSL
  1.1396 + 	select FB_CFB_FILLRECT
  1.1397 + 	select FB_CFB_COPYAREA
  1.1398 + 	select FB_CFB_IMAGEBLIT
  1.1399 +	---help---
  1.1400 +	  Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
  1.1401 +
  1.1402 +	  This driver is also available as a module ( = code which can be
  1.1403 +	  inserted and removed from the running kernel whenever you want). The
  1.1404 +	  module will be called w100fb. If you want to compile it as a module,
  1.1405 +	  say M here and read <file:Documentation/modules.txt>.
  1.1406 +
  1.1407 +	  If unsure, say N.
  1.1408 +
  1.1409 +config FB_S3C2410
  1.1410 +	tristate "S3C2410 LCD framebuffer support"
  1.1411 +	depends on FB && ARCH_S3C2410
  1.1412 +	select FB_CFB_FILLRECT
  1.1413 +	select FB_CFB_COPYAREA
  1.1414 +	select FB_CFB_IMAGEBLIT
  1.1415 +	---help---
  1.1416 +	  Frame buffer driver for the built-in LCD controller in the Samsung
  1.1417 +	  S3C2410 processor.
  1.1418 +
  1.1419 +	  This driver is also available as a module ( = code which can be
  1.1420 +	  inserted and removed from the running kernel whenever you want). The
  1.1421 +	  module will be called s3c2410fb. If you want to compile it as a module,
  1.1422 +	  say M here and read <file:Documentation/modules.txt>.
  1.1423 +
  1.1424 +	  If unsure, say N.
  1.1425 +config FB_S3C2410_DEBUG
  1.1426 +	bool "S3C2410 lcd debug messages"
  1.1427 +	depends on FB_S3C2410
  1.1428 +	help
  1.1429 +	  Turn on debugging messages. Note that you can set/unset at run time
  1.1430 +	  through sysfs
  1.1431 +
  1.1432 +config FB_VIRTUAL
  1.1433 +	tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
  1.1434 +	depends on FB
  1.1435 +	select FB_CFB_FILLRECT
  1.1436 +	select FB_CFB_COPYAREA
  1.1437 +	select FB_CFB_IMAGEBLIT
  1.1438 +	---help---
  1.1439 +	  This is a `virtual' frame buffer device. It operates on a chunk of
  1.1440 +	  unswappable kernel memory instead of on the memory of a graphics
  1.1441 +	  board. This means you cannot see any output sent to this frame
  1.1442 +	  buffer device, while it does consume precious memory. The main use
  1.1443 +	  of this frame buffer device is testing and debugging the frame
  1.1444 +	  buffer subsystem. Do NOT enable it for normal systems! To protect
  1.1445 +	  the innocent, it has to be enabled explicitly at boot time using the
  1.1446 +	  kernel option `video=vfb:'.
  1.1447 +
  1.1448 +	  To compile this driver as a module, choose M here: the
  1.1449 +	  module will be called vfb.
  1.1450 +
  1.1451 +	  If unsure, say N.
  1.1452 +if VT
  1.1453 +	source "drivers/video/console/Kconfig"
  1.1454 +endif
  1.1455 +
  1.1456 +if FB || SGI_NEWPORT_CONSOLE
  1.1457 +	source "drivers/video/logo/Kconfig"
  1.1458 +endif
  1.1459 +
  1.1460 +if FB && SYSFS
  1.1461 +	source "drivers/video/backlight/Kconfig"
  1.1462 +endif
  1.1463 +
  1.1464 +endmenu
  1.1465 +