5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/gpu/vga/Kconfig"
12 source "drivers/gpu/drm/Kconfig"
18 config VIDEO_OUTPUT_CONTROL
19 tristate "Lowlevel video output switch controls"
21 This framework adds support for low-level control of the video
25 tristate "Support for frame buffer devices"
27 The frame buffer device provides an abstraction for the graphics
28 hardware. It represents the frame buffer of some video hardware and
29 allows application software to access the graphics hardware through
30 a well-defined interface, so the software doesn't need to know
31 anything about the low-level (hardware register) stuff.
33 Frame buffer devices work identically across the different
34 architectures supported by Linux and make the implementation of
35 application programs easier and more portable; at this point, an X
36 server exists which uses the frame buffer device exclusively.
37 On several non-X86 architectures, the frame buffer device is the
38 only way to use the graphics hardware.
40 The device is accessed through special device nodes, usually located
41 in the /dev directory, i.e. /dev/fb*.
43 You need an utility program called fbset to make full use of frame
44 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
45 and the Framebuffer-HOWTO at
46 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more
49 Say Y here and to the driver for your graphics board below if you
50 are compiling a kernel for a non-x86 architecture.
52 If you are compiling for the x86 architecture, you can say Y if you
53 want to play with it, but it is not essential. Please note that
54 running graphical applications that directly touch the hardware
55 (e.g. an accelerated X server) and that are not frame buffer
56 device-aware may cause unexpected results. If unsure, say N.
59 bool "Enable firmware EDID"
63 This enables access to the EDID transferred from the firmware.
64 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
65 transfers do not work for your driver and if you are using
66 nvidiafb, i810fb or savagefb.
68 In general, choosing Y for this option is safe. If you
69 experience extremely long delays while booting before you get
70 something on your display, try setting this to N. Matrox cards in
71 combination with certain motherboards and monitors are known to
72 suffer from this problem.
81 config FB_BOOT_VESA_SUPPORT
86 If true, at least one selected framebuffer driver can take advantage
87 of VESA video modes set at an early boot stage via the vga= parameter.
89 config FB_CFB_FILLRECT
94 Include the cfb_fillrect function for generic software rectangle
95 filling. This is used by drivers that don't provide their own
96 (accelerated) version.
98 config FB_CFB_COPYAREA
103 Include the cfb_copyarea function for generic software area copying.
104 This is used by drivers that don't provide their own (accelerated)
107 config FB_CFB_IMAGEBLIT
112 Include the cfb_imageblit function for generic software image
113 blitting. This is used by drivers that don't provide their own
114 (accelerated) version.
116 config FB_CFB_REV_PIXELS_IN_BYTE
121 Allow generic frame-buffer functions to work on displays with 1, 2
122 and 4 bits per pixel depths which has opposite order of pixels in
123 byte order to bytes in long order.
125 config FB_SYS_FILLRECT
130 Include the sys_fillrect function for generic software rectangle
131 filling. This is used by drivers that don't provide their own
132 (accelerated) version and the framebuffer is in system RAM.
134 config FB_SYS_COPYAREA
139 Include the sys_copyarea function for generic software area copying.
140 This is used by drivers that don't provide their own (accelerated)
141 version and the framebuffer is in system RAM.
143 config FB_SYS_IMAGEBLIT
148 Include the sys_imageblit function for generic software image
149 blitting. This is used by drivers that don't provide their own
150 (accelerated) version and the framebuffer is in system RAM.
152 menuconfig FB_FOREIGN_ENDIAN
153 bool "Framebuffer foreign endianness support"
156 This menu will let you enable support for the framebuffers with
157 non-native endianness (e.g. Little-Endian framebuffer on a
158 Big-Endian machine). Most probably you don't have such hardware,
159 so it's safe to say "n" here.
162 prompt "Choice endianness support"
163 depends on FB_FOREIGN_ENDIAN
165 config FB_BOTH_ENDIAN
166 bool "Support for Big- and Little-Endian framebuffers"
169 bool "Support for Big-Endian framebuffers only"
171 config FB_LITTLE_ENDIAN
172 bool "Support for Little-Endian framebuffers only"
181 config FB_DEFERRED_IO
188 depends on FB_DEFERRED_IO
195 Common utility functions useful to fbdev drivers of VGA-based
206 select BACKLIGHT_LCD_SUPPORT
207 select BACKLIGHT_CLASS_DEVICE
210 config FB_MODE_HELPERS
211 bool "Enable Video Mode Handling Helpers"
215 This enables functions for handling video modes using the
216 Generalized Timing Formula and the EDID parser. A few drivers rely
217 on this feature such as the radeonfb, rivafb, and the i810fb. If
218 your driver does not take advantage of this feature, choosing Y will
219 just increase the kernel size by about 5K.
221 config FB_TILEBLITTING
222 bool "Enable Tile Blitting Support"
226 This enables tile blitting. Tile blitting is a drawing technique
227 where the screen is divided into rectangular sections (tiles), whereas
228 the standard blitting divides the screen into pixels. Because the
229 default drawing element is a tile, drawing functions will be passed
230 parameters in terms of number of tiles instead of number of pixels.
231 For example, to draw a single character, instead of using bitmaps,
232 an index to an array of bitmaps will be used. To clear or move a
233 rectangular section of a screen, the rectangle will be described in
234 terms of number of tiles in the x- and y-axis.
236 This is particularly important to one driver, matroxfb. If
239 comment "Frame buffer hardware drivers"
243 tristate "Cirrus Logic support"
244 depends on FB && (ZORRO || PCI)
245 select FB_CFB_FILLRECT
246 select FB_CFB_COPYAREA
247 select FB_CFB_IMAGEBLIT
249 This enables support for Cirrus Logic GD542x/543x based boards on
250 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
252 If you have a PCI-based system, this enables support for these
253 chips: GD-543x, GD-544x, GD-5480.
255 Please read the file <file:Documentation/fb/cirrusfb.txt>.
257 Say N unless you have such a graphics board or plan to get one
258 before you next recompile the kernel.
261 tristate "Permedia2 support"
262 depends on FB && ((AMIGA && BROKEN) || PCI)
263 select FB_CFB_FILLRECT
264 select FB_CFB_COPYAREA
265 select FB_CFB_IMAGEBLIT
267 This is the frame buffer device driver for cards based on
268 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
269 The driver was tested on the following cards:
270 Diamond FireGL 1000 PRO AGP
271 ELSA Gloria Synergy PCI
272 Appian Jeronimo PRO (both heads) PCI
273 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
274 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
275 ASK Graphic Blaster Exxtreme AGP
277 To compile this driver as a module, choose M here: the
278 module will be called pm2fb.
280 config FB_PM2_FIFO_DISCONNECT
281 bool "enable FIFO disconnect feature"
282 depends on FB_PM2 && PCI
284 Support the Permedia2 FIFO disconnect feature.
287 tristate "ARM PrimeCell PL110 support"
288 depends on FB && ARM && ARM_AMBA
289 select FB_CFB_FILLRECT
290 select FB_CFB_COPYAREA
291 select FB_CFB_IMAGEBLIT
293 This framebuffer device driver is for the ARM PrimeCell PL110
294 Colour LCD controller. ARM PrimeCells provide the building
295 blocks for System on a Chip devices.
297 If you want to compile this as a module (=code which can be
298 inserted into and removed from the running kernel), say M
299 here and read <file:Documentation/kbuild/modules.txt>. The module
300 will be called amba-clcd.
304 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
306 default FB_ARMCLCD_SHARP_LQ035Q7DB02
308 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
309 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
311 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
312 color QVGA, HRTFT panel. The LogicPD device includes
313 an integrated HRTFT controller IC.
314 The native resolution is 240x320.
316 config FB_ARMCLCD_SHARP_LQ057Q3DC02
317 bool "LogicPD LCD 5.7\" QVGA"
319 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
320 color QVGA, TFT panel. The LogicPD device includes an
321 The native resolution is 320x240.
323 config FB_ARMCLCD_SHARP_LQ64D343
324 bool "LogicPD LCD 6.4\" VGA"
326 This is an implementation of the Sharp LQ64D343, a 6.4"
327 color VGA, TFT panel. The LogicPD device includes an
328 The native resolution is 640x480.
330 config FB_ARMCLCD_SHARP_LQ10D368
331 bool "LogicPD LCD 10.4\" VGA"
333 This is an implementation of the Sharp LQ10D368, a 10.4"
334 color VGA, TFT panel. The LogicPD device includes an
335 The native resolution is 640x480.
338 config FB_ARMCLCD_SHARP_LQ121S1DG41
339 bool "LogicPD LCD 12.1\" SVGA"
341 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
342 color SVGA, TFT panel. The LogicPD device includes an
343 The native resolution is 800x600.
345 This panel requires a clock rate may be an integer fraction
346 of the base LCDCLK frequency. The driver will select the
347 highest frequency available that is lower than the maximum
348 allowed. The panel may flicker if the clock rate is
349 slower than the recommended minimum.
351 config FB_ARMCLCD_AUO_A070VW01_WIDE
352 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
354 This is an implementation of the AU Optronics, a 7.0"
355 WIDE Color. The native resolution is 234x480.
357 config FB_ARMCLCD_HITACHI
358 bool "Hitachi Wide Screen 800x480"
360 This is an implementation of the Hitachi 800x480.
366 bool "Acorn VIDC support"
367 depends on (FB = y) && ARM && ARCH_ACORN
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
372 This is the frame buffer device driver for the Acorn VIDC graphics
373 hardware found in Acorn RISC PCs and other ARM-based machines. If
377 bool "CLPS711X LCD support"
378 depends on (FB = y) && ARM && ARCH_CLPS711X
379 select FB_CFB_FILLRECT
380 select FB_CFB_COPYAREA
381 select FB_CFB_IMAGEBLIT
383 Say Y to enable the Framebuffer driver for the CLPS7111 and
387 bool "SA-1100 LCD support"
388 depends on (FB = y) && ARM && ARCH_SA1100
389 select FB_CFB_FILLRECT
390 select FB_CFB_COPYAREA
391 select FB_CFB_IMAGEBLIT
393 This is a framebuffer device for the SA-1100 LCD Controller.
394 See <http://www.linux-fbdev.org/> for information on framebuffer
397 If you plan to use the LCD display with your SA-1100 system, say
401 tristate "Motorola i.MX LCD support"
402 depends on FB && (ARCH_MX1 || ARCH_MX2)
403 select FB_CFB_FILLRECT
404 select FB_CFB_COPYAREA
405 select FB_CFB_IMAGEBLIT
408 tristate "CyberPro 2000/2010/5000 support"
409 depends on FB && PCI && (BROKEN || !SPARC64)
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
414 This enables support for the Integraphics CyberPro 20x0 and 5000
415 VGA chips used in the Rebel.com Netwinder and other machines.
416 Say Y if you have a NetWinder or a graphics card containing this
417 device, otherwise say N.
421 depends on (FB = y) && APOLLO
423 select FB_CFB_FILLRECT
424 select FB_CFB_IMAGEBLIT
428 depends on (FB = y) && Q40
430 select FB_CFB_FILLRECT
431 select FB_CFB_COPYAREA
432 select FB_CFB_IMAGEBLIT
435 tristate "Amiga native chipset support"
436 depends on FB && AMIGA
438 This is the frame buffer device driver for the builtin graphics
439 chipset found in Amigas.
441 To compile this driver as a module, choose M here: the
442 module will be called amifb.
445 bool "Amiga OCS chipset support"
448 This enables support for the original Agnus and Denise video chips,
449 found in the Amiga 1000 and most A500's and A2000's. If you intend
450 to run Linux on any of these systems, say Y; otherwise say N.
453 bool "Amiga ECS chipset support"
456 This enables support for the Enhanced Chip Set, found in later
457 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
458 you intend to run Linux on any of these systems, say Y; otherwise
462 bool "Amiga AGA chipset support"
465 This enables support for the Advanced Graphics Architecture (also
466 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
467 and CD32. If you intend to run Linux on any of these systems, say Y;
471 bool "Amiga FrameMaster II/Rainbow II support"
472 depends on (FB = y) && ZORRO
473 select FB_CFB_FILLRECT
474 select FB_CFB_COPYAREA
475 select FB_CFB_IMAGEBLIT
477 This is the frame buffer device driver for the Amiga FrameMaster
478 card from BSC (exhibited 1992 but not shipped as a CBM product).
481 tristate "Arc Monochrome LCD board support"
483 select FB_SYS_FILLRECT
484 select FB_SYS_COPYAREA
485 select FB_SYS_IMAGEBLIT
488 This enables support for the Arc Monochrome LCD board. The board
489 is based on the KS-108 lcd controller and is typically a matrix
490 of 2*n chips. This driver was tested with a 128x64 panel. This
491 driver supports it for use with x86 SBCs through a 16 bit GPIO
492 interface (8 bit data, 8 bit control). If you anticipate using
493 this driver, say Y or M; otherwise say N. You must specify the
494 GPIO IO address to be used for setting control and data.
497 bool "Atari native chipset support"
498 depends on (FB = y) && ATARI
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
503 This is the frame buffer device driver for the builtin graphics
504 chipset found in Ataris.
507 bool "Open Firmware frame buffer device support"
508 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
509 select FB_CFB_FILLRECT
510 select FB_CFB_COPYAREA
511 select FB_CFB_IMAGEBLIT
514 Say Y if you want support with Open Firmware for your graphics
518 bool "Apple \"control\" display support"
519 depends on (FB = y) && PPC_PMAC && PPC32
520 select FB_CFB_FILLRECT
521 select FB_CFB_COPYAREA
522 select FB_CFB_IMAGEBLIT
525 This driver supports a frame buffer for the graphics adapter in the
526 Power Macintosh 7300 and others.
529 bool "Apple \"platinum\" display support"
530 depends on (FB = y) && PPC_PMAC && PPC32
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
536 This driver supports a frame buffer for the "platinum" graphics
537 adapter in some Power Macintoshes.
540 bool "Apple \"valkyrie\" display support"
541 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
542 select FB_CFB_FILLRECT
543 select FB_CFB_COPYAREA
544 select FB_CFB_IMAGEBLIT
547 This driver supports a frame buffer for the "valkyrie" graphics
548 adapter in some Power Macintoshes.
551 bool "Chips 65550 display support"
552 depends on (FB = y) && PPC32 && PCI
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
557 This is the frame buffer device driver for the Chips & Technologies
558 65550 graphics chip in PowerBooks.
561 bool "Asiliant (Chips) 69000 display support"
562 depends on (FB = y) && PCI
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
567 This is the frame buffer device driver for the Asiliant 69030 chipset
570 bool "IMS Twin Turbo display support"
571 depends on (FB = y) && PCI
572 select FB_CFB_IMAGEBLIT
573 select FB_MACMODES if PPC
575 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
576 many Macintosh and compatible computers.
579 tristate "VGA 16-color graphics support"
580 depends on FB && (X86 || PPC)
581 select FB_CFB_FILLRECT
582 select FB_CFB_COPYAREA
583 select FB_CFB_IMAGEBLIT
585 select FONT_8x16 if FRAMEBUFFER_CONSOLE
587 This is the frame buffer device driver for VGA 16 color graphic
588 cards. Say Y if you have such a card.
590 To compile this driver as a module, choose M here: the
591 module will be called vga16fb.
593 config FB_BF54X_LQ043
594 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
595 depends on FB && (BF54x) && !BF542
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
602 config FB_BFIN_T350MCQB
603 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
604 depends on FB && BLACKFIN
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
610 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
611 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
612 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
616 tristate "HP STI frame buffer device support"
617 depends on FB && PARISC
618 select FB_CFB_FILLRECT
619 select FB_CFB_COPYAREA
620 select FB_CFB_IMAGEBLIT
625 STI refers to the HP "Standard Text Interface" which is a set of
626 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
627 Enabling this option will implement the linux framebuffer device
628 using calls to the STI BIOS routines for initialisation.
630 If you enable this option, you will get a planar framebuffer device
631 /dev/fb which will work on the most common HP graphic cards of the
632 NGLE family, including the artist chips (in the 7xx and Bxxx series),
633 HCRX, HCRX24, CRX, CRX24 and VisEG series.
635 It is safe to enable this option, so you should probably say "Y".
638 bool "Generic Macintosh display support"
639 depends on (FB = y) && MAC
640 select FB_CFB_FILLRECT
641 select FB_CFB_COPYAREA
642 select FB_CFB_IMAGEBLIT
647 depends on (FB = y) && DIO
648 select FB_CFB_IMAGEBLIT
652 tristate "TGA/SFB+ framebuffer support"
653 depends on FB && (ALPHA || TC)
654 select FB_CFB_FILLRECT
655 select FB_CFB_COPYAREA
656 select FB_CFB_IMAGEBLIT
659 This is the frame buffer device driver for generic TGA and SFB+
660 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
661 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
662 TURBOchannel cards, also known as PMAGD-A, -B and -C.
664 Due to hardware limitations ZLX-E2 and E3 cards are not supported
665 for DECstation 5000/200 systems. Additionally due to firmware
666 limitations these cards may cause troubles with booting DECstation
667 5000/240 and /260 systems, but are fully supported under Linux if
668 you manage to get it going. ;-)
670 Say Y if you have one of those.
673 tristate "Userspace VESA VGA graphics support"
674 depends on FB && CONNECTOR
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
678 select FB_MODE_HELPERS
680 This is the frame buffer driver for generic VBE 2.0 compliant
681 graphic cards. It can also take advantage of VBE 3.0 features,
682 such as refresh rate adjustment.
684 This driver generally provides more features than vesafb but
685 requires a userspace helper application called 'v86d'. See
686 <file:Documentation/fb/uvesafb.txt> for more information.
691 bool "VESA VGA graphics support"
692 depends on (FB = y) && X86
693 select FB_CFB_FILLRECT
694 select FB_CFB_COPYAREA
695 select FB_CFB_IMAGEBLIT
696 select FB_BOOT_VESA_SUPPORT
698 This is the frame buffer device driver for generic VESA 2.0
699 compliant graphic cards. The older VESA 1.2 cards are not supported.
700 You will get a boot time penguin logo at no additional cost. Please
701 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
704 bool "EFI-based Framebuffer Support"
705 depends on (FB = y) && X86 && EFI
706 select FB_CFB_FILLRECT
707 select FB_CFB_COPYAREA
708 select FB_CFB_IMAGEBLIT
710 This is the EFI frame buffer device driver. If the firmware on
711 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
712 using the EFI framebuffer as your console.
715 tristate "N411 Apollo/Hecuba devkit support"
716 depends on FB && X86 && MMU
717 select FB_SYS_FILLRECT
718 select FB_SYS_COPYAREA
719 select FB_SYS_IMAGEBLIT
721 select FB_DEFERRED_IO
724 This enables support for the Apollo display controller in its
725 Hecuba form using the n411 devkit.
728 tristate "Hercules mono graphics support"
730 select FB_CFB_FILLRECT
731 select FB_CFB_COPYAREA
732 select FB_CFB_IMAGEBLIT
734 Say Y here if you have a Hercules mono graphics card.
736 To compile this driver as a module, choose M here: the
737 module will be called hgafb.
739 As this card technology is 15 years old, most people will answer N
743 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
744 depends on FB_HGA && EXPERIMENTAL
746 This will compile the Hercules mono graphics with
747 acceleration functions.
750 tristate "SGI Visual Workstation framebuffer support"
751 depends on FB && X86_VISWS
752 select FB_CFB_FILLRECT
753 select FB_CFB_COPYAREA
754 select FB_CFB_IMAGEBLIT
756 SGI Visual Workstation support for framebuffer graphics.
759 bool "SGI Graphics Backend frame buffer support"
760 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
761 select FB_CFB_FILLRECT
762 select FB_CFB_COPYAREA
763 select FB_CFB_IMAGEBLIT
765 This is the frame buffer device driver for SGI Graphics Backend.
766 This chip is used in SGI O2 and Visual Workstation 320/540.
769 int "Video memory size in MB"
773 This is the amount of memory reserved for the framebuffer,
774 which can be any value between 1MB and 8MB.
777 bool "SBUS and UPA framebuffers"
778 depends on (FB = y) && SPARC
780 Say Y if you want support for SBUS or UPA based frame buffer device.
784 depends on (FB = y) && (SPARC && FB_SBUS)
785 select FB_CFB_FILLRECT
786 select FB_CFB_COPYAREA
787 select FB_CFB_IMAGEBLIT
789 This is the frame buffer device driver for the BWtwo frame buffer.
792 bool "CGthree support"
793 depends on (FB = y) && (SPARC && FB_SBUS)
794 select FB_CFB_FILLRECT
795 select FB_CFB_COPYAREA
796 select FB_CFB_IMAGEBLIT
798 This is the frame buffer device driver for the CGthree frame buffer.
801 bool "CGsix (GX,TurboGX) support"
802 depends on (FB = y) && (SPARC && FB_SBUS)
803 select FB_CFB_COPYAREA
804 select FB_CFB_IMAGEBLIT
806 This is the frame buffer device driver for the CGsix (GX, TurboGX)
810 bool "Creator/Creator3D/Elite3D support"
811 depends on FB_SBUS && SPARC64
812 select FB_CFB_COPYAREA
813 select FB_CFB_IMAGEBLIT
815 This is the frame buffer device driver for the Creator, Creator3D,
816 and Elite3D graphics boards.
819 bool "TCX (SS4/SS5 only) support"
821 select FB_CFB_FILLRECT
822 select FB_CFB_COPYAREA
823 select FB_CFB_IMAGEBLIT
825 This is the frame buffer device driver for the TCX 24/8bit frame
829 bool "CGfourteen (SX) support"
831 select FB_CFB_FILLRECT
832 select FB_CFB_COPYAREA
833 select FB_CFB_IMAGEBLIT
835 This is the frame buffer device driver for the CGfourteen frame
836 buffer on Desktop SPARCsystems with the SX graphics option.
839 bool "P9100 (Sparcbook 3 only) support"
841 select FB_CFB_FILLRECT
842 select FB_CFB_COPYAREA
843 select FB_CFB_IMAGEBLIT
845 This is the frame buffer device driver for the P9100 card
846 supported on Sparcbook 3 machines.
849 bool "Leo (ZX) support"
851 select FB_CFB_FILLRECT
852 select FB_CFB_COPYAREA
853 select FB_CFB_IMAGEBLIT
855 This is the frame buffer device driver for the SBUS-based Sun ZX
856 (leo) frame buffer cards.
859 bool "IGA 168x display support"
860 depends on (FB = y) && SPARC32
861 select FB_CFB_FILLRECT
862 select FB_CFB_COPYAREA
863 select FB_CFB_IMAGEBLIT
865 This is the framebuffer device for the INTERGRAPHICS 1680 and
866 successor frame buffer cards.
869 bool "Sun XVR-500 3DLABS Wildcat support"
870 depends on (FB = y) && PCI && SPARC64
871 select FB_CFB_FILLRECT
872 select FB_CFB_COPYAREA
873 select FB_CFB_IMAGEBLIT
875 This is the framebuffer device for the Sun XVR-500 and similar
876 graphics cards based upon the 3DLABS Wildcat chipset. The driver
877 only works on sparc64 systems where the system firmware has
878 mostly initialized the card already. It is treated as a
879 completely dumb framebuffer device.
882 bool "Sun XVR-2500 3DLABS Wildcat support"
883 depends on (FB = y) && PCI && SPARC64
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 This is the framebuffer device for the Sun XVR-2500 and similar
889 graphics cards based upon the 3DLABS Wildcat chipset. The driver
890 only works on sparc64 systems where the system firmware has
891 mostly initialized the card already. It is treated as a
892 completely dumb framebuffer device.
895 tristate "NEC PowerVR 2 display support"
896 depends on FB && SH_DREAMCAST
897 select FB_CFB_FILLRECT
898 select FB_CFB_COPYAREA
899 select FB_CFB_IMAGEBLIT
901 Say Y here if you have a PowerVR 2 card in your box. If you plan to
902 run linux on your Dreamcast, you will have to say Y here.
903 This driver may or may not work on other PowerVR 2 cards, but is
904 totally untested. Use at your own risk. If unsure, say N.
906 To compile this driver as a module, choose M here: the
907 module will be called pvr2fb.
909 You can pass several parameters to the driver at boot time or at
910 module load time. The parameters look like "video=pvr2:XXX", where
911 the meaning of XXX can be found at the end of the main source file
912 (<file:drivers/video/pvr2fb.c>). Please see the file
913 <file:Documentation/fb/pvr2fb.txt>.
916 bool "Epson 1355 framebuffer support"
917 depends on (FB = y) && ARCH_CEIVA
918 select FB_CFB_FILLRECT
919 select FB_CFB_COPYAREA
920 select FB_CFB_IMAGEBLIT
922 Build in support for the SED1355 Epson Research Embedded RAMDAC
923 LCD/CRT Controller (since redesignated as the S1D13505) as a
924 framebuffer. Product specs at
925 <http://www.erd.epson.com/vdc/html/products.htm>.
928 tristate "Epson S1D13XXX framebuffer support"
930 select FB_CFB_FILLRECT
931 select FB_CFB_COPYAREA
932 select FB_CFB_IMAGEBLIT
934 Support for S1D13XXX framebuffer device family (currently only
935 working with S1D13806). Product specs at
936 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
939 tristate "AT91/AT32 LCD Controller support"
940 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9G10 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 || ARCH_AT91CAP9 || AVR32)
941 select FB_CFB_FILLRECT
942 select FB_CFB_COPYAREA
943 select FB_CFB_IMAGEBLIT
945 This enables support for the AT91/AT32 LCD Controller.
948 bool "Frame Buffer in internal SRAM"
949 depends on FB_ATMEL && ARCH_AT91SAM9261
951 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
952 to let frame buffer in external SDRAM.
955 bool "Use a STN display with AT91/AT32 LCD Controller"
956 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
959 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
960 Controller. Say N if you want to connect a TFT.
965 tristate "nVidia Framebuffer Support"
967 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
968 select FB_MODE_HELPERS
969 select FB_CFB_FILLRECT
970 select FB_CFB_COPYAREA
971 select FB_CFB_IMAGEBLIT
975 This driver supports graphics boards with the nVidia chips, TNT
976 and newer. For very old chipsets, such as the RIVA128, then use
978 Say Y if you have such a graphics board.
980 To compile this driver as a module, choose M here: the
981 module will be called nvidiafb.
984 bool "Enable DDC Support"
988 This enables I2C support for nVidia Chipsets. This is used
989 only for getting EDID information from the attached display
990 allowing for robust video mode handling and switching.
992 Because fbdev-2.6 requires that drivers must be able to
993 independently validate video mode parameters, you should say Y
996 config FB_NVIDIA_DEBUG
997 bool "Lots of debug output"
1001 Say Y here if you want the nVidia driver to output all sorts
1002 of debugging information to provide to the maintainer when
1003 something goes wrong.
1005 config FB_NVIDIA_BACKLIGHT
1006 bool "Support for backlight control"
1007 depends on FB_NVIDIA
1010 Say Y here if you want to control the backlight of your display.
1013 tristate "nVidia Riva support"
1014 depends on FB && PCI
1015 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1016 select FB_MODE_HELPERS
1017 select FB_CFB_FILLRECT
1018 select FB_CFB_COPYAREA
1019 select FB_CFB_IMAGEBLIT
1023 This driver supports graphics boards with the nVidia Riva/Geforce
1025 Say Y if you have such a graphics board.
1027 To compile this driver as a module, choose M here: the
1028 module will be called rivafb.
1031 bool "Enable DDC Support"
1035 This enables I2C support for nVidia Chipsets. This is used
1036 only for getting EDID information from the attached display
1037 allowing for robust video mode handling and switching.
1039 Because fbdev-2.6 requires that drivers must be able to
1040 independently validate video mode parameters, you should say Y
1043 config FB_RIVA_DEBUG
1044 bool "Lots of debug output"
1048 Say Y here if you want the Riva driver to output all sorts
1049 of debugging information to provide to the maintainer when
1050 something goes wrong.
1052 config FB_RIVA_BACKLIGHT
1053 bool "Support for backlight control"
1057 Say Y here if you want to control the backlight of your display.
1060 tristate "Intel 810/815 support (EXPERIMENTAL)"
1061 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1062 select FB_MODE_HELPERS
1063 select FB_CFB_FILLRECT
1064 select FB_CFB_COPYAREA
1065 select FB_CFB_IMAGEBLIT
1068 This driver supports the on-board graphics built in to the Intel 810
1069 and 815 chipsets. Say Y if you have and plan to use such a board.
1071 To compile this driver as a module, choose M here: the
1072 module will be called i810fb.
1074 For more information, please read
1075 <file:Documentation/fb/intel810.txt>
1078 bool "use VESA Generalized Timing Formula"
1081 If you say Y, then the VESA standard, Generalized Timing Formula
1082 or GTF, will be used to calculate the required video timing values
1083 per video mode. Since the GTF allows nondiscrete timings
1084 (nondiscrete being a range of values as opposed to discrete being a
1085 set of values), you'll be able to use any combination of horizontal
1086 and vertical resolutions, and vertical refresh rates without having
1087 to specify your own timing parameters. This is especially useful
1088 to maximize the performance of an aging display, or if you just
1089 have a display with nonstandard dimensions. A VESA compliant
1090 monitor is recommended, but can still work with non-compliant ones.
1091 If you need or want this, then select this option. The timings may
1092 not be compliant with Intel's recommended values. Use at your own
1095 If you say N, the driver will revert to discrete video timings
1096 using a set recommended by Intel in their documentation.
1101 bool "Enable DDC Support"
1102 depends on FB_I810 && FB_I810_GTF
1107 tristate "Intel LE80578 (Vermilion) support"
1108 depends on FB && PCI && X86
1109 select FB_MODE_HELPERS
1110 select FB_CFB_FILLRECT
1111 select FB_CFB_COPYAREA
1112 select FB_CFB_IMAGEBLIT
1114 This driver supports the LE80578 (Vermilion Range) chipset
1116 config FB_CARILLO_RANCH
1117 tristate "Intel Carillo Ranch support"
1118 depends on FB_LE80578 && FB && PCI && X86
1120 This driver supports the LE80578 (Carillo Ranch) board
1123 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1124 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1125 select FB_MODE_HELPERS
1126 select FB_CFB_FILLRECT
1127 select FB_CFB_COPYAREA
1128 select FB_CFB_IMAGEBLIT
1129 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1130 depends on !DRM_I915
1132 This driver supports the on-board graphics built in to the Intel
1133 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1134 Say Y if you have and plan to use such a board.
1136 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1138 To compile this driver as a module, choose M here: the
1139 module will be called intelfb.
1141 For more information, please read <file:Documentation/fb/intelfb.txt>
1143 config FB_INTEL_DEBUG
1144 bool "Intel driver Debug Messages"
1147 Say Y here if you want the Intel driver to output all sorts
1148 of debugging information to provide to the maintainer when
1149 something goes wrong.
1152 bool "DDC/I2C for Intel framebuffer support"
1157 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1160 tristate "Matrox acceleration"
1161 depends on FB && PCI
1162 select FB_CFB_FILLRECT
1163 select FB_CFB_COPYAREA
1164 select FB_CFB_IMAGEBLIT
1165 select FB_TILEBLITTING
1166 select FB_MACMODES if PPC_PMAC
1168 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1169 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1170 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1171 Matrox G400, G450 or G550 card in your box.
1173 To compile this driver as a module, choose M here: the
1174 module will be called matroxfb.
1176 You can pass several parameters to the driver at boot time or at
1177 module load time. The parameters look like "video=matrox:XXX", and
1178 are described in <file:Documentation/fb/matroxfb.txt>.
1180 config FB_MATROX_MILLENIUM
1181 bool "Millennium I/II support"
1182 depends on FB_MATROX
1184 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1185 video card. If you select "Advanced lowlevel driver options" below,
1186 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1187 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1188 also use font widths different from 8.
1190 config FB_MATROX_MYSTIQUE
1191 bool "Mystique support"
1192 depends on FB_MATROX
1194 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1195 video card. If you select "Advanced lowlevel driver options" below,
1196 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1197 packed pixel and 32 bpp packed pixel. You can also use font widths
1201 bool "G100/G200/G400/G450/G550 support"
1202 depends on FB_MATROX
1204 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1205 video card. If you select "Advanced lowlevel driver options", you
1206 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1207 pixel and 32 bpp packed pixel. You can also use font widths
1210 If you need support for G400 secondary head, you must say Y to
1211 "Matrox I2C support" and "G400 second head support" right below.
1212 G450/G550 secondary head and digital output are supported without
1215 The driver starts in monitor mode. You must use the matroxset tool
1216 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1217 swap primary and secondary head outputs, or to change output mode.
1218 Secondary head driver always start in 640x480 resolution and you
1219 must use fbset to change it.
1221 Do not forget that second head supports only 16 and 32 bpp
1222 packed pixels, so it is a good idea to compile them into the kernel
1223 too. You can use only some font widths, as the driver uses generic
1224 painting procedures (the secondary head does not use acceleration
1227 G450/G550 hardware can display TV picture only from secondary CRTC,
1228 and it performs no scaling, so picture must have 525 or 625 lines.
1230 config FB_MATROX_I2C
1231 tristate "Matrox I2C support"
1232 depends on FB_MATROX
1235 This drivers creates I2C buses which are needed for accessing the
1236 DDC (I2C) bus present on all Matroxes, an I2C bus which
1237 interconnects Matrox optional devices, like MGA-TVO on G200 and
1238 G400, and the secondary head DDC bus, present on G400 only.
1240 You can say Y or M here if you want to experiment with monitor
1241 detection code. You must say Y or M here if you want to use either
1242 second head of G400 or MGA-TVO on G200 or G400.
1244 If you compile it as module, it will create a module named
1247 config FB_MATROX_MAVEN
1248 tristate "G400 second head support"
1249 depends on FB_MATROX_G && FB_MATROX_I2C
1251 WARNING !!! This support does not work with G450 !!!
1253 Say Y or M here if you want to use a secondary head (meaning two
1254 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1255 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1256 secondary head output is blanked while you are in X. With XFree
1257 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1258 the fbdev driver on first head and the fbdev driver on second head.
1260 If you compile it as module, two modules are created,
1261 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1262 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1263 also load i2c-matroxfb to get it to run.
1265 The driver starts in monitor mode and you must use the matroxset
1267 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1268 PAL or NTSC or to swap primary and secondary head outputs.
1269 Secondary head driver also always start in 640x480 resolution, you
1270 must use fbset to change it.
1272 Also do not forget that second head supports only 16 and 32 bpp
1273 packed pixels, so it is a good idea to compile them into the kernel
1274 too. You can use only some font widths, as the driver uses generic
1275 painting procedures (the secondary head does not use acceleration
1278 config FB_MATROX_MULTIHEAD
1279 bool "Multihead support"
1280 depends on FB_MATROX
1282 Say Y here if you have more than one (supported) Matrox device in
1283 your computer and you want to use all of them for different monitors
1284 ("multihead"). If you have only one device, you should say N because
1285 the driver compiled with Y is larger and a bit slower, especially on
1288 If you said M to "Matrox unified accelerated driver" and N here, you
1289 will still be able to use several Matrox devices simultaneously:
1290 insert several instances of the module matroxfb into the kernel
1291 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1292 for the different Matrox devices. This method is slightly faster but
1293 uses 40 KB of kernel memory per Matrox card.
1295 There is no need for enabling 'Matrox multihead support' if you have
1296 only one Matrox card in the box.
1299 tristate "ATI Radeon display support"
1300 depends on FB && PCI
1301 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1302 select FB_MODE_HELPERS
1303 select FB_CFB_FILLRECT
1304 select FB_CFB_COPYAREA
1305 select FB_CFB_IMAGEBLIT
1306 select FB_MACMODES if PPC_OF
1308 Choose this option if you want to use an ATI Radeon graphics card as
1309 a framebuffer device. There are both PCI and AGP versions. You
1310 don't need to choose this to run the Radeon in plain VGA mode.
1312 There is a product page at
1313 http://apps.ati.com/ATIcompare/
1315 config FB_RADEON_I2C
1316 bool "DDC/I2C for ATI Radeon support"
1317 depends on FB_RADEON
1321 Say Y here if you want DDC/I2C support for your Radeon board.
1323 config FB_RADEON_BACKLIGHT
1324 bool "Support for backlight control"
1325 depends on FB_RADEON
1328 Say Y here if you want to control the backlight of your display.
1330 config FB_RADEON_DEBUG
1331 bool "Lots of debug output from Radeon driver"
1332 depends on FB_RADEON
1335 Say Y here if you want the Radeon driver to output all sorts
1336 of debugging information to provide to the maintainer when
1337 something goes wrong.
1340 tristate "ATI Rage128 display support"
1341 depends on FB && PCI
1342 select FB_CFB_FILLRECT
1343 select FB_CFB_COPYAREA
1344 select FB_CFB_IMAGEBLIT
1345 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1346 select FB_MACMODES if PPC_PMAC
1348 This driver supports graphics boards with the ATI Rage128 chips.
1349 Say Y if you have such a graphics board and read
1350 <file:Documentation/fb/aty128fb.txt>.
1352 To compile this driver as a module, choose M here: the
1353 module will be called aty128fb.
1355 config FB_ATY128_BACKLIGHT
1356 bool "Support for backlight control"
1357 depends on FB_ATY128
1360 Say Y here if you want to control the backlight of your display.
1363 tristate "ATI Mach64 display support" if PCI || ATARI
1364 depends on FB && !SPARC32
1365 select FB_CFB_FILLRECT
1366 select FB_CFB_COPYAREA
1367 select FB_CFB_IMAGEBLIT
1368 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1369 select FB_MACMODES if PPC
1371 This driver supports graphics boards with the ATI Mach64 chips.
1372 Say Y if you have such a graphics board.
1374 To compile this driver as a module, choose M here: the
1375 module will be called atyfb.
1378 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1379 depends on PCI && FB_ATY
1380 default y if SPARC64 && PCI
1382 Say Y here to support use of ATI's 64-bit Rage boards (or other
1383 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1384 framebuffer device. The ATI product support page for these boards
1385 is at <http://support.ati.com/products/pc/mach64/>.
1387 config FB_ATY_GENERIC_LCD
1388 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1389 depends on FB_ATY_CT
1391 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1392 Rage XC, or Rage XL chipset.
1395 bool "Mach64 GX support" if PCI
1399 Say Y here to support use of the ATI Mach64 Graphics Expression
1400 board (or other boards based on the Mach64 GX chipset) as a
1401 framebuffer device. The ATI product support page for these boards
1403 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1405 config FB_ATY_BACKLIGHT
1406 bool "Support for backlight control"
1410 Say Y here if you want to control the backlight of your display.
1413 tristate "S3 Trio/Virge support"
1414 depends on FB && PCI
1415 select FB_CFB_FILLRECT
1416 select FB_CFB_COPYAREA
1417 select FB_CFB_IMAGEBLIT
1418 select FB_TILEBLITTING
1421 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1423 Driver for graphics boards with S3 Trio / S3 Virge chip.
1426 tristate "S3 Savage support"
1427 depends on FB && PCI && EXPERIMENTAL
1428 select FB_MODE_HELPERS
1429 select FB_CFB_FILLRECT
1430 select FB_CFB_COPYAREA
1431 select FB_CFB_IMAGEBLIT
1434 This driver supports notebooks and computers with S3 Savage PCI/AGP
1437 Say Y if you have such a graphics card.
1439 To compile this driver as a module, choose M here; the module
1440 will be called savagefb.
1442 config FB_SAVAGE_I2C
1443 bool "Enable DDC2 Support"
1444 depends on FB_SAVAGE
1447 This enables I2C support for S3 Savage Chipsets. This is used
1448 only for getting EDID information from the attached display
1449 allowing for robust video mode handling and switching.
1451 Because fbdev-2.6 requires that drivers must be able to
1452 independently validate video mode parameters, you should say Y
1455 config FB_SAVAGE_ACCEL
1456 bool "Enable Console Acceleration"
1457 depends on FB_SAVAGE
1460 This option will compile in console acceleration support. If
1461 the resulting framebuffer console has bothersome glitches, then
1465 tristate "SiS/XGI display support"
1466 depends on FB && PCI
1467 select FB_CFB_FILLRECT
1468 select FB_CFB_COPYAREA
1469 select FB_CFB_IMAGEBLIT
1470 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1472 This is the frame buffer device driver for the SiS 300, 315, 330
1473 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1474 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1476 To compile this driver as a module, choose M here; the module
1477 will be called sisfb.
1480 bool "SiS 300 series support"
1483 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1486 bool "SiS 315/330/340 series and XGI support"
1489 Say Y here to support use of the SiS 315, 330 and 340 series
1490 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1491 as XGI V3XT, V5, V8 and Z7.
1494 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1495 depends on FB && PCI
1496 select FB_CFB_FILLRECT
1497 select FB_CFB_COPYAREA
1498 select FB_CFB_IMAGEBLIT
1499 select FB_SOFT_CURSOR
1503 This is the frame buffer device driver for Graphics chips of VIA
1504 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1505 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1507 Say Y if you have a VIA UniChrome graphics board.
1509 To compile this driver as a module, choose M here: the
1510 module will be called viafb.
1512 tristate "NeoMagic display support"
1513 depends on FB && PCI
1514 select FB_MODE_HELPERS
1515 select FB_CFB_FILLRECT
1516 select FB_CFB_COPYAREA
1517 select FB_CFB_IMAGEBLIT
1520 This driver supports notebooks with NeoMagic PCI chips.
1521 Say Y if you have such a graphics card.
1523 To compile this driver as a module, choose M here: the
1524 module will be called neofb.
1527 tristate "IMG Kyro support"
1528 depends on FB && PCI
1529 select FB_CFB_FILLRECT
1530 select FB_CFB_COPYAREA
1531 select FB_CFB_IMAGEBLIT
1533 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1536 To compile this driver as a module, choose M here: the
1537 module will be called kyrofb.
1540 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1541 depends on FB && PCI
1542 select FB_CFB_IMAGEBLIT
1543 select FB_CFB_FILLRECT
1544 select FB_CFB_COPYAREA
1545 select FB_MODE_HELPERS
1547 This driver supports graphics boards with the 3Dfx Banshee,
1548 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1549 such a graphics board.
1551 To compile this driver as a module, choose M here: the
1552 module will be called tdfxfb.
1554 config FB_3DFX_ACCEL
1555 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1556 depends on FB_3DFX && EXPERIMENTAL
1558 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1559 device driver with acceleration functions.
1562 bool "Enable DDC/I2C support"
1563 depends on FB_3DFX && EXPERIMENTAL
1567 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1570 tristate "3Dfx Voodoo Graphics (sst1) support"
1571 depends on FB && PCI
1572 select FB_CFB_FILLRECT
1573 select FB_CFB_COPYAREA
1574 select FB_CFB_IMAGEBLIT
1576 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1577 Voodoo2 (cvg) based graphics card.
1579 To compile this driver as a module, choose M here: the
1580 module will be called sstfb.
1582 WARNING: Do not use any application that uses the 3D engine
1583 (namely glide) while using this driver.
1584 Please read the <file:Documentation/fb/sstfb.txt> for supported
1585 options and other important info support.
1588 tristate "VIA VT8623 support"
1589 depends on FB && PCI
1590 select FB_CFB_FILLRECT
1591 select FB_CFB_COPYAREA
1592 select FB_CFB_IMAGEBLIT
1593 select FB_TILEBLITTING
1596 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1598 Driver for CastleRock integrated graphics core in the
1599 VIA VT8623 [Apollo CLE266] chipset.
1602 tristate "Trident/CyberXXX/CyberBlade support"
1603 depends on FB && PCI
1604 select FB_CFB_FILLRECT
1605 select FB_CFB_COPYAREA
1606 select FB_CFB_IMAGEBLIT
1608 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1609 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1611 There are also integrated versions of these chips called CyberXXXX,
1612 CyberImage or CyberBlade. These chips are mostly found in laptops
1613 but also on some motherboards including early VIA EPIA motherboards.
1614 For more information, read <file:Documentation/fb/tridentfb.txt>
1616 Say Y if you have such a graphics board.
1618 To compile this driver as a module, choose M here: the
1619 module will be called tridentfb.
1622 tristate "ARK 2000PV support"
1623 depends on FB && PCI
1624 select FB_CFB_FILLRECT
1625 select FB_CFB_COPYAREA
1626 select FB_CFB_IMAGEBLIT
1627 select FB_TILEBLITTING
1630 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1632 Driver for PCI graphics boards with ARK 2000PV chip
1633 and ICS 5342 RAMDAC.
1636 tristate "Permedia3 support (EXPERIMENTAL)"
1637 depends on FB && PCI && EXPERIMENTAL
1638 select FB_CFB_FILLRECT
1639 select FB_CFB_COPYAREA
1640 select FB_CFB_IMAGEBLIT
1642 This is the frame buffer device driver for the 3DLabs Permedia3
1643 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1644 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1645 and maybe other boards.
1648 tristate "Fujitsu carmine frame buffer support"
1649 depends on FB && PCI
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 Fujitsu Carmine chip.
1655 The driver provides two independent frame buffer devices.
1658 depends on FB_CARMINE
1659 prompt "DRAM timing"
1660 default FB_CARMINE_DRAM_EVAL
1662 config FB_CARMINE_DRAM_EVAL
1663 bool "Eval board timings"
1665 Use timings which work on the eval card.
1667 config CARMINE_DRAM_CUSTOM
1668 bool "Custom board timings"
1670 Use custom board timings.
1674 bool "Au1100 LCD Driver"
1675 depends on (FB = y) && MIPS && SOC_AU1100
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1680 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1681 various panels and CRTs by passing in kernel cmd line option
1682 au1100fb:panel=<name>.
1685 bool "Au1200 LCD Driver"
1686 depends on (FB = y) && MIPS && SOC_AU1200
1687 select FB_CFB_FILLRECT
1688 select FB_CFB_COPYAREA
1689 select FB_CFB_IMAGEBLIT
1691 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1692 various panels and CRTs by passing in kernel cmd line option
1693 au1200fb:panel=<name>.
1695 source "drivers/video/geode/Kconfig"
1698 tristate "HD64461 Frame Buffer support"
1699 depends on FB && HD64461
1700 select FB_CFB_FILLRECT
1701 select FB_CFB_COPYAREA
1702 select FB_CFB_IMAGEBLIT
1704 This is the frame buffer device driver for the Hitachi HD64461 LCD
1708 bool "PMAG-AA TURBOchannel framebuffer support"
1709 depends on (FB = y) && TC
1710 select FB_CFB_FILLRECT
1711 select FB_CFB_COPYAREA
1712 select FB_CFB_IMAGEBLIT
1714 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1715 used mainly in the MIPS-based DECstation series.
1718 tristate "PMAG-BA TURBOchannel framebuffer support"
1720 select FB_CFB_FILLRECT
1721 select FB_CFB_COPYAREA
1722 select FB_CFB_IMAGEBLIT
1724 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1725 used mainly in the MIPS-based DECstation series.
1728 tristate "PMAGB-B TURBOchannel framebuffer support"
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1734 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1735 in the MIPS-based DECstation series. The card is currently only
1736 supported in 1280x1024x8 mode.
1739 bool "Maxine (Personal DECstation) onboard framebuffer support"
1740 depends on (FB = y) && MACH_DECSTATION
1741 select FB_CFB_FILLRECT
1742 select FB_CFB_COPYAREA
1743 select FB_CFB_IMAGEBLIT
1745 Support for the onboard framebuffer (1024x768x8) in the Personal
1746 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1750 bool "G364 frame buffer support"
1751 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1752 select FB_CFB_FILLRECT
1753 select FB_CFB_COPYAREA
1754 select FB_CFB_IMAGEBLIT
1756 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1757 Olivetti M700-10 systems.
1760 bool "Motorola 68328 native frame buffer support"
1761 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1762 select FB_CFB_FILLRECT
1763 select FB_CFB_COPYAREA
1764 select FB_CFB_IMAGEBLIT
1766 Say Y here if you want to support the built-in frame buffer of
1767 the Motorola 68328 CPU family.
1770 tristate "PXA168/910 LCD framebuffer support"
1771 depends on FB && (CPU_PXA168 || CPU_PXA910)
1772 select FB_CFB_FILLRECT
1773 select FB_CFB_COPYAREA
1774 select FB_CFB_IMAGEBLIT
1776 Frame buffer driver for the built-in LCD controller in the Marvell
1780 tristate "PXA LCD framebuffer support"
1781 depends on FB && ARCH_PXA
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1786 Frame buffer driver for the built-in LCD controller in the Intel
1789 This driver is also available as a module ( = code which can be
1790 inserted and removed from the running kernel whenever you want). The
1791 module will be called pxafb. If you want to compile it as a module,
1792 say M here and read <file:Documentation/kbuild/modules.txt>.
1796 config FB_PXA_OVERLAY
1797 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1799 depends on FB_PXA && (PXA27x || PXA3xx)
1801 config FB_PXA_SMARTPANEL
1802 bool "PXA Smartpanel LCD support"
1806 config FB_PXA_PARAMETERS
1807 bool "PXA LCD command line parameters"
1811 Enable the use of kernel command line or module parameters
1812 to configure the physical properties of the LCD panel when
1813 using the PXA LCD driver.
1815 This option allows you to override the panel parameters
1816 supplied by the platform in order to support multiple
1817 different models of flatpanel. If you will only be using a
1818 single model of flatpanel then you can safely leave this
1821 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1824 tristate "2700G LCD framebuffer support"
1825 depends on FB && ARCH_PXA
1826 select FB_CFB_FILLRECT
1827 select FB_CFB_COPYAREA
1828 select FB_CFB_IMAGEBLIT
1830 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1834 bool "Enable debugging info via debugfs"
1835 depends on FB_MBX && DEBUG_FS
1838 Enable this if you want debugging information using the debug
1839 filesystem (debugfs)
1844 tristate "Freescale DIU framebuffer support"
1845 depends on FB && FSL_SOC
1846 select FB_CFB_FILLRECT
1847 select FB_CFB_COPYAREA
1848 select FB_CFB_IMAGEBLIT
1849 select PPC_LIB_RHEAP
1851 Framebuffer driver for the Freescale SoC DIU
1854 tristate "W100 frame buffer support"
1855 depends on FB && ARCH_PXA
1856 select FB_CFB_FILLRECT
1857 select FB_CFB_COPYAREA
1858 select FB_CFB_IMAGEBLIT
1860 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1861 It can also drive the w3220 chip found on iPAQ hx4700.
1863 This driver is also available as a module ( = code which can be
1864 inserted and removed from the running kernel whenever you want). The
1865 module will be called w100fb. If you want to compile it as a module,
1866 say M here and read <file:Documentation/kbuild/modules.txt>.
1870 config FB_SH_MOBILE_LCDC
1871 tristate "SuperH Mobile LCDC framebuffer support"
1872 depends on FB && SUPERH && HAVE_CLK
1873 select FB_SYS_FILLRECT
1874 select FB_SYS_COPYAREA
1875 select FB_SYS_IMAGEBLIT
1877 select FB_DEFERRED_IO
1879 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1882 tristate "Toshiba Mobile IO FrameBuffer support"
1883 depends on FB && MFD_CORE
1884 select FB_CFB_FILLRECT
1885 select FB_CFB_COPYAREA
1886 select FB_CFB_IMAGEBLIT
1888 Frame buffer driver for the Toshiba Mobile IO integrated as found
1889 on the Sharp SL-6000 series
1891 This driver is also available as a module ( = code which can be
1892 inserted and removed from the running kernel whenever you want). The
1893 module will be called tmiofb. If you want to compile it as a module,
1894 say M here and read <file:Documentation/kbuild/modules.txt>.
1898 config FB_TMIO_ACCELL
1899 bool "tmiofb acceleration"
1904 tristate "Samsung S3C framebuffer support"
1905 depends on FB && ARCH_S3C64XX
1906 select FB_CFB_FILLRECT
1907 select FB_CFB_COPYAREA
1908 select FB_CFB_IMAGEBLIT
1910 Frame buffer driver for the built-in FB controller in the Samsung
1911 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1912 and the S3C64XX series such as the S3C6400 and S3C6410.
1914 These chips all have the same basic framebuffer design with the
1915 actual capabilities depending on the chip. For instance the S3C6400
1916 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1917 currently only have two.
1919 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1921 config FB_S3C_DEBUG_REGWRITE
1922 bool "Debug register writes"
1925 Show all register writes via printk(KERN_DEBUG)
1928 tristate "S3C2410 LCD framebuffer support"
1929 depends on FB && ARCH_S3C2410
1930 select FB_CFB_FILLRECT
1931 select FB_CFB_COPYAREA
1932 select FB_CFB_IMAGEBLIT
1934 Frame buffer driver for the built-in LCD controller in the Samsung
1937 This driver is also available as a module ( = code which can be
1938 inserted and removed from the running kernel whenever you want). The
1939 module will be called s3c2410fb. If you want to compile it as a module,
1940 say M here and read <file:Documentation/kbuild/modules.txt>.
1943 config FB_S3C2410_DEBUG
1944 bool "S3C2410 lcd debug messages"
1945 depends on FB_S3C2410
1947 Turn on debugging messages. Note that you can set/unset at run time
1951 tristate "Silicon Motion SM501 framebuffer support"
1952 depends on FB && MFD_SM501
1953 select FB_CFB_FILLRECT
1954 select FB_CFB_COPYAREA
1955 select FB_CFB_IMAGEBLIT
1957 Frame buffer driver for the CRT and LCD controllers in the Silicon
1960 This driver is also available as a module ( = code which can be
1961 inserted and removed from the running kernel whenever you want). The
1962 module will be called sm501fb. If you want to compile it as a module,
1963 say M here and read <file:Documentation/kbuild/modules.txt>.
1968 config FB_PNX4008_DUM
1969 tristate "Display Update Module support on Philips PNX4008 board"
1970 depends on FB && ARCH_PNX4008
1972 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1974 config FB_PNX4008_DUM_RGB
1975 tristate "RGB Framebuffer support on Philips PNX4008 board"
1976 depends on FB_PNX4008_DUM
1977 select FB_CFB_FILLRECT
1978 select FB_CFB_COPYAREA
1979 select FB_CFB_IMAGEBLIT
1981 Say Y here to enable support for PNX4008 RGB Framebuffer
1983 config FB_IBM_GXT4500
1984 tristate "Framebuffer support for IBM GXT4500P adaptor"
1985 depends on FB && PPC
1986 select FB_CFB_FILLRECT
1987 select FB_CFB_COPYAREA
1988 select FB_CFB_IMAGEBLIT
1990 Say Y here to enable support for the IBM GXT4500P display
1991 adaptor, found on some IBM System P (pSeries) machines.
1994 tristate "PS3 GPU framebuffer driver"
1995 depends on FB && PS3_PS3AV
1996 select FB_SYS_FILLRECT
1997 select FB_SYS_COPYAREA
1998 select FB_SYS_IMAGEBLIT
2000 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2002 Include support for the virtual frame buffer in the PS3 platform.
2004 config FB_PS3_DEFAULT_SIZE_M
2005 int "PS3 default frame buffer size (in MiB)"
2009 This is the default size (in MiB) of the virtual frame buffer in
2011 The default value can be overridden on the kernel command line
2012 using the "ps3fb" option (e.g. "ps3fb=9M");
2015 tristate "Xilinx frame buffer support"
2016 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2017 select FB_CFB_FILLRECT
2018 select FB_CFB_COPYAREA
2019 select FB_CFB_IMAGEBLIT
2021 Include support for the Xilinx ML300/ML403 reference design
2022 framebuffer. ML300 carries a 640*480 LCD display on the board,
2023 ML403 uses a standard DB15 VGA connector.
2026 tristate "Cobalt server LCD frame buffer support"
2027 depends on FB && MIPS_COBALT
2030 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2031 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2032 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2033 select FB_CFB_FILLRECT
2034 select FB_CFB_COPYAREA
2035 select FB_CFB_IMAGEBLIT
2037 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2038 (D)STN/TFT LCD Controller.
2039 Supports display resolutions up to 1024x1024 pixel, grayscale and
2040 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2041 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2042 panels <= 320 pixel horizontal resolution.
2045 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2047 select FB_SYS_FILLRECT
2048 select FB_SYS_COPYAREA
2049 select FB_SYS_IMAGEBLIT
2052 This is a `virtual' frame buffer device. It operates on a chunk of
2053 unswappable kernel memory instead of on the memory of a graphics
2054 board. This means you cannot see any output sent to this frame
2055 buffer device, while it does consume precious memory. The main use
2056 of this frame buffer device is testing and debugging the frame
2057 buffer subsystem. Do NOT enable it for normal systems! To protect
2058 the innocent, it has to be enabled explicitly at boot time using the
2059 kernel option `video=vfb:'.
2061 To compile this driver as a module, choose M here: the
2062 module will be called vfb. In order to load it, you must use
2063 the vfb_enable=1 option.
2067 config XEN_FBDEV_FRONTEND
2068 tristate "Xen virtual frame buffer support"
2069 depends on FB && XEN
2070 select FB_SYS_FILLRECT
2071 select FB_SYS_COPYAREA
2072 select FB_SYS_IMAGEBLIT
2074 select FB_DEFERRED_IO
2077 This driver implements the front-end of the Xen virtual
2078 frame buffer driver. It communicates with a back-end
2082 tristate "E-Ink Metronome/8track controller support"
2084 select FB_SYS_FILLRECT
2085 select FB_SYS_COPYAREA
2086 select FB_SYS_IMAGEBLIT
2088 select FB_DEFERRED_IO
2090 This driver implements support for the E-Ink Metronome
2091 controller. The pre-release name for this device was 8track
2092 and could also have been called by some vendors as PVI-nnnn.
2095 tristate "Fujitsu MB862xx GDC support"
2097 select FB_CFB_FILLRECT
2098 select FB_CFB_COPYAREA
2099 select FB_CFB_IMAGEBLIT
2101 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2103 config FB_MB862XX_PCI_GDC
2104 bool "Carmine/Coral-P(A) GDC"
2105 depends on PCI && FB_MB862XX
2107 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2108 PCI graphics controller devices.
2110 config FB_MB862XX_LIME
2112 depends on FB_MB862XX
2113 depends on OF && !FB_MB862XX_PCI_GDC
2115 select FB_FOREIGN_ENDIAN
2116 select FB_LITTLE_ENDIAN
2118 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2120 config FB_PRE_INIT_FB
2121 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2122 depends on FB_MB862XX_LIME
2124 Select this option if display contents should be inherited as set by
2128 tristate "MX3 Framebuffer support"
2129 depends on FB && MX3_IPU
2130 select FB_CFB_FILLRECT
2131 select FB_CFB_COPYAREA
2132 select FB_CFB_IMAGEBLIT
2135 This is a framebuffer device for the i.MX31 LCD Controller. So
2136 far only synchronous displays are supported. If you plan to use
2137 an LCD display with your i.MX31 system, say Y here.
2139 config FB_BROADSHEET
2140 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2142 select FB_SYS_FILLRECT
2143 select FB_SYS_COPYAREA
2144 select FB_SYS_IMAGEBLIT
2146 select FB_DEFERRED_IO
2148 This driver implements support for the E-Ink Broadsheet
2149 controller. The release name for this device was Epson S1D13521
2150 and could also have been called by other names when coupled with
2153 source "drivers/video/omap/Kconfig"
2155 source "drivers/video/backlight/Kconfig"
2156 source "drivers/video/display/Kconfig"
2159 source "drivers/video/console/Kconfig"
2162 if FB || SGI_NEWPORT_CONSOLE
2163 source "drivers/video/logo/Kconfig"