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
178 depends on FB_DEFERRED_IO
183 depends on FB_DEFERRED_IO
190 Common utility functions useful to fbdev drivers of VGA-based
201 select BACKLIGHT_LCD_SUPPORT
202 select BACKLIGHT_CLASS_DEVICE
205 config FB_MODE_HELPERS
206 bool "Enable Video Mode Handling Helpers"
210 This enables functions for handling video modes using the
211 Generalized Timing Formula and the EDID parser. A few drivers rely
212 on this feature such as the radeonfb, rivafb, and the i810fb. If
213 your driver does not take advantage of this feature, choosing Y will
214 just increase the kernel size by about 5K.
216 config FB_TILEBLITTING
217 bool "Enable Tile Blitting Support"
221 This enables tile blitting. Tile blitting is a drawing technique
222 where the screen is divided into rectangular sections (tiles), whereas
223 the standard blitting divides the screen into pixels. Because the
224 default drawing element is a tile, drawing functions will be passed
225 parameters in terms of number of tiles instead of number of pixels.
226 For example, to draw a single character, instead of using bitmaps,
227 an index to an array of bitmaps will be used. To clear or move a
228 rectangular section of a screen, the rectangle will be described in
229 terms of number of tiles in the x- and y-axis.
231 This is particularly important to one driver, matroxfb. If
234 comment "Frame buffer hardware drivers"
238 tristate "Cirrus Logic support"
239 depends on FB && (ZORRO || PCI)
240 select FB_CFB_FILLRECT
241 select FB_CFB_COPYAREA
242 select FB_CFB_IMAGEBLIT
244 This enables support for Cirrus Logic GD542x/543x based boards on
245 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
247 If you have a PCI-based system, this enables support for these
248 chips: GD-543x, GD-544x, GD-5480.
250 Please read the file <file:Documentation/fb/cirrusfb.txt>.
252 Say N unless you have such a graphics board or plan to get one
253 before you next recompile the kernel.
256 tristate "Permedia2 support"
257 depends on FB && ((AMIGA && BROKEN) || PCI)
258 select FB_CFB_FILLRECT
259 select FB_CFB_COPYAREA
260 select FB_CFB_IMAGEBLIT
262 This is the frame buffer device driver for the Permedia2 AGP frame
263 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
265 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
267 config FB_PM2_FIFO_DISCONNECT
268 bool "enable FIFO disconnect feature"
269 depends on FB_PM2 && PCI
271 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
274 tristate "ARM PrimeCell PL110 support"
275 depends on FB && ARM && ARM_AMBA
276 select FB_CFB_FILLRECT
277 select FB_CFB_COPYAREA
278 select FB_CFB_IMAGEBLIT
280 This framebuffer device driver is for the ARM PrimeCell PL110
281 Colour LCD controller. ARM PrimeCells provide the building
282 blocks for System on a Chip devices.
284 If you want to compile this as a module (=code which can be
285 inserted into and removed from the running kernel), say M
286 here and read <file:Documentation/kbuild/modules.txt>. The module
287 will be called amba-clcd.
291 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
293 default FB_ARMCLCD_SHARP_LQ035Q7DB02
295 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
296 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
298 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
299 color QVGA, HRTFT panel. The LogicPD device includes
300 an integrated HRTFT controller IC.
301 The native resolution is 240x320.
303 config FB_ARMCLCD_SHARP_LQ057Q3DC02
304 bool "LogicPD LCD 5.7\" QVGA"
306 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
307 color QVGA, TFT panel. The LogicPD device includes an
308 The native resolution is 320x240.
310 config FB_ARMCLCD_SHARP_LQ64D343
311 bool "LogicPD LCD 6.4\" VGA"
313 This is an implementation of the Sharp LQ64D343, a 6.4"
314 color VGA, TFT panel. The LogicPD device includes an
315 The native resolution is 640x480.
317 config FB_ARMCLCD_SHARP_LQ10D368
318 bool "LogicPD LCD 10.4\" VGA"
320 This is an implementation of the Sharp LQ10D368, a 10.4"
321 color VGA, TFT panel. The LogicPD device includes an
322 The native resolution is 640x480.
325 config FB_ARMCLCD_SHARP_LQ121S1DG41
326 bool "LogicPD LCD 12.1\" SVGA"
328 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
329 color SVGA, TFT panel. The LogicPD device includes an
330 The native resolution is 800x600.
332 This panel requires a clock rate may be an integer fraction
333 of the base LCDCLK frequency. The driver will select the
334 highest frequency available that is lower than the maximum
335 allowed. The panel may flicker if the clock rate is
336 slower than the recommended minimum.
338 config FB_ARMCLCD_AUO_A070VW01_WIDE
339 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
341 This is an implementation of the AU Optronics, a 7.0"
342 WIDE Color. The native resolution is 234x480.
344 config FB_ARMCLCD_HITACHI
345 bool "Hitachi Wide Screen 800x480"
347 This is an implementation of the Hitachi 800x480.
353 bool "Acorn VIDC support"
354 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
355 select FB_CFB_FILLRECT
356 select FB_CFB_COPYAREA
357 select FB_CFB_IMAGEBLIT
359 This is the frame buffer device driver for the Acorn VIDC graphics
360 hardware found in Acorn RISC PCs and other ARM-based machines. If
364 bool "CLPS711X LCD support"
365 depends on (FB = y) && ARM && ARCH_CLPS711X
366 select FB_CFB_FILLRECT
367 select FB_CFB_COPYAREA
368 select FB_CFB_IMAGEBLIT
370 Say Y to enable the Framebuffer driver for the CLPS7111 and
374 bool "SA-1100 LCD support"
375 depends on (FB = y) && ARM && ARCH_SA1100
376 select FB_CFB_FILLRECT
377 select FB_CFB_COPYAREA
378 select FB_CFB_IMAGEBLIT
380 This is a framebuffer device for the SA-1100 LCD Controller.
381 See <http://www.linux-fbdev.org/> for information on framebuffer
384 If you plan to use the LCD display with your SA-1100 system, say
388 tristate "Motorola i.MX LCD support"
389 depends on FB && ARM && ARCH_IMX
390 select FB_CFB_FILLRECT
391 select FB_CFB_COPYAREA
392 select FB_CFB_IMAGEBLIT
395 tristate "CyberPro 2000/2010/5000 support"
396 depends on FB && PCI && (BROKEN || !SPARC64)
397 select FB_CFB_FILLRECT
398 select FB_CFB_COPYAREA
399 select FB_CFB_IMAGEBLIT
401 This enables support for the Integraphics CyberPro 20x0 and 5000
402 VGA chips used in the Rebel.com Netwinder and other machines.
403 Say Y if you have a NetWinder or a graphics card containing this
404 device, otherwise say N.
408 depends on (FB = y) && APOLLO
410 select FB_CFB_FILLRECT
411 select FB_CFB_IMAGEBLIT
415 depends on (FB = y) && Q40
417 select FB_CFB_FILLRECT
418 select FB_CFB_COPYAREA
419 select FB_CFB_IMAGEBLIT
422 tristate "Amiga native chipset support"
423 depends on FB && AMIGA
425 This is the frame buffer device driver for the builtin graphics
426 chipset found in Amigas.
428 To compile this driver as a module, choose M here: the
429 module will be called amifb.
432 bool "Amiga OCS chipset support"
435 This enables support for the original Agnus and Denise video chips,
436 found in the Amiga 1000 and most A500's and A2000's. If you intend
437 to run Linux on any of these systems, say Y; otherwise say N.
440 bool "Amiga ECS chipset support"
443 This enables support for the Enhanced Chip Set, found in later
444 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
445 you intend to run Linux on any of these systems, say Y; otherwise
449 bool "Amiga AGA chipset support"
452 This enables support for the Advanced Graphics Architecture (also
453 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
454 and CD32. If you intend to run Linux on any of these systems, say Y;
458 bool "Amiga FrameMaster II/Rainbow II support"
459 depends on (FB = y) && ZORRO
460 select FB_CFB_FILLRECT
461 select FB_CFB_COPYAREA
462 select FB_CFB_IMAGEBLIT
464 This is the frame buffer device driver for the Amiga FrameMaster
465 card from BSC (exhibited 1992 but not shipped as a CBM product).
468 tristate "Arc Monochrome LCD board support"
470 select FB_SYS_FILLRECT
471 select FB_SYS_COPYAREA
472 select FB_SYS_IMAGEBLIT
475 This enables support for the Arc Monochrome LCD board. The board
476 is based on the KS-108 lcd controller and is typically a matrix
477 of 2*n chips. This driver was tested with a 128x64 panel. This
478 driver supports it for use with x86 SBCs through a 16 bit GPIO
479 interface (8 bit data, 8 bit control). If you anticipate using
480 this driver, say Y or M; otherwise say N. You must specify the
481 GPIO IO address to be used for setting control and data.
484 bool "Atari native chipset support"
485 depends on (FB = y) && ATARI
486 select FB_CFB_FILLRECT
487 select FB_CFB_COPYAREA
488 select FB_CFB_IMAGEBLIT
490 This is the frame buffer device driver for the builtin graphics
491 chipset found in Ataris.
494 bool "Open Firmware frame buffer device support"
495 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
496 select FB_CFB_FILLRECT
497 select FB_CFB_COPYAREA
498 select FB_CFB_IMAGEBLIT
501 Say Y if you want support with Open Firmware for your graphics
505 bool "Apple \"control\" display support"
506 depends on (FB = y) && PPC_PMAC && PPC32
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
512 This driver supports a frame buffer for the graphics adapter in the
513 Power Macintosh 7300 and others.
516 bool "Apple \"platinum\" display support"
517 depends on (FB = y) && PPC_PMAC && PPC32
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 This driver supports a frame buffer for the "platinum" graphics
524 adapter in some Power Macintoshes.
527 bool "Apple \"valkyrie\" display support"
528 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
529 select FB_CFB_FILLRECT
530 select FB_CFB_COPYAREA
531 select FB_CFB_IMAGEBLIT
534 This driver supports a frame buffer for the "valkyrie" graphics
535 adapter in some Power Macintoshes.
538 bool "Chips 65550 display support"
539 depends on (FB = y) && PPC32 && PCI
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
544 This is the frame buffer device driver for the Chips & Technologies
545 65550 graphics chip in PowerBooks.
548 bool "Asiliant (Chips) 69000 display support"
549 depends on (FB = y) && PCI
550 select FB_CFB_FILLRECT
551 select FB_CFB_COPYAREA
552 select FB_CFB_IMAGEBLIT
554 This is the frame buffer device driver for the Asiliant 69030 chipset
557 bool "IMS Twin Turbo display support"
558 depends on (FB = y) && PCI
559 select FB_CFB_IMAGEBLIT
560 select FB_MACMODES if PPC
562 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
563 many Macintosh and compatible computers.
566 tristate "VGA 16-color graphics support"
567 depends on FB && (X86 || PPC)
568 select FB_CFB_FILLRECT
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
572 select FONT_8x16 if FRAMEBUFFER_CONSOLE
574 This is the frame buffer device driver for VGA 16 color graphic
575 cards. Say Y if you have such a card.
577 To compile this driver as a module, choose M here: the
578 module will be called vga16fb.
580 config FB_BF54X_LQ043
581 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
582 depends on FB && (BF54x) && !BF542
583 select FB_CFB_FILLRECT
584 select FB_CFB_COPYAREA
585 select FB_CFB_IMAGEBLIT
587 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
589 config FB_BFIN_T350MCQB
590 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
591 depends on FB && BLACKFIN
593 select FB_CFB_FILLRECT
594 select FB_CFB_COPYAREA
595 select FB_CFB_IMAGEBLIT
597 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
598 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
599 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
603 tristate "HP STI frame buffer device support"
604 depends on FB && PARISC
605 select FB_CFB_FILLRECT
606 select FB_CFB_COPYAREA
607 select FB_CFB_IMAGEBLIT
610 STI refers to the HP "Standard Text Interface" which is a set of
611 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
612 Enabling this option will implement the linux framebuffer device
613 using calls to the STI BIOS routines for initialisation.
615 If you enable this option, you will get a planar framebuffer device
616 /dev/fb which will work on the most common HP graphic cards of the
617 NGLE family, including the artist chips (in the 7xx and Bxxx series),
618 HCRX, HCRX24, CRX, CRX24 and VisEG series.
620 It is safe to enable this option, so you should probably say "Y".
623 bool "Generic Macintosh display support"
624 depends on (FB = y) && MAC
625 select FB_CFB_FILLRECT
626 select FB_CFB_COPYAREA
627 select FB_CFB_IMAGEBLIT
632 depends on (FB = y) && HP300
633 select FB_CFB_FILLRECT
634 select FB_CFB_IMAGEBLIT
638 tristate "TGA/SFB+ framebuffer support"
639 depends on FB && (ALPHA || TC)
640 select FB_CFB_FILLRECT
641 select FB_CFB_COPYAREA
642 select FB_CFB_IMAGEBLIT
645 This is the frame buffer device driver for generic TGA and SFB+
646 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
647 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
648 TURBOchannel cards, also known as PMAGD-A, -B and -C.
650 Due to hardware limitations ZLX-E2 and E3 cards are not supported
651 for DECstation 5000/200 systems. Additionally due to firmware
652 limitations these cards may cause troubles with booting DECstation
653 5000/240 and /260 systems, but are fully supported under Linux if
654 you manage to get it going. ;-)
656 Say Y if you have one of those.
659 tristate "Userspace VESA VGA graphics support"
660 depends on FB && CONNECTOR
661 select FB_CFB_FILLRECT
662 select FB_CFB_COPYAREA
663 select FB_CFB_IMAGEBLIT
664 select FB_MODE_HELPERS
666 This is the frame buffer driver for generic VBE 2.0 compliant
667 graphic cards. It can also take advantage of VBE 3.0 features,
668 such as refresh rate adjustment.
670 This driver generally provides more features than vesafb but
671 requires a userspace helper application called 'v86d'. See
672 <file:Documentation/fb/uvesafb.txt> for more information.
677 bool "VESA VGA graphics support"
678 depends on (FB = y) && X86
679 select FB_CFB_FILLRECT
680 select FB_CFB_COPYAREA
681 select FB_CFB_IMAGEBLIT
684 This is the frame buffer device driver for generic VESA 2.0
685 compliant graphic cards. The older VESA 1.2 cards are not supported.
686 You will get a boot time penguin logo at no additional cost. Please
687 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
690 bool "EFI-based Framebuffer Support"
691 depends on (FB = y) && X86
692 select FB_CFB_FILLRECT
693 select FB_CFB_COPYAREA
694 select FB_CFB_IMAGEBLIT
696 This is the EFI frame buffer device driver. If the firmware on
697 your platform is UEFI2.0, select Y to add support for
698 Graphics Output Protocol for early console messages to appear.
701 bool "Intel-based Macintosh Framebuffer Support"
702 depends on (FB = y) && X86 && EFI
703 select FB_CFB_FILLRECT
704 select FB_CFB_COPYAREA
705 select FB_CFB_IMAGEBLIT
707 This is the frame buffer device driver for the Intel-based Macintosh
710 tristate "N411 Apollo/Hecuba devkit support"
711 depends on FB && X86 && MMU
712 select FB_SYS_FILLRECT
713 select FB_SYS_COPYAREA
714 select FB_SYS_IMAGEBLIT
716 select FB_DEFERRED_IO
719 This enables support for the Apollo display controller in its
720 Hecuba form using the n411 devkit.
723 tristate "Hercules mono graphics support"
725 select FB_CFB_FILLRECT
726 select FB_CFB_COPYAREA
727 select FB_CFB_IMAGEBLIT
729 Say Y here if you have a Hercules mono graphics card.
731 To compile this driver as a module, choose M here: the
732 module will be called hgafb.
734 As this card technology is 15 years old, most people will answer N
738 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
739 depends on FB_HGA && EXPERIMENTAL
741 This will compile the Hercules mono graphics with
742 acceleration functions.
745 tristate "SGI Visual Workstation framebuffer support"
746 depends on FB && X86_VISWS
747 select FB_CFB_FILLRECT
748 select FB_CFB_COPYAREA
749 select FB_CFB_IMAGEBLIT
751 SGI Visual Workstation support for framebuffer graphics.
754 bool "SGI Graphics Backend frame buffer support"
755 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
756 select FB_CFB_FILLRECT
757 select FB_CFB_COPYAREA
758 select FB_CFB_IMAGEBLIT
760 This is the frame buffer device driver for SGI Graphics Backend.
761 This chip is used in SGI O2 and Visual Workstation 320/540.
764 int "Video memory size in MB"
768 This is the amount of memory reserved for the framebuffer,
769 which can be any value between 1MB and 8MB.
772 bool "SBUS and UPA framebuffers"
773 depends on (FB = y) && SPARC
775 Say Y if you want support for SBUS or UPA based frame buffer device.
779 depends on (FB = y) && (SPARC && FB_SBUS)
780 select FB_CFB_FILLRECT
781 select FB_CFB_COPYAREA
782 select FB_CFB_IMAGEBLIT
784 This is the frame buffer device driver for the BWtwo frame buffer.
787 bool "CGthree support"
788 depends on (FB = y) && (SPARC && FB_SBUS)
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
793 This is the frame buffer device driver for the CGthree frame buffer.
796 bool "CGsix (GX,TurboGX) support"
797 depends on (FB = y) && (SPARC && FB_SBUS)
798 select FB_CFB_COPYAREA
799 select FB_CFB_IMAGEBLIT
801 This is the frame buffer device driver for the CGsix (GX, TurboGX)
805 bool "Creator/Creator3D/Elite3D support"
806 depends on FB_SBUS && SPARC64
807 select FB_CFB_COPYAREA
808 select FB_CFB_IMAGEBLIT
810 This is the frame buffer device driver for the Creator, Creator3D,
811 and Elite3D graphics boards.
814 bool "TCX (SS4/SS5 only) support"
816 select FB_CFB_FILLRECT
817 select FB_CFB_COPYAREA
818 select FB_CFB_IMAGEBLIT
820 This is the frame buffer device driver for the TCX 24/8bit frame
824 bool "CGfourteen (SX) support"
826 select FB_CFB_FILLRECT
827 select FB_CFB_COPYAREA
828 select FB_CFB_IMAGEBLIT
830 This is the frame buffer device driver for the CGfourteen frame
831 buffer on Desktop SPARCsystems with the SX graphics option.
834 bool "P9100 (Sparcbook 3 only) support"
836 select FB_CFB_FILLRECT
837 select FB_CFB_COPYAREA
838 select FB_CFB_IMAGEBLIT
840 This is the frame buffer device driver for the P9100 card
841 supported on Sparcbook 3 machines.
844 bool "Leo (ZX) support"
846 select FB_CFB_FILLRECT
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This is the frame buffer device driver for the SBUS-based Sun ZX
851 (leo) frame buffer cards.
854 bool "IGA 168x display support"
855 depends on (FB = y) && SPARC32
856 select FB_CFB_FILLRECT
857 select FB_CFB_COPYAREA
858 select FB_CFB_IMAGEBLIT
860 This is the framebuffer device for the INTERGRAPHICS 1680 and
861 successor frame buffer cards.
864 bool "Sun XVR-500 3DLABS Wildcat support"
865 depends on (FB = y) && PCI && SPARC64
866 select FB_CFB_FILLRECT
867 select FB_CFB_COPYAREA
868 select FB_CFB_IMAGEBLIT
870 This is the framebuffer device for the Sun XVR-500 and similar
871 graphics cards based upon the 3DLABS Wildcat chipset. The driver
872 only works on sparc64 systems where the system firmware has
873 mostly initialized the card already. It is treated as a
874 completely dumb framebuffer device.
877 bool "Sun XVR-2500 3DLABS Wildcat support"
878 depends on (FB = y) && PCI && SPARC64
879 select FB_CFB_FILLRECT
880 select FB_CFB_COPYAREA
881 select FB_CFB_IMAGEBLIT
883 This is the framebuffer device for the Sun XVR-2500 and similar
884 graphics cards based upon the 3DLABS Wildcat chipset. The driver
885 only works on sparc64 systems where the system firmware has
886 mostly initialized the card already. It is treated as a
887 completely dumb framebuffer device.
890 tristate "NEC PowerVR 2 display support"
891 depends on FB && SH_DREAMCAST
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
896 Say Y here if you have a PowerVR 2 card in your box. If you plan to
897 run linux on your Dreamcast, you will have to say Y here.
898 This driver may or may not work on other PowerVR 2 cards, but is
899 totally untested. Use at your own risk. If unsure, say N.
901 To compile this driver as a module, choose M here: the
902 module will be called pvr2fb.
904 You can pass several parameters to the driver at boot time or at
905 module load time. The parameters look like "video=pvr2:XXX", where
906 the meaning of XXX can be found at the end of the main source file
907 (<file:drivers/video/pvr2fb.c>). Please see the file
908 <file:Documentation/fb/pvr2fb.txt>.
911 bool "Epson 1355 framebuffer support"
912 depends on (FB = y) && ARCH_CEIVA
913 select FB_CFB_FILLRECT
914 select FB_CFB_COPYAREA
915 select FB_CFB_IMAGEBLIT
917 Build in support for the SED1355 Epson Research Embedded RAMDAC
918 LCD/CRT Controller (since redesignated as the S1D13505) as a
919 framebuffer. Product specs at
920 <http://www.erd.epson.com/vdc/html/products.htm>.
923 tristate "Epson S1D13XXX framebuffer support"
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 Support for S1D13XXX framebuffer device family (currently only
930 working with S1D13806). Product specs at
931 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
934 tristate "AT91/AT32 LCD Controller support"
935 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
936 select FB_CFB_FILLRECT
937 select FB_CFB_COPYAREA
938 select FB_CFB_IMAGEBLIT
940 This enables support for the AT91/AT32 LCD Controller.
943 bool "Frame Buffer in internal SRAM"
944 depends on FB_ATMEL && ARCH_AT91SAM9261
946 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
947 to let frame buffer in external SDRAM.
950 bool "Use a STN display with AT91/AT32 LCD Controller"
951 depends on FB_ATMEL && MACH_AT91SAM9261EK
954 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
955 Controller. Say N if you want to connect a TFT.
960 tristate "nVidia Framebuffer Support"
962 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
963 select FB_MODE_HELPERS
964 select FB_CFB_FILLRECT
965 select FB_CFB_COPYAREA
966 select FB_CFB_IMAGEBLIT
970 This driver supports graphics boards with the nVidia chips, TNT
971 and newer. For very old chipsets, such as the RIVA128, then use
973 Say Y if you have such a graphics board.
975 To compile this driver as a module, choose M here: the
976 module will be called nvidiafb.
979 bool "Enable DDC Support"
983 This enables I2C support for nVidia Chipsets. This is used
984 only for getting EDID information from the attached display
985 allowing for robust video mode handling and switching.
987 Because fbdev-2.6 requires that drivers must be able to
988 independently validate video mode parameters, you should say Y
991 config FB_NVIDIA_DEBUG
992 bool "Lots of debug output"
996 Say Y here if you want the nVidia driver to output all sorts
997 of debugging information to provide to the maintainer when
998 something goes wrong.
1000 config FB_NVIDIA_BACKLIGHT
1001 bool "Support for backlight control"
1002 depends on FB_NVIDIA
1005 Say Y here if you want to control the backlight of your display.
1008 tristate "nVidia Riva support"
1009 depends on FB && PCI
1010 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1011 select FB_MODE_HELPERS
1012 select FB_CFB_FILLRECT
1013 select FB_CFB_COPYAREA
1014 select FB_CFB_IMAGEBLIT
1018 This driver supports graphics boards with the nVidia Riva/Geforce
1020 Say Y if you have such a graphics board.
1022 To compile this driver as a module, choose M here: the
1023 module will be called rivafb.
1026 bool "Enable DDC Support"
1030 This enables I2C support for nVidia Chipsets. This is used
1031 only for getting EDID information from the attached display
1032 allowing for robust video mode handling and switching.
1034 Because fbdev-2.6 requires that drivers must be able to
1035 independently validate video mode parameters, you should say Y
1038 config FB_RIVA_DEBUG
1039 bool "Lots of debug output"
1043 Say Y here if you want the Riva driver to output all sorts
1044 of debugging information to provide to the maintainer when
1045 something goes wrong.
1047 config FB_RIVA_BACKLIGHT
1048 bool "Support for backlight control"
1052 Say Y here if you want to control the backlight of your display.
1055 tristate "Intel 810/815 support (EXPERIMENTAL)"
1056 depends on FB && EXPERIMENTAL && PCI && X86_32
1059 select FB_MODE_HELPERS
1060 select FB_CFB_FILLRECT
1061 select FB_CFB_COPYAREA
1062 select FB_CFB_IMAGEBLIT
1065 This driver supports the on-board graphics built in to the Intel 810
1066 and 815 chipsets. Say Y if you have and plan to use such a board.
1068 To compile this driver as a module, choose M here: the
1069 module will be called i810fb.
1071 For more information, please read
1072 <file:Documentation/fb/intel810.txt>
1075 bool "use VESA Generalized Timing Formula"
1078 If you say Y, then the VESA standard, Generalized Timing Formula
1079 or GTF, will be used to calculate the required video timing values
1080 per video mode. Since the GTF allows nondiscrete timings
1081 (nondiscrete being a range of values as opposed to discrete being a
1082 set of values), you'll be able to use any combination of horizontal
1083 and vertical resolutions, and vertical refresh rates without having
1084 to specify your own timing parameters. This is especially useful
1085 to maximize the performance of an aging display, or if you just
1086 have a display with nonstandard dimensions. A VESA compliant
1087 monitor is recommended, but can still work with non-compliant ones.
1088 If you need or want this, then select this option. The timings may
1089 not be compliant with Intel's recommended values. Use at your own
1092 If you say N, the driver will revert to discrete video timings
1093 using a set recommended by Intel in their documentation.
1098 bool "Enable DDC Support"
1099 depends on FB_I810 && FB_I810_GTF
1104 tristate "Intel LE80578 (Vermilion) support"
1105 depends on FB && PCI && X86
1106 select FB_MODE_HELPERS
1107 select FB_CFB_FILLRECT
1108 select FB_CFB_COPYAREA
1109 select FB_CFB_IMAGEBLIT
1111 This driver supports the LE80578 (Vermilion Range) chipset
1113 config FB_CARILLO_RANCH
1114 tristate "Intel Carillo Ranch support"
1115 depends on FB_LE80578 && FB && PCI && X86
1117 This driver supports the LE80578 (Carillo Ranch) board
1120 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1121 depends on FB && EXPERIMENTAL && PCI && X86
1124 select FB_MODE_HELPERS
1125 select FB_CFB_FILLRECT
1126 select FB_CFB_COPYAREA
1127 select FB_CFB_IMAGEBLIT
1129 This driver supports the on-board graphics built in to the Intel
1130 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1131 Say Y if you have and plan to use such a board.
1133 If you say Y here and want DDC/I2C support you must first say Y to
1134 "I2C support" and "I2C bit-banging support" in the character devices
1137 If you say M here then "I2C support" and "I2C bit-banging support"
1138 can be build either as modules or built-in.
1140 To compile this driver as a module, choose M here: the
1141 module will be called intelfb.
1143 For more information, please read <file:Documentation/fb/intelfb.txt>
1145 config FB_INTEL_DEBUG
1146 bool "Intel driver Debug Messages"
1149 Say Y here if you want the Intel driver to output all sorts
1150 of debugging information to provide to the maintainer when
1151 something goes wrong.
1154 bool "DDC/I2C for Intel framebuffer support"
1159 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1162 tristate "Matrox acceleration"
1163 depends on FB && PCI
1164 select FB_CFB_FILLRECT
1165 select FB_CFB_COPYAREA
1166 select FB_CFB_IMAGEBLIT
1167 select FB_TILEBLITTING
1168 select FB_MACMODES if PPC_PMAC
1170 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1171 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1172 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1173 Matrox G400, G450 or G550 card in your box.
1175 To compile this driver as a module, choose M here: the
1176 module will be called matroxfb.
1178 You can pass several parameters to the driver at boot time or at
1179 module load time. The parameters look like "video=matrox:XXX", and
1180 are described in <file:Documentation/fb/matroxfb.txt>.
1182 config FB_MATROX_MILLENIUM
1183 bool "Millennium I/II support"
1184 depends on FB_MATROX
1186 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1187 video card. If you select "Advanced lowlevel driver options" below,
1188 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1189 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1190 also use font widths different from 8.
1192 config FB_MATROX_MYSTIQUE
1193 bool "Mystique support"
1194 depends on FB_MATROX
1196 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1197 video card. If you select "Advanced lowlevel driver options" below,
1198 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1199 packed pixel and 32 bpp packed pixel. You can also use font widths
1203 bool "G100/G200/G400/G450/G550 support"
1204 depends on FB_MATROX
1206 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1207 video card. If you select "Advanced lowlevel driver options", you
1208 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1209 pixel and 32 bpp packed pixel. You can also use font widths
1212 If you need support for G400 secondary head, you must first say Y to
1213 "I2C support" in the character devices section, and then to
1214 "Matrox I2C support" and "G400 second head support" here in the
1215 framebuffer section. G450/G550 secondary head and digital output
1216 are supported without additional modules.
1218 The driver starts in monitor mode. You must use the matroxset tool
1219 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1220 swap primary and secondary head outputs, or to change output mode.
1221 Secondary head driver always start in 640x480 resolution and you
1222 must use fbset to change it.
1224 Do not forget that second head supports only 16 and 32 bpp
1225 packed pixels, so it is a good idea to compile them into the kernel
1226 too. You can use only some font widths, as the driver uses generic
1227 painting procedures (the secondary head does not use acceleration
1230 G450/G550 hardware can display TV picture only from secondary CRTC,
1231 and it performs no scaling, so picture must have 525 or 625 lines.
1233 config FB_MATROX_I2C
1234 tristate "Matrox I2C support"
1235 depends on FB_MATROX
1238 This drivers creates I2C buses which are needed for accessing the
1239 DDC (I2C) bus present on all Matroxes, an I2C bus which
1240 interconnects Matrox optional devices, like MGA-TVO on G200 and
1241 G400, and the secondary head DDC bus, present on G400 only.
1243 You can say Y or M here if you want to experiment with monitor
1244 detection code. You must say Y or M here if you want to use either
1245 second head of G400 or MGA-TVO on G200 or G400.
1247 If you compile it as module, it will create a module named
1250 config FB_MATROX_MAVEN
1251 tristate "G400 second head support"
1252 depends on FB_MATROX_G && FB_MATROX_I2C
1254 WARNING !!! This support does not work with G450 !!!
1256 Say Y or M here if you want to use a secondary head (meaning two
1257 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1258 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1259 secondary head output is blanked while you are in X. With XFree
1260 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1261 the fbdev driver on first head and the fbdev driver on second head.
1263 If you compile it as module, two modules are created,
1264 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1265 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1266 also load i2c-matroxfb to get it to run.
1268 The driver starts in monitor mode and you must use the matroxset
1270 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1271 PAL or NTSC or to swap primary and secondary head outputs.
1272 Secondary head driver also always start in 640x480 resolution, you
1273 must use fbset to change it.
1275 Also do not forget that second head supports only 16 and 32 bpp
1276 packed pixels, so it is a good idea to compile them into the kernel
1277 too. You can use only some font widths, as the driver uses generic
1278 painting procedures (the secondary head does not use acceleration
1281 config FB_MATROX_MULTIHEAD
1282 bool "Multihead support"
1283 depends on FB_MATROX
1285 Say Y here if you have more than one (supported) Matrox device in
1286 your computer and you want to use all of them for different monitors
1287 ("multihead"). If you have only one device, you should say N because
1288 the driver compiled with Y is larger and a bit slower, especially on
1291 If you said M to "Matrox unified accelerated driver" and N here, you
1292 will still be able to use several Matrox devices simultaneously:
1293 insert several instances of the module matroxfb into the kernel
1294 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1295 for the different Matrox devices. This method is slightly faster but
1296 uses 40 KB of kernel memory per Matrox card.
1298 There is no need for enabling 'Matrox multihead support' if you have
1299 only one Matrox card in the box.
1302 tristate "ATI Radeon display support"
1303 depends on FB && PCI
1304 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1305 select FB_MODE_HELPERS
1306 select FB_CFB_FILLRECT
1307 select FB_CFB_COPYAREA
1308 select FB_CFB_IMAGEBLIT
1309 select FB_MACMODES if PPC_OF
1311 Choose this option if you want to use an ATI Radeon graphics card as
1312 a framebuffer device. There are both PCI and AGP versions. You
1313 don't need to choose this to run the Radeon in plain VGA mode.
1315 If you say Y here and want DDC/I2C support you must first say Y to
1316 "I2C support" and "I2C bit-banging support" in the character devices
1319 If you say M here then "I2C support" and "I2C bit-banging support"
1320 can be build either as modules or built-in.
1322 There is a product page at
1323 http://apps.ati.com/ATIcompare/
1325 config FB_RADEON_I2C
1326 bool "DDC/I2C for ATI Radeon support"
1327 depends on FB_RADEON
1331 Say Y here if you want DDC/I2C support for your Radeon board.
1333 config FB_RADEON_BACKLIGHT
1334 bool "Support for backlight control"
1335 depends on FB_RADEON
1338 Say Y here if you want to control the backlight of your display.
1340 config FB_RADEON_DEBUG
1341 bool "Lots of debug output from Radeon driver"
1342 depends on FB_RADEON
1345 Say Y here if you want the Radeon driver to output all sorts
1346 of debugging information to provide to the maintainer when
1347 something goes wrong.
1350 tristate "ATI Rage128 display support"
1351 depends on FB && PCI
1352 select FB_CFB_FILLRECT
1353 select FB_CFB_COPYAREA
1354 select FB_CFB_IMAGEBLIT
1355 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1356 select FB_MACMODES if PPC_PMAC
1358 This driver supports graphics boards with the ATI Rage128 chips.
1359 Say Y if you have such a graphics board and read
1360 <file:Documentation/fb/aty128fb.txt>.
1362 To compile this driver as a module, choose M here: the
1363 module will be called aty128fb.
1365 config FB_ATY128_BACKLIGHT
1366 bool "Support for backlight control"
1367 depends on FB_ATY128
1370 Say Y here if you want to control the backlight of your display.
1373 tristate "ATI Mach64 display support" if PCI || ATARI
1374 depends on FB && !SPARC32
1375 select FB_CFB_FILLRECT
1376 select FB_CFB_COPYAREA
1377 select FB_CFB_IMAGEBLIT
1378 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1379 select FB_MACMODES if PPC
1381 This driver supports graphics boards with the ATI Mach64 chips.
1382 Say Y if you have such a graphics board.
1384 To compile this driver as a module, choose M here: the
1385 module will be called atyfb.
1388 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1389 depends on PCI && FB_ATY
1390 default y if SPARC64 && PCI
1392 Say Y here to support use of ATI's 64-bit Rage boards (or other
1393 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1394 framebuffer device. The ATI product support page for these boards
1395 is at <http://support.ati.com/products/pc/mach64/>.
1397 config FB_ATY_GENERIC_LCD
1398 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1399 depends on FB_ATY_CT
1401 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1402 Rage XC, or Rage XL chipset.
1405 bool "Mach64 GX support" if PCI
1409 Say Y here to support use of the ATI Mach64 Graphics Expression
1410 board (or other boards based on the Mach64 GX chipset) as a
1411 framebuffer device. The ATI product support page for these boards
1413 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1415 config FB_ATY_BACKLIGHT
1416 bool "Support for backlight control"
1420 Say Y here if you want to control the backlight of your display.
1423 tristate "S3 Trio/Virge support"
1424 depends on FB && PCI
1425 select FB_CFB_FILLRECT
1426 select FB_CFB_COPYAREA
1427 select FB_CFB_IMAGEBLIT
1428 select FB_TILEBLITTING
1431 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1433 Driver for graphics boards with S3 Trio / S3 Virge chip.
1436 tristate "S3 Savage support"
1437 depends on FB && PCI && EXPERIMENTAL
1438 select FB_MODE_HELPERS
1439 select FB_CFB_FILLRECT
1440 select FB_CFB_COPYAREA
1441 select FB_CFB_IMAGEBLIT
1444 This driver supports notebooks and computers with S3 Savage PCI/AGP
1447 Say Y if you have such a graphics card.
1449 To compile this driver as a module, choose M here; the module
1450 will be called savagefb.
1452 config FB_SAVAGE_I2C
1453 bool "Enable DDC2 Support"
1454 depends on FB_SAVAGE
1457 This enables I2C support for S3 Savage Chipsets. This is used
1458 only for getting EDID information from the attached display
1459 allowing for robust video mode handling and switching.
1461 Because fbdev-2.6 requires that drivers must be able to
1462 independently validate video mode parameters, you should say Y
1465 config FB_SAVAGE_ACCEL
1466 bool "Enable Console Acceleration"
1467 depends on FB_SAVAGE
1470 This option will compile in console acceleration support. If
1471 the resulting framebuffer console has bothersome glitches, then
1475 tristate "SiS/XGI display support"
1476 depends on FB && PCI
1477 select FB_CFB_FILLRECT
1478 select FB_CFB_COPYAREA
1479 select FB_CFB_IMAGEBLIT
1481 This is the frame buffer device driver for the SiS 300, 315, 330
1482 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1483 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1485 To compile this driver as a module, choose M here; the module
1486 will be called sisfb.
1489 bool "SiS 300 series support"
1492 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1495 bool "SiS 315/330/340 series and XGI support"
1498 Say Y here to support use of the SiS 315, 330 and 340 series
1499 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1500 as XGI V3XT, V5, V8 and Z7.
1503 tristate "NeoMagic display support"
1504 depends on FB && PCI
1505 select FB_MODE_HELPERS
1506 select FB_CFB_FILLRECT
1507 select FB_CFB_COPYAREA
1508 select FB_CFB_IMAGEBLIT
1511 This driver supports notebooks with NeoMagic PCI chips.
1512 Say Y if you have such a graphics card.
1514 To compile this driver as a module, choose M here: the
1515 module will be called neofb.
1518 tristate "IMG Kyro support"
1519 depends on FB && PCI
1520 select FB_CFB_FILLRECT
1521 select FB_CFB_COPYAREA
1522 select FB_CFB_IMAGEBLIT
1524 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1527 To compile this driver as a module, choose M here: the
1528 module will be called kyrofb.
1531 tristate "3Dfx Banshee/Voodoo3 display support"
1532 depends on FB && PCI
1533 select FB_CFB_IMAGEBLIT
1534 select FB_CFB_FILLRECT
1535 select FB_CFB_COPYAREA
1537 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1538 chips. Say Y if you have such a graphics board.
1540 To compile this driver as a module, choose M here: the
1541 module will be called tdfxfb.
1543 config FB_3DFX_ACCEL
1544 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1545 depends on FB_3DFX && EXPERIMENTAL
1547 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1548 with acceleration functions.
1552 tristate "3Dfx Voodoo Graphics (sst1) support"
1553 depends on FB && PCI
1554 select FB_CFB_FILLRECT
1555 select FB_CFB_COPYAREA
1556 select FB_CFB_IMAGEBLIT
1558 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1559 Voodoo2 (cvg) based graphics card.
1561 To compile this driver as a module, choose M here: the
1562 module will be called sstfb.
1564 WARNING: Do not use any application that uses the 3D engine
1565 (namely glide) while using this driver.
1566 Please read the <file:Documentation/fb/sstfb.txt> for supported
1567 options and other important info support.
1570 tristate "VIA VT8623 support"
1571 depends on FB && PCI
1572 select FB_CFB_FILLRECT
1573 select FB_CFB_COPYAREA
1574 select FB_CFB_IMAGEBLIT
1575 select FB_TILEBLITTING
1578 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1580 Driver for CastleRock integrated graphics core in the
1581 VIA VT8623 [Apollo CLE266] chipset.
1584 tristate "Cyberblade/i1 support"
1585 depends on FB && PCI && X86_32 && !64BIT
1586 select FB_CFB_IMAGEBLIT
1589 This driver is supposed to support the Trident Cyberblade/i1
1590 graphics core integrated in the VIA VT8601A North Bridge,
1591 also known as VIA Apollo PLE133.
1594 - Developed, tested and working on EPIA 5000 and EPIA 800.
1595 - Does work reliable on all systems with CRT/LCD connected to
1597 - Should work on systems that do use the internal LCD port, but
1598 this is absolutely not tested.
1600 Character imageblit, copyarea and rectangle fill are hw accelerated,
1601 ypan scrolling is used by default.
1603 Please do read <file:Documentation/fb/cyblafb/*>.
1605 To compile this driver as a module, choose M here: the
1606 module will be called cyblafb.
1609 tristate "Trident support"
1610 depends on FB && PCI
1611 select FB_CFB_FILLRECT
1612 select FB_CFB_COPYAREA
1613 select FB_CFB_IMAGEBLIT
1615 This driver is supposed to support graphics boards with the
1616 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1617 but also on some motherboards. For more information, read
1618 <file:Documentation/fb/tridentfb.txt>
1620 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1623 Say Y if you have such a graphics board.
1626 To compile this driver as a module, choose M here: the
1627 module will be called tridentfb.
1629 config FB_TRIDENT_ACCEL
1630 bool "Trident Acceleration functions (EXPERIMENTAL)"
1631 depends on FB_TRIDENT && EXPERIMENTAL
1633 This will compile the Trident frame buffer device with
1634 acceleration functions.
1637 tristate "ARK 2000PV support"
1638 depends on FB && PCI
1639 select FB_CFB_FILLRECT
1640 select FB_CFB_COPYAREA
1641 select FB_CFB_IMAGEBLIT
1642 select FB_TILEBLITTING
1645 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1647 Driver for PCI graphics boards with ARK 2000PV chip
1648 and ICS 5342 RAMDAC.
1651 tristate "Permedia3 support (EXPERIMENTAL)"
1652 depends on FB && PCI && EXPERIMENTAL
1653 select FB_CFB_FILLRECT
1654 select FB_CFB_COPYAREA
1655 select FB_CFB_IMAGEBLIT
1657 This is the frame buffer device driver for the 3DLabs Permedia3
1658 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1659 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1660 and maybe other boards.
1663 bool "Au1100 LCD Driver"
1664 depends on (FB = y) && MIPS && SOC_AU1100
1665 select FB_CFB_FILLRECT
1666 select FB_CFB_COPYAREA
1667 select FB_CFB_IMAGEBLIT
1669 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1670 various panels and CRTs by passing in kernel cmd line option
1671 au1100fb:panel=<name>.
1674 bool "Au1200 LCD Driver"
1675 depends on (FB = y) && MIPS && SOC_AU1200
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1680 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1681 various panels and CRTs by passing in kernel cmd line option
1682 au1200fb:panel=<name>.
1684 source "drivers/video/geode/Kconfig"
1687 tristate "HD64461 Frame Buffer support"
1688 depends on FB && HD64461
1689 select FB_CFB_FILLRECT
1690 select FB_CFB_COPYAREA
1691 select FB_CFB_IMAGEBLIT
1693 This is the frame buffer device driver for the Hitachi HD64461 LCD
1697 bool "PMAG-AA TURBOchannel framebuffer support"
1698 depends on (FB = y) && TC
1699 select FB_CFB_FILLRECT
1700 select FB_CFB_COPYAREA
1701 select FB_CFB_IMAGEBLIT
1703 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1704 used mainly in the MIPS-based DECstation series.
1707 tristate "PMAG-BA TURBOchannel framebuffer support"
1709 select FB_CFB_FILLRECT
1710 select FB_CFB_COPYAREA
1711 select FB_CFB_IMAGEBLIT
1713 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1714 used mainly in the MIPS-based DECstation series.
1717 tristate "PMAGB-B TURBOchannel framebuffer support"
1719 select FB_CFB_FILLRECT
1720 select FB_CFB_COPYAREA
1721 select FB_CFB_IMAGEBLIT
1723 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1724 in the MIPS-based DECstation series. The card is currently only
1725 supported in 1280x1024x8 mode.
1728 bool "Maxine (Personal DECstation) onboard framebuffer support"
1729 depends on (FB = y) && MACH_DECSTATION
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1734 Support for the onboard framebuffer (1024x768x8) in the Personal
1735 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1739 bool "G364 frame buffer support"
1740 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1741 select FB_CFB_FILLRECT
1742 select FB_CFB_COPYAREA
1743 select FB_CFB_IMAGEBLIT
1745 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1746 Olivetti M700-10 systems.
1749 bool "Motorola 68328 native frame buffer support"
1750 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1751 select FB_CFB_FILLRECT
1752 select FB_CFB_COPYAREA
1753 select FB_CFB_IMAGEBLIT
1755 Say Y here if you want to support the built-in frame buffer of
1756 the Motorola 68328 CPU family.
1759 tristate "PXA LCD framebuffer support"
1760 depends on FB && ARCH_PXA
1761 select FB_CFB_FILLRECT
1762 select FB_CFB_COPYAREA
1763 select FB_CFB_IMAGEBLIT
1765 Frame buffer driver for the built-in LCD controller in the Intel
1768 This driver is also available as a module ( = code which can be
1769 inserted and removed from the running kernel whenever you want). The
1770 module will be called pxafb. If you want to compile it as a module,
1771 say M here and read <file:Documentation/kbuild/modules.txt>.
1775 config FB_PXA_SMARTPANEL
1776 bool "PXA Smartpanel LCD support"
1780 config FB_PXA_PARAMETERS
1781 bool "PXA LCD command line parameters"
1785 Enable the use of kernel command line or module parameters
1786 to configure the physical properties of the LCD panel when
1787 using the PXA LCD driver.
1789 This option allows you to override the panel parameters
1790 supplied by the platform in order to support multiple
1791 different models of flatpanel. If you will only be using a
1792 single model of flatpanel then you can safely leave this
1795 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1798 tristate "2700G LCD framebuffer support"
1799 depends on FB && ARCH_PXA
1800 select FB_CFB_FILLRECT
1801 select FB_CFB_COPYAREA
1802 select FB_CFB_IMAGEBLIT
1804 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1808 bool "Enable debugging info via debugfs"
1809 depends on FB_MBX && DEBUG_FS
1812 Enable this if you want debugging information using the debug
1813 filesystem (debugfs)
1818 tristate "Freescale DIU framebuffer support"
1819 depends on FB && FSL_SOC
1820 select FB_CFB_FILLRECT
1821 select FB_CFB_COPYAREA
1822 select FB_CFB_IMAGEBLIT
1823 select PPC_LIB_RHEAP
1825 Framebuffer driver for the Freescale SoC DIU
1828 tristate "W100 frame buffer support"
1829 depends on FB && PXA_SHARPSL
1830 select FB_CFB_FILLRECT
1831 select FB_CFB_COPYAREA
1832 select FB_CFB_IMAGEBLIT
1834 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1836 This driver is also available as a module ( = code which can be
1837 inserted and removed from the running kernel whenever you want). The
1838 module will be called w100fb. If you want to compile it as a module,
1839 say M here and read <file:Documentation/kbuild/modules.txt>.
1844 tristate "S3C2410 LCD framebuffer support"
1845 depends on FB && ARCH_S3C2410
1846 select FB_CFB_FILLRECT
1847 select FB_CFB_COPYAREA
1848 select FB_CFB_IMAGEBLIT
1850 Frame buffer driver for the built-in LCD controller in the Samsung
1853 This driver is also available as a module ( = code which can be
1854 inserted and removed from the running kernel whenever you want). The
1855 module will be called s3c2410fb. If you want to compile it as a module,
1856 say M here and read <file:Documentation/kbuild/modules.txt>.
1859 config FB_S3C2410_DEBUG
1860 bool "S3C2410 lcd debug messages"
1861 depends on FB_S3C2410
1863 Turn on debugging messages. Note that you can set/unset at run time
1867 tristate "Silicon Motion SM501 framebuffer support"
1868 depends on FB && MFD_SM501
1869 select FB_CFB_FILLRECT
1870 select FB_CFB_COPYAREA
1871 select FB_CFB_IMAGEBLIT
1873 Frame buffer driver for the CRT and LCD controllers in the Silicon
1876 This driver is also available as a module ( = code which can be
1877 inserted and removed from the running kernel whenever you want). The
1878 module will be called sm501fb. If you want to compile it as a module,
1879 say M here and read <file:Documentation/kbuild/modules.txt>.
1884 config FB_PNX4008_DUM
1885 tristate "Display Update Module support on Philips PNX4008 board"
1886 depends on FB && ARCH_PNX4008
1888 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1890 config FB_PNX4008_DUM_RGB
1891 tristate "RGB Framebuffer support on Philips PNX4008 board"
1892 depends on FB_PNX4008_DUM
1893 select FB_CFB_FILLRECT
1894 select FB_CFB_COPYAREA
1895 select FB_CFB_IMAGEBLIT
1897 Say Y here to enable support for PNX4008 RGB Framebuffer
1899 config FB_IBM_GXT4500
1900 tristate "Framebuffer support for IBM GXT4500P adaptor"
1901 depends on FB && PPC
1902 select FB_CFB_FILLRECT
1903 select FB_CFB_COPYAREA
1904 select FB_CFB_IMAGEBLIT
1906 Say Y here to enable support for the IBM GXT4500P display
1907 adaptor, found on some IBM System P (pSeries) machines.
1910 tristate "PS3 GPU framebuffer driver"
1911 depends on FB && PS3_PS3AV
1912 select FB_SYS_FILLRECT
1913 select FB_SYS_COPYAREA
1914 select FB_SYS_IMAGEBLIT
1916 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1918 Include support for the virtual frame buffer in the PS3 platform.
1920 config FB_PS3_DEFAULT_SIZE_M
1921 int "PS3 default frame buffer size (in MiB)"
1925 This is the default size (in MiB) of the virtual frame buffer in
1927 The default value can be overridden on the kernel command line
1928 using the "ps3fb" option (e.g. "ps3fb=9M");
1931 tristate "Xilinx frame buffer support"
1932 depends on FB && XILINX_VIRTEX
1933 select FB_CFB_FILLRECT
1934 select FB_CFB_COPYAREA
1935 select FB_CFB_IMAGEBLIT
1937 Include support for the Xilinx ML300/ML403 reference design
1938 framebuffer. ML300 carries a 640*480 LCD display on the board,
1939 ML403 uses a standard DB15 VGA connector.
1942 tristate "AM-200 E-Ink EPD devkit support"
1943 depends on FB && ARCH_PXA && MMU
1944 select FB_SYS_FILLRECT
1945 select FB_SYS_COPYAREA
1946 select FB_SYS_IMAGEBLIT
1948 select FB_DEFERRED_IO
1951 This enables support for the Metronome display controller used on
1952 the E-Ink AM-200 EPD devkit.
1955 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1957 select FB_SYS_FILLRECT
1958 select FB_SYS_COPYAREA
1959 select FB_SYS_IMAGEBLIT
1962 This is a `virtual' frame buffer device. It operates on a chunk of
1963 unswappable kernel memory instead of on the memory of a graphics
1964 board. This means you cannot see any output sent to this frame
1965 buffer device, while it does consume precious memory. The main use
1966 of this frame buffer device is testing and debugging the frame
1967 buffer subsystem. Do NOT enable it for normal systems! To protect
1968 the innocent, it has to be enabled explicitly at boot time using the
1969 kernel option `video=vfb:'.
1971 To compile this driver as a module, choose M here: the
1972 module will be called vfb. In order to load it, you must use
1973 the vfb_enable=1 option.
1977 config XEN_FBDEV_FRONTEND
1978 tristate "Xen virtual frame buffer support"
1979 depends on FB && XEN
1980 select FB_SYS_FILLRECT
1981 select FB_SYS_COPYAREA
1982 select FB_SYS_IMAGEBLIT
1984 select FB_DEFERRED_IO
1987 This driver implements the front-end of the Xen virtual
1988 frame buffer driver. It communicates with a back-end
1991 source "drivers/video/omap/Kconfig"
1993 source "drivers/video/backlight/Kconfig"
1994 source "drivers/video/display/Kconfig"
1997 source "drivers/video/console/Kconfig"
2000 if FB || SGI_NEWPORT_CONSOLE
2001 source "drivers/video/logo/Kconfig"