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"
26 source "drivers/gpu/ion/Kconfig"
32 config VIDEO_OUTPUT_CONTROL
33 tristate "Lowlevel video output switch controls"
35 This framework adds support for low-level control of the video
39 tristate "Support for frame buffer devices"
41 The frame buffer device provides an abstraction for the graphics
42 hardware. It represents the frame buffer of some video hardware and
43 allows application software to access the graphics hardware through
44 a well-defined interface, so the software doesn't need to know
45 anything about the low-level (hardware register) stuff.
47 Frame buffer devices work identically across the different
48 architectures supported by Linux and make the implementation of
49 application programs easier and more portable; at this point, an X
50 server exists which uses the frame buffer device exclusively.
51 On several non-X86 architectures, the frame buffer device is the
52 only way to use the graphics hardware.
54 The device is accessed through special device nodes, usually located
55 in the /dev directory, i.e. /dev/fb*.
57 You need an utility program called fbset to make full use of frame
58 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
59 and the Framebuffer-HOWTO at
60 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
63 Say Y here and to the driver for your graphics board below if you
64 are compiling a kernel for a non-x86 architecture.
66 If you are compiling for the x86 architecture, you can say Y if you
67 want to play with it, but it is not essential. Please note that
68 running graphical applications that directly touch the hardware
69 (e.g. an accelerated X server) and that are not frame buffer
70 device-aware may cause unexpected results. If unsure, say N.
73 bool "Enable firmware EDID"
77 This enables access to the EDID transferred from the firmware.
78 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
79 transfers do not work for your driver and if you are using
80 nvidiafb, i810fb or savagefb.
82 In general, choosing Y for this option is safe. If you
83 experience extremely long delays while booting before you get
84 something on your display, try setting this to N. Matrox cards in
85 combination with certain motherboards and monitors are known to
86 suffer from this problem.
95 config FB_BOOT_VESA_SUPPORT
100 If true, at least one selected framebuffer driver can take advantage
101 of VESA video modes set at an early boot stage via the vga= parameter.
103 config FB_CFB_FILLRECT
108 Include the cfb_fillrect function for generic software rectangle
109 filling. This is used by drivers that don't provide their own
110 (accelerated) version.
112 config FB_CFB_COPYAREA
117 Include the cfb_copyarea function for generic software area copying.
118 This is used by drivers that don't provide their own (accelerated)
121 config FB_CFB_IMAGEBLIT
126 Include the cfb_imageblit function for generic software image
127 blitting. This is used by drivers that don't provide their own
128 (accelerated) version.
130 config FB_CFB_REV_PIXELS_IN_BYTE
135 Allow generic frame-buffer functions to work on displays with 1, 2
136 and 4 bits per pixel depths which has opposite order of pixels in
137 byte order to bytes in long order.
139 config FB_SYS_FILLRECT
144 Include the sys_fillrect function for generic software rectangle
145 filling. This is used by drivers that don't provide their own
146 (accelerated) version and the framebuffer is in system RAM.
148 config FB_SYS_COPYAREA
153 Include the sys_copyarea function for generic software area copying.
154 This is used by drivers that don't provide their own (accelerated)
155 version and the framebuffer is in system RAM.
157 config FB_SYS_IMAGEBLIT
162 Include the sys_imageblit function for generic software image
163 blitting. This is used by drivers that don't provide their own
164 (accelerated) version and the framebuffer is in system RAM.
166 menuconfig FB_FOREIGN_ENDIAN
167 bool "Framebuffer foreign endianness support"
170 This menu will let you enable support for the framebuffers with
171 non-native endianness (e.g. Little-Endian framebuffer on a
172 Big-Endian machine). Most probably you don't have such hardware,
173 so it's safe to say "n" here.
176 prompt "Choice endianness support"
177 depends on FB_FOREIGN_ENDIAN
179 config FB_BOTH_ENDIAN
180 bool "Support for Big- and Little-Endian framebuffers"
183 bool "Support for Big-Endian framebuffers only"
185 config FB_LITTLE_ENDIAN
186 bool "Support for Little-Endian framebuffers only"
195 config FB_WMT_GE_ROPS
200 Include functions for accelerated rectangle filling and area
201 copying using WonderMedia Graphics Engine operations.
203 config FB_DEFERRED_IO
210 depends on FB_DEFERRED_IO
217 Common utility functions useful to fbdev drivers of VGA-based
228 select BACKLIGHT_LCD_SUPPORT
229 select BACKLIGHT_CLASS_DEVICE
232 config FB_MODE_HELPERS
233 bool "Enable Video Mode Handling Helpers"
237 This enables functions for handling video modes using the
238 Generalized Timing Formula and the EDID parser. A few drivers rely
239 on this feature such as the radeonfb, rivafb, and the i810fb. If
240 your driver does not take advantage of this feature, choosing Y will
241 just increase the kernel size by about 5K.
243 config FB_TILEBLITTING
244 bool "Enable Tile Blitting Support"
248 This enables tile blitting. Tile blitting is a drawing technique
249 where the screen is divided into rectangular sections (tiles), whereas
250 the standard blitting divides the screen into pixels. Because the
251 default drawing element is a tile, drawing functions will be passed
252 parameters in terms of number of tiles instead of number of pixels.
253 For example, to draw a single character, instead of using bitmaps,
254 an index to an array of bitmaps will be used. To clear or move a
255 rectangular section of a screen, the rectangle will be described in
256 terms of number of tiles in the x- and y-axis.
258 This is particularly important to one driver, matroxfb. If
261 comment "Frame buffer hardware drivers"
265 tristate "Cirrus Logic support"
266 depends on FB && (ZORRO || PCI)
267 select FB_CFB_FILLRECT
268 select FB_CFB_COPYAREA
269 select FB_CFB_IMAGEBLIT
271 This enables support for Cirrus Logic GD542x/543x based boards on
272 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
274 If you have a PCI-based system, this enables support for these
275 chips: GD-543x, GD-544x, GD-5480.
277 Please read the file <file:Documentation/fb/cirrusfb.txt>.
279 Say N unless you have such a graphics board or plan to get one
280 before you next recompile the kernel.
283 tristate "Permedia2 support"
284 depends on FB && ((AMIGA && BROKEN) || PCI)
285 select FB_CFB_FILLRECT
286 select FB_CFB_COPYAREA
287 select FB_CFB_IMAGEBLIT
289 This is the frame buffer device driver for cards based on
290 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
291 The driver was tested on the following cards:
292 Diamond FireGL 1000 PRO AGP
293 ELSA Gloria Synergy PCI
294 Appian Jeronimo PRO (both heads) PCI
295 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
296 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
297 ASK Graphic Blaster Exxtreme AGP
299 To compile this driver as a module, choose M here: the
300 module will be called pm2fb.
302 config FB_PM2_FIFO_DISCONNECT
303 bool "enable FIFO disconnect feature"
304 depends on FB_PM2 && PCI
306 Support the Permedia2 FIFO disconnect feature.
309 tristate "ARM PrimeCell PL110 support"
310 depends on FB && ARM && ARM_AMBA
311 select FB_CFB_FILLRECT
312 select FB_CFB_COPYAREA
313 select FB_CFB_IMAGEBLIT
315 This framebuffer device driver is for the ARM PrimeCell PL110
316 Colour LCD controller. ARM PrimeCells provide the building
317 blocks for System on a Chip devices.
319 If you want to compile this as a module (=code which can be
320 inserted into and removed from the running kernel), say M
321 here and read <file:Documentation/kbuild/modules.txt>. The module
322 will be called amba-clcd.
325 bool "Acorn VIDC support"
326 depends on (FB = y) && ARM && ARCH_ACORN
327 select FB_CFB_FILLRECT
328 select FB_CFB_COPYAREA
329 select FB_CFB_IMAGEBLIT
331 This is the frame buffer device driver for the Acorn VIDC graphics
332 hardware found in Acorn RISC PCs and other ARM-based machines. If
336 bool "CLPS711X LCD support"
337 depends on (FB = y) && ARM && ARCH_CLPS711X
338 select FB_CFB_FILLRECT
339 select FB_CFB_COPYAREA
340 select FB_CFB_IMAGEBLIT
342 Say Y to enable the Framebuffer driver for the CLPS7111 and
346 bool "SA-1100 LCD support"
347 depends on (FB = y) && ARM && ARCH_SA1100
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This is a framebuffer device for the SA-1100 LCD Controller.
353 See <http://www.linux-fbdev.org/> for information on framebuffer
356 If you plan to use the LCD display with your SA-1100 system, say
360 tristate "Freescale i.MX LCD support"
361 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
362 select FB_CFB_FILLRECT
363 select FB_CFB_COPYAREA
364 select FB_CFB_IMAGEBLIT
367 tristate "CyberPro 2000/2010/5000 support"
368 depends on FB && PCI && (BROKEN || !SPARC64)
369 select FB_CFB_FILLRECT
370 select FB_CFB_COPYAREA
371 select FB_CFB_IMAGEBLIT
373 This enables support for the Integraphics CyberPro 20x0 and 5000
374 VGA chips used in the Rebel.com Netwinder and other machines.
375 Say Y if you have a NetWinder or a graphics card containing this
376 device, otherwise say N.
378 config FB_CYBER2000_DDC
379 bool "DDC for CyberPro support"
380 depends on FB_CYBER2000
384 Say Y here if you want DDC support for your CyberPro graphics
385 card. This is only I2C bus support, driver does not use EDID.
387 config FB_CYBER2000_I2C
388 bool "CyberPro 2000/2010/5000 I2C support"
389 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
392 Enable support for the I2C video decoder interface on the
393 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
394 on the Netwinder machines for the SAA7111 video capture.
398 depends on (FB = y) && APOLLO
400 select FB_CFB_FILLRECT
401 select FB_CFB_IMAGEBLIT
405 depends on (FB = y) && Q40
407 select FB_CFB_FILLRECT
408 select FB_CFB_COPYAREA
409 select FB_CFB_IMAGEBLIT
412 tristate "Amiga native chipset support"
413 depends on FB && AMIGA
415 This is the frame buffer device driver for the builtin graphics
416 chipset found in Amigas.
418 To compile this driver as a module, choose M here: the
419 module will be called amifb.
422 bool "Amiga OCS chipset support"
425 This enables support for the original Agnus and Denise video chips,
426 found in the Amiga 1000 and most A500's and A2000's. If you intend
427 to run Linux on any of these systems, say Y; otherwise say N.
430 bool "Amiga ECS chipset support"
433 This enables support for the Enhanced Chip Set, found in later
434 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
435 you intend to run Linux on any of these systems, say Y; otherwise
439 bool "Amiga AGA chipset support"
442 This enables support for the Advanced Graphics Architecture (also
443 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
444 and CD32. If you intend to run Linux on any of these systems, say Y;
448 bool "Amiga FrameMaster II/Rainbow II support"
449 depends on (FB = y) && ZORRO
450 select FB_CFB_FILLRECT
451 select FB_CFB_COPYAREA
452 select FB_CFB_IMAGEBLIT
454 This is the frame buffer device driver for the Amiga FrameMaster
455 card from BSC (exhibited 1992 but not shipped as a CBM product).
458 tristate "Arc Monochrome LCD board support"
460 select FB_SYS_FILLRECT
461 select FB_SYS_COPYAREA
462 select FB_SYS_IMAGEBLIT
465 This enables support for the Arc Monochrome LCD board. The board
466 is based on the KS-108 lcd controller and is typically a matrix
467 of 2*n chips. This driver was tested with a 128x64 panel. This
468 driver supports it for use with x86 SBCs through a 16 bit GPIO
469 interface (8 bit data, 8 bit control). If you anticipate using
470 this driver, say Y or M; otherwise say N. You must specify the
471 GPIO IO address to be used for setting control and data.
474 bool "Atari native chipset support"
475 depends on (FB = y) && ATARI
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
480 This is the frame buffer device driver for the builtin graphics
481 chipset found in Ataris.
484 bool "Open Firmware frame buffer device support"
485 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
486 select FB_CFB_FILLRECT
487 select FB_CFB_COPYAREA
488 select FB_CFB_IMAGEBLIT
491 Say Y if you want support with Open Firmware for your graphics
495 bool "Apple \"control\" display support"
496 depends on (FB = y) && PPC_PMAC && PPC32
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
502 This driver supports a frame buffer for the graphics adapter in the
503 Power Macintosh 7300 and others.
506 bool "Apple \"platinum\" display support"
507 depends on (FB = y) && PPC_PMAC && PPC32
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
513 This driver supports a frame buffer for the "platinum" graphics
514 adapter in some Power Macintoshes.
517 bool "Apple \"valkyrie\" display support"
518 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
524 This driver supports a frame buffer for the "valkyrie" graphics
525 adapter in some Power Macintoshes.
528 bool "Chips 65550 display support"
529 depends on (FB = y) && PPC32 && PCI
530 select FB_CFB_FILLRECT
531 select FB_CFB_COPYAREA
532 select FB_CFB_IMAGEBLIT
534 This is the frame buffer device driver for the Chips & Technologies
535 65550 graphics chip in PowerBooks.
538 bool "Asiliant (Chips) 69000 display support"
539 depends on (FB = y) && PCI
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
544 This is the frame buffer device driver for the Asiliant 69030 chipset
547 bool "IMS Twin Turbo display support"
548 depends on (FB = y) && PCI
549 select FB_CFB_IMAGEBLIT
550 select FB_MACMODES if PPC
552 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
553 many Macintosh and compatible computers.
556 tristate "VGA 16-color graphics support"
557 depends on FB && (X86 || PPC)
558 select FB_CFB_FILLRECT
559 select FB_CFB_COPYAREA
560 select FB_CFB_IMAGEBLIT
562 select FONT_8x16 if FRAMEBUFFER_CONSOLE
564 This is the frame buffer device driver for VGA 16 color graphic
565 cards. Say Y if you have such a card.
567 To compile this driver as a module, choose M here: the
568 module will be called vga16fb.
570 config FB_BF54X_LQ043
571 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
572 depends on FB && (BF54x) && !BF542
573 select FB_CFB_FILLRECT
574 select FB_CFB_COPYAREA
575 select FB_CFB_IMAGEBLIT
577 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
579 config FB_BFIN_T350MCQB
580 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
581 depends on FB && BLACKFIN
583 select FB_CFB_FILLRECT
584 select FB_CFB_COPYAREA
585 select FB_CFB_IMAGEBLIT
587 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
588 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
589 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
591 config FB_BFIN_LQ035Q1
592 tristate "SHARP LQ035Q1DH02 TFT LCD"
593 depends on FB && BLACKFIN && SPI
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
599 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
600 the Blackfin Landscape LCD EZ-Extender Card.
601 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
602 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
604 To compile this driver as a module, choose M here: the
605 module will be called bfin-lq035q1-fb.
607 config FB_BF537_LQ035
608 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
609 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
610 select FB_CFB_FILLRECT
611 select FB_CFB_COPYAREA
612 select FB_CFB_IMAGEBLIT
615 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
618 To compile this driver as a module, choose M here: the
619 module will be called bf537-lq035.
622 tristate "Blackfin ADV7393 Video encoder"
623 depends on FB && BLACKFIN
625 select FB_CFB_FILLRECT
626 select FB_CFB_COPYAREA
627 select FB_CFB_IMAGEBLIT
629 This is the framebuffer device for a ADV7393 video encoder
630 attached to a Blackfin on the PPI port.
631 If your Blackfin board has a ADV7393 select Y.
633 To compile this driver as a module, choose M here: the
634 module will be called bfin_adv7393fb.
637 prompt "Video mode support"
638 depends on FB_BFIN_7393
648 bool 'NTSC 640x480 (Experimental)'
651 bool 'PAL 640x480 (Experimental)'
654 bool 'NTSC 720x480 YCbCR input'
657 bool 'PAL 720x576 YCbCR input'
662 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
663 depends on (FB_BFIN_7393)
664 default ADV7393_1XMEM
674 tristate "HP STI frame buffer device support"
675 depends on FB && PARISC
676 select FB_CFB_FILLRECT
677 select FB_CFB_COPYAREA
678 select FB_CFB_IMAGEBLIT
683 STI refers to the HP "Standard Text Interface" which is a set of
684 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
685 Enabling this option will implement the linux framebuffer device
686 using calls to the STI BIOS routines for initialisation.
688 If you enable this option, you will get a planar framebuffer device
689 /dev/fb which will work on the most common HP graphic cards of the
690 NGLE family, including the artist chips (in the 7xx and Bxxx series),
691 HCRX, HCRX24, CRX, CRX24 and VisEG series.
693 It is safe to enable this option, so you should probably say "Y".
696 bool "Generic Macintosh display support"
697 depends on (FB = y) && MAC
698 select FB_CFB_FILLRECT
699 select FB_CFB_COPYAREA
700 select FB_CFB_IMAGEBLIT
705 depends on (FB = y) && DIO
706 select FB_CFB_IMAGEBLIT
710 tristate "TGA/SFB+ framebuffer support"
711 depends on FB && (ALPHA || TC)
712 select FB_CFB_FILLRECT
713 select FB_CFB_COPYAREA
714 select FB_CFB_IMAGEBLIT
717 This is the frame buffer device driver for generic TGA and SFB+
718 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
719 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
720 TURBOchannel cards, also known as PMAGD-A, -B and -C.
722 Due to hardware limitations ZLX-E2 and E3 cards are not supported
723 for DECstation 5000/200 systems. Additionally due to firmware
724 limitations these cards may cause troubles with booting DECstation
725 5000/240 and /260 systems, but are fully supported under Linux if
726 you manage to get it going. ;-)
728 Say Y if you have one of those.
731 tristate "Userspace VESA VGA graphics support"
732 depends on FB && CONNECTOR
733 select FB_CFB_FILLRECT
734 select FB_CFB_COPYAREA
735 select FB_CFB_IMAGEBLIT
736 select FB_MODE_HELPERS
738 This is the frame buffer driver for generic VBE 2.0 compliant
739 graphic cards. It can also take advantage of VBE 3.0 features,
740 such as refresh rate adjustment.
742 This driver generally provides more features than vesafb but
743 requires a userspace helper application called 'v86d'. See
744 <file:Documentation/fb/uvesafb.txt> for more information.
749 bool "VESA VGA graphics support"
750 depends on (FB = y) && X86
751 select FB_CFB_FILLRECT
752 select FB_CFB_COPYAREA
753 select FB_CFB_IMAGEBLIT
754 select FB_BOOT_VESA_SUPPORT
756 This is the frame buffer device driver for generic VESA 2.0
757 compliant graphic cards. The older VESA 1.2 cards are not supported.
758 You will get a boot time penguin logo at no additional cost. Please
759 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
762 bool "EFI-based Framebuffer Support"
763 depends on (FB = y) && X86 && EFI
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
768 This is the EFI frame buffer device driver. If the firmware on
769 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
770 using the EFI framebuffer as your console.
773 tristate "N411 Apollo/Hecuba devkit support"
774 depends on FB && X86 && MMU
775 select FB_SYS_FILLRECT
776 select FB_SYS_COPYAREA
777 select FB_SYS_IMAGEBLIT
779 select FB_DEFERRED_IO
782 This enables support for the Apollo display controller in its
783 Hecuba form using the n411 devkit.
786 tristate "Hercules mono graphics support"
789 Say Y here if you have a Hercules mono graphics card.
791 To compile this driver as a module, choose M here: the
792 module will be called hgafb.
794 As this card technology is at least 25 years old,
795 most people will answer N here.
798 tristate "SGI Visual Workstation framebuffer support"
799 depends on FB && X86_VISWS
800 select FB_CFB_FILLRECT
801 select FB_CFB_COPYAREA
802 select FB_CFB_IMAGEBLIT
804 SGI Visual Workstation support for framebuffer graphics.
807 bool "SGI Graphics Backend frame buffer support"
808 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
809 select FB_CFB_FILLRECT
810 select FB_CFB_COPYAREA
811 select FB_CFB_IMAGEBLIT
813 This is the frame buffer device driver for SGI Graphics Backend.
814 This chip is used in SGI O2 and Visual Workstation 320/540.
817 int "Video memory size in MB"
821 This is the amount of memory reserved for the framebuffer,
822 which can be any value between 1MB and 8MB.
825 bool "SBUS and UPA framebuffers"
826 depends on (FB = y) && SPARC
828 Say Y if you want support for SBUS or UPA based frame buffer device.
832 depends on (FB = y) && (SPARC && FB_SBUS)
833 select FB_CFB_FILLRECT
834 select FB_CFB_COPYAREA
835 select FB_CFB_IMAGEBLIT
837 This is the frame buffer device driver for the BWtwo frame buffer.
840 bool "CGthree support"
841 depends on (FB = y) && (SPARC && FB_SBUS)
842 select FB_CFB_FILLRECT
843 select FB_CFB_COPYAREA
844 select FB_CFB_IMAGEBLIT
846 This is the frame buffer device driver for the CGthree frame buffer.
849 bool "CGsix (GX,TurboGX) support"
850 depends on (FB = y) && (SPARC && FB_SBUS)
851 select FB_CFB_COPYAREA
852 select FB_CFB_IMAGEBLIT
854 This is the frame buffer device driver for the CGsix (GX, TurboGX)
858 bool "Creator/Creator3D/Elite3D support"
859 depends on FB_SBUS && SPARC64
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 This is the frame buffer device driver for the Creator, Creator3D,
864 and Elite3D graphics boards.
867 bool "TCX (SS4/SS5 only) support"
869 select FB_CFB_FILLRECT
870 select FB_CFB_COPYAREA
871 select FB_CFB_IMAGEBLIT
873 This is the frame buffer device driver for the TCX 24/8bit frame
877 bool "CGfourteen (SX) support"
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 CGfourteen frame
884 buffer on Desktop SPARCsystems with the SX graphics option.
887 bool "P9100 (Sparcbook 3 only) support"
889 select FB_CFB_FILLRECT
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This is the frame buffer device driver for the P9100 card
894 supported on Sparcbook 3 machines.
897 bool "Leo (ZX) support"
899 select FB_CFB_FILLRECT
900 select FB_CFB_COPYAREA
901 select FB_CFB_IMAGEBLIT
903 This is the frame buffer device driver for the SBUS-based Sun ZX
904 (leo) frame buffer cards.
907 bool "IGA 168x display support"
908 depends on (FB = y) && SPARC32
909 select FB_CFB_FILLRECT
910 select FB_CFB_COPYAREA
911 select FB_CFB_IMAGEBLIT
913 This is the framebuffer device for the INTERGRAPHICS 1680 and
914 successor frame buffer cards.
917 bool "Sun XVR-500 3DLABS Wildcat support"
918 depends on (FB = y) && PCI && SPARC64
919 select FB_CFB_FILLRECT
920 select FB_CFB_COPYAREA
921 select FB_CFB_IMAGEBLIT
923 This is the framebuffer device for the Sun XVR-500 and similar
924 graphics cards based upon the 3DLABS Wildcat chipset. The driver
925 only works on sparc64 systems where the system firmware has
926 mostly initialized the card already. It is treated as a
927 completely dumb framebuffer device.
930 bool "Sun XVR-2500 3DLABS Wildcat support"
931 depends on (FB = y) && PCI && SPARC64
932 select FB_CFB_FILLRECT
933 select FB_CFB_COPYAREA
934 select FB_CFB_IMAGEBLIT
936 This is the framebuffer device for the Sun XVR-2500 and similar
937 graphics cards based upon the 3DLABS Wildcat chipset. The driver
938 only works on sparc64 systems where the system firmware has
939 mostly initialized the card already. It is treated as a
940 completely dumb framebuffer device.
943 bool "Sun XVR-1000 support"
944 depends on (FB = y) && SPARC64
945 select FB_CFB_FILLRECT
946 select FB_CFB_COPYAREA
947 select FB_CFB_IMAGEBLIT
949 This is the framebuffer device for the Sun XVR-1000 and similar
950 graphics cards. The driver only works on sparc64 systems where
951 the system firmware has mostly initialized the card already. It
952 is treated as a completely dumb framebuffer device.
955 tristate "NEC PowerVR 2 display support"
956 depends on FB && SH_DREAMCAST
957 select FB_CFB_FILLRECT
958 select FB_CFB_COPYAREA
959 select FB_CFB_IMAGEBLIT
961 Say Y here if you have a PowerVR 2 card in your box. If you plan to
962 run linux on your Dreamcast, you will have to say Y here.
963 This driver may or may not work on other PowerVR 2 cards, but is
964 totally untested. Use at your own risk. If unsure, say N.
966 To compile this driver as a module, choose M here: the
967 module will be called pvr2fb.
969 You can pass several parameters to the driver at boot time or at
970 module load time. The parameters look like "video=pvr2:XXX", where
971 the meaning of XXX can be found at the end of the main source file
972 (<file:drivers/video/pvr2fb.c>). Please see the file
973 <file:Documentation/fb/pvr2fb.txt>.
976 bool "Epson 1355 framebuffer support"
977 depends on (FB = y) && ARCH_CEIVA
978 select FB_CFB_FILLRECT
979 select FB_CFB_COPYAREA
980 select FB_CFB_IMAGEBLIT
982 Build in support for the SED1355 Epson Research Embedded RAMDAC
983 LCD/CRT Controller (since redesignated as the S1D13505) as a
984 framebuffer. Product specs at
985 <http://vdc.epson.com/>.
988 tristate "Epson S1D13XXX framebuffer support"
990 select FB_CFB_FILLRECT
991 select FB_CFB_COPYAREA
992 select FB_CFB_IMAGEBLIT
994 Support for S1D13XXX framebuffer device family (currently only
995 working with S1D13806). Product specs at
996 <http://vdc.epson.com/>
999 tristate "AT91/AT32 LCD Controller support"
1000 depends on FB && HAVE_FB_ATMEL
1001 select FB_CFB_FILLRECT
1002 select FB_CFB_COPYAREA
1003 select FB_CFB_IMAGEBLIT
1005 This enables support for the AT91/AT32 LCD Controller.
1008 bool "Frame Buffer in internal SRAM"
1009 depends on FB_ATMEL && ARCH_AT91SAM9261
1011 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1012 to let frame buffer in external SDRAM.
1015 bool "Use a STN display with AT91/AT32 LCD Controller"
1016 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1019 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1020 Controller. Say N if you want to connect a TFT.
1025 tristate "nVidia Framebuffer Support"
1026 depends on FB && PCI
1027 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1028 select FB_MODE_HELPERS
1029 select FB_CFB_FILLRECT
1030 select FB_CFB_COPYAREA
1031 select FB_CFB_IMAGEBLIT
1035 This driver supports graphics boards with the nVidia chips, TNT
1036 and newer. For very old chipsets, such as the RIVA128, then use
1038 Say Y if you have such a graphics board.
1040 To compile this driver as a module, choose M here: the
1041 module will be called nvidiafb.
1043 config FB_NVIDIA_I2C
1044 bool "Enable DDC Support"
1045 depends on FB_NVIDIA
1048 This enables I2C support for nVidia Chipsets. This is used
1049 only for getting EDID information from the attached display
1050 allowing for robust video mode handling and switching.
1052 Because fbdev-2.6 requires that drivers must be able to
1053 independently validate video mode parameters, you should say Y
1056 config FB_NVIDIA_DEBUG
1057 bool "Lots of debug output"
1058 depends on FB_NVIDIA
1061 Say Y here if you want the nVidia driver to output all sorts
1062 of debugging information to provide to the maintainer when
1063 something goes wrong.
1065 config FB_NVIDIA_BACKLIGHT
1066 bool "Support for backlight control"
1067 depends on FB_NVIDIA
1070 Say Y here if you want to control the backlight of your display.
1073 tristate "nVidia Riva support"
1074 depends on FB && PCI
1075 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1076 select FB_MODE_HELPERS
1077 select FB_CFB_FILLRECT
1078 select FB_CFB_COPYAREA
1079 select FB_CFB_IMAGEBLIT
1083 This driver supports graphics boards with the nVidia Riva/Geforce
1085 Say Y if you have such a graphics board.
1087 To compile this driver as a module, choose M here: the
1088 module will be called rivafb.
1091 bool "Enable DDC Support"
1095 This enables I2C support for nVidia Chipsets. This is used
1096 only for getting EDID information from the attached display
1097 allowing for robust video mode handling and switching.
1099 Because fbdev-2.6 requires that drivers must be able to
1100 independently validate video mode parameters, you should say Y
1103 config FB_RIVA_DEBUG
1104 bool "Lots of debug output"
1108 Say Y here if you want the Riva driver to output all sorts
1109 of debugging information to provide to the maintainer when
1110 something goes wrong.
1112 config FB_RIVA_BACKLIGHT
1113 bool "Support for backlight control"
1117 Say Y here if you want to control the backlight of your display.
1120 tristate "Intel 810/815 support (EXPERIMENTAL)"
1121 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1122 select FB_MODE_HELPERS
1123 select FB_CFB_FILLRECT
1124 select FB_CFB_COPYAREA
1125 select FB_CFB_IMAGEBLIT
1128 This driver supports the on-board graphics built in to the Intel 810
1129 and 815 chipsets. Say Y if you have and plan to use such a board.
1131 To compile this driver as a module, choose M here: the
1132 module will be called i810fb.
1134 For more information, please read
1135 <file:Documentation/fb/intel810.txt>
1138 bool "use VESA Generalized Timing Formula"
1141 If you say Y, then the VESA standard, Generalized Timing Formula
1142 or GTF, will be used to calculate the required video timing values
1143 per video mode. Since the GTF allows nondiscrete timings
1144 (nondiscrete being a range of values as opposed to discrete being a
1145 set of values), you'll be able to use any combination of horizontal
1146 and vertical resolutions, and vertical refresh rates without having
1147 to specify your own timing parameters. This is especially useful
1148 to maximize the performance of an aging display, or if you just
1149 have a display with nonstandard dimensions. A VESA compliant
1150 monitor is recommended, but can still work with non-compliant ones.
1151 If you need or want this, then select this option. The timings may
1152 not be compliant with Intel's recommended values. Use at your own
1155 If you say N, the driver will revert to discrete video timings
1156 using a set recommended by Intel in their documentation.
1161 bool "Enable DDC Support"
1162 depends on FB_I810 && FB_I810_GTF
1167 tristate "Intel LE80578 (Vermilion) support"
1168 depends on FB && PCI && X86
1169 select FB_MODE_HELPERS
1170 select FB_CFB_FILLRECT
1171 select FB_CFB_COPYAREA
1172 select FB_CFB_IMAGEBLIT
1174 This driver supports the LE80578 (Vermilion Range) chipset
1176 config FB_CARILLO_RANCH
1177 tristate "Intel Carillo Ranch support"
1178 depends on FB_LE80578 && FB && PCI && X86
1180 This driver supports the LE80578 (Carillo Ranch) board
1183 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1184 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1185 select FB_MODE_HELPERS
1186 select FB_CFB_FILLRECT
1187 select FB_CFB_COPYAREA
1188 select FB_CFB_IMAGEBLIT
1189 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1190 depends on !DRM_I915
1192 This driver supports the on-board graphics built in to the Intel
1193 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1194 Say Y if you have and plan to use such a board.
1196 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1198 To compile this driver as a module, choose M here: the
1199 module will be called intelfb.
1201 For more information, please read <file:Documentation/fb/intelfb.txt>
1203 config FB_INTEL_DEBUG
1204 bool "Intel driver Debug Messages"
1207 Say Y here if you want the Intel driver to output all sorts
1208 of debugging information to provide to the maintainer when
1209 something goes wrong.
1212 bool "DDC/I2C for Intel framebuffer support"
1217 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1220 tristate "Matrox acceleration"
1221 depends on FB && PCI
1222 select FB_CFB_FILLRECT
1223 select FB_CFB_COPYAREA
1224 select FB_CFB_IMAGEBLIT
1225 select FB_TILEBLITTING
1226 select FB_MACMODES if PPC_PMAC
1228 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1229 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1230 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1231 Matrox G400, G450 or G550 card in your box.
1233 To compile this driver as a module, choose M here: the
1234 module will be called matroxfb.
1236 You can pass several parameters to the driver at boot time or at
1237 module load time. The parameters look like "video=matroxfb:XXX", and
1238 are described in <file:Documentation/fb/matroxfb.txt>.
1240 config FB_MATROX_MILLENIUM
1241 bool "Millennium I/II support"
1242 depends on FB_MATROX
1244 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1245 video card. If you select "Advanced lowlevel driver options" below,
1246 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1247 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1248 also use font widths different from 8.
1250 config FB_MATROX_MYSTIQUE
1251 bool "Mystique support"
1252 depends on FB_MATROX
1254 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1255 video card. If you select "Advanced lowlevel driver options" below,
1256 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1257 packed pixel and 32 bpp packed pixel. You can also use font widths
1261 bool "G100/G200/G400/G450/G550 support"
1262 depends on FB_MATROX
1264 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1265 video card. If you select "Advanced lowlevel driver options", you
1266 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1267 pixel and 32 bpp packed pixel. You can also use font widths
1270 If you need support for G400 secondary head, you must say Y to
1271 "Matrox I2C support" and "G400 second head support" right below.
1272 G450/G550 secondary head and digital output are supported without
1275 The driver starts in monitor mode. You must use the matroxset tool
1276 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1277 swap primary and secondary head outputs, or to change output mode.
1278 Secondary head driver always start in 640x480 resolution and you
1279 must use fbset to change it.
1281 Do not forget that second head supports only 16 and 32 bpp
1282 packed pixels, so it is a good idea to compile them into the kernel
1283 too. You can use only some font widths, as the driver uses generic
1284 painting procedures (the secondary head does not use acceleration
1287 G450/G550 hardware can display TV picture only from secondary CRTC,
1288 and it performs no scaling, so picture must have 525 or 625 lines.
1290 config FB_MATROX_I2C
1291 tristate "Matrox I2C support"
1292 depends on FB_MATROX
1295 This drivers creates I2C buses which are needed for accessing the
1296 DDC (I2C) bus present on all Matroxes, an I2C bus which
1297 interconnects Matrox optional devices, like MGA-TVO on G200 and
1298 G400, and the secondary head DDC bus, present on G400 only.
1300 You can say Y or M here if you want to experiment with monitor
1301 detection code. You must say Y or M here if you want to use either
1302 second head of G400 or MGA-TVO on G200 or G400.
1304 If you compile it as module, it will create a module named
1307 config FB_MATROX_MAVEN
1308 tristate "G400 second head support"
1309 depends on FB_MATROX_G && FB_MATROX_I2C
1311 WARNING !!! This support does not work with G450 !!!
1313 Say Y or M here if you want to use a secondary head (meaning two
1314 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1315 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1316 secondary head output is blanked while you are in X. With XFree
1317 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1318 the fbdev driver on first head and the fbdev driver on second head.
1320 If you compile it as module, two modules are created,
1321 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1322 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1323 also load i2c-matroxfb to get it to run.
1325 The driver starts in monitor mode and you must use the matroxset
1327 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1328 PAL or NTSC or to swap primary and secondary head outputs.
1329 Secondary head driver also always start in 640x480 resolution, you
1330 must use fbset to change it.
1332 Also do not forget that second head supports only 16 and 32 bpp
1333 packed pixels, so it is a good idea to compile them into the kernel
1334 too. You can use only some font widths, as the driver uses generic
1335 painting procedures (the secondary head does not use acceleration
1339 tristate "ATI Radeon display support"
1340 depends on FB && PCI
1341 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1342 select FB_MODE_HELPERS
1343 select FB_CFB_FILLRECT
1344 select FB_CFB_COPYAREA
1345 select FB_CFB_IMAGEBLIT
1346 select FB_MACMODES if PPC_OF
1348 Choose this option if you want to use an ATI Radeon graphics card as
1349 a framebuffer device. There are both PCI and AGP versions. You
1350 don't need to choose this to run the Radeon in plain VGA mode.
1352 There is a product page at
1353 http://products.amd.com/en-us/GraphicCardResult.aspx
1355 config FB_RADEON_I2C
1356 bool "DDC/I2C for ATI Radeon support"
1357 depends on FB_RADEON
1361 Say Y here if you want DDC/I2C support for your Radeon board.
1363 config FB_RADEON_BACKLIGHT
1364 bool "Support for backlight control"
1365 depends on FB_RADEON
1368 Say Y here if you want to control the backlight of your display.
1370 config FB_RADEON_DEBUG
1371 bool "Lots of debug output from Radeon driver"
1372 depends on FB_RADEON
1375 Say Y here if you want the Radeon driver to output all sorts
1376 of debugging information to provide to the maintainer when
1377 something goes wrong.
1380 tristate "ATI Rage128 display support"
1381 depends on FB && PCI
1382 select FB_CFB_FILLRECT
1383 select FB_CFB_COPYAREA
1384 select FB_CFB_IMAGEBLIT
1385 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1386 select FB_MACMODES if PPC_PMAC
1388 This driver supports graphics boards with the ATI Rage128 chips.
1389 Say Y if you have such a graphics board and read
1390 <file:Documentation/fb/aty128fb.txt>.
1392 To compile this driver as a module, choose M here: the
1393 module will be called aty128fb.
1395 config FB_ATY128_BACKLIGHT
1396 bool "Support for backlight control"
1397 depends on FB_ATY128
1400 Say Y here if you want to control the backlight of your display.
1403 tristate "ATI Mach64 display support" if PCI || ATARI
1404 depends on FB && !SPARC32
1405 select FB_CFB_FILLRECT
1406 select FB_CFB_COPYAREA
1407 select FB_CFB_IMAGEBLIT
1408 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1409 select FB_MACMODES if PPC
1411 This driver supports graphics boards with the ATI Mach64 chips.
1412 Say Y if you have such a graphics board.
1414 To compile this driver as a module, choose M here: the
1415 module will be called atyfb.
1418 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1419 depends on PCI && FB_ATY
1420 default y if SPARC64 && PCI
1422 Say Y here to support use of ATI's 64-bit Rage boards (or other
1423 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1424 framebuffer device. The ATI product support page for these boards
1425 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1427 config FB_ATY_GENERIC_LCD
1428 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1429 depends on FB_ATY_CT
1431 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1432 Rage XC, or Rage XL chipset.
1435 bool "Mach64 GX support" if PCI
1439 Say Y here to support use of the ATI Mach64 Graphics Expression
1440 board (or other boards based on the Mach64 GX chipset) as a
1441 framebuffer device. The ATI product support page for these boards
1443 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1445 config FB_ATY_BACKLIGHT
1446 bool "Support for backlight control"
1450 Say Y here if you want to control the backlight of your display.
1453 tristate "S3 Trio/Virge support"
1454 depends on FB && PCI
1455 select FB_CFB_FILLRECT
1456 select FB_CFB_COPYAREA
1457 select FB_CFB_IMAGEBLIT
1458 select FB_TILEBLITTING
1461 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1463 Driver for graphics boards with S3 Trio / S3 Virge chip.
1466 bool "DDC for S3 support"
1471 Say Y here if you want DDC support for your S3 graphics card.
1474 tristate "S3 Savage support"
1475 depends on FB && PCI && EXPERIMENTAL
1476 select FB_MODE_HELPERS
1477 select FB_CFB_FILLRECT
1478 select FB_CFB_COPYAREA
1479 select FB_CFB_IMAGEBLIT
1482 This driver supports notebooks and computers with S3 Savage PCI/AGP
1485 Say Y if you have such a graphics card.
1487 To compile this driver as a module, choose M here; the module
1488 will be called savagefb.
1490 config FB_SAVAGE_I2C
1491 bool "Enable DDC2 Support"
1492 depends on FB_SAVAGE
1495 This enables I2C support for S3 Savage Chipsets. This is used
1496 only for getting EDID information from the attached display
1497 allowing for robust video mode handling and switching.
1499 Because fbdev-2.6 requires that drivers must be able to
1500 independently validate video mode parameters, you should say Y
1503 config FB_SAVAGE_ACCEL
1504 bool "Enable Console Acceleration"
1505 depends on FB_SAVAGE
1508 This option will compile in console acceleration support. If
1509 the resulting framebuffer console has bothersome glitches, then
1513 tristate "SiS/XGI display support"
1514 depends on FB && PCI
1515 select FB_CFB_FILLRECT
1516 select FB_CFB_COPYAREA
1517 select FB_CFB_IMAGEBLIT
1518 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1520 This is the frame buffer device driver for the SiS 300, 315, 330
1521 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1522 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1524 To compile this driver as a module, choose M here; the module
1525 will be called sisfb.
1528 bool "SiS 300 series support"
1531 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1534 bool "SiS 315/330/340 series and XGI support"
1537 Say Y here to support use of the SiS 315, 330 and 340 series
1538 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1539 as XGI V3XT, V5, V8 and Z7.
1542 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1543 depends on FB && PCI && X86
1544 select FB_CFB_FILLRECT
1545 select FB_CFB_COPYAREA
1546 select FB_CFB_IMAGEBLIT
1551 This is the frame buffer device driver for Graphics chips of VIA
1552 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1553 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1555 Say Y if you have a VIA UniChrome graphics board.
1557 To compile this driver as a module, choose M here: the
1558 module will be called viafb.
1562 config FB_VIA_DIRECT_PROCFS
1563 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1567 Allow direct hardware access to some output registers via procfs.
1568 This is dangerous but may provide the only chance to get the
1569 correct output device configuration.
1570 Its use is strongly discouraged.
1572 config FB_VIA_X_COMPATIBILITY
1573 bool "X server compatibility"
1577 This option reduces the functionality (power saving, ...) of the
1578 framebuffer to avoid negative impact on the OpenChrome X server.
1579 If you use any X server other than fbdev you should enable this
1580 otherwise it should be safe to disable it and allow using all
1586 tristate "NeoMagic display support"
1587 depends on FB && PCI
1588 select FB_MODE_HELPERS
1589 select FB_CFB_FILLRECT
1590 select FB_CFB_COPYAREA
1591 select FB_CFB_IMAGEBLIT
1594 This driver supports notebooks with NeoMagic PCI chips.
1595 Say Y if you have such a graphics card.
1597 To compile this driver as a module, choose M here: the
1598 module will be called neofb.
1601 tristate "IMG Kyro support"
1602 depends on FB && PCI
1603 select FB_CFB_FILLRECT
1604 select FB_CFB_COPYAREA
1605 select FB_CFB_IMAGEBLIT
1607 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1610 To compile this driver as a module, choose M here: the
1611 module will be called kyrofb.
1614 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1615 depends on FB && PCI
1616 select FB_CFB_IMAGEBLIT
1617 select FB_CFB_FILLRECT
1618 select FB_CFB_COPYAREA
1619 select FB_MODE_HELPERS
1621 This driver supports graphics boards with the 3Dfx Banshee,
1622 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1623 such a graphics board.
1625 To compile this driver as a module, choose M here: the
1626 module will be called tdfxfb.
1628 config FB_3DFX_ACCEL
1629 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1630 depends on FB_3DFX && EXPERIMENTAL
1632 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1633 device driver with acceleration functions.
1636 bool "Enable DDC/I2C support"
1637 depends on FB_3DFX && EXPERIMENTAL
1641 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1644 tristate "3Dfx Voodoo Graphics (sst1) support"
1645 depends on FB && PCI
1646 select FB_CFB_FILLRECT
1647 select FB_CFB_COPYAREA
1648 select FB_CFB_IMAGEBLIT
1650 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1651 Voodoo2 (cvg) based graphics card.
1653 To compile this driver as a module, choose M here: the
1654 module will be called sstfb.
1656 WARNING: Do not use any application that uses the 3D engine
1657 (namely glide) while using this driver.
1658 Please read the <file:Documentation/fb/sstfb.txt> for supported
1659 options and other important info support.
1662 tristate "VIA VT8623 support"
1663 depends on FB && PCI
1664 select FB_CFB_FILLRECT
1665 select FB_CFB_COPYAREA
1666 select FB_CFB_IMAGEBLIT
1667 select FB_TILEBLITTING
1670 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1672 Driver for CastleRock integrated graphics core in the
1673 VIA VT8623 [Apollo CLE266] chipset.
1676 tristate "Trident/CyberXXX/CyberBlade support"
1677 depends on FB && PCI
1678 select FB_CFB_FILLRECT
1679 select FB_CFB_COPYAREA
1680 select FB_CFB_IMAGEBLIT
1682 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1683 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1685 There are also integrated versions of these chips called CyberXXXX,
1686 CyberImage or CyberBlade. These chips are mostly found in laptops
1687 but also on some motherboards including early VIA EPIA motherboards.
1688 For more information, read <file:Documentation/fb/tridentfb.txt>
1690 Say Y if you have such a graphics board.
1692 To compile this driver as a module, choose M here: the
1693 module will be called tridentfb.
1696 tristate "ARK 2000PV support"
1697 depends on FB && PCI
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1701 select FB_TILEBLITTING
1704 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1706 Driver for PCI graphics boards with ARK 2000PV chip
1707 and ICS 5342 RAMDAC.
1710 tristate "Permedia3 support (EXPERIMENTAL)"
1711 depends on FB && PCI && EXPERIMENTAL
1712 select FB_CFB_FILLRECT
1713 select FB_CFB_COPYAREA
1714 select FB_CFB_IMAGEBLIT
1716 This is the frame buffer device driver for the 3DLabs Permedia3
1717 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1718 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1719 and maybe other boards.
1722 tristate "Fujitsu carmine frame buffer support"
1723 depends on FB && PCI
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1728 This is the frame buffer device driver for the Fujitsu Carmine chip.
1729 The driver provides two independent frame buffer devices.
1732 depends on FB_CARMINE
1733 prompt "DRAM timing"
1734 default FB_CARMINE_DRAM_EVAL
1736 config FB_CARMINE_DRAM_EVAL
1737 bool "Eval board timings"
1739 Use timings which work on the eval card.
1741 config CARMINE_DRAM_CUSTOM
1742 bool "Custom board timings"
1744 Use custom board timings.
1748 bool "Au1100 LCD Driver"
1749 depends on (FB = y) && MIPS && SOC_AU1100
1750 select FB_CFB_FILLRECT
1751 select FB_CFB_COPYAREA
1752 select FB_CFB_IMAGEBLIT
1754 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1755 various panels and CRTs by passing in kernel cmd line option
1756 au1100fb:panel=<name>.
1759 bool "Au1200 LCD Driver"
1760 depends on (FB = y) && MIPS && SOC_AU1200
1761 select FB_CFB_FILLRECT
1762 select FB_CFB_COPYAREA
1763 select FB_CFB_IMAGEBLIT
1765 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1766 various panels and CRTs by passing in kernel cmd line option
1767 au1200fb:panel=<name>.
1770 bool "VT8500 LCD Driver"
1771 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1772 select FB_WMT_GE_ROPS
1773 select FB_SYS_IMAGEBLIT
1775 This is the framebuffer driver for VIA VT8500 integrated LCD
1779 bool "WM8505 frame buffer support"
1780 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1781 select FB_WMT_GE_ROPS
1782 select FB_SYS_IMAGEBLIT
1784 This is the framebuffer driver for WonderMedia WM8505
1785 integrated LCD controller.
1787 source "drivers/video/geode/Kconfig"
1790 tristate "HD64461 Frame Buffer support"
1791 depends on FB && HD64461
1792 select FB_CFB_FILLRECT
1793 select FB_CFB_COPYAREA
1794 select FB_CFB_IMAGEBLIT
1796 This is the frame buffer device driver for the Hitachi HD64461 LCD
1800 bool "PMAG-AA TURBOchannel framebuffer support"
1801 depends on (FB = y) && TC
1802 select FB_CFB_FILLRECT
1803 select FB_CFB_COPYAREA
1804 select FB_CFB_IMAGEBLIT
1806 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1807 used mainly in the MIPS-based DECstation series.
1810 tristate "PMAG-BA TURBOchannel framebuffer support"
1812 select FB_CFB_FILLRECT
1813 select FB_CFB_COPYAREA
1814 select FB_CFB_IMAGEBLIT
1816 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1817 used mainly in the MIPS-based DECstation series.
1820 tristate "PMAGB-B TURBOchannel framebuffer support"
1822 select FB_CFB_FILLRECT
1823 select FB_CFB_COPYAREA
1824 select FB_CFB_IMAGEBLIT
1826 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1827 in the MIPS-based DECstation series. The card is currently only
1828 supported in 1280x1024x8 mode.
1831 bool "Maxine (Personal DECstation) onboard framebuffer support"
1832 depends on (FB = y) && MACH_DECSTATION
1833 select FB_CFB_FILLRECT
1834 select FB_CFB_COPYAREA
1835 select FB_CFB_IMAGEBLIT
1837 Support for the onboard framebuffer (1024x768x8) in the Personal
1838 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1842 bool "G364 frame buffer support"
1843 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1849 Olivetti M700-10 systems.
1852 bool "Motorola 68328 native frame buffer support"
1853 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Say Y here if you want to support the built-in frame buffer of
1859 the Motorola 68328 CPU family.
1862 tristate "PXA168/910 LCD framebuffer support"
1863 depends on FB && (CPU_PXA168 || CPU_PXA910)
1864 select FB_CFB_FILLRECT
1865 select FB_CFB_COPYAREA
1866 select FB_CFB_IMAGEBLIT
1868 Frame buffer driver for the built-in LCD controller in the Marvell
1872 tristate "PXA LCD framebuffer support"
1873 depends on FB && ARCH_PXA
1874 select FB_CFB_FILLRECT
1875 select FB_CFB_COPYAREA
1876 select FB_CFB_IMAGEBLIT
1878 Frame buffer driver for the built-in LCD controller in the Intel
1881 This driver is also available as a module ( = code which can be
1882 inserted and removed from the running kernel whenever you want). The
1883 module will be called pxafb. If you want to compile it as a module,
1884 say M here and read <file:Documentation/kbuild/modules.txt>.
1888 config FB_PXA_OVERLAY
1889 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1891 depends on FB_PXA && (PXA27x || PXA3xx)
1893 config FB_PXA_SMARTPANEL
1894 bool "PXA Smartpanel LCD support"
1898 config FB_PXA_PARAMETERS
1899 bool "PXA LCD command line parameters"
1903 Enable the use of kernel command line or module parameters
1904 to configure the physical properties of the LCD panel when
1905 using the PXA LCD driver.
1907 This option allows you to override the panel parameters
1908 supplied by the platform in order to support multiple
1909 different models of flatpanel. If you will only be using a
1910 single model of flatpanel then you can safely leave this
1913 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1916 tristate "PXA3xx 2D graphics accelerator driver"
1919 Kernelspace driver for the 2D graphics controller unit (GCU)
1920 found on PXA3xx processors. There is a counterpart driver in the
1921 DirectFB suite, see http://www.directfb.org/
1923 If you compile this as a module, it will be called pxa3xx_gcu.
1926 tristate "2700G LCD framebuffer support"
1927 depends on FB && ARCH_PXA
1928 select FB_CFB_FILLRECT
1929 select FB_CFB_COPYAREA
1930 select FB_CFB_IMAGEBLIT
1932 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1936 bool "Enable debugging info via debugfs"
1937 depends on FB_MBX && DEBUG_FS
1940 Enable this if you want debugging information using the debug
1941 filesystem (debugfs)
1946 tristate "Freescale DIU framebuffer support"
1947 depends on FB && FSL_SOC
1948 select FB_MODE_HELPERS
1949 select FB_CFB_FILLRECT
1950 select FB_CFB_COPYAREA
1951 select FB_CFB_IMAGEBLIT
1952 select PPC_LIB_RHEAP
1954 Framebuffer driver for the Freescale SoC DIU
1957 tristate "W100 frame buffer support"
1958 depends on FB && ARCH_PXA
1959 select FB_CFB_FILLRECT
1960 select FB_CFB_COPYAREA
1961 select FB_CFB_IMAGEBLIT
1963 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1964 It can also drive the w3220 chip found on iPAQ hx4700.
1966 This driver is also available as a module ( = code which can be
1967 inserted and removed from the running kernel whenever you want). The
1968 module will be called w100fb. If you want to compile it as a module,
1969 say M here and read <file:Documentation/kbuild/modules.txt>.
1973 config FB_SH_MOBILE_LCDC
1974 tristate "SuperH Mobile LCDC framebuffer support"
1975 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1976 select FB_SYS_FILLRECT
1977 select FB_SYS_COPYAREA
1978 select FB_SYS_IMAGEBLIT
1980 select FB_DEFERRED_IO
1982 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1984 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1986 config FB_SH_MOBILE_HDMI
1987 tristate "SuperH Mobile HDMI controller support"
1988 depends on FB_SH_MOBILE_LCDC
1989 select FB_MODE_HELPERS
1994 Driver for the on-chip SH-Mobile HDMI controller.
1996 config FB_SH_MOBILE_MERAM
1997 tristate "SuperH Mobile MERAM read ahead support for LCDC"
1998 depends on FB_SH_MOBILE_LCDC
2001 Enable MERAM support for the SH-Mobile LCD controller.
2003 This will allow for caching of the framebuffer to provide more
2004 reliable access under heavy main memory bus traffic situations.
2005 Up to 4 memory channels can be configured, allowing 4 RGB or
2006 2 YCbCr framebuffers to be configured.
2009 tristate "Toshiba Mobile IO FrameBuffer support"
2010 depends on FB && MFD_CORE
2011 select FB_CFB_FILLRECT
2012 select FB_CFB_COPYAREA
2013 select FB_CFB_IMAGEBLIT
2015 Frame buffer driver for the Toshiba Mobile IO integrated as found
2016 on the Sharp SL-6000 series
2018 This driver is also available as a module ( = code which can be
2019 inserted and removed from the running kernel whenever you want). The
2020 module will be called tmiofb. If you want to compile it as a module,
2021 say M here and read <file:Documentation/kbuild/modules.txt>.
2025 config FB_TMIO_ACCELL
2026 bool "tmiofb acceleration"
2031 tristate "Samsung S3C framebuffer support"
2032 depends on FB && S3C_DEV_FB
2033 select FB_CFB_FILLRECT
2034 select FB_CFB_COPYAREA
2035 select FB_CFB_IMAGEBLIT
2037 Frame buffer driver for the built-in FB controller in the Samsung
2038 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2039 and the S3C64XX series such as the S3C6400 and S3C6410.
2041 These chips all have the same basic framebuffer design with the
2042 actual capabilities depending on the chip. For instance the S3C6400
2043 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2044 currently only have two.
2046 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2048 config FB_S3C_DEBUG_REGWRITE
2049 bool "Debug register writes"
2052 Show all register writes via printk(KERN_DEBUG)
2055 tristate "S3C2410 LCD framebuffer support"
2056 depends on FB && ARCH_S3C2410
2057 select FB_CFB_FILLRECT
2058 select FB_CFB_COPYAREA
2059 select FB_CFB_IMAGEBLIT
2061 Frame buffer driver for the built-in LCD controller in the Samsung
2064 This driver is also available as a module ( = code which can be
2065 inserted and removed from the running kernel whenever you want). The
2066 module will be called s3c2410fb. If you want to compile it as a module,
2067 say M here and read <file:Documentation/kbuild/modules.txt>.
2070 config FB_S3C2410_DEBUG
2071 bool "S3C2410 lcd debug messages"
2072 depends on FB_S3C2410
2074 Turn on debugging messages. Note that you can set/unset at run time
2078 tristate "RK29 lcd control"
2080 select FB_CFB_FILLRECT
2081 select FB_CFB_COPYAREA
2082 select FB_CFB_IMAGEBLIT
2084 Framebuffer driver for RK29 Platform,select it if you using rk29
2087 bool "fb use ipp to scale UI or rotate video"
2090 this function be used scale-up UI when video, it only support RGB565 UI;
2091 it can use to rotate video .
2093 config FB_SCALING_OSD
2094 bool "fb scale OSD support when video playing "
2095 depends on FB_WORK_IPP
2097 this function be used scale-up UI when video, it only support RGB565 UI;
2099 config FB_SCALING_OSD_1080P
2100 bool "fb scale OSD support when video playing in 1080P "
2101 depends on FB_WORK_IPP && FB_SCALING_OSD
2103 this function be used scale-up UI when video, it only support RGB565 UI;
2104 should set SCALE_UI_1080P_VIDEO to 1 in android
2105 config FB_ROTATE_VIDEO
2106 bool "fb video rotate support"
2107 depends on FB_WORK_IPP
2109 this function can use to rotate video .
2110 config FB_MIRROR_X_Y
2111 bool "fb video rotate support x y mirror"
2112 depends on FB_ROTATE_VIDEO
2114 this function can use to x y mirror video .
2115 config CLOSE_WIN1_DYNAMIC
2116 bool "close win1 dynamically when video"
2119 this function can close win1 when video and it have no data in fb0
2126 bool "NUC900 LCD framebuffer support"
2127 depends on FB && ARCH_W90X900
2128 select FB_CFB_FILLRECT
2129 select FB_CFB_COPYAREA
2130 select FB_CFB_IMAGEBLIT
2132 Frame buffer driver for the built-in LCD controller in the Nuvoton
2135 config GPM1040A0_320X240
2136 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2137 depends on FB_NUC900
2139 config FB_NUC900_DEBUG
2140 bool "NUC900 lcd debug messages"
2141 depends on FB_NUC900
2143 Turn on debugging messages. Note that you can set/unset at run time
2147 tristate "Silicon Motion SM501 framebuffer support"
2148 depends on FB && MFD_SM501
2149 select FB_CFB_FILLRECT
2150 select FB_CFB_COPYAREA
2151 select FB_CFB_IMAGEBLIT
2153 Frame buffer driver for the CRT and LCD controllers in the Silicon
2156 This driver is also available as a module ( = code which can be
2157 inserted and removed from the running kernel whenever you want). The
2158 module will be called sm501fb. If you want to compile it as a module,
2159 say M here and read <file:Documentation/kbuild/modules.txt>.
2164 tristate "Displaylink USB Framebuffer support"
2165 depends on FB && USB
2166 select FB_MODE_HELPERS
2167 select FB_SYS_FILLRECT
2168 select FB_SYS_COPYAREA
2169 select FB_SYS_IMAGEBLIT
2171 select FB_DEFERRED_IO
2173 This is a kernel framebuffer driver for DisplayLink USB devices.
2174 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2175 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2176 To compile as a module, choose M here: the module name is udlfb.
2178 config FB_PNX4008_DUM
2179 tristate "Display Update Module support on Philips PNX4008 board"
2180 depends on FB && ARCH_PNX4008
2182 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2184 config FB_PNX4008_DUM_RGB
2185 tristate "RGB Framebuffer support on Philips PNX4008 board"
2186 depends on FB_PNX4008_DUM
2187 select FB_CFB_FILLRECT
2188 select FB_CFB_COPYAREA
2189 select FB_CFB_IMAGEBLIT
2191 Say Y here to enable support for PNX4008 RGB Framebuffer
2193 config FB_IBM_GXT4500
2194 tristate "Framebuffer support for IBM GXT4500P adaptor"
2195 depends on FB && PPC
2196 select FB_CFB_FILLRECT
2197 select FB_CFB_COPYAREA
2198 select FB_CFB_IMAGEBLIT
2200 Say Y here to enable support for the IBM GXT4500P display
2201 adaptor, found on some IBM System P (pSeries) machines.
2204 tristate "PS3 GPU framebuffer driver"
2205 depends on FB && PS3_PS3AV
2206 select FB_SYS_FILLRECT
2207 select FB_SYS_COPYAREA
2208 select FB_SYS_IMAGEBLIT
2210 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2212 Include support for the virtual frame buffer in the PS3 platform.
2214 config FB_PS3_DEFAULT_SIZE_M
2215 int "PS3 default frame buffer size (in MiB)"
2219 This is the default size (in MiB) of the virtual frame buffer in
2221 The default value can be overridden on the kernel command line
2222 using the "ps3fb" option (e.g. "ps3fb=9M");
2225 tristate "Xilinx frame buffer support"
2226 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2227 select FB_CFB_FILLRECT
2228 select FB_CFB_COPYAREA
2229 select FB_CFB_IMAGEBLIT
2231 Include support for the Xilinx ML300/ML403 reference design
2232 framebuffer. ML300 carries a 640*480 LCD display on the board,
2233 ML403 uses a standard DB15 VGA connector.
2236 tristate "Cobalt server LCD frame buffer support"
2237 depends on FB && MIPS_COBALT
2240 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2241 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2242 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2243 select FB_CFB_FILLRECT
2244 select FB_CFB_COPYAREA
2245 select FB_CFB_IMAGEBLIT
2247 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2248 (D)STN/TFT LCD Controller.
2249 Supports display resolutions up to 1024x1024 pixel, grayscale and
2250 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2251 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2252 panels <= 320 pixel horizontal resolution.
2255 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2256 depends on FB && ARCH_DAVINCI_DA8XX
2257 select FB_CFB_FILLRECT
2258 select FB_CFB_COPYAREA
2259 select FB_CFB_IMAGEBLIT
2261 This is the frame buffer device driver for the TI LCD controller
2262 found on DA8xx/OMAP-L1xx SoCs.
2266 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2268 select FB_SYS_FILLRECT
2269 select FB_SYS_COPYAREA
2270 select FB_SYS_IMAGEBLIT
2273 This is a `virtual' frame buffer device. It operates on a chunk of
2274 unswappable kernel memory instead of on the memory of a graphics
2275 board. This means you cannot see any output sent to this frame
2276 buffer device, while it does consume precious memory. The main use
2277 of this frame buffer device is testing and debugging the frame
2278 buffer subsystem. Do NOT enable it for normal systems! To protect
2279 the innocent, it has to be enabled explicitly at boot time using the
2280 kernel option `video=vfb:'.
2282 To compile this driver as a module, choose M here: the
2283 module will be called vfb. In order to load it, you must use
2284 the vfb_enable=1 option.
2288 config XEN_FBDEV_FRONTEND
2289 tristate "Xen virtual frame buffer support"
2290 depends on FB && XEN
2291 select FB_SYS_FILLRECT
2292 select FB_SYS_COPYAREA
2293 select FB_SYS_IMAGEBLIT
2295 select FB_DEFERRED_IO
2296 select XEN_XENBUS_FRONTEND
2299 This driver implements the front-end of the Xen virtual
2300 frame buffer driver. It communicates with a back-end
2304 tristate "E-Ink Metronome/8track controller support"
2306 select FB_SYS_FILLRECT
2307 select FB_SYS_COPYAREA
2308 select FB_SYS_IMAGEBLIT
2310 select FB_DEFERRED_IO
2312 This driver implements support for the E-Ink Metronome
2313 controller. The pre-release name for this device was 8track
2314 and could also have been called by some vendors as PVI-nnnn.
2317 tristate "Fujitsu MB862xx GDC support"
2319 depends on PCI || (OF && PPC)
2320 select FB_CFB_FILLRECT
2321 select FB_CFB_COPYAREA
2322 select FB_CFB_IMAGEBLIT
2324 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2327 prompt "GDC variant"
2328 depends on FB_MB862XX
2330 config FB_MB862XX_PCI_GDC
2331 bool "Carmine/Coral-P(A) GDC"
2334 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2335 PCI graphics controller devices.
2337 config FB_MB862XX_LIME
2339 depends on OF && PPC
2340 select FB_FOREIGN_ENDIAN
2341 select FB_LITTLE_ENDIAN
2343 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2347 config FB_MB862XX_I2C
2348 bool "Support I2C bus on MB862XX GDC"
2349 depends on FB_MB862XX && I2C
2352 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2353 driver to support accessing I2C devices on controller's I2C bus.
2354 These are usually some video decoder chips.
2357 tristate "EP93XX frame buffer support"
2358 depends on FB && ARCH_EP93XX
2359 select FB_CFB_FILLRECT
2360 select FB_CFB_COPYAREA
2361 select FB_CFB_IMAGEBLIT
2363 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2364 This driver is also available as a module. The module will be called
2367 config FB_PRE_INIT_FB
2368 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2369 depends on FB && FB_MB862XX_LIME
2371 Select this option if display contents should be inherited as set by
2375 tristate "MSM Framebuffer support"
2376 depends on FB && ARCH_MSM
2377 select FB_CFB_FILLRECT
2378 select FB_CFB_COPYAREA
2379 select FB_CFB_IMAGEBLIT
2382 tristate "MX3 Framebuffer support"
2383 depends on FB && MX3_IPU
2384 select FB_CFB_FILLRECT
2385 select FB_CFB_COPYAREA
2386 select FB_CFB_IMAGEBLIT
2389 This is a framebuffer device for the i.MX31 LCD Controller. So
2390 far only synchronous displays are supported. If you plan to use
2391 an LCD display with your i.MX31 system, say Y here.
2393 config FB_BROADSHEET
2394 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2396 select FB_SYS_FILLRECT
2397 select FB_SYS_COPYAREA
2398 select FB_SYS_IMAGEBLIT
2400 select FB_DEFERRED_IO
2402 This driver implements support for the E-Ink Broadsheet
2403 controller. The release name for this device was Epson S1D13521
2404 and could also have been called by other names when coupled with
2408 tristate "JZ4740 LCD framebuffer support"
2409 depends on FB && MACH_JZ4740
2410 select FB_SYS_FILLRECT
2411 select FB_SYS_COPYAREA
2412 select FB_SYS_IMAGEBLIT
2414 Framebuffer support for the JZ4740 SoC.
2417 tristate "MXS LCD framebuffer support"
2418 depends on FB && ARCH_MXS
2419 select FB_CFB_FILLRECT
2420 select FB_CFB_COPYAREA
2421 select FB_CFB_IMAGEBLIT
2423 Framebuffer support for the MXS SoC.
2425 config FB_PUV3_UNIGFX
2426 tristate "PKUnity v3 Unigfx framebuffer support"
2427 depends on FB && UNICORE32 && ARCH_PUV3
2428 select FB_SYS_FILLRECT
2429 select FB_SYS_COPYAREA
2430 select FB_SYS_IMAGEBLIT
2433 Choose this option if you want to use the Unigfx device as a
2434 framebuffer device. Without the support of PCI & AGP.
2436 source "drivers/video/omap/Kconfig"
2437 source "drivers/video/omap2/Kconfig"
2439 source "drivers/video/backlight/Kconfig"
2440 source "drivers/video/display/Kconfig"
2441 source "drivers/video/hdmi/Kconfig"
2444 source "drivers/video/console/Kconfig"
2447 if FB || SGI_NEWPORT_CONSOLE
2448 source "drivers/video/logo/Kconfig"