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
78 select VIDEO_NOMODESET
80 This enables support for Cirrus Logic GD542x/543x based boards on
81 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
83 If you have a PCI-based system, this enables support for these
84 chips: GD-543x, GD-544x, GD-5480.
86 Please read the file <file:Documentation/fb/cirrusfb.rst>.
88 Say N unless you have such a graphics board or plan to get one
89 before you next recompile the kernel.
92 tristate "Permedia2 support"
93 depends on FB && ((AMIGA && BROKEN) || PCI)
94 select FB_CFB_FILLRECT
95 select FB_CFB_COPYAREA
96 select FB_CFB_IMAGEBLIT
97 select VIDEO_NOMODESET
99 This is the frame buffer device driver for cards based on
100 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
101 The driver was tested on the following cards:
102 Diamond FireGL 1000 PRO AGP
103 ELSA Gloria Synergy PCI
104 Appian Jeronimo PRO (both heads) PCI
105 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
106 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
107 ASK Graphic Blaster Exxtreme AGP
109 To compile this driver as a module, choose M here: the
110 module will be called pm2fb.
112 config FB_PM2_FIFO_DISCONNECT
113 bool "enable FIFO disconnect feature"
114 depends on FB_PM2 && PCI
116 Support the Permedia2 FIFO disconnect feature.
119 tristate "ARM PrimeCell PL110 support"
120 depends on ARM || ARM64 || COMPILE_TEST
121 depends on FB && ARM_AMBA && HAS_IOMEM
122 select FB_IOMEM_HELPERS
123 select FB_MODE_HELPERS if OF
124 select VIDEOMODE_HELPERS if OF
125 select BACKLIGHT_CLASS_DEVICE if OF
127 This framebuffer device driver is for the ARM PrimeCell PL110
128 Colour LCD controller. ARM PrimeCells provide the building
129 blocks for System on a Chip devices.
131 If you want to compile this as a module (=code which can be
132 inserted into and removed from the running kernel), say M
133 here and read <file:Documentation/kbuild/modules.rst>. The module
134 will be called amba-clcd.
137 bool "Acorn VIDC support"
138 depends on (FB = y) && ARM && ARCH_ACORN
139 select FB_IOMEM_HELPERS
141 This is the frame buffer device driver for the Acorn VIDC graphics
142 hardware found in Acorn RISC PCs and other ARM-based machines. If
146 tristate "CLPS711X LCD support"
147 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
148 select FB_MODE_HELPERS
149 select FB_SYS_FILLRECT
150 select FB_SYS_COPYAREA
151 select FB_SYS_IMAGEBLIT
152 select LCD_CLASS_DEVICE
153 select VIDEOMODE_HELPERS
155 Say Y to enable the Framebuffer driver for the Cirrus Logic
159 bool "SA-1100 LCD support"
160 depends on (FB = y) && ARM && ARCH_SA1100
161 select FB_CFB_FILLRECT
162 select FB_CFB_COPYAREA
163 select FB_CFB_IMAGEBLIT
165 This is a framebuffer device for the SA-1100 LCD Controller.
166 See <http://www.linux-fbdev.org/> for information on framebuffer
169 If you plan to use the LCD display with your SA-1100 system, say
173 tristate "Freescale i.MX1/21/25/27 LCD support"
174 depends on FB && HAVE_CLK && HAS_IOMEM
175 depends on ARCH_MXC || COMPILE_TEST
176 select LCD_CLASS_DEVICE
177 select FB_IOMEM_HELPERS
178 select FB_MODE_HELPERS
179 select VIDEOMODE_HELPERS
182 tristate "CyberPro 2000/2010/5000 support"
183 depends on FB && PCI && (BROKEN || !SPARC64)
184 select FB_CFB_FILLRECT
185 select FB_CFB_COPYAREA
186 select FB_CFB_IMAGEBLIT
187 select VIDEO_NOMODESET
189 This enables support for the Integraphics CyberPro 20x0 and 5000
190 VGA chips used in the Rebel.com Netwinder and other machines.
191 Say Y if you have a NetWinder or a graphics card containing this
192 device, otherwise say N.
194 config FB_CYBER2000_DDC
195 bool "DDC for CyberPro support"
196 depends on FB_CYBER2000
200 Say Y here if you want DDC support for your CyberPro graphics
201 card. This is only I2C bus support, driver does not use EDID.
203 config FB_CYBER2000_I2C
204 bool "CyberPro 2000/2010/5000 I2C support"
205 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
206 depends on I2C=y || FB_CYBER2000=m
209 Enable support for the I2C video decoder interface on the
210 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
211 on the Netwinder machines for the SAA7111 video capture.
215 depends on (FB = y) && APOLLO
217 select FB_CFB_FILLRECT
218 select FB_CFB_IMAGEBLIT
222 depends on (FB = y) && Q40
224 select FB_IOMEM_HELPERS
227 tristate "Amiga native chipset support"
228 depends on FB && AMIGA
231 This is the frame buffer device driver for the builtin graphics
232 chipset found in Amigas.
234 To compile this driver as a module, choose M here: the
235 module will be called amifb.
238 bool "Amiga OCS chipset support"
241 This enables support for the original Agnus and Denise video chips,
242 found in the Amiga 1000 and most A500's and A2000's. If you intend
243 to run Linux on any of these systems, say Y; otherwise say N.
246 bool "Amiga ECS chipset support"
249 This enables support for the Enhanced Chip Set, found in later
250 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
251 you intend to run Linux on any of these systems, say Y; otherwise
255 bool "Amiga AGA chipset support"
258 This enables support for the Advanced Graphics Architecture (also
259 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
260 and CD32. If you intend to run Linux on any of these systems, say Y;
264 bool "Amiga FrameMaster II/Rainbow II support"
265 depends on (FB = y) && ZORRO
266 select FB_IOMEM_HELPERS
268 This is the frame buffer device driver for the Amiga FrameMaster
269 card from BSC (exhibited 1992 but not shipped as a CBM product).
272 tristate "Arc Monochrome LCD board support"
273 depends on FB && (X86 || COMPILE_TEST)
274 select FB_SYS_FILLRECT
275 select FB_SYS_COPYAREA
276 select FB_SYS_IMAGEBLIT
279 This enables support for the Arc Monochrome LCD board. The board
280 is based on the KS-108 lcd controller and is typically a matrix
281 of 2*n chips. This driver was tested with a 128x64 panel. This
282 driver supports it for use with x86 SBCs through a 16 bit GPIO
283 interface (8 bit data, 8 bit control). If you anticipate using
284 this driver, say Y or M; otherwise say N. You must specify the
285 GPIO IO address to be used for setting control and data.
288 bool "Atari native chipset support"
289 depends on (FB = y) && ATARI
290 select FB_CFB_FILLRECT
291 select FB_CFB_COPYAREA
292 select FB_CFB_IMAGEBLIT
295 This is the frame buffer device driver for the builtin graphics
296 chipset found in Ataris.
299 tristate "Open Firmware frame buffer device support"
300 depends on FB && PPC && (!PPC_PSERIES || PCI)
301 depends on !DRM_OFDRM
302 select APERTURE_HELPERS
303 select FB_IOMEM_HELPERS
306 Say Y if you want support with Open Firmware for your graphics
310 bool "Apple \"control\" display support"
311 depends on (FB = y) && ((PPC_PMAC && PPC32) || COMPILE_TEST)
312 select FB_IOMEM_HELPERS
315 This driver supports a frame buffer for the graphics adapter in the
316 Power Macintosh 7300 and others.
319 bool "Apple \"platinum\" display support"
320 depends on (FB = y) && PPC_PMAC && PPC32
321 select FB_IOMEM_HELPERS
324 This driver supports a frame buffer for the "platinum" graphics
325 adapter in some Power Macintoshes.
328 bool "Apple \"valkyrie\" display support"
329 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
330 select FB_IOMEM_HELPERS
333 This driver supports a frame buffer for the "valkyrie" graphics
334 adapter in some Power Macintoshes.
337 bool "Chips 65550 display support"
338 depends on (FB = y) && PPC32 && PCI
339 select FB_IOMEM_HELPERS
340 select VIDEO_NOMODESET
342 This is the frame buffer device driver for the Chips & Technologies
343 65550 graphics chip in PowerBooks.
346 bool "Asiliant (Chips) 69000 display support"
347 depends on (FB = y) && PCI
348 select FB_IOMEM_HELPERS
349 select VIDEO_NOMODESET
351 This is the frame buffer device driver for the Asiliant 69030 chipset
354 bool "IMS Twin Turbo display support"
355 depends on (FB = y) && PCI
356 select FB_CFB_IMAGEBLIT
357 select FB_MACMODES if PPC_PMAC
358 select VIDEO_NOMODESET
360 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
361 many Macintosh and compatible computers.
364 tristate "VGA 16-color graphics support"
365 depends on FB && (X86 || PPC)
366 select APERTURE_HELPERS
367 select FB_CFB_FILLRECT
368 select FB_CFB_COPYAREA
369 select FB_CFB_IMAGEBLIT
371 select FONT_8x16 if FRAMEBUFFER_CONSOLE
373 This is the frame buffer device driver for VGA 16 color graphic
374 cards. Say Y if you have such a card.
376 To compile this driver as a module, choose M here: the
377 module will be called vga16fb.
380 tristate "HP STI frame buffer device support"
381 depends on FB && PARISC
382 select FB_CFB_FILLRECT
383 select FB_CFB_COPYAREA
384 select FB_CFB_IMAGEBLIT
388 Enabling this option will implement the linux framebuffer device
389 using calls to the STI BIOS routines for initialisation.
391 If you enable this option, you will get a planar framebuffer device
392 /dev/fb which will work on the most common HP graphic cards of the
393 NGLE family, including the artist chips (in the 7xx and Bxxx series),
394 HCRX, HCRX24, CRX, CRX24 and VisEG series.
396 It is safe to enable this option, so you should probably say "Y".
399 bool "Generic Macintosh display support"
400 depends on (FB = y) && MAC
401 select FB_IOMEM_HELPERS
406 depends on (FB = y) && DIO
407 select FB_CFB_IMAGEBLIT
411 tristate "TGA/SFB+ framebuffer support"
414 depends on ALPHA || TC
415 select FB_CFB_FILLRECT
416 select FB_CFB_COPYAREA
417 select FB_CFB_IMAGEBLIT
419 select VIDEO_NOMODESET
421 This is the frame buffer device driver for generic TGA and SFB+
422 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
423 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
424 TURBOchannel cards, also known as PMAGD-A, -B and -C.
426 Due to hardware limitations ZLX-E2 and E3 cards are not supported
427 for DECstation 5000/200 systems. Additionally due to firmware
428 limitations these cards may cause troubles with booting DECstation
429 5000/240 and /260 systems, but are fully supported under Linux if
430 you manage to get it going. ;-)
432 Say Y if you have one of those.
435 tristate "Userspace VESA VGA graphics support"
436 depends on FB && CONNECTOR
438 select FB_IOMEM_HELPERS
439 select FB_MODE_HELPERS
441 This is the frame buffer driver for generic VBE 2.0 compliant
442 graphic cards. It can also take advantage of VBE 3.0 features,
443 such as refresh rate adjustment.
445 This driver generally provides more features than vesafb but
446 requires a userspace helper application called 'v86d'. See
447 <file:Documentation/fb/uvesafb.rst> for more information.
452 bool "VESA VGA graphics support"
453 depends on (FB = y) && X86
454 select APERTURE_HELPERS
455 select FB_IOMEM_HELPERS
458 This is the frame buffer device driver for generic VESA 2.0
459 compliant graphic cards. The older VESA 1.2 cards are not supported.
460 You will get a boot time penguin logo at no additional cost. Please
461 read <file:Documentation/fb/vesafb.rst>. If unsure, say Y.
464 bool "EFI-based Framebuffer Support"
465 depends on (FB = y) && !IA64 && EFI
466 select APERTURE_HELPERS
467 select DRM_PANEL_ORIENTATION_QUIRKS
468 select FB_IOMEM_HELPERS
471 This is the EFI frame buffer device driver. If the firmware on
472 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
473 using the EFI framebuffer as your console.
476 tristate "N411 Apollo/Hecuba devkit support"
477 depends on FB && X86 && MMU
480 This enables support for the Apollo display controller in its
481 Hecuba form using the n411 devkit.
484 tristate "Hercules mono graphics support"
487 Say Y here if you have a Hercules mono graphics card.
489 To compile this driver as a module, choose M here: the
490 module will be called hgafb.
492 As this card technology is at least 25 years old,
493 most people will answer N here.
496 bool "SGI Graphics Backend frame buffer support"
497 depends on (FB = y) && HAS_IOMEM
498 depends on SGI_IP32 || COMPILE_TEST
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
503 This is the frame buffer device driver for SGI Graphics Backend.
504 This chip is used in SGI O2 and Visual Workstation 320/540.
507 int "Video memory size in MB"
511 This is the amount of memory reserved for the framebuffer,
512 which can be any value between 1MB and 8MB.
515 bool "SBUS and UPA framebuffers"
516 depends on (FB = y) && SPARC
518 Say Y if you want support for SBUS or UPA based frame buffer device.
520 config FB_SBUS_HELPERS
522 select FB_CFB_COPYAREA
523 select FB_CFB_FILLRECT
524 select FB_CFB_IMAGEBLIT
528 depends on (FB = y) && (SPARC && FB_SBUS)
529 select FB_SBUS_HELPERS
531 This is the frame buffer device driver for the BWtwo frame buffer.
534 bool "CGthree support"
535 depends on (FB = y) && (SPARC && FB_SBUS)
536 select FB_SBUS_HELPERS
538 This is the frame buffer device driver for the CGthree frame buffer.
541 bool "CGsix (GX,TurboGX) support"
542 depends on (FB = y) && (SPARC && FB_SBUS)
543 select FB_CFB_COPYAREA
544 select FB_CFB_IMAGEBLIT
546 This is the frame buffer device driver for the CGsix (GX, TurboGX)
550 bool "Creator/Creator3D/Elite3D support"
551 depends on FB_SBUS && SPARC64
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
555 This is the frame buffer device driver for the Creator, Creator3D,
556 and Elite3D graphics boards.
559 bool "TCX (SS4/SS5 only) support"
561 select FB_SBUS_HELPERS
563 This is the frame buffer device driver for the TCX 24/8bit frame
567 bool "CGfourteen (SX) support"
569 select FB_SBUS_HELPERS
571 This is the frame buffer device driver for the CGfourteen frame
572 buffer on Desktop SPARCsystems with the SX graphics option.
575 bool "P9100 (Sparcbook 3 only) support"
577 select FB_SBUS_HELPERS
579 This is the frame buffer device driver for the P9100 card
580 supported on Sparcbook 3 machines.
583 bool "Leo (ZX) support"
585 select FB_SBUS_HELPERS
587 This is the frame buffer device driver for the SBUS-based Sun ZX
588 (leo) frame buffer cards.
591 bool "Sun XVR-500 3DLABS Wildcat support"
592 depends on (FB = y) && PCI && SPARC64
593 select FB_CFB_FILLRECT
594 select FB_CFB_COPYAREA
595 select FB_CFB_IMAGEBLIT
596 select VIDEO_NOMODESET
598 This is the framebuffer device for the Sun XVR-500 and similar
599 graphics cards based upon the 3DLABS Wildcat chipset. The driver
600 only works on sparc64 systems where the system firmware has
601 mostly initialized the card already. It is treated as a
602 completely dumb framebuffer device.
605 bool "Sun XVR-2500 3DLABS Wildcat support"
606 depends on (FB = y) && PCI && SPARC64
607 select FB_IOMEM_HELPERS
608 select VIDEO_NOMODESET
610 This is the framebuffer device for the Sun XVR-2500 and similar
611 graphics cards based upon the 3DLABS Wildcat chipset. The driver
612 only works on sparc64 systems where the system firmware has
613 mostly initialized the card already. It is treated as a
614 completely dumb framebuffer device.
617 bool "Sun XVR-1000 support"
618 depends on (FB = y) && SPARC64
619 select FB_IOMEM_HELPERS
621 This is the framebuffer device for the Sun XVR-1000 and similar
622 graphics cards. The driver only works on sparc64 systems where
623 the system firmware has mostly initialized the card already. It
624 is treated as a completely dumb framebuffer device.
627 tristate "NEC PowerVR 2 display support"
628 depends on FB && HAS_IOMEM
629 depends on SH_DREAMCAST || COMPILE_TEST
630 select FB_CFB_FILLRECT
631 select FB_CFB_COPYAREA
632 select FB_CFB_IMAGEBLIT
633 select VIDEO_NOMODESET
635 Say Y here if you have a PowerVR 2 card in your box. If you plan to
636 run linux on your Dreamcast, you will have to say Y here.
637 This driver may or may not work on other PowerVR 2 cards, but is
638 totally untested. Use at your own risk. If unsure, say N.
640 To compile this driver as a module, choose M here: the
641 module will be called pvr2fb.
643 You can pass several parameters to the driver at boot time or at
644 module load time. The parameters look like "video=pvr2:XXX", where
645 the meaning of XXX can be found at the end of the main source file
646 (<file:drivers/video/fbdev/pvr2fb.c>). Please see the file
647 <file:Documentation/fb/pvr2fb.rst>.
650 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
651 depends on FB && HAS_DMA
652 select FB_IOMEM_HELPERS
654 This enables support for the OpenCores VGA/LCD core.
656 The OpenCores VGA/LCD core is typically used together with
657 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
658 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
660 The source code and specification for the core is available at
661 <https://opencores.org/project,vga_lcd>
664 tristate "Epson S1D13XXX framebuffer support"
666 select FB_CFB_FILLRECT
667 select FB_CFB_COPYAREA
668 select FB_CFB_IMAGEBLIT
670 Support for S1D13XXX framebuffer device family (currently only
671 working with S1D13806). Product specs at
672 <https://vdc.epson.com/>
675 tristate "AT91 LCD Controller support"
676 depends on FB && OF && HAVE_CLK && HAS_IOMEM
677 depends on HAVE_FB_ATMEL || COMPILE_TEST
679 select FB_IOMEM_HELPERS
680 select FB_MODE_HELPERS
681 select VIDEOMODE_HELPERS
683 This enables support for the AT91 LCD Controller.
686 tristate "nVidia Framebuffer Support"
688 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
689 select FB_MODE_HELPERS
690 select FB_CFB_FILLRECT
691 select FB_CFB_COPYAREA
692 select FB_CFB_IMAGEBLIT
695 select VIDEO_NOMODESET
697 This driver supports graphics boards with the nVidia chips, TNT
698 and newer. For very old chipsets, such as the RIVA128, then use
700 Say Y if you have such a graphics board.
702 To compile this driver as a module, choose M here: the
703 module will be called nvidiafb.
706 bool "Enable DDC Support"
710 This enables I2C support for nVidia Chipsets. This is used
711 only for getting EDID information from the attached display
712 allowing for robust video mode handling and switching.
714 Because fbdev-2.6 requires that drivers must be able to
715 independently validate video mode parameters, you should say Y
718 config FB_NVIDIA_DEBUG
719 bool "Lots of debug output"
722 Say Y here if you want the nVidia driver to output all sorts
723 of debugging information to provide to the maintainer when
724 something goes wrong.
726 config FB_NVIDIA_BACKLIGHT
727 bool "Support for backlight control"
731 Say Y here if you want to control the backlight of your display.
734 tristate "nVidia Riva support"
736 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
737 select FB_MODE_HELPERS
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
743 select VIDEO_NOMODESET
745 This driver supports graphics boards with the nVidia Riva/Geforce
747 Say Y if you have such a graphics board.
749 To compile this driver as a module, choose M here: the
750 module will be called rivafb.
753 bool "Enable DDC Support"
757 This enables I2C support for nVidia Chipsets. This is used
758 only for getting EDID information from the attached display
759 allowing for robust video mode handling and switching.
761 Because fbdev-2.6 requires that drivers must be able to
762 independently validate video mode parameters, you should say Y
766 bool "Lots of debug output"
769 Say Y here if you want the Riva driver to output all sorts
770 of debugging information to provide to the maintainer when
771 something goes wrong.
773 config FB_RIVA_BACKLIGHT
774 bool "Support for backlight control"
778 Say Y here if you want to control the backlight of your display.
781 tristate "Intel740 support"
783 select FB_IOMEM_HELPERS
784 select FB_MODE_HELPERS
786 select VIDEO_NOMODESET
789 This driver supports graphics cards based on Intel740 chip.
792 tristate "Intel 810/815 support"
793 depends on FB && PCI && X86_32 && AGP_INTEL
794 select FB_MODE_HELPERS
795 select FB_CFB_FILLRECT
796 select FB_CFB_COPYAREA
797 select FB_CFB_IMAGEBLIT
799 select VIDEO_NOMODESET
801 This driver supports the on-board graphics built in to the Intel 810
802 and 815 chipsets. Say Y if you have and plan to use such a board.
804 To compile this driver as a module, choose M here: the
805 module will be called i810fb.
807 For more information, please read
808 <file:Documentation/fb/intel810.rst>
811 bool "use VESA Generalized Timing Formula"
814 If you say Y, then the VESA standard, Generalized Timing Formula
815 or GTF, will be used to calculate the required video timing values
816 per video mode. Since the GTF allows nondiscrete timings
817 (nondiscrete being a range of values as opposed to discrete being a
818 set of values), you'll be able to use any combination of horizontal
819 and vertical resolutions, and vertical refresh rates without having
820 to specify your own timing parameters. This is especially useful
821 to maximize the performance of an aging display, or if you just
822 have a display with nonstandard dimensions. A VESA compliant
823 monitor is recommended, but can still work with non-compliant ones.
824 If you need or want this, then select this option. The timings may
825 not be compliant with Intel's recommended values. Use at your own
828 If you say N, the driver will revert to discrete video timings
829 using a set recommended by Intel in their documentation.
834 bool "Enable DDC Support"
835 depends on FB_I810 && FB_I810_GTF
838 Add DDC/I2C support for i810fb. This will allow the driver to get
839 display information, especially for monitors with fickle timings.
844 tristate "Intel LE80578 (Vermilion) support"
845 depends on FB && PCI && X86
846 select FB_MODE_HELPERS
847 select FB_CFB_FILLRECT
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
850 select VIDEO_NOMODESET
852 This driver supports the LE80578 (Vermilion Range) chipset
854 config FB_CARILLO_RANCH
855 tristate "Intel Carillo Ranch support"
856 depends on FB_LE80578 && FB && PCI && X86
858 This driver supports the LE80578 (Carillo Ranch) board
861 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
862 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
863 select FB_MODE_HELPERS
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
867 select BOOT_VESA_SUPPORT if FB_INTEL = y
868 select VIDEO_NOMODESET
871 This driver supports the on-board graphics built in to the Intel
872 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
873 Say Y if you have and plan to use such a board.
875 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
877 To compile this driver as a module, choose M here: the
878 module will be called intelfb.
880 For more information, please read <file:Documentation/fb/intelfb.rst>
882 config FB_INTEL_DEBUG
883 bool "Intel driver Debug Messages"
886 Say Y here if you want the Intel driver to output all sorts
887 of debugging information to provide to the maintainer when
888 something goes wrong.
891 bool "DDC/I2C for Intel framebuffer support"
896 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
899 tristate "Matrox acceleration"
901 select FB_CFB_FILLRECT
902 select FB_CFB_COPYAREA
903 select FB_CFB_IMAGEBLIT
904 select FB_TILEBLITTING
905 select FB_MACMODES if PPC_PMAC
906 select VIDEO_NOMODESET
908 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
909 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
910 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
911 Matrox G400, G450 or G550 card in your box.
913 To compile this driver as a module, choose M here: the
914 module will be called matroxfb.
916 You can pass several parameters to the driver at boot time or at
917 module load time. The parameters look like "video=matroxfb:XXX", and
918 are described in <file:Documentation/fb/matroxfb.rst>.
920 config FB_MATROX_MILLENIUM
921 bool "Millennium I/II support"
924 Say Y here if you have a Matrox Millennium or Matrox Millennium II
925 video card. If you select "Advanced lowlevel driver options" below,
926 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
927 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
928 also use font widths different from 8.
930 config FB_MATROX_MYSTIQUE
931 bool "Mystique support"
934 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
935 video card. If you select "Advanced lowlevel driver options" below,
936 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
937 packed pixel and 32 bpp packed pixel. You can also use font widths
941 bool "G100/G200/G400/G450/G550 support"
944 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
945 video card. If you select "Advanced lowlevel driver options", you
946 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
947 pixel and 32 bpp packed pixel. You can also use font widths
950 If you need support for G400 secondary head, you must say Y to
951 "Matrox I2C support" and "G400 second head support" right below.
952 G450/G550 secondary head and digital output are supported without
955 The driver starts in monitor mode. You must use the matroxset tool
956 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
957 swap primary and secondary head outputs, or to change output mode.
958 Secondary head driver always start in 640x480 resolution and you
959 must use fbset to change it.
961 Do not forget that second head supports only 16 and 32 bpp
962 packed pixels, so it is a good idea to compile them into the kernel
963 too. You can use only some font widths, as the driver uses generic
964 painting procedures (the secondary head does not use acceleration
967 G450/G550 hardware can display TV picture only from secondary CRTC,
968 and it performs no scaling, so picture must have 525 or 625 lines.
971 tristate "Matrox I2C support"
975 This drivers creates I2C buses which are needed for accessing the
976 DDC (I2C) bus present on all Matroxes, an I2C bus which
977 interconnects Matrox optional devices, like MGA-TVO on G200 and
978 G400, and the secondary head DDC bus, present on G400 only.
980 You can say Y or M here if you want to experiment with monitor
981 detection code. You must say Y or M here if you want to use either
982 second head of G400 or MGA-TVO on G200 or G400.
984 If you compile it as module, it will create a module named
987 config FB_MATROX_MAVEN
988 tristate "G400 second head support"
989 depends on FB_MATROX_G && FB_MATROX_I2C
991 WARNING !!! This support does not work with G450 !!!
993 Say Y or M here if you want to use a secondary head (meaning two
994 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
995 head is not compatible with accelerated XFree 3.3.x SVGA servers -
996 secondary head output is blanked while you are in X. With XFree
997 3.9.17 preview you can use both heads if you use SVGA over fbdev or
998 the fbdev driver on first head and the fbdev driver on second head.
1000 If you compile it as module, two modules are created,
1001 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1002 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1003 also load i2c-matroxfb to get it to run.
1005 The driver starts in monitor mode and you must use the matroxset
1007 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1008 PAL or NTSC or to swap primary and secondary head outputs.
1009 Secondary head driver also always start in 640x480 resolution, you
1010 must use fbset to change it.
1012 Also do not forget that second head supports only 16 and 32 bpp
1013 packed pixels, so it is a good idea to compile them into the kernel
1014 too. You can use only some font widths, as the driver uses generic
1015 painting procedures (the secondary head does not use acceleration
1019 tristate "ATI Radeon display support"
1020 depends on FB && PCI
1021 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1022 select FB_MODE_HELPERS
1023 select FB_CFB_FILLRECT
1024 select FB_CFB_COPYAREA
1025 select FB_CFB_IMAGEBLIT
1026 select FB_MACMODES if PPC
1027 select VIDEO_NOMODESET
1029 Choose this option if you want to use an ATI Radeon graphics card as
1030 a framebuffer device. There are both PCI and AGP versions. You
1031 don't need to choose this to run the Radeon in plain VGA mode.
1033 There is a product page at
1034 https://products.amd.com/en-us/GraphicCardResult.aspx
1036 config FB_RADEON_I2C
1037 bool "DDC/I2C for ATI Radeon support"
1038 depends on FB_RADEON
1042 Say Y here if you want DDC/I2C support for your Radeon board.
1044 config FB_RADEON_BACKLIGHT
1045 bool "Support for backlight control"
1046 depends on FB_RADEON
1049 Say Y here if you want to control the backlight of your display.
1051 config FB_RADEON_DEBUG
1052 bool "Lots of debug output from Radeon driver"
1053 depends on FB_RADEON
1055 Say Y here if you want the Radeon driver to output all sorts
1056 of debugging information to provide to the maintainer when
1057 something goes wrong.
1060 tristate "ATI Rage128 display support"
1061 depends on FB && PCI
1062 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1063 select FB_IOMEM_HELPERS
1064 select FB_MACMODES if PPC_PMAC
1065 select VIDEO_NOMODESET
1067 This driver supports graphics boards with the ATI Rage128 chips.
1068 Say Y if you have such a graphics board and read
1069 <file:Documentation/fb/aty128fb.rst>.
1071 To compile this driver as a module, choose M here: the
1072 module will be called aty128fb.
1074 config FB_ATY128_BACKLIGHT
1075 bool "Support for backlight control"
1076 depends on FB_ATY128
1079 Say Y here if you want to control the backlight of your display.
1082 tristate "ATI Mach64 display support" if PCI || ATARI
1083 depends on FB && !SPARC32
1084 select FB_CFB_FILLRECT
1085 select FB_CFB_COPYAREA
1086 select FB_CFB_IMAGEBLIT
1087 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1088 select FB_IOMEM_FOPS
1089 select FB_MACMODES if PPC
1090 select FB_ATY_CT if SPARC64 && PCI
1091 select VIDEO_NOMODESET
1093 This driver supports graphics boards with the ATI Mach64 chips.
1094 Say Y if you have such a graphics board.
1096 To compile this driver as a module, choose M here: the
1097 module will be called atyfb.
1100 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1101 depends on PCI && FB_ATY
1103 Say Y here to support use of ATI's 64-bit Rage boards (or other
1104 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1105 framebuffer device. The ATI product support page for these boards
1106 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1108 config FB_ATY_GENERIC_LCD
1109 bool "Mach64 generic LCD support"
1110 depends on FB_ATY_CT
1112 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1113 Rage XC, or Rage XL chipset.
1116 bool "Mach64 GX support" if PCI
1120 Say Y here to support use of the ATI Mach64 Graphics Expression
1121 board (or other boards based on the Mach64 GX chipset) as a
1122 framebuffer device. The ATI product support page for these boards
1124 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1126 config FB_ATY_BACKLIGHT
1127 bool "Support for backlight control"
1131 Say Y here if you want to control the backlight of your display.
1134 tristate "S3 Trio/Virge support"
1135 depends on FB && PCI
1136 select FB_CFB_FILLRECT
1137 select FB_CFB_COPYAREA
1138 select FB_CFB_IMAGEBLIT
1139 select FB_TILEBLITTING
1142 select VIDEO_NOMODESET
1143 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1145 Driver for graphics boards with S3 Trio / S3 Virge chip.
1148 bool "DDC for S3 support"
1153 Say Y here if you want DDC support for your S3 graphics card.
1156 tristate "S3 Savage support"
1157 depends on FB && PCI
1158 select FB_MODE_HELPERS
1159 select FB_CFB_FILLRECT
1160 select FB_CFB_COPYAREA
1161 select FB_CFB_IMAGEBLIT
1163 select VIDEO_NOMODESET
1165 This driver supports notebooks and computers with S3 Savage PCI/AGP
1168 Say Y if you have such a graphics card.
1170 To compile this driver as a module, choose M here; the module
1171 will be called savagefb.
1173 config FB_SAVAGE_I2C
1174 bool "Enable DDC2 Support"
1175 depends on FB_SAVAGE
1178 This enables I2C support for S3 Savage Chipsets. This is used
1179 only for getting EDID information from the attached display
1180 allowing for robust video mode handling and switching.
1182 Because fbdev-2.6 requires that drivers must be able to
1183 independently validate video mode parameters, you should say Y
1186 config FB_SAVAGE_ACCEL
1187 bool "Enable Console Acceleration"
1188 depends on FB_SAVAGE
1190 This option will compile in console acceleration support. If
1191 the resulting framebuffer console has bothersome glitches, then
1195 tristate "SiS/XGI display support"
1196 depends on FB && PCI
1197 select FB_CFB_FILLRECT
1198 select FB_CFB_COPYAREA
1199 select FB_CFB_IMAGEBLIT
1200 select BOOT_VESA_SUPPORT if FB_SIS = y
1201 select FB_SIS_300 if !FB_SIS_315
1202 select VIDEO_NOMODESET
1204 This is the frame buffer device driver for the SiS 300, 315, 330
1205 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1206 Specs available at <https://www.sis.com> and <http://www.xgitech.com>.
1208 To compile this driver as a module, choose M here; the module
1209 will be called sisfb.
1212 bool "SiS 300 series support"
1215 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1218 bool "SiS 315/330/340 series and XGI support"
1221 Say Y here to support use of the SiS 315, 330 and 340 series
1222 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1223 as XGI V3XT, V5, V8 and Z7.
1226 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1227 depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST)
1228 select FB_CFB_FILLRECT
1229 select FB_CFB_COPYAREA
1230 select FB_CFB_IMAGEBLIT
1232 select VIDEO_NOMODESET
1234 This is the frame buffer device driver for Graphics chips of VIA
1235 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1236 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1238 Say Y if you have a VIA UniChrome graphics board.
1240 To compile this driver as a module, choose M here: the
1241 module will be called viafb.
1245 config FB_VIA_DIRECT_PROCFS
1246 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1248 Allow direct hardware access to some output registers via procfs.
1249 This is dangerous but may provide the only chance to get the
1250 correct output device configuration.
1251 Its use is strongly discouraged.
1253 config FB_VIA_X_COMPATIBILITY
1254 bool "X server compatibility"
1256 This option reduces the functionality (power saving, ...) of the
1257 framebuffer to avoid negative impact on the OpenChrome X server.
1258 If you use any X server other than fbdev you should enable this
1259 otherwise it should be safe to disable it and allow using all
1265 tristate "NeoMagic display support"
1266 depends on FB && PCI
1267 select FB_MODE_HELPERS
1268 select FB_CFB_FILLRECT
1269 select FB_CFB_COPYAREA
1270 select FB_CFB_IMAGEBLIT
1272 select VIDEO_NOMODESET
1274 This driver supports notebooks with NeoMagic PCI chips.
1275 Say Y if you have such a graphics card.
1277 To compile this driver as a module, choose M here: the
1278 module will be called neofb.
1281 tristate "IMG Kyro support"
1282 depends on FB && PCI
1283 select FB_IOMEM_HELPERS
1284 select VIDEO_NOMODESET
1286 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1289 To compile this driver as a module, choose M here: the
1290 module will be called kyrofb.
1293 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1294 depends on FB && PCI
1295 select FB_CFB_IMAGEBLIT
1296 select FB_CFB_FILLRECT
1297 select FB_CFB_COPYAREA
1298 select FB_MODE_HELPERS
1299 select VIDEO_NOMODESET
1301 This driver supports graphics boards with the 3Dfx Banshee,
1302 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1303 such a graphics board.
1305 To compile this driver as a module, choose M here: the
1306 module will be called tdfxfb.
1308 config FB_3DFX_ACCEL
1309 bool "3Dfx Acceleration functions"
1312 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1313 device driver with acceleration functions.
1316 bool "Enable DDC/I2C support"
1321 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1324 tristate "3Dfx Voodoo Graphics (sst1) support"
1325 depends on FB && PCI
1326 depends on FB_DEVICE
1327 select FB_IOMEM_HELPERS
1328 select VIDEO_NOMODESET
1330 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1331 Voodoo2 (cvg) based graphics card.
1333 To compile this driver as a module, choose M here: the
1334 module will be called sstfb.
1336 WARNING: Do not use any application that uses the 3D engine
1337 (namely glide) while using this driver.
1338 Please read the <file:Documentation/fb/sstfb.rst> for supported
1339 options and other important info support.
1342 tristate "VIA VT8623 support"
1343 depends on FB && PCI
1344 select FB_CFB_FILLRECT
1345 select FB_CFB_COPYAREA
1346 select FB_CFB_IMAGEBLIT
1347 select FB_TILEBLITTING
1350 select VIDEO_NOMODESET
1351 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1353 Driver for CastleRock integrated graphics core in the
1354 VIA VT8623 [Apollo CLE266] chipset.
1357 tristate "Trident/CyberXXX/CyberBlade support"
1358 depends on FB && PCI
1359 select FB_CFB_FILLRECT
1360 select FB_CFB_COPYAREA
1361 select FB_CFB_IMAGEBLIT
1363 select FB_MODE_HELPERS
1364 select VIDEO_NOMODESET
1366 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1367 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1369 There are also integrated versions of these chips called CyberXXXX,
1370 CyberImage or CyberBlade. These chips are mostly found in laptops
1371 but also on some motherboards including early VIA EPIA motherboards.
1372 For more information, read <file:Documentation/fb/tridentfb.rst>
1374 Say Y if you have such a graphics board.
1376 To compile this driver as a module, choose M here: the
1377 module will be called tridentfb.
1380 tristate "ARK 2000PV support"
1381 depends on FB && PCI
1382 select FB_CFB_FILLRECT
1383 select FB_CFB_COPYAREA
1384 select FB_CFB_IMAGEBLIT
1385 select FB_IOMEM_FOPS
1386 select FB_TILEBLITTING
1389 select VIDEO_NOMODESET
1390 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1392 Driver for PCI graphics boards with ARK 2000PV chip
1393 and ICS 5342 RAMDAC.
1396 tristate "Permedia3 support"
1397 depends on FB && PCI
1398 select FB_CFB_FILLRECT
1399 select FB_CFB_COPYAREA
1400 select FB_CFB_IMAGEBLIT
1401 select VIDEO_NOMODESET
1403 This is the frame buffer device driver for the 3DLabs Permedia3
1404 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1405 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1406 and maybe other boards.
1409 tristate "Fujitsu carmine frame buffer support"
1410 depends on FB && PCI
1411 select FB_IOMEM_HELPERS
1412 select VIDEO_NOMODESET
1414 This is the frame buffer device driver for the Fujitsu Carmine chip.
1415 The driver provides two independent frame buffer devices.
1418 depends on FB_CARMINE
1419 prompt "DRAM timing"
1420 default FB_CARMINE_DRAM_EVAL
1422 config FB_CARMINE_DRAM_EVAL
1423 bool "Eval board timings"
1425 Use timings which work on the eval card.
1427 config CARMINE_DRAM_CUSTOM
1428 bool "Custom board timings"
1430 Use custom board timings.
1434 bool "Au1100 LCD Driver"
1435 depends on (FB = y) && MIPS_ALCHEMY
1436 select FB_IOMEM_HELPERS
1438 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1439 various panels and CRTs by passing in kernel cmd line option
1440 au1100fb:panel=<name>.
1443 bool "Au1200/Au1300 LCD Driver"
1444 depends on (FB = y) && MIPS_ALCHEMY
1445 select FB_SYS_FILLRECT
1446 select FB_SYS_COPYAREA
1447 select FB_SYS_IMAGEBLIT
1450 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1451 It can drive various panels and CRTs by passing in kernel cmd line
1452 option au1200fb:panel=<name>.
1455 bool "VIA VT8500 framebuffer support"
1456 depends on (FB = y) && ARM && ARCH_VT8500
1457 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1458 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1459 select FB_SYS_IMAGEBLIT
1460 select FB_MODE_HELPERS
1461 select VIDEOMODE_HELPERS
1463 This is the framebuffer driver for VIA VT8500 integrated LCD
1467 bool "Wondermedia WM8xxx-series frame buffer support"
1468 depends on (FB = y) && HAS_IOMEM && (ARCH_VT8500 || COMPILE_TEST)
1469 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1470 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1471 select FB_SYS_IMAGEBLIT
1472 select FB_MODE_HELPERS
1473 select VIDEOMODE_HELPERS
1475 This is the framebuffer driver for WonderMedia WM8xxx-series
1476 integrated LCD controller. This driver covers the WM8505, WM8650
1479 config FB_WMT_GE_ROPS
1480 bool "VT8500/WM8xxx accelerated raster ops support"
1481 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1483 This adds support for accelerated raster operations on the
1484 VIA VT8500 and Wondermedia 85xx series SoCs.
1486 source "drivers/video/fbdev/geode/Kconfig"
1489 tristate "HD64461 Frame Buffer support"
1490 depends on FB && HD64461
1491 select FB_CFB_FILLRECT
1492 select FB_CFB_COPYAREA
1493 select FB_CFB_IMAGEBLIT
1495 This is the frame buffer device driver for the Hitachi HD64461 LCD
1499 tristate "PMAG-AA TURBOchannel framebuffer support"
1501 select FB_IOMEM_HELPERS
1503 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1504 used mainly in the MIPS-based DECstation series.
1507 tristate "PMAG-BA TURBOchannel framebuffer support"
1509 select FB_IOMEM_HELPERS
1511 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1512 used mainly in the MIPS-based DECstation series.
1515 tristate "PMAGB-B TURBOchannel framebuffer support"
1517 select FB_IOMEM_HELPERS
1519 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1520 in the MIPS-based DECstation series. The card is currently only
1521 supported in 1280x1024x8 mode.
1524 bool "Maxine (Personal DECstation) onboard framebuffer support"
1525 depends on (FB = y) && MACH_DECSTATION
1526 select FB_IOMEM_HELPERS
1528 Support for the onboard framebuffer (1024x768x8) in the Personal
1529 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1533 bool "G364 frame buffer support"
1534 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1535 select FB_IOMEM_HELPERS
1537 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1538 Olivetti M700-10 systems.
1541 bool "Motorola 68328 native frame buffer support"
1542 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1543 select FB_IOMEM_HELPERS
1545 Say Y here if you want to support the built-in frame buffer of
1546 the Motorola 68328 CPU family.
1549 tristate "PXA168/910 LCD framebuffer support"
1550 depends on FB && HAVE_CLK && HAS_IOMEM
1551 depends on CPU_PXA168 || CPU_PXA910 || COMPILE_TEST
1552 select FB_IOMEM_HELPERS
1554 Frame buffer driver for the built-in LCD controller in the Marvell
1558 tristate "PXA LCD framebuffer support"
1559 depends on FB && ARCH_PXA
1560 select FB_IOMEM_HELPERS
1561 select VIDEOMODE_HELPERS if OF
1562 select FB_MODE_HELPERS if OF
1564 Frame buffer driver for the built-in LCD controller in the Intel
1567 This driver is also available as a module ( = code which can be
1568 inserted and removed from the running kernel whenever you want). The
1569 module will be called pxafb. If you want to compile it as a module,
1570 say M here and read <file:Documentation/kbuild/modules.rst>.
1574 config FB_PXA_OVERLAY
1575 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1576 depends on FB_PXA && (PXA27x || PXA3xx)
1578 config FB_PXA_SMARTPANEL
1579 bool "PXA Smartpanel LCD support"
1582 config FB_PXA_PARAMETERS
1583 bool "PXA LCD command line parameters"
1586 Enable the use of kernel command line or module parameters
1587 to configure the physical properties of the LCD panel when
1588 using the PXA LCD driver.
1590 This option allows you to override the panel parameters
1591 supplied by the platform in order to support multiple
1592 different models of flatpanel. If you will only be using a
1593 single model of flatpanel then you can safely leave this
1596 <file:Documentation/fb/pxafb.rst> describes the available parameters.
1599 tristate "PXA3xx 2D graphics accelerator driver"
1602 Kernelspace driver for the 2D graphics controller unit (GCU)
1603 found on PXA3xx processors. There is a counterpart driver in the
1604 DirectFB suite, see http://www.directfb.org/
1606 If you compile this as a module, it will be called pxa3xx_gcu.
1609 tristate "Freescale DIU framebuffer support"
1610 depends on FB && FSL_SOC
1611 select FB_IOMEM_HELPERS
1612 select FB_MODE_HELPERS
1613 select PPC_LIB_RHEAP
1615 Framebuffer driver for the Freescale SoC DIU
1617 config FB_SH_MOBILE_LCDC
1618 tristate "SuperH Mobile LCDC framebuffer support"
1619 depends on FB && HAVE_CLK && HAS_IOMEM
1620 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
1621 depends on FB_DEVICE
1622 select FB_SYS_FILLRECT
1623 select FB_SYS_COPYAREA
1624 select FB_SYS_IMAGEBLIT
1626 select FB_DEFERRED_IO
1629 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1632 tristate "Samsung S3C framebuffer support"
1633 depends on FB && HAVE_CLK && HAS_IOMEM
1634 depends on ARCH_S3C64XX || COMPILE_TEST
1635 select FB_IOMEM_HELPERS
1637 Frame buffer driver for the built-in FB controller in the Samsung
1638 SoC line such as the S3C6400 and S3C6410.
1640 These chips all have the same basic framebuffer design with the
1641 actual capabilities depending on the chip. The S3C6400
1642 and S3C6410 support 4 hardware windows.
1644 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1646 config FB_S3C_DEBUG_REGWRITE
1647 bool "Debug register writes"
1650 Show all register writes via pr_debug()
1653 tristate "Silicon Motion SM501 framebuffer support"
1654 depends on FB && MFD_SM501
1655 select FB_CFB_FILLRECT
1656 select FB_CFB_COPYAREA
1657 select FB_CFB_IMAGEBLIT
1659 Frame buffer driver for the CRT and LCD controllers in the Silicon
1662 This driver is also available as a module ( = code which can be
1663 inserted and removed from the running kernel whenever you want). The
1664 module will be called sm501fb. If you want to compile it as a module,
1665 say M here and read <file:Documentation/kbuild/modules.rst>.
1670 tristate "SMSC UFX6000/7000 USB Framebuffer support"
1671 depends on FB && USB
1672 select FB_MODE_HELPERS
1673 select FB_SYS_FILLRECT
1674 select FB_SYS_COPYAREA
1675 select FB_SYS_IMAGEBLIT
1677 select FB_DEFERRED_IO
1679 This is a kernel framebuffer driver for SMSC UFX USB devices.
1680 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1681 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1683 To compile as a module, choose M here: the module name is smscufx.
1686 tristate "Displaylink USB Framebuffer support"
1687 depends on FB && USB
1688 depends on FB_DEVICE
1689 select FB_MODE_HELPERS
1690 select FB_SYS_FILLRECT
1691 select FB_SYS_COPYAREA
1692 select FB_SYS_IMAGEBLIT
1694 select FB_DEFERRED_IO
1696 This is a kernel framebuffer driver for DisplayLink USB devices.
1697 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1698 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1699 To compile as a module, choose M here: the module name is udlfb.
1701 config FB_IBM_GXT4500
1702 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
1704 select FB_IOMEM_HELPERS
1705 select VIDEO_NOMODESET
1707 Say Y here to enable support for the IBM GXT4000P/6000P and
1708 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
1709 found on some IBM System P (pSeries) machines. This driver
1710 doesn't use Geometry Engine GT1000. This driver also supports
1711 AGP Fire GL2/3/4 cards on x86.
1714 tristate "PS3 GPU framebuffer driver"
1715 depends on FB && PS3_PS3AV
1716 select FB_SYS_FILLRECT
1717 select FB_SYS_COPYAREA
1718 select FB_SYS_IMAGEBLIT
1721 Include support for the virtual frame buffer in the PS3 platform.
1723 config FB_PS3_DEFAULT_SIZE_M
1724 int "PS3 default frame buffer size (in MiB)"
1728 This is the default size (in MiB) of the virtual frame buffer in
1730 The default value can be overridden on the kernel command line
1731 using the "ps3fb" option (e.g. "ps3fb=9M");
1734 tristate "Xilinx frame buffer support"
1735 depends on FB && (MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
1736 select FB_IOMEM_HELPERS
1738 Include support for the Xilinx ML300/ML403 reference design
1739 framebuffer. ML300 carries a 640*480 LCD display on the board,
1740 ML403 uses a standard DB15 VGA connector.
1743 tristate "Goldfish Framebuffer"
1745 depends on GOLDFISH || COMPILE_TEST
1746 select FB_IOMEM_HELPERS
1748 Framebuffer driver for Goldfish Virtual Platform
1751 tristate "Cobalt server LCD frame buffer support"
1752 depends on FB && MIPS_COBALT
1753 select FB_IOMEM_HELPERS
1756 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
1757 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
1758 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
1759 select FB_IOMEM_HELPERS
1761 Support for the SH7760/SH7763/SH7720/SH7721 integrated
1762 (D)STN/TFT LCD Controller.
1763 Supports display resolutions up to 1024x1024 pixel, grayscale and
1764 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
1765 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
1766 panels <= 320 pixel horizontal resolution.
1769 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
1770 depends on FB && HAVE_CLK && HAS_IOMEM
1771 depends on ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST
1772 select FB_CFB_REV_PIXELS_IN_BYTE
1773 select FB_IOMEM_HELPERS
1774 select FB_MODE_HELPERS
1775 select VIDEOMODE_HELPERS
1777 This is the frame buffer device driver for the TI LCD controller
1778 found on DA8xx/OMAP-L1xx/AM335x SoCs.
1782 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1784 select FB_SYS_FILLRECT
1785 select FB_SYS_COPYAREA
1786 select FB_SYS_IMAGEBLIT
1789 This is a `virtual' frame buffer device. It operates on a chunk of
1790 unswappable kernel memory instead of on the memory of a graphics
1791 board. This means you cannot see any output sent to this frame
1792 buffer device, while it does consume precious memory. The main use
1793 of this frame buffer device is testing and debugging the frame
1794 buffer subsystem. Do NOT enable it for normal systems! To protect
1795 the innocent, it has to be enabled explicitly at boot time using the
1796 kernel option `video=vfb:'.
1798 To compile this driver as a module, choose M here: the
1799 module will be called vfb. In order to load it, you must use
1800 the vfb_enable=1 option.
1804 config XEN_FBDEV_FRONTEND
1805 tristate "Xen virtual frame buffer support"
1806 depends on FB && XEN
1807 select FB_SYSMEM_HELPERS_DEFERRED
1808 select XEN_XENBUS_FRONTEND
1811 This driver implements the front-end of the Xen virtual
1812 frame buffer driver. It communicates with a back-end
1816 tristate "E-Ink Metronome/8track controller support"
1818 select FB_SYSMEM_HELPERS_DEFERRED
1820 This driver implements support for the E-Ink Metronome
1821 controller. The pre-release name for this device was 8track
1822 and could also have been called by some vendors as PVI-nnnn.
1825 tristate "Fujitsu MB862xx GDC support"
1827 depends on PCI || (OF && PPC)
1828 select FB_IOMEM_HELPERS
1829 select VIDEO_NOMODESET
1831 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
1834 prompt "GDC variant"
1835 depends on FB_MB862XX
1837 config FB_MB862XX_PCI_GDC
1838 bool "Carmine/Coral-P(A) GDC"
1841 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
1842 PCI graphics controller devices.
1844 config FB_MB862XX_LIME
1846 depends on OF && PPC
1847 select FB_FOREIGN_ENDIAN
1848 select FB_LITTLE_ENDIAN
1850 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
1854 config FB_MB862XX_I2C
1855 bool "Support I2C bus on MB862XX GDC"
1856 depends on FB_MB862XX && I2C
1857 depends on FB_MB862XX=m || I2C=y
1860 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
1861 driver to support accessing I2C devices on controller's I2C bus.
1862 These are usually some video decoder chips.
1865 tristate "EP93XX frame buffer support"
1866 depends on FB && ARCH_EP93XX
1867 select FB_CFB_FILLRECT
1868 select FB_CFB_COPYAREA
1869 select FB_CFB_IMAGEBLIT
1871 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
1872 This driver is also available as a module. The module will be called
1875 config FB_PRE_INIT_FB
1876 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
1877 depends on FB && FB_MB862XX_LIME
1879 Select this option if display contents should be inherited as set by
1882 config FB_BROADSHEET
1883 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
1884 depends on FB && (ARCH_PXA || COMPILE_TEST)
1885 select FB_SYSMEM_HELPERS_DEFERRED
1887 This driver implements support for the E-Ink Broadsheet
1888 controller. The release name for this device was Epson S1D13521
1889 and could also have been called by other names when coupled with
1893 tristate "Microsoft Hyper-V Synthetic Video support"
1894 depends on FB && HYPERV
1895 select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA
1896 select FB_IOMEM_HELPERS_DEFERRED
1897 select VIDEO_NOMODESET
1899 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
1902 tristate "Simple framebuffer support"
1904 depends on !DRM_SIMPLEDRM
1905 select APERTURE_HELPERS
1906 select FB_IOMEM_HELPERS
1908 Say Y if you want support for a simple frame-buffer.
1910 This driver assumes that the display hardware has been initialized
1911 before the kernel boots, and the kernel will simply render to the
1912 pre-allocated frame buffer surface.
1914 Configuration re: surface address, size, and format must be provided
1915 through device tree, or plain old platform data.
1918 tristate "Solomon SSD1307 framebuffer support"
1919 depends on FB && I2C
1920 depends on GPIOLIB || COMPILE_TEST
1922 select FB_SYSMEM_HELPERS_DEFERRED
1924 This driver implements support for the Solomon SSD1307
1925 OLED controller over I2C.
1928 tristate "Silicon Motion SM712 framebuffer support"
1929 depends on FB && PCI
1930 select FB_CFB_FILLRECT
1931 select FB_CFB_COPYAREA
1932 select FB_CFB_IMAGEBLIT
1933 select VIDEO_NOMODESET
1935 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
1938 This driver is also available as a module. The module will be
1939 called sm712fb. If you want to compile it as a module, say M
1940 here and read <file:Documentation/kbuild/modules.rst>.
1942 source "drivers/video/fbdev/omap/Kconfig"
1943 source "drivers/video/fbdev/omap2/Kconfig"
1944 source "drivers/video/fbdev/mmp/Kconfig"
1946 source "drivers/video/fbdev/core/Kconfig"