6 tristate "Support for frame buffer devices"
9 The frame buffer device provides an abstraction for the graphics
10 hardware. It represents the frame buffer of some video hardware and
11 allows application software to access the graphics hardware through
12 a well-defined interface, so the software doesn't need to know
13 anything about the low-level (hardware register) stuff.
15 Frame buffer devices work identically across the different
16 architectures supported by Linux and make the implementation of
17 application programs easier and more portable; at this point, an X
18 server exists which uses the frame buffer device exclusively.
19 On several non-X86 architectures, the frame buffer device is the
20 only way to use the graphics hardware.
22 The device is accessed through special device nodes, usually located
23 in the /dev directory, i.e. /dev/fb*.
25 You need an utility program called fbset to make full use of frame
26 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
27 and the Framebuffer-HOWTO at
28 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
31 Say Y here and to the driver for your graphics board below if you
32 are compiling a kernel for a non-x86 architecture.
34 If you are compiling for the x86 architecture, you can say Y if you
35 want to play with it, but it is not essential. Please note that
36 running graphical applications that directly touch the hardware
37 (e.g. an accelerated X server) and that are not frame buffer
38 device-aware may cause unexpected results. If unsure, say N.
41 bool "Enable firmware EDID"
45 This enables access to the EDID transferred from the firmware.
46 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
47 transfers do not work for your driver and if you are using
48 nvidiafb, i810fb or savagefb.
50 In general, choosing Y for this option is safe. If you
51 experience extremely long delays while booting before you get
52 something on your display, try setting this to N. Matrox cards in
53 combination with certain motherboards and monitors are known to
54 suffer from this problem.
66 config FB_BOOT_VESA_SUPPORT
71 If true, at least one selected framebuffer driver can take advantage
72 of VESA video modes set at an early boot stage via the vga= parameter.
74 config FB_CFB_FILLRECT
79 Include the cfb_fillrect function for generic software rectangle
80 filling. This is used by drivers that don't provide their own
81 (accelerated) version.
83 config FB_CFB_COPYAREA
88 Include the cfb_copyarea function for generic software area copying.
89 This is used by drivers that don't provide their own (accelerated)
92 config FB_CFB_IMAGEBLIT
97 Include the cfb_imageblit function for generic software image
98 blitting. This is used by drivers that don't provide their own
99 (accelerated) version.
101 config FB_CFB_REV_PIXELS_IN_BYTE
106 Allow generic frame-buffer functions to work on displays with 1, 2
107 and 4 bits per pixel depths which has opposite order of pixels in
108 byte order to bytes in long order.
110 config FB_SYS_FILLRECT
115 Include the sys_fillrect function for generic software rectangle
116 filling. This is used by drivers that don't provide their own
117 (accelerated) version and the framebuffer is in system RAM.
119 config FB_SYS_COPYAREA
124 Include the sys_copyarea function for generic software area copying.
125 This is used by drivers that don't provide their own (accelerated)
126 version and the framebuffer is in system RAM.
128 config FB_SYS_IMAGEBLIT
133 Include the sys_imageblit function for generic software image
134 blitting. This is used by drivers that don't provide their own
135 (accelerated) version and the framebuffer is in system RAM.
137 menuconfig FB_FOREIGN_ENDIAN
138 bool "Framebuffer foreign endianness support"
141 This menu will let you enable support for the framebuffers with
142 non-native endianness (e.g. Little-Endian framebuffer on a
143 Big-Endian machine). Most probably you don't have such hardware,
144 so it's safe to say "n" here.
147 prompt "Choice endianness support"
148 depends on FB_FOREIGN_ENDIAN
150 config FB_BOTH_ENDIAN
151 bool "Support for Big- and Little-Endian framebuffers"
154 bool "Support for Big-Endian framebuffers only"
156 config FB_LITTLE_ENDIAN
157 bool "Support for Little-Endian framebuffers only"
166 config FB_DEFERRED_IO
173 depends on FB_DEFERRED_IO
180 Common utility functions useful to fbdev drivers of VGA-based
191 select BACKLIGHT_LCD_SUPPORT
192 select BACKLIGHT_CLASS_DEVICE
195 config FB_MODE_HELPERS
196 bool "Enable Video Mode Handling Helpers"
200 This enables functions for handling video modes using the
201 Generalized Timing Formula and the EDID parser. A few drivers rely
202 on this feature such as the radeonfb, rivafb, and the i810fb. If
203 your driver does not take advantage of this feature, choosing Y will
204 just increase the kernel size by about 5K.
206 config FB_TILEBLITTING
207 bool "Enable Tile Blitting Support"
211 This enables tile blitting. Tile blitting is a drawing technique
212 where the screen is divided into rectangular sections (tiles), whereas
213 the standard blitting divides the screen into pixels. Because the
214 default drawing element is a tile, drawing functions will be passed
215 parameters in terms of number of tiles instead of number of pixels.
216 For example, to draw a single character, instead of using bitmaps,
217 an index to an array of bitmaps will be used. To clear or move a
218 rectangular section of a screen, the rectangle will be described in
219 terms of number of tiles in the x- and y-axis.
221 This is particularly important to one driver, matroxfb. If
224 comment "Frame buffer hardware drivers"
228 tristate "Aeroflex Gaisler framebuffer support"
229 depends on FB && SPARC
230 select FB_CFB_FILLRECT
231 select FB_CFB_COPYAREA
232 select FB_CFB_IMAGEBLIT
234 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
237 tristate "Cirrus Logic support"
238 depends on FB && (ZORRO || PCI)
239 select FB_CFB_FILLRECT
240 select FB_CFB_COPYAREA
241 select FB_CFB_IMAGEBLIT
243 This enables support for Cirrus Logic GD542x/543x based boards on
244 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
246 If you have a PCI-based system, this enables support for these
247 chips: GD-543x, GD-544x, GD-5480.
249 Please read the file <file:Documentation/fb/cirrusfb.txt>.
251 Say N unless you have such a graphics board or plan to get one
252 before you next recompile the kernel.
255 tristate "Permedia2 support"
256 depends on FB && ((AMIGA && BROKEN) || PCI)
257 select FB_CFB_FILLRECT
258 select FB_CFB_COPYAREA
259 select FB_CFB_IMAGEBLIT
261 This is the frame buffer device driver for cards based on
262 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
263 The driver was tested on the following cards:
264 Diamond FireGL 1000 PRO AGP
265 ELSA Gloria Synergy PCI
266 Appian Jeronimo PRO (both heads) PCI
267 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
268 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
269 ASK Graphic Blaster Exxtreme AGP
271 To compile this driver as a module, choose M here: the
272 module will be called pm2fb.
274 config FB_PM2_FIFO_DISCONNECT
275 bool "enable FIFO disconnect feature"
276 depends on FB_PM2 && PCI
278 Support the Permedia2 FIFO disconnect feature.
281 tristate "ARM PrimeCell PL110 support"
282 depends on ARM || ARM64 || COMPILE_TEST
283 depends on FB && ARM_AMBA
284 select FB_CFB_FILLRECT
285 select FB_CFB_COPYAREA
286 select FB_CFB_IMAGEBLIT
287 select FB_MODE_HELPERS if OF
288 select VIDEOMODE_HELPERS if OF
290 This framebuffer device driver is for the ARM PrimeCell PL110
291 Colour LCD controller. ARM PrimeCells provide the building
292 blocks for System on a Chip devices.
294 If you want to compile this as a module (=code which can be
295 inserted into and removed from the running kernel), say M
296 here and read <file:Documentation/kbuild/modules.txt>. The module
297 will be called amba-clcd.
299 # Helper logic selected only by the ARM Versatile platform family.
300 config PLAT_VERSATILE_CLCD
301 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
303 depends on FB_ARMCLCD && FB=y
306 bool "Acorn VIDC support"
307 depends on (FB = y) && ARM && ARCH_ACORN
308 select FB_CFB_FILLRECT
309 select FB_CFB_COPYAREA
310 select FB_CFB_IMAGEBLIT
312 This is the frame buffer device driver for the Acorn VIDC graphics
313 hardware found in Acorn RISC PCs and other ARM-based machines. If
316 config FB_CLPS711X_OLD
318 select FB_CFB_FILLRECT
319 select FB_CFB_COPYAREA
320 select FB_CFB_IMAGEBLIT
323 tristate "CLPS711X LCD support"
324 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
325 select FB_CLPS711X_OLD if ARCH_CLPS711X && !ARCH_MULTIPLATFORM
326 select BACKLIGHT_LCD_SUPPORT
327 select FB_MODE_HELPERS
328 select FB_SYS_FILLRECT
329 select FB_SYS_COPYAREA
330 select FB_SYS_IMAGEBLIT
331 select LCD_CLASS_DEVICE
332 select VIDEOMODE_HELPERS
334 Say Y to enable the Framebuffer driver for the Cirrus Logic
338 bool "SA-1100 LCD support"
339 depends on (FB = y) && ARM && ARCH_SA1100
340 select FB_CFB_FILLRECT
341 select FB_CFB_COPYAREA
342 select FB_CFB_IMAGEBLIT
344 This is a framebuffer device for the SA-1100 LCD Controller.
345 See <http://www.linux-fbdev.org/> for information on framebuffer
348 If you plan to use the LCD display with your SA-1100 system, say
352 tristate "Freescale i.MX1/21/25/27 LCD support"
353 depends on FB && ARCH_MXC
354 select BACKLIGHT_LCD_SUPPORT
355 select LCD_CLASS_DEVICE
356 select FB_CFB_FILLRECT
357 select FB_CFB_COPYAREA
358 select FB_CFB_IMAGEBLIT
359 select FB_MODE_HELPERS
360 select VIDEOMODE_HELPERS
363 tristate "CyberPro 2000/2010/5000 support"
364 depends on FB && PCI && (BROKEN || !SPARC64)
365 select FB_CFB_FILLRECT
366 select FB_CFB_COPYAREA
367 select FB_CFB_IMAGEBLIT
369 This enables support for the Integraphics CyberPro 20x0 and 5000
370 VGA chips used in the Rebel.com Netwinder and other machines.
371 Say Y if you have a NetWinder or a graphics card containing this
372 device, otherwise say N.
374 config FB_CYBER2000_DDC
375 bool "DDC for CyberPro support"
376 depends on FB_CYBER2000
380 Say Y here if you want DDC support for your CyberPro graphics
381 card. This is only I2C bus support, driver does not use EDID.
383 config FB_CYBER2000_I2C
384 bool "CyberPro 2000/2010/5000 I2C support"
385 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
386 depends on I2C=y || FB_CYBER2000=m
389 Enable support for the I2C video decoder interface on the
390 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
391 on the Netwinder machines for the SAA7111 video capture.
395 depends on (FB = y) && APOLLO
397 select FB_CFB_FILLRECT
398 select FB_CFB_IMAGEBLIT
402 depends on (FB = y) && Q40
404 select FB_CFB_FILLRECT
405 select FB_CFB_COPYAREA
406 select FB_CFB_IMAGEBLIT
409 tristate "Amiga native chipset support"
410 depends on FB && AMIGA
412 This is the frame buffer device driver for the builtin graphics
413 chipset found in Amigas.
415 To compile this driver as a module, choose M here: the
416 module will be called amifb.
419 bool "Amiga OCS chipset support"
422 This enables support for the original Agnus and Denise video chips,
423 found in the Amiga 1000 and most A500's and A2000's. If you intend
424 to run Linux on any of these systems, say Y; otherwise say N.
427 bool "Amiga ECS chipset support"
430 This enables support for the Enhanced Chip Set, found in later
431 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
432 you intend to run Linux on any of these systems, say Y; otherwise
436 bool "Amiga AGA chipset support"
439 This enables support for the Advanced Graphics Architecture (also
440 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
441 and CD32. If you intend to run Linux on any of these systems, say Y;
445 bool "Amiga FrameMaster II/Rainbow II support"
446 depends on (FB = y) && ZORRO
447 select FB_CFB_FILLRECT
448 select FB_CFB_COPYAREA
449 select FB_CFB_IMAGEBLIT
451 This is the frame buffer device driver for the Amiga FrameMaster
452 card from BSC (exhibited 1992 but not shipped as a CBM product).
455 tristate "Arc Monochrome LCD board support"
457 select FB_SYS_FILLRECT
458 select FB_SYS_COPYAREA
459 select FB_SYS_IMAGEBLIT
462 This enables support for the Arc Monochrome LCD board. The board
463 is based on the KS-108 lcd controller and is typically a matrix
464 of 2*n chips. This driver was tested with a 128x64 panel. This
465 driver supports it for use with x86 SBCs through a 16 bit GPIO
466 interface (8 bit data, 8 bit control). If you anticipate using
467 this driver, say Y or M; otherwise say N. You must specify the
468 GPIO IO address to be used for setting control and data.
471 bool "Atari native chipset support"
472 depends on (FB = y) && ATARI
473 select FB_CFB_FILLRECT
474 select FB_CFB_COPYAREA
475 select FB_CFB_IMAGEBLIT
477 This is the frame buffer device driver for the builtin graphics
478 chipset found in Ataris.
481 bool "Open Firmware frame buffer device support"
482 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
483 select FB_CFB_FILLRECT
484 select FB_CFB_COPYAREA
485 select FB_CFB_IMAGEBLIT
488 Say Y if you want support with Open Firmware for your graphics
492 bool "Apple \"control\" display support"
493 depends on (FB = y) && PPC_PMAC && PPC32
494 select FB_CFB_FILLRECT
495 select FB_CFB_COPYAREA
496 select FB_CFB_IMAGEBLIT
499 This driver supports a frame buffer for the graphics adapter in the
500 Power Macintosh 7300 and others.
503 bool "Apple \"platinum\" display support"
504 depends on (FB = y) && PPC_PMAC && PPC32
505 select FB_CFB_FILLRECT
506 select FB_CFB_COPYAREA
507 select FB_CFB_IMAGEBLIT
510 This driver supports a frame buffer for the "platinum" graphics
511 adapter in some Power Macintoshes.
514 bool "Apple \"valkyrie\" display support"
515 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
516 select FB_CFB_FILLRECT
517 select FB_CFB_COPYAREA
518 select FB_CFB_IMAGEBLIT
521 This driver supports a frame buffer for the "valkyrie" graphics
522 adapter in some Power Macintoshes.
525 bool "Chips 65550 display support"
526 depends on (FB = y) && PPC32 && PCI
527 select FB_CFB_FILLRECT
528 select FB_CFB_COPYAREA
529 select FB_CFB_IMAGEBLIT
531 This is the frame buffer device driver for the Chips & Technologies
532 65550 graphics chip in PowerBooks.
535 bool "Asiliant (Chips) 69000 display support"
536 depends on (FB = y) && PCI
537 select FB_CFB_FILLRECT
538 select FB_CFB_COPYAREA
539 select FB_CFB_IMAGEBLIT
541 This is the frame buffer device driver for the Asiliant 69030 chipset
544 bool "IMS Twin Turbo display support"
545 depends on (FB = y) && PCI
546 select FB_CFB_IMAGEBLIT
547 select FB_MACMODES if PPC
549 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
550 many Macintosh and compatible computers.
553 tristate "VGA 16-color graphics support"
554 depends on FB && (X86 || PPC)
555 select FB_CFB_FILLRECT
556 select FB_CFB_COPYAREA
557 select FB_CFB_IMAGEBLIT
559 select FONT_8x16 if FRAMEBUFFER_CONSOLE
561 This is the frame buffer device driver for VGA 16 color graphic
562 cards. Say Y if you have such a card.
564 To compile this driver as a module, choose M here: the
565 module will be called vga16fb.
567 config FB_BF54X_LQ043
568 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
569 depends on FB && (BF54x) && !BF542
570 select FB_CFB_FILLRECT
571 select FB_CFB_COPYAREA
572 select FB_CFB_IMAGEBLIT
574 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
576 config FB_BFIN_T350MCQB
577 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
578 depends on FB && BLACKFIN
580 select FB_CFB_FILLRECT
581 select FB_CFB_COPYAREA
582 select FB_CFB_IMAGEBLIT
584 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
585 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
586 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
588 config FB_BFIN_LQ035Q1
589 tristate "SHARP LQ035Q1DH02 TFT LCD"
590 depends on FB && BLACKFIN && SPI
591 select FB_CFB_FILLRECT
592 select FB_CFB_COPYAREA
593 select FB_CFB_IMAGEBLIT
596 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
597 the Blackfin Landscape LCD EZ-Extender Card.
598 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
599 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
601 To compile this driver as a module, choose M here: the
602 module will be called bfin-lq035q1-fb.
604 config FB_BF537_LQ035
605 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
606 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
607 select FB_CFB_FILLRECT
608 select FB_CFB_COPYAREA
609 select FB_CFB_IMAGEBLIT
612 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
615 To compile this driver as a module, choose M here: the
616 module will be called bf537-lq035.
619 tristate "Blackfin ADV7393 Video encoder"
620 depends on FB && BLACKFIN
622 select FB_CFB_FILLRECT
623 select FB_CFB_COPYAREA
624 select FB_CFB_IMAGEBLIT
626 This is the framebuffer device for a ADV7393 video encoder
627 attached to a Blackfin on the PPI port.
628 If your Blackfin board has a ADV7393 select Y.
630 To compile this driver as a module, choose M here: the
631 module will be called bfin_adv7393fb.
634 prompt "Video mode support"
635 depends on FB_BFIN_7393
645 bool 'NTSC 640x480 (Experimental)'
648 bool 'PAL 640x480 (Experimental)'
651 bool 'NTSC 720x480 YCbCR input'
654 bool 'PAL 720x576 YCbCR input'
659 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
660 depends on (FB_BFIN_7393)
661 default ADV7393_1XMEM
671 tristate "HP STI frame buffer device support"
672 depends on FB && PARISC
673 select FB_CFB_FILLRECT
674 select FB_CFB_COPYAREA
675 select FB_CFB_IMAGEBLIT
680 STI refers to the HP "Standard Text Interface" which is a set of
681 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
682 Enabling this option will implement the linux framebuffer device
683 using calls to the STI BIOS routines for initialisation.
685 If you enable this option, you will get a planar framebuffer device
686 /dev/fb which will work on the most common HP graphic cards of the
687 NGLE family, including the artist chips (in the 7xx and Bxxx series),
688 HCRX, HCRX24, CRX, CRX24 and VisEG series.
690 It is safe to enable this option, so you should probably say "Y".
693 bool "Generic Macintosh display support"
694 depends on (FB = y) && MAC
695 select FB_CFB_FILLRECT
696 select FB_CFB_COPYAREA
697 select FB_CFB_IMAGEBLIT
702 depends on (FB = y) && DIO
703 select FB_CFB_IMAGEBLIT
707 tristate "TGA/SFB+ framebuffer support"
708 depends on FB && (ALPHA || TC)
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
714 This is the frame buffer device driver for generic TGA and SFB+
715 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
716 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
717 TURBOchannel cards, also known as PMAGD-A, -B and -C.
719 Due to hardware limitations ZLX-E2 and E3 cards are not supported
720 for DECstation 5000/200 systems. Additionally due to firmware
721 limitations these cards may cause troubles with booting DECstation
722 5000/240 and /260 systems, but are fully supported under Linux if
723 you manage to get it going. ;-)
725 Say Y if you have one of those.
728 tristate "Userspace VESA VGA graphics support"
729 depends on FB && CONNECTOR
730 select FB_CFB_FILLRECT
731 select FB_CFB_COPYAREA
732 select FB_CFB_IMAGEBLIT
733 select FB_MODE_HELPERS
735 This is the frame buffer driver for generic VBE 2.0 compliant
736 graphic cards. It can also take advantage of VBE 3.0 features,
737 such as refresh rate adjustment.
739 This driver generally provides more features than vesafb but
740 requires a userspace helper application called 'v86d'. See
741 <file:Documentation/fb/uvesafb.txt> for more information.
746 bool "VESA VGA graphics support"
747 depends on (FB = y) && X86
748 select FB_CFB_FILLRECT
749 select FB_CFB_COPYAREA
750 select FB_CFB_IMAGEBLIT
751 select FB_BOOT_VESA_SUPPORT
753 This is the frame buffer device driver for generic VESA 2.0
754 compliant graphic cards. The older VESA 1.2 cards are not supported.
755 You will get a boot time penguin logo at no additional cost. Please
756 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
759 bool "EFI-based Framebuffer Support"
760 depends on (FB = y) && X86 && EFI
761 select FB_CFB_FILLRECT
762 select FB_CFB_COPYAREA
763 select FB_CFB_IMAGEBLIT
765 This is the EFI frame buffer device driver. If the firmware on
766 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
767 using the EFI framebuffer as your console.
770 tristate "N411 Apollo/Hecuba devkit support"
771 depends on FB && X86 && MMU
772 select FB_SYS_FILLRECT
773 select FB_SYS_COPYAREA
774 select FB_SYS_IMAGEBLIT
776 select FB_DEFERRED_IO
779 This enables support for the Apollo display controller in its
780 Hecuba form using the n411 devkit.
783 tristate "Hercules mono graphics support"
786 Say Y here if you have a Hercules mono graphics card.
788 To compile this driver as a module, choose M here: the
789 module will be called hgafb.
791 As this card technology is at least 25 years old,
792 most people will answer N here.
795 bool "SGI Graphics Backend frame buffer support"
796 depends on (FB = y) && SGI_IP32
797 select FB_CFB_FILLRECT
798 select FB_CFB_COPYAREA
799 select FB_CFB_IMAGEBLIT
801 This is the frame buffer device driver for SGI Graphics Backend.
802 This chip is used in SGI O2 and Visual Workstation 320/540.
805 int "Video memory size in MB"
809 This is the amount of memory reserved for the framebuffer,
810 which can be any value between 1MB and 8MB.
813 bool "SBUS and UPA framebuffers"
814 depends on (FB = y) && SPARC
816 Say Y if you want support for SBUS or UPA based frame buffer device.
820 depends on (FB = y) && (SPARC && FB_SBUS)
821 select FB_CFB_FILLRECT
822 select FB_CFB_COPYAREA
823 select FB_CFB_IMAGEBLIT
825 This is the frame buffer device driver for the BWtwo frame buffer.
828 bool "CGthree support"
829 depends on (FB = y) && (SPARC && FB_SBUS)
830 select FB_CFB_FILLRECT
831 select FB_CFB_COPYAREA
832 select FB_CFB_IMAGEBLIT
834 This is the frame buffer device driver for the CGthree frame buffer.
837 bool "CGsix (GX,TurboGX) support"
838 depends on (FB = y) && (SPARC && FB_SBUS)
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 This is the frame buffer device driver for the CGsix (GX, TurboGX)
846 bool "Creator/Creator3D/Elite3D support"
847 depends on FB_SBUS && SPARC64
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 This is the frame buffer device driver for the Creator, Creator3D,
852 and Elite3D graphics boards.
855 bool "TCX (SS4/SS5 only) support"
857 select FB_CFB_FILLRECT
858 select FB_CFB_COPYAREA
859 select FB_CFB_IMAGEBLIT
861 This is the frame buffer device driver for the TCX 24/8bit frame
865 bool "CGfourteen (SX) support"
867 select FB_CFB_FILLRECT
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
871 This is the frame buffer device driver for the CGfourteen frame
872 buffer on Desktop SPARCsystems with the SX graphics option.
875 bool "P9100 (Sparcbook 3 only) support"
877 select FB_CFB_FILLRECT
878 select FB_CFB_COPYAREA
879 select FB_CFB_IMAGEBLIT
881 This is the frame buffer device driver for the P9100 card
882 supported on Sparcbook 3 machines.
885 bool "Leo (ZX) support"
887 select FB_CFB_FILLRECT
888 select FB_CFB_COPYAREA
889 select FB_CFB_IMAGEBLIT
891 This is the frame buffer device driver for the SBUS-based Sun ZX
892 (leo) frame buffer cards.
895 bool "IGA 168x display support"
896 depends on (FB = y) && SPARC32
897 select FB_CFB_FILLRECT
898 select FB_CFB_COPYAREA
899 select FB_CFB_IMAGEBLIT
901 This is the framebuffer device for the INTERGRAPHICS 1680 and
902 successor frame buffer cards.
905 bool "Sun XVR-500 3DLABS Wildcat support"
906 depends on (FB = y) && PCI && SPARC64
907 select FB_CFB_FILLRECT
908 select FB_CFB_COPYAREA
909 select FB_CFB_IMAGEBLIT
911 This is the framebuffer device for the Sun XVR-500 and similar
912 graphics cards based upon the 3DLABS Wildcat chipset. The driver
913 only works on sparc64 systems where the system firmware has
914 mostly initialized the card already. It is treated as a
915 completely dumb framebuffer device.
918 bool "Sun XVR-2500 3DLABS Wildcat support"
919 depends on (FB = y) && PCI && SPARC64
920 select FB_CFB_FILLRECT
921 select FB_CFB_COPYAREA
922 select FB_CFB_IMAGEBLIT
924 This is the framebuffer device for the Sun XVR-2500 and similar
925 graphics cards based upon the 3DLABS Wildcat chipset. The driver
926 only works on sparc64 systems where the system firmware has
927 mostly initialized the card already. It is treated as a
928 completely dumb framebuffer device.
931 bool "Sun XVR-1000 support"
932 depends on (FB = y) && SPARC64
933 select FB_CFB_FILLRECT
934 select FB_CFB_COPYAREA
935 select FB_CFB_IMAGEBLIT
937 This is the framebuffer device for the Sun XVR-1000 and similar
938 graphics cards. The driver only works on sparc64 systems where
939 the system firmware has mostly initialized the card already. It
940 is treated as a completely dumb framebuffer device.
943 tristate "NEC PowerVR 2 display support"
944 depends on FB && SH_DREAMCAST
945 select FB_CFB_FILLRECT
946 select FB_CFB_COPYAREA
947 select FB_CFB_IMAGEBLIT
949 Say Y here if you have a PowerVR 2 card in your box. If you plan to
950 run linux on your Dreamcast, you will have to say Y here.
951 This driver may or may not work on other PowerVR 2 cards, but is
952 totally untested. Use at your own risk. If unsure, say N.
954 To compile this driver as a module, choose M here: the
955 module will be called pvr2fb.
957 You can pass several parameters to the driver at boot time or at
958 module load time. The parameters look like "video=pvr2:XXX", where
959 the meaning of XXX can be found at the end of the main source file
960 (<file:drivers/video/pvr2fb.c>). Please see the file
961 <file:Documentation/fb/pvr2fb.txt>.
964 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
965 depends on FB && HAS_DMA
966 select FB_CFB_FILLRECT
967 select FB_CFB_COPYAREA
968 select FB_CFB_IMAGEBLIT
970 This enables support for the OpenCores VGA/LCD core.
972 The OpenCores VGA/LCD core is typically used together with
973 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
974 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
976 The source code and specification for the core is available at
977 <http://opencores.org/project,vga_lcd>
980 tristate "Epson S1D13XXX framebuffer support"
982 select FB_CFB_FILLRECT
983 select FB_CFB_COPYAREA
984 select FB_CFB_IMAGEBLIT
986 Support for S1D13XXX framebuffer device family (currently only
987 working with S1D13806). Product specs at
988 <http://vdc.epson.com/>
991 tristate "AT91/AT32 LCD Controller support"
992 depends on FB && HAVE_FB_ATMEL
994 select FB_CFB_FILLRECT
995 select FB_CFB_COPYAREA
996 select FB_CFB_IMAGEBLIT
997 select FB_MODE_HELPERS
998 select VIDEOMODE_HELPERS
1000 This enables support for the AT91/AT32 LCD Controller.
1003 tristate "nVidia Framebuffer Support"
1004 depends on FB && PCI
1005 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1006 select FB_MODE_HELPERS
1007 select FB_CFB_FILLRECT
1008 select FB_CFB_COPYAREA
1009 select FB_CFB_IMAGEBLIT
1013 This driver supports graphics boards with the nVidia chips, TNT
1014 and newer. For very old chipsets, such as the RIVA128, then use
1016 Say Y if you have such a graphics board.
1018 To compile this driver as a module, choose M here: the
1019 module will be called nvidiafb.
1021 config FB_NVIDIA_I2C
1022 bool "Enable DDC Support"
1023 depends on FB_NVIDIA
1026 This enables I2C support for nVidia Chipsets. This is used
1027 only for getting EDID information from the attached display
1028 allowing for robust video mode handling and switching.
1030 Because fbdev-2.6 requires that drivers must be able to
1031 independently validate video mode parameters, you should say Y
1034 config FB_NVIDIA_DEBUG
1035 bool "Lots of debug output"
1036 depends on FB_NVIDIA
1039 Say Y here if you want the nVidia driver to output all sorts
1040 of debugging information to provide to the maintainer when
1041 something goes wrong.
1043 config FB_NVIDIA_BACKLIGHT
1044 bool "Support for backlight control"
1045 depends on FB_NVIDIA
1048 Say Y here if you want to control the backlight of your display.
1051 tristate "nVidia Riva support"
1052 depends on FB && PCI
1053 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1054 select FB_MODE_HELPERS
1055 select FB_CFB_FILLRECT
1056 select FB_CFB_COPYAREA
1057 select FB_CFB_IMAGEBLIT
1061 This driver supports graphics boards with the nVidia Riva/Geforce
1063 Say Y if you have such a graphics board.
1065 To compile this driver as a module, choose M here: the
1066 module will be called rivafb.
1069 bool "Enable DDC Support"
1073 This enables I2C support for nVidia Chipsets. This is used
1074 only for getting EDID information from the attached display
1075 allowing for robust video mode handling and switching.
1077 Because fbdev-2.6 requires that drivers must be able to
1078 independently validate video mode parameters, you should say Y
1081 config FB_RIVA_DEBUG
1082 bool "Lots of debug output"
1086 Say Y here if you want the Riva driver to output all sorts
1087 of debugging information to provide to the maintainer when
1088 something goes wrong.
1090 config FB_RIVA_BACKLIGHT
1091 bool "Support for backlight control"
1095 Say Y here if you want to control the backlight of your display.
1098 tristate "Intel740 support"
1099 depends on FB && PCI
1100 select FB_MODE_HELPERS
1101 select FB_CFB_FILLRECT
1102 select FB_CFB_COPYAREA
1103 select FB_CFB_IMAGEBLIT
1107 This driver supports graphics cards based on Intel740 chip.
1110 tristate "Intel 810/815 support"
1111 depends on FB && PCI && X86_32 && AGP_INTEL
1112 select FB_MODE_HELPERS
1113 select FB_CFB_FILLRECT
1114 select FB_CFB_COPYAREA
1115 select FB_CFB_IMAGEBLIT
1118 This driver supports the on-board graphics built in to the Intel 810
1119 and 815 chipsets. Say Y if you have and plan to use such a board.
1121 To compile this driver as a module, choose M here: the
1122 module will be called i810fb.
1124 For more information, please read
1125 <file:Documentation/fb/intel810.txt>
1128 bool "use VESA Generalized Timing Formula"
1131 If you say Y, then the VESA standard, Generalized Timing Formula
1132 or GTF, will be used to calculate the required video timing values
1133 per video mode. Since the GTF allows nondiscrete timings
1134 (nondiscrete being a range of values as opposed to discrete being a
1135 set of values), you'll be able to use any combination of horizontal
1136 and vertical resolutions, and vertical refresh rates without having
1137 to specify your own timing parameters. This is especially useful
1138 to maximize the performance of an aging display, or if you just
1139 have a display with nonstandard dimensions. A VESA compliant
1140 monitor is recommended, but can still work with non-compliant ones.
1141 If you need or want this, then select this option. The timings may
1142 not be compliant with Intel's recommended values. Use at your own
1145 If you say N, the driver will revert to discrete video timings
1146 using a set recommended by Intel in their documentation.
1151 bool "Enable DDC Support"
1152 depends on FB_I810 && FB_I810_GTF
1157 tristate "Intel LE80578 (Vermilion) support"
1158 depends on FB && PCI && X86
1159 select FB_MODE_HELPERS
1160 select FB_CFB_FILLRECT
1161 select FB_CFB_COPYAREA
1162 select FB_CFB_IMAGEBLIT
1164 This driver supports the LE80578 (Vermilion Range) chipset
1166 config FB_CARILLO_RANCH
1167 tristate "Intel Carillo Ranch support"
1168 depends on FB_LE80578 && FB && PCI && X86
1170 This driver supports the LE80578 (Carillo Ranch) board
1173 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1174 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1175 select FB_MODE_HELPERS
1176 select FB_CFB_FILLRECT
1177 select FB_CFB_COPYAREA
1178 select FB_CFB_IMAGEBLIT
1179 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1180 depends on !DRM_I915
1182 This driver supports the on-board graphics built in to the Intel
1183 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1184 Say Y if you have and plan to use such a board.
1186 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1188 To compile this driver as a module, choose M here: the
1189 module will be called intelfb.
1191 For more information, please read <file:Documentation/fb/intelfb.txt>
1193 config FB_INTEL_DEBUG
1194 bool "Intel driver Debug Messages"
1197 Say Y here if you want the Intel driver to output all sorts
1198 of debugging information to provide to the maintainer when
1199 something goes wrong.
1202 bool "DDC/I2C for Intel framebuffer support"
1207 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1210 tristate "Matrox acceleration"
1211 depends on FB && PCI
1212 select FB_CFB_FILLRECT
1213 select FB_CFB_COPYAREA
1214 select FB_CFB_IMAGEBLIT
1215 select FB_TILEBLITTING
1216 select FB_MACMODES if PPC_PMAC
1218 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1219 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1220 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1221 Matrox G400, G450 or G550 card in your box.
1223 To compile this driver as a module, choose M here: the
1224 module will be called matroxfb.
1226 You can pass several parameters to the driver at boot time or at
1227 module load time. The parameters look like "video=matroxfb:XXX", and
1228 are described in <file:Documentation/fb/matroxfb.txt>.
1230 config FB_MATROX_MILLENIUM
1231 bool "Millennium I/II support"
1232 depends on FB_MATROX
1234 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1235 video card. If you select "Advanced lowlevel driver options" below,
1236 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1237 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1238 also use font widths different from 8.
1240 config FB_MATROX_MYSTIQUE
1241 bool "Mystique support"
1242 depends on FB_MATROX
1244 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1245 video card. If you select "Advanced lowlevel driver options" below,
1246 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1247 packed pixel and 32 bpp packed pixel. You can also use font widths
1251 bool "G100/G200/G400/G450/G550 support"
1252 depends on FB_MATROX
1254 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1255 video card. If you select "Advanced lowlevel driver options", you
1256 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1257 pixel and 32 bpp packed pixel. You can also use font widths
1260 If you need support for G400 secondary head, you must say Y to
1261 "Matrox I2C support" and "G400 second head support" right below.
1262 G450/G550 secondary head and digital output are supported without
1265 The driver starts in monitor mode. You must use the matroxset tool
1266 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1267 swap primary and secondary head outputs, or to change output mode.
1268 Secondary head driver always start in 640x480 resolution and you
1269 must use fbset to change it.
1271 Do not forget that second head supports only 16 and 32 bpp
1272 packed pixels, so it is a good idea to compile them into the kernel
1273 too. You can use only some font widths, as the driver uses generic
1274 painting procedures (the secondary head does not use acceleration
1277 G450/G550 hardware can display TV picture only from secondary CRTC,
1278 and it performs no scaling, so picture must have 525 or 625 lines.
1280 config FB_MATROX_I2C
1281 tristate "Matrox I2C support"
1282 depends on FB_MATROX
1285 This drivers creates I2C buses which are needed for accessing the
1286 DDC (I2C) bus present on all Matroxes, an I2C bus which
1287 interconnects Matrox optional devices, like MGA-TVO on G200 and
1288 G400, and the secondary head DDC bus, present on G400 only.
1290 You can say Y or M here if you want to experiment with monitor
1291 detection code. You must say Y or M here if you want to use either
1292 second head of G400 or MGA-TVO on G200 or G400.
1294 If you compile it as module, it will create a module named
1297 config FB_MATROX_MAVEN
1298 tristate "G400 second head support"
1299 depends on FB_MATROX_G && FB_MATROX_I2C
1301 WARNING !!! This support does not work with G450 !!!
1303 Say Y or M here if you want to use a secondary head (meaning two
1304 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1305 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1306 secondary head output is blanked while you are in X. With XFree
1307 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1308 the fbdev driver on first head and the fbdev driver on second head.
1310 If you compile it as module, two modules are created,
1311 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1312 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1313 also load i2c-matroxfb to get it to run.
1315 The driver starts in monitor mode and you must use the matroxset
1317 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1318 PAL or NTSC or to swap primary and secondary head outputs.
1319 Secondary head driver also always start in 640x480 resolution, you
1320 must use fbset to change it.
1322 Also do not forget that second head supports only 16 and 32 bpp
1323 packed pixels, so it is a good idea to compile them into the kernel
1324 too. You can use only some font widths, as the driver uses generic
1325 painting procedures (the secondary head does not use acceleration
1329 tristate "ATI Radeon display support"
1330 depends on FB && PCI
1331 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1332 select FB_MODE_HELPERS
1333 select FB_CFB_FILLRECT
1334 select FB_CFB_COPYAREA
1335 select FB_CFB_IMAGEBLIT
1336 select FB_MACMODES if PPC
1338 Choose this option if you want to use an ATI Radeon graphics card as
1339 a framebuffer device. There are both PCI and AGP versions. You
1340 don't need to choose this to run the Radeon in plain VGA mode.
1342 There is a product page at
1343 http://products.amd.com/en-us/GraphicCardResult.aspx
1345 config FB_RADEON_I2C
1346 bool "DDC/I2C for ATI Radeon support"
1347 depends on FB_RADEON
1351 Say Y here if you want DDC/I2C support for your Radeon board.
1353 config FB_RADEON_BACKLIGHT
1354 bool "Support for backlight control"
1355 depends on FB_RADEON
1358 Say Y here if you want to control the backlight of your display.
1360 config FB_RADEON_DEBUG
1361 bool "Lots of debug output from Radeon driver"
1362 depends on FB_RADEON
1365 Say Y here if you want the Radeon driver to output all sorts
1366 of debugging information to provide to the maintainer when
1367 something goes wrong.
1370 tristate "ATI Rage128 display support"
1371 depends on FB && PCI
1372 select FB_CFB_FILLRECT
1373 select FB_CFB_COPYAREA
1374 select FB_CFB_IMAGEBLIT
1375 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1376 select FB_MACMODES if PPC_PMAC
1378 This driver supports graphics boards with the ATI Rage128 chips.
1379 Say Y if you have such a graphics board and read
1380 <file:Documentation/fb/aty128fb.txt>.
1382 To compile this driver as a module, choose M here: the
1383 module will be called aty128fb.
1385 config FB_ATY128_BACKLIGHT
1386 bool "Support for backlight control"
1387 depends on FB_ATY128
1390 Say Y here if you want to control the backlight of your display.
1393 tristate "ATI Mach64 display support" if PCI || ATARI
1394 depends on FB && !SPARC32
1395 select FB_CFB_FILLRECT
1396 select FB_CFB_COPYAREA
1397 select FB_CFB_IMAGEBLIT
1398 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1399 select FB_MACMODES if PPC
1401 This driver supports graphics boards with the ATI Mach64 chips.
1402 Say Y if you have such a graphics board.
1404 To compile this driver as a module, choose M here: the
1405 module will be called atyfb.
1408 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1409 depends on PCI && FB_ATY
1410 default y if SPARC64 && PCI
1412 Say Y here to support use of ATI's 64-bit Rage boards (or other
1413 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1414 framebuffer device. The ATI product support page for these boards
1415 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1417 config FB_ATY_GENERIC_LCD
1418 bool "Mach64 generic LCD support"
1419 depends on FB_ATY_CT
1421 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1422 Rage XC, or Rage XL chipset.
1425 bool "Mach64 GX support" if PCI
1429 Say Y here to support use of the ATI Mach64 Graphics Expression
1430 board (or other boards based on the Mach64 GX chipset) as a
1431 framebuffer device. The ATI product support page for these boards
1433 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1435 config FB_ATY_BACKLIGHT
1436 bool "Support for backlight control"
1440 Say Y here if you want to control the backlight of your display.
1443 tristate "S3 Trio/Virge support"
1444 depends on FB && PCI
1445 select FB_CFB_FILLRECT
1446 select FB_CFB_COPYAREA
1447 select FB_CFB_IMAGEBLIT
1448 select FB_TILEBLITTING
1451 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1453 Driver for graphics boards with S3 Trio / S3 Virge chip.
1456 bool "DDC for S3 support"
1461 Say Y here if you want DDC support for your S3 graphics card.
1464 tristate "S3 Savage support"
1465 depends on FB && PCI
1466 select FB_MODE_HELPERS
1467 select FB_CFB_FILLRECT
1468 select FB_CFB_COPYAREA
1469 select FB_CFB_IMAGEBLIT
1472 This driver supports notebooks and computers with S3 Savage PCI/AGP
1475 Say Y if you have such a graphics card.
1477 To compile this driver as a module, choose M here; the module
1478 will be called savagefb.
1480 config FB_SAVAGE_I2C
1481 bool "Enable DDC2 Support"
1482 depends on FB_SAVAGE
1485 This enables I2C support for S3 Savage Chipsets. This is used
1486 only for getting EDID information from the attached display
1487 allowing for robust video mode handling and switching.
1489 Because fbdev-2.6 requires that drivers must be able to
1490 independently validate video mode parameters, you should say Y
1493 config FB_SAVAGE_ACCEL
1494 bool "Enable Console Acceleration"
1495 depends on FB_SAVAGE
1498 This option will compile in console acceleration support. If
1499 the resulting framebuffer console has bothersome glitches, then
1503 tristate "SiS/XGI display support"
1504 depends on FB && PCI
1505 select FB_CFB_FILLRECT
1506 select FB_CFB_COPYAREA
1507 select FB_CFB_IMAGEBLIT
1508 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1510 This is the frame buffer device driver for the SiS 300, 315, 330
1511 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1512 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1514 To compile this driver as a module, choose M here; the module
1515 will be called sisfb.
1518 bool "SiS 300 series support"
1521 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1524 bool "SiS 315/330/340 series and XGI support"
1527 Say Y here to support use of the SiS 315, 330 and 340 series
1528 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1529 as XGI V3XT, V5, V8 and Z7.
1532 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1533 depends on FB && PCI && X86 && GPIOLIB && I2C
1534 select FB_CFB_FILLRECT
1535 select FB_CFB_COPYAREA
1536 select FB_CFB_IMAGEBLIT
1539 This is the frame buffer device driver for Graphics chips of VIA
1540 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1541 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1543 Say Y if you have a VIA UniChrome graphics board.
1545 To compile this driver as a module, choose M here: the
1546 module will be called viafb.
1550 config FB_VIA_DIRECT_PROCFS
1551 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1555 Allow direct hardware access to some output registers via procfs.
1556 This is dangerous but may provide the only chance to get the
1557 correct output device configuration.
1558 Its use is strongly discouraged.
1560 config FB_VIA_X_COMPATIBILITY
1561 bool "X server compatibility"
1565 This option reduces the functionality (power saving, ...) of the
1566 framebuffer to avoid negative impact on the OpenChrome X server.
1567 If you use any X server other than fbdev you should enable this
1568 otherwise it should be safe to disable it and allow using all
1574 tristate "NeoMagic display support"
1575 depends on FB && PCI
1576 select FB_MODE_HELPERS
1577 select FB_CFB_FILLRECT
1578 select FB_CFB_COPYAREA
1579 select FB_CFB_IMAGEBLIT
1582 This driver supports notebooks with NeoMagic PCI chips.
1583 Say Y if you have such a graphics card.
1585 To compile this driver as a module, choose M here: the
1586 module will be called neofb.
1589 tristate "IMG Kyro support"
1590 depends on FB && PCI
1591 select FB_CFB_FILLRECT
1592 select FB_CFB_COPYAREA
1593 select FB_CFB_IMAGEBLIT
1595 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1598 To compile this driver as a module, choose M here: the
1599 module will be called kyrofb.
1602 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1603 depends on FB && PCI
1604 select FB_CFB_IMAGEBLIT
1605 select FB_CFB_FILLRECT
1606 select FB_CFB_COPYAREA
1607 select FB_MODE_HELPERS
1609 This driver supports graphics boards with the 3Dfx Banshee,
1610 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1611 such a graphics board.
1613 To compile this driver as a module, choose M here: the
1614 module will be called tdfxfb.
1616 config FB_3DFX_ACCEL
1617 bool "3Dfx Acceleration functions"
1620 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1621 device driver with acceleration functions.
1624 bool "Enable DDC/I2C support"
1629 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1632 tristate "3Dfx Voodoo Graphics (sst1) support"
1633 depends on FB && PCI
1634 select FB_CFB_FILLRECT
1635 select FB_CFB_COPYAREA
1636 select FB_CFB_IMAGEBLIT
1638 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1639 Voodoo2 (cvg) based graphics card.
1641 To compile this driver as a module, choose M here: the
1642 module will be called sstfb.
1644 WARNING: Do not use any application that uses the 3D engine
1645 (namely glide) while using this driver.
1646 Please read the <file:Documentation/fb/sstfb.txt> for supported
1647 options and other important info support.
1650 tristate "VIA VT8623 support"
1651 depends on FB && PCI
1652 select FB_CFB_FILLRECT
1653 select FB_CFB_COPYAREA
1654 select FB_CFB_IMAGEBLIT
1655 select FB_TILEBLITTING
1658 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1660 Driver for CastleRock integrated graphics core in the
1661 VIA VT8623 [Apollo CLE266] chipset.
1664 tristate "Trident/CyberXXX/CyberBlade support"
1665 depends on FB && PCI
1666 select FB_CFB_FILLRECT
1667 select FB_CFB_COPYAREA
1668 select FB_CFB_IMAGEBLIT
1670 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1671 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1673 There are also integrated versions of these chips called CyberXXXX,
1674 CyberImage or CyberBlade. These chips are mostly found in laptops
1675 but also on some motherboards including early VIA EPIA motherboards.
1676 For more information, read <file:Documentation/fb/tridentfb.txt>
1678 Say Y if you have such a graphics board.
1680 To compile this driver as a module, choose M here: the
1681 module will be called tridentfb.
1684 tristate "ARK 2000PV support"
1685 depends on FB && PCI
1686 select FB_CFB_FILLRECT
1687 select FB_CFB_COPYAREA
1688 select FB_CFB_IMAGEBLIT
1689 select FB_TILEBLITTING
1692 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1694 Driver for PCI graphics boards with ARK 2000PV chip
1695 and ICS 5342 RAMDAC.
1698 tristate "Permedia3 support"
1699 depends on FB && PCI
1700 select FB_CFB_FILLRECT
1701 select FB_CFB_COPYAREA
1702 select FB_CFB_IMAGEBLIT
1704 This is the frame buffer device driver for the 3DLabs Permedia3
1705 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1706 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1707 and maybe other boards.
1710 tristate "Fujitsu carmine frame buffer support"
1711 depends on FB && PCI
1712 select FB_CFB_FILLRECT
1713 select FB_CFB_COPYAREA
1714 select FB_CFB_IMAGEBLIT
1716 This is the frame buffer device driver for the Fujitsu Carmine chip.
1717 The driver provides two independent frame buffer devices.
1720 depends on FB_CARMINE
1721 prompt "DRAM timing"
1722 default FB_CARMINE_DRAM_EVAL
1724 config FB_CARMINE_DRAM_EVAL
1725 bool "Eval board timings"
1727 Use timings which work on the eval card.
1729 config CARMINE_DRAM_CUSTOM
1730 bool "Custom board timings"
1732 Use custom board timings.
1736 bool "Au1100 LCD Driver"
1737 depends on (FB = y) && MIPS_ALCHEMY
1738 select FB_CFB_FILLRECT
1739 select FB_CFB_COPYAREA
1740 select FB_CFB_IMAGEBLIT
1742 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1743 various panels and CRTs by passing in kernel cmd line option
1744 au1100fb:panel=<name>.
1747 bool "Au1200/Au1300 LCD Driver"
1748 depends on (FB = y) && MIPS_ALCHEMY
1749 select FB_SYS_FILLRECT
1750 select FB_SYS_COPYAREA
1751 select FB_SYS_IMAGEBLIT
1754 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1755 It can drive various panels and CRTs by passing in kernel cmd line
1756 option au1200fb:panel=<name>.
1759 bool "VIA VT8500 framebuffer support"
1760 depends on (FB = y) && ARM && ARCH_VT8500
1761 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1762 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1763 select FB_SYS_IMAGEBLIT
1764 select FB_MODE_HELPERS
1765 select VIDEOMODE_HELPERS
1767 This is the framebuffer driver for VIA VT8500 integrated LCD
1771 bool "Wondermedia WM8xxx-series frame buffer support"
1772 depends on (FB = y) && ARM && ARCH_VT8500
1773 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1774 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1775 select FB_SYS_IMAGEBLIT
1776 select FB_MODE_HELPERS
1777 select VIDEOMODE_HELPERS
1779 This is the framebuffer driver for WonderMedia WM8xxx-series
1780 integrated LCD controller. This driver covers the WM8505, WM8650
1783 config FB_WMT_GE_ROPS
1784 bool "VT8500/WM8xxx accelerated raster ops support"
1785 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1788 This adds support for accelerated raster operations on the
1789 VIA VT8500 and Wondermedia 85xx series SoCs.
1791 source "drivers/video/fbdev/geode/Kconfig"
1794 tristate "HD64461 Frame Buffer support"
1795 depends on FB && HD64461
1796 select FB_CFB_FILLRECT
1797 select FB_CFB_COPYAREA
1798 select FB_CFB_IMAGEBLIT
1800 This is the frame buffer device driver for the Hitachi HD64461 LCD
1804 bool "PMAG-AA TURBOchannel framebuffer support"
1805 depends on (FB = y) && TC
1806 select FB_CFB_FILLRECT
1807 select FB_CFB_COPYAREA
1808 select FB_CFB_IMAGEBLIT
1810 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1811 used mainly in the MIPS-based DECstation series.
1814 tristate "PMAG-BA TURBOchannel framebuffer support"
1816 select FB_CFB_FILLRECT
1817 select FB_CFB_COPYAREA
1818 select FB_CFB_IMAGEBLIT
1820 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1821 used mainly in the MIPS-based DECstation series.
1824 tristate "PMAGB-B TURBOchannel framebuffer support"
1826 select FB_CFB_FILLRECT
1827 select FB_CFB_COPYAREA
1828 select FB_CFB_IMAGEBLIT
1830 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1831 in the MIPS-based DECstation series. The card is currently only
1832 supported in 1280x1024x8 mode.
1835 bool "Maxine (Personal DECstation) onboard framebuffer support"
1836 depends on (FB = y) && MACH_DECSTATION
1837 select FB_CFB_FILLRECT
1838 select FB_CFB_COPYAREA
1839 select FB_CFB_IMAGEBLIT
1841 Support for the onboard framebuffer (1024x768x8) in the Personal
1842 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1846 bool "G364 frame buffer support"
1847 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1848 select FB_CFB_FILLRECT
1849 select FB_CFB_COPYAREA
1850 select FB_CFB_IMAGEBLIT
1852 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1853 Olivetti M700-10 systems.
1856 bool "Motorola 68328 native frame buffer support"
1857 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1858 select FB_CFB_FILLRECT
1859 select FB_CFB_COPYAREA
1860 select FB_CFB_IMAGEBLIT
1862 Say Y here if you want to support the built-in frame buffer of
1863 the Motorola 68328 CPU family.
1866 tristate "PXA168/910 LCD framebuffer support"
1867 depends on FB && (CPU_PXA168 || CPU_PXA910)
1868 select FB_CFB_FILLRECT
1869 select FB_CFB_COPYAREA
1870 select FB_CFB_IMAGEBLIT
1872 Frame buffer driver for the built-in LCD controller in the Marvell
1876 tristate "PXA LCD framebuffer support"
1877 depends on FB && ARCH_PXA
1878 select FB_CFB_FILLRECT
1879 select FB_CFB_COPYAREA
1880 select FB_CFB_IMAGEBLIT
1882 Frame buffer driver for the built-in LCD controller in the Intel
1885 This driver is also available as a module ( = code which can be
1886 inserted and removed from the running kernel whenever you want). The
1887 module will be called pxafb. If you want to compile it as a module,
1888 say M here and read <file:Documentation/kbuild/modules.txt>.
1892 config FB_PXA_OVERLAY
1893 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1895 depends on FB_PXA && (PXA27x || PXA3xx)
1897 config FB_PXA_SMARTPANEL
1898 bool "PXA Smartpanel LCD support"
1902 config FB_PXA_PARAMETERS
1903 bool "PXA LCD command line parameters"
1907 Enable the use of kernel command line or module parameters
1908 to configure the physical properties of the LCD panel when
1909 using the PXA LCD driver.
1911 This option allows you to override the panel parameters
1912 supplied by the platform in order to support multiple
1913 different models of flatpanel. If you will only be using a
1914 single model of flatpanel then you can safely leave this
1917 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1920 tristate "PXA3xx 2D graphics accelerator driver"
1923 Kernelspace driver for the 2D graphics controller unit (GCU)
1924 found on PXA3xx processors. There is a counterpart driver in the
1925 DirectFB suite, see http://www.directfb.org/
1927 If you compile this as a module, it will be called pxa3xx_gcu.
1930 tristate "2700G LCD framebuffer support"
1931 depends on FB && ARCH_PXA
1932 select FB_CFB_FILLRECT
1933 select FB_CFB_COPYAREA
1934 select FB_CFB_IMAGEBLIT
1936 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1940 bool "Enable debugging info via debugfs"
1941 depends on FB_MBX && DEBUG_FS
1944 Enable this if you want debugging information using the debug
1945 filesystem (debugfs)
1950 tristate "Freescale DIU framebuffer support"
1951 depends on FB && FSL_SOC
1952 select FB_MODE_HELPERS
1953 select FB_CFB_FILLRECT
1954 select FB_CFB_COPYAREA
1955 select FB_CFB_IMAGEBLIT
1956 select PPC_LIB_RHEAP
1958 Framebuffer driver for the Freescale SoC DIU
1961 tristate "W100 frame buffer support"
1962 depends on FB && ARCH_PXA
1963 select FB_CFB_FILLRECT
1964 select FB_CFB_COPYAREA
1965 select FB_CFB_IMAGEBLIT
1967 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1968 It can also drive the w3220 chip found on iPAQ hx4700.
1970 This driver is also available as a module ( = code which can be
1971 inserted and removed from the running kernel whenever you want). The
1972 module will be called w100fb. If you want to compile it as a module,
1973 say M here and read <file:Documentation/kbuild/modules.txt>.
1977 config FB_SH_MOBILE_LCDC
1978 tristate "SuperH Mobile LCDC framebuffer support"
1979 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1980 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1981 select FB_SYS_FILLRECT
1982 select FB_SYS_COPYAREA
1983 select FB_SYS_IMAGEBLIT
1985 select FB_DEFERRED_IO
1987 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1989 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1991 config FB_SH_MOBILE_HDMI
1992 tristate "SuperH Mobile HDMI controller support"
1993 depends on FB_SH_MOBILE_LCDC
1994 select FB_MODE_HELPERS
1999 Driver for the on-chip SH-Mobile HDMI controller.
2002 tristate "Toshiba Mobile IO FrameBuffer support"
2003 depends on FB && (MFD_TMIO || COMPILE_TEST)
2004 select FB_CFB_FILLRECT
2005 select FB_CFB_COPYAREA
2006 select FB_CFB_IMAGEBLIT
2008 Frame buffer driver for the Toshiba Mobile IO integrated as found
2009 on the Sharp SL-6000 series
2011 This driver is also available as a module ( = code which can be
2012 inserted and removed from the running kernel whenever you want). The
2013 module will be called tmiofb. If you want to compile it as a module,
2014 say M here and read <file:Documentation/kbuild/modules.txt>.
2018 config FB_TMIO_ACCELL
2019 bool "tmiofb acceleration"
2024 tristate "Samsung S3C framebuffer support"
2025 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2026 ARCH_S5PV210 || ARCH_EXYNOS)
2027 select FB_CFB_FILLRECT
2028 select FB_CFB_COPYAREA
2029 select FB_CFB_IMAGEBLIT
2031 Frame buffer driver for the built-in FB controller in the Samsung
2032 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2033 and the S3C64XX series such as the S3C6400 and S3C6410.
2035 These chips all have the same basic framebuffer design with the
2036 actual capabilities depending on the chip. For instance the S3C6400
2037 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2038 currently only have two.
2040 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2042 config FB_S3C_DEBUG_REGWRITE
2043 bool "Debug register writes"
2046 Show all register writes via pr_debug()
2049 tristate "S3C2410 LCD framebuffer support"
2050 depends on FB && ARCH_S3C24XX
2051 select FB_CFB_FILLRECT
2052 select FB_CFB_COPYAREA
2053 select FB_CFB_IMAGEBLIT
2055 Frame buffer driver for the built-in LCD controller in the Samsung
2058 This driver is also available as a module ( = code which can be
2059 inserted and removed from the running kernel whenever you want). The
2060 module will be called s3c2410fb. If you want to compile it as a module,
2061 say M here and read <file:Documentation/kbuild/modules.txt>.
2064 config FB_S3C2410_DEBUG
2065 bool "S3C2410 lcd debug messages"
2066 depends on FB_S3C2410
2068 Turn on debugging messages. Note that you can set/unset at run time
2072 tristate "NUC900 LCD framebuffer support"
2073 depends on FB && ARCH_W90X900
2074 select FB_CFB_FILLRECT
2075 select FB_CFB_COPYAREA
2076 select FB_CFB_IMAGEBLIT
2078 Frame buffer driver for the built-in LCD controller in the Nuvoton
2081 config GPM1040A0_320X240
2082 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2083 depends on FB_NUC900
2086 tristate "Silicon Motion SM501 framebuffer support"
2087 depends on FB && MFD_SM501
2088 select FB_CFB_FILLRECT
2089 select FB_CFB_COPYAREA
2090 select FB_CFB_IMAGEBLIT
2092 Frame buffer driver for the CRT and LCD controllers in the Silicon
2095 This driver is also available as a module ( = code which can be
2096 inserted and removed from the running kernel whenever you want). The
2097 module will be called sm501fb. If you want to compile it as a module,
2098 say M here and read <file:Documentation/kbuild/modules.txt>.
2103 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2104 depends on FB && USB
2105 select FB_MODE_HELPERS
2106 select FB_SYS_FILLRECT
2107 select FB_SYS_COPYAREA
2108 select FB_SYS_IMAGEBLIT
2110 select FB_DEFERRED_IO
2112 This is a kernel framebuffer driver for SMSC UFX USB devices.
2113 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2114 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2116 To compile as a module, choose M here: the module name is smscufx.
2119 tristate "Displaylink USB Framebuffer support"
2120 depends on FB && USB
2121 select FB_MODE_HELPERS
2122 select FB_SYS_FILLRECT
2123 select FB_SYS_COPYAREA
2124 select FB_SYS_IMAGEBLIT
2126 select FB_DEFERRED_IO
2128 This is a kernel framebuffer driver for DisplayLink USB devices.
2129 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2130 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2131 To compile as a module, choose M here: the module name is udlfb.
2133 config FB_IBM_GXT4500
2134 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2135 depends on FB && PPC
2136 select FB_CFB_FILLRECT
2137 select FB_CFB_COPYAREA
2138 select FB_CFB_IMAGEBLIT
2140 Say Y here to enable support for the IBM GXT4000P/6000P and
2141 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2142 found on some IBM System P (pSeries) machines. This driver
2143 doesn't use Geometry Engine GT1000.
2146 tristate "PS3 GPU framebuffer driver"
2147 depends on FB && PS3_PS3AV
2148 select FB_SYS_FILLRECT
2149 select FB_SYS_COPYAREA
2150 select FB_SYS_IMAGEBLIT
2153 Include support for the virtual frame buffer in the PS3 platform.
2155 config FB_PS3_DEFAULT_SIZE_M
2156 int "PS3 default frame buffer size (in MiB)"
2160 This is the default size (in MiB) of the virtual frame buffer in
2162 The default value can be overridden on the kernel command line
2163 using the "ps3fb" option (e.g. "ps3fb=9M");
2166 tristate "Xilinx frame buffer support"
2167 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2168 select FB_CFB_FILLRECT
2169 select FB_CFB_COPYAREA
2170 select FB_CFB_IMAGEBLIT
2172 Include support for the Xilinx ML300/ML403 reference design
2173 framebuffer. ML300 carries a 640*480 LCD display on the board,
2174 ML403 uses a standard DB15 VGA connector.
2177 tristate "Goldfish Framebuffer"
2178 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2179 select FB_CFB_FILLRECT
2180 select FB_CFB_COPYAREA
2181 select FB_CFB_IMAGEBLIT
2183 Framebuffer driver for Goldfish Virtual Platform
2186 tristate "Cobalt server LCD frame buffer support"
2187 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2190 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2191 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2192 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2193 select FB_CFB_FILLRECT
2194 select FB_CFB_COPYAREA
2195 select FB_CFB_IMAGEBLIT
2197 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2198 (D)STN/TFT LCD Controller.
2199 Supports display resolutions up to 1024x1024 pixel, grayscale and
2200 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2201 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2202 panels <= 320 pixel horizontal resolution.
2205 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2206 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2207 select FB_CFB_FILLRECT
2208 select FB_CFB_COPYAREA
2209 select FB_CFB_IMAGEBLIT
2210 select FB_CFB_REV_PIXELS_IN_BYTE
2211 select FB_MODE_HELPERS
2212 select VIDEOMODE_HELPERS
2214 This is the frame buffer device driver for the TI LCD controller
2215 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2219 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2221 select FB_SYS_FILLRECT
2222 select FB_SYS_COPYAREA
2223 select FB_SYS_IMAGEBLIT
2226 This is a `virtual' frame buffer device. It operates on a chunk of
2227 unswappable kernel memory instead of on the memory of a graphics
2228 board. This means you cannot see any output sent to this frame
2229 buffer device, while it does consume precious memory. The main use
2230 of this frame buffer device is testing and debugging the frame
2231 buffer subsystem. Do NOT enable it for normal systems! To protect
2232 the innocent, it has to be enabled explicitly at boot time using the
2233 kernel option `video=vfb:'.
2235 To compile this driver as a module, choose M here: the
2236 module will be called vfb. In order to load it, you must use
2237 the vfb_enable=1 option.
2241 config XEN_FBDEV_FRONTEND
2242 tristate "Xen virtual frame buffer support"
2243 depends on FB && XEN
2244 select FB_SYS_FILLRECT
2245 select FB_SYS_COPYAREA
2246 select FB_SYS_IMAGEBLIT
2248 select FB_DEFERRED_IO
2249 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2250 select XEN_XENBUS_FRONTEND
2253 This driver implements the front-end of the Xen virtual
2254 frame buffer driver. It communicates with a back-end
2258 tristate "E-Ink Metronome/8track controller support"
2260 select FB_SYS_FILLRECT
2261 select FB_SYS_COPYAREA
2262 select FB_SYS_IMAGEBLIT
2264 select FB_DEFERRED_IO
2266 This driver implements support for the E-Ink Metronome
2267 controller. The pre-release name for this device was 8track
2268 and could also have been called by some vendors as PVI-nnnn.
2271 tristate "Fujitsu MB862xx GDC support"
2273 depends on PCI || (OF && PPC)
2274 select FB_CFB_FILLRECT
2275 select FB_CFB_COPYAREA
2276 select FB_CFB_IMAGEBLIT
2278 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2281 prompt "GDC variant"
2282 depends on FB_MB862XX
2284 config FB_MB862XX_PCI_GDC
2285 bool "Carmine/Coral-P(A) GDC"
2288 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2289 PCI graphics controller devices.
2291 config FB_MB862XX_LIME
2293 depends on OF && PPC
2294 select FB_FOREIGN_ENDIAN
2295 select FB_LITTLE_ENDIAN
2297 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2301 config FB_MB862XX_I2C
2302 bool "Support I2C bus on MB862XX GDC"
2303 depends on FB_MB862XX && I2C
2304 depends on FB_MB862XX=m || I2C=y
2307 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2308 driver to support accessing I2C devices on controller's I2C bus.
2309 These are usually some video decoder chips.
2312 tristate "EP93XX frame buffer support"
2313 depends on FB && ARCH_EP93XX
2314 select FB_CFB_FILLRECT
2315 select FB_CFB_COPYAREA
2316 select FB_CFB_IMAGEBLIT
2318 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2319 This driver is also available as a module. The module will be called
2322 config FB_PRE_INIT_FB
2323 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2324 depends on FB && FB_MB862XX_LIME
2326 Select this option if display contents should be inherited as set by
2330 tristate "MX3 Framebuffer support"
2331 depends on FB && MX3_IPU
2332 select BACKLIGHT_CLASS_DEVICE
2333 select BACKLIGHT_LCD_SUPPORT
2334 select FB_CFB_FILLRECT
2335 select FB_CFB_COPYAREA
2336 select FB_CFB_IMAGEBLIT
2339 This is a framebuffer device for the i.MX31 LCD Controller. So
2340 far only synchronous displays are supported. If you plan to use
2341 an LCD display with your i.MX31 system, say Y here.
2343 config FB_BROADSHEET
2344 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2346 select FB_SYS_FILLRECT
2347 select FB_SYS_COPYAREA
2348 select FB_SYS_IMAGEBLIT
2350 select FB_DEFERRED_IO
2352 This driver implements support for the E-Ink Broadsheet
2353 controller. The release name for this device was Epson S1D13521
2354 and could also have been called by other names when coupled with
2358 tristate "AUO-K190X EPD controller support"
2360 select FB_SYS_FILLRECT
2361 select FB_SYS_COPYAREA
2362 select FB_SYS_IMAGEBLIT
2364 select FB_DEFERRED_IO
2366 Provides support for epaper controllers from the K190X series
2367 of AUO. These controllers can be used to drive epaper displays
2370 This option enables the common support, shared by the individual
2371 controller drivers. You will also have to enable the driver
2372 for the controller type used in your device.
2375 tristate "AUO-K1900 EPD controller support"
2376 depends on FB && FB_AUO_K190X
2378 This driver implements support for the AUO K1900 epd-controller.
2379 This controller can drive Sipix epaper displays but can only do
2380 serial updates, reducing the number of possible frames per second.
2383 tristate "AUO-K1901 EPD controller support"
2384 depends on FB && FB_AUO_K190X
2386 This driver implements support for the AUO K1901 epd-controller.
2387 This controller can drive Sipix epaper displays and supports
2388 concurrent updates, making higher frames per second possible.
2391 tristate "JZ4740 LCD framebuffer support"
2392 depends on FB && MACH_JZ4740
2393 select FB_SYS_FILLRECT
2394 select FB_SYS_COPYAREA
2395 select FB_SYS_IMAGEBLIT
2397 Framebuffer support for the JZ4740 SoC.
2400 tristate "MXS LCD framebuffer support"
2401 depends on FB && (ARCH_MXS || ARCH_MXC)
2402 select FB_CFB_FILLRECT
2403 select FB_CFB_COPYAREA
2404 select FB_CFB_IMAGEBLIT
2405 select FB_MODE_HELPERS
2406 select VIDEOMODE_HELPERS
2408 Framebuffer support for the MXS SoC.
2410 config FB_PUV3_UNIGFX
2411 tristate "PKUnity v3 Unigfx framebuffer support"
2412 depends on FB && UNICORE32 && ARCH_PUV3
2413 select FB_SYS_FILLRECT
2414 select FB_SYS_COPYAREA
2415 select FB_SYS_IMAGEBLIT
2418 Choose this option if you want to use the Unigfx device as a
2419 framebuffer device. Without the support of PCI & AGP.
2422 tristate "Microsoft Hyper-V Synthetic Video support"
2423 depends on FB && HYPERV
2424 select FB_CFB_FILLRECT
2425 select FB_CFB_COPYAREA
2426 select FB_CFB_IMAGEBLIT
2428 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2431 bool "Simple framebuffer support"
2433 select FB_CFB_FILLRECT
2434 select FB_CFB_COPYAREA
2435 select FB_CFB_IMAGEBLIT
2437 Say Y if you want support for a simple frame-buffer.
2439 This driver assumes that the display hardware has been initialized
2440 before the kernel boots, and the kernel will simply render to the
2441 pre-allocated frame buffer surface.
2443 Configuration re: surface address, size, and format must be provided
2444 through device tree, or plain old platform data.
2446 source "drivers/video/fbdev/omap/Kconfig"
2447 source "drivers/video/fbdev/omap2/Kconfig"
2448 source "drivers/video/fbdev/exynos/Kconfig"
2449 source "drivers/video/fbdev/mmp/Kconfig"
2451 config FB_SH_MOBILE_MERAM
2452 tristate "SuperH Mobile MERAM read ahead support"
2453 depends on (SUPERH || ARCH_SHMOBILE)
2454 select GENERIC_ALLOCATOR
2456 Enable MERAM support for the SuperH controller.
2458 This will allow for caching of the framebuffer to provide more
2459 reliable access under heavy main memory bus traffic situations.
2460 Up to 4 memory channels can be configured, allowing 4 RGB or
2461 2 YCbCr framebuffers to be configured.
2464 tristate "Solomon SSD1307 framebuffer support"
2465 depends on FB && I2C
2469 select FB_SYS_FILLRECT
2470 select FB_SYS_COPYAREA
2471 select FB_SYS_IMAGEBLIT
2472 select FB_DEFERRED_IO
2476 This driver implements support for the Solomon SSD1307
2477 OLED controller over I2C.