5 menu "Graphics support"
11 source "drivers/char/agp/Kconfig"
13 source "drivers/gpu/vga/Kconfig"
15 source "drivers/gpu/drm/Kconfig"
21 config VIDEO_OUTPUT_CONTROL
22 tristate "Lowlevel video output switch controls"
24 This framework adds support for low-level control of the video
28 tristate "Support for frame buffer devices"
30 The frame buffer device provides an abstraction for the graphics
31 hardware. It represents the frame buffer of some video hardware and
32 allows application software to access the graphics hardware through
33 a well-defined interface, so the software doesn't need to know
34 anything about the low-level (hardware register) stuff.
36 Frame buffer devices work identically across the different
37 architectures supported by Linux and make the implementation of
38 application programs easier and more portable; at this point, an X
39 server exists which uses the frame buffer device exclusively.
40 On several non-X86 architectures, the frame buffer device is the
41 only way to use the graphics hardware.
43 The device is accessed through special device nodes, usually located
44 in the /dev directory, i.e. /dev/fb*.
46 You need an utility program called fbset to make full use of frame
47 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
48 and the Framebuffer-HOWTO at
49 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more
52 Say Y here and to the driver for your graphics board below if you
53 are compiling a kernel for a non-x86 architecture.
55 If you are compiling for the x86 architecture, you can say Y if you
56 want to play with it, but it is not essential. Please note that
57 running graphical applications that directly touch the hardware
58 (e.g. an accelerated X server) and that are not frame buffer
59 device-aware may cause unexpected results. If unsure, say N.
62 bool "Enable firmware EDID"
66 This enables access to the EDID transferred from the firmware.
67 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
68 transfers do not work for your driver and if you are using
69 nvidiafb, i810fb or savagefb.
71 In general, choosing Y for this option is safe. If you
72 experience extremely long delays while booting before you get
73 something on your display, try setting this to N. Matrox cards in
74 combination with certain motherboards and monitors are known to
75 suffer from this problem.
84 config FB_BOOT_VESA_SUPPORT
89 If true, at least one selected framebuffer driver can take advantage
90 of VESA video modes set at an early boot stage via the vga= parameter.
92 config FB_CFB_FILLRECT
97 Include the cfb_fillrect function for generic software rectangle
98 filling. This is used by drivers that don't provide their own
99 (accelerated) version.
101 config FB_CFB_COPYAREA
106 Include the cfb_copyarea function for generic software area copying.
107 This is used by drivers that don't provide their own (accelerated)
110 config FB_CFB_IMAGEBLIT
115 Include the cfb_imageblit function for generic software image
116 blitting. This is used by drivers that don't provide their own
117 (accelerated) version.
119 config FB_CFB_REV_PIXELS_IN_BYTE
124 Allow generic frame-buffer functions to work on displays with 1, 2
125 and 4 bits per pixel depths which has opposite order of pixels in
126 byte order to bytes in long order.
128 config FB_SYS_FILLRECT
133 Include the sys_fillrect function for generic software rectangle
134 filling. This is used by drivers that don't provide their own
135 (accelerated) version and the framebuffer is in system RAM.
137 config FB_SYS_COPYAREA
142 Include the sys_copyarea function for generic software area copying.
143 This is used by drivers that don't provide their own (accelerated)
144 version and the framebuffer is in system RAM.
146 config FB_SYS_IMAGEBLIT
151 Include the sys_imageblit function for generic software image
152 blitting. This is used by drivers that don't provide their own
153 (accelerated) version and the framebuffer is in system RAM.
155 menuconfig FB_FOREIGN_ENDIAN
156 bool "Framebuffer foreign endianness support"
159 This menu will let you enable support for the framebuffers with
160 non-native endianness (e.g. Little-Endian framebuffer on a
161 Big-Endian machine). Most probably you don't have such hardware,
162 so it's safe to say "n" here.
165 prompt "Choice endianness support"
166 depends on FB_FOREIGN_ENDIAN
168 config FB_BOTH_ENDIAN
169 bool "Support for Big- and Little-Endian framebuffers"
172 bool "Support for Big-Endian framebuffers only"
174 config FB_LITTLE_ENDIAN
175 bool "Support for Little-Endian framebuffers only"
184 config FB_DEFERRED_IO
191 depends on FB_DEFERRED_IO
198 Common utility functions useful to fbdev drivers of VGA-based
209 select BACKLIGHT_LCD_SUPPORT
210 select BACKLIGHT_CLASS_DEVICE
213 config FB_MODE_HELPERS
214 bool "Enable Video Mode Handling Helpers"
218 This enables functions for handling video modes using the
219 Generalized Timing Formula and the EDID parser. A few drivers rely
220 on this feature such as the radeonfb, rivafb, and the i810fb. If
221 your driver does not take advantage of this feature, choosing Y will
222 just increase the kernel size by about 5K.
224 config FB_TILEBLITTING
225 bool "Enable Tile Blitting Support"
229 This enables tile blitting. Tile blitting is a drawing technique
230 where the screen is divided into rectangular sections (tiles), whereas
231 the standard blitting divides the screen into pixels. Because the
232 default drawing element is a tile, drawing functions will be passed
233 parameters in terms of number of tiles instead of number of pixels.
234 For example, to draw a single character, instead of using bitmaps,
235 an index to an array of bitmaps will be used. To clear or move a
236 rectangular section of a screen, the rectangle will be described in
237 terms of number of tiles in the x- and y-axis.
239 This is particularly important to one driver, matroxfb. If
242 comment "Frame buffer hardware drivers"
246 tristate "Cirrus Logic support"
247 depends on FB && (ZORRO || PCI)
248 select FB_CFB_FILLRECT
249 select FB_CFB_COPYAREA
250 select FB_CFB_IMAGEBLIT
252 This enables support for Cirrus Logic GD542x/543x based boards on
253 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
255 If you have a PCI-based system, this enables support for these
256 chips: GD-543x, GD-544x, GD-5480.
258 Please read the file <file:Documentation/fb/cirrusfb.txt>.
260 Say N unless you have such a graphics board or plan to get one
261 before you next recompile the kernel.
264 tristate "Permedia2 support"
265 depends on FB && ((AMIGA && BROKEN) || PCI)
266 select FB_CFB_FILLRECT
267 select FB_CFB_COPYAREA
268 select FB_CFB_IMAGEBLIT
270 This is the frame buffer device driver for cards based on
271 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
272 The driver was tested on the following cards:
273 Diamond FireGL 1000 PRO AGP
274 ELSA Gloria Synergy PCI
275 Appian Jeronimo PRO (both heads) PCI
276 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
277 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
278 ASK Graphic Blaster Exxtreme AGP
280 To compile this driver as a module, choose M here: the
281 module will be called pm2fb.
283 config FB_PM2_FIFO_DISCONNECT
284 bool "enable FIFO disconnect feature"
285 depends on FB_PM2 && PCI
287 Support the Permedia2 FIFO disconnect feature.
290 tristate "ARM PrimeCell PL110 support"
291 depends on FB && ARM && ARM_AMBA
292 select FB_CFB_FILLRECT
293 select FB_CFB_COPYAREA
294 select FB_CFB_IMAGEBLIT
296 This framebuffer device driver is for the ARM PrimeCell PL110
297 Colour LCD controller. ARM PrimeCells provide the building
298 blocks for System on a Chip devices.
300 If you want to compile this as a module (=code which can be
301 inserted into and removed from the running kernel), say M
302 here and read <file:Documentation/kbuild/modules.txt>. The module
303 will be called amba-clcd.
307 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
309 default FB_ARMCLCD_SHARP_LQ035Q7DB02
311 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
312 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
314 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
315 color QVGA, HRTFT panel. The LogicPD device includes
316 an integrated HRTFT controller IC.
317 The native resolution is 240x320.
319 config FB_ARMCLCD_SHARP_LQ057Q3DC02
320 bool "LogicPD LCD 5.7\" QVGA"
322 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
323 color QVGA, TFT panel. The LogicPD device includes an
324 The native resolution is 320x240.
326 config FB_ARMCLCD_SHARP_LQ64D343
327 bool "LogicPD LCD 6.4\" VGA"
329 This is an implementation of the Sharp LQ64D343, a 6.4"
330 color VGA, TFT panel. The LogicPD device includes an
331 The native resolution is 640x480.
333 config FB_ARMCLCD_SHARP_LQ10D368
334 bool "LogicPD LCD 10.4\" VGA"
336 This is an implementation of the Sharp LQ10D368, a 10.4"
337 color VGA, TFT panel. The LogicPD device includes an
338 The native resolution is 640x480.
341 config FB_ARMCLCD_SHARP_LQ121S1DG41
342 bool "LogicPD LCD 12.1\" SVGA"
344 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
345 color SVGA, TFT panel. The LogicPD device includes an
346 The native resolution is 800x600.
348 This panel requires a clock rate may be an integer fraction
349 of the base LCDCLK frequency. The driver will select the
350 highest frequency available that is lower than the maximum
351 allowed. The panel may flicker if the clock rate is
352 slower than the recommended minimum.
354 config FB_ARMCLCD_AUO_A070VW01_WIDE
355 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
357 This is an implementation of the AU Optronics, a 7.0"
358 WIDE Color. The native resolution is 234x480.
360 config FB_ARMCLCD_HITACHI
361 bool "Hitachi Wide Screen 800x480"
363 This is an implementation of the Hitachi 800x480.
369 bool "Acorn VIDC support"
370 depends on (FB = y) && ARM && ARCH_ACORN
371 select FB_CFB_FILLRECT
372 select FB_CFB_COPYAREA
373 select FB_CFB_IMAGEBLIT
375 This is the frame buffer device driver for the Acorn VIDC graphics
376 hardware found in Acorn RISC PCs and other ARM-based machines. If
380 bool "CLPS711X LCD support"
381 depends on (FB = y) && ARM && ARCH_CLPS711X
382 select FB_CFB_FILLRECT
383 select FB_CFB_COPYAREA
384 select FB_CFB_IMAGEBLIT
386 Say Y to enable the Framebuffer driver for the CLPS7111 and
390 bool "SA-1100 LCD support"
391 depends on (FB = y) && ARM && ARCH_SA1100
392 select FB_CFB_FILLRECT
393 select FB_CFB_COPYAREA
394 select FB_CFB_IMAGEBLIT
396 This is a framebuffer device for the SA-1100 LCD Controller.
397 See <http://www.linux-fbdev.org/> for information on framebuffer
400 If you plan to use the LCD display with your SA-1100 system, say
404 tristate "Motorola i.MX LCD support"
405 depends on FB && (ARCH_MX1 || ARCH_MX2)
406 select FB_CFB_FILLRECT
407 select FB_CFB_COPYAREA
408 select FB_CFB_IMAGEBLIT
411 tristate "CyberPro 2000/2010/5000 support"
412 depends on FB && PCI && (BROKEN || !SPARC64)
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
417 This enables support for the Integraphics CyberPro 20x0 and 5000
418 VGA chips used in the Rebel.com Netwinder and other machines.
419 Say Y if you have a NetWinder or a graphics card containing this
420 device, otherwise say N.
424 depends on (FB = y) && APOLLO
426 select FB_CFB_FILLRECT
427 select FB_CFB_IMAGEBLIT
431 depends on (FB = y) && Q40
433 select FB_CFB_FILLRECT
434 select FB_CFB_COPYAREA
435 select FB_CFB_IMAGEBLIT
438 tristate "Amiga native chipset support"
439 depends on FB && AMIGA
441 This is the frame buffer device driver for the builtin graphics
442 chipset found in Amigas.
444 To compile this driver as a module, choose M here: the
445 module will be called amifb.
448 bool "Amiga OCS chipset support"
451 This enables support for the original Agnus and Denise video chips,
452 found in the Amiga 1000 and most A500's and A2000's. If you intend
453 to run Linux on any of these systems, say Y; otherwise say N.
456 bool "Amiga ECS chipset support"
459 This enables support for the Enhanced Chip Set, found in later
460 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
461 you intend to run Linux on any of these systems, say Y; otherwise
465 bool "Amiga AGA chipset support"
468 This enables support for the Advanced Graphics Architecture (also
469 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
470 and CD32. If you intend to run Linux on any of these systems, say Y;
474 bool "Amiga FrameMaster II/Rainbow II support"
475 depends on (FB = y) && ZORRO
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
480 This is the frame buffer device driver for the Amiga FrameMaster
481 card from BSC (exhibited 1992 but not shipped as a CBM product).
484 tristate "Arc Monochrome LCD board support"
486 select FB_SYS_FILLRECT
487 select FB_SYS_COPYAREA
488 select FB_SYS_IMAGEBLIT
491 This enables support for the Arc Monochrome LCD board. The board
492 is based on the KS-108 lcd controller and is typically a matrix
493 of 2*n chips. This driver was tested with a 128x64 panel. This
494 driver supports it for use with x86 SBCs through a 16 bit GPIO
495 interface (8 bit data, 8 bit control). If you anticipate using
496 this driver, say Y or M; otherwise say N. You must specify the
497 GPIO IO address to be used for setting control and data.
500 bool "Atari native chipset support"
501 depends on (FB = y) && ATARI
502 select FB_CFB_FILLRECT
503 select FB_CFB_COPYAREA
504 select FB_CFB_IMAGEBLIT
506 This is the frame buffer device driver for the builtin graphics
507 chipset found in Ataris.
510 bool "Open Firmware frame buffer device support"
511 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
512 select FB_CFB_FILLRECT
513 select FB_CFB_COPYAREA
514 select FB_CFB_IMAGEBLIT
517 Say Y if you want support with Open Firmware for your graphics
521 bool "Apple \"control\" display support"
522 depends on (FB = y) && PPC_PMAC && PPC32
523 select FB_CFB_FILLRECT
524 select FB_CFB_COPYAREA
525 select FB_CFB_IMAGEBLIT
528 This driver supports a frame buffer for the graphics adapter in the
529 Power Macintosh 7300 and others.
532 bool "Apple \"platinum\" display support"
533 depends on (FB = y) && PPC_PMAC && PPC32
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
539 This driver supports a frame buffer for the "platinum" graphics
540 adapter in some Power Macintoshes.
543 bool "Apple \"valkyrie\" display support"
544 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
550 This driver supports a frame buffer for the "valkyrie" graphics
551 adapter in some Power Macintoshes.
554 bool "Chips 65550 display support"
555 depends on (FB = y) && PPC32 && PCI
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 This is the frame buffer device driver for the Chips & Technologies
561 65550 graphics chip in PowerBooks.
564 bool "Asiliant (Chips) 69000 display support"
565 depends on (FB = y) && PCI
566 select FB_CFB_FILLRECT
567 select FB_CFB_COPYAREA
568 select FB_CFB_IMAGEBLIT
570 This is the frame buffer device driver for the Asiliant 69030 chipset
573 bool "IMS Twin Turbo display support"
574 depends on (FB = y) && PCI
575 select FB_CFB_IMAGEBLIT
576 select FB_MACMODES if PPC
578 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
579 many Macintosh and compatible computers.
582 tristate "VGA 16-color graphics support"
583 depends on FB && (X86 || PPC)
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
588 select FONT_8x16 if FRAMEBUFFER_CONSOLE
590 This is the frame buffer device driver for VGA 16 color graphic
591 cards. Say Y if you have such a card.
593 To compile this driver as a module, choose M here: the
594 module will be called vga16fb.
596 config FB_BF54X_LQ043
597 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
598 depends on FB && (BF54x) && !BF542
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
603 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
605 config FB_BFIN_T350MCQB
606 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
607 depends on FB && BLACKFIN
609 select FB_CFB_FILLRECT
610 select FB_CFB_COPYAREA
611 select FB_CFB_IMAGEBLIT
613 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
614 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
615 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
617 config FB_BFIN_LQ035Q1
618 tristate "SHARP LQ035Q1DH02 TFT LCD"
619 depends on FB && BLACKFIN && SPI
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
625 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
626 the Blackfin Landscape LCD EZ-Extender Card.
627 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
628 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
630 To compile this driver as a module, choose M here: the
631 module will be called bfin-lq035q1-fb.
634 tristate "HP STI frame buffer device support"
635 depends on FB && PARISC
636 select FB_CFB_FILLRECT
637 select FB_CFB_COPYAREA
638 select FB_CFB_IMAGEBLIT
643 STI refers to the HP "Standard Text Interface" which is a set of
644 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
645 Enabling this option will implement the linux framebuffer device
646 using calls to the STI BIOS routines for initialisation.
648 If you enable this option, you will get a planar framebuffer device
649 /dev/fb which will work on the most common HP graphic cards of the
650 NGLE family, including the artist chips (in the 7xx and Bxxx series),
651 HCRX, HCRX24, CRX, CRX24 and VisEG series.
653 It is safe to enable this option, so you should probably say "Y".
656 bool "Generic Macintosh display support"
657 depends on (FB = y) && MAC
658 select FB_CFB_FILLRECT
659 select FB_CFB_COPYAREA
660 select FB_CFB_IMAGEBLIT
665 depends on (FB = y) && DIO
666 select FB_CFB_IMAGEBLIT
670 tristate "TGA/SFB+ framebuffer support"
671 depends on FB && (ALPHA || TC)
672 select FB_CFB_FILLRECT
673 select FB_CFB_COPYAREA
674 select FB_CFB_IMAGEBLIT
677 This is the frame buffer device driver for generic TGA and SFB+
678 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
679 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
680 TURBOchannel cards, also known as PMAGD-A, -B and -C.
682 Due to hardware limitations ZLX-E2 and E3 cards are not supported
683 for DECstation 5000/200 systems. Additionally due to firmware
684 limitations these cards may cause troubles with booting DECstation
685 5000/240 and /260 systems, but are fully supported under Linux if
686 you manage to get it going. ;-)
688 Say Y if you have one of those.
691 tristate "Userspace VESA VGA graphics support"
692 depends on FB && CONNECTOR
693 select FB_CFB_FILLRECT
694 select FB_CFB_COPYAREA
695 select FB_CFB_IMAGEBLIT
696 select FB_MODE_HELPERS
698 This is the frame buffer driver for generic VBE 2.0 compliant
699 graphic cards. It can also take advantage of VBE 3.0 features,
700 such as refresh rate adjustment.
702 This driver generally provides more features than vesafb but
703 requires a userspace helper application called 'v86d'. See
704 <file:Documentation/fb/uvesafb.txt> for more information.
709 bool "VESA VGA graphics support"
710 depends on (FB = y) && X86
711 select FB_CFB_FILLRECT
712 select FB_CFB_COPYAREA
713 select FB_CFB_IMAGEBLIT
714 select FB_BOOT_VESA_SUPPORT
716 This is the frame buffer device driver for generic VESA 2.0
717 compliant graphic cards. The older VESA 1.2 cards are not supported.
718 You will get a boot time penguin logo at no additional cost. Please
719 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
722 bool "EFI-based Framebuffer Support"
723 depends on (FB = y) && X86 && EFI
724 select FB_CFB_FILLRECT
725 select FB_CFB_COPYAREA
726 select FB_CFB_IMAGEBLIT
728 This is the EFI frame buffer device driver. If the firmware on
729 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
730 using the EFI framebuffer as your console.
733 tristate "N411 Apollo/Hecuba devkit support"
734 depends on FB && X86 && MMU
735 select FB_SYS_FILLRECT
736 select FB_SYS_COPYAREA
737 select FB_SYS_IMAGEBLIT
739 select FB_DEFERRED_IO
742 This enables support for the Apollo display controller in its
743 Hecuba form using the n411 devkit.
746 tristate "Hercules mono graphics support"
748 select FB_CFB_FILLRECT
749 select FB_CFB_COPYAREA
750 select FB_CFB_IMAGEBLIT
752 Say Y here if you have a Hercules mono graphics card.
754 To compile this driver as a module, choose M here: the
755 module will be called hgafb.
757 As this card technology is 15 years old, most people will answer N
761 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
762 depends on FB_HGA && EXPERIMENTAL
764 This will compile the Hercules mono graphics with
765 acceleration functions.
768 tristate "SGI Visual Workstation framebuffer support"
769 depends on FB && X86_VISWS
770 select FB_CFB_FILLRECT
771 select FB_CFB_COPYAREA
772 select FB_CFB_IMAGEBLIT
774 SGI Visual Workstation support for framebuffer graphics.
777 bool "SGI Graphics Backend frame buffer support"
778 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
779 select FB_CFB_FILLRECT
780 select FB_CFB_COPYAREA
781 select FB_CFB_IMAGEBLIT
783 This is the frame buffer device driver for SGI Graphics Backend.
784 This chip is used in SGI O2 and Visual Workstation 320/540.
787 int "Video memory size in MB"
791 This is the amount of memory reserved for the framebuffer,
792 which can be any value between 1MB and 8MB.
795 bool "SBUS and UPA framebuffers"
796 depends on (FB = y) && SPARC
798 Say Y if you want support for SBUS or UPA based frame buffer device.
802 depends on (FB = y) && (SPARC && FB_SBUS)
803 select FB_CFB_FILLRECT
804 select FB_CFB_COPYAREA
805 select FB_CFB_IMAGEBLIT
807 This is the frame buffer device driver for the BWtwo frame buffer.
810 bool "CGthree support"
811 depends on (FB = y) && (SPARC && FB_SBUS)
812 select FB_CFB_FILLRECT
813 select FB_CFB_COPYAREA
814 select FB_CFB_IMAGEBLIT
816 This is the frame buffer device driver for the CGthree frame buffer.
819 bool "CGsix (GX,TurboGX) support"
820 depends on (FB = y) && (SPARC && FB_SBUS)
821 select FB_CFB_COPYAREA
822 select FB_CFB_IMAGEBLIT
824 This is the frame buffer device driver for the CGsix (GX, TurboGX)
828 bool "Creator/Creator3D/Elite3D support"
829 depends on FB_SBUS && SPARC64
830 select FB_CFB_COPYAREA
831 select FB_CFB_IMAGEBLIT
833 This is the frame buffer device driver for the Creator, Creator3D,
834 and Elite3D graphics boards.
837 bool "TCX (SS4/SS5 only) support"
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for the TCX 24/8bit frame
847 bool "CGfourteen (SX) support"
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
853 This is the frame buffer device driver for the CGfourteen frame
854 buffer on Desktop SPARCsystems with the SX graphics option.
857 bool "P9100 (Sparcbook 3 only) support"
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 This is the frame buffer device driver for the P9100 card
864 supported on Sparcbook 3 machines.
867 bool "Leo (ZX) support"
869 select FB_CFB_FILLRECT
870 select FB_CFB_COPYAREA
871 select FB_CFB_IMAGEBLIT
873 This is the frame buffer device driver for the SBUS-based Sun ZX
874 (leo) frame buffer cards.
877 bool "IGA 168x display support"
878 depends on (FB = y) && SPARC32
879 select FB_CFB_FILLRECT
880 select FB_CFB_COPYAREA
881 select FB_CFB_IMAGEBLIT
883 This is the framebuffer device for the INTERGRAPHICS 1680 and
884 successor frame buffer cards.
887 bool "Sun XVR-500 3DLABS Wildcat support"
888 depends on (FB = y) && PCI && SPARC64
889 select FB_CFB_FILLRECT
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This is the framebuffer device for the Sun XVR-500 and similar
894 graphics cards based upon the 3DLABS Wildcat chipset. The driver
895 only works on sparc64 systems where the system firmware has
896 mostly initialized the card already. It is treated as a
897 completely dumb framebuffer device.
900 bool "Sun XVR-2500 3DLABS Wildcat support"
901 depends on (FB = y) && PCI && SPARC64
902 select FB_CFB_FILLRECT
903 select FB_CFB_COPYAREA
904 select FB_CFB_IMAGEBLIT
906 This is the framebuffer device for the Sun XVR-2500 and similar
907 graphics cards based upon the 3DLABS Wildcat chipset. The driver
908 only works on sparc64 systems where the system firmware has
909 mostly initialized the card already. It is treated as a
910 completely dumb framebuffer device.
913 bool "Sun XVR-1000 support"
914 depends on (FB = y) && SPARC64
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the framebuffer device for the Sun XVR-1000 and similar
920 graphics cards. The driver only works on sparc64 systems where
921 the system firmware has mostly initialized the card already. It
922 is treated as a completely dumb framebuffer device.
925 tristate "NEC PowerVR 2 display support"
926 depends on FB && SH_DREAMCAST
927 select FB_CFB_FILLRECT
928 select FB_CFB_COPYAREA
929 select FB_CFB_IMAGEBLIT
931 Say Y here if you have a PowerVR 2 card in your box. If you plan to
932 run linux on your Dreamcast, you will have to say Y here.
933 This driver may or may not work on other PowerVR 2 cards, but is
934 totally untested. Use at your own risk. If unsure, say N.
936 To compile this driver as a module, choose M here: the
937 module will be called pvr2fb.
939 You can pass several parameters to the driver at boot time or at
940 module load time. The parameters look like "video=pvr2:XXX", where
941 the meaning of XXX can be found at the end of the main source file
942 (<file:drivers/video/pvr2fb.c>). Please see the file
943 <file:Documentation/fb/pvr2fb.txt>.
946 bool "Epson 1355 framebuffer support"
947 depends on (FB = y) && ARCH_CEIVA
948 select FB_CFB_FILLRECT
949 select FB_CFB_COPYAREA
950 select FB_CFB_IMAGEBLIT
952 Build in support for the SED1355 Epson Research Embedded RAMDAC
953 LCD/CRT Controller (since redesignated as the S1D13505) as a
954 framebuffer. Product specs at
955 <http://www.erd.epson.com/vdc/html/products.htm>.
958 tristate "Epson S1D13XXX framebuffer support"
960 select FB_CFB_FILLRECT
961 select FB_CFB_COPYAREA
962 select FB_CFB_IMAGEBLIT
964 Support for S1D13XXX framebuffer device family (currently only
965 working with S1D13806). Product specs at
966 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
969 tristate "AT91/AT32 LCD Controller support"
970 depends on FB && HAVE_FB_ATMEL
971 select FB_CFB_FILLRECT
972 select FB_CFB_COPYAREA
973 select FB_CFB_IMAGEBLIT
975 This enables support for the AT91/AT32 LCD Controller.
978 bool "Frame Buffer in internal SRAM"
979 depends on FB_ATMEL && ARCH_AT91SAM9261
981 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
982 to let frame buffer in external SDRAM.
985 bool "Use a STN display with AT91/AT32 LCD Controller"
986 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
989 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
990 Controller. Say N if you want to connect a TFT.
995 tristate "nVidia Framebuffer Support"
997 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
998 select FB_MODE_HELPERS
999 select FB_CFB_FILLRECT
1000 select FB_CFB_COPYAREA
1001 select FB_CFB_IMAGEBLIT
1005 This driver supports graphics boards with the nVidia chips, TNT
1006 and newer. For very old chipsets, such as the RIVA128, then use
1008 Say Y if you have such a graphics board.
1010 To compile this driver as a module, choose M here: the
1011 module will be called nvidiafb.
1013 config FB_NVIDIA_I2C
1014 bool "Enable DDC Support"
1015 depends on FB_NVIDIA
1018 This enables I2C support for nVidia Chipsets. This is used
1019 only for getting EDID information from the attached display
1020 allowing for robust video mode handling and switching.
1022 Because fbdev-2.6 requires that drivers must be able to
1023 independently validate video mode parameters, you should say Y
1026 config FB_NVIDIA_DEBUG
1027 bool "Lots of debug output"
1028 depends on FB_NVIDIA
1031 Say Y here if you want the nVidia driver to output all sorts
1032 of debugging information to provide to the maintainer when
1033 something goes wrong.
1035 config FB_NVIDIA_BACKLIGHT
1036 bool "Support for backlight control"
1037 depends on FB_NVIDIA
1040 Say Y here if you want to control the backlight of your display.
1043 tristate "nVidia Riva support"
1044 depends on FB && PCI
1045 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1046 select FB_MODE_HELPERS
1047 select FB_CFB_FILLRECT
1048 select FB_CFB_COPYAREA
1049 select FB_CFB_IMAGEBLIT
1053 This driver supports graphics boards with the nVidia Riva/Geforce
1055 Say Y if you have such a graphics board.
1057 To compile this driver as a module, choose M here: the
1058 module will be called rivafb.
1061 bool "Enable DDC Support"
1065 This enables I2C support for nVidia Chipsets. This is used
1066 only for getting EDID information from the attached display
1067 allowing for robust video mode handling and switching.
1069 Because fbdev-2.6 requires that drivers must be able to
1070 independently validate video mode parameters, you should say Y
1073 config FB_RIVA_DEBUG
1074 bool "Lots of debug output"
1078 Say Y here if you want the Riva driver to output all sorts
1079 of debugging information to provide to the maintainer when
1080 something goes wrong.
1082 config FB_RIVA_BACKLIGHT
1083 bool "Support for backlight control"
1087 Say Y here if you want to control the backlight of your display.
1090 tristate "Intel 810/815 support (EXPERIMENTAL)"
1091 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1092 select FB_MODE_HELPERS
1093 select FB_CFB_FILLRECT
1094 select FB_CFB_COPYAREA
1095 select FB_CFB_IMAGEBLIT
1098 This driver supports the on-board graphics built in to the Intel 810
1099 and 815 chipsets. Say Y if you have and plan to use such a board.
1101 To compile this driver as a module, choose M here: the
1102 module will be called i810fb.
1104 For more information, please read
1105 <file:Documentation/fb/intel810.txt>
1108 bool "use VESA Generalized Timing Formula"
1111 If you say Y, then the VESA standard, Generalized Timing Formula
1112 or GTF, will be used to calculate the required video timing values
1113 per video mode. Since the GTF allows nondiscrete timings
1114 (nondiscrete being a range of values as opposed to discrete being a
1115 set of values), you'll be able to use any combination of horizontal
1116 and vertical resolutions, and vertical refresh rates without having
1117 to specify your own timing parameters. This is especially useful
1118 to maximize the performance of an aging display, or if you just
1119 have a display with nonstandard dimensions. A VESA compliant
1120 monitor is recommended, but can still work with non-compliant ones.
1121 If you need or want this, then select this option. The timings may
1122 not be compliant with Intel's recommended values. Use at your own
1125 If you say N, the driver will revert to discrete video timings
1126 using a set recommended by Intel in their documentation.
1131 bool "Enable DDC Support"
1132 depends on FB_I810 && FB_I810_GTF
1137 tristate "Intel LE80578 (Vermilion) support"
1138 depends on FB && PCI && X86
1139 select FB_MODE_HELPERS
1140 select FB_CFB_FILLRECT
1141 select FB_CFB_COPYAREA
1142 select FB_CFB_IMAGEBLIT
1144 This driver supports the LE80578 (Vermilion Range) chipset
1146 config FB_CARILLO_RANCH
1147 tristate "Intel Carillo Ranch support"
1148 depends on FB_LE80578 && FB && PCI && X86
1150 This driver supports the LE80578 (Carillo Ranch) board
1153 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1154 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1155 select FB_MODE_HELPERS
1156 select FB_CFB_FILLRECT
1157 select FB_CFB_COPYAREA
1158 select FB_CFB_IMAGEBLIT
1159 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1160 depends on !DRM_I915
1162 This driver supports the on-board graphics built in to the Intel
1163 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1164 Say Y if you have and plan to use such a board.
1166 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1168 To compile this driver as a module, choose M here: the
1169 module will be called intelfb.
1171 For more information, please read <file:Documentation/fb/intelfb.txt>
1173 config FB_INTEL_DEBUG
1174 bool "Intel driver Debug Messages"
1177 Say Y here if you want the Intel driver to output all sorts
1178 of debugging information to provide to the maintainer when
1179 something goes wrong.
1182 bool "DDC/I2C for Intel framebuffer support"
1187 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1190 tristate "Matrox acceleration"
1191 depends on FB && PCI
1192 select FB_CFB_FILLRECT
1193 select FB_CFB_COPYAREA
1194 select FB_CFB_IMAGEBLIT
1195 select FB_TILEBLITTING
1196 select FB_MACMODES if PPC_PMAC
1198 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1199 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1200 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1201 Matrox G400, G450 or G550 card in your box.
1203 To compile this driver as a module, choose M here: the
1204 module will be called matroxfb.
1206 You can pass several parameters to the driver at boot time or at
1207 module load time. The parameters look like "video=matrox:XXX", and
1208 are described in <file:Documentation/fb/matroxfb.txt>.
1210 config FB_MATROX_MILLENIUM
1211 bool "Millennium I/II support"
1212 depends on FB_MATROX
1214 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1215 video card. If you select "Advanced lowlevel driver options" below,
1216 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1217 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1218 also use font widths different from 8.
1220 config FB_MATROX_MYSTIQUE
1221 bool "Mystique support"
1222 depends on FB_MATROX
1224 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1225 video card. If you select "Advanced lowlevel driver options" below,
1226 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1227 packed pixel and 32 bpp packed pixel. You can also use font widths
1231 bool "G100/G200/G400/G450/G550 support"
1232 depends on FB_MATROX
1234 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1235 video card. If you select "Advanced lowlevel driver options", you
1236 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1237 pixel and 32 bpp packed pixel. You can also use font widths
1240 If you need support for G400 secondary head, you must say Y to
1241 "Matrox I2C support" and "G400 second head support" right below.
1242 G450/G550 secondary head and digital output are supported without
1245 The driver starts in monitor mode. You must use the matroxset tool
1246 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1247 swap primary and secondary head outputs, or to change output mode.
1248 Secondary head driver always start in 640x480 resolution and you
1249 must use fbset to change it.
1251 Do not forget that second head supports only 16 and 32 bpp
1252 packed pixels, so it is a good idea to compile them into the kernel
1253 too. You can use only some font widths, as the driver uses generic
1254 painting procedures (the secondary head does not use acceleration
1257 G450/G550 hardware can display TV picture only from secondary CRTC,
1258 and it performs no scaling, so picture must have 525 or 625 lines.
1260 config FB_MATROX_I2C
1261 tristate "Matrox I2C support"
1262 depends on FB_MATROX
1265 This drivers creates I2C buses which are needed for accessing the
1266 DDC (I2C) bus present on all Matroxes, an I2C bus which
1267 interconnects Matrox optional devices, like MGA-TVO on G200 and
1268 G400, and the secondary head DDC bus, present on G400 only.
1270 You can say Y or M here if you want to experiment with monitor
1271 detection code. You must say Y or M here if you want to use either
1272 second head of G400 or MGA-TVO on G200 or G400.
1274 If you compile it as module, it will create a module named
1277 config FB_MATROX_MAVEN
1278 tristate "G400 second head support"
1279 depends on FB_MATROX_G && FB_MATROX_I2C
1281 WARNING !!! This support does not work with G450 !!!
1283 Say Y or M here if you want to use a secondary head (meaning two
1284 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1285 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1286 secondary head output is blanked while you are in X. With XFree
1287 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1288 the fbdev driver on first head and the fbdev driver on second head.
1290 If you compile it as module, two modules are created,
1291 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1292 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1293 also load i2c-matroxfb to get it to run.
1295 The driver starts in monitor mode and you must use the matroxset
1297 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1298 PAL or NTSC or to swap primary and secondary head outputs.
1299 Secondary head driver also always start in 640x480 resolution, you
1300 must use fbset to change it.
1302 Also do not forget that second head supports only 16 and 32 bpp
1303 packed pixels, so it is a good idea to compile them into the kernel
1304 too. You can use only some font widths, as the driver uses generic
1305 painting procedures (the secondary head does not use acceleration
1309 tristate "ATI Radeon display support"
1310 depends on FB && PCI
1311 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1312 select FB_MODE_HELPERS
1313 select FB_CFB_FILLRECT
1314 select FB_CFB_COPYAREA
1315 select FB_CFB_IMAGEBLIT
1316 select FB_MACMODES if PPC_OF
1318 Choose this option if you want to use an ATI Radeon graphics card as
1319 a framebuffer device. There are both PCI and AGP versions. You
1320 don't need to choose this to run the Radeon in plain VGA mode.
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
1480 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1482 This is the frame buffer device driver for the SiS 300, 315, 330
1483 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1484 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1486 To compile this driver as a module, choose M here; the module
1487 will be called sisfb.
1490 bool "SiS 300 series support"
1493 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1496 bool "SiS 315/330/340 series and XGI support"
1499 Say Y here to support use of the SiS 315, 330 and 340 series
1500 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1501 as XGI V3XT, V5, V8 and Z7.
1504 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1505 depends on FB && PCI
1506 select FB_CFB_FILLRECT
1507 select FB_CFB_COPYAREA
1508 select FB_CFB_IMAGEBLIT
1509 select FB_SOFT_CURSOR
1513 This is the frame buffer device driver for Graphics chips of VIA
1514 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1515 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1517 Say Y if you have a VIA UniChrome graphics board.
1519 To compile this driver as a module, choose M here: the
1520 module will be called viafb.
1522 tristate "NeoMagic display support"
1523 depends on FB && PCI
1524 select FB_MODE_HELPERS
1525 select FB_CFB_FILLRECT
1526 select FB_CFB_COPYAREA
1527 select FB_CFB_IMAGEBLIT
1530 This driver supports notebooks with NeoMagic PCI chips.
1531 Say Y if you have such a graphics card.
1533 To compile this driver as a module, choose M here: the
1534 module will be called neofb.
1537 tristate "IMG Kyro support"
1538 depends on FB && PCI
1539 select FB_CFB_FILLRECT
1540 select FB_CFB_COPYAREA
1541 select FB_CFB_IMAGEBLIT
1543 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1546 To compile this driver as a module, choose M here: the
1547 module will be called kyrofb.
1550 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1551 depends on FB && PCI
1552 select FB_CFB_IMAGEBLIT
1553 select FB_CFB_FILLRECT
1554 select FB_CFB_COPYAREA
1555 select FB_MODE_HELPERS
1557 This driver supports graphics boards with the 3Dfx Banshee,
1558 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1559 such a graphics board.
1561 To compile this driver as a module, choose M here: the
1562 module will be called tdfxfb.
1564 config FB_3DFX_ACCEL
1565 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1566 depends on FB_3DFX && EXPERIMENTAL
1568 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1569 device driver with acceleration functions.
1572 bool "Enable DDC/I2C support"
1573 depends on FB_3DFX && EXPERIMENTAL
1577 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1580 tristate "3Dfx Voodoo Graphics (sst1) support"
1581 depends on FB && PCI
1582 select FB_CFB_FILLRECT
1583 select FB_CFB_COPYAREA
1584 select FB_CFB_IMAGEBLIT
1586 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1587 Voodoo2 (cvg) based graphics card.
1589 To compile this driver as a module, choose M here: the
1590 module will be called sstfb.
1592 WARNING: Do not use any application that uses the 3D engine
1593 (namely glide) while using this driver.
1594 Please read the <file:Documentation/fb/sstfb.txt> for supported
1595 options and other important info support.
1598 tristate "VIA VT8623 support"
1599 depends on FB && PCI
1600 select FB_CFB_FILLRECT
1601 select FB_CFB_COPYAREA
1602 select FB_CFB_IMAGEBLIT
1603 select FB_TILEBLITTING
1606 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1608 Driver for CastleRock integrated graphics core in the
1609 VIA VT8623 [Apollo CLE266] chipset.
1612 tristate "Trident/CyberXXX/CyberBlade support"
1613 depends on FB && PCI
1614 select FB_CFB_FILLRECT
1615 select FB_CFB_COPYAREA
1616 select FB_CFB_IMAGEBLIT
1618 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1619 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1621 There are also integrated versions of these chips called CyberXXXX,
1622 CyberImage or CyberBlade. These chips are mostly found in laptops
1623 but also on some motherboards including early VIA EPIA motherboards.
1624 For more information, read <file:Documentation/fb/tridentfb.txt>
1626 Say Y if you have such a graphics board.
1628 To compile this driver as a module, choose M here: the
1629 module will be called tridentfb.
1632 tristate "ARK 2000PV support"
1633 depends on FB && PCI
1634 select FB_CFB_FILLRECT
1635 select FB_CFB_COPYAREA
1636 select FB_CFB_IMAGEBLIT
1637 select FB_TILEBLITTING
1640 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1642 Driver for PCI graphics boards with ARK 2000PV chip
1643 and ICS 5342 RAMDAC.
1646 tristate "Permedia3 support (EXPERIMENTAL)"
1647 depends on FB && PCI && EXPERIMENTAL
1648 select FB_CFB_FILLRECT
1649 select FB_CFB_COPYAREA
1650 select FB_CFB_IMAGEBLIT
1652 This is the frame buffer device driver for the 3DLabs Permedia3
1653 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1654 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1655 and maybe other boards.
1658 tristate "Fujitsu carmine frame buffer support"
1659 depends on FB && PCI
1660 select FB_CFB_FILLRECT
1661 select FB_CFB_COPYAREA
1662 select FB_CFB_IMAGEBLIT
1664 This is the frame buffer device driver for the Fujitsu Carmine chip.
1665 The driver provides two independent frame buffer devices.
1668 depends on FB_CARMINE
1669 prompt "DRAM timing"
1670 default FB_CARMINE_DRAM_EVAL
1672 config FB_CARMINE_DRAM_EVAL
1673 bool "Eval board timings"
1675 Use timings which work on the eval card.
1677 config CARMINE_DRAM_CUSTOM
1678 bool "Custom board timings"
1680 Use custom board timings.
1684 bool "Au1100 LCD Driver"
1685 depends on (FB = y) && MIPS && SOC_AU1100
1686 select FB_CFB_FILLRECT
1687 select FB_CFB_COPYAREA
1688 select FB_CFB_IMAGEBLIT
1690 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1691 various panels and CRTs by passing in kernel cmd line option
1692 au1100fb:panel=<name>.
1695 bool "Au1200 LCD Driver"
1696 depends on (FB = y) && MIPS && SOC_AU1200
1697 select FB_CFB_FILLRECT
1698 select FB_CFB_COPYAREA
1699 select FB_CFB_IMAGEBLIT
1701 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1702 various panels and CRTs by passing in kernel cmd line option
1703 au1200fb:panel=<name>.
1705 source "drivers/video/geode/Kconfig"
1708 tristate "HD64461 Frame Buffer support"
1709 depends on FB && HD64461
1710 select FB_CFB_FILLRECT
1711 select FB_CFB_COPYAREA
1712 select FB_CFB_IMAGEBLIT
1714 This is the frame buffer device driver for the Hitachi HD64461 LCD
1718 bool "PMAG-AA TURBOchannel framebuffer support"
1719 depends on (FB = y) && TC
1720 select FB_CFB_FILLRECT
1721 select FB_CFB_COPYAREA
1722 select FB_CFB_IMAGEBLIT
1724 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1725 used mainly in the MIPS-based DECstation series.
1728 tristate "PMAG-BA TURBOchannel framebuffer support"
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1734 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1735 used mainly in the MIPS-based DECstation series.
1738 tristate "PMAGB-B TURBOchannel framebuffer support"
1740 select FB_CFB_FILLRECT
1741 select FB_CFB_COPYAREA
1742 select FB_CFB_IMAGEBLIT
1744 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1745 in the MIPS-based DECstation series. The card is currently only
1746 supported in 1280x1024x8 mode.
1749 bool "Maxine (Personal DECstation) onboard framebuffer support"
1750 depends on (FB = y) && MACH_DECSTATION
1751 select FB_CFB_FILLRECT
1752 select FB_CFB_COPYAREA
1753 select FB_CFB_IMAGEBLIT
1755 Support for the onboard framebuffer (1024x768x8) in the Personal
1756 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1760 bool "G364 frame buffer support"
1761 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1762 select FB_CFB_FILLRECT
1763 select FB_CFB_COPYAREA
1764 select FB_CFB_IMAGEBLIT
1766 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1767 Olivetti M700-10 systems.
1770 bool "Motorola 68328 native frame buffer support"
1771 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1772 select FB_CFB_FILLRECT
1773 select FB_CFB_COPYAREA
1774 select FB_CFB_IMAGEBLIT
1776 Say Y here if you want to support the built-in frame buffer of
1777 the Motorola 68328 CPU family.
1780 tristate "PXA168/910 LCD framebuffer support"
1781 depends on FB && (CPU_PXA168 || CPU_PXA910)
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1786 Frame buffer driver for the built-in LCD controller in the Marvell
1790 tristate "PXA LCD framebuffer support"
1791 depends on FB && ARCH_PXA
1792 select FB_CFB_FILLRECT
1793 select FB_CFB_COPYAREA
1794 select FB_CFB_IMAGEBLIT
1796 Frame buffer driver for the built-in LCD controller in the Intel
1799 This driver is also available as a module ( = code which can be
1800 inserted and removed from the running kernel whenever you want). The
1801 module will be called pxafb. If you want to compile it as a module,
1802 say M here and read <file:Documentation/kbuild/modules.txt>.
1806 config FB_PXA_OVERLAY
1807 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1809 depends on FB_PXA && (PXA27x || PXA3xx)
1811 config FB_PXA_SMARTPANEL
1812 bool "PXA Smartpanel LCD support"
1816 config FB_PXA_PARAMETERS
1817 bool "PXA LCD command line parameters"
1821 Enable the use of kernel command line or module parameters
1822 to configure the physical properties of the LCD panel when
1823 using the PXA LCD driver.
1825 This option allows you to override the panel parameters
1826 supplied by the platform in order to support multiple
1827 different models of flatpanel. If you will only be using a
1828 single model of flatpanel then you can safely leave this
1831 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1834 tristate "2700G LCD framebuffer support"
1835 depends on FB && ARCH_PXA
1836 select FB_CFB_FILLRECT
1837 select FB_CFB_COPYAREA
1838 select FB_CFB_IMAGEBLIT
1840 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1844 bool "Enable debugging info via debugfs"
1845 depends on FB_MBX && DEBUG_FS
1848 Enable this if you want debugging information using the debug
1849 filesystem (debugfs)
1854 tristate "Freescale DIU framebuffer support"
1855 depends on FB && FSL_SOC
1856 select FB_CFB_FILLRECT
1857 select FB_CFB_COPYAREA
1858 select FB_CFB_IMAGEBLIT
1859 select PPC_LIB_RHEAP
1861 Framebuffer driver for the Freescale SoC DIU
1864 tristate "W100 frame buffer support"
1865 depends on FB && ARCH_PXA
1866 select FB_CFB_FILLRECT
1867 select FB_CFB_COPYAREA
1868 select FB_CFB_IMAGEBLIT
1870 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1871 It can also drive the w3220 chip found on iPAQ hx4700.
1873 This driver is also available as a module ( = code which can be
1874 inserted and removed from the running kernel whenever you want). The
1875 module will be called w100fb. If you want to compile it as a module,
1876 say M here and read <file:Documentation/kbuild/modules.txt>.
1880 config FB_SH_MOBILE_LCDC
1881 tristate "SuperH Mobile LCDC framebuffer support"
1882 depends on FB && SUPERH && HAVE_CLK
1883 select FB_SYS_FILLRECT
1884 select FB_SYS_COPYAREA
1885 select FB_SYS_IMAGEBLIT
1887 select FB_DEFERRED_IO
1889 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1892 tristate "Toshiba Mobile IO FrameBuffer support"
1893 depends on FB && MFD_CORE
1894 select FB_CFB_FILLRECT
1895 select FB_CFB_COPYAREA
1896 select FB_CFB_IMAGEBLIT
1898 Frame buffer driver for the Toshiba Mobile IO integrated as found
1899 on the Sharp SL-6000 series
1901 This driver is also available as a module ( = code which can be
1902 inserted and removed from the running kernel whenever you want). The
1903 module will be called tmiofb. If you want to compile it as a module,
1904 say M here and read <file:Documentation/kbuild/modules.txt>.
1908 config FB_TMIO_ACCELL
1909 bool "tmiofb acceleration"
1914 tristate "Samsung S3C framebuffer support"
1915 depends on FB && ARCH_S3C64XX
1916 select FB_CFB_FILLRECT
1917 select FB_CFB_COPYAREA
1918 select FB_CFB_IMAGEBLIT
1920 Frame buffer driver for the built-in FB controller in the Samsung
1921 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1922 and the S3C64XX series such as the S3C6400 and S3C6410.
1924 These chips all have the same basic framebuffer design with the
1925 actual capabilities depending on the chip. For instance the S3C6400
1926 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1927 currently only have two.
1929 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1931 config FB_S3C_DEBUG_REGWRITE
1932 bool "Debug register writes"
1935 Show all register writes via printk(KERN_DEBUG)
1938 tristate "S3C2410 LCD framebuffer support"
1939 depends on FB && ARCH_S3C2410
1940 select FB_CFB_FILLRECT
1941 select FB_CFB_COPYAREA
1942 select FB_CFB_IMAGEBLIT
1944 Frame buffer driver for the built-in LCD controller in the Samsung
1947 This driver is also available as a module ( = code which can be
1948 inserted and removed from the running kernel whenever you want). The
1949 module will be called s3c2410fb. If you want to compile it as a module,
1950 say M here and read <file:Documentation/kbuild/modules.txt>.
1953 config FB_S3C2410_DEBUG
1954 bool "S3C2410 lcd debug messages"
1955 depends on FB_S3C2410
1957 Turn on debugging messages. Note that you can set/unset at run time
1961 tristate "Silicon Motion SM501 framebuffer support"
1962 depends on FB && MFD_SM501
1963 select FB_CFB_FILLRECT
1964 select FB_CFB_COPYAREA
1965 select FB_CFB_IMAGEBLIT
1967 Frame buffer driver for the CRT and LCD controllers in the Silicon
1970 This driver is also available as a module ( = code which can be
1971 inserted and removed from the running kernel whenever you want). The
1972 module will be called sm501fb. If you want to compile it as a module,
1973 say M here and read <file:Documentation/kbuild/modules.txt>.
1978 config FB_PNX4008_DUM
1979 tristate "Display Update Module support on Philips PNX4008 board"
1980 depends on FB && ARCH_PNX4008
1982 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1984 config FB_PNX4008_DUM_RGB
1985 tristate "RGB Framebuffer support on Philips PNX4008 board"
1986 depends on FB_PNX4008_DUM
1987 select FB_CFB_FILLRECT
1988 select FB_CFB_COPYAREA
1989 select FB_CFB_IMAGEBLIT
1991 Say Y here to enable support for PNX4008 RGB Framebuffer
1993 config FB_IBM_GXT4500
1994 tristate "Framebuffer support for IBM GXT4500P adaptor"
1995 depends on FB && PPC
1996 select FB_CFB_FILLRECT
1997 select FB_CFB_COPYAREA
1998 select FB_CFB_IMAGEBLIT
2000 Say Y here to enable support for the IBM GXT4500P display
2001 adaptor, found on some IBM System P (pSeries) machines.
2004 tristate "PS3 GPU framebuffer driver"
2005 depends on FB && PS3_PS3AV
2006 select FB_SYS_FILLRECT
2007 select FB_SYS_COPYAREA
2008 select FB_SYS_IMAGEBLIT
2010 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2012 Include support for the virtual frame buffer in the PS3 platform.
2014 config FB_PS3_DEFAULT_SIZE_M
2015 int "PS3 default frame buffer size (in MiB)"
2019 This is the default size (in MiB) of the virtual frame buffer in
2021 The default value can be overridden on the kernel command line
2022 using the "ps3fb" option (e.g. "ps3fb=9M");
2025 tristate "Xilinx frame buffer support"
2026 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2027 select FB_CFB_FILLRECT
2028 select FB_CFB_COPYAREA
2029 select FB_CFB_IMAGEBLIT
2031 Include support for the Xilinx ML300/ML403 reference design
2032 framebuffer. ML300 carries a 640*480 LCD display on the board,
2033 ML403 uses a standard DB15 VGA connector.
2036 tristate "Cobalt server LCD frame buffer support"
2037 depends on FB && MIPS_COBALT
2040 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2041 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2042 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2043 select FB_CFB_FILLRECT
2044 select FB_CFB_COPYAREA
2045 select FB_CFB_IMAGEBLIT
2047 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2048 (D)STN/TFT LCD Controller.
2049 Supports display resolutions up to 1024x1024 pixel, grayscale and
2050 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2051 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2052 panels <= 320 pixel horizontal resolution.
2055 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2056 depends on FB && ARCH_DAVINCI_DA8XX
2057 select FB_CFB_FILLRECT
2058 select FB_CFB_COPYAREA
2059 select FB_CFB_IMAGEBLIT
2061 This is the frame buffer device driver for the TI LCD controller
2062 found on DA8xx/OMAP-L1xx SoCs.
2066 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2068 select FB_SYS_FILLRECT
2069 select FB_SYS_COPYAREA
2070 select FB_SYS_IMAGEBLIT
2073 This is a `virtual' frame buffer device. It operates on a chunk of
2074 unswappable kernel memory instead of on the memory of a graphics
2075 board. This means you cannot see any output sent to this frame
2076 buffer device, while it does consume precious memory. The main use
2077 of this frame buffer device is testing and debugging the frame
2078 buffer subsystem. Do NOT enable it for normal systems! To protect
2079 the innocent, it has to be enabled explicitly at boot time using the
2080 kernel option `video=vfb:'.
2082 To compile this driver as a module, choose M here: the
2083 module will be called vfb. In order to load it, you must use
2084 the vfb_enable=1 option.
2088 config XEN_FBDEV_FRONTEND
2089 tristate "Xen virtual frame buffer support"
2090 depends on FB && XEN
2091 select FB_SYS_FILLRECT
2092 select FB_SYS_COPYAREA
2093 select FB_SYS_IMAGEBLIT
2095 select FB_DEFERRED_IO
2096 select XEN_XENBUS_FRONTEND
2099 This driver implements the front-end of the Xen virtual
2100 frame buffer driver. It communicates with a back-end
2104 tristate "E-Ink Metronome/8track controller support"
2106 select FB_SYS_FILLRECT
2107 select FB_SYS_COPYAREA
2108 select FB_SYS_IMAGEBLIT
2110 select FB_DEFERRED_IO
2112 This driver implements support for the E-Ink Metronome
2113 controller. The pre-release name for this device was 8track
2114 and could also have been called by some vendors as PVI-nnnn.
2117 tristate "Fujitsu MB862xx GDC support"
2119 select FB_CFB_FILLRECT
2120 select FB_CFB_COPYAREA
2121 select FB_CFB_IMAGEBLIT
2123 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2125 config FB_MB862XX_PCI_GDC
2126 bool "Carmine/Coral-P(A) GDC"
2127 depends on PCI && FB_MB862XX
2129 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2130 PCI graphics controller devices.
2132 config FB_MB862XX_LIME
2134 depends on FB_MB862XX
2135 depends on OF && !FB_MB862XX_PCI_GDC
2137 select FB_FOREIGN_ENDIAN
2138 select FB_LITTLE_ENDIAN
2140 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2143 tristate "EP93XX frame buffer support"
2144 depends on FB && ARCH_EP93XX
2145 select FB_CFB_FILLRECT
2146 select FB_CFB_COPYAREA
2147 select FB_CFB_IMAGEBLIT
2149 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2150 This driver is also available as a module. The module will be called
2153 config FB_PRE_INIT_FB
2154 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2155 depends on FB && FB_MB862XX_LIME
2157 Select this option if display contents should be inherited as set by
2161 tristate "MSM Framebuffer support"
2162 depends on FB && ARCH_MSM
2163 select FB_CFB_FILLRECT
2164 select FB_CFB_COPYAREA
2165 select FB_CFB_IMAGEBLIT
2169 tristate "MX3 Framebuffer support"
2170 depends on FB && MX3_IPU
2171 select FB_CFB_FILLRECT
2172 select FB_CFB_COPYAREA
2173 select FB_CFB_IMAGEBLIT
2176 This is a framebuffer device for the i.MX31 LCD Controller. So
2177 far only synchronous displays are supported. If you plan to use
2178 an LCD display with your i.MX31 system, say Y here.
2180 config FB_BROADSHEET
2181 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2183 select FB_SYS_FILLRECT
2184 select FB_SYS_COPYAREA
2185 select FB_SYS_IMAGEBLIT
2187 select FB_DEFERRED_IO
2189 This driver implements support for the E-Ink Broadsheet
2190 controller. The release name for this device was Epson S1D13521
2191 and could also have been called by other names when coupled with
2194 source "drivers/video/omap/Kconfig"
2195 source "drivers/video/omap2/Kconfig"
2197 source "drivers/video/backlight/Kconfig"
2198 source "drivers/video/display/Kconfig"
2201 source "drivers/video/console/Kconfig"
2204 if FB || SGI_NEWPORT_CONSOLE
2205 source "drivers/video/logo/Kconfig"