6 tristate "Support for frame buffer devices"
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
42 bool "Enable firmware EDID"
46 This enables access to the EDID transferred from the firmware.
47 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
48 transfers do not work for your driver and if you are using
49 nvidiafb, i810fb or savagefb.
51 In general, choosing Y for this option is safe. If you
52 experience extremely long delays while booting before you get
53 something on your display, try setting this to N. Matrox cards in
54 combination with certain motherboards and monitors are known to
55 suffer from this problem.
70 config FB_BOOT_VESA_SUPPORT
75 If true, at least one selected framebuffer driver can take advantage
76 of VESA video modes set at an early boot stage via the vga= parameter.
78 config FB_CFB_FILLRECT
83 Include the cfb_fillrect function for generic software rectangle
84 filling. This is used by drivers that don't provide their own
85 (accelerated) version.
87 config FB_CFB_COPYAREA
92 Include the cfb_copyarea function for generic software area copying.
93 This is used by drivers that don't provide their own (accelerated)
96 config FB_CFB_IMAGEBLIT
101 Include the cfb_imageblit function for generic software image
102 blitting. This is used by drivers that don't provide their own
103 (accelerated) version.
105 config FB_CFB_REV_PIXELS_IN_BYTE
110 Allow generic frame-buffer functions to work on displays with 1, 2
111 and 4 bits per pixel depths which has opposite order of pixels in
112 byte order to bytes in long order.
114 config FB_SYS_FILLRECT
119 Include the sys_fillrect function for generic software rectangle
120 filling. This is used by drivers that don't provide their own
121 (accelerated) version and the framebuffer is in system RAM.
123 config FB_SYS_COPYAREA
128 Include the sys_copyarea function for generic software area copying.
129 This is used by drivers that don't provide their own (accelerated)
130 version and the framebuffer is in system RAM.
132 config FB_SYS_IMAGEBLIT
137 Include the sys_imageblit function for generic software image
138 blitting. This is used by drivers that don't provide their own
139 (accelerated) version and the framebuffer is in system RAM.
141 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
146 Allow generic frame-buffer to provide get_fb_unmapped_area
149 menuconfig FB_FOREIGN_ENDIAN
150 bool "Framebuffer foreign endianness support"
153 This menu will let you enable support for the framebuffers with
154 non-native endianness (e.g. Little-Endian framebuffer on a
155 Big-Endian machine). Most probably you don't have such hardware,
156 so it's safe to say "n" here.
159 prompt "Choice endianness support"
160 depends on FB_FOREIGN_ENDIAN
162 config FB_BOTH_ENDIAN
163 bool "Support for Big- and Little-Endian framebuffers"
166 bool "Support for Big-Endian framebuffers only"
168 config FB_LITTLE_ENDIAN
169 bool "Support for Little-Endian framebuffers only"
178 config FB_DEFERRED_IO
185 depends on FB_DEFERRED_IO
192 Common utility functions useful to fbdev drivers of VGA-based
203 select BACKLIGHT_LCD_SUPPORT
204 select BACKLIGHT_CLASS_DEVICE
207 config FB_MODE_HELPERS
208 bool "Enable Video Mode Handling Helpers"
212 This enables functions for handling video modes using the
213 Generalized Timing Formula and the EDID parser. A few drivers rely
214 on this feature such as the radeonfb, rivafb, and the i810fb. If
215 your driver does not take advantage of this feature, choosing Y will
216 just increase the kernel size by about 5K.
218 config FB_TILEBLITTING
219 bool "Enable Tile Blitting Support"
223 This enables tile blitting. Tile blitting is a drawing technique
224 where the screen is divided into rectangular sections (tiles), whereas
225 the standard blitting divides the screen into pixels. Because the
226 default drawing element is a tile, drawing functions will be passed
227 parameters in terms of number of tiles instead of number of pixels.
228 For example, to draw a single character, instead of using bitmaps,
229 an index to an array of bitmaps will be used. To clear or move a
230 rectangular section of a screen, the rectangle will be described in
231 terms of number of tiles in the x- and y-axis.
233 This is particularly important to one driver, matroxfb. If
236 comment "Frame buffer hardware drivers"
240 tristate "Aeroflex Gaisler framebuffer support"
241 depends on FB && SPARC
242 select FB_CFB_FILLRECT
243 select FB_CFB_COPYAREA
244 select FB_CFB_IMAGEBLIT
246 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
249 tristate "Cirrus Logic support"
250 depends on FB && (ZORRO || PCI)
251 select FB_CFB_FILLRECT
252 select FB_CFB_COPYAREA
253 select FB_CFB_IMAGEBLIT
255 This enables support for Cirrus Logic GD542x/543x based boards on
256 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
258 If you have a PCI-based system, this enables support for these
259 chips: GD-543x, GD-544x, GD-5480.
261 Please read the file <file:Documentation/fb/cirrusfb.txt>.
263 Say N unless you have such a graphics board or plan to get one
264 before you next recompile the kernel.
267 tristate "Permedia2 support"
268 depends on FB && ((AMIGA && BROKEN) || PCI)
269 select FB_CFB_FILLRECT
270 select FB_CFB_COPYAREA
271 select FB_CFB_IMAGEBLIT
273 This is the frame buffer device driver for cards based on
274 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
275 The driver was tested on the following cards:
276 Diamond FireGL 1000 PRO AGP
277 ELSA Gloria Synergy PCI
278 Appian Jeronimo PRO (both heads) PCI
279 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
280 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
281 ASK Graphic Blaster Exxtreme AGP
283 To compile this driver as a module, choose M here: the
284 module will be called pm2fb.
286 config FB_PM2_FIFO_DISCONNECT
287 bool "enable FIFO disconnect feature"
288 depends on FB_PM2 && PCI
290 Support the Permedia2 FIFO disconnect feature.
293 tristate "ARM PrimeCell PL110 support"
294 depends on ARM || ARM64 || COMPILE_TEST
295 depends on FB && ARM_AMBA && HAS_IOMEM
296 select FB_CFB_FILLRECT
297 select FB_CFB_COPYAREA
298 select FB_CFB_IMAGEBLIT
299 select FB_MODE_HELPERS if OF
300 select VIDEOMODE_HELPERS if OF
301 select BACKLIGHT_LCD_SUPPORT if OF
302 select BACKLIGHT_CLASS_DEVICE if OF
304 This framebuffer device driver is for the ARM PrimeCell PL110
305 Colour LCD controller. ARM PrimeCells provide the building
306 blocks for System on a Chip devices.
308 If you want to compile this as a module (=code which can be
309 inserted into and removed from the running kernel), say M
310 here and read <file:Documentation/kbuild/modules.txt>. The module
311 will be called amba-clcd.
313 # Helper logic selected only by the ARM Versatile platform family.
314 config PLAT_VERSATILE_CLCD
315 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
317 depends on FB_ARMCLCD && FB=y
322 bool "Acorn VIDC support"
323 depends on (FB = y) && ARM && ARCH_ACORN
324 select FB_CFB_FILLRECT
325 select FB_CFB_COPYAREA
326 select FB_CFB_IMAGEBLIT
328 This is the frame buffer device driver for the Acorn VIDC graphics
329 hardware found in Acorn RISC PCs and other ARM-based machines. If
332 config FB_CLPS711X_OLD
334 select FB_CFB_FILLRECT
335 select FB_CFB_COPYAREA
336 select FB_CFB_IMAGEBLIT
339 tristate "CLPS711X LCD support"
340 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
341 select FB_CLPS711X_OLD if ARCH_CLPS711X && !ARCH_MULTIPLATFORM
342 select BACKLIGHT_LCD_SUPPORT
343 select FB_MODE_HELPERS
344 select FB_SYS_FILLRECT
345 select FB_SYS_COPYAREA
346 select FB_SYS_IMAGEBLIT
347 select LCD_CLASS_DEVICE
348 select VIDEOMODE_HELPERS
350 Say Y to enable the Framebuffer driver for the Cirrus Logic
354 bool "SA-1100 LCD support"
355 depends on (FB = y) && ARM && ARCH_SA1100
356 select FB_CFB_FILLRECT
357 select FB_CFB_COPYAREA
358 select FB_CFB_IMAGEBLIT
360 This is a framebuffer device for the SA-1100 LCD Controller.
361 See <http://www.linux-fbdev.org/> for information on framebuffer
364 If you plan to use the LCD display with your SA-1100 system, say
368 tristate "Freescale i.MX1/21/25/27 LCD support"
369 depends on FB && ARCH_MXC
370 select BACKLIGHT_LCD_SUPPORT
371 select LCD_CLASS_DEVICE
372 select FB_CFB_FILLRECT
373 select FB_CFB_COPYAREA
374 select FB_CFB_IMAGEBLIT
375 select FB_MODE_HELPERS
376 select VIDEOMODE_HELPERS
379 tristate "CyberPro 2000/2010/5000 support"
380 depends on FB && PCI && (BROKEN || !SPARC64)
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
385 This enables support for the Integraphics CyberPro 20x0 and 5000
386 VGA chips used in the Rebel.com Netwinder and other machines.
387 Say Y if you have a NetWinder or a graphics card containing this
388 device, otherwise say N.
390 config FB_CYBER2000_DDC
391 bool "DDC for CyberPro support"
392 depends on FB_CYBER2000
396 Say Y here if you want DDC support for your CyberPro graphics
397 card. This is only I2C bus support, driver does not use EDID.
399 config FB_CYBER2000_I2C
400 bool "CyberPro 2000/2010/5000 I2C support"
401 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
402 depends on I2C=y || FB_CYBER2000=m
405 Enable support for the I2C video decoder interface on the
406 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
407 on the Netwinder machines for the SAA7111 video capture.
411 depends on (FB = y) && APOLLO
413 select FB_CFB_FILLRECT
414 select FB_CFB_IMAGEBLIT
418 depends on (FB = y) && Q40
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
425 tristate "Amiga native chipset support"
426 depends on FB && AMIGA
428 This is the frame buffer device driver for the builtin graphics
429 chipset found in Amigas.
431 To compile this driver as a module, choose M here: the
432 module will be called amifb.
435 bool "Amiga OCS chipset support"
438 This enables support for the original Agnus and Denise video chips,
439 found in the Amiga 1000 and most A500's and A2000's. If you intend
440 to run Linux on any of these systems, say Y; otherwise say N.
443 bool "Amiga ECS chipset support"
446 This enables support for the Enhanced Chip Set, found in later
447 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
448 you intend to run Linux on any of these systems, say Y; otherwise
452 bool "Amiga AGA chipset support"
455 This enables support for the Advanced Graphics Architecture (also
456 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
457 and CD32. If you intend to run Linux on any of these systems, say Y;
461 bool "Amiga FrameMaster II/Rainbow II support"
462 depends on (FB = y) && ZORRO
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
467 This is the frame buffer device driver for the Amiga FrameMaster
468 card from BSC (exhibited 1992 but not shipped as a CBM product).
471 tristate "Arc Monochrome LCD board support"
473 select FB_SYS_FILLRECT
474 select FB_SYS_COPYAREA
475 select FB_SYS_IMAGEBLIT
478 This enables support for the Arc Monochrome LCD board. The board
479 is based on the KS-108 lcd controller and is typically a matrix
480 of 2*n chips. This driver was tested with a 128x64 panel. This
481 driver supports it for use with x86 SBCs through a 16 bit GPIO
482 interface (8 bit data, 8 bit control). If you anticipate using
483 this driver, say Y or M; otherwise say N. You must specify the
484 GPIO IO address to be used for setting control and data.
487 bool "Atari native chipset support"
488 depends on (FB = y) && ATARI
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the builtin graphics
494 chipset found in Ataris.
497 bool "Open Firmware frame buffer device support"
498 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 Say Y if you want support with Open Firmware for your graphics
508 bool "Apple \"control\" display support"
509 depends on (FB = y) && PPC_PMAC && PPC32
510 select FB_CFB_FILLRECT
511 select FB_CFB_COPYAREA
512 select FB_CFB_IMAGEBLIT
515 This driver supports a frame buffer for the graphics adapter in the
516 Power Macintosh 7300 and others.
519 bool "Apple \"platinum\" display support"
520 depends on (FB = y) && PPC_PMAC && PPC32
521 select FB_CFB_FILLRECT
522 select FB_CFB_COPYAREA
523 select FB_CFB_IMAGEBLIT
526 This driver supports a frame buffer for the "platinum" graphics
527 adapter in some Power Macintoshes.
530 bool "Apple \"valkyrie\" display support"
531 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
537 This driver supports a frame buffer for the "valkyrie" graphics
538 adapter in some Power Macintoshes.
541 bool "Chips 65550 display support"
542 depends on (FB = y) && PPC32 && PCI
543 select FB_CFB_FILLRECT
544 select FB_CFB_COPYAREA
545 select FB_CFB_IMAGEBLIT
547 This is the frame buffer device driver for the Chips & Technologies
548 65550 graphics chip in PowerBooks.
551 bool "Asiliant (Chips) 69000 display support"
552 depends on (FB = y) && PCI
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
557 This is the frame buffer device driver for the Asiliant 69030 chipset
560 bool "IMS Twin Turbo display support"
561 depends on (FB = y) && PCI
562 select FB_CFB_IMAGEBLIT
563 select FB_MACMODES if PPC
565 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
566 many Macintosh and compatible computers.
569 tristate "VGA 16-color graphics support"
570 depends on FB && (X86 || PPC)
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 select FONT_8x16 if FRAMEBUFFER_CONSOLE
577 This is the frame buffer device driver for VGA 16 color graphic
578 cards. Say Y if you have such a card.
580 To compile this driver as a module, choose M here: the
581 module will be called vga16fb.
583 config FB_BF54X_LQ043
584 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
585 depends on FB && (BF54x) && !BF542
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
590 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
592 config FB_BFIN_T350MCQB
593 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
594 depends on FB && BLACKFIN
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
601 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
602 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
604 config FB_BFIN_LQ035Q1
605 tristate "SHARP LQ035Q1DH02 TFT LCD"
606 depends on FB && BLACKFIN && SPI
607 select FB_CFB_FILLRECT
608 select FB_CFB_COPYAREA
609 select FB_CFB_IMAGEBLIT
612 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
613 the Blackfin Landscape LCD EZ-Extender Card.
614 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
615 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
617 To compile this driver as a module, choose M here: the
618 module will be called bfin-lq035q1-fb.
620 config FB_BF537_LQ035
621 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
622 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
623 select FB_CFB_FILLRECT
624 select FB_CFB_COPYAREA
625 select FB_CFB_IMAGEBLIT
628 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
631 To compile this driver as a module, choose M here: the
632 module will be called bf537-lq035.
635 tristate "Blackfin ADV7393 Video encoder"
636 depends on FB && BLACKFIN
638 select FB_CFB_FILLRECT
639 select FB_CFB_COPYAREA
640 select FB_CFB_IMAGEBLIT
642 This is the framebuffer device for a ADV7393 video encoder
643 attached to a Blackfin on the PPI port.
644 If your Blackfin board has a ADV7393 select Y.
646 To compile this driver as a module, choose M here: the
647 module will be called bfin_adv7393fb.
650 prompt "Video mode support"
651 depends on FB_BFIN_7393
661 bool 'NTSC 640x480 (Experimental)'
664 bool 'PAL 640x480 (Experimental)'
667 bool 'NTSC 720x480 YCbCR input'
670 bool 'PAL 720x576 YCbCR input'
675 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
676 depends on (FB_BFIN_7393)
677 default ADV7393_1XMEM
687 tristate "HP STI frame buffer device support"
688 depends on FB && PARISC
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
694 STI refers to the HP "Standard Text Interface" which is a set of
695 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
696 Enabling this option will implement the linux framebuffer device
697 using calls to the STI BIOS routines for initialisation.
699 If you enable this option, you will get a planar framebuffer device
700 /dev/fb which will work on the most common HP graphic cards of the
701 NGLE family, including the artist chips (in the 7xx and Bxxx series),
702 HCRX, HCRX24, CRX, CRX24 and VisEG series.
704 It is safe to enable this option, so you should probably say "Y".
707 bool "Generic Macintosh display support"
708 depends on (FB = y) && MAC
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
716 depends on (FB = y) && DIO
717 select FB_CFB_IMAGEBLIT
721 tristate "TGA/SFB+ framebuffer support"
722 depends on FB && (ALPHA || TC)
723 select FB_CFB_FILLRECT
724 select FB_CFB_COPYAREA
725 select FB_CFB_IMAGEBLIT
728 This is the frame buffer device driver for generic TGA and SFB+
729 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
730 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
731 TURBOchannel cards, also known as PMAGD-A, -B and -C.
733 Due to hardware limitations ZLX-E2 and E3 cards are not supported
734 for DECstation 5000/200 systems. Additionally due to firmware
735 limitations these cards may cause troubles with booting DECstation
736 5000/240 and /260 systems, but are fully supported under Linux if
737 you manage to get it going. ;-)
739 Say Y if you have one of those.
742 tristate "Userspace VESA VGA graphics support"
743 depends on FB && CONNECTOR
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
747 select FB_MODE_HELPERS
749 This is the frame buffer driver for generic VBE 2.0 compliant
750 graphic cards. It can also take advantage of VBE 3.0 features,
751 such as refresh rate adjustment.
753 This driver generally provides more features than vesafb but
754 requires a userspace helper application called 'v86d'. See
755 <file:Documentation/fb/uvesafb.txt> for more information.
760 bool "VESA VGA graphics support"
761 depends on (FB = y) && X86
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
765 select FB_BOOT_VESA_SUPPORT
767 This is the frame buffer device driver for generic VESA 2.0
768 compliant graphic cards. The older VESA 1.2 cards are not supported.
769 You will get a boot time penguin logo at no additional cost. Please
770 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
773 bool "EFI-based Framebuffer Support"
774 depends on (FB = y) && !IA64 && EFI
775 select DRM_PANEL_ORIENTATION_QUIRKS
776 select FB_CFB_FILLRECT
777 select FB_CFB_COPYAREA
778 select FB_CFB_IMAGEBLIT
780 This is the EFI frame buffer device driver. If the firmware on
781 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
782 using the EFI framebuffer as your console.
785 tristate "N411 Apollo/Hecuba devkit support"
786 depends on FB && X86 && MMU
787 select FB_SYS_FILLRECT
788 select FB_SYS_COPYAREA
789 select FB_SYS_IMAGEBLIT
791 select FB_DEFERRED_IO
794 This enables support for the Apollo display controller in its
795 Hecuba form using the n411 devkit.
798 tristate "Hercules mono graphics support"
801 Say Y here if you have a Hercules mono graphics card.
803 To compile this driver as a module, choose M here: the
804 module will be called hgafb.
806 As this card technology is at least 25 years old,
807 most people will answer N here.
810 bool "SGI Graphics Backend frame buffer support"
811 depends on (FB = y) && SGI_IP32
812 select FB_CFB_FILLRECT
813 select FB_CFB_COPYAREA
814 select FB_CFB_IMAGEBLIT
816 This is the frame buffer device driver for SGI Graphics Backend.
817 This chip is used in SGI O2 and Visual Workstation 320/540.
820 int "Video memory size in MB"
824 This is the amount of memory reserved for the framebuffer,
825 which can be any value between 1MB and 8MB.
828 bool "SBUS and UPA framebuffers"
829 depends on (FB = y) && SPARC
831 Say Y if you want support for SBUS or UPA based frame buffer device.
835 depends on (FB = y) && (SPARC && FB_SBUS)
836 select FB_CFB_FILLRECT
837 select FB_CFB_COPYAREA
838 select FB_CFB_IMAGEBLIT
840 This is the frame buffer device driver for the BWtwo frame buffer.
843 bool "CGthree support"
844 depends on (FB = y) && (SPARC && FB_SBUS)
845 select FB_CFB_FILLRECT
846 select FB_CFB_COPYAREA
847 select FB_CFB_IMAGEBLIT
849 This is the frame buffer device driver for the CGthree frame buffer.
852 bool "CGsix (GX,TurboGX) support"
853 depends on (FB = y) && (SPARC && FB_SBUS)
854 select FB_CFB_COPYAREA
855 select FB_CFB_IMAGEBLIT
857 This is the frame buffer device driver for the CGsix (GX, TurboGX)
861 bool "Creator/Creator3D/Elite3D support"
862 depends on FB_SBUS && SPARC64
863 select FB_CFB_COPYAREA
864 select FB_CFB_IMAGEBLIT
866 This is the frame buffer device driver for the Creator, Creator3D,
867 and Elite3D graphics boards.
870 bool "TCX (SS4/SS5 only) support"
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the frame buffer device driver for the TCX 24/8bit frame
880 bool "CGfourteen (SX) support"
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the frame buffer device driver for the CGfourteen frame
887 buffer on Desktop SPARCsystems with the SX graphics option.
890 bool "P9100 (Sparcbook 3 only) support"
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
896 This is the frame buffer device driver for the P9100 card
897 supported on Sparcbook 3 machines.
900 bool "Leo (ZX) support"
902 select FB_CFB_FILLRECT
903 select FB_CFB_COPYAREA
904 select FB_CFB_IMAGEBLIT
906 This is the frame buffer device driver for the SBUS-based Sun ZX
907 (leo) frame buffer cards.
910 bool "Sun XVR-500 3DLABS Wildcat support"
911 depends on (FB = y) && PCI && SPARC64
912 select FB_CFB_FILLRECT
913 select FB_CFB_COPYAREA
914 select FB_CFB_IMAGEBLIT
916 This is the framebuffer device for the Sun XVR-500 and similar
917 graphics cards based upon the 3DLABS Wildcat chipset. The driver
918 only works on sparc64 systems where the system firmware has
919 mostly initialized the card already. It is treated as a
920 completely dumb framebuffer device.
923 bool "Sun XVR-2500 3DLABS Wildcat support"
924 depends on (FB = y) && PCI && SPARC64
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 This is the framebuffer device for the Sun XVR-2500 and similar
930 graphics cards based upon the 3DLABS Wildcat chipset. The driver
931 only works on sparc64 systems where the system firmware has
932 mostly initialized the card already. It is treated as a
933 completely dumb framebuffer device.
936 bool "Sun XVR-1000 support"
937 depends on (FB = y) && SPARC64
938 select FB_CFB_FILLRECT
939 select FB_CFB_COPYAREA
940 select FB_CFB_IMAGEBLIT
942 This is the framebuffer device for the Sun XVR-1000 and similar
943 graphics cards. The driver only works on sparc64 systems where
944 the system firmware has mostly initialized the card already. It
945 is treated as a completely dumb framebuffer device.
948 tristate "NEC PowerVR 2 display support"
949 depends on FB && SH_DREAMCAST
950 select FB_CFB_FILLRECT
951 select FB_CFB_COPYAREA
952 select FB_CFB_IMAGEBLIT
954 Say Y here if you have a PowerVR 2 card in your box. If you plan to
955 run linux on your Dreamcast, you will have to say Y here.
956 This driver may or may not work on other PowerVR 2 cards, but is
957 totally untested. Use at your own risk. If unsure, say N.
959 To compile this driver as a module, choose M here: the
960 module will be called pvr2fb.
962 You can pass several parameters to the driver at boot time or at
963 module load time. The parameters look like "video=pvr2:XXX", where
964 the meaning of XXX can be found at the end of the main source file
965 (<file:drivers/video/pvr2fb.c>). Please see the file
966 <file:Documentation/fb/pvr2fb.txt>.
969 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
970 depends on FB && HAS_DMA
971 select FB_CFB_FILLRECT
972 select FB_CFB_COPYAREA
973 select FB_CFB_IMAGEBLIT
975 This enables support for the OpenCores VGA/LCD core.
977 The OpenCores VGA/LCD core is typically used together with
978 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
979 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
981 The source code and specification for the core is available at
982 <http://opencores.org/project,vga_lcd>
985 tristate "Epson S1D13XXX framebuffer support"
987 select FB_CFB_FILLRECT
988 select FB_CFB_COPYAREA
989 select FB_CFB_IMAGEBLIT
991 Support for S1D13XXX framebuffer device family (currently only
992 working with S1D13806). Product specs at
993 <http://vdc.epson.com/>
996 tristate "AT91/AT32 LCD Controller support"
997 depends on FB && HAVE_FB_ATMEL
999 select FB_CFB_FILLRECT
1000 select FB_CFB_COPYAREA
1001 select FB_CFB_IMAGEBLIT
1002 select FB_MODE_HELPERS
1003 select VIDEOMODE_HELPERS
1005 This enables support for the AT91/AT32 LCD Controller.
1008 tristate "nVidia Framebuffer Support"
1009 depends on FB && PCI
1010 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1011 select FB_MODE_HELPERS
1012 select FB_CFB_FILLRECT
1013 select FB_CFB_COPYAREA
1014 select FB_CFB_IMAGEBLIT
1018 This driver supports graphics boards with the nVidia chips, TNT
1019 and newer. For very old chipsets, such as the RIVA128, then use
1021 Say Y if you have such a graphics board.
1023 To compile this driver as a module, choose M here: the
1024 module will be called nvidiafb.
1026 config FB_NVIDIA_I2C
1027 bool "Enable DDC Support"
1028 depends on FB_NVIDIA
1031 This enables I2C support for nVidia Chipsets. This is used
1032 only for getting EDID information from the attached display
1033 allowing for robust video mode handling and switching.
1035 Because fbdev-2.6 requires that drivers must be able to
1036 independently validate video mode parameters, you should say Y
1039 config FB_NVIDIA_DEBUG
1040 bool "Lots of debug output"
1041 depends on FB_NVIDIA
1044 Say Y here if you want the nVidia driver to output all sorts
1045 of debugging information to provide to the maintainer when
1046 something goes wrong.
1048 config FB_NVIDIA_BACKLIGHT
1049 bool "Support for backlight control"
1050 depends on FB_NVIDIA
1053 Say Y here if you want to control the backlight of your display.
1056 tristate "nVidia Riva support"
1057 depends on FB && PCI
1058 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1059 select FB_MODE_HELPERS
1060 select FB_CFB_FILLRECT
1061 select FB_CFB_COPYAREA
1062 select FB_CFB_IMAGEBLIT
1066 This driver supports graphics boards with the nVidia Riva/Geforce
1068 Say Y if you have such a graphics board.
1070 To compile this driver as a module, choose M here: the
1071 module will be called rivafb.
1074 bool "Enable DDC Support"
1078 This enables I2C support for nVidia Chipsets. This is used
1079 only for getting EDID information from the attached display
1080 allowing for robust video mode handling and switching.
1082 Because fbdev-2.6 requires that drivers must be able to
1083 independently validate video mode parameters, you should say Y
1086 config FB_RIVA_DEBUG
1087 bool "Lots of debug output"
1091 Say Y here if you want the Riva driver to output all sorts
1092 of debugging information to provide to the maintainer when
1093 something goes wrong.
1095 config FB_RIVA_BACKLIGHT
1096 bool "Support for backlight control"
1100 Say Y here if you want to control the backlight of your display.
1103 tristate "Intel740 support"
1104 depends on FB && PCI
1105 select FB_MODE_HELPERS
1106 select FB_CFB_FILLRECT
1107 select FB_CFB_COPYAREA
1108 select FB_CFB_IMAGEBLIT
1112 This driver supports graphics cards based on Intel740 chip.
1115 tristate "Intel 810/815 support"
1116 depends on FB && PCI && X86_32 && AGP_INTEL
1117 select FB_MODE_HELPERS
1118 select FB_CFB_FILLRECT
1119 select FB_CFB_COPYAREA
1120 select FB_CFB_IMAGEBLIT
1123 This driver supports the on-board graphics built in to the Intel 810
1124 and 815 chipsets. Say Y if you have and plan to use such a board.
1126 To compile this driver as a module, choose M here: the
1127 module will be called i810fb.
1129 For more information, please read
1130 <file:Documentation/fb/intel810.txt>
1133 bool "use VESA Generalized Timing Formula"
1136 If you say Y, then the VESA standard, Generalized Timing Formula
1137 or GTF, will be used to calculate the required video timing values
1138 per video mode. Since the GTF allows nondiscrete timings
1139 (nondiscrete being a range of values as opposed to discrete being a
1140 set of values), you'll be able to use any combination of horizontal
1141 and vertical resolutions, and vertical refresh rates without having
1142 to specify your own timing parameters. This is especially useful
1143 to maximize the performance of an aging display, or if you just
1144 have a display with nonstandard dimensions. A VESA compliant
1145 monitor is recommended, but can still work with non-compliant ones.
1146 If you need or want this, then select this option. The timings may
1147 not be compliant with Intel's recommended values. Use at your own
1150 If you say N, the driver will revert to discrete video timings
1151 using a set recommended by Intel in their documentation.
1156 bool "Enable DDC Support"
1157 depends on FB_I810 && FB_I810_GTF
1161 tristate "Intel LE80578 (Vermilion) support"
1162 depends on FB && PCI && X86
1163 select FB_MODE_HELPERS
1164 select FB_CFB_FILLRECT
1165 select FB_CFB_COPYAREA
1166 select FB_CFB_IMAGEBLIT
1168 This driver supports the LE80578 (Vermilion Range) chipset
1170 config FB_CARILLO_RANCH
1171 tristate "Intel Carillo Ranch support"
1172 depends on FB_LE80578 && FB && PCI && X86
1174 This driver supports the LE80578 (Carillo Ranch) board
1177 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1178 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1179 select FB_MODE_HELPERS
1180 select FB_CFB_FILLRECT
1181 select FB_CFB_COPYAREA
1182 select FB_CFB_IMAGEBLIT
1183 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1184 depends on !DRM_I915
1186 This driver supports the on-board graphics built in to the Intel
1187 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1188 Say Y if you have and plan to use such a board.
1190 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
1192 To compile this driver as a module, choose M here: the
1193 module will be called intelfb.
1195 For more information, please read <file:Documentation/fb/intelfb.txt>
1197 config FB_INTEL_DEBUG
1198 bool "Intel driver Debug Messages"
1201 Say Y here if you want the Intel driver to output all sorts
1202 of debugging information to provide to the maintainer when
1203 something goes wrong.
1206 bool "DDC/I2C for Intel framebuffer support"
1211 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1214 tristate "Matrox acceleration"
1215 depends on FB && PCI
1216 select FB_CFB_FILLRECT
1217 select FB_CFB_COPYAREA
1218 select FB_CFB_IMAGEBLIT
1219 select FB_TILEBLITTING
1220 select FB_MACMODES if PPC_PMAC
1222 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1223 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1224 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1225 Matrox G400, G450 or G550 card in your box.
1227 To compile this driver as a module, choose M here: the
1228 module will be called matroxfb.
1230 You can pass several parameters to the driver at boot time or at
1231 module load time. The parameters look like "video=matroxfb:XXX", and
1232 are described in <file:Documentation/fb/matroxfb.txt>.
1234 config FB_MATROX_MILLENIUM
1235 bool "Millennium I/II support"
1236 depends on FB_MATROX
1238 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1239 video card. If you select "Advanced lowlevel driver options" below,
1240 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1241 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1242 also use font widths different from 8.
1244 config FB_MATROX_MYSTIQUE
1245 bool "Mystique support"
1246 depends on FB_MATROX
1248 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1249 video card. If you select "Advanced lowlevel driver options" below,
1250 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1251 packed pixel and 32 bpp packed pixel. You can also use font widths
1255 bool "G100/G200/G400/G450/G550 support"
1256 depends on FB_MATROX
1258 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1259 video card. If you select "Advanced lowlevel driver options", you
1260 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1261 pixel and 32 bpp packed pixel. You can also use font widths
1264 If you need support for G400 secondary head, you must say Y to
1265 "Matrox I2C support" and "G400 second head support" right below.
1266 G450/G550 secondary head and digital output are supported without
1269 The driver starts in monitor mode. You must use the matroxset tool
1270 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1271 swap primary and secondary head outputs, or to change output mode.
1272 Secondary head driver always start in 640x480 resolution and you
1273 must use fbset to change it.
1275 Do not forget that second head supports only 16 and 32 bpp
1276 packed pixels, so it is a good idea to compile them into the kernel
1277 too. You can use only some font widths, as the driver uses generic
1278 painting procedures (the secondary head does not use acceleration
1281 G450/G550 hardware can display TV picture only from secondary CRTC,
1282 and it performs no scaling, so picture must have 525 or 625 lines.
1284 config FB_MATROX_I2C
1285 tristate "Matrox I2C support"
1286 depends on FB_MATROX
1289 This drivers creates I2C buses which are needed for accessing the
1290 DDC (I2C) bus present on all Matroxes, an I2C bus which
1291 interconnects Matrox optional devices, like MGA-TVO on G200 and
1292 G400, and the secondary head DDC bus, present on G400 only.
1294 You can say Y or M here if you want to experiment with monitor
1295 detection code. You must say Y or M here if you want to use either
1296 second head of G400 or MGA-TVO on G200 or G400.
1298 If you compile it as module, it will create a module named
1301 config FB_MATROX_MAVEN
1302 tristate "G400 second head support"
1303 depends on FB_MATROX_G && FB_MATROX_I2C
1305 WARNING !!! This support does not work with G450 !!!
1307 Say Y or M here if you want to use a secondary head (meaning two
1308 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1309 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1310 secondary head output is blanked while you are in X. With XFree
1311 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1312 the fbdev driver on first head and the fbdev driver on second head.
1314 If you compile it as module, two modules are created,
1315 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1316 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1317 also load i2c-matroxfb to get it to run.
1319 The driver starts in monitor mode and you must use the matroxset
1321 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1322 PAL or NTSC or to swap primary and secondary head outputs.
1323 Secondary head driver also always start in 640x480 resolution, you
1324 must use fbset to change it.
1326 Also do not forget that second head supports only 16 and 32 bpp
1327 packed pixels, so it is a good idea to compile them into the kernel
1328 too. You can use only some font widths, as the driver uses generic
1329 painting procedures (the secondary head does not use acceleration
1333 tristate "ATI Radeon display support"
1334 depends on FB && PCI
1335 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1336 select FB_MODE_HELPERS
1337 select FB_CFB_FILLRECT
1338 select FB_CFB_COPYAREA
1339 select FB_CFB_IMAGEBLIT
1340 select FB_MACMODES if PPC
1342 Choose this option if you want to use an ATI Radeon graphics card as
1343 a framebuffer device. There are both PCI and AGP versions. You
1344 don't need to choose this to run the Radeon in plain VGA mode.
1346 There is a product page at
1347 http://products.amd.com/en-us/GraphicCardResult.aspx
1349 config FB_RADEON_I2C
1350 bool "DDC/I2C for ATI Radeon support"
1351 depends on FB_RADEON
1355 Say Y here if you want DDC/I2C support for your Radeon board.
1357 config FB_RADEON_BACKLIGHT
1358 bool "Support for backlight control"
1359 depends on FB_RADEON
1362 Say Y here if you want to control the backlight of your display.
1364 config FB_RADEON_DEBUG
1365 bool "Lots of debug output from Radeon driver"
1366 depends on FB_RADEON
1369 Say Y here if you want the Radeon driver to output all sorts
1370 of debugging information to provide to the maintainer when
1371 something goes wrong.
1374 tristate "ATI Rage128 display support"
1375 depends on FB && PCI
1376 select FB_CFB_FILLRECT
1377 select FB_CFB_COPYAREA
1378 select FB_CFB_IMAGEBLIT
1379 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1380 select FB_MACMODES if PPC_PMAC
1382 This driver supports graphics boards with the ATI Rage128 chips.
1383 Say Y if you have such a graphics board and read
1384 <file:Documentation/fb/aty128fb.txt>.
1386 To compile this driver as a module, choose M here: the
1387 module will be called aty128fb.
1389 config FB_ATY128_BACKLIGHT
1390 bool "Support for backlight control"
1391 depends on FB_ATY128
1394 Say Y here if you want to control the backlight of your display.
1397 tristate "ATI Mach64 display support" if PCI || ATARI
1398 depends on FB && !SPARC32
1399 select FB_CFB_FILLRECT
1400 select FB_CFB_COPYAREA
1401 select FB_CFB_IMAGEBLIT
1402 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1403 select FB_MACMODES if PPC
1405 This driver supports graphics boards with the ATI Mach64 chips.
1406 Say Y if you have such a graphics board.
1408 To compile this driver as a module, choose M here: the
1409 module will be called atyfb.
1412 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1413 depends on PCI && FB_ATY
1414 default y if SPARC64 && PCI
1416 Say Y here to support use of ATI's 64-bit Rage boards (or other
1417 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1418 framebuffer device. The ATI product support page for these boards
1419 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1421 config FB_ATY_GENERIC_LCD
1422 bool "Mach64 generic LCD support"
1423 depends on FB_ATY_CT
1425 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1426 Rage XC, or Rage XL chipset.
1429 bool "Mach64 GX support" if PCI
1433 Say Y here to support use of the ATI Mach64 Graphics Expression
1434 board (or other boards based on the Mach64 GX chipset) as a
1435 framebuffer device. The ATI product support page for these boards
1437 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1439 config FB_ATY_BACKLIGHT
1440 bool "Support for backlight control"
1444 Say Y here if you want to control the backlight of your display.
1447 tristate "S3 Trio/Virge support"
1448 depends on FB && PCI
1449 select FB_CFB_FILLRECT
1450 select FB_CFB_COPYAREA
1451 select FB_CFB_IMAGEBLIT
1452 select FB_TILEBLITTING
1455 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1457 Driver for graphics boards with S3 Trio / S3 Virge chip.
1460 bool "DDC for S3 support"
1465 Say Y here if you want DDC support for your S3 graphics card.
1468 tristate "S3 Savage support"
1469 depends on FB && PCI
1470 select FB_MODE_HELPERS
1471 select FB_CFB_FILLRECT
1472 select FB_CFB_COPYAREA
1473 select FB_CFB_IMAGEBLIT
1476 This driver supports notebooks and computers with S3 Savage PCI/AGP
1479 Say Y if you have such a graphics card.
1481 To compile this driver as a module, choose M here; the module
1482 will be called savagefb.
1484 config FB_SAVAGE_I2C
1485 bool "Enable DDC2 Support"
1486 depends on FB_SAVAGE
1489 This enables I2C support for S3 Savage Chipsets. This is used
1490 only for getting EDID information from the attached display
1491 allowing for robust video mode handling and switching.
1493 Because fbdev-2.6 requires that drivers must be able to
1494 independently validate video mode parameters, you should say Y
1497 config FB_SAVAGE_ACCEL
1498 bool "Enable Console Acceleration"
1499 depends on FB_SAVAGE
1502 This option will compile in console acceleration support. If
1503 the resulting framebuffer console has bothersome glitches, then
1507 tristate "SiS/XGI display support"
1508 depends on FB && PCI
1509 select FB_CFB_FILLRECT
1510 select FB_CFB_COPYAREA
1511 select FB_CFB_IMAGEBLIT
1512 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1513 select FB_SIS_300 if !FB_SIS_315
1515 This is the frame buffer device driver for the SiS 300, 315, 330
1516 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1517 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1519 To compile this driver as a module, choose M here; the module
1520 will be called sisfb.
1523 bool "SiS 300 series support"
1526 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1529 bool "SiS 315/330/340 series and XGI support"
1532 Say Y here to support use of the SiS 315, 330 and 340 series
1533 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1534 as XGI V3XT, V5, V8 and Z7.
1537 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1538 depends on FB && PCI && X86 && GPIOLIB && I2C
1539 select FB_CFB_FILLRECT
1540 select FB_CFB_COPYAREA
1541 select FB_CFB_IMAGEBLIT
1544 This is the frame buffer device driver for Graphics chips of VIA
1545 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1546 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1548 Say Y if you have a VIA UniChrome graphics board.
1550 To compile this driver as a module, choose M here: the
1551 module will be called viafb.
1555 config FB_VIA_DIRECT_PROCFS
1556 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1560 Allow direct hardware access to some output registers via procfs.
1561 This is dangerous but may provide the only chance to get the
1562 correct output device configuration.
1563 Its use is strongly discouraged.
1565 config FB_VIA_X_COMPATIBILITY
1566 bool "X server compatibility"
1570 This option reduces the functionality (power saving, ...) of the
1571 framebuffer to avoid negative impact on the OpenChrome X server.
1572 If you use any X server other than fbdev you should enable this
1573 otherwise it should be safe to disable it and allow using all
1579 tristate "NeoMagic display support"
1580 depends on FB && PCI
1581 select FB_MODE_HELPERS
1582 select FB_CFB_FILLRECT
1583 select FB_CFB_COPYAREA
1584 select FB_CFB_IMAGEBLIT
1587 This driver supports notebooks with NeoMagic PCI chips.
1588 Say Y if you have such a graphics card.
1590 To compile this driver as a module, choose M here: the
1591 module will be called neofb.
1594 tristate "IMG Kyro support"
1595 depends on FB && PCI
1596 select FB_CFB_FILLRECT
1597 select FB_CFB_COPYAREA
1598 select FB_CFB_IMAGEBLIT
1600 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1603 To compile this driver as a module, choose M here: the
1604 module will be called kyrofb.
1607 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1608 depends on FB && PCI
1609 select FB_CFB_IMAGEBLIT
1610 select FB_CFB_FILLRECT
1611 select FB_CFB_COPYAREA
1612 select FB_MODE_HELPERS
1614 This driver supports graphics boards with the 3Dfx Banshee,
1615 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1616 such a graphics board.
1618 To compile this driver as a module, choose M here: the
1619 module will be called tdfxfb.
1621 config FB_3DFX_ACCEL
1622 bool "3Dfx Acceleration functions"
1625 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1626 device driver with acceleration functions.
1629 bool "Enable DDC/I2C support"
1634 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1637 tristate "3Dfx Voodoo Graphics (sst1) support"
1638 depends on FB && PCI
1639 select FB_CFB_FILLRECT
1640 select FB_CFB_COPYAREA
1641 select FB_CFB_IMAGEBLIT
1643 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1644 Voodoo2 (cvg) based graphics card.
1646 To compile this driver as a module, choose M here: the
1647 module will be called sstfb.
1649 WARNING: Do not use any application that uses the 3D engine
1650 (namely glide) while using this driver.
1651 Please read the <file:Documentation/fb/sstfb.txt> for supported
1652 options and other important info support.
1655 tristate "VIA VT8623 support"
1656 depends on FB && PCI
1657 select FB_CFB_FILLRECT
1658 select FB_CFB_COPYAREA
1659 select FB_CFB_IMAGEBLIT
1660 select FB_TILEBLITTING
1663 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1665 Driver for CastleRock integrated graphics core in the
1666 VIA VT8623 [Apollo CLE266] chipset.
1669 tristate "Trident/CyberXXX/CyberBlade support"
1670 depends on FB && PCI
1671 select FB_CFB_FILLRECT
1672 select FB_CFB_COPYAREA
1673 select FB_CFB_IMAGEBLIT
1675 select FB_MODE_HELPERS
1677 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1678 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1680 There are also integrated versions of these chips called CyberXXXX,
1681 CyberImage or CyberBlade. These chips are mostly found in laptops
1682 but also on some motherboards including early VIA EPIA motherboards.
1683 For more information, read <file:Documentation/fb/tridentfb.txt>
1685 Say Y if you have such a graphics board.
1687 To compile this driver as a module, choose M here: the
1688 module will be called tridentfb.
1691 tristate "ARK 2000PV support"
1692 depends on FB && PCI
1693 select FB_CFB_FILLRECT
1694 select FB_CFB_COPYAREA
1695 select FB_CFB_IMAGEBLIT
1696 select FB_TILEBLITTING
1699 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1701 Driver for PCI graphics boards with ARK 2000PV chip
1702 and ICS 5342 RAMDAC.
1705 tristate "Permedia3 support"
1706 depends on FB && PCI
1707 select FB_CFB_FILLRECT
1708 select FB_CFB_COPYAREA
1709 select FB_CFB_IMAGEBLIT
1711 This is the frame buffer device driver for the 3DLabs Permedia3
1712 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1713 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1714 and maybe other boards.
1717 tristate "Fujitsu carmine frame buffer support"
1718 depends on FB && PCI
1719 select FB_CFB_FILLRECT
1720 select FB_CFB_COPYAREA
1721 select FB_CFB_IMAGEBLIT
1723 This is the frame buffer device driver for the Fujitsu Carmine chip.
1724 The driver provides two independent frame buffer devices.
1727 depends on FB_CARMINE
1728 prompt "DRAM timing"
1729 default FB_CARMINE_DRAM_EVAL
1731 config FB_CARMINE_DRAM_EVAL
1732 bool "Eval board timings"
1734 Use timings which work on the eval card.
1736 config CARMINE_DRAM_CUSTOM
1737 bool "Custom board timings"
1739 Use custom board timings.
1743 bool "Au1100 LCD Driver"
1744 depends on (FB = y) && MIPS_ALCHEMY
1745 select FB_CFB_FILLRECT
1746 select FB_CFB_COPYAREA
1747 select FB_CFB_IMAGEBLIT
1749 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1750 various panels and CRTs by passing in kernel cmd line option
1751 au1100fb:panel=<name>.
1754 bool "Au1200/Au1300 LCD Driver"
1755 depends on (FB = y) && MIPS_ALCHEMY
1756 select FB_SYS_FILLRECT
1757 select FB_SYS_COPYAREA
1758 select FB_SYS_IMAGEBLIT
1761 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1762 It can drive various panels and CRTs by passing in kernel cmd line
1763 option au1200fb:panel=<name>.
1766 bool "VIA VT8500 framebuffer support"
1767 depends on (FB = y) && ARM && ARCH_VT8500
1768 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1769 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1770 select FB_SYS_IMAGEBLIT
1771 select FB_MODE_HELPERS
1772 select VIDEOMODE_HELPERS
1774 This is the framebuffer driver for VIA VT8500 integrated LCD
1778 bool "Wondermedia WM8xxx-series frame buffer support"
1779 depends on (FB = y) && ARM && ARCH_VT8500
1780 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1781 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1782 select FB_SYS_IMAGEBLIT
1783 select FB_MODE_HELPERS
1784 select VIDEOMODE_HELPERS
1786 This is the framebuffer driver for WonderMedia WM8xxx-series
1787 integrated LCD controller. This driver covers the WM8505, WM8650
1790 config FB_WMT_GE_ROPS
1791 bool "VT8500/WM8xxx accelerated raster ops support"
1792 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1795 This adds support for accelerated raster operations on the
1796 VIA VT8500 and Wondermedia 85xx series SoCs.
1798 source "drivers/video/fbdev/geode/Kconfig"
1801 tristate "HD64461 Frame Buffer support"
1802 depends on FB && HD64461
1803 select FB_CFB_FILLRECT
1804 select FB_CFB_COPYAREA
1805 select FB_CFB_IMAGEBLIT
1807 This is the frame buffer device driver for the Hitachi HD64461 LCD
1811 tristate "PMAG-AA TURBOchannel framebuffer support"
1813 select FB_CFB_FILLRECT
1814 select FB_CFB_COPYAREA
1815 select FB_CFB_IMAGEBLIT
1817 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1818 used mainly in the MIPS-based DECstation series.
1821 tristate "PMAG-BA TURBOchannel framebuffer support"
1823 select FB_CFB_FILLRECT
1824 select FB_CFB_COPYAREA
1825 select FB_CFB_IMAGEBLIT
1827 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1828 used mainly in the MIPS-based DECstation series.
1831 tristate "PMAGB-B TURBOchannel framebuffer support"
1833 select FB_CFB_FILLRECT
1834 select FB_CFB_COPYAREA
1835 select FB_CFB_IMAGEBLIT
1837 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1838 in the MIPS-based DECstation series. The card is currently only
1839 supported in 1280x1024x8 mode.
1842 bool "Maxine (Personal DECstation) onboard framebuffer support"
1843 depends on (FB = y) && MACH_DECSTATION
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 Support for the onboard framebuffer (1024x768x8) in the Personal
1849 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1853 bool "G364 frame buffer support"
1854 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1855 select FB_CFB_FILLRECT
1856 select FB_CFB_COPYAREA
1857 select FB_CFB_IMAGEBLIT
1859 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1860 Olivetti M700-10 systems.
1863 bool "Motorola 68328 native frame buffer support"
1864 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1865 select FB_CFB_FILLRECT
1866 select FB_CFB_COPYAREA
1867 select FB_CFB_IMAGEBLIT
1869 Say Y here if you want to support the built-in frame buffer of
1870 the Motorola 68328 CPU family.
1873 tristate "PXA168/910 LCD framebuffer support"
1874 depends on FB && (CPU_PXA168 || CPU_PXA910)
1875 select FB_CFB_FILLRECT
1876 select FB_CFB_COPYAREA
1877 select FB_CFB_IMAGEBLIT
1879 Frame buffer driver for the built-in LCD controller in the Marvell
1883 tristate "PXA LCD framebuffer support"
1884 depends on FB && ARCH_PXA
1885 select FB_CFB_FILLRECT
1886 select FB_CFB_COPYAREA
1887 select FB_CFB_IMAGEBLIT
1888 select VIDEOMODE_HELPERS if OF
1889 select FB_MODE_HELPERS if OF
1891 Frame buffer driver for the built-in LCD controller in the Intel
1894 This driver is also available as a module ( = code which can be
1895 inserted and removed from the running kernel whenever you want). The
1896 module will be called pxafb. If you want to compile it as a module,
1897 say M here and read <file:Documentation/kbuild/modules.txt>.
1901 config FB_PXA_OVERLAY
1902 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1904 depends on FB_PXA && (PXA27x || PXA3xx)
1906 config FB_PXA_SMARTPANEL
1907 bool "PXA Smartpanel LCD support"
1911 config FB_PXA_PARAMETERS
1912 bool "PXA LCD command line parameters"
1916 Enable the use of kernel command line or module parameters
1917 to configure the physical properties of the LCD panel when
1918 using the PXA LCD driver.
1920 This option allows you to override the panel parameters
1921 supplied by the platform in order to support multiple
1922 different models of flatpanel. If you will only be using a
1923 single model of flatpanel then you can safely leave this
1926 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1929 tristate "PXA3xx 2D graphics accelerator driver"
1932 Kernelspace driver for the 2D graphics controller unit (GCU)
1933 found on PXA3xx processors. There is a counterpart driver in the
1934 DirectFB suite, see http://www.directfb.org/
1936 If you compile this as a module, it will be called pxa3xx_gcu.
1939 tristate "2700G LCD framebuffer support"
1940 depends on FB && ARCH_PXA
1941 select FB_CFB_FILLRECT
1942 select FB_CFB_COPYAREA
1943 select FB_CFB_IMAGEBLIT
1945 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1949 bool "Enable debugging info via debugfs"
1950 depends on FB_MBX && DEBUG_FS
1953 Enable this if you want debugging information using the debug
1954 filesystem (debugfs)
1959 tristate "Freescale DIU framebuffer support"
1960 depends on FB && FSL_SOC
1961 select FB_MODE_HELPERS
1962 select FB_CFB_FILLRECT
1963 select FB_CFB_COPYAREA
1964 select FB_CFB_IMAGEBLIT
1965 select PPC_LIB_RHEAP
1967 Framebuffer driver for the Freescale SoC DIU
1970 tristate "W100 frame buffer support"
1971 depends on FB && ARCH_PXA
1972 select FB_CFB_FILLRECT
1973 select FB_CFB_COPYAREA
1974 select FB_CFB_IMAGEBLIT
1976 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1977 It can also drive the w3220 chip found on iPAQ hx4700.
1979 This driver is also available as a module ( = code which can be
1980 inserted and removed from the running kernel whenever you want). The
1981 module will be called w100fb. If you want to compile it as a module,
1982 say M here and read <file:Documentation/kbuild/modules.txt>.
1986 config FB_SH_MOBILE_LCDC
1987 tristate "SuperH Mobile LCDC framebuffer support"
1988 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1989 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1990 select FB_SYS_FILLRECT
1991 select FB_SYS_COPYAREA
1992 select FB_SYS_IMAGEBLIT
1994 select FB_DEFERRED_IO
1997 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2000 tristate "Toshiba Mobile IO FrameBuffer support"
2001 depends on FB && (MFD_TMIO || COMPILE_TEST)
2002 select FB_CFB_FILLRECT
2003 select FB_CFB_COPYAREA
2004 select FB_CFB_IMAGEBLIT
2006 Frame buffer driver for the Toshiba Mobile IO integrated as found
2007 on the Sharp SL-6000 series
2009 This driver is also available as a module ( = code which can be
2010 inserted and removed from the running kernel whenever you want). The
2011 module will be called tmiofb. If you want to compile it as a module,
2012 say M here and read <file:Documentation/kbuild/modules.txt>.
2016 config FB_TMIO_ACCELL
2017 bool "tmiofb acceleration"
2022 tristate "Samsung S3C framebuffer support"
2023 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2024 ARCH_S5PV210 || ARCH_EXYNOS)
2025 select FB_CFB_FILLRECT
2026 select FB_CFB_COPYAREA
2027 select FB_CFB_IMAGEBLIT
2029 Frame buffer driver for the built-in FB controller in the Samsung
2030 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2031 and the S3C64XX series such as the S3C6400 and S3C6410.
2033 These chips all have the same basic framebuffer design with the
2034 actual capabilities depending on the chip. For instance the S3C6400
2035 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2036 currently only have two.
2038 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2040 config FB_S3C_DEBUG_REGWRITE
2041 bool "Debug register writes"
2044 Show all register writes via pr_debug()
2047 tristate "S3C2410 LCD framebuffer support"
2048 depends on FB && ARCH_S3C24XX
2049 select FB_CFB_FILLRECT
2050 select FB_CFB_COPYAREA
2051 select FB_CFB_IMAGEBLIT
2053 Frame buffer driver for the built-in LCD controller in the Samsung
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 s3c2410fb. If you want to compile it as a module,
2059 say M here and read <file:Documentation/kbuild/modules.txt>.
2062 config FB_S3C2410_DEBUG
2063 bool "S3C2410 lcd debug messages"
2064 depends on FB_S3C2410
2066 Turn on debugging messages. Note that you can set/unset at run time
2070 tristate "NUC900 LCD framebuffer support"
2071 depends on FB && ARCH_W90X900
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 Nuvoton
2079 config GPM1040A0_320X240
2080 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2081 depends on FB_NUC900
2084 tristate "Silicon Motion SM501 framebuffer support"
2085 depends on FB && MFD_SM501
2086 select FB_CFB_FILLRECT
2087 select FB_CFB_COPYAREA
2088 select FB_CFB_IMAGEBLIT
2090 Frame buffer driver for the CRT and LCD controllers in the Silicon
2093 This driver is also available as a module ( = code which can be
2094 inserted and removed from the running kernel whenever you want). The
2095 module will be called sm501fb. If you want to compile it as a module,
2096 say M here and read <file:Documentation/kbuild/modules.txt>.
2101 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2102 depends on FB && USB
2103 select FB_MODE_HELPERS
2104 select FB_SYS_FILLRECT
2105 select FB_SYS_COPYAREA
2106 select FB_SYS_IMAGEBLIT
2108 select FB_DEFERRED_IO
2110 This is a kernel framebuffer driver for SMSC UFX USB devices.
2111 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2112 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2114 To compile as a module, choose M here: the module name is smscufx.
2117 tristate "Displaylink USB Framebuffer support"
2118 depends on FB && USB
2119 select FB_MODE_HELPERS
2120 select FB_SYS_FILLRECT
2121 select FB_SYS_COPYAREA
2122 select FB_SYS_IMAGEBLIT
2124 select FB_DEFERRED_IO
2126 This is a kernel framebuffer driver for DisplayLink USB devices.
2127 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2128 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2129 To compile as a module, choose M here: the module name is udlfb.
2131 config FB_IBM_GXT4500
2132 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2134 select FB_CFB_FILLRECT
2135 select FB_CFB_COPYAREA
2136 select FB_CFB_IMAGEBLIT
2138 Say Y here to enable support for the IBM GXT4000P/6000P and
2139 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2140 found on some IBM System P (pSeries) machines. This driver
2141 doesn't use Geometry Engine GT1000. This driver also supports
2142 AGP Fire GL2/3/4 cards on x86.
2145 tristate "PS3 GPU framebuffer driver"
2146 depends on FB && PS3_PS3AV
2147 select FB_SYS_FILLRECT
2148 select FB_SYS_COPYAREA
2149 select FB_SYS_IMAGEBLIT
2152 Include support for the virtual frame buffer in the PS3 platform.
2154 config FB_PS3_DEFAULT_SIZE_M
2155 int "PS3 default frame buffer size (in MiB)"
2159 This is the default size (in MiB) of the virtual frame buffer in
2161 The default value can be overridden on the kernel command line
2162 using the "ps3fb" option (e.g. "ps3fb=9M");
2165 tristate "Xilinx frame buffer support"
2166 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
2167 select FB_CFB_FILLRECT
2168 select FB_CFB_COPYAREA
2169 select FB_CFB_IMAGEBLIT
2171 Include support for the Xilinx ML300/ML403 reference design
2172 framebuffer. ML300 carries a 640*480 LCD display on the board,
2173 ML403 uses a standard DB15 VGA connector.
2176 tristate "Goldfish Framebuffer"
2177 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2178 select FB_CFB_FILLRECT
2179 select FB_CFB_COPYAREA
2180 select FB_CFB_IMAGEBLIT
2182 Framebuffer driver for Goldfish Virtual Platform
2185 tristate "Cobalt server LCD frame buffer support"
2186 depends on FB && MIPS_COBALT
2189 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2190 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2191 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2192 select FB_CFB_FILLRECT
2193 select FB_CFB_COPYAREA
2194 select FB_CFB_IMAGEBLIT
2196 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2197 (D)STN/TFT LCD Controller.
2198 Supports display resolutions up to 1024x1024 pixel, grayscale and
2199 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2200 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2201 panels <= 320 pixel horizontal resolution.
2204 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2205 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2206 select FB_CFB_FILLRECT
2207 select FB_CFB_COPYAREA
2208 select FB_CFB_IMAGEBLIT
2209 select FB_CFB_REV_PIXELS_IN_BYTE
2210 select FB_MODE_HELPERS
2211 select VIDEOMODE_HELPERS
2213 This is the frame buffer device driver for the TI LCD controller
2214 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2218 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2220 select FB_SYS_FILLRECT
2221 select FB_SYS_COPYAREA
2222 select FB_SYS_IMAGEBLIT
2225 This is a `virtual' frame buffer device. It operates on a chunk of
2226 unswappable kernel memory instead of on the memory of a graphics
2227 board. This means you cannot see any output sent to this frame
2228 buffer device, while it does consume precious memory. The main use
2229 of this frame buffer device is testing and debugging the frame
2230 buffer subsystem. Do NOT enable it for normal systems! To protect
2231 the innocent, it has to be enabled explicitly at boot time using the
2232 kernel option `video=vfb:'.
2234 To compile this driver as a module, choose M here: the
2235 module will be called vfb. In order to load it, you must use
2236 the vfb_enable=1 option.
2240 config XEN_FBDEV_FRONTEND
2241 tristate "Xen virtual frame buffer support"
2242 depends on FB && XEN
2243 select FB_SYS_FILLRECT
2244 select FB_SYS_COPYAREA
2245 select FB_SYS_IMAGEBLIT
2247 select FB_DEFERRED_IO
2248 select XEN_XENBUS_FRONTEND
2251 This driver implements the front-end of the Xen virtual
2252 frame buffer driver. It communicates with a back-end
2256 tristate "E-Ink Metronome/8track controller support"
2258 select FB_SYS_FILLRECT
2259 select FB_SYS_COPYAREA
2260 select FB_SYS_IMAGEBLIT
2262 select FB_DEFERRED_IO
2264 This driver implements support for the E-Ink Metronome
2265 controller. The pre-release name for this device was 8track
2266 and could also have been called by some vendors as PVI-nnnn.
2269 tristate "Fujitsu MB862xx GDC support"
2271 depends on PCI || (OF && PPC)
2272 select FB_CFB_FILLRECT
2273 select FB_CFB_COPYAREA
2274 select FB_CFB_IMAGEBLIT
2276 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2279 prompt "GDC variant"
2280 depends on FB_MB862XX
2282 config FB_MB862XX_PCI_GDC
2283 bool "Carmine/Coral-P(A) GDC"
2286 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2287 PCI graphics controller devices.
2289 config FB_MB862XX_LIME
2291 depends on OF && PPC
2292 select FB_FOREIGN_ENDIAN
2293 select FB_LITTLE_ENDIAN
2295 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2299 config FB_MB862XX_I2C
2300 bool "Support I2C bus on MB862XX GDC"
2301 depends on FB_MB862XX && I2C
2302 depends on FB_MB862XX=m || I2C=y
2305 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2306 driver to support accessing I2C devices on controller's I2C bus.
2307 These are usually some video decoder chips.
2310 tristate "EP93XX frame buffer support"
2311 depends on FB && ARCH_EP93XX
2312 select FB_CFB_FILLRECT
2313 select FB_CFB_COPYAREA
2314 select FB_CFB_IMAGEBLIT
2316 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2317 This driver is also available as a module. The module will be called
2320 config FB_PRE_INIT_FB
2321 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2322 depends on FB && FB_MB862XX_LIME
2324 Select this option if display contents should be inherited as set by
2328 tristate "MX3 Framebuffer support"
2329 depends on FB && MX3_IPU
2330 select BACKLIGHT_CLASS_DEVICE
2331 select BACKLIGHT_LCD_SUPPORT
2332 select FB_CFB_FILLRECT
2333 select FB_CFB_COPYAREA
2334 select FB_CFB_IMAGEBLIT
2337 This is a framebuffer device for the i.MX31 LCD Controller. So
2338 far only synchronous displays are supported. If you plan to use
2339 an LCD display with your i.MX31 system, say Y here.
2341 config FB_BROADSHEET
2342 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2344 select FB_SYS_FILLRECT
2345 select FB_SYS_COPYAREA
2346 select FB_SYS_IMAGEBLIT
2348 select FB_DEFERRED_IO
2350 This driver implements support for the E-Ink Broadsheet
2351 controller. The release name for this device was Epson S1D13521
2352 and could also have been called by other names when coupled with
2356 tristate "AUO-K190X EPD controller support"
2358 select FB_SYS_FILLRECT
2359 select FB_SYS_COPYAREA
2360 select FB_SYS_IMAGEBLIT
2362 select FB_DEFERRED_IO
2364 Provides support for epaper controllers from the K190X series
2365 of AUO. These controllers can be used to drive epaper displays
2368 This option enables the common support, shared by the individual
2369 controller drivers. You will also have to enable the driver
2370 for the controller type used in your device.
2373 tristate "AUO-K1900 EPD controller support"
2374 depends on FB && FB_AUO_K190X
2376 This driver implements support for the AUO K1900 epd-controller.
2377 This controller can drive Sipix epaper displays but can only do
2378 serial updates, reducing the number of possible frames per second.
2381 tristate "AUO-K1901 EPD controller support"
2382 depends on FB && FB_AUO_K190X
2384 This driver implements support for the AUO K1901 epd-controller.
2385 This controller can drive Sipix epaper displays and supports
2386 concurrent updates, making higher frames per second possible.
2389 tristate "JZ4740 LCD framebuffer support"
2390 depends on FB && MACH_JZ4740
2391 select FB_SYS_FILLRECT
2392 select FB_SYS_COPYAREA
2393 select FB_SYS_IMAGEBLIT
2395 Framebuffer support for the JZ4740 SoC.
2398 tristate "MXS LCD framebuffer support"
2399 depends on FB && (ARCH_MXS || ARCH_MXC)
2400 select FB_CFB_FILLRECT
2401 select FB_CFB_COPYAREA
2402 select FB_CFB_IMAGEBLIT
2403 select FB_MODE_HELPERS
2404 select VIDEOMODE_HELPERS
2406 Framebuffer support for the MXS SoC.
2408 config FB_PUV3_UNIGFX
2409 tristate "PKUnity v3 Unigfx framebuffer support"
2410 depends on FB && UNICORE32 && ARCH_PUV3
2411 select FB_SYS_FILLRECT
2412 select FB_SYS_COPYAREA
2413 select FB_SYS_IMAGEBLIT
2416 Choose this option if you want to use the Unigfx device as a
2417 framebuffer device. Without the support of PCI & AGP.
2420 tristate "Microsoft Hyper-V Synthetic Video support"
2421 depends on FB && HYPERV
2422 select FB_CFB_FILLRECT
2423 select FB_CFB_COPYAREA
2424 select FB_CFB_IMAGEBLIT
2426 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2429 bool "Simple framebuffer support"
2431 select FB_CFB_FILLRECT
2432 select FB_CFB_COPYAREA
2433 select FB_CFB_IMAGEBLIT
2435 Say Y if you want support for a simple frame-buffer.
2437 This driver assumes that the display hardware has been initialized
2438 before the kernel boots, and the kernel will simply render to the
2439 pre-allocated frame buffer surface.
2441 Configuration re: surface address, size, and format must be provided
2442 through device tree, or plain old platform data.
2444 source "drivers/video/fbdev/omap/Kconfig"
2445 source "drivers/video/fbdev/omap2/Kconfig"
2446 source "drivers/video/fbdev/mmp/Kconfig"
2448 config FB_SH_MOBILE_MERAM
2449 tristate "SuperH Mobile MERAM read ahead support"
2450 depends on (SUPERH || ARCH_SHMOBILE)
2451 select GENERIC_ALLOCATOR
2453 Enable MERAM support for the SuperH controller.
2455 This will allow for caching of the framebuffer to provide more
2456 reliable access under heavy main memory bus traffic situations.
2457 Up to 4 memory channels can be configured, allowing 4 RGB or
2458 2 YCbCr framebuffers to be configured.
2461 tristate "Solomon SSD1307 framebuffer support"
2462 depends on FB && I2C
2464 depends on GPIOLIB || COMPILE_TEST
2466 select FB_SYS_FILLRECT
2467 select FB_SYS_COPYAREA
2468 select FB_SYS_IMAGEBLIT
2469 select FB_DEFERRED_IO
2473 This driver implements support for the Solomon SSD1307
2474 OLED controller over I2C.
2477 tristate "Silicon Motion SM712 framebuffer support"
2478 depends on FB && PCI
2479 select FB_CFB_FILLRECT
2480 select FB_CFB_COPYAREA
2481 select FB_CFB_IMAGEBLIT
2483 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2486 This driver is also available as a module. The module will be
2487 called sm712fb. If you want to compile it as a module, say M
2488 here and read <file:Documentation/kbuild/modules.txt>.