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
407 tristate "Motorola i.MX LCD support"
408 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
409 select FB_CFB_FILLRECT
410 select FB_CFB_COPYAREA
411 select FB_CFB_IMAGEBLIT
414 tristate "CyberPro 2000/2010/5000 support"
415 depends on FB && PCI && (BROKEN || !SPARC64)
416 select FB_CFB_FILLRECT
417 select FB_CFB_COPYAREA
418 select FB_CFB_IMAGEBLIT
420 This enables support for the Integraphics CyberPro 20x0 and 5000
421 VGA chips used in the Rebel.com Netwinder and other machines.
422 Say Y if you have a NetWinder or a graphics card containing this
423 device, otherwise say N.
427 depends on (FB = y) && APOLLO
429 select FB_CFB_FILLRECT
430 select FB_CFB_IMAGEBLIT
434 depends on (FB = y) && Q40
436 select FB_CFB_FILLRECT
437 select FB_CFB_COPYAREA
438 select FB_CFB_IMAGEBLIT
441 tristate "Amiga native chipset support"
442 depends on FB && AMIGA
444 This is the frame buffer device driver for the builtin graphics
445 chipset found in Amigas.
447 To compile this driver as a module, choose M here: the
448 module will be called amifb.
451 bool "Amiga OCS chipset support"
454 This enables support for the original Agnus and Denise video chips,
455 found in the Amiga 1000 and most A500's and A2000's. If you intend
456 to run Linux on any of these systems, say Y; otherwise say N.
459 bool "Amiga ECS chipset support"
462 This enables support for the Enhanced Chip Set, found in later
463 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
464 you intend to run Linux on any of these systems, say Y; otherwise
468 bool "Amiga AGA chipset support"
471 This enables support for the Advanced Graphics Architecture (also
472 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
473 and CD32. If you intend to run Linux on any of these systems, say Y;
477 bool "Amiga FrameMaster II/Rainbow II support"
478 depends on (FB = y) && ZORRO
479 select FB_CFB_FILLRECT
480 select FB_CFB_COPYAREA
481 select FB_CFB_IMAGEBLIT
483 This is the frame buffer device driver for the Amiga FrameMaster
484 card from BSC (exhibited 1992 but not shipped as a CBM product).
487 tristate "Arc Monochrome LCD board support"
489 select FB_SYS_FILLRECT
490 select FB_SYS_COPYAREA
491 select FB_SYS_IMAGEBLIT
494 This enables support for the Arc Monochrome LCD board. The board
495 is based on the KS-108 lcd controller and is typically a matrix
496 of 2*n chips. This driver was tested with a 128x64 panel. This
497 driver supports it for use with x86 SBCs through a 16 bit GPIO
498 interface (8 bit data, 8 bit control). If you anticipate using
499 this driver, say Y or M; otherwise say N. You must specify the
500 GPIO IO address to be used for setting control and data.
503 bool "Atari native chipset support"
504 depends on (FB = y) && ATARI
505 select FB_CFB_FILLRECT
506 select FB_CFB_COPYAREA
507 select FB_CFB_IMAGEBLIT
509 This is the frame buffer device driver for the builtin graphics
510 chipset found in Ataris.
513 bool "Open Firmware frame buffer device support"
514 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
515 select FB_CFB_FILLRECT
516 select FB_CFB_COPYAREA
517 select FB_CFB_IMAGEBLIT
520 Say Y if you want support with Open Firmware for your graphics
524 bool "Apple \"control\" display support"
525 depends on (FB = y) && PPC_PMAC && PPC32
526 select FB_CFB_FILLRECT
527 select FB_CFB_COPYAREA
528 select FB_CFB_IMAGEBLIT
531 This driver supports a frame buffer for the graphics adapter in the
532 Power Macintosh 7300 and others.
535 bool "Apple \"platinum\" display support"
536 depends on (FB = y) && PPC_PMAC && PPC32
537 select FB_CFB_FILLRECT
538 select FB_CFB_COPYAREA
539 select FB_CFB_IMAGEBLIT
542 This driver supports a frame buffer for the "platinum" graphics
543 adapter in some Power Macintoshes.
546 bool "Apple \"valkyrie\" display support"
547 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
548 select FB_CFB_FILLRECT
549 select FB_CFB_COPYAREA
550 select FB_CFB_IMAGEBLIT
553 This driver supports a frame buffer for the "valkyrie" graphics
554 adapter in some Power Macintoshes.
557 bool "Chips 65550 display support"
558 depends on (FB = y) && PPC32 && PCI
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
563 This is the frame buffer device driver for the Chips & Technologies
564 65550 graphics chip in PowerBooks.
567 bool "Asiliant (Chips) 69000 display support"
568 depends on (FB = y) && PCI
569 select FB_CFB_FILLRECT
570 select FB_CFB_COPYAREA
571 select FB_CFB_IMAGEBLIT
573 This is the frame buffer device driver for the Asiliant 69030 chipset
576 bool "IMS Twin Turbo display support"
577 depends on (FB = y) && PCI
578 select FB_CFB_IMAGEBLIT
579 select FB_MACMODES if PPC
581 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
582 many Macintosh and compatible computers.
585 tristate "VGA 16-color graphics support"
586 depends on FB && (X86 || PPC)
587 select FB_CFB_FILLRECT
588 select FB_CFB_COPYAREA
589 select FB_CFB_IMAGEBLIT
591 select FONT_8x16 if FRAMEBUFFER_CONSOLE
593 This is the frame buffer device driver for VGA 16 color graphic
594 cards. Say Y if you have such a card.
596 To compile this driver as a module, choose M here: the
597 module will be called vga16fb.
599 config FB_BF54X_LQ043
600 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
601 depends on FB && (BF54x) && !BF542
602 select FB_CFB_FILLRECT
603 select FB_CFB_COPYAREA
604 select FB_CFB_IMAGEBLIT
606 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
608 config FB_BFIN_T350MCQB
609 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
610 depends on FB && BLACKFIN
612 select FB_CFB_FILLRECT
613 select FB_CFB_COPYAREA
614 select FB_CFB_IMAGEBLIT
616 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
617 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
618 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
620 config FB_BFIN_LQ035Q1
621 tristate "SHARP LQ035Q1DH02 TFT LCD"
622 depends on FB && BLACKFIN && SPI
623 select FB_CFB_FILLRECT
624 select FB_CFB_COPYAREA
625 select FB_CFB_IMAGEBLIT
628 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
629 the Blackfin Landscape LCD EZ-Extender Card.
630 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
631 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
633 To compile this driver as a module, choose M here: the
634 module will be called bfin-lq035q1-fb.
637 tristate "HP STI frame buffer device support"
638 depends on FB && PARISC
639 select FB_CFB_FILLRECT
640 select FB_CFB_COPYAREA
641 select FB_CFB_IMAGEBLIT
646 STI refers to the HP "Standard Text Interface" which is a set of
647 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
648 Enabling this option will implement the linux framebuffer device
649 using calls to the STI BIOS routines for initialisation.
651 If you enable this option, you will get a planar framebuffer device
652 /dev/fb which will work on the most common HP graphic cards of the
653 NGLE family, including the artist chips (in the 7xx and Bxxx series),
654 HCRX, HCRX24, CRX, CRX24 and VisEG series.
656 It is safe to enable this option, so you should probably say "Y".
659 bool "Generic Macintosh display support"
660 depends on (FB = y) && MAC
661 select FB_CFB_FILLRECT
662 select FB_CFB_COPYAREA
663 select FB_CFB_IMAGEBLIT
668 depends on (FB = y) && DIO
669 select FB_CFB_IMAGEBLIT
673 tristate "TGA/SFB+ framebuffer support"
674 depends on FB && (ALPHA || TC)
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
680 This is the frame buffer device driver for generic TGA and SFB+
681 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
682 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
683 TURBOchannel cards, also known as PMAGD-A, -B and -C.
685 Due to hardware limitations ZLX-E2 and E3 cards are not supported
686 for DECstation 5000/200 systems. Additionally due to firmware
687 limitations these cards may cause troubles with booting DECstation
688 5000/240 and /260 systems, but are fully supported under Linux if
689 you manage to get it going. ;-)
691 Say Y if you have one of those.
694 tristate "Userspace VESA VGA graphics support"
695 depends on FB && CONNECTOR
696 select FB_CFB_FILLRECT
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
699 select FB_MODE_HELPERS
701 This is the frame buffer driver for generic VBE 2.0 compliant
702 graphic cards. It can also take advantage of VBE 3.0 features,
703 such as refresh rate adjustment.
705 This driver generally provides more features than vesafb but
706 requires a userspace helper application called 'v86d'. See
707 <file:Documentation/fb/uvesafb.txt> for more information.
712 bool "VESA VGA graphics support"
713 depends on (FB = y) && X86
714 select FB_CFB_FILLRECT
715 select FB_CFB_COPYAREA
716 select FB_CFB_IMAGEBLIT
717 select FB_BOOT_VESA_SUPPORT
719 This is the frame buffer device driver for generic VESA 2.0
720 compliant graphic cards. The older VESA 1.2 cards are not supported.
721 You will get a boot time penguin logo at no additional cost. Please
722 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
725 bool "EFI-based Framebuffer Support"
726 depends on (FB = y) && X86 && EFI
727 select FB_CFB_FILLRECT
728 select FB_CFB_COPYAREA
729 select FB_CFB_IMAGEBLIT
731 This is the EFI frame buffer device driver. If the firmware on
732 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
733 using the EFI framebuffer as your console.
736 tristate "N411 Apollo/Hecuba devkit support"
737 depends on FB && X86 && MMU
738 select FB_SYS_FILLRECT
739 select FB_SYS_COPYAREA
740 select FB_SYS_IMAGEBLIT
742 select FB_DEFERRED_IO
745 This enables support for the Apollo display controller in its
746 Hecuba form using the n411 devkit.
749 tristate "Hercules mono graphics support"
751 select FB_CFB_FILLRECT
752 select FB_CFB_COPYAREA
753 select FB_CFB_IMAGEBLIT
755 Say Y here if you have a Hercules mono graphics card.
757 To compile this driver as a module, choose M here: the
758 module will be called hgafb.
760 As this card technology is 15 years old, most people will answer N
764 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
765 depends on FB_HGA && EXPERIMENTAL
767 This will compile the Hercules mono graphics with
768 acceleration functions.
771 tristate "SGI Visual Workstation framebuffer support"
772 depends on FB && X86_VISWS
773 select FB_CFB_FILLRECT
774 select FB_CFB_COPYAREA
775 select FB_CFB_IMAGEBLIT
777 SGI Visual Workstation support for framebuffer graphics.
780 bool "SGI Graphics Backend frame buffer support"
781 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
782 select FB_CFB_FILLRECT
783 select FB_CFB_COPYAREA
784 select FB_CFB_IMAGEBLIT
786 This is the frame buffer device driver for SGI Graphics Backend.
787 This chip is used in SGI O2 and Visual Workstation 320/540.
790 int "Video memory size in MB"
794 This is the amount of memory reserved for the framebuffer,
795 which can be any value between 1MB and 8MB.
798 bool "SBUS and UPA framebuffers"
799 depends on (FB = y) && SPARC
801 Say Y if you want support for SBUS or UPA based frame buffer device.
805 depends on (FB = y) && (SPARC && FB_SBUS)
806 select FB_CFB_FILLRECT
807 select FB_CFB_COPYAREA
808 select FB_CFB_IMAGEBLIT
810 This is the frame buffer device driver for the BWtwo frame buffer.
813 bool "CGthree support"
814 depends on (FB = y) && (SPARC && FB_SBUS)
815 select FB_CFB_FILLRECT
816 select FB_CFB_COPYAREA
817 select FB_CFB_IMAGEBLIT
819 This is the frame buffer device driver for the CGthree frame buffer.
822 bool "CGsix (GX,TurboGX) support"
823 depends on (FB = y) && (SPARC && FB_SBUS)
824 select FB_CFB_COPYAREA
825 select FB_CFB_IMAGEBLIT
827 This is the frame buffer device driver for the CGsix (GX, TurboGX)
831 bool "Creator/Creator3D/Elite3D support"
832 depends on FB_SBUS && SPARC64
833 select FB_CFB_COPYAREA
834 select FB_CFB_IMAGEBLIT
836 This is the frame buffer device driver for the Creator, Creator3D,
837 and Elite3D graphics boards.
840 bool "TCX (SS4/SS5 only) support"
842 select FB_CFB_FILLRECT
843 select FB_CFB_COPYAREA
844 select FB_CFB_IMAGEBLIT
846 This is the frame buffer device driver for the TCX 24/8bit frame
850 bool "CGfourteen (SX) support"
852 select FB_CFB_FILLRECT
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
856 This is the frame buffer device driver for the CGfourteen frame
857 buffer on Desktop SPARCsystems with the SX graphics option.
860 bool "P9100 (Sparcbook 3 only) support"
862 select FB_CFB_FILLRECT
863 select FB_CFB_COPYAREA
864 select FB_CFB_IMAGEBLIT
866 This is the frame buffer device driver for the P9100 card
867 supported on Sparcbook 3 machines.
870 bool "Leo (ZX) support"
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the frame buffer device driver for the SBUS-based Sun ZX
877 (leo) frame buffer cards.
880 bool "IGA 168x display support"
881 depends on (FB = y) && SPARC32
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the framebuffer device for the INTERGRAPHICS 1680 and
887 successor frame buffer cards.
890 bool "Sun XVR-500 3DLABS Wildcat support"
891 depends on (FB = y) && PCI && SPARC64
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
896 This is the framebuffer device for the Sun XVR-500 and similar
897 graphics cards based upon the 3DLABS Wildcat chipset. The driver
898 only works on sparc64 systems where the system firmware has
899 mostly initialized the card already. It is treated as a
900 completely dumb framebuffer device.
903 bool "Sun XVR-2500 3DLABS Wildcat support"
904 depends on (FB = y) && PCI && SPARC64
905 select FB_CFB_FILLRECT
906 select FB_CFB_COPYAREA
907 select FB_CFB_IMAGEBLIT
909 This is the framebuffer device for the Sun XVR-2500 and similar
910 graphics cards based upon the 3DLABS Wildcat chipset. The driver
911 only works on sparc64 systems where the system firmware has
912 mostly initialized the card already. It is treated as a
913 completely dumb framebuffer device.
916 bool "Sun XVR-1000 support"
917 depends on (FB = y) && SPARC64
918 select FB_CFB_FILLRECT
919 select FB_CFB_COPYAREA
920 select FB_CFB_IMAGEBLIT
922 This is the framebuffer device for the Sun XVR-1000 and similar
923 graphics cards. The driver only works on sparc64 systems where
924 the system firmware has mostly initialized the card already. It
925 is treated as a completely dumb framebuffer device.
928 tristate "NEC PowerVR 2 display support"
929 depends on FB && SH_DREAMCAST
930 select FB_CFB_FILLRECT
931 select FB_CFB_COPYAREA
932 select FB_CFB_IMAGEBLIT
934 Say Y here if you have a PowerVR 2 card in your box. If you plan to
935 run linux on your Dreamcast, you will have to say Y here.
936 This driver may or may not work on other PowerVR 2 cards, but is
937 totally untested. Use at your own risk. If unsure, say N.
939 To compile this driver as a module, choose M here: the
940 module will be called pvr2fb.
942 You can pass several parameters to the driver at boot time or at
943 module load time. The parameters look like "video=pvr2:XXX", where
944 the meaning of XXX can be found at the end of the main source file
945 (<file:drivers/video/pvr2fb.c>). Please see the file
946 <file:Documentation/fb/pvr2fb.txt>.
949 bool "Epson 1355 framebuffer support"
950 depends on (FB = y) && ARCH_CEIVA
951 select FB_CFB_FILLRECT
952 select FB_CFB_COPYAREA
953 select FB_CFB_IMAGEBLIT
955 Build in support for the SED1355 Epson Research Embedded RAMDAC
956 LCD/CRT Controller (since redesignated as the S1D13505) as a
957 framebuffer. Product specs at
958 <http://www.erd.epson.com/vdc/html/products.htm>.
961 tristate "Epson S1D13XXX framebuffer support"
963 select FB_CFB_FILLRECT
964 select FB_CFB_COPYAREA
965 select FB_CFB_IMAGEBLIT
967 Support for S1D13XXX framebuffer device family (currently only
968 working with S1D13806). Product specs at
969 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
972 tristate "AT91/AT32 LCD Controller support"
973 depends on FB && HAVE_FB_ATMEL
974 select FB_CFB_FILLRECT
975 select FB_CFB_COPYAREA
976 select FB_CFB_IMAGEBLIT
978 This enables support for the AT91/AT32 LCD Controller.
981 bool "Frame Buffer in internal SRAM"
982 depends on FB_ATMEL && ARCH_AT91SAM9261
984 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
985 to let frame buffer in external SDRAM.
988 bool "Use a STN display with AT91/AT32 LCD Controller"
989 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
992 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
993 Controller. Say N if you want to connect a TFT.
998 tristate "nVidia Framebuffer Support"
1000 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1001 select FB_MODE_HELPERS
1002 select FB_CFB_FILLRECT
1003 select FB_CFB_COPYAREA
1004 select FB_CFB_IMAGEBLIT
1008 This driver supports graphics boards with the nVidia chips, TNT
1009 and newer. For very old chipsets, such as the RIVA128, then use
1011 Say Y if you have such a graphics board.
1013 To compile this driver as a module, choose M here: the
1014 module will be called nvidiafb.
1016 config FB_NVIDIA_I2C
1017 bool "Enable DDC Support"
1018 depends on FB_NVIDIA
1021 This enables I2C support for nVidia Chipsets. This is used
1022 only for getting EDID information from the attached display
1023 allowing for robust video mode handling and switching.
1025 Because fbdev-2.6 requires that drivers must be able to
1026 independently validate video mode parameters, you should say Y
1029 config FB_NVIDIA_DEBUG
1030 bool "Lots of debug output"
1031 depends on FB_NVIDIA
1034 Say Y here if you want the nVidia driver to output all sorts
1035 of debugging information to provide to the maintainer when
1036 something goes wrong.
1038 config FB_NVIDIA_BACKLIGHT
1039 bool "Support for backlight control"
1040 depends on FB_NVIDIA
1043 Say Y here if you want to control the backlight of your display.
1046 tristate "nVidia Riva support"
1047 depends on FB && PCI
1048 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1049 select FB_MODE_HELPERS
1050 select FB_CFB_FILLRECT
1051 select FB_CFB_COPYAREA
1052 select FB_CFB_IMAGEBLIT
1056 This driver supports graphics boards with the nVidia Riva/Geforce
1058 Say Y if you have such a graphics board.
1060 To compile this driver as a module, choose M here: the
1061 module will be called rivafb.
1064 bool "Enable DDC Support"
1068 This enables I2C support for nVidia Chipsets. This is used
1069 only for getting EDID information from the attached display
1070 allowing for robust video mode handling and switching.
1072 Because fbdev-2.6 requires that drivers must be able to
1073 independently validate video mode parameters, you should say Y
1076 config FB_RIVA_DEBUG
1077 bool "Lots of debug output"
1081 Say Y here if you want the Riva driver to output all sorts
1082 of debugging information to provide to the maintainer when
1083 something goes wrong.
1085 config FB_RIVA_BACKLIGHT
1086 bool "Support for backlight control"
1090 Say Y here if you want to control the backlight of your display.
1093 tristate "Intel 810/815 support (EXPERIMENTAL)"
1094 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1095 select FB_MODE_HELPERS
1096 select FB_CFB_FILLRECT
1097 select FB_CFB_COPYAREA
1098 select FB_CFB_IMAGEBLIT
1101 This driver supports the on-board graphics built in to the Intel 810
1102 and 815 chipsets. Say Y if you have and plan to use such a board.
1104 To compile this driver as a module, choose M here: the
1105 module will be called i810fb.
1107 For more information, please read
1108 <file:Documentation/fb/intel810.txt>
1111 bool "use VESA Generalized Timing Formula"
1114 If you say Y, then the VESA standard, Generalized Timing Formula
1115 or GTF, will be used to calculate the required video timing values
1116 per video mode. Since the GTF allows nondiscrete timings
1117 (nondiscrete being a range of values as opposed to discrete being a
1118 set of values), you'll be able to use any combination of horizontal
1119 and vertical resolutions, and vertical refresh rates without having
1120 to specify your own timing parameters. This is especially useful
1121 to maximize the performance of an aging display, or if you just
1122 have a display with nonstandard dimensions. A VESA compliant
1123 monitor is recommended, but can still work with non-compliant ones.
1124 If you need or want this, then select this option. The timings may
1125 not be compliant with Intel's recommended values. Use at your own
1128 If you say N, the driver will revert to discrete video timings
1129 using a set recommended by Intel in their documentation.
1134 bool "Enable DDC Support"
1135 depends on FB_I810 && FB_I810_GTF
1140 tristate "Intel LE80578 (Vermilion) support"
1141 depends on FB && PCI && X86
1142 select FB_MODE_HELPERS
1143 select FB_CFB_FILLRECT
1144 select FB_CFB_COPYAREA
1145 select FB_CFB_IMAGEBLIT
1147 This driver supports the LE80578 (Vermilion Range) chipset
1149 config FB_CARILLO_RANCH
1150 tristate "Intel Carillo Ranch support"
1151 depends on FB_LE80578 && FB && PCI && X86
1153 This driver supports the LE80578 (Carillo Ranch) board
1156 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1157 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1158 select FB_MODE_HELPERS
1159 select FB_CFB_FILLRECT
1160 select FB_CFB_COPYAREA
1161 select FB_CFB_IMAGEBLIT
1162 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1163 depends on !DRM_I915
1165 This driver supports the on-board graphics built in to the Intel
1166 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1167 Say Y if you have and plan to use such a board.
1169 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1171 To compile this driver as a module, choose M here: the
1172 module will be called intelfb.
1174 For more information, please read <file:Documentation/fb/intelfb.txt>
1176 config FB_INTEL_DEBUG
1177 bool "Intel driver Debug Messages"
1180 Say Y here if you want the Intel driver to output all sorts
1181 of debugging information to provide to the maintainer when
1182 something goes wrong.
1185 bool "DDC/I2C for Intel framebuffer support"
1190 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1193 tristate "Matrox acceleration"
1194 depends on FB && PCI
1195 select FB_CFB_FILLRECT
1196 select FB_CFB_COPYAREA
1197 select FB_CFB_IMAGEBLIT
1198 select FB_TILEBLITTING
1199 select FB_MACMODES if PPC_PMAC
1201 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1202 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1203 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1204 Matrox G400, G450 or G550 card in your box.
1206 To compile this driver as a module, choose M here: the
1207 module will be called matroxfb.
1209 You can pass several parameters to the driver at boot time or at
1210 module load time. The parameters look like "video=matrox:XXX", and
1211 are described in <file:Documentation/fb/matroxfb.txt>.
1213 config FB_MATROX_MILLENIUM
1214 bool "Millennium I/II support"
1215 depends on FB_MATROX
1217 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1218 video card. If you select "Advanced lowlevel driver options" below,
1219 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1220 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1221 also use font widths different from 8.
1223 config FB_MATROX_MYSTIQUE
1224 bool "Mystique support"
1225 depends on FB_MATROX
1227 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1228 video card. If you select "Advanced lowlevel driver options" below,
1229 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1230 packed pixel and 32 bpp packed pixel. You can also use font widths
1234 bool "G100/G200/G400/G450/G550 support"
1235 depends on FB_MATROX
1237 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1238 video card. If you select "Advanced lowlevel driver options", you
1239 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1240 pixel and 32 bpp packed pixel. You can also use font widths
1243 If you need support for G400 secondary head, you must say Y to
1244 "Matrox I2C support" and "G400 second head support" right below.
1245 G450/G550 secondary head and digital output are supported without
1248 The driver starts in monitor mode. You must use the matroxset tool
1249 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1250 swap primary and secondary head outputs, or to change output mode.
1251 Secondary head driver always start in 640x480 resolution and you
1252 must use fbset to change it.
1254 Do not forget that second head supports only 16 and 32 bpp
1255 packed pixels, so it is a good idea to compile them into the kernel
1256 too. You can use only some font widths, as the driver uses generic
1257 painting procedures (the secondary head does not use acceleration
1260 G450/G550 hardware can display TV picture only from secondary CRTC,
1261 and it performs no scaling, so picture must have 525 or 625 lines.
1263 config FB_MATROX_I2C
1264 tristate "Matrox I2C support"
1265 depends on FB_MATROX
1268 This drivers creates I2C buses which are needed for accessing the
1269 DDC (I2C) bus present on all Matroxes, an I2C bus which
1270 interconnects Matrox optional devices, like MGA-TVO on G200 and
1271 G400, and the secondary head DDC bus, present on G400 only.
1273 You can say Y or M here if you want to experiment with monitor
1274 detection code. You must say Y or M here if you want to use either
1275 second head of G400 or MGA-TVO on G200 or G400.
1277 If you compile it as module, it will create a module named
1280 config FB_MATROX_MAVEN
1281 tristate "G400 second head support"
1282 depends on FB_MATROX_G && FB_MATROX_I2C
1284 WARNING !!! This support does not work with G450 !!!
1286 Say Y or M here if you want to use a secondary head (meaning two
1287 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1288 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1289 secondary head output is blanked while you are in X. With XFree
1290 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1291 the fbdev driver on first head and the fbdev driver on second head.
1293 If you compile it as module, two modules are created,
1294 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1295 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1296 also load i2c-matroxfb to get it to run.
1298 The driver starts in monitor mode and you must use the matroxset
1300 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1301 PAL or NTSC or to swap primary and secondary head outputs.
1302 Secondary head driver also always start in 640x480 resolution, you
1303 must use fbset to change it.
1305 Also do not forget that second head supports only 16 and 32 bpp
1306 packed pixels, so it is a good idea to compile them into the kernel
1307 too. You can use only some font widths, as the driver uses generic
1308 painting procedures (the secondary head does not use acceleration
1312 tristate "ATI Radeon display support"
1313 depends on FB && PCI
1314 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1315 select FB_MODE_HELPERS
1316 select FB_CFB_FILLRECT
1317 select FB_CFB_COPYAREA
1318 select FB_CFB_IMAGEBLIT
1319 select FB_MACMODES if PPC_OF
1321 Choose this option if you want to use an ATI Radeon graphics card as
1322 a framebuffer device. There are both PCI and AGP versions. You
1323 don't need to choose this to run the Radeon in plain VGA mode.
1325 There is a product page at
1326 http://apps.ati.com/ATIcompare/
1328 config FB_RADEON_I2C
1329 bool "DDC/I2C for ATI Radeon support"
1330 depends on FB_RADEON
1334 Say Y here if you want DDC/I2C support for your Radeon board.
1336 config FB_RADEON_BACKLIGHT
1337 bool "Support for backlight control"
1338 depends on FB_RADEON
1341 Say Y here if you want to control the backlight of your display.
1343 config FB_RADEON_DEBUG
1344 bool "Lots of debug output from Radeon driver"
1345 depends on FB_RADEON
1348 Say Y here if you want the Radeon driver to output all sorts
1349 of debugging information to provide to the maintainer when
1350 something goes wrong.
1353 tristate "ATI Rage128 display support"
1354 depends on FB && PCI
1355 select FB_CFB_FILLRECT
1356 select FB_CFB_COPYAREA
1357 select FB_CFB_IMAGEBLIT
1358 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1359 select FB_MACMODES if PPC_PMAC
1361 This driver supports graphics boards with the ATI Rage128 chips.
1362 Say Y if you have such a graphics board and read
1363 <file:Documentation/fb/aty128fb.txt>.
1365 To compile this driver as a module, choose M here: the
1366 module will be called aty128fb.
1368 config FB_ATY128_BACKLIGHT
1369 bool "Support for backlight control"
1370 depends on FB_ATY128
1373 Say Y here if you want to control the backlight of your display.
1376 tristate "ATI Mach64 display support" if PCI || ATARI
1377 depends on FB && !SPARC32
1378 select FB_CFB_FILLRECT
1379 select FB_CFB_COPYAREA
1380 select FB_CFB_IMAGEBLIT
1381 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1382 select FB_MACMODES if PPC
1384 This driver supports graphics boards with the ATI Mach64 chips.
1385 Say Y if you have such a graphics board.
1387 To compile this driver as a module, choose M here: the
1388 module will be called atyfb.
1391 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1392 depends on PCI && FB_ATY
1393 default y if SPARC64 && PCI
1395 Say Y here to support use of ATI's 64-bit Rage boards (or other
1396 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1397 framebuffer device. The ATI product support page for these boards
1398 is at <http://support.ati.com/products/pc/mach64/>.
1400 config FB_ATY_GENERIC_LCD
1401 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1402 depends on FB_ATY_CT
1404 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1405 Rage XC, or Rage XL chipset.
1408 bool "Mach64 GX support" if PCI
1412 Say Y here to support use of the ATI Mach64 Graphics Expression
1413 board (or other boards based on the Mach64 GX chipset) as a
1414 framebuffer device. The ATI product support page for these boards
1416 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1418 config FB_ATY_BACKLIGHT
1419 bool "Support for backlight control"
1423 Say Y here if you want to control the backlight of your display.
1426 tristate "S3 Trio/Virge support"
1427 depends on FB && PCI
1428 select FB_CFB_FILLRECT
1429 select FB_CFB_COPYAREA
1430 select FB_CFB_IMAGEBLIT
1431 select FB_TILEBLITTING
1434 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1436 Driver for graphics boards with S3 Trio / S3 Virge chip.
1439 tristate "S3 Savage support"
1440 depends on FB && PCI && EXPERIMENTAL
1441 select FB_MODE_HELPERS
1442 select FB_CFB_FILLRECT
1443 select FB_CFB_COPYAREA
1444 select FB_CFB_IMAGEBLIT
1447 This driver supports notebooks and computers with S3 Savage PCI/AGP
1450 Say Y if you have such a graphics card.
1452 To compile this driver as a module, choose M here; the module
1453 will be called savagefb.
1455 config FB_SAVAGE_I2C
1456 bool "Enable DDC2 Support"
1457 depends on FB_SAVAGE
1460 This enables I2C support for S3 Savage Chipsets. This is used
1461 only for getting EDID information from the attached display
1462 allowing for robust video mode handling and switching.
1464 Because fbdev-2.6 requires that drivers must be able to
1465 independently validate video mode parameters, you should say Y
1468 config FB_SAVAGE_ACCEL
1469 bool "Enable Console Acceleration"
1470 depends on FB_SAVAGE
1473 This option will compile in console acceleration support. If
1474 the resulting framebuffer console has bothersome glitches, then
1478 tristate "SiS/XGI display support"
1479 depends on FB && PCI
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1482 select FB_CFB_IMAGEBLIT
1483 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1485 This is the frame buffer device driver for the SiS 300, 315, 330
1486 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1487 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1489 To compile this driver as a module, choose M here; the module
1490 will be called sisfb.
1493 bool "SiS 300 series support"
1496 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1499 bool "SiS 315/330/340 series and XGI support"
1502 Say Y here to support use of the SiS 315, 330 and 340 series
1503 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1504 as XGI V3XT, V5, V8 and Z7.
1507 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1508 depends on FB && PCI
1509 select FB_CFB_FILLRECT
1510 select FB_CFB_COPYAREA
1511 select FB_CFB_IMAGEBLIT
1515 This is the frame buffer device driver for Graphics chips of VIA
1516 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1517 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1519 Say Y if you have a VIA UniChrome graphics board.
1521 To compile this driver as a module, choose M here: the
1522 module will be called viafb.
1524 tristate "NeoMagic display support"
1525 depends on FB && PCI
1526 select FB_MODE_HELPERS
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1529 select FB_CFB_IMAGEBLIT
1532 This driver supports notebooks with NeoMagic PCI chips.
1533 Say Y if you have such a graphics card.
1535 To compile this driver as a module, choose M here: the
1536 module will be called neofb.
1539 tristate "IMG Kyro support"
1540 depends on FB && PCI
1541 select FB_CFB_FILLRECT
1542 select FB_CFB_COPYAREA
1543 select FB_CFB_IMAGEBLIT
1545 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1548 To compile this driver as a module, choose M here: the
1549 module will be called kyrofb.
1552 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1553 depends on FB && PCI
1554 select FB_CFB_IMAGEBLIT
1555 select FB_CFB_FILLRECT
1556 select FB_CFB_COPYAREA
1557 select FB_MODE_HELPERS
1559 This driver supports graphics boards with the 3Dfx Banshee,
1560 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1561 such a graphics board.
1563 To compile this driver as a module, choose M here: the
1564 module will be called tdfxfb.
1566 config FB_3DFX_ACCEL
1567 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1568 depends on FB_3DFX && EXPERIMENTAL
1570 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1571 device driver with acceleration functions.
1574 bool "Enable DDC/I2C support"
1575 depends on FB_3DFX && EXPERIMENTAL
1579 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1582 tristate "3Dfx Voodoo Graphics (sst1) support"
1583 depends on FB && PCI
1584 select FB_CFB_FILLRECT
1585 select FB_CFB_COPYAREA
1586 select FB_CFB_IMAGEBLIT
1588 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1589 Voodoo2 (cvg) based graphics card.
1591 To compile this driver as a module, choose M here: the
1592 module will be called sstfb.
1594 WARNING: Do not use any application that uses the 3D engine
1595 (namely glide) while using this driver.
1596 Please read the <file:Documentation/fb/sstfb.txt> for supported
1597 options and other important info support.
1600 tristate "VIA VT8623 support"
1601 depends on FB && PCI
1602 select FB_CFB_FILLRECT
1603 select FB_CFB_COPYAREA
1604 select FB_CFB_IMAGEBLIT
1605 select FB_TILEBLITTING
1608 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1610 Driver for CastleRock integrated graphics core in the
1611 VIA VT8623 [Apollo CLE266] chipset.
1614 tristate "Trident/CyberXXX/CyberBlade support"
1615 depends on FB && PCI
1616 select FB_CFB_FILLRECT
1617 select FB_CFB_COPYAREA
1618 select FB_CFB_IMAGEBLIT
1620 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1621 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1623 There are also integrated versions of these chips called CyberXXXX,
1624 CyberImage or CyberBlade. These chips are mostly found in laptops
1625 but also on some motherboards including early VIA EPIA motherboards.
1626 For more information, read <file:Documentation/fb/tridentfb.txt>
1628 Say Y if you have such a graphics board.
1630 To compile this driver as a module, choose M here: the
1631 module will be called tridentfb.
1634 tristate "ARK 2000PV support"
1635 depends on FB && PCI
1636 select FB_CFB_FILLRECT
1637 select FB_CFB_COPYAREA
1638 select FB_CFB_IMAGEBLIT
1639 select FB_TILEBLITTING
1642 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1644 Driver for PCI graphics boards with ARK 2000PV chip
1645 and ICS 5342 RAMDAC.
1648 tristate "Permedia3 support (EXPERIMENTAL)"
1649 depends on FB && PCI && EXPERIMENTAL
1650 select FB_CFB_FILLRECT
1651 select FB_CFB_COPYAREA
1652 select FB_CFB_IMAGEBLIT
1654 This is the frame buffer device driver for the 3DLabs Permedia3
1655 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1656 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1657 and maybe other boards.
1660 tristate "Fujitsu carmine frame buffer support"
1661 depends on FB && PCI
1662 select FB_CFB_FILLRECT
1663 select FB_CFB_COPYAREA
1664 select FB_CFB_IMAGEBLIT
1666 This is the frame buffer device driver for the Fujitsu Carmine chip.
1667 The driver provides two independent frame buffer devices.
1670 depends on FB_CARMINE
1671 prompt "DRAM timing"
1672 default FB_CARMINE_DRAM_EVAL
1674 config FB_CARMINE_DRAM_EVAL
1675 bool "Eval board timings"
1677 Use timings which work on the eval card.
1679 config CARMINE_DRAM_CUSTOM
1680 bool "Custom board timings"
1682 Use custom board timings.
1686 bool "Au1100 LCD Driver"
1687 depends on (FB = y) && MIPS && SOC_AU1100
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1692 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1693 various panels and CRTs by passing in kernel cmd line option
1694 au1100fb:panel=<name>.
1697 bool "Au1200 LCD Driver"
1698 depends on (FB = y) && MIPS && SOC_AU1200
1699 select FB_CFB_FILLRECT
1700 select FB_CFB_COPYAREA
1701 select FB_CFB_IMAGEBLIT
1703 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1704 various panels and CRTs by passing in kernel cmd line option
1705 au1200fb:panel=<name>.
1707 source "drivers/video/geode/Kconfig"
1710 tristate "HD64461 Frame Buffer support"
1711 depends on FB && HD64461
1712 select FB_CFB_FILLRECT
1713 select FB_CFB_COPYAREA
1714 select FB_CFB_IMAGEBLIT
1716 This is the frame buffer device driver for the Hitachi HD64461 LCD
1720 bool "PMAG-AA TURBOchannel framebuffer support"
1721 depends on (FB = y) && TC
1722 select FB_CFB_FILLRECT
1723 select FB_CFB_COPYAREA
1724 select FB_CFB_IMAGEBLIT
1726 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1727 used mainly in the MIPS-based DECstation series.
1730 tristate "PMAG-BA TURBOchannel framebuffer support"
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1736 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1737 used mainly in the MIPS-based DECstation series.
1740 tristate "PMAGB-B TURBOchannel framebuffer support"
1742 select FB_CFB_FILLRECT
1743 select FB_CFB_COPYAREA
1744 select FB_CFB_IMAGEBLIT
1746 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1747 in the MIPS-based DECstation series. The card is currently only
1748 supported in 1280x1024x8 mode.
1751 bool "Maxine (Personal DECstation) onboard framebuffer support"
1752 depends on (FB = y) && MACH_DECSTATION
1753 select FB_CFB_FILLRECT
1754 select FB_CFB_COPYAREA
1755 select FB_CFB_IMAGEBLIT
1757 Support for the onboard framebuffer (1024x768x8) in the Personal
1758 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1762 bool "G364 frame buffer support"
1763 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1764 select FB_CFB_FILLRECT
1765 select FB_CFB_COPYAREA
1766 select FB_CFB_IMAGEBLIT
1768 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1769 Olivetti M700-10 systems.
1772 bool "Motorola 68328 native frame buffer support"
1773 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1774 select FB_CFB_FILLRECT
1775 select FB_CFB_COPYAREA
1776 select FB_CFB_IMAGEBLIT
1778 Say Y here if you want to support the built-in frame buffer of
1779 the Motorola 68328 CPU family.
1782 tristate "PXA168/910 LCD framebuffer support"
1783 depends on FB && (CPU_PXA168 || CPU_PXA910)
1784 select FB_CFB_FILLRECT
1785 select FB_CFB_COPYAREA
1786 select FB_CFB_IMAGEBLIT
1788 Frame buffer driver for the built-in LCD controller in the Marvell
1792 tristate "PXA LCD framebuffer support"
1793 depends on FB && ARCH_PXA
1794 select FB_CFB_FILLRECT
1795 select FB_CFB_COPYAREA
1796 select FB_CFB_IMAGEBLIT
1798 Frame buffer driver for the built-in LCD controller in the Intel
1801 This driver is also available as a module ( = code which can be
1802 inserted and removed from the running kernel whenever you want). The
1803 module will be called pxafb. If you want to compile it as a module,
1804 say M here and read <file:Documentation/kbuild/modules.txt>.
1808 config FB_PXA_OVERLAY
1809 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1811 depends on FB_PXA && (PXA27x || PXA3xx)
1813 config FB_PXA_SMARTPANEL
1814 bool "PXA Smartpanel LCD support"
1818 config FB_PXA_PARAMETERS
1819 bool "PXA LCD command line parameters"
1823 Enable the use of kernel command line or module parameters
1824 to configure the physical properties of the LCD panel when
1825 using the PXA LCD driver.
1827 This option allows you to override the panel parameters
1828 supplied by the platform in order to support multiple
1829 different models of flatpanel. If you will only be using a
1830 single model of flatpanel then you can safely leave this
1833 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1836 tristate "2700G LCD framebuffer support"
1837 depends on FB && ARCH_PXA
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1846 bool "Enable debugging info via debugfs"
1847 depends on FB_MBX && DEBUG_FS
1850 Enable this if you want debugging information using the debug
1851 filesystem (debugfs)
1856 tristate "Freescale DIU framebuffer support"
1857 depends on FB && FSL_SOC
1858 select FB_CFB_FILLRECT
1859 select FB_CFB_COPYAREA
1860 select FB_CFB_IMAGEBLIT
1861 select PPC_LIB_RHEAP
1863 Framebuffer driver for the Freescale SoC DIU
1866 tristate "W100 frame buffer support"
1867 depends on FB && ARCH_PXA
1868 select FB_CFB_FILLRECT
1869 select FB_CFB_COPYAREA
1870 select FB_CFB_IMAGEBLIT
1872 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1873 It can also drive the w3220 chip found on iPAQ hx4700.
1875 This driver is also available as a module ( = code which can be
1876 inserted and removed from the running kernel whenever you want). The
1877 module will be called w100fb. If you want to compile it as a module,
1878 say M here and read <file:Documentation/kbuild/modules.txt>.
1882 config FB_SH_MOBILE_LCDC
1883 tristate "SuperH Mobile LCDC framebuffer support"
1884 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1885 select FB_SYS_FILLRECT
1886 select FB_SYS_COPYAREA
1887 select FB_SYS_IMAGEBLIT
1889 select FB_DEFERRED_IO
1891 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1894 tristate "Toshiba Mobile IO FrameBuffer support"
1895 depends on FB && MFD_CORE
1896 select FB_CFB_FILLRECT
1897 select FB_CFB_COPYAREA
1898 select FB_CFB_IMAGEBLIT
1900 Frame buffer driver for the Toshiba Mobile IO integrated as found
1901 on the Sharp SL-6000 series
1903 This driver is also available as a module ( = code which can be
1904 inserted and removed from the running kernel whenever you want). The
1905 module will be called tmiofb. If you want to compile it as a module,
1906 say M here and read <file:Documentation/kbuild/modules.txt>.
1910 config FB_TMIO_ACCELL
1911 bool "tmiofb acceleration"
1916 tristate "Samsung S3C framebuffer support"
1917 depends on FB && ARCH_S3C64XX
1918 select FB_CFB_FILLRECT
1919 select FB_CFB_COPYAREA
1920 select FB_CFB_IMAGEBLIT
1922 Frame buffer driver for the built-in FB controller in the Samsung
1923 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1924 and the S3C64XX series such as the S3C6400 and S3C6410.
1926 These chips all have the same basic framebuffer design with the
1927 actual capabilities depending on the chip. For instance the S3C6400
1928 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1929 currently only have two.
1931 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1933 config FB_S3C_DEBUG_REGWRITE
1934 bool "Debug register writes"
1937 Show all register writes via printk(KERN_DEBUG)
1940 tristate "S3C2410 LCD framebuffer support"
1941 depends on FB && ARCH_S3C2410
1942 select FB_CFB_FILLRECT
1943 select FB_CFB_COPYAREA
1944 select FB_CFB_IMAGEBLIT
1946 Frame buffer driver for the built-in LCD controller in the Samsung
1949 This driver is also available as a module ( = code which can be
1950 inserted and removed from the running kernel whenever you want). The
1951 module will be called s3c2410fb. If you want to compile it as a module,
1952 say M here and read <file:Documentation/kbuild/modules.txt>.
1955 config FB_S3C2410_DEBUG
1956 bool "S3C2410 lcd debug messages"
1957 depends on FB_S3C2410
1959 Turn on debugging messages. Note that you can set/unset at run time
1963 bool "NUC900 LCD framebuffer support"
1964 depends on FB && ARCH_W90X900
1965 select FB_CFB_FILLRECT
1966 select FB_CFB_COPYAREA
1967 select FB_CFB_IMAGEBLIT
1969 Frame buffer driver for the built-in LCD controller in the Nuvoton
1972 config GPM1040A0_320X240
1973 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
1974 depends on FB_NUC900
1976 config FB_NUC900_DEBUG
1977 bool "NUC900 lcd debug messages"
1978 depends on FB_NUC900
1980 Turn on debugging messages. Note that you can set/unset at run time
1984 tristate "Silicon Motion SM501 framebuffer support"
1985 depends on FB && MFD_SM501
1986 select FB_CFB_FILLRECT
1987 select FB_CFB_COPYAREA
1988 select FB_CFB_IMAGEBLIT
1990 Frame buffer driver for the CRT and LCD controllers in the Silicon
1993 This driver is also available as a module ( = code which can be
1994 inserted and removed from the running kernel whenever you want). The
1995 module will be called sm501fb. If you want to compile it as a module,
1996 say M here and read <file:Documentation/kbuild/modules.txt>.
2001 config FB_PNX4008_DUM
2002 tristate "Display Update Module support on Philips PNX4008 board"
2003 depends on FB && ARCH_PNX4008
2005 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2007 config FB_PNX4008_DUM_RGB
2008 tristate "RGB Framebuffer support on Philips PNX4008 board"
2009 depends on FB_PNX4008_DUM
2010 select FB_CFB_FILLRECT
2011 select FB_CFB_COPYAREA
2012 select FB_CFB_IMAGEBLIT
2014 Say Y here to enable support for PNX4008 RGB Framebuffer
2016 config FB_IBM_GXT4500
2017 tristate "Framebuffer support for IBM GXT4500P adaptor"
2018 depends on FB && PPC
2019 select FB_CFB_FILLRECT
2020 select FB_CFB_COPYAREA
2021 select FB_CFB_IMAGEBLIT
2023 Say Y here to enable support for the IBM GXT4500P display
2024 adaptor, found on some IBM System P (pSeries) machines.
2027 tristate "PS3 GPU framebuffer driver"
2028 depends on FB && PS3_PS3AV
2029 select FB_SYS_FILLRECT
2030 select FB_SYS_COPYAREA
2031 select FB_SYS_IMAGEBLIT
2033 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2035 Include support for the virtual frame buffer in the PS3 platform.
2037 config FB_PS3_DEFAULT_SIZE_M
2038 int "PS3 default frame buffer size (in MiB)"
2042 This is the default size (in MiB) of the virtual frame buffer in
2044 The default value can be overridden on the kernel command line
2045 using the "ps3fb" option (e.g. "ps3fb=9M");
2048 tristate "Xilinx frame buffer support"
2049 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2050 select FB_CFB_FILLRECT
2051 select FB_CFB_COPYAREA
2052 select FB_CFB_IMAGEBLIT
2054 Include support for the Xilinx ML300/ML403 reference design
2055 framebuffer. ML300 carries a 640*480 LCD display on the board,
2056 ML403 uses a standard DB15 VGA connector.
2059 tristate "Cobalt server LCD frame buffer support"
2060 depends on FB && MIPS_COBALT
2063 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2064 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2065 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2066 select FB_CFB_FILLRECT
2067 select FB_CFB_COPYAREA
2068 select FB_CFB_IMAGEBLIT
2070 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2071 (D)STN/TFT LCD Controller.
2072 Supports display resolutions up to 1024x1024 pixel, grayscale and
2073 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2074 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2075 panels <= 320 pixel horizontal resolution.
2078 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2079 depends on FB && ARCH_DAVINCI_DA8XX
2080 select FB_CFB_FILLRECT
2081 select FB_CFB_COPYAREA
2082 select FB_CFB_IMAGEBLIT
2084 This is the frame buffer device driver for the TI LCD controller
2085 found on DA8xx/OMAP-L1xx SoCs.
2089 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2091 select FB_SYS_FILLRECT
2092 select FB_SYS_COPYAREA
2093 select FB_SYS_IMAGEBLIT
2096 This is a `virtual' frame buffer device. It operates on a chunk of
2097 unswappable kernel memory instead of on the memory of a graphics
2098 board. This means you cannot see any output sent to this frame
2099 buffer device, while it does consume precious memory. The main use
2100 of this frame buffer device is testing and debugging the frame
2101 buffer subsystem. Do NOT enable it for normal systems! To protect
2102 the innocent, it has to be enabled explicitly at boot time using the
2103 kernel option `video=vfb:'.
2105 To compile this driver as a module, choose M here: the
2106 module will be called vfb. In order to load it, you must use
2107 the vfb_enable=1 option.
2111 config XEN_FBDEV_FRONTEND
2112 tristate "Xen virtual frame buffer support"
2113 depends on FB && XEN
2114 select FB_SYS_FILLRECT
2115 select FB_SYS_COPYAREA
2116 select FB_SYS_IMAGEBLIT
2118 select FB_DEFERRED_IO
2119 select XEN_XENBUS_FRONTEND
2122 This driver implements the front-end of the Xen virtual
2123 frame buffer driver. It communicates with a back-end
2127 tristate "E-Ink Metronome/8track controller support"
2129 select FB_SYS_FILLRECT
2130 select FB_SYS_COPYAREA
2131 select FB_SYS_IMAGEBLIT
2133 select FB_DEFERRED_IO
2135 This driver implements support for the E-Ink Metronome
2136 controller. The pre-release name for this device was 8track
2137 and could also have been called by some vendors as PVI-nnnn.
2140 tristate "Fujitsu MB862xx GDC support"
2142 select FB_CFB_FILLRECT
2143 select FB_CFB_COPYAREA
2144 select FB_CFB_IMAGEBLIT
2146 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2148 config FB_MB862XX_PCI_GDC
2149 bool "Carmine/Coral-P(A) GDC"
2150 depends on PCI && FB_MB862XX
2152 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2153 PCI graphics controller devices.
2155 config FB_MB862XX_LIME
2157 depends on FB_MB862XX
2158 depends on OF && !FB_MB862XX_PCI_GDC
2160 select FB_FOREIGN_ENDIAN
2161 select FB_LITTLE_ENDIAN
2163 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2166 tristate "EP93XX frame buffer support"
2167 depends on FB && ARCH_EP93XX
2168 select FB_CFB_FILLRECT
2169 select FB_CFB_COPYAREA
2170 select FB_CFB_IMAGEBLIT
2172 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2173 This driver is also available as a module. The module will be called
2176 config FB_PRE_INIT_FB
2177 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2178 depends on FB && FB_MB862XX_LIME
2180 Select this option if display contents should be inherited as set by
2184 tristate "MSM Framebuffer support"
2185 depends on FB && ARCH_MSM
2186 select FB_CFB_FILLRECT
2187 select FB_CFB_COPYAREA
2188 select FB_CFB_IMAGEBLIT
2192 tristate "MX3 Framebuffer support"
2193 depends on FB && MX3_IPU
2194 select FB_CFB_FILLRECT
2195 select FB_CFB_COPYAREA
2196 select FB_CFB_IMAGEBLIT
2199 This is a framebuffer device for the i.MX31 LCD Controller. So
2200 far only synchronous displays are supported. If you plan to use
2201 an LCD display with your i.MX31 system, say Y here.
2203 config FB_BROADSHEET
2204 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2206 select FB_SYS_FILLRECT
2207 select FB_SYS_COPYAREA
2208 select FB_SYS_IMAGEBLIT
2210 select FB_DEFERRED_IO
2212 This driver implements support for the E-Ink Broadsheet
2213 controller. The release name for this device was Epson S1D13521
2214 and could also have been called by other names when coupled with
2217 source "drivers/video/omap/Kconfig"
2218 source "drivers/video/omap2/Kconfig"
2220 source "drivers/video/backlight/Kconfig"
2221 source "drivers/video/display/Kconfig"
2224 source "drivers/video/console/Kconfig"
2227 if FB || SGI_NEWPORT_CONSOLE
2228 source "drivers/video/logo/Kconfig"