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/host1x/Kconfig"
26 source "drivers/gpu/arm/midgard/Kconfig"
28 source "drivers/gpu/arm/mali400/mali/Kconfig"
30 source "drivers/gpu/arm/mali400/ump/Kconfig"
32 source "drivers/gpu/rogue/Kconfig"
38 config VIDEO_OUTPUT_CONTROL
39 tristate "Lowlevel video output switch controls"
41 This framework adds support for low-level control of the video
44 config VIDEOMODE_HELPERS
50 config VEXPRESS_DVI_CONTROL
51 bool "Versatile Express DVI control"
52 depends on FB && VEXPRESS_CONFIG
56 tristate "Support for frame buffer devices"
58 The frame buffer device provides an abstraction for the graphics
59 hardware. It represents the frame buffer of some video hardware and
60 allows application software to access the graphics hardware through
61 a well-defined interface, so the software doesn't need to know
62 anything about the low-level (hardware register) stuff.
64 Frame buffer devices work identically across the different
65 architectures supported by Linux and make the implementation of
66 application programs easier and more portable; at this point, an X
67 server exists which uses the frame buffer device exclusively.
68 On several non-X86 architectures, the frame buffer device is the
69 only way to use the graphics hardware.
71 The device is accessed through special device nodes, usually located
72 in the /dev directory, i.e. /dev/fb*.
74 You need an utility program called fbset to make full use of frame
75 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
76 and the Framebuffer-HOWTO at
77 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
80 Say Y here and to the driver for your graphics board below if you
81 are compiling a kernel for a non-x86 architecture.
83 If you are compiling for the x86 architecture, you can say Y if you
84 want to play with it, but it is not essential. Please note that
85 running graphical applications that directly touch the hardware
86 (e.g. an accelerated X server) and that are not frame buffer
87 device-aware may cause unexpected results. If unsure, say N.
90 bool "Enable firmware EDID"
94 This enables access to the EDID transferred from the firmware.
95 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
96 transfers do not work for your driver and if you are using
97 nvidiafb, i810fb or savagefb.
99 In general, choosing Y for this option is safe. If you
100 experience extremely long delays while booting before you get
101 something on your display, try setting this to N. Matrox cards in
102 combination with certain motherboards and monitors are known to
103 suffer from this problem.
112 config FB_BOOT_VESA_SUPPORT
117 If true, at least one selected framebuffer driver can take advantage
118 of VESA video modes set at an early boot stage via the vga= parameter.
120 config FB_CFB_FILLRECT
125 Include the cfb_fillrect function for generic software rectangle
126 filling. This is used by drivers that don't provide their own
127 (accelerated) version.
129 config FB_CFB_COPYAREA
134 Include the cfb_copyarea function for generic software area copying.
135 This is used by drivers that don't provide their own (accelerated)
138 config FB_CFB_IMAGEBLIT
143 Include the cfb_imageblit function for generic software image
144 blitting. This is used by drivers that don't provide their own
145 (accelerated) version.
147 config FB_CFB_REV_PIXELS_IN_BYTE
152 Allow generic frame-buffer functions to work on displays with 1, 2
153 and 4 bits per pixel depths which has opposite order of pixels in
154 byte order to bytes in long order.
156 config FB_SYS_FILLRECT
161 Include the sys_fillrect function for generic software rectangle
162 filling. This is used by drivers that don't provide their own
163 (accelerated) version and the framebuffer is in system RAM.
165 config FB_SYS_COPYAREA
170 Include the sys_copyarea function for generic software area copying.
171 This is used by drivers that don't provide their own (accelerated)
172 version and the framebuffer is in system RAM.
174 config FB_SYS_IMAGEBLIT
179 Include the sys_imageblit function for generic software image
180 blitting. This is used by drivers that don't provide their own
181 (accelerated) version and the framebuffer is in system RAM.
183 menuconfig FB_FOREIGN_ENDIAN
184 bool "Framebuffer foreign endianness support"
187 This menu will let you enable support for the framebuffers with
188 non-native endianness (e.g. Little-Endian framebuffer on a
189 Big-Endian machine). Most probably you don't have such hardware,
190 so it's safe to say "n" here.
193 prompt "Choice endianness support"
194 depends on FB_FOREIGN_ENDIAN
196 config FB_BOTH_ENDIAN
197 bool "Support for Big- and Little-Endian framebuffers"
200 bool "Support for Big-Endian framebuffers only"
202 config FB_LITTLE_ENDIAN
203 bool "Support for Little-Endian framebuffers only"
212 config FB_DEFERRED_IO
219 depends on FB_DEFERRED_IO
226 Common utility functions useful to fbdev drivers of VGA-based
237 select BACKLIGHT_LCD_SUPPORT
238 select BACKLIGHT_CLASS_DEVICE
241 config FB_MODE_HELPERS
242 bool "Enable Video Mode Handling Helpers"
246 This enables functions for handling video modes using the
247 Generalized Timing Formula and the EDID parser. A few drivers rely
248 on this feature such as the radeonfb, rivafb, and the i810fb. If
249 your driver does not take advantage of this feature, choosing Y will
250 just increase the kernel size by about 5K.
252 config FB_TILEBLITTING
253 bool "Enable Tile Blitting Support"
257 This enables tile blitting. Tile blitting is a drawing technique
258 where the screen is divided into rectangular sections (tiles), whereas
259 the standard blitting divides the screen into pixels. Because the
260 default drawing element is a tile, drawing functions will be passed
261 parameters in terms of number of tiles instead of number of pixels.
262 For example, to draw a single character, instead of using bitmaps,
263 an index to an array of bitmaps will be used. To clear or move a
264 rectangular section of a screen, the rectangle will be described in
265 terms of number of tiles in the x- and y-axis.
267 This is particularly important to one driver, matroxfb. If
270 comment "Frame buffer hardware drivers"
274 tristate "Aeroflex Gaisler framebuffer support"
275 depends on FB && SPARC
276 select FB_CFB_FILLRECT
277 select FB_CFB_COPYAREA
278 select FB_CFB_IMAGEBLIT
280 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
283 tristate "Cirrus Logic support"
284 depends on FB && (ZORRO || PCI)
285 select FB_CFB_FILLRECT
286 select FB_CFB_COPYAREA
287 select FB_CFB_IMAGEBLIT
289 This enables support for Cirrus Logic GD542x/543x based boards on
290 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
292 If you have a PCI-based system, this enables support for these
293 chips: GD-543x, GD-544x, GD-5480.
295 Please read the file <file:Documentation/fb/cirrusfb.txt>.
297 Say N unless you have such a graphics board or plan to get one
298 before you next recompile the kernel.
301 tristate "Permedia2 support"
302 depends on FB && ((AMIGA && BROKEN) || PCI)
303 select FB_CFB_FILLRECT
304 select FB_CFB_COPYAREA
305 select FB_CFB_IMAGEBLIT
307 This is the frame buffer device driver for cards based on
308 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
309 The driver was tested on the following cards:
310 Diamond FireGL 1000 PRO AGP
311 ELSA Gloria Synergy PCI
312 Appian Jeronimo PRO (both heads) PCI
313 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
314 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
315 ASK Graphic Blaster Exxtreme AGP
317 To compile this driver as a module, choose M here: the
318 module will be called pm2fb.
320 config FB_PM2_FIFO_DISCONNECT
321 bool "enable FIFO disconnect feature"
322 depends on FB_PM2 && PCI
324 Support the Permedia2 FIFO disconnect feature.
327 tristate "ARM PrimeCell PL110 support"
328 depends on ARM || ARM64 || COMPILE_TEST
329 depends on FB && ARM_AMBA
330 select FB_CFB_FILLRECT
331 select FB_CFB_COPYAREA
332 select FB_CFB_IMAGEBLIT
334 This framebuffer device driver is for the ARM PrimeCell PL110
335 Colour LCD controller. ARM PrimeCells provide the building
336 blocks for System on a Chip devices.
338 If you want to compile this as a module (=code which can be
339 inserted into and removed from the running kernel), say M
340 here and read <file:Documentation/kbuild/modules.txt>. The module
341 will be called amba-clcd.
344 tristate "ARM High Definition LCD support"
346 select FB_CFB_FILLRECT
347 select FB_CFB_COPYAREA
348 select FB_CFB_IMAGEBLIT
350 This framebuffer device driver is for the ARM High Definition
351 Colour LCD controller.
353 If you want to compile this as a module (=code which can be
354 inserted into and removed from the running kernel), say M
355 here and read <file:Documentation/kbuild/modules.txt>. The module
356 will be called arm-hdlcd.
359 bool "Acorn VIDC support"
360 depends on (FB = y) && ARM && ARCH_ACORN
361 select FB_CFB_FILLRECT
362 select FB_CFB_COPYAREA
363 select FB_CFB_IMAGEBLIT
365 This is the frame buffer device driver for the Acorn VIDC graphics
366 hardware found in Acorn RISC PCs and other ARM-based machines. If
370 bool "CLPS711X LCD support"
371 depends on (FB = y) && ARM && ARCH_CLPS711X
372 select FB_CFB_FILLRECT
373 select FB_CFB_COPYAREA
374 select FB_CFB_IMAGEBLIT
376 Say Y to enable the Framebuffer driver for the CLPS7111 and
380 bool "SA-1100 LCD support"
381 depends on (FB = y) && ARM && ARCH_SA1100
382 select FB_CFB_FILLRECT
383 select FB_CFB_COPYAREA
384 select FB_CFB_IMAGEBLIT
386 This is a framebuffer device for the SA-1100 LCD Controller.
387 See <http://www.linux-fbdev.org/> for information on framebuffer
390 If you plan to use the LCD display with your SA-1100 system, say
394 tristate "Freescale i.MX1/21/25/27 LCD support"
395 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
396 select FB_CFB_FILLRECT
397 select FB_CFB_COPYAREA
398 select FB_CFB_IMAGEBLIT
401 tristate "CyberPro 2000/2010/5000 support"
402 depends on FB && PCI && (BROKEN || !SPARC64)
403 select FB_CFB_FILLRECT
404 select FB_CFB_COPYAREA
405 select FB_CFB_IMAGEBLIT
407 This enables support for the Integraphics CyberPro 20x0 and 5000
408 VGA chips used in the Rebel.com Netwinder and other machines.
409 Say Y if you have a NetWinder or a graphics card containing this
410 device, otherwise say N.
412 config FB_CYBER2000_DDC
413 bool "DDC for CyberPro support"
414 depends on FB_CYBER2000
418 Say Y here if you want DDC support for your CyberPro graphics
419 card. This is only I2C bus support, driver does not use EDID.
421 config FB_CYBER2000_I2C
422 bool "CyberPro 2000/2010/5000 I2C support"
423 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
426 Enable support for the I2C video decoder interface on the
427 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
428 on the Netwinder machines for the SAA7111 video capture.
432 depends on (FB = y) && APOLLO
434 select FB_CFB_FILLRECT
435 select FB_CFB_IMAGEBLIT
439 depends on (FB = y) && Q40
441 select FB_CFB_FILLRECT
442 select FB_CFB_COPYAREA
443 select FB_CFB_IMAGEBLIT
446 tristate "Amiga native chipset support"
447 depends on FB && AMIGA
449 This is the frame buffer device driver for the builtin graphics
450 chipset found in Amigas.
452 To compile this driver as a module, choose M here: the
453 module will be called amifb.
456 bool "Amiga OCS chipset support"
459 This enables support for the original Agnus and Denise video chips,
460 found in the Amiga 1000 and most A500's and A2000's. If you intend
461 to run Linux on any of these systems, say Y; otherwise say N.
464 bool "Amiga ECS chipset support"
467 This enables support for the Enhanced Chip Set, found in later
468 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
469 you intend to run Linux on any of these systems, say Y; otherwise
473 bool "Amiga AGA chipset support"
476 This enables support for the Advanced Graphics Architecture (also
477 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
478 and CD32. If you intend to run Linux on any of these systems, say Y;
482 bool "Amiga FrameMaster II/Rainbow II support"
483 depends on (FB = y) && ZORRO
484 select FB_CFB_FILLRECT
485 select FB_CFB_COPYAREA
486 select FB_CFB_IMAGEBLIT
488 This is the frame buffer device driver for the Amiga FrameMaster
489 card from BSC (exhibited 1992 but not shipped as a CBM product).
492 tristate "Arc Monochrome LCD board support"
494 select FB_SYS_FILLRECT
495 select FB_SYS_COPYAREA
496 select FB_SYS_IMAGEBLIT
499 This enables support for the Arc Monochrome LCD board. The board
500 is based on the KS-108 lcd controller and is typically a matrix
501 of 2*n chips. This driver was tested with a 128x64 panel. This
502 driver supports it for use with x86 SBCs through a 16 bit GPIO
503 interface (8 bit data, 8 bit control). If you anticipate using
504 this driver, say Y or M; otherwise say N. You must specify the
505 GPIO IO address to be used for setting control and data.
508 bool "Atari native chipset support"
509 depends on (FB = y) && ATARI
510 select FB_CFB_FILLRECT
511 select FB_CFB_COPYAREA
512 select FB_CFB_IMAGEBLIT
514 This is the frame buffer device driver for the builtin graphics
515 chipset found in Ataris.
518 bool "Open Firmware frame buffer device support"
519 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
520 select FB_CFB_FILLRECT
521 select FB_CFB_COPYAREA
522 select FB_CFB_IMAGEBLIT
525 Say Y if you want support with Open Firmware for your graphics
529 bool "Apple \"control\" display support"
530 depends on (FB = y) && PPC_PMAC && PPC32
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
536 This driver supports a frame buffer for the graphics adapter in the
537 Power Macintosh 7300 and others.
540 bool "Apple \"platinum\" display support"
541 depends on (FB = y) && PPC_PMAC && PPC32
542 select FB_CFB_FILLRECT
543 select FB_CFB_COPYAREA
544 select FB_CFB_IMAGEBLIT
547 This driver supports a frame buffer for the "platinum" graphics
548 adapter in some Power Macintoshes.
551 bool "Apple \"valkyrie\" display support"
552 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
558 This driver supports a frame buffer for the "valkyrie" graphics
559 adapter in some Power Macintoshes.
562 bool "Chips 65550 display support"
563 depends on (FB = y) && PPC32 && PCI
564 select FB_CFB_FILLRECT
565 select FB_CFB_COPYAREA
566 select FB_CFB_IMAGEBLIT
568 This is the frame buffer device driver for the Chips & Technologies
569 65550 graphics chip in PowerBooks.
572 bool "Asiliant (Chips) 69000 display support"
573 depends on (FB = y) && PCI
574 select FB_CFB_FILLRECT
575 select FB_CFB_COPYAREA
576 select FB_CFB_IMAGEBLIT
578 This is the frame buffer device driver for the Asiliant 69030 chipset
581 bool "IMS Twin Turbo display support"
582 depends on (FB = y) && PCI
583 select FB_CFB_IMAGEBLIT
584 select FB_MACMODES if PPC
586 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
587 many Macintosh and compatible computers.
590 tristate "VGA 16-color graphics support"
591 depends on FB && (X86 || PPC)
592 select FB_CFB_FILLRECT
593 select FB_CFB_COPYAREA
594 select FB_CFB_IMAGEBLIT
596 select FONT_8x16 if FRAMEBUFFER_CONSOLE
598 This is the frame buffer device driver for VGA 16 color graphic
599 cards. Say Y if you have such a card.
601 To compile this driver as a module, choose M here: the
602 module will be called vga16fb.
604 config FB_BF54X_LQ043
605 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
606 depends on FB && (BF54x) && !BF542
607 select FB_CFB_FILLRECT
608 select FB_CFB_COPYAREA
609 select FB_CFB_IMAGEBLIT
611 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
613 config FB_BFIN_T350MCQB
614 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
615 depends on FB && BLACKFIN
617 select FB_CFB_FILLRECT
618 select FB_CFB_COPYAREA
619 select FB_CFB_IMAGEBLIT
621 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
622 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
623 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
625 config FB_BFIN_LQ035Q1
626 tristate "SHARP LQ035Q1DH02 TFT LCD"
627 depends on FB && BLACKFIN && SPI
628 select FB_CFB_FILLRECT
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
633 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
634 the Blackfin Landscape LCD EZ-Extender Card.
635 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
636 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
638 To compile this driver as a module, choose M here: the
639 module will be called bfin-lq035q1-fb.
641 config FB_BF537_LQ035
642 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
643 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
644 select FB_CFB_FILLRECT
645 select FB_CFB_COPYAREA
646 select FB_CFB_IMAGEBLIT
649 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
652 To compile this driver as a module, choose M here: the
653 module will be called bf537-lq035.
656 tristate "Blackfin ADV7393 Video encoder"
657 depends on FB && BLACKFIN
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
663 This is the framebuffer device for a ADV7393 video encoder
664 attached to a Blackfin on the PPI port.
665 If your Blackfin board has a ADV7393 select Y.
667 To compile this driver as a module, choose M here: the
668 module will be called bfin_adv7393fb.
671 prompt "Video mode support"
672 depends on FB_BFIN_7393
682 bool 'NTSC 640x480 (Experimental)'
685 bool 'PAL 640x480 (Experimental)'
688 bool 'NTSC 720x480 YCbCR input'
691 bool 'PAL 720x576 YCbCR input'
696 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
697 depends on (FB_BFIN_7393)
698 default ADV7393_1XMEM
708 tristate "HP STI frame buffer device support"
709 depends on FB && PARISC
710 select FB_CFB_FILLRECT
711 select FB_CFB_COPYAREA
712 select FB_CFB_IMAGEBLIT
717 STI refers to the HP "Standard Text Interface" which is a set of
718 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
719 Enabling this option will implement the linux framebuffer device
720 using calls to the STI BIOS routines for initialisation.
722 If you enable this option, you will get a planar framebuffer device
723 /dev/fb which will work on the most common HP graphic cards of the
724 NGLE family, including the artist chips (in the 7xx and Bxxx series),
725 HCRX, HCRX24, CRX, CRX24 and VisEG series.
727 It is safe to enable this option, so you should probably say "Y".
730 bool "Generic Macintosh display support"
731 depends on (FB = y) && MAC
732 select FB_CFB_FILLRECT
733 select FB_CFB_COPYAREA
734 select FB_CFB_IMAGEBLIT
739 depends on (FB = y) && DIO
740 select FB_CFB_IMAGEBLIT
744 tristate "TGA/SFB+ framebuffer support"
745 depends on FB && (ALPHA || TC)
746 select FB_CFB_FILLRECT
747 select FB_CFB_COPYAREA
748 select FB_CFB_IMAGEBLIT
751 This is the frame buffer device driver for generic TGA and SFB+
752 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
753 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
754 TURBOchannel cards, also known as PMAGD-A, -B and -C.
756 Due to hardware limitations ZLX-E2 and E3 cards are not supported
757 for DECstation 5000/200 systems. Additionally due to firmware
758 limitations these cards may cause troubles with booting DECstation
759 5000/240 and /260 systems, but are fully supported under Linux if
760 you manage to get it going. ;-)
762 Say Y if you have one of those.
765 tristate "Userspace VESA VGA graphics support"
766 depends on FB && CONNECTOR
767 select FB_CFB_FILLRECT
768 select FB_CFB_COPYAREA
769 select FB_CFB_IMAGEBLIT
770 select FB_MODE_HELPERS
772 This is the frame buffer driver for generic VBE 2.0 compliant
773 graphic cards. It can also take advantage of VBE 3.0 features,
774 such as refresh rate adjustment.
776 This driver generally provides more features than vesafb but
777 requires a userspace helper application called 'v86d'. See
778 <file:Documentation/fb/uvesafb.txt> for more information.
783 bool "VESA VGA graphics support"
784 depends on (FB = y) && X86
785 select FB_CFB_FILLRECT
786 select FB_CFB_COPYAREA
787 select FB_CFB_IMAGEBLIT
788 select FB_BOOT_VESA_SUPPORT
790 This is the frame buffer device driver for generic VESA 2.0
791 compliant graphic cards. The older VESA 1.2 cards are not supported.
792 You will get a boot time penguin logo at no additional cost. Please
793 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
796 bool "EFI-based Framebuffer Support"
797 depends on (FB = y) && X86 && EFI
798 select FB_CFB_FILLRECT
799 select FB_CFB_COPYAREA
800 select FB_CFB_IMAGEBLIT
802 This is the EFI frame buffer device driver. If the firmware on
803 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
804 using the EFI framebuffer as your console.
807 tristate "N411 Apollo/Hecuba devkit support"
808 depends on FB && X86 && MMU
809 select FB_SYS_FILLRECT
810 select FB_SYS_COPYAREA
811 select FB_SYS_IMAGEBLIT
813 select FB_DEFERRED_IO
816 This enables support for the Apollo display controller in its
817 Hecuba form using the n411 devkit.
820 tristate "Hercules mono graphics support"
823 Say Y here if you have a Hercules mono graphics card.
825 To compile this driver as a module, choose M here: the
826 module will be called hgafb.
828 As this card technology is at least 25 years old,
829 most people will answer N here.
832 tristate "SGI Visual Workstation framebuffer support"
833 depends on FB && X86_VISWS
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 SGI Visual Workstation support for framebuffer graphics.
841 bool "SGI Graphics Backend frame buffer support"
842 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
843 select FB_CFB_FILLRECT
844 select FB_CFB_COPYAREA
845 select FB_CFB_IMAGEBLIT
847 This is the frame buffer device driver for SGI Graphics Backend.
848 This chip is used in SGI O2 and Visual Workstation 320/540.
851 int "Video memory size in MB"
855 This is the amount of memory reserved for the framebuffer,
856 which can be any value between 1MB and 8MB.
859 bool "SBUS and UPA framebuffers"
860 depends on (FB = y) && SPARC
862 Say Y if you want support for SBUS or UPA based frame buffer device.
866 depends on (FB = y) && (SPARC && FB_SBUS)
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 BWtwo frame buffer.
874 bool "CGthree support"
875 depends on (FB = y) && (SPARC && FB_SBUS)
876 select FB_CFB_FILLRECT
877 select FB_CFB_COPYAREA
878 select FB_CFB_IMAGEBLIT
880 This is the frame buffer device driver for the CGthree frame buffer.
883 bool "CGsix (GX,TurboGX) support"
884 depends on (FB = y) && (SPARC && FB_SBUS)
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 This is the frame buffer device driver for the CGsix (GX, TurboGX)
892 bool "Creator/Creator3D/Elite3D support"
893 depends on FB_SBUS && SPARC64
894 select FB_CFB_COPYAREA
895 select FB_CFB_IMAGEBLIT
897 This is the frame buffer device driver for the Creator, Creator3D,
898 and Elite3D graphics boards.
901 bool "TCX (SS4/SS5 only) support"
903 select FB_CFB_FILLRECT
904 select FB_CFB_COPYAREA
905 select FB_CFB_IMAGEBLIT
907 This is the frame buffer device driver for the TCX 24/8bit frame
911 bool "CGfourteen (SX) support"
913 select FB_CFB_FILLRECT
914 select FB_CFB_COPYAREA
915 select FB_CFB_IMAGEBLIT
917 This is the frame buffer device driver for the CGfourteen frame
918 buffer on Desktop SPARCsystems with the SX graphics option.
921 bool "P9100 (Sparcbook 3 only) support"
923 select FB_CFB_FILLRECT
924 select FB_CFB_COPYAREA
925 select FB_CFB_IMAGEBLIT
927 This is the frame buffer device driver for the P9100 card
928 supported on Sparcbook 3 machines.
931 bool "Leo (ZX) support"
933 select FB_CFB_FILLRECT
934 select FB_CFB_COPYAREA
935 select FB_CFB_IMAGEBLIT
937 This is the frame buffer device driver for the SBUS-based Sun ZX
938 (leo) frame buffer cards.
941 bool "IGA 168x display support"
942 depends on (FB = y) && SPARC32
943 select FB_CFB_FILLRECT
944 select FB_CFB_COPYAREA
945 select FB_CFB_IMAGEBLIT
947 This is the framebuffer device for the INTERGRAPHICS 1680 and
948 successor frame buffer cards.
951 bool "Sun XVR-500 3DLABS Wildcat support"
952 depends on (FB = y) && PCI && SPARC64
953 select FB_CFB_FILLRECT
954 select FB_CFB_COPYAREA
955 select FB_CFB_IMAGEBLIT
957 This is the framebuffer device for the Sun XVR-500 and similar
958 graphics cards based upon the 3DLABS Wildcat chipset. The driver
959 only works on sparc64 systems where the system firmware has
960 mostly initialized the card already. It is treated as a
961 completely dumb framebuffer device.
964 bool "Sun XVR-2500 3DLABS Wildcat support"
965 depends on (FB = y) && PCI && SPARC64
966 select FB_CFB_FILLRECT
967 select FB_CFB_COPYAREA
968 select FB_CFB_IMAGEBLIT
970 This is the framebuffer device for the Sun XVR-2500 and similar
971 graphics cards based upon the 3DLABS Wildcat chipset. The driver
972 only works on sparc64 systems where the system firmware has
973 mostly initialized the card already. It is treated as a
974 completely dumb framebuffer device.
977 bool "Sun XVR-1000 support"
978 depends on (FB = y) && SPARC64
979 select FB_CFB_FILLRECT
980 select FB_CFB_COPYAREA
981 select FB_CFB_IMAGEBLIT
983 This is the framebuffer device for the Sun XVR-1000 and similar
984 graphics cards. The driver only works on sparc64 systems where
985 the system firmware has mostly initialized the card already. It
986 is treated as a completely dumb framebuffer device.
989 tristate "NEC PowerVR 2 display support"
990 depends on FB && SH_DREAMCAST
991 select FB_CFB_FILLRECT
992 select FB_CFB_COPYAREA
993 select FB_CFB_IMAGEBLIT
995 Say Y here if you have a PowerVR 2 card in your box. If you plan to
996 run linux on your Dreamcast, you will have to say Y here.
997 This driver may or may not work on other PowerVR 2 cards, but is
998 totally untested. Use at your own risk. If unsure, say N.
1000 To compile this driver as a module, choose M here: the
1001 module will be called pvr2fb.
1003 You can pass several parameters to the driver at boot time or at
1004 module load time. The parameters look like "video=pvr2:XXX", where
1005 the meaning of XXX can be found at the end of the main source file
1006 (<file:drivers/video/pvr2fb.c>). Please see the file
1007 <file:Documentation/fb/pvr2fb.txt>.
1010 tristate "Epson S1D13XXX framebuffer support"
1012 select FB_CFB_FILLRECT
1013 select FB_CFB_COPYAREA
1014 select FB_CFB_IMAGEBLIT
1016 Support for S1D13XXX framebuffer device family (currently only
1017 working with S1D13806). Product specs at
1018 <http://vdc.epson.com/>
1021 tristate "AT91/AT32 LCD Controller support"
1022 depends on FB && HAVE_FB_ATMEL
1023 select FB_CFB_FILLRECT
1024 select FB_CFB_COPYAREA
1025 select FB_CFB_IMAGEBLIT
1027 This enables support for the AT91/AT32 LCD Controller.
1030 bool "Frame Buffer in internal SRAM"
1031 depends on FB_ATMEL && ARCH_AT91SAM9261
1033 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1034 to let frame buffer in external SDRAM.
1037 bool "Use a STN display with AT91/AT32 LCD Controller"
1038 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1041 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1042 Controller. Say N if you want to connect a TFT.
1047 tristate "nVidia Framebuffer Support"
1048 depends on FB && PCI
1049 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1050 select FB_MODE_HELPERS
1051 select FB_CFB_FILLRECT
1052 select FB_CFB_COPYAREA
1053 select FB_CFB_IMAGEBLIT
1057 This driver supports graphics boards with the nVidia chips, TNT
1058 and newer. For very old chipsets, such as the RIVA128, then use
1060 Say Y if you have such a graphics board.
1062 To compile this driver as a module, choose M here: the
1063 module will be called nvidiafb.
1065 config FB_NVIDIA_I2C
1066 bool "Enable DDC Support"
1067 depends on FB_NVIDIA
1070 This enables I2C support for nVidia Chipsets. This is used
1071 only for getting EDID information from the attached display
1072 allowing for robust video mode handling and switching.
1074 Because fbdev-2.6 requires that drivers must be able to
1075 independently validate video mode parameters, you should say Y
1078 config FB_NVIDIA_DEBUG
1079 bool "Lots of debug output"
1080 depends on FB_NVIDIA
1083 Say Y here if you want the nVidia driver to output all sorts
1084 of debugging information to provide to the maintainer when
1085 something goes wrong.
1087 config FB_NVIDIA_BACKLIGHT
1088 bool "Support for backlight control"
1089 depends on FB_NVIDIA
1092 Say Y here if you want to control the backlight of your display.
1095 tristate "nVidia Riva support"
1096 depends on FB && PCI
1097 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1098 select FB_MODE_HELPERS
1099 select FB_CFB_FILLRECT
1100 select FB_CFB_COPYAREA
1101 select FB_CFB_IMAGEBLIT
1105 This driver supports graphics boards with the nVidia Riva/Geforce
1107 Say Y if you have such a graphics board.
1109 To compile this driver as a module, choose M here: the
1110 module will be called rivafb.
1113 bool "Enable DDC Support"
1117 This enables I2C support for nVidia Chipsets. This is used
1118 only for getting EDID information from the attached display
1119 allowing for robust video mode handling and switching.
1121 Because fbdev-2.6 requires that drivers must be able to
1122 independently validate video mode parameters, you should say Y
1125 config FB_RIVA_DEBUG
1126 bool "Lots of debug output"
1130 Say Y here if you want the Riva driver to output all sorts
1131 of debugging information to provide to the maintainer when
1132 something goes wrong.
1134 config FB_RIVA_BACKLIGHT
1135 bool "Support for backlight control"
1139 Say Y here if you want to control the backlight of your display.
1142 tristate "Intel740 support"
1143 depends on FB && PCI
1144 select FB_MODE_HELPERS
1145 select FB_CFB_FILLRECT
1146 select FB_CFB_COPYAREA
1147 select FB_CFB_IMAGEBLIT
1151 This driver supports graphics cards based on Intel740 chip.
1154 tristate "Intel 810/815 support"
1155 depends on FB && PCI && X86_32 && AGP_INTEL
1156 select FB_MODE_HELPERS
1157 select FB_CFB_FILLRECT
1158 select FB_CFB_COPYAREA
1159 select FB_CFB_IMAGEBLIT
1162 This driver supports the on-board graphics built in to the Intel 810
1163 and 815 chipsets. Say Y if you have and plan to use such a board.
1165 To compile this driver as a module, choose M here: the
1166 module will be called i810fb.
1168 For more information, please read
1169 <file:Documentation/fb/intel810.txt>
1172 bool "use VESA Generalized Timing Formula"
1175 If you say Y, then the VESA standard, Generalized Timing Formula
1176 or GTF, will be used to calculate the required video timing values
1177 per video mode. Since the GTF allows nondiscrete timings
1178 (nondiscrete being a range of values as opposed to discrete being a
1179 set of values), you'll be able to use any combination of horizontal
1180 and vertical resolutions, and vertical refresh rates without having
1181 to specify your own timing parameters. This is especially useful
1182 to maximize the performance of an aging display, or if you just
1183 have a display with nonstandard dimensions. A VESA compliant
1184 monitor is recommended, but can still work with non-compliant ones.
1185 If you need or want this, then select this option. The timings may
1186 not be compliant with Intel's recommended values. Use at your own
1189 If you say N, the driver will revert to discrete video timings
1190 using a set recommended by Intel in their documentation.
1195 bool "Enable DDC Support"
1196 depends on FB_I810 && FB_I810_GTF
1201 tristate "Intel LE80578 (Vermilion) support"
1202 depends on FB && PCI && X86
1203 select FB_MODE_HELPERS
1204 select FB_CFB_FILLRECT
1205 select FB_CFB_COPYAREA
1206 select FB_CFB_IMAGEBLIT
1208 This driver supports the LE80578 (Vermilion Range) chipset
1210 config FB_CARILLO_RANCH
1211 tristate "Intel Carillo Ranch support"
1212 depends on FB_LE80578 && FB && PCI && X86
1214 This driver supports the LE80578 (Carillo Ranch) board
1217 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1218 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1219 select FB_MODE_HELPERS
1220 select FB_CFB_FILLRECT
1221 select FB_CFB_COPYAREA
1222 select FB_CFB_IMAGEBLIT
1223 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1224 depends on !DRM_I915
1226 This driver supports the on-board graphics built in to the Intel
1227 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1228 Say Y if you have and plan to use such a board.
1230 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1232 To compile this driver as a module, choose M here: the
1233 module will be called intelfb.
1235 For more information, please read <file:Documentation/fb/intelfb.txt>
1237 config FB_INTEL_DEBUG
1238 bool "Intel driver Debug Messages"
1241 Say Y here if you want the Intel driver to output all sorts
1242 of debugging information to provide to the maintainer when
1243 something goes wrong.
1246 bool "DDC/I2C for Intel framebuffer support"
1251 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1254 tristate "Matrox acceleration"
1255 depends on FB && PCI
1256 select FB_CFB_FILLRECT
1257 select FB_CFB_COPYAREA
1258 select FB_CFB_IMAGEBLIT
1259 select FB_TILEBLITTING
1260 select FB_MACMODES if PPC_PMAC
1262 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1263 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1264 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1265 Matrox G400, G450 or G550 card in your box.
1267 To compile this driver as a module, choose M here: the
1268 module will be called matroxfb.
1270 You can pass several parameters to the driver at boot time or at
1271 module load time. The parameters look like "video=matroxfb:XXX", and
1272 are described in <file:Documentation/fb/matroxfb.txt>.
1274 config FB_MATROX_MILLENIUM
1275 bool "Millennium I/II support"
1276 depends on FB_MATROX
1278 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1279 video card. If you select "Advanced lowlevel driver options" below,
1280 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1281 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1282 also use font widths different from 8.
1284 config FB_MATROX_MYSTIQUE
1285 bool "Mystique support"
1286 depends on FB_MATROX
1288 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1289 video card. If you select "Advanced lowlevel driver options" below,
1290 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1291 packed pixel and 32 bpp packed pixel. You can also use font widths
1295 bool "G100/G200/G400/G450/G550 support"
1296 depends on FB_MATROX
1298 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1299 video card. If you select "Advanced lowlevel driver options", you
1300 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1301 pixel and 32 bpp packed pixel. You can also use font widths
1304 If you need support for G400 secondary head, you must say Y to
1305 "Matrox I2C support" and "G400 second head support" right below.
1306 G450/G550 secondary head and digital output are supported without
1309 The driver starts in monitor mode. You must use the matroxset tool
1310 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1311 swap primary and secondary head outputs, or to change output mode.
1312 Secondary head driver always start in 640x480 resolution and you
1313 must use fbset to change it.
1315 Do not forget that second head supports only 16 and 32 bpp
1316 packed pixels, so it is a good idea to compile them into the kernel
1317 too. You can use only some font widths, as the driver uses generic
1318 painting procedures (the secondary head does not use acceleration
1321 G450/G550 hardware can display TV picture only from secondary CRTC,
1322 and it performs no scaling, so picture must have 525 or 625 lines.
1324 config FB_MATROX_I2C
1325 tristate "Matrox I2C support"
1326 depends on FB_MATROX
1329 This drivers creates I2C buses which are needed for accessing the
1330 DDC (I2C) bus present on all Matroxes, an I2C bus which
1331 interconnects Matrox optional devices, like MGA-TVO on G200 and
1332 G400, and the secondary head DDC bus, present on G400 only.
1334 You can say Y or M here if you want to experiment with monitor
1335 detection code. You must say Y or M here if you want to use either
1336 second head of G400 or MGA-TVO on G200 or G400.
1338 If you compile it as module, it will create a module named
1341 config FB_MATROX_MAVEN
1342 tristate "G400 second head support"
1343 depends on FB_MATROX_G && FB_MATROX_I2C
1345 WARNING !!! This support does not work with G450 !!!
1347 Say Y or M here if you want to use a secondary head (meaning two
1348 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1349 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1350 secondary head output is blanked while you are in X. With XFree
1351 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1352 the fbdev driver on first head and the fbdev driver on second head.
1354 If you compile it as module, two modules are created,
1355 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1356 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1357 also load i2c-matroxfb to get it to run.
1359 The driver starts in monitor mode and you must use the matroxset
1361 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1362 PAL or NTSC or to swap primary and secondary head outputs.
1363 Secondary head driver also always start in 640x480 resolution, you
1364 must use fbset to change it.
1366 Also do not forget that second head supports only 16 and 32 bpp
1367 packed pixels, so it is a good idea to compile them into the kernel
1368 too. You can use only some font widths, as the driver uses generic
1369 painting procedures (the secondary head does not use acceleration
1373 tristate "ATI Radeon display support"
1374 depends on FB && PCI
1375 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1376 select FB_MODE_HELPERS
1377 select FB_CFB_FILLRECT
1378 select FB_CFB_COPYAREA
1379 select FB_CFB_IMAGEBLIT
1380 select FB_MACMODES if PPC_OF
1382 Choose this option if you want to use an ATI Radeon graphics card as
1383 a framebuffer device. There are both PCI and AGP versions. You
1384 don't need to choose this to run the Radeon in plain VGA mode.
1386 There is a product page at
1387 http://products.amd.com/en-us/GraphicCardResult.aspx
1389 config FB_RADEON_I2C
1390 bool "DDC/I2C for ATI Radeon support"
1391 depends on FB_RADEON
1395 Say Y here if you want DDC/I2C support for your Radeon board.
1397 config FB_RADEON_BACKLIGHT
1398 bool "Support for backlight control"
1399 depends on FB_RADEON
1402 Say Y here if you want to control the backlight of your display.
1404 config FB_RADEON_DEBUG
1405 bool "Lots of debug output from Radeon driver"
1406 depends on FB_RADEON
1409 Say Y here if you want the Radeon driver to output all sorts
1410 of debugging information to provide to the maintainer when
1411 something goes wrong.
1414 tristate "ATI Rage128 display support"
1415 depends on FB && PCI
1416 select FB_CFB_FILLRECT
1417 select FB_CFB_COPYAREA
1418 select FB_CFB_IMAGEBLIT
1419 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1420 select FB_MACMODES if PPC_PMAC
1422 This driver supports graphics boards with the ATI Rage128 chips.
1423 Say Y if you have such a graphics board and read
1424 <file:Documentation/fb/aty128fb.txt>.
1426 To compile this driver as a module, choose M here: the
1427 module will be called aty128fb.
1429 config FB_ATY128_BACKLIGHT
1430 bool "Support for backlight control"
1431 depends on FB_ATY128
1434 Say Y here if you want to control the backlight of your display.
1437 tristate "ATI Mach64 display support" if PCI || ATARI
1438 depends on FB && !SPARC32
1439 select FB_CFB_FILLRECT
1440 select FB_CFB_COPYAREA
1441 select FB_CFB_IMAGEBLIT
1442 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1443 select FB_MACMODES if PPC
1445 This driver supports graphics boards with the ATI Mach64 chips.
1446 Say Y if you have such a graphics board.
1448 To compile this driver as a module, choose M here: the
1449 module will be called atyfb.
1452 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1453 depends on PCI && FB_ATY
1454 default y if SPARC64 && PCI
1456 Say Y here to support use of ATI's 64-bit Rage boards (or other
1457 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1458 framebuffer device. The ATI product support page for these boards
1459 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1461 config FB_ATY_GENERIC_LCD
1462 bool "Mach64 generic LCD support"
1463 depends on FB_ATY_CT
1465 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1466 Rage XC, or Rage XL chipset.
1469 bool "Mach64 GX support" if PCI
1473 Say Y here to support use of the ATI Mach64 Graphics Expression
1474 board (or other boards based on the Mach64 GX chipset) as a
1475 framebuffer device. The ATI product support page for these boards
1477 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1479 config FB_ATY_BACKLIGHT
1480 bool "Support for backlight control"
1484 Say Y here if you want to control the backlight of your display.
1487 tristate "S3 Trio/Virge support"
1488 depends on FB && PCI
1489 select FB_CFB_FILLRECT
1490 select FB_CFB_COPYAREA
1491 select FB_CFB_IMAGEBLIT
1492 select FB_TILEBLITTING
1495 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1497 Driver for graphics boards with S3 Trio / S3 Virge chip.
1500 bool "DDC for S3 support"
1505 Say Y here if you want DDC support for your S3 graphics card.
1508 tristate "S3 Savage support"
1509 depends on FB && PCI
1510 select FB_MODE_HELPERS
1511 select FB_CFB_FILLRECT
1512 select FB_CFB_COPYAREA
1513 select FB_CFB_IMAGEBLIT
1516 This driver supports notebooks and computers with S3 Savage PCI/AGP
1519 Say Y if you have such a graphics card.
1521 To compile this driver as a module, choose M here; the module
1522 will be called savagefb.
1524 config FB_SAVAGE_I2C
1525 bool "Enable DDC2 Support"
1526 depends on FB_SAVAGE
1529 This enables I2C support for S3 Savage Chipsets. This is used
1530 only for getting EDID information from the attached display
1531 allowing for robust video mode handling and switching.
1533 Because fbdev-2.6 requires that drivers must be able to
1534 independently validate video mode parameters, you should say Y
1537 config FB_SAVAGE_ACCEL
1538 bool "Enable Console Acceleration"
1539 depends on FB_SAVAGE
1542 This option will compile in console acceleration support. If
1543 the resulting framebuffer console has bothersome glitches, then
1547 tristate "SiS/XGI display support"
1548 depends on FB && PCI
1549 select FB_CFB_FILLRECT
1550 select FB_CFB_COPYAREA
1551 select FB_CFB_IMAGEBLIT
1552 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1554 This is the frame buffer device driver for the SiS 300, 315, 330
1555 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1556 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1558 To compile this driver as a module, choose M here; the module
1559 will be called sisfb.
1562 bool "SiS 300 series support"
1565 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1568 bool "SiS 315/330/340 series and XGI support"
1571 Say Y here to support use of the SiS 315, 330 and 340 series
1572 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1573 as XGI V3XT, V5, V8 and Z7.
1576 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1577 depends on FB && PCI && X86
1578 select FB_CFB_FILLRECT
1579 select FB_CFB_COPYAREA
1580 select FB_CFB_IMAGEBLIT
1585 This is the frame buffer device driver for Graphics chips of VIA
1586 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1587 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1589 Say Y if you have a VIA UniChrome graphics board.
1591 To compile this driver as a module, choose M here: the
1592 module will be called viafb.
1596 config FB_VIA_DIRECT_PROCFS
1597 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1601 Allow direct hardware access to some output registers via procfs.
1602 This is dangerous but may provide the only chance to get the
1603 correct output device configuration.
1604 Its use is strongly discouraged.
1606 config FB_VIA_X_COMPATIBILITY
1607 bool "X server compatibility"
1611 This option reduces the functionality (power saving, ...) of the
1612 framebuffer to avoid negative impact on the OpenChrome X server.
1613 If you use any X server other than fbdev you should enable this
1614 otherwise it should be safe to disable it and allow using all
1620 tristate "NeoMagic display support"
1621 depends on FB && PCI
1622 select FB_MODE_HELPERS
1623 select FB_CFB_FILLRECT
1624 select FB_CFB_COPYAREA
1625 select FB_CFB_IMAGEBLIT
1628 This driver supports notebooks with NeoMagic PCI chips.
1629 Say Y if you have such a graphics card.
1631 To compile this driver as a module, choose M here: the
1632 module will be called neofb.
1635 tristate "IMG Kyro support"
1636 depends on FB && PCI
1637 select FB_CFB_FILLRECT
1638 select FB_CFB_COPYAREA
1639 select FB_CFB_IMAGEBLIT
1641 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1644 To compile this driver as a module, choose M here: the
1645 module will be called kyrofb.
1648 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1649 depends on FB && PCI
1650 select FB_CFB_IMAGEBLIT
1651 select FB_CFB_FILLRECT
1652 select FB_CFB_COPYAREA
1653 select FB_MODE_HELPERS
1655 This driver supports graphics boards with the 3Dfx Banshee,
1656 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1657 such a graphics board.
1659 To compile this driver as a module, choose M here: the
1660 module will be called tdfxfb.
1662 config FB_3DFX_ACCEL
1663 bool "3Dfx Acceleration functions"
1666 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1667 device driver with acceleration functions.
1670 bool "Enable DDC/I2C support"
1675 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1678 tristate "3Dfx Voodoo Graphics (sst1) support"
1679 depends on FB && PCI
1680 select FB_CFB_FILLRECT
1681 select FB_CFB_COPYAREA
1682 select FB_CFB_IMAGEBLIT
1684 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1685 Voodoo2 (cvg) based graphics card.
1687 To compile this driver as a module, choose M here: the
1688 module will be called sstfb.
1690 WARNING: Do not use any application that uses the 3D engine
1691 (namely glide) while using this driver.
1692 Please read the <file:Documentation/fb/sstfb.txt> for supported
1693 options and other important info support.
1696 tristate "VIA VT8623 support"
1697 depends on FB && PCI
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1701 select FB_TILEBLITTING
1704 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1706 Driver for CastleRock integrated graphics core in the
1707 VIA VT8623 [Apollo CLE266] chipset.
1710 tristate "Trident/CyberXXX/CyberBlade support"
1711 depends on FB && PCI
1712 select FB_CFB_FILLRECT
1713 select FB_CFB_COPYAREA
1714 select FB_CFB_IMAGEBLIT
1716 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1717 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1719 There are also integrated versions of these chips called CyberXXXX,
1720 CyberImage or CyberBlade. These chips are mostly found in laptops
1721 but also on some motherboards including early VIA EPIA motherboards.
1722 For more information, read <file:Documentation/fb/tridentfb.txt>
1724 Say Y if you have such a graphics board.
1726 To compile this driver as a module, choose M here: the
1727 module will be called tridentfb.
1730 tristate "ARK 2000PV support"
1731 depends on FB && PCI
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1735 select FB_TILEBLITTING
1738 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1740 Driver for PCI graphics boards with ARK 2000PV chip
1741 and ICS 5342 RAMDAC.
1744 tristate "Permedia3 support"
1745 depends on FB && PCI
1746 select FB_CFB_FILLRECT
1747 select FB_CFB_COPYAREA
1748 select FB_CFB_IMAGEBLIT
1750 This is the frame buffer device driver for the 3DLabs Permedia3
1751 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1752 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1753 and maybe other boards.
1756 tristate "Fujitsu carmine frame buffer support"
1757 depends on FB && PCI
1758 select FB_CFB_FILLRECT
1759 select FB_CFB_COPYAREA
1760 select FB_CFB_IMAGEBLIT
1762 This is the frame buffer device driver for the Fujitsu Carmine chip.
1763 The driver provides two independent frame buffer devices.
1766 depends on FB_CARMINE
1767 prompt "DRAM timing"
1768 default FB_CARMINE_DRAM_EVAL
1770 config FB_CARMINE_DRAM_EVAL
1771 bool "Eval board timings"
1773 Use timings which work on the eval card.
1775 config CARMINE_DRAM_CUSTOM
1776 bool "Custom board timings"
1778 Use custom board timings.
1782 bool "Au1100 LCD Driver"
1783 depends on (FB = y) && MIPS_ALCHEMY
1784 select FB_CFB_FILLRECT
1785 select FB_CFB_COPYAREA
1786 select FB_CFB_IMAGEBLIT
1788 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1789 various panels and CRTs by passing in kernel cmd line option
1790 au1100fb:panel=<name>.
1793 bool "Au1200/Au1300 LCD Driver"
1794 depends on (FB = y) && MIPS_ALCHEMY
1795 select FB_SYS_FILLRECT
1796 select FB_SYS_COPYAREA
1797 select FB_SYS_IMAGEBLIT
1800 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1801 It can drive various panels and CRTs by passing in kernel cmd line
1802 option au1200fb:panel=<name>.
1805 bool "VIA VT8500 framebuffer support"
1806 depends on (FB = y) && ARM && ARCH_VT8500
1807 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1808 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1809 select FB_SYS_IMAGEBLIT
1810 select FB_MODE_HELPERS
1811 select VIDEOMODE_HELPERS
1813 This is the framebuffer driver for VIA VT8500 integrated LCD
1817 bool "Wondermedia WM8xxx-series frame buffer support"
1818 depends on (FB = y) && ARM && ARCH_VT8500
1819 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1820 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1821 select FB_SYS_IMAGEBLIT
1822 select FB_MODE_HELPERS
1823 select VIDEOMODE_HELPERS
1825 This is the framebuffer driver for WonderMedia WM8xxx-series
1826 integrated LCD controller. This driver covers the WM8505, WM8650
1829 config FB_WMT_GE_ROPS
1830 bool "VT8500/WM8xxx accelerated raster ops support"
1831 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1834 This adds support for accelerated raster operations on the
1835 VIA VT8500 and Wondermedia 85xx series SoCs.
1837 source "drivers/video/geode/Kconfig"
1840 tristate "HD64461 Frame Buffer support"
1841 depends on FB && HD64461
1842 select FB_CFB_FILLRECT
1843 select FB_CFB_COPYAREA
1844 select FB_CFB_IMAGEBLIT
1846 This is the frame buffer device driver for the Hitachi HD64461 LCD
1850 bool "PMAG-AA TURBOchannel framebuffer support"
1851 depends on (FB = y) && TC
1852 select FB_CFB_FILLRECT
1853 select FB_CFB_COPYAREA
1854 select FB_CFB_IMAGEBLIT
1856 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1857 used mainly in the MIPS-based DECstation series.
1860 tristate "PMAG-BA TURBOchannel framebuffer support"
1862 select FB_CFB_FILLRECT
1863 select FB_CFB_COPYAREA
1864 select FB_CFB_IMAGEBLIT
1866 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1867 used mainly in the MIPS-based DECstation series.
1870 tristate "PMAGB-B TURBOchannel framebuffer support"
1872 select FB_CFB_FILLRECT
1873 select FB_CFB_COPYAREA
1874 select FB_CFB_IMAGEBLIT
1876 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1877 in the MIPS-based DECstation series. The card is currently only
1878 supported in 1280x1024x8 mode.
1881 bool "Maxine (Personal DECstation) onboard framebuffer support"
1882 depends on (FB = y) && MACH_DECSTATION
1883 select FB_CFB_FILLRECT
1884 select FB_CFB_COPYAREA
1885 select FB_CFB_IMAGEBLIT
1887 Support for the onboard framebuffer (1024x768x8) in the Personal
1888 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1892 bool "G364 frame buffer support"
1893 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1894 select FB_CFB_FILLRECT
1895 select FB_CFB_COPYAREA
1896 select FB_CFB_IMAGEBLIT
1898 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1899 Olivetti M700-10 systems.
1902 bool "Motorola 68328 native frame buffer support"
1903 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1904 select FB_CFB_FILLRECT
1905 select FB_CFB_COPYAREA
1906 select FB_CFB_IMAGEBLIT
1908 Say Y here if you want to support the built-in frame buffer of
1909 the Motorola 68328 CPU family.
1912 tristate "PXA168/910 LCD framebuffer support"
1913 depends on FB && (CPU_PXA168 || CPU_PXA910)
1914 select FB_CFB_FILLRECT
1915 select FB_CFB_COPYAREA
1916 select FB_CFB_IMAGEBLIT
1918 Frame buffer driver for the built-in LCD controller in the Marvell
1922 tristate "PXA LCD framebuffer support"
1923 depends on FB && ARCH_PXA
1924 select FB_CFB_FILLRECT
1925 select FB_CFB_COPYAREA
1926 select FB_CFB_IMAGEBLIT
1928 Frame buffer driver for the built-in LCD controller in the Intel
1931 This driver is also available as a module ( = code which can be
1932 inserted and removed from the running kernel whenever you want). The
1933 module will be called pxafb. If you want to compile it as a module,
1934 say M here and read <file:Documentation/kbuild/modules.txt>.
1938 config FB_PXA_OVERLAY
1939 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1941 depends on FB_PXA && (PXA27x || PXA3xx)
1943 config FB_PXA_SMARTPANEL
1944 bool "PXA Smartpanel LCD support"
1948 config FB_PXA_PARAMETERS
1949 bool "PXA LCD command line parameters"
1953 Enable the use of kernel command line or module parameters
1954 to configure the physical properties of the LCD panel when
1955 using the PXA LCD driver.
1957 This option allows you to override the panel parameters
1958 supplied by the platform in order to support multiple
1959 different models of flatpanel. If you will only be using a
1960 single model of flatpanel then you can safely leave this
1963 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1966 tristate "PXA3xx 2D graphics accelerator driver"
1969 Kernelspace driver for the 2D graphics controller unit (GCU)
1970 found on PXA3xx processors. There is a counterpart driver in the
1971 DirectFB suite, see http://www.directfb.org/
1973 If you compile this as a module, it will be called pxa3xx_gcu.
1976 tristate "2700G LCD framebuffer support"
1977 depends on FB && ARCH_PXA
1978 select FB_CFB_FILLRECT
1979 select FB_CFB_COPYAREA
1980 select FB_CFB_IMAGEBLIT
1982 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1986 bool "Enable debugging info via debugfs"
1987 depends on FB_MBX && DEBUG_FS
1990 Enable this if you want debugging information using the debug
1991 filesystem (debugfs)
1996 tristate "Freescale DIU framebuffer support"
1997 depends on FB && FSL_SOC
1998 select FB_MODE_HELPERS
1999 select FB_CFB_FILLRECT
2000 select FB_CFB_COPYAREA
2001 select FB_CFB_IMAGEBLIT
2002 select PPC_LIB_RHEAP
2004 Framebuffer driver for the Freescale SoC DIU
2007 tristate "W100 frame buffer support"
2008 depends on FB && ARCH_PXA
2009 select FB_CFB_FILLRECT
2010 select FB_CFB_COPYAREA
2011 select FB_CFB_IMAGEBLIT
2013 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2014 It can also drive the w3220 chip found on iPAQ hx4700.
2016 This driver is also available as a module ( = code which can be
2017 inserted and removed from the running kernel whenever you want). The
2018 module will be called w100fb. If you want to compile it as a module,
2019 say M here and read <file:Documentation/kbuild/modules.txt>.
2023 config FB_SH_MOBILE_LCDC
2024 tristate "SuperH Mobile LCDC framebuffer support"
2025 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2026 select FB_SYS_FILLRECT
2027 select FB_SYS_COPYAREA
2028 select FB_SYS_IMAGEBLIT
2030 select FB_DEFERRED_IO
2032 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2034 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2036 config FB_SH_MOBILE_HDMI
2037 tristate "SuperH Mobile HDMI controller support"
2038 depends on FB_SH_MOBILE_LCDC
2039 select FB_MODE_HELPERS
2044 Driver for the on-chip SH-Mobile HDMI controller.
2047 tristate "Toshiba Mobile IO FrameBuffer support"
2048 depends on FB && MFD_CORE
2049 select FB_CFB_FILLRECT
2050 select FB_CFB_COPYAREA
2051 select FB_CFB_IMAGEBLIT
2053 Frame buffer driver for the Toshiba Mobile IO integrated as found
2054 on the Sharp SL-6000 series
2056 This driver is also available as a module ( = code which can be
2057 inserted and removed from the running kernel whenever you want). The
2058 module will be called tmiofb. If you want to compile it as a module,
2059 say M here and read <file:Documentation/kbuild/modules.txt>.
2063 config FB_TMIO_ACCELL
2064 bool "tmiofb acceleration"
2069 tristate "Samsung S3C framebuffer support"
2070 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2071 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2072 select FB_CFB_FILLRECT
2073 select FB_CFB_COPYAREA
2074 select FB_CFB_IMAGEBLIT
2076 Frame buffer driver for the built-in FB controller in the Samsung
2077 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2078 and the S3C64XX series such as the S3C6400 and S3C6410.
2080 These chips all have the same basic framebuffer design with the
2081 actual capabilities depending on the chip. For instance the S3C6400
2082 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2083 currently only have two.
2085 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2087 config FB_S3C_DEBUG_REGWRITE
2088 bool "Debug register writes"
2091 Show all register writes via pr_debug()
2094 tristate "S3C2410 LCD framebuffer support"
2095 depends on FB && ARCH_S3C24XX
2096 select FB_CFB_FILLRECT
2097 select FB_CFB_COPYAREA
2098 select FB_CFB_IMAGEBLIT
2100 Frame buffer driver for the built-in LCD controller in the Samsung
2103 This driver is also available as a module ( = code which can be
2104 inserted and removed from the running kernel whenever you want). The
2105 module will be called s3c2410fb. If you want to compile it as a module,
2106 say M here and read <file:Documentation/kbuild/modules.txt>.
2109 config FB_S3C2410_DEBUG
2110 bool "S3C2410 lcd debug messages"
2111 depends on FB_S3C2410
2113 Turn on debugging messages. Note that you can set/unset at run time
2117 bool "NUC900 LCD framebuffer support"
2118 depends on FB && ARCH_W90X900
2119 select FB_CFB_FILLRECT
2120 select FB_CFB_COPYAREA
2121 select FB_CFB_IMAGEBLIT
2123 Frame buffer driver for the built-in LCD controller in the Nuvoton
2126 config GPM1040A0_320X240
2127 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2128 depends on FB_NUC900
2130 config FB_NUC900_DEBUG
2131 bool "NUC900 lcd debug messages"
2132 depends on FB_NUC900
2134 Turn on debugging messages. Note that you can set/unset at run time
2138 tristate "Silicon Motion SM501 framebuffer support"
2139 depends on FB && MFD_SM501
2140 select FB_CFB_FILLRECT
2141 select FB_CFB_COPYAREA
2142 select FB_CFB_IMAGEBLIT
2144 Frame buffer driver for the CRT and LCD controllers in the Silicon
2147 This driver is also available as a module ( = code which can be
2148 inserted and removed from the running kernel whenever you want). The
2149 module will be called sm501fb. If you want to compile it as a module,
2150 say M here and read <file:Documentation/kbuild/modules.txt>.
2155 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2156 depends on FB && USB
2157 select FB_MODE_HELPERS
2158 select FB_SYS_FILLRECT
2159 select FB_SYS_COPYAREA
2160 select FB_SYS_IMAGEBLIT
2162 select FB_DEFERRED_IO
2164 This is a kernel framebuffer driver for SMSC UFX USB devices.
2165 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2166 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2168 To compile as a module, choose M here: the module name is smscufx.
2171 tristate "Displaylink USB Framebuffer support"
2172 depends on FB && USB
2173 select FB_MODE_HELPERS
2174 select FB_SYS_FILLRECT
2175 select FB_SYS_COPYAREA
2176 select FB_SYS_IMAGEBLIT
2178 select FB_DEFERRED_IO
2180 This is a kernel framebuffer driver for DisplayLink USB devices.
2181 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2182 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2183 To compile as a module, choose M here: the module name is udlfb.
2185 config FB_IBM_GXT4500
2186 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2187 depends on FB && PPC
2188 select FB_CFB_FILLRECT
2189 select FB_CFB_COPYAREA
2190 select FB_CFB_IMAGEBLIT
2192 Say Y here to enable support for the IBM GXT4000P/6000P and
2193 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2194 found on some IBM System P (pSeries) machines. This driver
2195 doesn't use Geometry Engine GT1000.
2198 tristate "PS3 GPU framebuffer driver"
2199 depends on FB && PS3_PS3AV
2200 select FB_SYS_FILLRECT
2201 select FB_SYS_COPYAREA
2202 select FB_SYS_IMAGEBLIT
2204 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2206 Include support for the virtual frame buffer in the PS3 platform.
2208 config FB_PS3_DEFAULT_SIZE_M
2209 int "PS3 default frame buffer size (in MiB)"
2213 This is the default size (in MiB) of the virtual frame buffer in
2215 The default value can be overridden on the kernel command line
2216 using the "ps3fb" option (e.g. "ps3fb=9M");
2219 tristate "Xilinx frame buffer support"
2220 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2221 select FB_CFB_FILLRECT
2222 select FB_CFB_COPYAREA
2223 select FB_CFB_IMAGEBLIT
2225 Include support for the Xilinx ML300/ML403 reference design
2226 framebuffer. ML300 carries a 640*480 LCD display on the board,
2227 ML403 uses a standard DB15 VGA connector.
2230 tristate "Goldfish Framebuffer"
2231 depends on FB && HAS_DMA
2232 select FB_CFB_FILLRECT
2233 select FB_CFB_COPYAREA
2234 select FB_CFB_IMAGEBLIT
2236 Framebuffer driver for Goldfish Virtual Platform
2239 tristate "Cobalt server LCD frame buffer support"
2240 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2243 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2244 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2245 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2246 select FB_CFB_FILLRECT
2247 select FB_CFB_COPYAREA
2248 select FB_CFB_IMAGEBLIT
2250 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2251 (D)STN/TFT LCD Controller.
2252 Supports display resolutions up to 1024x1024 pixel, grayscale and
2253 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2254 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2255 panels <= 320 pixel horizontal resolution.
2258 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2259 depends on FB && ARCH_DAVINCI_DA8XX
2260 select FB_CFB_FILLRECT
2261 select FB_CFB_COPYAREA
2262 select FB_CFB_IMAGEBLIT
2263 select FB_CFB_REV_PIXELS_IN_BYTE
2265 This is the frame buffer device driver for the TI LCD controller
2266 found on DA8xx/OMAP-L1xx SoCs.
2270 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2272 select FB_SYS_FILLRECT
2273 select FB_SYS_COPYAREA
2274 select FB_SYS_IMAGEBLIT
2277 This is a `virtual' frame buffer device. It operates on a chunk of
2278 unswappable kernel memory instead of on the memory of a graphics
2279 board. This means you cannot see any output sent to this frame
2280 buffer device, while it does consume precious memory. The main use
2281 of this frame buffer device is testing and debugging the frame
2282 buffer subsystem. Do NOT enable it for normal systems! To protect
2283 the innocent, it has to be enabled explicitly at boot time using the
2284 kernel option `video=vfb:'.
2286 To compile this driver as a module, choose M here: the
2287 module will be called vfb. In order to load it, you must use
2288 the vfb_enable=1 option.
2292 config XEN_FBDEV_FRONTEND
2293 tristate "Xen virtual frame buffer support"
2294 depends on FB && XEN
2295 select FB_SYS_FILLRECT
2296 select FB_SYS_COPYAREA
2297 select FB_SYS_IMAGEBLIT
2299 select FB_DEFERRED_IO
2300 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2301 select XEN_XENBUS_FRONTEND
2304 This driver implements the front-end of the Xen virtual
2305 frame buffer driver. It communicates with a back-end
2309 tristate "E-Ink Metronome/8track controller support"
2311 select FB_SYS_FILLRECT
2312 select FB_SYS_COPYAREA
2313 select FB_SYS_IMAGEBLIT
2315 select FB_DEFERRED_IO
2317 This driver implements support for the E-Ink Metronome
2318 controller. The pre-release name for this device was 8track
2319 and could also have been called by some vendors as PVI-nnnn.
2322 tristate "Fujitsu MB862xx GDC support"
2324 depends on PCI || (OF && PPC)
2325 select FB_CFB_FILLRECT
2326 select FB_CFB_COPYAREA
2327 select FB_CFB_IMAGEBLIT
2329 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2332 prompt "GDC variant"
2333 depends on FB_MB862XX
2335 config FB_MB862XX_PCI_GDC
2336 bool "Carmine/Coral-P(A) GDC"
2339 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2340 PCI graphics controller devices.
2342 config FB_MB862XX_LIME
2344 depends on OF && PPC
2345 select FB_FOREIGN_ENDIAN
2346 select FB_LITTLE_ENDIAN
2348 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2352 config FB_MB862XX_I2C
2353 bool "Support I2C bus on MB862XX GDC"
2354 depends on FB_MB862XX && I2C
2357 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2358 driver to support accessing I2C devices on controller's I2C bus.
2359 These are usually some video decoder chips.
2362 tristate "EP93XX frame buffer support"
2363 depends on FB && ARCH_EP93XX
2364 select FB_CFB_FILLRECT
2365 select FB_CFB_COPYAREA
2366 select FB_CFB_IMAGEBLIT
2368 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2369 This driver is also available as a module. The module will be called
2372 config FB_PRE_INIT_FB
2373 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2374 depends on FB && FB_MB862XX_LIME
2376 Select this option if display contents should be inherited as set by
2380 tristate "MSM Framebuffer support"
2381 depends on FB && ARCH_MSM
2382 select FB_CFB_FILLRECT
2383 select FB_CFB_COPYAREA
2384 select FB_CFB_IMAGEBLIT
2387 tristate "MX3 Framebuffer support"
2388 depends on FB && MX3_IPU
2389 select FB_CFB_FILLRECT
2390 select FB_CFB_COPYAREA
2391 select FB_CFB_IMAGEBLIT
2394 This is a framebuffer device for the i.MX31 LCD Controller. So
2395 far only synchronous displays are supported. If you plan to use
2396 an LCD display with your i.MX31 system, say Y here.
2398 config FB_BROADSHEET
2399 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2401 select FB_SYS_FILLRECT
2402 select FB_SYS_COPYAREA
2403 select FB_SYS_IMAGEBLIT
2405 select FB_DEFERRED_IO
2407 This driver implements support for the E-Ink Broadsheet
2408 controller. The release name for this device was Epson S1D13521
2409 and could also have been called by other names when coupled with
2413 tristate "AUO-K190X EPD controller support"
2415 select FB_SYS_FILLRECT
2416 select FB_SYS_COPYAREA
2417 select FB_SYS_IMAGEBLIT
2419 select FB_DEFERRED_IO
2421 Provides support for epaper controllers from the K190X series
2422 of AUO. These controllers can be used to drive epaper displays
2425 This option enables the common support, shared by the individual
2426 controller drivers. You will also have to enable the driver
2427 for the controller type used in your device.
2430 tristate "AUO-K1900 EPD controller support"
2431 depends on FB && FB_AUO_K190X
2433 This driver implements support for the AUO K1900 epd-controller.
2434 This controller can drive Sipix epaper displays but can only do
2435 serial updates, reducing the number of possible frames per second.
2438 tristate "AUO-K1901 EPD controller support"
2439 depends on FB && FB_AUO_K190X
2441 This driver implements support for the AUO K1901 epd-controller.
2442 This controller can drive Sipix epaper displays and supports
2443 concurrent updates, making higher frames per second possible.
2446 tristate "JZ4740 LCD framebuffer support"
2447 depends on FB && MACH_JZ4740
2448 select FB_SYS_FILLRECT
2449 select FB_SYS_COPYAREA
2450 select FB_SYS_IMAGEBLIT
2452 Framebuffer support for the JZ4740 SoC.
2455 tristate "MXS LCD framebuffer support"
2456 depends on FB && ARCH_MXS
2457 select FB_CFB_FILLRECT
2458 select FB_CFB_COPYAREA
2459 select FB_CFB_IMAGEBLIT
2460 select FB_MODE_HELPERS
2461 select VIDEOMODE_HELPERS
2463 Framebuffer support for the MXS SoC.
2465 config FB_PUV3_UNIGFX
2466 tristate "PKUnity v3 Unigfx framebuffer support"
2467 depends on FB && UNICORE32 && ARCH_PUV3
2468 select FB_SYS_FILLRECT
2469 select FB_SYS_COPYAREA
2470 select FB_SYS_IMAGEBLIT
2473 Choose this option if you want to use the Unigfx device as a
2474 framebuffer device. Without the support of PCI & AGP.
2477 tristate "Microsoft Hyper-V Synthetic Video support"
2478 depends on FB && HYPERV
2479 select FB_CFB_FILLRECT
2480 select FB_CFB_COPYAREA
2481 select FB_CFB_IMAGEBLIT
2483 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2486 bool "Simple framebuffer support"
2487 depends on (FB = y) && OF
2488 select FB_CFB_FILLRECT
2489 select FB_CFB_COPYAREA
2490 select FB_CFB_IMAGEBLIT
2492 Say Y if you want support for a simple frame-buffer.
2494 This driver assumes that the display hardware has been initialized
2495 before the kernel boots, and the kernel will simply render to the
2496 pre-allocated frame buffer surface.
2498 Configuration re: surface address, size, and format must be provided
2499 through device tree, or potentially plain old platform data in the
2502 source "drivers/video/omap/Kconfig"
2503 source "drivers/video/omap2/Kconfig"
2504 source "drivers/video/exynos/Kconfig"
2505 source "drivers/video/mmp/Kconfig"
2506 source "drivers/video/backlight/Kconfig"
2507 source "drivers/video/adf/Kconfig"
2508 source "drivers/video/rockchip/Kconfig"
2511 source "drivers/video/console/Kconfig"
2514 if FB || SGI_NEWPORT_CONSOLE
2515 source "drivers/video/logo/Kconfig"
2518 config FB_SH_MOBILE_MERAM
2519 tristate "SuperH Mobile MERAM read ahead support"
2520 depends on (SUPERH || ARCH_SHMOBILE)
2521 select GENERIC_ALLOCATOR
2523 Enable MERAM support for the SuperH controller.
2525 This will allow for caching of the framebuffer to provide more
2526 reliable access under heavy main memory bus traffic situations.
2527 Up to 4 memory channels can be configured, allowing 4 RGB or
2528 2 YCbCr framebuffers to be configured.
2531 tristate "Solomon SSD1307 framebuffer support"
2532 depends on FB && I2C
2536 select FB_SYS_FILLRECT
2537 select FB_SYS_COPYAREA
2538 select FB_SYS_IMAGEBLIT
2539 select FB_DEFERRED_IO
2542 This driver implements support for the Solomon SSD1307
2543 OLED controller over I2C.