6 tristate "Support for frame buffer devices"
8 The frame buffer device provides an abstraction for the graphics
9 hardware. It represents the frame buffer of some video hardware and
10 allows application software to access the graphics hardware through
11 a well-defined interface, so the software doesn't need to know
12 anything about the low-level (hardware register) stuff.
14 Frame buffer devices work identically across the different
15 architectures supported by Linux and make the implementation of
16 application programs easier and more portable; at this point, an X
17 server exists which uses the frame buffer device exclusively.
18 On several non-X86 architectures, the frame buffer device is the
19 only way to use the graphics hardware.
21 The device is accessed through special device nodes, usually located
22 in the /dev directory, i.e. /dev/fb*.
24 You need an utility program called fbset to make full use of frame
25 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
26 and the Framebuffer-HOWTO at
27 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
30 Say Y here and to the driver for your graphics board below if you
31 are compiling a kernel for a non-x86 architecture.
33 If you are compiling for the x86 architecture, you can say Y if you
34 want to play with it, but it is not essential. Please note that
35 running graphical applications that directly touch the hardware
36 (e.g. an accelerated X server) and that are not frame buffer
37 device-aware may cause unexpected results. If unsure, say N.
40 bool "Enable firmware EDID"
44 This enables access to the EDID transferred from the firmware.
45 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
46 transfers do not work for your driver and if you are using
47 nvidiafb, i810fb or savagefb.
49 In general, choosing Y for this option is safe. If you
50 experience extremely long delays while booting before you get
51 something on your display, try setting this to N. Matrox cards in
52 combination with certain motherboards and monitors are known to
53 suffer from this problem.
62 config FB_BOOT_VESA_SUPPORT
67 If true, at least one selected framebuffer driver can take advantage
68 of VESA video modes set at an early boot stage via the vga= parameter.
70 config FB_CFB_FILLRECT
75 Include the cfb_fillrect function for generic software rectangle
76 filling. This is used by drivers that don't provide their own
77 (accelerated) version.
79 config FB_CFB_COPYAREA
84 Include the cfb_copyarea function for generic software area copying.
85 This is used by drivers that don't provide their own (accelerated)
88 config FB_CFB_IMAGEBLIT
93 Include the cfb_imageblit function for generic software image
94 blitting. This is used by drivers that don't provide their own
95 (accelerated) version.
97 config FB_CFB_REV_PIXELS_IN_BYTE
102 Allow generic frame-buffer functions to work on displays with 1, 2
103 and 4 bits per pixel depths which has opposite order of pixels in
104 byte order to bytes in long order.
106 config FB_SYS_FILLRECT
111 Include the sys_fillrect function for generic software rectangle
112 filling. This is used by drivers that don't provide their own
113 (accelerated) version and the framebuffer is in system RAM.
115 config FB_SYS_COPYAREA
120 Include the sys_copyarea function for generic software area copying.
121 This is used by drivers that don't provide their own (accelerated)
122 version and the framebuffer is in system RAM.
124 config FB_SYS_IMAGEBLIT
129 Include the sys_imageblit function for generic software image
130 blitting. This is used by drivers that don't provide their own
131 (accelerated) version and the framebuffer is in system RAM.
133 menuconfig FB_FOREIGN_ENDIAN
134 bool "Framebuffer foreign endianness support"
137 This menu will let you enable support for the framebuffers with
138 non-native endianness (e.g. Little-Endian framebuffer on a
139 Big-Endian machine). Most probably you don't have such hardware,
140 so it's safe to say "n" here.
143 prompt "Choice endianness support"
144 depends on FB_FOREIGN_ENDIAN
146 config FB_BOTH_ENDIAN
147 bool "Support for Big- and Little-Endian framebuffers"
150 bool "Support for Big-Endian framebuffers only"
152 config FB_LITTLE_ENDIAN
153 bool "Support for Little-Endian framebuffers only"
162 config FB_DEFERRED_IO
169 depends on FB_DEFERRED_IO
176 Common utility functions useful to fbdev drivers of VGA-based
187 select BACKLIGHT_LCD_SUPPORT
188 select BACKLIGHT_CLASS_DEVICE
191 config FB_MODE_HELPERS
192 bool "Enable Video Mode Handling Helpers"
196 This enables functions for handling video modes using the
197 Generalized Timing Formula and the EDID parser. A few drivers rely
198 on this feature such as the radeonfb, rivafb, and the i810fb. If
199 your driver does not take advantage of this feature, choosing Y will
200 just increase the kernel size by about 5K.
202 config FB_TILEBLITTING
203 bool "Enable Tile Blitting Support"
207 This enables tile blitting. Tile blitting is a drawing technique
208 where the screen is divided into rectangular sections (tiles), whereas
209 the standard blitting divides the screen into pixels. Because the
210 default drawing element is a tile, drawing functions will be passed
211 parameters in terms of number of tiles instead of number of pixels.
212 For example, to draw a single character, instead of using bitmaps,
213 an index to an array of bitmaps will be used. To clear or move a
214 rectangular section of a screen, the rectangle will be described in
215 terms of number of tiles in the x- and y-axis.
217 This is particularly important to one driver, matroxfb. If
220 comment "Frame buffer hardware drivers"
224 tristate "Aeroflex Gaisler framebuffer support"
225 depends on FB && SPARC
226 select FB_CFB_FILLRECT
227 select FB_CFB_COPYAREA
228 select FB_CFB_IMAGEBLIT
230 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
233 tristate "Cirrus Logic support"
234 depends on FB && (ZORRO || PCI)
235 select FB_CFB_FILLRECT
236 select FB_CFB_COPYAREA
237 select FB_CFB_IMAGEBLIT
239 This enables support for Cirrus Logic GD542x/543x based boards on
240 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
242 If you have a PCI-based system, this enables support for these
243 chips: GD-543x, GD-544x, GD-5480.
245 Please read the file <file:Documentation/fb/cirrusfb.txt>.
247 Say N unless you have such a graphics board or plan to get one
248 before you next recompile the kernel.
251 tristate "Permedia2 support"
252 depends on FB && ((AMIGA && BROKEN) || PCI)
253 select FB_CFB_FILLRECT
254 select FB_CFB_COPYAREA
255 select FB_CFB_IMAGEBLIT
257 This is the frame buffer device driver for cards based on
258 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
259 The driver was tested on the following cards:
260 Diamond FireGL 1000 PRO AGP
261 ELSA Gloria Synergy PCI
262 Appian Jeronimo PRO (both heads) PCI
263 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
264 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
265 ASK Graphic Blaster Exxtreme AGP
267 To compile this driver as a module, choose M here: the
268 module will be called pm2fb.
270 config FB_PM2_FIFO_DISCONNECT
271 bool "enable FIFO disconnect feature"
272 depends on FB_PM2 && PCI
274 Support the Permedia2 FIFO disconnect feature.
277 tristate "ARM PrimeCell PL110 support"
278 depends on ARM || ARM64 || COMPILE_TEST
279 depends on FB && ARM_AMBA
280 select FB_CFB_FILLRECT
281 select FB_CFB_COPYAREA
282 select FB_CFB_IMAGEBLIT
284 This framebuffer device driver is for the ARM PrimeCell PL110
285 Colour LCD controller. ARM PrimeCells provide the building
286 blocks for System on a Chip devices.
288 If you want to compile this as a module (=code which can be
289 inserted into and removed from the running kernel), say M
290 here and read <file:Documentation/kbuild/modules.txt>. The module
291 will be called amba-clcd.
293 # Helper logic selected only by the ARM Versatile platform family.
294 config PLAT_VERSATILE_CLCD
295 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
296 depends on FB_ARMCLCD && FB=y
299 bool "Acorn VIDC support"
300 depends on (FB = y) && ARM && ARCH_ACORN
301 select FB_CFB_FILLRECT
302 select FB_CFB_COPYAREA
303 select FB_CFB_IMAGEBLIT
305 This is the frame buffer device driver for the Acorn VIDC graphics
306 hardware found in Acorn RISC PCs and other ARM-based machines. If
310 bool "CLPS711X LCD support"
311 depends on (FB = y) && ARM && ARCH_CLPS711X
312 select FB_CFB_FILLRECT
313 select FB_CFB_COPYAREA
314 select FB_CFB_IMAGEBLIT
316 Say Y to enable the Framebuffer driver for the CLPS7111 and
320 bool "SA-1100 LCD support"
321 depends on (FB = y) && ARM && ARCH_SA1100
322 select FB_CFB_FILLRECT
323 select FB_CFB_COPYAREA
324 select FB_CFB_IMAGEBLIT
326 This is a framebuffer device for the SA-1100 LCD Controller.
327 See <http://www.linux-fbdev.org/> for information on framebuffer
330 If you plan to use the LCD display with your SA-1100 system, say
334 tristate "Freescale i.MX1/21/25/27 LCD support"
335 depends on FB && ARCH_MXC
336 select BACKLIGHT_LCD_SUPPORT
337 select LCD_CLASS_DEVICE
338 select FB_CFB_FILLRECT
339 select FB_CFB_COPYAREA
340 select FB_CFB_IMAGEBLIT
341 select FB_MODE_HELPERS
342 select VIDEOMODE_HELPERS
345 tristate "CyberPro 2000/2010/5000 support"
346 depends on FB && PCI && (BROKEN || !SPARC64)
347 select FB_CFB_FILLRECT
348 select FB_CFB_COPYAREA
349 select FB_CFB_IMAGEBLIT
351 This enables support for the Integraphics CyberPro 20x0 and 5000
352 VGA chips used in the Rebel.com Netwinder and other machines.
353 Say Y if you have a NetWinder or a graphics card containing this
354 device, otherwise say N.
356 config FB_CYBER2000_DDC
357 bool "DDC for CyberPro support"
358 depends on FB_CYBER2000
362 Say Y here if you want DDC support for your CyberPro graphics
363 card. This is only I2C bus support, driver does not use EDID.
365 config FB_CYBER2000_I2C
366 bool "CyberPro 2000/2010/5000 I2C support"
367 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
368 depends on I2C=y || FB_CYBER2000=m
371 Enable support for the I2C video decoder interface on the
372 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
373 on the Netwinder machines for the SAA7111 video capture.
377 depends on (FB = y) && APOLLO
379 select FB_CFB_FILLRECT
380 select FB_CFB_IMAGEBLIT
384 depends on (FB = y) && Q40
386 select FB_CFB_FILLRECT
387 select FB_CFB_COPYAREA
388 select FB_CFB_IMAGEBLIT
391 tristate "Amiga native chipset support"
392 depends on FB && AMIGA
394 This is the frame buffer device driver for the builtin graphics
395 chipset found in Amigas.
397 To compile this driver as a module, choose M here: the
398 module will be called amifb.
401 bool "Amiga OCS chipset support"
404 This enables support for the original Agnus and Denise video chips,
405 found in the Amiga 1000 and most A500's and A2000's. If you intend
406 to run Linux on any of these systems, say Y; otherwise say N.
409 bool "Amiga ECS chipset support"
412 This enables support for the Enhanced Chip Set, found in later
413 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
414 you intend to run Linux on any of these systems, say Y; otherwise
418 bool "Amiga AGA chipset support"
421 This enables support for the Advanced Graphics Architecture (also
422 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
423 and CD32. If you intend to run Linux on any of these systems, say Y;
427 bool "Amiga FrameMaster II/Rainbow II support"
428 depends on (FB = y) && ZORRO
429 select FB_CFB_FILLRECT
430 select FB_CFB_COPYAREA
431 select FB_CFB_IMAGEBLIT
433 This is the frame buffer device driver for the Amiga FrameMaster
434 card from BSC (exhibited 1992 but not shipped as a CBM product).
437 tristate "Arc Monochrome LCD board support"
439 select FB_SYS_FILLRECT
440 select FB_SYS_COPYAREA
441 select FB_SYS_IMAGEBLIT
444 This enables support for the Arc Monochrome LCD board. The board
445 is based on the KS-108 lcd controller and is typically a matrix
446 of 2*n chips. This driver was tested with a 128x64 panel. This
447 driver supports it for use with x86 SBCs through a 16 bit GPIO
448 interface (8 bit data, 8 bit control). If you anticipate using
449 this driver, say Y or M; otherwise say N. You must specify the
450 GPIO IO address to be used for setting control and data.
453 bool "Atari native chipset support"
454 depends on (FB = y) && ATARI
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 builtin graphics
460 chipset found in Ataris.
463 bool "Open Firmware frame buffer device support"
464 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
465 select FB_CFB_FILLRECT
466 select FB_CFB_COPYAREA
467 select FB_CFB_IMAGEBLIT
470 Say Y if you want support with Open Firmware for your graphics
474 bool "Apple \"control\" display support"
475 depends on (FB = y) && PPC_PMAC && PPC32
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
481 This driver supports a frame buffer for the graphics adapter in the
482 Power Macintosh 7300 and others.
485 bool "Apple \"platinum\" display support"
486 depends on (FB = y) && PPC_PMAC && PPC32
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
492 This driver supports a frame buffer for the "platinum" graphics
493 adapter in some Power Macintoshes.
496 bool "Apple \"valkyrie\" display support"
497 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
503 This driver supports a frame buffer for the "valkyrie" graphics
504 adapter in some Power Macintoshes.
507 bool "Chips 65550 display support"
508 depends on (FB = y) && PPC32 && PCI
509 select FB_CFB_FILLRECT
510 select FB_CFB_COPYAREA
511 select FB_CFB_IMAGEBLIT
513 This is the frame buffer device driver for the Chips & Technologies
514 65550 graphics chip in PowerBooks.
517 bool "Asiliant (Chips) 69000 display support"
518 depends on (FB = y) && PCI
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
523 This is the frame buffer device driver for the Asiliant 69030 chipset
526 bool "IMS Twin Turbo display support"
527 depends on (FB = y) && PCI
528 select FB_CFB_IMAGEBLIT
529 select FB_MACMODES if PPC
531 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
532 many Macintosh and compatible computers.
535 tristate "VGA 16-color graphics support"
536 depends on FB && (X86 || PPC)
537 select FB_CFB_FILLRECT
538 select FB_CFB_COPYAREA
539 select FB_CFB_IMAGEBLIT
541 select FONT_8x16 if FRAMEBUFFER_CONSOLE
543 This is the frame buffer device driver for VGA 16 color graphic
544 cards. Say Y if you have such a card.
546 To compile this driver as a module, choose M here: the
547 module will be called vga16fb.
549 config FB_BF54X_LQ043
550 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
551 depends on FB && (BF54x) && !BF542
552 select FB_CFB_FILLRECT
553 select FB_CFB_COPYAREA
554 select FB_CFB_IMAGEBLIT
556 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
558 config FB_BFIN_T350MCQB
559 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
560 depends on FB && BLACKFIN
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
566 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
567 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
568 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
570 config FB_BFIN_LQ035Q1
571 tristate "SHARP LQ035Q1DH02 TFT LCD"
572 depends on FB && BLACKFIN && SPI
573 select FB_CFB_FILLRECT
574 select FB_CFB_COPYAREA
575 select FB_CFB_IMAGEBLIT
578 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
579 the Blackfin Landscape LCD EZ-Extender Card.
580 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
581 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
583 To compile this driver as a module, choose M here: the
584 module will be called bfin-lq035q1-fb.
586 config FB_BF537_LQ035
587 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
588 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
589 select FB_CFB_FILLRECT
590 select FB_CFB_COPYAREA
591 select FB_CFB_IMAGEBLIT
594 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
597 To compile this driver as a module, choose M here: the
598 module will be called bf537-lq035.
601 tristate "Blackfin ADV7393 Video encoder"
602 depends on FB && BLACKFIN
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the framebuffer device for a ADV7393 video encoder
609 attached to a Blackfin on the PPI port.
610 If your Blackfin board has a ADV7393 select Y.
612 To compile this driver as a module, choose M here: the
613 module will be called bfin_adv7393fb.
616 prompt "Video mode support"
617 depends on FB_BFIN_7393
627 bool 'NTSC 640x480 (Experimental)'
630 bool 'PAL 640x480 (Experimental)'
633 bool 'NTSC 720x480 YCbCR input'
636 bool 'PAL 720x576 YCbCR input'
641 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
642 depends on (FB_BFIN_7393)
643 default ADV7393_1XMEM
653 tristate "HP STI frame buffer device support"
654 depends on FB && PARISC
655 select FB_CFB_FILLRECT
656 select FB_CFB_COPYAREA
657 select FB_CFB_IMAGEBLIT
662 STI refers to the HP "Standard Text Interface" which is a set of
663 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
664 Enabling this option will implement the linux framebuffer device
665 using calls to the STI BIOS routines for initialisation.
667 If you enable this option, you will get a planar framebuffer device
668 /dev/fb which will work on the most common HP graphic cards of the
669 NGLE family, including the artist chips (in the 7xx and Bxxx series),
670 HCRX, HCRX24, CRX, CRX24 and VisEG series.
672 It is safe to enable this option, so you should probably say "Y".
675 bool "Generic Macintosh display support"
676 depends on (FB = y) && MAC
677 select FB_CFB_FILLRECT
678 select FB_CFB_COPYAREA
679 select FB_CFB_IMAGEBLIT
684 depends on (FB = y) && DIO
685 select FB_CFB_IMAGEBLIT
689 tristate "TGA/SFB+ framebuffer support"
690 depends on FB && (ALPHA || TC)
691 select FB_CFB_FILLRECT
692 select FB_CFB_COPYAREA
693 select FB_CFB_IMAGEBLIT
696 This is the frame buffer device driver for generic TGA and SFB+
697 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
698 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
699 TURBOchannel cards, also known as PMAGD-A, -B and -C.
701 Due to hardware limitations ZLX-E2 and E3 cards are not supported
702 for DECstation 5000/200 systems. Additionally due to firmware
703 limitations these cards may cause troubles with booting DECstation
704 5000/240 and /260 systems, but are fully supported under Linux if
705 you manage to get it going. ;-)
707 Say Y if you have one of those.
710 tristate "Userspace VESA VGA graphics support"
711 depends on FB && CONNECTOR
712 select FB_CFB_FILLRECT
713 select FB_CFB_COPYAREA
714 select FB_CFB_IMAGEBLIT
715 select FB_MODE_HELPERS
717 This is the frame buffer driver for generic VBE 2.0 compliant
718 graphic cards. It can also take advantage of VBE 3.0 features,
719 such as refresh rate adjustment.
721 This driver generally provides more features than vesafb but
722 requires a userspace helper application called 'v86d'. See
723 <file:Documentation/fb/uvesafb.txt> for more information.
728 bool "VESA VGA graphics support"
729 depends on (FB = y) && X86
730 select FB_CFB_FILLRECT
731 select FB_CFB_COPYAREA
732 select FB_CFB_IMAGEBLIT
733 select FB_BOOT_VESA_SUPPORT
735 This is the frame buffer device driver for generic VESA 2.0
736 compliant graphic cards. The older VESA 1.2 cards are not supported.
737 You will get a boot time penguin logo at no additional cost. Please
738 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
741 bool "EFI-based Framebuffer Support"
742 depends on (FB = y) && X86 && EFI
743 select FB_CFB_FILLRECT
744 select FB_CFB_COPYAREA
745 select FB_CFB_IMAGEBLIT
747 This is the EFI frame buffer device driver. If the firmware on
748 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
749 using the EFI framebuffer as your console.
752 tristate "N411 Apollo/Hecuba devkit support"
753 depends on FB && X86 && MMU
754 select FB_SYS_FILLRECT
755 select FB_SYS_COPYAREA
756 select FB_SYS_IMAGEBLIT
758 select FB_DEFERRED_IO
761 This enables support for the Apollo display controller in its
762 Hecuba form using the n411 devkit.
765 tristate "Hercules mono graphics support"
768 Say Y here if you have a Hercules mono graphics card.
770 To compile this driver as a module, choose M here: the
771 module will be called hgafb.
773 As this card technology is at least 25 years old,
774 most people will answer N here.
777 bool "SGI Graphics Backend frame buffer support"
778 depends on (FB = y) && SGI_IP32
779 select FB_CFB_FILLRECT
780 select FB_CFB_COPYAREA
781 select FB_CFB_IMAGEBLIT
783 This is the frame buffer device driver for SGI Graphics Backend.
784 This chip is used in SGI O2 and Visual Workstation 320/540.
787 int "Video memory size in MB"
791 This is the amount of memory reserved for the framebuffer,
792 which can be any value between 1MB and 8MB.
795 bool "SBUS and UPA framebuffers"
796 depends on (FB = y) && SPARC
798 Say Y if you want support for SBUS or UPA based frame buffer device.
802 depends on (FB = y) && (SPARC && FB_SBUS)
803 select FB_CFB_FILLRECT
804 select FB_CFB_COPYAREA
805 select FB_CFB_IMAGEBLIT
807 This is the frame buffer device driver for the BWtwo frame buffer.
810 bool "CGthree support"
811 depends on (FB = y) && (SPARC && FB_SBUS)
812 select FB_CFB_FILLRECT
813 select FB_CFB_COPYAREA
814 select FB_CFB_IMAGEBLIT
816 This is the frame buffer device driver for the CGthree frame buffer.
819 bool "CGsix (GX,TurboGX) support"
820 depends on (FB = y) && (SPARC && FB_SBUS)
821 select FB_CFB_COPYAREA
822 select FB_CFB_IMAGEBLIT
824 This is the frame buffer device driver for the CGsix (GX, TurboGX)
828 bool "Creator/Creator3D/Elite3D support"
829 depends on FB_SBUS && SPARC64
830 select FB_CFB_COPYAREA
831 select FB_CFB_IMAGEBLIT
833 This is the frame buffer device driver for the Creator, Creator3D,
834 and Elite3D graphics boards.
837 bool "TCX (SS4/SS5 only) support"
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for the TCX 24/8bit frame
847 bool "CGfourteen (SX) support"
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
853 This is the frame buffer device driver for the CGfourteen frame
854 buffer on Desktop SPARCsystems with the SX graphics option.
857 bool "P9100 (Sparcbook 3 only) support"
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 This is the frame buffer device driver for the P9100 card
864 supported on Sparcbook 3 machines.
867 bool "Leo (ZX) support"
869 select FB_CFB_FILLRECT
870 select FB_CFB_COPYAREA
871 select FB_CFB_IMAGEBLIT
873 This is the frame buffer device driver for the SBUS-based Sun ZX
874 (leo) frame buffer cards.
877 bool "IGA 168x display support"
878 depends on (FB = y) && SPARC32
879 select FB_CFB_FILLRECT
880 select FB_CFB_COPYAREA
881 select FB_CFB_IMAGEBLIT
883 This is the framebuffer device for the INTERGRAPHICS 1680 and
884 successor frame buffer cards.
887 bool "Sun XVR-500 3DLABS Wildcat support"
888 depends on (FB = y) && PCI && SPARC64
889 select FB_CFB_FILLRECT
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This is the framebuffer device for the Sun XVR-500 and similar
894 graphics cards based upon the 3DLABS Wildcat chipset. The driver
895 only works on sparc64 systems where the system firmware has
896 mostly initialized the card already. It is treated as a
897 completely dumb framebuffer device.
900 bool "Sun XVR-2500 3DLABS Wildcat support"
901 depends on (FB = y) && PCI && SPARC64
902 select FB_CFB_FILLRECT
903 select FB_CFB_COPYAREA
904 select FB_CFB_IMAGEBLIT
906 This is the framebuffer device for the Sun XVR-2500 and similar
907 graphics cards based upon the 3DLABS Wildcat chipset. The driver
908 only works on sparc64 systems where the system firmware has
909 mostly initialized the card already. It is treated as a
910 completely dumb framebuffer device.
913 bool "Sun XVR-1000 support"
914 depends on (FB = y) && 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-1000 and similar
920 graphics cards. The driver only works on sparc64 systems where
921 the system firmware has mostly initialized the card already. It
922 is treated as a completely dumb framebuffer device.
925 tristate "NEC PowerVR 2 display support"
926 depends on FB && SH_DREAMCAST
927 select FB_CFB_FILLRECT
928 select FB_CFB_COPYAREA
929 select FB_CFB_IMAGEBLIT
931 Say Y here if you have a PowerVR 2 card in your box. If you plan to
932 run linux on your Dreamcast, you will have to say Y here.
933 This driver may or may not work on other PowerVR 2 cards, but is
934 totally untested. Use at your own risk. If unsure, say N.
936 To compile this driver as a module, choose M here: the
937 module will be called pvr2fb.
939 You can pass several parameters to the driver at boot time or at
940 module load time. The parameters look like "video=pvr2:XXX", where
941 the meaning of XXX can be found at the end of the main source file
942 (<file:drivers/video/pvr2fb.c>). Please see the file
943 <file:Documentation/fb/pvr2fb.txt>.
946 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
947 depends on FB && HAS_DMA
948 select FB_CFB_FILLRECT
949 select FB_CFB_COPYAREA
950 select FB_CFB_IMAGEBLIT
952 This enables support for the OpenCores VGA/LCD core.
954 The OpenCores VGA/LCD core is typically used together with
955 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
956 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
958 The source code and specification for the core is available at
959 <http://opencores.org/project,vga_lcd>
962 tristate "Epson S1D13XXX framebuffer support"
964 select FB_CFB_FILLRECT
965 select FB_CFB_COPYAREA
966 select FB_CFB_IMAGEBLIT
968 Support for S1D13XXX framebuffer device family (currently only
969 working with S1D13806). Product specs at
970 <http://vdc.epson.com/>
973 tristate "AT91/AT32 LCD Controller support"
974 depends on FB && HAVE_FB_ATMEL
976 select FB_CFB_FILLRECT
977 select FB_CFB_COPYAREA
978 select FB_CFB_IMAGEBLIT
979 select FB_MODE_HELPERS
980 select VIDEOMODE_HELPERS
982 This enables support for the AT91/AT32 LCD Controller.
985 bool "Frame Buffer in internal SRAM"
986 depends on FB_ATMEL && ARCH_AT91SAM9261
988 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
989 to let frame buffer in external SDRAM.
992 bool "Use a STN display with AT91/AT32 LCD Controller"
993 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
996 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
997 Controller. Say N if you want to connect a TFT.
1002 tristate "nVidia Framebuffer Support"
1003 depends on FB && PCI
1004 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1005 select FB_MODE_HELPERS
1006 select FB_CFB_FILLRECT
1007 select FB_CFB_COPYAREA
1008 select FB_CFB_IMAGEBLIT
1012 This driver supports graphics boards with the nVidia chips, TNT
1013 and newer. For very old chipsets, such as the RIVA128, then use
1015 Say Y if you have such a graphics board.
1017 To compile this driver as a module, choose M here: the
1018 module will be called nvidiafb.
1020 config FB_NVIDIA_I2C
1021 bool "Enable DDC Support"
1022 depends on FB_NVIDIA
1025 This enables I2C support for nVidia Chipsets. This is used
1026 only for getting EDID information from the attached display
1027 allowing for robust video mode handling and switching.
1029 Because fbdev-2.6 requires that drivers must be able to
1030 independently validate video mode parameters, you should say Y
1033 config FB_NVIDIA_DEBUG
1034 bool "Lots of debug output"
1035 depends on FB_NVIDIA
1038 Say Y here if you want the nVidia driver to output all sorts
1039 of debugging information to provide to the maintainer when
1040 something goes wrong.
1042 config FB_NVIDIA_BACKLIGHT
1043 bool "Support for backlight control"
1044 depends on FB_NVIDIA
1047 Say Y here if you want to control the backlight of your display.
1050 tristate "nVidia Riva support"
1051 depends on FB && PCI
1052 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1053 select FB_MODE_HELPERS
1054 select FB_CFB_FILLRECT
1055 select FB_CFB_COPYAREA
1056 select FB_CFB_IMAGEBLIT
1060 This driver supports graphics boards with the nVidia Riva/Geforce
1062 Say Y if you have such a graphics board.
1064 To compile this driver as a module, choose M here: the
1065 module will be called rivafb.
1068 bool "Enable DDC Support"
1072 This enables I2C support for nVidia Chipsets. This is used
1073 only for getting EDID information from the attached display
1074 allowing for robust video mode handling and switching.
1076 Because fbdev-2.6 requires that drivers must be able to
1077 independently validate video mode parameters, you should say Y
1080 config FB_RIVA_DEBUG
1081 bool "Lots of debug output"
1085 Say Y here if you want the Riva driver to output all sorts
1086 of debugging information to provide to the maintainer when
1087 something goes wrong.
1089 config FB_RIVA_BACKLIGHT
1090 bool "Support for backlight control"
1094 Say Y here if you want to control the backlight of your display.
1097 tristate "Intel740 support"
1098 depends on FB && PCI
1099 select FB_MODE_HELPERS
1100 select FB_CFB_FILLRECT
1101 select FB_CFB_COPYAREA
1102 select FB_CFB_IMAGEBLIT
1106 This driver supports graphics cards based on Intel740 chip.
1109 tristate "Intel 810/815 support"
1110 depends on FB && PCI && X86_32 && AGP_INTEL
1111 select FB_MODE_HELPERS
1112 select FB_CFB_FILLRECT
1113 select FB_CFB_COPYAREA
1114 select FB_CFB_IMAGEBLIT
1117 This driver supports the on-board graphics built in to the Intel 810
1118 and 815 chipsets. Say Y if you have and plan to use such a board.
1120 To compile this driver as a module, choose M here: the
1121 module will be called i810fb.
1123 For more information, please read
1124 <file:Documentation/fb/intel810.txt>
1127 bool "use VESA Generalized Timing Formula"
1130 If you say Y, then the VESA standard, Generalized Timing Formula
1131 or GTF, will be used to calculate the required video timing values
1132 per video mode. Since the GTF allows nondiscrete timings
1133 (nondiscrete being a range of values as opposed to discrete being a
1134 set of values), you'll be able to use any combination of horizontal
1135 and vertical resolutions, and vertical refresh rates without having
1136 to specify your own timing parameters. This is especially useful
1137 to maximize the performance of an aging display, or if you just
1138 have a display with nonstandard dimensions. A VESA compliant
1139 monitor is recommended, but can still work with non-compliant ones.
1140 If you need or want this, then select this option. The timings may
1141 not be compliant with Intel's recommended values. Use at your own
1144 If you say N, the driver will revert to discrete video timings
1145 using a set recommended by Intel in their documentation.
1150 bool "Enable DDC Support"
1151 depends on FB_I810 && FB_I810_GTF
1156 tristate "Intel LE80578 (Vermilion) support"
1157 depends on FB && PCI && X86
1158 select FB_MODE_HELPERS
1159 select FB_CFB_FILLRECT
1160 select FB_CFB_COPYAREA
1161 select FB_CFB_IMAGEBLIT
1163 This driver supports the LE80578 (Vermilion Range) chipset
1165 config FB_CARILLO_RANCH
1166 tristate "Intel Carillo Ranch support"
1167 depends on FB_LE80578 && FB && PCI && X86
1169 This driver supports the LE80578 (Carillo Ranch) board
1172 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1173 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1174 select FB_MODE_HELPERS
1175 select FB_CFB_FILLRECT
1176 select FB_CFB_COPYAREA
1177 select FB_CFB_IMAGEBLIT
1178 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1179 depends on !DRM_I915
1181 This driver supports the on-board graphics built in to the Intel
1182 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1183 Say Y if you have and plan to use such a board.
1185 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1187 To compile this driver as a module, choose M here: the
1188 module will be called intelfb.
1190 For more information, please read <file:Documentation/fb/intelfb.txt>
1192 config FB_INTEL_DEBUG
1193 bool "Intel driver Debug Messages"
1196 Say Y here if you want the Intel driver to output all sorts
1197 of debugging information to provide to the maintainer when
1198 something goes wrong.
1201 bool "DDC/I2C for Intel framebuffer support"
1206 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1209 tristate "Matrox acceleration"
1210 depends on FB && PCI
1211 select FB_CFB_FILLRECT
1212 select FB_CFB_COPYAREA
1213 select FB_CFB_IMAGEBLIT
1214 select FB_TILEBLITTING
1215 select FB_MACMODES if PPC_PMAC
1217 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1218 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1219 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1220 Matrox G400, G450 or G550 card in your box.
1222 To compile this driver as a module, choose M here: the
1223 module will be called matroxfb.
1225 You can pass several parameters to the driver at boot time or at
1226 module load time. The parameters look like "video=matroxfb:XXX", and
1227 are described in <file:Documentation/fb/matroxfb.txt>.
1229 config FB_MATROX_MILLENIUM
1230 bool "Millennium I/II support"
1231 depends on FB_MATROX
1233 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1234 video card. If you select "Advanced lowlevel driver options" below,
1235 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1236 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1237 also use font widths different from 8.
1239 config FB_MATROX_MYSTIQUE
1240 bool "Mystique support"
1241 depends on FB_MATROX
1243 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1244 video card. If you select "Advanced lowlevel driver options" below,
1245 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1246 packed pixel and 32 bpp packed pixel. You can also use font widths
1250 bool "G100/G200/G400/G450/G550 support"
1251 depends on FB_MATROX
1253 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1254 video card. If you select "Advanced lowlevel driver options", you
1255 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1256 pixel and 32 bpp packed pixel. You can also use font widths
1259 If you need support for G400 secondary head, you must say Y to
1260 "Matrox I2C support" and "G400 second head support" right below.
1261 G450/G550 secondary head and digital output are supported without
1264 The driver starts in monitor mode. You must use the matroxset tool
1265 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1266 swap primary and secondary head outputs, or to change output mode.
1267 Secondary head driver always start in 640x480 resolution and you
1268 must use fbset to change it.
1270 Do not forget that second head supports only 16 and 32 bpp
1271 packed pixels, so it is a good idea to compile them into the kernel
1272 too. You can use only some font widths, as the driver uses generic
1273 painting procedures (the secondary head does not use acceleration
1276 G450/G550 hardware can display TV picture only from secondary CRTC,
1277 and it performs no scaling, so picture must have 525 or 625 lines.
1279 config FB_MATROX_I2C
1280 tristate "Matrox I2C support"
1281 depends on FB_MATROX
1284 This drivers creates I2C buses which are needed for accessing the
1285 DDC (I2C) bus present on all Matroxes, an I2C bus which
1286 interconnects Matrox optional devices, like MGA-TVO on G200 and
1287 G400, and the secondary head DDC bus, present on G400 only.
1289 You can say Y or M here if you want to experiment with monitor
1290 detection code. You must say Y or M here if you want to use either
1291 second head of G400 or MGA-TVO on G200 or G400.
1293 If you compile it as module, it will create a module named
1296 config FB_MATROX_MAVEN
1297 tristate "G400 second head support"
1298 depends on FB_MATROX_G && FB_MATROX_I2C
1300 WARNING !!! This support does not work with G450 !!!
1302 Say Y or M here if you want to use a secondary head (meaning two
1303 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1304 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1305 secondary head output is blanked while you are in X. With XFree
1306 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1307 the fbdev driver on first head and the fbdev driver on second head.
1309 If you compile it as module, two modules are created,
1310 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1311 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1312 also load i2c-matroxfb to get it to run.
1314 The driver starts in monitor mode and you must use the matroxset
1316 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1317 PAL or NTSC or to swap primary and secondary head outputs.
1318 Secondary head driver also always start in 640x480 resolution, you
1319 must use fbset to change it.
1321 Also do not forget that second head supports only 16 and 32 bpp
1322 packed pixels, so it is a good idea to compile them into the kernel
1323 too. You can use only some font widths, as the driver uses generic
1324 painting procedures (the secondary head does not use acceleration
1328 tristate "ATI Radeon display support"
1329 depends on FB && PCI
1330 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1331 select FB_MODE_HELPERS
1332 select FB_CFB_FILLRECT
1333 select FB_CFB_COPYAREA
1334 select FB_CFB_IMAGEBLIT
1335 select FB_MACMODES if PPC_OF
1337 Choose this option if you want to use an ATI Radeon graphics card as
1338 a framebuffer device. There are both PCI and AGP versions. You
1339 don't need to choose this to run the Radeon in plain VGA mode.
1341 There is a product page at
1342 http://products.amd.com/en-us/GraphicCardResult.aspx
1344 config FB_RADEON_I2C
1345 bool "DDC/I2C for ATI Radeon support"
1346 depends on FB_RADEON
1350 Say Y here if you want DDC/I2C support for your Radeon board.
1352 config FB_RADEON_BACKLIGHT
1353 bool "Support for backlight control"
1354 depends on FB_RADEON
1357 Say Y here if you want to control the backlight of your display.
1359 config FB_RADEON_DEBUG
1360 bool "Lots of debug output from Radeon driver"
1361 depends on FB_RADEON
1364 Say Y here if you want the Radeon driver to output all sorts
1365 of debugging information to provide to the maintainer when
1366 something goes wrong.
1369 tristate "ATI Rage128 display support"
1370 depends on FB && PCI
1371 select FB_CFB_FILLRECT
1372 select FB_CFB_COPYAREA
1373 select FB_CFB_IMAGEBLIT
1374 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1375 select FB_MACMODES if PPC_PMAC
1377 This driver supports graphics boards with the ATI Rage128 chips.
1378 Say Y if you have such a graphics board and read
1379 <file:Documentation/fb/aty128fb.txt>.
1381 To compile this driver as a module, choose M here: the
1382 module will be called aty128fb.
1384 config FB_ATY128_BACKLIGHT
1385 bool "Support for backlight control"
1386 depends on FB_ATY128
1389 Say Y here if you want to control the backlight of your display.
1392 tristate "ATI Mach64 display support" if PCI || ATARI
1393 depends on FB && !SPARC32
1394 select FB_CFB_FILLRECT
1395 select FB_CFB_COPYAREA
1396 select FB_CFB_IMAGEBLIT
1397 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1398 select FB_MACMODES if PPC
1400 This driver supports graphics boards with the ATI Mach64 chips.
1401 Say Y if you have such a graphics board.
1403 To compile this driver as a module, choose M here: the
1404 module will be called atyfb.
1407 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1408 depends on PCI && FB_ATY
1409 default y if SPARC64 && PCI
1411 Say Y here to support use of ATI's 64-bit Rage boards (or other
1412 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1413 framebuffer device. The ATI product support page for these boards
1414 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1416 config FB_ATY_GENERIC_LCD
1417 bool "Mach64 generic LCD support"
1418 depends on FB_ATY_CT
1420 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1421 Rage XC, or Rage XL chipset.
1424 bool "Mach64 GX support" if PCI
1428 Say Y here to support use of the ATI Mach64 Graphics Expression
1429 board (or other boards based on the Mach64 GX chipset) as a
1430 framebuffer device. The ATI product support page for these boards
1432 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1434 config FB_ATY_BACKLIGHT
1435 bool "Support for backlight control"
1439 Say Y here if you want to control the backlight of your display.
1442 tristate "S3 Trio/Virge support"
1443 depends on FB && PCI
1444 select FB_CFB_FILLRECT
1445 select FB_CFB_COPYAREA
1446 select FB_CFB_IMAGEBLIT
1447 select FB_TILEBLITTING
1450 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1452 Driver for graphics boards with S3 Trio / S3 Virge chip.
1455 bool "DDC for S3 support"
1460 Say Y here if you want DDC support for your S3 graphics card.
1463 tristate "S3 Savage support"
1464 depends on FB && PCI
1465 select FB_MODE_HELPERS
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1471 This driver supports notebooks and computers with S3 Savage PCI/AGP
1474 Say Y if you have such a graphics card.
1476 To compile this driver as a module, choose M here; the module
1477 will be called savagefb.
1479 config FB_SAVAGE_I2C
1480 bool "Enable DDC2 Support"
1481 depends on FB_SAVAGE
1484 This enables I2C support for S3 Savage Chipsets. This is used
1485 only for getting EDID information from the attached display
1486 allowing for robust video mode handling and switching.
1488 Because fbdev-2.6 requires that drivers must be able to
1489 independently validate video mode parameters, you should say Y
1492 config FB_SAVAGE_ACCEL
1493 bool "Enable Console Acceleration"
1494 depends on FB_SAVAGE
1497 This option will compile in console acceleration support. If
1498 the resulting framebuffer console has bothersome glitches, then
1502 tristate "SiS/XGI display support"
1503 depends on FB && PCI
1504 select FB_CFB_FILLRECT
1505 select FB_CFB_COPYAREA
1506 select FB_CFB_IMAGEBLIT
1507 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1509 This is the frame buffer device driver for the SiS 300, 315, 330
1510 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1511 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1513 To compile this driver as a module, choose M here; the module
1514 will be called sisfb.
1517 bool "SiS 300 series support"
1520 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1523 bool "SiS 315/330/340 series and XGI support"
1526 Say Y here to support use of the SiS 315, 330 and 340 series
1527 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1528 as XGI V3XT, V5, V8 and Z7.
1531 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1532 depends on FB && PCI && X86
1533 select FB_CFB_FILLRECT
1534 select FB_CFB_COPYAREA
1535 select FB_CFB_IMAGEBLIT
1540 This is the frame buffer device driver for Graphics chips of VIA
1541 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1542 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1544 Say Y if you have a VIA UniChrome graphics board.
1546 To compile this driver as a module, choose M here: the
1547 module will be called viafb.
1551 config FB_VIA_DIRECT_PROCFS
1552 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1556 Allow direct hardware access to some output registers via procfs.
1557 This is dangerous but may provide the only chance to get the
1558 correct output device configuration.
1559 Its use is strongly discouraged.
1561 config FB_VIA_X_COMPATIBILITY
1562 bool "X server compatibility"
1566 This option reduces the functionality (power saving, ...) of the
1567 framebuffer to avoid negative impact on the OpenChrome X server.
1568 If you use any X server other than fbdev you should enable this
1569 otherwise it should be safe to disable it and allow using all
1575 tristate "NeoMagic display support"
1576 depends on FB && PCI
1577 select FB_MODE_HELPERS
1578 select FB_CFB_FILLRECT
1579 select FB_CFB_COPYAREA
1580 select FB_CFB_IMAGEBLIT
1583 This driver supports notebooks with NeoMagic PCI chips.
1584 Say Y if you have such a graphics card.
1586 To compile this driver as a module, choose M here: the
1587 module will be called neofb.
1590 tristate "IMG Kyro support"
1591 depends on FB && PCI
1592 select FB_CFB_FILLRECT
1593 select FB_CFB_COPYAREA
1594 select FB_CFB_IMAGEBLIT
1596 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1599 To compile this driver as a module, choose M here: the
1600 module will be called kyrofb.
1603 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1604 depends on FB && PCI
1605 select FB_CFB_IMAGEBLIT
1606 select FB_CFB_FILLRECT
1607 select FB_CFB_COPYAREA
1608 select FB_MODE_HELPERS
1610 This driver supports graphics boards with the 3Dfx Banshee,
1611 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1612 such a graphics board.
1614 To compile this driver as a module, choose M here: the
1615 module will be called tdfxfb.
1617 config FB_3DFX_ACCEL
1618 bool "3Dfx Acceleration functions"
1621 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1622 device driver with acceleration functions.
1625 bool "Enable DDC/I2C support"
1630 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1633 tristate "3Dfx Voodoo Graphics (sst1) support"
1634 depends on FB && PCI
1635 select FB_CFB_FILLRECT
1636 select FB_CFB_COPYAREA
1637 select FB_CFB_IMAGEBLIT
1639 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1640 Voodoo2 (cvg) based graphics card.
1642 To compile this driver as a module, choose M here: the
1643 module will be called sstfb.
1645 WARNING: Do not use any application that uses the 3D engine
1646 (namely glide) while using this driver.
1647 Please read the <file:Documentation/fb/sstfb.txt> for supported
1648 options and other important info support.
1651 tristate "VIA VT8623 support"
1652 depends on FB && PCI
1653 select FB_CFB_FILLRECT
1654 select FB_CFB_COPYAREA
1655 select FB_CFB_IMAGEBLIT
1656 select FB_TILEBLITTING
1659 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1661 Driver for CastleRock integrated graphics core in the
1662 VIA VT8623 [Apollo CLE266] chipset.
1665 tristate "Trident/CyberXXX/CyberBlade support"
1666 depends on FB && PCI
1667 select FB_CFB_FILLRECT
1668 select FB_CFB_COPYAREA
1669 select FB_CFB_IMAGEBLIT
1671 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1672 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1674 There are also integrated versions of these chips called CyberXXXX,
1675 CyberImage or CyberBlade. These chips are mostly found in laptops
1676 but also on some motherboards including early VIA EPIA motherboards.
1677 For more information, read <file:Documentation/fb/tridentfb.txt>
1679 Say Y if you have such a graphics board.
1681 To compile this driver as a module, choose M here: the
1682 module will be called tridentfb.
1685 tristate "ARK 2000PV support"
1686 depends on FB && PCI
1687 select FB_CFB_FILLRECT
1688 select FB_CFB_COPYAREA
1689 select FB_CFB_IMAGEBLIT
1690 select FB_TILEBLITTING
1693 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1695 Driver for PCI graphics boards with ARK 2000PV chip
1696 and ICS 5342 RAMDAC.
1699 tristate "Permedia3 support"
1700 depends on FB && PCI
1701 select FB_CFB_FILLRECT
1702 select FB_CFB_COPYAREA
1703 select FB_CFB_IMAGEBLIT
1705 This is the frame buffer device driver for the 3DLabs Permedia3
1706 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1707 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1708 and maybe other boards.
1711 tristate "Fujitsu carmine frame buffer support"
1712 depends on FB && PCI
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 This is the frame buffer device driver for the Fujitsu Carmine chip.
1718 The driver provides two independent frame buffer devices.
1721 depends on FB_CARMINE
1722 prompt "DRAM timing"
1723 default FB_CARMINE_DRAM_EVAL
1725 config FB_CARMINE_DRAM_EVAL
1726 bool "Eval board timings"
1728 Use timings which work on the eval card.
1730 config CARMINE_DRAM_CUSTOM
1731 bool "Custom board timings"
1733 Use custom board timings.
1737 bool "Au1100 LCD Driver"
1738 depends on (FB = y) && MIPS_ALCHEMY
1739 select FB_CFB_FILLRECT
1740 select FB_CFB_COPYAREA
1741 select FB_CFB_IMAGEBLIT
1743 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1744 various panels and CRTs by passing in kernel cmd line option
1745 au1100fb:panel=<name>.
1748 bool "Au1200/Au1300 LCD Driver"
1749 depends on (FB = y) && MIPS_ALCHEMY
1750 select FB_SYS_FILLRECT
1751 select FB_SYS_COPYAREA
1752 select FB_SYS_IMAGEBLIT
1755 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1756 It can drive various panels and CRTs by passing in kernel cmd line
1757 option au1200fb:panel=<name>.
1760 bool "VIA VT8500 framebuffer support"
1761 depends on (FB = y) && ARM && ARCH_VT8500
1762 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1763 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1764 select FB_SYS_IMAGEBLIT
1765 select FB_MODE_HELPERS
1766 select VIDEOMODE_HELPERS
1768 This is the framebuffer driver for VIA VT8500 integrated LCD
1772 bool "Wondermedia WM8xxx-series frame buffer support"
1773 depends on (FB = y) && ARM && ARCH_VT8500
1774 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1775 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1776 select FB_SYS_IMAGEBLIT
1777 select FB_MODE_HELPERS
1778 select VIDEOMODE_HELPERS
1780 This is the framebuffer driver for WonderMedia WM8xxx-series
1781 integrated LCD controller. This driver covers the WM8505, WM8650
1784 config FB_WMT_GE_ROPS
1785 bool "VT8500/WM8xxx accelerated raster ops support"
1786 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1789 This adds support for accelerated raster operations on the
1790 VIA VT8500 and Wondermedia 85xx series SoCs.
1792 source "drivers/video/fbdev/geode/Kconfig"
1795 tristate "HD64461 Frame Buffer support"
1796 depends on FB && HD64461
1797 select FB_CFB_FILLRECT
1798 select FB_CFB_COPYAREA
1799 select FB_CFB_IMAGEBLIT
1801 This is the frame buffer device driver for the Hitachi HD64461 LCD
1805 bool "PMAG-AA TURBOchannel framebuffer support"
1806 depends on (FB = y) && TC
1807 select FB_CFB_FILLRECT
1808 select FB_CFB_COPYAREA
1809 select FB_CFB_IMAGEBLIT
1811 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1812 used mainly in the MIPS-based DECstation series.
1815 tristate "PMAG-BA TURBOchannel framebuffer support"
1817 select FB_CFB_FILLRECT
1818 select FB_CFB_COPYAREA
1819 select FB_CFB_IMAGEBLIT
1821 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1822 used mainly in the MIPS-based DECstation series.
1825 tristate "PMAGB-B TURBOchannel framebuffer support"
1827 select FB_CFB_FILLRECT
1828 select FB_CFB_COPYAREA
1829 select FB_CFB_IMAGEBLIT
1831 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1832 in the MIPS-based DECstation series. The card is currently only
1833 supported in 1280x1024x8 mode.
1836 bool "Maxine (Personal DECstation) onboard framebuffer support"
1837 depends on (FB = y) && MACH_DECSTATION
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 Support for the onboard framebuffer (1024x768x8) in the Personal
1843 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1847 bool "G364 frame buffer support"
1848 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1849 select FB_CFB_FILLRECT
1850 select FB_CFB_COPYAREA
1851 select FB_CFB_IMAGEBLIT
1853 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1854 Olivetti M700-10 systems.
1857 bool "Motorola 68328 native frame buffer support"
1858 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1859 select FB_CFB_FILLRECT
1860 select FB_CFB_COPYAREA
1861 select FB_CFB_IMAGEBLIT
1863 Say Y here if you want to support the built-in frame buffer of
1864 the Motorola 68328 CPU family.
1867 tristate "PXA168/910 LCD framebuffer support"
1868 depends on FB && (CPU_PXA168 || CPU_PXA910)
1869 select FB_CFB_FILLRECT
1870 select FB_CFB_COPYAREA
1871 select FB_CFB_IMAGEBLIT
1873 Frame buffer driver for the built-in LCD controller in the Marvell
1877 tristate "PXA LCD framebuffer support"
1878 depends on FB && ARCH_PXA
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 Intel
1886 This driver is also available as a module ( = code which can be
1887 inserted and removed from the running kernel whenever you want). The
1888 module will be called pxafb. If you want to compile it as a module,
1889 say M here and read <file:Documentation/kbuild/modules.txt>.
1893 config FB_PXA_OVERLAY
1894 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1896 depends on FB_PXA && (PXA27x || PXA3xx)
1898 config FB_PXA_SMARTPANEL
1899 bool "PXA Smartpanel LCD support"
1903 config FB_PXA_PARAMETERS
1904 bool "PXA LCD command line parameters"
1908 Enable the use of kernel command line or module parameters
1909 to configure the physical properties of the LCD panel when
1910 using the PXA LCD driver.
1912 This option allows you to override the panel parameters
1913 supplied by the platform in order to support multiple
1914 different models of flatpanel. If you will only be using a
1915 single model of flatpanel then you can safely leave this
1918 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1921 tristate "PXA3xx 2D graphics accelerator driver"
1924 Kernelspace driver for the 2D graphics controller unit (GCU)
1925 found on PXA3xx processors. There is a counterpart driver in the
1926 DirectFB suite, see http://www.directfb.org/
1928 If you compile this as a module, it will be called pxa3xx_gcu.
1931 tristate "2700G LCD framebuffer support"
1932 depends on FB && ARCH_PXA
1933 select FB_CFB_FILLRECT
1934 select FB_CFB_COPYAREA
1935 select FB_CFB_IMAGEBLIT
1937 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1941 bool "Enable debugging info via debugfs"
1942 depends on FB_MBX && DEBUG_FS
1945 Enable this if you want debugging information using the debug
1946 filesystem (debugfs)
1951 tristate "Freescale DIU framebuffer support"
1952 depends on FB && FSL_SOC
1953 select FB_MODE_HELPERS
1954 select FB_CFB_FILLRECT
1955 select FB_CFB_COPYAREA
1956 select FB_CFB_IMAGEBLIT
1957 select PPC_LIB_RHEAP
1959 Framebuffer driver for the Freescale SoC DIU
1962 tristate "W100 frame buffer support"
1963 depends on FB && ARCH_PXA
1964 select FB_CFB_FILLRECT
1965 select FB_CFB_COPYAREA
1966 select FB_CFB_IMAGEBLIT
1968 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1969 It can also drive the w3220 chip found on iPAQ hx4700.
1971 This driver is also available as a module ( = code which can be
1972 inserted and removed from the running kernel whenever you want). The
1973 module will be called w100fb. If you want to compile it as a module,
1974 say M here and read <file:Documentation/kbuild/modules.txt>.
1978 config FB_SH_MOBILE_LCDC
1979 tristate "SuperH Mobile LCDC framebuffer support"
1980 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1981 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1982 select FB_SYS_FILLRECT
1983 select FB_SYS_COPYAREA
1984 select FB_SYS_IMAGEBLIT
1986 select FB_DEFERRED_IO
1988 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1990 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1992 config FB_SH_MOBILE_HDMI
1993 tristate "SuperH Mobile HDMI controller support"
1994 depends on FB_SH_MOBILE_LCDC
1995 select FB_MODE_HELPERS
2000 Driver for the on-chip SH-Mobile HDMI controller.
2003 tristate "Toshiba Mobile IO FrameBuffer support"
2004 depends on FB && (MFD_TMIO || COMPILE_TEST)
2005 select FB_CFB_FILLRECT
2006 select FB_CFB_COPYAREA
2007 select FB_CFB_IMAGEBLIT
2009 Frame buffer driver for the Toshiba Mobile IO integrated as found
2010 on the Sharp SL-6000 series
2012 This driver is also available as a module ( = code which can be
2013 inserted and removed from the running kernel whenever you want). The
2014 module will be called tmiofb. If you want to compile it as a module,
2015 say M here and read <file:Documentation/kbuild/modules.txt>.
2019 config FB_TMIO_ACCELL
2020 bool "tmiofb acceleration"
2025 tristate "Samsung S3C framebuffer support"
2026 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2027 ARCH_S5PV210 || ARCH_EXYNOS)
2028 select FB_CFB_FILLRECT
2029 select FB_CFB_COPYAREA
2030 select FB_CFB_IMAGEBLIT
2032 Frame buffer driver for the built-in FB controller in the Samsung
2033 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2034 and the S3C64XX series such as the S3C6400 and S3C6410.
2036 These chips all have the same basic framebuffer design with the
2037 actual capabilities depending on the chip. For instance the S3C6400
2038 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2039 currently only have two.
2041 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2043 config FB_S3C_DEBUG_REGWRITE
2044 bool "Debug register writes"
2047 Show all register writes via pr_debug()
2050 tristate "S3C2410 LCD framebuffer support"
2051 depends on FB && ARCH_S3C24XX
2052 select FB_CFB_FILLRECT
2053 select FB_CFB_COPYAREA
2054 select FB_CFB_IMAGEBLIT
2056 Frame buffer driver for the built-in LCD controller in the Samsung
2059 This driver is also available as a module ( = code which can be
2060 inserted and removed from the running kernel whenever you want). The
2061 module will be called s3c2410fb. If you want to compile it as a module,
2062 say M here and read <file:Documentation/kbuild/modules.txt>.
2065 config FB_S3C2410_DEBUG
2066 bool "S3C2410 lcd debug messages"
2067 depends on FB_S3C2410
2069 Turn on debugging messages. Note that you can set/unset at run time
2073 tristate "NUC900 LCD framebuffer support"
2074 depends on FB && ARCH_W90X900
2075 select FB_CFB_FILLRECT
2076 select FB_CFB_COPYAREA
2077 select FB_CFB_IMAGEBLIT
2079 Frame buffer driver for the built-in LCD controller in the Nuvoton
2082 config GPM1040A0_320X240
2083 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2084 depends on FB_NUC900
2087 tristate "Silicon Motion SM501 framebuffer support"
2088 depends on FB && MFD_SM501
2089 select FB_CFB_FILLRECT
2090 select FB_CFB_COPYAREA
2091 select FB_CFB_IMAGEBLIT
2093 Frame buffer driver for the CRT and LCD controllers in the Silicon
2096 This driver is also available as a module ( = code which can be
2097 inserted and removed from the running kernel whenever you want). The
2098 module will be called sm501fb. If you want to compile it as a module,
2099 say M here and read <file:Documentation/kbuild/modules.txt>.
2104 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2105 depends on FB && USB
2106 select FB_MODE_HELPERS
2107 select FB_SYS_FILLRECT
2108 select FB_SYS_COPYAREA
2109 select FB_SYS_IMAGEBLIT
2111 select FB_DEFERRED_IO
2113 This is a kernel framebuffer driver for SMSC UFX USB devices.
2114 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2115 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2117 To compile as a module, choose M here: the module name is smscufx.
2120 tristate "Displaylink USB Framebuffer support"
2121 depends on FB && USB
2122 select FB_MODE_HELPERS
2123 select FB_SYS_FILLRECT
2124 select FB_SYS_COPYAREA
2125 select FB_SYS_IMAGEBLIT
2127 select FB_DEFERRED_IO
2129 This is a kernel framebuffer driver for DisplayLink USB devices.
2130 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2131 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2132 To compile as a module, choose M here: the module name is udlfb.
2134 config FB_IBM_GXT4500
2135 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2136 depends on FB && PPC
2137 select FB_CFB_FILLRECT
2138 select FB_CFB_COPYAREA
2139 select FB_CFB_IMAGEBLIT
2141 Say Y here to enable support for the IBM GXT4000P/6000P and
2142 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2143 found on some IBM System P (pSeries) machines. This driver
2144 doesn't use Geometry Engine GT1000.
2147 tristate "PS3 GPU framebuffer driver"
2148 depends on FB && PS3_PS3AV
2149 select FB_SYS_FILLRECT
2150 select FB_SYS_COPYAREA
2151 select FB_SYS_IMAGEBLIT
2153 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2155 Include support for the virtual frame buffer in the PS3 platform.
2157 config FB_PS3_DEFAULT_SIZE_M
2158 int "PS3 default frame buffer size (in MiB)"
2162 This is the default size (in MiB) of the virtual frame buffer in
2164 The default value can be overridden on the kernel command line
2165 using the "ps3fb" option (e.g. "ps3fb=9M");
2168 tristate "Xilinx frame buffer support"
2169 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2170 select FB_CFB_FILLRECT
2171 select FB_CFB_COPYAREA
2172 select FB_CFB_IMAGEBLIT
2174 Include support for the Xilinx ML300/ML403 reference design
2175 framebuffer. ML300 carries a 640*480 LCD display on the board,
2176 ML403 uses a standard DB15 VGA connector.
2179 tristate "Goldfish Framebuffer"
2180 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2181 select FB_CFB_FILLRECT
2182 select FB_CFB_COPYAREA
2183 select FB_CFB_IMAGEBLIT
2185 Framebuffer driver for Goldfish Virtual Platform
2188 tristate "Cobalt server LCD frame buffer support"
2189 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2192 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2193 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2194 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2195 select FB_CFB_FILLRECT
2196 select FB_CFB_COPYAREA
2197 select FB_CFB_IMAGEBLIT
2199 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2200 (D)STN/TFT LCD Controller.
2201 Supports display resolutions up to 1024x1024 pixel, grayscale and
2202 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2203 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2204 panels <= 320 pixel horizontal resolution.
2207 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2208 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2209 select FB_CFB_FILLRECT
2210 select FB_CFB_COPYAREA
2211 select FB_CFB_IMAGEBLIT
2212 select FB_CFB_REV_PIXELS_IN_BYTE
2213 select FB_MODE_HELPERS
2214 select VIDEOMODE_HELPERS
2216 This is the frame buffer device driver for the TI LCD controller
2217 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2221 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2223 select FB_SYS_FILLRECT
2224 select FB_SYS_COPYAREA
2225 select FB_SYS_IMAGEBLIT
2228 This is a `virtual' frame buffer device. It operates on a chunk of
2229 unswappable kernel memory instead of on the memory of a graphics
2230 board. This means you cannot see any output sent to this frame
2231 buffer device, while it does consume precious memory. The main use
2232 of this frame buffer device is testing and debugging the frame
2233 buffer subsystem. Do NOT enable it for normal systems! To protect
2234 the innocent, it has to be enabled explicitly at boot time using the
2235 kernel option `video=vfb:'.
2237 To compile this driver as a module, choose M here: the
2238 module will be called vfb. In order to load it, you must use
2239 the vfb_enable=1 option.
2243 config XEN_FBDEV_FRONTEND
2244 tristate "Xen virtual frame buffer support"
2245 depends on FB && XEN
2246 select FB_SYS_FILLRECT
2247 select FB_SYS_COPYAREA
2248 select FB_SYS_IMAGEBLIT
2250 select FB_DEFERRED_IO
2251 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
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 "MSM Framebuffer support"
2333 depends on FB && ARCH_MSM
2334 select FB_CFB_FILLRECT
2335 select FB_CFB_COPYAREA
2336 select FB_CFB_IMAGEBLIT
2339 tristate "MX3 Framebuffer support"
2340 depends on FB && MX3_IPU
2341 select FB_CFB_FILLRECT
2342 select FB_CFB_COPYAREA
2343 select FB_CFB_IMAGEBLIT
2344 select BACKLIGHT_CLASS_DEVICE
2347 This is a framebuffer device for the i.MX31 LCD Controller. So
2348 far only synchronous displays are supported. If you plan to use
2349 an LCD display with your i.MX31 system, say Y here.
2351 config FB_BROADSHEET
2352 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2354 select FB_SYS_FILLRECT
2355 select FB_SYS_COPYAREA
2356 select FB_SYS_IMAGEBLIT
2358 select FB_DEFERRED_IO
2360 This driver implements support for the E-Ink Broadsheet
2361 controller. The release name for this device was Epson S1D13521
2362 and could also have been called by other names when coupled with
2366 tristate "AUO-K190X EPD controller support"
2368 select FB_SYS_FILLRECT
2369 select FB_SYS_COPYAREA
2370 select FB_SYS_IMAGEBLIT
2372 select FB_DEFERRED_IO
2374 Provides support for epaper controllers from the K190X series
2375 of AUO. These controllers can be used to drive epaper displays
2378 This option enables the common support, shared by the individual
2379 controller drivers. You will also have to enable the driver
2380 for the controller type used in your device.
2383 tristate "AUO-K1900 EPD controller support"
2384 depends on FB && FB_AUO_K190X
2386 This driver implements support for the AUO K1900 epd-controller.
2387 This controller can drive Sipix epaper displays but can only do
2388 serial updates, reducing the number of possible frames per second.
2391 tristate "AUO-K1901 EPD controller support"
2392 depends on FB && FB_AUO_K190X
2394 This driver implements support for the AUO K1901 epd-controller.
2395 This controller can drive Sipix epaper displays and supports
2396 concurrent updates, making higher frames per second possible.
2399 tristate "JZ4740 LCD framebuffer support"
2400 depends on FB && MACH_JZ4740
2401 select FB_SYS_FILLRECT
2402 select FB_SYS_COPYAREA
2403 select FB_SYS_IMAGEBLIT
2405 Framebuffer support for the JZ4740 SoC.
2408 tristate "MXS LCD framebuffer support"
2409 depends on FB && ARCH_MXS
2410 select FB_CFB_FILLRECT
2411 select FB_CFB_COPYAREA
2412 select FB_CFB_IMAGEBLIT
2413 select FB_MODE_HELPERS
2414 select VIDEOMODE_HELPERS
2416 Framebuffer support for the MXS SoC.
2418 config FB_PUV3_UNIGFX
2419 tristate "PKUnity v3 Unigfx framebuffer support"
2420 depends on FB && UNICORE32 && ARCH_PUV3
2421 select FB_SYS_FILLRECT
2422 select FB_SYS_COPYAREA
2423 select FB_SYS_IMAGEBLIT
2426 Choose this option if you want to use the Unigfx device as a
2427 framebuffer device. Without the support of PCI & AGP.
2430 tristate "Microsoft Hyper-V Synthetic Video support"
2431 depends on FB && HYPERV
2432 select FB_CFB_FILLRECT
2433 select FB_CFB_COPYAREA
2434 select FB_CFB_IMAGEBLIT
2436 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2439 bool "Simple framebuffer support"
2441 select FB_CFB_FILLRECT
2442 select FB_CFB_COPYAREA
2443 select FB_CFB_IMAGEBLIT
2445 Say Y if you want support for a simple frame-buffer.
2447 This driver assumes that the display hardware has been initialized
2448 before the kernel boots, and the kernel will simply render to the
2449 pre-allocated frame buffer surface.
2451 Configuration re: surface address, size, and format must be provided
2452 through device tree, or plain old platform data.
2454 source "drivers/video/fbdev/omap/Kconfig"
2455 source "drivers/video/fbdev/omap2/Kconfig"
2456 source "drivers/video/fbdev/exynos/Kconfig"
2457 source "drivers/video/fbdev/mmp/Kconfig"
2459 config FB_SH_MOBILE_MERAM
2460 tristate "SuperH Mobile MERAM read ahead support"
2461 depends on (SUPERH || ARCH_SHMOBILE)
2462 select GENERIC_ALLOCATOR
2464 Enable MERAM support for the SuperH controller.
2466 This will allow for caching of the framebuffer to provide more
2467 reliable access under heavy main memory bus traffic situations.
2468 Up to 4 memory channels can be configured, allowing 4 RGB or
2469 2 YCbCr framebuffers to be configured.
2472 tristate "Solomon SSD1307 framebuffer support"
2473 depends on FB && I2C
2477 select FB_SYS_FILLRECT
2478 select FB_SYS_COPYAREA
2479 select FB_SYS_IMAGEBLIT
2480 select FB_DEFERRED_IO
2483 This driver implements support for the Solomon SSD1307
2484 OLED controller over I2C.