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/stub/Kconfig"
26 source "drivers/gpu/ion/Kconfig"
28 source "drivers/gpu/arm/Kconfig"
34 config VIDEO_OUTPUT_CONTROL
35 tristate "Lowlevel video output switch controls"
37 This framework adds support for low-level control of the video
41 tristate "Support for frame buffer devices"
43 The frame buffer device provides an abstraction for the graphics
44 hardware. It represents the frame buffer of some video hardware and
45 allows application software to access the graphics hardware through
46 a well-defined interface, so the software doesn't need to know
47 anything about the low-level (hardware register) stuff.
49 Frame buffer devices work identically across the different
50 architectures supported by Linux and make the implementation of
51 application programs easier and more portable; at this point, an X
52 server exists which uses the frame buffer device exclusively.
53 On several non-X86 architectures, the frame buffer device is the
54 only way to use the graphics hardware.
56 The device is accessed through special device nodes, usually located
57 in the /dev directory, i.e. /dev/fb*.
59 You need an utility program called fbset to make full use of frame
60 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
61 and the Framebuffer-HOWTO at
62 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
65 Say Y here and to the driver for your graphics board below if you
66 are compiling a kernel for a non-x86 architecture.
68 If you are compiling for the x86 architecture, you can say Y if you
69 want to play with it, but it is not essential. Please note that
70 running graphical applications that directly touch the hardware
71 (e.g. an accelerated X server) and that are not frame buffer
72 device-aware may cause unexpected results. If unsure, say N.
75 bool "Enable firmware EDID"
79 This enables access to the EDID transferred from the firmware.
80 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
81 transfers do not work for your driver and if you are using
82 nvidiafb, i810fb or savagefb.
84 In general, choosing Y for this option is safe. If you
85 experience extremely long delays while booting before you get
86 something on your display, try setting this to N. Matrox cards in
87 combination with certain motherboards and monitors are known to
88 suffer from this problem.
97 config FB_BOOT_VESA_SUPPORT
102 If true, at least one selected framebuffer driver can take advantage
103 of VESA video modes set at an early boot stage via the vga= parameter.
105 config FB_CFB_FILLRECT
110 Include the cfb_fillrect function for generic software rectangle
111 filling. This is used by drivers that don't provide their own
112 (accelerated) version.
114 config FB_CFB_COPYAREA
119 Include the cfb_copyarea function for generic software area copying.
120 This is used by drivers that don't provide their own (accelerated)
123 config FB_CFB_IMAGEBLIT
128 Include the cfb_imageblit function for generic software image
129 blitting. This is used by drivers that don't provide their own
130 (accelerated) version.
132 config FB_CFB_REV_PIXELS_IN_BYTE
137 Allow generic frame-buffer functions to work on displays with 1, 2
138 and 4 bits per pixel depths which has opposite order of pixels in
139 byte order to bytes in long order.
141 config FB_SYS_FILLRECT
146 Include the sys_fillrect function for generic software rectangle
147 filling. This is used by drivers that don't provide their own
148 (accelerated) version and the framebuffer is in system RAM.
150 config FB_SYS_COPYAREA
155 Include the sys_copyarea function for generic software area copying.
156 This is used by drivers that don't provide their own (accelerated)
157 version and the framebuffer is in system RAM.
159 config FB_SYS_IMAGEBLIT
164 Include the sys_imageblit function for generic software image
165 blitting. This is used by drivers that don't provide their own
166 (accelerated) version and the framebuffer is in system RAM.
168 menuconfig FB_FOREIGN_ENDIAN
169 bool "Framebuffer foreign endianness support"
172 This menu will let you enable support for the framebuffers with
173 non-native endianness (e.g. Little-Endian framebuffer on a
174 Big-Endian machine). Most probably you don't have such hardware,
175 so it's safe to say "n" here.
178 prompt "Choice endianness support"
179 depends on FB_FOREIGN_ENDIAN
181 config FB_BOTH_ENDIAN
182 bool "Support for Big- and Little-Endian framebuffers"
185 bool "Support for Big-Endian framebuffers only"
187 config FB_LITTLE_ENDIAN
188 bool "Support for Little-Endian framebuffers only"
197 config FB_WMT_GE_ROPS
202 Include functions for accelerated rectangle filling and area
203 copying using WonderMedia Graphics Engine operations.
205 config FB_DEFERRED_IO
212 depends on FB_DEFERRED_IO
219 Common utility functions useful to fbdev drivers of VGA-based
230 select BACKLIGHT_LCD_SUPPORT
231 select BACKLIGHT_CLASS_DEVICE
234 config FB_MODE_HELPERS
235 bool "Enable Video Mode Handling Helpers"
239 This enables functions for handling video modes using the
240 Generalized Timing Formula and the EDID parser. A few drivers rely
241 on this feature such as the radeonfb, rivafb, and the i810fb. If
242 your driver does not take advantage of this feature, choosing Y will
243 just increase the kernel size by about 5K.
245 config FB_TILEBLITTING
246 bool "Enable Tile Blitting Support"
250 This enables tile blitting. Tile blitting is a drawing technique
251 where the screen is divided into rectangular sections (tiles), whereas
252 the standard blitting divides the screen into pixels. Because the
253 default drawing element is a tile, drawing functions will be passed
254 parameters in terms of number of tiles instead of number of pixels.
255 For example, to draw a single character, instead of using bitmaps,
256 an index to an array of bitmaps will be used. To clear or move a
257 rectangular section of a screen, the rectangle will be described in
258 terms of number of tiles in the x- and y-axis.
260 This is particularly important to one driver, matroxfb. If
263 comment "Frame buffer hardware drivers"
266 source "drivers/video/samsung/Kconfig"
267 source "drivers/video/samsung_extdisp/Kconfig"
268 source "drivers/video/samsung_duallcd/Kconfig"
271 tristate "Cirrus Logic support"
272 depends on FB && (ZORRO || PCI)
273 select FB_CFB_FILLRECT
274 select FB_CFB_COPYAREA
275 select FB_CFB_IMAGEBLIT
277 This enables support for Cirrus Logic GD542x/543x based boards on
278 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
280 If you have a PCI-based system, this enables support for these
281 chips: GD-543x, GD-544x, GD-5480.
283 Please read the file <file:Documentation/fb/cirrusfb.txt>.
285 Say N unless you have such a graphics board or plan to get one
286 before you next recompile the kernel.
289 tristate "Permedia2 support"
290 depends on FB && ((AMIGA && BROKEN) || PCI)
291 select FB_CFB_FILLRECT
292 select FB_CFB_COPYAREA
293 select FB_CFB_IMAGEBLIT
295 This is the frame buffer device driver for cards based on
296 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
297 The driver was tested on the following cards:
298 Diamond FireGL 1000 PRO AGP
299 ELSA Gloria Synergy PCI
300 Appian Jeronimo PRO (both heads) PCI
301 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
302 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
303 ASK Graphic Blaster Exxtreme AGP
305 To compile this driver as a module, choose M here: the
306 module will be called pm2fb.
308 config FB_PM2_FIFO_DISCONNECT
309 bool "enable FIFO disconnect feature"
310 depends on FB_PM2 && PCI
312 Support the Permedia2 FIFO disconnect feature.
315 tristate "ARM PrimeCell PL110 support"
316 depends on FB && ARM && ARM_AMBA
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
321 This framebuffer device driver is for the ARM PrimeCell PL110
322 Colour LCD controller. ARM PrimeCells provide the building
323 blocks for System on a Chip devices.
325 If you want to compile this as a module (=code which can be
326 inserted into and removed from the running kernel), say M
327 here and read <file:Documentation/kbuild/modules.txt>. The module
328 will be called amba-clcd.
331 bool "Acorn VIDC support"
332 depends on (FB = y) && ARM && ARCH_ACORN
333 select FB_CFB_FILLRECT
334 select FB_CFB_COPYAREA
335 select FB_CFB_IMAGEBLIT
337 This is the frame buffer device driver for the Acorn VIDC graphics
338 hardware found in Acorn RISC PCs and other ARM-based machines. If
342 bool "CLPS711X LCD support"
343 depends on (FB = y) && ARM && ARCH_CLPS711X
344 select FB_CFB_FILLRECT
345 select FB_CFB_COPYAREA
346 select FB_CFB_IMAGEBLIT
348 Say Y to enable the Framebuffer driver for the CLPS7111 and
352 bool "SA-1100 LCD support"
353 depends on (FB = y) && ARM && ARCH_SA1100
354 select FB_CFB_FILLRECT
355 select FB_CFB_COPYAREA
356 select FB_CFB_IMAGEBLIT
358 This is a framebuffer device for the SA-1100 LCD Controller.
359 See <http://www.linux-fbdev.org/> for information on framebuffer
362 If you plan to use the LCD display with your SA-1100 system, say
366 tristate "Freescale i.MX LCD support"
367 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
373 tristate "CyberPro 2000/2010/5000 support"
374 depends on FB && PCI && (BROKEN || !SPARC64)
375 select FB_CFB_FILLRECT
376 select FB_CFB_COPYAREA
377 select FB_CFB_IMAGEBLIT
379 This enables support for the Integraphics CyberPro 20x0 and 5000
380 VGA chips used in the Rebel.com Netwinder and other machines.
381 Say Y if you have a NetWinder or a graphics card containing this
382 device, otherwise say N.
384 config FB_CYBER2000_DDC
385 bool "DDC for CyberPro support"
386 depends on FB_CYBER2000
390 Say Y here if you want DDC support for your CyberPro graphics
391 card. This is only I2C bus support, driver does not use EDID.
393 config FB_CYBER2000_I2C
394 bool "CyberPro 2000/2010/5000 I2C support"
395 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
398 Enable support for the I2C video decoder interface on the
399 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
400 on the Netwinder machines for the SAA7111 video capture.
404 depends on (FB = y) && APOLLO
406 select FB_CFB_FILLRECT
407 select FB_CFB_IMAGEBLIT
411 depends on (FB = y) && Q40
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
418 tristate "Amiga native chipset support"
419 depends on FB && AMIGA
421 This is the frame buffer device driver for the builtin graphics
422 chipset found in Amigas.
424 To compile this driver as a module, choose M here: the
425 module will be called amifb.
428 bool "Amiga OCS chipset support"
431 This enables support for the original Agnus and Denise video chips,
432 found in the Amiga 1000 and most A500's and A2000's. If you intend
433 to run Linux on any of these systems, say Y; otherwise say N.
436 bool "Amiga ECS chipset support"
439 This enables support for the Enhanced Chip Set, found in later
440 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
441 you intend to run Linux on any of these systems, say Y; otherwise
445 bool "Amiga AGA chipset support"
448 This enables support for the Advanced Graphics Architecture (also
449 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
450 and CD32. If you intend to run Linux on any of these systems, say Y;
454 bool "Amiga FrameMaster II/Rainbow II support"
455 depends on (FB = y) && ZORRO
456 select FB_CFB_FILLRECT
457 select FB_CFB_COPYAREA
458 select FB_CFB_IMAGEBLIT
460 This is the frame buffer device driver for the Amiga FrameMaster
461 card from BSC (exhibited 1992 but not shipped as a CBM product).
464 tristate "Arc Monochrome LCD board support"
466 select FB_SYS_FILLRECT
467 select FB_SYS_COPYAREA
468 select FB_SYS_IMAGEBLIT
471 This enables support for the Arc Monochrome LCD board. The board
472 is based on the KS-108 lcd controller and is typically a matrix
473 of 2*n chips. This driver was tested with a 128x64 panel. This
474 driver supports it for use with x86 SBCs through a 16 bit GPIO
475 interface (8 bit data, 8 bit control). If you anticipate using
476 this driver, say Y or M; otherwise say N. You must specify the
477 GPIO IO address to be used for setting control and data.
480 bool "Atari native chipset support"
481 depends on (FB = y) && ATARI
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 builtin graphics
487 chipset found in Ataris.
490 bool "Open Firmware frame buffer device support"
491 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
492 select FB_CFB_FILLRECT
493 select FB_CFB_COPYAREA
494 select FB_CFB_IMAGEBLIT
497 Say Y if you want support with Open Firmware for your graphics
501 bool "Apple \"control\" display support"
502 depends on (FB = y) && PPC_PMAC && PPC32
503 select FB_CFB_FILLRECT
504 select FB_CFB_COPYAREA
505 select FB_CFB_IMAGEBLIT
508 This driver supports a frame buffer for the graphics adapter in the
509 Power Macintosh 7300 and others.
512 bool "Apple \"platinum\" display support"
513 depends on (FB = y) && PPC_PMAC && PPC32
514 select FB_CFB_FILLRECT
515 select FB_CFB_COPYAREA
516 select FB_CFB_IMAGEBLIT
519 This driver supports a frame buffer for the "platinum" graphics
520 adapter in some Power Macintoshes.
523 bool "Apple \"valkyrie\" display support"
524 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
525 select FB_CFB_FILLRECT
526 select FB_CFB_COPYAREA
527 select FB_CFB_IMAGEBLIT
530 This driver supports a frame buffer for the "valkyrie" graphics
531 adapter in some Power Macintoshes.
534 bool "Chips 65550 display support"
535 depends on (FB = y) && PPC32 && PCI
536 select FB_CFB_FILLRECT
537 select FB_CFB_COPYAREA
538 select FB_CFB_IMAGEBLIT
540 This is the frame buffer device driver for the Chips & Technologies
541 65550 graphics chip in PowerBooks.
544 bool "Asiliant (Chips) 69000 display support"
545 depends on (FB = y) && PCI
546 select FB_CFB_FILLRECT
547 select FB_CFB_COPYAREA
548 select FB_CFB_IMAGEBLIT
550 This is the frame buffer device driver for the Asiliant 69030 chipset
553 bool "IMS Twin Turbo display support"
554 depends on (FB = y) && PCI
555 select FB_CFB_IMAGEBLIT
556 select FB_MACMODES if PPC
558 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
559 many Macintosh and compatible computers.
562 tristate "VGA 16-color graphics support"
563 depends on FB && (X86 || PPC)
564 select FB_CFB_FILLRECT
565 select FB_CFB_COPYAREA
566 select FB_CFB_IMAGEBLIT
568 select FONT_8x16 if FRAMEBUFFER_CONSOLE
570 This is the frame buffer device driver for VGA 16 color graphic
571 cards. Say Y if you have such a card.
573 To compile this driver as a module, choose M here: the
574 module will be called vga16fb.
576 config FB_BF54X_LQ043
577 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
578 depends on FB && (BF54x) && !BF542
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
583 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
585 config FB_BFIN_T350MCQB
586 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
587 depends on FB && BLACKFIN
589 select FB_CFB_FILLRECT
590 select FB_CFB_COPYAREA
591 select FB_CFB_IMAGEBLIT
593 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
594 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
595 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
597 config FB_BFIN_LQ035Q1
598 tristate "SHARP LQ035Q1DH02 TFT LCD"
599 depends on FB && BLACKFIN && SPI
600 select FB_CFB_FILLRECT
601 select FB_CFB_COPYAREA
602 select FB_CFB_IMAGEBLIT
605 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
606 the Blackfin Landscape LCD EZ-Extender Card.
607 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
608 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
610 To compile this driver as a module, choose M here: the
611 module will be called bfin-lq035q1-fb.
613 config FB_BF537_LQ035
614 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
615 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
621 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
624 To compile this driver as a module, choose M here: the
625 module will be called bf537-lq035.
628 tristate "Blackfin ADV7393 Video encoder"
629 depends on FB && BLACKFIN
631 select FB_CFB_FILLRECT
632 select FB_CFB_COPYAREA
633 select FB_CFB_IMAGEBLIT
635 This is the framebuffer device for a ADV7393 video encoder
636 attached to a Blackfin on the PPI port.
637 If your Blackfin board has a ADV7393 select Y.
639 To compile this driver as a module, choose M here: the
640 module will be called bfin_adv7393fb.
643 prompt "Video mode support"
644 depends on FB_BFIN_7393
654 bool 'NTSC 640x480 (Experimental)'
657 bool 'PAL 640x480 (Experimental)'
660 bool 'NTSC 720x480 YCbCR input'
663 bool 'PAL 720x576 YCbCR input'
668 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
669 depends on (FB_BFIN_7393)
670 default ADV7393_1XMEM
680 tristate "HP STI frame buffer device support"
681 depends on FB && PARISC
682 select FB_CFB_FILLRECT
683 select FB_CFB_COPYAREA
684 select FB_CFB_IMAGEBLIT
689 STI refers to the HP "Standard Text Interface" which is a set of
690 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
691 Enabling this option will implement the linux framebuffer device
692 using calls to the STI BIOS routines for initialisation.
694 If you enable this option, you will get a planar framebuffer device
695 /dev/fb which will work on the most common HP graphic cards of the
696 NGLE family, including the artist chips (in the 7xx and Bxxx series),
697 HCRX, HCRX24, CRX, CRX24 and VisEG series.
699 It is safe to enable this option, so you should probably say "Y".
702 bool "Generic Macintosh display support"
703 depends on (FB = y) && MAC
704 select FB_CFB_FILLRECT
705 select FB_CFB_COPYAREA
706 select FB_CFB_IMAGEBLIT
711 depends on (FB = y) && DIO
712 select FB_CFB_IMAGEBLIT
716 tristate "TGA/SFB+ framebuffer support"
717 depends on FB && (ALPHA || TC)
718 select FB_CFB_FILLRECT
719 select FB_CFB_COPYAREA
720 select FB_CFB_IMAGEBLIT
723 This is the frame buffer device driver for generic TGA and SFB+
724 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
725 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
726 TURBOchannel cards, also known as PMAGD-A, -B and -C.
728 Due to hardware limitations ZLX-E2 and E3 cards are not supported
729 for DECstation 5000/200 systems. Additionally due to firmware
730 limitations these cards may cause troubles with booting DECstation
731 5000/240 and /260 systems, but are fully supported under Linux if
732 you manage to get it going. ;-)
734 Say Y if you have one of those.
737 tristate "Userspace VESA VGA graphics support"
738 depends on FB && CONNECTOR
739 select FB_CFB_FILLRECT
740 select FB_CFB_COPYAREA
741 select FB_CFB_IMAGEBLIT
742 select FB_MODE_HELPERS
744 This is the frame buffer driver for generic VBE 2.0 compliant
745 graphic cards. It can also take advantage of VBE 3.0 features,
746 such as refresh rate adjustment.
748 This driver generally provides more features than vesafb but
749 requires a userspace helper application called 'v86d'. See
750 <file:Documentation/fb/uvesafb.txt> for more information.
755 bool "VESA VGA graphics support"
756 depends on (FB = y) && X86
757 select FB_CFB_FILLRECT
758 select FB_CFB_COPYAREA
759 select FB_CFB_IMAGEBLIT
760 select FB_BOOT_VESA_SUPPORT
762 This is the frame buffer device driver for generic VESA 2.0
763 compliant graphic cards. The older VESA 1.2 cards are not supported.
764 You will get a boot time penguin logo at no additional cost. Please
765 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
768 bool "EFI-based Framebuffer Support"
769 depends on (FB = y) && X86 && EFI
770 select FB_CFB_FILLRECT
771 select FB_CFB_COPYAREA
772 select FB_CFB_IMAGEBLIT
774 This is the EFI frame buffer device driver. If the firmware on
775 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
776 using the EFI framebuffer as your console.
779 tristate "N411 Apollo/Hecuba devkit support"
780 depends on FB && X86 && MMU
781 select FB_SYS_FILLRECT
782 select FB_SYS_COPYAREA
783 select FB_SYS_IMAGEBLIT
785 select FB_DEFERRED_IO
788 This enables support for the Apollo display controller in its
789 Hecuba form using the n411 devkit.
792 tristate "Hercules mono graphics support"
795 Say Y here if you have a Hercules mono graphics card.
797 To compile this driver as a module, choose M here: the
798 module will be called hgafb.
800 As this card technology is at least 25 years old,
801 most people will answer N here.
804 tristate "SGI Visual Workstation framebuffer support"
805 depends on FB && X86_VISWS
806 select FB_CFB_FILLRECT
807 select FB_CFB_COPYAREA
808 select FB_CFB_IMAGEBLIT
810 SGI Visual Workstation support for framebuffer graphics.
813 bool "SGI Graphics Backend frame buffer support"
814 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
815 select FB_CFB_FILLRECT
816 select FB_CFB_COPYAREA
817 select FB_CFB_IMAGEBLIT
819 This is the frame buffer device driver for SGI Graphics Backend.
820 This chip is used in SGI O2 and Visual Workstation 320/540.
823 int "Video memory size in MB"
827 This is the amount of memory reserved for the framebuffer,
828 which can be any value between 1MB and 8MB.
831 bool "SBUS and UPA framebuffers"
832 depends on (FB = y) && SPARC
834 Say Y if you want support for SBUS or UPA based frame buffer device.
838 depends on (FB = y) && (SPARC && FB_SBUS)
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for the BWtwo frame buffer.
846 bool "CGthree support"
847 depends on (FB = y) && (SPARC && FB_SBUS)
848 select FB_CFB_FILLRECT
849 select FB_CFB_COPYAREA
850 select FB_CFB_IMAGEBLIT
852 This is the frame buffer device driver for the CGthree frame buffer.
855 bool "CGsix (GX,TurboGX) support"
856 depends on (FB = y) && (SPARC && FB_SBUS)
857 select FB_CFB_COPYAREA
858 select FB_CFB_IMAGEBLIT
860 This is the frame buffer device driver for the CGsix (GX, TurboGX)
864 bool "Creator/Creator3D/Elite3D support"
865 depends on FB_SBUS && SPARC64
866 select FB_CFB_COPYAREA
867 select FB_CFB_IMAGEBLIT
869 This is the frame buffer device driver for the Creator, Creator3D,
870 and Elite3D graphics boards.
873 bool "TCX (SS4/SS5 only) support"
875 select FB_CFB_FILLRECT
876 select FB_CFB_COPYAREA
877 select FB_CFB_IMAGEBLIT
879 This is the frame buffer device driver for the TCX 24/8bit frame
883 bool "CGfourteen (SX) support"
885 select FB_CFB_FILLRECT
886 select FB_CFB_COPYAREA
887 select FB_CFB_IMAGEBLIT
889 This is the frame buffer device driver for the CGfourteen frame
890 buffer on Desktop SPARCsystems with the SX graphics option.
893 bool "P9100 (Sparcbook 3 only) support"
895 select FB_CFB_FILLRECT
896 select FB_CFB_COPYAREA
897 select FB_CFB_IMAGEBLIT
899 This is the frame buffer device driver for the P9100 card
900 supported on Sparcbook 3 machines.
903 bool "Leo (ZX) support"
905 select FB_CFB_FILLRECT
906 select FB_CFB_COPYAREA
907 select FB_CFB_IMAGEBLIT
909 This is the frame buffer device driver for the SBUS-based Sun ZX
910 (leo) frame buffer cards.
913 bool "IGA 168x display support"
914 depends on (FB = y) && SPARC32
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the framebuffer device for the INTERGRAPHICS 1680 and
920 successor frame buffer cards.
923 bool "Sun XVR-500 3DLABS Wildcat support"
924 depends on (FB = y) && PCI && SPARC64
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 This is the framebuffer device for the Sun XVR-500 and similar
930 graphics cards based upon the 3DLABS Wildcat chipset. The driver
931 only works on sparc64 systems where the system firmware has
932 mostly initialized the card already. It is treated as a
933 completely dumb framebuffer device.
936 bool "Sun XVR-2500 3DLABS Wildcat support"
937 depends on (FB = y) && PCI && SPARC64
938 select FB_CFB_FILLRECT
939 select FB_CFB_COPYAREA
940 select FB_CFB_IMAGEBLIT
942 This is the framebuffer device for the Sun XVR-2500 and similar
943 graphics cards based upon the 3DLABS Wildcat chipset. The driver
944 only works on sparc64 systems where the system firmware has
945 mostly initialized the card already. It is treated as a
946 completely dumb framebuffer device.
949 bool "Sun XVR-1000 support"
950 depends on (FB = y) && 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-1000 and similar
956 graphics cards. The driver only works on sparc64 systems where
957 the system firmware has mostly initialized the card already. It
958 is treated as a completely dumb framebuffer device.
961 tristate "NEC PowerVR 2 display support"
962 depends on FB && SH_DREAMCAST
963 select FB_CFB_FILLRECT
964 select FB_CFB_COPYAREA
965 select FB_CFB_IMAGEBLIT
967 Say Y here if you have a PowerVR 2 card in your box. If you plan to
968 run linux on your Dreamcast, you will have to say Y here.
969 This driver may or may not work on other PowerVR 2 cards, but is
970 totally untested. Use at your own risk. If unsure, say N.
972 To compile this driver as a module, choose M here: the
973 module will be called pvr2fb.
975 You can pass several parameters to the driver at boot time or at
976 module load time. The parameters look like "video=pvr2:XXX", where
977 the meaning of XXX can be found at the end of the main source file
978 (<file:drivers/video/pvr2fb.c>). Please see the file
979 <file:Documentation/fb/pvr2fb.txt>.
982 bool "Epson 1355 framebuffer support"
983 depends on (FB = y) && ARCH_CEIVA
984 select FB_CFB_FILLRECT
985 select FB_CFB_COPYAREA
986 select FB_CFB_IMAGEBLIT
988 Build in support for the SED1355 Epson Research Embedded RAMDAC
989 LCD/CRT Controller (since redesignated as the S1D13505) as a
990 framebuffer. Product specs at
991 <http://vdc.epson.com/>.
994 tristate "Epson S1D13XXX framebuffer support"
996 select FB_CFB_FILLRECT
997 select FB_CFB_COPYAREA
998 select FB_CFB_IMAGEBLIT
1000 Support for S1D13XXX framebuffer device family (currently only
1001 working with S1D13806). Product specs at
1002 <http://vdc.epson.com/>
1005 tristate "AT91/AT32 LCD Controller support"
1006 depends on FB && HAVE_FB_ATMEL
1007 select FB_CFB_FILLRECT
1008 select FB_CFB_COPYAREA
1009 select FB_CFB_IMAGEBLIT
1011 This enables support for the AT91/AT32 LCD Controller.
1014 bool "Frame Buffer in internal SRAM"
1015 depends on FB_ATMEL && ARCH_AT91SAM9261
1017 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1018 to let frame buffer in external SDRAM.
1021 bool "Use a STN display with AT91/AT32 LCD Controller"
1022 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1025 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1026 Controller. Say N if you want to connect a TFT.
1031 tristate "nVidia Framebuffer Support"
1032 depends on FB && PCI
1033 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1034 select FB_MODE_HELPERS
1035 select FB_CFB_FILLRECT
1036 select FB_CFB_COPYAREA
1037 select FB_CFB_IMAGEBLIT
1041 This driver supports graphics boards with the nVidia chips, TNT
1042 and newer. For very old chipsets, such as the RIVA128, then use
1044 Say Y if you have such a graphics board.
1046 To compile this driver as a module, choose M here: the
1047 module will be called nvidiafb.
1049 config FB_NVIDIA_I2C
1050 bool "Enable DDC Support"
1051 depends on FB_NVIDIA
1054 This enables I2C support for nVidia Chipsets. This is used
1055 only for getting EDID information from the attached display
1056 allowing for robust video mode handling and switching.
1058 Because fbdev-2.6 requires that drivers must be able to
1059 independently validate video mode parameters, you should say Y
1062 config FB_NVIDIA_DEBUG
1063 bool "Lots of debug output"
1064 depends on FB_NVIDIA
1067 Say Y here if you want the nVidia driver to output all sorts
1068 of debugging information to provide to the maintainer when
1069 something goes wrong.
1071 config FB_NVIDIA_BACKLIGHT
1072 bool "Support for backlight control"
1073 depends on FB_NVIDIA
1076 Say Y here if you want to control the backlight of your display.
1079 tristate "nVidia Riva support"
1080 depends on FB && PCI
1081 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1082 select FB_MODE_HELPERS
1083 select FB_CFB_FILLRECT
1084 select FB_CFB_COPYAREA
1085 select FB_CFB_IMAGEBLIT
1089 This driver supports graphics boards with the nVidia Riva/Geforce
1091 Say Y if you have such a graphics board.
1093 To compile this driver as a module, choose M here: the
1094 module will be called rivafb.
1097 bool "Enable DDC Support"
1101 This enables I2C support for nVidia Chipsets. This is used
1102 only for getting EDID information from the attached display
1103 allowing for robust video mode handling and switching.
1105 Because fbdev-2.6 requires that drivers must be able to
1106 independently validate video mode parameters, you should say Y
1109 config FB_RIVA_DEBUG
1110 bool "Lots of debug output"
1114 Say Y here if you want the Riva driver to output all sorts
1115 of debugging information to provide to the maintainer when
1116 something goes wrong.
1118 config FB_RIVA_BACKLIGHT
1119 bool "Support for backlight control"
1123 Say Y here if you want to control the backlight of your display.
1126 tristate "Intel 810/815 support (EXPERIMENTAL)"
1127 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1128 select FB_MODE_HELPERS
1129 select FB_CFB_FILLRECT
1130 select FB_CFB_COPYAREA
1131 select FB_CFB_IMAGEBLIT
1134 This driver supports the on-board graphics built in to the Intel 810
1135 and 815 chipsets. Say Y if you have and plan to use such a board.
1137 To compile this driver as a module, choose M here: the
1138 module will be called i810fb.
1140 For more information, please read
1141 <file:Documentation/fb/intel810.txt>
1144 bool "use VESA Generalized Timing Formula"
1147 If you say Y, then the VESA standard, Generalized Timing Formula
1148 or GTF, will be used to calculate the required video timing values
1149 per video mode. Since the GTF allows nondiscrete timings
1150 (nondiscrete being a range of values as opposed to discrete being a
1151 set of values), you'll be able to use any combination of horizontal
1152 and vertical resolutions, and vertical refresh rates without having
1153 to specify your own timing parameters. This is especially useful
1154 to maximize the performance of an aging display, or if you just
1155 have a display with nonstandard dimensions. A VESA compliant
1156 monitor is recommended, but can still work with non-compliant ones.
1157 If you need or want this, then select this option. The timings may
1158 not be compliant with Intel's recommended values. Use at your own
1161 If you say N, the driver will revert to discrete video timings
1162 using a set recommended by Intel in their documentation.
1167 bool "Enable DDC Support"
1168 depends on FB_I810 && FB_I810_GTF
1173 tristate "Intel LE80578 (Vermilion) support"
1174 depends on FB && PCI && X86
1175 select FB_MODE_HELPERS
1176 select FB_CFB_FILLRECT
1177 select FB_CFB_COPYAREA
1178 select FB_CFB_IMAGEBLIT
1180 This driver supports the LE80578 (Vermilion Range) chipset
1182 config FB_CARILLO_RANCH
1183 tristate "Intel Carillo Ranch support"
1184 depends on FB_LE80578 && FB && PCI && X86
1186 This driver supports the LE80578 (Carillo Ranch) board
1189 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1190 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1191 select FB_MODE_HELPERS
1192 select FB_CFB_FILLRECT
1193 select FB_CFB_COPYAREA
1194 select FB_CFB_IMAGEBLIT
1195 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1196 depends on !DRM_I915
1198 This driver supports the on-board graphics built in to the Intel
1199 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1200 Say Y if you have and plan to use such a board.
1202 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1204 To compile this driver as a module, choose M here: the
1205 module will be called intelfb.
1207 For more information, please read <file:Documentation/fb/intelfb.txt>
1209 config FB_INTEL_DEBUG
1210 bool "Intel driver Debug Messages"
1213 Say Y here if you want the Intel driver to output all sorts
1214 of debugging information to provide to the maintainer when
1215 something goes wrong.
1218 bool "DDC/I2C for Intel framebuffer support"
1223 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1226 tristate "Matrox acceleration"
1227 depends on FB && PCI
1228 select FB_CFB_FILLRECT
1229 select FB_CFB_COPYAREA
1230 select FB_CFB_IMAGEBLIT
1231 select FB_TILEBLITTING
1232 select FB_MACMODES if PPC_PMAC
1234 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1235 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1236 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1237 Matrox G400, G450 or G550 card in your box.
1239 To compile this driver as a module, choose M here: the
1240 module will be called matroxfb.
1242 You can pass several parameters to the driver at boot time or at
1243 module load time. The parameters look like "video=matroxfb:XXX", and
1244 are described in <file:Documentation/fb/matroxfb.txt>.
1246 config FB_MATROX_MILLENIUM
1247 bool "Millennium I/II support"
1248 depends on FB_MATROX
1250 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1251 video card. If you select "Advanced lowlevel driver options" below,
1252 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1253 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1254 also use font widths different from 8.
1256 config FB_MATROX_MYSTIQUE
1257 bool "Mystique support"
1258 depends on FB_MATROX
1260 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1261 video card. If you select "Advanced lowlevel driver options" below,
1262 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1263 packed pixel and 32 bpp packed pixel. You can also use font widths
1267 bool "G100/G200/G400/G450/G550 support"
1268 depends on FB_MATROX
1270 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1271 video card. If you select "Advanced lowlevel driver options", you
1272 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1273 pixel and 32 bpp packed pixel. You can also use font widths
1276 If you need support for G400 secondary head, you must say Y to
1277 "Matrox I2C support" and "G400 second head support" right below.
1278 G450/G550 secondary head and digital output are supported without
1281 The driver starts in monitor mode. You must use the matroxset tool
1282 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1283 swap primary and secondary head outputs, or to change output mode.
1284 Secondary head driver always start in 640x480 resolution and you
1285 must use fbset to change it.
1287 Do not forget that second head supports only 16 and 32 bpp
1288 packed pixels, so it is a good idea to compile them into the kernel
1289 too. You can use only some font widths, as the driver uses generic
1290 painting procedures (the secondary head does not use acceleration
1293 G450/G550 hardware can display TV picture only from secondary CRTC,
1294 and it performs no scaling, so picture must have 525 or 625 lines.
1296 config FB_MATROX_I2C
1297 tristate "Matrox I2C support"
1298 depends on FB_MATROX
1301 This drivers creates I2C buses which are needed for accessing the
1302 DDC (I2C) bus present on all Matroxes, an I2C bus which
1303 interconnects Matrox optional devices, like MGA-TVO on G200 and
1304 G400, and the secondary head DDC bus, present on G400 only.
1306 You can say Y or M here if you want to experiment with monitor
1307 detection code. You must say Y or M here if you want to use either
1308 second head of G400 or MGA-TVO on G200 or G400.
1310 If you compile it as module, it will create a module named
1313 config FB_MATROX_MAVEN
1314 tristate "G400 second head support"
1315 depends on FB_MATROX_G && FB_MATROX_I2C
1317 WARNING !!! This support does not work with G450 !!!
1319 Say Y or M here if you want to use a secondary head (meaning two
1320 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1321 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1322 secondary head output is blanked while you are in X. With XFree
1323 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1324 the fbdev driver on first head and the fbdev driver on second head.
1326 If you compile it as module, two modules are created,
1327 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1328 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1329 also load i2c-matroxfb to get it to run.
1331 The driver starts in monitor mode and you must use the matroxset
1333 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1334 PAL or NTSC or to swap primary and secondary head outputs.
1335 Secondary head driver also always start in 640x480 resolution, you
1336 must use fbset to change it.
1338 Also do not forget that second head supports only 16 and 32 bpp
1339 packed pixels, so it is a good idea to compile them into the kernel
1340 too. You can use only some font widths, as the driver uses generic
1341 painting procedures (the secondary head does not use acceleration
1345 tristate "ATI Radeon display support"
1346 depends on FB && PCI
1347 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1348 select FB_MODE_HELPERS
1349 select FB_CFB_FILLRECT
1350 select FB_CFB_COPYAREA
1351 select FB_CFB_IMAGEBLIT
1352 select FB_MACMODES if PPC_OF
1354 Choose this option if you want to use an ATI Radeon graphics card as
1355 a framebuffer device. There are both PCI and AGP versions. You
1356 don't need to choose this to run the Radeon in plain VGA mode.
1358 There is a product page at
1359 http://products.amd.com/en-us/GraphicCardResult.aspx
1361 config FB_RADEON_I2C
1362 bool "DDC/I2C for ATI Radeon support"
1363 depends on FB_RADEON
1367 Say Y here if you want DDC/I2C support for your Radeon board.
1369 config FB_RADEON_BACKLIGHT
1370 bool "Support for backlight control"
1371 depends on FB_RADEON
1374 Say Y here if you want to control the backlight of your display.
1376 config FB_RADEON_DEBUG
1377 bool "Lots of debug output from Radeon driver"
1378 depends on FB_RADEON
1381 Say Y here if you want the Radeon driver to output all sorts
1382 of debugging information to provide to the maintainer when
1383 something goes wrong.
1386 tristate "ATI Rage128 display support"
1387 depends on FB && PCI
1388 select FB_CFB_FILLRECT
1389 select FB_CFB_COPYAREA
1390 select FB_CFB_IMAGEBLIT
1391 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1392 select FB_MACMODES if PPC_PMAC
1394 This driver supports graphics boards with the ATI Rage128 chips.
1395 Say Y if you have such a graphics board and read
1396 <file:Documentation/fb/aty128fb.txt>.
1398 To compile this driver as a module, choose M here: the
1399 module will be called aty128fb.
1401 config FB_ATY128_BACKLIGHT
1402 bool "Support for backlight control"
1403 depends on FB_ATY128
1406 Say Y here if you want to control the backlight of your display.
1409 tristate "ATI Mach64 display support" if PCI || ATARI
1410 depends on FB && !SPARC32
1411 select FB_CFB_FILLRECT
1412 select FB_CFB_COPYAREA
1413 select FB_CFB_IMAGEBLIT
1414 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1415 select FB_MACMODES if PPC
1417 This driver supports graphics boards with the ATI Mach64 chips.
1418 Say Y if you have such a graphics board.
1420 To compile this driver as a module, choose M here: the
1421 module will be called atyfb.
1424 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1425 depends on PCI && FB_ATY
1426 default y if SPARC64 && PCI
1428 Say Y here to support use of ATI's 64-bit Rage boards (or other
1429 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1430 framebuffer device. The ATI product support page for these boards
1431 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1433 config FB_ATY_GENERIC_LCD
1434 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1435 depends on FB_ATY_CT
1437 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1438 Rage XC, or Rage XL chipset.
1441 bool "Mach64 GX support" if PCI
1445 Say Y here to support use of the ATI Mach64 Graphics Expression
1446 board (or other boards based on the Mach64 GX chipset) as a
1447 framebuffer device. The ATI product support page for these boards
1449 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1451 config FB_ATY_BACKLIGHT
1452 bool "Support for backlight control"
1456 Say Y here if you want to control the backlight of your display.
1459 tristate "S3 Trio/Virge support"
1460 depends on FB && PCI
1461 select FB_CFB_FILLRECT
1462 select FB_CFB_COPYAREA
1463 select FB_CFB_IMAGEBLIT
1464 select FB_TILEBLITTING
1467 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1469 Driver for graphics boards with S3 Trio / S3 Virge chip.
1472 bool "DDC for S3 support"
1477 Say Y here if you want DDC support for your S3 graphics card.
1480 tristate "S3 Savage support"
1481 depends on FB && PCI && EXPERIMENTAL
1482 select FB_MODE_HELPERS
1483 select FB_CFB_FILLRECT
1484 select FB_CFB_COPYAREA
1485 select FB_CFB_IMAGEBLIT
1488 This driver supports notebooks and computers with S3 Savage PCI/AGP
1491 Say Y if you have such a graphics card.
1493 To compile this driver as a module, choose M here; the module
1494 will be called savagefb.
1496 config FB_SAVAGE_I2C
1497 bool "Enable DDC2 Support"
1498 depends on FB_SAVAGE
1501 This enables I2C support for S3 Savage Chipsets. This is used
1502 only for getting EDID information from the attached display
1503 allowing for robust video mode handling and switching.
1505 Because fbdev-2.6 requires that drivers must be able to
1506 independently validate video mode parameters, you should say Y
1509 config FB_SAVAGE_ACCEL
1510 bool "Enable Console Acceleration"
1511 depends on FB_SAVAGE
1514 This option will compile in console acceleration support. If
1515 the resulting framebuffer console has bothersome glitches, then
1519 tristate "SiS/XGI display support"
1520 depends on FB && PCI
1521 select FB_CFB_FILLRECT
1522 select FB_CFB_COPYAREA
1523 select FB_CFB_IMAGEBLIT
1524 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1526 This is the frame buffer device driver for the SiS 300, 315, 330
1527 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1528 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1530 To compile this driver as a module, choose M here; the module
1531 will be called sisfb.
1534 bool "SiS 300 series support"
1537 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1540 bool "SiS 315/330/340 series and XGI support"
1543 Say Y here to support use of the SiS 315, 330 and 340 series
1544 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1545 as XGI V3XT, V5, V8 and Z7.
1548 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1549 depends on FB && PCI && X86
1550 select FB_CFB_FILLRECT
1551 select FB_CFB_COPYAREA
1552 select FB_CFB_IMAGEBLIT
1557 This is the frame buffer device driver for Graphics chips of VIA
1558 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1559 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1561 Say Y if you have a VIA UniChrome graphics board.
1563 To compile this driver as a module, choose M here: the
1564 module will be called viafb.
1568 config FB_VIA_DIRECT_PROCFS
1569 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1573 Allow direct hardware access to some output registers via procfs.
1574 This is dangerous but may provide the only chance to get the
1575 correct output device configuration.
1576 Its use is strongly discouraged.
1578 config FB_VIA_X_COMPATIBILITY
1579 bool "X server compatibility"
1583 This option reduces the functionality (power saving, ...) of the
1584 framebuffer to avoid negative impact on the OpenChrome X server.
1585 If you use any X server other than fbdev you should enable this
1586 otherwise it should be safe to disable it and allow using all
1592 tristate "NeoMagic display support"
1593 depends on FB && PCI
1594 select FB_MODE_HELPERS
1595 select FB_CFB_FILLRECT
1596 select FB_CFB_COPYAREA
1597 select FB_CFB_IMAGEBLIT
1600 This driver supports notebooks with NeoMagic PCI chips.
1601 Say Y if you have such a graphics card.
1603 To compile this driver as a module, choose M here: the
1604 module will be called neofb.
1607 tristate "IMG Kyro support"
1608 depends on FB && PCI
1609 select FB_CFB_FILLRECT
1610 select FB_CFB_COPYAREA
1611 select FB_CFB_IMAGEBLIT
1613 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1616 To compile this driver as a module, choose M here: the
1617 module will be called kyrofb.
1620 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1621 depends on FB && PCI
1622 select FB_CFB_IMAGEBLIT
1623 select FB_CFB_FILLRECT
1624 select FB_CFB_COPYAREA
1625 select FB_MODE_HELPERS
1627 This driver supports graphics boards with the 3Dfx Banshee,
1628 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1629 such a graphics board.
1631 To compile this driver as a module, choose M here: the
1632 module will be called tdfxfb.
1634 config FB_3DFX_ACCEL
1635 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1636 depends on FB_3DFX && EXPERIMENTAL
1638 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1639 device driver with acceleration functions.
1642 bool "Enable DDC/I2C support"
1643 depends on FB_3DFX && EXPERIMENTAL
1647 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1650 tristate "3Dfx Voodoo Graphics (sst1) support"
1651 depends on FB && PCI
1652 select FB_CFB_FILLRECT
1653 select FB_CFB_COPYAREA
1654 select FB_CFB_IMAGEBLIT
1656 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1657 Voodoo2 (cvg) based graphics card.
1659 To compile this driver as a module, choose M here: the
1660 module will be called sstfb.
1662 WARNING: Do not use any application that uses the 3D engine
1663 (namely glide) while using this driver.
1664 Please read the <file:Documentation/fb/sstfb.txt> for supported
1665 options and other important info support.
1668 tristate "VIA VT8623 support"
1669 depends on FB && PCI
1670 select FB_CFB_FILLRECT
1671 select FB_CFB_COPYAREA
1672 select FB_CFB_IMAGEBLIT
1673 select FB_TILEBLITTING
1676 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1678 Driver for CastleRock integrated graphics core in the
1679 VIA VT8623 [Apollo CLE266] chipset.
1682 tristate "Trident/CyberXXX/CyberBlade support"
1683 depends on FB && PCI
1684 select FB_CFB_FILLRECT
1685 select FB_CFB_COPYAREA
1686 select FB_CFB_IMAGEBLIT
1688 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1689 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1691 There are also integrated versions of these chips called CyberXXXX,
1692 CyberImage or CyberBlade. These chips are mostly found in laptops
1693 but also on some motherboards including early VIA EPIA motherboards.
1694 For more information, read <file:Documentation/fb/tridentfb.txt>
1696 Say Y if you have such a graphics board.
1698 To compile this driver as a module, choose M here: the
1699 module will be called tridentfb.
1702 tristate "ARK 2000PV support"
1703 depends on FB && PCI
1704 select FB_CFB_FILLRECT
1705 select FB_CFB_COPYAREA
1706 select FB_CFB_IMAGEBLIT
1707 select FB_TILEBLITTING
1710 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1712 Driver for PCI graphics boards with ARK 2000PV chip
1713 and ICS 5342 RAMDAC.
1716 tristate "Permedia3 support (EXPERIMENTAL)"
1717 depends on FB && PCI && EXPERIMENTAL
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1722 This is the frame buffer device driver for the 3DLabs Permedia3
1723 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1724 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1725 and maybe other boards.
1728 tristate "Fujitsu carmine frame buffer support"
1729 depends on FB && PCI
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1734 This is the frame buffer device driver for the Fujitsu Carmine chip.
1735 The driver provides two independent frame buffer devices.
1738 depends on FB_CARMINE
1739 prompt "DRAM timing"
1740 default FB_CARMINE_DRAM_EVAL
1742 config FB_CARMINE_DRAM_EVAL
1743 bool "Eval board timings"
1745 Use timings which work on the eval card.
1747 config CARMINE_DRAM_CUSTOM
1748 bool "Custom board timings"
1750 Use custom board timings.
1754 bool "Au1100 LCD Driver"
1755 depends on (FB = y) && MIPS && SOC_AU1100
1756 select FB_CFB_FILLRECT
1757 select FB_CFB_COPYAREA
1758 select FB_CFB_IMAGEBLIT
1760 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1761 various panels and CRTs by passing in kernel cmd line option
1762 au1100fb:panel=<name>.
1765 bool "Au1200 LCD Driver"
1766 depends on (FB = y) && MIPS && SOC_AU1200
1767 select FB_CFB_FILLRECT
1768 select FB_CFB_COPYAREA
1769 select FB_CFB_IMAGEBLIT
1771 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1772 various panels and CRTs by passing in kernel cmd line option
1773 au1200fb:panel=<name>.
1776 bool "VT8500 LCD Driver"
1777 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1778 select FB_WMT_GE_ROPS
1779 select FB_SYS_IMAGEBLIT
1781 This is the framebuffer driver for VIA VT8500 integrated LCD
1785 bool "WM8505 frame buffer support"
1786 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1787 select FB_WMT_GE_ROPS
1788 select FB_SYS_IMAGEBLIT
1790 This is the framebuffer driver for WonderMedia WM8505
1791 integrated LCD controller.
1793 source "drivers/video/geode/Kconfig"
1796 tristate "HD64461 Frame Buffer support"
1797 depends on FB && HD64461
1798 select FB_CFB_FILLRECT
1799 select FB_CFB_COPYAREA
1800 select FB_CFB_IMAGEBLIT
1802 This is the frame buffer device driver for the Hitachi HD64461 LCD
1806 bool "PMAG-AA TURBOchannel framebuffer support"
1807 depends on (FB = y) && TC
1808 select FB_CFB_FILLRECT
1809 select FB_CFB_COPYAREA
1810 select FB_CFB_IMAGEBLIT
1812 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1813 used mainly in the MIPS-based DECstation series.
1816 tristate "PMAG-BA TURBOchannel framebuffer support"
1818 select FB_CFB_FILLRECT
1819 select FB_CFB_COPYAREA
1820 select FB_CFB_IMAGEBLIT
1822 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1823 used mainly in the MIPS-based DECstation series.
1826 tristate "PMAGB-B TURBOchannel framebuffer support"
1828 select FB_CFB_FILLRECT
1829 select FB_CFB_COPYAREA
1830 select FB_CFB_IMAGEBLIT
1832 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1833 in the MIPS-based DECstation series. The card is currently only
1834 supported in 1280x1024x8 mode.
1837 bool "Maxine (Personal DECstation) onboard framebuffer support"
1838 depends on (FB = y) && MACH_DECSTATION
1839 select FB_CFB_FILLRECT
1840 select FB_CFB_COPYAREA
1841 select FB_CFB_IMAGEBLIT
1843 Support for the onboard framebuffer (1024x768x8) in the Personal
1844 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1848 bool "G364 frame buffer support"
1849 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1850 select FB_CFB_FILLRECT
1851 select FB_CFB_COPYAREA
1852 select FB_CFB_IMAGEBLIT
1854 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1855 Olivetti M700-10 systems.
1858 bool "Motorola 68328 native frame buffer support"
1859 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1864 Say Y here if you want to support the built-in frame buffer of
1865 the Motorola 68328 CPU family.
1868 tristate "PXA168/910 LCD framebuffer support"
1869 depends on FB && (CPU_PXA168 || CPU_PXA910)
1870 select FB_CFB_FILLRECT
1871 select FB_CFB_COPYAREA
1872 select FB_CFB_IMAGEBLIT
1874 Frame buffer driver for the built-in LCD controller in the Marvell
1878 tristate "PXA LCD framebuffer support"
1879 depends on FB && ARCH_PXA
1880 select FB_CFB_FILLRECT
1881 select FB_CFB_COPYAREA
1882 select FB_CFB_IMAGEBLIT
1884 Frame buffer driver for the built-in LCD controller in the Intel
1887 This driver is also available as a module ( = code which can be
1888 inserted and removed from the running kernel whenever you want). The
1889 module will be called pxafb. If you want to compile it as a module,
1890 say M here and read <file:Documentation/kbuild/modules.txt>.
1894 config FB_PXA_OVERLAY
1895 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1897 depends on FB_PXA && (PXA27x || PXA3xx)
1899 config FB_PXA_SMARTPANEL
1900 bool "PXA Smartpanel LCD support"
1904 config FB_PXA_PARAMETERS
1905 bool "PXA LCD command line parameters"
1909 Enable the use of kernel command line or module parameters
1910 to configure the physical properties of the LCD panel when
1911 using the PXA LCD driver.
1913 This option allows you to override the panel parameters
1914 supplied by the platform in order to support multiple
1915 different models of flatpanel. If you will only be using a
1916 single model of flatpanel then you can safely leave this
1919 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1922 tristate "PXA3xx 2D graphics accelerator driver"
1925 Kernelspace driver for the 2D graphics controller unit (GCU)
1926 found on PXA3xx processors. There is a counterpart driver in the
1927 DirectFB suite, see http://www.directfb.org/
1929 If you compile this as a module, it will be called pxa3xx_gcu.
1932 tristate "2700G LCD framebuffer support"
1933 depends on FB && ARCH_PXA
1934 select FB_CFB_FILLRECT
1935 select FB_CFB_COPYAREA
1936 select FB_CFB_IMAGEBLIT
1938 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1942 bool "Enable debugging info via debugfs"
1943 depends on FB_MBX && DEBUG_FS
1946 Enable this if you want debugging information using the debug
1947 filesystem (debugfs)
1952 tristate "Freescale DIU framebuffer support"
1953 depends on FB && FSL_SOC
1954 select FB_MODE_HELPERS
1955 select FB_CFB_FILLRECT
1956 select FB_CFB_COPYAREA
1957 select FB_CFB_IMAGEBLIT
1958 select PPC_LIB_RHEAP
1960 Framebuffer driver for the Freescale SoC DIU
1963 tristate "W100 frame buffer support"
1964 depends on FB && ARCH_PXA
1965 select FB_CFB_FILLRECT
1966 select FB_CFB_COPYAREA
1967 select FB_CFB_IMAGEBLIT
1969 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1970 It can also drive the w3220 chip found on iPAQ hx4700.
1972 This driver is also available as a module ( = code which can be
1973 inserted and removed from the running kernel whenever you want). The
1974 module will be called w100fb. If you want to compile it as a module,
1975 say M here and read <file:Documentation/kbuild/modules.txt>.
1979 config FB_SH_MOBILE_LCDC
1980 tristate "SuperH Mobile LCDC framebuffer support"
1981 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1982 select FB_SYS_FILLRECT
1983 select FB_SYS_COPYAREA
1984 select FB_SYS_IMAGEBLIT
1986 select FB_DEFERRED_IO
1988 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1990 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1992 config FB_SH_MOBILE_HDMI
1993 tristate "SuperH Mobile HDMI controller support"
1994 depends on FB_SH_MOBILE_LCDC
1995 select FB_MODE_HELPERS
2000 Driver for the on-chip SH-Mobile HDMI controller.
2002 config FB_SH_MOBILE_MERAM
2003 tristate "SuperH Mobile MERAM read ahead support for LCDC"
2004 depends on FB_SH_MOBILE_LCDC
2007 Enable MERAM support for the SH-Mobile LCD controller.
2009 This will allow for caching of the framebuffer to provide more
2010 reliable access under heavy main memory bus traffic situations.
2011 Up to 4 memory channels can be configured, allowing 4 RGB or
2012 2 YCbCr framebuffers to be configured.
2015 tristate "Toshiba Mobile IO FrameBuffer support"
2016 depends on FB && MFD_CORE
2017 select FB_CFB_FILLRECT
2018 select FB_CFB_COPYAREA
2019 select FB_CFB_IMAGEBLIT
2021 Frame buffer driver for the Toshiba Mobile IO integrated as found
2022 on the Sharp SL-6000 series
2024 This driver is also available as a module ( = code which can be
2025 inserted and removed from the running kernel whenever you want). The
2026 module will be called tmiofb. If you want to compile it as a module,
2027 say M here and read <file:Documentation/kbuild/modules.txt>.
2031 config FB_TMIO_ACCELL
2032 bool "tmiofb acceleration"
2037 tristate "Samsung S3C framebuffer support"
2038 depends on FB && (S3C_DEV_FB || S5P_DEV_FIMD0 || S5P_DEV_FIMD1)
2039 select FB_CFB_FILLRECT
2040 select FB_CFB_COPYAREA
2041 select FB_CFB_IMAGEBLIT
2042 select FB_EXYNOS_FIMD_V8
2044 Frame buffer driver for the built-in FB controller in the Samsung
2045 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2046 and the S3C64XX series such as the S3C6400 and S3C6410.
2048 These chips all have the same basic framebuffer design with the
2049 actual capabilities depending on the chip. For instance the S3C6400
2050 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2051 currently only have two.
2053 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2056 bool "Samsung MIPI DSIM"
2060 This enables support for Samsung MIPI DSIM feature
2062 config FB_EXYNOS_FIMD_V8
2063 bool "regiter extensions for FIMD version 8"
2064 depends on FB_S3C && ARCH_EXYNOS5
2067 config FB_EYYNOS_TRACE_UNDERRUN
2068 bool "Framebuffer FIFO underrun trace"
2069 depends on FB_S3C && ARCH_EXYNOS5
2073 config FB_EXYNOS_FIMD_MC
2074 bool "Support of media controller on FIMD for local path"
2075 depends on FB_S3C && ARCH_EXYNOS5 && MEDIA_CONTROLLER
2079 config FB_EXYNOS_FIMD_MC_WB
2080 bool "Support of media controller on FIMD for writeback to GScaler"
2081 depends on FB_S3C && ARCH_EXYNOS5 && MEDIA_CONTROLLER
2085 config FB_S3C_DEBUG_REGWRITE
2086 bool "Debug register writes"
2089 Show all register writes via printk(KERN_DEBUG)
2091 config VIDEO_SAMSUNG_MEMSIZE_FIMD
2092 int "Memory size in kbytes for FIMD0"
2097 tristate "S3C2410 LCD framebuffer support"
2098 depends on FB && ARCH_S3C2410
2099 select FB_CFB_FILLRECT
2100 select FB_CFB_COPYAREA
2101 select FB_CFB_IMAGEBLIT
2103 Frame buffer driver for the built-in LCD controller in the Samsung
2106 This driver is also available as a module ( = code which can be
2107 inserted and removed from the running kernel whenever you want). The
2108 module will be called s3c2410fb. If you want to compile it as a module,
2109 say M here and read <file:Documentation/kbuild/modules.txt>.
2112 config FB_S3C2410_DEBUG
2113 bool "S3C2410 lcd debug messages"
2114 depends on FB_S3C2410
2116 Turn on debugging messages. Note that you can set/unset at run time
2119 config S5P_MIPI_DSI2
2120 tristate "Samsung SoC MIPI-DSI support."
2121 depends on !FB_S5P_MIPI_DSIM && (ARCH_S5PV210 || ARCH_EXYNOS4)
2124 This enables support for MIPI-DSI device.
2127 tristate "Samsung SoC DP support"
2128 depends on FB_S3C && ARCH_EXYNOS5
2131 This enables support for DP device.
2134 bool "NUC900 LCD framebuffer support"
2135 depends on FB && ARCH_W90X900
2136 select FB_CFB_FILLRECT
2137 select FB_CFB_COPYAREA
2138 select FB_CFB_IMAGEBLIT
2140 Frame buffer driver for the built-in LCD controller in the Nuvoton
2143 config GPM1040A0_320X240
2144 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2145 depends on FB_NUC900
2147 config FB_NUC900_DEBUG
2148 bool "NUC900 lcd debug messages"
2149 depends on FB_NUC900
2151 Turn on debugging messages. Note that you can set/unset at run time
2155 tristate "Silicon Motion SM501 framebuffer support"
2156 depends on FB && MFD_SM501
2157 select FB_CFB_FILLRECT
2158 select FB_CFB_COPYAREA
2159 select FB_CFB_IMAGEBLIT
2161 Frame buffer driver for the CRT and LCD controllers in the Silicon
2164 This driver is also available as a module ( = code which can be
2165 inserted and removed from the running kernel whenever you want). The
2166 module will be called sm501fb. If you want to compile it as a module,
2167 say M here and read <file:Documentation/kbuild/modules.txt>.
2172 tristate "Displaylink USB Framebuffer support"
2173 depends on FB && USB
2174 select FB_MODE_HELPERS
2175 select FB_SYS_FILLRECT
2176 select FB_SYS_COPYAREA
2177 select FB_SYS_IMAGEBLIT
2179 select FB_DEFERRED_IO
2181 This is a kernel framebuffer driver for DisplayLink USB devices.
2182 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2183 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2184 To compile as a module, choose M here: the module name is udlfb.
2186 config FB_PNX4008_DUM
2187 tristate "Display Update Module support on Philips PNX4008 board"
2188 depends on FB && ARCH_PNX4008
2190 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2192 config FB_PNX4008_DUM_RGB
2193 tristate "RGB Framebuffer support on Philips PNX4008 board"
2194 depends on FB_PNX4008_DUM
2195 select FB_CFB_FILLRECT
2196 select FB_CFB_COPYAREA
2197 select FB_CFB_IMAGEBLIT
2199 Say Y here to enable support for PNX4008 RGB Framebuffer
2201 config FB_IBM_GXT4500
2202 tristate "Framebuffer support for IBM GXT4500P adaptor"
2203 depends on FB && PPC
2204 select FB_CFB_FILLRECT
2205 select FB_CFB_COPYAREA
2206 select FB_CFB_IMAGEBLIT
2208 Say Y here to enable support for the IBM GXT4500P display
2209 adaptor, found on some IBM System P (pSeries) machines.
2212 tristate "PS3 GPU framebuffer driver"
2213 depends on FB && PS3_PS3AV
2214 select FB_SYS_FILLRECT
2215 select FB_SYS_COPYAREA
2216 select FB_SYS_IMAGEBLIT
2218 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2220 Include support for the virtual frame buffer in the PS3 platform.
2222 config FB_PS3_DEFAULT_SIZE_M
2223 int "PS3 default frame buffer size (in MiB)"
2227 This is the default size (in MiB) of the virtual frame buffer in
2229 The default value can be overridden on the kernel command line
2230 using the "ps3fb" option (e.g. "ps3fb=9M");
2233 tristate "Xilinx frame buffer support"
2234 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2235 select FB_CFB_FILLRECT
2236 select FB_CFB_COPYAREA
2237 select FB_CFB_IMAGEBLIT
2239 Include support for the Xilinx ML300/ML403 reference design
2240 framebuffer. ML300 carries a 640*480 LCD display on the board,
2241 ML403 uses a standard DB15 VGA connector.
2244 tristate "Cobalt server LCD frame buffer support"
2245 depends on FB && MIPS_COBALT
2248 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2249 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2250 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2251 select FB_CFB_FILLRECT
2252 select FB_CFB_COPYAREA
2253 select FB_CFB_IMAGEBLIT
2255 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2256 (D)STN/TFT LCD Controller.
2257 Supports display resolutions up to 1024x1024 pixel, grayscale and
2258 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2259 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2260 panels <= 320 pixel horizontal resolution.
2263 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2264 depends on FB && ARCH_DAVINCI_DA8XX
2265 select FB_CFB_FILLRECT
2266 select FB_CFB_COPYAREA
2267 select FB_CFB_IMAGEBLIT
2269 This is the frame buffer device driver for the TI LCD controller
2270 found on DA8xx/OMAP-L1xx SoCs.
2274 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2276 select FB_SYS_FILLRECT
2277 select FB_SYS_COPYAREA
2278 select FB_SYS_IMAGEBLIT
2281 This is a `virtual' frame buffer device. It operates on a chunk of
2282 unswappable kernel memory instead of on the memory of a graphics
2283 board. This means you cannot see any output sent to this frame
2284 buffer device, while it does consume precious memory. The main use
2285 of this frame buffer device is testing and debugging the frame
2286 buffer subsystem. Do NOT enable it for normal systems! To protect
2287 the innocent, it has to be enabled explicitly at boot time using the
2288 kernel option `video=vfb:'.
2290 To compile this driver as a module, choose M here: the
2291 module will be called vfb. In order to load it, you must use
2292 the vfb_enable=1 option.
2296 config XEN_FBDEV_FRONTEND
2297 tristate "Xen virtual frame buffer support"
2298 depends on FB && XEN
2299 select FB_SYS_FILLRECT
2300 select FB_SYS_COPYAREA
2301 select FB_SYS_IMAGEBLIT
2303 select FB_DEFERRED_IO
2304 select XEN_XENBUS_FRONTEND
2307 This driver implements the front-end of the Xen virtual
2308 frame buffer driver. It communicates with a back-end
2312 tristate "E-Ink Metronome/8track controller support"
2314 select FB_SYS_FILLRECT
2315 select FB_SYS_COPYAREA
2316 select FB_SYS_IMAGEBLIT
2318 select FB_DEFERRED_IO
2320 This driver implements support for the E-Ink Metronome
2321 controller. The pre-release name for this device was 8track
2322 and could also have been called by some vendors as PVI-nnnn.
2325 tristate "Fujitsu MB862xx GDC support"
2327 depends on PCI || (OF && PPC)
2328 select FB_CFB_FILLRECT
2329 select FB_CFB_COPYAREA
2330 select FB_CFB_IMAGEBLIT
2332 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2335 prompt "GDC variant"
2336 depends on FB_MB862XX
2338 config FB_MB862XX_PCI_GDC
2339 bool "Carmine/Coral-P(A) GDC"
2342 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2343 PCI graphics controller devices.
2345 config FB_MB862XX_LIME
2347 depends on OF && PPC
2348 select FB_FOREIGN_ENDIAN
2349 select FB_LITTLE_ENDIAN
2351 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2355 config FB_MB862XX_I2C
2356 bool "Support I2C bus on MB862XX GDC"
2357 depends on FB_MB862XX && I2C
2360 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2361 driver to support accessing I2C devices on controller's I2C bus.
2362 These are usually some video decoder chips.
2365 tristate "EP93XX frame buffer support"
2366 depends on FB && ARCH_EP93XX
2367 select FB_CFB_FILLRECT
2368 select FB_CFB_COPYAREA
2369 select FB_CFB_IMAGEBLIT
2371 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2372 This driver is also available as a module. The module will be called
2375 config FB_PRE_INIT_FB
2376 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2377 depends on FB && FB_MB862XX_LIME
2379 Select this option if display contents should be inherited as set by
2383 tristate "MSM Framebuffer support"
2384 depends on FB && ARCH_MSM
2385 select FB_CFB_FILLRECT
2386 select FB_CFB_COPYAREA
2387 select FB_CFB_IMAGEBLIT
2390 tristate "MX3 Framebuffer support"
2391 depends on FB && MX3_IPU
2392 select FB_CFB_FILLRECT
2393 select FB_CFB_COPYAREA
2394 select FB_CFB_IMAGEBLIT
2397 This is a framebuffer device for the i.MX31 LCD Controller. So
2398 far only synchronous displays are supported. If you plan to use
2399 an LCD display with your i.MX31 system, say Y here.
2401 config FB_BROADSHEET
2402 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2404 select FB_SYS_FILLRECT
2405 select FB_SYS_COPYAREA
2406 select FB_SYS_IMAGEBLIT
2408 select FB_DEFERRED_IO
2410 This driver implements support for the E-Ink Broadsheet
2411 controller. The release name for this device was Epson S1D13521
2412 and could also have been called by other names when coupled with
2416 tristate "JZ4740 LCD framebuffer support"
2417 depends on FB && MACH_JZ4740
2418 select FB_SYS_FILLRECT
2419 select FB_SYS_COPYAREA
2420 select FB_SYS_IMAGEBLIT
2422 Framebuffer support for the JZ4740 SoC.
2425 tristate "MXS LCD framebuffer support"
2426 depends on FB && ARCH_MXS
2427 select FB_CFB_FILLRECT
2428 select FB_CFB_COPYAREA
2429 select FB_CFB_IMAGEBLIT
2431 Framebuffer support for the MXS SoC.
2433 config FB_PUV3_UNIGFX
2434 tristate "PKUnity v3 Unigfx framebuffer support"
2435 depends on FB && UNICORE32 && ARCH_PUV3
2436 select FB_SYS_FILLRECT
2437 select FB_SYS_COPYAREA
2438 select FB_SYS_IMAGEBLIT
2441 Choose this option if you want to use the Unigfx device as a
2442 framebuffer device. Without the support of PCI & AGP.
2444 source "drivers/video/omap/Kconfig"
2445 source "drivers/video/omap2/Kconfig"
2447 source "drivers/video/backlight/Kconfig"
2448 source "drivers/video/display/Kconfig"
2451 source "drivers/video/console/Kconfig"
2454 if FB || SGI_NEWPORT_CONSOLE
2455 source "drivers/video/logo/Kconfig"