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"
24 source "drivers/gpu/host1x/Kconfig"
30 config VIDEO_OUTPUT_CONTROL
31 tristate "Lowlevel video output switch controls"
33 This framework adds support for low-level control of the video
36 config VIDEOMODE_HELPERS
42 config VEXPRESS_DVI_CONTROL
43 bool "Versatile Express DVI control"
44 depends on FB && VEXPRESS_CONFIG
48 tristate "Support for frame buffer devices"
50 The frame buffer device provides an abstraction for the graphics
51 hardware. It represents the frame buffer of some video hardware and
52 allows application software to access the graphics hardware through
53 a well-defined interface, so the software doesn't need to know
54 anything about the low-level (hardware register) stuff.
56 Frame buffer devices work identically across the different
57 architectures supported by Linux and make the implementation of
58 application programs easier and more portable; at this point, an X
59 server exists which uses the frame buffer device exclusively.
60 On several non-X86 architectures, the frame buffer device is the
61 only way to use the graphics hardware.
63 The device is accessed through special device nodes, usually located
64 in the /dev directory, i.e. /dev/fb*.
66 You need an utility program called fbset to make full use of frame
67 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
68 and the Framebuffer-HOWTO at
69 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
72 Say Y here and to the driver for your graphics board below if you
73 are compiling a kernel for a non-x86 architecture.
75 If you are compiling for the x86 architecture, you can say Y if you
76 want to play with it, but it is not essential. Please note that
77 running graphical applications that directly touch the hardware
78 (e.g. an accelerated X server) and that are not frame buffer
79 device-aware may cause unexpected results. If unsure, say N.
82 bool "Enable firmware EDID"
86 This enables access to the EDID transferred from the firmware.
87 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
88 transfers do not work for your driver and if you are using
89 nvidiafb, i810fb or savagefb.
91 In general, choosing Y for this option is safe. If you
92 experience extremely long delays while booting before you get
93 something on your display, try setting this to N. Matrox cards in
94 combination with certain motherboards and monitors are known to
95 suffer from this problem.
104 config FB_BOOT_VESA_SUPPORT
109 If true, at least one selected framebuffer driver can take advantage
110 of VESA video modes set at an early boot stage via the vga= parameter.
112 config FB_CFB_FILLRECT
117 Include the cfb_fillrect function for generic software rectangle
118 filling. This is used by drivers that don't provide their own
119 (accelerated) version.
121 config FB_CFB_COPYAREA
126 Include the cfb_copyarea function for generic software area copying.
127 This is used by drivers that don't provide their own (accelerated)
130 config FB_CFB_IMAGEBLIT
135 Include the cfb_imageblit function for generic software image
136 blitting. This is used by drivers that don't provide their own
137 (accelerated) version.
139 config FB_CFB_REV_PIXELS_IN_BYTE
144 Allow generic frame-buffer functions to work on displays with 1, 2
145 and 4 bits per pixel depths which has opposite order of pixels in
146 byte order to bytes in long order.
148 config FB_SYS_FILLRECT
153 Include the sys_fillrect function for generic software rectangle
154 filling. This is used by drivers that don't provide their own
155 (accelerated) version and the framebuffer is in system RAM.
157 config FB_SYS_COPYAREA
162 Include the sys_copyarea function for generic software area copying.
163 This is used by drivers that don't provide their own (accelerated)
164 version and the framebuffer is in system RAM.
166 config FB_SYS_IMAGEBLIT
171 Include the sys_imageblit function for generic software image
172 blitting. This is used by drivers that don't provide their own
173 (accelerated) version and the framebuffer is in system RAM.
175 menuconfig FB_FOREIGN_ENDIAN
176 bool "Framebuffer foreign endianness support"
179 This menu will let you enable support for the framebuffers with
180 non-native endianness (e.g. Little-Endian framebuffer on a
181 Big-Endian machine). Most probably you don't have such hardware,
182 so it's safe to say "n" here.
185 prompt "Choice endianness support"
186 depends on FB_FOREIGN_ENDIAN
188 config FB_BOTH_ENDIAN
189 bool "Support for Big- and Little-Endian framebuffers"
192 bool "Support for Big-Endian framebuffers only"
194 config FB_LITTLE_ENDIAN
195 bool "Support for Little-Endian framebuffers only"
204 config FB_DEFERRED_IO
211 depends on FB_DEFERRED_IO
218 Common utility functions useful to fbdev drivers of VGA-based
229 select BACKLIGHT_LCD_SUPPORT
230 select BACKLIGHT_CLASS_DEVICE
233 config FB_MODE_HELPERS
234 bool "Enable Video Mode Handling Helpers"
238 This enables functions for handling video modes using the
239 Generalized Timing Formula and the EDID parser. A few drivers rely
240 on this feature such as the radeonfb, rivafb, and the i810fb. If
241 your driver does not take advantage of this feature, choosing Y will
242 just increase the kernel size by about 5K.
244 config FB_TILEBLITTING
245 bool "Enable Tile Blitting Support"
249 This enables tile blitting. Tile blitting is a drawing technique
250 where the screen is divided into rectangular sections (tiles), whereas
251 the standard blitting divides the screen into pixels. Because the
252 default drawing element is a tile, drawing functions will be passed
253 parameters in terms of number of tiles instead of number of pixels.
254 For example, to draw a single character, instead of using bitmaps,
255 an index to an array of bitmaps will be used. To clear or move a
256 rectangular section of a screen, the rectangle will be described in
257 terms of number of tiles in the x- and y-axis.
259 This is particularly important to one driver, matroxfb. If
262 comment "Frame buffer hardware drivers"
266 tristate "Aeroflex Gaisler framebuffer support"
267 depends on FB && SPARC
268 select FB_CFB_FILLRECT
269 select FB_CFB_COPYAREA
270 select FB_CFB_IMAGEBLIT
272 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
275 tristate "Cirrus Logic support"
276 depends on FB && (ZORRO || PCI)
277 select FB_CFB_FILLRECT
278 select FB_CFB_COPYAREA
279 select FB_CFB_IMAGEBLIT
281 This enables support for Cirrus Logic GD542x/543x based boards on
282 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
284 If you have a PCI-based system, this enables support for these
285 chips: GD-543x, GD-544x, GD-5480.
287 Please read the file <file:Documentation/fb/cirrusfb.txt>.
289 Say N unless you have such a graphics board or plan to get one
290 before you next recompile the kernel.
293 tristate "Permedia2 support"
294 depends on FB && ((AMIGA && BROKEN) || PCI)
295 select FB_CFB_FILLRECT
296 select FB_CFB_COPYAREA
297 select FB_CFB_IMAGEBLIT
299 This is the frame buffer device driver for cards based on
300 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
301 The driver was tested on the following cards:
302 Diamond FireGL 1000 PRO AGP
303 ELSA Gloria Synergy PCI
304 Appian Jeronimo PRO (both heads) PCI
305 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
306 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
307 ASK Graphic Blaster Exxtreme AGP
309 To compile this driver as a module, choose M here: the
310 module will be called pm2fb.
312 config FB_PM2_FIFO_DISCONNECT
313 bool "enable FIFO disconnect feature"
314 depends on FB_PM2 && PCI
316 Support the Permedia2 FIFO disconnect feature.
319 tristate "ARM PrimeCell PL110 support"
320 depends on FB && ARM && ARM_AMBA
321 select FB_CFB_FILLRECT
322 select FB_CFB_COPYAREA
323 select FB_CFB_IMAGEBLIT
325 This framebuffer device driver is for the ARM PrimeCell PL110
326 Colour LCD controller. ARM PrimeCells provide the building
327 blocks for System on a Chip devices.
329 If you want to compile this as a module (=code which can be
330 inserted into and removed from the running kernel), say M
331 here and read <file:Documentation/kbuild/modules.txt>. The module
332 will be called amba-clcd.
335 tristate "ARM High Definition LCD support"
337 select FB_CFB_FILLRECT
338 select FB_CFB_COPYAREA
339 select FB_CFB_IMAGEBLIT
341 This framebuffer device driver is for the ARM High Definition
342 Colour LCD controller.
344 If you want to compile this as a module (=code which can be
345 inserted into and removed from the running kernel), say M
346 here and read <file:Documentation/kbuild/modules.txt>. The module
347 will be called arm-hdlcd.
350 bool "Acorn VIDC support"
351 depends on (FB = y) && ARM && ARCH_ACORN
352 select FB_CFB_FILLRECT
353 select FB_CFB_COPYAREA
354 select FB_CFB_IMAGEBLIT
356 This is the frame buffer device driver for the Acorn VIDC graphics
357 hardware found in Acorn RISC PCs and other ARM-based machines. If
361 bool "CLPS711X LCD support"
362 depends on (FB = y) && ARM && ARCH_CLPS711X
363 select FB_CFB_FILLRECT
364 select FB_CFB_COPYAREA
365 select FB_CFB_IMAGEBLIT
367 Say Y to enable the Framebuffer driver for the CLPS7111 and
371 bool "SA-1100 LCD support"
372 depends on (FB = y) && ARM && ARCH_SA1100
373 select FB_CFB_FILLRECT
374 select FB_CFB_COPYAREA
375 select FB_CFB_IMAGEBLIT
377 This is a framebuffer device for the SA-1100 LCD Controller.
378 See <http://www.linux-fbdev.org/> for information on framebuffer
381 If you plan to use the LCD display with your SA-1100 system, say
385 tristate "Freescale i.MX1/21/25/27 LCD support"
386 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
392 tristate "CyberPro 2000/2010/5000 support"
393 depends on FB && PCI && (BROKEN || !SPARC64)
394 select FB_CFB_FILLRECT
395 select FB_CFB_COPYAREA
396 select FB_CFB_IMAGEBLIT
398 This enables support for the Integraphics CyberPro 20x0 and 5000
399 VGA chips used in the Rebel.com Netwinder and other machines.
400 Say Y if you have a NetWinder or a graphics card containing this
401 device, otherwise say N.
403 config FB_CYBER2000_DDC
404 bool "DDC for CyberPro support"
405 depends on FB_CYBER2000
409 Say Y here if you want DDC support for your CyberPro graphics
410 card. This is only I2C bus support, driver does not use EDID.
412 config FB_CYBER2000_I2C
413 bool "CyberPro 2000/2010/5000 I2C support"
414 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
417 Enable support for the I2C video decoder interface on the
418 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
419 on the Netwinder machines for the SAA7111 video capture.
423 depends on (FB = y) && APOLLO
425 select FB_CFB_FILLRECT
426 select FB_CFB_IMAGEBLIT
430 depends on (FB = y) && Q40
432 select FB_CFB_FILLRECT
433 select FB_CFB_COPYAREA
434 select FB_CFB_IMAGEBLIT
437 tristate "Amiga native chipset support"
438 depends on FB && AMIGA
440 This is the frame buffer device driver for the builtin graphics
441 chipset found in Amigas.
443 To compile this driver as a module, choose M here: the
444 module will be called amifb.
447 bool "Amiga OCS chipset support"
450 This enables support for the original Agnus and Denise video chips,
451 found in the Amiga 1000 and most A500's and A2000's. If you intend
452 to run Linux on any of these systems, say Y; otherwise say N.
455 bool "Amiga ECS chipset support"
458 This enables support for the Enhanced Chip Set, found in later
459 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
460 you intend to run Linux on any of these systems, say Y; otherwise
464 bool "Amiga AGA chipset support"
467 This enables support for the Advanced Graphics Architecture (also
468 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
469 and CD32. If you intend to run Linux on any of these systems, say Y;
473 bool "Amiga FrameMaster II/Rainbow II support"
474 depends on (FB = y) && ZORRO
475 select FB_CFB_FILLRECT
476 select FB_CFB_COPYAREA
477 select FB_CFB_IMAGEBLIT
479 This is the frame buffer device driver for the Amiga FrameMaster
480 card from BSC (exhibited 1992 but not shipped as a CBM product).
483 tristate "Arc Monochrome LCD board support"
485 select FB_SYS_FILLRECT
486 select FB_SYS_COPYAREA
487 select FB_SYS_IMAGEBLIT
490 This enables support for the Arc Monochrome LCD board. The board
491 is based on the KS-108 lcd controller and is typically a matrix
492 of 2*n chips. This driver was tested with a 128x64 panel. This
493 driver supports it for use with x86 SBCs through a 16 bit GPIO
494 interface (8 bit data, 8 bit control). If you anticipate using
495 this driver, say Y or M; otherwise say N. You must specify the
496 GPIO IO address to be used for setting control and data.
499 bool "Atari native chipset support"
500 depends on (FB = y) && ATARI
501 select FB_CFB_FILLRECT
502 select FB_CFB_COPYAREA
503 select FB_CFB_IMAGEBLIT
505 This is the frame buffer device driver for the builtin graphics
506 chipset found in Ataris.
509 bool "Open Firmware frame buffer device support"
510 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
511 select FB_CFB_FILLRECT
512 select FB_CFB_COPYAREA
513 select FB_CFB_IMAGEBLIT
516 Say Y if you want support with Open Firmware for your graphics
520 bool "Apple \"control\" display support"
521 depends on (FB = y) && 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 graphics adapter in the
528 Power Macintosh 7300 and others.
531 bool "Apple \"platinum\" display support"
532 depends on (FB = y) && PPC_PMAC && PPC32
533 select FB_CFB_FILLRECT
534 select FB_CFB_COPYAREA
535 select FB_CFB_IMAGEBLIT
538 This driver supports a frame buffer for the "platinum" graphics
539 adapter in some Power Macintoshes.
542 bool "Apple \"valkyrie\" display support"
543 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
544 select FB_CFB_FILLRECT
545 select FB_CFB_COPYAREA
546 select FB_CFB_IMAGEBLIT
549 This driver supports a frame buffer for the "valkyrie" graphics
550 adapter in some Power Macintoshes.
553 bool "Chips 65550 display support"
554 depends on (FB = y) && PPC32 && PCI
555 select FB_CFB_FILLRECT
556 select FB_CFB_COPYAREA
557 select FB_CFB_IMAGEBLIT
559 This is the frame buffer device driver for the Chips & Technologies
560 65550 graphics chip in PowerBooks.
563 bool "Asiliant (Chips) 69000 display support"
564 depends on (FB = y) && PCI
565 select FB_CFB_FILLRECT
566 select FB_CFB_COPYAREA
567 select FB_CFB_IMAGEBLIT
569 This is the frame buffer device driver for the Asiliant 69030 chipset
572 bool "IMS Twin Turbo display support"
573 depends on (FB = y) && PCI
574 select FB_CFB_IMAGEBLIT
575 select FB_MACMODES if PPC
577 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
578 many Macintosh and compatible computers.
581 tristate "VGA 16-color graphics support"
582 depends on FB && (X86 || PPC)
583 select FB_CFB_FILLRECT
584 select FB_CFB_COPYAREA
585 select FB_CFB_IMAGEBLIT
587 select FONT_8x16 if FRAMEBUFFER_CONSOLE
589 This is the frame buffer device driver for VGA 16 color graphic
590 cards. Say Y if you have such a card.
592 To compile this driver as a module, choose M here: the
593 module will be called vga16fb.
595 config FB_BF54X_LQ043
596 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
597 depends on FB && (BF54x) && !BF542
598 select FB_CFB_FILLRECT
599 select FB_CFB_COPYAREA
600 select FB_CFB_IMAGEBLIT
602 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
604 config FB_BFIN_T350MCQB
605 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
606 depends on FB && BLACKFIN
608 select FB_CFB_FILLRECT
609 select FB_CFB_COPYAREA
610 select FB_CFB_IMAGEBLIT
612 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
613 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
614 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
616 config FB_BFIN_LQ035Q1
617 tristate "SHARP LQ035Q1DH02 TFT LCD"
618 depends on FB && BLACKFIN && SPI
619 select FB_CFB_FILLRECT
620 select FB_CFB_COPYAREA
621 select FB_CFB_IMAGEBLIT
624 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
625 the Blackfin Landscape LCD EZ-Extender Card.
626 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
627 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
629 To compile this driver as a module, choose M here: the
630 module will be called bfin-lq035q1-fb.
632 config FB_BF537_LQ035
633 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
634 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
635 select FB_CFB_FILLRECT
636 select FB_CFB_COPYAREA
637 select FB_CFB_IMAGEBLIT
640 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
643 To compile this driver as a module, choose M here: the
644 module will be called bf537-lq035.
647 tristate "Blackfin ADV7393 Video encoder"
648 depends on FB && BLACKFIN
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
654 This is the framebuffer device for a ADV7393 video encoder
655 attached to a Blackfin on the PPI port.
656 If your Blackfin board has a ADV7393 select Y.
658 To compile this driver as a module, choose M here: the
659 module will be called bfin_adv7393fb.
662 prompt "Video mode support"
663 depends on FB_BFIN_7393
673 bool 'NTSC 640x480 (Experimental)'
676 bool 'PAL 640x480 (Experimental)'
679 bool 'NTSC 720x480 YCbCR input'
682 bool 'PAL 720x576 YCbCR input'
687 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
688 depends on (FB_BFIN_7393)
689 default ADV7393_1XMEM
699 tristate "HP STI frame buffer device support"
700 depends on FB && PARISC
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
708 STI refers to the HP "Standard Text Interface" which is a set of
709 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
710 Enabling this option will implement the linux framebuffer device
711 using calls to the STI BIOS routines for initialisation.
713 If you enable this option, you will get a planar framebuffer device
714 /dev/fb which will work on the most common HP graphic cards of the
715 NGLE family, including the artist chips (in the 7xx and Bxxx series),
716 HCRX, HCRX24, CRX, CRX24 and VisEG series.
718 It is safe to enable this option, so you should probably say "Y".
721 bool "Generic Macintosh display support"
722 depends on (FB = y) && MAC
723 select FB_CFB_FILLRECT
724 select FB_CFB_COPYAREA
725 select FB_CFB_IMAGEBLIT
730 depends on (FB = y) && DIO
731 select FB_CFB_IMAGEBLIT
735 tristate "TGA/SFB+ framebuffer support"
736 depends on FB && (ALPHA || TC)
737 select FB_CFB_FILLRECT
738 select FB_CFB_COPYAREA
739 select FB_CFB_IMAGEBLIT
742 This is the frame buffer device driver for generic TGA and SFB+
743 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
744 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
745 TURBOchannel cards, also known as PMAGD-A, -B and -C.
747 Due to hardware limitations ZLX-E2 and E3 cards are not supported
748 for DECstation 5000/200 systems. Additionally due to firmware
749 limitations these cards may cause troubles with booting DECstation
750 5000/240 and /260 systems, but are fully supported under Linux if
751 you manage to get it going. ;-)
753 Say Y if you have one of those.
756 tristate "Userspace VESA VGA graphics support"
757 depends on FB && CONNECTOR
758 select FB_CFB_FILLRECT
759 select FB_CFB_COPYAREA
760 select FB_CFB_IMAGEBLIT
761 select FB_MODE_HELPERS
763 This is the frame buffer driver for generic VBE 2.0 compliant
764 graphic cards. It can also take advantage of VBE 3.0 features,
765 such as refresh rate adjustment.
767 This driver generally provides more features than vesafb but
768 requires a userspace helper application called 'v86d'. See
769 <file:Documentation/fb/uvesafb.txt> for more information.
774 bool "VESA VGA graphics support"
775 depends on (FB = y) && X86
776 select FB_CFB_FILLRECT
777 select FB_CFB_COPYAREA
778 select FB_CFB_IMAGEBLIT
779 select FB_BOOT_VESA_SUPPORT
781 This is the frame buffer device driver for generic VESA 2.0
782 compliant graphic cards. The older VESA 1.2 cards are not supported.
783 You will get a boot time penguin logo at no additional cost. Please
784 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
787 bool "EFI-based Framebuffer Support"
788 depends on (FB = y) && X86 && EFI
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
793 This is the EFI frame buffer device driver. If the firmware on
794 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
795 using the EFI framebuffer as your console.
798 tristate "N411 Apollo/Hecuba devkit support"
799 depends on FB && X86 && MMU
800 select FB_SYS_FILLRECT
801 select FB_SYS_COPYAREA
802 select FB_SYS_IMAGEBLIT
804 select FB_DEFERRED_IO
807 This enables support for the Apollo display controller in its
808 Hecuba form using the n411 devkit.
811 tristate "Hercules mono graphics support"
814 Say Y here if you have a Hercules mono graphics card.
816 To compile this driver as a module, choose M here: the
817 module will be called hgafb.
819 As this card technology is at least 25 years old,
820 most people will answer N here.
823 tristate "SGI Visual Workstation framebuffer support"
824 depends on FB && X86_VISWS
825 select FB_CFB_FILLRECT
826 select FB_CFB_COPYAREA
827 select FB_CFB_IMAGEBLIT
829 SGI Visual Workstation support for framebuffer graphics.
832 bool "SGI Graphics Backend frame buffer support"
833 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 This is the frame buffer device driver for SGI Graphics Backend.
839 This chip is used in SGI O2 and Visual Workstation 320/540.
842 int "Video memory size in MB"
846 This is the amount of memory reserved for the framebuffer,
847 which can be any value between 1MB and 8MB.
850 bool "SBUS and UPA framebuffers"
851 depends on (FB = y) && SPARC
853 Say Y if you want support for SBUS or UPA based frame buffer device.
857 depends on (FB = y) && (SPARC && FB_SBUS)
858 select FB_CFB_FILLRECT
859 select FB_CFB_COPYAREA
860 select FB_CFB_IMAGEBLIT
862 This is the frame buffer device driver for the BWtwo frame buffer.
865 bool "CGthree support"
866 depends on (FB = y) && (SPARC && FB_SBUS)
867 select FB_CFB_FILLRECT
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
871 This is the frame buffer device driver for the CGthree frame buffer.
874 bool "CGsix (GX,TurboGX) support"
875 depends on (FB = y) && (SPARC && FB_SBUS)
876 select FB_CFB_COPYAREA
877 select FB_CFB_IMAGEBLIT
879 This is the frame buffer device driver for the CGsix (GX, TurboGX)
883 bool "Creator/Creator3D/Elite3D support"
884 depends on FB_SBUS && SPARC64
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 This is the frame buffer device driver for the Creator, Creator3D,
889 and Elite3D graphics boards.
892 bool "TCX (SS4/SS5 only) support"
894 select FB_CFB_FILLRECT
895 select FB_CFB_COPYAREA
896 select FB_CFB_IMAGEBLIT
898 This is the frame buffer device driver for the TCX 24/8bit frame
902 bool "CGfourteen (SX) support"
904 select FB_CFB_FILLRECT
905 select FB_CFB_COPYAREA
906 select FB_CFB_IMAGEBLIT
908 This is the frame buffer device driver for the CGfourteen frame
909 buffer on Desktop SPARCsystems with the SX graphics option.
912 bool "P9100 (Sparcbook 3 only) support"
914 select FB_CFB_FILLRECT
915 select FB_CFB_COPYAREA
916 select FB_CFB_IMAGEBLIT
918 This is the frame buffer device driver for the P9100 card
919 supported on Sparcbook 3 machines.
922 bool "Leo (ZX) support"
924 select FB_CFB_FILLRECT
925 select FB_CFB_COPYAREA
926 select FB_CFB_IMAGEBLIT
928 This is the frame buffer device driver for the SBUS-based Sun ZX
929 (leo) frame buffer cards.
932 bool "IGA 168x display support"
933 depends on (FB = y) && SPARC32
934 select FB_CFB_FILLRECT
935 select FB_CFB_COPYAREA
936 select FB_CFB_IMAGEBLIT
938 This is the framebuffer device for the INTERGRAPHICS 1680 and
939 successor frame buffer cards.
942 bool "Sun XVR-500 3DLABS Wildcat support"
943 depends on (FB = y) && PCI && SPARC64
944 select FB_CFB_FILLRECT
945 select FB_CFB_COPYAREA
946 select FB_CFB_IMAGEBLIT
948 This is the framebuffer device for the Sun XVR-500 and similar
949 graphics cards based upon the 3DLABS Wildcat chipset. The driver
950 only works on sparc64 systems where the system firmware has
951 mostly initialized the card already. It is treated as a
952 completely dumb framebuffer device.
955 bool "Sun XVR-2500 3DLABS Wildcat support"
956 depends on (FB = y) && PCI && SPARC64
957 select FB_CFB_FILLRECT
958 select FB_CFB_COPYAREA
959 select FB_CFB_IMAGEBLIT
961 This is the framebuffer device for the Sun XVR-2500 and similar
962 graphics cards based upon the 3DLABS Wildcat chipset. The driver
963 only works on sparc64 systems where the system firmware has
964 mostly initialized the card already. It is treated as a
965 completely dumb framebuffer device.
968 bool "Sun XVR-1000 support"
969 depends on (FB = y) && SPARC64
970 select FB_CFB_FILLRECT
971 select FB_CFB_COPYAREA
972 select FB_CFB_IMAGEBLIT
974 This is the framebuffer device for the Sun XVR-1000 and similar
975 graphics cards. The driver only works on sparc64 systems where
976 the system firmware has mostly initialized the card already. It
977 is treated as a completely dumb framebuffer device.
980 tristate "NEC PowerVR 2 display support"
981 depends on FB && SH_DREAMCAST
982 select FB_CFB_FILLRECT
983 select FB_CFB_COPYAREA
984 select FB_CFB_IMAGEBLIT
986 Say Y here if you have a PowerVR 2 card in your box. If you plan to
987 run linux on your Dreamcast, you will have to say Y here.
988 This driver may or may not work on other PowerVR 2 cards, but is
989 totally untested. Use at your own risk. If unsure, say N.
991 To compile this driver as a module, choose M here: the
992 module will be called pvr2fb.
994 You can pass several parameters to the driver at boot time or at
995 module load time. The parameters look like "video=pvr2:XXX", where
996 the meaning of XXX can be found at the end of the main source file
997 (<file:drivers/video/pvr2fb.c>). Please see the file
998 <file:Documentation/fb/pvr2fb.txt>.
1001 tristate "Epson S1D13XXX framebuffer support"
1003 select FB_CFB_FILLRECT
1004 select FB_CFB_COPYAREA
1005 select FB_CFB_IMAGEBLIT
1007 Support for S1D13XXX framebuffer device family (currently only
1008 working with S1D13806). Product specs at
1009 <http://vdc.epson.com/>
1012 tristate "AT91/AT32 LCD Controller support"
1013 depends on FB && HAVE_FB_ATMEL
1014 select FB_CFB_FILLRECT
1015 select FB_CFB_COPYAREA
1016 select FB_CFB_IMAGEBLIT
1018 This enables support for the AT91/AT32 LCD Controller.
1021 bool "Frame Buffer in internal SRAM"
1022 depends on FB_ATMEL && ARCH_AT91SAM9261
1024 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1025 to let frame buffer in external SDRAM.
1028 bool "Use a STN display with AT91/AT32 LCD Controller"
1029 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1032 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1033 Controller. Say N if you want to connect a TFT.
1038 tristate "nVidia Framebuffer Support"
1039 depends on FB && PCI
1040 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1041 select FB_MODE_HELPERS
1042 select FB_CFB_FILLRECT
1043 select FB_CFB_COPYAREA
1044 select FB_CFB_IMAGEBLIT
1048 This driver supports graphics boards with the nVidia chips, TNT
1049 and newer. For very old chipsets, such as the RIVA128, then use
1051 Say Y if you have such a graphics board.
1053 To compile this driver as a module, choose M here: the
1054 module will be called nvidiafb.
1056 config FB_NVIDIA_I2C
1057 bool "Enable DDC Support"
1058 depends on FB_NVIDIA
1061 This enables I2C support for nVidia Chipsets. This is used
1062 only for getting EDID information from the attached display
1063 allowing for robust video mode handling and switching.
1065 Because fbdev-2.6 requires that drivers must be able to
1066 independently validate video mode parameters, you should say Y
1069 config FB_NVIDIA_DEBUG
1070 bool "Lots of debug output"
1071 depends on FB_NVIDIA
1074 Say Y here if you want the nVidia driver to output all sorts
1075 of debugging information to provide to the maintainer when
1076 something goes wrong.
1078 config FB_NVIDIA_BACKLIGHT
1079 bool "Support for backlight control"
1080 depends on FB_NVIDIA
1083 Say Y here if you want to control the backlight of your display.
1086 tristate "nVidia Riva support"
1087 depends on FB && PCI
1088 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1089 select FB_MODE_HELPERS
1090 select FB_CFB_FILLRECT
1091 select FB_CFB_COPYAREA
1092 select FB_CFB_IMAGEBLIT
1096 This driver supports graphics boards with the nVidia Riva/Geforce
1098 Say Y if you have such a graphics board.
1100 To compile this driver as a module, choose M here: the
1101 module will be called rivafb.
1104 bool "Enable DDC Support"
1108 This enables I2C support for nVidia Chipsets. This is used
1109 only for getting EDID information from the attached display
1110 allowing for robust video mode handling and switching.
1112 Because fbdev-2.6 requires that drivers must be able to
1113 independently validate video mode parameters, you should say Y
1116 config FB_RIVA_DEBUG
1117 bool "Lots of debug output"
1121 Say Y here if you want the Riva driver to output all sorts
1122 of debugging information to provide to the maintainer when
1123 something goes wrong.
1125 config FB_RIVA_BACKLIGHT
1126 bool "Support for backlight control"
1130 Say Y here if you want to control the backlight of your display.
1133 tristate "Intel740 support"
1134 depends on FB && PCI
1135 select FB_MODE_HELPERS
1136 select FB_CFB_FILLRECT
1137 select FB_CFB_COPYAREA
1138 select FB_CFB_IMAGEBLIT
1142 This driver supports graphics cards based on Intel740 chip.
1145 tristate "Intel 810/815 support"
1146 depends on FB && PCI && X86_32 && AGP_INTEL
1147 select FB_MODE_HELPERS
1148 select FB_CFB_FILLRECT
1149 select FB_CFB_COPYAREA
1150 select FB_CFB_IMAGEBLIT
1153 This driver supports the on-board graphics built in to the Intel 810
1154 and 815 chipsets. Say Y if you have and plan to use such a board.
1156 To compile this driver as a module, choose M here: the
1157 module will be called i810fb.
1159 For more information, please read
1160 <file:Documentation/fb/intel810.txt>
1163 bool "use VESA Generalized Timing Formula"
1166 If you say Y, then the VESA standard, Generalized Timing Formula
1167 or GTF, will be used to calculate the required video timing values
1168 per video mode. Since the GTF allows nondiscrete timings
1169 (nondiscrete being a range of values as opposed to discrete being a
1170 set of values), you'll be able to use any combination of horizontal
1171 and vertical resolutions, and vertical refresh rates without having
1172 to specify your own timing parameters. This is especially useful
1173 to maximize the performance of an aging display, or if you just
1174 have a display with nonstandard dimensions. A VESA compliant
1175 monitor is recommended, but can still work with non-compliant ones.
1176 If you need or want this, then select this option. The timings may
1177 not be compliant with Intel's recommended values. Use at your own
1180 If you say N, the driver will revert to discrete video timings
1181 using a set recommended by Intel in their documentation.
1186 bool "Enable DDC Support"
1187 depends on FB_I810 && FB_I810_GTF
1192 tristate "Intel LE80578 (Vermilion) support"
1193 depends on FB && PCI && X86
1194 select FB_MODE_HELPERS
1195 select FB_CFB_FILLRECT
1196 select FB_CFB_COPYAREA
1197 select FB_CFB_IMAGEBLIT
1199 This driver supports the LE80578 (Vermilion Range) chipset
1201 config FB_CARILLO_RANCH
1202 tristate "Intel Carillo Ranch support"
1203 depends on FB_LE80578 && FB && PCI && X86
1205 This driver supports the LE80578 (Carillo Ranch) board
1208 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1209 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1210 select FB_MODE_HELPERS
1211 select FB_CFB_FILLRECT
1212 select FB_CFB_COPYAREA
1213 select FB_CFB_IMAGEBLIT
1214 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1215 depends on !DRM_I915
1217 This driver supports the on-board graphics built in to the Intel
1218 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1219 Say Y if you have and plan to use such a board.
1221 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1223 To compile this driver as a module, choose M here: the
1224 module will be called intelfb.
1226 For more information, please read <file:Documentation/fb/intelfb.txt>
1228 config FB_INTEL_DEBUG
1229 bool "Intel driver Debug Messages"
1232 Say Y here if you want the Intel driver to output all sorts
1233 of debugging information to provide to the maintainer when
1234 something goes wrong.
1237 bool "DDC/I2C for Intel framebuffer support"
1242 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1245 tristate "Matrox acceleration"
1246 depends on FB && PCI
1247 select FB_CFB_FILLRECT
1248 select FB_CFB_COPYAREA
1249 select FB_CFB_IMAGEBLIT
1250 select FB_TILEBLITTING
1251 select FB_MACMODES if PPC_PMAC
1253 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1254 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1255 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1256 Matrox G400, G450 or G550 card in your box.
1258 To compile this driver as a module, choose M here: the
1259 module will be called matroxfb.
1261 You can pass several parameters to the driver at boot time or at
1262 module load time. The parameters look like "video=matroxfb:XXX", and
1263 are described in <file:Documentation/fb/matroxfb.txt>.
1265 config FB_MATROX_MILLENIUM
1266 bool "Millennium I/II support"
1267 depends on FB_MATROX
1269 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1270 video card. If you select "Advanced lowlevel driver options" below,
1271 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1272 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1273 also use font widths different from 8.
1275 config FB_MATROX_MYSTIQUE
1276 bool "Mystique support"
1277 depends on FB_MATROX
1279 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1280 video card. If you select "Advanced lowlevel driver options" below,
1281 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1282 packed pixel and 32 bpp packed pixel. You can also use font widths
1286 bool "G100/G200/G400/G450/G550 support"
1287 depends on FB_MATROX
1289 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1290 video card. If you select "Advanced lowlevel driver options", you
1291 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1292 pixel and 32 bpp packed pixel. You can also use font widths
1295 If you need support for G400 secondary head, you must say Y to
1296 "Matrox I2C support" and "G400 second head support" right below.
1297 G450/G550 secondary head and digital output are supported without
1300 The driver starts in monitor mode. You must use the matroxset tool
1301 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1302 swap primary and secondary head outputs, or to change output mode.
1303 Secondary head driver always start in 640x480 resolution and you
1304 must use fbset to change it.
1306 Do not forget that second head supports only 16 and 32 bpp
1307 packed pixels, so it is a good idea to compile them into the kernel
1308 too. You can use only some font widths, as the driver uses generic
1309 painting procedures (the secondary head does not use acceleration
1312 G450/G550 hardware can display TV picture only from secondary CRTC,
1313 and it performs no scaling, so picture must have 525 or 625 lines.
1315 config FB_MATROX_I2C
1316 tristate "Matrox I2C support"
1317 depends on FB_MATROX
1320 This drivers creates I2C buses which are needed for accessing the
1321 DDC (I2C) bus present on all Matroxes, an I2C bus which
1322 interconnects Matrox optional devices, like MGA-TVO on G200 and
1323 G400, and the secondary head DDC bus, present on G400 only.
1325 You can say Y or M here if you want to experiment with monitor
1326 detection code. You must say Y or M here if you want to use either
1327 second head of G400 or MGA-TVO on G200 or G400.
1329 If you compile it as module, it will create a module named
1332 config FB_MATROX_MAVEN
1333 tristate "G400 second head support"
1334 depends on FB_MATROX_G && FB_MATROX_I2C
1336 WARNING !!! This support does not work with G450 !!!
1338 Say Y or M here if you want to use a secondary head (meaning two
1339 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1340 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1341 secondary head output is blanked while you are in X. With XFree
1342 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1343 the fbdev driver on first head and the fbdev driver on second head.
1345 If you compile it as module, two modules are created,
1346 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1347 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1348 also load i2c-matroxfb to get it to run.
1350 The driver starts in monitor mode and you must use the matroxset
1352 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1353 PAL or NTSC or to swap primary and secondary head outputs.
1354 Secondary head driver also always start in 640x480 resolution, you
1355 must use fbset to change it.
1357 Also do not forget that second head supports only 16 and 32 bpp
1358 packed pixels, so it is a good idea to compile them into the kernel
1359 too. You can use only some font widths, as the driver uses generic
1360 painting procedures (the secondary head does not use acceleration
1364 tristate "ATI Radeon display support"
1365 depends on FB && PCI
1366 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1367 select FB_MODE_HELPERS
1368 select FB_CFB_FILLRECT
1369 select FB_CFB_COPYAREA
1370 select FB_CFB_IMAGEBLIT
1371 select FB_MACMODES if PPC_OF
1373 Choose this option if you want to use an ATI Radeon graphics card as
1374 a framebuffer device. There are both PCI and AGP versions. You
1375 don't need to choose this to run the Radeon in plain VGA mode.
1377 There is a product page at
1378 http://products.amd.com/en-us/GraphicCardResult.aspx
1380 config FB_RADEON_I2C
1381 bool "DDC/I2C for ATI Radeon support"
1382 depends on FB_RADEON
1386 Say Y here if you want DDC/I2C support for your Radeon board.
1388 config FB_RADEON_BACKLIGHT
1389 bool "Support for backlight control"
1390 depends on FB_RADEON
1393 Say Y here if you want to control the backlight of your display.
1395 config FB_RADEON_DEBUG
1396 bool "Lots of debug output from Radeon driver"
1397 depends on FB_RADEON
1400 Say Y here if you want the Radeon driver to output all sorts
1401 of debugging information to provide to the maintainer when
1402 something goes wrong.
1405 tristate "ATI Rage128 display support"
1406 depends on FB && PCI
1407 select FB_CFB_FILLRECT
1408 select FB_CFB_COPYAREA
1409 select FB_CFB_IMAGEBLIT
1410 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1411 select FB_MACMODES if PPC_PMAC
1413 This driver supports graphics boards with the ATI Rage128 chips.
1414 Say Y if you have such a graphics board and read
1415 <file:Documentation/fb/aty128fb.txt>.
1417 To compile this driver as a module, choose M here: the
1418 module will be called aty128fb.
1420 config FB_ATY128_BACKLIGHT
1421 bool "Support for backlight control"
1422 depends on FB_ATY128
1425 Say Y here if you want to control the backlight of your display.
1428 tristate "ATI Mach64 display support" if PCI || ATARI
1429 depends on FB && !SPARC32
1430 select FB_CFB_FILLRECT
1431 select FB_CFB_COPYAREA
1432 select FB_CFB_IMAGEBLIT
1433 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1434 select FB_MACMODES if PPC
1436 This driver supports graphics boards with the ATI Mach64 chips.
1437 Say Y if you have such a graphics board.
1439 To compile this driver as a module, choose M here: the
1440 module will be called atyfb.
1443 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1444 depends on PCI && FB_ATY
1445 default y if SPARC64 && PCI
1447 Say Y here to support use of ATI's 64-bit Rage boards (or other
1448 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1449 framebuffer device. The ATI product support page for these boards
1450 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1452 config FB_ATY_GENERIC_LCD
1453 bool "Mach64 generic LCD support"
1454 depends on FB_ATY_CT
1456 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1457 Rage XC, or Rage XL chipset.
1460 bool "Mach64 GX support" if PCI
1464 Say Y here to support use of the ATI Mach64 Graphics Expression
1465 board (or other boards based on the Mach64 GX chipset) as a
1466 framebuffer device. The ATI product support page for these boards
1468 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1470 config FB_ATY_BACKLIGHT
1471 bool "Support for backlight control"
1475 Say Y here if you want to control the backlight of your display.
1478 tristate "S3 Trio/Virge support"
1479 depends on FB && PCI
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1482 select FB_CFB_IMAGEBLIT
1483 select FB_TILEBLITTING
1486 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1488 Driver for graphics boards with S3 Trio / S3 Virge chip.
1491 bool "DDC for S3 support"
1496 Say Y here if you want DDC support for your S3 graphics card.
1499 tristate "S3 Savage support"
1500 depends on FB && PCI
1501 select FB_MODE_HELPERS
1502 select FB_CFB_FILLRECT
1503 select FB_CFB_COPYAREA
1504 select FB_CFB_IMAGEBLIT
1507 This driver supports notebooks and computers with S3 Savage PCI/AGP
1510 Say Y if you have such a graphics card.
1512 To compile this driver as a module, choose M here; the module
1513 will be called savagefb.
1515 config FB_SAVAGE_I2C
1516 bool "Enable DDC2 Support"
1517 depends on FB_SAVAGE
1520 This enables I2C support for S3 Savage Chipsets. This is used
1521 only for getting EDID information from the attached display
1522 allowing for robust video mode handling and switching.
1524 Because fbdev-2.6 requires that drivers must be able to
1525 independently validate video mode parameters, you should say Y
1528 config FB_SAVAGE_ACCEL
1529 bool "Enable Console Acceleration"
1530 depends on FB_SAVAGE
1533 This option will compile in console acceleration support. If
1534 the resulting framebuffer console has bothersome glitches, then
1538 tristate "SiS/XGI display support"
1539 depends on FB && PCI
1540 select FB_CFB_FILLRECT
1541 select FB_CFB_COPYAREA
1542 select FB_CFB_IMAGEBLIT
1543 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1545 This is the frame buffer device driver for the SiS 300, 315, 330
1546 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1547 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1549 To compile this driver as a module, choose M here; the module
1550 will be called sisfb.
1553 bool "SiS 300 series support"
1556 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1559 bool "SiS 315/330/340 series and XGI support"
1562 Say Y here to support use of the SiS 315, 330 and 340 series
1563 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1564 as XGI V3XT, V5, V8 and Z7.
1567 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1568 depends on FB && PCI && X86
1569 select FB_CFB_FILLRECT
1570 select FB_CFB_COPYAREA
1571 select FB_CFB_IMAGEBLIT
1576 This is the frame buffer device driver for Graphics chips of VIA
1577 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1578 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1580 Say Y if you have a VIA UniChrome graphics board.
1582 To compile this driver as a module, choose M here: the
1583 module will be called viafb.
1587 config FB_VIA_DIRECT_PROCFS
1588 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1592 Allow direct hardware access to some output registers via procfs.
1593 This is dangerous but may provide the only chance to get the
1594 correct output device configuration.
1595 Its use is strongly discouraged.
1597 config FB_VIA_X_COMPATIBILITY
1598 bool "X server compatibility"
1602 This option reduces the functionality (power saving, ...) of the
1603 framebuffer to avoid negative impact on the OpenChrome X server.
1604 If you use any X server other than fbdev you should enable this
1605 otherwise it should be safe to disable it and allow using all
1611 tristate "NeoMagic display support"
1612 depends on FB && PCI
1613 select FB_MODE_HELPERS
1614 select FB_CFB_FILLRECT
1615 select FB_CFB_COPYAREA
1616 select FB_CFB_IMAGEBLIT
1619 This driver supports notebooks with NeoMagic PCI chips.
1620 Say Y if you have such a graphics card.
1622 To compile this driver as a module, choose M here: the
1623 module will be called neofb.
1626 tristate "IMG Kyro support"
1627 depends on FB && PCI
1628 select FB_CFB_FILLRECT
1629 select FB_CFB_COPYAREA
1630 select FB_CFB_IMAGEBLIT
1632 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1635 To compile this driver as a module, choose M here: the
1636 module will be called kyrofb.
1639 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1640 depends on FB && PCI
1641 select FB_CFB_IMAGEBLIT
1642 select FB_CFB_FILLRECT
1643 select FB_CFB_COPYAREA
1644 select FB_MODE_HELPERS
1646 This driver supports graphics boards with the 3Dfx Banshee,
1647 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1648 such a graphics board.
1650 To compile this driver as a module, choose M here: the
1651 module will be called tdfxfb.
1653 config FB_3DFX_ACCEL
1654 bool "3Dfx Acceleration functions"
1657 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1658 device driver with acceleration functions.
1661 bool "Enable DDC/I2C support"
1666 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1669 tristate "3Dfx Voodoo Graphics (sst1) support"
1670 depends on FB && PCI
1671 select FB_CFB_FILLRECT
1672 select FB_CFB_COPYAREA
1673 select FB_CFB_IMAGEBLIT
1675 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1676 Voodoo2 (cvg) based graphics card.
1678 To compile this driver as a module, choose M here: the
1679 module will be called sstfb.
1681 WARNING: Do not use any application that uses the 3D engine
1682 (namely glide) while using this driver.
1683 Please read the <file:Documentation/fb/sstfb.txt> for supported
1684 options and other important info support.
1687 tristate "VIA VT8623 support"
1688 depends on FB && PCI
1689 select FB_CFB_FILLRECT
1690 select FB_CFB_COPYAREA
1691 select FB_CFB_IMAGEBLIT
1692 select FB_TILEBLITTING
1695 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1697 Driver for CastleRock integrated graphics core in the
1698 VIA VT8623 [Apollo CLE266] chipset.
1701 tristate "Trident/CyberXXX/CyberBlade support"
1702 depends on FB && PCI
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1708 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1710 There are also integrated versions of these chips called CyberXXXX,
1711 CyberImage or CyberBlade. These chips are mostly found in laptops
1712 but also on some motherboards including early VIA EPIA motherboards.
1713 For more information, read <file:Documentation/fb/tridentfb.txt>
1715 Say Y if you have such a graphics board.
1717 To compile this driver as a module, choose M here: the
1718 module will be called tridentfb.
1721 tristate "ARK 2000PV support"
1722 depends on FB && PCI
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1726 select FB_TILEBLITTING
1729 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1731 Driver for PCI graphics boards with ARK 2000PV chip
1732 and ICS 5342 RAMDAC.
1735 tristate "Permedia3 support"
1736 depends on FB && PCI
1737 select FB_CFB_FILLRECT
1738 select FB_CFB_COPYAREA
1739 select FB_CFB_IMAGEBLIT
1741 This is the frame buffer device driver for the 3DLabs Permedia3
1742 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1743 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1744 and maybe other boards.
1747 tristate "Fujitsu carmine frame buffer support"
1748 depends on FB && PCI
1749 select FB_CFB_FILLRECT
1750 select FB_CFB_COPYAREA
1751 select FB_CFB_IMAGEBLIT
1753 This is the frame buffer device driver for the Fujitsu Carmine chip.
1754 The driver provides two independent frame buffer devices.
1757 depends on FB_CARMINE
1758 prompt "DRAM timing"
1759 default FB_CARMINE_DRAM_EVAL
1761 config FB_CARMINE_DRAM_EVAL
1762 bool "Eval board timings"
1764 Use timings which work on the eval card.
1766 config CARMINE_DRAM_CUSTOM
1767 bool "Custom board timings"
1769 Use custom board timings.
1773 bool "Au1100 LCD Driver"
1774 depends on (FB = y) && MIPS_ALCHEMY
1775 select FB_CFB_FILLRECT
1776 select FB_CFB_COPYAREA
1777 select FB_CFB_IMAGEBLIT
1779 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1780 various panels and CRTs by passing in kernel cmd line option
1781 au1100fb:panel=<name>.
1784 bool "Au1200/Au1300 LCD Driver"
1785 depends on (FB = y) && MIPS_ALCHEMY
1786 select FB_SYS_FILLRECT
1787 select FB_SYS_COPYAREA
1788 select FB_SYS_IMAGEBLIT
1791 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1792 It can drive various panels and CRTs by passing in kernel cmd line
1793 option au1200fb:panel=<name>.
1796 bool "VIA VT8500 framebuffer support"
1797 depends on (FB = y) && ARM && ARCH_VT8500
1798 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1799 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1800 select FB_SYS_IMAGEBLIT
1801 select FB_MODE_HELPERS
1802 select VIDEOMODE_HELPERS
1804 This is the framebuffer driver for VIA VT8500 integrated LCD
1808 bool "Wondermedia WM8xxx-series frame buffer support"
1809 depends on (FB = y) && ARM && ARCH_VT8500
1810 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1811 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1812 select FB_SYS_IMAGEBLIT
1813 select FB_MODE_HELPERS
1814 select VIDEOMODE_HELPERS
1816 This is the framebuffer driver for WonderMedia WM8xxx-series
1817 integrated LCD controller. This driver covers the WM8505, WM8650
1820 config FB_WMT_GE_ROPS
1821 bool "VT8500/WM8xxx accelerated raster ops support"
1822 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1825 This adds support for accelerated raster operations on the
1826 VIA VT8500 and Wondermedia 85xx series SoCs.
1828 source "drivers/video/geode/Kconfig"
1831 tristate "HD64461 Frame Buffer support"
1832 depends on FB && HD64461
1833 select FB_CFB_FILLRECT
1834 select FB_CFB_COPYAREA
1835 select FB_CFB_IMAGEBLIT
1837 This is the frame buffer device driver for the Hitachi HD64461 LCD
1841 bool "PMAG-AA TURBOchannel framebuffer support"
1842 depends on (FB = y) && TC
1843 select FB_CFB_FILLRECT
1844 select FB_CFB_COPYAREA
1845 select FB_CFB_IMAGEBLIT
1847 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1848 used mainly in the MIPS-based DECstation series.
1851 tristate "PMAG-BA TURBOchannel framebuffer support"
1853 select FB_CFB_FILLRECT
1854 select FB_CFB_COPYAREA
1855 select FB_CFB_IMAGEBLIT
1857 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1858 used mainly in the MIPS-based DECstation series.
1861 tristate "PMAGB-B TURBOchannel framebuffer support"
1863 select FB_CFB_FILLRECT
1864 select FB_CFB_COPYAREA
1865 select FB_CFB_IMAGEBLIT
1867 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1868 in the MIPS-based DECstation series. The card is currently only
1869 supported in 1280x1024x8 mode.
1872 bool "Maxine (Personal DECstation) onboard framebuffer support"
1873 depends on (FB = y) && MACH_DECSTATION
1874 select FB_CFB_FILLRECT
1875 select FB_CFB_COPYAREA
1876 select FB_CFB_IMAGEBLIT
1878 Support for the onboard framebuffer (1024x768x8) in the Personal
1879 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1883 bool "G364 frame buffer support"
1884 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1885 select FB_CFB_FILLRECT
1886 select FB_CFB_COPYAREA
1887 select FB_CFB_IMAGEBLIT
1889 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1890 Olivetti M700-10 systems.
1893 bool "Motorola 68328 native frame buffer support"
1894 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1895 select FB_CFB_FILLRECT
1896 select FB_CFB_COPYAREA
1897 select FB_CFB_IMAGEBLIT
1899 Say Y here if you want to support the built-in frame buffer of
1900 the Motorola 68328 CPU family.
1903 tristate "PXA168/910 LCD framebuffer support"
1904 depends on FB && (CPU_PXA168 || CPU_PXA910)
1905 select FB_CFB_FILLRECT
1906 select FB_CFB_COPYAREA
1907 select FB_CFB_IMAGEBLIT
1909 Frame buffer driver for the built-in LCD controller in the Marvell
1913 tristate "PXA LCD framebuffer support"
1914 depends on FB && ARCH_PXA
1915 select FB_CFB_FILLRECT
1916 select FB_CFB_COPYAREA
1917 select FB_CFB_IMAGEBLIT
1919 Frame buffer driver for the built-in LCD controller in the Intel
1922 This driver is also available as a module ( = code which can be
1923 inserted and removed from the running kernel whenever you want). The
1924 module will be called pxafb. If you want to compile it as a module,
1925 say M here and read <file:Documentation/kbuild/modules.txt>.
1929 config FB_PXA_OVERLAY
1930 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1932 depends on FB_PXA && (PXA27x || PXA3xx)
1934 config FB_PXA_SMARTPANEL
1935 bool "PXA Smartpanel LCD support"
1939 config FB_PXA_PARAMETERS
1940 bool "PXA LCD command line parameters"
1944 Enable the use of kernel command line or module parameters
1945 to configure the physical properties of the LCD panel when
1946 using the PXA LCD driver.
1948 This option allows you to override the panel parameters
1949 supplied by the platform in order to support multiple
1950 different models of flatpanel. If you will only be using a
1951 single model of flatpanel then you can safely leave this
1954 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1957 tristate "PXA3xx 2D graphics accelerator driver"
1960 Kernelspace driver for the 2D graphics controller unit (GCU)
1961 found on PXA3xx processors. There is a counterpart driver in the
1962 DirectFB suite, see http://www.directfb.org/
1964 If you compile this as a module, it will be called pxa3xx_gcu.
1967 tristate "2700G LCD framebuffer support"
1968 depends on FB && ARCH_PXA
1969 select FB_CFB_FILLRECT
1970 select FB_CFB_COPYAREA
1971 select FB_CFB_IMAGEBLIT
1973 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1977 bool "Enable debugging info via debugfs"
1978 depends on FB_MBX && DEBUG_FS
1981 Enable this if you want debugging information using the debug
1982 filesystem (debugfs)
1987 tristate "Freescale DIU framebuffer support"
1988 depends on FB && FSL_SOC
1989 select FB_MODE_HELPERS
1990 select FB_CFB_FILLRECT
1991 select FB_CFB_COPYAREA
1992 select FB_CFB_IMAGEBLIT
1993 select PPC_LIB_RHEAP
1995 Framebuffer driver for the Freescale SoC DIU
1998 tristate "W100 frame buffer support"
1999 depends on FB && ARCH_PXA
2000 select FB_CFB_FILLRECT
2001 select FB_CFB_COPYAREA
2002 select FB_CFB_IMAGEBLIT
2004 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2005 It can also drive the w3220 chip found on iPAQ hx4700.
2007 This driver is also available as a module ( = code which can be
2008 inserted and removed from the running kernel whenever you want). The
2009 module will be called w100fb. If you want to compile it as a module,
2010 say M here and read <file:Documentation/kbuild/modules.txt>.
2014 config FB_SH_MOBILE_LCDC
2015 tristate "SuperH Mobile LCDC framebuffer support"
2016 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2017 select FB_SYS_FILLRECT
2018 select FB_SYS_COPYAREA
2019 select FB_SYS_IMAGEBLIT
2021 select FB_DEFERRED_IO
2023 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2025 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2027 config FB_SH_MOBILE_HDMI
2028 tristate "SuperH Mobile HDMI controller support"
2029 depends on FB_SH_MOBILE_LCDC
2030 select FB_MODE_HELPERS
2035 Driver for the on-chip SH-Mobile HDMI controller.
2038 tristate "Toshiba Mobile IO FrameBuffer support"
2039 depends on FB && MFD_CORE
2040 select FB_CFB_FILLRECT
2041 select FB_CFB_COPYAREA
2042 select FB_CFB_IMAGEBLIT
2044 Frame buffer driver for the Toshiba Mobile IO integrated as found
2045 on the Sharp SL-6000 series
2047 This driver is also available as a module ( = code which can be
2048 inserted and removed from the running kernel whenever you want). The
2049 module will be called tmiofb. If you want to compile it as a module,
2050 say M here and read <file:Documentation/kbuild/modules.txt>.
2054 config FB_TMIO_ACCELL
2055 bool "tmiofb acceleration"
2060 tristate "Samsung S3C framebuffer support"
2061 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2062 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2063 select FB_CFB_FILLRECT
2064 select FB_CFB_COPYAREA
2065 select FB_CFB_IMAGEBLIT
2067 Frame buffer driver for the built-in FB controller in the Samsung
2068 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2069 and the S3C64XX series such as the S3C6400 and S3C6410.
2071 These chips all have the same basic framebuffer design with the
2072 actual capabilities depending on the chip. For instance the S3C6400
2073 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2074 currently only have two.
2076 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2078 config FB_S3C_DEBUG_REGWRITE
2079 bool "Debug register writes"
2082 Show all register writes via pr_debug()
2085 tristate "S3C2410 LCD framebuffer support"
2086 depends on FB && ARCH_S3C24XX
2087 select FB_CFB_FILLRECT
2088 select FB_CFB_COPYAREA
2089 select FB_CFB_IMAGEBLIT
2091 Frame buffer driver for the built-in LCD controller in the Samsung
2094 This driver is also available as a module ( = code which can be
2095 inserted and removed from the running kernel whenever you want). The
2096 module will be called s3c2410fb. If you want to compile it as a module,
2097 say M here and read <file:Documentation/kbuild/modules.txt>.
2100 config FB_S3C2410_DEBUG
2101 bool "S3C2410 lcd debug messages"
2102 depends on FB_S3C2410
2104 Turn on debugging messages. Note that you can set/unset at run time
2108 bool "NUC900 LCD framebuffer support"
2109 depends on FB && ARCH_W90X900
2110 select FB_CFB_FILLRECT
2111 select FB_CFB_COPYAREA
2112 select FB_CFB_IMAGEBLIT
2114 Frame buffer driver for the built-in LCD controller in the Nuvoton
2117 config GPM1040A0_320X240
2118 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2119 depends on FB_NUC900
2121 config FB_NUC900_DEBUG
2122 bool "NUC900 lcd debug messages"
2123 depends on FB_NUC900
2125 Turn on debugging messages. Note that you can set/unset at run time
2129 tristate "Silicon Motion SM501 framebuffer support"
2130 depends on FB && MFD_SM501
2131 select FB_CFB_FILLRECT
2132 select FB_CFB_COPYAREA
2133 select FB_CFB_IMAGEBLIT
2135 Frame buffer driver for the CRT and LCD controllers in the Silicon
2138 This driver is also available as a module ( = code which can be
2139 inserted and removed from the running kernel whenever you want). The
2140 module will be called sm501fb. If you want to compile it as a module,
2141 say M here and read <file:Documentation/kbuild/modules.txt>.
2146 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2147 depends on FB && USB
2148 select FB_MODE_HELPERS
2149 select FB_SYS_FILLRECT
2150 select FB_SYS_COPYAREA
2151 select FB_SYS_IMAGEBLIT
2153 select FB_DEFERRED_IO
2155 This is a kernel framebuffer driver for SMSC UFX USB devices.
2156 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2157 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2159 To compile as a module, choose M here: the module name is smscufx.
2162 tristate "Displaylink USB Framebuffer support"
2163 depends on FB && USB
2164 select FB_MODE_HELPERS
2165 select FB_SYS_FILLRECT
2166 select FB_SYS_COPYAREA
2167 select FB_SYS_IMAGEBLIT
2169 select FB_DEFERRED_IO
2171 This is a kernel framebuffer driver for DisplayLink USB devices.
2172 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2173 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2174 To compile as a module, choose M here: the module name is udlfb.
2176 config FB_IBM_GXT4500
2177 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2178 depends on FB && PPC
2179 select FB_CFB_FILLRECT
2180 select FB_CFB_COPYAREA
2181 select FB_CFB_IMAGEBLIT
2183 Say Y here to enable support for the IBM GXT4000P/6000P and
2184 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2185 found on some IBM System P (pSeries) machines. This driver
2186 doesn't use Geometry Engine GT1000.
2189 tristate "PS3 GPU framebuffer driver"
2190 depends on FB && PS3_PS3AV
2191 select FB_SYS_FILLRECT
2192 select FB_SYS_COPYAREA
2193 select FB_SYS_IMAGEBLIT
2195 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2197 Include support for the virtual frame buffer in the PS3 platform.
2199 config FB_PS3_DEFAULT_SIZE_M
2200 int "PS3 default frame buffer size (in MiB)"
2204 This is the default size (in MiB) of the virtual frame buffer in
2206 The default value can be overridden on the kernel command line
2207 using the "ps3fb" option (e.g. "ps3fb=9M");
2210 tristate "Xilinx frame buffer support"
2211 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2212 select FB_CFB_FILLRECT
2213 select FB_CFB_COPYAREA
2214 select FB_CFB_IMAGEBLIT
2216 Include support for the Xilinx ML300/ML403 reference design
2217 framebuffer. ML300 carries a 640*480 LCD display on the board,
2218 ML403 uses a standard DB15 VGA connector.
2221 tristate "Goldfish Framebuffer"
2222 depends on FB && HAS_DMA
2223 select FB_CFB_FILLRECT
2224 select FB_CFB_COPYAREA
2225 select FB_CFB_IMAGEBLIT
2227 Framebuffer driver for Goldfish Virtual Platform
2230 tristate "Cobalt server LCD frame buffer support"
2231 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2234 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2235 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2236 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2237 select FB_CFB_FILLRECT
2238 select FB_CFB_COPYAREA
2239 select FB_CFB_IMAGEBLIT
2241 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2242 (D)STN/TFT LCD Controller.
2243 Supports display resolutions up to 1024x1024 pixel, grayscale and
2244 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2245 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2246 panels <= 320 pixel horizontal resolution.
2249 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2250 depends on FB && ARCH_DAVINCI_DA8XX
2251 select FB_CFB_FILLRECT
2252 select FB_CFB_COPYAREA
2253 select FB_CFB_IMAGEBLIT
2254 select FB_CFB_REV_PIXELS_IN_BYTE
2256 This is the frame buffer device driver for the TI LCD controller
2257 found on DA8xx/OMAP-L1xx SoCs.
2261 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2263 select FB_SYS_FILLRECT
2264 select FB_SYS_COPYAREA
2265 select FB_SYS_IMAGEBLIT
2268 This is a `virtual' frame buffer device. It operates on a chunk of
2269 unswappable kernel memory instead of on the memory of a graphics
2270 board. This means you cannot see any output sent to this frame
2271 buffer device, while it does consume precious memory. The main use
2272 of this frame buffer device is testing and debugging the frame
2273 buffer subsystem. Do NOT enable it for normal systems! To protect
2274 the innocent, it has to be enabled explicitly at boot time using the
2275 kernel option `video=vfb:'.
2277 To compile this driver as a module, choose M here: the
2278 module will be called vfb. In order to load it, you must use
2279 the vfb_enable=1 option.
2283 config XEN_FBDEV_FRONTEND
2284 tristate "Xen virtual frame buffer support"
2285 depends on FB && XEN
2286 select FB_SYS_FILLRECT
2287 select FB_SYS_COPYAREA
2288 select FB_SYS_IMAGEBLIT
2290 select FB_DEFERRED_IO
2291 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2292 select XEN_XENBUS_FRONTEND
2295 This driver implements the front-end of the Xen virtual
2296 frame buffer driver. It communicates with a back-end
2300 tristate "E-Ink Metronome/8track controller support"
2302 select FB_SYS_FILLRECT
2303 select FB_SYS_COPYAREA
2304 select FB_SYS_IMAGEBLIT
2306 select FB_DEFERRED_IO
2308 This driver implements support for the E-Ink Metronome
2309 controller. The pre-release name for this device was 8track
2310 and could also have been called by some vendors as PVI-nnnn.
2313 tristate "Fujitsu MB862xx GDC support"
2315 depends on PCI || (OF && PPC)
2316 select FB_CFB_FILLRECT
2317 select FB_CFB_COPYAREA
2318 select FB_CFB_IMAGEBLIT
2320 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2323 prompt "GDC variant"
2324 depends on FB_MB862XX
2326 config FB_MB862XX_PCI_GDC
2327 bool "Carmine/Coral-P(A) GDC"
2330 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2331 PCI graphics controller devices.
2333 config FB_MB862XX_LIME
2335 depends on OF && PPC
2336 select FB_FOREIGN_ENDIAN
2337 select FB_LITTLE_ENDIAN
2339 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2343 config FB_MB862XX_I2C
2344 bool "Support I2C bus on MB862XX GDC"
2345 depends on FB_MB862XX && I2C
2348 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2349 driver to support accessing I2C devices on controller's I2C bus.
2350 These are usually some video decoder chips.
2353 tristate "EP93XX frame buffer support"
2354 depends on FB && ARCH_EP93XX
2355 select FB_CFB_FILLRECT
2356 select FB_CFB_COPYAREA
2357 select FB_CFB_IMAGEBLIT
2359 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2360 This driver is also available as a module. The module will be called
2363 config FB_PRE_INIT_FB
2364 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2365 depends on FB && FB_MB862XX_LIME
2367 Select this option if display contents should be inherited as set by
2371 tristate "MSM Framebuffer support"
2372 depends on FB && ARCH_MSM
2373 select FB_CFB_FILLRECT
2374 select FB_CFB_COPYAREA
2375 select FB_CFB_IMAGEBLIT
2378 tristate "MX3 Framebuffer support"
2379 depends on FB && MX3_IPU
2380 select FB_CFB_FILLRECT
2381 select FB_CFB_COPYAREA
2382 select FB_CFB_IMAGEBLIT
2385 This is a framebuffer device for the i.MX31 LCD Controller. So
2386 far only synchronous displays are supported. If you plan to use
2387 an LCD display with your i.MX31 system, say Y here.
2389 config FB_BROADSHEET
2390 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2392 select FB_SYS_FILLRECT
2393 select FB_SYS_COPYAREA
2394 select FB_SYS_IMAGEBLIT
2396 select FB_DEFERRED_IO
2398 This driver implements support for the E-Ink Broadsheet
2399 controller. The release name for this device was Epson S1D13521
2400 and could also have been called by other names when coupled with
2404 tristate "AUO-K190X EPD controller support"
2406 select FB_SYS_FILLRECT
2407 select FB_SYS_COPYAREA
2408 select FB_SYS_IMAGEBLIT
2410 select FB_DEFERRED_IO
2412 Provides support for epaper controllers from the K190X series
2413 of AUO. These controllers can be used to drive epaper displays
2416 This option enables the common support, shared by the individual
2417 controller drivers. You will also have to enable the driver
2418 for the controller type used in your device.
2421 tristate "AUO-K1900 EPD controller support"
2422 depends on FB && FB_AUO_K190X
2424 This driver implements support for the AUO K1900 epd-controller.
2425 This controller can drive Sipix epaper displays but can only do
2426 serial updates, reducing the number of possible frames per second.
2429 tristate "AUO-K1901 EPD controller support"
2430 depends on FB && FB_AUO_K190X
2432 This driver implements support for the AUO K1901 epd-controller.
2433 This controller can drive Sipix epaper displays and supports
2434 concurrent updates, making higher frames per second possible.
2437 tristate "JZ4740 LCD framebuffer support"
2438 depends on FB && MACH_JZ4740
2439 select FB_SYS_FILLRECT
2440 select FB_SYS_COPYAREA
2441 select FB_SYS_IMAGEBLIT
2443 Framebuffer support for the JZ4740 SoC.
2446 tristate "MXS LCD framebuffer support"
2447 depends on FB && ARCH_MXS
2448 select FB_CFB_FILLRECT
2449 select FB_CFB_COPYAREA
2450 select FB_CFB_IMAGEBLIT
2451 select FB_MODE_HELPERS
2452 select VIDEOMODE_HELPERS
2454 Framebuffer support for the MXS SoC.
2456 config FB_PUV3_UNIGFX
2457 tristate "PKUnity v3 Unigfx framebuffer support"
2458 depends on FB && UNICORE32 && ARCH_PUV3
2459 select FB_SYS_FILLRECT
2460 select FB_SYS_COPYAREA
2461 select FB_SYS_IMAGEBLIT
2464 Choose this option if you want to use the Unigfx device as a
2465 framebuffer device. Without the support of PCI & AGP.
2468 tristate "Microsoft Hyper-V Synthetic Video support"
2469 depends on FB && HYPERV
2470 select FB_CFB_FILLRECT
2471 select FB_CFB_COPYAREA
2472 select FB_CFB_IMAGEBLIT
2474 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2477 bool "Simple framebuffer support"
2478 depends on (FB = y) && OF
2479 select FB_CFB_FILLRECT
2480 select FB_CFB_COPYAREA
2481 select FB_CFB_IMAGEBLIT
2483 Say Y if you want support for a simple frame-buffer.
2485 This driver assumes that the display hardware has been initialized
2486 before the kernel boots, and the kernel will simply render to the
2487 pre-allocated frame buffer surface.
2489 Configuration re: surface address, size, and format must be provided
2490 through device tree, or potentially plain old platform data in the
2493 source "drivers/video/omap/Kconfig"
2494 source "drivers/video/omap2/Kconfig"
2495 source "drivers/video/exynos/Kconfig"
2496 source "drivers/video/mmp/Kconfig"
2497 source "drivers/video/backlight/Kconfig"
2500 source "drivers/video/console/Kconfig"
2503 if FB || SGI_NEWPORT_CONSOLE
2504 source "drivers/video/logo/Kconfig"
2507 config FB_SH_MOBILE_MERAM
2508 tristate "SuperH Mobile MERAM read ahead support"
2509 depends on (SUPERH || ARCH_SHMOBILE)
2510 select GENERIC_ALLOCATOR
2512 Enable MERAM support for the SuperH controller.
2514 This will allow for caching of the framebuffer to provide more
2515 reliable access under heavy main memory bus traffic situations.
2516 Up to 4 memory channels can be configured, allowing 4 RGB or
2517 2 YCbCr framebuffers to be configured.
2520 tristate "Solomon SSD1307 framebuffer support"
2521 depends on FB && I2C
2525 select FB_SYS_FILLRECT
2526 select FB_SYS_COPYAREA
2527 select FB_SYS_IMAGEBLIT
2528 select FB_DEFERRED_IO
2531 This driver implements support for the Solomon SSD1307
2532 OLED controller over I2C.