1# 2# Video configuration 3# 4 5menu "Graphics support" 6 depends on HAS_IOMEM 7 8config HAVE_FB_ATMEL 9 bool 10 11config HAVE_FB_IMX 12 bool 13 14source "drivers/char/agp/Kconfig" 15 16source "drivers/gpu/vga/Kconfig" 17 18source "drivers/gpu/drm/Kconfig" 19 20config VGASTATE 21 tristate 22 default n 23 24config VIDEO_OUTPUT_CONTROL 25 tristate "Lowlevel video output switch controls" 26 help 27 This framework adds support for low-level control of the video 28 output switch. 29 30menuconfig FB 31 tristate "Support for frame buffer devices" 32 ---help--- 33 The frame buffer device provides an abstraction for the graphics 34 hardware. It represents the frame buffer of some video hardware and 35 allows application software to access the graphics hardware through 36 a well-defined interface, so the software doesn't need to know 37 anything about the low-level (hardware register) stuff. 38 39 Frame buffer devices work identically across the different 40 architectures supported by Linux and make the implementation of 41 application programs easier and more portable; at this point, an X 42 server exists which uses the frame buffer device exclusively. 43 On several non-X86 architectures, the frame buffer device is the 44 only way to use the graphics hardware. 45 46 The device is accessed through special device nodes, usually located 47 in the /dev directory, i.e. /dev/fb*. 48 49 You need an utility program called fbset to make full use of frame 50 buffer devices. Please read <file:Documentation/fb/framebuffer.txt> 51 and the Framebuffer-HOWTO at 52 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more 53 information. 54 55 Say Y here and to the driver for your graphics board below if you 56 are compiling a kernel for a non-x86 architecture. 57 58 If you are compiling for the x86 architecture, you can say Y if you 59 want to play with it, but it is not essential. Please note that 60 running graphical applications that directly touch the hardware 61 (e.g. an accelerated X server) and that are not frame buffer 62 device-aware may cause unexpected results. If unsure, say N. 63 64config FIRMWARE_EDID 65 bool "Enable firmware EDID" 66 depends on FB 67 default n 68 ---help--- 69 This enables access to the EDID transferred from the firmware. 70 On the i386, this is from the Video BIOS. Enable this if DDC/I2C 71 transfers do not work for your driver and if you are using 72 nvidiafb, i810fb or savagefb. 73 74 In general, choosing Y for this option is safe. If you 75 experience extremely long delays while booting before you get 76 something on your display, try setting this to N. Matrox cards in 77 combination with certain motherboards and monitors are known to 78 suffer from this problem. 79 80config FB_DDC 81 tristate 82 depends on FB 83 select I2C_ALGOBIT 84 select I2C 85 default n 86 87config FB_BOOT_VESA_SUPPORT 88 bool 89 depends on FB 90 default n 91 ---help--- 92 If true, at least one selected framebuffer driver can take advantage 93 of VESA video modes set at an early boot stage via the vga= parameter. 94 95config FB_CFB_FILLRECT 96 tristate 97 depends on FB 98 default n 99 ---help--- 100 Include the cfb_fillrect function for generic software rectangle 101 filling. This is used by drivers that don't provide their own 102 (accelerated) version. 103 104config FB_CFB_COPYAREA 105 tristate 106 depends on FB 107 default n 108 ---help--- 109 Include the cfb_copyarea function for generic software area copying. 110 This is used by drivers that don't provide their own (accelerated) 111 version. 112 113config FB_CFB_IMAGEBLIT 114 tristate 115 depends on FB 116 default n 117 ---help--- 118 Include the cfb_imageblit function for generic software image 119 blitting. This is used by drivers that don't provide their own 120 (accelerated) version. 121 122config FB_CFB_REV_PIXELS_IN_BYTE 123 bool 124 depends on FB 125 default n 126 ---help--- 127 Allow generic frame-buffer functions to work on displays with 1, 2 128 and 4 bits per pixel depths which has opposite order of pixels in 129 byte order to bytes in long order. 130 131config FB_SYS_FILLRECT 132 tristate 133 depends on FB 134 default n 135 ---help--- 136 Include the sys_fillrect function for generic software rectangle 137 filling. This is used by drivers that don't provide their own 138 (accelerated) version and the framebuffer is in system RAM. 139 140config FB_SYS_COPYAREA 141 tristate 142 depends on FB 143 default n 144 ---help--- 145 Include the sys_copyarea function for generic software area copying. 146 This is used by drivers that don't provide their own (accelerated) 147 version and the framebuffer is in system RAM. 148 149config FB_SYS_IMAGEBLIT 150 tristate 151 depends on FB 152 default n 153 ---help--- 154 Include the sys_imageblit function for generic software image 155 blitting. This is used by drivers that don't provide their own 156 (accelerated) version and the framebuffer is in system RAM. 157 158menuconfig FB_FOREIGN_ENDIAN 159 bool "Framebuffer foreign endianness support" 160 depends on FB 161 ---help--- 162 This menu will let you enable support for the framebuffers with 163 non-native endianness (e.g. Little-Endian framebuffer on a 164 Big-Endian machine). Most probably you don't have such hardware, 165 so it's safe to say "n" here. 166 167choice 168 prompt "Choice endianness support" 169 depends on FB_FOREIGN_ENDIAN 170 171config FB_BOTH_ENDIAN 172 bool "Support for Big- and Little-Endian framebuffers" 173 174config FB_BIG_ENDIAN 175 bool "Support for Big-Endian framebuffers only" 176 177config FB_LITTLE_ENDIAN 178 bool "Support for Little-Endian framebuffers only" 179 180endchoice 181 182config FB_SYS_FOPS 183 tristate 184 depends on FB 185 default n 186 187config FB_DEFERRED_IO 188 bool 189 depends on FB 190 191config FB_HECUBA 192 tristate 193 depends on FB 194 depends on FB_DEFERRED_IO 195 196config FB_SVGALIB 197 tristate 198 depends on FB 199 default n 200 ---help--- 201 Common utility functions useful to fbdev drivers of VGA-based 202 cards. 203 204config FB_MACMODES 205 tristate 206 depends on FB 207 default n 208 209config FB_BACKLIGHT 210 bool 211 depends on FB 212 select BACKLIGHT_LCD_SUPPORT 213 select BACKLIGHT_CLASS_DEVICE 214 default n 215 216config FB_MODE_HELPERS 217 bool "Enable Video Mode Handling Helpers" 218 depends on FB 219 default n 220 ---help--- 221 This enables functions for handling video modes using the 222 Generalized Timing Formula and the EDID parser. A few drivers rely 223 on this feature such as the radeonfb, rivafb, and the i810fb. If 224 your driver does not take advantage of this feature, choosing Y will 225 just increase the kernel size by about 5K. 226 227config FB_TILEBLITTING 228 bool "Enable Tile Blitting Support" 229 depends on FB 230 default n 231 ---help--- 232 This enables tile blitting. Tile blitting is a drawing technique 233 where the screen is divided into rectangular sections (tiles), whereas 234 the standard blitting divides the screen into pixels. Because the 235 default drawing element is a tile, drawing functions will be passed 236 parameters in terms of number of tiles instead of number of pixels. 237 For example, to draw a single character, instead of using bitmaps, 238 an index to an array of bitmaps will be used. To clear or move a 239 rectangular section of a screen, the rectangle will be described in 240 terms of number of tiles in the x- and y-axis. 241 242 This is particularly important to one driver, matroxfb. If 243 unsure, say N. 244 245comment "Frame buffer hardware drivers" 246 depends on FB 247 248config FB_CIRRUS 249 tristate "Cirrus Logic support" 250 depends on FB && (ZORRO || PCI) 251 select FB_CFB_FILLRECT 252 select FB_CFB_COPYAREA 253 select FB_CFB_IMAGEBLIT 254 ---help--- 255 This enables support for Cirrus Logic GD542x/543x based boards on 256 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum. 257 258 If you have a PCI-based system, this enables support for these 259 chips: GD-543x, GD-544x, GD-5480. 260 261 Please read the file <file:Documentation/fb/cirrusfb.txt>. 262 263 Say N unless you have such a graphics board or plan to get one 264 before you next recompile the kernel. 265 266config FB_PM2 267 tristate "Permedia2 support" 268 depends on FB && ((AMIGA && BROKEN) || PCI) 269 select FB_CFB_FILLRECT 270 select FB_CFB_COPYAREA 271 select FB_CFB_IMAGEBLIT 272 help 273 This is the frame buffer device driver for cards based on 274 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips. 275 The driver was tested on the following cards: 276 Diamond FireGL 1000 PRO AGP 277 ELSA Gloria Synergy PCI 278 Appian Jeronimo PRO (both heads) PCI 279 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI 280 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC 281 ASK Graphic Blaster Exxtreme AGP 282 283 To compile this driver as a module, choose M here: the 284 module will be called pm2fb. 285 286config FB_PM2_FIFO_DISCONNECT 287 bool "enable FIFO disconnect feature" 288 depends on FB_PM2 && PCI 289 help 290 Support the Permedia2 FIFO disconnect feature. 291 292config FB_ARMCLCD 293 tristate "ARM PrimeCell PL110 support" 294 depends on FB && ARM && ARM_AMBA 295 select FB_CFB_FILLRECT 296 select FB_CFB_COPYAREA 297 select FB_CFB_IMAGEBLIT 298 help 299 This framebuffer device driver is for the ARM PrimeCell PL110 300 Colour LCD controller. ARM PrimeCells provide the building 301 blocks for System on a Chip devices. 302 303 If you want to compile this as a module (=code which can be 304 inserted into and removed from the running kernel), say M 305 here and read <file:Documentation/kbuild/modules.txt>. The module 306 will be called amba-clcd. 307 308choice 309 310 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X) 311 prompt "LCD Panel" 312 default FB_ARMCLCD_SHARP_LQ035Q7DB02 313 314config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT 315 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC" 316 help 317 This is an implementation of the Sharp LQ035Q7DB02, a 3.5" 318 color QVGA, HRTFT panel. The LogicPD device includes 319 an integrated HRTFT controller IC. 320 The native resolution is 240x320. 321 322config FB_ARMCLCD_SHARP_LQ057Q3DC02 323 bool "LogicPD LCD 5.7\" QVGA" 324 help 325 This is an implementation of the Sharp LQ057Q3DC02, a 5.7" 326 color QVGA, TFT panel. The LogicPD device includes an 327 The native resolution is 320x240. 328 329config FB_ARMCLCD_SHARP_LQ64D343 330 bool "LogicPD LCD 6.4\" VGA" 331 help 332 This is an implementation of the Sharp LQ64D343, a 6.4" 333 color VGA, TFT panel. The LogicPD device includes an 334 The native resolution is 640x480. 335 336config FB_ARMCLCD_SHARP_LQ10D368 337 bool "LogicPD LCD 10.4\" VGA" 338 help 339 This is an implementation of the Sharp LQ10D368, a 10.4" 340 color VGA, TFT panel. The LogicPD device includes an 341 The native resolution is 640x480. 342 343 344config FB_ARMCLCD_SHARP_LQ121S1DG41 345 bool "LogicPD LCD 12.1\" SVGA" 346 help 347 This is an implementation of the Sharp LQ121S1DG41, a 12.1" 348 color SVGA, TFT panel. The LogicPD device includes an 349 The native resolution is 800x600. 350 351 This panel requires a clock rate may be an integer fraction 352 of the base LCDCLK frequency. The driver will select the 353 highest frequency available that is lower than the maximum 354 allowed. The panel may flicker if the clock rate is 355 slower than the recommended minimum. 356 357config FB_ARMCLCD_AUO_A070VW01_WIDE 358 bool "AU Optronics A070VW01 LCD 7.0\" WIDE" 359 help 360 This is an implementation of the AU Optronics, a 7.0" 361 WIDE Color. The native resolution is 234x480. 362 363config FB_ARMCLCD_HITACHI 364 bool "Hitachi Wide Screen 800x480" 365 help 366 This is an implementation of the Hitachi 800x480. 367 368endchoice 369 370 371config FB_ACORN 372 bool "Acorn VIDC support" 373 depends on (FB = y) && ARM && ARCH_ACORN 374 select FB_CFB_FILLRECT 375 select FB_CFB_COPYAREA 376 select FB_CFB_IMAGEBLIT 377 help 378 This is the frame buffer device driver for the Acorn VIDC graphics 379 hardware found in Acorn RISC PCs and other ARM-based machines. If 380 unsure, say N. 381 382config FB_CLPS711X 383 bool "CLPS711X LCD support" 384 depends on (FB = y) && ARM && ARCH_CLPS711X 385 select FB_CFB_FILLRECT 386 select FB_CFB_COPYAREA 387 select FB_CFB_IMAGEBLIT 388 help 389 Say Y to enable the Framebuffer driver for the CLPS7111 and 390 EP7212 processors. 391 392config FB_SA1100 393 bool "SA-1100 LCD support" 394 depends on (FB = y) && ARM && ARCH_SA1100 395 select FB_CFB_FILLRECT 396 select FB_CFB_COPYAREA 397 select FB_CFB_IMAGEBLIT 398 help 399 This is a framebuffer device for the SA-1100 LCD Controller. 400 See <http://www.linux-fbdev.org/> for information on framebuffer 401 devices. 402 403 If you plan to use the LCD display with your SA-1100 system, say 404 Y here. 405 406config FB_IMX 407 tristate "Motorola i.MX LCD support" 408 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2) 409 select FB_CFB_FILLRECT 410 select FB_CFB_COPYAREA 411 select FB_CFB_IMAGEBLIT 412 413config FB_CYBER2000 414 tristate "CyberPro 2000/2010/5000 support" 415 depends on FB && PCI && (BROKEN || !SPARC64) 416 select FB_CFB_FILLRECT 417 select FB_CFB_COPYAREA 418 select FB_CFB_IMAGEBLIT 419 help 420 This enables support for the Integraphics CyberPro 20x0 and 5000 421 VGA chips used in the Rebel.com Netwinder and other machines. 422 Say Y if you have a NetWinder or a graphics card containing this 423 device, otherwise say N. 424 425config FB_APOLLO 426 bool 427 depends on (FB = y) && APOLLO 428 default y 429 select FB_CFB_FILLRECT 430 select FB_CFB_IMAGEBLIT 431 432config FB_Q40 433 bool 434 depends on (FB = y) && Q40 435 default y 436 select FB_CFB_FILLRECT 437 select FB_CFB_COPYAREA 438 select FB_CFB_IMAGEBLIT 439 440config FB_AMIGA 441 tristate "Amiga native chipset support" 442 depends on FB && AMIGA 443 help 444 This is the frame buffer device driver for the builtin graphics 445 chipset found in Amigas. 446 447 To compile this driver as a module, choose M here: the 448 module will be called amifb. 449 450config FB_AMIGA_OCS 451 bool "Amiga OCS chipset support" 452 depends on FB_AMIGA 453 help 454 This enables support for the original Agnus and Denise video chips, 455 found in the Amiga 1000 and most A500's and A2000's. If you intend 456 to run Linux on any of these systems, say Y; otherwise say N. 457 458config FB_AMIGA_ECS 459 bool "Amiga ECS chipset support" 460 depends on FB_AMIGA 461 help 462 This enables support for the Enhanced Chip Set, found in later 463 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If 464 you intend to run Linux on any of these systems, say Y; otherwise 465 say N. 466 467config FB_AMIGA_AGA 468 bool "Amiga AGA chipset support" 469 depends on FB_AMIGA 470 help 471 This enables support for the Advanced Graphics Architecture (also 472 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T 473 and CD32. If you intend to run Linux on any of these systems, say Y; 474 otherwise say N. 475 476config FB_FM2 477 bool "Amiga FrameMaster II/Rainbow II support" 478 depends on (FB = y) && ZORRO 479 select FB_CFB_FILLRECT 480 select FB_CFB_COPYAREA 481 select FB_CFB_IMAGEBLIT 482 help 483 This is the frame buffer device driver for the Amiga FrameMaster 484 card from BSC (exhibited 1992 but not shipped as a CBM product). 485 486config FB_ARC 487 tristate "Arc Monochrome LCD board support" 488 depends on FB && X86 489 select FB_SYS_FILLRECT 490 select FB_SYS_COPYAREA 491 select FB_SYS_IMAGEBLIT 492 select FB_SYS_FOPS 493 help 494 This enables support for the Arc Monochrome LCD board. The board 495 is based on the KS-108 lcd controller and is typically a matrix 496 of 2*n chips. This driver was tested with a 128x64 panel. This 497 driver supports it for use with x86 SBCs through a 16 bit GPIO 498 interface (8 bit data, 8 bit control). If you anticipate using 499 this driver, say Y or M; otherwise say N. You must specify the 500 GPIO IO address to be used for setting control and data. 501 502config FB_ATARI 503 bool "Atari native chipset support" 504 depends on (FB = y) && ATARI 505 select FB_CFB_FILLRECT 506 select FB_CFB_COPYAREA 507 select FB_CFB_IMAGEBLIT 508 help 509 This is the frame buffer device driver for the builtin graphics 510 chipset found in Ataris. 511 512config FB_OF 513 bool "Open Firmware frame buffer device support" 514 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI) 515 select FB_CFB_FILLRECT 516 select FB_CFB_COPYAREA 517 select FB_CFB_IMAGEBLIT 518 select FB_MACMODES 519 help 520 Say Y if you want support with Open Firmware for your graphics 521 board. 522 523config FB_CONTROL 524 bool "Apple \"control\" display support" 525 depends on (FB = y) && PPC_PMAC && PPC32 526 select FB_CFB_FILLRECT 527 select FB_CFB_COPYAREA 528 select FB_CFB_IMAGEBLIT 529 select FB_MACMODES 530 help 531 This driver supports a frame buffer for the graphics adapter in the 532 Power Macintosh 7300 and others. 533 534config FB_PLATINUM 535 bool "Apple \"platinum\" display support" 536 depends on (FB = y) && PPC_PMAC && PPC32 537 select FB_CFB_FILLRECT 538 select FB_CFB_COPYAREA 539 select FB_CFB_IMAGEBLIT 540 select FB_MACMODES 541 help 542 This driver supports a frame buffer for the "platinum" graphics 543 adapter in some Power Macintoshes. 544 545config FB_VALKYRIE 546 bool "Apple \"valkyrie\" display support" 547 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32)) 548 select FB_CFB_FILLRECT 549 select FB_CFB_COPYAREA 550 select FB_CFB_IMAGEBLIT 551 select FB_MACMODES 552 help 553 This driver supports a frame buffer for the "valkyrie" graphics 554 adapter in some Power Macintoshes. 555 556config FB_CT65550 557 bool "Chips 65550 display support" 558 depends on (FB = y) && PPC32 && PCI 559 select FB_CFB_FILLRECT 560 select FB_CFB_COPYAREA 561 select FB_CFB_IMAGEBLIT 562 help 563 This is the frame buffer device driver for the Chips & Technologies 564 65550 graphics chip in PowerBooks. 565 566config FB_ASILIANT 567 bool "Asiliant (Chips) 69000 display support" 568 depends on (FB = y) && PCI 569 select FB_CFB_FILLRECT 570 select FB_CFB_COPYAREA 571 select FB_CFB_IMAGEBLIT 572 help 573 This is the frame buffer device driver for the Asiliant 69030 chipset 574 575config FB_IMSTT 576 bool "IMS Twin Turbo display support" 577 depends on (FB = y) && PCI 578 select FB_CFB_IMAGEBLIT 579 select FB_MACMODES if PPC 580 help 581 The IMS Twin Turbo is a PCI-based frame buffer card bundled with 582 many Macintosh and compatible computers. 583 584config FB_VGA16 585 tristate "VGA 16-color graphics support" 586 depends on FB && (X86 || PPC) 587 select FB_CFB_FILLRECT 588 select FB_CFB_COPYAREA 589 select FB_CFB_IMAGEBLIT 590 select VGASTATE 591 select FONT_8x16 if FRAMEBUFFER_CONSOLE 592 help 593 This is the frame buffer device driver for VGA 16 color graphic 594 cards. Say Y if you have such a card. 595 596 To compile this driver as a module, choose M here: the 597 module will be called vga16fb. 598 599config FB_BF54X_LQ043 600 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)" 601 depends on FB && (BF54x) && !BF542 602 select FB_CFB_FILLRECT 603 select FB_CFB_COPYAREA 604 select FB_CFB_IMAGEBLIT 605 help 606 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD 607 608config FB_BFIN_T350MCQB 609 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)" 610 depends on FB && BLACKFIN 611 select BFIN_GPTIMERS 612 select FB_CFB_FILLRECT 613 select FB_CFB_COPYAREA 614 select FB_CFB_IMAGEBLIT 615 help 616 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD 617 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI 618 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK. 619 620config FB_BFIN_LQ035Q1 621 tristate "SHARP LQ035Q1DH02 TFT LCD" 622 depends on FB && BLACKFIN && SPI 623 select FB_CFB_FILLRECT 624 select FB_CFB_COPYAREA 625 select FB_CFB_IMAGEBLIT 626 select BFIN_GPTIMERS 627 help 628 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on 629 the Blackfin Landscape LCD EZ-Extender Card. 630 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI 631 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK. 632 633 To compile this driver as a module, choose M here: the 634 module will be called bfin-lq035q1-fb. 635 636config FB_STI 637 tristate "HP STI frame buffer device support" 638 depends on FB && PARISC 639 select FB_CFB_FILLRECT 640 select FB_CFB_COPYAREA 641 select FB_CFB_IMAGEBLIT 642 select STI_CONSOLE 643 select VT 644 default y 645 ---help--- 646 STI refers to the HP "Standard Text Interface" which is a set of 647 BIOS routines contained in a ROM chip in HP PA-RISC based machines. 648 Enabling this option will implement the linux framebuffer device 649 using calls to the STI BIOS routines for initialisation. 650 651 If you enable this option, you will get a planar framebuffer device 652 /dev/fb which will work on the most common HP graphic cards of the 653 NGLE family, including the artist chips (in the 7xx and Bxxx series), 654 HCRX, HCRX24, CRX, CRX24 and VisEG series. 655 656 It is safe to enable this option, so you should probably say "Y". 657 658config FB_MAC 659 bool "Generic Macintosh display support" 660 depends on (FB = y) && MAC 661 select FB_CFB_FILLRECT 662 select FB_CFB_COPYAREA 663 select FB_CFB_IMAGEBLIT 664 select FB_MACMODES 665 666config FB_HP300 667 bool 668 depends on (FB = y) && DIO 669 select FB_CFB_IMAGEBLIT 670 default y 671 672config FB_TGA 673 tristate "TGA/SFB+ framebuffer support" 674 depends on FB && (ALPHA || TC) 675 select FB_CFB_FILLRECT 676 select FB_CFB_COPYAREA 677 select FB_CFB_IMAGEBLIT 678 select BITREVERSE 679 ---help--- 680 This is the frame buffer device driver for generic TGA and SFB+ 681 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards, 682 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3 683 TURBOchannel cards, also known as PMAGD-A, -B and -C. 684 685 Due to hardware limitations ZLX-E2 and E3 cards are not supported 686 for DECstation 5000/200 systems. Additionally due to firmware 687 limitations these cards may cause troubles with booting DECstation 688 5000/240 and /260 systems, but are fully supported under Linux if 689 you manage to get it going. ;-) 690 691 Say Y if you have one of those. 692 693config FB_UVESA 694 tristate "Userspace VESA VGA graphics support" 695 depends on FB && CONNECTOR 696 select FB_CFB_FILLRECT 697 select FB_CFB_COPYAREA 698 select FB_CFB_IMAGEBLIT 699 select FB_MODE_HELPERS 700 help 701 This is the frame buffer driver for generic VBE 2.0 compliant 702 graphic cards. It can also take advantage of VBE 3.0 features, 703 such as refresh rate adjustment. 704 705 This driver generally provides more features than vesafb but 706 requires a userspace helper application called 'v86d'. See 707 <file:Documentation/fb/uvesafb.txt> for more information. 708 709 If unsure, say N. 710 711config FB_VESA 712 bool "VESA VGA graphics support" 713 depends on (FB = y) && X86 714 select FB_CFB_FILLRECT 715 select FB_CFB_COPYAREA 716 select FB_CFB_IMAGEBLIT 717 select FB_BOOT_VESA_SUPPORT 718 help 719 This is the frame buffer device driver for generic VESA 2.0 720 compliant graphic cards. The older VESA 1.2 cards are not supported. 721 You will get a boot time penguin logo at no additional cost. Please 722 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y. 723 724config FB_EFI 725 bool "EFI-based Framebuffer Support" 726 depends on (FB = y) && X86 && EFI 727 select FB_CFB_FILLRECT 728 select FB_CFB_COPYAREA 729 select FB_CFB_IMAGEBLIT 730 help 731 This is the EFI frame buffer device driver. If the firmware on 732 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for 733 using the EFI framebuffer as your console. 734 735config FB_N411 736 tristate "N411 Apollo/Hecuba devkit support" 737 depends on FB && X86 && MMU 738 select FB_SYS_FILLRECT 739 select FB_SYS_COPYAREA 740 select FB_SYS_IMAGEBLIT 741 select FB_SYS_FOPS 742 select FB_DEFERRED_IO 743 select FB_HECUBA 744 help 745 This enables support for the Apollo display controller in its 746 Hecuba form using the n411 devkit. 747 748config FB_HGA 749 tristate "Hercules mono graphics support" 750 depends on FB && X86 751 select FB_CFB_FILLRECT 752 select FB_CFB_COPYAREA 753 select FB_CFB_IMAGEBLIT 754 help 755 Say Y here if you have a Hercules mono graphics card. 756 757 To compile this driver as a module, choose M here: the 758 module will be called hgafb. 759 760 As this card technology is 15 years old, most people will answer N 761 here. 762 763config FB_HGA_ACCEL 764 bool "Hercules mono Acceleration functions (EXPERIMENTAL)" 765 depends on FB_HGA && EXPERIMENTAL 766 ---help--- 767 This will compile the Hercules mono graphics with 768 acceleration functions. 769 770config FB_SGIVW 771 tristate "SGI Visual Workstation framebuffer support" 772 depends on FB && X86_VISWS 773 select FB_CFB_FILLRECT 774 select FB_CFB_COPYAREA 775 select FB_CFB_IMAGEBLIT 776 help 777 SGI Visual Workstation support for framebuffer graphics. 778 779config FB_GBE 780 bool "SGI Graphics Backend frame buffer support" 781 depends on (FB = y) && (SGI_IP32 || X86_VISWS) 782 select FB_CFB_FILLRECT 783 select FB_CFB_COPYAREA 784 select FB_CFB_IMAGEBLIT 785 help 786 This is the frame buffer device driver for SGI Graphics Backend. 787 This chip is used in SGI O2 and Visual Workstation 320/540. 788 789config FB_GBE_MEM 790 int "Video memory size in MB" 791 depends on FB_GBE 792 default 4 793 help 794 This is the amount of memory reserved for the framebuffer, 795 which can be any value between 1MB and 8MB. 796 797config FB_SBUS 798 bool "SBUS and UPA framebuffers" 799 depends on (FB = y) && SPARC 800 help 801 Say Y if you want support for SBUS or UPA based frame buffer device. 802 803config FB_BW2 804 bool "BWtwo support" 805 depends on (FB = y) && (SPARC && FB_SBUS) 806 select FB_CFB_FILLRECT 807 select FB_CFB_COPYAREA 808 select FB_CFB_IMAGEBLIT 809 help 810 This is the frame buffer device driver for the BWtwo frame buffer. 811 812config FB_CG3 813 bool "CGthree support" 814 depends on (FB = y) && (SPARC && FB_SBUS) 815 select FB_CFB_FILLRECT 816 select FB_CFB_COPYAREA 817 select FB_CFB_IMAGEBLIT 818 help 819 This is the frame buffer device driver for the CGthree frame buffer. 820 821config FB_CG6 822 bool "CGsix (GX,TurboGX) support" 823 depends on (FB = y) && (SPARC && FB_SBUS) 824 select FB_CFB_COPYAREA 825 select FB_CFB_IMAGEBLIT 826 help 827 This is the frame buffer device driver for the CGsix (GX, TurboGX) 828 frame buffer. 829 830config FB_FFB 831 bool "Creator/Creator3D/Elite3D support" 832 depends on FB_SBUS && SPARC64 833 select FB_CFB_COPYAREA 834 select FB_CFB_IMAGEBLIT 835 help 836 This is the frame buffer device driver for the Creator, Creator3D, 837 and Elite3D graphics boards. 838 839config FB_TCX 840 bool "TCX (SS4/SS5 only) support" 841 depends on FB_SBUS 842 select FB_CFB_FILLRECT 843 select FB_CFB_COPYAREA 844 select FB_CFB_IMAGEBLIT 845 help 846 This is the frame buffer device driver for the TCX 24/8bit frame 847 buffer. 848 849config FB_CG14 850 bool "CGfourteen (SX) support" 851 depends on FB_SBUS 852 select FB_CFB_FILLRECT 853 select FB_CFB_COPYAREA 854 select FB_CFB_IMAGEBLIT 855 help 856 This is the frame buffer device driver for the CGfourteen frame 857 buffer on Desktop SPARCsystems with the SX graphics option. 858 859config FB_P9100 860 bool "P9100 (Sparcbook 3 only) support" 861 depends on FB_SBUS 862 select FB_CFB_FILLRECT 863 select FB_CFB_COPYAREA 864 select FB_CFB_IMAGEBLIT 865 help 866 This is the frame buffer device driver for the P9100 card 867 supported on Sparcbook 3 machines. 868 869config FB_LEO 870 bool "Leo (ZX) support" 871 depends on FB_SBUS 872 select FB_CFB_FILLRECT 873 select FB_CFB_COPYAREA 874 select FB_CFB_IMAGEBLIT 875 help 876 This is the frame buffer device driver for the SBUS-based Sun ZX 877 (leo) frame buffer cards. 878 879config FB_IGA 880 bool "IGA 168x display support" 881 depends on (FB = y) && SPARC32 882 select FB_CFB_FILLRECT 883 select FB_CFB_COPYAREA 884 select FB_CFB_IMAGEBLIT 885 help 886 This is the framebuffer device for the INTERGRAPHICS 1680 and 887 successor frame buffer cards. 888 889config FB_XVR500 890 bool "Sun XVR-500 3DLABS Wildcat support" 891 depends on (FB = y) && PCI && SPARC64 892 select FB_CFB_FILLRECT 893 select FB_CFB_COPYAREA 894 select FB_CFB_IMAGEBLIT 895 help 896 This is the framebuffer device for the Sun XVR-500 and similar 897 graphics cards based upon the 3DLABS Wildcat chipset. The driver 898 only works on sparc64 systems where the system firmware has 899 mostly initialized the card already. It is treated as a 900 completely dumb framebuffer device. 901 902config FB_XVR2500 903 bool "Sun XVR-2500 3DLABS Wildcat support" 904 depends on (FB = y) && PCI && SPARC64 905 select FB_CFB_FILLRECT 906 select FB_CFB_COPYAREA 907 select FB_CFB_IMAGEBLIT 908 help 909 This is the framebuffer device for the Sun XVR-2500 and similar 910 graphics cards based upon the 3DLABS Wildcat chipset. The driver 911 only works on sparc64 systems where the system firmware has 912 mostly initialized the card already. It is treated as a 913 completely dumb framebuffer device. 914 915config FB_XVR1000 916 bool "Sun XVR-1000 support" 917 depends on (FB = y) && SPARC64 918 select FB_CFB_FILLRECT 919 select FB_CFB_COPYAREA 920 select FB_CFB_IMAGEBLIT 921 help 922 This is the framebuffer device for the Sun XVR-1000 and similar 923 graphics cards. The driver only works on sparc64 systems where 924 the system firmware has mostly initialized the card already. It 925 is treated as a completely dumb framebuffer device. 926 927config FB_PVR2 928 tristate "NEC PowerVR 2 display support" 929 depends on FB && SH_DREAMCAST 930 select FB_CFB_FILLRECT 931 select FB_CFB_COPYAREA 932 select FB_CFB_IMAGEBLIT 933 ---help--- 934 Say Y here if you have a PowerVR 2 card in your box. If you plan to 935 run linux on your Dreamcast, you will have to say Y here. 936 This driver may or may not work on other PowerVR 2 cards, but is 937 totally untested. Use at your own risk. If unsure, say N. 938 939 To compile this driver as a module, choose M here: the 940 module will be called pvr2fb. 941 942 You can pass several parameters to the driver at boot time or at 943 module load time. The parameters look like "video=pvr2:XXX", where 944 the meaning of XXX can be found at the end of the main source file 945 (<file:drivers/video/pvr2fb.c>). Please see the file 946 <file:Documentation/fb/pvr2fb.txt>. 947 948config FB_EPSON1355 949 bool "Epson 1355 framebuffer support" 950 depends on (FB = y) && ARCH_CEIVA 951 select FB_CFB_FILLRECT 952 select FB_CFB_COPYAREA 953 select FB_CFB_IMAGEBLIT 954 help 955 Build in support for the SED1355 Epson Research Embedded RAMDAC 956 LCD/CRT Controller (since redesignated as the S1D13505) as a 957 framebuffer. Product specs at 958 <http://www.erd.epson.com/vdc/html/products.htm>. 959 960config FB_S1D13XXX 961 tristate "Epson S1D13XXX framebuffer support" 962 depends on FB 963 select FB_CFB_FILLRECT 964 select FB_CFB_COPYAREA 965 select FB_CFB_IMAGEBLIT 966 help 967 Support for S1D13XXX framebuffer device family (currently only 968 working with S1D13806). Product specs at 969 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm> 970 971config FB_ATMEL 972 tristate "AT91/AT32 LCD Controller support" 973 depends on FB && HAVE_FB_ATMEL 974 select FB_CFB_FILLRECT 975 select FB_CFB_COPYAREA 976 select FB_CFB_IMAGEBLIT 977 help 978 This enables support for the AT91/AT32 LCD Controller. 979 980config FB_INTSRAM 981 bool "Frame Buffer in internal SRAM" 982 depends on FB_ATMEL && ARCH_AT91SAM9261 983 help 984 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want 985 to let frame buffer in external SDRAM. 986 987config FB_ATMEL_STN 988 bool "Use a STN display with AT91/AT32 LCD Controller" 989 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK) 990 default n 991 help 992 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD 993 Controller. Say N if you want to connect a TFT. 994 995 If unsure, say N. 996 997config FB_NVIDIA 998 tristate "nVidia Framebuffer Support" 999 depends on FB && PCI 1000 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1001 select FB_MODE_HELPERS 1002 select FB_CFB_FILLRECT 1003 select FB_CFB_COPYAREA 1004 select FB_CFB_IMAGEBLIT 1005 select BITREVERSE 1006 select VGASTATE 1007 help 1008 This driver supports graphics boards with the nVidia chips, TNT 1009 and newer. For very old chipsets, such as the RIVA128, then use 1010 the rivafb. 1011 Say Y if you have such a graphics board. 1012 1013 To compile this driver as a module, choose M here: the 1014 module will be called nvidiafb. 1015 1016config FB_NVIDIA_I2C 1017 bool "Enable DDC Support" 1018 depends on FB_NVIDIA 1019 select FB_DDC 1020 help 1021 This enables I2C support for nVidia Chipsets. This is used 1022 only for getting EDID information from the attached display 1023 allowing for robust video mode handling and switching. 1024 1025 Because fbdev-2.6 requires that drivers must be able to 1026 independently validate video mode parameters, you should say Y 1027 here. 1028 1029config FB_NVIDIA_DEBUG 1030 bool "Lots of debug output" 1031 depends on FB_NVIDIA 1032 default n 1033 help 1034 Say Y here if you want the nVidia driver to output all sorts 1035 of debugging information to provide to the maintainer when 1036 something goes wrong. 1037 1038config FB_NVIDIA_BACKLIGHT 1039 bool "Support for backlight control" 1040 depends on FB_NVIDIA 1041 default y 1042 help 1043 Say Y here if you want to control the backlight of your display. 1044 1045config FB_RIVA 1046 tristate "nVidia Riva support" 1047 depends on FB && PCI 1048 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT 1049 select FB_MODE_HELPERS 1050 select FB_CFB_FILLRECT 1051 select FB_CFB_COPYAREA 1052 select FB_CFB_IMAGEBLIT 1053 select BITREVERSE 1054 select VGASTATE 1055 help 1056 This driver supports graphics boards with the nVidia Riva/Geforce 1057 chips. 1058 Say Y if you have such a graphics board. 1059 1060 To compile this driver as a module, choose M here: the 1061 module will be called rivafb. 1062 1063config FB_RIVA_I2C 1064 bool "Enable DDC Support" 1065 depends on FB_RIVA 1066 select FB_DDC 1067 help 1068 This enables I2C support for nVidia Chipsets. This is used 1069 only for getting EDID information from the attached display 1070 allowing for robust video mode handling and switching. 1071 1072 Because fbdev-2.6 requires that drivers must be able to 1073 independently validate video mode parameters, you should say Y 1074 here. 1075 1076config FB_RIVA_DEBUG 1077 bool "Lots of debug output" 1078 depends on FB_RIVA 1079 default n 1080 help 1081 Say Y here if you want the Riva driver to output all sorts 1082 of debugging information to provide to the maintainer when 1083 something goes wrong. 1084 1085config FB_RIVA_BACKLIGHT 1086 bool "Support for backlight control" 1087 depends on FB_RIVA 1088 default y 1089 help 1090 Say Y here if you want to control the backlight of your display. 1091 1092config FB_I810 1093 tristate "Intel 810/815 support (EXPERIMENTAL)" 1094 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL 1095 select FB_MODE_HELPERS 1096 select FB_CFB_FILLRECT 1097 select FB_CFB_COPYAREA 1098 select FB_CFB_IMAGEBLIT 1099 select VGASTATE 1100 help 1101 This driver supports the on-board graphics built in to the Intel 810 1102 and 815 chipsets. Say Y if you have and plan to use such a board. 1103 1104 To compile this driver as a module, choose M here: the 1105 module will be called i810fb. 1106 1107 For more information, please read 1108 <file:Documentation/fb/intel810.txt> 1109 1110config FB_I810_GTF 1111 bool "use VESA Generalized Timing Formula" 1112 depends on FB_I810 1113 help 1114 If you say Y, then the VESA standard, Generalized Timing Formula 1115 or GTF, will be used to calculate the required video timing values 1116 per video mode. Since the GTF allows nondiscrete timings 1117 (nondiscrete being a range of values as opposed to discrete being a 1118 set of values), you'll be able to use any combination of horizontal 1119 and vertical resolutions, and vertical refresh rates without having 1120 to specify your own timing parameters. This is especially useful 1121 to maximize the performance of an aging display, or if you just 1122 have a display with nonstandard dimensions. A VESA compliant 1123 monitor is recommended, but can still work with non-compliant ones. 1124 If you need or want this, then select this option. The timings may 1125 not be compliant with Intel's recommended values. Use at your own 1126 risk. 1127 1128 If you say N, the driver will revert to discrete video timings 1129 using a set recommended by Intel in their documentation. 1130 1131 If unsure, say N. 1132 1133config FB_I810_I2C 1134 bool "Enable DDC Support" 1135 depends on FB_I810 && FB_I810_GTF 1136 select FB_DDC 1137 help 1138 1139config FB_LE80578 1140 tristate "Intel LE80578 (Vermilion) support" 1141 depends on FB && PCI && X86 1142 select FB_MODE_HELPERS 1143 select FB_CFB_FILLRECT 1144 select FB_CFB_COPYAREA 1145 select FB_CFB_IMAGEBLIT 1146 help 1147 This driver supports the LE80578 (Vermilion Range) chipset 1148 1149config FB_CARILLO_RANCH 1150 tristate "Intel Carillo Ranch support" 1151 depends on FB_LE80578 && FB && PCI && X86 1152 help 1153 This driver supports the LE80578 (Carillo Ranch) board 1154 1155config FB_INTEL 1156 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)" 1157 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED 1158 select FB_MODE_HELPERS 1159 select FB_CFB_FILLRECT 1160 select FB_CFB_COPYAREA 1161 select FB_CFB_IMAGEBLIT 1162 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y 1163 depends on !DRM_I915 1164 help 1165 This driver supports the on-board graphics built in to the Intel 1166 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets. 1167 Say Y if you have and plan to use such a board. 1168 1169 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too. 1170 1171 To compile this driver as a module, choose M here: the 1172 module will be called intelfb. 1173 1174 For more information, please read <file:Documentation/fb/intelfb.txt> 1175 1176config FB_INTEL_DEBUG 1177 bool "Intel driver Debug Messages" 1178 depends on FB_INTEL 1179 ---help--- 1180 Say Y here if you want the Intel driver to output all sorts 1181 of debugging information to provide to the maintainer when 1182 something goes wrong. 1183 1184config FB_INTEL_I2C 1185 bool "DDC/I2C for Intel framebuffer support" 1186 depends on FB_INTEL 1187 select FB_DDC 1188 default y 1189 help 1190 Say Y here if you want DDC/I2C support for your on-board Intel graphics. 1191 1192config FB_MATROX 1193 tristate "Matrox acceleration" 1194 depends on FB && PCI 1195 select FB_CFB_FILLRECT 1196 select FB_CFB_COPYAREA 1197 select FB_CFB_IMAGEBLIT 1198 select FB_TILEBLITTING 1199 select FB_MACMODES if PPC_PMAC 1200 ---help--- 1201 Say Y here if you have a Matrox Millennium, Matrox Millennium II, 1202 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox 1203 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video, 1204 Matrox G400, G450 or G550 card in your box. 1205 1206 To compile this driver as a module, choose M here: the 1207 module will be called matroxfb. 1208 1209 You can pass several parameters to the driver at boot time or at 1210 module load time. The parameters look like "video=matrox:XXX", and 1211 are described in <file:Documentation/fb/matroxfb.txt>. 1212 1213config FB_MATROX_MILLENIUM 1214 bool "Millennium I/II support" 1215 depends on FB_MATROX 1216 help 1217 Say Y here if you have a Matrox Millennium or Matrox Millennium II 1218 video card. If you select "Advanced lowlevel driver options" below, 1219 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp 1220 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can 1221 also use font widths different from 8. 1222 1223config FB_MATROX_MYSTIQUE 1224 bool "Mystique support" 1225 depends on FB_MATROX 1226 help 1227 Say Y here if you have a Matrox Mystique or Matrox Mystique 220 1228 video card. If you select "Advanced lowlevel driver options" below, 1229 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp 1230 packed pixel and 32 bpp packed pixel. You can also use font widths 1231 different from 8. 1232 1233config FB_MATROX_G 1234 bool "G100/G200/G400/G450/G550 support" 1235 depends on FB_MATROX 1236 ---help--- 1237 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based 1238 video card. If you select "Advanced lowlevel driver options", you 1239 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed 1240 pixel and 32 bpp packed pixel. You can also use font widths 1241 different from 8. 1242 1243 If you need support for G400 secondary head, you must say Y to 1244 "Matrox I2C support" and "G400 second head support" right below. 1245 G450/G550 secondary head and digital output are supported without 1246 additional modules. 1247 1248 The driver starts in monitor mode. You must use the matroxset tool 1249 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 1250 swap primary and secondary head outputs, or to change output mode. 1251 Secondary head driver always start in 640x480 resolution and you 1252 must use fbset to change it. 1253 1254 Do not forget that second head supports only 16 and 32 bpp 1255 packed pixels, so it is a good idea to compile them into the kernel 1256 too. You can use only some font widths, as the driver uses generic 1257 painting procedures (the secondary head does not use acceleration 1258 engine). 1259 1260 G450/G550 hardware can display TV picture only from secondary CRTC, 1261 and it performs no scaling, so picture must have 525 or 625 lines. 1262 1263config FB_MATROX_I2C 1264 tristate "Matrox I2C support" 1265 depends on FB_MATROX 1266 select FB_DDC 1267 ---help--- 1268 This drivers creates I2C buses which are needed for accessing the 1269 DDC (I2C) bus present on all Matroxes, an I2C bus which 1270 interconnects Matrox optional devices, like MGA-TVO on G200 and 1271 G400, and the secondary head DDC bus, present on G400 only. 1272 1273 You can say Y or M here if you want to experiment with monitor 1274 detection code. You must say Y or M here if you want to use either 1275 second head of G400 or MGA-TVO on G200 or G400. 1276 1277 If you compile it as module, it will create a module named 1278 i2c-matroxfb. 1279 1280config FB_MATROX_MAVEN 1281 tristate "G400 second head support" 1282 depends on FB_MATROX_G && FB_MATROX_I2C 1283 ---help--- 1284 WARNING !!! This support does not work with G450 !!! 1285 1286 Say Y or M here if you want to use a secondary head (meaning two 1287 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary 1288 head is not compatible with accelerated XFree 3.3.x SVGA servers - 1289 secondary head output is blanked while you are in X. With XFree 1290 3.9.17 preview you can use both heads if you use SVGA over fbdev or 1291 the fbdev driver on first head and the fbdev driver on second head. 1292 1293 If you compile it as module, two modules are created, 1294 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for 1295 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must 1296 also load i2c-matroxfb to get it to run. 1297 1298 The driver starts in monitor mode and you must use the matroxset 1299 tool (available at 1300 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to 1301 PAL or NTSC or to swap primary and secondary head outputs. 1302 Secondary head driver also always start in 640x480 resolution, you 1303 must use fbset to change it. 1304 1305 Also do not forget that second head supports only 16 and 32 bpp 1306 packed pixels, so it is a good idea to compile them into the kernel 1307 too. You can use only some font widths, as the driver uses generic 1308 painting procedures (the secondary head does not use acceleration 1309 engine). 1310 1311config FB_RADEON 1312 tristate "ATI Radeon display support" 1313 depends on FB && PCI 1314 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT 1315 select FB_MODE_HELPERS 1316 select FB_CFB_FILLRECT 1317 select FB_CFB_COPYAREA 1318 select FB_CFB_IMAGEBLIT 1319 select FB_MACMODES if PPC_OF 1320 help 1321 Choose this option if you want to use an ATI Radeon graphics card as 1322 a framebuffer device. There are both PCI and AGP versions. You 1323 don't need to choose this to run the Radeon in plain VGA mode. 1324 1325 There is a product page at 1326 http://apps.ati.com/ATIcompare/ 1327 1328config FB_RADEON_I2C 1329 bool "DDC/I2C for ATI Radeon support" 1330 depends on FB_RADEON 1331 select FB_DDC 1332 default y 1333 help 1334 Say Y here if you want DDC/I2C support for your Radeon board. 1335 1336config FB_RADEON_BACKLIGHT 1337 bool "Support for backlight control" 1338 depends on FB_RADEON 1339 default y 1340 help 1341 Say Y here if you want to control the backlight of your display. 1342 1343config FB_RADEON_DEBUG 1344 bool "Lots of debug output from Radeon driver" 1345 depends on FB_RADEON 1346 default n 1347 help 1348 Say Y here if you want the Radeon driver to output all sorts 1349 of debugging information to provide to the maintainer when 1350 something goes wrong. 1351 1352config FB_ATY128 1353 tristate "ATI Rage128 display support" 1354 depends on FB && PCI 1355 select FB_CFB_FILLRECT 1356 select FB_CFB_COPYAREA 1357 select FB_CFB_IMAGEBLIT 1358 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT 1359 select FB_MACMODES if PPC_PMAC 1360 help 1361 This driver supports graphics boards with the ATI Rage128 chips. 1362 Say Y if you have such a graphics board and read 1363 <file:Documentation/fb/aty128fb.txt>. 1364 1365 To compile this driver as a module, choose M here: the 1366 module will be called aty128fb. 1367 1368config FB_ATY128_BACKLIGHT 1369 bool "Support for backlight control" 1370 depends on FB_ATY128 1371 default y 1372 help 1373 Say Y here if you want to control the backlight of your display. 1374 1375config FB_ATY 1376 tristate "ATI Mach64 display support" if PCI || ATARI 1377 depends on FB && !SPARC32 1378 select FB_CFB_FILLRECT 1379 select FB_CFB_COPYAREA 1380 select FB_CFB_IMAGEBLIT 1381 select FB_BACKLIGHT if FB_ATY_BACKLIGHT 1382 select FB_MACMODES if PPC 1383 help 1384 This driver supports graphics boards with the ATI Mach64 chips. 1385 Say Y if you have such a graphics board. 1386 1387 To compile this driver as a module, choose M here: the 1388 module will be called atyfb. 1389 1390config FB_ATY_CT 1391 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support" 1392 depends on PCI && FB_ATY 1393 default y if SPARC64 && PCI 1394 help 1395 Say Y here to support use of ATI's 64-bit Rage boards (or other 1396 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a 1397 framebuffer device. The ATI product support page for these boards 1398 is at <http://support.ati.com/products/pc/mach64/>. 1399 1400config FB_ATY_GENERIC_LCD 1401 bool "Mach64 generic LCD support (EXPERIMENTAL)" 1402 depends on FB_ATY_CT 1403 help 1404 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility, 1405 Rage XC, or Rage XL chipset. 1406 1407config FB_ATY_GX 1408 bool "Mach64 GX support" if PCI 1409 depends on FB_ATY 1410 default y if ATARI 1411 help 1412 Say Y here to support use of the ATI Mach64 Graphics Expression 1413 board (or other boards based on the Mach64 GX chipset) as a 1414 framebuffer device. The ATI product support page for these boards 1415 is at 1416 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>. 1417 1418config FB_ATY_BACKLIGHT 1419 bool "Support for backlight control" 1420 depends on FB_ATY 1421 default y 1422 help 1423 Say Y here if you want to control the backlight of your display. 1424 1425config FB_S3 1426 tristate "S3 Trio/Virge support" 1427 depends on FB && PCI 1428 select FB_CFB_FILLRECT 1429 select FB_CFB_COPYAREA 1430 select FB_CFB_IMAGEBLIT 1431 select FB_TILEBLITTING 1432 select FB_SVGALIB 1433 select VGASTATE 1434 select FONT_8x16 if FRAMEBUFFER_CONSOLE 1435 ---help--- 1436 Driver for graphics boards with S3 Trio / S3 Virge chip. 1437 1438config FB_SAVAGE 1439 tristate "S3 Savage support" 1440 depends on FB && PCI && EXPERIMENTAL 1441 select FB_MODE_HELPERS 1442 select FB_CFB_FILLRECT 1443 select FB_CFB_COPYAREA 1444 select FB_CFB_IMAGEBLIT 1445 select VGASTATE 1446 help 1447 This driver supports notebooks and computers with S3 Savage PCI/AGP 1448 chips. 1449 1450 Say Y if you have such a graphics card. 1451 1452 To compile this driver as a module, choose M here; the module 1453 will be called savagefb. 1454 1455config FB_SAVAGE_I2C 1456 bool "Enable DDC2 Support" 1457 depends on FB_SAVAGE 1458 select FB_DDC 1459 help 1460 This enables I2C support for S3 Savage Chipsets. This is used 1461 only for getting EDID information from the attached display 1462 allowing for robust video mode handling and switching. 1463 1464 Because fbdev-2.6 requires that drivers must be able to 1465 independently validate video mode parameters, you should say Y 1466 here. 1467 1468config FB_SAVAGE_ACCEL 1469 bool "Enable Console Acceleration" 1470 depends on FB_SAVAGE 1471 default n 1472 help 1473 This option will compile in console acceleration support. If 1474 the resulting framebuffer console has bothersome glitches, then 1475 choose N here. 1476 1477config FB_SIS 1478 tristate "SiS/XGI display support" 1479 depends on FB && PCI 1480 select FB_CFB_FILLRECT 1481 select FB_CFB_COPYAREA 1482 select FB_CFB_IMAGEBLIT 1483 select FB_BOOT_VESA_SUPPORT if FB_SIS = y 1484 help 1485 This is the frame buffer device driver for the SiS 300, 315, 330 1486 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets. 1487 Specs available at <http://www.sis.com> and <http://www.xgitech.com>. 1488 1489 To compile this driver as a module, choose M here; the module 1490 will be called sisfb. 1491 1492config FB_SIS_300 1493 bool "SiS 300 series support" 1494 depends on FB_SIS 1495 help 1496 Say Y here to support use of the SiS 300/305, 540, 630 and 730. 1497 1498config FB_SIS_315 1499 bool "SiS 315/330/340 series and XGI support" 1500 depends on FB_SIS 1501 help 1502 Say Y here to support use of the SiS 315, 330 and 340 series 1503 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well 1504 as XGI V3XT, V5, V8 and Z7. 1505 1506config FB_VIA 1507 tristate "VIA UniChrome (Pro) and Chrome9 display support" 1508 depends on FB && PCI 1509 select FB_CFB_FILLRECT 1510 select FB_CFB_COPYAREA 1511 select FB_CFB_IMAGEBLIT 1512 select I2C_ALGOBIT 1513 select I2C 1514 select GPIOLIB 1515 help 1516 This is the frame buffer device driver for Graphics chips of VIA 1517 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/ 1518 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896 1519 /P4M900,VX800) 1520 Say Y if you have a VIA UniChrome graphics board. 1521 1522 To compile this driver as a module, choose M here: the 1523 module will be called viafb. 1524 1525if FB_VIA 1526 1527config FB_VIA_DIRECT_PROCFS 1528 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)" 1529 depends on FB_VIA 1530 default n 1531 help 1532 Allow direct hardware access to some output registers via procfs. 1533 This is dangerous but may provide the only chance to get the 1534 correct output device configuration. 1535 Its use is strongly discouraged. 1536 1537endif 1538 1539config FB_NEOMAGIC 1540 tristate "NeoMagic display support" 1541 depends on FB && PCI 1542 select FB_MODE_HELPERS 1543 select FB_CFB_FILLRECT 1544 select FB_CFB_COPYAREA 1545 select FB_CFB_IMAGEBLIT 1546 select VGASTATE 1547 help 1548 This driver supports notebooks with NeoMagic PCI chips. 1549 Say Y if you have such a graphics card. 1550 1551 To compile this driver as a module, choose M here: the 1552 module will be called neofb. 1553 1554config FB_KYRO 1555 tristate "IMG Kyro support" 1556 depends on FB && PCI 1557 select FB_CFB_FILLRECT 1558 select FB_CFB_COPYAREA 1559 select FB_CFB_IMAGEBLIT 1560 help 1561 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based 1562 graphics board. 1563 1564 To compile this driver as a module, choose M here: the 1565 module will be called kyrofb. 1566 1567config FB_3DFX 1568 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support" 1569 depends on FB && PCI 1570 select FB_CFB_IMAGEBLIT 1571 select FB_CFB_FILLRECT 1572 select FB_CFB_COPYAREA 1573 select FB_MODE_HELPERS 1574 help 1575 This driver supports graphics boards with the 3Dfx Banshee, 1576 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have 1577 such a graphics board. 1578 1579 To compile this driver as a module, choose M here: the 1580 module will be called tdfxfb. 1581 1582config FB_3DFX_ACCEL 1583 bool "3Dfx Acceleration functions (EXPERIMENTAL)" 1584 depends on FB_3DFX && EXPERIMENTAL 1585 ---help--- 1586 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer 1587 device driver with acceleration functions. 1588 1589config FB_3DFX_I2C 1590 bool "Enable DDC/I2C support" 1591 depends on FB_3DFX && EXPERIMENTAL 1592 select FB_DDC 1593 default y 1594 help 1595 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3. 1596 1597config FB_VOODOO1 1598 tristate "3Dfx Voodoo Graphics (sst1) support" 1599 depends on FB && PCI 1600 select FB_CFB_FILLRECT 1601 select FB_CFB_COPYAREA 1602 select FB_CFB_IMAGEBLIT 1603 ---help--- 1604 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 1605 Voodoo2 (cvg) based graphics card. 1606 1607 To compile this driver as a module, choose M here: the 1608 module will be called sstfb. 1609 1610 WARNING: Do not use any application that uses the 3D engine 1611 (namely glide) while using this driver. 1612 Please read the <file:Documentation/fb/sstfb.txt> for supported 1613 options and other important info support. 1614 1615config FB_VT8623 1616 tristate "VIA VT8623 support" 1617 depends on FB && PCI 1618 select FB_CFB_FILLRECT 1619 select FB_CFB_COPYAREA 1620 select FB_CFB_IMAGEBLIT 1621 select FB_TILEBLITTING 1622 select FB_SVGALIB 1623 select VGASTATE 1624 select FONT_8x16 if FRAMEBUFFER_CONSOLE 1625 ---help--- 1626 Driver for CastleRock integrated graphics core in the 1627 VIA VT8623 [Apollo CLE266] chipset. 1628 1629config FB_TRIDENT 1630 tristate "Trident/CyberXXX/CyberBlade support" 1631 depends on FB && PCI 1632 select FB_CFB_FILLRECT 1633 select FB_CFB_COPYAREA 1634 select FB_CFB_IMAGEBLIT 1635 ---help--- 1636 This is the frame buffer device driver for Trident PCI/AGP chipsets. 1637 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D 1638 and Blade XP. 1639 There are also integrated versions of these chips called CyberXXXX, 1640 CyberImage or CyberBlade. These chips are mostly found in laptops 1641 but also on some motherboards including early VIA EPIA motherboards. 1642 For more information, read <file:Documentation/fb/tridentfb.txt> 1643 1644 Say Y if you have such a graphics board. 1645 1646 To compile this driver as a module, choose M here: the 1647 module will be called tridentfb. 1648 1649config FB_ARK 1650 tristate "ARK 2000PV support" 1651 depends on FB && PCI 1652 select FB_CFB_FILLRECT 1653 select FB_CFB_COPYAREA 1654 select FB_CFB_IMAGEBLIT 1655 select FB_TILEBLITTING 1656 select FB_SVGALIB 1657 select VGASTATE 1658 select FONT_8x16 if FRAMEBUFFER_CONSOLE 1659 ---help--- 1660 Driver for PCI graphics boards with ARK 2000PV chip 1661 and ICS 5342 RAMDAC. 1662 1663config FB_PM3 1664 tristate "Permedia3 support (EXPERIMENTAL)" 1665 depends on FB && PCI && EXPERIMENTAL 1666 select FB_CFB_FILLRECT 1667 select FB_CFB_COPYAREA 1668 select FB_CFB_IMAGEBLIT 1669 help 1670 This is the frame buffer device driver for the 3DLabs Permedia3 1671 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & 1672 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000 1673 and maybe other boards. 1674 1675config FB_CARMINE 1676 tristate "Fujitsu carmine frame buffer support" 1677 depends on FB && PCI 1678 select FB_CFB_FILLRECT 1679 select FB_CFB_COPYAREA 1680 select FB_CFB_IMAGEBLIT 1681 help 1682 This is the frame buffer device driver for the Fujitsu Carmine chip. 1683 The driver provides two independent frame buffer devices. 1684 1685choice 1686 depends on FB_CARMINE 1687 prompt "DRAM timing" 1688 default FB_CARMINE_DRAM_EVAL 1689 1690config FB_CARMINE_DRAM_EVAL 1691 bool "Eval board timings" 1692 help 1693 Use timings which work on the eval card. 1694 1695config CARMINE_DRAM_CUSTOM 1696 bool "Custom board timings" 1697 help 1698 Use custom board timings. 1699endchoice 1700 1701config FB_AU1100 1702 bool "Au1100 LCD Driver" 1703 depends on (FB = y) && MIPS && SOC_AU1100 1704 select FB_CFB_FILLRECT 1705 select FB_CFB_COPYAREA 1706 select FB_CFB_IMAGEBLIT 1707 help 1708 This is the framebuffer driver for the AMD Au1100 SOC. It can drive 1709 various panels and CRTs by passing in kernel cmd line option 1710 au1100fb:panel=<name>. 1711 1712config FB_AU1200 1713 bool "Au1200 LCD Driver" 1714 depends on (FB = y) && MIPS && SOC_AU1200 1715 select FB_CFB_FILLRECT 1716 select FB_CFB_COPYAREA 1717 select FB_CFB_IMAGEBLIT 1718 help 1719 This is the framebuffer driver for the AMD Au1200 SOC. It can drive 1720 various panels and CRTs by passing in kernel cmd line option 1721 au1200fb:panel=<name>. 1722 1723source "drivers/video/geode/Kconfig" 1724 1725config FB_HIT 1726 tristate "HD64461 Frame Buffer support" 1727 depends on FB && HD64461 1728 select FB_CFB_FILLRECT 1729 select FB_CFB_COPYAREA 1730 select FB_CFB_IMAGEBLIT 1731 help 1732 This is the frame buffer device driver for the Hitachi HD64461 LCD 1733 frame buffer card. 1734 1735config FB_PMAG_AA 1736 bool "PMAG-AA TURBOchannel framebuffer support" 1737 depends on (FB = y) && TC 1738 select FB_CFB_FILLRECT 1739 select FB_CFB_COPYAREA 1740 select FB_CFB_IMAGEBLIT 1741 help 1742 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1) 1743 used mainly in the MIPS-based DECstation series. 1744 1745config FB_PMAG_BA 1746 tristate "PMAG-BA TURBOchannel framebuffer support" 1747 depends on FB && TC 1748 select FB_CFB_FILLRECT 1749 select FB_CFB_COPYAREA 1750 select FB_CFB_IMAGEBLIT 1751 help 1752 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) 1753 used mainly in the MIPS-based DECstation series. 1754 1755config FB_PMAGB_B 1756 tristate "PMAGB-B TURBOchannel framebuffer support" 1757 depends on FB && TC 1758 select FB_CFB_FILLRECT 1759 select FB_CFB_COPYAREA 1760 select FB_CFB_IMAGEBLIT 1761 help 1762 Support for the PMAGB-B TURBOchannel framebuffer card used mainly 1763 in the MIPS-based DECstation series. The card is currently only 1764 supported in 1280x1024x8 mode. 1765 1766config FB_MAXINE 1767 bool "Maxine (Personal DECstation) onboard framebuffer support" 1768 depends on (FB = y) && MACH_DECSTATION 1769 select FB_CFB_FILLRECT 1770 select FB_CFB_COPYAREA 1771 select FB_CFB_IMAGEBLIT 1772 help 1773 Support for the onboard framebuffer (1024x768x8) in the Personal 1774 DECstation series (Personal DECstation 5000/20, /25, /33, /50, 1775 Codename "Maxine"). 1776 1777config FB_G364 1778 bool "G364 frame buffer support" 1779 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700) 1780 select FB_CFB_FILLRECT 1781 select FB_CFB_COPYAREA 1782 select FB_CFB_IMAGEBLIT 1783 help 1784 The G364 driver is the framebuffer used in MIPS Magnum 4000 and 1785 Olivetti M700-10 systems. 1786 1787config FB_68328 1788 bool "Motorola 68328 native frame buffer support" 1789 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328) 1790 select FB_CFB_FILLRECT 1791 select FB_CFB_COPYAREA 1792 select FB_CFB_IMAGEBLIT 1793 help 1794 Say Y here if you want to support the built-in frame buffer of 1795 the Motorola 68328 CPU family. 1796 1797config FB_PXA168 1798 tristate "PXA168/910 LCD framebuffer support" 1799 depends on FB && (CPU_PXA168 || CPU_PXA910) 1800 select FB_CFB_FILLRECT 1801 select FB_CFB_COPYAREA 1802 select FB_CFB_IMAGEBLIT 1803 ---help--- 1804 Frame buffer driver for the built-in LCD controller in the Marvell 1805 MMP processor. 1806 1807config FB_PXA 1808 tristate "PXA LCD framebuffer support" 1809 depends on FB && ARCH_PXA 1810 select FB_CFB_FILLRECT 1811 select FB_CFB_COPYAREA 1812 select FB_CFB_IMAGEBLIT 1813 ---help--- 1814 Frame buffer driver for the built-in LCD controller in the Intel 1815 PXA2x0 processor. 1816 1817 This driver is also available as a module ( = code which can be 1818 inserted and removed from the running kernel whenever you want). The 1819 module will be called pxafb. If you want to compile it as a module, 1820 say M here and read <file:Documentation/kbuild/modules.txt>. 1821 1822 If unsure, say N. 1823 1824config FB_PXA_OVERLAY 1825 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer" 1826 default n 1827 depends on FB_PXA && (PXA27x || PXA3xx) 1828 1829config FB_PXA_SMARTPANEL 1830 bool "PXA Smartpanel LCD support" 1831 default n 1832 depends on FB_PXA 1833 1834config FB_PXA_PARAMETERS 1835 bool "PXA LCD command line parameters" 1836 default n 1837 depends on FB_PXA 1838 ---help--- 1839 Enable the use of kernel command line or module parameters 1840 to configure the physical properties of the LCD panel when 1841 using the PXA LCD driver. 1842 1843 This option allows you to override the panel parameters 1844 supplied by the platform in order to support multiple 1845 different models of flatpanel. If you will only be using a 1846 single model of flatpanel then you can safely leave this 1847 option disabled. 1848 1849 <file:Documentation/fb/pxafb.txt> describes the available parameters. 1850 1851config FB_MBX 1852 tristate "2700G LCD framebuffer support" 1853 depends on FB && ARCH_PXA 1854 select FB_CFB_FILLRECT 1855 select FB_CFB_COPYAREA 1856 select FB_CFB_IMAGEBLIT 1857 ---help--- 1858 Framebuffer driver for the Intel 2700G (Marathon) Graphics 1859 Accelerator 1860 1861config FB_MBX_DEBUG 1862 bool "Enable debugging info via debugfs" 1863 depends on FB_MBX && DEBUG_FS 1864 default n 1865 ---help--- 1866 Enable this if you want debugging information using the debug 1867 filesystem (debugfs) 1868 1869 If unsure, say N. 1870 1871config FB_FSL_DIU 1872 tristate "Freescale DIU framebuffer support" 1873 depends on FB && FSL_SOC 1874 select FB_CFB_FILLRECT 1875 select FB_CFB_COPYAREA 1876 select FB_CFB_IMAGEBLIT 1877 select PPC_LIB_RHEAP 1878 ---help--- 1879 Framebuffer driver for the Freescale SoC DIU 1880 1881config FB_W100 1882 tristate "W100 frame buffer support" 1883 depends on FB && ARCH_PXA 1884 select FB_CFB_FILLRECT 1885 select FB_CFB_COPYAREA 1886 select FB_CFB_IMAGEBLIT 1887 ---help--- 1888 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series. 1889 It can also drive the w3220 chip found on iPAQ hx4700. 1890 1891 This driver is also available as a module ( = code which can be 1892 inserted and removed from the running kernel whenever you want). The 1893 module will be called w100fb. If you want to compile it as a module, 1894 say M here and read <file:Documentation/kbuild/modules.txt>. 1895 1896 If unsure, say N. 1897 1898config FB_SH_MOBILE_LCDC 1899 tristate "SuperH Mobile LCDC framebuffer support" 1900 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK 1901 select FB_SYS_FILLRECT 1902 select FB_SYS_COPYAREA 1903 select FB_SYS_IMAGEBLIT 1904 select FB_SYS_FOPS 1905 select FB_DEFERRED_IO 1906 ---help--- 1907 Frame buffer driver for the on-chip SH-Mobile LCD controller. 1908 1909config FB_TMIO 1910 tristate "Toshiba Mobile IO FrameBuffer support" 1911 depends on FB && MFD_CORE 1912 select FB_CFB_FILLRECT 1913 select FB_CFB_COPYAREA 1914 select FB_CFB_IMAGEBLIT 1915 ---help--- 1916 Frame buffer driver for the Toshiba Mobile IO integrated as found 1917 on the Sharp SL-6000 series 1918 1919 This driver is also available as a module ( = code which can be 1920 inserted and removed from the running kernel whenever you want). The 1921 module will be called tmiofb. If you want to compile it as a module, 1922 say M here and read <file:Documentation/kbuild/modules.txt>. 1923 1924 If unsure, say N. 1925 1926config FB_TMIO_ACCELL 1927 bool "tmiofb acceleration" 1928 depends on FB_TMIO 1929 default y 1930 1931config FB_S3C 1932 tristate "Samsung S3C framebuffer support" 1933 depends on FB && ARCH_S3C64XX 1934 select FB_CFB_FILLRECT 1935 select FB_CFB_COPYAREA 1936 select FB_CFB_IMAGEBLIT 1937 ---help--- 1938 Frame buffer driver for the built-in FB controller in the Samsung 1939 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450, 1940 and the S3C64XX series such as the S3C6400 and S3C6410. 1941 1942 These chips all have the same basic framebuffer design with the 1943 actual capabilities depending on the chip. For instance the S3C6400 1944 and S3C6410 support 4 hardware windows whereas the S3C24XX series 1945 currently only have two. 1946 1947 Currently the support is only for the S3C6400 and S3C6410 SoCs. 1948 1949config FB_S3C_DEBUG_REGWRITE 1950 bool "Debug register writes" 1951 depends on FB_S3C 1952 ---help--- 1953 Show all register writes via printk(KERN_DEBUG) 1954 1955config FB_S3C2410 1956 tristate "S3C2410 LCD framebuffer support" 1957 depends on FB && ARCH_S3C2410 1958 select FB_CFB_FILLRECT 1959 select FB_CFB_COPYAREA 1960 select FB_CFB_IMAGEBLIT 1961 ---help--- 1962 Frame buffer driver for the built-in LCD controller in the Samsung 1963 S3C2410 processor. 1964 1965 This driver is also available as a module ( = code which can be 1966 inserted and removed from the running kernel whenever you want). The 1967 module will be called s3c2410fb. If you want to compile it as a module, 1968 say M here and read <file:Documentation/kbuild/modules.txt>. 1969 1970 If unsure, say N. 1971config FB_S3C2410_DEBUG 1972 bool "S3C2410 lcd debug messages" 1973 depends on FB_S3C2410 1974 help 1975 Turn on debugging messages. Note that you can set/unset at run time 1976 through sysfs 1977 1978config FB_NUC900 1979 bool "NUC900 LCD framebuffer support" 1980 depends on FB && ARCH_W90X900 1981 select FB_CFB_FILLRECT 1982 select FB_CFB_COPYAREA 1983 select FB_CFB_IMAGEBLIT 1984 ---help--- 1985 Frame buffer driver for the built-in LCD controller in the Nuvoton 1986 NUC900 processor 1987 1988config GPM1040A0_320X240 1989 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD" 1990 depends on FB_NUC900 1991 1992config FB_NUC900_DEBUG 1993 bool "NUC900 lcd debug messages" 1994 depends on FB_NUC900 1995 help 1996 Turn on debugging messages. Note that you can set/unset at run time 1997 through sysfs 1998 1999config FB_SM501 2000 tristate "Silicon Motion SM501 framebuffer support"
2001 depends on FB && MFD_SM501 2002 select FB_CFB_FILLRECT 2003 select FB_CFB_COPYAREA 2004 select FB_CFB_IMAGEBLIT 2005 ---help--- 2006 Frame buffer driver for the CRT and LCD controllers in the Silicon 2007 Motion SM501. 2008 2009 This driver is also available as a module ( = code which can be 2010 inserted and removed from the running kernel whenever you want). The 2011 module will be called sm501fb. If you want to compile it as a module, 2012 say M here and read <file:Documentation/kbuild/modules.txt>. 2013 2014 If unsure, say N. 2015 2016 2017config FB_PNX4008_DUM 2018 tristate "Display Update Module support on Philips PNX4008 board" 2019 depends on FB && ARCH_PNX4008 2020 ---help--- 2021 Say Y here to enable support for PNX4008 Display Update Module (DUM) 2022 2023config FB_PNX4008_DUM_RGB 2024 tristate "RGB Framebuffer support on Philips PNX4008 board" 2025 depends on FB_PNX4008_DUM 2026 select FB_CFB_FILLRECT 2027 select FB_CFB_COPYAREA 2028 select FB_CFB_IMAGEBLIT 2029 ---help--- 2030 Say Y here to enable support for PNX4008 RGB Framebuffer 2031 2032config FB_IBM_GXT4500 2033 tristate "Framebuffer support for IBM GXT4500P adaptor" 2034 depends on FB && PPC 2035 select FB_CFB_FILLRECT 2036 select FB_CFB_COPYAREA 2037 select FB_CFB_IMAGEBLIT 2038 ---help--- 2039 Say Y here to enable support for the IBM GXT4500P display 2040 adaptor, found on some IBM System P (pSeries) machines. 2041 2042config FB_PS3 2043 tristate "PS3 GPU framebuffer driver" 2044 depends on FB && PS3_PS3AV 2045 select FB_SYS_FILLRECT 2046 select FB_SYS_COPYAREA 2047 select FB_SYS_IMAGEBLIT 2048 select FB_SYS_FOPS 2049 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE 2050 ---help--- 2051 Include support for the virtual frame buffer in the PS3 platform. 2052 2053config FB_PS3_DEFAULT_SIZE_M 2054 int "PS3 default frame buffer size (in MiB)" 2055 depends on FB_PS3 2056 default 9 2057 ---help--- 2058 This is the default size (in MiB) of the virtual frame buffer in 2059 the PS3. 2060 The default value can be overridden on the kernel command line 2061 using the "ps3fb" option (e.g. "ps3fb=9M"); 2062 2063config FB_XILINX 2064 tristate "Xilinx frame buffer support" 2065 depends on FB && (XILINX_VIRTEX || MICROBLAZE) 2066 select FB_CFB_FILLRECT 2067 select FB_CFB_COPYAREA 2068 select FB_CFB_IMAGEBLIT 2069 ---help--- 2070 Include support for the Xilinx ML300/ML403 reference design 2071 framebuffer. ML300 carries a 640*480 LCD display on the board, 2072 ML403 uses a standard DB15 VGA connector. 2073 2074config FB_COBALT 2075 tristate "Cobalt server LCD frame buffer support" 2076 depends on FB && MIPS_COBALT 2077 2078config FB_SH7760 2079 bool "SH7760/SH7763/SH7720/SH7721 LCDC support" 2080 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \ 2081 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721) 2082 select FB_CFB_FILLRECT 2083 select FB_CFB_COPYAREA 2084 select FB_CFB_IMAGEBLIT 2085 ---help--- 2086 Support for the SH7760/SH7763/SH7720/SH7721 integrated 2087 (D)STN/TFT LCD Controller. 2088 Supports display resolutions up to 1024x1024 pixel, grayscale and 2089 color operation, with depths ranging from 1 bpp to 8 bpp monochrome 2090 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for 2091 panels <= 320 pixel horizontal resolution. 2092 2093config FB_DA8XX 2094 tristate "DA8xx/OMAP-L1xx Framebuffer support" 2095 depends on FB && ARCH_DAVINCI_DA8XX 2096 select FB_CFB_FILLRECT 2097 select FB_CFB_COPYAREA 2098 select FB_CFB_IMAGEBLIT 2099 ---help--- 2100 This is the frame buffer device driver for the TI LCD controller 2101 found on DA8xx/OMAP-L1xx SoCs. 2102 If unsure, say N. 2103 2104config FB_VIRTUAL 2105 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)" 2106 depends on FB 2107 select FB_SYS_FILLRECT 2108 select FB_SYS_COPYAREA 2109 select FB_SYS_IMAGEBLIT 2110 select FB_SYS_FOPS 2111 ---help--- 2112 This is a `virtual' frame buffer device. It operates on a chunk of 2113 unswappable kernel memory instead of on the memory of a graphics 2114 board. This means you cannot see any output sent to this frame 2115 buffer device, while it does consume precious memory. The main use 2116 of this frame buffer device is testing and debugging the frame 2117 buffer subsystem. Do NOT enable it for normal systems! To protect 2118 the innocent, it has to be enabled explicitly at boot time using the 2119 kernel option `video=vfb:'. 2120 2121 To compile this driver as a module, choose M here: the 2122 module will be called vfb. In order to load it, you must use 2123 the vfb_enable=1 option. 2124 2125 If unsure, say N. 2126 2127config XEN_FBDEV_FRONTEND 2128 tristate "Xen virtual frame buffer support" 2129 depends on FB && XEN 2130 select FB_SYS_FILLRECT 2131 select FB_SYS_COPYAREA 2132 select FB_SYS_IMAGEBLIT 2133 select FB_SYS_FOPS 2134 select FB_DEFERRED_IO 2135 select XEN_XENBUS_FRONTEND 2136 default y 2137 help 2138 This driver implements the front-end of the Xen virtual 2139 frame buffer driver. It communicates with a back-end 2140 in another domain. 2141 2142config FB_METRONOME 2143 tristate "E-Ink Metronome/8track controller support" 2144 depends on FB 2145 select FB_SYS_FILLRECT 2146 select FB_SYS_COPYAREA 2147 select FB_SYS_IMAGEBLIT 2148 select FB_SYS_FOPS 2149 select FB_DEFERRED_IO 2150 help 2151 This driver implements support for the E-Ink Metronome 2152 controller. The pre-release name for this device was 8track 2153 and could also have been called by some vendors as PVI-nnnn. 2154 2155config FB_MB862XX 2156 tristate "Fujitsu MB862xx GDC support" 2157 depends on FB 2158 select FB_CFB_FILLRECT 2159 select FB_CFB_COPYAREA 2160 select FB_CFB_IMAGEBLIT 2161 ---help--- 2162 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers. 2163 2164config FB_MB862XX_PCI_GDC 2165 bool "Carmine/Coral-P(A) GDC" 2166 depends on PCI && FB_MB862XX 2167 ---help--- 2168 This enables framebuffer support for Fujitsu Carmine/Coral-P(A) 2169 PCI graphics controller devices. 2170 2171config FB_MB862XX_LIME 2172 bool "Lime GDC" 2173 depends on FB_MB862XX 2174 depends on OF && !FB_MB862XX_PCI_GDC 2175 depends on PPC 2176 select FB_FOREIGN_ENDIAN 2177 select FB_LITTLE_ENDIAN 2178 ---help--- 2179 Framebuffer support for Fujitsu Lime GDC on host CPU bus. 2180 2181config FB_EP93XX 2182 tristate "EP93XX frame buffer support" 2183 depends on FB && ARCH_EP93XX 2184 select FB_CFB_FILLRECT 2185 select FB_CFB_COPYAREA 2186 select FB_CFB_IMAGEBLIT 2187 ---help--- 2188 Framebuffer driver for the Cirrus Logic EP93XX series of processors. 2189 This driver is also available as a module. The module will be called 2190 ep93xx-fb. 2191 2192config FB_PRE_INIT_FB 2193 bool "Don't reinitialize, use bootloader's GDC/Display configuration" 2194 depends on FB && FB_MB862XX_LIME 2195 ---help--- 2196 Select this option if display contents should be inherited as set by 2197 the bootloader. 2198 2199config FB_MSM 2200 tristate "MSM Framebuffer support" 2201 depends on FB && ARCH_MSM 2202 select FB_CFB_FILLRECT 2203 select FB_CFB_COPYAREA 2204 select FB_CFB_IMAGEBLIT 2205 2206config FB_MX3 2207 tristate "MX3 Framebuffer support" 2208 depends on FB && MX3_IPU 2209 select FB_CFB_FILLRECT 2210 select FB_CFB_COPYAREA 2211 select FB_CFB_IMAGEBLIT 2212 default y 2213 help 2214 This is a framebuffer device for the i.MX31 LCD Controller. So 2215 far only synchronous displays are supported. If you plan to use 2216 an LCD display with your i.MX31 system, say Y here. 2217 2218config FB_BROADSHEET 2219 tristate "E-Ink Broadsheet/Epson S1D13521 controller support" 2220 depends on FB 2221 select FB_SYS_FILLRECT 2222 select FB_SYS_COPYAREA 2223 select FB_SYS_IMAGEBLIT 2224 select FB_SYS_FOPS 2225 select FB_DEFERRED_IO 2226 help 2227 This driver implements support for the E-Ink Broadsheet 2228 controller. The release name for this device was Epson S1D13521 2229 and could also have been called by other names when coupled with 2230 a bridge adapter. 2231 2232source "drivers/video/omap/Kconfig" 2233source "drivers/video/omap2/Kconfig" 2234 2235source "drivers/video/backlight/Kconfig" 2236source "drivers/video/display/Kconfig" 2237 2238if VT 2239 source "drivers/video/console/Kconfig" 2240endif 2241 2242if FB || SGI_NEWPORT_CONSOLE 2243 source "drivers/video/logo/Kconfig" 2244endif 2245 2246endmenu 2247