5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/char/drm/Kconfig"
16 config VIDEO_OUTPUT_CONTROL
17 tristate "Lowlevel video output switch controls"
19 This framework adds support for low-level control of the video
23 tristate "Support for frame buffer devices"
25 The frame buffer device provides an abstraction for the graphics
26 hardware. It represents the frame buffer of some video hardware and
27 allows application software to access the graphics hardware through
28 a well-defined interface, so the software doesn't need to know
29 anything about the low-level (hardware register) stuff.
31 Frame buffer devices work identically across the different
32 architectures supported by Linux and make the implementation of
33 application programs easier and more portable; at this point, an X
34 server exists which uses the frame buffer device exclusively.
35 On several non-X86 architectures, the frame buffer device is the
36 only way to use the graphics hardware.
38 The device is accessed through special device nodes, usually located
39 in the /dev directory, i.e. /dev/fb*.
41 You need an utility program called fbset to make full use of frame
42 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
43 and the Framebuffer-HOWTO at
44 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
47 Say Y here and to the driver for your graphics board below if you
48 are compiling a kernel for a non-x86 architecture.
50 If you are compiling for the x86 architecture, you can say Y if you
51 want to play with it, but it is not essential. Please note that
52 running graphical applications that directly touch the hardware
53 (e.g. an accelerated X server) and that are not frame buffer
54 device-aware may cause unexpected results. If unsure, say N.
57 bool "Enable firmware EDID"
61 This enables access to the EDID transferred from the firmware.
62 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
63 transfers do not work for your driver and if you are using
64 nvidiafb, i810fb or savagefb.
66 In general, choosing Y for this option is safe. If you
67 experience extremely long delays while booting before you get
68 something on your display, try setting this to N. Matrox cards in
69 combination with certain motherboards and monitors are known to
70 suffer from this problem.
79 config FB_CFB_FILLRECT
84 Include the cfb_fillrect function for generic software rectangle
85 filling. This is used by drivers that don't provide their own
86 (accelerated) version.
88 config FB_CFB_COPYAREA
93 Include the cfb_copyarea function for generic software area copying.
94 This is used by drivers that don't provide their own (accelerated)
97 config FB_CFB_IMAGEBLIT
102 Include the cfb_imageblit function for generic software image
103 blitting. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_REV_PIXELS_IN_BYTE
111 Allow generic frame-buffer functions to work on displays with 1, 2
112 and 4 bits per pixel depths which has opposite order of pixels in
113 byte order to bytes in long order.
115 config FB_SYS_FILLRECT
120 Include the sys_fillrect function for generic software rectangle
121 filling. This is used by drivers that don't provide their own
122 (accelerated) version and the framebuffer is in system RAM.
124 config FB_SYS_COPYAREA
129 Include the sys_copyarea function for generic software area copying.
130 This is used by drivers that don't provide their own (accelerated)
131 version and the framebuffer is in system RAM.
133 config FB_SYS_IMAGEBLIT
138 Include the sys_imageblit function for generic software image
139 blitting. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 menuconfig FB_FOREIGN_ENDIAN
143 bool "Framebuffer foreign endianness support"
146 This menu will let you enable support for the framebuffers with
147 non-native endianness (e.g. Little-Endian framebuffer on a
148 Big-Endian machine). Most probably you don't have such hardware,
149 so it's safe to say "n" here.
152 prompt "Choice endianness support"
153 depends on FB_FOREIGN_ENDIAN
155 config FB_BOTH_ENDIAN
156 bool "Support for Big- and Little-Endian framebuffers"
159 bool "Support for Big-Endian framebuffers only"
161 config FB_LITTLE_ENDIAN
162 bool "Support for Little-Endian framebuffers only"
171 config FB_DEFERRED_IO
179 depends on FB_DEFERRED_IO
184 depends on FB_DEFERRED_IO
191 Common utility functions useful to fbdev drivers of VGA-based
202 select BACKLIGHT_LCD_SUPPORT
203 select BACKLIGHT_CLASS_DEVICE
206 config FB_MODE_HELPERS
207 bool "Enable Video Mode Handling Helpers"
211 This enables functions for handling video modes using the
212 Generalized Timing Formula and the EDID parser. A few drivers rely
213 on this feature such as the radeonfb, rivafb, and the i810fb. If
214 your driver does not take advantage of this feature, choosing Y will
215 just increase the kernel size by about 5K.
217 config FB_TILEBLITTING
218 bool "Enable Tile Blitting Support"
222 This enables tile blitting. Tile blitting is a drawing technique
223 where the screen is divided into rectangular sections (tiles), whereas
224 the standard blitting divides the screen into pixels. Because the
225 default drawing element is a tile, drawing functions will be passed
226 parameters in terms of number of tiles instead of number of pixels.
227 For example, to draw a single character, instead of using bitmaps,
228 an index to an array of bitmaps will be used. To clear or move a
229 rectangular section of a screen, the rectangle will be described in
230 terms of number of tiles in the x- and y-axis.
232 This is particularly important to one driver, matroxfb. If
235 comment "Frame buffer hardware drivers"
239 tristate "Cirrus Logic support"
240 depends on FB && (ZORRO || PCI)
241 select FB_CFB_FILLRECT
242 select FB_CFB_COPYAREA
243 select FB_CFB_IMAGEBLIT
245 This enables support for Cirrus Logic GD542x/543x based boards on
246 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
248 If you have a PCI-based system, this enables support for these
249 chips: GD-543x, GD-544x, GD-5480.
251 Please read the file <file:Documentation/fb/cirrusfb.txt>.
253 Say N unless you have such a graphics board or plan to get one
254 before you next recompile the kernel.
257 tristate "Permedia2 support"
258 depends on FB && ((AMIGA && BROKEN) || PCI)
259 select FB_CFB_FILLRECT
260 select FB_CFB_COPYAREA
261 select FB_CFB_IMAGEBLIT
263 This is the frame buffer device driver for the Permedia2 AGP frame
264 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
266 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
268 config FB_PM2_FIFO_DISCONNECT
269 bool "enable FIFO disconnect feature"
270 depends on FB_PM2 && PCI
272 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
275 tristate "ARM PrimeCell PL110 support"
276 depends on FB && ARM && ARM_AMBA
277 select FB_CFB_FILLRECT
278 select FB_CFB_COPYAREA
279 select FB_CFB_IMAGEBLIT
281 This framebuffer device driver is for the ARM PrimeCell PL110
282 Colour LCD controller. ARM PrimeCells provide the building
283 blocks for System on a Chip devices.
285 If you want to compile this as a module (=code which can be
286 inserted into and removed from the running kernel), say M
287 here and read <file:Documentation/kbuild/modules.txt>. The module
288 will be called amba-clcd.
292 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
294 default FB_ARMCLCD_SHARP_LQ035Q7DB02
296 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
297 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
299 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
300 color QVGA, HRTFT panel. The LogicPD device includes
301 an integrated HRTFT controller IC.
302 The native resolution is 240x320.
304 config FB_ARMCLCD_SHARP_LQ057Q3DC02
305 bool "LogicPD LCD 5.7\" QVGA"
307 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
308 color QVGA, TFT panel. The LogicPD device includes an
309 The native resolution is 320x240.
311 config FB_ARMCLCD_SHARP_LQ64D343
312 bool "LogicPD LCD 6.4\" VGA"
314 This is an implementation of the Sharp LQ64D343, a 6.4"
315 color VGA, TFT panel. The LogicPD device includes an
316 The native resolution is 640x480.
318 config FB_ARMCLCD_SHARP_LQ10D368
319 bool "LogicPD LCD 10.4\" VGA"
321 This is an implementation of the Sharp LQ10D368, a 10.4"
322 color VGA, TFT panel. The LogicPD device includes an
323 The native resolution is 640x480.
326 config FB_ARMCLCD_SHARP_LQ121S1DG41
327 bool "LogicPD LCD 12.1\" SVGA"
329 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
330 color SVGA, TFT panel. The LogicPD device includes an
331 The native resolution is 800x600.
333 This panel requires a clock rate may be an integer fraction
334 of the base LCDCLK frequency. The driver will select the
335 highest frequency available that is lower than the maximum
336 allowed. The panel may flicker if the clock rate is
337 slower than the recommended minimum.
339 config FB_ARMCLCD_AUO_A070VW01_WIDE
340 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
342 This is an implementation of the AU Optronics, a 7.0"
343 WIDE Color. The native resolution is 234x480.
345 config FB_ARMCLCD_HITACHI
346 bool "Hitachi Wide Screen 800x480"
348 This is an implementation of the Hitachi 800x480.
354 bool "Acorn VIDC support"
355 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
356 select FB_CFB_FILLRECT
357 select FB_CFB_COPYAREA
358 select FB_CFB_IMAGEBLIT
360 This is the frame buffer device driver for the Acorn VIDC graphics
361 hardware found in Acorn RISC PCs and other ARM-based machines. If
365 bool "CLPS711X LCD support"
366 depends on (FB = y) && ARM && ARCH_CLPS711X
367 select FB_CFB_FILLRECT
368 select FB_CFB_COPYAREA
369 select FB_CFB_IMAGEBLIT
371 Say Y to enable the Framebuffer driver for the CLPS7111 and
375 bool "SA-1100 LCD support"
376 depends on (FB = y) && ARM && ARCH_SA1100
377 select FB_CFB_FILLRECT
378 select FB_CFB_COPYAREA
379 select FB_CFB_IMAGEBLIT
381 This is a framebuffer device for the SA-1100 LCD Controller.
382 See <http://www.linux-fbdev.org/> for information on framebuffer
385 If you plan to use the LCD display with your SA-1100 system, say
389 tristate "Motorola i.MX LCD support"
390 depends on FB && ARM && ARCH_IMX
391 select FB_CFB_FILLRECT
392 select FB_CFB_COPYAREA
393 select FB_CFB_IMAGEBLIT
396 tristate "CyberPro 2000/2010/5000 support"
397 depends on FB && PCI && (BROKEN || !SPARC64)
398 select FB_CFB_FILLRECT
399 select FB_CFB_COPYAREA
400 select FB_CFB_IMAGEBLIT
402 This enables support for the Integraphics CyberPro 20x0 and 5000
403 VGA chips used in the Rebel.com Netwinder and other machines.
404 Say Y if you have a NetWinder or a graphics card containing this
405 device, otherwise say N.
409 depends on (FB = y) && APOLLO
411 select FB_CFB_FILLRECT
412 select FB_CFB_IMAGEBLIT
416 depends on (FB = y) && Q40
418 select FB_CFB_FILLRECT
419 select FB_CFB_COPYAREA
420 select FB_CFB_IMAGEBLIT
423 tristate "Amiga native chipset support"
424 depends on FB && AMIGA
426 This is the frame buffer device driver for the builtin graphics
427 chipset found in Amigas.
429 To compile this driver as a module, choose M here: the
430 module will be called amifb.
433 bool "Amiga OCS chipset support"
436 This enables support for the original Agnus and Denise video chips,
437 found in the Amiga 1000 and most A500's and A2000's. If you intend
438 to run Linux on any of these systems, say Y; otherwise say N.
441 bool "Amiga ECS chipset support"
444 This enables support for the Enhanced Chip Set, found in later
445 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
446 you intend to run Linux on any of these systems, say Y; otherwise
450 bool "Amiga AGA chipset support"
453 This enables support for the Advanced Graphics Architecture (also
454 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
455 and CD32. If you intend to run Linux on any of these systems, say Y;
459 bool "Amiga FrameMaster II/Rainbow II support"
460 depends on (FB = y) && ZORRO
461 select FB_CFB_FILLRECT
462 select FB_CFB_COPYAREA
463 select FB_CFB_IMAGEBLIT
465 This is the frame buffer device driver for the Amiga FrameMaster
466 card from BSC (exhibited 1992 but not shipped as a CBM product).
469 tristate "Arc Monochrome LCD board support"
471 select FB_SYS_FILLRECT
472 select FB_SYS_COPYAREA
473 select FB_SYS_IMAGEBLIT
476 This enables support for the Arc Monochrome LCD board. The board
477 is based on the KS-108 lcd controller and is typically a matrix
478 of 2*n chips. This driver was tested with a 128x64 panel. This
479 driver supports it for use with x86 SBCs through a 16 bit GPIO
480 interface (8 bit data, 8 bit control). If you anticipate using
481 this driver, say Y or M; otherwise say N. You must specify the
482 GPIO IO address to be used for setting control and data.
485 bool "Atari native chipset support"
486 depends on (FB = y) && ATARI
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
491 This is the frame buffer device driver for the builtin graphics
492 chipset found in Ataris.
495 bool "Open Firmware frame buffer device support"
496 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
502 Say Y if you want support with Open Firmware for your graphics
506 bool "Apple \"control\" display support"
507 depends on (FB = y) && PPC_PMAC && PPC32
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
513 This driver supports a frame buffer for the graphics adapter in the
514 Power Macintosh 7300 and others.
517 bool "Apple \"platinum\" display support"
518 depends on (FB = y) && PPC_PMAC && PPC32
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
524 This driver supports a frame buffer for the "platinum" graphics
525 adapter in some Power Macintoshes.
528 bool "Apple \"valkyrie\" display support"
529 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
530 select FB_CFB_FILLRECT
531 select FB_CFB_COPYAREA
532 select FB_CFB_IMAGEBLIT
535 This driver supports a frame buffer for the "valkyrie" graphics
536 adapter in some Power Macintoshes.
539 bool "Chips 65550 display support"
540 depends on (FB = y) && PPC32 && PCI
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
545 This is the frame buffer device driver for the Chips & Technologies
546 65550 graphics chip in PowerBooks.
549 bool "Asiliant (Chips) 69000 display support"
550 depends on (FB = y) && PCI
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
555 This is the frame buffer device driver for the Asiliant 69030 chipset
558 bool "IMS Twin Turbo display support"
559 depends on (FB = y) && PCI
560 select FB_CFB_IMAGEBLIT
561 select FB_MACMODES if PPC
563 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
564 many Macintosh and compatible computers.
567 tristate "VGA 16-color graphics support"
568 depends on FB && (X86 || PPC)
569 select FB_CFB_FILLRECT
570 select FB_CFB_COPYAREA
571 select FB_CFB_IMAGEBLIT
573 select FONT_8x16 if FRAMEBUFFER_CONSOLE
575 This is the frame buffer device driver for VGA 16 color graphic
576 cards. Say Y if you have such a card.
578 To compile this driver as a module, choose M here: the
579 module will be called vga16fb.
581 config FB_BF54X_LQ043
582 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
583 depends on FB && (BF54x) && !BF542
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
588 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
590 config FB_BFIN_T350MCQB
591 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
592 depends on FB && BLACKFIN
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
598 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
599 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
600 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
604 tristate "HP STI frame buffer device support"
605 depends on FB && PARISC
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
611 STI refers to the HP "Standard Text Interface" which is a set of
612 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
613 Enabling this option will implement the linux framebuffer device
614 using calls to the STI BIOS routines for initialisation.
616 If you enable this option, you will get a planar framebuffer device
617 /dev/fb which will work on the most common HP graphic cards of the
618 NGLE family, including the artist chips (in the 7xx and Bxxx series),
619 HCRX, HCRX24, CRX, CRX24 and VisEG series.
621 It is safe to enable this option, so you should probably say "Y".
624 bool "Generic Macintosh display support"
625 depends on (FB = y) && MAC
626 select FB_CFB_FILLRECT
627 select FB_CFB_COPYAREA
628 select FB_CFB_IMAGEBLIT
631 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
634 depends on (FB = y) && HP300
635 select FB_CFB_FILLRECT
636 select FB_CFB_IMAGEBLIT
640 tristate "TGA/SFB+ framebuffer support"
641 depends on FB && (ALPHA || TC)
642 select FB_CFB_FILLRECT
643 select FB_CFB_COPYAREA
644 select FB_CFB_IMAGEBLIT
647 This is the frame buffer device driver for generic TGA and SFB+
648 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
649 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
650 TURBOchannel cards, also known as PMAGD-A, -B and -C.
652 Due to hardware limitations ZLX-E2 and E3 cards are not supported
653 for DECstation 5000/200 systems. Additionally due to firmware
654 limitations these cards may cause troubles with booting DECstation
655 5000/240 and /260 systems, but are fully supported under Linux if
656 you manage to get it going. ;-)
658 Say Y if you have one of those.
661 tristate "Userspace VESA VGA graphics support"
662 depends on FB && CONNECTOR
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
666 select FB_MODE_HELPERS
668 This is the frame buffer driver for generic VBE 2.0 compliant
669 graphic cards. It can also take advantage of VBE 3.0 features,
670 such as refresh rate adjustment.
672 This driver generally provides more features than vesafb but
673 requires a userspace helper application called 'v86d'. See
674 <file:Documentation/fb/uvesafb.txt> for more information.
679 bool "VESA VGA graphics support"
680 depends on (FB = y) && X86
681 select FB_CFB_FILLRECT
682 select FB_CFB_COPYAREA
683 select FB_CFB_IMAGEBLIT
686 This is the frame buffer device driver for generic VESA 2.0
687 compliant graphic cards. The older VESA 1.2 cards are not supported.
688 You will get a boot time penguin logo at no additional cost. Please
689 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
692 bool "EFI-based Framebuffer Support"
693 depends on (FB = y) && X86
694 select FB_CFB_FILLRECT
695 select FB_CFB_COPYAREA
696 select FB_CFB_IMAGEBLIT
698 This is the EFI frame buffer device driver. If the firmware on
699 your platform is UEFI2.0, select Y to add support for
700 Graphics Output Protocol for early console messages to appear.
703 bool "Intel-based Macintosh Framebuffer Support"
704 depends on (FB = y) && X86 && EFI
705 select FB_CFB_FILLRECT
706 select FB_CFB_COPYAREA
707 select FB_CFB_IMAGEBLIT
709 This is the frame buffer device driver for the Intel-based Macintosh
712 tristate "N411 Apollo/Hecuba devkit support"
713 depends on FB && X86 && MMU
714 select FB_SYS_FILLRECT
715 select FB_SYS_COPYAREA
716 select FB_SYS_IMAGEBLIT
718 select FB_DEFERRED_IO
721 This enables support for the Apollo display controller in its
722 Hecuba form using the n411 devkit.
725 tristate "Hercules mono graphics support"
727 select FB_CFB_FILLRECT
728 select FB_CFB_COPYAREA
729 select FB_CFB_IMAGEBLIT
731 Say Y here if you have a Hercules mono graphics card.
733 To compile this driver as a module, choose M here: the
734 module will be called hgafb.
736 As this card technology is 15 years old, most people will answer N
740 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
741 depends on FB_HGA && EXPERIMENTAL
743 This will compile the Hercules mono graphics with
744 acceleration functions.
747 tristate "SGI Visual Workstation framebuffer support"
748 depends on FB && X86_VISWS
749 select FB_CFB_FILLRECT
750 select FB_CFB_COPYAREA
751 select FB_CFB_IMAGEBLIT
753 SGI Visual Workstation support for framebuffer graphics.
756 bool "SGI Graphics Backend frame buffer support"
757 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
758 select FB_CFB_FILLRECT
759 select FB_CFB_COPYAREA
760 select FB_CFB_IMAGEBLIT
762 This is the frame buffer device driver for SGI Graphics Backend.
763 This chip is used in SGI O2 and Visual Workstation 320/540.
766 int "Video memory size in MB"
770 This is the amount of memory reserved for the framebuffer,
771 which can be any value between 1MB and 8MB.
774 bool "SBUS and UPA framebuffers"
775 depends on (FB = y) && SPARC
777 Say Y if you want support for SBUS or UPA based frame buffer device.
781 depends on (FB = y) && (SPARC && FB_SBUS)
782 select FB_CFB_FILLRECT
783 select FB_CFB_COPYAREA
784 select FB_CFB_IMAGEBLIT
786 This is the frame buffer device driver for the BWtwo frame buffer.
789 bool "CGthree support"
790 depends on (FB = y) && (SPARC && FB_SBUS)
791 select FB_CFB_FILLRECT
792 select FB_CFB_COPYAREA
793 select FB_CFB_IMAGEBLIT
795 This is the frame buffer device driver for the CGthree frame buffer.
798 bool "CGsix (GX,TurboGX) support"
799 depends on (FB = y) && (SPARC && FB_SBUS)
800 select FB_CFB_COPYAREA
801 select FB_CFB_IMAGEBLIT
803 This is the frame buffer device driver for the CGsix (GX, TurboGX)
807 bool "Creator/Creator3D/Elite3D support"
808 depends on FB_SBUS && SPARC64
809 select FB_CFB_COPYAREA
810 select FB_CFB_IMAGEBLIT
812 This is the frame buffer device driver for the Creator, Creator3D,
813 and Elite3D graphics boards.
816 bool "TCX (SS4/SS5 only) support"
818 select FB_CFB_FILLRECT
819 select FB_CFB_COPYAREA
820 select FB_CFB_IMAGEBLIT
822 This is the frame buffer device driver for the TCX 24/8bit frame
826 bool "CGfourteen (SX) support"
828 select FB_CFB_FILLRECT
829 select FB_CFB_COPYAREA
830 select FB_CFB_IMAGEBLIT
832 This is the frame buffer device driver for the CGfourteen frame
833 buffer on Desktop SPARCsystems with the SX graphics option.
836 bool "P9100 (Sparcbook 3 only) support"
838 select FB_CFB_FILLRECT
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 This is the frame buffer device driver for the P9100 card
843 supported on Sparcbook 3 machines.
846 bool "Leo (ZX) support"
848 select FB_CFB_FILLRECT
849 select FB_CFB_COPYAREA
850 select FB_CFB_IMAGEBLIT
852 This is the frame buffer device driver for the SBUS-based Sun ZX
853 (leo) frame buffer cards.
856 bool "IGA 168x display support"
857 depends on (FB = y) && SPARC32
858 select FB_CFB_FILLRECT
859 select FB_CFB_COPYAREA
860 select FB_CFB_IMAGEBLIT
862 This is the framebuffer device for the INTERGRAPHICS 1680 and
863 successor frame buffer cards.
866 bool "Sun XVR-500 3DLABS Wildcat support"
867 depends on (FB = y) && PCI && SPARC64
868 select FB_CFB_FILLRECT
869 select FB_CFB_COPYAREA
870 select FB_CFB_IMAGEBLIT
872 This is the framebuffer device for the Sun XVR-500 and similar
873 graphics cards based upon the 3DLABS Wildcat chipset. The driver
874 only works on sparc64 systems where the system firmware has
875 mostly initialized the card already. It is treated as a
876 completely dumb framebuffer device.
879 bool "Sun XVR-2500 3DLABS Wildcat support"
880 depends on (FB = y) && PCI && SPARC64
881 select FB_CFB_FILLRECT
882 select FB_CFB_COPYAREA
883 select FB_CFB_IMAGEBLIT
885 This is the framebuffer device for the Sun XVR-2500 and similar
886 graphics cards based upon the 3DLABS Wildcat chipset. The driver
887 only works on sparc64 systems where the system firmware has
888 mostly initialized the card already. It is treated as a
889 completely dumb framebuffer device.
892 tristate "NEC PowerVR 2 display support"
893 depends on FB && SH_DREAMCAST
894 select FB_CFB_FILLRECT
895 select FB_CFB_COPYAREA
896 select FB_CFB_IMAGEBLIT
898 Say Y here if you have a PowerVR 2 card in your box. If you plan to
899 run linux on your Dreamcast, you will have to say Y here.
900 This driver may or may not work on other PowerVR 2 cards, but is
901 totally untested. Use at your own risk. If unsure, say N.
903 To compile this driver as a module, choose M here: the
904 module will be called pvr2fb.
906 You can pass several parameters to the driver at boot time or at
907 module load time. The parameters look like "video=pvr2:XXX", where
908 the meaning of XXX can be found at the end of the main source file
909 (<file:drivers/video/pvr2fb.c>). Please see the file
910 <file:Documentation/fb/pvr2fb.txt>.
913 bool "Epson 1355 framebuffer support"
914 depends on (FB = y) && ARCH_CEIVA
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 Build in support for the SED1355 Epson Research Embedded RAMDAC
920 LCD/CRT Controller (since redesignated as the S1D13505) as a
921 framebuffer. Product specs at
922 <http://www.erd.epson.com/vdc/html/products.htm>.
925 tristate "Epson S1D13XXX framebuffer support"
927 select FB_CFB_FILLRECT
928 select FB_CFB_COPYAREA
929 select FB_CFB_IMAGEBLIT
931 Support for S1D13XXX framebuffer device family (currently only
932 working with S1D13806). Product specs at
933 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
936 tristate "AT91/AT32 LCD Controller support"
937 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
938 select FB_CFB_FILLRECT
939 select FB_CFB_COPYAREA
940 select FB_CFB_IMAGEBLIT
942 This enables support for the AT91/AT32 LCD Controller.
945 bool "Frame Buffer in internal SRAM"
946 depends on FB_ATMEL && ARCH_AT91SAM9261
948 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
949 to let frame buffer in external SDRAM.
952 bool "Use a STN display with AT91/AT32 LCD Controller"
953 depends on FB_ATMEL && MACH_AT91SAM9261EK
956 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
957 Controller. Say N if you want to connect a TFT.
962 tristate "nVidia Framebuffer Support"
964 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
965 select FB_MODE_HELPERS
966 select FB_CFB_FILLRECT
967 select FB_CFB_COPYAREA
968 select FB_CFB_IMAGEBLIT
972 This driver supports graphics boards with the nVidia chips, TNT
973 and newer. For very old chipsets, such as the RIVA128, then use
975 Say Y if you have such a graphics board.
977 To compile this driver as a module, choose M here: the
978 module will be called nvidiafb.
981 bool "Enable DDC Support"
985 This enables I2C support for nVidia Chipsets. This is used
986 only for getting EDID information from the attached display
987 allowing for robust video mode handling and switching.
989 Because fbdev-2.6 requires that drivers must be able to
990 independently validate video mode parameters, you should say Y
993 config FB_NVIDIA_DEBUG
994 bool "Lots of debug output"
998 Say Y here if you want the nVidia driver to output all sorts
999 of debugging information to provide to the maintainer when
1000 something goes wrong.
1002 config FB_NVIDIA_BACKLIGHT
1003 bool "Support for backlight control"
1004 depends on FB_NVIDIA
1007 Say Y here if you want to control the backlight of your display.
1010 tristate "nVidia Riva support"
1011 depends on FB && PCI
1012 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1013 select FB_MODE_HELPERS
1014 select FB_CFB_FILLRECT
1015 select FB_CFB_COPYAREA
1016 select FB_CFB_IMAGEBLIT
1020 This driver supports graphics boards with the nVidia Riva/Geforce
1022 Say Y if you have such a graphics board.
1024 To compile this driver as a module, choose M here: the
1025 module will be called rivafb.
1028 bool "Enable DDC Support"
1032 This enables I2C support for nVidia Chipsets. This is used
1033 only for getting EDID information from the attached display
1034 allowing for robust video mode handling and switching.
1036 Because fbdev-2.6 requires that drivers must be able to
1037 independently validate video mode parameters, you should say Y
1040 config FB_RIVA_DEBUG
1041 bool "Lots of debug output"
1045 Say Y here if you want the Riva driver to output all sorts
1046 of debugging information to provide to the maintainer when
1047 something goes wrong.
1049 config FB_RIVA_BACKLIGHT
1050 bool "Support for backlight control"
1054 Say Y here if you want to control the backlight of your display.
1057 tristate "Intel 810/815 support (EXPERIMENTAL)"
1058 depends on FB && EXPERIMENTAL && PCI && X86_32
1061 select FB_MODE_HELPERS
1062 select FB_CFB_FILLRECT
1063 select FB_CFB_COPYAREA
1064 select FB_CFB_IMAGEBLIT
1067 This driver supports the on-board graphics built in to the Intel 810
1068 and 815 chipsets. Say Y if you have and plan to use such a board.
1070 To compile this driver as a module, choose M here: the
1071 module will be called i810fb.
1073 For more information, please read
1074 <file:Documentation/fb/intel810.txt>
1077 bool "use VESA Generalized Timing Formula"
1080 If you say Y, then the VESA standard, Generalized Timing Formula
1081 or GTF, will be used to calculate the required video timing values
1082 per video mode. Since the GTF allows nondiscrete timings
1083 (nondiscrete being a range of values as opposed to discrete being a
1084 set of values), you'll be able to use any combination of horizontal
1085 and vertical resolutions, and vertical refresh rates without having
1086 to specify your own timing parameters. This is especially useful
1087 to maximize the performance of an aging display, or if you just
1088 have a display with nonstandard dimensions. A VESA compliant
1089 monitor is recommended, but can still work with non-compliant ones.
1090 If you need or want this, then select this option. The timings may
1091 not be compliant with Intel's recommended values. Use at your own
1094 If you say N, the driver will revert to discrete video timings
1095 using a set recommended by Intel in their documentation.
1100 bool "Enable DDC Support"
1101 depends on FB_I810 && FB_I810_GTF
1106 tristate "Intel LE80578 (Vermilion) support"
1107 depends on FB && PCI && X86
1108 select FB_MODE_HELPERS
1109 select FB_CFB_FILLRECT
1110 select FB_CFB_COPYAREA
1111 select FB_CFB_IMAGEBLIT
1113 This driver supports the LE80578 (Vermilion Range) chipset
1115 config FB_CARILLO_RANCH
1116 tristate "Intel Carillo Ranch support"
1117 depends on FB_LE80578 && FB && PCI && X86
1119 This driver supports the LE80578 (Carillo Ranch) board
1122 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1123 depends on FB && EXPERIMENTAL && PCI && X86
1126 select FB_MODE_HELPERS
1127 select FB_CFB_FILLRECT
1128 select FB_CFB_COPYAREA
1129 select FB_CFB_IMAGEBLIT
1131 This driver supports the on-board graphics built in to the Intel
1132 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1133 Say Y if you have and plan to use such a board.
1135 If you say Y here and want DDC/I2C support you must first say Y to
1136 "I2C support" and "I2C bit-banging support" in the character devices
1139 If you say M here then "I2C support" and "I2C bit-banging support"
1140 can be build either as modules or built-in.
1142 To compile this driver as a module, choose M here: the
1143 module will be called intelfb.
1145 For more information, please read <file:Documentation/fb/intelfb.txt>
1147 config FB_INTEL_DEBUG
1148 bool "Intel driver Debug Messages"
1151 Say Y here if you want the Intel driver to output all sorts
1152 of debugging information to provide to the maintainer when
1153 something goes wrong.
1156 bool "DDC/I2C for Intel framebuffer support"
1161 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1164 tristate "Matrox acceleration"
1165 depends on FB && PCI
1166 select FB_CFB_FILLRECT
1167 select FB_CFB_COPYAREA
1168 select FB_CFB_IMAGEBLIT
1169 select FB_TILEBLITTING
1170 select FB_MACMODES if PPC_PMAC
1172 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1173 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1174 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1175 Matrox G400, G450 or G550 card in your box.
1177 To compile this driver as a module, choose M here: the
1178 module will be called matroxfb.
1180 You can pass several parameters to the driver at boot time or at
1181 module load time. The parameters look like "video=matrox:XXX", and
1182 are described in <file:Documentation/fb/matroxfb.txt>.
1184 config FB_MATROX_MILLENIUM
1185 bool "Millennium I/II support"
1186 depends on FB_MATROX
1188 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1189 video card. If you select "Advanced lowlevel driver options" below,
1190 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1191 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1192 also use font widths different from 8.
1194 config FB_MATROX_MYSTIQUE
1195 bool "Mystique support"
1196 depends on FB_MATROX
1198 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1199 video card. If you select "Advanced lowlevel driver options" below,
1200 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1201 packed pixel and 32 bpp packed pixel. You can also use font widths
1205 bool "G100/G200/G400/G450/G550 support"
1206 depends on FB_MATROX
1208 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1209 video card. If you select "Advanced lowlevel driver options", you
1210 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1211 pixel and 32 bpp packed pixel. You can also use font widths
1214 If you need support for G400 secondary head, you must first say Y to
1215 "I2C support" in the character devices section, and then to
1216 "Matrox I2C support" and "G400 second head support" here in the
1217 framebuffer section. G450/G550 secondary head and digital output
1218 are supported without additional modules.
1220 The driver starts in monitor mode. You must use the matroxset tool
1221 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1222 swap primary and secondary head outputs, or to change output mode.
1223 Secondary head driver always start in 640x480 resolution and you
1224 must use fbset to change it.
1226 Do not forget that second head supports only 16 and 32 bpp
1227 packed pixels, so it is a good idea to compile them into the kernel
1228 too. You can use only some font widths, as the driver uses generic
1229 painting procedures (the secondary head does not use acceleration
1232 G450/G550 hardware can display TV picture only from secondary CRTC,
1233 and it performs no scaling, so picture must have 525 or 625 lines.
1235 config FB_MATROX_I2C
1236 tristate "Matrox I2C support"
1237 depends on FB_MATROX
1240 This drivers creates I2C buses which are needed for accessing the
1241 DDC (I2C) bus present on all Matroxes, an I2C bus which
1242 interconnects Matrox optional devices, like MGA-TVO on G200 and
1243 G400, and the secondary head DDC bus, present on G400 only.
1245 You can say Y or M here if you want to experiment with monitor
1246 detection code. You must say Y or M here if you want to use either
1247 second head of G400 or MGA-TVO on G200 or G400.
1249 If you compile it as module, it will create a module named
1252 config FB_MATROX_MAVEN
1253 tristate "G400 second head support"
1254 depends on FB_MATROX_G && FB_MATROX_I2C
1256 WARNING !!! This support does not work with G450 !!!
1258 Say Y or M here if you want to use a secondary head (meaning two
1259 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1260 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1261 secondary head output is blanked while you are in X. With XFree
1262 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1263 the fbdev driver on first head and the fbdev driver on second head.
1265 If you compile it as module, two modules are created,
1266 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1267 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1268 also load i2c-matroxfb to get it to run.
1270 The driver starts in monitor mode and you must use the matroxset
1272 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1273 PAL or NTSC or to swap primary and secondary head outputs.
1274 Secondary head driver also always start in 640x480 resolution, you
1275 must use fbset to change it.
1277 Also do not forget that second head supports only 16 and 32 bpp
1278 packed pixels, so it is a good idea to compile them into the kernel
1279 too. You can use only some font widths, as the driver uses generic
1280 painting procedures (the secondary head does not use acceleration
1283 config FB_MATROX_MULTIHEAD
1284 bool "Multihead support"
1285 depends on FB_MATROX
1287 Say Y here if you have more than one (supported) Matrox device in
1288 your computer and you want to use all of them for different monitors
1289 ("multihead"). If you have only one device, you should say N because
1290 the driver compiled with Y is larger and a bit slower, especially on
1293 If you said M to "Matrox unified accelerated driver" and N here, you
1294 will still be able to use several Matrox devices simultaneously:
1295 insert several instances of the module matroxfb into the kernel
1296 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1297 for the different Matrox devices. This method is slightly faster but
1298 uses 40 KB of kernel memory per Matrox card.
1300 There is no need for enabling 'Matrox multihead support' if you have
1301 only one Matrox card in the box.
1304 tristate "ATI Radeon display support"
1305 depends on FB && PCI
1306 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1307 select FB_MODE_HELPERS
1308 select FB_CFB_FILLRECT
1309 select FB_CFB_COPYAREA
1310 select FB_CFB_IMAGEBLIT
1311 select FB_MACMODES if PPC_OF
1313 Choose this option if you want to use an ATI Radeon graphics card as
1314 a framebuffer device. There are both PCI and AGP versions. You
1315 don't need to choose this to run the Radeon in plain VGA mode.
1317 If you say Y here and want DDC/I2C support you must first say Y to
1318 "I2C support" and "I2C bit-banging support" in the character devices
1321 If you say M here then "I2C support" and "I2C bit-banging support"
1322 can be build either as modules or built-in.
1324 There is a product page at
1325 http://apps.ati.com/ATIcompare/
1327 config FB_RADEON_I2C
1328 bool "DDC/I2C for ATI Radeon support"
1329 depends on FB_RADEON
1333 Say Y here if you want DDC/I2C support for your Radeon board.
1335 config FB_RADEON_BACKLIGHT
1336 bool "Support for backlight control"
1337 depends on FB_RADEON
1340 Say Y here if you want to control the backlight of your display.
1342 config FB_RADEON_DEBUG
1343 bool "Lots of debug output from Radeon driver"
1344 depends on FB_RADEON
1347 Say Y here if you want the Radeon driver to output all sorts
1348 of debugging information to provide to the maintainer when
1349 something goes wrong.
1352 tristate "ATI Rage128 display support"
1353 depends on FB && PCI
1354 select FB_CFB_FILLRECT
1355 select FB_CFB_COPYAREA
1356 select FB_CFB_IMAGEBLIT
1357 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1358 select FB_MACMODES if PPC_PMAC
1360 This driver supports graphics boards with the ATI Rage128 chips.
1361 Say Y if you have such a graphics board and read
1362 <file:Documentation/fb/aty128fb.txt>.
1364 To compile this driver as a module, choose M here: the
1365 module will be called aty128fb.
1367 config FB_ATY128_BACKLIGHT
1368 bool "Support for backlight control"
1369 depends on FB_ATY128
1372 Say Y here if you want to control the backlight of your display.
1375 tristate "ATI Mach64 display support" if PCI || ATARI
1376 depends on FB && !SPARC32
1377 select FB_CFB_FILLRECT
1378 select FB_CFB_COPYAREA
1379 select FB_CFB_IMAGEBLIT
1380 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1381 select FB_MACMODES if PPC
1383 This driver supports graphics boards with the ATI Mach64 chips.
1384 Say Y if you have such a graphics board.
1386 To compile this driver as a module, choose M here: the
1387 module will be called atyfb.
1390 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1391 depends on PCI && FB_ATY
1392 default y if SPARC64 && PCI
1394 Say Y here to support use of ATI's 64-bit Rage boards (or other
1395 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1396 framebuffer device. The ATI product support page for these boards
1397 is at <http://support.ati.com/products/pc/mach64/>.
1399 config FB_ATY_GENERIC_LCD
1400 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1401 depends on FB_ATY_CT
1403 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1404 Rage XC, or Rage XL chipset.
1407 bool "Mach64 GX support" if PCI
1411 Say Y here to support use of the ATI Mach64 Graphics Expression
1412 board (or other boards based on the Mach64 GX chipset) as a
1413 framebuffer device. The ATI product support page for these boards
1415 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1417 config FB_ATY_BACKLIGHT
1418 bool "Support for backlight control"
1422 Say Y here if you want to control the backlight of your display.
1425 tristate "S3 Trio/Virge support"
1426 depends on FB && PCI
1427 select FB_CFB_FILLRECT
1428 select FB_CFB_COPYAREA
1429 select FB_CFB_IMAGEBLIT
1430 select FB_TILEBLITTING
1433 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1435 Driver for graphics boards with S3 Trio / S3 Virge chip.
1438 tristate "S3 Savage support"
1439 depends on FB && PCI && EXPERIMENTAL
1440 select FB_MODE_HELPERS
1441 select FB_CFB_FILLRECT
1442 select FB_CFB_COPYAREA
1443 select FB_CFB_IMAGEBLIT
1446 This driver supports notebooks and computers with S3 Savage PCI/AGP
1449 Say Y if you have such a graphics card.
1451 To compile this driver as a module, choose M here; the module
1452 will be called savagefb.
1454 config FB_SAVAGE_I2C
1455 bool "Enable DDC2 Support"
1456 depends on FB_SAVAGE
1459 This enables I2C support for S3 Savage Chipsets. This is used
1460 only for getting EDID information from the attached display
1461 allowing for robust video mode handling and switching.
1463 Because fbdev-2.6 requires that drivers must be able to
1464 independently validate video mode parameters, you should say Y
1467 config FB_SAVAGE_ACCEL
1468 bool "Enable Console Acceleration"
1469 depends on FB_SAVAGE
1472 This option will compile in console acceleration support. If
1473 the resulting framebuffer console has bothersome glitches, then
1477 tristate "SiS/XGI display support"
1478 depends on FB && PCI
1479 select FB_CFB_FILLRECT
1480 select FB_CFB_COPYAREA
1481 select FB_CFB_IMAGEBLIT
1483 This is the frame buffer device driver for the SiS 300, 315, 330
1484 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1485 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1487 To compile this driver as a module, choose M here; the module
1488 will be called sisfb.
1491 bool "SiS 300 series support"
1494 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1497 bool "SiS 315/330/340 series and XGI support"
1500 Say Y here to support use of the SiS 315, 330 and 340 series
1501 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1502 as XGI V3XT, V5, V8 and Z7.
1505 tristate "NeoMagic display support"
1506 depends on FB && PCI
1507 select FB_MODE_HELPERS
1508 select FB_CFB_FILLRECT
1509 select FB_CFB_COPYAREA
1510 select FB_CFB_IMAGEBLIT
1513 This driver supports notebooks with NeoMagic PCI chips.
1514 Say Y if you have such a graphics card.
1516 To compile this driver as a module, choose M here: the
1517 module will be called neofb.
1520 tristate "IMG Kyro support"
1521 depends on FB && PCI
1522 select FB_CFB_FILLRECT
1523 select FB_CFB_COPYAREA
1524 select FB_CFB_IMAGEBLIT
1526 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1529 To compile this driver as a module, choose M here: the
1530 module will be called kyrofb.
1533 tristate "3Dfx Banshee/Voodoo3 display support"
1534 depends on FB && PCI
1535 select FB_CFB_IMAGEBLIT
1536 select FB_CFB_FILLRECT
1537 select FB_CFB_COPYAREA
1539 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1540 chips. Say Y if you have such a graphics board.
1542 To compile this driver as a module, choose M here: the
1543 module will be called tdfxfb.
1545 config FB_3DFX_ACCEL
1546 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1547 depends on FB_3DFX && EXPERIMENTAL
1549 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1550 with acceleration functions.
1554 tristate "3Dfx Voodoo Graphics (sst1) support"
1555 depends on FB && PCI
1556 select FB_CFB_FILLRECT
1557 select FB_CFB_COPYAREA
1558 select FB_CFB_IMAGEBLIT
1560 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1561 Voodoo2 (cvg) based graphics card.
1563 To compile this driver as a module, choose M here: the
1564 module will be called sstfb.
1566 WARNING: Do not use any application that uses the 3D engine
1567 (namely glide) while using this driver.
1568 Please read the <file:Documentation/fb/sstfb.txt> for supported
1569 options and other important info support.
1572 tristate "VIA VT8623 support"
1573 depends on FB && PCI
1574 select FB_CFB_FILLRECT
1575 select FB_CFB_COPYAREA
1576 select FB_CFB_IMAGEBLIT
1577 select FB_TILEBLITTING
1580 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1582 Driver for CastleRock integrated graphics core in the
1583 VIA VT8623 [Apollo CLE266] chipset.
1586 tristate "Cyberblade/i1 support"
1587 depends on FB && PCI && X86_32 && !64BIT
1588 select FB_CFB_IMAGEBLIT
1591 This driver is supposed to support the Trident Cyberblade/i1
1592 graphics core integrated in the VIA VT8601A North Bridge,
1593 also known as VIA Apollo PLE133.
1596 - Developed, tested and working on EPIA 5000 and EPIA 800.
1597 - Does work reliable on all systems with CRT/LCD connected to
1599 - Should work on systems that do use the internal LCD port, but
1600 this is absolutely not tested.
1602 Character imageblit, copyarea and rectangle fill are hw accelerated,
1603 ypan scrolling is used by default.
1605 Please do read <file:Documentation/fb/cyblafb/*>.
1607 To compile this driver as a module, choose M here: the
1608 module will be called cyblafb.
1611 tristate "Trident support"
1612 depends on FB && PCI
1613 select FB_CFB_FILLRECT
1614 select FB_CFB_COPYAREA
1615 select FB_CFB_IMAGEBLIT
1617 This driver is supposed to support graphics boards with the
1618 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1619 but also on some motherboards. For more information, read
1620 <file:Documentation/fb/tridentfb.txt>
1622 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1625 Say Y if you have such a graphics board.
1628 To compile this driver as a module, choose M here: the
1629 module will be called tridentfb.
1631 config FB_TRIDENT_ACCEL
1632 bool "Trident Acceleration functions (EXPERIMENTAL)"
1633 depends on FB_TRIDENT && EXPERIMENTAL
1635 This will compile the Trident frame buffer device with
1636 acceleration functions.
1639 tristate "ARK 2000PV support"
1640 depends on FB && PCI
1641 select FB_CFB_FILLRECT
1642 select FB_CFB_COPYAREA
1643 select FB_CFB_IMAGEBLIT
1644 select FB_TILEBLITTING
1647 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1649 Driver for PCI graphics boards with ARK 2000PV chip
1650 and ICS 5342 RAMDAC.
1653 tristate "Permedia3 support (EXPERIMENTAL)"
1654 depends on FB && PCI && EXPERIMENTAL
1655 select FB_CFB_FILLRECT
1656 select FB_CFB_COPYAREA
1657 select FB_CFB_IMAGEBLIT
1659 This is the frame buffer device driver for the 3DLabs Permedia3
1660 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1661 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1662 and maybe other boards.
1665 bool "Au1100 LCD Driver"
1666 depends on (FB = y) && MIPS && SOC_AU1100
1667 select FB_CFB_FILLRECT
1668 select FB_CFB_COPYAREA
1669 select FB_CFB_IMAGEBLIT
1671 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1672 various panels and CRTs by passing in kernel cmd line option
1673 au1100fb:panel=<name>.
1676 bool "Au1200 LCD Driver"
1677 depends on (FB = y) && MIPS && SOC_AU1200
1678 select FB_CFB_FILLRECT
1679 select FB_CFB_COPYAREA
1680 select FB_CFB_IMAGEBLIT
1682 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1683 various panels and CRTs by passing in kernel cmd line option
1684 au1200fb:panel=<name>.
1686 source "drivers/video/geode/Kconfig"
1689 tristate "HD64461 Frame Buffer support"
1690 depends on FB && HD64461
1691 select FB_CFB_FILLRECT
1692 select FB_CFB_COPYAREA
1693 select FB_CFB_IMAGEBLIT
1695 This is the frame buffer device driver for the Hitachi HD64461 LCD
1699 bool "PMAG-AA TURBOchannel framebuffer support"
1700 depends on (FB = y) && TC
1701 select FB_CFB_FILLRECT
1702 select FB_CFB_COPYAREA
1703 select FB_CFB_IMAGEBLIT
1705 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1706 used mainly in the MIPS-based DECstation series.
1709 tristate "PMAG-BA TURBOchannel framebuffer support"
1711 select FB_CFB_FILLRECT
1712 select FB_CFB_COPYAREA
1713 select FB_CFB_IMAGEBLIT
1715 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1716 used mainly in the MIPS-based DECstation series.
1719 tristate "PMAGB-B TURBOchannel framebuffer support"
1721 select FB_CFB_FILLRECT
1722 select FB_CFB_COPYAREA
1723 select FB_CFB_IMAGEBLIT
1725 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1726 in the MIPS-based DECstation series. The card is currently only
1727 supported in 1280x1024x8 mode.
1730 bool "Maxine (Personal DECstation) onboard framebuffer support"
1731 depends on (FB = y) && MACH_DECSTATION
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1736 Support for the onboard framebuffer (1024x768x8) in the Personal
1737 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1741 bool "G364 frame buffer support"
1742 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1743 select FB_CFB_FILLRECT
1744 select FB_CFB_COPYAREA
1745 select FB_CFB_IMAGEBLIT
1747 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1748 Olivetti M700-10 systems.
1751 bool "Motorola 68328 native frame buffer support"
1752 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1753 select FB_CFB_FILLRECT
1754 select FB_CFB_COPYAREA
1755 select FB_CFB_IMAGEBLIT
1757 Say Y here if you want to support the built-in frame buffer of
1758 the Motorola 68328 CPU family.
1761 tristate "PXA LCD framebuffer support"
1762 depends on FB && ARCH_PXA
1763 select FB_CFB_FILLRECT
1764 select FB_CFB_COPYAREA
1765 select FB_CFB_IMAGEBLIT
1767 Frame buffer driver for the built-in LCD controller in the Intel
1770 This driver is also available as a module ( = code which can be
1771 inserted and removed from the running kernel whenever you want). The
1772 module will be called pxafb. If you want to compile it as a module,
1773 say M here and read <file:Documentation/kbuild/modules.txt>.
1777 config FB_PXA_SMARTPANEL
1778 bool "PXA Smartpanel LCD support"
1782 config FB_PXA_PARAMETERS
1783 bool "PXA LCD command line parameters"
1787 Enable the use of kernel command line or module parameters
1788 to configure the physical properties of the LCD panel when
1789 using the PXA LCD driver.
1791 This option allows you to override the panel parameters
1792 supplied by the platform in order to support multiple
1793 different models of flatpanel. If you will only be using a
1794 single model of flatpanel then you can safely leave this
1797 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1800 tristate "2700G LCD framebuffer support"
1801 depends on FB && ARCH_PXA
1802 select FB_CFB_FILLRECT
1803 select FB_CFB_COPYAREA
1804 select FB_CFB_IMAGEBLIT
1806 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1810 bool "Enable debugging info via debugfs"
1811 depends on FB_MBX && DEBUG_FS
1814 Enable this if you want debugging information using the debug
1815 filesystem (debugfs)
1820 tristate "Freescale DIU framebuffer support"
1821 depends on FB && FSL_SOC
1822 select FB_CFB_FILLRECT
1823 select FB_CFB_COPYAREA
1824 select FB_CFB_IMAGEBLIT
1825 select PPC_LIB_RHEAP
1827 Framebuffer driver for the Freescale SoC DIU
1830 tristate "W100 frame buffer support"
1831 depends on FB && PXA_SHARPSL
1832 select FB_CFB_FILLRECT
1833 select FB_CFB_COPYAREA
1834 select FB_CFB_IMAGEBLIT
1836 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1838 This driver is also available as a module ( = code which can be
1839 inserted and removed from the running kernel whenever you want). The
1840 module will be called w100fb. If you want to compile it as a module,
1841 say M here and read <file:Documentation/kbuild/modules.txt>.
1846 tristate "S3C2410 LCD framebuffer support"
1847 depends on FB && ARCH_S3C2410
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 Frame buffer driver for the built-in LCD controller in the Samsung
1855 This driver is also available as a module ( = code which can be
1856 inserted and removed from the running kernel whenever you want). The
1857 module will be called s3c2410fb. If you want to compile it as a module,
1858 say M here and read <file:Documentation/kbuild/modules.txt>.
1861 config FB_S3C2410_DEBUG
1862 bool "S3C2410 lcd debug messages"
1863 depends on FB_S3C2410
1865 Turn on debugging messages. Note that you can set/unset at run time
1869 tristate "Silicon Motion SM501 framebuffer support"
1870 depends on FB && MFD_SM501
1871 select FB_CFB_FILLRECT
1872 select FB_CFB_COPYAREA
1873 select FB_CFB_IMAGEBLIT
1875 Frame buffer driver for the CRT and LCD controllers in the Silicon
1878 This driver is also available as a module ( = code which can be
1879 inserted and removed from the running kernel whenever you want). The
1880 module will be called sm501fb. If you want to compile it as a module,
1881 say M here and read <file:Documentation/kbuild/modules.txt>.
1886 config FB_PNX4008_DUM
1887 tristate "Display Update Module support on Philips PNX4008 board"
1888 depends on FB && ARCH_PNX4008
1890 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1892 config FB_PNX4008_DUM_RGB
1893 tristate "RGB Framebuffer support on Philips PNX4008 board"
1894 depends on FB_PNX4008_DUM
1895 select FB_CFB_FILLRECT
1896 select FB_CFB_COPYAREA
1897 select FB_CFB_IMAGEBLIT
1899 Say Y here to enable support for PNX4008 RGB Framebuffer
1901 config FB_IBM_GXT4500
1902 tristate "Framebuffer support for IBM GXT4500P adaptor"
1903 depends on FB && PPC
1904 select FB_CFB_FILLRECT
1905 select FB_CFB_COPYAREA
1906 select FB_CFB_IMAGEBLIT
1908 Say Y here to enable support for the IBM GXT4500P display
1909 adaptor, found on some IBM System P (pSeries) machines.
1912 tristate "PS3 GPU framebuffer driver"
1913 depends on FB && PS3_PS3AV
1914 select FB_SYS_FILLRECT
1915 select FB_SYS_COPYAREA
1916 select FB_SYS_IMAGEBLIT
1918 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1920 Include support for the virtual frame buffer in the PS3 platform.
1922 config FB_PS3_DEFAULT_SIZE_M
1923 int "PS3 default frame buffer size (in MiB)"
1927 This is the default size (in MiB) of the virtual frame buffer in
1929 The default value can be overridden on the kernel command line
1930 using the "ps3fb" option (e.g. "ps3fb=9M");
1933 tristate "Xilinx frame buffer support"
1934 depends on FB && XILINX_VIRTEX
1935 select FB_CFB_FILLRECT
1936 select FB_CFB_COPYAREA
1937 select FB_CFB_IMAGEBLIT
1939 Include support for the Xilinx ML300/ML403 reference design
1940 framebuffer. ML300 carries a 640*480 LCD display on the board,
1941 ML403 uses a standard DB15 VGA connector.
1944 tristate "AM-200 E-Ink EPD devkit support"
1945 depends on FB && ARCH_PXA && MMU
1946 select FB_SYS_FILLRECT
1947 select FB_SYS_COPYAREA
1948 select FB_SYS_IMAGEBLIT
1950 select FB_DEFERRED_IO
1953 This enables support for the Metronome display controller used on
1954 the E-Ink AM-200 EPD devkit.
1957 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1959 select FB_SYS_FILLRECT
1960 select FB_SYS_COPYAREA
1961 select FB_SYS_IMAGEBLIT
1964 This is a `virtual' frame buffer device. It operates on a chunk of
1965 unswappable kernel memory instead of on the memory of a graphics
1966 board. This means you cannot see any output sent to this frame
1967 buffer device, while it does consume precious memory. The main use
1968 of this frame buffer device is testing and debugging the frame
1969 buffer subsystem. Do NOT enable it for normal systems! To protect
1970 the innocent, it has to be enabled explicitly at boot time using the
1971 kernel option `video=vfb:'.
1973 To compile this driver as a module, choose M here: the
1974 module will be called vfb. In order to load it, you must use
1975 the vfb_enable=1 option.
1979 config XEN_FBDEV_FRONTEND
1980 tristate "Xen virtual frame buffer support"
1981 depends on FB && XEN
1982 select FB_SYS_FILLRECT
1983 select FB_SYS_COPYAREA
1984 select FB_SYS_IMAGEBLIT
1986 select FB_DEFERRED_IO
1989 This driver implements the front-end of the Xen virtual
1990 frame buffer driver. It communicates with a back-end
1993 source "drivers/video/omap/Kconfig"
1995 source "drivers/video/backlight/Kconfig"
1996 source "drivers/video/display/Kconfig"
1999 source "drivers/video/console/Kconfig"
2002 if FB || SGI_NEWPORT_CONSOLE
2003 source "drivers/video/logo/Kconfig"