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 bool "SGI Graphics Backend frame buffer support"
801 depends on (FB = y) && SGI_IP32
802 select FB_CFB_FILLRECT
803 select FB_CFB_COPYAREA
804 select FB_CFB_IMAGEBLIT
806 This is the frame buffer device driver for SGI Graphics Backend.
807 This chip is used in SGI O2 and Visual Workstation 320/540.
810 int "Video memory size in MB"
814 This is the amount of memory reserved for the framebuffer,
815 which can be any value between 1MB and 8MB.
818 bool "SBUS and UPA framebuffers"
819 depends on (FB = y) && SPARC
821 Say Y if you want support for SBUS or UPA based frame buffer device.
825 depends on (FB = y) && (SPARC && FB_SBUS)
826 select FB_CFB_FILLRECT
827 select FB_CFB_COPYAREA
828 select FB_CFB_IMAGEBLIT
830 This is the frame buffer device driver for the BWtwo frame buffer.
833 bool "CGthree support"
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 CGthree frame buffer.
842 bool "CGsix (GX,TurboGX) support"
843 depends on (FB = y) && (SPARC && FB_SBUS)
844 select FB_CFB_COPYAREA
845 select FB_CFB_IMAGEBLIT
847 This is the frame buffer device driver for the CGsix (GX, TurboGX)
851 bool "Creator/Creator3D/Elite3D support"
852 depends on FB_SBUS && SPARC64
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
856 This is the frame buffer device driver for the Creator, Creator3D,
857 and Elite3D graphics boards.
860 bool "TCX (SS4/SS5 only) support"
862 select FB_CFB_FILLRECT
863 select FB_CFB_COPYAREA
864 select FB_CFB_IMAGEBLIT
866 This is the frame buffer device driver for the TCX 24/8bit frame
870 bool "CGfourteen (SX) support"
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the frame buffer device driver for the CGfourteen frame
877 buffer on Desktop SPARCsystems with the SX graphics option.
880 bool "P9100 (Sparcbook 3 only) support"
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the frame buffer device driver for the P9100 card
887 supported on Sparcbook 3 machines.
890 bool "Leo (ZX) support"
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
896 This is the frame buffer device driver for the SBUS-based Sun ZX
897 (leo) frame buffer cards.
900 bool "IGA 168x display support"
901 depends on (FB = y) && SPARC32
902 select FB_CFB_FILLRECT
903 select FB_CFB_COPYAREA
904 select FB_CFB_IMAGEBLIT
906 This is the framebuffer device for the INTERGRAPHICS 1680 and
907 successor frame buffer cards.
910 bool "Sun XVR-500 3DLABS Wildcat support"
911 depends on (FB = y) && PCI && SPARC64
912 select FB_CFB_FILLRECT
913 select FB_CFB_COPYAREA
914 select FB_CFB_IMAGEBLIT
916 This is the framebuffer device for the Sun XVR-500 and similar
917 graphics cards based upon the 3DLABS Wildcat chipset. The driver
918 only works on sparc64 systems where the system firmware has
919 mostly initialized the card already. It is treated as a
920 completely dumb framebuffer device.
923 bool "Sun XVR-2500 3DLABS Wildcat support"
924 depends on (FB = y) && PCI && SPARC64
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 This is the framebuffer device for the Sun XVR-2500 and similar
930 graphics cards based upon the 3DLABS Wildcat chipset. The driver
931 only works on sparc64 systems where the system firmware has
932 mostly initialized the card already. It is treated as a
933 completely dumb framebuffer device.
936 bool "Sun XVR-1000 support"
937 depends on (FB = y) && SPARC64
938 select FB_CFB_FILLRECT
939 select FB_CFB_COPYAREA
940 select FB_CFB_IMAGEBLIT
942 This is the framebuffer device for the Sun XVR-1000 and similar
943 graphics cards. The driver only works on sparc64 systems where
944 the system firmware has mostly initialized the card already. It
945 is treated as a completely dumb framebuffer device.
948 tristate "NEC PowerVR 2 display support"
949 depends on FB && SH_DREAMCAST
950 select FB_CFB_FILLRECT
951 select FB_CFB_COPYAREA
952 select FB_CFB_IMAGEBLIT
954 Say Y here if you have a PowerVR 2 card in your box. If you plan to
955 run linux on your Dreamcast, you will have to say Y here.
956 This driver may or may not work on other PowerVR 2 cards, but is
957 totally untested. Use at your own risk. If unsure, say N.
959 To compile this driver as a module, choose M here: the
960 module will be called pvr2fb.
962 You can pass several parameters to the driver at boot time or at
963 module load time. The parameters look like "video=pvr2:XXX", where
964 the meaning of XXX can be found at the end of the main source file
965 (<file:drivers/video/pvr2fb.c>). Please see the file
966 <file:Documentation/fb/pvr2fb.txt>.
969 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
970 depends on FB && HAS_DMA
971 select FB_CFB_FILLRECT
972 select FB_CFB_COPYAREA
973 select FB_CFB_IMAGEBLIT
975 This enables support for the OpenCores VGA/LCD core.
977 The OpenCores VGA/LCD core is typically used together with
978 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
979 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
981 The source code and specification for the core is available at
982 <http://opencores.org/project,vga_lcd>
985 tristate "Epson S1D13XXX framebuffer support"
987 select FB_CFB_FILLRECT
988 select FB_CFB_COPYAREA
989 select FB_CFB_IMAGEBLIT
991 Support for S1D13XXX framebuffer device family (currently only
992 working with S1D13806). Product specs at
993 <http://vdc.epson.com/>
996 tristate "AT91/AT32 LCD Controller support"
997 depends on FB && HAVE_FB_ATMEL
998 select FB_CFB_FILLRECT
999 select FB_CFB_COPYAREA
1000 select FB_CFB_IMAGEBLIT
1001 select FB_MODE_HELPERS
1002 select VIDEOMODE_HELPERS
1004 This enables support for the AT91/AT32 LCD Controller.
1007 bool "Frame Buffer in internal SRAM"
1008 depends on FB_ATMEL && ARCH_AT91SAM9261
1010 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1011 to let frame buffer in external SDRAM.
1014 bool "Use a STN display with AT91/AT32 LCD Controller"
1015 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1018 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1019 Controller. Say N if you want to connect a TFT.
1024 tristate "nVidia Framebuffer Support"
1025 depends on FB && PCI
1026 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1027 select FB_MODE_HELPERS
1028 select FB_CFB_FILLRECT
1029 select FB_CFB_COPYAREA
1030 select FB_CFB_IMAGEBLIT
1034 This driver supports graphics boards with the nVidia chips, TNT
1035 and newer. For very old chipsets, such as the RIVA128, then use
1037 Say Y if you have such a graphics board.
1039 To compile this driver as a module, choose M here: the
1040 module will be called nvidiafb.
1042 config FB_NVIDIA_I2C
1043 bool "Enable DDC Support"
1044 depends on FB_NVIDIA
1047 This enables I2C support for nVidia Chipsets. This is used
1048 only for getting EDID information from the attached display
1049 allowing for robust video mode handling and switching.
1051 Because fbdev-2.6 requires that drivers must be able to
1052 independently validate video mode parameters, you should say Y
1055 config FB_NVIDIA_DEBUG
1056 bool "Lots of debug output"
1057 depends on FB_NVIDIA
1060 Say Y here if you want the nVidia driver to output all sorts
1061 of debugging information to provide to the maintainer when
1062 something goes wrong.
1064 config FB_NVIDIA_BACKLIGHT
1065 bool "Support for backlight control"
1066 depends on FB_NVIDIA
1069 Say Y here if you want to control the backlight of your display.
1072 tristate "nVidia Riva support"
1073 depends on FB && PCI
1074 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1075 select FB_MODE_HELPERS
1076 select FB_CFB_FILLRECT
1077 select FB_CFB_COPYAREA
1078 select FB_CFB_IMAGEBLIT
1082 This driver supports graphics boards with the nVidia Riva/Geforce
1084 Say Y if you have such a graphics board.
1086 To compile this driver as a module, choose M here: the
1087 module will be called rivafb.
1090 bool "Enable DDC Support"
1094 This enables I2C support for nVidia Chipsets. This is used
1095 only for getting EDID information from the attached display
1096 allowing for robust video mode handling and switching.
1098 Because fbdev-2.6 requires that drivers must be able to
1099 independently validate video mode parameters, you should say Y
1102 config FB_RIVA_DEBUG
1103 bool "Lots of debug output"
1107 Say Y here if you want the Riva driver to output all sorts
1108 of debugging information to provide to the maintainer when
1109 something goes wrong.
1111 config FB_RIVA_BACKLIGHT
1112 bool "Support for backlight control"
1116 Say Y here if you want to control the backlight of your display.
1119 tristate "Intel740 support"
1120 depends on FB && PCI
1121 select FB_MODE_HELPERS
1122 select FB_CFB_FILLRECT
1123 select FB_CFB_COPYAREA
1124 select FB_CFB_IMAGEBLIT
1128 This driver supports graphics cards based on Intel740 chip.
1131 tristate "Intel 810/815 support"
1132 depends on FB && PCI && X86_32 && AGP_INTEL
1133 select FB_MODE_HELPERS
1134 select FB_CFB_FILLRECT
1135 select FB_CFB_COPYAREA
1136 select FB_CFB_IMAGEBLIT
1139 This driver supports the on-board graphics built in to the Intel 810
1140 and 815 chipsets. Say Y if you have and plan to use such a board.
1142 To compile this driver as a module, choose M here: the
1143 module will be called i810fb.
1145 For more information, please read
1146 <file:Documentation/fb/intel810.txt>
1149 bool "use VESA Generalized Timing Formula"
1152 If you say Y, then the VESA standard, Generalized Timing Formula
1153 or GTF, will be used to calculate the required video timing values
1154 per video mode. Since the GTF allows nondiscrete timings
1155 (nondiscrete being a range of values as opposed to discrete being a
1156 set of values), you'll be able to use any combination of horizontal
1157 and vertical resolutions, and vertical refresh rates without having
1158 to specify your own timing parameters. This is especially useful
1159 to maximize the performance of an aging display, or if you just
1160 have a display with nonstandard dimensions. A VESA compliant
1161 monitor is recommended, but can still work with non-compliant ones.
1162 If you need or want this, then select this option. The timings may
1163 not be compliant with Intel's recommended values. Use at your own
1166 If you say N, the driver will revert to discrete video timings
1167 using a set recommended by Intel in their documentation.
1172 bool "Enable DDC Support"
1173 depends on FB_I810 && FB_I810_GTF
1178 tristate "Intel LE80578 (Vermilion) support"
1179 depends on FB && PCI && X86
1180 select FB_MODE_HELPERS
1181 select FB_CFB_FILLRECT
1182 select FB_CFB_COPYAREA
1183 select FB_CFB_IMAGEBLIT
1185 This driver supports the LE80578 (Vermilion Range) chipset
1187 config FB_CARILLO_RANCH
1188 tristate "Intel Carillo Ranch support"
1189 depends on FB_LE80578 && FB && PCI && X86
1191 This driver supports the LE80578 (Carillo Ranch) board
1194 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1195 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1196 select FB_MODE_HELPERS
1197 select FB_CFB_FILLRECT
1198 select FB_CFB_COPYAREA
1199 select FB_CFB_IMAGEBLIT
1200 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1201 depends on !DRM_I915
1203 This driver supports the on-board graphics built in to the Intel
1204 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1205 Say Y if you have and plan to use such a board.
1207 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1209 To compile this driver as a module, choose M here: the
1210 module will be called intelfb.
1212 For more information, please read <file:Documentation/fb/intelfb.txt>
1214 config FB_INTEL_DEBUG
1215 bool "Intel driver Debug Messages"
1218 Say Y here if you want the Intel driver to output all sorts
1219 of debugging information to provide to the maintainer when
1220 something goes wrong.
1223 bool "DDC/I2C for Intel framebuffer support"
1228 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1231 tristate "Matrox acceleration"
1232 depends on FB && PCI
1233 select FB_CFB_FILLRECT
1234 select FB_CFB_COPYAREA
1235 select FB_CFB_IMAGEBLIT
1236 select FB_TILEBLITTING
1237 select FB_MACMODES if PPC_PMAC
1239 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1240 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1241 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1242 Matrox G400, G450 or G550 card in your box.
1244 To compile this driver as a module, choose M here: the
1245 module will be called matroxfb.
1247 You can pass several parameters to the driver at boot time or at
1248 module load time. The parameters look like "video=matroxfb:XXX", and
1249 are described in <file:Documentation/fb/matroxfb.txt>.
1251 config FB_MATROX_MILLENIUM
1252 bool "Millennium I/II support"
1253 depends on FB_MATROX
1255 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1256 video card. If you select "Advanced lowlevel driver options" below,
1257 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1258 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1259 also use font widths different from 8.
1261 config FB_MATROX_MYSTIQUE
1262 bool "Mystique support"
1263 depends on FB_MATROX
1265 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1266 video card. If you select "Advanced lowlevel driver options" below,
1267 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1268 packed pixel and 32 bpp packed pixel. You can also use font widths
1272 bool "G100/G200/G400/G450/G550 support"
1273 depends on FB_MATROX
1275 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1276 video card. If you select "Advanced lowlevel driver options", you
1277 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1278 pixel and 32 bpp packed pixel. You can also use font widths
1281 If you need support for G400 secondary head, you must say Y to
1282 "Matrox I2C support" and "G400 second head support" right below.
1283 G450/G550 secondary head and digital output are supported without
1286 The driver starts in monitor mode. You must use the matroxset tool
1287 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1288 swap primary and secondary head outputs, or to change output mode.
1289 Secondary head driver always start in 640x480 resolution and you
1290 must use fbset to change it.
1292 Do not forget that second head supports only 16 and 32 bpp
1293 packed pixels, so it is a good idea to compile them into the kernel
1294 too. You can use only some font widths, as the driver uses generic
1295 painting procedures (the secondary head does not use acceleration
1298 G450/G550 hardware can display TV picture only from secondary CRTC,
1299 and it performs no scaling, so picture must have 525 or 625 lines.
1301 config FB_MATROX_I2C
1302 tristate "Matrox I2C support"
1303 depends on FB_MATROX
1306 This drivers creates I2C buses which are needed for accessing the
1307 DDC (I2C) bus present on all Matroxes, an I2C bus which
1308 interconnects Matrox optional devices, like MGA-TVO on G200 and
1309 G400, and the secondary head DDC bus, present on G400 only.
1311 You can say Y or M here if you want to experiment with monitor
1312 detection code. You must say Y or M here if you want to use either
1313 second head of G400 or MGA-TVO on G200 or G400.
1315 If you compile it as module, it will create a module named
1318 config FB_MATROX_MAVEN
1319 tristate "G400 second head support"
1320 depends on FB_MATROX_G && FB_MATROX_I2C
1322 WARNING !!! This support does not work with G450 !!!
1324 Say Y or M here if you want to use a secondary head (meaning two
1325 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1326 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1327 secondary head output is blanked while you are in X. With XFree
1328 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1329 the fbdev driver on first head and the fbdev driver on second head.
1331 If you compile it as module, two modules are created,
1332 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1333 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1334 also load i2c-matroxfb to get it to run.
1336 The driver starts in monitor mode and you must use the matroxset
1338 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1339 PAL or NTSC or to swap primary and secondary head outputs.
1340 Secondary head driver also always start in 640x480 resolution, you
1341 must use fbset to change it.
1343 Also do not forget that second head supports only 16 and 32 bpp
1344 packed pixels, so it is a good idea to compile them into the kernel
1345 too. You can use only some font widths, as the driver uses generic
1346 painting procedures (the secondary head does not use acceleration
1350 tristate "ATI Radeon display support"
1351 depends on FB && PCI
1352 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1353 select FB_MODE_HELPERS
1354 select FB_CFB_FILLRECT
1355 select FB_CFB_COPYAREA
1356 select FB_CFB_IMAGEBLIT
1357 select FB_MACMODES if PPC_OF
1359 Choose this option if you want to use an ATI Radeon graphics card as
1360 a framebuffer device. There are both PCI and AGP versions. You
1361 don't need to choose this to run the Radeon in plain VGA mode.
1363 There is a product page at
1364 http://products.amd.com/en-us/GraphicCardResult.aspx
1366 config FB_RADEON_I2C
1367 bool "DDC/I2C for ATI Radeon support"
1368 depends on FB_RADEON
1372 Say Y here if you want DDC/I2C support for your Radeon board.
1374 config FB_RADEON_BACKLIGHT
1375 bool "Support for backlight control"
1376 depends on FB_RADEON
1379 Say Y here if you want to control the backlight of your display.
1381 config FB_RADEON_DEBUG
1382 bool "Lots of debug output from Radeon driver"
1383 depends on FB_RADEON
1386 Say Y here if you want the Radeon driver to output all sorts
1387 of debugging information to provide to the maintainer when
1388 something goes wrong.
1391 tristate "ATI Rage128 display support"
1392 depends on FB && PCI
1393 select FB_CFB_FILLRECT
1394 select FB_CFB_COPYAREA
1395 select FB_CFB_IMAGEBLIT
1396 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1397 select FB_MACMODES if PPC_PMAC
1399 This driver supports graphics boards with the ATI Rage128 chips.
1400 Say Y if you have such a graphics board and read
1401 <file:Documentation/fb/aty128fb.txt>.
1403 To compile this driver as a module, choose M here: the
1404 module will be called aty128fb.
1406 config FB_ATY128_BACKLIGHT
1407 bool "Support for backlight control"
1408 depends on FB_ATY128
1411 Say Y here if you want to control the backlight of your display.
1414 tristate "ATI Mach64 display support" if PCI || ATARI
1415 depends on FB && !SPARC32
1416 select FB_CFB_FILLRECT
1417 select FB_CFB_COPYAREA
1418 select FB_CFB_IMAGEBLIT
1419 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1420 select FB_MACMODES if PPC
1422 This driver supports graphics boards with the ATI Mach64 chips.
1423 Say Y if you have such a graphics board.
1425 To compile this driver as a module, choose M here: the
1426 module will be called atyfb.
1429 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1430 depends on PCI && FB_ATY
1431 default y if SPARC64 && PCI
1433 Say Y here to support use of ATI's 64-bit Rage boards (or other
1434 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1435 framebuffer device. The ATI product support page for these boards
1436 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1438 config FB_ATY_GENERIC_LCD
1439 bool "Mach64 generic LCD support"
1440 depends on FB_ATY_CT
1442 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1443 Rage XC, or Rage XL chipset.
1446 bool "Mach64 GX support" if PCI
1450 Say Y here to support use of the ATI Mach64 Graphics Expression
1451 board (or other boards based on the Mach64 GX chipset) as a
1452 framebuffer device. The ATI product support page for these boards
1454 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1456 config FB_ATY_BACKLIGHT
1457 bool "Support for backlight control"
1461 Say Y here if you want to control the backlight of your display.
1464 tristate "S3 Trio/Virge support"
1465 depends on FB && PCI
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1469 select FB_TILEBLITTING
1472 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1474 Driver for graphics boards with S3 Trio / S3 Virge chip.
1477 bool "DDC for S3 support"
1482 Say Y here if you want DDC support for your S3 graphics card.
1485 tristate "S3 Savage support"
1486 depends on FB && PCI
1487 select FB_MODE_HELPERS
1488 select FB_CFB_FILLRECT
1489 select FB_CFB_COPYAREA
1490 select FB_CFB_IMAGEBLIT
1493 This driver supports notebooks and computers with S3 Savage PCI/AGP
1496 Say Y if you have such a graphics card.
1498 To compile this driver as a module, choose M here; the module
1499 will be called savagefb.
1501 config FB_SAVAGE_I2C
1502 bool "Enable DDC2 Support"
1503 depends on FB_SAVAGE
1506 This enables I2C support for S3 Savage Chipsets. This is used
1507 only for getting EDID information from the attached display
1508 allowing for robust video mode handling and switching.
1510 Because fbdev-2.6 requires that drivers must be able to
1511 independently validate video mode parameters, you should say Y
1514 config FB_SAVAGE_ACCEL
1515 bool "Enable Console Acceleration"
1516 depends on FB_SAVAGE
1519 This option will compile in console acceleration support. If
1520 the resulting framebuffer console has bothersome glitches, then
1524 tristate "SiS/XGI display support"
1525 depends on FB && PCI
1526 select FB_CFB_FILLRECT
1527 select FB_CFB_COPYAREA
1528 select FB_CFB_IMAGEBLIT
1529 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1531 This is the frame buffer device driver for the SiS 300, 315, 330
1532 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1533 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1535 To compile this driver as a module, choose M here; the module
1536 will be called sisfb.
1539 bool "SiS 300 series support"
1542 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1545 bool "SiS 315/330/340 series and XGI support"
1548 Say Y here to support use of the SiS 315, 330 and 340 series
1549 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1550 as XGI V3XT, V5, V8 and Z7.
1553 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1554 depends on FB && PCI && X86
1555 select FB_CFB_FILLRECT
1556 select FB_CFB_COPYAREA
1557 select FB_CFB_IMAGEBLIT
1562 This is the frame buffer device driver for Graphics chips of VIA
1563 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1564 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1566 Say Y if you have a VIA UniChrome graphics board.
1568 To compile this driver as a module, choose M here: the
1569 module will be called viafb.
1573 config FB_VIA_DIRECT_PROCFS
1574 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1578 Allow direct hardware access to some output registers via procfs.
1579 This is dangerous but may provide the only chance to get the
1580 correct output device configuration.
1581 Its use is strongly discouraged.
1583 config FB_VIA_X_COMPATIBILITY
1584 bool "X server compatibility"
1588 This option reduces the functionality (power saving, ...) of the
1589 framebuffer to avoid negative impact on the OpenChrome X server.
1590 If you use any X server other than fbdev you should enable this
1591 otherwise it should be safe to disable it and allow using all
1597 tristate "NeoMagic display support"
1598 depends on FB && PCI
1599 select FB_MODE_HELPERS
1600 select FB_CFB_FILLRECT
1601 select FB_CFB_COPYAREA
1602 select FB_CFB_IMAGEBLIT
1605 This driver supports notebooks with NeoMagic PCI chips.
1606 Say Y if you have such a graphics card.
1608 To compile this driver as a module, choose M here: the
1609 module will be called neofb.
1612 tristate "IMG Kyro support"
1613 depends on FB && PCI
1614 select FB_CFB_FILLRECT
1615 select FB_CFB_COPYAREA
1616 select FB_CFB_IMAGEBLIT
1618 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1621 To compile this driver as a module, choose M here: the
1622 module will be called kyrofb.
1625 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1626 depends on FB && PCI
1627 select FB_CFB_IMAGEBLIT
1628 select FB_CFB_FILLRECT
1629 select FB_CFB_COPYAREA
1630 select FB_MODE_HELPERS
1632 This driver supports graphics boards with the 3Dfx Banshee,
1633 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1634 such a graphics board.
1636 To compile this driver as a module, choose M here: the
1637 module will be called tdfxfb.
1639 config FB_3DFX_ACCEL
1640 bool "3Dfx Acceleration functions"
1643 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1644 device driver with acceleration functions.
1647 bool "Enable DDC/I2C support"
1652 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1655 tristate "3Dfx Voodoo Graphics (sst1) support"
1656 depends on FB && PCI
1657 select FB_CFB_FILLRECT
1658 select FB_CFB_COPYAREA
1659 select FB_CFB_IMAGEBLIT
1661 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1662 Voodoo2 (cvg) based graphics card.
1664 To compile this driver as a module, choose M here: the
1665 module will be called sstfb.
1667 WARNING: Do not use any application that uses the 3D engine
1668 (namely glide) while using this driver.
1669 Please read the <file:Documentation/fb/sstfb.txt> for supported
1670 options and other important info support.
1673 tristate "VIA VT8623 support"
1674 depends on FB && PCI
1675 select FB_CFB_FILLRECT
1676 select FB_CFB_COPYAREA
1677 select FB_CFB_IMAGEBLIT
1678 select FB_TILEBLITTING
1681 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1683 Driver for CastleRock integrated graphics core in the
1684 VIA VT8623 [Apollo CLE266] chipset.
1687 tristate "Trident/CyberXXX/CyberBlade support"
1688 depends on FB && PCI
1689 select FB_CFB_FILLRECT
1690 select FB_CFB_COPYAREA
1691 select FB_CFB_IMAGEBLIT
1693 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1694 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1696 There are also integrated versions of these chips called CyberXXXX,
1697 CyberImage or CyberBlade. These chips are mostly found in laptops
1698 but also on some motherboards including early VIA EPIA motherboards.
1699 For more information, read <file:Documentation/fb/tridentfb.txt>
1701 Say Y if you have such a graphics board.
1703 To compile this driver as a module, choose M here: the
1704 module will be called tridentfb.
1707 tristate "ARK 2000PV support"
1708 depends on FB && PCI
1709 select FB_CFB_FILLRECT
1710 select FB_CFB_COPYAREA
1711 select FB_CFB_IMAGEBLIT
1712 select FB_TILEBLITTING
1715 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1717 Driver for PCI graphics boards with ARK 2000PV chip
1718 and ICS 5342 RAMDAC.
1721 tristate "Permedia3 support"
1722 depends on FB && PCI
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 This is the frame buffer device driver for the 3DLabs Permedia3
1728 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1729 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1730 and maybe other boards.
1733 tristate "Fujitsu carmine frame buffer support"
1734 depends on FB && PCI
1735 select FB_CFB_FILLRECT
1736 select FB_CFB_COPYAREA
1737 select FB_CFB_IMAGEBLIT
1739 This is the frame buffer device driver for the Fujitsu Carmine chip.
1740 The driver provides two independent frame buffer devices.
1743 depends on FB_CARMINE
1744 prompt "DRAM timing"
1745 default FB_CARMINE_DRAM_EVAL
1747 config FB_CARMINE_DRAM_EVAL
1748 bool "Eval board timings"
1750 Use timings which work on the eval card.
1752 config CARMINE_DRAM_CUSTOM
1753 bool "Custom board timings"
1755 Use custom board timings.
1759 bool "Au1100 LCD Driver"
1760 depends on (FB = y) && MIPS_ALCHEMY
1761 select FB_CFB_FILLRECT
1762 select FB_CFB_COPYAREA
1763 select FB_CFB_IMAGEBLIT
1765 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1766 various panels and CRTs by passing in kernel cmd line option
1767 au1100fb:panel=<name>.
1770 bool "Au1200/Au1300 LCD Driver"
1771 depends on (FB = y) && MIPS_ALCHEMY
1772 select FB_SYS_FILLRECT
1773 select FB_SYS_COPYAREA
1774 select FB_SYS_IMAGEBLIT
1777 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1778 It can drive various panels and CRTs by passing in kernel cmd line
1779 option au1200fb:panel=<name>.
1782 bool "VIA VT8500 framebuffer support"
1783 depends on (FB = y) && ARM && ARCH_VT8500
1784 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1785 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1786 select FB_SYS_IMAGEBLIT
1787 select FB_MODE_HELPERS
1788 select VIDEOMODE_HELPERS
1790 This is the framebuffer driver for VIA VT8500 integrated LCD
1794 bool "Wondermedia WM8xxx-series frame buffer support"
1795 depends on (FB = y) && ARM && ARCH_VT8500
1796 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1797 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1798 select FB_SYS_IMAGEBLIT
1799 select FB_MODE_HELPERS
1800 select VIDEOMODE_HELPERS
1802 This is the framebuffer driver for WonderMedia WM8xxx-series
1803 integrated LCD controller. This driver covers the WM8505, WM8650
1806 config FB_WMT_GE_ROPS
1807 bool "VT8500/WM8xxx accelerated raster ops support"
1808 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1811 This adds support for accelerated raster operations on the
1812 VIA VT8500 and Wondermedia 85xx series SoCs.
1814 source "drivers/video/geode/Kconfig"
1817 tristate "HD64461 Frame Buffer support"
1818 depends on FB && HD64461
1819 select FB_CFB_FILLRECT
1820 select FB_CFB_COPYAREA
1821 select FB_CFB_IMAGEBLIT
1823 This is the frame buffer device driver for the Hitachi HD64461 LCD
1827 bool "PMAG-AA TURBOchannel framebuffer support"
1828 depends on (FB = y) && TC
1829 select FB_CFB_FILLRECT
1830 select FB_CFB_COPYAREA
1831 select FB_CFB_IMAGEBLIT
1833 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1834 used mainly in the MIPS-based DECstation series.
1837 tristate "PMAG-BA TURBOchannel framebuffer support"
1839 select FB_CFB_FILLRECT
1840 select FB_CFB_COPYAREA
1841 select FB_CFB_IMAGEBLIT
1843 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1844 used mainly in the MIPS-based DECstation series.
1847 tristate "PMAGB-B TURBOchannel framebuffer support"
1849 select FB_CFB_FILLRECT
1850 select FB_CFB_COPYAREA
1851 select FB_CFB_IMAGEBLIT
1853 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1854 in the MIPS-based DECstation series. The card is currently only
1855 supported in 1280x1024x8 mode.
1858 bool "Maxine (Personal DECstation) onboard framebuffer support"
1859 depends on (FB = y) && MACH_DECSTATION
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1864 Support for the onboard framebuffer (1024x768x8) in the Personal
1865 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1869 bool "G364 frame buffer support"
1870 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1871 select FB_CFB_FILLRECT
1872 select FB_CFB_COPYAREA
1873 select FB_CFB_IMAGEBLIT
1875 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1876 Olivetti M700-10 systems.
1879 bool "Motorola 68328 native frame buffer support"
1880 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1881 select FB_CFB_FILLRECT
1882 select FB_CFB_COPYAREA
1883 select FB_CFB_IMAGEBLIT
1885 Say Y here if you want to support the built-in frame buffer of
1886 the Motorola 68328 CPU family.
1889 tristate "PXA168/910 LCD framebuffer support"
1890 depends on FB && (CPU_PXA168 || CPU_PXA910)
1891 select FB_CFB_FILLRECT
1892 select FB_CFB_COPYAREA
1893 select FB_CFB_IMAGEBLIT
1895 Frame buffer driver for the built-in LCD controller in the Marvell
1899 tristate "PXA LCD framebuffer support"
1900 depends on FB && ARCH_PXA
1901 select FB_CFB_FILLRECT
1902 select FB_CFB_COPYAREA
1903 select FB_CFB_IMAGEBLIT
1905 Frame buffer driver for the built-in LCD controller in the Intel
1908 This driver is also available as a module ( = code which can be
1909 inserted and removed from the running kernel whenever you want). The
1910 module will be called pxafb. If you want to compile it as a module,
1911 say M here and read <file:Documentation/kbuild/modules.txt>.
1915 config FB_PXA_OVERLAY
1916 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1918 depends on FB_PXA && (PXA27x || PXA3xx)
1920 config FB_PXA_SMARTPANEL
1921 bool "PXA Smartpanel LCD support"
1925 config FB_PXA_PARAMETERS
1926 bool "PXA LCD command line parameters"
1930 Enable the use of kernel command line or module parameters
1931 to configure the physical properties of the LCD panel when
1932 using the PXA LCD driver.
1934 This option allows you to override the panel parameters
1935 supplied by the platform in order to support multiple
1936 different models of flatpanel. If you will only be using a
1937 single model of flatpanel then you can safely leave this
1940 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1943 tristate "PXA3xx 2D graphics accelerator driver"
1946 Kernelspace driver for the 2D graphics controller unit (GCU)
1947 found on PXA3xx processors. There is a counterpart driver in the
1948 DirectFB suite, see http://www.directfb.org/
1950 If you compile this as a module, it will be called pxa3xx_gcu.
1953 tristate "2700G LCD framebuffer support"
1954 depends on FB && ARCH_PXA
1955 select FB_CFB_FILLRECT
1956 select FB_CFB_COPYAREA
1957 select FB_CFB_IMAGEBLIT
1959 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1963 bool "Enable debugging info via debugfs"
1964 depends on FB_MBX && DEBUG_FS
1967 Enable this if you want debugging information using the debug
1968 filesystem (debugfs)
1973 tristate "Freescale DIU framebuffer support"
1974 depends on FB && FSL_SOC
1975 select FB_MODE_HELPERS
1976 select FB_CFB_FILLRECT
1977 select FB_CFB_COPYAREA
1978 select FB_CFB_IMAGEBLIT
1979 select PPC_LIB_RHEAP
1981 Framebuffer driver for the Freescale SoC DIU
1984 tristate "W100 frame buffer support"
1985 depends on FB && ARCH_PXA
1986 select FB_CFB_FILLRECT
1987 select FB_CFB_COPYAREA
1988 select FB_CFB_IMAGEBLIT
1990 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1991 It can also drive the w3220 chip found on iPAQ hx4700.
1993 This driver is also available as a module ( = code which can be
1994 inserted and removed from the running kernel whenever you want). The
1995 module will be called w100fb. If you want to compile it as a module,
1996 say M here and read <file:Documentation/kbuild/modules.txt>.
2000 config FB_SH_MOBILE_LCDC
2001 tristate "SuperH Mobile LCDC framebuffer support"
2002 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2003 select FB_SYS_FILLRECT
2004 select FB_SYS_COPYAREA
2005 select FB_SYS_IMAGEBLIT
2007 select FB_DEFERRED_IO
2009 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2011 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2013 config FB_SH_MOBILE_HDMI
2014 tristate "SuperH Mobile HDMI controller support"
2015 depends on FB_SH_MOBILE_LCDC
2016 select FB_MODE_HELPERS
2021 Driver for the on-chip SH-Mobile HDMI controller.
2024 tristate "Toshiba Mobile IO FrameBuffer support"
2025 depends on FB && MFD_CORE
2026 select FB_CFB_FILLRECT
2027 select FB_CFB_COPYAREA
2028 select FB_CFB_IMAGEBLIT
2030 Frame buffer driver for the Toshiba Mobile IO integrated as found
2031 on the Sharp SL-6000 series
2033 This driver is also available as a module ( = code which can be
2034 inserted and removed from the running kernel whenever you want). The
2035 module will be called tmiofb. If you want to compile it as a module,
2036 say M here and read <file:Documentation/kbuild/modules.txt>.
2040 config FB_TMIO_ACCELL
2041 bool "tmiofb acceleration"
2046 tristate "Samsung S3C framebuffer support"
2047 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2048 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2049 select FB_CFB_FILLRECT
2050 select FB_CFB_COPYAREA
2051 select FB_CFB_IMAGEBLIT
2053 Frame buffer driver for the built-in FB controller in the Samsung
2054 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2055 and the S3C64XX series such as the S3C6400 and S3C6410.
2057 These chips all have the same basic framebuffer design with the
2058 actual capabilities depending on the chip. For instance the S3C6400
2059 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2060 currently only have two.
2062 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2064 config FB_S3C_DEBUG_REGWRITE
2065 bool "Debug register writes"
2068 Show all register writes via pr_debug()
2071 tristate "S3C2410 LCD framebuffer support"
2072 depends on FB && ARCH_S3C24XX
2073 select FB_CFB_FILLRECT
2074 select FB_CFB_COPYAREA
2075 select FB_CFB_IMAGEBLIT
2077 Frame buffer driver for the built-in LCD controller in the Samsung
2080 This driver is also available as a module ( = code which can be
2081 inserted and removed from the running kernel whenever you want). The
2082 module will be called s3c2410fb. If you want to compile it as a module,
2083 say M here and read <file:Documentation/kbuild/modules.txt>.
2086 config FB_S3C2410_DEBUG
2087 bool "S3C2410 lcd debug messages"
2088 depends on FB_S3C2410
2090 Turn on debugging messages. Note that you can set/unset at run time
2094 bool "NUC900 LCD framebuffer support"
2095 depends on FB && ARCH_W90X900
2096 select FB_CFB_FILLRECT
2097 select FB_CFB_COPYAREA
2098 select FB_CFB_IMAGEBLIT
2100 Frame buffer driver for the built-in LCD controller in the Nuvoton
2103 config GPM1040A0_320X240
2104 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2105 depends on FB_NUC900
2108 tristate "Silicon Motion SM501 framebuffer support"
2109 depends on FB && MFD_SM501
2110 select FB_CFB_FILLRECT
2111 select FB_CFB_COPYAREA
2112 select FB_CFB_IMAGEBLIT
2114 Frame buffer driver for the CRT and LCD controllers in the Silicon
2117 This driver is also available as a module ( = code which can be
2118 inserted and removed from the running kernel whenever you want). The
2119 module will be called sm501fb. If you want to compile it as a module,
2120 say M here and read <file:Documentation/kbuild/modules.txt>.
2125 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2126 depends on FB && USB
2127 select FB_MODE_HELPERS
2128 select FB_SYS_FILLRECT
2129 select FB_SYS_COPYAREA
2130 select FB_SYS_IMAGEBLIT
2132 select FB_DEFERRED_IO
2134 This is a kernel framebuffer driver for SMSC UFX USB devices.
2135 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2136 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2138 To compile as a module, choose M here: the module name is smscufx.
2141 tristate "Displaylink USB Framebuffer support"
2142 depends on FB && USB
2143 select FB_MODE_HELPERS
2144 select FB_SYS_FILLRECT
2145 select FB_SYS_COPYAREA
2146 select FB_SYS_IMAGEBLIT
2148 select FB_DEFERRED_IO
2150 This is a kernel framebuffer driver for DisplayLink USB devices.
2151 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2152 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2153 To compile as a module, choose M here: the module name is udlfb.
2155 config FB_IBM_GXT4500
2156 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2157 depends on FB && PPC
2158 select FB_CFB_FILLRECT
2159 select FB_CFB_COPYAREA
2160 select FB_CFB_IMAGEBLIT
2162 Say Y here to enable support for the IBM GXT4000P/6000P and
2163 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2164 found on some IBM System P (pSeries) machines. This driver
2165 doesn't use Geometry Engine GT1000.
2168 tristate "PS3 GPU framebuffer driver"
2169 depends on FB && PS3_PS3AV
2170 select FB_SYS_FILLRECT
2171 select FB_SYS_COPYAREA
2172 select FB_SYS_IMAGEBLIT
2174 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2176 Include support for the virtual frame buffer in the PS3 platform.
2178 config FB_PS3_DEFAULT_SIZE_M
2179 int "PS3 default frame buffer size (in MiB)"
2183 This is the default size (in MiB) of the virtual frame buffer in
2185 The default value can be overridden on the kernel command line
2186 using the "ps3fb" option (e.g. "ps3fb=9M");
2189 tristate "Xilinx frame buffer support"
2190 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2191 select FB_CFB_FILLRECT
2192 select FB_CFB_COPYAREA
2193 select FB_CFB_IMAGEBLIT
2195 Include support for the Xilinx ML300/ML403 reference design
2196 framebuffer. ML300 carries a 640*480 LCD display on the board,
2197 ML403 uses a standard DB15 VGA connector.
2200 tristate "Goldfish Framebuffer"
2201 depends on FB && HAS_DMA
2202 select FB_CFB_FILLRECT
2203 select FB_CFB_COPYAREA
2204 select FB_CFB_IMAGEBLIT
2206 Framebuffer driver for Goldfish Virtual Platform
2209 tristate "Cobalt server LCD frame buffer support"
2210 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2213 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2214 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2215 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2216 select FB_CFB_FILLRECT
2217 select FB_CFB_COPYAREA
2218 select FB_CFB_IMAGEBLIT
2220 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2221 (D)STN/TFT LCD Controller.
2222 Supports display resolutions up to 1024x1024 pixel, grayscale and
2223 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2224 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2225 panels <= 320 pixel horizontal resolution.
2228 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2229 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2230 select FB_CFB_FILLRECT
2231 select FB_CFB_COPYAREA
2232 select FB_CFB_IMAGEBLIT
2233 select FB_CFB_REV_PIXELS_IN_BYTE
2234 select FB_MODE_HELPERS
2235 select VIDEOMODE_HELPERS
2237 This is the frame buffer device driver for the TI LCD controller
2238 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2242 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2244 select FB_SYS_FILLRECT
2245 select FB_SYS_COPYAREA
2246 select FB_SYS_IMAGEBLIT
2249 This is a `virtual' frame buffer device. It operates on a chunk of
2250 unswappable kernel memory instead of on the memory of a graphics
2251 board. This means you cannot see any output sent to this frame
2252 buffer device, while it does consume precious memory. The main use
2253 of this frame buffer device is testing and debugging the frame
2254 buffer subsystem. Do NOT enable it for normal systems! To protect
2255 the innocent, it has to be enabled explicitly at boot time using the
2256 kernel option `video=vfb:'.
2258 To compile this driver as a module, choose M here: the
2259 module will be called vfb. In order to load it, you must use
2260 the vfb_enable=1 option.
2264 config XEN_FBDEV_FRONTEND
2265 tristate "Xen virtual frame buffer support"
2266 depends on FB && XEN
2267 select FB_SYS_FILLRECT
2268 select FB_SYS_COPYAREA
2269 select FB_SYS_IMAGEBLIT
2271 select FB_DEFERRED_IO
2272 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2273 select XEN_XENBUS_FRONTEND
2276 This driver implements the front-end of the Xen virtual
2277 frame buffer driver. It communicates with a back-end
2281 tristate "E-Ink Metronome/8track controller support"
2283 select FB_SYS_FILLRECT
2284 select FB_SYS_COPYAREA
2285 select FB_SYS_IMAGEBLIT
2287 select FB_DEFERRED_IO
2289 This driver implements support for the E-Ink Metronome
2290 controller. The pre-release name for this device was 8track
2291 and could also have been called by some vendors as PVI-nnnn.
2294 tristate "Fujitsu MB862xx GDC support"
2296 depends on PCI || (OF && PPC)
2297 select FB_CFB_FILLRECT
2298 select FB_CFB_COPYAREA
2299 select FB_CFB_IMAGEBLIT
2301 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2304 prompt "GDC variant"
2305 depends on FB_MB862XX
2307 config FB_MB862XX_PCI_GDC
2308 bool "Carmine/Coral-P(A) GDC"
2311 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2312 PCI graphics controller devices.
2314 config FB_MB862XX_LIME
2316 depends on OF && PPC
2317 select FB_FOREIGN_ENDIAN
2318 select FB_LITTLE_ENDIAN
2320 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2324 config FB_MB862XX_I2C
2325 bool "Support I2C bus on MB862XX GDC"
2326 depends on FB_MB862XX && I2C
2329 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2330 driver to support accessing I2C devices on controller's I2C bus.
2331 These are usually some video decoder chips.
2334 tristate "EP93XX frame buffer support"
2335 depends on FB && ARCH_EP93XX
2336 select FB_CFB_FILLRECT
2337 select FB_CFB_COPYAREA
2338 select FB_CFB_IMAGEBLIT
2340 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2341 This driver is also available as a module. The module will be called
2344 config FB_PRE_INIT_FB
2345 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2346 depends on FB && FB_MB862XX_LIME
2348 Select this option if display contents should be inherited as set by
2352 tristate "MSM Framebuffer support"
2353 depends on FB && ARCH_MSM
2354 select FB_CFB_FILLRECT
2355 select FB_CFB_COPYAREA
2356 select FB_CFB_IMAGEBLIT
2359 tristate "MX3 Framebuffer support"
2360 depends on FB && MX3_IPU
2361 select FB_CFB_FILLRECT
2362 select FB_CFB_COPYAREA
2363 select FB_CFB_IMAGEBLIT
2366 This is a framebuffer device for the i.MX31 LCD Controller. So
2367 far only synchronous displays are supported. If you plan to use
2368 an LCD display with your i.MX31 system, say Y here.
2370 config FB_BROADSHEET
2371 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2373 select FB_SYS_FILLRECT
2374 select FB_SYS_COPYAREA
2375 select FB_SYS_IMAGEBLIT
2377 select FB_DEFERRED_IO
2379 This driver implements support for the E-Ink Broadsheet
2380 controller. The release name for this device was Epson S1D13521
2381 and could also have been called by other names when coupled with
2385 tristate "AUO-K190X EPD controller support"
2387 select FB_SYS_FILLRECT
2388 select FB_SYS_COPYAREA
2389 select FB_SYS_IMAGEBLIT
2391 select FB_DEFERRED_IO
2393 Provides support for epaper controllers from the K190X series
2394 of AUO. These controllers can be used to drive epaper displays
2397 This option enables the common support, shared by the individual
2398 controller drivers. You will also have to enable the driver
2399 for the controller type used in your device.
2402 tristate "AUO-K1900 EPD controller support"
2403 depends on FB && FB_AUO_K190X
2405 This driver implements support for the AUO K1900 epd-controller.
2406 This controller can drive Sipix epaper displays but can only do
2407 serial updates, reducing the number of possible frames per second.
2410 tristate "AUO-K1901 EPD controller support"
2411 depends on FB && FB_AUO_K190X
2413 This driver implements support for the AUO K1901 epd-controller.
2414 This controller can drive Sipix epaper displays and supports
2415 concurrent updates, making higher frames per second possible.
2418 tristate "JZ4740 LCD framebuffer support"
2419 depends on FB && MACH_JZ4740
2420 select FB_SYS_FILLRECT
2421 select FB_SYS_COPYAREA
2422 select FB_SYS_IMAGEBLIT
2424 Framebuffer support for the JZ4740 SoC.
2427 tristate "MXS LCD framebuffer support"
2428 depends on FB && ARCH_MXS
2429 select FB_CFB_FILLRECT
2430 select FB_CFB_COPYAREA
2431 select FB_CFB_IMAGEBLIT
2432 select FB_MODE_HELPERS
2433 select VIDEOMODE_HELPERS
2435 Framebuffer support for the MXS SoC.
2437 config FB_PUV3_UNIGFX
2438 tristate "PKUnity v3 Unigfx framebuffer support"
2439 depends on FB && UNICORE32 && ARCH_PUV3
2440 select FB_SYS_FILLRECT
2441 select FB_SYS_COPYAREA
2442 select FB_SYS_IMAGEBLIT
2445 Choose this option if you want to use the Unigfx device as a
2446 framebuffer device. Without the support of PCI & AGP.
2449 tristate "Microsoft Hyper-V Synthetic Video support"
2450 depends on FB && HYPERV
2451 select FB_CFB_FILLRECT
2452 select FB_CFB_COPYAREA
2453 select FB_CFB_IMAGEBLIT
2455 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2458 bool "Simple framebuffer support"
2460 select FB_CFB_FILLRECT
2461 select FB_CFB_COPYAREA
2462 select FB_CFB_IMAGEBLIT
2464 Say Y if you want support for a simple frame-buffer.
2466 This driver assumes that the display hardware has been initialized
2467 before the kernel boots, and the kernel will simply render to the
2468 pre-allocated frame buffer surface.
2470 Configuration re: surface address, size, and format must be provided
2471 through device tree, or plain old platform data.
2473 source "drivers/video/omap/Kconfig"
2474 source "drivers/video/omap2/Kconfig"
2475 source "drivers/video/exynos/Kconfig"
2476 source "drivers/video/mmp/Kconfig"
2477 source "drivers/video/backlight/Kconfig"
2480 source "drivers/video/console/Kconfig"
2483 if FB || SGI_NEWPORT_CONSOLE
2484 source "drivers/video/logo/Kconfig"
2487 config FB_SH_MOBILE_MERAM
2488 tristate "SuperH Mobile MERAM read ahead support"
2489 depends on (SUPERH || ARCH_SHMOBILE)
2490 select GENERIC_ALLOCATOR
2492 Enable MERAM support for the SuperH controller.
2494 This will allow for caching of the framebuffer to provide more
2495 reliable access under heavy main memory bus traffic situations.
2496 Up to 4 memory channels can be configured, allowing 4 RGB or
2497 2 YCbCr framebuffers to be configured.
2500 tristate "Solomon SSD1307 framebuffer support"
2501 depends on FB && I2C
2505 select FB_SYS_FILLRECT
2506 select FB_SYS_COPYAREA
2507 select FB_SYS_IMAGEBLIT
2508 select FB_DEFERRED_IO
2511 This driver implements support for the Solomon SSD1307
2512 OLED controller over I2C.