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
694 STI refers to the HP "Standard Text Interface" which is a set of
695 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
696 Enabling this option will implement the linux framebuffer device
697 using calls to the STI BIOS routines for initialisation.
699 If you enable this option, you will get a planar framebuffer device
700 /dev/fb which will work on the most common HP graphic cards of the
701 NGLE family, including the artist chips (in the 7xx and Bxxx series),
702 HCRX, HCRX24, CRX, CRX24 and VisEG series.
704 It is safe to enable this option, so you should probably say "Y".
707 bool "Generic Macintosh display support"
708 depends on (FB = y) && MAC
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
716 depends on (FB = y) && DIO
717 select FB_CFB_IMAGEBLIT
721 tristate "TGA/SFB+ framebuffer support"
722 depends on FB && (ALPHA || TC)
723 select FB_CFB_FILLRECT
724 select FB_CFB_COPYAREA
725 select FB_CFB_IMAGEBLIT
728 This is the frame buffer device driver for generic TGA and SFB+
729 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
730 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
731 TURBOchannel cards, also known as PMAGD-A, -B and -C.
733 Due to hardware limitations ZLX-E2 and E3 cards are not supported
734 for DECstation 5000/200 systems. Additionally due to firmware
735 limitations these cards may cause troubles with booting DECstation
736 5000/240 and /260 systems, but are fully supported under Linux if
737 you manage to get it going. ;-)
739 Say Y if you have one of those.
742 tristate "Userspace VESA VGA graphics support"
743 depends on FB && CONNECTOR
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
747 select FB_MODE_HELPERS
749 This is the frame buffer driver for generic VBE 2.0 compliant
750 graphic cards. It can also take advantage of VBE 3.0 features,
751 such as refresh rate adjustment.
753 This driver generally provides more features than vesafb but
754 requires a userspace helper application called 'v86d'. See
755 <file:Documentation/fb/uvesafb.txt> for more information.
760 bool "VESA VGA graphics support"
761 depends on (FB = y) && X86
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
765 select FB_BOOT_VESA_SUPPORT
767 This is the frame buffer device driver for generic VESA 2.0
768 compliant graphic cards. The older VESA 1.2 cards are not supported.
769 You will get a boot time penguin logo at no additional cost. Please
770 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
773 bool "EFI-based Framebuffer Support"
774 depends on (FB = y) && !IA64 && EFI
775 select FB_CFB_FILLRECT
776 select FB_CFB_COPYAREA
777 select FB_CFB_IMAGEBLIT
779 This is the EFI frame buffer device driver. If the firmware on
780 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
781 using the EFI framebuffer as your console.
784 tristate "N411 Apollo/Hecuba devkit support"
785 depends on FB && X86 && MMU
786 select FB_SYS_FILLRECT
787 select FB_SYS_COPYAREA
788 select FB_SYS_IMAGEBLIT
790 select FB_DEFERRED_IO
793 This enables support for the Apollo display controller in its
794 Hecuba form using the n411 devkit.
797 tristate "Hercules mono graphics support"
800 Say Y here if you have a Hercules mono graphics card.
802 To compile this driver as a module, choose M here: the
803 module will be called hgafb.
805 As this card technology is at least 25 years old,
806 most people will answer N here.
809 bool "SGI Graphics Backend frame buffer support"
810 depends on (FB = y) && SGI_IP32
811 select FB_CFB_FILLRECT
812 select FB_CFB_COPYAREA
813 select FB_CFB_IMAGEBLIT
815 This is the frame buffer device driver for SGI Graphics Backend.
816 This chip is used in SGI O2 and Visual Workstation 320/540.
819 int "Video memory size in MB"
823 This is the amount of memory reserved for the framebuffer,
824 which can be any value between 1MB and 8MB.
827 bool "SBUS and UPA framebuffers"
828 depends on (FB = y) && SPARC
830 Say Y if you want support for SBUS or UPA based frame buffer device.
834 depends on (FB = y) && (SPARC && FB_SBUS)
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
839 This is the frame buffer device driver for the BWtwo frame buffer.
842 bool "CGthree support"
843 depends on (FB = y) && (SPARC && FB_SBUS)
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This is the frame buffer device driver for the CGthree frame buffer.
851 bool "CGsix (GX,TurboGX) support"
852 depends on (FB = y) && (SPARC && FB_SBUS)
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
856 This is the frame buffer device driver for the CGsix (GX, TurboGX)
860 bool "Creator/Creator3D/Elite3D support"
861 depends on FB_SBUS && SPARC64
862 select FB_CFB_COPYAREA
863 select FB_CFB_IMAGEBLIT
865 This is the frame buffer device driver for the Creator, Creator3D,
866 and Elite3D graphics boards.
869 bool "TCX (SS4/SS5 only) support"
871 select FB_CFB_FILLRECT
872 select FB_CFB_COPYAREA
873 select FB_CFB_IMAGEBLIT
875 This is the frame buffer device driver for the TCX 24/8bit frame
879 bool "CGfourteen (SX) support"
881 select FB_CFB_FILLRECT
882 select FB_CFB_COPYAREA
883 select FB_CFB_IMAGEBLIT
885 This is the frame buffer device driver for the CGfourteen frame
886 buffer on Desktop SPARCsystems with the SX graphics option.
889 bool "P9100 (Sparcbook 3 only) support"
891 select FB_CFB_FILLRECT
892 select FB_CFB_COPYAREA
893 select FB_CFB_IMAGEBLIT
895 This is the frame buffer device driver for the P9100 card
896 supported on Sparcbook 3 machines.
899 bool "Leo (ZX) support"
901 select FB_CFB_FILLRECT
902 select FB_CFB_COPYAREA
903 select FB_CFB_IMAGEBLIT
905 This is the frame buffer device driver for the SBUS-based Sun ZX
906 (leo) frame buffer cards.
909 bool "IGA 168x display support"
910 depends on (FB = y) && SPARC32
911 select FB_CFB_FILLRECT
912 select FB_CFB_COPYAREA
913 select FB_CFB_IMAGEBLIT
915 This is the framebuffer device for the INTERGRAPHICS 1680 and
916 successor frame buffer cards.
919 bool "Sun XVR-500 3DLABS Wildcat support"
920 depends on (FB = y) && PCI && SPARC64
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
925 This is the framebuffer device for the Sun XVR-500 and similar
926 graphics cards based upon the 3DLABS Wildcat chipset. The driver
927 only works on sparc64 systems where the system firmware has
928 mostly initialized the card already. It is treated as a
929 completely dumb framebuffer device.
932 bool "Sun XVR-2500 3DLABS Wildcat support"
933 depends on (FB = y) && PCI && SPARC64
934 select FB_CFB_FILLRECT
935 select FB_CFB_COPYAREA
936 select FB_CFB_IMAGEBLIT
938 This is the framebuffer device for the Sun XVR-2500 and similar
939 graphics cards based upon the 3DLABS Wildcat chipset. The driver
940 only works on sparc64 systems where the system firmware has
941 mostly initialized the card already. It is treated as a
942 completely dumb framebuffer device.
945 bool "Sun XVR-1000 support"
946 depends on (FB = y) && SPARC64
947 select FB_CFB_FILLRECT
948 select FB_CFB_COPYAREA
949 select FB_CFB_IMAGEBLIT
951 This is the framebuffer device for the Sun XVR-1000 and similar
952 graphics cards. The driver only works on sparc64 systems where
953 the system firmware has mostly initialized the card already. It
954 is treated as a completely dumb framebuffer device.
957 tristate "NEC PowerVR 2 display support"
958 depends on FB && SH_DREAMCAST
959 select FB_CFB_FILLRECT
960 select FB_CFB_COPYAREA
961 select FB_CFB_IMAGEBLIT
963 Say Y here if you have a PowerVR 2 card in your box. If you plan to
964 run linux on your Dreamcast, you will have to say Y here.
965 This driver may or may not work on other PowerVR 2 cards, but is
966 totally untested. Use at your own risk. If unsure, say N.
968 To compile this driver as a module, choose M here: the
969 module will be called pvr2fb.
971 You can pass several parameters to the driver at boot time or at
972 module load time. The parameters look like "video=pvr2:XXX", where
973 the meaning of XXX can be found at the end of the main source file
974 (<file:drivers/video/pvr2fb.c>). Please see the file
975 <file:Documentation/fb/pvr2fb.txt>.
978 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
979 depends on FB && HAS_DMA
980 select FB_CFB_FILLRECT
981 select FB_CFB_COPYAREA
982 select FB_CFB_IMAGEBLIT
984 This enables support for the OpenCores VGA/LCD core.
986 The OpenCores VGA/LCD core is typically used together with
987 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
988 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
990 The source code and specification for the core is available at
991 <http://opencores.org/project,vga_lcd>
994 tristate "Epson S1D13XXX framebuffer support"
996 select FB_CFB_FILLRECT
997 select FB_CFB_COPYAREA
998 select FB_CFB_IMAGEBLIT
1000 Support for S1D13XXX framebuffer device family (currently only
1001 working with S1D13806). Product specs at
1002 <http://vdc.epson.com/>
1005 tristate "AT91/AT32 LCD Controller support"
1006 depends on FB && HAVE_FB_ATMEL
1008 select FB_CFB_FILLRECT
1009 select FB_CFB_COPYAREA
1010 select FB_CFB_IMAGEBLIT
1011 select FB_MODE_HELPERS
1012 select VIDEOMODE_HELPERS
1014 This enables support for the AT91/AT32 LCD Controller.
1017 tristate "nVidia Framebuffer Support"
1018 depends on FB && PCI
1019 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1020 select FB_MODE_HELPERS
1021 select FB_CFB_FILLRECT
1022 select FB_CFB_COPYAREA
1023 select FB_CFB_IMAGEBLIT
1027 This driver supports graphics boards with the nVidia chips, TNT
1028 and newer. For very old chipsets, such as the RIVA128, then use
1030 Say Y if you have such a graphics board.
1032 To compile this driver as a module, choose M here: the
1033 module will be called nvidiafb.
1035 config FB_NVIDIA_I2C
1036 bool "Enable DDC Support"
1037 depends on FB_NVIDIA
1040 This enables I2C support for nVidia Chipsets. This is used
1041 only for getting EDID information from the attached display
1042 allowing for robust video mode handling and switching.
1044 Because fbdev-2.6 requires that drivers must be able to
1045 independently validate video mode parameters, you should say Y
1048 config FB_NVIDIA_DEBUG
1049 bool "Lots of debug output"
1050 depends on FB_NVIDIA
1053 Say Y here if you want the nVidia driver to output all sorts
1054 of debugging information to provide to the maintainer when
1055 something goes wrong.
1057 config FB_NVIDIA_BACKLIGHT
1058 bool "Support for backlight control"
1059 depends on FB_NVIDIA
1062 Say Y here if you want to control the backlight of your display.
1065 tristate "nVidia Riva support"
1066 depends on FB && PCI
1067 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1068 select FB_MODE_HELPERS
1069 select FB_CFB_FILLRECT
1070 select FB_CFB_COPYAREA
1071 select FB_CFB_IMAGEBLIT
1075 This driver supports graphics boards with the nVidia Riva/Geforce
1077 Say Y if you have such a graphics board.
1079 To compile this driver as a module, choose M here: the
1080 module will be called rivafb.
1083 bool "Enable DDC Support"
1087 This enables I2C support for nVidia Chipsets. This is used
1088 only for getting EDID information from the attached display
1089 allowing for robust video mode handling and switching.
1091 Because fbdev-2.6 requires that drivers must be able to
1092 independently validate video mode parameters, you should say Y
1095 config FB_RIVA_DEBUG
1096 bool "Lots of debug output"
1100 Say Y here if you want the Riva driver to output all sorts
1101 of debugging information to provide to the maintainer when
1102 something goes wrong.
1104 config FB_RIVA_BACKLIGHT
1105 bool "Support for backlight control"
1109 Say Y here if you want to control the backlight of your display.
1112 tristate "Intel740 support"
1113 depends on FB && PCI
1114 select FB_MODE_HELPERS
1115 select FB_CFB_FILLRECT
1116 select FB_CFB_COPYAREA
1117 select FB_CFB_IMAGEBLIT
1121 This driver supports graphics cards based on Intel740 chip.
1124 tristate "Intel 810/815 support"
1125 depends on FB && PCI && X86_32 && AGP_INTEL
1126 select FB_MODE_HELPERS
1127 select FB_CFB_FILLRECT
1128 select FB_CFB_COPYAREA
1129 select FB_CFB_IMAGEBLIT
1132 This driver supports the on-board graphics built in to the Intel 810
1133 and 815 chipsets. Say Y if you have and plan to use such a board.
1135 To compile this driver as a module, choose M here: the
1136 module will be called i810fb.
1138 For more information, please read
1139 <file:Documentation/fb/intel810.txt>
1142 bool "use VESA Generalized Timing Formula"
1145 If you say Y, then the VESA standard, Generalized Timing Formula
1146 or GTF, will be used to calculate the required video timing values
1147 per video mode. Since the GTF allows nondiscrete timings
1148 (nondiscrete being a range of values as opposed to discrete being a
1149 set of values), you'll be able to use any combination of horizontal
1150 and vertical resolutions, and vertical refresh rates without having
1151 to specify your own timing parameters. This is especially useful
1152 to maximize the performance of an aging display, or if you just
1153 have a display with nonstandard dimensions. A VESA compliant
1154 monitor is recommended, but can still work with non-compliant ones.
1155 If you need or want this, then select this option. The timings may
1156 not be compliant with Intel's recommended values. Use at your own
1159 If you say N, the driver will revert to discrete video timings
1160 using a set recommended by Intel in their documentation.
1165 bool "Enable DDC Support"
1166 depends on FB_I810 && FB_I810_GTF
1171 tristate "Intel LE80578 (Vermilion) support"
1172 depends on FB && PCI && X86
1173 select FB_MODE_HELPERS
1174 select FB_CFB_FILLRECT
1175 select FB_CFB_COPYAREA
1176 select FB_CFB_IMAGEBLIT
1178 This driver supports the LE80578 (Vermilion Range) chipset
1180 config FB_CARILLO_RANCH
1181 tristate "Intel Carillo Ranch support"
1182 depends on FB_LE80578 && FB && PCI && X86
1184 This driver supports the LE80578 (Carillo Ranch) board
1187 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1188 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1189 select FB_MODE_HELPERS
1190 select FB_CFB_FILLRECT
1191 select FB_CFB_COPYAREA
1192 select FB_CFB_IMAGEBLIT
1193 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1194 depends on !DRM_I915
1196 This driver supports the on-board graphics built in to the Intel
1197 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1198 Say Y if you have and plan to use such a board.
1200 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1202 To compile this driver as a module, choose M here: the
1203 module will be called intelfb.
1205 For more information, please read <file:Documentation/fb/intelfb.txt>
1207 config FB_INTEL_DEBUG
1208 bool "Intel driver Debug Messages"
1211 Say Y here if you want the Intel driver to output all sorts
1212 of debugging information to provide to the maintainer when
1213 something goes wrong.
1216 bool "DDC/I2C for Intel framebuffer support"
1221 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1224 tristate "Matrox acceleration"
1225 depends on FB && PCI
1226 select FB_CFB_FILLRECT
1227 select FB_CFB_COPYAREA
1228 select FB_CFB_IMAGEBLIT
1229 select FB_TILEBLITTING
1230 select FB_MACMODES if PPC_PMAC
1232 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1233 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1234 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1235 Matrox G400, G450 or G550 card in your box.
1237 To compile this driver as a module, choose M here: the
1238 module will be called matroxfb.
1240 You can pass several parameters to the driver at boot time or at
1241 module load time. The parameters look like "video=matroxfb:XXX", and
1242 are described in <file:Documentation/fb/matroxfb.txt>.
1244 config FB_MATROX_MILLENIUM
1245 bool "Millennium I/II support"
1246 depends on FB_MATROX
1248 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1249 video card. If you select "Advanced lowlevel driver options" below,
1250 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1251 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1252 also use font widths different from 8.
1254 config FB_MATROX_MYSTIQUE
1255 bool "Mystique support"
1256 depends on FB_MATROX
1258 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1259 video card. If you select "Advanced lowlevel driver options" below,
1260 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1261 packed pixel and 32 bpp packed pixel. You can also use font widths
1265 bool "G100/G200/G400/G450/G550 support"
1266 depends on FB_MATROX
1268 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1269 video card. If you select "Advanced lowlevel driver options", you
1270 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1271 pixel and 32 bpp packed pixel. You can also use font widths
1274 If you need support for G400 secondary head, you must say Y to
1275 "Matrox I2C support" and "G400 second head support" right below.
1276 G450/G550 secondary head and digital output are supported without
1279 The driver starts in monitor mode. You must use the matroxset tool
1280 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1281 swap primary and secondary head outputs, or to change output mode.
1282 Secondary head driver always start in 640x480 resolution and you
1283 must use fbset to change it.
1285 Do not forget that second head supports only 16 and 32 bpp
1286 packed pixels, so it is a good idea to compile them into the kernel
1287 too. You can use only some font widths, as the driver uses generic
1288 painting procedures (the secondary head does not use acceleration
1291 G450/G550 hardware can display TV picture only from secondary CRTC,
1292 and it performs no scaling, so picture must have 525 or 625 lines.
1294 config FB_MATROX_I2C
1295 tristate "Matrox I2C support"
1296 depends on FB_MATROX
1299 This drivers creates I2C buses which are needed for accessing the
1300 DDC (I2C) bus present on all Matroxes, an I2C bus which
1301 interconnects Matrox optional devices, like MGA-TVO on G200 and
1302 G400, and the secondary head DDC bus, present on G400 only.
1304 You can say Y or M here if you want to experiment with monitor
1305 detection code. You must say Y or M here if you want to use either
1306 second head of G400 or MGA-TVO on G200 or G400.
1308 If you compile it as module, it will create a module named
1311 config FB_MATROX_MAVEN
1312 tristate "G400 second head support"
1313 depends on FB_MATROX_G && FB_MATROX_I2C
1315 WARNING !!! This support does not work with G450 !!!
1317 Say Y or M here if you want to use a secondary head (meaning two
1318 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1319 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1320 secondary head output is blanked while you are in X. With XFree
1321 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1322 the fbdev driver on first head and the fbdev driver on second head.
1324 If you compile it as module, two modules are created,
1325 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1326 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1327 also load i2c-matroxfb to get it to run.
1329 The driver starts in monitor mode and you must use the matroxset
1331 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1332 PAL or NTSC or to swap primary and secondary head outputs.
1333 Secondary head driver also always start in 640x480 resolution, you
1334 must use fbset to change it.
1336 Also do not forget that second head supports only 16 and 32 bpp
1337 packed pixels, so it is a good idea to compile them into the kernel
1338 too. You can use only some font widths, as the driver uses generic
1339 painting procedures (the secondary head does not use acceleration
1343 tristate "ATI Radeon display support"
1344 depends on FB && PCI
1345 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1346 select FB_MODE_HELPERS
1347 select FB_CFB_FILLRECT
1348 select FB_CFB_COPYAREA
1349 select FB_CFB_IMAGEBLIT
1350 select FB_MACMODES if PPC
1352 Choose this option if you want to use an ATI Radeon graphics card as
1353 a framebuffer device. There are both PCI and AGP versions. You
1354 don't need to choose this to run the Radeon in plain VGA mode.
1356 There is a product page at
1357 http://products.amd.com/en-us/GraphicCardResult.aspx
1359 config FB_RADEON_I2C
1360 bool "DDC/I2C for ATI Radeon support"
1361 depends on FB_RADEON
1365 Say Y here if you want DDC/I2C support for your Radeon board.
1367 config FB_RADEON_BACKLIGHT
1368 bool "Support for backlight control"
1369 depends on FB_RADEON
1372 Say Y here if you want to control the backlight of your display.
1374 config FB_RADEON_DEBUG
1375 bool "Lots of debug output from Radeon driver"
1376 depends on FB_RADEON
1379 Say Y here if you want the Radeon driver to output all sorts
1380 of debugging information to provide to the maintainer when
1381 something goes wrong.
1384 tristate "ATI Rage128 display support"
1385 depends on FB && PCI
1386 select FB_CFB_FILLRECT
1387 select FB_CFB_COPYAREA
1388 select FB_CFB_IMAGEBLIT
1389 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1390 select FB_MACMODES if PPC_PMAC
1392 This driver supports graphics boards with the ATI Rage128 chips.
1393 Say Y if you have such a graphics board and read
1394 <file:Documentation/fb/aty128fb.txt>.
1396 To compile this driver as a module, choose M here: the
1397 module will be called aty128fb.
1399 config FB_ATY128_BACKLIGHT
1400 bool "Support for backlight control"
1401 depends on FB_ATY128
1404 Say Y here if you want to control the backlight of your display.
1407 tristate "ATI Mach64 display support" if PCI || ATARI
1408 depends on FB && !SPARC32
1409 select FB_CFB_FILLRECT
1410 select FB_CFB_COPYAREA
1411 select FB_CFB_IMAGEBLIT
1412 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1413 select FB_MACMODES if PPC
1415 This driver supports graphics boards with the ATI Mach64 chips.
1416 Say Y if you have such a graphics board.
1418 To compile this driver as a module, choose M here: the
1419 module will be called atyfb.
1422 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1423 depends on PCI && FB_ATY
1424 default y if SPARC64 && PCI
1426 Say Y here to support use of ATI's 64-bit Rage boards (or other
1427 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1428 framebuffer device. The ATI product support page for these boards
1429 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1431 config FB_ATY_GENERIC_LCD
1432 bool "Mach64 generic LCD support"
1433 depends on FB_ATY_CT
1435 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1436 Rage XC, or Rage XL chipset.
1439 bool "Mach64 GX support" if PCI
1443 Say Y here to support use of the ATI Mach64 Graphics Expression
1444 board (or other boards based on the Mach64 GX chipset) as a
1445 framebuffer device. The ATI product support page for these boards
1447 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1449 config FB_ATY_BACKLIGHT
1450 bool "Support for backlight control"
1454 Say Y here if you want to control the backlight of your display.
1457 tristate "S3 Trio/Virge support"
1458 depends on FB && PCI
1459 select FB_CFB_FILLRECT
1460 select FB_CFB_COPYAREA
1461 select FB_CFB_IMAGEBLIT
1462 select FB_TILEBLITTING
1465 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1467 Driver for graphics boards with S3 Trio / S3 Virge chip.
1470 bool "DDC for S3 support"
1475 Say Y here if you want DDC support for your S3 graphics card.
1478 tristate "S3 Savage support"
1479 depends on FB && PCI
1480 select FB_MODE_HELPERS
1481 select FB_CFB_FILLRECT
1482 select FB_CFB_COPYAREA
1483 select FB_CFB_IMAGEBLIT
1486 This driver supports notebooks and computers with S3 Savage PCI/AGP
1489 Say Y if you have such a graphics card.
1491 To compile this driver as a module, choose M here; the module
1492 will be called savagefb.
1494 config FB_SAVAGE_I2C
1495 bool "Enable DDC2 Support"
1496 depends on FB_SAVAGE
1499 This enables I2C support for S3 Savage Chipsets. This is used
1500 only for getting EDID information from the attached display
1501 allowing for robust video mode handling and switching.
1503 Because fbdev-2.6 requires that drivers must be able to
1504 independently validate video mode parameters, you should say Y
1507 config FB_SAVAGE_ACCEL
1508 bool "Enable Console Acceleration"
1509 depends on FB_SAVAGE
1512 This option will compile in console acceleration support. If
1513 the resulting framebuffer console has bothersome glitches, then
1517 tristate "SiS/XGI display support"
1518 depends on FB && PCI
1519 select FB_CFB_FILLRECT
1520 select FB_CFB_COPYAREA
1521 select FB_CFB_IMAGEBLIT
1522 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1523 select FB_SIS_300 if !FB_SIS_315
1525 This is the frame buffer device driver for the SiS 300, 315, 330
1526 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1527 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1529 To compile this driver as a module, choose M here; the module
1530 will be called sisfb.
1533 bool "SiS 300 series support"
1536 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1539 bool "SiS 315/330/340 series and XGI support"
1542 Say Y here to support use of the SiS 315, 330 and 340 series
1543 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1544 as XGI V3XT, V5, V8 and Z7.
1547 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1548 depends on FB && PCI && X86 && GPIOLIB && I2C
1549 select FB_CFB_FILLRECT
1550 select FB_CFB_COPYAREA
1551 select FB_CFB_IMAGEBLIT
1554 This is the frame buffer device driver for Graphics chips of VIA
1555 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1556 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1558 Say Y if you have a VIA UniChrome graphics board.
1560 To compile this driver as a module, choose M here: the
1561 module will be called viafb.
1565 config FB_VIA_DIRECT_PROCFS
1566 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1570 Allow direct hardware access to some output registers via procfs.
1571 This is dangerous but may provide the only chance to get the
1572 correct output device configuration.
1573 Its use is strongly discouraged.
1575 config FB_VIA_X_COMPATIBILITY
1576 bool "X server compatibility"
1580 This option reduces the functionality (power saving, ...) of the
1581 framebuffer to avoid negative impact on the OpenChrome X server.
1582 If you use any X server other than fbdev you should enable this
1583 otherwise it should be safe to disable it and allow using all
1589 tristate "NeoMagic display support"
1590 depends on FB && PCI
1591 select FB_MODE_HELPERS
1592 select FB_CFB_FILLRECT
1593 select FB_CFB_COPYAREA
1594 select FB_CFB_IMAGEBLIT
1597 This driver supports notebooks with NeoMagic PCI chips.
1598 Say Y if you have such a graphics card.
1600 To compile this driver as a module, choose M here: the
1601 module will be called neofb.
1604 tristate "IMG Kyro support"
1605 depends on FB && PCI
1606 select FB_CFB_FILLRECT
1607 select FB_CFB_COPYAREA
1608 select FB_CFB_IMAGEBLIT
1610 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1613 To compile this driver as a module, choose M here: the
1614 module will be called kyrofb.
1617 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1618 depends on FB && PCI
1619 select FB_CFB_IMAGEBLIT
1620 select FB_CFB_FILLRECT
1621 select FB_CFB_COPYAREA
1622 select FB_MODE_HELPERS
1624 This driver supports graphics boards with the 3Dfx Banshee,
1625 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1626 such a graphics board.
1628 To compile this driver as a module, choose M here: the
1629 module will be called tdfxfb.
1631 config FB_3DFX_ACCEL
1632 bool "3Dfx Acceleration functions"
1635 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1636 device driver with acceleration functions.
1639 bool "Enable DDC/I2C support"
1644 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1647 tristate "3Dfx Voodoo Graphics (sst1) support"
1648 depends on FB && PCI
1649 select FB_CFB_FILLRECT
1650 select FB_CFB_COPYAREA
1651 select FB_CFB_IMAGEBLIT
1653 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1654 Voodoo2 (cvg) based graphics card.
1656 To compile this driver as a module, choose M here: the
1657 module will be called sstfb.
1659 WARNING: Do not use any application that uses the 3D engine
1660 (namely glide) while using this driver.
1661 Please read the <file:Documentation/fb/sstfb.txt> for supported
1662 options and other important info support.
1665 tristate "VIA VT8623 support"
1666 depends on FB && PCI
1667 select FB_CFB_FILLRECT
1668 select FB_CFB_COPYAREA
1669 select FB_CFB_IMAGEBLIT
1670 select FB_TILEBLITTING
1673 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1675 Driver for CastleRock integrated graphics core in the
1676 VIA VT8623 [Apollo CLE266] chipset.
1679 tristate "Trident/CyberXXX/CyberBlade support"
1680 depends on FB && PCI
1681 select FB_CFB_FILLRECT
1682 select FB_CFB_COPYAREA
1683 select FB_CFB_IMAGEBLIT
1685 select FB_MODE_HELPERS
1687 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1688 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1690 There are also integrated versions of these chips called CyberXXXX,
1691 CyberImage or CyberBlade. These chips are mostly found in laptops
1692 but also on some motherboards including early VIA EPIA motherboards.
1693 For more information, read <file:Documentation/fb/tridentfb.txt>
1695 Say Y if you have such a graphics board.
1697 To compile this driver as a module, choose M here: the
1698 module will be called tridentfb.
1701 tristate "ARK 2000PV support"
1702 depends on FB && PCI
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1706 select FB_TILEBLITTING
1709 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1711 Driver for PCI graphics boards with ARK 2000PV chip
1712 and ICS 5342 RAMDAC.
1715 tristate "Permedia3 support"
1716 depends on FB && PCI
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1721 This is the frame buffer device driver for the 3DLabs Permedia3
1722 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1723 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1724 and maybe other boards.
1727 tristate "Fujitsu carmine frame buffer support"
1728 depends on FB && PCI
1729 select FB_CFB_FILLRECT
1730 select FB_CFB_COPYAREA
1731 select FB_CFB_IMAGEBLIT
1733 This is the frame buffer device driver for the Fujitsu Carmine chip.
1734 The driver provides two independent frame buffer devices.
1737 depends on FB_CARMINE
1738 prompt "DRAM timing"
1739 default FB_CARMINE_DRAM_EVAL
1741 config FB_CARMINE_DRAM_EVAL
1742 bool "Eval board timings"
1744 Use timings which work on the eval card.
1746 config CARMINE_DRAM_CUSTOM
1747 bool "Custom board timings"
1749 Use custom board timings.
1753 bool "Au1100 LCD Driver"
1754 depends on (FB = y) && MIPS_ALCHEMY
1755 select FB_CFB_FILLRECT
1756 select FB_CFB_COPYAREA
1757 select FB_CFB_IMAGEBLIT
1759 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1760 various panels and CRTs by passing in kernel cmd line option
1761 au1100fb:panel=<name>.
1764 bool "Au1200/Au1300 LCD Driver"
1765 depends on (FB = y) && MIPS_ALCHEMY
1766 select FB_SYS_FILLRECT
1767 select FB_SYS_COPYAREA
1768 select FB_SYS_IMAGEBLIT
1771 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1772 It can drive various panels and CRTs by passing in kernel cmd line
1773 option au1200fb:panel=<name>.
1776 bool "VIA VT8500 framebuffer support"
1777 depends on (FB = y) && ARM && ARCH_VT8500
1778 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1779 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1780 select FB_SYS_IMAGEBLIT
1781 select FB_MODE_HELPERS
1782 select VIDEOMODE_HELPERS
1784 This is the framebuffer driver for VIA VT8500 integrated LCD
1788 bool "Wondermedia WM8xxx-series frame buffer support"
1789 depends on (FB = y) && ARM && ARCH_VT8500
1790 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1791 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1792 select FB_SYS_IMAGEBLIT
1793 select FB_MODE_HELPERS
1794 select VIDEOMODE_HELPERS
1796 This is the framebuffer driver for WonderMedia WM8xxx-series
1797 integrated LCD controller. This driver covers the WM8505, WM8650
1800 config FB_WMT_GE_ROPS
1801 bool "VT8500/WM8xxx accelerated raster ops support"
1802 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1805 This adds support for accelerated raster operations on the
1806 VIA VT8500 and Wondermedia 85xx series SoCs.
1808 source "drivers/video/fbdev/geode/Kconfig"
1811 tristate "HD64461 Frame Buffer support"
1812 depends on FB && HD64461
1813 select FB_CFB_FILLRECT
1814 select FB_CFB_COPYAREA
1815 select FB_CFB_IMAGEBLIT
1817 This is the frame buffer device driver for the Hitachi HD64461 LCD
1821 tristate "PMAG-AA TURBOchannel framebuffer support"
1823 select FB_CFB_FILLRECT
1824 select FB_CFB_COPYAREA
1825 select FB_CFB_IMAGEBLIT
1827 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1828 used mainly in the MIPS-based DECstation series.
1831 tristate "PMAG-BA TURBOchannel framebuffer support"
1833 select FB_CFB_FILLRECT
1834 select FB_CFB_COPYAREA
1835 select FB_CFB_IMAGEBLIT
1837 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1838 used mainly in the MIPS-based DECstation series.
1841 tristate "PMAGB-B TURBOchannel framebuffer support"
1843 select FB_CFB_FILLRECT
1844 select FB_CFB_COPYAREA
1845 select FB_CFB_IMAGEBLIT
1847 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1848 in the MIPS-based DECstation series. The card is currently only
1849 supported in 1280x1024x8 mode.
1852 bool "Maxine (Personal DECstation) onboard framebuffer support"
1853 depends on (FB = y) && MACH_DECSTATION
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Support for the onboard framebuffer (1024x768x8) in the Personal
1859 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1863 bool "G364 frame buffer support"
1864 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1865 select FB_CFB_FILLRECT
1866 select FB_CFB_COPYAREA
1867 select FB_CFB_IMAGEBLIT
1869 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1870 Olivetti M700-10 systems.
1873 bool "Motorola 68328 native frame buffer support"
1874 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1875 select FB_CFB_FILLRECT
1876 select FB_CFB_COPYAREA
1877 select FB_CFB_IMAGEBLIT
1879 Say Y here if you want to support the built-in frame buffer of
1880 the Motorola 68328 CPU family.
1883 tristate "PXA168/910 LCD framebuffer support"
1884 depends on FB && (CPU_PXA168 || CPU_PXA910)
1885 select FB_CFB_FILLRECT
1886 select FB_CFB_COPYAREA
1887 select FB_CFB_IMAGEBLIT
1889 Frame buffer driver for the built-in LCD controller in the Marvell
1893 tristate "PXA LCD framebuffer support"
1894 depends on FB && ARCH_PXA
1895 select FB_CFB_FILLRECT
1896 select FB_CFB_COPYAREA
1897 select FB_CFB_IMAGEBLIT
1898 select VIDEOMODE_HELPERS if OF
1899 select FB_MODE_HELPERS if OF
1901 Frame buffer driver for the built-in LCD controller in the Intel
1904 This driver is also available as a module ( = code which can be
1905 inserted and removed from the running kernel whenever you want). The
1906 module will be called pxafb. If you want to compile it as a module,
1907 say M here and read <file:Documentation/kbuild/modules.txt>.
1911 config FB_PXA_OVERLAY
1912 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1914 depends on FB_PXA && (PXA27x || PXA3xx)
1916 config FB_PXA_SMARTPANEL
1917 bool "PXA Smartpanel LCD support"
1921 config FB_PXA_PARAMETERS
1922 bool "PXA LCD command line parameters"
1926 Enable the use of kernel command line or module parameters
1927 to configure the physical properties of the LCD panel when
1928 using the PXA LCD driver.
1930 This option allows you to override the panel parameters
1931 supplied by the platform in order to support multiple
1932 different models of flatpanel. If you will only be using a
1933 single model of flatpanel then you can safely leave this
1936 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1939 tristate "PXA3xx 2D graphics accelerator driver"
1942 Kernelspace driver for the 2D graphics controller unit (GCU)
1943 found on PXA3xx processors. There is a counterpart driver in the
1944 DirectFB suite, see http://www.directfb.org/
1946 If you compile this as a module, it will be called pxa3xx_gcu.
1949 tristate "2700G LCD framebuffer support"
1950 depends on FB && ARCH_PXA
1951 select FB_CFB_FILLRECT
1952 select FB_CFB_COPYAREA
1953 select FB_CFB_IMAGEBLIT
1955 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1959 bool "Enable debugging info via debugfs"
1960 depends on FB_MBX && DEBUG_FS
1963 Enable this if you want debugging information using the debug
1964 filesystem (debugfs)
1969 tristate "Freescale DIU framebuffer support"
1970 depends on FB && FSL_SOC
1971 select FB_MODE_HELPERS
1972 select FB_CFB_FILLRECT
1973 select FB_CFB_COPYAREA
1974 select FB_CFB_IMAGEBLIT
1975 select PPC_LIB_RHEAP
1977 Framebuffer driver for the Freescale SoC DIU
1980 tristate "W100 frame buffer support"
1981 depends on FB && ARCH_PXA
1982 select FB_CFB_FILLRECT
1983 select FB_CFB_COPYAREA
1984 select FB_CFB_IMAGEBLIT
1986 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1987 It can also drive the w3220 chip found on iPAQ hx4700.
1989 This driver is also available as a module ( = code which can be
1990 inserted and removed from the running kernel whenever you want). The
1991 module will be called w100fb. If you want to compile it as a module,
1992 say M here and read <file:Documentation/kbuild/modules.txt>.
1996 config FB_SH_MOBILE_LCDC
1997 tristate "SuperH Mobile LCDC framebuffer support"
1998 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1999 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
2000 select FB_SYS_FILLRECT
2001 select FB_SYS_COPYAREA
2002 select FB_SYS_IMAGEBLIT
2004 select FB_DEFERRED_IO
2007 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2010 tristate "Toshiba Mobile IO FrameBuffer support"
2011 depends on FB && (MFD_TMIO || COMPILE_TEST)
2012 select FB_CFB_FILLRECT
2013 select FB_CFB_COPYAREA
2014 select FB_CFB_IMAGEBLIT
2016 Frame buffer driver for the Toshiba Mobile IO integrated as found
2017 on the Sharp SL-6000 series
2019 This driver is also available as a module ( = code which can be
2020 inserted and removed from the running kernel whenever you want). The
2021 module will be called tmiofb. If you want to compile it as a module,
2022 say M here and read <file:Documentation/kbuild/modules.txt>.
2026 config FB_TMIO_ACCELL
2027 bool "tmiofb acceleration"
2032 tristate "Samsung S3C framebuffer support"
2033 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2034 ARCH_S5PV210 || ARCH_EXYNOS)
2035 select FB_CFB_FILLRECT
2036 select FB_CFB_COPYAREA
2037 select FB_CFB_IMAGEBLIT
2039 Frame buffer driver for the built-in FB controller in the Samsung
2040 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2041 and the S3C64XX series such as the S3C6400 and S3C6410.
2043 These chips all have the same basic framebuffer design with the
2044 actual capabilities depending on the chip. For instance the S3C6400
2045 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2046 currently only have two.
2048 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2050 config FB_S3C_DEBUG_REGWRITE
2051 bool "Debug register writes"
2054 Show all register writes via pr_debug()
2057 tristate "S3C2410 LCD framebuffer support"
2058 depends on FB && ARCH_S3C24XX
2059 select FB_CFB_FILLRECT
2060 select FB_CFB_COPYAREA
2061 select FB_CFB_IMAGEBLIT
2063 Frame buffer driver for the built-in LCD controller in the Samsung
2066 This driver is also available as a module ( = code which can be
2067 inserted and removed from the running kernel whenever you want). The
2068 module will be called s3c2410fb. If you want to compile it as a module,
2069 say M here and read <file:Documentation/kbuild/modules.txt>.
2072 config FB_S3C2410_DEBUG
2073 bool "S3C2410 lcd debug messages"
2074 depends on FB_S3C2410
2076 Turn on debugging messages. Note that you can set/unset at run time
2080 tristate "NUC900 LCD framebuffer support"
2081 depends on FB && ARCH_W90X900
2082 select FB_CFB_FILLRECT
2083 select FB_CFB_COPYAREA
2084 select FB_CFB_IMAGEBLIT
2086 Frame buffer driver for the built-in LCD controller in the Nuvoton
2089 config GPM1040A0_320X240
2090 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2091 depends on FB_NUC900
2094 tristate "Silicon Motion SM501 framebuffer support"
2095 depends on FB && MFD_SM501
2096 select FB_CFB_FILLRECT
2097 select FB_CFB_COPYAREA
2098 select FB_CFB_IMAGEBLIT
2100 Frame buffer driver for the CRT and LCD controllers in the Silicon
2103 This driver is also available as a module ( = code which can be
2104 inserted and removed from the running kernel whenever you want). The
2105 module will be called sm501fb. If you want to compile it as a module,
2106 say M here and read <file:Documentation/kbuild/modules.txt>.
2111 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2112 depends on FB && USB
2113 select FB_MODE_HELPERS
2114 select FB_SYS_FILLRECT
2115 select FB_SYS_COPYAREA
2116 select FB_SYS_IMAGEBLIT
2118 select FB_DEFERRED_IO
2120 This is a kernel framebuffer driver for SMSC UFX USB devices.
2121 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2122 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2124 To compile as a module, choose M here: the module name is smscufx.
2127 tristate "Displaylink USB Framebuffer support"
2128 depends on FB && USB
2129 select FB_MODE_HELPERS
2130 select FB_SYS_FILLRECT
2131 select FB_SYS_COPYAREA
2132 select FB_SYS_IMAGEBLIT
2134 select FB_DEFERRED_IO
2136 This is a kernel framebuffer driver for DisplayLink USB devices.
2137 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2138 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2139 To compile as a module, choose M here: the module name is udlfb.
2141 config FB_IBM_GXT4500
2142 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2144 select FB_CFB_FILLRECT
2145 select FB_CFB_COPYAREA
2146 select FB_CFB_IMAGEBLIT
2148 Say Y here to enable support for the IBM GXT4000P/6000P and
2149 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2150 found on some IBM System P (pSeries) machines. This driver
2151 doesn't use Geometry Engine GT1000. This driver also supports
2152 AGP Fire GL2/3/4 cards on x86.
2155 tristate "PS3 GPU framebuffer driver"
2156 depends on FB && PS3_PS3AV
2157 select FB_SYS_FILLRECT
2158 select FB_SYS_COPYAREA
2159 select FB_SYS_IMAGEBLIT
2162 Include support for the virtual frame buffer in the PS3 platform.
2164 config FB_PS3_DEFAULT_SIZE_M
2165 int "PS3 default frame buffer size (in MiB)"
2169 This is the default size (in MiB) of the virtual frame buffer in
2171 The default value can be overridden on the kernel command line
2172 using the "ps3fb" option (e.g. "ps3fb=9M");
2175 tristate "Xilinx frame buffer support"
2176 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2177 select FB_CFB_FILLRECT
2178 select FB_CFB_COPYAREA
2179 select FB_CFB_IMAGEBLIT
2181 Include support for the Xilinx ML300/ML403 reference design
2182 framebuffer. ML300 carries a 640*480 LCD display on the board,
2183 ML403 uses a standard DB15 VGA connector.
2186 tristate "Goldfish Framebuffer"
2187 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2188 select FB_CFB_FILLRECT
2189 select FB_CFB_COPYAREA
2190 select FB_CFB_IMAGEBLIT
2192 Framebuffer driver for Goldfish Virtual Platform
2195 tristate "Cobalt server LCD frame buffer support"
2196 depends on FB && MIPS_COBALT
2199 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2200 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2201 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2202 select FB_CFB_FILLRECT
2203 select FB_CFB_COPYAREA
2204 select FB_CFB_IMAGEBLIT
2206 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2207 (D)STN/TFT LCD Controller.
2208 Supports display resolutions up to 1024x1024 pixel, grayscale and
2209 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2210 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2211 panels <= 320 pixel horizontal resolution.
2214 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2215 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2216 select FB_CFB_FILLRECT
2217 select FB_CFB_COPYAREA
2218 select FB_CFB_IMAGEBLIT
2219 select FB_CFB_REV_PIXELS_IN_BYTE
2220 select FB_MODE_HELPERS
2221 select VIDEOMODE_HELPERS
2223 This is the frame buffer device driver for the TI LCD controller
2224 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2228 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2230 select FB_SYS_FILLRECT
2231 select FB_SYS_COPYAREA
2232 select FB_SYS_IMAGEBLIT
2235 This is a `virtual' frame buffer device. It operates on a chunk of
2236 unswappable kernel memory instead of on the memory of a graphics
2237 board. This means you cannot see any output sent to this frame
2238 buffer device, while it does consume precious memory. The main use
2239 of this frame buffer device is testing and debugging the frame
2240 buffer subsystem. Do NOT enable it for normal systems! To protect
2241 the innocent, it has to be enabled explicitly at boot time using the
2242 kernel option `video=vfb:'.
2244 To compile this driver as a module, choose M here: the
2245 module will be called vfb. In order to load it, you must use
2246 the vfb_enable=1 option.
2250 config XEN_FBDEV_FRONTEND
2251 tristate "Xen virtual frame buffer support"
2252 depends on FB && XEN
2253 select FB_SYS_FILLRECT
2254 select FB_SYS_COPYAREA
2255 select FB_SYS_IMAGEBLIT
2257 select FB_DEFERRED_IO
2258 select XEN_XENBUS_FRONTEND
2261 This driver implements the front-end of the Xen virtual
2262 frame buffer driver. It communicates with a back-end
2266 tristate "E-Ink Metronome/8track controller support"
2268 select FB_SYS_FILLRECT
2269 select FB_SYS_COPYAREA
2270 select FB_SYS_IMAGEBLIT
2272 select FB_DEFERRED_IO
2274 This driver implements support for the E-Ink Metronome
2275 controller. The pre-release name for this device was 8track
2276 and could also have been called by some vendors as PVI-nnnn.
2279 tristate "Fujitsu MB862xx GDC support"
2281 depends on PCI || (OF && PPC)
2282 select FB_CFB_FILLRECT
2283 select FB_CFB_COPYAREA
2284 select FB_CFB_IMAGEBLIT
2286 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2289 prompt "GDC variant"
2290 depends on FB_MB862XX
2292 config FB_MB862XX_PCI_GDC
2293 bool "Carmine/Coral-P(A) GDC"
2296 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2297 PCI graphics controller devices.
2299 config FB_MB862XX_LIME
2301 depends on OF && PPC
2302 select FB_FOREIGN_ENDIAN
2303 select FB_LITTLE_ENDIAN
2305 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2309 config FB_MB862XX_I2C
2310 bool "Support I2C bus on MB862XX GDC"
2311 depends on FB_MB862XX && I2C
2312 depends on FB_MB862XX=m || I2C=y
2315 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2316 driver to support accessing I2C devices on controller's I2C bus.
2317 These are usually some video decoder chips.
2320 tristate "EP93XX frame buffer support"
2321 depends on FB && ARCH_EP93XX
2322 select FB_CFB_FILLRECT
2323 select FB_CFB_COPYAREA
2324 select FB_CFB_IMAGEBLIT
2326 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2327 This driver is also available as a module. The module will be called
2330 config FB_PRE_INIT_FB
2331 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2332 depends on FB && FB_MB862XX_LIME
2334 Select this option if display contents should be inherited as set by
2338 tristate "MX3 Framebuffer support"
2339 depends on FB && MX3_IPU
2340 select BACKLIGHT_CLASS_DEVICE
2341 select BACKLIGHT_LCD_SUPPORT
2342 select FB_CFB_FILLRECT
2343 select FB_CFB_COPYAREA
2344 select FB_CFB_IMAGEBLIT
2347 This is a framebuffer device for the i.MX31 LCD Controller. So
2348 far only synchronous displays are supported. If you plan to use
2349 an LCD display with your i.MX31 system, say Y here.
2351 config FB_BROADSHEET
2352 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2354 select FB_SYS_FILLRECT
2355 select FB_SYS_COPYAREA
2356 select FB_SYS_IMAGEBLIT
2358 select FB_DEFERRED_IO
2360 This driver implements support for the E-Ink Broadsheet
2361 controller. The release name for this device was Epson S1D13521
2362 and could also have been called by other names when coupled with
2366 tristate "AUO-K190X EPD controller support"
2368 select FB_SYS_FILLRECT
2369 select FB_SYS_COPYAREA
2370 select FB_SYS_IMAGEBLIT
2372 select FB_DEFERRED_IO
2374 Provides support for epaper controllers from the K190X series
2375 of AUO. These controllers can be used to drive epaper displays
2378 This option enables the common support, shared by the individual
2379 controller drivers. You will also have to enable the driver
2380 for the controller type used in your device.
2383 tristate "AUO-K1900 EPD controller support"
2384 depends on FB && FB_AUO_K190X
2386 This driver implements support for the AUO K1900 epd-controller.
2387 This controller can drive Sipix epaper displays but can only do
2388 serial updates, reducing the number of possible frames per second.
2391 tristate "AUO-K1901 EPD controller support"
2392 depends on FB && FB_AUO_K190X
2394 This driver implements support for the AUO K1901 epd-controller.
2395 This controller can drive Sipix epaper displays and supports
2396 concurrent updates, making higher frames per second possible.
2399 tristate "JZ4740 LCD framebuffer support"
2400 depends on FB && MACH_JZ4740
2401 select FB_SYS_FILLRECT
2402 select FB_SYS_COPYAREA
2403 select FB_SYS_IMAGEBLIT
2405 Framebuffer support for the JZ4740 SoC.
2408 tristate "MXS LCD framebuffer support"
2409 depends on FB && (ARCH_MXS || ARCH_MXC)
2410 select FB_CFB_FILLRECT
2411 select FB_CFB_COPYAREA
2412 select FB_CFB_IMAGEBLIT
2413 select FB_MODE_HELPERS
2414 select VIDEOMODE_HELPERS
2416 Framebuffer support for the MXS SoC.
2418 config FB_PUV3_UNIGFX
2419 tristate "PKUnity v3 Unigfx framebuffer support"
2420 depends on FB && UNICORE32 && ARCH_PUV3
2421 select FB_SYS_FILLRECT
2422 select FB_SYS_COPYAREA
2423 select FB_SYS_IMAGEBLIT
2426 Choose this option if you want to use the Unigfx device as a
2427 framebuffer device. Without the support of PCI & AGP.
2430 tristate "Microsoft Hyper-V Synthetic Video support"
2431 depends on FB && HYPERV
2432 select FB_CFB_FILLRECT
2433 select FB_CFB_COPYAREA
2434 select FB_CFB_IMAGEBLIT
2436 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2439 bool "Simple framebuffer support"
2441 select FB_CFB_FILLRECT
2442 select FB_CFB_COPYAREA
2443 select FB_CFB_IMAGEBLIT
2445 Say Y if you want support for a simple frame-buffer.
2447 This driver assumes that the display hardware has been initialized
2448 before the kernel boots, and the kernel will simply render to the
2449 pre-allocated frame buffer surface.
2451 Configuration re: surface address, size, and format must be provided
2452 through device tree, or plain old platform data.
2454 source "drivers/video/fbdev/omap/Kconfig"
2455 source "drivers/video/fbdev/omap2/Kconfig"
2456 source "drivers/video/fbdev/mmp/Kconfig"
2458 config FB_SH_MOBILE_MERAM
2459 tristate "SuperH Mobile MERAM read ahead support"
2460 depends on (SUPERH || ARCH_SHMOBILE)
2461 select GENERIC_ALLOCATOR
2463 Enable MERAM support for the SuperH controller.
2465 This will allow for caching of the framebuffer to provide more
2466 reliable access under heavy main memory bus traffic situations.
2467 Up to 4 memory channels can be configured, allowing 4 RGB or
2468 2 YCbCr framebuffers to be configured.
2471 tristate "Solomon SSD1307 framebuffer support"
2472 depends on FB && I2C
2474 depends on GPIOLIB || COMPILE_TEST
2476 select FB_SYS_FILLRECT
2477 select FB_SYS_COPYAREA
2478 select FB_SYS_IMAGEBLIT
2479 select FB_DEFERRED_IO
2483 This driver implements support for the Solomon SSD1307
2484 OLED controller over I2C.
2487 tristate "Silicon Motion SM712 framebuffer support"
2488 depends on FB && PCI
2489 select FB_CFB_FILLRECT
2490 select FB_CFB_COPYAREA
2491 select FB_CFB_IMAGEBLIT
2493 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2496 This driver is also available as a module. The module will be
2497 called sm712fb. If you want to compile it as a module, say M
2498 here and read <file:Documentation/kbuild/modules.txt>.