5 menu "Graphics support"
13 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
15 config SH_LCD_MIPI_DSI
18 source "drivers/char/agp/Kconfig"
20 source "drivers/gpu/vga/Kconfig"
22 source "drivers/gpu/drm/Kconfig"
24 source "drivers/gpu/stub/Kconfig"
30 config VIDEO_OUTPUT_CONTROL
31 tristate "Lowlevel video output switch controls"
33 This framework adds support for low-level control of the video
37 tristate "Support for frame buffer devices"
39 The frame buffer device provides an abstraction for the graphics
40 hardware. It represents the frame buffer of some video hardware and
41 allows application software to access the graphics hardware through
42 a well-defined interface, so the software doesn't need to know
43 anything about the low-level (hardware register) stuff.
45 Frame buffer devices work identically across the different
46 architectures supported by Linux and make the implementation of
47 application programs easier and more portable; at this point, an X
48 server exists which uses the frame buffer device exclusively.
49 On several non-X86 architectures, the frame buffer device is the
50 only way to use the graphics hardware.
52 The device is accessed through special device nodes, usually located
53 in the /dev directory, i.e. /dev/fb*.
55 You need an utility program called fbset to make full use of frame
56 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
57 and the Framebuffer-HOWTO at
58 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
61 Say Y here and to the driver for your graphics board below if you
62 are compiling a kernel for a non-x86 architecture.
64 If you are compiling for the x86 architecture, you can say Y if you
65 want to play with it, but it is not essential. Please note that
66 running graphical applications that directly touch the hardware
67 (e.g. an accelerated X server) and that are not frame buffer
68 device-aware may cause unexpected results. If unsure, say N.
71 bool "Enable firmware EDID"
75 This enables access to the EDID transferred from the firmware.
76 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
77 transfers do not work for your driver and if you are using
78 nvidiafb, i810fb or savagefb.
80 In general, choosing Y for this option is safe. If you
81 experience extremely long delays while booting before you get
82 something on your display, try setting this to N. Matrox cards in
83 combination with certain motherboards and monitors are known to
84 suffer from this problem.
93 config FB_BOOT_VESA_SUPPORT
98 If true, at least one selected framebuffer driver can take advantage
99 of VESA video modes set at an early boot stage via the vga= parameter.
101 config FB_CFB_FILLRECT
106 Include the cfb_fillrect function for generic software rectangle
107 filling. This is used by drivers that don't provide their own
108 (accelerated) version.
110 config FB_CFB_COPYAREA
115 Include the cfb_copyarea function for generic software area copying.
116 This is used by drivers that don't provide their own (accelerated)
119 config FB_CFB_IMAGEBLIT
124 Include the cfb_imageblit function for generic software image
125 blitting. This is used by drivers that don't provide their own
126 (accelerated) version.
128 config FB_CFB_REV_PIXELS_IN_BYTE
133 Allow generic frame-buffer functions to work on displays with 1, 2
134 and 4 bits per pixel depths which has opposite order of pixels in
135 byte order to bytes in long order.
137 config FB_SYS_FILLRECT
142 Include the sys_fillrect function for generic software rectangle
143 filling. This is used by drivers that don't provide their own
144 (accelerated) version and the framebuffer is in system RAM.
146 config FB_SYS_COPYAREA
151 Include the sys_copyarea function for generic software area copying.
152 This is used by drivers that don't provide their own (accelerated)
153 version and the framebuffer is in system RAM.
155 config FB_SYS_IMAGEBLIT
160 Include the sys_imageblit function for generic software image
161 blitting. This is used by drivers that don't provide their own
162 (accelerated) version and the framebuffer is in system RAM.
164 menuconfig FB_FOREIGN_ENDIAN
165 bool "Framebuffer foreign endianness support"
168 This menu will let you enable support for the framebuffers with
169 non-native endianness (e.g. Little-Endian framebuffer on a
170 Big-Endian machine). Most probably you don't have such hardware,
171 so it's safe to say "n" here.
174 prompt "Choice endianness support"
175 depends on FB_FOREIGN_ENDIAN
177 config FB_BOTH_ENDIAN
178 bool "Support for Big- and Little-Endian framebuffers"
181 bool "Support for Big-Endian framebuffers only"
183 config FB_LITTLE_ENDIAN
184 bool "Support for Little-Endian framebuffers only"
193 config FB_WMT_GE_ROPS
198 Include functions for accelerated rectangle filling and area
199 copying using WonderMedia Graphics Engine operations.
201 config FB_DEFERRED_IO
208 depends on FB_DEFERRED_IO
215 Common utility functions useful to fbdev drivers of VGA-based
226 select BACKLIGHT_LCD_SUPPORT
227 select BACKLIGHT_CLASS_DEVICE
230 config FB_MODE_HELPERS
231 bool "Enable Video Mode Handling Helpers"
235 This enables functions for handling video modes using the
236 Generalized Timing Formula and the EDID parser. A few drivers rely
237 on this feature such as the radeonfb, rivafb, and the i810fb. If
238 your driver does not take advantage of this feature, choosing Y will
239 just increase the kernel size by about 5K.
241 config FB_TILEBLITTING
242 bool "Enable Tile Blitting Support"
246 This enables tile blitting. Tile blitting is a drawing technique
247 where the screen is divided into rectangular sections (tiles), whereas
248 the standard blitting divides the screen into pixels. Because the
249 default drawing element is a tile, drawing functions will be passed
250 parameters in terms of number of tiles instead of number of pixels.
251 For example, to draw a single character, instead of using bitmaps,
252 an index to an array of bitmaps will be used. To clear or move a
253 rectangular section of a screen, the rectangle will be described in
254 terms of number of tiles in the x- and y-axis.
256 This is particularly important to one driver, matroxfb. If
259 comment "Frame buffer hardware drivers"
263 tristate "Aeroflex Gaisler framebuffer support"
264 depends on FB && SPARC
265 select FB_CFB_FILLRECT
266 select FB_CFB_COPYAREA
267 select FB_CFB_IMAGEBLIT
269 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
272 tristate "Cirrus Logic support"
273 depends on FB && (ZORRO || PCI)
274 select FB_CFB_FILLRECT
275 select FB_CFB_COPYAREA
276 select FB_CFB_IMAGEBLIT
278 This enables support for Cirrus Logic GD542x/543x based boards on
279 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
281 If you have a PCI-based system, this enables support for these
282 chips: GD-543x, GD-544x, GD-5480.
284 Please read the file <file:Documentation/fb/cirrusfb.txt>.
286 Say N unless you have such a graphics board or plan to get one
287 before you next recompile the kernel.
290 tristate "Permedia2 support"
291 depends on FB && ((AMIGA && BROKEN) || PCI)
292 select FB_CFB_FILLRECT
293 select FB_CFB_COPYAREA
294 select FB_CFB_IMAGEBLIT
296 This is the frame buffer device driver for cards based on
297 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
298 The driver was tested on the following cards:
299 Diamond FireGL 1000 PRO AGP
300 ELSA Gloria Synergy PCI
301 Appian Jeronimo PRO (both heads) PCI
302 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
303 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
304 ASK Graphic Blaster Exxtreme AGP
306 To compile this driver as a module, choose M here: the
307 module will be called pm2fb.
309 config FB_PM2_FIFO_DISCONNECT
310 bool "enable FIFO disconnect feature"
311 depends on FB_PM2 && PCI
313 Support the Permedia2 FIFO disconnect feature.
316 tristate "ARM PrimeCell PL110 support"
317 depends on FB && ARM && ARM_AMBA
318 select FB_CFB_FILLRECT
319 select FB_CFB_COPYAREA
320 select FB_CFB_IMAGEBLIT
322 This framebuffer device driver is for the ARM PrimeCell PL110
323 Colour LCD controller. ARM PrimeCells provide the building
324 blocks for System on a Chip devices.
326 If you want to compile this as a module (=code which can be
327 inserted into and removed from the running kernel), say M
328 here and read <file:Documentation/kbuild/modules.txt>. The module
329 will be called amba-clcd.
332 bool "Acorn VIDC support"
333 depends on (FB = y) && ARM && ARCH_ACORN
334 select FB_CFB_FILLRECT
335 select FB_CFB_COPYAREA
336 select FB_CFB_IMAGEBLIT
338 This is the frame buffer device driver for the Acorn VIDC graphics
339 hardware found in Acorn RISC PCs and other ARM-based machines. If
343 bool "CLPS711X LCD support"
344 depends on (FB = y) && ARM && ARCH_CLPS711X
345 select FB_CFB_FILLRECT
346 select FB_CFB_COPYAREA
347 select FB_CFB_IMAGEBLIT
349 Say Y to enable the Framebuffer driver for the CLPS7111 and
353 bool "SA-1100 LCD support"
354 depends on (FB = y) && ARM && ARCH_SA1100
355 select FB_CFB_FILLRECT
356 select FB_CFB_COPYAREA
357 select FB_CFB_IMAGEBLIT
359 This is a framebuffer device for the SA-1100 LCD Controller.
360 See <http://www.linux-fbdev.org/> for information on framebuffer
363 If you plan to use the LCD display with your SA-1100 system, say
367 tristate "Freescale i.MX LCD support"
368 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
369 select FB_CFB_FILLRECT
370 select FB_CFB_COPYAREA
371 select FB_CFB_IMAGEBLIT
374 tristate "CyberPro 2000/2010/5000 support"
375 depends on FB && PCI && (BROKEN || !SPARC64)
376 select FB_CFB_FILLRECT
377 select FB_CFB_COPYAREA
378 select FB_CFB_IMAGEBLIT
380 This enables support for the Integraphics CyberPro 20x0 and 5000
381 VGA chips used in the Rebel.com Netwinder and other machines.
382 Say Y if you have a NetWinder or a graphics card containing this
383 device, otherwise say N.
385 config FB_CYBER2000_DDC
386 bool "DDC for CyberPro support"
387 depends on FB_CYBER2000
391 Say Y here if you want DDC support for your CyberPro graphics
392 card. This is only I2C bus support, driver does not use EDID.
394 config FB_CYBER2000_I2C
395 bool "CyberPro 2000/2010/5000 I2C support"
396 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
399 Enable support for the I2C video decoder interface on the
400 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
401 on the Netwinder machines for the SAA7111 video capture.
405 depends on (FB = y) && APOLLO
407 select FB_CFB_FILLRECT
408 select FB_CFB_IMAGEBLIT
412 depends on (FB = y) && Q40
414 select FB_CFB_FILLRECT
415 select FB_CFB_COPYAREA
416 select FB_CFB_IMAGEBLIT
419 tristate "Amiga native chipset support"
420 depends on FB && AMIGA
422 This is the frame buffer device driver for the builtin graphics
423 chipset found in Amigas.
425 To compile this driver as a module, choose M here: the
426 module will be called amifb.
429 bool "Amiga OCS chipset support"
432 This enables support for the original Agnus and Denise video chips,
433 found in the Amiga 1000 and most A500's and A2000's. If you intend
434 to run Linux on any of these systems, say Y; otherwise say N.
437 bool "Amiga ECS chipset support"
440 This enables support for the Enhanced Chip Set, found in later
441 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
442 you intend to run Linux on any of these systems, say Y; otherwise
446 bool "Amiga AGA chipset support"
449 This enables support for the Advanced Graphics Architecture (also
450 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
451 and CD32. If you intend to run Linux on any of these systems, say Y;
455 bool "Amiga FrameMaster II/Rainbow II support"
456 depends on (FB = y) && ZORRO
457 select FB_CFB_FILLRECT
458 select FB_CFB_COPYAREA
459 select FB_CFB_IMAGEBLIT
461 This is the frame buffer device driver for the Amiga FrameMaster
462 card from BSC (exhibited 1992 but not shipped as a CBM product).
465 tristate "Arc Monochrome LCD board support"
467 select FB_SYS_FILLRECT
468 select FB_SYS_COPYAREA
469 select FB_SYS_IMAGEBLIT
472 This enables support for the Arc Monochrome LCD board. The board
473 is based on the KS-108 lcd controller and is typically a matrix
474 of 2*n chips. This driver was tested with a 128x64 panel. This
475 driver supports it for use with x86 SBCs through a 16 bit GPIO
476 interface (8 bit data, 8 bit control). If you anticipate using
477 this driver, say Y or M; otherwise say N. You must specify the
478 GPIO IO address to be used for setting control and data.
481 bool "Atari native chipset support"
482 depends on (FB = y) && ATARI
483 select FB_CFB_FILLRECT
484 select FB_CFB_COPYAREA
485 select FB_CFB_IMAGEBLIT
487 This is the frame buffer device driver for the builtin graphics
488 chipset found in Ataris.
491 bool "Open Firmware frame buffer device support"
492 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
493 select FB_CFB_FILLRECT
494 select FB_CFB_COPYAREA
495 select FB_CFB_IMAGEBLIT
498 Say Y if you want support with Open Firmware for your graphics
502 bool "Apple \"control\" display support"
503 depends on (FB = y) && PPC_PMAC && PPC32
504 select FB_CFB_FILLRECT
505 select FB_CFB_COPYAREA
506 select FB_CFB_IMAGEBLIT
509 This driver supports a frame buffer for the graphics adapter in the
510 Power Macintosh 7300 and others.
513 bool "Apple \"platinum\" display support"
514 depends on (FB = y) && PPC_PMAC && PPC32
515 select FB_CFB_FILLRECT
516 select FB_CFB_COPYAREA
517 select FB_CFB_IMAGEBLIT
520 This driver supports a frame buffer for the "platinum" graphics
521 adapter in some Power Macintoshes.
524 bool "Apple \"valkyrie\" display support"
525 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
526 select FB_CFB_FILLRECT
527 select FB_CFB_COPYAREA
528 select FB_CFB_IMAGEBLIT
531 This driver supports a frame buffer for the "valkyrie" graphics
532 adapter in some Power Macintoshes.
535 bool "Chips 65550 display support"
536 depends on (FB = y) && PPC32 && PCI
537 select FB_CFB_FILLRECT
538 select FB_CFB_COPYAREA
539 select FB_CFB_IMAGEBLIT
541 This is the frame buffer device driver for the Chips & Technologies
542 65550 graphics chip in PowerBooks.
545 bool "Asiliant (Chips) 69000 display support"
546 depends on (FB = y) && PCI
547 select FB_CFB_FILLRECT
548 select FB_CFB_COPYAREA
549 select FB_CFB_IMAGEBLIT
551 This is the frame buffer device driver for the Asiliant 69030 chipset
554 bool "IMS Twin Turbo display support"
555 depends on (FB = y) && PCI
556 select FB_CFB_IMAGEBLIT
557 select FB_MACMODES if PPC
559 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
560 many Macintosh and compatible computers.
563 tristate "VGA 16-color graphics support"
564 depends on FB && (X86 || PPC)
565 select FB_CFB_FILLRECT
566 select FB_CFB_COPYAREA
567 select FB_CFB_IMAGEBLIT
569 select FONT_8x16 if FRAMEBUFFER_CONSOLE
571 This is the frame buffer device driver for VGA 16 color graphic
572 cards. Say Y if you have such a card.
574 To compile this driver as a module, choose M here: the
575 module will be called vga16fb.
577 config FB_BF54X_LQ043
578 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
579 depends on FB && (BF54x) && !BF542
580 select FB_CFB_FILLRECT
581 select FB_CFB_COPYAREA
582 select FB_CFB_IMAGEBLIT
584 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
586 config FB_BFIN_T350MCQB
587 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
588 depends on FB && BLACKFIN
590 select FB_CFB_FILLRECT
591 select FB_CFB_COPYAREA
592 select FB_CFB_IMAGEBLIT
594 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
595 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
596 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
598 config FB_BFIN_LQ035Q1
599 tristate "SHARP LQ035Q1DH02 TFT LCD"
600 depends on FB && BLACKFIN && SPI
601 select FB_CFB_FILLRECT
602 select FB_CFB_COPYAREA
603 select FB_CFB_IMAGEBLIT
606 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
607 the Blackfin Landscape LCD EZ-Extender Card.
608 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
609 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
611 To compile this driver as a module, choose M here: the
612 module will be called bfin-lq035q1-fb.
614 config FB_BF537_LQ035
615 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
616 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
617 select FB_CFB_FILLRECT
618 select FB_CFB_COPYAREA
619 select FB_CFB_IMAGEBLIT
622 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
625 To compile this driver as a module, choose M here: the
626 module will be called bf537-lq035.
629 tristate "Blackfin ADV7393 Video encoder"
630 depends on FB && BLACKFIN
632 select FB_CFB_FILLRECT
633 select FB_CFB_COPYAREA
634 select FB_CFB_IMAGEBLIT
636 This is the framebuffer device for a ADV7393 video encoder
637 attached to a Blackfin on the PPI port.
638 If your Blackfin board has a ADV7393 select Y.
640 To compile this driver as a module, choose M here: the
641 module will be called bfin_adv7393fb.
644 prompt "Video mode support"
645 depends on FB_BFIN_7393
655 bool 'NTSC 640x480 (Experimental)'
658 bool 'PAL 640x480 (Experimental)'
661 bool 'NTSC 720x480 YCbCR input'
664 bool 'PAL 720x576 YCbCR input'
669 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
670 depends on (FB_BFIN_7393)
671 default ADV7393_1XMEM
681 tristate "HP STI frame buffer device support"
682 depends on FB && PARISC
683 select FB_CFB_FILLRECT
684 select FB_CFB_COPYAREA
685 select FB_CFB_IMAGEBLIT
688 STI refers to the HP "Standard Text Interface" which is a set of
689 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
690 Enabling this option will implement the linux framebuffer device
691 using calls to the STI BIOS routines for initialisation.
693 If you enable this option, you will get a planar framebuffer device
694 /dev/fb which will work on the most common HP graphic cards of the
695 NGLE family, including the artist chips (in the 7xx and Bxxx series),
696 HCRX, HCRX24, CRX, CRX24 and VisEG series.
698 It is safe to enable this option, so you should probably say "Y".
701 bool "Generic Macintosh display support"
702 depends on (FB = y) && MAC
703 select FB_CFB_FILLRECT
704 select FB_CFB_COPYAREA
705 select FB_CFB_IMAGEBLIT
710 depends on (FB = y) && DIO
711 select FB_CFB_IMAGEBLIT
715 tristate "TGA/SFB+ framebuffer support"
716 depends on FB && (ALPHA || TC)
717 select FB_CFB_FILLRECT
718 select FB_CFB_COPYAREA
719 select FB_CFB_IMAGEBLIT
722 This is the frame buffer device driver for generic TGA and SFB+
723 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
724 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
725 TURBOchannel cards, also known as PMAGD-A, -B and -C.
727 Due to hardware limitations ZLX-E2 and E3 cards are not supported
728 for DECstation 5000/200 systems. Additionally due to firmware
729 limitations these cards may cause troubles with booting DECstation
730 5000/240 and /260 systems, but are fully supported under Linux if
731 you manage to get it going. ;-)
733 Say Y if you have one of those.
736 tristate "Userspace VESA VGA graphics support"
737 depends on FB && CONNECTOR
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
741 select FB_MODE_HELPERS
743 This is the frame buffer driver for generic VBE 2.0 compliant
744 graphic cards. It can also take advantage of VBE 3.0 features,
745 such as refresh rate adjustment.
747 This driver generally provides more features than vesafb but
748 requires a userspace helper application called 'v86d'. See
749 <file:Documentation/fb/uvesafb.txt> for more information.
754 bool "VESA VGA graphics support"
755 depends on (FB = y) && X86
756 select FB_CFB_FILLRECT
757 select FB_CFB_COPYAREA
758 select FB_CFB_IMAGEBLIT
759 select FB_BOOT_VESA_SUPPORT
761 This is the frame buffer device driver for generic VESA 2.0
762 compliant graphic cards. The older VESA 1.2 cards are not supported.
763 You will get a boot time penguin logo at no additional cost. Please
764 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
767 bool "EFI-based Framebuffer Support"
768 depends on (FB = y) && X86 && EFI
769 select FB_CFB_FILLRECT
770 select FB_CFB_COPYAREA
771 select FB_CFB_IMAGEBLIT
773 This is the EFI frame buffer device driver. If the firmware on
774 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
775 using the EFI framebuffer as your console.
778 tristate "N411 Apollo/Hecuba devkit support"
779 depends on FB && X86 && MMU
780 select FB_SYS_FILLRECT
781 select FB_SYS_COPYAREA
782 select FB_SYS_IMAGEBLIT
784 select FB_DEFERRED_IO
787 This enables support for the Apollo display controller in its
788 Hecuba form using the n411 devkit.
791 tristate "Hercules mono graphics support"
794 Say Y here if you have a Hercules mono graphics card.
796 To compile this driver as a module, choose M here: the
797 module will be called hgafb.
799 As this card technology is at least 25 years old,
800 most people will answer N here.
803 tristate "SGI Visual Workstation framebuffer support"
804 depends on FB && X86_VISWS
805 select FB_CFB_FILLRECT
806 select FB_CFB_COPYAREA
807 select FB_CFB_IMAGEBLIT
809 SGI Visual Workstation support for framebuffer graphics.
812 bool "SGI Graphics Backend frame buffer support"
813 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
814 select FB_CFB_FILLRECT
815 select FB_CFB_COPYAREA
816 select FB_CFB_IMAGEBLIT
818 This is the frame buffer device driver for SGI Graphics Backend.
819 This chip is used in SGI O2 and Visual Workstation 320/540.
822 int "Video memory size in MB"
826 This is the amount of memory reserved for the framebuffer,
827 which can be any value between 1MB and 8MB.
830 bool "SBUS and UPA framebuffers"
831 depends on (FB = y) && SPARC
833 Say Y if you want support for SBUS or UPA based frame buffer device.
837 depends on (FB = y) && (SPARC && FB_SBUS)
838 select FB_CFB_FILLRECT
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 This is the frame buffer device driver for the BWtwo frame buffer.
845 bool "CGthree support"
846 depends on (FB = y) && (SPARC && FB_SBUS)
847 select FB_CFB_FILLRECT
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 This is the frame buffer device driver for the CGthree frame buffer.
854 bool "CGsix (GX,TurboGX) support"
855 depends on (FB = y) && (SPARC && FB_SBUS)
856 select FB_CFB_COPYAREA
857 select FB_CFB_IMAGEBLIT
859 This is the frame buffer device driver for the CGsix (GX, TurboGX)
863 bool "Creator/Creator3D/Elite3D support"
864 depends on FB_SBUS && SPARC64
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This is the frame buffer device driver for the Creator, Creator3D,
869 and Elite3D graphics boards.
872 bool "TCX (SS4/SS5 only) support"
874 select FB_CFB_FILLRECT
875 select FB_CFB_COPYAREA
876 select FB_CFB_IMAGEBLIT
878 This is the frame buffer device driver for the TCX 24/8bit frame
882 bool "CGfourteen (SX) support"
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 This is the frame buffer device driver for the CGfourteen frame
889 buffer on Desktop SPARCsystems with the SX graphics option.
892 bool "P9100 (Sparcbook 3 only) support"
894 select FB_CFB_FILLRECT
895 select FB_CFB_COPYAREA
896 select FB_CFB_IMAGEBLIT
898 This is the frame buffer device driver for the P9100 card
899 supported on Sparcbook 3 machines.
902 bool "Leo (ZX) support"
904 select FB_CFB_FILLRECT
905 select FB_CFB_COPYAREA
906 select FB_CFB_IMAGEBLIT
908 This is the frame buffer device driver for the SBUS-based Sun ZX
909 (leo) frame buffer cards.
912 bool "IGA 168x display support"
913 depends on (FB = y) && SPARC32
914 select FB_CFB_FILLRECT
915 select FB_CFB_COPYAREA
916 select FB_CFB_IMAGEBLIT
918 This is the framebuffer device for the INTERGRAPHICS 1680 and
919 successor frame buffer cards.
922 bool "Sun XVR-500 3DLABS Wildcat support"
923 depends on (FB = y) && PCI && SPARC64
924 select FB_CFB_FILLRECT
925 select FB_CFB_COPYAREA
926 select FB_CFB_IMAGEBLIT
928 This is the framebuffer device for the Sun XVR-500 and similar
929 graphics cards based upon the 3DLABS Wildcat chipset. The driver
930 only works on sparc64 systems where the system firmware has
931 mostly initialized the card already. It is treated as a
932 completely dumb framebuffer device.
935 bool "Sun XVR-2500 3DLABS Wildcat support"
936 depends on (FB = y) && PCI && SPARC64
937 select FB_CFB_FILLRECT
938 select FB_CFB_COPYAREA
939 select FB_CFB_IMAGEBLIT
941 This is the framebuffer device for the Sun XVR-2500 and similar
942 graphics cards based upon the 3DLABS Wildcat chipset. The driver
943 only works on sparc64 systems where the system firmware has
944 mostly initialized the card already. It is treated as a
945 completely dumb framebuffer device.
948 bool "Sun XVR-1000 support"
949 depends on (FB = y) && SPARC64
950 select FB_CFB_FILLRECT
951 select FB_CFB_COPYAREA
952 select FB_CFB_IMAGEBLIT
954 This is the framebuffer device for the Sun XVR-1000 and similar
955 graphics cards. The driver only works on sparc64 systems where
956 the system firmware has mostly initialized the card already. It
957 is treated as a completely dumb framebuffer device.
960 tristate "NEC PowerVR 2 display support"
961 depends on FB && SH_DREAMCAST
962 select FB_CFB_FILLRECT
963 select FB_CFB_COPYAREA
964 select FB_CFB_IMAGEBLIT
966 Say Y here if you have a PowerVR 2 card in your box. If you plan to
967 run linux on your Dreamcast, you will have to say Y here.
968 This driver may or may not work on other PowerVR 2 cards, but is
969 totally untested. Use at your own risk. If unsure, say N.
971 To compile this driver as a module, choose M here: the
972 module will be called pvr2fb.
974 You can pass several parameters to the driver at boot time or at
975 module load time. The parameters look like "video=pvr2:XXX", where
976 the meaning of XXX can be found at the end of the main source file
977 (<file:drivers/video/pvr2fb.c>). Please see the file
978 <file:Documentation/fb/pvr2fb.txt>.
981 bool "Epson 1355 framebuffer support"
982 depends on (FB = y) && ARCH_CEIVA
983 select FB_CFB_FILLRECT
984 select FB_CFB_COPYAREA
985 select FB_CFB_IMAGEBLIT
987 Build in support for the SED1355 Epson Research Embedded RAMDAC
988 LCD/CRT Controller (since redesignated as the S1D13505) as a
989 framebuffer. Product specs at
990 <http://vdc.epson.com/>.
993 tristate "Epson S1D13XXX framebuffer support"
995 select FB_CFB_FILLRECT
996 select FB_CFB_COPYAREA
997 select FB_CFB_IMAGEBLIT
999 Support for S1D13XXX framebuffer device family (currently only
1000 working with S1D13806). Product specs at
1001 <http://vdc.epson.com/>
1004 tristate "AT91/AT32 LCD Controller support"
1005 depends on FB && HAVE_FB_ATMEL
1006 select FB_CFB_FILLRECT
1007 select FB_CFB_COPYAREA
1008 select FB_CFB_IMAGEBLIT
1010 This enables support for the AT91/AT32 LCD Controller.
1013 bool "Frame Buffer in internal SRAM"
1014 depends on FB_ATMEL && ARCH_AT91SAM9261
1016 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1017 to let frame buffer in external SDRAM.
1020 bool "Use a STN display with AT91/AT32 LCD Controller"
1021 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1024 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1025 Controller. Say N if you want to connect a TFT.
1030 tristate "nVidia Framebuffer Support"
1031 depends on FB && PCI
1032 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1033 select FB_MODE_HELPERS
1034 select FB_CFB_FILLRECT
1035 select FB_CFB_COPYAREA
1036 select FB_CFB_IMAGEBLIT
1040 This driver supports graphics boards with the nVidia chips, TNT
1041 and newer. For very old chipsets, such as the RIVA128, then use
1043 Say Y if you have such a graphics board.
1045 To compile this driver as a module, choose M here: the
1046 module will be called nvidiafb.
1048 config FB_NVIDIA_I2C
1049 bool "Enable DDC Support"
1050 depends on FB_NVIDIA
1053 This enables I2C support for nVidia Chipsets. This is used
1054 only for getting EDID information from the attached display
1055 allowing for robust video mode handling and switching.
1057 Because fbdev-2.6 requires that drivers must be able to
1058 independently validate video mode parameters, you should say Y
1061 config FB_NVIDIA_DEBUG
1062 bool "Lots of debug output"
1063 depends on FB_NVIDIA
1066 Say Y here if you want the nVidia driver to output all sorts
1067 of debugging information to provide to the maintainer when
1068 something goes wrong.
1070 config FB_NVIDIA_BACKLIGHT
1071 bool "Support for backlight control"
1072 depends on FB_NVIDIA
1075 Say Y here if you want to control the backlight of your display.
1078 tristate "nVidia Riva support"
1079 depends on FB && PCI
1080 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1081 select FB_MODE_HELPERS
1082 select FB_CFB_FILLRECT
1083 select FB_CFB_COPYAREA
1084 select FB_CFB_IMAGEBLIT
1088 This driver supports graphics boards with the nVidia Riva/Geforce
1090 Say Y if you have such a graphics board.
1092 To compile this driver as a module, choose M here: the
1093 module will be called rivafb.
1096 bool "Enable DDC Support"
1100 This enables I2C support for nVidia Chipsets. This is used
1101 only for getting EDID information from the attached display
1102 allowing for robust video mode handling and switching.
1104 Because fbdev-2.6 requires that drivers must be able to
1105 independently validate video mode parameters, you should say Y
1108 config FB_RIVA_DEBUG
1109 bool "Lots of debug output"
1113 Say Y here if you want the Riva driver to output all sorts
1114 of debugging information to provide to the maintainer when
1115 something goes wrong.
1117 config FB_RIVA_BACKLIGHT
1118 bool "Support for backlight control"
1122 Say Y here if you want to control the backlight of your display.
1125 tristate "Intel 810/815 support (EXPERIMENTAL)"
1126 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1127 select FB_MODE_HELPERS
1128 select FB_CFB_FILLRECT
1129 select FB_CFB_COPYAREA
1130 select FB_CFB_IMAGEBLIT
1133 This driver supports the on-board graphics built in to the Intel 810
1134 and 815 chipsets. Say Y if you have and plan to use such a board.
1136 To compile this driver as a module, choose M here: the
1137 module will be called i810fb.
1139 For more information, please read
1140 <file:Documentation/fb/intel810.txt>
1143 bool "use VESA Generalized Timing Formula"
1146 If you say Y, then the VESA standard, Generalized Timing Formula
1147 or GTF, will be used to calculate the required video timing values
1148 per video mode. Since the GTF allows nondiscrete timings
1149 (nondiscrete being a range of values as opposed to discrete being a
1150 set of values), you'll be able to use any combination of horizontal
1151 and vertical resolutions, and vertical refresh rates without having
1152 to specify your own timing parameters. This is especially useful
1153 to maximize the performance of an aging display, or if you just
1154 have a display with nonstandard dimensions. A VESA compliant
1155 monitor is recommended, but can still work with non-compliant ones.
1156 If you need or want this, then select this option. The timings may
1157 not be compliant with Intel's recommended values. Use at your own
1160 If you say N, the driver will revert to discrete video timings
1161 using a set recommended by Intel in their documentation.
1166 bool "Enable DDC Support"
1167 depends on FB_I810 && FB_I810_GTF
1172 tristate "Intel LE80578 (Vermilion) support"
1173 depends on FB && PCI && X86
1174 select FB_MODE_HELPERS
1175 select FB_CFB_FILLRECT
1176 select FB_CFB_COPYAREA
1177 select FB_CFB_IMAGEBLIT
1179 This driver supports the LE80578 (Vermilion Range) chipset
1181 config FB_CARILLO_RANCH
1182 tristate "Intel Carillo Ranch support"
1183 depends on FB_LE80578 && FB && PCI && X86
1185 This driver supports the LE80578 (Carillo Ranch) board
1188 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1189 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1190 select FB_MODE_HELPERS
1191 select FB_CFB_FILLRECT
1192 select FB_CFB_COPYAREA
1193 select FB_CFB_IMAGEBLIT
1194 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1195 depends on !DRM_I915
1197 This driver supports the on-board graphics built in to the Intel
1198 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1199 Say Y if you have and plan to use such a board.
1201 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1203 To compile this driver as a module, choose M here: the
1204 module will be called intelfb.
1206 For more information, please read <file:Documentation/fb/intelfb.txt>
1208 config FB_INTEL_DEBUG
1209 bool "Intel driver Debug Messages"
1212 Say Y here if you want the Intel driver to output all sorts
1213 of debugging information to provide to the maintainer when
1214 something goes wrong.
1217 bool "DDC/I2C for Intel framebuffer support"
1222 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1225 tristate "Matrox acceleration"
1226 depends on FB && PCI
1227 select FB_CFB_FILLRECT
1228 select FB_CFB_COPYAREA
1229 select FB_CFB_IMAGEBLIT
1230 select FB_TILEBLITTING
1231 select FB_MACMODES if PPC_PMAC
1233 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1234 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1235 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1236 Matrox G400, G450 or G550 card in your box.
1238 To compile this driver as a module, choose M here: the
1239 module will be called matroxfb.
1241 You can pass several parameters to the driver at boot time or at
1242 module load time. The parameters look like "video=matroxfb:XXX", and
1243 are described in <file:Documentation/fb/matroxfb.txt>.
1245 config FB_MATROX_MILLENIUM
1246 bool "Millennium I/II support"
1247 depends on FB_MATROX
1249 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1250 video card. If you select "Advanced lowlevel driver options" below,
1251 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1252 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1253 also use font widths different from 8.
1255 config FB_MATROX_MYSTIQUE
1256 bool "Mystique support"
1257 depends on FB_MATROX
1259 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1260 video card. If you select "Advanced lowlevel driver options" below,
1261 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1262 packed pixel and 32 bpp packed pixel. You can also use font widths
1266 bool "G100/G200/G400/G450/G550 support"
1267 depends on FB_MATROX
1269 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1270 video card. If you select "Advanced lowlevel driver options", you
1271 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1272 pixel and 32 bpp packed pixel. You can also use font widths
1275 If you need support for G400 secondary head, you must say Y to
1276 "Matrox I2C support" and "G400 second head support" right below.
1277 G450/G550 secondary head and digital output are supported without
1280 The driver starts in monitor mode. You must use the matroxset tool
1281 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1282 swap primary and secondary head outputs, or to change output mode.
1283 Secondary head driver always start in 640x480 resolution and you
1284 must use fbset to change it.
1286 Do not forget that second head supports only 16 and 32 bpp
1287 packed pixels, so it is a good idea to compile them into the kernel
1288 too. You can use only some font widths, as the driver uses generic
1289 painting procedures (the secondary head does not use acceleration
1292 G450/G550 hardware can display TV picture only from secondary CRTC,
1293 and it performs no scaling, so picture must have 525 or 625 lines.
1295 config FB_MATROX_I2C
1296 tristate "Matrox I2C support"
1297 depends on FB_MATROX
1300 This drivers creates I2C buses which are needed for accessing the
1301 DDC (I2C) bus present on all Matroxes, an I2C bus which
1302 interconnects Matrox optional devices, like MGA-TVO on G200 and
1303 G400, and the secondary head DDC bus, present on G400 only.
1305 You can say Y or M here if you want to experiment with monitor
1306 detection code. You must say Y or M here if you want to use either
1307 second head of G400 or MGA-TVO on G200 or G400.
1309 If you compile it as module, it will create a module named
1312 config FB_MATROX_MAVEN
1313 tristate "G400 second head support"
1314 depends on FB_MATROX_G && FB_MATROX_I2C
1316 WARNING !!! This support does not work with G450 !!!
1318 Say Y or M here if you want to use a secondary head (meaning two
1319 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1320 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1321 secondary head output is blanked while you are in X. With XFree
1322 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1323 the fbdev driver on first head and the fbdev driver on second head.
1325 If you compile it as module, two modules are created,
1326 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1327 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1328 also load i2c-matroxfb to get it to run.
1330 The driver starts in monitor mode and you must use the matroxset
1332 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1333 PAL or NTSC or to swap primary and secondary head outputs.
1334 Secondary head driver also always start in 640x480 resolution, you
1335 must use fbset to change it.
1337 Also do not forget that second head supports only 16 and 32 bpp
1338 packed pixels, so it is a good idea to compile them into the kernel
1339 too. You can use only some font widths, as the driver uses generic
1340 painting procedures (the secondary head does not use acceleration
1344 tristate "ATI Radeon display support"
1345 depends on FB && PCI
1346 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1347 select FB_MODE_HELPERS
1348 select FB_CFB_FILLRECT
1349 select FB_CFB_COPYAREA
1350 select FB_CFB_IMAGEBLIT
1351 select FB_MACMODES if PPC_OF
1353 Choose this option if you want to use an ATI Radeon graphics card as
1354 a framebuffer device. There are both PCI and AGP versions. You
1355 don't need to choose this to run the Radeon in plain VGA mode.
1357 There is a product page at
1358 http://products.amd.com/en-us/GraphicCardResult.aspx
1360 config FB_RADEON_I2C
1361 bool "DDC/I2C for ATI Radeon support"
1362 depends on FB_RADEON
1366 Say Y here if you want DDC/I2C support for your Radeon board.
1368 config FB_RADEON_BACKLIGHT
1369 bool "Support for backlight control"
1370 depends on FB_RADEON
1373 Say Y here if you want to control the backlight of your display.
1375 config FB_RADEON_DEBUG
1376 bool "Lots of debug output from Radeon driver"
1377 depends on FB_RADEON
1380 Say Y here if you want the Radeon driver to output all sorts
1381 of debugging information to provide to the maintainer when
1382 something goes wrong.
1385 tristate "ATI Rage128 display support"
1386 depends on FB && PCI
1387 select FB_CFB_FILLRECT
1388 select FB_CFB_COPYAREA
1389 select FB_CFB_IMAGEBLIT
1390 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1391 select FB_MACMODES if PPC_PMAC
1393 This driver supports graphics boards with the ATI Rage128 chips.
1394 Say Y if you have such a graphics board and read
1395 <file:Documentation/fb/aty128fb.txt>.
1397 To compile this driver as a module, choose M here: the
1398 module will be called aty128fb.
1400 config FB_ATY128_BACKLIGHT
1401 bool "Support for backlight control"
1402 depends on FB_ATY128
1405 Say Y here if you want to control the backlight of your display.
1408 tristate "ATI Mach64 display support" if PCI || ATARI
1409 depends on FB && !SPARC32
1410 select FB_CFB_FILLRECT
1411 select FB_CFB_COPYAREA
1412 select FB_CFB_IMAGEBLIT
1413 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1414 select FB_MACMODES if PPC
1416 This driver supports graphics boards with the ATI Mach64 chips.
1417 Say Y if you have such a graphics board.
1419 To compile this driver as a module, choose M here: the
1420 module will be called atyfb.
1423 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1424 depends on PCI && FB_ATY
1425 default y if SPARC64 && PCI
1427 Say Y here to support use of ATI's 64-bit Rage boards (or other
1428 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1429 framebuffer device. The ATI product support page for these boards
1430 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1432 config FB_ATY_GENERIC_LCD
1433 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1434 depends on FB_ATY_CT
1436 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1437 Rage XC, or Rage XL chipset.
1440 bool "Mach64 GX support" if PCI
1444 Say Y here to support use of the ATI Mach64 Graphics Expression
1445 board (or other boards based on the Mach64 GX chipset) as a
1446 framebuffer device. The ATI product support page for these boards
1448 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1450 config FB_ATY_BACKLIGHT
1451 bool "Support for backlight control"
1455 Say Y here if you want to control the backlight of your display.
1458 tristate "S3 Trio/Virge support"
1459 depends on FB && PCI
1460 select FB_CFB_FILLRECT
1461 select FB_CFB_COPYAREA
1462 select FB_CFB_IMAGEBLIT
1463 select FB_TILEBLITTING
1466 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1468 Driver for graphics boards with S3 Trio / S3 Virge chip.
1471 bool "DDC for S3 support"
1476 Say Y here if you want DDC support for your S3 graphics card.
1479 tristate "S3 Savage support"
1480 depends on FB && PCI && EXPERIMENTAL
1481 select FB_MODE_HELPERS
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1487 This driver supports notebooks and computers with S3 Savage PCI/AGP
1490 Say Y if you have such a graphics card.
1492 To compile this driver as a module, choose M here; the module
1493 will be called savagefb.
1495 config FB_SAVAGE_I2C
1496 bool "Enable DDC2 Support"
1497 depends on FB_SAVAGE
1500 This enables I2C support for S3 Savage Chipsets. This is used
1501 only for getting EDID information from the attached display
1502 allowing for robust video mode handling and switching.
1504 Because fbdev-2.6 requires that drivers must be able to
1505 independently validate video mode parameters, you should say Y
1508 config FB_SAVAGE_ACCEL
1509 bool "Enable Console Acceleration"
1510 depends on FB_SAVAGE
1513 This option will compile in console acceleration support. If
1514 the resulting framebuffer console has bothersome glitches, then
1518 tristate "SiS/XGI display support"
1519 depends on FB && PCI
1520 select FB_CFB_FILLRECT
1521 select FB_CFB_COPYAREA
1522 select FB_CFB_IMAGEBLIT
1523 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1525 This is the frame buffer device driver for the SiS 300, 315, 330
1526 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1527 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1529 To compile this driver as a module, choose M here; the module
1530 will be called sisfb.
1533 bool "SiS 300 series support"
1536 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1539 bool "SiS 315/330/340 series and XGI support"
1542 Say Y here to support use of the SiS 315, 330 and 340 series
1543 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1544 as XGI V3XT, V5, V8 and Z7.
1547 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1548 depends on FB && PCI && X86
1549 select FB_CFB_FILLRECT
1550 select FB_CFB_COPYAREA
1551 select FB_CFB_IMAGEBLIT
1556 This is the frame buffer device driver for Graphics chips of VIA
1557 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1558 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1560 Say Y if you have a VIA UniChrome graphics board.
1562 To compile this driver as a module, choose M here: the
1563 module will be called viafb.
1567 config FB_VIA_DIRECT_PROCFS
1568 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1572 Allow direct hardware access to some output registers via procfs.
1573 This is dangerous but may provide the only chance to get the
1574 correct output device configuration.
1575 Its use is strongly discouraged.
1577 config FB_VIA_X_COMPATIBILITY
1578 bool "X server compatibility"
1582 This option reduces the functionality (power saving, ...) of the
1583 framebuffer to avoid negative impact on the OpenChrome X server.
1584 If you use any X server other than fbdev you should enable this
1585 otherwise it should be safe to disable it and allow using all
1591 tristate "NeoMagic display support"
1592 depends on FB && PCI
1593 select FB_MODE_HELPERS
1594 select FB_CFB_FILLRECT
1595 select FB_CFB_COPYAREA
1596 select FB_CFB_IMAGEBLIT
1599 This driver supports notebooks with NeoMagic PCI chips.
1600 Say Y if you have such a graphics card.
1602 To compile this driver as a module, choose M here: the
1603 module will be called neofb.
1606 tristate "IMG Kyro support"
1607 depends on FB && PCI
1608 select FB_CFB_FILLRECT
1609 select FB_CFB_COPYAREA
1610 select FB_CFB_IMAGEBLIT
1612 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1615 To compile this driver as a module, choose M here: the
1616 module will be called kyrofb.
1619 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1620 depends on FB && PCI
1621 select FB_CFB_IMAGEBLIT
1622 select FB_CFB_FILLRECT
1623 select FB_CFB_COPYAREA
1624 select FB_MODE_HELPERS
1626 This driver supports graphics boards with the 3Dfx Banshee,
1627 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1628 such a graphics board.
1630 To compile this driver as a module, choose M here: the
1631 module will be called tdfxfb.
1633 config FB_3DFX_ACCEL
1634 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1635 depends on FB_3DFX && EXPERIMENTAL
1637 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1638 device driver with acceleration functions.
1641 bool "Enable DDC/I2C support"
1642 depends on FB_3DFX && EXPERIMENTAL
1646 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1649 tristate "3Dfx Voodoo Graphics (sst1) support"
1650 depends on FB && PCI
1651 select FB_CFB_FILLRECT
1652 select FB_CFB_COPYAREA
1653 select FB_CFB_IMAGEBLIT
1655 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1656 Voodoo2 (cvg) based graphics card.
1658 To compile this driver as a module, choose M here: the
1659 module will be called sstfb.
1661 WARNING: Do not use any application that uses the 3D engine
1662 (namely glide) while using this driver.
1663 Please read the <file:Documentation/fb/sstfb.txt> for supported
1664 options and other important info support.
1667 tristate "VIA VT8623 support"
1668 depends on FB && PCI
1669 select FB_CFB_FILLRECT
1670 select FB_CFB_COPYAREA
1671 select FB_CFB_IMAGEBLIT
1672 select FB_TILEBLITTING
1675 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1677 Driver for CastleRock integrated graphics core in the
1678 VIA VT8623 [Apollo CLE266] chipset.
1681 tristate "Trident/CyberXXX/CyberBlade support"
1682 depends on FB && PCI
1683 select FB_CFB_FILLRECT
1684 select FB_CFB_COPYAREA
1685 select FB_CFB_IMAGEBLIT
1687 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1688 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1690 There are also integrated versions of these chips called CyberXXXX,
1691 CyberImage or CyberBlade. These chips are mostly found in laptops
1692 but also on some motherboards including early VIA EPIA motherboards.
1693 For more information, read <file:Documentation/fb/tridentfb.txt>
1695 Say Y if you have such a graphics board.
1697 To compile this driver as a module, choose M here: the
1698 module will be called tridentfb.
1701 tristate "ARK 2000PV support"
1702 depends on FB && PCI
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1706 select FB_TILEBLITTING
1709 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1711 Driver for PCI graphics boards with ARK 2000PV chip
1712 and ICS 5342 RAMDAC.
1715 tristate "Permedia3 support (EXPERIMENTAL)"
1716 depends on FB && PCI && EXPERIMENTAL
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1721 This is the frame buffer device driver for the 3DLabs Permedia3
1722 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1723 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1724 and maybe other boards.
1727 tristate "Fujitsu carmine frame buffer support"
1728 depends on FB && PCI
1729 select FB_CFB_FILLRECT
1730 select FB_CFB_COPYAREA
1731 select FB_CFB_IMAGEBLIT
1733 This is the frame buffer device driver for the Fujitsu Carmine chip.
1734 The driver provides two independent frame buffer devices.
1737 depends on FB_CARMINE
1738 prompt "DRAM timing"
1739 default FB_CARMINE_DRAM_EVAL
1741 config FB_CARMINE_DRAM_EVAL
1742 bool "Eval board timings"
1744 Use timings which work on the eval card.
1746 config CARMINE_DRAM_CUSTOM
1747 bool "Custom board timings"
1749 Use custom board timings.
1753 bool "Au1100 LCD Driver"
1754 depends on (FB = y) && MIPS_ALCHEMY
1755 select FB_CFB_FILLRECT
1756 select FB_CFB_COPYAREA
1757 select FB_CFB_IMAGEBLIT
1759 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1760 various panels and CRTs by passing in kernel cmd line option
1761 au1100fb:panel=<name>.
1764 bool "Au1200 LCD Driver"
1765 depends on (FB = y) && MIPS_ALCHEMY
1766 select FB_SYS_FILLRECT
1767 select FB_SYS_COPYAREA
1768 select FB_SYS_IMAGEBLIT
1771 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1772 various panels and CRTs by passing in kernel cmd line option
1773 au1200fb:panel=<name>.
1776 bool "VT8500 LCD Driver"
1777 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1778 select FB_WMT_GE_ROPS
1779 select FB_SYS_IMAGEBLIT
1781 This is the framebuffer driver for VIA VT8500 integrated LCD
1785 bool "WM8505 frame buffer support"
1786 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1787 select FB_WMT_GE_ROPS
1788 select FB_SYS_IMAGEBLIT
1790 This is the framebuffer driver for WonderMedia WM8505
1791 integrated LCD controller.
1793 source "drivers/video/geode/Kconfig"
1796 tristate "HD64461 Frame Buffer support"
1797 depends on FB && HD64461
1798 select FB_CFB_FILLRECT
1799 select FB_CFB_COPYAREA
1800 select FB_CFB_IMAGEBLIT
1802 This is the frame buffer device driver for the Hitachi HD64461 LCD
1806 bool "PMAG-AA TURBOchannel framebuffer support"
1807 depends on (FB = y) && TC
1808 select FB_CFB_FILLRECT
1809 select FB_CFB_COPYAREA
1810 select FB_CFB_IMAGEBLIT
1812 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1813 used mainly in the MIPS-based DECstation series.
1816 tristate "PMAG-BA TURBOchannel framebuffer support"
1818 select FB_CFB_FILLRECT
1819 select FB_CFB_COPYAREA
1820 select FB_CFB_IMAGEBLIT
1822 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1823 used mainly in the MIPS-based DECstation series.
1826 tristate "PMAGB-B TURBOchannel framebuffer support"
1828 select FB_CFB_FILLRECT
1829 select FB_CFB_COPYAREA
1830 select FB_CFB_IMAGEBLIT
1832 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1833 in the MIPS-based DECstation series. The card is currently only
1834 supported in 1280x1024x8 mode.
1837 bool "Maxine (Personal DECstation) onboard framebuffer support"
1838 depends on (FB = y) && MACH_DECSTATION
1839 select FB_CFB_FILLRECT
1840 select FB_CFB_COPYAREA
1841 select FB_CFB_IMAGEBLIT
1843 Support for the onboard framebuffer (1024x768x8) in the Personal
1844 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1848 bool "G364 frame buffer support"
1849 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1850 select FB_CFB_FILLRECT
1851 select FB_CFB_COPYAREA
1852 select FB_CFB_IMAGEBLIT
1854 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1855 Olivetti M700-10 systems.
1858 bool "Motorola 68328 native frame buffer support"
1859 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1864 Say Y here if you want to support the built-in frame buffer of
1865 the Motorola 68328 CPU family.
1868 tristate "PXA168/910 LCD framebuffer support"
1869 depends on FB && (CPU_PXA168 || CPU_PXA910)
1870 select FB_CFB_FILLRECT
1871 select FB_CFB_COPYAREA
1872 select FB_CFB_IMAGEBLIT
1874 Frame buffer driver for the built-in LCD controller in the Marvell
1878 tristate "PXA LCD framebuffer support"
1879 depends on FB && ARCH_PXA
1880 select FB_CFB_FILLRECT
1881 select FB_CFB_COPYAREA
1882 select FB_CFB_IMAGEBLIT
1884 Frame buffer driver for the built-in LCD controller in the Intel
1887 This driver is also available as a module ( = code which can be
1888 inserted and removed from the running kernel whenever you want). The
1889 module will be called pxafb. If you want to compile it as a module,
1890 say M here and read <file:Documentation/kbuild/modules.txt>.
1894 config FB_PXA_OVERLAY
1895 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1897 depends on FB_PXA && (PXA27x || PXA3xx)
1899 config FB_PXA_SMARTPANEL
1900 bool "PXA Smartpanel LCD support"
1904 config FB_PXA_PARAMETERS
1905 bool "PXA LCD command line parameters"
1909 Enable the use of kernel command line or module parameters
1910 to configure the physical properties of the LCD panel when
1911 using the PXA LCD driver.
1913 This option allows you to override the panel parameters
1914 supplied by the platform in order to support multiple
1915 different models of flatpanel. If you will only be using a
1916 single model of flatpanel then you can safely leave this
1919 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1922 tristate "PXA3xx 2D graphics accelerator driver"
1925 Kernelspace driver for the 2D graphics controller unit (GCU)
1926 found on PXA3xx processors. There is a counterpart driver in the
1927 DirectFB suite, see http://www.directfb.org/
1929 If you compile this as a module, it will be called pxa3xx_gcu.
1932 tristate "2700G LCD framebuffer support"
1933 depends on FB && ARCH_PXA
1934 select FB_CFB_FILLRECT
1935 select FB_CFB_COPYAREA
1936 select FB_CFB_IMAGEBLIT
1938 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1942 bool "Enable debugging info via debugfs"
1943 depends on FB_MBX && DEBUG_FS
1946 Enable this if you want debugging information using the debug
1947 filesystem (debugfs)
1952 tristate "Freescale DIU framebuffer support"
1953 depends on FB && FSL_SOC
1954 select FB_MODE_HELPERS
1955 select FB_CFB_FILLRECT
1956 select FB_CFB_COPYAREA
1957 select FB_CFB_IMAGEBLIT
1958 select PPC_LIB_RHEAP
1960 Framebuffer driver for the Freescale SoC DIU
1963 tristate "W100 frame buffer support"
1964 depends on FB && ARCH_PXA
1965 select FB_CFB_FILLRECT
1966 select FB_CFB_COPYAREA
1967 select FB_CFB_IMAGEBLIT
1969 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1970 It can also drive the w3220 chip found on iPAQ hx4700.
1972 This driver is also available as a module ( = code which can be
1973 inserted and removed from the running kernel whenever you want). The
1974 module will be called w100fb. If you want to compile it as a module,
1975 say M here and read <file:Documentation/kbuild/modules.txt>.
1979 config FB_SH_MOBILE_LCDC
1980 tristate "SuperH Mobile LCDC framebuffer support"
1981 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1982 select FB_SYS_FILLRECT
1983 select FB_SYS_COPYAREA
1984 select FB_SYS_IMAGEBLIT
1986 select FB_DEFERRED_IO
1988 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1990 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1992 config FB_SH_MOBILE_HDMI
1993 tristate "SuperH Mobile HDMI controller support"
1994 depends on FB_SH_MOBILE_LCDC
1995 select FB_MODE_HELPERS
2000 Driver for the on-chip SH-Mobile HDMI controller.
2002 config FB_SH_MOBILE_MERAM
2003 tristate "SuperH Mobile MERAM read ahead support for LCDC"
2004 depends on FB_SH_MOBILE_LCDC
2007 Enable MERAM support for the SH-Mobile LCD controller.
2009 This will allow for caching of the framebuffer to provide more
2010 reliable access under heavy main memory bus traffic situations.
2011 Up to 4 memory channels can be configured, allowing 4 RGB or
2012 2 YCbCr framebuffers to be configured.
2015 tristate "Toshiba Mobile IO FrameBuffer support"
2016 depends on FB && MFD_CORE
2017 select FB_CFB_FILLRECT
2018 select FB_CFB_COPYAREA
2019 select FB_CFB_IMAGEBLIT
2021 Frame buffer driver for the Toshiba Mobile IO integrated as found
2022 on the Sharp SL-6000 series
2024 This driver is also available as a module ( = code which can be
2025 inserted and removed from the running kernel whenever you want). The
2026 module will be called tmiofb. If you want to compile it as a module,
2027 say M here and read <file:Documentation/kbuild/modules.txt>.
2031 config FB_TMIO_ACCELL
2032 bool "tmiofb acceleration"
2037 tristate "Samsung S3C framebuffer support"
2038 depends on FB && (S3C_DEV_FB || S5P_DEV_FIMD0)
2039 select FB_CFB_FILLRECT
2040 select FB_CFB_COPYAREA
2041 select FB_CFB_IMAGEBLIT
2043 Frame buffer driver for the built-in FB controller in the Samsung
2044 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2045 and the S3C64XX series such as the S3C6400 and S3C6410.
2047 These chips all have the same basic framebuffer design with the
2048 actual capabilities depending on the chip. For instance the S3C6400
2049 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2050 currently only have two.
2052 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2054 config FB_S3C_DEBUG_REGWRITE
2055 bool "Debug register writes"
2058 Show all register writes via printk(KERN_DEBUG)
2061 tristate "S3C2410 LCD framebuffer support"
2062 depends on FB && ARCH_S3C2410
2063 select FB_CFB_FILLRECT
2064 select FB_CFB_COPYAREA
2065 select FB_CFB_IMAGEBLIT
2067 Frame buffer driver for the built-in LCD controller in the Samsung
2070 This driver is also available as a module ( = code which can be
2071 inserted and removed from the running kernel whenever you want). The
2072 module will be called s3c2410fb. If you want to compile it as a module,
2073 say M here and read <file:Documentation/kbuild/modules.txt>.
2076 config FB_S3C2410_DEBUG
2077 bool "S3C2410 lcd debug messages"
2078 depends on FB_S3C2410
2080 Turn on debugging messages. Note that you can set/unset at run time
2084 bool "NUC900 LCD framebuffer support"
2085 depends on FB && ARCH_W90X900
2086 select FB_CFB_FILLRECT
2087 select FB_CFB_COPYAREA
2088 select FB_CFB_IMAGEBLIT
2090 Frame buffer driver for the built-in LCD controller in the Nuvoton
2093 config GPM1040A0_320X240
2094 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2095 depends on FB_NUC900
2097 config FB_NUC900_DEBUG
2098 bool "NUC900 lcd debug messages"
2099 depends on FB_NUC900
2101 Turn on debugging messages. Note that you can set/unset at run time
2105 tristate "Silicon Motion SM501 framebuffer support"
2106 depends on FB && MFD_SM501
2107 select FB_CFB_FILLRECT
2108 select FB_CFB_COPYAREA
2109 select FB_CFB_IMAGEBLIT
2111 Frame buffer driver for the CRT and LCD controllers in the Silicon
2114 This driver is also available as a module ( = code which can be
2115 inserted and removed from the running kernel whenever you want). The
2116 module will be called sm501fb. If you want to compile it as a module,
2117 say M here and read <file:Documentation/kbuild/modules.txt>.
2122 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2123 depends on FB && USB
2124 select FB_MODE_HELPERS
2125 select FB_SYS_FILLRECT
2126 select FB_SYS_COPYAREA
2127 select FB_SYS_IMAGEBLIT
2129 select FB_DEFERRED_IO
2131 This is a kernel framebuffer driver for SMSC UFX USB devices.
2132 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2133 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2135 To compile as a module, choose M here: the module name is smscufx.
2138 tristate "Displaylink USB Framebuffer support"
2139 depends on FB && USB
2140 select FB_MODE_HELPERS
2141 select FB_SYS_FILLRECT
2142 select FB_SYS_COPYAREA
2143 select FB_SYS_IMAGEBLIT
2145 select FB_DEFERRED_IO
2147 This is a kernel framebuffer driver for DisplayLink USB devices.
2148 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2149 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2150 To compile as a module, choose M here: the module name is udlfb.
2152 config FB_PNX4008_DUM
2153 tristate "Display Update Module support on Philips PNX4008 board"
2154 depends on FB && ARCH_PNX4008
2156 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2158 config FB_PNX4008_DUM_RGB
2159 tristate "RGB Framebuffer support on Philips PNX4008 board"
2160 depends on FB_PNX4008_DUM
2161 select FB_CFB_FILLRECT
2162 select FB_CFB_COPYAREA
2163 select FB_CFB_IMAGEBLIT
2165 Say Y here to enable support for PNX4008 RGB Framebuffer
2167 config FB_IBM_GXT4500
2168 tristate "Framebuffer support for IBM GXT4500P adaptor"
2169 depends on FB && PPC
2170 select FB_CFB_FILLRECT
2171 select FB_CFB_COPYAREA
2172 select FB_CFB_IMAGEBLIT
2174 Say Y here to enable support for the IBM GXT4500P display
2175 adaptor, found on some IBM System P (pSeries) machines.
2178 tristate "PS3 GPU framebuffer driver"
2179 depends on FB && PS3_PS3AV
2180 select FB_SYS_FILLRECT
2181 select FB_SYS_COPYAREA
2182 select FB_SYS_IMAGEBLIT
2184 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2186 Include support for the virtual frame buffer in the PS3 platform.
2188 config FB_PS3_DEFAULT_SIZE_M
2189 int "PS3 default frame buffer size (in MiB)"
2193 This is the default size (in MiB) of the virtual frame buffer in
2195 The default value can be overridden on the kernel command line
2196 using the "ps3fb" option (e.g. "ps3fb=9M");
2199 tristate "Xilinx frame buffer support"
2200 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2201 select FB_CFB_FILLRECT
2202 select FB_CFB_COPYAREA
2203 select FB_CFB_IMAGEBLIT
2205 Include support for the Xilinx ML300/ML403 reference design
2206 framebuffer. ML300 carries a 640*480 LCD display on the board,
2207 ML403 uses a standard DB15 VGA connector.
2210 tristate "Cobalt server LCD frame buffer support"
2211 depends on FB && MIPS_COBALT
2214 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2215 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2216 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2217 select FB_CFB_FILLRECT
2218 select FB_CFB_COPYAREA
2219 select FB_CFB_IMAGEBLIT
2221 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2222 (D)STN/TFT LCD Controller.
2223 Supports display resolutions up to 1024x1024 pixel, grayscale and
2224 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2225 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2226 panels <= 320 pixel horizontal resolution.
2229 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2230 depends on FB && ARCH_DAVINCI_DA8XX
2231 select FB_CFB_FILLRECT
2232 select FB_CFB_COPYAREA
2233 select FB_CFB_IMAGEBLIT
2235 This is the frame buffer device driver for the TI LCD controller
2236 found on DA8xx/OMAP-L1xx SoCs.
2240 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2242 select FB_SYS_FILLRECT
2243 select FB_SYS_COPYAREA
2244 select FB_SYS_IMAGEBLIT
2247 This is a `virtual' frame buffer device. It operates on a chunk of
2248 unswappable kernel memory instead of on the memory of a graphics
2249 board. This means you cannot see any output sent to this frame
2250 buffer device, while it does consume precious memory. The main use
2251 of this frame buffer device is testing and debugging the frame
2252 buffer subsystem. Do NOT enable it for normal systems! To protect
2253 the innocent, it has to be enabled explicitly at boot time using the
2254 kernel option `video=vfb:'.
2256 To compile this driver as a module, choose M here: the
2257 module will be called vfb. In order to load it, you must use
2258 the vfb_enable=1 option.
2262 config XEN_FBDEV_FRONTEND
2263 tristate "Xen virtual frame buffer support"
2264 depends on FB && XEN
2265 select FB_SYS_FILLRECT
2266 select FB_SYS_COPYAREA
2267 select FB_SYS_IMAGEBLIT
2269 select FB_DEFERRED_IO
2270 select XEN_XENBUS_FRONTEND
2273 This driver implements the front-end of the Xen virtual
2274 frame buffer driver. It communicates with a back-end
2278 tristate "E-Ink Metronome/8track controller support"
2280 select FB_SYS_FILLRECT
2281 select FB_SYS_COPYAREA
2282 select FB_SYS_IMAGEBLIT
2284 select FB_DEFERRED_IO
2286 This driver implements support for the E-Ink Metronome
2287 controller. The pre-release name for this device was 8track
2288 and could also have been called by some vendors as PVI-nnnn.
2291 tristate "Fujitsu MB862xx GDC support"
2293 depends on PCI || (OF && PPC)
2294 select FB_CFB_FILLRECT
2295 select FB_CFB_COPYAREA
2296 select FB_CFB_IMAGEBLIT
2298 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2301 prompt "GDC variant"
2302 depends on FB_MB862XX
2304 config FB_MB862XX_PCI_GDC
2305 bool "Carmine/Coral-P(A) GDC"
2308 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2309 PCI graphics controller devices.
2311 config FB_MB862XX_LIME
2313 depends on OF && PPC
2314 select FB_FOREIGN_ENDIAN
2315 select FB_LITTLE_ENDIAN
2317 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2321 config FB_MB862XX_I2C
2322 bool "Support I2C bus on MB862XX GDC"
2323 depends on FB_MB862XX && I2C
2326 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2327 driver to support accessing I2C devices on controller's I2C bus.
2328 These are usually some video decoder chips.
2331 tristate "EP93XX frame buffer support"
2332 depends on FB && ARCH_EP93XX
2333 select FB_CFB_FILLRECT
2334 select FB_CFB_COPYAREA
2335 select FB_CFB_IMAGEBLIT
2337 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2338 This driver is also available as a module. The module will be called
2341 config FB_PRE_INIT_FB
2342 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2343 depends on FB && FB_MB862XX_LIME
2345 Select this option if display contents should be inherited as set by
2349 tristate "MSM Framebuffer support"
2350 depends on FB && ARCH_MSM
2351 select FB_CFB_FILLRECT
2352 select FB_CFB_COPYAREA
2353 select FB_CFB_IMAGEBLIT
2356 tristate "MX3 Framebuffer support"
2357 depends on FB && MX3_IPU
2358 select FB_CFB_FILLRECT
2359 select FB_CFB_COPYAREA
2360 select FB_CFB_IMAGEBLIT
2363 This is a framebuffer device for the i.MX31 LCD Controller. So
2364 far only synchronous displays are supported. If you plan to use
2365 an LCD display with your i.MX31 system, say Y here.
2367 config FB_BROADSHEET
2368 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2370 select FB_SYS_FILLRECT
2371 select FB_SYS_COPYAREA
2372 select FB_SYS_IMAGEBLIT
2374 select FB_DEFERRED_IO
2376 This driver implements support for the E-Ink Broadsheet
2377 controller. The release name for this device was Epson S1D13521
2378 and could also have been called by other names when coupled with
2382 tristate "JZ4740 LCD framebuffer support"
2383 depends on FB && MACH_JZ4740
2384 select FB_SYS_FILLRECT
2385 select FB_SYS_COPYAREA
2386 select FB_SYS_IMAGEBLIT
2388 Framebuffer support for the JZ4740 SoC.
2391 tristate "MXS LCD framebuffer support"
2392 depends on FB && ARCH_MXS
2393 select FB_CFB_FILLRECT
2394 select FB_CFB_COPYAREA
2395 select FB_CFB_IMAGEBLIT
2397 Framebuffer support for the MXS SoC.
2399 config FB_PUV3_UNIGFX
2400 tristate "PKUnity v3 Unigfx framebuffer support"
2401 depends on FB && UNICORE32 && ARCH_PUV3
2402 select FB_SYS_FILLRECT
2403 select FB_SYS_COPYAREA
2404 select FB_SYS_IMAGEBLIT
2407 Choose this option if you want to use the Unigfx device as a
2408 framebuffer device. Without the support of PCI & AGP.
2410 source "drivers/video/omap/Kconfig"
2411 source "drivers/video/omap2/Kconfig"
2413 source "drivers/video/backlight/Kconfig"
2414 source "drivers/video/display/Kconfig"
2417 source "drivers/video/console/Kconfig"
2420 if FB || SGI_NEWPORT_CONSOLE
2421 source "drivers/video/logo/Kconfig"