5 menu "Graphics support"
13 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
15 config SH_LCD_MIPI_DSI
18 source "drivers/char/agp/Kconfig"
20 source "drivers/gpu/vga/Kconfig"
22 source "drivers/gpu/drm/Kconfig"
28 config VIDEO_OUTPUT_CONTROL
29 tristate "Lowlevel video output switch controls"
31 This framework adds support for low-level control of the video
34 config VIDEOMODE_HELPERS
41 tristate "Support for frame buffer devices"
43 The frame buffer device provides an abstraction for the graphics
44 hardware. It represents the frame buffer of some video hardware and
45 allows application software to access the graphics hardware through
46 a well-defined interface, so the software doesn't need to know
47 anything about the low-level (hardware register) stuff.
49 Frame buffer devices work identically across the different
50 architectures supported by Linux and make the implementation of
51 application programs easier and more portable; at this point, an X
52 server exists which uses the frame buffer device exclusively.
53 On several non-X86 architectures, the frame buffer device is the
54 only way to use the graphics hardware.
56 The device is accessed through special device nodes, usually located
57 in the /dev directory, i.e. /dev/fb*.
59 You need an utility program called fbset to make full use of frame
60 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
61 and the Framebuffer-HOWTO at
62 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
65 Say Y here and to the driver for your graphics board below if you
66 are compiling a kernel for a non-x86 architecture.
68 If you are compiling for the x86 architecture, you can say Y if you
69 want to play with it, but it is not essential. Please note that
70 running graphical applications that directly touch the hardware
71 (e.g. an accelerated X server) and that are not frame buffer
72 device-aware may cause unexpected results. If unsure, say N.
75 bool "Enable firmware EDID"
79 This enables access to the EDID transferred from the firmware.
80 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
81 transfers do not work for your driver and if you are using
82 nvidiafb, i810fb or savagefb.
84 In general, choosing Y for this option is safe. If you
85 experience extremely long delays while booting before you get
86 something on your display, try setting this to N. Matrox cards in
87 combination with certain motherboards and monitors are known to
88 suffer from this problem.
97 config FB_BOOT_VESA_SUPPORT
102 If true, at least one selected framebuffer driver can take advantage
103 of VESA video modes set at an early boot stage via the vga= parameter.
105 config FB_CFB_FILLRECT
110 Include the cfb_fillrect function for generic software rectangle
111 filling. This is used by drivers that don't provide their own
112 (accelerated) version.
114 config FB_CFB_COPYAREA
119 Include the cfb_copyarea function for generic software area copying.
120 This is used by drivers that don't provide their own (accelerated)
123 config FB_CFB_IMAGEBLIT
128 Include the cfb_imageblit function for generic software image
129 blitting. This is used by drivers that don't provide their own
130 (accelerated) version.
132 config FB_CFB_REV_PIXELS_IN_BYTE
137 Allow generic frame-buffer functions to work on displays with 1, 2
138 and 4 bits per pixel depths which has opposite order of pixels in
139 byte order to bytes in long order.
141 config FB_SYS_FILLRECT
146 Include the sys_fillrect function for generic software rectangle
147 filling. This is used by drivers that don't provide their own
148 (accelerated) version and the framebuffer is in system RAM.
150 config FB_SYS_COPYAREA
155 Include the sys_copyarea function for generic software area copying.
156 This is used by drivers that don't provide their own (accelerated)
157 version and the framebuffer is in system RAM.
159 config FB_SYS_IMAGEBLIT
164 Include the sys_imageblit function for generic software image
165 blitting. This is used by drivers that don't provide their own
166 (accelerated) version and the framebuffer is in system RAM.
168 menuconfig FB_FOREIGN_ENDIAN
169 bool "Framebuffer foreign endianness support"
172 This menu will let you enable support for the framebuffers with
173 non-native endianness (e.g. Little-Endian framebuffer on a
174 Big-Endian machine). Most probably you don't have such hardware,
175 so it's safe to say "n" here.
178 prompt "Choice endianness support"
179 depends on FB_FOREIGN_ENDIAN
181 config FB_BOTH_ENDIAN
182 bool "Support for Big- and Little-Endian framebuffers"
185 bool "Support for Big-Endian framebuffers only"
187 config FB_LITTLE_ENDIAN
188 bool "Support for Little-Endian framebuffers only"
197 config FB_DEFERRED_IO
204 depends on FB_DEFERRED_IO
211 Common utility functions useful to fbdev drivers of VGA-based
222 select BACKLIGHT_LCD_SUPPORT
223 select BACKLIGHT_CLASS_DEVICE
226 config FB_MODE_HELPERS
227 bool "Enable Video Mode Handling Helpers"
231 This enables functions for handling video modes using the
232 Generalized Timing Formula and the EDID parser. A few drivers rely
233 on this feature such as the radeonfb, rivafb, and the i810fb. If
234 your driver does not take advantage of this feature, choosing Y will
235 just increase the kernel size by about 5K.
237 config FB_TILEBLITTING
238 bool "Enable Tile Blitting Support"
242 This enables tile blitting. Tile blitting is a drawing technique
243 where the screen is divided into rectangular sections (tiles), whereas
244 the standard blitting divides the screen into pixels. Because the
245 default drawing element is a tile, drawing functions will be passed
246 parameters in terms of number of tiles instead of number of pixels.
247 For example, to draw a single character, instead of using bitmaps,
248 an index to an array of bitmaps will be used. To clear or move a
249 rectangular section of a screen, the rectangle will be described in
250 terms of number of tiles in the x- and y-axis.
252 This is particularly important to one driver, matroxfb. If
255 comment "Frame buffer hardware drivers"
259 tristate "Aeroflex Gaisler framebuffer support"
260 depends on FB && SPARC
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
268 tristate "Cirrus Logic support"
269 depends on FB && (ZORRO || PCI)
270 select FB_CFB_FILLRECT
271 select FB_CFB_COPYAREA
272 select FB_CFB_IMAGEBLIT
274 This enables support for Cirrus Logic GD542x/543x based boards on
275 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
277 If you have a PCI-based system, this enables support for these
278 chips: GD-543x, GD-544x, GD-5480.
280 Please read the file <file:Documentation/fb/cirrusfb.txt>.
282 Say N unless you have such a graphics board or plan to get one
283 before you next recompile the kernel.
286 tristate "Permedia2 support"
287 depends on FB && ((AMIGA && BROKEN) || PCI)
288 select FB_CFB_FILLRECT
289 select FB_CFB_COPYAREA
290 select FB_CFB_IMAGEBLIT
292 This is the frame buffer device driver for cards based on
293 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
294 The driver was tested on the following cards:
295 Diamond FireGL 1000 PRO AGP
296 ELSA Gloria Synergy PCI
297 Appian Jeronimo PRO (both heads) PCI
298 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
299 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
300 ASK Graphic Blaster Exxtreme AGP
302 To compile this driver as a module, choose M here: the
303 module will be called pm2fb.
305 config FB_PM2_FIFO_DISCONNECT
306 bool "enable FIFO disconnect feature"
307 depends on FB_PM2 && PCI
309 Support the Permedia2 FIFO disconnect feature.
312 tristate "ARM PrimeCell PL110 support"
313 depends on FB && ARM && ARM_AMBA
314 select FB_CFB_FILLRECT
315 select FB_CFB_COPYAREA
316 select FB_CFB_IMAGEBLIT
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.
328 bool "Acorn VIDC support"
329 depends on (FB = y) && ARM && ARCH_ACORN
330 select FB_CFB_FILLRECT
331 select FB_CFB_COPYAREA
332 select FB_CFB_IMAGEBLIT
334 This is the frame buffer device driver for the Acorn VIDC graphics
335 hardware found in Acorn RISC PCs and other ARM-based machines. If
339 bool "CLPS711X LCD support"
340 depends on (FB = y) && ARM && ARCH_CLPS711X
341 select FB_CFB_FILLRECT
342 select FB_CFB_COPYAREA
343 select FB_CFB_IMAGEBLIT
345 Say Y to enable the Framebuffer driver for the CLPS7111 and
349 bool "SA-1100 LCD support"
350 depends on (FB = y) && ARM && ARCH_SA1100
351 select FB_CFB_FILLRECT
352 select FB_CFB_COPYAREA
353 select FB_CFB_IMAGEBLIT
355 This is a framebuffer device for the SA-1100 LCD Controller.
356 See <http://www.linux-fbdev.org/> for information on framebuffer
359 If you plan to use the LCD display with your SA-1100 system, say
363 tristate "Freescale i.MX1/21/25/27 LCD support"
364 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
365 select FB_CFB_FILLRECT
366 select FB_CFB_COPYAREA
367 select FB_CFB_IMAGEBLIT
370 tristate "CyberPro 2000/2010/5000 support"
371 depends on FB && PCI && (BROKEN || !SPARC64)
372 select FB_CFB_FILLRECT
373 select FB_CFB_COPYAREA
374 select FB_CFB_IMAGEBLIT
376 This enables support for the Integraphics CyberPro 20x0 and 5000
377 VGA chips used in the Rebel.com Netwinder and other machines.
378 Say Y if you have a NetWinder or a graphics card containing this
379 device, otherwise say N.
381 config FB_CYBER2000_DDC
382 bool "DDC for CyberPro support"
383 depends on FB_CYBER2000
387 Say Y here if you want DDC support for your CyberPro graphics
388 card. This is only I2C bus support, driver does not use EDID.
390 config FB_CYBER2000_I2C
391 bool "CyberPro 2000/2010/5000 I2C support"
392 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
395 Enable support for the I2C video decoder interface on the
396 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
397 on the Netwinder machines for the SAA7111 video capture.
401 depends on (FB = y) && APOLLO
403 select FB_CFB_FILLRECT
404 select FB_CFB_IMAGEBLIT
408 depends on (FB = y) && Q40
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
415 tristate "Amiga native chipset support"
416 depends on FB && AMIGA
418 This is the frame buffer device driver for the builtin graphics
419 chipset found in Amigas.
421 To compile this driver as a module, choose M here: the
422 module will be called amifb.
425 bool "Amiga OCS chipset support"
428 This enables support for the original Agnus and Denise video chips,
429 found in the Amiga 1000 and most A500's and A2000's. If you intend
430 to run Linux on any of these systems, say Y; otherwise say N.
433 bool "Amiga ECS chipset support"
436 This enables support for the Enhanced Chip Set, found in later
437 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
438 you intend to run Linux on any of these systems, say Y; otherwise
442 bool "Amiga AGA chipset support"
445 This enables support for the Advanced Graphics Architecture (also
446 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
447 and CD32. If you intend to run Linux on any of these systems, say Y;
451 bool "Amiga FrameMaster II/Rainbow II support"
452 depends on (FB = y) && ZORRO
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
457 This is the frame buffer device driver for the Amiga FrameMaster
458 card from BSC (exhibited 1992 but not shipped as a CBM product).
461 tristate "Arc Monochrome LCD board support"
463 select FB_SYS_FILLRECT
464 select FB_SYS_COPYAREA
465 select FB_SYS_IMAGEBLIT
468 This enables support for the Arc Monochrome LCD board. The board
469 is based on the KS-108 lcd controller and is typically a matrix
470 of 2*n chips. This driver was tested with a 128x64 panel. This
471 driver supports it for use with x86 SBCs through a 16 bit GPIO
472 interface (8 bit data, 8 bit control). If you anticipate using
473 this driver, say Y or M; otherwise say N. You must specify the
474 GPIO IO address to be used for setting control and data.
477 bool "Atari native chipset support"
478 depends on (FB = y) && ATARI
479 select FB_CFB_FILLRECT
480 select FB_CFB_COPYAREA
481 select FB_CFB_IMAGEBLIT
483 This is the frame buffer device driver for the builtin graphics
484 chipset found in Ataris.
487 bool "Open Firmware frame buffer device support"
488 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
494 Say Y if you want support with Open Firmware for your graphics
498 bool "Apple \"control\" display support"
499 depends on (FB = y) && PPC_PMAC && PPC32
500 select FB_CFB_FILLRECT
501 select FB_CFB_COPYAREA
502 select FB_CFB_IMAGEBLIT
505 This driver supports a frame buffer for the graphics adapter in the
506 Power Macintosh 7300 and others.
509 bool "Apple \"platinum\" display support"
510 depends on (FB = y) && PPC_PMAC && PPC32
511 select FB_CFB_FILLRECT
512 select FB_CFB_COPYAREA
513 select FB_CFB_IMAGEBLIT
516 This driver supports a frame buffer for the "platinum" graphics
517 adapter in some Power Macintoshes.
520 bool "Apple \"valkyrie\" display support"
521 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
522 select FB_CFB_FILLRECT
523 select FB_CFB_COPYAREA
524 select FB_CFB_IMAGEBLIT
527 This driver supports a frame buffer for the "valkyrie" graphics
528 adapter in some Power Macintoshes.
531 bool "Chips 65550 display support"
532 depends on (FB = y) && PPC32 && PCI
533 select FB_CFB_FILLRECT
534 select FB_CFB_COPYAREA
535 select FB_CFB_IMAGEBLIT
537 This is the frame buffer device driver for the Chips & Technologies
538 65550 graphics chip in PowerBooks.
541 bool "Asiliant (Chips) 69000 display support"
542 depends on (FB = y) && PCI
543 select FB_CFB_FILLRECT
544 select FB_CFB_COPYAREA
545 select FB_CFB_IMAGEBLIT
547 This is the frame buffer device driver for the Asiliant 69030 chipset
550 bool "IMS Twin Turbo display support"
551 depends on (FB = y) && PCI
552 select FB_CFB_IMAGEBLIT
553 select FB_MACMODES if PPC
555 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
556 many Macintosh and compatible computers.
559 tristate "VGA 16-color graphics support"
560 depends on FB && (X86 || PPC)
561 select FB_CFB_FILLRECT
562 select FB_CFB_COPYAREA
563 select FB_CFB_IMAGEBLIT
565 select FONT_8x16 if FRAMEBUFFER_CONSOLE
567 This is the frame buffer device driver for VGA 16 color graphic
568 cards. Say Y if you have such a card.
570 To compile this driver as a module, choose M here: the
571 module will be called vga16fb.
573 config FB_BF54X_LQ043
574 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
575 depends on FB && (BF54x) && !BF542
576 select FB_CFB_FILLRECT
577 select FB_CFB_COPYAREA
578 select FB_CFB_IMAGEBLIT
580 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
582 config FB_BFIN_T350MCQB
583 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
584 depends on FB && BLACKFIN
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
590 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
591 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
592 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
594 config FB_BFIN_LQ035Q1
595 tristate "SHARP LQ035Q1DH02 TFT LCD"
596 depends on FB && BLACKFIN && SPI
597 select FB_CFB_FILLRECT
598 select FB_CFB_COPYAREA
599 select FB_CFB_IMAGEBLIT
602 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
603 the Blackfin Landscape LCD EZ-Extender Card.
604 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
605 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
607 To compile this driver as a module, choose M here: the
608 module will be called bfin-lq035q1-fb.
610 config FB_BF537_LQ035
611 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
612 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
613 select FB_CFB_FILLRECT
614 select FB_CFB_COPYAREA
615 select FB_CFB_IMAGEBLIT
618 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
621 To compile this driver as a module, choose M here: the
622 module will be called bf537-lq035.
625 tristate "Blackfin ADV7393 Video encoder"
626 depends on FB && BLACKFIN
628 select FB_CFB_FILLRECT
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
632 This is the framebuffer device for a ADV7393 video encoder
633 attached to a Blackfin on the PPI port.
634 If your Blackfin board has a ADV7393 select Y.
636 To compile this driver as a module, choose M here: the
637 module will be called bfin_adv7393fb.
640 prompt "Video mode support"
641 depends on FB_BFIN_7393
651 bool 'NTSC 640x480 (Experimental)'
654 bool 'PAL 640x480 (Experimental)'
657 bool 'NTSC 720x480 YCbCR input'
660 bool 'PAL 720x576 YCbCR input'
665 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
666 depends on (FB_BFIN_7393)
667 default ADV7393_1XMEM
677 tristate "HP STI frame buffer device support"
678 depends on FB && PARISC
679 select FB_CFB_FILLRECT
680 select FB_CFB_COPYAREA
681 select FB_CFB_IMAGEBLIT
686 STI refers to the HP "Standard Text Interface" which is a set of
687 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
688 Enabling this option will implement the linux framebuffer device
689 using calls to the STI BIOS routines for initialisation.
691 If you enable this option, you will get a planar framebuffer device
692 /dev/fb which will work on the most common HP graphic cards of the
693 NGLE family, including the artist chips (in the 7xx and Bxxx series),
694 HCRX, HCRX24, CRX, CRX24 and VisEG series.
696 It is safe to enable this option, so you should probably say "Y".
699 bool "Generic Macintosh display support"
700 depends on (FB = y) && MAC
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
708 depends on (FB = y) && DIO
709 select FB_CFB_IMAGEBLIT
713 tristate "TGA/SFB+ framebuffer support"
714 depends on FB && (ALPHA || TC)
715 select FB_CFB_FILLRECT
716 select FB_CFB_COPYAREA
717 select FB_CFB_IMAGEBLIT
720 This is the frame buffer device driver for generic TGA and SFB+
721 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
722 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
723 TURBOchannel cards, also known as PMAGD-A, -B and -C.
725 Due to hardware limitations ZLX-E2 and E3 cards are not supported
726 for DECstation 5000/200 systems. Additionally due to firmware
727 limitations these cards may cause troubles with booting DECstation
728 5000/240 and /260 systems, but are fully supported under Linux if
729 you manage to get it going. ;-)
731 Say Y if you have one of those.
734 tristate "Userspace VESA VGA graphics support"
735 depends on FB && CONNECTOR
736 select FB_CFB_FILLRECT
737 select FB_CFB_COPYAREA
738 select FB_CFB_IMAGEBLIT
739 select FB_MODE_HELPERS
741 This is the frame buffer driver for generic VBE 2.0 compliant
742 graphic cards. It can also take advantage of VBE 3.0 features,
743 such as refresh rate adjustment.
745 This driver generally provides more features than vesafb but
746 requires a userspace helper application called 'v86d'. See
747 <file:Documentation/fb/uvesafb.txt> for more information.
752 bool "VESA VGA graphics support"
753 depends on (FB = y) && X86
754 select FB_CFB_FILLRECT
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
757 select FB_BOOT_VESA_SUPPORT
759 This is the frame buffer device driver for generic VESA 2.0
760 compliant graphic cards. The older VESA 1.2 cards are not supported.
761 You will get a boot time penguin logo at no additional cost. Please
762 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
765 bool "EFI-based Framebuffer Support"
766 depends on (FB = y) && X86 && EFI
767 select FB_CFB_FILLRECT
768 select FB_CFB_COPYAREA
769 select FB_CFB_IMAGEBLIT
771 This is the EFI frame buffer device driver. If the firmware on
772 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
773 using the EFI framebuffer as your console.
776 tristate "N411 Apollo/Hecuba devkit support"
777 depends on FB && X86 && MMU
778 select FB_SYS_FILLRECT
779 select FB_SYS_COPYAREA
780 select FB_SYS_IMAGEBLIT
782 select FB_DEFERRED_IO
785 This enables support for the Apollo display controller in its
786 Hecuba form using the n411 devkit.
789 tristate "Hercules mono graphics support"
792 Say Y here if you have a Hercules mono graphics card.
794 To compile this driver as a module, choose M here: the
795 module will be called hgafb.
797 As this card technology is at least 25 years old,
798 most people will answer N here.
801 tristate "SGI Visual Workstation framebuffer support"
802 depends on FB && X86_VISWS
803 select FB_CFB_FILLRECT
804 select FB_CFB_COPYAREA
805 select FB_CFB_IMAGEBLIT
807 SGI Visual Workstation support for framebuffer graphics.
810 bool "SGI Graphics Backend frame buffer support"
811 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
812 select FB_CFB_FILLRECT
813 select FB_CFB_COPYAREA
814 select FB_CFB_IMAGEBLIT
816 This is the frame buffer device driver for SGI Graphics Backend.
817 This chip is used in SGI O2 and Visual Workstation 320/540.
820 int "Video memory size in MB"
824 This is the amount of memory reserved for the framebuffer,
825 which can be any value between 1MB and 8MB.
828 bool "SBUS and UPA framebuffers"
829 depends on (FB = y) && SPARC
831 Say Y if you want support for SBUS or UPA based frame buffer device.
835 depends on (FB = y) && (SPARC && FB_SBUS)
836 select FB_CFB_FILLRECT
837 select FB_CFB_COPYAREA
838 select FB_CFB_IMAGEBLIT
840 This is the frame buffer device driver for the BWtwo frame buffer.
843 bool "CGthree support"
844 depends on (FB = y) && (SPARC && FB_SBUS)
845 select FB_CFB_FILLRECT
846 select FB_CFB_COPYAREA
847 select FB_CFB_IMAGEBLIT
849 This is the frame buffer device driver for the CGthree frame buffer.
852 bool "CGsix (GX,TurboGX) support"
853 depends on (FB = y) && (SPARC && FB_SBUS)
854 select FB_CFB_COPYAREA
855 select FB_CFB_IMAGEBLIT
857 This is the frame buffer device driver for the CGsix (GX, TurboGX)
861 bool "Creator/Creator3D/Elite3D support"
862 depends on FB_SBUS && SPARC64
863 select FB_CFB_COPYAREA
864 select FB_CFB_IMAGEBLIT
866 This is the frame buffer device driver for the Creator, Creator3D,
867 and Elite3D graphics boards.
870 bool "TCX (SS4/SS5 only) support"
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the frame buffer device driver for the TCX 24/8bit frame
880 bool "CGfourteen (SX) support"
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the frame buffer device driver for the CGfourteen frame
887 buffer on Desktop SPARCsystems with the SX graphics option.
890 bool "P9100 (Sparcbook 3 only) support"
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
896 This is the frame buffer device driver for the P9100 card
897 supported on Sparcbook 3 machines.
900 bool "Leo (ZX) support"
902 select FB_CFB_FILLRECT
903 select FB_CFB_COPYAREA
904 select FB_CFB_IMAGEBLIT
906 This is the frame buffer device driver for the SBUS-based Sun ZX
907 (leo) frame buffer cards.
910 bool "IGA 168x display support"
911 depends on (FB = y) && SPARC32
912 select FB_CFB_FILLRECT
913 select FB_CFB_COPYAREA
914 select FB_CFB_IMAGEBLIT
916 This is the framebuffer device for the INTERGRAPHICS 1680 and
917 successor frame buffer cards.
920 bool "Sun XVR-500 3DLABS Wildcat support"
921 depends on (FB = y) && PCI && SPARC64
922 select FB_CFB_FILLRECT
923 select FB_CFB_COPYAREA
924 select FB_CFB_IMAGEBLIT
926 This is the framebuffer device for the Sun XVR-500 and similar
927 graphics cards based upon the 3DLABS Wildcat chipset. The driver
928 only works on sparc64 systems where the system firmware has
929 mostly initialized the card already. It is treated as a
930 completely dumb framebuffer device.
933 bool "Sun XVR-2500 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-2500 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-1000 support"
947 depends on (FB = y) && 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-1000 and similar
953 graphics cards. The driver only works on sparc64 systems where
954 the system firmware has mostly initialized the card already. It
955 is treated as a completely dumb framebuffer device.
958 tristate "NEC PowerVR 2 display support"
959 depends on FB && SH_DREAMCAST
960 select FB_CFB_FILLRECT
961 select FB_CFB_COPYAREA
962 select FB_CFB_IMAGEBLIT
964 Say Y here if you have a PowerVR 2 card in your box. If you plan to
965 run linux on your Dreamcast, you will have to say Y here.
966 This driver may or may not work on other PowerVR 2 cards, but is
967 totally untested. Use at your own risk. If unsure, say N.
969 To compile this driver as a module, choose M here: the
970 module will be called pvr2fb.
972 You can pass several parameters to the driver at boot time or at
973 module load time. The parameters look like "video=pvr2:XXX", where
974 the meaning of XXX can be found at the end of the main source file
975 (<file:drivers/video/pvr2fb.c>). Please see the file
976 <file:Documentation/fb/pvr2fb.txt>.
979 tristate "Epson S1D13XXX framebuffer support"
981 select FB_CFB_FILLRECT
982 select FB_CFB_COPYAREA
983 select FB_CFB_IMAGEBLIT
985 Support for S1D13XXX framebuffer device family (currently only
986 working with S1D13806). Product specs at
987 <http://vdc.epson.com/>
990 tristate "AT91/AT32 LCD Controller support"
991 depends on FB && HAVE_FB_ATMEL
992 select FB_CFB_FILLRECT
993 select FB_CFB_COPYAREA
994 select FB_CFB_IMAGEBLIT
996 This enables support for the AT91/AT32 LCD Controller.
999 bool "Frame Buffer in internal SRAM"
1000 depends on FB_ATMEL && ARCH_AT91SAM9261
1002 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1003 to let frame buffer in external SDRAM.
1006 bool "Use a STN display with AT91/AT32 LCD Controller"
1007 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1010 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1011 Controller. Say N if you want to connect a TFT.
1016 tristate "nVidia Framebuffer Support"
1017 depends on FB && PCI
1018 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1019 select FB_MODE_HELPERS
1020 select FB_CFB_FILLRECT
1021 select FB_CFB_COPYAREA
1022 select FB_CFB_IMAGEBLIT
1026 This driver supports graphics boards with the nVidia chips, TNT
1027 and newer. For very old chipsets, such as the RIVA128, then use
1029 Say Y if you have such a graphics board.
1031 To compile this driver as a module, choose M here: the
1032 module will be called nvidiafb.
1034 config FB_NVIDIA_I2C
1035 bool "Enable DDC Support"
1036 depends on FB_NVIDIA
1039 This enables I2C support for nVidia Chipsets. This is used
1040 only for getting EDID information from the attached display
1041 allowing for robust video mode handling and switching.
1043 Because fbdev-2.6 requires that drivers must be able to
1044 independently validate video mode parameters, you should say Y
1047 config FB_NVIDIA_DEBUG
1048 bool "Lots of debug output"
1049 depends on FB_NVIDIA
1052 Say Y here if you want the nVidia driver to output all sorts
1053 of debugging information to provide to the maintainer when
1054 something goes wrong.
1056 config FB_NVIDIA_BACKLIGHT
1057 bool "Support for backlight control"
1058 depends on FB_NVIDIA
1061 Say Y here if you want to control the backlight of your display.
1064 tristate "nVidia Riva support"
1065 depends on FB && PCI
1066 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1067 select FB_MODE_HELPERS
1068 select FB_CFB_FILLRECT
1069 select FB_CFB_COPYAREA
1070 select FB_CFB_IMAGEBLIT
1074 This driver supports graphics boards with the nVidia Riva/Geforce
1076 Say Y if you have such a graphics board.
1078 To compile this driver as a module, choose M here: the
1079 module will be called rivafb.
1082 bool "Enable DDC Support"
1086 This enables I2C support for nVidia Chipsets. This is used
1087 only for getting EDID information from the attached display
1088 allowing for robust video mode handling and switching.
1090 Because fbdev-2.6 requires that drivers must be able to
1091 independently validate video mode parameters, you should say Y
1094 config FB_RIVA_DEBUG
1095 bool "Lots of debug output"
1099 Say Y here if you want the Riva driver to output all sorts
1100 of debugging information to provide to the maintainer when
1101 something goes wrong.
1103 config FB_RIVA_BACKLIGHT
1104 bool "Support for backlight control"
1108 Say Y here if you want to control the backlight of your display.
1111 tristate "Intel740 support"
1112 depends on FB && PCI
1113 select FB_MODE_HELPERS
1114 select FB_CFB_FILLRECT
1115 select FB_CFB_COPYAREA
1116 select FB_CFB_IMAGEBLIT
1120 This driver supports graphics cards based on Intel740 chip.
1123 tristate "Intel 810/815 support"
1124 depends on FB && PCI && X86_32 && AGP_INTEL
1125 select FB_MODE_HELPERS
1126 select FB_CFB_FILLRECT
1127 select FB_CFB_COPYAREA
1128 select FB_CFB_IMAGEBLIT
1131 This driver supports the on-board graphics built in to the Intel 810
1132 and 815 chipsets. Say Y if you have and plan to use such a board.
1134 To compile this driver as a module, choose M here: the
1135 module will be called i810fb.
1137 For more information, please read
1138 <file:Documentation/fb/intel810.txt>
1141 bool "use VESA Generalized Timing Formula"
1144 If you say Y, then the VESA standard, Generalized Timing Formula
1145 or GTF, will be used to calculate the required video timing values
1146 per video mode. Since the GTF allows nondiscrete timings
1147 (nondiscrete being a range of values as opposed to discrete being a
1148 set of values), you'll be able to use any combination of horizontal
1149 and vertical resolutions, and vertical refresh rates without having
1150 to specify your own timing parameters. This is especially useful
1151 to maximize the performance of an aging display, or if you just
1152 have a display with nonstandard dimensions. A VESA compliant
1153 monitor is recommended, but can still work with non-compliant ones.
1154 If you need or want this, then select this option. The timings may
1155 not be compliant with Intel's recommended values. Use at your own
1158 If you say N, the driver will revert to discrete video timings
1159 using a set recommended by Intel in their documentation.
1164 bool "Enable DDC Support"
1165 depends on FB_I810 && FB_I810_GTF
1170 tristate "Intel LE80578 (Vermilion) support"
1171 depends on FB && PCI && X86
1172 select FB_MODE_HELPERS
1173 select FB_CFB_FILLRECT
1174 select FB_CFB_COPYAREA
1175 select FB_CFB_IMAGEBLIT
1177 This driver supports the LE80578 (Vermilion Range) chipset
1179 config FB_CARILLO_RANCH
1180 tristate "Intel Carillo Ranch support"
1181 depends on FB_LE80578 && FB && PCI && X86
1183 This driver supports the LE80578 (Carillo Ranch) board
1186 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1187 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1188 select FB_MODE_HELPERS
1189 select FB_CFB_FILLRECT
1190 select FB_CFB_COPYAREA
1191 select FB_CFB_IMAGEBLIT
1192 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1193 depends on !DRM_I915
1195 This driver supports the on-board graphics built in to the Intel
1196 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1197 Say Y if you have and plan to use such a board.
1199 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1201 To compile this driver as a module, choose M here: the
1202 module will be called intelfb.
1204 For more information, please read <file:Documentation/fb/intelfb.txt>
1206 config FB_INTEL_DEBUG
1207 bool "Intel driver Debug Messages"
1210 Say Y here if you want the Intel driver to output all sorts
1211 of debugging information to provide to the maintainer when
1212 something goes wrong.
1215 bool "DDC/I2C for Intel framebuffer support"
1220 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1223 tristate "Matrox acceleration"
1224 depends on FB && PCI
1225 select FB_CFB_FILLRECT
1226 select FB_CFB_COPYAREA
1227 select FB_CFB_IMAGEBLIT
1228 select FB_TILEBLITTING
1229 select FB_MACMODES if PPC_PMAC
1231 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1232 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1233 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1234 Matrox G400, G450 or G550 card in your box.
1236 To compile this driver as a module, choose M here: the
1237 module will be called matroxfb.
1239 You can pass several parameters to the driver at boot time or at
1240 module load time. The parameters look like "video=matroxfb:XXX", and
1241 are described in <file:Documentation/fb/matroxfb.txt>.
1243 config FB_MATROX_MILLENIUM
1244 bool "Millennium I/II support"
1245 depends on FB_MATROX
1247 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1248 video card. If you select "Advanced lowlevel driver options" below,
1249 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1250 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1251 also use font widths different from 8.
1253 config FB_MATROX_MYSTIQUE
1254 bool "Mystique support"
1255 depends on FB_MATROX
1257 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1258 video card. If you select "Advanced lowlevel driver options" below,
1259 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1260 packed pixel and 32 bpp packed pixel. You can also use font widths
1264 bool "G100/G200/G400/G450/G550 support"
1265 depends on FB_MATROX
1267 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1268 video card. If you select "Advanced lowlevel driver options", you
1269 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1270 pixel and 32 bpp packed pixel. You can also use font widths
1273 If you need support for G400 secondary head, you must say Y to
1274 "Matrox I2C support" and "G400 second head support" right below.
1275 G450/G550 secondary head and digital output are supported without
1278 The driver starts in monitor mode. You must use the matroxset tool
1279 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1280 swap primary and secondary head outputs, or to change output mode.
1281 Secondary head driver always start in 640x480 resolution and you
1282 must use fbset to change it.
1284 Do not forget that second head supports only 16 and 32 bpp
1285 packed pixels, so it is a good idea to compile them into the kernel
1286 too. You can use only some font widths, as the driver uses generic
1287 painting procedures (the secondary head does not use acceleration
1290 G450/G550 hardware can display TV picture only from secondary CRTC,
1291 and it performs no scaling, so picture must have 525 or 625 lines.
1293 config FB_MATROX_I2C
1294 tristate "Matrox I2C support"
1295 depends on FB_MATROX
1298 This drivers creates I2C buses which are needed for accessing the
1299 DDC (I2C) bus present on all Matroxes, an I2C bus which
1300 interconnects Matrox optional devices, like MGA-TVO on G200 and
1301 G400, and the secondary head DDC bus, present on G400 only.
1303 You can say Y or M here if you want to experiment with monitor
1304 detection code. You must say Y or M here if you want to use either
1305 second head of G400 or MGA-TVO on G200 or G400.
1307 If you compile it as module, it will create a module named
1310 config FB_MATROX_MAVEN
1311 tristate "G400 second head support"
1312 depends on FB_MATROX_G && FB_MATROX_I2C
1314 WARNING !!! This support does not work with G450 !!!
1316 Say Y or M here if you want to use a secondary head (meaning two
1317 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1318 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1319 secondary head output is blanked while you are in X. With XFree
1320 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1321 the fbdev driver on first head and the fbdev driver on second head.
1323 If you compile it as module, two modules are created,
1324 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1325 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1326 also load i2c-matroxfb to get it to run.
1328 The driver starts in monitor mode and you must use the matroxset
1330 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1331 PAL or NTSC or to swap primary and secondary head outputs.
1332 Secondary head driver also always start in 640x480 resolution, you
1333 must use fbset to change it.
1335 Also do not forget that second head supports only 16 and 32 bpp
1336 packed pixels, so it is a good idea to compile them into the kernel
1337 too. You can use only some font widths, as the driver uses generic
1338 painting procedures (the secondary head does not use acceleration
1342 tristate "ATI Radeon display support"
1343 depends on FB && PCI
1344 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1345 select FB_MODE_HELPERS
1346 select FB_CFB_FILLRECT
1347 select FB_CFB_COPYAREA
1348 select FB_CFB_IMAGEBLIT
1349 select FB_MACMODES if PPC_OF
1351 Choose this option if you want to use an ATI Radeon graphics card as
1352 a framebuffer device. There are both PCI and AGP versions. You
1353 don't need to choose this to run the Radeon in plain VGA mode.
1355 There is a product page at
1356 http://products.amd.com/en-us/GraphicCardResult.aspx
1358 config FB_RADEON_I2C
1359 bool "DDC/I2C for ATI Radeon support"
1360 depends on FB_RADEON
1364 Say Y here if you want DDC/I2C support for your Radeon board.
1366 config FB_RADEON_BACKLIGHT
1367 bool "Support for backlight control"
1368 depends on FB_RADEON
1371 Say Y here if you want to control the backlight of your display.
1373 config FB_RADEON_DEBUG
1374 bool "Lots of debug output from Radeon driver"
1375 depends on FB_RADEON
1378 Say Y here if you want the Radeon driver to output all sorts
1379 of debugging information to provide to the maintainer when
1380 something goes wrong.
1383 tristate "ATI Rage128 display support"
1384 depends on FB && PCI
1385 select FB_CFB_FILLRECT
1386 select FB_CFB_COPYAREA
1387 select FB_CFB_IMAGEBLIT
1388 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1389 select FB_MACMODES if PPC_PMAC
1391 This driver supports graphics boards with the ATI Rage128 chips.
1392 Say Y if you have such a graphics board and read
1393 <file:Documentation/fb/aty128fb.txt>.
1395 To compile this driver as a module, choose M here: the
1396 module will be called aty128fb.
1398 config FB_ATY128_BACKLIGHT
1399 bool "Support for backlight control"
1400 depends on FB_ATY128
1403 Say Y here if you want to control the backlight of your display.
1406 tristate "ATI Mach64 display support" if PCI || ATARI
1407 depends on FB && !SPARC32
1408 select FB_CFB_FILLRECT
1409 select FB_CFB_COPYAREA
1410 select FB_CFB_IMAGEBLIT
1411 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1412 select FB_MACMODES if PPC
1414 This driver supports graphics boards with the ATI Mach64 chips.
1415 Say Y if you have such a graphics board.
1417 To compile this driver as a module, choose M here: the
1418 module will be called atyfb.
1421 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1422 depends on PCI && FB_ATY
1423 default y if SPARC64 && PCI
1425 Say Y here to support use of ATI's 64-bit Rage boards (or other
1426 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1427 framebuffer device. The ATI product support page for these boards
1428 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1430 config FB_ATY_GENERIC_LCD
1431 bool "Mach64 generic LCD support"
1432 depends on FB_ATY_CT
1434 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1435 Rage XC, or Rage XL chipset.
1438 bool "Mach64 GX support" if PCI
1442 Say Y here to support use of the ATI Mach64 Graphics Expression
1443 board (or other boards based on the Mach64 GX chipset) as a
1444 framebuffer device. The ATI product support page for these boards
1446 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1448 config FB_ATY_BACKLIGHT
1449 bool "Support for backlight control"
1453 Say Y here if you want to control the backlight of your display.
1456 tristate "S3 Trio/Virge support"
1457 depends on FB && PCI
1458 select FB_CFB_FILLRECT
1459 select FB_CFB_COPYAREA
1460 select FB_CFB_IMAGEBLIT
1461 select FB_TILEBLITTING
1464 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1466 Driver for graphics boards with S3 Trio / S3 Virge chip.
1469 bool "DDC for S3 support"
1474 Say Y here if you want DDC support for your S3 graphics card.
1477 tristate "S3 Savage support"
1478 depends on FB && PCI
1479 select FB_MODE_HELPERS
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1482 select FB_CFB_IMAGEBLIT
1485 This driver supports notebooks and computers with S3 Savage PCI/AGP
1488 Say Y if you have such a graphics card.
1490 To compile this driver as a module, choose M here; the module
1491 will be called savagefb.
1493 config FB_SAVAGE_I2C
1494 bool "Enable DDC2 Support"
1495 depends on FB_SAVAGE
1498 This enables I2C support for S3 Savage Chipsets. This is used
1499 only for getting EDID information from the attached display
1500 allowing for robust video mode handling and switching.
1502 Because fbdev-2.6 requires that drivers must be able to
1503 independently validate video mode parameters, you should say Y
1506 config FB_SAVAGE_ACCEL
1507 bool "Enable Console Acceleration"
1508 depends on FB_SAVAGE
1511 This option will compile in console acceleration support. If
1512 the resulting framebuffer console has bothersome glitches, then
1516 tristate "SiS/XGI display support"
1517 depends on FB && PCI
1518 select FB_CFB_FILLRECT
1519 select FB_CFB_COPYAREA
1520 select FB_CFB_IMAGEBLIT
1521 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1523 This is the frame buffer device driver for the SiS 300, 315, 330
1524 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1525 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1527 To compile this driver as a module, choose M here; the module
1528 will be called sisfb.
1531 bool "SiS 300 series support"
1534 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1537 bool "SiS 315/330/340 series and XGI support"
1540 Say Y here to support use of the SiS 315, 330 and 340 series
1541 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1542 as XGI V3XT, V5, V8 and Z7.
1545 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1546 depends on FB && PCI && X86
1547 select FB_CFB_FILLRECT
1548 select FB_CFB_COPYAREA
1549 select FB_CFB_IMAGEBLIT
1554 This is the frame buffer device driver for Graphics chips of VIA
1555 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1556 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1558 Say Y if you have a VIA UniChrome graphics board.
1560 To compile this driver as a module, choose M here: the
1561 module will be called viafb.
1565 config FB_VIA_DIRECT_PROCFS
1566 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1570 Allow direct hardware access to some output registers via procfs.
1571 This is dangerous but may provide the only chance to get the
1572 correct output device configuration.
1573 Its use is strongly discouraged.
1575 config FB_VIA_X_COMPATIBILITY
1576 bool "X server compatibility"
1580 This option reduces the functionality (power saving, ...) of the
1581 framebuffer to avoid negative impact on the OpenChrome X server.
1582 If you use any X server other than fbdev you should enable this
1583 otherwise it should be safe to disable it and allow using all
1589 tristate "NeoMagic display support"
1590 depends on FB && PCI
1591 select FB_MODE_HELPERS
1592 select FB_CFB_FILLRECT
1593 select FB_CFB_COPYAREA
1594 select FB_CFB_IMAGEBLIT
1597 This driver supports notebooks with NeoMagic PCI chips.
1598 Say Y if you have such a graphics card.
1600 To compile this driver as a module, choose M here: the
1601 module will be called neofb.
1604 tristate "IMG Kyro support"
1605 depends on FB && PCI
1606 select FB_CFB_FILLRECT
1607 select FB_CFB_COPYAREA
1608 select FB_CFB_IMAGEBLIT
1610 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1613 To compile this driver as a module, choose M here: the
1614 module will be called kyrofb.
1617 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1618 depends on FB && PCI
1619 select FB_CFB_IMAGEBLIT
1620 select FB_CFB_FILLRECT
1621 select FB_CFB_COPYAREA
1622 select FB_MODE_HELPERS
1624 This driver supports graphics boards with the 3Dfx Banshee,
1625 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1626 such a graphics board.
1628 To compile this driver as a module, choose M here: the
1629 module will be called tdfxfb.
1631 config FB_3DFX_ACCEL
1632 bool "3Dfx Acceleration functions"
1635 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1636 device driver with acceleration functions.
1639 bool "Enable DDC/I2C support"
1644 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1647 tristate "3Dfx Voodoo Graphics (sst1) support"
1648 depends on FB && PCI
1649 select FB_CFB_FILLRECT
1650 select FB_CFB_COPYAREA
1651 select FB_CFB_IMAGEBLIT
1653 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1654 Voodoo2 (cvg) based graphics card.
1656 To compile this driver as a module, choose M here: the
1657 module will be called sstfb.
1659 WARNING: Do not use any application that uses the 3D engine
1660 (namely glide) while using this driver.
1661 Please read the <file:Documentation/fb/sstfb.txt> for supported
1662 options and other important info support.
1665 tristate "VIA VT8623 support"
1666 depends on FB && PCI
1667 select FB_CFB_FILLRECT
1668 select FB_CFB_COPYAREA
1669 select FB_CFB_IMAGEBLIT
1670 select FB_TILEBLITTING
1673 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1675 Driver for CastleRock integrated graphics core in the
1676 VIA VT8623 [Apollo CLE266] chipset.
1679 tristate "Trident/CyberXXX/CyberBlade support"
1680 depends on FB && PCI
1681 select FB_CFB_FILLRECT
1682 select FB_CFB_COPYAREA
1683 select FB_CFB_IMAGEBLIT
1685 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1686 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1688 There are also integrated versions of these chips called CyberXXXX,
1689 CyberImage or CyberBlade. These chips are mostly found in laptops
1690 but also on some motherboards including early VIA EPIA motherboards.
1691 For more information, read <file:Documentation/fb/tridentfb.txt>
1693 Say Y if you have such a graphics board.
1695 To compile this driver as a module, choose M here: the
1696 module will be called tridentfb.
1699 tristate "ARK 2000PV support"
1700 depends on FB && PCI
1701 select FB_CFB_FILLRECT
1702 select FB_CFB_COPYAREA
1703 select FB_CFB_IMAGEBLIT
1704 select FB_TILEBLITTING
1707 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1709 Driver for PCI graphics boards with ARK 2000PV chip
1710 and ICS 5342 RAMDAC.
1713 tristate "Permedia3 support"
1714 depends on FB && PCI
1715 select FB_CFB_FILLRECT
1716 select FB_CFB_COPYAREA
1717 select FB_CFB_IMAGEBLIT
1719 This is the frame buffer device driver for the 3DLabs Permedia3
1720 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1721 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1722 and maybe other boards.
1725 tristate "Fujitsu carmine frame buffer support"
1726 depends on FB && PCI
1727 select FB_CFB_FILLRECT
1728 select FB_CFB_COPYAREA
1729 select FB_CFB_IMAGEBLIT
1731 This is the frame buffer device driver for the Fujitsu Carmine chip.
1732 The driver provides two independent frame buffer devices.
1735 depends on FB_CARMINE
1736 prompt "DRAM timing"
1737 default FB_CARMINE_DRAM_EVAL
1739 config FB_CARMINE_DRAM_EVAL
1740 bool "Eval board timings"
1742 Use timings which work on the eval card.
1744 config CARMINE_DRAM_CUSTOM
1745 bool "Custom board timings"
1747 Use custom board timings.
1751 bool "Au1100 LCD Driver"
1752 depends on (FB = y) && MIPS_ALCHEMY
1753 select FB_CFB_FILLRECT
1754 select FB_CFB_COPYAREA
1755 select FB_CFB_IMAGEBLIT
1757 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1758 various panels and CRTs by passing in kernel cmd line option
1759 au1100fb:panel=<name>.
1762 bool "Au1200/Au1300 LCD Driver"
1763 depends on (FB = y) && MIPS_ALCHEMY
1764 select FB_SYS_FILLRECT
1765 select FB_SYS_COPYAREA
1766 select FB_SYS_IMAGEBLIT
1769 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1770 It can drive various panels and CRTs by passing in kernel cmd line
1771 option au1200fb:panel=<name>.
1774 bool "VIA VT8500 framebuffer support"
1775 depends on (FB = y) && ARM && ARCH_VT8500
1776 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1777 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1778 select FB_SYS_IMAGEBLIT
1779 select FB_MODE_HELPERS
1780 select VIDEOMODE_HELPERS
1782 This is the framebuffer driver for VIA VT8500 integrated LCD
1786 bool "Wondermedia WM8xxx-series frame buffer support"
1787 depends on (FB = y) && ARM && ARCH_VT8500
1788 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1789 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1790 select FB_SYS_IMAGEBLIT
1791 select FB_MODE_HELPERS
1792 select VIDEOMODE_HELPERS
1794 This is the framebuffer driver for WonderMedia WM8xxx-series
1795 integrated LCD controller. This driver covers the WM8505, WM8650
1798 config FB_WMT_GE_ROPS
1799 bool "VT8500/WM8xxx accelerated raster ops support"
1800 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1803 This adds support for accelerated raster operations on the
1804 VIA VT8500 and Wondermedia 85xx series SoCs.
1806 source "drivers/video/geode/Kconfig"
1809 tristate "HD64461 Frame Buffer support"
1810 depends on FB && HD64461
1811 select FB_CFB_FILLRECT
1812 select FB_CFB_COPYAREA
1813 select FB_CFB_IMAGEBLIT
1815 This is the frame buffer device driver for the Hitachi HD64461 LCD
1819 bool "PMAG-AA TURBOchannel framebuffer support"
1820 depends on (FB = y) && TC
1821 select FB_CFB_FILLRECT
1822 select FB_CFB_COPYAREA
1823 select FB_CFB_IMAGEBLIT
1825 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1826 used mainly in the MIPS-based DECstation series.
1829 tristate "PMAG-BA TURBOchannel framebuffer support"
1831 select FB_CFB_FILLRECT
1832 select FB_CFB_COPYAREA
1833 select FB_CFB_IMAGEBLIT
1835 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1836 used mainly in the MIPS-based DECstation series.
1839 tristate "PMAGB-B TURBOchannel framebuffer support"
1841 select FB_CFB_FILLRECT
1842 select FB_CFB_COPYAREA
1843 select FB_CFB_IMAGEBLIT
1845 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1846 in the MIPS-based DECstation series. The card is currently only
1847 supported in 1280x1024x8 mode.
1850 bool "Maxine (Personal DECstation) onboard framebuffer support"
1851 depends on (FB = y) && MACH_DECSTATION
1852 select FB_CFB_FILLRECT
1853 select FB_CFB_COPYAREA
1854 select FB_CFB_IMAGEBLIT
1856 Support for the onboard framebuffer (1024x768x8) in the Personal
1857 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1861 bool "G364 frame buffer support"
1862 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1863 select FB_CFB_FILLRECT
1864 select FB_CFB_COPYAREA
1865 select FB_CFB_IMAGEBLIT
1867 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1868 Olivetti M700-10 systems.
1871 bool "Motorola 68328 native frame buffer support"
1872 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1873 select FB_CFB_FILLRECT
1874 select FB_CFB_COPYAREA
1875 select FB_CFB_IMAGEBLIT
1877 Say Y here if you want to support the built-in frame buffer of
1878 the Motorola 68328 CPU family.
1881 tristate "PXA168/910 LCD framebuffer support"
1882 depends on FB && (CPU_PXA168 || CPU_PXA910)
1883 select FB_CFB_FILLRECT
1884 select FB_CFB_COPYAREA
1885 select FB_CFB_IMAGEBLIT
1887 Frame buffer driver for the built-in LCD controller in the Marvell
1891 tristate "PXA LCD framebuffer support"
1892 depends on FB && ARCH_PXA
1893 select FB_CFB_FILLRECT
1894 select FB_CFB_COPYAREA
1895 select FB_CFB_IMAGEBLIT
1897 Frame buffer driver for the built-in LCD controller in the Intel
1900 This driver is also available as a module ( = code which can be
1901 inserted and removed from the running kernel whenever you want). The
1902 module will be called pxafb. If you want to compile it as a module,
1903 say M here and read <file:Documentation/kbuild/modules.txt>.
1907 config FB_PXA_OVERLAY
1908 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1910 depends on FB_PXA && (PXA27x || PXA3xx)
1912 config FB_PXA_SMARTPANEL
1913 bool "PXA Smartpanel LCD support"
1917 config FB_PXA_PARAMETERS
1918 bool "PXA LCD command line parameters"
1922 Enable the use of kernel command line or module parameters
1923 to configure the physical properties of the LCD panel when
1924 using the PXA LCD driver.
1926 This option allows you to override the panel parameters
1927 supplied by the platform in order to support multiple
1928 different models of flatpanel. If you will only be using a
1929 single model of flatpanel then you can safely leave this
1932 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1935 tristate "PXA3xx 2D graphics accelerator driver"
1938 Kernelspace driver for the 2D graphics controller unit (GCU)
1939 found on PXA3xx processors. There is a counterpart driver in the
1940 DirectFB suite, see http://www.directfb.org/
1942 If you compile this as a module, it will be called pxa3xx_gcu.
1945 tristate "2700G LCD framebuffer support"
1946 depends on FB && ARCH_PXA
1947 select FB_CFB_FILLRECT
1948 select FB_CFB_COPYAREA
1949 select FB_CFB_IMAGEBLIT
1951 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1955 bool "Enable debugging info via debugfs"
1956 depends on FB_MBX && DEBUG_FS
1959 Enable this if you want debugging information using the debug
1960 filesystem (debugfs)
1965 tristate "Freescale DIU framebuffer support"
1966 depends on FB && FSL_SOC
1967 select FB_MODE_HELPERS
1968 select FB_CFB_FILLRECT
1969 select FB_CFB_COPYAREA
1970 select FB_CFB_IMAGEBLIT
1971 select PPC_LIB_RHEAP
1973 Framebuffer driver for the Freescale SoC DIU
1976 tristate "W100 frame buffer support"
1977 depends on FB && ARCH_PXA
1978 select FB_CFB_FILLRECT
1979 select FB_CFB_COPYAREA
1980 select FB_CFB_IMAGEBLIT
1982 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1983 It can also drive the w3220 chip found on iPAQ hx4700.
1985 This driver is also available as a module ( = code which can be
1986 inserted and removed from the running kernel whenever you want). The
1987 module will be called w100fb. If you want to compile it as a module,
1988 say M here and read <file:Documentation/kbuild/modules.txt>.
1992 config FB_SH_MOBILE_LCDC
1993 tristate "SuperH Mobile LCDC framebuffer support"
1994 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1995 select FB_SYS_FILLRECT
1996 select FB_SYS_COPYAREA
1997 select FB_SYS_IMAGEBLIT
1999 select FB_DEFERRED_IO
2001 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2003 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2005 config FB_SH_MOBILE_HDMI
2006 tristate "SuperH Mobile HDMI controller support"
2007 depends on FB_SH_MOBILE_LCDC
2008 select FB_MODE_HELPERS
2013 Driver for the on-chip SH-Mobile HDMI controller.
2016 tristate "Toshiba Mobile IO FrameBuffer support"
2017 depends on FB && MFD_CORE
2018 select FB_CFB_FILLRECT
2019 select FB_CFB_COPYAREA
2020 select FB_CFB_IMAGEBLIT
2022 Frame buffer driver for the Toshiba Mobile IO integrated as found
2023 on the Sharp SL-6000 series
2025 This driver is also available as a module ( = code which can be
2026 inserted and removed from the running kernel whenever you want). The
2027 module will be called tmiofb. If you want to compile it as a module,
2028 say M here and read <file:Documentation/kbuild/modules.txt>.
2032 config FB_TMIO_ACCELL
2033 bool "tmiofb acceleration"
2038 tristate "Samsung S3C framebuffer support"
2039 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2040 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2041 select FB_CFB_FILLRECT
2042 select FB_CFB_COPYAREA
2043 select FB_CFB_IMAGEBLIT
2045 Frame buffer driver for the built-in FB controller in the Samsung
2046 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2047 and the S3C64XX series such as the S3C6400 and S3C6410.
2049 These chips all have the same basic framebuffer design with the
2050 actual capabilities depending on the chip. For instance the S3C6400
2051 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2052 currently only have two.
2054 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2056 config FB_S3C_DEBUG_REGWRITE
2057 bool "Debug register writes"
2060 Show all register writes via pr_debug()
2063 tristate "S3C2410 LCD framebuffer support"
2064 depends on FB && ARCH_S3C24XX
2065 select FB_CFB_FILLRECT
2066 select FB_CFB_COPYAREA
2067 select FB_CFB_IMAGEBLIT
2069 Frame buffer driver for the built-in LCD controller in the Samsung
2072 This driver is also available as a module ( = code which can be
2073 inserted and removed from the running kernel whenever you want). The
2074 module will be called s3c2410fb. If you want to compile it as a module,
2075 say M here and read <file:Documentation/kbuild/modules.txt>.
2078 config FB_S3C2410_DEBUG
2079 bool "S3C2410 lcd debug messages"
2080 depends on FB_S3C2410
2082 Turn on debugging messages. Note that you can set/unset at run time
2086 bool "NUC900 LCD framebuffer support"
2087 depends on FB && ARCH_W90X900
2088 select FB_CFB_FILLRECT
2089 select FB_CFB_COPYAREA
2090 select FB_CFB_IMAGEBLIT
2092 Frame buffer driver for the built-in LCD controller in the Nuvoton
2095 config GPM1040A0_320X240
2096 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2097 depends on FB_NUC900
2099 config FB_NUC900_DEBUG
2100 bool "NUC900 lcd debug messages"
2101 depends on FB_NUC900
2103 Turn on debugging messages. Note that you can set/unset at run time
2107 tristate "Silicon Motion SM501 framebuffer support"
2108 depends on FB && MFD_SM501
2109 select FB_CFB_FILLRECT
2110 select FB_CFB_COPYAREA
2111 select FB_CFB_IMAGEBLIT
2113 Frame buffer driver for the CRT and LCD controllers in the Silicon
2116 This driver is also available as a module ( = code which can be
2117 inserted and removed from the running kernel whenever you want). The
2118 module will be called sm501fb. If you want to compile it as a module,
2119 say M here and read <file:Documentation/kbuild/modules.txt>.
2124 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2125 depends on FB && USB
2126 select FB_MODE_HELPERS
2127 select FB_SYS_FILLRECT
2128 select FB_SYS_COPYAREA
2129 select FB_SYS_IMAGEBLIT
2131 select FB_DEFERRED_IO
2133 This is a kernel framebuffer driver for SMSC UFX USB devices.
2134 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2135 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2137 To compile as a module, choose M here: the module name is smscufx.
2140 tristate "Displaylink USB Framebuffer support"
2141 depends on FB && USB
2142 select FB_MODE_HELPERS
2143 select FB_SYS_FILLRECT
2144 select FB_SYS_COPYAREA
2145 select FB_SYS_IMAGEBLIT
2147 select FB_DEFERRED_IO
2149 This is a kernel framebuffer driver for DisplayLink USB devices.
2150 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2151 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2152 To compile as a module, choose M here: the module name is udlfb.
2154 config FB_IBM_GXT4500
2155 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2156 depends on FB && PPC
2157 select FB_CFB_FILLRECT
2158 select FB_CFB_COPYAREA
2159 select FB_CFB_IMAGEBLIT
2161 Say Y here to enable support for the IBM GXT4000P/6000P and
2162 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2163 found on some IBM System P (pSeries) machines. This driver
2164 doesn't use Geometry Engine GT1000.
2167 tristate "PS3 GPU framebuffer driver"
2168 depends on FB && PS3_PS3AV
2169 select FB_SYS_FILLRECT
2170 select FB_SYS_COPYAREA
2171 select FB_SYS_IMAGEBLIT
2173 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2175 Include support for the virtual frame buffer in the PS3 platform.
2177 config FB_PS3_DEFAULT_SIZE_M
2178 int "PS3 default frame buffer size (in MiB)"
2182 This is the default size (in MiB) of the virtual frame buffer in
2184 The default value can be overridden on the kernel command line
2185 using the "ps3fb" option (e.g. "ps3fb=9M");
2188 tristate "Xilinx frame buffer support"
2189 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2190 select FB_CFB_FILLRECT
2191 select FB_CFB_COPYAREA
2192 select FB_CFB_IMAGEBLIT
2194 Include support for the Xilinx ML300/ML403 reference design
2195 framebuffer. ML300 carries a 640*480 LCD display on the board,
2196 ML403 uses a standard DB15 VGA connector.
2199 tristate "Goldfish Framebuffer"
2201 select FB_CFB_FILLRECT
2202 select FB_CFB_COPYAREA
2203 select FB_CFB_IMAGEBLIT
2205 Framebuffer driver for Goldfish Virtual Platform
2208 tristate "Cobalt server LCD frame buffer support"
2209 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2212 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2213 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2214 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2215 select FB_CFB_FILLRECT
2216 select FB_CFB_COPYAREA
2217 select FB_CFB_IMAGEBLIT
2219 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2220 (D)STN/TFT LCD Controller.
2221 Supports display resolutions up to 1024x1024 pixel, grayscale and
2222 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2223 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2224 panels <= 320 pixel horizontal resolution.
2227 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2228 depends on FB && ARCH_DAVINCI_DA8XX
2229 select FB_CFB_FILLRECT
2230 select FB_CFB_COPYAREA
2231 select FB_CFB_IMAGEBLIT
2232 select FB_CFB_REV_PIXELS_IN_BYTE
2234 This is the frame buffer device driver for the TI LCD controller
2235 found on DA8xx/OMAP-L1xx SoCs.
2239 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2241 select FB_SYS_FILLRECT
2242 select FB_SYS_COPYAREA
2243 select FB_SYS_IMAGEBLIT
2246 This is a `virtual' frame buffer device. It operates on a chunk of
2247 unswappable kernel memory instead of on the memory of a graphics
2248 board. This means you cannot see any output sent to this frame
2249 buffer device, while it does consume precious memory. The main use
2250 of this frame buffer device is testing and debugging the frame
2251 buffer subsystem. Do NOT enable it for normal systems! To protect
2252 the innocent, it has to be enabled explicitly at boot time using the
2253 kernel option `video=vfb:'.
2255 To compile this driver as a module, choose M here: the
2256 module will be called vfb. In order to load it, you must use
2257 the vfb_enable=1 option.
2261 config XEN_FBDEV_FRONTEND
2262 tristate "Xen virtual frame buffer support"
2263 depends on FB && XEN
2264 select FB_SYS_FILLRECT
2265 select FB_SYS_COPYAREA
2266 select FB_SYS_IMAGEBLIT
2268 select FB_DEFERRED_IO
2269 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2270 select XEN_XENBUS_FRONTEND
2273 This driver implements the front-end of the Xen virtual
2274 frame buffer driver. It communicates with a back-end
2278 tristate "E-Ink Metronome/8track controller support"
2280 select FB_SYS_FILLRECT
2281 select FB_SYS_COPYAREA
2282 select FB_SYS_IMAGEBLIT
2284 select FB_DEFERRED_IO
2286 This driver implements support for the E-Ink Metronome
2287 controller. The pre-release name for this device was 8track
2288 and could also have been called by some vendors as PVI-nnnn.
2291 tristate "Fujitsu MB862xx GDC support"
2293 depends on PCI || (OF && PPC)
2294 select FB_CFB_FILLRECT
2295 select FB_CFB_COPYAREA
2296 select FB_CFB_IMAGEBLIT
2298 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2301 prompt "GDC variant"
2302 depends on FB_MB862XX
2304 config FB_MB862XX_PCI_GDC
2305 bool "Carmine/Coral-P(A) GDC"
2308 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2309 PCI graphics controller devices.
2311 config FB_MB862XX_LIME
2313 depends on OF && PPC
2314 select FB_FOREIGN_ENDIAN
2315 select FB_LITTLE_ENDIAN
2317 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2321 config FB_MB862XX_I2C
2322 bool "Support I2C bus on MB862XX GDC"
2323 depends on FB_MB862XX && I2C
2326 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2327 driver to support accessing I2C devices on controller's I2C bus.
2328 These are usually some video decoder chips.
2331 tristate "EP93XX frame buffer support"
2332 depends on FB && ARCH_EP93XX
2333 select FB_CFB_FILLRECT
2334 select FB_CFB_COPYAREA
2335 select FB_CFB_IMAGEBLIT
2337 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2338 This driver is also available as a module. The module will be called
2341 config FB_PRE_INIT_FB
2342 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2343 depends on FB && FB_MB862XX_LIME
2345 Select this option if display contents should be inherited as set by
2349 tristate "MSM Framebuffer support"
2350 depends on FB && ARCH_MSM
2351 select FB_CFB_FILLRECT
2352 select FB_CFB_COPYAREA
2353 select FB_CFB_IMAGEBLIT
2356 tristate "MX3 Framebuffer support"
2357 depends on FB && MX3_IPU
2358 select FB_CFB_FILLRECT
2359 select FB_CFB_COPYAREA
2360 select FB_CFB_IMAGEBLIT
2363 This is a framebuffer device for the i.MX31 LCD Controller. So
2364 far only synchronous displays are supported. If you plan to use
2365 an LCD display with your i.MX31 system, say Y here.
2367 config FB_BROADSHEET
2368 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2370 select FB_SYS_FILLRECT
2371 select FB_SYS_COPYAREA
2372 select FB_SYS_IMAGEBLIT
2374 select FB_DEFERRED_IO
2376 This driver implements support for the E-Ink Broadsheet
2377 controller. The release name for this device was Epson S1D13521
2378 and could also have been called by other names when coupled with
2382 tristate "AUO-K190X EPD controller support"
2384 select FB_SYS_FILLRECT
2385 select FB_SYS_COPYAREA
2386 select FB_SYS_IMAGEBLIT
2388 select FB_DEFERRED_IO
2390 Provides support for epaper controllers from the K190X series
2391 of AUO. These controllers can be used to drive epaper displays
2394 This option enables the common support, shared by the individual
2395 controller drivers. You will also have to enable the driver
2396 for the controller type used in your device.
2399 tristate "AUO-K1900 EPD controller support"
2400 depends on FB && FB_AUO_K190X
2402 This driver implements support for the AUO K1900 epd-controller.
2403 This controller can drive Sipix epaper displays but can only do
2404 serial updates, reducing the number of possible frames per second.
2407 tristate "AUO-K1901 EPD controller support"
2408 depends on FB && FB_AUO_K190X
2410 This driver implements support for the AUO K1901 epd-controller.
2411 This controller can drive Sipix epaper displays and supports
2412 concurrent updates, making higher frames per second possible.
2415 tristate "JZ4740 LCD framebuffer support"
2416 depends on FB && MACH_JZ4740
2417 select FB_SYS_FILLRECT
2418 select FB_SYS_COPYAREA
2419 select FB_SYS_IMAGEBLIT
2421 Framebuffer support for the JZ4740 SoC.
2424 tristate "MXS LCD framebuffer support"
2425 depends on FB && ARCH_MXS
2426 select FB_CFB_FILLRECT
2427 select FB_CFB_COPYAREA
2428 select FB_CFB_IMAGEBLIT
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.
2452 source "drivers/video/omap/Kconfig"
2453 source "drivers/video/omap2/Kconfig"
2454 source "drivers/video/exynos/Kconfig"
2455 source "drivers/video/mmp/Kconfig"
2456 source "drivers/video/backlight/Kconfig"
2459 source "drivers/video/console/Kconfig"
2462 if FB || SGI_NEWPORT_CONSOLE
2463 source "drivers/video/logo/Kconfig"
2466 config FB_SH_MOBILE_MERAM
2467 tristate "SuperH Mobile MERAM read ahead support"
2468 depends on (SUPERH || ARCH_SHMOBILE)
2469 select GENERIC_ALLOCATOR
2471 Enable MERAM support for the SuperH controller.
2473 This will allow for caching of the framebuffer to provide more
2474 reliable access under heavy main memory bus traffic situations.
2475 Up to 4 memory channels can be configured, allowing 4 RGB or
2476 2 YCbCr framebuffers to be configured.
2479 tristate "Solomon SSD1307 framebuffer support"
2480 depends on FB && I2C
2482 depends on GENERIC_GPIO
2484 select FB_SYS_FILLRECT
2485 select FB_SYS_COPYAREA
2486 select FB_SYS_IMAGEBLIT
2487 select FB_DEFERRED_IO
2490 This driver implements support for the Solomon SSD1307
2491 OLED controller over I2C.