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"
24 source "drivers/gpu/host1x/Kconfig"
26 source "drivers/gpu/sprd_iommu/Kconfig"
28 source "drivers/gpu/arm/Kconfig"
34 config VIDEO_OUTPUT_CONTROL
35 tristate "Lowlevel video output switch controls"
37 This framework adds support for low-level control of the video
40 config VIDEOMODE_HELPERS
46 config VEXPRESS_DVI_CONTROL
47 bool "Versatile Express DVI control"
48 depends on FB && VEXPRESS_CONFIG
52 tristate "Support for frame buffer devices"
54 The frame buffer device provides an abstraction for the graphics
55 hardware. It represents the frame buffer of some video hardware and
56 allows application software to access the graphics hardware through
57 a well-defined interface, so the software doesn't need to know
58 anything about the low-level (hardware register) stuff.
60 Frame buffer devices work identically across the different
61 architectures supported by Linux and make the implementation of
62 application programs easier and more portable; at this point, an X
63 server exists which uses the frame buffer device exclusively.
64 On several non-X86 architectures, the frame buffer device is the
65 only way to use the graphics hardware.
67 The device is accessed through special device nodes, usually located
68 in the /dev directory, i.e. /dev/fb*.
70 You need an utility program called fbset to make full use of frame
71 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
72 and the Framebuffer-HOWTO at
73 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
76 Say Y here and to the driver for your graphics board below if you
77 are compiling a kernel for a non-x86 architecture.
79 If you are compiling for the x86 architecture, you can say Y if you
80 want to play with it, but it is not essential. Please note that
81 running graphical applications that directly touch the hardware
82 (e.g. an accelerated X server) and that are not frame buffer
83 device-aware may cause unexpected results. If unsure, say N.
86 bool "Enable firmware EDID"
90 This enables access to the EDID transferred from the firmware.
91 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
92 transfers do not work for your driver and if you are using
93 nvidiafb, i810fb or savagefb.
95 In general, choosing Y for this option is safe. If you
96 experience extremely long delays while booting before you get
97 something on your display, try setting this to N. Matrox cards in
98 combination with certain motherboards and monitors are known to
99 suffer from this problem.
108 config FB_BOOT_VESA_SUPPORT
113 If true, at least one selected framebuffer driver can take advantage
114 of VESA video modes set at an early boot stage via the vga= parameter.
116 config FB_CFB_FILLRECT
121 Include the cfb_fillrect function for generic software rectangle
122 filling. This is used by drivers that don't provide their own
123 (accelerated) version.
125 config FB_CFB_COPYAREA
130 Include the cfb_copyarea function for generic software area copying.
131 This is used by drivers that don't provide their own (accelerated)
134 config FB_CFB_IMAGEBLIT
139 Include the cfb_imageblit function for generic software image
140 blitting. This is used by drivers that don't provide their own
141 (accelerated) version.
143 config FB_CFB_REV_PIXELS_IN_BYTE
148 Allow generic frame-buffer functions to work on displays with 1, 2
149 and 4 bits per pixel depths which has opposite order of pixels in
150 byte order to bytes in long order.
152 config FB_SYS_FILLRECT
157 Include the sys_fillrect function for generic software rectangle
158 filling. This is used by drivers that don't provide their own
159 (accelerated) version and the framebuffer is in system RAM.
161 config FB_SYS_COPYAREA
166 Include the sys_copyarea function for generic software area copying.
167 This is used by drivers that don't provide their own (accelerated)
168 version and the framebuffer is in system RAM.
170 config FB_SYS_IMAGEBLIT
175 Include the sys_imageblit function for generic software image
176 blitting. This is used by drivers that don't provide their own
177 (accelerated) version and the framebuffer is in system RAM.
179 menuconfig FB_FOREIGN_ENDIAN
180 bool "Framebuffer foreign endianness support"
183 This menu will let you enable support for the framebuffers with
184 non-native endianness (e.g. Little-Endian framebuffer on a
185 Big-Endian machine). Most probably you don't have such hardware,
186 so it's safe to say "n" here.
189 prompt "Choice endianness support"
190 depends on FB_FOREIGN_ENDIAN
192 config FB_BOTH_ENDIAN
193 bool "Support for Big- and Little-Endian framebuffers"
196 bool "Support for Big-Endian framebuffers only"
198 config FB_LITTLE_ENDIAN
199 bool "Support for Little-Endian framebuffers only"
208 config FB_DEFERRED_IO
215 depends on FB_DEFERRED_IO
222 Common utility functions useful to fbdev drivers of VGA-based
233 select BACKLIGHT_LCD_SUPPORT
234 select BACKLIGHT_CLASS_DEVICE
237 config FB_MODE_HELPERS
238 bool "Enable Video Mode Handling Helpers"
242 This enables functions for handling video modes using the
243 Generalized Timing Formula and the EDID parser. A few drivers rely
244 on this feature such as the radeonfb, rivafb, and the i810fb. If
245 your driver does not take advantage of this feature, choosing Y will
246 just increase the kernel size by about 5K.
248 config FB_TILEBLITTING
249 bool "Enable Tile Blitting Support"
253 This enables tile blitting. Tile blitting is a drawing technique
254 where the screen is divided into rectangular sections (tiles), whereas
255 the standard blitting divides the screen into pixels. Because the
256 default drawing element is a tile, drawing functions will be passed
257 parameters in terms of number of tiles instead of number of pixels.
258 For example, to draw a single character, instead of using bitmaps,
259 an index to an array of bitmaps will be used. To clear or move a
260 rectangular section of a screen, the rectangle will be described in
261 terms of number of tiles in the x- and y-axis.
263 This is particularly important to one driver, matroxfb. If
266 comment "Frame buffer hardware drivers"
270 tristate "Aeroflex Gaisler framebuffer support"
271 depends on FB && SPARC
272 select FB_CFB_FILLRECT
273 select FB_CFB_COPYAREA
274 select FB_CFB_IMAGEBLIT
276 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
279 tristate "Cirrus Logic support"
280 depends on FB && (ZORRO || PCI)
281 select FB_CFB_FILLRECT
282 select FB_CFB_COPYAREA
283 select FB_CFB_IMAGEBLIT
285 This enables support for Cirrus Logic GD542x/543x based boards on
286 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
288 If you have a PCI-based system, this enables support for these
289 chips: GD-543x, GD-544x, GD-5480.
291 Please read the file <file:Documentation/fb/cirrusfb.txt>.
293 Say N unless you have such a graphics board or plan to get one
294 before you next recompile the kernel.
297 tristate "Permedia2 support"
298 depends on FB && ((AMIGA && BROKEN) || PCI)
299 select FB_CFB_FILLRECT
300 select FB_CFB_COPYAREA
301 select FB_CFB_IMAGEBLIT
303 This is the frame buffer device driver for cards based on
304 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
305 The driver was tested on the following cards:
306 Diamond FireGL 1000 PRO AGP
307 ELSA Gloria Synergy PCI
308 Appian Jeronimo PRO (both heads) PCI
309 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
310 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
311 ASK Graphic Blaster Exxtreme AGP
313 To compile this driver as a module, choose M here: the
314 module will be called pm2fb.
316 config FB_PM2_FIFO_DISCONNECT
317 bool "enable FIFO disconnect feature"
318 depends on FB_PM2 && PCI
320 Support the Permedia2 FIFO disconnect feature.
323 tristate "ARM PrimeCell PL110 support"
324 depends on ARM || ARM64 || COMPILE_TEST
325 depends on FB && ARM_AMBA
326 select FB_CFB_FILLRECT
327 select FB_CFB_COPYAREA
328 select FB_CFB_IMAGEBLIT
330 This framebuffer device driver is for the ARM PrimeCell PL110
331 Colour LCD controller. ARM PrimeCells provide the building
332 blocks for System on a Chip devices.
334 If you want to compile this as a module (=code which can be
335 inserted into and removed from the running kernel), say M
336 here and read <file:Documentation/kbuild/modules.txt>. The module
337 will be called amba-clcd.
340 tristate "ARM High Definition LCD support"
342 select FB_CFB_FILLRECT
343 select FB_CFB_COPYAREA
344 select FB_CFB_IMAGEBLIT
346 This framebuffer device driver is for the ARM High Definition
347 Colour LCD controller.
349 If you want to compile this as a module (=code which can be
350 inserted into and removed from the running kernel), say M
351 here and read <file:Documentation/kbuild/modules.txt>. The module
352 will be called arm-hdlcd.
355 bool "Acorn VIDC support"
356 depends on (FB = y) && ARM && ARCH_ACORN
357 select FB_CFB_FILLRECT
358 select FB_CFB_COPYAREA
359 select FB_CFB_IMAGEBLIT
361 This is the frame buffer device driver for the Acorn VIDC graphics
362 hardware found in Acorn RISC PCs and other ARM-based machines. If
366 bool "CLPS711X LCD support"
367 depends on (FB = y) && ARM && ARCH_CLPS711X
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
372 Say Y to enable the Framebuffer driver for the CLPS7111 and
376 bool "SA-1100 LCD support"
377 depends on (FB = y) && ARM && ARCH_SA1100
378 select FB_CFB_FILLRECT
379 select FB_CFB_COPYAREA
380 select FB_CFB_IMAGEBLIT
382 This is a framebuffer device for the SA-1100 LCD Controller.
383 See <http://www.linux-fbdev.org/> for information on framebuffer
386 If you plan to use the LCD display with your SA-1100 system, say
390 tristate "Freescale i.MX1/21/25/27 LCD support"
391 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
392 select FB_CFB_FILLRECT
393 select FB_CFB_COPYAREA
394 select FB_CFB_IMAGEBLIT
397 tristate "CyberPro 2000/2010/5000 support"
398 depends on FB && PCI && (BROKEN || !SPARC64)
399 select FB_CFB_FILLRECT
400 select FB_CFB_COPYAREA
401 select FB_CFB_IMAGEBLIT
403 This enables support for the Integraphics CyberPro 20x0 and 5000
404 VGA chips used in the Rebel.com Netwinder and other machines.
405 Say Y if you have a NetWinder or a graphics card containing this
406 device, otherwise say N.
408 config FB_CYBER2000_DDC
409 bool "DDC for CyberPro support"
410 depends on FB_CYBER2000
414 Say Y here if you want DDC support for your CyberPro graphics
415 card. This is only I2C bus support, driver does not use EDID.
417 config FB_CYBER2000_I2C
418 bool "CyberPro 2000/2010/5000 I2C support"
419 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
422 Enable support for the I2C video decoder interface on the
423 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
424 on the Netwinder machines for the SAA7111 video capture.
428 depends on (FB = y) && APOLLO
430 select FB_CFB_FILLRECT
431 select FB_CFB_IMAGEBLIT
435 depends on (FB = y) && Q40
437 select FB_CFB_FILLRECT
438 select FB_CFB_COPYAREA
439 select FB_CFB_IMAGEBLIT
442 tristate "Amiga native chipset support"
443 depends on FB && AMIGA
445 This is the frame buffer device driver for the builtin graphics
446 chipset found in Amigas.
448 To compile this driver as a module, choose M here: the
449 module will be called amifb.
452 bool "Amiga OCS chipset support"
455 This enables support for the original Agnus and Denise video chips,
456 found in the Amiga 1000 and most A500's and A2000's. If you intend
457 to run Linux on any of these systems, say Y; otherwise say N.
460 bool "Amiga ECS chipset support"
463 This enables support for the Enhanced Chip Set, found in later
464 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
465 you intend to run Linux on any of these systems, say Y; otherwise
469 bool "Amiga AGA chipset support"
472 This enables support for the Advanced Graphics Architecture (also
473 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
474 and CD32. If you intend to run Linux on any of these systems, say Y;
478 bool "Amiga FrameMaster II/Rainbow II support"
479 depends on (FB = y) && ZORRO
480 select FB_CFB_FILLRECT
481 select FB_CFB_COPYAREA
482 select FB_CFB_IMAGEBLIT
484 This is the frame buffer device driver for the Amiga FrameMaster
485 card from BSC (exhibited 1992 but not shipped as a CBM product).
488 tristate "Arc Monochrome LCD board support"
490 select FB_SYS_FILLRECT
491 select FB_SYS_COPYAREA
492 select FB_SYS_IMAGEBLIT
495 This enables support for the Arc Monochrome LCD board. The board
496 is based on the KS-108 lcd controller and is typically a matrix
497 of 2*n chips. This driver was tested with a 128x64 panel. This
498 driver supports it for use with x86 SBCs through a 16 bit GPIO
499 interface (8 bit data, 8 bit control). If you anticipate using
500 this driver, say Y or M; otherwise say N. You must specify the
501 GPIO IO address to be used for setting control and data.
504 bool "Atari native chipset support"
505 depends on (FB = y) && ATARI
506 select FB_CFB_FILLRECT
507 select FB_CFB_COPYAREA
508 select FB_CFB_IMAGEBLIT
510 This is the frame buffer device driver for the builtin graphics
511 chipset found in Ataris.
514 bool "Open Firmware frame buffer device support"
515 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
516 select FB_CFB_FILLRECT
517 select FB_CFB_COPYAREA
518 select FB_CFB_IMAGEBLIT
521 Say Y if you want support with Open Firmware for your graphics
525 bool "Apple \"control\" display support"
526 depends on (FB = y) && PPC_PMAC && PPC32
527 select FB_CFB_FILLRECT
528 select FB_CFB_COPYAREA
529 select FB_CFB_IMAGEBLIT
532 This driver supports a frame buffer for the graphics adapter in the
533 Power Macintosh 7300 and others.
536 bool "Apple \"platinum\" display support"
537 depends on (FB = y) && PPC_PMAC && PPC32
538 select FB_CFB_FILLRECT
539 select FB_CFB_COPYAREA
540 select FB_CFB_IMAGEBLIT
543 This driver supports a frame buffer for the "platinum" graphics
544 adapter in some Power Macintoshes.
547 bool "Apple \"valkyrie\" display support"
548 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
549 select FB_CFB_FILLRECT
550 select FB_CFB_COPYAREA
551 select FB_CFB_IMAGEBLIT
554 This driver supports a frame buffer for the "valkyrie" graphics
555 adapter in some Power Macintoshes.
558 bool "Chips 65550 display support"
559 depends on (FB = y) && PPC32 && PCI
560 select FB_CFB_FILLRECT
561 select FB_CFB_COPYAREA
562 select FB_CFB_IMAGEBLIT
564 This is the frame buffer device driver for the Chips & Technologies
565 65550 graphics chip in PowerBooks.
568 bool "Asiliant (Chips) 69000 display support"
569 depends on (FB = y) && PCI
570 select FB_CFB_FILLRECT
571 select FB_CFB_COPYAREA
572 select FB_CFB_IMAGEBLIT
574 This is the frame buffer device driver for the Asiliant 69030 chipset
577 bool "IMS Twin Turbo display support"
578 depends on (FB = y) && PCI
579 select FB_CFB_IMAGEBLIT
580 select FB_MACMODES if PPC
582 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
583 many Macintosh and compatible computers.
586 tristate "VGA 16-color graphics support"
587 depends on FB && (X86 || PPC)
588 select FB_CFB_FILLRECT
589 select FB_CFB_COPYAREA
590 select FB_CFB_IMAGEBLIT
592 select FONT_8x16 if FRAMEBUFFER_CONSOLE
594 This is the frame buffer device driver for VGA 16 color graphic
595 cards. Say Y if you have such a card.
597 To compile this driver as a module, choose M here: the
598 module will be called vga16fb.
600 config FB_BF54X_LQ043
601 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
602 depends on FB && (BF54x) && !BF542
603 select FB_CFB_FILLRECT
604 select FB_CFB_COPYAREA
605 select FB_CFB_IMAGEBLIT
607 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
609 config FB_BFIN_T350MCQB
610 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
611 depends on FB && BLACKFIN
613 select FB_CFB_FILLRECT
614 select FB_CFB_COPYAREA
615 select FB_CFB_IMAGEBLIT
617 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
618 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
619 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
621 config FB_BFIN_LQ035Q1
622 tristate "SHARP LQ035Q1DH02 TFT LCD"
623 depends on FB && BLACKFIN && SPI
624 select FB_CFB_FILLRECT
625 select FB_CFB_COPYAREA
626 select FB_CFB_IMAGEBLIT
629 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
630 the Blackfin Landscape LCD EZ-Extender Card.
631 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
632 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
634 To compile this driver as a module, choose M here: the
635 module will be called bfin-lq035q1-fb.
637 config FB_BF537_LQ035
638 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
639 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
640 select FB_CFB_FILLRECT
641 select FB_CFB_COPYAREA
642 select FB_CFB_IMAGEBLIT
645 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
648 To compile this driver as a module, choose M here: the
649 module will be called bf537-lq035.
652 tristate "Blackfin ADV7393 Video encoder"
653 depends on FB && BLACKFIN
655 select FB_CFB_FILLRECT
656 select FB_CFB_COPYAREA
657 select FB_CFB_IMAGEBLIT
659 This is the framebuffer device for a ADV7393 video encoder
660 attached to a Blackfin on the PPI port.
661 If your Blackfin board has a ADV7393 select Y.
663 To compile this driver as a module, choose M here: the
664 module will be called bfin_adv7393fb.
667 prompt "Video mode support"
668 depends on FB_BFIN_7393
678 bool 'NTSC 640x480 (Experimental)'
681 bool 'PAL 640x480 (Experimental)'
684 bool 'NTSC 720x480 YCbCR input'
687 bool 'PAL 720x576 YCbCR input'
692 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
693 depends on (FB_BFIN_7393)
694 default ADV7393_1XMEM
704 tristate "HP STI frame buffer device support"
705 depends on FB && PARISC
706 select FB_CFB_FILLRECT
707 select FB_CFB_COPYAREA
708 select FB_CFB_IMAGEBLIT
713 STI refers to the HP "Standard Text Interface" which is a set of
714 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
715 Enabling this option will implement the linux framebuffer device
716 using calls to the STI BIOS routines for initialisation.
718 If you enable this option, you will get a planar framebuffer device
719 /dev/fb which will work on the most common HP graphic cards of the
720 NGLE family, including the artist chips (in the 7xx and Bxxx series),
721 HCRX, HCRX24, CRX, CRX24 and VisEG series.
723 It is safe to enable this option, so you should probably say "Y".
726 bool "Generic Macintosh display support"
727 depends on (FB = y) && MAC
728 select FB_CFB_FILLRECT
729 select FB_CFB_COPYAREA
730 select FB_CFB_IMAGEBLIT
735 depends on (FB = y) && DIO
736 select FB_CFB_IMAGEBLIT
740 tristate "TGA/SFB+ framebuffer support"
741 depends on FB && (ALPHA || TC)
742 select FB_CFB_FILLRECT
743 select FB_CFB_COPYAREA
744 select FB_CFB_IMAGEBLIT
747 This is the frame buffer device driver for generic TGA and SFB+
748 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
749 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
750 TURBOchannel cards, also known as PMAGD-A, -B and -C.
752 Due to hardware limitations ZLX-E2 and E3 cards are not supported
753 for DECstation 5000/200 systems. Additionally due to firmware
754 limitations these cards may cause troubles with booting DECstation
755 5000/240 and /260 systems, but are fully supported under Linux if
756 you manage to get it going. ;-)
758 Say Y if you have one of those.
761 tristate "Userspace VESA VGA graphics support"
762 depends on FB && CONNECTOR
763 select FB_CFB_FILLRECT
764 select FB_CFB_COPYAREA
765 select FB_CFB_IMAGEBLIT
766 select FB_MODE_HELPERS
768 This is the frame buffer driver for generic VBE 2.0 compliant
769 graphic cards. It can also take advantage of VBE 3.0 features,
770 such as refresh rate adjustment.
772 This driver generally provides more features than vesafb but
773 requires a userspace helper application called 'v86d'. See
774 <file:Documentation/fb/uvesafb.txt> for more information.
779 bool "VESA VGA graphics support"
780 depends on (FB = y) && X86
781 select FB_CFB_FILLRECT
782 select FB_CFB_COPYAREA
783 select FB_CFB_IMAGEBLIT
784 select FB_BOOT_VESA_SUPPORT
786 This is the frame buffer device driver for generic VESA 2.0
787 compliant graphic cards. The older VESA 1.2 cards are not supported.
788 You will get a boot time penguin logo at no additional cost. Please
789 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
792 bool "EFI-based Framebuffer Support"
793 depends on (FB = y) && X86 && EFI
794 select FB_CFB_FILLRECT
795 select FB_CFB_COPYAREA
796 select FB_CFB_IMAGEBLIT
798 This is the EFI frame buffer device driver. If the firmware on
799 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
800 using the EFI framebuffer as your console.
803 tristate "N411 Apollo/Hecuba devkit support"
804 depends on FB && X86 && MMU
805 select FB_SYS_FILLRECT
806 select FB_SYS_COPYAREA
807 select FB_SYS_IMAGEBLIT
809 select FB_DEFERRED_IO
812 This enables support for the Apollo display controller in its
813 Hecuba form using the n411 devkit.
816 tristate "Hercules mono graphics support"
819 Say Y here if you have a Hercules mono graphics card.
821 To compile this driver as a module, choose M here: the
822 module will be called hgafb.
824 As this card technology is at least 25 years old,
825 most people will answer N here.
828 tristate "SGI Visual Workstation framebuffer support"
829 depends on FB && X86_VISWS
830 select FB_CFB_FILLRECT
831 select FB_CFB_COPYAREA
832 select FB_CFB_IMAGEBLIT
834 SGI Visual Workstation support for framebuffer graphics.
837 bool "SGI Graphics Backend frame buffer support"
838 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for SGI Graphics Backend.
844 This chip is used in SGI O2 and Visual Workstation 320/540.
847 int "Video memory size in MB"
851 This is the amount of memory reserved for the framebuffer,
852 which can be any value between 1MB and 8MB.
855 bool "SBUS and UPA framebuffers"
856 depends on (FB = y) && SPARC
858 Say Y if you want support for SBUS or UPA based frame buffer device.
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 BWtwo frame buffer.
870 bool "CGthree support"
871 depends on (FB = y) && (SPARC && FB_SBUS)
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 CGthree frame buffer.
879 bool "CGsix (GX,TurboGX) support"
880 depends on (FB = y) && (SPARC && FB_SBUS)
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
884 This is the frame buffer device driver for the CGsix (GX, TurboGX)
888 bool "Creator/Creator3D/Elite3D support"
889 depends on FB_SBUS && SPARC64
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This is the frame buffer device driver for the Creator, Creator3D,
894 and Elite3D graphics boards.
897 bool "TCX (SS4/SS5 only) support"
899 select FB_CFB_FILLRECT
900 select FB_CFB_COPYAREA
901 select FB_CFB_IMAGEBLIT
903 This is the frame buffer device driver for the TCX 24/8bit frame
907 bool "CGfourteen (SX) support"
909 select FB_CFB_FILLRECT
910 select FB_CFB_COPYAREA
911 select FB_CFB_IMAGEBLIT
913 This is the frame buffer device driver for the CGfourteen frame
914 buffer on Desktop SPARCsystems with the SX graphics option.
917 bool "P9100 (Sparcbook 3 only) support"
919 select FB_CFB_FILLRECT
920 select FB_CFB_COPYAREA
921 select FB_CFB_IMAGEBLIT
923 This is the frame buffer device driver for the P9100 card
924 supported on Sparcbook 3 machines.
927 bool "Leo (ZX) support"
929 select FB_CFB_FILLRECT
930 select FB_CFB_COPYAREA
931 select FB_CFB_IMAGEBLIT
933 This is the frame buffer device driver for the SBUS-based Sun ZX
934 (leo) frame buffer cards.
937 bool "IGA 168x display support"
938 depends on (FB = y) && SPARC32
939 select FB_CFB_FILLRECT
940 select FB_CFB_COPYAREA
941 select FB_CFB_IMAGEBLIT
943 This is the framebuffer device for the INTERGRAPHICS 1680 and
944 successor frame buffer cards.
947 bool "Sun XVR-500 3DLABS Wildcat support"
948 depends on (FB = y) && PCI && SPARC64
949 select FB_CFB_FILLRECT
950 select FB_CFB_COPYAREA
951 select FB_CFB_IMAGEBLIT
953 This is the framebuffer device for the Sun XVR-500 and similar
954 graphics cards based upon the 3DLABS Wildcat chipset. The driver
955 only works on sparc64 systems where the system firmware has
956 mostly initialized the card already. It is treated as a
957 completely dumb framebuffer device.
960 bool "Sun XVR-2500 3DLABS Wildcat support"
961 depends on (FB = y) && PCI && SPARC64
962 select FB_CFB_FILLRECT
963 select FB_CFB_COPYAREA
964 select FB_CFB_IMAGEBLIT
966 This is the framebuffer device for the Sun XVR-2500 and similar
967 graphics cards based upon the 3DLABS Wildcat chipset. The driver
968 only works on sparc64 systems where the system firmware has
969 mostly initialized the card already. It is treated as a
970 completely dumb framebuffer device.
973 bool "Sun XVR-1000 support"
974 depends on (FB = y) && SPARC64
975 select FB_CFB_FILLRECT
976 select FB_CFB_COPYAREA
977 select FB_CFB_IMAGEBLIT
979 This is the framebuffer device for the Sun XVR-1000 and similar
980 graphics cards. The driver only works on sparc64 systems where
981 the system firmware has mostly initialized the card already. It
982 is treated as a completely dumb framebuffer device.
985 tristate "NEC PowerVR 2 display support"
986 depends on FB && SH_DREAMCAST
987 select FB_CFB_FILLRECT
988 select FB_CFB_COPYAREA
989 select FB_CFB_IMAGEBLIT
991 Say Y here if you have a PowerVR 2 card in your box. If you plan to
992 run linux on your Dreamcast, you will have to say Y here.
993 This driver may or may not work on other PowerVR 2 cards, but is
994 totally untested. Use at your own risk. If unsure, say N.
996 To compile this driver as a module, choose M here: the
997 module will be called pvr2fb.
999 You can pass several parameters to the driver at boot time or at
1000 module load time. The parameters look like "video=pvr2:XXX", where
1001 the meaning of XXX can be found at the end of the main source file
1002 (<file:drivers/video/pvr2fb.c>). Please see the file
1003 <file:Documentation/fb/pvr2fb.txt>.
1006 tristate "Epson S1D13XXX framebuffer support"
1008 select FB_CFB_FILLRECT
1009 select FB_CFB_COPYAREA
1010 select FB_CFB_IMAGEBLIT
1012 Support for S1D13XXX framebuffer device family (currently only
1013 working with S1D13806). Product specs at
1014 <http://vdc.epson.com/>
1017 tristate "AT91/AT32 LCD Controller support"
1018 depends on FB && HAVE_FB_ATMEL
1019 select FB_CFB_FILLRECT
1020 select FB_CFB_COPYAREA
1021 select FB_CFB_IMAGEBLIT
1023 This enables support for the AT91/AT32 LCD Controller.
1026 bool "Frame Buffer in internal SRAM"
1027 depends on FB_ATMEL && ARCH_AT91SAM9261
1029 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1030 to let frame buffer in external SDRAM.
1033 bool "Use a STN display with AT91/AT32 LCD Controller"
1034 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1037 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1038 Controller. Say N if you want to connect a TFT.
1043 tristate "nVidia Framebuffer Support"
1044 depends on FB && PCI
1045 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1046 select FB_MODE_HELPERS
1047 select FB_CFB_FILLRECT
1048 select FB_CFB_COPYAREA
1049 select FB_CFB_IMAGEBLIT
1053 This driver supports graphics boards with the nVidia chips, TNT
1054 and newer. For very old chipsets, such as the RIVA128, then use
1056 Say Y if you have such a graphics board.
1058 To compile this driver as a module, choose M here: the
1059 module will be called nvidiafb.
1061 config FB_NVIDIA_I2C
1062 bool "Enable DDC Support"
1063 depends on FB_NVIDIA
1066 This enables I2C support for nVidia Chipsets. This is used
1067 only for getting EDID information from the attached display
1068 allowing for robust video mode handling and switching.
1070 Because fbdev-2.6 requires that drivers must be able to
1071 independently validate video mode parameters, you should say Y
1074 config FB_NVIDIA_DEBUG
1075 bool "Lots of debug output"
1076 depends on FB_NVIDIA
1079 Say Y here if you want the nVidia driver to output all sorts
1080 of debugging information to provide to the maintainer when
1081 something goes wrong.
1083 config FB_NVIDIA_BACKLIGHT
1084 bool "Support for backlight control"
1085 depends on FB_NVIDIA
1088 Say Y here if you want to control the backlight of your display.
1091 tristate "nVidia Riva support"
1092 depends on FB && PCI
1093 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1094 select FB_MODE_HELPERS
1095 select FB_CFB_FILLRECT
1096 select FB_CFB_COPYAREA
1097 select FB_CFB_IMAGEBLIT
1101 This driver supports graphics boards with the nVidia Riva/Geforce
1103 Say Y if you have such a graphics board.
1105 To compile this driver as a module, choose M here: the
1106 module will be called rivafb.
1109 bool "Enable DDC Support"
1113 This enables I2C support for nVidia Chipsets. This is used
1114 only for getting EDID information from the attached display
1115 allowing for robust video mode handling and switching.
1117 Because fbdev-2.6 requires that drivers must be able to
1118 independently validate video mode parameters, you should say Y
1121 config FB_RIVA_DEBUG
1122 bool "Lots of debug output"
1126 Say Y here if you want the Riva driver to output all sorts
1127 of debugging information to provide to the maintainer when
1128 something goes wrong.
1130 config FB_RIVA_BACKLIGHT
1131 bool "Support for backlight control"
1135 Say Y here if you want to control the backlight of your display.
1138 tristate "Intel740 support"
1139 depends on FB && PCI
1140 select FB_MODE_HELPERS
1141 select FB_CFB_FILLRECT
1142 select FB_CFB_COPYAREA
1143 select FB_CFB_IMAGEBLIT
1147 This driver supports graphics cards based on Intel740 chip.
1150 tristate "Intel 810/815 support"
1151 depends on FB && PCI && X86_32 && AGP_INTEL
1152 select FB_MODE_HELPERS
1153 select FB_CFB_FILLRECT
1154 select FB_CFB_COPYAREA
1155 select FB_CFB_IMAGEBLIT
1158 This driver supports the on-board graphics built in to the Intel 810
1159 and 815 chipsets. Say Y if you have and plan to use such a board.
1161 To compile this driver as a module, choose M here: the
1162 module will be called i810fb.
1164 For more information, please read
1165 <file:Documentation/fb/intel810.txt>
1168 bool "use VESA Generalized Timing Formula"
1171 If you say Y, then the VESA standard, Generalized Timing Formula
1172 or GTF, will be used to calculate the required video timing values
1173 per video mode. Since the GTF allows nondiscrete timings
1174 (nondiscrete being a range of values as opposed to discrete being a
1175 set of values), you'll be able to use any combination of horizontal
1176 and vertical resolutions, and vertical refresh rates without having
1177 to specify your own timing parameters. This is especially useful
1178 to maximize the performance of an aging display, or if you just
1179 have a display with nonstandard dimensions. A VESA compliant
1180 monitor is recommended, but can still work with non-compliant ones.
1181 If you need or want this, then select this option. The timings may
1182 not be compliant with Intel's recommended values. Use at your own
1185 If you say N, the driver will revert to discrete video timings
1186 using a set recommended by Intel in their documentation.
1191 bool "Enable DDC Support"
1192 depends on FB_I810 && FB_I810_GTF
1197 tristate "Intel LE80578 (Vermilion) support"
1198 depends on FB && PCI && X86
1199 select FB_MODE_HELPERS
1200 select FB_CFB_FILLRECT
1201 select FB_CFB_COPYAREA
1202 select FB_CFB_IMAGEBLIT
1204 This driver supports the LE80578 (Vermilion Range) chipset
1206 config FB_CARILLO_RANCH
1207 tristate "Intel Carillo Ranch support"
1208 depends on FB_LE80578 && FB && PCI && X86
1210 This driver supports the LE80578 (Carillo Ranch) board
1213 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1214 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1215 select FB_MODE_HELPERS
1216 select FB_CFB_FILLRECT
1217 select FB_CFB_COPYAREA
1218 select FB_CFB_IMAGEBLIT
1219 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1220 depends on !DRM_I915
1222 This driver supports the on-board graphics built in to the Intel
1223 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1224 Say Y if you have and plan to use such a board.
1226 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1228 To compile this driver as a module, choose M here: the
1229 module will be called intelfb.
1231 For more information, please read <file:Documentation/fb/intelfb.txt>
1233 config FB_INTEL_DEBUG
1234 bool "Intel driver Debug Messages"
1237 Say Y here if you want the Intel driver to output all sorts
1238 of debugging information to provide to the maintainer when
1239 something goes wrong.
1242 bool "DDC/I2C for Intel framebuffer support"
1247 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1250 tristate "Matrox acceleration"
1251 depends on FB && PCI
1252 select FB_CFB_FILLRECT
1253 select FB_CFB_COPYAREA
1254 select FB_CFB_IMAGEBLIT
1255 select FB_TILEBLITTING
1256 select FB_MACMODES if PPC_PMAC
1258 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1259 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1260 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1261 Matrox G400, G450 or G550 card in your box.
1263 To compile this driver as a module, choose M here: the
1264 module will be called matroxfb.
1266 You can pass several parameters to the driver at boot time or at
1267 module load time. The parameters look like "video=matroxfb:XXX", and
1268 are described in <file:Documentation/fb/matroxfb.txt>.
1270 config FB_MATROX_MILLENIUM
1271 bool "Millennium I/II support"
1272 depends on FB_MATROX
1274 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1275 video card. If you select "Advanced lowlevel driver options" below,
1276 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1277 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1278 also use font widths different from 8.
1280 config FB_MATROX_MYSTIQUE
1281 bool "Mystique support"
1282 depends on FB_MATROX
1284 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1285 video card. If you select "Advanced lowlevel driver options" below,
1286 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1287 packed pixel and 32 bpp packed pixel. You can also use font widths
1291 bool "G100/G200/G400/G450/G550 support"
1292 depends on FB_MATROX
1294 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1295 video card. If you select "Advanced lowlevel driver options", you
1296 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1297 pixel and 32 bpp packed pixel. You can also use font widths
1300 If you need support for G400 secondary head, you must say Y to
1301 "Matrox I2C support" and "G400 second head support" right below.
1302 G450/G550 secondary head and digital output are supported without
1305 The driver starts in monitor mode. You must use the matroxset tool
1306 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1307 swap primary and secondary head outputs, or to change output mode.
1308 Secondary head driver always start in 640x480 resolution and you
1309 must use fbset to change it.
1311 Do not forget that second head supports only 16 and 32 bpp
1312 packed pixels, so it is a good idea to compile them into the kernel
1313 too. You can use only some font widths, as the driver uses generic
1314 painting procedures (the secondary head does not use acceleration
1317 G450/G550 hardware can display TV picture only from secondary CRTC,
1318 and it performs no scaling, so picture must have 525 or 625 lines.
1320 config FB_MATROX_I2C
1321 tristate "Matrox I2C support"
1322 depends on FB_MATROX
1325 This drivers creates I2C buses which are needed for accessing the
1326 DDC (I2C) bus present on all Matroxes, an I2C bus which
1327 interconnects Matrox optional devices, like MGA-TVO on G200 and
1328 G400, and the secondary head DDC bus, present on G400 only.
1330 You can say Y or M here if you want to experiment with monitor
1331 detection code. You must say Y or M here if you want to use either
1332 second head of G400 or MGA-TVO on G200 or G400.
1334 If you compile it as module, it will create a module named
1337 config FB_MATROX_MAVEN
1338 tristate "G400 second head support"
1339 depends on FB_MATROX_G && FB_MATROX_I2C
1341 WARNING !!! This support does not work with G450 !!!
1343 Say Y or M here if you want to use a secondary head (meaning two
1344 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1345 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1346 secondary head output is blanked while you are in X. With XFree
1347 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1348 the fbdev driver on first head and the fbdev driver on second head.
1350 If you compile it as module, two modules are created,
1351 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1352 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1353 also load i2c-matroxfb to get it to run.
1355 The driver starts in monitor mode and you must use the matroxset
1357 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1358 PAL or NTSC or to swap primary and secondary head outputs.
1359 Secondary head driver also always start in 640x480 resolution, you
1360 must use fbset to change it.
1362 Also do not forget that second head supports only 16 and 32 bpp
1363 packed pixels, so it is a good idea to compile them into the kernel
1364 too. You can use only some font widths, as the driver uses generic
1365 painting procedures (the secondary head does not use acceleration
1369 tristate "ATI Radeon display support"
1370 depends on FB && PCI
1371 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1372 select FB_MODE_HELPERS
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1376 select FB_MACMODES if PPC_OF
1378 Choose this option if you want to use an ATI Radeon graphics card as
1379 a framebuffer device. There are both PCI and AGP versions. You
1380 don't need to choose this to run the Radeon in plain VGA mode.
1382 There is a product page at
1383 http://products.amd.com/en-us/GraphicCardResult.aspx
1385 config FB_RADEON_I2C
1386 bool "DDC/I2C for ATI Radeon support"
1387 depends on FB_RADEON
1391 Say Y here if you want DDC/I2C support for your Radeon board.
1393 config FB_RADEON_BACKLIGHT
1394 bool "Support for backlight control"
1395 depends on FB_RADEON
1398 Say Y here if you want to control the backlight of your display.
1400 config FB_RADEON_DEBUG
1401 bool "Lots of debug output from Radeon driver"
1402 depends on FB_RADEON
1405 Say Y here if you want the Radeon driver to output all sorts
1406 of debugging information to provide to the maintainer when
1407 something goes wrong.
1410 tristate "ATI Rage128 display support"
1411 depends on FB && PCI
1412 select FB_CFB_FILLRECT
1413 select FB_CFB_COPYAREA
1414 select FB_CFB_IMAGEBLIT
1415 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1416 select FB_MACMODES if PPC_PMAC
1418 This driver supports graphics boards with the ATI Rage128 chips.
1419 Say Y if you have such a graphics board and read
1420 <file:Documentation/fb/aty128fb.txt>.
1422 To compile this driver as a module, choose M here: the
1423 module will be called aty128fb.
1425 config FB_ATY128_BACKLIGHT
1426 bool "Support for backlight control"
1427 depends on FB_ATY128
1430 Say Y here if you want to control the backlight of your display.
1433 tristate "ATI Mach64 display support" if PCI || ATARI
1434 depends on FB && !SPARC32
1435 select FB_CFB_FILLRECT
1436 select FB_CFB_COPYAREA
1437 select FB_CFB_IMAGEBLIT
1438 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1439 select FB_MACMODES if PPC
1441 This driver supports graphics boards with the ATI Mach64 chips.
1442 Say Y if you have such a graphics board.
1444 To compile this driver as a module, choose M here: the
1445 module will be called atyfb.
1448 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1449 depends on PCI && FB_ATY
1450 default y if SPARC64 && PCI
1452 Say Y here to support use of ATI's 64-bit Rage boards (or other
1453 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1454 framebuffer device. The ATI product support page for these boards
1455 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1457 config FB_ATY_GENERIC_LCD
1458 bool "Mach64 generic LCD support"
1459 depends on FB_ATY_CT
1461 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1462 Rage XC, or Rage XL chipset.
1465 bool "Mach64 GX support" if PCI
1469 Say Y here to support use of the ATI Mach64 Graphics Expression
1470 board (or other boards based on the Mach64 GX chipset) as a
1471 framebuffer device. The ATI product support page for these boards
1473 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1475 config FB_ATY_BACKLIGHT
1476 bool "Support for backlight control"
1480 Say Y here if you want to control the backlight of your display.
1483 tristate "S3 Trio/Virge support"
1484 depends on FB && PCI
1485 select FB_CFB_FILLRECT
1486 select FB_CFB_COPYAREA
1487 select FB_CFB_IMAGEBLIT
1488 select FB_TILEBLITTING
1491 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1493 Driver for graphics boards with S3 Trio / S3 Virge chip.
1496 bool "DDC for S3 support"
1501 Say Y here if you want DDC support for your S3 graphics card.
1504 tristate "S3 Savage support"
1505 depends on FB && PCI
1506 select FB_MODE_HELPERS
1507 select FB_CFB_FILLRECT
1508 select FB_CFB_COPYAREA
1509 select FB_CFB_IMAGEBLIT
1512 This driver supports notebooks and computers with S3 Savage PCI/AGP
1515 Say Y if you have such a graphics card.
1517 To compile this driver as a module, choose M here; the module
1518 will be called savagefb.
1520 config FB_SAVAGE_I2C
1521 bool "Enable DDC2 Support"
1522 depends on FB_SAVAGE
1525 This enables I2C support for S3 Savage Chipsets. This is used
1526 only for getting EDID information from the attached display
1527 allowing for robust video mode handling and switching.
1529 Because fbdev-2.6 requires that drivers must be able to
1530 independently validate video mode parameters, you should say Y
1533 config FB_SAVAGE_ACCEL
1534 bool "Enable Console Acceleration"
1535 depends on FB_SAVAGE
1538 This option will compile in console acceleration support. If
1539 the resulting framebuffer console has bothersome glitches, then
1543 tristate "SiS/XGI display support"
1544 depends on FB && PCI
1545 select FB_CFB_FILLRECT
1546 select FB_CFB_COPYAREA
1547 select FB_CFB_IMAGEBLIT
1548 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1550 This is the frame buffer device driver for the SiS 300, 315, 330
1551 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1552 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1554 To compile this driver as a module, choose M here; the module
1555 will be called sisfb.
1558 bool "SiS 300 series support"
1561 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1564 bool "SiS 315/330/340 series and XGI support"
1567 Say Y here to support use of the SiS 315, 330 and 340 series
1568 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1569 as XGI V3XT, V5, V8 and Z7.
1572 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1573 depends on FB && PCI && X86
1574 select FB_CFB_FILLRECT
1575 select FB_CFB_COPYAREA
1576 select FB_CFB_IMAGEBLIT
1581 This is the frame buffer device driver for Graphics chips of VIA
1582 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1583 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1585 Say Y if you have a VIA UniChrome graphics board.
1587 To compile this driver as a module, choose M here: the
1588 module will be called viafb.
1592 config FB_VIA_DIRECT_PROCFS
1593 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1597 Allow direct hardware access to some output registers via procfs.
1598 This is dangerous but may provide the only chance to get the
1599 correct output device configuration.
1600 Its use is strongly discouraged.
1602 config FB_VIA_X_COMPATIBILITY
1603 bool "X server compatibility"
1607 This option reduces the functionality (power saving, ...) of the
1608 framebuffer to avoid negative impact on the OpenChrome X server.
1609 If you use any X server other than fbdev you should enable this
1610 otherwise it should be safe to disable it and allow using all
1616 tristate "NeoMagic display support"
1617 depends on FB && PCI
1618 select FB_MODE_HELPERS
1619 select FB_CFB_FILLRECT
1620 select FB_CFB_COPYAREA
1621 select FB_CFB_IMAGEBLIT
1624 This driver supports notebooks with NeoMagic PCI chips.
1625 Say Y if you have such a graphics card.
1627 To compile this driver as a module, choose M here: the
1628 module will be called neofb.
1631 tristate "IMG Kyro support"
1632 depends on FB && PCI
1633 select FB_CFB_FILLRECT
1634 select FB_CFB_COPYAREA
1635 select FB_CFB_IMAGEBLIT
1637 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1640 To compile this driver as a module, choose M here: the
1641 module will be called kyrofb.
1644 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1645 depends on FB && PCI
1646 select FB_CFB_IMAGEBLIT
1647 select FB_CFB_FILLRECT
1648 select FB_CFB_COPYAREA
1649 select FB_MODE_HELPERS
1651 This driver supports graphics boards with the 3Dfx Banshee,
1652 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1653 such a graphics board.
1655 To compile this driver as a module, choose M here: the
1656 module will be called tdfxfb.
1658 config FB_3DFX_ACCEL
1659 bool "3Dfx Acceleration functions"
1662 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1663 device driver with acceleration functions.
1666 bool "Enable DDC/I2C support"
1671 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1674 tristate "3Dfx Voodoo Graphics (sst1) support"
1675 depends on FB && PCI
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1680 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1681 Voodoo2 (cvg) based graphics card.
1683 To compile this driver as a module, choose M here: the
1684 module will be called sstfb.
1686 WARNING: Do not use any application that uses the 3D engine
1687 (namely glide) while using this driver.
1688 Please read the <file:Documentation/fb/sstfb.txt> for supported
1689 options and other important info support.
1692 tristate "VIA VT8623 support"
1693 depends on FB && PCI
1694 select FB_CFB_FILLRECT
1695 select FB_CFB_COPYAREA
1696 select FB_CFB_IMAGEBLIT
1697 select FB_TILEBLITTING
1700 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1702 Driver for CastleRock integrated graphics core in the
1703 VIA VT8623 [Apollo CLE266] chipset.
1706 tristate "Trident/CyberXXX/CyberBlade support"
1707 depends on FB && PCI
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1713 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1715 There are also integrated versions of these chips called CyberXXXX,
1716 CyberImage or CyberBlade. These chips are mostly found in laptops
1717 but also on some motherboards including early VIA EPIA motherboards.
1718 For more information, read <file:Documentation/fb/tridentfb.txt>
1720 Say Y if you have such a graphics board.
1722 To compile this driver as a module, choose M here: the
1723 module will be called tridentfb.
1726 tristate "ARK 2000PV support"
1727 depends on FB && PCI
1728 select FB_CFB_FILLRECT
1729 select FB_CFB_COPYAREA
1730 select FB_CFB_IMAGEBLIT
1731 select FB_TILEBLITTING
1734 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1736 Driver for PCI graphics boards with ARK 2000PV chip
1737 and ICS 5342 RAMDAC.
1740 tristate "Permedia3 support"
1741 depends on FB && PCI
1742 select FB_CFB_FILLRECT
1743 select FB_CFB_COPYAREA
1744 select FB_CFB_IMAGEBLIT
1746 This is the frame buffer device driver for the 3DLabs Permedia3
1747 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1748 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1749 and maybe other boards.
1752 tristate "Fujitsu carmine frame buffer support"
1753 depends on FB && PCI
1754 select FB_CFB_FILLRECT
1755 select FB_CFB_COPYAREA
1756 select FB_CFB_IMAGEBLIT
1758 This is the frame buffer device driver for the Fujitsu Carmine chip.
1759 The driver provides two independent frame buffer devices.
1762 depends on FB_CARMINE
1763 prompt "DRAM timing"
1764 default FB_CARMINE_DRAM_EVAL
1766 config FB_CARMINE_DRAM_EVAL
1767 bool "Eval board timings"
1769 Use timings which work on the eval card.
1771 config CARMINE_DRAM_CUSTOM
1772 bool "Custom board timings"
1774 Use custom board timings.
1778 bool "Au1100 LCD Driver"
1779 depends on (FB = y) && MIPS_ALCHEMY
1780 select FB_CFB_FILLRECT
1781 select FB_CFB_COPYAREA
1782 select FB_CFB_IMAGEBLIT
1784 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1785 various panels and CRTs by passing in kernel cmd line option
1786 au1100fb:panel=<name>.
1789 bool "Au1200/Au1300 LCD Driver"
1790 depends on (FB = y) && MIPS_ALCHEMY
1791 select FB_SYS_FILLRECT
1792 select FB_SYS_COPYAREA
1793 select FB_SYS_IMAGEBLIT
1796 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1797 It can drive various panels and CRTs by passing in kernel cmd line
1798 option au1200fb:panel=<name>.
1801 bool "VIA VT8500 framebuffer support"
1802 depends on (FB = y) && ARM && ARCH_VT8500
1803 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1804 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1805 select FB_SYS_IMAGEBLIT
1806 select FB_MODE_HELPERS
1807 select VIDEOMODE_HELPERS
1809 This is the framebuffer driver for VIA VT8500 integrated LCD
1813 bool "Wondermedia WM8xxx-series frame buffer support"
1814 depends on (FB = y) && ARM && ARCH_VT8500
1815 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1816 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1817 select FB_SYS_IMAGEBLIT
1818 select FB_MODE_HELPERS
1819 select VIDEOMODE_HELPERS
1821 This is the framebuffer driver for WonderMedia WM8xxx-series
1822 integrated LCD controller. This driver covers the WM8505, WM8650
1825 config FB_WMT_GE_ROPS
1826 bool "VT8500/WM8xxx accelerated raster ops support"
1827 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1830 This adds support for accelerated raster operations on the
1831 VIA VT8500 and Wondermedia 85xx series SoCs.
1833 source "drivers/video/geode/Kconfig"
1836 tristate "HD64461 Frame Buffer support"
1837 depends on FB && HD64461
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 This is the frame buffer device driver for the Hitachi HD64461 LCD
1846 bool "PMAG-AA TURBOchannel framebuffer support"
1847 depends on (FB = y) && TC
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1853 used mainly in the MIPS-based DECstation series.
1856 tristate "PMAG-BA TURBOchannel framebuffer support"
1858 select FB_CFB_FILLRECT
1859 select FB_CFB_COPYAREA
1860 select FB_CFB_IMAGEBLIT
1862 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1863 used mainly in the MIPS-based DECstation series.
1866 tristate "PMAGB-B TURBOchannel framebuffer support"
1868 select FB_CFB_FILLRECT
1869 select FB_CFB_COPYAREA
1870 select FB_CFB_IMAGEBLIT
1872 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1873 in the MIPS-based DECstation series. The card is currently only
1874 supported in 1280x1024x8 mode.
1877 bool "Maxine (Personal DECstation) onboard framebuffer support"
1878 depends on (FB = y) && MACH_DECSTATION
1879 select FB_CFB_FILLRECT
1880 select FB_CFB_COPYAREA
1881 select FB_CFB_IMAGEBLIT
1883 Support for the onboard framebuffer (1024x768x8) in the Personal
1884 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1888 bool "G364 frame buffer support"
1889 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1890 select FB_CFB_FILLRECT
1891 select FB_CFB_COPYAREA
1892 select FB_CFB_IMAGEBLIT
1894 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1895 Olivetti M700-10 systems.
1898 bool "Motorola 68328 native frame buffer support"
1899 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1900 select FB_CFB_FILLRECT
1901 select FB_CFB_COPYAREA
1902 select FB_CFB_IMAGEBLIT
1904 Say Y here if you want to support the built-in frame buffer of
1905 the Motorola 68328 CPU family.
1908 tristate "PXA168/910 LCD framebuffer support"
1909 depends on FB && (CPU_PXA168 || CPU_PXA910)
1910 select FB_CFB_FILLRECT
1911 select FB_CFB_COPYAREA
1912 select FB_CFB_IMAGEBLIT
1914 Frame buffer driver for the built-in LCD controller in the Marvell
1918 tristate "PXA LCD framebuffer support"
1919 depends on FB && ARCH_PXA
1920 select FB_CFB_FILLRECT
1921 select FB_CFB_COPYAREA
1922 select FB_CFB_IMAGEBLIT
1924 Frame buffer driver for the built-in LCD controller in the Intel
1927 This driver is also available as a module ( = code which can be
1928 inserted and removed from the running kernel whenever you want). The
1929 module will be called pxafb. If you want to compile it as a module,
1930 say M here and read <file:Documentation/kbuild/modules.txt>.
1934 config FB_PXA_OVERLAY
1935 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1937 depends on FB_PXA && (PXA27x || PXA3xx)
1939 config FB_PXA_SMARTPANEL
1940 bool "PXA Smartpanel LCD support"
1944 config FB_PXA_PARAMETERS
1945 bool "PXA LCD command line parameters"
1949 Enable the use of kernel command line or module parameters
1950 to configure the physical properties of the LCD panel when
1951 using the PXA LCD driver.
1953 This option allows you to override the panel parameters
1954 supplied by the platform in order to support multiple
1955 different models of flatpanel. If you will only be using a
1956 single model of flatpanel then you can safely leave this
1959 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1962 tristate "PXA3xx 2D graphics accelerator driver"
1965 Kernelspace driver for the 2D graphics controller unit (GCU)
1966 found on PXA3xx processors. There is a counterpart driver in the
1967 DirectFB suite, see http://www.directfb.org/
1969 If you compile this as a module, it will be called pxa3xx_gcu.
1972 tristate "2700G LCD framebuffer support"
1973 depends on FB && ARCH_PXA
1974 select FB_CFB_FILLRECT
1975 select FB_CFB_COPYAREA
1976 select FB_CFB_IMAGEBLIT
1978 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1982 bool "Enable debugging info via debugfs"
1983 depends on FB_MBX && DEBUG_FS
1986 Enable this if you want debugging information using the debug
1987 filesystem (debugfs)
1992 tristate "Freescale DIU framebuffer support"
1993 depends on FB && FSL_SOC
1994 select FB_MODE_HELPERS
1995 select FB_CFB_FILLRECT
1996 select FB_CFB_COPYAREA
1997 select FB_CFB_IMAGEBLIT
1998 select PPC_LIB_RHEAP
2000 Framebuffer driver for the Freescale SoC DIU
2003 tristate "W100 frame buffer support"
2004 depends on FB && ARCH_PXA
2005 select FB_CFB_FILLRECT
2006 select FB_CFB_COPYAREA
2007 select FB_CFB_IMAGEBLIT
2009 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2010 It can also drive the w3220 chip found on iPAQ hx4700.
2012 This driver is also available as a module ( = code which can be
2013 inserted and removed from the running kernel whenever you want). The
2014 module will be called w100fb. If you want to compile it as a module,
2015 say M here and read <file:Documentation/kbuild/modules.txt>.
2019 config FB_SH_MOBILE_LCDC
2020 tristate "SuperH Mobile LCDC framebuffer support"
2021 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2022 select FB_SYS_FILLRECT
2023 select FB_SYS_COPYAREA
2024 select FB_SYS_IMAGEBLIT
2026 select FB_DEFERRED_IO
2028 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2030 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2032 config FB_SH_MOBILE_HDMI
2033 tristate "SuperH Mobile HDMI controller support"
2034 depends on FB_SH_MOBILE_LCDC
2035 select FB_MODE_HELPERS
2040 Driver for the on-chip SH-Mobile HDMI controller.
2043 tristate "Toshiba Mobile IO FrameBuffer support"
2044 depends on FB && MFD_CORE
2045 select FB_CFB_FILLRECT
2046 select FB_CFB_COPYAREA
2047 select FB_CFB_IMAGEBLIT
2049 Frame buffer driver for the Toshiba Mobile IO integrated as found
2050 on the Sharp SL-6000 series
2052 This driver is also available as a module ( = code which can be
2053 inserted and removed from the running kernel whenever you want). The
2054 module will be called tmiofb. If you want to compile it as a module,
2055 say M here and read <file:Documentation/kbuild/modules.txt>.
2059 config FB_TMIO_ACCELL
2060 bool "tmiofb acceleration"
2065 tristate "Samsung S3C framebuffer support"
2066 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2067 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2068 select FB_CFB_FILLRECT
2069 select FB_CFB_COPYAREA
2070 select FB_CFB_IMAGEBLIT
2072 Frame buffer driver for the built-in FB controller in the Samsung
2073 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2074 and the S3C64XX series such as the S3C6400 and S3C6410.
2076 These chips all have the same basic framebuffer design with the
2077 actual capabilities depending on the chip. For instance the S3C6400
2078 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2079 currently only have two.
2081 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2083 config FB_S3C_DEBUG_REGWRITE
2084 bool "Debug register writes"
2087 Show all register writes via pr_debug()
2090 tristate "S3C2410 LCD framebuffer support"
2091 depends on FB && ARCH_S3C24XX
2092 select FB_CFB_FILLRECT
2093 select FB_CFB_COPYAREA
2094 select FB_CFB_IMAGEBLIT
2096 Frame buffer driver for the built-in LCD controller in the Samsung
2099 This driver is also available as a module ( = code which can be
2100 inserted and removed from the running kernel whenever you want). The
2101 module will be called s3c2410fb. If you want to compile it as a module,
2102 say M here and read <file:Documentation/kbuild/modules.txt>.
2105 config FB_S3C2410_DEBUG
2106 bool "S3C2410 lcd debug messages"
2107 depends on FB_S3C2410
2109 Turn on debugging messages. Note that you can set/unset at run time
2113 bool "NUC900 LCD framebuffer support"
2114 depends on FB && ARCH_W90X900
2115 select FB_CFB_FILLRECT
2116 select FB_CFB_COPYAREA
2117 select FB_CFB_IMAGEBLIT
2119 Frame buffer driver for the built-in LCD controller in the Nuvoton
2122 config GPM1040A0_320X240
2123 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2124 depends on FB_NUC900
2126 config FB_NUC900_DEBUG
2127 bool "NUC900 lcd debug messages"
2128 depends on FB_NUC900
2130 Turn on debugging messages. Note that you can set/unset at run time
2134 tristate "Silicon Motion SM501 framebuffer support"
2135 depends on FB && MFD_SM501
2136 select FB_CFB_FILLRECT
2137 select FB_CFB_COPYAREA
2138 select FB_CFB_IMAGEBLIT
2140 Frame buffer driver for the CRT and LCD controllers in the Silicon
2143 This driver is also available as a module ( = code which can be
2144 inserted and removed from the running kernel whenever you want). The
2145 module will be called sm501fb. If you want to compile it as a module,
2146 say M here and read <file:Documentation/kbuild/modules.txt>.
2151 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2152 depends on FB && USB
2153 select FB_MODE_HELPERS
2154 select FB_SYS_FILLRECT
2155 select FB_SYS_COPYAREA
2156 select FB_SYS_IMAGEBLIT
2158 select FB_DEFERRED_IO
2160 This is a kernel framebuffer driver for SMSC UFX USB devices.
2161 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2162 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2164 To compile as a module, choose M here: the module name is smscufx.
2167 tristate "Displaylink USB Framebuffer support"
2168 depends on FB && USB
2169 select FB_MODE_HELPERS
2170 select FB_SYS_FILLRECT
2171 select FB_SYS_COPYAREA
2172 select FB_SYS_IMAGEBLIT
2174 select FB_DEFERRED_IO
2176 This is a kernel framebuffer driver for DisplayLink USB devices.
2177 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2178 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2179 To compile as a module, choose M here: the module name is udlfb.
2181 config FB_IBM_GXT4500
2182 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2183 depends on FB && PPC
2184 select FB_CFB_FILLRECT
2185 select FB_CFB_COPYAREA
2186 select FB_CFB_IMAGEBLIT
2188 Say Y here to enable support for the IBM GXT4000P/6000P and
2189 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2190 found on some IBM System P (pSeries) machines. This driver
2191 doesn't use Geometry Engine GT1000.
2194 tristate "PS3 GPU framebuffer driver"
2195 depends on FB && PS3_PS3AV
2196 select FB_SYS_FILLRECT
2197 select FB_SYS_COPYAREA
2198 select FB_SYS_IMAGEBLIT
2200 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2202 Include support for the virtual frame buffer in the PS3 platform.
2204 config FB_PS3_DEFAULT_SIZE_M
2205 int "PS3 default frame buffer size (in MiB)"
2209 This is the default size (in MiB) of the virtual frame buffer in
2211 The default value can be overridden on the kernel command line
2212 using the "ps3fb" option (e.g. "ps3fb=9M");
2215 tristate "Xilinx frame buffer support"
2216 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2217 select FB_CFB_FILLRECT
2218 select FB_CFB_COPYAREA
2219 select FB_CFB_IMAGEBLIT
2221 Include support for the Xilinx ML300/ML403 reference design
2222 framebuffer. ML300 carries a 640*480 LCD display on the board,
2223 ML403 uses a standard DB15 VGA connector.
2226 tristate "Goldfish Framebuffer"
2227 depends on FB && HAS_DMA
2228 select FB_CFB_FILLRECT
2229 select FB_CFB_COPYAREA
2230 select FB_CFB_IMAGEBLIT
2232 Framebuffer driver for Goldfish Virtual Platform
2235 tristate "Cobalt server LCD frame buffer support"
2236 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2239 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2240 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2241 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2242 select FB_CFB_FILLRECT
2243 select FB_CFB_COPYAREA
2244 select FB_CFB_IMAGEBLIT
2246 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2247 (D)STN/TFT LCD Controller.
2248 Supports display resolutions up to 1024x1024 pixel, grayscale and
2249 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2250 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2251 panels <= 320 pixel horizontal resolution.
2254 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2255 depends on FB && ARCH_DAVINCI_DA8XX
2256 select FB_CFB_FILLRECT
2257 select FB_CFB_COPYAREA
2258 select FB_CFB_IMAGEBLIT
2259 select FB_CFB_REV_PIXELS_IN_BYTE
2261 This is the frame buffer device driver for the TI LCD controller
2262 found on DA8xx/OMAP-L1xx SoCs.
2266 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2268 select FB_SYS_FILLRECT
2269 select FB_SYS_COPYAREA
2270 select FB_SYS_IMAGEBLIT
2273 This is a `virtual' frame buffer device. It operates on a chunk of
2274 unswappable kernel memory instead of on the memory of a graphics
2275 board. This means you cannot see any output sent to this frame
2276 buffer device, while it does consume precious memory. The main use
2277 of this frame buffer device is testing and debugging the frame
2278 buffer subsystem. Do NOT enable it for normal systems! To protect
2279 the innocent, it has to be enabled explicitly at boot time using the
2280 kernel option `video=vfb:'.
2282 To compile this driver as a module, choose M here: the
2283 module will be called vfb. In order to load it, you must use
2284 the vfb_enable=1 option.
2288 config XEN_FBDEV_FRONTEND
2289 tristate "Xen virtual frame buffer support"
2290 depends on FB && XEN
2291 select FB_SYS_FILLRECT
2292 select FB_SYS_COPYAREA
2293 select FB_SYS_IMAGEBLIT
2295 select FB_DEFERRED_IO
2296 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2297 select XEN_XENBUS_FRONTEND
2300 This driver implements the front-end of the Xen virtual
2301 frame buffer driver. It communicates with a back-end
2305 tristate "E-Ink Metronome/8track controller support"
2307 select FB_SYS_FILLRECT
2308 select FB_SYS_COPYAREA
2309 select FB_SYS_IMAGEBLIT
2311 select FB_DEFERRED_IO
2313 This driver implements support for the E-Ink Metronome
2314 controller. The pre-release name for this device was 8track
2315 and could also have been called by some vendors as PVI-nnnn.
2318 tristate "Fujitsu MB862xx GDC support"
2320 depends on PCI || (OF && PPC)
2321 select FB_CFB_FILLRECT
2322 select FB_CFB_COPYAREA
2323 select FB_CFB_IMAGEBLIT
2325 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2328 prompt "GDC variant"
2329 depends on FB_MB862XX
2331 config FB_MB862XX_PCI_GDC
2332 bool "Carmine/Coral-P(A) GDC"
2335 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2336 PCI graphics controller devices.
2338 config FB_MB862XX_LIME
2340 depends on OF && PPC
2341 select FB_FOREIGN_ENDIAN
2342 select FB_LITTLE_ENDIAN
2344 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2348 config FB_MB862XX_I2C
2349 bool "Support I2C bus on MB862XX GDC"
2350 depends on FB_MB862XX && I2C
2353 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2354 driver to support accessing I2C devices on controller's I2C bus.
2355 These are usually some video decoder chips.
2358 tristate "EP93XX frame buffer support"
2359 depends on FB && ARCH_EP93XX
2360 select FB_CFB_FILLRECT
2361 select FB_CFB_COPYAREA
2362 select FB_CFB_IMAGEBLIT
2364 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2365 This driver is also available as a module. The module will be called
2368 config FB_PRE_INIT_FB
2369 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2370 depends on FB && FB_MB862XX_LIME
2372 Select this option if display contents should be inherited as set by
2376 tristate "MSM Framebuffer support"
2377 depends on FB && ARCH_MSM
2378 select FB_CFB_FILLRECT
2379 select FB_CFB_COPYAREA
2380 select FB_CFB_IMAGEBLIT
2383 tristate "MX3 Framebuffer support"
2384 depends on FB && MX3_IPU
2385 select FB_CFB_FILLRECT
2386 select FB_CFB_COPYAREA
2387 select FB_CFB_IMAGEBLIT
2390 This is a framebuffer device for the i.MX31 LCD Controller. So
2391 far only synchronous displays are supported. If you plan to use
2392 an LCD display with your i.MX31 system, say Y here.
2394 config FB_BROADSHEET
2395 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2397 select FB_SYS_FILLRECT
2398 select FB_SYS_COPYAREA
2399 select FB_SYS_IMAGEBLIT
2401 select FB_DEFERRED_IO
2403 This driver implements support for the E-Ink Broadsheet
2404 controller. The release name for this device was Epson S1D13521
2405 and could also have been called by other names when coupled with
2409 tristate "AUO-K190X EPD controller support"
2411 select FB_SYS_FILLRECT
2412 select FB_SYS_COPYAREA
2413 select FB_SYS_IMAGEBLIT
2415 select FB_DEFERRED_IO
2417 Provides support for epaper controllers from the K190X series
2418 of AUO. These controllers can be used to drive epaper displays
2421 This option enables the common support, shared by the individual
2422 controller drivers. You will also have to enable the driver
2423 for the controller type used in your device.
2426 tristate "AUO-K1900 EPD controller support"
2427 depends on FB && FB_AUO_K190X
2429 This driver implements support for the AUO K1900 epd-controller.
2430 This controller can drive Sipix epaper displays but can only do
2431 serial updates, reducing the number of possible frames per second.
2434 tristate "AUO-K1901 EPD controller support"
2435 depends on FB && FB_AUO_K190X
2437 This driver implements support for the AUO K1901 epd-controller.
2438 This controller can drive Sipix epaper displays and supports
2439 concurrent updates, making higher frames per second possible.
2442 tristate "JZ4740 LCD framebuffer support"
2443 depends on FB && MACH_JZ4740
2444 select FB_SYS_FILLRECT
2445 select FB_SYS_COPYAREA
2446 select FB_SYS_IMAGEBLIT
2448 Framebuffer support for the JZ4740 SoC.
2451 tristate "MXS LCD framebuffer support"
2452 depends on FB && ARCH_MXS
2453 select FB_CFB_FILLRECT
2454 select FB_CFB_COPYAREA
2455 select FB_CFB_IMAGEBLIT
2456 select FB_MODE_HELPERS
2457 select VIDEOMODE_HELPERS
2459 Framebuffer support for the MXS SoC.
2461 config FB_PUV3_UNIGFX
2462 tristate "PKUnity v3 Unigfx framebuffer support"
2463 depends on FB && UNICORE32 && ARCH_PUV3
2464 select FB_SYS_FILLRECT
2465 select FB_SYS_COPYAREA
2466 select FB_SYS_IMAGEBLIT
2469 Choose this option if you want to use the Unigfx device as a
2470 framebuffer device. Without the support of PCI & AGP.
2473 tristate "Microsoft Hyper-V Synthetic Video support"
2474 depends on FB && HYPERV
2475 select FB_CFB_FILLRECT
2476 select FB_CFB_COPYAREA
2477 select FB_CFB_IMAGEBLIT
2479 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2482 bool "Simple framebuffer support"
2483 depends on (FB = y) && OF
2484 select FB_CFB_FILLRECT
2485 select FB_CFB_COPYAREA
2486 select FB_CFB_IMAGEBLIT
2488 Say Y if you want support for a simple frame-buffer.
2490 This driver assumes that the display hardware has been initialized
2491 before the kernel boots, and the kernel will simply render to the
2492 pre-allocated frame buffer surface.
2494 Configuration re: surface address, size, and format must be provided
2495 through device tree, or potentially plain old platform data in the
2498 source "drivers/video/sprdfb/Kconfig"
2500 source "drivers/video/omap/Kconfig"
2501 source "drivers/video/omap2/Kconfig"
2502 source "drivers/video/exynos/Kconfig"
2503 source "drivers/video/mmp/Kconfig"
2504 source "drivers/video/backlight/Kconfig"
2505 source "drivers/video/adf/Kconfig"
2508 source "drivers/video/console/Kconfig"
2511 if FB || SGI_NEWPORT_CONSOLE
2512 source "drivers/video/logo/Kconfig"
2515 config FB_SH_MOBILE_MERAM
2516 tristate "SuperH Mobile MERAM read ahead support"
2517 depends on (SUPERH || ARCH_SHMOBILE)
2518 select GENERIC_ALLOCATOR
2520 Enable MERAM support for the SuperH controller.
2522 This will allow for caching of the framebuffer to provide more
2523 reliable access under heavy main memory bus traffic situations.
2524 Up to 4 memory channels can be configured, allowing 4 RGB or
2525 2 YCbCr framebuffers to be configured.
2528 tristate "Solomon SSD1307 framebuffer support"
2529 depends on FB && I2C
2533 select FB_SYS_FILLRECT
2534 select FB_SYS_COPYAREA
2535 select FB_SYS_IMAGEBLIT
2536 select FB_DEFERRED_IO
2539 This driver implements support for the Solomon SSD1307
2540 OLED controller over I2C.