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"
30 config VIDEO_OUTPUT_CONTROL
31 tristate "Lowlevel video output switch controls"
33 This framework adds support for low-level control of the video
42 config OF_DISPLAY_TIMING
43 bool "Enable device tree display timing support"
47 helper to parse display timings from the devicetree
50 bool "Enable device tree videomode support"
53 select OF_DISPLAY_TIMING
55 helper to get videomodes from the devicetree
61 tristate "Support for frame buffer devices"
63 The frame buffer device provides an abstraction for the graphics
64 hardware. It represents the frame buffer of some video hardware and
65 allows application software to access the graphics hardware through
66 a well-defined interface, so the software doesn't need to know
67 anything about the low-level (hardware register) stuff.
69 Frame buffer devices work identically across the different
70 architectures supported by Linux and make the implementation of
71 application programs easier and more portable; at this point, an X
72 server exists which uses the frame buffer device exclusively.
73 On several non-X86 architectures, the frame buffer device is the
74 only way to use the graphics hardware.
76 The device is accessed through special device nodes, usually located
77 in the /dev directory, i.e. /dev/fb*.
79 You need an utility program called fbset to make full use of frame
80 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
81 and the Framebuffer-HOWTO at
82 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
85 Say Y here and to the driver for your graphics board below if you
86 are compiling a kernel for a non-x86 architecture.
88 If you are compiling for the x86 architecture, you can say Y if you
89 want to play with it, but it is not essential. Please note that
90 running graphical applications that directly touch the hardware
91 (e.g. an accelerated X server) and that are not frame buffer
92 device-aware may cause unexpected results. If unsure, say N.
95 bool "Enable firmware EDID"
99 This enables access to the EDID transferred from the firmware.
100 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
101 transfers do not work for your driver and if you are using
102 nvidiafb, i810fb or savagefb.
104 In general, choosing Y for this option is safe. If you
105 experience extremely long delays while booting before you get
106 something on your display, try setting this to N. Matrox cards in
107 combination with certain motherboards and monitors are known to
108 suffer from this problem.
117 config FB_BOOT_VESA_SUPPORT
122 If true, at least one selected framebuffer driver can take advantage
123 of VESA video modes set at an early boot stage via the vga= parameter.
125 config FB_CFB_FILLRECT
130 Include the cfb_fillrect function for generic software rectangle
131 filling. This is used by drivers that don't provide their own
132 (accelerated) version.
134 config FB_CFB_COPYAREA
139 Include the cfb_copyarea function for generic software area copying.
140 This is used by drivers that don't provide their own (accelerated)
143 config FB_CFB_IMAGEBLIT
148 Include the cfb_imageblit function for generic software image
149 blitting. This is used by drivers that don't provide their own
150 (accelerated) version.
152 config FB_CFB_REV_PIXELS_IN_BYTE
157 Allow generic frame-buffer functions to work on displays with 1, 2
158 and 4 bits per pixel depths which has opposite order of pixels in
159 byte order to bytes in long order.
161 config FB_SYS_FILLRECT
166 Include the sys_fillrect function for generic software rectangle
167 filling. This is used by drivers that don't provide their own
168 (accelerated) version and the framebuffer is in system RAM.
170 config FB_SYS_COPYAREA
175 Include the sys_copyarea function for generic software area copying.
176 This is used by drivers that don't provide their own (accelerated)
177 version and the framebuffer is in system RAM.
179 config FB_SYS_IMAGEBLIT
184 Include the sys_imageblit function for generic software image
185 blitting. This is used by drivers that don't provide their own
186 (accelerated) version and the framebuffer is in system RAM.
188 menuconfig FB_FOREIGN_ENDIAN
189 bool "Framebuffer foreign endianness support"
192 This menu will let you enable support for the framebuffers with
193 non-native endianness (e.g. Little-Endian framebuffer on a
194 Big-Endian machine). Most probably you don't have such hardware,
195 so it's safe to say "n" here.
198 prompt "Choice endianness support"
199 depends on FB_FOREIGN_ENDIAN
201 config FB_BOTH_ENDIAN
202 bool "Support for Big- and Little-Endian framebuffers"
205 bool "Support for Big-Endian framebuffers only"
207 config FB_LITTLE_ENDIAN
208 bool "Support for Little-Endian framebuffers only"
217 config FB_WMT_GE_ROPS
222 Include functions for accelerated rectangle filling and area
223 copying using WonderMedia Graphics Engine operations.
225 config FB_DEFERRED_IO
232 depends on FB_DEFERRED_IO
239 Common utility functions useful to fbdev drivers of VGA-based
250 select BACKLIGHT_LCD_SUPPORT
251 select BACKLIGHT_CLASS_DEVICE
254 config FB_MODE_HELPERS
255 bool "Enable Video Mode Handling Helpers"
259 This enables functions for handling video modes using the
260 Generalized Timing Formula and the EDID parser. A few drivers rely
261 on this feature such as the radeonfb, rivafb, and the i810fb. If
262 your driver does not take advantage of this feature, choosing Y will
263 just increase the kernel size by about 5K.
265 config FB_TILEBLITTING
266 bool "Enable Tile Blitting Support"
270 This enables tile blitting. Tile blitting is a drawing technique
271 where the screen is divided into rectangular sections (tiles), whereas
272 the standard blitting divides the screen into pixels. Because the
273 default drawing element is a tile, drawing functions will be passed
274 parameters in terms of number of tiles instead of number of pixels.
275 For example, to draw a single character, instead of using bitmaps,
276 an index to an array of bitmaps will be used. To clear or move a
277 rectangular section of a screen, the rectangle will be described in
278 terms of number of tiles in the x- and y-axis.
280 This is particularly important to one driver, matroxfb. If
283 comment "Frame buffer hardware drivers"
287 tristate "Aeroflex Gaisler framebuffer support"
288 depends on FB && SPARC
289 select FB_CFB_FILLRECT
290 select FB_CFB_COPYAREA
291 select FB_CFB_IMAGEBLIT
293 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
296 tristate "Cirrus Logic support"
297 depends on FB && (ZORRO || PCI)
298 select FB_CFB_FILLRECT
299 select FB_CFB_COPYAREA
300 select FB_CFB_IMAGEBLIT
302 This enables support for Cirrus Logic GD542x/543x based boards on
303 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
305 If you have a PCI-based system, this enables support for these
306 chips: GD-543x, GD-544x, GD-5480.
308 Please read the file <file:Documentation/fb/cirrusfb.txt>.
310 Say N unless you have such a graphics board or plan to get one
311 before you next recompile the kernel.
314 tristate "Permedia2 support"
315 depends on FB && ((AMIGA && BROKEN) || PCI)
316 select FB_CFB_FILLRECT
317 select FB_CFB_COPYAREA
318 select FB_CFB_IMAGEBLIT
320 This is the frame buffer device driver for cards based on
321 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
322 The driver was tested on the following cards:
323 Diamond FireGL 1000 PRO AGP
324 ELSA Gloria Synergy PCI
325 Appian Jeronimo PRO (both heads) PCI
326 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
327 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
328 ASK Graphic Blaster Exxtreme AGP
330 To compile this driver as a module, choose M here: the
331 module will be called pm2fb.
333 config FB_PM2_FIFO_DISCONNECT
334 bool "enable FIFO disconnect feature"
335 depends on FB_PM2 && PCI
337 Support the Permedia2 FIFO disconnect feature.
340 tristate "ARM PrimeCell PL110 support"
341 depends on FB && ARM && ARM_AMBA
342 select FB_CFB_FILLRECT
343 select FB_CFB_COPYAREA
344 select FB_CFB_IMAGEBLIT
346 This framebuffer device driver is for the ARM PrimeCell PL110
347 Colour LCD controller. ARM PrimeCells provide the building
348 blocks for System on a Chip devices.
350 If you want to compile this as a module (=code which can be
351 inserted into and removed from the running kernel), say M
352 here and read <file:Documentation/kbuild/modules.txt>. The module
353 will be called amba-clcd.
356 bool "Acorn VIDC support"
357 depends on (FB = y) && ARM && ARCH_ACORN
358 select FB_CFB_FILLRECT
359 select FB_CFB_COPYAREA
360 select FB_CFB_IMAGEBLIT
362 This is the frame buffer device driver for the Acorn VIDC graphics
363 hardware found in Acorn RISC PCs and other ARM-based machines. If
367 bool "CLPS711X LCD support"
368 depends on (FB = y) && ARM && ARCH_CLPS711X
369 select FB_CFB_FILLRECT
370 select FB_CFB_COPYAREA
371 select FB_CFB_IMAGEBLIT
373 Say Y to enable the Framebuffer driver for the CLPS7111 and
377 bool "SA-1100 LCD support"
378 depends on (FB = y) && ARM && ARCH_SA1100
379 select FB_CFB_FILLRECT
380 select FB_CFB_COPYAREA
381 select FB_CFB_IMAGEBLIT
383 This is a framebuffer device for the SA-1100 LCD Controller.
384 See <http://www.linux-fbdev.org/> for information on framebuffer
387 If you plan to use the LCD display with your SA-1100 system, say
391 tristate "Freescale i.MX1/21/25/27 LCD support"
392 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
393 select FB_CFB_FILLRECT
394 select FB_CFB_COPYAREA
395 select FB_CFB_IMAGEBLIT
398 tristate "CyberPro 2000/2010/5000 support"
399 depends on FB && PCI && (BROKEN || !SPARC64)
400 select FB_CFB_FILLRECT
401 select FB_CFB_COPYAREA
402 select FB_CFB_IMAGEBLIT
404 This enables support for the Integraphics CyberPro 20x0 and 5000
405 VGA chips used in the Rebel.com Netwinder and other machines.
406 Say Y if you have a NetWinder or a graphics card containing this
407 device, otherwise say N.
409 config FB_CYBER2000_DDC
410 bool "DDC for CyberPro support"
411 depends on FB_CYBER2000
415 Say Y here if you want DDC support for your CyberPro graphics
416 card. This is only I2C bus support, driver does not use EDID.
418 config FB_CYBER2000_I2C
419 bool "CyberPro 2000/2010/5000 I2C support"
420 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
423 Enable support for the I2C video decoder interface on the
424 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
425 on the Netwinder machines for the SAA7111 video capture.
429 depends on (FB = y) && APOLLO
431 select FB_CFB_FILLRECT
432 select FB_CFB_IMAGEBLIT
436 depends on (FB = y) && Q40
438 select FB_CFB_FILLRECT
439 select FB_CFB_COPYAREA
440 select FB_CFB_IMAGEBLIT
443 tristate "Amiga native chipset support"
444 depends on FB && AMIGA
446 This is the frame buffer device driver for the builtin graphics
447 chipset found in Amigas.
449 To compile this driver as a module, choose M here: the
450 module will be called amifb.
453 bool "Amiga OCS chipset support"
456 This enables support for the original Agnus and Denise video chips,
457 found in the Amiga 1000 and most A500's and A2000's. If you intend
458 to run Linux on any of these systems, say Y; otherwise say N.
461 bool "Amiga ECS chipset support"
464 This enables support for the Enhanced Chip Set, found in later
465 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
466 you intend to run Linux on any of these systems, say Y; otherwise
470 bool "Amiga AGA chipset support"
473 This enables support for the Advanced Graphics Architecture (also
474 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
475 and CD32. If you intend to run Linux on any of these systems, say Y;
479 bool "Amiga FrameMaster II/Rainbow II support"
480 depends on (FB = y) && ZORRO
481 select FB_CFB_FILLRECT
482 select FB_CFB_COPYAREA
483 select FB_CFB_IMAGEBLIT
485 This is the frame buffer device driver for the Amiga FrameMaster
486 card from BSC (exhibited 1992 but not shipped as a CBM product).
489 tristate "Arc Monochrome LCD board support"
491 select FB_SYS_FILLRECT
492 select FB_SYS_COPYAREA
493 select FB_SYS_IMAGEBLIT
496 This enables support for the Arc Monochrome LCD board. The board
497 is based on the KS-108 lcd controller and is typically a matrix
498 of 2*n chips. This driver was tested with a 128x64 panel. This
499 driver supports it for use with x86 SBCs through a 16 bit GPIO
500 interface (8 bit data, 8 bit control). If you anticipate using
501 this driver, say Y or M; otherwise say N. You must specify the
502 GPIO IO address to be used for setting control and data.
505 bool "Atari native chipset support"
506 depends on (FB = y) && ATARI
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
511 This is the frame buffer device driver for the builtin graphics
512 chipset found in Ataris.
515 bool "Open Firmware frame buffer device support"
516 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
517 select FB_CFB_FILLRECT
518 select FB_CFB_COPYAREA
519 select FB_CFB_IMAGEBLIT
522 Say Y if you want support with Open Firmware for your graphics
526 bool "Apple \"control\" display support"
527 depends on (FB = y) && PPC_PMAC && PPC32
528 select FB_CFB_FILLRECT
529 select FB_CFB_COPYAREA
530 select FB_CFB_IMAGEBLIT
533 This driver supports a frame buffer for the graphics adapter in the
534 Power Macintosh 7300 and others.
537 bool "Apple \"platinum\" display support"
538 depends on (FB = y) && PPC_PMAC && PPC32
539 select FB_CFB_FILLRECT
540 select FB_CFB_COPYAREA
541 select FB_CFB_IMAGEBLIT
544 This driver supports a frame buffer for the "platinum" graphics
545 adapter in some Power Macintoshes.
548 bool "Apple \"valkyrie\" display support"
549 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
550 select FB_CFB_FILLRECT
551 select FB_CFB_COPYAREA
552 select FB_CFB_IMAGEBLIT
555 This driver supports a frame buffer for the "valkyrie" graphics
556 adapter in some Power Macintoshes.
559 bool "Chips 65550 display support"
560 depends on (FB = y) && PPC32 && PCI
561 select FB_CFB_FILLRECT
562 select FB_CFB_COPYAREA
563 select FB_CFB_IMAGEBLIT
565 This is the frame buffer device driver for the Chips & Technologies
566 65550 graphics chip in PowerBooks.
569 bool "Asiliant (Chips) 69000 display support"
570 depends on (FB = y) && PCI
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 This is the frame buffer device driver for the Asiliant 69030 chipset
578 bool "IMS Twin Turbo display support"
579 depends on (FB = y) && PCI
580 select FB_CFB_IMAGEBLIT
581 select FB_MACMODES if PPC
583 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
584 many Macintosh and compatible computers.
587 tristate "VGA 16-color graphics support"
588 depends on FB && (X86 || PPC)
589 select FB_CFB_FILLRECT
590 select FB_CFB_COPYAREA
591 select FB_CFB_IMAGEBLIT
593 select FONT_8x16 if FRAMEBUFFER_CONSOLE
595 This is the frame buffer device driver for VGA 16 color graphic
596 cards. Say Y if you have such a card.
598 To compile this driver as a module, choose M here: the
599 module will be called vga16fb.
601 config FB_BF54X_LQ043
602 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
603 depends on FB && (BF54x) && !BF542
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
610 config FB_BFIN_T350MCQB
611 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
612 depends on FB && BLACKFIN
614 select FB_CFB_FILLRECT
615 select FB_CFB_COPYAREA
616 select FB_CFB_IMAGEBLIT
618 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
619 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
620 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
622 config FB_BFIN_LQ035Q1
623 tristate "SHARP LQ035Q1DH02 TFT LCD"
624 depends on FB && BLACKFIN && SPI
625 select FB_CFB_FILLRECT
626 select FB_CFB_COPYAREA
627 select FB_CFB_IMAGEBLIT
630 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
631 the Blackfin Landscape LCD EZ-Extender Card.
632 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
633 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
635 To compile this driver as a module, choose M here: the
636 module will be called bfin-lq035q1-fb.
638 config FB_BF537_LQ035
639 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
640 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
641 select FB_CFB_FILLRECT
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
646 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
649 To compile this driver as a module, choose M here: the
650 module will be called bf537-lq035.
653 tristate "Blackfin ADV7393 Video encoder"
654 depends on FB && BLACKFIN
656 select FB_CFB_FILLRECT
657 select FB_CFB_COPYAREA
658 select FB_CFB_IMAGEBLIT
660 This is the framebuffer device for a ADV7393 video encoder
661 attached to a Blackfin on the PPI port.
662 If your Blackfin board has a ADV7393 select Y.
664 To compile this driver as a module, choose M here: the
665 module will be called bfin_adv7393fb.
668 prompt "Video mode support"
669 depends on FB_BFIN_7393
679 bool 'NTSC 640x480 (Experimental)'
682 bool 'PAL 640x480 (Experimental)'
685 bool 'NTSC 720x480 YCbCR input'
688 bool 'PAL 720x576 YCbCR input'
693 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
694 depends on (FB_BFIN_7393)
695 default ADV7393_1XMEM
705 tristate "HP STI frame buffer device support"
706 depends on FB && PARISC
707 select FB_CFB_FILLRECT
708 select FB_CFB_COPYAREA
709 select FB_CFB_IMAGEBLIT
714 STI refers to the HP "Standard Text Interface" which is a set of
715 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
716 Enabling this option will implement the linux framebuffer device
717 using calls to the STI BIOS routines for initialisation.
719 If you enable this option, you will get a planar framebuffer device
720 /dev/fb which will work on the most common HP graphic cards of the
721 NGLE family, including the artist chips (in the 7xx and Bxxx series),
722 HCRX, HCRX24, CRX, CRX24 and VisEG series.
724 It is safe to enable this option, so you should probably say "Y".
727 bool "Generic Macintosh display support"
728 depends on (FB = y) && MAC
729 select FB_CFB_FILLRECT
730 select FB_CFB_COPYAREA
731 select FB_CFB_IMAGEBLIT
736 depends on (FB = y) && DIO
737 select FB_CFB_IMAGEBLIT
741 tristate "TGA/SFB+ framebuffer support"
742 depends on FB && (ALPHA || TC)
743 select FB_CFB_FILLRECT
744 select FB_CFB_COPYAREA
745 select FB_CFB_IMAGEBLIT
748 This is the frame buffer device driver for generic TGA and SFB+
749 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
750 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
751 TURBOchannel cards, also known as PMAGD-A, -B and -C.
753 Due to hardware limitations ZLX-E2 and E3 cards are not supported
754 for DECstation 5000/200 systems. Additionally due to firmware
755 limitations these cards may cause troubles with booting DECstation
756 5000/240 and /260 systems, but are fully supported under Linux if
757 you manage to get it going. ;-)
759 Say Y if you have one of those.
762 tristate "Userspace VESA VGA graphics support"
763 depends on FB && CONNECTOR
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
767 select FB_MODE_HELPERS
769 This is the frame buffer driver for generic VBE 2.0 compliant
770 graphic cards. It can also take advantage of VBE 3.0 features,
771 such as refresh rate adjustment.
773 This driver generally provides more features than vesafb but
774 requires a userspace helper application called 'v86d'. See
775 <file:Documentation/fb/uvesafb.txt> for more information.
780 bool "VESA VGA graphics support"
781 depends on (FB = y) && X86
782 select FB_CFB_FILLRECT
783 select FB_CFB_COPYAREA
784 select FB_CFB_IMAGEBLIT
785 select FB_BOOT_VESA_SUPPORT
787 This is the frame buffer device driver for generic VESA 2.0
788 compliant graphic cards. The older VESA 1.2 cards are not supported.
789 You will get a boot time penguin logo at no additional cost. Please
790 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
793 bool "EFI-based Framebuffer Support"
794 depends on (FB = y) && X86 && EFI
795 select FB_CFB_FILLRECT
796 select FB_CFB_COPYAREA
797 select FB_CFB_IMAGEBLIT
799 This is the EFI frame buffer device driver. If the firmware on
800 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
801 using the EFI framebuffer as your console.
804 tristate "N411 Apollo/Hecuba devkit support"
805 depends on FB && X86 && MMU
806 select FB_SYS_FILLRECT
807 select FB_SYS_COPYAREA
808 select FB_SYS_IMAGEBLIT
810 select FB_DEFERRED_IO
813 This enables support for the Apollo display controller in its
814 Hecuba form using the n411 devkit.
817 tristate "Hercules mono graphics support"
820 Say Y here if you have a Hercules mono graphics card.
822 To compile this driver as a module, choose M here: the
823 module will be called hgafb.
825 As this card technology is at least 25 years old,
826 most people will answer N here.
829 tristate "SGI Visual Workstation framebuffer support"
830 depends on FB && X86_VISWS
831 select FB_CFB_FILLRECT
832 select FB_CFB_COPYAREA
833 select FB_CFB_IMAGEBLIT
835 SGI Visual Workstation support for framebuffer graphics.
838 bool "SGI Graphics Backend frame buffer support"
839 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
840 select FB_CFB_FILLRECT
841 select FB_CFB_COPYAREA
842 select FB_CFB_IMAGEBLIT
844 This is the frame buffer device driver for SGI Graphics Backend.
845 This chip is used in SGI O2 and Visual Workstation 320/540.
848 int "Video memory size in MB"
852 This is the amount of memory reserved for the framebuffer,
853 which can be any value between 1MB and 8MB.
856 bool "SBUS and UPA framebuffers"
857 depends on (FB = y) && SPARC
859 Say Y if you want support for SBUS or UPA based frame buffer device.
863 depends on (FB = y) && (SPARC && FB_SBUS)
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This is the frame buffer device driver for the BWtwo frame buffer.
871 bool "CGthree support"
872 depends on (FB = y) && (SPARC && FB_SBUS)
873 select FB_CFB_FILLRECT
874 select FB_CFB_COPYAREA
875 select FB_CFB_IMAGEBLIT
877 This is the frame buffer device driver for the CGthree frame buffer.
880 bool "CGsix (GX,TurboGX) support"
881 depends on (FB = y) && (SPARC && FB_SBUS)
882 select FB_CFB_COPYAREA
883 select FB_CFB_IMAGEBLIT
885 This is the frame buffer device driver for the CGsix (GX, TurboGX)
889 bool "Creator/Creator3D/Elite3D support"
890 depends on FB_SBUS && SPARC64
891 select FB_CFB_COPYAREA
892 select FB_CFB_IMAGEBLIT
894 This is the frame buffer device driver for the Creator, Creator3D,
895 and Elite3D graphics boards.
898 bool "TCX (SS4/SS5 only) support"
900 select FB_CFB_FILLRECT
901 select FB_CFB_COPYAREA
902 select FB_CFB_IMAGEBLIT
904 This is the frame buffer device driver for the TCX 24/8bit frame
908 bool "CGfourteen (SX) support"
910 select FB_CFB_FILLRECT
911 select FB_CFB_COPYAREA
912 select FB_CFB_IMAGEBLIT
914 This is the frame buffer device driver for the CGfourteen frame
915 buffer on Desktop SPARCsystems with the SX graphics option.
918 bool "P9100 (Sparcbook 3 only) support"
920 select FB_CFB_FILLRECT
921 select FB_CFB_COPYAREA
922 select FB_CFB_IMAGEBLIT
924 This is the frame buffer device driver for the P9100 card
925 supported on Sparcbook 3 machines.
928 bool "Leo (ZX) support"
930 select FB_CFB_FILLRECT
931 select FB_CFB_COPYAREA
932 select FB_CFB_IMAGEBLIT
934 This is the frame buffer device driver for the SBUS-based Sun ZX
935 (leo) frame buffer cards.
938 bool "IGA 168x display support"
939 depends on (FB = y) && SPARC32
940 select FB_CFB_FILLRECT
941 select FB_CFB_COPYAREA
942 select FB_CFB_IMAGEBLIT
944 This is the framebuffer device for the INTERGRAPHICS 1680 and
945 successor frame buffer cards.
948 bool "Sun XVR-500 3DLABS Wildcat support"
949 depends on (FB = y) && PCI && SPARC64
950 select FB_CFB_FILLRECT
951 select FB_CFB_COPYAREA
952 select FB_CFB_IMAGEBLIT
954 This is the framebuffer device for the Sun XVR-500 and similar
955 graphics cards based upon the 3DLABS Wildcat chipset. The driver
956 only works on sparc64 systems where the system firmware has
957 mostly initialized the card already. It is treated as a
958 completely dumb framebuffer device.
961 bool "Sun XVR-2500 3DLABS Wildcat support"
962 depends on (FB = y) && PCI && SPARC64
963 select FB_CFB_FILLRECT
964 select FB_CFB_COPYAREA
965 select FB_CFB_IMAGEBLIT
967 This is the framebuffer device for the Sun XVR-2500 and similar
968 graphics cards based upon the 3DLABS Wildcat chipset. The driver
969 only works on sparc64 systems where the system firmware has
970 mostly initialized the card already. It is treated as a
971 completely dumb framebuffer device.
974 bool "Sun XVR-1000 support"
975 depends on (FB = y) && SPARC64
976 select FB_CFB_FILLRECT
977 select FB_CFB_COPYAREA
978 select FB_CFB_IMAGEBLIT
980 This is the framebuffer device for the Sun XVR-1000 and similar
981 graphics cards. The driver only works on sparc64 systems where
982 the system firmware has mostly initialized the card already. It
983 is treated as a completely dumb framebuffer device.
986 tristate "NEC PowerVR 2 display support"
987 depends on FB && SH_DREAMCAST
988 select FB_CFB_FILLRECT
989 select FB_CFB_COPYAREA
990 select FB_CFB_IMAGEBLIT
992 Say Y here if you have a PowerVR 2 card in your box. If you plan to
993 run linux on your Dreamcast, you will have to say Y here.
994 This driver may or may not work on other PowerVR 2 cards, but is
995 totally untested. Use at your own risk. If unsure, say N.
997 To compile this driver as a module, choose M here: the
998 module will be called pvr2fb.
1000 You can pass several parameters to the driver at boot time or at
1001 module load time. The parameters look like "video=pvr2:XXX", where
1002 the meaning of XXX can be found at the end of the main source file
1003 (<file:drivers/video/pvr2fb.c>). Please see the file
1004 <file:Documentation/fb/pvr2fb.txt>.
1007 tristate "Epson S1D13XXX framebuffer support"
1009 select FB_CFB_FILLRECT
1010 select FB_CFB_COPYAREA
1011 select FB_CFB_IMAGEBLIT
1013 Support for S1D13XXX framebuffer device family (currently only
1014 working with S1D13806). Product specs at
1015 <http://vdc.epson.com/>
1018 tristate "AT91/AT32 LCD Controller support"
1019 depends on FB && HAVE_FB_ATMEL
1020 select FB_CFB_FILLRECT
1021 select FB_CFB_COPYAREA
1022 select FB_CFB_IMAGEBLIT
1024 This enables support for the AT91/AT32 LCD Controller.
1027 bool "Frame Buffer in internal SRAM"
1028 depends on FB_ATMEL && ARCH_AT91SAM9261
1030 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1031 to let frame buffer in external SDRAM.
1034 bool "Use a STN display with AT91/AT32 LCD Controller"
1035 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1038 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1039 Controller. Say N if you want to connect a TFT.
1044 tristate "nVidia Framebuffer Support"
1045 depends on FB && PCI
1046 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1047 select FB_MODE_HELPERS
1048 select FB_CFB_FILLRECT
1049 select FB_CFB_COPYAREA
1050 select FB_CFB_IMAGEBLIT
1054 This driver supports graphics boards with the nVidia chips, TNT
1055 and newer. For very old chipsets, such as the RIVA128, then use
1057 Say Y if you have such a graphics board.
1059 To compile this driver as a module, choose M here: the
1060 module will be called nvidiafb.
1062 config FB_NVIDIA_I2C
1063 bool "Enable DDC Support"
1064 depends on FB_NVIDIA
1067 This enables I2C support for nVidia Chipsets. This is used
1068 only for getting EDID information from the attached display
1069 allowing for robust video mode handling and switching.
1071 Because fbdev-2.6 requires that drivers must be able to
1072 independently validate video mode parameters, you should say Y
1075 config FB_NVIDIA_DEBUG
1076 bool "Lots of debug output"
1077 depends on FB_NVIDIA
1080 Say Y here if you want the nVidia driver to output all sorts
1081 of debugging information to provide to the maintainer when
1082 something goes wrong.
1084 config FB_NVIDIA_BACKLIGHT
1085 bool "Support for backlight control"
1086 depends on FB_NVIDIA
1089 Say Y here if you want to control the backlight of your display.
1092 tristate "nVidia Riva support"
1093 depends on FB && PCI
1094 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1095 select FB_MODE_HELPERS
1096 select FB_CFB_FILLRECT
1097 select FB_CFB_COPYAREA
1098 select FB_CFB_IMAGEBLIT
1102 This driver supports graphics boards with the nVidia Riva/Geforce
1104 Say Y if you have such a graphics board.
1106 To compile this driver as a module, choose M here: the
1107 module will be called rivafb.
1110 bool "Enable DDC Support"
1114 This enables I2C support for nVidia Chipsets. This is used
1115 only for getting EDID information from the attached display
1116 allowing for robust video mode handling and switching.
1118 Because fbdev-2.6 requires that drivers must be able to
1119 independently validate video mode parameters, you should say Y
1122 config FB_RIVA_DEBUG
1123 bool "Lots of debug output"
1127 Say Y here if you want the Riva driver to output all sorts
1128 of debugging information to provide to the maintainer when
1129 something goes wrong.
1131 config FB_RIVA_BACKLIGHT
1132 bool "Support for backlight control"
1136 Say Y here if you want to control the backlight of your display.
1139 tristate "Intel740 support"
1140 depends on FB && PCI
1141 select FB_MODE_HELPERS
1142 select FB_CFB_FILLRECT
1143 select FB_CFB_COPYAREA
1144 select FB_CFB_IMAGEBLIT
1148 This driver supports graphics cards based on Intel740 chip.
1151 tristate "Intel 810/815 support"
1152 depends on FB && PCI && X86_32 && AGP_INTEL
1153 select FB_MODE_HELPERS
1154 select FB_CFB_FILLRECT
1155 select FB_CFB_COPYAREA
1156 select FB_CFB_IMAGEBLIT
1159 This driver supports the on-board graphics built in to the Intel 810
1160 and 815 chipsets. Say Y if you have and plan to use such a board.
1162 To compile this driver as a module, choose M here: the
1163 module will be called i810fb.
1165 For more information, please read
1166 <file:Documentation/fb/intel810.txt>
1169 bool "use VESA Generalized Timing Formula"
1172 If you say Y, then the VESA standard, Generalized Timing Formula
1173 or GTF, will be used to calculate the required video timing values
1174 per video mode. Since the GTF allows nondiscrete timings
1175 (nondiscrete being a range of values as opposed to discrete being a
1176 set of values), you'll be able to use any combination of horizontal
1177 and vertical resolutions, and vertical refresh rates without having
1178 to specify your own timing parameters. This is especially useful
1179 to maximize the performance of an aging display, or if you just
1180 have a display with nonstandard dimensions. A VESA compliant
1181 monitor is recommended, but can still work with non-compliant ones.
1182 If you need or want this, then select this option. The timings may
1183 not be compliant with Intel's recommended values. Use at your own
1186 If you say N, the driver will revert to discrete video timings
1187 using a set recommended by Intel in their documentation.
1192 bool "Enable DDC Support"
1193 depends on FB_I810 && FB_I810_GTF
1198 tristate "Intel LE80578 (Vermilion) support"
1199 depends on FB && PCI && X86
1200 select FB_MODE_HELPERS
1201 select FB_CFB_FILLRECT
1202 select FB_CFB_COPYAREA
1203 select FB_CFB_IMAGEBLIT
1205 This driver supports the LE80578 (Vermilion Range) chipset
1207 config FB_CARILLO_RANCH
1208 tristate "Intel Carillo Ranch support"
1209 depends on FB_LE80578 && FB && PCI && X86
1211 This driver supports the LE80578 (Carillo Ranch) board
1214 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1215 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1216 select FB_MODE_HELPERS
1217 select FB_CFB_FILLRECT
1218 select FB_CFB_COPYAREA
1219 select FB_CFB_IMAGEBLIT
1220 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1221 depends on !DRM_I915
1223 This driver supports the on-board graphics built in to the Intel
1224 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1225 Say Y if you have and plan to use such a board.
1227 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1229 To compile this driver as a module, choose M here: the
1230 module will be called intelfb.
1232 For more information, please read <file:Documentation/fb/intelfb.txt>
1234 config FB_INTEL_DEBUG
1235 bool "Intel driver Debug Messages"
1238 Say Y here if you want the Intel driver to output all sorts
1239 of debugging information to provide to the maintainer when
1240 something goes wrong.
1243 bool "DDC/I2C for Intel framebuffer support"
1248 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1251 tristate "Matrox acceleration"
1252 depends on FB && PCI
1253 select FB_CFB_FILLRECT
1254 select FB_CFB_COPYAREA
1255 select FB_CFB_IMAGEBLIT
1256 select FB_TILEBLITTING
1257 select FB_MACMODES if PPC_PMAC
1259 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1260 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1261 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1262 Matrox G400, G450 or G550 card in your box.
1264 To compile this driver as a module, choose M here: the
1265 module will be called matroxfb.
1267 You can pass several parameters to the driver at boot time or at
1268 module load time. The parameters look like "video=matroxfb:XXX", and
1269 are described in <file:Documentation/fb/matroxfb.txt>.
1271 config FB_MATROX_MILLENIUM
1272 bool "Millennium I/II support"
1273 depends on FB_MATROX
1275 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1276 video card. If you select "Advanced lowlevel driver options" below,
1277 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1278 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1279 also use font widths different from 8.
1281 config FB_MATROX_MYSTIQUE
1282 bool "Mystique support"
1283 depends on FB_MATROX
1285 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1286 video card. If you select "Advanced lowlevel driver options" below,
1287 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1288 packed pixel and 32 bpp packed pixel. You can also use font widths
1292 bool "G100/G200/G400/G450/G550 support"
1293 depends on FB_MATROX
1295 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1296 video card. If you select "Advanced lowlevel driver options", you
1297 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1298 pixel and 32 bpp packed pixel. You can also use font widths
1301 If you need support for G400 secondary head, you must say Y to
1302 "Matrox I2C support" and "G400 second head support" right below.
1303 G450/G550 secondary head and digital output are supported without
1306 The driver starts in monitor mode. You must use the matroxset tool
1307 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1308 swap primary and secondary head outputs, or to change output mode.
1309 Secondary head driver always start in 640x480 resolution and you
1310 must use fbset to change it.
1312 Do not forget that second head supports only 16 and 32 bpp
1313 packed pixels, so it is a good idea to compile them into the kernel
1314 too. You can use only some font widths, as the driver uses generic
1315 painting procedures (the secondary head does not use acceleration
1318 G450/G550 hardware can display TV picture only from secondary CRTC,
1319 and it performs no scaling, so picture must have 525 or 625 lines.
1321 config FB_MATROX_I2C
1322 tristate "Matrox I2C support"
1323 depends on FB_MATROX
1326 This drivers creates I2C buses which are needed for accessing the
1327 DDC (I2C) bus present on all Matroxes, an I2C bus which
1328 interconnects Matrox optional devices, like MGA-TVO on G200 and
1329 G400, and the secondary head DDC bus, present on G400 only.
1331 You can say Y or M here if you want to experiment with monitor
1332 detection code. You must say Y or M here if you want to use either
1333 second head of G400 or MGA-TVO on G200 or G400.
1335 If you compile it as module, it will create a module named
1338 config FB_MATROX_MAVEN
1339 tristate "G400 second head support"
1340 depends on FB_MATROX_G && FB_MATROX_I2C
1342 WARNING !!! This support does not work with G450 !!!
1344 Say Y or M here if you want to use a secondary head (meaning two
1345 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1346 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1347 secondary head output is blanked while you are in X. With XFree
1348 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1349 the fbdev driver on first head and the fbdev driver on second head.
1351 If you compile it as module, two modules are created,
1352 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1353 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1354 also load i2c-matroxfb to get it to run.
1356 The driver starts in monitor mode and you must use the matroxset
1358 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1359 PAL or NTSC or to swap primary and secondary head outputs.
1360 Secondary head driver also always start in 640x480 resolution, you
1361 must use fbset to change it.
1363 Also do not forget that second head supports only 16 and 32 bpp
1364 packed pixels, so it is a good idea to compile them into the kernel
1365 too. You can use only some font widths, as the driver uses generic
1366 painting procedures (the secondary head does not use acceleration
1370 tristate "ATI Radeon display support"
1371 depends on FB && PCI
1372 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1373 select FB_MODE_HELPERS
1374 select FB_CFB_FILLRECT
1375 select FB_CFB_COPYAREA
1376 select FB_CFB_IMAGEBLIT
1377 select FB_MACMODES if PPC_OF
1379 Choose this option if you want to use an ATI Radeon graphics card as
1380 a framebuffer device. There are both PCI and AGP versions. You
1381 don't need to choose this to run the Radeon in plain VGA mode.
1383 There is a product page at
1384 http://products.amd.com/en-us/GraphicCardResult.aspx
1386 config FB_RADEON_I2C
1387 bool "DDC/I2C for ATI Radeon support"
1388 depends on FB_RADEON
1392 Say Y here if you want DDC/I2C support for your Radeon board.
1394 config FB_RADEON_BACKLIGHT
1395 bool "Support for backlight control"
1396 depends on FB_RADEON
1399 Say Y here if you want to control the backlight of your display.
1401 config FB_RADEON_DEBUG
1402 bool "Lots of debug output from Radeon driver"
1403 depends on FB_RADEON
1406 Say Y here if you want the Radeon driver to output all sorts
1407 of debugging information to provide to the maintainer when
1408 something goes wrong.
1411 tristate "ATI Rage128 display support"
1412 depends on FB && PCI
1413 select FB_CFB_FILLRECT
1414 select FB_CFB_COPYAREA
1415 select FB_CFB_IMAGEBLIT
1416 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1417 select FB_MACMODES if PPC_PMAC
1419 This driver supports graphics boards with the ATI Rage128 chips.
1420 Say Y if you have such a graphics board and read
1421 <file:Documentation/fb/aty128fb.txt>.
1423 To compile this driver as a module, choose M here: the
1424 module will be called aty128fb.
1426 config FB_ATY128_BACKLIGHT
1427 bool "Support for backlight control"
1428 depends on FB_ATY128
1431 Say Y here if you want to control the backlight of your display.
1434 tristate "ATI Mach64 display support" if PCI || ATARI
1435 depends on FB && !SPARC32
1436 select FB_CFB_FILLRECT
1437 select FB_CFB_COPYAREA
1438 select FB_CFB_IMAGEBLIT
1439 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1440 select FB_MACMODES if PPC
1442 This driver supports graphics boards with the ATI Mach64 chips.
1443 Say Y if you have such a graphics board.
1445 To compile this driver as a module, choose M here: the
1446 module will be called atyfb.
1449 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1450 depends on PCI && FB_ATY
1451 default y if SPARC64 && PCI
1453 Say Y here to support use of ATI's 64-bit Rage boards (or other
1454 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1455 framebuffer device. The ATI product support page for these boards
1456 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1458 config FB_ATY_GENERIC_LCD
1459 bool "Mach64 generic LCD support"
1460 depends on FB_ATY_CT
1462 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1463 Rage XC, or Rage XL chipset.
1466 bool "Mach64 GX support" if PCI
1470 Say Y here to support use of the ATI Mach64 Graphics Expression
1471 board (or other boards based on the Mach64 GX chipset) as a
1472 framebuffer device. The ATI product support page for these boards
1474 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1476 config FB_ATY_BACKLIGHT
1477 bool "Support for backlight control"
1481 Say Y here if you want to control the backlight of your display.
1484 tristate "S3 Trio/Virge support"
1485 depends on FB && PCI
1486 select FB_CFB_FILLRECT
1487 select FB_CFB_COPYAREA
1488 select FB_CFB_IMAGEBLIT
1489 select FB_TILEBLITTING
1492 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1494 Driver for graphics boards with S3 Trio / S3 Virge chip.
1497 bool "DDC for S3 support"
1502 Say Y here if you want DDC support for your S3 graphics card.
1505 tristate "S3 Savage support"
1506 depends on FB && PCI
1507 select FB_MODE_HELPERS
1508 select FB_CFB_FILLRECT
1509 select FB_CFB_COPYAREA
1510 select FB_CFB_IMAGEBLIT
1513 This driver supports notebooks and computers with S3 Savage PCI/AGP
1516 Say Y if you have such a graphics card.
1518 To compile this driver as a module, choose M here; the module
1519 will be called savagefb.
1521 config FB_SAVAGE_I2C
1522 bool "Enable DDC2 Support"
1523 depends on FB_SAVAGE
1526 This enables I2C support for S3 Savage Chipsets. This is used
1527 only for getting EDID information from the attached display
1528 allowing for robust video mode handling and switching.
1530 Because fbdev-2.6 requires that drivers must be able to
1531 independently validate video mode parameters, you should say Y
1534 config FB_SAVAGE_ACCEL
1535 bool "Enable Console Acceleration"
1536 depends on FB_SAVAGE
1539 This option will compile in console acceleration support. If
1540 the resulting framebuffer console has bothersome glitches, then
1544 tristate "SiS/XGI display support"
1545 depends on FB && PCI
1546 select FB_CFB_FILLRECT
1547 select FB_CFB_COPYAREA
1548 select FB_CFB_IMAGEBLIT
1549 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1551 This is the frame buffer device driver for the SiS 300, 315, 330
1552 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1553 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1555 To compile this driver as a module, choose M here; the module
1556 will be called sisfb.
1559 bool "SiS 300 series support"
1562 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1565 bool "SiS 315/330/340 series and XGI support"
1568 Say Y here to support use of the SiS 315, 330 and 340 series
1569 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1570 as XGI V3XT, V5, V8 and Z7.
1573 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1574 depends on FB && PCI && X86
1575 select FB_CFB_FILLRECT
1576 select FB_CFB_COPYAREA
1577 select FB_CFB_IMAGEBLIT
1582 This is the frame buffer device driver for Graphics chips of VIA
1583 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1584 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1586 Say Y if you have a VIA UniChrome graphics board.
1588 To compile this driver as a module, choose M here: the
1589 module will be called viafb.
1593 config FB_VIA_DIRECT_PROCFS
1594 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1598 Allow direct hardware access to some output registers via procfs.
1599 This is dangerous but may provide the only chance to get the
1600 correct output device configuration.
1601 Its use is strongly discouraged.
1603 config FB_VIA_X_COMPATIBILITY
1604 bool "X server compatibility"
1608 This option reduces the functionality (power saving, ...) of the
1609 framebuffer to avoid negative impact on the OpenChrome X server.
1610 If you use any X server other than fbdev you should enable this
1611 otherwise it should be safe to disable it and allow using all
1617 tristate "NeoMagic display support"
1618 depends on FB && PCI
1619 select FB_MODE_HELPERS
1620 select FB_CFB_FILLRECT
1621 select FB_CFB_COPYAREA
1622 select FB_CFB_IMAGEBLIT
1625 This driver supports notebooks with NeoMagic PCI chips.
1626 Say Y if you have such a graphics card.
1628 To compile this driver as a module, choose M here: the
1629 module will be called neofb.
1632 tristate "IMG Kyro support"
1633 depends on FB && PCI
1634 select FB_CFB_FILLRECT
1635 select FB_CFB_COPYAREA
1636 select FB_CFB_IMAGEBLIT
1638 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1641 To compile this driver as a module, choose M here: the
1642 module will be called kyrofb.
1645 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1646 depends on FB && PCI
1647 select FB_CFB_IMAGEBLIT
1648 select FB_CFB_FILLRECT
1649 select FB_CFB_COPYAREA
1650 select FB_MODE_HELPERS
1652 This driver supports graphics boards with the 3Dfx Banshee,
1653 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1654 such a graphics board.
1656 To compile this driver as a module, choose M here: the
1657 module will be called tdfxfb.
1659 config FB_3DFX_ACCEL
1660 bool "3Dfx Acceleration functions"
1663 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1664 device driver with acceleration functions.
1667 bool "Enable DDC/I2C support"
1672 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1675 tristate "3Dfx Voodoo Graphics (sst1) support"
1676 depends on FB && PCI
1677 select FB_CFB_FILLRECT
1678 select FB_CFB_COPYAREA
1679 select FB_CFB_IMAGEBLIT
1681 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1682 Voodoo2 (cvg) based graphics card.
1684 To compile this driver as a module, choose M here: the
1685 module will be called sstfb.
1687 WARNING: Do not use any application that uses the 3D engine
1688 (namely glide) while using this driver.
1689 Please read the <file:Documentation/fb/sstfb.txt> for supported
1690 options and other important info support.
1693 tristate "VIA VT8623 support"
1694 depends on FB && PCI
1695 select FB_CFB_FILLRECT
1696 select FB_CFB_COPYAREA
1697 select FB_CFB_IMAGEBLIT
1698 select FB_TILEBLITTING
1701 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1703 Driver for CastleRock integrated graphics core in the
1704 VIA VT8623 [Apollo CLE266] chipset.
1707 tristate "Trident/CyberXXX/CyberBlade support"
1708 depends on FB && PCI
1709 select FB_CFB_FILLRECT
1710 select FB_CFB_COPYAREA
1711 select FB_CFB_IMAGEBLIT
1713 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1714 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1716 There are also integrated versions of these chips called CyberXXXX,
1717 CyberImage or CyberBlade. These chips are mostly found in laptops
1718 but also on some motherboards including early VIA EPIA motherboards.
1719 For more information, read <file:Documentation/fb/tridentfb.txt>
1721 Say Y if you have such a graphics board.
1723 To compile this driver as a module, choose M here: the
1724 module will be called tridentfb.
1727 tristate "ARK 2000PV support"
1728 depends on FB && PCI
1729 select FB_CFB_FILLRECT
1730 select FB_CFB_COPYAREA
1731 select FB_CFB_IMAGEBLIT
1732 select FB_TILEBLITTING
1735 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1737 Driver for PCI graphics boards with ARK 2000PV chip
1738 and ICS 5342 RAMDAC.
1741 tristate "Permedia3 support"
1742 depends on FB && PCI
1743 select FB_CFB_FILLRECT
1744 select FB_CFB_COPYAREA
1745 select FB_CFB_IMAGEBLIT
1747 This is the frame buffer device driver for the 3DLabs Permedia3
1748 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1749 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1750 and maybe other boards.
1753 tristate "Fujitsu carmine frame buffer support"
1754 depends on FB && PCI
1755 select FB_CFB_FILLRECT
1756 select FB_CFB_COPYAREA
1757 select FB_CFB_IMAGEBLIT
1759 This is the frame buffer device driver for the Fujitsu Carmine chip.
1760 The driver provides two independent frame buffer devices.
1763 depends on FB_CARMINE
1764 prompt "DRAM timing"
1765 default FB_CARMINE_DRAM_EVAL
1767 config FB_CARMINE_DRAM_EVAL
1768 bool "Eval board timings"
1770 Use timings which work on the eval card.
1772 config CARMINE_DRAM_CUSTOM
1773 bool "Custom board timings"
1775 Use custom board timings.
1779 bool "Au1100 LCD Driver"
1780 depends on (FB = y) && MIPS_ALCHEMY
1781 select FB_CFB_FILLRECT
1782 select FB_CFB_COPYAREA
1783 select FB_CFB_IMAGEBLIT
1785 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1786 various panels and CRTs by passing in kernel cmd line option
1787 au1100fb:panel=<name>.
1790 bool "Au1200/Au1300 LCD Driver"
1791 depends on (FB = y) && MIPS_ALCHEMY
1792 select FB_SYS_FILLRECT
1793 select FB_SYS_COPYAREA
1794 select FB_SYS_IMAGEBLIT
1797 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1798 It can drive various panels and CRTs by passing in kernel cmd line
1799 option au1200fb:panel=<name>.
1802 bool "VT8500 LCD Driver"
1803 depends on (FB = y) && ARM && ARCH_VT8500
1804 select FB_WMT_GE_ROPS
1805 select FB_SYS_IMAGEBLIT
1807 This is the framebuffer driver for VIA VT8500 integrated LCD
1811 bool "WM8505 frame buffer support"
1812 depends on (FB = y) && ARM && ARCH_VT8500
1813 select FB_WMT_GE_ROPS
1814 select FB_SYS_IMAGEBLIT
1816 This is the framebuffer driver for WonderMedia WM8505/WM8650
1817 integrated LCD controller.
1819 source "drivers/video/geode/Kconfig"
1822 tristate "HD64461 Frame Buffer support"
1823 depends on FB && HD64461
1824 select FB_CFB_FILLRECT
1825 select FB_CFB_COPYAREA
1826 select FB_CFB_IMAGEBLIT
1828 This is the frame buffer device driver for the Hitachi HD64461 LCD
1832 bool "PMAG-AA TURBOchannel framebuffer support"
1833 depends on (FB = y) && TC
1834 select FB_CFB_FILLRECT
1835 select FB_CFB_COPYAREA
1836 select FB_CFB_IMAGEBLIT
1838 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1839 used mainly in the MIPS-based DECstation series.
1842 tristate "PMAG-BA TURBOchannel framebuffer support"
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1849 used mainly in the MIPS-based DECstation series.
1852 tristate "PMAGB-B TURBOchannel framebuffer support"
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1859 in the MIPS-based DECstation series. The card is currently only
1860 supported in 1280x1024x8 mode.
1863 bool "Maxine (Personal DECstation) onboard framebuffer support"
1864 depends on (FB = y) && MACH_DECSTATION
1865 select FB_CFB_FILLRECT
1866 select FB_CFB_COPYAREA
1867 select FB_CFB_IMAGEBLIT
1869 Support for the onboard framebuffer (1024x768x8) in the Personal
1870 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1874 bool "G364 frame buffer support"
1875 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1876 select FB_CFB_FILLRECT
1877 select FB_CFB_COPYAREA
1878 select FB_CFB_IMAGEBLIT
1880 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1881 Olivetti M700-10 systems.
1884 bool "Motorola 68328 native frame buffer support"
1885 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1886 select FB_CFB_FILLRECT
1887 select FB_CFB_COPYAREA
1888 select FB_CFB_IMAGEBLIT
1890 Say Y here if you want to support the built-in frame buffer of
1891 the Motorola 68328 CPU family.
1894 tristate "PXA168/910 LCD framebuffer support"
1895 depends on FB && (CPU_PXA168 || CPU_PXA910)
1896 select FB_CFB_FILLRECT
1897 select FB_CFB_COPYAREA
1898 select FB_CFB_IMAGEBLIT
1900 Frame buffer driver for the built-in LCD controller in the Marvell
1904 tristate "PXA LCD framebuffer support"
1905 depends on FB && ARCH_PXA
1906 select FB_CFB_FILLRECT
1907 select FB_CFB_COPYAREA
1908 select FB_CFB_IMAGEBLIT
1910 Frame buffer driver for the built-in LCD controller in the Intel
1913 This driver is also available as a module ( = code which can be
1914 inserted and removed from the running kernel whenever you want). The
1915 module will be called pxafb. If you want to compile it as a module,
1916 say M here and read <file:Documentation/kbuild/modules.txt>.
1920 config FB_PXA_OVERLAY
1921 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1923 depends on FB_PXA && (PXA27x || PXA3xx)
1925 config FB_PXA_SMARTPANEL
1926 bool "PXA Smartpanel LCD support"
1930 config FB_PXA_PARAMETERS
1931 bool "PXA LCD command line parameters"
1935 Enable the use of kernel command line or module parameters
1936 to configure the physical properties of the LCD panel when
1937 using the PXA LCD driver.
1939 This option allows you to override the panel parameters
1940 supplied by the platform in order to support multiple
1941 different models of flatpanel. If you will only be using a
1942 single model of flatpanel then you can safely leave this
1945 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1948 tristate "PXA3xx 2D graphics accelerator driver"
1951 Kernelspace driver for the 2D graphics controller unit (GCU)
1952 found on PXA3xx processors. There is a counterpart driver in the
1953 DirectFB suite, see http://www.directfb.org/
1955 If you compile this as a module, it will be called pxa3xx_gcu.
1958 tristate "2700G LCD framebuffer support"
1959 depends on FB && ARCH_PXA
1960 select FB_CFB_FILLRECT
1961 select FB_CFB_COPYAREA
1962 select FB_CFB_IMAGEBLIT
1964 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1968 bool "Enable debugging info via debugfs"
1969 depends on FB_MBX && DEBUG_FS
1972 Enable this if you want debugging information using the debug
1973 filesystem (debugfs)
1978 tristate "Freescale DIU framebuffer support"
1979 depends on FB && FSL_SOC
1980 select FB_MODE_HELPERS
1981 select FB_CFB_FILLRECT
1982 select FB_CFB_COPYAREA
1983 select FB_CFB_IMAGEBLIT
1984 select PPC_LIB_RHEAP
1986 Framebuffer driver for the Freescale SoC DIU
1989 tristate "W100 frame buffer support"
1990 depends on FB && ARCH_PXA
1991 select FB_CFB_FILLRECT
1992 select FB_CFB_COPYAREA
1993 select FB_CFB_IMAGEBLIT
1995 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1996 It can also drive the w3220 chip found on iPAQ hx4700.
1998 This driver is also available as a module ( = code which can be
1999 inserted and removed from the running kernel whenever you want). The
2000 module will be called w100fb. If you want to compile it as a module,
2001 say M here and read <file:Documentation/kbuild/modules.txt>.
2005 config FB_SH_MOBILE_LCDC
2006 tristate "SuperH Mobile LCDC framebuffer support"
2007 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2008 select FB_SYS_FILLRECT
2009 select FB_SYS_COPYAREA
2010 select FB_SYS_IMAGEBLIT
2012 select FB_DEFERRED_IO
2014 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2016 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2018 config FB_SH_MOBILE_HDMI
2019 tristate "SuperH Mobile HDMI controller support"
2020 depends on FB_SH_MOBILE_LCDC
2021 select FB_MODE_HELPERS
2026 Driver for the on-chip SH-Mobile HDMI controller.
2029 tristate "Toshiba Mobile IO FrameBuffer support"
2030 depends on FB && MFD_CORE
2031 select FB_CFB_FILLRECT
2032 select FB_CFB_COPYAREA
2033 select FB_CFB_IMAGEBLIT
2035 Frame buffer driver for the Toshiba Mobile IO integrated as found
2036 on the Sharp SL-6000 series
2038 This driver is also available as a module ( = code which can be
2039 inserted and removed from the running kernel whenever you want). The
2040 module will be called tmiofb. If you want to compile it as a module,
2041 say M here and read <file:Documentation/kbuild/modules.txt>.
2045 config FB_TMIO_ACCELL
2046 bool "tmiofb acceleration"
2051 tristate "Samsung S3C framebuffer support"
2052 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2053 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2054 select FB_CFB_FILLRECT
2055 select FB_CFB_COPYAREA
2056 select FB_CFB_IMAGEBLIT
2058 Frame buffer driver for the built-in FB controller in the Samsung
2059 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2060 and the S3C64XX series such as the S3C6400 and S3C6410.
2062 These chips all have the same basic framebuffer design with the
2063 actual capabilities depending on the chip. For instance the S3C6400
2064 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2065 currently only have two.
2067 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2069 config FB_S3C_DEBUG_REGWRITE
2070 bool "Debug register writes"
2073 Show all register writes via pr_debug()
2076 tristate "S3C2410 LCD framebuffer support"
2077 depends on FB && ARCH_S3C24XX
2078 select FB_CFB_FILLRECT
2079 select FB_CFB_COPYAREA
2080 select FB_CFB_IMAGEBLIT
2082 Frame buffer driver for the built-in LCD controller in the Samsung
2085 This driver is also available as a module ( = code which can be
2086 inserted and removed from the running kernel whenever you want). The
2087 module will be called s3c2410fb. If you want to compile it as a module,
2088 say M here and read <file:Documentation/kbuild/modules.txt>.
2091 config FB_S3C2410_DEBUG
2092 bool "S3C2410 lcd debug messages"
2093 depends on FB_S3C2410
2095 Turn on debugging messages. Note that you can set/unset at run time
2099 bool "NUC900 LCD framebuffer support"
2100 depends on FB && ARCH_W90X900
2101 select FB_CFB_FILLRECT
2102 select FB_CFB_COPYAREA
2103 select FB_CFB_IMAGEBLIT
2105 Frame buffer driver for the built-in LCD controller in the Nuvoton
2108 config GPM1040A0_320X240
2109 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2110 depends on FB_NUC900
2112 config FB_NUC900_DEBUG
2113 bool "NUC900 lcd debug messages"
2114 depends on FB_NUC900
2116 Turn on debugging messages. Note that you can set/unset at run time
2120 tristate "Silicon Motion SM501 framebuffer support"
2121 depends on FB && MFD_SM501
2122 select FB_CFB_FILLRECT
2123 select FB_CFB_COPYAREA
2124 select FB_CFB_IMAGEBLIT
2126 Frame buffer driver for the CRT and LCD controllers in the Silicon
2129 This driver is also available as a module ( = code which can be
2130 inserted and removed from the running kernel whenever you want). The
2131 module will be called sm501fb. If you want to compile it as a module,
2132 say M here and read <file:Documentation/kbuild/modules.txt>.
2137 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2138 depends on FB && USB
2139 select FB_MODE_HELPERS
2140 select FB_SYS_FILLRECT
2141 select FB_SYS_COPYAREA
2142 select FB_SYS_IMAGEBLIT
2144 select FB_DEFERRED_IO
2146 This is a kernel framebuffer driver for SMSC UFX USB devices.
2147 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2148 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2150 To compile as a module, choose M here: the module name is smscufx.
2153 tristate "Displaylink 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 DisplayLink USB devices.
2163 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2164 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2165 To compile as a module, choose M here: the module name is udlfb.
2167 config FB_IBM_GXT4500
2168 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2169 depends on FB && PPC
2170 select FB_CFB_FILLRECT
2171 select FB_CFB_COPYAREA
2172 select FB_CFB_IMAGEBLIT
2174 Say Y here to enable support for the IBM GXT4000P/6000P and
2175 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2176 found on some IBM System P (pSeries) machines. This driver
2177 doesn't use Geometry Engine GT1000.
2180 tristate "PS3 GPU framebuffer driver"
2181 depends on FB && PS3_PS3AV
2182 select FB_SYS_FILLRECT
2183 select FB_SYS_COPYAREA
2184 select FB_SYS_IMAGEBLIT
2186 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2188 Include support for the virtual frame buffer in the PS3 platform.
2190 config FB_PS3_DEFAULT_SIZE_M
2191 int "PS3 default frame buffer size (in MiB)"
2195 This is the default size (in MiB) of the virtual frame buffer in
2197 The default value can be overridden on the kernel command line
2198 using the "ps3fb" option (e.g. "ps3fb=9M");
2201 tristate "Xilinx frame buffer support"
2202 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2203 select FB_CFB_FILLRECT
2204 select FB_CFB_COPYAREA
2205 select FB_CFB_IMAGEBLIT
2207 Include support for the Xilinx ML300/ML403 reference design
2208 framebuffer. ML300 carries a 640*480 LCD display on the board,
2209 ML403 uses a standard DB15 VGA connector.
2212 tristate "Goldfish Framebuffer"
2214 select FB_CFB_FILLRECT
2215 select FB_CFB_COPYAREA
2216 select FB_CFB_IMAGEBLIT
2218 Framebuffer driver for Goldfish Virtual Platform
2221 tristate "Cobalt server LCD frame buffer support"
2222 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2225 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2226 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2227 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2228 select FB_CFB_FILLRECT
2229 select FB_CFB_COPYAREA
2230 select FB_CFB_IMAGEBLIT
2232 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2233 (D)STN/TFT LCD Controller.
2234 Supports display resolutions up to 1024x1024 pixel, grayscale and
2235 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2236 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2237 panels <= 320 pixel horizontal resolution.
2240 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2241 depends on FB && ARCH_DAVINCI_DA8XX
2242 select FB_CFB_FILLRECT
2243 select FB_CFB_COPYAREA
2244 select FB_CFB_IMAGEBLIT
2245 select FB_CFB_REV_PIXELS_IN_BYTE
2247 This is the frame buffer device driver for the TI LCD controller
2248 found on DA8xx/OMAP-L1xx SoCs.
2252 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2254 select FB_SYS_FILLRECT
2255 select FB_SYS_COPYAREA
2256 select FB_SYS_IMAGEBLIT
2259 This is a `virtual' frame buffer device. It operates on a chunk of
2260 unswappable kernel memory instead of on the memory of a graphics
2261 board. This means you cannot see any output sent to this frame
2262 buffer device, while it does consume precious memory. The main use
2263 of this frame buffer device is testing and debugging the frame
2264 buffer subsystem. Do NOT enable it for normal systems! To protect
2265 the innocent, it has to be enabled explicitly at boot time using the
2266 kernel option `video=vfb:'.
2268 To compile this driver as a module, choose M here: the
2269 module will be called vfb. In order to load it, you must use
2270 the vfb_enable=1 option.
2274 config XEN_FBDEV_FRONTEND
2275 tristate "Xen virtual frame buffer support"
2276 depends on FB && XEN
2277 select FB_SYS_FILLRECT
2278 select FB_SYS_COPYAREA
2279 select FB_SYS_IMAGEBLIT
2281 select FB_DEFERRED_IO
2282 select INPUT_XEN_KBDDEV_FRONTEND
2283 select XEN_XENBUS_FRONTEND
2286 This driver implements the front-end of the Xen virtual
2287 frame buffer driver. It communicates with a back-end
2291 tristate "E-Ink Metronome/8track controller support"
2293 select FB_SYS_FILLRECT
2294 select FB_SYS_COPYAREA
2295 select FB_SYS_IMAGEBLIT
2297 select FB_DEFERRED_IO
2299 This driver implements support for the E-Ink Metronome
2300 controller. The pre-release name for this device was 8track
2301 and could also have been called by some vendors as PVI-nnnn.
2304 tristate "Fujitsu MB862xx GDC support"
2306 depends on PCI || (OF && PPC)
2307 select FB_CFB_FILLRECT
2308 select FB_CFB_COPYAREA
2309 select FB_CFB_IMAGEBLIT
2311 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2314 prompt "GDC variant"
2315 depends on FB_MB862XX
2317 config FB_MB862XX_PCI_GDC
2318 bool "Carmine/Coral-P(A) GDC"
2321 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2322 PCI graphics controller devices.
2324 config FB_MB862XX_LIME
2326 depends on OF && PPC
2327 select FB_FOREIGN_ENDIAN
2328 select FB_LITTLE_ENDIAN
2330 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2334 config FB_MB862XX_I2C
2335 bool "Support I2C bus on MB862XX GDC"
2336 depends on FB_MB862XX && I2C
2339 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2340 driver to support accessing I2C devices on controller's I2C bus.
2341 These are usually some video decoder chips.
2344 tristate "EP93XX frame buffer support"
2345 depends on FB && ARCH_EP93XX
2346 select FB_CFB_FILLRECT
2347 select FB_CFB_COPYAREA
2348 select FB_CFB_IMAGEBLIT
2350 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2351 This driver is also available as a module. The module will be called
2354 config FB_PRE_INIT_FB
2355 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2356 depends on FB && FB_MB862XX_LIME
2358 Select this option if display contents should be inherited as set by
2362 tristate "MSM Framebuffer support"
2363 depends on FB && ARCH_MSM
2364 select FB_CFB_FILLRECT
2365 select FB_CFB_COPYAREA
2366 select FB_CFB_IMAGEBLIT
2369 tristate "MX3 Framebuffer support"
2370 depends on FB && MX3_IPU
2371 select FB_CFB_FILLRECT
2372 select FB_CFB_COPYAREA
2373 select FB_CFB_IMAGEBLIT
2376 This is a framebuffer device for the i.MX31 LCD Controller. So
2377 far only synchronous displays are supported. If you plan to use
2378 an LCD display with your i.MX31 system, say Y here.
2380 config FB_BROADSHEET
2381 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2383 select FB_SYS_FILLRECT
2384 select FB_SYS_COPYAREA
2385 select FB_SYS_IMAGEBLIT
2387 select FB_DEFERRED_IO
2389 This driver implements support for the E-Ink Broadsheet
2390 controller. The release name for this device was Epson S1D13521
2391 and could also have been called by other names when coupled with
2395 tristate "AUO-K190X EPD controller support"
2397 select FB_SYS_FILLRECT
2398 select FB_SYS_COPYAREA
2399 select FB_SYS_IMAGEBLIT
2401 select FB_DEFERRED_IO
2403 Provides support for epaper controllers from the K190X series
2404 of AUO. These controllers can be used to drive epaper displays
2407 This option enables the common support, shared by the individual
2408 controller drivers. You will also have to enable the driver
2409 for the controller type used in your device.
2412 tristate "AUO-K1900 EPD controller support"
2413 depends on FB && FB_AUO_K190X
2415 This driver implements support for the AUO K1900 epd-controller.
2416 This controller can drive Sipix epaper displays but can only do
2417 serial updates, reducing the number of possible frames per second.
2420 tristate "AUO-K1901 EPD controller support"
2421 depends on FB && FB_AUO_K190X
2423 This driver implements support for the AUO K1901 epd-controller.
2424 This controller can drive Sipix epaper displays and supports
2425 concurrent updates, making higher frames per second possible.
2428 tristate "JZ4740 LCD framebuffer support"
2429 depends on FB && MACH_JZ4740
2430 select FB_SYS_FILLRECT
2431 select FB_SYS_COPYAREA
2432 select FB_SYS_IMAGEBLIT
2434 Framebuffer support for the JZ4740 SoC.
2437 tristate "MXS LCD framebuffer support"
2438 depends on FB && ARCH_MXS
2439 select FB_CFB_FILLRECT
2440 select FB_CFB_COPYAREA
2441 select FB_CFB_IMAGEBLIT
2443 Framebuffer support for the MXS SoC.
2445 config FB_PUV3_UNIGFX
2446 tristate "PKUnity v3 Unigfx framebuffer support"
2447 depends on FB && UNICORE32 && ARCH_PUV3
2448 select FB_SYS_FILLRECT
2449 select FB_SYS_COPYAREA
2450 select FB_SYS_IMAGEBLIT
2453 Choose this option if you want to use the Unigfx device as a
2454 framebuffer device. Without the support of PCI & AGP.
2456 source "drivers/video/omap/Kconfig"
2457 source "drivers/video/omap2/Kconfig"
2458 source "drivers/video/exynos/Kconfig"
2459 source "drivers/video/mmp/Kconfig"
2460 source "drivers/video/backlight/Kconfig"
2463 source "drivers/video/console/Kconfig"
2466 if FB || SGI_NEWPORT_CONSOLE
2467 source "drivers/video/logo/Kconfig"
2470 config FB_SH_MOBILE_MERAM
2471 tristate "SuperH Mobile MERAM read ahead support"
2472 depends on (SUPERH || ARCH_SHMOBILE)
2473 select GENERIC_ALLOCATOR
2475 Enable MERAM support for the SuperH controller.
2477 This will allow for caching of the framebuffer to provide more
2478 reliable access under heavy main memory bus traffic situations.
2479 Up to 4 memory channels can be configured, allowing 4 RGB or
2480 2 YCbCr framebuffers to be configured.
2483 tristate "Solomon SSD1307 framebuffer support"
2484 depends on FB && I2C
2486 depends on GENERIC_GPIO
2488 select FB_SYS_FILLRECT
2489 select FB_SYS_COPYAREA
2490 select FB_SYS_IMAGEBLIT
2491 select FB_DEFERRED_IO
2494 This driver implements support for the Solomon SSD1307
2495 OLED controller over I2C.