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