Kconfig 32.2 KB
Newer Older
1 2 3 4
#
# Video configuration
#

5
menu "Graphics support"
6 7

config FB
8
	bool "Support for frame buffer devices"
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
	---help---
	  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 <file:Documentation/fb/framebuffer.txt>
	  and the Framebuffer-HOWTO at
	  <http://www.tahallah.demon.co.uk/programming/prog.html> 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.

41
config FB_CIRRUS
42
	tristate "Cirrus Logic support"
43
	depends on FB && (AMIGA || PCI) && BROKEN
44 45 46 47 48 49 50
	---help---
	  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.

51
	  Please read the file <file:Documentation/fb/cirrusfb.txt>.
52 53 54 55 56

	  Say N unless you have such a graphics board or plan to get one
	  before you next recompile the kernel.

config FB_PM2
57
	tristate "Permedia2 support"
58
	depends on FB && (AMIGA || PCI) && BROKEN
59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162
	help
	  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
	  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.

config FB_PM2_FIFO_DISCONNECT
	bool "enable FIFO disconnect feature"
	depends on FB_PM2 && PCI
	help
	  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).

config FB_PM2_PCI
	bool "generic Permedia2 PCI board support"
	depends on FB_PM2 && PCI
	help
	  Say Y to enable support for Permedia2 AGP frame buffer card from
	  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.

config FB_PM2_CVPPC
	bool "Phase5 CVisionPPC/BVisionPPC support"
	depends on FB_PM2 && AMIGA
	help
	  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
	  framebuffer cards.  Phase 5 is no longer with us, alas.

config FB_ACORN
	bool "Acorn VIDC support"
	depends on FB && ARM && ARCH_ACORN
	help
	  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.

config FB_ANAKIN
	bool "Anakin LCD support"
	depends on FB && ARM && ARCH_ANAKIN

config FB_CLPS711X
	bool "CLPS711X LCD support"
	depends on FB && ARM && ARCH_CLPS711X

config FB_SA1100
	bool "SA-1100 LCD support"
	depends on FB && ARM && ARCH_SA1100
	help
	  This is a framebuffer device for the SA-1100 LCD Controller.
	  See <http://www.linux-fbdev.org/> for information on framebuffer
	  devices.

	  If you plan to use the LCD display with your SA-1100 system, say
	  Y here.

choice
	prompt "CerfBoard LCD Display Size"
	depends on FB_SA1100 && SA1100_CERF
	default CERF_LCD_57_A

config CERF_LCD_38_A
	bool "3.8_Color"

config CERF_LCD_38_B
	bool "3.8_Mono"

config CERF_LCD_57_A
	bool "5.7"

config CERF_LCD_72_A
	bool "7.2"

endchoice

config SA1100_CERF_LCD_BACKLIGHT
	bool "Cerfboard Backlight (CerfPDA)"
	depends on FB_SA1100 && SA1100_CERF_CPLD

config FB_CYBER2000
	tristate "CyberPro 2000/2010/5000 support"
	depends on FB && PCI
	help
	  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.

config FB_APOLLO
	bool
	depends on FB && APOLLO
	default y

config FB_Q40
	bool
	depends on FB && Q40
	default y

config FB_AMIGA
	tristate "Amiga native chipset support"
	depends on FB && AMIGA
	help
	  This is the frame buffer device driver for the builtin graphics
	  chipset found in Amigas.

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
163
	  module will be called amifb. If you want to compile it as a
164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203
	  module, say M here and read <file:Documentation/modules.txt>.

config FB_AMIGA_OCS
	bool "Amiga OCS chipset support"
	depends on FB_AMIGA
	help
	  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.

config FB_AMIGA_ECS
	bool "Amiga ECS chipset support"
	depends on FB_AMIGA
	help
	  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.

config FB_AMIGA_AGA
	bool "Amiga AGA chipset support"
	depends on FB_AMIGA
	help
	  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.

config FB_CYBER
	tristate "Amiga CyberVision support"
	depends on FB && ZORRO
	help
	  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.

config FB_VIRGE
204 205
	bool "Amiga CyberVision3D support "
	depends on FB && ZORRO
206 207 208 209 210 211 212 213 214
	help
	  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.

config FB_RETINAZ3
215 216
	tristate "Amiga RetinaZ3 support"
	depends on FB && ZORRO
