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/drm/Kconfig"
28 config VIDEO_OUTPUT_CONTROL
29 tristate "Lowlevel video output switch controls"
31 This framework adds support for low-level control of the video
40 config OF_DISPLAY_TIMING
41 bool "Enable device tree display timing support"
45 helper to parse display timings from the devicetree
48 bool "Enable device tree videomode support"
51 select OF_DISPLAY_TIMING
53 helper to get videomodes from the devicetree
59 tristate "Support for frame buffer devices"
61 The frame buffer device provides an abstraction for the graphics
62 hardware. It represents the frame buffer of some video hardware and
63 allows application software to access the graphics hardware through
64 a well-defined interface, so the software doesn't need to know
65 anything about the low-level (hardware register) stuff.
67 Frame buffer devices work identically across the different
68 architectures supported by Linux and make the implementation of
69 application programs easier and more portable; at this point, an X
70 server exists which uses the frame buffer device exclusively.
71 On several non-X86 architectures, the frame buffer device is the
72 only way to use the graphics hardware.
74 The device is accessed through special device nodes, usually located
75 in the /dev directory, i.e. /dev/fb*.
77 You need an utility program called fbset to make full use of frame
78 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
79 and the Framebuffer-HOWTO at
80 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
83 Say Y here and to the driver for your graphics board below if you
84 are compiling a kernel for a non-x86 architecture.
86 If you are compiling for the x86 architecture, you can say Y if you
87 want to play with it, but it is not essential. Please note that
88 running graphical applications that directly touch the hardware
89 (e.g. an accelerated X server) and that are not frame buffer
90 device-aware may cause unexpected results. If unsure, say N.
93 bool "Enable firmware EDID"
97 This enables access to the EDID transferred from the firmware.
98 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
99 transfers do not work for your driver and if you are using
100 nvidiafb, i810fb or savagefb.
102 In general, choosing Y for this option is safe. If you
103 experience extremely long delays while booting before you get
104 something on your display, try setting this to N. Matrox cards in
105 combination with certain motherboards and monitors are known to
106 suffer from this problem.
115 config FB_BOOT_VESA_SUPPORT
120 If true, at least one selected framebuffer driver can take advantage
121 of VESA video modes set at an early boot stage via the vga= parameter.
123 config FB_CFB_FILLRECT
128 Include the cfb_fillrect function for generic software rectangle
129 filling. This is used by drivers that don't provide their own
130 (accelerated) version.
132 config FB_CFB_COPYAREA
137 Include the cfb_copyarea function for generic software area copying.
138 This is used by drivers that don't provide their own (accelerated)
141 config FB_CFB_IMAGEBLIT
146 Include the cfb_imageblit function for generic software image
147 blitting. This is used by drivers that don't provide their own
148 (accelerated) version.
150 config FB_CFB_REV_PIXELS_IN_BYTE
155 Allow generic frame-buffer functions to work on displays with 1, 2
156 and 4 bits per pixel depths which has opposite order of pixels in
157 byte order to bytes in long order.
159 config FB_SYS_FILLRECT
164 Include the sys_fillrect function for generic software rectangle
165 filling. This is used by drivers that don't provide their own
166 (accelerated) version and the framebuffer is in system RAM.
168 config FB_SYS_COPYAREA
173 Include the sys_copyarea function for generic software area copying.
174 This is used by drivers that don't provide their own (accelerated)
175 version and the framebuffer is in system RAM.
177 config FB_SYS_IMAGEBLIT
182 Include the sys_imageblit function for generic software image
183 blitting. This is used by drivers that don't provide their own
184 (accelerated) version and the framebuffer is in system RAM.
186 menuconfig FB_FOREIGN_ENDIAN
187 bool "Framebuffer foreign endianness support"
190 This menu will let you enable support for the framebuffers with
191 non-native endianness (e.g. Little-Endian framebuffer on a
192 Big-Endian machine). Most probably you don't have such hardware,
193 so it's safe to say "n" here.
196 prompt "Choice endianness support"
197 depends on FB_FOREIGN_ENDIAN
199 config FB_BOTH_ENDIAN
200 bool "Support for Big- and Little-Endian framebuffers"
203 bool "Support for Big-Endian framebuffers only"
205 config FB_LITTLE_ENDIAN
206 bool "Support for Little-Endian framebuffers only"
215 config FB_DEFERRED_IO
222 depends on FB_DEFERRED_IO
229 Common utility functions useful to fbdev drivers of VGA-based
240 select BACKLIGHT_LCD_SUPPORT
241 select BACKLIGHT_CLASS_DEVICE
244 config FB_MODE_HELPERS
245 bool "Enable Video Mode Handling Helpers"
249 This enables functions for handling video modes using the
250 Generalized Timing Formula and the EDID parser. A few drivers rely
251 on this feature such as the radeonfb, rivafb, and the i810fb. If
252 your driver does not take advantage of this feature, choosing Y will
253 just increase the kernel size by about 5K.
255 config FB_TILEBLITTING
256 bool "Enable Tile Blitting Support"
260 This enables tile blitting. Tile blitting is a drawing technique
261 where the screen is divided into rectangular sections (tiles), whereas
262 the standard blitting divides the screen into pixels. Because the
263 default drawing element is a tile, drawing functions will be passed
264 parameters in terms of number of tiles instead of number of pixels.
265 For example, to draw a single character, instead of using bitmaps,
266 an index to an array of bitmaps will be used. To clear or move a
267 rectangular section of a screen, the rectangle will be described in
268 terms of number of tiles in the x- and y-axis.
270 This is particularly important to one driver, matroxfb. If
273 comment "Frame buffer hardware drivers"
277 tristate "Aeroflex Gaisler framebuffer support"
278 depends on FB && SPARC
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
283 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
286 tristate "Cirrus Logic support"
287 depends on FB && (ZORRO || PCI)
288 select FB_CFB_FILLRECT
289 select FB_CFB_COPYAREA
290 select FB_CFB_IMAGEBLIT
292 This enables support for Cirrus Logic GD542x/543x based boards on
293 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
295 If you have a PCI-based system, this enables support for these
296 chips: GD-543x, GD-544x, GD-5480.
298 Please read the file <file:Documentation/fb/cirrusfb.txt>.
300 Say N unless you have such a graphics board or plan to get one
301 before you next recompile the kernel.
304 tristate "Permedia2 support"
305 depends on FB && ((AMIGA && BROKEN) || PCI)
306 select FB_CFB_FILLRECT
307 select FB_CFB_COPYAREA
308 select FB_CFB_IMAGEBLIT
310 This is the frame buffer device driver for cards based on
311 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
312 The driver was tested on the following cards:
313 Diamond FireGL 1000 PRO AGP
314 ELSA Gloria Synergy PCI
315 Appian Jeronimo PRO (both heads) PCI
316 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
317 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
318 ASK Graphic Blaster Exxtreme AGP
320 To compile this driver as a module, choose M here: the
321 module will be called pm2fb.
323 config FB_PM2_FIFO_DISCONNECT
324 bool "enable FIFO disconnect feature"
325 depends on FB_PM2 && PCI
327 Support the Permedia2 FIFO disconnect feature.
330 tristate "ARM PrimeCell PL110 support"
331 depends on FB && ARM && ARM_AMBA
332 select FB_CFB_FILLRECT
333 select FB_CFB_COPYAREA
334 select FB_CFB_IMAGEBLIT
336 This framebuffer device driver is for the ARM PrimeCell PL110
337 Colour LCD controller. ARM PrimeCells provide the building
338 blocks for System on a Chip devices.
340 If you want to compile this as a module (=code which can be
341 inserted into and removed from the running kernel), say M
342 here and read <file:Documentation/kbuild/modules.txt>. The module
343 will be called amba-clcd.
346 bool "Acorn VIDC support"
347 depends on (FB = y) && ARM && ARCH_ACORN
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This is the frame buffer device driver for the Acorn VIDC graphics
353 hardware found in Acorn RISC PCs and other ARM-based machines. If
357 bool "CLPS711X LCD support"
358 depends on (FB = y) && ARM && ARCH_CLPS711X
359 select FB_CFB_FILLRECT
360 select FB_CFB_COPYAREA
361 select FB_CFB_IMAGEBLIT
363 Say Y to enable the Framebuffer driver for the CLPS7111 and
367 bool "SA-1100 LCD support"
368 depends on (FB = y) && ARM && ARCH_SA1100
369 select FB_CFB_FILLRECT
370 select FB_CFB_COPYAREA
371 select FB_CFB_IMAGEBLIT
373 This is a framebuffer device for the SA-1100 LCD Controller.
374 See <http://www.linux-fbdev.org/> for information on framebuffer
377 If you plan to use the LCD display with your SA-1100 system, say
381 tristate "Freescale i.MX1/21/25/27 LCD support"
382 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
383 select FB_CFB_FILLRECT
384 select FB_CFB_COPYAREA
385 select FB_CFB_IMAGEBLIT
388 tristate "CyberPro 2000/2010/5000 support"
389 depends on FB && PCI && (BROKEN || !SPARC64)
390 select FB_CFB_FILLRECT
391 select FB_CFB_COPYAREA
392 select FB_CFB_IMAGEBLIT
394 This enables support for the Integraphics CyberPro 20x0 and 5000
395 VGA chips used in the Rebel.com Netwinder and other machines.
396 Say Y if you have a NetWinder or a graphics card containing this
397 device, otherwise say N.
399 config FB_CYBER2000_DDC
400 bool "DDC for CyberPro support"
401 depends on FB_CYBER2000
405 Say Y here if you want DDC support for your CyberPro graphics
406 card. This is only I2C bus support, driver does not use EDID.
408 config FB_CYBER2000_I2C
409 bool "CyberPro 2000/2010/5000 I2C support"
410 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
413 Enable support for the I2C video decoder interface on the
414 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
415 on the Netwinder machines for the SAA7111 video capture.
419 depends on (FB = y) && APOLLO
421 select FB_CFB_FILLRECT
422 select FB_CFB_IMAGEBLIT
426 depends on (FB = y) && Q40
428 select FB_CFB_FILLRECT
429 select FB_CFB_COPYAREA
430 select FB_CFB_IMAGEBLIT
433 tristate "Amiga native chipset support"
434 depends on FB && AMIGA
436 This is the frame buffer device driver for the builtin graphics
437 chipset found in Amigas.
439 To compile this driver as a module, choose M here: the
440 module will be called amifb.
443 bool "Amiga OCS chipset support"
446 This enables support for the original Agnus and Denise video chips,
447 found in the Amiga 1000 and most A500's and A2000's. If you intend
448 to run Linux on any of these systems, say Y; otherwise say N.
451 bool "Amiga ECS chipset support"
454 This enables support for the Enhanced Chip Set, found in later
455 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
456 you intend to run Linux on any of these systems, say Y; otherwise
460 bool "Amiga AGA chipset support"
463 This enables support for the Advanced Graphics Architecture (also
464 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
465 and CD32. If you intend to run Linux on any of these systems, say Y;
469 bool "Amiga FrameMaster II/Rainbow II support"
470 depends on (FB = y) && ZORRO
471 select FB_CFB_FILLRECT
472 select FB_CFB_COPYAREA
473 select FB_CFB_IMAGEBLIT
475 This is the frame buffer device driver for the Amiga FrameMaster
476 card from BSC (exhibited 1992 but not shipped as a CBM product).
479 tristate "Arc Monochrome LCD board support"
481 select FB_SYS_FILLRECT
482 select FB_SYS_COPYAREA
483 select FB_SYS_IMAGEBLIT
486 This enables support for the Arc Monochrome LCD board. The board
487 is based on the KS-108 lcd controller and is typically a matrix
488 of 2*n chips. This driver was tested with a 128x64 panel. This
489 driver supports it for use with x86 SBCs through a 16 bit GPIO
490 interface (8 bit data, 8 bit control). If you anticipate using
491 this driver, say Y or M; otherwise say N. You must specify the
492 GPIO IO address to be used for setting control and data.
495 bool "Atari native chipset support"
496 depends on (FB = y) && ATARI
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
501 This is the frame buffer device driver for the builtin graphics
502 chipset found in Ataris.
505 bool "Open Firmware frame buffer device support"
506 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
512 Say Y if you want support with Open Firmware for your graphics
516 bool "Apple \"control\" display support"
517 depends on (FB = y) && PPC_PMAC && PPC32
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 This driver supports a frame buffer for the graphics adapter in the
524 Power Macintosh 7300 and others.
527 bool "Apple \"platinum\" display support"
528 depends on (FB = y) && PPC_PMAC && PPC32
529 select FB_CFB_FILLRECT
530 select FB_CFB_COPYAREA
531 select FB_CFB_IMAGEBLIT
534 This driver supports a frame buffer for the "platinum" graphics
535 adapter in some Power Macintoshes.
538 bool "Apple \"valkyrie\" display support"
539 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
545 This driver supports a frame buffer for the "valkyrie" graphics
546 adapter in some Power Macintoshes.
549 bool "Chips 65550 display support"
550 depends on (FB = y) && PPC32 && PCI
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
555 This is the frame buffer device driver for the Chips & Technologies
556 65550 graphics chip in PowerBooks.
559 bool "Asiliant (Chips) 69000 display support"
560 depends on (FB = y) && PCI
561 select FB_CFB_FILLRECT
562 select FB_CFB_COPYAREA
563 select FB_CFB_IMAGEBLIT
565 This is the frame buffer device driver for the Asiliant 69030 chipset
568 bool "IMS Twin Turbo display support"
569 depends on (FB = y) && PCI
570 select FB_CFB_IMAGEBLIT
571 select FB_MACMODES if PPC
573 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
574 many Macintosh and compatible computers.
577 tristate "VGA 16-color graphics support"
578 depends on FB && (X86 || PPC)
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
583 select FONT_8x16 if FRAMEBUFFER_CONSOLE
585 This is the frame buffer device driver for VGA 16 color graphic
586 cards. Say Y if you have such a card.
588 To compile this driver as a module, choose M here: the
589 module will be called vga16fb.
591 config FB_BF54X_LQ043
592 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
593 depends on FB && (BF54x) && !BF542
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
598 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
600 config FB_BFIN_T350MCQB
601 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
602 depends on FB && BLACKFIN
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
609 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
610 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
612 config FB_BFIN_LQ035Q1
613 tristate "SHARP LQ035Q1DH02 TFT LCD"
614 depends on FB && BLACKFIN && SPI
615 select FB_CFB_FILLRECT
616 select FB_CFB_COPYAREA
617 select FB_CFB_IMAGEBLIT
620 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
621 the Blackfin Landscape LCD EZ-Extender Card.
622 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
623 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
625 To compile this driver as a module, choose M here: the
626 module will be called bfin-lq035q1-fb.
628 config FB_BF537_LQ035
629 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
630 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
631 select FB_CFB_FILLRECT
632 select FB_CFB_COPYAREA
633 select FB_CFB_IMAGEBLIT
636 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
639 To compile this driver as a module, choose M here: the
640 module will be called bf537-lq035.
643 tristate "Blackfin ADV7393 Video encoder"
644 depends on FB && BLACKFIN
646 select FB_CFB_FILLRECT
647 select FB_CFB_COPYAREA
648 select FB_CFB_IMAGEBLIT
650 This is the framebuffer device for a ADV7393 video encoder
651 attached to a Blackfin on the PPI port.
652 If your Blackfin board has a ADV7393 select Y.
654 To compile this driver as a module, choose M here: the
655 module will be called bfin_adv7393fb.
658 prompt "Video mode support"
659 depends on FB_BFIN_7393
669 bool 'NTSC 640x480 (Experimental)'
672 bool 'PAL 640x480 (Experimental)'
675 bool 'NTSC 720x480 YCbCR input'
678 bool 'PAL 720x576 YCbCR input'
683 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
684 depends on (FB_BFIN_7393)
685 default ADV7393_1XMEM
695 tristate "HP STI frame buffer device support"
696 depends on FB && PARISC
697 select FB_CFB_FILLRECT
698 select FB_CFB_COPYAREA
699 select FB_CFB_IMAGEBLIT
704 STI refers to the HP "Standard Text Interface" which is a set of
705 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
706 Enabling this option will implement the linux framebuffer device
707 using calls to the STI BIOS routines for initialisation.
709 If you enable this option, you will get a planar framebuffer device
710 /dev/fb which will work on the most common HP graphic cards of the
711 NGLE family, including the artist chips (in the 7xx and Bxxx series),
712 HCRX, HCRX24, CRX, CRX24 and VisEG series.
714 It is safe to enable this option, so you should probably say "Y".
717 bool "Generic Macintosh display support"
718 depends on (FB = y) && MAC
719 select FB_CFB_FILLRECT
720 select FB_CFB_COPYAREA
721 select FB_CFB_IMAGEBLIT
726 depends on (FB = y) && DIO
727 select FB_CFB_IMAGEBLIT
731 tristate "TGA/SFB+ framebuffer support"
732 depends on FB && (ALPHA || TC)
733 select FB_CFB_FILLRECT
734 select FB_CFB_COPYAREA
735 select FB_CFB_IMAGEBLIT
738 This is the frame buffer device driver for generic TGA and SFB+
739 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
740 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
741 TURBOchannel cards, also known as PMAGD-A, -B and -C.
743 Due to hardware limitations ZLX-E2 and E3 cards are not supported
744 for DECstation 5000/200 systems. Additionally due to firmware
745 limitations these cards may cause troubles with booting DECstation
746 5000/240 and /260 systems, but are fully supported under Linux if
747 you manage to get it going. ;-)
749 Say Y if you have one of those.
752 tristate "Userspace VESA VGA graphics support"
753 depends on FB && CONNECTOR
754 select FB_CFB_FILLRECT
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
757 select FB_MODE_HELPERS
759 This is the frame buffer driver for generic VBE 2.0 compliant
760 graphic cards. It can also take advantage of VBE 3.0 features,
761 such as refresh rate adjustment.
763 This driver generally provides more features than vesafb but
764 requires a userspace helper application called 'v86d'. See
765 <file:Documentation/fb/uvesafb.txt> for more information.
770 bool "VESA VGA graphics support"
771 depends on (FB = y) && X86
772 select FB_CFB_FILLRECT
773 select FB_CFB_COPYAREA
774 select FB_CFB_IMAGEBLIT
775 select FB_BOOT_VESA_SUPPORT
777 This is the frame buffer device driver for generic VESA 2.0
778 compliant graphic cards. The older VESA 1.2 cards are not supported.
779 You will get a boot time penguin logo at no additional cost. Please
780 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
783 bool "EFI-based Framebuffer Support"
784 depends on (FB = y) && X86 && EFI
785 select FB_CFB_FILLRECT
786 select FB_CFB_COPYAREA
787 select FB_CFB_IMAGEBLIT
789 This is the EFI frame buffer device driver. If the firmware on
790 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
791 using the EFI framebuffer as your console.
794 tristate "N411 Apollo/Hecuba devkit support"
795 depends on FB && X86 && MMU
796 select FB_SYS_FILLRECT
797 select FB_SYS_COPYAREA
798 select FB_SYS_IMAGEBLIT
800 select FB_DEFERRED_IO
803 This enables support for the Apollo display controller in its
804 Hecuba form using the n411 devkit.
807 tristate "Hercules mono graphics support"
810 Say Y here if you have a Hercules mono graphics card.
812 To compile this driver as a module, choose M here: the
813 module will be called hgafb.
815 As this card technology is at least 25 years old,
816 most people will answer N here.
819 tristate "SGI Visual Workstation framebuffer support"
820 depends on FB && X86_VISWS
821 select FB_CFB_FILLRECT
822 select FB_CFB_COPYAREA
823 select FB_CFB_IMAGEBLIT
825 SGI Visual Workstation support for framebuffer graphics.
828 bool "SGI Graphics Backend frame buffer support"
829 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
830 select FB_CFB_FILLRECT
831 select FB_CFB_COPYAREA
832 select FB_CFB_IMAGEBLIT
834 This is the frame buffer device driver for SGI Graphics Backend.
835 This chip is used in SGI O2 and Visual Workstation 320/540.
838 int "Video memory size in MB"
842 This is the amount of memory reserved for the framebuffer,
843 which can be any value between 1MB and 8MB.
846 bool "SBUS and UPA framebuffers"
847 depends on (FB = y) && SPARC
849 Say Y if you want support for SBUS or UPA based frame buffer device.
853 depends on (FB = y) && (SPARC && FB_SBUS)
854 select FB_CFB_FILLRECT
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the frame buffer device driver for the BWtwo frame buffer.
861 bool "CGthree support"
862 depends on (FB = y) && (SPARC && FB_SBUS)
863 select FB_CFB_FILLRECT
864 select FB_CFB_COPYAREA
865 select FB_CFB_IMAGEBLIT
867 This is the frame buffer device driver for the CGthree frame buffer.
870 bool "CGsix (GX,TurboGX) support"
871 depends on (FB = y) && (SPARC && FB_SBUS)
872 select FB_CFB_COPYAREA
873 select FB_CFB_IMAGEBLIT
875 This is the frame buffer device driver for the CGsix (GX, TurboGX)
879 bool "Creator/Creator3D/Elite3D support"
880 depends on FB_SBUS && SPARC64
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
884 This is the frame buffer device driver for the Creator, Creator3D,
885 and Elite3D graphics boards.
888 bool "TCX (SS4/SS5 only) support"
890 select FB_CFB_FILLRECT
891 select FB_CFB_COPYAREA
892 select FB_CFB_IMAGEBLIT
894 This is the frame buffer device driver for the TCX 24/8bit frame
898 bool "CGfourteen (SX) support"
900 select FB_CFB_FILLRECT
901 select FB_CFB_COPYAREA
902 select FB_CFB_IMAGEBLIT
904 This is the frame buffer device driver for the CGfourteen frame
905 buffer on Desktop SPARCsystems with the SX graphics option.
908 bool "P9100 (Sparcbook 3 only) support"
910 select FB_CFB_FILLRECT
911 select FB_CFB_COPYAREA
912 select FB_CFB_IMAGEBLIT
914 This is the frame buffer device driver for the P9100 card
915 supported on Sparcbook 3 machines.
918 bool "Leo (ZX) support"
920 select FB_CFB_FILLRECT
921 select FB_CFB_COPYAREA
922 select FB_CFB_IMAGEBLIT
924 This is the frame buffer device driver for the SBUS-based Sun ZX
925 (leo) frame buffer cards.
928 bool "IGA 168x display support"
929 depends on (FB = y) && SPARC32
930 select FB_CFB_FILLRECT
931 select FB_CFB_COPYAREA
932 select FB_CFB_IMAGEBLIT
934 This is the framebuffer device for the INTERGRAPHICS 1680 and
935 successor frame buffer cards.
938 bool "Sun XVR-500 3DLABS Wildcat support"
939 depends on (FB = y) && PCI && SPARC64
940 select FB_CFB_FILLRECT
941 select FB_CFB_COPYAREA
942 select FB_CFB_IMAGEBLIT
944 This is the framebuffer device for the Sun XVR-500 and similar
945 graphics cards based upon the 3DLABS Wildcat chipset. The driver
946 only works on sparc64 systems where the system firmware has
947 mostly initialized the card already. It is treated as a
948 completely dumb framebuffer device.
951 bool "Sun XVR-2500 3DLABS Wildcat support"
952 depends on (FB = y) && PCI && SPARC64
953 select FB_CFB_FILLRECT
954 select FB_CFB_COPYAREA
955 select FB_CFB_IMAGEBLIT
957 This is the framebuffer device for the Sun XVR-2500 and similar
958 graphics cards based upon the 3DLABS Wildcat chipset. The driver
959 only works on sparc64 systems where the system firmware has
960 mostly initialized the card already. It is treated as a
961 completely dumb framebuffer device.
964 bool "Sun XVR-1000 support"
965 depends on (FB = y) && SPARC64
966 select FB_CFB_FILLRECT
967 select FB_CFB_COPYAREA
968 select FB_CFB_IMAGEBLIT
970 This is the framebuffer device for the Sun XVR-1000 and similar
971 graphics cards. The driver only works on sparc64 systems where
972 the system firmware has mostly initialized the card already. It
973 is treated as a completely dumb framebuffer device.
976 tristate "NEC PowerVR 2 display support"
977 depends on FB && SH_DREAMCAST
978 select FB_CFB_FILLRECT
979 select FB_CFB_COPYAREA
980 select FB_CFB_IMAGEBLIT
982 Say Y here if you have a PowerVR 2 card in your box. If you plan to
983 run linux on your Dreamcast, you will have to say Y here.
984 This driver may or may not work on other PowerVR 2 cards, but is
985 totally untested. Use at your own risk. If unsure, say N.
987 To compile this driver as a module, choose M here: the
988 module will be called pvr2fb.
990 You can pass several parameters to the driver at boot time or at
991 module load time. The parameters look like "video=pvr2:XXX", where
992 the meaning of XXX can be found at the end of the main source file
993 (<file:drivers/video/pvr2fb.c>). Please see the file
994 <file:Documentation/fb/pvr2fb.txt>.
997 tristate "Epson S1D13XXX framebuffer support"
999 select FB_CFB_FILLRECT
1000 select FB_CFB_COPYAREA
1001 select FB_CFB_IMAGEBLIT
1003 Support for S1D13XXX framebuffer device family (currently only
1004 working with S1D13806). Product specs at
1005 <http://vdc.epson.com/>
1008 tristate "AT91/AT32 LCD Controller support"
1009 depends on FB && HAVE_FB_ATMEL
1010 select FB_CFB_FILLRECT
1011 select FB_CFB_COPYAREA
1012 select FB_CFB_IMAGEBLIT
1014 This enables support for the AT91/AT32 LCD Controller.
1017 bool "Frame Buffer in internal SRAM"
1018 depends on FB_ATMEL && ARCH_AT91SAM9261
1020 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1021 to let frame buffer in external SDRAM.
1024 bool "Use a STN display with AT91/AT32 LCD Controller"
1025 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1028 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1029 Controller. Say N if you want to connect a TFT.
1034 tristate "nVidia Framebuffer Support"
1035 depends on FB && PCI
1036 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1037 select FB_MODE_HELPERS
1038 select FB_CFB_FILLRECT
1039 select FB_CFB_COPYAREA
1040 select FB_CFB_IMAGEBLIT
1044 This driver supports graphics boards with the nVidia chips, TNT
1045 and newer. For very old chipsets, such as the RIVA128, then use
1047 Say Y if you have such a graphics board.
1049 To compile this driver as a module, choose M here: the
1050 module will be called nvidiafb.
1052 config FB_NVIDIA_I2C
1053 bool "Enable DDC Support"
1054 depends on FB_NVIDIA
1057 This enables I2C support for nVidia Chipsets. This is used
1058 only for getting EDID information from the attached display
1059 allowing for robust video mode handling and switching.
1061 Because fbdev-2.6 requires that drivers must be able to
1062 independently validate video mode parameters, you should say Y
1065 config FB_NVIDIA_DEBUG
1066 bool "Lots of debug output"
1067 depends on FB_NVIDIA
1070 Say Y here if you want the nVidia driver to output all sorts
1071 of debugging information to provide to the maintainer when
1072 something goes wrong.
1074 config FB_NVIDIA_BACKLIGHT
1075 bool "Support for backlight control"
1076 depends on FB_NVIDIA
1079 Say Y here if you want to control the backlight of your display.
1082 tristate "nVidia Riva support"
1083 depends on FB && PCI
1084 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1085 select FB_MODE_HELPERS
1086 select FB_CFB_FILLRECT
1087 select FB_CFB_COPYAREA
1088 select FB_CFB_IMAGEBLIT
1092 This driver supports graphics boards with the nVidia Riva/Geforce
1094 Say Y if you have such a graphics board.
1096 To compile this driver as a module, choose M here: the
1097 module will be called rivafb.
1100 bool "Enable DDC Support"
1104 This enables I2C support for nVidia Chipsets. This is used
1105 only for getting EDID information from the attached display
1106 allowing for robust video mode handling and switching.
1108 Because fbdev-2.6 requires that drivers must be able to
1109 independently validate video mode parameters, you should say Y
1112 config FB_RIVA_DEBUG
1113 bool "Lots of debug output"
1117 Say Y here if you want the Riva driver to output all sorts
1118 of debugging information to provide to the maintainer when
1119 something goes wrong.
1121 config FB_RIVA_BACKLIGHT
1122 bool "Support for backlight control"
1126 Say Y here if you want to control the backlight of your display.
1129 tristate "Intel740 support"
1130 depends on FB && PCI
1131 select FB_MODE_HELPERS
1132 select FB_CFB_FILLRECT
1133 select FB_CFB_COPYAREA
1134 select FB_CFB_IMAGEBLIT
1138 This driver supports graphics cards based on Intel740 chip.
1141 tristate "Intel 810/815 support"
1142 depends on FB && PCI && X86_32 && AGP_INTEL
1143 select FB_MODE_HELPERS
1144 select FB_CFB_FILLRECT
1145 select FB_CFB_COPYAREA
1146 select FB_CFB_IMAGEBLIT
1149 This driver supports the on-board graphics built in to the Intel 810
1150 and 815 chipsets. Say Y if you have and plan to use such a board.
1152 To compile this driver as a module, choose M here: the
1153 module will be called i810fb.
1155 For more information, please read
1156 <file:Documentation/fb/intel810.txt>
1159 bool "use VESA Generalized Timing Formula"
1162 If you say Y, then the VESA standard, Generalized Timing Formula
1163 or GTF, will be used to calculate the required video timing values
1164 per video mode. Since the GTF allows nondiscrete timings
1165 (nondiscrete being a range of values as opposed to discrete being a
1166 set of values), you'll be able to use any combination of horizontal
1167 and vertical resolutions, and vertical refresh rates without having
1168 to specify your own timing parameters. This is especially useful
1169 to maximize the performance of an aging display, or if you just
1170 have a display with nonstandard dimensions. A VESA compliant
1171 monitor is recommended, but can still work with non-compliant ones.
1172 If you need or want this, then select this option. The timings may
1173 not be compliant with Intel's recommended values. Use at your own
1176 If you say N, the driver will revert to discrete video timings
1177 using a set recommended by Intel in their documentation.
1182 bool "Enable DDC Support"
1183 depends on FB_I810 && FB_I810_GTF
1188 tristate "Intel LE80578 (Vermilion) support"
1189 depends on FB && PCI && X86
1190 select FB_MODE_HELPERS
1191 select FB_CFB_FILLRECT
1192 select FB_CFB_COPYAREA
1193 select FB_CFB_IMAGEBLIT
1195 This driver supports the LE80578 (Vermilion Range) chipset
1197 config FB_CARILLO_RANCH
1198 tristate "Intel Carillo Ranch support"
1199 depends on FB_LE80578 && FB && PCI && X86
1201 This driver supports the LE80578 (Carillo Ranch) board
1204 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1205 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1206 select FB_MODE_HELPERS
1207 select FB_CFB_FILLRECT
1208 select FB_CFB_COPYAREA
1209 select FB_CFB_IMAGEBLIT
1210 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1211 depends on !DRM_I915
1213 This driver supports the on-board graphics built in to the Intel
1214 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1215 Say Y if you have and plan to use such a board.
1217 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1219 To compile this driver as a module, choose M here: the
1220 module will be called intelfb.
1222 For more information, please read <file:Documentation/fb/intelfb.txt>
1224 config FB_INTEL_DEBUG
1225 bool "Intel driver Debug Messages"
1228 Say Y here if you want the Intel driver to output all sorts
1229 of debugging information to provide to the maintainer when
1230 something goes wrong.
1233 bool "DDC/I2C for Intel framebuffer support"
1238 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1241 tristate "Matrox acceleration"
1242 depends on FB && PCI
1243 select FB_CFB_FILLRECT
1244 select FB_CFB_COPYAREA
1245 select FB_CFB_IMAGEBLIT
1246 select FB_TILEBLITTING
1247 select FB_MACMODES if PPC_PMAC
1249 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1250 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1251 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1252 Matrox G400, G450 or G550 card in your box.
1254 To compile this driver as a module, choose M here: the
1255 module will be called matroxfb.
1257 You can pass several parameters to the driver at boot time or at
1258 module load time. The parameters look like "video=matroxfb:XXX", and
1259 are described in <file:Documentation/fb/matroxfb.txt>.
1261 config FB_MATROX_MILLENIUM
1262 bool "Millennium I/II support"
1263 depends on FB_MATROX
1265 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1266 video card. If you select "Advanced lowlevel driver options" below,
1267 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1268 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1269 also use font widths different from 8.
1271 config FB_MATROX_MYSTIQUE
1272 bool "Mystique support"
1273 depends on FB_MATROX
1275 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1276 video card. If you select "Advanced lowlevel driver options" below,
1277 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1278 packed pixel and 32 bpp packed pixel. You can also use font widths
1282 bool "G100/G200/G400/G450/G550 support"
1283 depends on FB_MATROX
1285 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1286 video card. If you select "Advanced lowlevel driver options", you
1287 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1288 pixel and 32 bpp packed pixel. You can also use font widths
1291 If you need support for G400 secondary head, you must say Y to
1292 "Matrox I2C support" and "G400 second head support" right below.
1293 G450/G550 secondary head and digital output are supported without
1296 The driver starts in monitor mode. You must use the matroxset tool
1297 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1298 swap primary and secondary head outputs, or to change output mode.
1299 Secondary head driver always start in 640x480 resolution and you
1300 must use fbset to change it.
1302 Do not forget that second head supports only 16 and 32 bpp
1303 packed pixels, so it is a good idea to compile them into the kernel
1304 too. You can use only some font widths, as the driver uses generic
1305 painting procedures (the secondary head does not use acceleration
1308 G450/G550 hardware can display TV picture only from secondary CRTC,
1309 and it performs no scaling, so picture must have 525 or 625 lines.
1311 config FB_MATROX_I2C
1312 tristate "Matrox I2C support"
1313 depends on FB_MATROX
1316 This drivers creates I2C buses which are needed for accessing the
1317 DDC (I2C) bus present on all Matroxes, an I2C bus which
1318 interconnects Matrox optional devices, like MGA-TVO on G200 and
1319 G400, and the secondary head DDC bus, present on G400 only.
1321 You can say Y or M here if you want to experiment with monitor
1322 detection code. You must say Y or M here if you want to use either
1323 second head of G400 or MGA-TVO on G200 or G400.
1325 If you compile it as module, it will create a module named
1328 config FB_MATROX_MAVEN
1329 tristate "G400 second head support"
1330 depends on FB_MATROX_G && FB_MATROX_I2C
1332 WARNING !!! This support does not work with G450 !!!
1334 Say Y or M here if you want to use a secondary head (meaning two
1335 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1336 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1337 secondary head output is blanked while you are in X. With XFree
1338 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1339 the fbdev driver on first head and the fbdev driver on second head.
1341 If you compile it as module, two modules are created,
1342 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1343 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1344 also load i2c-matroxfb to get it to run.
1346 The driver starts in monitor mode and you must use the matroxset
1348 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1349 PAL or NTSC or to swap primary and secondary head outputs.
1350 Secondary head driver also always start in 640x480 resolution, you
1351 must use fbset to change it.
1353 Also do not forget that second head supports only 16 and 32 bpp
1354 packed pixels, so it is a good idea to compile them into the kernel
1355 too. You can use only some font widths, as the driver uses generic
1356 painting procedures (the secondary head does not use acceleration
1360 tristate "ATI Radeon display support"
1361 depends on FB && PCI
1362 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1363 select FB_MODE_HELPERS
1364 select FB_CFB_FILLRECT
1365 select FB_CFB_COPYAREA
1366 select FB_CFB_IMAGEBLIT
1367 select FB_MACMODES if PPC_OF
1369 Choose this option if you want to use an ATI Radeon graphics card as
1370 a framebuffer device. There are both PCI and AGP versions. You
1371 don't need to choose this to run the Radeon in plain VGA mode.
1373 There is a product page at
1374 http://products.amd.com/en-us/GraphicCardResult.aspx
1376 config FB_RADEON_I2C
1377 bool "DDC/I2C for ATI Radeon support"
1378 depends on FB_RADEON
1382 Say Y here if you want DDC/I2C support for your Radeon board.
1384 config FB_RADEON_BACKLIGHT
1385 bool "Support for backlight control"
1386 depends on FB_RADEON
1389 Say Y here if you want to control the backlight of your display.
1391 config FB_RADEON_DEBUG
1392 bool "Lots of debug output from Radeon driver"
1393 depends on FB_RADEON
1396 Say Y here if you want the Radeon driver to output all sorts
1397 of debugging information to provide to the maintainer when
1398 something goes wrong.
1401 tristate "ATI Rage128 display support"
1402 depends on FB && PCI
1403 select FB_CFB_FILLRECT
1404 select FB_CFB_COPYAREA
1405 select FB_CFB_IMAGEBLIT
1406 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1407 select FB_MACMODES if PPC_PMAC
1409 This driver supports graphics boards with the ATI Rage128 chips.
1410 Say Y if you have such a graphics board and read
1411 <file:Documentation/fb/aty128fb.txt>.
1413 To compile this driver as a module, choose M here: the
1414 module will be called aty128fb.
1416 config FB_ATY128_BACKLIGHT
1417 bool "Support for backlight control"
1418 depends on FB_ATY128
1421 Say Y here if you want to control the backlight of your display.
1424 tristate "ATI Mach64 display support" if PCI || ATARI
1425 depends on FB && !SPARC32
1426 select FB_CFB_FILLRECT
1427 select FB_CFB_COPYAREA
1428 select FB_CFB_IMAGEBLIT
1429 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1430 select FB_MACMODES if PPC
1432 This driver supports graphics boards with the ATI Mach64 chips.
1433 Say Y if you have such a graphics board.
1435 To compile this driver as a module, choose M here: the
1436 module will be called atyfb.
1439 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1440 depends on PCI && FB_ATY
1441 default y if SPARC64 && PCI
1443 Say Y here to support use of ATI's 64-bit Rage boards (or other
1444 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1445 framebuffer device. The ATI product support page for these boards
1446 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1448 config FB_ATY_GENERIC_LCD
1449 bool "Mach64 generic LCD support"
1450 depends on FB_ATY_CT
1452 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1453 Rage XC, or Rage XL chipset.
1456 bool "Mach64 GX support" if PCI
1460 Say Y here to support use of the ATI Mach64 Graphics Expression
1461 board (or other boards based on the Mach64 GX chipset) as a
1462 framebuffer device. The ATI product support page for these boards
1464 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1466 config FB_ATY_BACKLIGHT
1467 bool "Support for backlight control"
1471 Say Y here if you want to control the backlight of your display.
1474 tristate "S3 Trio/Virge support"
1475 depends on FB && PCI
1476 select FB_CFB_FILLRECT
1477 select FB_CFB_COPYAREA
1478 select FB_CFB_IMAGEBLIT
1479 select FB_TILEBLITTING
1482 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1484 Driver for graphics boards with S3 Trio / S3 Virge chip.
1487 bool "DDC for S3 support"
1492 Say Y here if you want DDC support for your S3 graphics card.
1495 tristate "S3 Savage support"
1496 depends on FB && PCI
1497 select FB_MODE_HELPERS
1498 select FB_CFB_FILLRECT
1499 select FB_CFB_COPYAREA
1500 select FB_CFB_IMAGEBLIT
1503 This driver supports notebooks and computers with S3 Savage PCI/AGP
1506 Say Y if you have such a graphics card.
1508 To compile this driver as a module, choose M here; the module
1509 will be called savagefb.
1511 config FB_SAVAGE_I2C
1512 bool "Enable DDC2 Support"
1513 depends on FB_SAVAGE
1516 This enables I2C support for S3 Savage Chipsets. This is used
1517 only for getting EDID information from the attached display
1518 allowing for robust video mode handling and switching.
1520 Because fbdev-2.6 requires that drivers must be able to
1521 independently validate video mode parameters, you should say Y
1524 config FB_SAVAGE_ACCEL
1525 bool "Enable Console Acceleration"
1526 depends on FB_SAVAGE
1529 This option will compile in console acceleration support. If
1530 the resulting framebuffer console has bothersome glitches, then
1534 tristate "SiS/XGI display support"
1535 depends on FB && PCI
1536 select FB_CFB_FILLRECT
1537 select FB_CFB_COPYAREA
1538 select FB_CFB_IMAGEBLIT
1539 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1541 This is the frame buffer device driver for the SiS 300, 315, 330
1542 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1543 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1545 To compile this driver as a module, choose M here; the module
1546 will be called sisfb.
1549 bool "SiS 300 series support"
1552 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1555 bool "SiS 315/330/340 series and XGI support"
1558 Say Y here to support use of the SiS 315, 330 and 340 series
1559 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1560 as XGI V3XT, V5, V8 and Z7.
1563 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1564 depends on FB && PCI && X86
1565 select FB_CFB_FILLRECT
1566 select FB_CFB_COPYAREA
1567 select FB_CFB_IMAGEBLIT
1572 This is the frame buffer device driver for Graphics chips of VIA
1573 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1574 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1576 Say Y if you have a VIA UniChrome graphics board.
1578 To compile this driver as a module, choose M here: the
1579 module will be called viafb.
1583 config FB_VIA_DIRECT_PROCFS
1584 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1588 Allow direct hardware access to some output registers via procfs.
1589 This is dangerous but may provide the only chance to get the
1590 correct output device configuration.
1591 Its use is strongly discouraged.
1593 config FB_VIA_X_COMPATIBILITY
1594 bool "X server compatibility"
1598 This option reduces the functionality (power saving, ...) of the
1599 framebuffer to avoid negative impact on the OpenChrome X server.
1600 If you use any X server other than fbdev you should enable this
1601 otherwise it should be safe to disable it and allow using all
1607 tristate "NeoMagic display support"
1608 depends on FB && PCI
1609 select FB_MODE_HELPERS
1610 select FB_CFB_FILLRECT
1611 select FB_CFB_COPYAREA
1612 select FB_CFB_IMAGEBLIT
1615 This driver supports notebooks with NeoMagic PCI chips.
1616 Say Y if you have such a graphics card.
1618 To compile this driver as a module, choose M here: the
1619 module will be called neofb.
1622 tristate "IMG Kyro support"
1623 depends on FB && PCI
1624 select FB_CFB_FILLRECT
1625 select FB_CFB_COPYAREA
1626 select FB_CFB_IMAGEBLIT
1628 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1631 To compile this driver as a module, choose M here: the
1632 module will be called kyrofb.
1635 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1636 depends on FB && PCI
1637 select FB_CFB_IMAGEBLIT
1638 select FB_CFB_FILLRECT
1639 select FB_CFB_COPYAREA
1640 select FB_MODE_HELPERS
1642 This driver supports graphics boards with the 3Dfx Banshee,
1643 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1644 such a graphics board.
1646 To compile this driver as a module, choose M here: the
1647 module will be called tdfxfb.
1649 config FB_3DFX_ACCEL
1650 bool "3Dfx Acceleration functions"
1653 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1654 device driver with acceleration functions.
1657 bool "Enable DDC/I2C support"
1662 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1665 tristate "3Dfx Voodoo Graphics (sst1) support"
1666 depends on FB && PCI
1667 select FB_CFB_FILLRECT
1668 select FB_CFB_COPYAREA
1669 select FB_CFB_IMAGEBLIT
1671 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1672 Voodoo2 (cvg) based graphics card.
1674 To compile this driver as a module, choose M here: the
1675 module will be called sstfb.
1677 WARNING: Do not use any application that uses the 3D engine
1678 (namely glide) while using this driver.
1679 Please read the <file:Documentation/fb/sstfb.txt> for supported
1680 options and other important info support.
1683 tristate "VIA VT8623 support"
1684 depends on FB && PCI
1685 select FB_CFB_FILLRECT
1686 select FB_CFB_COPYAREA
1687 select FB_CFB_IMAGEBLIT
1688 select FB_TILEBLITTING
1691 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1693 Driver for CastleRock integrated graphics core in the
1694 VIA VT8623 [Apollo CLE266] chipset.
1697 tristate "Trident/CyberXXX/CyberBlade support"
1698 depends on FB && PCI
1699 select FB_CFB_FILLRECT
1700 select FB_CFB_COPYAREA
1701 select FB_CFB_IMAGEBLIT
1703 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1704 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1706 There are also integrated versions of these chips called CyberXXXX,
1707 CyberImage or CyberBlade. These chips are mostly found in laptops
1708 but also on some motherboards including early VIA EPIA motherboards.
1709 For more information, read <file:Documentation/fb/tridentfb.txt>
1711 Say Y if you have such a graphics board.
1713 To compile this driver as a module, choose M here: the
1714 module will be called tridentfb.
1717 tristate "ARK 2000PV support"
1718 depends on FB && PCI
1719 select FB_CFB_FILLRECT
1720 select FB_CFB_COPYAREA
1721 select FB_CFB_IMAGEBLIT
1722 select FB_TILEBLITTING
1725 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1727 Driver for PCI graphics boards with ARK 2000PV chip
1728 and ICS 5342 RAMDAC.
1731 tristate "Permedia3 support"
1732 depends on FB && PCI
1733 select FB_CFB_FILLRECT
1734 select FB_CFB_COPYAREA
1735 select FB_CFB_IMAGEBLIT
1737 This is the frame buffer device driver for the 3DLabs Permedia3
1738 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1739 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1740 and maybe other boards.
1743 tristate "Fujitsu carmine frame buffer support"
1744 depends on FB && PCI
1745 select FB_CFB_FILLRECT
1746 select FB_CFB_COPYAREA
1747 select FB_CFB_IMAGEBLIT
1749 This is the frame buffer device driver for the Fujitsu Carmine chip.
1750 The driver provides two independent frame buffer devices.
1753 depends on FB_CARMINE
1754 prompt "DRAM timing"
1755 default FB_CARMINE_DRAM_EVAL
1757 config FB_CARMINE_DRAM_EVAL
1758 bool "Eval board timings"
1760 Use timings which work on the eval card.
1762 config CARMINE_DRAM_CUSTOM
1763 bool "Custom board timings"
1765 Use custom board timings.
1769 bool "Au1100 LCD Driver"
1770 depends on (FB = y) && MIPS_ALCHEMY
1771 select FB_CFB_FILLRECT
1772 select FB_CFB_COPYAREA
1773 select FB_CFB_IMAGEBLIT
1775 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1776 various panels and CRTs by passing in kernel cmd line option
1777 au1100fb:panel=<name>.
1780 bool "Au1200/Au1300 LCD Driver"
1781 depends on (FB = y) && MIPS_ALCHEMY
1782 select FB_SYS_FILLRECT
1783 select FB_SYS_COPYAREA
1784 select FB_SYS_IMAGEBLIT
1787 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1788 It can drive various panels and CRTs by passing in kernel cmd line
1789 option au1200fb:panel=<name>.
1792 bool "VIA VT8500 framebuffer support"
1793 depends on (FB = y) && ARM && ARCH_VT8500
1794 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1795 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1796 select FB_SYS_IMAGEBLIT
1798 This is the framebuffer driver for VIA VT8500 integrated LCD
1802 bool "Wondermedia WM8xxx-series frame buffer support"
1803 depends on (FB = y) && ARM && ARCH_VT8500
1804 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1805 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1806 select FB_SYS_IMAGEBLIT
1808 This is the framebuffer driver for WonderMedia WM8xxx-series
1809 integrated LCD controller. This driver covers the WM8505, WM8650
1812 config FB_WMT_GE_ROPS
1813 bool "VT8500/WM8xxx accelerated raster ops support"
1814 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1817 This adds support for accelerated raster operations on the
1818 VIA VT8500 and Wondermedia 85xx series SoCs.
1820 source "drivers/video/geode/Kconfig"
1823 tristate "HD64461 Frame Buffer support"
1824 depends on FB && HD64461
1825 select FB_CFB_FILLRECT
1826 select FB_CFB_COPYAREA
1827 select FB_CFB_IMAGEBLIT
1829 This is the frame buffer device driver for the Hitachi HD64461 LCD
1833 bool "PMAG-AA TURBOchannel framebuffer support"
1834 depends on (FB = y) && TC
1835 select FB_CFB_FILLRECT
1836 select FB_CFB_COPYAREA
1837 select FB_CFB_IMAGEBLIT
1839 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1840 used mainly in the MIPS-based DECstation series.
1843 tristate "PMAG-BA TURBOchannel framebuffer support"
1845 select FB_CFB_FILLRECT
1846 select FB_CFB_COPYAREA
1847 select FB_CFB_IMAGEBLIT
1849 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1850 used mainly in the MIPS-based DECstation series.
1853 tristate "PMAGB-B TURBOchannel framebuffer support"
1855 select FB_CFB_FILLRECT
1856 select FB_CFB_COPYAREA
1857 select FB_CFB_IMAGEBLIT
1859 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1860 in the MIPS-based DECstation series. The card is currently only
1861 supported in 1280x1024x8 mode.
1864 bool "Maxine (Personal DECstation) onboard framebuffer support"
1865 depends on (FB = y) && MACH_DECSTATION
1866 select FB_CFB_FILLRECT
1867 select FB_CFB_COPYAREA
1868 select FB_CFB_IMAGEBLIT
1870 Support for the onboard framebuffer (1024x768x8) in the Personal
1871 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1875 bool "G364 frame buffer support"
1876 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1877 select FB_CFB_FILLRECT
1878 select FB_CFB_COPYAREA
1879 select FB_CFB_IMAGEBLIT
1881 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1882 Olivetti M700-10 systems.
1885 bool "Motorola 68328 native frame buffer support"
1886 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1887 select FB_CFB_FILLRECT
1888 select FB_CFB_COPYAREA
1889 select FB_CFB_IMAGEBLIT
1891 Say Y here if you want to support the built-in frame buffer of
1892 the Motorola 68328 CPU family.
1895 tristate "PXA168/910 LCD framebuffer support"
1896 depends on FB && (CPU_PXA168 || CPU_PXA910)
1897 select FB_CFB_FILLRECT
1898 select FB_CFB_COPYAREA
1899 select FB_CFB_IMAGEBLIT
1901 Frame buffer driver for the built-in LCD controller in the Marvell
1905 tristate "PXA LCD framebuffer support"
1906 depends on FB && ARCH_PXA
1907 select FB_CFB_FILLRECT
1908 select FB_CFB_COPYAREA
1909 select FB_CFB_IMAGEBLIT
1911 Frame buffer driver for the built-in LCD controller in the Intel
1914 This driver is also available as a module ( = code which can be
1915 inserted and removed from the running kernel whenever you want). The
1916 module will be called pxafb. If you want to compile it as a module,
1917 say M here and read <file:Documentation/kbuild/modules.txt>.
1921 config FB_PXA_OVERLAY
1922 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1924 depends on FB_PXA && (PXA27x || PXA3xx)
1926 config FB_PXA_SMARTPANEL
1927 bool "PXA Smartpanel LCD support"
1931 config FB_PXA_PARAMETERS
1932 bool "PXA LCD command line parameters"
1936 Enable the use of kernel command line or module parameters
1937 to configure the physical properties of the LCD panel when
1938 using the PXA LCD driver.
1940 This option allows you to override the panel parameters
1941 supplied by the platform in order to support multiple
1942 different models of flatpanel. If you will only be using a
1943 single model of flatpanel then you can safely leave this
1946 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1949 tristate "PXA3xx 2D graphics accelerator driver"
1952 Kernelspace driver for the 2D graphics controller unit (GCU)
1953 found on PXA3xx processors. There is a counterpart driver in the
1954 DirectFB suite, see http://www.directfb.org/
1956 If you compile this as a module, it will be called pxa3xx_gcu.
1959 tristate "2700G LCD framebuffer support"
1960 depends on FB && ARCH_PXA
1961 select FB_CFB_FILLRECT
1962 select FB_CFB_COPYAREA
1963 select FB_CFB_IMAGEBLIT
1965 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1969 bool "Enable debugging info via debugfs"
1970 depends on FB_MBX && DEBUG_FS
1973 Enable this if you want debugging information using the debug
1974 filesystem (debugfs)
1979 tristate "Freescale DIU framebuffer support"
1980 depends on FB && FSL_SOC
1981 select FB_MODE_HELPERS
1982 select FB_CFB_FILLRECT
1983 select FB_CFB_COPYAREA
1984 select FB_CFB_IMAGEBLIT
1985 select PPC_LIB_RHEAP
1987 Framebuffer driver for the Freescale SoC DIU
1990 tristate "W100 frame buffer support"
1991 depends on FB && ARCH_PXA
1992 select FB_CFB_FILLRECT
1993 select FB_CFB_COPYAREA
1994 select FB_CFB_IMAGEBLIT
1996 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1997 It can also drive the w3220 chip found on iPAQ hx4700.
1999 This driver is also available as a module ( = code which can be
2000 inserted and removed from the running kernel whenever you want). The
2001 module will be called w100fb. If you want to compile it as a module,
2002 say M here and read <file:Documentation/kbuild/modules.txt>.
2006 config FB_SH_MOBILE_LCDC
2007 tristate "SuperH Mobile LCDC framebuffer support"
2008 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2009 select FB_SYS_FILLRECT
2010 select FB_SYS_COPYAREA
2011 select FB_SYS_IMAGEBLIT
2013 select FB_DEFERRED_IO
2015 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2017 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2019 config FB_SH_MOBILE_HDMI
2020 tristate "SuperH Mobile HDMI controller support"
2021 depends on FB_SH_MOBILE_LCDC
2022 select FB_MODE_HELPERS
2027 Driver for the on-chip SH-Mobile HDMI controller.
2030 tristate "Toshiba Mobile IO FrameBuffer support"
2031 depends on FB && MFD_CORE
2032 select FB_CFB_FILLRECT
2033 select FB_CFB_COPYAREA
2034 select FB_CFB_IMAGEBLIT
2036 Frame buffer driver for the Toshiba Mobile IO integrated as found
2037 on the Sharp SL-6000 series
2039 This driver is also available as a module ( = code which can be
2040 inserted and removed from the running kernel whenever you want). The
2041 module will be called tmiofb. If you want to compile it as a module,
2042 say M here and read <file:Documentation/kbuild/modules.txt>.
2046 config FB_TMIO_ACCELL
2047 bool "tmiofb acceleration"
2052 tristate "Samsung S3C framebuffer support"
2053 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2054 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2055 select FB_CFB_FILLRECT
2056 select FB_CFB_COPYAREA
2057 select FB_CFB_IMAGEBLIT
2059 Frame buffer driver for the built-in FB controller in the Samsung
2060 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2061 and the S3C64XX series such as the S3C6400 and S3C6410.
2063 These chips all have the same basic framebuffer design with the
2064 actual capabilities depending on the chip. For instance the S3C6400
2065 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2066 currently only have two.
2068 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2070 config FB_S3C_DEBUG_REGWRITE
2071 bool "Debug register writes"
2074 Show all register writes via pr_debug()
2077 tristate "S3C2410 LCD framebuffer support"
2078 depends on FB && ARCH_S3C24XX
2079 select FB_CFB_FILLRECT
2080 select FB_CFB_COPYAREA
2081 select FB_CFB_IMAGEBLIT
2083 Frame buffer driver for the built-in LCD controller in the Samsung
2086 This driver is also available as a module ( = code which can be
2087 inserted and removed from the running kernel whenever you want). The
2088 module will be called s3c2410fb. If you want to compile it as a module,
2089 say M here and read <file:Documentation/kbuild/modules.txt>.
2092 config FB_S3C2410_DEBUG
2093 bool "S3C2410 lcd debug messages"
2094 depends on FB_S3C2410
2096 Turn on debugging messages. Note that you can set/unset at run time
2100 bool "NUC900 LCD framebuffer support"
2101 depends on FB && ARCH_W90X900
2102 select FB_CFB_FILLRECT
2103 select FB_CFB_COPYAREA
2104 select FB_CFB_IMAGEBLIT
2106 Frame buffer driver for the built-in LCD controller in the Nuvoton
2109 config GPM1040A0_320X240
2110 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2111 depends on FB_NUC900
2113 config FB_NUC900_DEBUG
2114 bool "NUC900 lcd debug messages"
2115 depends on FB_NUC900
2117 Turn on debugging messages. Note that you can set/unset at run time
2121 tristate "Silicon Motion SM501 framebuffer support"
2122 depends on FB && MFD_SM501
2123 select FB_CFB_FILLRECT
2124 select FB_CFB_COPYAREA
2125 select FB_CFB_IMAGEBLIT
2127 Frame buffer driver for the CRT and LCD controllers in the Silicon
2130 This driver is also available as a module ( = code which can be
2131 inserted and removed from the running kernel whenever you want). The
2132 module will be called sm501fb. If you want to compile it as a module,
2133 say M here and read <file:Documentation/kbuild/modules.txt>.
2138 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2139 depends on FB && USB
2140 select FB_MODE_HELPERS
2141 select FB_SYS_FILLRECT
2142 select FB_SYS_COPYAREA
2143 select FB_SYS_IMAGEBLIT
2145 select FB_DEFERRED_IO
2147 This is a kernel framebuffer driver for SMSC UFX USB devices.
2148 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2149 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2151 To compile as a module, choose M here: the module name is smscufx.
2154 tristate "Displaylink USB Framebuffer support"
2155 depends on FB && USB
2156 select FB_MODE_HELPERS
2157 select FB_SYS_FILLRECT
2158 select FB_SYS_COPYAREA
2159 select FB_SYS_IMAGEBLIT
2161 select FB_DEFERRED_IO
2163 This is a kernel framebuffer driver for DisplayLink USB devices.
2164 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2165 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2166 To compile as a module, choose M here: the module name is udlfb.
2168 config FB_IBM_GXT4500
2169 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2170 depends on FB && PPC
2171 select FB_CFB_FILLRECT
2172 select FB_CFB_COPYAREA
2173 select FB_CFB_IMAGEBLIT
2175 Say Y here to enable support for the IBM GXT4000P/6000P and
2176 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2177 found on some IBM System P (pSeries) machines. This driver
2178 doesn't use Geometry Engine GT1000.
2181 tristate "PS3 GPU framebuffer driver"
2182 depends on FB && PS3_PS3AV
2183 select FB_SYS_FILLRECT
2184 select FB_SYS_COPYAREA
2185 select FB_SYS_IMAGEBLIT
2187 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2189 Include support for the virtual frame buffer in the PS3 platform.
2191 config FB_PS3_DEFAULT_SIZE_M
2192 int "PS3 default frame buffer size (in MiB)"
2196 This is the default size (in MiB) of the virtual frame buffer in
2198 The default value can be overridden on the kernel command line
2199 using the "ps3fb" option (e.g. "ps3fb=9M");
2202 tristate "Xilinx frame buffer support"
2203 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2204 select FB_CFB_FILLRECT
2205 select FB_CFB_COPYAREA
2206 select FB_CFB_IMAGEBLIT
2208 Include support for the Xilinx ML300/ML403 reference design
2209 framebuffer. ML300 carries a 640*480 LCD display on the board,
2210 ML403 uses a standard DB15 VGA connector.
2213 tristate "Goldfish Framebuffer"
2215 select FB_CFB_FILLRECT
2216 select FB_CFB_COPYAREA
2217 select FB_CFB_IMAGEBLIT
2219 Framebuffer driver for Goldfish Virtual Platform
2222 tristate "Cobalt server LCD frame buffer support"
2223 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2226 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2227 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2228 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2229 select FB_CFB_FILLRECT
2230 select FB_CFB_COPYAREA
2231 select FB_CFB_IMAGEBLIT
2233 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2234 (D)STN/TFT LCD Controller.
2235 Supports display resolutions up to 1024x1024 pixel, grayscale and
2236 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2237 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2238 panels <= 320 pixel horizontal resolution.
2241 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2242 depends on FB && ARCH_DAVINCI_DA8XX
2243 select FB_CFB_FILLRECT
2244 select FB_CFB_COPYAREA
2245 select FB_CFB_IMAGEBLIT
2246 select FB_CFB_REV_PIXELS_IN_BYTE
2248 This is the frame buffer device driver for the TI LCD controller
2249 found on DA8xx/OMAP-L1xx SoCs.
2253 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2255 select FB_SYS_FILLRECT
2256 select FB_SYS_COPYAREA
2257 select FB_SYS_IMAGEBLIT
2260 This is a `virtual' frame buffer device. It operates on a chunk of
2261 unswappable kernel memory instead of on the memory of a graphics
2262 board. This means you cannot see any output sent to this frame
2263 buffer device, while it does consume precious memory. The main use
2264 of this frame buffer device is testing and debugging the frame
2265 buffer subsystem. Do NOT enable it for normal systems! To protect
2266 the innocent, it has to be enabled explicitly at boot time using the
2267 kernel option `video=vfb:'.
2269 To compile this driver as a module, choose M here: the
2270 module will be called vfb. In order to load it, you must use
2271 the vfb_enable=1 option.
2275 config XEN_FBDEV_FRONTEND
2276 tristate "Xen virtual frame buffer support"
2277 depends on FB && XEN
2278 select FB_SYS_FILLRECT
2279 select FB_SYS_COPYAREA
2280 select FB_SYS_IMAGEBLIT
2282 select FB_DEFERRED_IO
2283 select INPUT_XEN_KBDDEV_FRONTEND
2284 select XEN_XENBUS_FRONTEND
2287 This driver implements the front-end of the Xen virtual
2288 frame buffer driver. It communicates with a back-end
2292 tristate "E-Ink Metronome/8track controller support"
2294 select FB_SYS_FILLRECT
2295 select FB_SYS_COPYAREA
2296 select FB_SYS_IMAGEBLIT
2298 select FB_DEFERRED_IO
2300 This driver implements support for the E-Ink Metronome
2301 controller. The pre-release name for this device was 8track
2302 and could also have been called by some vendors as PVI-nnnn.
2305 tristate "Fujitsu MB862xx GDC support"
2307 depends on PCI || (OF && PPC)
2308 select FB_CFB_FILLRECT
2309 select FB_CFB_COPYAREA
2310 select FB_CFB_IMAGEBLIT
2312 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2315 prompt "GDC variant"
2316 depends on FB_MB862XX
2318 config FB_MB862XX_PCI_GDC
2319 bool "Carmine/Coral-P(A) GDC"
2322 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2323 PCI graphics controller devices.
2325 config FB_MB862XX_LIME
2327 depends on OF && PPC
2328 select FB_FOREIGN_ENDIAN
2329 select FB_LITTLE_ENDIAN
2331 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2335 config FB_MB862XX_I2C
2336 bool "Support I2C bus on MB862XX GDC"
2337 depends on FB_MB862XX && I2C
2340 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2341 driver to support accessing I2C devices on controller's I2C bus.
2342 These are usually some video decoder chips.
2345 tristate "EP93XX frame buffer support"
2346 depends on FB && ARCH_EP93XX
2347 select FB_CFB_FILLRECT
2348 select FB_CFB_COPYAREA
2349 select FB_CFB_IMAGEBLIT
2351 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2352 This driver is also available as a module. The module will be called
2355 config FB_PRE_INIT_FB
2356 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2357 depends on FB && FB_MB862XX_LIME
2359 Select this option if display contents should be inherited as set by
2363 tristate "MSM Framebuffer support"
2364 depends on FB && ARCH_MSM
2365 select FB_CFB_FILLRECT
2366 select FB_CFB_COPYAREA
2367 select FB_CFB_IMAGEBLIT
2370 tristate "MX3 Framebuffer support"
2371 depends on FB && MX3_IPU
2372 select FB_CFB_FILLRECT
2373 select FB_CFB_COPYAREA
2374 select FB_CFB_IMAGEBLIT
2377 This is a framebuffer device for the i.MX31 LCD Controller. So
2378 far only synchronous displays are supported. If you plan to use
2379 an LCD display with your i.MX31 system, say Y here.
2381 config FB_BROADSHEET
2382 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2384 select FB_SYS_FILLRECT
2385 select FB_SYS_COPYAREA
2386 select FB_SYS_IMAGEBLIT
2388 select FB_DEFERRED_IO
2390 This driver implements support for the E-Ink Broadsheet
2391 controller. The release name for this device was Epson S1D13521
2392 and could also have been called by other names when coupled with
2396 tristate "AUO-K190X EPD controller support"
2398 select FB_SYS_FILLRECT
2399 select FB_SYS_COPYAREA
2400 select FB_SYS_IMAGEBLIT
2402 select FB_DEFERRED_IO
2404 Provides support for epaper controllers from the K190X series
2405 of AUO. These controllers can be used to drive epaper displays
2408 This option enables the common support, shared by the individual
2409 controller drivers. You will also have to enable the driver
2410 for the controller type used in your device.
2413 tristate "AUO-K1900 EPD controller support"
2414 depends on FB && FB_AUO_K190X
2416 This driver implements support for the AUO K1900 epd-controller.
2417 This controller can drive Sipix epaper displays but can only do
2418 serial updates, reducing the number of possible frames per second.
2421 tristate "AUO-K1901 EPD controller support"
2422 depends on FB && FB_AUO_K190X
2424 This driver implements support for the AUO K1901 epd-controller.
2425 This controller can drive Sipix epaper displays and supports
2426 concurrent updates, making higher frames per second possible.
2429 tristate "JZ4740 LCD framebuffer support"
2430 depends on FB && MACH_JZ4740
2431 select FB_SYS_FILLRECT
2432 select FB_SYS_COPYAREA
2433 select FB_SYS_IMAGEBLIT
2435 Framebuffer support for the JZ4740 SoC.
2438 tristate "MXS LCD framebuffer support"
2439 depends on FB && ARCH_MXS
2440 select FB_CFB_FILLRECT
2441 select FB_CFB_COPYAREA
2442 select FB_CFB_IMAGEBLIT
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.
2457 source "drivers/video/omap/Kconfig"
2458 source "drivers/video/omap2/Kconfig"
2459 source "drivers/video/exynos/Kconfig"
2460 source "drivers/video/mmp/Kconfig"
2461 source "drivers/video/backlight/Kconfig"
2464 source "drivers/video/console/Kconfig"
2467 if FB || SGI_NEWPORT_CONSOLE
2468 source "drivers/video/logo/Kconfig"
2471 config FB_SH_MOBILE_MERAM
2472 tristate "SuperH Mobile MERAM read ahead support"
2473 depends on (SUPERH || ARCH_SHMOBILE)
2474 select GENERIC_ALLOCATOR
2476 Enable MERAM support for the SuperH controller.
2478 This will allow for caching of the framebuffer to provide more
2479 reliable access under heavy main memory bus traffic situations.
2480 Up to 4 memory channels can be configured, allowing 4 RGB or
2481 2 YCbCr framebuffers to be configured.
2484 tristate "Solomon SSD1307 framebuffer support"
2485 depends on FB && I2C
2487 depends on GENERIC_GPIO
2489 select FB_SYS_FILLRECT
2490 select FB_SYS_COPYAREA
2491 select FB_SYS_IMAGEBLIT
2492 select FB_DEFERRED_IO
2495 This driver implements support for the Solomon SSD1307
2496 OLED controller over I2C.