5 menu "Graphics support"
13 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
15 config SH_LCD_MIPI_DSI
18 source "drivers/char/agp/Kconfig"
20 source "drivers/gpu/vga/Kconfig"
22 source "drivers/gpu/host1x/Kconfig"
24 source "drivers/gpu/drm/Kconfig"
30 config VIDEOMODE_HELPERS
37 tristate "Support for frame buffer devices"
39 The frame buffer device provides an abstraction for the graphics
40 hardware. It represents the frame buffer of some video hardware and
41 allows application software to access the graphics hardware through
42 a well-defined interface, so the software doesn't need to know
43 anything about the low-level (hardware register) stuff.
45 Frame buffer devices work identically across the different
46 architectures supported by Linux and make the implementation of
47 application programs easier and more portable; at this point, an X
48 server exists which uses the frame buffer device exclusively.
49 On several non-X86 architectures, the frame buffer device is the
50 only way to use the graphics hardware.
52 The device is accessed through special device nodes, usually located
53 in the /dev directory, i.e. /dev/fb*.
55 You need an utility program called fbset to make full use of frame
56 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
57 and the Framebuffer-HOWTO at
58 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
61 Say Y here and to the driver for your graphics board below if you
62 are compiling a kernel for a non-x86 architecture.
64 If you are compiling for the x86 architecture, you can say Y if you
65 want to play with it, but it is not essential. Please note that
66 running graphical applications that directly touch the hardware
67 (e.g. an accelerated X server) and that are not frame buffer
68 device-aware may cause unexpected results. If unsure, say N.
71 bool "Enable firmware EDID"
75 This enables access to the EDID transferred from the firmware.
76 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
77 transfers do not work for your driver and if you are using
78 nvidiafb, i810fb or savagefb.
80 In general, choosing Y for this option is safe. If you
81 experience extremely long delays while booting before you get
82 something on your display, try setting this to N. Matrox cards in
83 combination with certain motherboards and monitors are known to
84 suffer from this problem.
93 config FB_BOOT_VESA_SUPPORT
98 If true, at least one selected framebuffer driver can take advantage
99 of VESA video modes set at an early boot stage via the vga= parameter.
101 config FB_CFB_FILLRECT
106 Include the cfb_fillrect function for generic software rectangle
107 filling. This is used by drivers that don't provide their own
108 (accelerated) version.
110 config FB_CFB_COPYAREA
115 Include the cfb_copyarea function for generic software area copying.
116 This is used by drivers that don't provide their own (accelerated)
119 config FB_CFB_IMAGEBLIT
124 Include the cfb_imageblit function for generic software image
125 blitting. This is used by drivers that don't provide their own
126 (accelerated) version.
128 config FB_CFB_REV_PIXELS_IN_BYTE
133 Allow generic frame-buffer functions to work on displays with 1, 2
134 and 4 bits per pixel depths which has opposite order of pixels in
135 byte order to bytes in long order.
137 config FB_SYS_FILLRECT
142 Include the sys_fillrect function for generic software rectangle
143 filling. This is used by drivers that don't provide their own
144 (accelerated) version and the framebuffer is in system RAM.
146 config FB_SYS_COPYAREA
151 Include the sys_copyarea function for generic software area copying.
152 This is used by drivers that don't provide their own (accelerated)
153 version and the framebuffer is in system RAM.
155 config FB_SYS_IMAGEBLIT
160 Include the sys_imageblit function for generic software image
161 blitting. This is used by drivers that don't provide their own
162 (accelerated) version and the framebuffer is in system RAM.
164 menuconfig FB_FOREIGN_ENDIAN
165 bool "Framebuffer foreign endianness support"
168 This menu will let you enable support for the framebuffers with
169 non-native endianness (e.g. Little-Endian framebuffer on a
170 Big-Endian machine). Most probably you don't have such hardware,
171 so it's safe to say "n" here.
174 prompt "Choice endianness support"
175 depends on FB_FOREIGN_ENDIAN
177 config FB_BOTH_ENDIAN
178 bool "Support for Big- and Little-Endian framebuffers"
181 bool "Support for Big-Endian framebuffers only"
183 config FB_LITTLE_ENDIAN
184 bool "Support for Little-Endian framebuffers only"
193 config FB_DEFERRED_IO
200 depends on FB_DEFERRED_IO
207 Common utility functions useful to fbdev drivers of VGA-based
218 select BACKLIGHT_LCD_SUPPORT
219 select BACKLIGHT_CLASS_DEVICE
222 config FB_MODE_HELPERS
223 bool "Enable Video Mode Handling Helpers"
227 This enables functions for handling video modes using the
228 Generalized Timing Formula and the EDID parser. A few drivers rely
229 on this feature such as the radeonfb, rivafb, and the i810fb. If
230 your driver does not take advantage of this feature, choosing Y will
231 just increase the kernel size by about 5K.
233 config FB_TILEBLITTING
234 bool "Enable Tile Blitting Support"
238 This enables tile blitting. Tile blitting is a drawing technique
239 where the screen is divided into rectangular sections (tiles), whereas
240 the standard blitting divides the screen into pixels. Because the
241 default drawing element is a tile, drawing functions will be passed
242 parameters in terms of number of tiles instead of number of pixels.
243 For example, to draw a single character, instead of using bitmaps,
244 an index to an array of bitmaps will be used. To clear or move a
245 rectangular section of a screen, the rectangle will be described in
246 terms of number of tiles in the x- and y-axis.
248 This is particularly important to one driver, matroxfb. If
251 comment "Frame buffer hardware drivers"
255 tristate "Aeroflex Gaisler framebuffer support"
256 depends on FB && SPARC
257 select FB_CFB_FILLRECT
258 select FB_CFB_COPYAREA
259 select FB_CFB_IMAGEBLIT
261 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
264 tristate "Cirrus Logic support"
265 depends on FB && (ZORRO || PCI)
266 select FB_CFB_FILLRECT
267 select FB_CFB_COPYAREA
268 select FB_CFB_IMAGEBLIT
270 This enables support for Cirrus Logic GD542x/543x based boards on
271 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
273 If you have a PCI-based system, this enables support for these
274 chips: GD-543x, GD-544x, GD-5480.
276 Please read the file <file:Documentation/fb/cirrusfb.txt>.
278 Say N unless you have such a graphics board or plan to get one
279 before you next recompile the kernel.
282 tristate "Permedia2 support"
283 depends on FB && ((AMIGA && BROKEN) || PCI)
284 select FB_CFB_FILLRECT
285 select FB_CFB_COPYAREA
286 select FB_CFB_IMAGEBLIT
288 This is the frame buffer device driver for cards based on
289 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
290 The driver was tested on the following cards:
291 Diamond FireGL 1000 PRO AGP
292 ELSA Gloria Synergy PCI
293 Appian Jeronimo PRO (both heads) PCI
294 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
295 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
296 ASK Graphic Blaster Exxtreme AGP
298 To compile this driver as a module, choose M here: the
299 module will be called pm2fb.
301 config FB_PM2_FIFO_DISCONNECT
302 bool "enable FIFO disconnect feature"
303 depends on FB_PM2 && PCI
305 Support the Permedia2 FIFO disconnect feature.
308 tristate "ARM PrimeCell PL110 support"
309 depends on ARM || ARM64 || COMPILE_TEST
310 depends on FB && ARM_AMBA
311 select FB_CFB_FILLRECT
312 select FB_CFB_COPYAREA
313 select FB_CFB_IMAGEBLIT
315 This framebuffer device driver is for the ARM PrimeCell PL110
316 Colour LCD controller. ARM PrimeCells provide the building
317 blocks for System on a Chip devices.
319 If you want to compile this as a module (=code which can be
320 inserted into and removed from the running kernel), say M
321 here and read <file:Documentation/kbuild/modules.txt>. The module
322 will be called amba-clcd.
325 bool "Acorn VIDC support"
326 depends on (FB = y) && ARM && ARCH_ACORN
327 select FB_CFB_FILLRECT
328 select FB_CFB_COPYAREA
329 select FB_CFB_IMAGEBLIT
331 This is the frame buffer device driver for the Acorn VIDC graphics
332 hardware found in Acorn RISC PCs and other ARM-based machines. If
336 bool "CLPS711X LCD support"
337 depends on (FB = y) && ARM && ARCH_CLPS711X
338 select FB_CFB_FILLRECT
339 select FB_CFB_COPYAREA
340 select FB_CFB_IMAGEBLIT
342 Say Y to enable the Framebuffer driver for the CLPS7111 and
346 bool "SA-1100 LCD support"
347 depends on (FB = y) && ARM && ARCH_SA1100
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This is a framebuffer device for the SA-1100 LCD Controller.
353 See <http://www.linux-fbdev.org/> for information on framebuffer
356 If you plan to use the LCD display with your SA-1100 system, say
360 tristate "Freescale i.MX1/21/25/27 LCD support"
361 depends on FB && ARCH_MXC
362 select FB_CFB_FILLRECT
363 select FB_CFB_COPYAREA
364 select FB_CFB_IMAGEBLIT
365 select FB_MODE_HELPERS
366 select VIDEOMODE_HELPERS
369 tristate "CyberPro 2000/2010/5000 support"
370 depends on FB && PCI && (BROKEN || !SPARC64)
371 select FB_CFB_FILLRECT
372 select FB_CFB_COPYAREA
373 select FB_CFB_IMAGEBLIT
375 This enables support for the Integraphics CyberPro 20x0 and 5000
376 VGA chips used in the Rebel.com Netwinder and other machines.
377 Say Y if you have a NetWinder or a graphics card containing this
378 device, otherwise say N.
380 config FB_CYBER2000_DDC
381 bool "DDC for CyberPro support"
382 depends on FB_CYBER2000
386 Say Y here if you want DDC support for your CyberPro graphics
387 card. This is only I2C bus support, driver does not use EDID.
389 config FB_CYBER2000_I2C
390 bool "CyberPro 2000/2010/5000 I2C support"
391 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
394 Enable support for the I2C video decoder interface on the
395 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
396 on the Netwinder machines for the SAA7111 video capture.
400 depends on (FB = y) && APOLLO
402 select FB_CFB_FILLRECT
403 select FB_CFB_IMAGEBLIT
407 depends on (FB = y) && Q40
409 select FB_CFB_FILLRECT
410 select FB_CFB_COPYAREA
411 select FB_CFB_IMAGEBLIT
414 tristate "Amiga native chipset support"
415 depends on FB && AMIGA
417 This is the frame buffer device driver for the builtin graphics
418 chipset found in Amigas.
420 To compile this driver as a module, choose M here: the
421 module will be called amifb.
424 bool "Amiga OCS chipset support"
427 This enables support for the original Agnus and Denise video chips,
428 found in the Amiga 1000 and most A500's and A2000's. If you intend
429 to run Linux on any of these systems, say Y; otherwise say N.
432 bool "Amiga ECS chipset support"
435 This enables support for the Enhanced Chip Set, found in later
436 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
437 you intend to run Linux on any of these systems, say Y; otherwise
441 bool "Amiga AGA chipset support"
444 This enables support for the Advanced Graphics Architecture (also
445 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
446 and CD32. If you intend to run Linux on any of these systems, say Y;
450 bool "Amiga FrameMaster II/Rainbow II support"
451 depends on (FB = y) && ZORRO
452 select FB_CFB_FILLRECT
453 select FB_CFB_COPYAREA
454 select FB_CFB_IMAGEBLIT
456 This is the frame buffer device driver for the Amiga FrameMaster
457 card from BSC (exhibited 1992 but not shipped as a CBM product).
460 tristate "Arc Monochrome LCD board support"
462 select FB_SYS_FILLRECT
463 select FB_SYS_COPYAREA
464 select FB_SYS_IMAGEBLIT
467 This enables support for the Arc Monochrome LCD board. The board
468 is based on the KS-108 lcd controller and is typically a matrix
469 of 2*n chips. This driver was tested with a 128x64 panel. This
470 driver supports it for use with x86 SBCs through a 16 bit GPIO
471 interface (8 bit data, 8 bit control). If you anticipate using
472 this driver, say Y or M; otherwise say N. You must specify the
473 GPIO IO address to be used for setting control and data.
476 bool "Atari native chipset support"
477 depends on (FB = y) && ATARI
478 select FB_CFB_FILLRECT
479 select FB_CFB_COPYAREA
480 select FB_CFB_IMAGEBLIT
482 This is the frame buffer device driver for the builtin graphics
483 chipset found in Ataris.
486 bool "Open Firmware frame buffer device support"
487 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
488 select FB_CFB_FILLRECT
489 select FB_CFB_COPYAREA
490 select FB_CFB_IMAGEBLIT
493 Say Y if you want support with Open Firmware for your graphics
497 bool "Apple \"control\" display support"
498 depends on (FB = y) && PPC_PMAC && PPC32
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 This driver supports a frame buffer for the graphics adapter in the
505 Power Macintosh 7300 and others.
508 bool "Apple \"platinum\" 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 "platinum" graphics
516 adapter in some Power Macintoshes.
519 bool "Apple \"valkyrie\" display support"
520 depends on (FB = y) && (MAC || (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 "valkyrie" graphics
527 adapter in some Power Macintoshes.
530 bool "Chips 65550 display support"
531 depends on (FB = y) && PPC32 && PCI
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
536 This is the frame buffer device driver for the Chips & Technologies
537 65550 graphics chip in PowerBooks.
540 bool "Asiliant (Chips) 69000 display support"
541 depends on (FB = y) && PCI
542 select FB_CFB_FILLRECT
543 select FB_CFB_COPYAREA
544 select FB_CFB_IMAGEBLIT
546 This is the frame buffer device driver for the Asiliant 69030 chipset
549 bool "IMS Twin Turbo display support"
550 depends on (FB = y) && PCI
551 select FB_CFB_IMAGEBLIT
552 select FB_MACMODES if PPC
554 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
555 many Macintosh and compatible computers.
558 tristate "VGA 16-color graphics support"
559 depends on FB && (X86 || PPC)
560 select FB_CFB_FILLRECT
561 select FB_CFB_COPYAREA
562 select FB_CFB_IMAGEBLIT
564 select FONT_8x16 if FRAMEBUFFER_CONSOLE
566 This is the frame buffer device driver for VGA 16 color graphic
567 cards. Say Y if you have such a card.
569 To compile this driver as a module, choose M here: the
570 module will be called vga16fb.
572 config FB_BF54X_LQ043
573 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
574 depends on FB && (BF54x) && !BF542
575 select FB_CFB_FILLRECT
576 select FB_CFB_COPYAREA
577 select FB_CFB_IMAGEBLIT
579 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
581 config FB_BFIN_T350MCQB
582 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
583 depends on FB && BLACKFIN
585 select FB_CFB_FILLRECT
586 select FB_CFB_COPYAREA
587 select FB_CFB_IMAGEBLIT
589 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
590 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
591 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
593 config FB_BFIN_LQ035Q1
594 tristate "SHARP LQ035Q1DH02 TFT LCD"
595 depends on FB && BLACKFIN && SPI
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
601 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
602 the Blackfin Landscape LCD EZ-Extender Card.
603 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
604 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
606 To compile this driver as a module, choose M here: the
607 module will be called bfin-lq035q1-fb.
609 config FB_BF537_LQ035
610 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
611 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
612 select FB_CFB_FILLRECT
613 select FB_CFB_COPYAREA
614 select FB_CFB_IMAGEBLIT
617 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
620 To compile this driver as a module, choose M here: the
621 module will be called bf537-lq035.
624 tristate "Blackfin ADV7393 Video encoder"
625 depends on FB && BLACKFIN
627 select FB_CFB_FILLRECT
628 select FB_CFB_COPYAREA
629 select FB_CFB_IMAGEBLIT
631 This is the framebuffer device for a ADV7393 video encoder
632 attached to a Blackfin on the PPI port.
633 If your Blackfin board has a ADV7393 select Y.
635 To compile this driver as a module, choose M here: the
636 module will be called bfin_adv7393fb.
639 prompt "Video mode support"
640 depends on FB_BFIN_7393
650 bool 'NTSC 640x480 (Experimental)'
653 bool 'PAL 640x480 (Experimental)'
656 bool 'NTSC 720x480 YCbCR input'
659 bool 'PAL 720x576 YCbCR input'
664 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
665 depends on (FB_BFIN_7393)
666 default ADV7393_1XMEM
676 tristate "HP STI frame buffer device support"
677 depends on FB && PARISC
678 select FB_CFB_FILLRECT
679 select FB_CFB_COPYAREA
680 select FB_CFB_IMAGEBLIT
685 STI refers to the HP "Standard Text Interface" which is a set of
686 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
687 Enabling this option will implement the linux framebuffer device
688 using calls to the STI BIOS routines for initialisation.
690 If you enable this option, you will get a planar framebuffer device
691 /dev/fb which will work on the most common HP graphic cards of the
692 NGLE family, including the artist chips (in the 7xx and Bxxx series),
693 HCRX, HCRX24, CRX, CRX24 and VisEG series.
695 It is safe to enable this option, so you should probably say "Y".
698 bool "Generic Macintosh display support"
699 depends on (FB = y) && MAC
700 select FB_CFB_FILLRECT
701 select FB_CFB_COPYAREA
702 select FB_CFB_IMAGEBLIT
707 depends on (FB = y) && DIO
708 select FB_CFB_IMAGEBLIT
712 tristate "TGA/SFB+ framebuffer support"
713 depends on FB && (ALPHA || TC)
714 select FB_CFB_FILLRECT
715 select FB_CFB_COPYAREA
716 select FB_CFB_IMAGEBLIT
719 This is the frame buffer device driver for generic TGA and SFB+
720 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
721 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
722 TURBOchannel cards, also known as PMAGD-A, -B and -C.
724 Due to hardware limitations ZLX-E2 and E3 cards are not supported
725 for DECstation 5000/200 systems. Additionally due to firmware
726 limitations these cards may cause troubles with booting DECstation
727 5000/240 and /260 systems, but are fully supported under Linux if
728 you manage to get it going. ;-)
730 Say Y if you have one of those.
733 tristate "Userspace VESA VGA graphics support"
734 depends on FB && CONNECTOR
735 select FB_CFB_FILLRECT
736 select FB_CFB_COPYAREA
737 select FB_CFB_IMAGEBLIT
738 select FB_MODE_HELPERS
740 This is the frame buffer driver for generic VBE 2.0 compliant
741 graphic cards. It can also take advantage of VBE 3.0 features,
742 such as refresh rate adjustment.
744 This driver generally provides more features than vesafb but
745 requires a userspace helper application called 'v86d'. See
746 <file:Documentation/fb/uvesafb.txt> for more information.
751 bool "VESA VGA graphics support"
752 depends on (FB = y) && X86
753 select FB_CFB_FILLRECT
754 select FB_CFB_COPYAREA
755 select FB_CFB_IMAGEBLIT
756 select FB_BOOT_VESA_SUPPORT
758 This is the frame buffer device driver for generic VESA 2.0
759 compliant graphic cards. The older VESA 1.2 cards are not supported.
760 You will get a boot time penguin logo at no additional cost. Please
761 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
764 bool "EFI-based Framebuffer Support"
765 depends on (FB = y) && X86 && EFI
766 select FB_CFB_FILLRECT
767 select FB_CFB_COPYAREA
768 select FB_CFB_IMAGEBLIT
770 This is the EFI frame buffer device driver. If the firmware on
771 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
772 using the EFI framebuffer as your console.
775 tristate "N411 Apollo/Hecuba devkit support"
776 depends on FB && X86 && MMU
777 select FB_SYS_FILLRECT
778 select FB_SYS_COPYAREA
779 select FB_SYS_IMAGEBLIT
781 select FB_DEFERRED_IO
784 This enables support for the Apollo display controller in its
785 Hecuba form using the n411 devkit.
788 tristate "Hercules mono graphics support"
791 Say Y here if you have a Hercules mono graphics card.
793 To compile this driver as a module, choose M here: the
794 module will be called hgafb.
796 As this card technology is at least 25 years old,
797 most people will answer N here.
800 tristate "SGI Visual Workstation framebuffer support"
801 depends on FB && X86_VISWS
802 select FB_CFB_FILLRECT
803 select FB_CFB_COPYAREA
804 select FB_CFB_IMAGEBLIT
806 SGI Visual Workstation support for framebuffer graphics.
809 bool "SGI Graphics Backend frame buffer support"
810 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
811 select FB_CFB_FILLRECT
812 select FB_CFB_COPYAREA
813 select FB_CFB_IMAGEBLIT
815 This is the frame buffer device driver for SGI Graphics Backend.
816 This chip is used in SGI O2 and Visual Workstation 320/540.
819 int "Video memory size in MB"
823 This is the amount of memory reserved for the framebuffer,
824 which can be any value between 1MB and 8MB.
827 bool "SBUS and UPA framebuffers"
828 depends on (FB = y) && SPARC
830 Say Y if you want support for SBUS or UPA based frame buffer device.
834 depends on (FB = y) && (SPARC && FB_SBUS)
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
839 This is the frame buffer device driver for the BWtwo frame buffer.
842 bool "CGthree support"
843 depends on (FB = y) && (SPARC && FB_SBUS)
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This is the frame buffer device driver for the CGthree frame buffer.
851 bool "CGsix (GX,TurboGX) support"
852 depends on (FB = y) && (SPARC && FB_SBUS)
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
856 This is the frame buffer device driver for the CGsix (GX, TurboGX)
860 bool "Creator/Creator3D/Elite3D support"
861 depends on FB_SBUS && SPARC64
862 select FB_CFB_COPYAREA
863 select FB_CFB_IMAGEBLIT
865 This is the frame buffer device driver for the Creator, Creator3D,
866 and Elite3D graphics boards.
869 bool "TCX (SS4/SS5 only) support"
871 select FB_CFB_FILLRECT
872 select FB_CFB_COPYAREA
873 select FB_CFB_IMAGEBLIT
875 This is the frame buffer device driver for the TCX 24/8bit frame
879 bool "CGfourteen (SX) support"
881 select FB_CFB_FILLRECT
882 select FB_CFB_COPYAREA
883 select FB_CFB_IMAGEBLIT
885 This is the frame buffer device driver for the CGfourteen frame
886 buffer on Desktop SPARCsystems with the SX graphics option.
889 bool "P9100 (Sparcbook 3 only) support"
891 select FB_CFB_FILLRECT
892 select FB_CFB_COPYAREA
893 select FB_CFB_IMAGEBLIT
895 This is the frame buffer device driver for the P9100 card
896 supported on Sparcbook 3 machines.
899 bool "Leo (ZX) support"
901 select FB_CFB_FILLRECT
902 select FB_CFB_COPYAREA
903 select FB_CFB_IMAGEBLIT
905 This is the frame buffer device driver for the SBUS-based Sun ZX
906 (leo) frame buffer cards.
909 bool "IGA 168x display support"
910 depends on (FB = y) && SPARC32
911 select FB_CFB_FILLRECT
912 select FB_CFB_COPYAREA
913 select FB_CFB_IMAGEBLIT
915 This is the framebuffer device for the INTERGRAPHICS 1680 and
916 successor frame buffer cards.
919 bool "Sun XVR-500 3DLABS Wildcat support"
920 depends on (FB = y) && PCI && SPARC64
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
925 This is the framebuffer device for the Sun XVR-500 and similar
926 graphics cards based upon the 3DLABS Wildcat chipset. The driver
927 only works on sparc64 systems where the system firmware has
928 mostly initialized the card already. It is treated as a
929 completely dumb framebuffer device.
932 bool "Sun XVR-2500 3DLABS Wildcat support"
933 depends on (FB = y) && PCI && SPARC64
934 select FB_CFB_FILLRECT
935 select FB_CFB_COPYAREA
936 select FB_CFB_IMAGEBLIT
938 This is the framebuffer device for the Sun XVR-2500 and similar
939 graphics cards based upon the 3DLABS Wildcat chipset. The driver
940 only works on sparc64 systems where the system firmware has
941 mostly initialized the card already. It is treated as a
942 completely dumb framebuffer device.
945 bool "Sun XVR-1000 support"
946 depends on (FB = y) && SPARC64
947 select FB_CFB_FILLRECT
948 select FB_CFB_COPYAREA
949 select FB_CFB_IMAGEBLIT
951 This is the framebuffer device for the Sun XVR-1000 and similar
952 graphics cards. The driver only works on sparc64 systems where
953 the system firmware has mostly initialized the card already. It
954 is treated as a completely dumb framebuffer device.
957 tristate "NEC PowerVR 2 display support"
958 depends on FB && SH_DREAMCAST
959 select FB_CFB_FILLRECT
960 select FB_CFB_COPYAREA
961 select FB_CFB_IMAGEBLIT
963 Say Y here if you have a PowerVR 2 card in your box. If you plan to
964 run linux on your Dreamcast, you will have to say Y here.
965 This driver may or may not work on other PowerVR 2 cards, but is
966 totally untested. Use at your own risk. If unsure, say N.
968 To compile this driver as a module, choose M here: the
969 module will be called pvr2fb.
971 You can pass several parameters to the driver at boot time or at
972 module load time. The parameters look like "video=pvr2:XXX", where
973 the meaning of XXX can be found at the end of the main source file
974 (<file:drivers/video/pvr2fb.c>). Please see the file
975 <file:Documentation/fb/pvr2fb.txt>.
978 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
980 select FB_CFB_FILLRECT
981 select FB_CFB_COPYAREA
982 select FB_CFB_IMAGEBLIT
984 This enables support for the OpenCores VGA/LCD core.
986 The OpenCores VGA/LCD core is typically used together with
987 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
988 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
990 The source code and specification for the core is available at
991 <http://opencores.org/project,vga_lcd>
994 tristate "Epson S1D13XXX framebuffer support"
996 select FB_CFB_FILLRECT
997 select FB_CFB_COPYAREA
998 select FB_CFB_IMAGEBLIT
1000 Support for S1D13XXX framebuffer device family (currently only
1001 working with S1D13806). Product specs at
1002 <http://vdc.epson.com/>
1005 tristate "AT91/AT32 LCD Controller support"
1006 depends on FB && HAVE_FB_ATMEL
1007 select FB_CFB_FILLRECT
1008 select FB_CFB_COPYAREA
1009 select FB_CFB_IMAGEBLIT
1010 select FB_MODE_HELPERS
1011 select VIDEOMODE_HELPERS
1013 This enables support for the AT91/AT32 LCD Controller.
1016 bool "Frame Buffer in internal SRAM"
1017 depends on FB_ATMEL && ARCH_AT91SAM9261
1019 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1020 to let frame buffer in external SDRAM.
1023 bool "Use a STN display with AT91/AT32 LCD Controller"
1024 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1027 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1028 Controller. Say N if you want to connect a TFT.
1033 tristate "nVidia Framebuffer Support"
1034 depends on FB && PCI
1035 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1036 select FB_MODE_HELPERS
1037 select FB_CFB_FILLRECT
1038 select FB_CFB_COPYAREA
1039 select FB_CFB_IMAGEBLIT
1043 This driver supports graphics boards with the nVidia chips, TNT
1044 and newer. For very old chipsets, such as the RIVA128, then use
1046 Say Y if you have such a graphics board.
1048 To compile this driver as a module, choose M here: the
1049 module will be called nvidiafb.
1051 config FB_NVIDIA_I2C
1052 bool "Enable DDC Support"
1053 depends on FB_NVIDIA
1056 This enables I2C support for nVidia Chipsets. This is used
1057 only for getting EDID information from the attached display
1058 allowing for robust video mode handling and switching.
1060 Because fbdev-2.6 requires that drivers must be able to
1061 independently validate video mode parameters, you should say Y
1064 config FB_NVIDIA_DEBUG
1065 bool "Lots of debug output"
1066 depends on FB_NVIDIA
1069 Say Y here if you want the nVidia driver to output all sorts
1070 of debugging information to provide to the maintainer when
1071 something goes wrong.
1073 config FB_NVIDIA_BACKLIGHT
1074 bool "Support for backlight control"
1075 depends on FB_NVIDIA
1078 Say Y here if you want to control the backlight of your display.
1081 tristate "nVidia Riva support"
1082 depends on FB && PCI
1083 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1084 select FB_MODE_HELPERS
1085 select FB_CFB_FILLRECT
1086 select FB_CFB_COPYAREA
1087 select FB_CFB_IMAGEBLIT
1091 This driver supports graphics boards with the nVidia Riva/Geforce
1093 Say Y if you have such a graphics board.
1095 To compile this driver as a module, choose M here: the
1096 module will be called rivafb.
1099 bool "Enable DDC Support"
1103 This enables I2C support for nVidia Chipsets. This is used
1104 only for getting EDID information from the attached display
1105 allowing for robust video mode handling and switching.
1107 Because fbdev-2.6 requires that drivers must be able to
1108 independently validate video mode parameters, you should say Y
1111 config FB_RIVA_DEBUG
1112 bool "Lots of debug output"
1116 Say Y here if you want the Riva driver to output all sorts
1117 of debugging information to provide to the maintainer when
1118 something goes wrong.
1120 config FB_RIVA_BACKLIGHT
1121 bool "Support for backlight control"
1125 Say Y here if you want to control the backlight of your display.
1128 tristate "Intel740 support"
1129 depends on FB && PCI
1130 select FB_MODE_HELPERS
1131 select FB_CFB_FILLRECT
1132 select FB_CFB_COPYAREA
1133 select FB_CFB_IMAGEBLIT
1137 This driver supports graphics cards based on Intel740 chip.
1140 tristate "Intel 810/815 support"
1141 depends on FB && PCI && X86_32 && AGP_INTEL
1142 select FB_MODE_HELPERS
1143 select FB_CFB_FILLRECT
1144 select FB_CFB_COPYAREA
1145 select FB_CFB_IMAGEBLIT
1148 This driver supports the on-board graphics built in to the Intel 810
1149 and 815 chipsets. Say Y if you have and plan to use such a board.
1151 To compile this driver as a module, choose M here: the
1152 module will be called i810fb.
1154 For more information, please read
1155 <file:Documentation/fb/intel810.txt>
1158 bool "use VESA Generalized Timing Formula"
1161 If you say Y, then the VESA standard, Generalized Timing Formula
1162 or GTF, will be used to calculate the required video timing values
1163 per video mode. Since the GTF allows nondiscrete timings
1164 (nondiscrete being a range of values as opposed to discrete being a
1165 set of values), you'll be able to use any combination of horizontal
1166 and vertical resolutions, and vertical refresh rates without having
1167 to specify your own timing parameters. This is especially useful
1168 to maximize the performance of an aging display, or if you just
1169 have a display with nonstandard dimensions. A VESA compliant
1170 monitor is recommended, but can still work with non-compliant ones.
1171 If you need or want this, then select this option. The timings may
1172 not be compliant with Intel's recommended values. Use at your own
1175 If you say N, the driver will revert to discrete video timings
1176 using a set recommended by Intel in their documentation.
1181 bool "Enable DDC Support"
1182 depends on FB_I810 && FB_I810_GTF
1187 tristate "Intel LE80578 (Vermilion) support"
1188 depends on FB && PCI && X86
1189 select FB_MODE_HELPERS
1190 select FB_CFB_FILLRECT
1191 select FB_CFB_COPYAREA
1192 select FB_CFB_IMAGEBLIT
1194 This driver supports the LE80578 (Vermilion Range) chipset
1196 config FB_CARILLO_RANCH
1197 tristate "Intel Carillo Ranch support"
1198 depends on FB_LE80578 && FB && PCI && X86
1200 This driver supports the LE80578 (Carillo Ranch) board
1203 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1204 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1205 select FB_MODE_HELPERS
1206 select FB_CFB_FILLRECT
1207 select FB_CFB_COPYAREA
1208 select FB_CFB_IMAGEBLIT
1209 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1210 depends on !DRM_I915
1212 This driver supports the on-board graphics built in to the Intel
1213 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1214 Say Y if you have and plan to use such a board.
1216 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1218 To compile this driver as a module, choose M here: the
1219 module will be called intelfb.
1221 For more information, please read <file:Documentation/fb/intelfb.txt>
1223 config FB_INTEL_DEBUG
1224 bool "Intel driver Debug Messages"
1227 Say Y here if you want the Intel driver to output all sorts
1228 of debugging information to provide to the maintainer when
1229 something goes wrong.
1232 bool "DDC/I2C for Intel framebuffer support"
1237 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1240 tristate "Matrox acceleration"
1241 depends on FB && PCI
1242 select FB_CFB_FILLRECT
1243 select FB_CFB_COPYAREA
1244 select FB_CFB_IMAGEBLIT
1245 select FB_TILEBLITTING
1246 select FB_MACMODES if PPC_PMAC
1248 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1249 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1250 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1251 Matrox G400, G450 or G550 card in your box.
1253 To compile this driver as a module, choose M here: the
1254 module will be called matroxfb.
1256 You can pass several parameters to the driver at boot time or at
1257 module load time. The parameters look like "video=matroxfb:XXX", and
1258 are described in <file:Documentation/fb/matroxfb.txt>.
1260 config FB_MATROX_MILLENIUM
1261 bool "Millennium I/II support"
1262 depends on FB_MATROX
1264 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1265 video card. If you select "Advanced lowlevel driver options" below,
1266 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1267 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1268 also use font widths different from 8.
1270 config FB_MATROX_MYSTIQUE
1271 bool "Mystique support"
1272 depends on FB_MATROX
1274 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1275 video card. If you select "Advanced lowlevel driver options" below,
1276 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1277 packed pixel and 32 bpp packed pixel. You can also use font widths
1281 bool "G100/G200/G400/G450/G550 support"
1282 depends on FB_MATROX
1284 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1285 video card. If you select "Advanced lowlevel driver options", you
1286 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1287 pixel and 32 bpp packed pixel. You can also use font widths
1290 If you need support for G400 secondary head, you must say Y to
1291 "Matrox I2C support" and "G400 second head support" right below.
1292 G450/G550 secondary head and digital output are supported without
1295 The driver starts in monitor mode. You must use the matroxset tool
1296 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1297 swap primary and secondary head outputs, or to change output mode.
1298 Secondary head driver always start in 640x480 resolution and you
1299 must use fbset to change it.
1301 Do not forget that second head supports only 16 and 32 bpp
1302 packed pixels, so it is a good idea to compile them into the kernel
1303 too. You can use only some font widths, as the driver uses generic
1304 painting procedures (the secondary head does not use acceleration
1307 G450/G550 hardware can display TV picture only from secondary CRTC,
1308 and it performs no scaling, so picture must have 525 or 625 lines.
1310 config FB_MATROX_I2C
1311 tristate "Matrox I2C support"
1312 depends on FB_MATROX
1315 This drivers creates I2C buses which are needed for accessing the
1316 DDC (I2C) bus present on all Matroxes, an I2C bus which
1317 interconnects Matrox optional devices, like MGA-TVO on G200 and
1318 G400, and the secondary head DDC bus, present on G400 only.
1320 You can say Y or M here if you want to experiment with monitor
1321 detection code. You must say Y or M here if you want to use either
1322 second head of G400 or MGA-TVO on G200 or G400.
1324 If you compile it as module, it will create a module named
1327 config FB_MATROX_MAVEN
1328 tristate "G400 second head support"
1329 depends on FB_MATROX_G && FB_MATROX_I2C
1331 WARNING !!! This support does not work with G450 !!!
1333 Say Y or M here if you want to use a secondary head (meaning two
1334 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1335 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1336 secondary head output is blanked while you are in X. With XFree
1337 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1338 the fbdev driver on first head and the fbdev driver on second head.
1340 If you compile it as module, two modules are created,
1341 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1342 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1343 also load i2c-matroxfb to get it to run.
1345 The driver starts in monitor mode and you must use the matroxset
1347 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1348 PAL or NTSC or to swap primary and secondary head outputs.
1349 Secondary head driver also always start in 640x480 resolution, you
1350 must use fbset to change it.
1352 Also do not forget that second head supports only 16 and 32 bpp
1353 packed pixels, so it is a good idea to compile them into the kernel
1354 too. You can use only some font widths, as the driver uses generic
1355 painting procedures (the secondary head does not use acceleration
1359 tristate "ATI Radeon display support"
1360 depends on FB && PCI
1361 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1362 select FB_MODE_HELPERS
1363 select FB_CFB_FILLRECT
1364 select FB_CFB_COPYAREA
1365 select FB_CFB_IMAGEBLIT
1366 select FB_MACMODES if PPC_OF
1368 Choose this option if you want to use an ATI Radeon graphics card as
1369 a framebuffer device. There are both PCI and AGP versions. You
1370 don't need to choose this to run the Radeon in plain VGA mode.
1372 There is a product page at
1373 http://products.amd.com/en-us/GraphicCardResult.aspx
1375 config FB_RADEON_I2C
1376 bool "DDC/I2C for ATI Radeon support"
1377 depends on FB_RADEON
1381 Say Y here if you want DDC/I2C support for your Radeon board.
1383 config FB_RADEON_BACKLIGHT
1384 bool "Support for backlight control"
1385 depends on FB_RADEON
1388 Say Y here if you want to control the backlight of your display.
1390 config FB_RADEON_DEBUG
1391 bool "Lots of debug output from Radeon driver"
1392 depends on FB_RADEON
1395 Say Y here if you want the Radeon driver to output all sorts
1396 of debugging information to provide to the maintainer when
1397 something goes wrong.
1400 tristate "ATI Rage128 display support"
1401 depends on FB && PCI
1402 select FB_CFB_FILLRECT
1403 select FB_CFB_COPYAREA
1404 select FB_CFB_IMAGEBLIT
1405 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1406 select FB_MACMODES if PPC_PMAC
1408 This driver supports graphics boards with the ATI Rage128 chips.
1409 Say Y if you have such a graphics board and read
1410 <file:Documentation/fb/aty128fb.txt>.
1412 To compile this driver as a module, choose M here: the
1413 module will be called aty128fb.
1415 config FB_ATY128_BACKLIGHT
1416 bool "Support for backlight control"
1417 depends on FB_ATY128
1420 Say Y here if you want to control the backlight of your display.
1423 tristate "ATI Mach64 display support" if PCI || ATARI
1424 depends on FB && !SPARC32
1425 select FB_CFB_FILLRECT
1426 select FB_CFB_COPYAREA
1427 select FB_CFB_IMAGEBLIT
1428 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1429 select FB_MACMODES if PPC
1431 This driver supports graphics boards with the ATI Mach64 chips.
1432 Say Y if you have such a graphics board.
1434 To compile this driver as a module, choose M here: the
1435 module will be called atyfb.
1438 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1439 depends on PCI && FB_ATY
1440 default y if SPARC64 && PCI
1442 Say Y here to support use of ATI's 64-bit Rage boards (or other
1443 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1444 framebuffer device. The ATI product support page for these boards
1445 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1447 config FB_ATY_GENERIC_LCD
1448 bool "Mach64 generic LCD support"
1449 depends on FB_ATY_CT
1451 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1452 Rage XC, or Rage XL chipset.
1455 bool "Mach64 GX support" if PCI
1459 Say Y here to support use of the ATI Mach64 Graphics Expression
1460 board (or other boards based on the Mach64 GX chipset) as a
1461 framebuffer device. The ATI product support page for these boards
1463 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1465 config FB_ATY_BACKLIGHT
1466 bool "Support for backlight control"
1470 Say Y here if you want to control the backlight of your display.
1473 tristate "S3 Trio/Virge support"
1474 depends on FB && PCI
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1478 select FB_TILEBLITTING
1481 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1483 Driver for graphics boards with S3 Trio / S3 Virge chip.
1486 bool "DDC for S3 support"
1491 Say Y here if you want DDC support for your S3 graphics card.
1494 tristate "S3 Savage support"
1495 depends on FB && PCI
1496 select FB_MODE_HELPERS
1497 select FB_CFB_FILLRECT
1498 select FB_CFB_COPYAREA
1499 select FB_CFB_IMAGEBLIT
1502 This driver supports notebooks and computers with S3 Savage PCI/AGP
1505 Say Y if you have such a graphics card.
1507 To compile this driver as a module, choose M here; the module
1508 will be called savagefb.
1510 config FB_SAVAGE_I2C
1511 bool "Enable DDC2 Support"
1512 depends on FB_SAVAGE
1515 This enables I2C support for S3 Savage Chipsets. This is used
1516 only for getting EDID information from the attached display
1517 allowing for robust video mode handling and switching.
1519 Because fbdev-2.6 requires that drivers must be able to
1520 independently validate video mode parameters, you should say Y
1523 config FB_SAVAGE_ACCEL
1524 bool "Enable Console Acceleration"
1525 depends on FB_SAVAGE
1528 This option will compile in console acceleration support. If
1529 the resulting framebuffer console has bothersome glitches, then
1533 tristate "SiS/XGI display support"
1534 depends on FB && PCI
1535 select FB_CFB_FILLRECT
1536 select FB_CFB_COPYAREA
1537 select FB_CFB_IMAGEBLIT
1538 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1540 This is the frame buffer device driver for the SiS 300, 315, 330
1541 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1542 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1544 To compile this driver as a module, choose M here; the module
1545 will be called sisfb.
1548 bool "SiS 300 series support"
1551 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1554 bool "SiS 315/330/340 series and XGI support"
1557 Say Y here to support use of the SiS 315, 330 and 340 series
1558 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1559 as XGI V3XT, V5, V8 and Z7.
1562 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1563 depends on FB && PCI && X86
1564 select FB_CFB_FILLRECT
1565 select FB_CFB_COPYAREA
1566 select FB_CFB_IMAGEBLIT
1571 This is the frame buffer device driver for Graphics chips of VIA
1572 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1573 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1575 Say Y if you have a VIA UniChrome graphics board.
1577 To compile this driver as a module, choose M here: the
1578 module will be called viafb.
1582 config FB_VIA_DIRECT_PROCFS
1583 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1587 Allow direct hardware access to some output registers via procfs.
1588 This is dangerous but may provide the only chance to get the
1589 correct output device configuration.
1590 Its use is strongly discouraged.
1592 config FB_VIA_X_COMPATIBILITY
1593 bool "X server compatibility"
1597 This option reduces the functionality (power saving, ...) of the
1598 framebuffer to avoid negative impact on the OpenChrome X server.
1599 If you use any X server other than fbdev you should enable this
1600 otherwise it should be safe to disable it and allow using all
1606 tristate "NeoMagic display support"
1607 depends on FB && PCI
1608 select FB_MODE_HELPERS
1609 select FB_CFB_FILLRECT
1610 select FB_CFB_COPYAREA
1611 select FB_CFB_IMAGEBLIT
1614 This driver supports notebooks with NeoMagic PCI chips.
1615 Say Y if you have such a graphics card.
1617 To compile this driver as a module, choose M here: the
1618 module will be called neofb.
1621 tristate "IMG Kyro support"
1622 depends on FB && PCI
1623 select FB_CFB_FILLRECT
1624 select FB_CFB_COPYAREA
1625 select FB_CFB_IMAGEBLIT
1627 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1630 To compile this driver as a module, choose M here: the
1631 module will be called kyrofb.
1634 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1635 depends on FB && PCI
1636 select FB_CFB_IMAGEBLIT
1637 select FB_CFB_FILLRECT
1638 select FB_CFB_COPYAREA
1639 select FB_MODE_HELPERS
1641 This driver supports graphics boards with the 3Dfx Banshee,
1642 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1643 such a graphics board.
1645 To compile this driver as a module, choose M here: the
1646 module will be called tdfxfb.
1648 config FB_3DFX_ACCEL
1649 bool "3Dfx Acceleration functions"
1652 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1653 device driver with acceleration functions.
1656 bool "Enable DDC/I2C support"
1661 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1664 tristate "3Dfx Voodoo Graphics (sst1) support"
1665 depends on FB && PCI
1666 select FB_CFB_FILLRECT
1667 select FB_CFB_COPYAREA
1668 select FB_CFB_IMAGEBLIT
1670 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1671 Voodoo2 (cvg) based graphics card.
1673 To compile this driver as a module, choose M here: the
1674 module will be called sstfb.
1676 WARNING: Do not use any application that uses the 3D engine
1677 (namely glide) while using this driver.
1678 Please read the <file:Documentation/fb/sstfb.txt> for supported
1679 options and other important info support.
1682 tristate "VIA VT8623 support"
1683 depends on FB && PCI
1684 select FB_CFB_FILLRECT
1685 select FB_CFB_COPYAREA
1686 select FB_CFB_IMAGEBLIT
1687 select FB_TILEBLITTING
1690 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1692 Driver for CastleRock integrated graphics core in the
1693 VIA VT8623 [Apollo CLE266] chipset.
1696 tristate "Trident/CyberXXX/CyberBlade support"
1697 depends on FB && PCI
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1702 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1703 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1705 There are also integrated versions of these chips called CyberXXXX,
1706 CyberImage or CyberBlade. These chips are mostly found in laptops
1707 but also on some motherboards including early VIA EPIA motherboards.
1708 For more information, read <file:Documentation/fb/tridentfb.txt>
1710 Say Y if you have such a graphics board.
1712 To compile this driver as a module, choose M here: the
1713 module will be called tridentfb.
1716 tristate "ARK 2000PV support"
1717 depends on FB && PCI
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1721 select FB_TILEBLITTING
1724 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1726 Driver for PCI graphics boards with ARK 2000PV chip
1727 and ICS 5342 RAMDAC.
1730 tristate "Permedia3 support"
1731 depends on FB && PCI
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1736 This is the frame buffer device driver for the 3DLabs Permedia3
1737 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1738 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1739 and maybe other boards.
1742 tristate "Fujitsu carmine frame buffer support"
1743 depends on FB && PCI
1744 select FB_CFB_FILLRECT
1745 select FB_CFB_COPYAREA
1746 select FB_CFB_IMAGEBLIT
1748 This is the frame buffer device driver for the Fujitsu Carmine chip.
1749 The driver provides two independent frame buffer devices.
1752 depends on FB_CARMINE
1753 prompt "DRAM timing"
1754 default FB_CARMINE_DRAM_EVAL
1756 config FB_CARMINE_DRAM_EVAL
1757 bool "Eval board timings"
1759 Use timings which work on the eval card.
1761 config CARMINE_DRAM_CUSTOM
1762 bool "Custom board timings"
1764 Use custom board timings.
1768 bool "Au1100 LCD Driver"
1769 depends on (FB = y) && MIPS_ALCHEMY
1770 select FB_CFB_FILLRECT
1771 select FB_CFB_COPYAREA
1772 select FB_CFB_IMAGEBLIT
1774 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1775 various panels and CRTs by passing in kernel cmd line option
1776 au1100fb:panel=<name>.
1779 bool "Au1200/Au1300 LCD Driver"
1780 depends on (FB = y) && MIPS_ALCHEMY
1781 select FB_SYS_FILLRECT
1782 select FB_SYS_COPYAREA
1783 select FB_SYS_IMAGEBLIT
1786 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1787 It can drive various panels and CRTs by passing in kernel cmd line
1788 option au1200fb:panel=<name>.
1791 bool "VIA VT8500 framebuffer support"
1792 depends on (FB = y) && ARM && ARCH_VT8500
1793 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1794 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1795 select FB_SYS_IMAGEBLIT
1796 select FB_MODE_HELPERS
1797 select VIDEOMODE_HELPERS
1799 This is the framebuffer driver for VIA VT8500 integrated LCD
1803 bool "Wondermedia WM8xxx-series frame buffer support"
1804 depends on (FB = y) && ARM && ARCH_VT8500
1805 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1806 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1807 select FB_SYS_IMAGEBLIT
1808 select FB_MODE_HELPERS
1809 select VIDEOMODE_HELPERS
1811 This is the framebuffer driver for WonderMedia WM8xxx-series
1812 integrated LCD controller. This driver covers the WM8505, WM8650
1815 config FB_WMT_GE_ROPS
1816 bool "VT8500/WM8xxx accelerated raster ops support"
1817 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1820 This adds support for accelerated raster operations on the
1821 VIA VT8500 and Wondermedia 85xx series SoCs.
1823 source "drivers/video/geode/Kconfig"
1826 tristate "HD64461 Frame Buffer support"
1827 depends on FB && HD64461
1828 select FB_CFB_FILLRECT
1829 select FB_CFB_COPYAREA
1830 select FB_CFB_IMAGEBLIT
1832 This is the frame buffer device driver for the Hitachi HD64461 LCD
1836 bool "PMAG-AA TURBOchannel framebuffer support"
1837 depends on (FB = y) && TC
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1843 used mainly in the MIPS-based DECstation series.
1846 tristate "PMAG-BA TURBOchannel framebuffer support"
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1853 used mainly in the MIPS-based DECstation series.
1856 tristate "PMAGB-B TURBOchannel framebuffer support"
1858 select FB_CFB_FILLRECT
1859 select FB_CFB_COPYAREA
1860 select FB_CFB_IMAGEBLIT
1862 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1863 in the MIPS-based DECstation series. The card is currently only
1864 supported in 1280x1024x8 mode.
1867 bool "Maxine (Personal DECstation) onboard framebuffer support"
1868 depends on (FB = y) && MACH_DECSTATION
1869 select FB_CFB_FILLRECT
1870 select FB_CFB_COPYAREA
1871 select FB_CFB_IMAGEBLIT
1873 Support for the onboard framebuffer (1024x768x8) in the Personal
1874 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1878 bool "G364 frame buffer support"
1879 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1880 select FB_CFB_FILLRECT
1881 select FB_CFB_COPYAREA
1882 select FB_CFB_IMAGEBLIT
1884 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1885 Olivetti M700-10 systems.
1888 bool "Motorola 68328 native frame buffer support"
1889 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1890 select FB_CFB_FILLRECT
1891 select FB_CFB_COPYAREA
1892 select FB_CFB_IMAGEBLIT
1894 Say Y here if you want to support the built-in frame buffer of
1895 the Motorola 68328 CPU family.
1898 tristate "PXA168/910 LCD framebuffer support"
1899 depends on FB && (CPU_PXA168 || CPU_PXA910)
1900 select FB_CFB_FILLRECT
1901 select FB_CFB_COPYAREA
1902 select FB_CFB_IMAGEBLIT
1904 Frame buffer driver for the built-in LCD controller in the Marvell
1908 tristate "PXA LCD framebuffer support"
1909 depends on FB && ARCH_PXA
1910 select FB_CFB_FILLRECT
1911 select FB_CFB_COPYAREA
1912 select FB_CFB_IMAGEBLIT
1914 Frame buffer driver for the built-in LCD controller in the Intel
1917 This driver is also available as a module ( = code which can be
1918 inserted and removed from the running kernel whenever you want). The
1919 module will be called pxafb. If you want to compile it as a module,
1920 say M here and read <file:Documentation/kbuild/modules.txt>.
1924 config FB_PXA_OVERLAY
1925 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1927 depends on FB_PXA && (PXA27x || PXA3xx)
1929 config FB_PXA_SMARTPANEL
1930 bool "PXA Smartpanel LCD support"
1934 config FB_PXA_PARAMETERS
1935 bool "PXA LCD command line parameters"
1939 Enable the use of kernel command line or module parameters
1940 to configure the physical properties of the LCD panel when
1941 using the PXA LCD driver.
1943 This option allows you to override the panel parameters
1944 supplied by the platform in order to support multiple
1945 different models of flatpanel. If you will only be using a
1946 single model of flatpanel then you can safely leave this
1949 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1952 tristate "PXA3xx 2D graphics accelerator driver"
1955 Kernelspace driver for the 2D graphics controller unit (GCU)
1956 found on PXA3xx processors. There is a counterpart driver in the
1957 DirectFB suite, see http://www.directfb.org/
1959 If you compile this as a module, it will be called pxa3xx_gcu.
1962 tristate "2700G LCD framebuffer support"
1963 depends on FB && ARCH_PXA
1964 select FB_CFB_FILLRECT
1965 select FB_CFB_COPYAREA
1966 select FB_CFB_IMAGEBLIT
1968 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1972 bool "Enable debugging info via debugfs"
1973 depends on FB_MBX && DEBUG_FS
1976 Enable this if you want debugging information using the debug
1977 filesystem (debugfs)
1982 tristate "Freescale DIU framebuffer support"
1983 depends on FB && FSL_SOC
1984 select FB_MODE_HELPERS
1985 select FB_CFB_FILLRECT
1986 select FB_CFB_COPYAREA
1987 select FB_CFB_IMAGEBLIT
1988 select PPC_LIB_RHEAP
1990 Framebuffer driver for the Freescale SoC DIU
1993 tristate "W100 frame buffer support"
1994 depends on FB && ARCH_PXA
1995 select FB_CFB_FILLRECT
1996 select FB_CFB_COPYAREA
1997 select FB_CFB_IMAGEBLIT
1999 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2000 It can also drive the w3220 chip found on iPAQ hx4700.
2002 This driver is also available as a module ( = code which can be
2003 inserted and removed from the running kernel whenever you want). The
2004 module will be called w100fb. If you want to compile it as a module,
2005 say M here and read <file:Documentation/kbuild/modules.txt>.
2009 config FB_SH_MOBILE_LCDC
2010 tristate "SuperH Mobile LCDC framebuffer support"
2011 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2012 select FB_SYS_FILLRECT
2013 select FB_SYS_COPYAREA
2014 select FB_SYS_IMAGEBLIT
2016 select FB_DEFERRED_IO
2018 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2020 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2022 config FB_SH_MOBILE_HDMI
2023 tristate "SuperH Mobile HDMI controller support"
2024 depends on FB_SH_MOBILE_LCDC
2025 select FB_MODE_HELPERS
2030 Driver for the on-chip SH-Mobile HDMI controller.
2033 tristate "Toshiba Mobile IO FrameBuffer support"
2034 depends on FB && MFD_CORE
2035 select FB_CFB_FILLRECT
2036 select FB_CFB_COPYAREA
2037 select FB_CFB_IMAGEBLIT
2039 Frame buffer driver for the Toshiba Mobile IO integrated as found
2040 on the Sharp SL-6000 series
2042 This driver is also available as a module ( = code which can be
2043 inserted and removed from the running kernel whenever you want). The
2044 module will be called tmiofb. If you want to compile it as a module,
2045 say M here and read <file:Documentation/kbuild/modules.txt>.
2049 config FB_TMIO_ACCELL
2050 bool "tmiofb acceleration"
2055 tristate "Samsung S3C framebuffer support"
2056 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2057 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2058 select FB_CFB_FILLRECT
2059 select FB_CFB_COPYAREA
2060 select FB_CFB_IMAGEBLIT
2062 Frame buffer driver for the built-in FB controller in the Samsung
2063 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2064 and the S3C64XX series such as the S3C6400 and S3C6410.
2066 These chips all have the same basic framebuffer design with the
2067 actual capabilities depending on the chip. For instance the S3C6400
2068 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2069 currently only have two.
2071 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2073 config FB_S3C_DEBUG_REGWRITE
2074 bool "Debug register writes"
2077 Show all register writes via pr_debug()
2080 tristate "S3C2410 LCD framebuffer support"
2081 depends on FB && ARCH_S3C24XX
2082 select FB_CFB_FILLRECT
2083 select FB_CFB_COPYAREA
2084 select FB_CFB_IMAGEBLIT
2086 Frame buffer driver for the built-in LCD controller in the Samsung
2089 This driver is also available as a module ( = code which can be
2090 inserted and removed from the running kernel whenever you want). The
2091 module will be called s3c2410fb. If you want to compile it as a module,
2092 say M here and read <file:Documentation/kbuild/modules.txt>.
2095 config FB_S3C2410_DEBUG
2096 bool "S3C2410 lcd debug messages"
2097 depends on FB_S3C2410
2099 Turn on debugging messages. Note that you can set/unset at run time
2103 bool "NUC900 LCD framebuffer support"
2104 depends on FB && ARCH_W90X900
2105 select FB_CFB_FILLRECT
2106 select FB_CFB_COPYAREA
2107 select FB_CFB_IMAGEBLIT
2109 Frame buffer driver for the built-in LCD controller in the Nuvoton
2112 config GPM1040A0_320X240
2113 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2114 depends on FB_NUC900
2117 tristate "Silicon Motion SM501 framebuffer support"
2118 depends on FB && MFD_SM501
2119 select FB_CFB_FILLRECT
2120 select FB_CFB_COPYAREA
2121 select FB_CFB_IMAGEBLIT
2123 Frame buffer driver for the CRT and LCD controllers in the Silicon
2126 This driver is also available as a module ( = code which can be
2127 inserted and removed from the running kernel whenever you want). The
2128 module will be called sm501fb. If you want to compile it as a module,
2129 say M here and read <file:Documentation/kbuild/modules.txt>.
2134 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2135 depends on FB && USB
2136 select FB_MODE_HELPERS
2137 select FB_SYS_FILLRECT
2138 select FB_SYS_COPYAREA
2139 select FB_SYS_IMAGEBLIT
2141 select FB_DEFERRED_IO
2143 This is a kernel framebuffer driver for SMSC UFX USB devices.
2144 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2145 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2147 To compile as a module, choose M here: the module name is smscufx.
2150 tristate "Displaylink USB Framebuffer support"
2151 depends on FB && USB
2152 select FB_MODE_HELPERS
2153 select FB_SYS_FILLRECT
2154 select FB_SYS_COPYAREA
2155 select FB_SYS_IMAGEBLIT
2157 select FB_DEFERRED_IO
2159 This is a kernel framebuffer driver for DisplayLink USB devices.
2160 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2161 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2162 To compile as a module, choose M here: the module name is udlfb.
2164 config FB_IBM_GXT4500
2165 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2166 depends on FB && PPC
2167 select FB_CFB_FILLRECT
2168 select FB_CFB_COPYAREA
2169 select FB_CFB_IMAGEBLIT
2171 Say Y here to enable support for the IBM GXT4000P/6000P and
2172 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2173 found on some IBM System P (pSeries) machines. This driver
2174 doesn't use Geometry Engine GT1000.
2177 tristate "PS3 GPU framebuffer driver"
2178 depends on FB && PS3_PS3AV
2179 select FB_SYS_FILLRECT
2180 select FB_SYS_COPYAREA
2181 select FB_SYS_IMAGEBLIT
2183 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2185 Include support for the virtual frame buffer in the PS3 platform.
2187 config FB_PS3_DEFAULT_SIZE_M
2188 int "PS3 default frame buffer size (in MiB)"
2192 This is the default size (in MiB) of the virtual frame buffer in
2194 The default value can be overridden on the kernel command line
2195 using the "ps3fb" option (e.g. "ps3fb=9M");
2198 tristate "Xilinx frame buffer support"
2199 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2200 select FB_CFB_FILLRECT
2201 select FB_CFB_COPYAREA
2202 select FB_CFB_IMAGEBLIT
2204 Include support for the Xilinx ML300/ML403 reference design
2205 framebuffer. ML300 carries a 640*480 LCD display on the board,
2206 ML403 uses a standard DB15 VGA connector.
2209 tristate "Goldfish Framebuffer"
2210 depends on FB && HAS_DMA
2211 select FB_CFB_FILLRECT
2212 select FB_CFB_COPYAREA
2213 select FB_CFB_IMAGEBLIT
2215 Framebuffer driver for Goldfish Virtual Platform
2218 tristate "Cobalt server LCD frame buffer support"
2219 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2222 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2223 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2224 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2225 select FB_CFB_FILLRECT
2226 select FB_CFB_COPYAREA
2227 select FB_CFB_IMAGEBLIT
2229 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2230 (D)STN/TFT LCD Controller.
2231 Supports display resolutions up to 1024x1024 pixel, grayscale and
2232 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2233 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2234 panels <= 320 pixel horizontal resolution.
2237 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2238 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2239 select FB_CFB_FILLRECT
2240 select FB_CFB_COPYAREA
2241 select FB_CFB_IMAGEBLIT
2242 select FB_CFB_REV_PIXELS_IN_BYTE
2243 select FB_MODE_HELPERS
2244 select VIDEOMODE_HELPERS
2246 This is the frame buffer device driver for the TI LCD controller
2247 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2251 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2253 select FB_SYS_FILLRECT
2254 select FB_SYS_COPYAREA
2255 select FB_SYS_IMAGEBLIT
2258 This is a `virtual' frame buffer device. It operates on a chunk of
2259 unswappable kernel memory instead of on the memory of a graphics
2260 board. This means you cannot see any output sent to this frame
2261 buffer device, while it does consume precious memory. The main use
2262 of this frame buffer device is testing and debugging the frame
2263 buffer subsystem. Do NOT enable it for normal systems! To protect
2264 the innocent, it has to be enabled explicitly at boot time using the
2265 kernel option `video=vfb:'.
2267 To compile this driver as a module, choose M here: the
2268 module will be called vfb. In order to load it, you must use
2269 the vfb_enable=1 option.
2273 config XEN_FBDEV_FRONTEND
2274 tristate "Xen virtual frame buffer support"
2275 depends on FB && XEN
2276 select FB_SYS_FILLRECT
2277 select FB_SYS_COPYAREA
2278 select FB_SYS_IMAGEBLIT
2280 select FB_DEFERRED_IO
2281 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2282 select XEN_XENBUS_FRONTEND
2285 This driver implements the front-end of the Xen virtual
2286 frame buffer driver. It communicates with a back-end
2290 tristate "E-Ink Metronome/8track controller support"
2292 select FB_SYS_FILLRECT
2293 select FB_SYS_COPYAREA
2294 select FB_SYS_IMAGEBLIT
2296 select FB_DEFERRED_IO
2298 This driver implements support for the E-Ink Metronome
2299 controller. The pre-release name for this device was 8track
2300 and could also have been called by some vendors as PVI-nnnn.
2303 tristate "Fujitsu MB862xx GDC support"
2305 depends on PCI || (OF && PPC)
2306 select FB_CFB_FILLRECT
2307 select FB_CFB_COPYAREA
2308 select FB_CFB_IMAGEBLIT
2310 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2313 prompt "GDC variant"
2314 depends on FB_MB862XX
2316 config FB_MB862XX_PCI_GDC
2317 bool "Carmine/Coral-P(A) GDC"
2320 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2321 PCI graphics controller devices.
2323 config FB_MB862XX_LIME
2325 depends on OF && PPC
2326 select FB_FOREIGN_ENDIAN
2327 select FB_LITTLE_ENDIAN
2329 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2333 config FB_MB862XX_I2C
2334 bool "Support I2C bus on MB862XX GDC"
2335 depends on FB_MB862XX && I2C
2338 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2339 driver to support accessing I2C devices on controller's I2C bus.
2340 These are usually some video decoder chips.
2343 tristate "EP93XX frame buffer support"
2344 depends on FB && ARCH_EP93XX
2345 select FB_CFB_FILLRECT
2346 select FB_CFB_COPYAREA
2347 select FB_CFB_IMAGEBLIT
2349 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2350 This driver is also available as a module. The module will be called
2353 config FB_PRE_INIT_FB
2354 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2355 depends on FB && FB_MB862XX_LIME
2357 Select this option if display contents should be inherited as set by
2361 tristate "MSM Framebuffer support"
2362 depends on FB && ARCH_MSM
2363 select FB_CFB_FILLRECT
2364 select FB_CFB_COPYAREA
2365 select FB_CFB_IMAGEBLIT
2368 tristate "MX3 Framebuffer support"
2369 depends on FB && MX3_IPU
2370 select FB_CFB_FILLRECT
2371 select FB_CFB_COPYAREA
2372 select FB_CFB_IMAGEBLIT
2375 This is a framebuffer device for the i.MX31 LCD Controller. So
2376 far only synchronous displays are supported. If you plan to use
2377 an LCD display with your i.MX31 system, say Y here.
2379 config FB_BROADSHEET
2380 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2382 select FB_SYS_FILLRECT
2383 select FB_SYS_COPYAREA
2384 select FB_SYS_IMAGEBLIT
2386 select FB_DEFERRED_IO
2388 This driver implements support for the E-Ink Broadsheet
2389 controller. The release name for this device was Epson S1D13521
2390 and could also have been called by other names when coupled with
2394 tristate "AUO-K190X EPD controller support"
2396 select FB_SYS_FILLRECT
2397 select FB_SYS_COPYAREA
2398 select FB_SYS_IMAGEBLIT
2400 select FB_DEFERRED_IO
2402 Provides support for epaper controllers from the K190X series
2403 of AUO. These controllers can be used to drive epaper displays
2406 This option enables the common support, shared by the individual
2407 controller drivers. You will also have to enable the driver
2408 for the controller type used in your device.
2411 tristate "AUO-K1900 EPD controller support"
2412 depends on FB && FB_AUO_K190X
2414 This driver implements support for the AUO K1900 epd-controller.
2415 This controller can drive Sipix epaper displays but can only do
2416 serial updates, reducing the number of possible frames per second.
2419 tristate "AUO-K1901 EPD controller support"
2420 depends on FB && FB_AUO_K190X
2422 This driver implements support for the AUO K1901 epd-controller.
2423 This controller can drive Sipix epaper displays and supports
2424 concurrent updates, making higher frames per second possible.
2427 tristate "JZ4740 LCD framebuffer support"
2428 depends on FB && MACH_JZ4740
2429 select FB_SYS_FILLRECT
2430 select FB_SYS_COPYAREA
2431 select FB_SYS_IMAGEBLIT
2433 Framebuffer support for the JZ4740 SoC.
2436 tristate "MXS LCD framebuffer support"
2437 depends on FB && ARCH_MXS
2438 select FB_CFB_FILLRECT
2439 select FB_CFB_COPYAREA
2440 select FB_CFB_IMAGEBLIT
2441 select FB_MODE_HELPERS
2442 select VIDEOMODE_HELPERS
2444 Framebuffer support for the MXS SoC.
2446 config FB_PUV3_UNIGFX
2447 tristate "PKUnity v3 Unigfx framebuffer support"
2448 depends on FB && UNICORE32 && ARCH_PUV3
2449 select FB_SYS_FILLRECT
2450 select FB_SYS_COPYAREA
2451 select FB_SYS_IMAGEBLIT
2454 Choose this option if you want to use the Unigfx device as a
2455 framebuffer device. Without the support of PCI & AGP.
2458 tristate "Microsoft Hyper-V Synthetic Video support"
2459 depends on FB && HYPERV
2460 select FB_CFB_FILLRECT
2461 select FB_CFB_COPYAREA
2462 select FB_CFB_IMAGEBLIT
2464 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2467 bool "Simple framebuffer support"
2469 select FB_CFB_FILLRECT
2470 select FB_CFB_COPYAREA
2471 select FB_CFB_IMAGEBLIT
2473 Say Y if you want support for a simple frame-buffer.
2475 This driver assumes that the display hardware has been initialized
2476 before the kernel boots, and the kernel will simply render to the
2477 pre-allocated frame buffer surface.
2479 Configuration re: surface address, size, and format must be provided
2480 through device tree, or plain old platform data.
2482 source "drivers/video/omap/Kconfig"
2483 source "drivers/video/omap2/Kconfig"
2484 source "drivers/video/exynos/Kconfig"
2485 source "drivers/video/mmp/Kconfig"
2486 source "drivers/video/backlight/Kconfig"
2489 source "drivers/video/console/Kconfig"
2492 if FB || SGI_NEWPORT_CONSOLE
2493 source "drivers/video/logo/Kconfig"
2496 config FB_SH_MOBILE_MERAM
2497 tristate "SuperH Mobile MERAM read ahead support"
2498 depends on (SUPERH || ARCH_SHMOBILE)
2499 select GENERIC_ALLOCATOR
2501 Enable MERAM support for the SuperH controller.
2503 This will allow for caching of the framebuffer to provide more
2504 reliable access under heavy main memory bus traffic situations.
2505 Up to 4 memory channels can be configured, allowing 4 RGB or
2506 2 YCbCr framebuffers to be configured.
2509 tristate "Solomon SSD1307 framebuffer support"
2510 depends on FB && I2C
2514 select FB_SYS_FILLRECT
2515 select FB_SYS_COPYAREA
2516 select FB_SYS_IMAGEBLIT
2517 select FB_DEFERRED_IO
2520 This driver implements support for the Solomon SSD1307
2521 OLED controller over I2C.