6 tristate "Support for frame buffer devices"
8 The frame buffer device provides an abstraction for the graphics
9 hardware. It represents the frame buffer of some video hardware and
10 allows application software to access the graphics hardware through
11 a well-defined interface, so the software doesn't need to know
12 anything about the low-level (hardware register) stuff.
14 Frame buffer devices work identically across the different
15 architectures supported by Linux and make the implementation of
16 application programs easier and more portable; at this point, an X
17 server exists which uses the frame buffer device exclusively.
18 On several non-X86 architectures, the frame buffer device is the
19 only way to use the graphics hardware.
21 The device is accessed through special device nodes, usually located
22 in the /dev directory, i.e. /dev/fb*.
24 You need an utility program called fbset to make full use of frame
25 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
26 and the Framebuffer-HOWTO at
27 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
30 Say Y here and to the driver for your graphics board below if you
31 are compiling a kernel for a non-x86 architecture.
33 If you are compiling for the x86 architecture, you can say Y if you
34 want to play with it, but it is not essential. Please note that
35 running graphical applications that directly touch the hardware
36 (e.g. an accelerated X server) and that are not frame buffer
37 device-aware may cause unexpected results. If unsure, say N.
40 bool "Enable firmware EDID"
44 This enables access to the EDID transferred from the firmware.
45 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
46 transfers do not work for your driver and if you are using
47 nvidiafb, i810fb or savagefb.
49 In general, choosing Y for this option is safe. If you
50 experience extremely long delays while booting before you get
51 something on your display, try setting this to N. Matrox cards in
52 combination with certain motherboards and monitors are known to
53 suffer from this problem.
62 config FB_BOOT_VESA_SUPPORT
67 If true, at least one selected framebuffer driver can take advantage
68 of VESA video modes set at an early boot stage via the vga= parameter.
70 config FB_CFB_FILLRECT
75 Include the cfb_fillrect function for generic software rectangle
76 filling. This is used by drivers that don't provide their own
77 (accelerated) version.
79 config FB_CFB_COPYAREA
84 Include the cfb_copyarea function for generic software area copying.
85 This is used by drivers that don't provide their own (accelerated)
88 config FB_CFB_IMAGEBLIT
93 Include the cfb_imageblit function for generic software image
94 blitting. This is used by drivers that don't provide their own
95 (accelerated) version.
97 config FB_CFB_REV_PIXELS_IN_BYTE
102 Allow generic frame-buffer functions to work on displays with 1, 2
103 and 4 bits per pixel depths which has opposite order of pixels in
104 byte order to bytes in long order.
106 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
120 Include the sys_copyarea function for generic software area copying.
121 This is used by drivers that don't provide their own (accelerated)
122 version and the framebuffer is in system RAM.
124 config FB_SYS_IMAGEBLIT
129 Include the sys_imageblit function for generic software image
130 blitting. This is used by drivers that don't provide their own
131 (accelerated) version and the framebuffer is in system RAM.
133 menuconfig FB_FOREIGN_ENDIAN
134 bool "Framebuffer foreign endianness support"
137 This menu will let you enable support for the framebuffers with
138 non-native endianness (e.g. Little-Endian framebuffer on a
139 Big-Endian machine). Most probably you don't have such hardware,
140 so it's safe to say "n" here.
143 prompt "Choice endianness support"
144 depends on FB_FOREIGN_ENDIAN
146 config FB_BOTH_ENDIAN
147 bool "Support for Big- and Little-Endian framebuffers"
150 bool "Support for Big-Endian framebuffers only"
152 config FB_LITTLE_ENDIAN
153 bool "Support for Little-Endian framebuffers only"
162 config FB_DEFERRED_IO
169 depends on FB_DEFERRED_IO
176 Common utility functions useful to fbdev drivers of VGA-based
187 select BACKLIGHT_LCD_SUPPORT
188 select BACKLIGHT_CLASS_DEVICE
191 config FB_MODE_HELPERS
192 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"
207 This enables tile blitting. Tile blitting is a drawing technique
208 where the screen is divided into rectangular sections (tiles), whereas
209 the standard blitting divides the screen into pixels. Because the
210 default drawing element is a tile, drawing functions will be passed
211 parameters in terms of number of tiles instead of number of pixels.
212 For example, to draw a single character, instead of using bitmaps,
213 an index to an array of bitmaps will be used. To clear or move a
214 rectangular section of a screen, the rectangle will be described in
215 terms of number of tiles in the x- and y-axis.
217 This is particularly important to one driver, matroxfb. If
220 comment "Frame buffer hardware drivers"
224 tristate "Aeroflex Gaisler framebuffer support"
225 depends on FB && SPARC
226 select FB_CFB_FILLRECT
227 select FB_CFB_COPYAREA
228 select FB_CFB_IMAGEBLIT
230 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
233 tristate "Cirrus Logic support"
234 depends on FB && (ZORRO || PCI)
235 select FB_CFB_FILLRECT
236 select FB_CFB_COPYAREA
237 select FB_CFB_IMAGEBLIT
239 This enables support for Cirrus Logic GD542x/543x based boards on
240 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
242 If you have a PCI-based system, this enables support for these
243 chips: GD-543x, GD-544x, GD-5480.
245 Please read the file <file:Documentation/fb/cirrusfb.txt>.
247 Say N unless you have such a graphics board or plan to get one
248 before you next recompile the kernel.
251 tristate "Permedia2 support"
252 depends on FB && ((AMIGA && BROKEN) || PCI)
253 select FB_CFB_FILLRECT
254 select FB_CFB_COPYAREA
255 select FB_CFB_IMAGEBLIT
257 This is the frame buffer device driver for cards based on
258 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
259 The driver was tested on the following cards:
260 Diamond FireGL 1000 PRO AGP
261 ELSA Gloria Synergy PCI
262 Appian Jeronimo PRO (both heads) PCI
263 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
264 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
265 ASK Graphic Blaster Exxtreme AGP
267 To compile this driver as a module, choose M here: the
268 module will be called pm2fb.
270 config FB_PM2_FIFO_DISCONNECT
271 bool "enable FIFO disconnect feature"
272 depends on FB_PM2 && PCI
274 Support the Permedia2 FIFO disconnect feature.
277 tristate "ARM PrimeCell PL110 support"
278 depends on ARM || ARM64 || COMPILE_TEST
279 depends on FB && ARM_AMBA
280 select FB_CFB_FILLRECT
281 select FB_CFB_COPYAREA
282 select FB_CFB_IMAGEBLIT
284 This framebuffer device driver is for the ARM PrimeCell PL110
285 Colour LCD controller. ARM PrimeCells provide the building
286 blocks for System on a Chip devices.
288 If you want to compile this as a module (=code which can be
289 inserted into and removed from the running kernel), say M
290 here and read <file:Documentation/kbuild/modules.txt>. The module
291 will be called amba-clcd.
293 # Helper logic selected only by the ARM Versatile platform family.
294 config PLAT_VERSATILE_CLCD
295 def_bool ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
297 depends on FB_ARMCLCD && FB=y
300 bool "Acorn VIDC support"
301 depends on (FB = y) && ARM && ARCH_ACORN
302 select FB_CFB_FILLRECT
303 select FB_CFB_COPYAREA
304 select FB_CFB_IMAGEBLIT
306 This is the frame buffer device driver for the Acorn VIDC graphics
307 hardware found in Acorn RISC PCs and other ARM-based machines. If
311 bool "CLPS711X LCD support"
312 depends on (FB = y) && ARM && ARCH_CLPS711X
313 select FB_CFB_FILLRECT
314 select FB_CFB_COPYAREA
315 select FB_CFB_IMAGEBLIT
317 Say Y to enable the Framebuffer driver for the CLPS7111 and
321 bool "SA-1100 LCD support"
322 depends on (FB = y) && ARM && ARCH_SA1100
323 select FB_CFB_FILLRECT
324 select FB_CFB_COPYAREA
325 select FB_CFB_IMAGEBLIT
327 This is a framebuffer device for the SA-1100 LCD Controller.
328 See <http://www.linux-fbdev.org/> for information on framebuffer
331 If you plan to use the LCD display with your SA-1100 system, say
335 tristate "Freescale i.MX1/21/25/27 LCD support"
336 depends on FB && ARCH_MXC
337 select BACKLIGHT_LCD_SUPPORT
338 select LCD_CLASS_DEVICE
339 select FB_CFB_FILLRECT
340 select FB_CFB_COPYAREA
341 select FB_CFB_IMAGEBLIT
342 select FB_MODE_HELPERS
343 select VIDEOMODE_HELPERS
346 tristate "CyberPro 2000/2010/5000 support"
347 depends on FB && PCI && (BROKEN || !SPARC64)
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This enables support for the Integraphics CyberPro 20x0 and 5000
353 VGA chips used in the Rebel.com Netwinder and other machines.
354 Say Y if you have a NetWinder or a graphics card containing this
355 device, otherwise say N.
357 config FB_CYBER2000_DDC
358 bool "DDC for CyberPro support"
359 depends on FB_CYBER2000
363 Say Y here if you want DDC support for your CyberPro graphics
364 card. This is only I2C bus support, driver does not use EDID.
366 config FB_CYBER2000_I2C
367 bool "CyberPro 2000/2010/5000 I2C support"
368 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
369 depends on I2C=y || FB_CYBER2000=m
372 Enable support for the I2C video decoder interface on the
373 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
374 on the Netwinder machines for the SAA7111 video capture.
378 depends on (FB = y) && APOLLO
380 select FB_CFB_FILLRECT
381 select FB_CFB_IMAGEBLIT
385 depends on (FB = y) && Q40
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
392 tristate "Amiga native chipset support"
393 depends on FB && AMIGA
395 This is the frame buffer device driver for the builtin graphics
396 chipset found in Amigas.
398 To compile this driver as a module, choose M here: the
399 module will be called amifb.
402 bool "Amiga OCS chipset support"
405 This enables support for the original Agnus and Denise video chips,
406 found in the Amiga 1000 and most A500's and A2000's. If you intend
407 to run Linux on any of these systems, say Y; otherwise say N.
410 bool "Amiga ECS chipset support"
413 This enables support for the Enhanced Chip Set, found in later
414 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
415 you intend to run Linux on any of these systems, say Y; otherwise
419 bool "Amiga AGA chipset support"
422 This enables support for the Advanced Graphics Architecture (also
423 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
424 and CD32. If you intend to run Linux on any of these systems, say Y;
428 bool "Amiga FrameMaster II/Rainbow II support"
429 depends on (FB = y) && ZORRO
430 select FB_CFB_FILLRECT
431 select FB_CFB_COPYAREA
432 select FB_CFB_IMAGEBLIT
434 This is the frame buffer device driver for the Amiga FrameMaster
435 card from BSC (exhibited 1992 but not shipped as a CBM product).
438 tristate "Arc Monochrome LCD board support"
440 select FB_SYS_FILLRECT
441 select FB_SYS_COPYAREA
442 select FB_SYS_IMAGEBLIT
445 This enables support for the Arc Monochrome LCD board. The board
446 is based on the KS-108 lcd controller and is typically a matrix
447 of 2*n chips. This driver was tested with a 128x64 panel. This
448 driver supports it for use with x86 SBCs through a 16 bit GPIO
449 interface (8 bit data, 8 bit control). If you anticipate using
450 this driver, say Y or M; otherwise say N. You must specify the
451 GPIO IO address to be used for setting control and data.
454 bool "Atari native chipset support"
455 depends on (FB = y) && ATARI
456 select FB_CFB_FILLRECT
457 select FB_CFB_COPYAREA
458 select FB_CFB_IMAGEBLIT
460 This is the frame buffer device driver for the builtin graphics
461 chipset found in Ataris.
464 bool "Open Firmware frame buffer device support"
465 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
466 select FB_CFB_FILLRECT
467 select FB_CFB_COPYAREA
468 select FB_CFB_IMAGEBLIT
471 Say Y if you want support with Open Firmware for your graphics
475 bool "Apple \"control\" display support"
476 depends on (FB = y) && PPC_PMAC && PPC32
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
482 This driver supports a frame buffer for the graphics adapter in the
483 Power Macintosh 7300 and others.
486 bool "Apple \"platinum\" display support"
487 depends on (FB = y) && PPC_PMAC && PPC32
488 select FB_CFB_FILLRECT
489 select FB_CFB_COPYAREA
490 select FB_CFB_IMAGEBLIT
493 This driver supports a frame buffer for the "platinum" graphics
494 adapter in some Power Macintoshes.
497 bool "Apple \"valkyrie\" display support"
498 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 This driver supports a frame buffer for the "valkyrie" graphics
505 adapter in some Power Macintoshes.
508 bool "Chips 65550 display support"
509 depends on (FB = y) && PPC32 && PCI
510 select FB_CFB_FILLRECT
511 select FB_CFB_COPYAREA
512 select FB_CFB_IMAGEBLIT
514 This is the frame buffer device driver for the Chips & Technologies
515 65550 graphics chip in PowerBooks.
518 bool "Asiliant (Chips) 69000 display support"
519 depends on (FB = y) && PCI
520 select FB_CFB_FILLRECT
521 select FB_CFB_COPYAREA
522 select FB_CFB_IMAGEBLIT
524 This is the frame buffer device driver for the Asiliant 69030 chipset
527 bool "IMS Twin Turbo display support"
528 depends on (FB = y) && PCI
529 select FB_CFB_IMAGEBLIT
530 select FB_MACMODES if PPC
532 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
533 many Macintosh and compatible computers.
536 tristate "VGA 16-color graphics support"
537 depends on FB && (X86 || PPC)
538 select FB_CFB_FILLRECT
539 select FB_CFB_COPYAREA
540 select FB_CFB_IMAGEBLIT
542 select FONT_8x16 if FRAMEBUFFER_CONSOLE
544 This is the frame buffer device driver for VGA 16 color graphic
545 cards. Say Y if you have such a card.
547 To compile this driver as a module, choose M here: the
548 module will be called vga16fb.
550 config FB_BF54X_LQ043
551 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
552 depends on FB && (BF54x) && !BF542
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
557 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
559 config FB_BFIN_T350MCQB
560 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
561 depends on FB && BLACKFIN
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
567 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
568 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
569 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
571 config FB_BFIN_LQ035Q1
572 tristate "SHARP LQ035Q1DH02 TFT LCD"
573 depends on FB && BLACKFIN && SPI
574 select FB_CFB_FILLRECT
575 select FB_CFB_COPYAREA
576 select FB_CFB_IMAGEBLIT
579 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
580 the Blackfin Landscape LCD EZ-Extender Card.
581 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
582 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
584 To compile this driver as a module, choose M here: the
585 module will be called bfin-lq035q1-fb.
587 config FB_BF537_LQ035
588 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
589 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
590 select FB_CFB_FILLRECT
591 select FB_CFB_COPYAREA
592 select FB_CFB_IMAGEBLIT
595 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
598 To compile this driver as a module, choose M here: the
599 module will be called bf537-lq035.
602 tristate "Blackfin ADV7393 Video encoder"
603 depends on FB && BLACKFIN
605 select FB_CFB_FILLRECT
606 select FB_CFB_COPYAREA
607 select FB_CFB_IMAGEBLIT
609 This is the framebuffer device for a ADV7393 video encoder
610 attached to a Blackfin on the PPI port.
611 If your Blackfin board has a ADV7393 select Y.
613 To compile this driver as a module, choose M here: the
614 module will be called bfin_adv7393fb.
617 prompt "Video mode support"
618 depends on FB_BFIN_7393
628 bool 'NTSC 640x480 (Experimental)'
631 bool 'PAL 640x480 (Experimental)'
634 bool 'NTSC 720x480 YCbCR input'
637 bool 'PAL 720x576 YCbCR input'
642 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
643 depends on (FB_BFIN_7393)
644 default ADV7393_1XMEM
654 tristate "HP STI frame buffer device support"
655 depends on FB && PARISC
656 select FB_CFB_FILLRECT
657 select FB_CFB_COPYAREA
658 select FB_CFB_IMAGEBLIT
663 STI refers to the HP "Standard Text Interface" which is a set of
664 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
665 Enabling this option will implement the linux framebuffer device
666 using calls to the STI BIOS routines for initialisation.
668 If you enable this option, you will get a planar framebuffer device
669 /dev/fb which will work on the most common HP graphic cards of the
670 NGLE family, including the artist chips (in the 7xx and Bxxx series),
671 HCRX, HCRX24, CRX, CRX24 and VisEG series.
673 It is safe to enable this option, so you should probably say "Y".
676 bool "Generic Macintosh display support"
677 depends on (FB = y) && MAC
678 select FB_CFB_FILLRECT
679 select FB_CFB_COPYAREA
680 select FB_CFB_IMAGEBLIT
685 depends on (FB = y) && DIO
686 select FB_CFB_IMAGEBLIT
690 tristate "TGA/SFB+ framebuffer support"
691 depends on FB && (ALPHA || TC)
692 select FB_CFB_FILLRECT
693 select FB_CFB_COPYAREA
694 select FB_CFB_IMAGEBLIT
697 This is the frame buffer device driver for generic TGA and SFB+
698 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
699 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
700 TURBOchannel cards, also known as PMAGD-A, -B and -C.
702 Due to hardware limitations ZLX-E2 and E3 cards are not supported
703 for DECstation 5000/200 systems. Additionally due to firmware
704 limitations these cards may cause troubles with booting DECstation
705 5000/240 and /260 systems, but are fully supported under Linux if
706 you manage to get it going. ;-)
708 Say Y if you have one of those.
711 tristate "Userspace VESA VGA graphics support"
712 depends on FB && CONNECTOR
713 select FB_CFB_FILLRECT
714 select FB_CFB_COPYAREA
715 select FB_CFB_IMAGEBLIT
716 select FB_MODE_HELPERS
718 This is the frame buffer driver for generic VBE 2.0 compliant
719 graphic cards. It can also take advantage of VBE 3.0 features,
720 such as refresh rate adjustment.
722 This driver generally provides more features than vesafb but
723 requires a userspace helper application called 'v86d'. See
724 <file:Documentation/fb/uvesafb.txt> for more information.
729 bool "VESA VGA graphics support"
730 depends on (FB = y) && X86
731 select FB_CFB_FILLRECT
732 select FB_CFB_COPYAREA
733 select FB_CFB_IMAGEBLIT
734 select FB_BOOT_VESA_SUPPORT
736 This is the frame buffer device driver for generic VESA 2.0
737 compliant graphic cards. The older VESA 1.2 cards are not supported.
738 You will get a boot time penguin logo at no additional cost. Please
739 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
742 bool "EFI-based Framebuffer Support"
743 depends on (FB = y) && X86 && EFI
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
748 This is the EFI frame buffer device driver. If the firmware on
749 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
750 using the EFI framebuffer as your console.
753 tristate "N411 Apollo/Hecuba devkit support"
754 depends on FB && X86 && MMU
755 select FB_SYS_FILLRECT
756 select FB_SYS_COPYAREA
757 select FB_SYS_IMAGEBLIT
759 select FB_DEFERRED_IO
762 This enables support for the Apollo display controller in its
763 Hecuba form using the n411 devkit.
766 tristate "Hercules mono graphics support"
769 Say Y here if you have a Hercules mono graphics card.
771 To compile this driver as a module, choose M here: the
772 module will be called hgafb.
774 As this card technology is at least 25 years old,
775 most people will answer N here.
778 bool "SGI Graphics Backend frame buffer support"
779 depends on (FB = y) && SGI_IP32
780 select FB_CFB_FILLRECT
781 select FB_CFB_COPYAREA
782 select FB_CFB_IMAGEBLIT
784 This is the frame buffer device driver for SGI Graphics Backend.
785 This chip is used in SGI O2 and Visual Workstation 320/540.
788 int "Video memory size in MB"
792 This is the amount of memory reserved for the framebuffer,
793 which can be any value between 1MB and 8MB.
796 bool "SBUS and UPA framebuffers"
797 depends on (FB = y) && SPARC
799 Say Y if you want support for SBUS or UPA based frame buffer device.
803 depends on (FB = y) && (SPARC && FB_SBUS)
804 select FB_CFB_FILLRECT
805 select FB_CFB_COPYAREA
806 select FB_CFB_IMAGEBLIT
808 This is the frame buffer device driver for the BWtwo frame buffer.
811 bool "CGthree support"
812 depends on (FB = y) && (SPARC && FB_SBUS)
813 select FB_CFB_FILLRECT
814 select FB_CFB_COPYAREA
815 select FB_CFB_IMAGEBLIT
817 This is the frame buffer device driver for the CGthree frame buffer.
820 bool "CGsix (GX,TurboGX) support"
821 depends on (FB = y) && (SPARC && FB_SBUS)
822 select FB_CFB_COPYAREA
823 select FB_CFB_IMAGEBLIT
825 This is the frame buffer device driver for the CGsix (GX, TurboGX)
829 bool "Creator/Creator3D/Elite3D support"
830 depends on FB_SBUS && SPARC64
831 select FB_CFB_COPYAREA
832 select FB_CFB_IMAGEBLIT
834 This is the frame buffer device driver for the Creator, Creator3D,
835 and Elite3D graphics boards.
838 bool "TCX (SS4/SS5 only) support"
840 select FB_CFB_FILLRECT
841 select FB_CFB_COPYAREA
842 select FB_CFB_IMAGEBLIT
844 This is the frame buffer device driver for the TCX 24/8bit frame
848 bool "CGfourteen (SX) support"
850 select FB_CFB_FILLRECT
851 select FB_CFB_COPYAREA
852 select FB_CFB_IMAGEBLIT
854 This is the frame buffer device driver for the CGfourteen frame
855 buffer on Desktop SPARCsystems with the SX graphics option.
858 bool "P9100 (Sparcbook 3 only) support"
860 select FB_CFB_FILLRECT
861 select FB_CFB_COPYAREA
862 select FB_CFB_IMAGEBLIT
864 This is the frame buffer device driver for the P9100 card
865 supported on Sparcbook 3 machines.
868 bool "Leo (ZX) support"
870 select FB_CFB_FILLRECT
871 select FB_CFB_COPYAREA
872 select FB_CFB_IMAGEBLIT
874 This is the frame buffer device driver for the SBUS-based Sun ZX
875 (leo) frame buffer cards.
878 bool "IGA 168x display support"
879 depends on (FB = y) && SPARC32
880 select FB_CFB_FILLRECT
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
884 This is the framebuffer device for the INTERGRAPHICS 1680 and
885 successor frame buffer cards.
888 bool "Sun XVR-500 3DLABS Wildcat support"
889 depends on (FB = y) && PCI && SPARC64
890 select FB_CFB_FILLRECT
891 select FB_CFB_COPYAREA
892 select FB_CFB_IMAGEBLIT
894 This is the framebuffer device for the Sun XVR-500 and similar
895 graphics cards based upon the 3DLABS Wildcat chipset. The driver
896 only works on sparc64 systems where the system firmware has
897 mostly initialized the card already. It is treated as a
898 completely dumb framebuffer device.
901 bool "Sun XVR-2500 3DLABS Wildcat support"
902 depends on (FB = y) && PCI && SPARC64
903 select FB_CFB_FILLRECT
904 select FB_CFB_COPYAREA
905 select FB_CFB_IMAGEBLIT
907 This is the framebuffer device for the Sun XVR-2500 and similar
908 graphics cards based upon the 3DLABS Wildcat chipset. The driver
909 only works on sparc64 systems where the system firmware has
910 mostly initialized the card already. It is treated as a
911 completely dumb framebuffer device.
914 bool "Sun XVR-1000 support"
915 depends on (FB = y) && SPARC64
916 select FB_CFB_FILLRECT
917 select FB_CFB_COPYAREA
918 select FB_CFB_IMAGEBLIT
920 This is the framebuffer device for the Sun XVR-1000 and similar
921 graphics cards. The driver only works on sparc64 systems where
922 the system firmware has mostly initialized the card already. It
923 is treated as a completely dumb framebuffer device.
926 tristate "NEC PowerVR 2 display support"
927 depends on FB && SH_DREAMCAST
928 select FB_CFB_FILLRECT
929 select FB_CFB_COPYAREA
930 select FB_CFB_IMAGEBLIT
932 Say Y here if you have a PowerVR 2 card in your box. If you plan to
933 run linux on your Dreamcast, you will have to say Y here.
934 This driver may or may not work on other PowerVR 2 cards, but is
935 totally untested. Use at your own risk. If unsure, say N.
937 To compile this driver as a module, choose M here: the
938 module will be called pvr2fb.
940 You can pass several parameters to the driver at boot time or at
941 module load time. The parameters look like "video=pvr2:XXX", where
942 the meaning of XXX can be found at the end of the main source file
943 (<file:drivers/video/pvr2fb.c>). Please see the file
944 <file:Documentation/fb/pvr2fb.txt>.
947 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
948 depends on FB && HAS_DMA
949 select FB_CFB_FILLRECT
950 select FB_CFB_COPYAREA
951 select FB_CFB_IMAGEBLIT
953 This enables support for the OpenCores VGA/LCD core.
955 The OpenCores VGA/LCD core is typically used together with
956 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
957 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
959 The source code and specification for the core is available at
960 <http://opencores.org/project,vga_lcd>
963 tristate "Epson S1D13XXX framebuffer support"
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
969 Support for S1D13XXX framebuffer device family (currently only
970 working with S1D13806). Product specs at
971 <http://vdc.epson.com/>
974 tristate "AT91/AT32 LCD Controller support"
975 depends on FB && HAVE_FB_ATMEL
977 select FB_CFB_FILLRECT
978 select FB_CFB_COPYAREA
979 select FB_CFB_IMAGEBLIT
980 select FB_MODE_HELPERS
981 select VIDEOMODE_HELPERS
983 This enables support for the AT91/AT32 LCD Controller.
986 bool "Frame Buffer in internal SRAM"
987 depends on FB_ATMEL && ARCH_AT91SAM9261
989 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
990 to let frame buffer in external SDRAM.
993 bool "Use a STN display with AT91/AT32 LCD Controller"
994 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
997 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
998 Controller. Say N if you want to connect a TFT.
1003 tristate "nVidia Framebuffer Support"
1004 depends on FB && PCI
1005 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1006 select FB_MODE_HELPERS
1007 select FB_CFB_FILLRECT
1008 select FB_CFB_COPYAREA
1009 select FB_CFB_IMAGEBLIT
1013 This driver supports graphics boards with the nVidia chips, TNT
1014 and newer. For very old chipsets, such as the RIVA128, then use
1016 Say Y if you have such a graphics board.
1018 To compile this driver as a module, choose M here: the
1019 module will be called nvidiafb.
1021 config FB_NVIDIA_I2C
1022 bool "Enable DDC Support"
1023 depends on FB_NVIDIA
1026 This enables I2C support for nVidia Chipsets. This is used
1027 only for getting EDID information from the attached display
1028 allowing for robust video mode handling and switching.
1030 Because fbdev-2.6 requires that drivers must be able to
1031 independently validate video mode parameters, you should say Y
1034 config FB_NVIDIA_DEBUG
1035 bool "Lots of debug output"
1036 depends on FB_NVIDIA
1039 Say Y here if you want the nVidia driver to output all sorts
1040 of debugging information to provide to the maintainer when
1041 something goes wrong.
1043 config FB_NVIDIA_BACKLIGHT
1044 bool "Support for backlight control"
1045 depends on FB_NVIDIA
1048 Say Y here if you want to control the backlight of your display.
1051 tristate "nVidia Riva support"
1052 depends on FB && PCI
1053 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1054 select FB_MODE_HELPERS
1055 select FB_CFB_FILLRECT
1056 select FB_CFB_COPYAREA
1057 select FB_CFB_IMAGEBLIT
1061 This driver supports graphics boards with the nVidia Riva/Geforce
1063 Say Y if you have such a graphics board.
1065 To compile this driver as a module, choose M here: the
1066 module will be called rivafb.
1069 bool "Enable DDC Support"
1073 This enables I2C support for nVidia Chipsets. This is used
1074 only for getting EDID information from the attached display
1075 allowing for robust video mode handling and switching.
1077 Because fbdev-2.6 requires that drivers must be able to
1078 independently validate video mode parameters, you should say Y
1081 config FB_RIVA_DEBUG
1082 bool "Lots of debug output"
1086 Say Y here if you want the Riva driver to output all sorts
1087 of debugging information to provide to the maintainer when
1088 something goes wrong.
1090 config FB_RIVA_BACKLIGHT
1091 bool "Support for backlight control"
1095 Say Y here if you want to control the backlight of your display.
1098 tristate "Intel740 support"
1099 depends on FB && PCI
1100 select FB_MODE_HELPERS
1101 select FB_CFB_FILLRECT
1102 select FB_CFB_COPYAREA
1103 select FB_CFB_IMAGEBLIT
1107 This driver supports graphics cards based on Intel740 chip.
1110 tristate "Intel 810/815 support"
1111 depends on FB && PCI && X86_32 && AGP_INTEL
1112 select FB_MODE_HELPERS
1113 select FB_CFB_FILLRECT
1114 select FB_CFB_COPYAREA
1115 select FB_CFB_IMAGEBLIT
1118 This driver supports the on-board graphics built in to the Intel 810
1119 and 815 chipsets. Say Y if you have and plan to use such a board.
1121 To compile this driver as a module, choose M here: the
1122 module will be called i810fb.
1124 For more information, please read
1125 <file:Documentation/fb/intel810.txt>
1128 bool "use VESA Generalized Timing Formula"
1131 If you say Y, then the VESA standard, Generalized Timing Formula
1132 or GTF, will be used to calculate the required video timing values
1133 per video mode. Since the GTF allows nondiscrete timings
1134 (nondiscrete being a range of values as opposed to discrete being a
1135 set of values), you'll be able to use any combination of horizontal
1136 and vertical resolutions, and vertical refresh rates without having
1137 to specify your own timing parameters. This is especially useful
1138 to maximize the performance of an aging display, or if you just
1139 have a display with nonstandard dimensions. A VESA compliant
1140 monitor is recommended, but can still work with non-compliant ones.
1141 If you need or want this, then select this option. The timings may
1142 not be compliant with Intel's recommended values. Use at your own
1145 If you say N, the driver will revert to discrete video timings
1146 using a set recommended by Intel in their documentation.
1151 bool "Enable DDC Support"
1152 depends on FB_I810 && FB_I810_GTF
1157 tristate "Intel LE80578 (Vermilion) support"
1158 depends on FB && PCI && X86
1159 select FB_MODE_HELPERS
1160 select FB_CFB_FILLRECT
1161 select FB_CFB_COPYAREA
1162 select FB_CFB_IMAGEBLIT
1164 This driver supports the LE80578 (Vermilion Range) chipset
1166 config FB_CARILLO_RANCH
1167 tristate "Intel Carillo Ranch support"
1168 depends on FB_LE80578 && FB && PCI && X86
1170 This driver supports the LE80578 (Carillo Ranch) board
1173 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1174 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1175 select FB_MODE_HELPERS
1176 select FB_CFB_FILLRECT
1177 select FB_CFB_COPYAREA
1178 select FB_CFB_IMAGEBLIT
1179 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1180 depends on !DRM_I915
1182 This driver supports the on-board graphics built in to the Intel
1183 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1184 Say Y if you have and plan to use such a board.
1186 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1188 To compile this driver as a module, choose M here: the
1189 module will be called intelfb.
1191 For more information, please read <file:Documentation/fb/intelfb.txt>
1193 config FB_INTEL_DEBUG
1194 bool "Intel driver Debug Messages"
1197 Say Y here if you want the Intel driver to output all sorts
1198 of debugging information to provide to the maintainer when
1199 something goes wrong.
1202 bool "DDC/I2C for Intel framebuffer support"
1207 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1210 tristate "Matrox acceleration"
1211 depends on FB && PCI
1212 select FB_CFB_FILLRECT
1213 select FB_CFB_COPYAREA
1214 select FB_CFB_IMAGEBLIT
1215 select FB_TILEBLITTING
1216 select FB_MACMODES if PPC_PMAC
1218 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1219 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1220 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1221 Matrox G400, G450 or G550 card in your box.
1223 To compile this driver as a module, choose M here: the
1224 module will be called matroxfb.
1226 You can pass several parameters to the driver at boot time or at
1227 module load time. The parameters look like "video=matroxfb:XXX", and
1228 are described in <file:Documentation/fb/matroxfb.txt>.
1230 config FB_MATROX_MILLENIUM
1231 bool "Millennium I/II support"
1232 depends on FB_MATROX
1234 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1235 video card. If you select "Advanced lowlevel driver options" below,
1236 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1237 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1238 also use font widths different from 8.
1240 config FB_MATROX_MYSTIQUE
1241 bool "Mystique support"
1242 depends on FB_MATROX
1244 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1245 video card. If you select "Advanced lowlevel driver options" below,
1246 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1247 packed pixel and 32 bpp packed pixel. You can also use font widths
1251 bool "G100/G200/G400/G450/G550 support"
1252 depends on FB_MATROX
1254 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1255 video card. If you select "Advanced lowlevel driver options", you
1256 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1257 pixel and 32 bpp packed pixel. You can also use font widths
1260 If you need support for G400 secondary head, you must say Y to
1261 "Matrox I2C support" and "G400 second head support" right below.
1262 G450/G550 secondary head and digital output are supported without
1265 The driver starts in monitor mode. You must use the matroxset tool
1266 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1267 swap primary and secondary head outputs, or to change output mode.
1268 Secondary head driver always start in 640x480 resolution and you
1269 must use fbset to change it.
1271 Do not forget that second head supports only 16 and 32 bpp
1272 packed pixels, so it is a good idea to compile them into the kernel
1273 too. You can use only some font widths, as the driver uses generic
1274 painting procedures (the secondary head does not use acceleration
1277 G450/G550 hardware can display TV picture only from secondary CRTC,
1278 and it performs no scaling, so picture must have 525 or 625 lines.
1280 config FB_MATROX_I2C
1281 tristate "Matrox I2C support"
1282 depends on FB_MATROX
1285 This drivers creates I2C buses which are needed for accessing the
1286 DDC (I2C) bus present on all Matroxes, an I2C bus which
1287 interconnects Matrox optional devices, like MGA-TVO on G200 and
1288 G400, and the secondary head DDC bus, present on G400 only.
1290 You can say Y or M here if you want to experiment with monitor
1291 detection code. You must say Y or M here if you want to use either
1292 second head of G400 or MGA-TVO on G200 or G400.
1294 If you compile it as module, it will create a module named
1297 config FB_MATROX_MAVEN
1298 tristate "G400 second head support"
1299 depends on FB_MATROX_G && FB_MATROX_I2C
1301 WARNING !!! This support does not work with G450 !!!
1303 Say Y or M here if you want to use a secondary head (meaning two
1304 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1305 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1306 secondary head output is blanked while you are in X. With XFree
1307 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1308 the fbdev driver on first head and the fbdev driver on second head.
1310 If you compile it as module, two modules are created,
1311 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1312 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1313 also load i2c-matroxfb to get it to run.
1315 The driver starts in monitor mode and you must use the matroxset
1317 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1318 PAL or NTSC or to swap primary and secondary head outputs.
1319 Secondary head driver also always start in 640x480 resolution, you
1320 must use fbset to change it.
1322 Also do not forget that second head supports only 16 and 32 bpp
1323 packed pixels, so it is a good idea to compile them into the kernel
1324 too. You can use only some font widths, as the driver uses generic
1325 painting procedures (the secondary head does not use acceleration
1329 tristate "ATI Radeon display support"
1330 depends on FB && PCI
1331 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1332 select FB_MODE_HELPERS
1333 select FB_CFB_FILLRECT
1334 select FB_CFB_COPYAREA
1335 select FB_CFB_IMAGEBLIT
1336 select FB_MACMODES if PPC_OF
1338 Choose this option if you want to use an ATI Radeon graphics card as
1339 a framebuffer device. There are both PCI and AGP versions. You
1340 don't need to choose this to run the Radeon in plain VGA mode.
1342 There is a product page at
1343 http://products.amd.com/en-us/GraphicCardResult.aspx
1345 config FB_RADEON_I2C
1346 bool "DDC/I2C for ATI Radeon support"
1347 depends on FB_RADEON
1351 Say Y here if you want DDC/I2C support for your Radeon board.
1353 config FB_RADEON_BACKLIGHT
1354 bool "Support for backlight control"
1355 depends on FB_RADEON
1358 Say Y here if you want to control the backlight of your display.
1360 config FB_RADEON_DEBUG
1361 bool "Lots of debug output from Radeon driver"
1362 depends on FB_RADEON
1365 Say Y here if you want the Radeon driver to output all sorts
1366 of debugging information to provide to the maintainer when
1367 something goes wrong.
1370 tristate "ATI Rage128 display support"
1371 depends on FB && PCI
1372 select FB_CFB_FILLRECT
1373 select FB_CFB_COPYAREA
1374 select FB_CFB_IMAGEBLIT
1375 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1376 select FB_MACMODES if PPC_PMAC
1378 This driver supports graphics boards with the ATI Rage128 chips.
1379 Say Y if you have such a graphics board and read
1380 <file:Documentation/fb/aty128fb.txt>.
1382 To compile this driver as a module, choose M here: the
1383 module will be called aty128fb.
1385 config FB_ATY128_BACKLIGHT
1386 bool "Support for backlight control"
1387 depends on FB_ATY128
1390 Say Y here if you want to control the backlight of your display.
1393 tristate "ATI Mach64 display support" if PCI || ATARI
1394 depends on FB && !SPARC32
1395 select FB_CFB_FILLRECT
1396 select FB_CFB_COPYAREA
1397 select FB_CFB_IMAGEBLIT
1398 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1399 select FB_MACMODES if PPC
1401 This driver supports graphics boards with the ATI Mach64 chips.
1402 Say Y if you have such a graphics board.
1404 To compile this driver as a module, choose M here: the
1405 module will be called atyfb.
1408 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1409 depends on PCI && FB_ATY
1410 default y if SPARC64 && PCI
1412 Say Y here to support use of ATI's 64-bit Rage boards (or other
1413 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1414 framebuffer device. The ATI product support page for these boards
1415 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1417 config FB_ATY_GENERIC_LCD
1418 bool "Mach64 generic LCD support"
1419 depends on FB_ATY_CT
1421 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1422 Rage XC, or Rage XL chipset.
1425 bool "Mach64 GX support" if PCI
1429 Say Y here to support use of the ATI Mach64 Graphics Expression
1430 board (or other boards based on the Mach64 GX chipset) as a
1431 framebuffer device. The ATI product support page for these boards
1433 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1435 config FB_ATY_BACKLIGHT
1436 bool "Support for backlight control"
1440 Say Y here if you want to control the backlight of your display.
1443 tristate "S3 Trio/Virge support"
1444 depends on FB && PCI
1445 select FB_CFB_FILLRECT
1446 select FB_CFB_COPYAREA
1447 select FB_CFB_IMAGEBLIT
1448 select FB_TILEBLITTING
1451 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1453 Driver for graphics boards with S3 Trio / S3 Virge chip.
1456 bool "DDC for S3 support"
1461 Say Y here if you want DDC support for your S3 graphics card.
1464 tristate "S3 Savage support"
1465 depends on FB && PCI
1466 select FB_MODE_HELPERS
1467 select FB_CFB_FILLRECT
1468 select FB_CFB_COPYAREA
1469 select FB_CFB_IMAGEBLIT
1472 This driver supports notebooks and computers with S3 Savage PCI/AGP
1475 Say Y if you have such a graphics card.
1477 To compile this driver as a module, choose M here; the module
1478 will be called savagefb.
1480 config FB_SAVAGE_I2C
1481 bool "Enable DDC2 Support"
1482 depends on FB_SAVAGE
1485 This enables I2C support for S3 Savage Chipsets. This is used
1486 only for getting EDID information from the attached display
1487 allowing for robust video mode handling and switching.
1489 Because fbdev-2.6 requires that drivers must be able to
1490 independently validate video mode parameters, you should say Y
1493 config FB_SAVAGE_ACCEL
1494 bool "Enable Console Acceleration"
1495 depends on FB_SAVAGE
1498 This option will compile in console acceleration support. If
1499 the resulting framebuffer console has bothersome glitches, then
1503 tristate "SiS/XGI display support"
1504 depends on FB && PCI
1505 select FB_CFB_FILLRECT
1506 select FB_CFB_COPYAREA
1507 select FB_CFB_IMAGEBLIT
1508 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1510 This is the frame buffer device driver for the SiS 300, 315, 330
1511 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1512 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1514 To compile this driver as a module, choose M here; the module
1515 will be called sisfb.
1518 bool "SiS 300 series support"
1521 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1524 bool "SiS 315/330/340 series and XGI support"
1527 Say Y here to support use of the SiS 315, 330 and 340 series
1528 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1529 as XGI V3XT, V5, V8 and Z7.
1532 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1533 depends on FB && PCI && X86
1534 select FB_CFB_FILLRECT
1535 select FB_CFB_COPYAREA
1536 select FB_CFB_IMAGEBLIT
1541 This is the frame buffer device driver for Graphics chips of VIA
1542 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1543 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1545 Say Y if you have a VIA UniChrome graphics board.
1547 To compile this driver as a module, choose M here: the
1548 module will be called viafb.
1552 config FB_VIA_DIRECT_PROCFS
1553 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1557 Allow direct hardware access to some output registers via procfs.
1558 This is dangerous but may provide the only chance to get the
1559 correct output device configuration.
1560 Its use is strongly discouraged.
1562 config FB_VIA_X_COMPATIBILITY
1563 bool "X server compatibility"
1567 This option reduces the functionality (power saving, ...) of the
1568 framebuffer to avoid negative impact on the OpenChrome X server.
1569 If you use any X server other than fbdev you should enable this
1570 otherwise it should be safe to disable it and allow using all
1576 tristate "NeoMagic display support"
1577 depends on FB && PCI
1578 select FB_MODE_HELPERS
1579 select FB_CFB_FILLRECT
1580 select FB_CFB_COPYAREA
1581 select FB_CFB_IMAGEBLIT
1584 This driver supports notebooks with NeoMagic PCI chips.
1585 Say Y if you have such a graphics card.
1587 To compile this driver as a module, choose M here: the
1588 module will be called neofb.
1591 tristate "IMG Kyro support"
1592 depends on FB && PCI
1593 select FB_CFB_FILLRECT
1594 select FB_CFB_COPYAREA
1595 select FB_CFB_IMAGEBLIT
1597 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1600 To compile this driver as a module, choose M here: the
1601 module will be called kyrofb.
1604 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1605 depends on FB && PCI
1606 select FB_CFB_IMAGEBLIT
1607 select FB_CFB_FILLRECT
1608 select FB_CFB_COPYAREA
1609 select FB_MODE_HELPERS
1611 This driver supports graphics boards with the 3Dfx Banshee,
1612 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1613 such a graphics board.
1615 To compile this driver as a module, choose M here: the
1616 module will be called tdfxfb.
1618 config FB_3DFX_ACCEL
1619 bool "3Dfx Acceleration functions"
1622 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1623 device driver with acceleration functions.
1626 bool "Enable DDC/I2C support"
1631 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1634 tristate "3Dfx Voodoo Graphics (sst1) support"
1635 depends on FB && PCI
1636 select FB_CFB_FILLRECT
1637 select FB_CFB_COPYAREA
1638 select FB_CFB_IMAGEBLIT
1640 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1641 Voodoo2 (cvg) based graphics card.
1643 To compile this driver as a module, choose M here: the
1644 module will be called sstfb.
1646 WARNING: Do not use any application that uses the 3D engine
1647 (namely glide) while using this driver.
1648 Please read the <file:Documentation/fb/sstfb.txt> for supported
1649 options and other important info support.
1652 tristate "VIA VT8623 support"
1653 depends on FB && PCI
1654 select FB_CFB_FILLRECT
1655 select FB_CFB_COPYAREA
1656 select FB_CFB_IMAGEBLIT
1657 select FB_TILEBLITTING
1660 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1662 Driver for CastleRock integrated graphics core in the
1663 VIA VT8623 [Apollo CLE266] chipset.
1666 tristate "Trident/CyberXXX/CyberBlade support"
1667 depends on FB && PCI
1668 select FB_CFB_FILLRECT
1669 select FB_CFB_COPYAREA
1670 select FB_CFB_IMAGEBLIT
1672 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1673 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1675 There are also integrated versions of these chips called CyberXXXX,
1676 CyberImage or CyberBlade. These chips are mostly found in laptops
1677 but also on some motherboards including early VIA EPIA motherboards.
1678 For more information, read <file:Documentation/fb/tridentfb.txt>
1680 Say Y if you have such a graphics board.
1682 To compile this driver as a module, choose M here: the
1683 module will be called tridentfb.
1686 tristate "ARK 2000PV support"
1687 depends on FB && PCI
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1691 select FB_TILEBLITTING
1694 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1696 Driver for PCI graphics boards with ARK 2000PV chip
1697 and ICS 5342 RAMDAC.
1700 tristate "Permedia3 support"
1701 depends on FB && PCI
1702 select FB_CFB_FILLRECT
1703 select FB_CFB_COPYAREA
1704 select FB_CFB_IMAGEBLIT
1706 This is the frame buffer device driver for the 3DLabs Permedia3
1707 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1708 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1709 and maybe other boards.
1712 tristate "Fujitsu carmine frame buffer support"
1713 depends on FB && PCI
1714 select FB_CFB_FILLRECT
1715 select FB_CFB_COPYAREA
1716 select FB_CFB_IMAGEBLIT
1718 This is the frame buffer device driver for the Fujitsu Carmine chip.
1719 The driver provides two independent frame buffer devices.
1722 depends on FB_CARMINE
1723 prompt "DRAM timing"
1724 default FB_CARMINE_DRAM_EVAL
1726 config FB_CARMINE_DRAM_EVAL
1727 bool "Eval board timings"
1729 Use timings which work on the eval card.
1731 config CARMINE_DRAM_CUSTOM
1732 bool "Custom board timings"
1734 Use custom board timings.
1738 bool "Au1100 LCD Driver"
1739 depends on (FB = y) && MIPS_ALCHEMY
1740 select FB_CFB_FILLRECT
1741 select FB_CFB_COPYAREA
1742 select FB_CFB_IMAGEBLIT
1744 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1745 various panels and CRTs by passing in kernel cmd line option
1746 au1100fb:panel=<name>.
1749 bool "Au1200/Au1300 LCD Driver"
1750 depends on (FB = y) && MIPS_ALCHEMY
1751 select FB_SYS_FILLRECT
1752 select FB_SYS_COPYAREA
1753 select FB_SYS_IMAGEBLIT
1756 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1757 It can drive various panels and CRTs by passing in kernel cmd line
1758 option au1200fb:panel=<name>.
1761 bool "VIA VT8500 framebuffer support"
1762 depends on (FB = y) && ARM && ARCH_VT8500
1763 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1764 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1765 select FB_SYS_IMAGEBLIT
1766 select FB_MODE_HELPERS
1767 select VIDEOMODE_HELPERS
1769 This is the framebuffer driver for VIA VT8500 integrated LCD
1773 bool "Wondermedia WM8xxx-series frame buffer support"
1774 depends on (FB = y) && ARM && ARCH_VT8500
1775 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1776 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1777 select FB_SYS_IMAGEBLIT
1778 select FB_MODE_HELPERS
1779 select VIDEOMODE_HELPERS
1781 This is the framebuffer driver for WonderMedia WM8xxx-series
1782 integrated LCD controller. This driver covers the WM8505, WM8650
1785 config FB_WMT_GE_ROPS
1786 bool "VT8500/WM8xxx accelerated raster ops support"
1787 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1790 This adds support for accelerated raster operations on the
1791 VIA VT8500 and Wondermedia 85xx series SoCs.
1793 source "drivers/video/fbdev/geode/Kconfig"
1796 tristate "HD64461 Frame Buffer support"
1797 depends on FB && HD64461
1798 select FB_CFB_FILLRECT
1799 select FB_CFB_COPYAREA
1800 select FB_CFB_IMAGEBLIT
1802 This is the frame buffer device driver for the Hitachi HD64461 LCD
1806 bool "PMAG-AA TURBOchannel framebuffer support"
1807 depends on (FB = y) && TC
1808 select FB_CFB_FILLRECT
1809 select FB_CFB_COPYAREA
1810 select FB_CFB_IMAGEBLIT
1812 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1813 used mainly in the MIPS-based DECstation series.
1816 tristate "PMAG-BA TURBOchannel framebuffer support"
1818 select FB_CFB_FILLRECT
1819 select FB_CFB_COPYAREA
1820 select FB_CFB_IMAGEBLIT
1822 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1823 used mainly in the MIPS-based DECstation series.
1826 tristate "PMAGB-B TURBOchannel framebuffer support"
1828 select FB_CFB_FILLRECT
1829 select FB_CFB_COPYAREA
1830 select FB_CFB_IMAGEBLIT
1832 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1833 in the MIPS-based DECstation series. The card is currently only
1834 supported in 1280x1024x8 mode.
1837 bool "Maxine (Personal DECstation) onboard framebuffer support"
1838 depends on (FB = y) && MACH_DECSTATION
1839 select FB_CFB_FILLRECT
1840 select FB_CFB_COPYAREA
1841 select FB_CFB_IMAGEBLIT
1843 Support for the onboard framebuffer (1024x768x8) in the Personal
1844 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1848 bool "G364 frame buffer support"
1849 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1850 select FB_CFB_FILLRECT
1851 select FB_CFB_COPYAREA
1852 select FB_CFB_IMAGEBLIT
1854 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1855 Olivetti M700-10 systems.
1858 bool "Motorola 68328 native frame buffer support"
1859 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1864 Say Y here if you want to support the built-in frame buffer of
1865 the Motorola 68328 CPU family.
1868 tristate "PXA168/910 LCD framebuffer support"
1869 depends on FB && (CPU_PXA168 || CPU_PXA910)
1870 select FB_CFB_FILLRECT
1871 select FB_CFB_COPYAREA
1872 select FB_CFB_IMAGEBLIT
1874 Frame buffer driver for the built-in LCD controller in the Marvell
1878 tristate "PXA LCD framebuffer support"
1879 depends on FB && ARCH_PXA
1880 select FB_CFB_FILLRECT
1881 select FB_CFB_COPYAREA
1882 select FB_CFB_IMAGEBLIT
1884 Frame buffer driver for the built-in LCD controller in the Intel
1887 This driver is also available as a module ( = code which can be
1888 inserted and removed from the running kernel whenever you want). The
1889 module will be called pxafb. If you want to compile it as a module,
1890 say M here and read <file:Documentation/kbuild/modules.txt>.
1894 config FB_PXA_OVERLAY
1895 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1897 depends on FB_PXA && (PXA27x || PXA3xx)
1899 config FB_PXA_SMARTPANEL
1900 bool "PXA Smartpanel LCD support"
1904 config FB_PXA_PARAMETERS
1905 bool "PXA LCD command line parameters"
1909 Enable the use of kernel command line or module parameters
1910 to configure the physical properties of the LCD panel when
1911 using the PXA LCD driver.
1913 This option allows you to override the panel parameters
1914 supplied by the platform in order to support multiple
1915 different models of flatpanel. If you will only be using a
1916 single model of flatpanel then you can safely leave this
1919 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1922 tristate "PXA3xx 2D graphics accelerator driver"
1925 Kernelspace driver for the 2D graphics controller unit (GCU)
1926 found on PXA3xx processors. There is a counterpart driver in the
1927 DirectFB suite, see http://www.directfb.org/
1929 If you compile this as a module, it will be called pxa3xx_gcu.
1932 tristate "2700G LCD framebuffer support"
1933 depends on FB && ARCH_PXA
1934 select FB_CFB_FILLRECT
1935 select FB_CFB_COPYAREA
1936 select FB_CFB_IMAGEBLIT
1938 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1942 bool "Enable debugging info via debugfs"
1943 depends on FB_MBX && DEBUG_FS
1946 Enable this if you want debugging information using the debug
1947 filesystem (debugfs)
1952 tristate "Freescale DIU framebuffer support"
1953 depends on FB && FSL_SOC
1954 select FB_MODE_HELPERS
1955 select FB_CFB_FILLRECT
1956 select FB_CFB_COPYAREA
1957 select FB_CFB_IMAGEBLIT
1958 select PPC_LIB_RHEAP
1960 Framebuffer driver for the Freescale SoC DIU
1963 tristate "W100 frame buffer support"
1964 depends on FB && ARCH_PXA
1965 select FB_CFB_FILLRECT
1966 select FB_CFB_COPYAREA
1967 select FB_CFB_IMAGEBLIT
1969 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1970 It can also drive the w3220 chip found on iPAQ hx4700.
1972 This driver is also available as a module ( = code which can be
1973 inserted and removed from the running kernel whenever you want). The
1974 module will be called w100fb. If you want to compile it as a module,
1975 say M here and read <file:Documentation/kbuild/modules.txt>.
1979 config FB_SH_MOBILE_LCDC
1980 tristate "SuperH Mobile LCDC framebuffer support"
1981 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1982 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1983 select FB_SYS_FILLRECT
1984 select FB_SYS_COPYAREA
1985 select FB_SYS_IMAGEBLIT
1987 select FB_DEFERRED_IO
1989 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1991 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1993 config FB_SH_MOBILE_HDMI
1994 tristate "SuperH Mobile HDMI controller support"
1995 depends on FB_SH_MOBILE_LCDC
1996 select FB_MODE_HELPERS
2001 Driver for the on-chip SH-Mobile HDMI controller.
2004 tristate "Toshiba Mobile IO FrameBuffer support"
2005 depends on FB && (MFD_TMIO || COMPILE_TEST)
2006 select FB_CFB_FILLRECT
2007 select FB_CFB_COPYAREA
2008 select FB_CFB_IMAGEBLIT
2010 Frame buffer driver for the Toshiba Mobile IO integrated as found
2011 on the Sharp SL-6000 series
2013 This driver is also available as a module ( = code which can be
2014 inserted and removed from the running kernel whenever you want). The
2015 module will be called tmiofb. If you want to compile it as a module,
2016 say M here and read <file:Documentation/kbuild/modules.txt>.
2020 config FB_TMIO_ACCELL
2021 bool "tmiofb acceleration"
2026 tristate "Samsung S3C framebuffer support"
2027 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
2028 ARCH_S5PV210 || ARCH_EXYNOS)
2029 select FB_CFB_FILLRECT
2030 select FB_CFB_COPYAREA
2031 select FB_CFB_IMAGEBLIT
2033 Frame buffer driver for the built-in FB controller in the Samsung
2034 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2035 and the S3C64XX series such as the S3C6400 and S3C6410.
2037 These chips all have the same basic framebuffer design with the
2038 actual capabilities depending on the chip. For instance the S3C6400
2039 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2040 currently only have two.
2042 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2044 config FB_S3C_DEBUG_REGWRITE
2045 bool "Debug register writes"
2048 Show all register writes via pr_debug()
2051 tristate "S3C2410 LCD framebuffer support"
2052 depends on FB && ARCH_S3C24XX
2053 select FB_CFB_FILLRECT
2054 select FB_CFB_COPYAREA
2055 select FB_CFB_IMAGEBLIT
2057 Frame buffer driver for the built-in LCD controller in the Samsung
2060 This driver is also available as a module ( = code which can be
2061 inserted and removed from the running kernel whenever you want). The
2062 module will be called s3c2410fb. If you want to compile it as a module,
2063 say M here and read <file:Documentation/kbuild/modules.txt>.
2066 config FB_S3C2410_DEBUG
2067 bool "S3C2410 lcd debug messages"
2068 depends on FB_S3C2410
2070 Turn on debugging messages. Note that you can set/unset at run time
2074 tristate "NUC900 LCD framebuffer support"
2075 depends on FB && ARCH_W90X900
2076 select FB_CFB_FILLRECT
2077 select FB_CFB_COPYAREA
2078 select FB_CFB_IMAGEBLIT
2080 Frame buffer driver for the built-in LCD controller in the Nuvoton
2083 config GPM1040A0_320X240
2084 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2085 depends on FB_NUC900
2088 tristate "Silicon Motion SM501 framebuffer support"
2089 depends on FB && MFD_SM501
2090 select FB_CFB_FILLRECT
2091 select FB_CFB_COPYAREA
2092 select FB_CFB_IMAGEBLIT
2094 Frame buffer driver for the CRT and LCD controllers in the Silicon
2097 This driver is also available as a module ( = code which can be
2098 inserted and removed from the running kernel whenever you want). The
2099 module will be called sm501fb. If you want to compile it as a module,
2100 say M here and read <file:Documentation/kbuild/modules.txt>.
2105 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2106 depends on FB && USB
2107 select FB_MODE_HELPERS
2108 select FB_SYS_FILLRECT
2109 select FB_SYS_COPYAREA
2110 select FB_SYS_IMAGEBLIT
2112 select FB_DEFERRED_IO
2114 This is a kernel framebuffer driver for SMSC UFX USB devices.
2115 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2116 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2118 To compile as a module, choose M here: the module name is smscufx.
2121 tristate "Displaylink USB Framebuffer support"
2122 depends on FB && USB
2123 select FB_MODE_HELPERS
2124 select FB_SYS_FILLRECT
2125 select FB_SYS_COPYAREA
2126 select FB_SYS_IMAGEBLIT
2128 select FB_DEFERRED_IO
2130 This is a kernel framebuffer driver for DisplayLink USB devices.
2131 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2132 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2133 To compile as a module, choose M here: the module name is udlfb.
2135 config FB_IBM_GXT4500
2136 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2137 depends on FB && PPC
2138 select FB_CFB_FILLRECT
2139 select FB_CFB_COPYAREA
2140 select FB_CFB_IMAGEBLIT
2142 Say Y here to enable support for the IBM GXT4000P/6000P and
2143 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2144 found on some IBM System P (pSeries) machines. This driver
2145 doesn't use Geometry Engine GT1000.
2148 tristate "PS3 GPU framebuffer driver"
2149 depends on FB && PS3_PS3AV
2150 select FB_SYS_FILLRECT
2151 select FB_SYS_COPYAREA
2152 select FB_SYS_IMAGEBLIT
2154 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2156 Include support for the virtual frame buffer in the PS3 platform.
2158 config FB_PS3_DEFAULT_SIZE_M
2159 int "PS3 default frame buffer size (in MiB)"
2163 This is the default size (in MiB) of the virtual frame buffer in
2165 The default value can be overridden on the kernel command line
2166 using the "ps3fb" option (e.g. "ps3fb=9M");
2169 tristate "Xilinx frame buffer support"
2170 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2171 select FB_CFB_FILLRECT
2172 select FB_CFB_COPYAREA
2173 select FB_CFB_IMAGEBLIT
2175 Include support for the Xilinx ML300/ML403 reference design
2176 framebuffer. ML300 carries a 640*480 LCD display on the board,
2177 ML403 uses a standard DB15 VGA connector.
2180 tristate "Goldfish Framebuffer"
2181 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2182 select FB_CFB_FILLRECT
2183 select FB_CFB_COPYAREA
2184 select FB_CFB_IMAGEBLIT
2186 Framebuffer driver for Goldfish Virtual Platform
2189 tristate "Cobalt server LCD frame buffer support"
2190 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2193 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2194 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2195 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2196 select FB_CFB_FILLRECT
2197 select FB_CFB_COPYAREA
2198 select FB_CFB_IMAGEBLIT
2200 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2201 (D)STN/TFT LCD Controller.
2202 Supports display resolutions up to 1024x1024 pixel, grayscale and
2203 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2204 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2205 panels <= 320 pixel horizontal resolution.
2208 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2209 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2210 select FB_CFB_FILLRECT
2211 select FB_CFB_COPYAREA
2212 select FB_CFB_IMAGEBLIT
2213 select FB_CFB_REV_PIXELS_IN_BYTE
2214 select FB_MODE_HELPERS
2215 select VIDEOMODE_HELPERS
2217 This is the frame buffer device driver for the TI LCD controller
2218 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2222 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2224 select FB_SYS_FILLRECT
2225 select FB_SYS_COPYAREA
2226 select FB_SYS_IMAGEBLIT
2229 This is a `virtual' frame buffer device. It operates on a chunk of
2230 unswappable kernel memory instead of on the memory of a graphics
2231 board. This means you cannot see any output sent to this frame
2232 buffer device, while it does consume precious memory. The main use
2233 of this frame buffer device is testing and debugging the frame
2234 buffer subsystem. Do NOT enable it for normal systems! To protect
2235 the innocent, it has to be enabled explicitly at boot time using the
2236 kernel option `video=vfb:'.
2238 To compile this driver as a module, choose M here: the
2239 module will be called vfb. In order to load it, you must use
2240 the vfb_enable=1 option.
2244 config XEN_FBDEV_FRONTEND
2245 tristate "Xen virtual frame buffer support"
2246 depends on FB && XEN
2247 select FB_SYS_FILLRECT
2248 select FB_SYS_COPYAREA
2249 select FB_SYS_IMAGEBLIT
2251 select FB_DEFERRED_IO
2252 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2253 select XEN_XENBUS_FRONTEND
2256 This driver implements the front-end of the Xen virtual
2257 frame buffer driver. It communicates with a back-end
2261 tristate "E-Ink Metronome/8track controller support"
2263 select FB_SYS_FILLRECT
2264 select FB_SYS_COPYAREA
2265 select FB_SYS_IMAGEBLIT
2267 select FB_DEFERRED_IO
2269 This driver implements support for the E-Ink Metronome
2270 controller. The pre-release name for this device was 8track
2271 and could also have been called by some vendors as PVI-nnnn.
2274 tristate "Fujitsu MB862xx GDC support"
2276 depends on PCI || (OF && PPC)
2277 select FB_CFB_FILLRECT
2278 select FB_CFB_COPYAREA
2279 select FB_CFB_IMAGEBLIT
2281 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2284 prompt "GDC variant"
2285 depends on FB_MB862XX
2287 config FB_MB862XX_PCI_GDC
2288 bool "Carmine/Coral-P(A) GDC"
2291 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2292 PCI graphics controller devices.
2294 config FB_MB862XX_LIME
2296 depends on OF && PPC
2297 select FB_FOREIGN_ENDIAN
2298 select FB_LITTLE_ENDIAN
2300 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2304 config FB_MB862XX_I2C
2305 bool "Support I2C bus on MB862XX GDC"
2306 depends on FB_MB862XX && I2C
2307 depends on FB_MB862XX=m || I2C=y
2310 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2311 driver to support accessing I2C devices on controller's I2C bus.
2312 These are usually some video decoder chips.
2315 tristate "EP93XX frame buffer support"
2316 depends on FB && ARCH_EP93XX
2317 select FB_CFB_FILLRECT
2318 select FB_CFB_COPYAREA
2319 select FB_CFB_IMAGEBLIT
2321 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2322 This driver is also available as a module. The module will be called
2325 config FB_PRE_INIT_FB
2326 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2327 depends on FB && FB_MB862XX_LIME
2329 Select this option if display contents should be inherited as set by
2333 tristate "MSM Framebuffer support"
2334 depends on FB && ARCH_MSM
2335 select FB_CFB_FILLRECT
2336 select FB_CFB_COPYAREA
2337 select FB_CFB_IMAGEBLIT
2340 tristate "MX3 Framebuffer support"
2341 depends on FB && MX3_IPU
2342 select FB_CFB_FILLRECT
2343 select FB_CFB_COPYAREA
2344 select FB_CFB_IMAGEBLIT
2345 select BACKLIGHT_CLASS_DEVICE
2348 This is a framebuffer device for the i.MX31 LCD Controller. So
2349 far only synchronous displays are supported. If you plan to use
2350 an LCD display with your i.MX31 system, say Y here.
2352 config FB_BROADSHEET
2353 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2355 select FB_SYS_FILLRECT
2356 select FB_SYS_COPYAREA
2357 select FB_SYS_IMAGEBLIT
2359 select FB_DEFERRED_IO
2361 This driver implements support for the E-Ink Broadsheet
2362 controller. The release name for this device was Epson S1D13521
2363 and could also have been called by other names when coupled with
2367 tristate "AUO-K190X EPD controller support"
2369 select FB_SYS_FILLRECT
2370 select FB_SYS_COPYAREA
2371 select FB_SYS_IMAGEBLIT
2373 select FB_DEFERRED_IO
2375 Provides support for epaper controllers from the K190X series
2376 of AUO. These controllers can be used to drive epaper displays
2379 This option enables the common support, shared by the individual
2380 controller drivers. You will also have to enable the driver
2381 for the controller type used in your device.
2384 tristate "AUO-K1900 EPD controller support"
2385 depends on FB && FB_AUO_K190X
2387 This driver implements support for the AUO K1900 epd-controller.
2388 This controller can drive Sipix epaper displays but can only do
2389 serial updates, reducing the number of possible frames per second.
2392 tristate "AUO-K1901 EPD controller support"
2393 depends on FB && FB_AUO_K190X
2395 This driver implements support for the AUO K1901 epd-controller.
2396 This controller can drive Sipix epaper displays and supports
2397 concurrent updates, making higher frames per second possible.
2400 tristate "JZ4740 LCD framebuffer support"
2401 depends on FB && MACH_JZ4740
2402 select FB_SYS_FILLRECT
2403 select FB_SYS_COPYAREA
2404 select FB_SYS_IMAGEBLIT
2406 Framebuffer support for the JZ4740 SoC.
2409 tristate "MXS LCD framebuffer support"
2410 depends on FB && ARCH_MXS
2411 select FB_CFB_FILLRECT
2412 select FB_CFB_COPYAREA
2413 select FB_CFB_IMAGEBLIT
2414 select FB_MODE_HELPERS
2415 select VIDEOMODE_HELPERS
2417 Framebuffer support for the MXS SoC.
2419 config FB_PUV3_UNIGFX
2420 tristate "PKUnity v3 Unigfx framebuffer support"
2421 depends on FB && UNICORE32 && ARCH_PUV3
2422 select FB_SYS_FILLRECT
2423 select FB_SYS_COPYAREA
2424 select FB_SYS_IMAGEBLIT
2427 Choose this option if you want to use the Unigfx device as a
2428 framebuffer device. Without the support of PCI & AGP.
2431 tristate "Microsoft Hyper-V Synthetic Video support"
2432 depends on FB && HYPERV
2433 select FB_CFB_FILLRECT
2434 select FB_CFB_COPYAREA
2435 select FB_CFB_IMAGEBLIT
2437 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2440 bool "Simple framebuffer support"
2442 select FB_CFB_FILLRECT
2443 select FB_CFB_COPYAREA
2444 select FB_CFB_IMAGEBLIT
2446 Say Y if you want support for a simple frame-buffer.
2448 This driver assumes that the display hardware has been initialized
2449 before the kernel boots, and the kernel will simply render to the
2450 pre-allocated frame buffer surface.
2452 Configuration re: surface address, size, and format must be provided
2453 through device tree, or plain old platform data.
2455 source "drivers/video/fbdev/omap/Kconfig"
2456 source "drivers/video/fbdev/omap2/Kconfig"
2457 source "drivers/video/fbdev/exynos/Kconfig"
2458 source "drivers/video/fbdev/mmp/Kconfig"
2460 config FB_SH_MOBILE_MERAM
2461 tristate "SuperH Mobile MERAM read ahead support"
2462 depends on (SUPERH || ARCH_SHMOBILE)
2463 select GENERIC_ALLOCATOR
2465 Enable MERAM support for the SuperH controller.
2467 This will allow for caching of the framebuffer to provide more
2468 reliable access under heavy main memory bus traffic situations.
2469 Up to 4 memory channels can be configured, allowing 4 RGB or
2470 2 YCbCr framebuffers to be configured.
2473 tristate "Solomon SSD1307 framebuffer support"
2474 depends on FB && I2C
2478 select FB_SYS_FILLRECT
2479 select FB_SYS_COPYAREA
2480 select FB_SYS_IMAGEBLIT
2481 select FB_DEFERRED_IO
2484 This driver implements support for the Solomon SSD1307
2485 OLED controller over I2C.