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.munted.org.uk/programming/Framebuffer-HOWTO-1.2.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_BOOT_VESA_SUPPORT
84 If true, at least one selected framebuffer driver can take advantage
85 of VESA video modes set at an early boot stage via the vga= parameter.
87 config FB_CFB_FILLRECT
92 Include the cfb_fillrect function for generic software rectangle
93 filling. This is used by drivers that don't provide their own
94 (accelerated) version.
96 config FB_CFB_COPYAREA
101 Include the cfb_copyarea function for generic software area copying.
102 This is used by drivers that don't provide their own (accelerated)
105 config FB_CFB_IMAGEBLIT
110 Include the cfb_imageblit function for generic software image
111 blitting. This is used by drivers that don't provide their own
112 (accelerated) version.
114 config FB_CFB_REV_PIXELS_IN_BYTE
119 Allow generic frame-buffer functions to work on displays with 1, 2
120 and 4 bits per pixel depths which has opposite order of pixels in
121 byte order to bytes in long order.
123 config FB_SYS_FILLRECT
128 Include the sys_fillrect function for generic software rectangle
129 filling. This is used by drivers that don't provide their own
130 (accelerated) version and the framebuffer is in system RAM.
132 config FB_SYS_COPYAREA
137 Include the sys_copyarea function for generic software area copying.
138 This is used by drivers that don't provide their own (accelerated)
139 version and the framebuffer is in system RAM.
141 config FB_SYS_IMAGEBLIT
146 Include the sys_imageblit function for generic software image
147 blitting. This is used by drivers that don't provide their own
148 (accelerated) version and the framebuffer is in system RAM.
150 menuconfig FB_FOREIGN_ENDIAN
151 bool "Framebuffer foreign endianness support"
154 This menu will let you enable support for the framebuffers with
155 non-native endianness (e.g. Little-Endian framebuffer on a
156 Big-Endian machine). Most probably you don't have such hardware,
157 so it's safe to say "n" here.
160 prompt "Choice endianness support"
161 depends on FB_FOREIGN_ENDIAN
163 config FB_BOTH_ENDIAN
164 bool "Support for Big- and Little-Endian framebuffers"
167 bool "Support for Big-Endian framebuffers only"
169 config FB_LITTLE_ENDIAN
170 bool "Support for Little-Endian framebuffers only"
179 config FB_DEFERRED_IO
186 depends on FB_DEFERRED_IO
193 Common utility functions useful to fbdev drivers of VGA-based
204 select BACKLIGHT_LCD_SUPPORT
205 select BACKLIGHT_CLASS_DEVICE
208 config FB_MODE_HELPERS
209 bool "Enable Video Mode Handling Helpers"
213 This enables functions for handling video modes using the
214 Generalized Timing Formula and the EDID parser. A few drivers rely
215 on this feature such as the radeonfb, rivafb, and the i810fb. If
216 your driver does not take advantage of this feature, choosing Y will
217 just increase the kernel size by about 5K.
219 config FB_TILEBLITTING
220 bool "Enable Tile Blitting Support"
224 This enables tile blitting. Tile blitting is a drawing technique
225 where the screen is divided into rectangular sections (tiles), whereas
226 the standard blitting divides the screen into pixels. Because the
227 default drawing element is a tile, drawing functions will be passed
228 parameters in terms of number of tiles instead of number of pixels.
229 For example, to draw a single character, instead of using bitmaps,
230 an index to an array of bitmaps will be used. To clear or move a
231 rectangular section of a screen, the rectangle will be described in
232 terms of number of tiles in the x- and y-axis.
234 This is particularly important to one driver, matroxfb. If
237 comment "Frame buffer hardware drivers"
241 tristate "Cirrus Logic support"
242 depends on FB && (ZORRO || PCI)
243 select FB_CFB_FILLRECT
244 select FB_CFB_COPYAREA
245 select FB_CFB_IMAGEBLIT
247 This enables support for Cirrus Logic GD542x/543x based boards on
248 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
250 If you have a PCI-based system, this enables support for these
251 chips: GD-543x, GD-544x, GD-5480.
253 Please read the file <file:Documentation/fb/cirrusfb.txt>.
255 Say N unless you have such a graphics board or plan to get one
256 before you next recompile the kernel.
259 tristate "Permedia2 support"
260 depends on FB && ((AMIGA && BROKEN) || PCI)
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This is the frame buffer device driver for cards based on
266 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
267 The driver was tested on the following cards:
268 Diamond FireGL 1000 PRO AGP
269 ELSA Gloria Synergy PCI
270 Appian Jeronimo PRO (both heads) PCI
271 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
272 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
273 ASK Graphic Blaster Exxtreme AGP
275 To compile this driver as a module, choose M here: the
276 module will be called pm2fb.
278 config FB_PM2_FIFO_DISCONNECT
279 bool "enable FIFO disconnect feature"
280 depends on FB_PM2 && PCI
282 Support the Permedia2 FIFO disconnect feature.
285 tristate "ARM PrimeCell PL110 support"
286 depends on FB && ARM && ARM_AMBA
287 select FB_CFB_FILLRECT
288 select FB_CFB_COPYAREA
289 select FB_CFB_IMAGEBLIT
291 This framebuffer device driver is for the ARM PrimeCell PL110
292 Colour LCD controller. ARM PrimeCells provide the building
293 blocks for System on a Chip devices.
295 If you want to compile this as a module (=code which can be
296 inserted into and removed from the running kernel), say M
297 here and read <file:Documentation/kbuild/modules.txt>. The module
298 will be called amba-clcd.
302 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
304 default FB_ARMCLCD_SHARP_LQ035Q7DB02
306 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
307 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
309 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
310 color QVGA, HRTFT panel. The LogicPD device includes
311 an integrated HRTFT controller IC.
312 The native resolution is 240x320.
314 config FB_ARMCLCD_SHARP_LQ057Q3DC02
315 bool "LogicPD LCD 5.7\" QVGA"
317 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
318 color QVGA, TFT panel. The LogicPD device includes an
319 The native resolution is 320x240.
321 config FB_ARMCLCD_SHARP_LQ64D343
322 bool "LogicPD LCD 6.4\" VGA"
324 This is an implementation of the Sharp LQ64D343, a 6.4"
325 color VGA, TFT panel. The LogicPD device includes an
326 The native resolution is 640x480.
328 config FB_ARMCLCD_SHARP_LQ10D368
329 bool "LogicPD LCD 10.4\" VGA"
331 This is an implementation of the Sharp LQ10D368, a 10.4"
332 color VGA, TFT panel. The LogicPD device includes an
333 The native resolution is 640x480.
336 config FB_ARMCLCD_SHARP_LQ121S1DG41
337 bool "LogicPD LCD 12.1\" SVGA"
339 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
340 color SVGA, TFT panel. The LogicPD device includes an
341 The native resolution is 800x600.
343 This panel requires a clock rate may be an integer fraction
344 of the base LCDCLK frequency. The driver will select the
345 highest frequency available that is lower than the maximum
346 allowed. The panel may flicker if the clock rate is
347 slower than the recommended minimum.
349 config FB_ARMCLCD_AUO_A070VW01_WIDE
350 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
352 This is an implementation of the AU Optronics, a 7.0"
353 WIDE Color. The native resolution is 234x480.
355 config FB_ARMCLCD_HITACHI
356 bool "Hitachi Wide Screen 800x480"
358 This is an implementation of the Hitachi 800x480.
364 bool "Acorn VIDC support"
365 depends on (FB = y) && ARM && ARCH_ACORN
366 select FB_CFB_FILLRECT
367 select FB_CFB_COPYAREA
368 select FB_CFB_IMAGEBLIT
370 This is the frame buffer device driver for the Acorn VIDC graphics
371 hardware found in Acorn RISC PCs and other ARM-based machines. If
375 bool "CLPS711X LCD support"
376 depends on (FB = y) && ARM && ARCH_CLPS711X
377 select FB_CFB_FILLRECT
378 select FB_CFB_COPYAREA
379 select FB_CFB_IMAGEBLIT
381 Say Y to enable the Framebuffer driver for the CLPS7111 and
385 bool "SA-1100 LCD support"
386 depends on (FB = y) && ARM && ARCH_SA1100
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
391 This is a framebuffer device for the SA-1100 LCD Controller.
392 See <http://www.linux-fbdev.org/> for information on framebuffer
395 If you plan to use the LCD display with your SA-1100 system, say
399 tristate "Motorola i.MX LCD support"
400 depends on FB && (ARCH_MX1 || ARCH_MX2)
401 select FB_CFB_FILLRECT
402 select FB_CFB_COPYAREA
403 select FB_CFB_IMAGEBLIT
406 tristate "CyberPro 2000/2010/5000 support"
407 depends on FB && PCI && (BROKEN || !SPARC64)
408 select FB_CFB_FILLRECT
409 select FB_CFB_COPYAREA
410 select FB_CFB_IMAGEBLIT
412 This enables support for the Integraphics CyberPro 20x0 and 5000
413 VGA chips used in the Rebel.com Netwinder and other machines.
414 Say Y if you have a NetWinder or a graphics card containing this
415 device, otherwise say N.
419 depends on (FB = y) && APOLLO
421 select FB_CFB_FILLRECT
422 select FB_CFB_IMAGEBLIT
426 depends on (FB = y) && Q40
428 select FB_CFB_FILLRECT
429 select FB_CFB_COPYAREA
430 select FB_CFB_IMAGEBLIT
433 tristate "Amiga native chipset support"
434 depends on FB && AMIGA
436 This is the frame buffer device driver for the builtin graphics
437 chipset found in Amigas.
439 To compile this driver as a module, choose M here: the
440 module will be called amifb.
443 bool "Amiga OCS chipset support"
446 This enables support for the original Agnus and Denise video chips,
447 found in the Amiga 1000 and most A500's and A2000's. If you intend
448 to run Linux on any of these systems, say Y; otherwise say N.
451 bool "Amiga ECS chipset support"
454 This enables support for the Enhanced Chip Set, found in later
455 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
456 you intend to run Linux on any of these systems, say Y; otherwise
460 bool "Amiga AGA chipset support"
463 This enables support for the Advanced Graphics Architecture (also
464 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
465 and CD32. If you intend to run Linux on any of these systems, say Y;
469 bool "Amiga FrameMaster II/Rainbow II support"
470 depends on (FB = y) && ZORRO
471 select FB_CFB_FILLRECT
472 select FB_CFB_COPYAREA
473 select FB_CFB_IMAGEBLIT
475 This is the frame buffer device driver for the Amiga FrameMaster
476 card from BSC (exhibited 1992 but not shipped as a CBM product).
479 tristate "Arc Monochrome LCD board support"
481 select FB_SYS_FILLRECT
482 select FB_SYS_COPYAREA
483 select FB_SYS_IMAGEBLIT
486 This enables support for the Arc Monochrome LCD board. The board
487 is based on the KS-108 lcd controller and is typically a matrix
488 of 2*n chips. This driver was tested with a 128x64 panel. This
489 driver supports it for use with x86 SBCs through a 16 bit GPIO
490 interface (8 bit data, 8 bit control). If you anticipate using
491 this driver, say Y or M; otherwise say N. You must specify the
492 GPIO IO address to be used for setting control and data.
495 bool "Atari native chipset support"
496 depends on (FB = y) && ATARI
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
501 This is the frame buffer device driver for the builtin graphics
502 chipset found in Ataris.
505 bool "Open Firmware frame buffer device support"
506 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
512 Say Y if you want support with Open Firmware for your graphics
516 bool "Apple \"control\" display support"
517 depends on (FB = y) && PPC_PMAC && PPC32
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 This driver supports a frame buffer for the graphics adapter in the
524 Power Macintosh 7300 and others.
527 bool "Apple \"platinum\" display support"
528 depends on (FB = y) && PPC_PMAC && PPC32
529 select FB_CFB_FILLRECT
530 select FB_CFB_COPYAREA
531 select FB_CFB_IMAGEBLIT
534 This driver supports a frame buffer for the "platinum" graphics
535 adapter in some Power Macintoshes.
538 bool "Apple \"valkyrie\" display support"
539 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
545 This driver supports a frame buffer for the "valkyrie" graphics
546 adapter in some Power Macintoshes.
549 bool "Chips 65550 display support"
550 depends on (FB = y) && PPC32 && PCI
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
555 This is the frame buffer device driver for the Chips & Technologies
556 65550 graphics chip in PowerBooks.
559 bool "Asiliant (Chips) 69000 display support"
560 depends on (FB = y) && PCI
561 select FB_CFB_FILLRECT
562 select FB_CFB_COPYAREA
563 select FB_CFB_IMAGEBLIT
565 This is the frame buffer device driver for the Asiliant 69030 chipset
568 bool "IMS Twin Turbo display support"
569 depends on (FB = y) && PCI
570 select FB_CFB_IMAGEBLIT
571 select FB_MACMODES if PPC
573 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
574 many Macintosh and compatible computers.
577 tristate "VGA 16-color graphics support"
578 depends on FB && (X86 || PPC)
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
583 select FONT_8x16 if FRAMEBUFFER_CONSOLE
585 This is the frame buffer device driver for VGA 16 color graphic
586 cards. Say Y if you have such a card.
588 To compile this driver as a module, choose M here: the
589 module will be called vga16fb.
591 config FB_BF54X_LQ043
592 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
593 depends on FB && (BF54x) && !BF542
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
598 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
600 config FB_BFIN_T350MCQB
601 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
602 depends on FB && BLACKFIN
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
609 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
610 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
614 tristate "HP STI frame buffer device support"
615 depends on FB && PARISC
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
623 STI refers to the HP "Standard Text Interface" which is a set of
624 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
625 Enabling this option will implement the linux framebuffer device
626 using calls to the STI BIOS routines for initialisation.
628 If you enable this option, you will get a planar framebuffer device
629 /dev/fb which will work on the most common HP graphic cards of the
630 NGLE family, including the artist chips (in the 7xx and Bxxx series),
631 HCRX, HCRX24, CRX, CRX24 and VisEG series.
633 It is safe to enable this option, so you should probably say "Y".
636 bool "Generic Macintosh display support"
637 depends on (FB = y) && MAC
638 select FB_CFB_FILLRECT
639 select FB_CFB_COPYAREA
640 select FB_CFB_IMAGEBLIT
645 depends on (FB = y) && DIO
646 select FB_CFB_IMAGEBLIT
650 tristate "TGA/SFB+ framebuffer support"
651 depends on FB && (ALPHA || TC)
652 select FB_CFB_FILLRECT
653 select FB_CFB_COPYAREA
654 select FB_CFB_IMAGEBLIT
657 This is the frame buffer device driver for generic TGA and SFB+
658 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
659 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
660 TURBOchannel cards, also known as PMAGD-A, -B and -C.
662 Due to hardware limitations ZLX-E2 and E3 cards are not supported
663 for DECstation 5000/200 systems. Additionally due to firmware
664 limitations these cards may cause troubles with booting DECstation
665 5000/240 and /260 systems, but are fully supported under Linux if
666 you manage to get it going. ;-)
668 Say Y if you have one of those.
671 tristate "Userspace VESA VGA graphics support"
672 depends on FB && CONNECTOR
673 select FB_CFB_FILLRECT
674 select FB_CFB_COPYAREA
675 select FB_CFB_IMAGEBLIT
676 select FB_MODE_HELPERS
678 This is the frame buffer driver for generic VBE 2.0 compliant
679 graphic cards. It can also take advantage of VBE 3.0 features,
680 such as refresh rate adjustment.
682 This driver generally provides more features than vesafb but
683 requires a userspace helper application called 'v86d'. See
684 <file:Documentation/fb/uvesafb.txt> for more information.
689 bool "VESA VGA graphics support"
690 depends on (FB = y) && X86
691 select FB_CFB_FILLRECT
692 select FB_CFB_COPYAREA
693 select FB_CFB_IMAGEBLIT
694 select FB_BOOT_VESA_SUPPORT
696 This is the frame buffer device driver for generic VESA 2.0
697 compliant graphic cards. The older VESA 1.2 cards are not supported.
698 You will get a boot time penguin logo at no additional cost. Please
699 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
702 bool "EFI-based 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 EFI frame buffer device driver. If the firmware on
709 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
710 using the EFI framebuffer as your console.
713 tristate "N411 Apollo/Hecuba devkit support"
714 depends on FB && X86 && MMU
715 select FB_SYS_FILLRECT
716 select FB_SYS_COPYAREA
717 select FB_SYS_IMAGEBLIT
719 select FB_DEFERRED_IO
722 This enables support for the Apollo display controller in its
723 Hecuba form using the n411 devkit.
726 tristate "Hercules mono graphics support"
728 select FB_CFB_FILLRECT
729 select FB_CFB_COPYAREA
730 select FB_CFB_IMAGEBLIT
732 Say Y here if you have a Hercules mono graphics card.
734 To compile this driver as a module, choose M here: the
735 module will be called hgafb.
737 As this card technology is 15 years old, most people will answer N
741 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
742 depends on FB_HGA && EXPERIMENTAL
744 This will compile the Hercules mono graphics with
745 acceleration functions.
748 tristate "SGI Visual Workstation framebuffer support"
749 depends on FB && X86_VISWS
750 select FB_CFB_FILLRECT
751 select FB_CFB_COPYAREA
752 select FB_CFB_IMAGEBLIT
754 SGI Visual Workstation support for framebuffer graphics.
757 bool "SGI Graphics Backend frame buffer support"
758 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
759 select FB_CFB_FILLRECT
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
763 This is the frame buffer device driver for SGI Graphics Backend.
764 This chip is used in SGI O2 and Visual Workstation 320/540.
767 int "Video memory size in MB"
771 This is the amount of memory reserved for the framebuffer,
772 which can be any value between 1MB and 8MB.
775 bool "SBUS and UPA framebuffers"
776 depends on (FB = y) && SPARC
778 Say Y if you want support for SBUS or UPA based frame buffer device.
782 depends on (FB = y) && (SPARC && FB_SBUS)
783 select FB_CFB_FILLRECT
784 select FB_CFB_COPYAREA
785 select FB_CFB_IMAGEBLIT
787 This is the frame buffer device driver for the BWtwo frame buffer.
790 bool "CGthree support"
791 depends on (FB = y) && (SPARC && FB_SBUS)
792 select FB_CFB_FILLRECT
793 select FB_CFB_COPYAREA
794 select FB_CFB_IMAGEBLIT
796 This is the frame buffer device driver for the CGthree frame buffer.
799 bool "CGsix (GX,TurboGX) support"
800 depends on (FB = y) && (SPARC && FB_SBUS)
801 select FB_CFB_COPYAREA
802 select FB_CFB_IMAGEBLIT
804 This is the frame buffer device driver for the CGsix (GX, TurboGX)
808 bool "Creator/Creator3D/Elite3D support"
809 depends on FB_SBUS && SPARC64
810 select FB_CFB_COPYAREA
811 select FB_CFB_IMAGEBLIT
813 This is the frame buffer device driver for the Creator, Creator3D,
814 and Elite3D graphics boards.
817 bool "TCX (SS4/SS5 only) 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 TCX 24/8bit frame
827 bool "CGfourteen (SX) 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 CGfourteen frame
834 buffer on Desktop SPARCsystems with the SX graphics option.
837 bool "P9100 (Sparcbook 3 only) support"
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for the P9100 card
844 supported on Sparcbook 3 machines.
847 bool "Leo (ZX) support"
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
853 This is the frame buffer device driver for the SBUS-based Sun ZX
854 (leo) frame buffer cards.
857 bool "IGA 168x display support"
858 depends on (FB = y) && SPARC32
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 This is the framebuffer device for the INTERGRAPHICS 1680 and
864 successor frame buffer cards.
867 bool "Sun XVR-500 3DLABS Wildcat support"
868 depends on (FB = y) && PCI && SPARC64
869 select FB_CFB_FILLRECT
870 select FB_CFB_COPYAREA
871 select FB_CFB_IMAGEBLIT
873 This is the framebuffer device for the Sun XVR-500 and similar
874 graphics cards based upon the 3DLABS Wildcat chipset. The driver
875 only works on sparc64 systems where the system firmware has
876 mostly initialized the card already. It is treated as a
877 completely dumb framebuffer device.
880 bool "Sun XVR-2500 3DLABS Wildcat support"
881 depends on (FB = y) && PCI && SPARC64
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the framebuffer device for the Sun XVR-2500 and similar
887 graphics cards based upon the 3DLABS Wildcat chipset. The driver
888 only works on sparc64 systems where the system firmware has
889 mostly initialized the card already. It is treated as a
890 completely dumb framebuffer device.
893 tristate "NEC PowerVR 2 display support"
894 depends on FB && SH_DREAMCAST
895 select FB_CFB_FILLRECT
896 select FB_CFB_COPYAREA
897 select FB_CFB_IMAGEBLIT
899 Say Y here if you have a PowerVR 2 card in your box. If you plan to
900 run linux on your Dreamcast, you will have to say Y here.
901 This driver may or may not work on other PowerVR 2 cards, but is
902 totally untested. Use at your own risk. If unsure, say N.
904 To compile this driver as a module, choose M here: the
905 module will be called pvr2fb.
907 You can pass several parameters to the driver at boot time or at
908 module load time. The parameters look like "video=pvr2:XXX", where
909 the meaning of XXX can be found at the end of the main source file
910 (<file:drivers/video/pvr2fb.c>). Please see the file
911 <file:Documentation/fb/pvr2fb.txt>.
914 bool "Epson 1355 framebuffer support"
915 depends on (FB = y) && ARCH_CEIVA
916 select FB_CFB_FILLRECT
917 select FB_CFB_COPYAREA
918 select FB_CFB_IMAGEBLIT
920 Build in support for the SED1355 Epson Research Embedded RAMDAC
921 LCD/CRT Controller (since redesignated as the S1D13505) as a
922 framebuffer. Product specs at
923 <http://www.erd.epson.com/vdc/html/products.htm>.
926 tristate "Epson S1D13XXX framebuffer support"
928 select FB_CFB_FILLRECT
929 select FB_CFB_COPYAREA
930 select FB_CFB_IMAGEBLIT
932 Support for S1D13XXX framebuffer device family (currently only
933 working with S1D13806). Product specs at
934 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
937 tristate "AT91/AT32 LCD Controller support"
938 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
939 select FB_CFB_FILLRECT
940 select FB_CFB_COPYAREA
941 select FB_CFB_IMAGEBLIT
943 This enables support for the AT91/AT32 LCD Controller.
946 bool "Frame Buffer in internal SRAM"
947 depends on FB_ATMEL && ARCH_AT91SAM9261
949 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
950 to let frame buffer in external SDRAM.
953 bool "Use a STN display with AT91/AT32 LCD Controller"
954 depends on FB_ATMEL && MACH_AT91SAM9261EK
957 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
958 Controller. Say N if you want to connect a TFT.
963 tristate "nVidia Framebuffer Support"
965 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
966 select FB_MODE_HELPERS
967 select FB_CFB_FILLRECT
968 select FB_CFB_COPYAREA
969 select FB_CFB_IMAGEBLIT
973 This driver supports graphics boards with the nVidia chips, TNT
974 and newer. For very old chipsets, such as the RIVA128, then use
976 Say Y if you have such a graphics board.
978 To compile this driver as a module, choose M here: the
979 module will be called nvidiafb.
982 bool "Enable DDC Support"
986 This enables I2C support for nVidia Chipsets. This is used
987 only for getting EDID information from the attached display
988 allowing for robust video mode handling and switching.
990 Because fbdev-2.6 requires that drivers must be able to
991 independently validate video mode parameters, you should say Y
994 config FB_NVIDIA_DEBUG
995 bool "Lots of debug output"
999 Say Y here if you want the nVidia driver to output all sorts
1000 of debugging information to provide to the maintainer when
1001 something goes wrong.
1003 config FB_NVIDIA_BACKLIGHT
1004 bool "Support for backlight control"
1005 depends on FB_NVIDIA
1008 Say Y here if you want to control the backlight of your display.
1011 tristate "nVidia Riva support"
1012 depends on FB && PCI
1013 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1014 select FB_MODE_HELPERS
1015 select FB_CFB_FILLRECT
1016 select FB_CFB_COPYAREA
1017 select FB_CFB_IMAGEBLIT
1021 This driver supports graphics boards with the nVidia Riva/Geforce
1023 Say Y if you have such a graphics board.
1025 To compile this driver as a module, choose M here: the
1026 module will be called rivafb.
1029 bool "Enable DDC Support"
1033 This enables I2C support for nVidia Chipsets. This is used
1034 only for getting EDID information from the attached display
1035 allowing for robust video mode handling and switching.
1037 Because fbdev-2.6 requires that drivers must be able to
1038 independently validate video mode parameters, you should say Y
1041 config FB_RIVA_DEBUG
1042 bool "Lots of debug output"
1046 Say Y here if you want the Riva driver to output all sorts
1047 of debugging information to provide to the maintainer when
1048 something goes wrong.
1050 config FB_RIVA_BACKLIGHT
1051 bool "Support for backlight control"
1055 Say Y here if you want to control the backlight of your display.
1058 tristate "Intel 810/815 support (EXPERIMENTAL)"
1059 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
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 EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL
1123 select FB_MODE_HELPERS
1124 select FB_CFB_FILLRECT
1125 select FB_CFB_COPYAREA
1126 select FB_CFB_IMAGEBLIT
1127 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1129 This driver supports the on-board graphics built in to the Intel
1130 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1131 Say Y if you have and plan to use such a board.
1133 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1135 To compile this driver as a module, choose M here: the
1136 module will be called intelfb.
1138 For more information, please read <file:Documentation/fb/intelfb.txt>
1140 config FB_INTEL_DEBUG
1141 bool "Intel driver Debug Messages"
1144 Say Y here if you want the Intel driver to output all sorts
1145 of debugging information to provide to the maintainer when
1146 something goes wrong.
1149 bool "DDC/I2C for Intel framebuffer support"
1154 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1157 tristate "Matrox acceleration"
1158 depends on FB && PCI
1159 select FB_CFB_FILLRECT
1160 select FB_CFB_COPYAREA
1161 select FB_CFB_IMAGEBLIT
1162 select FB_TILEBLITTING
1163 select FB_MACMODES if PPC_PMAC
1165 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1166 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1167 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1168 Matrox G400, G450 or G550 card in your box.
1170 To compile this driver as a module, choose M here: the
1171 module will be called matroxfb.
1173 You can pass several parameters to the driver at boot time or at
1174 module load time. The parameters look like "video=matrox:XXX", and
1175 are described in <file:Documentation/fb/matroxfb.txt>.
1177 config FB_MATROX_MILLENIUM
1178 bool "Millennium I/II support"
1179 depends on FB_MATROX
1181 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1182 video card. If you select "Advanced lowlevel driver options" below,
1183 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1184 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1185 also use font widths different from 8.
1187 config FB_MATROX_MYSTIQUE
1188 bool "Mystique support"
1189 depends on FB_MATROX
1191 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1192 video card. If you select "Advanced lowlevel driver options" below,
1193 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1194 packed pixel and 32 bpp packed pixel. You can also use font widths
1198 bool "G100/G200/G400/G450/G550 support"
1199 depends on FB_MATROX
1201 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1202 video card. If you select "Advanced lowlevel driver options", you
1203 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1204 pixel and 32 bpp packed pixel. You can also use font widths
1207 If you need support for G400 secondary head, you must say Y to
1208 "Matrox I2C support" and "G400 second head support" right below.
1209 G450/G550 secondary head and digital output are supported without
1212 The driver starts in monitor mode. You must use the matroxset tool
1213 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1214 swap primary and secondary head outputs, or to change output mode.
1215 Secondary head driver always start in 640x480 resolution and you
1216 must use fbset to change it.
1218 Do not forget that second head supports only 16 and 32 bpp
1219 packed pixels, so it is a good idea to compile them into the kernel
1220 too. You can use only some font widths, as the driver uses generic
1221 painting procedures (the secondary head does not use acceleration
1224 G450/G550 hardware can display TV picture only from secondary CRTC,
1225 and it performs no scaling, so picture must have 525 or 625 lines.
1227 config FB_MATROX_I2C
1228 tristate "Matrox I2C support"
1229 depends on FB_MATROX
1232 This drivers creates I2C buses which are needed for accessing the
1233 DDC (I2C) bus present on all Matroxes, an I2C bus which
1234 interconnects Matrox optional devices, like MGA-TVO on G200 and
1235 G400, and the secondary head DDC bus, present on G400 only.
1237 You can say Y or M here if you want to experiment with monitor
1238 detection code. You must say Y or M here if you want to use either
1239 second head of G400 or MGA-TVO on G200 or G400.
1241 If you compile it as module, it will create a module named
1244 config FB_MATROX_MAVEN
1245 tristate "G400 second head support"
1246 depends on FB_MATROX_G && FB_MATROX_I2C
1248 WARNING !!! This support does not work with G450 !!!
1250 Say Y or M here if you want to use a secondary head (meaning two
1251 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1252 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1253 secondary head output is blanked while you are in X. With XFree
1254 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1255 the fbdev driver on first head and the fbdev driver on second head.
1257 If you compile it as module, two modules are created,
1258 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1259 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1260 also load i2c-matroxfb to get it to run.
1262 The driver starts in monitor mode and you must use the matroxset
1264 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1265 PAL or NTSC or to swap primary and secondary head outputs.
1266 Secondary head driver also always start in 640x480 resolution, you
1267 must use fbset to change it.
1269 Also do not forget that second head supports only 16 and 32 bpp
1270 packed pixels, so it is a good idea to compile them into the kernel
1271 too. You can use only some font widths, as the driver uses generic
1272 painting procedures (the secondary head does not use acceleration
1275 config FB_MATROX_MULTIHEAD
1276 bool "Multihead support"
1277 depends on FB_MATROX
1279 Say Y here if you have more than one (supported) Matrox device in
1280 your computer and you want to use all of them for different monitors
1281 ("multihead"). If you have only one device, you should say N because
1282 the driver compiled with Y is larger and a bit slower, especially on
1285 If you said M to "Matrox unified accelerated driver" and N here, you
1286 will still be able to use several Matrox devices simultaneously:
1287 insert several instances of the module matroxfb into the kernel
1288 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1289 for the different Matrox devices. This method is slightly faster but
1290 uses 40 KB of kernel memory per Matrox card.
1292 There is no need for enabling 'Matrox multihead support' if you have
1293 only one Matrox card in the box.
1296 tristate "ATI Radeon display support"
1297 depends on FB && PCI
1298 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1299 select FB_MODE_HELPERS
1300 select FB_CFB_FILLRECT
1301 select FB_CFB_COPYAREA
1302 select FB_CFB_IMAGEBLIT
1303 select FB_MACMODES if PPC_OF
1305 Choose this option if you want to use an ATI Radeon graphics card as
1306 a framebuffer device. There are both PCI and AGP versions. You
1307 don't need to choose this to run the Radeon in plain VGA mode.
1309 There is a product page at
1310 http://apps.ati.com/ATIcompare/
1312 config FB_RADEON_I2C
1313 bool "DDC/I2C for ATI Radeon support"
1314 depends on FB_RADEON
1318 Say Y here if you want DDC/I2C support for your Radeon board.
1320 config FB_RADEON_BACKLIGHT
1321 bool "Support for backlight control"
1322 depends on FB_RADEON
1325 Say Y here if you want to control the backlight of your display.
1327 config FB_RADEON_DEBUG
1328 bool "Lots of debug output from Radeon driver"
1329 depends on FB_RADEON
1332 Say Y here if you want the Radeon driver to output all sorts
1333 of debugging information to provide to the maintainer when
1334 something goes wrong.
1337 tristate "ATI Rage128 display support"
1338 depends on FB && PCI
1339 select FB_CFB_FILLRECT
1340 select FB_CFB_COPYAREA
1341 select FB_CFB_IMAGEBLIT
1342 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1343 select FB_MACMODES if PPC_PMAC
1345 This driver supports graphics boards with the ATI Rage128 chips.
1346 Say Y if you have such a graphics board and read
1347 <file:Documentation/fb/aty128fb.txt>.
1349 To compile this driver as a module, choose M here: the
1350 module will be called aty128fb.
1352 config FB_ATY128_BACKLIGHT
1353 bool "Support for backlight control"
1354 depends on FB_ATY128
1357 Say Y here if you want to control the backlight of your display.
1360 tristate "ATI Mach64 display support" if PCI || ATARI
1361 depends on FB && !SPARC32
1362 select FB_CFB_FILLRECT
1363 select FB_CFB_COPYAREA
1364 select FB_CFB_IMAGEBLIT
1365 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1366 select FB_MACMODES if PPC
1368 This driver supports graphics boards with the ATI Mach64 chips.
1369 Say Y if you have such a graphics board.
1371 To compile this driver as a module, choose M here: the
1372 module will be called atyfb.
1375 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1376 depends on PCI && FB_ATY
1377 default y if SPARC64 && PCI
1379 Say Y here to support use of ATI's 64-bit Rage boards (or other
1380 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1381 framebuffer device. The ATI product support page for these boards
1382 is at <http://support.ati.com/products/pc/mach64/>.
1384 config FB_ATY_GENERIC_LCD
1385 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1386 depends on FB_ATY_CT
1388 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1389 Rage XC, or Rage XL chipset.
1392 bool "Mach64 GX support" if PCI
1396 Say Y here to support use of the ATI Mach64 Graphics Expression
1397 board (or other boards based on the Mach64 GX chipset) as a
1398 framebuffer device. The ATI product support page for these boards
1400 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1402 config FB_ATY_BACKLIGHT
1403 bool "Support for backlight control"
1407 Say Y here if you want to control the backlight of your display.
1410 tristate "S3 Trio/Virge support"
1411 depends on FB && PCI
1412 select FB_CFB_FILLRECT
1413 select FB_CFB_COPYAREA
1414 select FB_CFB_IMAGEBLIT
1415 select FB_TILEBLITTING
1418 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1420 Driver for graphics boards with S3 Trio / S3 Virge chip.
1423 tristate "S3 Savage support"
1424 depends on FB && PCI && EXPERIMENTAL
1425 select FB_MODE_HELPERS
1426 select FB_CFB_FILLRECT
1427 select FB_CFB_COPYAREA
1428 select FB_CFB_IMAGEBLIT
1431 This driver supports notebooks and computers with S3 Savage PCI/AGP
1434 Say Y if you have such a graphics card.
1436 To compile this driver as a module, choose M here; the module
1437 will be called savagefb.
1439 config FB_SAVAGE_I2C
1440 bool "Enable DDC2 Support"
1441 depends on FB_SAVAGE
1444 This enables I2C support for S3 Savage Chipsets. This is used
1445 only for getting EDID information from the attached display
1446 allowing for robust video mode handling and switching.
1448 Because fbdev-2.6 requires that drivers must be able to
1449 independently validate video mode parameters, you should say Y
1452 config FB_SAVAGE_ACCEL
1453 bool "Enable Console Acceleration"
1454 depends on FB_SAVAGE
1457 This option will compile in console acceleration support. If
1458 the resulting framebuffer console has bothersome glitches, then
1462 tristate "SiS/XGI display support"
1463 depends on FB && PCI
1464 select FB_CFB_FILLRECT
1465 select FB_CFB_COPYAREA
1466 select FB_CFB_IMAGEBLIT
1467 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1469 This is the frame buffer device driver for the SiS 300, 315, 330
1470 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1471 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1473 To compile this driver as a module, choose M here; the module
1474 will be called sisfb.
1477 bool "SiS 300 series support"
1480 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1483 bool "SiS 315/330/340 series and XGI support"
1486 Say Y here to support use of the SiS 315, 330 and 340 series
1487 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1488 as XGI V3XT, V5, V8 and Z7.
1491 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1492 depends on FB && PCI
1493 select FB_CFB_FILLRECT
1494 select FB_CFB_COPYAREA
1495 select FB_CFB_IMAGEBLIT
1496 select FB_SOFT_CURSOR
1500 This is the frame buffer device driver for Graphics chips of VIA
1501 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1502 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1504 Say Y if you have a VIA UniChrome graphics board.
1506 To compile this driver as a module, choose M here: the
1507 module will be called viafb.
1509 tristate "NeoMagic display support"
1510 depends on FB && PCI
1511 select FB_MODE_HELPERS
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1517 This driver supports notebooks with NeoMagic PCI chips.
1518 Say Y if you have such a graphics card.
1520 To compile this driver as a module, choose M here: the
1521 module will be called neofb.
1524 tristate "IMG Kyro support"
1525 depends on FB && PCI
1526 select FB_CFB_FILLRECT
1527 select FB_CFB_COPYAREA
1528 select FB_CFB_IMAGEBLIT
1530 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1533 To compile this driver as a module, choose M here: the
1534 module will be called kyrofb.
1537 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1538 depends on FB && PCI
1539 select FB_CFB_IMAGEBLIT
1540 select FB_CFB_FILLRECT
1541 select FB_CFB_COPYAREA
1542 select FB_MODE_HELPERS
1544 This driver supports graphics boards with the 3Dfx Banshee,
1545 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1546 such a graphics board.
1548 To compile this driver as a module, choose M here: the
1549 module will be called tdfxfb.
1551 config FB_3DFX_ACCEL
1552 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1553 depends on FB_3DFX && EXPERIMENTAL
1555 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1556 device driver with acceleration functions.
1559 bool "Enable DDC/I2C support"
1560 depends on FB_3DFX && EXPERIMENTAL
1564 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1567 tristate "3Dfx Voodoo Graphics (sst1) support"
1568 depends on FB && PCI
1569 select FB_CFB_FILLRECT
1570 select FB_CFB_COPYAREA
1571 select FB_CFB_IMAGEBLIT
1573 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1574 Voodoo2 (cvg) based graphics card.
1576 To compile this driver as a module, choose M here: the
1577 module will be called sstfb.
1579 WARNING: Do not use any application that uses the 3D engine
1580 (namely glide) while using this driver.
1581 Please read the <file:Documentation/fb/sstfb.txt> for supported
1582 options and other important info support.
1585 tristate "VIA VT8623 support"
1586 depends on FB && PCI
1587 select FB_CFB_FILLRECT
1588 select FB_CFB_COPYAREA
1589 select FB_CFB_IMAGEBLIT
1590 select FB_TILEBLITTING
1593 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1595 Driver for CastleRock integrated graphics core in the
1596 VIA VT8623 [Apollo CLE266] chipset.
1599 tristate "Trident/CyberXXX/CyberBlade support"
1600 depends on FB && PCI
1601 select FB_CFB_FILLRECT
1602 select FB_CFB_COPYAREA
1603 select FB_CFB_IMAGEBLIT
1605 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1606 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1608 There are also integrated versions of these chips called CyberXXXX,
1609 CyberImage or CyberBlade. These chips are mostly found in laptops
1610 but also on some motherboards including early VIA EPIA motherboards.
1611 For more information, read <file:Documentation/fb/tridentfb.txt>
1613 Say Y if you have such a graphics board.
1615 To compile this driver as a module, choose M here: the
1616 module will be called tridentfb.
1619 tristate "ARK 2000PV support"
1620 depends on FB && PCI
1621 select FB_CFB_FILLRECT
1622 select FB_CFB_COPYAREA
1623 select FB_CFB_IMAGEBLIT
1624 select FB_TILEBLITTING
1627 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1629 Driver for PCI graphics boards with ARK 2000PV chip
1630 and ICS 5342 RAMDAC.
1633 tristate "Permedia3 support (EXPERIMENTAL)"
1634 depends on FB && PCI && EXPERIMENTAL
1635 select FB_CFB_FILLRECT
1636 select FB_CFB_COPYAREA
1637 select FB_CFB_IMAGEBLIT
1639 This is the frame buffer device driver for the 3DLabs Permedia3
1640 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1641 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1642 and maybe other boards.
1645 tristate "Fujitsu carmine frame buffer support"
1646 depends on FB && PCI
1647 select FB_CFB_FILLRECT
1648 select FB_CFB_COPYAREA
1649 select FB_CFB_IMAGEBLIT
1651 This is the frame buffer device driver for the Fujitsu Carmine chip.
1652 The driver provides two independent frame buffer devices.
1655 depends on FB_CARMINE
1656 prompt "DRAM timing"
1657 default FB_CARMINE_DRAM_EVAL
1659 config FB_CARMINE_DRAM_EVAL
1660 bool "Eval board timings"
1662 Use timings which work on the eval card.
1664 config CARMINE_DRAM_CUSTOM
1665 bool "Custom board timings"
1667 Use custom board timings.
1671 bool "Au1100 LCD Driver"
1672 depends on (FB = y) && MIPS && SOC_AU1100
1673 select FB_CFB_FILLRECT
1674 select FB_CFB_COPYAREA
1675 select FB_CFB_IMAGEBLIT
1677 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1678 various panels and CRTs by passing in kernel cmd line option
1679 au1100fb:panel=<name>.
1682 bool "Au1200 LCD Driver"
1683 depends on (FB = y) && MIPS && SOC_AU1200
1684 select FB_CFB_FILLRECT
1685 select FB_CFB_COPYAREA
1686 select FB_CFB_IMAGEBLIT
1688 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1689 various panels and CRTs by passing in kernel cmd line option
1690 au1200fb:panel=<name>.
1692 source "drivers/video/geode/Kconfig"
1695 tristate "HD64461 Frame Buffer support"
1696 depends on FB && HD64461
1697 select FB_CFB_FILLRECT
1698 select FB_CFB_COPYAREA
1699 select FB_CFB_IMAGEBLIT
1701 This is the frame buffer device driver for the Hitachi HD64461 LCD
1705 bool "PMAG-AA TURBOchannel framebuffer support"
1706 depends on (FB = y) && TC
1707 select FB_CFB_FILLRECT
1708 select FB_CFB_COPYAREA
1709 select FB_CFB_IMAGEBLIT
1711 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1712 used mainly in the MIPS-based DECstation series.
1715 tristate "PMAG-BA TURBOchannel framebuffer support"
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1721 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1722 used mainly in the MIPS-based DECstation series.
1725 tristate "PMAGB-B TURBOchannel framebuffer support"
1727 select FB_CFB_FILLRECT
1728 select FB_CFB_COPYAREA
1729 select FB_CFB_IMAGEBLIT
1731 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1732 in the MIPS-based DECstation series. The card is currently only
1733 supported in 1280x1024x8 mode.
1736 bool "Maxine (Personal DECstation) onboard framebuffer support"
1737 depends on (FB = y) && MACH_DECSTATION
1738 select FB_CFB_FILLRECT
1739 select FB_CFB_COPYAREA
1740 select FB_CFB_IMAGEBLIT
1742 Support for the onboard framebuffer (1024x768x8) in the Personal
1743 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1747 bool "G364 frame buffer support"
1748 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1749 select FB_CFB_FILLRECT
1750 select FB_CFB_COPYAREA
1751 select FB_CFB_IMAGEBLIT
1753 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1754 Olivetti M700-10 systems.
1757 bool "Motorola 68328 native frame buffer support"
1758 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1759 select FB_CFB_FILLRECT
1760 select FB_CFB_COPYAREA
1761 select FB_CFB_IMAGEBLIT
1763 Say Y here if you want to support the built-in frame buffer of
1764 the Motorola 68328 CPU family.
1767 tristate "PXA168/910 LCD framebuffer support"
1768 depends on FB && (CPU_PXA168 || CPU_PXA910)
1769 select FB_CFB_FILLRECT
1770 select FB_CFB_COPYAREA
1771 select FB_CFB_IMAGEBLIT
1773 Frame buffer driver for the built-in LCD controller in the Marvell
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_OVERLAY
1794 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1796 depends on FB_PXA && (PXA27x || PXA3xx)
1798 config FB_PXA_SMARTPANEL
1799 bool "PXA Smartpanel LCD support"
1803 config FB_PXA_PARAMETERS
1804 bool "PXA LCD command line parameters"
1808 Enable the use of kernel command line or module parameters
1809 to configure the physical properties of the LCD panel when
1810 using the PXA LCD driver.
1812 This option allows you to override the panel parameters
1813 supplied by the platform in order to support multiple
1814 different models of flatpanel. If you will only be using a
1815 single model of flatpanel then you can safely leave this
1818 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1821 tristate "2700G LCD framebuffer support"
1822 depends on FB && ARCH_PXA
1823 select FB_CFB_FILLRECT
1824 select FB_CFB_COPYAREA
1825 select FB_CFB_IMAGEBLIT
1827 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1831 bool "Enable debugging info via debugfs"
1832 depends on FB_MBX && DEBUG_FS
1835 Enable this if you want debugging information using the debug
1836 filesystem (debugfs)
1841 tristate "Freescale DIU framebuffer support"
1842 depends on FB && FSL_SOC
1843 select FB_CFB_FILLRECT
1844 select FB_CFB_COPYAREA
1845 select FB_CFB_IMAGEBLIT
1846 select PPC_LIB_RHEAP
1848 Framebuffer driver for the Freescale SoC DIU
1851 tristate "W100 frame buffer support"
1852 depends on FB && ARCH_PXA
1853 select FB_CFB_FILLRECT
1854 select FB_CFB_COPYAREA
1855 select FB_CFB_IMAGEBLIT
1857 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1858 It can also drive the w3220 chip found on iPAQ hx4700.
1860 This driver is also available as a module ( = code which can be
1861 inserted and removed from the running kernel whenever you want). The
1862 module will be called w100fb. If you want to compile it as a module,
1863 say M here and read <file:Documentation/kbuild/modules.txt>.
1867 config FB_SH_MOBILE_LCDC
1868 tristate "SuperH Mobile LCDC framebuffer support"
1869 depends on FB && SUPERH
1870 select FB_SYS_FILLRECT
1871 select FB_SYS_COPYAREA
1872 select FB_SYS_IMAGEBLIT
1874 select FB_DEFERRED_IO
1876 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1879 tristate "Toshiba Mobile IO FrameBuffer support"
1880 depends on FB && MFD_CORE
1881 select FB_CFB_FILLRECT
1882 select FB_CFB_COPYAREA
1883 select FB_CFB_IMAGEBLIT
1885 Frame buffer driver for the Toshiba Mobile IO integrated as found
1886 on the Sharp SL-6000 series
1888 This driver is also available as a module ( = code which can be
1889 inserted and removed from the running kernel whenever you want). The
1890 module will be called tmiofb. If you want to compile it as a module,
1891 say M here and read <file:Documentation/kbuild/modules.txt>.
1895 config FB_TMIO_ACCELL
1896 bool "tmiofb acceleration"
1901 tristate "Samsung S3C framebuffer support"
1902 depends on FB && ARCH_S3C64XX
1903 select FB_CFB_FILLRECT
1904 select FB_CFB_COPYAREA
1905 select FB_CFB_IMAGEBLIT
1907 Frame buffer driver for the built-in FB controller in the Samsung
1908 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1909 and the S3C64XX series such as the S3C6400 and S3C6410.
1911 These chips all have the same basic framebuffer design with the
1912 actual capabilities depending on the chip. For instance the S3C6400
1913 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1914 currently only have two.
1916 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1918 config FB_S3C_DEBUG_REGWRITE
1919 bool "Debug register writes"
1922 Show all register writes via printk(KERN_DEBUG)
1925 tristate "S3C2410 LCD framebuffer support"
1926 depends on FB && ARCH_S3C2410
1927 select FB_CFB_FILLRECT
1928 select FB_CFB_COPYAREA
1929 select FB_CFB_IMAGEBLIT
1931 Frame buffer driver for the built-in LCD controller in the Samsung
1934 This driver is also available as a module ( = code which can be
1935 inserted and removed from the running kernel whenever you want). The
1936 module will be called s3c2410fb. If you want to compile it as a module,
1937 say M here and read <file:Documentation/kbuild/modules.txt>.
1940 config FB_S3C2410_DEBUG
1941 bool "S3C2410 lcd debug messages"
1942 depends on FB_S3C2410
1944 Turn on debugging messages. Note that you can set/unset at run time
1948 tristate "Silicon Motion SM501 framebuffer support"
1949 depends on FB && MFD_SM501
1950 select FB_CFB_FILLRECT
1951 select FB_CFB_COPYAREA
1952 select FB_CFB_IMAGEBLIT
1954 Frame buffer driver for the CRT and LCD controllers in the Silicon
1957 This driver is also available as a module ( = code which can be
1958 inserted and removed from the running kernel whenever you want). The
1959 module will be called sm501fb. If you want to compile it as a module,
1960 say M here and read <file:Documentation/kbuild/modules.txt>.
1965 config FB_PNX4008_DUM
1966 tristate "Display Update Module support on Philips PNX4008 board"
1967 depends on FB && ARCH_PNX4008
1969 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1971 config FB_PNX4008_DUM_RGB
1972 tristate "RGB Framebuffer support on Philips PNX4008 board"
1973 depends on FB_PNX4008_DUM
1974 select FB_CFB_FILLRECT
1975 select FB_CFB_COPYAREA
1976 select FB_CFB_IMAGEBLIT
1978 Say Y here to enable support for PNX4008 RGB Framebuffer
1980 config FB_IBM_GXT4500
1981 tristate "Framebuffer support for IBM GXT4500P adaptor"
1982 depends on FB && PPC
1983 select FB_CFB_FILLRECT
1984 select FB_CFB_COPYAREA
1985 select FB_CFB_IMAGEBLIT
1987 Say Y here to enable support for the IBM GXT4500P display
1988 adaptor, found on some IBM System P (pSeries) machines.
1991 tristate "PS3 GPU framebuffer driver"
1992 depends on FB && PS3_PS3AV
1993 select FB_SYS_FILLRECT
1994 select FB_SYS_COPYAREA
1995 select FB_SYS_IMAGEBLIT
1997 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1999 Include support for the virtual frame buffer in the PS3 platform.
2001 config FB_PS3_DEFAULT_SIZE_M
2002 int "PS3 default frame buffer size (in MiB)"
2006 This is the default size (in MiB) of the virtual frame buffer in
2008 The default value can be overridden on the kernel command line
2009 using the "ps3fb" option (e.g. "ps3fb=9M");
2012 tristate "Xilinx frame buffer support"
2013 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2014 select FB_CFB_FILLRECT
2015 select FB_CFB_COPYAREA
2016 select FB_CFB_IMAGEBLIT
2018 Include support for the Xilinx ML300/ML403 reference design
2019 framebuffer. ML300 carries a 640*480 LCD display on the board,
2020 ML403 uses a standard DB15 VGA connector.
2023 tristate "Cobalt server LCD frame buffer support"
2024 depends on FB && MIPS_COBALT
2027 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2028 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2029 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2030 select FB_CFB_FILLRECT
2031 select FB_CFB_COPYAREA
2032 select FB_CFB_IMAGEBLIT
2034 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2035 (D)STN/TFT LCD Controller.
2036 Supports display resolutions up to 1024x1024 pixel, grayscale and
2037 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2038 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2039 panels <= 320 pixel horizontal resolution.
2042 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2044 select FB_SYS_FILLRECT
2045 select FB_SYS_COPYAREA
2046 select FB_SYS_IMAGEBLIT
2049 This is a `virtual' frame buffer device. It operates on a chunk of
2050 unswappable kernel memory instead of on the memory of a graphics
2051 board. This means you cannot see any output sent to this frame
2052 buffer device, while it does consume precious memory. The main use
2053 of this frame buffer device is testing and debugging the frame
2054 buffer subsystem. Do NOT enable it for normal systems! To protect
2055 the innocent, it has to be enabled explicitly at boot time using the
2056 kernel option `video=vfb:'.
2058 To compile this driver as a module, choose M here: the
2059 module will be called vfb. In order to load it, you must use
2060 the vfb_enable=1 option.
2064 config XEN_FBDEV_FRONTEND
2065 tristate "Xen virtual frame buffer support"
2066 depends on FB && XEN
2067 select FB_SYS_FILLRECT
2068 select FB_SYS_COPYAREA
2069 select FB_SYS_IMAGEBLIT
2071 select FB_DEFERRED_IO
2074 This driver implements the front-end of the Xen virtual
2075 frame buffer driver. It communicates with a back-end
2079 tristate "E-Ink Metronome/8track controller support"
2081 select FB_SYS_FILLRECT
2082 select FB_SYS_COPYAREA
2083 select FB_SYS_IMAGEBLIT
2085 select FB_DEFERRED_IO
2087 This driver implements support for the E-Ink Metronome
2088 controller. The pre-release name for this device was 8track
2089 and could also have been called by some vendors as PVI-nnnn.
2092 tristate "Fujitsu MB862xx GDC support"
2094 select FB_CFB_FILLRECT
2095 select FB_CFB_COPYAREA
2096 select FB_CFB_IMAGEBLIT
2098 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2100 config FB_MB862XX_PCI_GDC
2101 bool "Carmine/Coral-P(A) GDC"
2102 depends on PCI && FB_MB862XX
2104 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2105 PCI graphics controller devices.
2107 config FB_MB862XX_LIME
2109 depends on FB_MB862XX
2110 depends on OF && !FB_MB862XX_PCI_GDC
2112 select FB_FOREIGN_ENDIAN
2113 select FB_LITTLE_ENDIAN
2115 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2117 config FB_PRE_INIT_FB
2118 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2119 depends on FB_MB862XX_LIME
2121 Select this option if display contents should be inherited as set by
2125 tristate "MX3 Framebuffer support"
2126 depends on FB && MX3_IPU
2127 select FB_CFB_FILLRECT
2128 select FB_CFB_COPYAREA
2129 select FB_CFB_IMAGEBLIT
2132 This is a framebuffer device for the i.MX31 LCD Controller. So
2133 far only synchronous displays are supported. If you plan to use
2134 an LCD display with your i.MX31 system, say Y here.
2136 config FB_BROADSHEET
2137 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2139 select FB_SYS_FILLRECT
2140 select FB_SYS_COPYAREA
2141 select FB_SYS_IMAGEBLIT
2143 select FB_DEFERRED_IO
2145 This driver implements support for the E-Ink Broadsheet
2146 controller. The release name for this device was Epson S1D13521
2147 and could also have been called by other names when coupled with
2150 source "drivers/video/omap/Kconfig"
2152 source "drivers/video/backlight/Kconfig"
2153 source "drivers/video/display/Kconfig"
2156 source "drivers/video/console/Kconfig"
2159 if FB || SGI_NEWPORT_CONSOLE
2160 source "drivers/video/logo/Kconfig"