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_IMX || 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
621 STI refers to the HP "Standard Text Interface" which is a set of
622 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
623 Enabling this option will implement the linux framebuffer device
624 using calls to the STI BIOS routines for initialisation.
626 If you enable this option, you will get a planar framebuffer device
627 /dev/fb which will work on the most common HP graphic cards of the
628 NGLE family, including the artist chips (in the 7xx and Bxxx series),
629 HCRX, HCRX24, CRX, CRX24 and VisEG series.
631 It is safe to enable this option, so you should probably say "Y".
634 bool "Generic Macintosh display support"
635 depends on (FB = y) && MAC
636 select FB_CFB_FILLRECT
637 select FB_CFB_COPYAREA
638 select FB_CFB_IMAGEBLIT
643 depends on (FB = y) && DIO
644 select FB_CFB_IMAGEBLIT
648 tristate "TGA/SFB+ framebuffer support"
649 depends on FB && (ALPHA || TC)
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
655 This is the frame buffer device driver for generic TGA and SFB+
656 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
657 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
658 TURBOchannel cards, also known as PMAGD-A, -B and -C.
660 Due to hardware limitations ZLX-E2 and E3 cards are not supported
661 for DECstation 5000/200 systems. Additionally due to firmware
662 limitations these cards may cause troubles with booting DECstation
663 5000/240 and /260 systems, but are fully supported under Linux if
664 you manage to get it going. ;-)
666 Say Y if you have one of those.
669 tristate "Userspace VESA VGA graphics support"
670 depends on FB && CONNECTOR
671 select FB_CFB_FILLRECT
672 select FB_CFB_COPYAREA
673 select FB_CFB_IMAGEBLIT
674 select FB_MODE_HELPERS
676 This is the frame buffer driver for generic VBE 2.0 compliant
677 graphic cards. It can also take advantage of VBE 3.0 features,
678 such as refresh rate adjustment.
680 This driver generally provides more features than vesafb but
681 requires a userspace helper application called 'v86d'. See
682 <file:Documentation/fb/uvesafb.txt> for more information.
687 bool "VESA VGA graphics support"
688 depends on (FB = y) && X86
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
692 select FB_BOOT_VESA_SUPPORT
694 This is the frame buffer device driver for generic VESA 2.0
695 compliant graphic cards. The older VESA 1.2 cards are not supported.
696 You will get a boot time penguin logo at no additional cost. Please
697 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
700 bool "EFI-based Framebuffer Support"
701 depends on (FB = y) && X86 && EFI
702 select FB_CFB_FILLRECT
703 select FB_CFB_COPYAREA
704 select FB_CFB_IMAGEBLIT
706 This is the EFI frame buffer device driver. If the firmware on
707 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
708 using the EFI framebuffer as your console.
711 tristate "N411 Apollo/Hecuba devkit support"
712 depends on FB && X86 && MMU
713 select FB_SYS_FILLRECT
714 select FB_SYS_COPYAREA
715 select FB_SYS_IMAGEBLIT
717 select FB_DEFERRED_IO
720 This enables support for the Apollo display controller in its
721 Hecuba form using the n411 devkit.
724 tristate "Hercules mono graphics support"
726 select FB_CFB_FILLRECT
727 select FB_CFB_COPYAREA
728 select FB_CFB_IMAGEBLIT
730 Say Y here if you have a Hercules mono graphics card.
732 To compile this driver as a module, choose M here: the
733 module will be called hgafb.
735 As this card technology is 15 years old, most people will answer N
739 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
740 depends on FB_HGA && EXPERIMENTAL
742 This will compile the Hercules mono graphics with
743 acceleration functions.
746 tristate "SGI Visual Workstation framebuffer support"
747 depends on FB && X86_VISWS
748 select FB_CFB_FILLRECT
749 select FB_CFB_COPYAREA
750 select FB_CFB_IMAGEBLIT
752 SGI Visual Workstation support for framebuffer graphics.
755 bool "SGI Graphics Backend frame buffer support"
756 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
757 select FB_CFB_FILLRECT
758 select FB_CFB_COPYAREA
759 select FB_CFB_IMAGEBLIT
761 This is the frame buffer device driver for SGI Graphics Backend.
762 This chip is used in SGI O2 and Visual Workstation 320/540.
765 int "Video memory size in MB"
769 This is the amount of memory reserved for the framebuffer,
770 which can be any value between 1MB and 8MB.
773 bool "SBUS and UPA framebuffers"
774 depends on (FB = y) && SPARC
776 Say Y if you want support for SBUS or UPA based frame buffer device.
780 depends on (FB = y) && (SPARC && FB_SBUS)
781 select FB_CFB_FILLRECT
782 select FB_CFB_COPYAREA
783 select FB_CFB_IMAGEBLIT
785 This is the frame buffer device driver for the BWtwo frame buffer.
788 bool "CGthree support"
789 depends on (FB = y) && (SPARC && FB_SBUS)
790 select FB_CFB_FILLRECT
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
794 This is the frame buffer device driver for the CGthree frame buffer.
797 bool "CGsix (GX,TurboGX) support"
798 depends on (FB = y) && (SPARC && FB_SBUS)
799 select FB_CFB_COPYAREA
800 select FB_CFB_IMAGEBLIT
802 This is the frame buffer device driver for the CGsix (GX, TurboGX)
806 bool "Creator/Creator3D/Elite3D support"
807 depends on FB_SBUS && SPARC64
808 select FB_CFB_COPYAREA
809 select FB_CFB_IMAGEBLIT
811 This is the frame buffer device driver for the Creator, Creator3D,
812 and Elite3D graphics boards.
815 bool "TCX (SS4/SS5 only) support"
817 select FB_CFB_FILLRECT
818 select FB_CFB_COPYAREA
819 select FB_CFB_IMAGEBLIT
821 This is the frame buffer device driver for the TCX 24/8bit frame
825 bool "CGfourteen (SX) support"
827 select FB_CFB_FILLRECT
828 select FB_CFB_COPYAREA
829 select FB_CFB_IMAGEBLIT
831 This is the frame buffer device driver for the CGfourteen frame
832 buffer on Desktop SPARCsystems with the SX graphics option.
835 bool "P9100 (Sparcbook 3 only) support"
837 select FB_CFB_FILLRECT
838 select FB_CFB_COPYAREA
839 select FB_CFB_IMAGEBLIT
841 This is the frame buffer device driver for the P9100 card
842 supported on Sparcbook 3 machines.
845 bool "Leo (ZX) support"
847 select FB_CFB_FILLRECT
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 This is the frame buffer device driver for the SBUS-based Sun ZX
852 (leo) frame buffer cards.
855 bool "IGA 168x display support"
856 depends on (FB = y) && SPARC32
857 select FB_CFB_FILLRECT
858 select FB_CFB_COPYAREA
859 select FB_CFB_IMAGEBLIT
861 This is the framebuffer device for the INTERGRAPHICS 1680 and
862 successor frame buffer cards.
865 bool "Sun XVR-500 3DLABS Wildcat support"
866 depends on (FB = y) && PCI && SPARC64
867 select FB_CFB_FILLRECT
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
871 This is the framebuffer device for the Sun XVR-500 and similar
872 graphics cards based upon the 3DLABS Wildcat chipset. The driver
873 only works on sparc64 systems where the system firmware has
874 mostly initialized the card already. It is treated as a
875 completely dumb framebuffer device.
878 bool "Sun XVR-2500 3DLABS Wildcat support"
879 depends on (FB = y) && PCI && SPARC64
880 select FB_CFB_FILLRECT
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
884 This is the framebuffer device for the Sun XVR-2500 and similar
885 graphics cards based upon the 3DLABS Wildcat chipset. The driver
886 only works on sparc64 systems where the system firmware has
887 mostly initialized the card already. It is treated as a
888 completely dumb framebuffer device.
891 tristate "NEC PowerVR 2 display support"
892 depends on FB && SH_DREAMCAST
893 select FB_CFB_FILLRECT
894 select FB_CFB_COPYAREA
895 select FB_CFB_IMAGEBLIT
897 Say Y here if you have a PowerVR 2 card in your box. If you plan to
898 run linux on your Dreamcast, you will have to say Y here.
899 This driver may or may not work on other PowerVR 2 cards, but is
900 totally untested. Use at your own risk. If unsure, say N.
902 To compile this driver as a module, choose M here: the
903 module will be called pvr2fb.
905 You can pass several parameters to the driver at boot time or at
906 module load time. The parameters look like "video=pvr2:XXX", where
907 the meaning of XXX can be found at the end of the main source file
908 (<file:drivers/video/pvr2fb.c>). Please see the file
909 <file:Documentation/fb/pvr2fb.txt>.
912 bool "Epson 1355 framebuffer support"
913 depends on (FB = y) && ARCH_CEIVA
914 select FB_CFB_FILLRECT
915 select FB_CFB_COPYAREA
916 select FB_CFB_IMAGEBLIT
918 Build in support for the SED1355 Epson Research Embedded RAMDAC
919 LCD/CRT Controller (since redesignated as the S1D13505) as a
920 framebuffer. Product specs at
921 <http://www.erd.epson.com/vdc/html/products.htm>.
924 tristate "Epson S1D13XXX framebuffer support"
926 select FB_CFB_FILLRECT
927 select FB_CFB_COPYAREA
928 select FB_CFB_IMAGEBLIT
930 Support for S1D13XXX framebuffer device family (currently only
931 working with S1D13806). Product specs at
932 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
935 tristate "AT91/AT32 LCD Controller support"
936 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
937 select FB_CFB_FILLRECT
938 select FB_CFB_COPYAREA
939 select FB_CFB_IMAGEBLIT
941 This enables support for the AT91/AT32 LCD Controller.
944 bool "Frame Buffer in internal SRAM"
945 depends on FB_ATMEL && ARCH_AT91SAM9261
947 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
948 to let frame buffer in external SDRAM.
951 bool "Use a STN display with AT91/AT32 LCD Controller"
952 depends on FB_ATMEL && MACH_AT91SAM9261EK
955 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
956 Controller. Say N if you want to connect a TFT.
961 tristate "nVidia Framebuffer Support"
963 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
964 select FB_MODE_HELPERS
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
971 This driver supports graphics boards with the nVidia chips, TNT
972 and newer. For very old chipsets, such as the RIVA128, then use
974 Say Y if you have such a graphics board.
976 To compile this driver as a module, choose M here: the
977 module will be called nvidiafb.
980 bool "Enable DDC Support"
984 This enables I2C support for nVidia Chipsets. This is used
985 only for getting EDID information from the attached display
986 allowing for robust video mode handling and switching.
988 Because fbdev-2.6 requires that drivers must be able to
989 independently validate video mode parameters, you should say Y
992 config FB_NVIDIA_DEBUG
993 bool "Lots of debug output"
997 Say Y here if you want the nVidia driver to output all sorts
998 of debugging information to provide to the maintainer when
999 something goes wrong.
1001 config FB_NVIDIA_BACKLIGHT
1002 bool "Support for backlight control"
1003 depends on FB_NVIDIA
1006 Say Y here if you want to control the backlight of your display.
1009 tristate "nVidia Riva support"
1010 depends on FB && PCI
1011 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1012 select FB_MODE_HELPERS
1013 select FB_CFB_FILLRECT
1014 select FB_CFB_COPYAREA
1015 select FB_CFB_IMAGEBLIT
1019 This driver supports graphics boards with the nVidia Riva/Geforce
1021 Say Y if you have such a graphics board.
1023 To compile this driver as a module, choose M here: the
1024 module will be called rivafb.
1027 bool "Enable DDC Support"
1031 This enables I2C support for nVidia Chipsets. This is used
1032 only for getting EDID information from the attached display
1033 allowing for robust video mode handling and switching.
1035 Because fbdev-2.6 requires that drivers must be able to
1036 independently validate video mode parameters, you should say Y
1039 config FB_RIVA_DEBUG
1040 bool "Lots of debug output"
1044 Say Y here if you want the Riva driver to output all sorts
1045 of debugging information to provide to the maintainer when
1046 something goes wrong.
1048 config FB_RIVA_BACKLIGHT
1049 bool "Support for backlight control"
1053 Say Y here if you want to control the backlight of your display.
1056 tristate "Intel 810/815 support (EXPERIMENTAL)"
1057 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1058 select FB_MODE_HELPERS
1059 select FB_CFB_FILLRECT
1060 select FB_CFB_COPYAREA
1061 select FB_CFB_IMAGEBLIT
1064 This driver supports the on-board graphics built in to the Intel 810
1065 and 815 chipsets. Say Y if you have and plan to use such a board.
1067 To compile this driver as a module, choose M here: the
1068 module will be called i810fb.
1070 For more information, please read
1071 <file:Documentation/fb/intel810.txt>
1074 bool "use VESA Generalized Timing Formula"
1077 If you say Y, then the VESA standard, Generalized Timing Formula
1078 or GTF, will be used to calculate the required video timing values
1079 per video mode. Since the GTF allows nondiscrete timings
1080 (nondiscrete being a range of values as opposed to discrete being a
1081 set of values), you'll be able to use any combination of horizontal
1082 and vertical resolutions, and vertical refresh rates without having
1083 to specify your own timing parameters. This is especially useful
1084 to maximize the performance of an aging display, or if you just
1085 have a display with nonstandard dimensions. A VESA compliant
1086 monitor is recommended, but can still work with non-compliant ones.
1087 If you need or want this, then select this option. The timings may
1088 not be compliant with Intel's recommended values. Use at your own
1091 If you say N, the driver will revert to discrete video timings
1092 using a set recommended by Intel in their documentation.
1097 bool "Enable DDC Support"
1098 depends on FB_I810 && FB_I810_GTF
1103 tristate "Intel LE80578 (Vermilion) support"
1104 depends on FB && PCI && X86
1105 select FB_MODE_HELPERS
1106 select FB_CFB_FILLRECT
1107 select FB_CFB_COPYAREA
1108 select FB_CFB_IMAGEBLIT
1110 This driver supports the LE80578 (Vermilion Range) chipset
1112 config FB_CARILLO_RANCH
1113 tristate "Intel Carillo Ranch support"
1114 depends on FB_LE80578 && FB && PCI && X86
1116 This driver supports the LE80578 (Carillo Ranch) board
1119 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1120 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL
1121 select FB_MODE_HELPERS
1122 select FB_CFB_FILLRECT
1123 select FB_CFB_COPYAREA
1124 select FB_CFB_IMAGEBLIT
1125 select FB_BOOT_VESA_SUPPORT
1127 This driver supports the on-board graphics built in to the Intel
1128 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1129 Say Y if you have and plan to use such a board.
1131 If you say Y here and want DDC/I2C support you must first say Y to
1132 "I2C support" and "I2C bit-banging support" in the character devices
1135 If you say M here then "I2C support" and "I2C bit-banging support"
1136 can be build either as modules or built-in.
1138 To compile this driver as a module, choose M here: the
1139 module will be called intelfb.
1141 For more information, please read <file:Documentation/fb/intelfb.txt>
1143 config FB_INTEL_DEBUG
1144 bool "Intel driver Debug Messages"
1147 Say Y here if you want the Intel driver to output all sorts
1148 of debugging information to provide to the maintainer when
1149 something goes wrong.
1152 bool "DDC/I2C for Intel framebuffer support"
1157 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1160 tristate "Matrox acceleration"
1161 depends on FB && PCI
1162 select FB_CFB_FILLRECT
1163 select FB_CFB_COPYAREA
1164 select FB_CFB_IMAGEBLIT
1165 select FB_TILEBLITTING
1166 select FB_MACMODES if PPC_PMAC
1168 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1169 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1170 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1171 Matrox G400, G450 or G550 card in your box.
1173 To compile this driver as a module, choose M here: the
1174 module will be called matroxfb.
1176 You can pass several parameters to the driver at boot time or at
1177 module load time. The parameters look like "video=matrox:XXX", and
1178 are described in <file:Documentation/fb/matroxfb.txt>.
1180 config FB_MATROX_MILLENIUM
1181 bool "Millennium I/II support"
1182 depends on FB_MATROX
1184 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1185 video card. If you select "Advanced lowlevel driver options" below,
1186 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1187 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1188 also use font widths different from 8.
1190 config FB_MATROX_MYSTIQUE
1191 bool "Mystique support"
1192 depends on FB_MATROX
1194 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1195 video card. If you select "Advanced lowlevel driver options" below,
1196 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1197 packed pixel and 32 bpp packed pixel. You can also use font widths
1201 bool "G100/G200/G400/G450/G550 support"
1202 depends on FB_MATROX
1204 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1205 video card. If you select "Advanced lowlevel driver options", you
1206 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1207 pixel and 32 bpp packed pixel. You can also use font widths
1210 If you need support for G400 secondary head, you must first say Y to
1211 "I2C support" in the character devices section, and then to
1212 "Matrox I2C support" and "G400 second head support" here in the
1213 framebuffer section. G450/G550 secondary head and digital output
1214 are supported without additional modules.
1216 The driver starts in monitor mode. You must use the matroxset tool
1217 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1218 swap primary and secondary head outputs, or to change output mode.
1219 Secondary head driver always start in 640x480 resolution and you
1220 must use fbset to change it.
1222 Do not forget that second head supports only 16 and 32 bpp
1223 packed pixels, so it is a good idea to compile them into the kernel
1224 too. You can use only some font widths, as the driver uses generic
1225 painting procedures (the secondary head does not use acceleration
1228 G450/G550 hardware can display TV picture only from secondary CRTC,
1229 and it performs no scaling, so picture must have 525 or 625 lines.
1231 config FB_MATROX_I2C
1232 tristate "Matrox I2C support"
1233 depends on FB_MATROX
1236 This drivers creates I2C buses which are needed for accessing the
1237 DDC (I2C) bus present on all Matroxes, an I2C bus which
1238 interconnects Matrox optional devices, like MGA-TVO on G200 and
1239 G400, and the secondary head DDC bus, present on G400 only.
1241 You can say Y or M here if you want to experiment with monitor
1242 detection code. You must say Y or M here if you want to use either
1243 second head of G400 or MGA-TVO on G200 or G400.
1245 If you compile it as module, it will create a module named
1248 config FB_MATROX_MAVEN
1249 tristate "G400 second head support"
1250 depends on FB_MATROX_G && FB_MATROX_I2C
1252 WARNING !!! This support does not work with G450 !!!
1254 Say Y or M here if you want to use a secondary head (meaning two
1255 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1256 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1257 secondary head output is blanked while you are in X. With XFree
1258 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1259 the fbdev driver on first head and the fbdev driver on second head.
1261 If you compile it as module, two modules are created,
1262 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1263 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1264 also load i2c-matroxfb to get it to run.
1266 The driver starts in monitor mode and you must use the matroxset
1268 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1269 PAL or NTSC or to swap primary and secondary head outputs.
1270 Secondary head driver also always start in 640x480 resolution, you
1271 must use fbset to change it.
1273 Also do not forget that second head supports only 16 and 32 bpp
1274 packed pixels, so it is a good idea to compile them into the kernel
1275 too. You can use only some font widths, as the driver uses generic
1276 painting procedures (the secondary head does not use acceleration
1279 config FB_MATROX_MULTIHEAD
1280 bool "Multihead support"
1281 depends on FB_MATROX
1283 Say Y here if you have more than one (supported) Matrox device in
1284 your computer and you want to use all of them for different monitors
1285 ("multihead"). If you have only one device, you should say N because
1286 the driver compiled with Y is larger and a bit slower, especially on
1289 If you said M to "Matrox unified accelerated driver" and N here, you
1290 will still be able to use several Matrox devices simultaneously:
1291 insert several instances of the module matroxfb into the kernel
1292 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1293 for the different Matrox devices. This method is slightly faster but
1294 uses 40 KB of kernel memory per Matrox card.
1296 There is no need for enabling 'Matrox multihead support' if you have
1297 only one Matrox card in the box.
1300 tristate "ATI Radeon display support"
1301 depends on FB && PCI
1302 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1303 select FB_MODE_HELPERS
1304 select FB_CFB_FILLRECT
1305 select FB_CFB_COPYAREA
1306 select FB_CFB_IMAGEBLIT
1307 select FB_MACMODES if PPC_OF
1309 Choose this option if you want to use an ATI Radeon graphics card as
1310 a framebuffer device. There are both PCI and AGP versions. You
1311 don't need to choose this to run the Radeon in plain VGA mode.
1313 If you say Y here and want DDC/I2C support you must first say Y to
1314 "I2C support" and "I2C bit-banging support" in the character devices
1317 If you say M here then "I2C support" and "I2C bit-banging support"
1318 can be build either as modules or built-in.
1320 There is a product page at
1321 http://apps.ati.com/ATIcompare/
1323 config FB_RADEON_I2C
1324 bool "DDC/I2C for ATI Radeon support"
1325 depends on FB_RADEON
1329 Say Y here if you want DDC/I2C support for your Radeon board.
1331 config FB_RADEON_BACKLIGHT
1332 bool "Support for backlight control"
1333 depends on FB_RADEON
1336 Say Y here if you want to control the backlight of your display.
1338 config FB_RADEON_DEBUG
1339 bool "Lots of debug output from Radeon driver"
1340 depends on FB_RADEON
1343 Say Y here if you want the Radeon driver to output all sorts
1344 of debugging information to provide to the maintainer when
1345 something goes wrong.
1348 tristate "ATI Rage128 display support"
1349 depends on FB && PCI
1350 select FB_CFB_FILLRECT
1351 select FB_CFB_COPYAREA
1352 select FB_CFB_IMAGEBLIT
1353 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1354 select FB_MACMODES if PPC_PMAC
1356 This driver supports graphics boards with the ATI Rage128 chips.
1357 Say Y if you have such a graphics board and read
1358 <file:Documentation/fb/aty128fb.txt>.
1360 To compile this driver as a module, choose M here: the
1361 module will be called aty128fb.
1363 config FB_ATY128_BACKLIGHT
1364 bool "Support for backlight control"
1365 depends on FB_ATY128
1368 Say Y here if you want to control the backlight of your display.
1371 tristate "ATI Mach64 display support" if PCI || ATARI
1372 depends on FB && !SPARC32
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1376 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1377 select FB_MACMODES if PPC
1379 This driver supports graphics boards with the ATI Mach64 chips.
1380 Say Y if you have such a graphics board.
1382 To compile this driver as a module, choose M here: the
1383 module will be called atyfb.
1386 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1387 depends on PCI && FB_ATY
1388 default y if SPARC64 && PCI
1390 Say Y here to support use of ATI's 64-bit Rage boards (or other
1391 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1392 framebuffer device. The ATI product support page for these boards
1393 is at <http://support.ati.com/products/pc/mach64/>.
1395 config FB_ATY_GENERIC_LCD
1396 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1397 depends on FB_ATY_CT
1399 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1400 Rage XC, or Rage XL chipset.
1403 bool "Mach64 GX support" if PCI
1407 Say Y here to support use of the ATI Mach64 Graphics Expression
1408 board (or other boards based on the Mach64 GX chipset) as a
1409 framebuffer device. The ATI product support page for these boards
1411 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1413 config FB_ATY_BACKLIGHT
1414 bool "Support for backlight control"
1418 Say Y here if you want to control the backlight of your display.
1421 tristate "S3 Trio/Virge support"
1422 depends on FB && PCI
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1426 select FB_TILEBLITTING
1429 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1431 Driver for graphics boards with S3 Trio / S3 Virge chip.
1434 tristate "S3 Savage support"
1435 depends on FB && PCI && EXPERIMENTAL
1436 select FB_MODE_HELPERS
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1439 select FB_CFB_IMAGEBLIT
1442 This driver supports notebooks and computers with S3 Savage PCI/AGP
1445 Say Y if you have such a graphics card.
1447 To compile this driver as a module, choose M here; the module
1448 will be called savagefb.
1450 config FB_SAVAGE_I2C
1451 bool "Enable DDC2 Support"
1452 depends on FB_SAVAGE
1455 This enables I2C support for S3 Savage Chipsets. This is used
1456 only for getting EDID information from the attached display
1457 allowing for robust video mode handling and switching.
1459 Because fbdev-2.6 requires that drivers must be able to
1460 independently validate video mode parameters, you should say Y
1463 config FB_SAVAGE_ACCEL
1464 bool "Enable Console Acceleration"
1465 depends on FB_SAVAGE
1468 This option will compile in console acceleration support. If
1469 the resulting framebuffer console has bothersome glitches, then
1473 tristate "SiS/XGI display support"
1474 depends on FB && PCI
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1478 select FB_BOOT_VESA_SUPPORT
1480 This is the frame buffer device driver for the SiS 300, 315, 330
1481 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1482 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1484 To compile this driver as a module, choose M here; the module
1485 will be called sisfb.
1488 bool "SiS 300 series support"
1491 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1494 bool "SiS 315/330/340 series and XGI support"
1497 Say Y here to support use of the SiS 315, 330 and 340 series
1498 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1499 as XGI V3XT, V5, V8 and Z7.
1502 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1503 depends on FB && PCI
1504 select FB_CFB_FILLRECT
1505 select FB_CFB_COPYAREA
1506 select FB_CFB_IMAGEBLIT
1507 select FB_SOFT_CURSOR
1511 This is the frame buffer device driver for Graphics chips of VIA
1512 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1513 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1515 Say Y if you have a VIA UniChrome graphics board.
1517 To compile this driver as a module, choose M here: the
1518 module will be called viafb.
1520 tristate "NeoMagic display support"
1521 depends on FB && PCI
1522 select FB_MODE_HELPERS
1523 select FB_CFB_FILLRECT
1524 select FB_CFB_COPYAREA
1525 select FB_CFB_IMAGEBLIT
1528 This driver supports notebooks with NeoMagic PCI chips.
1529 Say Y if you have such a graphics card.
1531 To compile this driver as a module, choose M here: the
1532 module will be called neofb.
1535 tristate "IMG Kyro support"
1536 depends on FB && PCI
1537 select FB_CFB_FILLRECT
1538 select FB_CFB_COPYAREA
1539 select FB_CFB_IMAGEBLIT
1541 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1544 To compile this driver as a module, choose M here: the
1545 module will be called kyrofb.
1548 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1549 depends on FB && PCI
1550 select FB_CFB_IMAGEBLIT
1551 select FB_CFB_FILLRECT
1552 select FB_CFB_COPYAREA
1553 select FB_MODE_HELPERS
1555 This driver supports graphics boards with the 3Dfx Banshee,
1556 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1557 such a graphics board.
1559 To compile this driver as a module, choose M here: the
1560 module will be called tdfxfb.
1562 config FB_3DFX_ACCEL
1563 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1564 depends on FB_3DFX && EXPERIMENTAL
1566 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1567 device driver with acceleration functions.
1570 bool "Enable DDC/I2C support"
1571 depends on FB_3DFX && EXPERIMENTAL
1575 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1578 tristate "3Dfx Voodoo Graphics (sst1) support"
1579 depends on FB && PCI
1580 select FB_CFB_FILLRECT
1581 select FB_CFB_COPYAREA
1582 select FB_CFB_IMAGEBLIT
1584 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1585 Voodoo2 (cvg) based graphics card.
1587 To compile this driver as a module, choose M here: the
1588 module will be called sstfb.
1590 WARNING: Do not use any application that uses the 3D engine
1591 (namely glide) while using this driver.
1592 Please read the <file:Documentation/fb/sstfb.txt> for supported
1593 options and other important info support.
1596 tristate "VIA VT8623 support"
1597 depends on FB && PCI
1598 select FB_CFB_FILLRECT
1599 select FB_CFB_COPYAREA
1600 select FB_CFB_IMAGEBLIT
1601 select FB_TILEBLITTING
1604 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1606 Driver for CastleRock integrated graphics core in the
1607 VIA VT8623 [Apollo CLE266] chipset.
1610 tristate "Trident/CyberXXX/CyberBlade support"
1611 depends on FB && PCI
1612 select FB_CFB_FILLRECT
1613 select FB_CFB_COPYAREA
1614 select FB_CFB_IMAGEBLIT
1616 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1617 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1619 There are also integrated versions of these chips called CyberXXXX,
1620 CyberImage or CyberBlade. These chips are mostly found in laptops
1621 but also on some motherboards including early VIA EPIA motherboards.
1622 For more information, read <file:Documentation/fb/tridentfb.txt>
1624 Say Y if you have such a graphics board.
1626 To compile this driver as a module, choose M here: the
1627 module will be called tridentfb.
1630 tristate "ARK 2000PV support"
1631 depends on FB && PCI
1632 select FB_CFB_FILLRECT
1633 select FB_CFB_COPYAREA
1634 select FB_CFB_IMAGEBLIT
1635 select FB_TILEBLITTING
1638 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1640 Driver for PCI graphics boards with ARK 2000PV chip
1641 and ICS 5342 RAMDAC.
1644 tristate "Permedia3 support (EXPERIMENTAL)"
1645 depends on FB && PCI && EXPERIMENTAL
1646 select FB_CFB_FILLRECT
1647 select FB_CFB_COPYAREA
1648 select FB_CFB_IMAGEBLIT
1650 This is the frame buffer device driver for the 3DLabs Permedia3
1651 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1652 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1653 and maybe other boards.
1656 tristate "Fujitsu carmine frame buffer support"
1657 depends on FB && PCI
1658 select FB_CFB_FILLRECT
1659 select FB_CFB_COPYAREA
1660 select FB_CFB_IMAGEBLIT
1662 This is the frame buffer device driver for the Fujitsu Carmine chip.
1663 The driver provides two independent frame buffer devices.
1666 depends on FB_CARMINE
1667 prompt "DRAM timing"
1668 default FB_CARMINE_DRAM_EVAL
1670 config FB_CARMINE_DRAM_EVAL
1671 bool "Eval board timings"
1673 Use timings which work on the eval card.
1675 config CARMINE_DRAM_CUSTOM
1676 bool "Custom board timings"
1678 Use custom board timings.
1682 bool "Au1100 LCD Driver"
1683 depends on (FB = y) && MIPS && SOC_AU1100
1684 select FB_CFB_FILLRECT
1685 select FB_CFB_COPYAREA
1686 select FB_CFB_IMAGEBLIT
1688 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1689 various panels and CRTs by passing in kernel cmd line option
1690 au1100fb:panel=<name>.
1693 bool "Au1200 LCD Driver"
1694 depends on (FB = y) && MIPS && SOC_AU1200
1695 select FB_CFB_FILLRECT
1696 select FB_CFB_COPYAREA
1697 select FB_CFB_IMAGEBLIT
1699 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1700 various panels and CRTs by passing in kernel cmd line option
1701 au1200fb:panel=<name>.
1703 source "drivers/video/geode/Kconfig"
1706 tristate "HD64461 Frame Buffer support"
1707 depends on FB && HD64461
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 This is the frame buffer device driver for the Hitachi HD64461 LCD
1716 bool "PMAG-AA TURBOchannel framebuffer support"
1717 depends on (FB = y) && TC
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1722 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1723 used mainly in the MIPS-based DECstation series.
1726 tristate "PMAG-BA TURBOchannel framebuffer support"
1728 select FB_CFB_FILLRECT
1729 select FB_CFB_COPYAREA
1730 select FB_CFB_IMAGEBLIT
1732 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1733 used mainly in the MIPS-based DECstation series.
1736 tristate "PMAGB-B TURBOchannel framebuffer support"
1738 select FB_CFB_FILLRECT
1739 select FB_CFB_COPYAREA
1740 select FB_CFB_IMAGEBLIT
1742 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1743 in the MIPS-based DECstation series. The card is currently only
1744 supported in 1280x1024x8 mode.
1747 bool "Maxine (Personal DECstation) onboard framebuffer support"
1748 depends on (FB = y) && MACH_DECSTATION
1749 select FB_CFB_FILLRECT
1750 select FB_CFB_COPYAREA
1751 select FB_CFB_IMAGEBLIT
1753 Support for the onboard framebuffer (1024x768x8) in the Personal
1754 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1758 bool "G364 frame buffer support"
1759 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1760 select FB_CFB_FILLRECT
1761 select FB_CFB_COPYAREA
1762 select FB_CFB_IMAGEBLIT
1764 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1765 Olivetti M700-10 systems.
1768 bool "Motorola 68328 native frame buffer support"
1769 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1770 select FB_CFB_FILLRECT
1771 select FB_CFB_COPYAREA
1772 select FB_CFB_IMAGEBLIT
1774 Say Y here if you want to support the built-in frame buffer of
1775 the Motorola 68328 CPU family.
1778 tristate "PXA LCD framebuffer support"
1779 depends on FB && ARCH_PXA
1780 select FB_CFB_FILLRECT
1781 select FB_CFB_COPYAREA
1782 select FB_CFB_IMAGEBLIT
1784 Frame buffer driver for the built-in LCD controller in the Intel
1787 This driver is also available as a module ( = code which can be
1788 inserted and removed from the running kernel whenever you want). The
1789 module will be called pxafb. If you want to compile it as a module,
1790 say M here and read <file:Documentation/kbuild/modules.txt>.
1794 config FB_PXA_OVERLAY
1795 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1797 depends on FB_PXA && (PXA27x || PXA3xx)
1799 config FB_PXA_SMARTPANEL
1800 bool "PXA Smartpanel LCD support"
1804 config FB_PXA_PARAMETERS
1805 bool "PXA LCD command line parameters"
1809 Enable the use of kernel command line or module parameters
1810 to configure the physical properties of the LCD panel when
1811 using the PXA LCD driver.
1813 This option allows you to override the panel parameters
1814 supplied by the platform in order to support multiple
1815 different models of flatpanel. If you will only be using a
1816 single model of flatpanel then you can safely leave this
1819 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1822 tristate "2700G LCD framebuffer support"
1823 depends on FB && ARCH_PXA
1824 select FB_CFB_FILLRECT
1825 select FB_CFB_COPYAREA
1826 select FB_CFB_IMAGEBLIT
1828 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1832 bool "Enable debugging info via debugfs"
1833 depends on FB_MBX && DEBUG_FS
1836 Enable this if you want debugging information using the debug
1837 filesystem (debugfs)
1842 tristate "Freescale DIU framebuffer support"
1843 depends on FB && FSL_SOC
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1847 select PPC_LIB_RHEAP
1849 Framebuffer driver for the Freescale SoC DIU
1852 tristate "W100 frame buffer support"
1853 depends on FB && ARCH_PXA
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1859 It can also drive the w3220 chip found on iPAQ hx4700.
1861 This driver is also available as a module ( = code which can be
1862 inserted and removed from the running kernel whenever you want). The
1863 module will be called w100fb. If you want to compile it as a module,
1864 say M here and read <file:Documentation/kbuild/modules.txt>.
1868 config FB_SH_MOBILE_LCDC
1869 tristate "SuperH Mobile LCDC framebuffer support"
1870 depends on FB && SUPERH
1871 select FB_SYS_FILLRECT
1872 select FB_SYS_COPYAREA
1873 select FB_SYS_IMAGEBLIT
1875 select FB_DEFERRED_IO
1877 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1880 tristate "Toshiba Mobile IO FrameBuffer support"
1881 depends on FB && MFD_CORE
1882 select FB_CFB_FILLRECT
1883 select FB_CFB_COPYAREA
1884 select FB_CFB_IMAGEBLIT
1886 Frame buffer driver for the Toshiba Mobile IO integrated as found
1887 on the Sharp SL-6000 series
1889 This driver is also available as a module ( = code which can be
1890 inserted and removed from the running kernel whenever you want). The
1891 module will be called tmiofb. If you want to compile it as a module,
1892 say M here and read <file:Documentation/kbuild/modules.txt>.
1896 config FB_TMIO_ACCELL
1897 bool "tmiofb acceleration"
1902 tristate "Samsung S3C framebuffer support"
1903 depends on FB && ARCH_S3C64XX
1904 select FB_CFB_FILLRECT
1905 select FB_CFB_COPYAREA
1906 select FB_CFB_IMAGEBLIT
1908 Frame buffer driver for the built-in FB controller in the Samsung
1909 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1910 and the S3C64XX series such as the S3C6400 and S3C6410.
1912 These chips all have the same basic framebuffer design with the
1913 actual capabilities depending on the chip. For instance the S3C6400
1914 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1915 currently only have two.
1917 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1919 config FB_S3C_DEBUG_REGWRITE
1920 bool "Debug register writes"
1923 Show all register writes via printk(KERN_DEBUG)
1926 tristate "S3C2410 LCD framebuffer support"
1927 depends on FB && ARCH_S3C2410
1928 select FB_CFB_FILLRECT
1929 select FB_CFB_COPYAREA
1930 select FB_CFB_IMAGEBLIT
1932 Frame buffer driver for the built-in LCD controller in the Samsung
1935 This driver is also available as a module ( = code which can be
1936 inserted and removed from the running kernel whenever you want). The
1937 module will be called s3c2410fb. If you want to compile it as a module,
1938 say M here and read <file:Documentation/kbuild/modules.txt>.
1941 config FB_S3C2410_DEBUG
1942 bool "S3C2410 lcd debug messages"
1943 depends on FB_S3C2410
1945 Turn on debugging messages. Note that you can set/unset at run time
1949 tristate "Silicon Motion SM501 framebuffer support"
1950 depends on FB && MFD_SM501
1951 select FB_CFB_FILLRECT
1952 select FB_CFB_COPYAREA
1953 select FB_CFB_IMAGEBLIT
1955 Frame buffer driver for the CRT and LCD controllers in the Silicon
1958 This driver is also available as a module ( = code which can be
1959 inserted and removed from the running kernel whenever you want). The
1960 module will be called sm501fb. If you want to compile it as a module,
1961 say M here and read <file:Documentation/kbuild/modules.txt>.
1966 config FB_PNX4008_DUM
1967 tristate "Display Update Module support on Philips PNX4008 board"
1968 depends on FB && ARCH_PNX4008
1970 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1972 config FB_PNX4008_DUM_RGB
1973 tristate "RGB Framebuffer support on Philips PNX4008 board"
1974 depends on FB_PNX4008_DUM
1975 select FB_CFB_FILLRECT
1976 select FB_CFB_COPYAREA
1977 select FB_CFB_IMAGEBLIT
1979 Say Y here to enable support for PNX4008 RGB Framebuffer
1981 config FB_IBM_GXT4500
1982 tristate "Framebuffer support for IBM GXT4500P adaptor"
1983 depends on FB && PPC
1984 select FB_CFB_FILLRECT
1985 select FB_CFB_COPYAREA
1986 select FB_CFB_IMAGEBLIT
1988 Say Y here to enable support for the IBM GXT4500P display
1989 adaptor, found on some IBM System P (pSeries) machines.
1992 tristate "PS3 GPU framebuffer driver"
1993 depends on FB && PS3_PS3AV
1994 select FB_SYS_FILLRECT
1995 select FB_SYS_COPYAREA
1996 select FB_SYS_IMAGEBLIT
1998 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2000 Include support for the virtual frame buffer in the PS3 platform.
2002 config FB_PS3_DEFAULT_SIZE_M
2003 int "PS3 default frame buffer size (in MiB)"
2007 This is the default size (in MiB) of the virtual frame buffer in
2009 The default value can be overridden on the kernel command line
2010 using the "ps3fb" option (e.g. "ps3fb=9M");
2013 tristate "Xilinx frame buffer support"
2014 depends on FB && XILINX_VIRTEX
2015 select FB_CFB_FILLRECT
2016 select FB_CFB_COPYAREA
2017 select FB_CFB_IMAGEBLIT
2019 Include support for the Xilinx ML300/ML403 reference design
2020 framebuffer. ML300 carries a 640*480 LCD display on the board,
2021 ML403 uses a standard DB15 VGA connector.
2024 tristate "Cobalt server LCD frame buffer support"
2025 depends on FB && MIPS_COBALT
2028 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2029 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2030 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2031 select FB_CFB_FILLRECT
2032 select FB_CFB_COPYAREA
2033 select FB_CFB_IMAGEBLIT
2035 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2036 (D)STN/TFT LCD Controller.
2037 Supports display resolutions up to 1024x1024 pixel, grayscale and
2038 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2039 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2040 panels <= 320 pixel horizontal resolution.
2043 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2045 select FB_SYS_FILLRECT
2046 select FB_SYS_COPYAREA
2047 select FB_SYS_IMAGEBLIT
2050 This is a `virtual' frame buffer device. It operates on a chunk of
2051 unswappable kernel memory instead of on the memory of a graphics
2052 board. This means you cannot see any output sent to this frame
2053 buffer device, while it does consume precious memory. The main use
2054 of this frame buffer device is testing and debugging the frame
2055 buffer subsystem. Do NOT enable it for normal systems! To protect
2056 the innocent, it has to be enabled explicitly at boot time using the
2057 kernel option `video=vfb:'.
2059 To compile this driver as a module, choose M here: the
2060 module will be called vfb. In order to load it, you must use
2061 the vfb_enable=1 option.
2065 config XEN_FBDEV_FRONTEND
2066 tristate "Xen virtual frame buffer support"
2067 depends on FB && XEN
2068 select FB_SYS_FILLRECT
2069 select FB_SYS_COPYAREA
2070 select FB_SYS_IMAGEBLIT
2072 select FB_DEFERRED_IO
2075 This driver implements the front-end of the Xen virtual
2076 frame buffer driver. It communicates with a back-end
2080 tristate "E-Ink Metronome/8track controller support"
2082 select FB_SYS_FILLRECT
2083 select FB_SYS_COPYAREA
2084 select FB_SYS_IMAGEBLIT
2086 select FB_DEFERRED_IO
2088 This driver implements support for the E-Ink Metronome
2089 controller. The pre-release name for this device was 8track
2090 and could also have been called by some vendors as PVI-nnnn.
2093 tristate "Fujitsu MB862xx GDC support"
2095 select FB_CFB_FILLRECT
2096 select FB_CFB_COPYAREA
2097 select FB_CFB_IMAGEBLIT
2099 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2101 config FB_MB862XX_PCI_GDC
2102 bool "Carmine/Coral-P(A) GDC"
2103 depends on PCI && FB_MB862XX
2105 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2106 PCI graphics controller devices.
2108 config FB_MB862XX_LIME
2110 depends on FB_MB862XX
2111 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"