1 # SPDX-License-Identifier: GPL-2.0-only
13 tristate "Support for frame buffer devices"
17 The frame buffer device provides an abstraction for the graphics
18 hardware. It represents the frame buffer of some video hardware and
19 allows application software to access the graphics hardware through
20 a well-defined interface, so the software doesn't need to know
21 anything about the low-level (hardware register) stuff.
23 Frame buffer devices work identically across the different
24 architectures supported by Linux and make the implementation of
25 application programs easier and more portable; at this point, an X
26 server exists which uses the frame buffer device exclusively.
27 On several non-X86 architectures, the frame buffer device is the
28 only way to use the graphics hardware.
30 The device is accessed through special device nodes, usually located
31 in the /dev directory, i.e. /dev/fb*.
33 You need an utility program called fbset to make full use of frame
34 buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
35 and the Framebuffer-HOWTO at
36 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
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.
49 bool "Enable firmware EDID"
52 This enables access to the EDID transferred from the firmware.
53 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
54 transfers do not work for your driver and if you are using
55 nvidiafb, i810fb or savagefb.
57 In general, choosing Y for this option is safe. If you
58 experience extremely long delays while booting before you get
59 something on your display, try setting this to N. Matrox cards in
60 combination with certain motherboards and monitors are known to
61 suffer from this problem.
69 config FB_BOOT_VESA_SUPPORT
73 If true, at least one selected framebuffer driver can take advantage
74 of VESA video modes set at an early boot stage via the vga= parameter.
76 config FB_CFB_FILLRECT
80 Include the cfb_fillrect function for generic software rectangle
81 filling. This is used by drivers that don't provide their own
82 (accelerated) version.
84 config FB_CFB_COPYAREA
88 Include the cfb_copyarea function for generic software area copying.
89 This is used by drivers that don't provide their own (accelerated)
92 config FB_CFB_IMAGEBLIT
96 Include the cfb_imageblit function for generic software image
97 blitting. This is used by drivers that don't provide their own
98 (accelerated) version.
100 config FB_CFB_REV_PIXELS_IN_BYTE
104 Allow generic frame-buffer functions to work on displays with 1, 2
105 and 4 bits per pixel depths which has opposite order of pixels in
106 byte order to bytes in long order.
108 config FB_SYS_FILLRECT
112 Include the sys_fillrect function for generic software rectangle
113 filling. This is used by drivers that don't provide their own
114 (accelerated) version and the framebuffer is in system RAM.
116 config FB_SYS_COPYAREA
120 Include the sys_copyarea function for generic software area copying.
121 This is used by drivers that don't provide their own (accelerated)
122 version and the framebuffer is in system RAM.
124 config FB_SYS_IMAGEBLIT
128 Include the sys_imageblit function for generic software image
129 blitting. This is used by drivers that don't provide their own
130 (accelerated) version and the framebuffer is in system RAM.
132 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
136 Allow generic frame-buffer to provide get_fb_unmapped_area
139 menuconfig FB_FOREIGN_ENDIAN
140 bool "Framebuffer foreign endianness support"
143 This menu will let you enable support for the framebuffers with
144 non-native endianness (e.g. Little-Endian framebuffer on a
145 Big-Endian machine). Most probably you don't have such hardware,
146 so it's safe to say "n" here.
149 prompt "Choice endianness support"
150 depends on FB_FOREIGN_ENDIAN
152 config FB_BOTH_ENDIAN
153 bool "Support for Big- and Little-Endian framebuffers"
156 bool "Support for Big-Endian framebuffers only"
158 config FB_LITTLE_ENDIAN
159 bool "Support for Little-Endian framebuffers only"
167 config FB_DEFERRED_IO
174 depends on FB_DEFERRED_IO
180 Common utility functions useful to fbdev drivers of VGA-based
190 select BACKLIGHT_CLASS_DEVICE
192 config FB_MODE_HELPERS
193 bool "Enable Video Mode Handling Helpers"
196 This enables functions for handling video modes using the
197 Generalized Timing Formula and the EDID parser. A few drivers rely
198 on this feature such as the radeonfb, rivafb, and the i810fb. If
199 your driver does not take advantage of this feature, choosing Y will
200 just increase the kernel size by about 5K.
202 config FB_TILEBLITTING
203 bool "Enable Tile Blitting Support"
206 This enables tile blitting. Tile blitting is a drawing technique
207 where the screen is divided into rectangular sections (tiles), whereas
208 the standard blitting divides the screen into pixels. Because the
209 default drawing element is a tile, drawing functions will be passed
210 parameters in terms of number of tiles instead of number of pixels.
211 For example, to draw a single character, instead of using bitmaps,
212 an index to an array of bitmaps will be used. To clear or move a
213 rectangular section of a screen, the rectangle will be described in
214 terms of number of tiles in the x- and y-axis.
216 This is particularly important to one driver, matroxfb. If
219 comment "Frame buffer hardware drivers"
223 tristate "Aeroflex Gaisler framebuffer support"
224 depends on FB && SPARC
225 select FB_CFB_FILLRECT
226 select FB_CFB_COPYAREA
227 select FB_CFB_IMAGEBLIT
229 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
232 tristate "Cirrus Logic support"
233 depends on FB && (ZORRO || PCI)
234 select FB_CFB_FILLRECT
235 select FB_CFB_COPYAREA
236 select FB_CFB_IMAGEBLIT
238 This enables support for Cirrus Logic GD542x/543x based boards on
239 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
241 If you have a PCI-based system, this enables support for these
242 chips: GD-543x, GD-544x, GD-5480.
244 Please read the file <file:Documentation/fb/cirrusfb.rst>.
246 Say N unless you have such a graphics board or plan to get one
247 before you next recompile the kernel.
250 tristate "Permedia2 support"
251 depends on FB && ((AMIGA && BROKEN) || PCI)
252 select FB_CFB_FILLRECT
253 select FB_CFB_COPYAREA
254 select FB_CFB_IMAGEBLIT
256 This is the frame buffer device driver for cards based on
257 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
258 The driver was tested on the following cards:
259 Diamond FireGL 1000 PRO AGP
260 ELSA Gloria Synergy PCI
261 Appian Jeronimo PRO (both heads) PCI
262 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
263 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
264 ASK Graphic Blaster Exxtreme AGP
266 To compile this driver as a module, choose M here: the
267 module will be called pm2fb.
269 config FB_PM2_FIFO_DISCONNECT
270 bool "enable FIFO disconnect feature"
271 depends on FB_PM2 && PCI
273 Support the Permedia2 FIFO disconnect feature.
276 tristate "ARM PrimeCell PL110 support"
277 depends on ARM || ARM64 || COMPILE_TEST
278 depends on FB && ARM_AMBA && HAS_IOMEM
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
282 select FB_MODE_HELPERS if OF
283 select VIDEOMODE_HELPERS if OF
284 select BACKLIGHT_CLASS_DEVICE if OF
286 This framebuffer device driver is for the ARM PrimeCell PL110
287 Colour LCD controller. ARM PrimeCells provide the building
288 blocks for System on a Chip devices.
290 If you want to compile this as a module (=code which can be
291 inserted into and removed from the running kernel), say M
292 here and read <file:Documentation/kbuild/modules.rst>. The module
293 will be called amba-clcd.
296 bool "Acorn VIDC support"
297 depends on (FB = y) && ARM && ARCH_ACORN
298 select FB_CFB_FILLRECT
299 select FB_CFB_COPYAREA
300 select FB_CFB_IMAGEBLIT
302 This is the frame buffer device driver for the Acorn VIDC graphics
303 hardware found in Acorn RISC PCs and other ARM-based machines. If
307 tristate "CLPS711X LCD support"
308 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
309 select FB_MODE_HELPERS
310 select FB_SYS_FILLRECT
311 select FB_SYS_COPYAREA
312 select FB_SYS_IMAGEBLIT
313 select LCD_CLASS_DEVICE
314 select VIDEOMODE_HELPERS
316 Say Y to enable the Framebuffer driver for the Cirrus Logic
320 bool "SA-1100 LCD support"
321 depends on (FB = y) && ARM && ARCH_SA1100
322 select FB_CFB_FILLRECT
323 select FB_CFB_COPYAREA
324 select FB_CFB_IMAGEBLIT
326 This is a framebuffer device for the SA-1100 LCD Controller.
327 See <http://www.linux-fbdev.org/> for information on framebuffer
330 If you plan to use the LCD display with your SA-1100 system, say
334 tristate "Freescale i.MX1/21/25/27 LCD support"
335 depends on FB && ARCH_MXC
336 select LCD_CLASS_DEVICE
337 select FB_CFB_FILLRECT
338 select FB_CFB_COPYAREA
339 select FB_CFB_IMAGEBLIT
340 select FB_MODE_HELPERS
341 select VIDEOMODE_HELPERS
344 tristate "CyberPro 2000/2010/5000 support"
345 depends on FB && PCI && (BROKEN || !SPARC64)
346 select FB_CFB_FILLRECT
347 select FB_CFB_COPYAREA
348 select FB_CFB_IMAGEBLIT
350 This enables support for the Integraphics CyberPro 20x0 and 5000
351 VGA chips used in the Rebel.com Netwinder and other machines.
352 Say Y if you have a NetWinder or a graphics card containing this
353 device, otherwise say N.
355 config FB_CYBER2000_DDC
356 bool "DDC for CyberPro support"
357 depends on FB_CYBER2000
361 Say Y here if you want DDC support for your CyberPro graphics
362 card. This is only I2C bus support, driver does not use EDID.
364 config FB_CYBER2000_I2C
365 bool "CyberPro 2000/2010/5000 I2C support"
366 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
367 depends on I2C=y || FB_CYBER2000=m
370 Enable support for the I2C video decoder interface on the
371 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
372 on the Netwinder machines for the SAA7111 video capture.
376 depends on (FB = y) && APOLLO
378 select FB_CFB_FILLRECT
379 select FB_CFB_IMAGEBLIT
383 depends on (FB = y) && Q40
385 select FB_CFB_FILLRECT
386 select FB_CFB_COPYAREA
387 select FB_CFB_IMAGEBLIT
390 tristate "Amiga native chipset support"
391 depends on FB && AMIGA
393 This is the frame buffer device driver for the builtin graphics
394 chipset found in Amigas.
396 To compile this driver as a module, choose M here: the
397 module will be called amifb.
400 bool "Amiga OCS chipset support"
403 This enables support for the original Agnus and Denise video chips,
404 found in the Amiga 1000 and most A500's and A2000's. If you intend
405 to run Linux on any of these systems, say Y; otherwise say N.
408 bool "Amiga ECS chipset support"
411 This enables support for the Enhanced Chip Set, found in later
412 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
413 you intend to run Linux on any of these systems, say Y; otherwise
417 bool "Amiga AGA chipset support"
420 This enables support for the Advanced Graphics Architecture (also
421 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
422 and CD32. If you intend to run Linux on any of these systems, say Y;
426 bool "Amiga FrameMaster II/Rainbow II support"
427 depends on (FB = y) && ZORRO
428 select FB_CFB_FILLRECT
429 select FB_CFB_COPYAREA
430 select FB_CFB_IMAGEBLIT
432 This is the frame buffer device driver for the Amiga FrameMaster
433 card from BSC (exhibited 1992 but not shipped as a CBM product).
436 tristate "Arc Monochrome LCD board support"
438 select FB_SYS_FILLRECT
439 select FB_SYS_COPYAREA
440 select FB_SYS_IMAGEBLIT
443 This enables support for the Arc Monochrome LCD board. The board
444 is based on the KS-108 lcd controller and is typically a matrix
445 of 2*n chips. This driver was tested with a 128x64 panel. This
446 driver supports it for use with x86 SBCs through a 16 bit GPIO
447 interface (8 bit data, 8 bit control). If you anticipate using
448 this driver, say Y or M; otherwise say N. You must specify the
449 GPIO IO address to be used for setting control and data.
452 bool "Atari native chipset support"
453 depends on (FB = y) && ATARI
454 select FB_CFB_FILLRECT
455 select FB_CFB_COPYAREA
456 select FB_CFB_IMAGEBLIT
458 This is the frame buffer device driver for the builtin graphics
459 chipset found in Ataris.
462 bool "Open Firmware frame buffer device support"
463 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
464 select FB_CFB_FILLRECT
465 select FB_CFB_COPYAREA
466 select FB_CFB_IMAGEBLIT
469 Say Y if you want support with Open Firmware for your graphics
473 bool "Apple \"control\" display support"
474 depends on (FB = y) && PPC_PMAC && PPC32
475 select FB_CFB_FILLRECT
476 select FB_CFB_COPYAREA
477 select FB_CFB_IMAGEBLIT
480 This driver supports a frame buffer for the graphics adapter in the
481 Power Macintosh 7300 and others.
484 bool "Apple \"platinum\" display support"
485 depends on (FB = y) && PPC_PMAC && PPC32
486 select FB_CFB_FILLRECT
487 select FB_CFB_COPYAREA
488 select FB_CFB_IMAGEBLIT
491 This driver supports a frame buffer for the "platinum" graphics
492 adapter in some Power Macintoshes.
495 bool "Apple \"valkyrie\" display support"
496 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
502 This driver supports a frame buffer for the "valkyrie" graphics
503 adapter in some Power Macintoshes.
506 bool "Chips 65550 display support"
507 depends on (FB = y) && PPC32 && PCI
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
512 This is the frame buffer device driver for the Chips & Technologies
513 65550 graphics chip in PowerBooks.
516 bool "Asiliant (Chips) 69000 display support"
517 depends on (FB = y) && PCI
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
522 This is the frame buffer device driver for the Asiliant 69030 chipset
525 bool "IMS Twin Turbo display support"
526 depends on (FB = y) && PCI
527 select FB_CFB_IMAGEBLIT
528 select FB_MACMODES if PPC_PMAC
530 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
531 many Macintosh and compatible computers.
534 tristate "VGA 16-color graphics support"
535 depends on FB && (X86 || PPC)
536 select FB_CFB_FILLRECT
537 select FB_CFB_COPYAREA
538 select FB_CFB_IMAGEBLIT
540 select FONT_8x16 if FRAMEBUFFER_CONSOLE
542 This is the frame buffer device driver for VGA 16 color graphic
543 cards. Say Y if you have such a card.
545 To compile this driver as a module, choose M here: the
546 module will be called vga16fb.
549 tristate "HP STI frame buffer device support"
550 depends on FB && PARISC
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
556 STI refers to the HP "Standard Text Interface" which is a set of
557 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
558 Enabling this option will implement the linux framebuffer device
559 using calls to the STI BIOS routines for initialisation.
561 If you enable this option, you will get a planar framebuffer device
562 /dev/fb which will work on the most common HP graphic cards of the
563 NGLE family, including the artist chips (in the 7xx and Bxxx series),
564 HCRX, HCRX24, CRX, CRX24 and VisEG series.
566 It is safe to enable this option, so you should probably say "Y".
569 bool "Generic Macintosh display support"
570 depends on (FB = y) && MAC
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
578 depends on (FB = y) && DIO
579 select FB_CFB_IMAGEBLIT
583 tristate "TGA/SFB+ framebuffer support"
584 depends on FB && (ALPHA || TC)
585 select FB_CFB_FILLRECT
586 select FB_CFB_COPYAREA
587 select FB_CFB_IMAGEBLIT
590 This is the frame buffer device driver for generic TGA and SFB+
591 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
592 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
593 TURBOchannel cards, also known as PMAGD-A, -B and -C.
595 Due to hardware limitations ZLX-E2 and E3 cards are not supported
596 for DECstation 5000/200 systems. Additionally due to firmware
597 limitations these cards may cause troubles with booting DECstation
598 5000/240 and /260 systems, but are fully supported under Linux if
599 you manage to get it going. ;-)
601 Say Y if you have one of those.
604 tristate "Userspace VESA VGA graphics support"
605 depends on FB && CONNECTOR
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
609 select FB_MODE_HELPERS
611 This is the frame buffer driver for generic VBE 2.0 compliant
612 graphic cards. It can also take advantage of VBE 3.0 features,
613 such as refresh rate adjustment.
615 This driver generally provides more features than vesafb but
616 requires a userspace helper application called 'v86d'. See
617 <file:Documentation/fb/uvesafb.rst> for more information.
622 bool "VESA VGA graphics support"
623 depends on (FB = y) && X86
624 select FB_CFB_FILLRECT
625 select FB_CFB_COPYAREA
626 select FB_CFB_IMAGEBLIT
627 select FB_BOOT_VESA_SUPPORT
629 This is the frame buffer device driver for generic VESA 2.0
630 compliant graphic cards. The older VESA 1.2 cards are not supported.
631 You will get a boot time penguin logo at no additional cost. Please
632 read <file:Documentation/fb/vesafb.rst>. If unsure, say Y.
635 bool "EFI-based Framebuffer Support"
636 depends on (FB = y) && !IA64 && EFI
637 select DRM_PANEL_ORIENTATION_QUIRKS
638 select FB_CFB_FILLRECT
639 select FB_CFB_COPYAREA
640 select FB_CFB_IMAGEBLIT
642 This is the EFI frame buffer device driver. If the firmware on
643 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
644 using the EFI framebuffer as your console.
647 tristate "N411 Apollo/Hecuba devkit support"
648 depends on FB && X86 && MMU
649 select FB_SYS_FILLRECT
650 select FB_SYS_COPYAREA
651 select FB_SYS_IMAGEBLIT
653 select FB_DEFERRED_IO
656 This enables support for the Apollo display controller in its
657 Hecuba form using the n411 devkit.
660 tristate "Hercules mono graphics support"
663 Say Y here if you have a Hercules mono graphics card.
665 To compile this driver as a module, choose M here: the
666 module will be called hgafb.
668 As this card technology is at least 25 years old,
669 most people will answer N here.
672 bool "SGI Graphics Backend frame buffer support"
673 depends on (FB = y) && SGI_IP32
674 select FB_CFB_FILLRECT
675 select FB_CFB_COPYAREA
676 select FB_CFB_IMAGEBLIT
678 This is the frame buffer device driver for SGI Graphics Backend.
679 This chip is used in SGI O2 and Visual Workstation 320/540.
682 int "Video memory size in MB"
686 This is the amount of memory reserved for the framebuffer,
687 which can be any value between 1MB and 8MB.
690 bool "SBUS and UPA framebuffers"
691 depends on (FB = y) && SPARC
693 Say Y if you want support for SBUS or UPA based frame buffer device.
697 depends on (FB = y) && (SPARC && FB_SBUS)
698 select FB_CFB_FILLRECT
699 select FB_CFB_COPYAREA
700 select FB_CFB_IMAGEBLIT
702 This is the frame buffer device driver for the BWtwo frame buffer.
705 bool "CGthree support"
706 depends on (FB = y) && (SPARC && FB_SBUS)
707 select FB_CFB_FILLRECT
708 select FB_CFB_COPYAREA
709 select FB_CFB_IMAGEBLIT
711 This is the frame buffer device driver for the CGthree frame buffer.
714 bool "CGsix (GX,TurboGX) support"
715 depends on (FB = y) && (SPARC && FB_SBUS)
716 select FB_CFB_COPYAREA
717 select FB_CFB_IMAGEBLIT
719 This is the frame buffer device driver for the CGsix (GX, TurboGX)
723 bool "Creator/Creator3D/Elite3D support"
724 depends on FB_SBUS && SPARC64
725 select FB_CFB_COPYAREA
726 select FB_CFB_IMAGEBLIT
728 This is the frame buffer device driver for the Creator, Creator3D,
729 and Elite3D graphics boards.
732 bool "TCX (SS4/SS5 only) support"
734 select FB_CFB_FILLRECT
735 select FB_CFB_COPYAREA
736 select FB_CFB_IMAGEBLIT
738 This is the frame buffer device driver for the TCX 24/8bit frame
742 bool "CGfourteen (SX) support"
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
748 This is the frame buffer device driver for the CGfourteen frame
749 buffer on Desktop SPARCsystems with the SX graphics option.
752 bool "P9100 (Sparcbook 3 only) support"
754 select FB_CFB_FILLRECT
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
758 This is the frame buffer device driver for the P9100 card
759 supported on Sparcbook 3 machines.
762 bool "Leo (ZX) support"
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
768 This is the frame buffer device driver for the SBUS-based Sun ZX
769 (leo) frame buffer cards.
772 bool "Sun XVR-500 3DLABS Wildcat support"
773 depends on (FB = y) && PCI && SPARC64
774 select FB_CFB_FILLRECT
775 select FB_CFB_COPYAREA
776 select FB_CFB_IMAGEBLIT
778 This is the framebuffer device for the Sun XVR-500 and similar
779 graphics cards based upon the 3DLABS Wildcat chipset. The driver
780 only works on sparc64 systems where the system firmware has
781 mostly initialized the card already. It is treated as a
782 completely dumb framebuffer device.
785 bool "Sun XVR-2500 3DLABS Wildcat support"
786 depends on (FB = y) && PCI && SPARC64
787 select FB_CFB_FILLRECT
788 select FB_CFB_COPYAREA
789 select FB_CFB_IMAGEBLIT
791 This is the framebuffer device for the Sun XVR-2500 and similar
792 graphics cards based upon the 3DLABS Wildcat chipset. The driver
793 only works on sparc64 systems where the system firmware has
794 mostly initialized the card already. It is treated as a
795 completely dumb framebuffer device.
798 bool "Sun XVR-1000 support"
799 depends on (FB = y) && SPARC64
800 select FB_CFB_FILLRECT
801 select FB_CFB_COPYAREA
802 select FB_CFB_IMAGEBLIT
804 This is the framebuffer device for the Sun XVR-1000 and similar
805 graphics cards. The driver only works on sparc64 systems where
806 the system firmware has mostly initialized the card already. It
807 is treated as a completely dumb framebuffer device.
810 tristate "NEC PowerVR 2 display support"
811 depends on FB && SH_DREAMCAST
812 select FB_CFB_FILLRECT
813 select FB_CFB_COPYAREA
814 select FB_CFB_IMAGEBLIT
816 Say Y here if you have a PowerVR 2 card in your box. If you plan to
817 run linux on your Dreamcast, you will have to say Y here.
818 This driver may or may not work on other PowerVR 2 cards, but is
819 totally untested. Use at your own risk. If unsure, say N.
821 To compile this driver as a module, choose M here: the
822 module will be called pvr2fb.
824 You can pass several parameters to the driver at boot time or at
825 module load time. The parameters look like "video=pvr2:XXX", where
826 the meaning of XXX can be found at the end of the main source file
827 (<file:drivers/video/pvr2fb.c>). Please see the file
828 <file:Documentation/fb/pvr2fb.rst>.
831 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
832 depends on FB && HAS_DMA
833 select FB_CFB_FILLRECT
834 select FB_CFB_COPYAREA
835 select FB_CFB_IMAGEBLIT
837 This enables support for the OpenCores VGA/LCD core.
839 The OpenCores VGA/LCD core is typically used together with
840 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
841 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
843 The source code and specification for the core is available at
844 <http://opencores.org/project,vga_lcd>
847 tristate "Epson S1D13XXX framebuffer support"
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
853 Support for S1D13XXX framebuffer device family (currently only
854 working with S1D13806). Product specs at
855 <http://vdc.epson.com/>
858 tristate "AT91 LCD Controller support"
859 depends on FB && OF && HAVE_FB_ATMEL
861 select FB_CFB_FILLRECT
862 select FB_CFB_COPYAREA
863 select FB_CFB_IMAGEBLIT
864 select FB_MODE_HELPERS
865 select VIDEOMODE_HELPERS
867 This enables support for the AT91 LCD Controller.
870 tristate "nVidia Framebuffer Support"
872 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
873 select FB_MODE_HELPERS
874 select FB_CFB_FILLRECT
875 select FB_CFB_COPYAREA
876 select FB_CFB_IMAGEBLIT
880 This driver supports graphics boards with the nVidia chips, TNT
881 and newer. For very old chipsets, such as the RIVA128, then use
883 Say Y if you have such a graphics board.
885 To compile this driver as a module, choose M here: the
886 module will be called nvidiafb.
889 bool "Enable DDC Support"
893 This enables I2C support for nVidia Chipsets. This is used
894 only for getting EDID information from the attached display
895 allowing for robust video mode handling and switching.
897 Because fbdev-2.6 requires that drivers must be able to
898 independently validate video mode parameters, you should say Y
901 config FB_NVIDIA_DEBUG
902 bool "Lots of debug output"
905 Say Y here if you want the nVidia driver to output all sorts
906 of debugging information to provide to the maintainer when
907 something goes wrong.
909 config FB_NVIDIA_BACKLIGHT
910 bool "Support for backlight control"
914 Say Y here if you want to control the backlight of your display.
917 tristate "nVidia Riva support"
919 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
920 select FB_MODE_HELPERS
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
927 This driver supports graphics boards with the nVidia Riva/Geforce
929 Say Y if you have such a graphics board.
931 To compile this driver as a module, choose M here: the
932 module will be called rivafb.
935 bool "Enable DDC Support"
939 This enables I2C support for nVidia Chipsets. This is used
940 only for getting EDID information from the attached display
941 allowing for robust video mode handling and switching.
943 Because fbdev-2.6 requires that drivers must be able to
944 independently validate video mode parameters, you should say Y
948 bool "Lots of debug output"
951 Say Y here if you want the Riva driver to output all sorts
952 of debugging information to provide to the maintainer when
953 something goes wrong.
955 config FB_RIVA_BACKLIGHT
956 bool "Support for backlight control"
960 Say Y here if you want to control the backlight of your display.
963 tristate "Intel740 support"
965 select FB_MODE_HELPERS
966 select FB_CFB_FILLRECT
967 select FB_CFB_COPYAREA
968 select FB_CFB_IMAGEBLIT
972 This driver supports graphics cards based on Intel740 chip.
975 tristate "Intel 810/815 support"
976 depends on FB && PCI && X86_32 && AGP_INTEL
977 select FB_MODE_HELPERS
978 select FB_CFB_FILLRECT
979 select FB_CFB_COPYAREA
980 select FB_CFB_IMAGEBLIT
983 This driver supports the on-board graphics built in to the Intel 810
984 and 815 chipsets. Say Y if you have and plan to use such a board.
986 To compile this driver as a module, choose M here: the
987 module will be called i810fb.
989 For more information, please read
990 <file:Documentation/fb/intel810.rst>
993 bool "use VESA Generalized Timing Formula"
996 If you say Y, then the VESA standard, Generalized Timing Formula
997 or GTF, will be used to calculate the required video timing values
998 per video mode. Since the GTF allows nondiscrete timings
999 (nondiscrete being a range of values as opposed to discrete being a
1000 set of values), you'll be able to use any combination of horizontal
1001 and vertical resolutions, and vertical refresh rates without having
1002 to specify your own timing parameters. This is especially useful
1003 to maximize the performance of an aging display, or if you just
1004 have a display with nonstandard dimensions. A VESA compliant
1005 monitor is recommended, but can still work with non-compliant ones.
1006 If you need or want this, then select this option. The timings may
1007 not be compliant with Intel's recommended values. Use at your own
1010 If you say N, the driver will revert to discrete video timings
1011 using a set recommended by Intel in their documentation.
1016 bool "Enable DDC Support"
1017 depends on FB_I810 && FB_I810_GTF
1020 Add DDC/I2C support for i810fb. This will allow the driver to get
1021 display information, especially for monitors with fickle timings.
1026 tristate "Intel LE80578 (Vermilion) support"
1027 depends on FB && PCI && X86
1028 select FB_MODE_HELPERS
1029 select FB_CFB_FILLRECT
1030 select FB_CFB_COPYAREA
1031 select FB_CFB_IMAGEBLIT
1033 This driver supports the LE80578 (Vermilion Range) chipset
1035 config FB_CARILLO_RANCH
1036 tristate "Intel Carillo Ranch support"
1037 depends on FB_LE80578 && FB && PCI && X86
1039 This driver supports the LE80578 (Carillo Ranch) board
1042 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1043 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1044 select FB_MODE_HELPERS
1045 select FB_CFB_FILLRECT
1046 select FB_CFB_COPYAREA
1047 select FB_CFB_IMAGEBLIT
1048 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1049 depends on !DRM_I915
1051 This driver supports the on-board graphics built in to the Intel
1052 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1053 Say Y if you have and plan to use such a board.
1055 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
1057 To compile this driver as a module, choose M here: the
1058 module will be called intelfb.
1060 For more information, please read <file:Documentation/fb/intelfb.rst>
1062 config FB_INTEL_DEBUG
1063 bool "Intel driver Debug Messages"
1066 Say Y here if you want the Intel driver to output all sorts
1067 of debugging information to provide to the maintainer when
1068 something goes wrong.
1071 bool "DDC/I2C for Intel framebuffer support"
1076 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1079 tristate "Matrox acceleration"
1080 depends on FB && PCI
1081 select FB_CFB_FILLRECT
1082 select FB_CFB_COPYAREA
1083 select FB_CFB_IMAGEBLIT
1084 select FB_TILEBLITTING
1085 select FB_MACMODES if PPC_PMAC
1087 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1088 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1089 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1090 Matrox G400, G450 or G550 card in your box.
1092 To compile this driver as a module, choose M here: the
1093 module will be called matroxfb.
1095 You can pass several parameters to the driver at boot time or at
1096 module load time. The parameters look like "video=matroxfb:XXX", and
1097 are described in <file:Documentation/fb/matroxfb.rst>.
1099 config FB_MATROX_MILLENIUM
1100 bool "Millennium I/II support"
1101 depends on FB_MATROX
1103 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1104 video card. If you select "Advanced lowlevel driver options" below,
1105 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1106 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1107 also use font widths different from 8.
1109 config FB_MATROX_MYSTIQUE
1110 bool "Mystique support"
1111 depends on FB_MATROX
1113 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1114 video card. If you select "Advanced lowlevel driver options" below,
1115 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1116 packed pixel and 32 bpp packed pixel. You can also use font widths
1120 bool "G100/G200/G400/G450/G550 support"
1121 depends on FB_MATROX
1123 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1124 video card. If you select "Advanced lowlevel driver options", you
1125 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1126 pixel and 32 bpp packed pixel. You can also use font widths
1129 If you need support for G400 secondary head, you must say Y to
1130 "Matrox I2C support" and "G400 second head support" right below.
1131 G450/G550 secondary head and digital output are supported without
1134 The driver starts in monitor mode. You must use the matroxset tool
1135 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1136 swap primary and secondary head outputs, or to change output mode.
1137 Secondary head driver always start in 640x480 resolution and you
1138 must use fbset to change it.
1140 Do not forget that second head supports only 16 and 32 bpp
1141 packed pixels, so it is a good idea to compile them into the kernel
1142 too. You can use only some font widths, as the driver uses generic
1143 painting procedures (the secondary head does not use acceleration
1146 G450/G550 hardware can display TV picture only from secondary CRTC,
1147 and it performs no scaling, so picture must have 525 or 625 lines.
1149 config FB_MATROX_I2C
1150 tristate "Matrox I2C support"
1151 depends on FB_MATROX
1154 This drivers creates I2C buses which are needed for accessing the
1155 DDC (I2C) bus present on all Matroxes, an I2C bus which
1156 interconnects Matrox optional devices, like MGA-TVO on G200 and
1157 G400, and the secondary head DDC bus, present on G400 only.
1159 You can say Y or M here if you want to experiment with monitor
1160 detection code. You must say Y or M here if you want to use either
1161 second head of G400 or MGA-TVO on G200 or G400.
1163 If you compile it as module, it will create a module named
1166 config FB_MATROX_MAVEN
1167 tristate "G400 second head support"
1168 depends on FB_MATROX_G && FB_MATROX_I2C
1170 WARNING !!! This support does not work with G450 !!!
1172 Say Y or M here if you want to use a secondary head (meaning two
1173 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1174 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1175 secondary head output is blanked while you are in X. With XFree
1176 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1177 the fbdev driver on first head and the fbdev driver on second head.
1179 If you compile it as module, two modules are created,
1180 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1181 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1182 also load i2c-matroxfb to get it to run.
1184 The driver starts in monitor mode and you must use the matroxset
1186 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1187 PAL or NTSC or to swap primary and secondary head outputs.
1188 Secondary head driver also always start in 640x480 resolution, you
1189 must use fbset to change it.
1191 Also do not forget that second head supports only 16 and 32 bpp
1192 packed pixels, so it is a good idea to compile them into the kernel
1193 too. You can use only some font widths, as the driver uses generic
1194 painting procedures (the secondary head does not use acceleration
1198 tristate "ATI Radeon display support"
1199 depends on FB && PCI
1200 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1201 select FB_MODE_HELPERS
1202 select FB_CFB_FILLRECT
1203 select FB_CFB_COPYAREA
1204 select FB_CFB_IMAGEBLIT
1205 select FB_MACMODES if PPC
1207 Choose this option if you want to use an ATI Radeon graphics card as
1208 a framebuffer device. There are both PCI and AGP versions. You
1209 don't need to choose this to run the Radeon in plain VGA mode.
1211 There is a product page at
1212 http://products.amd.com/en-us/GraphicCardResult.aspx
1214 config FB_RADEON_I2C
1215 bool "DDC/I2C for ATI Radeon support"
1216 depends on FB_RADEON
1220 Say Y here if you want DDC/I2C support for your Radeon board.
1222 config FB_RADEON_BACKLIGHT
1223 bool "Support for backlight control"
1224 depends on FB_RADEON
1227 Say Y here if you want to control the backlight of your display.
1229 config FB_RADEON_DEBUG
1230 bool "Lots of debug output from Radeon driver"
1231 depends on FB_RADEON
1233 Say Y here if you want the Radeon driver to output all sorts
1234 of debugging information to provide to the maintainer when
1235 something goes wrong.
1238 tristate "ATI Rage128 display support"
1239 depends on FB && PCI
1240 select FB_CFB_FILLRECT
1241 select FB_CFB_COPYAREA
1242 select FB_CFB_IMAGEBLIT
1243 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1244 select FB_MACMODES if PPC_PMAC
1246 This driver supports graphics boards with the ATI Rage128 chips.
1247 Say Y if you have such a graphics board and read
1248 <file:Documentation/fb/aty128fb.rst>.
1250 To compile this driver as a module, choose M here: the
1251 module will be called aty128fb.
1253 config FB_ATY128_BACKLIGHT
1254 bool "Support for backlight control"
1255 depends on FB_ATY128
1258 Say Y here if you want to control the backlight of your display.
1261 tristate "ATI Mach64 display support" if PCI || ATARI
1262 depends on FB && !SPARC32
1263 select FB_CFB_FILLRECT
1264 select FB_CFB_COPYAREA
1265 select FB_CFB_IMAGEBLIT
1266 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1267 select FB_MACMODES if PPC
1269 This driver supports graphics boards with the ATI Mach64 chips.
1270 Say Y if you have such a graphics board.
1272 To compile this driver as a module, choose M here: the
1273 module will be called atyfb.
1276 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1277 depends on PCI && FB_ATY
1278 default y if SPARC64 && PCI
1280 Say Y here to support use of ATI's 64-bit Rage boards (or other
1281 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1282 framebuffer device. The ATI product support page for these boards
1283 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1285 config FB_ATY_GENERIC_LCD
1286 bool "Mach64 generic LCD support"
1287 depends on FB_ATY_CT
1289 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1290 Rage XC, or Rage XL chipset.
1293 bool "Mach64 GX support" if PCI
1297 Say Y here to support use of the ATI Mach64 Graphics Expression
1298 board (or other boards based on the Mach64 GX chipset) as a
1299 framebuffer device. The ATI product support page for these boards
1301 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1303 config FB_ATY_BACKLIGHT
1304 bool "Support for backlight control"
1308 Say Y here if you want to control the backlight of your display.
1311 tristate "S3 Trio/Virge support"
1312 depends on FB && PCI
1313 select FB_CFB_FILLRECT
1314 select FB_CFB_COPYAREA
1315 select FB_CFB_IMAGEBLIT
1316 select FB_TILEBLITTING
1319 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1321 Driver for graphics boards with S3 Trio / S3 Virge chip.
1324 bool "DDC for S3 support"
1329 Say Y here if you want DDC support for your S3 graphics card.
1332 tristate "S3 Savage support"
1333 depends on FB && PCI
1334 select FB_MODE_HELPERS
1335 select FB_CFB_FILLRECT
1336 select FB_CFB_COPYAREA
1337 select FB_CFB_IMAGEBLIT
1340 This driver supports notebooks and computers with S3 Savage PCI/AGP
1343 Say Y if you have such a graphics card.
1345 To compile this driver as a module, choose M here; the module
1346 will be called savagefb.
1348 config FB_SAVAGE_I2C
1349 bool "Enable DDC2 Support"
1350 depends on FB_SAVAGE
1353 This enables I2C support for S3 Savage Chipsets. This is used
1354 only for getting EDID information from the attached display
1355 allowing for robust video mode handling and switching.
1357 Because fbdev-2.6 requires that drivers must be able to
1358 independently validate video mode parameters, you should say Y
1361 config FB_SAVAGE_ACCEL
1362 bool "Enable Console Acceleration"
1363 depends on FB_SAVAGE
1365 This option will compile in console acceleration support. If
1366 the resulting framebuffer console has bothersome glitches, then
1370 tristate "SiS/XGI display support"
1371 depends on FB && PCI
1372 select FB_CFB_FILLRECT
1373 select FB_CFB_COPYAREA
1374 select FB_CFB_IMAGEBLIT
1375 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1376 select FB_SIS_300 if !FB_SIS_315
1378 This is the frame buffer device driver for the SiS 300, 315, 330
1379 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1380 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1382 To compile this driver as a module, choose M here; the module
1383 will be called sisfb.
1386 bool "SiS 300 series support"
1389 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1392 bool "SiS 315/330/340 series and XGI support"
1395 Say Y here to support use of the SiS 315, 330 and 340 series
1396 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1397 as XGI V3XT, V5, V8 and Z7.
1400 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1401 depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST)
1402 select FB_CFB_FILLRECT
1403 select FB_CFB_COPYAREA
1404 select FB_CFB_IMAGEBLIT
1407 This is the frame buffer device driver for Graphics chips of VIA
1408 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1409 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1411 Say Y if you have a VIA UniChrome graphics board.
1413 To compile this driver as a module, choose M here: the
1414 module will be called viafb.
1418 config FB_VIA_DIRECT_PROCFS
1419 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1421 Allow direct hardware access to some output registers via procfs.
1422 This is dangerous but may provide the only chance to get the
1423 correct output device configuration.
1424 Its use is strongly discouraged.
1426 config FB_VIA_X_COMPATIBILITY
1427 bool "X server compatibility"
1429 This option reduces the functionality (power saving, ...) of the
1430 framebuffer to avoid negative impact on the OpenChrome X server.
1431 If you use any X server other than fbdev you should enable this
1432 otherwise it should be safe to disable it and allow using all
1438 tristate "NeoMagic display support"
1439 depends on FB && PCI
1440 select FB_MODE_HELPERS
1441 select FB_CFB_FILLRECT
1442 select FB_CFB_COPYAREA
1443 select FB_CFB_IMAGEBLIT
1446 This driver supports notebooks with NeoMagic PCI chips.
1447 Say Y if you have such a graphics card.
1449 To compile this driver as a module, choose M here: the
1450 module will be called neofb.
1453 tristate "IMG Kyro support"
1454 depends on FB && PCI
1455 select FB_CFB_FILLRECT
1456 select FB_CFB_COPYAREA
1457 select FB_CFB_IMAGEBLIT
1459 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1462 To compile this driver as a module, choose M here: the
1463 module will be called kyrofb.
1466 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1467 depends on FB && PCI
1468 select FB_CFB_IMAGEBLIT
1469 select FB_CFB_FILLRECT
1470 select FB_CFB_COPYAREA
1471 select FB_MODE_HELPERS
1473 This driver supports graphics boards with the 3Dfx Banshee,
1474 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1475 such a graphics board.
1477 To compile this driver as a module, choose M here: the
1478 module will be called tdfxfb.
1480 config FB_3DFX_ACCEL
1481 bool "3Dfx Acceleration functions"
1484 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1485 device driver with acceleration functions.
1488 bool "Enable DDC/I2C support"
1493 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1496 tristate "3Dfx Voodoo Graphics (sst1) support"
1497 depends on FB && PCI
1498 select FB_CFB_FILLRECT
1499 select FB_CFB_COPYAREA
1500 select FB_CFB_IMAGEBLIT
1502 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1503 Voodoo2 (cvg) based graphics card.
1505 To compile this driver as a module, choose M here: the
1506 module will be called sstfb.
1508 WARNING: Do not use any application that uses the 3D engine
1509 (namely glide) while using this driver.
1510 Please read the <file:Documentation/fb/sstfb.rst> for supported
1511 options and other important info support.
1514 tristate "VIA VT8623 support"
1515 depends on FB && PCI
1516 select FB_CFB_FILLRECT
1517 select FB_CFB_COPYAREA
1518 select FB_CFB_IMAGEBLIT
1519 select FB_TILEBLITTING
1522 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1524 Driver for CastleRock integrated graphics core in the
1525 VIA VT8623 [Apollo CLE266] chipset.
1528 tristate "Trident/CyberXXX/CyberBlade support"
1529 depends on FB && PCI
1530 select FB_CFB_FILLRECT
1531 select FB_CFB_COPYAREA
1532 select FB_CFB_IMAGEBLIT
1534 select FB_MODE_HELPERS
1536 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1537 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1539 There are also integrated versions of these chips called CyberXXXX,
1540 CyberImage or CyberBlade. These chips are mostly found in laptops
1541 but also on some motherboards including early VIA EPIA motherboards.
1542 For more information, read <file:Documentation/fb/tridentfb.rst>
1544 Say Y if you have such a graphics board.
1546 To compile this driver as a module, choose M here: the
1547 module will be called tridentfb.
1550 tristate "ARK 2000PV support"
1551 depends on FB && PCI
1552 select FB_CFB_FILLRECT
1553 select FB_CFB_COPYAREA
1554 select FB_CFB_IMAGEBLIT
1555 select FB_TILEBLITTING
1558 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1560 Driver for PCI graphics boards with ARK 2000PV chip
1561 and ICS 5342 RAMDAC.
1564 tristate "Permedia3 support"
1565 depends on FB && PCI
1566 select FB_CFB_FILLRECT
1567 select FB_CFB_COPYAREA
1568 select FB_CFB_IMAGEBLIT
1570 This is the frame buffer device driver for the 3DLabs Permedia3
1571 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1572 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1573 and maybe other boards.
1576 tristate "Fujitsu carmine frame buffer support"
1577 depends on FB && PCI
1578 select FB_CFB_FILLRECT
1579 select FB_CFB_COPYAREA
1580 select FB_CFB_IMAGEBLIT
1582 This is the frame buffer device driver for the Fujitsu Carmine chip.
1583 The driver provides two independent frame buffer devices.
1586 depends on FB_CARMINE
1587 prompt "DRAM timing"
1588 default FB_CARMINE_DRAM_EVAL
1590 config FB_CARMINE_DRAM_EVAL
1591 bool "Eval board timings"
1593 Use timings which work on the eval card.
1595 config CARMINE_DRAM_CUSTOM
1596 bool "Custom board timings"
1598 Use custom board timings.
1602 bool "Au1100 LCD Driver"
1603 depends on (FB = y) && MIPS_ALCHEMY
1604 select FB_CFB_FILLRECT
1605 select FB_CFB_COPYAREA
1606 select FB_CFB_IMAGEBLIT
1608 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1609 various panels and CRTs by passing in kernel cmd line option
1610 au1100fb:panel=<name>.
1613 bool "Au1200/Au1300 LCD Driver"
1614 depends on (FB = y) && MIPS_ALCHEMY
1615 select FB_SYS_FILLRECT
1616 select FB_SYS_COPYAREA
1617 select FB_SYS_IMAGEBLIT
1620 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1621 It can drive various panels and CRTs by passing in kernel cmd line
1622 option au1200fb:panel=<name>.
1625 bool "VIA VT8500 framebuffer support"
1626 depends on (FB = y) && ARM && ARCH_VT8500
1627 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1628 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1629 select FB_SYS_IMAGEBLIT
1630 select FB_MODE_HELPERS
1631 select VIDEOMODE_HELPERS
1633 This is the framebuffer driver for VIA VT8500 integrated LCD
1637 bool "Wondermedia WM8xxx-series frame buffer support"
1638 depends on (FB = y) && ARM && ARCH_VT8500
1639 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1640 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1641 select FB_SYS_IMAGEBLIT
1642 select FB_MODE_HELPERS
1643 select VIDEOMODE_HELPERS
1645 This is the framebuffer driver for WonderMedia WM8xxx-series
1646 integrated LCD controller. This driver covers the WM8505, WM8650
1649 config FB_WMT_GE_ROPS
1650 bool "VT8500/WM8xxx accelerated raster ops support"
1651 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1653 This adds support for accelerated raster operations on the
1654 VIA VT8500 and Wondermedia 85xx series SoCs.
1656 source "drivers/video/fbdev/geode/Kconfig"
1659 tristate "HD64461 Frame Buffer support"
1660 depends on FB && HD64461
1661 select FB_CFB_FILLRECT
1662 select FB_CFB_COPYAREA
1663 select FB_CFB_IMAGEBLIT
1665 This is the frame buffer device driver for the Hitachi HD64461 LCD
1669 tristate "PMAG-AA TURBOchannel framebuffer support"
1671 select FB_CFB_FILLRECT
1672 select FB_CFB_COPYAREA
1673 select FB_CFB_IMAGEBLIT
1675 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1676 used mainly in the MIPS-based DECstation series.
1679 tristate "PMAG-BA TURBOchannel framebuffer support"
1681 select FB_CFB_FILLRECT
1682 select FB_CFB_COPYAREA
1683 select FB_CFB_IMAGEBLIT
1685 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1686 used mainly in the MIPS-based DECstation series.
1689 tristate "PMAGB-B TURBOchannel framebuffer support"
1691 select FB_CFB_FILLRECT
1692 select FB_CFB_COPYAREA
1693 select FB_CFB_IMAGEBLIT
1695 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1696 in the MIPS-based DECstation series. The card is currently only
1697 supported in 1280x1024x8 mode.
1700 bool "Maxine (Personal DECstation) onboard framebuffer support"
1701 depends on (FB = y) && MACH_DECSTATION
1702 select FB_CFB_FILLRECT
1703 select FB_CFB_COPYAREA
1704 select FB_CFB_IMAGEBLIT
1706 Support for the onboard framebuffer (1024x768x8) in the Personal
1707 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1711 bool "G364 frame buffer support"
1712 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1718 Olivetti M700-10 systems.
1721 bool "Motorola 68328 native frame buffer support"
1722 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 Say Y here if you want to support the built-in frame buffer of
1728 the Motorola 68328 CPU family.
1731 tristate "PXA168/910 LCD framebuffer support"
1732 depends on FB && (CPU_PXA168 || CPU_PXA910)
1733 select FB_CFB_FILLRECT
1734 select FB_CFB_COPYAREA
1735 select FB_CFB_IMAGEBLIT
1737 Frame buffer driver for the built-in LCD controller in the Marvell
1741 tristate "PXA LCD framebuffer support"
1742 depends on FB && ARCH_PXA
1743 select FB_CFB_FILLRECT
1744 select FB_CFB_COPYAREA
1745 select FB_CFB_IMAGEBLIT
1746 select VIDEOMODE_HELPERS if OF
1747 select FB_MODE_HELPERS if OF
1749 Frame buffer driver for the built-in LCD controller in the Intel
1752 This driver is also available as a module ( = code which can be
1753 inserted and removed from the running kernel whenever you want). The
1754 module will be called pxafb. If you want to compile it as a module,
1755 say M here and read <file:Documentation/kbuild/modules.rst>.
1759 config FB_PXA_OVERLAY
1760 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1761 depends on FB_PXA && (PXA27x || PXA3xx)
1763 config FB_PXA_SMARTPANEL
1764 bool "PXA Smartpanel LCD support"
1767 config FB_PXA_PARAMETERS
1768 bool "PXA LCD command line parameters"
1771 Enable the use of kernel command line or module parameters
1772 to configure the physical properties of the LCD panel when
1773 using the PXA LCD driver.
1775 This option allows you to override the panel parameters
1776 supplied by the platform in order to support multiple
1777 different models of flatpanel. If you will only be using a
1778 single model of flatpanel then you can safely leave this
1781 <file:Documentation/fb/pxafb.rst> describes the available parameters.
1784 tristate "PXA3xx 2D graphics accelerator driver"
1787 Kernelspace driver for the 2D graphics controller unit (GCU)
1788 found on PXA3xx processors. There is a counterpart driver in the
1789 DirectFB suite, see http://www.directfb.org/
1791 If you compile this as a module, it will be called pxa3xx_gcu.
1794 tristate "2700G LCD framebuffer support"
1795 depends on FB && ARCH_PXA
1796 select FB_CFB_FILLRECT
1797 select FB_CFB_COPYAREA
1798 select FB_CFB_IMAGEBLIT
1800 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1804 bool "Enable debugging info via debugfs"
1805 depends on FB_MBX && DEBUG_FS
1807 Enable this if you want debugging information using the debug
1808 filesystem (debugfs)
1813 tristate "Freescale DIU framebuffer support"
1814 depends on FB && FSL_SOC
1815 select FB_MODE_HELPERS
1816 select FB_CFB_FILLRECT
1817 select FB_CFB_COPYAREA
1818 select FB_CFB_IMAGEBLIT
1819 select PPC_LIB_RHEAP
1821 Framebuffer driver for the Freescale SoC DIU
1824 tristate "W100 frame buffer support"
1825 depends on FB && ARCH_PXA
1826 select FB_CFB_FILLRECT
1827 select FB_CFB_COPYAREA
1828 select FB_CFB_IMAGEBLIT
1830 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1831 It can also drive the w3220 chip found on iPAQ hx4700.
1833 This driver is also available as a module ( = code which can be
1834 inserted and removed from the running kernel whenever you want). The
1835 module will be called w100fb. If you want to compile it as a module,
1836 say M here and read <file:Documentation/kbuild/modules.rst>.
1840 config FB_SH_MOBILE_LCDC
1841 tristate "SuperH Mobile LCDC framebuffer support"
1842 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1843 select FB_SYS_FILLRECT
1844 select FB_SYS_COPYAREA
1845 select FB_SYS_IMAGEBLIT
1847 select FB_DEFERRED_IO
1850 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1853 tristate "Toshiba Mobile IO FrameBuffer support"
1854 depends on FB && (MFD_TMIO || COMPILE_TEST)
1855 select FB_CFB_FILLRECT
1856 select FB_CFB_COPYAREA
1857 select FB_CFB_IMAGEBLIT
1859 Frame buffer driver for the Toshiba Mobile IO integrated as found
1860 on the Sharp SL-6000 series
1862 This driver is also available as a module ( = code which can be
1863 inserted and removed from the running kernel whenever you want). The
1864 module will be called tmiofb. If you want to compile it as a module,
1865 say M here and read <file:Documentation/kbuild/modules.rst>.
1869 config FB_TMIO_ACCELL
1870 bool "tmiofb acceleration"
1875 tristate "Samsung S3C framebuffer support"
1876 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX)
1877 select FB_CFB_FILLRECT
1878 select FB_CFB_COPYAREA
1879 select FB_CFB_IMAGEBLIT
1881 Frame buffer driver for the built-in FB controller in the Samsung
1882 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1883 and the S3C64XX series such as the S3C6400 and S3C6410.
1885 These chips all have the same basic framebuffer design with the
1886 actual capabilities depending on the chip. For instance the S3C6400
1887 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1888 currently only have two.
1890 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1892 config FB_S3C_DEBUG_REGWRITE
1893 bool "Debug register writes"
1896 Show all register writes via pr_debug()
1899 tristate "S3C2410 LCD framebuffer support"
1900 depends on FB && ARCH_S3C24XX
1901 select FB_CFB_FILLRECT
1902 select FB_CFB_COPYAREA
1903 select FB_CFB_IMAGEBLIT
1905 Frame buffer driver for the built-in LCD controller in the Samsung
1908 This driver is also available as a module ( = code which can be
1909 inserted and removed from the running kernel whenever you want). The
1910 module will be called s3c2410fb. If you want to compile it as a module,
1911 say M here and read <file:Documentation/kbuild/modules.rst>.
1914 config FB_S3C2410_DEBUG
1915 bool "S3C2410 lcd debug messages"
1916 depends on FB_S3C2410
1918 Turn on debugging messages. Note that you can set/unset at run time
1922 tristate "NUC900 LCD framebuffer support"
1923 depends on FB && ARCH_W90X900
1924 select FB_CFB_FILLRECT
1925 select FB_CFB_COPYAREA
1926 select FB_CFB_IMAGEBLIT
1928 Frame buffer driver for the built-in LCD controller in the Nuvoton
1931 config GPM1040A0_320X240
1932 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
1933 depends on FB_NUC900
1936 tristate "Silicon Motion SM501 framebuffer support"
1937 depends on FB && MFD_SM501
1938 select FB_CFB_FILLRECT
1939 select FB_CFB_COPYAREA
1940 select FB_CFB_IMAGEBLIT
1942 Frame buffer driver for the CRT and LCD controllers in the Silicon
1945 This driver is also available as a module ( = code which can be
1946 inserted and removed from the running kernel whenever you want). The
1947 module will be called sm501fb. If you want to compile it as a module,
1948 say M here and read <file:Documentation/kbuild/modules.rst>.
1953 tristate "SMSC UFX6000/7000 USB Framebuffer support"
1954 depends on FB && USB
1955 select FB_MODE_HELPERS
1956 select FB_SYS_FILLRECT
1957 select FB_SYS_COPYAREA
1958 select FB_SYS_IMAGEBLIT
1960 select FB_DEFERRED_IO
1962 This is a kernel framebuffer driver for SMSC UFX USB devices.
1963 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1964 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1966 To compile as a module, choose M here: the module name is smscufx.
1969 tristate "Displaylink USB Framebuffer support"
1970 depends on FB && USB
1971 select FB_MODE_HELPERS
1972 select FB_SYS_FILLRECT
1973 select FB_SYS_COPYAREA
1974 select FB_SYS_IMAGEBLIT
1976 select FB_DEFERRED_IO
1978 This is a kernel framebuffer driver for DisplayLink USB devices.
1979 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1980 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1981 To compile as a module, choose M here: the module name is udlfb.
1983 config FB_IBM_GXT4500
1984 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
1986 select FB_CFB_FILLRECT
1987 select FB_CFB_COPYAREA
1988 select FB_CFB_IMAGEBLIT
1990 Say Y here to enable support for the IBM GXT4000P/6000P and
1991 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
1992 found on some IBM System P (pSeries) machines. This driver
1993 doesn't use Geometry Engine GT1000. This driver also supports
1994 AGP Fire GL2/3/4 cards on x86.
1997 tristate "PS3 GPU framebuffer driver"
1998 depends on FB && PS3_PS3AV
1999 select FB_SYS_FILLRECT
2000 select FB_SYS_COPYAREA
2001 select FB_SYS_IMAGEBLIT
2004 Include support for the virtual frame buffer in the PS3 platform.
2006 config FB_PS3_DEFAULT_SIZE_M
2007 int "PS3 default frame buffer size (in MiB)"
2011 This is the default size (in MiB) of the virtual frame buffer in
2013 The default value can be overridden on the kernel command line
2014 using the "ps3fb" option (e.g. "ps3fb=9M");
2017 tristate "Xilinx frame buffer support"
2018 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
2019 select FB_CFB_FILLRECT
2020 select FB_CFB_COPYAREA
2021 select FB_CFB_IMAGEBLIT
2023 Include support for the Xilinx ML300/ML403 reference design
2024 framebuffer. ML300 carries a 640*480 LCD display on the board,
2025 ML403 uses a standard DB15 VGA connector.
2028 tristate "Goldfish Framebuffer"
2030 depends on GOLDFISH || COMPILE_TEST
2031 select FB_CFB_FILLRECT
2032 select FB_CFB_COPYAREA
2033 select FB_CFB_IMAGEBLIT
2035 Framebuffer driver for Goldfish Virtual Platform
2038 tristate "Cobalt server LCD frame buffer support"
2039 depends on FB && MIPS_COBALT
2042 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2043 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2044 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2045 select FB_CFB_FILLRECT
2046 select FB_CFB_COPYAREA
2047 select FB_CFB_IMAGEBLIT
2049 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2050 (D)STN/TFT LCD Controller.
2051 Supports display resolutions up to 1024x1024 pixel, grayscale and
2052 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2053 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2054 panels <= 320 pixel horizontal resolution.
2057 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2058 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2059 select FB_CFB_FILLRECT
2060 select FB_CFB_COPYAREA
2061 select FB_CFB_IMAGEBLIT
2062 select FB_CFB_REV_PIXELS_IN_BYTE
2063 select FB_MODE_HELPERS
2064 select VIDEOMODE_HELPERS
2066 This is the frame buffer device driver for the TI LCD controller
2067 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2071 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2073 select FB_SYS_FILLRECT
2074 select FB_SYS_COPYAREA
2075 select FB_SYS_IMAGEBLIT
2078 This is a `virtual' frame buffer device. It operates on a chunk of
2079 unswappable kernel memory instead of on the memory of a graphics
2080 board. This means you cannot see any output sent to this frame
2081 buffer device, while it does consume precious memory. The main use
2082 of this frame buffer device is testing and debugging the frame
2083 buffer subsystem. Do NOT enable it for normal systems! To protect
2084 the innocent, it has to be enabled explicitly at boot time using the
2085 kernel option `video=vfb:'.
2087 To compile this driver as a module, choose M here: the
2088 module will be called vfb. In order to load it, you must use
2089 the vfb_enable=1 option.
2093 config XEN_FBDEV_FRONTEND
2094 tristate "Xen virtual frame buffer support"
2095 depends on FB && XEN
2096 select FB_SYS_FILLRECT
2097 select FB_SYS_COPYAREA
2098 select FB_SYS_IMAGEBLIT
2100 select FB_DEFERRED_IO
2101 select XEN_XENBUS_FRONTEND
2104 This driver implements the front-end of the Xen virtual
2105 frame buffer driver. It communicates with a back-end
2109 tristate "E-Ink Metronome/8track controller support"
2111 select FB_SYS_FILLRECT
2112 select FB_SYS_COPYAREA
2113 select FB_SYS_IMAGEBLIT
2115 select FB_DEFERRED_IO
2117 This driver implements support for the E-Ink Metronome
2118 controller. The pre-release name for this device was 8track
2119 and could also have been called by some vendors as PVI-nnnn.
2122 tristate "Fujitsu MB862xx GDC support"
2124 depends on PCI || (OF && PPC)
2125 select FB_CFB_FILLRECT
2126 select FB_CFB_COPYAREA
2127 select FB_CFB_IMAGEBLIT
2129 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2132 prompt "GDC variant"
2133 depends on FB_MB862XX
2135 config FB_MB862XX_PCI_GDC
2136 bool "Carmine/Coral-P(A) GDC"
2139 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2140 PCI graphics controller devices.
2142 config FB_MB862XX_LIME
2144 depends on OF && PPC
2145 select FB_FOREIGN_ENDIAN
2146 select FB_LITTLE_ENDIAN
2148 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2152 config FB_MB862XX_I2C
2153 bool "Support I2C bus on MB862XX GDC"
2154 depends on FB_MB862XX && I2C
2155 depends on FB_MB862XX=m || I2C=y
2158 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2159 driver to support accessing I2C devices on controller's I2C bus.
2160 These are usually some video decoder chips.
2163 tristate "EP93XX frame buffer support"
2164 depends on FB && ARCH_EP93XX
2165 select FB_CFB_FILLRECT
2166 select FB_CFB_COPYAREA
2167 select FB_CFB_IMAGEBLIT
2169 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2170 This driver is also available as a module. The module will be called
2173 config FB_PRE_INIT_FB
2174 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2175 depends on FB && (FB_MB862XX_LIME || FB_MXS)
2177 Select this option if display contents should be inherited as set by
2181 tristate "MX3 Framebuffer support"
2182 depends on FB && MX3_IPU
2183 select BACKLIGHT_CLASS_DEVICE
2184 select FB_CFB_FILLRECT
2185 select FB_CFB_COPYAREA
2186 select FB_CFB_IMAGEBLIT
2189 This is a framebuffer device for the i.MX31 LCD Controller. So
2190 far only synchronous displays are supported. If you plan to use
2191 an LCD display with your i.MX31 system, say Y here.
2193 config FB_BROADSHEET
2194 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2195 depends on FB && (ARCH_PXA || COMPILE_TEST)
2196 select FB_SYS_FILLRECT
2197 select FB_SYS_COPYAREA
2198 select FB_SYS_IMAGEBLIT
2200 select FB_DEFERRED_IO
2202 This driver implements support for the E-Ink Broadsheet
2203 controller. The release name for this device was Epson S1D13521
2204 and could also have been called by other names when coupled with
2208 tristate "JZ4740 LCD framebuffer support"
2209 depends on FB && MACH_JZ4740
2210 select FB_SYS_FILLRECT
2211 select FB_SYS_COPYAREA
2212 select FB_SYS_IMAGEBLIT
2214 Framebuffer support for the JZ4740 SoC.
2217 tristate "MXS LCD framebuffer support"
2218 depends on FB && (ARCH_MXS || ARCH_MXC)
2219 select FB_CFB_FILLRECT
2220 select FB_CFB_COPYAREA
2221 select FB_CFB_IMAGEBLIT
2222 select FB_MODE_HELPERS
2223 select VIDEOMODE_HELPERS
2225 Framebuffer support for the MXS SoC.
2227 config FB_PUV3_UNIGFX
2228 tristate "PKUnity v3 Unigfx framebuffer support"
2229 depends on FB && UNICORE32 && ARCH_PUV3
2230 select FB_SYS_FILLRECT
2231 select FB_SYS_COPYAREA
2232 select FB_SYS_IMAGEBLIT
2235 Choose this option if you want to use the Unigfx device as a
2236 framebuffer device. Without the support of PCI & AGP.
2239 tristate "Microsoft Hyper-V Synthetic Video support"
2240 depends on FB && HYPERV
2241 select FB_CFB_FILLRECT
2242 select FB_CFB_COPYAREA
2243 select FB_CFB_IMAGEBLIT
2245 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2248 bool "Simple framebuffer support"
2250 select FB_CFB_FILLRECT
2251 select FB_CFB_COPYAREA
2252 select FB_CFB_IMAGEBLIT
2254 Say Y if you want support for a simple frame-buffer.
2256 This driver assumes that the display hardware has been initialized
2257 before the kernel boots, and the kernel will simply render to the
2258 pre-allocated frame buffer surface.
2260 Configuration re: surface address, size, and format must be provided
2261 through device tree, or plain old platform data.
2264 tristate "Solomon SSD1307 framebuffer support"
2265 depends on FB && I2C
2267 depends on GPIOLIB || COMPILE_TEST
2269 select FB_SYS_FILLRECT
2270 select FB_SYS_COPYAREA
2271 select FB_SYS_IMAGEBLIT
2272 select FB_DEFERRED_IO
2276 This driver implements support for the Solomon SSD1307
2277 OLED controller over I2C.
2280 tristate "Silicon Motion SM712 framebuffer support"
2281 depends on FB && PCI
2282 select FB_CFB_FILLRECT
2283 select FB_CFB_COPYAREA
2284 select FB_CFB_IMAGEBLIT
2286 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2289 This driver is also available as a module. The module will be
2290 called sm712fb. If you want to compile it as a module, say M
2291 here and read <file:Documentation/kbuild/modules.rst>.
2293 source "drivers/video/fbdev/omap/Kconfig"
2294 source "drivers/video/fbdev/omap2/Kconfig"
2295 source "drivers/video/fbdev/mmp/Kconfig"