11 config FB_CLPS711X_OLD
13 select FB_CFB_FILLRECT
14 select FB_CFB_COPYAREA
15 select FB_CFB_IMAGEBLIT
18 tristate "Support for frame buffer devices"
22 The frame buffer device provides an abstraction for the graphics
23 hardware. It represents the frame buffer of some video hardware and
24 allows application software to access the graphics hardware through
25 a well-defined interface, so the software doesn't need to know
26 anything about the low-level (hardware register) stuff.
28 Frame buffer devices work identically across the different
29 architectures supported by Linux and make the implementation of
30 application programs easier and more portable; at this point, an X
31 server exists which uses the frame buffer device exclusively.
32 On several non-X86 architectures, the frame buffer device is the
33 only way to use the graphics hardware.
35 The device is accessed through special device nodes, usually located
36 in the /dev directory, i.e. /dev/fb*.
38 You need an utility program called fbset to make full use of frame
39 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
40 and the Framebuffer-HOWTO at
41 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
44 Say Y here and to the driver for your graphics board below if you
45 are compiling a kernel for a non-x86 architecture.
47 If you are compiling for the x86 architecture, you can say Y if you
48 want to play with it, but it is not essential. Please note that
49 running graphical applications that directly touch the hardware
50 (e.g. an accelerated X server) and that are not frame buffer
51 device-aware may cause unexpected results. If unsure, say N.
54 bool "Enable firmware EDID"
58 This enables access to the EDID transferred from the firmware.
59 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
60 transfers do not work for your driver and if you are using
61 nvidiafb, i810fb or savagefb.
63 In general, choosing Y for this option is safe. If you
64 experience extremely long delays while booting before you get
65 something on your display, try setting this to N. Matrox cards in
66 combination with certain motherboards and monitors are known to
67 suffer from this problem.
76 config FB_BOOT_VESA_SUPPORT
81 If true, at least one selected framebuffer driver can take advantage
82 of VESA video modes set at an early boot stage via the vga= parameter.
84 config FB_CFB_FILLRECT
89 Include the cfb_fillrect function for generic software rectangle
90 filling. This is used by drivers that don't provide their own
91 (accelerated) version.
93 config FB_CFB_COPYAREA
98 Include the cfb_copyarea function for generic software area copying.
99 This is used by drivers that don't provide their own (accelerated)
102 config FB_CFB_IMAGEBLIT
107 Include the cfb_imageblit function for generic software image
108 blitting. This is used by drivers that don't provide their own
109 (accelerated) version.
111 config FB_CFB_REV_PIXELS_IN_BYTE
116 Allow generic frame-buffer functions to work on displays with 1, 2
117 and 4 bits per pixel depths which has opposite order of pixels in
118 byte order to bytes in long order.
120 config FB_SYS_FILLRECT
125 Include the sys_fillrect function for generic software rectangle
126 filling. This is used by drivers that don't provide their own
127 (accelerated) version and the framebuffer is in system RAM.
129 config FB_SYS_COPYAREA
134 Include the sys_copyarea function for generic software area copying.
135 This is used by drivers that don't provide their own (accelerated)
136 version and the framebuffer is in system RAM.
138 config FB_SYS_IMAGEBLIT
143 Include the sys_imageblit function for generic software image
144 blitting. This is used by drivers that don't provide their own
145 (accelerated) version and the framebuffer is in system RAM.
147 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
152 Allow generic frame-buffer to provide get_fb_unmapped_area
155 menuconfig FB_FOREIGN_ENDIAN
156 bool "Framebuffer foreign endianness support"
159 This menu will let you enable support for the framebuffers with
160 non-native endianness (e.g. Little-Endian framebuffer on a
161 Big-Endian machine). Most probably you don't have such hardware,
162 so it's safe to say "n" here.
165 prompt "Choice endianness support"
166 depends on FB_FOREIGN_ENDIAN
168 config FB_BOTH_ENDIAN
169 bool "Support for Big- and Little-Endian framebuffers"
172 bool "Support for Big-Endian framebuffers only"
174 config FB_LITTLE_ENDIAN
175 bool "Support for Little-Endian framebuffers only"
184 config FB_DEFERRED_IO
191 depends on FB_DEFERRED_IO
198 Common utility functions useful to fbdev drivers of VGA-based
209 select BACKLIGHT_LCD_SUPPORT
210 select BACKLIGHT_CLASS_DEVICE
213 config FB_MODE_HELPERS
214 bool "Enable Video Mode Handling Helpers"
218 This enables functions for handling video modes using the
219 Generalized Timing Formula and the EDID parser. A few drivers rely
220 on this feature such as the radeonfb, rivafb, and the i810fb. If
221 your driver does not take advantage of this feature, choosing Y will
222 just increase the kernel size by about 5K.
224 config FB_TILEBLITTING
225 bool "Enable Tile Blitting Support"
229 This enables tile blitting. Tile blitting is a drawing technique
230 where the screen is divided into rectangular sections (tiles), whereas
231 the standard blitting divides the screen into pixels. Because the
232 default drawing element is a tile, drawing functions will be passed
233 parameters in terms of number of tiles instead of number of pixels.
234 For example, to draw a single character, instead of using bitmaps,
235 an index to an array of bitmaps will be used. To clear or move a
236 rectangular section of a screen, the rectangle will be described in
237 terms of number of tiles in the x- and y-axis.
239 This is particularly important to one driver, matroxfb. If
242 comment "Frame buffer hardware drivers"
246 tristate "Aeroflex Gaisler framebuffer support"
247 depends on FB && SPARC
248 select FB_CFB_FILLRECT
249 select FB_CFB_COPYAREA
250 select FB_CFB_IMAGEBLIT
252 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
255 tristate "Cirrus Logic support"
256 depends on FB && (ZORRO || PCI)
257 select FB_CFB_FILLRECT
258 select FB_CFB_COPYAREA
259 select FB_CFB_IMAGEBLIT
261 This enables support for Cirrus Logic GD542x/543x based boards on
262 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
264 If you have a PCI-based system, this enables support for these
265 chips: GD-543x, GD-544x, GD-5480.
267 Please read the file <file:Documentation/fb/cirrusfb.txt>.
269 Say N unless you have such a graphics board or plan to get one
270 before you next recompile the kernel.
273 tristate "Permedia2 support"
274 depends on FB && ((AMIGA && BROKEN) || PCI)
275 select FB_CFB_FILLRECT
276 select FB_CFB_COPYAREA
277 select FB_CFB_IMAGEBLIT
279 This is the frame buffer device driver for cards based on
280 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
281 The driver was tested on the following cards:
282 Diamond FireGL 1000 PRO AGP
283 ELSA Gloria Synergy PCI
284 Appian Jeronimo PRO (both heads) PCI
285 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
286 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
287 ASK Graphic Blaster Exxtreme AGP
289 To compile this driver as a module, choose M here: the
290 module will be called pm2fb.
292 config FB_PM2_FIFO_DISCONNECT
293 bool "enable FIFO disconnect feature"
294 depends on FB_PM2 && PCI
296 Support the Permedia2 FIFO disconnect feature.
299 tristate "ARM PrimeCell PL110 support"
300 depends on ARM || ARM64 || COMPILE_TEST
301 depends on FB && ARM_AMBA && HAS_IOMEM
302 select FB_CFB_FILLRECT
303 select FB_CFB_COPYAREA
304 select FB_CFB_IMAGEBLIT
305 select FB_MODE_HELPERS if OF
306 select VIDEOMODE_HELPERS if OF
307 select BACKLIGHT_LCD_SUPPORT if OF
308 select BACKLIGHT_CLASS_DEVICE if OF
310 This framebuffer device driver is for the ARM PrimeCell PL110
311 Colour LCD controller. ARM PrimeCells provide the building
312 blocks for System on a Chip devices.
314 If you want to compile this as a module (=code which can be
315 inserted into and removed from the running kernel), say M
316 here and read <file:Documentation/kbuild/modules.txt>. The module
317 will be called amba-clcd.
319 # Helper logic selected only by the ARM Versatile platform family.
320 config PLAT_VERSATILE_CLCD
321 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
323 depends on FB_ARMCLCD && FB=y
328 bool "Acorn VIDC support"
329 depends on (FB = y) && ARM && ARCH_ACORN
330 select FB_CFB_FILLRECT
331 select FB_CFB_COPYAREA
332 select FB_CFB_IMAGEBLIT
334 This is the frame buffer device driver for the Acorn VIDC graphics
335 hardware found in Acorn RISC PCs and other ARM-based machines. If
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.
584 tristate "HP STI frame buffer device support"
585 depends on FB && PARISC
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
591 STI refers to the HP "Standard Text Interface" which is a set of
592 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
593 Enabling this option will implement the linux framebuffer device
594 using calls to the STI BIOS routines for initialisation.
596 If you enable this option, you will get a planar framebuffer device
597 /dev/fb which will work on the most common HP graphic cards of the
598 NGLE family, including the artist chips (in the 7xx and Bxxx series),
599 HCRX, HCRX24, CRX, CRX24 and VisEG series.
601 It is safe to enable this option, so you should probably say "Y".
604 bool "Generic Macintosh display support"
605 depends on (FB = y) && MAC
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
613 depends on (FB = y) && DIO
614 select FB_CFB_IMAGEBLIT
618 tristate "TGA/SFB+ framebuffer support"
619 depends on FB && (ALPHA || TC)
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
625 This is the frame buffer device driver for generic TGA and SFB+
626 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
627 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
628 TURBOchannel cards, also known as PMAGD-A, -B and -C.
630 Due to hardware limitations ZLX-E2 and E3 cards are not supported
631 for DECstation 5000/200 systems. Additionally due to firmware
632 limitations these cards may cause troubles with booting DECstation
633 5000/240 and /260 systems, but are fully supported under Linux if
634 you manage to get it going. ;-)
636 Say Y if you have one of those.
639 tristate "Userspace VESA VGA graphics support"
640 depends on FB && CONNECTOR
641 select FB_CFB_FILLRECT
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
644 select FB_MODE_HELPERS
646 This is the frame buffer driver for generic VBE 2.0 compliant
647 graphic cards. It can also take advantage of VBE 3.0 features,
648 such as refresh rate adjustment.
650 This driver generally provides more features than vesafb but
651 requires a userspace helper application called 'v86d'. See
652 <file:Documentation/fb/uvesafb.txt> for more information.
657 bool "VESA VGA graphics support"
658 depends on (FB = y) && X86
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
662 select FB_BOOT_VESA_SUPPORT
664 This is the frame buffer device driver for generic VESA 2.0
665 compliant graphic cards. The older VESA 1.2 cards are not supported.
666 You will get a boot time penguin logo at no additional cost. Please
667 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
670 bool "EFI-based Framebuffer Support"
671 depends on (FB = y) && !IA64 && EFI
672 select DRM_PANEL_ORIENTATION_QUIRKS
673 select FB_CFB_FILLRECT
674 select FB_CFB_COPYAREA
675 select FB_CFB_IMAGEBLIT
677 This is the EFI frame buffer device driver. If the firmware on
678 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
679 using the EFI framebuffer as your console.
682 tristate "N411 Apollo/Hecuba devkit support"
683 depends on FB && X86 && MMU
684 select FB_SYS_FILLRECT
685 select FB_SYS_COPYAREA
686 select FB_SYS_IMAGEBLIT
688 select FB_DEFERRED_IO
691 This enables support for the Apollo display controller in its
692 Hecuba form using the n411 devkit.
695 tristate "Hercules mono graphics support"
698 Say Y here if you have a Hercules mono graphics card.
700 To compile this driver as a module, choose M here: the
701 module will be called hgafb.
703 As this card technology is at least 25 years old,
704 most people will answer N here.
707 bool "SGI Graphics Backend frame buffer support"
708 depends on (FB = y) && SGI_IP32
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
713 This is the frame buffer device driver for SGI Graphics Backend.
714 This chip is used in SGI O2 and Visual Workstation 320/540.
717 int "Video memory size in MB"
721 This is the amount of memory reserved for the framebuffer,
722 which can be any value between 1MB and 8MB.
725 bool "SBUS and UPA framebuffers"
726 depends on (FB = y) && SPARC
728 Say Y if you want support for SBUS or UPA based frame buffer device.
732 depends on (FB = y) && (SPARC && FB_SBUS)
733 select FB_CFB_FILLRECT
734 select FB_CFB_COPYAREA
735 select FB_CFB_IMAGEBLIT
737 This is the frame buffer device driver for the BWtwo frame buffer.
740 bool "CGthree support"
741 depends on (FB = y) && (SPARC && FB_SBUS)
742 select FB_CFB_FILLRECT
743 select FB_CFB_COPYAREA
744 select FB_CFB_IMAGEBLIT
746 This is the frame buffer device driver for the CGthree frame buffer.
749 bool "CGsix (GX,TurboGX) support"
750 depends on (FB = y) && (SPARC && FB_SBUS)
751 select FB_CFB_COPYAREA
752 select FB_CFB_IMAGEBLIT
754 This is the frame buffer device driver for the CGsix (GX, TurboGX)
758 bool "Creator/Creator3D/Elite3D support"
759 depends on FB_SBUS && SPARC64
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
763 This is the frame buffer device driver for the Creator, Creator3D,
764 and Elite3D graphics boards.
767 bool "TCX (SS4/SS5 only) support"
769 select FB_CFB_FILLRECT
770 select FB_CFB_COPYAREA
771 select FB_CFB_IMAGEBLIT
773 This is the frame buffer device driver for the TCX 24/8bit frame
777 bool "CGfourteen (SX) support"
779 select FB_CFB_FILLRECT
780 select FB_CFB_COPYAREA
781 select FB_CFB_IMAGEBLIT
783 This is the frame buffer device driver for the CGfourteen frame
784 buffer on Desktop SPARCsystems with the SX graphics option.
787 bool "P9100 (Sparcbook 3 only) support"
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
793 This is the frame buffer device driver for the P9100 card
794 supported on Sparcbook 3 machines.
797 bool "Leo (ZX) support"
799 select FB_CFB_FILLRECT
800 select FB_CFB_COPYAREA
801 select FB_CFB_IMAGEBLIT
803 This is the frame buffer device driver for the SBUS-based Sun ZX
804 (leo) frame buffer cards.
807 bool "Sun XVR-500 3DLABS Wildcat support"
808 depends on (FB = y) && PCI && SPARC64
809 select FB_CFB_FILLRECT
810 select FB_CFB_COPYAREA
811 select FB_CFB_IMAGEBLIT
813 This is the framebuffer device for the Sun XVR-500 and similar
814 graphics cards based upon the 3DLABS Wildcat chipset. The driver
815 only works on sparc64 systems where the system firmware has
816 mostly initialized the card already. It is treated as a
817 completely dumb framebuffer device.
820 bool "Sun XVR-2500 3DLABS Wildcat support"
821 depends on (FB = y) && PCI && SPARC64
822 select FB_CFB_FILLRECT
823 select FB_CFB_COPYAREA
824 select FB_CFB_IMAGEBLIT
826 This is the framebuffer device for the Sun XVR-2500 and similar
827 graphics cards based upon the 3DLABS Wildcat chipset. The driver
828 only works on sparc64 systems where the system firmware has
829 mostly initialized the card already. It is treated as a
830 completely dumb framebuffer device.
833 bool "Sun XVR-1000 support"
834 depends on (FB = y) && SPARC64
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
839 This is the framebuffer device for the Sun XVR-1000 and similar
840 graphics cards. The driver only works on sparc64 systems where
841 the system firmware has mostly initialized the card already. It
842 is treated as a completely dumb framebuffer device.
845 tristate "NEC PowerVR 2 display support"
846 depends on FB && SH_DREAMCAST
847 select FB_CFB_FILLRECT
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 Say Y here if you have a PowerVR 2 card in your box. If you plan to
852 run linux on your Dreamcast, you will have to say Y here.
853 This driver may or may not work on other PowerVR 2 cards, but is
854 totally untested. Use at your own risk. If unsure, say N.
856 To compile this driver as a module, choose M here: the
857 module will be called pvr2fb.
859 You can pass several parameters to the driver at boot time or at
860 module load time. The parameters look like "video=pvr2:XXX", where
861 the meaning of XXX can be found at the end of the main source file
862 (<file:drivers/video/pvr2fb.c>). Please see the file
863 <file:Documentation/fb/pvr2fb.txt>.
866 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
867 depends on FB && HAS_DMA
868 select FB_CFB_FILLRECT
869 select FB_CFB_COPYAREA
870 select FB_CFB_IMAGEBLIT
872 This enables support for the OpenCores VGA/LCD core.
874 The OpenCores VGA/LCD core is typically used together with
875 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
876 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
878 The source code and specification for the core is available at
879 <http://opencores.org/project,vga_lcd>
882 tristate "Epson S1D13XXX framebuffer support"
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 Support for S1D13XXX framebuffer device family (currently only
889 working with S1D13806). Product specs at
890 <http://vdc.epson.com/>
893 tristate "AT91/AT32 LCD Controller support"
894 depends on FB && HAVE_FB_ATMEL
896 select FB_CFB_FILLRECT
897 select FB_CFB_COPYAREA
898 select FB_CFB_IMAGEBLIT
899 select FB_MODE_HELPERS
900 select VIDEOMODE_HELPERS
902 This enables support for the AT91/AT32 LCD Controller.
905 tristate "nVidia Framebuffer Support"
907 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
908 select FB_MODE_HELPERS
909 select FB_CFB_FILLRECT
910 select FB_CFB_COPYAREA
911 select FB_CFB_IMAGEBLIT
915 This driver supports graphics boards with the nVidia chips, TNT
916 and newer. For very old chipsets, such as the RIVA128, then use
918 Say Y if you have such a graphics board.
920 To compile this driver as a module, choose M here: the
921 module will be called nvidiafb.
924 bool "Enable DDC Support"
928 This enables I2C support for nVidia Chipsets. This is used
929 only for getting EDID information from the attached display
930 allowing for robust video mode handling and switching.
932 Because fbdev-2.6 requires that drivers must be able to
933 independently validate video mode parameters, you should say Y
936 config FB_NVIDIA_DEBUG
937 bool "Lots of debug output"
941 Say Y here if you want the nVidia driver to output all sorts
942 of debugging information to provide to the maintainer when
943 something goes wrong.
945 config FB_NVIDIA_BACKLIGHT
946 bool "Support for backlight control"
950 Say Y here if you want to control the backlight of your display.
953 tristate "nVidia Riva support"
955 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
956 select FB_MODE_HELPERS
957 select FB_CFB_FILLRECT
958 select FB_CFB_COPYAREA
959 select FB_CFB_IMAGEBLIT
963 This driver supports graphics boards with the nVidia Riva/Geforce
965 Say Y if you have such a graphics board.
967 To compile this driver as a module, choose M here: the
968 module will be called rivafb.
971 bool "Enable DDC Support"
975 This enables I2C support for nVidia Chipsets. This is used
976 only for getting EDID information from the attached display
977 allowing for robust video mode handling and switching.
979 Because fbdev-2.6 requires that drivers must be able to
980 independently validate video mode parameters, you should say Y
984 bool "Lots of debug output"
988 Say Y here if you want the Riva driver to output all sorts
989 of debugging information to provide to the maintainer when
990 something goes wrong.
992 config FB_RIVA_BACKLIGHT
993 bool "Support for backlight control"
997 Say Y here if you want to control the backlight of your display.
1000 tristate "Intel740 support"
1001 depends on FB && PCI
1002 select FB_MODE_HELPERS
1003 select FB_CFB_FILLRECT
1004 select FB_CFB_COPYAREA
1005 select FB_CFB_IMAGEBLIT
1009 This driver supports graphics cards based on Intel740 chip.
1012 tristate "Intel 810/815 support"
1013 depends on FB && PCI && X86_32 && AGP_INTEL
1014 select FB_MODE_HELPERS
1015 select FB_CFB_FILLRECT
1016 select FB_CFB_COPYAREA
1017 select FB_CFB_IMAGEBLIT
1020 This driver supports the on-board graphics built in to the Intel 810
1021 and 815 chipsets. Say Y if you have and plan to use such a board.
1023 To compile this driver as a module, choose M here: the
1024 module will be called i810fb.
1026 For more information, please read
1027 <file:Documentation/fb/intel810.txt>
1030 bool "use VESA Generalized Timing Formula"
1033 If you say Y, then the VESA standard, Generalized Timing Formula
1034 or GTF, will be used to calculate the required video timing values
1035 per video mode. Since the GTF allows nondiscrete timings
1036 (nondiscrete being a range of values as opposed to discrete being a
1037 set of values), you'll be able to use any combination of horizontal
1038 and vertical resolutions, and vertical refresh rates without having
1039 to specify your own timing parameters. This is especially useful
1040 to maximize the performance of an aging display, or if you just
1041 have a display with nonstandard dimensions. A VESA compliant
1042 monitor is recommended, but can still work with non-compliant ones.
1043 If you need or want this, then select this option. The timings may
1044 not be compliant with Intel's recommended values. Use at your own
1047 If you say N, the driver will revert to discrete video timings
1048 using a set recommended by Intel in their documentation.
1053 bool "Enable DDC Support"
1054 depends on FB_I810 && FB_I810_GTF
1057 Add DDC/I2C support for i810fb. This will allow the driver to get
1058 display information, especially for monitors with fickle timings.
1063 tristate "Intel LE80578 (Vermilion) support"
1064 depends on FB && PCI && X86
1065 select FB_MODE_HELPERS
1066 select FB_CFB_FILLRECT
1067 select FB_CFB_COPYAREA
1068 select FB_CFB_IMAGEBLIT
1070 This driver supports the LE80578 (Vermilion Range) chipset
1072 config FB_CARILLO_RANCH
1073 tristate "Intel Carillo Ranch support"
1074 depends on FB_LE80578 && FB && PCI && X86
1076 This driver supports the LE80578 (Carillo Ranch) board
1079 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1080 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1081 select FB_MODE_HELPERS
1082 select FB_CFB_FILLRECT
1083 select FB_CFB_COPYAREA
1084 select FB_CFB_IMAGEBLIT
1085 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1086 depends on !DRM_I915
1088 This driver supports the on-board graphics built in to the Intel
1089 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1090 Say Y if you have and plan to use such a board.
1092 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
1094 To compile this driver as a module, choose M here: the
1095 module will be called intelfb.
1097 For more information, please read <file:Documentation/fb/intelfb.txt>
1099 config FB_INTEL_DEBUG
1100 bool "Intel driver Debug Messages"
1103 Say Y here if you want the Intel driver to output all sorts
1104 of debugging information to provide to the maintainer when
1105 something goes wrong.
1108 bool "DDC/I2C for Intel framebuffer support"
1113 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1116 tristate "Matrox acceleration"
1117 depends on FB && PCI
1118 select FB_CFB_FILLRECT
1119 select FB_CFB_COPYAREA
1120 select FB_CFB_IMAGEBLIT
1121 select FB_TILEBLITTING
1122 select FB_MACMODES if PPC_PMAC
1124 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1125 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1126 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1127 Matrox G400, G450 or G550 card in your box.
1129 To compile this driver as a module, choose M here: the
1130 module will be called matroxfb.
1132 You can pass several parameters to the driver at boot time or at
1133 module load time. The parameters look like "video=matroxfb:XXX", and
1134 are described in <file:Documentation/fb/matroxfb.txt>.
1136 config FB_MATROX_MILLENIUM
1137 bool "Millennium I/II support"
1138 depends on FB_MATROX
1140 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1141 video card. If you select "Advanced lowlevel driver options" below,
1142 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1143 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1144 also use font widths different from 8.
1146 config FB_MATROX_MYSTIQUE
1147 bool "Mystique support"
1148 depends on FB_MATROX
1150 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1151 video card. If you select "Advanced lowlevel driver options" below,
1152 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1153 packed pixel and 32 bpp packed pixel. You can also use font widths
1157 bool "G100/G200/G400/G450/G550 support"
1158 depends on FB_MATROX
1160 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1161 video card. If you select "Advanced lowlevel driver options", you
1162 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1163 pixel and 32 bpp packed pixel. You can also use font widths
1166 If you need support for G400 secondary head, you must say Y to
1167 "Matrox I2C support" and "G400 second head support" right below.
1168 G450/G550 secondary head and digital output are supported without
1171 The driver starts in monitor mode. You must use the matroxset tool
1172 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1173 swap primary and secondary head outputs, or to change output mode.
1174 Secondary head driver always start in 640x480 resolution and you
1175 must use fbset to change it.
1177 Do not forget that second head supports only 16 and 32 bpp
1178 packed pixels, so it is a good idea to compile them into the kernel
1179 too. You can use only some font widths, as the driver uses generic
1180 painting procedures (the secondary head does not use acceleration
1183 G450/G550 hardware can display TV picture only from secondary CRTC,
1184 and it performs no scaling, so picture must have 525 or 625 lines.
1186 config FB_MATROX_I2C
1187 tristate "Matrox I2C support"
1188 depends on FB_MATROX
1191 This drivers creates I2C buses which are needed for accessing the
1192 DDC (I2C) bus present on all Matroxes, an I2C bus which
1193 interconnects Matrox optional devices, like MGA-TVO on G200 and
1194 G400, and the secondary head DDC bus, present on G400 only.
1196 You can say Y or M here if you want to experiment with monitor
1197 detection code. You must say Y or M here if you want to use either
1198 second head of G400 or MGA-TVO on G200 or G400.
1200 If you compile it as module, it will create a module named
1203 config FB_MATROX_MAVEN
1204 tristate "G400 second head support"
1205 depends on FB_MATROX_G && FB_MATROX_I2C
1207 WARNING !!! This support does not work with G450 !!!
1209 Say Y or M here if you want to use a secondary head (meaning two
1210 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1211 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1212 secondary head output is blanked while you are in X. With XFree
1213 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1214 the fbdev driver on first head and the fbdev driver on second head.
1216 If you compile it as module, two modules are created,
1217 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1218 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1219 also load i2c-matroxfb to get it to run.
1221 The driver starts in monitor mode and you must use the matroxset
1223 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1224 PAL or NTSC or to swap primary and secondary head outputs.
1225 Secondary head driver also always start in 640x480 resolution, you
1226 must use fbset to change it.
1228 Also do not forget that second head supports only 16 and 32 bpp
1229 packed pixels, so it is a good idea to compile them into the kernel
1230 too. You can use only some font widths, as the driver uses generic
1231 painting procedures (the secondary head does not use acceleration
1235 tristate "ATI Radeon display support"
1236 depends on FB && PCI
1237 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1238 select FB_MODE_HELPERS
1239 select FB_CFB_FILLRECT
1240 select FB_CFB_COPYAREA
1241 select FB_CFB_IMAGEBLIT
1242 select FB_MACMODES if PPC
1244 Choose this option if you want to use an ATI Radeon graphics card as
1245 a framebuffer device. There are both PCI and AGP versions. You
1246 don't need to choose this to run the Radeon in plain VGA mode.
1248 There is a product page at
1249 http://products.amd.com/en-us/GraphicCardResult.aspx
1251 config FB_RADEON_I2C
1252 bool "DDC/I2C for ATI Radeon support"
1253 depends on FB_RADEON
1257 Say Y here if you want DDC/I2C support for your Radeon board.
1259 config FB_RADEON_BACKLIGHT
1260 bool "Support for backlight control"
1261 depends on FB_RADEON
1264 Say Y here if you want to control the backlight of your display.
1266 config FB_RADEON_DEBUG
1267 bool "Lots of debug output from Radeon driver"
1268 depends on FB_RADEON
1271 Say Y here if you want the Radeon driver to output all sorts
1272 of debugging information to provide to the maintainer when
1273 something goes wrong.
1276 tristate "ATI Rage128 display support"
1277 depends on FB && PCI
1278 select FB_CFB_FILLRECT
1279 select FB_CFB_COPYAREA
1280 select FB_CFB_IMAGEBLIT
1281 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1282 select FB_MACMODES if PPC_PMAC
1284 This driver supports graphics boards with the ATI Rage128 chips.
1285 Say Y if you have such a graphics board and read
1286 <file:Documentation/fb/aty128fb.txt>.
1288 To compile this driver as a module, choose M here: the
1289 module will be called aty128fb.
1291 config FB_ATY128_BACKLIGHT
1292 bool "Support for backlight control"
1293 depends on FB_ATY128
1296 Say Y here if you want to control the backlight of your display.
1299 tristate "ATI Mach64 display support" if PCI || ATARI
1300 depends on FB && !SPARC32
1301 select FB_CFB_FILLRECT
1302 select FB_CFB_COPYAREA
1303 select FB_CFB_IMAGEBLIT
1304 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1305 select FB_MACMODES if PPC
1307 This driver supports graphics boards with the ATI Mach64 chips.
1308 Say Y if you have such a graphics board.
1310 To compile this driver as a module, choose M here: the
1311 module will be called atyfb.
1314 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1315 depends on PCI && FB_ATY
1316 default y if SPARC64 && PCI
1318 Say Y here to support use of ATI's 64-bit Rage boards (or other
1319 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1320 framebuffer device. The ATI product support page for these boards
1321 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1323 config FB_ATY_GENERIC_LCD
1324 bool "Mach64 generic LCD support"
1325 depends on FB_ATY_CT
1327 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1328 Rage XC, or Rage XL chipset.
1331 bool "Mach64 GX support" if PCI
1335 Say Y here to support use of the ATI Mach64 Graphics Expression
1336 board (or other boards based on the Mach64 GX chipset) as a
1337 framebuffer device. The ATI product support page for these boards
1339 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1341 config FB_ATY_BACKLIGHT
1342 bool "Support for backlight control"
1346 Say Y here if you want to control the backlight of your display.
1349 tristate "S3 Trio/Virge support"
1350 depends on FB && PCI
1351 select FB_CFB_FILLRECT
1352 select FB_CFB_COPYAREA
1353 select FB_CFB_IMAGEBLIT
1354 select FB_TILEBLITTING
1357 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1359 Driver for graphics boards with S3 Trio / S3 Virge chip.
1362 bool "DDC for S3 support"
1367 Say Y here if you want DDC support for your S3 graphics card.
1370 tristate "S3 Savage support"
1371 depends on FB && PCI
1372 select FB_MODE_HELPERS
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1378 This driver supports notebooks and computers with S3 Savage PCI/AGP
1381 Say Y if you have such a graphics card.
1383 To compile this driver as a module, choose M here; the module
1384 will be called savagefb.
1386 config FB_SAVAGE_I2C
1387 bool "Enable DDC2 Support"
1388 depends on FB_SAVAGE
1391 This enables I2C support for S3 Savage Chipsets. This is used
1392 only for getting EDID information from the attached display
1393 allowing for robust video mode handling and switching.
1395 Because fbdev-2.6 requires that drivers must be able to
1396 independently validate video mode parameters, you should say Y
1399 config FB_SAVAGE_ACCEL
1400 bool "Enable Console Acceleration"
1401 depends on FB_SAVAGE
1404 This option will compile in console acceleration support. If
1405 the resulting framebuffer console has bothersome glitches, then
1409 tristate "SiS/XGI display support"
1410 depends on FB && PCI
1411 select FB_CFB_FILLRECT
1412 select FB_CFB_COPYAREA
1413 select FB_CFB_IMAGEBLIT
1414 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1415 select FB_SIS_300 if !FB_SIS_315
1417 This is the frame buffer device driver for the SiS 300, 315, 330
1418 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1419 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1421 To compile this driver as a module, choose M here; the module
1422 will be called sisfb.
1425 bool "SiS 300 series support"
1428 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1431 bool "SiS 315/330/340 series and XGI support"
1434 Say Y here to support use of the SiS 315, 330 and 340 series
1435 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1436 as XGI V3XT, V5, V8 and Z7.
1439 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1440 depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST)
1441 select FB_CFB_FILLRECT
1442 select FB_CFB_COPYAREA
1443 select FB_CFB_IMAGEBLIT
1446 This is the frame buffer device driver for Graphics chips of VIA
1447 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1448 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1450 Say Y if you have a VIA UniChrome graphics board.
1452 To compile this driver as a module, choose M here: the
1453 module will be called viafb.
1457 config FB_VIA_DIRECT_PROCFS
1458 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1461 Allow direct hardware access to some output registers via procfs.
1462 This is dangerous but may provide the only chance to get the
1463 correct output device configuration.
1464 Its use is strongly discouraged.
1466 config FB_VIA_X_COMPATIBILITY
1467 bool "X server compatibility"
1470 This option reduces the functionality (power saving, ...) of the
1471 framebuffer to avoid negative impact on the OpenChrome X server.
1472 If you use any X server other than fbdev you should enable this
1473 otherwise it should be safe to disable it and allow using all
1479 tristate "NeoMagic display support"
1480 depends on FB && PCI
1481 select FB_MODE_HELPERS
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1487 This driver supports notebooks with NeoMagic PCI chips.
1488 Say Y if you have such a graphics card.
1490 To compile this driver as a module, choose M here: the
1491 module will be called neofb.
1494 tristate "IMG Kyro support"
1495 depends on FB && PCI
1496 select FB_CFB_FILLRECT
1497 select FB_CFB_COPYAREA
1498 select FB_CFB_IMAGEBLIT
1500 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1503 To compile this driver as a module, choose M here: the
1504 module will be called kyrofb.
1507 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1508 depends on FB && PCI
1509 select FB_CFB_IMAGEBLIT
1510 select FB_CFB_FILLRECT
1511 select FB_CFB_COPYAREA
1512 select FB_MODE_HELPERS
1514 This driver supports graphics boards with the 3Dfx Banshee,
1515 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1516 such a graphics board.
1518 To compile this driver as a module, choose M here: the
1519 module will be called tdfxfb.
1521 config FB_3DFX_ACCEL
1522 bool "3Dfx Acceleration functions"
1525 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1526 device driver with acceleration functions.
1529 bool "Enable DDC/I2C support"
1534 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1537 tristate "3Dfx Voodoo Graphics (sst1) support"
1538 depends on FB && PCI
1539 select FB_CFB_FILLRECT
1540 select FB_CFB_COPYAREA
1541 select FB_CFB_IMAGEBLIT
1543 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1544 Voodoo2 (cvg) based graphics card.
1546 To compile this driver as a module, choose M here: the
1547 module will be called sstfb.
1549 WARNING: Do not use any application that uses the 3D engine
1550 (namely glide) while using this driver.
1551 Please read the <file:Documentation/fb/sstfb.txt> for supported
1552 options and other important info support.
1555 tristate "VIA VT8623 support"
1556 depends on FB && PCI
1557 select FB_CFB_FILLRECT
1558 select FB_CFB_COPYAREA
1559 select FB_CFB_IMAGEBLIT
1560 select FB_TILEBLITTING
1563 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1565 Driver for CastleRock integrated graphics core in the
1566 VIA VT8623 [Apollo CLE266] chipset.
1569 tristate "Trident/CyberXXX/CyberBlade support"
1570 depends on FB && PCI
1571 select FB_CFB_FILLRECT
1572 select FB_CFB_COPYAREA
1573 select FB_CFB_IMAGEBLIT
1575 select FB_MODE_HELPERS
1577 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1578 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1580 There are also integrated versions of these chips called CyberXXXX,
1581 CyberImage or CyberBlade. These chips are mostly found in laptops
1582 but also on some motherboards including early VIA EPIA motherboards.
1583 For more information, read <file:Documentation/fb/tridentfb.txt>
1585 Say Y if you have such a graphics board.
1587 To compile this driver as a module, choose M here: the
1588 module will be called tridentfb.
1591 tristate "ARK 2000PV support"
1592 depends on FB && PCI
1593 select FB_CFB_FILLRECT
1594 select FB_CFB_COPYAREA
1595 select FB_CFB_IMAGEBLIT
1596 select FB_TILEBLITTING
1599 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1601 Driver for PCI graphics boards with ARK 2000PV chip
1602 and ICS 5342 RAMDAC.
1605 tristate "Permedia3 support"
1606 depends on FB && PCI
1607 select FB_CFB_FILLRECT
1608 select FB_CFB_COPYAREA
1609 select FB_CFB_IMAGEBLIT
1611 This is the frame buffer device driver for the 3DLabs Permedia3
1612 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1613 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1614 and maybe other boards.
1617 tristate "Fujitsu carmine frame buffer support"
1618 depends on FB && PCI
1619 select FB_CFB_FILLRECT
1620 select FB_CFB_COPYAREA
1621 select FB_CFB_IMAGEBLIT
1623 This is the frame buffer device driver for the Fujitsu Carmine chip.
1624 The driver provides two independent frame buffer devices.
1627 depends on FB_CARMINE
1628 prompt "DRAM timing"
1629 default FB_CARMINE_DRAM_EVAL
1631 config FB_CARMINE_DRAM_EVAL
1632 bool "Eval board timings"
1634 Use timings which work on the eval card.
1636 config CARMINE_DRAM_CUSTOM
1637 bool "Custom board timings"
1639 Use custom board timings.
1643 bool "Au1100 LCD Driver"
1644 depends on (FB = y) && MIPS_ALCHEMY
1645 select FB_CFB_FILLRECT
1646 select FB_CFB_COPYAREA
1647 select FB_CFB_IMAGEBLIT
1649 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1650 various panels and CRTs by passing in kernel cmd line option
1651 au1100fb:panel=<name>.
1654 bool "Au1200/Au1300 LCD Driver"
1655 depends on (FB = y) && MIPS_ALCHEMY
1656 select FB_SYS_FILLRECT
1657 select FB_SYS_COPYAREA
1658 select FB_SYS_IMAGEBLIT
1661 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1662 It can drive various panels and CRTs by passing in kernel cmd line
1663 option au1200fb:panel=<name>.
1666 bool "VIA VT8500 framebuffer support"
1667 depends on (FB = y) && ARM && ARCH_VT8500
1668 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1669 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1670 select FB_SYS_IMAGEBLIT
1671 select FB_MODE_HELPERS
1672 select VIDEOMODE_HELPERS
1674 This is the framebuffer driver for VIA VT8500 integrated LCD
1678 bool "Wondermedia WM8xxx-series frame buffer support"
1679 depends on (FB = y) && ARM && ARCH_VT8500
1680 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1681 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1682 select FB_SYS_IMAGEBLIT
1683 select FB_MODE_HELPERS
1684 select VIDEOMODE_HELPERS
1686 This is the framebuffer driver for WonderMedia WM8xxx-series
1687 integrated LCD controller. This driver covers the WM8505, WM8650
1690 config FB_WMT_GE_ROPS
1691 bool "VT8500/WM8xxx accelerated raster ops support"
1692 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1695 This adds support for accelerated raster operations on the
1696 VIA VT8500 and Wondermedia 85xx series SoCs.
1698 source "drivers/video/fbdev/geode/Kconfig"
1701 tristate "HD64461 Frame Buffer support"
1702 depends on FB && HD64461
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 This is the frame buffer device driver for the Hitachi HD64461 LCD
1711 tristate "PMAG-AA TURBOchannel framebuffer support"
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1718 used mainly in the MIPS-based DECstation series.
1721 tristate "PMAG-BA TURBOchannel framebuffer support"
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1728 used mainly in the MIPS-based DECstation series.
1731 tristate "PMAGB-B TURBOchannel framebuffer support"
1733 select FB_CFB_FILLRECT
1734 select FB_CFB_COPYAREA
1735 select FB_CFB_IMAGEBLIT
1737 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1738 in the MIPS-based DECstation series. The card is currently only
1739 supported in 1280x1024x8 mode.
1742 bool "Maxine (Personal DECstation) onboard framebuffer support"
1743 depends on (FB = y) && MACH_DECSTATION
1744 select FB_CFB_FILLRECT
1745 select FB_CFB_COPYAREA
1746 select FB_CFB_IMAGEBLIT
1748 Support for the onboard framebuffer (1024x768x8) in the Personal
1749 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1753 bool "G364 frame buffer support"
1754 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1755 select FB_CFB_FILLRECT
1756 select FB_CFB_COPYAREA
1757 select FB_CFB_IMAGEBLIT
1759 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1760 Olivetti M700-10 systems.
1763 bool "Motorola 68328 native frame buffer support"
1764 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1765 select FB_CFB_FILLRECT
1766 select FB_CFB_COPYAREA
1767 select FB_CFB_IMAGEBLIT
1769 Say Y here if you want to support the built-in frame buffer of
1770 the Motorola 68328 CPU family.
1773 tristate "PXA168/910 LCD framebuffer support"
1774 depends on FB && (CPU_PXA168 || CPU_PXA910)
1775 select FB_CFB_FILLRECT
1776 select FB_CFB_COPYAREA
1777 select FB_CFB_IMAGEBLIT
1779 Frame buffer driver for the built-in LCD controller in the Marvell
1783 tristate "PXA LCD framebuffer support"
1784 depends on FB && ARCH_PXA
1785 select FB_CFB_FILLRECT
1786 select FB_CFB_COPYAREA
1787 select FB_CFB_IMAGEBLIT
1788 select VIDEOMODE_HELPERS if OF
1789 select FB_MODE_HELPERS if OF
1791 Frame buffer driver for the built-in LCD controller in the Intel
1794 This driver is also available as a module ( = code which can be
1795 inserted and removed from the running kernel whenever you want). The
1796 module will be called pxafb. If you want to compile it as a module,
1797 say M here and read <file:Documentation/kbuild/modules.txt>.
1801 config FB_PXA_OVERLAY
1802 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1804 depends on FB_PXA && (PXA27x || PXA3xx)
1806 config FB_PXA_SMARTPANEL
1807 bool "PXA Smartpanel LCD support"
1811 config FB_PXA_PARAMETERS
1812 bool "PXA LCD command line parameters"
1816 Enable the use of kernel command line or module parameters
1817 to configure the physical properties of the LCD panel when
1818 using the PXA LCD driver.
1820 This option allows you to override the panel parameters
1821 supplied by the platform in order to support multiple
1822 different models of flatpanel. If you will only be using a
1823 single model of flatpanel then you can safely leave this
1826 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1829 tristate "PXA3xx 2D graphics accelerator driver"
1832 Kernelspace driver for the 2D graphics controller unit (GCU)
1833 found on PXA3xx processors. There is a counterpart driver in the
1834 DirectFB suite, see http://www.directfb.org/
1836 If you compile this as a module, it will be called pxa3xx_gcu.
1839 tristate "2700G LCD framebuffer support"
1840 depends on FB && ARCH_PXA
1841 select FB_CFB_FILLRECT
1842 select FB_CFB_COPYAREA
1843 select FB_CFB_IMAGEBLIT
1845 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1849 bool "Enable debugging info via debugfs"
1850 depends on FB_MBX && DEBUG_FS
1853 Enable this if you want debugging information using the debug
1854 filesystem (debugfs)
1859 tristate "Freescale DIU framebuffer support"
1860 depends on FB && FSL_SOC
1861 select FB_MODE_HELPERS
1862 select FB_CFB_FILLRECT
1863 select FB_CFB_COPYAREA
1864 select FB_CFB_IMAGEBLIT
1865 select PPC_LIB_RHEAP
1867 Framebuffer driver for the Freescale SoC DIU
1870 tristate "W100 frame buffer support"
1871 depends on FB && ARCH_PXA
1872 select FB_CFB_FILLRECT
1873 select FB_CFB_COPYAREA
1874 select FB_CFB_IMAGEBLIT
1876 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1877 It can also drive the w3220 chip found on iPAQ hx4700.
1879 This driver is also available as a module ( = code which can be
1880 inserted and removed from the running kernel whenever you want). The
1881 module will be called w100fb. If you want to compile it as a module,
1882 say M here and read <file:Documentation/kbuild/modules.txt>.
1886 config FB_SH_MOBILE_LCDC
1887 tristate "SuperH Mobile LCDC framebuffer support"
1888 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1889 select FB_SYS_FILLRECT
1890 select FB_SYS_COPYAREA
1891 select FB_SYS_IMAGEBLIT
1893 select FB_DEFERRED_IO
1896 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1899 tristate "Toshiba Mobile IO FrameBuffer support"
1900 depends on FB && (MFD_TMIO || COMPILE_TEST)
1901 select FB_CFB_FILLRECT
1902 select FB_CFB_COPYAREA
1903 select FB_CFB_IMAGEBLIT
1905 Frame buffer driver for the Toshiba Mobile IO integrated as found
1906 on the Sharp SL-6000 series
1908 This driver is also available as a module ( = code which can be
1909 inserted and removed from the running kernel whenever you want). The
1910 module will be called tmiofb. If you want to compile it as a module,
1911 say M here and read <file:Documentation/kbuild/modules.txt>.
1915 config FB_TMIO_ACCELL
1916 bool "tmiofb acceleration"
1921 tristate "Samsung S3C framebuffer support"
1922 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX)
1923 select FB_CFB_FILLRECT
1924 select FB_CFB_COPYAREA
1925 select FB_CFB_IMAGEBLIT
1927 Frame buffer driver for the built-in FB controller in the Samsung
1928 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1929 and the S3C64XX series such as the S3C6400 and S3C6410.
1931 These chips all have the same basic framebuffer design with the
1932 actual capabilities depending on the chip. For instance the S3C6400
1933 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1934 currently only have two.
1936 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1938 config FB_S3C_DEBUG_REGWRITE
1939 bool "Debug register writes"
1942 Show all register writes via pr_debug()
1945 tristate "S3C2410 LCD framebuffer support"
1946 depends on FB && ARCH_S3C24XX
1947 select FB_CFB_FILLRECT
1948 select FB_CFB_COPYAREA
1949 select FB_CFB_IMAGEBLIT
1951 Frame buffer driver for the built-in LCD controller in the Samsung
1954 This driver is also available as a module ( = code which can be
1955 inserted and removed from the running kernel whenever you want). The
1956 module will be called s3c2410fb. If you want to compile it as a module,
1957 say M here and read <file:Documentation/kbuild/modules.txt>.
1960 config FB_S3C2410_DEBUG
1961 bool "S3C2410 lcd debug messages"
1962 depends on FB_S3C2410
1964 Turn on debugging messages. Note that you can set/unset at run time
1968 tristate "NUC900 LCD framebuffer support"
1969 depends on FB && ARCH_W90X900
1970 select FB_CFB_FILLRECT
1971 select FB_CFB_COPYAREA
1972 select FB_CFB_IMAGEBLIT
1974 Frame buffer driver for the built-in LCD controller in the Nuvoton
1977 config GPM1040A0_320X240
1978 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
1979 depends on FB_NUC900
1982 tristate "Silicon Motion SM501 framebuffer support"
1983 depends on FB && MFD_SM501
1984 select FB_CFB_FILLRECT
1985 select FB_CFB_COPYAREA
1986 select FB_CFB_IMAGEBLIT
1988 Frame buffer driver for the CRT and LCD controllers in the Silicon
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 sm501fb. If you want to compile it as a module,
1994 say M here and read <file:Documentation/kbuild/modules.txt>.
1999 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2000 depends on FB && USB
2001 select FB_MODE_HELPERS
2002 select FB_SYS_FILLRECT
2003 select FB_SYS_COPYAREA
2004 select FB_SYS_IMAGEBLIT
2006 select FB_DEFERRED_IO
2008 This is a kernel framebuffer driver for SMSC UFX USB devices.
2009 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2010 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2012 To compile as a module, choose M here: the module name is smscufx.
2015 tristate "Displaylink USB Framebuffer support"
2016 depends on FB && USB
2017 select FB_MODE_HELPERS
2018 select FB_SYS_FILLRECT
2019 select FB_SYS_COPYAREA
2020 select FB_SYS_IMAGEBLIT
2022 select FB_DEFERRED_IO
2024 This is a kernel framebuffer driver for DisplayLink USB devices.
2025 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2026 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2027 To compile as a module, choose M here: the module name is udlfb.
2029 config FB_IBM_GXT4500
2030 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2032 select FB_CFB_FILLRECT
2033 select FB_CFB_COPYAREA
2034 select FB_CFB_IMAGEBLIT
2036 Say Y here to enable support for the IBM GXT4000P/6000P and
2037 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2038 found on some IBM System P (pSeries) machines. This driver
2039 doesn't use Geometry Engine GT1000. This driver also supports
2040 AGP Fire GL2/3/4 cards on x86.
2043 tristate "PS3 GPU framebuffer driver"
2044 depends on FB && PS3_PS3AV
2045 select FB_SYS_FILLRECT
2046 select FB_SYS_COPYAREA
2047 select FB_SYS_IMAGEBLIT
2050 Include support for the virtual frame buffer in the PS3 platform.
2052 config FB_PS3_DEFAULT_SIZE_M
2053 int "PS3 default frame buffer size (in MiB)"
2057 This is the default size (in MiB) of the virtual frame buffer in
2059 The default value can be overridden on the kernel command line
2060 using the "ps3fb" option (e.g. "ps3fb=9M");
2063 tristate "Xilinx frame buffer support"
2064 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
2065 select FB_CFB_FILLRECT
2066 select FB_CFB_COPYAREA
2067 select FB_CFB_IMAGEBLIT
2069 Include support for the Xilinx ML300/ML403 reference design
2070 framebuffer. ML300 carries a 640*480 LCD display on the board,
2071 ML403 uses a standard DB15 VGA connector.
2074 tristate "Goldfish Framebuffer"
2075 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2076 select FB_CFB_FILLRECT
2077 select FB_CFB_COPYAREA
2078 select FB_CFB_IMAGEBLIT
2080 Framebuffer driver for Goldfish Virtual Platform
2083 tristate "Cobalt server LCD frame buffer support"
2084 depends on FB && MIPS_COBALT
2087 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2088 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2089 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2090 select FB_CFB_FILLRECT
2091 select FB_CFB_COPYAREA
2092 select FB_CFB_IMAGEBLIT
2094 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2095 (D)STN/TFT LCD Controller.
2096 Supports display resolutions up to 1024x1024 pixel, grayscale and
2097 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2098 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2099 panels <= 320 pixel horizontal resolution.
2102 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2103 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2104 select FB_CFB_FILLRECT
2105 select FB_CFB_COPYAREA
2106 select FB_CFB_IMAGEBLIT
2107 select FB_CFB_REV_PIXELS_IN_BYTE
2108 select FB_MODE_HELPERS
2109 select VIDEOMODE_HELPERS
2111 This is the frame buffer device driver for the TI LCD controller
2112 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2116 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2118 select FB_SYS_FILLRECT
2119 select FB_SYS_COPYAREA
2120 select FB_SYS_IMAGEBLIT
2123 This is a `virtual' frame buffer device. It operates on a chunk of
2124 unswappable kernel memory instead of on the memory of a graphics
2125 board. This means you cannot see any output sent to this frame
2126 buffer device, while it does consume precious memory. The main use
2127 of this frame buffer device is testing and debugging the frame
2128 buffer subsystem. Do NOT enable it for normal systems! To protect
2129 the innocent, it has to be enabled explicitly at boot time using the
2130 kernel option `video=vfb:'.
2132 To compile this driver as a module, choose M here: the
2133 module will be called vfb. In order to load it, you must use
2134 the vfb_enable=1 option.
2138 config XEN_FBDEV_FRONTEND
2139 tristate "Xen virtual frame buffer support"
2140 depends on FB && XEN
2141 select FB_SYS_FILLRECT
2142 select FB_SYS_COPYAREA
2143 select FB_SYS_IMAGEBLIT
2145 select FB_DEFERRED_IO
2146 select XEN_XENBUS_FRONTEND
2149 This driver implements the front-end of the Xen virtual
2150 frame buffer driver. It communicates with a back-end
2154 tristate "E-Ink Metronome/8track controller support"
2156 select FB_SYS_FILLRECT
2157 select FB_SYS_COPYAREA
2158 select FB_SYS_IMAGEBLIT
2160 select FB_DEFERRED_IO
2162 This driver implements support for the E-Ink Metronome
2163 controller. The pre-release name for this device was 8track
2164 and could also have been called by some vendors as PVI-nnnn.
2167 tristate "Fujitsu MB862xx GDC support"
2169 depends on PCI || (OF && PPC)
2170 select FB_CFB_FILLRECT
2171 select FB_CFB_COPYAREA
2172 select FB_CFB_IMAGEBLIT
2174 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2177 prompt "GDC variant"
2178 depends on FB_MB862XX
2180 config FB_MB862XX_PCI_GDC
2181 bool "Carmine/Coral-P(A) GDC"
2184 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2185 PCI graphics controller devices.
2187 config FB_MB862XX_LIME
2189 depends on OF && PPC
2190 select FB_FOREIGN_ENDIAN
2191 select FB_LITTLE_ENDIAN
2193 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2197 config FB_MB862XX_I2C
2198 bool "Support I2C bus on MB862XX GDC"
2199 depends on FB_MB862XX && I2C
2200 depends on FB_MB862XX=m || I2C=y
2203 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2204 driver to support accessing I2C devices on controller's I2C bus.
2205 These are usually some video decoder chips.
2208 tristate "EP93XX frame buffer support"
2209 depends on FB && ARCH_EP93XX
2210 select FB_CFB_FILLRECT
2211 select FB_CFB_COPYAREA
2212 select FB_CFB_IMAGEBLIT
2214 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2215 This driver is also available as a module. The module will be called
2218 config FB_PRE_INIT_FB
2219 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2220 depends on FB && FB_MB862XX_LIME
2222 Select this option if display contents should be inherited as set by
2226 tristate "MX3 Framebuffer support"
2227 depends on FB && MX3_IPU
2228 select BACKLIGHT_CLASS_DEVICE
2229 select BACKLIGHT_LCD_SUPPORT
2230 select FB_CFB_FILLRECT
2231 select FB_CFB_COPYAREA
2232 select FB_CFB_IMAGEBLIT
2235 This is a framebuffer device for the i.MX31 LCD Controller. So
2236 far only synchronous displays are supported. If you plan to use
2237 an LCD display with your i.MX31 system, say Y here.
2239 config FB_BROADSHEET
2240 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2241 depends on FB && (ARCH_PXA || COMPILE_TEST)
2242 select FB_SYS_FILLRECT
2243 select FB_SYS_COPYAREA
2244 select FB_SYS_IMAGEBLIT
2246 select FB_DEFERRED_IO
2248 This driver implements support for the E-Ink Broadsheet
2249 controller. The release name for this device was Epson S1D13521
2250 and could also have been called by other names when coupled with
2254 tristate "JZ4740 LCD framebuffer support"
2255 depends on FB && MACH_JZ4740
2256 select FB_SYS_FILLRECT
2257 select FB_SYS_COPYAREA
2258 select FB_SYS_IMAGEBLIT
2260 Framebuffer support for the JZ4740 SoC.
2263 tristate "MXS LCD framebuffer support"
2264 depends on FB && (ARCH_MXS || ARCH_MXC)
2265 select FB_CFB_FILLRECT
2266 select FB_CFB_COPYAREA
2267 select FB_CFB_IMAGEBLIT
2268 select FB_MODE_HELPERS
2269 select VIDEOMODE_HELPERS
2271 Framebuffer support for the MXS SoC.
2273 config FB_PUV3_UNIGFX
2274 tristate "PKUnity v3 Unigfx framebuffer support"
2275 depends on FB && UNICORE32 && ARCH_PUV3
2276 select FB_SYS_FILLRECT
2277 select FB_SYS_COPYAREA
2278 select FB_SYS_IMAGEBLIT
2281 Choose this option if you want to use the Unigfx device as a
2282 framebuffer device. Without the support of PCI & AGP.
2285 tristate "Microsoft Hyper-V Synthetic Video support"
2286 depends on FB && HYPERV
2287 select FB_CFB_FILLRECT
2288 select FB_CFB_COPYAREA
2289 select FB_CFB_IMAGEBLIT
2291 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2294 bool "Simple framebuffer support"
2296 select FB_CFB_FILLRECT
2297 select FB_CFB_COPYAREA
2298 select FB_CFB_IMAGEBLIT
2300 Say Y if you want support for a simple frame-buffer.
2302 This driver assumes that the display hardware has been initialized
2303 before the kernel boots, and the kernel will simply render to the
2304 pre-allocated frame buffer surface.
2306 Configuration re: surface address, size, and format must be provided
2307 through device tree, or plain old platform data.
2310 tristate "Solomon SSD1307 framebuffer support"
2311 depends on FB && I2C
2313 depends on GPIOLIB || COMPILE_TEST
2315 select FB_SYS_FILLRECT
2316 select FB_SYS_COPYAREA
2317 select FB_SYS_IMAGEBLIT
2318 select FB_DEFERRED_IO
2322 This driver implements support for the Solomon SSD1307
2323 OLED controller over I2C.
2326 tristate "Silicon Motion SM712 framebuffer support"
2327 depends on FB && PCI
2328 select FB_CFB_FILLRECT
2329 select FB_CFB_COPYAREA
2330 select FB_CFB_IMAGEBLIT
2332 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2335 This driver is also available as a module. The module will be
2336 called sm712fb. If you want to compile it as a module, say M
2337 here and read <file:Documentation/kbuild/modules.txt>.
2339 source "drivers/video/fbdev/omap/Kconfig"
2340 source "drivers/video/fbdev/omap2/Kconfig"
2341 source "drivers/video/fbdev/mmp/Kconfig"