drivers/video/Kconfig

   1 #
   2 # Video configuration
   3 #
   4
   5 menu "Graphics support"
   6
   7 source "drivers/video/backlight/Kconfig"
   8
   9 config FB
  10         tristate "Support for frame buffer devices"
  11         ---help---
  12           The frame buffer device provides an abstraction for the graphics
  13           hardware. It represents the frame buffer of some video hardware and
  14           allows application software to access the graphics hardware through
  15           a well-defined interface, so the software doesn't need to know
  16           anything about the low-level (hardware register) stuff.
  17
  18           Frame buffer devices work identically across the different
  19           architectures supported by Linux and make the implementation of
  20           application programs easier and more portable; at this point, an X
  21           server exists which uses the frame buffer device exclusively.
  22           On several non-X86 architectures, the frame buffer device is the
  23           only way to use the graphics hardware.
  24
  25           The device is accessed through special device nodes, usually located
  26           in the /dev directory, i.e. /dev/fb*.
  27
  28           You need an utility program called fbset to make full use of frame
  29           buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
  30           and the Framebuffer-HOWTO at
  31           <http://www.tahallah.demon.co.uk/programming/prog.html> for more
  32           information.
  33
  34           Say Y here and to the driver for your graphics board below if you
  35           are compiling a kernel for a non-x86 architecture.
  36
  37           If you are compiling for the x86 architecture, you can say Y if you
  38           want to play with it, but it is not essential. Please note that
  39           running graphical applications that directly touch the hardware
  40           (e.g. an accelerated X server) and that are not frame buffer
  41           device-aware may cause unexpected results. If unsure, say N.
  42
  43 config FIRMWARE_EDID
  44        bool "Enable firmware EDID"
  45        depends on FB
  46        default n
  47        ---help---
  48          This enables access to the EDID transferred from the firmware.
  49          On the i386, this is from the Video BIOS. Enable this if DDC/I2C
  50          transfers do not work for your driver and if you are using
  51          nvidiafb, i810fb or savagefb.
  52
  53          In general, choosing Y for this option is safe.  If you
  54          experience extremely long delays while booting before you get
  55          something on your display, try setting this to N.  Matrox cards in
  56          combination with certain motherboards and monitors are known to
  57          suffer from this problem.
  58
  59 config FB_DDC
  60        tristate
  61        depends on FB
  62        select I2C_ALGOBIT
  63        select I2C
  64        default n
  65
  66 config FB_CFB_FILLRECT
  67         tristate
  68         depends on FB
  69         default n
  70         ---help---
  71           Include the cfb_fillrect function for generic software rectangle
  72           filling. This is used by drivers that don't provide their own
  73           (accelerated) version.
  74
  75 config FB_CFB_COPYAREA
  76         tristate
  77         depends on FB
  78         default n
  79         ---help---
  80           Include the cfb_copyarea function for generic software area copying.
  81           This is used by drivers that don't provide their own (accelerated)
  82           version.
  83
  84 config FB_CFB_IMAGEBLIT
  85         tristate
  86         depends on FB
  87         default n
  88         ---help---
  89           Include the cfb_imageblit function for generic software image
  90           blitting. This is used by drivers that don't provide their own
  91           (accelerated) version.
  92
  93 config FB_SVGALIB
  94         tristate
  95         depends on FB
  96         default n
  97         ---help---
  98           Common utility functions useful to fbdev drivers of VGA-based
  99           cards.
 100
 101 config FB_MACMODES
 102        tristate
 103        depends on FB
 104        default n
 105
 106 config FB_BACKLIGHT
 107         bool
 108         depends on FB
 109         select BACKLIGHT_LCD_SUPPORT
 110         select BACKLIGHT_CLASS_DEVICE
 111         default n
 112
 113 config FB_MODE_HELPERS
 114         bool "Enable Video Mode Handling Helpers"
 115         depends on FB
 116         default n
 117         ---help---
 118           This enables functions for handling video modes using the
 119           Generalized Timing Formula and the EDID parser. A few drivers rely
 120           on this feature such as the radeonfb, rivafb, and the i810fb. If
 121           your driver does not take advantage of this feature, choosing Y will
 122           just increase the kernel size by about 5K.
 123
 124 config FB_TILEBLITTING
 125        bool "Enable Tile Blitting Support"
 126        depends on FB
 127        default n
 128        ---help---
 129          This enables tile blitting.  Tile blitting is a drawing technique
 130          where the screen is divided into rectangular sections (tiles), whereas
 131          the standard blitting divides the screen into pixels. Because the
 132          default drawing element is a tile, drawing functions will be passed
 133          parameters in terms of number of tiles instead of number of pixels.
 134          For example, to draw a single character, instead of using bitmaps,
 135          an index to an array of bitmaps will be used.  To clear or move a
 136          rectangular section of a screen, the rectangle will be described in
 137          terms of number of tiles in the x- and y-axis.
 138
 139          This is particularly important to one driver, matroxfb.  If
 140          unsure, say N.
 141
 142 comment "Frame buffer hardware drivers"
 143         depends on FB
 144
 145 config FB_CIRRUS
 146         tristate "Cirrus Logic support"
 147         depends on FB && (ZORRO || PCI)
 148         select FB_CFB_FILLRECT
 149         select FB_CFB_COPYAREA
 150         select FB_CFB_IMAGEBLIT
 151         ---help---
 152           This enables support for Cirrus Logic GD542x/543x based boards on
 153           Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
 154
 155           If you have a PCI-based system, this enables support for these
 156           chips: GD-543x, GD-544x, GD-5480.
 157
 158           Please read the file <file:Documentation/fb/cirrusfb.txt>.
 159
 160           Say N unless you have such a graphics board or plan to get one
 161           before you next recompile the kernel.
 162
 163 config FB_PM2
 164         tristate "Permedia2 support"
 165         depends on FB && ((AMIGA && BROKEN) || PCI)
 166         select FB_CFB_FILLRECT
 167         select FB_CFB_COPYAREA
 168         select FB_CFB_IMAGEBLIT
 169         help
 170           This is the frame buffer device driver for the Permedia2 AGP frame
 171           buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
 172           product page at
 173           <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
 174
 175 config FB_PM2_FIFO_DISCONNECT
 176         bool "enable FIFO disconnect feature"
 177         depends on FB_PM2 && PCI
 178         help
 179           Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
 180
 181 config FB_ARMCLCD
 182         tristate "ARM PrimeCell PL110 support"
 183         depends on FB && ARM && ARM_AMBA
 184         select FB_CFB_FILLRECT
 185         select FB_CFB_COPYAREA
 186         select FB_CFB_IMAGEBLIT
 187         help
 188           This framebuffer device driver is for the ARM PrimeCell PL110
 189           Colour LCD controller.  ARM PrimeCells provide the building
 190           blocks for System on a Chip devices.
 191
 192           If you want to compile this as a module (=code which can be
 193           inserted into and removed from the running kernel), say M
 194           here and read <file:Documentation/modules.txt>.  The module
 195           will be called amba-clcd.
 196
 197 choice
 198
 199         depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
 200         prompt "LCD Panel"
 201         default FB_ARMCLCD_SHARP_LQ035Q7DB02
 202
 203 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
 204         bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
 205         help
 206           This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
 207           color QVGA, HRTFT panel.  The LogicPD device includes
 208           an integrated HRTFT controller IC.
 209           The native resolution is 240x320.
 210
 211 config FB_ARMCLCD_SHARP_LQ057Q3DC02
 212         bool "LogicPD LCD 5.7\" QVGA"
 213         help
 214           This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
 215           color QVGA, TFT panel.  The LogicPD device includes an
 216           The native resolution is 320x240.
 217
 218 config FB_ARMCLCD_SHARP_LQ64D343
 219         bool "LogicPD LCD 6.4\" VGA"
 220         help
 221           This is an implementation of the Sharp LQ64D343, a 6.4"
 222           color VGA, TFT panel.  The LogicPD device includes an
 223           The native resolution is 640x480.
 224
 225 config FB_ARMCLCD_SHARP_LQ10D368
 226         bool "LogicPD LCD 10.4\" VGA"
 227         help
 228           This is an implementation of the Sharp LQ10D368, a 10.4"
 229           color VGA, TFT panel.  The LogicPD device includes an
 230           The native resolution is 640x480.
 231
 232
 233 config FB_ARMCLCD_SHARP_LQ121S1DG41
 234         bool "LogicPD LCD 12.1\" SVGA"
 235         help
 236           This is an implementation of the Sharp LQ121S1DG41, a 12.1"
 237           color SVGA, TFT panel.  The LogicPD device includes an
 238           The native resolution is 800x600.
 239
 240           This panel requires a clock rate may be an integer fraction
 241           of the base LCDCLK frequency.  The driver will select the
 242           highest frequency available that is lower than the maximum
 243           allowed.  The panel may flicker if the clock rate is
 244           slower than the recommended minimum.
 245
 246 config FB_ARMCLCD_AUO_A070VW01_WIDE
 247         bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
 248         help
 249           This is an implementation of the AU Optronics, a 7.0"
 250           WIDE Color.  The native resolution is 234x480.
 251
 252 config FB_ARMCLCD_HITACHI
 253         bool "Hitachi Wide Screen 800x480"
 254         help
 255           This is an implementation of the Hitachi 800x480.
 256
 257 endchoice
 258
 259
 260 config FB_ACORN
 261         bool "Acorn VIDC support"
 262         depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
 263         select FB_CFB_FILLRECT
 264         select FB_CFB_COPYAREA
 265         select FB_CFB_IMAGEBLIT
 266         help
 267           This is the frame buffer device driver for the Acorn VIDC graphics
 268           hardware found in Acorn RISC PCs and other ARM-based machines.  If
 269           unsure, say N.
 270
 271 config FB_CLPS711X
 272         bool "CLPS711X LCD support"
 273         depends on (FB = y) && ARM && ARCH_CLPS711X
 274         select FB_CFB_FILLRECT
 275         select FB_CFB_COPYAREA
 276         select FB_CFB_IMAGEBLIT
 277         help
 278           Say Y to enable the Framebuffer driver for the CLPS7111 and
 279           EP7212 processors.
 280
 281 config FB_SA1100
 282         bool "SA-1100 LCD support"
 283         depends on (FB = y) && ARM && ARCH_SA1100
 284         select FB_CFB_FILLRECT
 285         select FB_CFB_COPYAREA
 286         select FB_CFB_IMAGEBLIT
 287         help
 288           This is a framebuffer device for the SA-1100 LCD Controller.
 289           See <http://www.linux-fbdev.org/> for information on framebuffer
 290           devices.
 291
 292           If you plan to use the LCD display with your SA-1100 system, say
 293           Y here.
 294
 295 config FB_IMX
 296         tristate "Motorola i.MX LCD support"
 297         depends on FB && ARM && ARCH_IMX
 298         select FB_CFB_FILLRECT
 299         select FB_CFB_COPYAREA
 300         select FB_CFB_IMAGEBLIT
 301
 302 config FB_CYBER2000
 303         tristate "CyberPro 2000/2010/5000 support"
 304         depends on FB && PCI && (BROKEN || !SPARC64)
 305         select FB_CFB_FILLRECT
 306         select FB_CFB_COPYAREA
 307         select FB_CFB_IMAGEBLIT
 308         help
 309           This enables support for the Integraphics CyberPro 20x0 and 5000
 310           VGA chips used in the Rebel.com Netwinder and other machines.
 311           Say Y if you have a NetWinder or a graphics card containing this
 312           device, otherwise say N.
 313
 314 config FB_APOLLO
 315         bool
 316         depends on (FB = y) && APOLLO
 317         default y
 318         select FB_CFB_FILLRECT
 319         select FB_CFB_IMAGEBLIT
 320
 321 config FB_Q40
 322         bool
 323         depends on (FB = y) && Q40
 324         default y
 325         select FB_CFB_FILLRECT
 326         select FB_CFB_COPYAREA
 327         select FB_CFB_IMAGEBLIT
 328
 329 config FB_AMIGA
 330         tristate "Amiga native chipset support"
 331         depends on FB && AMIGA
 332         help
 333           This is the frame buffer device driver for the builtin graphics
 334           chipset found in Amigas.
 335
 336           To compile this driver as a module, choose M here: the
 337           module will be called amifb.
 338
 339 config FB_AMIGA_OCS
 340         bool "Amiga OCS chipset support"
 341         depends on FB_AMIGA
 342         help
 343           This enables support for the original Agnus and Denise video chips,
 344           found in the Amiga 1000 and most A500's and A2000's. If you intend
 345           to run Linux on any of these systems, say Y; otherwise say N.
 346
 347 config FB_AMIGA_ECS
 348         bool "Amiga ECS chipset support"
 349         depends on FB_AMIGA
 350         help
 351           This enables support for the Enhanced Chip Set, found in later
 352           A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
 353           you intend to run Linux on any of these systems, say Y; otherwise
 354           say N.
 355
 356 config FB_AMIGA_AGA
 357         bool "Amiga AGA chipset support"
 358         depends on FB_AMIGA
 359         help
 360           This enables support for the Advanced Graphics Architecture (also
 361           known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
 362           and CD32. If you intend to run Linux on any of these systems, say Y;
 363           otherwise say N.
 364
 365 config FB_FM2
 366         bool "Amiga FrameMaster II/Rainbow II support"
 367         depends on (FB = y) && ZORRO
 368         select FB_CFB_FILLRECT
 369         select FB_CFB_COPYAREA
 370         select FB_CFB_IMAGEBLIT
 371         help
 372           This is the frame buffer device driver for the Amiga FrameMaster
 373           card from BSC (exhibited 1992 but not shipped as a CBM product).
 374
 375 config FB_ARC
 376         tristate "Arc Monochrome LCD board support"
 377         depends on FB && X86
 378         select FB_CFB_FILLRECT
 379         select FB_CFB_COPYAREA
 380         select FB_CFB_IMAGEBLIT
 381         help
 382           This enables support for the Arc Monochrome LCD board. The board
 383           is based on the KS-108 lcd controller and is typically a matrix
 384           of 2*n chips. This driver was tested with a 128x64 panel. This
 385           driver supports it for use with x86 SBCs through a 16 bit GPIO
 386           interface (8 bit data, 8 bit control). If you anticipate using
 387           this driver, say Y or M; otherwise say N. You must specify the
 388           GPIO IO address to be used for setting control and data.
 389
 390 config FB_ATARI
 391         bool "Atari native chipset support"
 392         depends on (FB = y) && ATARI
 393         select FB_CFB_FILLRECT
 394         select FB_CFB_COPYAREA
 395         select FB_CFB_IMAGEBLIT
 396         help
 397           This is the frame buffer device driver for the builtin graphics
 398           chipset found in Ataris.
 399
 400 config FB_OF
 401         bool "Open Firmware frame buffer device support"
 402         depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
 403         select FB_CFB_FILLRECT
 404         select FB_CFB_COPYAREA
 405         select FB_CFB_IMAGEBLIT
 406         select FB_MACMODES
 407         help
 408           Say Y if you want support with Open Firmware for your graphics
 409           board.
 410
 411 config FB_CONTROL
 412         bool "Apple \"control\" display support"
 413         depends on (FB = y) && PPC_PMAC && PPC32
 414         select FB_CFB_FILLRECT
 415         select FB_CFB_COPYAREA
 416         select FB_CFB_IMAGEBLIT
 417         select FB_MACMODES
 418         help
 419           This driver supports a frame buffer for the graphics adapter in the
 420           Power Macintosh 7300 and others.
 421
 422 config FB_PLATINUM
 423         bool "Apple \"platinum\" display support"
 424         depends on (FB = y) && PPC_PMAC && PPC32
 425         select FB_CFB_FILLRECT
 426         select FB_CFB_COPYAREA
 427         select FB_CFB_IMAGEBLIT
 428         select FB_MACMODES
 429         help
 430           This driver supports a frame buffer for the "platinum" graphics
 431           adapter in some Power Macintoshes.
 432
 433 config FB_VALKYRIE
 434         bool "Apple \"valkyrie\" display support"
 435         depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
 436         select FB_CFB_FILLRECT
 437         select FB_CFB_COPYAREA
 438         select FB_CFB_IMAGEBLIT
 439         select FB_MACMODES
 440         help
 441           This driver supports a frame buffer for the "valkyrie" graphics
 442           adapter in some Power Macintoshes.
 443
 444 config FB_CT65550
 445         bool "Chips 65550 display support"
 446         depends on (FB = y) && PPC32
 447         select FB_CFB_FILLRECT
 448         select FB_CFB_COPYAREA
 449         select FB_CFB_IMAGEBLIT
 450         help
 451           This is the frame buffer device driver for the Chips & Technologies
 452           65550 graphics chip in PowerBooks.
 453
 454 config FB_ASILIANT
 455         bool "Asiliant (Chips) 69000 display support"
 456         depends on (FB = y) && PCI
 457         select FB_CFB_FILLRECT
 458         select FB_CFB_COPYAREA
 459         select FB_CFB_IMAGEBLIT
 460         help
 461           This is the frame buffer device driver for the Asiliant 69030 chipset
 462
 463 config FB_IMSTT
 464         bool "IMS Twin Turbo display support"
 465         depends on (FB = y) && PCI
 466         select FB_CFB_IMAGEBLIT
 467         select FB_MACMODES if PPC
 468         help
 469           The IMS Twin Turbo is a PCI-based frame buffer card bundled with
 470           many Macintosh and compatible computers.
 471
 472 config FB_VGA16
 473         tristate "VGA 16-color graphics support"
 474         depends on FB && (X86 || PPC)
 475         select FB_CFB_FILLRECT
 476         select FB_CFB_COPYAREA
 477         select FB_CFB_IMAGEBLIT
 478         help
 479           This is the frame buffer device driver for VGA 16 color graphic
 480           cards. Say Y if you have such a card.
 481
 482           To compile this driver as a module, choose M here: the
 483           module will be called vga16fb.
 484
 485 config FB_STI
 486         tristate "HP STI frame buffer device support"
 487         depends on FB && PARISC
 488         select FB_CFB_FILLRECT
 489         select FB_CFB_COPYAREA
 490         select FB_CFB_IMAGEBLIT
 491         default y
 492         ---help---
 493           STI refers to the HP "Standard Text Interface" which is a set of
 494           BIOS routines contained in a ROM chip in HP PA-RISC based machines.
 495           Enabling this option will implement the linux framebuffer device
 496           using calls to the STI BIOS routines for initialisation.
 497
 498           If you enable this option, you will get a planar framebuffer device
 499           /dev/fb which will work on the most common HP graphic cards of the
 500           NGLE family, including the artist chips (in the 7xx and Bxxx series),
 501           HCRX, HCRX24, CRX, CRX24 and VisEG series.
 502
 503           It is safe to enable this option, so you should probably say "Y".
 504
 505 config FB_MAC
 506         bool "Generic Macintosh display support"
 507         depends on (FB = y) && MAC
 508         select FB_CFB_FILLRECT
 509         select FB_CFB_COPYAREA
 510         select FB_CFB_IMAGEBLIT
 511         select FB_MACMODES
 512
 513 #      bool '  Apple DAFB display support' CONFIG_FB_DAFB
 514 config FB_HP300
 515         bool
 516         depends on (FB = y) && HP300
 517         select FB_CFB_FILLRECT
 518         select FB_CFB_IMAGEBLIT
 519         default y
 520
 521 config FB_TGA
 522         tristate "TGA framebuffer support"
 523         depends on FB && ALPHA
 524         select FB_CFB_FILLRECT
 525         select FB_CFB_COPYAREA
 526         select FB_CFB_IMAGEBLIT
 527         select BITREVERSE
 528         help
 529           This is the frame buffer device driver for generic TGA graphic
 530           cards. Say Y if you have one of those.
 531
 532 config FB_VESA
 533         bool "VESA VGA graphics support"
 534         depends on (FB = y) && X86
 535         select FB_CFB_FILLRECT
 536         select FB_CFB_COPYAREA
 537         select FB_CFB_IMAGEBLIT
 538         select VIDEO_SELECT
 539         help
 540           This is the frame buffer device driver for generic VESA 2.0
 541           compliant graphic cards. The older VESA 1.2 cards are not supported.
 542           You will get a boot time penguin logo at no additional cost. Please
 543           read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
 544
 545 config FB_IMAC
 546         bool "Intel-based Macintosh Framebuffer Support"
 547         depends on (FB = y) && X86 && EFI
 548         select FB_CFB_FILLRECT
 549         select FB_CFB_COPYAREA
 550         select FB_CFB_IMAGEBLIT
 551         help
 552           This is the frame buffer device driver for the Intel-based Macintosh
 553
 554 config FB_HGA
 555         tristate "Hercules mono graphics support"
 556         depends on FB && X86
 557         select FB_CFB_FILLRECT
 558         select FB_CFB_COPYAREA
 559         select FB_CFB_IMAGEBLIT
 560         help
 561           Say Y here if you have a Hercules mono graphics card.
 562
 563           To compile this driver as a module, choose M here: the
 564           module will be called hgafb.
 565
 566           As this card technology is 15 years old, most people will answer N
 567           here.
 568
 569 config FB_HGA_ACCEL
 570         bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
 571         depends on FB_HGA && EXPERIMENTAL
 572         ---help---
 573         This will compile the Hercules mono graphics with
 574         acceleration functions.
 575
 576 config FB_SGIVW
 577         tristate "SGI Visual Workstation framebuffer support"
 578         depends on FB && X86_VISWS
 579         select FB_CFB_FILLRECT
 580         select FB_CFB_COPYAREA
 581         select FB_CFB_IMAGEBLIT
 582         help
 583           SGI Visual Workstation support for framebuffer graphics.
 584
 585 config FB_GBE
 586         bool "SGI Graphics Backend frame buffer support"
 587         depends on (FB = y) && (SGI_IP32 || X86_VISWS)
 588         select FB_CFB_FILLRECT
 589         select FB_CFB_COPYAREA
 590         select FB_CFB_IMAGEBLIT
 591         help
 592           This is the frame buffer device driver for SGI Graphics Backend.
 593           This chip is used in SGI O2 and Visual Workstation 320/540.
 594
 595 config FB_GBE_MEM
 596         int "Video memory size in MB"
 597         depends on FB_GBE
 598         default 4
 599         help
 600           This is the amount of memory reserved for the framebuffer,
 601           which can be any value between 1MB and 8MB.
 602
 603 config FB_SBUS
 604         bool "SBUS and UPA framebuffers"
 605         depends on (FB = y) && SPARC
 606         help
 607           Say Y if you want support for SBUS or UPA based frame buffer device.
 608
 609 config FB_BW2
 610         bool "BWtwo support"
 611         depends on (FB = y) && (SPARC && FB_SBUS)
 612         select FB_CFB_FILLRECT
 613         select FB_CFB_COPYAREA
 614         select FB_CFB_IMAGEBLIT
 615         help
 616           This is the frame buffer device driver for the BWtwo frame buffer.
 617
 618 config FB_CG3
 619         bool "CGthree support"
 620         depends on (FB = y) && (SPARC && FB_SBUS)
 621         select FB_CFB_FILLRECT
 622         select FB_CFB_COPYAREA
 623         select FB_CFB_IMAGEBLIT
 624         help
 625           This is the frame buffer device driver for the CGthree frame buffer.
 626
 627 config FB_CG6
 628         bool "CGsix (GX,TurboGX) support"
 629         depends on (FB = y) && (SPARC && FB_SBUS)
 630         select FB_CFB_COPYAREA
 631         select FB_CFB_IMAGEBLIT
 632         help
 633           This is the frame buffer device driver for the CGsix (GX, TurboGX)
 634           frame buffer.
 635
 636 config FB_PVR2
 637         tristate "NEC PowerVR 2 display support"
 638         depends on FB && SH_DREAMCAST
 639         select FB_CFB_FILLRECT
 640         select FB_CFB_COPYAREA
 641         select FB_CFB_IMAGEBLIT
 642         ---help---
 643           Say Y here if you have a PowerVR 2 card in your box.  If you plan to
 644           run linux on your Dreamcast, you will have to say Y here.
 645           This driver may or may not work on other PowerVR 2 cards, but is
 646           totally untested.  Use at your own risk.  If unsure, say N.
 647
 648           To compile this driver as a module, choose M here: the
 649           module will be called pvr2fb.
 650
 651           You can pass several parameters to the driver at boot time or at
 652           module load time.  The parameters look like "video=pvr2:XXX", where
 653           the meaning of XXX can be found at the end of the main source file
 654           (<file:drivers/video/pvr2fb.c>). Please see the file
 655           <file:Documentation/fb/pvr2fb.txt>.
 656
 657 config FB_EPSON1355
 658         bool "Epson 1355 framebuffer support"
 659         depends on (FB = y) && (SUPERH || ARCH_CEIVA)
 660         select FB_CFB_FILLRECT
 661         select FB_CFB_COPYAREA
 662         select FB_CFB_IMAGEBLIT
 663         help
 664           Build in support for the SED1355 Epson Research Embedded RAMDAC
 665           LCD/CRT Controller (since redesignated as the S1D13505) as a
 666           framebuffer.  Product specs at
 667           <http://www.erd.epson.com/vdc/html/products.htm>.
 668
 669 config FB_S1D13XXX
 670         tristate "Epson S1D13XXX framebuffer support"
 671         depends on FB
 672         select FB_CFB_FILLRECT
 673         select FB_CFB_COPYAREA
 674         select FB_CFB_IMAGEBLIT
 675         help
 676           Support for S1D13XXX framebuffer device family (currently only
 677           working with S1D13806). Product specs at
 678           <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
 679
 680 config FB_NVIDIA
 681         tristate "nVidia Framebuffer Support"
 682         depends on FB && PCI
 683         select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
 684         select FB_MODE_HELPERS
 685         select FB_CFB_FILLRECT
 686         select FB_CFB_COPYAREA
 687         select FB_CFB_IMAGEBLIT
 688         select BITREVERSE
 689         help
 690           This driver supports graphics boards with the nVidia chips, TNT
 691           and newer. For very old chipsets, such as the RIVA128, then use
 692           the rivafb.
 693           Say Y if you have such a graphics board.
 694
 695           To compile this driver as a module, choose M here: the
 696           module will be called nvidiafb.
 697
 698 config FB_NVIDIA_I2C
 699        bool "Enable DDC Support"
 700        depends on FB_NVIDIA
 701        select FB_DDC
 702        help
 703           This enables I2C support for nVidia Chipsets.  This is used
 704           only for getting EDID information from the attached display
 705           allowing for robust video mode handling and switching.
 706
 707           Because fbdev-2.6 requires that drivers must be able to
 708           independently validate video mode parameters, you should say Y
 709           here.
 710
 711 config FB_NVIDIA_BACKLIGHT
 712         bool "Support for backlight control"
 713         depends on FB_NVIDIA
 714         default y
 715         help
 716           Say Y here if you want to control the backlight of your display.
 717
 718 config FB_RIVA
 719         tristate "nVidia Riva support"
 720         depends on FB && PCI
 721         select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
 722         select FB_MODE_HELPERS
 723         select FB_CFB_FILLRECT
 724         select FB_CFB_COPYAREA
 725         select FB_CFB_IMAGEBLIT
 726         select BITREVERSE
 727         help
 728           This driver supports graphics boards with the nVidia Riva/Geforce
 729           chips.
 730           Say Y if you have such a graphics board.
 731
 732           To compile this driver as a module, choose M here: the
 733           module will be called rivafb.
 734
 735 config FB_RIVA_I2C
 736        bool "Enable DDC Support"
 737        depends on FB_RIVA
 738        select FB_DDC
 739        help
 740           This enables I2C support for nVidia Chipsets.  This is used
 741           only for getting EDID information from the attached display
 742           allowing for robust video mode handling and switching.
 743
 744           Because fbdev-2.6 requires that drivers must be able to
 745           independently validate video mode parameters, you should say Y
 746           here.
 747
 748 config FB_RIVA_DEBUG
 749         bool "Lots of debug output from Riva(nVidia) driver"
 750         depends on FB_RIVA
 751         default n
 752         help
 753           Say Y here if you want the Riva driver to output all sorts
 754           of debugging information to provide to the maintainer when
 755           something goes wrong.
 756
 757 config FB_RIVA_BACKLIGHT
 758         bool "Support for backlight control"
 759         depends on FB_RIVA
 760         default y
 761         help
 762           Say Y here if you want to control the backlight of your display.
 763
 764 config FB_I810
 765         tristate "Intel 810/815 support (EXPERIMENTAL)"
 766         depends on FB && EXPERIMENTAL && PCI && X86_32
 767         select AGP
 768         select AGP_INTEL
 769         select FB_MODE_HELPERS
 770         select FB_CFB_FILLRECT
 771         select FB_CFB_COPYAREA
 772         select FB_CFB_IMAGEBLIT
 773         help
 774           This driver supports the on-board graphics built in to the Intel 810
 775           and 815 chipsets.  Say Y if you have and plan to use such a board.
 776
 777           To compile this driver as a module, choose M here: the
 778           module will be called i810fb.
 779
 780           For more information, please read
 781           <file:Documentation/fb/intel810.txt>
 782
 783 config FB_I810_GTF
 784         bool "use VESA Generalized Timing Formula"
 785         depends on FB_I810
 786         help
 787           If you say Y, then the VESA standard, Generalized Timing Formula
 788           or GTF, will be used to calculate the required video timing values
 789           per video mode.  Since the GTF allows nondiscrete timings
 790           (nondiscrete being a range of values as opposed to discrete being a
 791           set of values), you'll be able to use any combination of horizontal
 792           and vertical resolutions, and vertical refresh rates without having
 793           to specify your own timing parameters.  This is especially useful
 794           to maximize the performance of an aging display, or if you just
 795           have a display with nonstandard dimensions. A VESA compliant
 796           monitor is recommended, but can still work with non-compliant ones.
 797           If you need or want this, then select this option. The timings may
 798           not be compliant with Intel's recommended values. Use at your own
 799           risk.
 800
 801           If you say N, the driver will revert to discrete video timings
 802           using a set recommended by Intel in their documentation.
 803
 804           If unsure, say N.
 805
 806 config FB_I810_I2C
 807         bool "Enable DDC Support"
 808         depends on FB_I810 && FB_I810_GTF
 809         select FB_DDC
 810         help
 811
 812 config FB_INTEL
 813         tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
 814         depends on FB && EXPERIMENTAL && PCI && X86
 815         select AGP
 816         select AGP_INTEL
 817         select FB_MODE_HELPERS
 818         select FB_CFB_FILLRECT
 819         select FB_CFB_COPYAREA
 820         select FB_CFB_IMAGEBLIT
 821         help
 822           This driver supports the on-board graphics built in to the Intel
 823           830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
 824           Say Y if you have and plan to use such a board.
 825
 826           If you say Y here and want DDC/I2C support you must first say Y to
 827           "I2C support" and "I2C bit-banging support" in the character devices
 828           section.
 829
 830           If you say M here then "I2C support" and "I2C bit-banging support"
 831           can be build either as modules or built-in.
 832
 833           To compile this driver as a module, choose M here: the
 834           module will be called intelfb.
 835
 836           For more information, please read <file:Documentation/fb/intelfb.txt>
 837
 838 config FB_INTEL_DEBUG
 839         bool "Intel driver Debug Messages"
 840         depends on FB_INTEL
 841         ---help---
 842           Say Y here if you want the Intel driver to output all sorts
 843           of debugging information to provide to the maintainer when
 844           something goes wrong.
 845
 846 config FB_INTEL_I2C
 847         bool "DDC/I2C for Intel framebuffer support"
 848         depends on FB_INTEL
 849         select FB_DDC
 850         default y
 851         help
 852           Say Y here if you want DDC/I2C support for your on-board Intel graphics.
 853
 854 config FB_MATROX
 855         tristate "Matrox acceleration"
 856         depends on FB && PCI
 857         select FB_CFB_FILLRECT
 858         select FB_CFB_COPYAREA
 859         select FB_CFB_IMAGEBLIT
 860         select FB_TILEBLITTING
 861         select FB_MACMODES if PPC_PMAC
 862         ---help---
 863           Say Y here if you have a Matrox Millennium, Matrox Millennium II,
 864           Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
 865           Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
 866           Matrox G400, G450 or G550 card in your box.
 867
 868           To compile this driver as a module, choose M here: the
 869           module will be called matroxfb.
 870
 871           You can pass several parameters to the driver at boot time or at
 872           module load time. The parameters look like "video=matrox:XXX", and
 873           are described in <file:Documentation/fb/matroxfb.txt>.
 874
 875 config FB_MATROX_MILLENIUM
 876         bool "Millennium I/II support"
 877         depends on FB_MATROX
 878         help
 879           Say Y here if you have a Matrox Millennium or Matrox Millennium II
 880           video card. If you select "Advanced lowlevel driver options" below,
 881           you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
 882           packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
 883           also use font widths different from 8.
 884
 885 config FB_MATROX_MYSTIQUE
 886         bool "Mystique support"
 887         depends on FB_MATROX
 888         help
 889           Say Y here if you have a Matrox Mystique or Matrox Mystique 220
 890           video card. If you select "Advanced lowlevel driver options" below,
 891           you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
 892           packed pixel and 32 bpp packed pixel. You can also use font widths
 893           different from 8.
 894
 895 config FB_MATROX_G
 896         bool "G100/G200/G400/G450/G550 support"
 897         depends on FB_MATROX
 898         ---help---
 899           Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
 900           video card. If you select "Advanced lowlevel driver options", you
 901           should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
 902           pixel and 32 bpp packed pixel. You can also use font widths
 903           different from 8.
 904
 905           If you need support for G400 secondary head, you must first say Y to
 906           "I2C support" in the character devices section, and then to
 907           "Matrox I2C support" and "G400 second head support" here in the
 908           framebuffer section. G450/G550 secondary head and digital output
 909           are supported without additional modules.
 910
 911           The driver starts in monitor mode. You must use the matroxset tool
 912           (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
 913           swap primary and secondary head outputs, or to change output mode.
 914           Secondary head driver always start in 640x480 resolution and you
 915           must use fbset to change it.
 916
 917           Do not forget that second head supports only 16 and 32 bpp
 918           packed pixels, so it is a good idea to compile them into the kernel
 919           too. You can use only some font widths, as the driver uses generic
 920           painting procedures (the secondary head does not use acceleration
 921           engine).
 922
 923           G450/G550 hardware can display TV picture only from secondary CRTC,
 924           and it performs no scaling, so picture must have 525 or 625 lines.
 925
 926 config FB_MATROX_I2C
 927         tristate "Matrox I2C support"
 928         depends on FB_MATROX
 929         select FB_DDC
 930         ---help---
 931           This drivers creates I2C buses which are needed for accessing the
 932           DDC (I2C) bus present on all Matroxes, an I2C bus which
 933           interconnects Matrox optional devices, like MGA-TVO on G200 and
 934           G400, and the secondary head DDC bus, present on G400 only.
 935
 936           You can say Y or M here if you want to experiment with monitor
 937           detection code. You must say Y or M here if you want to use either
 938           second head of G400 or MGA-TVO on G200 or G400.
 939
 940           If you compile it as module, it will create a module named
 941           i2c-matroxfb.
 942
 943 config FB_MATROX_MAVEN
 944         tristate "G400 second head support"
 945         depends on FB_MATROX_G && FB_MATROX_I2C
 946         ---help---
 947           WARNING !!! This support does not work with G450 !!!
 948
 949           Say Y or M here if you want to use a secondary head (meaning two
 950           monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
 951           head is not compatible with accelerated XFree 3.3.x SVGA servers -
 952           secondary head output is blanked while you are in X. With XFree
 953           3.9.17 preview you can use both heads if you use SVGA over fbdev or
 954           the fbdev driver on first head and the fbdev driver on second head.
 955
 956           If you compile it as module, two modules are created,
 957           matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
 958           both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
 959           also load i2c-matroxfb to get it to run.
 960
 961           The driver starts in monitor mode and you must use the matroxset
 962           tool (available at
 963           <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
 964           PAL or NTSC or to swap primary and secondary head outputs.
 965           Secondary head driver also always start in 640x480 resolution, you
 966           must use fbset to change it.
 967
 968           Also do not forget that second head supports only 16 and 32 bpp
 969           packed pixels, so it is a good idea to compile them into the kernel
 970           too.  You can use only some font widths, as the driver uses generic
 971           painting procedures (the secondary head does not use acceleration
 972           engine).
 973
 974 config FB_MATROX_MULTIHEAD
 975         bool "Multihead support"
 976         depends on FB_MATROX
 977         ---help---
 978           Say Y here if you have more than one (supported) Matrox device in
 979           your computer and you want to use all of them for different monitors
 980           ("multihead"). If you have only one device, you should say N because
 981           the driver compiled with Y is larger and a bit slower, especially on
 982           ia32 (ix86).
 983
 984           If you said M to "Matrox unified accelerated driver" and N here, you
 985           will still be able to use several Matrox devices simultaneously:
 986           insert several instances of the module matroxfb into the kernel
 987           with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
 988           for the different Matrox devices. This method is slightly faster but
 989           uses 40 KB of kernel memory per Matrox card.
 990
 991           There is no need for enabling 'Matrox multihead support' if you have
 992           only one Matrox card in the box.
 993
 994 config FB_RADEON
 995         tristate "ATI Radeon display support"
 996         depends on FB && PCI
 997         select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
 998         select FB_MODE_HELPERS
 999         select FB_CFB_FILLRECT
1000         select FB_CFB_COPYAREA
1001         select FB_CFB_IMAGEBLIT
1002         select FB_MACMODES if PPC_OF
1003         help
1004           Choose this option if you want to use an ATI Radeon graphics card as
1005           a framebuffer device.  There are both PCI and AGP versions.  You
1006           don't need to choose this to run the Radeon in plain VGA mode.
1007
1008           If you say Y here and want DDC/I2C support you must first say Y to
1009           "I2C support" and "I2C bit-banging support" in the character devices
1010           section.
1011
1012           If you say M here then "I2C support" and "I2C bit-banging support"
1013           can be build either as modules or built-in.
1014
1015           There is a product page at
1016           http://apps.ati.com/ATIcompare/
1017
1018 config FB_RADEON_I2C
1019         bool "DDC/I2C for ATI Radeon support"
1020         depends on FB_RADEON
1021         select FB_DDC
1022         default y
1023         help
1024           Say Y here if you want DDC/I2C support for your Radeon board.
1025
1026 config FB_RADEON_BACKLIGHT
1027         bool "Support for backlight control"
1028         depends on FB_RADEON
1029         default y
1030         help
1031           Say Y here if you want to control the backlight of your display.
1032
1033 config FB_RADEON_DEBUG
1034         bool "Lots of debug output from Radeon driver"
1035         depends on FB_RADEON
1036         default n
1037         help
1038           Say Y here if you want the Radeon driver to output all sorts
1039           of debugging information to provide to the maintainer when
1040           something goes wrong.
1041
1042 config FB_ATY128
1043         tristate "ATI Rage128 display support"
1044         depends on FB && PCI
1045         select FB_CFB_FILLRECT
1046         select FB_CFB_COPYAREA
1047         select FB_CFB_IMAGEBLIT
1048         select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1049         select FB_MACMODES if PPC_PMAC
1050         help
1051           This driver supports graphics boards with the ATI Rage128 chips.
1052           Say Y if you have such a graphics board and read
1053           <file:Documentation/fb/aty128fb.txt>.
1054
1055           To compile this driver as a module, choose M here: the
1056           module will be called aty128fb.
1057
1058 config FB_ATY128_BACKLIGHT
1059         bool "Support for backlight control"
1060         depends on FB_ATY128
1061         default y
1062         help
1063           Say Y here if you want to control the backlight of your display.
1064
1065 config FB_ATY
1066         tristate "ATI Mach64 display support" if PCI || ATARI
1067         depends on FB && !SPARC32
1068         select FB_CFB_FILLRECT
1069         select FB_CFB_COPYAREA
1070         select FB_CFB_IMAGEBLIT
1071         select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1072         select FB_MACMODES if PPC
1073         help
1074           This driver supports graphics boards with the ATI Mach64 chips.
1075           Say Y if you have such a graphics board.
1076
1077           To compile this driver as a module, choose M here: the
1078           module will be called atyfb.
1079
1080 config FB_ATY_CT
1081         bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1082         depends on PCI && FB_ATY
1083         default y if SPARC64 && FB_PCI
1084         help
1085           Say Y here to support use of ATI's 64-bit Rage boards (or other
1086           boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1087           framebuffer device.  The ATI product support page for these boards
1088           is at <http://support.ati.com/products/pc/mach64/>.
1089
1090 config FB_ATY_GENERIC_LCD
1091         bool "Mach64 generic LCD support (EXPERIMENTAL)"
1092         depends on FB_ATY_CT
1093         help
1094           Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1095           Rage XC, or Rage XL chipset.
1096
1097 config FB_ATY_GX
1098         bool "Mach64 GX support" if PCI
1099         depends on FB_ATY
1100         default y if ATARI
1101         help
1102           Say Y here to support use of the ATI Mach64 Graphics Expression
1103           board (or other boards based on the Mach64 GX chipset) as a
1104           framebuffer device.  The ATI product support page for these boards
1105           is at
1106           <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1107
1108 config FB_ATY_BACKLIGHT
1109         bool "Support for backlight control"
1110         depends on FB_ATY
1111         default y
1112         help
1113           Say Y here if you want to control the backlight of your display.
1114
1115 config FB_S3
1116         tristate "S3 Trio/Virge support"
1117         depends on FB && PCI
1118         select FB_CFB_FILLRECT
1119         select FB_CFB_COPYAREA
1120         select FB_CFB_IMAGEBLIT
1121         select FB_TILEBLITTING
1122         select FB_SVGALIB
1123         ---help---
1124           Driver for graphics boards with S3 Trio / S3 Virge chip.
1125
1126 config FB_SAVAGE
1127         tristate "S3 Savage support"
1128         depends on FB && PCI && EXPERIMENTAL
1129         select FB_MODE_HELPERS
1130         select FB_CFB_FILLRECT
1131         select FB_CFB_COPYAREA
1132         select FB_CFB_IMAGEBLIT
1133         help
1134           This driver supports notebooks and computers with S3 Savage PCI/AGP
1135           chips.
1136
1137           Say Y if you have such a graphics card.
1138
1139           To compile this driver as a module, choose M here; the module
1140           will be called savagefb.
1141
1142 config FB_SAVAGE_I2C
1143        bool "Enable DDC2 Support"
1144        depends on FB_SAVAGE
1145        select FB_DDC
1146        help
1147           This enables I2C support for S3 Savage Chipsets.  This is used
1148           only for getting EDID information from the attached display
1149           allowing for robust video mode handling and switching.
1150
1151           Because fbdev-2.6 requires that drivers must be able to
1152           independently validate video mode parameters, you should say Y
1153           here.
1154
1155 config FB_SAVAGE_ACCEL
1156        bool "Enable Console Acceleration"
1157        depends on FB_SAVAGE
1158        default n
1159        help
1160           This option will compile in console acceleration support. If
1161           the resulting framebuffer console has bothersome glitches, then
1162           choose N here.
1163
1164 config FB_SIS
1165         tristate "SiS/XGI display support"
1166         depends on FB && PCI
1167         select FB_CFB_FILLRECT
1168         select FB_CFB_COPYAREA
1169         select FB_CFB_IMAGEBLIT
1170         help
1171           This is the frame buffer device driver for the SiS 300, 315, 330
1172           and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1173           Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1174
1175           To compile this driver as a module, choose M here; the module
1176           will be called sisfb.
1177
1178 config FB_SIS_300
1179         bool "SiS 300 series support"
1180         depends on FB_SIS
1181         help
1182           Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1183
1184 config FB_SIS_315
1185         bool "SiS 315/330/340 series and XGI support"
1186         depends on FB_SIS
1187         help
1188           Say Y here to support use of the SiS 315, 330 and 340 series
1189           (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1190           as XGI V3XT, V5, V8 and Z7.
1191
1192 config FB_NEOMAGIC
1193         tristate "NeoMagic display support"
1194         depends on FB && PCI
1195         select FB_MODE_HELPERS
1196         select FB_CFB_FILLRECT
1197         select FB_CFB_COPYAREA
1198         select FB_CFB_IMAGEBLIT
1199         help
1200           This driver supports notebooks with NeoMagic PCI chips.
1201           Say Y if you have such a graphics card.
1202
1203           To compile this driver as a module, choose M here: the
1204           module will be called neofb.
1205
1206 config FB_KYRO
1207         tristate "IMG Kyro support"
1208         depends on FB && PCI
1209         select FB_CFB_FILLRECT
1210         select FB_CFB_COPYAREA
1211         select FB_CFB_IMAGEBLIT
1212         help
1213           Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1214           graphics board.
1215
1216           To compile this driver as a module, choose M here: the
1217           module will be called kyrofb.
1218
1219 config FB_3DFX
1220         tristate "3Dfx Banshee/Voodoo3 display support"
1221         depends on FB && PCI
1222         select FB_CFB_IMAGEBLIT
1223         select FB_CFB_FILLRECT
1224         select FB_CFB_COPYAREA
1225         help
1226           This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1227           chips. Say Y if you have such a graphics board.
1228
1229           To compile this driver as a module, choose M here: the
1230           module will be called tdfxfb.
1231
1232 config FB_3DFX_ACCEL
1233         bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1234         depends on FB_3DFX && EXPERIMENTAL
1235         ---help---
1236         This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1237         with acceleration functions.
1238
1239
1240 config FB_VOODOO1
1241         tristate "3Dfx Voodoo Graphics (sst1) support"
1242         depends on FB && PCI
1243         select FB_CFB_FILLRECT
1244         select FB_CFB_COPYAREA
1245         select FB_CFB_IMAGEBLIT
1246         ---help---
1247           Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1248           Voodoo2 (cvg) based graphics card.
1249
1250           To compile this driver as a module, choose M here: the
1251           module will be called sstfb.
1252
1253           WARNING: Do not use any application that uses the 3D engine
1254           (namely glide) while using this driver.
1255           Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1256           options and other important info  support.
1257
1258 config FB_CYBLA
1259         tristate "Cyberblade/i1 support"
1260         depends on FB && PCI && X86_32 && !64BIT
1261         select FB_CFB_IMAGEBLIT
1262         select VIDEO_SELECT
1263         ---help---
1264           This driver is supposed to support the Trident Cyberblade/i1
1265           graphics core integrated in the VIA VT8601A North Bridge,
1266           also known as VIA Apollo PLE133.
1267
1268           Status:
1269            - Developed, tested and working on EPIA 5000 and EPIA 800.
1270            - Does work reliable on all systems with CRT/LCD connected to
1271              normal VGA ports.
1272            - Should work on systems that do use the internal LCD port, but
1273              this is absolutely not tested.
1274
1275           Character imageblit, copyarea and rectangle fill are hw accelerated,
1276           ypan scrolling is used by default.
1277
1278           Please do read <file:Documentation/fb/cyblafb/*>.
1279
1280           To compile this driver as a module, choose M here: the
1281           module will be called cyblafb.
1282
1283 config FB_TRIDENT
1284         tristate "Trident support"
1285         depends on FB && PCI
1286         select FB_CFB_FILLRECT
1287         select FB_CFB_COPYAREA
1288         select FB_CFB_IMAGEBLIT
1289         ---help---
1290           This driver is supposed to support graphics boards with the
1291           Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1292           but also on some motherboards. For more information, read
1293           <file:Documentation/fb/tridentfb.txt>
1294
1295           Cyberblade/i1 support will be removed soon, use the cyblafb driver
1296           instead.
1297
1298           Say Y if you have such a graphics board.
1299
1300
1301           To compile this driver as a module, choose M here: the
1302           module will be called tridentfb.
1303
1304 config FB_TRIDENT_ACCEL
1305         bool "Trident Acceleration functions (EXPERIMENTAL)"
1306         depends on FB_TRIDENT && EXPERIMENTAL
1307         ---help---
1308         This will compile the Trident frame buffer device with
1309         acceleration functions.
1310
1311 config FB_PM3
1312         tristate "Permedia3 support"
1313         depends on FB && PCI && BROKEN
1314         help
1315           This is the frame buffer device driver for the 3DLabs Permedia3
1316           chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1317           similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1318           and maybe other boards.
1319
1320 config FB_AU1100
1321         bool "Au1100 LCD Driver"
1322         depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1323
1324 config FB_AU1200
1325         bool "Au1200 LCD Driver"
1326         depends on (FB = y) && MIPS && SOC_AU1200
1327         select FB_CFB_FILLRECT
1328         select FB_CFB_COPYAREA
1329         select FB_CFB_IMAGEBLIT
1330         help
1331           This is the framebuffer driver for the AMD Au1200 SOC.  It can drive
1332           various panels and CRTs by passing in kernel cmd line option
1333           au1200fb:panel=<name>.
1334
1335 source "drivers/video/geode/Kconfig"
1336
1337 config FB_FFB
1338         bool "Creator/Creator3D/Elite3D support"
1339         depends on FB_SBUS && SPARC64
1340         select FB_CFB_COPYAREA
1341         select FB_CFB_IMAGEBLIT
1342         help
1343           This is the frame buffer device driver for the Creator, Creator3D,
1344           and Elite3D graphics boards.
1345
1346 config FB_TCX
1347         bool "TCX (SS4/SS5 only) support"
1348         depends on FB_SBUS
1349         select FB_CFB_FILLRECT
1350         select FB_CFB_COPYAREA
1351         select FB_CFB_IMAGEBLIT
1352         help
1353           This is the frame buffer device driver for the TCX 24/8bit frame
1354           buffer.
1355
1356 config FB_CG14
1357         bool "CGfourteen (SX) support"
1358         depends on FB_SBUS
1359         select FB_CFB_FILLRECT
1360         select FB_CFB_COPYAREA
1361         select FB_CFB_IMAGEBLIT
1362         help
1363           This is the frame buffer device driver for the CGfourteen frame
1364           buffer on Desktop SPARCsystems with the SX graphics option.
1365
1366 config FB_P9100
1367         bool "P9100 (Sparcbook 3 only) support"
1368         depends on FB_SBUS
1369         select FB_CFB_FILLRECT
1370         select FB_CFB_COPYAREA
1371         select FB_CFB_IMAGEBLIT
1372         help
1373           This is the frame buffer device driver for the P9100 card
1374           supported on Sparcbook 3 machines.
1375
1376 config FB_LEO
1377         bool "Leo (ZX) support"
1378         depends on FB_SBUS
1379         select FB_CFB_FILLRECT
1380         select FB_CFB_COPYAREA
1381         select FB_CFB_IMAGEBLIT
1382         help
1383           This is the frame buffer device driver for the SBUS-based Sun ZX
1384           (leo) frame buffer cards.
1385
1386 config FB_PCI
1387         bool "PCI framebuffers"
1388         depends on (FB = y) && PCI && SPARC
1389
1390 config FB_IGA
1391         bool "IGA 168x display support"
1392         depends on SPARC32 && FB_PCI
1393         select FB_CFB_FILLRECT
1394         select FB_CFB_COPYAREA
1395         select FB_CFB_IMAGEBLIT
1396         help
1397           This is the framebuffer device for the INTERGRAPHICS 1680 and
1398           successor frame buffer cards.
1399
1400 config FB_HIT
1401         tristate "HD64461 Frame Buffer support"
1402         depends on FB && HD64461
1403         select FB_CFB_FILLRECT
1404         select FB_CFB_COPYAREA
1405         select FB_CFB_IMAGEBLIT
1406         help
1407           This is the frame buffer device driver for the Hitachi HD64461 LCD
1408           frame buffer card.
1409
1410 config FB_PMAG_AA
1411         bool "PMAG-AA TURBOchannel framebuffer support"
1412         depends on (FB = y) && TC
1413         select FB_CFB_FILLRECT
1414         select FB_CFB_COPYAREA
1415         select FB_CFB_IMAGEBLIT
1416         help
1417           Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1418           used mainly in the MIPS-based DECstation series.
1419
1420 config FB_PMAG_BA
1421         tristate "PMAG-BA TURBOchannel framebuffer support"
1422         depends on FB && TC
1423         select FB_CFB_FILLRECT
1424         select FB_CFB_COPYAREA
1425         select FB_CFB_IMAGEBLIT
1426         help
1427           Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1428           used mainly in the MIPS-based DECstation series.
1429
1430 config FB_PMAGB_B
1431         tristate "PMAGB-B TURBOchannel framebuffer support"
1432         depends on TC
1433         select FB_CFB_FILLRECT
1434         select FB_CFB_COPYAREA
1435         select FB_CFB_IMAGEBLIT
1436         help
1437           Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1438           in the MIPS-based DECstation series. The card is currently only
1439           supported in 1280x1024x8 mode.
1440
1441 config FB_MAXINE
1442         bool "Maxine (Personal DECstation) onboard framebuffer support"
1443         depends on (FB = y) && MACH_DECSTATION
1444         select FB_CFB_FILLRECT
1445         select FB_CFB_COPYAREA
1446         select FB_CFB_IMAGEBLIT
1447         help
1448           Support for the onboard framebuffer (1024x768x8) in the Personal
1449           DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1450           Codename "Maxine").
1451
1452 config FB_TX3912
1453         bool "TMPTX3912/PR31700 frame buffer support"
1454         depends on (FB = y) && NINO
1455         select FB_CFB_FILLRECT
1456         select FB_CFB_COPYAREA
1457         select FB_CFB_IMAGEBLIT
1458         help
1459           The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1460           see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1461
1462           Say Y here to enable kernel support for the on-board framebuffer.
1463
1464 config FB_G364
1465         bool "G364 frame buffer support"
1466         depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1467         select FB_CFB_FILLRECT
1468         select FB_CFB_COPYAREA
1469         select FB_CFB_IMAGEBLIT
1470         help
1471           The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1472           Olivetti M700-10 systems.
1473
1474 config FB_68328
1475         bool "Motorola 68328 native frame buffer support"
1476         depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1477         select FB_CFB_FILLRECT
1478         select FB_CFB_COPYAREA
1479         select FB_CFB_IMAGEBLIT
1480         help
1481           Say Y here if you want to support the built-in frame buffer of
1482           the Motorola 68328 CPU family.
1483
1484 config FB_PXA
1485         tristate "PXA LCD framebuffer support"
1486         depends on FB && ARCH_PXA
1487         select FB_CFB_FILLRECT
1488         select FB_CFB_COPYAREA
1489         select FB_CFB_IMAGEBLIT
1490         ---help---
1491           Frame buffer driver for the built-in LCD controller in the Intel
1492           PXA2x0 processor.
1493
1494           This driver is also available as a module ( = code which can be
1495           inserted and removed from the running kernel whenever you want). The
1496           module will be called pxafb. If you want to compile it as a module,
1497           say M here and read <file:Documentation/modules.txt>.
1498
1499           If unsure, say N.
1500
1501 config FB_PXA_PARAMETERS
1502         bool "PXA LCD command line parameters"
1503         default n
1504         depends on FB_PXA
1505         ---help---
1506           Enable the use of kernel command line or module parameters
1507           to configure the physical properties of the LCD panel when
1508           using the PXA LCD driver.
1509
1510           This option allows you to override the panel parameters
1511           supplied by the platform in order to support multiple
1512           different models of flatpanel. If you will only be using a
1513           single model of flatpanel then you can safely leave this
1514           option disabled.
1515
1516           <file:Documentation/fb/pxafb.txt> describes the available parameters.
1517
1518 config FB_MBX
1519         tristate "2700G LCD framebuffer support"
1520         depends on FB && ARCH_PXA
1521         select FB_CFB_FILLRECT
1522         select FB_CFB_COPYAREA
1523         select FB_CFB_IMAGEBLIT
1524         ---help---
1525           Framebuffer driver for the Intel 2700G (Marathon) Graphics
1526           Accelerator
1527
1528 config FB_MBX_DEBUG
1529        bool "Enable debugging info via debugfs"
1530        depends on FB_MBX && DEBUG_FS
1531        default n
1532        ---help---
1533          Enable this if you want debugging information using the debug
1534          filesystem (debugfs)
1535
1536          If unsure, say N.
1537
1538 config FB_W100
1539         tristate "W100 frame buffer support"
1540         depends on FB && PXA_SHARPSL
1541         select FB_CFB_FILLRECT
1542         select FB_CFB_COPYAREA
1543         select FB_CFB_IMAGEBLIT
1544         ---help---
1545           Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1546
1547           This driver is also available as a module ( = code which can be
1548           inserted and removed from the running kernel whenever you want). The
1549           module will be called w100fb. If you want to compile it as a module,
1550           say M here and read <file:Documentation/modules.txt>.
1551
1552           If unsure, say N.
1553
1554 config FB_S3C2410
1555         tristate "S3C2410 LCD framebuffer support"
1556         depends on FB && ARCH_S3C2410
1557         select FB_CFB_FILLRECT
1558         select FB_CFB_COPYAREA
1559         select FB_CFB_IMAGEBLIT
1560         ---help---
1561           Frame buffer driver for the built-in LCD controller in the Samsung
1562           S3C2410 processor.
1563
1564           This driver is also available as a module ( = code which can be
1565           inserted and removed from the running kernel whenever you want). The
1566           module will be called s3c2410fb. If you want to compile it as a module,
1567           say M here and read <file:Documentation/modules.txt>.
1568
1569           If unsure, say N.
1570 config FB_S3C2410_DEBUG
1571         bool "S3C2410 lcd debug messages"
1572         depends on FB_S3C2410
1573         help
1574           Turn on debugging messages. Note that you can set/unset at run time
1575           through sysfs
1576
1577 config FB_SM501
1578         tristate "Silicon Motion SM501 framebuffer support"
1579         depends on FB && MFD_SM501
1580         select FB_CFB_FILLRECT
1581         select FB_CFB_COPYAREA
1582         select FB_CFB_IMAGEBLIT
1583         ---help---
1584           Frame buffer driver for the CRT and LCD controllers in the Silicon
1585           Motion SM501.
1586
1587           This driver is also available as a module ( = code which can be
1588           inserted and removed from the running kernel whenever you want). The
1589           module will be called sm501fb. If you want to compile it as a module,
1590           say M here and read <file:Documentation/modules.txt>.
1591
1592           If unsure, say N.
1593
1594
1595 config FB_PNX4008_DUM
1596         tristate "Display Update Module support on Philips PNX4008 board"
1597         depends on FB && ARCH_PNX4008
1598         ---help---
1599           Say Y here to enable support for PNX4008 Display Update Module (DUM)
1600
1601 config FB_PNX4008_DUM_RGB
1602         tristate "RGB Framebuffer support on Philips PNX4008 board"
1603         depends on FB_PNX4008_DUM
1604         select FB_CFB_FILLRECT
1605         select FB_CFB_COPYAREA
1606         select FB_CFB_IMAGEBLIT
1607         ---help---
1608           Say Y here to enable support for PNX4008 RGB Framebuffer
1609
1610 config FB_IBM_GXT4500
1611         tristate "Framebuffer support for IBM GXT4500P adaptor"
1612         depends on PPC
1613         select FB_CFB_FILLRECT
1614         select FB_CFB_COPYAREA
1615         select FB_CFB_IMAGEBLIT
1616         ---help---
1617           Say Y here to enable support for the IBM GXT4500P display
1618           adaptor, found on some IBM System P (pSeries) machines.
1619
1620 config FB_PS3
1621         bool "PS3 GPU framebuffer driver"
1622         depends on (FB = y) && PS3_PS3AV
1623         select FB_CFB_FILLRECT
1624         select FB_CFB_COPYAREA
1625         select FB_CFB_IMAGEBLIT
1626         ---help---
1627           Include support for the virtual frame buffer in the PS3 platform.
1628
1629 config FB_PS3_DEFAULT_SIZE_M
1630         int "PS3 default frame buffer size (in MiB)"
1631         depends on FB_PS3
1632         default 18
1633         ---help---
1634           This is the default size (in MiB) of the virtual frame buffer in
1635           the PS3.
1636           The default value can be overridden on the kernel command line
1637           using the "ps3fb" option (e.g. "ps3fb=9M");
1638
1639 config FB_VIRTUAL
1640         tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1641         depends on FB
1642         select FB_CFB_FILLRECT
1643         select FB_CFB_COPYAREA
1644         select FB_CFB_IMAGEBLIT
1645         ---help---
1646           This is a `virtual' frame buffer device. It operates on a chunk of
1647           unswappable kernel memory instead of on the memory of a graphics
1648           board. This means you cannot see any output sent to this frame
1649           buffer device, while it does consume precious memory. The main use
1650           of this frame buffer device is testing and debugging the frame
1651           buffer subsystem. Do NOT enable it for normal systems! To protect
1652           the innocent, it has to be enabled explicitly at boot time using the
1653           kernel option `video=vfb:'.
1654
1655           To compile this driver as a module, choose M here: the
1656           module will be called vfb. In order to load it, you must use
1657           the vfb_enable=1 option.
1658
1659           If unsure, say N.
1660
1661 if VT
1662         source "drivers/video/console/Kconfig"
1663 endif
1664
1665 if FB || SGI_NEWPORT_CONSOLE
1666         source "drivers/video/logo/Kconfig"
1667 endif
1668
1669 endmenu
1670