217 218 219 220 221 222
	help
	  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.

config FB_FM2
223 224
	bool "Amiga FrameMaster II/Rainbow II support"
	depends on FB && ZORRO
225 226 227 228 229 230 231 232 233 234 235 236 237
	help
	  This is the frame buffer device driver for the Amiga FrameMaster
	  card from BSC (exhibited 1992 but not shipped as a CBM product).

config FB_ATARI
	bool "Atari native chipset support"
	depends on FB && ATARI
	help
	  This is the frame buffer device driver for the builtin graphics
	  chipset found in Ataris.

config FB_OF
	bool "Open Firmware frame buffer device support"
238
	depends on FB && (PPC64 || PPC_OF)
239 240 241 242 243 244
	help
	  Say Y if you want support with Open Firmware for your graphics
	  board.

config FB_CONTROL
	bool "Apple \"control\" display support"
245
	depends on FB && PPC_PMAC
246 247 248 249 250 251
	help
	  This driver supports a frame buffer for the graphics adapter in the
	  Power Macintosh 7300 and others.

config FB_PLATINUM
	bool "Apple \"platinum\" display support"
252
	depends on FB && PPC_PMAC
253 254 255 256 257 258
	help
	  This driver supports a frame buffer for the "platinum" graphics
	  adapter in some Power Macintoshes.

config FB_VALKYRIE
	bool "Apple \"valkyrie\" display support"
259
	depends on FB && (MAC || PPC_PMAC)
260 261 262 263 264 265 266 267 268 269 270 271 272
	help
	  This driver supports a frame buffer for the "valkyrie" graphics
	  adapter in some Power Macintoshes.

config FB_CT65550
	bool "Chips 65550 display support"
	depends on FB && PPC
	help
	  This is the frame buffer device driver for the Chips & Technologies
	  65550 graphics chip in PowerBooks.

config FB_IMSTT
	bool "IMS Twin Turbo display support"
273
	depends on FB && PCI
274 275 276 277 278 279 280 281 282 283 284
	help
	  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
	  many Macintosh and compatible computers.

config FB_S3TRIO
	bool "S3 Trio display support"
	depends on FB && PPC
	help
	  If you have a S3 Trio say Y. Say N for S3 Virge.

config FB_VGA16
285
	tristate "VGA 16-color graphics support"
286 287 288 289 290 291 292 293 294
	depends on FB && (X86 || PPC)
	help
	  This is the frame buffer device driver for VGA 16 color graphic
	  cards. Say Y if you have such a card.

	  This code is also available as a module. If you want to compile it
	  as a module ( = code which can be inserted in and removed from the
	  running kernel whenever you want), say M here and read
	  <file:Documentation/modules.txt>.  The module will be called
295
	  vga16fb.
296 297

config FB_STI
298
	tristate "HP STI frame buffer device support"
299
	depends on FB && PARISC
300
	default y
301 302 303
	---help---
	  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.
304 305 306 307 308 309 310 311 312
	  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".
313 314

config FB_MAC
315
	bool "Generic Macintosh display support"
316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331
	depends on FB && MAC

#      bool '  Apple DAFB display support' CONFIG_FB_DAFB
config FB_HP300
	bool
	depends on FB && HP300
	default y

config FB_TGA
	tristate "TGA framebuffer support"
	depends on FB && ALPHA
	help
	  This is the frame buffer device driver for generic TGA graphic
	  cards. Say Y if you have one of those.

config FB_VESA
332
	bool "VESA VGA graphics support"
333
	depends on FB && (X86 || X86_64)
334 335 336 337 338 339
	help
	  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 <file:Documentation/fb/vesafb.txt>. If unsure, say Y.

340 341 342 343 344
config VIDEO_SELECT
	bool
	depends on FB_VESA
	default y

345
config FB_HGA
346
	tristate "Hercules mono graphics support"
347 348 349 350 351 352
	depends on FB && X86
	help
	  Say Y here if you have a Hercules mono graphics card.

	  This driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want).
353
	  The module will be called hgafb. If you want to compile it as
354 355 356 357 358 359 360 361 362 363 364 365
	  a module, say M here and read <file:Documentation/modules.txt>.

	  As this card technology is 15 years old, most people will answer N
	  here.

config VIDEO_SELECT
	bool
	depends on FB && X86
	default y

