1819 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# fbdev configuration4#5 6menuconfig FB7 tristate "Support for frame buffer device drivers"8 select FB_CORE9 select FB_NOTIFY10 help11 The frame buffer device provides an abstraction for the graphics12 hardware. It represents the frame buffer of some video hardware and13 allows application software to access the graphics hardware through14 a well-defined interface, so the software doesn't need to know15 anything about the low-level (hardware register) stuff.16 17 Frame buffer devices work identically across the different18 architectures supported by Linux and make the implementation of19 application programs easier and more portable; at this point, an X20 server exists which uses the frame buffer device exclusively.21 On several non-X86 architectures, the frame buffer device is the22 only way to use the graphics hardware.23 24 The device is accessed through special device nodes, usually located25 in the /dev directory, i.e. /dev/fb*.26 27 You need an utility program called fbset to make full use of frame28 buffer devices. Please read <file:Documentation/fb/framebuffer.rst>29 and the Framebuffer-HOWTO at30 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more31 information.32 33 This enables support for native frame buffer device (fbdev) drivers.34 35 The DRM subsystem provides support for emulated frame buffer devices36 on top of KMS drivers, but this option allows legacy fbdev drivers to37 be enabled as well.38 39 Say Y here and to the driver for your graphics board below if you40 are compiling a kernel for a non-x86 architecture.41 42 If you are compiling for the x86 architecture, you can say Y if you43 want to play with it, but it is not essential. Please note that44 running graphical applications that directly touch the hardware45 (e.g. an accelerated X server) and that are not frame buffer46 device-aware may cause unexpected results. If unsure, say N.47 48config FB_HECUBA49 tristate50 depends on FB51 select FB_SYSMEM_HELPERS_DEFERRED52 53config FB_SVGALIB54 tristate55 depends on FB56 help57 Common utility functions useful to fbdev drivers of VGA-based58 cards.59 60config FB_MACMODES61 tristate62 depends on FB63 64config FB_GRVGA65 tristate "Aeroflex Gaisler framebuffer support"66 depends on FB && SPARC67 select FB_IOMEM_HELPERS68 help69 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.70 71config FB_CIRRUS72 tristate "Cirrus Logic support"73 depends on FB && (ZORRO || PCI)74 select FB_CFB_FILLRECT75 select FB_CFB_COPYAREA76 select FB_CFB_IMAGEBLIT77 select FB_IOMEM_FOPS78 help79 This enables support for Cirrus Logic GD542x/543x based boards on80 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.81 82 If you have a PCI-based system, this enables support for these83 chips: GD-543x, GD-544x, GD-5480.84 85 Please read the file <file:Documentation/fb/cirrusfb.rst>.86 87 Say N unless you have such a graphics board or plan to get one88 before you next recompile the kernel.89 90config FB_PM291 tristate "Permedia2 support"92 depends on FB && ((AMIGA && BROKEN) || PCI)93 select FB_CFB_FILLRECT94 select FB_CFB_COPYAREA95 select FB_CFB_IMAGEBLIT96 select FB_IOMEM_FOPS97 help98 This is the frame buffer device driver for cards based on99 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.100 The driver was tested on the following cards:101 Diamond FireGL 1000 PRO AGP102 ELSA Gloria Synergy PCI103 Appian Jeronimo PRO (both heads) PCI104 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI105 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC106 ASK Graphic Blaster Exxtreme AGP107 108 To compile this driver as a module, choose M here: the109 module will be called pm2fb.110 111config FB_PM2_FIFO_DISCONNECT112 bool "enable FIFO disconnect feature"113 depends on FB_PM2 && PCI114 help115 Support the Permedia2 FIFO disconnect feature.116 117config FB_ACORN118 bool "Acorn VIDC support"119 depends on (FB = y) && ARM && ARCH_ACORN120 select FB_IOMEM_HELPERS121 help122 This is the frame buffer device driver for the Acorn VIDC graphics123 hardware found in Acorn RISC PCs and other ARM-based machines. If124 unsure, say N.125 126config FB_CLPS711X127 tristate "CLPS711X LCD support"128 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)129 select FB_IOMEM_HELPERS130 select FB_MODE_HELPERS131 select LCD_CLASS_DEVICE132 select VIDEOMODE_HELPERS133 help134 Say Y to enable the Framebuffer driver for the Cirrus Logic135 CLPS711X CPUs.136 137config FB_SA1100138 bool "SA-1100 LCD support"139 depends on (FB = y) && ARM && ARCH_SA1100140 select FB_IOMEM_HELPERS141 help142 This is a framebuffer device for the SA-1100 LCD Controller.143 See <http://www.linux-fbdev.org/> for information on framebuffer144 devices.145 146 If you plan to use the LCD display with your SA-1100 system, say147 Y here.148 149config FB_IMX150 tristate "Freescale i.MX1/21/25/27 LCD support"151 depends on FB && HAVE_CLK && HAS_IOMEM152 depends on ARCH_MXC || COMPILE_TEST153 select LCD_CLASS_DEVICE154 select FB_IOMEM_HELPERS155 select FB_MODE_HELPERS156 select VIDEOMODE_HELPERS157 158config FB_CYBER2000159 tristate "CyberPro 2000/2010/5000 support"160 depends on FB && PCI && HAS_IOPORT && (BROKEN || !SPARC64)161 select FB_IOMEM_HELPERS162 help163 This enables support for the Integraphics CyberPro 20x0 and 5000164 VGA chips used in the Rebel.com Netwinder and other machines.165 Say Y if you have a NetWinder or a graphics card containing this166 device, otherwise say N.167 168config FB_CYBER2000_DDC169 bool "DDC for CyberPro support"170 depends on FB_CYBER2000171 select FB_DDC172 default y173 help174 Say Y here if you want DDC support for your CyberPro graphics175 card. This is only I2C bus support, driver does not use EDID.176 177config FB_CYBER2000_I2C178 bool "CyberPro 2000/2010/5000 I2C support"179 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER180 depends on I2C=y || FB_CYBER2000=m181 select I2C_ALGOBIT182 help183 Enable support for the I2C video decoder interface on the184 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used185 on the Netwinder machines for the SAA7111 video capture.186 187config FB_APOLLO188 bool189 depends on (FB = y) && APOLLO190 default y191 select FB_CFB_FILLRECT192 select FB_CFB_IMAGEBLIT193 select FB_IOMEM_FOPS194 195config FB_Q40196 bool197 depends on (FB = y) && Q40198 default y199 select FB_IOMEM_HELPERS200 201config FB_AMIGA202 tristate "Amiga native chipset support"203 depends on FB && AMIGA204 select FB_IOMEM_FOPS205 help206 This is the frame buffer device driver for the builtin graphics207 chipset found in Amigas.208 209 To compile this driver as a module, choose M here: the210 module will be called amifb.211 212config FB_AMIGA_OCS213 bool "Amiga OCS chipset support"214 depends on FB_AMIGA215 help216 This enables support for the original Agnus and Denise video chips,217 found in the Amiga 1000 and most A500's and A2000's. If you intend218 to run Linux on any of these systems, say Y; otherwise say N.219 220config FB_AMIGA_ECS221 bool "Amiga ECS chipset support"222 depends on FB_AMIGA223 help224 This enables support for the Enhanced Chip Set, found in later225 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If226 you intend to run Linux on any of these systems, say Y; otherwise227 say N.228 229config FB_AMIGA_AGA230 bool "Amiga AGA chipset support"231 depends on FB_AMIGA232 help233 This enables support for the Advanced Graphics Architecture (also234 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T235 and CD32. If you intend to run Linux on any of these systems, say Y;236 otherwise say N.237 238config FB_FM2239 bool "Amiga FrameMaster II/Rainbow II support"240 depends on (FB = y) && ZORRO241 select FB_IOMEM_HELPERS242 help243 This is the frame buffer device driver for the Amiga FrameMaster244 card from BSC (exhibited 1992 but not shipped as a CBM product).245 246config FB_ARC247 tristate "Arc Monochrome LCD board support"248 depends on FB && HAS_IOPORT && (X86 || COMPILE_TEST)249 select FB_SYSMEM_HELPERS_DEFERRED250 help251 This enables support for the Arc Monochrome LCD board. The board252 is based on the KS-108 lcd controller and is typically a matrix253 of 2*n chips. This driver was tested with a 128x64 panel. This254 driver supports it for use with x86 SBCs through a 16 bit GPIO255 interface (8 bit data, 8 bit control). If you anticipate using256 this driver, say Y or M; otherwise say N. You must specify the257 GPIO IO address to be used for setting control and data.258 259config FB_ATARI260 bool "Atari native chipset support"261 depends on (FB = y) && ATARI262 select FB_CFB_FILLRECT263 select FB_CFB_COPYAREA264 select FB_CFB_IMAGEBLIT265 select FB_IOMEM_FOPS266 help267 This is the frame buffer device driver for the builtin graphics268 chipset found in Ataris.269 270config FB_OF271 tristate "Open Firmware frame buffer device support"272 depends on FB && PPC && (!PPC_PSERIES || PCI)273 depends on !DRM_OFDRM274 select APERTURE_HELPERS275 select FB_IOMEM_HELPERS276 select FB_MACMODES277 help278 Say Y if you want support with Open Firmware for your graphics279 board.280 281config FB_CONTROL282 bool "Apple \"control\" display support"283 depends on (FB = y) && ((PPC_PMAC && PPC32) || COMPILE_TEST)284 select FB_IOMEM_HELPERS285 select FB_MACMODES286 help287 This driver supports a frame buffer for the graphics adapter in the288 Power Macintosh 7300 and others.289 290config FB_PLATINUM291 bool "Apple \"platinum\" display support"292 depends on (FB = y) && PPC_PMAC && PPC32293 select FB_IOMEM_HELPERS294 select FB_MACMODES295 help296 This driver supports a frame buffer for the "platinum" graphics297 adapter in some Power Macintoshes.298 299config FB_VALKYRIE300 bool "Apple \"valkyrie\" display support"301 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))302 select FB_IOMEM_HELPERS303 select FB_MACMODES304 help305 This driver supports a frame buffer for the "valkyrie" graphics306 adapter in some Power Macintoshes.307 308config FB_CT65550309 bool "Chips 65550 display support"310 depends on (FB = y) && PPC32 && PCI311 select FB_IOMEM_HELPERS312 help313 This is the frame buffer device driver for the Chips & Technologies314 65550 graphics chip in PowerBooks.315 316config FB_ASILIANT317 bool "Asiliant (Chips) 69000 display support"318 depends on (FB = y) && PCI319 select FB_IOMEM_HELPERS320 help321 This is the frame buffer device driver for the Asiliant 69030 chipset322 323config FB_IMSTT324 bool "IMS Twin Turbo display support"325 depends on (FB = y) && PCI326 select FB_CFB_IMAGEBLIT327 select FB_IOMEM_FOPS328 select FB_MACMODES if PPC_PMAC329 help330 The IMS Twin Turbo is a PCI-based frame buffer card bundled with331 many Macintosh and compatible computers.332 333config FB_VGA16334 tristate "VGA 16-color graphics support"335 depends on FB && X86336 select APERTURE_HELPERS337 select FB_CFB_FILLRECT338 select FB_CFB_COPYAREA339 select FB_CFB_IMAGEBLIT340 select FB_IOMEM_FOPS341 select VGASTATE342 select FONT_8x16 if FRAMEBUFFER_CONSOLE343 help344 This is the frame buffer device driver for VGA 16 color graphic345 cards. Say Y if you have such a card.346 347 To compile this driver as a module, choose M here: the348 module will be called vga16fb.349 350config FB_STI351 tristate "HP STI frame buffer device support"352 depends on FB && PARISC353 select FB_CFB_FILLRECT354 select FB_CFB_COPYAREA355 select FB_CFB_IMAGEBLIT356 select FB_IOMEM_FOPS357 select STI_CORE358 default y359 help360 Enabling this option will implement the linux framebuffer device361 using calls to the STI BIOS routines for initialisation.362 363 If you enable this option, you will get a planar framebuffer device364 /dev/fb which will work on the most common HP graphic cards of the365 NGLE family, including the artist chips (in the 7xx and Bxxx series),366 HCRX, HCRX24, CRX, CRX24 and VisEG series.367 368 It is safe to enable this option, so you should probably say "Y".369 370config FB_MAC371 bool "Generic Macintosh display support"372 depends on (FB = y) && MAC373 select FB_IOMEM_HELPERS374 select FB_MACMODES375 376config FB_HP300377 bool378 depends on (FB = y) && DIO379 select FB_CFB_IMAGEBLIT380 select FB_IOMEM_FOPS381 default y382 383config FB_TGA384 tristate "TGA/SFB+ framebuffer support"385 depends on FB386 depends on PCI || TC387 depends on ALPHA || TC388 select BITREVERSE389 select FB_CFB_FILLRECT390 select FB_CFB_COPYAREA391 select FB_CFB_IMAGEBLIT392 select FB_IOMEM_FOPS393 help394 This is the frame buffer device driver for generic TGA and SFB+395 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,396 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3397 TURBOchannel cards, also known as PMAGD-A, -B and -C.398 399 Due to hardware limitations ZLX-E2 and E3 cards are not supported400 for DECstation 5000/200 systems. Additionally due to firmware401 limitations these cards may cause troubles with booting DECstation402 5000/240 and /260 systems, but are fully supported under Linux if403 you manage to get it going. ;-)404 405 Say Y if you have one of those.406 407config FB_UVESA408 tristate "Userspace VESA VGA graphics support"409 depends on FB && CONNECTOR410 depends on !UML411 select FB_IOMEM_HELPERS412 select FB_MODE_HELPERS413 help414 This is the frame buffer driver for generic VBE 2.0 compliant415 graphic cards. It can also take advantage of VBE 3.0 features,416 such as refresh rate adjustment.417 418 This driver generally provides more features than vesafb but419 requires a userspace helper application called 'v86d'. See420 <file:Documentation/fb/uvesafb.rst> for more information.421 422 If unsure, say N.423 424config FB_VESA425 bool "VESA VGA graphics support"426 depends on (FB = y) && X86427 select APERTURE_HELPERS428 select FB_IOMEM_HELPERS429 select SYSFB430 help431 This is the frame buffer device driver for generic VESA 2.0432 compliant graphic cards. The older VESA 1.2 cards are not supported.433 You will get a boot time penguin logo at no additional cost. Please434 read <file:Documentation/fb/vesafb.rst>. If unsure, say Y.435 436config FB_EFI437 bool "EFI-based Framebuffer Support"438 depends on (FB = y) && EFI439 select APERTURE_HELPERS440 select DRM_PANEL_ORIENTATION_QUIRKS441 select FB_IOMEM_HELPERS442 select SYSFB443 help444 This is the EFI frame buffer device driver. If the firmware on445 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for446 using the EFI framebuffer as your console.447 448config FB_N411449 tristate "N411 Apollo/Hecuba devkit support"450 depends on FB && X86 && MMU451 select FB_HECUBA452 help453 This enables support for the Apollo display controller in its454 Hecuba form using the n411 devkit.455 456config FB_HGA457 tristate "Hercules mono graphics support"458 depends on FB && X86459 select FB_IOMEM_FOPS460 help461 Say Y here if you have a Hercules mono graphics card.462 463 To compile this driver as a module, choose M here: the464 module will be called hgafb.465 466 As this card technology is at least 25 years old,467 most people will answer N here.468 469config FB_GBE470 bool "SGI Graphics Backend frame buffer support"471 depends on (FB = y) && HAS_IOMEM472 depends on SGI_IP32 || COMPILE_TEST473 select FB_IOMEM_HELPERS474 help475 This is the frame buffer device driver for SGI Graphics Backend.476 This chip is used in SGI O2 and Visual Workstation 320/540.477 478config FB_GBE_MEM479 int "Video memory size in MB"480 depends on FB_GBE481 default 4482 help483 This is the amount of memory reserved for the framebuffer,484 which can be any value between 1MB and 8MB.485 486config FB_SBUS487 bool "SBUS and UPA framebuffers"488 depends on (FB = y) && SPARC489 help490 Say Y if you want support for SBUS or UPA based frame buffer device.491 492config FB_SBUS_HELPERS493 bool494 select FB_CFB_COPYAREA495 select FB_CFB_FILLRECT496 select FB_CFB_IMAGEBLIT497 select FB_IOMEM_FOPS498 499config FB_BW2500 bool "BWtwo support"501 depends on (FB = y) && (SPARC && FB_SBUS)502 select FB_SBUS_HELPERS503 help504 This is the frame buffer device driver for the BWtwo frame buffer.505 506config FB_CG3507 bool "CGthree support"508 depends on (FB = y) && (SPARC && FB_SBUS)509 select FB_SBUS_HELPERS510 help511 This is the frame buffer device driver for the CGthree frame buffer.512 513config FB_CG6514 bool "CGsix (GX,TurboGX) support"515 depends on (FB = y) && (SPARC && FB_SBUS)516 select FB_CFB_COPYAREA517 select FB_CFB_IMAGEBLIT518 select FB_IOMEM_FOPS519 help520 This is the frame buffer device driver for the CGsix (GX, TurboGX)521 frame buffer.522 523config FB_FFB524 bool "Creator/Creator3D/Elite3D support"525 depends on FB_SBUS && SPARC64526 select FB_CFB_COPYAREA527 select FB_CFB_IMAGEBLIT528 select FB_IOMEM_FOPS529 help530 This is the frame buffer device driver for the Creator, Creator3D,531 and Elite3D graphics boards.532 533config FB_TCX534 bool "TCX (SS4/SS5 only) support"535 depends on FB_SBUS536 select FB_SBUS_HELPERS537 help538 This is the frame buffer device driver for the TCX 24/8bit frame539 buffer.540 541config FB_CG14542 bool "CGfourteen (SX) support"543 depends on FB_SBUS544 select FB_SBUS_HELPERS545 help546 This is the frame buffer device driver for the CGfourteen frame547 buffer on Desktop SPARCsystems with the SX graphics option.548 549config FB_P9100550 bool "P9100 (Sparcbook 3 only) support"551 depends on FB_SBUS552 select FB_SBUS_HELPERS553 help554 This is the frame buffer device driver for the P9100 card555 supported on Sparcbook 3 machines.556 557config FB_LEO558 bool "Leo (ZX) support"559 depends on FB_SBUS560 select FB_SBUS_HELPERS561 help562 This is the frame buffer device driver for the SBUS-based Sun ZX563 (leo) frame buffer cards.564 565config FB_XVR500566 bool "Sun XVR-500 3DLABS Wildcat support"567 depends on (FB = y) && PCI && SPARC64568 select FB_CFB_FILLRECT569 select FB_CFB_COPYAREA570 select FB_CFB_IMAGEBLIT571 select FB_IOMEM_FOPS572 help573 This is the framebuffer device for the Sun XVR-500 and similar574 graphics cards based upon the 3DLABS Wildcat chipset. The driver575 only works on sparc64 systems where the system firmware has576 mostly initialized the card already. It is treated as a577 completely dumb framebuffer device.578 579config FB_XVR2500580 bool "Sun XVR-2500 3DLABS Wildcat support"581 depends on (FB = y) && PCI && SPARC64582 select FB_IOMEM_HELPERS583 help584 This is the framebuffer device for the Sun XVR-2500 and similar585 graphics cards based upon the 3DLABS Wildcat chipset. The driver586 only works on sparc64 systems where the system firmware has587 mostly initialized the card already. It is treated as a588 completely dumb framebuffer device.589 590config FB_XVR1000591 bool "Sun XVR-1000 support"592 depends on (FB = y) && SPARC64593 select FB_IOMEM_HELPERS594 help595 This is the framebuffer device for the Sun XVR-1000 and similar596 graphics cards. The driver only works on sparc64 systems where597 the system firmware has mostly initialized the card already. It598 is treated as a completely dumb framebuffer device.599 600config FB_PVR2601 tristate "NEC PowerVR 2 display support"602 depends on FB && HAS_IOMEM603 depends on SH_DREAMCAST || COMPILE_TEST604 select FB_CFB_FILLRECT605 select FB_CFB_COPYAREA606 select FB_CFB_IMAGEBLIT607 select FB_IOMEM_FOPS608 help609 Say Y here if you have a PowerVR 2 card in your box. If you plan to610 run linux on your Dreamcast, you will have to say Y here.611 This driver may or may not work on other PowerVR 2 cards, but is612 totally untested. Use at your own risk. If unsure, say N.613 614 To compile this driver as a module, choose M here: the615 module will be called pvr2fb.616 617 You can pass several parameters to the driver at boot time or at618 module load time. The parameters look like "video=pvr2:XXX", where619 the meaning of XXX can be found at the end of the main source file620 (<file:drivers/video/fbdev/pvr2fb.c>). Please see the file621 <file:Documentation/fb/pvr2fb.rst>.622 623config FB_OPENCORES624 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"625 depends on FB && HAS_DMA626 select FB_IOMEM_HELPERS627 help628 This enables support for the OpenCores VGA/LCD core.629 630 The OpenCores VGA/LCD core is typically used together with631 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor632 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.633 634 The source code and specification for the core is available at635 <https://opencores.org/project,vga_lcd>636 637config FB_S1D13XXX638 tristate "Epson S1D13XXX framebuffer support"639 depends on FB640 select FB_CFB_FILLRECT641 select FB_CFB_COPYAREA642 select FB_CFB_IMAGEBLIT643 select FB_IOMEM_FOPS644 help645 Support for S1D13XXX framebuffer device family (currently only646 working with S1D13806). Product specs at647 <https://vdc.epson.com/>648 649config FB_ATMEL650 tristate "AT91 LCD Controller support"651 depends on FB && OF && HAVE_CLK && HAS_IOMEM652 depends on HAVE_FB_ATMEL || COMPILE_TEST653 select FB_BACKLIGHT654 select FB_IOMEM_HELPERS655 select FB_MODE_HELPERS656 select VIDEOMODE_HELPERS657 help658 This enables support for the AT91 LCD Controller.659 660config FB_NVIDIA661 tristate "nVidia Framebuffer Support"662 depends on FB && PCI663 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT664 select FB_CFB_FILLRECT665 select FB_CFB_COPYAREA666 select FB_CFB_IMAGEBLIT667 select FB_IOMEM_FOPS668 select BITREVERSE669 select VGASTATE670 help671 This driver supports graphics boards with the nVidia chips, TNT672 and newer. For very old chipsets, such as the RIVA128, then use673 the rivafb.674 Say Y if you have such a graphics board.675 676 To compile this driver as a module, choose M here: the677 module will be called nvidiafb.678 679config FB_NVIDIA_I2C680 bool "Enable DDC Support"681 depends on FB_NVIDIA682 select FB_DDC683 help684 This enables I2C support for nVidia Chipsets. This is used685 only for getting EDID information from the attached display686 allowing for robust video mode handling and switching.687 688 Because fbdev-2.6 requires that drivers must be able to689 independently validate video mode parameters, you should say Y690 here.691 692config FB_NVIDIA_DEBUG693 bool "Lots of debug output"694 depends on FB_NVIDIA695 help696 Say Y here if you want the nVidia driver to output all sorts697 of debugging information to provide to the maintainer when698 something goes wrong.699 700config FB_NVIDIA_BACKLIGHT701 bool "Support for backlight control"702 depends on FB_NVIDIA703 default y704 help705 Say Y here if you want to control the backlight of your display.706 707config FB_RIVA708 tristate "nVidia Riva support"709 depends on FB && PCI710 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT711 select FB_CFB_FILLRECT712 select FB_CFB_COPYAREA713 select FB_CFB_IMAGEBLIT714 select FB_IOMEM_FOPS715 select FB_MODE_HELPERS716 select BITREVERSE717 select VGASTATE718 help719 This driver supports graphics boards with the nVidia Riva/Geforce720 chips.721 Say Y if you have such a graphics board.722 723 To compile this driver as a module, choose M here: the724 module will be called rivafb.725 726config FB_RIVA_I2C727 bool "Enable DDC Support"728 depends on FB_RIVA729 select FB_DDC730 help731 This enables I2C support for nVidia Chipsets. This is used732 only for getting EDID information from the attached display733 allowing for robust video mode handling and switching.734 735 Because fbdev-2.6 requires that drivers must be able to736 independently validate video mode parameters, you should say Y737 here.738 739config FB_RIVA_DEBUG740 bool "Lots of debug output"741 depends on FB_RIVA742 help743 Say Y here if you want the Riva driver to output all sorts744 of debugging information to provide to the maintainer when745 something goes wrong.746 747config FB_RIVA_BACKLIGHT748 bool "Support for backlight control"749 depends on FB_RIVA750 default y751 help752 Say Y here if you want to control the backlight of your display.753 754config FB_I740755 tristate "Intel740 support"756 depends on FB && PCI757 select FB_IOMEM_HELPERS758 select FB_MODE_HELPERS759 select VGASTATE760 select FB_DDC761 help762 This driver supports graphics cards based on Intel740 chip.763 764config FB_I810765 tristate "Intel 810/815 support"766 depends on FB && PCI && X86_32 && AGP_INTEL767 select FB_IOMEM_FOPS768 select FB_MODE_HELPERS769 select VGASTATE770 help771 This driver supports the on-board graphics built in to the Intel 810772 and 815 chipsets. Say Y if you have and plan to use such a board.773 774 To compile this driver as a module, choose M here: the775 module will be called i810fb.776 777 For more information, please read778 <file:Documentation/fb/intel810.rst>779 780config FB_I810_GTF781 bool "use VESA Generalized Timing Formula"782 depends on FB_I810783 help784 If you say Y, then the VESA standard, Generalized Timing Formula785 or GTF, will be used to calculate the required video timing values786 per video mode. Since the GTF allows nondiscrete timings787 (nondiscrete being a range of values as opposed to discrete being a788 set of values), you'll be able to use any combination of horizontal789 and vertical resolutions, and vertical refresh rates without having790 to specify your own timing parameters. This is especially useful791 to maximize the performance of an aging display, or if you just792 have a display with nonstandard dimensions. A VESA compliant793 monitor is recommended, but can still work with non-compliant ones.794 If you need or want this, then select this option. The timings may795 not be compliant with Intel's recommended values. Use at your own796 risk.797 798 If you say N, the driver will revert to discrete video timings799 using a set recommended by Intel in their documentation.800 801 If unsure, say N.802 803config FB_I810_I2C804 bool "Enable DDC Support"805 depends on FB_I810 && FB_I810_GTF806 select FB_DDC807 help808 Add DDC/I2C support for i810fb. This will allow the driver to get809 display information, especially for monitors with fickle timings.810 811 If unsure, say Y.812 813config FB_MATROX814 tristate "Matrox acceleration"815 depends on FB && PCI816 select FB_CFB_FILLRECT817 select FB_CFB_COPYAREA818 select FB_CFB_IMAGEBLIT819 select FB_IOMEM_FOPS820 select FB_TILEBLITTING821 select FB_MACMODES if PPC_PMAC822 help823 Say Y here if you have a Matrox Millennium, Matrox Millennium II,824 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox825 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,826 Matrox G400, G450 or G550 card in your box.827 828 To compile this driver as a module, choose M here: the829 module will be called matroxfb.830 831 You can pass several parameters to the driver at boot time or at832 module load time. The parameters look like "video=matroxfb:XXX", and833 are described in <file:Documentation/fb/matroxfb.rst>.834 835config FB_MATROX_MILLENIUM836 bool "Millennium I/II support"837 depends on FB_MATROX838 help839 Say Y here if you have a Matrox Millennium or Matrox Millennium II840 video card. If you select "Advanced lowlevel driver options" below,841 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp842 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can843 also use font widths different from 8.844 845config FB_MATROX_MYSTIQUE846 bool "Mystique support"847 depends on FB_MATROX848 help849 Say Y here if you have a Matrox Mystique or Matrox Mystique 220850 video card. If you select "Advanced lowlevel driver options" below,851 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp852 packed pixel and 32 bpp packed pixel. You can also use font widths853 different from 8.854 855config FB_MATROX_G856 bool "G100/G200/G400/G450/G550 support"857 depends on FB_MATROX858 help859 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based860 video card. If you select "Advanced lowlevel driver options", you861 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed862 pixel and 32 bpp packed pixel. You can also use font widths863 different from 8.864 865 If you need support for G400 secondary head, you must say Y to866 "Matrox I2C support" and "G400 second head support" right below.867 G450/G550 secondary head and digital output are supported without868 additional modules.869 870 The driver starts in monitor mode. You must use the matroxset tool871 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to872 swap primary and secondary head outputs, or to change output mode.873 Secondary head driver always start in 640x480 resolution and you874 must use fbset to change it.875 876 Do not forget that second head supports only 16 and 32 bpp877 packed pixels, so it is a good idea to compile them into the kernel878 too. You can use only some font widths, as the driver uses generic879 painting procedures (the secondary head does not use acceleration880 engine).881 882 G450/G550 hardware can display TV picture only from secondary CRTC,883 and it performs no scaling, so picture must have 525 or 625 lines.884 885config FB_MATROX_I2C886 tristate "Matrox I2C support"887 depends on FB_MATROX888 select FB_DDC889 help890 This drivers creates I2C buses which are needed for accessing the891 DDC (I2C) bus present on all Matroxes, an I2C bus which892 interconnects Matrox optional devices, like MGA-TVO on G200 and893 G400, and the secondary head DDC bus, present on G400 only.894 895 You can say Y or M here if you want to experiment with monitor896 detection code. You must say Y or M here if you want to use either897 second head of G400 or MGA-TVO on G200 or G400.898 899 If you compile it as module, it will create a module named900 i2c-matroxfb.901 902config FB_MATROX_MAVEN903 tristate "G400 second head support"904 depends on FB_MATROX_G && FB_MATROX_I2C905 select FB_IOMEM_HELPERS906 help907 WARNING !!! This support does not work with G450 !!!908 909 Say Y or M here if you want to use a secondary head (meaning two910 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary911 head is not compatible with accelerated XFree 3.3.x SVGA servers -912 secondary head output is blanked while you are in X. With XFree913 3.9.17 preview you can use both heads if you use SVGA over fbdev or914 the fbdev driver on first head and the fbdev driver on second head.915 916 If you compile it as module, two modules are created,917 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for918 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must919 also load i2c-matroxfb to get it to run.920 921 The driver starts in monitor mode and you must use the matroxset922 tool (available at923 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to924 PAL or NTSC or to swap primary and secondary head outputs.925 Secondary head driver also always start in 640x480 resolution, you926 must use fbset to change it.927 928 Also do not forget that second head supports only 16 and 32 bpp929 packed pixels, so it is a good idea to compile them into the kernel930 too. You can use only some font widths, as the driver uses generic931 painting procedures (the secondary head does not use acceleration932 engine).933 934config FB_RADEON935 tristate "ATI Radeon display support"936 depends on FB && PCI937 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT938 select FB_CFB_FILLRECT939 select FB_CFB_COPYAREA940 select FB_CFB_IMAGEBLIT941 select FB_IOMEM_FOPS942 select FB_MACMODES if PPC943 select FB_MODE_HELPERS944 help945 Choose this option if you want to use an ATI Radeon graphics card as946 a framebuffer device. There are both PCI and AGP versions. You947 don't need to choose this to run the Radeon in plain VGA mode.948 949 There is a product page at950 https://products.amd.com/en-us/GraphicCardResult.aspx951 952config FB_RADEON_I2C953 bool "DDC/I2C for ATI Radeon support"954 depends on FB_RADEON955 select FB_DDC956 default y957 help958 Say Y here if you want DDC/I2C support for your Radeon board.959 960config FB_RADEON_BACKLIGHT961 bool "Support for backlight control"962 depends on FB_RADEON963 default y964 help965 Say Y here if you want to control the backlight of your display.966 967config FB_RADEON_DEBUG968 bool "Lots of debug output from Radeon driver"969 depends on FB_RADEON970 help971 Say Y here if you want the Radeon driver to output all sorts972 of debugging information to provide to the maintainer when973 something goes wrong.974 975config FB_ATY128976 tristate "ATI Rage128 display support"977 depends on FB && PCI978 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT979 select FB_IOMEM_HELPERS980 select FB_MACMODES if PPC_PMAC981 help982 This driver supports graphics boards with the ATI Rage128 chips.983 Say Y if you have such a graphics board and read984 <file:Documentation/fb/aty128fb.rst>.985 986 To compile this driver as a module, choose M here: the987 module will be called aty128fb.988 989config FB_ATY128_BACKLIGHT990 bool "Support for backlight control"991 depends on FB_ATY128992 default y993 help994 Say Y here if you want to control the backlight of your display.995 996config FB_ATY997 tristate "ATI Mach64 display support" if PCI || ATARI998 depends on FB && !SPARC32999 select FB_CFB_FILLRECT1000 select FB_CFB_COPYAREA1001 select FB_CFB_IMAGEBLIT1002 select FB_BACKLIGHT if FB_ATY_BACKLIGHT1003 select FB_IOMEM_FOPS1004 select FB_MACMODES if PPC1005 select FB_ATY_CT if SPARC64 && PCI1006 help1007 This driver supports graphics boards with the ATI Mach64 chips.1008 Say Y if you have such a graphics board.1009 1010 To compile this driver as a module, choose M here: the1011 module will be called atyfb.1012 1013config FB_ATY_CT1014 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"1015 depends on PCI && FB_ATY1016 help1017 Say Y here to support use of ATI's 64-bit Rage boards (or other1018 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a1019 framebuffer device. The ATI product support page for these boards1020 is at <http://support.ati.com/products/pc/mach64/mach64.html>.1021 1022config FB_ATY_GENERIC_LCD1023 bool "Mach64 generic LCD support"1024 depends on FB_ATY_CT1025 help1026 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,1027 Rage XC, or Rage XL chipset.1028 1029config FB_ATY_GX1030 bool "Mach64 GX support" if PCI1031 depends on FB_ATY1032 default y if ATARI1033 help1034 Say Y here to support use of the ATI Mach64 Graphics Expression1035 board (or other boards based on the Mach64 GX chipset) as a1036 framebuffer device. The ATI product support page for these boards1037 is at1038 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.1039 1040config FB_ATY_BACKLIGHT1041 bool "Support for backlight control"1042 depends on FB_ATY1043 default y1044 help1045 Say Y here if you want to control the backlight of your display.1046 1047config FB_S31048 tristate "S3 Trio/Virge support"1049 depends on FB && PCI && HAS_IOPORT1050 select FB_CFB_FILLRECT1051 select FB_CFB_COPYAREA1052 select FB_CFB_IMAGEBLIT1053 select FB_IOMEM_FOPS1054 select FB_TILEBLITTING1055 select FB_SVGALIB1056 select VGASTATE1057 select FONT_8x16 if FRAMEBUFFER_CONSOLE1058 help1059 Driver for graphics boards with S3 Trio / S3 Virge chip.1060 1061config FB_S3_DDC1062 bool "DDC for S3 support"1063 depends on FB_S31064 select FB_DDC1065 default y1066 help1067 Say Y here if you want DDC support for your S3 graphics card.1068 1069config FB_SAVAGE1070 tristate "S3 Savage support"1071 depends on FB && PCI1072 select FB_CFB_FILLRECT1073 select FB_CFB_COPYAREA1074 select FB_CFB_IMAGEBLIT1075 select FB_IOMEM_FOPS1076 select FB_MODE_HELPERS1077 select VGASTATE1078 help1079 This driver supports notebooks and computers with S3 Savage PCI/AGP1080 chips.1081 1082 Say Y if you have such a graphics card.1083 1084 To compile this driver as a module, choose M here; the module1085 will be called savagefb.1086 1087config FB_SAVAGE_I2C1088 bool "Enable DDC2 Support"1089 depends on FB_SAVAGE1090 select FB_DDC1091 help1092 This enables I2C support for S3 Savage Chipsets. This is used1093 only for getting EDID information from the attached display1094 allowing for robust video mode handling and switching.1095 1096 Because fbdev-2.6 requires that drivers must be able to1097 independently validate video mode parameters, you should say Y1098 here.1099 1100config FB_SAVAGE_ACCEL1101 bool "Enable Console Acceleration"1102 depends on FB_SAVAGE1103 help1104 This option will compile in console acceleration support. If1105 the resulting framebuffer console has bothersome glitches, then1106 choose N here.1107 1108config FB_SIS1109 tristate "SiS/XGI display support"1110 depends on FB && PCI && HAS_IOPORT1111 select BOOT_VESA_SUPPORT if FB_SIS = y1112 select FB_CFB_FILLRECT1113 select FB_CFB_COPYAREA1114 select FB_CFB_IMAGEBLIT1115 select FB_IOMEM_FOPS1116 select FB_SIS_300 if !FB_SIS_3151117 help1118 This is the frame buffer device driver for the SiS 300, 315, 3301119 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.1120 Specs available at <https://www.sis.com> and <http://www.xgitech.com>.1121 1122 To compile this driver as a module, choose M here; the module1123 will be called sisfb.1124 1125config FB_SIS_3001126 bool "SiS 300 series support"1127 depends on FB_SIS1128 help1129 Say Y here to support use of the SiS 300/305, 540, 630 and 730.1130 1131config FB_SIS_3151132 bool "SiS 315/330/340 series and XGI support"1133 depends on FB_SIS1134 help1135 Say Y here to support use of the SiS 315, 330 and 340 series1136 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well1137 as XGI V3XT, V5, V8 and Z7.1138 1139config FB_VIA1140 tristate "VIA UniChrome (Pro) and Chrome9 display support"1141 depends on FB && PCI && GPIOLIB && I2C && HAS_IOPORT && (X86 || COMPILE_TEST)1142 select FB_CFB_FILLRECT1143 select FB_CFB_COPYAREA1144 select FB_CFB_IMAGEBLIT1145 select FB_IOMEM_FOPS1146 select I2C_ALGOBIT1147 help1148 This is the frame buffer device driver for Graphics chips of VIA1149 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/1150 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN8961151 /P4M900,VX800)1152 Say Y if you have a VIA UniChrome graphics board.1153 1154 To compile this driver as a module, choose M here: the1155 module will be called viafb.1156 1157if FB_VIA1158 1159config FB_VIA_DIRECT_PROCFS1160 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"1161 help1162 Allow direct hardware access to some output registers via procfs.1163 This is dangerous but may provide the only chance to get the1164 correct output device configuration.1165 Its use is strongly discouraged.1166 1167config FB_VIA_X_COMPATIBILITY1168 bool "X server compatibility"1169 help1170 This option reduces the functionality (power saving, ...) of the1171 framebuffer to avoid negative impact on the OpenChrome X server.1172 If you use any X server other than fbdev you should enable this1173 otherwise it should be safe to disable it and allow using all1174 features.1175 1176endif1177 1178config FB_NEOMAGIC1179 tristate "NeoMagic display support"1180 depends on FB && PCI && HAS_IOPORT1181 select FB_CFB_FILLRECT1182 select FB_CFB_COPYAREA1183 select FB_CFB_IMAGEBLIT1184 select FB_IOMEM_FOPS1185 select FB_MODE_HELPERS1186 select VGASTATE1187 help1188 This driver supports notebooks with NeoMagic PCI chips.1189 Say Y if you have such a graphics card.1190 1191 To compile this driver as a module, choose M here: the1192 module will be called neofb.1193 1194config FB_KYRO1195 tristate "IMG Kyro support"1196 depends on FB && PCI1197 select FB_IOMEM_HELPERS1198 help1199 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based1200 graphics board.1201 1202 To compile this driver as a module, choose M here: the1203 module will be called kyrofb.1204 1205config FB_3DFX1206 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"1207 depends on FB && PCI && HAS_IOPORT1208 select FB_CFB_FILLRECT1209 select FB_CFB_COPYAREA1210 select FB_CFB_IMAGEBLIT1211 select FB_IOMEM_FOPS1212 select FB_MODE_HELPERS1213 help1214 This driver supports graphics boards with the 3Dfx Banshee,1215 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have1216 such a graphics board.1217 1218 To compile this driver as a module, choose M here: the1219 module will be called tdfxfb.1220 1221config FB_3DFX_ACCEL1222 bool "3Dfx Acceleration functions"1223 depends on FB_3DFX1224 help1225 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer1226 device driver with acceleration functions.1227 1228config FB_3DFX_I2C1229 bool "Enable DDC/I2C support"1230 depends on FB_3DFX1231 select FB_DDC1232 default y1233 help1234 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.1235 1236config FB_VOODOO11237 tristate "3Dfx Voodoo Graphics (sst1) support"1238 depends on FB && PCI1239 select FB_IOMEM_HELPERS1240 help1241 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or1242 Voodoo2 (cvg) based graphics card.1243 1244 To compile this driver as a module, choose M here: the1245 module will be called sstfb.1246 1247 WARNING: Do not use any application that uses the 3D engine1248 (namely glide) while using this driver.1249 Please read the <file:Documentation/fb/sstfb.rst> for supported1250 options and other important info support.1251 1252config FB_VT86231253 tristate "VIA VT8623 support"1254 depends on FB && PCI && HAS_IOPORT1255 select FB_CFB_FILLRECT1256 select FB_CFB_COPYAREA1257 select FB_CFB_IMAGEBLIT1258 select FB_IOMEM_FOPS1259 select FB_TILEBLITTING1260 select FB_SVGALIB1261 select VGASTATE1262 select FONT_8x16 if FRAMEBUFFER_CONSOLE1263 help1264 Driver for CastleRock integrated graphics core in the1265 VIA VT8623 [Apollo CLE266] chipset.1266 1267config FB_TRIDENT1268 tristate "Trident/CyberXXX/CyberBlade support"1269 depends on FB && PCI && HAS_IOPORT1270 select FB_CFB_FILLRECT1271 select FB_CFB_COPYAREA1272 select FB_CFB_IMAGEBLIT1273 select FB_DDC1274 select FB_IOMEM_FOPS1275 select FB_MODE_HELPERS1276 help1277 This is the frame buffer device driver for Trident PCI/AGP chipsets.1278 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D1279 and Blade XP.1280 There are also integrated versions of these chips called CyberXXXX,1281 CyberImage or CyberBlade. These chips are mostly found in laptops1282 but also on some motherboards including early VIA EPIA motherboards.1283 For more information, read <file:Documentation/fb/tridentfb.rst>1284 1285 Say Y if you have such a graphics board.1286 1287 To compile this driver as a module, choose M here: the1288 module will be called tridentfb.1289 1290config FB_ARK1291 tristate "ARK 2000PV support"1292 depends on FB && PCI && HAS_IOPORT1293 select FB_CFB_FILLRECT1294 select FB_CFB_COPYAREA1295 select FB_CFB_IMAGEBLIT1296 select FB_IOMEM_FOPS1297 select FB_TILEBLITTING1298 select FB_SVGALIB1299 select VGASTATE1300 select FONT_8x16 if FRAMEBUFFER_CONSOLE1301 help1302 Driver for PCI graphics boards with ARK 2000PV chip1303 and ICS 5342 RAMDAC.1304 1305config FB_PM31306 tristate "Permedia3 support"1307 depends on FB && PCI1308 select FB_CFB_FILLRECT1309 select FB_CFB_COPYAREA1310 select FB_CFB_IMAGEBLIT1311 select FB_IOMEM_FOPS1312 help1313 This is the frame buffer device driver for the 3DLabs Permedia31314 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &1315 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 20001316 and maybe other boards.1317 1318config FB_CARMINE1319 tristate "Fujitsu carmine frame buffer support"1320 depends on FB && PCI1321 select FB_IOMEM_HELPERS1322 help1323 This is the frame buffer device driver for the Fujitsu Carmine chip.1324 The driver provides two independent frame buffer devices.1325 1326choice1327 depends on FB_CARMINE1328 prompt "DRAM timing"1329 default FB_CARMINE_DRAM_EVAL1330 1331config FB_CARMINE_DRAM_EVAL1332 bool "Eval board timings"1333 help1334 Use timings which work on the eval card.1335 1336config CARMINE_DRAM_CUSTOM1337 bool "Custom board timings"1338 help1339 Use custom board timings.1340endchoice1341 1342config FB_AU11001343 bool "Au1100 LCD Driver"1344 depends on (FB = y) && MIPS_ALCHEMY1345 select FB_IOMEM_HELPERS1346 help1347 This is the framebuffer driver for the AMD Au1100 SOC. It can drive1348 various panels and CRTs by passing in kernel cmd line option1349 au1100fb:panel=<name>.1350 1351config FB_AU12001352 bool "Au1200/Au1300 LCD Driver"1353 depends on (FB = y) && MIPS_ALCHEMY1354 select FB_DMAMEM_HELPERS1355 help1356 This is the framebuffer driver for the Au1200/Au1300 SOCs.1357 It can drive various panels and CRTs by passing in kernel cmd line1358 option au1200fb:panel=<name>.1359 1360config FB_VT85001361 bool "VIA VT8500 framebuffer support"1362 depends on (FB = y) && ARM && ARCH_VT85001363 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)1364 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)1365 select FB_SYS_IMAGEBLIT1366 select FB_SYSMEM_FOPS1367 select FB_MODE_HELPERS1368 select VIDEOMODE_HELPERS1369 help1370 This is the framebuffer driver for VIA VT8500 integrated LCD1371 controller.1372 1373config FB_WM85051374 bool "Wondermedia WM8xxx-series frame buffer support"1375 depends on (FB = y) && HAS_IOMEM && (ARCH_VT8500 || COMPILE_TEST)1376 select FB_IOMEM_FOPS1377 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)1378 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)1379 select FB_SYS_IMAGEBLIT1380 select FB_SYSMEM_FOPS1381 select FB_MODE_HELPERS1382 select VIDEOMODE_HELPERS1383 help1384 This is the framebuffer driver for WonderMedia WM8xxx-series1385 integrated LCD controller. This driver covers the WM8505, WM86501386 and WM8850 SoCs.1387 1388config FB_WMT_GE_ROPS1389 bool "VT8500/WM8xxx accelerated raster ops support"1390 depends on (FB = y) && (FB_VT8500 || FB_WM8505)1391 help1392 This adds support for accelerated raster operations on the1393 VIA VT8500 and Wondermedia 85xx series SoCs.1394 1395source "drivers/video/fbdev/geode/Kconfig"1396 1397config FB_HIT1398 tristate "HD64461 Frame Buffer support"1399 depends on FB && HD644611400 select FB_CFB_FILLRECT1401 select FB_CFB_IMAGEBLIT1402 select FB_IOMEM_FOPS1403 help1404 This is the frame buffer device driver for the Hitachi HD64461 LCD1405 frame buffer card.1406 1407config FB_PMAG_AA1408 tristate "PMAG-AA TURBOchannel framebuffer support"1409 depends on FB && TC1410 select FB_IOMEM_HELPERS1411 help1412 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)1413 used mainly in the MIPS-based DECstation series.1414 1415config FB_PMAG_BA1416 tristate "PMAG-BA TURBOchannel framebuffer support"1417 depends on FB && TC1418 select FB_IOMEM_HELPERS1419 help1420 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)1421 used mainly in the MIPS-based DECstation series.1422 1423config FB_PMAGB_B1424 tristate "PMAGB-B TURBOchannel framebuffer support"1425 depends on FB && TC1426 select FB_IOMEM_HELPERS1427 help1428 Support for the PMAGB-B TURBOchannel framebuffer card used mainly1429 in the MIPS-based DECstation series. The card is currently only1430 supported in 1280x1024x8 mode.1431 1432config FB_MAXINE1433 bool "Maxine (Personal DECstation) onboard framebuffer support"1434 depends on (FB = y) && MACH_DECSTATION1435 select FB_IOMEM_HELPERS1436 help1437 Support for the onboard framebuffer (1024x768x8) in the Personal1438 DECstation series (Personal DECstation 5000/20, /25, /33, /50,1439 Codename "Maxine").1440 1441config FB_G3641442 bool "G364 frame buffer support"1443 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)1444 select FB_IOMEM_HELPERS1445 help1446 The G364 driver is the framebuffer used in MIPS Magnum 4000 and1447 Olivetti M700-10 systems.1448 1449config FB_683281450 bool "Motorola 68328 native frame buffer support"1451 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)1452 select FB_IOMEM_HELPERS1453 help1454 Say Y here if you want to support the built-in frame buffer of1455 the Motorola 68328 CPU family.1456 1457config FB_PXA1681458 tristate "PXA168/910 LCD framebuffer support"1459 depends on FB && HAVE_CLK && HAS_IOMEM1460 depends on CPU_PXA168 || CPU_PXA910 || COMPILE_TEST1461 select FB_IOMEM_HELPERS1462 help1463 Frame buffer driver for the built-in LCD controller in the Marvell1464 MMP processor.1465 1466config FB_PXA1467 tristate "PXA LCD framebuffer support"1468 depends on FB && ARCH_PXA1469 select FB_IOMEM_HELPERS1470 select VIDEOMODE_HELPERS if OF1471 select FB_MODE_HELPERS if OF1472 help1473 Frame buffer driver for the built-in LCD controller in the Intel1474 PXA2x0 processor.1475 1476 This driver is also available as a module ( = code which can be1477 inserted and removed from the running kernel whenever you want). The1478 module will be called pxafb. If you want to compile it as a module,1479 say M here and read <file:Documentation/kbuild/modules.rst>.1480 1481 If unsure, say N.1482 1483config FB_PXA_OVERLAY1484 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"1485 depends on FB_PXA && (PXA27x || PXA3xx)1486 1487config FB_PXA_SMARTPANEL1488 bool "PXA Smartpanel LCD support"1489 depends on FB_PXA1490 1491config FB_PXA_PARAMETERS1492 bool "PXA LCD command line parameters"1493 depends on FB_PXA1494 help1495 Enable the use of kernel command line or module parameters1496 to configure the physical properties of the LCD panel when1497 using the PXA LCD driver.1498 1499 This option allows you to override the panel parameters1500 supplied by the platform in order to support multiple1501 different models of flatpanel. If you will only be using a1502 single model of flatpanel then you can safely leave this1503 option disabled.1504 1505 <file:Documentation/fb/pxafb.rst> describes the available parameters.1506 1507config PXA3XX_GCU1508 tristate "PXA3xx 2D graphics accelerator driver"1509 depends on FB_PXA1510 help1511 Kernelspace driver for the 2D graphics controller unit (GCU)1512 found on PXA3xx processors. There is a counterpart driver in the1513 DirectFB suite, see http://www.directfb.org/1514 1515 If you compile this as a module, it will be called pxa3xx_gcu.1516 1517config FB_FSL_DIU1518 tristate "Freescale DIU framebuffer support"1519 depends on FB && FSL_SOC1520 select FB_IOMEM_HELPERS1521 select FB_MODE_HELPERS1522 select PPC_LIB_RHEAP1523 help1524 Framebuffer driver for the Freescale SoC DIU1525 1526config FB_SH_MOBILE_LCDC1527 tristate "SuperH Mobile LCDC framebuffer support"1528 depends on FB && HAVE_CLK && HAS_IOMEM1529 depends on SUPERH || COMPILE_TEST1530 depends on FB_DEVICE1531 select FB_BACKLIGHT1532 select FB_DEFERRED_IO1533 select FB_DMAMEM_HELPERS1534 help1535 Frame buffer driver for the on-chip SH-Mobile LCD controller.1536 1537config FB_S3C1538 tristate "Samsung S3C framebuffer support"1539 depends on FB && HAVE_CLK && HAS_IOMEM1540 depends on ARCH_S3C64XX || COMPILE_TEST1541 select FB_IOMEM_HELPERS1542 help1543 Frame buffer driver for the built-in FB controller in the Samsung1544 SoC line such as the S3C6400 and S3C6410.1545 1546 These chips all have the same basic framebuffer design with the1547 actual capabilities depending on the chip. The S3C64001548 and S3C6410 support 4 hardware windows.1549 1550 Currently the support is only for the S3C6400 and S3C6410 SoCs.1551 1552config FB_S3C_DEBUG_REGWRITE1553 bool "Debug register writes"1554 depends on FB_S3C1555 help1556 Show all register writes via pr_debug()1557 1558config FB_SM5011559 tristate "Silicon Motion SM501 framebuffer support"1560 depends on FB && MFD_SM5011561 select FB_CFB_FILLRECT1562 select FB_CFB_COPYAREA1563 select FB_CFB_IMAGEBLIT1564 select FB_IOMEM_FOPS1565 help1566 Frame buffer driver for the CRT and LCD controllers in the Silicon1567 Motion SM501.1568 1569 This driver is also available as a module ( = code which can be1570 inserted and removed from the running kernel whenever you want). The1571 module will be called sm501fb. If you want to compile it as a module,1572 say M here and read <file:Documentation/kbuild/modules.rst>.1573 1574 If unsure, say N.1575 1576config FB_SMSCUFX1577 tristate "SMSC UFX6000/7000 USB Framebuffer support"1578 depends on FB && USB1579 select FB_MODE_HELPERS1580 select FB_SYSMEM_HELPERS_DEFERRED1581 help1582 This is a kernel framebuffer driver for SMSC UFX USB devices.1583 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and1584 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX70001585 (USB 3.0) devices.1586 To compile as a module, choose M here: the module name is smscufx.1587 1588config FB_UDL1589 tristate "Displaylink USB Framebuffer support"1590 depends on FB && USB1591 depends on FB_DEVICE1592 select FB_MODE_HELPERS1593 select FB_SYSMEM_HELPERS_DEFERRED1594 help1595 This is a kernel framebuffer driver for DisplayLink USB devices.1596 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and1597 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.1598 To compile as a module, choose M here: the module name is udlfb.1599 1600config FB_IBM_GXT45001601 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"1602 depends on FB1603 select FB_IOMEM_HELPERS1604 help1605 Say Y here to enable support for the IBM GXT4000P/6000P and1606 GXT4500P/6500P display adaptor based on Raster Engine RC1000,1607 found on some IBM System P (pSeries) machines. This driver1608 doesn't use Geometry Engine GT1000. This driver also supports1609 AGP Fire GL2/3/4 cards on x86.1610 1611config FB_PS31612 tristate "PS3 GPU framebuffer driver"1613 depends on FB && PS3_PS3AV1614 select FB_SYSMEM_HELPERS1615 help1616 Include support for the virtual frame buffer in the PS3 platform.1617 1618config FB_PS3_DEFAULT_SIZE_M1619 int "PS3 default frame buffer size (in MiB)"1620 depends on FB_PS31621 default 91622 help1623 This is the default size (in MiB) of the virtual frame buffer in1624 the PS3.1625 The default value can be overridden on the kernel command line1626 using the "ps3fb" option (e.g. "ps3fb=9M");1627 1628config FB_XILINX1629 tristate "Xilinx frame buffer support"1630 depends on FB && (MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)1631 select FB_IOMEM_HELPERS1632 help1633 Include support for the Xilinx ML300/ML403 reference design1634 framebuffer. ML300 carries a 640*480 LCD display on the board,1635 ML403 uses a standard DB15 VGA connector.1636 1637config FB_GOLDFISH1638 tristate "Goldfish Framebuffer"1639 depends on FB1640 depends on GOLDFISH || COMPILE_TEST1641 select FB_IOMEM_HELPERS1642 help1643 Framebuffer driver for Goldfish Virtual Platform1644 1645config FB_COBALT1646 tristate "Cobalt server LCD frame buffer support"1647 depends on FB && MIPS_COBALT1648 select FB_IOMEM_HELPERS1649 1650config FB_SH77601651 tristate "SH7760/SH7763/SH7720/SH7721 LCDC support"1652 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \1653 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)1654 select FB_IOMEM_HELPERS1655 help1656 Support for the SH7760/SH7763/SH7720/SH7721 integrated1657 (D)STN/TFT LCD Controller.1658 Supports display resolutions up to 1024x1024 pixel, grayscale and1659 color operation, with depths ranging from 1 bpp to 8 bpp monochrome1660 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for1661 panels <= 320 pixel horizontal resolution.1662 1663config FB_VIRTUAL1664 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"1665 depends on FB1666 select FB_SYSMEM_HELPERS1667 help1668 This is a `virtual' frame buffer device. It operates on a chunk of1669 unswappable kernel memory instead of on the memory of a graphics1670 board. This means you cannot see any output sent to this frame1671 buffer device, while it does consume precious memory. The main use1672 of this frame buffer device is testing and debugging the frame1673 buffer subsystem. Do NOT enable it for normal systems! To protect1674 the innocent, it has to be enabled explicitly at boot time using the1675 kernel option `video=vfb:'.1676 1677 To compile this driver as a module, choose M here: the1678 module will be called vfb. In order to load it, you must use1679 the vfb_enable=1 option.1680 1681 If unsure, say N.1682 1683config XEN_FBDEV_FRONTEND1684 tristate "Xen virtual frame buffer support"1685 depends on FB && XEN1686 select FB_SYSMEM_HELPERS_DEFERRED1687 select XEN_XENBUS_FRONTEND1688 default y1689 help1690 This driver implements the front-end of the Xen virtual1691 frame buffer driver. It communicates with a back-end1692 in another domain.1693 1694config FB_METRONOME1695 tristate "E-Ink Metronome/8track controller support"1696 depends on FB1697 select FB_SYSMEM_HELPERS_DEFERRED1698 help1699 This driver implements support for the E-Ink Metronome1700 controller. The pre-release name for this device was 8track1701 and could also have been called by some vendors as PVI-nnnn.1702 1703config FB_MB862XX1704 tristate "Fujitsu MB862xx GDC support"1705 depends on FB1706 depends on PCI || (OF && PPC)1707 select FB_IOMEM_HELPERS1708 help1709 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.1710 1711choice1712 prompt "GDC variant"1713 depends on FB_MB862XX1714 1715config FB_MB862XX_PCI_GDC1716 bool "Carmine/Coral-P(A) GDC"1717 depends on PCI1718 help1719 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)1720 PCI graphics controller devices.1721 1722config FB_MB862XX_LIME1723 bool "Lime GDC"1724 depends on OF && PPC1725 select FB_FOREIGN_ENDIAN1726 select FB_LITTLE_ENDIAN1727 help1728 Framebuffer support for Fujitsu Lime GDC on host CPU bus.1729 1730endchoice1731 1732config FB_MB862XX_I2C1733 bool "Support I2C bus on MB862XX GDC"1734 depends on FB_MB862XX && I2C1735 depends on FB_MB862XX=m || I2C=y1736 default y1737 help1738 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter1739 driver to support accessing I2C devices on controller's I2C bus.1740 These are usually some video decoder chips.1741 1742config FB_EP93XX1743 tristate "EP93XX frame buffer support"1744 depends on FB && ARCH_EP93XX1745 select FB_IOMEM_HELPERS1746 help1747 Framebuffer driver for the Cirrus Logic EP93XX series of processors.1748 This driver is also available as a module. The module will be called1749 ep93xx-fb.1750 1751config FB_PRE_INIT_FB1752 bool "Don't reinitialize, use bootloader's GDC/Display configuration"1753 depends on FB && FB_MB862XX_LIME1754 help1755 Select this option if display contents should be inherited as set by1756 the bootloader.1757 1758config FB_BROADSHEET1759 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"1760 depends on FB && (ARCH_PXA || COMPILE_TEST)1761 select FB_SYSMEM_HELPERS_DEFERRED1762 help1763 This driver implements support for the E-Ink Broadsheet1764 controller. The release name for this device was Epson S1D135211765 and could also have been called by other names when coupled with1766 a bridge adapter.1767 1768config FB_HYPERV1769 tristate "Microsoft Hyper-V Synthetic Video support"1770 depends on FB && HYPERV1771 select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA1772 select FB_IOMEM_HELPERS_DEFERRED1773 help1774 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.1775 1776config FB_SIMPLE1777 tristate "Simple framebuffer support"1778 depends on FB1779 depends on !DRM_SIMPLEDRM1780 select APERTURE_HELPERS1781 select FB_IOMEM_HELPERS1782 help1783 Say Y if you want support for a simple frame-buffer.1784 1785 This driver assumes that the display hardware has been initialized1786 before the kernel boots, and the kernel will simply render to the1787 pre-allocated frame buffer surface.1788 1789 Configuration re: surface address, size, and format must be provided1790 through device tree, or plain old platform data.1791 1792config FB_SSD13071793 tristate "Solomon SSD1307 framebuffer support"1794 depends on FB && I2C1795 depends on GPIOLIB || COMPILE_TEST1796 select FB_BACKLIGHT1797 select FB_SYSMEM_HELPERS_DEFERRED1798 help1799 This driver implements support for the Solomon SSD13071800 OLED controller over I2C.1801 1802config FB_SM7121803 tristate "Silicon Motion SM712 framebuffer support"1804 depends on FB && PCI && HAS_IOPORT1805 select FB_IOMEM_HELPERS1806 help1807 Frame buffer driver for the Silicon Motion SM710, SM712, SM7211808 and SM722 chips.1809 1810 This driver is also available as a module. The module will be1811 called sm712fb. If you want to compile it as a module, say M1812 here and read <file:Documentation/kbuild/modules.rst>.1813 1814source "drivers/video/fbdev/omap/Kconfig"1815source "drivers/video/fbdev/omap2/Kconfig"1816source "drivers/video/fbdev/mmp/Kconfig"1817 1818source "drivers/video/fbdev/core/Kconfig"1819