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/arm/midgard/Kconfig"
28 source "drivers/gpu/arm/mali400/mali/Kconfig"
30 source "drivers/gpu/arm/mali400/ump/Kconfig"
36 config VIDEO_OUTPUT_CONTROL
37 tristate "Lowlevel video output switch controls"
39 This framework adds support for low-level control of the video
42 config VIDEOMODE_HELPERS
48 config VEXPRESS_DVI_CONTROL
49 bool "Versatile Express DVI control"
50 depends on FB && VEXPRESS_CONFIG
54 tristate "Support for frame buffer devices"
56 The frame buffer device provides an abstraction for the graphics
57 hardware. It represents the frame buffer of some video hardware and
58 allows application software to access the graphics hardware through
59 a well-defined interface, so the software doesn't need to know
60 anything about the low-level (hardware register) stuff.
62 Frame buffer devices work identically across the different
63 architectures supported by Linux and make the implementation of
64 application programs easier and more portable; at this point, an X
65 server exists which uses the frame buffer device exclusively.
66 On several non-X86 architectures, the frame buffer device is the
67 only way to use the graphics hardware.
69 The device is accessed through special device nodes, usually located
70 in the /dev directory, i.e. /dev/fb*.
72 You need an utility program called fbset to make full use of frame
73 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
74 and the Framebuffer-HOWTO at
75 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
78 Say Y here and to the driver for your graphics board below if you
79 are compiling a kernel for a non-x86 architecture.
81 If you are compiling for the x86 architecture, you can say Y if you
82 want to play with it, but it is not essential. Please note that
83 running graphical applications that directly touch the hardware
84 (e.g. an accelerated X server) and that are not frame buffer
85 device-aware may cause unexpected results. If unsure, say N.
88 bool "Enable firmware EDID"
92 This enables access to the EDID transferred from the firmware.
93 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
94 transfers do not work for your driver and if you are using
95 nvidiafb, i810fb or savagefb.
97 In general, choosing Y for this option is safe. If you
98 experience extremely long delays while booting before you get
99 something on your display, try setting this to N. Matrox cards in
100 combination with certain motherboards and monitors are known to
101 suffer from this problem.
110 config FB_BOOT_VESA_SUPPORT
115 If true, at least one selected framebuffer driver can take advantage
116 of VESA video modes set at an early boot stage via the vga= parameter.
118 config FB_CFB_FILLRECT
123 Include the cfb_fillrect function for generic software rectangle
124 filling. This is used by drivers that don't provide their own
125 (accelerated) version.
127 config FB_CFB_COPYAREA
132 Include the cfb_copyarea function for generic software area copying.
133 This is used by drivers that don't provide their own (accelerated)
136 config FB_CFB_IMAGEBLIT
141 Include the cfb_imageblit function for generic software image
142 blitting. This is used by drivers that don't provide their own
143 (accelerated) version.
145 config FB_CFB_REV_PIXELS_IN_BYTE
150 Allow generic frame-buffer functions to work on displays with 1, 2
151 and 4 bits per pixel depths which has opposite order of pixels in
152 byte order to bytes in long order.
154 config FB_SYS_FILLRECT
159 Include the sys_fillrect function for generic software rectangle
160 filling. This is used by drivers that don't provide their own
161 (accelerated) version and the framebuffer is in system RAM.
163 config FB_SYS_COPYAREA
168 Include the sys_copyarea function for generic software area copying.
169 This is used by drivers that don't provide their own (accelerated)
170 version and the framebuffer is in system RAM.
172 config FB_SYS_IMAGEBLIT
177 Include the sys_imageblit function for generic software image
178 blitting. This is used by drivers that don't provide their own
179 (accelerated) version and the framebuffer is in system RAM.
181 menuconfig FB_FOREIGN_ENDIAN
182 bool "Framebuffer foreign endianness support"
185 This menu will let you enable support for the framebuffers with
186 non-native endianness (e.g. Little-Endian framebuffer on a
187 Big-Endian machine). Most probably you don't have such hardware,
188 so it's safe to say "n" here.
191 prompt "Choice endianness support"
192 depends on FB_FOREIGN_ENDIAN
194 config FB_BOTH_ENDIAN
195 bool "Support for Big- and Little-Endian framebuffers"
198 bool "Support for Big-Endian framebuffers only"
200 config FB_LITTLE_ENDIAN
201 bool "Support for Little-Endian framebuffers only"
210 config FB_DEFERRED_IO
217 depends on FB_DEFERRED_IO
224 Common utility functions useful to fbdev drivers of VGA-based
235 select BACKLIGHT_LCD_SUPPORT
236 select BACKLIGHT_CLASS_DEVICE
239 config FB_MODE_HELPERS
240 bool "Enable Video Mode Handling Helpers"
244 This enables functions for handling video modes using the
245 Generalized Timing Formula and the EDID parser. A few drivers rely
246 on this feature such as the radeonfb, rivafb, and the i810fb. If
247 your driver does not take advantage of this feature, choosing Y will
248 just increase the kernel size by about 5K.
250 config FB_TILEBLITTING
251 bool "Enable Tile Blitting Support"
255 This enables tile blitting. Tile blitting is a drawing technique
256 where the screen is divided into rectangular sections (tiles), whereas
257 the standard blitting divides the screen into pixels. Because the
258 default drawing element is a tile, drawing functions will be passed
259 parameters in terms of number of tiles instead of number of pixels.
260 For example, to draw a single character, instead of using bitmaps,
261 an index to an array of bitmaps will be used. To clear or move a
262 rectangular section of a screen, the rectangle will be described in
263 terms of number of tiles in the x- and y-axis.
265 This is particularly important to one driver, matroxfb. If
268 comment "Frame buffer hardware drivers"
272 tristate "Aeroflex Gaisler framebuffer support"
273 depends on FB && SPARC
274 select FB_CFB_FILLRECT
275 select FB_CFB_COPYAREA
276 select FB_CFB_IMAGEBLIT
278 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
281 tristate "Cirrus Logic support"
282 depends on FB && (ZORRO || PCI)
283 select FB_CFB_FILLRECT
284 select FB_CFB_COPYAREA
285 select FB_CFB_IMAGEBLIT
287 This enables support for Cirrus Logic GD542x/543x based boards on
288 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
290 If you have a PCI-based system, this enables support for these
291 chips: GD-543x, GD-544x, GD-5480.
293 Please read the file <file:Documentation/fb/cirrusfb.txt>.
295 Say N unless you have such a graphics board or plan to get one
296 before you next recompile the kernel.
299 tristate "Permedia2 support"
300 depends on FB && ((AMIGA && BROKEN) || PCI)
301 select FB_CFB_FILLRECT
302 select FB_CFB_COPYAREA
303 select FB_CFB_IMAGEBLIT
305 This is the frame buffer device driver for cards based on
306 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
307 The driver was tested on the following cards:
308 Diamond FireGL 1000 PRO AGP
309 ELSA Gloria Synergy PCI
310 Appian Jeronimo PRO (both heads) PCI
311 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
312 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
313 ASK Graphic Blaster Exxtreme AGP
315 To compile this driver as a module, choose M here: the
316 module will be called pm2fb.
318 config FB_PM2_FIFO_DISCONNECT
319 bool "enable FIFO disconnect feature"
320 depends on FB_PM2 && PCI
322 Support the Permedia2 FIFO disconnect feature.
325 tristate "ARM PrimeCell PL110 support"
326 depends on ARM || ARM64 || COMPILE_TEST
327 depends on FB && ARM_AMBA
328 select FB_CFB_FILLRECT
329 select FB_CFB_COPYAREA
330 select FB_CFB_IMAGEBLIT
332 This framebuffer device driver is for the ARM PrimeCell PL110
333 Colour LCD controller. ARM PrimeCells provide the building
334 blocks for System on a Chip devices.
336 If you want to compile this as a module (=code which can be
337 inserted into and removed from the running kernel), say M
338 here and read <file:Documentation/kbuild/modules.txt>. The module
339 will be called amba-clcd.
342 tristate "ARM High Definition LCD support"
344 select FB_CFB_FILLRECT
345 select FB_CFB_COPYAREA
346 select FB_CFB_IMAGEBLIT
348 This framebuffer device driver is for the ARM High Definition
349 Colour LCD controller.
351 If you want to compile this as a module (=code which can be
352 inserted into and removed from the running kernel), say M
353 here and read <file:Documentation/kbuild/modules.txt>. The module
354 will be called arm-hdlcd.
357 bool "Acorn VIDC support"
358 depends on (FB = y) && ARM && ARCH_ACORN
359 select FB_CFB_FILLRECT
360 select FB_CFB_COPYAREA
361 select FB_CFB_IMAGEBLIT
363 This is the frame buffer device driver for the Acorn VIDC graphics
364 hardware found in Acorn RISC PCs and other ARM-based machines. If
368 bool "CLPS711X LCD support"
369 depends on (FB = y) && ARM && ARCH_CLPS711X
370 select FB_CFB_FILLRECT
371 select FB_CFB_COPYAREA
372 select FB_CFB_IMAGEBLIT
374 Say Y to enable the Framebuffer driver for the CLPS7111 and
378 bool "SA-1100 LCD support"
379 depends on (FB = y) && ARM && ARCH_SA1100
380 select FB_CFB_FILLRECT
381 select FB_CFB_COPYAREA
382 select FB_CFB_IMAGEBLIT
384 This is a framebuffer device for the SA-1100 LCD Controller.
385 See <http://www.linux-fbdev.org/> for information on framebuffer
388 If you plan to use the LCD display with your SA-1100 system, say
392 tristate "Freescale i.MX1/21/25/27 LCD support"
393 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
394 select FB_CFB_FILLRECT
395 select FB_CFB_COPYAREA
396 select FB_CFB_IMAGEBLIT
399 tristate "CyberPro 2000/2010/5000 support"
400 depends on FB && PCI && (BROKEN || !SPARC64)
401 select FB_CFB_FILLRECT
402 select FB_CFB_COPYAREA
403 select FB_CFB_IMAGEBLIT
405 This enables support for the Integraphics CyberPro 20x0 and 5000
406 VGA chips used in the Rebel.com Netwinder and other machines.
407 Say Y if you have a NetWinder or a graphics card containing this
408 device, otherwise say N.
410 config FB_CYBER2000_DDC
411 bool "DDC for CyberPro support"
412 depends on FB_CYBER2000
416 Say Y here if you want DDC support for your CyberPro graphics
417 card. This is only I2C bus support, driver does not use EDID.
419 config FB_CYBER2000_I2C
420 bool "CyberPro 2000/2010/5000 I2C support"
421 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
424 Enable support for the I2C video decoder interface on the
425 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
426 on the Netwinder machines for the SAA7111 video capture.
430 depends on (FB = y) && APOLLO
432 select FB_CFB_FILLRECT
433 select FB_CFB_IMAGEBLIT
437 depends on (FB = y) && Q40
439 select FB_CFB_FILLRECT
440 select FB_CFB_COPYAREA
441 select FB_CFB_IMAGEBLIT
444 tristate "Amiga native chipset support"
445 depends on FB && AMIGA
447 This is the frame buffer device driver for the builtin graphics
448 chipset found in Amigas.
450 To compile this driver as a module, choose M here: the
451 module will be called amifb.
454 bool "Amiga OCS chipset support"
457 This enables support for the original Agnus and Denise video chips,
458 found in the Amiga 1000 and most A500's and A2000's. If you intend
459 to run Linux on any of these systems, say Y; otherwise say N.
462 bool "Amiga ECS chipset support"
465 This enables support for the Enhanced Chip Set, found in later
466 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
467 you intend to run Linux on any of these systems, say Y; otherwise
471 bool "Amiga AGA chipset support"
474 This enables support for the Advanced Graphics Architecture (also
475 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
476 and CD32. If you intend to run Linux on any of these systems, say Y;
480 bool "Amiga FrameMaster II/Rainbow II support"
481 depends on (FB = y) && ZORRO
482 select FB_CFB_FILLRECT
483 select FB_CFB_COPYAREA
484 select FB_CFB_IMAGEBLIT
486 This is the frame buffer device driver for the Amiga FrameMaster
487 card from BSC (exhibited 1992 but not shipped as a CBM product).
490 tristate "Arc Monochrome LCD board support"
492 select FB_SYS_FILLRECT
493 select FB_SYS_COPYAREA
494 select FB_SYS_IMAGEBLIT
497 This enables support for the Arc Monochrome LCD board. The board
498 is based on the KS-108 lcd controller and is typically a matrix
499 of 2*n chips. This driver was tested with a 128x64 panel. This
500 driver supports it for use with x86 SBCs through a 16 bit GPIO
501 interface (8 bit data, 8 bit control). If you anticipate using
502 this driver, say Y or M; otherwise say N. You must specify the
503 GPIO IO address to be used for setting control and data.
506 bool "Atari native chipset support"
507 depends on (FB = y) && ATARI
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
512 This is the frame buffer device driver for the builtin graphics
513 chipset found in Ataris.
516 bool "Open Firmware frame buffer device support"
517 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 Say Y if you want support with Open Firmware for your graphics
527 bool "Apple \"control\" display support"
528 depends on (FB = y) && PPC_PMAC && PPC32
529 select FB_CFB_FILLRECT
530 select FB_CFB_COPYAREA
531 select FB_CFB_IMAGEBLIT
534 This driver supports a frame buffer for the graphics adapter in the
535 Power Macintosh 7300 and others.
538 bool "Apple \"platinum\" display support"
539 depends on (FB = y) && PPC_PMAC && PPC32
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
545 This driver supports a frame buffer for the "platinum" graphics
546 adapter in some Power Macintoshes.
549 bool "Apple \"valkyrie\" display support"
550 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
556 This driver supports a frame buffer for the "valkyrie" graphics
557 adapter in some Power Macintoshes.
560 bool "Chips 65550 display support"
561 depends on (FB = y) && PPC32 && PCI
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
566 This is the frame buffer device driver for the Chips & Technologies
567 65550 graphics chip in PowerBooks.
570 bool "Asiliant (Chips) 69000 display support"
571 depends on (FB = y) && PCI
572 select FB_CFB_FILLRECT
573 select FB_CFB_COPYAREA
574 select FB_CFB_IMAGEBLIT
576 This is the frame buffer device driver for the Asiliant 69030 chipset
579 bool "IMS Twin Turbo display support"
580 depends on (FB = y) && PCI
581 select FB_CFB_IMAGEBLIT
582 select FB_MACMODES if PPC
584 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
585 many Macintosh and compatible computers.
588 tristate "VGA 16-color graphics support"
589 depends on FB && (X86 || PPC)
590 select FB_CFB_FILLRECT
591 select FB_CFB_COPYAREA
592 select FB_CFB_IMAGEBLIT
594 select FONT_8x16 if FRAMEBUFFER_CONSOLE
596 This is the frame buffer device driver for VGA 16 color graphic
597 cards. Say Y if you have such a card.
599 To compile this driver as a module, choose M here: the
600 module will be called vga16fb.
602 config FB_BF54X_LQ043
603 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
604 depends on FB && (BF54x) && !BF542
605 select FB_CFB_FILLRECT
606 select FB_CFB_COPYAREA
607 select FB_CFB_IMAGEBLIT
609 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
611 config FB_BFIN_T350MCQB
612 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
613 depends on FB && BLACKFIN
615 select FB_CFB_FILLRECT
616 select FB_CFB_COPYAREA
617 select FB_CFB_IMAGEBLIT
619 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
620 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
621 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
623 config FB_BFIN_LQ035Q1
624 tristate "SHARP LQ035Q1DH02 TFT LCD"
625 depends on FB && BLACKFIN && SPI
626 select FB_CFB_FILLRECT
627 select FB_CFB_COPYAREA
628 select FB_CFB_IMAGEBLIT
631 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
632 the Blackfin Landscape LCD EZ-Extender Card.
633 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
634 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
636 To compile this driver as a module, choose M here: the
637 module will be called bfin-lq035q1-fb.
639 config FB_BF537_LQ035
640 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
641 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
642 select FB_CFB_FILLRECT
643 select FB_CFB_COPYAREA
644 select FB_CFB_IMAGEBLIT
647 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
650 To compile this driver as a module, choose M here: the
651 module will be called bf537-lq035.
654 tristate "Blackfin ADV7393 Video encoder"
655 depends on FB && BLACKFIN
657 select FB_CFB_FILLRECT
658 select FB_CFB_COPYAREA
659 select FB_CFB_IMAGEBLIT
661 This is the framebuffer device for a ADV7393 video encoder
662 attached to a Blackfin on the PPI port.
663 If your Blackfin board has a ADV7393 select Y.
665 To compile this driver as a module, choose M here: the
666 module will be called bfin_adv7393fb.
669 prompt "Video mode support"
670 depends on FB_BFIN_7393
680 bool 'NTSC 640x480 (Experimental)'
683 bool 'PAL 640x480 (Experimental)'
686 bool 'NTSC 720x480 YCbCR input'
689 bool 'PAL 720x576 YCbCR input'
694 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
695 depends on (FB_BFIN_7393)
696 default ADV7393_1XMEM
706 tristate "HP STI frame buffer device support"
707 depends on FB && PARISC
708 select FB_CFB_FILLRECT
709 select FB_CFB_COPYAREA
710 select FB_CFB_IMAGEBLIT
715 STI refers to the HP "Standard Text Interface" which is a set of
716 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
717 Enabling this option will implement the linux framebuffer device
718 using calls to the STI BIOS routines for initialisation.
720 If you enable this option, you will get a planar framebuffer device
721 /dev/fb which will work on the most common HP graphic cards of the
722 NGLE family, including the artist chips (in the 7xx and Bxxx series),
723 HCRX, HCRX24, CRX, CRX24 and VisEG series.
725 It is safe to enable this option, so you should probably say "Y".
728 bool "Generic Macintosh display support"
729 depends on (FB = y) && MAC
730 select FB_CFB_FILLRECT
731 select FB_CFB_COPYAREA
732 select FB_CFB_IMAGEBLIT
737 depends on (FB = y) && DIO
738 select FB_CFB_IMAGEBLIT
742 tristate "TGA/SFB+ framebuffer support"
743 depends on FB && (ALPHA || TC)
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
749 This is the frame buffer device driver for generic TGA and SFB+
750 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
751 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
752 TURBOchannel cards, also known as PMAGD-A, -B and -C.
754 Due to hardware limitations ZLX-E2 and E3 cards are not supported
755 for DECstation 5000/200 systems. Additionally due to firmware
756 limitations these cards may cause troubles with booting DECstation
757 5000/240 and /260 systems, but are fully supported under Linux if
758 you manage to get it going. ;-)
760 Say Y if you have one of those.
763 tristate "Userspace VESA VGA graphics support"
764 depends on FB && CONNECTOR
765 select FB_CFB_FILLRECT
766 select FB_CFB_COPYAREA
767 select FB_CFB_IMAGEBLIT
768 select FB_MODE_HELPERS
770 This is the frame buffer driver for generic VBE 2.0 compliant
771 graphic cards. It can also take advantage of VBE 3.0 features,
772 such as refresh rate adjustment.
774 This driver generally provides more features than vesafb but
775 requires a userspace helper application called 'v86d'. See
776 <file:Documentation/fb/uvesafb.txt> for more information.
781 bool "VESA VGA graphics support"
782 depends on (FB = y) && X86
783 select FB_CFB_FILLRECT
784 select FB_CFB_COPYAREA
785 select FB_CFB_IMAGEBLIT
786 select FB_BOOT_VESA_SUPPORT
788 This is the frame buffer device driver for generic VESA 2.0
789 compliant graphic cards. The older VESA 1.2 cards are not supported.
790 You will get a boot time penguin logo at no additional cost. Please
791 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
794 bool "EFI-based Framebuffer Support"
795 depends on (FB = y) && X86 && EFI
796 select FB_CFB_FILLRECT
797 select FB_CFB_COPYAREA
798 select FB_CFB_IMAGEBLIT
800 This is the EFI frame buffer device driver. If the firmware on
801 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
802 using the EFI framebuffer as your console.
805 tristate "N411 Apollo/Hecuba devkit support"
806 depends on FB && X86 && MMU
807 select FB_SYS_FILLRECT
808 select FB_SYS_COPYAREA
809 select FB_SYS_IMAGEBLIT
811 select FB_DEFERRED_IO
814 This enables support for the Apollo display controller in its
815 Hecuba form using the n411 devkit.
818 tristate "Hercules mono graphics support"
821 Say Y here if you have a Hercules mono graphics card.
823 To compile this driver as a module, choose M here: the
824 module will be called hgafb.
826 As this card technology is at least 25 years old,
827 most people will answer N here.
830 tristate "SGI Visual Workstation framebuffer support"
831 depends on FB && X86_VISWS
832 select FB_CFB_FILLRECT
833 select FB_CFB_COPYAREA
834 select FB_CFB_IMAGEBLIT
836 SGI Visual Workstation support for framebuffer graphics.
839 bool "SGI Graphics Backend frame buffer support"
840 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
841 select FB_CFB_FILLRECT
842 select FB_CFB_COPYAREA
843 select FB_CFB_IMAGEBLIT
845 This is the frame buffer device driver for SGI Graphics Backend.
846 This chip is used in SGI O2 and Visual Workstation 320/540.
849 int "Video memory size in MB"
853 This is the amount of memory reserved for the framebuffer,
854 which can be any value between 1MB and 8MB.
857 bool "SBUS and UPA framebuffers"
858 depends on (FB = y) && SPARC
860 Say Y if you want support for SBUS or UPA based frame buffer device.
864 depends on (FB = y) && (SPARC && FB_SBUS)
865 select FB_CFB_FILLRECT
866 select FB_CFB_COPYAREA
867 select FB_CFB_IMAGEBLIT
869 This is the frame buffer device driver for the BWtwo frame buffer.
872 bool "CGthree support"
873 depends on (FB = y) && (SPARC && FB_SBUS)
874 select FB_CFB_FILLRECT
875 select FB_CFB_COPYAREA
876 select FB_CFB_IMAGEBLIT
878 This is the frame buffer device driver for the CGthree frame buffer.
881 bool "CGsix (GX,TurboGX) support"
882 depends on (FB = y) && (SPARC && FB_SBUS)
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the frame buffer device driver for the CGsix (GX, TurboGX)
890 bool "Creator/Creator3D/Elite3D support"
891 depends on FB_SBUS && SPARC64
892 select FB_CFB_COPYAREA
893 select FB_CFB_IMAGEBLIT
895 This is the frame buffer device driver for the Creator, Creator3D,
896 and Elite3D graphics boards.
899 bool "TCX (SS4/SS5 only) support"
901 select FB_CFB_FILLRECT
902 select FB_CFB_COPYAREA
903 select FB_CFB_IMAGEBLIT
905 This is the frame buffer device driver for the TCX 24/8bit frame
909 bool "CGfourteen (SX) support"
911 select FB_CFB_FILLRECT
912 select FB_CFB_COPYAREA
913 select FB_CFB_IMAGEBLIT
915 This is the frame buffer device driver for the CGfourteen frame
916 buffer on Desktop SPARCsystems with the SX graphics option.
919 bool "P9100 (Sparcbook 3 only) support"
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
925 This is the frame buffer device driver for the P9100 card
926 supported on Sparcbook 3 machines.
929 bool "Leo (ZX) support"
931 select FB_CFB_FILLRECT
932 select FB_CFB_COPYAREA
933 select FB_CFB_IMAGEBLIT
935 This is the frame buffer device driver for the SBUS-based Sun ZX
936 (leo) frame buffer cards.
939 bool "IGA 168x display support"
940 depends on (FB = y) && SPARC32
941 select FB_CFB_FILLRECT
942 select FB_CFB_COPYAREA
943 select FB_CFB_IMAGEBLIT
945 This is the framebuffer device for the INTERGRAPHICS 1680 and
946 successor frame buffer cards.
949 bool "Sun XVR-500 3DLABS Wildcat support"
950 depends on (FB = y) && PCI && SPARC64
951 select FB_CFB_FILLRECT
952 select FB_CFB_COPYAREA
953 select FB_CFB_IMAGEBLIT
955 This is the framebuffer device for the Sun XVR-500 and similar
956 graphics cards based upon the 3DLABS Wildcat chipset. The driver
957 only works on sparc64 systems where the system firmware has
958 mostly initialized the card already. It is treated as a
959 completely dumb framebuffer device.
962 bool "Sun XVR-2500 3DLABS Wildcat support"
963 depends on (FB = y) && PCI && SPARC64
964 select FB_CFB_FILLRECT
965 select FB_CFB_COPYAREA
966 select FB_CFB_IMAGEBLIT
968 This is the framebuffer device for the Sun XVR-2500 and similar
969 graphics cards based upon the 3DLABS Wildcat chipset. The driver
970 only works on sparc64 systems where the system firmware has
971 mostly initialized the card already. It is treated as a
972 completely dumb framebuffer device.
975 bool "Sun XVR-1000 support"
976 depends on (FB = y) && SPARC64
977 select FB_CFB_FILLRECT
978 select FB_CFB_COPYAREA
979 select FB_CFB_IMAGEBLIT
981 This is the framebuffer device for the Sun XVR-1000 and similar
982 graphics cards. The driver only works on sparc64 systems where
983 the system firmware has mostly initialized the card already. It
984 is treated as a completely dumb framebuffer device.
987 tristate "NEC PowerVR 2 display support"
988 depends on FB && SH_DREAMCAST
989 select FB_CFB_FILLRECT
990 select FB_CFB_COPYAREA
991 select FB_CFB_IMAGEBLIT
993 Say Y here if you have a PowerVR 2 card in your box. If you plan to
994 run linux on your Dreamcast, you will have to say Y here.
995 This driver may or may not work on other PowerVR 2 cards, but is
996 totally untested. Use at your own risk. If unsure, say N.
998 To compile this driver as a module, choose M here: the
999 module will be called pvr2fb.
1001 You can pass several parameters to the driver at boot time or at
1002 module load time. The parameters look like "video=pvr2:XXX", where
1003 the meaning of XXX can be found at the end of the main source file
1004 (<file:drivers/video/pvr2fb.c>). Please see the file
1005 <file:Documentation/fb/pvr2fb.txt>.
1008 tristate "Epson S1D13XXX framebuffer support"
1010 select FB_CFB_FILLRECT
1011 select FB_CFB_COPYAREA
1012 select FB_CFB_IMAGEBLIT
1014 Support for S1D13XXX framebuffer device family (currently only
1015 working with S1D13806). Product specs at
1016 <http://vdc.epson.com/>
1019 tristate "AT91/AT32 LCD Controller support"
1020 depends on FB && HAVE_FB_ATMEL
1021 select FB_CFB_FILLRECT
1022 select FB_CFB_COPYAREA
1023 select FB_CFB_IMAGEBLIT
1025 This enables support for the AT91/AT32 LCD Controller.
1028 bool "Frame Buffer in internal SRAM"
1029 depends on FB_ATMEL && ARCH_AT91SAM9261
1031 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1032 to let frame buffer in external SDRAM.
1035 bool "Use a STN display with AT91/AT32 LCD Controller"
1036 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1039 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1040 Controller. Say N if you want to connect a TFT.
1045 tristate "nVidia Framebuffer Support"
1046 depends on FB && PCI
1047 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1048 select FB_MODE_HELPERS
1049 select FB_CFB_FILLRECT
1050 select FB_CFB_COPYAREA
1051 select FB_CFB_IMAGEBLIT
1055 This driver supports graphics boards with the nVidia chips, TNT
1056 and newer. For very old chipsets, such as the RIVA128, then use
1058 Say Y if you have such a graphics board.
1060 To compile this driver as a module, choose M here: the
1061 module will be called nvidiafb.
1063 config FB_NVIDIA_I2C
1064 bool "Enable DDC Support"
1065 depends on FB_NVIDIA
1068 This enables I2C support for nVidia Chipsets. This is used
1069 only for getting EDID information from the attached display
1070 allowing for robust video mode handling and switching.
1072 Because fbdev-2.6 requires that drivers must be able to
1073 independently validate video mode parameters, you should say Y
1076 config FB_NVIDIA_DEBUG
1077 bool "Lots of debug output"
1078 depends on FB_NVIDIA
1081 Say Y here if you want the nVidia driver to output all sorts
1082 of debugging information to provide to the maintainer when
1083 something goes wrong.
1085 config FB_NVIDIA_BACKLIGHT
1086 bool "Support for backlight control"
1087 depends on FB_NVIDIA
1090 Say Y here if you want to control the backlight of your display.
1093 tristate "nVidia Riva support"
1094 depends on FB && PCI
1095 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1096 select FB_MODE_HELPERS
1097 select FB_CFB_FILLRECT
1098 select FB_CFB_COPYAREA
1099 select FB_CFB_IMAGEBLIT
1103 This driver supports graphics boards with the nVidia Riva/Geforce
1105 Say Y if you have such a graphics board.
1107 To compile this driver as a module, choose M here: the
1108 module will be called rivafb.
1111 bool "Enable DDC Support"
1115 This enables I2C support for nVidia Chipsets. This is used
1116 only for getting EDID information from the attached display
1117 allowing for robust video mode handling and switching.
1119 Because fbdev-2.6 requires that drivers must be able to
1120 independently validate video mode parameters, you should say Y
1123 config FB_RIVA_DEBUG
1124 bool "Lots of debug output"
1128 Say Y here if you want the Riva driver to output all sorts
1129 of debugging information to provide to the maintainer when
1130 something goes wrong.
1132 config FB_RIVA_BACKLIGHT
1133 bool "Support for backlight control"
1137 Say Y here if you want to control the backlight of your display.
1140 tristate "Intel740 support"
1141 depends on FB && PCI
1142 select FB_MODE_HELPERS
1143 select FB_CFB_FILLRECT
1144 select FB_CFB_COPYAREA
1145 select FB_CFB_IMAGEBLIT
1149 This driver supports graphics cards based on Intel740 chip.
1152 tristate "Intel 810/815 support"
1153 depends on FB && PCI && X86_32 && AGP_INTEL
1154 select FB_MODE_HELPERS
1155 select FB_CFB_FILLRECT
1156 select FB_CFB_COPYAREA
1157 select FB_CFB_IMAGEBLIT
1160 This driver supports the on-board graphics built in to the Intel 810
1161 and 815 chipsets. Say Y if you have and plan to use such a board.
1163 To compile this driver as a module, choose M here: the
1164 module will be called i810fb.
1166 For more information, please read
1167 <file:Documentation/fb/intel810.txt>
1170 bool "use VESA Generalized Timing Formula"
1173 If you say Y, then the VESA standard, Generalized Timing Formula
1174 or GTF, will be used to calculate the required video timing values
1175 per video mode. Since the GTF allows nondiscrete timings
1176 (nondiscrete being a range of values as opposed to discrete being a
1177 set of values), you'll be able to use any combination of horizontal
1178 and vertical resolutions, and vertical refresh rates without having
1179 to specify your own timing parameters. This is especially useful
1180 to maximize the performance of an aging display, or if you just
1181 have a display with nonstandard dimensions. A VESA compliant
1182 monitor is recommended, but can still work with non-compliant ones.
1183 If you need or want this, then select this option. The timings may
1184 not be compliant with Intel's recommended values. Use at your own
1187 If you say N, the driver will revert to discrete video timings
1188 using a set recommended by Intel in their documentation.
1193 bool "Enable DDC Support"
1194 depends on FB_I810 && FB_I810_GTF
1199 tristate "Intel LE80578 (Vermilion) support"
1200 depends on FB && PCI && X86
1201 select FB_MODE_HELPERS
1202 select FB_CFB_FILLRECT
1203 select FB_CFB_COPYAREA
1204 select FB_CFB_IMAGEBLIT
1206 This driver supports the LE80578 (Vermilion Range) chipset
1208 config FB_CARILLO_RANCH
1209 tristate "Intel Carillo Ranch support"
1210 depends on FB_LE80578 && FB && PCI && X86
1212 This driver supports the LE80578 (Carillo Ranch) board
1215 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1216 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1217 select FB_MODE_HELPERS
1218 select FB_CFB_FILLRECT
1219 select FB_CFB_COPYAREA
1220 select FB_CFB_IMAGEBLIT
1221 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1222 depends on !DRM_I915
1224 This driver supports the on-board graphics built in to the Intel
1225 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1226 Say Y if you have and plan to use such a board.
1228 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1230 To compile this driver as a module, choose M here: the
1231 module will be called intelfb.
1233 For more information, please read <file:Documentation/fb/intelfb.txt>
1235 config FB_INTEL_DEBUG
1236 bool "Intel driver Debug Messages"
1239 Say Y here if you want the Intel driver to output all sorts
1240 of debugging information to provide to the maintainer when
1241 something goes wrong.
1244 bool "DDC/I2C for Intel framebuffer support"
1249 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1252 tristate "Matrox acceleration"
1253 depends on FB && PCI
1254 select FB_CFB_FILLRECT
1255 select FB_CFB_COPYAREA
1256 select FB_CFB_IMAGEBLIT
1257 select FB_TILEBLITTING
1258 select FB_MACMODES if PPC_PMAC
1260 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1261 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1262 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1263 Matrox G400, G450 or G550 card in your box.
1265 To compile this driver as a module, choose M here: the
1266 module will be called matroxfb.
1268 You can pass several parameters to the driver at boot time or at
1269 module load time. The parameters look like "video=matroxfb:XXX", and
1270 are described in <file:Documentation/fb/matroxfb.txt>.
1272 config FB_MATROX_MILLENIUM
1273 bool "Millennium I/II support"
1274 depends on FB_MATROX
1276 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1277 video card. If you select "Advanced lowlevel driver options" below,
1278 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1279 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1280 also use font widths different from 8.
1282 config FB_MATROX_MYSTIQUE
1283 bool "Mystique support"
1284 depends on FB_MATROX
1286 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1287 video card. If you select "Advanced lowlevel driver options" below,
1288 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1289 packed pixel and 32 bpp packed pixel. You can also use font widths
1293 bool "G100/G200/G400/G450/G550 support"
1294 depends on FB_MATROX
1296 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1297 video card. If you select "Advanced lowlevel driver options", you
1298 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1299 pixel and 32 bpp packed pixel. You can also use font widths
1302 If you need support for G400 secondary head, you must say Y to
1303 "Matrox I2C support" and "G400 second head support" right below.
1304 G450/G550 secondary head and digital output are supported without
1307 The driver starts in monitor mode. You must use the matroxset tool
1308 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1309 swap primary and secondary head outputs, or to change output mode.
1310 Secondary head driver always start in 640x480 resolution and you
1311 must use fbset to change it.
1313 Do not forget that second head supports only 16 and 32 bpp
1314 packed pixels, so it is a good idea to compile them into the kernel
1315 too. You can use only some font widths, as the driver uses generic
1316 painting procedures (the secondary head does not use acceleration
1319 G450/G550 hardware can display TV picture only from secondary CRTC,
1320 and it performs no scaling, so picture must have 525 or 625 lines.
1322 config FB_MATROX_I2C
1323 tristate "Matrox I2C support"
1324 depends on FB_MATROX
1327 This drivers creates I2C buses which are needed for accessing the
1328 DDC (I2C) bus present on all Matroxes, an I2C bus which
1329 interconnects Matrox optional devices, like MGA-TVO on G200 and
1330 G400, and the secondary head DDC bus, present on G400 only.
1332 You can say Y or M here if you want to experiment with monitor
1333 detection code. You must say Y or M here if you want to use either
1334 second head of G400 or MGA-TVO on G200 or G400.
1336 If you compile it as module, it will create a module named
1339 config FB_MATROX_MAVEN
1340 tristate "G400 second head support"
1341 depends on FB_MATROX_G && FB_MATROX_I2C
1343 WARNING !!! This support does not work with G450 !!!
1345 Say Y or M here if you want to use a secondary head (meaning two
1346 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1347 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1348 secondary head output is blanked while you are in X. With XFree
1349 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1350 the fbdev driver on first head and the fbdev driver on second head.
1352 If you compile it as module, two modules are created,
1353 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1354 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1355 also load i2c-matroxfb to get it to run.
1357 The driver starts in monitor mode and you must use the matroxset
1359 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1360 PAL or NTSC or to swap primary and secondary head outputs.
1361 Secondary head driver also always start in 640x480 resolution, you
1362 must use fbset to change it.
1364 Also do not forget that second head supports only 16 and 32 bpp
1365 packed pixels, so it is a good idea to compile them into the kernel
1366 too. You can use only some font widths, as the driver uses generic
1367 painting procedures (the secondary head does not use acceleration
1371 tristate "ATI Radeon display support"
1372 depends on FB && PCI
1373 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1374 select FB_MODE_HELPERS
1375 select FB_CFB_FILLRECT
1376 select FB_CFB_COPYAREA
1377 select FB_CFB_IMAGEBLIT
1378 select FB_MACMODES if PPC_OF
1380 Choose this option if you want to use an ATI Radeon graphics card as
1381 a framebuffer device. There are both PCI and AGP versions. You
1382 don't need to choose this to run the Radeon in plain VGA mode.
1384 There is a product page at
1385 http://products.amd.com/en-us/GraphicCardResult.aspx
1387 config FB_RADEON_I2C
1388 bool "DDC/I2C for ATI Radeon support"
1389 depends on FB_RADEON
1393 Say Y here if you want DDC/I2C support for your Radeon board.
1395 config FB_RADEON_BACKLIGHT
1396 bool "Support for backlight control"
1397 depends on FB_RADEON
1400 Say Y here if you want to control the backlight of your display.
1402 config FB_RADEON_DEBUG
1403 bool "Lots of debug output from Radeon driver"
1404 depends on FB_RADEON
1407 Say Y here if you want the Radeon driver to output all sorts
1408 of debugging information to provide to the maintainer when
1409 something goes wrong.
1412 tristate "ATI Rage128 display support"
1413 depends on FB && PCI
1414 select FB_CFB_FILLRECT
1415 select FB_CFB_COPYAREA
1416 select FB_CFB_IMAGEBLIT
1417 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1418 select FB_MACMODES if PPC_PMAC
1420 This driver supports graphics boards with the ATI Rage128 chips.
1421 Say Y if you have such a graphics board and read
1422 <file:Documentation/fb/aty128fb.txt>.
1424 To compile this driver as a module, choose M here: the
1425 module will be called aty128fb.
1427 config FB_ATY128_BACKLIGHT
1428 bool "Support for backlight control"
1429 depends on FB_ATY128
1432 Say Y here if you want to control the backlight of your display.
1435 tristate "ATI Mach64 display support" if PCI || ATARI
1436 depends on FB && !SPARC32
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1439 select FB_CFB_IMAGEBLIT
1440 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1441 select FB_MACMODES if PPC
1443 This driver supports graphics boards with the ATI Mach64 chips.
1444 Say Y if you have such a graphics board.
1446 To compile this driver as a module, choose M here: the
1447 module will be called atyfb.
1450 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1451 depends on PCI && FB_ATY
1452 default y if SPARC64 && PCI
1454 Say Y here to support use of ATI's 64-bit Rage boards (or other
1455 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1456 framebuffer device. The ATI product support page for these boards
1457 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1459 config FB_ATY_GENERIC_LCD
1460 bool "Mach64 generic LCD support"
1461 depends on FB_ATY_CT
1463 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1464 Rage XC, or Rage XL chipset.
1467 bool "Mach64 GX support" if PCI
1471 Say Y here to support use of the ATI Mach64 Graphics Expression
1472 board (or other boards based on the Mach64 GX chipset) as a
1473 framebuffer device. The ATI product support page for these boards
1475 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1477 config FB_ATY_BACKLIGHT
1478 bool "Support for backlight control"
1482 Say Y here if you want to control the backlight of your display.
1485 tristate "S3 Trio/Virge support"
1486 depends on FB && PCI
1487 select FB_CFB_FILLRECT
1488 select FB_CFB_COPYAREA
1489 select FB_CFB_IMAGEBLIT
1490 select FB_TILEBLITTING
1493 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1495 Driver for graphics boards with S3 Trio / S3 Virge chip.
1498 bool "DDC for S3 support"
1503 Say Y here if you want DDC support for your S3 graphics card.
1506 tristate "S3 Savage support"
1507 depends on FB && PCI
1508 select FB_MODE_HELPERS
1509 select FB_CFB_FILLRECT
1510 select FB_CFB_COPYAREA
1511 select FB_CFB_IMAGEBLIT
1514 This driver supports notebooks and computers with S3 Savage PCI/AGP
1517 Say Y if you have such a graphics card.
1519 To compile this driver as a module, choose M here; the module
1520 will be called savagefb.
1522 config FB_SAVAGE_I2C
1523 bool "Enable DDC2 Support"
1524 depends on FB_SAVAGE
1527 This enables I2C support for S3 Savage Chipsets. This is used
1528 only for getting EDID information from the attached display
1529 allowing for robust video mode handling and switching.
1531 Because fbdev-2.6 requires that drivers must be able to
1532 independently validate video mode parameters, you should say Y
1535 config FB_SAVAGE_ACCEL
1536 bool "Enable Console Acceleration"
1537 depends on FB_SAVAGE
1540 This option will compile in console acceleration support. If
1541 the resulting framebuffer console has bothersome glitches, then
1545 tristate "SiS/XGI display support"
1546 depends on FB && PCI
1547 select FB_CFB_FILLRECT
1548 select FB_CFB_COPYAREA
1549 select FB_CFB_IMAGEBLIT
1550 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1552 This is the frame buffer device driver for the SiS 300, 315, 330
1553 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1554 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1556 To compile this driver as a module, choose M here; the module
1557 will be called sisfb.
1560 bool "SiS 300 series support"
1563 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1566 bool "SiS 315/330/340 series and XGI support"
1569 Say Y here to support use of the SiS 315, 330 and 340 series
1570 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1571 as XGI V3XT, V5, V8 and Z7.
1574 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1575 depends on FB && PCI && X86
1576 select FB_CFB_FILLRECT
1577 select FB_CFB_COPYAREA
1578 select FB_CFB_IMAGEBLIT
1583 This is the frame buffer device driver for Graphics chips of VIA
1584 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1585 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1587 Say Y if you have a VIA UniChrome graphics board.
1589 To compile this driver as a module, choose M here: the
1590 module will be called viafb.
1594 config FB_VIA_DIRECT_PROCFS
1595 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1599 Allow direct hardware access to some output registers via procfs.
1600 This is dangerous but may provide the only chance to get the
1601 correct output device configuration.
1602 Its use is strongly discouraged.
1604 config FB_VIA_X_COMPATIBILITY
1605 bool "X server compatibility"
1609 This option reduces the functionality (power saving, ...) of the
1610 framebuffer to avoid negative impact on the OpenChrome X server.
1611 If you use any X server other than fbdev you should enable this
1612 otherwise it should be safe to disable it and allow using all
1618 tristate "NeoMagic display support"
1619 depends on FB && PCI
1620 select FB_MODE_HELPERS
1621 select FB_CFB_FILLRECT
1622 select FB_CFB_COPYAREA
1623 select FB_CFB_IMAGEBLIT
1626 This driver supports notebooks with NeoMagic PCI chips.
1627 Say Y if you have such a graphics card.
1629 To compile this driver as a module, choose M here: the
1630 module will be called neofb.
1633 tristate "IMG Kyro support"
1634 depends on FB && PCI
1635 select FB_CFB_FILLRECT
1636 select FB_CFB_COPYAREA
1637 select FB_CFB_IMAGEBLIT
1639 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1642 To compile this driver as a module, choose M here: the
1643 module will be called kyrofb.
1646 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1647 depends on FB && PCI
1648 select FB_CFB_IMAGEBLIT
1649 select FB_CFB_FILLRECT
1650 select FB_CFB_COPYAREA
1651 select FB_MODE_HELPERS
1653 This driver supports graphics boards with the 3Dfx Banshee,
1654 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1655 such a graphics board.
1657 To compile this driver as a module, choose M here: the
1658 module will be called tdfxfb.
1660 config FB_3DFX_ACCEL
1661 bool "3Dfx Acceleration functions"
1664 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1665 device driver with acceleration functions.
1668 bool "Enable DDC/I2C support"
1673 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1676 tristate "3Dfx Voodoo Graphics (sst1) support"
1677 depends on FB && PCI
1678 select FB_CFB_FILLRECT
1679 select FB_CFB_COPYAREA
1680 select FB_CFB_IMAGEBLIT
1682 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1683 Voodoo2 (cvg) based graphics card.
1685 To compile this driver as a module, choose M here: the
1686 module will be called sstfb.
1688 WARNING: Do not use any application that uses the 3D engine
1689 (namely glide) while using this driver.
1690 Please read the <file:Documentation/fb/sstfb.txt> for supported
1691 options and other important info support.
1694 tristate "VIA VT8623 support"
1695 depends on FB && PCI
1696 select FB_CFB_FILLRECT
1697 select FB_CFB_COPYAREA
1698 select FB_CFB_IMAGEBLIT
1699 select FB_TILEBLITTING
1702 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1704 Driver for CastleRock integrated graphics core in the
1705 VIA VT8623 [Apollo CLE266] chipset.
1708 tristate "Trident/CyberXXX/CyberBlade support"
1709 depends on FB && PCI
1710 select FB_CFB_FILLRECT
1711 select FB_CFB_COPYAREA
1712 select FB_CFB_IMAGEBLIT
1714 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1715 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1717 There are also integrated versions of these chips called CyberXXXX,
1718 CyberImage or CyberBlade. These chips are mostly found in laptops
1719 but also on some motherboards including early VIA EPIA motherboards.
1720 For more information, read <file:Documentation/fb/tridentfb.txt>
1722 Say Y if you have such a graphics board.
1724 To compile this driver as a module, choose M here: the
1725 module will be called tridentfb.
1728 tristate "ARK 2000PV support"
1729 depends on FB && PCI
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1733 select FB_TILEBLITTING
1736 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1738 Driver for PCI graphics boards with ARK 2000PV chip
1739 and ICS 5342 RAMDAC.
1742 tristate "Permedia3 support"
1743 depends on FB && PCI
1744 select FB_CFB_FILLRECT
1745 select FB_CFB_COPYAREA
1746 select FB_CFB_IMAGEBLIT
1748 This is the frame buffer device driver for the 3DLabs Permedia3
1749 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1750 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1751 and maybe other boards.
1754 tristate "Fujitsu carmine frame buffer support"
1755 depends on FB && PCI
1756 select FB_CFB_FILLRECT
1757 select FB_CFB_COPYAREA
1758 select FB_CFB_IMAGEBLIT
1760 This is the frame buffer device driver for the Fujitsu Carmine chip.
1761 The driver provides two independent frame buffer devices.
1764 depends on FB_CARMINE
1765 prompt "DRAM timing"
1766 default FB_CARMINE_DRAM_EVAL
1768 config FB_CARMINE_DRAM_EVAL
1769 bool "Eval board timings"
1771 Use timings which work on the eval card.
1773 config CARMINE_DRAM_CUSTOM
1774 bool "Custom board timings"
1776 Use custom board timings.
1780 bool "Au1100 LCD Driver"
1781 depends on (FB = y) && MIPS_ALCHEMY
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1786 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1787 various panels and CRTs by passing in kernel cmd line option
1788 au1100fb:panel=<name>.
1791 bool "Au1200/Au1300 LCD Driver"
1792 depends on (FB = y) && MIPS_ALCHEMY
1793 select FB_SYS_FILLRECT
1794 select FB_SYS_COPYAREA
1795 select FB_SYS_IMAGEBLIT
1798 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1799 It can drive various panels and CRTs by passing in kernel cmd line
1800 option au1200fb:panel=<name>.
1803 bool "VIA VT8500 framebuffer support"
1804 depends on (FB = y) && ARM && ARCH_VT8500
1805 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1806 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1807 select FB_SYS_IMAGEBLIT
1808 select FB_MODE_HELPERS
1809 select VIDEOMODE_HELPERS
1811 This is the framebuffer driver for VIA VT8500 integrated LCD
1815 bool "Wondermedia WM8xxx-series frame buffer support"
1816 depends on (FB = y) && ARM && ARCH_VT8500
1817 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1818 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1819 select FB_SYS_IMAGEBLIT
1820 select FB_MODE_HELPERS
1821 select VIDEOMODE_HELPERS
1823 This is the framebuffer driver for WonderMedia WM8xxx-series
1824 integrated LCD controller. This driver covers the WM8505, WM8650
1827 config FB_WMT_GE_ROPS
1828 bool "VT8500/WM8xxx accelerated raster ops support"
1829 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1832 This adds support for accelerated raster operations on the
1833 VIA VT8500 and Wondermedia 85xx series SoCs.
1835 source "drivers/video/geode/Kconfig"
1838 tristate "HD64461 Frame Buffer support"
1839 depends on FB && HD64461
1840 select FB_CFB_FILLRECT
1841 select FB_CFB_COPYAREA
1842 select FB_CFB_IMAGEBLIT
1844 This is the frame buffer device driver for the Hitachi HD64461 LCD
1848 bool "PMAG-AA TURBOchannel framebuffer support"
1849 depends on (FB = y) && TC
1850 select FB_CFB_FILLRECT
1851 select FB_CFB_COPYAREA
1852 select FB_CFB_IMAGEBLIT
1854 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1855 used mainly in the MIPS-based DECstation series.
1858 tristate "PMAG-BA TURBOchannel framebuffer support"
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1864 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1865 used mainly in the MIPS-based DECstation series.
1868 tristate "PMAGB-B TURBOchannel framebuffer support"
1870 select FB_CFB_FILLRECT
1871 select FB_CFB_COPYAREA
1872 select FB_CFB_IMAGEBLIT
1874 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1875 in the MIPS-based DECstation series. The card is currently only
1876 supported in 1280x1024x8 mode.
1879 bool "Maxine (Personal DECstation) onboard framebuffer support"
1880 depends on (FB = y) && MACH_DECSTATION
1881 select FB_CFB_FILLRECT
1882 select FB_CFB_COPYAREA
1883 select FB_CFB_IMAGEBLIT
1885 Support for the onboard framebuffer (1024x768x8) in the Personal
1886 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1890 bool "G364 frame buffer support"
1891 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1892 select FB_CFB_FILLRECT
1893 select FB_CFB_COPYAREA
1894 select FB_CFB_IMAGEBLIT
1896 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1897 Olivetti M700-10 systems.
1900 bool "Motorola 68328 native frame buffer support"
1901 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1902 select FB_CFB_FILLRECT
1903 select FB_CFB_COPYAREA
1904 select FB_CFB_IMAGEBLIT
1906 Say Y here if you want to support the built-in frame buffer of
1907 the Motorola 68328 CPU family.
1910 tristate "PXA168/910 LCD framebuffer support"
1911 depends on FB && (CPU_PXA168 || CPU_PXA910)
1912 select FB_CFB_FILLRECT
1913 select FB_CFB_COPYAREA
1914 select FB_CFB_IMAGEBLIT
1916 Frame buffer driver for the built-in LCD controller in the Marvell
1920 tristate "PXA LCD framebuffer support"
1921 depends on FB && ARCH_PXA
1922 select FB_CFB_FILLRECT
1923 select FB_CFB_COPYAREA
1924 select FB_CFB_IMAGEBLIT
1926 Frame buffer driver for the built-in LCD controller in the Intel
1929 This driver is also available as a module ( = code which can be
1930 inserted and removed from the running kernel whenever you want). The
1931 module will be called pxafb. If you want to compile it as a module,
1932 say M here and read <file:Documentation/kbuild/modules.txt>.
1936 config FB_PXA_OVERLAY
1937 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1939 depends on FB_PXA && (PXA27x || PXA3xx)
1941 config FB_PXA_SMARTPANEL
1942 bool "PXA Smartpanel LCD support"
1946 config FB_PXA_PARAMETERS
1947 bool "PXA LCD command line parameters"
1951 Enable the use of kernel command line or module parameters
1952 to configure the physical properties of the LCD panel when
1953 using the PXA LCD driver.
1955 This option allows you to override the panel parameters
1956 supplied by the platform in order to support multiple
1957 different models of flatpanel. If you will only be using a
1958 single model of flatpanel then you can safely leave this
1961 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1964 tristate "PXA3xx 2D graphics accelerator driver"
1967 Kernelspace driver for the 2D graphics controller unit (GCU)
1968 found on PXA3xx processors. There is a counterpart driver in the
1969 DirectFB suite, see http://www.directfb.org/
1971 If you compile this as a module, it will be called pxa3xx_gcu.
1974 tristate "2700G LCD framebuffer support"
1975 depends on FB && ARCH_PXA
1976 select FB_CFB_FILLRECT
1977 select FB_CFB_COPYAREA
1978 select FB_CFB_IMAGEBLIT
1980 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1984 bool "Enable debugging info via debugfs"
1985 depends on FB_MBX && DEBUG_FS
1988 Enable this if you want debugging information using the debug
1989 filesystem (debugfs)
1994 tristate "Freescale DIU framebuffer support"
1995 depends on FB && FSL_SOC
1996 select FB_MODE_HELPERS
1997 select FB_CFB_FILLRECT
1998 select FB_CFB_COPYAREA
1999 select FB_CFB_IMAGEBLIT
2000 select PPC_LIB_RHEAP
2002 Framebuffer driver for the Freescale SoC DIU
2005 tristate "W100 frame buffer support"
2006 depends on FB && ARCH_PXA
2007 select FB_CFB_FILLRECT
2008 select FB_CFB_COPYAREA
2009 select FB_CFB_IMAGEBLIT
2011 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2012 It can also drive the w3220 chip found on iPAQ hx4700.
2014 This driver is also available as a module ( = code which can be
2015 inserted and removed from the running kernel whenever you want). The
2016 module will be called w100fb. If you want to compile it as a module,
2017 say M here and read <file:Documentation/kbuild/modules.txt>.
2021 config FB_SH_MOBILE_LCDC
2022 tristate "SuperH Mobile LCDC framebuffer support"
2023 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2024 select FB_SYS_FILLRECT
2025 select FB_SYS_COPYAREA
2026 select FB_SYS_IMAGEBLIT
2028 select FB_DEFERRED_IO
2030 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2032 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2034 config FB_SH_MOBILE_HDMI
2035 tristate "SuperH Mobile HDMI controller support"
2036 depends on FB_SH_MOBILE_LCDC
2037 select FB_MODE_HELPERS
2042 Driver for the on-chip SH-Mobile HDMI controller.
2045 tristate "Toshiba Mobile IO FrameBuffer support"
2046 depends on FB && MFD_CORE
2047 select FB_CFB_FILLRECT
2048 select FB_CFB_COPYAREA
2049 select FB_CFB_IMAGEBLIT
2051 Frame buffer driver for the Toshiba Mobile IO integrated as found
2052 on the Sharp SL-6000 series
2054 This driver is also available as a module ( = code which can be
2055 inserted and removed from the running kernel whenever you want). The
2056 module will be called tmiofb. If you want to compile it as a module,
2057 say M here and read <file:Documentation/kbuild/modules.txt>.
2061 config FB_TMIO_ACCELL
2062 bool "tmiofb acceleration"
2067 tristate "Samsung S3C framebuffer support"
2068 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2069 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2070 select FB_CFB_FILLRECT
2071 select FB_CFB_COPYAREA
2072 select FB_CFB_IMAGEBLIT
2074 Frame buffer driver for the built-in FB controller in the Samsung
2075 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2076 and the S3C64XX series such as the S3C6400 and S3C6410.
2078 These chips all have the same basic framebuffer design with the
2079 actual capabilities depending on the chip. For instance the S3C6400
2080 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2081 currently only have two.
2083 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2085 config FB_S3C_DEBUG_REGWRITE
2086 bool "Debug register writes"
2089 Show all register writes via pr_debug()
2092 tristate "S3C2410 LCD framebuffer support"
2093 depends on FB && ARCH_S3C24XX
2094 select FB_CFB_FILLRECT
2095 select FB_CFB_COPYAREA
2096 select FB_CFB_IMAGEBLIT
2098 Frame buffer driver for the built-in LCD controller in the Samsung
2101 This driver is also available as a module ( = code which can be
2102 inserted and removed from the running kernel whenever you want). The
2103 module will be called s3c2410fb. If you want to compile it as a module,
2104 say M here and read <file:Documentation/kbuild/modules.txt>.
2107 config FB_S3C2410_DEBUG
2108 bool "S3C2410 lcd debug messages"
2109 depends on FB_S3C2410
2111 Turn on debugging messages. Note that you can set/unset at run time
2115 bool "NUC900 LCD framebuffer support"
2116 depends on FB && ARCH_W90X900
2117 select FB_CFB_FILLRECT
2118 select FB_CFB_COPYAREA
2119 select FB_CFB_IMAGEBLIT
2121 Frame buffer driver for the built-in LCD controller in the Nuvoton
2124 config GPM1040A0_320X240
2125 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2126 depends on FB_NUC900
2128 config FB_NUC900_DEBUG
2129 bool "NUC900 lcd debug messages"
2130 depends on FB_NUC900
2132 Turn on debugging messages. Note that you can set/unset at run time
2136 tristate "Silicon Motion SM501 framebuffer support"
2137 depends on FB && MFD_SM501
2138 select FB_CFB_FILLRECT
2139 select FB_CFB_COPYAREA
2140 select FB_CFB_IMAGEBLIT
2142 Frame buffer driver for the CRT and LCD controllers in the Silicon
2145 This driver is also available as a module ( = code which can be
2146 inserted and removed from the running kernel whenever you want). The
2147 module will be called sm501fb. If you want to compile it as a module,
2148 say M here and read <file:Documentation/kbuild/modules.txt>.
2153 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2154 depends on FB && USB
2155 select FB_MODE_HELPERS
2156 select FB_SYS_FILLRECT
2157 select FB_SYS_COPYAREA
2158 select FB_SYS_IMAGEBLIT
2160 select FB_DEFERRED_IO
2162 This is a kernel framebuffer driver for SMSC UFX USB devices.
2163 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2164 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2166 To compile as a module, choose M here: the module name is smscufx.
2169 tristate "Displaylink USB Framebuffer support"
2170 depends on FB && USB
2171 select FB_MODE_HELPERS
2172 select FB_SYS_FILLRECT
2173 select FB_SYS_COPYAREA
2174 select FB_SYS_IMAGEBLIT
2176 select FB_DEFERRED_IO
2178 This is a kernel framebuffer driver for DisplayLink USB devices.
2179 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2180 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2181 To compile as a module, choose M here: the module name is udlfb.
2183 config FB_IBM_GXT4500
2184 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2185 depends on FB && PPC
2186 select FB_CFB_FILLRECT
2187 select FB_CFB_COPYAREA
2188 select FB_CFB_IMAGEBLIT
2190 Say Y here to enable support for the IBM GXT4000P/6000P and
2191 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2192 found on some IBM System P (pSeries) machines. This driver
2193 doesn't use Geometry Engine GT1000.
2196 tristate "PS3 GPU framebuffer driver"
2197 depends on FB && PS3_PS3AV
2198 select FB_SYS_FILLRECT
2199 select FB_SYS_COPYAREA
2200 select FB_SYS_IMAGEBLIT
2202 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2204 Include support for the virtual frame buffer in the PS3 platform.
2206 config FB_PS3_DEFAULT_SIZE_M
2207 int "PS3 default frame buffer size (in MiB)"
2211 This is the default size (in MiB) of the virtual frame buffer in
2213 The default value can be overridden on the kernel command line
2214 using the "ps3fb" option (e.g. "ps3fb=9M");
2217 tristate "Xilinx frame buffer support"
2218 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2219 select FB_CFB_FILLRECT
2220 select FB_CFB_COPYAREA
2221 select FB_CFB_IMAGEBLIT
2223 Include support for the Xilinx ML300/ML403 reference design
2224 framebuffer. ML300 carries a 640*480 LCD display on the board,
2225 ML403 uses a standard DB15 VGA connector.
2228 tristate "Goldfish Framebuffer"
2229 depends on FB && HAS_DMA
2230 select FB_CFB_FILLRECT
2231 select FB_CFB_COPYAREA
2232 select FB_CFB_IMAGEBLIT
2234 Framebuffer driver for Goldfish Virtual Platform
2237 tristate "Cobalt server LCD frame buffer support"
2238 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2241 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2242 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2243 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2244 select FB_CFB_FILLRECT
2245 select FB_CFB_COPYAREA
2246 select FB_CFB_IMAGEBLIT
2248 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2249 (D)STN/TFT LCD Controller.
2250 Supports display resolutions up to 1024x1024 pixel, grayscale and
2251 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2252 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2253 panels <= 320 pixel horizontal resolution.
2256 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2257 depends on FB && ARCH_DAVINCI_DA8XX
2258 select FB_CFB_FILLRECT
2259 select FB_CFB_COPYAREA
2260 select FB_CFB_IMAGEBLIT
2261 select FB_CFB_REV_PIXELS_IN_BYTE
2263 This is the frame buffer device driver for the TI LCD controller
2264 found on DA8xx/OMAP-L1xx SoCs.
2268 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2270 select FB_SYS_FILLRECT
2271 select FB_SYS_COPYAREA
2272 select FB_SYS_IMAGEBLIT
2275 This is a `virtual' frame buffer device. It operates on a chunk of
2276 unswappable kernel memory instead of on the memory of a graphics
2277 board. This means you cannot see any output sent to this frame
2278 buffer device, while it does consume precious memory. The main use
2279 of this frame buffer device is testing and debugging the frame
2280 buffer subsystem. Do NOT enable it for normal systems! To protect
2281 the innocent, it has to be enabled explicitly at boot time using the
2282 kernel option `video=vfb:'.
2284 To compile this driver as a module, choose M here: the
2285 module will be called vfb. In order to load it, you must use
2286 the vfb_enable=1 option.
2290 config XEN_FBDEV_FRONTEND
2291 tristate "Xen virtual frame buffer support"
2292 depends on FB && XEN
2293 select FB_SYS_FILLRECT
2294 select FB_SYS_COPYAREA
2295 select FB_SYS_IMAGEBLIT
2297 select FB_DEFERRED_IO
2298 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2299 select XEN_XENBUS_FRONTEND
2302 This driver implements the front-end of the Xen virtual
2303 frame buffer driver. It communicates with a back-end
2307 tristate "E-Ink Metronome/8track controller support"
2309 select FB_SYS_FILLRECT
2310 select FB_SYS_COPYAREA
2311 select FB_SYS_IMAGEBLIT
2313 select FB_DEFERRED_IO
2315 This driver implements support for the E-Ink Metronome
2316 controller. The pre-release name for this device was 8track
2317 and could also have been called by some vendors as PVI-nnnn.
2320 tristate "Fujitsu MB862xx GDC support"
2322 depends on PCI || (OF && PPC)
2323 select FB_CFB_FILLRECT
2324 select FB_CFB_COPYAREA
2325 select FB_CFB_IMAGEBLIT
2327 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2330 prompt "GDC variant"
2331 depends on FB_MB862XX
2333 config FB_MB862XX_PCI_GDC
2334 bool "Carmine/Coral-P(A) GDC"
2337 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2338 PCI graphics controller devices.
2340 config FB_MB862XX_LIME
2342 depends on OF && PPC
2343 select FB_FOREIGN_ENDIAN
2344 select FB_LITTLE_ENDIAN
2346 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2350 config FB_MB862XX_I2C
2351 bool "Support I2C bus on MB862XX GDC"
2352 depends on FB_MB862XX && I2C
2355 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2356 driver to support accessing I2C devices on controller's I2C bus.
2357 These are usually some video decoder chips.
2360 tristate "EP93XX frame buffer support"
2361 depends on FB && ARCH_EP93XX
2362 select FB_CFB_FILLRECT
2363 select FB_CFB_COPYAREA
2364 select FB_CFB_IMAGEBLIT
2366 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2367 This driver is also available as a module. The module will be called
2370 config FB_PRE_INIT_FB
2371 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2372 depends on FB && FB_MB862XX_LIME
2374 Select this option if display contents should be inherited as set by
2378 tristate "MSM Framebuffer support"
2379 depends on FB && ARCH_MSM
2380 select FB_CFB_FILLRECT
2381 select FB_CFB_COPYAREA
2382 select FB_CFB_IMAGEBLIT
2385 tristate "MX3 Framebuffer support"
2386 depends on FB && MX3_IPU
2387 select FB_CFB_FILLRECT
2388 select FB_CFB_COPYAREA
2389 select FB_CFB_IMAGEBLIT
2392 This is a framebuffer device for the i.MX31 LCD Controller. So
2393 far only synchronous displays are supported. If you plan to use
2394 an LCD display with your i.MX31 system, say Y here.
2396 config FB_BROADSHEET
2397 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2399 select FB_SYS_FILLRECT
2400 select FB_SYS_COPYAREA
2401 select FB_SYS_IMAGEBLIT
2403 select FB_DEFERRED_IO
2405 This driver implements support for the E-Ink Broadsheet
2406 controller. The release name for this device was Epson S1D13521
2407 and could also have been called by other names when coupled with
2411 tristate "AUO-K190X EPD controller support"
2413 select FB_SYS_FILLRECT
2414 select FB_SYS_COPYAREA
2415 select FB_SYS_IMAGEBLIT
2417 select FB_DEFERRED_IO
2419 Provides support for epaper controllers from the K190X series
2420 of AUO. These controllers can be used to drive epaper displays
2423 This option enables the common support, shared by the individual
2424 controller drivers. You will also have to enable the driver
2425 for the controller type used in your device.
2428 tristate "AUO-K1900 EPD controller support"
2429 depends on FB && FB_AUO_K190X
2431 This driver implements support for the AUO K1900 epd-controller.
2432 This controller can drive Sipix epaper displays but can only do
2433 serial updates, reducing the number of possible frames per second.
2436 tristate "AUO-K1901 EPD controller support"
2437 depends on FB && FB_AUO_K190X
2439 This driver implements support for the AUO K1901 epd-controller.
2440 This controller can drive Sipix epaper displays and supports
2441 concurrent updates, making higher frames per second possible.
2444 tristate "JZ4740 LCD framebuffer support"
2445 depends on FB && MACH_JZ4740
2446 select FB_SYS_FILLRECT
2447 select FB_SYS_COPYAREA
2448 select FB_SYS_IMAGEBLIT
2450 Framebuffer support for the JZ4740 SoC.
2453 tristate "MXS LCD framebuffer support"
2454 depends on FB && ARCH_MXS
2455 select FB_CFB_FILLRECT
2456 select FB_CFB_COPYAREA
2457 select FB_CFB_IMAGEBLIT
2458 select FB_MODE_HELPERS
2459 select VIDEOMODE_HELPERS
2461 Framebuffer support for the MXS SoC.
2463 config FB_PUV3_UNIGFX
2464 tristate "PKUnity v3 Unigfx framebuffer support"
2465 depends on FB && UNICORE32 && ARCH_PUV3
2466 select FB_SYS_FILLRECT
2467 select FB_SYS_COPYAREA
2468 select FB_SYS_IMAGEBLIT
2471 Choose this option if you want to use the Unigfx device as a
2472 framebuffer device. Without the support of PCI & AGP.
2475 tristate "Microsoft Hyper-V Synthetic Video support"
2476 depends on FB && HYPERV
2477 select FB_CFB_FILLRECT
2478 select FB_CFB_COPYAREA
2479 select FB_CFB_IMAGEBLIT
2481 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2484 bool "Simple framebuffer support"
2485 depends on (FB = y) && OF
2486 select FB_CFB_FILLRECT
2487 select FB_CFB_COPYAREA
2488 select FB_CFB_IMAGEBLIT
2490 Say Y if you want support for a simple frame-buffer.
2492 This driver assumes that the display hardware has been initialized
2493 before the kernel boots, and the kernel will simply render to the
2494 pre-allocated frame buffer surface.
2496 Configuration re: surface address, size, and format must be provided
2497 through device tree, or potentially plain old platform data in the
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"
2506 source "drivers/video/rockchip/Kconfig"
2509 source "drivers/video/console/Kconfig"
2512 if FB || SGI_NEWPORT_CONSOLE
2513 source "drivers/video/logo/Kconfig"
2516 config FB_SH_MOBILE_MERAM
2517 tristate "SuperH Mobile MERAM read ahead support"
2518 depends on (SUPERH || ARCH_SHMOBILE)
2519 select GENERIC_ALLOCATOR
2521 Enable MERAM support for the SuperH controller.
2523 This will allow for caching of the framebuffer to provide more
2524 reliable access under heavy main memory bus traffic situations.
2525 Up to 4 memory channels can be configured, allowing 4 RGB or
2526 2 YCbCr framebuffers to be configured.
2529 tristate "Solomon SSD1307 framebuffer support"
2530 depends on FB && I2C
2534 select FB_SYS_FILLRECT
2535 select FB_SYS_COPYAREA
2536 select FB_SYS_IMAGEBLIT
2537 select FB_DEFERRED_IO
2540 This driver implements support for the Solomon SSD1307
2541 OLED controller over I2C.