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
1162 tristate "Intel LE80578 (Vermilion) support"
1163 depends on FB && PCI && X86
1164 select FB_MODE_HELPERS
1165 select FB_CFB_FILLRECT
1166 select FB_CFB_COPYAREA
1167 select FB_CFB_IMAGEBLIT
1169 This driver supports the LE80578 (Vermilion Range) chipset
1171 config FB_CARILLO_RANCH
1172 tristate "Intel Carillo Ranch support"
1173 depends on FB_LE80578 && FB && PCI && X86
1175 This driver supports the LE80578 (Carillo Ranch) board
1178 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1179 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1180 select FB_MODE_HELPERS
1181 select FB_CFB_FILLRECT
1182 select FB_CFB_COPYAREA
1183 select FB_CFB_IMAGEBLIT
1184 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1185 depends on !DRM_I915
1187 This driver supports the on-board graphics built in to the Intel
1188 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1189 Say Y if you have and plan to use such a board.
1191 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
1193 To compile this driver as a module, choose M here: the
1194 module will be called intelfb.
1196 For more information, please read <file:Documentation/fb/intelfb.txt>
1198 config FB_INTEL_DEBUG
1199 bool "Intel driver Debug Messages"
1202 Say Y here if you want the Intel driver to output all sorts
1203 of debugging information to provide to the maintainer when
1204 something goes wrong.
1207 bool "DDC/I2C for Intel framebuffer support"
1212 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1215 tristate "Matrox acceleration"
1216 depends on FB && PCI
1217 select FB_CFB_FILLRECT
1218 select FB_CFB_COPYAREA
1219 select FB_CFB_IMAGEBLIT
1220 select FB_TILEBLITTING
1221 select FB_MACMODES if PPC_PMAC
1223 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1224 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1225 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1226 Matrox G400, G450 or G550 card in your box.
1228 To compile this driver as a module, choose M here: the
1229 module will be called matroxfb.
1231 You can pass several parameters to the driver at boot time or at
1232 module load time. The parameters look like "video=matroxfb:XXX", and
1233 are described in <file:Documentation/fb/matroxfb.txt>.
1235 config FB_MATROX_MILLENIUM
1236 bool "Millennium I/II support"
1237 depends on FB_MATROX
1239 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1240 video card. If you select "Advanced lowlevel driver options" below,
1241 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1242 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1243 also use font widths different from 8.
1245 config FB_MATROX_MYSTIQUE
1246 bool "Mystique support"
1247 depends on FB_MATROX
1249 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1250 video card. If you select "Advanced lowlevel driver options" below,
1251 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1252 packed pixel and 32 bpp packed pixel. You can also use font widths
1256 bool "G100/G200/G400/G450/G550 support"
1257 depends on FB_MATROX
1259 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1260 video card. If you select "Advanced lowlevel driver options", you
1261 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1262 pixel and 32 bpp packed pixel. You can also use font widths
1265 If you need support for G400 secondary head, you must say Y to
1266 "Matrox I2C support" and "G400 second head support" right below.
1267 G450/G550 secondary head and digital output are supported without
1270 The driver starts in monitor mode. You must use the matroxset tool
1271 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1272 swap primary and secondary head outputs, or to change output mode.
1273 Secondary head driver always start in 640x480 resolution and you
1274 must use fbset to change it.
1276 Do not forget that second head supports only 16 and 32 bpp
1277 packed pixels, so it is a good idea to compile them into the kernel
1278 too. You can use only some font widths, as the driver uses generic
1279 painting procedures (the secondary head does not use acceleration
1282 G450/G550 hardware can display TV picture only from secondary CRTC,
1283 and it performs no scaling, so picture must have 525 or 625 lines.
1285 config FB_MATROX_I2C
1286 tristate "Matrox I2C support"
1287 depends on FB_MATROX
1290 This drivers creates I2C buses which are needed for accessing the
1291 DDC (I2C) bus present on all Matroxes, an I2C bus which
1292 interconnects Matrox optional devices, like MGA-TVO on G200 and
1293 G400, and the secondary head DDC bus, present on G400 only.
1295 You can say Y or M here if you want to experiment with monitor
1296 detection code. You must say Y or M here if you want to use either
1297 second head of G400 or MGA-TVO on G200 or G400.
1299 If you compile it as module, it will create a module named
1302 config FB_MATROX_MAVEN
1303 tristate "G400 second head support"
1304 depends on FB_MATROX_G && FB_MATROX_I2C
1306 WARNING !!! This support does not work with G450 !!!
1308 Say Y or M here if you want to use a secondary head (meaning two
1309 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1310 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1311 secondary head output is blanked while you are in X. With XFree
1312 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1313 the fbdev driver on first head and the fbdev driver on second head.
1315 If you compile it as module, two modules are created,
1316 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1317 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1318 also load i2c-matroxfb to get it to run.
1320 The driver starts in monitor mode and you must use the matroxset
1322 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1323 PAL or NTSC or to swap primary and secondary head outputs.
1324 Secondary head driver also always start in 640x480 resolution, you
1325 must use fbset to change it.
1327 Also do not forget that second head supports only 16 and 32 bpp
1328 packed pixels, so it is a good idea to compile them into the kernel
1329 too. You can use only some font widths, as the driver uses generic
1330 painting procedures (the secondary head does not use acceleration
1334 tristate "ATI Radeon display support"
1335 depends on FB && PCI
1336 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1337 select FB_MODE_HELPERS
1338 select FB_CFB_FILLRECT
1339 select FB_CFB_COPYAREA
1340 select FB_CFB_IMAGEBLIT
1341 select FB_MACMODES if PPC
1343 Choose this option if you want to use an ATI Radeon graphics card as
1344 a framebuffer device. There are both PCI and AGP versions. You
1345 don't need to choose this to run the Radeon in plain VGA mode.
1347 There is a product page at
1348 http://products.amd.com/en-us/GraphicCardResult.aspx
1350 config FB_RADEON_I2C
1351 bool "DDC/I2C for ATI Radeon support"
1352 depends on FB_RADEON
1356 Say Y here if you want DDC/I2C support for your Radeon board.
1358 config FB_RADEON_BACKLIGHT
1359 bool "Support for backlight control"
1360 depends on FB_RADEON
1363 Say Y here if you want to control the backlight of your display.
1365 config FB_RADEON_DEBUG
1366 bool "Lots of debug output from Radeon driver"
1367 depends on FB_RADEON
1370 Say Y here if you want the Radeon driver to output all sorts
1371 of debugging information to provide to the maintainer when
1372 something goes wrong.
1375 tristate "ATI Rage128 display support"
1376 depends on FB && PCI
1377 select FB_CFB_FILLRECT
1378 select FB_CFB_COPYAREA
1379 select FB_CFB_IMAGEBLIT
1380 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1381 select FB_MACMODES if PPC_PMAC
1383 This driver supports graphics boards with the ATI Rage128 chips.
1384 Say Y if you have such a graphics board and read
1385 <file:Documentation/fb/aty128fb.txt>.
1387 To compile this driver as a module, choose M here: the
1388 module will be called aty128fb.
1390 config FB_ATY128_BACKLIGHT
1391 bool "Support for backlight control"
1392 depends on FB_ATY128
1395 Say Y here if you want to control the backlight of your display.
1398 tristate "ATI Mach64 display support" if PCI || ATARI
1399 depends on FB && !SPARC32
1400 select FB_CFB_FILLRECT
1401 select FB_CFB_COPYAREA
1402 select FB_CFB_IMAGEBLIT
1403 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1404 select FB_MACMODES if PPC
1406 This driver supports graphics boards with the ATI Mach64 chips.
1407 Say Y if you have such a graphics board.
1409 To compile this driver as a module, choose M here: the
1410 module will be called atyfb.
1413 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1414 depends on PCI && FB_ATY
1415 default y if SPARC64 && PCI
1417 Say Y here to support use of ATI's 64-bit Rage boards (or other
1418 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1419 framebuffer device. The ATI product support page for these boards
1420 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1422 config FB_ATY_GENERIC_LCD
1423 bool "Mach64 generic LCD support"
1424 depends on FB_ATY_CT
1426 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1427 Rage XC, or Rage XL chipset.
1430 bool "Mach64 GX support" if PCI
1434 Say Y here to support use of the ATI Mach64 Graphics Expression
1435 board (or other boards based on the Mach64 GX chipset) as a
1436 framebuffer device. The ATI product support page for these boards
1438 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1440 config FB_ATY_BACKLIGHT
1441 bool "Support for backlight control"
1445 Say Y here if you want to control the backlight of your display.
1448 tristate "S3 Trio/Virge support"
1449 depends on FB && PCI
1450 select FB_CFB_FILLRECT
1451 select FB_CFB_COPYAREA
1452 select FB_CFB_IMAGEBLIT
1453 select FB_TILEBLITTING
1456 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1458 Driver for graphics boards with S3 Trio / S3 Virge chip.
1461 bool "DDC for S3 support"
1466 Say Y here if you want DDC support for your S3 graphics card.
1469 tristate "S3 Savage support"
1470 depends on FB && PCI
1471 select FB_MODE_HELPERS
1472 select FB_CFB_FILLRECT
1473 select FB_CFB_COPYAREA
1474 select FB_CFB_IMAGEBLIT
1477 This driver supports notebooks and computers with S3 Savage PCI/AGP
1480 Say Y if you have such a graphics card.
1482 To compile this driver as a module, choose M here; the module
1483 will be called savagefb.
1485 config FB_SAVAGE_I2C
1486 bool "Enable DDC2 Support"
1487 depends on FB_SAVAGE
1490 This enables I2C support for S3 Savage Chipsets. This is used
1491 only for getting EDID information from the attached display
1492 allowing for robust video mode handling and switching.
1494 Because fbdev-2.6 requires that drivers must be able to
1495 independently validate video mode parameters, you should say Y
1498 config FB_SAVAGE_ACCEL
1499 bool "Enable Console Acceleration"
1500 depends on FB_SAVAGE
1503 This option will compile in console acceleration support. If
1504 the resulting framebuffer console has bothersome glitches, then
1508 tristate "SiS/XGI display support"
1509 depends on FB && PCI
1510 select FB_CFB_FILLRECT
1511 select FB_CFB_COPYAREA
1512 select FB_CFB_IMAGEBLIT
1513 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1514 select FB_SIS_300 if !FB_SIS_315
1516 This is the frame buffer device driver for the SiS 300, 315, 330
1517 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1518 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1520 To compile this driver as a module, choose M here; the module
1521 will be called sisfb.
1524 bool "SiS 300 series support"
1527 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1530 bool "SiS 315/330/340 series and XGI support"
1533 Say Y here to support use of the SiS 315, 330 and 340 series
1534 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1535 as XGI V3XT, V5, V8 and Z7.
1538 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1539 depends on FB && PCI && X86 && GPIOLIB && I2C
1540 select FB_CFB_FILLRECT
1541 select FB_CFB_COPYAREA
1542 select FB_CFB_IMAGEBLIT
1545 This is the frame buffer device driver for Graphics chips of VIA
1546 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1547 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1549 Say Y if you have a VIA UniChrome graphics board.
1551 To compile this driver as a module, choose M here: the
1552 module will be called viafb.
1556 config FB_VIA_DIRECT_PROCFS
1557 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1561 Allow direct hardware access to some output registers via procfs.
1562 This is dangerous but may provide the only chance to get the
1563 correct output device configuration.
1564 Its use is strongly discouraged.
1566 config FB_VIA_X_COMPATIBILITY
1567 bool "X server compatibility"
1571 This option reduces the functionality (power saving, ...) of the
1572 framebuffer to avoid negative impact on the OpenChrome X server.
1573 If you use any X server other than fbdev you should enable this
1574 otherwise it should be safe to disable it and allow using all
1580 tristate "NeoMagic display support"
1581 depends on FB && PCI
1582 select FB_MODE_HELPERS
1583 select FB_CFB_FILLRECT
1584 select FB_CFB_COPYAREA
1585 select FB_CFB_IMAGEBLIT
1588 This driver supports notebooks with NeoMagic PCI chips.
1589 Say Y if you have such a graphics card.
1591 To compile this driver as a module, choose M here: the
1592 module will be called neofb.
1595 tristate "IMG Kyro support"
1596 depends on FB && PCI
1597 select FB_CFB_FILLRECT
1598 select FB_CFB_COPYAREA
1599 select FB_CFB_IMAGEBLIT
1601 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1604 To compile this driver as a module, choose M here: the
1605 module will be called kyrofb.
1608 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1609 depends on FB && PCI
1610 select FB_CFB_IMAGEBLIT
1611 select FB_CFB_FILLRECT
1612 select FB_CFB_COPYAREA
1613 select FB_MODE_HELPERS
1615 This driver supports graphics boards with the 3Dfx Banshee,
1616 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1617 such a graphics board.
1619 To compile this driver as a module, choose M here: the
1620 module will be called tdfxfb.
1622 config FB_3DFX_ACCEL
1623 bool "3Dfx Acceleration functions"
1626 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1627 device driver with acceleration functions.
1630 bool "Enable DDC/I2C support"
1635 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1638 tristate "3Dfx Voodoo Graphics (sst1) support"
1639 depends on FB && PCI
1640 select FB_CFB_FILLRECT
1641 select FB_CFB_COPYAREA
1642 select FB_CFB_IMAGEBLIT
1644 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1645 Voodoo2 (cvg) based graphics card.
1647 To compile this driver as a module, choose M here: the
1648 module will be called sstfb.
1650 WARNING: Do not use any application that uses the 3D engine
1651 (namely glide) while using this driver.
1652 Please read the <file:Documentation/fb/sstfb.txt> for supported
1653 options and other important info support.
1656 tristate "VIA VT8623 support"
1657 depends on FB && PCI
1658 select FB_CFB_FILLRECT
1659 select FB_CFB_COPYAREA
1660 select FB_CFB_IMAGEBLIT
1661 select FB_TILEBLITTING
1664 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1666 Driver for CastleRock integrated graphics core in the
1667 VIA VT8623 [Apollo CLE266] chipset.
1670 tristate "Trident/CyberXXX/CyberBlade support"
1671 depends on FB && PCI
1672 select FB_CFB_FILLRECT
1673 select FB_CFB_COPYAREA
1674 select FB_CFB_IMAGEBLIT
1676 select FB_MODE_HELPERS
1678 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1679 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1681 There are also integrated versions of these chips called CyberXXXX,
1682 CyberImage or CyberBlade. These chips are mostly found in laptops
1683 but also on some motherboards including early VIA EPIA motherboards.
1684 For more information, read <file:Documentation/fb/tridentfb.txt>
1686 Say Y if you have such a graphics board.
1688 To compile this driver as a module, choose M here: the
1689 module will be called tridentfb.
1692 tristate "ARK 2000PV support"
1693 depends on FB && PCI
1694 select FB_CFB_FILLRECT
1695 select FB_CFB_COPYAREA
1696 select FB_CFB_IMAGEBLIT
1697 select FB_TILEBLITTING
1700 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1702 Driver for PCI graphics boards with ARK 2000PV chip
1703 and ICS 5342 RAMDAC.
1706 tristate "Permedia3 support"
1707 depends on FB && PCI
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 This is the frame buffer device driver for the 3DLabs Permedia3
1713 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1714 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1715 and maybe other boards.
1718 tristate "Fujitsu carmine frame buffer support"
1719 depends on FB && PCI
1720 select FB_CFB_FILLRECT
1721 select FB_CFB_COPYAREA
1722 select FB_CFB_IMAGEBLIT
1724 This is the frame buffer device driver for the Fujitsu Carmine chip.
1725 The driver provides two independent frame buffer devices.
1728 depends on FB_CARMINE
1729 prompt "DRAM timing"
1730 default FB_CARMINE_DRAM_EVAL
1732 config FB_CARMINE_DRAM_EVAL
1733 bool "Eval board timings"
1735 Use timings which work on the eval card.
1737 config CARMINE_DRAM_CUSTOM
1738 bool "Custom board timings"
1740 Use custom board timings.
1744 bool "Au1100 LCD Driver"
1745 depends on (FB = y) && MIPS_ALCHEMY
1746 select FB_CFB_FILLRECT
1747 select FB_CFB_COPYAREA
1748 select FB_CFB_IMAGEBLIT
1750 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1751 various panels and CRTs by passing in kernel cmd line option
1752 au1100fb:panel=<name>.
1755 bool "Au1200/Au1300 LCD Driver"
1756 depends on (FB = y) && MIPS_ALCHEMY
1757 select FB_SYS_FILLRECT
1758 select FB_SYS_COPYAREA
1759 select FB_SYS_IMAGEBLIT
1762 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1763 It can drive various panels and CRTs by passing in kernel cmd line
1764 option au1200fb:panel=<name>.
1767 bool "VIA VT8500 framebuffer support"
1768 depends on (FB = y) && ARM && ARCH_VT8500
1769 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1770 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1771 select FB_SYS_IMAGEBLIT
1772 select FB_MODE_HELPERS
1773 select VIDEOMODE_HELPERS
1775 This is the framebuffer driver for VIA VT8500 integrated LCD
1779 bool "Wondermedia WM8xxx-series frame buffer support"
1780 depends on (FB = y) && ARM && ARCH_VT8500
1781 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1782 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1783 select FB_SYS_IMAGEBLIT
1784 select FB_MODE_HELPERS
1785 select VIDEOMODE_HELPERS
1787 This is the framebuffer driver for WonderMedia WM8xxx-series
1788 integrated LCD controller. This driver covers the WM8505, WM8650
1791 config FB_WMT_GE_ROPS
1792 bool "VT8500/WM8xxx accelerated raster ops support"
1793 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1796 This adds support for accelerated raster operations on the
1797 VIA VT8500 and Wondermedia 85xx series SoCs.
1799 source "drivers/video/fbdev/geode/Kconfig"
1802 tristate "HD64461 Frame Buffer support"
1803 depends on FB && HD64461
1804 select FB_CFB_FILLRECT
1805 select FB_CFB_COPYAREA
1806 select FB_CFB_IMAGEBLIT
1808 This is the frame buffer device driver for the Hitachi HD64461 LCD
1812 tristate "PMAG-AA TURBOchannel framebuffer support"
1814 select FB_CFB_FILLRECT
1815 select FB_CFB_COPYAREA
1816 select FB_CFB_IMAGEBLIT
1818 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1819 used mainly in the MIPS-based DECstation series.
1822 tristate "PMAG-BA TURBOchannel framebuffer support"
1824 select FB_CFB_FILLRECT
1825 select FB_CFB_COPYAREA
1826 select FB_CFB_IMAGEBLIT
1828 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1829 used mainly in the MIPS-based DECstation series.
1832 tristate "PMAGB-B TURBOchannel framebuffer support"
1834 select FB_CFB_FILLRECT
1835 select FB_CFB_COPYAREA
1836 select FB_CFB_IMAGEBLIT
1838 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1839 in the MIPS-based DECstation series. The card is currently only
1840 supported in 1280x1024x8 mode.
1843 bool "Maxine (Personal DECstation) onboard framebuffer support"
1844 depends on (FB = y) && MACH_DECSTATION
1845 select FB_CFB_FILLRECT
1846 select FB_CFB_COPYAREA
1847 select FB_CFB_IMAGEBLIT
1849 Support for the onboard framebuffer (1024x768x8) in the Personal
1850 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1854 bool "G364 frame buffer support"
1855 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1856 select FB_CFB_FILLRECT
1857 select FB_CFB_COPYAREA
1858 select FB_CFB_IMAGEBLIT
1860 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1861 Olivetti M700-10 systems.
1864 bool "Motorola 68328 native frame buffer support"
1865 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1866 select FB_CFB_FILLRECT
1867 select FB_CFB_COPYAREA
1868 select FB_CFB_IMAGEBLIT
1870 Say Y here if you want to support the built-in frame buffer of
1871 the Motorola 68328 CPU family.
1874 tristate "PXA168/910 LCD framebuffer support"
1875 depends on FB && (CPU_PXA168 || CPU_PXA910)
1876 select FB_CFB_FILLRECT
1877 select FB_CFB_COPYAREA
1878 select FB_CFB_IMAGEBLIT
1880 Frame buffer driver for the built-in LCD controller in the Marvell
1884 tristate "PXA LCD framebuffer support"
1885 depends on FB && ARCH_PXA
1886 select FB_CFB_FILLRECT
1887 select FB_CFB_COPYAREA
1888 select FB_CFB_IMAGEBLIT
1889 select VIDEOMODE_HELPERS if OF
1890 select FB_MODE_HELPERS if OF
1892 Frame buffer driver for the built-in LCD controller in the Intel
1895 This driver is also available as a module ( = code which can be
1896 inserted and removed from the running kernel whenever you want). The
1897 module will be called pxafb. If you want to compile it as a module,
1898 say M here and read <file:Documentation/kbuild/modules.txt>.
1902 config FB_PXA_OVERLAY
1903 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1905 depends on FB_PXA && (PXA27x || PXA3xx)
1907 config FB_PXA_SMARTPANEL
1908 bool "PXA Smartpanel LCD support"
1912 config FB_PXA_PARAMETERS
1913 bool "PXA LCD command line parameters"
1917 Enable the use of kernel command line or module parameters
1918 to configure the physical properties of the LCD panel when
1919 using the PXA LCD driver.
1921 This option allows you to override the panel parameters
1922 supplied by the platform in order to support multiple
1923 different models of flatpanel. If you will only be using a
1924 single model of flatpanel then you can safely leave this
1927 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1930 tristate "PXA3xx 2D graphics accelerator driver"
1933 Kernelspace driver for the 2D graphics controller unit (GCU)
1934 found on PXA3xx processors. There is a counterpart driver in the
1935 DirectFB suite, see http://www.directfb.org/
1937 If you compile this as a module, it will be called pxa3xx_gcu.
1940 tristate "2700G LCD framebuffer support"
1941 depends on FB && ARCH_PXA
1942 select FB_CFB_FILLRECT
1943 select FB_CFB_COPYAREA
1944 select FB_CFB_IMAGEBLIT
1946 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1950 bool "Enable debugging info via debugfs"
1951 depends on FB_MBX && DEBUG_FS
1954 Enable this if you want debugging information using the debug
1955 filesystem (debugfs)
1960 tristate "Freescale DIU framebuffer support"
1961 depends on FB && FSL_SOC
1962 select FB_MODE_HELPERS
1963 select FB_CFB_FILLRECT
1964 select FB_CFB_COPYAREA
1965 select FB_CFB_IMAGEBLIT
1966 select PPC_LIB_RHEAP
1968 Framebuffer driver for the Freescale SoC DIU
1971 tristate "W100 frame buffer support"
1972 depends on FB && ARCH_PXA
1973 select FB_CFB_FILLRECT
1974 select FB_CFB_COPYAREA
1975 select FB_CFB_IMAGEBLIT
1977 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1978 It can also drive the w3220 chip found on iPAQ hx4700.
1980 This driver is also available as a module ( = code which can be
1981 inserted and removed from the running kernel whenever you want). The
1982 module will be called w100fb. If you want to compile it as a module,
1983 say M here and read <file:Documentation/kbuild/modules.txt>.
1987 config FB_SH_MOBILE_LCDC
1988 tristate "SuperH Mobile LCDC framebuffer support"
1989 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1990 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1991 select FB_SYS_FILLRECT
1992 select FB_SYS_COPYAREA
1993 select FB_SYS_IMAGEBLIT
1995 select FB_DEFERRED_IO
1998 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2001 tristate "Toshiba Mobile IO FrameBuffer support"
2002 depends on FB && (MFD_TMIO || COMPILE_TEST)
2003 select FB_CFB_FILLRECT
2004 select FB_CFB_COPYAREA
2005 select FB_CFB_IMAGEBLIT
2007 Frame buffer driver for the Toshiba Mobile IO integrated as found
2008 on the Sharp SL-6000 series
2010 This driver is also available as a module ( = code which can be
2011 inserted and removed from the running kernel whenever you want). The
2012 module will be called tmiofb. If you want to compile it as a module,
2013 say M here and read <file:Documentation/kbuild/modules.txt>.
2017 config FB_TMIO_ACCELL
2018 bool "tmiofb acceleration"
2023 tristate "Samsung S3C framebuffer support"
2024 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2025 ARCH_S5PV210 || ARCH_EXYNOS)
2026 select FB_CFB_FILLRECT
2027 select FB_CFB_COPYAREA
2028 select FB_CFB_IMAGEBLIT
2030 Frame buffer driver for the built-in FB controller in the Samsung
2031 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2032 and the S3C64XX series such as the S3C6400 and S3C6410.
2034 These chips all have the same basic framebuffer design with the
2035 actual capabilities depending on the chip. For instance the S3C6400
2036 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2037 currently only have two.
2039 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2041 config FB_S3C_DEBUG_REGWRITE
2042 bool "Debug register writes"
2045 Show all register writes via pr_debug()
2048 tristate "S3C2410 LCD framebuffer support"
2049 depends on FB && ARCH_S3C24XX
2050 select FB_CFB_FILLRECT
2051 select FB_CFB_COPYAREA
2052 select FB_CFB_IMAGEBLIT
2054 Frame buffer driver for the built-in LCD controller in the Samsung
2057 This driver is also available as a module ( = code which can be
2058 inserted and removed from the running kernel whenever you want). The
2059 module will be called s3c2410fb. If you want to compile it as a module,
2060 say M here and read <file:Documentation/kbuild/modules.txt>.
2063 config FB_S3C2410_DEBUG
2064 bool "S3C2410 lcd debug messages"
2065 depends on FB_S3C2410
2067 Turn on debugging messages. Note that you can set/unset at run time
2071 tristate "NUC900 LCD framebuffer support"
2072 depends on FB && ARCH_W90X900
2073 select FB_CFB_FILLRECT
2074 select FB_CFB_COPYAREA
2075 select FB_CFB_IMAGEBLIT
2077 Frame buffer driver for the built-in LCD controller in the Nuvoton
2080 config GPM1040A0_320X240
2081 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2082 depends on FB_NUC900
2085 tristate "Silicon Motion SM501 framebuffer support"
2086 depends on FB && MFD_SM501
2087 select FB_CFB_FILLRECT
2088 select FB_CFB_COPYAREA
2089 select FB_CFB_IMAGEBLIT
2091 Frame buffer driver for the CRT and LCD controllers in the Silicon
2094 This driver is also available as a module ( = code which can be
2095 inserted and removed from the running kernel whenever you want). The
2096 module will be called sm501fb. If you want to compile it as a module,
2097 say M here and read <file:Documentation/kbuild/modules.txt>.
2102 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2103 depends on FB && USB
2104 select FB_MODE_HELPERS
2105 select FB_SYS_FILLRECT
2106 select FB_SYS_COPYAREA
2107 select FB_SYS_IMAGEBLIT
2109 select FB_DEFERRED_IO
2111 This is a kernel framebuffer driver for SMSC UFX USB devices.
2112 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2113 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2115 To compile as a module, choose M here: the module name is smscufx.
2118 tristate "Displaylink USB Framebuffer support"
2119 depends on FB && USB
2120 select FB_MODE_HELPERS
2121 select FB_SYS_FILLRECT
2122 select FB_SYS_COPYAREA
2123 select FB_SYS_IMAGEBLIT
2125 select FB_DEFERRED_IO
2127 This is a kernel framebuffer driver for DisplayLink USB devices.
2128 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2129 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2130 To compile as a module, choose M here: the module name is udlfb.
2132 config FB_IBM_GXT4500
2133 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2135 select FB_CFB_FILLRECT
2136 select FB_CFB_COPYAREA
2137 select FB_CFB_IMAGEBLIT
2139 Say Y here to enable support for the IBM GXT4000P/6000P and
2140 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2141 found on some IBM System P (pSeries) machines. This driver
2142 doesn't use Geometry Engine GT1000. This driver also supports
2143 AGP Fire GL2/3/4 cards on x86.
2146 tristate "PS3 GPU framebuffer driver"
2147 depends on FB && PS3_PS3AV
2148 select FB_SYS_FILLRECT
2149 select FB_SYS_COPYAREA
2150 select FB_SYS_IMAGEBLIT
2153 Include support for the virtual frame buffer in the PS3 platform.
2155 config FB_PS3_DEFAULT_SIZE_M
2156 int "PS3 default frame buffer size (in MiB)"
2160 This is the default size (in MiB) of the virtual frame buffer in
2162 The default value can be overridden on the kernel command line
2163 using the "ps3fb" option (e.g. "ps3fb=9M");
2166 tristate "Xilinx frame buffer support"
2167 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
2168 select FB_CFB_FILLRECT
2169 select FB_CFB_COPYAREA
2170 select FB_CFB_IMAGEBLIT
2172 Include support for the Xilinx ML300/ML403 reference design
2173 framebuffer. ML300 carries a 640*480 LCD display on the board,
2174 ML403 uses a standard DB15 VGA connector.
2177 tristate "Goldfish Framebuffer"
2178 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2179 select FB_CFB_FILLRECT
2180 select FB_CFB_COPYAREA
2181 select FB_CFB_IMAGEBLIT
2183 Framebuffer driver for Goldfish Virtual Platform
2186 tristate "Cobalt server LCD frame buffer support"
2187 depends on FB && MIPS_COBALT
2190 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2191 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2192 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2193 select FB_CFB_FILLRECT
2194 select FB_CFB_COPYAREA
2195 select FB_CFB_IMAGEBLIT
2197 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2198 (D)STN/TFT LCD Controller.
2199 Supports display resolutions up to 1024x1024 pixel, grayscale and
2200 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2201 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2202 panels <= 320 pixel horizontal resolution.
2205 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2206 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2207 select FB_CFB_FILLRECT
2208 select FB_CFB_COPYAREA
2209 select FB_CFB_IMAGEBLIT
2210 select FB_CFB_REV_PIXELS_IN_BYTE
2211 select FB_MODE_HELPERS
2212 select VIDEOMODE_HELPERS
2214 This is the frame buffer device driver for the TI LCD controller
2215 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2219 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2221 select FB_SYS_FILLRECT
2222 select FB_SYS_COPYAREA
2223 select FB_SYS_IMAGEBLIT
2226 This is a `virtual' frame buffer device. It operates on a chunk of
2227 unswappable kernel memory instead of on the memory of a graphics
2228 board. This means you cannot see any output sent to this frame
2229 buffer device, while it does consume precious memory. The main use
2230 of this frame buffer device is testing and debugging the frame
2231 buffer subsystem. Do NOT enable it for normal systems! To protect
2232 the innocent, it has to be enabled explicitly at boot time using the
2233 kernel option `video=vfb:'.
2235 To compile this driver as a module, choose M here: the
2236 module will be called vfb. In order to load it, you must use
2237 the vfb_enable=1 option.
2241 config XEN_FBDEV_FRONTEND
2242 tristate "Xen virtual frame buffer support"
2243 depends on FB && XEN
2244 select FB_SYS_FILLRECT
2245 select FB_SYS_COPYAREA
2246 select FB_SYS_IMAGEBLIT
2248 select FB_DEFERRED_IO
2249 select XEN_XENBUS_FRONTEND
2252 This driver implements the front-end of the Xen virtual
2253 frame buffer driver. It communicates with a back-end
2257 tristate "E-Ink Metronome/8track controller support"
2259 select FB_SYS_FILLRECT
2260 select FB_SYS_COPYAREA
2261 select FB_SYS_IMAGEBLIT
2263 select FB_DEFERRED_IO
2265 This driver implements support for the E-Ink Metronome
2266 controller. The pre-release name for this device was 8track
2267 and could also have been called by some vendors as PVI-nnnn.
2270 tristate "Fujitsu MB862xx GDC support"
2272 depends on PCI || (OF && PPC)
2273 select FB_CFB_FILLRECT
2274 select FB_CFB_COPYAREA
2275 select FB_CFB_IMAGEBLIT
2277 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2280 prompt "GDC variant"
2281 depends on FB_MB862XX
2283 config FB_MB862XX_PCI_GDC
2284 bool "Carmine/Coral-P(A) GDC"
2287 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2288 PCI graphics controller devices.
2290 config FB_MB862XX_LIME
2292 depends on OF && PPC
2293 select FB_FOREIGN_ENDIAN
2294 select FB_LITTLE_ENDIAN
2296 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2300 config FB_MB862XX_I2C
2301 bool "Support I2C bus on MB862XX GDC"
2302 depends on FB_MB862XX && I2C
2303 depends on FB_MB862XX=m || I2C=y
2306 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2307 driver to support accessing I2C devices on controller's I2C bus.
2308 These are usually some video decoder chips.
2311 tristate "EP93XX frame buffer support"
2312 depends on FB && ARCH_EP93XX
2313 select FB_CFB_FILLRECT
2314 select FB_CFB_COPYAREA
2315 select FB_CFB_IMAGEBLIT
2317 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2318 This driver is also available as a module. The module will be called
2321 config FB_PRE_INIT_FB
2322 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2323 depends on FB && FB_MB862XX_LIME
2325 Select this option if display contents should be inherited as set by
2329 tristate "MX3 Framebuffer support"
2330 depends on FB && MX3_IPU
2331 select BACKLIGHT_CLASS_DEVICE
2332 select BACKLIGHT_LCD_SUPPORT
2333 select FB_CFB_FILLRECT
2334 select FB_CFB_COPYAREA
2335 select FB_CFB_IMAGEBLIT
2338 This is a framebuffer device for the i.MX31 LCD Controller. So
2339 far only synchronous displays are supported. If you plan to use
2340 an LCD display with your i.MX31 system, say Y here.
2342 config FB_BROADSHEET
2343 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2345 select FB_SYS_FILLRECT
2346 select FB_SYS_COPYAREA
2347 select FB_SYS_IMAGEBLIT
2349 select FB_DEFERRED_IO
2351 This driver implements support for the E-Ink Broadsheet
2352 controller. The release name for this device was Epson S1D13521
2353 and could also have been called by other names when coupled with
2357 tristate "AUO-K190X EPD controller support"
2359 select FB_SYS_FILLRECT
2360 select FB_SYS_COPYAREA
2361 select FB_SYS_IMAGEBLIT
2363 select FB_DEFERRED_IO
2365 Provides support for epaper controllers from the K190X series
2366 of AUO. These controllers can be used to drive epaper displays
2369 This option enables the common support, shared by the individual
2370 controller drivers. You will also have to enable the driver
2371 for the controller type used in your device.
2374 tristate "AUO-K1900 EPD controller support"
2375 depends on FB && FB_AUO_K190X
2377 This driver implements support for the AUO K1900 epd-controller.
2378 This controller can drive Sipix epaper displays but can only do
2379 serial updates, reducing the number of possible frames per second.
2382 tristate "AUO-K1901 EPD controller support"
2383 depends on FB && FB_AUO_K190X
2385 This driver implements support for the AUO K1901 epd-controller.
2386 This controller can drive Sipix epaper displays and supports
2387 concurrent updates, making higher frames per second possible.
2390 tristate "JZ4740 LCD framebuffer support"
2391 depends on FB && MACH_JZ4740
2392 select FB_SYS_FILLRECT
2393 select FB_SYS_COPYAREA
2394 select FB_SYS_IMAGEBLIT
2396 Framebuffer support for the JZ4740 SoC.
2399 tristate "MXS LCD framebuffer support"
2400 depends on FB && (ARCH_MXS || ARCH_MXC)
2401 select FB_CFB_FILLRECT
2402 select FB_CFB_COPYAREA
2403 select FB_CFB_IMAGEBLIT
2404 select FB_MODE_HELPERS
2405 select VIDEOMODE_HELPERS
2407 Framebuffer support for the MXS SoC.
2409 config FB_PUV3_UNIGFX
2410 tristate "PKUnity v3 Unigfx framebuffer support"
2411 depends on FB && UNICORE32 && ARCH_PUV3
2412 select FB_SYS_FILLRECT
2413 select FB_SYS_COPYAREA
2414 select FB_SYS_IMAGEBLIT
2417 Choose this option if you want to use the Unigfx device as a
2418 framebuffer device. Without the support of PCI & AGP.
2421 tristate "Microsoft Hyper-V Synthetic Video support"
2422 depends on FB && HYPERV
2423 select FB_CFB_FILLRECT
2424 select FB_CFB_COPYAREA
2425 select FB_CFB_IMAGEBLIT
2427 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2430 bool "Simple framebuffer support"
2432 select FB_CFB_FILLRECT
2433 select FB_CFB_COPYAREA
2434 select FB_CFB_IMAGEBLIT
2436 Say Y if you want support for a simple frame-buffer.
2438 This driver assumes that the display hardware has been initialized
2439 before the kernel boots, and the kernel will simply render to the
2440 pre-allocated frame buffer surface.
2442 Configuration re: surface address, size, and format must be provided
2443 through device tree, or plain old platform data.
2445 source "drivers/video/fbdev/omap/Kconfig"
2446 source "drivers/video/fbdev/omap2/Kconfig"
2447 source "drivers/video/fbdev/mmp/Kconfig"
2449 config FB_SH_MOBILE_MERAM
2450 tristate "SuperH Mobile MERAM read ahead support"
2451 depends on (SUPERH || ARCH_SHMOBILE)
2452 select GENERIC_ALLOCATOR
2454 Enable MERAM support for the SuperH controller.
2456 This will allow for caching of the framebuffer to provide more
2457 reliable access under heavy main memory bus traffic situations.
2458 Up to 4 memory channels can be configured, allowing 4 RGB or
2459 2 YCbCr framebuffers to be configured.
2462 tristate "Solomon SSD1307 framebuffer support"
2463 depends on FB && I2C
2465 depends on GPIOLIB || COMPILE_TEST
2467 select FB_SYS_FILLRECT
2468 select FB_SYS_COPYAREA
2469 select FB_SYS_IMAGEBLIT
2470 select FB_DEFERRED_IO
2474 This driver implements support for the Solomon SSD1307
2475 OLED controller over I2C.
2478 tristate "Silicon Motion SM712 framebuffer support"
2479 depends on FB && PCI
2480 select FB_CFB_FILLRECT
2481 select FB_CFB_COPYAREA
2482 select FB_CFB_IMAGEBLIT
2484 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2487 This driver is also available as a module. The module will be
2488 called sm712fb. If you want to compile it as a module, say M
2489 here and read <file:Documentation/kbuild/modules.txt>.