1 # SPDX-License-Identifier: GPL-2.0-only
7 tristate "Support for frame buffer device drivers"
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.
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.
24 The device is accessed through special device nodes, usually located
25 in the /dev directory, i.e. /dev/fb*.
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
33 This enables support for native frame buffer device (fbdev) drivers.
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
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.
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.
51 select FB_SYSMEM_HELPERS_DEFERRED
57 Common utility functions useful to fbdev drivers of VGA-based
65 tristate "Aeroflex Gaisler framebuffer support"
66 depends on FB && SPARC
67 select FB_IOMEM_HELPERS
69 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
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 VIDEO_NOMODESET
79 This enables support for Cirrus Logic GD542x/543x based boards on
80 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
82 If you have a PCI-based system, this enables support for these
83 chips: GD-543x, GD-544x, GD-5480.
85 Please read the file <file:Documentation/fb/cirrusfb.rst>.
87 Say N unless you have such a graphics board or plan to get one
88 before you next recompile the kernel.
91 tristate "Permedia2 support"
92 depends on FB && ((AMIGA && BROKEN) || PCI)
93 select FB_CFB_FILLRECT
94 select FB_CFB_COPYAREA
95 select FB_CFB_IMAGEBLIT
96 select VIDEO_NOMODESET
98 This is the frame buffer device driver for cards based on
99 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
100 The driver was tested on the following cards:
101 Diamond FireGL 1000 PRO AGP
102 ELSA Gloria Synergy PCI
103 Appian Jeronimo PRO (both heads) PCI
104 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
105 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
106 ASK Graphic Blaster Exxtreme AGP
108 To compile this driver as a module, choose M here: the
109 module will be called pm2fb.
111 config FB_PM2_FIFO_DISCONNECT
112 bool "enable FIFO disconnect feature"
113 depends on FB_PM2 && PCI
115 Support the Permedia2 FIFO disconnect feature.
118 tristate "ARM PrimeCell PL110 support"
119 depends on ARM || ARM64 || COMPILE_TEST
120 depends on FB && ARM_AMBA && HAS_IOMEM
121 select FB_CFB_FILLRECT
122 select FB_CFB_COPYAREA
123 select FB_CFB_IMAGEBLIT
124 select FB_MODE_HELPERS if OF
125 select VIDEOMODE_HELPERS if OF
126 select BACKLIGHT_CLASS_DEVICE if OF
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.
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.
138 bool "Acorn VIDC support"
139 depends on (FB = y) && ARM && ARCH_ACORN
140 select FB_IOMEM_HELPERS
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
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
156 Say Y to enable the Framebuffer driver for the Cirrus Logic
160 bool "SA-1100 LCD support"
161 depends on (FB = y) && ARM && ARCH_SA1100
162 select FB_CFB_FILLRECT
163 select FB_CFB_COPYAREA
164 select FB_CFB_IMAGEBLIT
166 This is a framebuffer device for the SA-1100 LCD Controller.
167 See <http://www.linux-fbdev.org/> for information on framebuffer
170 If you plan to use the LCD display with your SA-1100 system, say
174 tristate "Freescale i.MX1/21/25/27 LCD support"
175 depends on FB && HAVE_CLK && HAS_IOMEM
176 depends on ARCH_MXC || COMPILE_TEST
177 select LCD_CLASS_DEVICE
178 select FB_IOMEM_HELPERS
179 select FB_MODE_HELPERS
180 select VIDEOMODE_HELPERS
183 tristate "CyberPro 2000/2010/5000 support"
184 depends on FB && PCI && (BROKEN || !SPARC64)
185 select FB_CFB_FILLRECT
186 select FB_CFB_COPYAREA
187 select FB_CFB_IMAGEBLIT
188 select VIDEO_NOMODESET
190 This enables support for the Integraphics CyberPro 20x0 and 5000
191 VGA chips used in the Rebel.com Netwinder and other machines.
192 Say Y if you have a NetWinder or a graphics card containing this
193 device, otherwise say N.
195 config FB_CYBER2000_DDC
196 bool "DDC for CyberPro support"
197 depends on FB_CYBER2000
201 Say Y here if you want DDC support for your CyberPro graphics
202 card. This is only I2C bus support, driver does not use EDID.
204 config FB_CYBER2000_I2C
205 bool "CyberPro 2000/2010/5000 I2C support"
206 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
207 depends on I2C=y || FB_CYBER2000=m
210 Enable support for the I2C video decoder interface on the
211 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
212 on the Netwinder machines for the SAA7111 video capture.
216 depends on (FB = y) && APOLLO
218 select FB_CFB_FILLRECT
219 select FB_CFB_IMAGEBLIT
223 depends on (FB = y) && Q40
225 select FB_CFB_FILLRECT
226 select FB_CFB_COPYAREA
227 select FB_CFB_IMAGEBLIT
230 tristate "Amiga native chipset support"
231 depends on FB && AMIGA
233 This is the frame buffer device driver for the builtin graphics
234 chipset found in Amigas.
236 To compile this driver as a module, choose M here: the
237 module will be called amifb.
240 bool "Amiga OCS chipset support"
243 This enables support for the original Agnus and Denise video chips,
244 found in the Amiga 1000 and most A500's and A2000's. If you intend
245 to run Linux on any of these systems, say Y; otherwise say N.
248 bool "Amiga ECS chipset support"
251 This enables support for the Enhanced Chip Set, found in later
252 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
253 you intend to run Linux on any of these systems, say Y; otherwise
257 bool "Amiga AGA chipset support"
260 This enables support for the Advanced Graphics Architecture (also
261 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
262 and CD32. If you intend to run Linux on any of these systems, say Y;
266 bool "Amiga FrameMaster II/Rainbow II support"
267 depends on (FB = y) && ZORRO
268 select FB_IOMEM_HELPERS
270 This is the frame buffer device driver for the Amiga FrameMaster
271 card from BSC (exhibited 1992 but not shipped as a CBM product).
274 tristate "Arc Monochrome LCD board support"
275 depends on FB && (X86 || COMPILE_TEST)
276 select FB_SYS_FILLRECT
277 select FB_SYS_COPYAREA
278 select FB_SYS_IMAGEBLIT
281 This enables support for the Arc Monochrome LCD board. The board
282 is based on the KS-108 lcd controller and is typically a matrix
283 of 2*n chips. This driver was tested with a 128x64 panel. This
284 driver supports it for use with x86 SBCs through a 16 bit GPIO
285 interface (8 bit data, 8 bit control). If you anticipate using
286 this driver, say Y or M; otherwise say N. You must specify the
287 GPIO IO address to be used for setting control and data.
290 bool "Atari native chipset support"
291 depends on (FB = y) && ATARI
292 select FB_CFB_FILLRECT
293 select FB_CFB_COPYAREA
294 select FB_CFB_IMAGEBLIT
296 This is the frame buffer device driver for the builtin graphics
297 chipset found in Ataris.
300 tristate "Open Firmware frame buffer device support"
301 depends on FB && PPC && (!PPC_PSERIES || PCI)
302 depends on !DRM_OFDRM
303 select APERTURE_HELPERS
304 select FB_IOMEM_HELPERS
307 Say Y if you want support with Open Firmware for your graphics
311 bool "Apple \"control\" display support"
312 depends on (FB = y) && ((PPC_PMAC && PPC32) || COMPILE_TEST)
313 select FB_CFB_FILLRECT
314 select FB_CFB_COPYAREA
315 select FB_CFB_IMAGEBLIT
318 This driver supports a frame buffer for the graphics adapter in the
319 Power Macintosh 7300 and others.
322 bool "Apple \"platinum\" display support"
323 depends on (FB = y) && PPC_PMAC && PPC32
324 select FB_IOMEM_HELPERS
327 This driver supports a frame buffer for the "platinum" graphics
328 adapter in some Power Macintoshes.
331 bool "Apple \"valkyrie\" display support"
332 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
333 select FB_CFB_FILLRECT
334 select FB_CFB_COPYAREA
335 select FB_CFB_IMAGEBLIT
338 This driver supports a frame buffer for the "valkyrie" graphics
339 adapter in some Power Macintoshes.
342 bool "Chips 65550 display support"
343 depends on (FB = y) && PPC32 && PCI
344 select FB_IOMEM_HELPERS
345 select VIDEO_NOMODESET
347 This is the frame buffer device driver for the Chips & Technologies
348 65550 graphics chip in PowerBooks.
351 bool "Asiliant (Chips) 69000 display support"
352 depends on (FB = y) && PCI
353 select FB_IOMEM_HELPERS
354 select VIDEO_NOMODESET
356 This is the frame buffer device driver for the Asiliant 69030 chipset
359 bool "IMS Twin Turbo display support"
360 depends on (FB = y) && PCI
361 select FB_CFB_IMAGEBLIT
362 select FB_MACMODES if PPC_PMAC
363 select VIDEO_NOMODESET
365 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
366 many Macintosh and compatible computers.
369 tristate "VGA 16-color graphics support"
370 depends on FB && (X86 || PPC)
371 select APERTURE_HELPERS
372 select FB_CFB_FILLRECT
373 select FB_CFB_COPYAREA
374 select FB_CFB_IMAGEBLIT
376 select FONT_8x16 if FRAMEBUFFER_CONSOLE
378 This is the frame buffer device driver for VGA 16 color graphic
379 cards. Say Y if you have such a card.
381 To compile this driver as a module, choose M here: the
382 module will be called vga16fb.
385 tristate "HP STI frame buffer device support"
386 depends on FB && PARISC
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
393 Enabling this option will implement the linux framebuffer device
394 using calls to the STI BIOS routines for initialisation.
396 If you enable this option, you will get a planar framebuffer device
397 /dev/fb which will work on the most common HP graphic cards of the
398 NGLE family, including the artist chips (in the 7xx and Bxxx series),
399 HCRX, HCRX24, CRX, CRX24 and VisEG series.
401 It is safe to enable this option, so you should probably say "Y".
404 bool "Generic Macintosh display support"
405 depends on (FB = y) && MAC
406 select FB_IOMEM_HELPERS
411 depends on (FB = y) && DIO
412 select FB_CFB_IMAGEBLIT
416 tristate "TGA/SFB+ framebuffer support"
419 depends on ALPHA || TC
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
424 select VIDEO_NOMODESET
426 This is the frame buffer device driver for generic TGA and SFB+
427 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
428 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
429 TURBOchannel cards, also known as PMAGD-A, -B and -C.
431 Due to hardware limitations ZLX-E2 and E3 cards are not supported
432 for DECstation 5000/200 systems. Additionally due to firmware
433 limitations these cards may cause troubles with booting DECstation
434 5000/240 and /260 systems, but are fully supported under Linux if
435 you manage to get it going. ;-)
437 Say Y if you have one of those.
440 tristate "Userspace VESA VGA graphics support"
441 depends on FB && CONNECTOR
443 select FB_CFB_FILLRECT
444 select FB_CFB_COPYAREA
445 select FB_CFB_IMAGEBLIT
446 select FB_MODE_HELPERS
448 This is the frame buffer driver for generic VBE 2.0 compliant
449 graphic cards. It can also take advantage of VBE 3.0 features,
450 such as refresh rate adjustment.
452 This driver generally provides more features than vesafb but
453 requires a userspace helper application called 'v86d'. See
454 <file:Documentation/fb/uvesafb.rst> for more information.
459 bool "VESA VGA graphics support"
460 depends on (FB = y) && X86
461 select APERTURE_HELPERS
462 select FB_CFB_FILLRECT
463 select FB_CFB_COPYAREA
464 select FB_CFB_IMAGEBLIT
467 This is the frame buffer device driver for generic VESA 2.0
468 compliant graphic cards. The older VESA 1.2 cards are not supported.
469 You will get a boot time penguin logo at no additional cost. Please
470 read <file:Documentation/fb/vesafb.rst>. If unsure, say Y.
473 bool "EFI-based Framebuffer Support"
474 depends on (FB = y) && !IA64 && EFI
475 select APERTURE_HELPERS
476 select DRM_PANEL_ORIENTATION_QUIRKS
477 select FB_IOMEM_HELPERS
480 This is the EFI frame buffer device driver. If the firmware on
481 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
482 using the EFI framebuffer as your console.
485 tristate "N411 Apollo/Hecuba devkit support"
486 depends on FB && X86 && MMU
489 This enables support for the Apollo display controller in its
490 Hecuba form using the n411 devkit.
493 tristate "Hercules mono graphics support"
496 Say Y here if you have a Hercules mono graphics card.
498 To compile this driver as a module, choose M here: the
499 module will be called hgafb.
501 As this card technology is at least 25 years old,
502 most people will answer N here.
505 bool "SGI Graphics Backend frame buffer support"
506 depends on (FB = y) && HAS_IOMEM
507 depends on SGI_IP32 || COMPILE_TEST
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
512 This is the frame buffer device driver for SGI Graphics Backend.
513 This chip is used in SGI O2 and Visual Workstation 320/540.
516 int "Video memory size in MB"
520 This is the amount of memory reserved for the framebuffer,
521 which can be any value between 1MB and 8MB.
524 bool "SBUS and UPA framebuffers"
525 depends on (FB = y) && SPARC
527 Say Y if you want support for SBUS or UPA based frame buffer device.
531 depends on (FB = y) && (SPARC && FB_SBUS)
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
536 This is the frame buffer device driver for the BWtwo frame buffer.
539 bool "CGthree support"
540 depends on (FB = y) && (SPARC && FB_SBUS)
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
545 This is the frame buffer device driver for the CGthree frame buffer.
548 bool "CGsix (GX,TurboGX) support"
549 depends on (FB = y) && (SPARC && FB_SBUS)
550 select FB_CFB_COPYAREA
551 select FB_CFB_IMAGEBLIT
553 This is the frame buffer device driver for the CGsix (GX, TurboGX)
557 bool "Creator/Creator3D/Elite3D support"
558 depends on FB_SBUS && SPARC64
559 select FB_CFB_COPYAREA
560 select FB_CFB_IMAGEBLIT
562 This is the frame buffer device driver for the Creator, Creator3D,
563 and Elite3D graphics boards.
566 bool "TCX (SS4/SS5 only) support"
568 select FB_CFB_FILLRECT
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
572 This is the frame buffer device driver for the TCX 24/8bit frame
576 bool "CGfourteen (SX) support"
578 select FB_CFB_FILLRECT
579 select FB_CFB_COPYAREA
580 select FB_CFB_IMAGEBLIT
582 This is the frame buffer device driver for the CGfourteen frame
583 buffer on Desktop SPARCsystems with the SX graphics option.
586 bool "P9100 (Sparcbook 3 only) support"
588 select FB_CFB_FILLRECT
589 select FB_CFB_COPYAREA
590 select FB_CFB_IMAGEBLIT
592 This is the frame buffer device driver for the P9100 card
593 supported on Sparcbook 3 machines.
596 bool "Leo (ZX) support"
598 select FB_CFB_FILLRECT
599 select FB_CFB_COPYAREA
600 select FB_CFB_IMAGEBLIT
602 This is the frame buffer device driver for the SBUS-based Sun ZX
603 (leo) frame buffer cards.
606 bool "Sun XVR-500 3DLABS Wildcat support"
607 depends on (FB = y) && PCI && SPARC64
608 select FB_CFB_FILLRECT
609 select FB_CFB_COPYAREA
610 select FB_CFB_IMAGEBLIT
611 select VIDEO_NOMODESET
613 This is the framebuffer device for the Sun XVR-500 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.
620 bool "Sun XVR-2500 3DLABS Wildcat support"
621 depends on (FB = y) && PCI && SPARC64
622 select FB_CFB_FILLRECT
623 select FB_CFB_COPYAREA
624 select FB_CFB_IMAGEBLIT
625 select VIDEO_NOMODESET
627 This is the framebuffer device for the Sun XVR-2500 and similar
628 graphics cards based upon the 3DLABS Wildcat chipset. The driver
629 only works on sparc64 systems where the system firmware has
630 mostly initialized the card already. It is treated as a
631 completely dumb framebuffer device.
634 bool "Sun XVR-1000 support"
635 depends on (FB = y) && SPARC64
636 select FB_CFB_FILLRECT
637 select FB_CFB_COPYAREA
638 select FB_CFB_IMAGEBLIT
640 This is the framebuffer device for the Sun XVR-1000 and similar
641 graphics cards. The driver only works on sparc64 systems where
642 the system firmware has mostly initialized the card already. It
643 is treated as a completely dumb framebuffer device.
646 tristate "NEC PowerVR 2 display support"
647 depends on FB && HAS_IOMEM
648 depends on SH_DREAMCAST || COMPILE_TEST
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
652 select VIDEO_NOMODESET
654 Say Y here if you have a PowerVR 2 card in your box. If you plan to
655 run linux on your Dreamcast, you will have to say Y here.
656 This driver may or may not work on other PowerVR 2 cards, but is
657 totally untested. Use at your own risk. If unsure, say N.
659 To compile this driver as a module, choose M here: the
660 module will be called pvr2fb.
662 You can pass several parameters to the driver at boot time or at
663 module load time. The parameters look like "video=pvr2:XXX", where
664 the meaning of XXX can be found at the end of the main source file
665 (<file:drivers/video/fbdev/pvr2fb.c>). Please see the file
666 <file:Documentation/fb/pvr2fb.rst>.
669 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
670 depends on FB && HAS_DMA
671 select FB_IOMEM_HELPERS
673 This enables support for the OpenCores VGA/LCD core.
675 The OpenCores VGA/LCD core is typically used together with
676 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
677 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
679 The source code and specification for the core is available at
680 <https://opencores.org/project,vga_lcd>
683 tristate "Epson S1D13XXX framebuffer support"
685 select FB_CFB_FILLRECT
686 select FB_CFB_COPYAREA
687 select FB_CFB_IMAGEBLIT
689 Support for S1D13XXX framebuffer device family (currently only
690 working with S1D13806). Product specs at
691 <https://vdc.epson.com/>
694 tristate "AT91 LCD Controller support"
695 depends on FB && OF && HAVE_CLK && HAS_IOMEM
696 depends on HAVE_FB_ATMEL || COMPILE_TEST
698 select FB_IOMEM_HELPERS
699 select FB_MODE_HELPERS
700 select VIDEOMODE_HELPERS
702 This enables support for the AT91 LCD Controller.
705 tristate "nVidia Framebuffer Support"
707 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
708 select FB_MODE_HELPERS
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
714 select VIDEO_NOMODESET
716 This driver supports graphics boards with the nVidia chips, TNT
717 and newer. For very old chipsets, such as the RIVA128, then use
719 Say Y if you have such a graphics board.
721 To compile this driver as a module, choose M here: the
722 module will be called nvidiafb.
725 bool "Enable DDC Support"
729 This enables I2C support for nVidia Chipsets. This is used
730 only for getting EDID information from the attached display
731 allowing for robust video mode handling and switching.
733 Because fbdev-2.6 requires that drivers must be able to
734 independently validate video mode parameters, you should say Y
737 config FB_NVIDIA_DEBUG
738 bool "Lots of debug output"
741 Say Y here if you want the nVidia driver to output all sorts
742 of debugging information to provide to the maintainer when
743 something goes wrong.
745 config FB_NVIDIA_BACKLIGHT
746 bool "Support for backlight control"
750 Say Y here if you want to control the backlight of your display.
753 tristate "nVidia Riva support"
755 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
756 select FB_MODE_HELPERS
757 select FB_CFB_FILLRECT
758 select FB_CFB_COPYAREA
759 select FB_CFB_IMAGEBLIT
762 select VIDEO_NOMODESET
764 This driver supports graphics boards with the nVidia Riva/Geforce
766 Say Y if you have such a graphics board.
768 To compile this driver as a module, choose M here: the
769 module will be called rivafb.
772 bool "Enable DDC Support"
776 This enables I2C support for nVidia Chipsets. This is used
777 only for getting EDID information from the attached display
778 allowing for robust video mode handling and switching.
780 Because fbdev-2.6 requires that drivers must be able to
781 independently validate video mode parameters, you should say Y
785 bool "Lots of debug output"
788 Say Y here if you want the Riva driver to output all sorts
789 of debugging information to provide to the maintainer when
790 something goes wrong.
792 config FB_RIVA_BACKLIGHT
793 bool "Support for backlight control"
797 Say Y here if you want to control the backlight of your display.
800 tristate "Intel740 support"
802 select FB_IOMEM_HELPERS
803 select FB_MODE_HELPERS
805 select VIDEO_NOMODESET
808 This driver supports graphics cards based on Intel740 chip.
811 tristate "Intel 810/815 support"
812 depends on FB && PCI && X86_32 && AGP_INTEL
813 select FB_MODE_HELPERS
814 select FB_CFB_FILLRECT
815 select FB_CFB_COPYAREA
816 select FB_CFB_IMAGEBLIT
818 select VIDEO_NOMODESET
820 This driver supports the on-board graphics built in to the Intel 810
821 and 815 chipsets. Say Y if you have and plan to use such a board.
823 To compile this driver as a module, choose M here: the
824 module will be called i810fb.
826 For more information, please read
827 <file:Documentation/fb/intel810.rst>
830 bool "use VESA Generalized Timing Formula"
833 If you say Y, then the VESA standard, Generalized Timing Formula
834 or GTF, will be used to calculate the required video timing values
835 per video mode. Since the GTF allows nondiscrete timings
836 (nondiscrete being a range of values as opposed to discrete being a
837 set of values), you'll be able to use any combination of horizontal
838 and vertical resolutions, and vertical refresh rates without having
839 to specify your own timing parameters. This is especially useful
840 to maximize the performance of an aging display, or if you just
841 have a display with nonstandard dimensions. A VESA compliant
842 monitor is recommended, but can still work with non-compliant ones.
843 If you need or want this, then select this option. The timings may
844 not be compliant with Intel's recommended values. Use at your own
847 If you say N, the driver will revert to discrete video timings
848 using a set recommended by Intel in their documentation.
853 bool "Enable DDC Support"
854 depends on FB_I810 && FB_I810_GTF
857 Add DDC/I2C support for i810fb. This will allow the driver to get
858 display information, especially for monitors with fickle timings.
863 tristate "Intel LE80578 (Vermilion) support"
864 depends on FB && PCI && X86
865 select FB_MODE_HELPERS
866 select FB_CFB_FILLRECT
867 select FB_CFB_COPYAREA
868 select FB_CFB_IMAGEBLIT
869 select VIDEO_NOMODESET
871 This driver supports the LE80578 (Vermilion Range) chipset
873 config FB_CARILLO_RANCH
874 tristate "Intel Carillo Ranch support"
875 depends on FB_LE80578 && FB && PCI && X86
877 This driver supports the LE80578 (Carillo Ranch) board
880 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
881 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
882 select FB_MODE_HELPERS
883 select FB_CFB_FILLRECT
884 select FB_CFB_COPYAREA
885 select FB_CFB_IMAGEBLIT
886 select BOOT_VESA_SUPPORT if FB_INTEL = y
887 select VIDEO_NOMODESET
890 This driver supports the on-board graphics built in to the Intel
891 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
892 Say Y if you have and plan to use such a board.
894 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
896 To compile this driver as a module, choose M here: the
897 module will be called intelfb.
899 For more information, please read <file:Documentation/fb/intelfb.rst>
901 config FB_INTEL_DEBUG
902 bool "Intel driver Debug Messages"
905 Say Y here if you want the Intel driver to output all sorts
906 of debugging information to provide to the maintainer when
907 something goes wrong.
910 bool "DDC/I2C for Intel framebuffer support"
915 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
918 tristate "Matrox acceleration"
920 select FB_CFB_FILLRECT
921 select FB_CFB_COPYAREA
922 select FB_CFB_IMAGEBLIT
923 select FB_TILEBLITTING
924 select FB_MACMODES if PPC_PMAC
925 select VIDEO_NOMODESET
927 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
928 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
929 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
930 Matrox G400, G450 or G550 card in your box.
932 To compile this driver as a module, choose M here: the
933 module will be called matroxfb.
935 You can pass several parameters to the driver at boot time or at
936 module load time. The parameters look like "video=matroxfb:XXX", and
937 are described in <file:Documentation/fb/matroxfb.rst>.
939 config FB_MATROX_MILLENIUM
940 bool "Millennium I/II support"
943 Say Y here if you have a Matrox Millennium or Matrox Millennium II
944 video card. If you select "Advanced lowlevel driver options" below,
945 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
946 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
947 also use font widths different from 8.
949 config FB_MATROX_MYSTIQUE
950 bool "Mystique support"
953 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
954 video card. If you select "Advanced lowlevel driver options" below,
955 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
956 packed pixel and 32 bpp packed pixel. You can also use font widths
960 bool "G100/G200/G400/G450/G550 support"
963 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
964 video card. If you select "Advanced lowlevel driver options", you
965 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
966 pixel and 32 bpp packed pixel. You can also use font widths
969 If you need support for G400 secondary head, you must say Y to
970 "Matrox I2C support" and "G400 second head support" right below.
971 G450/G550 secondary head and digital output are supported without
974 The driver starts in monitor mode. You must use the matroxset tool
975 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
976 swap primary and secondary head outputs, or to change output mode.
977 Secondary head driver always start in 640x480 resolution and you
978 must use fbset to change it.
980 Do not forget that second head supports only 16 and 32 bpp
981 packed pixels, so it is a good idea to compile them into the kernel
982 too. You can use only some font widths, as the driver uses generic
983 painting procedures (the secondary head does not use acceleration
986 G450/G550 hardware can display TV picture only from secondary CRTC,
987 and it performs no scaling, so picture must have 525 or 625 lines.
990 tristate "Matrox I2C support"
994 This drivers creates I2C buses which are needed for accessing the
995 DDC (I2C) bus present on all Matroxes, an I2C bus which
996 interconnects Matrox optional devices, like MGA-TVO on G200 and
997 G400, and the secondary head DDC bus, present on G400 only.
999 You can say Y or M here if you want to experiment with monitor
1000 detection code. You must say Y or M here if you want to use either
1001 second head of G400 or MGA-TVO on G200 or G400.
1003 If you compile it as module, it will create a module named
1006 config FB_MATROX_MAVEN
1007 tristate "G400 second head support"
1008 depends on FB_MATROX_G && FB_MATROX_I2C
1010 WARNING !!! This support does not work with G450 !!!
1012 Say Y or M here if you want to use a secondary head (meaning two
1013 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1014 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1015 secondary head output is blanked while you are in X. With XFree
1016 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1017 the fbdev driver on first head and the fbdev driver on second head.
1019 If you compile it as module, two modules are created,
1020 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1021 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1022 also load i2c-matroxfb to get it to run.
1024 The driver starts in monitor mode and you must use the matroxset
1026 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1027 PAL or NTSC or to swap primary and secondary head outputs.
1028 Secondary head driver also always start in 640x480 resolution, you
1029 must use fbset to change it.
1031 Also do not forget that second head supports only 16 and 32 bpp
1032 packed pixels, so it is a good idea to compile them into the kernel
1033 too. You can use only some font widths, as the driver uses generic
1034 painting procedures (the secondary head does not use acceleration
1038 tristate "ATI Radeon display support"
1039 depends on FB && PCI
1040 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1041 select FB_MODE_HELPERS
1042 select FB_CFB_FILLRECT
1043 select FB_CFB_COPYAREA
1044 select FB_CFB_IMAGEBLIT
1045 select FB_MACMODES if PPC
1046 select VIDEO_NOMODESET
1048 Choose this option if you want to use an ATI Radeon graphics card as
1049 a framebuffer device. There are both PCI and AGP versions. You
1050 don't need to choose this to run the Radeon in plain VGA mode.
1052 There is a product page at
1053 https://products.amd.com/en-us/GraphicCardResult.aspx
1055 config FB_RADEON_I2C
1056 bool "DDC/I2C for ATI Radeon support"
1057 depends on FB_RADEON
1061 Say Y here if you want DDC/I2C support for your Radeon board.
1063 config FB_RADEON_BACKLIGHT
1064 bool "Support for backlight control"
1065 depends on FB_RADEON
1068 Say Y here if you want to control the backlight of your display.
1070 config FB_RADEON_DEBUG
1071 bool "Lots of debug output from Radeon driver"
1072 depends on FB_RADEON
1074 Say Y here if you want the Radeon driver to output all sorts
1075 of debugging information to provide to the maintainer when
1076 something goes wrong.
1079 tristate "ATI Rage128 display support"
1080 depends on FB && PCI
1081 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1082 select FB_IOMEM_HELPERS
1083 select FB_MACMODES if PPC_PMAC
1084 select VIDEO_NOMODESET
1086 This driver supports graphics boards with the ATI Rage128 chips.
1087 Say Y if you have such a graphics board and read
1088 <file:Documentation/fb/aty128fb.rst>.
1090 To compile this driver as a module, choose M here: the
1091 module will be called aty128fb.
1093 config FB_ATY128_BACKLIGHT
1094 bool "Support for backlight control"
1095 depends on FB_ATY128
1098 Say Y here if you want to control the backlight of your display.
1101 tristate "ATI Mach64 display support" if PCI || ATARI
1102 depends on FB && !SPARC32
1103 select FB_CFB_FILLRECT
1104 select FB_CFB_COPYAREA
1105 select FB_CFB_IMAGEBLIT
1106 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1107 select FB_MACMODES if PPC
1108 select FB_ATY_CT if SPARC64 && PCI
1109 select VIDEO_NOMODESET
1111 This driver supports graphics boards with the ATI Mach64 chips.
1112 Say Y if you have such a graphics board.
1114 To compile this driver as a module, choose M here: the
1115 module will be called atyfb.
1118 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1119 depends on PCI && FB_ATY
1121 Say Y here to support use of ATI's 64-bit Rage boards (or other
1122 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1123 framebuffer device. The ATI product support page for these boards
1124 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1126 config FB_ATY_GENERIC_LCD
1127 bool "Mach64 generic LCD support"
1128 depends on FB_ATY_CT
1130 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1131 Rage XC, or Rage XL chipset.
1134 bool "Mach64 GX support" if PCI
1138 Say Y here to support use of the ATI Mach64 Graphics Expression
1139 board (or other boards based on the Mach64 GX chipset) as a
1140 framebuffer device. The ATI product support page for these boards
1142 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1144 config FB_ATY_BACKLIGHT
1145 bool "Support for backlight control"
1149 Say Y here if you want to control the backlight of your display.
1152 tristate "S3 Trio/Virge support"
1153 depends on FB && PCI
1154 select FB_CFB_FILLRECT
1155 select FB_CFB_COPYAREA
1156 select FB_CFB_IMAGEBLIT
1157 select FB_TILEBLITTING
1160 select VIDEO_NOMODESET
1161 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1163 Driver for graphics boards with S3 Trio / S3 Virge chip.
1166 bool "DDC for S3 support"
1171 Say Y here if you want DDC support for your S3 graphics card.
1174 tristate "S3 Savage support"
1175 depends on FB && PCI
1176 select FB_MODE_HELPERS
1177 select FB_CFB_FILLRECT
1178 select FB_CFB_COPYAREA
1179 select FB_CFB_IMAGEBLIT
1181 select VIDEO_NOMODESET
1183 This driver supports notebooks and computers with S3 Savage PCI/AGP
1186 Say Y if you have such a graphics card.
1188 To compile this driver as a module, choose M here; the module
1189 will be called savagefb.
1191 config FB_SAVAGE_I2C
1192 bool "Enable DDC2 Support"
1193 depends on FB_SAVAGE
1196 This enables I2C support for S3 Savage Chipsets. This is used
1197 only for getting EDID information from the attached display
1198 allowing for robust video mode handling and switching.
1200 Because fbdev-2.6 requires that drivers must be able to
1201 independently validate video mode parameters, you should say Y
1204 config FB_SAVAGE_ACCEL
1205 bool "Enable Console Acceleration"
1206 depends on FB_SAVAGE
1208 This option will compile in console acceleration support. If
1209 the resulting framebuffer console has bothersome glitches, then
1213 tristate "SiS/XGI display support"
1214 depends on FB && PCI
1215 select FB_CFB_FILLRECT
1216 select FB_CFB_COPYAREA
1217 select FB_CFB_IMAGEBLIT
1218 select BOOT_VESA_SUPPORT if FB_SIS = y
1219 select FB_SIS_300 if !FB_SIS_315
1220 select VIDEO_NOMODESET
1222 This is the frame buffer device driver for the SiS 300, 315, 330
1223 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1224 Specs available at <https://www.sis.com> and <http://www.xgitech.com>.
1226 To compile this driver as a module, choose M here; the module
1227 will be called sisfb.
1230 bool "SiS 300 series support"
1233 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1236 bool "SiS 315/330/340 series and XGI support"
1239 Say Y here to support use of the SiS 315, 330 and 340 series
1240 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1241 as XGI V3XT, V5, V8 and Z7.
1244 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1245 depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST)
1246 select FB_CFB_FILLRECT
1247 select FB_CFB_COPYAREA
1248 select FB_CFB_IMAGEBLIT
1250 select VIDEO_NOMODESET
1252 This is the frame buffer device driver for Graphics chips of VIA
1253 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1254 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1256 Say Y if you have a VIA UniChrome graphics board.
1258 To compile this driver as a module, choose M here: the
1259 module will be called viafb.
1263 config FB_VIA_DIRECT_PROCFS
1264 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1266 Allow direct hardware access to some output registers via procfs.
1267 This is dangerous but may provide the only chance to get the
1268 correct output device configuration.
1269 Its use is strongly discouraged.
1271 config FB_VIA_X_COMPATIBILITY
1272 bool "X server compatibility"
1274 This option reduces the functionality (power saving, ...) of the
1275 framebuffer to avoid negative impact on the OpenChrome X server.
1276 If you use any X server other than fbdev you should enable this
1277 otherwise it should be safe to disable it and allow using all
1283 tristate "NeoMagic display support"
1284 depends on FB && PCI
1285 select FB_MODE_HELPERS
1286 select FB_CFB_FILLRECT
1287 select FB_CFB_COPYAREA
1288 select FB_CFB_IMAGEBLIT
1290 select VIDEO_NOMODESET
1292 This driver supports notebooks with NeoMagic PCI chips.
1293 Say Y if you have such a graphics card.
1295 To compile this driver as a module, choose M here: the
1296 module will be called neofb.
1299 tristate "IMG Kyro support"
1300 depends on FB && PCI
1301 select FB_IOMEM_HELPERS
1302 select VIDEO_NOMODESET
1304 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1307 To compile this driver as a module, choose M here: the
1308 module will be called kyrofb.
1311 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1312 depends on FB && PCI
1313 select FB_CFB_IMAGEBLIT
1314 select FB_CFB_FILLRECT
1315 select FB_CFB_COPYAREA
1316 select FB_MODE_HELPERS
1317 select VIDEO_NOMODESET
1319 This driver supports graphics boards with the 3Dfx Banshee,
1320 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1321 such a graphics board.
1323 To compile this driver as a module, choose M here: the
1324 module will be called tdfxfb.
1326 config FB_3DFX_ACCEL
1327 bool "3Dfx Acceleration functions"
1330 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1331 device driver with acceleration functions.
1334 bool "Enable DDC/I2C support"
1339 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1342 tristate "3Dfx Voodoo Graphics (sst1) support"
1343 depends on FB && PCI
1344 depends on FB_DEVICE
1345 select FB_CFB_FILLRECT
1346 select FB_CFB_COPYAREA
1347 select FB_CFB_IMAGEBLIT
1348 select VIDEO_NOMODESET
1350 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1351 Voodoo2 (cvg) based graphics card.
1353 To compile this driver as a module, choose M here: the
1354 module will be called sstfb.
1356 WARNING: Do not use any application that uses the 3D engine
1357 (namely glide) while using this driver.
1358 Please read the <file:Documentation/fb/sstfb.rst> for supported
1359 options and other important info support.
1362 tristate "VIA VT8623 support"
1363 depends on FB && PCI
1364 select FB_CFB_FILLRECT
1365 select FB_CFB_COPYAREA
1366 select FB_CFB_IMAGEBLIT
1367 select FB_TILEBLITTING
1370 select VIDEO_NOMODESET
1371 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1373 Driver for CastleRock integrated graphics core in the
1374 VIA VT8623 [Apollo CLE266] chipset.
1377 tristate "Trident/CyberXXX/CyberBlade support"
1378 depends on FB && PCI
1379 select FB_CFB_FILLRECT
1380 select FB_CFB_COPYAREA
1381 select FB_CFB_IMAGEBLIT
1383 select FB_MODE_HELPERS
1384 select VIDEO_NOMODESET
1386 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1387 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1389 There are also integrated versions of these chips called CyberXXXX,
1390 CyberImage or CyberBlade. These chips are mostly found in laptops
1391 but also on some motherboards including early VIA EPIA motherboards.
1392 For more information, read <file:Documentation/fb/tridentfb.rst>
1394 Say Y if you have such a graphics board.
1396 To compile this driver as a module, choose M here: the
1397 module will be called tridentfb.
1400 tristate "ARK 2000PV support"
1401 depends on FB && PCI
1402 select FB_CFB_FILLRECT
1403 select FB_CFB_COPYAREA
1404 select FB_CFB_IMAGEBLIT
1405 select FB_TILEBLITTING
1408 select VIDEO_NOMODESET
1409 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1411 Driver for PCI graphics boards with ARK 2000PV chip
1412 and ICS 5342 RAMDAC.
1415 tristate "Permedia3 support"
1416 depends on FB && PCI
1417 select FB_CFB_FILLRECT
1418 select FB_CFB_COPYAREA
1419 select FB_CFB_IMAGEBLIT
1420 select VIDEO_NOMODESET
1422 This is the frame buffer device driver for the 3DLabs Permedia3
1423 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1424 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1425 and maybe other boards.
1428 tristate "Fujitsu carmine frame buffer support"
1429 depends on FB && PCI
1430 select FB_IOMEM_HELPERS
1431 select VIDEO_NOMODESET
1433 This is the frame buffer device driver for the Fujitsu Carmine chip.
1434 The driver provides two independent frame buffer devices.
1437 depends on FB_CARMINE
1438 prompt "DRAM timing"
1439 default FB_CARMINE_DRAM_EVAL
1441 config FB_CARMINE_DRAM_EVAL
1442 bool "Eval board timings"
1444 Use timings which work on the eval card.
1446 config CARMINE_DRAM_CUSTOM
1447 bool "Custom board timings"
1449 Use custom board timings.
1453 bool "Au1100 LCD Driver"
1454 depends on (FB = y) && MIPS_ALCHEMY
1455 select FB_CFB_FILLRECT
1456 select FB_CFB_COPYAREA
1457 select FB_CFB_IMAGEBLIT
1459 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1460 various panels and CRTs by passing in kernel cmd line option
1461 au1100fb:panel=<name>.
1464 bool "Au1200/Au1300 LCD Driver"
1465 depends on (FB = y) && MIPS_ALCHEMY
1466 select FB_SYS_FILLRECT
1467 select FB_SYS_COPYAREA
1468 select FB_SYS_IMAGEBLIT
1471 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1472 It can drive various panels and CRTs by passing in kernel cmd line
1473 option au1200fb:panel=<name>.
1476 bool "VIA VT8500 framebuffer support"
1477 depends on (FB = y) && ARM && ARCH_VT8500
1478 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1479 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1480 select FB_SYS_IMAGEBLIT
1481 select FB_MODE_HELPERS
1482 select VIDEOMODE_HELPERS
1484 This is the framebuffer driver for VIA VT8500 integrated LCD
1488 bool "Wondermedia WM8xxx-series frame buffer support"
1489 depends on (FB = y) && HAS_IOMEM && (ARCH_VT8500 || COMPILE_TEST)
1490 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1491 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1492 select FB_SYS_IMAGEBLIT
1493 select FB_MODE_HELPERS
1494 select VIDEOMODE_HELPERS
1496 This is the framebuffer driver for WonderMedia WM8xxx-series
1497 integrated LCD controller. This driver covers the WM8505, WM8650
1500 config FB_WMT_GE_ROPS
1501 bool "VT8500/WM8xxx accelerated raster ops support"
1502 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1504 This adds support for accelerated raster operations on the
1505 VIA VT8500 and Wondermedia 85xx series SoCs.
1507 source "drivers/video/fbdev/geode/Kconfig"
1510 tristate "HD64461 Frame Buffer support"
1511 depends on FB && HD64461
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1516 This is the frame buffer device driver for the Hitachi HD64461 LCD
1520 tristate "PMAG-AA TURBOchannel framebuffer support"
1522 select FB_IOMEM_HELPERS
1524 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1525 used mainly in the MIPS-based DECstation series.
1528 tristate "PMAG-BA TURBOchannel framebuffer support"
1530 select FB_IOMEM_HELPERS
1532 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1533 used mainly in the MIPS-based DECstation series.
1536 tristate "PMAGB-B TURBOchannel framebuffer support"
1538 select FB_IOMEM_HELPERS
1540 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1541 in the MIPS-based DECstation series. The card is currently only
1542 supported in 1280x1024x8 mode.
1545 bool "Maxine (Personal DECstation) onboard framebuffer support"
1546 depends on (FB = y) && MACH_DECSTATION
1547 select FB_IOMEM_HELPERS
1549 Support for the onboard framebuffer (1024x768x8) in the Personal
1550 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1554 bool "G364 frame buffer support"
1555 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1556 select FB_IOMEM_HELPERS
1558 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1559 Olivetti M700-10 systems.
1562 bool "Motorola 68328 native frame buffer support"
1563 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1564 select FB_CFB_FILLRECT
1565 select FB_CFB_COPYAREA
1566 select FB_CFB_IMAGEBLIT
1568 Say Y here if you want to support the built-in frame buffer of
1569 the Motorola 68328 CPU family.
1572 tristate "PXA168/910 LCD framebuffer support"
1573 depends on FB && HAVE_CLK && HAS_IOMEM
1574 depends on CPU_PXA168 || CPU_PXA910 || COMPILE_TEST
1575 select FB_IOMEM_HELPERS
1577 Frame buffer driver for the built-in LCD controller in the Marvell
1581 tristate "PXA LCD framebuffer support"
1582 depends on FB && ARCH_PXA
1583 select FB_IOMEM_HELPERS
1584 select VIDEOMODE_HELPERS if OF
1585 select FB_MODE_HELPERS if OF
1587 Frame buffer driver for the built-in LCD controller in the Intel
1590 This driver is also available as a module ( = code which can be
1591 inserted and removed from the running kernel whenever you want). The
1592 module will be called pxafb. If you want to compile it as a module,
1593 say M here and read <file:Documentation/kbuild/modules.rst>.
1597 config FB_PXA_OVERLAY
1598 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1599 depends on FB_PXA && (PXA27x || PXA3xx)
1601 config FB_PXA_SMARTPANEL
1602 bool "PXA Smartpanel LCD support"
1605 config FB_PXA_PARAMETERS
1606 bool "PXA LCD command line parameters"
1609 Enable the use of kernel command line or module parameters
1610 to configure the physical properties of the LCD panel when
1611 using the PXA LCD driver.
1613 This option allows you to override the panel parameters
1614 supplied by the platform in order to support multiple
1615 different models of flatpanel. If you will only be using a
1616 single model of flatpanel then you can safely leave this
1619 <file:Documentation/fb/pxafb.rst> describes the available parameters.
1622 tristate "PXA3xx 2D graphics accelerator driver"
1625 Kernelspace driver for the 2D graphics controller unit (GCU)
1626 found on PXA3xx processors. There is a counterpart driver in the
1627 DirectFB suite, see http://www.directfb.org/
1629 If you compile this as a module, it will be called pxa3xx_gcu.
1632 tristate "Freescale DIU framebuffer support"
1633 depends on FB && FSL_SOC
1634 select FB_IOMEM_HELPERS
1635 select FB_MODE_HELPERS
1636 select PPC_LIB_RHEAP
1638 Framebuffer driver for the Freescale SoC DIU
1640 config FB_SH_MOBILE_LCDC
1641 tristate "SuperH Mobile LCDC framebuffer support"
1642 depends on FB && HAVE_CLK && HAS_IOMEM
1643 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
1644 depends on FB_DEVICE
1645 select FB_SYS_FILLRECT
1646 select FB_SYS_COPYAREA
1647 select FB_SYS_IMAGEBLIT
1649 select FB_DEFERRED_IO
1652 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1655 tristate "Samsung S3C framebuffer support"
1656 depends on FB && HAVE_CLK && HAS_IOMEM
1657 depends on ARCH_S3C64XX || COMPILE_TEST
1658 select FB_CFB_FILLRECT
1659 select FB_CFB_COPYAREA
1660 select FB_CFB_IMAGEBLIT
1662 Frame buffer driver for the built-in FB controller in the Samsung
1663 SoC line such as the S3C6400 and S3C6410.
1665 These chips all have the same basic framebuffer design with the
1666 actual capabilities depending on the chip. The S3C6400
1667 and S3C6410 support 4 hardware windows.
1669 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1671 config FB_S3C_DEBUG_REGWRITE
1672 bool "Debug register writes"
1675 Show all register writes via pr_debug()
1678 tristate "Silicon Motion SM501 framebuffer support"
1679 depends on FB && MFD_SM501
1680 select FB_CFB_FILLRECT
1681 select FB_CFB_COPYAREA
1682 select FB_CFB_IMAGEBLIT
1684 Frame buffer driver for the CRT and LCD controllers in the Silicon
1687 This driver is also available as a module ( = code which can be
1688 inserted and removed from the running kernel whenever you want). The
1689 module will be called sm501fb. If you want to compile it as a module,
1690 say M here and read <file:Documentation/kbuild/modules.rst>.
1695 tristate "SMSC UFX6000/7000 USB Framebuffer support"
1696 depends on FB && USB
1697 select FB_MODE_HELPERS
1698 select FB_SYS_FILLRECT
1699 select FB_SYS_COPYAREA
1700 select FB_SYS_IMAGEBLIT
1702 select FB_DEFERRED_IO
1704 This is a kernel framebuffer driver for SMSC UFX USB devices.
1705 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1706 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1708 To compile as a module, choose M here: the module name is smscufx.
1711 tristate "Displaylink USB Framebuffer support"
1712 depends on FB && USB
1713 depends on FB_DEVICE
1714 select FB_MODE_HELPERS
1715 select FB_SYS_FILLRECT
1716 select FB_SYS_COPYAREA
1717 select FB_SYS_IMAGEBLIT
1719 select FB_DEFERRED_IO
1721 This is a kernel framebuffer driver for DisplayLink USB devices.
1722 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1723 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1724 To compile as a module, choose M here: the module name is udlfb.
1726 config FB_IBM_GXT4500
1727 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
1729 select FB_IOMEM_HELPERS
1730 select VIDEO_NOMODESET
1732 Say Y here to enable support for the IBM GXT4000P/6000P and
1733 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
1734 found on some IBM System P (pSeries) machines. This driver
1735 doesn't use Geometry Engine GT1000. This driver also supports
1736 AGP Fire GL2/3/4 cards on x86.
1739 tristate "PS3 GPU framebuffer driver"
1740 depends on FB && PS3_PS3AV
1741 select FB_SYS_FILLRECT
1742 select FB_SYS_COPYAREA
1743 select FB_SYS_IMAGEBLIT
1746 Include support for the virtual frame buffer in the PS3 platform.
1748 config FB_PS3_DEFAULT_SIZE_M
1749 int "PS3 default frame buffer size (in MiB)"
1753 This is the default size (in MiB) of the virtual frame buffer in
1755 The default value can be overridden on the kernel command line
1756 using the "ps3fb" option (e.g. "ps3fb=9M");
1759 tristate "Xilinx frame buffer support"
1760 depends on FB && (MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
1761 select FB_CFB_FILLRECT
1762 select FB_CFB_COPYAREA
1763 select FB_CFB_IMAGEBLIT
1765 Include support for the Xilinx ML300/ML403 reference design
1766 framebuffer. ML300 carries a 640*480 LCD display on the board,
1767 ML403 uses a standard DB15 VGA connector.
1770 tristate "Goldfish Framebuffer"
1772 depends on GOLDFISH || COMPILE_TEST
1773 select FB_IOMEM_HELPERS
1775 Framebuffer driver for Goldfish Virtual Platform
1778 tristate "Cobalt server LCD frame buffer support"
1779 depends on FB && MIPS_COBALT
1782 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
1783 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
1784 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
1785 select FB_CFB_FILLRECT
1786 select FB_CFB_COPYAREA
1787 select FB_CFB_IMAGEBLIT
1789 Support for the SH7760/SH7763/SH7720/SH7721 integrated
1790 (D)STN/TFT LCD Controller.
1791 Supports display resolutions up to 1024x1024 pixel, grayscale and
1792 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
1793 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
1794 panels <= 320 pixel horizontal resolution.
1797 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
1798 depends on FB && HAVE_CLK && HAS_IOMEM
1799 depends on ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST
1800 select FB_CFB_REV_PIXELS_IN_BYTE
1801 select FB_IOMEM_HELPERS
1802 select FB_MODE_HELPERS
1803 select VIDEOMODE_HELPERS
1805 This is the frame buffer device driver for the TI LCD controller
1806 found on DA8xx/OMAP-L1xx/AM335x SoCs.
1810 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1812 select FB_SYS_FILLRECT
1813 select FB_SYS_COPYAREA
1814 select FB_SYS_IMAGEBLIT
1817 This is a `virtual' frame buffer device. It operates on a chunk of
1818 unswappable kernel memory instead of on the memory of a graphics
1819 board. This means you cannot see any output sent to this frame
1820 buffer device, while it does consume precious memory. The main use
1821 of this frame buffer device is testing and debugging the frame
1822 buffer subsystem. Do NOT enable it for normal systems! To protect
1823 the innocent, it has to be enabled explicitly at boot time using the
1824 kernel option `video=vfb:'.
1826 To compile this driver as a module, choose M here: the
1827 module will be called vfb. In order to load it, you must use
1828 the vfb_enable=1 option.
1832 config XEN_FBDEV_FRONTEND
1833 tristate "Xen virtual frame buffer support"
1834 depends on FB && XEN
1835 select FB_SYSMEM_HELPERS_DEFERRED
1836 select XEN_XENBUS_FRONTEND
1839 This driver implements the front-end of the Xen virtual
1840 frame buffer driver. It communicates with a back-end
1844 tristate "E-Ink Metronome/8track controller support"
1846 select FB_SYSMEM_HELPERS_DEFERRED
1848 This driver implements support for the E-Ink Metronome
1849 controller. The pre-release name for this device was 8track
1850 and could also have been called by some vendors as PVI-nnnn.
1853 tristate "Fujitsu MB862xx GDC support"
1855 depends on PCI || (OF && PPC)
1856 select FB_IOMEM_HELPERS
1857 select VIDEO_NOMODESET
1859 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
1862 prompt "GDC variant"
1863 depends on FB_MB862XX
1865 config FB_MB862XX_PCI_GDC
1866 bool "Carmine/Coral-P(A) GDC"
1869 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
1870 PCI graphics controller devices.
1872 config FB_MB862XX_LIME
1874 depends on OF && PPC
1875 select FB_FOREIGN_ENDIAN
1876 select FB_LITTLE_ENDIAN
1878 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
1882 config FB_MB862XX_I2C
1883 bool "Support I2C bus on MB862XX GDC"
1884 depends on FB_MB862XX && I2C
1885 depends on FB_MB862XX=m || I2C=y
1888 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
1889 driver to support accessing I2C devices on controller's I2C bus.
1890 These are usually some video decoder chips.
1893 tristate "EP93XX frame buffer support"
1894 depends on FB && ARCH_EP93XX
1895 select FB_CFB_FILLRECT
1896 select FB_CFB_COPYAREA
1897 select FB_CFB_IMAGEBLIT
1899 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
1900 This driver is also available as a module. The module will be called
1903 config FB_PRE_INIT_FB
1904 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
1905 depends on FB && FB_MB862XX_LIME
1907 Select this option if display contents should be inherited as set by
1911 tristate "MX3 Framebuffer support"
1912 depends on FB && MX3_IPU
1913 select BACKLIGHT_CLASS_DEVICE
1914 select FB_IOMEM_HELPERS
1917 This is a framebuffer device for the i.MX31 LCD Controller. So
1918 far only synchronous displays are supported. If you plan to use
1919 an LCD display with your i.MX31 system, say Y here.
1921 config FB_BROADSHEET
1922 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
1923 depends on FB && (ARCH_PXA || COMPILE_TEST)
1924 select FB_SYSMEM_HELPERS_DEFERRED
1926 This driver implements support for the E-Ink Broadsheet
1927 controller. The release name for this device was Epson S1D13521
1928 and could also have been called by other names when coupled with
1932 tristate "Microsoft Hyper-V Synthetic Video support"
1933 depends on FB && HYPERV
1934 select FB_CFB_FILLRECT
1935 select FB_CFB_COPYAREA
1936 select FB_CFB_IMAGEBLIT
1937 select FB_DEFERRED_IO
1938 select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA
1939 select VIDEO_NOMODESET
1941 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
1944 tristate "Simple framebuffer support"
1946 depends on !DRM_SIMPLEDRM
1947 select APERTURE_HELPERS
1948 select FB_CFB_FILLRECT
1949 select FB_CFB_COPYAREA
1950 select FB_CFB_IMAGEBLIT
1952 Say Y if you want support for a simple frame-buffer.
1954 This driver assumes that the display hardware has been initialized
1955 before the kernel boots, and the kernel will simply render to the
1956 pre-allocated frame buffer surface.
1958 Configuration re: surface address, size, and format must be provided
1959 through device tree, or plain old platform data.
1962 tristate "Solomon SSD1307 framebuffer support"
1963 depends on FB && I2C
1964 depends on GPIOLIB || COMPILE_TEST
1966 select FB_SYSMEM_HELPERS_DEFERRED
1968 This driver implements support for the Solomon SSD1307
1969 OLED controller over I2C.
1972 tristate "Silicon Motion SM712 framebuffer support"
1973 depends on FB && PCI
1974 select FB_CFB_FILLRECT
1975 select FB_CFB_COPYAREA
1976 select FB_CFB_IMAGEBLIT
1977 select VIDEO_NOMODESET
1979 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
1982 This driver is also available as a module. The module will be
1983 called sm712fb. If you want to compile it as a module, say M
1984 here and read <file:Documentation/kbuild/modules.rst>.
1986 source "drivers/video/fbdev/omap/Kconfig"
1987 source "drivers/video/fbdev/omap2/Kconfig"
1988 source "drivers/video/fbdev/mmp/Kconfig"
1990 source "drivers/video/fbdev/core/Kconfig"