5 menu "Graphics support"
14 source "drivers/char/agp/Kconfig"
16 source "drivers/gpu/vga/Kconfig"
18 source "drivers/gpu/drm/Kconfig"
20 source "drivers/gpu/stub/Kconfig"
26 config VIDEO_OUTPUT_CONTROL
27 tristate "Lowlevel video output switch controls"
29 This framework adds support for low-level control of the video
33 tristate "Support for frame buffer devices"
35 The frame buffer device provides an abstraction for the graphics
36 hardware. It represents the frame buffer of some video hardware and
37 allows application software to access the graphics hardware through
38 a well-defined interface, so the software doesn't need to know
39 anything about the low-level (hardware register) stuff.
41 Frame buffer devices work identically across the different
42 architectures supported by Linux and make the implementation of
43 application programs easier and more portable; at this point, an X
44 server exists which uses the frame buffer device exclusively.
45 On several non-X86 architectures, the frame buffer device is the
46 only way to use the graphics hardware.
48 The device is accessed through special device nodes, usually located
49 in the /dev directory, i.e. /dev/fb*.
51 You need an utility program called fbset to make full use of frame
52 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
53 and the Framebuffer-HOWTO at
54 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
57 Say Y here and to the driver for your graphics board below if you
58 are compiling a kernel for a non-x86 architecture.
60 If you are compiling for the x86 architecture, you can say Y if you
61 want to play with it, but it is not essential. Please note that
62 running graphical applications that directly touch the hardware
63 (e.g. an accelerated X server) and that are not frame buffer
64 device-aware may cause unexpected results. If unsure, say N.
67 bool "Enable firmware EDID"
71 This enables access to the EDID transferred from the firmware.
72 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
73 transfers do not work for your driver and if you are using
74 nvidiafb, i810fb or savagefb.
76 In general, choosing Y for this option is safe. If you
77 experience extremely long delays while booting before you get
78 something on your display, try setting this to N. Matrox cards in
79 combination with certain motherboards and monitors are known to
80 suffer from this problem.
89 config FB_BOOT_VESA_SUPPORT
94 If true, at least one selected framebuffer driver can take advantage
95 of VESA video modes set at an early boot stage via the vga= parameter.
97 config FB_CFB_FILLRECT
102 Include the cfb_fillrect function for generic software rectangle
103 filling. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_COPYAREA
111 Include the cfb_copyarea function for generic software area copying.
112 This is used by drivers that don't provide their own (accelerated)
115 config FB_CFB_IMAGEBLIT
120 Include the cfb_imageblit function for generic software image
121 blitting. This is used by drivers that don't provide their own
122 (accelerated) version.
124 config FB_CFB_REV_PIXELS_IN_BYTE
129 Allow generic frame-buffer functions to work on displays with 1, 2
130 and 4 bits per pixel depths which has opposite order of pixels in
131 byte order to bytes in long order.
133 config FB_SYS_FILLRECT
138 Include the sys_fillrect function for generic software rectangle
139 filling. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 config FB_SYS_COPYAREA
147 Include the sys_copyarea function for generic software area copying.
148 This is used by drivers that don't provide their own (accelerated)
149 version and the framebuffer is in system RAM.
151 config FB_SYS_IMAGEBLIT
156 Include the sys_imageblit function for generic software image
157 blitting. This is used by drivers that don't provide their own
158 (accelerated) version and the framebuffer is in system RAM.
160 menuconfig FB_FOREIGN_ENDIAN
161 bool "Framebuffer foreign endianness support"
164 This menu will let you enable support for the framebuffers with
165 non-native endianness (e.g. Little-Endian framebuffer on a
166 Big-Endian machine). Most probably you don't have such hardware,
167 so it's safe to say "n" here.
170 prompt "Choice endianness support"
171 depends on FB_FOREIGN_ENDIAN
173 config FB_BOTH_ENDIAN
174 bool "Support for Big- and Little-Endian framebuffers"
177 bool "Support for Big-Endian framebuffers only"
179 config FB_LITTLE_ENDIAN
180 bool "Support for Little-Endian framebuffers only"
189 config FB_WMT_GE_ROPS
194 Include functions for accelerated rectangle filling and area
195 copying using WonderMedia Graphics Engine operations.
197 config FB_DEFERRED_IO
204 depends on FB_DEFERRED_IO
211 Common utility functions useful to fbdev drivers of VGA-based
222 select BACKLIGHT_LCD_SUPPORT
223 select BACKLIGHT_CLASS_DEVICE
226 config FB_MODE_HELPERS
227 bool "Enable Video Mode Handling Helpers"
231 This enables functions for handling video modes using the
232 Generalized Timing Formula and the EDID parser. A few drivers rely
233 on this feature such as the radeonfb, rivafb, and the i810fb. If
234 your driver does not take advantage of this feature, choosing Y will
235 just increase the kernel size by about 5K.
237 config FB_TILEBLITTING
238 bool "Enable Tile Blitting Support"
242 This enables tile blitting. Tile blitting is a drawing technique
243 where the screen is divided into rectangular sections (tiles), whereas
244 the standard blitting divides the screen into pixels. Because the
245 default drawing element is a tile, drawing functions will be passed
246 parameters in terms of number of tiles instead of number of pixels.
247 For example, to draw a single character, instead of using bitmaps,
248 an index to an array of bitmaps will be used. To clear or move a
249 rectangular section of a screen, the rectangle will be described in
250 terms of number of tiles in the x- and y-axis.
252 This is particularly important to one driver, matroxfb. If
255 comment "Frame buffer hardware drivers"
259 tristate "Cirrus Logic support"
260 depends on FB && (ZORRO || PCI)
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This enables support for Cirrus Logic GD542x/543x based boards on
266 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
268 If you have a PCI-based system, this enables support for these
269 chips: GD-543x, GD-544x, GD-5480.
271 Please read the file <file:Documentation/fb/cirrusfb.txt>.
273 Say N unless you have such a graphics board or plan to get one
274 before you next recompile the kernel.
277 tristate "Permedia2 support"
278 depends on FB && ((AMIGA && BROKEN) || PCI)
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
283 This is the frame buffer device driver for cards based on
284 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
285 The driver was tested on the following cards:
286 Diamond FireGL 1000 PRO AGP
287 ELSA Gloria Synergy PCI
288 Appian Jeronimo PRO (both heads) PCI
289 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
290 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
291 ASK Graphic Blaster Exxtreme AGP
293 To compile this driver as a module, choose M here: the
294 module will be called pm2fb.
296 config FB_PM2_FIFO_DISCONNECT
297 bool "enable FIFO disconnect feature"
298 depends on FB_PM2 && PCI
300 Support the Permedia2 FIFO disconnect feature.
303 tristate "ARM PrimeCell PL110 support"
304 depends on FB && ARM && ARM_AMBA
305 select FB_CFB_FILLRECT
306 select FB_CFB_COPYAREA
307 select FB_CFB_IMAGEBLIT
309 This framebuffer device driver is for the ARM PrimeCell PL110
310 Colour LCD controller. ARM PrimeCells provide the building
311 blocks for System on a Chip devices.
313 If you want to compile this as a module (=code which can be
314 inserted into and removed from the running kernel), say M
315 here and read <file:Documentation/kbuild/modules.txt>. The module
316 will be called amba-clcd.
320 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
322 default FB_ARMCLCD_SHARP_LQ035Q7DB02
324 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
325 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
327 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
328 color QVGA, HRTFT panel. The LogicPD device includes
329 an integrated HRTFT controller IC.
330 The native resolution is 240x320.
332 config FB_ARMCLCD_SHARP_LQ057Q3DC02
333 bool "LogicPD LCD 5.7\" QVGA"
335 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
336 color QVGA, TFT panel. The LogicPD device includes an
337 The native resolution is 320x240.
339 config FB_ARMCLCD_SHARP_LQ64D343
340 bool "LogicPD LCD 6.4\" VGA"
342 This is an implementation of the Sharp LQ64D343, a 6.4"
343 color VGA, TFT panel. The LogicPD device includes an
344 The native resolution is 640x480.
346 config FB_ARMCLCD_SHARP_LQ10D368
347 bool "LogicPD LCD 10.4\" VGA"
349 This is an implementation of the Sharp LQ10D368, a 10.4"
350 color VGA, TFT panel. The LogicPD device includes an
351 The native resolution is 640x480.
354 config FB_ARMCLCD_SHARP_LQ121S1DG41
355 bool "LogicPD LCD 12.1\" SVGA"
357 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
358 color SVGA, TFT panel. The LogicPD device includes an
359 The native resolution is 800x600.
361 This panel requires a clock rate may be an integer fraction
362 of the base LCDCLK frequency. The driver will select the
363 highest frequency available that is lower than the maximum
364 allowed. The panel may flicker if the clock rate is
365 slower than the recommended minimum.
367 config FB_ARMCLCD_AUO_A070VW01_WIDE
368 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
370 This is an implementation of the AU Optronics, a 7.0"
371 WIDE Color. The native resolution is 234x480.
373 config FB_ARMCLCD_HITACHI
374 bool "Hitachi Wide Screen 800x480"
376 This is an implementation of the Hitachi 800x480.
382 bool "Acorn VIDC support"
383 depends on (FB = y) && ARM && ARCH_ACORN
384 select FB_CFB_FILLRECT
385 select FB_CFB_COPYAREA
386 select FB_CFB_IMAGEBLIT
388 This is the frame buffer device driver for the Acorn VIDC graphics
389 hardware found in Acorn RISC PCs and other ARM-based machines. If
393 bool "CLPS711X LCD support"
394 depends on (FB = y) && ARM && ARCH_CLPS711X
395 select FB_CFB_FILLRECT
396 select FB_CFB_COPYAREA
397 select FB_CFB_IMAGEBLIT
399 Say Y to enable the Framebuffer driver for the CLPS7111 and
403 bool "SA-1100 LCD support"
404 depends on (FB = y) && ARM && ARCH_SA1100
405 select FB_CFB_FILLRECT
406 select FB_CFB_COPYAREA
407 select FB_CFB_IMAGEBLIT
409 This is a framebuffer device for the SA-1100 LCD Controller.
410 See <http://www.linux-fbdev.org/> for information on framebuffer
413 If you plan to use the LCD display with your SA-1100 system, say
417 tristate "Motorola i.MX LCD support"
418 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
419 select FB_CFB_FILLRECT
420 select FB_CFB_COPYAREA
421 select FB_CFB_IMAGEBLIT
424 tristate "CyberPro 2000/2010/5000 support"
425 depends on FB && PCI && (BROKEN || !SPARC64)
426 select FB_CFB_FILLRECT
427 select FB_CFB_COPYAREA
428 select FB_CFB_IMAGEBLIT
430 This enables support for the Integraphics CyberPro 20x0 and 5000
431 VGA chips used in the Rebel.com Netwinder and other machines.
432 Say Y if you have a NetWinder or a graphics card containing this
433 device, otherwise say N.
437 depends on (FB = y) && APOLLO
439 select FB_CFB_FILLRECT
440 select FB_CFB_IMAGEBLIT
444 depends on (FB = y) && Q40
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
451 tristate "Amiga native chipset support"
452 depends on FB && AMIGA
454 This is the frame buffer device driver for the builtin graphics
455 chipset found in Amigas.
457 To compile this driver as a module, choose M here: the
458 module will be called amifb.
461 bool "Amiga OCS chipset support"
464 This enables support for the original Agnus and Denise video chips,
465 found in the Amiga 1000 and most A500's and A2000's. If you intend
466 to run Linux on any of these systems, say Y; otherwise say N.
469 bool "Amiga ECS chipset support"
472 This enables support for the Enhanced Chip Set, found in later
473 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
474 you intend to run Linux on any of these systems, say Y; otherwise
478 bool "Amiga AGA chipset support"
481 This enables support for the Advanced Graphics Architecture (also
482 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
483 and CD32. If you intend to run Linux on any of these systems, say Y;
487 bool "Amiga FrameMaster II/Rainbow II support"
488 depends on (FB = y) && ZORRO
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the Amiga FrameMaster
494 card from BSC (exhibited 1992 but not shipped as a CBM product).
497 tristate "Arc Monochrome LCD board support"
499 select FB_SYS_FILLRECT
500 select FB_SYS_COPYAREA
501 select FB_SYS_IMAGEBLIT
504 This enables support for the Arc Monochrome LCD board. The board
505 is based on the KS-108 lcd controller and is typically a matrix
506 of 2*n chips. This driver was tested with a 128x64 panel. This
507 driver supports it for use with x86 SBCs through a 16 bit GPIO
508 interface (8 bit data, 8 bit control). If you anticipate using
509 this driver, say Y or M; otherwise say N. You must specify the
510 GPIO IO address to be used for setting control and data.
513 bool "Atari native chipset support"
514 depends on (FB = y) && ATARI
515 select FB_CFB_FILLRECT
516 select FB_CFB_COPYAREA
517 select FB_CFB_IMAGEBLIT
519 This is the frame buffer device driver for the builtin graphics
520 chipset found in Ataris.
523 bool "Open Firmware frame buffer device support"
524 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
525 select FB_CFB_FILLRECT
526 select FB_CFB_COPYAREA
527 select FB_CFB_IMAGEBLIT
530 Say Y if you want support with Open Firmware for your graphics
534 bool "Apple \"control\" display support"
535 depends on (FB = y) && PPC_PMAC && PPC32
536 select FB_CFB_FILLRECT
537 select FB_CFB_COPYAREA
538 select FB_CFB_IMAGEBLIT
541 This driver supports a frame buffer for the graphics adapter in the
542 Power Macintosh 7300 and others.
545 bool "Apple \"platinum\" display support"
546 depends on (FB = y) && PPC_PMAC && PPC32
547 select FB_CFB_FILLRECT
548 select FB_CFB_COPYAREA
549 select FB_CFB_IMAGEBLIT
552 This driver supports a frame buffer for the "platinum" graphics
553 adapter in some Power Macintoshes.
556 bool "Apple \"valkyrie\" display support"
557 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
558 select FB_CFB_FILLRECT
559 select FB_CFB_COPYAREA
560 select FB_CFB_IMAGEBLIT
563 This driver supports a frame buffer for the "valkyrie" graphics
564 adapter in some Power Macintoshes.
567 bool "Chips 65550 display support"
568 depends on (FB = y) && PPC32 && PCI
569 select FB_CFB_FILLRECT
570 select FB_CFB_COPYAREA
571 select FB_CFB_IMAGEBLIT
573 This is the frame buffer device driver for the Chips & Technologies
574 65550 graphics chip in PowerBooks.
577 bool "Asiliant (Chips) 69000 display support"
578 depends on (FB = y) && PCI
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
583 This is the frame buffer device driver for the Asiliant 69030 chipset
586 bool "IMS Twin Turbo display support"
587 depends on (FB = y) && PCI
588 select FB_CFB_IMAGEBLIT
589 select FB_MACMODES if PPC
591 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
592 many Macintosh and compatible computers.
595 tristate "VGA 16-color graphics support"
596 depends on FB && (X86 || PPC)
597 select FB_CFB_FILLRECT
598 select FB_CFB_COPYAREA
599 select FB_CFB_IMAGEBLIT
601 select FONT_8x16 if FRAMEBUFFER_CONSOLE
603 This is the frame buffer device driver for VGA 16 color graphic
604 cards. Say Y if you have such a card.
606 To compile this driver as a module, choose M here: the
607 module will be called vga16fb.
609 config FB_BF54X_LQ043
610 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
611 depends on FB && (BF54x) && !BF542
612 select FB_CFB_FILLRECT
613 select FB_CFB_COPYAREA
614 select FB_CFB_IMAGEBLIT
616 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
618 config FB_BFIN_T350MCQB
619 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
620 depends on FB && BLACKFIN
622 select FB_CFB_FILLRECT
623 select FB_CFB_COPYAREA
624 select FB_CFB_IMAGEBLIT
626 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
627 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
628 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
630 config FB_BFIN_LQ035Q1
631 tristate "SHARP LQ035Q1DH02 TFT LCD"
632 depends on FB && BLACKFIN && SPI
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
638 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
639 the Blackfin Landscape LCD EZ-Extender Card.
640 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
641 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
643 To compile this driver as a module, choose M here: the
644 module will be called bfin-lq035q1-fb.
646 config FB_BF537_LQ035
647 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
648 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
654 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
657 To compile this driver as a module, choose M here: the
658 module will be called bf537-lq035.
661 tristate "Blackfin ADV7393 Video encoder"
662 depends on FB && BLACKFIN
664 select FB_CFB_FILLRECT
665 select FB_CFB_COPYAREA
666 select FB_CFB_IMAGEBLIT
668 This is the framebuffer device for a ADV7393 video encoder
669 attached to a Blackfin on the PPI port.
670 If your Blackfin board has a ADV7393 select Y.
672 To compile this driver as a module, choose M here: the
673 module will be called bfin_adv7393fb.
676 prompt "Video mode support"
677 depends on FB_BFIN_7393
687 bool 'NTSC 640x480 (Experimental)'
690 bool 'PAL 640x480 (Experimental)'
693 bool 'NTSC 720x480 YCbCR input'
696 bool 'PAL 720x576 YCbCR input'
701 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
702 depends on (FB_BFIN_7393)
703 default ADV7393_1XMEM
713 tristate "HP STI frame buffer device support"
714 depends on FB && PARISC
715 select FB_CFB_FILLRECT
716 select FB_CFB_COPYAREA
717 select FB_CFB_IMAGEBLIT
722 STI refers to the HP "Standard Text Interface" which is a set of
723 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
724 Enabling this option will implement the linux framebuffer device
725 using calls to the STI BIOS routines for initialisation.
727 If you enable this option, you will get a planar framebuffer device
728 /dev/fb which will work on the most common HP graphic cards of the
729 NGLE family, including the artist chips (in the 7xx and Bxxx series),
730 HCRX, HCRX24, CRX, CRX24 and VisEG series.
732 It is safe to enable this option, so you should probably say "Y".
735 bool "Generic Macintosh display support"
736 depends on (FB = y) && MAC
737 select FB_CFB_FILLRECT
738 select FB_CFB_COPYAREA
739 select FB_CFB_IMAGEBLIT
744 depends on (FB = y) && DIO
745 select FB_CFB_IMAGEBLIT
749 tristate "TGA/SFB+ framebuffer support"
750 depends on FB && (ALPHA || TC)
751 select FB_CFB_FILLRECT
752 select FB_CFB_COPYAREA
753 select FB_CFB_IMAGEBLIT
756 This is the frame buffer device driver for generic TGA and SFB+
757 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
758 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
759 TURBOchannel cards, also known as PMAGD-A, -B and -C.
761 Due to hardware limitations ZLX-E2 and E3 cards are not supported
762 for DECstation 5000/200 systems. Additionally due to firmware
763 limitations these cards may cause troubles with booting DECstation
764 5000/240 and /260 systems, but are fully supported under Linux if
765 you manage to get it going. ;-)
767 Say Y if you have one of those.
770 tristate "Userspace VESA VGA graphics support"
771 depends on FB && CONNECTOR
772 select FB_CFB_FILLRECT
773 select FB_CFB_COPYAREA
774 select FB_CFB_IMAGEBLIT
775 select FB_MODE_HELPERS
777 This is the frame buffer driver for generic VBE 2.0 compliant
778 graphic cards. It can also take advantage of VBE 3.0 features,
779 such as refresh rate adjustment.
781 This driver generally provides more features than vesafb but
782 requires a userspace helper application called 'v86d'. See
783 <file:Documentation/fb/uvesafb.txt> for more information.
788 bool "VESA VGA graphics support"
789 depends on (FB = y) && X86
790 select FB_CFB_FILLRECT
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
793 select FB_BOOT_VESA_SUPPORT
795 This is the frame buffer device driver for generic VESA 2.0
796 compliant graphic cards. The older VESA 1.2 cards are not supported.
797 You will get a boot time penguin logo at no additional cost. Please
798 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
801 bool "EFI-based Framebuffer Support"
802 depends on (FB = y) && X86 && EFI
803 select FB_CFB_FILLRECT
804 select FB_CFB_COPYAREA
805 select FB_CFB_IMAGEBLIT
807 This is the EFI frame buffer device driver. If the firmware on
808 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
809 using the EFI framebuffer as your console.
812 tristate "N411 Apollo/Hecuba devkit support"
813 depends on FB && X86 && MMU
814 select FB_SYS_FILLRECT
815 select FB_SYS_COPYAREA
816 select FB_SYS_IMAGEBLIT
818 select FB_DEFERRED_IO
821 This enables support for the Apollo display controller in its
822 Hecuba form using the n411 devkit.
825 tristate "Hercules mono graphics support"
828 Say Y here if you have a Hercules mono graphics card.
830 To compile this driver as a module, choose M here: the
831 module will be called hgafb.
833 As this card technology is at least 25 years old,
834 most people will answer N here.
837 tristate "SGI Visual Workstation framebuffer support"
838 depends on FB && X86_VISWS
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 SGI Visual Workstation support for framebuffer graphics.
846 bool "SGI Graphics Backend frame buffer support"
847 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
848 select FB_CFB_FILLRECT
849 select FB_CFB_COPYAREA
850 select FB_CFB_IMAGEBLIT
852 This is the frame buffer device driver for SGI Graphics Backend.
853 This chip is used in SGI O2 and Visual Workstation 320/540.
856 int "Video memory size in MB"
860 This is the amount of memory reserved for the framebuffer,
861 which can be any value between 1MB and 8MB.
864 bool "SBUS and UPA framebuffers"
865 depends on (FB = y) && SPARC
867 Say Y if you want support for SBUS or UPA based frame buffer device.
871 depends on (FB = y) && (SPARC && FB_SBUS)
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the frame buffer device driver for the BWtwo frame buffer.
879 bool "CGthree support"
880 depends on (FB = y) && (SPARC && FB_SBUS)
881 select FB_CFB_FILLRECT
882 select FB_CFB_COPYAREA
883 select FB_CFB_IMAGEBLIT
885 This is the frame buffer device driver for the CGthree frame buffer.
888 bool "CGsix (GX,TurboGX) support"
889 depends on (FB = y) && (SPARC && FB_SBUS)
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This is the frame buffer device driver for the CGsix (GX, TurboGX)
897 bool "Creator/Creator3D/Elite3D support"
898 depends on FB_SBUS && SPARC64
899 select FB_CFB_COPYAREA
900 select FB_CFB_IMAGEBLIT
902 This is the frame buffer device driver for the Creator, Creator3D,
903 and Elite3D graphics boards.
906 bool "TCX (SS4/SS5 only) support"
908 select FB_CFB_FILLRECT
909 select FB_CFB_COPYAREA
910 select FB_CFB_IMAGEBLIT
912 This is the frame buffer device driver for the TCX 24/8bit frame
916 bool "CGfourteen (SX) support"
918 select FB_CFB_FILLRECT
919 select FB_CFB_COPYAREA
920 select FB_CFB_IMAGEBLIT
922 This is the frame buffer device driver for the CGfourteen frame
923 buffer on Desktop SPARCsystems with the SX graphics option.
926 bool "P9100 (Sparcbook 3 only) support"
928 select FB_CFB_FILLRECT
929 select FB_CFB_COPYAREA
930 select FB_CFB_IMAGEBLIT
932 This is the frame buffer device driver for the P9100 card
933 supported on Sparcbook 3 machines.
936 bool "Leo (ZX) support"
938 select FB_CFB_FILLRECT
939 select FB_CFB_COPYAREA
940 select FB_CFB_IMAGEBLIT
942 This is the frame buffer device driver for the SBUS-based Sun ZX
943 (leo) frame buffer cards.
946 bool "IGA 168x display support"
947 depends on (FB = y) && SPARC32
948 select FB_CFB_FILLRECT
949 select FB_CFB_COPYAREA
950 select FB_CFB_IMAGEBLIT
952 This is the framebuffer device for the INTERGRAPHICS 1680 and
953 successor frame buffer cards.
956 bool "Sun XVR-500 3DLABS Wildcat support"
957 depends on (FB = y) && PCI && SPARC64
958 select FB_CFB_FILLRECT
959 select FB_CFB_COPYAREA
960 select FB_CFB_IMAGEBLIT
962 This is the framebuffer device for the Sun XVR-500 and similar
963 graphics cards based upon the 3DLABS Wildcat chipset. The driver
964 only works on sparc64 systems where the system firmware has
965 mostly initialized the card already. It is treated as a
966 completely dumb framebuffer device.
969 bool "Sun XVR-2500 3DLABS Wildcat support"
970 depends on (FB = y) && PCI && SPARC64
971 select FB_CFB_FILLRECT
972 select FB_CFB_COPYAREA
973 select FB_CFB_IMAGEBLIT
975 This is the framebuffer device for the Sun XVR-2500 and similar
976 graphics cards based upon the 3DLABS Wildcat chipset. The driver
977 only works on sparc64 systems where the system firmware has
978 mostly initialized the card already. It is treated as a
979 completely dumb framebuffer device.
982 bool "Sun XVR-1000 support"
983 depends on (FB = y) && SPARC64
984 select FB_CFB_FILLRECT
985 select FB_CFB_COPYAREA
986 select FB_CFB_IMAGEBLIT
988 This is the framebuffer device for the Sun XVR-1000 and similar
989 graphics cards. The driver only works on sparc64 systems where
990 the system firmware has mostly initialized the card already. It
991 is treated as a completely dumb framebuffer device.
994 tristate "NEC PowerVR 2 display support"
995 depends on FB && SH_DREAMCAST
996 select FB_CFB_FILLRECT
997 select FB_CFB_COPYAREA
998 select FB_CFB_IMAGEBLIT
1000 Say Y here if you have a PowerVR 2 card in your box. If you plan to
1001 run linux on your Dreamcast, you will have to say Y here.
1002 This driver may or may not work on other PowerVR 2 cards, but is
1003 totally untested. Use at your own risk. If unsure, say N.
1005 To compile this driver as a module, choose M here: the
1006 module will be called pvr2fb.
1008 You can pass several parameters to the driver at boot time or at
1009 module load time. The parameters look like "video=pvr2:XXX", where
1010 the meaning of XXX can be found at the end of the main source file
1011 (<file:drivers/video/pvr2fb.c>). Please see the file
1012 <file:Documentation/fb/pvr2fb.txt>.
1015 bool "Epson 1355 framebuffer support"
1016 depends on (FB = y) && ARCH_CEIVA
1017 select FB_CFB_FILLRECT
1018 select FB_CFB_COPYAREA
1019 select FB_CFB_IMAGEBLIT
1021 Build in support for the SED1355 Epson Research Embedded RAMDAC
1022 LCD/CRT Controller (since redesignated as the S1D13505) as a
1023 framebuffer. Product specs at
1024 <http://vdc.epson.com/>.
1027 tristate "Epson S1D13XXX framebuffer support"
1029 select FB_CFB_FILLRECT
1030 select FB_CFB_COPYAREA
1031 select FB_CFB_IMAGEBLIT
1033 Support for S1D13XXX framebuffer device family (currently only
1034 working with S1D13806). Product specs at
1035 <http://vdc.epson.com/>
1038 tristate "AT91/AT32 LCD Controller support"
1039 depends on FB && HAVE_FB_ATMEL
1040 select FB_CFB_FILLRECT
1041 select FB_CFB_COPYAREA
1042 select FB_CFB_IMAGEBLIT
1044 This enables support for the AT91/AT32 LCD Controller.
1047 bool "Frame Buffer in internal SRAM"
1048 depends on FB_ATMEL && ARCH_AT91SAM9261
1050 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1051 to let frame buffer in external SDRAM.
1054 bool "Use a STN display with AT91/AT32 LCD Controller"
1055 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1058 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1059 Controller. Say N if you want to connect a TFT.
1064 tristate "nVidia Framebuffer Support"
1065 depends on FB && PCI
1066 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1067 select FB_MODE_HELPERS
1068 select FB_CFB_FILLRECT
1069 select FB_CFB_COPYAREA
1070 select FB_CFB_IMAGEBLIT
1074 This driver supports graphics boards with the nVidia chips, TNT
1075 and newer. For very old chipsets, such as the RIVA128, then use
1077 Say Y if you have such a graphics board.
1079 To compile this driver as a module, choose M here: the
1080 module will be called nvidiafb.
1082 config FB_NVIDIA_I2C
1083 bool "Enable DDC Support"
1084 depends on FB_NVIDIA
1087 This enables I2C support for nVidia Chipsets. This is used
1088 only for getting EDID information from the attached display
1089 allowing for robust video mode handling and switching.
1091 Because fbdev-2.6 requires that drivers must be able to
1092 independently validate video mode parameters, you should say Y
1095 config FB_NVIDIA_DEBUG
1096 bool "Lots of debug output"
1097 depends on FB_NVIDIA
1100 Say Y here if you want the nVidia driver to output all sorts
1101 of debugging information to provide to the maintainer when
1102 something goes wrong.
1104 config FB_NVIDIA_BACKLIGHT
1105 bool "Support for backlight control"
1106 depends on FB_NVIDIA
1109 Say Y here if you want to control the backlight of your display.
1112 tristate "nVidia Riva support"
1113 depends on FB && PCI
1114 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1115 select FB_MODE_HELPERS
1116 select FB_CFB_FILLRECT
1117 select FB_CFB_COPYAREA
1118 select FB_CFB_IMAGEBLIT
1122 This driver supports graphics boards with the nVidia Riva/Geforce
1124 Say Y if you have such a graphics board.
1126 To compile this driver as a module, choose M here: the
1127 module will be called rivafb.
1130 bool "Enable DDC Support"
1134 This enables I2C support for nVidia Chipsets. This is used
1135 only for getting EDID information from the attached display
1136 allowing for robust video mode handling and switching.
1138 Because fbdev-2.6 requires that drivers must be able to
1139 independently validate video mode parameters, you should say Y
1142 config FB_RIVA_DEBUG
1143 bool "Lots of debug output"
1147 Say Y here if you want the Riva driver to output all sorts
1148 of debugging information to provide to the maintainer when
1149 something goes wrong.
1151 config FB_RIVA_BACKLIGHT
1152 bool "Support for backlight control"
1156 Say Y here if you want to control the backlight of your display.
1159 tristate "Intel 810/815 support (EXPERIMENTAL)"
1160 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1161 select FB_MODE_HELPERS
1162 select FB_CFB_FILLRECT
1163 select FB_CFB_COPYAREA
1164 select FB_CFB_IMAGEBLIT
1167 This driver supports the on-board graphics built in to the Intel 810
1168 and 815 chipsets. Say Y if you have and plan to use such a board.
1170 To compile this driver as a module, choose M here: the
1171 module will be called i810fb.
1173 For more information, please read
1174 <file:Documentation/fb/intel810.txt>
1177 bool "use VESA Generalized Timing Formula"
1180 If you say Y, then the VESA standard, Generalized Timing Formula
1181 or GTF, will be used to calculate the required video timing values
1182 per video mode. Since the GTF allows nondiscrete timings
1183 (nondiscrete being a range of values as opposed to discrete being a
1184 set of values), you'll be able to use any combination of horizontal
1185 and vertical resolutions, and vertical refresh rates without having
1186 to specify your own timing parameters. This is especially useful
1187 to maximize the performance of an aging display, or if you just
1188 have a display with nonstandard dimensions. A VESA compliant
1189 monitor is recommended, but can still work with non-compliant ones.
1190 If you need or want this, then select this option. The timings may
1191 not be compliant with Intel's recommended values. Use at your own
1194 If you say N, the driver will revert to discrete video timings
1195 using a set recommended by Intel in their documentation.
1200 bool "Enable DDC Support"
1201 depends on FB_I810 && FB_I810_GTF
1206 tristate "Intel LE80578 (Vermilion) support"
1207 depends on FB && PCI && X86
1208 select FB_MODE_HELPERS
1209 select FB_CFB_FILLRECT
1210 select FB_CFB_COPYAREA
1211 select FB_CFB_IMAGEBLIT
1213 This driver supports the LE80578 (Vermilion Range) chipset
1215 config FB_CARILLO_RANCH
1216 tristate "Intel Carillo Ranch support"
1217 depends on FB_LE80578 && FB && PCI && X86
1219 This driver supports the LE80578 (Carillo Ranch) board
1222 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1223 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1224 select FB_MODE_HELPERS
1225 select FB_CFB_FILLRECT
1226 select FB_CFB_COPYAREA
1227 select FB_CFB_IMAGEBLIT
1228 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1229 depends on !DRM_I915
1231 This driver supports the on-board graphics built in to the Intel
1232 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1233 Say Y if you have and plan to use such a board.
1235 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1237 To compile this driver as a module, choose M here: the
1238 module will be called intelfb.
1240 For more information, please read <file:Documentation/fb/intelfb.txt>
1242 config FB_INTEL_DEBUG
1243 bool "Intel driver Debug Messages"
1246 Say Y here if you want the Intel driver to output all sorts
1247 of debugging information to provide to the maintainer when
1248 something goes wrong.
1251 bool "DDC/I2C for Intel framebuffer support"
1256 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1259 tristate "Matrox acceleration"
1260 depends on FB && PCI
1261 select FB_CFB_FILLRECT
1262 select FB_CFB_COPYAREA
1263 select FB_CFB_IMAGEBLIT
1264 select FB_TILEBLITTING
1265 select FB_MACMODES if PPC_PMAC
1267 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1268 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1269 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1270 Matrox G400, G450 or G550 card in your box.
1272 To compile this driver as a module, choose M here: the
1273 module will be called matroxfb.
1275 You can pass several parameters to the driver at boot time or at
1276 module load time. The parameters look like "video=matrox:XXX", and
1277 are described in <file:Documentation/fb/matroxfb.txt>.
1279 config FB_MATROX_MILLENIUM
1280 bool "Millennium I/II support"
1281 depends on FB_MATROX
1283 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1284 video card. If you select "Advanced lowlevel driver options" below,
1285 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1286 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1287 also use font widths different from 8.
1289 config FB_MATROX_MYSTIQUE
1290 bool "Mystique support"
1291 depends on FB_MATROX
1293 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1294 video card. If you select "Advanced lowlevel driver options" below,
1295 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1296 packed pixel and 32 bpp packed pixel. You can also use font widths
1300 bool "G100/G200/G400/G450/G550 support"
1301 depends on FB_MATROX
1303 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1304 video card. If you select "Advanced lowlevel driver options", you
1305 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1306 pixel and 32 bpp packed pixel. You can also use font widths
1309 If you need support for G400 secondary head, you must say Y to
1310 "Matrox I2C support" and "G400 second head support" right below.
1311 G450/G550 secondary head and digital output are supported without
1314 The driver starts in monitor mode. You must use the matroxset tool
1315 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1316 swap primary and secondary head outputs, or to change output mode.
1317 Secondary head driver always start in 640x480 resolution and you
1318 must use fbset to change it.
1320 Do not forget that second head supports only 16 and 32 bpp
1321 packed pixels, so it is a good idea to compile them into the kernel
1322 too. You can use only some font widths, as the driver uses generic
1323 painting procedures (the secondary head does not use acceleration
1326 G450/G550 hardware can display TV picture only from secondary CRTC,
1327 and it performs no scaling, so picture must have 525 or 625 lines.
1329 config FB_MATROX_I2C
1330 tristate "Matrox I2C support"
1331 depends on FB_MATROX
1334 This drivers creates I2C buses which are needed for accessing the
1335 DDC (I2C) bus present on all Matroxes, an I2C bus which
1336 interconnects Matrox optional devices, like MGA-TVO on G200 and
1337 G400, and the secondary head DDC bus, present on G400 only.
1339 You can say Y or M here if you want to experiment with monitor
1340 detection code. You must say Y or M here if you want to use either
1341 second head of G400 or MGA-TVO on G200 or G400.
1343 If you compile it as module, it will create a module named
1346 config FB_MATROX_MAVEN
1347 tristate "G400 second head support"
1348 depends on FB_MATROX_G && FB_MATROX_I2C
1350 WARNING !!! This support does not work with G450 !!!
1352 Say Y or M here if you want to use a secondary head (meaning two
1353 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1354 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1355 secondary head output is blanked while you are in X. With XFree
1356 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1357 the fbdev driver on first head and the fbdev driver on second head.
1359 If you compile it as module, two modules are created,
1360 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1361 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1362 also load i2c-matroxfb to get it to run.
1364 The driver starts in monitor mode and you must use the matroxset
1366 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1367 PAL or NTSC or to swap primary and secondary head outputs.
1368 Secondary head driver also always start in 640x480 resolution, you
1369 must use fbset to change it.
1371 Also do not forget that second head supports only 16 and 32 bpp
1372 packed pixels, so it is a good idea to compile them into the kernel
1373 too. You can use only some font widths, as the driver uses generic
1374 painting procedures (the secondary head does not use acceleration
1378 tristate "ATI Radeon display support"
1379 depends on FB && PCI
1380 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1381 select FB_MODE_HELPERS
1382 select FB_CFB_FILLRECT
1383 select FB_CFB_COPYAREA
1384 select FB_CFB_IMAGEBLIT
1385 select FB_MACMODES if PPC_OF
1387 Choose this option if you want to use an ATI Radeon graphics card as
1388 a framebuffer device. There are both PCI and AGP versions. You
1389 don't need to choose this to run the Radeon in plain VGA mode.
1391 There is a product page at
1392 http://products.amd.com/en-us/GraphicCardResult.aspx
1394 config FB_RADEON_I2C
1395 bool "DDC/I2C for ATI Radeon support"
1396 depends on FB_RADEON
1400 Say Y here if you want DDC/I2C support for your Radeon board.
1402 config FB_RADEON_BACKLIGHT
1403 bool "Support for backlight control"
1404 depends on FB_RADEON
1407 Say Y here if you want to control the backlight of your display.
1409 config FB_RADEON_DEBUG
1410 bool "Lots of debug output from Radeon driver"
1411 depends on FB_RADEON
1414 Say Y here if you want the Radeon driver to output all sorts
1415 of debugging information to provide to the maintainer when
1416 something goes wrong.
1419 tristate "ATI Rage128 display support"
1420 depends on FB && PCI
1421 select FB_CFB_FILLRECT
1422 select FB_CFB_COPYAREA
1423 select FB_CFB_IMAGEBLIT
1424 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1425 select FB_MACMODES if PPC_PMAC
1427 This driver supports graphics boards with the ATI Rage128 chips.
1428 Say Y if you have such a graphics board and read
1429 <file:Documentation/fb/aty128fb.txt>.
1431 To compile this driver as a module, choose M here: the
1432 module will be called aty128fb.
1434 config FB_ATY128_BACKLIGHT
1435 bool "Support for backlight control"
1436 depends on FB_ATY128
1439 Say Y here if you want to control the backlight of your display.
1442 tristate "ATI Mach64 display support" if PCI || ATARI
1443 depends on FB && !SPARC32
1444 select FB_CFB_FILLRECT
1445 select FB_CFB_COPYAREA
1446 select FB_CFB_IMAGEBLIT
1447 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1448 select FB_MACMODES if PPC
1450 This driver supports graphics boards with the ATI Mach64 chips.
1451 Say Y if you have such a graphics board.
1453 To compile this driver as a module, choose M here: the
1454 module will be called atyfb.
1457 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1458 depends on PCI && FB_ATY
1459 default y if SPARC64 && PCI
1461 Say Y here to support use of ATI's 64-bit Rage boards (or other
1462 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1463 framebuffer device. The ATI product support page for these boards
1464 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1466 config FB_ATY_GENERIC_LCD
1467 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1468 depends on FB_ATY_CT
1470 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1471 Rage XC, or Rage XL chipset.
1474 bool "Mach64 GX support" if PCI
1478 Say Y here to support use of the ATI Mach64 Graphics Expression
1479 board (or other boards based on the Mach64 GX chipset) as a
1480 framebuffer device. The ATI product support page for these boards
1482 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1484 config FB_ATY_BACKLIGHT
1485 bool "Support for backlight control"
1489 Say Y here if you want to control the backlight of your display.
1492 tristate "S3 Trio/Virge support"
1493 depends on FB && PCI
1494 select FB_CFB_FILLRECT
1495 select FB_CFB_COPYAREA
1496 select FB_CFB_IMAGEBLIT
1497 select FB_TILEBLITTING
1500 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1502 Driver for graphics boards with S3 Trio / S3 Virge chip.
1505 tristate "S3 Savage support"
1506 depends on FB && PCI && EXPERIMENTAL
1507 select FB_MODE_HELPERS
1508 select FB_CFB_FILLRECT
1509 select FB_CFB_COPYAREA
1510 select FB_CFB_IMAGEBLIT
1513 This driver supports notebooks and computers with S3 Savage PCI/AGP
1516 Say Y if you have such a graphics card.
1518 To compile this driver as a module, choose M here; the module
1519 will be called savagefb.
1521 config FB_SAVAGE_I2C
1522 bool "Enable DDC2 Support"
1523 depends on FB_SAVAGE
1526 This enables I2C support for S3 Savage Chipsets. This is used
1527 only for getting EDID information from the attached display
1528 allowing for robust video mode handling and switching.
1530 Because fbdev-2.6 requires that drivers must be able to
1531 independently validate video mode parameters, you should say Y
1534 config FB_SAVAGE_ACCEL
1535 bool "Enable Console Acceleration"
1536 depends on FB_SAVAGE
1539 This option will compile in console acceleration support. If
1540 the resulting framebuffer console has bothersome glitches, then
1544 tristate "SiS/XGI display support"
1545 depends on FB && PCI
1546 select FB_CFB_FILLRECT
1547 select FB_CFB_COPYAREA
1548 select FB_CFB_IMAGEBLIT
1549 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1551 This is the frame buffer device driver for the SiS 300, 315, 330
1552 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1553 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1555 To compile this driver as a module, choose M here; the module
1556 will be called sisfb.
1559 bool "SiS 300 series support"
1562 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1565 bool "SiS 315/330/340 series and XGI support"
1568 Say Y here to support use of the SiS 315, 330 and 340 series
1569 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1570 as XGI V3XT, V5, V8 and Z7.
1573 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1574 depends on FB && PCI && X86
1575 select FB_CFB_FILLRECT
1576 select FB_CFB_COPYAREA
1577 select FB_CFB_IMAGEBLIT
1582 This is the frame buffer device driver for Graphics chips of VIA
1583 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1584 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1586 Say Y if you have a VIA UniChrome graphics board.
1588 To compile this driver as a module, choose M here: the
1589 module will be called viafb.
1593 config FB_VIA_DIRECT_PROCFS
1594 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1598 Allow direct hardware access to some output registers via procfs.
1599 This is dangerous but may provide the only chance to get the
1600 correct output device configuration.
1601 Its use is strongly discouraged.
1606 tristate "NeoMagic display support"
1607 depends on FB && PCI
1608 select FB_MODE_HELPERS
1609 select FB_CFB_FILLRECT
1610 select FB_CFB_COPYAREA
1611 select FB_CFB_IMAGEBLIT
1614 This driver supports notebooks with NeoMagic PCI chips.
1615 Say Y if you have such a graphics card.
1617 To compile this driver as a module, choose M here: the
1618 module will be called neofb.
1621 tristate "IMG Kyro support"
1622 depends on FB && PCI
1623 select FB_CFB_FILLRECT
1624 select FB_CFB_COPYAREA
1625 select FB_CFB_IMAGEBLIT
1627 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1630 To compile this driver as a module, choose M here: the
1631 module will be called kyrofb.
1634 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1635 depends on FB && PCI
1636 select FB_CFB_IMAGEBLIT
1637 select FB_CFB_FILLRECT
1638 select FB_CFB_COPYAREA
1639 select FB_MODE_HELPERS
1641 This driver supports graphics boards with the 3Dfx Banshee,
1642 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1643 such a graphics board.
1645 To compile this driver as a module, choose M here: the
1646 module will be called tdfxfb.
1648 config FB_3DFX_ACCEL
1649 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1650 depends on FB_3DFX && EXPERIMENTAL
1652 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1653 device driver with acceleration functions.
1656 bool "Enable DDC/I2C support"
1657 depends on FB_3DFX && EXPERIMENTAL
1661 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1664 tristate "3Dfx Voodoo Graphics (sst1) support"
1665 depends on FB && PCI
1666 select FB_CFB_FILLRECT
1667 select FB_CFB_COPYAREA
1668 select FB_CFB_IMAGEBLIT
1670 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1671 Voodoo2 (cvg) based graphics card.
1673 To compile this driver as a module, choose M here: the
1674 module will be called sstfb.
1676 WARNING: Do not use any application that uses the 3D engine
1677 (namely glide) while using this driver.
1678 Please read the <file:Documentation/fb/sstfb.txt> for supported
1679 options and other important info support.
1682 tristate "VIA VT8623 support"
1683 depends on FB && PCI
1684 select FB_CFB_FILLRECT
1685 select FB_CFB_COPYAREA
1686 select FB_CFB_IMAGEBLIT
1687 select FB_TILEBLITTING
1690 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1692 Driver for CastleRock integrated graphics core in the
1693 VIA VT8623 [Apollo CLE266] chipset.
1696 tristate "Trident/CyberXXX/CyberBlade support"
1697 depends on FB && PCI
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1702 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1703 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1705 There are also integrated versions of these chips called CyberXXXX,
1706 CyberImage or CyberBlade. These chips are mostly found in laptops
1707 but also on some motherboards including early VIA EPIA motherboards.
1708 For more information, read <file:Documentation/fb/tridentfb.txt>
1710 Say Y if you have such a graphics board.
1712 To compile this driver as a module, choose M here: the
1713 module will be called tridentfb.
1716 tristate "ARK 2000PV support"
1717 depends on FB && PCI
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1721 select FB_TILEBLITTING
1724 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1726 Driver for PCI graphics boards with ARK 2000PV chip
1727 and ICS 5342 RAMDAC.
1730 tristate "Permedia3 support (EXPERIMENTAL)"
1731 depends on FB && PCI && EXPERIMENTAL
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1736 This is the frame buffer device driver for the 3DLabs Permedia3
1737 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1738 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1739 and maybe other boards.
1742 tristate "Fujitsu carmine frame buffer support"
1743 depends on FB && PCI
1744 select FB_CFB_FILLRECT
1745 select FB_CFB_COPYAREA
1746 select FB_CFB_IMAGEBLIT
1748 This is the frame buffer device driver for the Fujitsu Carmine chip.
1749 The driver provides two independent frame buffer devices.
1752 depends on FB_CARMINE
1753 prompt "DRAM timing"
1754 default FB_CARMINE_DRAM_EVAL
1756 config FB_CARMINE_DRAM_EVAL
1757 bool "Eval board timings"
1759 Use timings which work on the eval card.
1761 config CARMINE_DRAM_CUSTOM
1762 bool "Custom board timings"
1764 Use custom board timings.
1768 bool "Au1100 LCD Driver"
1769 depends on (FB = y) && MIPS && SOC_AU1100
1770 select FB_CFB_FILLRECT
1771 select FB_CFB_COPYAREA
1772 select FB_CFB_IMAGEBLIT
1774 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1775 various panels and CRTs by passing in kernel cmd line option
1776 au1100fb:panel=<name>.
1779 bool "Au1200 LCD Driver"
1780 depends on (FB = y) && MIPS && SOC_AU1200
1781 select FB_CFB_FILLRECT
1782 select FB_CFB_COPYAREA
1783 select FB_CFB_IMAGEBLIT
1785 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1786 various panels and CRTs by passing in kernel cmd line option
1787 au1200fb:panel=<name>.
1790 bool "VT8500 LCD Driver"
1791 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1792 select FB_WMT_GE_ROPS
1793 select FB_SYS_IMAGEBLIT
1795 This is the framebuffer driver for VIA VT8500 integrated LCD
1799 bool "WM8505 frame buffer support"
1800 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1801 select FB_WMT_GE_ROPS
1802 select FB_SYS_IMAGEBLIT
1804 This is the framebuffer driver for WonderMedia WM8505
1805 integrated LCD controller.
1807 source "drivers/video/geode/Kconfig"
1810 tristate "HD64461 Frame Buffer support"
1811 depends on FB && HD64461
1812 select FB_CFB_FILLRECT
1813 select FB_CFB_COPYAREA
1814 select FB_CFB_IMAGEBLIT
1816 This is the frame buffer device driver for the Hitachi HD64461 LCD
1820 bool "PMAG-AA TURBOchannel framebuffer support"
1821 depends on (FB = y) && TC
1822 select FB_CFB_FILLRECT
1823 select FB_CFB_COPYAREA
1824 select FB_CFB_IMAGEBLIT
1826 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1827 used mainly in the MIPS-based DECstation series.
1830 tristate "PMAG-BA TURBOchannel framebuffer support"
1832 select FB_CFB_FILLRECT
1833 select FB_CFB_COPYAREA
1834 select FB_CFB_IMAGEBLIT
1836 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1837 used mainly in the MIPS-based DECstation series.
1840 tristate "PMAGB-B TURBOchannel framebuffer support"
1842 select FB_CFB_FILLRECT
1843 select FB_CFB_COPYAREA
1844 select FB_CFB_IMAGEBLIT
1846 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1847 in the MIPS-based DECstation series. The card is currently only
1848 supported in 1280x1024x8 mode.
1851 bool "Maxine (Personal DECstation) onboard framebuffer support"
1852 depends on (FB = y) && MACH_DECSTATION
1853 select FB_CFB_FILLRECT
1854 select FB_CFB_COPYAREA
1855 select FB_CFB_IMAGEBLIT
1857 Support for the onboard framebuffer (1024x768x8) in the Personal
1858 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1862 bool "G364 frame buffer support"
1863 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1864 select FB_CFB_FILLRECT
1865 select FB_CFB_COPYAREA
1866 select FB_CFB_IMAGEBLIT
1868 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1869 Olivetti M700-10 systems.
1872 bool "Motorola 68328 native frame buffer support"
1873 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1874 select FB_CFB_FILLRECT
1875 select FB_CFB_COPYAREA
1876 select FB_CFB_IMAGEBLIT
1878 Say Y here if you want to support the built-in frame buffer of
1879 the Motorola 68328 CPU family.
1882 tristate "PXA168/910 LCD framebuffer support"
1883 depends on FB && (CPU_PXA168 || CPU_PXA910)
1884 select FB_CFB_FILLRECT
1885 select FB_CFB_COPYAREA
1886 select FB_CFB_IMAGEBLIT
1888 Frame buffer driver for the built-in LCD controller in the Marvell
1892 tristate "PXA LCD framebuffer support"
1893 depends on FB && ARCH_PXA
1894 select FB_CFB_FILLRECT
1895 select FB_CFB_COPYAREA
1896 select FB_CFB_IMAGEBLIT
1898 Frame buffer driver for the built-in LCD controller in the Intel
1901 This driver is also available as a module ( = code which can be
1902 inserted and removed from the running kernel whenever you want). The
1903 module will be called pxafb. If you want to compile it as a module,
1904 say M here and read <file:Documentation/kbuild/modules.txt>.
1908 config FB_PXA_OVERLAY
1909 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1911 depends on FB_PXA && (PXA27x || PXA3xx)
1913 config FB_PXA_SMARTPANEL
1914 bool "PXA Smartpanel LCD support"
1918 config FB_PXA_PARAMETERS
1919 bool "PXA LCD command line parameters"
1923 Enable the use of kernel command line or module parameters
1924 to configure the physical properties of the LCD panel when
1925 using the PXA LCD driver.
1927 This option allows you to override the panel parameters
1928 supplied by the platform in order to support multiple
1929 different models of flatpanel. If you will only be using a
1930 single model of flatpanel then you can safely leave this
1933 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1936 tristate "PXA3xx 2D graphics accelerator driver"
1939 Kernelspace driver for the 2D graphics controller unit (GCU)
1940 found on PXA3xx processors. There is a counterpart driver in the
1941 DirectFB suite, see http://www.directfb.org/
1943 If you compile this as a module, it will be called pxa3xx_gcu.
1946 tristate "2700G LCD framebuffer support"
1947 depends on FB && ARCH_PXA
1948 select FB_CFB_FILLRECT
1949 select FB_CFB_COPYAREA
1950 select FB_CFB_IMAGEBLIT
1952 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1956 bool "Enable debugging info via debugfs"
1957 depends on FB_MBX && DEBUG_FS
1960 Enable this if you want debugging information using the debug
1961 filesystem (debugfs)
1966 tristate "Freescale DIU framebuffer support"
1967 depends on FB && FSL_SOC
1968 select FB_MODE_HELPERS
1969 select FB_CFB_FILLRECT
1970 select FB_CFB_COPYAREA
1971 select FB_CFB_IMAGEBLIT
1972 select PPC_LIB_RHEAP
1974 Framebuffer driver for the Freescale SoC DIU
1977 tristate "W100 frame buffer support"
1978 depends on FB && ARCH_PXA
1979 select FB_CFB_FILLRECT
1980 select FB_CFB_COPYAREA
1981 select FB_CFB_IMAGEBLIT
1983 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1984 It can also drive the w3220 chip found on iPAQ hx4700.
1986 This driver is also available as a module ( = code which can be
1987 inserted and removed from the running kernel whenever you want). The
1988 module will be called w100fb. If you want to compile it as a module,
1989 say M here and read <file:Documentation/kbuild/modules.txt>.
1995 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1997 config SH_LCD_MIPI_DSI
2000 config FB_SH_MOBILE_LCDC
2001 tristate "SuperH Mobile LCDC framebuffer support"
2002 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2003 select FB_SYS_FILLRECT
2004 select FB_SYS_COPYAREA
2005 select FB_SYS_IMAGEBLIT
2007 select FB_DEFERRED_IO
2008 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2010 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2012 config FB_SH_MOBILE_HDMI
2013 tristate "SuperH Mobile HDMI controller support"
2014 depends on FB_SH_MOBILE_LCDC
2015 select FB_MODE_HELPERS
2020 Driver for the on-chip SH-Mobile HDMI controller.
2023 tristate "Toshiba Mobile IO FrameBuffer support"
2024 depends on FB && MFD_CORE
2025 select FB_CFB_FILLRECT
2026 select FB_CFB_COPYAREA
2027 select FB_CFB_IMAGEBLIT
2029 Frame buffer driver for the Toshiba Mobile IO integrated as found
2030 on the Sharp SL-6000 series
2032 This driver is also available as a module ( = code which can be
2033 inserted and removed from the running kernel whenever you want). The
2034 module will be called tmiofb. If you want to compile it as a module,
2035 say M here and read <file:Documentation/kbuild/modules.txt>.
2039 config FB_TMIO_ACCELL
2040 bool "tmiofb acceleration"
2045 tristate "Samsung S3C framebuffer support"
2046 depends on FB && S3C_DEV_FB
2047 select FB_CFB_FILLRECT
2048 select FB_CFB_COPYAREA
2049 select FB_CFB_IMAGEBLIT
2051 Frame buffer driver for the built-in FB controller in the Samsung
2052 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2053 and the S3C64XX series such as the S3C6400 and S3C6410.
2055 These chips all have the same basic framebuffer design with the
2056 actual capabilities depending on the chip. For instance the S3C6400
2057 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2058 currently only have two.
2060 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2062 config FB_S3C_DEBUG_REGWRITE
2063 bool "Debug register writes"
2066 Show all register writes via printk(KERN_DEBUG)
2069 tristate "S3C2410 LCD framebuffer support"
2070 depends on FB && ARCH_S3C2410
2071 select FB_CFB_FILLRECT
2072 select FB_CFB_COPYAREA
2073 select FB_CFB_IMAGEBLIT
2075 Frame buffer driver for the built-in LCD controller in the Samsung
2078 This driver is also available as a module ( = code which can be
2079 inserted and removed from the running kernel whenever you want). The
2080 module will be called s3c2410fb. If you want to compile it as a module,
2081 say M here and read <file:Documentation/kbuild/modules.txt>.
2084 config FB_S3C2410_DEBUG
2085 bool "S3C2410 lcd debug messages"
2086 depends on FB_S3C2410
2088 Turn on debugging messages. Note that you can set/unset at run time
2092 bool "NUC900 LCD framebuffer support"
2093 depends on FB && ARCH_W90X900
2094 select FB_CFB_FILLRECT
2095 select FB_CFB_COPYAREA
2096 select FB_CFB_IMAGEBLIT
2098 Frame buffer driver for the built-in LCD controller in the Nuvoton
2101 config GPM1040A0_320X240
2102 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2103 depends on FB_NUC900
2105 config FB_NUC900_DEBUG
2106 bool "NUC900 lcd debug messages"
2107 depends on FB_NUC900
2109 Turn on debugging messages. Note that you can set/unset at run time
2113 tristate "Silicon Motion SM501 framebuffer support"
2114 depends on FB && MFD_SM501
2115 select FB_CFB_FILLRECT
2116 select FB_CFB_COPYAREA
2117 select FB_CFB_IMAGEBLIT
2119 Frame buffer driver for the CRT and LCD controllers in the Silicon
2122 This driver is also available as a module ( = code which can be
2123 inserted and removed from the running kernel whenever you want). The
2124 module will be called sm501fb. If you want to compile it as a module,
2125 say M here and read <file:Documentation/kbuild/modules.txt>.
2130 tristate "Displaylink USB Framebuffer support"
2131 depends on FB && USB
2132 select FB_MODE_HELPERS
2133 select FB_SYS_FILLRECT
2134 select FB_SYS_COPYAREA
2135 select FB_SYS_IMAGEBLIT
2137 select FB_DEFERRED_IO
2139 This is a kernel framebuffer driver for DisplayLink USB devices.
2140 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2141 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2142 To compile as a module, choose M here: the module name is udlfb.
2144 config FB_PNX4008_DUM
2145 tristate "Display Update Module support on Philips PNX4008 board"
2146 depends on FB && ARCH_PNX4008
2148 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2150 config FB_PNX4008_DUM_RGB
2151 tristate "RGB Framebuffer support on Philips PNX4008 board"
2152 depends on FB_PNX4008_DUM
2153 select FB_CFB_FILLRECT
2154 select FB_CFB_COPYAREA
2155 select FB_CFB_IMAGEBLIT
2157 Say Y here to enable support for PNX4008 RGB Framebuffer
2159 config FB_IBM_GXT4500
2160 tristate "Framebuffer support for IBM GXT4500P adaptor"
2161 depends on FB && PPC
2162 select FB_CFB_FILLRECT
2163 select FB_CFB_COPYAREA
2164 select FB_CFB_IMAGEBLIT
2166 Say Y here to enable support for the IBM GXT4500P display
2167 adaptor, found on some IBM System P (pSeries) machines.
2170 tristate "PS3 GPU framebuffer driver"
2171 depends on FB && PS3_PS3AV
2172 select FB_SYS_FILLRECT
2173 select FB_SYS_COPYAREA
2174 select FB_SYS_IMAGEBLIT
2176 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2178 Include support for the virtual frame buffer in the PS3 platform.
2180 config FB_PS3_DEFAULT_SIZE_M
2181 int "PS3 default frame buffer size (in MiB)"
2185 This is the default size (in MiB) of the virtual frame buffer in
2187 The default value can be overridden on the kernel command line
2188 using the "ps3fb" option (e.g. "ps3fb=9M");
2191 tristate "Xilinx frame buffer support"
2192 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2193 select FB_CFB_FILLRECT
2194 select FB_CFB_COPYAREA
2195 select FB_CFB_IMAGEBLIT
2197 Include support for the Xilinx ML300/ML403 reference design
2198 framebuffer. ML300 carries a 640*480 LCD display on the board,
2199 ML403 uses a standard DB15 VGA connector.
2202 tristate "Cobalt server LCD frame buffer support"
2203 depends on FB && MIPS_COBALT
2206 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2207 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2208 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2209 select FB_CFB_FILLRECT
2210 select FB_CFB_COPYAREA
2211 select FB_CFB_IMAGEBLIT
2213 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2214 (D)STN/TFT LCD Controller.
2215 Supports display resolutions up to 1024x1024 pixel, grayscale and
2216 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2217 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2218 panels <= 320 pixel horizontal resolution.
2221 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2222 depends on FB && ARCH_DAVINCI_DA8XX
2223 select FB_CFB_FILLRECT
2224 select FB_CFB_COPYAREA
2225 select FB_CFB_IMAGEBLIT
2227 This is the frame buffer device driver for the TI LCD controller
2228 found on DA8xx/OMAP-L1xx SoCs.
2232 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2234 select FB_SYS_FILLRECT
2235 select FB_SYS_COPYAREA
2236 select FB_SYS_IMAGEBLIT
2239 This is a `virtual' frame buffer device. It operates on a chunk of
2240 unswappable kernel memory instead of on the memory of a graphics
2241 board. This means you cannot see any output sent to this frame
2242 buffer device, while it does consume precious memory. The main use
2243 of this frame buffer device is testing and debugging the frame
2244 buffer subsystem. Do NOT enable it for normal systems! To protect
2245 the innocent, it has to be enabled explicitly at boot time using the
2246 kernel option `video=vfb:'.
2248 To compile this driver as a module, choose M here: the
2249 module will be called vfb. In order to load it, you must use
2250 the vfb_enable=1 option.
2254 config XEN_FBDEV_FRONTEND
2255 tristate "Xen virtual frame buffer support"
2256 depends on FB && XEN
2257 select FB_SYS_FILLRECT
2258 select FB_SYS_COPYAREA
2259 select FB_SYS_IMAGEBLIT
2261 select FB_DEFERRED_IO
2262 select XEN_XENBUS_FRONTEND
2265 This driver implements the front-end of the Xen virtual
2266 frame buffer driver. It communicates with a back-end
2270 tristate "E-Ink Metronome/8track controller support"
2272 select FB_SYS_FILLRECT
2273 select FB_SYS_COPYAREA
2274 select FB_SYS_IMAGEBLIT
2276 select FB_DEFERRED_IO
2278 This driver implements support for the E-Ink Metronome
2279 controller. The pre-release name for this device was 8track
2280 and could also have been called by some vendors as PVI-nnnn.
2283 tristate "Fujitsu MB862xx GDC support"
2285 select FB_CFB_FILLRECT
2286 select FB_CFB_COPYAREA
2287 select FB_CFB_IMAGEBLIT
2289 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2291 config FB_MB862XX_PCI_GDC
2292 bool "Carmine/Coral-P(A) GDC"
2293 depends on PCI && FB_MB862XX
2295 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2296 PCI graphics controller devices.
2298 config FB_MB862XX_LIME
2300 depends on FB_MB862XX
2301 depends on OF && !FB_MB862XX_PCI_GDC
2303 select FB_FOREIGN_ENDIAN
2304 select FB_LITTLE_ENDIAN
2306 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2309 tristate "EP93XX frame buffer support"
2310 depends on FB && ARCH_EP93XX
2311 select FB_CFB_FILLRECT
2312 select FB_CFB_COPYAREA
2313 select FB_CFB_IMAGEBLIT
2315 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2316 This driver is also available as a module. The module will be called
2319 config FB_PRE_INIT_FB
2320 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2321 depends on FB && FB_MB862XX_LIME
2323 Select this option if display contents should be inherited as set by
2327 tristate "MSM Framebuffer support"
2328 depends on FB && ARCH_MSM
2329 select FB_CFB_FILLRECT
2330 select FB_CFB_COPYAREA
2331 select FB_CFB_IMAGEBLIT
2334 tristate "MX3 Framebuffer support"
2335 depends on FB && MX3_IPU
2336 select FB_CFB_FILLRECT
2337 select FB_CFB_COPYAREA
2338 select FB_CFB_IMAGEBLIT
2341 This is a framebuffer device for the i.MX31 LCD Controller. So
2342 far only synchronous displays are supported. If you plan to use
2343 an LCD display with your i.MX31 system, say Y here.
2345 config FB_BROADSHEET
2346 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2348 select FB_SYS_FILLRECT
2349 select FB_SYS_COPYAREA
2350 select FB_SYS_IMAGEBLIT
2352 select FB_DEFERRED_IO
2354 This driver implements support for the E-Ink Broadsheet
2355 controller. The release name for this device was Epson S1D13521
2356 and could also have been called by other names when coupled with
2360 tristate "JZ4740 LCD framebuffer support"
2361 depends on FB && MACH_JZ4740
2362 select FB_SYS_FILLRECT
2363 select FB_SYS_COPYAREA
2364 select FB_SYS_IMAGEBLIT
2366 Framebuffer support for the JZ4740 SoC.
2368 source "drivers/video/omap/Kconfig"
2369 source "drivers/video/omap2/Kconfig"
2371 source "drivers/video/backlight/Kconfig"
2372 source "drivers/video/display/Kconfig"
2375 source "drivers/video/console/Kconfig"
2378 if FB || SGI_NEWPORT_CONSOLE
2379 source "drivers/video/logo/Kconfig"