6 tristate "Support for frame buffer devices"
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
42 bool "Enable firmware EDID"
46 This enables access to the EDID transferred from the firmware.
47 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
48 transfers do not work for your driver and if you are using
49 nvidiafb, i810fb or savagefb.
51 In general, choosing Y for this option is safe. If you
52 experience extremely long delays while booting before you get
53 something on your display, try setting this to N. Matrox cards in
54 combination with certain motherboards and monitors are known to
55 suffer from this problem.
70 config FB_BOOT_VESA_SUPPORT
75 If true, at least one selected framebuffer driver can take advantage
76 of VESA video modes set at an early boot stage via the vga= parameter.
78 config FB_CFB_FILLRECT
83 Include the cfb_fillrect function for generic software rectangle
84 filling. This is used by drivers that don't provide their own
85 (accelerated) version.
87 config FB_CFB_COPYAREA
92 Include the cfb_copyarea function for generic software area copying.
93 This is used by drivers that don't provide their own (accelerated)
96 config FB_CFB_IMAGEBLIT
101 Include the cfb_imageblit function for generic software image
102 blitting. This is used by drivers that don't provide their own
103 (accelerated) version.
105 config FB_CFB_REV_PIXELS_IN_BYTE
110 Allow generic frame-buffer functions to work on displays with 1, 2
111 and 4 bits per pixel depths which has opposite order of pixels in
112 byte order to bytes in long order.
114 config FB_SYS_FILLRECT
119 Include the sys_fillrect function for generic software rectangle
120 filling. This is used by drivers that don't provide their own
121 (accelerated) version and the framebuffer is in system RAM.
123 config FB_SYS_COPYAREA
128 Include the sys_copyarea function for generic software area copying.
129 This is used by drivers that don't provide their own (accelerated)
130 version and the framebuffer is in system RAM.
132 config FB_SYS_IMAGEBLIT
137 Include the sys_imageblit function for generic software image
138 blitting. This is used by drivers that don't provide their own
139 (accelerated) version and the framebuffer is in system RAM.
141 config FB_PROVIDE_GET_FB_UNMAPPED_AREA
146 Allow generic frame-buffer to provide get_fb_unmapped_area
149 menuconfig FB_FOREIGN_ENDIAN
150 bool "Framebuffer foreign endianness support"
153 This menu will let you enable support for the framebuffers with
154 non-native endianness (e.g. Little-Endian framebuffer on a
155 Big-Endian machine). Most probably you don't have such hardware,
156 so it's safe to say "n" here.
159 prompt "Choice endianness support"
160 depends on FB_FOREIGN_ENDIAN
162 config FB_BOTH_ENDIAN
163 bool "Support for Big- and Little-Endian framebuffers"
166 bool "Support for Big-Endian framebuffers only"
168 config FB_LITTLE_ENDIAN
169 bool "Support for Little-Endian framebuffers only"
178 config FB_DEFERRED_IO
185 depends on FB_DEFERRED_IO
192 Common utility functions useful to fbdev drivers of VGA-based
203 select BACKLIGHT_LCD_SUPPORT
204 select BACKLIGHT_CLASS_DEVICE
207 config FB_MODE_HELPERS
208 bool "Enable Video Mode Handling Helpers"
212 This enables functions for handling video modes using the
213 Generalized Timing Formula and the EDID parser. A few drivers rely
214 on this feature such as the radeonfb, rivafb, and the i810fb. If
215 your driver does not take advantage of this feature, choosing Y will
216 just increase the kernel size by about 5K.
218 config FB_TILEBLITTING
219 bool "Enable Tile Blitting Support"
223 This enables tile blitting. Tile blitting is a drawing technique
224 where the screen is divided into rectangular sections (tiles), whereas
225 the standard blitting divides the screen into pixels. Because the
226 default drawing element is a tile, drawing functions will be passed
227 parameters in terms of number of tiles instead of number of pixels.
228 For example, to draw a single character, instead of using bitmaps,
229 an index to an array of bitmaps will be used. To clear or move a
230 rectangular section of a screen, the rectangle will be described in
231 terms of number of tiles in the x- and y-axis.
233 This is particularly important to one driver, matroxfb. If
236 comment "Frame buffer hardware drivers"
240 tristate "BCM2708 framebuffer support"
241 depends on FB && RASPBERRYPI_FIRMWARE
242 select FB_CFB_FILLRECT
243 select FB_CFB_COPYAREA
244 select FB_CFB_IMAGEBLIT
246 This framebuffer device driver is for the BCM2708 framebuffer.
248 If you want to compile this as a module (=code which can be
249 inserted into and removed from the running kernel), say M
250 here and read <file:Documentation/kbuild/modules.txt>. The module
251 will be called bcm2708_fb.
254 tristate "Aeroflex Gaisler framebuffer support"
255 depends on FB && SPARC
256 select FB_CFB_FILLRECT
257 select FB_CFB_COPYAREA
258 select FB_CFB_IMAGEBLIT
260 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
263 tristate "Cirrus Logic support"
264 depends on FB && (ZORRO || PCI)
265 select FB_CFB_FILLRECT
266 select FB_CFB_COPYAREA
267 select FB_CFB_IMAGEBLIT
269 This enables support for Cirrus Logic GD542x/543x based boards on
270 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
272 If you have a PCI-based system, this enables support for these
273 chips: GD-543x, GD-544x, GD-5480.
275 Please read the file <file:Documentation/fb/cirrusfb.txt>.
277 Say N unless you have such a graphics board or plan to get one
278 before you next recompile the kernel.
281 tristate "Permedia2 support"
282 depends on FB && ((AMIGA && BROKEN) || PCI)
283 select FB_CFB_FILLRECT
284 select FB_CFB_COPYAREA
285 select FB_CFB_IMAGEBLIT
287 This is the frame buffer device driver for cards based on
288 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
289 The driver was tested on the following cards:
290 Diamond FireGL 1000 PRO AGP
291 ELSA Gloria Synergy PCI
292 Appian Jeronimo PRO (both heads) PCI
293 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
294 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
295 ASK Graphic Blaster Exxtreme AGP
297 To compile this driver as a module, choose M here: the
298 module will be called pm2fb.
300 config FB_PM2_FIFO_DISCONNECT
301 bool "enable FIFO disconnect feature"
302 depends on FB_PM2 && PCI
304 Support the Permedia2 FIFO disconnect feature.
307 tristate "ARM PrimeCell PL110 support"
308 depends on ARM || ARM64 || COMPILE_TEST
309 depends on FB && ARM_AMBA && HAS_IOMEM
310 select FB_CFB_FILLRECT
311 select FB_CFB_COPYAREA
312 select FB_CFB_IMAGEBLIT
313 select FB_MODE_HELPERS if OF
314 select VIDEOMODE_HELPERS if OF
315 select BACKLIGHT_LCD_SUPPORT if OF
316 select BACKLIGHT_CLASS_DEVICE if OF
318 This framebuffer device driver is for the ARM PrimeCell PL110
319 Colour LCD controller. ARM PrimeCells provide the building
320 blocks for System on a Chip devices.
322 If you want to compile this as a module (=code which can be
323 inserted into and removed from the running kernel), say M
324 here and read <file:Documentation/kbuild/modules.txt>. The module
325 will be called amba-clcd.
327 # Helper logic selected only by the ARM Versatile platform family.
328 config PLAT_VERSATILE_CLCD
329 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_INTEGRATOR
331 depends on FB_ARMCLCD && FB=y
336 bool "Acorn VIDC support"
337 depends on (FB = y) && ARM && ARCH_ACORN
338 select FB_CFB_FILLRECT
339 select FB_CFB_COPYAREA
340 select FB_CFB_IMAGEBLIT
342 This is the frame buffer device driver for the Acorn VIDC graphics
343 hardware found in Acorn RISC PCs and other ARM-based machines. If
346 config FB_CLPS711X_OLD
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
353 tristate "CLPS711X LCD support"
354 depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
355 select FB_CLPS711X_OLD if ARCH_CLPS711X && !ARCH_MULTIPLATFORM
356 select BACKLIGHT_LCD_SUPPORT
357 select FB_MODE_HELPERS
358 select FB_SYS_FILLRECT
359 select FB_SYS_COPYAREA
360 select FB_SYS_IMAGEBLIT
361 select LCD_CLASS_DEVICE
362 select VIDEOMODE_HELPERS
364 Say Y to enable the Framebuffer driver for the Cirrus Logic
368 bool "SA-1100 LCD support"
369 depends on (FB = y) && ARM && ARCH_SA1100
370 select FB_CFB_FILLRECT
371 select FB_CFB_COPYAREA
372 select FB_CFB_IMAGEBLIT
374 This is a framebuffer device for the SA-1100 LCD Controller.
375 See <http://www.linux-fbdev.org/> for information on framebuffer
378 If you plan to use the LCD display with your SA-1100 system, say
382 tristate "Freescale i.MX1/21/25/27 LCD support"
383 depends on FB && ARCH_MXC
384 select BACKLIGHT_LCD_SUPPORT
385 select LCD_CLASS_DEVICE
386 select FB_CFB_FILLRECT
387 select FB_CFB_COPYAREA
388 select FB_CFB_IMAGEBLIT
389 select FB_MODE_HELPERS
390 select VIDEOMODE_HELPERS
393 tristate "CyberPro 2000/2010/5000 support"
394 depends on FB && PCI && (BROKEN || !SPARC64)
395 select FB_CFB_FILLRECT
396 select FB_CFB_COPYAREA
397 select FB_CFB_IMAGEBLIT
399 This enables support for the Integraphics CyberPro 20x0 and 5000
400 VGA chips used in the Rebel.com Netwinder and other machines.
401 Say Y if you have a NetWinder or a graphics card containing this
402 device, otherwise say N.
404 config FB_CYBER2000_DDC
405 bool "DDC for CyberPro support"
406 depends on FB_CYBER2000
410 Say Y here if you want DDC support for your CyberPro graphics
411 card. This is only I2C bus support, driver does not use EDID.
413 config FB_CYBER2000_I2C
414 bool "CyberPro 2000/2010/5000 I2C support"
415 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
416 depends on I2C=y || FB_CYBER2000=m
419 Enable support for the I2C video decoder interface on the
420 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
421 on the Netwinder machines for the SAA7111 video capture.
425 depends on (FB = y) && APOLLO
427 select FB_CFB_FILLRECT
428 select FB_CFB_IMAGEBLIT
432 depends on (FB = y) && Q40
434 select FB_CFB_FILLRECT
435 select FB_CFB_COPYAREA
436 select FB_CFB_IMAGEBLIT
439 tristate "Amiga native chipset support"
440 depends on FB && AMIGA
442 This is the frame buffer device driver for the builtin graphics
443 chipset found in Amigas.
445 To compile this driver as a module, choose M here: the
446 module will be called amifb.
449 bool "Amiga OCS chipset support"
452 This enables support for the original Agnus and Denise video chips,
453 found in the Amiga 1000 and most A500's and A2000's. If you intend
454 to run Linux on any of these systems, say Y; otherwise say N.
457 bool "Amiga ECS chipset support"
460 This enables support for the Enhanced Chip Set, found in later
461 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
462 you intend to run Linux on any of these systems, say Y; otherwise
466 bool "Amiga AGA chipset support"
469 This enables support for the Advanced Graphics Architecture (also
470 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
471 and CD32. If you intend to run Linux on any of these systems, say Y;
475 bool "Amiga FrameMaster II/Rainbow II support"
476 depends on (FB = y) && ZORRO
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
481 This is the frame buffer device driver for the Amiga FrameMaster
482 card from BSC (exhibited 1992 but not shipped as a CBM product).
485 tristate "Arc Monochrome LCD board support"
487 select FB_SYS_FILLRECT
488 select FB_SYS_COPYAREA
489 select FB_SYS_IMAGEBLIT
492 This enables support for the Arc Monochrome LCD board. The board
493 is based on the KS-108 lcd controller and is typically a matrix
494 of 2*n chips. This driver was tested with a 128x64 panel. This
495 driver supports it for use with x86 SBCs through a 16 bit GPIO
496 interface (8 bit data, 8 bit control). If you anticipate using
497 this driver, say Y or M; otherwise say N. You must specify the
498 GPIO IO address to be used for setting control and data.
501 bool "Atari native chipset support"
502 depends on (FB = y) && ATARI
503 select FB_CFB_FILLRECT
504 select FB_CFB_COPYAREA
505 select FB_CFB_IMAGEBLIT
507 This is the frame buffer device driver for the builtin graphics
508 chipset found in Ataris.
511 bool "Open Firmware frame buffer device support"
512 depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
518 Say Y if you want support with Open Firmware for your graphics
522 bool "Apple \"control\" display support"
523 depends on (FB = y) && PPC_PMAC && PPC32
524 select FB_CFB_FILLRECT
525 select FB_CFB_COPYAREA
526 select FB_CFB_IMAGEBLIT
529 This driver supports a frame buffer for the graphics adapter in the
530 Power Macintosh 7300 and others.
533 bool "Apple \"platinum\" display support"
534 depends on (FB = y) && PPC_PMAC && PPC32
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
540 This driver supports a frame buffer for the "platinum" graphics
541 adapter in some Power Macintoshes.
544 bool "Apple \"valkyrie\" display support"
545 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
546 select FB_CFB_FILLRECT
547 select FB_CFB_COPYAREA
548 select FB_CFB_IMAGEBLIT
551 This driver supports a frame buffer for the "valkyrie" graphics
552 adapter in some Power Macintoshes.
555 bool "Chips 65550 display support"
556 depends on (FB = y) && PPC32 && PCI
557 select FB_CFB_FILLRECT
558 select FB_CFB_COPYAREA
559 select FB_CFB_IMAGEBLIT
561 This is the frame buffer device driver for the Chips & Technologies
562 65550 graphics chip in PowerBooks.
565 bool "Asiliant (Chips) 69000 display support"
566 depends on (FB = y) && PCI
567 select FB_CFB_FILLRECT
568 select FB_CFB_COPYAREA
569 select FB_CFB_IMAGEBLIT
571 This is the frame buffer device driver for the Asiliant 69030 chipset
574 bool "IMS Twin Turbo display support"
575 depends on (FB = y) && PCI
576 select FB_CFB_IMAGEBLIT
577 select FB_MACMODES if PPC
579 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
580 many Macintosh and compatible computers.
583 tristate "VGA 16-color graphics support"
584 depends on FB && (X86 || PPC)
585 select FB_CFB_FILLRECT
586 select FB_CFB_COPYAREA
587 select FB_CFB_IMAGEBLIT
589 select FONT_8x16 if FRAMEBUFFER_CONSOLE
591 This is the frame buffer device driver for VGA 16 color graphic
592 cards. Say Y if you have such a card.
594 To compile this driver as a module, choose M here: the
595 module will be called vga16fb.
597 config FB_BF54X_LQ043
598 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
599 depends on FB && (BF54x) && !BF542
600 select FB_CFB_FILLRECT
601 select FB_CFB_COPYAREA
602 select FB_CFB_IMAGEBLIT
604 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
606 config FB_BFIN_T350MCQB
607 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
608 depends on FB && BLACKFIN
610 select FB_CFB_FILLRECT
611 select FB_CFB_COPYAREA
612 select FB_CFB_IMAGEBLIT
614 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
615 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
616 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
618 config FB_BFIN_LQ035Q1
619 tristate "SHARP LQ035Q1DH02 TFT LCD"
620 depends on FB && BLACKFIN && SPI
621 select FB_CFB_FILLRECT
622 select FB_CFB_COPYAREA
623 select FB_CFB_IMAGEBLIT
626 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
627 the Blackfin Landscape LCD EZ-Extender Card.
628 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
629 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
631 To compile this driver as a module, choose M here: the
632 module will be called bfin-lq035q1-fb.
634 config FB_BF537_LQ035
635 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
636 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
637 select FB_CFB_FILLRECT
638 select FB_CFB_COPYAREA
639 select FB_CFB_IMAGEBLIT
642 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
645 To compile this driver as a module, choose M here: the
646 module will be called bf537-lq035.
649 tristate "Blackfin ADV7393 Video encoder"
650 depends on FB && BLACKFIN
652 select FB_CFB_FILLRECT
653 select FB_CFB_COPYAREA
654 select FB_CFB_IMAGEBLIT
656 This is the framebuffer device for a ADV7393 video encoder
657 attached to a Blackfin on the PPI port.
658 If your Blackfin board has a ADV7393 select Y.
660 To compile this driver as a module, choose M here: the
661 module will be called bfin_adv7393fb.
664 prompt "Video mode support"
665 depends on FB_BFIN_7393
675 bool 'NTSC 640x480 (Experimental)'
678 bool 'PAL 640x480 (Experimental)'
681 bool 'NTSC 720x480 YCbCR input'
684 bool 'PAL 720x576 YCbCR input'
689 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
690 depends on (FB_BFIN_7393)
691 default ADV7393_1XMEM
701 tristate "HP STI frame buffer device support"
702 depends on FB && PARISC
703 select FB_CFB_FILLRECT
704 select FB_CFB_COPYAREA
705 select FB_CFB_IMAGEBLIT
708 STI refers to the HP "Standard Text Interface" which is a set of
709 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
710 Enabling this option will implement the linux framebuffer device
711 using calls to the STI BIOS routines for initialisation.
713 If you enable this option, you will get a planar framebuffer device
714 /dev/fb which will work on the most common HP graphic cards of the
715 NGLE family, including the artist chips (in the 7xx and Bxxx series),
716 HCRX, HCRX24, CRX, CRX24 and VisEG series.
718 It is safe to enable this option, so you should probably say "Y".
721 bool "Generic Macintosh display support"
722 depends on (FB = y) && MAC
723 select FB_CFB_FILLRECT
724 select FB_CFB_COPYAREA
725 select FB_CFB_IMAGEBLIT
730 depends on (FB = y) && DIO
731 select FB_CFB_IMAGEBLIT
735 tristate "TGA/SFB+ framebuffer support"
736 depends on FB && (ALPHA || TC)
737 select FB_CFB_FILLRECT
738 select FB_CFB_COPYAREA
739 select FB_CFB_IMAGEBLIT
742 This is the frame buffer device driver for generic TGA and SFB+
743 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
744 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
745 TURBOchannel cards, also known as PMAGD-A, -B and -C.
747 Due to hardware limitations ZLX-E2 and E3 cards are not supported
748 for DECstation 5000/200 systems. Additionally due to firmware
749 limitations these cards may cause troubles with booting DECstation
750 5000/240 and /260 systems, but are fully supported under Linux if
751 you manage to get it going. ;-)
753 Say Y if you have one of those.
756 tristate "Userspace VESA VGA graphics support"
757 depends on FB && CONNECTOR
758 select FB_CFB_FILLRECT
759 select FB_CFB_COPYAREA
760 select FB_CFB_IMAGEBLIT
761 select FB_MODE_HELPERS
763 This is the frame buffer driver for generic VBE 2.0 compliant
764 graphic cards. It can also take advantage of VBE 3.0 features,
765 such as refresh rate adjustment.
767 This driver generally provides more features than vesafb but
768 requires a userspace helper application called 'v86d'. See
769 <file:Documentation/fb/uvesafb.txt> for more information.
774 bool "VESA VGA graphics support"
775 depends on (FB = y) && X86
776 select FB_CFB_FILLRECT
777 select FB_CFB_COPYAREA
778 select FB_CFB_IMAGEBLIT
779 select FB_BOOT_VESA_SUPPORT
781 This is the frame buffer device driver for generic VESA 2.0
782 compliant graphic cards. The older VESA 1.2 cards are not supported.
783 You will get a boot time penguin logo at no additional cost. Please
784 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
787 bool "EFI-based Framebuffer Support"
788 depends on (FB = y) && !IA64 && EFI
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
793 This is the EFI frame buffer device driver. If the firmware on
794 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
795 using the EFI framebuffer as your console.
798 tristate "N411 Apollo/Hecuba devkit support"
799 depends on FB && X86 && MMU
800 select FB_SYS_FILLRECT
801 select FB_SYS_COPYAREA
802 select FB_SYS_IMAGEBLIT
804 select FB_DEFERRED_IO
807 This enables support for the Apollo display controller in its
808 Hecuba form using the n411 devkit.
811 tristate "Hercules mono graphics support"
814 Say Y here if you have a Hercules mono graphics card.
816 To compile this driver as a module, choose M here: the
817 module will be called hgafb.
819 As this card technology is at least 25 years old,
820 most people will answer N here.
823 bool "SGI Graphics Backend frame buffer support"
824 depends on (FB = y) && SGI_IP32
825 select FB_CFB_FILLRECT
826 select FB_CFB_COPYAREA
827 select FB_CFB_IMAGEBLIT
829 This is the frame buffer device driver for SGI Graphics Backend.
830 This chip is used in SGI O2 and Visual Workstation 320/540.
833 int "Video memory size in MB"
837 This is the amount of memory reserved for the framebuffer,
838 which can be any value between 1MB and 8MB.
841 bool "SBUS and UPA framebuffers"
842 depends on (FB = y) && SPARC
844 Say Y if you want support for SBUS or UPA based frame buffer device.
848 depends on (FB = y) && (SPARC && FB_SBUS)
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
853 This is the frame buffer device driver for the BWtwo frame buffer.
856 bool "CGthree support"
857 depends on (FB = y) && (SPARC && FB_SBUS)
858 select FB_CFB_FILLRECT
859 select FB_CFB_COPYAREA
860 select FB_CFB_IMAGEBLIT
862 This is the frame buffer device driver for the CGthree frame buffer.
865 bool "CGsix (GX,TurboGX) support"
866 depends on (FB = y) && (SPARC && FB_SBUS)
867 select FB_CFB_COPYAREA
868 select FB_CFB_IMAGEBLIT
870 This is the frame buffer device driver for the CGsix (GX, TurboGX)
874 bool "Creator/Creator3D/Elite3D support"
875 depends on FB_SBUS && SPARC64
876 select FB_CFB_COPYAREA
877 select FB_CFB_IMAGEBLIT
879 This is the frame buffer device driver for the Creator, Creator3D,
880 and Elite3D graphics boards.
883 bool "TCX (SS4/SS5 only) support"
885 select FB_CFB_FILLRECT
886 select FB_CFB_COPYAREA
887 select FB_CFB_IMAGEBLIT
889 This is the frame buffer device driver for the TCX 24/8bit frame
893 bool "CGfourteen (SX) support"
895 select FB_CFB_FILLRECT
896 select FB_CFB_COPYAREA
897 select FB_CFB_IMAGEBLIT
899 This is the frame buffer device driver for the CGfourteen frame
900 buffer on Desktop SPARCsystems with the SX graphics option.
903 bool "P9100 (Sparcbook 3 only) support"
905 select FB_CFB_FILLRECT
906 select FB_CFB_COPYAREA
907 select FB_CFB_IMAGEBLIT
909 This is the frame buffer device driver for the P9100 card
910 supported on Sparcbook 3 machines.
913 bool "Leo (ZX) support"
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the frame buffer device driver for the SBUS-based Sun ZX
920 (leo) frame buffer cards.
923 bool "IGA 168x display support"
924 depends on (FB = y) && SPARC32
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 This is the framebuffer device for the INTERGRAPHICS 1680 and
930 successor frame buffer cards.
933 bool "Sun XVR-500 3DLABS Wildcat support"
934 depends on (FB = y) && PCI && SPARC64
935 select FB_CFB_FILLRECT
936 select FB_CFB_COPYAREA
937 select FB_CFB_IMAGEBLIT
939 This is the framebuffer device for the Sun XVR-500 and similar
940 graphics cards based upon the 3DLABS Wildcat chipset. The driver
941 only works on sparc64 systems where the system firmware has
942 mostly initialized the card already. It is treated as a
943 completely dumb framebuffer device.
946 bool "Sun XVR-2500 3DLABS Wildcat support"
947 depends on (FB = y) && PCI && SPARC64
948 select FB_CFB_FILLRECT
949 select FB_CFB_COPYAREA
950 select FB_CFB_IMAGEBLIT
952 This is the framebuffer device for the Sun XVR-2500 and similar
953 graphics cards based upon the 3DLABS Wildcat chipset. The driver
954 only works on sparc64 systems where the system firmware has
955 mostly initialized the card already. It is treated as a
956 completely dumb framebuffer device.
959 bool "Sun XVR-1000 support"
960 depends on (FB = y) && SPARC64
961 select FB_CFB_FILLRECT
962 select FB_CFB_COPYAREA
963 select FB_CFB_IMAGEBLIT
965 This is the framebuffer device for the Sun XVR-1000 and similar
966 graphics cards. The driver only works on sparc64 systems where
967 the system firmware has mostly initialized the card already. It
968 is treated as a completely dumb framebuffer device.
971 tristate "NEC PowerVR 2 display support"
972 depends on FB && SH_DREAMCAST
973 select FB_CFB_FILLRECT
974 select FB_CFB_COPYAREA
975 select FB_CFB_IMAGEBLIT
977 Say Y here if you have a PowerVR 2 card in your box. If you plan to
978 run linux on your Dreamcast, you will have to say Y here.
979 This driver may or may not work on other PowerVR 2 cards, but is
980 totally untested. Use at your own risk. If unsure, say N.
982 To compile this driver as a module, choose M here: the
983 module will be called pvr2fb.
985 You can pass several parameters to the driver at boot time or at
986 module load time. The parameters look like "video=pvr2:XXX", where
987 the meaning of XXX can be found at the end of the main source file
988 (<file:drivers/video/pvr2fb.c>). Please see the file
989 <file:Documentation/fb/pvr2fb.txt>.
992 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
993 depends on FB && HAS_DMA
994 select FB_CFB_FILLRECT
995 select FB_CFB_COPYAREA
996 select FB_CFB_IMAGEBLIT
998 This enables support for the OpenCores VGA/LCD core.
1000 The OpenCores VGA/LCD core is typically used together with
1001 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
1002 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
1004 The source code and specification for the core is available at
1005 <http://opencores.org/project,vga_lcd>
1008 tristate "Epson S1D13XXX framebuffer support"
1010 select FB_CFB_FILLRECT
1011 select FB_CFB_COPYAREA
1012 select FB_CFB_IMAGEBLIT
1014 Support for S1D13XXX framebuffer device family (currently only
1015 working with S1D13806). Product specs at
1016 <http://vdc.epson.com/>
1019 tristate "AT91/AT32 LCD Controller support"
1020 depends on FB && HAVE_FB_ATMEL
1022 select FB_CFB_FILLRECT
1023 select FB_CFB_COPYAREA
1024 select FB_CFB_IMAGEBLIT
1025 select FB_MODE_HELPERS
1026 select VIDEOMODE_HELPERS
1028 This enables support for the AT91/AT32 LCD Controller.
1031 tristate "nVidia Framebuffer Support"
1032 depends on FB && PCI
1033 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1034 select FB_MODE_HELPERS
1035 select FB_CFB_FILLRECT
1036 select FB_CFB_COPYAREA
1037 select FB_CFB_IMAGEBLIT
1041 This driver supports graphics boards with the nVidia chips, TNT
1042 and newer. For very old chipsets, such as the RIVA128, then use
1044 Say Y if you have such a graphics board.
1046 To compile this driver as a module, choose M here: the
1047 module will be called nvidiafb.
1049 config FB_NVIDIA_I2C
1050 bool "Enable DDC Support"
1051 depends on FB_NVIDIA
1054 This enables I2C support for nVidia Chipsets. This is used
1055 only for getting EDID information from the attached display
1056 allowing for robust video mode handling and switching.
1058 Because fbdev-2.6 requires that drivers must be able to
1059 independently validate video mode parameters, you should say Y
1062 config FB_NVIDIA_DEBUG
1063 bool "Lots of debug output"
1064 depends on FB_NVIDIA
1067 Say Y here if you want the nVidia driver to output all sorts
1068 of debugging information to provide to the maintainer when
1069 something goes wrong.
1071 config FB_NVIDIA_BACKLIGHT
1072 bool "Support for backlight control"
1073 depends on FB_NVIDIA
1076 Say Y here if you want to control the backlight of your display.
1079 tristate "nVidia Riva support"
1080 depends on FB && PCI
1081 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1082 select FB_MODE_HELPERS
1083 select FB_CFB_FILLRECT
1084 select FB_CFB_COPYAREA
1085 select FB_CFB_IMAGEBLIT
1089 This driver supports graphics boards with the nVidia Riva/Geforce
1091 Say Y if you have such a graphics board.
1093 To compile this driver as a module, choose M here: the
1094 module will be called rivafb.
1097 bool "Enable DDC Support"
1101 This enables I2C support for nVidia Chipsets. This is used
1102 only for getting EDID information from the attached display
1103 allowing for robust video mode handling and switching.
1105 Because fbdev-2.6 requires that drivers must be able to
1106 independently validate video mode parameters, you should say Y
1109 config FB_RIVA_DEBUG
1110 bool "Lots of debug output"
1114 Say Y here if you want the Riva driver to output all sorts
1115 of debugging information to provide to the maintainer when
1116 something goes wrong.
1118 config FB_RIVA_BACKLIGHT
1119 bool "Support for backlight control"
1123 Say Y here if you want to control the backlight of your display.
1126 tristate "Intel740 support"
1127 depends on FB && PCI
1128 select FB_MODE_HELPERS
1129 select FB_CFB_FILLRECT
1130 select FB_CFB_COPYAREA
1131 select FB_CFB_IMAGEBLIT
1135 This driver supports graphics cards based on Intel740 chip.
1138 tristate "Intel 810/815 support"
1139 depends on FB && PCI && X86_32 && AGP_INTEL
1140 select FB_MODE_HELPERS
1141 select FB_CFB_FILLRECT
1142 select FB_CFB_COPYAREA
1143 select FB_CFB_IMAGEBLIT
1146 This driver supports the on-board graphics built in to the Intel 810
1147 and 815 chipsets. Say Y if you have and plan to use such a board.
1149 To compile this driver as a module, choose M here: the
1150 module will be called i810fb.
1152 For more information, please read
1153 <file:Documentation/fb/intel810.txt>
1156 bool "use VESA Generalized Timing Formula"
1159 If you say Y, then the VESA standard, Generalized Timing Formula
1160 or GTF, will be used to calculate the required video timing values
1161 per video mode. Since the GTF allows nondiscrete timings
1162 (nondiscrete being a range of values as opposed to discrete being a
1163 set of values), you'll be able to use any combination of horizontal
1164 and vertical resolutions, and vertical refresh rates without having
1165 to specify your own timing parameters. This is especially useful
1166 to maximize the performance of an aging display, or if you just
1167 have a display with nonstandard dimensions. A VESA compliant
1168 monitor is recommended, but can still work with non-compliant ones.
1169 If you need or want this, then select this option. The timings may
1170 not be compliant with Intel's recommended values. Use at your own
1173 If you say N, the driver will revert to discrete video timings
1174 using a set recommended by Intel in their documentation.
1179 bool "Enable DDC Support"
1180 depends on FB_I810 && FB_I810_GTF
1185 tristate "Intel LE80578 (Vermilion) support"
1186 depends on FB && PCI && X86
1187 select FB_MODE_HELPERS
1188 select FB_CFB_FILLRECT
1189 select FB_CFB_COPYAREA
1190 select FB_CFB_IMAGEBLIT
1192 This driver supports the LE80578 (Vermilion Range) chipset
1194 config FB_CARILLO_RANCH
1195 tristate "Intel Carillo Ranch support"
1196 depends on FB_LE80578 && FB && PCI && X86
1198 This driver supports the LE80578 (Carillo Ranch) board
1201 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1202 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1203 select FB_MODE_HELPERS
1204 select FB_CFB_FILLRECT
1205 select FB_CFB_COPYAREA
1206 select FB_CFB_IMAGEBLIT
1207 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1208 depends on !DRM_I915
1210 This driver supports the on-board graphics built in to the Intel
1211 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1212 Say Y if you have and plan to use such a board.
1214 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1216 To compile this driver as a module, choose M here: the
1217 module will be called intelfb.
1219 For more information, please read <file:Documentation/fb/intelfb.txt>
1221 config FB_INTEL_DEBUG
1222 bool "Intel driver Debug Messages"
1225 Say Y here if you want the Intel driver to output all sorts
1226 of debugging information to provide to the maintainer when
1227 something goes wrong.
1230 bool "DDC/I2C for Intel framebuffer support"
1235 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1238 tristate "Matrox acceleration"
1239 depends on FB && PCI
1240 select FB_CFB_FILLRECT
1241 select FB_CFB_COPYAREA
1242 select FB_CFB_IMAGEBLIT
1243 select FB_TILEBLITTING
1244 select FB_MACMODES if PPC_PMAC
1246 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1247 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1248 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1249 Matrox G400, G450 or G550 card in your box.
1251 To compile this driver as a module, choose M here: the
1252 module will be called matroxfb.
1254 You can pass several parameters to the driver at boot time or at
1255 module load time. The parameters look like "video=matroxfb:XXX", and
1256 are described in <file:Documentation/fb/matroxfb.txt>.
1258 config FB_MATROX_MILLENIUM
1259 bool "Millennium I/II support"
1260 depends on FB_MATROX
1262 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1263 video card. If you select "Advanced lowlevel driver options" below,
1264 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1265 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1266 also use font widths different from 8.
1268 config FB_MATROX_MYSTIQUE
1269 bool "Mystique support"
1270 depends on FB_MATROX
1272 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1273 video card. If you select "Advanced lowlevel driver options" below,
1274 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1275 packed pixel and 32 bpp packed pixel. You can also use font widths
1279 bool "G100/G200/G400/G450/G550 support"
1280 depends on FB_MATROX
1282 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1283 video card. If you select "Advanced lowlevel driver options", you
1284 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1285 pixel and 32 bpp packed pixel. You can also use font widths
1288 If you need support for G400 secondary head, you must say Y to
1289 "Matrox I2C support" and "G400 second head support" right below.
1290 G450/G550 secondary head and digital output are supported without
1293 The driver starts in monitor mode. You must use the matroxset tool
1294 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1295 swap primary and secondary head outputs, or to change output mode.
1296 Secondary head driver always start in 640x480 resolution and you
1297 must use fbset to change it.
1299 Do not forget that second head supports only 16 and 32 bpp
1300 packed pixels, so it is a good idea to compile them into the kernel
1301 too. You can use only some font widths, as the driver uses generic
1302 painting procedures (the secondary head does not use acceleration
1305 G450/G550 hardware can display TV picture only from secondary CRTC,
1306 and it performs no scaling, so picture must have 525 or 625 lines.
1308 config FB_MATROX_I2C
1309 tristate "Matrox I2C support"
1310 depends on FB_MATROX
1313 This drivers creates I2C buses which are needed for accessing the
1314 DDC (I2C) bus present on all Matroxes, an I2C bus which
1315 interconnects Matrox optional devices, like MGA-TVO on G200 and
1316 G400, and the secondary head DDC bus, present on G400 only.
1318 You can say Y or M here if you want to experiment with monitor
1319 detection code. You must say Y or M here if you want to use either
1320 second head of G400 or MGA-TVO on G200 or G400.
1322 If you compile it as module, it will create a module named
1325 config FB_MATROX_MAVEN
1326 tristate "G400 second head support"
1327 depends on FB_MATROX_G && FB_MATROX_I2C
1329 WARNING !!! This support does not work with G450 !!!
1331 Say Y or M here if you want to use a secondary head (meaning two
1332 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1333 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1334 secondary head output is blanked while you are in X. With XFree
1335 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1336 the fbdev driver on first head and the fbdev driver on second head.
1338 If you compile it as module, two modules are created,
1339 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1340 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1341 also load i2c-matroxfb to get it to run.
1343 The driver starts in monitor mode and you must use the matroxset
1345 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1346 PAL or NTSC or to swap primary and secondary head outputs.
1347 Secondary head driver also always start in 640x480 resolution, you
1348 must use fbset to change it.
1350 Also do not forget that second head supports only 16 and 32 bpp
1351 packed pixels, so it is a good idea to compile them into the kernel
1352 too. You can use only some font widths, as the driver uses generic
1353 painting procedures (the secondary head does not use acceleration
1357 tristate "ATI Radeon display support"
1358 depends on FB && PCI
1359 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1360 select FB_MODE_HELPERS
1361 select FB_CFB_FILLRECT
1362 select FB_CFB_COPYAREA
1363 select FB_CFB_IMAGEBLIT
1364 select FB_MACMODES if PPC
1366 Choose this option if you want to use an ATI Radeon graphics card as
1367 a framebuffer device. There are both PCI and AGP versions. You
1368 don't need to choose this to run the Radeon in plain VGA mode.
1370 There is a product page at
1371 http://products.amd.com/en-us/GraphicCardResult.aspx
1373 config FB_RADEON_I2C
1374 bool "DDC/I2C for ATI Radeon support"
1375 depends on FB_RADEON
1379 Say Y here if you want DDC/I2C support for your Radeon board.
1381 config FB_RADEON_BACKLIGHT
1382 bool "Support for backlight control"
1383 depends on FB_RADEON
1386 Say Y here if you want to control the backlight of your display.
1388 config FB_RADEON_DEBUG
1389 bool "Lots of debug output from Radeon driver"
1390 depends on FB_RADEON
1393 Say Y here if you want the Radeon driver to output all sorts
1394 of debugging information to provide to the maintainer when
1395 something goes wrong.
1398 tristate "ATI Rage128 display support"
1399 depends on FB && PCI
1400 select FB_CFB_FILLRECT
1401 select FB_CFB_COPYAREA
1402 select FB_CFB_IMAGEBLIT
1403 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1404 select FB_MACMODES if PPC_PMAC
1406 This driver supports graphics boards with the ATI Rage128 chips.
1407 Say Y if you have such a graphics board and read
1408 <file:Documentation/fb/aty128fb.txt>.
1410 To compile this driver as a module, choose M here: the
1411 module will be called aty128fb.
1413 config FB_ATY128_BACKLIGHT
1414 bool "Support for backlight control"
1415 depends on FB_ATY128
1418 Say Y here if you want to control the backlight of your display.
1421 tristate "ATI Mach64 display support" if PCI || ATARI
1422 depends on FB && !SPARC32
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1426 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1427 select FB_MACMODES if PPC
1429 This driver supports graphics boards with the ATI Mach64 chips.
1430 Say Y if you have such a graphics board.
1432 To compile this driver as a module, choose M here: the
1433 module will be called atyfb.
1436 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1437 depends on PCI && FB_ATY
1438 default y if SPARC64 && PCI
1440 Say Y here to support use of ATI's 64-bit Rage boards (or other
1441 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1442 framebuffer device. The ATI product support page for these boards
1443 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1445 config FB_ATY_GENERIC_LCD
1446 bool "Mach64 generic LCD support"
1447 depends on FB_ATY_CT
1449 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1450 Rage XC, or Rage XL chipset.
1453 bool "Mach64 GX support" if PCI
1457 Say Y here to support use of the ATI Mach64 Graphics Expression
1458 board (or other boards based on the Mach64 GX chipset) as a
1459 framebuffer device. The ATI product support page for these boards
1461 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1463 config FB_ATY_BACKLIGHT
1464 bool "Support for backlight control"
1468 Say Y here if you want to control the backlight of your display.
1471 tristate "S3 Trio/Virge support"
1472 depends on FB && PCI
1473 select FB_CFB_FILLRECT
1474 select FB_CFB_COPYAREA
1475 select FB_CFB_IMAGEBLIT
1476 select FB_TILEBLITTING
1479 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1481 Driver for graphics boards with S3 Trio / S3 Virge chip.
1484 bool "DDC for S3 support"
1489 Say Y here if you want DDC support for your S3 graphics card.
1492 tristate "S3 Savage support"
1493 depends on FB && PCI
1494 select FB_MODE_HELPERS
1495 select FB_CFB_FILLRECT
1496 select FB_CFB_COPYAREA
1497 select FB_CFB_IMAGEBLIT
1500 This driver supports notebooks and computers with S3 Savage PCI/AGP
1503 Say Y if you have such a graphics card.
1505 To compile this driver as a module, choose M here; the module
1506 will be called savagefb.
1508 config FB_SAVAGE_I2C
1509 bool "Enable DDC2 Support"
1510 depends on FB_SAVAGE
1513 This enables I2C support for S3 Savage Chipsets. This is used
1514 only for getting EDID information from the attached display
1515 allowing for robust video mode handling and switching.
1517 Because fbdev-2.6 requires that drivers must be able to
1518 independently validate video mode parameters, you should say Y
1521 config FB_SAVAGE_ACCEL
1522 bool "Enable Console Acceleration"
1523 depends on FB_SAVAGE
1526 This option will compile in console acceleration support. If
1527 the resulting framebuffer console has bothersome glitches, then
1531 tristate "SiS/XGI display support"
1532 depends on FB && PCI
1533 select FB_CFB_FILLRECT
1534 select FB_CFB_COPYAREA
1535 select FB_CFB_IMAGEBLIT
1536 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1537 select FB_SIS_300 if !FB_SIS_315
1539 This is the frame buffer device driver for the SiS 300, 315, 330
1540 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1541 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1543 To compile this driver as a module, choose M here; the module
1544 will be called sisfb.
1547 bool "SiS 300 series support"
1550 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1553 bool "SiS 315/330/340 series and XGI support"
1556 Say Y here to support use of the SiS 315, 330 and 340 series
1557 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1558 as XGI V3XT, V5, V8 and Z7.
1561 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1562 depends on FB && PCI && X86 && GPIOLIB && I2C
1563 select FB_CFB_FILLRECT
1564 select FB_CFB_COPYAREA
1565 select FB_CFB_IMAGEBLIT
1568 This is the frame buffer device driver for Graphics chips of VIA
1569 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1570 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1572 Say Y if you have a VIA UniChrome graphics board.
1574 To compile this driver as a module, choose M here: the
1575 module will be called viafb.
1579 config FB_VIA_DIRECT_PROCFS
1580 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1584 Allow direct hardware access to some output registers via procfs.
1585 This is dangerous but may provide the only chance to get the
1586 correct output device configuration.
1587 Its use is strongly discouraged.
1589 config FB_VIA_X_COMPATIBILITY
1590 bool "X server compatibility"
1594 This option reduces the functionality (power saving, ...) of the
1595 framebuffer to avoid negative impact on the OpenChrome X server.
1596 If you use any X server other than fbdev you should enable this
1597 otherwise it should be safe to disable it and allow using all
1603 tristate "NeoMagic display support"
1604 depends on FB && PCI
1605 select FB_MODE_HELPERS
1606 select FB_CFB_FILLRECT
1607 select FB_CFB_COPYAREA
1608 select FB_CFB_IMAGEBLIT
1611 This driver supports notebooks with NeoMagic PCI chips.
1612 Say Y if you have such a graphics card.
1614 To compile this driver as a module, choose M here: the
1615 module will be called neofb.
1618 tristate "IMG Kyro support"
1619 depends on FB && PCI
1620 select FB_CFB_FILLRECT
1621 select FB_CFB_COPYAREA
1622 select FB_CFB_IMAGEBLIT
1624 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1627 To compile this driver as a module, choose M here: the
1628 module will be called kyrofb.
1631 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1632 depends on FB && PCI
1633 select FB_CFB_IMAGEBLIT
1634 select FB_CFB_FILLRECT
1635 select FB_CFB_COPYAREA
1636 select FB_MODE_HELPERS
1638 This driver supports graphics boards with the 3Dfx Banshee,
1639 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1640 such a graphics board.
1642 To compile this driver as a module, choose M here: the
1643 module will be called tdfxfb.
1645 config FB_3DFX_ACCEL
1646 bool "3Dfx Acceleration functions"
1649 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1650 device driver with acceleration functions.
1653 bool "Enable DDC/I2C support"
1658 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1661 tristate "3Dfx Voodoo Graphics (sst1) support"
1662 depends on FB && PCI
1663 select FB_CFB_FILLRECT
1664 select FB_CFB_COPYAREA
1665 select FB_CFB_IMAGEBLIT
1667 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1668 Voodoo2 (cvg) based graphics card.
1670 To compile this driver as a module, choose M here: the
1671 module will be called sstfb.
1673 WARNING: Do not use any application that uses the 3D engine
1674 (namely glide) while using this driver.
1675 Please read the <file:Documentation/fb/sstfb.txt> for supported
1676 options and other important info support.
1679 tristate "VIA VT8623 support"
1680 depends on FB && PCI
1681 select FB_CFB_FILLRECT
1682 select FB_CFB_COPYAREA
1683 select FB_CFB_IMAGEBLIT
1684 select FB_TILEBLITTING
1687 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1689 Driver for CastleRock integrated graphics core in the
1690 VIA VT8623 [Apollo CLE266] chipset.
1693 tristate "Trident/CyberXXX/CyberBlade support"
1694 depends on FB && PCI
1695 select FB_CFB_FILLRECT
1696 select FB_CFB_COPYAREA
1697 select FB_CFB_IMAGEBLIT
1699 select FB_MODE_HELPERS
1701 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1702 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1704 There are also integrated versions of these chips called CyberXXXX,
1705 CyberImage or CyberBlade. These chips are mostly found in laptops
1706 but also on some motherboards including early VIA EPIA motherboards.
1707 For more information, read <file:Documentation/fb/tridentfb.txt>
1709 Say Y if you have such a graphics board.
1711 To compile this driver as a module, choose M here: the
1712 module will be called tridentfb.
1715 tristate "ARK 2000PV support"
1716 depends on FB && PCI
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1720 select FB_TILEBLITTING
1723 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1725 Driver for PCI graphics boards with ARK 2000PV chip
1726 and ICS 5342 RAMDAC.
1729 tristate "Permedia3 support"
1730 depends on FB && PCI
1731 select FB_CFB_FILLRECT
1732 select FB_CFB_COPYAREA
1733 select FB_CFB_IMAGEBLIT
1735 This is the frame buffer device driver for the 3DLabs Permedia3
1736 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1737 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1738 and maybe other boards.
1741 tristate "Fujitsu carmine frame buffer support"
1742 depends on FB && PCI
1743 select FB_CFB_FILLRECT
1744 select FB_CFB_COPYAREA
1745 select FB_CFB_IMAGEBLIT
1747 This is the frame buffer device driver for the Fujitsu Carmine chip.
1748 The driver provides two independent frame buffer devices.
1751 depends on FB_CARMINE
1752 prompt "DRAM timing"
1753 default FB_CARMINE_DRAM_EVAL
1755 config FB_CARMINE_DRAM_EVAL
1756 bool "Eval board timings"
1758 Use timings which work on the eval card.
1760 config CARMINE_DRAM_CUSTOM
1761 bool "Custom board timings"
1763 Use custom board timings.
1767 bool "Au1100 LCD Driver"
1768 depends on (FB = y) && MIPS_ALCHEMY
1769 select FB_CFB_FILLRECT
1770 select FB_CFB_COPYAREA
1771 select FB_CFB_IMAGEBLIT
1773 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1774 various panels and CRTs by passing in kernel cmd line option
1775 au1100fb:panel=<name>.
1778 bool "Au1200/Au1300 LCD Driver"
1779 depends on (FB = y) && MIPS_ALCHEMY
1780 select FB_SYS_FILLRECT
1781 select FB_SYS_COPYAREA
1782 select FB_SYS_IMAGEBLIT
1785 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1786 It can drive various panels and CRTs by passing in kernel cmd line
1787 option au1200fb:panel=<name>.
1790 bool "VIA VT8500 framebuffer support"
1791 depends on (FB = y) && ARM && ARCH_VT8500
1792 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1793 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1794 select FB_SYS_IMAGEBLIT
1795 select FB_MODE_HELPERS
1796 select VIDEOMODE_HELPERS
1798 This is the framebuffer driver for VIA VT8500 integrated LCD
1802 bool "Wondermedia WM8xxx-series frame buffer support"
1803 depends on (FB = y) && ARM && ARCH_VT8500
1804 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1805 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1806 select FB_SYS_IMAGEBLIT
1807 select FB_MODE_HELPERS
1808 select VIDEOMODE_HELPERS
1810 This is the framebuffer driver for WonderMedia WM8xxx-series
1811 integrated LCD controller. This driver covers the WM8505, WM8650
1814 config FB_WMT_GE_ROPS
1815 bool "VT8500/WM8xxx accelerated raster ops support"
1816 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1819 This adds support for accelerated raster operations on the
1820 VIA VT8500 and Wondermedia 85xx series SoCs.
1822 source "drivers/video/fbdev/geode/Kconfig"
1825 tristate "HD64461 Frame Buffer support"
1826 depends on FB && HD64461
1827 select FB_CFB_FILLRECT
1828 select FB_CFB_COPYAREA
1829 select FB_CFB_IMAGEBLIT
1831 This is the frame buffer device driver for the Hitachi HD64461 LCD
1835 tristate "PMAG-AA TURBOchannel framebuffer support"
1837 select FB_CFB_FILLRECT
1838 select FB_CFB_COPYAREA
1839 select FB_CFB_IMAGEBLIT
1841 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1842 used mainly in the MIPS-based DECstation series.
1845 tristate "PMAG-BA TURBOchannel framebuffer support"
1847 select FB_CFB_FILLRECT
1848 select FB_CFB_COPYAREA
1849 select FB_CFB_IMAGEBLIT
1851 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1852 used mainly in the MIPS-based DECstation series.
1855 tristate "PMAGB-B TURBOchannel framebuffer support"
1857 select FB_CFB_FILLRECT
1858 select FB_CFB_COPYAREA
1859 select FB_CFB_IMAGEBLIT
1861 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1862 in the MIPS-based DECstation series. The card is currently only
1863 supported in 1280x1024x8 mode.
1866 bool "Maxine (Personal DECstation) onboard framebuffer support"
1867 depends on (FB = y) && MACH_DECSTATION
1868 select FB_CFB_FILLRECT
1869 select FB_CFB_COPYAREA
1870 select FB_CFB_IMAGEBLIT
1872 Support for the onboard framebuffer (1024x768x8) in the Personal
1873 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1877 bool "G364 frame buffer support"
1878 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1879 select FB_CFB_FILLRECT
1880 select FB_CFB_COPYAREA
1881 select FB_CFB_IMAGEBLIT
1883 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1884 Olivetti M700-10 systems.
1887 bool "Motorola 68328 native frame buffer support"
1888 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1889 select FB_CFB_FILLRECT
1890 select FB_CFB_COPYAREA
1891 select FB_CFB_IMAGEBLIT
1893 Say Y here if you want to support the built-in frame buffer of
1894 the Motorola 68328 CPU family.
1897 tristate "PXA168/910 LCD framebuffer support"
1898 depends on FB && (CPU_PXA168 || CPU_PXA910)
1899 select FB_CFB_FILLRECT
1900 select FB_CFB_COPYAREA
1901 select FB_CFB_IMAGEBLIT
1903 Frame buffer driver for the built-in LCD controller in the Marvell
1907 tristate "PXA LCD framebuffer support"
1908 depends on FB && ARCH_PXA
1909 select FB_CFB_FILLRECT
1910 select FB_CFB_COPYAREA
1911 select FB_CFB_IMAGEBLIT
1912 select VIDEOMODE_HELPERS if OF
1913 select FB_MODE_HELPERS if OF
1915 Frame buffer driver for the built-in LCD controller in the Intel
1918 This driver is also available as a module ( = code which can be
1919 inserted and removed from the running kernel whenever you want). The
1920 module will be called pxafb. If you want to compile it as a module,
1921 say M here and read <file:Documentation/kbuild/modules.txt>.
1925 config FB_PXA_OVERLAY
1926 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1928 depends on FB_PXA && (PXA27x || PXA3xx)
1930 config FB_PXA_SMARTPANEL
1931 bool "PXA Smartpanel LCD support"
1935 config FB_PXA_PARAMETERS
1936 bool "PXA LCD command line parameters"
1940 Enable the use of kernel command line or module parameters
1941 to configure the physical properties of the LCD panel when
1942 using the PXA LCD driver.
1944 This option allows you to override the panel parameters
1945 supplied by the platform in order to support multiple
1946 different models of flatpanel. If you will only be using a
1947 single model of flatpanel then you can safely leave this
1950 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1953 tristate "PXA3xx 2D graphics accelerator driver"
1956 Kernelspace driver for the 2D graphics controller unit (GCU)
1957 found on PXA3xx processors. There is a counterpart driver in the
1958 DirectFB suite, see http://www.directfb.org/
1960 If you compile this as a module, it will be called pxa3xx_gcu.
1963 tristate "2700G LCD framebuffer support"
1964 depends on FB && ARCH_PXA
1965 select FB_CFB_FILLRECT
1966 select FB_CFB_COPYAREA
1967 select FB_CFB_IMAGEBLIT
1969 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1973 bool "Enable debugging info via debugfs"
1974 depends on FB_MBX && DEBUG_FS
1977 Enable this if you want debugging information using the debug
1978 filesystem (debugfs)
1983 tristate "Freescale DIU framebuffer support"
1984 depends on FB && FSL_SOC
1985 select FB_MODE_HELPERS
1986 select FB_CFB_FILLRECT
1987 select FB_CFB_COPYAREA
1988 select FB_CFB_IMAGEBLIT
1989 select PPC_LIB_RHEAP
1991 Framebuffer driver for the Freescale SoC DIU
1994 tristate "W100 frame buffer support"
1995 depends on FB && ARCH_PXA
1996 select FB_CFB_FILLRECT
1997 select FB_CFB_COPYAREA
1998 select FB_CFB_IMAGEBLIT
2000 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2001 It can also drive the w3220 chip found on iPAQ hx4700.
2003 This driver is also available as a module ( = code which can be
2004 inserted and removed from the running kernel whenever you want). The
2005 module will be called w100fb. If you want to compile it as a module,
2006 say M here and read <file:Documentation/kbuild/modules.txt>.
2010 config FB_SH_MOBILE_LCDC
2011 tristate "SuperH Mobile LCDC framebuffer support"
2012 depends on FB && (SUPERH || ARCH_RENESAS) && HAVE_CLK
2013 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
2014 select FB_SYS_FILLRECT
2015 select FB_SYS_COPYAREA
2016 select FB_SYS_IMAGEBLIT
2018 select FB_DEFERRED_IO
2021 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2024 tristate "Toshiba Mobile IO FrameBuffer support"
2025 depends on FB && (MFD_TMIO || COMPILE_TEST)
2026 select FB_CFB_FILLRECT
2027 select FB_CFB_COPYAREA
2028 select FB_CFB_IMAGEBLIT
2030 Frame buffer driver for the Toshiba Mobile IO integrated as found
2031 on the Sharp SL-6000 series
2033 This driver is also available as a module ( = code which can be
2034 inserted and removed from the running kernel whenever you want). The
2035 module will be called tmiofb. If you want to compile it as a module,
2036 say M here and read <file:Documentation/kbuild/modules.txt>.
2040 config FB_TMIO_ACCELL
2041 bool "tmiofb acceleration"
2046 tristate "Samsung S3C framebuffer support"
2047 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2048 ARCH_S5PV210 || ARCH_EXYNOS)
2049 select FB_CFB_FILLRECT
2050 select FB_CFB_COPYAREA
2051 select FB_CFB_IMAGEBLIT
2053 Frame buffer driver for the built-in FB controller in the Samsung
2054 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2055 and the S3C64XX series such as the S3C6400 and S3C6410.
2057 These chips all have the same basic framebuffer design with the
2058 actual capabilities depending on the chip. For instance the S3C6400
2059 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2060 currently only have two.
2062 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2064 config FB_S3C_DEBUG_REGWRITE
2065 bool "Debug register writes"
2068 Show all register writes via pr_debug()
2071 tristate "S3C2410 LCD framebuffer support"
2072 depends on FB && ARCH_S3C24XX
2073 select FB_CFB_FILLRECT
2074 select FB_CFB_COPYAREA
2075 select FB_CFB_IMAGEBLIT
2077 Frame buffer driver for the built-in LCD controller in the Samsung
2080 This driver is also available as a module ( = code which can be
2081 inserted and removed from the running kernel whenever you want). The
2082 module will be called s3c2410fb. If you want to compile it as a module,
2083 say M here and read <file:Documentation/kbuild/modules.txt>.
2086 config FB_S3C2410_DEBUG
2087 bool "S3C2410 lcd debug messages"
2088 depends on FB_S3C2410
2090 Turn on debugging messages. Note that you can set/unset at run time
2094 tristate "NUC900 LCD framebuffer support"
2095 depends on FB && ARCH_W90X900
2096 select FB_CFB_FILLRECT
2097 select FB_CFB_COPYAREA
2098 select FB_CFB_IMAGEBLIT
2100 Frame buffer driver for the built-in LCD controller in the Nuvoton
2103 config GPM1040A0_320X240
2104 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2105 depends on FB_NUC900
2108 tristate "Silicon Motion SM501 framebuffer support"
2109 depends on FB && MFD_SM501
2110 select FB_CFB_FILLRECT
2111 select FB_CFB_COPYAREA
2112 select FB_CFB_IMAGEBLIT
2114 Frame buffer driver for the CRT and LCD controllers in the Silicon
2117 This driver is also available as a module ( = code which can be
2118 inserted and removed from the running kernel whenever you want). The
2119 module will be called sm501fb. If you want to compile it as a module,
2120 say M here and read <file:Documentation/kbuild/modules.txt>.
2125 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2126 depends on FB && USB
2127 select FB_MODE_HELPERS
2128 select FB_SYS_FILLRECT
2129 select FB_SYS_COPYAREA
2130 select FB_SYS_IMAGEBLIT
2132 select FB_DEFERRED_IO
2134 This is a kernel framebuffer driver for SMSC UFX USB devices.
2135 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2136 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2138 To compile as a module, choose M here: the module name is smscufx.
2141 tristate "Displaylink USB Framebuffer support"
2142 depends on FB && USB
2143 select FB_MODE_HELPERS
2144 select FB_SYS_FILLRECT
2145 select FB_SYS_COPYAREA
2146 select FB_SYS_IMAGEBLIT
2148 select FB_DEFERRED_IO
2150 This is a kernel framebuffer driver for DisplayLink USB devices.
2151 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2152 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2153 To compile as a module, choose M here: the module name is udlfb.
2155 config FB_IBM_GXT4500
2156 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2158 select FB_CFB_FILLRECT
2159 select FB_CFB_COPYAREA
2160 select FB_CFB_IMAGEBLIT
2162 Say Y here to enable support for the IBM GXT4000P/6000P and
2163 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2164 found on some IBM System P (pSeries) machines. This driver
2165 doesn't use Geometry Engine GT1000. This driver also supports
2166 AGP Fire GL2/3/4 cards on x86.
2169 tristate "PS3 GPU framebuffer driver"
2170 depends on FB && PS3_PS3AV
2171 select FB_SYS_FILLRECT
2172 select FB_SYS_COPYAREA
2173 select FB_SYS_IMAGEBLIT
2176 Include support for the virtual frame buffer in the PS3 platform.
2178 config FB_PS3_DEFAULT_SIZE_M
2179 int "PS3 default frame buffer size (in MiB)"
2183 This is the default size (in MiB) of the virtual frame buffer in
2185 The default value can be overridden on the kernel command line
2186 using the "ps3fb" option (e.g. "ps3fb=9M");
2189 tristate "Xilinx frame buffer support"
2190 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2191 select FB_CFB_FILLRECT
2192 select FB_CFB_COPYAREA
2193 select FB_CFB_IMAGEBLIT
2195 Include support for the Xilinx ML300/ML403 reference design
2196 framebuffer. ML300 carries a 640*480 LCD display on the board,
2197 ML403 uses a standard DB15 VGA connector.
2200 tristate "Goldfish Framebuffer"
2201 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2202 select FB_CFB_FILLRECT
2203 select FB_CFB_COPYAREA
2204 select FB_CFB_IMAGEBLIT
2206 Framebuffer driver for Goldfish Virtual Platform
2209 tristate "Cobalt server LCD frame buffer support"
2210 depends on FB && MIPS_COBALT
2213 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2214 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2215 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2216 select FB_CFB_FILLRECT
2217 select FB_CFB_COPYAREA
2218 select FB_CFB_IMAGEBLIT
2220 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2221 (D)STN/TFT LCD Controller.
2222 Supports display resolutions up to 1024x1024 pixel, grayscale and
2223 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2224 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2225 panels <= 320 pixel horizontal resolution.
2228 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2229 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2230 select FB_CFB_FILLRECT
2231 select FB_CFB_COPYAREA
2232 select FB_CFB_IMAGEBLIT
2233 select FB_CFB_REV_PIXELS_IN_BYTE
2234 select FB_MODE_HELPERS
2235 select VIDEOMODE_HELPERS
2237 This is the frame buffer device driver for the TI LCD controller
2238 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2242 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2244 select FB_SYS_FILLRECT
2245 select FB_SYS_COPYAREA
2246 select FB_SYS_IMAGEBLIT
2249 This is a `virtual' frame buffer device. It operates on a chunk of
2250 unswappable kernel memory instead of on the memory of a graphics
2251 board. This means you cannot see any output sent to this frame
2252 buffer device, while it does consume precious memory. The main use
2253 of this frame buffer device is testing and debugging the frame
2254 buffer subsystem. Do NOT enable it for normal systems! To protect
2255 the innocent, it has to be enabled explicitly at boot time using the
2256 kernel option `video=vfb:'.
2258 To compile this driver as a module, choose M here: the
2259 module will be called vfb. In order to load it, you must use
2260 the vfb_enable=1 option.
2264 config XEN_FBDEV_FRONTEND
2265 tristate "Xen virtual frame buffer support"
2266 depends on FB && XEN
2267 select FB_SYS_FILLRECT
2268 select FB_SYS_COPYAREA
2269 select FB_SYS_IMAGEBLIT
2271 select FB_DEFERRED_IO
2272 select XEN_XENBUS_FRONTEND
2275 This driver implements the front-end of the Xen virtual
2276 frame buffer driver. It communicates with a back-end
2280 tristate "E-Ink Metronome/8track controller support"
2282 select FB_SYS_FILLRECT
2283 select FB_SYS_COPYAREA
2284 select FB_SYS_IMAGEBLIT
2286 select FB_DEFERRED_IO
2288 This driver implements support for the E-Ink Metronome
2289 controller. The pre-release name for this device was 8track
2290 and could also have been called by some vendors as PVI-nnnn.
2293 tristate "Fujitsu MB862xx GDC support"
2295 depends on PCI || (OF && PPC)
2296 select FB_CFB_FILLRECT
2297 select FB_CFB_COPYAREA
2298 select FB_CFB_IMAGEBLIT
2300 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2303 prompt "GDC variant"
2304 depends on FB_MB862XX
2306 config FB_MB862XX_PCI_GDC
2307 bool "Carmine/Coral-P(A) GDC"
2310 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2311 PCI graphics controller devices.
2313 config FB_MB862XX_LIME
2315 depends on OF && PPC
2316 select FB_FOREIGN_ENDIAN
2317 select FB_LITTLE_ENDIAN
2319 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2323 config FB_MB862XX_I2C
2324 bool "Support I2C bus on MB862XX GDC"
2325 depends on FB_MB862XX && I2C
2326 depends on FB_MB862XX=m || I2C=y
2329 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2330 driver to support accessing I2C devices on controller's I2C bus.
2331 These are usually some video decoder chips.
2334 tristate "EP93XX frame buffer support"
2335 depends on FB && ARCH_EP93XX
2336 select FB_CFB_FILLRECT
2337 select FB_CFB_COPYAREA
2338 select FB_CFB_IMAGEBLIT
2340 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2341 This driver is also available as a module. The module will be called
2344 config FB_PRE_INIT_FB
2345 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2346 depends on FB && FB_MB862XX_LIME
2348 Select this option if display contents should be inherited as set by
2352 tristate "MX3 Framebuffer support"
2353 depends on FB && MX3_IPU
2354 select BACKLIGHT_CLASS_DEVICE
2355 select BACKLIGHT_LCD_SUPPORT
2356 select FB_CFB_FILLRECT
2357 select FB_CFB_COPYAREA
2358 select FB_CFB_IMAGEBLIT
2361 This is a framebuffer device for the i.MX31 LCD Controller. So
2362 far only synchronous displays are supported. If you plan to use
2363 an LCD display with your i.MX31 system, say Y here.
2365 config FB_BROADSHEET
2366 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2368 select FB_SYS_FILLRECT
2369 select FB_SYS_COPYAREA
2370 select FB_SYS_IMAGEBLIT
2372 select FB_DEFERRED_IO
2374 This driver implements support for the E-Ink Broadsheet
2375 controller. The release name for this device was Epson S1D13521
2376 and could also have been called by other names when coupled with
2380 tristate "AUO-K190X EPD controller support"
2382 select FB_SYS_FILLRECT
2383 select FB_SYS_COPYAREA
2384 select FB_SYS_IMAGEBLIT
2386 select FB_DEFERRED_IO
2388 Provides support for epaper controllers from the K190X series
2389 of AUO. These controllers can be used to drive epaper displays
2392 This option enables the common support, shared by the individual
2393 controller drivers. You will also have to enable the driver
2394 for the controller type used in your device.
2397 tristate "AUO-K1900 EPD controller support"
2398 depends on FB && FB_AUO_K190X
2400 This driver implements support for the AUO K1900 epd-controller.
2401 This controller can drive Sipix epaper displays but can only do
2402 serial updates, reducing the number of possible frames per second.
2405 tristate "AUO-K1901 EPD controller support"
2406 depends on FB && FB_AUO_K190X
2408 This driver implements support for the AUO K1901 epd-controller.
2409 This controller can drive Sipix epaper displays and supports
2410 concurrent updates, making higher frames per second possible.
2413 tristate "JZ4740 LCD framebuffer support"
2414 depends on FB && MACH_JZ4740
2415 select FB_SYS_FILLRECT
2416 select FB_SYS_COPYAREA
2417 select FB_SYS_IMAGEBLIT
2419 Framebuffer support for the JZ4740 SoC.
2422 tristate "MXS LCD framebuffer support"
2423 depends on FB && (ARCH_MXS || ARCH_MXC)
2424 select FB_CFB_FILLRECT
2425 select FB_CFB_COPYAREA
2426 select FB_CFB_IMAGEBLIT
2427 select FB_MODE_HELPERS
2428 select VIDEOMODE_HELPERS
2430 Framebuffer support for the MXS SoC.
2432 config FB_PUV3_UNIGFX
2433 tristate "PKUnity v3 Unigfx framebuffer support"
2434 depends on FB && UNICORE32 && ARCH_PUV3
2435 select FB_SYS_FILLRECT
2436 select FB_SYS_COPYAREA
2437 select FB_SYS_IMAGEBLIT
2440 Choose this option if you want to use the Unigfx device as a
2441 framebuffer device. Without the support of PCI & AGP.
2444 tristate "Microsoft Hyper-V Synthetic Video support"
2445 depends on FB && HYPERV
2446 select FB_CFB_FILLRECT
2447 select FB_CFB_COPYAREA
2448 select FB_CFB_IMAGEBLIT
2450 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2453 bool "Simple framebuffer support"
2455 select FB_CFB_FILLRECT
2456 select FB_CFB_COPYAREA
2457 select FB_CFB_IMAGEBLIT
2459 Say Y if you want support for a simple frame-buffer.
2461 This driver assumes that the display hardware has been initialized
2462 before the kernel boots, and the kernel will simply render to the
2463 pre-allocated frame buffer surface.
2465 Configuration re: surface address, size, and format must be provided
2466 through device tree, or plain old platform data.
2468 source "drivers/video/fbdev/omap/Kconfig"
2469 source "drivers/video/fbdev/omap2/Kconfig"
2470 source "drivers/video/fbdev/mmp/Kconfig"
2472 config FB_SH_MOBILE_MERAM
2473 tristate "SuperH Mobile MERAM read ahead support"
2474 depends on (SUPERH || ARCH_SHMOBILE)
2475 select GENERIC_ALLOCATOR
2477 Enable MERAM support for the SuperH controller.
2479 This will allow for caching of the framebuffer to provide more
2480 reliable access under heavy main memory bus traffic situations.
2481 Up to 4 memory channels can be configured, allowing 4 RGB or
2482 2 YCbCr framebuffers to be configured.
2485 tristate "Solomon SSD1307 framebuffer support"
2486 depends on FB && I2C
2488 depends on GPIOLIB || COMPILE_TEST
2490 select FB_SYS_FILLRECT
2491 select FB_SYS_COPYAREA
2492 select FB_SYS_IMAGEBLIT
2493 select FB_DEFERRED_IO
2497 This driver implements support for the Solomon SSD1307
2498 OLED controller over I2C.
2501 tristate "Silicon Motion SM712 framebuffer support"
2502 depends on FB && PCI
2503 select FB_CFB_FILLRECT
2504 select FB_CFB_COPYAREA
2505 select FB_CFB_IMAGEBLIT
2507 Frame buffer driver for the Silicon Motion SM710, SM712, SM721
2510 This driver is also available as a module. The module will be
2511 called sm712fb. If you want to compile it as a module, say M
2512 here and read <file:Documentation/kbuild/modules.txt>.