config FB_SGIVW
	tristate "SGI Visual Workstation framebuffer support"
366
	depends on FB && X86_VISWS
367 368 369 370 371 372 373 374 375 376 377 378
	help
	  SGI Visual Workstation support for framebuffer graphics.

config BUS_I2C
	bool
	depends on FB && VISWS
	default y

config FB_SUN3
	bool "Sun3 framebuffer support"
	depends on FB && (SUN3 || SUN3X)

379
config FB_BW2
380 381 382 383 384
	bool "BWtwo support"
	depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
	help
	  This is the frame buffer device driver for the BWtwo frame buffer.

385
config FB_CG3
386 387 388 389 390
	bool "CGthree support"
	depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
	help
	  This is the frame buffer device driver for the CGthree frame buffer.

391
config FB_CG6
392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408
	bool "CGsix (GX,TurboGX) support"
	depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
	help
	  This is the frame buffer device driver for the CGsix (GX, TurboGX)
	  frame buffer.

config FB_PVR2
	tristate "NEC PowerVR 2 display support"
	depends on FB && SH_DREAMCAST
	---help---
	  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
	  run linux on your Dreamcast, you will have to say Y here.
	  This driver may or may not work on other PowerVR 2 cards, but is
	  totally untested.  Use at your own risk.  If unsure, say N.

	  This driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want).
409
	  The module will be called pvr2fb.  If you want to compile it as
410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455
	  a module, say M here and read <file:Documentation/modules.txt>.

	  You can pass several parameters to the driver at boot time or at
	  module load time.  The parameters look like "video=pvr2:XXX", where
	  the meaning of XXX can be found at the end of the main source file
	  (<file:drivers/video/pvr2fb.c>). Please see the file
	  <file:Documentation/fb/pvr2fb.txt>.

config FB_PVR2_DEBUG
	bool "Debug pvr2fb"
	depends on FB_PVR2=y
	help
	  Say Y here if you wish for the pvr2fb driver to print out debugging
	  messages. Most people will want to say N here. If unsure, you will
	  also want to say N.

config FB_E1355
	bool "Epson 1355 framebuffer support"
	depends on FB && SUPERH
	help
	  Build in support for the SED1355 Epson Research Embedded RAMDAC
	  LCD/CRT Controller (since redesignated as the S1D13505) as a
	  framebuffer.  Product specs at
	  <http://www.erd.epson.com/vdc/html/products.htm>.

config E1355_REG_BASE
	hex "Register Base Address"
	depends on FB_E1355
	default "a8000000"
	help
	  Epson SED1355/S1D13505 LCD/CRT controller register base address.
	  See the manuals at
	  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
	  discussion.

config E1355_FB_BASE
	hex "Framebuffer Base Address"
	depends on FB_E1355
	default "a8200000"
	help
	  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
	  the manuals at
	  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
	  discussion.

config FB_RIVA
456 457
	tristate "nVidia Riva support"
	depends on FB && PCI
458 459 460 461 462 463 464
	help
	  This driver supports graphics boards with the nVidia Riva/Geforce
	  chips.
	  Say Y if you have such a graphics board.

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
465
	  module will be called rivafb. If you want to compile it as a
466 467
	  module, say M here and read <file:Documentation/modules.txt>.

James Simmons's avatar
James Simmons committed
468 469 470 471 472 473 474 475 476
config FB_I810
	tristate "Intel 810/815 support (EXPERIMENTAL)"
	depends on FB && AGP && AGP_INTEL && EXPERIMENTAL && PCI	
	help
	  This driver supports the on-board graphics built in to the Intel 810 
          and 815 chipsets.  Say Y if you have and plan to use such a board.

          The driver is also available as a module ( = code which can be
          inserted and removed from the running kernel whenever you want). 
477
          The module will be called i810fb. If you want to compile it as a
James Simmons's avatar
James Simmons committed
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505
          module, say M here and read <file:Documentation/modules.txt>.

          For more information, please read 
	  <file:Documentation/fb/intel810.txt>

