6 tristate "Support for frame buffer devices"
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
42 bool "Enable firmware EDID"
46 This enables access to the EDID transferred from the firmware.
47 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
48 transfers do not work for your driver and if you are using
49 nvidiafb, i810fb or savagefb.
51 In general, choosing Y for this option is safe. If you
52 experience extremely long delays while booting before you get
53 something on your display, try setting this to N. Matrox cards in
54 combination with certain motherboards and monitors are known to
55 suffer from this problem.
70 config FB_BOOT_VESA_SUPPORT
75 If true, at least one selected framebuffer driver can take advantage
76 of VESA video modes set at an early boot stage via the vga= parameter.
78 config FB_CFB_FILLRECT
83 Include the cfb_fillrect function for generic software rectangle
84 filling. This is used by drivers that don't provide their own
85 (accelerated) version.
87 config FB_CFB_COPYAREA
92 Include the cfb_copyarea function for generic software area copying.
93 This is used by drivers that don't provide their own (accelerated)
96 config FB_CFB_IMAGEBLIT
101 Include the cfb_imageblit function for generic software image
102 blitting. This is used by drivers that don't provide their own
103 (accelerated) version.
105 config FB_CFB_REV_PIXELS_IN_BYTE
110 Allow generic frame-buffer functions to work on displays with 1, 2
111 and 4 bits per pixel depths which has opposite order of pixels in
112 byte order to bytes in long order.
114 config FB_SYS_FILLRECT
119 Include the sys_fillrect function for generic software rectangle
120 filling. This is used by drivers that don't provide their own
121 (accelerated) version and the framebuffer is in system RAM.
123 config FB_SYS_COPYAREA
128 Include the sys_copyarea function for generic software area copying.
129 This is used by drivers that don't provide their own (accelerated)
130 version and the framebuffer is in system RAM.
132 config FB_SYS_IMAGEBLIT
137 Include the sys_imageblit function for generic software image
138 blitting. This is used by drivers that don't provide their own
139 (accelerated) version and the framebuffer is in system RAM.
141 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
146 Allow generic frame-buffer to provide get_fb_unmapped_area
149 menuconfig FB_FOREIGN_ENDIAN
150 bool "Framebuffer foreign endianness support"
153 This menu will let you enable support for the framebuffers with
154 non-native endianness (e.g. Little-Endian framebuffer on a
155 Big-Endian machine). Most probably you don't have such hardware,
156 so it's safe to say "n" here.
159 prompt "Choice endianness support"
160 depends on FB_FOREIGN_ENDIAN
162 config FB_BOTH_ENDIAN
163 bool "Support for Big- and Little-Endian framebuffers"
166 bool "Support for Big-Endian framebuffers only"
168 config FB_LITTLE_ENDIAN
169 bool "Support for Little-Endian framebuffers only"
178 config FB_DEFERRED_IO
185 depends on FB_DEFERRED_IO
192 Common utility functions useful to fbdev drivers of VGA-based
203 select BACKLIGHT_LCD_SUPPORT
204 select BACKLIGHT_CLASS_DEVICE
207 config FB_MODE_HELPERS
208 bool "Enable Video Mode Handling Helpers"
212 This enables functions for handling video modes using the
213 Generalized Timing Formula and the EDID parser. A few drivers rely
214 on this feature such as the radeonfb, rivafb, and the i810fb. If
215 your driver does not take advantage of this feature, choosing Y will
216 just increase the kernel size by about 5K.
218 config FB_TILEBLITTING
219 bool "Enable Tile Blitting Support"
223 This enables tile blitting. Tile blitting is a drawing technique
224 where the screen is divided into rectangular sections (tiles), whereas
225 the standard blitting divides the screen into pixels. Because the
226 default drawing element is a tile, drawing functions will be passed
227 parameters in terms of number of tiles instead of number of pixels.
228 For example, to draw a single character, instead of using bitmaps,
229 an index to an array of bitmaps will be used. To clear or move a
230 rectangular section of a screen, the rectangle will be described in
231 terms of number of tiles in the x- and y-axis.
233 This is particularly important to one driver, matroxfb. If
236 comment "Frame buffer hardware drivers"
240 tristate "Aeroflex Gaisler framebuffer support"
241 depends on FB && SPARC
242 select FB_CFB_FILLRECT
243 select FB_CFB_COPYAREA
244 select FB_CFB_IMAGEBLIT
246 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
249 tristate "Cirrus Logic support"
250 depends on FB && (ZORRO || PCI)
251 select FB_CFB_FILLRECT
252 select FB_CFB_COPYAREA
253 select FB_CFB_IMAGEBLIT
255 This enables support for Cirrus Logic GD542x/543x based boards on
256 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
258 If you have a PCI-based system, this enables support for these
259 chips: GD-543x, GD-544x, GD-5480.
261 Please read the file <file:Documentation/fb/cirrusfb.txt>.
263 Say N unless you have such a graphics board or plan to get one
264 before you next recompile the kernel.
267 tristate "Permedia2 support"
268 depends on FB && ((AMIGA && BROKEN) || PCI)
269 select FB_CFB_FILLRECT
270 select FB_CFB_COPYAREA
271 select FB_CFB_IMAGEBLIT
273 This is the frame buffer device driver for cards based on
274 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
275 The driver was tested on the following cards:
276 Diamond FireGL 1000 PRO AGP
277 ELSA Gloria Synergy PCI
278 Appian Jeronimo PRO (both heads) PCI
279 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
280 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
281 ASK Graphic Blaster Exxtreme AGP
283 To compile this driver as a module, choose M here: the
284 module will be called pm2fb.
286 config FB_PM2_FIFO_DISCONNECT
287 bool "enable FIFO disconnect feature"
288 depends on FB_PM2 && PCI
290 Support the Permedia2 FIFO disconnect feature.
293 tristate "ARM PrimeCell PL110 support"
294 depends on ARM || ARM64 || COMPILE_TEST
295 depends on FB && ARM_AMBA && HAS_IOMEM
296 select FB_CFB_FILLRECT
297 select FB_CFB_COPYAREA
298 select FB_CFB_IMAGEBLIT
299 select FB_MODE_HELPERS if OF
300 select VIDEOMODE_HELPERS if OF
301 select BACKLIGHT_LCD_SUPPORT if OF
302 select BACKLIGHT_CLASS_DEVICE if OF
304 This framebuffer device driver is for the ARM PrimeCell PL110
305 Colour LCD controller. ARM PrimeCells provide the building
306 blocks for System on a Chip devices.
308 If you want to compile this as a module (=code which can be
309 inserted into and removed from the running kernel), say M
310 here and read <file:Documentation/kbuild/modules.txt>. The module
311 will be called amba-clcd.
313 # Helper logic selected only by the ARM Versatile platform family.
314 config PLAT_VERSATILE_CLCD
315 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
317 depends on FB_ARMCLCD && FB=y
322 bool "Acorn VIDC support"
323 depends on (FB = y) && ARM && ARCH_ACORN
324 select FB_CFB_FILLRECT
325 select FB_CFB_COPYAREA
326 select FB_CFB_IMAGEBLIT
328 This is the frame buffer device driver for the Acorn VIDC graphics
329 hardware found in Acorn RISC PCs and other ARM-based machines. If
332 config FB_CLPS711X_OLD
334 select FB_CFB_FILLRECT
335 select FB_CFB_COPYAREA
336 select FB_CFB_IMAGEBLIT
339 tristate "CLPS711X LCD support"
340 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
341 select FB_CLPS711X_OLD if ARCH_CLPS711X && !ARCH_MULTIPLATFORM
342 select BACKLIGHT_LCD_SUPPORT
343 select FB_MODE_HELPERS
344 select FB_SYS_FILLRECT
345 select FB_SYS_COPYAREA
346 select FB_SYS_IMAGEBLIT
347 select LCD_CLASS_DEVICE
348 select VIDEOMODE_HELPERS
350 Say Y to enable the Framebuffer driver for the Cirrus Logic
354 bool "SA-1100 LCD support"
355 depends on (FB = y) && ARM && ARCH_SA1100
356 select FB_CFB_FILLRECT
357 select FB_CFB_COPYAREA
358 select FB_CFB_IMAGEBLIT
360 This is a framebuffer device for the SA-1100 LCD Controller.
361 See <http://www.linux-fbdev.org/> for information on framebuffer
364 If you plan to use the LCD display with your SA-1100 system, say
368 tristate "Freescale i.MX1/21/25/27 LCD support"
369 depends on FB && ARCH_MXC
370 select BACKLIGHT_LCD_SUPPORT
371 select LCD_CLASS_DEVICE
372 select FB_CFB_FILLRECT
373 select FB_CFB_COPYAREA
374 select FB_CFB_IMAGEBLIT
375 select FB_MODE_HELPERS
376 select VIDEOMODE_HELPERS
379 tristate "CyberPro 2000/2010/5000 support"
380 depends on FB && PCI && (BROKEN || !SPARC64)
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
385 This enables support for the Integraphics CyberPro 20x0 and 5000
386 VGA chips used in the Rebel.com Netwinder and other machines.
387 Say Y if you have a NetWinder or a graphics card containing this
388 device, otherwise say N.
390 config FB_CYBER2000_DDC
391 bool "DDC for CyberPro support"
392 depends on FB_CYBER2000
396 Say Y here if you want DDC support for your CyberPro graphics
397 card. This is only I2C bus support, driver does not use EDID.
399 config FB_CYBER2000_I2C
400 bool "CyberPro 2000/2010/5000 I2C support"
401 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
402 depends on I2C=y || FB_CYBER2000=m
405 Enable support for the I2C video decoder interface on the
406 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
407 on the Netwinder machines for the SAA7111 video capture.
411 depends on (FB = y) && APOLLO
413 select FB_CFB_FILLRECT
414 select FB_CFB_IMAGEBLIT
418 depends on (FB = y) && Q40
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
425 tristate "Amiga native chipset support"
426 depends on FB && AMIGA
428 This is the frame buffer device driver for the builtin graphics
429 chipset found in Amigas.
431 To compile this driver as a module, choose M here: the
432 module will be called amifb.
435 bool "Amiga OCS chipset support"
438 This enables support for the original Agnus and Denise video chips,
439 found in the Amiga 1000 and most A500's and A2000's. If you intend
440 to run Linux on any of these systems, say Y; otherwise say N.
443 bool "Amiga ECS chipset support"
446 This enables support for the Enhanced Chip Set, found in later
447 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
448 you intend to run Linux on any of these systems, say Y; otherwise
452 bool "Amiga AGA chipset support"
455 This enables support for the Advanced Graphics Architecture (also
456 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
457 and CD32. If you intend to run Linux on any of these systems, say Y;
461 bool "Amiga FrameMaster II/Rainbow II support"
462 depends on (FB = y) && ZORRO
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
467 This is the frame buffer device driver for the Amiga FrameMaster
468 card from BSC (exhibited 1992 but not shipped as a CBM product).
471 tristate "Arc Monochrome LCD board support"
473 select FB_SYS_FILLRECT
474 select FB_SYS_COPYAREA
475 select FB_SYS_IMAGEBLIT
478 This enables support for the Arc Monochrome LCD board. The board
479 is based on the KS-108 lcd controller and is typically a matrix
480 of 2*n chips. This driver was tested with a 128x64 panel. This
481 driver supports it for use with x86 SBCs through a 16 bit GPIO
482 interface (8 bit data, 8 bit control). If you anticipate using
483 this driver, say Y or M; otherwise say N. You must specify the
484 GPIO IO address to be used for setting control and data.
487 bool "Atari native chipset support"
488 depends on (FB = y) && ATARI
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the builtin graphics
494 chipset found in Ataris.
497 bool "Open Firmware frame buffer device support"
498 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 Say Y if you want support with Open Firmware for your graphics
508 bool "Apple \"control\" display support"
509 depends on (FB = y) && PPC_PMAC && PPC32
510 select FB_CFB_FILLRECT
511 select FB_CFB_COPYAREA
512 select FB_CFB_IMAGEBLIT
515 This driver supports a frame buffer for the graphics adapter in the
516 Power Macintosh 7300 and others.
519 bool "Apple \"platinum\" display support"
520 depends on (FB = y) && PPC_PMAC && PPC32
521 select FB_CFB_FILLRECT
522 select FB_CFB_COPYAREA
523 select FB_CFB_IMAGEBLIT
526 This driver supports a frame buffer for the "platinum" graphics
527 adapter in some Power Macintoshes.
530 bool "Apple \"valkyrie\" display support"
531 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
537 This driver supports a frame buffer for the "valkyrie" graphics
538 adapter in some Power Macintoshes.
541 bool "Chips 65550 display support"
542 depends on (FB = y) && PPC32 && PCI
543 select FB_CFB_FILLRECT
544 select FB_CFB_COPYAREA
545 select FB_CFB_IMAGEBLIT
547 This is the frame buffer device driver for the Chips & Technologies
548 65550 graphics chip in PowerBooks.
551 bool "Asiliant (Chips) 69000 display support"
552 depends on (FB = y) && PCI
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
557 This is the frame buffer device driver for the Asiliant 69030 chipset
560 bool "IMS Twin Turbo display support"
561 depends on (FB = y) && PCI
562 select FB_CFB_IMAGEBLIT
563 select FB_MACMODES if PPC
565 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
566 many Macintosh and compatible computers.
569 tristate "VGA 16-color graphics support"
570 depends on FB && (X86 || PPC)
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 select FONT_8x16 if FRAMEBUFFER_CONSOLE
577 This is the frame buffer device driver for VGA 16 color graphic
578 cards. Say Y if you have such a card.
580 To compile this driver as a module, choose M here: the
581 module will be called vga16fb.
583 config FB_BF54X_LQ043
584 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
585 depends on FB && (BF54x) && !BF542
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
590 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
592 config FB_BFIN_T350MCQB
593 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
594 depends on FB && BLACKFIN
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
601 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
602 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
604 config FB_BFIN_LQ035Q1
605 tristate "SHARP LQ035Q1DH02 TFT LCD"
606 depends on FB && BLACKFIN && SPI
607 select FB_CFB_FILLRECT
608 select FB_CFB_COPYAREA
609 select FB_CFB_IMAGEBLIT
612 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
613 the Blackfin Landscape LCD EZ-Extender Card.
614 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
615 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
617 To compile this driver as a module, choose M here: the
618 module will be called bfin-lq035q1-fb.
620 config FB_BF537_LQ035
621 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
622 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
623 select FB_CFB_FILLRECT
624 select FB_CFB_COPYAREA
625 select FB_CFB_IMAGEBLIT
628 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
631 To compile this driver as a module, choose M here: the
632 module will be called bf537-lq035.
635 tristate "Blackfin ADV7393 Video encoder"
636 depends on FB && BLACKFIN
638 select FB_CFB_FILLRECT
639 select FB_CFB_COPYAREA
640 select FB_CFB_IMAGEBLIT
642 This is the framebuffer device for a ADV7393 video encoder
643 attached to a Blackfin on the PPI port.
644 If your Blackfin board has a ADV7393 select Y.
646 To compile this driver as a module, choose M here: the
647 module will be called bfin_adv7393fb.
650 prompt "Video mode support"
651 depends on FB_BFIN_7393
661 bool 'NTSC 640x480 (Experimental)'
664 bool 'PAL 640x480 (Experimental)'
667 bool 'NTSC 720x480 YCbCR input'
670 bool 'PAL 720x576 YCbCR input'
675 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
676 depends on (FB_BFIN_7393)
677 default ADV7393_1XMEM
687 tristate "HP STI frame buffer device support"
688 depends on FB && PARISC
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
696 STI refers to the HP "Standard Text Interface" which is a set of
697 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
698 Enabling this option will implement the linux framebuffer device
699 using calls to the STI BIOS routines for initialisation.
701 If you enable this option, you will get a planar framebuffer device
702 /dev/fb which will work on the most common HP graphic cards of the
703 NGLE family, including the artist chips (in the 7xx and Bxxx series),
704 HCRX, HCRX24, CRX, CRX24 and VisEG series.
706 It is safe to enable this option, so you should probably say "Y".
709 bool "Generic Macintosh display support"
710 depends on (FB = y) && MAC
711 select FB_CFB_FILLRECT
712 select FB_CFB_COPYAREA
713 select FB_CFB_IMAGEBLIT
718 depends on (FB = y) && DIO
719 select FB_CFB_IMAGEBLIT
723 tristate "TGA/SFB+ framebuffer support"
724 depends on FB && (ALPHA || TC)
725 select FB_CFB_FILLRECT
726 select FB_CFB_COPYAREA
727 select FB_CFB_IMAGEBLIT
730 This is the frame buffer device driver for generic TGA and SFB+
731 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
732 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
733 TURBOchannel cards, also known as PMAGD-A, -B and -C.
735 Due to hardware limitations ZLX-E2 and E3 cards are not supported
736 for DECstation 5000/200 systems. Additionally due to firmware
737 limitations these cards may cause troubles with booting DECstation
738 5000/240 and /260 systems, but are fully supported under Linux if
739 you manage to get it going. ;-)
741 Say Y if you have one of those.
744 tristate "Userspace VESA VGA graphics support"
745 depends on FB && CONNECTOR
746 select FB_CFB_FILLRECT
747 select FB_CFB_COPYAREA
748 select FB_CFB_IMAGEBLIT
749 select FB_MODE_HELPERS
751 This is the frame buffer driver for generic VBE 2.0 compliant
752 graphic cards. It can also take advantage of VBE 3.0 features,
753 such as refresh rate adjustment.
755 This driver generally provides more features than vesafb but
756 requires a userspace helper application called 'v86d'. See
757 <file:Documentation/fb/uvesafb.txt> for more information.
762 bool "VESA VGA graphics support"
763 depends on (FB = y) && X86
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
767 select FB_BOOT_VESA_SUPPORT
769 This is the frame buffer device driver for generic VESA 2.0
770 compliant graphic cards. The older VESA 1.2 cards are not supported.
771 You will get a boot time penguin logo at no additional cost. Please
772 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
775 bool "EFI-based Framebuffer Support"
776 depends on (FB = y) && !IA64 && EFI
777 select FB_CFB_FILLRECT
778 select FB_CFB_COPYAREA
779 select FB_CFB_IMAGEBLIT
781 This is the EFI frame buffer device driver. If the firmware on
782 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
783 using the EFI framebuffer as your console.
786 tristate "N411 Apollo/Hecuba devkit support"
787 depends on FB && X86 && MMU
788 select FB_SYS_FILLRECT
789 select FB_SYS_COPYAREA
790 select FB_SYS_IMAGEBLIT
792 select FB_DEFERRED_IO
795 This enables support for the Apollo display controller in its
796 Hecuba form using the n411 devkit.
799 tristate "Hercules mono graphics support"
802 Say Y here if you have a Hercules mono graphics card.
804 To compile this driver as a module, choose M here: the
805 module will be called hgafb.
807 As this card technology is at least 25 years old,
808 most people will answer N here.
811 bool "SGI Graphics Backend frame buffer support"
812 depends on (FB = y) && SGI_IP32
813 select FB_CFB_FILLRECT
814 select FB_CFB_COPYAREA
815 select FB_CFB_IMAGEBLIT
817 This is the frame buffer device driver for SGI Graphics Backend.
818 This chip is used in SGI O2 and Visual Workstation 320/540.
821 int "Video memory size in MB"
825 This is the amount of memory reserved for the framebuffer,
826 which can be any value between 1MB and 8MB.
829 bool "SBUS and UPA framebuffers"
830 depends on (FB = y) && SPARC
832 Say Y if you want support for SBUS or UPA based frame buffer device.
836 depends on (FB = y) && (SPARC && FB_SBUS)
837 select FB_CFB_FILLRECT
838 select FB_CFB_COPYAREA
839 select FB_CFB_IMAGEBLIT
841 This is the frame buffer device driver for the BWtwo frame buffer.
844 bool "CGthree support"
845 depends on (FB = y) && (SPARC && FB_SBUS)
846 select FB_CFB_FILLRECT
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This is the frame buffer device driver for the CGthree frame buffer.
853 bool "CGsix (GX,TurboGX) support"
854 depends on (FB = y) && (SPARC && FB_SBUS)
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the frame buffer device driver for the CGsix (GX, TurboGX)
862 bool "Creator/Creator3D/Elite3D support"
863 depends on FB_SBUS && SPARC64
864 select FB_CFB_COPYAREA
865 select FB_CFB_IMAGEBLIT
867 This is the frame buffer device driver for the Creator, Creator3D,
868 and Elite3D graphics boards.
871 bool "TCX (SS4/SS5 only) support"
873 select FB_CFB_FILLRECT
874 select FB_CFB_COPYAREA
875 select FB_CFB_IMAGEBLIT
877 This is the frame buffer device driver for the TCX 24/8bit frame
881 bool "CGfourteen (SX) support"
883 select FB_CFB_FILLRECT
884 select FB_CFB_COPYAREA
885 select FB_CFB_IMAGEBLIT
887 This is the frame buffer device driver for the CGfourteen frame
888 buffer on Desktop SPARCsystems with the SX graphics option.
891 bool "P9100 (Sparcbook 3 only) support"
893 select FB_CFB_FILLRECT
894 select FB_CFB_COPYAREA
895 select FB_CFB_IMAGEBLIT
897 This is the frame buffer device driver for the P9100 card
898 supported on Sparcbook 3 machines.
901 bool "Leo (ZX) support"
903 select FB_CFB_FILLRECT
904 select FB_CFB_COPYAREA
905 select FB_CFB_IMAGEBLIT
907 This is the frame buffer device driver for the SBUS-based Sun ZX
908 (leo) frame buffer cards.
911 bool "IGA 168x display support"
912 depends on (FB = y) && SPARC32
913 select FB_CFB_FILLRECT
914 select FB_CFB_COPYAREA
915 select FB_CFB_IMAGEBLIT
917 This is the framebuffer device for the INTERGRAPHICS 1680 and
918 successor frame buffer cards.
921 bool "Sun XVR-500 3DLABS Wildcat support"
922 depends on (FB = y) && PCI && SPARC64
923 select FB_CFB_FILLRECT
924 select FB_CFB_COPYAREA
925 select FB_CFB_IMAGEBLIT
927 This is the framebuffer device for the Sun XVR-500 and similar
928 graphics cards based upon the 3DLABS Wildcat chipset. The driver
929 only works on sparc64 systems where the system firmware has
930 mostly initialized the card already. It is treated as a
931 completely dumb framebuffer device.
934 bool "Sun XVR-2500 3DLABS Wildcat support"
935 depends on (FB = y) && PCI && SPARC64
936 select FB_CFB_FILLRECT
937 select FB_CFB_COPYAREA
938 select FB_CFB_IMAGEBLIT
940 This is the framebuffer device for the Sun XVR-2500 and similar
941 graphics cards based upon the 3DLABS Wildcat chipset. The driver
942 only works on sparc64 systems where the system firmware has
943 mostly initialized the card already. It is treated as a
944 completely dumb framebuffer device.
947 bool "Sun XVR-1000 support"
948 depends on (FB = y) && SPARC64
949 select FB_CFB_FILLRECT
950 select FB_CFB_COPYAREA
951 select FB_CFB_IMAGEBLIT
953 This is the framebuffer device for the Sun XVR-1000 and similar
954 graphics cards. The driver only works on sparc64 systems where
955 the system firmware has mostly initialized the card already. It
956 is treated as a completely dumb framebuffer device.
959 tristate "NEC PowerVR 2 display support"
960 depends on FB && SH_DREAMCAST
961 select FB_CFB_FILLRECT
962 select FB_CFB_COPYAREA
963 select FB_CFB_IMAGEBLIT
965 Say Y here if you have a PowerVR 2 card in your box. If you plan to
966 run linux on your Dreamcast, you will have to say Y here.
967 This driver may or may not work on other PowerVR 2 cards, but is
968 totally untested. Use at your own risk. If unsure, say N.
970 To compile this driver as a module, choose M here: the
971 module will be called pvr2fb.
973 You can pass several parameters to the driver at boot time or at
974 module load time. The parameters look like "video=pvr2:XXX", where
975 the meaning of XXX can be found at the end of the main source file
976 (<file:drivers/video/pvr2fb.c>). Please see the file
977 <file:Documentation/fb/pvr2fb.txt>.
980 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
981 depends on FB && HAS_DMA
982 select FB_CFB_FILLRECT
983 select FB_CFB_COPYAREA
984 select FB_CFB_IMAGEBLIT
986 This enables support for the OpenCores VGA/LCD core.
988 The OpenCores VGA/LCD core is typically used together with
989 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
990 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
992 The source code and specification for the core is available at
993 <http://opencores.org/project,vga_lcd>
996 tristate "Epson S1D13XXX framebuffer support"
998 select FB_CFB_FILLRECT
999 select FB_CFB_COPYAREA
1000 select FB_CFB_IMAGEBLIT
1002 Support for S1D13XXX framebuffer device family (currently only
1003 working with S1D13806). Product specs at
1004 <http://vdc.epson.com/>
1007 tristate "AT91/AT32 LCD Controller support"
1008 depends on FB && HAVE_FB_ATMEL
1010 select FB_CFB_FILLRECT
1011 select FB_CFB_COPYAREA
1012 select FB_CFB_IMAGEBLIT
1013 select FB_MODE_HELPERS
1014 select VIDEOMODE_HELPERS
1016 This enables support for the AT91/AT32 LCD Controller.
1019 tristate "nVidia Framebuffer Support"
1020 depends on FB && PCI
1021 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1022 select FB_MODE_HELPERS
1023 select FB_CFB_FILLRECT
1024 select FB_CFB_COPYAREA
1025 select FB_CFB_IMAGEBLIT
1029 This driver supports graphics boards with the nVidia chips, TNT
1030 and newer. For very old chipsets, such as the RIVA128, then use
1032 Say Y if you have such a graphics board.
1034 To compile this driver as a module, choose M here: the
1035 module will be called nvidiafb.
1037 config FB_NVIDIA_I2C
1038 bool "Enable DDC Support"
1039 depends on FB_NVIDIA
1042 This enables I2C support for nVidia Chipsets. This is used
1043 only for getting EDID information from the attached display
1044 allowing for robust video mode handling and switching.
1046 Because fbdev-2.6 requires that drivers must be able to
1047 independently validate video mode parameters, you should say Y
1050 config FB_NVIDIA_DEBUG
1051 bool "Lots of debug output"
1052 depends on FB_NVIDIA
1055 Say Y here if you want the nVidia driver to output all sorts
1056 of debugging information to provide to the maintainer when
1057 something goes wrong.
1059 config FB_NVIDIA_BACKLIGHT
1060 bool "Support for backlight control"
1061 depends on FB_NVIDIA
1064 Say Y here if you want to control the backlight of your display.
1067 tristate "nVidia Riva support"
1068 depends on FB && PCI
1069 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1070 select FB_MODE_HELPERS
1071 select FB_CFB_FILLRECT
1072 select FB_CFB_COPYAREA
1073 select FB_CFB_IMAGEBLIT
1077 This driver supports graphics boards with the nVidia Riva/Geforce
1079 Say Y if you have such a graphics board.
1081 To compile this driver as a module, choose M here: the
1082 module will be called rivafb.
1085 bool "Enable DDC Support"
1089 This enables I2C support for nVidia Chipsets. This is used
1090 only for getting EDID information from the attached display
1091 allowing for robust video mode handling and switching.
1093 Because fbdev-2.6 requires that drivers must be able to
1094 independently validate video mode parameters, you should say Y
1097 config FB_RIVA_DEBUG
1098 bool "Lots of debug output"
1102 Say Y here if you want the Riva driver to output all sorts
1103 of debugging information to provide to the maintainer when
1104 something goes wrong.
1106 config FB_RIVA_BACKLIGHT
1107 bool "Support for backlight control"
1111 Say Y here if you want to control the backlight of your display.
1114 tristate "Intel740 support"
1115 depends on FB && PCI
1116 select FB_MODE_HELPERS
1117 select FB_CFB_FILLRECT
1118 select FB_CFB_COPYAREA
1119 select FB_CFB_IMAGEBLIT
1123 This driver supports graphics cards based on Intel740 chip.
1126 tristate "Intel 810/815 support"
1127 depends on FB && PCI && X86_32 && AGP_INTEL
1128 select FB_MODE_HELPERS
1129 select FB_CFB_FILLRECT
1130 select FB_CFB_COPYAREA
1131 select FB_CFB_IMAGEBLIT
1134 This driver supports the on-board graphics built in to the Intel 810
1135 and 815 chipsets. Say Y if you have and plan to use such a board.
1137 To compile this driver as a module, choose M here: the
1138 module will be called i810fb.
1140 For more information, please read
1141 <file:Documentation/fb/intel810.txt>
1144 bool "use VESA Generalized Timing Formula"
1147 If you say Y, then the VESA standard, Generalized Timing Formula
1148 or GTF, will be used to calculate the required video timing values
1149 per video mode. Since the GTF allows nondiscrete timings
1150 (nondiscrete being a range of values as opposed to discrete being a
1151 set of values), you'll be able to use any combination of horizontal
1152 and vertical resolutions, and vertical refresh rates without having
1153 to specify your own timing parameters. This is especially useful
1154 to maximize the performance of an aging display, or if you just
1155 have a display with nonstandard dimensions. A VESA compliant
1156 monitor is recommended, but can still work with non-compliant ones.
1157 If you need or want this, then select this option. The timings may
1158 not be compliant with Intel's recommended values. Use at your own
1161 If you say N, the driver will revert to discrete video timings
1162 using a set recommended by Intel in their documentation.
1167 bool "Enable DDC Support"
1168 depends on FB_I810 && FB_I810_GTF
1173 tristate "Intel LE80578 (Vermilion) support"
1174 depends on FB && PCI && X86
1175 select FB_MODE_HELPERS
1176 select FB_CFB_FILLRECT
1177 select FB_CFB_COPYAREA
1178 select FB_CFB_IMAGEBLIT
1180 This driver supports the LE80578 (Vermilion Range) chipset
1182 config FB_CARILLO_RANCH
1183 tristate "Intel Carillo Ranch support"
1184 depends on FB_LE80578 && FB && PCI && X86
1186 This driver supports the LE80578 (Carillo Ranch) board
1189 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1190 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1191 select FB_MODE_HELPERS
1192 select FB_CFB_FILLRECT
1193 select FB_CFB_COPYAREA
1194 select FB_CFB_IMAGEBLIT
1195 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1196 depends on !DRM_I915
1198 This driver supports the on-board graphics built in to the Intel
1199 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1200 Say Y if you have and plan to use such a board.
1202 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1204 To compile this driver as a module, choose M here: the
1205 module will be called intelfb.
1207 For more information, please read <file:Documentation/fb/intelfb.txt>
1209 config FB_INTEL_DEBUG
1210 bool "Intel driver Debug Messages"
1213 Say Y here if you want the Intel driver to output all sorts
1214 of debugging information to provide to the maintainer when
1215 something goes wrong.
1218 bool "DDC/I2C for Intel framebuffer support"
1223 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1226 tristate "Matrox acceleration"
1227 depends on FB && PCI
1228 select FB_CFB_FILLRECT
1229 select FB_CFB_COPYAREA
1230 select FB_CFB_IMAGEBLIT
1231 select FB_TILEBLITTING
1232 select FB_MACMODES if PPC_PMAC
1234 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1235 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1236 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1237 Matrox G400, G450 or G550 card in your box.
1239 To compile this driver as a module, choose M here: the
1240 module will be called matroxfb.
1242 You can pass several parameters to the driver at boot time or at
1243 module load time. The parameters look like "video=matroxfb:XXX", and
1244 are described in <file:Documentation/fb/matroxfb.txt>.
1246 config FB_MATROX_MILLENIUM
1247 bool "Millennium I/II support"
1248 depends on FB_MATROX
1250 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1251 video card. If you select "Advanced lowlevel driver options" below,
1252 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1253 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1254 also use font widths different from 8.
1256 config FB_MATROX_MYSTIQUE
1257 bool "Mystique support"
1258 depends on FB_MATROX
1260 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1261 video card. If you select "Advanced lowlevel driver options" below,
1262 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1263 packed pixel and 32 bpp packed pixel. You can also use font widths
1267 bool "G100/G200/G400/G450/G550 support"
1268 depends on FB_MATROX
1270 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1271 video card. If you select "Advanced lowlevel driver options", you
1272 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1273 pixel and 32 bpp packed pixel. You can also use font widths
1276 If you need support for G400 secondary head, you must say Y to
1277 "Matrox I2C support" and "G400 second head support" right below.
1278 G450/G550 secondary head and digital output are supported without
1281 The driver starts in monitor mode. You must use the matroxset tool
1282 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1283 swap primary and secondary head outputs, or to change output mode.
1284 Secondary head driver always start in 640x480 resolution and you
1285 must use fbset to change it.
1287 Do not forget that second head supports only 16 and 32 bpp
1288 packed pixels, so it is a good idea to compile them into the kernel
1289 too. You can use only some font widths, as the driver uses generic
1290 painting procedures (the secondary head does not use acceleration
1293 G450/G550 hardware can display TV picture only from secondary CRTC,
1294 and it performs no scaling, so picture must have 525 or 625 lines.
1296 config FB_MATROX_I2C
1297 tristate "Matrox I2C support"
1298 depends on FB_MATROX
1301 This drivers creates I2C buses which are needed for accessing the
1302 DDC (I2C) bus present on all Matroxes, an I2C bus which
1303 interconnects Matrox optional devices, like MGA-TVO on G200 and
1304 G400, and the secondary head DDC bus, present on G400 only.
1306 You can say Y or M here if you want to experiment with monitor
1307 detection code. You must say Y or M here if you want to use either
1308 second head of G400 or MGA-TVO on G200 or G400.
1310 If you compile it as module, it will create a module named
1313 config FB_MATROX_MAVEN
1314 tristate "G400 second head support"
1315 depends on FB_MATROX_G && FB_MATROX_I2C
1317 WARNING !!! This support does not work with G450 !!!
1319 Say Y or M here if you want to use a secondary head (meaning two
1320 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1321 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1322 secondary head output is blanked while you are in X. With XFree
1323 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1324 the fbdev driver on first head and the fbdev driver on second head.
1326 If you compile it as module, two modules are created,
1327 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1328 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1329 also load i2c-matroxfb to get it to run.
1331 The driver starts in monitor mode and you must use the matroxset
1333 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1334 PAL or NTSC or to swap primary and secondary head outputs.
1335 Secondary head driver also always start in 640x480 resolution, you
1336 must use fbset to change it.
1338 Also do not forget that second head supports only 16 and 32 bpp
1339 packed pixels, so it is a good idea to compile them into the kernel
1340 too. You can use only some font widths, as the driver uses generic
1341 painting procedures (the secondary head does not use acceleration
1345 tristate "ATI Radeon display support"
1346 depends on FB && PCI
1347 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1348 select FB_MODE_HELPERS
1349 select FB_CFB_FILLRECT
1350 select FB_CFB_COPYAREA
1351 select FB_CFB_IMAGEBLIT
1352 select FB_MACMODES if PPC
1354 Choose this option if you want to use an ATI Radeon graphics card as
1355 a framebuffer device. There are both PCI and AGP versions. You
1356 don't need to choose this to run the Radeon in plain VGA mode.
1358 There is a product page at
1359 http://products.amd.com/en-us/GraphicCardResult.aspx
1361 config FB_RADEON_I2C
1362 bool "DDC/I2C for ATI Radeon support"
1363 depends on FB_RADEON
1367 Say Y here if you want DDC/I2C support for your Radeon board.
1369 config FB_RADEON_BACKLIGHT
1370 bool "Support for backlight control"
1371 depends on FB_RADEON
1374 Say Y here if you want to control the backlight of your display.
1376 config FB_RADEON_DEBUG
1377 bool "Lots of debug output from Radeon driver"
1378 depends on FB_RADEON
1381 Say Y here if you want the Radeon driver to output all sorts
1382 of debugging information to provide to the maintainer when
1383 something goes wrong.
1386 tristate "ATI Rage128 display support"
1387 depends on FB && PCI
1388 select FB_CFB_FILLRECT
1389 select FB_CFB_COPYAREA
1390 select FB_CFB_IMAGEBLIT
1391 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1392 select FB_MACMODES if PPC_PMAC
1394 This driver supports graphics boards with the ATI Rage128 chips.
1395 Say Y if you have such a graphics board and read
1396 <file:Documentation/fb/aty128fb.txt>.
1398 To compile this driver as a module, choose M here: the
1399 module will be called aty128fb.
1401 config FB_ATY128_BACKLIGHT
1402 bool "Support for backlight control"
1403 depends on FB_ATY128
1406 Say Y here if you want to control the backlight of your display.
1409 tristate "ATI Mach64 display support" if PCI || ATARI
1410 depends on FB && !SPARC32
1411 select FB_CFB_FILLRECT
1412 select FB_CFB_COPYAREA
1413 select FB_CFB_IMAGEBLIT
1414 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1415 select FB_MACMODES if PPC
1417 This driver supports graphics boards with the ATI Mach64 chips.
1418 Say Y if you have such a graphics board.
1420 To compile this driver as a module, choose M here: the
1421 module will be called atyfb.
1424 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1425 depends on PCI && FB_ATY
1426 default y if SPARC64 && PCI
1428 Say Y here to support use of ATI's 64-bit Rage boards (or other
1429 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1430 framebuffer device. The ATI product support page for these boards
1431 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1433 config FB_ATY_GENERIC_LCD
1434 bool "Mach64 generic LCD support"
1435 depends on FB_ATY_CT
1437 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1438 Rage XC, or Rage XL chipset.
1441 bool "Mach64 GX support" if PCI
1445 Say Y here to support use of the ATI Mach64 Graphics Expression
1446 board (or other boards based on the Mach64 GX chipset) as a
1447 framebuffer device. The ATI product support page for these boards
1449 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1451 config FB_ATY_BACKLIGHT
1452 bool "Support for backlight control"
1456 Say Y here if you want to control the backlight of your display.
1459 tristate "S3 Trio/Virge support"
1460 depends on FB && PCI
1461 select FB_CFB_FILLRECT
1462 select FB_CFB_COPYAREA
1463 select FB_CFB_IMAGEBLIT
1464 select FB_TILEBLITTING
1467 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1469 Driver for graphics boards with S3 Trio / S3 Virge chip.
1472 bool "DDC for S3 support"
1477 Say Y here if you want DDC support for your S3 graphics card.
1480 tristate "S3 Savage support"
1481 depends on FB && PCI
1482 select FB_MODE_HELPERS
1483 select FB_CFB_FILLRECT
1484 select FB_CFB_COPYAREA
1485 select FB_CFB_IMAGEBLIT
1488 This driver supports notebooks and computers with S3 Savage PCI/AGP
1491 Say Y if you have such a graphics card.
1493 To compile this driver as a module, choose M here; the module
1494 will be called savagefb.
1496 config FB_SAVAGE_I2C
1497 bool "Enable DDC2 Support"
1498 depends on FB_SAVAGE
1501 This enables I2C support for S3 Savage Chipsets. This is used
1502 only for getting EDID information from the attached display
1503 allowing for robust video mode handling and switching.
1505 Because fbdev-2.6 requires that drivers must be able to
1506 independently validate video mode parameters, you should say Y
1509 config FB_SAVAGE_ACCEL
1510 bool "Enable Console Acceleration"
1511 depends on FB_SAVAGE
1514 This option will compile in console acceleration support. If
1515 the resulting framebuffer console has bothersome glitches, then
1519 tristate "SiS/XGI display support"
1520 depends on FB && PCI
1521 select FB_CFB_FILLRECT
1522 select FB_CFB_COPYAREA
1523 select FB_CFB_IMAGEBLIT
1524 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1525 select FB_SIS_300 if !FB_SIS_315
1527 This is the frame buffer device driver for the SiS 300, 315, 330
1528 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1529 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1531 To compile this driver as a module, choose M here; the module
1532 will be called sisfb.
1535 bool "SiS 300 series support"
1538 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1541 bool "SiS 315/330/340 series and XGI support"
1544 Say Y here to support use of the SiS 315, 330 and 340 series
1545 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1546 as XGI V3XT, V5, V8 and Z7.
1549 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1550 depends on FB && PCI && X86 && GPIOLIB && I2C
1551 select FB_CFB_FILLRECT
1552 select FB_CFB_COPYAREA
1553 select FB_CFB_IMAGEBLIT
1556 This is the frame buffer device driver for Graphics chips of VIA
1557 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1558 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1560 Say Y if you have a VIA UniChrome graphics board.
1562 To compile this driver as a module, choose M here: the
1563 module will be called viafb.
1567 config FB_VIA_DIRECT_PROCFS
1568 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1572 Allow direct hardware access to some output registers via procfs.
1573 This is dangerous but may provide the only chance to get the
1574 correct output device configuration.
1575 Its use is strongly discouraged.
1577 config FB_VIA_X_COMPATIBILITY
1578 bool "X server compatibility"
1582 This option reduces the functionality (power saving, ...) of the
1583 framebuffer to avoid negative impact on the OpenChrome X server.
1584 If you use any X server other than fbdev you should enable this
1585 otherwise it should be safe to disable it and allow using all
1591 tristate "NeoMagic display support"
1592 depends on FB && PCI
1593 select FB_MODE_HELPERS
1594 select FB_CFB_FILLRECT
1595 select FB_CFB_COPYAREA
1596 select FB_CFB_IMAGEBLIT
1599 This driver supports notebooks with NeoMagic PCI chips.
1600 Say Y if you have such a graphics card.
1602 To compile this driver as a module, choose M here: the
1603 module will be called neofb.
1606 tristate "IMG Kyro support"
1607 depends on FB && PCI
1608 select FB_CFB_FILLRECT
1609 select FB_CFB_COPYAREA
1610 select FB_CFB_IMAGEBLIT
1612 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1615 To compile this driver as a module, choose M here: the
1616 module will be called kyrofb.
1619 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1620 depends on FB && PCI
1621 select FB_CFB_IMAGEBLIT
1622 select FB_CFB_FILLRECT
1623 select FB_CFB_COPYAREA
1624 select FB_MODE_HELPERS
1626 This driver supports graphics boards with the 3Dfx Banshee,
1627 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1628 such a graphics board.
1630 To compile this driver as a module, choose M here: the
1631 module will be called tdfxfb.
1633 config FB_3DFX_ACCEL
1634 bool "3Dfx Acceleration functions"
1637 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1638 device driver with acceleration functions.
1641 bool "Enable DDC/I2C support"
1646 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1649 tristate "3Dfx Voodoo Graphics (sst1) support"
1650 depends on FB && PCI
1651 select FB_CFB_FILLRECT
1652 select FB_CFB_COPYAREA
1653 select FB_CFB_IMAGEBLIT
1655 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1656 Voodoo2 (cvg) based graphics card.
1658 To compile this driver as a module, choose M here: the
1659 module will be called sstfb.
1661 WARNING: Do not use any application that uses the 3D engine
1662 (namely glide) while using this driver.
1663 Please read the <file:Documentation/fb/sstfb.txt> for supported
1664 options and other important info support.
1667 tristate "VIA VT8623 support"
1668 depends on FB && PCI
1669 select FB_CFB_FILLRECT
1670 select FB_CFB_COPYAREA
1671 select FB_CFB_IMAGEBLIT
1672 select FB_TILEBLITTING
1675 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1677 Driver for CastleRock integrated graphics core in the
1678 VIA VT8623 [Apollo CLE266] chipset.
1681 tristate "Trident/CyberXXX/CyberBlade support"
1682 depends on FB && PCI
1683 select FB_CFB_FILLRECT
1684 select FB_CFB_COPYAREA
1685 select FB_CFB_IMAGEBLIT
1687 select FB_MODE_HELPERS
1689 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1690 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1692 There are also integrated versions of these chips called CyberXXXX,
1693 CyberImage or CyberBlade. These chips are mostly found in laptops
1694 but also on some motherboards including early VIA EPIA motherboards.
1695 For more information, read <file:Documentation/fb/tridentfb.txt>
1697 Say Y if you have such a graphics board.
1699 To compile this driver as a module, choose M here: the
1700 module will be called tridentfb.
1703 tristate "ARK 2000PV support"
1704 depends on FB && PCI
1705 select FB_CFB_FILLRECT
1706 select FB_CFB_COPYAREA
1707 select FB_CFB_IMAGEBLIT
1708 select FB_TILEBLITTING
1711 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1713 Driver for PCI graphics boards with ARK 2000PV chip
1714 and ICS 5342 RAMDAC.
1717 tristate "Permedia3 support"
1718 depends on FB && PCI
1719 select FB_CFB_FILLRECT
1720 select FB_CFB_COPYAREA
1721 select FB_CFB_IMAGEBLIT
1723 This is the frame buffer device driver for the 3DLabs Permedia3
1724 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1725 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1726 and maybe other boards.
1729 tristate "Fujitsu carmine frame buffer support"
1730 depends on FB && PCI
1731 select FB_CFB_FILLRECT
1732 select FB_CFB_COPYAREA
1733 select FB_CFB_IMAGEBLIT
1735 This is the frame buffer device driver for the Fujitsu Carmine chip.
1736 The driver provides two independent frame buffer devices.
1739 depends on FB_CARMINE
1740 prompt "DRAM timing"
1741 default FB_CARMINE_DRAM_EVAL
1743 config FB_CARMINE_DRAM_EVAL
1744 bool "Eval board timings"
1746 Use timings which work on the eval card.
1748 config CARMINE_DRAM_CUSTOM
1749 bool "Custom board timings"
1751 Use custom board timings.
1755 bool "Au1100 LCD Driver"
1756 depends on (FB = y) && MIPS_ALCHEMY
1757 select FB_CFB_FILLRECT
1758 select FB_CFB_COPYAREA
1759 select FB_CFB_IMAGEBLIT
1761 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1762 various panels and CRTs by passing in kernel cmd line option
1763 au1100fb:panel=<name>.
1766 bool "Au1200/Au1300 LCD Driver"
1767 depends on (FB = y) && MIPS_ALCHEMY
1768 select FB_SYS_FILLRECT
1769 select FB_SYS_COPYAREA
1770 select FB_SYS_IMAGEBLIT
1773 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1774 It can drive various panels and CRTs by passing in kernel cmd line
1775 option au1200fb:panel=<name>.
1778 bool "VIA VT8500 framebuffer support"
1779 depends on (FB = y) && ARM && ARCH_VT8500
1780 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1781 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1782 select FB_SYS_IMAGEBLIT
1783 select FB_MODE_HELPERS
1784 select VIDEOMODE_HELPERS
1786 This is the framebuffer driver for VIA VT8500 integrated LCD
1790 bool "Wondermedia WM8xxx-series frame buffer support"
1791 depends on (FB = y) && ARM && ARCH_VT8500
1792 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1793 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1794 select FB_SYS_IMAGEBLIT
1795 select FB_MODE_HELPERS
1796 select VIDEOMODE_HELPERS
1798 This is the framebuffer driver for WonderMedia WM8xxx-series
1799 integrated LCD controller. This driver covers the WM8505, WM8650
1802 config FB_WMT_GE_ROPS
1803 bool "VT8500/WM8xxx accelerated raster ops support"
1804 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1807 This adds support for accelerated raster operations on the
1808 VIA VT8500 and Wondermedia 85xx series SoCs.
1810 source "drivers/video/fbdev/geode/Kconfig"
1813 tristate "HD64461 Frame Buffer support"
1814 depends on FB && HD64461
1815 select FB_CFB_FILLRECT
1816 select FB_CFB_COPYAREA
1817 select FB_CFB_IMAGEBLIT
1819 This is the frame buffer device driver for the Hitachi HD64461 LCD
1823 tristate "PMAG-AA TURBOchannel framebuffer support"
1825 select FB_CFB_FILLRECT
1826 select FB_CFB_COPYAREA
1827 select FB_CFB_IMAGEBLIT
1829 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1830 used mainly in the MIPS-based DECstation series.
1833 tristate "PMAG-BA TURBOchannel framebuffer support"
1835 select FB_CFB_FILLRECT
1836 select FB_CFB_COPYAREA
1837 select FB_CFB_IMAGEBLIT
1839 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1840 used mainly in the MIPS-based DECstation series.
1843 tristate "PMAGB-B TURBOchannel framebuffer support"
1845 select FB_CFB_FILLRECT
1846 select FB_CFB_COPYAREA
1847 select FB_CFB_IMAGEBLIT
1849 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1850 in the MIPS-based DECstation series. The card is currently only
1851 supported in 1280x1024x8 mode.
1854 bool "Maxine (Personal DECstation) onboard framebuffer support"
1855 depends on (FB = y) && MACH_DECSTATION
1856 select FB_CFB_FILLRECT
1857 select FB_CFB_COPYAREA
1858 select FB_CFB_IMAGEBLIT
1860 Support for the onboard framebuffer (1024x768x8) in the Personal
1861 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1865 bool "G364 frame buffer support"
1866 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1867 select FB_CFB_FILLRECT
1868 select FB_CFB_COPYAREA
1869 select FB_CFB_IMAGEBLIT
1871 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1872 Olivetti M700-10 systems.
1875 bool "Motorola 68328 native frame buffer support"
1876 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1877 select FB_CFB_FILLRECT
1878 select FB_CFB_COPYAREA
1879 select FB_CFB_IMAGEBLIT
1881 Say Y here if you want to support the built-in frame buffer of
1882 the Motorola 68328 CPU family.
1885 tristate "PXA168/910 LCD framebuffer support"
1886 depends on FB && (CPU_PXA168 || CPU_PXA910)
1887 select FB_CFB_FILLRECT
1888 select FB_CFB_COPYAREA
1889 select FB_CFB_IMAGEBLIT
1891 Frame buffer driver for the built-in LCD controller in the Marvell
1895 tristate "PXA LCD framebuffer support"
1896 depends on FB && ARCH_PXA
1897 select FB_CFB_FILLRECT
1898 select FB_CFB_COPYAREA
1899 select FB_CFB_IMAGEBLIT
1900 select VIDEOMODE_HELPERS if OF
1901 select FB_MODE_HELPERS if OF
1903 Frame buffer driver for the built-in LCD controller in the Intel
1906 This driver is also available as a module ( = code which can be
1907 inserted and removed from the running kernel whenever you want). The
1908 module will be called pxafb. If you want to compile it as a module,
1909 say M here and read <file:Documentation/kbuild/modules.txt>.
1913 config FB_PXA_OVERLAY
1914 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1916 depends on FB_PXA && (PXA27x || PXA3xx)
1918 config FB_PXA_SMARTPANEL
1919 bool "PXA Smartpanel LCD support"
1923 config FB_PXA_PARAMETERS
1924 bool "PXA LCD command line parameters"
1928 Enable the use of kernel command line or module parameters
1929 to configure the physical properties of the LCD panel when
1930 using the PXA LCD driver.
1932 This option allows you to override the panel parameters
1933 supplied by the platform in order to support multiple
1934 different models of flatpanel. If you will only be using a
1935 single model of flatpanel then you can safely leave this
1938 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1941 tristate "PXA3xx 2D graphics accelerator driver"
1944 Kernelspace driver for the 2D graphics controller unit (GCU)
1945 found on PXA3xx processors. There is a counterpart driver in the
1946 DirectFB suite, see http://www.directfb.org/
1948 If you compile this as a module, it will be called pxa3xx_gcu.
1951 tristate "2700G LCD framebuffer support"
1952 depends on FB && ARCH_PXA
1953 select FB_CFB_FILLRECT
1954 select FB_CFB_COPYAREA
1955 select FB_CFB_IMAGEBLIT
1957 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1961 bool "Enable debugging info via debugfs"
1962 depends on FB_MBX && DEBUG_FS
1965 Enable this if you want debugging information using the debug
1966 filesystem (debugfs)
1971 tristate "Freescale DIU framebuffer support"
1972 depends on FB && FSL_SOC
1973 select FB_MODE_HELPERS
1974 select FB_CFB_FILLRECT
1975 select FB_CFB_COPYAREA
1976 select FB_CFB_IMAGEBLIT
1977 select PPC_LIB_RHEAP
1979 Framebuffer driver for the Freescale SoC DIU
1982 tristate "W100 frame buffer support"
1983 depends on FB && ARCH_PXA
1984 select FB_CFB_FILLRECT
1985 select FB_CFB_COPYAREA
1986 select FB_CFB_IMAGEBLIT
1988 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1989 It can also drive the w3220 chip found on iPAQ hx4700.
1991 This driver is also available as a module ( = code which can be
1992 inserted and removed from the running kernel whenever you want). The
1993 module will be called w100fb. If you want to compile it as a module,
1994 say M here and read <file:Documentation/kbuild/modules.txt>.
1998 config FB_SH_MOBILE_LCDC
1999 tristate "SuperH Mobile LCDC framebuffer support"
2000 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
2001 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
2002 select FB_SYS_FILLRECT
2003 select FB_SYS_COPYAREA
2004 select FB_SYS_IMAGEBLIT
2006 select FB_DEFERRED_IO
2009 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2012 tristate "Toshiba Mobile IO FrameBuffer support"
2013 depends on FB && (MFD_TMIO || COMPILE_TEST)
2014 select FB_CFB_FILLRECT
2015 select FB_CFB_COPYAREA
2016 select FB_CFB_IMAGEBLIT
2018 Frame buffer driver for the Toshiba Mobile IO integrated as found
2019 on the Sharp SL-6000 series
2021 This driver is also available as a module ( = code which can be
2022 inserted and removed from the running kernel whenever you want). The
2023 module will be called tmiofb. If you want to compile it as a module,
2024 say M here and read <file:Documentation/kbuild/modules.txt>.
2028 config FB_TMIO_ACCELL
2029 bool "tmiofb acceleration"
2034 tristate "Samsung S3C framebuffer support"
2035 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2036 ARCH_S5PV210 || ARCH_EXYNOS)
2037 select FB_CFB_FILLRECT
2038 select FB_CFB_COPYAREA
2039 select FB_CFB_IMAGEBLIT
2041 Frame buffer driver for the built-in FB controller in the Samsung
2042 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2043 and the S3C64XX series such as the S3C6400 and S3C6410.
2045 These chips all have the same basic framebuffer design with the
2046 actual capabilities depending on the chip. For instance the S3C6400
2047 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2048 currently only have two.
2050 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2052 config FB_S3C_DEBUG_REGWRITE
2053 bool "Debug register writes"
2056 Show all register writes via pr_debug()
2059 tristate "S3C2410 LCD framebuffer support"
2060 depends on FB && ARCH_S3C24XX
2061 select FB_CFB_FILLRECT
2062 select FB_CFB_COPYAREA
2063 select FB_CFB_IMAGEBLIT
2065 Frame buffer driver for the built-in LCD controller in the Samsung
2068 This driver is also available as a module ( = code which can be
2069 inserted and removed from the running kernel whenever you want). The
2070 module will be called s3c2410fb. If you want to compile it as a module,
2071 say M here and read <file:Documentation/kbuild/modules.txt>.
2074 config FB_S3C2410_DEBUG
2075 bool "S3C2410 lcd debug messages"
2076 depends on FB_S3C2410
2078 Turn on debugging messages. Note that you can set/unset at run time
2082 tristate "NUC900 LCD framebuffer support"
2083 depends on FB && ARCH_W90X900
2084 select FB_CFB_FILLRECT
2085 select FB_CFB_COPYAREA
2086 select FB_CFB_IMAGEBLIT
2088 Frame buffer driver for the built-in LCD controller in the Nuvoton
2091 config GPM1040A0_320X240
2092 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2093 depends on FB_NUC900
2096 tristate "Silicon Motion SM501 framebuffer support"
2097 depends on FB && MFD_SM501
2098 select FB_CFB_FILLRECT
2099 select FB_CFB_COPYAREA
2100 select FB_CFB_IMAGEBLIT
2102 Frame buffer driver for the CRT and LCD controllers in the Silicon
2105 This driver is also available as a module ( = code which can be
2106 inserted and removed from the running kernel whenever you want). The
2107 module will be called sm501fb. If you want to compile it as a module,
2108 say M here and read <file:Documentation/kbuild/modules.txt>.
2113 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2114 depends on FB && USB
2115 select FB_MODE_HELPERS
2116 select FB_SYS_FILLRECT
2117 select FB_SYS_COPYAREA
2118 select FB_SYS_IMAGEBLIT
2120 select FB_DEFERRED_IO
2122 This is a kernel framebuffer driver for SMSC UFX USB devices.
2123 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2124 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2126 To compile as a module, choose M here: the module name is smscufx.
2129 tristate "Displaylink USB Framebuffer support"
2130 depends on FB && USB
2131 select FB_MODE_HELPERS
2132 select FB_SYS_FILLRECT
2133 select FB_SYS_COPYAREA
2134 select FB_SYS_IMAGEBLIT
2136 select FB_DEFERRED_IO
2138 This is a kernel framebuffer driver for DisplayLink USB devices.
2139 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2140 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2141 To compile as a module, choose M here: the module name is udlfb.
2143 config FB_IBM_GXT4500
2144 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2146 select FB_CFB_FILLRECT
2147 select FB_CFB_COPYAREA
2148 select FB_CFB_IMAGEBLIT
2150 Say Y here to enable support for the IBM GXT4000P/6000P and
2151 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2152 found on some IBM System P (pSeries) machines. This driver
2153 doesn't use Geometry Engine GT1000. This driver also supports
2154 AGP Fire GL2/3/4 cards on x86.
2157 tristate "PS3 GPU framebuffer driver"
2158 depends on FB && PS3_PS3AV
2159 select FB_SYS_FILLRECT
2160 select FB_SYS_COPYAREA
2161 select FB_SYS_IMAGEBLIT
2164 Include support for the virtual frame buffer in the PS3 platform.
2166 config FB_PS3_DEFAULT_SIZE_M
2167 int "PS3 default frame buffer size (in MiB)"
2171 This is the default size (in MiB) of the virtual frame buffer in
2173 The default value can be overridden on the kernel command line
2174 using the "ps3fb" option (e.g. "ps3fb=9M");
2177 tristate "Xilinx frame buffer support"
2178 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2179 select FB_CFB_FILLRECT
2180 select FB_CFB_COPYAREA
2181 select FB_CFB_IMAGEBLIT
2183 Include support for the Xilinx ML300/ML403 reference design
2184 framebuffer. ML300 carries a 640*480 LCD display on the board,
2185 ML403 uses a standard DB15 VGA connector.
2188 tristate "Goldfish Framebuffer"
2189 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2190 select FB_CFB_FILLRECT
2191 select FB_CFB_COPYAREA
2192 select FB_CFB_IMAGEBLIT
2194 Framebuffer driver for Goldfish Virtual Platform
2197 tristate "Cobalt server LCD frame buffer support"
2198 depends on FB && MIPS_COBALT
2201 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2202 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2203 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2204 select FB_CFB_FILLRECT
2205 select FB_CFB_COPYAREA
2206 select FB_CFB_IMAGEBLIT
2208 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2209 (D)STN/TFT LCD Controller.
2210 Supports display resolutions up to 1024x1024 pixel, grayscale and
2211 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2212 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2213 panels <= 320 pixel horizontal resolution.
2216 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2217 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2218 select FB_CFB_FILLRECT
2219 select FB_CFB_COPYAREA
2220 select FB_CFB_IMAGEBLIT
2221 select FB_CFB_REV_PIXELS_IN_BYTE
2222 select FB_MODE_HELPERS
2223 select VIDEOMODE_HELPERS
2225 This is the frame buffer device driver for the TI LCD controller
2226 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2230 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2232 select FB_SYS_FILLRECT
2233 select FB_SYS_COPYAREA
2234 select FB_SYS_IMAGEBLIT
2237 This is a `virtual' frame buffer device. It operates on a chunk of
2238 unswappable kernel memory instead of on the memory of a graphics
2239 board. This means you cannot see any output sent to this frame
2240 buffer device, while it does consume precious memory. The main use
2241 of this frame buffer device is testing and debugging the frame
2242 buffer subsystem. Do NOT enable it for normal systems! To protect
2243 the innocent, it has to be enabled explicitly at boot time using the
2244 kernel option `video=vfb:'.
2246 To compile this driver as a module, choose M here: the
2247 module will be called vfb. In order to load it, you must use
2248 the vfb_enable=1 option.
2252 config XEN_FBDEV_FRONTEND
2253 tristate "Xen virtual frame buffer support"
2254 depends on FB && XEN
2255 select FB_SYS_FILLRECT
2256 select FB_SYS_COPYAREA
2257 select FB_SYS_IMAGEBLIT
2259 select FB_DEFERRED_IO
2260 select XEN_XENBUS_FRONTEND
2263 This driver implements the front-end of the Xen virtual
2264 frame buffer driver. It communicates with a back-end
2268 tristate "E-Ink Metronome/8track controller support"
2270 select FB_SYS_FILLRECT
2271 select FB_SYS_COPYAREA
2272 select FB_SYS_IMAGEBLIT
2274 select FB_DEFERRED_IO
2276 This driver implements support for the E-Ink Metronome
2277 controller. The pre-release name for this device was 8track
2278 and could also have been called by some vendors as PVI-nnnn.
2281 tristate "Fujitsu MB862xx GDC support"
2283 depends on PCI || (OF && PPC)
2284 select FB_CFB_FILLRECT
2285 select FB_CFB_COPYAREA
2286 select FB_CFB_IMAGEBLIT
2288 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2291 prompt "GDC variant"
2292 depends on FB_MB862XX
2294 config FB_MB862XX_PCI_GDC
2295 bool "Carmine/Coral-P(A) GDC"
2298 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2299 PCI graphics controller devices.
2301 config FB_MB862XX_LIME
2303 depends on OF && PPC
2304 select FB_FOREIGN_ENDIAN
2305 select FB_LITTLE_ENDIAN
2307 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2311 config FB_MB862XX_I2C
2312 bool "Support I2C bus on MB862XX GDC"
2313 depends on FB_MB862XX && I2C
2314 depends on FB_MB862XX=m || I2C=y
2317 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2318 driver to support accessing I2C devices on controller's I2C bus.
2319 These are usually some video decoder chips.
2322 tristate "EP93XX frame buffer support"
2323 depends on FB && ARCH_EP93XX
2324 select FB_CFB_FILLRECT
2325 select FB_CFB_COPYAREA
2326 select FB_CFB_IMAGEBLIT
2328 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2329 This driver is also available as a module. The module will be called
2332 config FB_PRE_INIT_FB
2333 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2334 depends on FB && FB_MB862XX_LIME
2336 Select this option if display contents should be inherited as set by
2340 tristate "MX3 Framebuffer support"
2341 depends on FB && MX3_IPU
2342 select BACKLIGHT_CLASS_DEVICE
2343 select BACKLIGHT_LCD_SUPPORT
2344 select FB_CFB_FILLRECT
2345 select FB_CFB_COPYAREA
2346 select FB_CFB_IMAGEBLIT
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 || ARCH_MXC)
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/mmp/Kconfig"
2460 config FB_SH_MOBILE_MERAM
2461 tristate "SuperH Mobile MERAM read ahead support"
2462 depends on (SUPERH || ARCH_SHMOBILE)
2463 select GENERIC_ALLOCATOR
2465 Enable MERAM support for the SuperH controller.
2467 This will allow for caching of the framebuffer to provide more
2468 reliable access under heavy main memory bus traffic situations.
2469 Up to 4 memory channels can be configured, allowing 4 RGB or
2470 2 YCbCr framebuffers to be configured.
2473 tristate "Solomon SSD1307 framebuffer support"
2474 depends on FB && I2C
2476 depends on GPIOLIB || COMPILE_TEST
2478 select FB_SYS_FILLRECT
2479 select FB_SYS_COPYAREA
2480 select FB_SYS_IMAGEBLIT
2481 select FB_DEFERRED_IO
2485 This driver implements support for the Solomon SSD1307
2486 OLED controller over I2C.
2489 tristate "Silicon Motion SM712 framebuffer support"
2490 depends on FB && PCI
2491 select FB_CFB_FILLRECT
2492 select FB_CFB_COPYAREA
2493 select FB_CFB_IMAGEBLIT
2495 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2498 This driver is also available as a module. The module will be
2499 called sm712fb. If you want to compile it as a module, say M
2500 here and read <file:Documentation/kbuild/modules.txt>.