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/host1x/Kconfig"
24 source "drivers/gpu/drm/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
36 config VIDEOMODE_HELPERS
43 tristate "Support for frame buffer devices"
45 The frame buffer device provides an abstraction for the graphics
46 hardware. It represents the frame buffer of some video hardware and
47 allows application software to access the graphics hardware through
48 a well-defined interface, so the software doesn't need to know
49 anything about the low-level (hardware register) stuff.
51 Frame buffer devices work identically across the different
52 architectures supported by Linux and make the implementation of
53 application programs easier and more portable; at this point, an X
54 server exists which uses the frame buffer device exclusively.
55 On several non-X86 architectures, the frame buffer device is the
56 only way to use the graphics hardware.
58 The device is accessed through special device nodes, usually located
59 in the /dev directory, i.e. /dev/fb*.
61 You need an utility program called fbset to make full use of frame
62 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
63 and the Framebuffer-HOWTO at
64 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
67 Say Y here and to the driver for your graphics board below if you
68 are compiling a kernel for a non-x86 architecture.
70 If you are compiling for the x86 architecture, you can say Y if you
71 want to play with it, but it is not essential. Please note that
72 running graphical applications that directly touch the hardware
73 (e.g. an accelerated X server) and that are not frame buffer
74 device-aware may cause unexpected results. If unsure, say N.
77 bool "Enable firmware EDID"
81 This enables access to the EDID transferred from the firmware.
82 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
83 transfers do not work for your driver and if you are using
84 nvidiafb, i810fb or savagefb.
86 In general, choosing Y for this option is safe. If you
87 experience extremely long delays while booting before you get
88 something on your display, try setting this to N. Matrox cards in
89 combination with certain motherboards and monitors are known to
90 suffer from this problem.
99 config FB_BOOT_VESA_SUPPORT
104 If true, at least one selected framebuffer driver can take advantage
105 of VESA video modes set at an early boot stage via the vga= parameter.
107 config FB_CFB_FILLRECT
112 Include the cfb_fillrect function for generic software rectangle
113 filling. This is used by drivers that don't provide their own
114 (accelerated) version.
116 config FB_CFB_COPYAREA
121 Include the cfb_copyarea function for generic software area copying.
122 This is used by drivers that don't provide their own (accelerated)
125 config FB_CFB_IMAGEBLIT
130 Include the cfb_imageblit function for generic software image
131 blitting. This is used by drivers that don't provide their own
132 (accelerated) version.
134 config FB_CFB_REV_PIXELS_IN_BYTE
139 Allow generic frame-buffer functions to work on displays with 1, 2
140 and 4 bits per pixel depths which has opposite order of pixels in
141 byte order to bytes in long order.
143 config FB_SYS_FILLRECT
148 Include the sys_fillrect function for generic software rectangle
149 filling. This is used by drivers that don't provide their own
150 (accelerated) version and the framebuffer is in system RAM.
152 config FB_SYS_COPYAREA
157 Include the sys_copyarea function for generic software area copying.
158 This is used by drivers that don't provide their own (accelerated)
159 version and the framebuffer is in system RAM.
161 config FB_SYS_IMAGEBLIT
166 Include the sys_imageblit function for generic software image
167 blitting. This is used by drivers that don't provide their own
168 (accelerated) version and the framebuffer is in system RAM.
170 menuconfig FB_FOREIGN_ENDIAN
171 bool "Framebuffer foreign endianness support"
174 This menu will let you enable support for the framebuffers with
175 non-native endianness (e.g. Little-Endian framebuffer on a
176 Big-Endian machine). Most probably you don't have such hardware,
177 so it's safe to say "n" here.
180 prompt "Choice endianness support"
181 depends on FB_FOREIGN_ENDIAN
183 config FB_BOTH_ENDIAN
184 bool "Support for Big- and Little-Endian framebuffers"
187 bool "Support for Big-Endian framebuffers only"
189 config FB_LITTLE_ENDIAN
190 bool "Support for Little-Endian framebuffers only"
199 config FB_DEFERRED_IO
206 depends on FB_DEFERRED_IO
213 Common utility functions useful to fbdev drivers of VGA-based
224 select BACKLIGHT_LCD_SUPPORT
225 select BACKLIGHT_CLASS_DEVICE
228 config FB_MODE_HELPERS
229 bool "Enable Video Mode Handling Helpers"
233 This enables functions for handling video modes using the
234 Generalized Timing Formula and the EDID parser. A few drivers rely
235 on this feature such as the radeonfb, rivafb, and the i810fb. If
236 your driver does not take advantage of this feature, choosing Y will
237 just increase the kernel size by about 5K.
239 config FB_TILEBLITTING
240 bool "Enable Tile Blitting Support"
244 This enables tile blitting. Tile blitting is a drawing technique
245 where the screen is divided into rectangular sections (tiles), whereas
246 the standard blitting divides the screen into pixels. Because the
247 default drawing element is a tile, drawing functions will be passed
248 parameters in terms of number of tiles instead of number of pixels.
249 For example, to draw a single character, instead of using bitmaps,
250 an index to an array of bitmaps will be used. To clear or move a
251 rectangular section of a screen, the rectangle will be described in
252 terms of number of tiles in the x- and y-axis.
254 This is particularly important to one driver, matroxfb. If
257 comment "Frame buffer hardware drivers"
261 tristate "Aeroflex Gaisler framebuffer support"
262 depends on FB && SPARC
263 select FB_CFB_FILLRECT
264 select FB_CFB_COPYAREA
265 select FB_CFB_IMAGEBLIT
267 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
270 tristate "Cirrus Logic support"
271 depends on FB && (ZORRO || PCI)
272 select FB_CFB_FILLRECT
273 select FB_CFB_COPYAREA
274 select FB_CFB_IMAGEBLIT
276 This enables support for Cirrus Logic GD542x/543x based boards on
277 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
279 If you have a PCI-based system, this enables support for these
280 chips: GD-543x, GD-544x, GD-5480.
282 Please read the file <file:Documentation/fb/cirrusfb.txt>.
284 Say N unless you have such a graphics board or plan to get one
285 before you next recompile the kernel.
288 tristate "Permedia2 support"
289 depends on FB && ((AMIGA && BROKEN) || PCI)
290 select FB_CFB_FILLRECT
291 select FB_CFB_COPYAREA
292 select FB_CFB_IMAGEBLIT
294 This is the frame buffer device driver for cards based on
295 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
296 The driver was tested on the following cards:
297 Diamond FireGL 1000 PRO AGP
298 ELSA Gloria Synergy PCI
299 Appian Jeronimo PRO (both heads) PCI
300 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
301 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
302 ASK Graphic Blaster Exxtreme AGP
304 To compile this driver as a module, choose M here: the
305 module will be called pm2fb.
307 config FB_PM2_FIFO_DISCONNECT
308 bool "enable FIFO disconnect feature"
309 depends on FB_PM2 && PCI
311 Support the Permedia2 FIFO disconnect feature.
314 tristate "ARM PrimeCell PL110 support"
315 depends on ARM || ARM64 || COMPILE_TEST
316 depends on FB && ARM_AMBA
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
321 This framebuffer device driver is for the ARM PrimeCell PL110
322 Colour LCD controller. ARM PrimeCells provide the building
323 blocks for System on a Chip devices.
325 If you want to compile this as a module (=code which can be
326 inserted into and removed from the running kernel), say M
327 here and read <file:Documentation/kbuild/modules.txt>. The module
328 will be called amba-clcd.
331 bool "Acorn VIDC support"
332 depends on (FB = y) && ARM && ARCH_ACORN
333 select FB_CFB_FILLRECT
334 select FB_CFB_COPYAREA
335 select FB_CFB_IMAGEBLIT
337 This is the frame buffer device driver for the Acorn VIDC graphics
338 hardware found in Acorn RISC PCs and other ARM-based machines. If
342 bool "CLPS711X LCD support"
343 depends on (FB = y) && ARM && ARCH_CLPS711X
344 select FB_CFB_FILLRECT
345 select FB_CFB_COPYAREA
346 select FB_CFB_IMAGEBLIT
348 Say Y to enable the Framebuffer driver for the CLPS7111 and
352 bool "SA-1100 LCD support"
353 depends on (FB = y) && ARM && ARCH_SA1100
354 select FB_CFB_FILLRECT
355 select FB_CFB_COPYAREA
356 select FB_CFB_IMAGEBLIT
358 This is a framebuffer device for the SA-1100 LCD Controller.
359 See <http://www.linux-fbdev.org/> for information on framebuffer
362 If you plan to use the LCD display with your SA-1100 system, say
366 tristate "Freescale i.MX1/21/25/27 LCD support"
367 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
371 select FB_MODE_HELPERS
372 select VIDEOMODE_HELPERS
375 tristate "CyberPro 2000/2010/5000 support"
376 depends on FB && PCI && (BROKEN || !SPARC64)
377 select FB_CFB_FILLRECT
378 select FB_CFB_COPYAREA
379 select FB_CFB_IMAGEBLIT
381 This enables support for the Integraphics CyberPro 20x0 and 5000
382 VGA chips used in the Rebel.com Netwinder and other machines.
383 Say Y if you have a NetWinder or a graphics card containing this
384 device, otherwise say N.
386 config FB_CYBER2000_DDC
387 bool "DDC for CyberPro support"
388 depends on FB_CYBER2000
392 Say Y here if you want DDC support for your CyberPro graphics
393 card. This is only I2C bus support, driver does not use EDID.
395 config FB_CYBER2000_I2C
396 bool "CyberPro 2000/2010/5000 I2C support"
397 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
400 Enable support for the I2C video decoder interface on the
401 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
402 on the Netwinder machines for the SAA7111 video capture.
406 depends on (FB = y) && APOLLO
408 select FB_CFB_FILLRECT
409 select FB_CFB_IMAGEBLIT
413 depends on (FB = y) && Q40
415 select FB_CFB_FILLRECT
416 select FB_CFB_COPYAREA
417 select FB_CFB_IMAGEBLIT
420 tristate "Amiga native chipset support"
421 depends on FB && AMIGA
423 This is the frame buffer device driver for the builtin graphics
424 chipset found in Amigas.
426 To compile this driver as a module, choose M here: the
427 module will be called amifb.
430 bool "Amiga OCS chipset support"
433 This enables support for the original Agnus and Denise video chips,
434 found in the Amiga 1000 and most A500's and A2000's. If you intend
435 to run Linux on any of these systems, say Y; otherwise say N.
438 bool "Amiga ECS chipset support"
441 This enables support for the Enhanced Chip Set, found in later
442 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
443 you intend to run Linux on any of these systems, say Y; otherwise
447 bool "Amiga AGA chipset support"
450 This enables support for the Advanced Graphics Architecture (also
451 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
452 and CD32. If you intend to run Linux on any of these systems, say Y;
456 bool "Amiga FrameMaster II/Rainbow II support"
457 depends on (FB = y) && ZORRO
458 select FB_CFB_FILLRECT
459 select FB_CFB_COPYAREA
460 select FB_CFB_IMAGEBLIT
462 This is the frame buffer device driver for the Amiga FrameMaster
463 card from BSC (exhibited 1992 but not shipped as a CBM product).
466 tristate "Arc Monochrome LCD board support"
468 select FB_SYS_FILLRECT
469 select FB_SYS_COPYAREA
470 select FB_SYS_IMAGEBLIT
473 This enables support for the Arc Monochrome LCD board. The board
474 is based on the KS-108 lcd controller and is typically a matrix
475 of 2*n chips. This driver was tested with a 128x64 panel. This
476 driver supports it for use with x86 SBCs through a 16 bit GPIO
477 interface (8 bit data, 8 bit control). If you anticipate using
478 this driver, say Y or M; otherwise say N. You must specify the
479 GPIO IO address to be used for setting control and data.
482 bool "Atari native chipset support"
483 depends on (FB = y) && ATARI
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 builtin graphics
489 chipset found in Ataris.
492 bool "Open Firmware frame buffer device support"
493 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
494 select FB_CFB_FILLRECT
495 select FB_CFB_COPYAREA
496 select FB_CFB_IMAGEBLIT
499 Say Y if you want support with Open Firmware for your graphics
503 bool "Apple \"control\" display support"
504 depends on (FB = y) && PPC_PMAC && PPC32
505 select FB_CFB_FILLRECT
506 select FB_CFB_COPYAREA
507 select FB_CFB_IMAGEBLIT
510 This driver supports a frame buffer for the graphics adapter in the
511 Power Macintosh 7300 and others.
514 bool "Apple \"platinum\" display support"
515 depends on (FB = y) && PPC_PMAC && PPC32
516 select FB_CFB_FILLRECT
517 select FB_CFB_COPYAREA
518 select FB_CFB_IMAGEBLIT
521 This driver supports a frame buffer for the "platinum" graphics
522 adapter in some Power Macintoshes.
525 bool "Apple \"valkyrie\" display support"
526 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
527 select FB_CFB_FILLRECT
528 select FB_CFB_COPYAREA
529 select FB_CFB_IMAGEBLIT
532 This driver supports a frame buffer for the "valkyrie" graphics
533 adapter in some Power Macintoshes.
536 bool "Chips 65550 display support"
537 depends on (FB = y) && PPC32 && 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 Chips & Technologies
543 65550 graphics chip in PowerBooks.
546 bool "Asiliant (Chips) 69000 display support"
547 depends on (FB = y) && PCI
548 select FB_CFB_FILLRECT
549 select FB_CFB_COPYAREA
550 select FB_CFB_IMAGEBLIT
552 This is the frame buffer device driver for the Asiliant 69030 chipset
555 bool "IMS Twin Turbo display support"
556 depends on (FB = y) && PCI
557 select FB_CFB_IMAGEBLIT
558 select FB_MACMODES if PPC
560 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
561 many Macintosh and compatible computers.
564 tristate "VGA 16-color graphics support"
565 depends on FB && (X86 || PPC)
566 select FB_CFB_FILLRECT
567 select FB_CFB_COPYAREA
568 select FB_CFB_IMAGEBLIT
570 select FONT_8x16 if FRAMEBUFFER_CONSOLE
572 This is the frame buffer device driver for VGA 16 color graphic
573 cards. Say Y if you have such a card.
575 To compile this driver as a module, choose M here: the
576 module will be called vga16fb.
578 config FB_BF54X_LQ043
579 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
580 depends on FB && (BF54x) && !BF542
581 select FB_CFB_FILLRECT
582 select FB_CFB_COPYAREA
583 select FB_CFB_IMAGEBLIT
585 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
587 config FB_BFIN_T350MCQB
588 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
589 depends on FB && BLACKFIN
591 select FB_CFB_FILLRECT
592 select FB_CFB_COPYAREA
593 select FB_CFB_IMAGEBLIT
595 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
596 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
597 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
599 config FB_BFIN_LQ035Q1
600 tristate "SHARP LQ035Q1DH02 TFT LCD"
601 depends on FB && BLACKFIN && SPI
602 select FB_CFB_FILLRECT
603 select FB_CFB_COPYAREA
604 select FB_CFB_IMAGEBLIT
607 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
608 the Blackfin Landscape LCD EZ-Extender Card.
609 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
610 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
612 To compile this driver as a module, choose M here: the
613 module will be called bfin-lq035q1-fb.
615 config FB_BF537_LQ035
616 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
617 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
618 select FB_CFB_FILLRECT
619 select FB_CFB_COPYAREA
620 select FB_CFB_IMAGEBLIT
623 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
626 To compile this driver as a module, choose M here: the
627 module will be called bf537-lq035.
630 tristate "Blackfin ADV7393 Video encoder"
631 depends on FB && BLACKFIN
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
637 This is the framebuffer device for a ADV7393 video encoder
638 attached to a Blackfin on the PPI port.
639 If your Blackfin board has a ADV7393 select Y.
641 To compile this driver as a module, choose M here: the
642 module will be called bfin_adv7393fb.
645 prompt "Video mode support"
646 depends on FB_BFIN_7393
656 bool 'NTSC 640x480 (Experimental)'
659 bool 'PAL 640x480 (Experimental)'
662 bool 'NTSC 720x480 YCbCR input'
665 bool 'PAL 720x576 YCbCR input'
670 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
671 depends on (FB_BFIN_7393)
672 default ADV7393_1XMEM
682 tristate "HP STI frame buffer device support"
683 depends on FB && PARISC
684 select FB_CFB_FILLRECT
685 select FB_CFB_COPYAREA
686 select FB_CFB_IMAGEBLIT
691 STI refers to the HP "Standard Text Interface" which is a set of
692 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
693 Enabling this option will implement the linux framebuffer device
694 using calls to the STI BIOS routines for initialisation.
696 If you enable this option, you will get a planar framebuffer device
697 /dev/fb which will work on the most common HP graphic cards of the
698 NGLE family, including the artist chips (in the 7xx and Bxxx series),
699 HCRX, HCRX24, CRX, CRX24 and VisEG series.
701 It is safe to enable this option, so you should probably say "Y".
704 bool "Generic Macintosh display support"
705 depends on (FB = y) && MAC
706 select FB_CFB_FILLRECT
707 select FB_CFB_COPYAREA
708 select FB_CFB_IMAGEBLIT
713 depends on (FB = y) && DIO
714 select FB_CFB_IMAGEBLIT
718 tristate "TGA/SFB+ framebuffer support"
719 depends on FB && (ALPHA || TC)
720 select FB_CFB_FILLRECT
721 select FB_CFB_COPYAREA
722 select FB_CFB_IMAGEBLIT
725 This is the frame buffer device driver for generic TGA and SFB+
726 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
727 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
728 TURBOchannel cards, also known as PMAGD-A, -B and -C.
730 Due to hardware limitations ZLX-E2 and E3 cards are not supported
731 for DECstation 5000/200 systems. Additionally due to firmware
732 limitations these cards may cause troubles with booting DECstation
733 5000/240 and /260 systems, but are fully supported under Linux if
734 you manage to get it going. ;-)
736 Say Y if you have one of those.
739 tristate "Userspace VESA VGA graphics support"
740 depends on FB && CONNECTOR
741 select FB_CFB_FILLRECT
742 select FB_CFB_COPYAREA
743 select FB_CFB_IMAGEBLIT
744 select FB_MODE_HELPERS
746 This is the frame buffer driver for generic VBE 2.0 compliant
747 graphic cards. It can also take advantage of VBE 3.0 features,
748 such as refresh rate adjustment.
750 This driver generally provides more features than vesafb but
751 requires a userspace helper application called 'v86d'. See
752 <file:Documentation/fb/uvesafb.txt> for more information.
757 bool "VESA VGA graphics support"
758 depends on (FB = y) && X86
759 select FB_CFB_FILLRECT
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
762 select FB_BOOT_VESA_SUPPORT
764 This is the frame buffer device driver for generic VESA 2.0
765 compliant graphic cards. The older VESA 1.2 cards are not supported.
766 You will get a boot time penguin logo at no additional cost. Please
767 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
770 bool "EFI-based Framebuffer Support"
771 depends on (FB = y) && X86 && EFI
772 select FB_CFB_FILLRECT
773 select FB_CFB_COPYAREA
774 select FB_CFB_IMAGEBLIT
776 This is the EFI frame buffer device driver. If the firmware on
777 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
778 using the EFI framebuffer as your console.
781 tristate "N411 Apollo/Hecuba devkit support"
782 depends on FB && X86 && MMU
783 select FB_SYS_FILLRECT
784 select FB_SYS_COPYAREA
785 select FB_SYS_IMAGEBLIT
787 select FB_DEFERRED_IO
790 This enables support for the Apollo display controller in its
791 Hecuba form using the n411 devkit.
794 tristate "Hercules mono graphics support"
797 Say Y here if you have a Hercules mono graphics card.
799 To compile this driver as a module, choose M here: the
800 module will be called hgafb.
802 As this card technology is at least 25 years old,
803 most people will answer N here.
806 tristate "SGI Visual Workstation framebuffer support"
807 depends on FB && X86_VISWS
808 select FB_CFB_FILLRECT
809 select FB_CFB_COPYAREA
810 select FB_CFB_IMAGEBLIT
812 SGI Visual Workstation support for framebuffer graphics.
815 bool "SGI Graphics Backend frame buffer support"
816 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
817 select FB_CFB_FILLRECT
818 select FB_CFB_COPYAREA
819 select FB_CFB_IMAGEBLIT
821 This is the frame buffer device driver for SGI Graphics Backend.
822 This chip is used in SGI O2 and Visual Workstation 320/540.
825 int "Video memory size in MB"
829 This is the amount of memory reserved for the framebuffer,
830 which can be any value between 1MB and 8MB.
833 bool "SBUS and UPA framebuffers"
834 depends on (FB = y) && SPARC
836 Say Y if you want support for SBUS or UPA based frame buffer device.
840 depends on (FB = y) && (SPARC && FB_SBUS)
841 select FB_CFB_FILLRECT
842 select FB_CFB_COPYAREA
843 select FB_CFB_IMAGEBLIT
845 This is the frame buffer device driver for the BWtwo frame buffer.
848 bool "CGthree support"
849 depends on (FB = y) && (SPARC && FB_SBUS)
850 select FB_CFB_FILLRECT
851 select FB_CFB_COPYAREA
852 select FB_CFB_IMAGEBLIT
854 This is the frame buffer device driver for the CGthree frame buffer.
857 bool "CGsix (GX,TurboGX) support"
858 depends on (FB = y) && (SPARC && FB_SBUS)
859 select FB_CFB_COPYAREA
860 select FB_CFB_IMAGEBLIT
862 This is the frame buffer device driver for the CGsix (GX, TurboGX)
866 bool "Creator/Creator3D/Elite3D support"
867 depends on FB_SBUS && SPARC64
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
871 This is the frame buffer device driver for the Creator, Creator3D,
872 and Elite3D graphics boards.
875 bool "TCX (SS4/SS5 only) 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 TCX 24/8bit frame
885 bool "CGfourteen (SX) 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 CGfourteen frame
892 buffer on Desktop SPARCsystems with the SX graphics option.
895 bool "P9100 (Sparcbook 3 only) 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 P9100 card
902 supported on Sparcbook 3 machines.
905 bool "Leo (ZX) support"
907 select FB_CFB_FILLRECT
908 select FB_CFB_COPYAREA
909 select FB_CFB_IMAGEBLIT
911 This is the frame buffer device driver for the SBUS-based Sun ZX
912 (leo) frame buffer cards.
915 bool "IGA 168x display support"
916 depends on (FB = y) && SPARC32
917 select FB_CFB_FILLRECT
918 select FB_CFB_COPYAREA
919 select FB_CFB_IMAGEBLIT
921 This is the framebuffer device for the INTERGRAPHICS 1680 and
922 successor frame buffer cards.
925 bool "Sun XVR-500 3DLABS Wildcat support"
926 depends on (FB = y) && PCI && SPARC64
927 select FB_CFB_FILLRECT
928 select FB_CFB_COPYAREA
929 select FB_CFB_IMAGEBLIT
931 This is the framebuffer device for the Sun XVR-500 and similar
932 graphics cards based upon the 3DLABS Wildcat chipset. The driver
933 only works on sparc64 systems where the system firmware has
934 mostly initialized the card already. It is treated as a
935 completely dumb framebuffer device.
938 bool "Sun XVR-2500 3DLABS Wildcat support"
939 depends on (FB = y) && PCI && SPARC64
940 select FB_CFB_FILLRECT
941 select FB_CFB_COPYAREA
942 select FB_CFB_IMAGEBLIT
944 This is the framebuffer device for the Sun XVR-2500 and similar
945 graphics cards based upon the 3DLABS Wildcat chipset. The driver
946 only works on sparc64 systems where the system firmware has
947 mostly initialized the card already. It is treated as a
948 completely dumb framebuffer device.
951 bool "Sun XVR-1000 support"
952 depends on (FB = y) && 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-1000 and similar
958 graphics cards. The driver only works on sparc64 systems where
959 the system firmware has mostly initialized the card already. It
960 is treated as a completely dumb framebuffer device.
963 tristate "NEC PowerVR 2 display support"
964 depends on FB && SH_DREAMCAST
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
969 Say Y here if you have a PowerVR 2 card in your box. If you plan to
970 run linux on your Dreamcast, you will have to say Y here.
971 This driver may or may not work on other PowerVR 2 cards, but is
972 totally untested. Use at your own risk. If unsure, say N.
974 To compile this driver as a module, choose M here: the
975 module will be called pvr2fb.
977 You can pass several parameters to the driver at boot time or at
978 module load time. The parameters look like "video=pvr2:XXX", where
979 the meaning of XXX can be found at the end of the main source file
980 (<file:drivers/video/pvr2fb.c>). Please see the file
981 <file:Documentation/fb/pvr2fb.txt>.
984 tristate "Epson S1D13XXX framebuffer support"
986 select FB_CFB_FILLRECT
987 select FB_CFB_COPYAREA
988 select FB_CFB_IMAGEBLIT
990 Support for S1D13XXX framebuffer device family (currently only
991 working with S1D13806). Product specs at
992 <http://vdc.epson.com/>
995 tristate "AT91/AT32 LCD Controller support"
996 depends on FB && HAVE_FB_ATMEL
997 select FB_CFB_FILLRECT
998 select FB_CFB_COPYAREA
999 select FB_CFB_IMAGEBLIT
1000 select FB_MODE_HELPERS
1001 select VIDEOMODE_HELPERS
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 "Intel740 support"
1119 depends on FB && PCI
1120 select FB_MODE_HELPERS
1121 select FB_CFB_FILLRECT
1122 select FB_CFB_COPYAREA
1123 select FB_CFB_IMAGEBLIT
1127 This driver supports graphics cards based on Intel740 chip.
1130 tristate "Intel 810/815 support"
1131 depends on FB && PCI && X86_32 && AGP_INTEL
1132 select FB_MODE_HELPERS
1133 select FB_CFB_FILLRECT
1134 select FB_CFB_COPYAREA
1135 select FB_CFB_IMAGEBLIT
1138 This driver supports the on-board graphics built in to the Intel 810
1139 and 815 chipsets. Say Y if you have and plan to use such a board.
1141 To compile this driver as a module, choose M here: the
1142 module will be called i810fb.
1144 For more information, please read
1145 <file:Documentation/fb/intel810.txt>
1148 bool "use VESA Generalized Timing Formula"
1151 If you say Y, then the VESA standard, Generalized Timing Formula
1152 or GTF, will be used to calculate the required video timing values
1153 per video mode. Since the GTF allows nondiscrete timings
1154 (nondiscrete being a range of values as opposed to discrete being a
1155 set of values), you'll be able to use any combination of horizontal
1156 and vertical resolutions, and vertical refresh rates without having
1157 to specify your own timing parameters. This is especially useful
1158 to maximize the performance of an aging display, or if you just
1159 have a display with nonstandard dimensions. A VESA compliant
1160 monitor is recommended, but can still work with non-compliant ones.
1161 If you need or want this, then select this option. The timings may
1162 not be compliant with Intel's recommended values. Use at your own
1165 If you say N, the driver will revert to discrete video timings
1166 using a set recommended by Intel in their documentation.
1171 bool "Enable DDC Support"
1172 depends on FB_I810 && FB_I810_GTF
1177 tristate "Intel LE80578 (Vermilion) support"
1178 depends on FB && PCI && X86
1179 select FB_MODE_HELPERS
1180 select FB_CFB_FILLRECT
1181 select FB_CFB_COPYAREA
1182 select FB_CFB_IMAGEBLIT
1184 This driver supports the LE80578 (Vermilion Range) chipset
1186 config FB_CARILLO_RANCH
1187 tristate "Intel Carillo Ranch support"
1188 depends on FB_LE80578 && FB && PCI && X86
1190 This driver supports the LE80578 (Carillo Ranch) board
1193 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1194 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1195 select FB_MODE_HELPERS
1196 select FB_CFB_FILLRECT
1197 select FB_CFB_COPYAREA
1198 select FB_CFB_IMAGEBLIT
1199 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1200 depends on !DRM_I915
1202 This driver supports the on-board graphics built in to the Intel
1203 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1204 Say Y if you have and plan to use such a board.
1206 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1208 To compile this driver as a module, choose M here: the
1209 module will be called intelfb.
1211 For more information, please read <file:Documentation/fb/intelfb.txt>
1213 config FB_INTEL_DEBUG
1214 bool "Intel driver Debug Messages"
1217 Say Y here if you want the Intel driver to output all sorts
1218 of debugging information to provide to the maintainer when
1219 something goes wrong.
1222 bool "DDC/I2C for Intel framebuffer support"
1227 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1230 tristate "Matrox acceleration"
1231 depends on FB && PCI
1232 select FB_CFB_FILLRECT
1233 select FB_CFB_COPYAREA
1234 select FB_CFB_IMAGEBLIT
1235 select FB_TILEBLITTING
1236 select FB_MACMODES if PPC_PMAC
1238 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1239 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1240 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1241 Matrox G400, G450 or G550 card in your box.
1243 To compile this driver as a module, choose M here: the
1244 module will be called matroxfb.
1246 You can pass several parameters to the driver at boot time or at
1247 module load time. The parameters look like "video=matroxfb:XXX", and
1248 are described in <file:Documentation/fb/matroxfb.txt>.
1250 config FB_MATROX_MILLENIUM
1251 bool "Millennium I/II support"
1252 depends on FB_MATROX
1254 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1255 video card. If you select "Advanced lowlevel driver options" below,
1256 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1257 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1258 also use font widths different from 8.
1260 config FB_MATROX_MYSTIQUE
1261 bool "Mystique support"
1262 depends on FB_MATROX
1264 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1265 video card. If you select "Advanced lowlevel driver options" below,
1266 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1267 packed pixel and 32 bpp packed pixel. You can also use font widths
1271 bool "G100/G200/G400/G450/G550 support"
1272 depends on FB_MATROX
1274 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1275 video card. If you select "Advanced lowlevel driver options", you
1276 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1277 pixel and 32 bpp packed pixel. You can also use font widths
1280 If you need support for G400 secondary head, you must say Y to
1281 "Matrox I2C support" and "G400 second head support" right below.
1282 G450/G550 secondary head and digital output are supported without
1285 The driver starts in monitor mode. You must use the matroxset tool
1286 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1287 swap primary and secondary head outputs, or to change output mode.
1288 Secondary head driver always start in 640x480 resolution and you
1289 must use fbset to change it.
1291 Do not forget that second head supports only 16 and 32 bpp
1292 packed pixels, so it is a good idea to compile them into the kernel
1293 too. You can use only some font widths, as the driver uses generic
1294 painting procedures (the secondary head does not use acceleration
1297 G450/G550 hardware can display TV picture only from secondary CRTC,
1298 and it performs no scaling, so picture must have 525 or 625 lines.
1300 config FB_MATROX_I2C
1301 tristate "Matrox I2C support"
1302 depends on FB_MATROX
1305 This drivers creates I2C buses which are needed for accessing the
1306 DDC (I2C) bus present on all Matroxes, an I2C bus which
1307 interconnects Matrox optional devices, like MGA-TVO on G200 and
1308 G400, and the secondary head DDC bus, present on G400 only.
1310 You can say Y or M here if you want to experiment with monitor
1311 detection code. You must say Y or M here if you want to use either
1312 second head of G400 or MGA-TVO on G200 or G400.
1314 If you compile it as module, it will create a module named
1317 config FB_MATROX_MAVEN
1318 tristate "G400 second head support"
1319 depends on FB_MATROX_G && FB_MATROX_I2C
1321 WARNING !!! This support does not work with G450 !!!
1323 Say Y or M here if you want to use a secondary head (meaning two
1324 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1325 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1326 secondary head output is blanked while you are in X. With XFree
1327 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1328 the fbdev driver on first head and the fbdev driver on second head.
1330 If you compile it as module, two modules are created,
1331 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1332 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1333 also load i2c-matroxfb to get it to run.
1335 The driver starts in monitor mode and you must use the matroxset
1337 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1338 PAL or NTSC or to swap primary and secondary head outputs.
1339 Secondary head driver also always start in 640x480 resolution, you
1340 must use fbset to change it.
1342 Also do not forget that second head supports only 16 and 32 bpp
1343 packed pixels, so it is a good idea to compile them into the kernel
1344 too. You can use only some font widths, as the driver uses generic
1345 painting procedures (the secondary head does not use acceleration
1349 tristate "ATI Radeon display support"
1350 depends on FB && PCI
1351 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1352 select FB_MODE_HELPERS
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1356 select FB_MACMODES if PPC_OF
1358 Choose this option if you want to use an ATI Radeon graphics card as
1359 a framebuffer device. There are both PCI and AGP versions. You
1360 don't need to choose this to run the Radeon in plain VGA mode.
1362 There is a product page at
1363 http://products.amd.com/en-us/GraphicCardResult.aspx
1365 config FB_RADEON_I2C
1366 bool "DDC/I2C for ATI Radeon support"
1367 depends on FB_RADEON
1371 Say Y here if you want DDC/I2C support for your Radeon board.
1373 config FB_RADEON_BACKLIGHT
1374 bool "Support for backlight control"
1375 depends on FB_RADEON
1378 Say Y here if you want to control the backlight of your display.
1380 config FB_RADEON_DEBUG
1381 bool "Lots of debug output from Radeon driver"
1382 depends on FB_RADEON
1385 Say Y here if you want the Radeon driver to output all sorts
1386 of debugging information to provide to the maintainer when
1387 something goes wrong.
1390 tristate "ATI Rage128 display support"
1391 depends on FB && PCI
1392 select FB_CFB_FILLRECT
1393 select FB_CFB_COPYAREA
1394 select FB_CFB_IMAGEBLIT
1395 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1396 select FB_MACMODES if PPC_PMAC
1398 This driver supports graphics boards with the ATI Rage128 chips.
1399 Say Y if you have such a graphics board and read
1400 <file:Documentation/fb/aty128fb.txt>.
1402 To compile this driver as a module, choose M here: the
1403 module will be called aty128fb.
1405 config FB_ATY128_BACKLIGHT
1406 bool "Support for backlight control"
1407 depends on FB_ATY128
1410 Say Y here if you want to control the backlight of your display.
1413 tristate "ATI Mach64 display support" if PCI || ATARI
1414 depends on FB && !SPARC32
1415 select FB_CFB_FILLRECT
1416 select FB_CFB_COPYAREA
1417 select FB_CFB_IMAGEBLIT
1418 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1419 select FB_MACMODES if PPC
1421 This driver supports graphics boards with the ATI Mach64 chips.
1422 Say Y if you have such a graphics board.
1424 To compile this driver as a module, choose M here: the
1425 module will be called atyfb.
1428 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1429 depends on PCI && FB_ATY
1430 default y if SPARC64 && PCI
1432 Say Y here to support use of ATI's 64-bit Rage boards (or other
1433 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1434 framebuffer device. The ATI product support page for these boards
1435 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1437 config FB_ATY_GENERIC_LCD
1438 bool "Mach64 generic LCD support"
1439 depends on FB_ATY_CT
1441 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1442 Rage XC, or Rage XL chipset.
1445 bool "Mach64 GX support" if PCI
1449 Say Y here to support use of the ATI Mach64 Graphics Expression
1450 board (or other boards based on the Mach64 GX chipset) as a
1451 framebuffer device. The ATI product support page for these boards
1453 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1455 config FB_ATY_BACKLIGHT
1456 bool "Support for backlight control"
1460 Say Y here if you want to control the backlight of your display.
1463 tristate "S3 Trio/Virge support"
1464 depends on FB && PCI
1465 select FB_CFB_FILLRECT
1466 select FB_CFB_COPYAREA
1467 select FB_CFB_IMAGEBLIT
1468 select FB_TILEBLITTING
1471 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1473 Driver for graphics boards with S3 Trio / S3 Virge chip.
1476 bool "DDC for S3 support"
1481 Say Y here if you want DDC support for your S3 graphics card.
1484 tristate "S3 Savage support"
1485 depends on FB && PCI
1486 select FB_MODE_HELPERS
1487 select FB_CFB_FILLRECT
1488 select FB_CFB_COPYAREA
1489 select FB_CFB_IMAGEBLIT
1492 This driver supports notebooks and computers with S3 Savage PCI/AGP
1495 Say Y if you have such a graphics card.
1497 To compile this driver as a module, choose M here; the module
1498 will be called savagefb.
1500 config FB_SAVAGE_I2C
1501 bool "Enable DDC2 Support"
1502 depends on FB_SAVAGE
1505 This enables I2C support for S3 Savage Chipsets. This is used
1506 only for getting EDID information from the attached display
1507 allowing for robust video mode handling and switching.
1509 Because fbdev-2.6 requires that drivers must be able to
1510 independently validate video mode parameters, you should say Y
1513 config FB_SAVAGE_ACCEL
1514 bool "Enable Console Acceleration"
1515 depends on FB_SAVAGE
1518 This option will compile in console acceleration support. If
1519 the resulting framebuffer console has bothersome glitches, then
1523 tristate "SiS/XGI display support"
1524 depends on FB && PCI
1525 select FB_CFB_FILLRECT
1526 select FB_CFB_COPYAREA
1527 select FB_CFB_IMAGEBLIT
1528 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1530 This is the frame buffer device driver for the SiS 300, 315, 330
1531 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1532 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1534 To compile this driver as a module, choose M here; the module
1535 will be called sisfb.
1538 bool "SiS 300 series support"
1541 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1544 bool "SiS 315/330/340 series and XGI support"
1547 Say Y here to support use of the SiS 315, 330 and 340 series
1548 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1549 as XGI V3XT, V5, V8 and Z7.
1552 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1553 depends on FB && PCI && X86
1554 select FB_CFB_FILLRECT
1555 select FB_CFB_COPYAREA
1556 select FB_CFB_IMAGEBLIT
1561 This is the frame buffer device driver for Graphics chips of VIA
1562 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1563 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1565 Say Y if you have a VIA UniChrome graphics board.
1567 To compile this driver as a module, choose M here: the
1568 module will be called viafb.
1572 config FB_VIA_DIRECT_PROCFS
1573 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1577 Allow direct hardware access to some output registers via procfs.
1578 This is dangerous but may provide the only chance to get the
1579 correct output device configuration.
1580 Its use is strongly discouraged.
1582 config FB_VIA_X_COMPATIBILITY
1583 bool "X server compatibility"
1587 This option reduces the functionality (power saving, ...) of the
1588 framebuffer to avoid negative impact on the OpenChrome X server.
1589 If you use any X server other than fbdev you should enable this
1590 otherwise it should be safe to disable it and allow using all
1596 tristate "NeoMagic display support"
1597 depends on FB && PCI
1598 select FB_MODE_HELPERS
1599 select FB_CFB_FILLRECT
1600 select FB_CFB_COPYAREA
1601 select FB_CFB_IMAGEBLIT
1604 This driver supports notebooks with NeoMagic PCI chips.
1605 Say Y if you have such a graphics card.
1607 To compile this driver as a module, choose M here: the
1608 module will be called neofb.
1611 tristate "IMG Kyro support"
1612 depends on FB && PCI
1613 select FB_CFB_FILLRECT
1614 select FB_CFB_COPYAREA
1615 select FB_CFB_IMAGEBLIT
1617 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1620 To compile this driver as a module, choose M here: the
1621 module will be called kyrofb.
1624 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1625 depends on FB && PCI
1626 select FB_CFB_IMAGEBLIT
1627 select FB_CFB_FILLRECT
1628 select FB_CFB_COPYAREA
1629 select FB_MODE_HELPERS
1631 This driver supports graphics boards with the 3Dfx Banshee,
1632 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1633 such a graphics board.
1635 To compile this driver as a module, choose M here: the
1636 module will be called tdfxfb.
1638 config FB_3DFX_ACCEL
1639 bool "3Dfx Acceleration functions"
1642 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1643 device driver with acceleration functions.
1646 bool "Enable DDC/I2C support"
1651 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1654 tristate "3Dfx Voodoo Graphics (sst1) support"
1655 depends on FB && PCI
1656 select FB_CFB_FILLRECT
1657 select FB_CFB_COPYAREA
1658 select FB_CFB_IMAGEBLIT
1660 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1661 Voodoo2 (cvg) based graphics card.
1663 To compile this driver as a module, choose M here: the
1664 module will be called sstfb.
1666 WARNING: Do not use any application that uses the 3D engine
1667 (namely glide) while using this driver.
1668 Please read the <file:Documentation/fb/sstfb.txt> for supported
1669 options and other important info support.
1672 tristate "VIA VT8623 support"
1673 depends on FB && PCI
1674 select FB_CFB_FILLRECT
1675 select FB_CFB_COPYAREA
1676 select FB_CFB_IMAGEBLIT
1677 select FB_TILEBLITTING
1680 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1682 Driver for CastleRock integrated graphics core in the
1683 VIA VT8623 [Apollo CLE266] chipset.
1686 tristate "Trident/CyberXXX/CyberBlade support"
1687 depends on FB && PCI
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1692 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1693 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1695 There are also integrated versions of these chips called CyberXXXX,
1696 CyberImage or CyberBlade. These chips are mostly found in laptops
1697 but also on some motherboards including early VIA EPIA motherboards.
1698 For more information, read <file:Documentation/fb/tridentfb.txt>
1700 Say Y if you have such a graphics board.
1702 To compile this driver as a module, choose M here: the
1703 module will be called tridentfb.
1706 tristate "ARK 2000PV support"
1707 depends on FB && PCI
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1711 select FB_TILEBLITTING
1714 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1716 Driver for PCI graphics boards with ARK 2000PV chip
1717 and ICS 5342 RAMDAC.
1720 tristate "Permedia3 support"
1721 depends on FB && PCI
1722 select FB_CFB_FILLRECT
1723 select FB_CFB_COPYAREA
1724 select FB_CFB_IMAGEBLIT
1726 This is the frame buffer device driver for the 3DLabs Permedia3
1727 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1728 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1729 and maybe other boards.
1732 tristate "Fujitsu carmine frame buffer support"
1733 depends on FB && PCI
1734 select FB_CFB_FILLRECT
1735 select FB_CFB_COPYAREA
1736 select FB_CFB_IMAGEBLIT
1738 This is the frame buffer device driver for the Fujitsu Carmine chip.
1739 The driver provides two independent frame buffer devices.
1742 depends on FB_CARMINE
1743 prompt "DRAM timing"
1744 default FB_CARMINE_DRAM_EVAL
1746 config FB_CARMINE_DRAM_EVAL
1747 bool "Eval board timings"
1749 Use timings which work on the eval card.
1751 config CARMINE_DRAM_CUSTOM
1752 bool "Custom board timings"
1754 Use custom board timings.
1758 bool "Au1100 LCD Driver"
1759 depends on (FB = y) && MIPS_ALCHEMY
1760 select FB_CFB_FILLRECT
1761 select FB_CFB_COPYAREA
1762 select FB_CFB_IMAGEBLIT
1764 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1765 various panels and CRTs by passing in kernel cmd line option
1766 au1100fb:panel=<name>.
1769 bool "Au1200/Au1300 LCD Driver"
1770 depends on (FB = y) && MIPS_ALCHEMY
1771 select FB_SYS_FILLRECT
1772 select FB_SYS_COPYAREA
1773 select FB_SYS_IMAGEBLIT
1776 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1777 It can drive various panels and CRTs by passing in kernel cmd line
1778 option au1200fb:panel=<name>.
1781 bool "VIA VT8500 framebuffer support"
1782 depends on (FB = y) && ARM && ARCH_VT8500
1783 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1784 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1785 select FB_SYS_IMAGEBLIT
1786 select FB_MODE_HELPERS
1787 select VIDEOMODE_HELPERS
1789 This is the framebuffer driver for VIA VT8500 integrated LCD
1793 bool "Wondermedia WM8xxx-series frame buffer support"
1794 depends on (FB = y) && ARM && ARCH_VT8500
1795 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1796 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1797 select FB_SYS_IMAGEBLIT
1798 select FB_MODE_HELPERS
1799 select VIDEOMODE_HELPERS
1801 This is the framebuffer driver for WonderMedia WM8xxx-series
1802 integrated LCD controller. This driver covers the WM8505, WM8650
1805 config FB_WMT_GE_ROPS
1806 bool "VT8500/WM8xxx accelerated raster ops support"
1807 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1810 This adds support for accelerated raster operations on the
1811 VIA VT8500 and Wondermedia 85xx series SoCs.
1813 source "drivers/video/geode/Kconfig"
1816 tristate "HD64461 Frame Buffer support"
1817 depends on FB && HD64461
1818 select FB_CFB_FILLRECT
1819 select FB_CFB_COPYAREA
1820 select FB_CFB_IMAGEBLIT
1822 This is the frame buffer device driver for the Hitachi HD64461 LCD
1826 bool "PMAG-AA TURBOchannel framebuffer support"
1827 depends on (FB = y) && TC
1828 select FB_CFB_FILLRECT
1829 select FB_CFB_COPYAREA
1830 select FB_CFB_IMAGEBLIT
1832 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1833 used mainly in the MIPS-based DECstation series.
1836 tristate "PMAG-BA TURBOchannel framebuffer support"
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1843 used mainly in the MIPS-based DECstation series.
1846 tristate "PMAGB-B TURBOchannel framebuffer support"
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1853 in the MIPS-based DECstation series. The card is currently only
1854 supported in 1280x1024x8 mode.
1857 bool "Maxine (Personal DECstation) onboard framebuffer support"
1858 depends on (FB = y) && MACH_DECSTATION
1859 select FB_CFB_FILLRECT
1860 select FB_CFB_COPYAREA
1861 select FB_CFB_IMAGEBLIT
1863 Support for the onboard framebuffer (1024x768x8) in the Personal
1864 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1868 bool "G364 frame buffer support"
1869 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1870 select FB_CFB_FILLRECT
1871 select FB_CFB_COPYAREA
1872 select FB_CFB_IMAGEBLIT
1874 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1875 Olivetti M700-10 systems.
1878 bool "Motorola 68328 native frame buffer support"
1879 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1880 select FB_CFB_FILLRECT
1881 select FB_CFB_COPYAREA
1882 select FB_CFB_IMAGEBLIT
1884 Say Y here if you want to support the built-in frame buffer of
1885 the Motorola 68328 CPU family.
1888 tristate "PXA168/910 LCD framebuffer support"
1889 depends on FB && (CPU_PXA168 || CPU_PXA910)
1890 select FB_CFB_FILLRECT
1891 select FB_CFB_COPYAREA
1892 select FB_CFB_IMAGEBLIT
1894 Frame buffer driver for the built-in LCD controller in the Marvell
1898 tristate "PXA LCD framebuffer support"
1899 depends on FB && ARCH_PXA
1900 select FB_CFB_FILLRECT
1901 select FB_CFB_COPYAREA
1902 select FB_CFB_IMAGEBLIT
1904 Frame buffer driver for the built-in LCD controller in the Intel
1907 This driver is also available as a module ( = code which can be
1908 inserted and removed from the running kernel whenever you want). The
1909 module will be called pxafb. If you want to compile it as a module,
1910 say M here and read <file:Documentation/kbuild/modules.txt>.
1914 config FB_PXA_OVERLAY
1915 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1917 depends on FB_PXA && (PXA27x || PXA3xx)
1919 config FB_PXA_SMARTPANEL
1920 bool "PXA Smartpanel LCD support"
1924 config FB_PXA_PARAMETERS
1925 bool "PXA LCD command line parameters"
1929 Enable the use of kernel command line or module parameters
1930 to configure the physical properties of the LCD panel when
1931 using the PXA LCD driver.
1933 This option allows you to override the panel parameters
1934 supplied by the platform in order to support multiple
1935 different models of flatpanel. If you will only be using a
1936 single model of flatpanel then you can safely leave this
1939 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1942 tristate "PXA3xx 2D graphics accelerator driver"
1945 Kernelspace driver for the 2D graphics controller unit (GCU)
1946 found on PXA3xx processors. There is a counterpart driver in the
1947 DirectFB suite, see http://www.directfb.org/
1949 If you compile this as a module, it will be called pxa3xx_gcu.
1952 tristate "2700G LCD framebuffer support"
1953 depends on FB && ARCH_PXA
1954 select FB_CFB_FILLRECT
1955 select FB_CFB_COPYAREA
1956 select FB_CFB_IMAGEBLIT
1958 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1962 bool "Enable debugging info via debugfs"
1963 depends on FB_MBX && DEBUG_FS
1966 Enable this if you want debugging information using the debug
1967 filesystem (debugfs)
1972 tristate "Freescale DIU framebuffer support"
1973 depends on FB && FSL_SOC
1974 select FB_MODE_HELPERS
1975 select FB_CFB_FILLRECT
1976 select FB_CFB_COPYAREA
1977 select FB_CFB_IMAGEBLIT
1978 select PPC_LIB_RHEAP
1980 Framebuffer driver for the Freescale SoC DIU
1983 tristate "W100 frame buffer support"
1984 depends on FB && ARCH_PXA
1985 select FB_CFB_FILLRECT
1986 select FB_CFB_COPYAREA
1987 select FB_CFB_IMAGEBLIT
1989 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1990 It can also drive the w3220 chip found on iPAQ hx4700.
1992 This driver is also available as a module ( = code which can be
1993 inserted and removed from the running kernel whenever you want). The
1994 module will be called w100fb. If you want to compile it as a module,
1995 say M here and read <file:Documentation/kbuild/modules.txt>.
1999 config FB_SH_MOBILE_LCDC
2000 tristate "SuperH Mobile LCDC framebuffer support"
2001 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2002 select FB_SYS_FILLRECT
2003 select FB_SYS_COPYAREA
2004 select FB_SYS_IMAGEBLIT
2006 select FB_DEFERRED_IO
2008 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2010 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2012 config FB_SH_MOBILE_HDMI
2013 tristate "SuperH Mobile HDMI controller support"
2014 depends on FB_SH_MOBILE_LCDC
2015 select FB_MODE_HELPERS
2020 Driver for the on-chip SH-Mobile HDMI controller.
2023 tristate "Toshiba Mobile IO FrameBuffer support"
2024 depends on FB && MFD_CORE
2025 select FB_CFB_FILLRECT
2026 select FB_CFB_COPYAREA
2027 select FB_CFB_IMAGEBLIT
2029 Frame buffer driver for the Toshiba Mobile IO integrated as found
2030 on the Sharp SL-6000 series
2032 This driver is also available as a module ( = code which can be
2033 inserted and removed from the running kernel whenever you want). The
2034 module will be called tmiofb. If you want to compile it as a module,
2035 say M here and read <file:Documentation/kbuild/modules.txt>.
2039 config FB_TMIO_ACCELL
2040 bool "tmiofb acceleration"
2045 tristate "Samsung S3C framebuffer support"
2046 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2047 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2048 select FB_CFB_FILLRECT
2049 select FB_CFB_COPYAREA
2050 select FB_CFB_IMAGEBLIT
2052 Frame buffer driver for the built-in FB controller in the Samsung
2053 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2054 and the S3C64XX series such as the S3C6400 and S3C6410.
2056 These chips all have the same basic framebuffer design with the
2057 actual capabilities depending on the chip. For instance the S3C6400
2058 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2059 currently only have two.
2061 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2063 config FB_S3C_DEBUG_REGWRITE
2064 bool "Debug register writes"
2067 Show all register writes via pr_debug()
2070 tristate "S3C2410 LCD framebuffer support"
2071 depends on FB && ARCH_S3C24XX
2072 select FB_CFB_FILLRECT
2073 select FB_CFB_COPYAREA
2074 select FB_CFB_IMAGEBLIT
2076 Frame buffer driver for the built-in LCD controller in the Samsung
2079 This driver is also available as a module ( = code which can be
2080 inserted and removed from the running kernel whenever you want). The
2081 module will be called s3c2410fb. If you want to compile it as a module,
2082 say M here and read <file:Documentation/kbuild/modules.txt>.
2085 config FB_S3C2410_DEBUG
2086 bool "S3C2410 lcd debug messages"
2087 depends on FB_S3C2410
2089 Turn on debugging messages. Note that you can set/unset at run time
2093 bool "NUC900 LCD framebuffer support"
2094 depends on FB && ARCH_W90X900
2095 select FB_CFB_FILLRECT
2096 select FB_CFB_COPYAREA
2097 select FB_CFB_IMAGEBLIT
2099 Frame buffer driver for the built-in LCD controller in the Nuvoton
2102 config GPM1040A0_320X240
2103 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2104 depends on FB_NUC900
2107 tristate "Silicon Motion SM501 framebuffer support"
2108 depends on FB && MFD_SM501
2109 select FB_CFB_FILLRECT
2110 select FB_CFB_COPYAREA
2111 select FB_CFB_IMAGEBLIT
2113 Frame buffer driver for the CRT and LCD controllers in the Silicon
2116 This driver is also available as a module ( = code which can be
2117 inserted and removed from the running kernel whenever you want). The
2118 module will be called sm501fb. If you want to compile it as a module,
2119 say M here and read <file:Documentation/kbuild/modules.txt>.
2124 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2125 depends on FB && USB
2126 select FB_MODE_HELPERS
2127 select FB_SYS_FILLRECT
2128 select FB_SYS_COPYAREA
2129 select FB_SYS_IMAGEBLIT
2131 select FB_DEFERRED_IO
2133 This is a kernel framebuffer driver for SMSC UFX USB devices.
2134 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2135 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2137 To compile as a module, choose M here: the module name is smscufx.
2140 tristate "Displaylink USB Framebuffer support"
2141 depends on FB && USB
2142 select FB_MODE_HELPERS
2143 select FB_SYS_FILLRECT
2144 select FB_SYS_COPYAREA
2145 select FB_SYS_IMAGEBLIT
2147 select FB_DEFERRED_IO
2149 This is a kernel framebuffer driver for DisplayLink USB devices.
2150 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2151 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2152 To compile as a module, choose M here: the module name is udlfb.
2154 config FB_IBM_GXT4500
2155 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2156 depends on FB && PPC
2157 select FB_CFB_FILLRECT
2158 select FB_CFB_COPYAREA
2159 select FB_CFB_IMAGEBLIT
2161 Say Y here to enable support for the IBM GXT4000P/6000P and
2162 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2163 found on some IBM System P (pSeries) machines. This driver
2164 doesn't use Geometry Engine GT1000.
2167 tristate "PS3 GPU framebuffer driver"
2168 depends on FB && PS3_PS3AV
2169 select FB_SYS_FILLRECT
2170 select FB_SYS_COPYAREA
2171 select FB_SYS_IMAGEBLIT
2173 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2175 Include support for the virtual frame buffer in the PS3 platform.
2177 config FB_PS3_DEFAULT_SIZE_M
2178 int "PS3 default frame buffer size (in MiB)"
2182 This is the default size (in MiB) of the virtual frame buffer in
2184 The default value can be overridden on the kernel command line
2185 using the "ps3fb" option (e.g. "ps3fb=9M");
2188 tristate "Xilinx frame buffer support"
2189 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2190 select FB_CFB_FILLRECT
2191 select FB_CFB_COPYAREA
2192 select FB_CFB_IMAGEBLIT
2194 Include support for the Xilinx ML300/ML403 reference design
2195 framebuffer. ML300 carries a 640*480 LCD display on the board,
2196 ML403 uses a standard DB15 VGA connector.
2199 tristate "Goldfish Framebuffer"
2200 depends on FB && HAS_DMA
2201 select FB_CFB_FILLRECT
2202 select FB_CFB_COPYAREA
2203 select FB_CFB_IMAGEBLIT
2205 Framebuffer driver for Goldfish Virtual Platform
2208 tristate "Cobalt server LCD frame buffer support"
2209 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2212 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2213 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2214 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2215 select FB_CFB_FILLRECT
2216 select FB_CFB_COPYAREA
2217 select FB_CFB_IMAGEBLIT
2219 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2220 (D)STN/TFT LCD Controller.
2221 Supports display resolutions up to 1024x1024 pixel, grayscale and
2222 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2223 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2224 panels <= 320 pixel horizontal resolution.
2227 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2228 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2229 select FB_CFB_FILLRECT
2230 select FB_CFB_COPYAREA
2231 select FB_CFB_IMAGEBLIT
2232 select FB_CFB_REV_PIXELS_IN_BYTE
2233 select FB_MODE_HELPERS
2234 select VIDEOMODE_HELPERS
2236 This is the frame buffer device driver for the TI LCD controller
2237 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2241 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2243 select FB_SYS_FILLRECT
2244 select FB_SYS_COPYAREA
2245 select FB_SYS_IMAGEBLIT
2248 This is a `virtual' frame buffer device. It operates on a chunk of
2249 unswappable kernel memory instead of on the memory of a graphics
2250 board. This means you cannot see any output sent to this frame
2251 buffer device, while it does consume precious memory. The main use
2252 of this frame buffer device is testing and debugging the frame
2253 buffer subsystem. Do NOT enable it for normal systems! To protect
2254 the innocent, it has to be enabled explicitly at boot time using the
2255 kernel option `video=vfb:'.
2257 To compile this driver as a module, choose M here: the
2258 module will be called vfb. In order to load it, you must use
2259 the vfb_enable=1 option.
2263 config XEN_FBDEV_FRONTEND
2264 tristate "Xen virtual frame buffer support"
2265 depends on FB && XEN
2266 select FB_SYS_FILLRECT
2267 select FB_SYS_COPYAREA
2268 select FB_SYS_IMAGEBLIT
2270 select FB_DEFERRED_IO
2271 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2272 select XEN_XENBUS_FRONTEND
2275 This driver implements the front-end of the Xen virtual
2276 frame buffer driver. It communicates with a back-end
2280 tristate "E-Ink Metronome/8track controller support"
2282 select FB_SYS_FILLRECT
2283 select FB_SYS_COPYAREA
2284 select FB_SYS_IMAGEBLIT
2286 select FB_DEFERRED_IO
2288 This driver implements support for the E-Ink Metronome
2289 controller. The pre-release name for this device was 8track
2290 and could also have been called by some vendors as PVI-nnnn.
2293 tristate "Fujitsu MB862xx GDC support"
2295 depends on PCI || (OF && PPC)
2296 select FB_CFB_FILLRECT
2297 select FB_CFB_COPYAREA
2298 select FB_CFB_IMAGEBLIT
2300 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2303 prompt "GDC variant"
2304 depends on FB_MB862XX
2306 config FB_MB862XX_PCI_GDC
2307 bool "Carmine/Coral-P(A) GDC"
2310 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2311 PCI graphics controller devices.
2313 config FB_MB862XX_LIME
2315 depends on OF && PPC
2316 select FB_FOREIGN_ENDIAN
2317 select FB_LITTLE_ENDIAN
2319 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2323 config FB_MB862XX_I2C
2324 bool "Support I2C bus on MB862XX GDC"
2325 depends on FB_MB862XX && I2C
2328 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2329 driver to support accessing I2C devices on controller's I2C bus.
2330 These are usually some video decoder chips.
2333 tristate "EP93XX frame buffer support"
2334 depends on FB && ARCH_EP93XX
2335 select FB_CFB_FILLRECT
2336 select FB_CFB_COPYAREA
2337 select FB_CFB_IMAGEBLIT
2339 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2340 This driver is also available as a module. The module will be called
2343 config FB_PRE_INIT_FB
2344 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2345 depends on FB && FB_MB862XX_LIME
2347 Select this option if display contents should be inherited as set by
2351 tristate "MSM Framebuffer support"
2352 depends on FB && ARCH_MSM
2353 select FB_CFB_FILLRECT
2354 select FB_CFB_COPYAREA
2355 select FB_CFB_IMAGEBLIT
2358 tristate "MX3 Framebuffer support"
2359 depends on FB && MX3_IPU
2360 select FB_CFB_FILLRECT
2361 select FB_CFB_COPYAREA
2362 select FB_CFB_IMAGEBLIT
2365 This is a framebuffer device for the i.MX31 LCD Controller. So
2366 far only synchronous displays are supported. If you plan to use
2367 an LCD display with your i.MX31 system, say Y here.
2369 config FB_BROADSHEET
2370 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2372 select FB_SYS_FILLRECT
2373 select FB_SYS_COPYAREA
2374 select FB_SYS_IMAGEBLIT
2376 select FB_DEFERRED_IO
2378 This driver implements support for the E-Ink Broadsheet
2379 controller. The release name for this device was Epson S1D13521
2380 and could also have been called by other names when coupled with
2384 tristate "AUO-K190X EPD controller support"
2386 select FB_SYS_FILLRECT
2387 select FB_SYS_COPYAREA
2388 select FB_SYS_IMAGEBLIT
2390 select FB_DEFERRED_IO
2392 Provides support for epaper controllers from the K190X series
2393 of AUO. These controllers can be used to drive epaper displays
2396 This option enables the common support, shared by the individual
2397 controller drivers. You will also have to enable the driver
2398 for the controller type used in your device.
2401 tristate "AUO-K1900 EPD controller support"
2402 depends on FB && FB_AUO_K190X
2404 This driver implements support for the AUO K1900 epd-controller.
2405 This controller can drive Sipix epaper displays but can only do
2406 serial updates, reducing the number of possible frames per second.
2409 tristate "AUO-K1901 EPD controller support"
2410 depends on FB && FB_AUO_K190X
2412 This driver implements support for the AUO K1901 epd-controller.
2413 This controller can drive Sipix epaper displays and supports
2414 concurrent updates, making higher frames per second possible.
2417 tristate "JZ4740 LCD framebuffer support"
2418 depends on FB && MACH_JZ4740
2419 select FB_SYS_FILLRECT
2420 select FB_SYS_COPYAREA
2421 select FB_SYS_IMAGEBLIT
2423 Framebuffer support for the JZ4740 SoC.
2426 tristate "MXS LCD framebuffer support"
2427 depends on FB && ARCH_MXS
2428 select FB_CFB_FILLRECT
2429 select FB_CFB_COPYAREA
2430 select FB_CFB_IMAGEBLIT
2431 select FB_MODE_HELPERS
2432 select VIDEOMODE_HELPERS
2434 Framebuffer support for the MXS SoC.
2436 config FB_PUV3_UNIGFX
2437 tristate "PKUnity v3 Unigfx framebuffer support"
2438 depends on FB && UNICORE32 && ARCH_PUV3
2439 select FB_SYS_FILLRECT
2440 select FB_SYS_COPYAREA
2441 select FB_SYS_IMAGEBLIT
2444 Choose this option if you want to use the Unigfx device as a
2445 framebuffer device. Without the support of PCI & AGP.
2448 tristate "Microsoft Hyper-V Synthetic Video support"
2449 depends on FB && HYPERV
2450 select FB_CFB_FILLRECT
2451 select FB_CFB_COPYAREA
2452 select FB_CFB_IMAGEBLIT
2454 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2457 bool "Simple framebuffer support"
2459 select FB_CFB_FILLRECT
2460 select FB_CFB_COPYAREA
2461 select FB_CFB_IMAGEBLIT
2463 Say Y if you want support for a simple frame-buffer.
2465 This driver assumes that the display hardware has been initialized
2466 before the kernel boots, and the kernel will simply render to the
2467 pre-allocated frame buffer surface.
2469 Configuration re: surface address, size, and format must be provided
2470 through device tree, or plain old platform data.
2472 source "drivers/video/omap/Kconfig"
2473 source "drivers/video/omap2/Kconfig"
2474 source "drivers/video/exynos/Kconfig"
2475 source "drivers/video/mmp/Kconfig"
2476 source "drivers/video/backlight/Kconfig"
2479 source "drivers/video/console/Kconfig"
2482 if FB || SGI_NEWPORT_CONSOLE
2483 source "drivers/video/logo/Kconfig"
2486 config FB_SH_MOBILE_MERAM
2487 tristate "SuperH Mobile MERAM read ahead support"
2488 depends on (SUPERH || ARCH_SHMOBILE)
2489 select GENERIC_ALLOCATOR
2491 Enable MERAM support for the SuperH controller.
2493 This will allow for caching of the framebuffer to provide more
2494 reliable access under heavy main memory bus traffic situations.
2495 Up to 4 memory channels can be configured, allowing 4 RGB or
2496 2 YCbCr framebuffers to be configured.
2499 tristate "Solomon SSD1307 framebuffer support"
2500 depends on FB && I2C
2504 select FB_SYS_FILLRECT
2505 select FB_SYS_COPYAREA
2506 select FB_SYS_IMAGEBLIT
2507 select FB_DEFERRED_IO
2510 This driver implements support for the Solomon SSD1307
2511 OLED controller over I2C.