5 menu "Graphics support"
11 source "drivers/char/agp/Kconfig"
13 source "drivers/gpu/vga/Kconfig"
15 source "drivers/gpu/drm/Kconfig"
21 config VIDEO_OUTPUT_CONTROL
22 tristate "Lowlevel video output switch controls"
24 This framework adds support for low-level control of the video
28 tristate "Support for frame buffer devices"
30 The frame buffer device provides an abstraction for the graphics
31 hardware. It represents the frame buffer of some video hardware and
32 allows application software to access the graphics hardware through
33 a well-defined interface, so the software doesn't need to know
34 anything about the low-level (hardware register) stuff.
36 Frame buffer devices work identically across the different
37 architectures supported by Linux and make the implementation of
38 application programs easier and more portable; at this point, an X
39 server exists which uses the frame buffer device exclusively.
40 On several non-X86 architectures, the frame buffer device is the
41 only way to use the graphics hardware.
43 The device is accessed through special device nodes, usually located
44 in the /dev directory, i.e. /dev/fb*.
46 You need an utility program called fbset to make full use of frame
47 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
48 and the Framebuffer-HOWTO at
49 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more
52 Say Y here and to the driver for your graphics board below if you
53 are compiling a kernel for a non-x86 architecture.
55 If you are compiling for the x86 architecture, you can say Y if you
56 want to play with it, but it is not essential. Please note that
57 running graphical applications that directly touch the hardware
58 (e.g. an accelerated X server) and that are not frame buffer
59 device-aware may cause unexpected results. If unsure, say N.
62 bool "Enable firmware EDID"
66 This enables access to the EDID transferred from the firmware.
67 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
68 transfers do not work for your driver and if you are using
69 nvidiafb, i810fb or savagefb.
71 In general, choosing Y for this option is safe. If you
72 experience extremely long delays while booting before you get
73 something on your display, try setting this to N. Matrox cards in
74 combination with certain motherboards and monitors are known to
75 suffer from this problem.
84 config FB_BOOT_VESA_SUPPORT
89 If true, at least one selected framebuffer driver can take advantage
90 of VESA video modes set at an early boot stage via the vga= parameter.
92 config FB_CFB_FILLRECT
97 Include the cfb_fillrect function for generic software rectangle
98 filling. This is used by drivers that don't provide their own
99 (accelerated) version.
101 config FB_CFB_COPYAREA
106 Include the cfb_copyarea function for generic software area copying.
107 This is used by drivers that don't provide their own (accelerated)
110 config FB_CFB_IMAGEBLIT
115 Include the cfb_imageblit function for generic software image
116 blitting. This is used by drivers that don't provide their own
117 (accelerated) version.
119 config FB_CFB_REV_PIXELS_IN_BYTE
124 Allow generic frame-buffer functions to work on displays with 1, 2
125 and 4 bits per pixel depths which has opposite order of pixels in
126 byte order to bytes in long order.
128 config FB_SYS_FILLRECT
133 Include the sys_fillrect function for generic software rectangle
134 filling. This is used by drivers that don't provide their own
135 (accelerated) version and the framebuffer is in system RAM.
137 config FB_SYS_COPYAREA
142 Include the sys_copyarea function for generic software area copying.
143 This is used by drivers that don't provide their own (accelerated)
144 version and the framebuffer is in system RAM.
146 config FB_SYS_IMAGEBLIT
151 Include the sys_imageblit function for generic software image
152 blitting. This is used by drivers that don't provide their own
153 (accelerated) version and the framebuffer is in system RAM.
155 menuconfig FB_FOREIGN_ENDIAN
156 bool "Framebuffer foreign endianness support"
159 This menu will let you enable support for the framebuffers with
160 non-native endianness (e.g. Little-Endian framebuffer on a
161 Big-Endian machine). Most probably you don't have such hardware,
162 so it's safe to say "n" here.
165 prompt "Choice endianness support"
166 depends on FB_FOREIGN_ENDIAN
168 config FB_BOTH_ENDIAN
169 bool "Support for Big- and Little-Endian framebuffers"
172 bool "Support for Big-Endian framebuffers only"
174 config FB_LITTLE_ENDIAN
175 bool "Support for Little-Endian framebuffers only"
184 config FB_DEFERRED_IO
191 depends on FB_DEFERRED_IO
198 Common utility functions useful to fbdev drivers of VGA-based
209 select BACKLIGHT_LCD_SUPPORT
210 select BACKLIGHT_CLASS_DEVICE
213 config FB_MODE_HELPERS
214 bool "Enable Video Mode Handling Helpers"
218 This enables functions for handling video modes using the
219 Generalized Timing Formula and the EDID parser. A few drivers rely
220 on this feature such as the radeonfb, rivafb, and the i810fb. If
221 your driver does not take advantage of this feature, choosing Y will
222 just increase the kernel size by about 5K.
224 config FB_TILEBLITTING
225 bool "Enable Tile Blitting Support"
229 This enables tile blitting. Tile blitting is a drawing technique
230 where the screen is divided into rectangular sections (tiles), whereas
231 the standard blitting divides the screen into pixels. Because the
232 default drawing element is a tile, drawing functions will be passed
233 parameters in terms of number of tiles instead of number of pixels.
234 For example, to draw a single character, instead of using bitmaps,
235 an index to an array of bitmaps will be used. To clear or move a
236 rectangular section of a screen, the rectangle will be described in
237 terms of number of tiles in the x- and y-axis.
239 This is particularly important to one driver, matroxfb. If
242 comment "Frame buffer hardware drivers"
246 tristate "Cirrus Logic support"
247 depends on FB && (ZORRO || PCI)
248 select FB_CFB_FILLRECT
249 select FB_CFB_COPYAREA
250 select FB_CFB_IMAGEBLIT
252 This enables support for Cirrus Logic GD542x/543x based boards on
253 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
255 If you have a PCI-based system, this enables support for these
256 chips: GD-543x, GD-544x, GD-5480.
258 Please read the file <file:Documentation/fb/cirrusfb.txt>.
260 Say N unless you have such a graphics board or plan to get one
261 before you next recompile the kernel.
264 tristate "Permedia2 support"
265 depends on FB && ((AMIGA && BROKEN) || PCI)
266 select FB_CFB_FILLRECT
267 select FB_CFB_COPYAREA
268 select FB_CFB_IMAGEBLIT
270 This is the frame buffer device driver for cards based on
271 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
272 The driver was tested on the following cards:
273 Diamond FireGL 1000 PRO AGP
274 ELSA Gloria Synergy PCI
275 Appian Jeronimo PRO (both heads) PCI
276 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
277 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
278 ASK Graphic Blaster Exxtreme AGP
280 To compile this driver as a module, choose M here: the
281 module will be called pm2fb.
283 config FB_PM2_FIFO_DISCONNECT
284 bool "enable FIFO disconnect feature"
285 depends on FB_PM2 && PCI
287 Support the Permedia2 FIFO disconnect feature.
290 tristate "ARM PrimeCell PL110 support"
291 depends on FB && ARM && ARM_AMBA
292 select FB_CFB_FILLRECT
293 select FB_CFB_COPYAREA
294 select FB_CFB_IMAGEBLIT
296 This framebuffer device driver is for the ARM PrimeCell PL110
297 Colour LCD controller. ARM PrimeCells provide the building
298 blocks for System on a Chip devices.
300 If you want to compile this as a module (=code which can be
301 inserted into and removed from the running kernel), say M
302 here and read <file:Documentation/kbuild/modules.txt>. The module
303 will be called amba-clcd.
307 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
309 default FB_ARMCLCD_SHARP_LQ035Q7DB02
311 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
312 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
314 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
315 color QVGA, HRTFT panel. The LogicPD device includes
316 an integrated HRTFT controller IC.
317 The native resolution is 240x320.
319 config FB_ARMCLCD_SHARP_LQ057Q3DC02
320 bool "LogicPD LCD 5.7\" QVGA"
322 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
323 color QVGA, TFT panel. The LogicPD device includes an
324 The native resolution is 320x240.
326 config FB_ARMCLCD_SHARP_LQ64D343
327 bool "LogicPD LCD 6.4\" VGA"
329 This is an implementation of the Sharp LQ64D343, a 6.4"
330 color VGA, TFT panel. The LogicPD device includes an
331 The native resolution is 640x480.
333 config FB_ARMCLCD_SHARP_LQ10D368
334 bool "LogicPD LCD 10.4\" VGA"
336 This is an implementation of the Sharp LQ10D368, a 10.4"
337 color VGA, TFT panel. The LogicPD device includes an
338 The native resolution is 640x480.
341 config FB_ARMCLCD_SHARP_LQ121S1DG41
342 bool "LogicPD LCD 12.1\" SVGA"
344 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
345 color SVGA, TFT panel. The LogicPD device includes an
346 The native resolution is 800x600.
348 This panel requires a clock rate may be an integer fraction
349 of the base LCDCLK frequency. The driver will select the
350 highest frequency available that is lower than the maximum
351 allowed. The panel may flicker if the clock rate is
352 slower than the recommended minimum.
354 config FB_ARMCLCD_AUO_A070VW01_WIDE
355 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
357 This is an implementation of the AU Optronics, a 7.0"
358 WIDE Color. The native resolution is 234x480.
360 config FB_ARMCLCD_HITACHI
361 bool "Hitachi Wide Screen 800x480"
363 This is an implementation of the Hitachi 800x480.
369 bool "Acorn VIDC support"
370 depends on (FB = y) && ARM && ARCH_ACORN
371 select FB_CFB_FILLRECT
372 select FB_CFB_COPYAREA
373 select FB_CFB_IMAGEBLIT
375 This is the frame buffer device driver for the Acorn VIDC graphics
376 hardware found in Acorn RISC PCs and other ARM-based machines. If
380 bool "CLPS711X LCD support"
381 depends on (FB = y) && ARM && ARCH_CLPS711X
382 select FB_CFB_FILLRECT
383 select FB_CFB_COPYAREA
384 select FB_CFB_IMAGEBLIT
386 Say Y to enable the Framebuffer driver for the CLPS7111 and
390 bool "SA-1100 LCD support"
391 depends on (FB = y) && ARM && ARCH_SA1100
392 select FB_CFB_FILLRECT
393 select FB_CFB_COPYAREA
394 select FB_CFB_IMAGEBLIT
396 This is a framebuffer device for the SA-1100 LCD Controller.
397 See <http://www.linux-fbdev.org/> for information on framebuffer
400 If you plan to use the LCD display with your SA-1100 system, say
404 tristate "Motorola i.MX LCD support"
405 depends on FB && (ARCH_MX1 || ARCH_MX2)
406 select FB_CFB_FILLRECT
407 select FB_CFB_COPYAREA
408 select FB_CFB_IMAGEBLIT
411 tristate "CyberPro 2000/2010/5000 support"
412 depends on FB && PCI && (BROKEN || !SPARC64)
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
417 This enables support for the Integraphics CyberPro 20x0 and 5000
418 VGA chips used in the Rebel.com Netwinder and other machines.
419 Say Y if you have a NetWinder or a graphics card containing this
420 device, otherwise say N.
424 depends on (FB = y) && APOLLO
426 select FB_CFB_FILLRECT
427 select FB_CFB_IMAGEBLIT
431 depends on (FB = y) && Q40
433 select FB_CFB_FILLRECT
434 select FB_CFB_COPYAREA
435 select FB_CFB_IMAGEBLIT
438 tristate "Amiga native chipset support"
439 depends on FB && AMIGA
441 This is the frame buffer device driver for the builtin graphics
442 chipset found in Amigas.
444 To compile this driver as a module, choose M here: the
445 module will be called amifb.
448 bool "Amiga OCS chipset support"
451 This enables support for the original Agnus and Denise video chips,
452 found in the Amiga 1000 and most A500's and A2000's. If you intend
453 to run Linux on any of these systems, say Y; otherwise say N.
456 bool "Amiga ECS chipset support"
459 This enables support for the Enhanced Chip Set, found in later
460 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
461 you intend to run Linux on any of these systems, say Y; otherwise
465 bool "Amiga AGA chipset support"
468 This enables support for the Advanced Graphics Architecture (also
469 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
470 and CD32. If you intend to run Linux on any of these systems, say Y;
474 bool "Amiga FrameMaster II/Rainbow II support"
475 depends on (FB = y) && ZORRO
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
480 This is the frame buffer device driver for the Amiga FrameMaster
481 card from BSC (exhibited 1992 but not shipped as a CBM product).
484 tristate "Arc Monochrome LCD board support"
486 select FB_SYS_FILLRECT
487 select FB_SYS_COPYAREA
488 select FB_SYS_IMAGEBLIT
491 This enables support for the Arc Monochrome LCD board. The board
492 is based on the KS-108 lcd controller and is typically a matrix
493 of 2*n chips. This driver was tested with a 128x64 panel. This
494 driver supports it for use with x86 SBCs through a 16 bit GPIO
495 interface (8 bit data, 8 bit control). If you anticipate using
496 this driver, say Y or M; otherwise say N. You must specify the
497 GPIO IO address to be used for setting control and data.
500 bool "Atari native chipset support"
501 depends on (FB = y) && ATARI
502 select FB_CFB_FILLRECT
503 select FB_CFB_COPYAREA
504 select FB_CFB_IMAGEBLIT
506 This is the frame buffer device driver for the builtin graphics
507 chipset found in Ataris.
510 bool "Open Firmware frame buffer device support"
511 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
512 select FB_CFB_FILLRECT
513 select FB_CFB_COPYAREA
514 select FB_CFB_IMAGEBLIT
517 Say Y if you want support with Open Firmware for your graphics
521 bool "Apple \"control\" display support"
522 depends on (FB = y) && 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 graphics adapter in the
529 Power Macintosh 7300 and others.
532 bool "Apple \"platinum\" display support"
533 depends on (FB = y) && PPC_PMAC && PPC32
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
539 This driver supports a frame buffer for the "platinum" graphics
540 adapter in some Power Macintoshes.
543 bool "Apple \"valkyrie\" display support"
544 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
550 This driver supports a frame buffer for the "valkyrie" graphics
551 adapter in some Power Macintoshes.
554 bool "Chips 65550 display support"
555 depends on (FB = y) && PPC32 && PCI
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 This is the frame buffer device driver for the Chips & Technologies
561 65550 graphics chip in PowerBooks.
564 bool "Asiliant (Chips) 69000 display support"
565 depends on (FB = y) && PCI
566 select FB_CFB_FILLRECT
567 select FB_CFB_COPYAREA
568 select FB_CFB_IMAGEBLIT
570 This is the frame buffer device driver for the Asiliant 69030 chipset
573 bool "IMS Twin Turbo display support"
574 depends on (FB = y) && PCI
575 select FB_CFB_IMAGEBLIT
576 select FB_MACMODES if PPC
578 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
579 many Macintosh and compatible computers.
582 tristate "VGA 16-color graphics support"
583 depends on FB && (X86 || PPC)
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
588 select FONT_8x16 if FRAMEBUFFER_CONSOLE
590 This is the frame buffer device driver for VGA 16 color graphic
591 cards. Say Y if you have such a card.
593 To compile this driver as a module, choose M here: the
594 module will be called vga16fb.
596 config FB_BF54X_LQ043
597 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
598 depends on FB && (BF54x) && !BF542
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
603 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
605 config FB_BFIN_T350MCQB
606 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
607 depends on FB && BLACKFIN
609 select FB_CFB_FILLRECT
610 select FB_CFB_COPYAREA
611 select FB_CFB_IMAGEBLIT
613 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
614 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
615 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
619 tristate "HP STI frame buffer device support"
620 depends on FB && PARISC
621 select FB_CFB_FILLRECT
622 select FB_CFB_COPYAREA
623 select FB_CFB_IMAGEBLIT
628 STI refers to the HP "Standard Text Interface" which is a set of
629 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
630 Enabling this option will implement the linux framebuffer device
631 using calls to the STI BIOS routines for initialisation.
633 If you enable this option, you will get a planar framebuffer device
634 /dev/fb which will work on the most common HP graphic cards of the
635 NGLE family, including the artist chips (in the 7xx and Bxxx series),
636 HCRX, HCRX24, CRX, CRX24 and VisEG series.
638 It is safe to enable this option, so you should probably say "Y".
641 bool "Generic Macintosh display support"
642 depends on (FB = y) && MAC
643 select FB_CFB_FILLRECT
644 select FB_CFB_COPYAREA
645 select FB_CFB_IMAGEBLIT
650 depends on (FB = y) && DIO
651 select FB_CFB_IMAGEBLIT
655 tristate "TGA/SFB+ framebuffer support"
656 depends on FB && (ALPHA || TC)
657 select FB_CFB_FILLRECT
658 select FB_CFB_COPYAREA
659 select FB_CFB_IMAGEBLIT
662 This is the frame buffer device driver for generic TGA and SFB+
663 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
664 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
665 TURBOchannel cards, also known as PMAGD-A, -B and -C.
667 Due to hardware limitations ZLX-E2 and E3 cards are not supported
668 for DECstation 5000/200 systems. Additionally due to firmware
669 limitations these cards may cause troubles with booting DECstation
670 5000/240 and /260 systems, but are fully supported under Linux if
671 you manage to get it going. ;-)
673 Say Y if you have one of those.
676 tristate "Userspace VESA VGA graphics support"
677 depends on FB && CONNECTOR
678 select FB_CFB_FILLRECT
679 select FB_CFB_COPYAREA
680 select FB_CFB_IMAGEBLIT
681 select FB_MODE_HELPERS
683 This is the frame buffer driver for generic VBE 2.0 compliant
684 graphic cards. It can also take advantage of VBE 3.0 features,
685 such as refresh rate adjustment.
687 This driver generally provides more features than vesafb but
688 requires a userspace helper application called 'v86d'. See
689 <file:Documentation/fb/uvesafb.txt> for more information.
694 bool "VESA VGA graphics support"
695 depends on (FB = y) && X86
696 select FB_CFB_FILLRECT
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
699 select FB_BOOT_VESA_SUPPORT
701 This is the frame buffer device driver for generic VESA 2.0
702 compliant graphic cards. The older VESA 1.2 cards are not supported.
703 You will get a boot time penguin logo at no additional cost. Please
704 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
707 bool "EFI-based Framebuffer Support"
708 depends on (FB = y) && X86 && EFI
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
713 This is the EFI frame buffer device driver. If the firmware on
714 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
715 using the EFI framebuffer as your console.
718 tristate "N411 Apollo/Hecuba devkit support"
719 depends on FB && X86 && MMU
720 select FB_SYS_FILLRECT
721 select FB_SYS_COPYAREA
722 select FB_SYS_IMAGEBLIT
724 select FB_DEFERRED_IO
727 This enables support for the Apollo display controller in its
728 Hecuba form using the n411 devkit.
731 tristate "Hercules mono graphics support"
733 select FB_CFB_FILLRECT
734 select FB_CFB_COPYAREA
735 select FB_CFB_IMAGEBLIT
737 Say Y here if you have a Hercules mono graphics card.
739 To compile this driver as a module, choose M here: the
740 module will be called hgafb.
742 As this card technology is 15 years old, most people will answer N
746 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
747 depends on FB_HGA && EXPERIMENTAL
749 This will compile the Hercules mono graphics with
750 acceleration functions.
753 tristate "SGI Visual Workstation framebuffer support"
754 depends on FB && X86_VISWS
755 select FB_CFB_FILLRECT
756 select FB_CFB_COPYAREA
757 select FB_CFB_IMAGEBLIT
759 SGI Visual Workstation support for framebuffer graphics.
762 bool "SGI Graphics Backend frame buffer support"
763 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
768 This is the frame buffer device driver for SGI Graphics Backend.
769 This chip is used in SGI O2 and Visual Workstation 320/540.
772 int "Video memory size in MB"
776 This is the amount of memory reserved for the framebuffer,
777 which can be any value between 1MB and 8MB.
780 bool "SBUS and UPA framebuffers"
781 depends on (FB = y) && SPARC
783 Say Y if you want support for SBUS or UPA based frame buffer device.
787 depends on (FB = y) && (SPARC && FB_SBUS)
788 select FB_CFB_FILLRECT
789 select FB_CFB_COPYAREA
790 select FB_CFB_IMAGEBLIT
792 This is the frame buffer device driver for the BWtwo frame buffer.
795 bool "CGthree support"
796 depends on (FB = y) && (SPARC && FB_SBUS)
797 select FB_CFB_FILLRECT
798 select FB_CFB_COPYAREA
799 select FB_CFB_IMAGEBLIT
801 This is the frame buffer device driver for the CGthree frame buffer.
804 bool "CGsix (GX,TurboGX) support"
805 depends on (FB = y) && (SPARC && FB_SBUS)
806 select FB_CFB_COPYAREA
807 select FB_CFB_IMAGEBLIT
809 This is the frame buffer device driver for the CGsix (GX, TurboGX)
813 bool "Creator/Creator3D/Elite3D support"
814 depends on FB_SBUS && SPARC64
815 select FB_CFB_COPYAREA
816 select FB_CFB_IMAGEBLIT
818 This is the frame buffer device driver for the Creator, Creator3D,
819 and Elite3D graphics boards.
822 bool "TCX (SS4/SS5 only) support"
824 select FB_CFB_FILLRECT
825 select FB_CFB_COPYAREA
826 select FB_CFB_IMAGEBLIT
828 This is the frame buffer device driver for the TCX 24/8bit frame
832 bool "CGfourteen (SX) support"
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 This is the frame buffer device driver for the CGfourteen frame
839 buffer on Desktop SPARCsystems with the SX graphics option.
842 bool "P9100 (Sparcbook 3 only) support"
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This is the frame buffer device driver for the P9100 card
849 supported on Sparcbook 3 machines.
852 bool "Leo (ZX) support"
854 select FB_CFB_FILLRECT
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the frame buffer device driver for the SBUS-based Sun ZX
859 (leo) frame buffer cards.
862 bool "IGA 168x display support"
863 depends on (FB = y) && SPARC32
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This is the framebuffer device for the INTERGRAPHICS 1680 and
869 successor frame buffer cards.
872 bool "Sun XVR-500 3DLABS Wildcat support"
873 depends on (FB = y) && PCI && SPARC64
874 select FB_CFB_FILLRECT
875 select FB_CFB_COPYAREA
876 select FB_CFB_IMAGEBLIT
878 This is the framebuffer device for the Sun XVR-500 and similar
879 graphics cards based upon the 3DLABS Wildcat chipset. The driver
880 only works on sparc64 systems where the system firmware has
881 mostly initialized the card already. It is treated as a
882 completely dumb framebuffer device.
885 bool "Sun XVR-2500 3DLABS Wildcat support"
886 depends on (FB = y) && PCI && SPARC64
887 select FB_CFB_FILLRECT
888 select FB_CFB_COPYAREA
889 select FB_CFB_IMAGEBLIT
891 This is the framebuffer device for the Sun XVR-2500 and similar
892 graphics cards based upon the 3DLABS Wildcat chipset. The driver
893 only works on sparc64 systems where the system firmware has
894 mostly initialized the card already. It is treated as a
895 completely dumb framebuffer device.
898 tristate "NEC PowerVR 2 display support"
899 depends on FB && SH_DREAMCAST
900 select FB_CFB_FILLRECT
901 select FB_CFB_COPYAREA
902 select FB_CFB_IMAGEBLIT
904 Say Y here if you have a PowerVR 2 card in your box. If you plan to
905 run linux on your Dreamcast, you will have to say Y here.
906 This driver may or may not work on other PowerVR 2 cards, but is
907 totally untested. Use at your own risk. If unsure, say N.
909 To compile this driver as a module, choose M here: the
910 module will be called pvr2fb.
912 You can pass several parameters to the driver at boot time or at
913 module load time. The parameters look like "video=pvr2:XXX", where
914 the meaning of XXX can be found at the end of the main source file
915 (<file:drivers/video/pvr2fb.c>). Please see the file
916 <file:Documentation/fb/pvr2fb.txt>.
919 bool "Epson 1355 framebuffer support"
920 depends on (FB = y) && ARCH_CEIVA
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
925 Build in support for the SED1355 Epson Research Embedded RAMDAC
926 LCD/CRT Controller (since redesignated as the S1D13505) as a
927 framebuffer. Product specs at
928 <http://www.erd.epson.com/vdc/html/products.htm>.
931 tristate "Epson S1D13XXX framebuffer support"
933 select FB_CFB_FILLRECT
934 select FB_CFB_COPYAREA
935 select FB_CFB_IMAGEBLIT
937 Support for S1D13XXX framebuffer device family (currently only
938 working with S1D13806). Product specs at
939 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
942 tristate "AT91/AT32 LCD Controller support"
943 depends on FB && HAVE_FB_ATMEL
944 select FB_CFB_FILLRECT
945 select FB_CFB_COPYAREA
946 select FB_CFB_IMAGEBLIT
948 This enables support for the AT91/AT32 LCD Controller.
951 bool "Frame Buffer in internal SRAM"
952 depends on FB_ATMEL && ARCH_AT91SAM9261
954 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
955 to let frame buffer in external SDRAM.
958 bool "Use a STN display with AT91/AT32 LCD Controller"
959 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
962 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
963 Controller. Say N if you want to connect a TFT.
968 tristate "nVidia Framebuffer Support"
970 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
971 select FB_MODE_HELPERS
972 select FB_CFB_FILLRECT
973 select FB_CFB_COPYAREA
974 select FB_CFB_IMAGEBLIT
978 This driver supports graphics boards with the nVidia chips, TNT
979 and newer. For very old chipsets, such as the RIVA128, then use
981 Say Y if you have such a graphics board.
983 To compile this driver as a module, choose M here: the
984 module will be called nvidiafb.
987 bool "Enable DDC Support"
991 This enables I2C support for nVidia Chipsets. This is used
992 only for getting EDID information from the attached display
993 allowing for robust video mode handling and switching.
995 Because fbdev-2.6 requires that drivers must be able to
996 independently validate video mode parameters, you should say Y
999 config FB_NVIDIA_DEBUG
1000 bool "Lots of debug output"
1001 depends on FB_NVIDIA
1004 Say Y here if you want the nVidia driver to output all sorts
1005 of debugging information to provide to the maintainer when
1006 something goes wrong.
1008 config FB_NVIDIA_BACKLIGHT
1009 bool "Support for backlight control"
1010 depends on FB_NVIDIA
1013 Say Y here if you want to control the backlight of your display.
1016 tristate "nVidia Riva support"
1017 depends on FB && PCI
1018 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1019 select FB_MODE_HELPERS
1020 select FB_CFB_FILLRECT
1021 select FB_CFB_COPYAREA
1022 select FB_CFB_IMAGEBLIT
1026 This driver supports graphics boards with the nVidia Riva/Geforce
1028 Say Y if you have such a graphics board.
1030 To compile this driver as a module, choose M here: the
1031 module will be called rivafb.
1034 bool "Enable DDC Support"
1038 This enables I2C support for nVidia Chipsets. This is used
1039 only for getting EDID information from the attached display
1040 allowing for robust video mode handling and switching.
1042 Because fbdev-2.6 requires that drivers must be able to
1043 independently validate video mode parameters, you should say Y
1046 config FB_RIVA_DEBUG
1047 bool "Lots of debug output"
1051 Say Y here if you want the Riva driver to output all sorts
1052 of debugging information to provide to the maintainer when
1053 something goes wrong.
1055 config FB_RIVA_BACKLIGHT
1056 bool "Support for backlight control"
1060 Say Y here if you want to control the backlight of your display.
1063 tristate "Intel 810/815 support (EXPERIMENTAL)"
1064 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1065 select FB_MODE_HELPERS
1066 select FB_CFB_FILLRECT
1067 select FB_CFB_COPYAREA
1068 select FB_CFB_IMAGEBLIT
1071 This driver supports the on-board graphics built in to the Intel 810
1072 and 815 chipsets. Say Y if you have and plan to use such a board.
1074 To compile this driver as a module, choose M here: the
1075 module will be called i810fb.
1077 For more information, please read
1078 <file:Documentation/fb/intel810.txt>
1081 bool "use VESA Generalized Timing Formula"
1084 If you say Y, then the VESA standard, Generalized Timing Formula
1085 or GTF, will be used to calculate the required video timing values
1086 per video mode. Since the GTF allows nondiscrete timings
1087 (nondiscrete being a range of values as opposed to discrete being a
1088 set of values), you'll be able to use any combination of horizontal
1089 and vertical resolutions, and vertical refresh rates without having
1090 to specify your own timing parameters. This is especially useful
1091 to maximize the performance of an aging display, or if you just
1092 have a display with nonstandard dimensions. A VESA compliant
1093 monitor is recommended, but can still work with non-compliant ones.
1094 If you need or want this, then select this option. The timings may
1095 not be compliant with Intel's recommended values. Use at your own
1098 If you say N, the driver will revert to discrete video timings
1099 using a set recommended by Intel in their documentation.
1104 bool "Enable DDC Support"
1105 depends on FB_I810 && FB_I810_GTF
1110 tristate "Intel LE80578 (Vermilion) support"
1111 depends on FB && PCI && X86
1112 select FB_MODE_HELPERS
1113 select FB_CFB_FILLRECT
1114 select FB_CFB_COPYAREA
1115 select FB_CFB_IMAGEBLIT
1117 This driver supports the LE80578 (Vermilion Range) chipset
1119 config FB_CARILLO_RANCH
1120 tristate "Intel Carillo Ranch support"
1121 depends on FB_LE80578 && FB && PCI && X86
1123 This driver supports the LE80578 (Carillo Ranch) board
1126 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1127 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1128 select FB_MODE_HELPERS
1129 select FB_CFB_FILLRECT
1130 select FB_CFB_COPYAREA
1131 select FB_CFB_IMAGEBLIT
1132 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1133 depends on !DRM_I915
1135 This driver supports the on-board graphics built in to the Intel
1136 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1137 Say Y if you have and plan to use such a board.
1139 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1141 To compile this driver as a module, choose M here: the
1142 module will be called intelfb.
1144 For more information, please read <file:Documentation/fb/intelfb.txt>
1146 config FB_INTEL_DEBUG
1147 bool "Intel driver Debug Messages"
1150 Say Y here if you want the Intel driver to output all sorts
1151 of debugging information to provide to the maintainer when
1152 something goes wrong.
1155 bool "DDC/I2C for Intel framebuffer support"
1160 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1163 tristate "Matrox acceleration"
1164 depends on FB && PCI
1165 select FB_CFB_FILLRECT
1166 select FB_CFB_COPYAREA
1167 select FB_CFB_IMAGEBLIT
1168 select FB_TILEBLITTING
1169 select FB_MACMODES if PPC_PMAC
1171 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1172 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1173 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1174 Matrox G400, G450 or G550 card in your box.
1176 To compile this driver as a module, choose M here: the
1177 module will be called matroxfb.
1179 You can pass several parameters to the driver at boot time or at
1180 module load time. The parameters look like "video=matrox:XXX", and
1181 are described in <file:Documentation/fb/matroxfb.txt>.
1183 config FB_MATROX_MILLENIUM
1184 bool "Millennium I/II support"
1185 depends on FB_MATROX
1187 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1188 video card. If you select "Advanced lowlevel driver options" below,
1189 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1190 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1191 also use font widths different from 8.
1193 config FB_MATROX_MYSTIQUE
1194 bool "Mystique support"
1195 depends on FB_MATROX
1197 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1198 video card. If you select "Advanced lowlevel driver options" below,
1199 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1200 packed pixel and 32 bpp packed pixel. You can also use font widths
1204 bool "G100/G200/G400/G450/G550 support"
1205 depends on FB_MATROX
1207 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1208 video card. If you select "Advanced lowlevel driver options", you
1209 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1210 pixel and 32 bpp packed pixel. You can also use font widths
1213 If you need support for G400 secondary head, you must say Y to
1214 "Matrox I2C support" and "G400 second head support" right below.
1215 G450/G550 secondary head and digital output are supported without
1218 The driver starts in monitor mode. You must use the matroxset tool
1219 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1220 swap primary and secondary head outputs, or to change output mode.
1221 Secondary head driver always start in 640x480 resolution and you
1222 must use fbset to change it.
1224 Do not forget that second head supports only 16 and 32 bpp
1225 packed pixels, so it is a good idea to compile them into the kernel
1226 too. You can use only some font widths, as the driver uses generic
1227 painting procedures (the secondary head does not use acceleration
1230 G450/G550 hardware can display TV picture only from secondary CRTC,
1231 and it performs no scaling, so picture must have 525 or 625 lines.
1233 config FB_MATROX_I2C
1234 tristate "Matrox I2C support"
1235 depends on FB_MATROX
1238 This drivers creates I2C buses which are needed for accessing the
1239 DDC (I2C) bus present on all Matroxes, an I2C bus which
1240 interconnects Matrox optional devices, like MGA-TVO on G200 and
1241 G400, and the secondary head DDC bus, present on G400 only.
1243 You can say Y or M here if you want to experiment with monitor
1244 detection code. You must say Y or M here if you want to use either
1245 second head of G400 or MGA-TVO on G200 or G400.
1247 If you compile it as module, it will create a module named
1250 config FB_MATROX_MAVEN
1251 tristate "G400 second head support"
1252 depends on FB_MATROX_G && FB_MATROX_I2C
1254 WARNING !!! This support does not work with G450 !!!
1256 Say Y or M here if you want to use a secondary head (meaning two
1257 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1258 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1259 secondary head output is blanked while you are in X. With XFree
1260 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1261 the fbdev driver on first head and the fbdev driver on second head.
1263 If you compile it as module, two modules are created,
1264 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1265 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1266 also load i2c-matroxfb to get it to run.
1268 The driver starts in monitor mode and you must use the matroxset
1270 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1271 PAL or NTSC or to swap primary and secondary head outputs.
1272 Secondary head driver also always start in 640x480 resolution, you
1273 must use fbset to change it.
1275 Also do not forget that second head supports only 16 and 32 bpp
1276 packed pixels, so it is a good idea to compile them into the kernel
1277 too. You can use only some font widths, as the driver uses generic
1278 painting procedures (the secondary head does not use acceleration
1282 tristate "ATI Radeon display support"
1283 depends on FB && PCI
1284 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1285 select FB_MODE_HELPERS
1286 select FB_CFB_FILLRECT
1287 select FB_CFB_COPYAREA
1288 select FB_CFB_IMAGEBLIT
1289 select FB_MACMODES if PPC_OF
1291 Choose this option if you want to use an ATI Radeon graphics card as
1292 a framebuffer device. There are both PCI and AGP versions. You
1293 don't need to choose this to run the Radeon in plain VGA mode.
1295 There is a product page at
1296 http://apps.ati.com/ATIcompare/
1298 config FB_RADEON_I2C
1299 bool "DDC/I2C for ATI Radeon support"
1300 depends on FB_RADEON
1304 Say Y here if you want DDC/I2C support for your Radeon board.
1306 config FB_RADEON_BACKLIGHT
1307 bool "Support for backlight control"
1308 depends on FB_RADEON
1311 Say Y here if you want to control the backlight of your display.
1313 config FB_RADEON_DEBUG
1314 bool "Lots of debug output from Radeon driver"
1315 depends on FB_RADEON
1318 Say Y here if you want the Radeon driver to output all sorts
1319 of debugging information to provide to the maintainer when
1320 something goes wrong.
1323 tristate "ATI Rage128 display support"
1324 depends on FB && PCI
1325 select FB_CFB_FILLRECT
1326 select FB_CFB_COPYAREA
1327 select FB_CFB_IMAGEBLIT
1328 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1329 select FB_MACMODES if PPC_PMAC
1331 This driver supports graphics boards with the ATI Rage128 chips.
1332 Say Y if you have such a graphics board and read
1333 <file:Documentation/fb/aty128fb.txt>.
1335 To compile this driver as a module, choose M here: the
1336 module will be called aty128fb.
1338 config FB_ATY128_BACKLIGHT
1339 bool "Support for backlight control"
1340 depends on FB_ATY128
1343 Say Y here if you want to control the backlight of your display.
1346 tristate "ATI Mach64 display support" if PCI || ATARI
1347 depends on FB && !SPARC32
1348 select FB_CFB_FILLRECT
1349 select FB_CFB_COPYAREA
1350 select FB_CFB_IMAGEBLIT
1351 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1352 select FB_MACMODES if PPC
1354 This driver supports graphics boards with the ATI Mach64 chips.
1355 Say Y if you have such a graphics board.
1357 To compile this driver as a module, choose M here: the
1358 module will be called atyfb.
1361 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1362 depends on PCI && FB_ATY
1363 default y if SPARC64 && PCI
1365 Say Y here to support use of ATI's 64-bit Rage boards (or other
1366 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1367 framebuffer device. The ATI product support page for these boards
1368 is at <http://support.ati.com/products/pc/mach64/>.
1370 config FB_ATY_GENERIC_LCD
1371 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1372 depends on FB_ATY_CT
1374 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1375 Rage XC, or Rage XL chipset.
1378 bool "Mach64 GX support" if PCI
1382 Say Y here to support use of the ATI Mach64 Graphics Expression
1383 board (or other boards based on the Mach64 GX chipset) as a
1384 framebuffer device. The ATI product support page for these boards
1386 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1388 config FB_ATY_BACKLIGHT
1389 bool "Support for backlight control"
1393 Say Y here if you want to control the backlight of your display.
1396 tristate "S3 Trio/Virge support"
1397 depends on FB && PCI
1398 select FB_CFB_FILLRECT
1399 select FB_CFB_COPYAREA
1400 select FB_CFB_IMAGEBLIT
1401 select FB_TILEBLITTING
1404 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1406 Driver for graphics boards with S3 Trio / S3 Virge chip.
1409 tristate "S3 Savage support"
1410 depends on FB && PCI && EXPERIMENTAL
1411 select FB_MODE_HELPERS
1412 select FB_CFB_FILLRECT
1413 select FB_CFB_COPYAREA
1414 select FB_CFB_IMAGEBLIT
1417 This driver supports notebooks and computers with S3 Savage PCI/AGP
1420 Say Y if you have such a graphics card.
1422 To compile this driver as a module, choose M here; the module
1423 will be called savagefb.
1425 config FB_SAVAGE_I2C
1426 bool "Enable DDC2 Support"
1427 depends on FB_SAVAGE
1430 This enables I2C support for S3 Savage Chipsets. This is used
1431 only for getting EDID information from the attached display
1432 allowing for robust video mode handling and switching.
1434 Because fbdev-2.6 requires that drivers must be able to
1435 independently validate video mode parameters, you should say Y
1438 config FB_SAVAGE_ACCEL
1439 bool "Enable Console Acceleration"
1440 depends on FB_SAVAGE
1443 This option will compile in console acceleration support. If
1444 the resulting framebuffer console has bothersome glitches, then
1448 tristate "SiS/XGI display support"
1449 depends on FB && PCI
1450 select FB_CFB_FILLRECT
1451 select FB_CFB_COPYAREA
1452 select FB_CFB_IMAGEBLIT
1453 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1455 This is the frame buffer device driver for the SiS 300, 315, 330
1456 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1457 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1459 To compile this driver as a module, choose M here; the module
1460 will be called sisfb.
1463 bool "SiS 300 series support"
1466 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1469 bool "SiS 315/330/340 series and XGI support"
1472 Say Y here to support use of the SiS 315, 330 and 340 series
1473 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1474 as XGI V3XT, V5, V8 and Z7.
1477 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1478 depends on FB && PCI
1479 select FB_CFB_FILLRECT
1480 select FB_CFB_COPYAREA
1481 select FB_CFB_IMAGEBLIT
1482 select FB_SOFT_CURSOR
1486 This is the frame buffer device driver for Graphics chips of VIA
1487 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1488 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1490 Say Y if you have a VIA UniChrome graphics board.
1492 To compile this driver as a module, choose M here: the
1493 module will be called viafb.
1495 tristate "NeoMagic display support"
1496 depends on FB && PCI
1497 select FB_MODE_HELPERS
1498 select FB_CFB_FILLRECT
1499 select FB_CFB_COPYAREA
1500 select FB_CFB_IMAGEBLIT
1503 This driver supports notebooks with NeoMagic PCI chips.
1504 Say Y if you have such a graphics card.
1506 To compile this driver as a module, choose M here: the
1507 module will be called neofb.
1510 tristate "IMG Kyro support"
1511 depends on FB && PCI
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1516 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1519 To compile this driver as a module, choose M here: the
1520 module will be called kyrofb.
1523 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1524 depends on FB && PCI
1525 select FB_CFB_IMAGEBLIT
1526 select FB_CFB_FILLRECT
1527 select FB_CFB_COPYAREA
1528 select FB_MODE_HELPERS
1530 This driver supports graphics boards with the 3Dfx Banshee,
1531 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1532 such a graphics board.
1534 To compile this driver as a module, choose M here: the
1535 module will be called tdfxfb.
1537 config FB_3DFX_ACCEL
1538 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1539 depends on FB_3DFX && EXPERIMENTAL
1541 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1542 device driver with acceleration functions.
1545 bool "Enable DDC/I2C support"
1546 depends on FB_3DFX && EXPERIMENTAL
1550 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1553 tristate "3Dfx Voodoo Graphics (sst1) support"
1554 depends on FB && PCI
1555 select FB_CFB_FILLRECT
1556 select FB_CFB_COPYAREA
1557 select FB_CFB_IMAGEBLIT
1559 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1560 Voodoo2 (cvg) based graphics card.
1562 To compile this driver as a module, choose M here: the
1563 module will be called sstfb.
1565 WARNING: Do not use any application that uses the 3D engine
1566 (namely glide) while using this driver.
1567 Please read the <file:Documentation/fb/sstfb.txt> for supported
1568 options and other important info support.
1571 tristate "VIA VT8623 support"
1572 depends on FB && PCI
1573 select FB_CFB_FILLRECT
1574 select FB_CFB_COPYAREA
1575 select FB_CFB_IMAGEBLIT
1576 select FB_TILEBLITTING
1579 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1581 Driver for CastleRock integrated graphics core in the
1582 VIA VT8623 [Apollo CLE266] chipset.
1585 tristate "Trident/CyberXXX/CyberBlade support"
1586 depends on FB && PCI
1587 select FB_CFB_FILLRECT
1588 select FB_CFB_COPYAREA
1589 select FB_CFB_IMAGEBLIT
1591 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1592 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1594 There are also integrated versions of these chips called CyberXXXX,
1595 CyberImage or CyberBlade. These chips are mostly found in laptops
1596 but also on some motherboards including early VIA EPIA motherboards.
1597 For more information, read <file:Documentation/fb/tridentfb.txt>
1599 Say Y if you have such a graphics board.
1601 To compile this driver as a module, choose M here: the
1602 module will be called tridentfb.
1605 tristate "ARK 2000PV support"
1606 depends on FB && PCI
1607 select FB_CFB_FILLRECT
1608 select FB_CFB_COPYAREA
1609 select FB_CFB_IMAGEBLIT
1610 select FB_TILEBLITTING
1613 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1615 Driver for PCI graphics boards with ARK 2000PV chip
1616 and ICS 5342 RAMDAC.
1619 tristate "Permedia3 support (EXPERIMENTAL)"
1620 depends on FB && PCI && EXPERIMENTAL
1621 select FB_CFB_FILLRECT
1622 select FB_CFB_COPYAREA
1623 select FB_CFB_IMAGEBLIT
1625 This is the frame buffer device driver for the 3DLabs Permedia3
1626 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1627 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1628 and maybe other boards.
1631 tristate "Fujitsu carmine frame buffer support"
1632 depends on FB && PCI
1633 select FB_CFB_FILLRECT
1634 select FB_CFB_COPYAREA
1635 select FB_CFB_IMAGEBLIT
1637 This is the frame buffer device driver for the Fujitsu Carmine chip.
1638 The driver provides two independent frame buffer devices.
1641 depends on FB_CARMINE
1642 prompt "DRAM timing"
1643 default FB_CARMINE_DRAM_EVAL
1645 config FB_CARMINE_DRAM_EVAL
1646 bool "Eval board timings"
1648 Use timings which work on the eval card.
1650 config CARMINE_DRAM_CUSTOM
1651 bool "Custom board timings"
1653 Use custom board timings.
1657 bool "Au1100 LCD Driver"
1658 depends on (FB = y) && MIPS && SOC_AU1100
1659 select FB_CFB_FILLRECT
1660 select FB_CFB_COPYAREA
1661 select FB_CFB_IMAGEBLIT
1663 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1664 various panels and CRTs by passing in kernel cmd line option
1665 au1100fb:panel=<name>.
1668 bool "Au1200 LCD Driver"
1669 depends on (FB = y) && MIPS && SOC_AU1200
1670 select FB_CFB_FILLRECT
1671 select FB_CFB_COPYAREA
1672 select FB_CFB_IMAGEBLIT
1674 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1675 various panels and CRTs by passing in kernel cmd line option
1676 au1200fb:panel=<name>.
1678 source "drivers/video/geode/Kconfig"
1681 tristate "HD64461 Frame Buffer support"
1682 depends on FB && HD64461
1683 select FB_CFB_FILLRECT
1684 select FB_CFB_COPYAREA
1685 select FB_CFB_IMAGEBLIT
1687 This is the frame buffer device driver for the Hitachi HD64461 LCD
1691 bool "PMAG-AA TURBOchannel framebuffer support"
1692 depends on (FB = y) && TC
1693 select FB_CFB_FILLRECT
1694 select FB_CFB_COPYAREA
1695 select FB_CFB_IMAGEBLIT
1697 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1698 used mainly in the MIPS-based DECstation series.
1701 tristate "PMAG-BA TURBOchannel framebuffer support"
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1708 used mainly in the MIPS-based DECstation series.
1711 tristate "PMAGB-B TURBOchannel framebuffer support"
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1718 in the MIPS-based DECstation series. The card is currently only
1719 supported in 1280x1024x8 mode.
1722 bool "Maxine (Personal DECstation) onboard framebuffer support"
1723 depends on (FB = y) && MACH_DECSTATION
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1728 Support for the onboard framebuffer (1024x768x8) in the Personal
1729 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1733 bool "G364 frame buffer support"
1734 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1735 select FB_CFB_FILLRECT
1736 select FB_CFB_COPYAREA
1737 select FB_CFB_IMAGEBLIT
1739 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1740 Olivetti M700-10 systems.
1743 bool "Motorola 68328 native frame buffer support"
1744 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1745 select FB_CFB_FILLRECT
1746 select FB_CFB_COPYAREA
1747 select FB_CFB_IMAGEBLIT
1749 Say Y here if you want to support the built-in frame buffer of
1750 the Motorola 68328 CPU family.
1753 tristate "PXA168/910 LCD framebuffer support"
1754 depends on FB && (CPU_PXA168 || CPU_PXA910)
1755 select FB_CFB_FILLRECT
1756 select FB_CFB_COPYAREA
1757 select FB_CFB_IMAGEBLIT
1759 Frame buffer driver for the built-in LCD controller in the Marvell
1763 tristate "PXA LCD framebuffer support"
1764 depends on FB && ARCH_PXA
1765 select FB_CFB_FILLRECT
1766 select FB_CFB_COPYAREA
1767 select FB_CFB_IMAGEBLIT
1769 Frame buffer driver for the built-in LCD controller in the Intel
1772 This driver is also available as a module ( = code which can be
1773 inserted and removed from the running kernel whenever you want). The
1774 module will be called pxafb. If you want to compile it as a module,
1775 say M here and read <file:Documentation/kbuild/modules.txt>.
1779 config FB_PXA_OVERLAY
1780 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1782 depends on FB_PXA && (PXA27x || PXA3xx)
1784 config FB_PXA_SMARTPANEL
1785 bool "PXA Smartpanel LCD support"
1789 config FB_PXA_PARAMETERS
1790 bool "PXA LCD command line parameters"
1794 Enable the use of kernel command line or module parameters
1795 to configure the physical properties of the LCD panel when
1796 using the PXA LCD driver.
1798 This option allows you to override the panel parameters
1799 supplied by the platform in order to support multiple
1800 different models of flatpanel. If you will only be using a
1801 single model of flatpanel then you can safely leave this
1804 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1807 tristate "2700G LCD framebuffer support"
1808 depends on FB && ARCH_PXA
1809 select FB_CFB_FILLRECT
1810 select FB_CFB_COPYAREA
1811 select FB_CFB_IMAGEBLIT
1813 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1817 bool "Enable debugging info via debugfs"
1818 depends on FB_MBX && DEBUG_FS
1821 Enable this if you want debugging information using the debug
1822 filesystem (debugfs)
1827 tristate "Freescale DIU framebuffer support"
1828 depends on FB && FSL_SOC
1829 select FB_CFB_FILLRECT
1830 select FB_CFB_COPYAREA
1831 select FB_CFB_IMAGEBLIT
1832 select PPC_LIB_RHEAP
1834 Framebuffer driver for the Freescale SoC DIU
1837 tristate "W100 frame buffer support"
1838 depends on FB && ARCH_PXA
1839 select FB_CFB_FILLRECT
1840 select FB_CFB_COPYAREA
1841 select FB_CFB_IMAGEBLIT
1843 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1844 It can also drive the w3220 chip found on iPAQ hx4700.
1846 This driver is also available as a module ( = code which can be
1847 inserted and removed from the running kernel whenever you want). The
1848 module will be called w100fb. If you want to compile it as a module,
1849 say M here and read <file:Documentation/kbuild/modules.txt>.
1853 config FB_SH_MOBILE_LCDC
1854 tristate "SuperH Mobile LCDC framebuffer support"
1855 depends on FB && SUPERH && HAVE_CLK
1856 select FB_SYS_FILLRECT
1857 select FB_SYS_COPYAREA
1858 select FB_SYS_IMAGEBLIT
1860 select FB_DEFERRED_IO
1862 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1865 tristate "Toshiba Mobile IO FrameBuffer support"
1866 depends on FB && MFD_CORE
1867 select FB_CFB_FILLRECT
1868 select FB_CFB_COPYAREA
1869 select FB_CFB_IMAGEBLIT
1871 Frame buffer driver for the Toshiba Mobile IO integrated as found
1872 on the Sharp SL-6000 series
1874 This driver is also available as a module ( = code which can be
1875 inserted and removed from the running kernel whenever you want). The
1876 module will be called tmiofb. If you want to compile it as a module,
1877 say M here and read <file:Documentation/kbuild/modules.txt>.
1881 config FB_TMIO_ACCELL
1882 bool "tmiofb acceleration"
1887 tristate "Samsung S3C framebuffer support"
1888 depends on FB && ARCH_S3C64XX
1889 select FB_CFB_FILLRECT
1890 select FB_CFB_COPYAREA
1891 select FB_CFB_IMAGEBLIT
1893 Frame buffer driver for the built-in FB controller in the Samsung
1894 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1895 and the S3C64XX series such as the S3C6400 and S3C6410.
1897 These chips all have the same basic framebuffer design with the
1898 actual capabilities depending on the chip. For instance the S3C6400
1899 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1900 currently only have two.
1902 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1904 config FB_S3C_DEBUG_REGWRITE
1905 bool "Debug register writes"
1908 Show all register writes via printk(KERN_DEBUG)
1911 tristate "S3C2410 LCD framebuffer support"
1912 depends on FB && ARCH_S3C2410
1913 select FB_CFB_FILLRECT
1914 select FB_CFB_COPYAREA
1915 select FB_CFB_IMAGEBLIT
1917 Frame buffer driver for the built-in LCD controller in the Samsung
1920 This driver is also available as a module ( = code which can be
1921 inserted and removed from the running kernel whenever you want). The
1922 module will be called s3c2410fb. If you want to compile it as a module,
1923 say M here and read <file:Documentation/kbuild/modules.txt>.
1926 config FB_S3C2410_DEBUG
1927 bool "S3C2410 lcd debug messages"
1928 depends on FB_S3C2410
1930 Turn on debugging messages. Note that you can set/unset at run time
1934 tristate "Silicon Motion SM501 framebuffer support"
1935 depends on FB && MFD_SM501
1936 select FB_CFB_FILLRECT
1937 select FB_CFB_COPYAREA
1938 select FB_CFB_IMAGEBLIT
1940 Frame buffer driver for the CRT and LCD controllers in the Silicon
1943 This driver is also available as a module ( = code which can be
1944 inserted and removed from the running kernel whenever you want). The
1945 module will be called sm501fb. If you want to compile it as a module,
1946 say M here and read <file:Documentation/kbuild/modules.txt>.
1951 config FB_PNX4008_DUM
1952 tristate "Display Update Module support on Philips PNX4008 board"
1953 depends on FB && ARCH_PNX4008
1955 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1957 config FB_PNX4008_DUM_RGB
1958 tristate "RGB Framebuffer support on Philips PNX4008 board"
1959 depends on FB_PNX4008_DUM
1960 select FB_CFB_FILLRECT
1961 select FB_CFB_COPYAREA
1962 select FB_CFB_IMAGEBLIT
1964 Say Y here to enable support for PNX4008 RGB Framebuffer
1966 config FB_IBM_GXT4500
1967 tristate "Framebuffer support for IBM GXT4500P adaptor"
1968 depends on FB && PPC
1969 select FB_CFB_FILLRECT
1970 select FB_CFB_COPYAREA
1971 select FB_CFB_IMAGEBLIT
1973 Say Y here to enable support for the IBM GXT4500P display
1974 adaptor, found on some IBM System P (pSeries) machines.
1977 tristate "PS3 GPU framebuffer driver"
1978 depends on FB && PS3_PS3AV
1979 select FB_SYS_FILLRECT
1980 select FB_SYS_COPYAREA
1981 select FB_SYS_IMAGEBLIT
1983 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1985 Include support for the virtual frame buffer in the PS3 platform.
1987 config FB_PS3_DEFAULT_SIZE_M
1988 int "PS3 default frame buffer size (in MiB)"
1992 This is the default size (in MiB) of the virtual frame buffer in
1994 The default value can be overridden on the kernel command line
1995 using the "ps3fb" option (e.g. "ps3fb=9M");
1998 tristate "Xilinx frame buffer support"
1999 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2000 select FB_CFB_FILLRECT
2001 select FB_CFB_COPYAREA
2002 select FB_CFB_IMAGEBLIT
2004 Include support for the Xilinx ML300/ML403 reference design
2005 framebuffer. ML300 carries a 640*480 LCD display on the board,
2006 ML403 uses a standard DB15 VGA connector.
2009 tristate "Cobalt server LCD frame buffer support"
2010 depends on FB && MIPS_COBALT
2013 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2014 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2015 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2016 select FB_CFB_FILLRECT
2017 select FB_CFB_COPYAREA
2018 select FB_CFB_IMAGEBLIT
2020 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2021 (D)STN/TFT LCD Controller.
2022 Supports display resolutions up to 1024x1024 pixel, grayscale and
2023 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2024 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2025 panels <= 320 pixel horizontal resolution.
2028 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2029 depends on FB && ARCH_DAVINCI_DA8XX
2030 select FB_CFB_FILLRECT
2031 select FB_CFB_COPYAREA
2032 select FB_CFB_IMAGEBLIT
2034 This is the frame buffer device driver for the TI LCD controller
2035 found on DA8xx/OMAP-L1xx SoCs.
2039 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2041 select FB_SYS_FILLRECT
2042 select FB_SYS_COPYAREA
2043 select FB_SYS_IMAGEBLIT
2046 This is a `virtual' frame buffer device. It operates on a chunk of
2047 unswappable kernel memory instead of on the memory of a graphics
2048 board. This means you cannot see any output sent to this frame
2049 buffer device, while it does consume precious memory. The main use
2050 of this frame buffer device is testing and debugging the frame
2051 buffer subsystem. Do NOT enable it for normal systems! To protect
2052 the innocent, it has to be enabled explicitly at boot time using the
2053 kernel option `video=vfb:'.
2055 To compile this driver as a module, choose M here: the
2056 module will be called vfb. In order to load it, you must use
2057 the vfb_enable=1 option.
2061 config XEN_FBDEV_FRONTEND
2062 tristate "Xen virtual frame buffer support"
2063 depends on FB && XEN
2064 select FB_SYS_FILLRECT
2065 select FB_SYS_COPYAREA
2066 select FB_SYS_IMAGEBLIT
2068 select FB_DEFERRED_IO
2069 select XEN_XENBUS_FRONTEND
2072 This driver implements the front-end of the Xen virtual
2073 frame buffer driver. It communicates with a back-end
2077 tristate "E-Ink Metronome/8track controller support"
2079 select FB_SYS_FILLRECT
2080 select FB_SYS_COPYAREA
2081 select FB_SYS_IMAGEBLIT
2083 select FB_DEFERRED_IO
2085 This driver implements support for the E-Ink Metronome
2086 controller. The pre-release name for this device was 8track
2087 and could also have been called by some vendors as PVI-nnnn.
2090 tristate "Fujitsu MB862xx GDC support"
2092 select FB_CFB_FILLRECT
2093 select FB_CFB_COPYAREA
2094 select FB_CFB_IMAGEBLIT
2096 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2098 config FB_MB862XX_PCI_GDC
2099 bool "Carmine/Coral-P(A) GDC"
2100 depends on PCI && FB_MB862XX
2102 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2103 PCI graphics controller devices.
2105 config FB_MB862XX_LIME
2107 depends on FB_MB862XX
2108 depends on OF && !FB_MB862XX_PCI_GDC
2110 select FB_FOREIGN_ENDIAN
2111 select FB_LITTLE_ENDIAN
2113 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2116 tristate "EP93XX frame buffer support"
2117 depends on FB && ARCH_EP93XX
2118 select FB_CFB_FILLRECT
2119 select FB_CFB_COPYAREA
2120 select FB_CFB_IMAGEBLIT
2122 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2123 This driver is also available as a module. The module will be called
2126 config FB_PRE_INIT_FB
2127 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2128 depends on FB && FB_MB862XX_LIME
2130 Select this option if display contents should be inherited as set by
2134 tristate "MSM Framebuffer support"
2135 depends on FB && ARCH_MSM
2136 select FB_CFB_FILLRECT
2137 select FB_CFB_COPYAREA
2138 select FB_CFB_IMAGEBLIT
2142 tristate "MX3 Framebuffer support"
2143 depends on FB && MX3_IPU
2144 select FB_CFB_FILLRECT
2145 select FB_CFB_COPYAREA
2146 select FB_CFB_IMAGEBLIT
2149 This is a framebuffer device for the i.MX31 LCD Controller. So
2150 far only synchronous displays are supported. If you plan to use
2151 an LCD display with your i.MX31 system, say Y here.
2153 config FB_BROADSHEET
2154 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2156 select FB_SYS_FILLRECT
2157 select FB_SYS_COPYAREA
2158 select FB_SYS_IMAGEBLIT
2160 select FB_DEFERRED_IO
2162 This driver implements support for the E-Ink Broadsheet
2163 controller. The release name for this device was Epson S1D13521
2164 and could also have been called by other names when coupled with
2167 source "drivers/video/omap/Kconfig"
2168 source "drivers/video/omap2/Kconfig"
2170 source "drivers/video/backlight/Kconfig"
2171 source "drivers/video/display/Kconfig"
2174 source "drivers/video/console/Kconfig"
2177 if FB || SGI_NEWPORT_CONSOLE
2178 source "drivers/video/logo/Kconfig"