config FB_I810_GTF
	bool "use VESA Generalized Timing Formula"
	depends on FB_I810
	help
	  If you say Y, then the VESA standard, Generalized Timing Formula 
          or GTF, will be used to calculate the required video timing values
	  per video mode.  Since the GTF allows nondiscrete timings 
          (nondiscrete being a range of values as opposed to discrete being a
          set of values), you'll be able to use any combination of horizontal 
	  and vertical resolutions, and vertical refresh rates without having
	  to specify your own timing parameters.  This is especially useful
	  to maximize the performance of an aging display, or if you just 
          have a display with nonstandard dimensions. A VESA compliant 
	  monitor is recommended, but can still work with non-compliant ones.
	  If you need or want this, then select this option. The timings may 
	  not be compliant with Intel's recommended values. Use at your own 
	  risk.

          If you say N, the driver will revert to discrete video timings 
	  using a set recommended by Intel in their documentation.
  
          If unsure, say N.

506
config FB_MATROX
507 508
	tristate "Matrox acceleration"
	depends on FB && PCI
509 510 511 512 513 514 515 516
	---help---
	  Say Y here if you have a Matrox Millennium, Matrox Millennium II,
	  Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
	  Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
	  Matrox G400, G450 or G550 card in your box.

	  This driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want).
517
	  The module will be called matroxfb. If you want to compile it as
518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608
	  a module, say M here and read <file:Documentation/modules.txt>.

	  You can pass several parameters to the driver at boot time or at
	  module load time. The parameters look like "video=matrox:XXX", and
	  are described in <file:Documentation/fb/matroxfb.txt>.

config FB_MATROX_MILLENIUM
	bool "Millennium I/II support"
	depends on FB_MATROX
	help
	  Say Y here if you have a Matrox Millennium or Matrox Millennium II
	  video card. If you select "Advanced lowlevel driver options" below,
	  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
	  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
	  also use font widths different from 8.

config FB_MATROX_MYSTIQUE
	bool "Mystique support"
	depends on FB_MATROX
	help
	  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
	  video card. If you select "Advanced lowlevel driver options" below,
	  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
	  packed pixel and 32 bpp packed pixel. You can also use font widths
	  different from 8.

config FB_MATROX_G450
	bool "G100/G200/G400/G450/G550 support"
	depends on FB_MATROX
	---help---
	  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
	  video card. If you select "Advanced lowlevel driver options", you
	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
	  pixel and 32 bpp packed pixel. You can also use font widths
	  different from 8.

	  If you need support for G400 secondary head, you must first say Y to
	  "I2C support" and "I2C bit-banging support" in the character devices
	  section, and then to "Matrox I2C support" and "G400 second head
	  support" here in the framebuffer section. G450/G550 secondary head
	  and digital output are supported without additional modules.

	  The driver starts in monitor mode. You must use the matroxset tool 
	  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 
	  swap primary and secondary head outputs, or to change output mode.  
	  Secondary head driver always start in 640x480 resolution and you 
	  must use fbset to change it.

	  Do not forget that second head supports only 16 and 32 bpp
	  packed pixels, so it is a good idea to compile them into the kernel
	  too. You can use only some font widths, as the driver uses generic
	  painting procedures (the secondary head does not use acceleration
	  engine).

	  G450/G550 hardware can display TV picture only from secondary CRTC,
	  and it performs no scaling, so picture must have 525 or 625 lines.

config FB_MATROX_G100A
	bool "G100/G200/G400 support"
	depends on FB_MATROX && !FB_MATROX_G450
	---help---
	  Say Y here if you have a Matrox G100, G200 or G400 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" and "I2C bit-banging support" in the character devices
	  section, and then to "Matrox I2C support" and "G400 second head
	  support" here in the framebuffer section.

config FB_MATROX_G100
	bool
	depends on FB_MATROX && (FB_MATROX_G450 || FB_MATROX_G100A)
	default y

config FB_MATROX_I2C
	tristate "Matrox I2C support"
	depends on FB_MATROX && I2C_ALGOBIT
	---help---
	  This drivers creates I2C buses which are needed for accessing the
	  DDC (I2C) bus present on all Matroxes, an I2C bus which
	  interconnects Matrox optional devices, like MGA-TVO on G200 and
	  G400, and the secondary head DDC bus, present on G400 only.

	  You can say Y or M here if you want to experiment with monitor
	  detection code. You must say Y or M here if you want to use either
	  second head of G400 or MGA-TVO on G200 or G400.

	  If you compile it as module, it will create a module named
609
	  i2c-matroxfb.
610 611 612 613 614 615 616 617 618 619 620 621 622 623 624

