5 menu "Graphics support"
16 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
18 config SH_LCD_MIPI_DSI
21 source "drivers/char/agp/Kconfig"
23 source "drivers/gpu/vga/Kconfig"
25 source "drivers/gpu/drm/Kconfig"
27 source "drivers/gpu/stub/Kconfig"
33 config VIDEO_OUTPUT_CONTROL
34 tristate "Lowlevel video output switch controls"
36 This framework adds support for low-level control of the video
40 tristate "Support for frame buffer devices"
42 The frame buffer device provides an abstraction for the graphics
43 hardware. It represents the frame buffer of some video hardware and
44 allows application software to access the graphics hardware through
45 a well-defined interface, so the software doesn't need to know
46 anything about the low-level (hardware register) stuff.
48 Frame buffer devices work identically across the different
49 architectures supported by Linux and make the implementation of
50 application programs easier and more portable; at this point, an X
51 server exists which uses the frame buffer device exclusively.
52 On several non-X86 architectures, the frame buffer device is the
53 only way to use the graphics hardware.
55 The device is accessed through special device nodes, usually located
56 in the /dev directory, i.e. /dev/fb*.
58 You need an utility program called fbset to make full use of frame
59 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
60 and the Framebuffer-HOWTO at
61 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
64 Say Y here and to the driver for your graphics board below if you
65 are compiling a kernel for a non-x86 architecture.
67 If you are compiling for the x86 architecture, you can say Y if you
68 want to play with it, but it is not essential. Please note that
69 running graphical applications that directly touch the hardware
70 (e.g. an accelerated X server) and that are not frame buffer
71 device-aware may cause unexpected results. If unsure, say N.
74 bool "Enable firmware EDID"
78 This enables access to the EDID transferred from the firmware.
79 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
80 transfers do not work for your driver and if you are using
81 nvidiafb, i810fb or savagefb.
83 In general, choosing Y for this option is safe. If you
84 experience extremely long delays while booting before you get
85 something on your display, try setting this to N. Matrox cards in
86 combination with certain motherboards and monitors are known to
87 suffer from this problem.
96 config FB_BOOT_VESA_SUPPORT
101 If true, at least one selected framebuffer driver can take advantage
102 of VESA video modes set at an early boot stage via the vga= parameter.
104 config FB_CFB_FILLRECT
109 Include the cfb_fillrect function for generic software rectangle
110 filling. This is used by drivers that don't provide their own
111 (accelerated) version.
113 config FB_CFB_COPYAREA
118 Include the cfb_copyarea function for generic software area copying.
119 This is used by drivers that don't provide their own (accelerated)
122 config FB_CFB_IMAGEBLIT
127 Include the cfb_imageblit function for generic software image
128 blitting. This is used by drivers that don't provide their own
129 (accelerated) version.
131 config FB_CFB_REV_PIXELS_IN_BYTE
136 Allow generic frame-buffer functions to work on displays with 1, 2
137 and 4 bits per pixel depths which has opposite order of pixels in
138 byte order to bytes in long order.
140 config FB_SYS_FILLRECT
145 Include the sys_fillrect function for generic software rectangle
146 filling. This is used by drivers that don't provide their own
147 (accelerated) version and the framebuffer is in system RAM.
149 config FB_SYS_COPYAREA
154 Include the sys_copyarea function for generic software area copying.
155 This is used by drivers that don't provide their own (accelerated)
156 version and the framebuffer is in system RAM.
158 config FB_SYS_IMAGEBLIT
163 Include the sys_imageblit function for generic software image
164 blitting. This is used by drivers that don't provide their own
165 (accelerated) version and the framebuffer is in system RAM.
167 menuconfig FB_FOREIGN_ENDIAN
168 bool "Framebuffer foreign endianness support"
171 This menu will let you enable support for the framebuffers with
172 non-native endianness (e.g. Little-Endian framebuffer on a
173 Big-Endian machine). Most probably you don't have such hardware,
174 so it's safe to say "n" here.
177 prompt "Choice endianness support"
178 depends on FB_FOREIGN_ENDIAN
180 config FB_BOTH_ENDIAN
181 bool "Support for Big- and Little-Endian framebuffers"
184 bool "Support for Big-Endian framebuffers only"
186 config FB_LITTLE_ENDIAN
187 bool "Support for Little-Endian framebuffers only"
196 config FB_WMT_GE_ROPS
201 Include functions for accelerated rectangle filling and area
202 copying using WonderMedia Graphics Engine operations.
204 config FB_DEFERRED_IO
211 depends on FB_DEFERRED_IO
218 Common utility functions useful to fbdev drivers of VGA-based
229 select BACKLIGHT_LCD_SUPPORT
230 select BACKLIGHT_CLASS_DEVICE
233 config FB_MODE_HELPERS
234 bool "Enable Video Mode Handling Helpers"
238 This enables functions for handling video modes using the
239 Generalized Timing Formula and the EDID parser. A few drivers rely
240 on this feature such as the radeonfb, rivafb, and the i810fb. If
241 your driver does not take advantage of this feature, choosing Y will
242 just increase the kernel size by about 5K.
244 config FB_TILEBLITTING
245 bool "Enable Tile Blitting Support"
249 This enables tile blitting. Tile blitting is a drawing technique
250 where the screen is divided into rectangular sections (tiles), whereas
251 the standard blitting divides the screen into pixels. Because the
252 default drawing element is a tile, drawing functions will be passed
253 parameters in terms of number of tiles instead of number of pixels.
254 For example, to draw a single character, instead of using bitmaps,
255 an index to an array of bitmaps will be used. To clear or move a
256 rectangular section of a screen, the rectangle will be described in
257 terms of number of tiles in the x- and y-axis.
259 This is particularly important to one driver, matroxfb. If
262 comment "Frame buffer hardware drivers"
266 tristate "Cirrus Logic support"
267 depends on FB && (ZORRO || PCI)
268 select FB_CFB_FILLRECT
269 select FB_CFB_COPYAREA
270 select FB_CFB_IMAGEBLIT
272 This enables support for Cirrus Logic GD542x/543x based boards on
273 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
275 If you have a PCI-based system, this enables support for these
276 chips: GD-543x, GD-544x, GD-5480.
278 Please read the file <file:Documentation/fb/cirrusfb.txt>.
280 Say N unless you have such a graphics board or plan to get one
281 before you next recompile the kernel.
284 tristate "Permedia2 support"
285 depends on FB && ((AMIGA && BROKEN) || PCI)
286 select FB_CFB_FILLRECT
287 select FB_CFB_COPYAREA
288 select FB_CFB_IMAGEBLIT
290 This is the frame buffer device driver for cards based on
291 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
292 The driver was tested on the following cards:
293 Diamond FireGL 1000 PRO AGP
294 ELSA Gloria Synergy PCI
295 Appian Jeronimo PRO (both heads) PCI
296 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
297 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
298 ASK Graphic Blaster Exxtreme AGP
300 To compile this driver as a module, choose M here: the
301 module will be called pm2fb.
303 config FB_PM2_FIFO_DISCONNECT
304 bool "enable FIFO disconnect feature"
305 depends on FB_PM2 && PCI
307 Support the Permedia2 FIFO disconnect feature.
310 tristate "ARM PrimeCell PL110 support"
311 depends on FB && ARM && ARM_AMBA
312 select FB_CFB_FILLRECT
313 select FB_CFB_COPYAREA
314 select FB_CFB_IMAGEBLIT
316 This framebuffer device driver is for the ARM PrimeCell PL110
317 Colour LCD controller. ARM PrimeCells provide the building
318 blocks for System on a Chip devices.
320 If you want to compile this as a module (=code which can be
321 inserted into and removed from the running kernel), say M
322 here and read <file:Documentation/kbuild/modules.txt>. The module
323 will be called amba-clcd.
327 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
329 default FB_ARMCLCD_SHARP_LQ035Q7DB02
331 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
332 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
334 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
335 color QVGA, HRTFT panel. The LogicPD device includes
336 an integrated HRTFT controller IC.
337 The native resolution is 240x320.
339 config FB_ARMCLCD_SHARP_LQ057Q3DC02
340 bool "LogicPD LCD 5.7\" QVGA"
342 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
343 color QVGA, TFT panel. The LogicPD device includes an
344 The native resolution is 320x240.
346 config FB_ARMCLCD_SHARP_LQ64D343
347 bool "LogicPD LCD 6.4\" VGA"
349 This is an implementation of the Sharp LQ64D343, a 6.4"
350 color VGA, TFT panel. The LogicPD device includes an
351 The native resolution is 640x480.
353 config FB_ARMCLCD_SHARP_LQ10D368
354 bool "LogicPD LCD 10.4\" VGA"
356 This is an implementation of the Sharp LQ10D368, a 10.4"
357 color VGA, TFT panel. The LogicPD device includes an
358 The native resolution is 640x480.
361 config FB_ARMCLCD_SHARP_LQ121S1DG41
362 bool "LogicPD LCD 12.1\" SVGA"
364 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
365 color SVGA, TFT panel. The LogicPD device includes an
366 The native resolution is 800x600.
368 This panel requires a clock rate may be an integer fraction
369 of the base LCDCLK frequency. The driver will select the
370 highest frequency available that is lower than the maximum
371 allowed. The panel may flicker if the clock rate is
372 slower than the recommended minimum.
374 config FB_ARMCLCD_AUO_A070VW01_WIDE
375 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
377 This is an implementation of the AU Optronics, a 7.0"
378 WIDE Color. The native resolution is 234x480.
380 config FB_ARMCLCD_HITACHI
381 bool "Hitachi Wide Screen 800x480"
383 This is an implementation of the Hitachi 800x480.
389 bool "Acorn VIDC support"
390 depends on (FB = y) && ARM && ARCH_ACORN
391 select FB_CFB_FILLRECT
392 select FB_CFB_COPYAREA
393 select FB_CFB_IMAGEBLIT
395 This is the frame buffer device driver for the Acorn VIDC graphics
396 hardware found in Acorn RISC PCs and other ARM-based machines. If
400 bool "CLPS711X LCD support"
401 depends on (FB = y) && ARM && ARCH_CLPS711X
402 select FB_CFB_FILLRECT
403 select FB_CFB_COPYAREA
404 select FB_CFB_IMAGEBLIT
406 Say Y to enable the Framebuffer driver for the CLPS7111 and
410 bool "SA-1100 LCD support"
411 depends on (FB = y) && ARM && ARCH_SA1100
412 select FB_CFB_FILLRECT
413 select FB_CFB_COPYAREA
414 select FB_CFB_IMAGEBLIT
416 This is a framebuffer device for the SA-1100 LCD Controller.
417 See <http://www.linux-fbdev.org/> for information on framebuffer
420 If you plan to use the LCD display with your SA-1100 system, say
424 tristate "Freescale i.MX LCD support"
425 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
426 select FB_CFB_FILLRECT
427 select FB_CFB_COPYAREA
428 select FB_CFB_IMAGEBLIT
431 tristate "CyberPro 2000/2010/5000 support"
432 depends on FB && PCI && (BROKEN || !SPARC64)
433 select FB_CFB_FILLRECT
434 select FB_CFB_COPYAREA
435 select FB_CFB_IMAGEBLIT
437 This enables support for the Integraphics CyberPro 20x0 and 5000
438 VGA chips used in the Rebel.com Netwinder and other machines.
439 Say Y if you have a NetWinder or a graphics card containing this
440 device, otherwise say N.
444 depends on (FB = y) && APOLLO
446 select FB_CFB_FILLRECT
447 select FB_CFB_IMAGEBLIT
451 depends on (FB = y) && Q40
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
458 tristate "Amiga native chipset support"
459 depends on FB && AMIGA
461 This is the frame buffer device driver for the builtin graphics
462 chipset found in Amigas.
464 To compile this driver as a module, choose M here: the
465 module will be called amifb.
468 bool "Amiga OCS chipset support"
471 This enables support for the original Agnus and Denise video chips,
472 found in the Amiga 1000 and most A500's and A2000's. If you intend
473 to run Linux on any of these systems, say Y; otherwise say N.
476 bool "Amiga ECS chipset support"
479 This enables support for the Enhanced Chip Set, found in later
480 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
481 you intend to run Linux on any of these systems, say Y; otherwise
485 bool "Amiga AGA chipset support"
488 This enables support for the Advanced Graphics Architecture (also
489 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
490 and CD32. If you intend to run Linux on any of these systems, say Y;
494 bool "Amiga FrameMaster II/Rainbow II support"
495 depends on (FB = y) && ZORRO
496 select FB_CFB_FILLRECT
497 select FB_CFB_COPYAREA
498 select FB_CFB_IMAGEBLIT
500 This is the frame buffer device driver for the Amiga FrameMaster
501 card from BSC (exhibited 1992 but not shipped as a CBM product).
504 tristate "Arc Monochrome LCD board support"
506 select FB_SYS_FILLRECT
507 select FB_SYS_COPYAREA
508 select FB_SYS_IMAGEBLIT
511 This enables support for the Arc Monochrome LCD board. The board
512 is based on the KS-108 lcd controller and is typically a matrix
513 of 2*n chips. This driver was tested with a 128x64 panel. This
514 driver supports it for use with x86 SBCs through a 16 bit GPIO
515 interface (8 bit data, 8 bit control). If you anticipate using
516 this driver, say Y or M; otherwise say N. You must specify the
517 GPIO IO address to be used for setting control and data.
520 bool "Atari native chipset support"
521 depends on (FB = y) && ATARI
522 select FB_CFB_FILLRECT
523 select FB_CFB_COPYAREA
524 select FB_CFB_IMAGEBLIT
526 This is the frame buffer device driver for the builtin graphics
527 chipset found in Ataris.
530 bool "Open Firmware frame buffer device support"
531 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
537 Say Y if you want support with Open Firmware for your graphics
541 bool "Apple \"control\" display support"
542 depends on (FB = y) && PPC_PMAC && PPC32
543 select FB_CFB_FILLRECT
544 select FB_CFB_COPYAREA
545 select FB_CFB_IMAGEBLIT
548 This driver supports a frame buffer for the graphics adapter in the
549 Power Macintosh 7300 and others.
552 bool "Apple \"platinum\" display support"
553 depends on (FB = y) && PPC_PMAC && PPC32
554 select FB_CFB_FILLRECT
555 select FB_CFB_COPYAREA
556 select FB_CFB_IMAGEBLIT
559 This driver supports a frame buffer for the "platinum" graphics
560 adapter in some Power Macintoshes.
563 bool "Apple \"valkyrie\" display support"
564 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
565 select FB_CFB_FILLRECT
566 select FB_CFB_COPYAREA
567 select FB_CFB_IMAGEBLIT
570 This driver supports a frame buffer for the "valkyrie" graphics
571 adapter in some Power Macintoshes.
574 bool "Chips 65550 display support"
575 depends on (FB = y) && PPC32 && PCI
576 select FB_CFB_FILLRECT
577 select FB_CFB_COPYAREA
578 select FB_CFB_IMAGEBLIT
580 This is the frame buffer device driver for the Chips & Technologies
581 65550 graphics chip in PowerBooks.
584 bool "Asiliant (Chips) 69000 display support"
585 depends on (FB = y) && PCI
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
590 This is the frame buffer device driver for the Asiliant 69030 chipset
593 bool "IMS Twin Turbo display support"
594 depends on (FB = y) && PCI
595 select FB_CFB_IMAGEBLIT
596 select FB_MACMODES if PPC
598 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
599 many Macintosh and compatible computers.
602 tristate "VGA 16-color graphics support"
603 depends on FB && (X86 || PPC)
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 select FONT_8x16 if FRAMEBUFFER_CONSOLE
610 This is the frame buffer device driver for VGA 16 color graphic
611 cards. Say Y if you have such a card.
613 To compile this driver as a module, choose M here: the
614 module will be called vga16fb.
616 config FB_BF54X_LQ043
617 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
618 depends on FB && (BF54x) && !BF542
619 select FB_CFB_FILLRECT
620 select FB_CFB_COPYAREA
621 select FB_CFB_IMAGEBLIT
623 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
625 config FB_BFIN_T350MCQB
626 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
627 depends on FB && BLACKFIN
629 select FB_CFB_FILLRECT
630 select FB_CFB_COPYAREA
631 select FB_CFB_IMAGEBLIT
633 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
634 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
635 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
637 config FB_BFIN_LQ035Q1
638 tristate "SHARP LQ035Q1DH02 TFT LCD"
639 depends on FB && BLACKFIN && SPI
640 select FB_CFB_FILLRECT
641 select FB_CFB_COPYAREA
642 select FB_CFB_IMAGEBLIT
645 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
646 the Blackfin Landscape LCD EZ-Extender Card.
647 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
648 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
650 To compile this driver as a module, choose M here: the
651 module will be called bfin-lq035q1-fb.
653 config FB_BF537_LQ035
654 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
655 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
656 select FB_CFB_FILLRECT
657 select FB_CFB_COPYAREA
658 select FB_CFB_IMAGEBLIT
661 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
664 To compile this driver as a module, choose M here: the
665 module will be called bf537-lq035.
668 tristate "Blackfin ADV7393 Video encoder"
669 depends on FB && BLACKFIN
671 select FB_CFB_FILLRECT
672 select FB_CFB_COPYAREA
673 select FB_CFB_IMAGEBLIT
675 This is the framebuffer device for a ADV7393 video encoder
676 attached to a Blackfin on the PPI port.
677 If your Blackfin board has a ADV7393 select Y.
679 To compile this driver as a module, choose M here: the
680 module will be called bfin_adv7393fb.
683 prompt "Video mode support"
684 depends on FB_BFIN_7393
694 bool 'NTSC 640x480 (Experimental)'
697 bool 'PAL 640x480 (Experimental)'
700 bool 'NTSC 720x480 YCbCR input'
703 bool 'PAL 720x576 YCbCR input'
708 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
709 depends on (FB_BFIN_7393)
710 default ADV7393_1XMEM
720 tristate "HP STI frame buffer device support"
721 depends on FB && PARISC
722 select FB_CFB_FILLRECT
723 select FB_CFB_COPYAREA
724 select FB_CFB_IMAGEBLIT
729 STI refers to the HP "Standard Text Interface" which is a set of
730 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
731 Enabling this option will implement the linux framebuffer device
732 using calls to the STI BIOS routines for initialisation.
734 If you enable this option, you will get a planar framebuffer device
735 /dev/fb which will work on the most common HP graphic cards of the
736 NGLE family, including the artist chips (in the 7xx and Bxxx series),
737 HCRX, HCRX24, CRX, CRX24 and VisEG series.
739 It is safe to enable this option, so you should probably say "Y".
742 bool "Generic Macintosh display support"
743 depends on (FB = y) && MAC
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
751 depends on (FB = y) && DIO
752 select FB_CFB_IMAGEBLIT
756 tristate "TGA/SFB+ framebuffer support"
757 depends on FB && (ALPHA || TC)
758 select FB_CFB_FILLRECT
759 select FB_CFB_COPYAREA
760 select FB_CFB_IMAGEBLIT
763 This is the frame buffer device driver for generic TGA and SFB+
764 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
765 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
766 TURBOchannel cards, also known as PMAGD-A, -B and -C.
768 Due to hardware limitations ZLX-E2 and E3 cards are not supported
769 for DECstation 5000/200 systems. Additionally due to firmware
770 limitations these cards may cause troubles with booting DECstation
771 5000/240 and /260 systems, but are fully supported under Linux if
772 you manage to get it going. ;-)
774 Say Y if you have one of those.
777 tristate "Userspace VESA VGA graphics support"
778 depends on FB && CONNECTOR
779 select FB_CFB_FILLRECT
780 select FB_CFB_COPYAREA
781 select FB_CFB_IMAGEBLIT
782 select FB_MODE_HELPERS
784 This is the frame buffer driver for generic VBE 2.0 compliant
785 graphic cards. It can also take advantage of VBE 3.0 features,
786 such as refresh rate adjustment.
788 This driver generally provides more features than vesafb but
789 requires a userspace helper application called 'v86d'. See
790 <file:Documentation/fb/uvesafb.txt> for more information.
795 bool "VESA VGA graphics support"
796 depends on (FB = y) && X86
797 select FB_CFB_FILLRECT
798 select FB_CFB_COPYAREA
799 select FB_CFB_IMAGEBLIT
800 select FB_BOOT_VESA_SUPPORT
802 This is the frame buffer device driver for generic VESA 2.0
803 compliant graphic cards. The older VESA 1.2 cards are not supported.
804 You will get a boot time penguin logo at no additional cost. Please
805 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
808 bool "EFI-based Framebuffer Support"
809 depends on (FB = y) && X86 && EFI
810 select FB_CFB_FILLRECT
811 select FB_CFB_COPYAREA
812 select FB_CFB_IMAGEBLIT
814 This is the EFI frame buffer device driver. If the firmware on
815 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
816 using the EFI framebuffer as your console.
819 tristate "N411 Apollo/Hecuba devkit support"
820 depends on FB && X86 && MMU
821 select FB_SYS_FILLRECT
822 select FB_SYS_COPYAREA
823 select FB_SYS_IMAGEBLIT
825 select FB_DEFERRED_IO
828 This enables support for the Apollo display controller in its
829 Hecuba form using the n411 devkit.
832 tristate "Hercules mono graphics support"
835 Say Y here if you have a Hercules mono graphics card.
837 To compile this driver as a module, choose M here: the
838 module will be called hgafb.
840 As this card technology is at least 25 years old,
841 most people will answer N here.
844 tristate "SGI Visual Workstation framebuffer support"
845 depends on FB && X86_VISWS
846 select FB_CFB_FILLRECT
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 SGI Visual Workstation support for framebuffer graphics.
853 bool "SGI Graphics Backend frame buffer support"
854 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
855 select FB_CFB_FILLRECT
856 select FB_CFB_COPYAREA
857 select FB_CFB_IMAGEBLIT
859 This is the frame buffer device driver for SGI Graphics Backend.
860 This chip is used in SGI O2 and Visual Workstation 320/540.
863 int "Video memory size in MB"
867 This is the amount of memory reserved for the framebuffer,
868 which can be any value between 1MB and 8MB.
871 bool "SBUS and UPA framebuffers"
872 depends on (FB = y) && SPARC
874 Say Y if you want support for SBUS or UPA based frame buffer device.
878 depends on (FB = y) && (SPARC && FB_SBUS)
879 select FB_CFB_FILLRECT
880 select FB_CFB_COPYAREA
881 select FB_CFB_IMAGEBLIT
883 This is the frame buffer device driver for the BWtwo frame buffer.
886 bool "CGthree support"
887 depends on (FB = y) && (SPARC && FB_SBUS)
888 select FB_CFB_FILLRECT
889 select FB_CFB_COPYAREA
890 select FB_CFB_IMAGEBLIT
892 This is the frame buffer device driver for the CGthree frame buffer.
895 bool "CGsix (GX,TurboGX) support"
896 depends on (FB = y) && (SPARC && FB_SBUS)
897 select FB_CFB_COPYAREA
898 select FB_CFB_IMAGEBLIT
900 This is the frame buffer device driver for the CGsix (GX, TurboGX)
904 bool "Creator/Creator3D/Elite3D support"
905 depends on FB_SBUS && SPARC64
906 select FB_CFB_COPYAREA
907 select FB_CFB_IMAGEBLIT
909 This is the frame buffer device driver for the Creator, Creator3D,
910 and Elite3D graphics boards.
913 bool "TCX (SS4/SS5 only) support"
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the frame buffer device driver for the TCX 24/8bit frame
923 bool "CGfourteen (SX) support"
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 This is the frame buffer device driver for the CGfourteen frame
930 buffer on Desktop SPARCsystems with the SX graphics option.
933 bool "P9100 (Sparcbook 3 only) support"
935 select FB_CFB_FILLRECT
936 select FB_CFB_COPYAREA
937 select FB_CFB_IMAGEBLIT
939 This is the frame buffer device driver for the P9100 card
940 supported on Sparcbook 3 machines.
943 bool "Leo (ZX) support"
945 select FB_CFB_FILLRECT
946 select FB_CFB_COPYAREA
947 select FB_CFB_IMAGEBLIT
949 This is the frame buffer device driver for the SBUS-based Sun ZX
950 (leo) frame buffer cards.
953 bool "IGA 168x display support"
954 depends on (FB = y) && SPARC32
955 select FB_CFB_FILLRECT
956 select FB_CFB_COPYAREA
957 select FB_CFB_IMAGEBLIT
959 This is the framebuffer device for the INTERGRAPHICS 1680 and
960 successor frame buffer cards.
963 bool "Sun XVR-500 3DLABS Wildcat support"
964 depends on (FB = y) && PCI && SPARC64
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
969 This is the framebuffer device for the Sun XVR-500 and similar
970 graphics cards based upon the 3DLABS Wildcat chipset. The driver
971 only works on sparc64 systems where the system firmware has
972 mostly initialized the card already. It is treated as a
973 completely dumb framebuffer device.
976 bool "Sun XVR-2500 3DLABS Wildcat support"
977 depends on (FB = y) && PCI && SPARC64
978 select FB_CFB_FILLRECT
979 select FB_CFB_COPYAREA
980 select FB_CFB_IMAGEBLIT
982 This is the framebuffer device for the Sun XVR-2500 and similar
983 graphics cards based upon the 3DLABS Wildcat chipset. The driver
984 only works on sparc64 systems where the system firmware has
985 mostly initialized the card already. It is treated as a
986 completely dumb framebuffer device.
989 bool "Sun XVR-1000 support"
990 depends on (FB = y) && SPARC64
991 select FB_CFB_FILLRECT
992 select FB_CFB_COPYAREA
993 select FB_CFB_IMAGEBLIT
995 This is the framebuffer device for the Sun XVR-1000 and similar
996 graphics cards. The driver only works on sparc64 systems where
997 the system firmware has mostly initialized the card already. It
998 is treated as a completely dumb framebuffer device.
1001 tristate "NEC PowerVR 2 display support"
1002 depends on FB && SH_DREAMCAST
1003 select FB_CFB_FILLRECT
1004 select FB_CFB_COPYAREA
1005 select FB_CFB_IMAGEBLIT
1007 Say Y here if you have a PowerVR 2 card in your box. If you plan to
1008 run linux on your Dreamcast, you will have to say Y here.
1009 This driver may or may not work on other PowerVR 2 cards, but is
1010 totally untested. Use at your own risk. If unsure, say N.
1012 To compile this driver as a module, choose M here: the
1013 module will be called pvr2fb.
1015 You can pass several parameters to the driver at boot time or at
1016 module load time. The parameters look like "video=pvr2:XXX", where
1017 the meaning of XXX can be found at the end of the main source file
1018 (<file:drivers/video/pvr2fb.c>). Please see the file
1019 <file:Documentation/fb/pvr2fb.txt>.
1022 bool "Epson 1355 framebuffer support"
1023 depends on (FB = y) && ARCH_CEIVA
1024 select FB_CFB_FILLRECT
1025 select FB_CFB_COPYAREA
1026 select FB_CFB_IMAGEBLIT
1028 Build in support for the SED1355 Epson Research Embedded RAMDAC
1029 LCD/CRT Controller (since redesignated as the S1D13505) as a
1030 framebuffer. Product specs at
1031 <http://vdc.epson.com/>.
1034 tristate "Epson S1D13XXX framebuffer support"
1036 select FB_CFB_FILLRECT
1037 select FB_CFB_COPYAREA
1038 select FB_CFB_IMAGEBLIT
1040 Support for S1D13XXX framebuffer device family (currently only
1041 working with S1D13806). Product specs at
1042 <http://vdc.epson.com/>
1045 tristate "AT91/AT32 LCD Controller support"
1046 depends on FB && HAVE_FB_ATMEL
1047 select FB_CFB_FILLRECT
1048 select FB_CFB_COPYAREA
1049 select FB_CFB_IMAGEBLIT
1051 This enables support for the AT91/AT32 LCD Controller.
1054 bool "Frame Buffer in internal SRAM"
1055 depends on FB_ATMEL && ARCH_AT91SAM9261
1057 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1058 to let frame buffer in external SDRAM.
1061 bool "Use a STN display with AT91/AT32 LCD Controller"
1062 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1065 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1066 Controller. Say N if you want to connect a TFT.
1071 tristate "nVidia Framebuffer Support"
1072 depends on FB && PCI
1073 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1074 select FB_MODE_HELPERS
1075 select FB_CFB_FILLRECT
1076 select FB_CFB_COPYAREA
1077 select FB_CFB_IMAGEBLIT
1081 This driver supports graphics boards with the nVidia chips, TNT
1082 and newer. For very old chipsets, such as the RIVA128, then use
1084 Say Y if you have such a graphics board.
1086 To compile this driver as a module, choose M here: the
1087 module will be called nvidiafb.
1089 config FB_NVIDIA_I2C
1090 bool "Enable DDC Support"
1091 depends on FB_NVIDIA
1094 This enables I2C support for nVidia Chipsets. This is used
1095 only for getting EDID information from the attached display
1096 allowing for robust video mode handling and switching.
1098 Because fbdev-2.6 requires that drivers must be able to
1099 independently validate video mode parameters, you should say Y
1102 config FB_NVIDIA_DEBUG
1103 bool "Lots of debug output"
1104 depends on FB_NVIDIA
1107 Say Y here if you want the nVidia driver to output all sorts
1108 of debugging information to provide to the maintainer when
1109 something goes wrong.
1111 config FB_NVIDIA_BACKLIGHT
1112 bool "Support for backlight control"
1113 depends on FB_NVIDIA
1116 Say Y here if you want to control the backlight of your display.
1119 tristate "nVidia Riva support"
1120 depends on FB && PCI
1121 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1122 select FB_MODE_HELPERS
1123 select FB_CFB_FILLRECT
1124 select FB_CFB_COPYAREA
1125 select FB_CFB_IMAGEBLIT
1129 This driver supports graphics boards with the nVidia Riva/Geforce
1131 Say Y if you have such a graphics board.
1133 To compile this driver as a module, choose M here: the
1134 module will be called rivafb.
1137 bool "Enable DDC Support"
1141 This enables I2C support for nVidia Chipsets. This is used
1142 only for getting EDID information from the attached display
1143 allowing for robust video mode handling and switching.
1145 Because fbdev-2.6 requires that drivers must be able to
1146 independently validate video mode parameters, you should say Y
1149 config FB_RIVA_DEBUG
1150 bool "Lots of debug output"
1154 Say Y here if you want the Riva driver to output all sorts
1155 of debugging information to provide to the maintainer when
1156 something goes wrong.
1158 config FB_RIVA_BACKLIGHT
1159 bool "Support for backlight control"
1163 Say Y here if you want to control the backlight of your display.
1166 tristate "Intel 810/815 support (EXPERIMENTAL)"
1167 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1168 select FB_MODE_HELPERS
1169 select FB_CFB_FILLRECT
1170 select FB_CFB_COPYAREA
1171 select FB_CFB_IMAGEBLIT
1174 This driver supports the on-board graphics built in to the Intel 810
1175 and 815 chipsets. Say Y if you have and plan to use such a board.
1177 To compile this driver as a module, choose M here: the
1178 module will be called i810fb.
1180 For more information, please read
1181 <file:Documentation/fb/intel810.txt>
1184 bool "use VESA Generalized Timing Formula"
1187 If you say Y, then the VESA standard, Generalized Timing Formula
1188 or GTF, will be used to calculate the required video timing values
1189 per video mode. Since the GTF allows nondiscrete timings
1190 (nondiscrete being a range of values as opposed to discrete being a
1191 set of values), you'll be able to use any combination of horizontal
1192 and vertical resolutions, and vertical refresh rates without having
1193 to specify your own timing parameters. This is especially useful
1194 to maximize the performance of an aging display, or if you just
1195 have a display with nonstandard dimensions. A VESA compliant
1196 monitor is recommended, but can still work with non-compliant ones.
1197 If you need or want this, then select this option. The timings may
1198 not be compliant with Intel's recommended values. Use at your own
1201 If you say N, the driver will revert to discrete video timings
1202 using a set recommended by Intel in their documentation.
1207 bool "Enable DDC Support"
1208 depends on FB_I810 && FB_I810_GTF
1213 tristate "Intel LE80578 (Vermilion) support"
1214 depends on FB && PCI && X86
1215 select FB_MODE_HELPERS
1216 select FB_CFB_FILLRECT
1217 select FB_CFB_COPYAREA
1218 select FB_CFB_IMAGEBLIT
1220 This driver supports the LE80578 (Vermilion Range) chipset
1222 config FB_CARILLO_RANCH
1223 tristate "Intel Carillo Ranch support"
1224 depends on FB_LE80578 && FB && PCI && X86
1226 This driver supports the LE80578 (Carillo Ranch) board
1229 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1230 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1231 select FB_MODE_HELPERS
1232 select FB_CFB_FILLRECT
1233 select FB_CFB_COPYAREA
1234 select FB_CFB_IMAGEBLIT
1235 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1236 depends on !DRM_I915
1238 This driver supports the on-board graphics built in to the Intel
1239 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1240 Say Y if you have and plan to use such a board.
1242 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1244 To compile this driver as a module, choose M here: the
1245 module will be called intelfb.
1247 For more information, please read <file:Documentation/fb/intelfb.txt>
1249 config FB_INTEL_DEBUG
1250 bool "Intel driver Debug Messages"
1253 Say Y here if you want the Intel driver to output all sorts
1254 of debugging information to provide to the maintainer when
1255 something goes wrong.
1258 bool "DDC/I2C for Intel framebuffer support"
1263 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1266 tristate "Matrox acceleration"
1267 depends on FB && PCI
1268 select FB_CFB_FILLRECT
1269 select FB_CFB_COPYAREA
1270 select FB_CFB_IMAGEBLIT
1271 select FB_TILEBLITTING
1272 select FB_MACMODES if PPC_PMAC
1274 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1275 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1276 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1277 Matrox G400, G450 or G550 card in your box.
1279 To compile this driver as a module, choose M here: the
1280 module will be called matroxfb.
1282 You can pass several parameters to the driver at boot time or at
1283 module load time. The parameters look like "video=matroxfb:XXX", and
1284 are described in <file:Documentation/fb/matroxfb.txt>.
1286 config FB_MATROX_MILLENIUM
1287 bool "Millennium I/II support"
1288 depends on FB_MATROX
1290 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1291 video card. If you select "Advanced lowlevel driver options" below,
1292 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1293 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1294 also use font widths different from 8.
1296 config FB_MATROX_MYSTIQUE
1297 bool "Mystique support"
1298 depends on FB_MATROX
1300 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1301 video card. If you select "Advanced lowlevel driver options" below,
1302 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1303 packed pixel and 32 bpp packed pixel. You can also use font widths
1307 bool "G100/G200/G400/G450/G550 support"
1308 depends on FB_MATROX
1310 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1311 video card. If you select "Advanced lowlevel driver options", you
1312 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1313 pixel and 32 bpp packed pixel. You can also use font widths
1316 If you need support for G400 secondary head, you must say Y to
1317 "Matrox I2C support" and "G400 second head support" right below.
1318 G450/G550 secondary head and digital output are supported without
1321 The driver starts in monitor mode. You must use the matroxset tool
1322 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1323 swap primary and secondary head outputs, or to change output mode.
1324 Secondary head driver always start in 640x480 resolution and you
1325 must use fbset to change it.
1327 Do not forget that second head supports only 16 and 32 bpp
1328 packed pixels, so it is a good idea to compile them into the kernel
1329 too. You can use only some font widths, as the driver uses generic
1330 painting procedures (the secondary head does not use acceleration
1333 G450/G550 hardware can display TV picture only from secondary CRTC,
1334 and it performs no scaling, so picture must have 525 or 625 lines.
1336 config FB_MATROX_I2C
1337 tristate "Matrox I2C support"
1338 depends on FB_MATROX
1341 This drivers creates I2C buses which are needed for accessing the
1342 DDC (I2C) bus present on all Matroxes, an I2C bus which
1343 interconnects Matrox optional devices, like MGA-TVO on G200 and
1344 G400, and the secondary head DDC bus, present on G400 only.
1346 You can say Y or M here if you want to experiment with monitor
1347 detection code. You must say Y or M here if you want to use either
1348 second head of G400 or MGA-TVO on G200 or G400.
1350 If you compile it as module, it will create a module named
1353 config FB_MATROX_MAVEN
1354 tristate "G400 second head support"
1355 depends on FB_MATROX_G && FB_MATROX_I2C
1357 WARNING !!! This support does not work with G450 !!!
1359 Say Y or M here if you want to use a secondary head (meaning two
1360 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1361 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1362 secondary head output is blanked while you are in X. With XFree
1363 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1364 the fbdev driver on first head and the fbdev driver on second head.
1366 If you compile it as module, two modules are created,
1367 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1368 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1369 also load i2c-matroxfb to get it to run.
1371 The driver starts in monitor mode and you must use the matroxset
1373 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1374 PAL or NTSC or to swap primary and secondary head outputs.
1375 Secondary head driver also always start in 640x480 resolution, you
1376 must use fbset to change it.
1378 Also do not forget that second head supports only 16 and 32 bpp
1379 packed pixels, so it is a good idea to compile them into the kernel
1380 too. You can use only some font widths, as the driver uses generic
1381 painting procedures (the secondary head does not use acceleration
1385 tristate "ATI Radeon display support"
1386 depends on FB && PCI
1387 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1388 select FB_MODE_HELPERS
1389 select FB_CFB_FILLRECT
1390 select FB_CFB_COPYAREA
1391 select FB_CFB_IMAGEBLIT
1392 select FB_MACMODES if PPC_OF
1394 Choose this option if you want to use an ATI Radeon graphics card as
1395 a framebuffer device. There are both PCI and AGP versions. You
1396 don't need to choose this to run the Radeon in plain VGA mode.
1398 There is a product page at
1399 http://products.amd.com/en-us/GraphicCardResult.aspx
1401 config FB_RADEON_I2C
1402 bool "DDC/I2C for ATI Radeon support"
1403 depends on FB_RADEON
1407 Say Y here if you want DDC/I2C support for your Radeon board.
1409 config FB_RADEON_BACKLIGHT
1410 bool "Support for backlight control"
1411 depends on FB_RADEON
1414 Say Y here if you want to control the backlight of your display.
1416 config FB_RADEON_DEBUG
1417 bool "Lots of debug output from Radeon driver"
1418 depends on FB_RADEON
1421 Say Y here if you want the Radeon driver to output all sorts
1422 of debugging information to provide to the maintainer when
1423 something goes wrong.
1426 tristate "ATI Rage128 display support"
1427 depends on FB && PCI
1428 select FB_CFB_FILLRECT
1429 select FB_CFB_COPYAREA
1430 select FB_CFB_IMAGEBLIT
1431 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1432 select FB_MACMODES if PPC_PMAC
1434 This driver supports graphics boards with the ATI Rage128 chips.
1435 Say Y if you have such a graphics board and read
1436 <file:Documentation/fb/aty128fb.txt>.
1438 To compile this driver as a module, choose M here: the
1439 module will be called aty128fb.
1441 config FB_ATY128_BACKLIGHT
1442 bool "Support for backlight control"
1443 depends on FB_ATY128
1446 Say Y here if you want to control the backlight of your display.
1449 tristate "ATI Mach64 display support" if PCI || ATARI
1450 depends on FB && !SPARC32
1451 select FB_CFB_FILLRECT
1452 select FB_CFB_COPYAREA
1453 select FB_CFB_IMAGEBLIT
1454 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1455 select FB_MACMODES if PPC
1457 This driver supports graphics boards with the ATI Mach64 chips.
1458 Say Y if you have such a graphics board.
1460 To compile this driver as a module, choose M here: the
1461 module will be called atyfb.
1464 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1465 depends on PCI && FB_ATY
1466 default y if SPARC64 && PCI
1468 Say Y here to support use of ATI's 64-bit Rage boards (or other
1469 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1470 framebuffer device. The ATI product support page for these boards
1471 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1473 config FB_ATY_GENERIC_LCD
1474 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1475 depends on FB_ATY_CT
1477 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1478 Rage XC, or Rage XL chipset.
1481 bool "Mach64 GX support" if PCI
1485 Say Y here to support use of the ATI Mach64 Graphics Expression
1486 board (or other boards based on the Mach64 GX chipset) as a
1487 framebuffer device. The ATI product support page for these boards
1489 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1491 config FB_ATY_BACKLIGHT
1492 bool "Support for backlight control"
1496 Say Y here if you want to control the backlight of your display.
1499 tristate "S3 Trio/Virge support"
1500 depends on FB && PCI
1501 select FB_CFB_FILLRECT
1502 select FB_CFB_COPYAREA
1503 select FB_CFB_IMAGEBLIT
1504 select FB_TILEBLITTING
1507 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1509 Driver for graphics boards with S3 Trio / S3 Virge chip.
1512 tristate "S3 Savage support"
1513 depends on FB && PCI && EXPERIMENTAL
1514 select FB_MODE_HELPERS
1515 select FB_CFB_FILLRECT
1516 select FB_CFB_COPYAREA
1517 select FB_CFB_IMAGEBLIT
1520 This driver supports notebooks and computers with S3 Savage PCI/AGP
1523 Say Y if you have such a graphics card.
1525 To compile this driver as a module, choose M here; the module
1526 will be called savagefb.
1528 config FB_SAVAGE_I2C
1529 bool "Enable DDC2 Support"
1530 depends on FB_SAVAGE
1533 This enables I2C support for S3 Savage Chipsets. This is used
1534 only for getting EDID information from the attached display
1535 allowing for robust video mode handling and switching.
1537 Because fbdev-2.6 requires that drivers must be able to
1538 independently validate video mode parameters, you should say Y
1541 config FB_SAVAGE_ACCEL
1542 bool "Enable Console Acceleration"
1543 depends on FB_SAVAGE
1546 This option will compile in console acceleration support. If
1547 the resulting framebuffer console has bothersome glitches, then
1551 tristate "SiS/XGI display support"
1552 depends on FB && PCI
1553 select FB_CFB_FILLRECT
1554 select FB_CFB_COPYAREA
1555 select FB_CFB_IMAGEBLIT
1556 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1558 This is the frame buffer device driver for the SiS 300, 315, 330
1559 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1560 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1562 To compile this driver as a module, choose M here; the module
1563 will be called sisfb.
1566 bool "SiS 300 series support"
1569 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1572 bool "SiS 315/330/340 series and XGI support"
1575 Say Y here to support use of the SiS 315, 330 and 340 series
1576 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1577 as XGI V3XT, V5, V8 and Z7.
1580 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1581 depends on FB && PCI && X86
1582 select FB_CFB_FILLRECT
1583 select FB_CFB_COPYAREA
1584 select FB_CFB_IMAGEBLIT
1589 This is the frame buffer device driver for Graphics chips of VIA
1590 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1591 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1593 Say Y if you have a VIA UniChrome graphics board.
1595 To compile this driver as a module, choose M here: the
1596 module will be called viafb.
1600 config FB_VIA_DIRECT_PROCFS
1601 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1605 Allow direct hardware access to some output registers via procfs.
1606 This is dangerous but may provide the only chance to get the
1607 correct output device configuration.
1608 Its use is strongly discouraged.
1613 tristate "NeoMagic display support"
1614 depends on FB && PCI
1615 select FB_MODE_HELPERS
1616 select FB_CFB_FILLRECT
1617 select FB_CFB_COPYAREA
1618 select FB_CFB_IMAGEBLIT
1621 This driver supports notebooks with NeoMagic PCI chips.
1622 Say Y if you have such a graphics card.
1624 To compile this driver as a module, choose M here: the
1625 module will be called neofb.
1628 tristate "IMG Kyro support"
1629 depends on FB && PCI
1630 select FB_CFB_FILLRECT
1631 select FB_CFB_COPYAREA
1632 select FB_CFB_IMAGEBLIT
1634 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1637 To compile this driver as a module, choose M here: the
1638 module will be called kyrofb.
1641 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1642 depends on FB && PCI
1643 select FB_CFB_IMAGEBLIT
1644 select FB_CFB_FILLRECT
1645 select FB_CFB_COPYAREA
1646 select FB_MODE_HELPERS
1648 This driver supports graphics boards with the 3Dfx Banshee,
1649 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1650 such a graphics board.
1652 To compile this driver as a module, choose M here: the
1653 module will be called tdfxfb.
1655 config FB_3DFX_ACCEL
1656 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1657 depends on FB_3DFX && EXPERIMENTAL
1659 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1660 device driver with acceleration functions.
1663 bool "Enable DDC/I2C support"
1664 depends on FB_3DFX && EXPERIMENTAL
1668 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1671 tristate "3Dfx Voodoo Graphics (sst1) support"
1672 depends on FB && PCI
1673 select FB_CFB_FILLRECT
1674 select FB_CFB_COPYAREA
1675 select FB_CFB_IMAGEBLIT
1677 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1678 Voodoo2 (cvg) based graphics card.
1680 To compile this driver as a module, choose M here: the
1681 module will be called sstfb.
1683 WARNING: Do not use any application that uses the 3D engine
1684 (namely glide) while using this driver.
1685 Please read the <file:Documentation/fb/sstfb.txt> for supported
1686 options and other important info support.
1689 tristate "VIA VT8623 support"
1690 depends on FB && PCI
1691 select FB_CFB_FILLRECT
1692 select FB_CFB_COPYAREA
1693 select FB_CFB_IMAGEBLIT
1694 select FB_TILEBLITTING
1697 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1699 Driver for CastleRock integrated graphics core in the
1700 VIA VT8623 [Apollo CLE266] chipset.
1703 tristate "Trident/CyberXXX/CyberBlade support"
1704 depends on FB && PCI
1705 select FB_CFB_FILLRECT
1706 select FB_CFB_COPYAREA
1707 select FB_CFB_IMAGEBLIT
1709 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1710 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1712 There are also integrated versions of these chips called CyberXXXX,
1713 CyberImage or CyberBlade. These chips are mostly found in laptops
1714 but also on some motherboards including early VIA EPIA motherboards.
1715 For more information, read <file:Documentation/fb/tridentfb.txt>
1717 Say Y if you have such a graphics board.
1719 To compile this driver as a module, choose M here: the
1720 module will be called tridentfb.
1723 tristate "ARK 2000PV support"
1724 depends on FB && PCI
1725 select FB_CFB_FILLRECT
1726 select FB_CFB_COPYAREA
1727 select FB_CFB_IMAGEBLIT
1728 select FB_TILEBLITTING
1731 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1733 Driver for PCI graphics boards with ARK 2000PV chip
1734 and ICS 5342 RAMDAC.
1737 tristate "Permedia3 support (EXPERIMENTAL)"
1738 depends on FB && PCI && EXPERIMENTAL
1739 select FB_CFB_FILLRECT
1740 select FB_CFB_COPYAREA
1741 select FB_CFB_IMAGEBLIT
1743 This is the frame buffer device driver for the 3DLabs Permedia3
1744 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1745 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1746 and maybe other boards.
1749 tristate "Fujitsu carmine frame buffer support"
1750 depends on FB && PCI
1751 select FB_CFB_FILLRECT
1752 select FB_CFB_COPYAREA
1753 select FB_CFB_IMAGEBLIT
1755 This is the frame buffer device driver for the Fujitsu Carmine chip.
1756 The driver provides two independent frame buffer devices.
1759 depends on FB_CARMINE
1760 prompt "DRAM timing"
1761 default FB_CARMINE_DRAM_EVAL
1763 config FB_CARMINE_DRAM_EVAL
1764 bool "Eval board timings"
1766 Use timings which work on the eval card.
1768 config CARMINE_DRAM_CUSTOM
1769 bool "Custom board timings"
1771 Use custom board timings.
1775 bool "Au1100 LCD Driver"
1776 depends on (FB = y) && MIPS && SOC_AU1100
1777 select FB_CFB_FILLRECT
1778 select FB_CFB_COPYAREA
1779 select FB_CFB_IMAGEBLIT
1781 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1782 various panels and CRTs by passing in kernel cmd line option
1783 au1100fb:panel=<name>.
1786 bool "Au1200 LCD Driver"
1787 depends on (FB = y) && MIPS && SOC_AU1200
1788 select FB_CFB_FILLRECT
1789 select FB_CFB_COPYAREA
1790 select FB_CFB_IMAGEBLIT
1792 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1793 various panels and CRTs by passing in kernel cmd line option
1794 au1200fb:panel=<name>.
1797 bool "VT8500 LCD Driver"
1798 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1799 select FB_WMT_GE_ROPS
1800 select FB_SYS_IMAGEBLIT
1802 This is the framebuffer driver for VIA VT8500 integrated LCD
1806 bool "WM8505 frame buffer support"
1807 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1808 select FB_WMT_GE_ROPS
1809 select FB_SYS_IMAGEBLIT
1811 This is the framebuffer driver for WonderMedia WM8505
1812 integrated LCD controller.
1814 source "drivers/video/geode/Kconfig"
1817 tristate "HD64461 Frame Buffer support"
1818 depends on FB && HD64461
1819 select FB_CFB_FILLRECT
1820 select FB_CFB_COPYAREA
1821 select FB_CFB_IMAGEBLIT
1823 This is the frame buffer device driver for the Hitachi HD64461 LCD
1827 bool "PMAG-AA TURBOchannel framebuffer support"
1828 depends on (FB = y) && TC
1829 select FB_CFB_FILLRECT
1830 select FB_CFB_COPYAREA
1831 select FB_CFB_IMAGEBLIT
1833 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1834 used mainly in the MIPS-based DECstation series.
1837 tristate "PMAG-BA TURBOchannel framebuffer support"
1839 select FB_CFB_FILLRECT
1840 select FB_CFB_COPYAREA
1841 select FB_CFB_IMAGEBLIT
1843 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1844 used mainly in the MIPS-based DECstation series.
1847 tristate "PMAGB-B TURBOchannel framebuffer support"
1849 select FB_CFB_FILLRECT
1850 select FB_CFB_COPYAREA
1851 select FB_CFB_IMAGEBLIT
1853 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1854 in the MIPS-based DECstation series. The card is currently only
1855 supported in 1280x1024x8 mode.
1858 bool "Maxine (Personal DECstation) onboard framebuffer support"
1859 depends on (FB = y) && MACH_DECSTATION
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1864 Support for the onboard framebuffer (1024x768x8) in the Personal
1865 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1869 bool "G364 frame buffer support"
1870 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1871 select FB_CFB_FILLRECT
1872 select FB_CFB_COPYAREA
1873 select FB_CFB_IMAGEBLIT
1875 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1876 Olivetti M700-10 systems.
1879 bool "Motorola 68328 native frame buffer support"
1880 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1881 select FB_CFB_FILLRECT
1882 select FB_CFB_COPYAREA
1883 select FB_CFB_IMAGEBLIT
1885 Say Y here if you want to support the built-in frame buffer of
1886 the Motorola 68328 CPU family.
1889 tristate "PXA168/910 LCD framebuffer support"
1890 depends on FB && (CPU_PXA168 || CPU_PXA910)
1891 select FB_CFB_FILLRECT
1892 select FB_CFB_COPYAREA
1893 select FB_CFB_IMAGEBLIT
1895 Frame buffer driver for the built-in LCD controller in the Marvell
1899 tristate "PXA LCD framebuffer support"
1900 depends on FB && ARCH_PXA
1901 select FB_CFB_FILLRECT
1902 select FB_CFB_COPYAREA
1903 select FB_CFB_IMAGEBLIT
1905 Frame buffer driver for the built-in LCD controller in the Intel
1908 This driver is also available as a module ( = code which can be
1909 inserted and removed from the running kernel whenever you want). The
1910 module will be called pxafb. If you want to compile it as a module,
1911 say M here and read <file:Documentation/kbuild/modules.txt>.
1915 config FB_PXA_OVERLAY
1916 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1918 depends on FB_PXA && (PXA27x || PXA3xx)
1920 config FB_PXA_SMARTPANEL
1921 bool "PXA Smartpanel LCD support"
1925 config FB_PXA_PARAMETERS
1926 bool "PXA LCD command line parameters"
1930 Enable the use of kernel command line or module parameters
1931 to configure the physical properties of the LCD panel when
1932 using the PXA LCD driver.
1934 This option allows you to override the panel parameters
1935 supplied by the platform in order to support multiple
1936 different models of flatpanel. If you will only be using a
1937 single model of flatpanel then you can safely leave this
1940 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1943 tristate "PXA3xx 2D graphics accelerator driver"
1946 Kernelspace driver for the 2D graphics controller unit (GCU)
1947 found on PXA3xx processors. There is a counterpart driver in the
1948 DirectFB suite, see http://www.directfb.org/
1950 If you compile this as a module, it will be called pxa3xx_gcu.
1953 tristate "2700G LCD framebuffer support"
1954 depends on FB && ARCH_PXA
1955 select FB_CFB_FILLRECT
1956 select FB_CFB_COPYAREA
1957 select FB_CFB_IMAGEBLIT
1959 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1963 bool "Enable debugging info via debugfs"
1964 depends on FB_MBX && DEBUG_FS
1967 Enable this if you want debugging information using the debug
1968 filesystem (debugfs)
1973 tristate "Freescale DIU framebuffer support"
1974 depends on FB && FSL_SOC
1975 select FB_MODE_HELPERS
1976 select FB_CFB_FILLRECT
1977 select FB_CFB_COPYAREA
1978 select FB_CFB_IMAGEBLIT
1979 select PPC_LIB_RHEAP
1981 Framebuffer driver for the Freescale SoC DIU
1984 tristate "W100 frame buffer support"
1985 depends on FB && ARCH_PXA
1986 select FB_CFB_FILLRECT
1987 select FB_CFB_COPYAREA
1988 select FB_CFB_IMAGEBLIT
1990 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1991 It can also drive the w3220 chip found on iPAQ hx4700.
1993 This driver is also available as a module ( = code which can be
1994 inserted and removed from the running kernel whenever you want). The
1995 module will be called w100fb. If you want to compile it as a module,
1996 say M here and read <file:Documentation/kbuild/modules.txt>.
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"