5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/gpu/vga/Kconfig"
12 source "drivers/gpu/drm/Kconfig"
18 config VIDEO_OUTPUT_CONTROL
19 tristate "Lowlevel video output switch controls"
21 This framework adds support for low-level control of the video
25 tristate "Support for frame buffer devices"
27 The frame buffer device provides an abstraction for the graphics
28 hardware. It represents the frame buffer of some video hardware and
29 allows application software to access the graphics hardware through
30 a well-defined interface, so the software doesn't need to know
31 anything about the low-level (hardware register) stuff.
33 Frame buffer devices work identically across the different
34 architectures supported by Linux and make the implementation of
35 application programs easier and more portable; at this point, an X
36 server exists which uses the frame buffer device exclusively.
37 On several non-X86 architectures, the frame buffer device is the
38 only way to use the graphics hardware.
40 The device is accessed through special device nodes, usually located
41 in the /dev directory, i.e. /dev/fb*.
43 You need an utility program called fbset to make full use of frame
44 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
45 and the Framebuffer-HOWTO at
46 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more
49 Say Y here and to the driver for your graphics board below if you
50 are compiling a kernel for a non-x86 architecture.
52 If you are compiling for the x86 architecture, you can say Y if you
53 want to play with it, but it is not essential. Please note that
54 running graphical applications that directly touch the hardware
55 (e.g. an accelerated X server) and that are not frame buffer
56 device-aware may cause unexpected results. If unsure, say N.
59 bool "Enable firmware EDID"
63 This enables access to the EDID transferred from the firmware.
64 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
65 transfers do not work for your driver and if you are using
66 nvidiafb, i810fb or savagefb.
68 In general, choosing Y for this option is safe. If you
69 experience extremely long delays while booting before you get
70 something on your display, try setting this to N. Matrox cards in
71 combination with certain motherboards and monitors are known to
72 suffer from this problem.
81 config FB_BOOT_VESA_SUPPORT
86 If true, at least one selected framebuffer driver can take advantage
87 of VESA video modes set at an early boot stage via the vga= parameter.
89 config FB_CFB_FILLRECT
94 Include the cfb_fillrect function for generic software rectangle
95 filling. This is used by drivers that don't provide their own
96 (accelerated) version.
98 config FB_CFB_COPYAREA
103 Include the cfb_copyarea function for generic software area copying.
104 This is used by drivers that don't provide their own (accelerated)
107 config FB_CFB_IMAGEBLIT
112 Include the cfb_imageblit function for generic software image
113 blitting. This is used by drivers that don't provide their own
114 (accelerated) version.
116 config FB_CFB_REV_PIXELS_IN_BYTE
121 Allow generic frame-buffer functions to work on displays with 1, 2
122 and 4 bits per pixel depths which has opposite order of pixels in
123 byte order to bytes in long order.
125 config FB_SYS_FILLRECT
130 Include the sys_fillrect function for generic software rectangle
131 filling. This is used by drivers that don't provide their own
132 (accelerated) version and the framebuffer is in system RAM.
134 config FB_SYS_COPYAREA
139 Include the sys_copyarea function for generic software area copying.
140 This is used by drivers that don't provide their own (accelerated)
141 version and the framebuffer is in system RAM.
143 config FB_SYS_IMAGEBLIT
148 Include the sys_imageblit function for generic software image
149 blitting. This is used by drivers that don't provide their own
150 (accelerated) version and the framebuffer is in system RAM.
152 menuconfig FB_FOREIGN_ENDIAN
153 bool "Framebuffer foreign endianness support"
156 This menu will let you enable support for the framebuffers with
157 non-native endianness (e.g. Little-Endian framebuffer on a
158 Big-Endian machine). Most probably you don't have such hardware,
159 so it's safe to say "n" here.
162 prompt "Choice endianness support"
163 depends on FB_FOREIGN_ENDIAN
165 config FB_BOTH_ENDIAN
166 bool "Support for Big- and Little-Endian framebuffers"
169 bool "Support for Big-Endian framebuffers only"
171 config FB_LITTLE_ENDIAN
172 bool "Support for Little-Endian framebuffers only"
181 config FB_DEFERRED_IO
188 depends on FB_DEFERRED_IO
195 Common utility functions useful to fbdev drivers of VGA-based
206 select BACKLIGHT_LCD_SUPPORT
207 select BACKLIGHT_CLASS_DEVICE
210 config FB_MODE_HELPERS
211 bool "Enable Video Mode Handling Helpers"
215 This enables functions for handling video modes using the
216 Generalized Timing Formula and the EDID parser. A few drivers rely
217 on this feature such as the radeonfb, rivafb, and the i810fb. If
218 your driver does not take advantage of this feature, choosing Y will
219 just increase the kernel size by about 5K.
221 config FB_TILEBLITTING
222 bool "Enable Tile Blitting Support"
226 This enables tile blitting. Tile blitting is a drawing technique
227 where the screen is divided into rectangular sections (tiles), whereas
228 the standard blitting divides the screen into pixels. Because the
229 default drawing element is a tile, drawing functions will be passed
230 parameters in terms of number of tiles instead of number of pixels.
231 For example, to draw a single character, instead of using bitmaps,
232 an index to an array of bitmaps will be used. To clear or move a
233 rectangular section of a screen, the rectangle will be described in
234 terms of number of tiles in the x- and y-axis.
236 This is particularly important to one driver, matroxfb. If
239 comment "Frame buffer hardware drivers"
243 tristate "Cirrus Logic support"
244 depends on FB && (ZORRO || PCI)
245 select FB_CFB_FILLRECT
246 select FB_CFB_COPYAREA
247 select FB_CFB_IMAGEBLIT
249 This enables support for Cirrus Logic GD542x/543x based boards on
250 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
252 If you have a PCI-based system, this enables support for these
253 chips: GD-543x, GD-544x, GD-5480.
255 Please read the file <file:Documentation/fb/cirrusfb.txt>.
257 Say N unless you have such a graphics board or plan to get one
258 before you next recompile the kernel.
261 tristate "Permedia2 support"
262 depends on FB && ((AMIGA && BROKEN) || PCI)
263 select FB_CFB_FILLRECT
264 select FB_CFB_COPYAREA
265 select FB_CFB_IMAGEBLIT
267 This is the frame buffer device driver for cards based on
268 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
269 The driver was tested on the following cards:
270 Diamond FireGL 1000 PRO AGP
271 ELSA Gloria Synergy PCI
272 Appian Jeronimo PRO (both heads) PCI
273 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
274 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
275 ASK Graphic Blaster Exxtreme AGP
277 To compile this driver as a module, choose M here: the
278 module will be called pm2fb.
280 config FB_PM2_FIFO_DISCONNECT
281 bool "enable FIFO disconnect feature"
282 depends on FB_PM2 && PCI
284 Support the Permedia2 FIFO disconnect feature.
287 tristate "ARM PrimeCell PL110 support"
288 depends on FB && ARM && ARM_AMBA
289 select FB_CFB_FILLRECT
290 select FB_CFB_COPYAREA
291 select FB_CFB_IMAGEBLIT
293 This framebuffer device driver is for the ARM PrimeCell PL110
294 Colour LCD controller. ARM PrimeCells provide the building
295 blocks for System on a Chip devices.
297 If you want to compile this as a module (=code which can be
298 inserted into and removed from the running kernel), say M
299 here and read <file:Documentation/kbuild/modules.txt>. The module
300 will be called amba-clcd.
304 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
306 default FB_ARMCLCD_SHARP_LQ035Q7DB02
308 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
309 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
311 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
312 color QVGA, HRTFT panel. The LogicPD device includes
313 an integrated HRTFT controller IC.
314 The native resolution is 240x320.
316 config FB_ARMCLCD_SHARP_LQ057Q3DC02
317 bool "LogicPD LCD 5.7\" QVGA"
319 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
320 color QVGA, TFT panel. The LogicPD device includes an
321 The native resolution is 320x240.
323 config FB_ARMCLCD_SHARP_LQ64D343
324 bool "LogicPD LCD 6.4\" VGA"
326 This is an implementation of the Sharp LQ64D343, a 6.4"
327 color VGA, TFT panel. The LogicPD device includes an
328 The native resolution is 640x480.
330 config FB_ARMCLCD_SHARP_LQ10D368
331 bool "LogicPD LCD 10.4\" VGA"
333 This is an implementation of the Sharp LQ10D368, a 10.4"
334 color VGA, TFT panel. The LogicPD device includes an
335 The native resolution is 640x480.
338 config FB_ARMCLCD_SHARP_LQ121S1DG41
339 bool "LogicPD LCD 12.1\" SVGA"
341 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
342 color SVGA, TFT panel. The LogicPD device includes an
343 The native resolution is 800x600.
345 This panel requires a clock rate may be an integer fraction
346 of the base LCDCLK frequency. The driver will select the
347 highest frequency available that is lower than the maximum
348 allowed. The panel may flicker if the clock rate is
349 slower than the recommended minimum.
351 config FB_ARMCLCD_AUO_A070VW01_WIDE
352 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
354 This is an implementation of the AU Optronics, a 7.0"
355 WIDE Color. The native resolution is 234x480.
357 config FB_ARMCLCD_HITACHI
358 bool "Hitachi Wide Screen 800x480"
360 This is an implementation of the Hitachi 800x480.
366 bool "Acorn VIDC support"
367 depends on (FB = y) && ARM && ARCH_ACORN
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
372 This is the frame buffer device driver for the Acorn VIDC graphics
373 hardware found in Acorn RISC PCs and other ARM-based machines. If
377 bool "CLPS711X LCD support"
378 depends on (FB = y) && ARM && ARCH_CLPS711X
379 select FB_CFB_FILLRECT
380 select FB_CFB_COPYAREA
381 select FB_CFB_IMAGEBLIT
383 Say Y to enable the Framebuffer driver for the CLPS7111 and
387 bool "SA-1100 LCD support"
388 depends on (FB = y) && ARM && ARCH_SA1100
389 select FB_CFB_FILLRECT
390 select FB_CFB_COPYAREA
391 select FB_CFB_IMAGEBLIT
393 This is a framebuffer device for the SA-1100 LCD Controller.
394 See <http://www.linux-fbdev.org/> for information on framebuffer
397 If you plan to use the LCD display with your SA-1100 system, say
401 tristate "Motorola i.MX LCD support"
402 depends on FB && (ARCH_MX1 || ARCH_MX2)
403 select FB_CFB_FILLRECT
404 select FB_CFB_COPYAREA
405 select FB_CFB_IMAGEBLIT
408 tristate "CyberPro 2000/2010/5000 support"
409 depends on FB && PCI && (BROKEN || !SPARC64)
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
414 This enables support for the Integraphics CyberPro 20x0 and 5000
415 VGA chips used in the Rebel.com Netwinder and other machines.
416 Say Y if you have a NetWinder or a graphics card containing this
417 device, otherwise say N.
421 depends on (FB = y) && APOLLO
423 select FB_CFB_FILLRECT
424 select FB_CFB_IMAGEBLIT
428 depends on (FB = y) && Q40
430 select FB_CFB_FILLRECT
431 select FB_CFB_COPYAREA
432 select FB_CFB_IMAGEBLIT
435 tristate "Amiga native chipset support"
436 depends on FB && AMIGA
438 This is the frame buffer device driver for the builtin graphics
439 chipset found in Amigas.
441 To compile this driver as a module, choose M here: the
442 module will be called amifb.
445 bool "Amiga OCS chipset support"
448 This enables support for the original Agnus and Denise video chips,
449 found in the Amiga 1000 and most A500's and A2000's. If you intend
450 to run Linux on any of these systems, say Y; otherwise say N.
453 bool "Amiga ECS chipset support"
456 This enables support for the Enhanced Chip Set, found in later
457 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
458 you intend to run Linux on any of these systems, say Y; otherwise
462 bool "Amiga AGA chipset support"
465 This enables support for the Advanced Graphics Architecture (also
466 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
467 and CD32. If you intend to run Linux on any of these systems, say Y;
471 bool "Amiga FrameMaster II/Rainbow II support"
472 depends on (FB = y) && ZORRO
473 select FB_CFB_FILLRECT
474 select FB_CFB_COPYAREA
475 select FB_CFB_IMAGEBLIT
477 This is the frame buffer device driver for the Amiga FrameMaster
478 card from BSC (exhibited 1992 but not shipped as a CBM product).
481 tristate "Arc Monochrome LCD board support"
483 select FB_SYS_FILLRECT
484 select FB_SYS_COPYAREA
485 select FB_SYS_IMAGEBLIT
488 This enables support for the Arc Monochrome LCD board. The board
489 is based on the KS-108 lcd controller and is typically a matrix
490 of 2*n chips. This driver was tested with a 128x64 panel. This
491 driver supports it for use with x86 SBCs through a 16 bit GPIO
492 interface (8 bit data, 8 bit control). If you anticipate using
493 this driver, say Y or M; otherwise say N. You must specify the
494 GPIO IO address to be used for setting control and data.
497 bool "Atari native chipset support"
498 depends on (FB = y) && ATARI
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
503 This is the frame buffer device driver for the builtin graphics
504 chipset found in Ataris.
507 bool "Open Firmware frame buffer device support"
508 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
509 select FB_CFB_FILLRECT
510 select FB_CFB_COPYAREA
511 select FB_CFB_IMAGEBLIT
514 Say Y if you want support with Open Firmware for your graphics
518 bool "Apple \"control\" display support"
519 depends on (FB = y) && PPC_PMAC && PPC32
520 select FB_CFB_FILLRECT
521 select FB_CFB_COPYAREA
522 select FB_CFB_IMAGEBLIT
525 This driver supports a frame buffer for the graphics adapter in the
526 Power Macintosh 7300 and others.
529 bool "Apple \"platinum\" display support"
530 depends on (FB = y) && PPC_PMAC && PPC32
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
536 This driver supports a frame buffer for the "platinum" graphics
537 adapter in some Power Macintoshes.
540 bool "Apple \"valkyrie\" display support"
541 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
542 select FB_CFB_FILLRECT
543 select FB_CFB_COPYAREA
544 select FB_CFB_IMAGEBLIT
547 This driver supports a frame buffer for the "valkyrie" graphics
548 adapter in some Power Macintoshes.
551 bool "Chips 65550 display support"
552 depends on (FB = y) && PPC32 && PCI
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
557 This is the frame buffer device driver for the Chips & Technologies
558 65550 graphics chip in PowerBooks.
561 bool "Asiliant (Chips) 69000 display support"
562 depends on (FB = y) && PCI
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
567 This is the frame buffer device driver for the Asiliant 69030 chipset
570 bool "IMS Twin Turbo display support"
571 depends on (FB = y) && PCI
572 select FB_CFB_IMAGEBLIT
573 select FB_MACMODES if PPC
575 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
576 many Macintosh and compatible computers.
579 tristate "VGA 16-color graphics support"
580 depends on FB && (X86 || PPC)
581 select FB_CFB_FILLRECT
582 select FB_CFB_COPYAREA
583 select FB_CFB_IMAGEBLIT
585 select FONT_8x16 if FRAMEBUFFER_CONSOLE
587 This is the frame buffer device driver for VGA 16 color graphic
588 cards. Say Y if you have such a card.
590 To compile this driver as a module, choose M here: the
591 module will be called vga16fb.
593 config FB_BF54X_LQ043
594 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
595 depends on FB && (BF54x) && !BF542
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
602 config FB_BFIN_T350MCQB
603 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
604 depends on FB && BLACKFIN
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
610 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
611 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
612 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
614 config FB_BFIN_LQ035Q1
615 tristate "SHARP LQ035Q1DH02 TFT LCD"
616 depends on FB && BLACKFIN && SPI
617 select FB_CFB_FILLRECT
618 select FB_CFB_COPYAREA
619 select FB_CFB_IMAGEBLIT
622 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
623 the Blackfin Landscape LCD EZ-Extender Card.
624 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
625 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
627 To compile this driver as a module, choose M here: the
628 module will be called bfin-lq035q1-fb.
631 tristate "HP STI frame buffer device support"
632 depends on FB && PARISC
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
640 STI refers to the HP "Standard Text Interface" which is a set of
641 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
642 Enabling this option will implement the linux framebuffer device
643 using calls to the STI BIOS routines for initialisation.
645 If you enable this option, you will get a planar framebuffer device
646 /dev/fb which will work on the most common HP graphic cards of the
647 NGLE family, including the artist chips (in the 7xx and Bxxx series),
648 HCRX, HCRX24, CRX, CRX24 and VisEG series.
650 It is safe to enable this option, so you should probably say "Y".
653 bool "Generic Macintosh display support"
654 depends on (FB = y) && MAC
655 select FB_CFB_FILLRECT
656 select FB_CFB_COPYAREA
657 select FB_CFB_IMAGEBLIT
662 depends on (FB = y) && DIO
663 select FB_CFB_IMAGEBLIT
667 tristate "TGA/SFB+ framebuffer support"
668 depends on FB && (ALPHA || TC)
669 select FB_CFB_FILLRECT
670 select FB_CFB_COPYAREA
671 select FB_CFB_IMAGEBLIT
674 This is the frame buffer device driver for generic TGA and SFB+
675 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
676 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
677 TURBOchannel cards, also known as PMAGD-A, -B and -C.
679 Due to hardware limitations ZLX-E2 and E3 cards are not supported
680 for DECstation 5000/200 systems. Additionally due to firmware
681 limitations these cards may cause troubles with booting DECstation
682 5000/240 and /260 systems, but are fully supported under Linux if
683 you manage to get it going. ;-)
685 Say Y if you have one of those.
688 tristate "Userspace VESA VGA graphics support"
689 depends on FB && CONNECTOR
690 select FB_CFB_FILLRECT
691 select FB_CFB_COPYAREA
692 select FB_CFB_IMAGEBLIT
693 select FB_MODE_HELPERS
695 This is the frame buffer driver for generic VBE 2.0 compliant
696 graphic cards. It can also take advantage of VBE 3.0 features,
697 such as refresh rate adjustment.
699 This driver generally provides more features than vesafb but
700 requires a userspace helper application called 'v86d'. See
701 <file:Documentation/fb/uvesafb.txt> for more information.
706 bool "VESA VGA graphics support"
707 depends on (FB = y) && X86
708 select FB_CFB_FILLRECT
709 select FB_CFB_COPYAREA
710 select FB_CFB_IMAGEBLIT
711 select FB_BOOT_VESA_SUPPORT
713 This is the frame buffer device driver for generic VESA 2.0
714 compliant graphic cards. The older VESA 1.2 cards are not supported.
715 You will get a boot time penguin logo at no additional cost. Please
716 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
719 bool "EFI-based Framebuffer Support"
720 depends on (FB = y) && X86 && EFI
721 select FB_CFB_FILLRECT
722 select FB_CFB_COPYAREA
723 select FB_CFB_IMAGEBLIT
725 This is the EFI frame buffer device driver. If the firmware on
726 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
727 using the EFI framebuffer as your console.
730 tristate "N411 Apollo/Hecuba devkit support"
731 depends on FB && X86 && MMU
732 select FB_SYS_FILLRECT
733 select FB_SYS_COPYAREA
734 select FB_SYS_IMAGEBLIT
736 select FB_DEFERRED_IO
739 This enables support for the Apollo display controller in its
740 Hecuba form using the n411 devkit.
743 tristate "Hercules mono graphics support"
745 select FB_CFB_FILLRECT
746 select FB_CFB_COPYAREA
747 select FB_CFB_IMAGEBLIT
749 Say Y here if you have a Hercules mono graphics card.
751 To compile this driver as a module, choose M here: the
752 module will be called hgafb.
754 As this card technology is 15 years old, most people will answer N
758 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
759 depends on FB_HGA && EXPERIMENTAL
761 This will compile the Hercules mono graphics with
762 acceleration functions.
765 tristate "SGI Visual Workstation framebuffer support"
766 depends on FB && X86_VISWS
767 select FB_CFB_FILLRECT
768 select FB_CFB_COPYAREA
769 select FB_CFB_IMAGEBLIT
771 SGI Visual Workstation support for framebuffer graphics.
774 bool "SGI Graphics Backend frame buffer support"
775 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
776 select FB_CFB_FILLRECT
777 select FB_CFB_COPYAREA
778 select FB_CFB_IMAGEBLIT
780 This is the frame buffer device driver for SGI Graphics Backend.
781 This chip is used in SGI O2 and Visual Workstation 320/540.
784 int "Video memory size in MB"
788 This is the amount of memory reserved for the framebuffer,
789 which can be any value between 1MB and 8MB.
792 bool "SBUS and UPA framebuffers"
793 depends on (FB = y) && SPARC
795 Say Y if you want support for SBUS or UPA based frame buffer device.
799 depends on (FB = y) && (SPARC && FB_SBUS)
800 select FB_CFB_FILLRECT
801 select FB_CFB_COPYAREA
802 select FB_CFB_IMAGEBLIT
804 This is the frame buffer device driver for the BWtwo frame buffer.
807 bool "CGthree support"
808 depends on (FB = y) && (SPARC && FB_SBUS)
809 select FB_CFB_FILLRECT
810 select FB_CFB_COPYAREA
811 select FB_CFB_IMAGEBLIT
813 This is the frame buffer device driver for the CGthree frame buffer.
816 bool "CGsix (GX,TurboGX) support"
817 depends on (FB = y) && (SPARC && FB_SBUS)
818 select FB_CFB_COPYAREA
819 select FB_CFB_IMAGEBLIT
821 This is the frame buffer device driver for the CGsix (GX, TurboGX)
825 bool "Creator/Creator3D/Elite3D support"
826 depends on FB_SBUS && SPARC64
827 select FB_CFB_COPYAREA
828 select FB_CFB_IMAGEBLIT
830 This is the frame buffer device driver for the Creator, Creator3D,
831 and Elite3D graphics boards.
834 bool "TCX (SS4/SS5 only) support"
836 select FB_CFB_FILLRECT
837 select FB_CFB_COPYAREA
838 select FB_CFB_IMAGEBLIT
840 This is the frame buffer device driver for the TCX 24/8bit frame
844 bool "CGfourteen (SX) support"
846 select FB_CFB_FILLRECT
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This is the frame buffer device driver for the CGfourteen frame
851 buffer on Desktop SPARCsystems with the SX graphics option.
854 bool "P9100 (Sparcbook 3 only) support"
856 select FB_CFB_FILLRECT
857 select FB_CFB_COPYAREA
858 select FB_CFB_IMAGEBLIT
860 This is the frame buffer device driver for the P9100 card
861 supported on Sparcbook 3 machines.
864 bool "Leo (ZX) support"
866 select FB_CFB_FILLRECT
867 select FB_CFB_COPYAREA
868 select FB_CFB_IMAGEBLIT
870 This is the frame buffer device driver for the SBUS-based Sun ZX
871 (leo) frame buffer cards.
874 bool "IGA 168x display support"
875 depends on (FB = y) && SPARC32
876 select FB_CFB_FILLRECT
877 select FB_CFB_COPYAREA
878 select FB_CFB_IMAGEBLIT
880 This is the framebuffer device for the INTERGRAPHICS 1680 and
881 successor frame buffer cards.
884 bool "Sun XVR-500 3DLABS Wildcat support"
885 depends on (FB = y) && PCI && SPARC64
886 select FB_CFB_FILLRECT
887 select FB_CFB_COPYAREA
888 select FB_CFB_IMAGEBLIT
890 This is the framebuffer device for the Sun XVR-500 and similar
891 graphics cards based upon the 3DLABS Wildcat chipset. The driver
892 only works on sparc64 systems where the system firmware has
893 mostly initialized the card already. It is treated as a
894 completely dumb framebuffer device.
897 bool "Sun XVR-2500 3DLABS Wildcat support"
898 depends on (FB = y) && PCI && SPARC64
899 select FB_CFB_FILLRECT
900 select FB_CFB_COPYAREA
901 select FB_CFB_IMAGEBLIT
903 This is the framebuffer device for the Sun XVR-2500 and similar
904 graphics cards based upon the 3DLABS Wildcat chipset. The driver
905 only works on sparc64 systems where the system firmware has
906 mostly initialized the card already. It is treated as a
907 completely dumb framebuffer device.
910 tristate "NEC PowerVR 2 display support"
911 depends on FB && SH_DREAMCAST
912 select FB_CFB_FILLRECT
913 select FB_CFB_COPYAREA
914 select FB_CFB_IMAGEBLIT
916 Say Y here if you have a PowerVR 2 card in your box. If you plan to
917 run linux on your Dreamcast, you will have to say Y here.
918 This driver may or may not work on other PowerVR 2 cards, but is
919 totally untested. Use at your own risk. If unsure, say N.
921 To compile this driver as a module, choose M here: the
922 module will be called pvr2fb.
924 You can pass several parameters to the driver at boot time or at
925 module load time. The parameters look like "video=pvr2:XXX", where
926 the meaning of XXX can be found at the end of the main source file
927 (<file:drivers/video/pvr2fb.c>). Please see the file
928 <file:Documentation/fb/pvr2fb.txt>.
931 bool "Epson 1355 framebuffer support"
932 depends on (FB = y) && ARCH_CEIVA
933 select FB_CFB_FILLRECT
934 select FB_CFB_COPYAREA
935 select FB_CFB_IMAGEBLIT
937 Build in support for the SED1355 Epson Research Embedded RAMDAC
938 LCD/CRT Controller (since redesignated as the S1D13505) as a
939 framebuffer. Product specs at
940 <http://www.erd.epson.com/vdc/html/products.htm>.
943 tristate "Epson S1D13XXX framebuffer support"
945 select FB_CFB_FILLRECT
946 select FB_CFB_COPYAREA
947 select FB_CFB_IMAGEBLIT
949 Support for S1D13XXX framebuffer device family (currently only
950 working with S1D13806). Product specs at
951 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
954 tristate "AT91/AT32 LCD Controller support"
955 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9G10 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 || ARCH_AT91CAP9 || AVR32)
956 select FB_CFB_FILLRECT
957 select FB_CFB_COPYAREA
958 select FB_CFB_IMAGEBLIT
960 This enables support for the AT91/AT32 LCD Controller.
963 bool "Frame Buffer in internal SRAM"
964 depends on FB_ATMEL && ARCH_AT91SAM9261
966 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
967 to let frame buffer in external SDRAM.
970 bool "Use a STN display with AT91/AT32 LCD Controller"
971 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
974 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
975 Controller. Say N if you want to connect a TFT.
980 tristate "nVidia Framebuffer Support"
982 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
983 select FB_MODE_HELPERS
984 select FB_CFB_FILLRECT
985 select FB_CFB_COPYAREA
986 select FB_CFB_IMAGEBLIT
990 This driver supports graphics boards with the nVidia chips, TNT
991 and newer. For very old chipsets, such as the RIVA128, then use
993 Say Y if you have such a graphics board.
995 To compile this driver as a module, choose M here: the
996 module will be called nvidiafb.
999 bool "Enable DDC Support"
1000 depends on FB_NVIDIA
1003 This enables I2C support for nVidia Chipsets. This is used
1004 only for getting EDID information from the attached display
1005 allowing for robust video mode handling and switching.
1007 Because fbdev-2.6 requires that drivers must be able to
1008 independently validate video mode parameters, you should say Y
1011 config FB_NVIDIA_DEBUG
1012 bool "Lots of debug output"
1013 depends on FB_NVIDIA
1016 Say Y here if you want the nVidia driver to output all sorts
1017 of debugging information to provide to the maintainer when
1018 something goes wrong.
1020 config FB_NVIDIA_BACKLIGHT
1021 bool "Support for backlight control"
1022 depends on FB_NVIDIA
1025 Say Y here if you want to control the backlight of your display.
1028 tristate "nVidia Riva support"
1029 depends on FB && PCI
1030 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1031 select FB_MODE_HELPERS
1032 select FB_CFB_FILLRECT
1033 select FB_CFB_COPYAREA
1034 select FB_CFB_IMAGEBLIT
1038 This driver supports graphics boards with the nVidia Riva/Geforce
1040 Say Y if you have such a graphics board.
1042 To compile this driver as a module, choose M here: the
1043 module will be called rivafb.
1046 bool "Enable DDC Support"
1050 This enables I2C support for nVidia Chipsets. This is used
1051 only for getting EDID information from the attached display
1052 allowing for robust video mode handling and switching.
1054 Because fbdev-2.6 requires that drivers must be able to
1055 independently validate video mode parameters, you should say Y
1058 config FB_RIVA_DEBUG
1059 bool "Lots of debug output"
1063 Say Y here if you want the Riva driver to output all sorts
1064 of debugging information to provide to the maintainer when
1065 something goes wrong.
1067 config FB_RIVA_BACKLIGHT
1068 bool "Support for backlight control"
1072 Say Y here if you want to control the backlight of your display.
1075 tristate "Intel 810/815 support (EXPERIMENTAL)"
1076 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1077 select FB_MODE_HELPERS
1078 select FB_CFB_FILLRECT
1079 select FB_CFB_COPYAREA
1080 select FB_CFB_IMAGEBLIT
1083 This driver supports the on-board graphics built in to the Intel 810
1084 and 815 chipsets. Say Y if you have and plan to use such a board.
1086 To compile this driver as a module, choose M here: the
1087 module will be called i810fb.
1089 For more information, please read
1090 <file:Documentation/fb/intel810.txt>
1093 bool "use VESA Generalized Timing Formula"
1096 If you say Y, then the VESA standard, Generalized Timing Formula
1097 or GTF, will be used to calculate the required video timing values
1098 per video mode. Since the GTF allows nondiscrete timings
1099 (nondiscrete being a range of values as opposed to discrete being a
1100 set of values), you'll be able to use any combination of horizontal
1101 and vertical resolutions, and vertical refresh rates without having
1102 to specify your own timing parameters. This is especially useful
1103 to maximize the performance of an aging display, or if you just
1104 have a display with nonstandard dimensions. A VESA compliant
1105 monitor is recommended, but can still work with non-compliant ones.
1106 If you need or want this, then select this option. The timings may
1107 not be compliant with Intel's recommended values. Use at your own
1110 If you say N, the driver will revert to discrete video timings
1111 using a set recommended by Intel in their documentation.
1116 bool "Enable DDC Support"
1117 depends on FB_I810 && FB_I810_GTF
1122 tristate "Intel LE80578 (Vermilion) support"
1123 depends on FB && PCI && X86
1124 select FB_MODE_HELPERS
1125 select FB_CFB_FILLRECT
1126 select FB_CFB_COPYAREA
1127 select FB_CFB_IMAGEBLIT
1129 This driver supports the LE80578 (Vermilion Range) chipset
1131 config FB_CARILLO_RANCH
1132 tristate "Intel Carillo Ranch support"
1133 depends on FB_LE80578 && FB && PCI && X86
1135 This driver supports the LE80578 (Carillo Ranch) board
1138 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1139 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1140 select FB_MODE_HELPERS
1141 select FB_CFB_FILLRECT
1142 select FB_CFB_COPYAREA
1143 select FB_CFB_IMAGEBLIT
1144 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1145 depends on !DRM_I915
1147 This driver supports the on-board graphics built in to the Intel
1148 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1149 Say Y if you have and plan to use such a board.
1151 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1153 To compile this driver as a module, choose M here: the
1154 module will be called intelfb.
1156 For more information, please read <file:Documentation/fb/intelfb.txt>
1158 config FB_INTEL_DEBUG
1159 bool "Intel driver Debug Messages"
1162 Say Y here if you want the Intel driver to output all sorts
1163 of debugging information to provide to the maintainer when
1164 something goes wrong.
1167 bool "DDC/I2C for Intel framebuffer support"
1172 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1175 tristate "Matrox acceleration"
1176 depends on FB && PCI
1177 select FB_CFB_FILLRECT
1178 select FB_CFB_COPYAREA
1179 select FB_CFB_IMAGEBLIT
1180 select FB_TILEBLITTING
1181 select FB_MACMODES if PPC_PMAC
1183 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1184 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1185 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1186 Matrox G400, G450 or G550 card in your box.
1188 To compile this driver as a module, choose M here: the
1189 module will be called matroxfb.
1191 You can pass several parameters to the driver at boot time or at
1192 module load time. The parameters look like "video=matrox:XXX", and
1193 are described in <file:Documentation/fb/matroxfb.txt>.
1195 config FB_MATROX_MILLENIUM
1196 bool "Millennium I/II support"
1197 depends on FB_MATROX
1199 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1200 video card. If you select "Advanced lowlevel driver options" below,
1201 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1202 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1203 also use font widths different from 8.
1205 config FB_MATROX_MYSTIQUE
1206 bool "Mystique support"
1207 depends on FB_MATROX
1209 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1210 video card. If you select "Advanced lowlevel driver options" below,
1211 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1212 packed pixel and 32 bpp packed pixel. You can also use font widths
1216 bool "G100/G200/G400/G450/G550 support"
1217 depends on FB_MATROX
1219 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1220 video card. If you select "Advanced lowlevel driver options", you
1221 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1222 pixel and 32 bpp packed pixel. You can also use font widths
1225 If you need support for G400 secondary head, you must say Y to
1226 "Matrox I2C support" and "G400 second head support" right below.
1227 G450/G550 secondary head and digital output are supported without
1230 The driver starts in monitor mode. You must use the matroxset tool
1231 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1232 swap primary and secondary head outputs, or to change output mode.
1233 Secondary head driver always start in 640x480 resolution and you
1234 must use fbset to change it.
1236 Do not forget that second head supports only 16 and 32 bpp
1237 packed pixels, so it is a good idea to compile them into the kernel
1238 too. You can use only some font widths, as the driver uses generic
1239 painting procedures (the secondary head does not use acceleration
1242 G450/G550 hardware can display TV picture only from secondary CRTC,
1243 and it performs no scaling, so picture must have 525 or 625 lines.
1245 config FB_MATROX_I2C
1246 tristate "Matrox I2C support"
1247 depends on FB_MATROX
1250 This drivers creates I2C buses which are needed for accessing the
1251 DDC (I2C) bus present on all Matroxes, an I2C bus which
1252 interconnects Matrox optional devices, like MGA-TVO on G200 and
1253 G400, and the secondary head DDC bus, present on G400 only.
1255 You can say Y or M here if you want to experiment with monitor
1256 detection code. You must say Y or M here if you want to use either
1257 second head of G400 or MGA-TVO on G200 or G400.
1259 If you compile it as module, it will create a module named
1262 config FB_MATROX_MAVEN
1263 tristate "G400 second head support"
1264 depends on FB_MATROX_G && FB_MATROX_I2C
1266 WARNING !!! This support does not work with G450 !!!
1268 Say Y or M here if you want to use a secondary head (meaning two
1269 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1270 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1271 secondary head output is blanked while you are in X. With XFree
1272 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1273 the fbdev driver on first head and the fbdev driver on second head.
1275 If you compile it as module, two modules are created,
1276 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1277 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1278 also load i2c-matroxfb to get it to run.
1280 The driver starts in monitor mode and you must use the matroxset
1282 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1283 PAL or NTSC or to swap primary and secondary head outputs.
1284 Secondary head driver also always start in 640x480 resolution, you
1285 must use fbset to change it.
1287 Also do not forget that second head supports only 16 and 32 bpp
1288 packed pixels, so it is a good idea to compile them into the kernel
1289 too. You can use only some font widths, as the driver uses generic
1290 painting procedures (the secondary head does not use acceleration
1294 tristate "ATI Radeon display support"
1295 depends on FB && PCI
1296 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1297 select FB_MODE_HELPERS
1298 select FB_CFB_FILLRECT
1299 select FB_CFB_COPYAREA
1300 select FB_CFB_IMAGEBLIT
1301 select FB_MACMODES if PPC_OF
1303 Choose this option if you want to use an ATI Radeon graphics card as
1304 a framebuffer device. There are both PCI and AGP versions. You
1305 don't need to choose this to run the Radeon in plain VGA mode.
1307 There is a product page at
1308 http://apps.ati.com/ATIcompare/
1310 config FB_RADEON_I2C
1311 bool "DDC/I2C for ATI Radeon support"
1312 depends on FB_RADEON
1316 Say Y here if you want DDC/I2C support for your Radeon board.
1318 config FB_RADEON_BACKLIGHT
1319 bool "Support for backlight control"
1320 depends on FB_RADEON
1323 Say Y here if you want to control the backlight of your display.
1325 config FB_RADEON_DEBUG
1326 bool "Lots of debug output from Radeon driver"
1327 depends on FB_RADEON
1330 Say Y here if you want the Radeon driver to output all sorts
1331 of debugging information to provide to the maintainer when
1332 something goes wrong.
1335 tristate "ATI Rage128 display support"
1336 depends on FB && PCI
1337 select FB_CFB_FILLRECT
1338 select FB_CFB_COPYAREA
1339 select FB_CFB_IMAGEBLIT
1340 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1341 select FB_MACMODES if PPC_PMAC
1343 This driver supports graphics boards with the ATI Rage128 chips.
1344 Say Y if you have such a graphics board and read
1345 <file:Documentation/fb/aty128fb.txt>.
1347 To compile this driver as a module, choose M here: the
1348 module will be called aty128fb.
1350 config FB_ATY128_BACKLIGHT
1351 bool "Support for backlight control"
1352 depends on FB_ATY128
1355 Say Y here if you want to control the backlight of your display.
1358 tristate "ATI Mach64 display support" if PCI || ATARI
1359 depends on FB && !SPARC32
1360 select FB_CFB_FILLRECT
1361 select FB_CFB_COPYAREA
1362 select FB_CFB_IMAGEBLIT
1363 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1364 select FB_MACMODES if PPC
1366 This driver supports graphics boards with the ATI Mach64 chips.
1367 Say Y if you have such a graphics board.
1369 To compile this driver as a module, choose M here: the
1370 module will be called atyfb.
1373 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1374 depends on PCI && FB_ATY
1375 default y if SPARC64 && PCI
1377 Say Y here to support use of ATI's 64-bit Rage boards (or other
1378 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1379 framebuffer device. The ATI product support page for these boards
1380 is at <http://support.ati.com/products/pc/mach64/>.
1382 config FB_ATY_GENERIC_LCD
1383 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1384 depends on FB_ATY_CT
1386 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1387 Rage XC, or Rage XL chipset.
1390 bool "Mach64 GX support" if PCI
1394 Say Y here to support use of the ATI Mach64 Graphics Expression
1395 board (or other boards based on the Mach64 GX chipset) as a
1396 framebuffer device. The ATI product support page for these boards
1398 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1400 config FB_ATY_BACKLIGHT
1401 bool "Support for backlight control"
1405 Say Y here if you want to control the backlight of your display.
1408 tristate "S3 Trio/Virge support"
1409 depends on FB && PCI
1410 select FB_CFB_FILLRECT
1411 select FB_CFB_COPYAREA
1412 select FB_CFB_IMAGEBLIT
1413 select FB_TILEBLITTING
1416 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1418 Driver for graphics boards with S3 Trio / S3 Virge chip.
1421 tristate "S3 Savage support"
1422 depends on FB && PCI && EXPERIMENTAL
1423 select FB_MODE_HELPERS
1424 select FB_CFB_FILLRECT
1425 select FB_CFB_COPYAREA
1426 select FB_CFB_IMAGEBLIT
1429 This driver supports notebooks and computers with S3 Savage PCI/AGP
1432 Say Y if you have such a graphics card.
1434 To compile this driver as a module, choose M here; the module
1435 will be called savagefb.
1437 config FB_SAVAGE_I2C
1438 bool "Enable DDC2 Support"
1439 depends on FB_SAVAGE
1442 This enables I2C support for S3 Savage Chipsets. This is used
1443 only for getting EDID information from the attached display
1444 allowing for robust video mode handling and switching.
1446 Because fbdev-2.6 requires that drivers must be able to
1447 independently validate video mode parameters, you should say Y
1450 config FB_SAVAGE_ACCEL
1451 bool "Enable Console Acceleration"
1452 depends on FB_SAVAGE
1455 This option will compile in console acceleration support. If
1456 the resulting framebuffer console has bothersome glitches, then
1460 tristate "SiS/XGI display support"
1461 depends on FB && PCI
1462 select FB_CFB_FILLRECT
1463 select FB_CFB_COPYAREA
1464 select FB_CFB_IMAGEBLIT
1465 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1467 This is the frame buffer device driver for the SiS 300, 315, 330
1468 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1469 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1471 To compile this driver as a module, choose M here; the module
1472 will be called sisfb.
1475 bool "SiS 300 series support"
1478 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1481 bool "SiS 315/330/340 series and XGI support"
1484 Say Y here to support use of the SiS 315, 330 and 340 series
1485 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1486 as XGI V3XT, V5, V8 and Z7.
1489 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1490 depends on FB && PCI
1491 select FB_CFB_FILLRECT
1492 select FB_CFB_COPYAREA
1493 select FB_CFB_IMAGEBLIT
1494 select FB_SOFT_CURSOR
1498 This is the frame buffer device driver for Graphics chips of VIA
1499 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1500 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1502 Say Y if you have a VIA UniChrome graphics board.
1504 To compile this driver as a module, choose M here: the
1505 module will be called viafb.
1507 tristate "NeoMagic display support"
1508 depends on FB && PCI
1509 select FB_MODE_HELPERS
1510 select FB_CFB_FILLRECT
1511 select FB_CFB_COPYAREA
1512 select FB_CFB_IMAGEBLIT
1515 This driver supports notebooks with NeoMagic PCI chips.
1516 Say Y if you have such a graphics card.
1518 To compile this driver as a module, choose M here: the
1519 module will be called neofb.
1522 tristate "IMG Kyro support"
1523 depends on FB && PCI
1524 select FB_CFB_FILLRECT
1525 select FB_CFB_COPYAREA
1526 select FB_CFB_IMAGEBLIT
1528 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1531 To compile this driver as a module, choose M here: the
1532 module will be called kyrofb.
1535 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1536 depends on FB && PCI
1537 select FB_CFB_IMAGEBLIT
1538 select FB_CFB_FILLRECT
1539 select FB_CFB_COPYAREA
1540 select FB_MODE_HELPERS
1542 This driver supports graphics boards with the 3Dfx Banshee,
1543 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1544 such a graphics board.
1546 To compile this driver as a module, choose M here: the
1547 module will be called tdfxfb.
1549 config FB_3DFX_ACCEL
1550 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1551 depends on FB_3DFX && EXPERIMENTAL
1553 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1554 device driver with acceleration functions.
1557 bool "Enable DDC/I2C support"
1558 depends on FB_3DFX && EXPERIMENTAL
1562 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1565 tristate "3Dfx Voodoo Graphics (sst1) support"
1566 depends on FB && PCI
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1571 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1572 Voodoo2 (cvg) based graphics card.
1574 To compile this driver as a module, choose M here: the
1575 module will be called sstfb.
1577 WARNING: Do not use any application that uses the 3D engine
1578 (namely glide) while using this driver.
1579 Please read the <file:Documentation/fb/sstfb.txt> for supported
1580 options and other important info support.
1583 tristate "VIA VT8623 support"
1584 depends on FB && PCI
1585 select FB_CFB_FILLRECT
1586 select FB_CFB_COPYAREA
1587 select FB_CFB_IMAGEBLIT
1588 select FB_TILEBLITTING
1591 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1593 Driver for CastleRock integrated graphics core in the
1594 VIA VT8623 [Apollo CLE266] chipset.
1597 tristate "Trident/CyberXXX/CyberBlade support"
1598 depends on FB && PCI
1599 select FB_CFB_FILLRECT
1600 select FB_CFB_COPYAREA
1601 select FB_CFB_IMAGEBLIT
1603 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1604 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1606 There are also integrated versions of these chips called CyberXXXX,
1607 CyberImage or CyberBlade. These chips are mostly found in laptops
1608 but also on some motherboards including early VIA EPIA motherboards.
1609 For more information, read <file:Documentation/fb/tridentfb.txt>
1611 Say Y if you have such a graphics board.
1613 To compile this driver as a module, choose M here: the
1614 module will be called tridentfb.
1617 tristate "ARK 2000PV support"
1618 depends on FB && PCI
1619 select FB_CFB_FILLRECT
1620 select FB_CFB_COPYAREA
1621 select FB_CFB_IMAGEBLIT
1622 select FB_TILEBLITTING
1625 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1627 Driver for PCI graphics boards with ARK 2000PV chip
1628 and ICS 5342 RAMDAC.
1631 tristate "Permedia3 support (EXPERIMENTAL)"
1632 depends on FB && PCI && EXPERIMENTAL
1633 select FB_CFB_FILLRECT
1634 select FB_CFB_COPYAREA
1635 select FB_CFB_IMAGEBLIT
1637 This is the frame buffer device driver for the 3DLabs Permedia3
1638 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1639 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1640 and maybe other boards.
1643 tristate "Fujitsu carmine frame buffer support"
1644 depends on FB && PCI
1645 select FB_CFB_FILLRECT
1646 select FB_CFB_COPYAREA
1647 select FB_CFB_IMAGEBLIT
1649 This is the frame buffer device driver for the Fujitsu Carmine chip.
1650 The driver provides two independent frame buffer devices.
1653 depends on FB_CARMINE
1654 prompt "DRAM timing"
1655 default FB_CARMINE_DRAM_EVAL
1657 config FB_CARMINE_DRAM_EVAL
1658 bool "Eval board timings"
1660 Use timings which work on the eval card.
1662 config CARMINE_DRAM_CUSTOM
1663 bool "Custom board timings"
1665 Use custom board timings.
1669 bool "Au1100 LCD Driver"
1670 depends on (FB = y) && MIPS && SOC_AU1100
1671 select FB_CFB_FILLRECT
1672 select FB_CFB_COPYAREA
1673 select FB_CFB_IMAGEBLIT
1675 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1676 various panels and CRTs by passing in kernel cmd line option
1677 au1100fb:panel=<name>.
1680 bool "Au1200 LCD Driver"
1681 depends on (FB = y) && MIPS && SOC_AU1200
1682 select FB_CFB_FILLRECT
1683 select FB_CFB_COPYAREA
1684 select FB_CFB_IMAGEBLIT
1686 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1687 various panels and CRTs by passing in kernel cmd line option
1688 au1200fb:panel=<name>.
1690 source "drivers/video/geode/Kconfig"
1693 tristate "HD64461 Frame Buffer support"
1694 depends on FB && HD64461
1695 select FB_CFB_FILLRECT
1696 select FB_CFB_COPYAREA
1697 select FB_CFB_IMAGEBLIT
1699 This is the frame buffer device driver for the Hitachi HD64461 LCD
1703 bool "PMAG-AA TURBOchannel framebuffer support"
1704 depends on (FB = y) && TC
1705 select FB_CFB_FILLRECT
1706 select FB_CFB_COPYAREA
1707 select FB_CFB_IMAGEBLIT
1709 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1710 used mainly in the MIPS-based DECstation series.
1713 tristate "PMAG-BA TURBOchannel framebuffer support"
1715 select FB_CFB_FILLRECT
1716 select FB_CFB_COPYAREA
1717 select FB_CFB_IMAGEBLIT
1719 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1720 used mainly in the MIPS-based DECstation series.
1723 tristate "PMAGB-B TURBOchannel framebuffer support"
1725 select FB_CFB_FILLRECT
1726 select FB_CFB_COPYAREA
1727 select FB_CFB_IMAGEBLIT
1729 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1730 in the MIPS-based DECstation series. The card is currently only
1731 supported in 1280x1024x8 mode.
1734 bool "Maxine (Personal DECstation) onboard framebuffer support"
1735 depends on (FB = y) && MACH_DECSTATION
1736 select FB_CFB_FILLRECT
1737 select FB_CFB_COPYAREA
1738 select FB_CFB_IMAGEBLIT
1740 Support for the onboard framebuffer (1024x768x8) in the Personal
1741 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1745 bool "G364 frame buffer support"
1746 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1747 select FB_CFB_FILLRECT
1748 select FB_CFB_COPYAREA
1749 select FB_CFB_IMAGEBLIT
1751 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1752 Olivetti M700-10 systems.
1755 bool "Motorola 68328 native frame buffer support"
1756 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1757 select FB_CFB_FILLRECT
1758 select FB_CFB_COPYAREA
1759 select FB_CFB_IMAGEBLIT
1761 Say Y here if you want to support the built-in frame buffer of
1762 the Motorola 68328 CPU family.
1765 tristate "PXA168/910 LCD framebuffer support"
1766 depends on FB && (CPU_PXA168 || CPU_PXA910)
1767 select FB_CFB_FILLRECT
1768 select FB_CFB_COPYAREA
1769 select FB_CFB_IMAGEBLIT
1771 Frame buffer driver for the built-in LCD controller in the Marvell
1775 tristate "PXA LCD framebuffer support"
1776 depends on FB && ARCH_PXA
1777 select FB_CFB_FILLRECT
1778 select FB_CFB_COPYAREA
1779 select FB_CFB_IMAGEBLIT
1781 Frame buffer driver for the built-in LCD controller in the Intel
1784 This driver is also available as a module ( = code which can be
1785 inserted and removed from the running kernel whenever you want). The
1786 module will be called pxafb. If you want to compile it as a module,
1787 say M here and read <file:Documentation/kbuild/modules.txt>.
1791 config FB_PXA_OVERLAY
1792 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1794 depends on FB_PXA && (PXA27x || PXA3xx)
1796 config FB_PXA_SMARTPANEL
1797 bool "PXA Smartpanel LCD support"
1801 config FB_PXA_PARAMETERS
1802 bool "PXA LCD command line parameters"
1806 Enable the use of kernel command line or module parameters
1807 to configure the physical properties of the LCD panel when
1808 using the PXA LCD driver.
1810 This option allows you to override the panel parameters
1811 supplied by the platform in order to support multiple
1812 different models of flatpanel. If you will only be using a
1813 single model of flatpanel then you can safely leave this
1816 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1819 tristate "2700G LCD framebuffer support"
1820 depends on FB && ARCH_PXA
1821 select FB_CFB_FILLRECT
1822 select FB_CFB_COPYAREA
1823 select FB_CFB_IMAGEBLIT
1825 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1829 bool "Enable debugging info via debugfs"
1830 depends on FB_MBX && DEBUG_FS
1833 Enable this if you want debugging information using the debug
1834 filesystem (debugfs)
1839 tristate "Freescale DIU framebuffer support"
1840 depends on FB && FSL_SOC
1841 select FB_CFB_FILLRECT
1842 select FB_CFB_COPYAREA
1843 select FB_CFB_IMAGEBLIT
1844 select PPC_LIB_RHEAP
1846 Framebuffer driver for the Freescale SoC DIU
1849 tristate "W100 frame buffer support"
1850 depends on FB && ARCH_PXA
1851 select FB_CFB_FILLRECT
1852 select FB_CFB_COPYAREA
1853 select FB_CFB_IMAGEBLIT
1855 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1856 It can also drive the w3220 chip found on iPAQ hx4700.
1858 This driver is also available as a module ( = code which can be
1859 inserted and removed from the running kernel whenever you want). The
1860 module will be called w100fb. If you want to compile it as a module,
1861 say M here and read <file:Documentation/kbuild/modules.txt>.
1865 config FB_SH_MOBILE_LCDC
1866 tristate "SuperH Mobile LCDC framebuffer support"
1867 depends on FB && SUPERH && HAVE_CLK
1868 select FB_SYS_FILLRECT
1869 select FB_SYS_COPYAREA
1870 select FB_SYS_IMAGEBLIT
1872 select FB_DEFERRED_IO
1874 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1877 tristate "Toshiba Mobile IO FrameBuffer support"
1878 depends on FB && MFD_CORE
1879 select FB_CFB_FILLRECT
1880 select FB_CFB_COPYAREA
1881 select FB_CFB_IMAGEBLIT
1883 Frame buffer driver for the Toshiba Mobile IO integrated as found
1884 on the Sharp SL-6000 series
1886 This driver is also available as a module ( = code which can be
1887 inserted and removed from the running kernel whenever you want). The
1888 module will be called tmiofb. If you want to compile it as a module,
1889 say M here and read <file:Documentation/kbuild/modules.txt>.
1893 config FB_TMIO_ACCELL
1894 bool "tmiofb acceleration"
1899 tristate "Samsung S3C framebuffer support"
1900 depends on FB && ARCH_S3C64XX
1901 select FB_CFB_FILLRECT
1902 select FB_CFB_COPYAREA
1903 select FB_CFB_IMAGEBLIT
1905 Frame buffer driver for the built-in FB controller in the Samsung
1906 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1907 and the S3C64XX series such as the S3C6400 and S3C6410.
1909 These chips all have the same basic framebuffer design with the
1910 actual capabilities depending on the chip. For instance the S3C6400
1911 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1912 currently only have two.
1914 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1916 config FB_S3C_DEBUG_REGWRITE
1917 bool "Debug register writes"
1920 Show all register writes via printk(KERN_DEBUG)
1923 tristate "S3C2410 LCD framebuffer support"
1924 depends on FB && ARCH_S3C2410
1925 select FB_CFB_FILLRECT
1926 select FB_CFB_COPYAREA
1927 select FB_CFB_IMAGEBLIT
1929 Frame buffer driver for the built-in LCD controller in the Samsung
1932 This driver is also available as a module ( = code which can be
1933 inserted and removed from the running kernel whenever you want). The
1934 module will be called s3c2410fb. If you want to compile it as a module,
1935 say M here and read <file:Documentation/kbuild/modules.txt>.
1938 config FB_S3C2410_DEBUG
1939 bool "S3C2410 lcd debug messages"
1940 depends on FB_S3C2410
1942 Turn on debugging messages. Note that you can set/unset at run time
1946 tristate "Silicon Motion SM501 framebuffer support"
1947 depends on FB && MFD_SM501
1948 select FB_CFB_FILLRECT
1949 select FB_CFB_COPYAREA
1950 select FB_CFB_IMAGEBLIT
1952 Frame buffer driver for the CRT and LCD controllers in the Silicon
1955 This driver is also available as a module ( = code which can be
1956 inserted and removed from the running kernel whenever you want). The
1957 module will be called sm501fb. If you want to compile it as a module,
1958 say M here and read <file:Documentation/kbuild/modules.txt>.
1963 config FB_PNX4008_DUM
1964 tristate "Display Update Module support on Philips PNX4008 board"
1965 depends on FB && ARCH_PNX4008
1967 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1969 config FB_PNX4008_DUM_RGB
1970 tristate "RGB Framebuffer support on Philips PNX4008 board"
1971 depends on FB_PNX4008_DUM
1972 select FB_CFB_FILLRECT
1973 select FB_CFB_COPYAREA
1974 select FB_CFB_IMAGEBLIT
1976 Say Y here to enable support for PNX4008 RGB Framebuffer
1978 config FB_IBM_GXT4500
1979 tristate "Framebuffer support for IBM GXT4500P adaptor"
1980 depends on FB && PPC
1981 select FB_CFB_FILLRECT
1982 select FB_CFB_COPYAREA
1983 select FB_CFB_IMAGEBLIT
1985 Say Y here to enable support for the IBM GXT4500P display
1986 adaptor, found on some IBM System P (pSeries) machines.
1989 tristate "PS3 GPU framebuffer driver"
1990 depends on FB && PS3_PS3AV
1991 select FB_SYS_FILLRECT
1992 select FB_SYS_COPYAREA
1993 select FB_SYS_IMAGEBLIT
1995 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1997 Include support for the virtual frame buffer in the PS3 platform.
1999 config FB_PS3_DEFAULT_SIZE_M
2000 int "PS3 default frame buffer size (in MiB)"
2004 This is the default size (in MiB) of the virtual frame buffer in
2006 The default value can be overridden on the kernel command line
2007 using the "ps3fb" option (e.g. "ps3fb=9M");
2010 tristate "Xilinx frame buffer support"
2011 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2012 select FB_CFB_FILLRECT
2013 select FB_CFB_COPYAREA
2014 select FB_CFB_IMAGEBLIT
2016 Include support for the Xilinx ML300/ML403 reference design
2017 framebuffer. ML300 carries a 640*480 LCD display on the board,
2018 ML403 uses a standard DB15 VGA connector.
2021 tristate "Cobalt server LCD frame buffer support"
2022 depends on FB && MIPS_COBALT
2025 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2026 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2027 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2028 select FB_CFB_FILLRECT
2029 select FB_CFB_COPYAREA
2030 select FB_CFB_IMAGEBLIT
2032 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2033 (D)STN/TFT LCD Controller.
2034 Supports display resolutions up to 1024x1024 pixel, grayscale and
2035 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2036 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2037 panels <= 320 pixel horizontal resolution.
2040 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2041 depends on FB && ARCH_DAVINCI_DA8XX
2042 select FB_CFB_FILLRECT
2043 select FB_CFB_COPYAREA
2044 select FB_CFB_IMAGEBLIT
2046 This is the frame buffer device driver for the TI LCD controller
2047 found on DA8xx/OMAP-L1xx SoCs.
2051 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2053 select FB_SYS_FILLRECT
2054 select FB_SYS_COPYAREA
2055 select FB_SYS_IMAGEBLIT
2058 This is a `virtual' frame buffer device. It operates on a chunk of
2059 unswappable kernel memory instead of on the memory of a graphics
2060 board. This means you cannot see any output sent to this frame
2061 buffer device, while it does consume precious memory. The main use
2062 of this frame buffer device is testing and debugging the frame
2063 buffer subsystem. Do NOT enable it for normal systems! To protect
2064 the innocent, it has to be enabled explicitly at boot time using the
2065 kernel option `video=vfb:'.
2067 To compile this driver as a module, choose M here: the
2068 module will be called vfb. In order to load it, you must use
2069 the vfb_enable=1 option.
2073 config XEN_FBDEV_FRONTEND
2074 tristate "Xen virtual frame buffer support"
2075 depends on FB && XEN
2076 select FB_SYS_FILLRECT
2077 select FB_SYS_COPYAREA
2078 select FB_SYS_IMAGEBLIT
2080 select FB_DEFERRED_IO
2083 This driver implements the front-end of the Xen virtual
2084 frame buffer driver. It communicates with a back-end
2088 tristate "E-Ink Metronome/8track controller support"
2090 select FB_SYS_FILLRECT
2091 select FB_SYS_COPYAREA
2092 select FB_SYS_IMAGEBLIT
2094 select FB_DEFERRED_IO
2096 This driver implements support for the E-Ink Metronome
2097 controller. The pre-release name for this device was 8track
2098 and could also have been called by some vendors as PVI-nnnn.
2101 tristate "Fujitsu MB862xx GDC support"
2103 select FB_CFB_FILLRECT
2104 select FB_CFB_COPYAREA
2105 select FB_CFB_IMAGEBLIT
2107 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2109 config FB_MB862XX_PCI_GDC
2110 bool "Carmine/Coral-P(A) GDC"
2111 depends on PCI && FB_MB862XX
2113 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2114 PCI graphics controller devices.
2116 config FB_MB862XX_LIME
2118 depends on FB_MB862XX
2119 depends on OF && !FB_MB862XX_PCI_GDC
2121 select FB_FOREIGN_ENDIAN
2122 select FB_LITTLE_ENDIAN
2124 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2127 tristate "EP93XX frame buffer support"
2128 depends on FB && ARCH_EP93XX
2129 select FB_CFB_FILLRECT
2130 select FB_CFB_COPYAREA
2131 select FB_CFB_IMAGEBLIT
2133 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2134 This driver is also available as a module. The module will be called
2137 config FB_PRE_INIT_FB
2138 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2139 depends on FB_MB862XX_LIME
2141 Select this option if display contents should be inherited as set by
2146 depends on FB && ARCH_MSM
2147 select FB_CFB_FILLRECT
2148 select FB_CFB_COPYAREA
2149 select FB_CFB_IMAGEBLIT
2153 tristate "MX3 Framebuffer support"
2154 depends on FB && MX3_IPU
2155 select FB_CFB_FILLRECT
2156 select FB_CFB_COPYAREA
2157 select FB_CFB_IMAGEBLIT
2160 This is a framebuffer device for the i.MX31 LCD Controller. So
2161 far only synchronous displays are supported. If you plan to use
2162 an LCD display with your i.MX31 system, say Y here.
2164 config FB_BROADSHEET
2165 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2167 select FB_SYS_FILLRECT
2168 select FB_SYS_COPYAREA
2169 select FB_SYS_IMAGEBLIT
2171 select FB_DEFERRED_IO
2173 This driver implements support for the E-Ink Broadsheet
2174 controller. The release name for this device was Epson S1D13521
2175 and could also have been called by other names when coupled with
2178 source "drivers/video/omap/Kconfig"
2180 source "drivers/video/backlight/Kconfig"
2181 source "drivers/video/display/Kconfig"
2184 source "drivers/video/console/Kconfig"
2187 if FB || SGI_NEWPORT_CONSOLE
2188 source "drivers/video/logo/Kconfig"