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 the Permedia2 AGP frame
258 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
260 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
262 config FB_PM2_FIFO_DISCONNECT
263 bool "enable FIFO disconnect feature"
264 depends on FB_PM2 && PCI
266 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
269 tristate "ARM PrimeCell PL110 support"
270 depends on FB && ARM && ARM_AMBA
271 select FB_CFB_FILLRECT
272 select FB_CFB_COPYAREA
273 select FB_CFB_IMAGEBLIT
275 This framebuffer device driver is for the ARM PrimeCell PL110
276 Colour LCD controller. ARM PrimeCells provide the building
277 blocks for System on a Chip devices.
279 If you want to compile this as a module (=code which can be
280 inserted into and removed from the running kernel), say M
281 here and read <file:Documentation/kbuild/modules.txt>. The module
282 will be called amba-clcd.
286 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
288 default FB_ARMCLCD_SHARP_LQ035Q7DB02
290 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
291 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
293 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
294 color QVGA, HRTFT panel. The LogicPD device includes
295 an integrated HRTFT controller IC.
296 The native resolution is 240x320.
298 config FB_ARMCLCD_SHARP_LQ057Q3DC02
299 bool "LogicPD LCD 5.7\" QVGA"
301 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
302 color QVGA, TFT panel. The LogicPD device includes an
303 The native resolution is 320x240.
305 config FB_ARMCLCD_SHARP_LQ64D343
306 bool "LogicPD LCD 6.4\" VGA"
308 This is an implementation of the Sharp LQ64D343, a 6.4"
309 color VGA, TFT panel. The LogicPD device includes an
310 The native resolution is 640x480.
312 config FB_ARMCLCD_SHARP_LQ10D368
313 bool "LogicPD LCD 10.4\" VGA"
315 This is an implementation of the Sharp LQ10D368, a 10.4"
316 color VGA, TFT panel. The LogicPD device includes an
317 The native resolution is 640x480.
320 config FB_ARMCLCD_SHARP_LQ121S1DG41
321 bool "LogicPD LCD 12.1\" SVGA"
323 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
324 color SVGA, TFT panel. The LogicPD device includes an
325 The native resolution is 800x600.
327 This panel requires a clock rate may be an integer fraction
328 of the base LCDCLK frequency. The driver will select the
329 highest frequency available that is lower than the maximum
330 allowed. The panel may flicker if the clock rate is
331 slower than the recommended minimum.
333 config FB_ARMCLCD_AUO_A070VW01_WIDE
334 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
336 This is an implementation of the AU Optronics, a 7.0"
337 WIDE Color. The native resolution is 234x480.
339 config FB_ARMCLCD_HITACHI
340 bool "Hitachi Wide Screen 800x480"
342 This is an implementation of the Hitachi 800x480.
348 bool "Acorn VIDC support"
349 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
350 select FB_CFB_FILLRECT
351 select FB_CFB_COPYAREA
352 select FB_CFB_IMAGEBLIT
354 This is the frame buffer device driver for the Acorn VIDC graphics
355 hardware found in Acorn RISC PCs and other ARM-based machines. If
359 bool "CLPS711X LCD support"
360 depends on (FB = y) && ARM && ARCH_CLPS711X
361 select FB_CFB_FILLRECT
362 select FB_CFB_COPYAREA
363 select FB_CFB_IMAGEBLIT
365 Say Y to enable the Framebuffer driver for the CLPS7111 and
369 bool "SA-1100 LCD support"
370 depends on (FB = y) && ARM && ARCH_SA1100
371 select FB_CFB_FILLRECT
372 select FB_CFB_COPYAREA
373 select FB_CFB_IMAGEBLIT
375 This is a framebuffer device for the SA-1100 LCD Controller.
376 See <http://www.linux-fbdev.org/> for information on framebuffer
379 If you plan to use the LCD display with your SA-1100 system, say
383 tristate "Motorola i.MX LCD support"
384 depends on FB && ARM && ARCH_IMX
385 select FB_CFB_FILLRECT
386 select FB_CFB_COPYAREA
387 select FB_CFB_IMAGEBLIT
390 tristate "CyberPro 2000/2010/5000 support"
391 depends on FB && PCI && (BROKEN || !SPARC64)
392 select FB_CFB_FILLRECT
393 select FB_CFB_COPYAREA
394 select FB_CFB_IMAGEBLIT
396 This enables support for the Integraphics CyberPro 20x0 and 5000
397 VGA chips used in the Rebel.com Netwinder and other machines.
398 Say Y if you have a NetWinder or a graphics card containing this
399 device, otherwise say N.
403 depends on (FB = y) && APOLLO
405 select FB_CFB_FILLRECT
406 select FB_CFB_IMAGEBLIT
410 depends on (FB = y) && Q40
412 select FB_CFB_FILLRECT
413 select FB_CFB_COPYAREA
414 select FB_CFB_IMAGEBLIT
417 tristate "Amiga native chipset support"
418 depends on FB && AMIGA
420 This is the frame buffer device driver for the builtin graphics
421 chipset found in Amigas.
423 To compile this driver as a module, choose M here: the
424 module will be called amifb.
427 bool "Amiga OCS chipset support"
430 This enables support for the original Agnus and Denise video chips,
431 found in the Amiga 1000 and most A500's and A2000's. If you intend
432 to run Linux on any of these systems, say Y; otherwise say N.
435 bool "Amiga ECS chipset support"
438 This enables support for the Enhanced Chip Set, found in later
439 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
440 you intend to run Linux on any of these systems, say Y; otherwise
444 bool "Amiga AGA chipset support"
447 This enables support for the Advanced Graphics Architecture (also
448 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
449 and CD32. If you intend to run Linux on any of these systems, say Y;
453 bool "Amiga FrameMaster II/Rainbow II support"
454 depends on (FB = y) && ZORRO
455 select FB_CFB_FILLRECT
456 select FB_CFB_COPYAREA
457 select FB_CFB_IMAGEBLIT
459 This is the frame buffer device driver for the Amiga FrameMaster
460 card from BSC (exhibited 1992 but not shipped as a CBM product).
463 tristate "Arc Monochrome LCD board support"
465 select FB_SYS_FILLRECT
466 select FB_SYS_COPYAREA
467 select FB_SYS_IMAGEBLIT
470 This enables support for the Arc Monochrome LCD board. The board
471 is based on the KS-108 lcd controller and is typically a matrix
472 of 2*n chips. This driver was tested with a 128x64 panel. This
473 driver supports it for use with x86 SBCs through a 16 bit GPIO
474 interface (8 bit data, 8 bit control). If you anticipate using
475 this driver, say Y or M; otherwise say N. You must specify the
476 GPIO IO address to be used for setting control and data.
479 bool "Atari native chipset support"
480 depends on (FB = y) && ATARI
481 select FB_CFB_FILLRECT
482 select FB_CFB_COPYAREA
483 select FB_CFB_IMAGEBLIT
485 This is the frame buffer device driver for the builtin graphics
486 chipset found in Ataris.
489 bool "Open Firmware frame buffer device support"
490 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
491 select FB_CFB_FILLRECT
492 select FB_CFB_COPYAREA
493 select FB_CFB_IMAGEBLIT
496 Say Y if you want support with Open Firmware for your graphics
500 bool "Apple \"control\" display support"
501 depends on (FB = y) && PPC_PMAC && PPC32
502 select FB_CFB_FILLRECT
503 select FB_CFB_COPYAREA
504 select FB_CFB_IMAGEBLIT
507 This driver supports a frame buffer for the graphics adapter in the
508 Power Macintosh 7300 and others.
511 bool "Apple \"platinum\" display support"
512 depends on (FB = y) && PPC_PMAC && PPC32
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
518 This driver supports a frame buffer for the "platinum" graphics
519 adapter in some Power Macintoshes.
522 bool "Apple \"valkyrie\" display support"
523 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
524 select FB_CFB_FILLRECT
525 select FB_CFB_COPYAREA
526 select FB_CFB_IMAGEBLIT
529 This driver supports a frame buffer for the "valkyrie" graphics
530 adapter in some Power Macintoshes.
533 bool "Chips 65550 display support"
534 depends on (FB = y) && PPC32 && PCI
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
539 This is the frame buffer device driver for the Chips & Technologies
540 65550 graphics chip in PowerBooks.
543 bool "Asiliant (Chips) 69000 display support"
544 depends on (FB = y) && PCI
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
549 This is the frame buffer device driver for the Asiliant 69030 chipset
552 bool "IMS Twin Turbo display support"
553 depends on (FB = y) && PCI
554 select FB_CFB_IMAGEBLIT
555 select FB_MACMODES if PPC
557 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
558 many Macintosh and compatible computers.
561 tristate "VGA 16-color graphics support"
562 depends on FB && (X86 || PPC)
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
567 select FONT_8x16 if FRAMEBUFFER_CONSOLE
569 This is the frame buffer device driver for VGA 16 color graphic
570 cards. Say Y if you have such a card.
572 To compile this driver as a module, choose M here: the
573 module will be called vga16fb.
575 config FB_BF54X_LQ043
576 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
577 depends on FB && (BF54x) && !BF542
578 select FB_CFB_FILLRECT
579 select FB_CFB_COPYAREA
580 select FB_CFB_IMAGEBLIT
582 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
584 config FB_BFIN_T350MCQB
585 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
586 depends on FB && BLACKFIN
588 select FB_CFB_FILLRECT
589 select FB_CFB_COPYAREA
590 select FB_CFB_IMAGEBLIT
592 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
593 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
594 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
598 tristate "HP STI frame buffer device support"
599 depends on FB && PARISC
600 select FB_CFB_FILLRECT
601 select FB_CFB_COPYAREA
602 select FB_CFB_IMAGEBLIT
605 STI refers to the HP "Standard Text Interface" which is a set of
606 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
607 Enabling this option will implement the linux framebuffer device
608 using calls to the STI BIOS routines for initialisation.
610 If you enable this option, you will get a planar framebuffer device
611 /dev/fb which will work on the most common HP graphic cards of the
612 NGLE family, including the artist chips (in the 7xx and Bxxx series),
613 HCRX, HCRX24, CRX, CRX24 and VisEG series.
615 It is safe to enable this option, so you should probably say "Y".
618 bool "Generic Macintosh display support"
619 depends on (FB = y) && MAC
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
627 depends on (FB = y) && DIO
628 select FB_CFB_IMAGEBLIT
632 tristate "TGA/SFB+ framebuffer support"
633 depends on FB && (ALPHA || TC)
634 select FB_CFB_FILLRECT
635 select FB_CFB_COPYAREA
636 select FB_CFB_IMAGEBLIT
639 This is the frame buffer device driver for generic TGA and SFB+
640 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
641 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
642 TURBOchannel cards, also known as PMAGD-A, -B and -C.
644 Due to hardware limitations ZLX-E2 and E3 cards are not supported
645 for DECstation 5000/200 systems. Additionally due to firmware
646 limitations these cards may cause troubles with booting DECstation
647 5000/240 and /260 systems, but are fully supported under Linux if
648 you manage to get it going. ;-)
650 Say Y if you have one of those.
653 tristate "Userspace VESA VGA graphics support"
654 depends on FB && CONNECTOR
655 select FB_CFB_FILLRECT
656 select FB_CFB_COPYAREA
657 select FB_CFB_IMAGEBLIT
658 select FB_MODE_HELPERS
660 This is the frame buffer driver for generic VBE 2.0 compliant
661 graphic cards. It can also take advantage of VBE 3.0 features,
662 such as refresh rate adjustment.
664 This driver generally provides more features than vesafb but
665 requires a userspace helper application called 'v86d'. See
666 <file:Documentation/fb/uvesafb.txt> for more information.
671 bool "VESA VGA graphics support"
672 depends on (FB = y) && X86
673 select FB_CFB_FILLRECT
674 select FB_CFB_COPYAREA
675 select FB_CFB_IMAGEBLIT
677 This is the frame buffer device driver for generic VESA 2.0
678 compliant graphic cards. The older VESA 1.2 cards are not supported.
679 You will get a boot time penguin logo at no additional cost. Please
680 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
683 bool "EFI-based Framebuffer Support"
684 depends on (FB = y) && X86
685 select FB_CFB_FILLRECT
686 select FB_CFB_COPYAREA
687 select FB_CFB_IMAGEBLIT
689 This is the EFI frame buffer device driver. If the firmware on
690 your platform is UEFI2.0, select Y to add support for
691 Graphics Output Protocol for early console messages to appear.
694 bool "Intel-based Macintosh Framebuffer Support"
695 depends on (FB = y) && X86 && EFI
696 select FB_CFB_FILLRECT
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
700 This is the frame buffer device driver for the Intel-based Macintosh
703 tristate "N411 Apollo/Hecuba devkit support"
704 depends on FB && X86 && MMU
705 select FB_SYS_FILLRECT
706 select FB_SYS_COPYAREA
707 select FB_SYS_IMAGEBLIT
709 select FB_DEFERRED_IO
712 This enables support for the Apollo display controller in its
713 Hecuba form using the n411 devkit.
716 tristate "Hercules mono graphics support"
718 select FB_CFB_FILLRECT
719 select FB_CFB_COPYAREA
720 select FB_CFB_IMAGEBLIT
722 Say Y here if you have a Hercules mono graphics card.
724 To compile this driver as a module, choose M here: the
725 module will be called hgafb.
727 As this card technology is 15 years old, most people will answer N
731 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
732 depends on FB_HGA && EXPERIMENTAL
734 This will compile the Hercules mono graphics with
735 acceleration functions.
738 tristate "SGI Visual Workstation framebuffer support"
739 depends on FB && X86_VISWS
740 select FB_CFB_FILLRECT
741 select FB_CFB_COPYAREA
742 select FB_CFB_IMAGEBLIT
744 SGI Visual Workstation support for framebuffer graphics.
747 bool "SGI Graphics Backend frame buffer support"
748 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
749 select FB_CFB_FILLRECT
750 select FB_CFB_COPYAREA
751 select FB_CFB_IMAGEBLIT
753 This is the frame buffer device driver for SGI Graphics Backend.
754 This chip is used in SGI O2 and Visual Workstation 320/540.
757 int "Video memory size in MB"
761 This is the amount of memory reserved for the framebuffer,
762 which can be any value between 1MB and 8MB.
765 bool "SBUS and UPA framebuffers"
766 depends on (FB = y) && SPARC
768 Say Y if you want support for SBUS or UPA based frame buffer device.
772 depends on (FB = y) && (SPARC && FB_SBUS)
773 select FB_CFB_FILLRECT
774 select FB_CFB_COPYAREA
775 select FB_CFB_IMAGEBLIT
777 This is the frame buffer device driver for the BWtwo frame buffer.
780 bool "CGthree support"
781 depends on (FB = y) && (SPARC && FB_SBUS)
782 select FB_CFB_FILLRECT
783 select FB_CFB_COPYAREA
784 select FB_CFB_IMAGEBLIT
786 This is the frame buffer device driver for the CGthree frame buffer.
789 bool "CGsix (GX,TurboGX) support"
790 depends on (FB = y) && (SPARC && FB_SBUS)
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
794 This is the frame buffer device driver for the CGsix (GX, TurboGX)
798 bool "Creator/Creator3D/Elite3D support"
799 depends on FB_SBUS && SPARC64
800 select FB_CFB_COPYAREA
801 select FB_CFB_IMAGEBLIT
803 This is the frame buffer device driver for the Creator, Creator3D,
804 and Elite3D graphics boards.
807 bool "TCX (SS4/SS5 only) support"
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 TCX 24/8bit frame
817 bool "CGfourteen (SX) support"
819 select FB_CFB_FILLRECT
820 select FB_CFB_COPYAREA
821 select FB_CFB_IMAGEBLIT
823 This is the frame buffer device driver for the CGfourteen frame
824 buffer on Desktop SPARCsystems with the SX graphics option.
827 bool "P9100 (Sparcbook 3 only) support"
829 select FB_CFB_FILLRECT
830 select FB_CFB_COPYAREA
831 select FB_CFB_IMAGEBLIT
833 This is the frame buffer device driver for the P9100 card
834 supported on Sparcbook 3 machines.
837 bool "Leo (ZX) support"
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for the SBUS-based Sun ZX
844 (leo) frame buffer cards.
847 bool "IGA 168x display support"
848 depends on (FB = y) && SPARC32
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
853 This is the framebuffer device for the INTERGRAPHICS 1680 and
854 successor frame buffer cards.
857 bool "Sun XVR-500 3DLABS Wildcat support"
858 depends on (FB = y) && PCI && SPARC64
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 This is the framebuffer device for the Sun XVR-500 and similar
864 graphics cards based upon the 3DLABS Wildcat chipset. The driver
865 only works on sparc64 systems where the system firmware has
866 mostly initialized the card already. It is treated as a
867 completely dumb framebuffer device.
870 bool "Sun XVR-2500 3DLABS Wildcat support"
871 depends on (FB = y) && PCI && SPARC64
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the framebuffer device for the Sun XVR-2500 and similar
877 graphics cards based upon the 3DLABS Wildcat chipset. The driver
878 only works on sparc64 systems where the system firmware has
879 mostly initialized the card already. It is treated as a
880 completely dumb framebuffer device.
883 tristate "NEC PowerVR 2 display support"
884 depends on FB && SH_DREAMCAST
885 select FB_CFB_FILLRECT
886 select FB_CFB_COPYAREA
887 select FB_CFB_IMAGEBLIT
889 Say Y here if you have a PowerVR 2 card in your box. If you plan to
890 run linux on your Dreamcast, you will have to say Y here.
891 This driver may or may not work on other PowerVR 2 cards, but is
892 totally untested. Use at your own risk. If unsure, say N.
894 To compile this driver as a module, choose M here: the
895 module will be called pvr2fb.
897 You can pass several parameters to the driver at boot time or at
898 module load time. The parameters look like "video=pvr2:XXX", where
899 the meaning of XXX can be found at the end of the main source file
900 (<file:drivers/video/pvr2fb.c>). Please see the file
901 <file:Documentation/fb/pvr2fb.txt>.
904 bool "Epson 1355 framebuffer support"
905 depends on (FB = y) && ARCH_CEIVA
906 select FB_CFB_FILLRECT
907 select FB_CFB_COPYAREA
908 select FB_CFB_IMAGEBLIT
910 Build in support for the SED1355 Epson Research Embedded RAMDAC
911 LCD/CRT Controller (since redesignated as the S1D13505) as a
912 framebuffer. Product specs at
913 <http://www.erd.epson.com/vdc/html/products.htm>.
916 tristate "Epson S1D13XXX framebuffer support"
918 select FB_CFB_FILLRECT
919 select FB_CFB_COPYAREA
920 select FB_CFB_IMAGEBLIT
922 Support for S1D13XXX framebuffer device family (currently only
923 working with S1D13806). Product specs at
924 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
927 tristate "AT91/AT32 LCD Controller support"
928 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
929 select FB_CFB_FILLRECT
930 select FB_CFB_COPYAREA
931 select FB_CFB_IMAGEBLIT
933 This enables support for the AT91/AT32 LCD Controller.
936 bool "Frame Buffer in internal SRAM"
937 depends on FB_ATMEL && ARCH_AT91SAM9261
939 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
940 to let frame buffer in external SDRAM.
943 bool "Use a STN display with AT91/AT32 LCD Controller"
944 depends on FB_ATMEL && MACH_AT91SAM9261EK
947 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
948 Controller. Say N if you want to connect a TFT.
953 tristate "nVidia Framebuffer Support"
955 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
956 select FB_MODE_HELPERS
957 select FB_CFB_FILLRECT
958 select FB_CFB_COPYAREA
959 select FB_CFB_IMAGEBLIT
963 This driver supports graphics boards with the nVidia chips, TNT
964 and newer. For very old chipsets, such as the RIVA128, then use
966 Say Y if you have such a graphics board.
968 To compile this driver as a module, choose M here: the
969 module will be called nvidiafb.
972 bool "Enable DDC Support"
976 This enables I2C support for nVidia Chipsets. This is used
977 only for getting EDID information from the attached display
978 allowing for robust video mode handling and switching.
980 Because fbdev-2.6 requires that drivers must be able to
981 independently validate video mode parameters, you should say Y
984 config FB_NVIDIA_DEBUG
985 bool "Lots of debug output"
989 Say Y here if you want the nVidia driver to output all sorts
990 of debugging information to provide to the maintainer when
991 something goes wrong.
993 config FB_NVIDIA_BACKLIGHT
994 bool "Support for backlight control"
998 Say Y here if you want to control the backlight of your display.
1001 tristate "nVidia Riva support"
1002 depends on FB && PCI
1003 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1004 select FB_MODE_HELPERS
1005 select FB_CFB_FILLRECT
1006 select FB_CFB_COPYAREA
1007 select FB_CFB_IMAGEBLIT
1011 This driver supports graphics boards with the nVidia Riva/Geforce
1013 Say Y if you have such a graphics board.
1015 To compile this driver as a module, choose M here: the
1016 module will be called rivafb.
1019 bool "Enable DDC Support"
1023 This enables I2C support for nVidia Chipsets. This is used
1024 only for getting EDID information from the attached display
1025 allowing for robust video mode handling and switching.
1027 Because fbdev-2.6 requires that drivers must be able to
1028 independently validate video mode parameters, you should say Y
1031 config FB_RIVA_DEBUG
1032 bool "Lots of debug output"
1036 Say Y here if you want the Riva driver to output all sorts
1037 of debugging information to provide to the maintainer when
1038 something goes wrong.
1040 config FB_RIVA_BACKLIGHT
1041 bool "Support for backlight control"
1045 Say Y here if you want to control the backlight of your display.
1048 tristate "Intel 810/815 support (EXPERIMENTAL)"
1049 depends on FB && EXPERIMENTAL && PCI && X86_32
1052 select FB_MODE_HELPERS
1053 select FB_CFB_FILLRECT
1054 select FB_CFB_COPYAREA
1055 select FB_CFB_IMAGEBLIT
1058 This driver supports the on-board graphics built in to the Intel 810
1059 and 815 chipsets. Say Y if you have and plan to use such a board.
1061 To compile this driver as a module, choose M here: the
1062 module will be called i810fb.
1064 For more information, please read
1065 <file:Documentation/fb/intel810.txt>
1068 bool "use VESA Generalized Timing Formula"
1071 If you say Y, then the VESA standard, Generalized Timing Formula
1072 or GTF, will be used to calculate the required video timing values
1073 per video mode. Since the GTF allows nondiscrete timings
1074 (nondiscrete being a range of values as opposed to discrete being a
1075 set of values), you'll be able to use any combination of horizontal
1076 and vertical resolutions, and vertical refresh rates without having
1077 to specify your own timing parameters. This is especially useful
1078 to maximize the performance of an aging display, or if you just
1079 have a display with nonstandard dimensions. A VESA compliant
1080 monitor is recommended, but can still work with non-compliant ones.
1081 If you need or want this, then select this option. The timings may
1082 not be compliant with Intel's recommended values. Use at your own
1085 If you say N, the driver will revert to discrete video timings
1086 using a set recommended by Intel in their documentation.
1091 bool "Enable DDC Support"
1092 depends on FB_I810 && FB_I810_GTF
1097 tristate "Intel LE80578 (Vermilion) support"
1098 depends on FB && PCI && X86
1099 select FB_MODE_HELPERS
1100 select FB_CFB_FILLRECT
1101 select FB_CFB_COPYAREA
1102 select FB_CFB_IMAGEBLIT
1104 This driver supports the LE80578 (Vermilion Range) chipset
1106 config FB_CARILLO_RANCH
1107 tristate "Intel Carillo Ranch support"
1108 depends on FB_LE80578 && FB && PCI && X86
1110 This driver supports the LE80578 (Carillo Ranch) board
1113 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1114 depends on FB && EXPERIMENTAL && PCI && X86
1117 select FB_MODE_HELPERS
1118 select FB_CFB_FILLRECT
1119 select FB_CFB_COPYAREA
1120 select FB_CFB_IMAGEBLIT
1122 This driver supports the on-board graphics built in to the Intel
1123 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1124 Say Y if you have and plan to use such a board.
1126 If you say Y here and want DDC/I2C support you must first say Y to
1127 "I2C support" and "I2C bit-banging support" in the character devices
1130 If you say M here then "I2C support" and "I2C bit-banging support"
1131 can be build either as modules or built-in.
1133 To compile this driver as a module, choose M here: the
1134 module will be called intelfb.
1136 For more information, please read <file:Documentation/fb/intelfb.txt>
1138 config FB_INTEL_DEBUG
1139 bool "Intel driver Debug Messages"
1142 Say Y here if you want the Intel driver to output all sorts
1143 of debugging information to provide to the maintainer when
1144 something goes wrong.
1147 bool "DDC/I2C for Intel framebuffer support"
1152 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1155 tristate "Matrox acceleration"
1156 depends on FB && PCI
1157 select FB_CFB_FILLRECT
1158 select FB_CFB_COPYAREA
1159 select FB_CFB_IMAGEBLIT
1160 select FB_TILEBLITTING
1161 select FB_MACMODES if PPC_PMAC
1163 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1164 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1165 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1166 Matrox G400, G450 or G550 card in your box.
1168 To compile this driver as a module, choose M here: the
1169 module will be called matroxfb.
1171 You can pass several parameters to the driver at boot time or at
1172 module load time. The parameters look like "video=matrox:XXX", and
1173 are described in <file:Documentation/fb/matroxfb.txt>.
1175 config FB_MATROX_MILLENIUM
1176 bool "Millennium I/II support"
1177 depends on FB_MATROX
1179 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1180 video card. If you select "Advanced lowlevel driver options" below,
1181 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1182 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1183 also use font widths different from 8.
1185 config FB_MATROX_MYSTIQUE
1186 bool "Mystique support"
1187 depends on FB_MATROX
1189 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1190 video card. If you select "Advanced lowlevel driver options" below,
1191 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1192 packed pixel and 32 bpp packed pixel. You can also use font widths
1196 bool "G100/G200/G400/G450/G550 support"
1197 depends on FB_MATROX
1199 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1200 video card. If you select "Advanced lowlevel driver options", you
1201 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1202 pixel and 32 bpp packed pixel. You can also use font widths
1205 If you need support for G400 secondary head, you must first say Y to
1206 "I2C support" in the character devices section, and then to
1207 "Matrox I2C support" and "G400 second head support" here in the
1208 framebuffer section. G450/G550 secondary head and digital output
1209 are supported without additional modules.
1211 The driver starts in monitor mode. You must use the matroxset tool
1212 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1213 swap primary and secondary head outputs, or to change output mode.
1214 Secondary head driver always start in 640x480 resolution and you
1215 must use fbset to change it.
1217 Do not forget that second head supports only 16 and 32 bpp
1218 packed pixels, so it is a good idea to compile them into the kernel
1219 too. You can use only some font widths, as the driver uses generic
1220 painting procedures (the secondary head does not use acceleration
1223 G450/G550 hardware can display TV picture only from secondary CRTC,
1224 and it performs no scaling, so picture must have 525 or 625 lines.
1226 config FB_MATROX_I2C
1227 tristate "Matrox I2C support"
1228 depends on FB_MATROX
1231 This drivers creates I2C buses which are needed for accessing the
1232 DDC (I2C) bus present on all Matroxes, an I2C bus which
1233 interconnects Matrox optional devices, like MGA-TVO on G200 and
1234 G400, and the secondary head DDC bus, present on G400 only.
1236 You can say Y or M here if you want to experiment with monitor
1237 detection code. You must say Y or M here if you want to use either
1238 second head of G400 or MGA-TVO on G200 or G400.
1240 If you compile it as module, it will create a module named
1243 config FB_MATROX_MAVEN
1244 tristate "G400 second head support"
1245 depends on FB_MATROX_G && FB_MATROX_I2C
1247 WARNING !!! This support does not work with G450 !!!
1249 Say Y or M here if you want to use a secondary head (meaning two
1250 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1251 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1252 secondary head output is blanked while you are in X. With XFree
1253 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1254 the fbdev driver on first head and the fbdev driver on second head.
1256 If you compile it as module, two modules are created,
1257 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1258 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1259 also load i2c-matroxfb to get it to run.
1261 The driver starts in monitor mode and you must use the matroxset
1263 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1264 PAL or NTSC or to swap primary and secondary head outputs.
1265 Secondary head driver also always start in 640x480 resolution, you
1266 must use fbset to change it.
1268 Also do not forget that second head supports only 16 and 32 bpp
1269 packed pixels, so it is a good idea to compile them into the kernel
1270 too. You can use only some font widths, as the driver uses generic
1271 painting procedures (the secondary head does not use acceleration
1274 config FB_MATROX_MULTIHEAD
1275 bool "Multihead support"
1276 depends on FB_MATROX
1278 Say Y here if you have more than one (supported) Matrox device in
1279 your computer and you want to use all of them for different monitors
1280 ("multihead"). If you have only one device, you should say N because
1281 the driver compiled with Y is larger and a bit slower, especially on
1284 If you said M to "Matrox unified accelerated driver" and N here, you
1285 will still be able to use several Matrox devices simultaneously:
1286 insert several instances of the module matroxfb into the kernel
1287 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1288 for the different Matrox devices. This method is slightly faster but
1289 uses 40 KB of kernel memory per Matrox card.
1291 There is no need for enabling 'Matrox multihead support' if you have
1292 only one Matrox card in the box.
1295 tristate "ATI Radeon display support"
1296 depends on FB && PCI
1297 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1298 select FB_MODE_HELPERS
1299 select FB_CFB_FILLRECT
1300 select FB_CFB_COPYAREA
1301 select FB_CFB_IMAGEBLIT
1302 select FB_MACMODES if PPC_OF
1304 Choose this option if you want to use an ATI Radeon graphics card as
1305 a framebuffer device. There are both PCI and AGP versions. You
1306 don't need to choose this to run the Radeon in plain VGA mode.
1308 If you say Y here and want DDC/I2C support you must first say Y to
1309 "I2C support" and "I2C bit-banging support" in the character devices
1312 If you say M here then "I2C support" and "I2C bit-banging support"
1313 can be build either as modules or built-in.
1315 There is a product page at
1316 http://apps.ati.com/ATIcompare/
1318 config FB_RADEON_I2C
1319 bool "DDC/I2C for ATI Radeon support"
1320 depends on FB_RADEON
1324 Say Y here if you want DDC/I2C support for your Radeon board.
1326 config FB_RADEON_BACKLIGHT
1327 bool "Support for backlight control"
1328 depends on FB_RADEON
1331 Say Y here if you want to control the backlight of your display.
1333 config FB_RADEON_DEBUG
1334 bool "Lots of debug output from Radeon driver"
1335 depends on FB_RADEON
1338 Say Y here if you want the Radeon driver to output all sorts
1339 of debugging information to provide to the maintainer when
1340 something goes wrong.
1343 tristate "ATI Rage128 display support"
1344 depends on FB && PCI
1345 select FB_CFB_FILLRECT
1346 select FB_CFB_COPYAREA
1347 select FB_CFB_IMAGEBLIT
1348 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1349 select FB_MACMODES if PPC_PMAC
1351 This driver supports graphics boards with the ATI Rage128 chips.
1352 Say Y if you have such a graphics board and read
1353 <file:Documentation/fb/aty128fb.txt>.
1355 To compile this driver as a module, choose M here: the
1356 module will be called aty128fb.
1358 config FB_ATY128_BACKLIGHT
1359 bool "Support for backlight control"
1360 depends on FB_ATY128
1363 Say Y here if you want to control the backlight of your display.
1366 tristate "ATI Mach64 display support" if PCI || ATARI
1367 depends on FB && !SPARC32
1368 select FB_CFB_FILLRECT
1369 select FB_CFB_COPYAREA
1370 select FB_CFB_IMAGEBLIT
1371 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1372 select FB_MACMODES if PPC
1374 This driver supports graphics boards with the ATI Mach64 chips.
1375 Say Y if you have such a graphics board.
1377 To compile this driver as a module, choose M here: the
1378 module will be called atyfb.
1381 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1382 depends on PCI && FB_ATY
1383 default y if SPARC64 && PCI
1385 Say Y here to support use of ATI's 64-bit Rage boards (or other
1386 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1387 framebuffer device. The ATI product support page for these boards
1388 is at <http://support.ati.com/products/pc/mach64/>.
1390 config FB_ATY_GENERIC_LCD
1391 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1392 depends on FB_ATY_CT
1394 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1395 Rage XC, or Rage XL chipset.
1398 bool "Mach64 GX support" if PCI
1402 Say Y here to support use of the ATI Mach64 Graphics Expression
1403 board (or other boards based on the Mach64 GX chipset) as a
1404 framebuffer device. The ATI product support page for these boards
1406 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1408 config FB_ATY_BACKLIGHT
1409 bool "Support for backlight control"
1413 Say Y here if you want to control the backlight of your display.
1416 tristate "S3 Trio/Virge support"
1417 depends on FB && PCI
1418 select FB_CFB_FILLRECT
1419 select FB_CFB_COPYAREA
1420 select FB_CFB_IMAGEBLIT
1421 select FB_TILEBLITTING
1424 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1426 Driver for graphics boards with S3 Trio / S3 Virge chip.
1429 tristate "S3 Savage support"
1430 depends on FB && PCI && EXPERIMENTAL
1431 select FB_MODE_HELPERS
1432 select FB_CFB_FILLRECT
1433 select FB_CFB_COPYAREA
1434 select FB_CFB_IMAGEBLIT
1437 This driver supports notebooks and computers with S3 Savage PCI/AGP
1440 Say Y if you have such a graphics card.
1442 To compile this driver as a module, choose M here; the module
1443 will be called savagefb.
1445 config FB_SAVAGE_I2C
1446 bool "Enable DDC2 Support"
1447 depends on FB_SAVAGE
1450 This enables I2C support for S3 Savage Chipsets. This is used
1451 only for getting EDID information from the attached display
1452 allowing for robust video mode handling and switching.
1454 Because fbdev-2.6 requires that drivers must be able to
1455 independently validate video mode parameters, you should say Y
1458 config FB_SAVAGE_ACCEL
1459 bool "Enable Console Acceleration"
1460 depends on FB_SAVAGE
1463 This option will compile in console acceleration support. If
1464 the resulting framebuffer console has bothersome glitches, then
1468 tristate "SiS/XGI display support"
1469 depends on FB && PCI
1470 select FB_CFB_FILLRECT
1471 select FB_CFB_COPYAREA
1472 select FB_CFB_IMAGEBLIT
1474 This is the frame buffer device driver for the SiS 300, 315, 330
1475 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1476 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1478 To compile this driver as a module, choose M here; the module
1479 will be called sisfb.
1482 bool "SiS 300 series support"
1485 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1488 bool "SiS 315/330/340 series and XGI support"
1491 Say Y here to support use of the SiS 315, 330 and 340 series
1492 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1493 as XGI V3XT, V5, V8 and Z7.
1496 tristate "NeoMagic display support"
1497 depends on FB && PCI
1498 select FB_MODE_HELPERS
1499 select FB_CFB_FILLRECT
1500 select FB_CFB_COPYAREA
1501 select FB_CFB_IMAGEBLIT
1504 This driver supports notebooks with NeoMagic PCI chips.
1505 Say Y if you have such a graphics card.
1507 To compile this driver as a module, choose M here: the
1508 module will be called neofb.
1511 tristate "IMG Kyro support"
1512 depends on FB && PCI
1513 select FB_CFB_FILLRECT
1514 select FB_CFB_COPYAREA
1515 select FB_CFB_IMAGEBLIT
1517 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1520 To compile this driver as a module, choose M here: the
1521 module will be called kyrofb.
1524 tristate "3Dfx Banshee/Voodoo3 display support"
1525 depends on FB && PCI
1526 select FB_CFB_IMAGEBLIT
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1530 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1531 chips. Say Y if you have such a graphics board.
1533 To compile this driver as a module, choose M here: the
1534 module will be called tdfxfb.
1536 config FB_3DFX_ACCEL
1537 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1538 depends on FB_3DFX && EXPERIMENTAL
1540 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1541 with acceleration functions.
1545 tristate "3Dfx Voodoo Graphics (sst1) support"
1546 depends on FB && PCI
1547 select FB_CFB_FILLRECT
1548 select FB_CFB_COPYAREA
1549 select FB_CFB_IMAGEBLIT
1551 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1552 Voodoo2 (cvg) based graphics card.
1554 To compile this driver as a module, choose M here: the
1555 module will be called sstfb.
1557 WARNING: Do not use any application that uses the 3D engine
1558 (namely glide) while using this driver.
1559 Please read the <file:Documentation/fb/sstfb.txt> for supported
1560 options and other important info support.
1563 tristate "VIA VT8623 support"
1564 depends on FB && PCI
1565 select FB_CFB_FILLRECT
1566 select FB_CFB_COPYAREA
1567 select FB_CFB_IMAGEBLIT
1568 select FB_TILEBLITTING
1571 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1573 Driver for CastleRock integrated graphics core in the
1574 VIA VT8623 [Apollo CLE266] chipset.
1577 tristate "Cyberblade/i1 support"
1578 depends on FB && PCI && X86_32 && !64BIT
1579 select FB_CFB_IMAGEBLIT
1581 This driver is supposed to support the Trident Cyberblade/i1
1582 graphics core integrated in the VIA VT8601A North Bridge,
1583 also known as VIA Apollo PLE133.
1586 - Developed, tested and working on EPIA 5000 and EPIA 800.
1587 - Does work reliable on all systems with CRT/LCD connected to
1589 - Should work on systems that do use the internal LCD port, but
1590 this is absolutely not tested.
1592 Character imageblit, copyarea and rectangle fill are hw accelerated,
1593 ypan scrolling is used by default.
1595 Please do read <file:Documentation/fb/cyblafb/*>.
1597 To compile this driver as a module, choose M here: the
1598 module will be called cyblafb.
1601 tristate "Trident support"
1602 depends on FB && PCI
1603 select FB_CFB_FILLRECT
1604 select FB_CFB_COPYAREA
1605 select FB_CFB_IMAGEBLIT
1607 This driver is supposed to support graphics boards with the
1608 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1609 but also on some motherboards. For more information, read
1610 <file:Documentation/fb/tridentfb.txt>
1612 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1615 Say Y if you have such a graphics board.
1618 To compile this driver as a module, choose M here: the
1619 module will be called tridentfb.
1621 config FB_TRIDENT_ACCEL
1622 bool "Trident Acceleration functions (EXPERIMENTAL)"
1623 depends on FB_TRIDENT && EXPERIMENTAL
1625 This will compile the Trident frame buffer device with
1626 acceleration functions.
1629 tristate "ARK 2000PV support"
1630 depends on FB && PCI
1631 select FB_CFB_FILLRECT
1632 select FB_CFB_COPYAREA
1633 select FB_CFB_IMAGEBLIT
1634 select FB_TILEBLITTING
1637 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1639 Driver for PCI graphics boards with ARK 2000PV chip
1640 and ICS 5342 RAMDAC.
1643 tristate "Permedia3 support (EXPERIMENTAL)"
1644 depends on FB && PCI && EXPERIMENTAL
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 3DLabs Permedia3
1650 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1651 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1652 and maybe other boards.
1655 tristate "Fujitsu carmine frame buffer support"
1656 depends on FB && PCI
1657 select FB_CFB_FILLRECT
1658 select FB_CFB_COPYAREA
1659 select FB_CFB_IMAGEBLIT
1661 This is the frame buffer device driver for the Fujitsu Carmine chip.
1662 The driver provides two independent frame buffer devices.
1665 depends on FB_CARMINE
1666 prompt "DRAM timing"
1667 default FB_CARMINE_DRAM_EVAL
1669 config FB_CARMINE_DRAM_EVAL
1670 bool "Eval board timings"
1672 Use timings which work on the eval card.
1674 config CARMINE_DRAM_CUSTOM
1675 bool "Custom board timings"
1677 Use custom board timings.
1681 bool "Au1100 LCD Driver"
1682 depends on (FB = y) && MIPS && SOC_AU1100
1683 select FB_CFB_FILLRECT
1684 select FB_CFB_COPYAREA
1685 select FB_CFB_IMAGEBLIT
1687 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1688 various panels and CRTs by passing in kernel cmd line option
1689 au1100fb:panel=<name>.
1692 bool "Au1200 LCD Driver"
1693 depends on (FB = y) && MIPS && SOC_AU1200
1694 select FB_CFB_FILLRECT
1695 select FB_CFB_COPYAREA
1696 select FB_CFB_IMAGEBLIT
1698 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1699 various panels and CRTs by passing in kernel cmd line option
1700 au1200fb:panel=<name>.
1702 source "drivers/video/geode/Kconfig"
1705 tristate "HD64461 Frame Buffer support"
1706 depends on FB && HD64461
1707 select FB_CFB_FILLRECT
1708 select FB_CFB_COPYAREA
1709 select FB_CFB_IMAGEBLIT
1711 This is the frame buffer device driver for the Hitachi HD64461 LCD
1715 bool "PMAG-AA TURBOchannel framebuffer support"
1716 depends on (FB = y) && TC
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1721 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1722 used mainly in the MIPS-based DECstation series.
1725 tristate "PMAG-BA TURBOchannel framebuffer support"
1727 select FB_CFB_FILLRECT
1728 select FB_CFB_COPYAREA
1729 select FB_CFB_IMAGEBLIT
1731 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1732 used mainly in the MIPS-based DECstation series.
1735 tristate "PMAGB-B TURBOchannel framebuffer support"
1737 select FB_CFB_FILLRECT
1738 select FB_CFB_COPYAREA
1739 select FB_CFB_IMAGEBLIT
1741 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1742 in the MIPS-based DECstation series. The card is currently only
1743 supported in 1280x1024x8 mode.
1746 bool "Maxine (Personal DECstation) onboard framebuffer support"
1747 depends on (FB = y) && MACH_DECSTATION
1748 select FB_CFB_FILLRECT
1749 select FB_CFB_COPYAREA
1750 select FB_CFB_IMAGEBLIT
1752 Support for the onboard framebuffer (1024x768x8) in the Personal
1753 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1757 bool "G364 frame buffer support"
1758 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1759 select FB_CFB_FILLRECT
1760 select FB_CFB_COPYAREA
1761 select FB_CFB_IMAGEBLIT
1763 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1764 Olivetti M700-10 systems.
1767 bool "Motorola 68328 native frame buffer support"
1768 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1769 select FB_CFB_FILLRECT
1770 select FB_CFB_COPYAREA
1771 select FB_CFB_IMAGEBLIT
1773 Say Y here if you want to support the built-in frame buffer of
1774 the Motorola 68328 CPU family.
1777 tristate "PXA LCD framebuffer support"
1778 depends on FB && ARCH_PXA
1779 select FB_CFB_FILLRECT
1780 select FB_CFB_COPYAREA
1781 select FB_CFB_IMAGEBLIT
1783 Frame buffer driver for the built-in LCD controller in the Intel
1786 This driver is also available as a module ( = code which can be
1787 inserted and removed from the running kernel whenever you want). The
1788 module will be called pxafb. If you want to compile it as a module,
1789 say M here and read <file:Documentation/kbuild/modules.txt>.
1793 config FB_PXA_SMARTPANEL
1794 bool "PXA Smartpanel LCD support"
1798 config FB_PXA_PARAMETERS
1799 bool "PXA LCD command line parameters"
1803 Enable the use of kernel command line or module parameters
1804 to configure the physical properties of the LCD panel when
1805 using the PXA LCD driver.
1807 This option allows you to override the panel parameters
1808 supplied by the platform in order to support multiple
1809 different models of flatpanel. If you will only be using a
1810 single model of flatpanel then you can safely leave this
1813 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1816 tristate "2700G LCD framebuffer support"
1817 depends on FB && ARCH_PXA
1818 select FB_CFB_FILLRECT
1819 select FB_CFB_COPYAREA
1820 select FB_CFB_IMAGEBLIT
1822 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1826 bool "Enable debugging info via debugfs"
1827 depends on FB_MBX && DEBUG_FS
1830 Enable this if you want debugging information using the debug
1831 filesystem (debugfs)
1836 tristate "Freescale DIU framebuffer support"
1837 depends on FB && FSL_SOC
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1841 select PPC_LIB_RHEAP
1843 Framebuffer driver for the Freescale SoC DIU
1846 tristate "W100 frame buffer support"
1847 depends on FB && ARCH_PXA
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1853 It can also drive the w3220 chip found on iPAQ hx4700.
1855 This driver is also available as a module ( = code which can be
1856 inserted and removed from the running kernel whenever you want). The
1857 module will be called w100fb. If you want to compile it as a module,
1858 say M here and read <file:Documentation/kbuild/modules.txt>.
1862 config FB_SH_MOBILE_LCDC
1863 tristate "SuperH Mobile LCDC framebuffer support"
1864 depends on FB && SUPERH
1865 select FB_CFB_FILLRECT
1866 select FB_CFB_COPYAREA
1867 select FB_CFB_IMAGEBLIT
1870 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1873 tristate "S3C2410 LCD framebuffer support"
1874 depends on FB && ARCH_S3C2410
1875 select FB_CFB_FILLRECT
1876 select FB_CFB_COPYAREA
1877 select FB_CFB_IMAGEBLIT
1879 Frame buffer driver for the built-in LCD controller in the Samsung
1882 This driver is also available as a module ( = code which can be
1883 inserted and removed from the running kernel whenever you want). The
1884 module will be called s3c2410fb. If you want to compile it as a module,
1885 say M here and read <file:Documentation/kbuild/modules.txt>.
1888 config FB_S3C2410_DEBUG
1889 bool "S3C2410 lcd debug messages"
1890 depends on FB_S3C2410
1892 Turn on debugging messages. Note that you can set/unset at run time
1896 tristate "Silicon Motion SM501 framebuffer support"
1897 depends on FB && MFD_SM501
1898 select FB_CFB_FILLRECT
1899 select FB_CFB_COPYAREA
1900 select FB_CFB_IMAGEBLIT
1902 Frame buffer driver for the CRT and LCD controllers in the Silicon
1905 This driver is also available as a module ( = code which can be
1906 inserted and removed from the running kernel whenever you want). The
1907 module will be called sm501fb. If you want to compile it as a module,
1908 say M here and read <file:Documentation/kbuild/modules.txt>.
1913 config FB_PNX4008_DUM
1914 tristate "Display Update Module support on Philips PNX4008 board"
1915 depends on FB && ARCH_PNX4008
1917 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1919 config FB_PNX4008_DUM_RGB
1920 tristate "RGB Framebuffer support on Philips PNX4008 board"
1921 depends on FB_PNX4008_DUM
1922 select FB_CFB_FILLRECT
1923 select FB_CFB_COPYAREA
1924 select FB_CFB_IMAGEBLIT
1926 Say Y here to enable support for PNX4008 RGB Framebuffer
1928 config FB_IBM_GXT4500
1929 tristate "Framebuffer support for IBM GXT4500P adaptor"
1930 depends on FB && PPC
1931 select FB_CFB_FILLRECT
1932 select FB_CFB_COPYAREA
1933 select FB_CFB_IMAGEBLIT
1935 Say Y here to enable support for the IBM GXT4500P display
1936 adaptor, found on some IBM System P (pSeries) machines.
1939 tristate "PS3 GPU framebuffer driver"
1940 depends on FB && PS3_PS3AV
1941 select FB_SYS_FILLRECT
1942 select FB_SYS_COPYAREA
1943 select FB_SYS_IMAGEBLIT
1945 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1947 Include support for the virtual frame buffer in the PS3 platform.
1949 config FB_PS3_DEFAULT_SIZE_M
1950 int "PS3 default frame buffer size (in MiB)"
1954 This is the default size (in MiB) of the virtual frame buffer in
1956 The default value can be overridden on the kernel command line
1957 using the "ps3fb" option (e.g. "ps3fb=9M");
1960 tristate "Xilinx frame buffer support"
1961 depends on FB && XILINX_VIRTEX
1962 select FB_CFB_FILLRECT
1963 select FB_CFB_COPYAREA
1964 select FB_CFB_IMAGEBLIT
1966 Include support for the Xilinx ML300/ML403 reference design
1967 framebuffer. ML300 carries a 640*480 LCD display on the board,
1968 ML403 uses a standard DB15 VGA connector.
1971 tristate "Cobalt server LCD frame buffer support"
1972 depends on FB && MIPS_COBALT
1975 bool "SH7760/SH7763 LCDC support"
1976 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763)
1977 select FB_CFB_FILLRECT
1978 select FB_CFB_COPYAREA
1979 select FB_CFB_IMAGEBLIT
1981 Support for the SH7760/SH7763 integrated (D)STN/TFT LCD Controller.
1982 Supports display resolutions up to 1024x1024 pixel, grayscale and
1983 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
1984 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
1985 panels <= 320 pixel horizontal resolution.
1988 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1990 select FB_SYS_FILLRECT
1991 select FB_SYS_COPYAREA
1992 select FB_SYS_IMAGEBLIT
1995 This is a `virtual' frame buffer device. It operates on a chunk of
1996 unswappable kernel memory instead of on the memory of a graphics
1997 board. This means you cannot see any output sent to this frame
1998 buffer device, while it does consume precious memory. The main use
1999 of this frame buffer device is testing and debugging the frame
2000 buffer subsystem. Do NOT enable it for normal systems! To protect
2001 the innocent, it has to be enabled explicitly at boot time using the
2002 kernel option `video=vfb:'.
2004 To compile this driver as a module, choose M here: the
2005 module will be called vfb. In order to load it, you must use
2006 the vfb_enable=1 option.
2010 config XEN_FBDEV_FRONTEND
2011 tristate "Xen virtual frame buffer support"
2012 depends on FB && XEN
2013 select FB_SYS_FILLRECT
2014 select FB_SYS_COPYAREA
2015 select FB_SYS_IMAGEBLIT
2017 select FB_DEFERRED_IO
2020 This driver implements the front-end of the Xen virtual
2021 frame buffer driver. It communicates with a back-end
2025 tristate "E-Ink Metronome/8track controller support"
2027 select FB_SYS_FILLRECT
2028 select FB_SYS_COPYAREA
2029 select FB_SYS_IMAGEBLIT
2031 select FB_DEFERRED_IO
2033 This driver implements support for the E-Ink Metronome
2034 controller. The pre-release name for this device was 8track
2035 and could also have been called by some vendors as PVI-nnnn.
2037 source "drivers/video/omap/Kconfig"
2039 source "drivers/video/backlight/Kconfig"
2040 source "drivers/video/display/Kconfig"
2043 source "drivers/video/console/Kconfig"
2046 if FB || SGI_NEWPORT_CONSOLE
2047 source "drivers/video/logo/Kconfig"