6 tristate "Support for frame buffer devices"
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
42 bool "Enable firmware EDID"
46 This enables access to the EDID transferred from the firmware.
47 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
48 transfers do not work for your driver and if you are using
49 nvidiafb, i810fb or savagefb.
51 In general, choosing Y for this option is safe. If you
52 experience extremely long delays while booting before you get
53 something on your display, try setting this to N. Matrox cards in
54 combination with certain motherboards and monitors are known to
55 suffer from this problem.
70 config FB_BOOT_VESA_SUPPORT
75 If true, at least one selected framebuffer driver can take advantage
76 of VESA video modes set at an early boot stage via the vga= parameter.
78 config FB_CFB_FILLRECT
83 Include the cfb_fillrect function for generic software rectangle
84 filling. This is used by drivers that don't provide their own
85 (accelerated) version.
87 config FB_CFB_COPYAREA
92 Include the cfb_copyarea function for generic software area copying.
93 This is used by drivers that don't provide their own (accelerated)
96 config FB_CFB_IMAGEBLIT
101 Include the cfb_imageblit function for generic software image
102 blitting. This is used by drivers that don't provide their own
103 (accelerated) version.
105 config FB_CFB_REV_PIXELS_IN_BYTE
110 Allow generic frame-buffer functions to work on displays with 1, 2
111 and 4 bits per pixel depths which has opposite order of pixels in
112 byte order to bytes in long order.
114 config FB_SYS_FILLRECT
119 Include the sys_fillrect function for generic software rectangle
120 filling. This is used by drivers that don't provide their own
121 (accelerated) version and the framebuffer is in system RAM.
123 config FB_SYS_COPYAREA
128 Include the sys_copyarea function for generic software area copying.
129 This is used by drivers that don't provide their own (accelerated)
130 version and the framebuffer is in system RAM.
132 config FB_SYS_IMAGEBLIT
137 Include the sys_imageblit function for generic software image
138 blitting. This is used by drivers that don't provide their own
139 (accelerated) version and the framebuffer is in system RAM.
141 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
146 Allow generic frame-buffer to provide get_fb_unmapped_area
149 menuconfig FB_FOREIGN_ENDIAN
150 bool "Framebuffer foreign endianness support"
153 This menu will let you enable support for the framebuffers with
154 non-native endianness (e.g. Little-Endian framebuffer on a
155 Big-Endian machine). Most probably you don't have such hardware,
156 so it's safe to say "n" here.
159 prompt "Choice endianness support"
160 depends on FB_FOREIGN_ENDIAN
162 config FB_BOTH_ENDIAN
163 bool "Support for Big- and Little-Endian framebuffers"
166 bool "Support for Big-Endian framebuffers only"
168 config FB_LITTLE_ENDIAN
169 bool "Support for Little-Endian framebuffers only"
178 config FB_DEFERRED_IO
185 depends on FB_DEFERRED_IO
192 Common utility functions useful to fbdev drivers of VGA-based
203 select BACKLIGHT_LCD_SUPPORT
204 select BACKLIGHT_CLASS_DEVICE
207 config FB_MODE_HELPERS
208 bool "Enable Video Mode Handling Helpers"
212 This enables functions for handling video modes using the
213 Generalized Timing Formula and the EDID parser. A few drivers rely
214 on this feature such as the radeonfb, rivafb, and the i810fb. If
215 your driver does not take advantage of this feature, choosing Y will
216 just increase the kernel size by about 5K.
218 config FB_TILEBLITTING
219 bool "Enable Tile Blitting Support"
223 This enables tile blitting. Tile blitting is a drawing technique
224 where the screen is divided into rectangular sections (tiles), whereas
225 the standard blitting divides the screen into pixels. Because the
226 default drawing element is a tile, drawing functions will be passed
227 parameters in terms of number of tiles instead of number of pixels.
228 For example, to draw a single character, instead of using bitmaps,
229 an index to an array of bitmaps will be used. To clear or move a
230 rectangular section of a screen, the rectangle will be described in
231 terms of number of tiles in the x- and y-axis.
233 This is particularly important to one driver, matroxfb. If
236 comment "Frame buffer hardware drivers"
240 tristate "Aeroflex Gaisler framebuffer support"
241 depends on FB && SPARC
242 select FB_CFB_FILLRECT
243 select FB_CFB_COPYAREA
244 select FB_CFB_IMAGEBLIT
246 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
249 tristate "Cirrus Logic support"
250 depends on FB && (ZORRO || PCI)
251 select FB_CFB_FILLRECT
252 select FB_CFB_COPYAREA
253 select FB_CFB_IMAGEBLIT
255 This enables support for Cirrus Logic GD542x/543x based boards on
256 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
258 If you have a PCI-based system, this enables support for these
259 chips: GD-543x, GD-544x, GD-5480.
261 Please read the file <file:Documentation/fb/cirrusfb.txt>.
263 Say N unless you have such a graphics board or plan to get one
264 before you next recompile the kernel.
267 tristate "Permedia2 support"
268 depends on FB && ((AMIGA && BROKEN) || PCI)
269 select FB_CFB_FILLRECT
270 select FB_CFB_COPYAREA
271 select FB_CFB_IMAGEBLIT
273 This is the frame buffer device driver for cards based on
274 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
275 The driver was tested on the following cards:
276 Diamond FireGL 1000 PRO AGP
277 ELSA Gloria Synergy PCI
278 Appian Jeronimo PRO (both heads) PCI
279 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
280 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
281 ASK Graphic Blaster Exxtreme AGP
283 To compile this driver as a module, choose M here: the
284 module will be called pm2fb.
286 config FB_PM2_FIFO_DISCONNECT
287 bool "enable FIFO disconnect feature"
288 depends on FB_PM2 && PCI
290 Support the Permedia2 FIFO disconnect feature.
293 tristate "ARM PrimeCell PL110 support"
294 depends on ARM || ARM64 || COMPILE_TEST
295 depends on FB && ARM_AMBA && HAS_IOMEM
296 select FB_CFB_FILLRECT
297 select FB_CFB_COPYAREA
298 select FB_CFB_IMAGEBLIT
299 select FB_MODE_HELPERS if OF
300 select VIDEOMODE_HELPERS if OF
301 select BACKLIGHT_LCD_SUPPORT if OF
302 select BACKLIGHT_CLASS_DEVICE if OF
304 This framebuffer device driver is for the ARM PrimeCell PL110
305 Colour LCD controller. ARM PrimeCells provide the building
306 blocks for System on a Chip devices.
308 If you want to compile this as a module (=code which can be
309 inserted into and removed from the running kernel), say M
310 here and read <file:Documentation/kbuild/modules.txt>. The module
311 will be called amba-clcd.
313 # Helper logic selected only by the ARM Versatile platform family.
314 config PLAT_VERSATILE_CLCD
315 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
317 depends on FB_ARMCLCD && FB=y
322 bool "Acorn VIDC support"
323 depends on (FB = y) && ARM && ARCH_ACORN
324 select FB_CFB_FILLRECT
325 select FB_CFB_COPYAREA
326 select FB_CFB_IMAGEBLIT
328 This is the frame buffer device driver for the Acorn VIDC graphics
329 hardware found in Acorn RISC PCs and other ARM-based machines. If
332 config FB_CLPS711X_OLD
334 select FB_CFB_FILLRECT
335 select FB_CFB_COPYAREA
336 select FB_CFB_IMAGEBLIT
339 tristate "CLPS711X LCD support"
340 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
341 select FB_CLPS711X_OLD if ARCH_CLPS711X && !ARCH_MULTIPLATFORM
342 select BACKLIGHT_LCD_SUPPORT
343 select FB_MODE_HELPERS
344 select FB_SYS_FILLRECT
345 select FB_SYS_COPYAREA
346 select FB_SYS_IMAGEBLIT
347 select LCD_CLASS_DEVICE
348 select VIDEOMODE_HELPERS
350 Say Y to enable the Framebuffer driver for the Cirrus Logic
354 bool "SA-1100 LCD support"
355 depends on (FB = y) && ARM && ARCH_SA1100
356 select FB_CFB_FILLRECT
357 select FB_CFB_COPYAREA
358 select FB_CFB_IMAGEBLIT
360 This is a framebuffer device for the SA-1100 LCD Controller.
361 See <http://www.linux-fbdev.org/> for information on framebuffer
364 If you plan to use the LCD display with your SA-1100 system, say
368 tristate "Freescale i.MX1/21/25/27 LCD support"
369 depends on FB && ARCH_MXC
370 select BACKLIGHT_LCD_SUPPORT
371 select LCD_CLASS_DEVICE
372 select FB_CFB_FILLRECT
373 select FB_CFB_COPYAREA
374 select FB_CFB_IMAGEBLIT
375 select FB_MODE_HELPERS
376 select VIDEOMODE_HELPERS
379 tristate "CyberPro 2000/2010/5000 support"
380 depends on FB && PCI && (BROKEN || !SPARC64)
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
385 This enables support for the Integraphics CyberPro 20x0 and 5000
386 VGA chips used in the Rebel.com Netwinder and other machines.
387 Say Y if you have a NetWinder or a graphics card containing this
388 device, otherwise say N.
390 config FB_CYBER2000_DDC
391 bool "DDC for CyberPro support"
392 depends on FB_CYBER2000
396 Say Y here if you want DDC support for your CyberPro graphics
397 card. This is only I2C bus support, driver does not use EDID.
399 config FB_CYBER2000_I2C
400 bool "CyberPro 2000/2010/5000 I2C support"
401 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
402 depends on I2C=y || FB_CYBER2000=m
405 Enable support for the I2C video decoder interface on the
406 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
407 on the Netwinder machines for the SAA7111 video capture.
411 depends on (FB = y) && APOLLO
413 select FB_CFB_FILLRECT
414 select FB_CFB_IMAGEBLIT
418 depends on (FB = y) && Q40
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
425 tristate "Amiga native chipset support"
426 depends on FB && AMIGA
428 This is the frame buffer device driver for the builtin graphics
429 chipset found in Amigas.
431 To compile this driver as a module, choose M here: the
432 module will be called amifb.
435 bool "Amiga OCS chipset support"
438 This enables support for the original Agnus and Denise video chips,
439 found in the Amiga 1000 and most A500's and A2000's. If you intend
440 to run Linux on any of these systems, say Y; otherwise say N.
443 bool "Amiga ECS chipset support"
446 This enables support for the Enhanced Chip Set, found in later
447 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
448 you intend to run Linux on any of these systems, say Y; otherwise
452 bool "Amiga AGA chipset support"
455 This enables support for the Advanced Graphics Architecture (also
456 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
457 and CD32. If you intend to run Linux on any of these systems, say Y;
461 bool "Amiga FrameMaster II/Rainbow II support"
462 depends on (FB = y) && ZORRO
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
467 This is the frame buffer device driver for the Amiga FrameMaster
468 card from BSC (exhibited 1992 but not shipped as a CBM product).
471 tristate "Arc Monochrome LCD board support"
473 select FB_SYS_FILLRECT
474 select FB_SYS_COPYAREA
475 select FB_SYS_IMAGEBLIT
478 This enables support for the Arc Monochrome LCD board. The board
479 is based on the KS-108 lcd controller and is typically a matrix
480 of 2*n chips. This driver was tested with a 128x64 panel. This
481 driver supports it for use with x86 SBCs through a 16 bit GPIO
482 interface (8 bit data, 8 bit control). If you anticipate using
483 this driver, say Y or M; otherwise say N. You must specify the
484 GPIO IO address to be used for setting control and data.
487 bool "Atari native chipset support"
488 depends on (FB = y) && ATARI
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the builtin graphics
494 chipset found in Ataris.
497 bool "Open Firmware frame buffer device support"
498 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 Say Y if you want support with Open Firmware for your graphics
508 bool "Apple \"control\" display support"
509 depends on (FB = y) && PPC_PMAC && PPC32
510 select FB_CFB_FILLRECT
511 select FB_CFB_COPYAREA
512 select FB_CFB_IMAGEBLIT
515 This driver supports a frame buffer for the graphics adapter in the
516 Power Macintosh 7300 and others.
519 bool "Apple \"platinum\" display support"
520 depends on (FB = y) && PPC_PMAC && PPC32
521 select FB_CFB_FILLRECT
522 select FB_CFB_COPYAREA
523 select FB_CFB_IMAGEBLIT
526 This driver supports a frame buffer for the "platinum" graphics
527 adapter in some Power Macintoshes.
530 bool "Apple \"valkyrie\" display support"
531 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
537 This driver supports a frame buffer for the "valkyrie" graphics
538 adapter in some Power Macintoshes.
541 bool "Chips 65550 display support"
542 depends on (FB = y) && PPC32 && PCI
543 select FB_CFB_FILLRECT
544 select FB_CFB_COPYAREA
545 select FB_CFB_IMAGEBLIT
547 This is the frame buffer device driver for the Chips & Technologies
548 65550 graphics chip in PowerBooks.
551 bool "Asiliant (Chips) 69000 display support"
552 depends on (FB = y) && PCI
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
557 This is the frame buffer device driver for the Asiliant 69030 chipset
560 bool "IMS Twin Turbo display support"
561 depends on (FB = y) && PCI
562 select FB_CFB_IMAGEBLIT
563 select FB_MACMODES if PPC
565 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
566 many Macintosh and compatible computers.
569 tristate "VGA 16-color graphics support"
570 depends on FB && (X86 || PPC)
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 select FONT_8x16 if FRAMEBUFFER_CONSOLE
577 This is the frame buffer device driver for VGA 16 color graphic
578 cards. Say Y if you have such a card.
580 To compile this driver as a module, choose M here: the
581 module will be called vga16fb.
584 tristate "HP STI frame buffer device support"
585 depends on FB && PARISC
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
591 STI refers to the HP "Standard Text Interface" which is a set of
592 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
593 Enabling this option will implement the linux framebuffer device
594 using calls to the STI BIOS routines for initialisation.
596 If you enable this option, you will get a planar framebuffer device
597 /dev/fb which will work on the most common HP graphic cards of the
598 NGLE family, including the artist chips (in the 7xx and Bxxx series),
599 HCRX, HCRX24, CRX, CRX24 and VisEG series.
601 It is safe to enable this option, so you should probably say "Y".
604 bool "Generic Macintosh display support"
605 depends on (FB = y) && MAC
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
613 depends on (FB = y) && DIO
614 select FB_CFB_IMAGEBLIT
618 tristate "TGA/SFB+ framebuffer support"
619 depends on FB && (ALPHA || TC)
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
625 This is the frame buffer device driver for generic TGA and SFB+
626 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
627 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
628 TURBOchannel cards, also known as PMAGD-A, -B and -C.
630 Due to hardware limitations ZLX-E2 and E3 cards are not supported
631 for DECstation 5000/200 systems. Additionally due to firmware
632 limitations these cards may cause troubles with booting DECstation
633 5000/240 and /260 systems, but are fully supported under Linux if
634 you manage to get it going. ;-)
636 Say Y if you have one of those.
639 tristate "Userspace VESA VGA graphics support"
640 depends on FB && CONNECTOR
641 select FB_CFB_FILLRECT
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
644 select FB_MODE_HELPERS
646 This is the frame buffer driver for generic VBE 2.0 compliant
647 graphic cards. It can also take advantage of VBE 3.0 features,
648 such as refresh rate adjustment.
650 This driver generally provides more features than vesafb but
651 requires a userspace helper application called 'v86d'. See
652 <file:Documentation/fb/uvesafb.txt> for more information.
657 bool "VESA VGA graphics support"
658 depends on (FB = y) && X86
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
662 select FB_BOOT_VESA_SUPPORT
664 This is the frame buffer device driver for generic VESA 2.0
665 compliant graphic cards. The older VESA 1.2 cards are not supported.
666 You will get a boot time penguin logo at no additional cost. Please
667 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
670 bool "EFI-based Framebuffer Support"
671 depends on (FB = y) && !IA64 && EFI
672 select DRM_PANEL_ORIENTATION_QUIRKS
673 select FB_CFB_FILLRECT
674 select FB_CFB_COPYAREA
675 select FB_CFB_IMAGEBLIT
677 This is the EFI frame buffer device driver. If the firmware on
678 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
679 using the EFI framebuffer as your console.
682 tristate "N411 Apollo/Hecuba devkit support"
683 depends on FB && X86 && MMU
684 select FB_SYS_FILLRECT
685 select FB_SYS_COPYAREA
686 select FB_SYS_IMAGEBLIT
688 select FB_DEFERRED_IO
691 This enables support for the Apollo display controller in its
692 Hecuba form using the n411 devkit.
695 tristate "Hercules mono graphics support"
698 Say Y here if you have a Hercules mono graphics card.
700 To compile this driver as a module, choose M here: the
701 module will be called hgafb.
703 As this card technology is at least 25 years old,
704 most people will answer N here.
707 bool "SGI Graphics Backend frame buffer support"
708 depends on (FB = y) && SGI_IP32
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
713 This is the frame buffer device driver for SGI Graphics Backend.
714 This chip is used in SGI O2 and Visual Workstation 320/540.
717 int "Video memory size in MB"
721 This is the amount of memory reserved for the framebuffer,
722 which can be any value between 1MB and 8MB.
725 bool "SBUS and UPA framebuffers"
726 depends on (FB = y) && SPARC
728 Say Y if you want support for SBUS or UPA based frame buffer device.
732 depends on (FB = y) && (SPARC && FB_SBUS)
733 select FB_CFB_FILLRECT
734 select FB_CFB_COPYAREA
735 select FB_CFB_IMAGEBLIT
737 This is the frame buffer device driver for the BWtwo frame buffer.
740 bool "CGthree support"
741 depends on (FB = y) && (SPARC && FB_SBUS)
742 select FB_CFB_FILLRECT
743 select FB_CFB_COPYAREA
744 select FB_CFB_IMAGEBLIT
746 This is the frame buffer device driver for the CGthree frame buffer.
749 bool "CGsix (GX,TurboGX) support"
750 depends on (FB = y) && (SPARC && FB_SBUS)
751 select FB_CFB_COPYAREA
752 select FB_CFB_IMAGEBLIT
754 This is the frame buffer device driver for the CGsix (GX, TurboGX)
758 bool "Creator/Creator3D/Elite3D support"
759 depends on FB_SBUS && SPARC64
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
763 This is the frame buffer device driver for the Creator, Creator3D,
764 and Elite3D graphics boards.
767 bool "TCX (SS4/SS5 only) support"
769 select FB_CFB_FILLRECT
770 select FB_CFB_COPYAREA
771 select FB_CFB_IMAGEBLIT
773 This is the frame buffer device driver for the TCX 24/8bit frame
777 bool "CGfourteen (SX) support"
779 select FB_CFB_FILLRECT
780 select FB_CFB_COPYAREA
781 select FB_CFB_IMAGEBLIT
783 This is the frame buffer device driver for the CGfourteen frame
784 buffer on Desktop SPARCsystems with the SX graphics option.
787 bool "P9100 (Sparcbook 3 only) support"
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
793 This is the frame buffer device driver for the P9100 card
794 supported on Sparcbook 3 machines.
797 bool "Leo (ZX) support"
799 select FB_CFB_FILLRECT
800 select FB_CFB_COPYAREA
801 select FB_CFB_IMAGEBLIT
803 This is the frame buffer device driver for the SBUS-based Sun ZX
804 (leo) frame buffer cards.
807 bool "Sun XVR-500 3DLABS Wildcat support"
808 depends on (FB = y) && PCI && SPARC64
809 select FB_CFB_FILLRECT
810 select FB_CFB_COPYAREA
811 select FB_CFB_IMAGEBLIT
813 This is the framebuffer device for the Sun XVR-500 and similar
814 graphics cards based upon the 3DLABS Wildcat chipset. The driver
815 only works on sparc64 systems where the system firmware has
816 mostly initialized the card already. It is treated as a
817 completely dumb framebuffer device.
820 bool "Sun XVR-2500 3DLABS Wildcat support"
821 depends on (FB = y) && PCI && SPARC64
822 select FB_CFB_FILLRECT
823 select FB_CFB_COPYAREA
824 select FB_CFB_IMAGEBLIT
826 This is the framebuffer device for the Sun XVR-2500 and similar
827 graphics cards based upon the 3DLABS Wildcat chipset. The driver
828 only works on sparc64 systems where the system firmware has
829 mostly initialized the card already. It is treated as a
830 completely dumb framebuffer device.
833 bool "Sun XVR-1000 support"
834 depends on (FB = y) && SPARC64
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
839 This is the framebuffer device for the Sun XVR-1000 and similar
840 graphics cards. The driver only works on sparc64 systems where
841 the system firmware has mostly initialized the card already. It
842 is treated as a completely dumb framebuffer device.
845 tristate "NEC PowerVR 2 display support"
846 depends on FB && SH_DREAMCAST
847 select FB_CFB_FILLRECT
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 Say Y here if you have a PowerVR 2 card in your box. If you plan to
852 run linux on your Dreamcast, you will have to say Y here.
853 This driver may or may not work on other PowerVR 2 cards, but is
854 totally untested. Use at your own risk. If unsure, say N.
856 To compile this driver as a module, choose M here: the
857 module will be called pvr2fb.
859 You can pass several parameters to the driver at boot time or at
860 module load time. The parameters look like "video=pvr2:XXX", where
861 the meaning of XXX can be found at the end of the main source file
862 (<file:drivers/video/pvr2fb.c>). Please see the file
863 <file:Documentation/fb/pvr2fb.txt>.
866 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
867 depends on FB && HAS_DMA
868 select FB_CFB_FILLRECT
869 select FB_CFB_COPYAREA
870 select FB_CFB_IMAGEBLIT
872 This enables support for the OpenCores VGA/LCD core.
874 The OpenCores VGA/LCD core is typically used together with
875 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
876 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
878 The source code and specification for the core is available at
879 <http://opencores.org/project,vga_lcd>
882 tristate "Epson S1D13XXX framebuffer support"
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 Support for S1D13XXX framebuffer device family (currently only
889 working with S1D13806). Product specs at
890 <http://vdc.epson.com/>
893 tristate "AT91/AT32 LCD Controller support"
894 depends on FB && HAVE_FB_ATMEL
896 select FB_CFB_FILLRECT
897 select FB_CFB_COPYAREA
898 select FB_CFB_IMAGEBLIT
899 select FB_MODE_HELPERS
900 select VIDEOMODE_HELPERS
902 This enables support for the AT91/AT32 LCD Controller.
905 tristate "nVidia Framebuffer Support"
907 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
908 select FB_MODE_HELPERS
909 select FB_CFB_FILLRECT
910 select FB_CFB_COPYAREA
911 select FB_CFB_IMAGEBLIT
915 This driver supports graphics boards with the nVidia chips, TNT
916 and newer. For very old chipsets, such as the RIVA128, then use
918 Say Y if you have such a graphics board.
920 To compile this driver as a module, choose M here: the
921 module will be called nvidiafb.
924 bool "Enable DDC Support"
928 This enables I2C support for nVidia Chipsets. This is used
929 only for getting EDID information from the attached display
930 allowing for robust video mode handling and switching.
932 Because fbdev-2.6 requires that drivers must be able to
933 independently validate video mode parameters, you should say Y
936 config FB_NVIDIA_DEBUG
937 bool "Lots of debug output"
941 Say Y here if you want the nVidia driver to output all sorts
942 of debugging information to provide to the maintainer when
943 something goes wrong.
945 config FB_NVIDIA_BACKLIGHT
946 bool "Support for backlight control"
950 Say Y here if you want to control the backlight of your display.
953 tristate "nVidia Riva support"
955 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
956 select FB_MODE_HELPERS
957 select FB_CFB_FILLRECT
958 select FB_CFB_COPYAREA
959 select FB_CFB_IMAGEBLIT
963 This driver supports graphics boards with the nVidia Riva/Geforce
965 Say Y if you have such a graphics board.
967 To compile this driver as a module, choose M here: the
968 module will be called rivafb.
971 bool "Enable DDC Support"
975 This enables I2C support for nVidia Chipsets. This is used
976 only for getting EDID information from the attached display
977 allowing for robust video mode handling and switching.
979 Because fbdev-2.6 requires that drivers must be able to
980 independently validate video mode parameters, you should say Y
984 bool "Lots of debug output"
988 Say Y here if you want the Riva driver to output all sorts
989 of debugging information to provide to the maintainer when
990 something goes wrong.
992 config FB_RIVA_BACKLIGHT
993 bool "Support for backlight control"
997 Say Y here if you want to control the backlight of your display.
1000 tristate "Intel740 support"
1001 depends on FB && PCI
1002 select FB_MODE_HELPERS
1003 select FB_CFB_FILLRECT
1004 select FB_CFB_COPYAREA
1005 select FB_CFB_IMAGEBLIT
1009 This driver supports graphics cards based on Intel740 chip.
1012 tristate "Intel 810/815 support"
1013 depends on FB && PCI && X86_32 && AGP_INTEL
1014 select FB_MODE_HELPERS
1015 select FB_CFB_FILLRECT
1016 select FB_CFB_COPYAREA
1017 select FB_CFB_IMAGEBLIT
1020 This driver supports the on-board graphics built in to the Intel 810
1021 and 815 chipsets. Say Y if you have and plan to use such a board.
1023 To compile this driver as a module, choose M here: the
1024 module will be called i810fb.
1026 For more information, please read
1027 <file:Documentation/fb/intel810.txt>
1030 bool "use VESA Generalized Timing Formula"
1033 If you say Y, then the VESA standard, Generalized Timing Formula
1034 or GTF, will be used to calculate the required video timing values
1035 per video mode. Since the GTF allows nondiscrete timings
1036 (nondiscrete being a range of values as opposed to discrete being a
1037 set of values), you'll be able to use any combination of horizontal
1038 and vertical resolutions, and vertical refresh rates without having
1039 to specify your own timing parameters. This is especially useful
1040 to maximize the performance of an aging display, or if you just
1041 have a display with nonstandard dimensions. A VESA compliant
1042 monitor is recommended, but can still work with non-compliant ones.
1043 If you need or want this, then select this option. The timings may
1044 not be compliant with Intel's recommended values. Use at your own
1047 If you say N, the driver will revert to discrete video timings
1048 using a set recommended by Intel in their documentation.
1053 bool "Enable DDC Support"
1054 depends on FB_I810 && FB_I810_GTF
1058 tristate "Intel LE80578 (Vermilion) support"
1059 depends on FB && PCI && X86
1060 select FB_MODE_HELPERS
1061 select FB_CFB_FILLRECT
1062 select FB_CFB_COPYAREA
1063 select FB_CFB_IMAGEBLIT
1065 This driver supports the LE80578 (Vermilion Range) chipset
1067 config FB_CARILLO_RANCH
1068 tristate "Intel Carillo Ranch support"
1069 depends on FB_LE80578 && FB && PCI && X86
1071 This driver supports the LE80578 (Carillo Ranch) board
1074 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1075 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1076 select FB_MODE_HELPERS
1077 select FB_CFB_FILLRECT
1078 select FB_CFB_COPYAREA
1079 select FB_CFB_IMAGEBLIT
1080 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1081 depends on !DRM_I915
1083 This driver supports the on-board graphics built in to the Intel
1084 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1085 Say Y if you have and plan to use such a board.
1087 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
1089 To compile this driver as a module, choose M here: the
1090 module will be called intelfb.
1092 For more information, please read <file:Documentation/fb/intelfb.txt>
1094 config FB_INTEL_DEBUG
1095 bool "Intel driver Debug Messages"
1098 Say Y here if you want the Intel driver to output all sorts
1099 of debugging information to provide to the maintainer when
1100 something goes wrong.
1103 bool "DDC/I2C for Intel framebuffer support"
1108 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1111 tristate "Matrox acceleration"
1112 depends on FB && PCI
1113 select FB_CFB_FILLRECT
1114 select FB_CFB_COPYAREA
1115 select FB_CFB_IMAGEBLIT
1116 select FB_TILEBLITTING
1117 select FB_MACMODES if PPC_PMAC
1119 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1120 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1121 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1122 Matrox G400, G450 or G550 card in your box.
1124 To compile this driver as a module, choose M here: the
1125 module will be called matroxfb.
1127 You can pass several parameters to the driver at boot time or at
1128 module load time. The parameters look like "video=matroxfb:XXX", and
1129 are described in <file:Documentation/fb/matroxfb.txt>.
1131 config FB_MATROX_MILLENIUM
1132 bool "Millennium I/II support"
1133 depends on FB_MATROX
1135 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1136 video card. If you select "Advanced lowlevel driver options" below,
1137 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1138 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1139 also use font widths different from 8.
1141 config FB_MATROX_MYSTIQUE
1142 bool "Mystique support"
1143 depends on FB_MATROX
1145 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1146 video card. If you select "Advanced lowlevel driver options" below,
1147 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1148 packed pixel and 32 bpp packed pixel. You can also use font widths
1152 bool "G100/G200/G400/G450/G550 support"
1153 depends on FB_MATROX
1155 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1156 video card. If you select "Advanced lowlevel driver options", you
1157 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1158 pixel and 32 bpp packed pixel. You can also use font widths
1161 If you need support for G400 secondary head, you must say Y to
1162 "Matrox I2C support" and "G400 second head support" right below.
1163 G450/G550 secondary head and digital output are supported without
1166 The driver starts in monitor mode. You must use the matroxset tool
1167 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1168 swap primary and secondary head outputs, or to change output mode.
1169 Secondary head driver always start in 640x480 resolution and you
1170 must use fbset to change it.
1172 Do not forget that second head supports only 16 and 32 bpp
1173 packed pixels, so it is a good idea to compile them into the kernel
1174 too. You can use only some font widths, as the driver uses generic
1175 painting procedures (the secondary head does not use acceleration
1178 G450/G550 hardware can display TV picture only from secondary CRTC,
1179 and it performs no scaling, so picture must have 525 or 625 lines.
1181 config FB_MATROX_I2C
1182 tristate "Matrox I2C support"
1183 depends on FB_MATROX
1186 This drivers creates I2C buses which are needed for accessing the
1187 DDC (I2C) bus present on all Matroxes, an I2C bus which
1188 interconnects Matrox optional devices, like MGA-TVO on G200 and
1189 G400, and the secondary head DDC bus, present on G400 only.
1191 You can say Y or M here if you want to experiment with monitor
1192 detection code. You must say Y or M here if you want to use either
1193 second head of G400 or MGA-TVO on G200 or G400.
1195 If you compile it as module, it will create a module named
1198 config FB_MATROX_MAVEN
1199 tristate "G400 second head support"
1200 depends on FB_MATROX_G && FB_MATROX_I2C
1202 WARNING !!! This support does not work with G450 !!!
1204 Say Y or M here if you want to use a secondary head (meaning two
1205 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1206 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1207 secondary head output is blanked while you are in X. With XFree
1208 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1209 the fbdev driver on first head and the fbdev driver on second head.
1211 If you compile it as module, two modules are created,
1212 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1213 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1214 also load i2c-matroxfb to get it to run.
1216 The driver starts in monitor mode and you must use the matroxset
1218 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1219 PAL or NTSC or to swap primary and secondary head outputs.
1220 Secondary head driver also always start in 640x480 resolution, you
1221 must use fbset to change it.
1223 Also do not forget that second head supports only 16 and 32 bpp
1224 packed pixels, so it is a good idea to compile them into the kernel
1225 too. You can use only some font widths, as the driver uses generic
1226 painting procedures (the secondary head does not use acceleration
1230 tristate "ATI Radeon display support"
1231 depends on FB && PCI
1232 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1233 select FB_MODE_HELPERS
1234 select FB_CFB_FILLRECT
1235 select FB_CFB_COPYAREA
1236 select FB_CFB_IMAGEBLIT
1237 select FB_MACMODES if PPC
1239 Choose this option if you want to use an ATI Radeon graphics card as
1240 a framebuffer device. There are both PCI and AGP versions. You
1241 don't need to choose this to run the Radeon in plain VGA mode.
1243 There is a product page at
1244 http://products.amd.com/en-us/GraphicCardResult.aspx
1246 config FB_RADEON_I2C
1247 bool "DDC/I2C for ATI Radeon support"
1248 depends on FB_RADEON
1252 Say Y here if you want DDC/I2C support for your Radeon board.
1254 config FB_RADEON_BACKLIGHT
1255 bool "Support for backlight control"
1256 depends on FB_RADEON
1259 Say Y here if you want to control the backlight of your display.
1261 config FB_RADEON_DEBUG
1262 bool "Lots of debug output from Radeon driver"
1263 depends on FB_RADEON
1266 Say Y here if you want the Radeon driver to output all sorts
1267 of debugging information to provide to the maintainer when
1268 something goes wrong.
1271 tristate "ATI Rage128 display support"
1272 depends on FB && PCI
1273 select FB_CFB_FILLRECT
1274 select FB_CFB_COPYAREA
1275 select FB_CFB_IMAGEBLIT
1276 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1277 select FB_MACMODES if PPC_PMAC
1279 This driver supports graphics boards with the ATI Rage128 chips.
1280 Say Y if you have such a graphics board and read
1281 <file:Documentation/fb/aty128fb.txt>.
1283 To compile this driver as a module, choose M here: the
1284 module will be called aty128fb.
1286 config FB_ATY128_BACKLIGHT
1287 bool "Support for backlight control"
1288 depends on FB_ATY128
1291 Say Y here if you want to control the backlight of your display.
1294 tristate "ATI Mach64 display support" if PCI || ATARI
1295 depends on FB && !SPARC32
1296 select FB_CFB_FILLRECT
1297 select FB_CFB_COPYAREA
1298 select FB_CFB_IMAGEBLIT
1299 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1300 select FB_MACMODES if PPC
1302 This driver supports graphics boards with the ATI Mach64 chips.
1303 Say Y if you have such a graphics board.
1305 To compile this driver as a module, choose M here: the
1306 module will be called atyfb.
1309 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1310 depends on PCI && FB_ATY
1311 default y if SPARC64 && PCI
1313 Say Y here to support use of ATI's 64-bit Rage boards (or other
1314 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1315 framebuffer device. The ATI product support page for these boards
1316 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1318 config FB_ATY_GENERIC_LCD
1319 bool "Mach64 generic LCD support"
1320 depends on FB_ATY_CT
1322 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1323 Rage XC, or Rage XL chipset.
1326 bool "Mach64 GX support" if PCI
1330 Say Y here to support use of the ATI Mach64 Graphics Expression
1331 board (or other boards based on the Mach64 GX chipset) as a
1332 framebuffer device. The ATI product support page for these boards
1334 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1336 config FB_ATY_BACKLIGHT
1337 bool "Support for backlight control"
1341 Say Y here if you want to control the backlight of your display.
1344 tristate "S3 Trio/Virge support"
1345 depends on FB && PCI
1346 select FB_CFB_FILLRECT
1347 select FB_CFB_COPYAREA
1348 select FB_CFB_IMAGEBLIT
1349 select FB_TILEBLITTING
1352 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1354 Driver for graphics boards with S3 Trio / S3 Virge chip.
1357 bool "DDC for S3 support"
1362 Say Y here if you want DDC support for your S3 graphics card.
1365 tristate "S3 Savage support"
1366 depends on FB && PCI
1367 select FB_MODE_HELPERS
1368 select FB_CFB_FILLRECT
1369 select FB_CFB_COPYAREA
1370 select FB_CFB_IMAGEBLIT
1373 This driver supports notebooks and computers with S3 Savage PCI/AGP
1376 Say Y if you have such a graphics card.
1378 To compile this driver as a module, choose M here; the module
1379 will be called savagefb.
1381 config FB_SAVAGE_I2C
1382 bool "Enable DDC2 Support"
1383 depends on FB_SAVAGE
1386 This enables I2C support for S3 Savage Chipsets. This is used
1387 only for getting EDID information from the attached display
1388 allowing for robust video mode handling and switching.
1390 Because fbdev-2.6 requires that drivers must be able to
1391 independently validate video mode parameters, you should say Y
1394 config FB_SAVAGE_ACCEL
1395 bool "Enable Console Acceleration"
1396 depends on FB_SAVAGE
1399 This option will compile in console acceleration support. If
1400 the resulting framebuffer console has bothersome glitches, then
1404 tristate "SiS/XGI display support"
1405 depends on FB && PCI
1406 select FB_CFB_FILLRECT
1407 select FB_CFB_COPYAREA
1408 select FB_CFB_IMAGEBLIT
1409 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1410 select FB_SIS_300 if !FB_SIS_315
1412 This is the frame buffer device driver for the SiS 300, 315, 330
1413 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1414 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1416 To compile this driver as a module, choose M here; the module
1417 will be called sisfb.
1420 bool "SiS 300 series support"
1423 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1426 bool "SiS 315/330/340 series and XGI support"
1429 Say Y here to support use of the SiS 315, 330 and 340 series
1430 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1431 as XGI V3XT, V5, V8 and Z7.
1434 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1435 depends on FB && PCI && X86 && GPIOLIB && I2C
1436 select FB_CFB_FILLRECT
1437 select FB_CFB_COPYAREA
1438 select FB_CFB_IMAGEBLIT
1441 This is the frame buffer device driver for Graphics chips of VIA
1442 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1443 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1445 Say Y if you have a VIA UniChrome graphics board.
1447 To compile this driver as a module, choose M here: the
1448 module will be called viafb.
1452 config FB_VIA_DIRECT_PROCFS
1453 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1457 Allow direct hardware access to some output registers via procfs.
1458 This is dangerous but may provide the only chance to get the
1459 correct output device configuration.
1460 Its use is strongly discouraged.
1462 config FB_VIA_X_COMPATIBILITY
1463 bool "X server compatibility"
1467 This option reduces the functionality (power saving, ...) of the
1468 framebuffer to avoid negative impact on the OpenChrome X server.
1469 If you use any X server other than fbdev you should enable this
1470 otherwise it should be safe to disable it and allow using all
1476 tristate "NeoMagic display support"
1477 depends on FB && PCI
1478 select FB_MODE_HELPERS
1479 select FB_CFB_FILLRECT
1480 select FB_CFB_COPYAREA
1481 select FB_CFB_IMAGEBLIT
1484 This driver supports notebooks with NeoMagic PCI chips.
1485 Say Y if you have such a graphics card.
1487 To compile this driver as a module, choose M here: the
1488 module will be called neofb.
1491 tristate "IMG Kyro support"
1492 depends on FB && PCI
1493 select FB_CFB_FILLRECT
1494 select FB_CFB_COPYAREA
1495 select FB_CFB_IMAGEBLIT
1497 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1500 To compile this driver as a module, choose M here: the
1501 module will be called kyrofb.
1504 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1505 depends on FB && PCI
1506 select FB_CFB_IMAGEBLIT
1507 select FB_CFB_FILLRECT
1508 select FB_CFB_COPYAREA
1509 select FB_MODE_HELPERS
1511 This driver supports graphics boards with the 3Dfx Banshee,
1512 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1513 such a graphics board.
1515 To compile this driver as a module, choose M here: the
1516 module will be called tdfxfb.
1518 config FB_3DFX_ACCEL
1519 bool "3Dfx Acceleration functions"
1522 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1523 device driver with acceleration functions.
1526 bool "Enable DDC/I2C support"
1531 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1534 tristate "3Dfx Voodoo Graphics (sst1) support"
1535 depends on FB && PCI
1536 select FB_CFB_FILLRECT
1537 select FB_CFB_COPYAREA
1538 select FB_CFB_IMAGEBLIT
1540 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1541 Voodoo2 (cvg) based graphics card.
1543 To compile this driver as a module, choose M here: the
1544 module will be called sstfb.
1546 WARNING: Do not use any application that uses the 3D engine
1547 (namely glide) while using this driver.
1548 Please read the <file:Documentation/fb/sstfb.txt> for supported
1549 options and other important info support.
1552 tristate "VIA VT8623 support"
1553 depends on FB && PCI
1554 select FB_CFB_FILLRECT
1555 select FB_CFB_COPYAREA
1556 select FB_CFB_IMAGEBLIT
1557 select FB_TILEBLITTING
1560 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1562 Driver for CastleRock integrated graphics core in the
1563 VIA VT8623 [Apollo CLE266] chipset.
1566 tristate "Trident/CyberXXX/CyberBlade support"
1567 depends on FB && PCI
1568 select FB_CFB_FILLRECT
1569 select FB_CFB_COPYAREA
1570 select FB_CFB_IMAGEBLIT
1572 select FB_MODE_HELPERS
1574 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1575 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1577 There are also integrated versions of these chips called CyberXXXX,
1578 CyberImage or CyberBlade. These chips are mostly found in laptops
1579 but also on some motherboards including early VIA EPIA motherboards.
1580 For more information, read <file:Documentation/fb/tridentfb.txt>
1582 Say Y if you have such a graphics board.
1584 To compile this driver as a module, choose M here: the
1585 module will be called tridentfb.
1588 tristate "ARK 2000PV support"
1589 depends on FB && PCI
1590 select FB_CFB_FILLRECT
1591 select FB_CFB_COPYAREA
1592 select FB_CFB_IMAGEBLIT
1593 select FB_TILEBLITTING
1596 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1598 Driver for PCI graphics boards with ARK 2000PV chip
1599 and ICS 5342 RAMDAC.
1602 tristate "Permedia3 support"
1603 depends on FB && PCI
1604 select FB_CFB_FILLRECT
1605 select FB_CFB_COPYAREA
1606 select FB_CFB_IMAGEBLIT
1608 This is the frame buffer device driver for the 3DLabs Permedia3
1609 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1610 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1611 and maybe other boards.
1614 tristate "Fujitsu carmine frame buffer support"
1615 depends on FB && PCI
1616 select FB_CFB_FILLRECT
1617 select FB_CFB_COPYAREA
1618 select FB_CFB_IMAGEBLIT
1620 This is the frame buffer device driver for the Fujitsu Carmine chip.
1621 The driver provides two independent frame buffer devices.
1624 depends on FB_CARMINE
1625 prompt "DRAM timing"
1626 default FB_CARMINE_DRAM_EVAL
1628 config FB_CARMINE_DRAM_EVAL
1629 bool "Eval board timings"
1631 Use timings which work on the eval card.
1633 config CARMINE_DRAM_CUSTOM
1634 bool "Custom board timings"
1636 Use custom board timings.
1640 bool "Au1100 LCD Driver"
1641 depends on (FB = y) && MIPS_ALCHEMY
1642 select FB_CFB_FILLRECT
1643 select FB_CFB_COPYAREA
1644 select FB_CFB_IMAGEBLIT
1646 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1647 various panels and CRTs by passing in kernel cmd line option
1648 au1100fb:panel=<name>.
1651 bool "Au1200/Au1300 LCD Driver"
1652 depends on (FB = y) && MIPS_ALCHEMY
1653 select FB_SYS_FILLRECT
1654 select FB_SYS_COPYAREA
1655 select FB_SYS_IMAGEBLIT
1658 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1659 It can drive various panels and CRTs by passing in kernel cmd line
1660 option au1200fb:panel=<name>.
1663 bool "VIA VT8500 framebuffer support"
1664 depends on (FB = y) && ARM && ARCH_VT8500
1665 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1666 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1667 select FB_SYS_IMAGEBLIT
1668 select FB_MODE_HELPERS
1669 select VIDEOMODE_HELPERS
1671 This is the framebuffer driver for VIA VT8500 integrated LCD
1675 bool "Wondermedia WM8xxx-series frame buffer support"
1676 depends on (FB = y) && ARM && ARCH_VT8500
1677 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1678 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1679 select FB_SYS_IMAGEBLIT
1680 select FB_MODE_HELPERS
1681 select VIDEOMODE_HELPERS
1683 This is the framebuffer driver for WonderMedia WM8xxx-series
1684 integrated LCD controller. This driver covers the WM8505, WM8650
1687 config FB_WMT_GE_ROPS
1688 bool "VT8500/WM8xxx accelerated raster ops support"
1689 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1692 This adds support for accelerated raster operations on the
1693 VIA VT8500 and Wondermedia 85xx series SoCs.
1695 source "drivers/video/fbdev/geode/Kconfig"
1698 tristate "HD64461 Frame Buffer support"
1699 depends on FB && HD64461
1700 select FB_CFB_FILLRECT
1701 select FB_CFB_COPYAREA
1702 select FB_CFB_IMAGEBLIT
1704 This is the frame buffer device driver for the Hitachi HD64461 LCD
1708 tristate "PMAG-AA TURBOchannel framebuffer support"
1710 select FB_CFB_FILLRECT
1711 select FB_CFB_COPYAREA
1712 select FB_CFB_IMAGEBLIT
1714 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1715 used mainly in the MIPS-based DECstation series.
1718 tristate "PMAG-BA TURBOchannel framebuffer support"
1720 select FB_CFB_FILLRECT
1721 select FB_CFB_COPYAREA
1722 select FB_CFB_IMAGEBLIT
1724 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1725 used mainly in the MIPS-based DECstation series.
1728 tristate "PMAGB-B TURBOchannel framebuffer support"
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1734 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1735 in the MIPS-based DECstation series. The card is currently only
1736 supported in 1280x1024x8 mode.
1739 bool "Maxine (Personal DECstation) onboard framebuffer support"
1740 depends on (FB = y) && MACH_DECSTATION
1741 select FB_CFB_FILLRECT
1742 select FB_CFB_COPYAREA
1743 select FB_CFB_IMAGEBLIT
1745 Support for the onboard framebuffer (1024x768x8) in the Personal
1746 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1750 bool "G364 frame buffer support"
1751 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1752 select FB_CFB_FILLRECT
1753 select FB_CFB_COPYAREA
1754 select FB_CFB_IMAGEBLIT
1756 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1757 Olivetti M700-10 systems.
1760 bool "Motorola 68328 native frame buffer support"
1761 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1762 select FB_CFB_FILLRECT
1763 select FB_CFB_COPYAREA
1764 select FB_CFB_IMAGEBLIT
1766 Say Y here if you want to support the built-in frame buffer of
1767 the Motorola 68328 CPU family.
1770 tristate "PXA168/910 LCD framebuffer support"
1771 depends on FB && (CPU_PXA168 || CPU_PXA910)
1772 select FB_CFB_FILLRECT
1773 select FB_CFB_COPYAREA
1774 select FB_CFB_IMAGEBLIT
1776 Frame buffer driver for the built-in LCD controller in the Marvell
1780 tristate "PXA LCD framebuffer support"
1781 depends on FB && ARCH_PXA
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1785 select VIDEOMODE_HELPERS if OF
1786 select FB_MODE_HELPERS if OF
1788 Frame buffer driver for the built-in LCD controller in the Intel
1791 This driver is also available as a module ( = code which can be
1792 inserted and removed from the running kernel whenever you want). The
1793 module will be called pxafb. If you want to compile it as a module,
1794 say M here and read <file:Documentation/kbuild/modules.txt>.
1798 config FB_PXA_OVERLAY
1799 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1801 depends on FB_PXA && (PXA27x || PXA3xx)
1803 config FB_PXA_SMARTPANEL
1804 bool "PXA Smartpanel LCD support"
1808 config FB_PXA_PARAMETERS
1809 bool "PXA LCD command line parameters"
1813 Enable the use of kernel command line or module parameters
1814 to configure the physical properties of the LCD panel when
1815 using the PXA LCD driver.
1817 This option allows you to override the panel parameters
1818 supplied by the platform in order to support multiple
1819 different models of flatpanel. If you will only be using a
1820 single model of flatpanel then you can safely leave this
1823 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1826 tristate "PXA3xx 2D graphics accelerator driver"
1829 Kernelspace driver for the 2D graphics controller unit (GCU)
1830 found on PXA3xx processors. There is a counterpart driver in the
1831 DirectFB suite, see http://www.directfb.org/
1833 If you compile this as a module, it will be called pxa3xx_gcu.
1836 tristate "2700G LCD framebuffer support"
1837 depends on FB && ARCH_PXA
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1846 bool "Enable debugging info via debugfs"
1847 depends on FB_MBX && DEBUG_FS
1850 Enable this if you want debugging information using the debug
1851 filesystem (debugfs)
1856 tristate "Freescale DIU framebuffer support"
1857 depends on FB && FSL_SOC
1858 select FB_MODE_HELPERS
1859 select FB_CFB_FILLRECT
1860 select FB_CFB_COPYAREA
1861 select FB_CFB_IMAGEBLIT
1862 select PPC_LIB_RHEAP
1864 Framebuffer driver for the Freescale SoC DIU
1867 tristate "W100 frame buffer support"
1868 depends on FB && ARCH_PXA
1869 select FB_CFB_FILLRECT
1870 select FB_CFB_COPYAREA
1871 select FB_CFB_IMAGEBLIT
1873 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1874 It can also drive the w3220 chip found on iPAQ hx4700.
1876 This driver is also available as a module ( = code which can be
1877 inserted and removed from the running kernel whenever you want). The
1878 module will be called w100fb. If you want to compile it as a module,
1879 say M here and read <file:Documentation/kbuild/modules.txt>.
1883 config FB_SH_MOBILE_LCDC
1884 tristate "SuperH Mobile LCDC framebuffer support"
1885 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1886 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1887 select FB_SYS_FILLRECT
1888 select FB_SYS_COPYAREA
1889 select FB_SYS_IMAGEBLIT
1891 select FB_DEFERRED_IO
1894 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1897 tristate "Toshiba Mobile IO FrameBuffer support"
1898 depends on FB && (MFD_TMIO || COMPILE_TEST)
1899 select FB_CFB_FILLRECT
1900 select FB_CFB_COPYAREA
1901 select FB_CFB_IMAGEBLIT
1903 Frame buffer driver for the Toshiba Mobile IO integrated as found
1904 on the Sharp SL-6000 series
1906 This driver is also available as a module ( = code which can be
1907 inserted and removed from the running kernel whenever you want). The
1908 module will be called tmiofb. If you want to compile it as a module,
1909 say M here and read <file:Documentation/kbuild/modules.txt>.
1913 config FB_TMIO_ACCELL
1914 bool "tmiofb acceleration"
1919 tristate "Samsung S3C framebuffer support"
1920 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
1921 ARCH_S5PV210 || ARCH_EXYNOS)
1922 select FB_CFB_FILLRECT
1923 select FB_CFB_COPYAREA
1924 select FB_CFB_IMAGEBLIT
1926 Frame buffer driver for the built-in FB controller in the Samsung
1927 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1928 and the S3C64XX series such as the S3C6400 and S3C6410.
1930 These chips all have the same basic framebuffer design with the
1931 actual capabilities depending on the chip. For instance the S3C6400
1932 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1933 currently only have two.
1935 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1937 config FB_S3C_DEBUG_REGWRITE
1938 bool "Debug register writes"
1941 Show all register writes via pr_debug()
1944 tristate "S3C2410 LCD framebuffer support"
1945 depends on FB && ARCH_S3C24XX
1946 select FB_CFB_FILLRECT
1947 select FB_CFB_COPYAREA
1948 select FB_CFB_IMAGEBLIT
1950 Frame buffer driver for the built-in LCD controller in the Samsung
1953 This driver is also available as a module ( = code which can be
1954 inserted and removed from the running kernel whenever you want). The
1955 module will be called s3c2410fb. If you want to compile it as a module,
1956 say M here and read <file:Documentation/kbuild/modules.txt>.
1959 config FB_S3C2410_DEBUG
1960 bool "S3C2410 lcd debug messages"
1961 depends on FB_S3C2410
1963 Turn on debugging messages. Note that you can set/unset at run time
1967 tristate "NUC900 LCD framebuffer support"
1968 depends on FB && ARCH_W90X900
1969 select FB_CFB_FILLRECT
1970 select FB_CFB_COPYAREA
1971 select FB_CFB_IMAGEBLIT
1973 Frame buffer driver for the built-in LCD controller in the Nuvoton
1976 config GPM1040A0_320X240
1977 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
1978 depends on FB_NUC900
1981 tristate "Silicon Motion SM501 framebuffer support"
1982 depends on FB && MFD_SM501
1983 select FB_CFB_FILLRECT
1984 select FB_CFB_COPYAREA
1985 select FB_CFB_IMAGEBLIT
1987 Frame buffer driver for the CRT and LCD controllers in the Silicon
1990 This driver is also available as a module ( = code which can be
1991 inserted and removed from the running kernel whenever you want). The
1992 module will be called sm501fb. If you want to compile it as a module,
1993 say M here and read <file:Documentation/kbuild/modules.txt>.
1998 tristate "SMSC UFX6000/7000 USB Framebuffer support"
1999 depends on FB && USB
2000 select FB_MODE_HELPERS
2001 select FB_SYS_FILLRECT
2002 select FB_SYS_COPYAREA
2003 select FB_SYS_IMAGEBLIT
2005 select FB_DEFERRED_IO
2007 This is a kernel framebuffer driver for SMSC UFX USB devices.
2008 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2009 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2011 To compile as a module, choose M here: the module name is smscufx.
2014 tristate "Displaylink USB Framebuffer support"
2015 depends on FB && USB
2016 select FB_MODE_HELPERS
2017 select FB_SYS_FILLRECT
2018 select FB_SYS_COPYAREA
2019 select FB_SYS_IMAGEBLIT
2021 select FB_DEFERRED_IO
2023 This is a kernel framebuffer driver for DisplayLink USB devices.
2024 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2025 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2026 To compile as a module, choose M here: the module name is udlfb.
2028 config FB_IBM_GXT4500
2029 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2031 select FB_CFB_FILLRECT
2032 select FB_CFB_COPYAREA
2033 select FB_CFB_IMAGEBLIT
2035 Say Y here to enable support for the IBM GXT4000P/6000P and
2036 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2037 found on some IBM System P (pSeries) machines. This driver
2038 doesn't use Geometry Engine GT1000. This driver also supports
2039 AGP Fire GL2/3/4 cards on x86.
2042 tristate "PS3 GPU framebuffer driver"
2043 depends on FB && PS3_PS3AV
2044 select FB_SYS_FILLRECT
2045 select FB_SYS_COPYAREA
2046 select FB_SYS_IMAGEBLIT
2049 Include support for the virtual frame buffer in the PS3 platform.
2051 config FB_PS3_DEFAULT_SIZE_M
2052 int "PS3 default frame buffer size (in MiB)"
2056 This is the default size (in MiB) of the virtual frame buffer in
2058 The default value can be overridden on the kernel command line
2059 using the "ps3fb" option (e.g. "ps3fb=9M");
2062 tristate "Xilinx frame buffer support"
2063 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
2064 select FB_CFB_FILLRECT
2065 select FB_CFB_COPYAREA
2066 select FB_CFB_IMAGEBLIT
2068 Include support for the Xilinx ML300/ML403 reference design
2069 framebuffer. ML300 carries a 640*480 LCD display on the board,
2070 ML403 uses a standard DB15 VGA connector.
2073 tristate "Goldfish Framebuffer"
2074 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2075 select FB_CFB_FILLRECT
2076 select FB_CFB_COPYAREA
2077 select FB_CFB_IMAGEBLIT
2079 Framebuffer driver for Goldfish Virtual Platform
2082 tristate "Cobalt server LCD frame buffer support"
2083 depends on FB && MIPS_COBALT
2086 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2087 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2088 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2089 select FB_CFB_FILLRECT
2090 select FB_CFB_COPYAREA
2091 select FB_CFB_IMAGEBLIT
2093 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2094 (D)STN/TFT LCD Controller.
2095 Supports display resolutions up to 1024x1024 pixel, grayscale and
2096 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2097 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2098 panels <= 320 pixel horizontal resolution.
2101 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2102 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2103 select FB_CFB_FILLRECT
2104 select FB_CFB_COPYAREA
2105 select FB_CFB_IMAGEBLIT
2106 select FB_CFB_REV_PIXELS_IN_BYTE
2107 select FB_MODE_HELPERS
2108 select VIDEOMODE_HELPERS
2110 This is the frame buffer device driver for the TI LCD controller
2111 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2115 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2117 select FB_SYS_FILLRECT
2118 select FB_SYS_COPYAREA
2119 select FB_SYS_IMAGEBLIT
2122 This is a `virtual' frame buffer device. It operates on a chunk of
2123 unswappable kernel memory instead of on the memory of a graphics
2124 board. This means you cannot see any output sent to this frame
2125 buffer device, while it does consume precious memory. The main use
2126 of this frame buffer device is testing and debugging the frame
2127 buffer subsystem. Do NOT enable it for normal systems! To protect
2128 the innocent, it has to be enabled explicitly at boot time using the
2129 kernel option `video=vfb:'.
2131 To compile this driver as a module, choose M here: the
2132 module will be called vfb. In order to load it, you must use
2133 the vfb_enable=1 option.
2137 config XEN_FBDEV_FRONTEND
2138 tristate "Xen virtual frame buffer support"
2139 depends on FB && XEN
2140 select FB_SYS_FILLRECT
2141 select FB_SYS_COPYAREA
2142 select FB_SYS_IMAGEBLIT
2144 select FB_DEFERRED_IO
2145 select XEN_XENBUS_FRONTEND
2148 This driver implements the front-end of the Xen virtual
2149 frame buffer driver. It communicates with a back-end
2153 tristate "E-Ink Metronome/8track controller support"
2155 select FB_SYS_FILLRECT
2156 select FB_SYS_COPYAREA
2157 select FB_SYS_IMAGEBLIT
2159 select FB_DEFERRED_IO
2161 This driver implements support for the E-Ink Metronome
2162 controller. The pre-release name for this device was 8track
2163 and could also have been called by some vendors as PVI-nnnn.
2166 tristate "Fujitsu MB862xx GDC support"
2168 depends on PCI || (OF && PPC)
2169 select FB_CFB_FILLRECT
2170 select FB_CFB_COPYAREA
2171 select FB_CFB_IMAGEBLIT
2173 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2176 prompt "GDC variant"
2177 depends on FB_MB862XX
2179 config FB_MB862XX_PCI_GDC
2180 bool "Carmine/Coral-P(A) GDC"
2183 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2184 PCI graphics controller devices.
2186 config FB_MB862XX_LIME
2188 depends on OF && PPC
2189 select FB_FOREIGN_ENDIAN
2190 select FB_LITTLE_ENDIAN
2192 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2196 config FB_MB862XX_I2C
2197 bool "Support I2C bus on MB862XX GDC"
2198 depends on FB_MB862XX && I2C
2199 depends on FB_MB862XX=m || I2C=y
2202 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2203 driver to support accessing I2C devices on controller's I2C bus.
2204 These are usually some video decoder chips.
2207 tristate "EP93XX frame buffer support"
2208 depends on FB && ARCH_EP93XX
2209 select FB_CFB_FILLRECT
2210 select FB_CFB_COPYAREA
2211 select FB_CFB_IMAGEBLIT
2213 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2214 This driver is also available as a module. The module will be called
2217 config FB_PRE_INIT_FB
2218 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2219 depends on FB && FB_MB862XX_LIME
2221 Select this option if display contents should be inherited as set by
2225 tristate "MX3 Framebuffer support"
2226 depends on FB && MX3_IPU
2227 select BACKLIGHT_CLASS_DEVICE
2228 select BACKLIGHT_LCD_SUPPORT
2229 select FB_CFB_FILLRECT
2230 select FB_CFB_COPYAREA
2231 select FB_CFB_IMAGEBLIT
2234 This is a framebuffer device for the i.MX31 LCD Controller. So
2235 far only synchronous displays are supported. If you plan to use
2236 an LCD display with your i.MX31 system, say Y here.
2238 config FB_BROADSHEET
2239 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2241 select FB_SYS_FILLRECT
2242 select FB_SYS_COPYAREA
2243 select FB_SYS_IMAGEBLIT
2245 select FB_DEFERRED_IO
2247 This driver implements support for the E-Ink Broadsheet
2248 controller. The release name for this device was Epson S1D13521
2249 and could also have been called by other names when coupled with
2253 tristate "AUO-K190X EPD controller support"
2255 select FB_SYS_FILLRECT
2256 select FB_SYS_COPYAREA
2257 select FB_SYS_IMAGEBLIT
2259 select FB_DEFERRED_IO
2261 Provides support for epaper controllers from the K190X series
2262 of AUO. These controllers can be used to drive epaper displays
2265 This option enables the common support, shared by the individual
2266 controller drivers. You will also have to enable the driver
2267 for the controller type used in your device.
2270 tristate "AUO-K1900 EPD controller support"
2271 depends on FB && FB_AUO_K190X
2273 This driver implements support for the AUO K1900 epd-controller.
2274 This controller can drive Sipix epaper displays but can only do
2275 serial updates, reducing the number of possible frames per second.
2278 tristate "AUO-K1901 EPD controller support"
2279 depends on FB && FB_AUO_K190X
2281 This driver implements support for the AUO K1901 epd-controller.
2282 This controller can drive Sipix epaper displays and supports
2283 concurrent updates, making higher frames per second possible.
2286 tristate "JZ4740 LCD framebuffer support"
2287 depends on FB && MACH_JZ4740
2288 select FB_SYS_FILLRECT
2289 select FB_SYS_COPYAREA
2290 select FB_SYS_IMAGEBLIT
2292 Framebuffer support for the JZ4740 SoC.
2295 tristate "MXS LCD framebuffer support"
2296 depends on FB && (ARCH_MXS || ARCH_MXC)
2297 select FB_CFB_FILLRECT
2298 select FB_CFB_COPYAREA
2299 select FB_CFB_IMAGEBLIT
2300 select FB_MODE_HELPERS
2301 select VIDEOMODE_HELPERS
2303 Framebuffer support for the MXS SoC.
2305 config FB_PUV3_UNIGFX
2306 tristate "PKUnity v3 Unigfx framebuffer support"
2307 depends on FB && UNICORE32 && ARCH_PUV3
2308 select FB_SYS_FILLRECT
2309 select FB_SYS_COPYAREA
2310 select FB_SYS_IMAGEBLIT
2313 Choose this option if you want to use the Unigfx device as a
2314 framebuffer device. Without the support of PCI & AGP.
2317 tristate "Microsoft Hyper-V Synthetic Video support"
2318 depends on FB && HYPERV
2319 select FB_CFB_FILLRECT
2320 select FB_CFB_COPYAREA
2321 select FB_CFB_IMAGEBLIT
2323 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2326 bool "Simple framebuffer support"
2328 select FB_CFB_FILLRECT
2329 select FB_CFB_COPYAREA
2330 select FB_CFB_IMAGEBLIT
2332 Say Y if you want support for a simple frame-buffer.
2334 This driver assumes that the display hardware has been initialized
2335 before the kernel boots, and the kernel will simply render to the
2336 pre-allocated frame buffer surface.
2338 Configuration re: surface address, size, and format must be provided
2339 through device tree, or plain old platform data.
2341 source "drivers/video/fbdev/omap/Kconfig"
2342 source "drivers/video/fbdev/omap2/Kconfig"
2343 source "drivers/video/fbdev/mmp/Kconfig"
2345 config FB_SH_MOBILE_MERAM
2346 tristate "SuperH Mobile MERAM read ahead support"
2347 depends on (SUPERH || ARCH_SHMOBILE)
2348 select GENERIC_ALLOCATOR
2350 Enable MERAM support for the SuperH controller.
2352 This will allow for caching of the framebuffer to provide more
2353 reliable access under heavy main memory bus traffic situations.
2354 Up to 4 memory channels can be configured, allowing 4 RGB or
2355 2 YCbCr framebuffers to be configured.
2358 tristate "Solomon SSD1307 framebuffer support"
2359 depends on FB && I2C
2361 depends on GPIOLIB || COMPILE_TEST
2363 select FB_SYS_FILLRECT
2364 select FB_SYS_COPYAREA
2365 select FB_SYS_IMAGEBLIT
2366 select FB_DEFERRED_IO
2370 This driver implements support for the Solomon SSD1307
2371 OLED controller over I2C.
2374 tristate "Silicon Motion SM712 framebuffer support"
2375 depends on FB && PCI
2376 select FB_CFB_FILLRECT
2377 select FB_CFB_COPYAREA
2378 select FB_CFB_IMAGEBLIT
2380 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2383 This driver is also available as a module. The module will be
2384 called sm712fb. If you want to compile it as a module, say M
2385 here and read <file:Documentation/kbuild/modules.txt>.