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 menuconfig FB_FOREIGN_ENDIAN
142 bool "Framebuffer foreign endianness support"
145 This menu will let you enable support for the framebuffers with
146 non-native endianness (e.g. Little-Endian framebuffer on a
147 Big-Endian machine). Most probably you don't have such hardware,
148 so it's safe to say "n" here.
151 prompt "Choice endianness support"
152 depends on FB_FOREIGN_ENDIAN
154 config FB_BOTH_ENDIAN
155 bool "Support for Big- and Little-Endian framebuffers"
158 bool "Support for Big-Endian framebuffers only"
160 config FB_LITTLE_ENDIAN
161 bool "Support for Little-Endian framebuffers only"
170 config FB_DEFERRED_IO
177 depends on FB_DEFERRED_IO
184 Common utility functions useful to fbdev drivers of VGA-based
195 select BACKLIGHT_LCD_SUPPORT
196 select BACKLIGHT_CLASS_DEVICE
199 config FB_MODE_HELPERS
200 bool "Enable Video Mode Handling Helpers"
204 This enables functions for handling video modes using the
205 Generalized Timing Formula and the EDID parser. A few drivers rely
206 on this feature such as the radeonfb, rivafb, and the i810fb. If
207 your driver does not take advantage of this feature, choosing Y will
208 just increase the kernel size by about 5K.
210 config FB_TILEBLITTING
211 bool "Enable Tile Blitting Support"
215 This enables tile blitting. Tile blitting is a drawing technique
216 where the screen is divided into rectangular sections (tiles), whereas
217 the standard blitting divides the screen into pixels. Because the
218 default drawing element is a tile, drawing functions will be passed
219 parameters in terms of number of tiles instead of number of pixels.
220 For example, to draw a single character, instead of using bitmaps,
221 an index to an array of bitmaps will be used. To clear or move a
222 rectangular section of a screen, the rectangle will be described in
223 terms of number of tiles in the x- and y-axis.
225 This is particularly important to one driver, matroxfb. If
228 comment "Frame buffer hardware drivers"
232 tristate "Aeroflex Gaisler framebuffer support"
233 depends on FB && SPARC
234 select FB_CFB_FILLRECT
235 select FB_CFB_COPYAREA
236 select FB_CFB_IMAGEBLIT
238 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
241 tristate "Cirrus Logic support"
242 depends on FB && (ZORRO || PCI)
243 select FB_CFB_FILLRECT
244 select FB_CFB_COPYAREA
245 select FB_CFB_IMAGEBLIT
247 This enables support for Cirrus Logic GD542x/543x based boards on
248 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
250 If you have a PCI-based system, this enables support for these
251 chips: GD-543x, GD-544x, GD-5480.
253 Please read the file <file:Documentation/fb/cirrusfb.txt>.
255 Say N unless you have such a graphics board or plan to get one
256 before you next recompile the kernel.
259 tristate "Permedia2 support"
260 depends on FB && ((AMIGA && BROKEN) || PCI)
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This is the frame buffer device driver for cards based on
266 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
267 The driver was tested on the following cards:
268 Diamond FireGL 1000 PRO AGP
269 ELSA Gloria Synergy PCI
270 Appian Jeronimo PRO (both heads) PCI
271 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
272 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
273 ASK Graphic Blaster Exxtreme AGP
275 To compile this driver as a module, choose M here: the
276 module will be called pm2fb.
278 config FB_PM2_FIFO_DISCONNECT
279 bool "enable FIFO disconnect feature"
280 depends on FB_PM2 && PCI
282 Support the Permedia2 FIFO disconnect feature.
285 tristate "ARM PrimeCell PL110 support"
286 depends on ARM || ARM64 || COMPILE_TEST
287 depends on FB && ARM_AMBA && HAS_IOMEM
288 select FB_CFB_FILLRECT
289 select FB_CFB_COPYAREA
290 select FB_CFB_IMAGEBLIT
291 select FB_MODE_HELPERS if OF
292 select VIDEOMODE_HELPERS if OF
293 select BACKLIGHT_LCD_SUPPORT if OF
294 select BACKLIGHT_CLASS_DEVICE if OF
296 This framebuffer device driver is for the ARM PrimeCell PL110
297 Colour LCD controller. ARM PrimeCells provide the building
298 blocks for System on a Chip devices.
300 If you want to compile this as a module (=code which can be
301 inserted into and removed from the running kernel), say M
302 here and read <file:Documentation/kbuild/modules.txt>. The module
303 will be called amba-clcd.
305 # Helper logic selected only by the ARM Versatile platform family.
306 config PLAT_VERSATILE_CLCD
307 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
309 depends on FB_ARMCLCD && FB=y
314 bool "Acorn VIDC support"
315 depends on (FB = y) && ARM && ARCH_ACORN
316 select FB_CFB_FILLRECT
317 select FB_CFB_COPYAREA
318 select FB_CFB_IMAGEBLIT
320 This is the frame buffer device driver for the Acorn VIDC graphics
321 hardware found in Acorn RISC PCs and other ARM-based machines. If
324 config FB_CLPS711X_OLD
326 select FB_CFB_FILLRECT
327 select FB_CFB_COPYAREA
328 select FB_CFB_IMAGEBLIT
331 tristate "CLPS711X LCD support"
332 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
333 select FB_CLPS711X_OLD if ARCH_CLPS711X && !ARCH_MULTIPLATFORM
334 select BACKLIGHT_LCD_SUPPORT
335 select FB_MODE_HELPERS
336 select FB_SYS_FILLRECT
337 select FB_SYS_COPYAREA
338 select FB_SYS_IMAGEBLIT
339 select LCD_CLASS_DEVICE
340 select VIDEOMODE_HELPERS
342 Say Y to enable the Framebuffer driver for the Cirrus Logic
346 bool "SA-1100 LCD support"
347 depends on (FB = y) && ARM && ARCH_SA1100
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This is a framebuffer device for the SA-1100 LCD Controller.
353 See <http://www.linux-fbdev.org/> for information on framebuffer
356 If you plan to use the LCD display with your SA-1100 system, say
360 tristate "Freescale i.MX1/21/25/27 LCD support"
361 depends on FB && ARCH_MXC
362 select BACKLIGHT_LCD_SUPPORT
363 select LCD_CLASS_DEVICE
364 select FB_CFB_FILLRECT
365 select FB_CFB_COPYAREA
366 select FB_CFB_IMAGEBLIT
367 select FB_MODE_HELPERS
368 select VIDEOMODE_HELPERS
371 tristate "CyberPro 2000/2010/5000 support"
372 depends on FB && PCI && (BROKEN || !SPARC64)
373 select FB_CFB_FILLRECT
374 select FB_CFB_COPYAREA
375 select FB_CFB_IMAGEBLIT
377 This enables support for the Integraphics CyberPro 20x0 and 5000
378 VGA chips used in the Rebel.com Netwinder and other machines.
379 Say Y if you have a NetWinder or a graphics card containing this
380 device, otherwise say N.
382 config FB_CYBER2000_DDC
383 bool "DDC for CyberPro support"
384 depends on FB_CYBER2000
388 Say Y here if you want DDC support for your CyberPro graphics
389 card. This is only I2C bus support, driver does not use EDID.
391 config FB_CYBER2000_I2C
392 bool "CyberPro 2000/2010/5000 I2C support"
393 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
394 depends on I2C=y || FB_CYBER2000=m
397 Enable support for the I2C video decoder interface on the
398 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
399 on the Netwinder machines for the SAA7111 video capture.
403 depends on (FB = y) && APOLLO
405 select FB_CFB_FILLRECT
406 select FB_CFB_IMAGEBLIT
410 depends on (FB = y) && Q40
412 select FB_CFB_FILLRECT
413 select FB_CFB_COPYAREA
414 select FB_CFB_IMAGEBLIT
417 tristate "Amiga native chipset support"
418 depends on FB && AMIGA
420 This is the frame buffer device driver for the builtin graphics
421 chipset found in Amigas.
423 To compile this driver as a module, choose M here: the
424 module will be called amifb.
427 bool "Amiga OCS chipset support"
430 This enables support for the original Agnus and Denise video chips,
431 found in the Amiga 1000 and most A500's and A2000's. If you intend
432 to run Linux on any of these systems, say Y; otherwise say N.
435 bool "Amiga ECS chipset support"
438 This enables support for the Enhanced Chip Set, found in later
439 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
440 you intend to run Linux on any of these systems, say Y; otherwise
444 bool "Amiga AGA chipset support"
447 This enables support for the Advanced Graphics Architecture (also
448 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
449 and CD32. If you intend to run Linux on any of these systems, say Y;
453 bool "Amiga FrameMaster II/Rainbow II support"
454 depends on (FB = y) && ZORRO
455 select FB_CFB_FILLRECT
456 select FB_CFB_COPYAREA
457 select FB_CFB_IMAGEBLIT
459 This is the frame buffer device driver for the Amiga FrameMaster
460 card from BSC (exhibited 1992 but not shipped as a CBM product).
463 tristate "Arc Monochrome LCD board support"
465 select FB_SYS_FILLRECT
466 select FB_SYS_COPYAREA
467 select FB_SYS_IMAGEBLIT
470 This enables support for the Arc Monochrome LCD board. The board
471 is based on the KS-108 lcd controller and is typically a matrix
472 of 2*n chips. This driver was tested with a 128x64 panel. This
473 driver supports it for use with x86 SBCs through a 16 bit GPIO
474 interface (8 bit data, 8 bit control). If you anticipate using
475 this driver, say Y or M; otherwise say N. You must specify the
476 GPIO IO address to be used for setting control and data.
479 bool "Atari native chipset support"
480 depends on (FB = y) && ATARI
481 select FB_CFB_FILLRECT
482 select FB_CFB_COPYAREA
483 select FB_CFB_IMAGEBLIT
485 This is the frame buffer device driver for the builtin graphics
486 chipset found in Ataris.
489 bool "Open Firmware frame buffer device support"
490 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
491 select FB_CFB_FILLRECT
492 select FB_CFB_COPYAREA
493 select FB_CFB_IMAGEBLIT
496 Say Y if you want support with Open Firmware for your graphics
500 bool "Apple \"control\" display support"
501 depends on (FB = y) && PPC_PMAC && PPC32
502 select FB_CFB_FILLRECT
503 select FB_CFB_COPYAREA
504 select FB_CFB_IMAGEBLIT
507 This driver supports a frame buffer for the graphics adapter in the
508 Power Macintosh 7300 and others.
511 bool "Apple \"platinum\" display support"
512 depends on (FB = y) && PPC_PMAC && PPC32
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
518 This driver supports a frame buffer for the "platinum" graphics
519 adapter in some Power Macintoshes.
522 bool "Apple \"valkyrie\" display support"
523 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
524 select FB_CFB_FILLRECT
525 select FB_CFB_COPYAREA
526 select FB_CFB_IMAGEBLIT
529 This driver supports a frame buffer for the "valkyrie" graphics
530 adapter in some Power Macintoshes.
533 bool "Chips 65550 display support"
534 depends on (FB = y) && PPC32 && PCI
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
539 This is the frame buffer device driver for the Chips & Technologies
540 65550 graphics chip in PowerBooks.
543 bool "Asiliant (Chips) 69000 display support"
544 depends on (FB = y) && PCI
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
549 This is the frame buffer device driver for the Asiliant 69030 chipset
552 bool "IMS Twin Turbo display support"
553 depends on (FB = y) && PCI
554 select FB_CFB_IMAGEBLIT
555 select FB_MACMODES if PPC
557 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
558 many Macintosh and compatible computers.
561 tristate "VGA 16-color graphics support"
562 depends on FB && (X86 || PPC)
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
567 select FONT_8x16 if FRAMEBUFFER_CONSOLE
569 This is the frame buffer device driver for VGA 16 color graphic
570 cards. Say Y if you have such a card.
572 To compile this driver as a module, choose M here: the
573 module will be called vga16fb.
575 config FB_BF54X_LQ043
576 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
577 depends on FB && (BF54x) && !BF542
578 select FB_CFB_FILLRECT
579 select FB_CFB_COPYAREA
580 select FB_CFB_IMAGEBLIT
582 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
584 config FB_BFIN_T350MCQB
585 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
586 depends on FB && BLACKFIN
588 select FB_CFB_FILLRECT
589 select FB_CFB_COPYAREA
590 select FB_CFB_IMAGEBLIT
592 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
593 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
594 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
596 config FB_BFIN_LQ035Q1
597 tristate "SHARP LQ035Q1DH02 TFT LCD"
598 depends on FB && BLACKFIN && SPI
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
604 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
605 the Blackfin Landscape LCD EZ-Extender Card.
606 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
607 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
609 To compile this driver as a module, choose M here: the
610 module will be called bfin-lq035q1-fb.
612 config FB_BF537_LQ035
613 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
614 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
615 select FB_CFB_FILLRECT
616 select FB_CFB_COPYAREA
617 select FB_CFB_IMAGEBLIT
620 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
623 To compile this driver as a module, choose M here: the
624 module will be called bf537-lq035.
627 tristate "Blackfin ADV7393 Video encoder"
628 depends on FB && BLACKFIN
630 select FB_CFB_FILLRECT
631 select FB_CFB_COPYAREA
632 select FB_CFB_IMAGEBLIT
634 This is the framebuffer device for a ADV7393 video encoder
635 attached to a Blackfin on the PPI port.
636 If your Blackfin board has a ADV7393 select Y.
638 To compile this driver as a module, choose M here: the
639 module will be called bfin_adv7393fb.
642 prompt "Video mode support"
643 depends on FB_BFIN_7393
653 bool 'NTSC 640x480 (Experimental)'
656 bool 'PAL 640x480 (Experimental)'
659 bool 'NTSC 720x480 YCbCR input'
662 bool 'PAL 720x576 YCbCR input'
667 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
668 depends on (FB_BFIN_7393)
669 default ADV7393_1XMEM
679 tristate "HP STI frame buffer device support"
680 depends on FB && PARISC
681 select FB_CFB_FILLRECT
682 select FB_CFB_COPYAREA
683 select FB_CFB_IMAGEBLIT
688 STI refers to the HP "Standard Text Interface" which is a set of
689 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
690 Enabling this option will implement the linux framebuffer device
691 using calls to the STI BIOS routines for initialisation.
693 If you enable this option, you will get a planar framebuffer device
694 /dev/fb which will work on the most common HP graphic cards of the
695 NGLE family, including the artist chips (in the 7xx and Bxxx series),
696 HCRX, HCRX24, CRX, CRX24 and VisEG series.
698 It is safe to enable this option, so you should probably say "Y".
701 bool "Generic Macintosh display support"
702 depends on (FB = y) && MAC
703 select FB_CFB_FILLRECT
704 select FB_CFB_COPYAREA
705 select FB_CFB_IMAGEBLIT
710 depends on (FB = y) && DIO
711 select FB_CFB_IMAGEBLIT
715 tristate "TGA/SFB+ framebuffer support"
716 depends on FB && (ALPHA || TC)
717 select FB_CFB_FILLRECT
718 select FB_CFB_COPYAREA
719 select FB_CFB_IMAGEBLIT
722 This is the frame buffer device driver for generic TGA and SFB+
723 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
724 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
725 TURBOchannel cards, also known as PMAGD-A, -B and -C.
727 Due to hardware limitations ZLX-E2 and E3 cards are not supported
728 for DECstation 5000/200 systems. Additionally due to firmware
729 limitations these cards may cause troubles with booting DECstation
730 5000/240 and /260 systems, but are fully supported under Linux if
731 you manage to get it going. ;-)
733 Say Y if you have one of those.
736 tristate "Userspace VESA VGA graphics support"
737 depends on FB && CONNECTOR
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
741 select FB_MODE_HELPERS
743 This is the frame buffer driver for generic VBE 2.0 compliant
744 graphic cards. It can also take advantage of VBE 3.0 features,
745 such as refresh rate adjustment.
747 This driver generally provides more features than vesafb but
748 requires a userspace helper application called 'v86d'. See
749 <file:Documentation/fb/uvesafb.txt> for more information.
754 bool "VESA VGA graphics support"
755 depends on (FB = y) && X86
756 select FB_CFB_FILLRECT
757 select FB_CFB_COPYAREA
758 select FB_CFB_IMAGEBLIT
759 select FB_BOOT_VESA_SUPPORT
761 This is the frame buffer device driver for generic VESA 2.0
762 compliant graphic cards. The older VESA 1.2 cards are not supported.
763 You will get a boot time penguin logo at no additional cost. Please
764 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
767 bool "EFI-based Framebuffer Support"
768 depends on (FB = y) && !IA64 && EFI
769 select FB_CFB_FILLRECT
770 select FB_CFB_COPYAREA
771 select FB_CFB_IMAGEBLIT
773 This is the EFI frame buffer device driver. If the firmware on
774 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
775 using the EFI framebuffer as your console.
778 tristate "N411 Apollo/Hecuba devkit support"
779 depends on FB && X86 && MMU
780 select FB_SYS_FILLRECT
781 select FB_SYS_COPYAREA
782 select FB_SYS_IMAGEBLIT
784 select FB_DEFERRED_IO
787 This enables support for the Apollo display controller in its
788 Hecuba form using the n411 devkit.
791 tristate "Hercules mono graphics support"
794 Say Y here if you have a Hercules mono graphics card.
796 To compile this driver as a module, choose M here: the
797 module will be called hgafb.
799 As this card technology is at least 25 years old,
800 most people will answer N here.
803 bool "SGI Graphics Backend frame buffer support"
804 depends on (FB = y) && SGI_IP32
805 select FB_CFB_FILLRECT
806 select FB_CFB_COPYAREA
807 select FB_CFB_IMAGEBLIT
809 This is the frame buffer device driver for SGI Graphics Backend.
810 This chip is used in SGI O2 and Visual Workstation 320/540.
813 int "Video memory size in MB"
817 This is the amount of memory reserved for the framebuffer,
818 which can be any value between 1MB and 8MB.
821 bool "SBUS and UPA framebuffers"
822 depends on (FB = y) && SPARC
824 Say Y if you want support for SBUS or UPA based frame buffer device.
828 depends on (FB = y) && (SPARC && FB_SBUS)
829 select FB_CFB_FILLRECT
830 select FB_CFB_COPYAREA
831 select FB_CFB_IMAGEBLIT
833 This is the frame buffer device driver for the BWtwo frame buffer.
836 bool "CGthree support"
837 depends on (FB = y) && (SPARC && FB_SBUS)
838 select FB_CFB_FILLRECT
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 This is the frame buffer device driver for the CGthree frame buffer.
845 bool "CGsix (GX,TurboGX) support"
846 depends on (FB = y) && (SPARC && FB_SBUS)
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This is the frame buffer device driver for the CGsix (GX, TurboGX)
854 bool "Creator/Creator3D/Elite3D support"
855 depends on FB_SBUS && SPARC64
856 select FB_CFB_COPYAREA
857 select FB_CFB_IMAGEBLIT
859 This is the frame buffer device driver for the Creator, Creator3D,
860 and Elite3D graphics boards.
863 bool "TCX (SS4/SS5 only) support"
865 select FB_CFB_FILLRECT
866 select FB_CFB_COPYAREA
867 select FB_CFB_IMAGEBLIT
869 This is the frame buffer device driver for the TCX 24/8bit frame
873 bool "CGfourteen (SX) support"
875 select FB_CFB_FILLRECT
876 select FB_CFB_COPYAREA
877 select FB_CFB_IMAGEBLIT
879 This is the frame buffer device driver for the CGfourteen frame
880 buffer on Desktop SPARCsystems with the SX graphics option.
883 bool "P9100 (Sparcbook 3 only) support"
885 select FB_CFB_FILLRECT
886 select FB_CFB_COPYAREA
887 select FB_CFB_IMAGEBLIT
889 This is the frame buffer device driver for the P9100 card
890 supported on Sparcbook 3 machines.
893 bool "Leo (ZX) support"
895 select FB_CFB_FILLRECT
896 select FB_CFB_COPYAREA
897 select FB_CFB_IMAGEBLIT
899 This is the frame buffer device driver for the SBUS-based Sun ZX
900 (leo) frame buffer cards.
903 bool "IGA 168x display support"
904 depends on (FB = y) && SPARC32
905 select FB_CFB_FILLRECT
906 select FB_CFB_COPYAREA
907 select FB_CFB_IMAGEBLIT
909 This is the framebuffer device for the INTERGRAPHICS 1680 and
910 successor frame buffer cards.
913 bool "Sun XVR-500 3DLABS Wildcat support"
914 depends on (FB = y) && PCI && SPARC64
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the framebuffer device for the Sun XVR-500 and similar
920 graphics cards based upon the 3DLABS Wildcat chipset. The driver
921 only works on sparc64 systems where the system firmware has
922 mostly initialized the card already. It is treated as a
923 completely dumb framebuffer device.
926 bool "Sun XVR-2500 3DLABS Wildcat support"
927 depends on (FB = y) && PCI && SPARC64
928 select FB_CFB_FILLRECT
929 select FB_CFB_COPYAREA
930 select FB_CFB_IMAGEBLIT
932 This is the framebuffer device for the Sun XVR-2500 and similar
933 graphics cards based upon the 3DLABS Wildcat chipset. The driver
934 only works on sparc64 systems where the system firmware has
935 mostly initialized the card already. It is treated as a
936 completely dumb framebuffer device.
939 bool "Sun XVR-1000 support"
940 depends on (FB = y) && SPARC64
941 select FB_CFB_FILLRECT
942 select FB_CFB_COPYAREA
943 select FB_CFB_IMAGEBLIT
945 This is the framebuffer device for the Sun XVR-1000 and similar
946 graphics cards. The driver only works on sparc64 systems where
947 the system firmware has mostly initialized the card already. It
948 is treated as a completely dumb framebuffer device.
951 tristate "NEC PowerVR 2 display support"
952 depends on FB && SH_DREAMCAST
953 select FB_CFB_FILLRECT
954 select FB_CFB_COPYAREA
955 select FB_CFB_IMAGEBLIT
957 Say Y here if you have a PowerVR 2 card in your box. If you plan to
958 run linux on your Dreamcast, you will have to say Y here.
959 This driver may or may not work on other PowerVR 2 cards, but is
960 totally untested. Use at your own risk. If unsure, say N.
962 To compile this driver as a module, choose M here: the
963 module will be called pvr2fb.
965 You can pass several parameters to the driver at boot time or at
966 module load time. The parameters look like "video=pvr2:XXX", where
967 the meaning of XXX can be found at the end of the main source file
968 (<file:drivers/video/pvr2fb.c>). Please see the file
969 <file:Documentation/fb/pvr2fb.txt>.
972 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
973 depends on FB && HAS_DMA
974 select FB_CFB_FILLRECT
975 select FB_CFB_COPYAREA
976 select FB_CFB_IMAGEBLIT
978 This enables support for the OpenCores VGA/LCD core.
980 The OpenCores VGA/LCD core is typically used together with
981 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
982 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
984 The source code and specification for the core is available at
985 <http://opencores.org/project,vga_lcd>
988 tristate "Epson S1D13XXX framebuffer support"
990 select FB_CFB_FILLRECT
991 select FB_CFB_COPYAREA
992 select FB_CFB_IMAGEBLIT
994 Support for S1D13XXX framebuffer device family (currently only
995 working with S1D13806). Product specs at
996 <http://vdc.epson.com/>
999 tristate "AT91/AT32 LCD Controller support"
1000 depends on FB && HAVE_FB_ATMEL
1002 select FB_CFB_FILLRECT
1003 select FB_CFB_COPYAREA
1004 select FB_CFB_IMAGEBLIT
1005 select FB_MODE_HELPERS
1006 select VIDEOMODE_HELPERS
1008 This enables support for the AT91/AT32 LCD Controller.
1011 tristate "nVidia Framebuffer Support"
1012 depends on FB && PCI
1013 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1014 select FB_MODE_HELPERS
1015 select FB_CFB_FILLRECT
1016 select FB_CFB_COPYAREA
1017 select FB_CFB_IMAGEBLIT
1021 This driver supports graphics boards with the nVidia chips, TNT
1022 and newer. For very old chipsets, such as the RIVA128, then use
1024 Say Y if you have such a graphics board.
1026 To compile this driver as a module, choose M here: the
1027 module will be called nvidiafb.
1029 config FB_NVIDIA_I2C
1030 bool "Enable DDC Support"
1031 depends on FB_NVIDIA
1034 This enables I2C support for nVidia Chipsets. This is used
1035 only for getting EDID information from the attached display
1036 allowing for robust video mode handling and switching.
1038 Because fbdev-2.6 requires that drivers must be able to
1039 independently validate video mode parameters, you should say Y
1042 config FB_NVIDIA_DEBUG
1043 bool "Lots of debug output"
1044 depends on FB_NVIDIA
1047 Say Y here if you want the nVidia driver to output all sorts
1048 of debugging information to provide to the maintainer when
1049 something goes wrong.
1051 config FB_NVIDIA_BACKLIGHT
1052 bool "Support for backlight control"
1053 depends on FB_NVIDIA
1056 Say Y here if you want to control the backlight of your display.
1059 tristate "nVidia Riva support"
1060 depends on FB && PCI
1061 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1062 select FB_MODE_HELPERS
1063 select FB_CFB_FILLRECT
1064 select FB_CFB_COPYAREA
1065 select FB_CFB_IMAGEBLIT
1069 This driver supports graphics boards with the nVidia Riva/Geforce
1071 Say Y if you have such a graphics board.
1073 To compile this driver as a module, choose M here: the
1074 module will be called rivafb.
1077 bool "Enable DDC Support"
1081 This enables I2C support for nVidia Chipsets. This is used
1082 only for getting EDID information from the attached display
1083 allowing for robust video mode handling and switching.
1085 Because fbdev-2.6 requires that drivers must be able to
1086 independently validate video mode parameters, you should say Y
1089 config FB_RIVA_DEBUG
1090 bool "Lots of debug output"
1094 Say Y here if you want the Riva driver to output all sorts
1095 of debugging information to provide to the maintainer when
1096 something goes wrong.
1098 config FB_RIVA_BACKLIGHT
1099 bool "Support for backlight control"
1103 Say Y here if you want to control the backlight of your display.
1106 tristate "Intel740 support"
1107 depends on FB && PCI
1108 select FB_MODE_HELPERS
1109 select FB_CFB_FILLRECT
1110 select FB_CFB_COPYAREA
1111 select FB_CFB_IMAGEBLIT
1115 This driver supports graphics cards based on Intel740 chip.
1118 tristate "Intel 810/815 support"
1119 depends on FB && PCI && X86_32 && AGP_INTEL
1120 select FB_MODE_HELPERS
1121 select FB_CFB_FILLRECT
1122 select FB_CFB_COPYAREA
1123 select FB_CFB_IMAGEBLIT
1126 This driver supports the on-board graphics built in to the Intel 810
1127 and 815 chipsets. Say Y if you have and plan to use such a board.
1129 To compile this driver as a module, choose M here: the
1130 module will be called i810fb.
1132 For more information, please read
1133 <file:Documentation/fb/intel810.txt>
1136 bool "use VESA Generalized Timing Formula"
1139 If you say Y, then the VESA standard, Generalized Timing Formula
1140 or GTF, will be used to calculate the required video timing values
1141 per video mode. Since the GTF allows nondiscrete timings
1142 (nondiscrete being a range of values as opposed to discrete being a
1143 set of values), you'll be able to use any combination of horizontal
1144 and vertical resolutions, and vertical refresh rates without having
1145 to specify your own timing parameters. This is especially useful
1146 to maximize the performance of an aging display, or if you just
1147 have a display with nonstandard dimensions. A VESA compliant
1148 monitor is recommended, but can still work with non-compliant ones.
1149 If you need or want this, then select this option. The timings may
1150 not be compliant with Intel's recommended values. Use at your own
1153 If you say N, the driver will revert to discrete video timings
1154 using a set recommended by Intel in their documentation.
1159 bool "Enable DDC Support"
1160 depends on FB_I810 && FB_I810_GTF
1165 tristate "Intel LE80578 (Vermilion) support"
1166 depends on FB && PCI && X86
1167 select FB_MODE_HELPERS
1168 select FB_CFB_FILLRECT
1169 select FB_CFB_COPYAREA
1170 select FB_CFB_IMAGEBLIT
1172 This driver supports the LE80578 (Vermilion Range) chipset
1174 config FB_CARILLO_RANCH
1175 tristate "Intel Carillo Ranch support"
1176 depends on FB_LE80578 && FB && PCI && X86
1178 This driver supports the LE80578 (Carillo Ranch) board
1181 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1182 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1183 select FB_MODE_HELPERS
1184 select FB_CFB_FILLRECT
1185 select FB_CFB_COPYAREA
1186 select FB_CFB_IMAGEBLIT
1187 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1188 depends on !DRM_I915
1190 This driver supports the on-board graphics built in to the Intel
1191 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1192 Say Y if you have and plan to use such a board.
1194 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1196 To compile this driver as a module, choose M here: the
1197 module will be called intelfb.
1199 For more information, please read <file:Documentation/fb/intelfb.txt>
1201 config FB_INTEL_DEBUG
1202 bool "Intel driver Debug Messages"
1205 Say Y here if you want the Intel driver to output all sorts
1206 of debugging information to provide to the maintainer when
1207 something goes wrong.
1210 bool "DDC/I2C for Intel framebuffer support"
1215 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1218 tristate "Matrox acceleration"
1219 depends on FB && PCI
1220 select FB_CFB_FILLRECT
1221 select FB_CFB_COPYAREA
1222 select FB_CFB_IMAGEBLIT
1223 select FB_TILEBLITTING
1224 select FB_MACMODES if PPC_PMAC
1226 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1227 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1228 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1229 Matrox G400, G450 or G550 card in your box.
1231 To compile this driver as a module, choose M here: the
1232 module will be called matroxfb.
1234 You can pass several parameters to the driver at boot time or at
1235 module load time. The parameters look like "video=matroxfb:XXX", and
1236 are described in <file:Documentation/fb/matroxfb.txt>.
1238 config FB_MATROX_MILLENIUM
1239 bool "Millennium I/II support"
1240 depends on FB_MATROX
1242 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1243 video card. If you select "Advanced lowlevel driver options" below,
1244 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1245 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1246 also use font widths different from 8.
1248 config FB_MATROX_MYSTIQUE
1249 bool "Mystique support"
1250 depends on FB_MATROX
1252 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1253 video card. If you select "Advanced lowlevel driver options" below,
1254 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1255 packed pixel and 32 bpp packed pixel. You can also use font widths
1259 bool "G100/G200/G400/G450/G550 support"
1260 depends on FB_MATROX
1262 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1263 video card. If you select "Advanced lowlevel driver options", you
1264 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1265 pixel and 32 bpp packed pixel. You can also use font widths
1268 If you need support for G400 secondary head, you must say Y to
1269 "Matrox I2C support" and "G400 second head support" right below.
1270 G450/G550 secondary head and digital output are supported without
1273 The driver starts in monitor mode. You must use the matroxset tool
1274 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1275 swap primary and secondary head outputs, or to change output mode.
1276 Secondary head driver always start in 640x480 resolution and you
1277 must use fbset to change it.
1279 Do not forget that second head supports only 16 and 32 bpp
1280 packed pixels, so it is a good idea to compile them into the kernel
1281 too. You can use only some font widths, as the driver uses generic
1282 painting procedures (the secondary head does not use acceleration
1285 G450/G550 hardware can display TV picture only from secondary CRTC,
1286 and it performs no scaling, so picture must have 525 or 625 lines.
1288 config FB_MATROX_I2C
1289 tristate "Matrox I2C support"
1290 depends on FB_MATROX
1293 This drivers creates I2C buses which are needed for accessing the
1294 DDC (I2C) bus present on all Matroxes, an I2C bus which
1295 interconnects Matrox optional devices, like MGA-TVO on G200 and
1296 G400, and the secondary head DDC bus, present on G400 only.
1298 You can say Y or M here if you want to experiment with monitor
1299 detection code. You must say Y or M here if you want to use either
1300 second head of G400 or MGA-TVO on G200 or G400.
1302 If you compile it as module, it will create a module named
1305 config FB_MATROX_MAVEN
1306 tristate "G400 second head support"
1307 depends on FB_MATROX_G && FB_MATROX_I2C
1309 WARNING !!! This support does not work with G450 !!!
1311 Say Y or M here if you want to use a secondary head (meaning two
1312 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1313 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1314 secondary head output is blanked while you are in X. With XFree
1315 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1316 the fbdev driver on first head and the fbdev driver on second head.
1318 If you compile it as module, two modules are created,
1319 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1320 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1321 also load i2c-matroxfb to get it to run.
1323 The driver starts in monitor mode and you must use the matroxset
1325 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1326 PAL or NTSC or to swap primary and secondary head outputs.
1327 Secondary head driver also always start in 640x480 resolution, you
1328 must use fbset to change it.
1330 Also do not forget that second head supports only 16 and 32 bpp
1331 packed pixels, so it is a good idea to compile them into the kernel
1332 too. You can use only some font widths, as the driver uses generic
1333 painting procedures (the secondary head does not use acceleration
1337 tristate "ATI Radeon display support"
1338 depends on FB && PCI
1339 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1340 select FB_MODE_HELPERS
1341 select FB_CFB_FILLRECT
1342 select FB_CFB_COPYAREA
1343 select FB_CFB_IMAGEBLIT
1344 select FB_MACMODES if PPC
1346 Choose this option if you want to use an ATI Radeon graphics card as
1347 a framebuffer device. There are both PCI and AGP versions. You
1348 don't need to choose this to run the Radeon in plain VGA mode.
1350 There is a product page at
1351 http://products.amd.com/en-us/GraphicCardResult.aspx
1353 config FB_RADEON_I2C
1354 bool "DDC/I2C for ATI Radeon support"
1355 depends on FB_RADEON
1359 Say Y here if you want DDC/I2C support for your Radeon board.
1361 config FB_RADEON_BACKLIGHT
1362 bool "Support for backlight control"
1363 depends on FB_RADEON
1366 Say Y here if you want to control the backlight of your display.
1368 config FB_RADEON_DEBUG
1369 bool "Lots of debug output from Radeon driver"
1370 depends on FB_RADEON
1373 Say Y here if you want the Radeon driver to output all sorts
1374 of debugging information to provide to the maintainer when
1375 something goes wrong.
1378 tristate "ATI Rage128 display support"
1379 depends on FB && PCI
1380 select FB_CFB_FILLRECT
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1383 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1384 select FB_MACMODES if PPC_PMAC
1386 This driver supports graphics boards with the ATI Rage128 chips.
1387 Say Y if you have such a graphics board and read
1388 <file:Documentation/fb/aty128fb.txt>.
1390 To compile this driver as a module, choose M here: the
1391 module will be called aty128fb.
1393 config FB_ATY128_BACKLIGHT
1394 bool "Support for backlight control"
1395 depends on FB_ATY128
1398 Say Y here if you want to control the backlight of your display.
1401 tristate "ATI Mach64 display support" if PCI || ATARI
1402 depends on FB && !SPARC32
1403 select FB_CFB_FILLRECT
1404 select FB_CFB_COPYAREA
1405 select FB_CFB_IMAGEBLIT
1406 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1407 select FB_MACMODES if PPC
1409 This driver supports graphics boards with the ATI Mach64 chips.
1410 Say Y if you have such a graphics board.
1412 To compile this driver as a module, choose M here: the
1413 module will be called atyfb.
1416 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1417 depends on PCI && FB_ATY
1418 default y if SPARC64 && PCI
1420 Say Y here to support use of ATI's 64-bit Rage boards (or other
1421 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1422 framebuffer device. The ATI product support page for these boards
1423 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1425 config FB_ATY_GENERIC_LCD
1426 bool "Mach64 generic LCD support"
1427 depends on FB_ATY_CT
1429 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1430 Rage XC, or Rage XL chipset.
1433 bool "Mach64 GX support" if PCI
1437 Say Y here to support use of the ATI Mach64 Graphics Expression
1438 board (or other boards based on the Mach64 GX chipset) as a
1439 framebuffer device. The ATI product support page for these boards
1441 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1443 config FB_ATY_BACKLIGHT
1444 bool "Support for backlight control"
1448 Say Y here if you want to control the backlight of your display.
1451 tristate "S3 Trio/Virge support"
1452 depends on FB && PCI
1453 select FB_CFB_FILLRECT
1454 select FB_CFB_COPYAREA
1455 select FB_CFB_IMAGEBLIT
1456 select FB_TILEBLITTING
1459 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1461 Driver for graphics boards with S3 Trio / S3 Virge chip.
1464 bool "DDC for S3 support"
1469 Say Y here if you want DDC support for your S3 graphics card.
1472 tristate "S3 Savage support"
1473 depends on FB && PCI
1474 select FB_MODE_HELPERS
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1480 This driver supports notebooks and computers with S3 Savage PCI/AGP
1483 Say Y if you have such a graphics card.
1485 To compile this driver as a module, choose M here; the module
1486 will be called savagefb.
1488 config FB_SAVAGE_I2C
1489 bool "Enable DDC2 Support"
1490 depends on FB_SAVAGE
1493 This enables I2C support for S3 Savage Chipsets. This is used
1494 only for getting EDID information from the attached display
1495 allowing for robust video mode handling and switching.
1497 Because fbdev-2.6 requires that drivers must be able to
1498 independently validate video mode parameters, you should say Y
1501 config FB_SAVAGE_ACCEL
1502 bool "Enable Console Acceleration"
1503 depends on FB_SAVAGE
1506 This option will compile in console acceleration support. If
1507 the resulting framebuffer console has bothersome glitches, then
1511 tristate "SiS/XGI display support"
1512 depends on FB && PCI
1513 select FB_CFB_FILLRECT
1514 select FB_CFB_COPYAREA
1515 select FB_CFB_IMAGEBLIT
1516 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1517 select FB_SIS_300 if !FB_SIS_315
1519 This is the frame buffer device driver for the SiS 300, 315, 330
1520 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1521 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1523 To compile this driver as a module, choose M here; the module
1524 will be called sisfb.
1527 bool "SiS 300 series support"
1530 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1533 bool "SiS 315/330/340 series and XGI support"
1536 Say Y here to support use of the SiS 315, 330 and 340 series
1537 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1538 as XGI V3XT, V5, V8 and Z7.
1541 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1542 depends on FB && PCI && X86 && GPIOLIB && I2C
1543 select FB_CFB_FILLRECT
1544 select FB_CFB_COPYAREA
1545 select FB_CFB_IMAGEBLIT
1548 This is the frame buffer device driver for Graphics chips of VIA
1549 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1550 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1552 Say Y if you have a VIA UniChrome graphics board.
1554 To compile this driver as a module, choose M here: the
1555 module will be called viafb.
1559 config FB_VIA_DIRECT_PROCFS
1560 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1564 Allow direct hardware access to some output registers via procfs.
1565 This is dangerous but may provide the only chance to get the
1566 correct output device configuration.
1567 Its use is strongly discouraged.
1569 config FB_VIA_X_COMPATIBILITY
1570 bool "X server compatibility"
1574 This option reduces the functionality (power saving, ...) of the
1575 framebuffer to avoid negative impact on the OpenChrome X server.
1576 If you use any X server other than fbdev you should enable this
1577 otherwise it should be safe to disable it and allow using all
1583 tristate "NeoMagic display support"
1584 depends on FB && PCI
1585 select FB_MODE_HELPERS
1586 select FB_CFB_FILLRECT
1587 select FB_CFB_COPYAREA
1588 select FB_CFB_IMAGEBLIT
1591 This driver supports notebooks with NeoMagic PCI chips.
1592 Say Y if you have such a graphics card.
1594 To compile this driver as a module, choose M here: the
1595 module will be called neofb.
1598 tristate "IMG Kyro support"
1599 depends on FB && PCI
1600 select FB_CFB_FILLRECT
1601 select FB_CFB_COPYAREA
1602 select FB_CFB_IMAGEBLIT
1604 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1607 To compile this driver as a module, choose M here: the
1608 module will be called kyrofb.
1611 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1612 depends on FB && PCI
1613 select FB_CFB_IMAGEBLIT
1614 select FB_CFB_FILLRECT
1615 select FB_CFB_COPYAREA
1616 select FB_MODE_HELPERS
1618 This driver supports graphics boards with the 3Dfx Banshee,
1619 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1620 such a graphics board.
1622 To compile this driver as a module, choose M here: the
1623 module will be called tdfxfb.
1625 config FB_3DFX_ACCEL
1626 bool "3Dfx Acceleration functions"
1629 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1630 device driver with acceleration functions.
1633 bool "Enable DDC/I2C support"
1638 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1641 tristate "3Dfx Voodoo Graphics (sst1) support"
1642 depends on FB && PCI
1643 select FB_CFB_FILLRECT
1644 select FB_CFB_COPYAREA
1645 select FB_CFB_IMAGEBLIT
1647 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1648 Voodoo2 (cvg) based graphics card.
1650 To compile this driver as a module, choose M here: the
1651 module will be called sstfb.
1653 WARNING: Do not use any application that uses the 3D engine
1654 (namely glide) while using this driver.
1655 Please read the <file:Documentation/fb/sstfb.txt> for supported
1656 options and other important info support.
1659 tristate "VIA VT8623 support"
1660 depends on FB && PCI
1661 select FB_CFB_FILLRECT
1662 select FB_CFB_COPYAREA
1663 select FB_CFB_IMAGEBLIT
1664 select FB_TILEBLITTING
1667 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1669 Driver for CastleRock integrated graphics core in the
1670 VIA VT8623 [Apollo CLE266] chipset.
1673 tristate "Trident/CyberXXX/CyberBlade support"
1674 depends on FB && PCI
1675 select FB_CFB_FILLRECT
1676 select FB_CFB_COPYAREA
1677 select FB_CFB_IMAGEBLIT
1679 select FB_MODE_HELPERS
1681 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1682 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1684 There are also integrated versions of these chips called CyberXXXX,
1685 CyberImage or CyberBlade. These chips are mostly found in laptops
1686 but also on some motherboards including early VIA EPIA motherboards.
1687 For more information, read <file:Documentation/fb/tridentfb.txt>
1689 Say Y if you have such a graphics board.
1691 To compile this driver as a module, choose M here: the
1692 module will be called tridentfb.
1695 tristate "ARK 2000PV support"
1696 depends on FB && PCI
1697 select FB_CFB_FILLRECT
1698 select FB_CFB_COPYAREA
1699 select FB_CFB_IMAGEBLIT
1700 select FB_TILEBLITTING
1703 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1705 Driver for PCI graphics boards with ARK 2000PV chip
1706 and ICS 5342 RAMDAC.
1709 tristate "Permedia3 support"
1710 depends on FB && PCI
1711 select FB_CFB_FILLRECT
1712 select FB_CFB_COPYAREA
1713 select FB_CFB_IMAGEBLIT
1715 This is the frame buffer device driver for the 3DLabs Permedia3
1716 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1717 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1718 and maybe other boards.
1721 tristate "Fujitsu carmine frame buffer support"
1722 depends on FB && PCI
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 This is the frame buffer device driver for the Fujitsu Carmine chip.
1728 The driver provides two independent frame buffer devices.
1731 depends on FB_CARMINE
1732 prompt "DRAM timing"
1733 default FB_CARMINE_DRAM_EVAL
1735 config FB_CARMINE_DRAM_EVAL
1736 bool "Eval board timings"
1738 Use timings which work on the eval card.
1740 config CARMINE_DRAM_CUSTOM
1741 bool "Custom board timings"
1743 Use custom board timings.
1747 bool "Au1100 LCD Driver"
1748 depends on (FB = y) && MIPS_ALCHEMY
1749 select FB_CFB_FILLRECT
1750 select FB_CFB_COPYAREA
1751 select FB_CFB_IMAGEBLIT
1753 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1754 various panels and CRTs by passing in kernel cmd line option
1755 au1100fb:panel=<name>.
1758 bool "Au1200/Au1300 LCD Driver"
1759 depends on (FB = y) && MIPS_ALCHEMY
1760 select FB_SYS_FILLRECT
1761 select FB_SYS_COPYAREA
1762 select FB_SYS_IMAGEBLIT
1765 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1766 It can drive various panels and CRTs by passing in kernel cmd line
1767 option au1200fb:panel=<name>.
1770 bool "VIA VT8500 framebuffer support"
1771 depends on (FB = y) && ARM && ARCH_VT8500
1772 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1773 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1774 select FB_SYS_IMAGEBLIT
1775 select FB_MODE_HELPERS
1776 select VIDEOMODE_HELPERS
1778 This is the framebuffer driver for VIA VT8500 integrated LCD
1782 bool "Wondermedia WM8xxx-series frame buffer support"
1783 depends on (FB = y) && ARM && ARCH_VT8500
1784 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1785 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1786 select FB_SYS_IMAGEBLIT
1787 select FB_MODE_HELPERS
1788 select VIDEOMODE_HELPERS
1790 This is the framebuffer driver for WonderMedia WM8xxx-series
1791 integrated LCD controller. This driver covers the WM8505, WM8650
1794 config FB_WMT_GE_ROPS
1795 bool "VT8500/WM8xxx accelerated raster ops support"
1796 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1799 This adds support for accelerated raster operations on the
1800 VIA VT8500 and Wondermedia 85xx series SoCs.
1802 source "drivers/video/fbdev/geode/Kconfig"
1805 tristate "HD64461 Frame Buffer support"
1806 depends on FB && HD64461
1807 select FB_CFB_FILLRECT
1808 select FB_CFB_COPYAREA
1809 select FB_CFB_IMAGEBLIT
1811 This is the frame buffer device driver for the Hitachi HD64461 LCD
1815 tristate "PMAG-AA TURBOchannel framebuffer support"
1817 select FB_CFB_FILLRECT
1818 select FB_CFB_COPYAREA
1819 select FB_CFB_IMAGEBLIT
1821 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1822 used mainly in the MIPS-based DECstation series.
1825 tristate "PMAG-BA TURBOchannel framebuffer support"
1827 select FB_CFB_FILLRECT
1828 select FB_CFB_COPYAREA
1829 select FB_CFB_IMAGEBLIT
1831 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1832 used mainly in the MIPS-based DECstation series.
1835 tristate "PMAGB-B TURBOchannel framebuffer support"
1837 select FB_CFB_FILLRECT
1838 select FB_CFB_COPYAREA
1839 select FB_CFB_IMAGEBLIT
1841 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1842 in the MIPS-based DECstation series. The card is currently only
1843 supported in 1280x1024x8 mode.
1846 bool "Maxine (Personal DECstation) onboard framebuffer support"
1847 depends on (FB = y) && MACH_DECSTATION
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 Support for the onboard framebuffer (1024x768x8) in the Personal
1853 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1857 bool "G364 frame buffer support"
1858 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1859 select FB_CFB_FILLRECT
1860 select FB_CFB_COPYAREA
1861 select FB_CFB_IMAGEBLIT
1863 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1864 Olivetti M700-10 systems.
1867 bool "Motorola 68328 native frame buffer support"
1868 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1869 select FB_CFB_FILLRECT
1870 select FB_CFB_COPYAREA
1871 select FB_CFB_IMAGEBLIT
1873 Say Y here if you want to support the built-in frame buffer of
1874 the Motorola 68328 CPU family.
1877 tristate "PXA168/910 LCD framebuffer support"
1878 depends on FB && (CPU_PXA168 || CPU_PXA910)
1879 select FB_CFB_FILLRECT
1880 select FB_CFB_COPYAREA
1881 select FB_CFB_IMAGEBLIT
1883 Frame buffer driver for the built-in LCD controller in the Marvell
1887 tristate "PXA LCD framebuffer support"
1888 depends on FB && ARCH_PXA
1889 select FB_CFB_FILLRECT
1890 select FB_CFB_COPYAREA
1891 select FB_CFB_IMAGEBLIT
1892 select VIDEOMODE_HELPERS if OF
1893 select FB_MODE_HELPERS if OF
1895 Frame buffer driver for the built-in LCD controller in the Intel
1898 This driver is also available as a module ( = code which can be
1899 inserted and removed from the running kernel whenever you want). The
1900 module will be called pxafb. If you want to compile it as a module,
1901 say M here and read <file:Documentation/kbuild/modules.txt>.
1905 config FB_PXA_OVERLAY
1906 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1908 depends on FB_PXA && (PXA27x || PXA3xx)
1910 config FB_PXA_SMARTPANEL
1911 bool "PXA Smartpanel LCD support"
1915 config FB_PXA_PARAMETERS
1916 bool "PXA LCD command line parameters"
1920 Enable the use of kernel command line or module parameters
1921 to configure the physical properties of the LCD panel when
1922 using the PXA LCD driver.
1924 This option allows you to override the panel parameters
1925 supplied by the platform in order to support multiple
1926 different models of flatpanel. If you will only be using a
1927 single model of flatpanel then you can safely leave this
1930 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1933 tristate "PXA3xx 2D graphics accelerator driver"
1936 Kernelspace driver for the 2D graphics controller unit (GCU)
1937 found on PXA3xx processors. There is a counterpart driver in the
1938 DirectFB suite, see http://www.directfb.org/
1940 If you compile this as a module, it will be called pxa3xx_gcu.
1943 tristate "2700G LCD framebuffer support"
1944 depends on FB && ARCH_PXA
1945 select FB_CFB_FILLRECT
1946 select FB_CFB_COPYAREA
1947 select FB_CFB_IMAGEBLIT
1949 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1953 bool "Enable debugging info via debugfs"
1954 depends on FB_MBX && DEBUG_FS
1957 Enable this if you want debugging information using the debug
1958 filesystem (debugfs)
1963 tristate "Freescale DIU framebuffer support"
1964 depends on FB && FSL_SOC
1965 select FB_MODE_HELPERS
1966 select FB_CFB_FILLRECT
1967 select FB_CFB_COPYAREA
1968 select FB_CFB_IMAGEBLIT
1969 select PPC_LIB_RHEAP
1971 Framebuffer driver for the Freescale SoC DIU
1974 tristate "W100 frame buffer support"
1975 depends on FB && ARCH_PXA
1976 select FB_CFB_FILLRECT
1977 select FB_CFB_COPYAREA
1978 select FB_CFB_IMAGEBLIT
1980 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1981 It can also drive the w3220 chip found on iPAQ hx4700.
1983 This driver is also available as a module ( = code which can be
1984 inserted and removed from the running kernel whenever you want). The
1985 module will be called w100fb. If you want to compile it as a module,
1986 say M here and read <file:Documentation/kbuild/modules.txt>.
1990 config FB_SH_MOBILE_LCDC
1991 tristate "SuperH Mobile LCDC framebuffer support"
1992 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1993 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1994 select FB_SYS_FILLRECT
1995 select FB_SYS_COPYAREA
1996 select FB_SYS_IMAGEBLIT
1998 select FB_DEFERRED_IO
2001 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2004 tristate "Toshiba Mobile IO FrameBuffer support"
2005 depends on FB && (MFD_TMIO || COMPILE_TEST)
2006 select FB_CFB_FILLRECT
2007 select FB_CFB_COPYAREA
2008 select FB_CFB_IMAGEBLIT
2010 Frame buffer driver for the Toshiba Mobile IO integrated as found
2011 on the Sharp SL-6000 series
2013 This driver is also available as a module ( = code which can be
2014 inserted and removed from the running kernel whenever you want). The
2015 module will be called tmiofb. If you want to compile it as a module,
2016 say M here and read <file:Documentation/kbuild/modules.txt>.
2020 config FB_TMIO_ACCELL
2021 bool "tmiofb acceleration"
2026 tristate "Samsung S3C framebuffer support"
2027 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2028 ARCH_S5PV210 || ARCH_EXYNOS)
2029 select FB_CFB_FILLRECT
2030 select FB_CFB_COPYAREA
2031 select FB_CFB_IMAGEBLIT
2033 Frame buffer driver for the built-in FB controller in the Samsung
2034 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2035 and the S3C64XX series such as the S3C6400 and S3C6410.
2037 These chips all have the same basic framebuffer design with the
2038 actual capabilities depending on the chip. For instance the S3C6400
2039 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2040 currently only have two.
2042 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2044 config FB_S3C_DEBUG_REGWRITE
2045 bool "Debug register writes"
2048 Show all register writes via pr_debug()
2051 tristate "S3C2410 LCD framebuffer support"
2052 depends on FB && ARCH_S3C24XX
2053 select FB_CFB_FILLRECT
2054 select FB_CFB_COPYAREA
2055 select FB_CFB_IMAGEBLIT
2057 Frame buffer driver for the built-in LCD controller in the Samsung
2060 This driver is also available as a module ( = code which can be
2061 inserted and removed from the running kernel whenever you want). The
2062 module will be called s3c2410fb. If you want to compile it as a module,
2063 say M here and read <file:Documentation/kbuild/modules.txt>.
2066 config FB_S3C2410_DEBUG
2067 bool "S3C2410 lcd debug messages"
2068 depends on FB_S3C2410
2070 Turn on debugging messages. Note that you can set/unset at run time
2074 tristate "NUC900 LCD framebuffer support"
2075 depends on FB && ARCH_W90X900
2076 select FB_CFB_FILLRECT
2077 select FB_CFB_COPYAREA
2078 select FB_CFB_IMAGEBLIT
2080 Frame buffer driver for the built-in LCD controller in the Nuvoton
2083 config GPM1040A0_320X240
2084 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2085 depends on FB_NUC900
2088 tristate "Silicon Motion SM501 framebuffer support"
2089 depends on FB && MFD_SM501
2090 select FB_CFB_FILLRECT
2091 select FB_CFB_COPYAREA
2092 select FB_CFB_IMAGEBLIT
2094 Frame buffer driver for the CRT and LCD controllers in the Silicon
2097 This driver is also available as a module ( = code which can be
2098 inserted and removed from the running kernel whenever you want). The
2099 module will be called sm501fb. If you want to compile it as a module,
2100 say M here and read <file:Documentation/kbuild/modules.txt>.
2105 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2106 depends on FB && USB
2107 select FB_MODE_HELPERS
2108 select FB_SYS_FILLRECT
2109 select FB_SYS_COPYAREA
2110 select FB_SYS_IMAGEBLIT
2112 select FB_DEFERRED_IO
2114 This is a kernel framebuffer driver for SMSC UFX USB devices.
2115 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2116 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2118 To compile as a module, choose M here: the module name is smscufx.
2121 tristate "Displaylink USB Framebuffer support"
2122 depends on FB && USB
2123 select FB_MODE_HELPERS
2124 select FB_SYS_FILLRECT
2125 select FB_SYS_COPYAREA
2126 select FB_SYS_IMAGEBLIT
2128 select FB_DEFERRED_IO
2130 This is a kernel framebuffer driver for DisplayLink USB devices.
2131 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2132 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2133 To compile as a module, choose M here: the module name is udlfb.
2135 config FB_IBM_GXT4500
2136 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2138 select FB_CFB_FILLRECT
2139 select FB_CFB_COPYAREA
2140 select FB_CFB_IMAGEBLIT
2142 Say Y here to enable support for the IBM GXT4000P/6000P and
2143 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2144 found on some IBM System P (pSeries) machines. This driver
2145 doesn't use Geometry Engine GT1000. This driver also supports
2146 AGP Fire GL2/3/4 cards on x86.
2149 tristate "PS3 GPU framebuffer driver"
2150 depends on FB && PS3_PS3AV
2151 select FB_SYS_FILLRECT
2152 select FB_SYS_COPYAREA
2153 select FB_SYS_IMAGEBLIT
2156 Include support for the virtual frame buffer in the PS3 platform.
2158 config FB_PS3_DEFAULT_SIZE_M
2159 int "PS3 default frame buffer size (in MiB)"
2163 This is the default size (in MiB) of the virtual frame buffer in
2165 The default value can be overridden on the kernel command line
2166 using the "ps3fb" option (e.g. "ps3fb=9M");
2169 tristate "Xilinx frame buffer support"
2170 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2171 select FB_CFB_FILLRECT
2172 select FB_CFB_COPYAREA
2173 select FB_CFB_IMAGEBLIT
2175 Include support for the Xilinx ML300/ML403 reference design
2176 framebuffer. ML300 carries a 640*480 LCD display on the board,
2177 ML403 uses a standard DB15 VGA connector.
2180 tristate "Goldfish Framebuffer"
2181 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2182 select FB_CFB_FILLRECT
2183 select FB_CFB_COPYAREA
2184 select FB_CFB_IMAGEBLIT
2186 Framebuffer driver for Goldfish Virtual Platform
2189 tristate "Cobalt server LCD frame buffer support"
2190 depends on FB && MIPS_COBALT
2193 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2194 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2195 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2196 select FB_CFB_FILLRECT
2197 select FB_CFB_COPYAREA
2198 select FB_CFB_IMAGEBLIT
2200 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2201 (D)STN/TFT LCD Controller.
2202 Supports display resolutions up to 1024x1024 pixel, grayscale and
2203 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2204 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2205 panels <= 320 pixel horizontal resolution.
2208 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2209 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2210 select FB_CFB_FILLRECT
2211 select FB_CFB_COPYAREA
2212 select FB_CFB_IMAGEBLIT
2213 select FB_CFB_REV_PIXELS_IN_BYTE
2214 select FB_MODE_HELPERS
2215 select VIDEOMODE_HELPERS
2217 This is the frame buffer device driver for the TI LCD controller
2218 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2222 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2224 select FB_SYS_FILLRECT
2225 select FB_SYS_COPYAREA
2226 select FB_SYS_IMAGEBLIT
2229 This is a `virtual' frame buffer device. It operates on a chunk of
2230 unswappable kernel memory instead of on the memory of a graphics
2231 board. This means you cannot see any output sent to this frame
2232 buffer device, while it does consume precious memory. The main use
2233 of this frame buffer device is testing and debugging the frame
2234 buffer subsystem. Do NOT enable it for normal systems! To protect
2235 the innocent, it has to be enabled explicitly at boot time using the
2236 kernel option `video=vfb:'.
2238 To compile this driver as a module, choose M here: the
2239 module will be called vfb. In order to load it, you must use
2240 the vfb_enable=1 option.
2244 config XEN_FBDEV_FRONTEND
2245 tristate "Xen virtual frame buffer support"
2246 depends on FB && XEN
2247 select FB_SYS_FILLRECT
2248 select FB_SYS_COPYAREA
2249 select FB_SYS_IMAGEBLIT
2251 select FB_DEFERRED_IO
2252 select XEN_XENBUS_FRONTEND
2255 This driver implements the front-end of the Xen virtual
2256 frame buffer driver. It communicates with a back-end
2260 tristate "E-Ink Metronome/8track controller support"
2262 select FB_SYS_FILLRECT
2263 select FB_SYS_COPYAREA
2264 select FB_SYS_IMAGEBLIT
2266 select FB_DEFERRED_IO
2268 This driver implements support for the E-Ink Metronome
2269 controller. The pre-release name for this device was 8track
2270 and could also have been called by some vendors as PVI-nnnn.
2273 tristate "Fujitsu MB862xx GDC support"
2275 depends on PCI || (OF && PPC)
2276 select FB_CFB_FILLRECT
2277 select FB_CFB_COPYAREA
2278 select FB_CFB_IMAGEBLIT
2280 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2283 prompt "GDC variant"
2284 depends on FB_MB862XX
2286 config FB_MB862XX_PCI_GDC
2287 bool "Carmine/Coral-P(A) GDC"
2290 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2291 PCI graphics controller devices.
2293 config FB_MB862XX_LIME
2295 depends on OF && PPC
2296 select FB_FOREIGN_ENDIAN
2297 select FB_LITTLE_ENDIAN
2299 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2303 config FB_MB862XX_I2C
2304 bool "Support I2C bus on MB862XX GDC"
2305 depends on FB_MB862XX && I2C
2306 depends on FB_MB862XX=m || I2C=y
2309 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2310 driver to support accessing I2C devices on controller's I2C bus.
2311 These are usually some video decoder chips.
2314 tristate "EP93XX frame buffer support"
2315 depends on FB && ARCH_EP93XX
2316 select FB_CFB_FILLRECT
2317 select FB_CFB_COPYAREA
2318 select FB_CFB_IMAGEBLIT
2320 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2321 This driver is also available as a module. The module will be called
2324 config FB_PRE_INIT_FB
2325 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2326 depends on FB && FB_MB862XX_LIME
2328 Select this option if display contents should be inherited as set by
2332 tristate "MX3 Framebuffer support"
2333 depends on FB && MX3_IPU
2334 select BACKLIGHT_CLASS_DEVICE
2335 select BACKLIGHT_LCD_SUPPORT
2336 select FB_CFB_FILLRECT
2337 select FB_CFB_COPYAREA
2338 select FB_CFB_IMAGEBLIT
2341 This is a framebuffer device for the i.MX31 LCD Controller. So
2342 far only synchronous displays are supported. If you plan to use
2343 an LCD display with your i.MX31 system, say Y here.
2345 config FB_BROADSHEET
2346 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2348 select FB_SYS_FILLRECT
2349 select FB_SYS_COPYAREA
2350 select FB_SYS_IMAGEBLIT
2352 select FB_DEFERRED_IO
2354 This driver implements support for the E-Ink Broadsheet
2355 controller. The release name for this device was Epson S1D13521
2356 and could also have been called by other names when coupled with
2360 tristate "AUO-K190X EPD controller support"
2362 select FB_SYS_FILLRECT
2363 select FB_SYS_COPYAREA
2364 select FB_SYS_IMAGEBLIT
2366 select FB_DEFERRED_IO
2368 Provides support for epaper controllers from the K190X series
2369 of AUO. These controllers can be used to drive epaper displays
2372 This option enables the common support, shared by the individual
2373 controller drivers. You will also have to enable the driver
2374 for the controller type used in your device.
2377 tristate "AUO-K1900 EPD controller support"
2378 depends on FB && FB_AUO_K190X
2380 This driver implements support for the AUO K1900 epd-controller.
2381 This controller can drive Sipix epaper displays but can only do
2382 serial updates, reducing the number of possible frames per second.
2385 tristate "AUO-K1901 EPD controller support"
2386 depends on FB && FB_AUO_K190X
2388 This driver implements support for the AUO K1901 epd-controller.
2389 This controller can drive Sipix epaper displays and supports
2390 concurrent updates, making higher frames per second possible.
2393 tristate "JZ4740 LCD framebuffer support"
2394 depends on FB && MACH_JZ4740
2395 select FB_SYS_FILLRECT
2396 select FB_SYS_COPYAREA
2397 select FB_SYS_IMAGEBLIT
2399 Framebuffer support for the JZ4740 SoC.
2402 tristate "MXS LCD framebuffer support"
2403 depends on FB && (ARCH_MXS || ARCH_MXC)
2404 select FB_CFB_FILLRECT
2405 select FB_CFB_COPYAREA
2406 select FB_CFB_IMAGEBLIT
2407 select FB_MODE_HELPERS
2408 select VIDEOMODE_HELPERS
2410 Framebuffer support for the MXS SoC.
2412 config FB_PUV3_UNIGFX
2413 tristate "PKUnity v3 Unigfx framebuffer support"
2414 depends on FB && UNICORE32 && ARCH_PUV3
2415 select FB_SYS_FILLRECT
2416 select FB_SYS_COPYAREA
2417 select FB_SYS_IMAGEBLIT
2420 Choose this option if you want to use the Unigfx device as a
2421 framebuffer device. Without the support of PCI & AGP.
2424 tristate "Microsoft Hyper-V Synthetic Video support"
2425 depends on FB && HYPERV
2426 select FB_CFB_FILLRECT
2427 select FB_CFB_COPYAREA
2428 select FB_CFB_IMAGEBLIT
2430 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2433 bool "Simple framebuffer support"
2435 select FB_CFB_FILLRECT
2436 select FB_CFB_COPYAREA
2437 select FB_CFB_IMAGEBLIT
2439 Say Y if you want support for a simple frame-buffer.
2441 This driver assumes that the display hardware has been initialized
2442 before the kernel boots, and the kernel will simply render to the
2443 pre-allocated frame buffer surface.
2445 Configuration re: surface address, size, and format must be provided
2446 through device tree, or plain old platform data.
2448 source "drivers/video/fbdev/omap/Kconfig"
2449 source "drivers/video/fbdev/omap2/Kconfig"
2450 source "drivers/video/fbdev/mmp/Kconfig"
2452 config FB_SH_MOBILE_MERAM
2453 tristate "SuperH Mobile MERAM read ahead support"
2454 depends on (SUPERH || ARCH_SHMOBILE)
2455 select GENERIC_ALLOCATOR
2457 Enable MERAM support for the SuperH controller.
2459 This will allow for caching of the framebuffer to provide more
2460 reliable access under heavy main memory bus traffic situations.
2461 Up to 4 memory channels can be configured, allowing 4 RGB or
2462 2 YCbCr framebuffers to be configured.
2465 tristate "Solomon SSD1307 framebuffer support"
2466 depends on FB && I2C
2468 depends on GPIOLIB || COMPILE_TEST
2470 select FB_SYS_FILLRECT
2471 select FB_SYS_COPYAREA
2472 select FB_SYS_IMAGEBLIT
2473 select FB_DEFERRED_IO
2477 This driver implements support for the Solomon SSD1307
2478 OLED controller over I2C.
2481 tristate "Silicon Motion SM712 framebuffer support"
2482 depends on FB && PCI
2483 select FB_CFB_FILLRECT
2484 select FB_CFB_COPYAREA
2485 select FB_CFB_IMAGEBLIT
2487 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2490 This driver is also available as a module. The module will be
2491 called sm712fb. If you want to compile it as a module, say M
2492 here and read <file:Documentation/kbuild/modules.txt>.