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"
32 config VIDEO_OUTPUT_CONTROL
33 tristate "Lowlevel video output switch controls"
35 This framework adds support for low-level control of the video
39 tristate "Support for frame buffer devices"
41 The frame buffer device provides an abstraction for the graphics
42 hardware. It represents the frame buffer of some video hardware and
43 allows application software to access the graphics hardware through
44 a well-defined interface, so the software doesn't need to know
45 anything about the low-level (hardware register) stuff.
47 Frame buffer devices work identically across the different
48 architectures supported by Linux and make the implementation of
49 application programs easier and more portable; at this point, an X
50 server exists which uses the frame buffer device exclusively.
51 On several non-X86 architectures, the frame buffer device is the
52 only way to use the graphics hardware.
54 The device is accessed through special device nodes, usually located
55 in the /dev directory, i.e. /dev/fb*.
57 You need an utility program called fbset to make full use of frame
58 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
59 and the Framebuffer-HOWTO at
60 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
63 Say Y here and to the driver for your graphics board below if you
64 are compiling a kernel for a non-x86 architecture.
66 If you are compiling for the x86 architecture, you can say Y if you
67 want to play with it, but it is not essential. Please note that
68 running graphical applications that directly touch the hardware
69 (e.g. an accelerated X server) and that are not frame buffer
70 device-aware may cause unexpected results. If unsure, say N.
73 bool "Enable firmware EDID"
77 This enables access to the EDID transferred from the firmware.
78 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
79 transfers do not work for your driver and if you are using
80 nvidiafb, i810fb or savagefb.
82 In general, choosing Y for this option is safe. If you
83 experience extremely long delays while booting before you get
84 something on your display, try setting this to N. Matrox cards in
85 combination with certain motherboards and monitors are known to
86 suffer from this problem.
95 config FB_BOOT_VESA_SUPPORT
100 If true, at least one selected framebuffer driver can take advantage
101 of VESA video modes set at an early boot stage via the vga= parameter.
103 config FB_CFB_FILLRECT
108 Include the cfb_fillrect function for generic software rectangle
109 filling. This is used by drivers that don't provide their own
110 (accelerated) version.
112 config FB_CFB_COPYAREA
117 Include the cfb_copyarea function for generic software area copying.
118 This is used by drivers that don't provide their own (accelerated)
121 config FB_CFB_IMAGEBLIT
126 Include the cfb_imageblit function for generic software image
127 blitting. This is used by drivers that don't provide their own
128 (accelerated) version.
130 config FB_CFB_REV_PIXELS_IN_BYTE
135 Allow generic frame-buffer functions to work on displays with 1, 2
136 and 4 bits per pixel depths which has opposite order of pixels in
137 byte order to bytes in long order.
139 config FB_SYS_FILLRECT
144 Include the sys_fillrect function for generic software rectangle
145 filling. This is used by drivers that don't provide their own
146 (accelerated) version and the framebuffer is in system RAM.
148 config FB_SYS_COPYAREA
153 Include the sys_copyarea function for generic software area copying.
154 This is used by drivers that don't provide their own (accelerated)
155 version and the framebuffer is in system RAM.
157 config FB_SYS_IMAGEBLIT
162 Include the sys_imageblit function for generic software image
163 blitting. This is used by drivers that don't provide their own
164 (accelerated) version and the framebuffer is in system RAM.
166 menuconfig FB_FOREIGN_ENDIAN
167 bool "Framebuffer foreign endianness support"
170 This menu will let you enable support for the framebuffers with
171 non-native endianness (e.g. Little-Endian framebuffer on a
172 Big-Endian machine). Most probably you don't have such hardware,
173 so it's safe to say "n" here.
176 prompt "Choice endianness support"
177 depends on FB_FOREIGN_ENDIAN
179 config FB_BOTH_ENDIAN
180 bool "Support for Big- and Little-Endian framebuffers"
183 bool "Support for Big-Endian framebuffers only"
185 config FB_LITTLE_ENDIAN
186 bool "Support for Little-Endian framebuffers only"
195 config FB_WMT_GE_ROPS
200 Include functions for accelerated rectangle filling and area
201 copying using WonderMedia Graphics Engine operations.
203 config FB_DEFERRED_IO
210 depends on FB_DEFERRED_IO
217 Common utility functions useful to fbdev drivers of VGA-based
228 select BACKLIGHT_LCD_SUPPORT
229 select BACKLIGHT_CLASS_DEVICE
232 config FB_MODE_HELPERS
233 bool "Enable Video Mode Handling Helpers"
237 This enables functions for handling video modes using the
238 Generalized Timing Formula and the EDID parser. A few drivers rely
239 on this feature such as the radeonfb, rivafb, and the i810fb. If
240 your driver does not take advantage of this feature, choosing Y will
241 just increase the kernel size by about 5K.
243 config FB_TILEBLITTING
244 bool "Enable Tile Blitting Support"
248 This enables tile blitting. Tile blitting is a drawing technique
249 where the screen is divided into rectangular sections (tiles), whereas
250 the standard blitting divides the screen into pixels. Because the
251 default drawing element is a tile, drawing functions will be passed
252 parameters in terms of number of tiles instead of number of pixels.
253 For example, to draw a single character, instead of using bitmaps,
254 an index to an array of bitmaps will be used. To clear or move a
255 rectangular section of a screen, the rectangle will be described in
256 terms of number of tiles in the x- and y-axis.
258 This is particularly important to one driver, matroxfb. If
261 comment "Frame buffer hardware drivers"
264 source "drivers/video/samsung/Kconfig"
265 source "drivers/video/samsung_extdisp/Kconfig"
266 source "drivers/video/samsung_duallcd/Kconfig"
269 tristate "Cirrus Logic support"
270 depends on FB && (ZORRO || PCI)
271 select FB_CFB_FILLRECT
272 select FB_CFB_COPYAREA
273 select FB_CFB_IMAGEBLIT
275 This enables support for Cirrus Logic GD542x/543x based boards on
276 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
278 If you have a PCI-based system, this enables support for these
279 chips: GD-543x, GD-544x, GD-5480.
281 Please read the file <file:Documentation/fb/cirrusfb.txt>.
283 Say N unless you have such a graphics board or plan to get one
284 before you next recompile the kernel.
287 tristate "Permedia2 support"
288 depends on FB && ((AMIGA && BROKEN) || PCI)
289 select FB_CFB_FILLRECT
290 select FB_CFB_COPYAREA
291 select FB_CFB_IMAGEBLIT
293 This is the frame buffer device driver for cards based on
294 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
295 The driver was tested on the following cards:
296 Diamond FireGL 1000 PRO AGP
297 ELSA Gloria Synergy PCI
298 Appian Jeronimo PRO (both heads) PCI
299 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
300 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
301 ASK Graphic Blaster Exxtreme AGP
303 To compile this driver as a module, choose M here: the
304 module will be called pm2fb.
306 config FB_PM2_FIFO_DISCONNECT
307 bool "enable FIFO disconnect feature"
308 depends on FB_PM2 && PCI
310 Support the Permedia2 FIFO disconnect feature.
313 tristate "ARM PrimeCell PL110 support"
314 depends on FB && ARM && ARM_AMBA
315 select FB_CFB_FILLRECT
316 select FB_CFB_COPYAREA
317 select FB_CFB_IMAGEBLIT
319 This framebuffer device driver is for the ARM PrimeCell PL110
320 Colour LCD controller. ARM PrimeCells provide the building
321 blocks for System on a Chip devices.
323 If you want to compile this as a module (=code which can be
324 inserted into and removed from the running kernel), say M
325 here and read <file:Documentation/kbuild/modules.txt>. The module
326 will be called amba-clcd.
329 bool "Acorn VIDC support"
330 depends on (FB = y) && ARM && ARCH_ACORN
331 select FB_CFB_FILLRECT
332 select FB_CFB_COPYAREA
333 select FB_CFB_IMAGEBLIT
335 This is the frame buffer device driver for the Acorn VIDC graphics
336 hardware found in Acorn RISC PCs and other ARM-based machines. If
340 bool "CLPS711X LCD support"
341 depends on (FB = y) && ARM && ARCH_CLPS711X
342 select FB_CFB_FILLRECT
343 select FB_CFB_COPYAREA
344 select FB_CFB_IMAGEBLIT
346 Say Y to enable the Framebuffer driver for the CLPS7111 and
350 bool "SA-1100 LCD support"
351 depends on (FB = y) && ARM && ARCH_SA1100
352 select FB_CFB_FILLRECT
353 select FB_CFB_COPYAREA
354 select FB_CFB_IMAGEBLIT
356 This is a framebuffer device for the SA-1100 LCD Controller.
357 See <http://www.linux-fbdev.org/> for information on framebuffer
360 If you plan to use the LCD display with your SA-1100 system, say
364 tristate "Freescale i.MX LCD support"
365 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
366 select FB_CFB_FILLRECT
367 select FB_CFB_COPYAREA
368 select FB_CFB_IMAGEBLIT
371 tristate "CyberPro 2000/2010/5000 support"
372 depends on FB && PCI && (BROKEN || !SPARC64)
373 select FB_CFB_FILLRECT
374 select FB_CFB_COPYAREA
375 select FB_CFB_IMAGEBLIT
377 This enables support for the Integraphics CyberPro 20x0 and 5000
378 VGA chips used in the Rebel.com Netwinder and other machines.
379 Say Y if you have a NetWinder or a graphics card containing this
380 device, otherwise say N.
382 config FB_CYBER2000_DDC
383 bool "DDC for CyberPro support"
384 depends on FB_CYBER2000
388 Say Y here if you want DDC support for your CyberPro graphics
389 card. This is only I2C bus support, driver does not use EDID.
391 config FB_CYBER2000_I2C
392 bool "CyberPro 2000/2010/5000 I2C support"
393 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
396 Enable support for the I2C video decoder interface on the
397 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
398 on the Netwinder machines for the SAA7111 video capture.
402 depends on (FB = y) && APOLLO
404 select FB_CFB_FILLRECT
405 select FB_CFB_IMAGEBLIT
409 depends on (FB = y) && Q40
411 select FB_CFB_FILLRECT
412 select FB_CFB_COPYAREA
413 select FB_CFB_IMAGEBLIT
416 tristate "Amiga native chipset support"
417 depends on FB && AMIGA
419 This is the frame buffer device driver for the builtin graphics
420 chipset found in Amigas.
422 To compile this driver as a module, choose M here: the
423 module will be called amifb.
426 bool "Amiga OCS chipset support"
429 This enables support for the original Agnus and Denise video chips,
430 found in the Amiga 1000 and most A500's and A2000's. If you intend
431 to run Linux on any of these systems, say Y; otherwise say N.
434 bool "Amiga ECS chipset support"
437 This enables support for the Enhanced Chip Set, found in later
438 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
439 you intend to run Linux on any of these systems, say Y; otherwise
443 bool "Amiga AGA chipset support"
446 This enables support for the Advanced Graphics Architecture (also
447 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
448 and CD32. If you intend to run Linux on any of these systems, say Y;
452 bool "Amiga FrameMaster II/Rainbow II support"
453 depends on (FB = y) && ZORRO
454 select FB_CFB_FILLRECT
455 select FB_CFB_COPYAREA
456 select FB_CFB_IMAGEBLIT
458 This is the frame buffer device driver for the Amiga FrameMaster
459 card from BSC (exhibited 1992 but not shipped as a CBM product).
462 tristate "Arc Monochrome LCD board support"
464 select FB_SYS_FILLRECT
465 select FB_SYS_COPYAREA
466 select FB_SYS_IMAGEBLIT
469 This enables support for the Arc Monochrome LCD board. The board
470 is based on the KS-108 lcd controller and is typically a matrix
471 of 2*n chips. This driver was tested with a 128x64 panel. This
472 driver supports it for use with x86 SBCs through a 16 bit GPIO
473 interface (8 bit data, 8 bit control). If you anticipate using
474 this driver, say Y or M; otherwise say N. You must specify the
475 GPIO IO address to be used for setting control and data.
478 bool "Atari native chipset support"
479 depends on (FB = y) && ATARI
480 select FB_CFB_FILLRECT
481 select FB_CFB_COPYAREA
482 select FB_CFB_IMAGEBLIT
484 This is the frame buffer device driver for the builtin graphics
485 chipset found in Ataris.
488 bool "Open Firmware frame buffer device support"
489 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
490 select FB_CFB_FILLRECT
491 select FB_CFB_COPYAREA
492 select FB_CFB_IMAGEBLIT
495 Say Y if you want support with Open Firmware for your graphics
499 bool "Apple \"control\" display support"
500 depends on (FB = y) && PPC_PMAC && PPC32
501 select FB_CFB_FILLRECT
502 select FB_CFB_COPYAREA
503 select FB_CFB_IMAGEBLIT
506 This driver supports a frame buffer for the graphics adapter in the
507 Power Macintosh 7300 and others.
510 bool "Apple \"platinum\" display support"
511 depends on (FB = y) && PPC_PMAC && PPC32
512 select FB_CFB_FILLRECT
513 select FB_CFB_COPYAREA
514 select FB_CFB_IMAGEBLIT
517 This driver supports a frame buffer for the "platinum" graphics
518 adapter in some Power Macintoshes.
521 bool "Apple \"valkyrie\" display support"
522 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
523 select FB_CFB_FILLRECT
524 select FB_CFB_COPYAREA
525 select FB_CFB_IMAGEBLIT
528 This driver supports a frame buffer for the "valkyrie" graphics
529 adapter in some Power Macintoshes.
532 bool "Chips 65550 display support"
533 depends on (FB = y) && PPC32 && PCI
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
538 This is the frame buffer device driver for the Chips & Technologies
539 65550 graphics chip in PowerBooks.
542 bool "Asiliant (Chips) 69000 display support"
543 depends on (FB = y) && PCI
544 select FB_CFB_FILLRECT
545 select FB_CFB_COPYAREA
546 select FB_CFB_IMAGEBLIT
548 This is the frame buffer device driver for the Asiliant 69030 chipset
551 bool "IMS Twin Turbo display support"
552 depends on (FB = y) && PCI
553 select FB_CFB_IMAGEBLIT
554 select FB_MACMODES if PPC
556 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
557 many Macintosh and compatible computers.
560 tristate "VGA 16-color graphics support"
561 depends on FB && (X86 || PPC)
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
566 select FONT_8x16 if FRAMEBUFFER_CONSOLE
568 This is the frame buffer device driver for VGA 16 color graphic
569 cards. Say Y if you have such a card.
571 To compile this driver as a module, choose M here: the
572 module will be called vga16fb.
574 config FB_BF54X_LQ043
575 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
576 depends on FB && (BF54x) && !BF542
577 select FB_CFB_FILLRECT
578 select FB_CFB_COPYAREA
579 select FB_CFB_IMAGEBLIT
581 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
583 config FB_BFIN_T350MCQB
584 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
585 depends on FB && BLACKFIN
587 select FB_CFB_FILLRECT
588 select FB_CFB_COPYAREA
589 select FB_CFB_IMAGEBLIT
591 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
592 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
593 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
595 config FB_BFIN_LQ035Q1
596 tristate "SHARP LQ035Q1DH02 TFT LCD"
597 depends on FB && BLACKFIN && SPI
598 select FB_CFB_FILLRECT
599 select FB_CFB_COPYAREA
600 select FB_CFB_IMAGEBLIT
603 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
604 the Blackfin Landscape LCD EZ-Extender Card.
605 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
606 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
608 To compile this driver as a module, choose M here: the
609 module will be called bfin-lq035q1-fb.
611 config FB_BF537_LQ035
612 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
613 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
614 select FB_CFB_FILLRECT
615 select FB_CFB_COPYAREA
616 select FB_CFB_IMAGEBLIT
619 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
622 To compile this driver as a module, choose M here: the
623 module will be called bf537-lq035.
626 tristate "Blackfin ADV7393 Video encoder"
627 depends on FB && BLACKFIN
629 select FB_CFB_FILLRECT
630 select FB_CFB_COPYAREA
631 select FB_CFB_IMAGEBLIT
633 This is the framebuffer device for a ADV7393 video encoder
634 attached to a Blackfin on the PPI port.
635 If your Blackfin board has a ADV7393 select Y.
637 To compile this driver as a module, choose M here: the
638 module will be called bfin_adv7393fb.
641 prompt "Video mode support"
642 depends on FB_BFIN_7393
652 bool 'NTSC 640x480 (Experimental)'
655 bool 'PAL 640x480 (Experimental)'
658 bool 'NTSC 720x480 YCbCR input'
661 bool 'PAL 720x576 YCbCR input'
666 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
667 depends on (FB_BFIN_7393)
668 default ADV7393_1XMEM
678 tristate "HP STI frame buffer device support"
679 depends on FB && PARISC
680 select FB_CFB_FILLRECT
681 select FB_CFB_COPYAREA
682 select FB_CFB_IMAGEBLIT
687 STI refers to the HP "Standard Text Interface" which is a set of
688 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
689 Enabling this option will implement the linux framebuffer device
690 using calls to the STI BIOS routines for initialisation.
692 If you enable this option, you will get a planar framebuffer device
693 /dev/fb which will work on the most common HP graphic cards of the
694 NGLE family, including the artist chips (in the 7xx and Bxxx series),
695 HCRX, HCRX24, CRX, CRX24 and VisEG series.
697 It is safe to enable this option, so you should probably say "Y".
700 bool "Generic Macintosh display support"
701 depends on (FB = y) && MAC
702 select FB_CFB_FILLRECT
703 select FB_CFB_COPYAREA
704 select FB_CFB_IMAGEBLIT
709 depends on (FB = y) && DIO
710 select FB_CFB_IMAGEBLIT
714 tristate "TGA/SFB+ framebuffer support"
715 depends on FB && (ALPHA || TC)
716 select FB_CFB_FILLRECT
717 select FB_CFB_COPYAREA
718 select FB_CFB_IMAGEBLIT
721 This is the frame buffer device driver for generic TGA and SFB+
722 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
723 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
724 TURBOchannel cards, also known as PMAGD-A, -B and -C.
726 Due to hardware limitations ZLX-E2 and E3 cards are not supported
727 for DECstation 5000/200 systems. Additionally due to firmware
728 limitations these cards may cause troubles with booting DECstation
729 5000/240 and /260 systems, but are fully supported under Linux if
730 you manage to get it going. ;-)
732 Say Y if you have one of those.
735 tristate "Userspace VESA VGA graphics support"
736 depends on FB && CONNECTOR
737 select FB_CFB_FILLRECT
738 select FB_CFB_COPYAREA
739 select FB_CFB_IMAGEBLIT
740 select FB_MODE_HELPERS
742 This is the frame buffer driver for generic VBE 2.0 compliant
743 graphic cards. It can also take advantage of VBE 3.0 features,
744 such as refresh rate adjustment.
746 This driver generally provides more features than vesafb but
747 requires a userspace helper application called 'v86d'. See
748 <file:Documentation/fb/uvesafb.txt> for more information.
753 bool "VESA VGA graphics support"
754 depends on (FB = y) && X86
755 select FB_CFB_FILLRECT
756 select FB_CFB_COPYAREA
757 select FB_CFB_IMAGEBLIT
758 select FB_BOOT_VESA_SUPPORT
760 This is the frame buffer device driver for generic VESA 2.0
761 compliant graphic cards. The older VESA 1.2 cards are not supported.
762 You will get a boot time penguin logo at no additional cost. Please
763 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
766 bool "EFI-based Framebuffer Support"
767 depends on (FB = y) && X86 && EFI
768 select FB_CFB_FILLRECT
769 select FB_CFB_COPYAREA
770 select FB_CFB_IMAGEBLIT
772 This is the EFI frame buffer device driver. If the firmware on
773 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
774 using the EFI framebuffer as your console.
777 tristate "N411 Apollo/Hecuba devkit support"
778 depends on FB && X86 && MMU
779 select FB_SYS_FILLRECT
780 select FB_SYS_COPYAREA
781 select FB_SYS_IMAGEBLIT
783 select FB_DEFERRED_IO
786 This enables support for the Apollo display controller in its
787 Hecuba form using the n411 devkit.
790 tristate "Hercules mono graphics support"
793 Say Y here if you have a Hercules mono graphics card.
795 To compile this driver as a module, choose M here: the
796 module will be called hgafb.
798 As this card technology is at least 25 years old,
799 most people will answer N here.
802 tristate "SGI Visual Workstation framebuffer support"
803 depends on FB && X86_VISWS
804 select FB_CFB_FILLRECT
805 select FB_CFB_COPYAREA
806 select FB_CFB_IMAGEBLIT
808 SGI Visual Workstation support for framebuffer graphics.
811 bool "SGI Graphics Backend frame buffer support"
812 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
813 select FB_CFB_FILLRECT
814 select FB_CFB_COPYAREA
815 select FB_CFB_IMAGEBLIT
817 This is the frame buffer device driver for SGI Graphics Backend.
818 This chip is used in SGI O2 and Visual Workstation 320/540.
821 int "Video memory size in MB"
825 This is the amount of memory reserved for the framebuffer,
826 which can be any value between 1MB and 8MB.
829 bool "SBUS and UPA framebuffers"
830 depends on (FB = y) && SPARC
832 Say Y if you want support for SBUS or UPA based frame buffer device.
836 depends on (FB = y) && (SPARC && FB_SBUS)
837 select FB_CFB_FILLRECT
838 select FB_CFB_COPYAREA
839 select FB_CFB_IMAGEBLIT
841 This is the frame buffer device driver for the BWtwo frame buffer.
844 bool "CGthree support"
845 depends on (FB = y) && (SPARC && FB_SBUS)
846 select FB_CFB_FILLRECT
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This is the frame buffer device driver for the CGthree frame buffer.
853 bool "CGsix (GX,TurboGX) support"
854 depends on (FB = y) && (SPARC && FB_SBUS)
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the frame buffer device driver for the CGsix (GX, TurboGX)
862 bool "Creator/Creator3D/Elite3D support"
863 depends on FB_SBUS && SPARC64
864 select FB_CFB_COPYAREA
865 select FB_CFB_IMAGEBLIT
867 This is the frame buffer device driver for the Creator, Creator3D,
868 and Elite3D graphics boards.
871 bool "TCX (SS4/SS5 only) support"
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 TCX 24/8bit frame
881 bool "CGfourteen (SX) support"
883 select FB_CFB_FILLRECT
884 select FB_CFB_COPYAREA
885 select FB_CFB_IMAGEBLIT
887 This is the frame buffer device driver for the CGfourteen frame
888 buffer on Desktop SPARCsystems with the SX graphics option.
891 bool "P9100 (Sparcbook 3 only) support"
893 select FB_CFB_FILLRECT
894 select FB_CFB_COPYAREA
895 select FB_CFB_IMAGEBLIT
897 This is the frame buffer device driver for the P9100 card
898 supported on Sparcbook 3 machines.
901 bool "Leo (ZX) support"
903 select FB_CFB_FILLRECT
904 select FB_CFB_COPYAREA
905 select FB_CFB_IMAGEBLIT
907 This is the frame buffer device driver for the SBUS-based Sun ZX
908 (leo) frame buffer cards.
911 bool "IGA 168x display support"
912 depends on (FB = y) && SPARC32
913 select FB_CFB_FILLRECT
914 select FB_CFB_COPYAREA
915 select FB_CFB_IMAGEBLIT
917 This is the framebuffer device for the INTERGRAPHICS 1680 and
918 successor frame buffer cards.
921 bool "Sun XVR-500 3DLABS Wildcat support"
922 depends on (FB = y) && PCI && SPARC64
923 select FB_CFB_FILLRECT
924 select FB_CFB_COPYAREA
925 select FB_CFB_IMAGEBLIT
927 This is the framebuffer device for the Sun XVR-500 and similar
928 graphics cards based upon the 3DLABS Wildcat chipset. The driver
929 only works on sparc64 systems where the system firmware has
930 mostly initialized the card already. It is treated as a
931 completely dumb framebuffer device.
934 bool "Sun XVR-2500 3DLABS Wildcat support"
935 depends on (FB = y) && PCI && SPARC64
936 select FB_CFB_FILLRECT
937 select FB_CFB_COPYAREA
938 select FB_CFB_IMAGEBLIT
940 This is the framebuffer device for the Sun XVR-2500 and similar
941 graphics cards based upon the 3DLABS Wildcat chipset. The driver
942 only works on sparc64 systems where the system firmware has
943 mostly initialized the card already. It is treated as a
944 completely dumb framebuffer device.
947 bool "Sun XVR-1000 support"
948 depends on (FB = y) && SPARC64
949 select FB_CFB_FILLRECT
950 select FB_CFB_COPYAREA
951 select FB_CFB_IMAGEBLIT
953 This is the framebuffer device for the Sun XVR-1000 and similar
954 graphics cards. The driver only works on sparc64 systems where
955 the system firmware has mostly initialized the card already. It
956 is treated as a completely dumb framebuffer device.
959 tristate "NEC PowerVR 2 display support"
960 depends on FB && SH_DREAMCAST
961 select FB_CFB_FILLRECT
962 select FB_CFB_COPYAREA
963 select FB_CFB_IMAGEBLIT
965 Say Y here if you have a PowerVR 2 card in your box. If you plan to
966 run linux on your Dreamcast, you will have to say Y here.
967 This driver may or may not work on other PowerVR 2 cards, but is
968 totally untested. Use at your own risk. If unsure, say N.
970 To compile this driver as a module, choose M here: the
971 module will be called pvr2fb.
973 You can pass several parameters to the driver at boot time or at
974 module load time. The parameters look like "video=pvr2:XXX", where
975 the meaning of XXX can be found at the end of the main source file
976 (<file:drivers/video/pvr2fb.c>). Please see the file
977 <file:Documentation/fb/pvr2fb.txt>.
980 bool "Epson 1355 framebuffer support"
981 depends on (FB = y) && ARCH_CEIVA
982 select FB_CFB_FILLRECT
983 select FB_CFB_COPYAREA
984 select FB_CFB_IMAGEBLIT
986 Build in support for the SED1355 Epson Research Embedded RAMDAC
987 LCD/CRT Controller (since redesignated as the S1D13505) as a
988 framebuffer. Product specs at
989 <http://vdc.epson.com/>.
992 tristate "Epson S1D13XXX framebuffer support"
994 select FB_CFB_FILLRECT
995 select FB_CFB_COPYAREA
996 select FB_CFB_IMAGEBLIT
998 Support for S1D13XXX framebuffer device family (currently only
999 working with S1D13806). Product specs at
1000 <http://vdc.epson.com/>
1003 tristate "AT91/AT32 LCD Controller support"
1004 depends on FB && HAVE_FB_ATMEL
1005 select FB_CFB_FILLRECT
1006 select FB_CFB_COPYAREA
1007 select FB_CFB_IMAGEBLIT
1009 This enables support for the AT91/AT32 LCD Controller.
1012 bool "Frame Buffer in internal SRAM"
1013 depends on FB_ATMEL && ARCH_AT91SAM9261
1015 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1016 to let frame buffer in external SDRAM.
1019 bool "Use a STN display with AT91/AT32 LCD Controller"
1020 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1023 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1024 Controller. Say N if you want to connect a TFT.
1029 tristate "nVidia Framebuffer Support"
1030 depends on FB && PCI
1031 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1032 select FB_MODE_HELPERS
1033 select FB_CFB_FILLRECT
1034 select FB_CFB_COPYAREA
1035 select FB_CFB_IMAGEBLIT
1039 This driver supports graphics boards with the nVidia chips, TNT
1040 and newer. For very old chipsets, such as the RIVA128, then use
1042 Say Y if you have such a graphics board.
1044 To compile this driver as a module, choose M here: the
1045 module will be called nvidiafb.
1047 config FB_NVIDIA_I2C
1048 bool "Enable DDC Support"
1049 depends on FB_NVIDIA
1052 This enables I2C support for nVidia Chipsets. This is used
1053 only for getting EDID information from the attached display
1054 allowing for robust video mode handling and switching.
1056 Because fbdev-2.6 requires that drivers must be able to
1057 independently validate video mode parameters, you should say Y
1060 config FB_NVIDIA_DEBUG
1061 bool "Lots of debug output"
1062 depends on FB_NVIDIA
1065 Say Y here if you want the nVidia driver to output all sorts
1066 of debugging information to provide to the maintainer when
1067 something goes wrong.
1069 config FB_NVIDIA_BACKLIGHT
1070 bool "Support for backlight control"
1071 depends on FB_NVIDIA
1074 Say Y here if you want to control the backlight of your display.
1077 tristate "nVidia Riva support"
1078 depends on FB && PCI
1079 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1080 select FB_MODE_HELPERS
1081 select FB_CFB_FILLRECT
1082 select FB_CFB_COPYAREA
1083 select FB_CFB_IMAGEBLIT
1087 This driver supports graphics boards with the nVidia Riva/Geforce
1089 Say Y if you have such a graphics board.
1091 To compile this driver as a module, choose M here: the
1092 module will be called rivafb.
1095 bool "Enable DDC Support"
1099 This enables I2C support for nVidia Chipsets. This is used
1100 only for getting EDID information from the attached display
1101 allowing for robust video mode handling and switching.
1103 Because fbdev-2.6 requires that drivers must be able to
1104 independently validate video mode parameters, you should say Y
1107 config FB_RIVA_DEBUG
1108 bool "Lots of debug output"
1112 Say Y here if you want the Riva driver to output all sorts
1113 of debugging information to provide to the maintainer when
1114 something goes wrong.
1116 config FB_RIVA_BACKLIGHT
1117 bool "Support for backlight control"
1121 Say Y here if you want to control the backlight of your display.
1124 tristate "Intel 810/815 support (EXPERIMENTAL)"
1125 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1126 select FB_MODE_HELPERS
1127 select FB_CFB_FILLRECT
1128 select FB_CFB_COPYAREA
1129 select FB_CFB_IMAGEBLIT
1132 This driver supports the on-board graphics built in to the Intel 810
1133 and 815 chipsets. Say Y if you have and plan to use such a board.
1135 To compile this driver as a module, choose M here: the
1136 module will be called i810fb.
1138 For more information, please read
1139 <file:Documentation/fb/intel810.txt>
1142 bool "use VESA Generalized Timing Formula"
1145 If you say Y, then the VESA standard, Generalized Timing Formula
1146 or GTF, will be used to calculate the required video timing values
1147 per video mode. Since the GTF allows nondiscrete timings
1148 (nondiscrete being a range of values as opposed to discrete being a
1149 set of values), you'll be able to use any combination of horizontal
1150 and vertical resolutions, and vertical refresh rates without having
1151 to specify your own timing parameters. This is especially useful
1152 to maximize the performance of an aging display, or if you just
1153 have a display with nonstandard dimensions. A VESA compliant
1154 monitor is recommended, but can still work with non-compliant ones.
1155 If you need or want this, then select this option. The timings may
1156 not be compliant with Intel's recommended values. Use at your own
1159 If you say N, the driver will revert to discrete video timings
1160 using a set recommended by Intel in their documentation.
1165 bool "Enable DDC Support"
1166 depends on FB_I810 && FB_I810_GTF
1171 tristate "Intel LE80578 (Vermilion) support"
1172 depends on FB && PCI && X86
1173 select FB_MODE_HELPERS
1174 select FB_CFB_FILLRECT
1175 select FB_CFB_COPYAREA
1176 select FB_CFB_IMAGEBLIT
1178 This driver supports the LE80578 (Vermilion Range) chipset
1180 config FB_CARILLO_RANCH
1181 tristate "Intel Carillo Ranch support"
1182 depends on FB_LE80578 && FB && PCI && X86
1184 This driver supports the LE80578 (Carillo Ranch) board
1187 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1188 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1189 select FB_MODE_HELPERS
1190 select FB_CFB_FILLRECT
1191 select FB_CFB_COPYAREA
1192 select FB_CFB_IMAGEBLIT
1193 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1194 depends on !DRM_I915
1196 This driver supports the on-board graphics built in to the Intel
1197 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1198 Say Y if you have and plan to use such a board.
1200 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1202 To compile this driver as a module, choose M here: the
1203 module will be called intelfb.
1205 For more information, please read <file:Documentation/fb/intelfb.txt>
1207 config FB_INTEL_DEBUG
1208 bool "Intel driver Debug Messages"
1211 Say Y here if you want the Intel driver to output all sorts
1212 of debugging information to provide to the maintainer when
1213 something goes wrong.
1216 bool "DDC/I2C for Intel framebuffer support"
1221 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1224 tristate "Matrox acceleration"
1225 depends on FB && PCI
1226 select FB_CFB_FILLRECT
1227 select FB_CFB_COPYAREA
1228 select FB_CFB_IMAGEBLIT
1229 select FB_TILEBLITTING
1230 select FB_MACMODES if PPC_PMAC
1232 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1233 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1234 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1235 Matrox G400, G450 or G550 card in your box.
1237 To compile this driver as a module, choose M here: the
1238 module will be called matroxfb.
1240 You can pass several parameters to the driver at boot time or at
1241 module load time. The parameters look like "video=matroxfb:XXX", and
1242 are described in <file:Documentation/fb/matroxfb.txt>.
1244 config FB_MATROX_MILLENIUM
1245 bool "Millennium I/II support"
1246 depends on FB_MATROX
1248 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1249 video card. If you select "Advanced lowlevel driver options" below,
1250 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1251 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1252 also use font widths different from 8.
1254 config FB_MATROX_MYSTIQUE
1255 bool "Mystique support"
1256 depends on FB_MATROX
1258 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1259 video card. If you select "Advanced lowlevel driver options" below,
1260 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1261 packed pixel and 32 bpp packed pixel. You can also use font widths
1265 bool "G100/G200/G400/G450/G550 support"
1266 depends on FB_MATROX
1268 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1269 video card. If you select "Advanced lowlevel driver options", you
1270 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1271 pixel and 32 bpp packed pixel. You can also use font widths
1274 If you need support for G400 secondary head, you must say Y to
1275 "Matrox I2C support" and "G400 second head support" right below.
1276 G450/G550 secondary head and digital output are supported without
1279 The driver starts in monitor mode. You must use the matroxset tool
1280 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1281 swap primary and secondary head outputs, or to change output mode.
1282 Secondary head driver always start in 640x480 resolution and you
1283 must use fbset to change it.
1285 Do not forget that second head supports only 16 and 32 bpp
1286 packed pixels, so it is a good idea to compile them into the kernel
1287 too. You can use only some font widths, as the driver uses generic
1288 painting procedures (the secondary head does not use acceleration
1291 G450/G550 hardware can display TV picture only from secondary CRTC,
1292 and it performs no scaling, so picture must have 525 or 625 lines.
1294 config FB_MATROX_I2C
1295 tristate "Matrox I2C support"
1296 depends on FB_MATROX
1299 This drivers creates I2C buses which are needed for accessing the
1300 DDC (I2C) bus present on all Matroxes, an I2C bus which
1301 interconnects Matrox optional devices, like MGA-TVO on G200 and
1302 G400, and the secondary head DDC bus, present on G400 only.
1304 You can say Y or M here if you want to experiment with monitor
1305 detection code. You must say Y or M here if you want to use either
1306 second head of G400 or MGA-TVO on G200 or G400.
1308 If you compile it as module, it will create a module named
1311 config FB_MATROX_MAVEN
1312 tristate "G400 second head support"
1313 depends on FB_MATROX_G && FB_MATROX_I2C
1315 WARNING !!! This support does not work with G450 !!!
1317 Say Y or M here if you want to use a secondary head (meaning two
1318 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1319 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1320 secondary head output is blanked while you are in X. With XFree
1321 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1322 the fbdev driver on first head and the fbdev driver on second head.
1324 If you compile it as module, two modules are created,
1325 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1326 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1327 also load i2c-matroxfb to get it to run.
1329 The driver starts in monitor mode and you must use the matroxset
1331 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1332 PAL or NTSC or to swap primary and secondary head outputs.
1333 Secondary head driver also always start in 640x480 resolution, you
1334 must use fbset to change it.
1336 Also do not forget that second head supports only 16 and 32 bpp
1337 packed pixels, so it is a good idea to compile them into the kernel
1338 too. You can use only some font widths, as the driver uses generic
1339 painting procedures (the secondary head does not use acceleration
1343 tristate "ATI Radeon display support"
1344 depends on FB && PCI
1345 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1346 select FB_MODE_HELPERS
1347 select FB_CFB_FILLRECT
1348 select FB_CFB_COPYAREA
1349 select FB_CFB_IMAGEBLIT
1350 select FB_MACMODES if PPC_OF
1352 Choose this option if you want to use an ATI Radeon graphics card as
1353 a framebuffer device. There are both PCI and AGP versions. You
1354 don't need to choose this to run the Radeon in plain VGA mode.
1356 There is a product page at
1357 http://products.amd.com/en-us/GraphicCardResult.aspx
1359 config FB_RADEON_I2C
1360 bool "DDC/I2C for ATI Radeon support"
1361 depends on FB_RADEON
1365 Say Y here if you want DDC/I2C support for your Radeon board.
1367 config FB_RADEON_BACKLIGHT
1368 bool "Support for backlight control"
1369 depends on FB_RADEON
1372 Say Y here if you want to control the backlight of your display.
1374 config FB_RADEON_DEBUG
1375 bool "Lots of debug output from Radeon driver"
1376 depends on FB_RADEON
1379 Say Y here if you want the Radeon driver to output all sorts
1380 of debugging information to provide to the maintainer when
1381 something goes wrong.
1384 tristate "ATI Rage128 display support"
1385 depends on FB && PCI
1386 select FB_CFB_FILLRECT
1387 select FB_CFB_COPYAREA
1388 select FB_CFB_IMAGEBLIT
1389 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1390 select FB_MACMODES if PPC_PMAC
1392 This driver supports graphics boards with the ATI Rage128 chips.
1393 Say Y if you have such a graphics board and read
1394 <file:Documentation/fb/aty128fb.txt>.
1396 To compile this driver as a module, choose M here: the
1397 module will be called aty128fb.
1399 config FB_ATY128_BACKLIGHT
1400 bool "Support for backlight control"
1401 depends on FB_ATY128
1404 Say Y here if you want to control the backlight of your display.
1407 tristate "ATI Mach64 display support" if PCI || ATARI
1408 depends on FB && !SPARC32
1409 select FB_CFB_FILLRECT
1410 select FB_CFB_COPYAREA
1411 select FB_CFB_IMAGEBLIT
1412 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1413 select FB_MACMODES if PPC
1415 This driver supports graphics boards with the ATI Mach64 chips.
1416 Say Y if you have such a graphics board.
1418 To compile this driver as a module, choose M here: the
1419 module will be called atyfb.
1422 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1423 depends on PCI && FB_ATY
1424 default y if SPARC64 && PCI
1426 Say Y here to support use of ATI's 64-bit Rage boards (or other
1427 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1428 framebuffer device. The ATI product support page for these boards
1429 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1431 config FB_ATY_GENERIC_LCD
1432 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1433 depends on FB_ATY_CT
1435 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1436 Rage XC, or Rage XL chipset.
1439 bool "Mach64 GX support" if PCI
1443 Say Y here to support use of the ATI Mach64 Graphics Expression
1444 board (or other boards based on the Mach64 GX chipset) as a
1445 framebuffer device. The ATI product support page for these boards
1447 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1449 config FB_ATY_BACKLIGHT
1450 bool "Support for backlight control"
1454 Say Y here if you want to control the backlight of your display.
1457 tristate "S3 Trio/Virge support"
1458 depends on FB && PCI
1459 select FB_CFB_FILLRECT
1460 select FB_CFB_COPYAREA
1461 select FB_CFB_IMAGEBLIT
1462 select FB_TILEBLITTING
1465 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1467 Driver for graphics boards with S3 Trio / S3 Virge chip.
1470 bool "DDC for S3 support"
1475 Say Y here if you want DDC support for your S3 graphics card.
1478 tristate "S3 Savage support"
1479 depends on FB && PCI && EXPERIMENTAL
1480 select FB_MODE_HELPERS
1481 select FB_CFB_FILLRECT
1482 select FB_CFB_COPYAREA
1483 select FB_CFB_IMAGEBLIT
1486 This driver supports notebooks and computers with S3 Savage PCI/AGP
1489 Say Y if you have such a graphics card.
1491 To compile this driver as a module, choose M here; the module
1492 will be called savagefb.
1494 config FB_SAVAGE_I2C
1495 bool "Enable DDC2 Support"
1496 depends on FB_SAVAGE
1499 This enables I2C support for S3 Savage Chipsets. This is used
1500 only for getting EDID information from the attached display
1501 allowing for robust video mode handling and switching.
1503 Because fbdev-2.6 requires that drivers must be able to
1504 independently validate video mode parameters, you should say Y
1507 config FB_SAVAGE_ACCEL
1508 bool "Enable Console Acceleration"
1509 depends on FB_SAVAGE
1512 This option will compile in console acceleration support. If
1513 the resulting framebuffer console has bothersome glitches, then
1517 tristate "SiS/XGI display support"
1518 depends on FB && PCI
1519 select FB_CFB_FILLRECT
1520 select FB_CFB_COPYAREA
1521 select FB_CFB_IMAGEBLIT
1522 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1524 This is the frame buffer device driver for the SiS 300, 315, 330
1525 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1526 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1528 To compile this driver as a module, choose M here; the module
1529 will be called sisfb.
1532 bool "SiS 300 series support"
1535 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1538 bool "SiS 315/330/340 series and XGI support"
1541 Say Y here to support use of the SiS 315, 330 and 340 series
1542 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1543 as XGI V3XT, V5, V8 and Z7.
1546 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1547 depends on FB && PCI && X86
1548 select FB_CFB_FILLRECT
1549 select FB_CFB_COPYAREA
1550 select FB_CFB_IMAGEBLIT
1555 This is the frame buffer device driver for Graphics chips of VIA
1556 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1557 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1559 Say Y if you have a VIA UniChrome graphics board.
1561 To compile this driver as a module, choose M here: the
1562 module will be called viafb.
1566 config FB_VIA_DIRECT_PROCFS
1567 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1571 Allow direct hardware access to some output registers via procfs.
1572 This is dangerous but may provide the only chance to get the
1573 correct output device configuration.
1574 Its use is strongly discouraged.
1576 config FB_VIA_X_COMPATIBILITY
1577 bool "X server compatibility"
1581 This option reduces the functionality (power saving, ...) of the
1582 framebuffer to avoid negative impact on the OpenChrome X server.
1583 If you use any X server other than fbdev you should enable this
1584 otherwise it should be safe to disable it and allow using all
1590 tristate "NeoMagic display support"
1591 depends on FB && PCI
1592 select FB_MODE_HELPERS
1593 select FB_CFB_FILLRECT
1594 select FB_CFB_COPYAREA
1595 select FB_CFB_IMAGEBLIT
1598 This driver supports notebooks with NeoMagic PCI chips.
1599 Say Y if you have such a graphics card.
1601 To compile this driver as a module, choose M here: the
1602 module will be called neofb.
1605 tristate "IMG Kyro support"
1606 depends on FB && PCI
1607 select FB_CFB_FILLRECT
1608 select FB_CFB_COPYAREA
1609 select FB_CFB_IMAGEBLIT
1611 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1614 To compile this driver as a module, choose M here: the
1615 module will be called kyrofb.
1618 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1619 depends on FB && PCI
1620 select FB_CFB_IMAGEBLIT
1621 select FB_CFB_FILLRECT
1622 select FB_CFB_COPYAREA
1623 select FB_MODE_HELPERS
1625 This driver supports graphics boards with the 3Dfx Banshee,
1626 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1627 such a graphics board.
1629 To compile this driver as a module, choose M here: the
1630 module will be called tdfxfb.
1632 config FB_3DFX_ACCEL
1633 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1634 depends on FB_3DFX && EXPERIMENTAL
1636 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1637 device driver with acceleration functions.
1640 bool "Enable DDC/I2C support"
1641 depends on FB_3DFX && EXPERIMENTAL
1645 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1648 tristate "3Dfx Voodoo Graphics (sst1) support"
1649 depends on FB && PCI
1650 select FB_CFB_FILLRECT
1651 select FB_CFB_COPYAREA
1652 select FB_CFB_IMAGEBLIT
1654 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1655 Voodoo2 (cvg) based graphics card.
1657 To compile this driver as a module, choose M here: the
1658 module will be called sstfb.
1660 WARNING: Do not use any application that uses the 3D engine
1661 (namely glide) while using this driver.
1662 Please read the <file:Documentation/fb/sstfb.txt> for supported
1663 options and other important info support.
1666 tristate "VIA VT8623 support"
1667 depends on FB && PCI
1668 select FB_CFB_FILLRECT
1669 select FB_CFB_COPYAREA
1670 select FB_CFB_IMAGEBLIT
1671 select FB_TILEBLITTING
1674 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1676 Driver for CastleRock integrated graphics core in the
1677 VIA VT8623 [Apollo CLE266] chipset.
1680 tristate "Trident/CyberXXX/CyberBlade support"
1681 depends on FB && PCI
1682 select FB_CFB_FILLRECT
1683 select FB_CFB_COPYAREA
1684 select FB_CFB_IMAGEBLIT
1686 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1687 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1689 There are also integrated versions of these chips called CyberXXXX,
1690 CyberImage or CyberBlade. These chips are mostly found in laptops
1691 but also on some motherboards including early VIA EPIA motherboards.
1692 For more information, read <file:Documentation/fb/tridentfb.txt>
1694 Say Y if you have such a graphics board.
1696 To compile this driver as a module, choose M here: the
1697 module will be called tridentfb.
1700 tristate "ARK 2000PV support"
1701 depends on FB && PCI
1702 select FB_CFB_FILLRECT
1703 select FB_CFB_COPYAREA
1704 select FB_CFB_IMAGEBLIT
1705 select FB_TILEBLITTING
1708 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1710 Driver for PCI graphics boards with ARK 2000PV chip
1711 and ICS 5342 RAMDAC.
1714 tristate "Permedia3 support (EXPERIMENTAL)"
1715 depends on FB && PCI && EXPERIMENTAL
1716 select FB_CFB_FILLRECT
1717 select FB_CFB_COPYAREA
1718 select FB_CFB_IMAGEBLIT
1720 This is the frame buffer device driver for the 3DLabs Permedia3
1721 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1722 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1723 and maybe other boards.
1726 tristate "Fujitsu carmine frame buffer support"
1727 depends on FB && PCI
1728 select FB_CFB_FILLRECT
1729 select FB_CFB_COPYAREA
1730 select FB_CFB_IMAGEBLIT
1732 This is the frame buffer device driver for the Fujitsu Carmine chip.
1733 The driver provides two independent frame buffer devices.
1736 depends on FB_CARMINE
1737 prompt "DRAM timing"
1738 default FB_CARMINE_DRAM_EVAL
1740 config FB_CARMINE_DRAM_EVAL
1741 bool "Eval board timings"
1743 Use timings which work on the eval card.
1745 config CARMINE_DRAM_CUSTOM
1746 bool "Custom board timings"
1748 Use custom board timings.
1752 bool "Au1100 LCD Driver"
1753 depends on (FB = y) && MIPS && SOC_AU1100
1754 select FB_CFB_FILLRECT
1755 select FB_CFB_COPYAREA
1756 select FB_CFB_IMAGEBLIT
1758 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1759 various panels and CRTs by passing in kernel cmd line option
1760 au1100fb:panel=<name>.
1763 bool "Au1200 LCD Driver"
1764 depends on (FB = y) && MIPS && SOC_AU1200
1765 select FB_CFB_FILLRECT
1766 select FB_CFB_COPYAREA
1767 select FB_CFB_IMAGEBLIT
1769 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1770 various panels and CRTs by passing in kernel cmd line option
1771 au1200fb:panel=<name>.
1774 bool "VT8500 LCD Driver"
1775 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1776 select FB_WMT_GE_ROPS
1777 select FB_SYS_IMAGEBLIT
1779 This is the framebuffer driver for VIA VT8500 integrated LCD
1783 bool "WM8505 frame buffer support"
1784 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1785 select FB_WMT_GE_ROPS
1786 select FB_SYS_IMAGEBLIT
1788 This is the framebuffer driver for WonderMedia WM8505
1789 integrated LCD controller.
1791 source "drivers/video/geode/Kconfig"
1794 tristate "HD64461 Frame Buffer support"
1795 depends on FB && HD64461
1796 select FB_CFB_FILLRECT
1797 select FB_CFB_COPYAREA
1798 select FB_CFB_IMAGEBLIT
1800 This is the frame buffer device driver for the Hitachi HD64461 LCD
1804 bool "PMAG-AA TURBOchannel framebuffer support"
1805 depends on (FB = y) && TC
1806 select FB_CFB_FILLRECT
1807 select FB_CFB_COPYAREA
1808 select FB_CFB_IMAGEBLIT
1810 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1811 used mainly in the MIPS-based DECstation series.
1814 tristate "PMAG-BA TURBOchannel framebuffer support"
1816 select FB_CFB_FILLRECT
1817 select FB_CFB_COPYAREA
1818 select FB_CFB_IMAGEBLIT
1820 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1821 used mainly in the MIPS-based DECstation series.
1824 tristate "PMAGB-B TURBOchannel framebuffer support"
1826 select FB_CFB_FILLRECT
1827 select FB_CFB_COPYAREA
1828 select FB_CFB_IMAGEBLIT
1830 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1831 in the MIPS-based DECstation series. The card is currently only
1832 supported in 1280x1024x8 mode.
1835 bool "Maxine (Personal DECstation) onboard framebuffer support"
1836 depends on (FB = y) && MACH_DECSTATION
1837 select FB_CFB_FILLRECT
1838 select FB_CFB_COPYAREA
1839 select FB_CFB_IMAGEBLIT
1841 Support for the onboard framebuffer (1024x768x8) in the Personal
1842 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1846 bool "G364 frame buffer support"
1847 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1853 Olivetti M700-10 systems.
1856 bool "Motorola 68328 native frame buffer support"
1857 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1858 select FB_CFB_FILLRECT
1859 select FB_CFB_COPYAREA
1860 select FB_CFB_IMAGEBLIT
1862 Say Y here if you want to support the built-in frame buffer of
1863 the Motorola 68328 CPU family.
1866 tristate "PXA168/910 LCD framebuffer support"
1867 depends on FB && (CPU_PXA168 || CPU_PXA910)
1868 select FB_CFB_FILLRECT
1869 select FB_CFB_COPYAREA
1870 select FB_CFB_IMAGEBLIT
1872 Frame buffer driver for the built-in LCD controller in the Marvell
1876 tristate "PXA LCD framebuffer support"
1877 depends on FB && ARCH_PXA
1878 select FB_CFB_FILLRECT
1879 select FB_CFB_COPYAREA
1880 select FB_CFB_IMAGEBLIT
1882 Frame buffer driver for the built-in LCD controller in the Intel
1885 This driver is also available as a module ( = code which can be
1886 inserted and removed from the running kernel whenever you want). The
1887 module will be called pxafb. If you want to compile it as a module,
1888 say M here and read <file:Documentation/kbuild/modules.txt>.
1892 config FB_PXA_OVERLAY
1893 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1895 depends on FB_PXA && (PXA27x || PXA3xx)
1897 config FB_PXA_SMARTPANEL
1898 bool "PXA Smartpanel LCD support"
1902 config FB_PXA_PARAMETERS
1903 bool "PXA LCD command line parameters"
1907 Enable the use of kernel command line or module parameters
1908 to configure the physical properties of the LCD panel when
1909 using the PXA LCD driver.
1911 This option allows you to override the panel parameters
1912 supplied by the platform in order to support multiple
1913 different models of flatpanel. If you will only be using a
1914 single model of flatpanel then you can safely leave this
1917 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1920 tristate "PXA3xx 2D graphics accelerator driver"
1923 Kernelspace driver for the 2D graphics controller unit (GCU)
1924 found on PXA3xx processors. There is a counterpart driver in the
1925 DirectFB suite, see http://www.directfb.org/
1927 If you compile this as a module, it will be called pxa3xx_gcu.
1930 tristate "2700G LCD framebuffer support"
1931 depends on FB && ARCH_PXA
1932 select FB_CFB_FILLRECT
1933 select FB_CFB_COPYAREA
1934 select FB_CFB_IMAGEBLIT
1936 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1940 bool "Enable debugging info via debugfs"
1941 depends on FB_MBX && DEBUG_FS
1944 Enable this if you want debugging information using the debug
1945 filesystem (debugfs)
1950 tristate "Freescale DIU framebuffer support"
1951 depends on FB && FSL_SOC
1952 select FB_MODE_HELPERS
1953 select FB_CFB_FILLRECT
1954 select FB_CFB_COPYAREA
1955 select FB_CFB_IMAGEBLIT
1956 select PPC_LIB_RHEAP
1958 Framebuffer driver for the Freescale SoC DIU
1961 tristate "W100 frame buffer support"
1962 depends on FB && ARCH_PXA
1963 select FB_CFB_FILLRECT
1964 select FB_CFB_COPYAREA
1965 select FB_CFB_IMAGEBLIT
1967 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1968 It can also drive the w3220 chip found on iPAQ hx4700.
1970 This driver is also available as a module ( = code which can be
1971 inserted and removed from the running kernel whenever you want). The
1972 module will be called w100fb. If you want to compile it as a module,
1973 say M here and read <file:Documentation/kbuild/modules.txt>.
1977 config FB_SH_MOBILE_LCDC
1978 tristate "SuperH Mobile LCDC framebuffer support"
1979 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1980 select FB_SYS_FILLRECT
1981 select FB_SYS_COPYAREA
1982 select FB_SYS_IMAGEBLIT
1984 select FB_DEFERRED_IO
1986 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1988 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1990 config FB_SH_MOBILE_HDMI
1991 tristate "SuperH Mobile HDMI controller support"
1992 depends on FB_SH_MOBILE_LCDC
1993 select FB_MODE_HELPERS
1998 Driver for the on-chip SH-Mobile HDMI controller.
2000 config FB_SH_MOBILE_MERAM
2001 tristate "SuperH Mobile MERAM read ahead support for LCDC"
2002 depends on FB_SH_MOBILE_LCDC
2005 Enable MERAM support for the SH-Mobile LCD controller.
2007 This will allow for caching of the framebuffer to provide more
2008 reliable access under heavy main memory bus traffic situations.
2009 Up to 4 memory channels can be configured, allowing 4 RGB or
2010 2 YCbCr framebuffers to be configured.
2013 tristate "Toshiba Mobile IO FrameBuffer support"
2014 depends on FB && MFD_CORE
2015 select FB_CFB_FILLRECT
2016 select FB_CFB_COPYAREA
2017 select FB_CFB_IMAGEBLIT
2019 Frame buffer driver for the Toshiba Mobile IO integrated as found
2020 on the Sharp SL-6000 series
2022 This driver is also available as a module ( = code which can be
2023 inserted and removed from the running kernel whenever you want). The
2024 module will be called tmiofb. If you want to compile it as a module,
2025 say M here and read <file:Documentation/kbuild/modules.txt>.
2029 config FB_TMIO_ACCELL
2030 bool "tmiofb acceleration"
2035 tristate "Samsung S3C framebuffer support"
2036 depends on FB && (S3C_DEV_FB || S5P_DEV_FIMD0 || S5P_DEV_FIMD1)
2037 select FB_CFB_FILLRECT
2038 select FB_CFB_COPYAREA
2039 select FB_CFB_IMAGEBLIT
2040 select FB_EXYNOS_FIMD_V8
2042 Frame buffer driver for the built-in FB controller in the Samsung
2043 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2044 and the S3C64XX series such as the S3C6400 and S3C6410.
2046 These chips all have the same basic framebuffer design with the
2047 actual capabilities depending on the chip. For instance the S3C6400
2048 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2049 currently only have two.
2051 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2054 bool "Samsung MIPI DSIM"
2058 This enables support for Samsung MIPI DSIM feature
2060 config FB_EXYNOS_FIMD_V8
2061 bool "regiter extensions for FIMD version 8"
2062 depends on FB_S3C && ARCH_EXYNOS5
2065 config FB_EYYNOS_TRACE_UNDERRUN
2066 bool "Framebuffer FIFO underrun trace"
2067 depends on FB_S3C && ARCH_EXYNOS5
2071 config FB_EXYNOS_FIMD_MC
2072 bool "Support of media controller on FIMD for local path"
2073 depends on FB_S3C && ARCH_EXYNOS5 && MEDIA_CONTROLLER
2077 config FB_EXYNOS_FIMD_MC_WB
2078 bool "Support of media controller on FIMD for writeback to GScaler"
2079 depends on FB_S3C && ARCH_EXYNOS5 && MEDIA_CONTROLLER
2083 config FB_S3C_DEBUG_REGWRITE
2084 bool "Debug register writes"
2087 Show all register writes via printk(KERN_DEBUG)
2089 config VIDEO_SAMSUNG_MEMSIZE_FIMD
2090 int "Memory size in kbytes for FIMD0"
2095 tristate "S3C2410 LCD framebuffer support"
2096 depends on FB && ARCH_S3C2410
2097 select FB_CFB_FILLRECT
2098 select FB_CFB_COPYAREA
2099 select FB_CFB_IMAGEBLIT
2101 Frame buffer driver for the built-in LCD controller in the Samsung
2104 This driver is also available as a module ( = code which can be
2105 inserted and removed from the running kernel whenever you want). The
2106 module will be called s3c2410fb. If you want to compile it as a module,
2107 say M here and read <file:Documentation/kbuild/modules.txt>.
2110 config FB_S3C2410_DEBUG
2111 bool "S3C2410 lcd debug messages"
2112 depends on FB_S3C2410
2114 Turn on debugging messages. Note that you can set/unset at run time
2117 config S5P_MIPI_DSI2
2118 tristate "Samsung SoC MIPI-DSI support."
2119 depends on !FB_S5P_MIPI_DSIM && (ARCH_S5PV210 || ARCH_EXYNOS4)
2122 This enables support for MIPI-DSI device.
2125 tristate "Samsung SoC DP support"
2126 depends on FB_S3C && ARCH_EXYNOS5
2129 This enables support for DP device.
2132 bool "NUC900 LCD framebuffer support"
2133 depends on FB && ARCH_W90X900
2134 select FB_CFB_FILLRECT
2135 select FB_CFB_COPYAREA
2136 select FB_CFB_IMAGEBLIT
2138 Frame buffer driver for the built-in LCD controller in the Nuvoton
2141 config GPM1040A0_320X240
2142 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2143 depends on FB_NUC900
2145 config FB_NUC900_DEBUG
2146 bool "NUC900 lcd debug messages"
2147 depends on FB_NUC900
2149 Turn on debugging messages. Note that you can set/unset at run time
2153 tristate "Silicon Motion SM501 framebuffer support"
2154 depends on FB && MFD_SM501
2155 select FB_CFB_FILLRECT
2156 select FB_CFB_COPYAREA
2157 select FB_CFB_IMAGEBLIT
2159 Frame buffer driver for the CRT and LCD controllers in the Silicon
2162 This driver is also available as a module ( = code which can be
2163 inserted and removed from the running kernel whenever you want). The
2164 module will be called sm501fb. If you want to compile it as a module,
2165 say M here and read <file:Documentation/kbuild/modules.txt>.
2170 tristate "Displaylink USB Framebuffer support"
2171 depends on FB && USB
2172 select FB_MODE_HELPERS
2173 select FB_SYS_FILLRECT
2174 select FB_SYS_COPYAREA
2175 select FB_SYS_IMAGEBLIT
2177 select FB_DEFERRED_IO
2179 This is a kernel framebuffer driver for DisplayLink USB devices.
2180 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2181 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2182 To compile as a module, choose M here: the module name is udlfb.
2184 config FB_PNX4008_DUM
2185 tristate "Display Update Module support on Philips PNX4008 board"
2186 depends on FB && ARCH_PNX4008
2188 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2190 config FB_PNX4008_DUM_RGB
2191 tristate "RGB Framebuffer support on Philips PNX4008 board"
2192 depends on FB_PNX4008_DUM
2193 select FB_CFB_FILLRECT
2194 select FB_CFB_COPYAREA
2195 select FB_CFB_IMAGEBLIT
2197 Say Y here to enable support for PNX4008 RGB Framebuffer
2199 config FB_IBM_GXT4500
2200 tristate "Framebuffer support for IBM GXT4500P adaptor"
2201 depends on FB && PPC
2202 select FB_CFB_FILLRECT
2203 select FB_CFB_COPYAREA
2204 select FB_CFB_IMAGEBLIT
2206 Say Y here to enable support for the IBM GXT4500P display
2207 adaptor, found on some IBM System P (pSeries) machines.
2210 tristate "PS3 GPU framebuffer driver"
2211 depends on FB && PS3_PS3AV
2212 select FB_SYS_FILLRECT
2213 select FB_SYS_COPYAREA
2214 select FB_SYS_IMAGEBLIT
2216 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2218 Include support for the virtual frame buffer in the PS3 platform.
2220 config FB_PS3_DEFAULT_SIZE_M
2221 int "PS3 default frame buffer size (in MiB)"
2225 This is the default size (in MiB) of the virtual frame buffer in
2227 The default value can be overridden on the kernel command line
2228 using the "ps3fb" option (e.g. "ps3fb=9M");
2231 tristate "Xilinx frame buffer support"
2232 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2233 select FB_CFB_FILLRECT
2234 select FB_CFB_COPYAREA
2235 select FB_CFB_IMAGEBLIT
2237 Include support for the Xilinx ML300/ML403 reference design
2238 framebuffer. ML300 carries a 640*480 LCD display on the board,
2239 ML403 uses a standard DB15 VGA connector.
2242 tristate "Cobalt server LCD frame buffer support"
2243 depends on FB && MIPS_COBALT
2246 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2247 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2248 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2249 select FB_CFB_FILLRECT
2250 select FB_CFB_COPYAREA
2251 select FB_CFB_IMAGEBLIT
2253 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2254 (D)STN/TFT LCD Controller.
2255 Supports display resolutions up to 1024x1024 pixel, grayscale and
2256 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2257 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2258 panels <= 320 pixel horizontal resolution.
2261 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2262 depends on FB && ARCH_DAVINCI_DA8XX
2263 select FB_CFB_FILLRECT
2264 select FB_CFB_COPYAREA
2265 select FB_CFB_IMAGEBLIT
2267 This is the frame buffer device driver for the TI LCD controller
2268 found on DA8xx/OMAP-L1xx SoCs.
2272 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2274 select FB_SYS_FILLRECT
2275 select FB_SYS_COPYAREA
2276 select FB_SYS_IMAGEBLIT
2279 This is a `virtual' frame buffer device. It operates on a chunk of
2280 unswappable kernel memory instead of on the memory of a graphics
2281 board. This means you cannot see any output sent to this frame
2282 buffer device, while it does consume precious memory. The main use
2283 of this frame buffer device is testing and debugging the frame
2284 buffer subsystem. Do NOT enable it for normal systems! To protect
2285 the innocent, it has to be enabled explicitly at boot time using the
2286 kernel option `video=vfb:'.
2288 To compile this driver as a module, choose M here: the
2289 module will be called vfb. In order to load it, you must use
2290 the vfb_enable=1 option.
2294 config XEN_FBDEV_FRONTEND
2295 tristate "Xen virtual frame buffer support"
2296 depends on FB && XEN
2297 select FB_SYS_FILLRECT
2298 select FB_SYS_COPYAREA
2299 select FB_SYS_IMAGEBLIT
2301 select FB_DEFERRED_IO
2302 select XEN_XENBUS_FRONTEND
2305 This driver implements the front-end of the Xen virtual
2306 frame buffer driver. It communicates with a back-end
2310 tristate "E-Ink Metronome/8track controller support"
2312 select FB_SYS_FILLRECT
2313 select FB_SYS_COPYAREA
2314 select FB_SYS_IMAGEBLIT
2316 select FB_DEFERRED_IO
2318 This driver implements support for the E-Ink Metronome
2319 controller. The pre-release name for this device was 8track
2320 and could also have been called by some vendors as PVI-nnnn.
2323 tristate "Fujitsu MB862xx GDC support"
2325 depends on PCI || (OF && PPC)
2326 select FB_CFB_FILLRECT
2327 select FB_CFB_COPYAREA
2328 select FB_CFB_IMAGEBLIT
2330 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2333 prompt "GDC variant"
2334 depends on FB_MB862XX
2336 config FB_MB862XX_PCI_GDC
2337 bool "Carmine/Coral-P(A) GDC"
2340 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2341 PCI graphics controller devices.
2343 config FB_MB862XX_LIME
2345 depends on OF && PPC
2346 select FB_FOREIGN_ENDIAN
2347 select FB_LITTLE_ENDIAN
2349 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2353 config FB_MB862XX_I2C
2354 bool "Support I2C bus on MB862XX GDC"
2355 depends on FB_MB862XX && I2C
2358 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2359 driver to support accessing I2C devices on controller's I2C bus.
2360 These are usually some video decoder chips.
2363 tristate "EP93XX frame buffer support"
2364 depends on FB && ARCH_EP93XX
2365 select FB_CFB_FILLRECT
2366 select FB_CFB_COPYAREA
2367 select FB_CFB_IMAGEBLIT
2369 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2370 This driver is also available as a module. The module will be called
2373 config FB_PRE_INIT_FB
2374 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2375 depends on FB && FB_MB862XX_LIME
2377 Select this option if display contents should be inherited as set by
2381 tristate "MSM Framebuffer support"
2382 depends on FB && ARCH_MSM
2383 select FB_CFB_FILLRECT
2384 select FB_CFB_COPYAREA
2385 select FB_CFB_IMAGEBLIT
2388 tristate "MX3 Framebuffer support"
2389 depends on FB && MX3_IPU
2390 select FB_CFB_FILLRECT
2391 select FB_CFB_COPYAREA
2392 select FB_CFB_IMAGEBLIT
2395 This is a framebuffer device for the i.MX31 LCD Controller. So
2396 far only synchronous displays are supported. If you plan to use
2397 an LCD display with your i.MX31 system, say Y here.
2399 config FB_BROADSHEET
2400 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2402 select FB_SYS_FILLRECT
2403 select FB_SYS_COPYAREA
2404 select FB_SYS_IMAGEBLIT
2406 select FB_DEFERRED_IO
2408 This driver implements support for the E-Ink Broadsheet
2409 controller. The release name for this device was Epson S1D13521
2410 and could also have been called by other names when coupled with
2414 tristate "JZ4740 LCD framebuffer support"
2415 depends on FB && MACH_JZ4740
2416 select FB_SYS_FILLRECT
2417 select FB_SYS_COPYAREA
2418 select FB_SYS_IMAGEBLIT
2420 Framebuffer support for the JZ4740 SoC.
2423 tristate "MXS LCD framebuffer support"
2424 depends on FB && ARCH_MXS
2425 select FB_CFB_FILLRECT
2426 select FB_CFB_COPYAREA
2427 select FB_CFB_IMAGEBLIT
2429 Framebuffer support for the MXS SoC.
2431 config FB_PUV3_UNIGFX
2432 tristate "PKUnity v3 Unigfx framebuffer support"
2433 depends on FB && UNICORE32 && ARCH_PUV3
2434 select FB_SYS_FILLRECT
2435 select FB_SYS_COPYAREA
2436 select FB_SYS_IMAGEBLIT
2439 Choose this option if you want to use the Unigfx device as a
2440 framebuffer device. Without the support of PCI & AGP.
2442 source "drivers/video/omap/Kconfig"
2443 source "drivers/video/omap2/Kconfig"
2445 source "drivers/video/backlight/Kconfig"
2446 source "drivers/video/display/Kconfig"
2449 source "drivers/video/console/Kconfig"
2452 if FB || SGI_NEWPORT_CONSOLE
2453 source "drivers/video/logo/Kconfig"