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