5 menu "Graphics support"
13 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
15 config SH_LCD_MIPI_DSI
18 source "drivers/char/agp/Kconfig"
20 source "drivers/gpu/vga/Kconfig"
22 source "drivers/gpu/drm/Kconfig"
24 source "drivers/gpu/stub/Kconfig"
30 config VIDEO_OUTPUT_CONTROL
31 tristate "Lowlevel video output switch controls"
33 This framework adds support for low-level control of the video
37 tristate "Support for frame buffer devices"
39 The frame buffer device provides an abstraction for the graphics
40 hardware. It represents the frame buffer of some video hardware and
41 allows application software to access the graphics hardware through
42 a well-defined interface, so the software doesn't need to know
43 anything about the low-level (hardware register) stuff.
45 Frame buffer devices work identically across the different
46 architectures supported by Linux and make the implementation of
47 application programs easier and more portable; at this point, an X
48 server exists which uses the frame buffer device exclusively.
49 On several non-X86 architectures, the frame buffer device is the
50 only way to use the graphics hardware.
52 The device is accessed through special device nodes, usually located
53 in the /dev directory, i.e. /dev/fb*.
55 You need an utility program called fbset to make full use of frame
56 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
57 and the Framebuffer-HOWTO at
58 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
61 Say Y here and to the driver for your graphics board below if you
62 are compiling a kernel for a non-x86 architecture.
64 If you are compiling for the x86 architecture, you can say Y if you
65 want to play with it, but it is not essential. Please note that
66 running graphical applications that directly touch the hardware
67 (e.g. an accelerated X server) and that are not frame buffer
68 device-aware may cause unexpected results. If unsure, say N.
71 bool "Enable firmware EDID"
75 This enables access to the EDID transferred from the firmware.
76 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
77 transfers do not work for your driver and if you are using
78 nvidiafb, i810fb or savagefb.
80 In general, choosing Y for this option is safe. If you
81 experience extremely long delays while booting before you get
82 something on your display, try setting this to N. Matrox cards in
83 combination with certain motherboards and monitors are known to
84 suffer from this problem.
93 config FB_BOOT_VESA_SUPPORT
98 If true, at least one selected framebuffer driver can take advantage
99 of VESA video modes set at an early boot stage via the vga= parameter.
101 config FB_CFB_FILLRECT
106 Include the cfb_fillrect function for generic software rectangle
107 filling. This is used by drivers that don't provide their own
108 (accelerated) version.
110 config FB_CFB_COPYAREA
115 Include the cfb_copyarea function for generic software area copying.
116 This is used by drivers that don't provide their own (accelerated)
119 config FB_CFB_IMAGEBLIT
124 Include the cfb_imageblit function for generic software image
125 blitting. This is used by drivers that don't provide their own
126 (accelerated) version.
128 config FB_CFB_REV_PIXELS_IN_BYTE
133 Allow generic frame-buffer functions to work on displays with 1, 2
134 and 4 bits per pixel depths which has opposite order of pixels in
135 byte order to bytes in long order.
137 config FB_SYS_FILLRECT
142 Include the sys_fillrect function for generic software rectangle
143 filling. This is used by drivers that don't provide their own
144 (accelerated) version and the framebuffer is in system RAM.
146 config FB_SYS_COPYAREA
151 Include the sys_copyarea function for generic software area copying.
152 This is used by drivers that don't provide their own (accelerated)
153 version and the framebuffer is in system RAM.
155 config FB_SYS_IMAGEBLIT
160 Include the sys_imageblit function for generic software image
161 blitting. This is used by drivers that don't provide their own
162 (accelerated) version and the framebuffer is in system RAM.
164 menuconfig FB_FOREIGN_ENDIAN
165 bool "Framebuffer foreign endianness support"
168 This menu will let you enable support for the framebuffers with
169 non-native endianness (e.g. Little-Endian framebuffer on a
170 Big-Endian machine). Most probably you don't have such hardware,
171 so it's safe to say "n" here.
174 prompt "Choice endianness support"
175 depends on FB_FOREIGN_ENDIAN
177 config FB_BOTH_ENDIAN
178 bool "Support for Big- and Little-Endian framebuffers"
181 bool "Support for Big-Endian framebuffers only"
183 config FB_LITTLE_ENDIAN
184 bool "Support for Little-Endian framebuffers only"
193 config FB_WMT_GE_ROPS
198 Include functions for accelerated rectangle filling and area
199 copying using WonderMedia Graphics Engine operations.
201 config FB_DEFERRED_IO
208 depends on FB_DEFERRED_IO
215 Common utility functions useful to fbdev drivers of VGA-based
226 select BACKLIGHT_LCD_SUPPORT
227 select BACKLIGHT_CLASS_DEVICE
230 config FB_MODE_HELPERS
231 bool "Enable Video Mode Handling Helpers"
235 This enables functions for handling video modes using the
236 Generalized Timing Formula and the EDID parser. A few drivers rely
237 on this feature such as the radeonfb, rivafb, and the i810fb. If
238 your driver does not take advantage of this feature, choosing Y will
239 just increase the kernel size by about 5K.
241 config FB_TILEBLITTING
242 bool "Enable Tile Blitting Support"
246 This enables tile blitting. Tile blitting is a drawing technique
247 where the screen is divided into rectangular sections (tiles), whereas
248 the standard blitting divides the screen into pixels. Because the
249 default drawing element is a tile, drawing functions will be passed
250 parameters in terms of number of tiles instead of number of pixels.
251 For example, to draw a single character, instead of using bitmaps,
252 an index to an array of bitmaps will be used. To clear or move a
253 rectangular section of a screen, the rectangle will be described in
254 terms of number of tiles in the x- and y-axis.
256 This is particularly important to one driver, matroxfb. If
259 comment "Frame buffer hardware drivers"
263 tristate "Cirrus Logic support"
264 depends on FB && (ZORRO || PCI)
265 select FB_CFB_FILLRECT
266 select FB_CFB_COPYAREA
267 select FB_CFB_IMAGEBLIT
269 This enables support for Cirrus Logic GD542x/543x based boards on
270 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
272 If you have a PCI-based system, this enables support for these
273 chips: GD-543x, GD-544x, GD-5480.
275 Please read the file <file:Documentation/fb/cirrusfb.txt>.
277 Say N unless you have such a graphics board or plan to get one
278 before you next recompile the kernel.
281 tristate "Permedia2 support"
282 depends on FB && ((AMIGA && BROKEN) || PCI)
283 select FB_CFB_FILLRECT
284 select FB_CFB_COPYAREA
285 select FB_CFB_IMAGEBLIT
287 This is the frame buffer device driver for cards based on
288 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
289 The driver was tested on the following cards:
290 Diamond FireGL 1000 PRO AGP
291 ELSA Gloria Synergy PCI
292 Appian Jeronimo PRO (both heads) PCI
293 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
294 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
295 ASK Graphic Blaster Exxtreme AGP
297 To compile this driver as a module, choose M here: the
298 module will be called pm2fb.
300 config FB_PM2_FIFO_DISCONNECT
301 bool "enable FIFO disconnect feature"
302 depends on FB_PM2 && PCI
304 Support the Permedia2 FIFO disconnect feature.
307 tristate "ARM PrimeCell PL110 support"
308 depends on FB && ARM && ARM_AMBA
309 select FB_CFB_FILLRECT
310 select FB_CFB_COPYAREA
311 select FB_CFB_IMAGEBLIT
313 This framebuffer device driver is for the ARM PrimeCell PL110
314 Colour LCD controller. ARM PrimeCells provide the building
315 blocks for System on a Chip devices.
317 If you want to compile this as a module (=code which can be
318 inserted into and removed from the running kernel), say M
319 here and read <file:Documentation/kbuild/modules.txt>. The module
320 will be called amba-clcd.
323 bool "Acorn VIDC support"
324 depends on (FB = y) && ARM && ARCH_ACORN
325 select FB_CFB_FILLRECT
326 select FB_CFB_COPYAREA
327 select FB_CFB_IMAGEBLIT
329 This is the frame buffer device driver for the Acorn VIDC graphics
330 hardware found in Acorn RISC PCs and other ARM-based machines. If
334 bool "CLPS711X LCD support"
335 depends on (FB = y) && ARM && ARCH_CLPS711X
336 select FB_CFB_FILLRECT
337 select FB_CFB_COPYAREA
338 select FB_CFB_IMAGEBLIT
340 Say Y to enable the Framebuffer driver for the CLPS7111 and
344 bool "SA-1100 LCD support"
345 depends on (FB = y) && ARM && ARCH_SA1100
346 select FB_CFB_FILLRECT
347 select FB_CFB_COPYAREA
348 select FB_CFB_IMAGEBLIT
350 This is a framebuffer device for the SA-1100 LCD Controller.
351 See <http://www.linux-fbdev.org/> for information on framebuffer
354 If you plan to use the LCD display with your SA-1100 system, say
358 tristate "Freescale i.MX LCD support"
359 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
360 select FB_CFB_FILLRECT
361 select FB_CFB_COPYAREA
362 select FB_CFB_IMAGEBLIT
365 tristate "CyberPro 2000/2010/5000 support"
366 depends on FB && PCI && (BROKEN || !SPARC64)
367 select FB_CFB_FILLRECT
368 select FB_CFB_COPYAREA
369 select FB_CFB_IMAGEBLIT
371 This enables support for the Integraphics CyberPro 20x0 and 5000
372 VGA chips used in the Rebel.com Netwinder and other machines.
373 Say Y if you have a NetWinder or a graphics card containing this
374 device, otherwise say N.
376 config FB_CYBER2000_DDC
377 bool "DDC for CyberPro support"
378 depends on FB_CYBER2000
382 Say Y here if you want DDC support for your CyberPro graphics
383 card. This is only I2C bus support, driver does not use EDID.
385 config FB_CYBER2000_I2C
386 bool "CyberPro 2000/2010/5000 I2C support"
387 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
390 Enable support for the I2C video decoder interface on the
391 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
392 on the Netwinder machines for the SAA7111 video capture.
396 depends on (FB = y) && APOLLO
398 select FB_CFB_FILLRECT
399 select FB_CFB_IMAGEBLIT
403 depends on (FB = y) && Q40
405 select FB_CFB_FILLRECT
406 select FB_CFB_COPYAREA
407 select FB_CFB_IMAGEBLIT
410 tristate "Amiga native chipset support"
411 depends on FB && AMIGA
413 This is the frame buffer device driver for the builtin graphics
414 chipset found in Amigas.
416 To compile this driver as a module, choose M here: the
417 module will be called amifb.
420 bool "Amiga OCS chipset support"
423 This enables support for the original Agnus and Denise video chips,
424 found in the Amiga 1000 and most A500's and A2000's. If you intend
425 to run Linux on any of these systems, say Y; otherwise say N.
428 bool "Amiga ECS chipset support"
431 This enables support for the Enhanced Chip Set, found in later
432 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
433 you intend to run Linux on any of these systems, say Y; otherwise
437 bool "Amiga AGA chipset support"
440 This enables support for the Advanced Graphics Architecture (also
441 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
442 and CD32. If you intend to run Linux on any of these systems, say Y;
446 bool "Amiga FrameMaster II/Rainbow II support"
447 depends on (FB = y) && ZORRO
448 select FB_CFB_FILLRECT
449 select FB_CFB_COPYAREA
450 select FB_CFB_IMAGEBLIT
452 This is the frame buffer device driver for the Amiga FrameMaster
453 card from BSC (exhibited 1992 but not shipped as a CBM product).
456 tristate "Arc Monochrome LCD board support"
458 select FB_SYS_FILLRECT
459 select FB_SYS_COPYAREA
460 select FB_SYS_IMAGEBLIT
463 This enables support for the Arc Monochrome LCD board. The board
464 is based on the KS-108 lcd controller and is typically a matrix
465 of 2*n chips. This driver was tested with a 128x64 panel. This
466 driver supports it for use with x86 SBCs through a 16 bit GPIO
467 interface (8 bit data, 8 bit control). If you anticipate using
468 this driver, say Y or M; otherwise say N. You must specify the
469 GPIO IO address to be used for setting control and data.
472 bool "Atari native chipset support"
473 depends on (FB = y) && ATARI
474 select FB_CFB_FILLRECT
475 select FB_CFB_COPYAREA
476 select FB_CFB_IMAGEBLIT
478 This is the frame buffer device driver for the builtin graphics
479 chipset found in Ataris.
482 bool "Open Firmware frame buffer device support"
483 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
484 select FB_CFB_FILLRECT
485 select FB_CFB_COPYAREA
486 select FB_CFB_IMAGEBLIT
489 Say Y if you want support with Open Firmware for your graphics
493 bool "Apple \"control\" display support"
494 depends on (FB = y) && PPC_PMAC && PPC32
495 select FB_CFB_FILLRECT
496 select FB_CFB_COPYAREA
497 select FB_CFB_IMAGEBLIT
500 This driver supports a frame buffer for the graphics adapter in the
501 Power Macintosh 7300 and others.
504 bool "Apple \"platinum\" display support"
505 depends on (FB = y) && PPC_PMAC && PPC32
506 select FB_CFB_FILLRECT
507 select FB_CFB_COPYAREA
508 select FB_CFB_IMAGEBLIT
511 This driver supports a frame buffer for the "platinum" graphics
512 adapter in some Power Macintoshes.
515 bool "Apple \"valkyrie\" display support"
516 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
517 select FB_CFB_FILLRECT
518 select FB_CFB_COPYAREA
519 select FB_CFB_IMAGEBLIT
522 This driver supports a frame buffer for the "valkyrie" graphics
523 adapter in some Power Macintoshes.
526 bool "Chips 65550 display support"
527 depends on (FB = y) && PPC32 && PCI
528 select FB_CFB_FILLRECT
529 select FB_CFB_COPYAREA
530 select FB_CFB_IMAGEBLIT
532 This is the frame buffer device driver for the Chips & Technologies
533 65550 graphics chip in PowerBooks.
536 bool "Asiliant (Chips) 69000 display support"
537 depends on (FB = y) && PCI
538 select FB_CFB_FILLRECT
539 select FB_CFB_COPYAREA
540 select FB_CFB_IMAGEBLIT
542 This is the frame buffer device driver for the Asiliant 69030 chipset
545 bool "IMS Twin Turbo display support"
546 depends on (FB = y) && PCI
547 select FB_CFB_IMAGEBLIT
548 select FB_MACMODES if PPC
550 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
551 many Macintosh and compatible computers.
554 tristate "VGA 16-color graphics support"
555 depends on FB && (X86 || PPC)
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 select FONT_8x16 if FRAMEBUFFER_CONSOLE
562 This is the frame buffer device driver for VGA 16 color graphic
563 cards. Say Y if you have such a card.
565 To compile this driver as a module, choose M here: the
566 module will be called vga16fb.
568 config FB_BF54X_LQ043
569 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
570 depends on FB && (BF54x) && !BF542
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
577 config FB_BFIN_T350MCQB
578 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
579 depends on FB && BLACKFIN
581 select FB_CFB_FILLRECT
582 select FB_CFB_COPYAREA
583 select FB_CFB_IMAGEBLIT
585 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
586 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
587 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
589 config FB_BFIN_LQ035Q1
590 tristate "SHARP LQ035Q1DH02 TFT LCD"
591 depends on FB && BLACKFIN && SPI
592 select FB_CFB_FILLRECT
593 select FB_CFB_COPYAREA
594 select FB_CFB_IMAGEBLIT
597 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
598 the Blackfin Landscape LCD EZ-Extender Card.
599 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
600 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
602 To compile this driver as a module, choose M here: the
603 module will be called bfin-lq035q1-fb.
605 config FB_BF537_LQ035
606 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
607 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
608 select FB_CFB_FILLRECT
609 select FB_CFB_COPYAREA
610 select FB_CFB_IMAGEBLIT
613 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
616 To compile this driver as a module, choose M here: the
617 module will be called bf537-lq035.
620 tristate "Blackfin ADV7393 Video encoder"
621 depends on FB && BLACKFIN
623 select FB_CFB_FILLRECT
624 select FB_CFB_COPYAREA
625 select FB_CFB_IMAGEBLIT
627 This is the framebuffer device for a ADV7393 video encoder
628 attached to a Blackfin on the PPI port.
629 If your Blackfin board has a ADV7393 select Y.
631 To compile this driver as a module, choose M here: the
632 module will be called bfin_adv7393fb.
635 prompt "Video mode support"
636 depends on FB_BFIN_7393
646 bool 'NTSC 640x480 (Experimental)'
649 bool 'PAL 640x480 (Experimental)'
652 bool 'NTSC 720x480 YCbCR input'
655 bool 'PAL 720x576 YCbCR input'
660 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
661 depends on (FB_BFIN_7393)
662 default ADV7393_1XMEM
672 tristate "HP STI frame buffer device support"
673 depends on FB && PARISC
674 select FB_CFB_FILLRECT
675 select FB_CFB_COPYAREA
676 select FB_CFB_IMAGEBLIT
681 STI refers to the HP "Standard Text Interface" which is a set of
682 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
683 Enabling this option will implement the linux framebuffer device
684 using calls to the STI BIOS routines for initialisation.
686 If you enable this option, you will get a planar framebuffer device
687 /dev/fb which will work on the most common HP graphic cards of the
688 NGLE family, including the artist chips (in the 7xx and Bxxx series),
689 HCRX, HCRX24, CRX, CRX24 and VisEG series.
691 It is safe to enable this option, so you should probably say "Y".
694 bool "Generic Macintosh display support"
695 depends on (FB = y) && MAC
696 select FB_CFB_FILLRECT
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
703 depends on (FB = y) && DIO
704 select FB_CFB_IMAGEBLIT
708 tristate "TGA/SFB+ framebuffer support"
709 depends on FB && (ALPHA || TC)
710 select FB_CFB_FILLRECT
711 select FB_CFB_COPYAREA
712 select FB_CFB_IMAGEBLIT
715 This is the frame buffer device driver for generic TGA and SFB+
716 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
717 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
718 TURBOchannel cards, also known as PMAGD-A, -B and -C.
720 Due to hardware limitations ZLX-E2 and E3 cards are not supported
721 for DECstation 5000/200 systems. Additionally due to firmware
722 limitations these cards may cause troubles with booting DECstation
723 5000/240 and /260 systems, but are fully supported under Linux if
724 you manage to get it going. ;-)
726 Say Y if you have one of those.
729 tristate "Userspace VESA VGA graphics support"
730 depends on FB && CONNECTOR
731 select FB_CFB_FILLRECT
732 select FB_CFB_COPYAREA
733 select FB_CFB_IMAGEBLIT
734 select FB_MODE_HELPERS
736 This is the frame buffer driver for generic VBE 2.0 compliant
737 graphic cards. It can also take advantage of VBE 3.0 features,
738 such as refresh rate adjustment.
740 This driver generally provides more features than vesafb but
741 requires a userspace helper application called 'v86d'. See
742 <file:Documentation/fb/uvesafb.txt> for more information.
747 bool "VESA VGA graphics support"
748 depends on (FB = y) && X86
749 select FB_CFB_FILLRECT
750 select FB_CFB_COPYAREA
751 select FB_CFB_IMAGEBLIT
752 select FB_BOOT_VESA_SUPPORT
754 This is the frame buffer device driver for generic VESA 2.0
755 compliant graphic cards. The older VESA 1.2 cards are not supported.
756 You will get a boot time penguin logo at no additional cost. Please
757 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
760 bool "EFI-based Framebuffer Support"
761 depends on (FB = y) && X86 && EFI
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
766 This is the EFI frame buffer device driver. If the firmware on
767 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
768 using the EFI framebuffer as your console.
771 tristate "N411 Apollo/Hecuba devkit support"
772 depends on FB && X86 && MMU
773 select FB_SYS_FILLRECT
774 select FB_SYS_COPYAREA
775 select FB_SYS_IMAGEBLIT
777 select FB_DEFERRED_IO
780 This enables support for the Apollo display controller in its
781 Hecuba form using the n411 devkit.
784 tristate "Hercules mono graphics support"
787 Say Y here if you have a Hercules mono graphics card.
789 To compile this driver as a module, choose M here: the
790 module will be called hgafb.
792 As this card technology is at least 25 years old,
793 most people will answer N here.
796 tristate "SGI Visual Workstation framebuffer support"
797 depends on FB && X86_VISWS
798 select FB_CFB_FILLRECT
799 select FB_CFB_COPYAREA
800 select FB_CFB_IMAGEBLIT
802 SGI Visual Workstation support for framebuffer graphics.
805 bool "SGI Graphics Backend frame buffer support"
806 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
807 select FB_CFB_FILLRECT
808 select FB_CFB_COPYAREA
809 select FB_CFB_IMAGEBLIT
811 This is the frame buffer device driver for SGI Graphics Backend.
812 This chip is used in SGI O2 and Visual Workstation 320/540.
815 int "Video memory size in MB"
819 This is the amount of memory reserved for the framebuffer,
820 which can be any value between 1MB and 8MB.
823 bool "SBUS and UPA framebuffers"
824 depends on (FB = y) && SPARC
826 Say Y if you want support for SBUS or UPA based frame buffer device.
830 depends on (FB = y) && (SPARC && FB_SBUS)
831 select FB_CFB_FILLRECT
832 select FB_CFB_COPYAREA
833 select FB_CFB_IMAGEBLIT
835 This is the frame buffer device driver for the BWtwo frame buffer.
838 bool "CGthree support"
839 depends on (FB = y) && (SPARC && FB_SBUS)
840 select FB_CFB_FILLRECT
841 select FB_CFB_COPYAREA
842 select FB_CFB_IMAGEBLIT
844 This is the frame buffer device driver for the CGthree frame buffer.
847 bool "CGsix (GX,TurboGX) support"
848 depends on (FB = y) && (SPARC && FB_SBUS)
849 select FB_CFB_COPYAREA
850 select FB_CFB_IMAGEBLIT
852 This is the frame buffer device driver for the CGsix (GX, TurboGX)
856 bool "Creator/Creator3D/Elite3D support"
857 depends on FB_SBUS && SPARC64
858 select FB_CFB_COPYAREA
859 select FB_CFB_IMAGEBLIT
861 This is the frame buffer device driver for the Creator, Creator3D,
862 and Elite3D graphics boards.
865 bool "TCX (SS4/SS5 only) support"
867 select FB_CFB_FILLRECT
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
871 This is the frame buffer device driver for the TCX 24/8bit frame
875 bool "CGfourteen (SX) support"
877 select FB_CFB_FILLRECT
878 select FB_CFB_COPYAREA
879 select FB_CFB_IMAGEBLIT
881 This is the frame buffer device driver for the CGfourteen frame
882 buffer on Desktop SPARCsystems with the SX graphics option.
885 bool "P9100 (Sparcbook 3 only) support"
887 select FB_CFB_FILLRECT
888 select FB_CFB_COPYAREA
889 select FB_CFB_IMAGEBLIT
891 This is the frame buffer device driver for the P9100 card
892 supported on Sparcbook 3 machines.
895 bool "Leo (ZX) support"
897 select FB_CFB_FILLRECT
898 select FB_CFB_COPYAREA
899 select FB_CFB_IMAGEBLIT
901 This is the frame buffer device driver for the SBUS-based Sun ZX
902 (leo) frame buffer cards.
905 bool "IGA 168x display support"
906 depends on (FB = y) && SPARC32
907 select FB_CFB_FILLRECT
908 select FB_CFB_COPYAREA
909 select FB_CFB_IMAGEBLIT
911 This is the framebuffer device for the INTERGRAPHICS 1680 and
912 successor frame buffer cards.
915 bool "Sun XVR-500 3DLABS Wildcat support"
916 depends on (FB = y) && PCI && SPARC64
917 select FB_CFB_FILLRECT
918 select FB_CFB_COPYAREA
919 select FB_CFB_IMAGEBLIT
921 This is the framebuffer device for the Sun XVR-500 and similar
922 graphics cards based upon the 3DLABS Wildcat chipset. The driver
923 only works on sparc64 systems where the system firmware has
924 mostly initialized the card already. It is treated as a
925 completely dumb framebuffer device.
928 bool "Sun XVR-2500 3DLABS Wildcat support"
929 depends on (FB = y) && PCI && SPARC64
930 select FB_CFB_FILLRECT
931 select FB_CFB_COPYAREA
932 select FB_CFB_IMAGEBLIT
934 This is the framebuffer device for the Sun XVR-2500 and similar
935 graphics cards based upon the 3DLABS Wildcat chipset. The driver
936 only works on sparc64 systems where the system firmware has
937 mostly initialized the card already. It is treated as a
938 completely dumb framebuffer device.
941 bool "Sun XVR-1000 support"
942 depends on (FB = y) && SPARC64
943 select FB_CFB_FILLRECT
944 select FB_CFB_COPYAREA
945 select FB_CFB_IMAGEBLIT
947 This is the framebuffer device for the Sun XVR-1000 and similar
948 graphics cards. The driver only works on sparc64 systems where
949 the system firmware has mostly initialized the card already. It
950 is treated as a completely dumb framebuffer device.
953 tristate "NEC PowerVR 2 display support"
954 depends on FB && SH_DREAMCAST
955 select FB_CFB_FILLRECT
956 select FB_CFB_COPYAREA
957 select FB_CFB_IMAGEBLIT
959 Say Y here if you have a PowerVR 2 card in your box. If you plan to
960 run linux on your Dreamcast, you will have to say Y here.
961 This driver may or may not work on other PowerVR 2 cards, but is
962 totally untested. Use at your own risk. If unsure, say N.
964 To compile this driver as a module, choose M here: the
965 module will be called pvr2fb.
967 You can pass several parameters to the driver at boot time or at
968 module load time. The parameters look like "video=pvr2:XXX", where
969 the meaning of XXX can be found at the end of the main source file
970 (<file:drivers/video/pvr2fb.c>). Please see the file
971 <file:Documentation/fb/pvr2fb.txt>.
974 bool "Epson 1355 framebuffer support"
975 depends on (FB = y) && ARCH_CEIVA
976 select FB_CFB_FILLRECT
977 select FB_CFB_COPYAREA
978 select FB_CFB_IMAGEBLIT
980 Build in support for the SED1355 Epson Research Embedded RAMDAC
981 LCD/CRT Controller (since redesignated as the S1D13505) as a
982 framebuffer. Product specs at
983 <http://vdc.epson.com/>.
986 tristate "Epson S1D13XXX framebuffer support"
988 select FB_CFB_FILLRECT
989 select FB_CFB_COPYAREA
990 select FB_CFB_IMAGEBLIT
992 Support for S1D13XXX framebuffer device family (currently only
993 working with S1D13806). Product specs at
994 <http://vdc.epson.com/>
997 tristate "AT91/AT32 LCD Controller support"
998 depends on FB && HAVE_FB_ATMEL
999 select FB_CFB_FILLRECT
1000 select FB_CFB_COPYAREA
1001 select FB_CFB_IMAGEBLIT
1003 This enables support for the AT91/AT32 LCD Controller.
1006 bool "Frame Buffer in internal SRAM"
1007 depends on FB_ATMEL && ARCH_AT91SAM9261
1009 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1010 to let frame buffer in external SDRAM.
1013 bool "Use a STN display with AT91/AT32 LCD Controller"
1014 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1017 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1018 Controller. Say N if you want to connect a TFT.
1023 tristate "nVidia Framebuffer Support"
1024 depends on FB && PCI
1025 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1026 select FB_MODE_HELPERS
1027 select FB_CFB_FILLRECT
1028 select FB_CFB_COPYAREA
1029 select FB_CFB_IMAGEBLIT
1033 This driver supports graphics boards with the nVidia chips, TNT
1034 and newer. For very old chipsets, such as the RIVA128, then use
1036 Say Y if you have such a graphics board.
1038 To compile this driver as a module, choose M here: the
1039 module will be called nvidiafb.
1041 config FB_NVIDIA_I2C
1042 bool "Enable DDC Support"
1043 depends on FB_NVIDIA
1046 This enables I2C support for nVidia Chipsets. This is used
1047 only for getting EDID information from the attached display
1048 allowing for robust video mode handling and switching.
1050 Because fbdev-2.6 requires that drivers must be able to
1051 independently validate video mode parameters, you should say Y
1054 config FB_NVIDIA_DEBUG
1055 bool "Lots of debug output"
1056 depends on FB_NVIDIA
1059 Say Y here if you want the nVidia driver to output all sorts
1060 of debugging information to provide to the maintainer when
1061 something goes wrong.
1063 config FB_NVIDIA_BACKLIGHT
1064 bool "Support for backlight control"
1065 depends on FB_NVIDIA
1068 Say Y here if you want to control the backlight of your display.
1071 tristate "nVidia Riva support"
1072 depends on FB && PCI
1073 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1074 select FB_MODE_HELPERS
1075 select FB_CFB_FILLRECT
1076 select FB_CFB_COPYAREA
1077 select FB_CFB_IMAGEBLIT
1081 This driver supports graphics boards with the nVidia Riva/Geforce
1083 Say Y if you have such a graphics board.
1085 To compile this driver as a module, choose M here: the
1086 module will be called rivafb.
1089 bool "Enable DDC Support"
1093 This enables I2C support for nVidia Chipsets. This is used
1094 only for getting EDID information from the attached display
1095 allowing for robust video mode handling and switching.
1097 Because fbdev-2.6 requires that drivers must be able to
1098 independently validate video mode parameters, you should say Y
1101 config FB_RIVA_DEBUG
1102 bool "Lots of debug output"
1106 Say Y here if you want the Riva driver to output all sorts
1107 of debugging information to provide to the maintainer when
1108 something goes wrong.
1110 config FB_RIVA_BACKLIGHT
1111 bool "Support for backlight control"
1115 Say Y here if you want to control the backlight of your display.
1118 tristate "Intel 810/815 support (EXPERIMENTAL)"
1119 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1120 select FB_MODE_HELPERS
1121 select FB_CFB_FILLRECT
1122 select FB_CFB_COPYAREA
1123 select FB_CFB_IMAGEBLIT
1126 This driver supports the on-board graphics built in to the Intel 810
1127 and 815 chipsets. Say Y if you have and plan to use such a board.
1129 To compile this driver as a module, choose M here: the
1130 module will be called i810fb.
1132 For more information, please read
1133 <file:Documentation/fb/intel810.txt>
1136 bool "use VESA Generalized Timing Formula"
1139 If you say Y, then the VESA standard, Generalized Timing Formula
1140 or GTF, will be used to calculate the required video timing values
1141 per video mode. Since the GTF allows nondiscrete timings
1142 (nondiscrete being a range of values as opposed to discrete being a
1143 set of values), you'll be able to use any combination of horizontal
1144 and vertical resolutions, and vertical refresh rates without having
1145 to specify your own timing parameters. This is especially useful
1146 to maximize the performance of an aging display, or if you just
1147 have a display with nonstandard dimensions. A VESA compliant
1148 monitor is recommended, but can still work with non-compliant ones.
1149 If you need or want this, then select this option. The timings may
1150 not be compliant with Intel's recommended values. Use at your own
1153 If you say N, the driver will revert to discrete video timings
1154 using a set recommended by Intel in their documentation.
1159 bool "Enable DDC Support"
1160 depends on FB_I810 && FB_I810_GTF
1165 tristate "Intel LE80578 (Vermilion) support"
1166 depends on FB && PCI && X86
1167 select FB_MODE_HELPERS
1168 select FB_CFB_FILLRECT
1169 select FB_CFB_COPYAREA
1170 select FB_CFB_IMAGEBLIT
1172 This driver supports the LE80578 (Vermilion Range) chipset
1174 config FB_CARILLO_RANCH
1175 tristate "Intel Carillo Ranch support"
1176 depends on FB_LE80578 && FB && PCI && X86
1178 This driver supports the LE80578 (Carillo Ranch) board
1181 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1182 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1183 select FB_MODE_HELPERS
1184 select FB_CFB_FILLRECT
1185 select FB_CFB_COPYAREA
1186 select FB_CFB_IMAGEBLIT
1187 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1188 depends on !DRM_I915
1190 This driver supports the on-board graphics built in to the Intel
1191 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1192 Say Y if you have and plan to use such a board.
1194 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1196 To compile this driver as a module, choose M here: the
1197 module will be called intelfb.
1199 For more information, please read <file:Documentation/fb/intelfb.txt>
1201 config FB_INTEL_DEBUG
1202 bool "Intel driver Debug Messages"
1205 Say Y here if you want the Intel driver to output all sorts
1206 of debugging information to provide to the maintainer when
1207 something goes wrong.
1210 bool "DDC/I2C for Intel framebuffer support"
1215 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1218 tristate "Matrox acceleration"
1219 depends on FB && PCI
1220 select FB_CFB_FILLRECT
1221 select FB_CFB_COPYAREA
1222 select FB_CFB_IMAGEBLIT
1223 select FB_TILEBLITTING
1224 select FB_MACMODES if PPC_PMAC
1226 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1227 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1228 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1229 Matrox G400, G450 or G550 card in your box.
1231 To compile this driver as a module, choose M here: the
1232 module will be called matroxfb.
1234 You can pass several parameters to the driver at boot time or at
1235 module load time. The parameters look like "video=matroxfb:XXX", and
1236 are described in <file:Documentation/fb/matroxfb.txt>.
1238 config FB_MATROX_MILLENIUM
1239 bool "Millennium I/II support"
1240 depends on FB_MATROX
1242 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1243 video card. If you select "Advanced lowlevel driver options" below,
1244 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1245 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1246 also use font widths different from 8.
1248 config FB_MATROX_MYSTIQUE
1249 bool "Mystique support"
1250 depends on FB_MATROX
1252 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1253 video card. If you select "Advanced lowlevel driver options" below,
1254 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1255 packed pixel and 32 bpp packed pixel. You can also use font widths
1259 bool "G100/G200/G400/G450/G550 support"
1260 depends on FB_MATROX
1262 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1263 video card. If you select "Advanced lowlevel driver options", you
1264 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1265 pixel and 32 bpp packed pixel. You can also use font widths
1268 If you need support for G400 secondary head, you must say Y to
1269 "Matrox I2C support" and "G400 second head support" right below.
1270 G450/G550 secondary head and digital output are supported without
1273 The driver starts in monitor mode. You must use the matroxset tool
1274 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1275 swap primary and secondary head outputs, or to change output mode.
1276 Secondary head driver always start in 640x480 resolution and you
1277 must use fbset to change it.
1279 Do not forget that second head supports only 16 and 32 bpp
1280 packed pixels, so it is a good idea to compile them into the kernel
1281 too. You can use only some font widths, as the driver uses generic
1282 painting procedures (the secondary head does not use acceleration
1285 G450/G550 hardware can display TV picture only from secondary CRTC,
1286 and it performs no scaling, so picture must have 525 or 625 lines.
1288 config FB_MATROX_I2C
1289 tristate "Matrox I2C support"
1290 depends on FB_MATROX
1293 This drivers creates I2C buses which are needed for accessing the
1294 DDC (I2C) bus present on all Matroxes, an I2C bus which
1295 interconnects Matrox optional devices, like MGA-TVO on G200 and
1296 G400, and the secondary head DDC bus, present on G400 only.
1298 You can say Y or M here if you want to experiment with monitor
1299 detection code. You must say Y or M here if you want to use either
1300 second head of G400 or MGA-TVO on G200 or G400.
1302 If you compile it as module, it will create a module named
1305 config FB_MATROX_MAVEN
1306 tristate "G400 second head support"
1307 depends on FB_MATROX_G && FB_MATROX_I2C
1309 WARNING !!! This support does not work with G450 !!!
1311 Say Y or M here if you want to use a secondary head (meaning two
1312 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1313 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1314 secondary head output is blanked while you are in X. With XFree
1315 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1316 the fbdev driver on first head and the fbdev driver on second head.
1318 If you compile it as module, two modules are created,
1319 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1320 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1321 also load i2c-matroxfb to get it to run.
1323 The driver starts in monitor mode and you must use the matroxset
1325 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1326 PAL or NTSC or to swap primary and secondary head outputs.
1327 Secondary head driver also always start in 640x480 resolution, you
1328 must use fbset to change it.
1330 Also do not forget that second head supports only 16 and 32 bpp
1331 packed pixels, so it is a good idea to compile them into the kernel
1332 too. You can use only some font widths, as the driver uses generic
1333 painting procedures (the secondary head does not use acceleration
1337 tristate "ATI Radeon display support"
1338 depends on FB && PCI
1339 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1340 select FB_MODE_HELPERS
1341 select FB_CFB_FILLRECT
1342 select FB_CFB_COPYAREA
1343 select FB_CFB_IMAGEBLIT
1344 select FB_MACMODES if PPC_OF
1346 Choose this option if you want to use an ATI Radeon graphics card as
1347 a framebuffer device. There are both PCI and AGP versions. You
1348 don't need to choose this to run the Radeon in plain VGA mode.
1350 There is a product page at
1351 http://products.amd.com/en-us/GraphicCardResult.aspx
1353 config FB_RADEON_I2C
1354 bool "DDC/I2C for ATI Radeon support"
1355 depends on FB_RADEON
1359 Say Y here if you want DDC/I2C support for your Radeon board.
1361 config FB_RADEON_BACKLIGHT
1362 bool "Support for backlight control"
1363 depends on FB_RADEON
1366 Say Y here if you want to control the backlight of your display.
1368 config FB_RADEON_DEBUG
1369 bool "Lots of debug output from Radeon driver"
1370 depends on FB_RADEON
1373 Say Y here if you want the Radeon driver to output all sorts
1374 of debugging information to provide to the maintainer when
1375 something goes wrong.
1378 tristate "ATI Rage128 display support"
1379 depends on FB && PCI
1380 select FB_CFB_FILLRECT
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1383 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1384 select FB_MACMODES if PPC_PMAC
1386 This driver supports graphics boards with the ATI Rage128 chips.
1387 Say Y if you have such a graphics board and read
1388 <file:Documentation/fb/aty128fb.txt>.
1390 To compile this driver as a module, choose M here: the
1391 module will be called aty128fb.
1393 config FB_ATY128_BACKLIGHT
1394 bool "Support for backlight control"
1395 depends on FB_ATY128
1398 Say Y here if you want to control the backlight of your display.
1401 tristate "ATI Mach64 display support" if PCI || ATARI
1402 depends on FB && !SPARC32
1403 select FB_CFB_FILLRECT
1404 select FB_CFB_COPYAREA
1405 select FB_CFB_IMAGEBLIT
1406 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1407 select FB_MACMODES if PPC
1409 This driver supports graphics boards with the ATI Mach64 chips.
1410 Say Y if you have such a graphics board.
1412 To compile this driver as a module, choose M here: the
1413 module will be called atyfb.
1416 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1417 depends on PCI && FB_ATY
1418 default y if SPARC64 && PCI
1420 Say Y here to support use of ATI's 64-bit Rage boards (or other
1421 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1422 framebuffer device. The ATI product support page for these boards
1423 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1425 config FB_ATY_GENERIC_LCD
1426 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1427 depends on FB_ATY_CT
1429 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1430 Rage XC, or Rage XL chipset.
1433 bool "Mach64 GX support" if PCI
1437 Say Y here to support use of the ATI Mach64 Graphics Expression
1438 board (or other boards based on the Mach64 GX chipset) as a
1439 framebuffer device. The ATI product support page for these boards
1441 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1443 config FB_ATY_BACKLIGHT
1444 bool "Support for backlight control"
1448 Say Y here if you want to control the backlight of your display.
1451 tristate "S3 Trio/Virge support"
1452 depends on FB && PCI
1453 select FB_CFB_FILLRECT
1454 select FB_CFB_COPYAREA
1455 select FB_CFB_IMAGEBLIT
1456 select FB_TILEBLITTING
1459 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1461 Driver for graphics boards with S3 Trio / S3 Virge chip.
1464 tristate "S3 Savage support"
1465 depends on FB && PCI && EXPERIMENTAL
1466 select FB_MODE_HELPERS
1467 select FB_CFB_FILLRECT
1468 select FB_CFB_COPYAREA
1469 select FB_CFB_IMAGEBLIT
1472 This driver supports notebooks and computers with S3 Savage PCI/AGP
1475 Say Y if you have such a graphics card.
1477 To compile this driver as a module, choose M here; the module
1478 will be called savagefb.
1480 config FB_SAVAGE_I2C
1481 bool "Enable DDC2 Support"
1482 depends on FB_SAVAGE
1485 This enables I2C support for S3 Savage Chipsets. This is used
1486 only for getting EDID information from the attached display
1487 allowing for robust video mode handling and switching.
1489 Because fbdev-2.6 requires that drivers must be able to
1490 independently validate video mode parameters, you should say Y
1493 config FB_SAVAGE_ACCEL
1494 bool "Enable Console Acceleration"
1495 depends on FB_SAVAGE
1498 This option will compile in console acceleration support. If
1499 the resulting framebuffer console has bothersome glitches, then
1503 tristate "SiS/XGI display support"
1504 depends on FB && PCI
1505 select FB_CFB_FILLRECT
1506 select FB_CFB_COPYAREA
1507 select FB_CFB_IMAGEBLIT
1508 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1510 This is the frame buffer device driver for the SiS 300, 315, 330
1511 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1512 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1514 To compile this driver as a module, choose M here; the module
1515 will be called sisfb.
1518 bool "SiS 300 series support"
1521 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1524 bool "SiS 315/330/340 series and XGI support"
1527 Say Y here to support use of the SiS 315, 330 and 340 series
1528 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1529 as XGI V3XT, V5, V8 and Z7.
1532 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1533 depends on FB && PCI && X86
1534 select FB_CFB_FILLRECT
1535 select FB_CFB_COPYAREA
1536 select FB_CFB_IMAGEBLIT
1541 This is the frame buffer device driver for Graphics chips of VIA
1542 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1543 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1545 Say Y if you have a VIA UniChrome graphics board.
1547 To compile this driver as a module, choose M here: the
1548 module will be called viafb.
1552 config FB_VIA_DIRECT_PROCFS
1553 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1557 Allow direct hardware access to some output registers via procfs.
1558 This is dangerous but may provide the only chance to get the
1559 correct output device configuration.
1560 Its use is strongly discouraged.
1562 config FB_VIA_X_COMPATIBILITY
1563 bool "X server compatibility"
1567 This option reduces the functionality (power saving, ...) of the
1568 framebuffer to avoid negative impact on the OpenChrome X server.
1569 If you use any X server other than fbdev you should enable this
1570 otherwise it should be safe to disable it and allow using all
1576 tristate "NeoMagic display support"
1577 depends on FB && PCI
1578 select FB_MODE_HELPERS
1579 select FB_CFB_FILLRECT
1580 select FB_CFB_COPYAREA
1581 select FB_CFB_IMAGEBLIT
1584 This driver supports notebooks with NeoMagic PCI chips.
1585 Say Y if you have such a graphics card.
1587 To compile this driver as a module, choose M here: the
1588 module will be called neofb.
1591 tristate "IMG Kyro support"
1592 depends on FB && PCI
1593 select FB_CFB_FILLRECT
1594 select FB_CFB_COPYAREA
1595 select FB_CFB_IMAGEBLIT
1597 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1600 To compile this driver as a module, choose M here: the
1601 module will be called kyrofb.
1604 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1605 depends on FB && PCI
1606 select FB_CFB_IMAGEBLIT
1607 select FB_CFB_FILLRECT
1608 select FB_CFB_COPYAREA
1609 select FB_MODE_HELPERS
1611 This driver supports graphics boards with the 3Dfx Banshee,
1612 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1613 such a graphics board.
1615 To compile this driver as a module, choose M here: the
1616 module will be called tdfxfb.
1618 config FB_3DFX_ACCEL
1619 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1620 depends on FB_3DFX && EXPERIMENTAL
1622 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1623 device driver with acceleration functions.
1626 bool "Enable DDC/I2C support"
1627 depends on FB_3DFX && EXPERIMENTAL
1631 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1634 tristate "3Dfx Voodoo Graphics (sst1) support"
1635 depends on FB && PCI
1636 select FB_CFB_FILLRECT
1637 select FB_CFB_COPYAREA
1638 select FB_CFB_IMAGEBLIT
1640 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1641 Voodoo2 (cvg) based graphics card.
1643 To compile this driver as a module, choose M here: the
1644 module will be called sstfb.
1646 WARNING: Do not use any application that uses the 3D engine
1647 (namely glide) while using this driver.
1648 Please read the <file:Documentation/fb/sstfb.txt> for supported
1649 options and other important info support.
1652 tristate "VIA VT8623 support"
1653 depends on FB && PCI
1654 select FB_CFB_FILLRECT
1655 select FB_CFB_COPYAREA
1656 select FB_CFB_IMAGEBLIT
1657 select FB_TILEBLITTING
1660 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1662 Driver for CastleRock integrated graphics core in the
1663 VIA VT8623 [Apollo CLE266] chipset.
1666 tristate "Trident/CyberXXX/CyberBlade support"
1667 depends on FB && PCI
1668 select FB_CFB_FILLRECT
1669 select FB_CFB_COPYAREA
1670 select FB_CFB_IMAGEBLIT
1672 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1673 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1675 There are also integrated versions of these chips called CyberXXXX,
1676 CyberImage or CyberBlade. These chips are mostly found in laptops
1677 but also on some motherboards including early VIA EPIA motherboards.
1678 For more information, read <file:Documentation/fb/tridentfb.txt>
1680 Say Y if you have such a graphics board.
1682 To compile this driver as a module, choose M here: the
1683 module will be called tridentfb.
1686 tristate "ARK 2000PV support"
1687 depends on FB && PCI
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1691 select FB_TILEBLITTING
1694 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1696 Driver for PCI graphics boards with ARK 2000PV chip
1697 and ICS 5342 RAMDAC.
1700 tristate "Permedia3 support (EXPERIMENTAL)"
1701 depends on FB && PCI && EXPERIMENTAL
1702 select FB_CFB_FILLRECT
1703 select FB_CFB_COPYAREA
1704 select FB_CFB_IMAGEBLIT
1706 This is the frame buffer device driver for the 3DLabs Permedia3
1707 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1708 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1709 and maybe other boards.
1712 tristate "Fujitsu carmine frame buffer support"
1713 depends on FB && PCI
1714 select FB_CFB_FILLRECT
1715 select FB_CFB_COPYAREA
1716 select FB_CFB_IMAGEBLIT
1718 This is the frame buffer device driver for the Fujitsu Carmine chip.
1719 The driver provides two independent frame buffer devices.
1722 depends on FB_CARMINE
1723 prompt "DRAM timing"
1724 default FB_CARMINE_DRAM_EVAL
1726 config FB_CARMINE_DRAM_EVAL
1727 bool "Eval board timings"
1729 Use timings which work on the eval card.
1731 config CARMINE_DRAM_CUSTOM
1732 bool "Custom board timings"
1734 Use custom board timings.
1738 bool "Au1100 LCD Driver"
1739 depends on (FB = y) && MIPS && SOC_AU1100
1740 select FB_CFB_FILLRECT
1741 select FB_CFB_COPYAREA
1742 select FB_CFB_IMAGEBLIT
1744 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1745 various panels and CRTs by passing in kernel cmd line option
1746 au1100fb:panel=<name>.
1749 bool "Au1200 LCD Driver"
1750 depends on (FB = y) && MIPS && SOC_AU1200
1751 select FB_CFB_FILLRECT
1752 select FB_CFB_COPYAREA
1753 select FB_CFB_IMAGEBLIT
1755 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1756 various panels and CRTs by passing in kernel cmd line option
1757 au1200fb:panel=<name>.
1760 bool "VT8500 LCD Driver"
1761 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1762 select FB_WMT_GE_ROPS
1763 select FB_SYS_IMAGEBLIT
1765 This is the framebuffer driver for VIA VT8500 integrated LCD
1769 bool "WM8505 frame buffer support"
1770 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1771 select FB_WMT_GE_ROPS
1772 select FB_SYS_IMAGEBLIT
1774 This is the framebuffer driver for WonderMedia WM8505
1775 integrated LCD controller.
1777 source "drivers/video/geode/Kconfig"
1780 tristate "HD64461 Frame Buffer support"
1781 depends on FB && HD64461
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1786 This is the frame buffer device driver for the Hitachi HD64461 LCD
1790 bool "PMAG-AA TURBOchannel framebuffer support"
1791 depends on (FB = y) && TC
1792 select FB_CFB_FILLRECT
1793 select FB_CFB_COPYAREA
1794 select FB_CFB_IMAGEBLIT
1796 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1797 used mainly in the MIPS-based DECstation series.
1800 tristate "PMAG-BA TURBOchannel framebuffer support"
1802 select FB_CFB_FILLRECT
1803 select FB_CFB_COPYAREA
1804 select FB_CFB_IMAGEBLIT
1806 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1807 used mainly in the MIPS-based DECstation series.
1810 tristate "PMAGB-B TURBOchannel framebuffer support"
1812 select FB_CFB_FILLRECT
1813 select FB_CFB_COPYAREA
1814 select FB_CFB_IMAGEBLIT
1816 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1817 in the MIPS-based DECstation series. The card is currently only
1818 supported in 1280x1024x8 mode.
1821 bool "Maxine (Personal DECstation) onboard framebuffer support"
1822 depends on (FB = y) && MACH_DECSTATION
1823 select FB_CFB_FILLRECT
1824 select FB_CFB_COPYAREA
1825 select FB_CFB_IMAGEBLIT
1827 Support for the onboard framebuffer (1024x768x8) in the Personal
1828 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1832 bool "G364 frame buffer support"
1833 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1834 select FB_CFB_FILLRECT
1835 select FB_CFB_COPYAREA
1836 select FB_CFB_IMAGEBLIT
1838 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1839 Olivetti M700-10 systems.
1842 bool "Motorola 68328 native frame buffer support"
1843 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 Say Y here if you want to support the built-in frame buffer of
1849 the Motorola 68328 CPU family.
1852 tristate "PXA168/910 LCD framebuffer support"
1853 depends on FB && (CPU_PXA168 || CPU_PXA910)
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Frame buffer driver for the built-in LCD controller in the Marvell
1862 tristate "PXA LCD framebuffer support"
1863 depends on FB && ARCH_PXA
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 Intel
1871 This driver is also available as a module ( = code which can be
1872 inserted and removed from the running kernel whenever you want). The
1873 module will be called pxafb. If you want to compile it as a module,
1874 say M here and read <file:Documentation/kbuild/modules.txt>.
1878 config FB_PXA_OVERLAY
1879 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1881 depends on FB_PXA && (PXA27x || PXA3xx)
1883 config FB_PXA_SMARTPANEL
1884 bool "PXA Smartpanel LCD support"
1888 config FB_PXA_PARAMETERS
1889 bool "PXA LCD command line parameters"
1893 Enable the use of kernel command line or module parameters
1894 to configure the physical properties of the LCD panel when
1895 using the PXA LCD driver.
1897 This option allows you to override the panel parameters
1898 supplied by the platform in order to support multiple
1899 different models of flatpanel. If you will only be using a
1900 single model of flatpanel then you can safely leave this
1903 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1906 tristate "PXA3xx 2D graphics accelerator driver"
1909 Kernelspace driver for the 2D graphics controller unit (GCU)
1910 found on PXA3xx processors. There is a counterpart driver in the
1911 DirectFB suite, see http://www.directfb.org/
1913 If you compile this as a module, it will be called pxa3xx_gcu.
1916 tristate "2700G LCD framebuffer support"
1917 depends on FB && ARCH_PXA
1918 select FB_CFB_FILLRECT
1919 select FB_CFB_COPYAREA
1920 select FB_CFB_IMAGEBLIT
1922 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1926 bool "Enable debugging info via debugfs"
1927 depends on FB_MBX && DEBUG_FS
1930 Enable this if you want debugging information using the debug
1931 filesystem (debugfs)
1936 tristate "Freescale DIU framebuffer support"
1937 depends on FB && FSL_SOC
1938 select FB_MODE_HELPERS
1939 select FB_CFB_FILLRECT
1940 select FB_CFB_COPYAREA
1941 select FB_CFB_IMAGEBLIT
1942 select PPC_LIB_RHEAP
1944 Framebuffer driver for the Freescale SoC DIU
1947 tristate "W100 frame buffer support"
1948 depends on FB && ARCH_PXA
1949 select FB_CFB_FILLRECT
1950 select FB_CFB_COPYAREA
1951 select FB_CFB_IMAGEBLIT
1953 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1954 It can also drive the w3220 chip found on iPAQ hx4700.
1956 This driver is also available as a module ( = code which can be
1957 inserted and removed from the running kernel whenever you want). The
1958 module will be called w100fb. If you want to compile it as a module,
1959 say M here and read <file:Documentation/kbuild/modules.txt>.
1963 config FB_SH_MOBILE_LCDC
1964 tristate "SuperH Mobile LCDC framebuffer support"
1965 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1966 select FB_SYS_FILLRECT
1967 select FB_SYS_COPYAREA
1968 select FB_SYS_IMAGEBLIT
1970 select FB_DEFERRED_IO
1972 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1974 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1976 config FB_SH_MOBILE_HDMI
1977 tristate "SuperH Mobile HDMI controller support"
1978 depends on FB_SH_MOBILE_LCDC
1979 select FB_MODE_HELPERS
1984 Driver for the on-chip SH-Mobile HDMI controller.
1987 tristate "Toshiba Mobile IO FrameBuffer support"
1988 depends on FB && MFD_CORE
1989 select FB_CFB_FILLRECT
1990 select FB_CFB_COPYAREA
1991 select FB_CFB_IMAGEBLIT
1993 Frame buffer driver for the Toshiba Mobile IO integrated as found
1994 on the Sharp SL-6000 series
1996 This driver is also available as a module ( = code which can be
1997 inserted and removed from the running kernel whenever you want). The
1998 module will be called tmiofb. If you want to compile it as a module,
1999 say M here and read <file:Documentation/kbuild/modules.txt>.
2003 config FB_TMIO_ACCELL
2004 bool "tmiofb acceleration"
2009 tristate "Samsung S3C framebuffer support"
2010 depends on FB && S3C_DEV_FB
2011 select FB_CFB_FILLRECT
2012 select FB_CFB_COPYAREA
2013 select FB_CFB_IMAGEBLIT
2015 Frame buffer driver for the built-in FB controller in the Samsung
2016 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2017 and the S3C64XX series such as the S3C6400 and S3C6410.
2019 These chips all have the same basic framebuffer design with the
2020 actual capabilities depending on the chip. For instance the S3C6400
2021 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2022 currently only have two.
2024 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2026 config FB_S3C_DEBUG_REGWRITE
2027 bool "Debug register writes"
2030 Show all register writes via printk(KERN_DEBUG)
2033 tristate "S3C2410 LCD framebuffer support"
2034 depends on FB && ARCH_S3C2410
2035 select FB_CFB_FILLRECT
2036 select FB_CFB_COPYAREA
2037 select FB_CFB_IMAGEBLIT
2039 Frame buffer driver for the built-in LCD controller in the Samsung
2042 This driver is also available as a module ( = code which can be
2043 inserted and removed from the running kernel whenever you want). The
2044 module will be called s3c2410fb. If you want to compile it as a module,
2045 say M here and read <file:Documentation/kbuild/modules.txt>.
2048 config FB_S3C2410_DEBUG
2049 bool "S3C2410 lcd debug messages"
2050 depends on FB_S3C2410
2052 Turn on debugging messages. Note that you can set/unset at run time
2056 bool "NUC900 LCD framebuffer support"
2057 depends on FB && ARCH_W90X900
2058 select FB_CFB_FILLRECT
2059 select FB_CFB_COPYAREA
2060 select FB_CFB_IMAGEBLIT
2062 Frame buffer driver for the built-in LCD controller in the Nuvoton
2065 config GPM1040A0_320X240
2066 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2067 depends on FB_NUC900
2069 config FB_NUC900_DEBUG
2070 bool "NUC900 lcd debug messages"
2071 depends on FB_NUC900
2073 Turn on debugging messages. Note that you can set/unset at run time
2077 tristate "Silicon Motion SM501 framebuffer support"
2078 depends on FB && MFD_SM501
2079 select FB_CFB_FILLRECT
2080 select FB_CFB_COPYAREA
2081 select FB_CFB_IMAGEBLIT
2083 Frame buffer driver for the CRT and LCD controllers in the Silicon
2086 This driver is also available as a module ( = code which can be
2087 inserted and removed from the running kernel whenever you want). The
2088 module will be called sm501fb. If you want to compile it as a module,
2089 say M here and read <file:Documentation/kbuild/modules.txt>.
2094 tristate "Displaylink USB Framebuffer support"
2095 depends on FB && USB
2096 select FB_MODE_HELPERS
2097 select FB_SYS_FILLRECT
2098 select FB_SYS_COPYAREA
2099 select FB_SYS_IMAGEBLIT
2101 select FB_DEFERRED_IO
2103 This is a kernel framebuffer driver for DisplayLink USB devices.
2104 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2105 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2106 To compile as a module, choose M here: the module name is udlfb.
2108 config FB_PNX4008_DUM
2109 tristate "Display Update Module support on Philips PNX4008 board"
2110 depends on FB && ARCH_PNX4008
2112 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2114 config FB_PNX4008_DUM_RGB
2115 tristate "RGB Framebuffer support on Philips PNX4008 board"
2116 depends on FB_PNX4008_DUM
2117 select FB_CFB_FILLRECT
2118 select FB_CFB_COPYAREA
2119 select FB_CFB_IMAGEBLIT
2121 Say Y here to enable support for PNX4008 RGB Framebuffer
2123 config FB_IBM_GXT4500
2124 tristate "Framebuffer support for IBM GXT4500P adaptor"
2125 depends on FB && PPC
2126 select FB_CFB_FILLRECT
2127 select FB_CFB_COPYAREA
2128 select FB_CFB_IMAGEBLIT
2130 Say Y here to enable support for the IBM GXT4500P display
2131 adaptor, found on some IBM System P (pSeries) machines.
2134 tristate "PS3 GPU framebuffer driver"
2135 depends on FB && PS3_PS3AV
2136 select FB_SYS_FILLRECT
2137 select FB_SYS_COPYAREA
2138 select FB_SYS_IMAGEBLIT
2140 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2142 Include support for the virtual frame buffer in the PS3 platform.
2144 config FB_PS3_DEFAULT_SIZE_M
2145 int "PS3 default frame buffer size (in MiB)"
2149 This is the default size (in MiB) of the virtual frame buffer in
2151 The default value can be overridden on the kernel command line
2152 using the "ps3fb" option (e.g. "ps3fb=9M");
2155 tristate "Xilinx frame buffer support"
2156 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2157 select FB_CFB_FILLRECT
2158 select FB_CFB_COPYAREA
2159 select FB_CFB_IMAGEBLIT
2161 Include support for the Xilinx ML300/ML403 reference design
2162 framebuffer. ML300 carries a 640*480 LCD display on the board,
2163 ML403 uses a standard DB15 VGA connector.
2166 tristate "Cobalt server LCD frame buffer support"
2167 depends on FB && MIPS_COBALT
2170 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2171 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2172 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2173 select FB_CFB_FILLRECT
2174 select FB_CFB_COPYAREA
2175 select FB_CFB_IMAGEBLIT
2177 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2178 (D)STN/TFT LCD Controller.
2179 Supports display resolutions up to 1024x1024 pixel, grayscale and
2180 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2181 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2182 panels <= 320 pixel horizontal resolution.
2185 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2186 depends on FB && ARCH_DAVINCI_DA8XX
2187 select FB_CFB_FILLRECT
2188 select FB_CFB_COPYAREA
2189 select FB_CFB_IMAGEBLIT
2191 This is the frame buffer device driver for the TI LCD controller
2192 found on DA8xx/OMAP-L1xx SoCs.
2196 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2198 select FB_SYS_FILLRECT
2199 select FB_SYS_COPYAREA
2200 select FB_SYS_IMAGEBLIT
2203 This is a `virtual' frame buffer device. It operates on a chunk of
2204 unswappable kernel memory instead of on the memory of a graphics
2205 board. This means you cannot see any output sent to this frame
2206 buffer device, while it does consume precious memory. The main use
2207 of this frame buffer device is testing and debugging the frame
2208 buffer subsystem. Do NOT enable it for normal systems! To protect
2209 the innocent, it has to be enabled explicitly at boot time using the
2210 kernel option `video=vfb:'.
2212 To compile this driver as a module, choose M here: the
2213 module will be called vfb. In order to load it, you must use
2214 the vfb_enable=1 option.
2218 config XEN_FBDEV_FRONTEND
2219 tristate "Xen virtual frame buffer support"
2220 depends on FB && XEN
2221 select FB_SYS_FILLRECT
2222 select FB_SYS_COPYAREA
2223 select FB_SYS_IMAGEBLIT
2225 select FB_DEFERRED_IO
2226 select XEN_XENBUS_FRONTEND
2229 This driver implements the front-end of the Xen virtual
2230 frame buffer driver. It communicates with a back-end
2234 tristate "E-Ink Metronome/8track controller support"
2236 select FB_SYS_FILLRECT
2237 select FB_SYS_COPYAREA
2238 select FB_SYS_IMAGEBLIT
2240 select FB_DEFERRED_IO
2242 This driver implements support for the E-Ink Metronome
2243 controller. The pre-release name for this device was 8track
2244 and could also have been called by some vendors as PVI-nnnn.
2247 tristate "Fujitsu MB862xx GDC support"
2249 select FB_CFB_FILLRECT
2250 select FB_CFB_COPYAREA
2251 select FB_CFB_IMAGEBLIT
2253 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2255 config FB_MB862XX_PCI_GDC
2256 bool "Carmine/Coral-P(A) GDC"
2257 depends on PCI && FB_MB862XX
2259 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2260 PCI graphics controller devices.
2262 config FB_MB862XX_LIME
2264 depends on FB_MB862XX
2265 depends on OF && !FB_MB862XX_PCI_GDC
2267 select FB_FOREIGN_ENDIAN
2268 select FB_LITTLE_ENDIAN
2270 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2273 tristate "EP93XX frame buffer support"
2274 depends on FB && ARCH_EP93XX
2275 select FB_CFB_FILLRECT
2276 select FB_CFB_COPYAREA
2277 select FB_CFB_IMAGEBLIT
2279 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2280 This driver is also available as a module. The module will be called
2283 config FB_PRE_INIT_FB
2284 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2285 depends on FB && FB_MB862XX_LIME
2287 Select this option if display contents should be inherited as set by
2291 tristate "MSM Framebuffer support"
2292 depends on FB && ARCH_MSM
2293 select FB_CFB_FILLRECT
2294 select FB_CFB_COPYAREA
2295 select FB_CFB_IMAGEBLIT
2298 tristate "MX3 Framebuffer support"
2299 depends on FB && MX3_IPU
2300 select FB_CFB_FILLRECT
2301 select FB_CFB_COPYAREA
2302 select FB_CFB_IMAGEBLIT
2305 This is a framebuffer device for the i.MX31 LCD Controller. So
2306 far only synchronous displays are supported. If you plan to use
2307 an LCD display with your i.MX31 system, say Y here.
2309 config FB_BROADSHEET
2310 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2312 select FB_SYS_FILLRECT
2313 select FB_SYS_COPYAREA
2314 select FB_SYS_IMAGEBLIT
2316 select FB_DEFERRED_IO
2318 This driver implements support for the E-Ink Broadsheet
2319 controller. The release name for this device was Epson S1D13521
2320 and could also have been called by other names when coupled with
2324 tristate "JZ4740 LCD framebuffer support"
2325 depends on FB && MACH_JZ4740
2326 select FB_SYS_FILLRECT
2327 select FB_SYS_COPYAREA
2328 select FB_SYS_IMAGEBLIT
2330 Framebuffer support for the JZ4740 SoC.
2333 tristate "MXS LCD framebuffer support"
2334 depends on FB && ARCH_MXS
2335 select FB_CFB_FILLRECT
2336 select FB_CFB_COPYAREA
2337 select FB_CFB_IMAGEBLIT
2339 Framebuffer support for the MXS SoC.
2341 config FB_PUV3_UNIGFX
2342 tristate "PKUnity v3 Unigfx framebuffer support"
2343 depends on FB && UNICORE32 && ARCH_PUV3
2344 select FB_SYS_FILLRECT
2345 select FB_SYS_COPYAREA
2346 select FB_SYS_IMAGEBLIT
2349 Choose this option if you want to use the Unigfx device as a
2350 framebuffer device. Without the support of PCI & AGP.
2352 source "drivers/video/omap/Kconfig"
2353 source "drivers/video/omap2/Kconfig"
2355 source "drivers/video/backlight/Kconfig"
2356 source "drivers/video/display/Kconfig"
2359 source "drivers/video/console/Kconfig"
2362 if FB || SGI_NEWPORT_CONSOLE
2363 source "drivers/video/logo/Kconfig"