5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/gpu/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) && DIO
633 select FB_CFB_IMAGEBLIT
637 tristate "TGA/SFB+ framebuffer support"
638 depends on FB && (ALPHA || TC)
639 select FB_CFB_FILLRECT
640 select FB_CFB_COPYAREA
641 select FB_CFB_IMAGEBLIT
644 This is the frame buffer device driver for generic TGA and SFB+
645 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
646 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
647 TURBOchannel cards, also known as PMAGD-A, -B and -C.
649 Due to hardware limitations ZLX-E2 and E3 cards are not supported
650 for DECstation 5000/200 systems. Additionally due to firmware
651 limitations these cards may cause troubles with booting DECstation
652 5000/240 and /260 systems, but are fully supported under Linux if
653 you manage to get it going. ;-)
655 Say Y if you have one of those.
658 tristate "Userspace VESA VGA graphics support"
659 depends on FB && CONNECTOR
660 select FB_CFB_FILLRECT
661 select FB_CFB_COPYAREA
662 select FB_CFB_IMAGEBLIT
663 select FB_MODE_HELPERS
665 This is the frame buffer driver for generic VBE 2.0 compliant
666 graphic cards. It can also take advantage of VBE 3.0 features,
667 such as refresh rate adjustment.
669 This driver generally provides more features than vesafb but
670 requires a userspace helper application called 'v86d'. See
671 <file:Documentation/fb/uvesafb.txt> for more information.
676 bool "VESA VGA graphics support"
677 depends on (FB = y) && X86
678 select FB_CFB_FILLRECT
679 select FB_CFB_COPYAREA
680 select FB_CFB_IMAGEBLIT
682 This is the frame buffer device driver for generic VESA 2.0
683 compliant graphic cards. The older VESA 1.2 cards are not supported.
684 You will get a boot time penguin logo at no additional cost. Please
685 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
688 bool "EFI-based Framebuffer Support"
689 depends on (FB = y) && X86
690 select FB_CFB_FILLRECT
691 select FB_CFB_COPYAREA
692 select FB_CFB_IMAGEBLIT
694 This is the EFI frame buffer device driver. If the firmware on
695 your platform is UEFI2.0, select Y to add support for
696 Graphics Output Protocol for early console messages to appear.
699 bool "Intel-based Macintosh Framebuffer Support"
700 depends on (FB = y) && X86 && EFI
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
705 This is the frame buffer device driver for the Intel-based Macintosh
708 tristate "N411 Apollo/Hecuba devkit support"
709 depends on FB && X86 && MMU
710 select FB_SYS_FILLRECT
711 select FB_SYS_COPYAREA
712 select FB_SYS_IMAGEBLIT
714 select FB_DEFERRED_IO
717 This enables support for the Apollo display controller in its
718 Hecuba form using the n411 devkit.
721 tristate "Hercules mono graphics support"
723 select FB_CFB_FILLRECT
724 select FB_CFB_COPYAREA
725 select FB_CFB_IMAGEBLIT
727 Say Y here if you have a Hercules mono graphics card.
729 To compile this driver as a module, choose M here: the
730 module will be called hgafb.
732 As this card technology is 15 years old, most people will answer N
736 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
737 depends on FB_HGA && EXPERIMENTAL
739 This will compile the Hercules mono graphics with
740 acceleration functions.
743 tristate "SGI Visual Workstation framebuffer support"
744 depends on FB && X86_VISWS
745 select FB_CFB_FILLRECT
746 select FB_CFB_COPYAREA
747 select FB_CFB_IMAGEBLIT
749 SGI Visual Workstation support for framebuffer graphics.
752 bool "SGI Graphics Backend frame buffer support"
753 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
754 select FB_CFB_FILLRECT
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
758 This is the frame buffer device driver for SGI Graphics Backend.
759 This chip is used in SGI O2 and Visual Workstation 320/540.
762 int "Video memory size in MB"
766 This is the amount of memory reserved for the framebuffer,
767 which can be any value between 1MB and 8MB.
770 bool "SBUS and UPA framebuffers"
771 depends on (FB = y) && SPARC
773 Say Y if you want support for SBUS or UPA based frame buffer device.
777 depends on (FB = y) && (SPARC && FB_SBUS)
778 select FB_CFB_FILLRECT
779 select FB_CFB_COPYAREA
780 select FB_CFB_IMAGEBLIT
782 This is the frame buffer device driver for the BWtwo frame buffer.
785 bool "CGthree support"
786 depends on (FB = y) && (SPARC && FB_SBUS)
787 select FB_CFB_FILLRECT
788 select FB_CFB_COPYAREA
789 select FB_CFB_IMAGEBLIT
791 This is the frame buffer device driver for the CGthree frame buffer.
794 bool "CGsix (GX,TurboGX) support"
795 depends on (FB = y) && (SPARC && FB_SBUS)
796 select FB_CFB_COPYAREA
797 select FB_CFB_IMAGEBLIT
799 This is the frame buffer device driver for the CGsix (GX, TurboGX)
803 bool "Creator/Creator3D/Elite3D support"
804 depends on FB_SBUS && SPARC64
805 select FB_CFB_COPYAREA
806 select FB_CFB_IMAGEBLIT
808 This is the frame buffer device driver for the Creator, Creator3D,
809 and Elite3D graphics boards.
812 bool "TCX (SS4/SS5 only) support"
814 select FB_CFB_FILLRECT
815 select FB_CFB_COPYAREA
816 select FB_CFB_IMAGEBLIT
818 This is the frame buffer device driver for the TCX 24/8bit frame
822 bool "CGfourteen (SX) support"
824 select FB_CFB_FILLRECT
825 select FB_CFB_COPYAREA
826 select FB_CFB_IMAGEBLIT
828 This is the frame buffer device driver for the CGfourteen frame
829 buffer on Desktop SPARCsystems with the SX graphics option.
832 bool "P9100 (Sparcbook 3 only) support"
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 This is the frame buffer device driver for the P9100 card
839 supported on Sparcbook 3 machines.
842 bool "Leo (ZX) support"
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This is the frame buffer device driver for the SBUS-based Sun ZX
849 (leo) frame buffer cards.
852 bool "IGA 168x display support"
853 depends on (FB = y) && SPARC32
854 select FB_CFB_FILLRECT
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the framebuffer device for the INTERGRAPHICS 1680 and
859 successor frame buffer cards.
862 bool "Sun XVR-500 3DLABS Wildcat support"
863 depends on (FB = y) && PCI && SPARC64
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This is the framebuffer device for the Sun XVR-500 and similar
869 graphics cards based upon the 3DLABS Wildcat chipset. The driver
870 only works on sparc64 systems where the system firmware has
871 mostly initialized the card already. It is treated as a
872 completely dumb framebuffer device.
875 bool "Sun XVR-2500 3DLABS Wildcat support"
876 depends on (FB = y) && PCI && SPARC64
877 select FB_CFB_FILLRECT
878 select FB_CFB_COPYAREA
879 select FB_CFB_IMAGEBLIT
881 This is the framebuffer device for the Sun XVR-2500 and similar
882 graphics cards based upon the 3DLABS Wildcat chipset. The driver
883 only works on sparc64 systems where the system firmware has
884 mostly initialized the card already. It is treated as a
885 completely dumb framebuffer device.
888 tristate "NEC PowerVR 2 display support"
889 depends on FB && SH_DREAMCAST
890 select FB_CFB_FILLRECT
891 select FB_CFB_COPYAREA
892 select FB_CFB_IMAGEBLIT
894 Say Y here if you have a PowerVR 2 card in your box. If you plan to
895 run linux on your Dreamcast, you will have to say Y here.
896 This driver may or may not work on other PowerVR 2 cards, but is
897 totally untested. Use at your own risk. If unsure, say N.
899 To compile this driver as a module, choose M here: the
900 module will be called pvr2fb.
902 You can pass several parameters to the driver at boot time or at
903 module load time. The parameters look like "video=pvr2:XXX", where
904 the meaning of XXX can be found at the end of the main source file
905 (<file:drivers/video/pvr2fb.c>). Please see the file
906 <file:Documentation/fb/pvr2fb.txt>.
909 bool "Epson 1355 framebuffer support"
910 depends on (FB = y) && ARCH_CEIVA
911 select FB_CFB_FILLRECT
912 select FB_CFB_COPYAREA
913 select FB_CFB_IMAGEBLIT
915 Build in support for the SED1355 Epson Research Embedded RAMDAC
916 LCD/CRT Controller (since redesignated as the S1D13505) as a
917 framebuffer. Product specs at
918 <http://www.erd.epson.com/vdc/html/products.htm>.
921 tristate "Epson S1D13XXX framebuffer support"
923 select FB_CFB_FILLRECT
924 select FB_CFB_COPYAREA
925 select FB_CFB_IMAGEBLIT
927 Support for S1D13XXX framebuffer device family (currently only
928 working with S1D13806). Product specs at
929 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
932 tristate "AT91/AT32 LCD Controller support"
933 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
934 select FB_CFB_FILLRECT
935 select FB_CFB_COPYAREA
936 select FB_CFB_IMAGEBLIT
938 This enables support for the AT91/AT32 LCD Controller.
941 bool "Frame Buffer in internal SRAM"
942 depends on FB_ATMEL && ARCH_AT91SAM9261
944 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
945 to let frame buffer in external SDRAM.
948 bool "Use a STN display with AT91/AT32 LCD Controller"
949 depends on FB_ATMEL && MACH_AT91SAM9261EK
952 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
953 Controller. Say N if you want to connect a TFT.
958 tristate "nVidia Framebuffer Support"
960 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
961 select FB_MODE_HELPERS
962 select FB_CFB_FILLRECT
963 select FB_CFB_COPYAREA
964 select FB_CFB_IMAGEBLIT
968 This driver supports graphics boards with the nVidia chips, TNT
969 and newer. For very old chipsets, such as the RIVA128, then use
971 Say Y if you have such a graphics board.
973 To compile this driver as a module, choose M here: the
974 module will be called nvidiafb.
977 bool "Enable DDC Support"
981 This enables I2C support for nVidia Chipsets. This is used
982 only for getting EDID information from the attached display
983 allowing for robust video mode handling and switching.
985 Because fbdev-2.6 requires that drivers must be able to
986 independently validate video mode parameters, you should say Y
989 config FB_NVIDIA_DEBUG
990 bool "Lots of debug output"
994 Say Y here if you want the nVidia driver to output all sorts
995 of debugging information to provide to the maintainer when
996 something goes wrong.
998 config FB_NVIDIA_BACKLIGHT
999 bool "Support for backlight control"
1000 depends on FB_NVIDIA
1003 Say Y here if you want to control the backlight of your display.
1006 tristate "nVidia Riva support"
1007 depends on FB && PCI
1008 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1009 select FB_MODE_HELPERS
1010 select FB_CFB_FILLRECT
1011 select FB_CFB_COPYAREA
1012 select FB_CFB_IMAGEBLIT
1016 This driver supports graphics boards with the nVidia Riva/Geforce
1018 Say Y if you have such a graphics board.
1020 To compile this driver as a module, choose M here: the
1021 module will be called rivafb.
1024 bool "Enable DDC Support"
1028 This enables I2C support for nVidia Chipsets. This is used
1029 only for getting EDID information from the attached display
1030 allowing for robust video mode handling and switching.
1032 Because fbdev-2.6 requires that drivers must be able to
1033 independently validate video mode parameters, you should say Y
1036 config FB_RIVA_DEBUG
1037 bool "Lots of debug output"
1041 Say Y here if you want the Riva driver to output all sorts
1042 of debugging information to provide to the maintainer when
1043 something goes wrong.
1045 config FB_RIVA_BACKLIGHT
1046 bool "Support for backlight control"
1050 Say Y here if you want to control the backlight of your display.
1053 tristate "Intel 810/815 support (EXPERIMENTAL)"
1054 depends on FB && EXPERIMENTAL && PCI && X86_32
1057 select FB_MODE_HELPERS
1058 select FB_CFB_FILLRECT
1059 select FB_CFB_COPYAREA
1060 select FB_CFB_IMAGEBLIT
1063 This driver supports the on-board graphics built in to the Intel 810
1064 and 815 chipsets. Say Y if you have and plan to use such a board.
1066 To compile this driver as a module, choose M here: the
1067 module will be called i810fb.
1069 For more information, please read
1070 <file:Documentation/fb/intel810.txt>
1073 bool "use VESA Generalized Timing Formula"
1076 If you say Y, then the VESA standard, Generalized Timing Formula
1077 or GTF, will be used to calculate the required video timing values
1078 per video mode. Since the GTF allows nondiscrete timings
1079 (nondiscrete being a range of values as opposed to discrete being a
1080 set of values), you'll be able to use any combination of horizontal
1081 and vertical resolutions, and vertical refresh rates without having
1082 to specify your own timing parameters. This is especially useful
1083 to maximize the performance of an aging display, or if you just
1084 have a display with nonstandard dimensions. A VESA compliant
1085 monitor is recommended, but can still work with non-compliant ones.
1086 If you need or want this, then select this option. The timings may
1087 not be compliant with Intel's recommended values. Use at your own
1090 If you say N, the driver will revert to discrete video timings
1091 using a set recommended by Intel in their documentation.
1096 bool "Enable DDC Support"
1097 depends on FB_I810 && FB_I810_GTF
1102 tristate "Intel LE80578 (Vermilion) support"
1103 depends on FB && PCI && X86
1104 select FB_MODE_HELPERS
1105 select FB_CFB_FILLRECT
1106 select FB_CFB_COPYAREA
1107 select FB_CFB_IMAGEBLIT
1109 This driver supports the LE80578 (Vermilion Range) chipset
1111 config FB_CARILLO_RANCH
1112 tristate "Intel Carillo Ranch support"
1113 depends on FB_LE80578 && FB && PCI && X86
1115 This driver supports the LE80578 (Carillo Ranch) board
1118 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1119 depends on FB && EXPERIMENTAL && PCI && X86
1122 select FB_MODE_HELPERS
1123 select FB_CFB_FILLRECT
1124 select FB_CFB_COPYAREA
1125 select FB_CFB_IMAGEBLIT
1127 This driver supports the on-board graphics built in to the Intel
1128 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1129 Say Y if you have and plan to use such a board.
1131 If you say Y here and want DDC/I2C support you must first say Y to
1132 "I2C support" and "I2C bit-banging support" in the character devices
1135 If you say M here then "I2C support" and "I2C bit-banging support"
1136 can be build either as modules or built-in.
1138 To compile this driver as a module, choose M here: the
1139 module will be called intelfb.
1141 For more information, please read <file:Documentation/fb/intelfb.txt>
1143 config FB_INTEL_DEBUG
1144 bool "Intel driver Debug Messages"
1147 Say Y here if you want the Intel driver to output all sorts
1148 of debugging information to provide to the maintainer when
1149 something goes wrong.
1152 bool "DDC/I2C for Intel framebuffer support"
1157 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1160 tristate "Matrox acceleration"
1161 depends on FB && PCI
1162 select FB_CFB_FILLRECT
1163 select FB_CFB_COPYAREA
1164 select FB_CFB_IMAGEBLIT
1165 select FB_TILEBLITTING
1166 select FB_MACMODES if PPC_PMAC
1168 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1169 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1170 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1171 Matrox G400, G450 or G550 card in your box.
1173 To compile this driver as a module, choose M here: the
1174 module will be called matroxfb.
1176 You can pass several parameters to the driver at boot time or at
1177 module load time. The parameters look like "video=matrox:XXX", and
1178 are described in <file:Documentation/fb/matroxfb.txt>.
1180 config FB_MATROX_MILLENIUM
1181 bool "Millennium I/II support"
1182 depends on FB_MATROX
1184 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1185 video card. If you select "Advanced lowlevel driver options" below,
1186 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1187 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1188 also use font widths different from 8.
1190 config FB_MATROX_MYSTIQUE
1191 bool "Mystique support"
1192 depends on FB_MATROX
1194 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1195 video card. If you select "Advanced lowlevel driver options" below,
1196 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1197 packed pixel and 32 bpp packed pixel. You can also use font widths
1201 bool "G100/G200/G400/G450/G550 support"
1202 depends on FB_MATROX
1204 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1205 video card. If you select "Advanced lowlevel driver options", you
1206 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1207 pixel and 32 bpp packed pixel. You can also use font widths
1210 If you need support for G400 secondary head, you must first say Y to
1211 "I2C support" in the character devices section, and then to
1212 "Matrox I2C support" and "G400 second head support" here in the
1213 framebuffer section. G450/G550 secondary head and digital output
1214 are supported without additional modules.
1216 The driver starts in monitor mode. You must use the matroxset tool
1217 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1218 swap primary and secondary head outputs, or to change output mode.
1219 Secondary head driver always start in 640x480 resolution and you
1220 must use fbset to change it.
1222 Do not forget that second head supports only 16 and 32 bpp
1223 packed pixels, so it is a good idea to compile them into the kernel
1224 too. You can use only some font widths, as the driver uses generic
1225 painting procedures (the secondary head does not use acceleration
1228 G450/G550 hardware can display TV picture only from secondary CRTC,
1229 and it performs no scaling, so picture must have 525 or 625 lines.
1231 config FB_MATROX_I2C
1232 tristate "Matrox I2C support"
1233 depends on FB_MATROX
1236 This drivers creates I2C buses which are needed for accessing the
1237 DDC (I2C) bus present on all Matroxes, an I2C bus which
1238 interconnects Matrox optional devices, like MGA-TVO on G200 and
1239 G400, and the secondary head DDC bus, present on G400 only.
1241 You can say Y or M here if you want to experiment with monitor
1242 detection code. You must say Y or M here if you want to use either
1243 second head of G400 or MGA-TVO on G200 or G400.
1245 If you compile it as module, it will create a module named
1248 config FB_MATROX_MAVEN
1249 tristate "G400 second head support"
1250 depends on FB_MATROX_G && FB_MATROX_I2C
1252 WARNING !!! This support does not work with G450 !!!
1254 Say Y or M here if you want to use a secondary head (meaning two
1255 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1256 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1257 secondary head output is blanked while you are in X. With XFree
1258 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1259 the fbdev driver on first head and the fbdev driver on second head.
1261 If you compile it as module, two modules are created,
1262 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1263 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1264 also load i2c-matroxfb to get it to run.
1266 The driver starts in monitor mode and you must use the matroxset
1268 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1269 PAL or NTSC or to swap primary and secondary head outputs.
1270 Secondary head driver also always start in 640x480 resolution, you
1271 must use fbset to change it.
1273 Also do not forget that second head supports only 16 and 32 bpp
1274 packed pixels, so it is a good idea to compile them into the kernel
1275 too. You can use only some font widths, as the driver uses generic
1276 painting procedures (the secondary head does not use acceleration
1279 config FB_MATROX_MULTIHEAD
1280 bool "Multihead support"
1281 depends on FB_MATROX
1283 Say Y here if you have more than one (supported) Matrox device in
1284 your computer and you want to use all of them for different monitors
1285 ("multihead"). If you have only one device, you should say N because
1286 the driver compiled with Y is larger and a bit slower, especially on
1289 If you said M to "Matrox unified accelerated driver" and N here, you
1290 will still be able to use several Matrox devices simultaneously:
1291 insert several instances of the module matroxfb into the kernel
1292 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1293 for the different Matrox devices. This method is slightly faster but
1294 uses 40 KB of kernel memory per Matrox card.
1296 There is no need for enabling 'Matrox multihead support' if you have
1297 only one Matrox card in the box.
1300 tristate "ATI Radeon display support"
1301 depends on FB && PCI
1302 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1303 select FB_MODE_HELPERS
1304 select FB_CFB_FILLRECT
1305 select FB_CFB_COPYAREA
1306 select FB_CFB_IMAGEBLIT
1307 select FB_MACMODES if PPC_OF
1309 Choose this option if you want to use an ATI Radeon graphics card as
1310 a framebuffer device. There are both PCI and AGP versions. You
1311 don't need to choose this to run the Radeon in plain VGA mode.
1313 If you say Y here and want DDC/I2C support you must first say Y to
1314 "I2C support" and "I2C bit-banging support" in the character devices
1317 If you say M here then "I2C support" and "I2C bit-banging support"
1318 can be build either as modules or built-in.
1320 There is a product page at
1321 http://apps.ati.com/ATIcompare/
1323 config FB_RADEON_I2C
1324 bool "DDC/I2C for ATI Radeon support"
1325 depends on FB_RADEON
1329 Say Y here if you want DDC/I2C support for your Radeon board.
1331 config FB_RADEON_BACKLIGHT
1332 bool "Support for backlight control"
1333 depends on FB_RADEON
1336 Say Y here if you want to control the backlight of your display.
1338 config FB_RADEON_DEBUG
1339 bool "Lots of debug output from Radeon driver"
1340 depends on FB_RADEON
1343 Say Y here if you want the Radeon driver to output all sorts
1344 of debugging information to provide to the maintainer when
1345 something goes wrong.
1348 tristate "ATI Rage128 display support"
1349 depends on FB && PCI
1350 select FB_CFB_FILLRECT
1351 select FB_CFB_COPYAREA
1352 select FB_CFB_IMAGEBLIT
1353 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1354 select FB_MACMODES if PPC_PMAC
1356 This driver supports graphics boards with the ATI Rage128 chips.
1357 Say Y if you have such a graphics board and read
1358 <file:Documentation/fb/aty128fb.txt>.
1360 To compile this driver as a module, choose M here: the
1361 module will be called aty128fb.
1363 config FB_ATY128_BACKLIGHT
1364 bool "Support for backlight control"
1365 depends on FB_ATY128
1368 Say Y here if you want to control the backlight of your display.
1371 tristate "ATI Mach64 display support" if PCI || ATARI
1372 depends on FB && !SPARC32
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1376 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1377 select FB_MACMODES if PPC
1379 This driver supports graphics boards with the ATI Mach64 chips.
1380 Say Y if you have such a graphics board.
1382 To compile this driver as a module, choose M here: the
1383 module will be called atyfb.
1386 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1387 depends on PCI && FB_ATY
1388 default y if SPARC64 && PCI
1390 Say Y here to support use of ATI's 64-bit Rage boards (or other
1391 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1392 framebuffer device. The ATI product support page for these boards
1393 is at <http://support.ati.com/products/pc/mach64/>.
1395 config FB_ATY_GENERIC_LCD
1396 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1397 depends on FB_ATY_CT
1399 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1400 Rage XC, or Rage XL chipset.
1403 bool "Mach64 GX support" if PCI
1407 Say Y here to support use of the ATI Mach64 Graphics Expression
1408 board (or other boards based on the Mach64 GX chipset) as a
1409 framebuffer device. The ATI product support page for these boards
1411 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1413 config FB_ATY_BACKLIGHT
1414 bool "Support for backlight control"
1418 Say Y here if you want to control the backlight of your display.
1421 tristate "S3 Trio/Virge support"
1422 depends on FB && PCI
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1426 select FB_TILEBLITTING
1429 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1431 Driver for graphics boards with S3 Trio / S3 Virge chip.
1434 tristate "S3 Savage support"
1435 depends on FB && PCI && EXPERIMENTAL
1436 select FB_MODE_HELPERS
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1439 select FB_CFB_IMAGEBLIT
1442 This driver supports notebooks and computers with S3 Savage PCI/AGP
1445 Say Y if you have such a graphics card.
1447 To compile this driver as a module, choose M here; the module
1448 will be called savagefb.
1450 config FB_SAVAGE_I2C
1451 bool "Enable DDC2 Support"
1452 depends on FB_SAVAGE
1455 This enables I2C support for S3 Savage Chipsets. This is used
1456 only for getting EDID information from the attached display
1457 allowing for robust video mode handling and switching.
1459 Because fbdev-2.6 requires that drivers must be able to
1460 independently validate video mode parameters, you should say Y
1463 config FB_SAVAGE_ACCEL
1464 bool "Enable Console Acceleration"
1465 depends on FB_SAVAGE
1468 This option will compile in console acceleration support. If
1469 the resulting framebuffer console has bothersome glitches, then
1473 tristate "SiS/XGI display support"
1474 depends on FB && PCI
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1479 This is the frame buffer device driver for the SiS 300, 315, 330
1480 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1481 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1483 To compile this driver as a module, choose M here; the module
1484 will be called sisfb.
1487 bool "SiS 300 series support"
1490 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1493 bool "SiS 315/330/340 series and XGI support"
1496 Say Y here to support use of the SiS 315, 330 and 340 series
1497 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1498 as XGI V3XT, V5, V8 and Z7.
1501 tristate "NeoMagic display support"
1502 depends on FB && PCI
1503 select FB_MODE_HELPERS
1504 select FB_CFB_FILLRECT
1505 select FB_CFB_COPYAREA
1506 select FB_CFB_IMAGEBLIT
1509 This driver supports notebooks with NeoMagic PCI chips.
1510 Say Y if you have such a graphics card.
1512 To compile this driver as a module, choose M here: the
1513 module will be called neofb.
1516 tristate "IMG Kyro support"
1517 depends on FB && PCI
1518 select FB_CFB_FILLRECT
1519 select FB_CFB_COPYAREA
1520 select FB_CFB_IMAGEBLIT
1522 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1525 To compile this driver as a module, choose M here: the
1526 module will be called kyrofb.
1529 tristate "3Dfx Banshee/Voodoo3 display support"
1530 depends on FB && PCI
1531 select FB_CFB_IMAGEBLIT
1532 select FB_CFB_FILLRECT
1533 select FB_CFB_COPYAREA
1535 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1536 chips. Say Y if you have such a graphics board.
1538 To compile this driver as a module, choose M here: the
1539 module will be called tdfxfb.
1541 config FB_3DFX_ACCEL
1542 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1543 depends on FB_3DFX && EXPERIMENTAL
1545 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1546 with acceleration functions.
1550 tristate "3Dfx Voodoo Graphics (sst1) support"
1551 depends on FB && PCI
1552 select FB_CFB_FILLRECT
1553 select FB_CFB_COPYAREA
1554 select FB_CFB_IMAGEBLIT
1556 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1557 Voodoo2 (cvg) based graphics card.
1559 To compile this driver as a module, choose M here: the
1560 module will be called sstfb.
1562 WARNING: Do not use any application that uses the 3D engine
1563 (namely glide) while using this driver.
1564 Please read the <file:Documentation/fb/sstfb.txt> for supported
1565 options and other important info support.
1568 tristate "VIA VT8623 support"
1569 depends on FB && PCI
1570 select FB_CFB_FILLRECT
1571 select FB_CFB_COPYAREA
1572 select FB_CFB_IMAGEBLIT
1573 select FB_TILEBLITTING
1576 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1578 Driver for CastleRock integrated graphics core in the
1579 VIA VT8623 [Apollo CLE266] chipset.
1582 tristate "Cyberblade/i1 support"
1583 depends on FB && PCI && X86_32 && !64BIT
1584 select FB_CFB_IMAGEBLIT
1586 This driver is supposed to support the Trident Cyberblade/i1
1587 graphics core integrated in the VIA VT8601A North Bridge,
1588 also known as VIA Apollo PLE133.
1591 - Developed, tested and working on EPIA 5000 and EPIA 800.
1592 - Does work reliable on all systems with CRT/LCD connected to
1594 - Should work on systems that do use the internal LCD port, but
1595 this is absolutely not tested.
1597 Character imageblit, copyarea and rectangle fill are hw accelerated,
1598 ypan scrolling is used by default.
1600 Please do read <file:Documentation/fb/cyblafb/*>.
1602 To compile this driver as a module, choose M here: the
1603 module will be called cyblafb.
1606 tristate "Trident support"
1607 depends on FB && PCI
1608 select FB_CFB_FILLRECT
1609 select FB_CFB_COPYAREA
1610 select FB_CFB_IMAGEBLIT
1612 This driver is supposed to support graphics boards with the
1613 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1614 but also on some motherboards. For more information, read
1615 <file:Documentation/fb/tridentfb.txt>
1617 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1620 Say Y if you have such a graphics board.
1623 To compile this driver as a module, choose M here: the
1624 module will be called tridentfb.
1626 config FB_TRIDENT_ACCEL
1627 bool "Trident Acceleration functions (EXPERIMENTAL)"
1628 depends on FB_TRIDENT && EXPERIMENTAL
1630 This will compile the Trident frame buffer device with
1631 acceleration functions.
1634 tristate "ARK 2000PV support"
1635 depends on FB && PCI
1636 select FB_CFB_FILLRECT
1637 select FB_CFB_COPYAREA
1638 select FB_CFB_IMAGEBLIT
1639 select FB_TILEBLITTING
1642 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1644 Driver for PCI graphics boards with ARK 2000PV chip
1645 and ICS 5342 RAMDAC.
1648 tristate "Permedia3 support (EXPERIMENTAL)"
1649 depends on FB && PCI && EXPERIMENTAL
1650 select FB_CFB_FILLRECT
1651 select FB_CFB_COPYAREA
1652 select FB_CFB_IMAGEBLIT
1654 This is the frame buffer device driver for the 3DLabs Permedia3
1655 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1656 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1657 and maybe other boards.
1660 bool "Au1100 LCD Driver"
1661 depends on (FB = y) && MIPS && SOC_AU1100
1662 select FB_CFB_FILLRECT
1663 select FB_CFB_COPYAREA
1664 select FB_CFB_IMAGEBLIT
1666 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1667 various panels and CRTs by passing in kernel cmd line option
1668 au1100fb:panel=<name>.
1671 bool "Au1200 LCD Driver"
1672 depends on (FB = y) && MIPS && SOC_AU1200
1673 select FB_CFB_FILLRECT
1674 select FB_CFB_COPYAREA
1675 select FB_CFB_IMAGEBLIT
1677 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1678 various panels and CRTs by passing in kernel cmd line option
1679 au1200fb:panel=<name>.
1681 source "drivers/video/geode/Kconfig"
1684 tristate "HD64461 Frame Buffer support"
1685 depends on FB && HD64461
1686 select FB_CFB_FILLRECT
1687 select FB_CFB_COPYAREA
1688 select FB_CFB_IMAGEBLIT
1690 This is the frame buffer device driver for the Hitachi HD64461 LCD
1694 bool "PMAG-AA TURBOchannel framebuffer support"
1695 depends on (FB = y) && TC
1696 select FB_CFB_FILLRECT
1697 select FB_CFB_COPYAREA
1698 select FB_CFB_IMAGEBLIT
1700 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1701 used mainly in the MIPS-based DECstation series.
1704 tristate "PMAG-BA TURBOchannel framebuffer support"
1706 select FB_CFB_FILLRECT
1707 select FB_CFB_COPYAREA
1708 select FB_CFB_IMAGEBLIT
1710 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1711 used mainly in the MIPS-based DECstation series.
1714 tristate "PMAGB-B TURBOchannel framebuffer support"
1716 select FB_CFB_FILLRECT
1717 select FB_CFB_COPYAREA
1718 select FB_CFB_IMAGEBLIT
1720 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1721 in the MIPS-based DECstation series. The card is currently only
1722 supported in 1280x1024x8 mode.
1725 bool "Maxine (Personal DECstation) onboard framebuffer support"
1726 depends on (FB = y) && MACH_DECSTATION
1727 select FB_CFB_FILLRECT
1728 select FB_CFB_COPYAREA
1729 select FB_CFB_IMAGEBLIT
1731 Support for the onboard framebuffer (1024x768x8) in the Personal
1732 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1736 bool "G364 frame buffer support"
1737 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1738 select FB_CFB_FILLRECT
1739 select FB_CFB_COPYAREA
1740 select FB_CFB_IMAGEBLIT
1742 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1743 Olivetti M700-10 systems.
1746 bool "Motorola 68328 native frame buffer support"
1747 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1748 select FB_CFB_FILLRECT
1749 select FB_CFB_COPYAREA
1750 select FB_CFB_IMAGEBLIT
1752 Say Y here if you want to support the built-in frame buffer of
1753 the Motorola 68328 CPU family.
1756 tristate "PXA LCD framebuffer support"
1757 depends on FB && ARCH_PXA
1758 select FB_CFB_FILLRECT
1759 select FB_CFB_COPYAREA
1760 select FB_CFB_IMAGEBLIT
1762 Frame buffer driver for the built-in LCD controller in the Intel
1765 This driver is also available as a module ( = code which can be
1766 inserted and removed from the running kernel whenever you want). The
1767 module will be called pxafb. If you want to compile it as a module,
1768 say M here and read <file:Documentation/kbuild/modules.txt>.
1772 config FB_PXA_SMARTPANEL
1773 bool "PXA Smartpanel LCD support"
1777 config FB_PXA_PARAMETERS
1778 bool "PXA LCD command line parameters"
1782 Enable the use of kernel command line or module parameters
1783 to configure the physical properties of the LCD panel when
1784 using the PXA LCD driver.
1786 This option allows you to override the panel parameters
1787 supplied by the platform in order to support multiple
1788 different models of flatpanel. If you will only be using a
1789 single model of flatpanel then you can safely leave this
1792 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1795 tristate "2700G LCD framebuffer support"
1796 depends on FB && ARCH_PXA
1797 select FB_CFB_FILLRECT
1798 select FB_CFB_COPYAREA
1799 select FB_CFB_IMAGEBLIT
1801 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1805 bool "Enable debugging info via debugfs"
1806 depends on FB_MBX && DEBUG_FS
1809 Enable this if you want debugging information using the debug
1810 filesystem (debugfs)
1815 tristate "Freescale DIU framebuffer support"
1816 depends on FB && FSL_SOC
1817 select FB_CFB_FILLRECT
1818 select FB_CFB_COPYAREA
1819 select FB_CFB_IMAGEBLIT
1820 select PPC_LIB_RHEAP
1822 Framebuffer driver for the Freescale SoC DIU
1825 tristate "W100 frame buffer support"
1826 depends on FB && ARCH_PXA
1827 select FB_CFB_FILLRECT
1828 select FB_CFB_COPYAREA
1829 select FB_CFB_IMAGEBLIT
1831 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1832 It can also drive the w3220 chip found on iPAQ hx4700.
1834 This driver is also available as a module ( = code which can be
1835 inserted and removed from the running kernel whenever you want). The
1836 module will be called w100fb. If you want to compile it as a module,
1837 say M here and read <file:Documentation/kbuild/modules.txt>.
1842 tristate "S3C2410 LCD framebuffer support"
1843 depends on FB && ARCH_S3C2410
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 Frame buffer driver for the built-in LCD controller in the Samsung
1851 This driver is also available as a module ( = code which can be
1852 inserted and removed from the running kernel whenever you want). The
1853 module will be called s3c2410fb. If you want to compile it as a module,
1854 say M here and read <file:Documentation/kbuild/modules.txt>.
1857 config FB_S3C2410_DEBUG
1858 bool "S3C2410 lcd debug messages"
1859 depends on FB_S3C2410
1861 Turn on debugging messages. Note that you can set/unset at run time
1865 tristate "Silicon Motion SM501 framebuffer support"
1866 depends on FB && MFD_SM501
1867 select FB_CFB_FILLRECT
1868 select FB_CFB_COPYAREA
1869 select FB_CFB_IMAGEBLIT
1871 Frame buffer driver for the CRT and LCD controllers in the Silicon
1874 This driver is also available as a module ( = code which can be
1875 inserted and removed from the running kernel whenever you want). The
1876 module will be called sm501fb. If you want to compile it as a module,
1877 say M here and read <file:Documentation/kbuild/modules.txt>.
1882 config FB_PNX4008_DUM
1883 tristate "Display Update Module support on Philips PNX4008 board"
1884 depends on FB && ARCH_PNX4008
1886 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1888 config FB_PNX4008_DUM_RGB
1889 tristate "RGB Framebuffer support on Philips PNX4008 board"
1890 depends on FB_PNX4008_DUM
1891 select FB_CFB_FILLRECT
1892 select FB_CFB_COPYAREA
1893 select FB_CFB_IMAGEBLIT
1895 Say Y here to enable support for PNX4008 RGB Framebuffer
1897 config FB_IBM_GXT4500
1898 tristate "Framebuffer support for IBM GXT4500P adaptor"
1899 depends on FB && PPC
1900 select FB_CFB_FILLRECT
1901 select FB_CFB_COPYAREA
1902 select FB_CFB_IMAGEBLIT
1904 Say Y here to enable support for the IBM GXT4500P display
1905 adaptor, found on some IBM System P (pSeries) machines.
1908 tristate "PS3 GPU framebuffer driver"
1909 depends on FB && PS3_PS3AV
1910 select FB_SYS_FILLRECT
1911 select FB_SYS_COPYAREA
1912 select FB_SYS_IMAGEBLIT
1914 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1916 Include support for the virtual frame buffer in the PS3 platform.
1918 config FB_PS3_DEFAULT_SIZE_M
1919 int "PS3 default frame buffer size (in MiB)"
1923 This is the default size (in MiB) of the virtual frame buffer in
1925 The default value can be overridden on the kernel command line
1926 using the "ps3fb" option (e.g. "ps3fb=9M");
1929 tristate "Xilinx frame buffer support"
1930 depends on FB && XILINX_VIRTEX
1931 select FB_CFB_FILLRECT
1932 select FB_CFB_COPYAREA
1933 select FB_CFB_IMAGEBLIT
1935 Include support for the Xilinx ML300/ML403 reference design
1936 framebuffer. ML300 carries a 640*480 LCD display on the board,
1937 ML403 uses a standard DB15 VGA connector.
1940 tristate "AM-200 E-Ink EPD devkit support"
1941 depends on FB && ARCH_PXA && MMU
1942 select FB_SYS_FILLRECT
1943 select FB_SYS_COPYAREA
1944 select FB_SYS_IMAGEBLIT
1946 select FB_DEFERRED_IO
1949 This enables support for the Metronome display controller used on
1950 the E-Ink AM-200 EPD devkit.
1953 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1955 select FB_SYS_FILLRECT
1956 select FB_SYS_COPYAREA
1957 select FB_SYS_IMAGEBLIT
1960 This is a `virtual' frame buffer device. It operates on a chunk of
1961 unswappable kernel memory instead of on the memory of a graphics
1962 board. This means you cannot see any output sent to this frame
1963 buffer device, while it does consume precious memory. The main use
1964 of this frame buffer device is testing and debugging the frame
1965 buffer subsystem. Do NOT enable it for normal systems! To protect
1966 the innocent, it has to be enabled explicitly at boot time using the
1967 kernel option `video=vfb:'.
1969 To compile this driver as a module, choose M here: the
1970 module will be called vfb. In order to load it, you must use
1971 the vfb_enable=1 option.
1975 config XEN_FBDEV_FRONTEND
1976 tristate "Xen virtual frame buffer support"
1977 depends on FB && XEN
1978 select FB_SYS_FILLRECT
1979 select FB_SYS_COPYAREA
1980 select FB_SYS_IMAGEBLIT
1982 select FB_DEFERRED_IO
1985 This driver implements the front-end of the Xen virtual
1986 frame buffer driver. It communicates with a back-end
1989 source "drivers/video/omap/Kconfig"
1991 source "drivers/video/backlight/Kconfig"
1992 source "drivers/video/display/Kconfig"
1995 source "drivers/video/console/Kconfig"
1998 if FB || SGI_NEWPORT_CONSOLE
1999 source "drivers/video/logo/Kconfig"