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 ARM || ARM64 || COMPILE_TEST
321 depends on FB && ARM_AMBA
322 select FB_CFB_FILLRECT
323 select FB_CFB_COPYAREA
324 select FB_CFB_IMAGEBLIT
326 This framebuffer device driver is for the ARM PrimeCell PL110
327 Colour LCD controller. ARM PrimeCells provide the building
328 blocks for System on a Chip devices.
330 If you want to compile this as a module (=code which can be
331 inserted into and removed from the running kernel), say M
332 here and read <file:Documentation/kbuild/modules.txt>. The module
333 will be called amba-clcd.
336 tristate "ARM High Definition LCD support"
338 select FB_CFB_FILLRECT
339 select FB_CFB_COPYAREA
340 select FB_CFB_IMAGEBLIT
342 This framebuffer device driver is for the ARM High Definition
343 Colour LCD controller.
345 If you want to compile this as a module (=code which can be
346 inserted into and removed from the running kernel), say M
347 here and read <file:Documentation/kbuild/modules.txt>. The module
348 will be called arm-hdlcd.
351 bool "Acorn VIDC support"
352 depends on (FB = y) && ARM && ARCH_ACORN
353 select FB_CFB_FILLRECT
354 select FB_CFB_COPYAREA
355 select FB_CFB_IMAGEBLIT
357 This is the frame buffer device driver for the Acorn VIDC graphics
358 hardware found in Acorn RISC PCs and other ARM-based machines. If
362 bool "CLPS711X LCD support"
363 depends on (FB = y) && ARM && ARCH_CLPS711X
364 select FB_CFB_FILLRECT
365 select FB_CFB_COPYAREA
366 select FB_CFB_IMAGEBLIT
368 Say Y to enable the Framebuffer driver for the CLPS7111 and
372 bool "SA-1100 LCD support"
373 depends on (FB = y) && ARM && ARCH_SA1100
374 select FB_CFB_FILLRECT
375 select FB_CFB_COPYAREA
376 select FB_CFB_IMAGEBLIT
378 This is a framebuffer device for the SA-1100 LCD Controller.
379 See <http://www.linux-fbdev.org/> for information on framebuffer
382 If you plan to use the LCD display with your SA-1100 system, say
386 tristate "Freescale i.MX1/21/25/27 LCD support"
387 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
388 select FB_CFB_FILLRECT
389 select FB_CFB_COPYAREA
390 select FB_CFB_IMAGEBLIT
393 tristate "CyberPro 2000/2010/5000 support"
394 depends on FB && PCI && (BROKEN || !SPARC64)
395 select FB_CFB_FILLRECT
396 select FB_CFB_COPYAREA
397 select FB_CFB_IMAGEBLIT
399 This enables support for the Integraphics CyberPro 20x0 and 5000
400 VGA chips used in the Rebel.com Netwinder and other machines.
401 Say Y if you have a NetWinder or a graphics card containing this
402 device, otherwise say N.
404 config FB_CYBER2000_DDC
405 bool "DDC for CyberPro support"
406 depends on FB_CYBER2000
410 Say Y here if you want DDC support for your CyberPro graphics
411 card. This is only I2C bus support, driver does not use EDID.
413 config FB_CYBER2000_I2C
414 bool "CyberPro 2000/2010/5000 I2C support"
415 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
418 Enable support for the I2C video decoder interface on the
419 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
420 on the Netwinder machines for the SAA7111 video capture.
424 depends on (FB = y) && APOLLO
426 select FB_CFB_FILLRECT
427 select FB_CFB_IMAGEBLIT
431 depends on (FB = y) && Q40
433 select FB_CFB_FILLRECT
434 select FB_CFB_COPYAREA
435 select FB_CFB_IMAGEBLIT
438 tristate "Amiga native chipset support"
439 depends on FB && AMIGA
441 This is the frame buffer device driver for the builtin graphics
442 chipset found in Amigas.
444 To compile this driver as a module, choose M here: the
445 module will be called amifb.
448 bool "Amiga OCS chipset support"
451 This enables support for the original Agnus and Denise video chips,
452 found in the Amiga 1000 and most A500's and A2000's. If you intend
453 to run Linux on any of these systems, say Y; otherwise say N.
456 bool "Amiga ECS chipset support"
459 This enables support for the Enhanced Chip Set, found in later
460 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
461 you intend to run Linux on any of these systems, say Y; otherwise
465 bool "Amiga AGA chipset support"
468 This enables support for the Advanced Graphics Architecture (also
469 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
470 and CD32. If you intend to run Linux on any of these systems, say Y;
474 bool "Amiga FrameMaster II/Rainbow II support"
475 depends on (FB = y) && ZORRO
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
480 This is the frame buffer device driver for the Amiga FrameMaster
481 card from BSC (exhibited 1992 but not shipped as a CBM product).
484 tristate "Arc Monochrome LCD board support"
486 select FB_SYS_FILLRECT
487 select FB_SYS_COPYAREA
488 select FB_SYS_IMAGEBLIT
491 This enables support for the Arc Monochrome LCD board. The board
492 is based on the KS-108 lcd controller and is typically a matrix
493 of 2*n chips. This driver was tested with a 128x64 panel. This
494 driver supports it for use with x86 SBCs through a 16 bit GPIO
495 interface (8 bit data, 8 bit control). If you anticipate using
496 this driver, say Y or M; otherwise say N. You must specify the
497 GPIO IO address to be used for setting control and data.
500 bool "Atari native chipset support"
501 depends on (FB = y) && ATARI
502 select FB_CFB_FILLRECT
503 select FB_CFB_COPYAREA
504 select FB_CFB_IMAGEBLIT
506 This is the frame buffer device driver for the builtin graphics
507 chipset found in Ataris.
510 bool "Open Firmware frame buffer device support"
511 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
512 select FB_CFB_FILLRECT
513 select FB_CFB_COPYAREA
514 select FB_CFB_IMAGEBLIT
517 Say Y if you want support with Open Firmware for your graphics
521 bool "Apple \"control\" display support"
522 depends on (FB = y) && PPC_PMAC && PPC32
523 select FB_CFB_FILLRECT
524 select FB_CFB_COPYAREA
525 select FB_CFB_IMAGEBLIT
528 This driver supports a frame buffer for the graphics adapter in the
529 Power Macintosh 7300 and others.
532 bool "Apple \"platinum\" display support"
533 depends on (FB = y) && PPC_PMAC && PPC32
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
539 This driver supports a frame buffer for the "platinum" graphics
540 adapter in some Power Macintoshes.
543 bool "Apple \"valkyrie\" display support"
544 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
550 This driver supports a frame buffer for the "valkyrie" graphics
551 adapter in some Power Macintoshes.
554 bool "Chips 65550 display support"
555 depends on (FB = y) && PPC32 && PCI
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 This is the frame buffer device driver for the Chips & Technologies
561 65550 graphics chip in PowerBooks.
564 bool "Asiliant (Chips) 69000 display support"
565 depends on (FB = y) && PCI
566 select FB_CFB_FILLRECT
567 select FB_CFB_COPYAREA
568 select FB_CFB_IMAGEBLIT
570 This is the frame buffer device driver for the Asiliant 69030 chipset
573 bool "IMS Twin Turbo display support"
574 depends on (FB = y) && PCI
575 select FB_CFB_IMAGEBLIT
576 select FB_MACMODES if PPC
578 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
579 many Macintosh and compatible computers.
582 tristate "VGA 16-color graphics support"
583 depends on FB && (X86 || PPC)
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
588 select FONT_8x16 if FRAMEBUFFER_CONSOLE
590 This is the frame buffer device driver for VGA 16 color graphic
591 cards. Say Y if you have such a card.
593 To compile this driver as a module, choose M here: the
594 module will be called vga16fb.
596 config FB_BF54X_LQ043
597 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
598 depends on FB && (BF54x) && !BF542
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
603 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
605 config FB_BFIN_T350MCQB
606 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
607 depends on FB && BLACKFIN
609 select FB_CFB_FILLRECT
610 select FB_CFB_COPYAREA
611 select FB_CFB_IMAGEBLIT
613 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
614 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
615 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
617 config FB_BFIN_LQ035Q1
618 tristate "SHARP LQ035Q1DH02 TFT LCD"
619 depends on FB && BLACKFIN && SPI
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
625 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
626 the Blackfin Landscape LCD EZ-Extender Card.
627 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
628 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
630 To compile this driver as a module, choose M here: the
631 module will be called bfin-lq035q1-fb.
633 config FB_BF537_LQ035
634 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
635 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
636 select FB_CFB_FILLRECT
637 select FB_CFB_COPYAREA
638 select FB_CFB_IMAGEBLIT
641 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
644 To compile this driver as a module, choose M here: the
645 module will be called bf537-lq035.
648 tristate "Blackfin ADV7393 Video encoder"
649 depends on FB && BLACKFIN
651 select FB_CFB_FILLRECT
652 select FB_CFB_COPYAREA
653 select FB_CFB_IMAGEBLIT
655 This is the framebuffer device for a ADV7393 video encoder
656 attached to a Blackfin on the PPI port.
657 If your Blackfin board has a ADV7393 select Y.
659 To compile this driver as a module, choose M here: the
660 module will be called bfin_adv7393fb.
663 prompt "Video mode support"
664 depends on FB_BFIN_7393
674 bool 'NTSC 640x480 (Experimental)'
677 bool 'PAL 640x480 (Experimental)'
680 bool 'NTSC 720x480 YCbCR input'
683 bool 'PAL 720x576 YCbCR input'
688 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
689 depends on (FB_BFIN_7393)
690 default ADV7393_1XMEM
700 tristate "HP STI frame buffer device support"
701 depends on FB && PARISC
702 select FB_CFB_FILLRECT
703 select FB_CFB_COPYAREA
704 select FB_CFB_IMAGEBLIT
709 STI refers to the HP "Standard Text Interface" which is a set of
710 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
711 Enabling this option will implement the linux framebuffer device
712 using calls to the STI BIOS routines for initialisation.
714 If you enable this option, you will get a planar framebuffer device
715 /dev/fb which will work on the most common HP graphic cards of the
716 NGLE family, including the artist chips (in the 7xx and Bxxx series),
717 HCRX, HCRX24, CRX, CRX24 and VisEG series.
719 It is safe to enable this option, so you should probably say "Y".
722 bool "Generic Macintosh display support"
723 depends on (FB = y) && MAC
724 select FB_CFB_FILLRECT
725 select FB_CFB_COPYAREA
726 select FB_CFB_IMAGEBLIT
731 depends on (FB = y) && DIO
732 select FB_CFB_IMAGEBLIT
736 tristate "TGA/SFB+ framebuffer support"
737 depends on FB && (ALPHA || TC)
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
743 This is the frame buffer device driver for generic TGA and SFB+
744 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
745 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
746 TURBOchannel cards, also known as PMAGD-A, -B and -C.
748 Due to hardware limitations ZLX-E2 and E3 cards are not supported
749 for DECstation 5000/200 systems. Additionally due to firmware
750 limitations these cards may cause troubles with booting DECstation
751 5000/240 and /260 systems, but are fully supported under Linux if
752 you manage to get it going. ;-)
754 Say Y if you have one of those.
757 tristate "Userspace VESA VGA graphics support"
758 depends on FB && CONNECTOR
759 select FB_CFB_FILLRECT
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
762 select FB_MODE_HELPERS
764 This is the frame buffer driver for generic VBE 2.0 compliant
765 graphic cards. It can also take advantage of VBE 3.0 features,
766 such as refresh rate adjustment.
768 This driver generally provides more features than vesafb but
769 requires a userspace helper application called 'v86d'. See
770 <file:Documentation/fb/uvesafb.txt> for more information.
775 bool "VESA VGA graphics support"
776 depends on (FB = y) && X86
777 select FB_CFB_FILLRECT
778 select FB_CFB_COPYAREA
779 select FB_CFB_IMAGEBLIT
780 select FB_BOOT_VESA_SUPPORT
782 This is the frame buffer device driver for generic VESA 2.0
783 compliant graphic cards. The older VESA 1.2 cards are not supported.
784 You will get a boot time penguin logo at no additional cost. Please
785 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
788 bool "EFI-based Framebuffer Support"
789 depends on (FB = y) && X86 && EFI
790 select FB_CFB_FILLRECT
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
794 This is the EFI frame buffer device driver. If the firmware on
795 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
796 using the EFI framebuffer as your console.
799 tristate "N411 Apollo/Hecuba devkit support"
800 depends on FB && X86 && MMU
801 select FB_SYS_FILLRECT
802 select FB_SYS_COPYAREA
803 select FB_SYS_IMAGEBLIT
805 select FB_DEFERRED_IO
808 This enables support for the Apollo display controller in its
809 Hecuba form using the n411 devkit.
812 tristate "Hercules mono graphics support"
815 Say Y here if you have a Hercules mono graphics card.
817 To compile this driver as a module, choose M here: the
818 module will be called hgafb.
820 As this card technology is at least 25 years old,
821 most people will answer N here.
824 tristate "SGI Visual Workstation framebuffer support"
825 depends on FB && X86_VISWS
826 select FB_CFB_FILLRECT
827 select FB_CFB_COPYAREA
828 select FB_CFB_IMAGEBLIT
830 SGI Visual Workstation support for framebuffer graphics.
833 bool "SGI Graphics Backend frame buffer support"
834 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
839 This is the frame buffer device driver for SGI Graphics Backend.
840 This chip is used in SGI O2 and Visual Workstation 320/540.
843 int "Video memory size in MB"
847 This is the amount of memory reserved for the framebuffer,
848 which can be any value between 1MB and 8MB.
851 bool "SBUS and UPA framebuffers"
852 depends on (FB = y) && SPARC
854 Say Y if you want support for SBUS or UPA based frame buffer device.
858 depends on (FB = y) && (SPARC && FB_SBUS)
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 This is the frame buffer device driver for the BWtwo frame buffer.
866 bool "CGthree support"
867 depends on (FB = y) && (SPARC && FB_SBUS)
868 select FB_CFB_FILLRECT
869 select FB_CFB_COPYAREA
870 select FB_CFB_IMAGEBLIT
872 This is the frame buffer device driver for the CGthree frame buffer.
875 bool "CGsix (GX,TurboGX) support"
876 depends on (FB = y) && (SPARC && FB_SBUS)
877 select FB_CFB_COPYAREA
878 select FB_CFB_IMAGEBLIT
880 This is the frame buffer device driver for the CGsix (GX, TurboGX)
884 bool "Creator/Creator3D/Elite3D support"
885 depends on FB_SBUS && SPARC64
886 select FB_CFB_COPYAREA
887 select FB_CFB_IMAGEBLIT
889 This is the frame buffer device driver for the Creator, Creator3D,
890 and Elite3D graphics boards.
893 bool "TCX (SS4/SS5 only) support"
895 select FB_CFB_FILLRECT
896 select FB_CFB_COPYAREA
897 select FB_CFB_IMAGEBLIT
899 This is the frame buffer device driver for the TCX 24/8bit frame
903 bool "CGfourteen (SX) support"
905 select FB_CFB_FILLRECT
906 select FB_CFB_COPYAREA
907 select FB_CFB_IMAGEBLIT
909 This is the frame buffer device driver for the CGfourteen frame
910 buffer on Desktop SPARCsystems with the SX graphics option.
913 bool "P9100 (Sparcbook 3 only) support"
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the frame buffer device driver for the P9100 card
920 supported on Sparcbook 3 machines.
923 bool "Leo (ZX) support"
925 select FB_CFB_FILLRECT
926 select FB_CFB_COPYAREA
927 select FB_CFB_IMAGEBLIT
929 This is the frame buffer device driver for the SBUS-based Sun ZX
930 (leo) frame buffer cards.
933 bool "IGA 168x display support"
934 depends on (FB = y) && SPARC32
935 select FB_CFB_FILLRECT
936 select FB_CFB_COPYAREA
937 select FB_CFB_IMAGEBLIT
939 This is the framebuffer device for the INTERGRAPHICS 1680 and
940 successor frame buffer cards.
943 bool "Sun XVR-500 3DLABS Wildcat support"
944 depends on (FB = y) && PCI && SPARC64
945 select FB_CFB_FILLRECT
946 select FB_CFB_COPYAREA
947 select FB_CFB_IMAGEBLIT
949 This is the framebuffer device for the Sun XVR-500 and similar
950 graphics cards based upon the 3DLABS Wildcat chipset. The driver
951 only works on sparc64 systems where the system firmware has
952 mostly initialized the card already. It is treated as a
953 completely dumb framebuffer device.
956 bool "Sun XVR-2500 3DLABS Wildcat support"
957 depends on (FB = y) && PCI && SPARC64
958 select FB_CFB_FILLRECT
959 select FB_CFB_COPYAREA
960 select FB_CFB_IMAGEBLIT
962 This is the framebuffer device for the Sun XVR-2500 and similar
963 graphics cards based upon the 3DLABS Wildcat chipset. The driver
964 only works on sparc64 systems where the system firmware has
965 mostly initialized the card already. It is treated as a
966 completely dumb framebuffer device.
969 bool "Sun XVR-1000 support"
970 depends on (FB = y) && SPARC64
971 select FB_CFB_FILLRECT
972 select FB_CFB_COPYAREA
973 select FB_CFB_IMAGEBLIT
975 This is the framebuffer device for the Sun XVR-1000 and similar
976 graphics cards. The driver only works on sparc64 systems where
977 the system firmware has mostly initialized the card already. It
978 is treated as a completely dumb framebuffer device.
981 tristate "NEC PowerVR 2 display support"
982 depends on FB && SH_DREAMCAST
983 select FB_CFB_FILLRECT
984 select FB_CFB_COPYAREA
985 select FB_CFB_IMAGEBLIT
987 Say Y here if you have a PowerVR 2 card in your box. If you plan to
988 run linux on your Dreamcast, you will have to say Y here.
989 This driver may or may not work on other PowerVR 2 cards, but is
990 totally untested. Use at your own risk. If unsure, say N.
992 To compile this driver as a module, choose M here: the
993 module will be called pvr2fb.
995 You can pass several parameters to the driver at boot time or at
996 module load time. The parameters look like "video=pvr2:XXX", where
997 the meaning of XXX can be found at the end of the main source file
998 (<file:drivers/video/pvr2fb.c>). Please see the file
999 <file:Documentation/fb/pvr2fb.txt>.
1002 tristate "Epson S1D13XXX framebuffer support"
1004 select FB_CFB_FILLRECT
1005 select FB_CFB_COPYAREA
1006 select FB_CFB_IMAGEBLIT
1008 Support for S1D13XXX framebuffer device family (currently only
1009 working with S1D13806). Product specs at
1010 <http://vdc.epson.com/>
1013 tristate "AT91/AT32 LCD Controller support"
1014 depends on FB && HAVE_FB_ATMEL
1015 select FB_CFB_FILLRECT
1016 select FB_CFB_COPYAREA
1017 select FB_CFB_IMAGEBLIT
1019 This enables support for the AT91/AT32 LCD Controller.
1022 bool "Frame Buffer in internal SRAM"
1023 depends on FB_ATMEL && ARCH_AT91SAM9261
1025 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1026 to let frame buffer in external SDRAM.
1029 bool "Use a STN display with AT91/AT32 LCD Controller"
1030 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1033 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1034 Controller. Say N if you want to connect a TFT.
1039 tristate "nVidia Framebuffer Support"
1040 depends on FB && PCI
1041 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1042 select FB_MODE_HELPERS
1043 select FB_CFB_FILLRECT
1044 select FB_CFB_COPYAREA
1045 select FB_CFB_IMAGEBLIT
1049 This driver supports graphics boards with the nVidia chips, TNT
1050 and newer. For very old chipsets, such as the RIVA128, then use
1052 Say Y if you have such a graphics board.
1054 To compile this driver as a module, choose M here: the
1055 module will be called nvidiafb.
1057 config FB_NVIDIA_I2C
1058 bool "Enable DDC Support"
1059 depends on FB_NVIDIA
1062 This enables I2C support for nVidia Chipsets. This is used
1063 only for getting EDID information from the attached display
1064 allowing for robust video mode handling and switching.
1066 Because fbdev-2.6 requires that drivers must be able to
1067 independently validate video mode parameters, you should say Y
1070 config FB_NVIDIA_DEBUG
1071 bool "Lots of debug output"
1072 depends on FB_NVIDIA
1075 Say Y here if you want the nVidia driver to output all sorts
1076 of debugging information to provide to the maintainer when
1077 something goes wrong.
1079 config FB_NVIDIA_BACKLIGHT
1080 bool "Support for backlight control"
1081 depends on FB_NVIDIA
1084 Say Y here if you want to control the backlight of your display.
1087 tristate "nVidia Riva support"
1088 depends on FB && PCI
1089 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1090 select FB_MODE_HELPERS
1091 select FB_CFB_FILLRECT
1092 select FB_CFB_COPYAREA
1093 select FB_CFB_IMAGEBLIT
1097 This driver supports graphics boards with the nVidia Riva/Geforce
1099 Say Y if you have such a graphics board.
1101 To compile this driver as a module, choose M here: the
1102 module will be called rivafb.
1105 bool "Enable DDC Support"
1109 This enables I2C support for nVidia Chipsets. This is used
1110 only for getting EDID information from the attached display
1111 allowing for robust video mode handling and switching.
1113 Because fbdev-2.6 requires that drivers must be able to
1114 independently validate video mode parameters, you should say Y
1117 config FB_RIVA_DEBUG
1118 bool "Lots of debug output"
1122 Say Y here if you want the Riva driver to output all sorts
1123 of debugging information to provide to the maintainer when
1124 something goes wrong.
1126 config FB_RIVA_BACKLIGHT
1127 bool "Support for backlight control"
1131 Say Y here if you want to control the backlight of your display.
1134 tristate "Intel740 support"
1135 depends on FB && PCI
1136 select FB_MODE_HELPERS
1137 select FB_CFB_FILLRECT
1138 select FB_CFB_COPYAREA
1139 select FB_CFB_IMAGEBLIT
1143 This driver supports graphics cards based on Intel740 chip.
1146 tristate "Intel 810/815 support"
1147 depends on FB && PCI && X86_32 && AGP_INTEL
1148 select FB_MODE_HELPERS
1149 select FB_CFB_FILLRECT
1150 select FB_CFB_COPYAREA
1151 select FB_CFB_IMAGEBLIT
1154 This driver supports the on-board graphics built in to the Intel 810
1155 and 815 chipsets. Say Y if you have and plan to use such a board.
1157 To compile this driver as a module, choose M here: the
1158 module will be called i810fb.
1160 For more information, please read
1161 <file:Documentation/fb/intel810.txt>
1164 bool "use VESA Generalized Timing Formula"
1167 If you say Y, then the VESA standard, Generalized Timing Formula
1168 or GTF, will be used to calculate the required video timing values
1169 per video mode. Since the GTF allows nondiscrete timings
1170 (nondiscrete being a range of values as opposed to discrete being a
1171 set of values), you'll be able to use any combination of horizontal
1172 and vertical resolutions, and vertical refresh rates without having
1173 to specify your own timing parameters. This is especially useful
1174 to maximize the performance of an aging display, or if you just
1175 have a display with nonstandard dimensions. A VESA compliant
1176 monitor is recommended, but can still work with non-compliant ones.
1177 If you need or want this, then select this option. The timings may
1178 not be compliant with Intel's recommended values. Use at your own
1181 If you say N, the driver will revert to discrete video timings
1182 using a set recommended by Intel in their documentation.
1187 bool "Enable DDC Support"
1188 depends on FB_I810 && FB_I810_GTF
1193 tristate "Intel LE80578 (Vermilion) support"
1194 depends on FB && PCI && X86
1195 select FB_MODE_HELPERS
1196 select FB_CFB_FILLRECT
1197 select FB_CFB_COPYAREA
1198 select FB_CFB_IMAGEBLIT
1200 This driver supports the LE80578 (Vermilion Range) chipset
1202 config FB_CARILLO_RANCH
1203 tristate "Intel Carillo Ranch support"
1204 depends on FB_LE80578 && FB && PCI && X86
1206 This driver supports the LE80578 (Carillo Ranch) board
1209 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1210 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1211 select FB_MODE_HELPERS
1212 select FB_CFB_FILLRECT
1213 select FB_CFB_COPYAREA
1214 select FB_CFB_IMAGEBLIT
1215 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1216 depends on !DRM_I915
1218 This driver supports the on-board graphics built in to the Intel
1219 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1220 Say Y if you have and plan to use such a board.
1222 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1224 To compile this driver as a module, choose M here: the
1225 module will be called intelfb.
1227 For more information, please read <file:Documentation/fb/intelfb.txt>
1229 config FB_INTEL_DEBUG
1230 bool "Intel driver Debug Messages"
1233 Say Y here if you want the Intel driver to output all sorts
1234 of debugging information to provide to the maintainer when
1235 something goes wrong.
1238 bool "DDC/I2C for Intel framebuffer support"
1243 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1246 tristate "Matrox acceleration"
1247 depends on FB && PCI
1248 select FB_CFB_FILLRECT
1249 select FB_CFB_COPYAREA
1250 select FB_CFB_IMAGEBLIT
1251 select FB_TILEBLITTING
1252 select FB_MACMODES if PPC_PMAC
1254 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1255 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1256 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1257 Matrox G400, G450 or G550 card in your box.
1259 To compile this driver as a module, choose M here: the
1260 module will be called matroxfb.
1262 You can pass several parameters to the driver at boot time or at
1263 module load time. The parameters look like "video=matroxfb:XXX", and
1264 are described in <file:Documentation/fb/matroxfb.txt>.
1266 config FB_MATROX_MILLENIUM
1267 bool "Millennium I/II support"
1268 depends on FB_MATROX
1270 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1271 video card. If you select "Advanced lowlevel driver options" below,
1272 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1273 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1274 also use font widths different from 8.
1276 config FB_MATROX_MYSTIQUE
1277 bool "Mystique support"
1278 depends on FB_MATROX
1280 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1281 video card. If you select "Advanced lowlevel driver options" below,
1282 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1283 packed pixel and 32 bpp packed pixel. You can also use font widths
1287 bool "G100/G200/G400/G450/G550 support"
1288 depends on FB_MATROX
1290 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1291 video card. If you select "Advanced lowlevel driver options", you
1292 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1293 pixel and 32 bpp packed pixel. You can also use font widths
1296 If you need support for G400 secondary head, you must say Y to
1297 "Matrox I2C support" and "G400 second head support" right below.
1298 G450/G550 secondary head and digital output are supported without
1301 The driver starts in monitor mode. You must use the matroxset tool
1302 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1303 swap primary and secondary head outputs, or to change output mode.
1304 Secondary head driver always start in 640x480 resolution and you
1305 must use fbset to change it.
1307 Do not forget that second head supports only 16 and 32 bpp
1308 packed pixels, so it is a good idea to compile them into the kernel
1309 too. You can use only some font widths, as the driver uses generic
1310 painting procedures (the secondary head does not use acceleration
1313 G450/G550 hardware can display TV picture only from secondary CRTC,
1314 and it performs no scaling, so picture must have 525 or 625 lines.
1316 config FB_MATROX_I2C
1317 tristate "Matrox I2C support"
1318 depends on FB_MATROX
1321 This drivers creates I2C buses which are needed for accessing the
1322 DDC (I2C) bus present on all Matroxes, an I2C bus which
1323 interconnects Matrox optional devices, like MGA-TVO on G200 and
1324 G400, and the secondary head DDC bus, present on G400 only.
1326 You can say Y or M here if you want to experiment with monitor
1327 detection code. You must say Y or M here if you want to use either
1328 second head of G400 or MGA-TVO on G200 or G400.
1330 If you compile it as module, it will create a module named
1333 config FB_MATROX_MAVEN
1334 tristate "G400 second head support"
1335 depends on FB_MATROX_G && FB_MATROX_I2C
1337 WARNING !!! This support does not work with G450 !!!
1339 Say Y or M here if you want to use a secondary head (meaning two
1340 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1341 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1342 secondary head output is blanked while you are in X. With XFree
1343 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1344 the fbdev driver on first head and the fbdev driver on second head.
1346 If you compile it as module, two modules are created,
1347 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1348 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1349 also load i2c-matroxfb to get it to run.
1351 The driver starts in monitor mode and you must use the matroxset
1353 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1354 PAL or NTSC or to swap primary and secondary head outputs.
1355 Secondary head driver also always start in 640x480 resolution, you
1356 must use fbset to change it.
1358 Also do not forget that second head supports only 16 and 32 bpp
1359 packed pixels, so it is a good idea to compile them into the kernel
1360 too. You can use only some font widths, as the driver uses generic
1361 painting procedures (the secondary head does not use acceleration
1365 tristate "ATI Radeon display support"
1366 depends on FB && PCI
1367 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1368 select FB_MODE_HELPERS
1369 select FB_CFB_FILLRECT
1370 select FB_CFB_COPYAREA
1371 select FB_CFB_IMAGEBLIT
1372 select FB_MACMODES if PPC_OF
1374 Choose this option if you want to use an ATI Radeon graphics card as
1375 a framebuffer device. There are both PCI and AGP versions. You
1376 don't need to choose this to run the Radeon in plain VGA mode.
1378 There is a product page at
1379 http://products.amd.com/en-us/GraphicCardResult.aspx
1381 config FB_RADEON_I2C
1382 bool "DDC/I2C for ATI Radeon support"
1383 depends on FB_RADEON
1387 Say Y here if you want DDC/I2C support for your Radeon board.
1389 config FB_RADEON_BACKLIGHT
1390 bool "Support for backlight control"
1391 depends on FB_RADEON
1394 Say Y here if you want to control the backlight of your display.
1396 config FB_RADEON_DEBUG
1397 bool "Lots of debug output from Radeon driver"
1398 depends on FB_RADEON
1401 Say Y here if you want the Radeon driver to output all sorts
1402 of debugging information to provide to the maintainer when
1403 something goes wrong.
1406 tristate "ATI Rage128 display support"
1407 depends on FB && PCI
1408 select FB_CFB_FILLRECT
1409 select FB_CFB_COPYAREA
1410 select FB_CFB_IMAGEBLIT
1411 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1412 select FB_MACMODES if PPC_PMAC
1414 This driver supports graphics boards with the ATI Rage128 chips.
1415 Say Y if you have such a graphics board and read
1416 <file:Documentation/fb/aty128fb.txt>.
1418 To compile this driver as a module, choose M here: the
1419 module will be called aty128fb.
1421 config FB_ATY128_BACKLIGHT
1422 bool "Support for backlight control"
1423 depends on FB_ATY128
1426 Say Y here if you want to control the backlight of your display.
1429 tristate "ATI Mach64 display support" if PCI || ATARI
1430 depends on FB && !SPARC32
1431 select FB_CFB_FILLRECT
1432 select FB_CFB_COPYAREA
1433 select FB_CFB_IMAGEBLIT
1434 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1435 select FB_MACMODES if PPC
1437 This driver supports graphics boards with the ATI Mach64 chips.
1438 Say Y if you have such a graphics board.
1440 To compile this driver as a module, choose M here: the
1441 module will be called atyfb.
1444 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1445 depends on PCI && FB_ATY
1446 default y if SPARC64 && PCI
1448 Say Y here to support use of ATI's 64-bit Rage boards (or other
1449 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1450 framebuffer device. The ATI product support page for these boards
1451 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1453 config FB_ATY_GENERIC_LCD
1454 bool "Mach64 generic LCD support"
1455 depends on FB_ATY_CT
1457 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1458 Rage XC, or Rage XL chipset.
1461 bool "Mach64 GX support" if PCI
1465 Say Y here to support use of the ATI Mach64 Graphics Expression
1466 board (or other boards based on the Mach64 GX chipset) as a
1467 framebuffer device. The ATI product support page for these boards
1469 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1471 config FB_ATY_BACKLIGHT
1472 bool "Support for backlight control"
1476 Say Y here if you want to control the backlight of your display.
1479 tristate "S3 Trio/Virge support"
1480 depends on FB && PCI
1481 select FB_CFB_FILLRECT
1482 select FB_CFB_COPYAREA
1483 select FB_CFB_IMAGEBLIT
1484 select FB_TILEBLITTING
1487 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1489 Driver for graphics boards with S3 Trio / S3 Virge chip.
1492 bool "DDC for S3 support"
1497 Say Y here if you want DDC support for your S3 graphics card.
1500 tristate "S3 Savage support"
1501 depends on FB && PCI
1502 select FB_MODE_HELPERS
1503 select FB_CFB_FILLRECT
1504 select FB_CFB_COPYAREA
1505 select FB_CFB_IMAGEBLIT
1508 This driver supports notebooks and computers with S3 Savage PCI/AGP
1511 Say Y if you have such a graphics card.
1513 To compile this driver as a module, choose M here; the module
1514 will be called savagefb.
1516 config FB_SAVAGE_I2C
1517 bool "Enable DDC2 Support"
1518 depends on FB_SAVAGE
1521 This enables I2C support for S3 Savage Chipsets. This is used
1522 only for getting EDID information from the attached display
1523 allowing for robust video mode handling and switching.
1525 Because fbdev-2.6 requires that drivers must be able to
1526 independently validate video mode parameters, you should say Y
1529 config FB_SAVAGE_ACCEL
1530 bool "Enable Console Acceleration"
1531 depends on FB_SAVAGE
1534 This option will compile in console acceleration support. If
1535 the resulting framebuffer console has bothersome glitches, then
1539 tristate "SiS/XGI display support"
1540 depends on FB && PCI
1541 select FB_CFB_FILLRECT
1542 select FB_CFB_COPYAREA
1543 select FB_CFB_IMAGEBLIT
1544 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1546 This is the frame buffer device driver for the SiS 300, 315, 330
1547 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1548 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1550 To compile this driver as a module, choose M here; the module
1551 will be called sisfb.
1554 bool "SiS 300 series support"
1557 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1560 bool "SiS 315/330/340 series and XGI support"
1563 Say Y here to support use of the SiS 315, 330 and 340 series
1564 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1565 as XGI V3XT, V5, V8 and Z7.
1568 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1569 depends on FB && PCI && X86
1570 select FB_CFB_FILLRECT
1571 select FB_CFB_COPYAREA
1572 select FB_CFB_IMAGEBLIT
1577 This is the frame buffer device driver for Graphics chips of VIA
1578 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1579 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1581 Say Y if you have a VIA UniChrome graphics board.
1583 To compile this driver as a module, choose M here: the
1584 module will be called viafb.
1588 config FB_VIA_DIRECT_PROCFS
1589 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1593 Allow direct hardware access to some output registers via procfs.
1594 This is dangerous but may provide the only chance to get the
1595 correct output device configuration.
1596 Its use is strongly discouraged.
1598 config FB_VIA_X_COMPATIBILITY
1599 bool "X server compatibility"
1603 This option reduces the functionality (power saving, ...) of the
1604 framebuffer to avoid negative impact on the OpenChrome X server.
1605 If you use any X server other than fbdev you should enable this
1606 otherwise it should be safe to disable it and allow using all
1612 tristate "NeoMagic display support"
1613 depends on FB && PCI
1614 select FB_MODE_HELPERS
1615 select FB_CFB_FILLRECT
1616 select FB_CFB_COPYAREA
1617 select FB_CFB_IMAGEBLIT
1620 This driver supports notebooks with NeoMagic PCI chips.
1621 Say Y if you have such a graphics card.
1623 To compile this driver as a module, choose M here: the
1624 module will be called neofb.
1627 tristate "IMG Kyro support"
1628 depends on FB && PCI
1629 select FB_CFB_FILLRECT
1630 select FB_CFB_COPYAREA
1631 select FB_CFB_IMAGEBLIT
1633 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1636 To compile this driver as a module, choose M here: the
1637 module will be called kyrofb.
1640 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1641 depends on FB && PCI
1642 select FB_CFB_IMAGEBLIT
1643 select FB_CFB_FILLRECT
1644 select FB_CFB_COPYAREA
1645 select FB_MODE_HELPERS
1647 This driver supports graphics boards with the 3Dfx Banshee,
1648 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1649 such a graphics board.
1651 To compile this driver as a module, choose M here: the
1652 module will be called tdfxfb.
1654 config FB_3DFX_ACCEL
1655 bool "3Dfx Acceleration functions"
1658 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1659 device driver with acceleration functions.
1662 bool "Enable DDC/I2C support"
1667 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1670 tristate "3Dfx Voodoo Graphics (sst1) support"
1671 depends on FB && PCI
1672 select FB_CFB_FILLRECT
1673 select FB_CFB_COPYAREA
1674 select FB_CFB_IMAGEBLIT
1676 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1677 Voodoo2 (cvg) based graphics card.
1679 To compile this driver as a module, choose M here: the
1680 module will be called sstfb.
1682 WARNING: Do not use any application that uses the 3D engine
1683 (namely glide) while using this driver.
1684 Please read the <file:Documentation/fb/sstfb.txt> for supported
1685 options and other important info support.
1688 tristate "VIA VT8623 support"
1689 depends on FB && PCI
1690 select FB_CFB_FILLRECT
1691 select FB_CFB_COPYAREA
1692 select FB_CFB_IMAGEBLIT
1693 select FB_TILEBLITTING
1696 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1698 Driver for CastleRock integrated graphics core in the
1699 VIA VT8623 [Apollo CLE266] chipset.
1702 tristate "Trident/CyberXXX/CyberBlade support"
1703 depends on FB && PCI
1704 select FB_CFB_FILLRECT
1705 select FB_CFB_COPYAREA
1706 select FB_CFB_IMAGEBLIT
1708 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1709 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1711 There are also integrated versions of these chips called CyberXXXX,
1712 CyberImage or CyberBlade. These chips are mostly found in laptops
1713 but also on some motherboards including early VIA EPIA motherboards.
1714 For more information, read <file:Documentation/fb/tridentfb.txt>
1716 Say Y if you have such a graphics board.
1718 To compile this driver as a module, choose M here: the
1719 module will be called tridentfb.
1722 tristate "ARK 2000PV support"
1723 depends on FB && PCI
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1727 select FB_TILEBLITTING
1730 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1732 Driver for PCI graphics boards with ARK 2000PV chip
1733 and ICS 5342 RAMDAC.
1736 tristate "Permedia3 support"
1737 depends on FB && PCI
1738 select FB_CFB_FILLRECT
1739 select FB_CFB_COPYAREA
1740 select FB_CFB_IMAGEBLIT
1742 This is the frame buffer device driver for the 3DLabs Permedia3
1743 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1744 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1745 and maybe other boards.
1748 tristate "Fujitsu carmine frame buffer support"
1749 depends on FB && PCI
1750 select FB_CFB_FILLRECT
1751 select FB_CFB_COPYAREA
1752 select FB_CFB_IMAGEBLIT
1754 This is the frame buffer device driver for the Fujitsu Carmine chip.
1755 The driver provides two independent frame buffer devices.
1758 depends on FB_CARMINE
1759 prompt "DRAM timing"
1760 default FB_CARMINE_DRAM_EVAL
1762 config FB_CARMINE_DRAM_EVAL
1763 bool "Eval board timings"
1765 Use timings which work on the eval card.
1767 config CARMINE_DRAM_CUSTOM
1768 bool "Custom board timings"
1770 Use custom board timings.
1774 bool "Au1100 LCD Driver"
1775 depends on (FB = y) && MIPS_ALCHEMY
1776 select FB_CFB_FILLRECT
1777 select FB_CFB_COPYAREA
1778 select FB_CFB_IMAGEBLIT
1780 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1781 various panels and CRTs by passing in kernel cmd line option
1782 au1100fb:panel=<name>.
1785 bool "Au1200/Au1300 LCD Driver"
1786 depends on (FB = y) && MIPS_ALCHEMY
1787 select FB_SYS_FILLRECT
1788 select FB_SYS_COPYAREA
1789 select FB_SYS_IMAGEBLIT
1792 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1793 It can drive various panels and CRTs by passing in kernel cmd line
1794 option au1200fb:panel=<name>.
1797 bool "VIA VT8500 framebuffer support"
1798 depends on (FB = y) && ARM && ARCH_VT8500
1799 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1800 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1801 select FB_SYS_IMAGEBLIT
1802 select FB_MODE_HELPERS
1803 select VIDEOMODE_HELPERS
1805 This is the framebuffer driver for VIA VT8500 integrated LCD
1809 bool "Wondermedia WM8xxx-series frame buffer support"
1810 depends on (FB = y) && ARM && ARCH_VT8500
1811 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1812 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1813 select FB_SYS_IMAGEBLIT
1814 select FB_MODE_HELPERS
1815 select VIDEOMODE_HELPERS
1817 This is the framebuffer driver for WonderMedia WM8xxx-series
1818 integrated LCD controller. This driver covers the WM8505, WM8650
1821 config FB_WMT_GE_ROPS
1822 bool "VT8500/WM8xxx accelerated raster ops support"
1823 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1826 This adds support for accelerated raster operations on the
1827 VIA VT8500 and Wondermedia 85xx series SoCs.
1829 source "drivers/video/geode/Kconfig"
1832 tristate "HD64461 Frame Buffer support"
1833 depends on FB && HD64461
1834 select FB_CFB_FILLRECT
1835 select FB_CFB_COPYAREA
1836 select FB_CFB_IMAGEBLIT
1838 This is the frame buffer device driver for the Hitachi HD64461 LCD
1842 bool "PMAG-AA TURBOchannel framebuffer support"
1843 depends on (FB = y) && TC
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1849 used mainly in the MIPS-based DECstation series.
1852 tristate "PMAG-BA TURBOchannel framebuffer support"
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1859 used mainly in the MIPS-based DECstation series.
1862 tristate "PMAGB-B TURBOchannel framebuffer support"
1864 select FB_CFB_FILLRECT
1865 select FB_CFB_COPYAREA
1866 select FB_CFB_IMAGEBLIT
1868 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1869 in the MIPS-based DECstation series. The card is currently only
1870 supported in 1280x1024x8 mode.
1873 bool "Maxine (Personal DECstation) onboard framebuffer support"
1874 depends on (FB = y) && MACH_DECSTATION
1875 select FB_CFB_FILLRECT
1876 select FB_CFB_COPYAREA
1877 select FB_CFB_IMAGEBLIT
1879 Support for the onboard framebuffer (1024x768x8) in the Personal
1880 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1884 bool "G364 frame buffer support"
1885 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1886 select FB_CFB_FILLRECT
1887 select FB_CFB_COPYAREA
1888 select FB_CFB_IMAGEBLIT
1890 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1891 Olivetti M700-10 systems.
1894 bool "Motorola 68328 native frame buffer support"
1895 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1896 select FB_CFB_FILLRECT
1897 select FB_CFB_COPYAREA
1898 select FB_CFB_IMAGEBLIT
1900 Say Y here if you want to support the built-in frame buffer of
1901 the Motorola 68328 CPU family.
1904 tristate "PXA168/910 LCD framebuffer support"
1905 depends on FB && (CPU_PXA168 || CPU_PXA910)
1906 select FB_CFB_FILLRECT
1907 select FB_CFB_COPYAREA
1908 select FB_CFB_IMAGEBLIT
1910 Frame buffer driver for the built-in LCD controller in the Marvell
1914 tristate "PXA LCD framebuffer support"
1915 depends on FB && ARCH_PXA
1916 select FB_CFB_FILLRECT
1917 select FB_CFB_COPYAREA
1918 select FB_CFB_IMAGEBLIT
1920 Frame buffer driver for the built-in LCD controller in the Intel
1923 This driver is also available as a module ( = code which can be
1924 inserted and removed from the running kernel whenever you want). The
1925 module will be called pxafb. If you want to compile it as a module,
1926 say M here and read <file:Documentation/kbuild/modules.txt>.
1930 config FB_PXA_OVERLAY
1931 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1933 depends on FB_PXA && (PXA27x || PXA3xx)
1935 config FB_PXA_SMARTPANEL
1936 bool "PXA Smartpanel LCD support"
1940 config FB_PXA_PARAMETERS
1941 bool "PXA LCD command line parameters"
1945 Enable the use of kernel command line or module parameters
1946 to configure the physical properties of the LCD panel when
1947 using the PXA LCD driver.
1949 This option allows you to override the panel parameters
1950 supplied by the platform in order to support multiple
1951 different models of flatpanel. If you will only be using a
1952 single model of flatpanel then you can safely leave this
1955 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1958 tristate "PXA3xx 2D graphics accelerator driver"
1961 Kernelspace driver for the 2D graphics controller unit (GCU)
1962 found on PXA3xx processors. There is a counterpart driver in the
1963 DirectFB suite, see http://www.directfb.org/
1965 If you compile this as a module, it will be called pxa3xx_gcu.
1968 tristate "2700G LCD framebuffer support"
1969 depends on FB && ARCH_PXA
1970 select FB_CFB_FILLRECT
1971 select FB_CFB_COPYAREA
1972 select FB_CFB_IMAGEBLIT
1974 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1978 bool "Enable debugging info via debugfs"
1979 depends on FB_MBX && DEBUG_FS
1982 Enable this if you want debugging information using the debug
1983 filesystem (debugfs)
1988 tristate "Freescale DIU framebuffer support"
1989 depends on FB && FSL_SOC
1990 select FB_MODE_HELPERS
1991 select FB_CFB_FILLRECT
1992 select FB_CFB_COPYAREA
1993 select FB_CFB_IMAGEBLIT
1994 select PPC_LIB_RHEAP
1996 Framebuffer driver for the Freescale SoC DIU
1999 tristate "W100 frame buffer support"
2000 depends on FB && ARCH_PXA
2001 select FB_CFB_FILLRECT
2002 select FB_CFB_COPYAREA
2003 select FB_CFB_IMAGEBLIT
2005 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2006 It can also drive the w3220 chip found on iPAQ hx4700.
2008 This driver is also available as a module ( = code which can be
2009 inserted and removed from the running kernel whenever you want). The
2010 module will be called w100fb. If you want to compile it as a module,
2011 say M here and read <file:Documentation/kbuild/modules.txt>.
2015 config FB_SH_MOBILE_LCDC
2016 tristate "SuperH Mobile LCDC framebuffer support"
2017 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2018 select FB_SYS_FILLRECT
2019 select FB_SYS_COPYAREA
2020 select FB_SYS_IMAGEBLIT
2022 select FB_DEFERRED_IO
2024 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2026 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2028 config FB_SH_MOBILE_HDMI
2029 tristate "SuperH Mobile HDMI controller support"
2030 depends on FB_SH_MOBILE_LCDC
2031 select FB_MODE_HELPERS
2036 Driver for the on-chip SH-Mobile HDMI controller.
2039 tristate "Toshiba Mobile IO FrameBuffer support"
2040 depends on FB && MFD_CORE
2041 select FB_CFB_FILLRECT
2042 select FB_CFB_COPYAREA
2043 select FB_CFB_IMAGEBLIT
2045 Frame buffer driver for the Toshiba Mobile IO integrated as found
2046 on the Sharp SL-6000 series
2048 This driver is also available as a module ( = code which can be
2049 inserted and removed from the running kernel whenever you want). The
2050 module will be called tmiofb. If you want to compile it as a module,
2051 say M here and read <file:Documentation/kbuild/modules.txt>.
2055 config FB_TMIO_ACCELL
2056 bool "tmiofb acceleration"
2061 tristate "Samsung S3C framebuffer support"
2062 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2063 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2064 select FB_CFB_FILLRECT
2065 select FB_CFB_COPYAREA
2066 select FB_CFB_IMAGEBLIT
2068 Frame buffer driver for the built-in FB controller in the Samsung
2069 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2070 and the S3C64XX series such as the S3C6400 and S3C6410.
2072 These chips all have the same basic framebuffer design with the
2073 actual capabilities depending on the chip. For instance the S3C6400
2074 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2075 currently only have two.
2077 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2079 config FB_S3C_DEBUG_REGWRITE
2080 bool "Debug register writes"
2083 Show all register writes via pr_debug()
2086 tristate "S3C2410 LCD framebuffer support"
2087 depends on FB && ARCH_S3C24XX
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 Samsung
2095 This driver is also available as a module ( = code which can be
2096 inserted and removed from the running kernel whenever you want). The
2097 module will be called s3c2410fb. If you want to compile it as a module,
2098 say M here and read <file:Documentation/kbuild/modules.txt>.
2101 config FB_S3C2410_DEBUG
2102 bool "S3C2410 lcd debug messages"
2103 depends on FB_S3C2410
2105 Turn on debugging messages. Note that you can set/unset at run time
2109 bool "NUC900 LCD framebuffer support"
2110 depends on FB && ARCH_W90X900
2111 select FB_CFB_FILLRECT
2112 select FB_CFB_COPYAREA
2113 select FB_CFB_IMAGEBLIT
2115 Frame buffer driver for the built-in LCD controller in the Nuvoton
2118 config GPM1040A0_320X240
2119 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2120 depends on FB_NUC900
2122 config FB_NUC900_DEBUG
2123 bool "NUC900 lcd debug messages"
2124 depends on FB_NUC900
2126 Turn on debugging messages. Note that you can set/unset at run time
2130 tristate "Silicon Motion SM501 framebuffer support"
2131 depends on FB && MFD_SM501
2132 select FB_CFB_FILLRECT
2133 select FB_CFB_COPYAREA
2134 select FB_CFB_IMAGEBLIT
2136 Frame buffer driver for the CRT and LCD controllers in the Silicon
2139 This driver is also available as a module ( = code which can be
2140 inserted and removed from the running kernel whenever you want). The
2141 module will be called sm501fb. If you want to compile it as a module,
2142 say M here and read <file:Documentation/kbuild/modules.txt>.
2147 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2148 depends on FB && USB
2149 select FB_MODE_HELPERS
2150 select FB_SYS_FILLRECT
2151 select FB_SYS_COPYAREA
2152 select FB_SYS_IMAGEBLIT
2154 select FB_DEFERRED_IO
2156 This is a kernel framebuffer driver for SMSC UFX USB devices.
2157 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2158 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2160 To compile as a module, choose M here: the module name is smscufx.
2163 tristate "Displaylink USB Framebuffer support"
2164 depends on FB && USB
2165 select FB_MODE_HELPERS
2166 select FB_SYS_FILLRECT
2167 select FB_SYS_COPYAREA
2168 select FB_SYS_IMAGEBLIT
2170 select FB_DEFERRED_IO
2172 This is a kernel framebuffer driver for DisplayLink USB devices.
2173 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2174 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2175 To compile as a module, choose M here: the module name is udlfb.
2177 config FB_IBM_GXT4500
2178 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2179 depends on FB && PPC
2180 select FB_CFB_FILLRECT
2181 select FB_CFB_COPYAREA
2182 select FB_CFB_IMAGEBLIT
2184 Say Y here to enable support for the IBM GXT4000P/6000P and
2185 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2186 found on some IBM System P (pSeries) machines. This driver
2187 doesn't use Geometry Engine GT1000.
2190 tristate "PS3 GPU framebuffer driver"
2191 depends on FB && PS3_PS3AV
2192 select FB_SYS_FILLRECT
2193 select FB_SYS_COPYAREA
2194 select FB_SYS_IMAGEBLIT
2196 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2198 Include support for the virtual frame buffer in the PS3 platform.
2200 config FB_PS3_DEFAULT_SIZE_M
2201 int "PS3 default frame buffer size (in MiB)"
2205 This is the default size (in MiB) of the virtual frame buffer in
2207 The default value can be overridden on the kernel command line
2208 using the "ps3fb" option (e.g. "ps3fb=9M");
2211 tristate "Xilinx frame buffer support"
2212 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2213 select FB_CFB_FILLRECT
2214 select FB_CFB_COPYAREA
2215 select FB_CFB_IMAGEBLIT
2217 Include support for the Xilinx ML300/ML403 reference design
2218 framebuffer. ML300 carries a 640*480 LCD display on the board,
2219 ML403 uses a standard DB15 VGA connector.
2222 tristate "Goldfish Framebuffer"
2223 depends on FB && HAS_DMA
2224 select FB_CFB_FILLRECT
2225 select FB_CFB_COPYAREA
2226 select FB_CFB_IMAGEBLIT
2228 Framebuffer driver for Goldfish Virtual Platform
2231 tristate "Cobalt server LCD frame buffer support"
2232 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2235 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2236 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2237 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2238 select FB_CFB_FILLRECT
2239 select FB_CFB_COPYAREA
2240 select FB_CFB_IMAGEBLIT
2242 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2243 (D)STN/TFT LCD Controller.
2244 Supports display resolutions up to 1024x1024 pixel, grayscale and
2245 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2246 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2247 panels <= 320 pixel horizontal resolution.
2250 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2251 depends on FB && ARCH_DAVINCI_DA8XX
2252 select FB_CFB_FILLRECT
2253 select FB_CFB_COPYAREA
2254 select FB_CFB_IMAGEBLIT
2255 select FB_CFB_REV_PIXELS_IN_BYTE
2257 This is the frame buffer device driver for the TI LCD controller
2258 found on DA8xx/OMAP-L1xx SoCs.
2262 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2264 select FB_SYS_FILLRECT
2265 select FB_SYS_COPYAREA
2266 select FB_SYS_IMAGEBLIT
2269 This is a `virtual' frame buffer device. It operates on a chunk of
2270 unswappable kernel memory instead of on the memory of a graphics
2271 board. This means you cannot see any output sent to this frame
2272 buffer device, while it does consume precious memory. The main use
2273 of this frame buffer device is testing and debugging the frame
2274 buffer subsystem. Do NOT enable it for normal systems! To protect
2275 the innocent, it has to be enabled explicitly at boot time using the
2276 kernel option `video=vfb:'.
2278 To compile this driver as a module, choose M here: the
2279 module will be called vfb. In order to load it, you must use
2280 the vfb_enable=1 option.
2284 config XEN_FBDEV_FRONTEND
2285 tristate "Xen virtual frame buffer support"
2286 depends on FB && XEN
2287 select FB_SYS_FILLRECT
2288 select FB_SYS_COPYAREA
2289 select FB_SYS_IMAGEBLIT
2291 select FB_DEFERRED_IO
2292 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2293 select XEN_XENBUS_FRONTEND
2296 This driver implements the front-end of the Xen virtual
2297 frame buffer driver. It communicates with a back-end
2301 tristate "E-Ink Metronome/8track controller support"
2303 select FB_SYS_FILLRECT
2304 select FB_SYS_COPYAREA
2305 select FB_SYS_IMAGEBLIT
2307 select FB_DEFERRED_IO
2309 This driver implements support for the E-Ink Metronome
2310 controller. The pre-release name for this device was 8track
2311 and could also have been called by some vendors as PVI-nnnn.
2314 tristate "Fujitsu MB862xx GDC support"
2316 depends on PCI || (OF && PPC)
2317 select FB_CFB_FILLRECT
2318 select FB_CFB_COPYAREA
2319 select FB_CFB_IMAGEBLIT
2321 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2324 prompt "GDC variant"
2325 depends on FB_MB862XX
2327 config FB_MB862XX_PCI_GDC
2328 bool "Carmine/Coral-P(A) GDC"
2331 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2332 PCI graphics controller devices.
2334 config FB_MB862XX_LIME
2336 depends on OF && PPC
2337 select FB_FOREIGN_ENDIAN
2338 select FB_LITTLE_ENDIAN
2340 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2344 config FB_MB862XX_I2C
2345 bool "Support I2C bus on MB862XX GDC"
2346 depends on FB_MB862XX && I2C
2349 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2350 driver to support accessing I2C devices on controller's I2C bus.
2351 These are usually some video decoder chips.
2354 tristate "EP93XX frame buffer support"
2355 depends on FB && ARCH_EP93XX
2356 select FB_CFB_FILLRECT
2357 select FB_CFB_COPYAREA
2358 select FB_CFB_IMAGEBLIT
2360 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2361 This driver is also available as a module. The module will be called
2364 config FB_PRE_INIT_FB
2365 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2366 depends on FB && FB_MB862XX_LIME
2368 Select this option if display contents should be inherited as set by
2372 tristate "MSM Framebuffer support"
2373 depends on FB && ARCH_MSM
2374 select FB_CFB_FILLRECT
2375 select FB_CFB_COPYAREA
2376 select FB_CFB_IMAGEBLIT
2379 tristate "MX3 Framebuffer support"
2380 depends on FB && MX3_IPU
2381 select FB_CFB_FILLRECT
2382 select FB_CFB_COPYAREA
2383 select FB_CFB_IMAGEBLIT
2386 This is a framebuffer device for the i.MX31 LCD Controller. So
2387 far only synchronous displays are supported. If you plan to use
2388 an LCD display with your i.MX31 system, say Y here.
2390 config FB_BROADSHEET
2391 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2393 select FB_SYS_FILLRECT
2394 select FB_SYS_COPYAREA
2395 select FB_SYS_IMAGEBLIT
2397 select FB_DEFERRED_IO
2399 This driver implements support for the E-Ink Broadsheet
2400 controller. The release name for this device was Epson S1D13521
2401 and could also have been called by other names when coupled with
2405 tristate "AUO-K190X EPD controller support"
2407 select FB_SYS_FILLRECT
2408 select FB_SYS_COPYAREA
2409 select FB_SYS_IMAGEBLIT
2411 select FB_DEFERRED_IO
2413 Provides support for epaper controllers from the K190X series
2414 of AUO. These controllers can be used to drive epaper displays
2417 This option enables the common support, shared by the individual
2418 controller drivers. You will also have to enable the driver
2419 for the controller type used in your device.
2422 tristate "AUO-K1900 EPD controller support"
2423 depends on FB && FB_AUO_K190X
2425 This driver implements support for the AUO K1900 epd-controller.
2426 This controller can drive Sipix epaper displays but can only do
2427 serial updates, reducing the number of possible frames per second.
2430 tristate "AUO-K1901 EPD controller support"
2431 depends on FB && FB_AUO_K190X
2433 This driver implements support for the AUO K1901 epd-controller.
2434 This controller can drive Sipix epaper displays and supports
2435 concurrent updates, making higher frames per second possible.
2438 tristate "JZ4740 LCD framebuffer support"
2439 depends on FB && MACH_JZ4740
2440 select FB_SYS_FILLRECT
2441 select FB_SYS_COPYAREA
2442 select FB_SYS_IMAGEBLIT
2444 Framebuffer support for the JZ4740 SoC.
2447 tristate "MXS LCD framebuffer support"
2448 depends on FB && ARCH_MXS
2449 select FB_CFB_FILLRECT
2450 select FB_CFB_COPYAREA
2451 select FB_CFB_IMAGEBLIT
2452 select FB_MODE_HELPERS
2453 select VIDEOMODE_HELPERS
2455 Framebuffer support for the MXS SoC.
2457 config FB_PUV3_UNIGFX
2458 tristate "PKUnity v3 Unigfx framebuffer support"
2459 depends on FB && UNICORE32 && ARCH_PUV3
2460 select FB_SYS_FILLRECT
2461 select FB_SYS_COPYAREA
2462 select FB_SYS_IMAGEBLIT
2465 Choose this option if you want to use the Unigfx device as a
2466 framebuffer device. Without the support of PCI & AGP.
2469 tristate "Microsoft Hyper-V Synthetic Video support"
2470 depends on FB && HYPERV
2471 select FB_CFB_FILLRECT
2472 select FB_CFB_COPYAREA
2473 select FB_CFB_IMAGEBLIT
2475 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2478 bool "Simple framebuffer support"
2479 depends on (FB = y) && OF
2480 select FB_CFB_FILLRECT
2481 select FB_CFB_COPYAREA
2482 select FB_CFB_IMAGEBLIT
2484 Say Y if you want support for a simple frame-buffer.
2486 This driver assumes that the display hardware has been initialized
2487 before the kernel boots, and the kernel will simply render to the
2488 pre-allocated frame buffer surface.
2490 Configuration re: surface address, size, and format must be provided
2491 through device tree, or potentially plain old platform data in the
2494 source "drivers/video/omap/Kconfig"
2495 source "drivers/video/omap2/Kconfig"
2496 source "drivers/video/exynos/Kconfig"
2497 source "drivers/video/mmp/Kconfig"
2498 source "drivers/video/backlight/Kconfig"
2501 source "drivers/video/console/Kconfig"
2504 if FB || SGI_NEWPORT_CONSOLE
2505 source "drivers/video/logo/Kconfig"
2508 config FB_SH_MOBILE_MERAM
2509 tristate "SuperH Mobile MERAM read ahead support"
2510 depends on (SUPERH || ARCH_SHMOBILE)
2511 select GENERIC_ALLOCATOR
2513 Enable MERAM support for the SuperH controller.
2515 This will allow for caching of the framebuffer to provide more
2516 reliable access under heavy main memory bus traffic situations.
2517 Up to 4 memory channels can be configured, allowing 4 RGB or
2518 2 YCbCr framebuffers to be configured.
2521 tristate "Solomon SSD1307 framebuffer support"
2522 depends on FB && I2C
2526 select FB_SYS_FILLRECT
2527 select FB_SYS_COPYAREA
2528 select FB_SYS_IMAGEBLIT
2529 select FB_DEFERRED_IO
2532 This driver implements support for the Solomon SSD1307
2533 OLED controller over I2C.