12 tristate "Support for frame buffer devices"
16 The frame buffer device provides an abstraction for the graphics
17 hardware. It represents the frame buffer of some video hardware and
18 allows application software to access the graphics hardware through
19 a well-defined interface, so the software doesn't need to know
20 anything about the low-level (hardware register) stuff.
22 Frame buffer devices work identically across the different
23 architectures supported by Linux and make the implementation of
24 application programs easier and more portable; at this point, an X
25 server exists which uses the frame buffer device exclusively.
26 On several non-X86 architectures, the frame buffer device is the
27 only way to use the graphics hardware.
29 The device is accessed through special device nodes, usually located
30 in the /dev directory, i.e. /dev/fb*.
32 You need an utility program called fbset to make full use of frame
33 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
34 and the Framebuffer-HOWTO at
35 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
38 Say Y here and to the driver for your graphics board below if you
39 are compiling a kernel for a non-x86 architecture.
41 If you are compiling for the x86 architecture, you can say Y if you
42 want to play with it, but it is not essential. Please note that
43 running graphical applications that directly touch the hardware
44 (e.g. an accelerated X server) and that are not frame buffer
45 device-aware may cause unexpected results. If unsure, say N.
48 bool "Enable firmware EDID"
51 This enables access to the EDID transferred from the firmware.
52 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
53 transfers do not work for your driver and if you are using
54 nvidiafb, i810fb or savagefb.
56 In general, choosing Y for this option is safe. If you
57 experience extremely long delays while booting before you get
58 something on your display, try setting this to N. Matrox cards in
59 combination with certain motherboards and monitors are known to
60 suffer from this problem.
68 config FB_BOOT_VESA_SUPPORT
72 If true, at least one selected framebuffer driver can take advantage
73 of VESA video modes set at an early boot stage via the vga= parameter.
75 config FB_CFB_FILLRECT
79 Include the cfb_fillrect function for generic software rectangle
80 filling. This is used by drivers that don't provide their own
81 (accelerated) version.
83 config FB_CFB_COPYAREA
87 Include the cfb_copyarea function for generic software area copying.
88 This is used by drivers that don't provide their own (accelerated)
91 config FB_CFB_IMAGEBLIT
95 Include the cfb_imageblit function for generic software image
96 blitting. This is used by drivers that don't provide their own
97 (accelerated) version.
99 config FB_CFB_REV_PIXELS_IN_BYTE
103 Allow generic frame-buffer functions to work on displays with 1, 2
104 and 4 bits per pixel depths which has opposite order of pixels in
105 byte order to bytes in long order.
107 config FB_SYS_FILLRECT
111 Include the sys_fillrect function for generic software rectangle
112 filling. This is used by drivers that don't provide their own
113 (accelerated) version and the framebuffer is in system RAM.
115 config FB_SYS_COPYAREA
119 Include the sys_copyarea function for generic software area copying.
120 This is used by drivers that don't provide their own (accelerated)
121 version and the framebuffer is in system RAM.
123 config FB_SYS_IMAGEBLIT
127 Include the sys_imageblit function for generic software image
128 blitting. This is used by drivers that don't provide their own
129 (accelerated) version and the framebuffer is in system RAM.
131 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
135 Allow generic frame-buffer to provide get_fb_unmapped_area
138 menuconfig FB_FOREIGN_ENDIAN
139 bool "Framebuffer foreign endianness support"
142 This menu will let you enable support for the framebuffers with
143 non-native endianness (e.g. Little-Endian framebuffer on a
144 Big-Endian machine). Most probably you don't have such hardware,
145 so it's safe to say "n" here.
148 prompt "Choice endianness support"
149 depends on FB_FOREIGN_ENDIAN
151 config FB_BOTH_ENDIAN
152 bool "Support for Big- and Little-Endian framebuffers"
155 bool "Support for Big-Endian framebuffers only"
157 config FB_LITTLE_ENDIAN
158 bool "Support for Little-Endian framebuffers only"
166 config FB_DEFERRED_IO
173 depends on FB_DEFERRED_IO
179 Common utility functions useful to fbdev drivers of VGA-based
189 select BACKLIGHT_LCD_SUPPORT
190 select BACKLIGHT_CLASS_DEVICE
192 config FB_MODE_HELPERS
193 bool "Enable Video Mode Handling Helpers"
196 This enables functions for handling video modes using the
197 Generalized Timing Formula and the EDID parser. A few drivers rely
198 on this feature such as the radeonfb, rivafb, and the i810fb. If
199 your driver does not take advantage of this feature, choosing Y will
200 just increase the kernel size by about 5K.
202 config FB_TILEBLITTING
203 bool "Enable Tile Blitting Support"
206 This enables tile blitting. Tile blitting is a drawing technique
207 where the screen is divided into rectangular sections (tiles), whereas
208 the standard blitting divides the screen into pixels. Because the
209 default drawing element is a tile, drawing functions will be passed
210 parameters in terms of number of tiles instead of number of pixels.
211 For example, to draw a single character, instead of using bitmaps,
212 an index to an array of bitmaps will be used. To clear or move a
213 rectangular section of a screen, the rectangle will be described in
214 terms of number of tiles in the x- and y-axis.
216 This is particularly important to one driver, matroxfb. If
219 comment "Frame buffer hardware drivers"
223 tristate "Aeroflex Gaisler framebuffer support"
224 depends on FB && SPARC
225 select FB_CFB_FILLRECT
226 select FB_CFB_COPYAREA
227 select FB_CFB_IMAGEBLIT
229 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
232 tristate "Cirrus Logic support"
233 depends on FB && (ZORRO || PCI)
234 select FB_CFB_FILLRECT
235 select FB_CFB_COPYAREA
236 select FB_CFB_IMAGEBLIT
238 This enables support for Cirrus Logic GD542x/543x based boards on
239 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
241 If you have a PCI-based system, this enables support for these
242 chips: GD-543x, GD-544x, GD-5480.
244 Please read the file <file:Documentation/fb/cirrusfb.txt>.
246 Say N unless you have such a graphics board or plan to get one
247 before you next recompile the kernel.
250 tristate "Permedia2 support"
251 depends on FB && ((AMIGA && BROKEN) || PCI)
252 select FB_CFB_FILLRECT
253 select FB_CFB_COPYAREA
254 select FB_CFB_IMAGEBLIT
256 This is the frame buffer device driver for cards based on
257 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
258 The driver was tested on the following cards:
259 Diamond FireGL 1000 PRO AGP
260 ELSA Gloria Synergy PCI
261 Appian Jeronimo PRO (both heads) PCI
262 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
263 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
264 ASK Graphic Blaster Exxtreme AGP
266 To compile this driver as a module, choose M here: the
267 module will be called pm2fb.
269 config FB_PM2_FIFO_DISCONNECT
270 bool "enable FIFO disconnect feature"
271 depends on FB_PM2 && PCI
273 Support the Permedia2 FIFO disconnect feature.
276 tristate "ARM PrimeCell PL110 support"
277 depends on ARM || ARM64 || COMPILE_TEST
278 depends on FB && ARM_AMBA && HAS_IOMEM
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
282 select FB_MODE_HELPERS if OF
283 select VIDEOMODE_HELPERS if OF
284 select BACKLIGHT_LCD_SUPPORT if OF
285 select BACKLIGHT_CLASS_DEVICE if OF
287 This framebuffer device driver is for the ARM PrimeCell PL110
288 Colour LCD controller. ARM PrimeCells provide the building
289 blocks for System on a Chip devices.
291 If you want to compile this as a module (=code which can be
292 inserted into and removed from the running kernel), say M
293 here and read <file:Documentation/kbuild/modules.txt>. The module
294 will be called amba-clcd.
296 # Helper logic selected only by the ARM Versatile platform family.
297 config PLAT_VERSATILE_CLCD
298 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
300 depends on FB_ARMCLCD && FB=y
305 bool "Acorn VIDC support"
306 depends on (FB = y) && ARM && ARCH_ACORN
307 select FB_CFB_FILLRECT
308 select FB_CFB_COPYAREA
309 select FB_CFB_IMAGEBLIT
311 This is the frame buffer device driver for the Acorn VIDC graphics
312 hardware found in Acorn RISC PCs and other ARM-based machines. If
316 tristate "CLPS711X LCD support"
317 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
318 select BACKLIGHT_LCD_SUPPORT
319 select FB_MODE_HELPERS
320 select FB_SYS_FILLRECT
321 select FB_SYS_COPYAREA
322 select FB_SYS_IMAGEBLIT
323 select LCD_CLASS_DEVICE
324 select VIDEOMODE_HELPERS
326 Say Y to enable the Framebuffer driver for the Cirrus Logic
330 bool "SA-1100 LCD support"
331 depends on (FB = y) && ARM && ARCH_SA1100
332 select FB_CFB_FILLRECT
333 select FB_CFB_COPYAREA
334 select FB_CFB_IMAGEBLIT
336 This is a framebuffer device for the SA-1100 LCD Controller.
337 See <http://www.linux-fbdev.org/> for information on framebuffer
340 If you plan to use the LCD display with your SA-1100 system, say
344 tristate "Freescale i.MX1/21/25/27 LCD support"
345 depends on FB && ARCH_MXC
346 select BACKLIGHT_LCD_SUPPORT
347 select LCD_CLASS_DEVICE
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
351 select FB_MODE_HELPERS
352 select VIDEOMODE_HELPERS
355 tristate "CyberPro 2000/2010/5000 support"
356 depends on FB && PCI && (BROKEN || !SPARC64)
357 select FB_CFB_FILLRECT
358 select FB_CFB_COPYAREA
359 select FB_CFB_IMAGEBLIT
361 This enables support for the Integraphics CyberPro 20x0 and 5000
362 VGA chips used in the Rebel.com Netwinder and other machines.
363 Say Y if you have a NetWinder or a graphics card containing this
364 device, otherwise say N.
366 config FB_CYBER2000_DDC
367 bool "DDC for CyberPro support"
368 depends on FB_CYBER2000
372 Say Y here if you want DDC support for your CyberPro graphics
373 card. This is only I2C bus support, driver does not use EDID.
375 config FB_CYBER2000_I2C
376 bool "CyberPro 2000/2010/5000 I2C support"
377 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
378 depends on I2C=y || FB_CYBER2000=m
381 Enable support for the I2C video decoder interface on the
382 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
383 on the Netwinder machines for the SAA7111 video capture.
387 depends on (FB = y) && APOLLO
389 select FB_CFB_FILLRECT
390 select FB_CFB_IMAGEBLIT
394 depends on (FB = y) && Q40
396 select FB_CFB_FILLRECT
397 select FB_CFB_COPYAREA
398 select FB_CFB_IMAGEBLIT
401 tristate "Amiga native chipset support"
402 depends on FB && AMIGA
404 This is the frame buffer device driver for the builtin graphics
405 chipset found in Amigas.
407 To compile this driver as a module, choose M here: the
408 module will be called amifb.
411 bool "Amiga OCS chipset support"
414 This enables support for the original Agnus and Denise video chips,
415 found in the Amiga 1000 and most A500's and A2000's. If you intend
416 to run Linux on any of these systems, say Y; otherwise say N.
419 bool "Amiga ECS chipset support"
422 This enables support for the Enhanced Chip Set, found in later
423 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
424 you intend to run Linux on any of these systems, say Y; otherwise
428 bool "Amiga AGA chipset support"
431 This enables support for the Advanced Graphics Architecture (also
432 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
433 and CD32. If you intend to run Linux on any of these systems, say Y;
437 bool "Amiga FrameMaster II/Rainbow II support"
438 depends on (FB = y) && ZORRO
439 select FB_CFB_FILLRECT
440 select FB_CFB_COPYAREA
441 select FB_CFB_IMAGEBLIT
443 This is the frame buffer device driver for the Amiga FrameMaster
444 card from BSC (exhibited 1992 but not shipped as a CBM product).
447 tristate "Arc Monochrome LCD board support"
449 select FB_SYS_FILLRECT
450 select FB_SYS_COPYAREA
451 select FB_SYS_IMAGEBLIT
454 This enables support for the Arc Monochrome LCD board. The board
455 is based on the KS-108 lcd controller and is typically a matrix
456 of 2*n chips. This driver was tested with a 128x64 panel. This
457 driver supports it for use with x86 SBCs through a 16 bit GPIO
458 interface (8 bit data, 8 bit control). If you anticipate using
459 this driver, say Y or M; otherwise say N. You must specify the
460 GPIO IO address to be used for setting control and data.
463 bool "Atari native chipset support"
464 depends on (FB = y) && ATARI
465 select FB_CFB_FILLRECT
466 select FB_CFB_COPYAREA
467 select FB_CFB_IMAGEBLIT
469 This is the frame buffer device driver for the builtin graphics
470 chipset found in Ataris.
473 bool "Open Firmware frame buffer device support"
474 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
475 select FB_CFB_FILLRECT
476 select FB_CFB_COPYAREA
477 select FB_CFB_IMAGEBLIT
480 Say Y if you want support with Open Firmware for your graphics
484 bool "Apple \"control\" display support"
485 depends on (FB = y) && PPC_PMAC && PPC32
486 select FB_CFB_FILLRECT
487 select FB_CFB_COPYAREA
488 select FB_CFB_IMAGEBLIT
491 This driver supports a frame buffer for the graphics adapter in the
492 Power Macintosh 7300 and others.
495 bool "Apple \"platinum\" display support"
496 depends on (FB = y) && PPC_PMAC && PPC32
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
502 This driver supports a frame buffer for the "platinum" graphics
503 adapter in some Power Macintoshes.
506 bool "Apple \"valkyrie\" display support"
507 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
513 This driver supports a frame buffer for the "valkyrie" graphics
514 adapter in some Power Macintoshes.
517 bool "Chips 65550 display support"
518 depends on (FB = y) && PPC32 && PCI
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
523 This is the frame buffer device driver for the Chips & Technologies
524 65550 graphics chip in PowerBooks.
527 bool "Asiliant (Chips) 69000 display support"
528 depends on (FB = y) && PCI
529 select FB_CFB_FILLRECT
530 select FB_CFB_COPYAREA
531 select FB_CFB_IMAGEBLIT
533 This is the frame buffer device driver for the Asiliant 69030 chipset
536 bool "IMS Twin Turbo display support"
537 depends on (FB = y) && PCI
538 select FB_CFB_IMAGEBLIT
539 select FB_MACMODES if PPC_PMAC
541 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
542 many Macintosh and compatible computers.
545 tristate "VGA 16-color graphics support"
546 depends on FB && (X86 || PPC)
547 select FB_CFB_FILLRECT
548 select FB_CFB_COPYAREA
549 select FB_CFB_IMAGEBLIT
551 select FONT_8x16 if FRAMEBUFFER_CONSOLE
553 This is the frame buffer device driver for VGA 16 color graphic
554 cards. Say Y if you have such a card.
556 To compile this driver as a module, choose M here: the
557 module will be called vga16fb.
560 tristate "HP STI frame buffer device support"
561 depends on FB && PARISC
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
567 STI refers to the HP "Standard Text Interface" which is a set of
568 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
569 Enabling this option will implement the linux framebuffer device
570 using calls to the STI BIOS routines for initialisation.
572 If you enable this option, you will get a planar framebuffer device
573 /dev/fb which will work on the most common HP graphic cards of the
574 NGLE family, including the artist chips (in the 7xx and Bxxx series),
575 HCRX, HCRX24, CRX, CRX24 and VisEG series.
577 It is safe to enable this option, so you should probably say "Y".
580 bool "Generic Macintosh display support"
581 depends on (FB = y) && MAC
582 select FB_CFB_FILLRECT
583 select FB_CFB_COPYAREA
584 select FB_CFB_IMAGEBLIT
589 depends on (FB = y) && DIO
590 select FB_CFB_IMAGEBLIT
594 tristate "TGA/SFB+ framebuffer support"
595 depends on FB && (ALPHA || TC)
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
601 This is the frame buffer device driver for generic TGA and SFB+
602 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
603 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
604 TURBOchannel cards, also known as PMAGD-A, -B and -C.
606 Due to hardware limitations ZLX-E2 and E3 cards are not supported
607 for DECstation 5000/200 systems. Additionally due to firmware
608 limitations these cards may cause troubles with booting DECstation
609 5000/240 and /260 systems, but are fully supported under Linux if
610 you manage to get it going. ;-)
612 Say Y if you have one of those.
615 tristate "Userspace VESA VGA graphics support"
616 depends on FB && CONNECTOR
617 select FB_CFB_FILLRECT
618 select FB_CFB_COPYAREA
619 select FB_CFB_IMAGEBLIT
620 select FB_MODE_HELPERS
622 This is the frame buffer driver for generic VBE 2.0 compliant
623 graphic cards. It can also take advantage of VBE 3.0 features,
624 such as refresh rate adjustment.
626 This driver generally provides more features than vesafb but
627 requires a userspace helper application called 'v86d'. See
628 <file:Documentation/fb/uvesafb.txt> for more information.
633 bool "VESA VGA graphics support"
634 depends on (FB = y) && X86
635 select FB_CFB_FILLRECT
636 select FB_CFB_COPYAREA
637 select FB_CFB_IMAGEBLIT
638 select FB_BOOT_VESA_SUPPORT
640 This is the frame buffer device driver for generic VESA 2.0
641 compliant graphic cards. The older VESA 1.2 cards are not supported.
642 You will get a boot time penguin logo at no additional cost. Please
643 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
646 bool "EFI-based Framebuffer Support"
647 depends on (FB = y) && !IA64 && EFI
648 select DRM_PANEL_ORIENTATION_QUIRKS
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
653 This is the EFI frame buffer device driver. If the firmware on
654 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
655 using the EFI framebuffer as your console.
658 tristate "N411 Apollo/Hecuba devkit support"
659 depends on FB && X86 && MMU
660 select FB_SYS_FILLRECT
661 select FB_SYS_COPYAREA
662 select FB_SYS_IMAGEBLIT
664 select FB_DEFERRED_IO
667 This enables support for the Apollo display controller in its
668 Hecuba form using the n411 devkit.
671 tristate "Hercules mono graphics support"
674 Say Y here if you have a Hercules mono graphics card.
676 To compile this driver as a module, choose M here: the
677 module will be called hgafb.
679 As this card technology is at least 25 years old,
680 most people will answer N here.
683 bool "SGI Graphics Backend frame buffer support"
684 depends on (FB = y) && SGI_IP32
685 select FB_CFB_FILLRECT
686 select FB_CFB_COPYAREA
687 select FB_CFB_IMAGEBLIT
689 This is the frame buffer device driver for SGI Graphics Backend.
690 This chip is used in SGI O2 and Visual Workstation 320/540.
693 int "Video memory size in MB"
697 This is the amount of memory reserved for the framebuffer,
698 which can be any value between 1MB and 8MB.
701 bool "SBUS and UPA framebuffers"
702 depends on (FB = y) && SPARC
704 Say Y if you want support for SBUS or UPA based frame buffer device.
708 depends on (FB = y) && (SPARC && FB_SBUS)
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
713 This is the frame buffer device driver for the BWtwo frame buffer.
716 bool "CGthree support"
717 depends on (FB = y) && (SPARC && FB_SBUS)
718 select FB_CFB_FILLRECT
719 select FB_CFB_COPYAREA
720 select FB_CFB_IMAGEBLIT
722 This is the frame buffer device driver for the CGthree frame buffer.
725 bool "CGsix (GX,TurboGX) support"
726 depends on (FB = y) && (SPARC && FB_SBUS)
727 select FB_CFB_COPYAREA
728 select FB_CFB_IMAGEBLIT
730 This is the frame buffer device driver for the CGsix (GX, TurboGX)
734 bool "Creator/Creator3D/Elite3D support"
735 depends on FB_SBUS && SPARC64
736 select FB_CFB_COPYAREA
737 select FB_CFB_IMAGEBLIT
739 This is the frame buffer device driver for the Creator, Creator3D,
740 and Elite3D graphics boards.
743 bool "TCX (SS4/SS5 only) support"
745 select FB_CFB_FILLRECT
746 select FB_CFB_COPYAREA
747 select FB_CFB_IMAGEBLIT
749 This is the frame buffer device driver for the TCX 24/8bit frame
753 bool "CGfourteen (SX) support"
755 select FB_CFB_FILLRECT
756 select FB_CFB_COPYAREA
757 select FB_CFB_IMAGEBLIT
759 This is the frame buffer device driver for the CGfourteen frame
760 buffer on Desktop SPARCsystems with the SX graphics option.
763 bool "P9100 (Sparcbook 3 only) support"
765 select FB_CFB_FILLRECT
766 select FB_CFB_COPYAREA
767 select FB_CFB_IMAGEBLIT
769 This is the frame buffer device driver for the P9100 card
770 supported on Sparcbook 3 machines.
773 bool "Leo (ZX) support"
775 select FB_CFB_FILLRECT
776 select FB_CFB_COPYAREA
777 select FB_CFB_IMAGEBLIT
779 This is the frame buffer device driver for the SBUS-based Sun ZX
780 (leo) frame buffer cards.
783 bool "Sun XVR-500 3DLABS Wildcat support"
784 depends on (FB = y) && PCI && SPARC64
785 select FB_CFB_FILLRECT
786 select FB_CFB_COPYAREA
787 select FB_CFB_IMAGEBLIT
789 This is the framebuffer device for the Sun XVR-500 and similar
790 graphics cards based upon the 3DLABS Wildcat chipset. The driver
791 only works on sparc64 systems where the system firmware has
792 mostly initialized the card already. It is treated as a
793 completely dumb framebuffer device.
796 bool "Sun XVR-2500 3DLABS Wildcat support"
797 depends on (FB = y) && PCI && SPARC64
798 select FB_CFB_FILLRECT
799 select FB_CFB_COPYAREA
800 select FB_CFB_IMAGEBLIT
802 This is the framebuffer device for the Sun XVR-2500 and similar
803 graphics cards based upon the 3DLABS Wildcat chipset. The driver
804 only works on sparc64 systems where the system firmware has
805 mostly initialized the card already. It is treated as a
806 completely dumb framebuffer device.
809 bool "Sun XVR-1000 support"
810 depends on (FB = y) && SPARC64
811 select FB_CFB_FILLRECT
812 select FB_CFB_COPYAREA
813 select FB_CFB_IMAGEBLIT
815 This is the framebuffer device for the Sun XVR-1000 and similar
816 graphics cards. The driver only works on sparc64 systems where
817 the system firmware has mostly initialized the card already. It
818 is treated as a completely dumb framebuffer device.
821 tristate "NEC PowerVR 2 display support"
822 depends on FB && SH_DREAMCAST
823 select FB_CFB_FILLRECT
824 select FB_CFB_COPYAREA
825 select FB_CFB_IMAGEBLIT
827 Say Y here if you have a PowerVR 2 card in your box. If you plan to
828 run linux on your Dreamcast, you will have to say Y here.
829 This driver may or may not work on other PowerVR 2 cards, but is
830 totally untested. Use at your own risk. If unsure, say N.
832 To compile this driver as a module, choose M here: the
833 module will be called pvr2fb.
835 You can pass several parameters to the driver at boot time or at
836 module load time. The parameters look like "video=pvr2:XXX", where
837 the meaning of XXX can be found at the end of the main source file
838 (<file:drivers/video/pvr2fb.c>). Please see the file
839 <file:Documentation/fb/pvr2fb.txt>.
842 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
843 depends on FB && HAS_DMA
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This enables support for the OpenCores VGA/LCD core.
850 The OpenCores VGA/LCD core is typically used together with
851 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
852 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
854 The source code and specification for the core is available at
855 <http://opencores.org/project,vga_lcd>
858 tristate "Epson S1D13XXX framebuffer support"
860 select FB_CFB_FILLRECT
861 select FB_CFB_COPYAREA
862 select FB_CFB_IMAGEBLIT
864 Support for S1D13XXX framebuffer device family (currently only
865 working with S1D13806). Product specs at
866 <http://vdc.epson.com/>
869 tristate "AT91/AT32 LCD Controller support"
870 depends on FB && HAVE_FB_ATMEL
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
875 select FB_MODE_HELPERS
876 select VIDEOMODE_HELPERS
878 This enables support for the AT91/AT32 LCD Controller.
881 tristate "nVidia Framebuffer Support"
883 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
884 select FB_MODE_HELPERS
885 select FB_CFB_FILLRECT
886 select FB_CFB_COPYAREA
887 select FB_CFB_IMAGEBLIT
891 This driver supports graphics boards with the nVidia chips, TNT
892 and newer. For very old chipsets, such as the RIVA128, then use
894 Say Y if you have such a graphics board.
896 To compile this driver as a module, choose M here: the
897 module will be called nvidiafb.
900 bool "Enable DDC Support"
904 This enables I2C support for nVidia Chipsets. This is used
905 only for getting EDID information from the attached display
906 allowing for robust video mode handling and switching.
908 Because fbdev-2.6 requires that drivers must be able to
909 independently validate video mode parameters, you should say Y
912 config FB_NVIDIA_DEBUG
913 bool "Lots of debug output"
916 Say Y here if you want the nVidia driver to output all sorts
917 of debugging information to provide to the maintainer when
918 something goes wrong.
920 config FB_NVIDIA_BACKLIGHT
921 bool "Support for backlight control"
925 Say Y here if you want to control the backlight of your display.
928 tristate "nVidia Riva support"
930 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
931 select FB_MODE_HELPERS
932 select FB_CFB_FILLRECT
933 select FB_CFB_COPYAREA
934 select FB_CFB_IMAGEBLIT
938 This driver supports graphics boards with the nVidia Riva/Geforce
940 Say Y if you have such a graphics board.
942 To compile this driver as a module, choose M here: the
943 module will be called rivafb.
946 bool "Enable DDC Support"
950 This enables I2C support for nVidia Chipsets. This is used
951 only for getting EDID information from the attached display
952 allowing for robust video mode handling and switching.
954 Because fbdev-2.6 requires that drivers must be able to
955 independently validate video mode parameters, you should say Y
959 bool "Lots of debug output"
962 Say Y here if you want the Riva driver to output all sorts
963 of debugging information to provide to the maintainer when
964 something goes wrong.
966 config FB_RIVA_BACKLIGHT
967 bool "Support for backlight control"
971 Say Y here if you want to control the backlight of your display.
974 tristate "Intel740 support"
976 select FB_MODE_HELPERS
977 select FB_CFB_FILLRECT
978 select FB_CFB_COPYAREA
979 select FB_CFB_IMAGEBLIT
983 This driver supports graphics cards based on Intel740 chip.
986 tristate "Intel 810/815 support"
987 depends on FB && PCI && X86_32 && AGP_INTEL
988 select FB_MODE_HELPERS
989 select FB_CFB_FILLRECT
990 select FB_CFB_COPYAREA
991 select FB_CFB_IMAGEBLIT
994 This driver supports the on-board graphics built in to the Intel 810
995 and 815 chipsets. Say Y if you have and plan to use such a board.
997 To compile this driver as a module, choose M here: the
998 module will be called i810fb.
1000 For more information, please read
1001 <file:Documentation/fb/intel810.txt>
1004 bool "use VESA Generalized Timing Formula"
1007 If you say Y, then the VESA standard, Generalized Timing Formula
1008 or GTF, will be used to calculate the required video timing values
1009 per video mode. Since the GTF allows nondiscrete timings
1010 (nondiscrete being a range of values as opposed to discrete being a
1011 set of values), you'll be able to use any combination of horizontal
1012 and vertical resolutions, and vertical refresh rates without having
1013 to specify your own timing parameters. This is especially useful
1014 to maximize the performance of an aging display, or if you just
1015 have a display with nonstandard dimensions. A VESA compliant
1016 monitor is recommended, but can still work with non-compliant ones.
1017 If you need or want this, then select this option. The timings may
1018 not be compliant with Intel's recommended values. Use at your own
1021 If you say N, the driver will revert to discrete video timings
1022 using a set recommended by Intel in their documentation.
1027 bool "Enable DDC Support"
1028 depends on FB_I810 && FB_I810_GTF
1031 Add DDC/I2C support for i810fb. This will allow the driver to get
1032 display information, especially for monitors with fickle timings.
1037 tristate "Intel LE80578 (Vermilion) support"
1038 depends on FB && PCI && X86
1039 select FB_MODE_HELPERS
1040 select FB_CFB_FILLRECT
1041 select FB_CFB_COPYAREA
1042 select FB_CFB_IMAGEBLIT
1044 This driver supports the LE80578 (Vermilion Range) chipset
1046 config FB_CARILLO_RANCH
1047 tristate "Intel Carillo Ranch support"
1048 depends on FB_LE80578 && FB && PCI && X86
1050 This driver supports the LE80578 (Carillo Ranch) board
1053 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1054 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1055 select FB_MODE_HELPERS
1056 select FB_CFB_FILLRECT
1057 select FB_CFB_COPYAREA
1058 select FB_CFB_IMAGEBLIT
1059 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1060 depends on !DRM_I915
1062 This driver supports the on-board graphics built in to the Intel
1063 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1064 Say Y if you have and plan to use such a board.
1066 To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
1068 To compile this driver as a module, choose M here: the
1069 module will be called intelfb.
1071 For more information, please read <file:Documentation/fb/intelfb.txt>
1073 config FB_INTEL_DEBUG
1074 bool "Intel driver Debug Messages"
1077 Say Y here if you want the Intel driver to output all sorts
1078 of debugging information to provide to the maintainer when
1079 something goes wrong.
1082 bool "DDC/I2C for Intel framebuffer support"
1087 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1090 tristate "Matrox acceleration"
1091 depends on FB && PCI
1092 select FB_CFB_FILLRECT
1093 select FB_CFB_COPYAREA
1094 select FB_CFB_IMAGEBLIT
1095 select FB_TILEBLITTING
1096 select FB_MACMODES if PPC_PMAC
1098 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1099 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1100 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1101 Matrox G400, G450 or G550 card in your box.
1103 To compile this driver as a module, choose M here: the
1104 module will be called matroxfb.
1106 You can pass several parameters to the driver at boot time or at
1107 module load time. The parameters look like "video=matroxfb:XXX", and
1108 are described in <file:Documentation/fb/matroxfb.txt>.
1110 config FB_MATROX_MILLENIUM
1111 bool "Millennium I/II support"
1112 depends on FB_MATROX
1114 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1115 video card. If you select "Advanced lowlevel driver options" below,
1116 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1117 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1118 also use font widths different from 8.
1120 config FB_MATROX_MYSTIQUE
1121 bool "Mystique support"
1122 depends on FB_MATROX
1124 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1125 video card. If you select "Advanced lowlevel driver options" below,
1126 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1127 packed pixel and 32 bpp packed pixel. You can also use font widths
1131 bool "G100/G200/G400/G450/G550 support"
1132 depends on FB_MATROX
1134 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1135 video card. If you select "Advanced lowlevel driver options", you
1136 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1137 pixel and 32 bpp packed pixel. You can also use font widths
1140 If you need support for G400 secondary head, you must say Y to
1141 "Matrox I2C support" and "G400 second head support" right below.
1142 G450/G550 secondary head and digital output are supported without
1145 The driver starts in monitor mode. You must use the matroxset tool
1146 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1147 swap primary and secondary head outputs, or to change output mode.
1148 Secondary head driver always start in 640x480 resolution and you
1149 must use fbset to change it.
1151 Do not forget that second head supports only 16 and 32 bpp
1152 packed pixels, so it is a good idea to compile them into the kernel
1153 too. You can use only some font widths, as the driver uses generic
1154 painting procedures (the secondary head does not use acceleration
1157 G450/G550 hardware can display TV picture only from secondary CRTC,
1158 and it performs no scaling, so picture must have 525 or 625 lines.
1160 config FB_MATROX_I2C
1161 tristate "Matrox I2C support"
1162 depends on FB_MATROX
1165 This drivers creates I2C buses which are needed for accessing the
1166 DDC (I2C) bus present on all Matroxes, an I2C bus which
1167 interconnects Matrox optional devices, like MGA-TVO on G200 and
1168 G400, and the secondary head DDC bus, present on G400 only.
1170 You can say Y or M here if you want to experiment with monitor
1171 detection code. You must say Y or M here if you want to use either
1172 second head of G400 or MGA-TVO on G200 or G400.
1174 If you compile it as module, it will create a module named
1177 config FB_MATROX_MAVEN
1178 tristate "G400 second head support"
1179 depends on FB_MATROX_G && FB_MATROX_I2C
1181 WARNING !!! This support does not work with G450 !!!
1183 Say Y or M here if you want to use a secondary head (meaning two
1184 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1185 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1186 secondary head output is blanked while you are in X. With XFree
1187 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1188 the fbdev driver on first head and the fbdev driver on second head.
1190 If you compile it as module, two modules are created,
1191 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1192 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1193 also load i2c-matroxfb to get it to run.
1195 The driver starts in monitor mode and you must use the matroxset
1197 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1198 PAL or NTSC or to swap primary and secondary head outputs.
1199 Secondary head driver also always start in 640x480 resolution, you
1200 must use fbset to change it.
1202 Also do not forget that second head supports only 16 and 32 bpp
1203 packed pixels, so it is a good idea to compile them into the kernel
1204 too. You can use only some font widths, as the driver uses generic
1205 painting procedures (the secondary head does not use acceleration
1209 tristate "ATI Radeon display support"
1210 depends on FB && PCI
1211 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1212 select FB_MODE_HELPERS
1213 select FB_CFB_FILLRECT
1214 select FB_CFB_COPYAREA
1215 select FB_CFB_IMAGEBLIT
1216 select FB_MACMODES if PPC
1218 Choose this option if you want to use an ATI Radeon graphics card as
1219 a framebuffer device. There are both PCI and AGP versions. You
1220 don't need to choose this to run the Radeon in plain VGA mode.
1222 There is a product page at
1223 http://products.amd.com/en-us/GraphicCardResult.aspx
1225 config FB_RADEON_I2C
1226 bool "DDC/I2C for ATI Radeon support"
1227 depends on FB_RADEON
1231 Say Y here if you want DDC/I2C support for your Radeon board.
1233 config FB_RADEON_BACKLIGHT
1234 bool "Support for backlight control"
1235 depends on FB_RADEON
1238 Say Y here if you want to control the backlight of your display.
1240 config FB_RADEON_DEBUG
1241 bool "Lots of debug output from Radeon driver"
1242 depends on FB_RADEON
1244 Say Y here if you want the Radeon driver to output all sorts
1245 of debugging information to provide to the maintainer when
1246 something goes wrong.
1249 tristate "ATI Rage128 display support"
1250 depends on FB && PCI
1251 select FB_CFB_FILLRECT
1252 select FB_CFB_COPYAREA
1253 select FB_CFB_IMAGEBLIT
1254 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1255 select FB_MACMODES if PPC_PMAC
1257 This driver supports graphics boards with the ATI Rage128 chips.
1258 Say Y if you have such a graphics board and read
1259 <file:Documentation/fb/aty128fb.txt>.
1261 To compile this driver as a module, choose M here: the
1262 module will be called aty128fb.
1264 config FB_ATY128_BACKLIGHT
1265 bool "Support for backlight control"
1266 depends on FB_ATY128
1269 Say Y here if you want to control the backlight of your display.
1272 tristate "ATI Mach64 display support" if PCI || ATARI
1273 depends on FB && !SPARC32
1274 select FB_CFB_FILLRECT
1275 select FB_CFB_COPYAREA
1276 select FB_CFB_IMAGEBLIT
1277 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1278 select FB_MACMODES if PPC
1280 This driver supports graphics boards with the ATI Mach64 chips.
1281 Say Y if you have such a graphics board.
1283 To compile this driver as a module, choose M here: the
1284 module will be called atyfb.
1287 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1288 depends on PCI && FB_ATY
1289 default y if SPARC64 && PCI
1291 Say Y here to support use of ATI's 64-bit Rage boards (or other
1292 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1293 framebuffer device. The ATI product support page for these boards
1294 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1296 config FB_ATY_GENERIC_LCD
1297 bool "Mach64 generic LCD support"
1298 depends on FB_ATY_CT
1300 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1301 Rage XC, or Rage XL chipset.
1304 bool "Mach64 GX support" if PCI
1308 Say Y here to support use of the ATI Mach64 Graphics Expression
1309 board (or other boards based on the Mach64 GX chipset) as a
1310 framebuffer device. The ATI product support page for these boards
1312 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1314 config FB_ATY_BACKLIGHT
1315 bool "Support for backlight control"
1319 Say Y here if you want to control the backlight of your display.
1322 tristate "S3 Trio/Virge support"
1323 depends on FB && PCI
1324 select FB_CFB_FILLRECT
1325 select FB_CFB_COPYAREA
1326 select FB_CFB_IMAGEBLIT
1327 select FB_TILEBLITTING
1330 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1332 Driver for graphics boards with S3 Trio / S3 Virge chip.
1335 bool "DDC for S3 support"
1340 Say Y here if you want DDC support for your S3 graphics card.
1343 tristate "S3 Savage support"
1344 depends on FB && PCI
1345 select FB_MODE_HELPERS
1346 select FB_CFB_FILLRECT
1347 select FB_CFB_COPYAREA
1348 select FB_CFB_IMAGEBLIT
1351 This driver supports notebooks and computers with S3 Savage PCI/AGP
1354 Say Y if you have such a graphics card.
1356 To compile this driver as a module, choose M here; the module
1357 will be called savagefb.
1359 config FB_SAVAGE_I2C
1360 bool "Enable DDC2 Support"
1361 depends on FB_SAVAGE
1364 This enables I2C support for S3 Savage Chipsets. This is used
1365 only for getting EDID information from the attached display
1366 allowing for robust video mode handling and switching.
1368 Because fbdev-2.6 requires that drivers must be able to
1369 independently validate video mode parameters, you should say Y
1372 config FB_SAVAGE_ACCEL
1373 bool "Enable Console Acceleration"
1374 depends on FB_SAVAGE
1376 This option will compile in console acceleration support. If
1377 the resulting framebuffer console has bothersome glitches, then
1381 tristate "SiS/XGI display support"
1382 depends on FB && PCI
1383 select FB_CFB_FILLRECT
1384 select FB_CFB_COPYAREA
1385 select FB_CFB_IMAGEBLIT
1386 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1387 select FB_SIS_300 if !FB_SIS_315
1389 This is the frame buffer device driver for the SiS 300, 315, 330
1390 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1391 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1393 To compile this driver as a module, choose M here; the module
1394 will be called sisfb.
1397 bool "SiS 300 series support"
1400 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1403 bool "SiS 315/330/340 series and XGI support"
1406 Say Y here to support use of the SiS 315, 330 and 340 series
1407 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1408 as XGI V3XT, V5, V8 and Z7.
1411 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1412 depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST)
1413 select FB_CFB_FILLRECT
1414 select FB_CFB_COPYAREA
1415 select FB_CFB_IMAGEBLIT
1418 This is the frame buffer device driver for Graphics chips of VIA
1419 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1420 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1422 Say Y if you have a VIA UniChrome graphics board.
1424 To compile this driver as a module, choose M here: the
1425 module will be called viafb.
1429 config FB_VIA_DIRECT_PROCFS
1430 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1432 Allow direct hardware access to some output registers via procfs.
1433 This is dangerous but may provide the only chance to get the
1434 correct output device configuration.
1435 Its use is strongly discouraged.
1437 config FB_VIA_X_COMPATIBILITY
1438 bool "X server compatibility"
1440 This option reduces the functionality (power saving, ...) of the
1441 framebuffer to avoid negative impact on the OpenChrome X server.
1442 If you use any X server other than fbdev you should enable this
1443 otherwise it should be safe to disable it and allow using all
1449 tristate "NeoMagic display support"
1450 depends on FB && PCI
1451 select FB_MODE_HELPERS
1452 select FB_CFB_FILLRECT
1453 select FB_CFB_COPYAREA
1454 select FB_CFB_IMAGEBLIT
1457 This driver supports notebooks with NeoMagic PCI chips.
1458 Say Y if you have such a graphics card.
1460 To compile this driver as a module, choose M here: the
1461 module will be called neofb.
1464 tristate "IMG Kyro support"
1465 depends on FB && PCI
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1470 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1473 To compile this driver as a module, choose M here: the
1474 module will be called kyrofb.
1477 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1478 depends on FB && PCI
1479 select FB_CFB_IMAGEBLIT
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1482 select FB_MODE_HELPERS
1484 This driver supports graphics boards with the 3Dfx Banshee,
1485 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1486 such a graphics board.
1488 To compile this driver as a module, choose M here: the
1489 module will be called tdfxfb.
1491 config FB_3DFX_ACCEL
1492 bool "3Dfx Acceleration functions"
1495 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1496 device driver with acceleration functions.
1499 bool "Enable DDC/I2C support"
1504 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1507 tristate "3Dfx Voodoo Graphics (sst1) support"
1508 depends on FB && PCI
1509 select FB_CFB_FILLRECT
1510 select FB_CFB_COPYAREA
1511 select FB_CFB_IMAGEBLIT
1513 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1514 Voodoo2 (cvg) based graphics card.
1516 To compile this driver as a module, choose M here: the
1517 module will be called sstfb.
1519 WARNING: Do not use any application that uses the 3D engine
1520 (namely glide) while using this driver.
1521 Please read the <file:Documentation/fb/sstfb.txt> for supported
1522 options and other important info support.
1525 tristate "VIA VT8623 support"
1526 depends on FB && PCI
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1529 select FB_CFB_IMAGEBLIT
1530 select FB_TILEBLITTING
1533 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1535 Driver for CastleRock integrated graphics core in the
1536 VIA VT8623 [Apollo CLE266] chipset.
1539 tristate "Trident/CyberXXX/CyberBlade support"
1540 depends on FB && PCI
1541 select FB_CFB_FILLRECT
1542 select FB_CFB_COPYAREA
1543 select FB_CFB_IMAGEBLIT
1545 select FB_MODE_HELPERS
1547 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1548 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1550 There are also integrated versions of these chips called CyberXXXX,
1551 CyberImage or CyberBlade. These chips are mostly found in laptops
1552 but also on some motherboards including early VIA EPIA motherboards.
1553 For more information, read <file:Documentation/fb/tridentfb.txt>
1555 Say Y if you have such a graphics board.
1557 To compile this driver as a module, choose M here: the
1558 module will be called tridentfb.
1561 tristate "ARK 2000PV support"
1562 depends on FB && PCI
1563 select FB_CFB_FILLRECT
1564 select FB_CFB_COPYAREA
1565 select FB_CFB_IMAGEBLIT
1566 select FB_TILEBLITTING
1569 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1571 Driver for PCI graphics boards with ARK 2000PV chip
1572 and ICS 5342 RAMDAC.
1575 tristate "Permedia3 support"
1576 depends on FB && PCI
1577 select FB_CFB_FILLRECT
1578 select FB_CFB_COPYAREA
1579 select FB_CFB_IMAGEBLIT
1581 This is the frame buffer device driver for the 3DLabs Permedia3
1582 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1583 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1584 and maybe other boards.
1587 tristate "Fujitsu carmine frame buffer support"
1588 depends on FB && PCI
1589 select FB_CFB_FILLRECT
1590 select FB_CFB_COPYAREA
1591 select FB_CFB_IMAGEBLIT
1593 This is the frame buffer device driver for the Fujitsu Carmine chip.
1594 The driver provides two independent frame buffer devices.
1597 depends on FB_CARMINE
1598 prompt "DRAM timing"
1599 default FB_CARMINE_DRAM_EVAL
1601 config FB_CARMINE_DRAM_EVAL
1602 bool "Eval board timings"
1604 Use timings which work on the eval card.
1606 config CARMINE_DRAM_CUSTOM
1607 bool "Custom board timings"
1609 Use custom board timings.
1613 bool "Au1100 LCD Driver"
1614 depends on (FB = y) && MIPS_ALCHEMY
1615 select FB_CFB_FILLRECT
1616 select FB_CFB_COPYAREA
1617 select FB_CFB_IMAGEBLIT
1619 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1620 various panels and CRTs by passing in kernel cmd line option
1621 au1100fb:panel=<name>.
1624 bool "Au1200/Au1300 LCD Driver"
1625 depends on (FB = y) && MIPS_ALCHEMY
1626 select FB_SYS_FILLRECT
1627 select FB_SYS_COPYAREA
1628 select FB_SYS_IMAGEBLIT
1631 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1632 It can drive various panels and CRTs by passing in kernel cmd line
1633 option au1200fb:panel=<name>.
1636 bool "VIA VT8500 framebuffer support"
1637 depends on (FB = y) && ARM && ARCH_VT8500
1638 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1639 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1640 select FB_SYS_IMAGEBLIT
1641 select FB_MODE_HELPERS
1642 select VIDEOMODE_HELPERS
1644 This is the framebuffer driver for VIA VT8500 integrated LCD
1648 bool "Wondermedia WM8xxx-series frame buffer support"
1649 depends on (FB = y) && ARM && ARCH_VT8500
1650 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1651 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1652 select FB_SYS_IMAGEBLIT
1653 select FB_MODE_HELPERS
1654 select VIDEOMODE_HELPERS
1656 This is the framebuffer driver for WonderMedia WM8xxx-series
1657 integrated LCD controller. This driver covers the WM8505, WM8650
1660 config FB_WMT_GE_ROPS
1661 bool "VT8500/WM8xxx accelerated raster ops support"
1662 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1664 This adds support for accelerated raster operations on the
1665 VIA VT8500 and Wondermedia 85xx series SoCs.
1667 source "drivers/video/fbdev/geode/Kconfig"
1670 tristate "HD64461 Frame Buffer support"
1671 depends on FB && HD64461
1672 select FB_CFB_FILLRECT
1673 select FB_CFB_COPYAREA
1674 select FB_CFB_IMAGEBLIT
1676 This is the frame buffer device driver for the Hitachi HD64461 LCD
1680 tristate "PMAG-AA TURBOchannel framebuffer support"
1682 select FB_CFB_FILLRECT
1683 select FB_CFB_COPYAREA
1684 select FB_CFB_IMAGEBLIT
1686 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1687 used mainly in the MIPS-based DECstation series.
1690 tristate "PMAG-BA TURBOchannel framebuffer support"
1692 select FB_CFB_FILLRECT
1693 select FB_CFB_COPYAREA
1694 select FB_CFB_IMAGEBLIT
1696 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1697 used mainly in the MIPS-based DECstation series.
1700 tristate "PMAGB-B TURBOchannel framebuffer support"
1702 select FB_CFB_FILLRECT
1703 select FB_CFB_COPYAREA
1704 select FB_CFB_IMAGEBLIT
1706 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1707 in the MIPS-based DECstation series. The card is currently only
1708 supported in 1280x1024x8 mode.
1711 bool "Maxine (Personal DECstation) onboard framebuffer support"
1712 depends on (FB = y) && MACH_DECSTATION
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 Support for the onboard framebuffer (1024x768x8) in the Personal
1718 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1722 bool "G364 frame buffer support"
1723 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1728 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1729 Olivetti M700-10 systems.
1732 bool "Motorola 68328 native frame buffer support"
1733 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1734 select FB_CFB_FILLRECT
1735 select FB_CFB_COPYAREA
1736 select FB_CFB_IMAGEBLIT
1738 Say Y here if you want to support the built-in frame buffer of
1739 the Motorola 68328 CPU family.
1742 tristate "PXA168/910 LCD framebuffer support"
1743 depends on FB && (CPU_PXA168 || CPU_PXA910)
1744 select FB_CFB_FILLRECT
1745 select FB_CFB_COPYAREA
1746 select FB_CFB_IMAGEBLIT
1748 Frame buffer driver for the built-in LCD controller in the Marvell
1752 tristate "PXA LCD framebuffer support"
1753 depends on FB && ARCH_PXA
1754 select FB_CFB_FILLRECT
1755 select FB_CFB_COPYAREA
1756 select FB_CFB_IMAGEBLIT
1757 select VIDEOMODE_HELPERS if OF
1758 select FB_MODE_HELPERS if OF
1760 Frame buffer driver for the built-in LCD controller in the Intel
1763 This driver is also available as a module ( = code which can be
1764 inserted and removed from the running kernel whenever you want). The
1765 module will be called pxafb. If you want to compile it as a module,
1766 say M here and read <file:Documentation/kbuild/modules.txt>.
1770 config FB_PXA_OVERLAY
1771 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1772 depends on FB_PXA && (PXA27x || PXA3xx)
1774 config FB_PXA_SMARTPANEL
1775 bool "PXA Smartpanel LCD support"
1778 config FB_PXA_PARAMETERS
1779 bool "PXA LCD command line parameters"
1782 Enable the use of kernel command line or module parameters
1783 to configure the physical properties of the LCD panel when
1784 using the PXA LCD driver.
1786 This option allows you to override the panel parameters
1787 supplied by the platform in order to support multiple
1788 different models of flatpanel. If you will only be using a
1789 single model of flatpanel then you can safely leave this
1792 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1795 tristate "PXA3xx 2D graphics accelerator driver"
1798 Kernelspace driver for the 2D graphics controller unit (GCU)
1799 found on PXA3xx processors. There is a counterpart driver in the
1800 DirectFB suite, see http://www.directfb.org/
1802 If you compile this as a module, it will be called pxa3xx_gcu.
1805 tristate "2700G LCD framebuffer support"
1806 depends on FB && ARCH_PXA
1807 select FB_CFB_FILLRECT
1808 select FB_CFB_COPYAREA
1809 select FB_CFB_IMAGEBLIT
1811 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1815 bool "Enable debugging info via debugfs"
1816 depends on FB_MBX && DEBUG_FS
1818 Enable this if you want debugging information using the debug
1819 filesystem (debugfs)
1824 tristate "Freescale DIU framebuffer support"
1825 depends on FB && FSL_SOC
1826 select FB_MODE_HELPERS
1827 select FB_CFB_FILLRECT
1828 select FB_CFB_COPYAREA
1829 select FB_CFB_IMAGEBLIT
1830 select PPC_LIB_RHEAP
1832 Framebuffer driver for the Freescale SoC DIU
1835 tristate "W100 frame buffer support"
1836 depends on FB && ARCH_PXA
1837 select FB_CFB_FILLRECT
1838 select FB_CFB_COPYAREA
1839 select FB_CFB_IMAGEBLIT
1841 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1842 It can also drive the w3220 chip found on iPAQ hx4700.
1844 This driver is also available as a module ( = code which can be
1845 inserted and removed from the running kernel whenever you want). The
1846 module will be called w100fb. If you want to compile it as a module,
1847 say M here and read <file:Documentation/kbuild/modules.txt>.
1851 config FB_SH_MOBILE_LCDC
1852 tristate "SuperH Mobile LCDC framebuffer support"
1853 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
1854 select FB_SYS_FILLRECT
1855 select FB_SYS_COPYAREA
1856 select FB_SYS_IMAGEBLIT
1858 select FB_DEFERRED_IO
1861 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1864 tristate "Toshiba Mobile IO FrameBuffer support"
1865 depends on FB && (MFD_TMIO || COMPILE_TEST)
1866 select FB_CFB_FILLRECT
1867 select FB_CFB_COPYAREA
1868 select FB_CFB_IMAGEBLIT
1870 Frame buffer driver for the Toshiba Mobile IO integrated as found
1871 on the Sharp SL-6000 series
1873 This driver is also available as a module ( = code which can be
1874 inserted and removed from the running kernel whenever you want). The
1875 module will be called tmiofb. If you want to compile it as a module,
1876 say M here and read <file:Documentation/kbuild/modules.txt>.
1880 config FB_TMIO_ACCELL
1881 bool "tmiofb acceleration"
1886 tristate "Samsung S3C framebuffer support"
1887 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX)
1888 select FB_CFB_FILLRECT
1889 select FB_CFB_COPYAREA
1890 select FB_CFB_IMAGEBLIT
1892 Frame buffer driver for the built-in FB controller in the Samsung
1893 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1894 and the S3C64XX series such as the S3C6400 and S3C6410.
1896 These chips all have the same basic framebuffer design with the
1897 actual capabilities depending on the chip. For instance the S3C6400
1898 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1899 currently only have two.
1901 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1903 config FB_S3C_DEBUG_REGWRITE
1904 bool "Debug register writes"
1907 Show all register writes via pr_debug()
1910 tristate "S3C2410 LCD framebuffer support"
1911 depends on FB && ARCH_S3C24XX
1912 select FB_CFB_FILLRECT
1913 select FB_CFB_COPYAREA
1914 select FB_CFB_IMAGEBLIT
1916 Frame buffer driver for the built-in LCD controller in the Samsung
1919 This driver is also available as a module ( = code which can be
1920 inserted and removed from the running kernel whenever you want). The
1921 module will be called s3c2410fb. If you want to compile it as a module,
1922 say M here and read <file:Documentation/kbuild/modules.txt>.
1925 config FB_S3C2410_DEBUG
1926 bool "S3C2410 lcd debug messages"
1927 depends on FB_S3C2410
1929 Turn on debugging messages. Note that you can set/unset at run time
1933 tristate "NUC900 LCD framebuffer support"
1934 depends on FB && ARCH_W90X900
1935 select FB_CFB_FILLRECT
1936 select FB_CFB_COPYAREA
1937 select FB_CFB_IMAGEBLIT
1939 Frame buffer driver for the built-in LCD controller in the Nuvoton
1942 config GPM1040A0_320X240
1943 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
1944 depends on FB_NUC900
1947 tristate "Silicon Motion SM501 framebuffer support"
1948 depends on FB && MFD_SM501
1949 select FB_CFB_FILLRECT
1950 select FB_CFB_COPYAREA
1951 select FB_CFB_IMAGEBLIT
1953 Frame buffer driver for the CRT and LCD controllers in the Silicon
1956 This driver is also available as a module ( = code which can be
1957 inserted and removed from the running kernel whenever you want). The
1958 module will be called sm501fb. If you want to compile it as a module,
1959 say M here and read <file:Documentation/kbuild/modules.txt>.
1964 tristate "SMSC UFX6000/7000 USB Framebuffer support"
1965 depends on FB && USB
1966 select FB_MODE_HELPERS
1967 select FB_SYS_FILLRECT
1968 select FB_SYS_COPYAREA
1969 select FB_SYS_IMAGEBLIT
1971 select FB_DEFERRED_IO
1973 This is a kernel framebuffer driver for SMSC UFX USB devices.
1974 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1975 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1977 To compile as a module, choose M here: the module name is smscufx.
1980 tristate "Displaylink USB Framebuffer support"
1981 depends on FB && USB
1982 select FB_MODE_HELPERS
1983 select FB_SYS_FILLRECT
1984 select FB_SYS_COPYAREA
1985 select FB_SYS_IMAGEBLIT
1987 select FB_DEFERRED_IO
1989 This is a kernel framebuffer driver for DisplayLink USB devices.
1990 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1991 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1992 To compile as a module, choose M here: the module name is udlfb.
1994 config FB_IBM_GXT4500
1995 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
1997 select FB_CFB_FILLRECT
1998 select FB_CFB_COPYAREA
1999 select FB_CFB_IMAGEBLIT
2001 Say Y here to enable support for the IBM GXT4000P/6000P and
2002 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2003 found on some IBM System P (pSeries) machines. This driver
2004 doesn't use Geometry Engine GT1000. This driver also supports
2005 AGP Fire GL2/3/4 cards on x86.
2008 tristate "PS3 GPU framebuffer driver"
2009 depends on FB && PS3_PS3AV
2010 select FB_SYS_FILLRECT
2011 select FB_SYS_COPYAREA
2012 select FB_SYS_IMAGEBLIT
2015 Include support for the virtual frame buffer in the PS3 platform.
2017 config FB_PS3_DEFAULT_SIZE_M
2018 int "PS3 default frame buffer size (in MiB)"
2022 This is the default size (in MiB) of the virtual frame buffer in
2024 The default value can be overridden on the kernel command line
2025 using the "ps3fb" option (e.g. "ps3fb=9M");
2028 tristate "Xilinx frame buffer support"
2029 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
2030 select FB_CFB_FILLRECT
2031 select FB_CFB_COPYAREA
2032 select FB_CFB_IMAGEBLIT
2034 Include support for the Xilinx ML300/ML403 reference design
2035 framebuffer. ML300 carries a 640*480 LCD display on the board,
2036 ML403 uses a standard DB15 VGA connector.
2039 tristate "Goldfish Framebuffer"
2041 depends on GOLDFISH || COMPILE_TEST
2042 select FB_CFB_FILLRECT
2043 select FB_CFB_COPYAREA
2044 select FB_CFB_IMAGEBLIT
2046 Framebuffer driver for Goldfish Virtual Platform
2049 tristate "Cobalt server LCD frame buffer support"
2050 depends on FB && MIPS_COBALT
2053 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2054 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2055 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2056 select FB_CFB_FILLRECT
2057 select FB_CFB_COPYAREA
2058 select FB_CFB_IMAGEBLIT
2060 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2061 (D)STN/TFT LCD Controller.
2062 Supports display resolutions up to 1024x1024 pixel, grayscale and
2063 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2064 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2065 panels <= 320 pixel horizontal resolution.
2068 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2069 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2070 select FB_CFB_FILLRECT
2071 select FB_CFB_COPYAREA
2072 select FB_CFB_IMAGEBLIT
2073 select FB_CFB_REV_PIXELS_IN_BYTE
2074 select FB_MODE_HELPERS
2075 select VIDEOMODE_HELPERS
2077 This is the frame buffer device driver for the TI LCD controller
2078 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2082 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2084 select FB_SYS_FILLRECT
2085 select FB_SYS_COPYAREA
2086 select FB_SYS_IMAGEBLIT
2089 This is a `virtual' frame buffer device. It operates on a chunk of
2090 unswappable kernel memory instead of on the memory of a graphics
2091 board. This means you cannot see any output sent to this frame
2092 buffer device, while it does consume precious memory. The main use
2093 of this frame buffer device is testing and debugging the frame
2094 buffer subsystem. Do NOT enable it for normal systems! To protect
2095 the innocent, it has to be enabled explicitly at boot time using the
2096 kernel option `video=vfb:'.
2098 To compile this driver as a module, choose M here: the
2099 module will be called vfb. In order to load it, you must use
2100 the vfb_enable=1 option.
2104 config XEN_FBDEV_FRONTEND
2105 tristate "Xen virtual frame buffer support"
2106 depends on FB && XEN
2107 select FB_SYS_FILLRECT
2108 select FB_SYS_COPYAREA
2109 select FB_SYS_IMAGEBLIT
2111 select FB_DEFERRED_IO
2112 select XEN_XENBUS_FRONTEND
2115 This driver implements the front-end of the Xen virtual
2116 frame buffer driver. It communicates with a back-end
2120 tristate "E-Ink Metronome/8track controller support"
2122 select FB_SYS_FILLRECT
2123 select FB_SYS_COPYAREA
2124 select FB_SYS_IMAGEBLIT
2126 select FB_DEFERRED_IO
2128 This driver implements support for the E-Ink Metronome
2129 controller. The pre-release name for this device was 8track
2130 and could also have been called by some vendors as PVI-nnnn.
2133 tristate "Fujitsu MB862xx GDC support"
2135 depends on PCI || (OF && PPC)
2136 select FB_CFB_FILLRECT
2137 select FB_CFB_COPYAREA
2138 select FB_CFB_IMAGEBLIT
2140 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2143 prompt "GDC variant"
2144 depends on FB_MB862XX
2146 config FB_MB862XX_PCI_GDC
2147 bool "Carmine/Coral-P(A) GDC"
2150 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2151 PCI graphics controller devices.
2153 config FB_MB862XX_LIME
2155 depends on OF && PPC
2156 select FB_FOREIGN_ENDIAN
2157 select FB_LITTLE_ENDIAN
2159 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2163 config FB_MB862XX_I2C
2164 bool "Support I2C bus on MB862XX GDC"
2165 depends on FB_MB862XX && I2C
2166 depends on FB_MB862XX=m || I2C=y
2169 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2170 driver to support accessing I2C devices on controller's I2C bus.
2171 These are usually some video decoder chips.
2174 tristate "EP93XX frame buffer support"
2175 depends on FB && ARCH_EP93XX
2176 select FB_CFB_FILLRECT
2177 select FB_CFB_COPYAREA
2178 select FB_CFB_IMAGEBLIT
2180 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2181 This driver is also available as a module. The module will be called
2184 config FB_PRE_INIT_FB
2185 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2186 depends on FB && FB_MB862XX_LIME
2188 Select this option if display contents should be inherited as set by
2192 tristate "MX3 Framebuffer support"
2193 depends on FB && MX3_IPU
2194 select BACKLIGHT_CLASS_DEVICE
2195 select BACKLIGHT_LCD_SUPPORT
2196 select FB_CFB_FILLRECT
2197 select FB_CFB_COPYAREA
2198 select FB_CFB_IMAGEBLIT
2201 This is a framebuffer device for the i.MX31 LCD Controller. So
2202 far only synchronous displays are supported. If you plan to use
2203 an LCD display with your i.MX31 system, say Y here.
2205 config FB_BROADSHEET
2206 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2207 depends on FB && (ARCH_PXA || COMPILE_TEST)
2208 select FB_SYS_FILLRECT
2209 select FB_SYS_COPYAREA
2210 select FB_SYS_IMAGEBLIT
2212 select FB_DEFERRED_IO
2214 This driver implements support for the E-Ink Broadsheet
2215 controller. The release name for this device was Epson S1D13521
2216 and could also have been called by other names when coupled with
2220 tristate "JZ4740 LCD framebuffer support"
2221 depends on FB && MACH_JZ4740
2222 select FB_SYS_FILLRECT
2223 select FB_SYS_COPYAREA
2224 select FB_SYS_IMAGEBLIT
2226 Framebuffer support for the JZ4740 SoC.
2229 tristate "MXS LCD framebuffer support"
2230 depends on FB && (ARCH_MXS || ARCH_MXC)
2231 select FB_CFB_FILLRECT
2232 select FB_CFB_COPYAREA
2233 select FB_CFB_IMAGEBLIT
2234 select FB_MODE_HELPERS
2235 select VIDEOMODE_HELPERS
2237 Framebuffer support for the MXS SoC.
2239 config FB_PUV3_UNIGFX
2240 tristate "PKUnity v3 Unigfx framebuffer support"
2241 depends on FB && UNICORE32 && ARCH_PUV3
2242 select FB_SYS_FILLRECT
2243 select FB_SYS_COPYAREA
2244 select FB_SYS_IMAGEBLIT
2247 Choose this option if you want to use the Unigfx device as a
2248 framebuffer device. Without the support of PCI & AGP.
2251 tristate "Microsoft Hyper-V Synthetic Video support"
2252 depends on FB && HYPERV
2253 select FB_CFB_FILLRECT
2254 select FB_CFB_COPYAREA
2255 select FB_CFB_IMAGEBLIT
2257 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2260 bool "Simple framebuffer support"
2262 select FB_CFB_FILLRECT
2263 select FB_CFB_COPYAREA
2264 select FB_CFB_IMAGEBLIT
2266 Say Y if you want support for a simple frame-buffer.
2268 This driver assumes that the display hardware has been initialized
2269 before the kernel boots, and the kernel will simply render to the
2270 pre-allocated frame buffer surface.
2272 Configuration re: surface address, size, and format must be provided
2273 through device tree, or plain old platform data.
2276 tristate "Solomon SSD1307 framebuffer support"
2277 depends on FB && I2C
2279 depends on GPIOLIB || COMPILE_TEST
2281 select FB_SYS_FILLRECT
2282 select FB_SYS_COPYAREA
2283 select FB_SYS_IMAGEBLIT
2284 select FB_DEFERRED_IO
2288 This driver implements support for the Solomon SSD1307
2289 OLED controller over I2C.
2292 tristate "Silicon Motion SM712 framebuffer support"
2293 depends on FB && PCI
2294 select FB_CFB_FILLRECT
2295 select FB_CFB_COPYAREA
2296 select FB_CFB_IMAGEBLIT
2298 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2301 This driver is also available as a module. The module will be
2302 called sm712fb. If you want to compile it as a module, say M
2303 here and read <file:Documentation/kbuild/modules.txt>.
2305 source "drivers/video/fbdev/omap/Kconfig"
2306 source "drivers/video/fbdev/omap2/Kconfig"
2307 source "drivers/video/fbdev/mmp/Kconfig"