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 tristate "NEC PowerVR 2 display support"
914 depends on FB && SH_DREAMCAST
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 Say Y here if you have a PowerVR 2 card in your box. If you plan to
920 run linux on your Dreamcast, you will have to say Y here.
921 This driver may or may not work on other PowerVR 2 cards, but is
922 totally untested. Use at your own risk. If unsure, say N.
924 To compile this driver as a module, choose M here: the
925 module will be called pvr2fb.
927 You can pass several parameters to the driver at boot time or at
928 module load time. The parameters look like "video=pvr2:XXX", where
929 the meaning of XXX can be found at the end of the main source file
930 (<file:drivers/video/pvr2fb.c>). Please see the file
931 <file:Documentation/fb/pvr2fb.txt>.
934 bool "Epson 1355 framebuffer support"
935 depends on (FB = y) && ARCH_CEIVA
936 select FB_CFB_FILLRECT
937 select FB_CFB_COPYAREA
938 select FB_CFB_IMAGEBLIT
940 Build in support for the SED1355 Epson Research Embedded RAMDAC
941 LCD/CRT Controller (since redesignated as the S1D13505) as a
942 framebuffer. Product specs at
943 <http://www.erd.epson.com/vdc/html/products.htm>.
946 tristate "Epson S1D13XXX framebuffer support"
948 select FB_CFB_FILLRECT
949 select FB_CFB_COPYAREA
950 select FB_CFB_IMAGEBLIT
952 Support for S1D13XXX framebuffer device family (currently only
953 working with S1D13806). Product specs at
954 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
957 tristate "AT91/AT32 LCD Controller support"
958 depends on FB && HAVE_FB_ATMEL
959 select FB_CFB_FILLRECT
960 select FB_CFB_COPYAREA
961 select FB_CFB_IMAGEBLIT
963 This enables support for the AT91/AT32 LCD Controller.
966 bool "Frame Buffer in internal SRAM"
967 depends on FB_ATMEL && ARCH_AT91SAM9261
969 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
970 to let frame buffer in external SDRAM.
973 bool "Use a STN display with AT91/AT32 LCD Controller"
974 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
977 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
978 Controller. Say N if you want to connect a TFT.
983 tristate "nVidia Framebuffer Support"
985 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
986 select FB_MODE_HELPERS
987 select FB_CFB_FILLRECT
988 select FB_CFB_COPYAREA
989 select FB_CFB_IMAGEBLIT
993 This driver supports graphics boards with the nVidia chips, TNT
994 and newer. For very old chipsets, such as the RIVA128, then use
996 Say Y if you have such a graphics board.
998 To compile this driver as a module, choose M here: the
999 module will be called nvidiafb.
1001 config FB_NVIDIA_I2C
1002 bool "Enable DDC Support"
1003 depends on FB_NVIDIA
1006 This enables I2C support for nVidia Chipsets. This is used
1007 only for getting EDID information from the attached display
1008 allowing for robust video mode handling and switching.
1010 Because fbdev-2.6 requires that drivers must be able to
1011 independently validate video mode parameters, you should say Y
1014 config FB_NVIDIA_DEBUG
1015 bool "Lots of debug output"
1016 depends on FB_NVIDIA
1019 Say Y here if you want the nVidia driver to output all sorts
1020 of debugging information to provide to the maintainer when
1021 something goes wrong.
1023 config FB_NVIDIA_BACKLIGHT
1024 bool "Support for backlight control"
1025 depends on FB_NVIDIA
1028 Say Y here if you want to control the backlight of your display.
1031 tristate "nVidia Riva support"
1032 depends on FB && PCI
1033 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1034 select FB_MODE_HELPERS
1035 select FB_CFB_FILLRECT
1036 select FB_CFB_COPYAREA
1037 select FB_CFB_IMAGEBLIT
1041 This driver supports graphics boards with the nVidia Riva/Geforce
1043 Say Y if you have such a graphics board.
1045 To compile this driver as a module, choose M here: the
1046 module will be called rivafb.
1049 bool "Enable DDC Support"
1053 This enables I2C support for nVidia Chipsets. This is used
1054 only for getting EDID information from the attached display
1055 allowing for robust video mode handling and switching.
1057 Because fbdev-2.6 requires that drivers must be able to
1058 independently validate video mode parameters, you should say Y
1061 config FB_RIVA_DEBUG
1062 bool "Lots of debug output"
1066 Say Y here if you want the Riva driver to output all sorts
1067 of debugging information to provide to the maintainer when
1068 something goes wrong.
1070 config FB_RIVA_BACKLIGHT
1071 bool "Support for backlight control"
1075 Say Y here if you want to control the backlight of your display.
1078 tristate "Intel 810/815 support (EXPERIMENTAL)"
1079 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1080 select FB_MODE_HELPERS
1081 select FB_CFB_FILLRECT
1082 select FB_CFB_COPYAREA
1083 select FB_CFB_IMAGEBLIT
1086 This driver supports the on-board graphics built in to the Intel 810
1087 and 815 chipsets. Say Y if you have and plan to use such a board.
1089 To compile this driver as a module, choose M here: the
1090 module will be called i810fb.
1092 For more information, please read
1093 <file:Documentation/fb/intel810.txt>
1096 bool "use VESA Generalized Timing Formula"
1099 If you say Y, then the VESA standard, Generalized Timing Formula
1100 or GTF, will be used to calculate the required video timing values
1101 per video mode. Since the GTF allows nondiscrete timings
1102 (nondiscrete being a range of values as opposed to discrete being a
1103 set of values), you'll be able to use any combination of horizontal
1104 and vertical resolutions, and vertical refresh rates without having
1105 to specify your own timing parameters. This is especially useful
1106 to maximize the performance of an aging display, or if you just
1107 have a display with nonstandard dimensions. A VESA compliant
1108 monitor is recommended, but can still work with non-compliant ones.
1109 If you need or want this, then select this option. The timings may
1110 not be compliant with Intel's recommended values. Use at your own
1113 If you say N, the driver will revert to discrete video timings
1114 using a set recommended by Intel in their documentation.
1119 bool "Enable DDC Support"
1120 depends on FB_I810 && FB_I810_GTF
1125 tristate "Intel LE80578 (Vermilion) support"
1126 depends on FB && PCI && X86
1127 select FB_MODE_HELPERS
1128 select FB_CFB_FILLRECT
1129 select FB_CFB_COPYAREA
1130 select FB_CFB_IMAGEBLIT
1132 This driver supports the LE80578 (Vermilion Range) chipset
1134 config FB_CARILLO_RANCH
1135 tristate "Intel Carillo Ranch support"
1136 depends on FB_LE80578 && FB && PCI && X86
1138 This driver supports the LE80578 (Carillo Ranch) board
1141 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1142 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1143 select FB_MODE_HELPERS
1144 select FB_CFB_FILLRECT
1145 select FB_CFB_COPYAREA
1146 select FB_CFB_IMAGEBLIT
1147 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1148 depends on !DRM_I915
1150 This driver supports the on-board graphics built in to the Intel
1151 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1152 Say Y if you have and plan to use such a board.
1154 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1156 To compile this driver as a module, choose M here: the
1157 module will be called intelfb.
1159 For more information, please read <file:Documentation/fb/intelfb.txt>
1161 config FB_INTEL_DEBUG
1162 bool "Intel driver Debug Messages"
1165 Say Y here if you want the Intel driver to output all sorts
1166 of debugging information to provide to the maintainer when
1167 something goes wrong.
1170 bool "DDC/I2C for Intel framebuffer support"
1175 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1178 tristate "Matrox acceleration"
1179 depends on FB && PCI
1180 select FB_CFB_FILLRECT
1181 select FB_CFB_COPYAREA
1182 select FB_CFB_IMAGEBLIT
1183 select FB_TILEBLITTING
1184 select FB_MACMODES if PPC_PMAC
1186 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1187 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1188 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1189 Matrox G400, G450 or G550 card in your box.
1191 To compile this driver as a module, choose M here: the
1192 module will be called matroxfb.
1194 You can pass several parameters to the driver at boot time or at
1195 module load time. The parameters look like "video=matrox:XXX", and
1196 are described in <file:Documentation/fb/matroxfb.txt>.
1198 config FB_MATROX_MILLENIUM
1199 bool "Millennium I/II support"
1200 depends on FB_MATROX
1202 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1203 video card. If you select "Advanced lowlevel driver options" below,
1204 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1205 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1206 also use font widths different from 8.
1208 config FB_MATROX_MYSTIQUE
1209 bool "Mystique support"
1210 depends on FB_MATROX
1212 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1213 video card. If you select "Advanced lowlevel driver options" below,
1214 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1215 packed pixel and 32 bpp packed pixel. You can also use font widths
1219 bool "G100/G200/G400/G450/G550 support"
1220 depends on FB_MATROX
1222 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1223 video card. If you select "Advanced lowlevel driver options", you
1224 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1225 pixel and 32 bpp packed pixel. You can also use font widths
1228 If you need support for G400 secondary head, you must say Y to
1229 "Matrox I2C support" and "G400 second head support" right below.
1230 G450/G550 secondary head and digital output are supported without
1233 The driver starts in monitor mode. You must use the matroxset tool
1234 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1235 swap primary and secondary head outputs, or to change output mode.
1236 Secondary head driver always start in 640x480 resolution and you
1237 must use fbset to change it.
1239 Do not forget that second head supports only 16 and 32 bpp
1240 packed pixels, so it is a good idea to compile them into the kernel
1241 too. You can use only some font widths, as the driver uses generic
1242 painting procedures (the secondary head does not use acceleration
1245 G450/G550 hardware can display TV picture only from secondary CRTC,
1246 and it performs no scaling, so picture must have 525 or 625 lines.
1248 config FB_MATROX_I2C
1249 tristate "Matrox I2C support"
1250 depends on FB_MATROX
1253 This drivers creates I2C buses which are needed for accessing the
1254 DDC (I2C) bus present on all Matroxes, an I2C bus which
1255 interconnects Matrox optional devices, like MGA-TVO on G200 and
1256 G400, and the secondary head DDC bus, present on G400 only.
1258 You can say Y or M here if you want to experiment with monitor
1259 detection code. You must say Y or M here if you want to use either
1260 second head of G400 or MGA-TVO on G200 or G400.
1262 If you compile it as module, it will create a module named
1265 config FB_MATROX_MAVEN
1266 tristate "G400 second head support"
1267 depends on FB_MATROX_G && FB_MATROX_I2C
1269 WARNING !!! This support does not work with G450 !!!
1271 Say Y or M here if you want to use a secondary head (meaning two
1272 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1273 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1274 secondary head output is blanked while you are in X. With XFree
1275 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1276 the fbdev driver on first head and the fbdev driver on second head.
1278 If you compile it as module, two modules are created,
1279 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1280 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1281 also load i2c-matroxfb to get it to run.
1283 The driver starts in monitor mode and you must use the matroxset
1285 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1286 PAL or NTSC or to swap primary and secondary head outputs.
1287 Secondary head driver also always start in 640x480 resolution, you
1288 must use fbset to change it.
1290 Also do not forget that second head supports only 16 and 32 bpp
1291 packed pixels, so it is a good idea to compile them into the kernel
1292 too. You can use only some font widths, as the driver uses generic
1293 painting procedures (the secondary head does not use acceleration
1297 tristate "ATI Radeon display support"
1298 depends on FB && PCI
1299 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1300 select FB_MODE_HELPERS
1301 select FB_CFB_FILLRECT
1302 select FB_CFB_COPYAREA
1303 select FB_CFB_IMAGEBLIT
1304 select FB_MACMODES if PPC_OF
1306 Choose this option if you want to use an ATI Radeon graphics card as
1307 a framebuffer device. There are both PCI and AGP versions. You
1308 don't need to choose this to run the Radeon in plain VGA mode.
1310 There is a product page at
1311 http://apps.ati.com/ATIcompare/
1313 config FB_RADEON_I2C
1314 bool "DDC/I2C for ATI Radeon support"
1315 depends on FB_RADEON
1319 Say Y here if you want DDC/I2C support for your Radeon board.
1321 config FB_RADEON_BACKLIGHT
1322 bool "Support for backlight control"
1323 depends on FB_RADEON
1326 Say Y here if you want to control the backlight of your display.
1328 config FB_RADEON_DEBUG
1329 bool "Lots of debug output from Radeon driver"
1330 depends on FB_RADEON
1333 Say Y here if you want the Radeon driver to output all sorts
1334 of debugging information to provide to the maintainer when
1335 something goes wrong.
1338 tristate "ATI Rage128 display support"
1339 depends on FB && PCI
1340 select FB_CFB_FILLRECT
1341 select FB_CFB_COPYAREA
1342 select FB_CFB_IMAGEBLIT
1343 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1344 select FB_MACMODES if PPC_PMAC
1346 This driver supports graphics boards with the ATI Rage128 chips.
1347 Say Y if you have such a graphics board and read
1348 <file:Documentation/fb/aty128fb.txt>.
1350 To compile this driver as a module, choose M here: the
1351 module will be called aty128fb.
1353 config FB_ATY128_BACKLIGHT
1354 bool "Support for backlight control"
1355 depends on FB_ATY128
1358 Say Y here if you want to control the backlight of your display.
1361 tristate "ATI Mach64 display support" if PCI || ATARI
1362 depends on FB && !SPARC32
1363 select FB_CFB_FILLRECT
1364 select FB_CFB_COPYAREA
1365 select FB_CFB_IMAGEBLIT
1366 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1367 select FB_MACMODES if PPC
1369 This driver supports graphics boards with the ATI Mach64 chips.
1370 Say Y if you have such a graphics board.
1372 To compile this driver as a module, choose M here: the
1373 module will be called atyfb.
1376 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1377 depends on PCI && FB_ATY
1378 default y if SPARC64 && PCI
1380 Say Y here to support use of ATI's 64-bit Rage boards (or other
1381 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1382 framebuffer device. The ATI product support page for these boards
1383 is at <http://support.ati.com/products/pc/mach64/>.
1385 config FB_ATY_GENERIC_LCD
1386 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1387 depends on FB_ATY_CT
1389 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1390 Rage XC, or Rage XL chipset.
1393 bool "Mach64 GX support" if PCI
1397 Say Y here to support use of the ATI Mach64 Graphics Expression
1398 board (or other boards based on the Mach64 GX chipset) as a
1399 framebuffer device. The ATI product support page for these boards
1401 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1403 config FB_ATY_BACKLIGHT
1404 bool "Support for backlight control"
1408 Say Y here if you want to control the backlight of your display.
1411 tristate "S3 Trio/Virge support"
1412 depends on FB && PCI
1413 select FB_CFB_FILLRECT
1414 select FB_CFB_COPYAREA
1415 select FB_CFB_IMAGEBLIT
1416 select FB_TILEBLITTING
1419 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1421 Driver for graphics boards with S3 Trio / S3 Virge chip.
1424 tristate "S3 Savage support"
1425 depends on FB && PCI && EXPERIMENTAL
1426 select FB_MODE_HELPERS
1427 select FB_CFB_FILLRECT
1428 select FB_CFB_COPYAREA
1429 select FB_CFB_IMAGEBLIT
1432 This driver supports notebooks and computers with S3 Savage PCI/AGP
1435 Say Y if you have such a graphics card.
1437 To compile this driver as a module, choose M here; the module
1438 will be called savagefb.
1440 config FB_SAVAGE_I2C
1441 bool "Enable DDC2 Support"
1442 depends on FB_SAVAGE
1445 This enables I2C support for S3 Savage Chipsets. This is used
1446 only for getting EDID information from the attached display
1447 allowing for robust video mode handling and switching.
1449 Because fbdev-2.6 requires that drivers must be able to
1450 independently validate video mode parameters, you should say Y
1453 config FB_SAVAGE_ACCEL
1454 bool "Enable Console Acceleration"
1455 depends on FB_SAVAGE
1458 This option will compile in console acceleration support. If
1459 the resulting framebuffer console has bothersome glitches, then
1463 tristate "SiS/XGI display support"
1464 depends on FB && PCI
1465 select FB_CFB_FILLRECT
1466 select FB_CFB_COPYAREA
1467 select FB_CFB_IMAGEBLIT
1468 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1470 This is the frame buffer device driver for the SiS 300, 315, 330
1471 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1472 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1474 To compile this driver as a module, choose M here; the module
1475 will be called sisfb.
1478 bool "SiS 300 series support"
1481 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1484 bool "SiS 315/330/340 series and XGI support"
1487 Say Y here to support use of the SiS 315, 330 and 340 series
1488 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1489 as XGI V3XT, V5, V8 and Z7.
1492 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1493 depends on FB && PCI
1494 select FB_CFB_FILLRECT
1495 select FB_CFB_COPYAREA
1496 select FB_CFB_IMAGEBLIT
1497 select FB_SOFT_CURSOR
1501 This is the frame buffer device driver for Graphics chips of VIA
1502 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1503 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1505 Say Y if you have a VIA UniChrome graphics board.
1507 To compile this driver as a module, choose M here: the
1508 module will be called viafb.
1510 tristate "NeoMagic display support"
1511 depends on FB && PCI
1512 select FB_MODE_HELPERS
1513 select FB_CFB_FILLRECT
1514 select FB_CFB_COPYAREA
1515 select FB_CFB_IMAGEBLIT
1518 This driver supports notebooks with NeoMagic PCI chips.
1519 Say Y if you have such a graphics card.
1521 To compile this driver as a module, choose M here: the
1522 module will be called neofb.
1525 tristate "IMG Kyro support"
1526 depends on FB && PCI
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1529 select FB_CFB_IMAGEBLIT
1531 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1534 To compile this driver as a module, choose M here: the
1535 module will be called kyrofb.
1538 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1539 depends on FB && PCI
1540 select FB_CFB_IMAGEBLIT
1541 select FB_CFB_FILLRECT
1542 select FB_CFB_COPYAREA
1543 select FB_MODE_HELPERS
1545 This driver supports graphics boards with the 3Dfx Banshee,
1546 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1547 such a graphics board.
1549 To compile this driver as a module, choose M here: the
1550 module will be called tdfxfb.
1552 config FB_3DFX_ACCEL
1553 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1554 depends on FB_3DFX && EXPERIMENTAL
1556 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1557 device driver with acceleration functions.
1560 bool "Enable DDC/I2C support"
1561 depends on FB_3DFX && EXPERIMENTAL
1565 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1568 tristate "3Dfx Voodoo Graphics (sst1) support"
1569 depends on FB && PCI
1570 select FB_CFB_FILLRECT
1571 select FB_CFB_COPYAREA
1572 select FB_CFB_IMAGEBLIT
1574 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1575 Voodoo2 (cvg) based graphics card.
1577 To compile this driver as a module, choose M here: the
1578 module will be called sstfb.
1580 WARNING: Do not use any application that uses the 3D engine
1581 (namely glide) while using this driver.
1582 Please read the <file:Documentation/fb/sstfb.txt> for supported
1583 options and other important info support.
1586 tristate "VIA VT8623 support"
1587 depends on FB && PCI
1588 select FB_CFB_FILLRECT
1589 select FB_CFB_COPYAREA
1590 select FB_CFB_IMAGEBLIT
1591 select FB_TILEBLITTING
1594 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1596 Driver for CastleRock integrated graphics core in the
1597 VIA VT8623 [Apollo CLE266] chipset.
1600 tristate "Trident/CyberXXX/CyberBlade support"
1601 depends on FB && PCI
1602 select FB_CFB_FILLRECT
1603 select FB_CFB_COPYAREA
1604 select FB_CFB_IMAGEBLIT
1606 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1607 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1609 There are also integrated versions of these chips called CyberXXXX,
1610 CyberImage or CyberBlade. These chips are mostly found in laptops
1611 but also on some motherboards including early VIA EPIA motherboards.
1612 For more information, read <file:Documentation/fb/tridentfb.txt>
1614 Say Y if you have such a graphics board.
1616 To compile this driver as a module, choose M here: the
1617 module will be called tridentfb.
1620 tristate "ARK 2000PV support"
1621 depends on FB && PCI
1622 select FB_CFB_FILLRECT
1623 select FB_CFB_COPYAREA
1624 select FB_CFB_IMAGEBLIT
1625 select FB_TILEBLITTING
1628 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1630 Driver for PCI graphics boards with ARK 2000PV chip
1631 and ICS 5342 RAMDAC.
1634 tristate "Permedia3 support (EXPERIMENTAL)"
1635 depends on FB && PCI && EXPERIMENTAL
1636 select FB_CFB_FILLRECT
1637 select FB_CFB_COPYAREA
1638 select FB_CFB_IMAGEBLIT
1640 This is the frame buffer device driver for the 3DLabs Permedia3
1641 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1642 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1643 and maybe other boards.
1646 tristate "Fujitsu carmine frame buffer support"
1647 depends on FB && PCI
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 Fujitsu Carmine chip.
1653 The driver provides two independent frame buffer devices.
1656 depends on FB_CARMINE
1657 prompt "DRAM timing"
1658 default FB_CARMINE_DRAM_EVAL
1660 config FB_CARMINE_DRAM_EVAL
1661 bool "Eval board timings"
1663 Use timings which work on the eval card.
1665 config CARMINE_DRAM_CUSTOM
1666 bool "Custom board timings"
1668 Use custom board timings.
1672 bool "Au1100 LCD Driver"
1673 depends on (FB = y) && MIPS && SOC_AU1100
1674 select FB_CFB_FILLRECT
1675 select FB_CFB_COPYAREA
1676 select FB_CFB_IMAGEBLIT
1678 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1679 various panels and CRTs by passing in kernel cmd line option
1680 au1100fb:panel=<name>.
1683 bool "Au1200 LCD Driver"
1684 depends on (FB = y) && MIPS && SOC_AU1200
1685 select FB_CFB_FILLRECT
1686 select FB_CFB_COPYAREA
1687 select FB_CFB_IMAGEBLIT
1689 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1690 various panels and CRTs by passing in kernel cmd line option
1691 au1200fb:panel=<name>.
1693 source "drivers/video/geode/Kconfig"
1696 tristate "HD64461 Frame Buffer support"
1697 depends on FB && HD64461
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1702 This is the frame buffer device driver for the Hitachi HD64461 LCD
1706 bool "PMAG-AA TURBOchannel framebuffer support"
1707 depends on (FB = y) && TC
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1713 used mainly in the MIPS-based DECstation series.
1716 tristate "PMAG-BA TURBOchannel framebuffer support"
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1722 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1723 used mainly in the MIPS-based DECstation series.
1726 tristate "PMAGB-B TURBOchannel framebuffer support"
1728 select FB_CFB_FILLRECT
1729 select FB_CFB_COPYAREA
1730 select FB_CFB_IMAGEBLIT
1732 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1733 in the MIPS-based DECstation series. The card is currently only
1734 supported in 1280x1024x8 mode.
1737 bool "Maxine (Personal DECstation) onboard framebuffer support"
1738 depends on (FB = y) && MACH_DECSTATION
1739 select FB_CFB_FILLRECT
1740 select FB_CFB_COPYAREA
1741 select FB_CFB_IMAGEBLIT
1743 Support for the onboard framebuffer (1024x768x8) in the Personal
1744 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1748 bool "G364 frame buffer support"
1749 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1750 select FB_CFB_FILLRECT
1751 select FB_CFB_COPYAREA
1752 select FB_CFB_IMAGEBLIT
1754 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1755 Olivetti M700-10 systems.
1758 bool "Motorola 68328 native frame buffer support"
1759 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1760 select FB_CFB_FILLRECT
1761 select FB_CFB_COPYAREA
1762 select FB_CFB_IMAGEBLIT
1764 Say Y here if you want to support the built-in frame buffer of
1765 the Motorola 68328 CPU family.
1768 tristate "PXA168/910 LCD framebuffer support"
1769 depends on FB && (CPU_PXA168 || CPU_PXA910)
1770 select FB_CFB_FILLRECT
1771 select FB_CFB_COPYAREA
1772 select FB_CFB_IMAGEBLIT
1774 Frame buffer driver for the built-in LCD controller in the Marvell
1778 tristate "PXA LCD framebuffer support"
1779 depends on FB && ARCH_PXA
1780 select FB_CFB_FILLRECT
1781 select FB_CFB_COPYAREA
1782 select FB_CFB_IMAGEBLIT
1784 Frame buffer driver for the built-in LCD controller in the Intel
1787 This driver is also available as a module ( = code which can be
1788 inserted and removed from the running kernel whenever you want). The
1789 module will be called pxafb. If you want to compile it as a module,
1790 say M here and read <file:Documentation/kbuild/modules.txt>.
1794 config FB_PXA_OVERLAY
1795 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1797 depends on FB_PXA && (PXA27x || PXA3xx)
1799 config FB_PXA_SMARTPANEL
1800 bool "PXA Smartpanel LCD support"
1804 config FB_PXA_PARAMETERS
1805 bool "PXA LCD command line parameters"
1809 Enable the use of kernel command line or module parameters
1810 to configure the physical properties of the LCD panel when
1811 using the PXA LCD driver.
1813 This option allows you to override the panel parameters
1814 supplied by the platform in order to support multiple
1815 different models of flatpanel. If you will only be using a
1816 single model of flatpanel then you can safely leave this
1819 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1822 tristate "2700G LCD framebuffer support"
1823 depends on FB && ARCH_PXA
1824 select FB_CFB_FILLRECT
1825 select FB_CFB_COPYAREA
1826 select FB_CFB_IMAGEBLIT
1828 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1832 bool "Enable debugging info via debugfs"
1833 depends on FB_MBX && DEBUG_FS
1836 Enable this if you want debugging information using the debug
1837 filesystem (debugfs)
1842 tristate "Freescale DIU framebuffer support"
1843 depends on FB && FSL_SOC
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1847 select PPC_LIB_RHEAP
1849 Framebuffer driver for the Freescale SoC DIU
1852 tristate "W100 frame buffer support"
1853 depends on FB && ARCH_PXA
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1859 It can also drive the w3220 chip found on iPAQ hx4700.
1861 This driver is also available as a module ( = code which can be
1862 inserted and removed from the running kernel whenever you want). The
1863 module will be called w100fb. If you want to compile it as a module,
1864 say M here and read <file:Documentation/kbuild/modules.txt>.
1868 config FB_SH_MOBILE_LCDC
1869 tristate "SuperH Mobile LCDC framebuffer support"
1870 depends on FB && SUPERH && HAVE_CLK
1871 select FB_SYS_FILLRECT
1872 select FB_SYS_COPYAREA
1873 select FB_SYS_IMAGEBLIT
1875 select FB_DEFERRED_IO
1877 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1880 tristate "Toshiba Mobile IO FrameBuffer support"
1881 depends on FB && MFD_CORE
1882 select FB_CFB_FILLRECT
1883 select FB_CFB_COPYAREA
1884 select FB_CFB_IMAGEBLIT
1886 Frame buffer driver for the Toshiba Mobile IO integrated as found
1887 on the Sharp SL-6000 series
1889 This driver is also available as a module ( = code which can be
1890 inserted and removed from the running kernel whenever you want). The
1891 module will be called tmiofb. If you want to compile it as a module,
1892 say M here and read <file:Documentation/kbuild/modules.txt>.
1896 config FB_TMIO_ACCELL
1897 bool "tmiofb acceleration"
1902 tristate "Samsung S3C framebuffer support"
1903 depends on FB && ARCH_S3C64XX
1904 select FB_CFB_FILLRECT
1905 select FB_CFB_COPYAREA
1906 select FB_CFB_IMAGEBLIT
1908 Frame buffer driver for the built-in FB controller in the Samsung
1909 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1910 and the S3C64XX series such as the S3C6400 and S3C6410.
1912 These chips all have the same basic framebuffer design with the
1913 actual capabilities depending on the chip. For instance the S3C6400
1914 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1915 currently only have two.
1917 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1919 config FB_S3C_DEBUG_REGWRITE
1920 bool "Debug register writes"
1923 Show all register writes via printk(KERN_DEBUG)
1926 tristate "S3C2410 LCD framebuffer support"
1927 depends on FB && ARCH_S3C2410
1928 select FB_CFB_FILLRECT
1929 select FB_CFB_COPYAREA
1930 select FB_CFB_IMAGEBLIT
1932 Frame buffer driver for the built-in LCD controller in the Samsung
1935 This driver is also available as a module ( = code which can be
1936 inserted and removed from the running kernel whenever you want). The
1937 module will be called s3c2410fb. If you want to compile it as a module,
1938 say M here and read <file:Documentation/kbuild/modules.txt>.
1941 config FB_S3C2410_DEBUG
1942 bool "S3C2410 lcd debug messages"
1943 depends on FB_S3C2410
1945 Turn on debugging messages. Note that you can set/unset at run time
1949 tristate "Silicon Motion SM501 framebuffer support"
1950 depends on FB && MFD_SM501
1951 select FB_CFB_FILLRECT
1952 select FB_CFB_COPYAREA
1953 select FB_CFB_IMAGEBLIT
1955 Frame buffer driver for the CRT and LCD controllers in the Silicon
1958 This driver is also available as a module ( = code which can be
1959 inserted and removed from the running kernel whenever you want). The
1960 module will be called sm501fb. If you want to compile it as a module,
1961 say M here and read <file:Documentation/kbuild/modules.txt>.
1966 config FB_PNX4008_DUM
1967 tristate "Display Update Module support on Philips PNX4008 board"
1968 depends on FB && ARCH_PNX4008
1970 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1972 config FB_PNX4008_DUM_RGB
1973 tristate "RGB Framebuffer support on Philips PNX4008 board"
1974 depends on FB_PNX4008_DUM
1975 select FB_CFB_FILLRECT
1976 select FB_CFB_COPYAREA
1977 select FB_CFB_IMAGEBLIT
1979 Say Y here to enable support for PNX4008 RGB Framebuffer
1981 config FB_IBM_GXT4500
1982 tristate "Framebuffer support for IBM GXT4500P adaptor"
1983 depends on FB && PPC
1984 select FB_CFB_FILLRECT
1985 select FB_CFB_COPYAREA
1986 select FB_CFB_IMAGEBLIT
1988 Say Y here to enable support for the IBM GXT4500P display
1989 adaptor, found on some IBM System P (pSeries) machines.
1992 tristate "PS3 GPU framebuffer driver"
1993 depends on FB && PS3_PS3AV
1994 select FB_SYS_FILLRECT
1995 select FB_SYS_COPYAREA
1996 select FB_SYS_IMAGEBLIT
1998 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2000 Include support for the virtual frame buffer in the PS3 platform.
2002 config FB_PS3_DEFAULT_SIZE_M
2003 int "PS3 default frame buffer size (in MiB)"
2007 This is the default size (in MiB) of the virtual frame buffer in
2009 The default value can be overridden on the kernel command line
2010 using the "ps3fb" option (e.g. "ps3fb=9M");
2013 tristate "Xilinx frame buffer support"
2014 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2015 select FB_CFB_FILLRECT
2016 select FB_CFB_COPYAREA
2017 select FB_CFB_IMAGEBLIT
2019 Include support for the Xilinx ML300/ML403 reference design
2020 framebuffer. ML300 carries a 640*480 LCD display on the board,
2021 ML403 uses a standard DB15 VGA connector.
2024 tristate "Cobalt server LCD frame buffer support"
2025 depends on FB && MIPS_COBALT
2028 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2029 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2030 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2031 select FB_CFB_FILLRECT
2032 select FB_CFB_COPYAREA
2033 select FB_CFB_IMAGEBLIT
2035 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2036 (D)STN/TFT LCD Controller.
2037 Supports display resolutions up to 1024x1024 pixel, grayscale and
2038 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2039 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2040 panels <= 320 pixel horizontal resolution.
2043 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2044 depends on FB && ARCH_DAVINCI_DA8XX
2045 select FB_CFB_FILLRECT
2046 select FB_CFB_COPYAREA
2047 select FB_CFB_IMAGEBLIT
2049 This is the frame buffer device driver for the TI LCD controller
2050 found on DA8xx/OMAP-L1xx SoCs.
2054 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2056 select FB_SYS_FILLRECT
2057 select FB_SYS_COPYAREA
2058 select FB_SYS_IMAGEBLIT
2061 This is a `virtual' frame buffer device. It operates on a chunk of
2062 unswappable kernel memory instead of on the memory of a graphics
2063 board. This means you cannot see any output sent to this frame
2064 buffer device, while it does consume precious memory. The main use
2065 of this frame buffer device is testing and debugging the frame
2066 buffer subsystem. Do NOT enable it for normal systems! To protect
2067 the innocent, it has to be enabled explicitly at boot time using the
2068 kernel option `video=vfb:'.
2070 To compile this driver as a module, choose M here: the
2071 module will be called vfb. In order to load it, you must use
2072 the vfb_enable=1 option.
2076 config XEN_FBDEV_FRONTEND
2077 tristate "Xen virtual frame buffer support"
2078 depends on FB && XEN
2079 select FB_SYS_FILLRECT
2080 select FB_SYS_COPYAREA
2081 select FB_SYS_IMAGEBLIT
2083 select FB_DEFERRED_IO
2084 select XEN_XENBUS_FRONTEND
2087 This driver implements the front-end of the Xen virtual
2088 frame buffer driver. It communicates with a back-end
2092 tristate "E-Ink Metronome/8track controller support"
2094 select FB_SYS_FILLRECT
2095 select FB_SYS_COPYAREA
2096 select FB_SYS_IMAGEBLIT
2098 select FB_DEFERRED_IO
2100 This driver implements support for the E-Ink Metronome
2101 controller. The pre-release name for this device was 8track
2102 and could also have been called by some vendors as PVI-nnnn.
2105 tristate "Fujitsu MB862xx GDC support"
2107 select FB_CFB_FILLRECT
2108 select FB_CFB_COPYAREA
2109 select FB_CFB_IMAGEBLIT
2111 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2113 config FB_MB862XX_PCI_GDC
2114 bool "Carmine/Coral-P(A) GDC"
2115 depends on PCI && FB_MB862XX
2117 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2118 PCI graphics controller devices.
2120 config FB_MB862XX_LIME
2122 depends on FB_MB862XX
2123 depends on OF && !FB_MB862XX_PCI_GDC
2125 select FB_FOREIGN_ENDIAN
2126 select FB_LITTLE_ENDIAN
2128 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2131 tristate "EP93XX frame buffer support"
2132 depends on FB && ARCH_EP93XX
2133 select FB_CFB_FILLRECT
2134 select FB_CFB_COPYAREA
2135 select FB_CFB_IMAGEBLIT
2137 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2138 This driver is also available as a module. The module will be called
2141 config FB_PRE_INIT_FB
2142 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2143 depends on FB && FB_MB862XX_LIME
2145 Select this option if display contents should be inherited as set by
2149 tristate "MSM Framebuffer support"
2150 depends on FB && ARCH_MSM
2151 select FB_CFB_FILLRECT
2152 select FB_CFB_COPYAREA
2153 select FB_CFB_IMAGEBLIT
2157 tristate "MX3 Framebuffer support"
2158 depends on FB && MX3_IPU
2159 select FB_CFB_FILLRECT
2160 select FB_CFB_COPYAREA
2161 select FB_CFB_IMAGEBLIT
2164 This is a framebuffer device for the i.MX31 LCD Controller. So
2165 far only synchronous displays are supported. If you plan to use
2166 an LCD display with your i.MX31 system, say Y here.
2168 config FB_BROADSHEET
2169 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2171 select FB_SYS_FILLRECT
2172 select FB_SYS_COPYAREA
2173 select FB_SYS_IMAGEBLIT
2175 select FB_DEFERRED_IO
2177 This driver implements support for the E-Ink Broadsheet
2178 controller. The release name for this device was Epson S1D13521
2179 and could also have been called by other names when coupled with
2182 source "drivers/video/omap/Kconfig"
2183 source "drivers/video/omap2/Kconfig"
2185 source "drivers/video/backlight/Kconfig"
2186 source "drivers/video/display/Kconfig"
2189 source "drivers/video/console/Kconfig"
2192 if FB || SGI_NEWPORT_CONSOLE
2193 source "drivers/video/logo/Kconfig"