config FB_MATROX_MAVEN
	tristate "G400 second head support"
	depends on FB_MATROX_G100 && FB_MATROX_I2C
	---help---
	  WARNING !!! This support does not work with G450 !!!

	  Say Y or M here if you want to use a secondary head (meaning two
	  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
	  head is not compatible with accelerated XFree 3.3.x SVGA servers -
	  secondary head output is blanked while you are in X. With XFree
	  3.9.17 preview you can use both heads if you use SVGA over fbdev or
	  the fbdev driver on first head and the fbdev driver on second head.

	  If you compile it as module, two modules are created,
625
	  matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653
	  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:
654
	  insert several instances of the module matroxfb into the kernel
655 656 657 658 659 660 661 662
	  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
663 664
	tristate "ATI Radeon display support"
	depends on FB && PCI
665 666 667 668 669 670 671 672
	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.
	  There is a product page at
	  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.

config FB_ATY128
673 674
	tristate "ATI Rage128 display support"
	depends on FB && PCI
675 676 677 678 679 680 681
	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>.

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
682
	  module will be called aty128fb. If you want to compile it as a
683 684
	  module, say M here and read <file:Documentation/modules.txt>.

685 686 687 688 689 690 691 692 693
config FB_ATY
	tristate "ATI Mach64 display support" if PCI || ATARI
	depends on FB
	help
	  This driver supports graphics boards with the ATI Mach64 chips.
	  Say Y if you have such a graphics board.

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
694
	  module will be called atyfb. If you want to compile it as a
695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717
	  module, say M here and read <file:Documentation/modules.txt>.

config FB_ATY_CT
	bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
	depends on PCI && FB_ATY
	default y if SPARC64 && FB_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_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>.

718 719 720 721 722 723
config FB_ATY_XL_INIT
	bool "  Rage XL No-BIOS Init support" if FB_ATY_CT
	depends on FB_ATY
	help
	  Say Y here to support booting a Rage XL without BIOS support.

724
config FB_SIS
725 726
	tristate "SIS acceleration"
	depends on FB && PCI
727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746
	help
	  This is the frame buffer device driver for the SiS 630 and 640 Super
	  Socket 7 UMA cards.  Specs available at <http://www.sis.com.tw/>.

config FB_SIS_300
	bool "SIS 630/540/730 support"
	depends on FB_SIS
	help
	  This is the frame buffer device driver for the SiS 630 and related
	  Super Socket 7 UMA cards.  Specs available at
	  <http://www.sis.com.tw/>.

config FB_SIS_315
	bool "SIS 315H/315 support"
	depends on FB_SIS
	help
	  This is the frame buffer device driver for the SiS 315 graphics
	  card.  Specs available at <http://www.sis.com.tw/>.

config FB_NEOMAGIC
747 748
	tristate "NeoMagic display support"
	depends on FB && PCI
749 750 751 752 753 754
	help
	  This driver supports notebooks with NeoMagic PCI chips.
	  Say Y if you have such a graphics card. 

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
755
	  module will be called neofb. If you want to compile it as a
756 757 758
	  module, say M here and read Documentation/modules.txt.

config FB_3DFX
759 760
	tristate "3Dfx Banshee/Voodoo3 display support"
	depends on FB && PCI
761 762 763 764 765 766
	help
	  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
	  chips. Say Y if you have such a graphics board.

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
767
	  module will be called tdfxfb. If you want to compile it as a
768 769 770
	  module, say M here and read <file:Documentation/modules.txt>.

config FB_VOODOO1
771 772
	tristate "3Dfx Voodoo Graphics (sst1) support"
	depends on FB && PCI
773 774 775 776 777 778
	---help---
	  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
	  Voodoo2 (cvg) based graphics card.

	  This driver is also available as a module ( = code which can be 
	  inserted and removed from the running kernel whenever you want).
779
	  The module will be called sstfb. If you want to compile it as
780 781 782 783 784 785 786 787
	  a module, say M here and read Documentation/modules.txt.

	  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.

config FB_TRIDENT
788 789
	tristate "Trident support"
	depends on FB && PCI
790 791 792 793 794 795 796 797 798 799
	---help---
	  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>

	  Say Y if you have such a graphics board.

	  The driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
800
	  module will be called tridentfb. If you want to compile it as a
801 802 803
	  module, say M here and read <file:Documentation/modules.txt>.

config FB_PM3
804
	tristate "Permedia3 support"
805
	depends on FB && PCI && BROKEN
806 807 808 809 810 811 812 813 814 815 816 817
	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_SBUS
	bool "SBUS and UPA framebuffers"
	depends on FB && (SPARC32 || SPARC64)
	help
	  Say Y if you want support for SBUS or UPA based frame buffer device.

818 819
config FB_FFB
	bool "Creator/Creator3D/Elite3D support"
820 821
	depends on FB_SBUS && SPARC64
	help
822 823
	  This is the frame buffer device driver for the Creator, Creator3D,
	  and Elite3D graphics boards.
824 825 826

config FB_TCX
	bool "TCX (SS4/SS5 only) support"
827
	depends on FB_SBUS
828 829 830 831
	help
	  This is the frame buffer device driver for the TCX 24/8bit frame
	  buffer.

832
config FB_CG14
833
	bool "CGfourteen (SX) support"
834
	depends on FB_SBUS
835 836 837 838 839 840
	help
	  This is the frame buffer device driver for the CGfourteen frame
	  buffer on Desktop SPARCsystems with the SX graphics option.

config FB_P9100
	bool "P9100 (Sparcbook 3 only) support"
841
	depends on FB_SBUS
842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903
	help
	  This is the frame buffer device driver for the P9100 card
	  supported on Sparcbook 3 machines.

config FB_LEO
	bool "Leo (ZX) support"
	depends on FB_SBUS
	help
	  This is the frame buffer device driver for the SBUS-based Sun ZX
	  (leo) frame buffer cards.

config FB_PCI
	bool "PCI framebuffers"
	depends on FB && PCI && (SPARC64 || SPARC32)

config FB_IGA
	bool "IGA 168x display support"
	depends on SPARC32 && FB_PCI
	help
	  This is the framebuffer device for the INTERGRAPHICS 1680 and
	  successor frame buffer cards.

config FB_HIT
	tristate "HD64461 Frame Buffer support"
	depends on FB && HD64461
	help
	  This is the frame buffer device driver for the Hitachi HD64461 LCD
	  frame buffer card.

config FB_PMAG_BA
	bool "PMAG-BA TURBOchannel framebuffer support"
	depends on FB && DECSTATION && TC
	help
	  Say Y here to directly support the on-board PMAG-BA framebuffer in
	  the 5000/1xx versions of the DECstation.  There is a page dedicated
	  to Linux on DECstations at <http://decstation.unix-ag.org/>.

config FB_PMAGB_B
	bool "PMAGB-B TURBOchannel framebuffer spport"
	depends on FB && DECSTATION && TC
	help
	  Say Y here to directly support the on-board PMAGB-B framebuffer in
	  the 5000/1xx versions of the DECstation.  There is a page dedicated
	  to Linux on DECstations at <http://decstation.unix-ag.org/>.

config FB_MAXINE
	bool "Maxine (Personal DECstation) onboard framebuffer spport"
	depends on FB && DECSTATION && TC
	help
	  Say Y here to directly support the on-board framebuffer in the
	  Maxine (5000/20, /25, /33) version of the DECstation.  There is a
	  page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.

config FB_TX3912
	bool "TMPTX3912/PR31700 frame buffer support"
	depends on FB && NINO
	help
	  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.

904 905 906 907 908 909 910
config FB_68328
	bool "Motorola 68328 native frame buffer support"
	depends on (M68328 || M68EZ328 || M68VZ328)
	help
	  Say Y here if you want to support the built-in frame buffer of
	  the Motorola 68328 CPU family.

911
config FB_VIRTUAL
912 913
	tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
	depends on FB
914 915 916 917 918 919 920 921 922 923 924 925
	---help---
	  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:'.

	  This driver is also available as a module ( = code which can be
	  inserted and removed from the running kernel whenever you want). The
926
	  module will be called vfb. If you want to compile it as a module,
927 928 929
	  say M here and read <file:Documentation/modules.txt>.

	  If unsure, say N.
930 931 932
if VT
	source "drivers/video/console/Kconfig"
endif
933

934 935 936
if FB || SGI_NEWPORT_CONSOLE
	source "drivers/video/logo/Kconfig"
endif
937 938 939

endmenu