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 depends on FB_ARMCLCD
296 depends on (PLAT_VERSATILE || ARCH_INTEGRATOR)
301 bool "Acorn VIDC support"
302 depends on (FB = y) && ARM && ARCH_ACORN
303 select FB_CFB_FILLRECT
304 select FB_CFB_COPYAREA
305 select FB_CFB_IMAGEBLIT
307 This is the frame buffer device driver for the Acorn VIDC graphics
308 hardware found in Acorn RISC PCs and other ARM-based machines. If
312 bool "CLPS711X LCD support"
313 depends on (FB = y) && ARM && ARCH_CLPS711X
314 select FB_CFB_FILLRECT
315 select FB_CFB_COPYAREA
316 select FB_CFB_IMAGEBLIT
318 Say Y to enable the Framebuffer driver for the CLPS7111 and
322 bool "SA-1100 LCD support"
323 depends on (FB = y) && ARM && ARCH_SA1100
324 select FB_CFB_FILLRECT
325 select FB_CFB_COPYAREA
326 select FB_CFB_IMAGEBLIT
328 This is a framebuffer device for the SA-1100 LCD Controller.
329 See <http://www.linux-fbdev.org/> for information on framebuffer
332 If you plan to use the LCD display with your SA-1100 system, say
336 tristate "Freescale i.MX1/21/25/27 LCD support"
337 depends on FB && ARCH_MXC
338 select BACKLIGHT_LCD_SUPPORT
339 select LCD_CLASS_DEVICE
340 select FB_CFB_FILLRECT
341 select FB_CFB_COPYAREA
342 select FB_CFB_IMAGEBLIT
343 select FB_MODE_HELPERS
344 select VIDEOMODE_HELPERS
347 tristate "CyberPro 2000/2010/5000 support"
348 depends on FB && PCI && (BROKEN || !SPARC64)
349 select FB_CFB_FILLRECT
350 select FB_CFB_COPYAREA
351 select FB_CFB_IMAGEBLIT
353 This enables support for the Integraphics CyberPro 20x0 and 5000
354 VGA chips used in the Rebel.com Netwinder and other machines.
355 Say Y if you have a NetWinder or a graphics card containing this
356 device, otherwise say N.
358 config FB_CYBER2000_DDC
359 bool "DDC for CyberPro support"
360 depends on FB_CYBER2000
364 Say Y here if you want DDC support for your CyberPro graphics
365 card. This is only I2C bus support, driver does not use EDID.
367 config FB_CYBER2000_I2C
368 bool "CyberPro 2000/2010/5000 I2C support"
369 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
370 depends on I2C=y || FB_CYBER2000=m
373 Enable support for the I2C video decoder interface on the
374 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
375 on the Netwinder machines for the SAA7111 video capture.
379 depends on (FB = y) && APOLLO
381 select FB_CFB_FILLRECT
382 select FB_CFB_IMAGEBLIT
386 depends on (FB = y) && Q40
388 select FB_CFB_FILLRECT
389 select FB_CFB_COPYAREA
390 select FB_CFB_IMAGEBLIT
393 tristate "Amiga native chipset support"
394 depends on FB && AMIGA
396 This is the frame buffer device driver for the builtin graphics
397 chipset found in Amigas.
399 To compile this driver as a module, choose M here: the
400 module will be called amifb.
403 bool "Amiga OCS chipset support"
406 This enables support for the original Agnus and Denise video chips,
407 found in the Amiga 1000 and most A500's and A2000's. If you intend
408 to run Linux on any of these systems, say Y; otherwise say N.
411 bool "Amiga ECS chipset support"
414 This enables support for the Enhanced Chip Set, found in later
415 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
416 you intend to run Linux on any of these systems, say Y; otherwise
420 bool "Amiga AGA chipset support"
423 This enables support for the Advanced Graphics Architecture (also
424 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
425 and CD32. If you intend to run Linux on any of these systems, say Y;
429 bool "Amiga FrameMaster II/Rainbow II support"
430 depends on (FB = y) && ZORRO
431 select FB_CFB_FILLRECT
432 select FB_CFB_COPYAREA
433 select FB_CFB_IMAGEBLIT
435 This is the frame buffer device driver for the Amiga FrameMaster
436 card from BSC (exhibited 1992 but not shipped as a CBM product).
439 tristate "Arc Monochrome LCD board support"
441 select FB_SYS_FILLRECT
442 select FB_SYS_COPYAREA
443 select FB_SYS_IMAGEBLIT
446 This enables support for the Arc Monochrome LCD board. The board
447 is based on the KS-108 lcd controller and is typically a matrix
448 of 2*n chips. This driver was tested with a 128x64 panel. This
449 driver supports it for use with x86 SBCs through a 16 bit GPIO
450 interface (8 bit data, 8 bit control). If you anticipate using
451 this driver, say Y or M; otherwise say N. You must specify the
452 GPIO IO address to be used for setting control and data.
455 bool "Atari native chipset support"
456 depends on (FB = y) && ATARI
457 select FB_CFB_FILLRECT
458 select FB_CFB_COPYAREA
459 select FB_CFB_IMAGEBLIT
461 This is the frame buffer device driver for the builtin graphics
462 chipset found in Ataris.
465 bool "Open Firmware frame buffer device support"
466 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
467 select FB_CFB_FILLRECT
468 select FB_CFB_COPYAREA
469 select FB_CFB_IMAGEBLIT
472 Say Y if you want support with Open Firmware for your graphics
476 bool "Apple \"control\" display support"
477 depends on (FB = y) && PPC_PMAC && PPC32
478 select FB_CFB_FILLRECT
479 select FB_CFB_COPYAREA
480 select FB_CFB_IMAGEBLIT
483 This driver supports a frame buffer for the graphics adapter in the
484 Power Macintosh 7300 and others.
487 bool "Apple \"platinum\" display support"
488 depends on (FB = y) && PPC_PMAC && PPC32
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
494 This driver supports a frame buffer for the "platinum" graphics
495 adapter in some Power Macintoshes.
498 bool "Apple \"valkyrie\" display support"
499 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
500 select FB_CFB_FILLRECT
501 select FB_CFB_COPYAREA
502 select FB_CFB_IMAGEBLIT
505 This driver supports a frame buffer for the "valkyrie" graphics
506 adapter in some Power Macintoshes.
509 bool "Chips 65550 display support"
510 depends on (FB = y) && PPC32 && PCI
511 select FB_CFB_FILLRECT
512 select FB_CFB_COPYAREA
513 select FB_CFB_IMAGEBLIT
515 This is the frame buffer device driver for the Chips & Technologies
516 65550 graphics chip in PowerBooks.
519 bool "Asiliant (Chips) 69000 display support"
520 depends on (FB = y) && PCI
521 select FB_CFB_FILLRECT
522 select FB_CFB_COPYAREA
523 select FB_CFB_IMAGEBLIT
525 This is the frame buffer device driver for the Asiliant 69030 chipset
528 bool "IMS Twin Turbo display support"
529 depends on (FB = y) && PCI
530 select FB_CFB_IMAGEBLIT
531 select FB_MACMODES if PPC
533 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
534 many Macintosh and compatible computers.
537 tristate "VGA 16-color graphics support"
538 depends on FB && (X86 || PPC)
539 select FB_CFB_FILLRECT
540 select FB_CFB_COPYAREA
541 select FB_CFB_IMAGEBLIT
543 select FONT_8x16 if FRAMEBUFFER_CONSOLE
545 This is the frame buffer device driver for VGA 16 color graphic
546 cards. Say Y if you have such a card.
548 To compile this driver as a module, choose M here: the
549 module will be called vga16fb.
551 config FB_BF54X_LQ043
552 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
553 depends on FB && (BF54x) && !BF542
554 select FB_CFB_FILLRECT
555 select FB_CFB_COPYAREA
556 select FB_CFB_IMAGEBLIT
558 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
560 config FB_BFIN_T350MCQB
561 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
562 depends on FB && BLACKFIN
564 select FB_CFB_FILLRECT
565 select FB_CFB_COPYAREA
566 select FB_CFB_IMAGEBLIT
568 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
569 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
570 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
572 config FB_BFIN_LQ035Q1
573 tristate "SHARP LQ035Q1DH02 TFT LCD"
574 depends on FB && BLACKFIN && SPI
575 select FB_CFB_FILLRECT
576 select FB_CFB_COPYAREA
577 select FB_CFB_IMAGEBLIT
580 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
581 the Blackfin Landscape LCD EZ-Extender Card.
582 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
583 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
585 To compile this driver as a module, choose M here: the
586 module will be called bfin-lq035q1-fb.
588 config FB_BF537_LQ035
589 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
590 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
591 select FB_CFB_FILLRECT
592 select FB_CFB_COPYAREA
593 select FB_CFB_IMAGEBLIT
596 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
599 To compile this driver as a module, choose M here: the
600 module will be called bf537-lq035.
603 tristate "Blackfin ADV7393 Video encoder"
604 depends on FB && BLACKFIN
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
610 This is the framebuffer device for a ADV7393 video encoder
611 attached to a Blackfin on the PPI port.
612 If your Blackfin board has a ADV7393 select Y.
614 To compile this driver as a module, choose M here: the
615 module will be called bfin_adv7393fb.
618 prompt "Video mode support"
619 depends on FB_BFIN_7393
629 bool 'NTSC 640x480 (Experimental)'
632 bool 'PAL 640x480 (Experimental)'
635 bool 'NTSC 720x480 YCbCR input'
638 bool 'PAL 720x576 YCbCR input'
643 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
644 depends on (FB_BFIN_7393)
645 default ADV7393_1XMEM
655 tristate "HP STI frame buffer device support"
656 depends on FB && PARISC
657 select FB_CFB_FILLRECT
658 select FB_CFB_COPYAREA
659 select FB_CFB_IMAGEBLIT
664 STI refers to the HP "Standard Text Interface" which is a set of
665 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
666 Enabling this option will implement the linux framebuffer device
667 using calls to the STI BIOS routines for initialisation.
669 If you enable this option, you will get a planar framebuffer device
670 /dev/fb which will work on the most common HP graphic cards of the
671 NGLE family, including the artist chips (in the 7xx and Bxxx series),
672 HCRX, HCRX24, CRX, CRX24 and VisEG series.
674 It is safe to enable this option, so you should probably say "Y".
677 bool "Generic Macintosh display support"
678 depends on (FB = y) && MAC
679 select FB_CFB_FILLRECT
680 select FB_CFB_COPYAREA
681 select FB_CFB_IMAGEBLIT
686 depends on (FB = y) && DIO
687 select FB_CFB_IMAGEBLIT
691 tristate "TGA/SFB+ framebuffer support"
692 depends on FB && (ALPHA || TC)
693 select FB_CFB_FILLRECT
694 select FB_CFB_COPYAREA
695 select FB_CFB_IMAGEBLIT
698 This is the frame buffer device driver for generic TGA and SFB+
699 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
700 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
701 TURBOchannel cards, also known as PMAGD-A, -B and -C.
703 Due to hardware limitations ZLX-E2 and E3 cards are not supported
704 for DECstation 5000/200 systems. Additionally due to firmware
705 limitations these cards may cause troubles with booting DECstation
706 5000/240 and /260 systems, but are fully supported under Linux if
707 you manage to get it going. ;-)
709 Say Y if you have one of those.
712 tristate "Userspace VESA VGA graphics support"
713 depends on FB && CONNECTOR
714 select FB_CFB_FILLRECT
715 select FB_CFB_COPYAREA
716 select FB_CFB_IMAGEBLIT
717 select FB_MODE_HELPERS
719 This is the frame buffer driver for generic VBE 2.0 compliant
720 graphic cards. It can also take advantage of VBE 3.0 features,
721 such as refresh rate adjustment.
723 This driver generally provides more features than vesafb but
724 requires a userspace helper application called 'v86d'. See
725 <file:Documentation/fb/uvesafb.txt> for more information.
730 bool "VESA VGA graphics support"
731 depends on (FB = y) && X86
732 select FB_CFB_FILLRECT
733 select FB_CFB_COPYAREA
734 select FB_CFB_IMAGEBLIT
735 select FB_BOOT_VESA_SUPPORT
737 This is the frame buffer device driver for generic VESA 2.0
738 compliant graphic cards. The older VESA 1.2 cards are not supported.
739 You will get a boot time penguin logo at no additional cost. Please
740 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
743 bool "EFI-based Framebuffer Support"
744 depends on (FB = y) && X86 && EFI
745 select FB_CFB_FILLRECT
746 select FB_CFB_COPYAREA
747 select FB_CFB_IMAGEBLIT
749 This is the EFI frame buffer device driver. If the firmware on
750 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
751 using the EFI framebuffer as your console.
754 tristate "N411 Apollo/Hecuba devkit support"
755 depends on FB && X86 && MMU
756 select FB_SYS_FILLRECT
757 select FB_SYS_COPYAREA
758 select FB_SYS_IMAGEBLIT
760 select FB_DEFERRED_IO
763 This enables support for the Apollo display controller in its
764 Hecuba form using the n411 devkit.
767 tristate "Hercules mono graphics support"
770 Say Y here if you have a Hercules mono graphics card.
772 To compile this driver as a module, choose M here: the
773 module will be called hgafb.
775 As this card technology is at least 25 years old,
776 most people will answer N here.
779 bool "SGI Graphics Backend frame buffer support"
780 depends on (FB = y) && SGI_IP32
781 select FB_CFB_FILLRECT
782 select FB_CFB_COPYAREA
783 select FB_CFB_IMAGEBLIT
785 This is the frame buffer device driver for SGI Graphics Backend.
786 This chip is used in SGI O2 and Visual Workstation 320/540.
789 int "Video memory size in MB"
793 This is the amount of memory reserved for the framebuffer,
794 which can be any value between 1MB and 8MB.
797 bool "SBUS and UPA framebuffers"
798 depends on (FB = y) && SPARC
800 Say Y if you want support for SBUS or UPA based frame buffer device.
804 depends on (FB = y) && (SPARC && FB_SBUS)
805 select FB_CFB_FILLRECT
806 select FB_CFB_COPYAREA
807 select FB_CFB_IMAGEBLIT
809 This is the frame buffer device driver for the BWtwo frame buffer.
812 bool "CGthree support"
813 depends on (FB = y) && (SPARC && FB_SBUS)
814 select FB_CFB_FILLRECT
815 select FB_CFB_COPYAREA
816 select FB_CFB_IMAGEBLIT
818 This is the frame buffer device driver for the CGthree frame buffer.
821 bool "CGsix (GX,TurboGX) support"
822 depends on (FB = y) && (SPARC && FB_SBUS)
823 select FB_CFB_COPYAREA
824 select FB_CFB_IMAGEBLIT
826 This is the frame buffer device driver for the CGsix (GX, TurboGX)
830 bool "Creator/Creator3D/Elite3D support"
831 depends on FB_SBUS && SPARC64
832 select FB_CFB_COPYAREA
833 select FB_CFB_IMAGEBLIT
835 This is the frame buffer device driver for the Creator, Creator3D,
836 and Elite3D graphics boards.
839 bool "TCX (SS4/SS5 only) support"
841 select FB_CFB_FILLRECT
842 select FB_CFB_COPYAREA
843 select FB_CFB_IMAGEBLIT
845 This is the frame buffer device driver for the TCX 24/8bit frame
849 bool "CGfourteen (SX) support"
851 select FB_CFB_FILLRECT
852 select FB_CFB_COPYAREA
853 select FB_CFB_IMAGEBLIT
855 This is the frame buffer device driver for the CGfourteen frame
856 buffer on Desktop SPARCsystems with the SX graphics option.
859 bool "P9100 (Sparcbook 3 only) support"
861 select FB_CFB_FILLRECT
862 select FB_CFB_COPYAREA
863 select FB_CFB_IMAGEBLIT
865 This is the frame buffer device driver for the P9100 card
866 supported on Sparcbook 3 machines.
869 bool "Leo (ZX) support"
871 select FB_CFB_FILLRECT
872 select FB_CFB_COPYAREA
873 select FB_CFB_IMAGEBLIT
875 This is the frame buffer device driver for the SBUS-based Sun ZX
876 (leo) frame buffer cards.
879 bool "IGA 168x display support"
880 depends on (FB = y) && SPARC32
881 select FB_CFB_FILLRECT
882 select FB_CFB_COPYAREA
883 select FB_CFB_IMAGEBLIT
885 This is the framebuffer device for the INTERGRAPHICS 1680 and
886 successor frame buffer cards.
889 bool "Sun XVR-500 3DLABS Wildcat support"
890 depends on (FB = y) && PCI && SPARC64
891 select FB_CFB_FILLRECT
892 select FB_CFB_COPYAREA
893 select FB_CFB_IMAGEBLIT
895 This is the framebuffer device for the Sun XVR-500 and similar
896 graphics cards based upon the 3DLABS Wildcat chipset. The driver
897 only works on sparc64 systems where the system firmware has
898 mostly initialized the card already. It is treated as a
899 completely dumb framebuffer device.
902 bool "Sun XVR-2500 3DLABS Wildcat support"
903 depends on (FB = y) && PCI && SPARC64
904 select FB_CFB_FILLRECT
905 select FB_CFB_COPYAREA
906 select FB_CFB_IMAGEBLIT
908 This is the framebuffer device for the Sun XVR-2500 and similar
909 graphics cards based upon the 3DLABS Wildcat chipset. The driver
910 only works on sparc64 systems where the system firmware has
911 mostly initialized the card already. It is treated as a
912 completely dumb framebuffer device.
915 bool "Sun XVR-1000 support"
916 depends on (FB = y) && SPARC64
917 select FB_CFB_FILLRECT
918 select FB_CFB_COPYAREA
919 select FB_CFB_IMAGEBLIT
921 This is the framebuffer device for the Sun XVR-1000 and similar
922 graphics cards. The driver only works on sparc64 systems where
923 the system firmware has mostly initialized the card already. It
924 is treated as a completely dumb framebuffer device.
927 tristate "NEC PowerVR 2 display support"
928 depends on FB && SH_DREAMCAST
929 select FB_CFB_FILLRECT
930 select FB_CFB_COPYAREA
931 select FB_CFB_IMAGEBLIT
933 Say Y here if you have a PowerVR 2 card in your box. If you plan to
934 run linux on your Dreamcast, you will have to say Y here.
935 This driver may or may not work on other PowerVR 2 cards, but is
936 totally untested. Use at your own risk. If unsure, say N.
938 To compile this driver as a module, choose M here: the
939 module will be called pvr2fb.
941 You can pass several parameters to the driver at boot time or at
942 module load time. The parameters look like "video=pvr2:XXX", where
943 the meaning of XXX can be found at the end of the main source file
944 (<file:drivers/video/pvr2fb.c>). Please see the file
945 <file:Documentation/fb/pvr2fb.txt>.
948 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
949 depends on FB && HAS_DMA
950 select FB_CFB_FILLRECT
951 select FB_CFB_COPYAREA
952 select FB_CFB_IMAGEBLIT
954 This enables support for the OpenCores VGA/LCD core.
956 The OpenCores VGA/LCD core is typically used together with
957 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
958 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
960 The source code and specification for the core is available at
961 <http://opencores.org/project,vga_lcd>
964 tristate "Epson S1D13XXX framebuffer support"
966 select FB_CFB_FILLRECT
967 select FB_CFB_COPYAREA
968 select FB_CFB_IMAGEBLIT
970 Support for S1D13XXX framebuffer device family (currently only
971 working with S1D13806). Product specs at
972 <http://vdc.epson.com/>
975 tristate "AT91/AT32 LCD Controller support"
976 depends on FB && HAVE_FB_ATMEL
978 select FB_CFB_FILLRECT
979 select FB_CFB_COPYAREA
980 select FB_CFB_IMAGEBLIT
981 select FB_MODE_HELPERS
982 select VIDEOMODE_HELPERS
984 This enables support for the AT91/AT32 LCD Controller.
987 bool "Frame Buffer in internal SRAM"
988 depends on FB_ATMEL && ARCH_AT91SAM9261
990 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
991 to let frame buffer in external SDRAM.
994 bool "Use a STN display with AT91/AT32 LCD Controller"
995 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
998 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
999 Controller. Say N if you want to connect a TFT.
1004 tristate "nVidia Framebuffer Support"
1005 depends on FB && PCI
1006 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1007 select FB_MODE_HELPERS
1008 select FB_CFB_FILLRECT
1009 select FB_CFB_COPYAREA
1010 select FB_CFB_IMAGEBLIT
1014 This driver supports graphics boards with the nVidia chips, TNT
1015 and newer. For very old chipsets, such as the RIVA128, then use
1017 Say Y if you have such a graphics board.
1019 To compile this driver as a module, choose M here: the
1020 module will be called nvidiafb.
1022 config FB_NVIDIA_I2C
1023 bool "Enable DDC Support"
1024 depends on FB_NVIDIA
1027 This enables I2C support for nVidia Chipsets. This is used
1028 only for getting EDID information from the attached display
1029 allowing for robust video mode handling and switching.
1031 Because fbdev-2.6 requires that drivers must be able to
1032 independently validate video mode parameters, you should say Y
1035 config FB_NVIDIA_DEBUG
1036 bool "Lots of debug output"
1037 depends on FB_NVIDIA
1040 Say Y here if you want the nVidia driver to output all sorts
1041 of debugging information to provide to the maintainer when
1042 something goes wrong.
1044 config FB_NVIDIA_BACKLIGHT
1045 bool "Support for backlight control"
1046 depends on FB_NVIDIA
1049 Say Y here if you want to control the backlight of your display.
1052 tristate "nVidia Riva support"
1053 depends on FB && PCI
1054 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1055 select FB_MODE_HELPERS
1056 select FB_CFB_FILLRECT
1057 select FB_CFB_COPYAREA
1058 select FB_CFB_IMAGEBLIT
1062 This driver supports graphics boards with the nVidia Riva/Geforce
1064 Say Y if you have such a graphics board.
1066 To compile this driver as a module, choose M here: the
1067 module will be called rivafb.
1070 bool "Enable DDC Support"
1074 This enables I2C support for nVidia Chipsets. This is used
1075 only for getting EDID information from the attached display
1076 allowing for robust video mode handling and switching.
1078 Because fbdev-2.6 requires that drivers must be able to
1079 independently validate video mode parameters, you should say Y
1082 config FB_RIVA_DEBUG
1083 bool "Lots of debug output"
1087 Say Y here if you want the Riva driver to output all sorts
1088 of debugging information to provide to the maintainer when
1089 something goes wrong.
1091 config FB_RIVA_BACKLIGHT
1092 bool "Support for backlight control"
1096 Say Y here if you want to control the backlight of your display.
1099 tristate "Intel740 support"
1100 depends on FB && PCI
1101 select FB_MODE_HELPERS
1102 select FB_CFB_FILLRECT
1103 select FB_CFB_COPYAREA
1104 select FB_CFB_IMAGEBLIT
1108 This driver supports graphics cards based on Intel740 chip.
1111 tristate "Intel 810/815 support"
1112 depends on FB && PCI && X86_32 && AGP_INTEL
1113 select FB_MODE_HELPERS
1114 select FB_CFB_FILLRECT
1115 select FB_CFB_COPYAREA
1116 select FB_CFB_IMAGEBLIT
1119 This driver supports the on-board graphics built in to the Intel 810
1120 and 815 chipsets. Say Y if you have and plan to use such a board.
1122 To compile this driver as a module, choose M here: the
1123 module will be called i810fb.
1125 For more information, please read
1126 <file:Documentation/fb/intel810.txt>
1129 bool "use VESA Generalized Timing Formula"
1132 If you say Y, then the VESA standard, Generalized Timing Formula
1133 or GTF, will be used to calculate the required video timing values
1134 per video mode. Since the GTF allows nondiscrete timings
1135 (nondiscrete being a range of values as opposed to discrete being a
1136 set of values), you'll be able to use any combination of horizontal
1137 and vertical resolutions, and vertical refresh rates without having
1138 to specify your own timing parameters. This is especially useful
1139 to maximize the performance of an aging display, or if you just
1140 have a display with nonstandard dimensions. A VESA compliant
1141 monitor is recommended, but can still work with non-compliant ones.
1142 If you need or want this, then select this option. The timings may
1143 not be compliant with Intel's recommended values. Use at your own
1146 If you say N, the driver will revert to discrete video timings
1147 using a set recommended by Intel in their documentation.
1152 bool "Enable DDC Support"
1153 depends on FB_I810 && FB_I810_GTF
1158 tristate "Intel LE80578 (Vermilion) support"
1159 depends on FB && PCI && X86
1160 select FB_MODE_HELPERS
1161 select FB_CFB_FILLRECT
1162 select FB_CFB_COPYAREA
1163 select FB_CFB_IMAGEBLIT
1165 This driver supports the LE80578 (Vermilion Range) chipset
1167 config FB_CARILLO_RANCH
1168 tristate "Intel Carillo Ranch support"
1169 depends on FB_LE80578 && FB && PCI && X86
1171 This driver supports the LE80578 (Carillo Ranch) board
1174 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1175 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1176 select FB_MODE_HELPERS
1177 select FB_CFB_FILLRECT
1178 select FB_CFB_COPYAREA
1179 select FB_CFB_IMAGEBLIT
1180 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1181 depends on !DRM_I915
1183 This driver supports the on-board graphics built in to the Intel
1184 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1185 Say Y if you have and plan to use such a board.
1187 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1189 To compile this driver as a module, choose M here: the
1190 module will be called intelfb.
1192 For more information, please read <file:Documentation/fb/intelfb.txt>
1194 config FB_INTEL_DEBUG
1195 bool "Intel driver Debug Messages"
1198 Say Y here if you want the Intel driver to output all sorts
1199 of debugging information to provide to the maintainer when
1200 something goes wrong.
1203 bool "DDC/I2C for Intel framebuffer support"
1208 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1211 tristate "Matrox acceleration"
1212 depends on FB && PCI
1213 select FB_CFB_FILLRECT
1214 select FB_CFB_COPYAREA
1215 select FB_CFB_IMAGEBLIT
1216 select FB_TILEBLITTING
1217 select FB_MACMODES if PPC_PMAC
1219 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1220 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1221 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1222 Matrox G400, G450 or G550 card in your box.
1224 To compile this driver as a module, choose M here: the
1225 module will be called matroxfb.
1227 You can pass several parameters to the driver at boot time or at
1228 module load time. The parameters look like "video=matroxfb:XXX", and
1229 are described in <file:Documentation/fb/matroxfb.txt>.
1231 config FB_MATROX_MILLENIUM
1232 bool "Millennium I/II support"
1233 depends on FB_MATROX
1235 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1236 video card. If you select "Advanced lowlevel driver options" below,
1237 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1238 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1239 also use font widths different from 8.
1241 config FB_MATROX_MYSTIQUE
1242 bool "Mystique support"
1243 depends on FB_MATROX
1245 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1246 video card. If you select "Advanced lowlevel driver options" below,
1247 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1248 packed pixel and 32 bpp packed pixel. You can also use font widths
1252 bool "G100/G200/G400/G450/G550 support"
1253 depends on FB_MATROX
1255 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1256 video card. If you select "Advanced lowlevel driver options", you
1257 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1258 pixel and 32 bpp packed pixel. You can also use font widths
1261 If you need support for G400 secondary head, you must say Y to
1262 "Matrox I2C support" and "G400 second head support" right below.
1263 G450/G550 secondary head and digital output are supported without
1266 The driver starts in monitor mode. You must use the matroxset tool
1267 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1268 swap primary and secondary head outputs, or to change output mode.
1269 Secondary head driver always start in 640x480 resolution and you
1270 must use fbset to change it.
1272 Do not forget that second head supports only 16 and 32 bpp
1273 packed pixels, so it is a good idea to compile them into the kernel
1274 too. You can use only some font widths, as the driver uses generic
1275 painting procedures (the secondary head does not use acceleration
1278 G450/G550 hardware can display TV picture only from secondary CRTC,
1279 and it performs no scaling, so picture must have 525 or 625 lines.
1281 config FB_MATROX_I2C
1282 tristate "Matrox I2C support"
1283 depends on FB_MATROX
1286 This drivers creates I2C buses which are needed for accessing the
1287 DDC (I2C) bus present on all Matroxes, an I2C bus which
1288 interconnects Matrox optional devices, like MGA-TVO on G200 and
1289 G400, and the secondary head DDC bus, present on G400 only.
1291 You can say Y or M here if you want to experiment with monitor
1292 detection code. You must say Y or M here if you want to use either
1293 second head of G400 or MGA-TVO on G200 or G400.
1295 If you compile it as module, it will create a module named
1298 config FB_MATROX_MAVEN
1299 tristate "G400 second head support"
1300 depends on FB_MATROX_G && FB_MATROX_I2C
1302 WARNING !!! This support does not work with G450 !!!
1304 Say Y or M here if you want to use a secondary head (meaning two
1305 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1306 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1307 secondary head output is blanked while you are in X. With XFree
1308 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1309 the fbdev driver on first head and the fbdev driver on second head.
1311 If you compile it as module, two modules are created,
1312 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1313 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1314 also load i2c-matroxfb to get it to run.
1316 The driver starts in monitor mode and you must use the matroxset
1318 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1319 PAL or NTSC or to swap primary and secondary head outputs.
1320 Secondary head driver also always start in 640x480 resolution, you
1321 must use fbset to change it.
1323 Also do not forget that second head supports only 16 and 32 bpp
1324 packed pixels, so it is a good idea to compile them into the kernel
1325 too. You can use only some font widths, as the driver uses generic
1326 painting procedures (the secondary head does not use acceleration
1330 tristate "ATI Radeon display support"
1331 depends on FB && PCI
1332 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1333 select FB_MODE_HELPERS
1334 select FB_CFB_FILLRECT
1335 select FB_CFB_COPYAREA
1336 select FB_CFB_IMAGEBLIT
1337 select FB_MACMODES if PPC_OF
1339 Choose this option if you want to use an ATI Radeon graphics card as
1340 a framebuffer device. There are both PCI and AGP versions. You
1341 don't need to choose this to run the Radeon in plain VGA mode.
1343 There is a product page at
1344 http://products.amd.com/en-us/GraphicCardResult.aspx
1346 config FB_RADEON_I2C
1347 bool "DDC/I2C for ATI Radeon support"
1348 depends on FB_RADEON
1352 Say Y here if you want DDC/I2C support for your Radeon board.
1354 config FB_RADEON_BACKLIGHT
1355 bool "Support for backlight control"
1356 depends on FB_RADEON
1359 Say Y here if you want to control the backlight of your display.
1361 config FB_RADEON_DEBUG
1362 bool "Lots of debug output from Radeon driver"
1363 depends on FB_RADEON
1366 Say Y here if you want the Radeon driver to output all sorts
1367 of debugging information to provide to the maintainer when
1368 something goes wrong.
1371 tristate "ATI Rage128 display support"
1372 depends on FB && PCI
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1376 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1377 select FB_MACMODES if PPC_PMAC
1379 This driver supports graphics boards with the ATI Rage128 chips.
1380 Say Y if you have such a graphics board and read
1381 <file:Documentation/fb/aty128fb.txt>.
1383 To compile this driver as a module, choose M here: the
1384 module will be called aty128fb.
1386 config FB_ATY128_BACKLIGHT
1387 bool "Support for backlight control"
1388 depends on FB_ATY128
1391 Say Y here if you want to control the backlight of your display.
1394 tristate "ATI Mach64 display support" if PCI || ATARI
1395 depends on FB && !SPARC32
1396 select FB_CFB_FILLRECT
1397 select FB_CFB_COPYAREA
1398 select FB_CFB_IMAGEBLIT
1399 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1400 select FB_MACMODES if PPC
1402 This driver supports graphics boards with the ATI Mach64 chips.
1403 Say Y if you have such a graphics board.
1405 To compile this driver as a module, choose M here: the
1406 module will be called atyfb.
1409 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1410 depends on PCI && FB_ATY
1411 default y if SPARC64 && PCI
1413 Say Y here to support use of ATI's 64-bit Rage boards (or other
1414 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1415 framebuffer device. The ATI product support page for these boards
1416 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1418 config FB_ATY_GENERIC_LCD
1419 bool "Mach64 generic LCD support"
1420 depends on FB_ATY_CT
1422 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1423 Rage XC, or Rage XL chipset.
1426 bool "Mach64 GX support" if PCI
1430 Say Y here to support use of the ATI Mach64 Graphics Expression
1431 board (or other boards based on the Mach64 GX chipset) as a
1432 framebuffer device. The ATI product support page for these boards
1434 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1436 config FB_ATY_BACKLIGHT
1437 bool "Support for backlight control"
1441 Say Y here if you want to control the backlight of your display.
1444 tristate "S3 Trio/Virge support"
1445 depends on FB && PCI
1446 select FB_CFB_FILLRECT
1447 select FB_CFB_COPYAREA
1448 select FB_CFB_IMAGEBLIT
1449 select FB_TILEBLITTING
1452 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1454 Driver for graphics boards with S3 Trio / S3 Virge chip.
1457 bool "DDC for S3 support"
1462 Say Y here if you want DDC support for your S3 graphics card.
1465 tristate "S3 Savage support"
1466 depends on FB && PCI
1467 select FB_MODE_HELPERS
1468 select FB_CFB_FILLRECT
1469 select FB_CFB_COPYAREA
1470 select FB_CFB_IMAGEBLIT
1473 This driver supports notebooks and computers with S3 Savage PCI/AGP
1476 Say Y if you have such a graphics card.
1478 To compile this driver as a module, choose M here; the module
1479 will be called savagefb.
1481 config FB_SAVAGE_I2C
1482 bool "Enable DDC2 Support"
1483 depends on FB_SAVAGE
1486 This enables I2C support for S3 Savage Chipsets. This is used
1487 only for getting EDID information from the attached display
1488 allowing for robust video mode handling and switching.
1490 Because fbdev-2.6 requires that drivers must be able to
1491 independently validate video mode parameters, you should say Y
1494 config FB_SAVAGE_ACCEL
1495 bool "Enable Console Acceleration"
1496 depends on FB_SAVAGE
1499 This option will compile in console acceleration support. If
1500 the resulting framebuffer console has bothersome glitches, then
1504 tristate "SiS/XGI display support"
1505 depends on FB && PCI
1506 select FB_CFB_FILLRECT
1507 select FB_CFB_COPYAREA
1508 select FB_CFB_IMAGEBLIT
1509 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1511 This is the frame buffer device driver for the SiS 300, 315, 330
1512 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1513 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1515 To compile this driver as a module, choose M here; the module
1516 will be called sisfb.
1519 bool "SiS 300 series support"
1522 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1525 bool "SiS 315/330/340 series and XGI support"
1528 Say Y here to support use of the SiS 315, 330 and 340 series
1529 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1530 as XGI V3XT, V5, V8 and Z7.
1533 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1534 depends on FB && PCI && X86
1535 select FB_CFB_FILLRECT
1536 select FB_CFB_COPYAREA
1537 select FB_CFB_IMAGEBLIT
1542 This is the frame buffer device driver for Graphics chips of VIA
1543 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1544 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1546 Say Y if you have a VIA UniChrome graphics board.
1548 To compile this driver as a module, choose M here: the
1549 module will be called viafb.
1553 config FB_VIA_DIRECT_PROCFS
1554 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1558 Allow direct hardware access to some output registers via procfs.
1559 This is dangerous but may provide the only chance to get the
1560 correct output device configuration.
1561 Its use is strongly discouraged.
1563 config FB_VIA_X_COMPATIBILITY
1564 bool "X server compatibility"
1568 This option reduces the functionality (power saving, ...) of the
1569 framebuffer to avoid negative impact on the OpenChrome X server.
1570 If you use any X server other than fbdev you should enable this
1571 otherwise it should be safe to disable it and allow using all
1577 tristate "NeoMagic display support"
1578 depends on FB && PCI
1579 select FB_MODE_HELPERS
1580 select FB_CFB_FILLRECT
1581 select FB_CFB_COPYAREA
1582 select FB_CFB_IMAGEBLIT
1585 This driver supports notebooks with NeoMagic PCI chips.
1586 Say Y if you have such a graphics card.
1588 To compile this driver as a module, choose M here: the
1589 module will be called neofb.
1592 tristate "IMG Kyro support"
1593 depends on FB && PCI
1594 select FB_CFB_FILLRECT
1595 select FB_CFB_COPYAREA
1596 select FB_CFB_IMAGEBLIT
1598 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1601 To compile this driver as a module, choose M here: the
1602 module will be called kyrofb.
1605 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1606 depends on FB && PCI
1607 select FB_CFB_IMAGEBLIT
1608 select FB_CFB_FILLRECT
1609 select FB_CFB_COPYAREA
1610 select FB_MODE_HELPERS
1612 This driver supports graphics boards with the 3Dfx Banshee,
1613 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1614 such a graphics board.
1616 To compile this driver as a module, choose M here: the
1617 module will be called tdfxfb.
1619 config FB_3DFX_ACCEL
1620 bool "3Dfx Acceleration functions"
1623 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1624 device driver with acceleration functions.
1627 bool "Enable DDC/I2C support"
1632 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1635 tristate "3Dfx Voodoo Graphics (sst1) support"
1636 depends on FB && PCI
1637 select FB_CFB_FILLRECT
1638 select FB_CFB_COPYAREA
1639 select FB_CFB_IMAGEBLIT
1641 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1642 Voodoo2 (cvg) based graphics card.
1644 To compile this driver as a module, choose M here: the
1645 module will be called sstfb.
1647 WARNING: Do not use any application that uses the 3D engine
1648 (namely glide) while using this driver.
1649 Please read the <file:Documentation/fb/sstfb.txt> for supported
1650 options and other important info support.
1653 tristate "VIA VT8623 support"
1654 depends on FB && PCI
1655 select FB_CFB_FILLRECT
1656 select FB_CFB_COPYAREA
1657 select FB_CFB_IMAGEBLIT
1658 select FB_TILEBLITTING
1661 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1663 Driver for CastleRock integrated graphics core in the
1664 VIA VT8623 [Apollo CLE266] chipset.
1667 tristate "Trident/CyberXXX/CyberBlade support"
1668 depends on FB && PCI
1669 select FB_CFB_FILLRECT
1670 select FB_CFB_COPYAREA
1671 select FB_CFB_IMAGEBLIT
1673 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1674 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1676 There are also integrated versions of these chips called CyberXXXX,
1677 CyberImage or CyberBlade. These chips are mostly found in laptops
1678 but also on some motherboards including early VIA EPIA motherboards.
1679 For more information, read <file:Documentation/fb/tridentfb.txt>
1681 Say Y if you have such a graphics board.
1683 To compile this driver as a module, choose M here: the
1684 module will be called tridentfb.
1687 tristate "ARK 2000PV support"
1688 depends on FB && PCI
1689 select FB_CFB_FILLRECT
1690 select FB_CFB_COPYAREA
1691 select FB_CFB_IMAGEBLIT
1692 select FB_TILEBLITTING
1695 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1697 Driver for PCI graphics boards with ARK 2000PV chip
1698 and ICS 5342 RAMDAC.
1701 tristate "Permedia3 support"
1702 depends on FB && PCI
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 This is the frame buffer device driver for the 3DLabs Permedia3
1708 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1709 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1710 and maybe other boards.
1713 tristate "Fujitsu carmine frame buffer support"
1714 depends on FB && PCI
1715 select FB_CFB_FILLRECT
1716 select FB_CFB_COPYAREA
1717 select FB_CFB_IMAGEBLIT
1719 This is the frame buffer device driver for the Fujitsu Carmine chip.
1720 The driver provides two independent frame buffer devices.
1723 depends on FB_CARMINE
1724 prompt "DRAM timing"
1725 default FB_CARMINE_DRAM_EVAL
1727 config FB_CARMINE_DRAM_EVAL
1728 bool "Eval board timings"
1730 Use timings which work on the eval card.
1732 config CARMINE_DRAM_CUSTOM
1733 bool "Custom board timings"
1735 Use custom board timings.
1739 bool "Au1100 LCD Driver"
1740 depends on (FB = y) && MIPS_ALCHEMY
1741 select FB_CFB_FILLRECT
1742 select FB_CFB_COPYAREA
1743 select FB_CFB_IMAGEBLIT
1745 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1746 various panels and CRTs by passing in kernel cmd line option
1747 au1100fb:panel=<name>.
1750 bool "Au1200/Au1300 LCD Driver"
1751 depends on (FB = y) && MIPS_ALCHEMY
1752 select FB_SYS_FILLRECT
1753 select FB_SYS_COPYAREA
1754 select FB_SYS_IMAGEBLIT
1757 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1758 It can drive various panels and CRTs by passing in kernel cmd line
1759 option au1200fb:panel=<name>.
1762 bool "VIA VT8500 framebuffer support"
1763 depends on (FB = y) && ARM && ARCH_VT8500
1764 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1765 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1766 select FB_SYS_IMAGEBLIT
1767 select FB_MODE_HELPERS
1768 select VIDEOMODE_HELPERS
1770 This is the framebuffer driver for VIA VT8500 integrated LCD
1774 bool "Wondermedia WM8xxx-series frame buffer support"
1775 depends on (FB = y) && ARM && ARCH_VT8500
1776 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1777 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1778 select FB_SYS_IMAGEBLIT
1779 select FB_MODE_HELPERS
1780 select VIDEOMODE_HELPERS
1782 This is the framebuffer driver for WonderMedia WM8xxx-series
1783 integrated LCD controller. This driver covers the WM8505, WM8650
1786 config FB_WMT_GE_ROPS
1787 bool "VT8500/WM8xxx accelerated raster ops support"
1788 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1791 This adds support for accelerated raster operations on the
1792 VIA VT8500 and Wondermedia 85xx series SoCs.
1794 source "drivers/video/fbdev/geode/Kconfig"
1797 tristate "HD64461 Frame Buffer support"
1798 depends on FB && HD64461
1799 select FB_CFB_FILLRECT
1800 select FB_CFB_COPYAREA
1801 select FB_CFB_IMAGEBLIT
1803 This is the frame buffer device driver for the Hitachi HD64461 LCD
1807 bool "PMAG-AA TURBOchannel framebuffer support"
1808 depends on (FB = y) && TC
1809 select FB_CFB_FILLRECT
1810 select FB_CFB_COPYAREA
1811 select FB_CFB_IMAGEBLIT
1813 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1814 used mainly in the MIPS-based DECstation series.
1817 tristate "PMAG-BA TURBOchannel framebuffer support"
1819 select FB_CFB_FILLRECT
1820 select FB_CFB_COPYAREA
1821 select FB_CFB_IMAGEBLIT
1823 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1824 used mainly in the MIPS-based DECstation series.
1827 tristate "PMAGB-B TURBOchannel framebuffer support"
1829 select FB_CFB_FILLRECT
1830 select FB_CFB_COPYAREA
1831 select FB_CFB_IMAGEBLIT
1833 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1834 in the MIPS-based DECstation series. The card is currently only
1835 supported in 1280x1024x8 mode.
1838 bool "Maxine (Personal DECstation) onboard framebuffer support"
1839 depends on (FB = y) && MACH_DECSTATION
1840 select FB_CFB_FILLRECT
1841 select FB_CFB_COPYAREA
1842 select FB_CFB_IMAGEBLIT
1844 Support for the onboard framebuffer (1024x768x8) in the Personal
1845 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1849 bool "G364 frame buffer support"
1850 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1851 select FB_CFB_FILLRECT
1852 select FB_CFB_COPYAREA
1853 select FB_CFB_IMAGEBLIT
1855 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1856 Olivetti M700-10 systems.
1859 bool "Motorola 68328 native frame buffer support"
1860 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1861 select FB_CFB_FILLRECT
1862 select FB_CFB_COPYAREA
1863 select FB_CFB_IMAGEBLIT
1865 Say Y here if you want to support the built-in frame buffer of
1866 the Motorola 68328 CPU family.
1869 tristate "PXA168/910 LCD framebuffer support"
1870 depends on FB && (CPU_PXA168 || CPU_PXA910)
1871 select FB_CFB_FILLRECT
1872 select FB_CFB_COPYAREA
1873 select FB_CFB_IMAGEBLIT
1875 Frame buffer driver for the built-in LCD controller in the Marvell
1879 tristate "PXA LCD framebuffer support"
1880 depends on FB && ARCH_PXA
1881 select FB_CFB_FILLRECT
1882 select FB_CFB_COPYAREA
1883 select FB_CFB_IMAGEBLIT
1885 Frame buffer driver for the built-in LCD controller in the Intel
1888 This driver is also available as a module ( = code which can be
1889 inserted and removed from the running kernel whenever you want). The
1890 module will be called pxafb. If you want to compile it as a module,
1891 say M here and read <file:Documentation/kbuild/modules.txt>.
1895 config FB_PXA_OVERLAY
1896 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1898 depends on FB_PXA && (PXA27x || PXA3xx)
1900 config FB_PXA_SMARTPANEL
1901 bool "PXA Smartpanel LCD support"
1905 config FB_PXA_PARAMETERS
1906 bool "PXA LCD command line parameters"
1910 Enable the use of kernel command line or module parameters
1911 to configure the physical properties of the LCD panel when
1912 using the PXA LCD driver.
1914 This option allows you to override the panel parameters
1915 supplied by the platform in order to support multiple
1916 different models of flatpanel. If you will only be using a
1917 single model of flatpanel then you can safely leave this
1920 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1923 tristate "PXA3xx 2D graphics accelerator driver"
1926 Kernelspace driver for the 2D graphics controller unit (GCU)
1927 found on PXA3xx processors. There is a counterpart driver in the
1928 DirectFB suite, see http://www.directfb.org/
1930 If you compile this as a module, it will be called pxa3xx_gcu.
1933 tristate "2700G LCD framebuffer support"
1934 depends on FB && ARCH_PXA
1935 select FB_CFB_FILLRECT
1936 select FB_CFB_COPYAREA
1937 select FB_CFB_IMAGEBLIT
1939 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1943 bool "Enable debugging info via debugfs"
1944 depends on FB_MBX && DEBUG_FS
1947 Enable this if you want debugging information using the debug
1948 filesystem (debugfs)
1953 tristate "Freescale DIU framebuffer support"
1954 depends on FB && FSL_SOC
1955 select FB_MODE_HELPERS
1956 select FB_CFB_FILLRECT
1957 select FB_CFB_COPYAREA
1958 select FB_CFB_IMAGEBLIT
1959 select PPC_LIB_RHEAP
1961 Framebuffer driver for the Freescale SoC DIU
1964 tristate "W100 frame buffer support"
1965 depends on FB && ARCH_PXA
1966 select FB_CFB_FILLRECT
1967 select FB_CFB_COPYAREA
1968 select FB_CFB_IMAGEBLIT
1970 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1971 It can also drive the w3220 chip found on iPAQ hx4700.
1973 This driver is also available as a module ( = code which can be
1974 inserted and removed from the running kernel whenever you want). The
1975 module will be called w100fb. If you want to compile it as a module,
1976 say M here and read <file:Documentation/kbuild/modules.txt>.
1980 config FB_SH_MOBILE_LCDC
1981 tristate "SuperH Mobile LCDC framebuffer support"
1982 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1983 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1984 select FB_SYS_FILLRECT
1985 select FB_SYS_COPYAREA
1986 select FB_SYS_IMAGEBLIT
1988 select FB_DEFERRED_IO
1990 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1992 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1994 config FB_SH_MOBILE_HDMI
1995 tristate "SuperH Mobile HDMI controller support"
1996 depends on FB_SH_MOBILE_LCDC
1997 select FB_MODE_HELPERS
2002 Driver for the on-chip SH-Mobile HDMI controller.
2005 tristate "Toshiba Mobile IO FrameBuffer support"
2006 depends on FB && (MFD_TMIO || COMPILE_TEST)
2007 select FB_CFB_FILLRECT
2008 select FB_CFB_COPYAREA
2009 select FB_CFB_IMAGEBLIT
2011 Frame buffer driver for the Toshiba Mobile IO integrated as found
2012 on the Sharp SL-6000 series
2014 This driver is also available as a module ( = code which can be
2015 inserted and removed from the running kernel whenever you want). The
2016 module will be called tmiofb. If you want to compile it as a module,
2017 say M here and read <file:Documentation/kbuild/modules.txt>.
2021 config FB_TMIO_ACCELL
2022 bool "tmiofb acceleration"
2027 tristate "Samsung S3C framebuffer support"
2028 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2029 ARCH_S5PV210 || ARCH_EXYNOS)
2030 select FB_CFB_FILLRECT
2031 select FB_CFB_COPYAREA
2032 select FB_CFB_IMAGEBLIT
2034 Frame buffer driver for the built-in FB controller in the Samsung
2035 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2036 and the S3C64XX series such as the S3C6400 and S3C6410.
2038 These chips all have the same basic framebuffer design with the
2039 actual capabilities depending on the chip. For instance the S3C6400
2040 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2041 currently only have two.
2043 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2045 config FB_S3C_DEBUG_REGWRITE
2046 bool "Debug register writes"
2049 Show all register writes via pr_debug()
2052 tristate "S3C2410 LCD framebuffer support"
2053 depends on FB && ARCH_S3C24XX
2054 select FB_CFB_FILLRECT
2055 select FB_CFB_COPYAREA
2056 select FB_CFB_IMAGEBLIT
2058 Frame buffer driver for the built-in LCD controller in the Samsung
2061 This driver is also available as a module ( = code which can be
2062 inserted and removed from the running kernel whenever you want). The
2063 module will be called s3c2410fb. If you want to compile it as a module,
2064 say M here and read <file:Documentation/kbuild/modules.txt>.
2067 config FB_S3C2410_DEBUG
2068 bool "S3C2410 lcd debug messages"
2069 depends on FB_S3C2410
2071 Turn on debugging messages. Note that you can set/unset at run time
2075 tristate "NUC900 LCD framebuffer support"
2076 depends on FB && ARCH_W90X900
2077 select FB_CFB_FILLRECT
2078 select FB_CFB_COPYAREA
2079 select FB_CFB_IMAGEBLIT
2081 Frame buffer driver for the built-in LCD controller in the Nuvoton
2084 config GPM1040A0_320X240
2085 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2086 depends on FB_NUC900
2089 tristate "Silicon Motion SM501 framebuffer support"
2090 depends on FB && MFD_SM501
2091 select FB_CFB_FILLRECT
2092 select FB_CFB_COPYAREA
2093 select FB_CFB_IMAGEBLIT
2095 Frame buffer driver for the CRT and LCD controllers in the Silicon
2098 This driver is also available as a module ( = code which can be
2099 inserted and removed from the running kernel whenever you want). The
2100 module will be called sm501fb. If you want to compile it as a module,
2101 say M here and read <file:Documentation/kbuild/modules.txt>.
2106 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2107 depends on FB && USB
2108 select FB_MODE_HELPERS
2109 select FB_SYS_FILLRECT
2110 select FB_SYS_COPYAREA
2111 select FB_SYS_IMAGEBLIT
2113 select FB_DEFERRED_IO
2115 This is a kernel framebuffer driver for SMSC UFX USB devices.
2116 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2117 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2119 To compile as a module, choose M here: the module name is smscufx.
2122 tristate "Displaylink USB Framebuffer support"
2123 depends on FB && USB
2124 select FB_MODE_HELPERS
2125 select FB_SYS_FILLRECT
2126 select FB_SYS_COPYAREA
2127 select FB_SYS_IMAGEBLIT
2129 select FB_DEFERRED_IO
2131 This is a kernel framebuffer driver for DisplayLink USB devices.
2132 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2133 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2134 To compile as a module, choose M here: the module name is udlfb.
2136 config FB_IBM_GXT4500
2137 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2138 depends on FB && PPC
2139 select FB_CFB_FILLRECT
2140 select FB_CFB_COPYAREA
2141 select FB_CFB_IMAGEBLIT
2143 Say Y here to enable support for the IBM GXT4000P/6000P and
2144 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2145 found on some IBM System P (pSeries) machines. This driver
2146 doesn't use Geometry Engine GT1000.
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
2155 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2157 Include support for the virtual frame buffer in the PS3 platform.
2159 config FB_PS3_DEFAULT_SIZE_M
2160 int "PS3 default frame buffer size (in MiB)"
2164 This is the default size (in MiB) of the virtual frame buffer in
2166 The default value can be overridden on the kernel command line
2167 using the "ps3fb" option (e.g. "ps3fb=9M");
2170 tristate "Xilinx frame buffer support"
2171 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2172 select FB_CFB_FILLRECT
2173 select FB_CFB_COPYAREA
2174 select FB_CFB_IMAGEBLIT
2176 Include support for the Xilinx ML300/ML403 reference design
2177 framebuffer. ML300 carries a 640*480 LCD display on the board,
2178 ML403 uses a standard DB15 VGA connector.
2181 tristate "Goldfish Framebuffer"
2182 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2183 select FB_CFB_FILLRECT
2184 select FB_CFB_COPYAREA
2185 select FB_CFB_IMAGEBLIT
2187 Framebuffer driver for Goldfish Virtual Platform
2190 tristate "Cobalt server LCD frame buffer support"
2191 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2194 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2195 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2196 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2197 select FB_CFB_FILLRECT
2198 select FB_CFB_COPYAREA
2199 select FB_CFB_IMAGEBLIT
2201 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2202 (D)STN/TFT LCD Controller.
2203 Supports display resolutions up to 1024x1024 pixel, grayscale and
2204 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2205 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2206 panels <= 320 pixel horizontal resolution.
2209 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2210 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2211 select FB_CFB_FILLRECT
2212 select FB_CFB_COPYAREA
2213 select FB_CFB_IMAGEBLIT
2214 select FB_CFB_REV_PIXELS_IN_BYTE
2215 select FB_MODE_HELPERS
2216 select VIDEOMODE_HELPERS
2218 This is the frame buffer device driver for the TI LCD controller
2219 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2223 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2225 select FB_SYS_FILLRECT
2226 select FB_SYS_COPYAREA
2227 select FB_SYS_IMAGEBLIT
2230 This is a `virtual' frame buffer device. It operates on a chunk of
2231 unswappable kernel memory instead of on the memory of a graphics
2232 board. This means you cannot see any output sent to this frame
2233 buffer device, while it does consume precious memory. The main use
2234 of this frame buffer device is testing and debugging the frame
2235 buffer subsystem. Do NOT enable it for normal systems! To protect
2236 the innocent, it has to be enabled explicitly at boot time using the
2237 kernel option `video=vfb:'.
2239 To compile this driver as a module, choose M here: the
2240 module will be called vfb. In order to load it, you must use
2241 the vfb_enable=1 option.
2245 config XEN_FBDEV_FRONTEND
2246 tristate "Xen virtual frame buffer support"
2247 depends on FB && XEN
2248 select FB_SYS_FILLRECT
2249 select FB_SYS_COPYAREA
2250 select FB_SYS_IMAGEBLIT
2252 select FB_DEFERRED_IO
2253 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2254 select XEN_XENBUS_FRONTEND
2257 This driver implements the front-end of the Xen virtual
2258 frame buffer driver. It communicates with a back-end
2262 tristate "E-Ink Metronome/8track controller support"
2264 select FB_SYS_FILLRECT
2265 select FB_SYS_COPYAREA
2266 select FB_SYS_IMAGEBLIT
2268 select FB_DEFERRED_IO
2270 This driver implements support for the E-Ink Metronome
2271 controller. The pre-release name for this device was 8track
2272 and could also have been called by some vendors as PVI-nnnn.
2275 tristate "Fujitsu MB862xx GDC support"
2277 depends on PCI || (OF && PPC)
2278 select FB_CFB_FILLRECT
2279 select FB_CFB_COPYAREA
2280 select FB_CFB_IMAGEBLIT
2282 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2285 prompt "GDC variant"
2286 depends on FB_MB862XX
2288 config FB_MB862XX_PCI_GDC
2289 bool "Carmine/Coral-P(A) GDC"
2292 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2293 PCI graphics controller devices.
2295 config FB_MB862XX_LIME
2297 depends on OF && PPC
2298 select FB_FOREIGN_ENDIAN
2299 select FB_LITTLE_ENDIAN
2301 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2305 config FB_MB862XX_I2C
2306 bool "Support I2C bus on MB862XX GDC"
2307 depends on FB_MB862XX && I2C
2308 depends on FB_MB862XX=m || I2C=y
2311 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2312 driver to support accessing I2C devices on controller's I2C bus.
2313 These are usually some video decoder chips.
2316 tristate "EP93XX frame buffer support"
2317 depends on FB && ARCH_EP93XX
2318 select FB_CFB_FILLRECT
2319 select FB_CFB_COPYAREA
2320 select FB_CFB_IMAGEBLIT
2322 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2323 This driver is also available as a module. The module will be called
2326 config FB_PRE_INIT_FB
2327 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2328 depends on FB && FB_MB862XX_LIME
2330 Select this option if display contents should be inherited as set by
2334 tristate "MSM Framebuffer support"
2335 depends on FB && ARCH_MSM
2336 select FB_CFB_FILLRECT
2337 select FB_CFB_COPYAREA
2338 select FB_CFB_IMAGEBLIT
2341 tristate "MX3 Framebuffer support"
2342 depends on FB && MX3_IPU
2343 select FB_CFB_FILLRECT
2344 select FB_CFB_COPYAREA
2345 select FB_CFB_IMAGEBLIT
2346 select BACKLIGHT_CLASS_DEVICE
2349 This is a framebuffer device for the i.MX31 LCD Controller. So
2350 far only synchronous displays are supported. If you plan to use
2351 an LCD display with your i.MX31 system, say Y here.
2353 config FB_BROADSHEET
2354 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2356 select FB_SYS_FILLRECT
2357 select FB_SYS_COPYAREA
2358 select FB_SYS_IMAGEBLIT
2360 select FB_DEFERRED_IO
2362 This driver implements support for the E-Ink Broadsheet
2363 controller. The release name for this device was Epson S1D13521
2364 and could also have been called by other names when coupled with
2368 tristate "AUO-K190X EPD controller support"
2370 select FB_SYS_FILLRECT
2371 select FB_SYS_COPYAREA
2372 select FB_SYS_IMAGEBLIT
2374 select FB_DEFERRED_IO
2376 Provides support for epaper controllers from the K190X series
2377 of AUO. These controllers can be used to drive epaper displays
2380 This option enables the common support, shared by the individual
2381 controller drivers. You will also have to enable the driver
2382 for the controller type used in your device.
2385 tristate "AUO-K1900 EPD controller support"
2386 depends on FB && FB_AUO_K190X
2388 This driver implements support for the AUO K1900 epd-controller.
2389 This controller can drive Sipix epaper displays but can only do
2390 serial updates, reducing the number of possible frames per second.
2393 tristate "AUO-K1901 EPD controller support"
2394 depends on FB && FB_AUO_K190X
2396 This driver implements support for the AUO K1901 epd-controller.
2397 This controller can drive Sipix epaper displays and supports
2398 concurrent updates, making higher frames per second possible.
2401 tristate "JZ4740 LCD framebuffer support"
2402 depends on FB && MACH_JZ4740
2403 select FB_SYS_FILLRECT
2404 select FB_SYS_COPYAREA
2405 select FB_SYS_IMAGEBLIT
2407 Framebuffer support for the JZ4740 SoC.
2410 tristate "MXS LCD framebuffer support"
2411 depends on FB && ARCH_MXS
2412 select FB_CFB_FILLRECT
2413 select FB_CFB_COPYAREA
2414 select FB_CFB_IMAGEBLIT
2415 select FB_MODE_HELPERS
2416 select VIDEOMODE_HELPERS
2418 Framebuffer support for the MXS SoC.
2420 config FB_PUV3_UNIGFX
2421 tristate "PKUnity v3 Unigfx framebuffer support"
2422 depends on FB && UNICORE32 && ARCH_PUV3
2423 select FB_SYS_FILLRECT
2424 select FB_SYS_COPYAREA
2425 select FB_SYS_IMAGEBLIT
2428 Choose this option if you want to use the Unigfx device as a
2429 framebuffer device. Without the support of PCI & AGP.
2432 tristate "Microsoft Hyper-V Synthetic Video support"
2433 depends on FB && HYPERV
2434 select FB_CFB_FILLRECT
2435 select FB_CFB_COPYAREA
2436 select FB_CFB_IMAGEBLIT
2438 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2441 bool "Simple framebuffer support"
2443 select FB_CFB_FILLRECT
2444 select FB_CFB_COPYAREA
2445 select FB_CFB_IMAGEBLIT
2447 Say Y if you want support for a simple frame-buffer.
2449 This driver assumes that the display hardware has been initialized
2450 before the kernel boots, and the kernel will simply render to the
2451 pre-allocated frame buffer surface.
2453 Configuration re: surface address, size, and format must be provided
2454 through device tree, or plain old platform data.
2456 source "drivers/video/fbdev/omap/Kconfig"
2457 source "drivers/video/fbdev/omap2/Kconfig"
2458 source "drivers/video/fbdev/exynos/Kconfig"
2459 source "drivers/video/fbdev/mmp/Kconfig"
2461 config FB_SH_MOBILE_MERAM
2462 tristate "SuperH Mobile MERAM read ahead support"
2463 depends on (SUPERH || ARCH_SHMOBILE)
2464 select GENERIC_ALLOCATOR
2466 Enable MERAM support for the SuperH controller.
2468 This will allow for caching of the framebuffer to provide more
2469 reliable access under heavy main memory bus traffic situations.
2470 Up to 4 memory channels can be configured, allowing 4 RGB or
2471 2 YCbCr framebuffers to be configured.
2474 tristate "Solomon SSD1307 framebuffer support"
2475 depends on FB && I2C
2479 select FB_SYS_FILLRECT
2480 select FB_SYS_COPYAREA
2481 select FB_SYS_IMAGEBLIT
2482 select FB_DEFERRED_IO
2485 This driver implements support for the Solomon SSD1307
2486 OLED controller over I2C.