5 menu "Graphics support"
16 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
18 config SH_LCD_MIPI_DSI
21 source "drivers/char/agp/Kconfig"
23 source "drivers/gpu/vga/Kconfig"
25 source "drivers/gpu/drm/Kconfig"
27 source "drivers/gpu/stub/Kconfig"
33 config VIDEO_OUTPUT_CONTROL
34 tristate "Lowlevel video output switch controls"
36 This framework adds support for low-level control of the video
40 tristate "Support for frame buffer devices"
42 The frame buffer device provides an abstraction for the graphics
43 hardware. It represents the frame buffer of some video hardware and
44 allows application software to access the graphics hardware through
45 a well-defined interface, so the software doesn't need to know
46 anything about the low-level (hardware register) stuff.
48 Frame buffer devices work identically across the different
49 architectures supported by Linux and make the implementation of
50 application programs easier and more portable; at this point, an X
51 server exists which uses the frame buffer device exclusively.
52 On several non-X86 architectures, the frame buffer device is the
53 only way to use the graphics hardware.
55 The device is accessed through special device nodes, usually located
56 in the /dev directory, i.e. /dev/fb*.
58 You need an utility program called fbset to make full use of frame
59 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
60 and the Framebuffer-HOWTO at
61 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
64 Say Y here and to the driver for your graphics board below if you
65 are compiling a kernel for a non-x86 architecture.
67 If you are compiling for the x86 architecture, you can say Y if you
68 want to play with it, but it is not essential. Please note that
69 running graphical applications that directly touch the hardware
70 (e.g. an accelerated X server) and that are not frame buffer
71 device-aware may cause unexpected results. If unsure, say N.
74 bool "Enable firmware EDID"
78 This enables access to the EDID transferred from the firmware.
79 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
80 transfers do not work for your driver and if you are using
81 nvidiafb, i810fb or savagefb.
83 In general, choosing Y for this option is safe. If you
84 experience extremely long delays while booting before you get
85 something on your display, try setting this to N. Matrox cards in
86 combination with certain motherboards and monitors are known to
87 suffer from this problem.
96 config FB_BOOT_VESA_SUPPORT
101 If true, at least one selected framebuffer driver can take advantage
102 of VESA video modes set at an early boot stage via the vga= parameter.
104 config FB_CFB_FILLRECT
109 Include the cfb_fillrect function for generic software rectangle
110 filling. This is used by drivers that don't provide their own
111 (accelerated) version.
113 config FB_CFB_COPYAREA
118 Include the cfb_copyarea function for generic software area copying.
119 This is used by drivers that don't provide their own (accelerated)
122 config FB_CFB_IMAGEBLIT
127 Include the cfb_imageblit function for generic software image
128 blitting. This is used by drivers that don't provide their own
129 (accelerated) version.
131 config FB_CFB_REV_PIXELS_IN_BYTE
136 Allow generic frame-buffer functions to work on displays with 1, 2
137 and 4 bits per pixel depths which has opposite order of pixels in
138 byte order to bytes in long order.
140 config FB_SYS_FILLRECT
145 Include the sys_fillrect function for generic software rectangle
146 filling. This is used by drivers that don't provide their own
147 (accelerated) version and the framebuffer is in system RAM.
149 config FB_SYS_COPYAREA
154 Include the sys_copyarea function for generic software area copying.
155 This is used by drivers that don't provide their own (accelerated)
156 version and the framebuffer is in system RAM.
158 config FB_SYS_IMAGEBLIT
163 Include the sys_imageblit function for generic software image
164 blitting. This is used by drivers that don't provide their own
165 (accelerated) version and the framebuffer is in system RAM.
167 menuconfig FB_FOREIGN_ENDIAN
168 bool "Framebuffer foreign endianness support"
171 This menu will let you enable support for the framebuffers with
172 non-native endianness (e.g. Little-Endian framebuffer on a
173 Big-Endian machine). Most probably you don't have such hardware,
174 so it's safe to say "n" here.
177 prompt "Choice endianness support"
178 depends on FB_FOREIGN_ENDIAN
180 config FB_BOTH_ENDIAN
181 bool "Support for Big- and Little-Endian framebuffers"
184 bool "Support for Big-Endian framebuffers only"
186 config FB_LITTLE_ENDIAN
187 bool "Support for Little-Endian framebuffers only"
196 config FB_WMT_GE_ROPS
201 Include functions for accelerated rectangle filling and area
202 copying using WonderMedia Graphics Engine operations.
204 config FB_DEFERRED_IO
211 depends on FB_DEFERRED_IO
218 Common utility functions useful to fbdev drivers of VGA-based
229 select BACKLIGHT_LCD_SUPPORT
230 select BACKLIGHT_CLASS_DEVICE
233 config FB_MODE_HELPERS
234 bool "Enable Video Mode Handling Helpers"
238 This enables functions for handling video modes using the
239 Generalized Timing Formula and the EDID parser. A few drivers rely
240 on this feature such as the radeonfb, rivafb, and the i810fb. If
241 your driver does not take advantage of this feature, choosing Y will
242 just increase the kernel size by about 5K.
244 config FB_TILEBLITTING
245 bool "Enable Tile Blitting Support"
249 This enables tile blitting. Tile blitting is a drawing technique
250 where the screen is divided into rectangular sections (tiles), whereas
251 the standard blitting divides the screen into pixels. Because the
252 default drawing element is a tile, drawing functions will be passed
253 parameters in terms of number of tiles instead of number of pixels.
254 For example, to draw a single character, instead of using bitmaps,
255 an index to an array of bitmaps will be used. To clear or move a
256 rectangular section of a screen, the rectangle will be described in
257 terms of number of tiles in the x- and y-axis.
259 This is particularly important to one driver, matroxfb. If
262 comment "Frame buffer hardware drivers"
266 tristate "Cirrus Logic support"
267 depends on FB && (ZORRO || PCI)
268 select FB_CFB_FILLRECT
269 select FB_CFB_COPYAREA
270 select FB_CFB_IMAGEBLIT
272 This enables support for Cirrus Logic GD542x/543x based boards on
273 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
275 If you have a PCI-based system, this enables support for these
276 chips: GD-543x, GD-544x, GD-5480.
278 Please read the file <file:Documentation/fb/cirrusfb.txt>.
280 Say N unless you have such a graphics board or plan to get one
281 before you next recompile the kernel.
284 tristate "Permedia2 support"
285 depends on FB && ((AMIGA && BROKEN) || PCI)
286 select FB_CFB_FILLRECT
287 select FB_CFB_COPYAREA
288 select FB_CFB_IMAGEBLIT
290 This is the frame buffer device driver for cards based on
291 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
292 The driver was tested on the following cards:
293 Diamond FireGL 1000 PRO AGP
294 ELSA Gloria Synergy PCI
295 Appian Jeronimo PRO (both heads) PCI
296 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
297 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
298 ASK Graphic Blaster Exxtreme AGP
300 To compile this driver as a module, choose M here: the
301 module will be called pm2fb.
303 config FB_PM2_FIFO_DISCONNECT
304 bool "enable FIFO disconnect feature"
305 depends on FB_PM2 && PCI
307 Support the Permedia2 FIFO disconnect feature.
310 tristate "ARM PrimeCell PL110 support"
311 depends on FB && ARM && ARM_AMBA
312 select FB_CFB_FILLRECT
313 select FB_CFB_COPYAREA
314 select FB_CFB_IMAGEBLIT
316 This framebuffer device driver is for the ARM PrimeCell PL110
317 Colour LCD controller. ARM PrimeCells provide the building
318 blocks for System on a Chip devices.
320 If you want to compile this as a module (=code which can be
321 inserted into and removed from the running kernel), say M
322 here and read <file:Documentation/kbuild/modules.txt>. The module
323 will be called amba-clcd.
326 bool "Acorn VIDC support"
327 depends on (FB = y) && ARM && ARCH_ACORN
328 select FB_CFB_FILLRECT
329 select FB_CFB_COPYAREA
330 select FB_CFB_IMAGEBLIT
332 This is the frame buffer device driver for the Acorn VIDC graphics
333 hardware found in Acorn RISC PCs and other ARM-based machines. If
337 bool "CLPS711X LCD support"
338 depends on (FB = y) && ARM && ARCH_CLPS711X
339 select FB_CFB_FILLRECT
340 select FB_CFB_COPYAREA
341 select FB_CFB_IMAGEBLIT
343 Say Y to enable the Framebuffer driver for the CLPS7111 and
347 bool "SA-1100 LCD support"
348 depends on (FB = y) && ARM && ARCH_SA1100
349 select FB_CFB_FILLRECT
350 select FB_CFB_COPYAREA
351 select FB_CFB_IMAGEBLIT
353 This is a framebuffer device for the SA-1100 LCD Controller.
354 See <http://www.linux-fbdev.org/> for information on framebuffer
357 If you plan to use the LCD display with your SA-1100 system, say
361 tristate "Freescale i.MX LCD support"
362 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
363 select FB_CFB_FILLRECT
364 select FB_CFB_COPYAREA
365 select FB_CFB_IMAGEBLIT
368 tristate "CyberPro 2000/2010/5000 support"
369 depends on FB && PCI && (BROKEN || !SPARC64)
370 select FB_CFB_FILLRECT
371 select FB_CFB_COPYAREA
372 select FB_CFB_IMAGEBLIT
374 This enables support for the Integraphics CyberPro 20x0 and 5000
375 VGA chips used in the Rebel.com Netwinder and other machines.
376 Say Y if you have a NetWinder or a graphics card containing this
377 device, otherwise say N.
379 config FB_CYBER2000_DDC
380 bool "DDC for CyberPro support"
381 depends on FB_CYBER2000
385 Say Y here if you want DDC support for your CyberPro graphics
386 card. This is only I2C bus support, driver does not use EDID.
388 config FB_CYBER2000_I2C
389 bool "CyberPro 2000/2010/5000 I2C support"
390 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
393 Enable support for the I2C video decoder interface on the
394 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
395 on the Netwinder machines for the SAA7111 video capture.
399 depends on (FB = y) && APOLLO
401 select FB_CFB_FILLRECT
402 select FB_CFB_IMAGEBLIT
406 depends on (FB = y) && Q40
408 select FB_CFB_FILLRECT
409 select FB_CFB_COPYAREA
410 select FB_CFB_IMAGEBLIT
413 tristate "Amiga native chipset support"
414 depends on FB && AMIGA
416 This is the frame buffer device driver for the builtin graphics
417 chipset found in Amigas.
419 To compile this driver as a module, choose M here: the
420 module will be called amifb.
423 bool "Amiga OCS chipset support"
426 This enables support for the original Agnus and Denise video chips,
427 found in the Amiga 1000 and most A500's and A2000's. If you intend
428 to run Linux on any of these systems, say Y; otherwise say N.
431 bool "Amiga ECS chipset support"
434 This enables support for the Enhanced Chip Set, found in later
435 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
436 you intend to run Linux on any of these systems, say Y; otherwise
440 bool "Amiga AGA chipset support"
443 This enables support for the Advanced Graphics Architecture (also
444 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
445 and CD32. If you intend to run Linux on any of these systems, say Y;
449 bool "Amiga FrameMaster II/Rainbow II support"
450 depends on (FB = y) && ZORRO
451 select FB_CFB_FILLRECT
452 select FB_CFB_COPYAREA
453 select FB_CFB_IMAGEBLIT
455 This is the frame buffer device driver for the Amiga FrameMaster
456 card from BSC (exhibited 1992 but not shipped as a CBM product).
459 tristate "Arc Monochrome LCD board support"
461 select FB_SYS_FILLRECT
462 select FB_SYS_COPYAREA
463 select FB_SYS_IMAGEBLIT
466 This enables support for the Arc Monochrome LCD board. The board
467 is based on the KS-108 lcd controller and is typically a matrix
468 of 2*n chips. This driver was tested with a 128x64 panel. This
469 driver supports it for use with x86 SBCs through a 16 bit GPIO
470 interface (8 bit data, 8 bit control). If you anticipate using
471 this driver, say Y or M; otherwise say N. You must specify the
472 GPIO IO address to be used for setting control and data.
475 bool "Atari native chipset support"
476 depends on (FB = y) && ATARI
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
481 This is the frame buffer device driver for the builtin graphics
482 chipset found in Ataris.
485 bool "Open Firmware frame buffer device support"
486 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
492 Say Y if you want support with Open Firmware for your graphics
496 bool "Apple \"control\" display support"
497 depends on (FB = y) && PPC_PMAC && PPC32
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
503 This driver supports a frame buffer for the graphics adapter in the
504 Power Macintosh 7300 and others.
507 bool "Apple \"platinum\" display support"
508 depends on (FB = y) && PPC_PMAC && PPC32
509 select FB_CFB_FILLRECT
510 select FB_CFB_COPYAREA
511 select FB_CFB_IMAGEBLIT
514 This driver supports a frame buffer for the "platinum" graphics
515 adapter in some Power Macintoshes.
518 bool "Apple \"valkyrie\" display support"
519 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
520 select FB_CFB_FILLRECT
521 select FB_CFB_COPYAREA
522 select FB_CFB_IMAGEBLIT
525 This driver supports a frame buffer for the "valkyrie" graphics
526 adapter in some Power Macintoshes.
529 bool "Chips 65550 display support"
530 depends on (FB = y) && PPC32 && PCI
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
535 This is the frame buffer device driver for the Chips & Technologies
536 65550 graphics chip in PowerBooks.
539 bool "Asiliant (Chips) 69000 display support"
540 depends on (FB = y) && PCI
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
545 This is the frame buffer device driver for the Asiliant 69030 chipset
548 bool "IMS Twin Turbo display support"
549 depends on (FB = y) && PCI
550 select FB_CFB_IMAGEBLIT
551 select FB_MACMODES if PPC
553 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
554 many Macintosh and compatible computers.
557 tristate "VGA 16-color graphics support"
558 depends on FB && (X86 || PPC)
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
563 select FONT_8x16 if FRAMEBUFFER_CONSOLE
565 This is the frame buffer device driver for VGA 16 color graphic
566 cards. Say Y if you have such a card.
568 To compile this driver as a module, choose M here: the
569 module will be called vga16fb.
571 config FB_BF54X_LQ043
572 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
573 depends on FB && (BF54x) && !BF542
574 select FB_CFB_FILLRECT
575 select FB_CFB_COPYAREA
576 select FB_CFB_IMAGEBLIT
578 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
580 config FB_BFIN_T350MCQB
581 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
582 depends on FB && BLACKFIN
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
588 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
589 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
590 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
592 config FB_BFIN_LQ035Q1
593 tristate "SHARP LQ035Q1DH02 TFT LCD"
594 depends on FB && BLACKFIN && SPI
595 select FB_CFB_FILLRECT
596 select FB_CFB_COPYAREA
597 select FB_CFB_IMAGEBLIT
600 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
601 the Blackfin Landscape LCD EZ-Extender Card.
602 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
603 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
605 To compile this driver as a module, choose M here: the
606 module will be called bfin-lq035q1-fb.
608 config FB_BF537_LQ035
609 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
610 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
611 select FB_CFB_FILLRECT
612 select FB_CFB_COPYAREA
613 select FB_CFB_IMAGEBLIT
616 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
619 To compile this driver as a module, choose M here: the
620 module will be called bf537-lq035.
623 tristate "Blackfin ADV7393 Video encoder"
624 depends on FB && BLACKFIN
626 select FB_CFB_FILLRECT
627 select FB_CFB_COPYAREA
628 select FB_CFB_IMAGEBLIT
630 This is the framebuffer device for a ADV7393 video encoder
631 attached to a Blackfin on the PPI port.
632 If your Blackfin board has a ADV7393 select Y.
634 To compile this driver as a module, choose M here: the
635 module will be called bfin_adv7393fb.
638 prompt "Video mode support"
639 depends on FB_BFIN_7393
649 bool 'NTSC 640x480 (Experimental)'
652 bool 'PAL 640x480 (Experimental)'
655 bool 'NTSC 720x480 YCbCR input'
658 bool 'PAL 720x576 YCbCR input'
663 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
664 depends on (FB_BFIN_7393)
665 default ADV7393_1XMEM
675 tristate "HP STI frame buffer device support"
676 depends on FB && PARISC
677 select FB_CFB_FILLRECT
678 select FB_CFB_COPYAREA
679 select FB_CFB_IMAGEBLIT
684 STI refers to the HP "Standard Text Interface" which is a set of
685 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
686 Enabling this option will implement the linux framebuffer device
687 using calls to the STI BIOS routines for initialisation.
689 If you enable this option, you will get a planar framebuffer device
690 /dev/fb which will work on the most common HP graphic cards of the
691 NGLE family, including the artist chips (in the 7xx and Bxxx series),
692 HCRX, HCRX24, CRX, CRX24 and VisEG series.
694 It is safe to enable this option, so you should probably say "Y".
697 bool "Generic Macintosh display support"
698 depends on (FB = y) && MAC
699 select FB_CFB_FILLRECT
700 select FB_CFB_COPYAREA
701 select FB_CFB_IMAGEBLIT
706 depends on (FB = y) && DIO
707 select FB_CFB_IMAGEBLIT
711 tristate "TGA/SFB+ framebuffer support"
712 depends on FB && (ALPHA || TC)
713 select FB_CFB_FILLRECT
714 select FB_CFB_COPYAREA
715 select FB_CFB_IMAGEBLIT
718 This is the frame buffer device driver for generic TGA and SFB+
719 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
720 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
721 TURBOchannel cards, also known as PMAGD-A, -B and -C.
723 Due to hardware limitations ZLX-E2 and E3 cards are not supported
724 for DECstation 5000/200 systems. Additionally due to firmware
725 limitations these cards may cause troubles with booting DECstation
726 5000/240 and /260 systems, but are fully supported under Linux if
727 you manage to get it going. ;-)
729 Say Y if you have one of those.
732 tristate "Userspace VESA VGA graphics support"
733 depends on FB && CONNECTOR
734 select FB_CFB_FILLRECT
735 select FB_CFB_COPYAREA
736 select FB_CFB_IMAGEBLIT
737 select FB_MODE_HELPERS
739 This is the frame buffer driver for generic VBE 2.0 compliant
740 graphic cards. It can also take advantage of VBE 3.0 features,
741 such as refresh rate adjustment.
743 This driver generally provides more features than vesafb but
744 requires a userspace helper application called 'v86d'. See
745 <file:Documentation/fb/uvesafb.txt> for more information.
750 bool "VESA VGA graphics support"
751 depends on (FB = y) && X86
752 select FB_CFB_FILLRECT
753 select FB_CFB_COPYAREA
754 select FB_CFB_IMAGEBLIT
755 select FB_BOOT_VESA_SUPPORT
757 This is the frame buffer device driver for generic VESA 2.0
758 compliant graphic cards. The older VESA 1.2 cards are not supported.
759 You will get a boot time penguin logo at no additional cost. Please
760 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
763 bool "EFI-based Framebuffer Support"
764 depends on (FB = y) && X86 && EFI
765 select FB_CFB_FILLRECT
766 select FB_CFB_COPYAREA
767 select FB_CFB_IMAGEBLIT
769 This is the EFI frame buffer device driver. If the firmware on
770 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
771 using the EFI framebuffer as your console.
774 tristate "N411 Apollo/Hecuba devkit support"
775 depends on FB && X86 && MMU
776 select FB_SYS_FILLRECT
777 select FB_SYS_COPYAREA
778 select FB_SYS_IMAGEBLIT
780 select FB_DEFERRED_IO
783 This enables support for the Apollo display controller in its
784 Hecuba form using the n411 devkit.
787 tristate "Hercules mono graphics support"
790 Say Y here if you have a Hercules mono graphics card.
792 To compile this driver as a module, choose M here: the
793 module will be called hgafb.
795 As this card technology is at least 25 years old,
796 most people will answer N here.
799 tristate "SGI Visual Workstation framebuffer support"
800 depends on FB && X86_VISWS
801 select FB_CFB_FILLRECT
802 select FB_CFB_COPYAREA
803 select FB_CFB_IMAGEBLIT
805 SGI Visual Workstation support for framebuffer graphics.
808 bool "SGI Graphics Backend frame buffer support"
809 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
810 select FB_CFB_FILLRECT
811 select FB_CFB_COPYAREA
812 select FB_CFB_IMAGEBLIT
814 This is the frame buffer device driver for SGI Graphics Backend.
815 This chip is used in SGI O2 and Visual Workstation 320/540.
818 int "Video memory size in MB"
822 This is the amount of memory reserved for the framebuffer,
823 which can be any value between 1MB and 8MB.
826 bool "SBUS and UPA framebuffers"
827 depends on (FB = y) && SPARC
829 Say Y if you want support for SBUS or UPA based frame buffer device.
833 depends on (FB = y) && (SPARC && FB_SBUS)
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 This is the frame buffer device driver for the BWtwo frame buffer.
841 bool "CGthree support"
842 depends on (FB = y) && (SPARC && FB_SBUS)
843 select FB_CFB_FILLRECT
844 select FB_CFB_COPYAREA
845 select FB_CFB_IMAGEBLIT
847 This is the frame buffer device driver for the CGthree frame buffer.
850 bool "CGsix (GX,TurboGX) support"
851 depends on (FB = y) && (SPARC && FB_SBUS)
852 select FB_CFB_COPYAREA
853 select FB_CFB_IMAGEBLIT
855 This is the frame buffer device driver for the CGsix (GX, TurboGX)
859 bool "Creator/Creator3D/Elite3D support"
860 depends on FB_SBUS && SPARC64
861 select FB_CFB_COPYAREA
862 select FB_CFB_IMAGEBLIT
864 This is the frame buffer device driver for the Creator, Creator3D,
865 and Elite3D graphics boards.
868 bool "TCX (SS4/SS5 only) support"
870 select FB_CFB_FILLRECT
871 select FB_CFB_COPYAREA
872 select FB_CFB_IMAGEBLIT
874 This is the frame buffer device driver for the TCX 24/8bit frame
878 bool "CGfourteen (SX) support"
880 select FB_CFB_FILLRECT
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
884 This is the frame buffer device driver for the CGfourteen frame
885 buffer on Desktop SPARCsystems with the SX graphics option.
888 bool "P9100 (Sparcbook 3 only) support"
890 select FB_CFB_FILLRECT
891 select FB_CFB_COPYAREA
892 select FB_CFB_IMAGEBLIT
894 This is the frame buffer device driver for the P9100 card
895 supported on Sparcbook 3 machines.
898 bool "Leo (ZX) support"
900 select FB_CFB_FILLRECT
901 select FB_CFB_COPYAREA
902 select FB_CFB_IMAGEBLIT
904 This is the frame buffer device driver for the SBUS-based Sun ZX
905 (leo) frame buffer cards.
908 bool "IGA 168x display support"
909 depends on (FB = y) && SPARC32
910 select FB_CFB_FILLRECT
911 select FB_CFB_COPYAREA
912 select FB_CFB_IMAGEBLIT
914 This is the framebuffer device for the INTERGRAPHICS 1680 and
915 successor frame buffer cards.
918 bool "Sun XVR-500 3DLABS Wildcat support"
919 depends on (FB = y) && PCI && SPARC64
920 select FB_CFB_FILLRECT
921 select FB_CFB_COPYAREA
922 select FB_CFB_IMAGEBLIT
924 This is the framebuffer device for the Sun XVR-500 and similar
925 graphics cards based upon the 3DLABS Wildcat chipset. The driver
926 only works on sparc64 systems where the system firmware has
927 mostly initialized the card already. It is treated as a
928 completely dumb framebuffer device.
931 bool "Sun XVR-2500 3DLABS Wildcat support"
932 depends on (FB = y) && PCI && SPARC64
933 select FB_CFB_FILLRECT
934 select FB_CFB_COPYAREA
935 select FB_CFB_IMAGEBLIT
937 This is the framebuffer device for the Sun XVR-2500 and similar
938 graphics cards based upon the 3DLABS Wildcat chipset. The driver
939 only works on sparc64 systems where the system firmware has
940 mostly initialized the card already. It is treated as a
941 completely dumb framebuffer device.
944 bool "Sun XVR-1000 support"
945 depends on (FB = y) && SPARC64
946 select FB_CFB_FILLRECT
947 select FB_CFB_COPYAREA
948 select FB_CFB_IMAGEBLIT
950 This is the framebuffer device for the Sun XVR-1000 and similar
951 graphics cards. The driver only works on sparc64 systems where
952 the system firmware has mostly initialized the card already. It
953 is treated as a completely dumb framebuffer device.
956 tristate "NEC PowerVR 2 display support"
957 depends on FB && SH_DREAMCAST
958 select FB_CFB_FILLRECT
959 select FB_CFB_COPYAREA
960 select FB_CFB_IMAGEBLIT
962 Say Y here if you have a PowerVR 2 card in your box. If you plan to
963 run linux on your Dreamcast, you will have to say Y here.
964 This driver may or may not work on other PowerVR 2 cards, but is
965 totally untested. Use at your own risk. If unsure, say N.
967 To compile this driver as a module, choose M here: the
968 module will be called pvr2fb.
970 You can pass several parameters to the driver at boot time or at
971 module load time. The parameters look like "video=pvr2:XXX", where
972 the meaning of XXX can be found at the end of the main source file
973 (<file:drivers/video/pvr2fb.c>). Please see the file
974 <file:Documentation/fb/pvr2fb.txt>.
977 bool "Epson 1355 framebuffer support"
978 depends on (FB = y) && ARCH_CEIVA
979 select FB_CFB_FILLRECT
980 select FB_CFB_COPYAREA
981 select FB_CFB_IMAGEBLIT
983 Build in support for the SED1355 Epson Research Embedded RAMDAC
984 LCD/CRT Controller (since redesignated as the S1D13505) as a
985 framebuffer. Product specs at
986 <http://vdc.epson.com/>.
989 tristate "Epson S1D13XXX framebuffer support"
991 select FB_CFB_FILLRECT
992 select FB_CFB_COPYAREA
993 select FB_CFB_IMAGEBLIT
995 Support for S1D13XXX framebuffer device family (currently only
996 working with S1D13806). Product specs at
997 <http://vdc.epson.com/>
1000 tristate "AT91/AT32 LCD Controller support"
1001 depends on FB && HAVE_FB_ATMEL
1002 select FB_CFB_FILLRECT
1003 select FB_CFB_COPYAREA
1004 select FB_CFB_IMAGEBLIT
1006 This enables support for the AT91/AT32 LCD Controller.
1009 bool "Frame Buffer in internal SRAM"
1010 depends on FB_ATMEL && ARCH_AT91SAM9261
1012 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1013 to let frame buffer in external SDRAM.
1016 bool "Use a STN display with AT91/AT32 LCD Controller"
1017 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1020 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1021 Controller. Say N if you want to connect a TFT.
1026 tristate "nVidia Framebuffer Support"
1027 depends on FB && PCI
1028 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1029 select FB_MODE_HELPERS
1030 select FB_CFB_FILLRECT
1031 select FB_CFB_COPYAREA
1032 select FB_CFB_IMAGEBLIT
1036 This driver supports graphics boards with the nVidia chips, TNT
1037 and newer. For very old chipsets, such as the RIVA128, then use
1039 Say Y if you have such a graphics board.
1041 To compile this driver as a module, choose M here: the
1042 module will be called nvidiafb.
1044 config FB_NVIDIA_I2C
1045 bool "Enable DDC Support"
1046 depends on FB_NVIDIA
1049 This enables I2C support for nVidia Chipsets. This is used
1050 only for getting EDID information from the attached display
1051 allowing for robust video mode handling and switching.
1053 Because fbdev-2.6 requires that drivers must be able to
1054 independently validate video mode parameters, you should say Y
1057 config FB_NVIDIA_DEBUG
1058 bool "Lots of debug output"
1059 depends on FB_NVIDIA
1062 Say Y here if you want the nVidia driver to output all sorts
1063 of debugging information to provide to the maintainer when
1064 something goes wrong.
1066 config FB_NVIDIA_BACKLIGHT
1067 bool "Support for backlight control"
1068 depends on FB_NVIDIA
1071 Say Y here if you want to control the backlight of your display.
1074 tristate "nVidia Riva support"
1075 depends on FB && PCI
1076 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1077 select FB_MODE_HELPERS
1078 select FB_CFB_FILLRECT
1079 select FB_CFB_COPYAREA
1080 select FB_CFB_IMAGEBLIT
1084 This driver supports graphics boards with the nVidia Riva/Geforce
1086 Say Y if you have such a graphics board.
1088 To compile this driver as a module, choose M here: the
1089 module will be called rivafb.
1092 bool "Enable DDC Support"
1096 This enables I2C support for nVidia Chipsets. This is used
1097 only for getting EDID information from the attached display
1098 allowing for robust video mode handling and switching.
1100 Because fbdev-2.6 requires that drivers must be able to
1101 independently validate video mode parameters, you should say Y
1104 config FB_RIVA_DEBUG
1105 bool "Lots of debug output"
1109 Say Y here if you want the Riva driver to output all sorts
1110 of debugging information to provide to the maintainer when
1111 something goes wrong.
1113 config FB_RIVA_BACKLIGHT
1114 bool "Support for backlight control"
1118 Say Y here if you want to control the backlight of your display.
1121 tristate "Intel 810/815 support (EXPERIMENTAL)"
1122 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1123 select FB_MODE_HELPERS
1124 select FB_CFB_FILLRECT
1125 select FB_CFB_COPYAREA
1126 select FB_CFB_IMAGEBLIT
1129 This driver supports the on-board graphics built in to the Intel 810
1130 and 815 chipsets. Say Y if you have and plan to use such a board.
1132 To compile this driver as a module, choose M here: the
1133 module will be called i810fb.
1135 For more information, please read
1136 <file:Documentation/fb/intel810.txt>
1139 bool "use VESA Generalized Timing Formula"
1142 If you say Y, then the VESA standard, Generalized Timing Formula
1143 or GTF, will be used to calculate the required video timing values
1144 per video mode. Since the GTF allows nondiscrete timings
1145 (nondiscrete being a range of values as opposed to discrete being a
1146 set of values), you'll be able to use any combination of horizontal
1147 and vertical resolutions, and vertical refresh rates without having
1148 to specify your own timing parameters. This is especially useful
1149 to maximize the performance of an aging display, or if you just
1150 have a display with nonstandard dimensions. A VESA compliant
1151 monitor is recommended, but can still work with non-compliant ones.
1152 If you need or want this, then select this option. The timings may
1153 not be compliant with Intel's recommended values. Use at your own
1156 If you say N, the driver will revert to discrete video timings
1157 using a set recommended by Intel in their documentation.
1162 bool "Enable DDC Support"
1163 depends on FB_I810 && FB_I810_GTF
1168 tristate "Intel LE80578 (Vermilion) support"
1169 depends on FB && PCI && X86
1170 select FB_MODE_HELPERS
1171 select FB_CFB_FILLRECT
1172 select FB_CFB_COPYAREA
1173 select FB_CFB_IMAGEBLIT
1175 This driver supports the LE80578 (Vermilion Range) chipset
1177 config FB_CARILLO_RANCH
1178 tristate "Intel Carillo Ranch support"
1179 depends on FB_LE80578 && FB && PCI && X86
1181 This driver supports the LE80578 (Carillo Ranch) board
1184 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1185 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1186 select FB_MODE_HELPERS
1187 select FB_CFB_FILLRECT
1188 select FB_CFB_COPYAREA
1189 select FB_CFB_IMAGEBLIT
1190 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1191 depends on !DRM_I915
1193 This driver supports the on-board graphics built in to the Intel
1194 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1195 Say Y if you have and plan to use such a board.
1197 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1199 To compile this driver as a module, choose M here: the
1200 module will be called intelfb.
1202 For more information, please read <file:Documentation/fb/intelfb.txt>
1204 config FB_INTEL_DEBUG
1205 bool "Intel driver Debug Messages"
1208 Say Y here if you want the Intel driver to output all sorts
1209 of debugging information to provide to the maintainer when
1210 something goes wrong.
1213 bool "DDC/I2C for Intel framebuffer support"
1218 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1221 tristate "Matrox acceleration"
1222 depends on FB && PCI
1223 select FB_CFB_FILLRECT
1224 select FB_CFB_COPYAREA
1225 select FB_CFB_IMAGEBLIT
1226 select FB_TILEBLITTING
1227 select FB_MACMODES if PPC_PMAC
1229 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1230 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1231 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1232 Matrox G400, G450 or G550 card in your box.
1234 To compile this driver as a module, choose M here: the
1235 module will be called matroxfb.
1237 You can pass several parameters to the driver at boot time or at
1238 module load time. The parameters look like "video=matroxfb:XXX", and
1239 are described in <file:Documentation/fb/matroxfb.txt>.
1241 config FB_MATROX_MILLENIUM
1242 bool "Millennium I/II support"
1243 depends on FB_MATROX
1245 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1246 video card. If you select "Advanced lowlevel driver options" below,
1247 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1248 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1249 also use font widths different from 8.
1251 config FB_MATROX_MYSTIQUE
1252 bool "Mystique support"
1253 depends on FB_MATROX
1255 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1256 video card. If you select "Advanced lowlevel driver options" below,
1257 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1258 packed pixel and 32 bpp packed pixel. You can also use font widths
1262 bool "G100/G200/G400/G450/G550 support"
1263 depends on FB_MATROX
1265 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1266 video card. If you select "Advanced lowlevel driver options", you
1267 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1268 pixel and 32 bpp packed pixel. You can also use font widths
1271 If you need support for G400 secondary head, you must say Y to
1272 "Matrox I2C support" and "G400 second head support" right below.
1273 G450/G550 secondary head and digital output are supported without
1276 The driver starts in monitor mode. You must use the matroxset tool
1277 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1278 swap primary and secondary head outputs, or to change output mode.
1279 Secondary head driver always start in 640x480 resolution and you
1280 must use fbset to change it.
1282 Do not forget that second head supports only 16 and 32 bpp
1283 packed pixels, so it is a good idea to compile them into the kernel
1284 too. You can use only some font widths, as the driver uses generic
1285 painting procedures (the secondary head does not use acceleration
1288 G450/G550 hardware can display TV picture only from secondary CRTC,
1289 and it performs no scaling, so picture must have 525 or 625 lines.
1291 config FB_MATROX_I2C
1292 tristate "Matrox I2C support"
1293 depends on FB_MATROX
1296 This drivers creates I2C buses which are needed for accessing the
1297 DDC (I2C) bus present on all Matroxes, an I2C bus which
1298 interconnects Matrox optional devices, like MGA-TVO on G200 and
1299 G400, and the secondary head DDC bus, present on G400 only.
1301 You can say Y or M here if you want to experiment with monitor
1302 detection code. You must say Y or M here if you want to use either
1303 second head of G400 or MGA-TVO on G200 or G400.
1305 If you compile it as module, it will create a module named
1308 config FB_MATROX_MAVEN
1309 tristate "G400 second head support"
1310 depends on FB_MATROX_G && FB_MATROX_I2C
1312 WARNING !!! This support does not work with G450 !!!
1314 Say Y or M here if you want to use a secondary head (meaning two
1315 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1316 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1317 secondary head output is blanked while you are in X. With XFree
1318 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1319 the fbdev driver on first head and the fbdev driver on second head.
1321 If you compile it as module, two modules are created,
1322 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1323 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1324 also load i2c-matroxfb to get it to run.
1326 The driver starts in monitor mode and you must use the matroxset
1328 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1329 PAL or NTSC or to swap primary and secondary head outputs.
1330 Secondary head driver also always start in 640x480 resolution, you
1331 must use fbset to change it.
1333 Also do not forget that second head supports only 16 and 32 bpp
1334 packed pixels, so it is a good idea to compile them into the kernel
1335 too. You can use only some font widths, as the driver uses generic
1336 painting procedures (the secondary head does not use acceleration
1340 tristate "ATI Radeon display support"
1341 depends on FB && PCI
1342 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1343 select FB_MODE_HELPERS
1344 select FB_CFB_FILLRECT
1345 select FB_CFB_COPYAREA
1346 select FB_CFB_IMAGEBLIT
1347 select FB_MACMODES if PPC_OF
1349 Choose this option if you want to use an ATI Radeon graphics card as
1350 a framebuffer device. There are both PCI and AGP versions. You
1351 don't need to choose this to run the Radeon in plain VGA mode.
1353 There is a product page at
1354 http://products.amd.com/en-us/GraphicCardResult.aspx
1356 config FB_RADEON_I2C
1357 bool "DDC/I2C for ATI Radeon support"
1358 depends on FB_RADEON
1362 Say Y here if you want DDC/I2C support for your Radeon board.
1364 config FB_RADEON_BACKLIGHT
1365 bool "Support for backlight control"
1366 depends on FB_RADEON
1369 Say Y here if you want to control the backlight of your display.
1371 config FB_RADEON_DEBUG
1372 bool "Lots of debug output from Radeon driver"
1373 depends on FB_RADEON
1376 Say Y here if you want the Radeon driver to output all sorts
1377 of debugging information to provide to the maintainer when
1378 something goes wrong.
1381 tristate "ATI Rage128 display support"
1382 depends on FB && PCI
1383 select FB_CFB_FILLRECT
1384 select FB_CFB_COPYAREA
1385 select FB_CFB_IMAGEBLIT
1386 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1387 select FB_MACMODES if PPC_PMAC
1389 This driver supports graphics boards with the ATI Rage128 chips.
1390 Say Y if you have such a graphics board and read
1391 <file:Documentation/fb/aty128fb.txt>.
1393 To compile this driver as a module, choose M here: the
1394 module will be called aty128fb.
1396 config FB_ATY128_BACKLIGHT
1397 bool "Support for backlight control"
1398 depends on FB_ATY128
1401 Say Y here if you want to control the backlight of your display.
1404 tristate "ATI Mach64 display support" if PCI || ATARI
1405 depends on FB && !SPARC32
1406 select FB_CFB_FILLRECT
1407 select FB_CFB_COPYAREA
1408 select FB_CFB_IMAGEBLIT
1409 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1410 select FB_MACMODES if PPC
1412 This driver supports graphics boards with the ATI Mach64 chips.
1413 Say Y if you have such a graphics board.
1415 To compile this driver as a module, choose M here: the
1416 module will be called atyfb.
1419 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1420 depends on PCI && FB_ATY
1421 default y if SPARC64 && PCI
1423 Say Y here to support use of ATI's 64-bit Rage boards (or other
1424 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1425 framebuffer device. The ATI product support page for these boards
1426 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1428 config FB_ATY_GENERIC_LCD
1429 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1430 depends on FB_ATY_CT
1432 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1433 Rage XC, or Rage XL chipset.
1436 bool "Mach64 GX support" if PCI
1440 Say Y here to support use of the ATI Mach64 Graphics Expression
1441 board (or other boards based on the Mach64 GX chipset) as a
1442 framebuffer device. The ATI product support page for these boards
1444 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1446 config FB_ATY_BACKLIGHT
1447 bool "Support for backlight control"
1451 Say Y here if you want to control the backlight of your display.
1454 tristate "S3 Trio/Virge support"
1455 depends on FB && PCI
1456 select FB_CFB_FILLRECT
1457 select FB_CFB_COPYAREA
1458 select FB_CFB_IMAGEBLIT
1459 select FB_TILEBLITTING
1462 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1464 Driver for graphics boards with S3 Trio / S3 Virge chip.
1467 tristate "S3 Savage support"
1468 depends on FB && PCI && EXPERIMENTAL
1469 select FB_MODE_HELPERS
1470 select FB_CFB_FILLRECT
1471 select FB_CFB_COPYAREA
1472 select FB_CFB_IMAGEBLIT
1475 This driver supports notebooks and computers with S3 Savage PCI/AGP
1478 Say Y if you have such a graphics card.
1480 To compile this driver as a module, choose M here; the module
1481 will be called savagefb.
1483 config FB_SAVAGE_I2C
1484 bool "Enable DDC2 Support"
1485 depends on FB_SAVAGE
1488 This enables I2C support for S3 Savage Chipsets. This is used
1489 only for getting EDID information from the attached display
1490 allowing for robust video mode handling and switching.
1492 Because fbdev-2.6 requires that drivers must be able to
1493 independently validate video mode parameters, you should say Y
1496 config FB_SAVAGE_ACCEL
1497 bool "Enable Console Acceleration"
1498 depends on FB_SAVAGE
1501 This option will compile in console acceleration support. If
1502 the resulting framebuffer console has bothersome glitches, then
1506 tristate "SiS/XGI display support"
1507 depends on FB && PCI
1508 select FB_CFB_FILLRECT
1509 select FB_CFB_COPYAREA
1510 select FB_CFB_IMAGEBLIT
1511 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1513 This is the frame buffer device driver for the SiS 300, 315, 330
1514 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1515 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1517 To compile this driver as a module, choose M here; the module
1518 will be called sisfb.
1521 bool "SiS 300 series support"
1524 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1527 bool "SiS 315/330/340 series and XGI support"
1530 Say Y here to support use of the SiS 315, 330 and 340 series
1531 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1532 as XGI V3XT, V5, V8 and Z7.
1535 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1536 depends on FB && PCI && X86
1537 select FB_CFB_FILLRECT
1538 select FB_CFB_COPYAREA
1539 select FB_CFB_IMAGEBLIT
1544 This is the frame buffer device driver for Graphics chips of VIA
1545 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1546 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1548 Say Y if you have a VIA UniChrome graphics board.
1550 To compile this driver as a module, choose M here: the
1551 module will be called viafb.
1555 config FB_VIA_DIRECT_PROCFS
1556 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1560 Allow direct hardware access to some output registers via procfs.
1561 This is dangerous but may provide the only chance to get the
1562 correct output device configuration.
1563 Its use is strongly discouraged.
1565 config FB_VIA_X_COMPATIBILITY
1566 bool "X server compatibility"
1570 This option reduces the functionality (power saving, ...) of the
1571 framebuffer to avoid negative impact on the OpenChrome X server.
1572 If you use any X server other than fbdev you should enable this
1573 otherwise it should be safe to disable it and allow using all
1579 tristate "NeoMagic display support"
1580 depends on FB && PCI
1581 select FB_MODE_HELPERS
1582 select FB_CFB_FILLRECT
1583 select FB_CFB_COPYAREA
1584 select FB_CFB_IMAGEBLIT
1587 This driver supports notebooks with NeoMagic PCI chips.
1588 Say Y if you have such a graphics card.
1590 To compile this driver as a module, choose M here: the
1591 module will be called neofb.
1594 tristate "IMG Kyro support"
1595 depends on FB && PCI
1596 select FB_CFB_FILLRECT
1597 select FB_CFB_COPYAREA
1598 select FB_CFB_IMAGEBLIT
1600 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1603 To compile this driver as a module, choose M here: the
1604 module will be called kyrofb.
1607 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1608 depends on FB && PCI
1609 select FB_CFB_IMAGEBLIT
1610 select FB_CFB_FILLRECT
1611 select FB_CFB_COPYAREA
1612 select FB_MODE_HELPERS
1614 This driver supports graphics boards with the 3Dfx Banshee,
1615 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1616 such a graphics board.
1618 To compile this driver as a module, choose M here: the
1619 module will be called tdfxfb.
1621 config FB_3DFX_ACCEL
1622 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1623 depends on FB_3DFX && EXPERIMENTAL
1625 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1626 device driver with acceleration functions.
1629 bool "Enable DDC/I2C support"
1630 depends on FB_3DFX && EXPERIMENTAL
1634 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1637 tristate "3Dfx Voodoo Graphics (sst1) support"
1638 depends on FB && PCI
1639 select FB_CFB_FILLRECT
1640 select FB_CFB_COPYAREA
1641 select FB_CFB_IMAGEBLIT
1643 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1644 Voodoo2 (cvg) based graphics card.
1646 To compile this driver as a module, choose M here: the
1647 module will be called sstfb.
1649 WARNING: Do not use any application that uses the 3D engine
1650 (namely glide) while using this driver.
1651 Please read the <file:Documentation/fb/sstfb.txt> for supported
1652 options and other important info support.
1655 tristate "VIA VT8623 support"
1656 depends on FB && PCI
1657 select FB_CFB_FILLRECT
1658 select FB_CFB_COPYAREA
1659 select FB_CFB_IMAGEBLIT
1660 select FB_TILEBLITTING
1663 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1665 Driver for CastleRock integrated graphics core in the
1666 VIA VT8623 [Apollo CLE266] chipset.
1669 tristate "Trident/CyberXXX/CyberBlade support"
1670 depends on FB && PCI
1671 select FB_CFB_FILLRECT
1672 select FB_CFB_COPYAREA
1673 select FB_CFB_IMAGEBLIT
1675 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1676 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1678 There are also integrated versions of these chips called CyberXXXX,
1679 CyberImage or CyberBlade. These chips are mostly found in laptops
1680 but also on some motherboards including early VIA EPIA motherboards.
1681 For more information, read <file:Documentation/fb/tridentfb.txt>
1683 Say Y if you have such a graphics board.
1685 To compile this driver as a module, choose M here: the
1686 module will be called tridentfb.
1689 tristate "ARK 2000PV support"
1690 depends on FB && PCI
1691 select FB_CFB_FILLRECT
1692 select FB_CFB_COPYAREA
1693 select FB_CFB_IMAGEBLIT
1694 select FB_TILEBLITTING
1697 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1699 Driver for PCI graphics boards with ARK 2000PV chip
1700 and ICS 5342 RAMDAC.
1703 tristate "Permedia3 support (EXPERIMENTAL)"
1704 depends on FB && PCI && EXPERIMENTAL
1705 select FB_CFB_FILLRECT
1706 select FB_CFB_COPYAREA
1707 select FB_CFB_IMAGEBLIT
1709 This is the frame buffer device driver for the 3DLabs Permedia3
1710 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1711 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1712 and maybe other boards.
1715 tristate "Fujitsu carmine frame buffer support"
1716 depends on FB && PCI
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 Fujitsu Carmine chip.
1722 The driver provides two independent frame buffer devices.
1725 depends on FB_CARMINE
1726 prompt "DRAM timing"
1727 default FB_CARMINE_DRAM_EVAL
1729 config FB_CARMINE_DRAM_EVAL
1730 bool "Eval board timings"
1732 Use timings which work on the eval card.
1734 config CARMINE_DRAM_CUSTOM
1735 bool "Custom board timings"
1737 Use custom board timings.
1741 bool "Au1100 LCD Driver"
1742 depends on (FB = y) && MIPS && SOC_AU1100
1743 select FB_CFB_FILLRECT
1744 select FB_CFB_COPYAREA
1745 select FB_CFB_IMAGEBLIT
1747 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1748 various panels and CRTs by passing in kernel cmd line option
1749 au1100fb:panel=<name>.
1752 bool "Au1200 LCD Driver"
1753 depends on (FB = y) && MIPS && SOC_AU1200
1754 select FB_CFB_FILLRECT
1755 select FB_CFB_COPYAREA
1756 select FB_CFB_IMAGEBLIT
1758 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1759 various panels and CRTs by passing in kernel cmd line option
1760 au1200fb:panel=<name>.
1763 bool "VT8500 LCD Driver"
1764 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1765 select FB_WMT_GE_ROPS
1766 select FB_SYS_IMAGEBLIT
1768 This is the framebuffer driver for VIA VT8500 integrated LCD
1772 bool "WM8505 frame buffer support"
1773 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1774 select FB_WMT_GE_ROPS
1775 select FB_SYS_IMAGEBLIT
1777 This is the framebuffer driver for WonderMedia WM8505
1778 integrated LCD controller.
1780 source "drivers/video/geode/Kconfig"
1783 tristate "HD64461 Frame Buffer support"
1784 depends on FB && HD64461
1785 select FB_CFB_FILLRECT
1786 select FB_CFB_COPYAREA
1787 select FB_CFB_IMAGEBLIT
1789 This is the frame buffer device driver for the Hitachi HD64461 LCD
1793 bool "PMAG-AA TURBOchannel framebuffer support"
1794 depends on (FB = y) && TC
1795 select FB_CFB_FILLRECT
1796 select FB_CFB_COPYAREA
1797 select FB_CFB_IMAGEBLIT
1799 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1800 used mainly in the MIPS-based DECstation series.
1803 tristate "PMAG-BA TURBOchannel framebuffer support"
1805 select FB_CFB_FILLRECT
1806 select FB_CFB_COPYAREA
1807 select FB_CFB_IMAGEBLIT
1809 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1810 used mainly in the MIPS-based DECstation series.
1813 tristate "PMAGB-B TURBOchannel framebuffer support"
1815 select FB_CFB_FILLRECT
1816 select FB_CFB_COPYAREA
1817 select FB_CFB_IMAGEBLIT
1819 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1820 in the MIPS-based DECstation series. The card is currently only
1821 supported in 1280x1024x8 mode.
1824 bool "Maxine (Personal DECstation) onboard framebuffer support"
1825 depends on (FB = y) && MACH_DECSTATION
1826 select FB_CFB_FILLRECT
1827 select FB_CFB_COPYAREA
1828 select FB_CFB_IMAGEBLIT
1830 Support for the onboard framebuffer (1024x768x8) in the Personal
1831 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1835 bool "G364 frame buffer support"
1836 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1837 select FB_CFB_FILLRECT
1838 select FB_CFB_COPYAREA
1839 select FB_CFB_IMAGEBLIT
1841 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1842 Olivetti M700-10 systems.
1845 bool "Motorola 68328 native frame buffer support"
1846 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1847 select FB_CFB_FILLRECT
1848 select FB_CFB_COPYAREA
1849 select FB_CFB_IMAGEBLIT
1851 Say Y here if you want to support the built-in frame buffer of
1852 the Motorola 68328 CPU family.
1855 tristate "PXA168/910 LCD framebuffer support"
1856 depends on FB && (CPU_PXA168 || CPU_PXA910)
1857 select FB_CFB_FILLRECT
1858 select FB_CFB_COPYAREA
1859 select FB_CFB_IMAGEBLIT
1861 Frame buffer driver for the built-in LCD controller in the Marvell
1865 tristate "PXA LCD framebuffer support"
1866 depends on FB && ARCH_PXA
1867 select FB_CFB_FILLRECT
1868 select FB_CFB_COPYAREA
1869 select FB_CFB_IMAGEBLIT
1871 Frame buffer driver for the built-in LCD controller in the Intel
1874 This driver is also available as a module ( = code which can be
1875 inserted and removed from the running kernel whenever you want). The
1876 module will be called pxafb. If you want to compile it as a module,
1877 say M here and read <file:Documentation/kbuild/modules.txt>.
1881 config FB_PXA_OVERLAY
1882 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1884 depends on FB_PXA && (PXA27x || PXA3xx)
1886 config FB_PXA_SMARTPANEL
1887 bool "PXA Smartpanel LCD support"
1891 config FB_PXA_PARAMETERS
1892 bool "PXA LCD command line parameters"
1896 Enable the use of kernel command line or module parameters
1897 to configure the physical properties of the LCD panel when
1898 using the PXA LCD driver.
1900 This option allows you to override the panel parameters
1901 supplied by the platform in order to support multiple
1902 different models of flatpanel. If you will only be using a
1903 single model of flatpanel then you can safely leave this
1906 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1909 tristate "PXA3xx 2D graphics accelerator driver"
1912 Kernelspace driver for the 2D graphics controller unit (GCU)
1913 found on PXA3xx processors. There is a counterpart driver in the
1914 DirectFB suite, see http://www.directfb.org/
1916 If you compile this as a module, it will be called pxa3xx_gcu.
1919 tristate "2700G LCD framebuffer support"
1920 depends on FB && ARCH_PXA
1921 select FB_CFB_FILLRECT
1922 select FB_CFB_COPYAREA
1923 select FB_CFB_IMAGEBLIT
1925 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1929 bool "Enable debugging info via debugfs"
1930 depends on FB_MBX && DEBUG_FS
1933 Enable this if you want debugging information using the debug
1934 filesystem (debugfs)
1939 tristate "Freescale DIU framebuffer support"
1940 depends on FB && FSL_SOC
1941 select FB_MODE_HELPERS
1942 select FB_CFB_FILLRECT
1943 select FB_CFB_COPYAREA
1944 select FB_CFB_IMAGEBLIT
1945 select PPC_LIB_RHEAP
1947 Framebuffer driver for the Freescale SoC DIU
1950 tristate "W100 frame buffer support"
1951 depends on FB && ARCH_PXA
1952 select FB_CFB_FILLRECT
1953 select FB_CFB_COPYAREA
1954 select FB_CFB_IMAGEBLIT
1956 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1957 It can also drive the w3220 chip found on iPAQ hx4700.
1959 This driver is also available as a module ( = code which can be
1960 inserted and removed from the running kernel whenever you want). The
1961 module will be called w100fb. If you want to compile it as a module,
1962 say M here and read <file:Documentation/kbuild/modules.txt>.
1966 config FB_SH_MOBILE_LCDC
1967 tristate "SuperH Mobile LCDC framebuffer support"
1968 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1969 select FB_SYS_FILLRECT
1970 select FB_SYS_COPYAREA
1971 select FB_SYS_IMAGEBLIT
1973 select FB_DEFERRED_IO
1975 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1977 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1979 config FB_SH_MOBILE_HDMI
1980 tristate "SuperH Mobile HDMI controller support"
1981 depends on FB_SH_MOBILE_LCDC
1982 select FB_MODE_HELPERS
1987 Driver for the on-chip SH-Mobile HDMI controller.
1990 tristate "Toshiba Mobile IO FrameBuffer support"
1991 depends on FB && MFD_CORE
1992 select FB_CFB_FILLRECT
1993 select FB_CFB_COPYAREA
1994 select FB_CFB_IMAGEBLIT
1996 Frame buffer driver for the Toshiba Mobile IO integrated as found
1997 on the Sharp SL-6000 series
1999 This driver is also available as a module ( = code which can be
2000 inserted and removed from the running kernel whenever you want). The
2001 module will be called tmiofb. If you want to compile it as a module,
2002 say M here and read <file:Documentation/kbuild/modules.txt>.
2006 config FB_TMIO_ACCELL
2007 bool "tmiofb acceleration"
2012 tristate "Samsung S3C framebuffer support"
2013 depends on FB && S3C_DEV_FB
2014 select FB_CFB_FILLRECT
2015 select FB_CFB_COPYAREA
2016 select FB_CFB_IMAGEBLIT
2018 Frame buffer driver for the built-in FB controller in the Samsung
2019 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2020 and the S3C64XX series such as the S3C6400 and S3C6410.
2022 These chips all have the same basic framebuffer design with the
2023 actual capabilities depending on the chip. For instance the S3C6400
2024 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2025 currently only have two.
2027 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2029 config FB_S3C_DEBUG_REGWRITE
2030 bool "Debug register writes"
2033 Show all register writes via printk(KERN_DEBUG)
2036 tristate "S3C2410 LCD framebuffer support"
2037 depends on FB && ARCH_S3C2410
2038 select FB_CFB_FILLRECT
2039 select FB_CFB_COPYAREA
2040 select FB_CFB_IMAGEBLIT
2042 Frame buffer driver for the built-in LCD controller in the Samsung
2045 This driver is also available as a module ( = code which can be
2046 inserted and removed from the running kernel whenever you want). The
2047 module will be called s3c2410fb. If you want to compile it as a module,
2048 say M here and read <file:Documentation/kbuild/modules.txt>.
2051 config FB_S3C2410_DEBUG
2052 bool "S3C2410 lcd debug messages"
2053 depends on FB_S3C2410
2055 Turn on debugging messages. Note that you can set/unset at run time
2059 bool "NUC900 LCD framebuffer support"
2060 depends on FB && ARCH_W90X900
2061 select FB_CFB_FILLRECT
2062 select FB_CFB_COPYAREA
2063 select FB_CFB_IMAGEBLIT
2065 Frame buffer driver for the built-in LCD controller in the Nuvoton
2068 config GPM1040A0_320X240
2069 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2070 depends on FB_NUC900
2072 config FB_NUC900_DEBUG
2073 bool "NUC900 lcd debug messages"
2074 depends on FB_NUC900
2076 Turn on debugging messages. Note that you can set/unset at run time
2080 tristate "Silicon Motion SM501 framebuffer support"
2081 depends on FB && MFD_SM501
2082 select FB_CFB_FILLRECT
2083 select FB_CFB_COPYAREA
2084 select FB_CFB_IMAGEBLIT
2086 Frame buffer driver for the CRT and LCD controllers in the Silicon
2089 This driver is also available as a module ( = code which can be
2090 inserted and removed from the running kernel whenever you want). The
2091 module will be called sm501fb. If you want to compile it as a module,
2092 say M here and read <file:Documentation/kbuild/modules.txt>.
2097 tristate "Displaylink USB Framebuffer support"
2098 depends on FB && USB
2099 select FB_MODE_HELPERS
2100 select FB_SYS_FILLRECT
2101 select FB_SYS_COPYAREA
2102 select FB_SYS_IMAGEBLIT
2104 select FB_DEFERRED_IO
2106 This is a kernel framebuffer driver for DisplayLink USB devices.
2107 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2108 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2109 To compile as a module, choose M here: the module name is udlfb.
2111 config FB_PNX4008_DUM
2112 tristate "Display Update Module support on Philips PNX4008 board"
2113 depends on FB && ARCH_PNX4008
2115 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2117 config FB_PNX4008_DUM_RGB
2118 tristate "RGB Framebuffer support on Philips PNX4008 board"
2119 depends on FB_PNX4008_DUM
2120 select FB_CFB_FILLRECT
2121 select FB_CFB_COPYAREA
2122 select FB_CFB_IMAGEBLIT
2124 Say Y here to enable support for PNX4008 RGB Framebuffer
2126 config FB_IBM_GXT4500
2127 tristate "Framebuffer support for IBM GXT4500P adaptor"
2128 depends on FB && PPC
2129 select FB_CFB_FILLRECT
2130 select FB_CFB_COPYAREA
2131 select FB_CFB_IMAGEBLIT
2133 Say Y here to enable support for the IBM GXT4500P display
2134 adaptor, found on some IBM System P (pSeries) machines.
2137 tristate "PS3 GPU framebuffer driver"
2138 depends on FB && PS3_PS3AV
2139 select FB_SYS_FILLRECT
2140 select FB_SYS_COPYAREA
2141 select FB_SYS_IMAGEBLIT
2143 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2145 Include support for the virtual frame buffer in the PS3 platform.
2147 config FB_PS3_DEFAULT_SIZE_M
2148 int "PS3 default frame buffer size (in MiB)"
2152 This is the default size (in MiB) of the virtual frame buffer in
2154 The default value can be overridden on the kernel command line
2155 using the "ps3fb" option (e.g. "ps3fb=9M");
2158 tristate "Xilinx frame buffer support"
2159 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2160 select FB_CFB_FILLRECT
2161 select FB_CFB_COPYAREA
2162 select FB_CFB_IMAGEBLIT
2164 Include support for the Xilinx ML300/ML403 reference design
2165 framebuffer. ML300 carries a 640*480 LCD display on the board,
2166 ML403 uses a standard DB15 VGA connector.
2169 tristate "Cobalt server LCD frame buffer support"
2170 depends on FB && MIPS_COBALT
2173 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2174 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2175 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2176 select FB_CFB_FILLRECT
2177 select FB_CFB_COPYAREA
2178 select FB_CFB_IMAGEBLIT
2180 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2181 (D)STN/TFT LCD Controller.
2182 Supports display resolutions up to 1024x1024 pixel, grayscale and
2183 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2184 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2185 panels <= 320 pixel horizontal resolution.
2188 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2189 depends on FB && ARCH_DAVINCI_DA8XX
2190 select FB_CFB_FILLRECT
2191 select FB_CFB_COPYAREA
2192 select FB_CFB_IMAGEBLIT
2194 This is the frame buffer device driver for the TI LCD controller
2195 found on DA8xx/OMAP-L1xx SoCs.
2199 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2201 select FB_SYS_FILLRECT
2202 select FB_SYS_COPYAREA
2203 select FB_SYS_IMAGEBLIT
2206 This is a `virtual' frame buffer device. It operates on a chunk of
2207 unswappable kernel memory instead of on the memory of a graphics
2208 board. This means you cannot see any output sent to this frame
2209 buffer device, while it does consume precious memory. The main use
2210 of this frame buffer device is testing and debugging the frame
2211 buffer subsystem. Do NOT enable it for normal systems! To protect
2212 the innocent, it has to be enabled explicitly at boot time using the
2213 kernel option `video=vfb:'.
2215 To compile this driver as a module, choose M here: the
2216 module will be called vfb. In order to load it, you must use
2217 the vfb_enable=1 option.
2221 config XEN_FBDEV_FRONTEND
2222 tristate "Xen virtual frame buffer support"
2223 depends on FB && XEN
2224 select FB_SYS_FILLRECT
2225 select FB_SYS_COPYAREA
2226 select FB_SYS_IMAGEBLIT
2228 select FB_DEFERRED_IO
2229 select XEN_XENBUS_FRONTEND
2232 This driver implements the front-end of the Xen virtual
2233 frame buffer driver. It communicates with a back-end
2237 tristate "E-Ink Metronome/8track controller support"
2239 select FB_SYS_FILLRECT
2240 select FB_SYS_COPYAREA
2241 select FB_SYS_IMAGEBLIT
2243 select FB_DEFERRED_IO
2245 This driver implements support for the E-Ink Metronome
2246 controller. The pre-release name for this device was 8track
2247 and could also have been called by some vendors as PVI-nnnn.
2250 tristate "Fujitsu MB862xx GDC support"
2252 select FB_CFB_FILLRECT
2253 select FB_CFB_COPYAREA
2254 select FB_CFB_IMAGEBLIT
2256 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2258 config FB_MB862XX_PCI_GDC
2259 bool "Carmine/Coral-P(A) GDC"
2260 depends on PCI && FB_MB862XX
2262 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2263 PCI graphics controller devices.
2265 config FB_MB862XX_LIME
2267 depends on FB_MB862XX
2268 depends on OF && !FB_MB862XX_PCI_GDC
2270 select FB_FOREIGN_ENDIAN
2271 select FB_LITTLE_ENDIAN
2273 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2276 tristate "EP93XX frame buffer support"
2277 depends on FB && ARCH_EP93XX
2278 select FB_CFB_FILLRECT
2279 select FB_CFB_COPYAREA
2280 select FB_CFB_IMAGEBLIT
2282 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2283 This driver is also available as a module. The module will be called
2286 config FB_PRE_INIT_FB
2287 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2288 depends on FB && FB_MB862XX_LIME
2290 Select this option if display contents should be inherited as set by
2294 tristate "MSM Framebuffer support"
2295 depends on FB && ARCH_MSM
2296 select FB_CFB_FILLRECT
2297 select FB_CFB_COPYAREA
2298 select FB_CFB_IMAGEBLIT
2301 tristate "MX3 Framebuffer support"
2302 depends on FB && MX3_IPU
2303 select FB_CFB_FILLRECT
2304 select FB_CFB_COPYAREA
2305 select FB_CFB_IMAGEBLIT
2308 This is a framebuffer device for the i.MX31 LCD Controller. So
2309 far only synchronous displays are supported. If you plan to use
2310 an LCD display with your i.MX31 system, say Y here.
2312 config FB_BROADSHEET
2313 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2315 select FB_SYS_FILLRECT
2316 select FB_SYS_COPYAREA
2317 select FB_SYS_IMAGEBLIT
2319 select FB_DEFERRED_IO
2321 This driver implements support for the E-Ink Broadsheet
2322 controller. The release name for this device was Epson S1D13521
2323 and could also have been called by other names when coupled with
2327 tristate "JZ4740 LCD framebuffer support"
2328 depends on FB && MACH_JZ4740
2329 select FB_SYS_FILLRECT
2330 select FB_SYS_COPYAREA
2331 select FB_SYS_IMAGEBLIT
2333 Framebuffer support for the JZ4740 SoC.
2336 tristate "MXS LCD framebuffer support"
2337 depends on FB && ARCH_MXS
2338 select FB_CFB_FILLRECT
2339 select FB_CFB_COPYAREA
2340 select FB_CFB_IMAGEBLIT
2342 Framebuffer support for the MXS SoC.
2344 config FB_PUV3_UNIGFX
2345 tristate "PKUnity v3 Unigfx framebuffer support"
2346 depends on FB && UNICORE32 && ARCH_PUV3
2347 select FB_SYS_FILLRECT
2348 select FB_SYS_COPYAREA
2349 select FB_SYS_IMAGEBLIT
2352 Choose this option if you want to use the Unigfx device as a
2353 framebuffer device. Without the support of PCI & AGP.
2355 source "drivers/video/omap/Kconfig"
2356 source "drivers/video/omap2/Kconfig"
2358 source "drivers/video/backlight/Kconfig"
2359 source "drivers/video/display/Kconfig"
2362 source "drivers/video/console/Kconfig"
2365 if FB || SGI_NEWPORT_CONSOLE
2366 source "drivers/video/logo/Kconfig"