5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/char/drm/Kconfig"
16 config VIDEO_OUTPUT_CONTROL
17 tristate "Lowlevel video output switch controls"
19 This framework adds support for low-level control of the video
23 tristate "Support for frame buffer devices"
25 The frame buffer device provides an abstraction for the graphics
26 hardware. It represents the frame buffer of some video hardware and
27 allows application software to access the graphics hardware through
28 a well-defined interface, so the software doesn't need to know
29 anything about the low-level (hardware register) stuff.
31 Frame buffer devices work identically across the different
32 architectures supported by Linux and make the implementation of
33 application programs easier and more portable; at this point, an X
34 server exists which uses the frame buffer device exclusively.
35 On several non-X86 architectures, the frame buffer device is the
36 only way to use the graphics hardware.
38 The device is accessed through special device nodes, usually located
39 in the /dev directory, i.e. /dev/fb*.
41 You need an utility program called fbset to make full use of frame
42 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
43 and the Framebuffer-HOWTO at
44 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
47 Say Y here and to the driver for your graphics board below if you
48 are compiling a kernel for a non-x86 architecture.
50 If you are compiling for the x86 architecture, you can say Y if you
51 want to play with it, but it is not essential. Please note that
52 running graphical applications that directly touch the hardware
53 (e.g. an accelerated X server) and that are not frame buffer
54 device-aware may cause unexpected results. If unsure, say N.
57 bool "Enable firmware EDID"
61 This enables access to the EDID transferred from the firmware.
62 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
63 transfers do not work for your driver and if you are using
64 nvidiafb, i810fb or savagefb.
66 In general, choosing Y for this option is safe. If you
67 experience extremely long delays while booting before you get
68 something on your display, try setting this to N. Matrox cards in
69 combination with certain motherboards and monitors are known to
70 suffer from this problem.
79 config FB_CFB_FILLRECT
84 Include the cfb_fillrect function for generic software rectangle
85 filling. This is used by drivers that don't provide their own
86 (accelerated) version.
88 config FB_CFB_COPYAREA
93 Include the cfb_copyarea function for generic software area copying.
94 This is used by drivers that don't provide their own (accelerated)
97 config FB_CFB_IMAGEBLIT
102 Include the cfb_imageblit function for generic software image
103 blitting. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_REV_PIXELS_IN_BYTE
111 Allow generic frame-buffer functions to work on displays with 1, 2
112 and 4 bits per pixel depths which has opposite order of pixels in
113 byte order to bytes in long order.
115 config FB_SYS_FILLRECT
120 Include the sys_fillrect function for generic software rectangle
121 filling. This is used by drivers that don't provide their own
122 (accelerated) version and the framebuffer is in system RAM.
124 config FB_SYS_COPYAREA
129 Include the sys_copyarea function for generic software area copying.
130 This is used by drivers that don't provide their own (accelerated)
131 version and the framebuffer is in system RAM.
133 config FB_SYS_IMAGEBLIT
138 Include the sys_imageblit function for generic software image
139 blitting. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 menuconfig FB_FOREIGN_ENDIAN
143 bool "Framebuffer foreign endianness support"
146 This menu will let you enable support for the framebuffers with
147 non-native endianness (e.g. Little-Endian framebuffer on a
148 Big-Endian machine). Most probably you don't have such hardware,
149 so it's safe to say "n" here.
152 prompt "Choice endianness support"
153 depends on FB_FOREIGN_ENDIAN
155 config FB_BOTH_ENDIAN
156 bool "Support for Big- and Little-Endian framebuffers"
159 bool "Support for Big-Endian framebuffers only"
161 config FB_LITTLE_ENDIAN
162 bool "Support for Little-Endian framebuffers only"
171 config FB_DEFERRED_IO
181 Common utility functions useful to fbdev drivers of VGA-based
192 select BACKLIGHT_LCD_SUPPORT
193 select BACKLIGHT_CLASS_DEVICE
196 config FB_MODE_HELPERS
197 bool "Enable Video Mode Handling Helpers"
201 This enables functions for handling video modes using the
202 Generalized Timing Formula and the EDID parser. A few drivers rely
203 on this feature such as the radeonfb, rivafb, and the i810fb. If
204 your driver does not take advantage of this feature, choosing Y will
205 just increase the kernel size by about 5K.
207 config FB_TILEBLITTING
208 bool "Enable Tile Blitting Support"
212 This enables tile blitting. Tile blitting is a drawing technique
213 where the screen is divided into rectangular sections (tiles), whereas
214 the standard blitting divides the screen into pixels. Because the
215 default drawing element is a tile, drawing functions will be passed
216 parameters in terms of number of tiles instead of number of pixels.
217 For example, to draw a single character, instead of using bitmaps,
218 an index to an array of bitmaps will be used. To clear or move a
219 rectangular section of a screen, the rectangle will be described in
220 terms of number of tiles in the x- and y-axis.
222 This is particularly important to one driver, matroxfb. If
225 comment "Frame buffer hardware drivers"
229 tristate "Cirrus Logic support"
230 depends on FB && (ZORRO || PCI)
231 select FB_CFB_FILLRECT
232 select FB_CFB_COPYAREA
233 select FB_CFB_IMAGEBLIT
235 This enables support for Cirrus Logic GD542x/543x based boards on
236 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
238 If you have a PCI-based system, this enables support for these
239 chips: GD-543x, GD-544x, GD-5480.
241 Please read the file <file:Documentation/fb/cirrusfb.txt>.
243 Say N unless you have such a graphics board or plan to get one
244 before you next recompile the kernel.
247 tristate "Permedia2 support"
248 depends on FB && ((AMIGA && BROKEN) || PCI)
249 select FB_CFB_FILLRECT
250 select FB_CFB_COPYAREA
251 select FB_CFB_IMAGEBLIT
253 This is the frame buffer device driver for the Permedia2 AGP frame
254 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
256 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
258 config FB_PM2_FIFO_DISCONNECT
259 bool "enable FIFO disconnect feature"
260 depends on FB_PM2 && PCI
262 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
265 tristate "ARM PrimeCell PL110 support"
266 depends on FB && ARM && ARM_AMBA
267 select FB_CFB_FILLRECT
268 select FB_CFB_COPYAREA
269 select FB_CFB_IMAGEBLIT
271 This framebuffer device driver is for the ARM PrimeCell PL110
272 Colour LCD controller. ARM PrimeCells provide the building
273 blocks for System on a Chip devices.
275 If you want to compile this as a module (=code which can be
276 inserted into and removed from the running kernel), say M
277 here and read <file:Documentation/kbuild/modules.txt>. The module
278 will be called amba-clcd.
282 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
284 default FB_ARMCLCD_SHARP_LQ035Q7DB02
286 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
287 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
289 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
290 color QVGA, HRTFT panel. The LogicPD device includes
291 an integrated HRTFT controller IC.
292 The native resolution is 240x320.
294 config FB_ARMCLCD_SHARP_LQ057Q3DC02
295 bool "LogicPD LCD 5.7\" QVGA"
297 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
298 color QVGA, TFT panel. The LogicPD device includes an
299 The native resolution is 320x240.
301 config FB_ARMCLCD_SHARP_LQ64D343
302 bool "LogicPD LCD 6.4\" VGA"
304 This is an implementation of the Sharp LQ64D343, a 6.4"
305 color VGA, TFT panel. The LogicPD device includes an
306 The native resolution is 640x480.
308 config FB_ARMCLCD_SHARP_LQ10D368
309 bool "LogicPD LCD 10.4\" VGA"
311 This is an implementation of the Sharp LQ10D368, a 10.4"
312 color VGA, TFT panel. The LogicPD device includes an
313 The native resolution is 640x480.
316 config FB_ARMCLCD_SHARP_LQ121S1DG41
317 bool "LogicPD LCD 12.1\" SVGA"
319 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
320 color SVGA, TFT panel. The LogicPD device includes an
321 The native resolution is 800x600.
323 This panel requires a clock rate may be an integer fraction
324 of the base LCDCLK frequency. The driver will select the
325 highest frequency available that is lower than the maximum
326 allowed. The panel may flicker if the clock rate is
327 slower than the recommended minimum.
329 config FB_ARMCLCD_AUO_A070VW01_WIDE
330 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
332 This is an implementation of the AU Optronics, a 7.0"
333 WIDE Color. The native resolution is 234x480.
335 config FB_ARMCLCD_HITACHI
336 bool "Hitachi Wide Screen 800x480"
338 This is an implementation of the Hitachi 800x480.
344 bool "Acorn VIDC support"
345 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
346 select FB_CFB_FILLRECT
347 select FB_CFB_COPYAREA
348 select FB_CFB_IMAGEBLIT
350 This is the frame buffer device driver for the Acorn VIDC graphics
351 hardware found in Acorn RISC PCs and other ARM-based machines. If
355 bool "CLPS711X LCD support"
356 depends on (FB = y) && ARM && ARCH_CLPS711X
357 select FB_CFB_FILLRECT
358 select FB_CFB_COPYAREA
359 select FB_CFB_IMAGEBLIT
361 Say Y to enable the Framebuffer driver for the CLPS7111 and
365 bool "SA-1100 LCD support"
366 depends on (FB = y) && ARM && ARCH_SA1100
367 select FB_CFB_FILLRECT
368 select FB_CFB_COPYAREA
369 select FB_CFB_IMAGEBLIT
371 This is a framebuffer device for the SA-1100 LCD Controller.
372 See <http://www.linux-fbdev.org/> for information on framebuffer
375 If you plan to use the LCD display with your SA-1100 system, say
379 tristate "Motorola i.MX LCD support"
380 depends on FB && ARM && ARCH_IMX
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
386 tristate "CyberPro 2000/2010/5000 support"
387 depends on FB && PCI && (BROKEN || !SPARC64)
388 select FB_CFB_FILLRECT
389 select FB_CFB_COPYAREA
390 select FB_CFB_IMAGEBLIT
392 This enables support for the Integraphics CyberPro 20x0 and 5000
393 VGA chips used in the Rebel.com Netwinder and other machines.
394 Say Y if you have a NetWinder or a graphics card containing this
395 device, otherwise say N.
399 depends on (FB = y) && APOLLO
401 select FB_CFB_FILLRECT
402 select FB_CFB_IMAGEBLIT
406 depends on (FB = y) && Q40
408 select FB_CFB_FILLRECT
409 select FB_CFB_COPYAREA
410 select FB_CFB_IMAGEBLIT
413 tristate "Amiga native chipset support"
414 depends on FB && AMIGA
416 This is the frame buffer device driver for the builtin graphics
417 chipset found in Amigas.
419 To compile this driver as a module, choose M here: the
420 module will be called amifb.
423 bool "Amiga OCS chipset support"
426 This enables support for the original Agnus and Denise video chips,
427 found in the Amiga 1000 and most A500's and A2000's. If you intend
428 to run Linux on any of these systems, say Y; otherwise say N.
431 bool "Amiga ECS chipset support"
434 This enables support for the Enhanced Chip Set, found in later
435 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
436 you intend to run Linux on any of these systems, say Y; otherwise
440 bool "Amiga AGA chipset support"
443 This enables support for the Advanced Graphics Architecture (also
444 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
445 and CD32. If you intend to run Linux on any of these systems, say Y;
449 bool "Amiga FrameMaster II/Rainbow II support"
450 depends on (FB = y) && ZORRO
451 select FB_CFB_FILLRECT
452 select FB_CFB_COPYAREA
453 select FB_CFB_IMAGEBLIT
455 This is the frame buffer device driver for the Amiga FrameMaster
456 card from BSC (exhibited 1992 but not shipped as a CBM product).
459 tristate "Arc Monochrome LCD board support"
461 select FB_SYS_FILLRECT
462 select FB_SYS_COPYAREA
463 select FB_SYS_IMAGEBLIT
466 This enables support for the Arc Monochrome LCD board. The board
467 is based on the KS-108 lcd controller and is typically a matrix
468 of 2*n chips. This driver was tested with a 128x64 panel. This
469 driver supports it for use with x86 SBCs through a 16 bit GPIO
470 interface (8 bit data, 8 bit control). If you anticipate using
471 this driver, say Y or M; otherwise say N. You must specify the
472 GPIO IO address to be used for setting control and data.
475 bool "Atari native chipset support"
476 depends on (FB = y) && ATARI
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
481 This is the frame buffer device driver for the builtin graphics
482 chipset found in Ataris.
485 bool "Open Firmware frame buffer device support"
486 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
492 Say Y if you want support with Open Firmware for your graphics
496 bool "Apple \"control\" display support"
497 depends on (FB = y) && PPC_PMAC && PPC32
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
503 This driver supports a frame buffer for the graphics adapter in the
504 Power Macintosh 7300 and others.
507 bool "Apple \"platinum\" display support"
508 depends on (FB = y) && PPC_PMAC && PPC32
509 select FB_CFB_FILLRECT
510 select FB_CFB_COPYAREA
511 select FB_CFB_IMAGEBLIT
514 This driver supports a frame buffer for the "platinum" graphics
515 adapter in some Power Macintoshes.
518 bool "Apple \"valkyrie\" display support"
519 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
520 select FB_CFB_FILLRECT
521 select FB_CFB_COPYAREA
522 select FB_CFB_IMAGEBLIT
525 This driver supports a frame buffer for the "valkyrie" graphics
526 adapter in some Power Macintoshes.
529 bool "Chips 65550 display support"
530 depends on (FB = y) && PPC32 && PCI
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
535 This is the frame buffer device driver for the Chips & Technologies
536 65550 graphics chip in PowerBooks.
539 bool "Asiliant (Chips) 69000 display support"
540 depends on (FB = y) && PCI
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
545 This is the frame buffer device driver for the Asiliant 69030 chipset
548 bool "IMS Twin Turbo display support"
549 depends on (FB = y) && PCI
550 select FB_CFB_IMAGEBLIT
551 select FB_MACMODES if PPC
553 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
554 many Macintosh and compatible computers.
557 tristate "VGA 16-color graphics support"
558 depends on FB && (X86 || PPC)
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
563 select FONT_8x16 if FRAMEBUFFER_CONSOLE
565 This is the frame buffer device driver for VGA 16 color graphic
566 cards. Say Y if you have such a card.
568 To compile this driver as a module, choose M here: the
569 module will be called vga16fb.
571 config FB_BF54X_LQ043
572 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
573 depends on FB && (BF54x)
574 select FB_CFB_FILLRECT
575 select FB_CFB_COPYAREA
576 select FB_CFB_IMAGEBLIT
578 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
580 config FB_BFIN_T350MCQB
581 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
582 depends on FB && BLACKFIN
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
588 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
589 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
590 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
594 tristate "HP STI frame buffer device support"
595 depends on FB && PARISC
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
601 STI refers to the HP "Standard Text Interface" which is a set of
602 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
603 Enabling this option will implement the linux framebuffer device
604 using calls to the STI BIOS routines for initialisation.
606 If you enable this option, you will get a planar framebuffer device
607 /dev/fb which will work on the most common HP graphic cards of the
608 NGLE family, including the artist chips (in the 7xx and Bxxx series),
609 HCRX, HCRX24, CRX, CRX24 and VisEG series.
611 It is safe to enable this option, so you should probably say "Y".
614 bool "Generic Macintosh display support"
615 depends on (FB = y) && MAC
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
621 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
624 depends on (FB = y) && HP300
625 select FB_CFB_FILLRECT
626 select FB_CFB_IMAGEBLIT
630 tristate "TGA/SFB+ framebuffer support"
631 depends on FB && (ALPHA || TC)
632 select FB_CFB_FILLRECT
633 select FB_CFB_COPYAREA
634 select FB_CFB_IMAGEBLIT
637 This is the frame buffer device driver for generic TGA and SFB+
638 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
639 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
640 TURBOchannel cards, also known as PMAGD-A, -B and -C.
642 Due to hardware limitations ZLX-E2 and E3 cards are not supported
643 for DECstation 5000/200 systems. Additionally due to firmware
644 limitations these cards may cause troubles with booting DECstation
645 5000/240 and /260 systems, but are fully supported under Linux if
646 you manage to get it going. ;-)
648 Say Y if you have one of those.
651 tristate "Userspace VESA VGA graphics support"
652 depends on FB && CONNECTOR
653 select FB_CFB_FILLRECT
654 select FB_CFB_COPYAREA
655 select FB_CFB_IMAGEBLIT
656 select FB_MODE_HELPERS
658 This is the frame buffer driver for generic VBE 2.0 compliant
659 graphic cards. It can also take advantage of VBE 3.0 features,
660 such as refresh rate adjustment.
662 This driver generally provides more features than vesafb but
663 requires a userspace helper application called 'v86d'. See
664 <file:Documentation/fb/uvesafb.txt> for more information.
669 bool "VESA VGA graphics support"
670 depends on (FB = y) && X86
671 select FB_CFB_FILLRECT
672 select FB_CFB_COPYAREA
673 select FB_CFB_IMAGEBLIT
676 This is the frame buffer device driver for generic VESA 2.0
677 compliant graphic cards. The older VESA 1.2 cards are not supported.
678 You will get a boot time penguin logo at no additional cost. Please
679 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
682 bool "EFI-based Framebuffer Support"
683 depends on (FB = y) && X86
684 select FB_CFB_FILLRECT
685 select FB_CFB_COPYAREA
686 select FB_CFB_IMAGEBLIT
688 This is the EFI frame buffer device driver. If the firmware on
689 your platform is UEFI2.0, select Y to add support for
690 Graphics Output Protocol for early console messages to appear.
693 bool "Intel-based Macintosh Framebuffer Support"
694 depends on (FB = y) && X86 && EFI
695 select FB_CFB_FILLRECT
696 select FB_CFB_COPYAREA
697 select FB_CFB_IMAGEBLIT
699 This is the frame buffer device driver for the Intel-based Macintosh
702 tristate "Hecuba board support"
703 depends on FB && X86 && MMU
704 select FB_SYS_FILLRECT
705 select FB_SYS_COPYAREA
706 select FB_SYS_IMAGEBLIT
708 select FB_DEFERRED_IO
710 This enables support for the Hecuba board. This driver was tested
711 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
712 interface (8 bit data, 4 bit control). If you anticipate using
713 this driver, say Y or M; otherwise say N. You must specify the
714 GPIO IO address to be used for setting control and data.
717 tristate "Hercules mono graphics support"
719 select FB_CFB_FILLRECT
720 select FB_CFB_COPYAREA
721 select FB_CFB_IMAGEBLIT
723 Say Y here if you have a Hercules mono graphics card.
725 To compile this driver as a module, choose M here: the
726 module will be called hgafb.
728 As this card technology is 15 years old, most people will answer N
732 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
733 depends on FB_HGA && EXPERIMENTAL
735 This will compile the Hercules mono graphics with
736 acceleration functions.
739 tristate "SGI Visual Workstation framebuffer support"
740 depends on FB && X86_VISWS
741 select FB_CFB_FILLRECT
742 select FB_CFB_COPYAREA
743 select FB_CFB_IMAGEBLIT
745 SGI Visual Workstation support for framebuffer graphics.
748 bool "SGI Graphics Backend frame buffer support"
749 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
750 select FB_CFB_FILLRECT
751 select FB_CFB_COPYAREA
752 select FB_CFB_IMAGEBLIT
754 This is the frame buffer device driver for SGI Graphics Backend.
755 This chip is used in SGI O2 and Visual Workstation 320/540.
758 int "Video memory size in MB"
762 This is the amount of memory reserved for the framebuffer,
763 which can be any value between 1MB and 8MB.
766 bool "SBUS and UPA framebuffers"
767 depends on (FB = y) && SPARC
769 Say Y if you want support for SBUS or UPA based frame buffer device.
773 depends on (FB = y) && (SPARC && FB_SBUS)
774 select FB_CFB_FILLRECT
775 select FB_CFB_COPYAREA
776 select FB_CFB_IMAGEBLIT
778 This is the frame buffer device driver for the BWtwo frame buffer.
781 bool "CGthree support"
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 CGthree frame buffer.
790 bool "CGsix (GX,TurboGX) support"
791 depends on (FB = y) && (SPARC && FB_SBUS)
792 select FB_CFB_COPYAREA
793 select FB_CFB_IMAGEBLIT
795 This is the frame buffer device driver for the CGsix (GX, TurboGX)
799 bool "Creator/Creator3D/Elite3D support"
800 depends on FB_SBUS && SPARC64
801 select FB_CFB_COPYAREA
802 select FB_CFB_IMAGEBLIT
804 This is the frame buffer device driver for the Creator, Creator3D,
805 and Elite3D graphics boards.
808 bool "TCX (SS4/SS5 only) support"
810 select FB_CFB_FILLRECT
811 select FB_CFB_COPYAREA
812 select FB_CFB_IMAGEBLIT
814 This is the frame buffer device driver for the TCX 24/8bit frame
818 bool "CGfourteen (SX) support"
820 select FB_CFB_FILLRECT
821 select FB_CFB_COPYAREA
822 select FB_CFB_IMAGEBLIT
824 This is the frame buffer device driver for the CGfourteen frame
825 buffer on Desktop SPARCsystems with the SX graphics option.
828 bool "P9100 (Sparcbook 3 only) support"
830 select FB_CFB_FILLRECT
831 select FB_CFB_COPYAREA
832 select FB_CFB_IMAGEBLIT
834 This is the frame buffer device driver for the P9100 card
835 supported on Sparcbook 3 machines.
838 bool "Leo (ZX) support"
840 select FB_CFB_FILLRECT
841 select FB_CFB_COPYAREA
842 select FB_CFB_IMAGEBLIT
844 This is the frame buffer device driver for the SBUS-based Sun ZX
845 (leo) frame buffer cards.
848 bool "IGA 168x display support"
849 depends on (FB = y) && SPARC32
850 select FB_CFB_FILLRECT
851 select FB_CFB_COPYAREA
852 select FB_CFB_IMAGEBLIT
854 This is the framebuffer device for the INTERGRAPHICS 1680 and
855 successor frame buffer cards.
858 bool "Sun XVR-500 3DLABS Wildcat support"
859 depends on (FB = y) && PCI && SPARC64
860 select FB_CFB_FILLRECT
861 select FB_CFB_COPYAREA
862 select FB_CFB_IMAGEBLIT
864 This is the framebuffer device for the Sun XVR-500 and similar
865 graphics cards based upon the 3DLABS Wildcat chipset. The driver
866 only works on sparc64 systems where the system firmware has
867 mostly initialized the card already. It is treated as a
868 completely dumb framebuffer device.
871 bool "Sun XVR-2500 3DLABS Wildcat support"
872 depends on (FB = y) && PCI && SPARC64
873 select FB_CFB_FILLRECT
874 select FB_CFB_COPYAREA
875 select FB_CFB_IMAGEBLIT
877 This is the framebuffer device for the Sun XVR-2500 and similar
878 graphics cards based upon the 3DLABS Wildcat chipset. The driver
879 only works on sparc64 systems where the system firmware has
880 mostly initialized the card already. It is treated as a
881 completely dumb framebuffer device.
884 tristate "NEC PowerVR 2 display support"
885 depends on FB && SH_DREAMCAST
886 select FB_CFB_FILLRECT
887 select FB_CFB_COPYAREA
888 select FB_CFB_IMAGEBLIT
890 Say Y here if you have a PowerVR 2 card in your box. If you plan to
891 run linux on your Dreamcast, you will have to say Y here.
892 This driver may or may not work on other PowerVR 2 cards, but is
893 totally untested. Use at your own risk. If unsure, say N.
895 To compile this driver as a module, choose M here: the
896 module will be called pvr2fb.
898 You can pass several parameters to the driver at boot time or at
899 module load time. The parameters look like "video=pvr2:XXX", where
900 the meaning of XXX can be found at the end of the main source file
901 (<file:drivers/video/pvr2fb.c>). Please see the file
902 <file:Documentation/fb/pvr2fb.txt>.
905 bool "Epson 1355 framebuffer support"
906 depends on (FB = y) && ARCH_CEIVA
907 select FB_CFB_FILLRECT
908 select FB_CFB_COPYAREA
909 select FB_CFB_IMAGEBLIT
911 Build in support for the SED1355 Epson Research Embedded RAMDAC
912 LCD/CRT Controller (since redesignated as the S1D13505) as a
913 framebuffer. Product specs at
914 <http://www.erd.epson.com/vdc/html/products.htm>.
917 tristate "Epson S1D13XXX framebuffer support"
919 select FB_CFB_FILLRECT
920 select FB_CFB_COPYAREA
921 select FB_CFB_IMAGEBLIT
923 Support for S1D13XXX framebuffer device family (currently only
924 working with S1D13806). Product specs at
925 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
928 tristate "AT91/AT32 LCD Controller support"
929 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
930 select FB_CFB_FILLRECT
931 select FB_CFB_COPYAREA
932 select FB_CFB_IMAGEBLIT
934 This enables support for the AT91/AT32 LCD Controller.
937 bool "Frame Buffer in internal SRAM"
938 depends on FB_ATMEL && ARCH_AT91SAM9261
940 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
941 to let frame buffer in external SDRAM.
944 bool "Use a STN display with AT91/AT32 LCD Controller"
945 depends on FB_ATMEL && MACH_AT91SAM9261EK
948 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
949 Controller. Say N if you want to connect a TFT.
954 tristate "nVidia Framebuffer Support"
956 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
957 select FB_MODE_HELPERS
958 select FB_CFB_FILLRECT
959 select FB_CFB_COPYAREA
960 select FB_CFB_IMAGEBLIT
964 This driver supports graphics boards with the nVidia chips, TNT
965 and newer. For very old chipsets, such as the RIVA128, then use
967 Say Y if you have such a graphics board.
969 To compile this driver as a module, choose M here: the
970 module will be called nvidiafb.
973 bool "Enable DDC Support"
977 This enables I2C support for nVidia Chipsets. This is used
978 only for getting EDID information from the attached display
979 allowing for robust video mode handling and switching.
981 Because fbdev-2.6 requires that drivers must be able to
982 independently validate video mode parameters, you should say Y
985 config FB_NVIDIA_DEBUG
986 bool "Lots of debug output"
990 Say Y here if you want the nVidia driver to output all sorts
991 of debugging information to provide to the maintainer when
992 something goes wrong.
994 config FB_NVIDIA_BACKLIGHT
995 bool "Support for backlight control"
999 Say Y here if you want to control the backlight of your display.
1002 tristate "nVidia Riva support"
1003 depends on FB && PCI
1004 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1005 select FB_MODE_HELPERS
1006 select FB_CFB_FILLRECT
1007 select FB_CFB_COPYAREA
1008 select FB_CFB_IMAGEBLIT
1012 This driver supports graphics boards with the nVidia Riva/Geforce
1014 Say Y if you have such a graphics board.
1016 To compile this driver as a module, choose M here: the
1017 module will be called rivafb.
1020 bool "Enable DDC Support"
1024 This enables I2C support for nVidia Chipsets. This is used
1025 only for getting EDID information from the attached display
1026 allowing for robust video mode handling and switching.
1028 Because fbdev-2.6 requires that drivers must be able to
1029 independently validate video mode parameters, you should say Y
1032 config FB_RIVA_DEBUG
1033 bool "Lots of debug output"
1037 Say Y here if you want the Riva driver to output all sorts
1038 of debugging information to provide to the maintainer when
1039 something goes wrong.
1041 config FB_RIVA_BACKLIGHT
1042 bool "Support for backlight control"
1046 Say Y here if you want to control the backlight of your display.
1049 tristate "Intel 810/815 support (EXPERIMENTAL)"
1050 depends on FB && EXPERIMENTAL && PCI && X86_32
1053 select FB_MODE_HELPERS
1054 select FB_CFB_FILLRECT
1055 select FB_CFB_COPYAREA
1056 select FB_CFB_IMAGEBLIT
1059 This driver supports the on-board graphics built in to the Intel 810
1060 and 815 chipsets. Say Y if you have and plan to use such a board.
1062 To compile this driver as a module, choose M here: the
1063 module will be called i810fb.
1065 For more information, please read
1066 <file:Documentation/fb/intel810.txt>
1069 bool "use VESA Generalized Timing Formula"
1072 If you say Y, then the VESA standard, Generalized Timing Formula
1073 or GTF, will be used to calculate the required video timing values
1074 per video mode. Since the GTF allows nondiscrete timings
1075 (nondiscrete being a range of values as opposed to discrete being a
1076 set of values), you'll be able to use any combination of horizontal
1077 and vertical resolutions, and vertical refresh rates without having
1078 to specify your own timing parameters. This is especially useful
1079 to maximize the performance of an aging display, or if you just
1080 have a display with nonstandard dimensions. A VESA compliant
1081 monitor is recommended, but can still work with non-compliant ones.
1082 If you need or want this, then select this option. The timings may
1083 not be compliant with Intel's recommended values. Use at your own
1086 If you say N, the driver will revert to discrete video timings
1087 using a set recommended by Intel in their documentation.
1092 bool "Enable DDC Support"
1093 depends on FB_I810 && FB_I810_GTF
1098 tristate "Intel LE80578 (Vermilion) support"
1099 depends on FB && PCI && X86
1100 select FB_MODE_HELPERS
1101 select FB_CFB_FILLRECT
1102 select FB_CFB_COPYAREA
1103 select FB_CFB_IMAGEBLIT
1105 This driver supports the LE80578 (Vermilion Range) chipset
1107 config FB_CARILLO_RANCH
1108 tristate "Intel Carillo Ranch support"
1109 depends on FB_LE80578 && FB && PCI && X86
1111 This driver supports the LE80578 (Carillo Ranch) board
1114 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
1115 depends on FB && EXPERIMENTAL && PCI && X86
1118 select FB_MODE_HELPERS
1119 select FB_CFB_FILLRECT
1120 select FB_CFB_COPYAREA
1121 select FB_CFB_IMAGEBLIT
1123 This driver supports the on-board graphics built in to the Intel
1124 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
1125 Say Y if you have and plan to use such a board.
1127 If you say Y here and want DDC/I2C support you must first say Y to
1128 "I2C support" and "I2C bit-banging support" in the character devices
1131 If you say M here then "I2C support" and "I2C bit-banging support"
1132 can be build either as modules or built-in.
1134 To compile this driver as a module, choose M here: the
1135 module will be called intelfb.
1137 For more information, please read <file:Documentation/fb/intelfb.txt>
1139 config FB_INTEL_DEBUG
1140 bool "Intel driver Debug Messages"
1143 Say Y here if you want the Intel driver to output all sorts
1144 of debugging information to provide to the maintainer when
1145 something goes wrong.
1148 bool "DDC/I2C for Intel framebuffer support"
1153 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1156 tristate "Matrox acceleration"
1157 depends on FB && PCI
1158 select FB_CFB_FILLRECT
1159 select FB_CFB_COPYAREA
1160 select FB_CFB_IMAGEBLIT
1161 select FB_TILEBLITTING
1162 select FB_MACMODES if PPC_PMAC
1164 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1165 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1166 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1167 Matrox G400, G450 or G550 card in your box.
1169 To compile this driver as a module, choose M here: the
1170 module will be called matroxfb.
1172 You can pass several parameters to the driver at boot time or at
1173 module load time. The parameters look like "video=matrox:XXX", and
1174 are described in <file:Documentation/fb/matroxfb.txt>.
1176 config FB_MATROX_MILLENIUM
1177 bool "Millennium I/II support"
1178 depends on FB_MATROX
1180 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1181 video card. If you select "Advanced lowlevel driver options" below,
1182 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1183 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1184 also use font widths different from 8.
1186 config FB_MATROX_MYSTIQUE
1187 bool "Mystique support"
1188 depends on FB_MATROX
1190 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1191 video card. If you select "Advanced lowlevel driver options" below,
1192 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1193 packed pixel and 32 bpp packed pixel. You can also use font widths
1197 bool "G100/G200/G400/G450/G550 support"
1198 depends on FB_MATROX
1200 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1201 video card. If you select "Advanced lowlevel driver options", you
1202 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1203 pixel and 32 bpp packed pixel. You can also use font widths
1206 If you need support for G400 secondary head, you must first say Y to
1207 "I2C support" in the character devices section, and then to
1208 "Matrox I2C support" and "G400 second head support" here in the
1209 framebuffer section. G450/G550 secondary head and digital output
1210 are supported without additional modules.
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 If you say Y here and want DDC/I2C support you must first say Y to
1310 "I2C support" and "I2C bit-banging support" in the character devices
1313 If you say M here then "I2C support" and "I2C bit-banging support"
1314 can be build either as modules or built-in.
1316 There is a product page at
1317 http://apps.ati.com/ATIcompare/
1319 config FB_RADEON_I2C
1320 bool "DDC/I2C for ATI Radeon support"
1321 depends on FB_RADEON
1325 Say Y here if you want DDC/I2C support for your Radeon board.
1327 config FB_RADEON_BACKLIGHT
1328 bool "Support for backlight control"
1329 depends on FB_RADEON
1332 Say Y here if you want to control the backlight of your display.
1334 config FB_RADEON_DEBUG
1335 bool "Lots of debug output from Radeon driver"
1336 depends on FB_RADEON
1339 Say Y here if you want the Radeon driver to output all sorts
1340 of debugging information to provide to the maintainer when
1341 something goes wrong.
1344 tristate "ATI Rage128 display support"
1345 depends on FB && PCI
1346 select FB_CFB_FILLRECT
1347 select FB_CFB_COPYAREA
1348 select FB_CFB_IMAGEBLIT
1349 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1350 select FB_MACMODES if PPC_PMAC
1352 This driver supports graphics boards with the ATI Rage128 chips.
1353 Say Y if you have such a graphics board and read
1354 <file:Documentation/fb/aty128fb.txt>.
1356 To compile this driver as a module, choose M here: the
1357 module will be called aty128fb.
1359 config FB_ATY128_BACKLIGHT
1360 bool "Support for backlight control"
1361 depends on FB_ATY128
1364 Say Y here if you want to control the backlight of your display.
1367 tristate "ATI Mach64 display support" if PCI || ATARI
1368 depends on FB && !SPARC32
1369 select FB_CFB_FILLRECT
1370 select FB_CFB_COPYAREA
1371 select FB_CFB_IMAGEBLIT
1372 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1373 select FB_MACMODES if PPC
1375 This driver supports graphics boards with the ATI Mach64 chips.
1376 Say Y if you have such a graphics board.
1378 To compile this driver as a module, choose M here: the
1379 module will be called atyfb.
1382 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1383 depends on PCI && FB_ATY
1384 default y if SPARC64 && PCI
1386 Say Y here to support use of ATI's 64-bit Rage boards (or other
1387 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1388 framebuffer device. The ATI product support page for these boards
1389 is at <http://support.ati.com/products/pc/mach64/>.
1391 config FB_ATY_GENERIC_LCD
1392 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1393 depends on FB_ATY_CT
1395 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1396 Rage XC, or Rage XL chipset.
1399 bool "Mach64 GX support" if PCI
1403 Say Y here to support use of the ATI Mach64 Graphics Expression
1404 board (or other boards based on the Mach64 GX chipset) as a
1405 framebuffer device. The ATI product support page for these boards
1407 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1409 config FB_ATY_BACKLIGHT
1410 bool "Support for backlight control"
1414 Say Y here if you want to control the backlight of your display.
1417 tristate "S3 Trio/Virge support"
1418 depends on FB && PCI
1419 select FB_CFB_FILLRECT
1420 select FB_CFB_COPYAREA
1421 select FB_CFB_IMAGEBLIT
1422 select FB_TILEBLITTING
1425 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1427 Driver for graphics boards with S3 Trio / S3 Virge chip.
1430 tristate "S3 Savage support"
1431 depends on FB && PCI && EXPERIMENTAL
1432 select FB_MODE_HELPERS
1433 select FB_CFB_FILLRECT
1434 select FB_CFB_COPYAREA
1435 select FB_CFB_IMAGEBLIT
1438 This driver supports notebooks and computers with S3 Savage PCI/AGP
1441 Say Y if you have such a graphics card.
1443 To compile this driver as a module, choose M here; the module
1444 will be called savagefb.
1446 config FB_SAVAGE_I2C
1447 bool "Enable DDC2 Support"
1448 depends on FB_SAVAGE
1451 This enables I2C support for S3 Savage Chipsets. This is used
1452 only for getting EDID information from the attached display
1453 allowing for robust video mode handling and switching.
1455 Because fbdev-2.6 requires that drivers must be able to
1456 independently validate video mode parameters, you should say Y
1459 config FB_SAVAGE_ACCEL
1460 bool "Enable Console Acceleration"
1461 depends on FB_SAVAGE
1464 This option will compile in console acceleration support. If
1465 the resulting framebuffer console has bothersome glitches, then
1469 tristate "SiS/XGI display support"
1470 depends on FB && PCI
1471 select FB_CFB_FILLRECT
1472 select FB_CFB_COPYAREA
1473 select FB_CFB_IMAGEBLIT
1475 This is the frame buffer device driver for the SiS 300, 315, 330
1476 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1477 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1479 To compile this driver as a module, choose M here; the module
1480 will be called sisfb.
1483 bool "SiS 300 series support"
1486 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1489 bool "SiS 315/330/340 series and XGI support"
1492 Say Y here to support use of the SiS 315, 330 and 340 series
1493 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1494 as XGI V3XT, V5, V8 and Z7.
1497 tristate "NeoMagic display support"
1498 depends on FB && PCI
1499 select FB_MODE_HELPERS
1500 select FB_CFB_FILLRECT
1501 select FB_CFB_COPYAREA
1502 select FB_CFB_IMAGEBLIT
1505 This driver supports notebooks with NeoMagic PCI chips.
1506 Say Y if you have such a graphics card.
1508 To compile this driver as a module, choose M here: the
1509 module will be called neofb.
1512 tristate "IMG Kyro support"
1513 depends on FB && PCI
1514 select FB_CFB_FILLRECT
1515 select FB_CFB_COPYAREA
1516 select FB_CFB_IMAGEBLIT
1518 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1521 To compile this driver as a module, choose M here: the
1522 module will be called kyrofb.
1525 tristate "3Dfx Banshee/Voodoo3 display support"
1526 depends on FB && PCI
1527 select FB_CFB_IMAGEBLIT
1528 select FB_CFB_FILLRECT
1529 select FB_CFB_COPYAREA
1531 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1532 chips. Say Y if you have such a graphics board.
1534 To compile this driver as a module, choose M here: the
1535 module will be called tdfxfb.
1537 config FB_3DFX_ACCEL
1538 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1539 depends on FB_3DFX && EXPERIMENTAL
1541 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1542 with acceleration functions.
1546 tristate "3Dfx Voodoo Graphics (sst1) support"
1547 depends on FB && PCI
1548 select FB_CFB_FILLRECT
1549 select FB_CFB_COPYAREA
1550 select FB_CFB_IMAGEBLIT
1552 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1553 Voodoo2 (cvg) based graphics card.
1555 To compile this driver as a module, choose M here: the
1556 module will be called sstfb.
1558 WARNING: Do not use any application that uses the 3D engine
1559 (namely glide) while using this driver.
1560 Please read the <file:Documentation/fb/sstfb.txt> for supported
1561 options and other important info support.
1564 tristate "VIA VT8623 support"
1565 depends on FB && PCI
1566 select FB_CFB_FILLRECT
1567 select FB_CFB_COPYAREA
1568 select FB_CFB_IMAGEBLIT
1569 select FB_TILEBLITTING
1572 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1574 Driver for CastleRock integrated graphics core in the
1575 VIA VT8623 [Apollo CLE266] chipset.
1578 tristate "Cyberblade/i1 support"
1579 depends on FB && PCI && X86_32 && !64BIT
1580 select FB_CFB_IMAGEBLIT
1583 This driver is supposed to support the Trident Cyberblade/i1
1584 graphics core integrated in the VIA VT8601A North Bridge,
1585 also known as VIA Apollo PLE133.
1588 - Developed, tested and working on EPIA 5000 and EPIA 800.
1589 - Does work reliable on all systems with CRT/LCD connected to
1591 - Should work on systems that do use the internal LCD port, but
1592 this is absolutely not tested.
1594 Character imageblit, copyarea and rectangle fill are hw accelerated,
1595 ypan scrolling is used by default.
1597 Please do read <file:Documentation/fb/cyblafb/*>.
1599 To compile this driver as a module, choose M here: the
1600 module will be called cyblafb.
1603 tristate "Trident support"
1604 depends on FB && PCI
1605 select FB_CFB_FILLRECT
1606 select FB_CFB_COPYAREA
1607 select FB_CFB_IMAGEBLIT
1609 This driver is supposed to support graphics boards with the
1610 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1611 but also on some motherboards. For more information, read
1612 <file:Documentation/fb/tridentfb.txt>
1614 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1617 Say Y if you have such a graphics board.
1620 To compile this driver as a module, choose M here: the
1621 module will be called tridentfb.
1623 config FB_TRIDENT_ACCEL
1624 bool "Trident Acceleration functions (EXPERIMENTAL)"
1625 depends on FB_TRIDENT && EXPERIMENTAL
1627 This will compile the Trident frame buffer device with
1628 acceleration functions.
1631 tristate "ARK 2000PV support"
1632 depends on FB && PCI
1633 select FB_CFB_FILLRECT
1634 select FB_CFB_COPYAREA
1635 select FB_CFB_IMAGEBLIT
1636 select FB_TILEBLITTING
1639 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1641 Driver for PCI graphics boards with ARK 2000PV chip
1642 and ICS 5342 RAMDAC.
1645 tristate "Permedia3 support (EXPERIMENTAL)"
1646 depends on FB && PCI && EXPERIMENTAL
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 3DLabs Permedia3
1652 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1653 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1654 and maybe other boards.
1657 bool "Au1100 LCD Driver"
1658 depends on (FB = y) && MIPS && SOC_AU1100
1659 select FB_CFB_FILLRECT
1660 select FB_CFB_COPYAREA
1661 select FB_CFB_IMAGEBLIT
1663 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1664 various panels and CRTs by passing in kernel cmd line option
1665 au1100fb:panel=<name>.
1668 bool "Au1200 LCD Driver"
1669 depends on (FB = y) && MIPS && SOC_AU1200
1670 select FB_CFB_FILLRECT
1671 select FB_CFB_COPYAREA
1672 select FB_CFB_IMAGEBLIT
1674 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1675 various panels and CRTs by passing in kernel cmd line option
1676 au1200fb:panel=<name>.
1678 source "drivers/video/geode/Kconfig"
1681 tristate "HD64461 Frame Buffer support"
1682 depends on FB && HD64461
1683 select FB_CFB_FILLRECT
1684 select FB_CFB_COPYAREA
1685 select FB_CFB_IMAGEBLIT
1687 This is the frame buffer device driver for the Hitachi HD64461 LCD
1691 bool "PMAG-AA TURBOchannel framebuffer support"
1692 depends on (FB = y) && TC
1693 select FB_CFB_FILLRECT
1694 select FB_CFB_COPYAREA
1695 select FB_CFB_IMAGEBLIT
1697 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1698 used mainly in the MIPS-based DECstation series.
1701 tristate "PMAG-BA TURBOchannel framebuffer support"
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1708 used mainly in the MIPS-based DECstation series.
1711 tristate "PMAGB-B TURBOchannel framebuffer support"
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1718 in the MIPS-based DECstation series. The card is currently only
1719 supported in 1280x1024x8 mode.
1722 bool "Maxine (Personal DECstation) onboard framebuffer support"
1723 depends on (FB = y) && MACH_DECSTATION
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1728 Support for the onboard framebuffer (1024x768x8) in the Personal
1729 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1733 bool "G364 frame buffer support"
1734 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1735 select FB_CFB_FILLRECT
1736 select FB_CFB_COPYAREA
1737 select FB_CFB_IMAGEBLIT
1739 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1740 Olivetti M700-10 systems.
1743 bool "Motorola 68328 native frame buffer support"
1744 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1745 select FB_CFB_FILLRECT
1746 select FB_CFB_COPYAREA
1747 select FB_CFB_IMAGEBLIT
1749 Say Y here if you want to support the built-in frame buffer of
1750 the Motorola 68328 CPU family.
1753 tristate "PXA LCD framebuffer support"
1754 depends on FB && ARCH_PXA
1755 select FB_CFB_FILLRECT
1756 select FB_CFB_COPYAREA
1757 select FB_CFB_IMAGEBLIT
1759 Frame buffer driver for the built-in LCD controller in the Intel
1762 This driver is also available as a module ( = code which can be
1763 inserted and removed from the running kernel whenever you want). The
1764 module will be called pxafb. If you want to compile it as a module,
1765 say M here and read <file:Documentation/kbuild/modules.txt>.
1769 config FB_PXA_PARAMETERS
1770 bool "PXA LCD command line parameters"
1774 Enable the use of kernel command line or module parameters
1775 to configure the physical properties of the LCD panel when
1776 using the PXA LCD driver.
1778 This option allows you to override the panel parameters
1779 supplied by the platform in order to support multiple
1780 different models of flatpanel. If you will only be using a
1781 single model of flatpanel then you can safely leave this
1784 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1787 tristate "2700G LCD framebuffer support"
1788 depends on FB && ARCH_PXA
1789 select FB_CFB_FILLRECT
1790 select FB_CFB_COPYAREA
1791 select FB_CFB_IMAGEBLIT
1793 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1797 bool "Enable debugging info via debugfs"
1798 depends on FB_MBX && DEBUG_FS
1801 Enable this if you want debugging information using the debug
1802 filesystem (debugfs)
1807 tristate "Freescale DIU framebuffer support"
1808 depends on FB && FSL_SOC
1809 select FB_CFB_FILLRECT
1810 select FB_CFB_COPYAREA
1811 select FB_CFB_IMAGEBLIT
1812 select PPC_LIB_RHEAP
1814 Framebuffer driver for the Freescale SoC DIU
1817 tristate "W100 frame buffer support"
1818 depends on FB && PXA_SHARPSL
1819 select FB_CFB_FILLRECT
1820 select FB_CFB_COPYAREA
1821 select FB_CFB_IMAGEBLIT
1823 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1825 This driver is also available as a module ( = code which can be
1826 inserted and removed from the running kernel whenever you want). The
1827 module will be called w100fb. If you want to compile it as a module,
1828 say M here and read <file:Documentation/kbuild/modules.txt>.
1833 tristate "S3C2410 LCD framebuffer support"
1834 depends on FB && ARCH_S3C2410
1835 select FB_CFB_FILLRECT
1836 select FB_CFB_COPYAREA
1837 select FB_CFB_IMAGEBLIT
1839 Frame buffer driver for the built-in LCD controller in the Samsung
1842 This driver is also available as a module ( = code which can be
1843 inserted and removed from the running kernel whenever you want). The
1844 module will be called s3c2410fb. If you want to compile it as a module,
1845 say M here and read <file:Documentation/kbuild/modules.txt>.
1848 config FB_S3C2410_DEBUG
1849 bool "S3C2410 lcd debug messages"
1850 depends on FB_S3C2410
1852 Turn on debugging messages. Note that you can set/unset at run time
1856 tristate "Silicon Motion SM501 framebuffer support"
1857 depends on FB && MFD_SM501
1858 select FB_CFB_FILLRECT
1859 select FB_CFB_COPYAREA
1860 select FB_CFB_IMAGEBLIT
1862 Frame buffer driver for the CRT and LCD controllers in the Silicon
1865 This driver is also available as a module ( = code which can be
1866 inserted and removed from the running kernel whenever you want). The
1867 module will be called sm501fb. If you want to compile it as a module,
1868 say M here and read <file:Documentation/kbuild/modules.txt>.
1873 config FB_PNX4008_DUM
1874 tristate "Display Update Module support on Philips PNX4008 board"
1875 depends on FB && ARCH_PNX4008
1877 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1879 config FB_PNX4008_DUM_RGB
1880 tristate "RGB Framebuffer support on Philips PNX4008 board"
1881 depends on FB_PNX4008_DUM
1882 select FB_CFB_FILLRECT
1883 select FB_CFB_COPYAREA
1884 select FB_CFB_IMAGEBLIT
1886 Say Y here to enable support for PNX4008 RGB Framebuffer
1888 config FB_IBM_GXT4500
1889 tristate "Framebuffer support for IBM GXT4500P adaptor"
1890 depends on FB && PPC
1891 select FB_CFB_FILLRECT
1892 select FB_CFB_COPYAREA
1893 select FB_CFB_IMAGEBLIT
1895 Say Y here to enable support for the IBM GXT4500P display
1896 adaptor, found on some IBM System P (pSeries) machines.
1899 tristate "PS3 GPU framebuffer driver"
1900 depends on FB && PS3_PS3AV
1901 select FB_SYS_FILLRECT
1902 select FB_SYS_COPYAREA
1903 select FB_SYS_IMAGEBLIT
1905 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1907 Include support for the virtual frame buffer in the PS3 platform.
1909 config FB_PS3_DEFAULT_SIZE_M
1910 int "PS3 default frame buffer size (in MiB)"
1914 This is the default size (in MiB) of the virtual frame buffer in
1916 The default value can be overridden on the kernel command line
1917 using the "ps3fb" option (e.g. "ps3fb=9M");
1920 tristate "Xilinx frame buffer support"
1921 depends on FB && XILINX_VIRTEX
1922 select FB_CFB_FILLRECT
1923 select FB_CFB_COPYAREA
1924 select FB_CFB_IMAGEBLIT
1926 Include support for the Xilinx ML300/ML403 reference design
1927 framebuffer. ML300 carries a 640*480 LCD display on the board,
1928 ML403 uses a standard DB15 VGA connector.
1931 tristate "Metronome display controller support"
1932 depends on FB && ARCH_PXA && MMU
1933 select FB_SYS_FILLRECT
1934 select FB_SYS_COPYAREA
1935 select FB_SYS_IMAGEBLIT
1937 select FB_DEFERRED_IO
1939 This enables support for the Metronome display controller. Tested
1940 with an E-Ink 800x600 display and Gumstix Connex through an AMLCD
1941 interface. Please read <file:Documentation/fb/metronomefb.txt>
1942 for more information.
1945 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1947 select FB_SYS_FILLRECT
1948 select FB_SYS_COPYAREA
1949 select FB_SYS_IMAGEBLIT
1952 This is a `virtual' frame buffer device. It operates on a chunk of
1953 unswappable kernel memory instead of on the memory of a graphics
1954 board. This means you cannot see any output sent to this frame
1955 buffer device, while it does consume precious memory. The main use
1956 of this frame buffer device is testing and debugging the frame
1957 buffer subsystem. Do NOT enable it for normal systems! To protect
1958 the innocent, it has to be enabled explicitly at boot time using the
1959 kernel option `video=vfb:'.
1961 To compile this driver as a module, choose M here: the
1962 module will be called vfb. In order to load it, you must use
1963 the vfb_enable=1 option.
1967 config XEN_FBDEV_FRONTEND
1968 tristate "Xen virtual frame buffer support"
1969 depends on FB && XEN
1970 select FB_SYS_FILLRECT
1971 select FB_SYS_COPYAREA
1972 select FB_SYS_IMAGEBLIT
1974 select FB_DEFERRED_IO
1977 This driver implements the front-end of the Xen virtual
1978 frame buffer driver. It communicates with a back-end
1981 source "drivers/video/omap/Kconfig"
1983 source "drivers/video/backlight/Kconfig"
1984 source "drivers/video/display/Kconfig"
1987 source "drivers/video/console/Kconfig"
1990 if FB || SGI_NEWPORT_CONSOLE
1991 source "drivers/video/logo/Kconfig"