5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/gpu/drm/Kconfig"
16 config VIDEO_OUTPUT_CONTROL
17 tristate "Lowlevel video output switch controls"
19 This framework adds support for low-level control of the video
23 tristate "Support for frame buffer devices"
25 The frame buffer device provides an abstraction for the graphics
26 hardware. It represents the frame buffer of some video hardware and
27 allows application software to access the graphics hardware through
28 a well-defined interface, so the software doesn't need to know
29 anything about the low-level (hardware register) stuff.
31 Frame buffer devices work identically across the different
32 architectures supported by Linux and make the implementation of
33 application programs easier and more portable; at this point, an X
34 server exists which uses the frame buffer device exclusively.
35 On several non-X86 architectures, the frame buffer device is the
36 only way to use the graphics hardware.
38 The device is accessed through special device nodes, usually located
39 in the /dev directory, i.e. /dev/fb*.
41 You need an utility program called fbset to make full use of frame
42 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
43 and the Framebuffer-HOWTO at
44 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
47 Say Y here and to the driver for your graphics board below if you
48 are compiling a kernel for a non-x86 architecture.
50 If you are compiling for the x86 architecture, you can say Y if you
51 want to play with it, but it is not essential. Please note that
52 running graphical applications that directly touch the hardware
53 (e.g. an accelerated X server) and that are not frame buffer
54 device-aware may cause unexpected results. If unsure, say N.
57 bool "Enable firmware EDID"
61 This enables access to the EDID transferred from the firmware.
62 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
63 transfers do not work for your driver and if you are using
64 nvidiafb, i810fb or savagefb.
66 In general, choosing Y for this option is safe. If you
67 experience extremely long delays while booting before you get
68 something on your display, try setting this to N. Matrox cards in
69 combination with certain motherboards and monitors are known to
70 suffer from this problem.
79 config FB_CFB_FILLRECT
84 Include the cfb_fillrect function for generic software rectangle
85 filling. This is used by drivers that don't provide their own
86 (accelerated) version.
88 config FB_CFB_COPYAREA
93 Include the cfb_copyarea function for generic software area copying.
94 This is used by drivers that don't provide their own (accelerated)
97 config FB_CFB_IMAGEBLIT
102 Include the cfb_imageblit function for generic software image
103 blitting. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_REV_PIXELS_IN_BYTE
111 Allow generic frame-buffer functions to work on displays with 1, 2
112 and 4 bits per pixel depths which has opposite order of pixels in
113 byte order to bytes in long order.
115 config FB_SYS_FILLRECT
120 Include the sys_fillrect function for generic software rectangle
121 filling. This is used by drivers that don't provide their own
122 (accelerated) version and the framebuffer is in system RAM.
124 config FB_SYS_COPYAREA
129 Include the sys_copyarea function for generic software area copying.
130 This is used by drivers that don't provide their own (accelerated)
131 version and the framebuffer is in system RAM.
133 config FB_SYS_IMAGEBLIT
138 Include the sys_imageblit function for generic software image
139 blitting. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 menuconfig FB_FOREIGN_ENDIAN
143 bool "Framebuffer foreign endianness support"
146 This menu will let you enable support for the framebuffers with
147 non-native endianness (e.g. Little-Endian framebuffer on a
148 Big-Endian machine). Most probably you don't have such hardware,
149 so it's safe to say "n" here.
152 prompt "Choice endianness support"
153 depends on FB_FOREIGN_ENDIAN
155 config FB_BOTH_ENDIAN
156 bool "Support for Big- and Little-Endian framebuffers"
159 bool "Support for Big-Endian framebuffers only"
161 config FB_LITTLE_ENDIAN
162 bool "Support for Little-Endian framebuffers only"
171 config FB_DEFERRED_IO
178 depends on FB_DEFERRED_IO
185 Common utility functions useful to fbdev drivers of VGA-based
196 select BACKLIGHT_LCD_SUPPORT
197 select BACKLIGHT_CLASS_DEVICE
200 config FB_MODE_HELPERS
201 bool "Enable Video Mode Handling Helpers"
205 This enables functions for handling video modes using the
206 Generalized Timing Formula and the EDID parser. A few drivers rely
207 on this feature such as the radeonfb, rivafb, and the i810fb. If
208 your driver does not take advantage of this feature, choosing Y will
209 just increase the kernel size by about 5K.
211 config FB_TILEBLITTING
212 bool "Enable Tile Blitting Support"
216 This enables tile blitting. Tile blitting is a drawing technique
217 where the screen is divided into rectangular sections (tiles), whereas
218 the standard blitting divides the screen into pixels. Because the
219 default drawing element is a tile, drawing functions will be passed
220 parameters in terms of number of tiles instead of number of pixels.
221 For example, to draw a single character, instead of using bitmaps,
222 an index to an array of bitmaps will be used. To clear or move a
223 rectangular section of a screen, the rectangle will be described in
224 terms of number of tiles in the x- and y-axis.
226 This is particularly important to one driver, matroxfb. If
229 comment "Frame buffer hardware drivers"
233 tristate "Cirrus Logic support"
234 depends on FB && (ZORRO || PCI)
235 select FB_CFB_FILLRECT
236 select FB_CFB_COPYAREA
237 select FB_CFB_IMAGEBLIT
239 This enables support for Cirrus Logic GD542x/543x based boards on
240 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
242 If you have a PCI-based system, this enables support for these
243 chips: GD-543x, GD-544x, GD-5480.
245 Please read the file <file:Documentation/fb/cirrusfb.txt>.
247 Say N unless you have such a graphics board or plan to get one
248 before you next recompile the kernel.
251 tristate "Permedia2 support"
252 depends on FB && ((AMIGA && BROKEN) || PCI)
253 select FB_CFB_FILLRECT
254 select FB_CFB_COPYAREA
255 select FB_CFB_IMAGEBLIT
257 This is the frame buffer device driver for cards based on
258 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
259 The driver was tested on the following cards:
260 Diamond FireGL 1000 PRO AGP
261 ELSA Gloria Synergy PCI
262 Appian Jeronimo PRO (both heads) PCI
263 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
264 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
265 ASK Graphic Blaster Exxtreme AGP
267 To compile this driver as a module, choose M here: the
268 module will be called pm2fb.
270 config FB_PM2_FIFO_DISCONNECT
271 bool "enable FIFO disconnect feature"
272 depends on FB_PM2 && PCI
274 Support the Permedia2 FIFO disconnect feature.
277 tristate "ARM PrimeCell PL110 support"
278 depends on FB && ARM && ARM_AMBA
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
283 This framebuffer device driver is for the ARM PrimeCell PL110
284 Colour LCD controller. ARM PrimeCells provide the building
285 blocks for System on a Chip devices.
287 If you want to compile this as a module (=code which can be
288 inserted into and removed from the running kernel), say M
289 here and read <file:Documentation/kbuild/modules.txt>. The module
290 will be called amba-clcd.
294 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
296 default FB_ARMCLCD_SHARP_LQ035Q7DB02
298 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
299 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
301 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
302 color QVGA, HRTFT panel. The LogicPD device includes
303 an integrated HRTFT controller IC.
304 The native resolution is 240x320.
306 config FB_ARMCLCD_SHARP_LQ057Q3DC02
307 bool "LogicPD LCD 5.7\" QVGA"
309 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
310 color QVGA, TFT panel. The LogicPD device includes an
311 The native resolution is 320x240.
313 config FB_ARMCLCD_SHARP_LQ64D343
314 bool "LogicPD LCD 6.4\" VGA"
316 This is an implementation of the Sharp LQ64D343, a 6.4"
317 color VGA, TFT panel. The LogicPD device includes an
318 The native resolution is 640x480.
320 config FB_ARMCLCD_SHARP_LQ10D368
321 bool "LogicPD LCD 10.4\" VGA"
323 This is an implementation of the Sharp LQ10D368, a 10.4"
324 color VGA, TFT panel. The LogicPD device includes an
325 The native resolution is 640x480.
328 config FB_ARMCLCD_SHARP_LQ121S1DG41
329 bool "LogicPD LCD 12.1\" SVGA"
331 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
332 color SVGA, TFT panel. The LogicPD device includes an
333 The native resolution is 800x600.
335 This panel requires a clock rate may be an integer fraction
336 of the base LCDCLK frequency. The driver will select the
337 highest frequency available that is lower than the maximum
338 allowed. The panel may flicker if the clock rate is
339 slower than the recommended minimum.
341 config FB_ARMCLCD_AUO_A070VW01_WIDE
342 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
344 This is an implementation of the AU Optronics, a 7.0"
345 WIDE Color. The native resolution is 234x480.
347 config FB_ARMCLCD_HITACHI
348 bool "Hitachi Wide Screen 800x480"
350 This is an implementation of the Hitachi 800x480.
356 bool "Acorn VIDC support"
357 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
358 select FB_CFB_FILLRECT
359 select FB_CFB_COPYAREA
360 select FB_CFB_IMAGEBLIT
362 This is the frame buffer device driver for the Acorn VIDC graphics
363 hardware found in Acorn RISC PCs and other ARM-based machines. If
367 bool "CLPS711X LCD support"
368 depends on (FB = y) && ARM && ARCH_CLPS711X
369 select FB_CFB_FILLRECT
370 select FB_CFB_COPYAREA
371 select FB_CFB_IMAGEBLIT
373 Say Y to enable the Framebuffer driver for the CLPS7111 and
377 bool "SA-1100 LCD support"
378 depends on (FB = y) && ARM && ARCH_SA1100
379 select FB_CFB_FILLRECT
380 select FB_CFB_COPYAREA
381 select FB_CFB_IMAGEBLIT
383 This is a framebuffer device for the SA-1100 LCD Controller.
384 See <http://www.linux-fbdev.org/> for information on framebuffer
387 If you plan to use the LCD display with your SA-1100 system, say
391 tristate "Motorola i.MX LCD support"
392 depends on FB && ARM && ARCH_IMX
393 select FB_CFB_FILLRECT
394 select FB_CFB_COPYAREA
395 select FB_CFB_IMAGEBLIT
398 tristate "CyberPro 2000/2010/5000 support"
399 depends on FB && PCI && (BROKEN || !SPARC64)
400 select FB_CFB_FILLRECT
401 select FB_CFB_COPYAREA
402 select FB_CFB_IMAGEBLIT
404 This enables support for the Integraphics CyberPro 20x0 and 5000
405 VGA chips used in the Rebel.com Netwinder and other machines.
406 Say Y if you have a NetWinder or a graphics card containing this
407 device, otherwise say N.
411 depends on (FB = y) && APOLLO
413 select FB_CFB_FILLRECT
414 select FB_CFB_IMAGEBLIT
418 depends on (FB = y) && Q40
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
425 tristate "Amiga native chipset support"
426 depends on FB && AMIGA
428 This is the frame buffer device driver for the builtin graphics
429 chipset found in Amigas.
431 To compile this driver as a module, choose M here: the
432 module will be called amifb.
435 bool "Amiga OCS chipset support"
438 This enables support for the original Agnus and Denise video chips,
439 found in the Amiga 1000 and most A500's and A2000's. If you intend
440 to run Linux on any of these systems, say Y; otherwise say N.
443 bool "Amiga ECS chipset support"
446 This enables support for the Enhanced Chip Set, found in later
447 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
448 you intend to run Linux on any of these systems, say Y; otherwise
452 bool "Amiga AGA chipset support"
455 This enables support for the Advanced Graphics Architecture (also
456 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
457 and CD32. If you intend to run Linux on any of these systems, say Y;
461 bool "Amiga FrameMaster II/Rainbow II support"
462 depends on (FB = y) && ZORRO
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
467 This is the frame buffer device driver for the Amiga FrameMaster
468 card from BSC (exhibited 1992 but not shipped as a CBM product).
471 tristate "Arc Monochrome LCD board support"
473 select FB_SYS_FILLRECT
474 select FB_SYS_COPYAREA
475 select FB_SYS_IMAGEBLIT
478 This enables support for the Arc Monochrome LCD board. The board
479 is based on the KS-108 lcd controller and is typically a matrix
480 of 2*n chips. This driver was tested with a 128x64 panel. This
481 driver supports it for use with x86 SBCs through a 16 bit GPIO
482 interface (8 bit data, 8 bit control). If you anticipate using
483 this driver, say Y or M; otherwise say N. You must specify the
484 GPIO IO address to be used for setting control and data.
487 bool "Atari native chipset support"
488 depends on (FB = y) && ATARI
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the builtin graphics
494 chipset found in Ataris.
497 bool "Open Firmware frame buffer device support"
498 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 Say Y if you want support with Open Firmware for your graphics
508 bool "Apple \"control\" display support"
509 depends on (FB = y) && PPC_PMAC && PPC32
510 select FB_CFB_FILLRECT
511 select FB_CFB_COPYAREA
512 select FB_CFB_IMAGEBLIT
515 This driver supports a frame buffer for the graphics adapter in the
516 Power Macintosh 7300 and others.
519 bool "Apple \"platinum\" display support"
520 depends on (FB = y) && PPC_PMAC && PPC32
521 select FB_CFB_FILLRECT
522 select FB_CFB_COPYAREA
523 select FB_CFB_IMAGEBLIT
526 This driver supports a frame buffer for the "platinum" graphics
527 adapter in some Power Macintoshes.
530 bool "Apple \"valkyrie\" display support"
531 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
537 This driver supports a frame buffer for the "valkyrie" graphics
538 adapter in some Power Macintoshes.
541 bool "Chips 65550 display support"
542 depends on (FB = y) && PPC32 && PCI
543 select FB_CFB_FILLRECT
544 select FB_CFB_COPYAREA
545 select FB_CFB_IMAGEBLIT
547 This is the frame buffer device driver for the Chips & Technologies
548 65550 graphics chip in PowerBooks.
551 bool "Asiliant (Chips) 69000 display support"
552 depends on (FB = y) && 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 Asiliant 69030 chipset
560 bool "IMS Twin Turbo display support"
561 depends on (FB = y) && PCI
562 select FB_CFB_IMAGEBLIT
563 select FB_MACMODES if PPC
565 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
566 many Macintosh and compatible computers.
569 tristate "VGA 16-color graphics support"
570 depends on FB && (X86 || PPC)
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 select FONT_8x16 if FRAMEBUFFER_CONSOLE
577 This is the frame buffer device driver for VGA 16 color graphic
578 cards. Say Y if you have such a card.
580 To compile this driver as a module, choose M here: the
581 module will be called vga16fb.
583 config FB_BF54X_LQ043
584 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
585 depends on FB && (BF54x) && !BF542
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
590 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
592 config FB_BFIN_T350MCQB
593 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
594 depends on FB && BLACKFIN
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
601 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
602 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
606 tristate "HP STI frame buffer device support"
607 depends on FB && PARISC
608 select FB_CFB_FILLRECT
609 select FB_CFB_COPYAREA
610 select FB_CFB_IMAGEBLIT
613 STI refers to the HP "Standard Text Interface" which is a set of
614 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
615 Enabling this option will implement the linux framebuffer device
616 using calls to the STI BIOS routines for initialisation.
618 If you enable this option, you will get a planar framebuffer device
619 /dev/fb which will work on the most common HP graphic cards of the
620 NGLE family, including the artist chips (in the 7xx and Bxxx series),
621 HCRX, HCRX24, CRX, CRX24 and VisEG series.
623 It is safe to enable this option, so you should probably say "Y".
626 bool "Generic Macintosh display support"
627 depends on (FB = y) && MAC
628 select FB_CFB_FILLRECT
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
635 depends on (FB = y) && DIO
636 select FB_CFB_IMAGEBLIT
640 tristate "TGA/SFB+ framebuffer support"
641 depends on FB && (ALPHA || TC)
642 select FB_CFB_FILLRECT
643 select FB_CFB_COPYAREA
644 select FB_CFB_IMAGEBLIT
647 This is the frame buffer device driver for generic TGA and SFB+
648 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
649 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
650 TURBOchannel cards, also known as PMAGD-A, -B and -C.
652 Due to hardware limitations ZLX-E2 and E3 cards are not supported
653 for DECstation 5000/200 systems. Additionally due to firmware
654 limitations these cards may cause troubles with booting DECstation
655 5000/240 and /260 systems, but are fully supported under Linux if
656 you manage to get it going. ;-)
658 Say Y if you have one of those.
661 tristate "Userspace VESA VGA graphics support"
662 depends on FB && CONNECTOR
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
666 select FB_MODE_HELPERS
668 This is the frame buffer driver for generic VBE 2.0 compliant
669 graphic cards. It can also take advantage of VBE 3.0 features,
670 such as refresh rate adjustment.
672 This driver generally provides more features than vesafb but
673 requires a userspace helper application called 'v86d'. See
674 <file:Documentation/fb/uvesafb.txt> for more information.
679 bool "VESA VGA graphics support"
680 depends on (FB = y) && X86
681 select FB_CFB_FILLRECT
682 select FB_CFB_COPYAREA
683 select FB_CFB_IMAGEBLIT
685 This is the frame buffer device driver for generic VESA 2.0
686 compliant graphic cards. The older VESA 1.2 cards are not supported.
687 You will get a boot time penguin logo at no additional cost. Please
688 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
691 bool "EFI-based Framebuffer Support"
692 depends on (FB = y) && X86
693 select FB_CFB_FILLRECT
694 select FB_CFB_COPYAREA
695 select FB_CFB_IMAGEBLIT
697 This is the EFI frame buffer device driver. If the firmware on
698 your platform is UEFI2.0, select Y to add support for
699 Graphics Output Protocol for early console messages to appear.
702 bool "Intel-based Macintosh Framebuffer Support"
703 depends on (FB = y) && X86 && EFI
704 select FB_CFB_FILLRECT
705 select FB_CFB_COPYAREA
706 select FB_CFB_IMAGEBLIT
708 This is the frame buffer device driver for the Intel-based Macintosh
711 tristate "N411 Apollo/Hecuba devkit support"
712 depends on FB && X86 && MMU
713 select FB_SYS_FILLRECT
714 select FB_SYS_COPYAREA
715 select FB_SYS_IMAGEBLIT
717 select FB_DEFERRED_IO
720 This enables support for the Apollo display controller in its
721 Hecuba form using the n411 devkit.
724 tristate "Hercules mono graphics support"
726 select FB_CFB_FILLRECT
727 select FB_CFB_COPYAREA
728 select FB_CFB_IMAGEBLIT
730 Say Y here if you have a Hercules mono graphics card.
732 To compile this driver as a module, choose M here: the
733 module will be called hgafb.
735 As this card technology is 15 years old, most people will answer N
739 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
740 depends on FB_HGA && EXPERIMENTAL
742 This will compile the Hercules mono graphics with
743 acceleration functions.
746 tristate "SGI Visual Workstation framebuffer support"
747 depends on FB && X86_VISWS
748 select FB_CFB_FILLRECT
749 select FB_CFB_COPYAREA
750 select FB_CFB_IMAGEBLIT
752 SGI Visual Workstation support for framebuffer graphics.
755 bool "SGI Graphics Backend frame buffer support"
756 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
757 select FB_CFB_FILLRECT
758 select FB_CFB_COPYAREA
759 select FB_CFB_IMAGEBLIT
761 This is the frame buffer device driver for SGI Graphics Backend.
762 This chip is used in SGI O2 and Visual Workstation 320/540.
765 int "Video memory size in MB"
769 This is the amount of memory reserved for the framebuffer,
770 which can be any value between 1MB and 8MB.
773 bool "SBUS and UPA framebuffers"
774 depends on (FB = y) && SPARC
776 Say Y if you want support for SBUS or UPA based frame buffer device.
780 depends on (FB = y) && (SPARC && FB_SBUS)
781 select FB_CFB_FILLRECT
782 select FB_CFB_COPYAREA
783 select FB_CFB_IMAGEBLIT
785 This is the frame buffer device driver for the BWtwo frame buffer.
788 bool "CGthree support"
789 depends on (FB = y) && (SPARC && FB_SBUS)
790 select FB_CFB_FILLRECT
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
794 This is the frame buffer device driver for the CGthree frame buffer.
797 bool "CGsix (GX,TurboGX) support"
798 depends on (FB = y) && (SPARC && FB_SBUS)
799 select FB_CFB_COPYAREA
800 select FB_CFB_IMAGEBLIT
802 This is the frame buffer device driver for the CGsix (GX, TurboGX)
806 bool "Creator/Creator3D/Elite3D support"
807 depends on FB_SBUS && SPARC64
808 select FB_CFB_COPYAREA
809 select FB_CFB_IMAGEBLIT
811 This is the frame buffer device driver for the Creator, Creator3D,
812 and Elite3D graphics boards.
815 bool "TCX (SS4/SS5 only) support"
817 select FB_CFB_FILLRECT
818 select FB_CFB_COPYAREA
819 select FB_CFB_IMAGEBLIT
821 This is the frame buffer device driver for the TCX 24/8bit frame
825 bool "CGfourteen (SX) support"
827 select FB_CFB_FILLRECT
828 select FB_CFB_COPYAREA
829 select FB_CFB_IMAGEBLIT
831 This is the frame buffer device driver for the CGfourteen frame
832 buffer on Desktop SPARCsystems with the SX graphics option.
835 bool "P9100 (Sparcbook 3 only) support"
837 select FB_CFB_FILLRECT
838 select FB_CFB_COPYAREA
839 select FB_CFB_IMAGEBLIT
841 This is the frame buffer device driver for the P9100 card
842 supported on Sparcbook 3 machines.
845 bool "Leo (ZX) support"
847 select FB_CFB_FILLRECT
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 This is the frame buffer device driver for the SBUS-based Sun ZX
852 (leo) frame buffer cards.
855 bool "IGA 168x display support"
856 depends on (FB = y) && SPARC32
857 select FB_CFB_FILLRECT
858 select FB_CFB_COPYAREA
859 select FB_CFB_IMAGEBLIT
861 This is the framebuffer device for the INTERGRAPHICS 1680 and
862 successor frame buffer cards.
865 bool "Sun XVR-500 3DLABS Wildcat support"
866 depends on (FB = y) && PCI && SPARC64
867 select FB_CFB_FILLRECT
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
871 This is the framebuffer device for the Sun XVR-500 and similar
872 graphics cards based upon the 3DLABS Wildcat chipset. The driver
873 only works on sparc64 systems where the system firmware has
874 mostly initialized the card already. It is treated as a
875 completely dumb framebuffer device.
878 bool "Sun XVR-2500 3DLABS Wildcat support"
879 depends on (FB = y) && PCI && SPARC64
880 select FB_CFB_FILLRECT
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
884 This is the framebuffer device for the Sun XVR-2500 and similar
885 graphics cards based upon the 3DLABS Wildcat chipset. The driver
886 only works on sparc64 systems where the system firmware has
887 mostly initialized the card already. It is treated as a
888 completely dumb framebuffer device.
891 tristate "NEC PowerVR 2 display support"
892 depends on FB && SH_DREAMCAST
893 select FB_CFB_FILLRECT
894 select FB_CFB_COPYAREA
895 select FB_CFB_IMAGEBLIT
897 Say Y here if you have a PowerVR 2 card in your box. If you plan to
898 run linux on your Dreamcast, you will have to say Y here.
899 This driver may or may not work on other PowerVR 2 cards, but is
900 totally untested. Use at your own risk. If unsure, say N.
902 To compile this driver as a module, choose M here: the
903 module will be called pvr2fb.
905 You can pass several parameters to the driver at boot time or at
906 module load time. The parameters look like "video=pvr2:XXX", where
907 the meaning of XXX can be found at the end of the main source file
908 (<file:drivers/video/pvr2fb.c>). Please see the file
909 <file:Documentation/fb/pvr2fb.txt>.
912 bool "Epson 1355 framebuffer support"
913 depends on (FB = y) && ARCH_CEIVA
914 select FB_CFB_FILLRECT
915 select FB_CFB_COPYAREA
916 select FB_CFB_IMAGEBLIT
918 Build in support for the SED1355 Epson Research Embedded RAMDAC
919 LCD/CRT Controller (since redesignated as the S1D13505) as a
920 framebuffer. Product specs at
921 <http://www.erd.epson.com/vdc/html/products.htm>.
924 tristate "Epson S1D13XXX framebuffer support"
926 select FB_CFB_FILLRECT
927 select FB_CFB_COPYAREA
928 select FB_CFB_IMAGEBLIT
930 Support for S1D13XXX framebuffer device family (currently only
931 working with S1D13806). Product specs at
932 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
935 tristate "AT91/AT32 LCD Controller support"
936 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
937 select FB_CFB_FILLRECT
938 select FB_CFB_COPYAREA
939 select FB_CFB_IMAGEBLIT
941 This enables support for the AT91/AT32 LCD Controller.
944 bool "Frame Buffer in internal SRAM"
945 depends on FB_ATMEL && ARCH_AT91SAM9261
947 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
948 to let frame buffer in external SDRAM.
951 bool "Use a STN display with AT91/AT32 LCD Controller"
952 depends on FB_ATMEL && MACH_AT91SAM9261EK
955 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
956 Controller. Say N if you want to connect a TFT.
961 tristate "nVidia Framebuffer Support"
963 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
964 select FB_MODE_HELPERS
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
971 This driver supports graphics boards with the nVidia chips, TNT
972 and newer. For very old chipsets, such as the RIVA128, then use
974 Say Y if you have such a graphics board.
976 To compile this driver as a module, choose M here: the
977 module will be called nvidiafb.
980 bool "Enable DDC Support"
984 This enables I2C support for nVidia Chipsets. This is used
985 only for getting EDID information from the attached display
986 allowing for robust video mode handling and switching.
988 Because fbdev-2.6 requires that drivers must be able to
989 independently validate video mode parameters, you should say Y
992 config FB_NVIDIA_DEBUG
993 bool "Lots of debug output"
997 Say Y here if you want the nVidia driver to output all sorts
998 of debugging information to provide to the maintainer when
999 something goes wrong.
1001 config FB_NVIDIA_BACKLIGHT
1002 bool "Support for backlight control"
1003 depends on FB_NVIDIA
1006 Say Y here if you want to control the backlight of your display.
1009 tristate "nVidia Riva support"
1010 depends on FB && PCI
1011 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1012 select FB_MODE_HELPERS
1013 select FB_CFB_FILLRECT
1014 select FB_CFB_COPYAREA
1015 select FB_CFB_IMAGEBLIT
1019 This driver supports graphics boards with the nVidia Riva/Geforce
1021 Say Y if you have such a graphics board.
1023 To compile this driver as a module, choose M here: the
1024 module will be called rivafb.
1027 bool "Enable DDC Support"
1031 This enables I2C support for nVidia Chipsets. This is used
1032 only for getting EDID information from the attached display
1033 allowing for robust video mode handling and switching.
1035 Because fbdev-2.6 requires that drivers must be able to
1036 independently validate video mode parameters, you should say Y
1039 config FB_RIVA_DEBUG
1040 bool "Lots of debug output"
1044 Say Y here if you want the Riva driver to output all sorts
1045 of debugging information to provide to the maintainer when
1046 something goes wrong.
1048 config FB_RIVA_BACKLIGHT
1049 bool "Support for backlight control"
1053 Say Y here if you want to control the backlight of your display.
1056 tristate "Intel 810/815 support (EXPERIMENTAL)"
1057 depends on FB && EXPERIMENTAL && PCI && X86_32
1060 select FB_MODE_HELPERS
1061 select FB_CFB_FILLRECT
1062 select FB_CFB_COPYAREA
1063 select FB_CFB_IMAGEBLIT
1066 This driver supports the on-board graphics built in to the Intel 810
1067 and 815 chipsets. Say Y if you have and plan to use such a board.
1069 To compile this driver as a module, choose M here: the
1070 module will be called i810fb.
1072 For more information, please read
1073 <file:Documentation/fb/intel810.txt>
1076 bool "use VESA Generalized Timing Formula"
1079 If you say Y, then the VESA standard, Generalized Timing Formula
1080 or GTF, will be used to calculate the required video timing values
1081 per video mode. Since the GTF allows nondiscrete timings
1082 (nondiscrete being a range of values as opposed to discrete being a
1083 set of values), you'll be able to use any combination of horizontal
1084 and vertical resolutions, and vertical refresh rates without having
1085 to specify your own timing parameters. This is especially useful
1086 to maximize the performance of an aging display, or if you just
1087 have a display with nonstandard dimensions. A VESA compliant
1088 monitor is recommended, but can still work with non-compliant ones.
1089 If you need or want this, then select this option. The timings may
1090 not be compliant with Intel's recommended values. Use at your own
1093 If you say N, the driver will revert to discrete video timings
1094 using a set recommended by Intel in their documentation.
1099 bool "Enable DDC Support"
1100 depends on FB_I810 && FB_I810_GTF
1105 tristate "Intel LE80578 (Vermilion) support"
1106 depends on FB && PCI && X86
1107 select FB_MODE_HELPERS
1108 select FB_CFB_FILLRECT
1109 select FB_CFB_COPYAREA
1110 select FB_CFB_IMAGEBLIT
1112 This driver supports the LE80578 (Vermilion Range) chipset
1114 config FB_CARILLO_RANCH
1115 tristate "Intel Carillo Ranch support"
1116 depends on FB_LE80578 && FB && PCI && X86
1118 This driver supports the LE80578 (Carillo Ranch) board
1121 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1122 depends on FB && EXPERIMENTAL && PCI && X86
1125 select FB_MODE_HELPERS
1126 select FB_CFB_FILLRECT
1127 select FB_CFB_COPYAREA
1128 select FB_CFB_IMAGEBLIT
1130 This driver supports the on-board graphics built in to the Intel
1131 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1132 Say Y if you have and plan to use such a board.
1134 If you say Y here and want DDC/I2C support you must first say Y to
1135 "I2C support" and "I2C bit-banging support" in the character devices
1138 If you say M here then "I2C support" and "I2C bit-banging support"
1139 can be build either as modules or built-in.
1141 To compile this driver as a module, choose M here: the
1142 module will be called intelfb.
1144 For more information, please read <file:Documentation/fb/intelfb.txt>
1146 config FB_INTEL_DEBUG
1147 bool "Intel driver Debug Messages"
1150 Say Y here if you want the Intel driver to output all sorts
1151 of debugging information to provide to the maintainer when
1152 something goes wrong.
1155 bool "DDC/I2C for Intel framebuffer support"
1160 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1163 tristate "Matrox acceleration"
1164 depends on FB && PCI
1165 select FB_CFB_FILLRECT
1166 select FB_CFB_COPYAREA
1167 select FB_CFB_IMAGEBLIT
1168 select FB_TILEBLITTING
1169 select FB_MACMODES if PPC_PMAC
1171 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1172 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1173 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1174 Matrox G400, G450 or G550 card in your box.
1176 To compile this driver as a module, choose M here: the
1177 module will be called matroxfb.
1179 You can pass several parameters to the driver at boot time or at
1180 module load time. The parameters look like "video=matrox:XXX", and
1181 are described in <file:Documentation/fb/matroxfb.txt>.
1183 config FB_MATROX_MILLENIUM
1184 bool "Millennium I/II support"
1185 depends on FB_MATROX
1187 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1188 video card. If you select "Advanced lowlevel driver options" below,
1189 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1190 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1191 also use font widths different from 8.
1193 config FB_MATROX_MYSTIQUE
1194 bool "Mystique support"
1195 depends on FB_MATROX
1197 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1198 video card. If you select "Advanced lowlevel driver options" below,
1199 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1200 packed pixel and 32 bpp packed pixel. You can also use font widths
1204 bool "G100/G200/G400/G450/G550 support"
1205 depends on FB_MATROX
1207 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1208 video card. If you select "Advanced lowlevel driver options", you
1209 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1210 pixel and 32 bpp packed pixel. You can also use font widths
1213 If you need support for G400 secondary head, you must first say Y to
1214 "I2C support" in the character devices section, and then to
1215 "Matrox I2C support" and "G400 second head support" here in the
1216 framebuffer section. G450/G550 secondary head and digital output
1217 are supported without additional modules.
1219 The driver starts in monitor mode. You must use the matroxset tool
1220 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1221 swap primary and secondary head outputs, or to change output mode.
1222 Secondary head driver always start in 640x480 resolution and you
1223 must use fbset to change it.
1225 Do not forget that second head supports only 16 and 32 bpp
1226 packed pixels, so it is a good idea to compile them into the kernel
1227 too. You can use only some font widths, as the driver uses generic
1228 painting procedures (the secondary head does not use acceleration
1231 G450/G550 hardware can display TV picture only from secondary CRTC,
1232 and it performs no scaling, so picture must have 525 or 625 lines.
1234 config FB_MATROX_I2C
1235 tristate "Matrox I2C support"
1236 depends on FB_MATROX
1239 This drivers creates I2C buses which are needed for accessing the
1240 DDC (I2C) bus present on all Matroxes, an I2C bus which
1241 interconnects Matrox optional devices, like MGA-TVO on G200 and
1242 G400, and the secondary head DDC bus, present on G400 only.
1244 You can say Y or M here if you want to experiment with monitor
1245 detection code. You must say Y or M here if you want to use either
1246 second head of G400 or MGA-TVO on G200 or G400.
1248 If you compile it as module, it will create a module named
1251 config FB_MATROX_MAVEN
1252 tristate "G400 second head support"
1253 depends on FB_MATROX_G && FB_MATROX_I2C
1255 WARNING !!! This support does not work with G450 !!!
1257 Say Y or M here if you want to use a secondary head (meaning two
1258 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1259 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1260 secondary head output is blanked while you are in X. With XFree
1261 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1262 the fbdev driver on first head and the fbdev driver on second head.
1264 If you compile it as module, two modules are created,
1265 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1266 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1267 also load i2c-matroxfb to get it to run.
1269 The driver starts in monitor mode and you must use the matroxset
1271 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1272 PAL or NTSC or to swap primary and secondary head outputs.
1273 Secondary head driver also always start in 640x480 resolution, you
1274 must use fbset to change it.
1276 Also do not forget that second head supports only 16 and 32 bpp
1277 packed pixels, so it is a good idea to compile them into the kernel
1278 too. You can use only some font widths, as the driver uses generic
1279 painting procedures (the secondary head does not use acceleration
1282 config FB_MATROX_MULTIHEAD
1283 bool "Multihead support"
1284 depends on FB_MATROX
1286 Say Y here if you have more than one (supported) Matrox device in
1287 your computer and you want to use all of them for different monitors
1288 ("multihead"). If you have only one device, you should say N because
1289 the driver compiled with Y is larger and a bit slower, especially on
1292 If you said M to "Matrox unified accelerated driver" and N here, you
1293 will still be able to use several Matrox devices simultaneously:
1294 insert several instances of the module matroxfb into the kernel
1295 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1296 for the different Matrox devices. This method is slightly faster but
1297 uses 40 KB of kernel memory per Matrox card.
1299 There is no need for enabling 'Matrox multihead support' if you have
1300 only one Matrox card in the box.
1303 tristate "ATI Radeon display support"
1304 depends on FB && PCI
1305 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1306 select FB_MODE_HELPERS
1307 select FB_CFB_FILLRECT
1308 select FB_CFB_COPYAREA
1309 select FB_CFB_IMAGEBLIT
1310 select FB_MACMODES if PPC_OF
1312 Choose this option if you want to use an ATI Radeon graphics card as
1313 a framebuffer device. There are both PCI and AGP versions. You
1314 don't need to choose this to run the Radeon in plain VGA mode.
1316 If you say Y here and want DDC/I2C support you must first say Y to
1317 "I2C support" and "I2C bit-banging support" in the character devices
1320 If you say M here then "I2C support" and "I2C bit-banging support"
1321 can be build either as modules or built-in.
1323 There is a product page at
1324 http://apps.ati.com/ATIcompare/
1326 config FB_RADEON_I2C
1327 bool "DDC/I2C for ATI Radeon support"
1328 depends on FB_RADEON
1332 Say Y here if you want DDC/I2C support for your Radeon board.
1334 config FB_RADEON_BACKLIGHT
1335 bool "Support for backlight control"
1336 depends on FB_RADEON
1339 Say Y here if you want to control the backlight of your display.
1341 config FB_RADEON_DEBUG
1342 bool "Lots of debug output from Radeon driver"
1343 depends on FB_RADEON
1346 Say Y here if you want the Radeon driver to output all sorts
1347 of debugging information to provide to the maintainer when
1348 something goes wrong.
1351 tristate "ATI Rage128 display support"
1352 depends on FB && PCI
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1356 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1357 select FB_MACMODES if PPC_PMAC
1359 This driver supports graphics boards with the ATI Rage128 chips.
1360 Say Y if you have such a graphics board and read
1361 <file:Documentation/fb/aty128fb.txt>.
1363 To compile this driver as a module, choose M here: the
1364 module will be called aty128fb.
1366 config FB_ATY128_BACKLIGHT
1367 bool "Support for backlight control"
1368 depends on FB_ATY128
1371 Say Y here if you want to control the backlight of your display.
1374 tristate "ATI Mach64 display support" if PCI || ATARI
1375 depends on FB && !SPARC32
1376 select FB_CFB_FILLRECT
1377 select FB_CFB_COPYAREA
1378 select FB_CFB_IMAGEBLIT
1379 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1380 select FB_MACMODES if PPC
1382 This driver supports graphics boards with the ATI Mach64 chips.
1383 Say Y if you have such a graphics board.
1385 To compile this driver as a module, choose M here: the
1386 module will be called atyfb.
1389 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1390 depends on PCI && FB_ATY
1391 default y if SPARC64 && PCI
1393 Say Y here to support use of ATI's 64-bit Rage boards (or other
1394 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1395 framebuffer device. The ATI product support page for these boards
1396 is at <http://support.ati.com/products/pc/mach64/>.
1398 config FB_ATY_GENERIC_LCD
1399 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1400 depends on FB_ATY_CT
1402 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1403 Rage XC, or Rage XL chipset.
1406 bool "Mach64 GX support" if PCI
1410 Say Y here to support use of the ATI Mach64 Graphics Expression
1411 board (or other boards based on the Mach64 GX chipset) as a
1412 framebuffer device. The ATI product support page for these boards
1414 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1416 config FB_ATY_BACKLIGHT
1417 bool "Support for backlight control"
1421 Say Y here if you want to control the backlight of your display.
1424 tristate "S3 Trio/Virge support"
1425 depends on FB && PCI
1426 select FB_CFB_FILLRECT
1427 select FB_CFB_COPYAREA
1428 select FB_CFB_IMAGEBLIT
1429 select FB_TILEBLITTING
1432 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1434 Driver for graphics boards with S3 Trio / S3 Virge chip.
1437 tristate "S3 Savage support"
1438 depends on FB && PCI && EXPERIMENTAL
1439 select FB_MODE_HELPERS
1440 select FB_CFB_FILLRECT
1441 select FB_CFB_COPYAREA
1442 select FB_CFB_IMAGEBLIT
1445 This driver supports notebooks and computers with S3 Savage PCI/AGP
1448 Say Y if you have such a graphics card.
1450 To compile this driver as a module, choose M here; the module
1451 will be called savagefb.
1453 config FB_SAVAGE_I2C
1454 bool "Enable DDC2 Support"
1455 depends on FB_SAVAGE
1458 This enables I2C support for S3 Savage Chipsets. This is used
1459 only for getting EDID information from the attached display
1460 allowing for robust video mode handling and switching.
1462 Because fbdev-2.6 requires that drivers must be able to
1463 independently validate video mode parameters, you should say Y
1466 config FB_SAVAGE_ACCEL
1467 bool "Enable Console Acceleration"
1468 depends on FB_SAVAGE
1471 This option will compile in console acceleration support. If
1472 the resulting framebuffer console has bothersome glitches, then
1476 tristate "SiS/XGI display support"
1477 depends on FB && PCI
1478 select FB_CFB_FILLRECT
1479 select FB_CFB_COPYAREA
1480 select FB_CFB_IMAGEBLIT
1482 This is the frame buffer device driver for the SiS 300, 315, 330
1483 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1484 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1486 To compile this driver as a module, choose M here; the module
1487 will be called sisfb.
1490 bool "SiS 300 series support"
1493 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1496 bool "SiS 315/330/340 series and XGI support"
1499 Say Y here to support use of the SiS 315, 330 and 340 series
1500 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1501 as XGI V3XT, V5, V8 and Z7.
1504 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1505 depends on FB && PCI
1506 select FB_CFB_FILLRECT
1507 select FB_CFB_COPYAREA
1508 select FB_CFB_IMAGEBLIT
1509 select FB_SOFT_CURSOR
1513 This is the frame buffer device driver for Graphics chips of VIA
1514 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1515 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1517 Say Y if you have a VIA UniChrome graphics board.
1519 To compile this driver as a module, choose M here: the
1520 module will be called viafb.
1522 tristate "NeoMagic display support"
1523 depends on FB && PCI
1524 select FB_MODE_HELPERS
1525 select FB_CFB_FILLRECT
1526 select FB_CFB_COPYAREA
1527 select FB_CFB_IMAGEBLIT
1530 This driver supports notebooks with NeoMagic PCI chips.
1531 Say Y if you have such a graphics card.
1533 To compile this driver as a module, choose M here: the
1534 module will be called neofb.
1537 tristate "IMG Kyro support"
1538 depends on FB && PCI
1539 select FB_CFB_FILLRECT
1540 select FB_CFB_COPYAREA
1541 select FB_CFB_IMAGEBLIT
1543 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1546 To compile this driver as a module, choose M here: the
1547 module will be called kyrofb.
1550 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1551 depends on FB && PCI
1552 select FB_CFB_IMAGEBLIT
1553 select FB_CFB_FILLRECT
1554 select FB_CFB_COPYAREA
1556 This driver supports graphics boards with the 3Dfx Banshee,
1557 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1558 such a graphics board.
1560 To compile this driver as a module, choose M here: the
1561 module will be called tdfxfb.
1563 config FB_3DFX_ACCEL
1564 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1565 depends on FB_3DFX && EXPERIMENTAL
1567 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1568 device driver with acceleration functions.
1571 tristate "3Dfx Voodoo Graphics (sst1) support"
1572 depends on FB && PCI
1573 select FB_CFB_FILLRECT
1574 select FB_CFB_COPYAREA
1575 select FB_CFB_IMAGEBLIT
1577 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1578 Voodoo2 (cvg) based graphics card.
1580 To compile this driver as a module, choose M here: the
1581 module will be called sstfb.
1583 WARNING: Do not use any application that uses the 3D engine
1584 (namely glide) while using this driver.
1585 Please read the <file:Documentation/fb/sstfb.txt> for supported
1586 options and other important info support.
1589 tristate "VIA VT8623 support"
1590 depends on FB && PCI
1591 select FB_CFB_FILLRECT
1592 select FB_CFB_COPYAREA
1593 select FB_CFB_IMAGEBLIT
1594 select FB_TILEBLITTING
1597 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1599 Driver for CastleRock integrated graphics core in the
1600 VIA VT8623 [Apollo CLE266] chipset.
1603 tristate "Cyberblade/i1 support"
1604 depends on FB && PCI && X86_32 && !64BIT
1605 select FB_CFB_IMAGEBLIT
1607 This driver is supposed to support the Trident Cyberblade/i1
1608 graphics core integrated in the VIA VT8601A North Bridge,
1609 also known as VIA Apollo PLE133.
1612 - Developed, tested and working on EPIA 5000 and EPIA 800.
1613 - Does work reliable on all systems with CRT/LCD connected to
1615 - Should work on systems that do use the internal LCD port, but
1616 this is absolutely not tested.
1618 Character imageblit, copyarea and rectangle fill are hw accelerated,
1619 ypan scrolling is used by default.
1621 Please do read <file:Documentation/fb/cyblafb/*>.
1623 To compile this driver as a module, choose M here: the
1624 module will be called cyblafb.
1627 tristate "Trident support"
1628 depends on FB && PCI
1629 select FB_CFB_FILLRECT
1630 select FB_CFB_COPYAREA
1631 select FB_CFB_IMAGEBLIT
1633 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1634 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1636 There are also integrated versions of these chips called CyberXXXX,
1637 CyberImage or CyberBlade. These chips are mostly found in laptops
1638 but also on some motherboards. For more information, read
1639 <file:Documentation/fb/tridentfb.txt>
1641 Say Y if you have such a graphics board.
1643 To compile this driver as a module, choose M here: the
1644 module will be called tridentfb.
1646 config FB_TRIDENT_ACCEL
1647 bool "Trident Acceleration functions (EXPERIMENTAL)"
1648 depends on FB_TRIDENT && EXPERIMENTAL
1650 This will compile the Trident frame buffer device with
1651 acceleration functions.
1654 tristate "ARK 2000PV support"
1655 depends on FB && PCI
1656 select FB_CFB_FILLRECT
1657 select FB_CFB_COPYAREA
1658 select FB_CFB_IMAGEBLIT
1659 select FB_TILEBLITTING
1662 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1664 Driver for PCI graphics boards with ARK 2000PV chip
1665 and ICS 5342 RAMDAC.
1668 tristate "Permedia3 support (EXPERIMENTAL)"
1669 depends on FB && PCI && EXPERIMENTAL
1670 select FB_CFB_FILLRECT
1671 select FB_CFB_COPYAREA
1672 select FB_CFB_IMAGEBLIT
1674 This is the frame buffer device driver for the 3DLabs Permedia3
1675 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1676 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1677 and maybe other boards.
1680 tristate "Fujitsu carmine frame buffer support"
1681 depends on FB && PCI
1682 select FB_CFB_FILLRECT
1683 select FB_CFB_COPYAREA
1684 select FB_CFB_IMAGEBLIT
1686 This is the frame buffer device driver for the Fujitsu Carmine chip.
1687 The driver provides two independent frame buffer devices.
1690 depends on FB_CARMINE
1691 prompt "DRAM timing"
1692 default FB_CARMINE_DRAM_EVAL
1694 config FB_CARMINE_DRAM_EVAL
1695 bool "Eval board timings"
1697 Use timings which work on the eval card.
1699 config CARMINE_DRAM_CUSTOM
1700 bool "Custom board timings"
1702 Use custom board timings.
1706 bool "Au1100 LCD Driver"
1707 depends on (FB = y) && MIPS && SOC_AU1100
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1713 various panels and CRTs by passing in kernel cmd line option
1714 au1100fb:panel=<name>.
1717 bool "Au1200 LCD Driver"
1718 depends on (FB = y) && MIPS && SOC_AU1200
1719 select FB_CFB_FILLRECT
1720 select FB_CFB_COPYAREA
1721 select FB_CFB_IMAGEBLIT
1723 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1724 various panels and CRTs by passing in kernel cmd line option
1725 au1200fb:panel=<name>.
1727 source "drivers/video/geode/Kconfig"
1730 tristate "HD64461 Frame Buffer support"
1731 depends on FB && HD64461
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1736 This is the frame buffer device driver for the Hitachi HD64461 LCD
1740 bool "PMAG-AA TURBOchannel framebuffer support"
1741 depends on (FB = y) && TC
1742 select FB_CFB_FILLRECT
1743 select FB_CFB_COPYAREA
1744 select FB_CFB_IMAGEBLIT
1746 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1747 used mainly in the MIPS-based DECstation series.
1750 tristate "PMAG-BA TURBOchannel framebuffer support"
1752 select FB_CFB_FILLRECT
1753 select FB_CFB_COPYAREA
1754 select FB_CFB_IMAGEBLIT
1756 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1757 used mainly in the MIPS-based DECstation series.
1760 tristate "PMAGB-B TURBOchannel framebuffer support"
1762 select FB_CFB_FILLRECT
1763 select FB_CFB_COPYAREA
1764 select FB_CFB_IMAGEBLIT
1766 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1767 in the MIPS-based DECstation series. The card is currently only
1768 supported in 1280x1024x8 mode.
1771 bool "Maxine (Personal DECstation) onboard framebuffer support"
1772 depends on (FB = y) && MACH_DECSTATION
1773 select FB_CFB_FILLRECT
1774 select FB_CFB_COPYAREA
1775 select FB_CFB_IMAGEBLIT
1777 Support for the onboard framebuffer (1024x768x8) in the Personal
1778 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1782 bool "G364 frame buffer support"
1783 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1784 select FB_CFB_FILLRECT
1785 select FB_CFB_COPYAREA
1786 select FB_CFB_IMAGEBLIT
1788 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1789 Olivetti M700-10 systems.
1792 bool "Motorola 68328 native frame buffer support"
1793 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1794 select FB_CFB_FILLRECT
1795 select FB_CFB_COPYAREA
1796 select FB_CFB_IMAGEBLIT
1798 Say Y here if you want to support the built-in frame buffer of
1799 the Motorola 68328 CPU family.
1802 tristate "PXA LCD framebuffer support"
1803 depends on FB && ARCH_PXA
1804 select FB_CFB_FILLRECT
1805 select FB_CFB_COPYAREA
1806 select FB_CFB_IMAGEBLIT
1808 Frame buffer driver for the built-in LCD controller in the Intel
1811 This driver is also available as a module ( = code which can be
1812 inserted and removed from the running kernel whenever you want). The
1813 module will be called pxafb. If you want to compile it as a module,
1814 say M here and read <file:Documentation/kbuild/modules.txt>.
1818 config FB_PXA_SMARTPANEL
1819 bool "PXA Smartpanel LCD support"
1823 config FB_PXA_PARAMETERS
1824 bool "PXA LCD command line parameters"
1828 Enable the use of kernel command line or module parameters
1829 to configure the physical properties of the LCD panel when
1830 using the PXA LCD driver.
1832 This option allows you to override the panel parameters
1833 supplied by the platform in order to support multiple
1834 different models of flatpanel. If you will only be using a
1835 single model of flatpanel then you can safely leave this
1838 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1841 tristate "2700G LCD framebuffer support"
1842 depends on FB && ARCH_PXA
1843 select FB_CFB_FILLRECT
1844 select FB_CFB_COPYAREA
1845 select FB_CFB_IMAGEBLIT
1847 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1851 bool "Enable debugging info via debugfs"
1852 depends on FB_MBX && DEBUG_FS
1855 Enable this if you want debugging information using the debug
1856 filesystem (debugfs)
1861 tristate "Freescale DIU framebuffer support"
1862 depends on FB && FSL_SOC
1863 select FB_CFB_FILLRECT
1864 select FB_CFB_COPYAREA
1865 select FB_CFB_IMAGEBLIT
1866 select PPC_LIB_RHEAP
1868 Framebuffer driver for the Freescale SoC DIU
1871 tristate "W100 frame buffer support"
1872 depends on FB && ARCH_PXA
1873 select FB_CFB_FILLRECT
1874 select FB_CFB_COPYAREA
1875 select FB_CFB_IMAGEBLIT
1877 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1878 It can also drive the w3220 chip found on iPAQ hx4700.
1880 This driver is also available as a module ( = code which can be
1881 inserted and removed from the running kernel whenever you want). The
1882 module will be called w100fb. If you want to compile it as a module,
1883 say M here and read <file:Documentation/kbuild/modules.txt>.
1887 config FB_SH_MOBILE_LCDC
1888 tristate "SuperH Mobile LCDC framebuffer support"
1889 depends on FB && SUPERH
1890 select FB_CFB_FILLRECT
1891 select FB_CFB_COPYAREA
1892 select FB_CFB_IMAGEBLIT
1895 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1898 tristate "S3C2410 LCD framebuffer support"
1899 depends on FB && ARCH_S3C2410
1900 select FB_CFB_FILLRECT
1901 select FB_CFB_COPYAREA
1902 select FB_CFB_IMAGEBLIT
1904 Frame buffer driver for the built-in LCD controller in the Samsung
1907 This driver is also available as a module ( = code which can be
1908 inserted and removed from the running kernel whenever you want). The
1909 module will be called s3c2410fb. If you want to compile it as a module,
1910 say M here and read <file:Documentation/kbuild/modules.txt>.
1913 config FB_S3C2410_DEBUG
1914 bool "S3C2410 lcd debug messages"
1915 depends on FB_S3C2410
1917 Turn on debugging messages. Note that you can set/unset at run time
1921 tristate "Silicon Motion SM501 framebuffer support"
1922 depends on FB && MFD_SM501
1923 select FB_CFB_FILLRECT
1924 select FB_CFB_COPYAREA
1925 select FB_CFB_IMAGEBLIT
1927 Frame buffer driver for the CRT and LCD controllers in the Silicon
1930 This driver is also available as a module ( = code which can be
1931 inserted and removed from the running kernel whenever you want). The
1932 module will be called sm501fb. If you want to compile it as a module,
1933 say M here and read <file:Documentation/kbuild/modules.txt>.
1938 config FB_PNX4008_DUM
1939 tristate "Display Update Module support on Philips PNX4008 board"
1940 depends on FB && ARCH_PNX4008
1942 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1944 config FB_PNX4008_DUM_RGB
1945 tristate "RGB Framebuffer support on Philips PNX4008 board"
1946 depends on FB_PNX4008_DUM
1947 select FB_CFB_FILLRECT
1948 select FB_CFB_COPYAREA
1949 select FB_CFB_IMAGEBLIT
1951 Say Y here to enable support for PNX4008 RGB Framebuffer
1953 config FB_IBM_GXT4500
1954 tristate "Framebuffer support for IBM GXT4500P adaptor"
1955 depends on FB && PPC
1956 select FB_CFB_FILLRECT
1957 select FB_CFB_COPYAREA
1958 select FB_CFB_IMAGEBLIT
1960 Say Y here to enable support for the IBM GXT4500P display
1961 adaptor, found on some IBM System P (pSeries) machines.
1964 tristate "PS3 GPU framebuffer driver"
1965 depends on FB && PS3_PS3AV
1966 select FB_SYS_FILLRECT
1967 select FB_SYS_COPYAREA
1968 select FB_SYS_IMAGEBLIT
1970 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1972 Include support for the virtual frame buffer in the PS3 platform.
1974 config FB_PS3_DEFAULT_SIZE_M
1975 int "PS3 default frame buffer size (in MiB)"
1979 This is the default size (in MiB) of the virtual frame buffer in
1981 The default value can be overridden on the kernel command line
1982 using the "ps3fb" option (e.g. "ps3fb=9M");
1985 tristate "Xilinx frame buffer support"
1986 depends on FB && XILINX_VIRTEX
1987 select FB_CFB_FILLRECT
1988 select FB_CFB_COPYAREA
1989 select FB_CFB_IMAGEBLIT
1991 Include support for the Xilinx ML300/ML403 reference design
1992 framebuffer. ML300 carries a 640*480 LCD display on the board,
1993 ML403 uses a standard DB15 VGA connector.
1996 tristate "Cobalt server LCD frame buffer support"
1997 depends on FB && MIPS_COBALT
2000 bool "SH7760/SH7763 LCDC support"
2001 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763)
2002 select FB_CFB_FILLRECT
2003 select FB_CFB_COPYAREA
2004 select FB_CFB_IMAGEBLIT
2006 Support for the SH7760/SH7763 integrated (D)STN/TFT LCD Controller.
2007 Supports display resolutions up to 1024x1024 pixel, grayscale and
2008 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2009 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2010 panels <= 320 pixel horizontal resolution.
2013 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2015 select FB_SYS_FILLRECT
2016 select FB_SYS_COPYAREA
2017 select FB_SYS_IMAGEBLIT
2020 This is a `virtual' frame buffer device. It operates on a chunk of
2021 unswappable kernel memory instead of on the memory of a graphics
2022 board. This means you cannot see any output sent to this frame
2023 buffer device, while it does consume precious memory. The main use
2024 of this frame buffer device is testing and debugging the frame
2025 buffer subsystem. Do NOT enable it for normal systems! To protect
2026 the innocent, it has to be enabled explicitly at boot time using the
2027 kernel option `video=vfb:'.
2029 To compile this driver as a module, choose M here: the
2030 module will be called vfb. In order to load it, you must use
2031 the vfb_enable=1 option.
2035 config XEN_FBDEV_FRONTEND
2036 tristate "Xen virtual frame buffer support"
2037 depends on FB && XEN
2038 select FB_SYS_FILLRECT
2039 select FB_SYS_COPYAREA
2040 select FB_SYS_IMAGEBLIT
2042 select FB_DEFERRED_IO
2045 This driver implements the front-end of the Xen virtual
2046 frame buffer driver. It communicates with a back-end
2050 tristate "E-Ink Metronome/8track controller support"
2052 select FB_SYS_FILLRECT
2053 select FB_SYS_COPYAREA
2054 select FB_SYS_IMAGEBLIT
2056 select FB_DEFERRED_IO
2058 This driver implements support for the E-Ink Metronome
2059 controller. The pre-release name for this device was 8track
2060 and could also have been called by some vendors as PVI-nnnn.
2062 source "drivers/video/omap/Kconfig"
2064 source "drivers/video/backlight/Kconfig"
2065 source "drivers/video/display/Kconfig"
2068 source "drivers/video/console/Kconfig"
2071 if FB || SGI_NEWPORT_CONSOLE
2072 source "drivers/video/logo/Kconfig"