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"
26 source "drivers/gpu/ion/Kconfig"
32 config VIDEO_OUTPUT_CONTROL
33 tristate "Lowlevel video output switch controls"
35 This framework adds support for low-level control of the video
38 config VIDEOMODE_HELPERS
44 config VEXPRESS_DVI_CONTROL
45 bool "Versatile Express DVI control"
46 depends on FB && VEXPRESS_CONFIG
50 tristate "Support for frame buffer devices"
52 The frame buffer device provides an abstraction for the graphics
53 hardware. It represents the frame buffer of some video hardware and
54 allows application software to access the graphics hardware through
55 a well-defined interface, so the software doesn't need to know
56 anything about the low-level (hardware register) stuff.
58 Frame buffer devices work identically across the different
59 architectures supported by Linux and make the implementation of
60 application programs easier and more portable; at this point, an X
61 server exists which uses the frame buffer device exclusively.
62 On several non-X86 architectures, the frame buffer device is the
63 only way to use the graphics hardware.
65 The device is accessed through special device nodes, usually located
66 in the /dev directory, i.e. /dev/fb*.
68 You need an utility program called fbset to make full use of frame
69 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
70 and the Framebuffer-HOWTO at
71 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
74 Say Y here and to the driver for your graphics board below if you
75 are compiling a kernel for a non-x86 architecture.
77 If you are compiling for the x86 architecture, you can say Y if you
78 want to play with it, but it is not essential. Please note that
79 running graphical applications that directly touch the hardware
80 (e.g. an accelerated X server) and that are not frame buffer
81 device-aware may cause unexpected results. If unsure, say N.
84 bool "Enable firmware EDID"
88 This enables access to the EDID transferred from the firmware.
89 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
90 transfers do not work for your driver and if you are using
91 nvidiafb, i810fb or savagefb.
93 In general, choosing Y for this option is safe. If you
94 experience extremely long delays while booting before you get
95 something on your display, try setting this to N. Matrox cards in
96 combination with certain motherboards and monitors are known to
97 suffer from this problem.
106 config FB_BOOT_VESA_SUPPORT
111 If true, at least one selected framebuffer driver can take advantage
112 of VESA video modes set at an early boot stage via the vga= parameter.
114 config FB_CFB_FILLRECT
119 Include the cfb_fillrect function for generic software rectangle
120 filling. This is used by drivers that don't provide their own
121 (accelerated) version.
123 config FB_CFB_COPYAREA
128 Include the cfb_copyarea function for generic software area copying.
129 This is used by drivers that don't provide their own (accelerated)
132 config FB_CFB_IMAGEBLIT
137 Include the cfb_imageblit function for generic software image
138 blitting. This is used by drivers that don't provide their own
139 (accelerated) version.
141 config FB_CFB_REV_PIXELS_IN_BYTE
146 Allow generic frame-buffer functions to work on displays with 1, 2
147 and 4 bits per pixel depths which has opposite order of pixels in
148 byte order to bytes in long order.
150 config FB_SYS_FILLRECT
155 Include the sys_fillrect function for generic software rectangle
156 filling. This is used by drivers that don't provide their own
157 (accelerated) version and the framebuffer is in system RAM.
159 config FB_SYS_COPYAREA
164 Include the sys_copyarea function for generic software area copying.
165 This is used by drivers that don't provide their own (accelerated)
166 version and the framebuffer is in system RAM.
168 config FB_SYS_IMAGEBLIT
173 Include the sys_imageblit function for generic software image
174 blitting. This is used by drivers that don't provide their own
175 (accelerated) version and the framebuffer is in system RAM.
177 menuconfig FB_FOREIGN_ENDIAN
178 bool "Framebuffer foreign endianness support"
181 This menu will let you enable support for the framebuffers with
182 non-native endianness (e.g. Little-Endian framebuffer on a
183 Big-Endian machine). Most probably you don't have such hardware,
184 so it's safe to say "n" here.
187 prompt "Choice endianness support"
188 depends on FB_FOREIGN_ENDIAN
190 config FB_BOTH_ENDIAN
191 bool "Support for Big- and Little-Endian framebuffers"
194 bool "Support for Big-Endian framebuffers only"
196 config FB_LITTLE_ENDIAN
197 bool "Support for Little-Endian framebuffers only"
206 config FB_DEFERRED_IO
213 depends on FB_DEFERRED_IO
220 Common utility functions useful to fbdev drivers of VGA-based
231 select BACKLIGHT_LCD_SUPPORT
232 select BACKLIGHT_CLASS_DEVICE
235 config FB_MODE_HELPERS
236 bool "Enable Video Mode Handling Helpers"
240 This enables functions for handling video modes using the
241 Generalized Timing Formula and the EDID parser. A few drivers rely
242 on this feature such as the radeonfb, rivafb, and the i810fb. If
243 your driver does not take advantage of this feature, choosing Y will
244 just increase the kernel size by about 5K.
246 config FB_TILEBLITTING
247 bool "Enable Tile Blitting Support"
251 This enables tile blitting. Tile blitting is a drawing technique
252 where the screen is divided into rectangular sections (tiles), whereas
253 the standard blitting divides the screen into pixels. Because the
254 default drawing element is a tile, drawing functions will be passed
255 parameters in terms of number of tiles instead of number of pixels.
256 For example, to draw a single character, instead of using bitmaps,
257 an index to an array of bitmaps will be used. To clear or move a
258 rectangular section of a screen, the rectangle will be described in
259 terms of number of tiles in the x- and y-axis.
261 This is particularly important to one driver, matroxfb. If
264 comment "Frame buffer hardware drivers"
268 tristate "Aeroflex Gaisler framebuffer support"
269 depends on FB && SPARC
270 select FB_CFB_FILLRECT
271 select FB_CFB_COPYAREA
272 select FB_CFB_IMAGEBLIT
274 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
277 tristate "Cirrus Logic support"
278 depends on FB && (ZORRO || PCI)
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
283 This enables support for Cirrus Logic GD542x/543x based boards on
284 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
286 If you have a PCI-based system, this enables support for these
287 chips: GD-543x, GD-544x, GD-5480.
289 Please read the file <file:Documentation/fb/cirrusfb.txt>.
291 Say N unless you have such a graphics board or plan to get one
292 before you next recompile the kernel.
295 tristate "Permedia2 support"
296 depends on FB && ((AMIGA && BROKEN) || PCI)
297 select FB_CFB_FILLRECT
298 select FB_CFB_COPYAREA
299 select FB_CFB_IMAGEBLIT
301 This is the frame buffer device driver for cards based on
302 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
303 The driver was tested on the following cards:
304 Diamond FireGL 1000 PRO AGP
305 ELSA Gloria Synergy PCI
306 Appian Jeronimo PRO (both heads) PCI
307 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
308 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
309 ASK Graphic Blaster Exxtreme AGP
311 To compile this driver as a module, choose M here: the
312 module will be called pm2fb.
314 config FB_PM2_FIFO_DISCONNECT
315 bool "enable FIFO disconnect feature"
316 depends on FB_PM2 && PCI
318 Support the Permedia2 FIFO disconnect feature.
321 tristate "ARM PrimeCell PL110 support"
322 depends on FB && ARM && ARM_AMBA
323 select FB_CFB_FILLRECT
324 select FB_CFB_COPYAREA
325 select FB_CFB_IMAGEBLIT
327 This framebuffer device driver is for the ARM PrimeCell PL110
328 Colour LCD controller. ARM PrimeCells provide the building
329 blocks for System on a Chip devices.
331 If you want to compile this as a module (=code which can be
332 inserted into and removed from the running kernel), say M
333 here and read <file:Documentation/kbuild/modules.txt>. The module
334 will be called amba-clcd.
337 tristate "ARM High Definition LCD support"
339 select FB_CFB_FILLRECT
340 select FB_CFB_COPYAREA
341 select FB_CFB_IMAGEBLIT
343 This framebuffer device driver is for the ARM High Definition
344 Colour LCD controller.
346 If you want to compile this as a module (=code which can be
347 inserted into and removed from the running kernel), say M
348 here and read <file:Documentation/kbuild/modules.txt>. The module
349 will be called arm-hdlcd.
352 bool "Acorn VIDC support"
353 depends on (FB = y) && ARM && ARCH_ACORN
354 select FB_CFB_FILLRECT
355 select FB_CFB_COPYAREA
356 select FB_CFB_IMAGEBLIT
358 This is the frame buffer device driver for the Acorn VIDC graphics
359 hardware found in Acorn RISC PCs and other ARM-based machines. If
363 bool "CLPS711X LCD support"
364 depends on (FB = y) && ARM && ARCH_CLPS711X
365 select FB_CFB_FILLRECT
366 select FB_CFB_COPYAREA
367 select FB_CFB_IMAGEBLIT
369 Say Y to enable the Framebuffer driver for the CLPS7111 and
373 bool "SA-1100 LCD support"
374 depends on (FB = y) && ARM && ARCH_SA1100
375 select FB_CFB_FILLRECT
376 select FB_CFB_COPYAREA
377 select FB_CFB_IMAGEBLIT
379 This is a framebuffer device for the SA-1100 LCD Controller.
380 See <http://www.linux-fbdev.org/> for information on framebuffer
383 If you plan to use the LCD display with your SA-1100 system, say
387 tristate "Freescale i.MX1/21/25/27 LCD support"
388 depends on FB && IMX_HAVE_PLATFORM_IMX_FB
389 select FB_CFB_FILLRECT
390 select FB_CFB_COPYAREA
391 select FB_CFB_IMAGEBLIT
394 tristate "CyberPro 2000/2010/5000 support"
395 depends on FB && PCI && (BROKEN || !SPARC64)
396 select FB_CFB_FILLRECT
397 select FB_CFB_COPYAREA
398 select FB_CFB_IMAGEBLIT
400 This enables support for the Integraphics CyberPro 20x0 and 5000
401 VGA chips used in the Rebel.com Netwinder and other machines.
402 Say Y if you have a NetWinder or a graphics card containing this
403 device, otherwise say N.
405 config FB_CYBER2000_DDC
406 bool "DDC for CyberPro support"
407 depends on FB_CYBER2000
411 Say Y here if you want DDC support for your CyberPro graphics
412 card. This is only I2C bus support, driver does not use EDID.
414 config FB_CYBER2000_I2C
415 bool "CyberPro 2000/2010/5000 I2C support"
416 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
419 Enable support for the I2C video decoder interface on the
420 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
421 on the Netwinder machines for the SAA7111 video capture.
425 depends on (FB = y) && APOLLO
427 select FB_CFB_FILLRECT
428 select FB_CFB_IMAGEBLIT
432 depends on (FB = y) && Q40
434 select FB_CFB_FILLRECT
435 select FB_CFB_COPYAREA
436 select FB_CFB_IMAGEBLIT
439 tristate "Amiga native chipset support"
440 depends on FB && AMIGA
442 This is the frame buffer device driver for the builtin graphics
443 chipset found in Amigas.
445 To compile this driver as a module, choose M here: the
446 module will be called amifb.
449 bool "Amiga OCS chipset support"
452 This enables support for the original Agnus and Denise video chips,
453 found in the Amiga 1000 and most A500's and A2000's. If you intend
454 to run Linux on any of these systems, say Y; otherwise say N.
457 bool "Amiga ECS chipset support"
460 This enables support for the Enhanced Chip Set, found in later
461 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
462 you intend to run Linux on any of these systems, say Y; otherwise
466 bool "Amiga AGA chipset support"
469 This enables support for the Advanced Graphics Architecture (also
470 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
471 and CD32. If you intend to run Linux on any of these systems, say Y;
475 bool "Amiga FrameMaster II/Rainbow II support"
476 depends on (FB = y) && ZORRO
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
481 This is the frame buffer device driver for the Amiga FrameMaster
482 card from BSC (exhibited 1992 but not shipped as a CBM product).
485 tristate "Arc Monochrome LCD board support"
487 select FB_SYS_FILLRECT
488 select FB_SYS_COPYAREA
489 select FB_SYS_IMAGEBLIT
492 This enables support for the Arc Monochrome LCD board. The board
493 is based on the KS-108 lcd controller and is typically a matrix
494 of 2*n chips. This driver was tested with a 128x64 panel. This
495 driver supports it for use with x86 SBCs through a 16 bit GPIO
496 interface (8 bit data, 8 bit control). If you anticipate using
497 this driver, say Y or M; otherwise say N. You must specify the
498 GPIO IO address to be used for setting control and data.
501 bool "Atari native chipset support"
502 depends on (FB = y) && ATARI
503 select FB_CFB_FILLRECT
504 select FB_CFB_COPYAREA
505 select FB_CFB_IMAGEBLIT
507 This is the frame buffer device driver for the builtin graphics
508 chipset found in Ataris.
511 bool "Open Firmware frame buffer device support"
512 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
518 Say Y if you want support with Open Firmware for your graphics
522 bool "Apple \"control\" display support"
523 depends on (FB = y) && PPC_PMAC && PPC32
524 select FB_CFB_FILLRECT
525 select FB_CFB_COPYAREA
526 select FB_CFB_IMAGEBLIT
529 This driver supports a frame buffer for the graphics adapter in the
530 Power Macintosh 7300 and others.
533 bool "Apple \"platinum\" display support"
534 depends on (FB = y) && PPC_PMAC && PPC32
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
540 This driver supports a frame buffer for the "platinum" graphics
541 adapter in some Power Macintoshes.
544 bool "Apple \"valkyrie\" display support"
545 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
546 select FB_CFB_FILLRECT
547 select FB_CFB_COPYAREA
548 select FB_CFB_IMAGEBLIT
551 This driver supports a frame buffer for the "valkyrie" graphics
552 adapter in some Power Macintoshes.
555 bool "Chips 65550 display support"
556 depends on (FB = y) && PPC32 && PCI
557 select FB_CFB_FILLRECT
558 select FB_CFB_COPYAREA
559 select FB_CFB_IMAGEBLIT
561 This is the frame buffer device driver for the Chips & Technologies
562 65550 graphics chip in PowerBooks.
565 bool "Asiliant (Chips) 69000 display support"
566 depends on (FB = y) && PCI
567 select FB_CFB_FILLRECT
568 select FB_CFB_COPYAREA
569 select FB_CFB_IMAGEBLIT
571 This is the frame buffer device driver for the Asiliant 69030 chipset
574 bool "IMS Twin Turbo display support"
575 depends on (FB = y) && PCI
576 select FB_CFB_IMAGEBLIT
577 select FB_MACMODES if PPC
579 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
580 many Macintosh and compatible computers.
583 tristate "VGA 16-color graphics support"
584 depends on FB && (X86 || PPC)
585 select FB_CFB_FILLRECT
586 select FB_CFB_COPYAREA
587 select FB_CFB_IMAGEBLIT
589 select FONT_8x16 if FRAMEBUFFER_CONSOLE
591 This is the frame buffer device driver for VGA 16 color graphic
592 cards. Say Y if you have such a card.
594 To compile this driver as a module, choose M here: the
595 module will be called vga16fb.
597 config FB_BF54X_LQ043
598 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
599 depends on FB && (BF54x) && !BF542
600 select FB_CFB_FILLRECT
601 select FB_CFB_COPYAREA
602 select FB_CFB_IMAGEBLIT
604 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
606 config FB_BFIN_T350MCQB
607 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
608 depends on FB && BLACKFIN
610 select FB_CFB_FILLRECT
611 select FB_CFB_COPYAREA
612 select FB_CFB_IMAGEBLIT
614 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
615 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
616 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
618 config FB_BFIN_LQ035Q1
619 tristate "SHARP LQ035Q1DH02 TFT LCD"
620 depends on FB && BLACKFIN && SPI
621 select FB_CFB_FILLRECT
622 select FB_CFB_COPYAREA
623 select FB_CFB_IMAGEBLIT
626 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
627 the Blackfin Landscape LCD EZ-Extender Card.
628 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
629 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
631 To compile this driver as a module, choose M here: the
632 module will be called bfin-lq035q1-fb.
634 config FB_BF537_LQ035
635 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
636 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
637 select FB_CFB_FILLRECT
638 select FB_CFB_COPYAREA
639 select FB_CFB_IMAGEBLIT
642 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
645 To compile this driver as a module, choose M here: the
646 module will be called bf537-lq035.
649 tristate "Blackfin ADV7393 Video encoder"
650 depends on FB && BLACKFIN
652 select FB_CFB_FILLRECT
653 select FB_CFB_COPYAREA
654 select FB_CFB_IMAGEBLIT
656 This is the framebuffer device for a ADV7393 video encoder
657 attached to a Blackfin on the PPI port.
658 If your Blackfin board has a ADV7393 select Y.
660 To compile this driver as a module, choose M here: the
661 module will be called bfin_adv7393fb.
664 prompt "Video mode support"
665 depends on FB_BFIN_7393
675 bool 'NTSC 640x480 (Experimental)'
678 bool 'PAL 640x480 (Experimental)'
681 bool 'NTSC 720x480 YCbCR input'
684 bool 'PAL 720x576 YCbCR input'
689 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
690 depends on (FB_BFIN_7393)
691 default ADV7393_1XMEM
701 tristate "HP STI frame buffer device support"
702 depends on FB && PARISC
703 select FB_CFB_FILLRECT
704 select FB_CFB_COPYAREA
705 select FB_CFB_IMAGEBLIT
710 STI refers to the HP "Standard Text Interface" which is a set of
711 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
712 Enabling this option will implement the linux framebuffer device
713 using calls to the STI BIOS routines for initialisation.
715 If you enable this option, you will get a planar framebuffer device
716 /dev/fb which will work on the most common HP graphic cards of the
717 NGLE family, including the artist chips (in the 7xx and Bxxx series),
718 HCRX, HCRX24, CRX, CRX24 and VisEG series.
720 It is safe to enable this option, so you should probably say "Y".
723 bool "Generic Macintosh display support"
724 depends on (FB = y) && MAC
725 select FB_CFB_FILLRECT
726 select FB_CFB_COPYAREA
727 select FB_CFB_IMAGEBLIT
732 depends on (FB = y) && DIO
733 select FB_CFB_IMAGEBLIT
737 tristate "TGA/SFB+ framebuffer support"
738 depends on FB && (ALPHA || TC)
739 select FB_CFB_FILLRECT
740 select FB_CFB_COPYAREA
741 select FB_CFB_IMAGEBLIT
744 This is the frame buffer device driver for generic TGA and SFB+
745 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
746 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
747 TURBOchannel cards, also known as PMAGD-A, -B and -C.
749 Due to hardware limitations ZLX-E2 and E3 cards are not supported
750 for DECstation 5000/200 systems. Additionally due to firmware
751 limitations these cards may cause troubles with booting DECstation
752 5000/240 and /260 systems, but are fully supported under Linux if
753 you manage to get it going. ;-)
755 Say Y if you have one of those.
758 tristate "Userspace VESA VGA graphics support"
759 depends on FB && CONNECTOR
760 select FB_CFB_FILLRECT
761 select FB_CFB_COPYAREA
762 select FB_CFB_IMAGEBLIT
763 select FB_MODE_HELPERS
765 This is the frame buffer driver for generic VBE 2.0 compliant
766 graphic cards. It can also take advantage of VBE 3.0 features,
767 such as refresh rate adjustment.
769 This driver generally provides more features than vesafb but
770 requires a userspace helper application called 'v86d'. See
771 <file:Documentation/fb/uvesafb.txt> for more information.
776 bool "VESA VGA graphics support"
777 depends on (FB = y) && X86
778 select FB_CFB_FILLRECT
779 select FB_CFB_COPYAREA
780 select FB_CFB_IMAGEBLIT
781 select FB_BOOT_VESA_SUPPORT
783 This is the frame buffer device driver for generic VESA 2.0
784 compliant graphic cards. The older VESA 1.2 cards are not supported.
785 You will get a boot time penguin logo at no additional cost. Please
786 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
789 bool "EFI-based Framebuffer Support"
790 depends on (FB = y) && X86 && EFI
791 select FB_CFB_FILLRECT
792 select FB_CFB_COPYAREA
793 select FB_CFB_IMAGEBLIT
795 This is the EFI frame buffer device driver. If the firmware on
796 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
797 using the EFI framebuffer as your console.
800 tristate "N411 Apollo/Hecuba devkit support"
801 depends on FB && X86 && MMU
802 select FB_SYS_FILLRECT
803 select FB_SYS_COPYAREA
804 select FB_SYS_IMAGEBLIT
806 select FB_DEFERRED_IO
809 This enables support for the Apollo display controller in its
810 Hecuba form using the n411 devkit.
813 tristate "Hercules mono graphics support"
816 Say Y here if you have a Hercules mono graphics card.
818 To compile this driver as a module, choose M here: the
819 module will be called hgafb.
821 As this card technology is at least 25 years old,
822 most people will answer N here.
825 tristate "SGI Visual Workstation framebuffer support"
826 depends on FB && X86_VISWS
827 select FB_CFB_FILLRECT
828 select FB_CFB_COPYAREA
829 select FB_CFB_IMAGEBLIT
831 SGI Visual Workstation support for framebuffer graphics.
834 bool "SGI Graphics Backend frame buffer support"
835 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
836 select FB_CFB_FILLRECT
837 select FB_CFB_COPYAREA
838 select FB_CFB_IMAGEBLIT
840 This is the frame buffer device driver for SGI Graphics Backend.
841 This chip is used in SGI O2 and Visual Workstation 320/540.
844 int "Video memory size in MB"
848 This is the amount of memory reserved for the framebuffer,
849 which can be any value between 1MB and 8MB.
852 bool "SBUS and UPA framebuffers"
853 depends on (FB = y) && SPARC
855 Say Y if you want support for SBUS or UPA based frame buffer device.
859 depends on (FB = y) && (SPARC && FB_SBUS)
860 select FB_CFB_FILLRECT
861 select FB_CFB_COPYAREA
862 select FB_CFB_IMAGEBLIT
864 This is the frame buffer device driver for the BWtwo frame buffer.
867 bool "CGthree support"
868 depends on (FB = y) && (SPARC && FB_SBUS)
869 select FB_CFB_FILLRECT
870 select FB_CFB_COPYAREA
871 select FB_CFB_IMAGEBLIT
873 This is the frame buffer device driver for the CGthree frame buffer.
876 bool "CGsix (GX,TurboGX) support"
877 depends on (FB = y) && (SPARC && FB_SBUS)
878 select FB_CFB_COPYAREA
879 select FB_CFB_IMAGEBLIT
881 This is the frame buffer device driver for the CGsix (GX, TurboGX)
885 bool "Creator/Creator3D/Elite3D support"
886 depends on FB_SBUS && SPARC64
887 select FB_CFB_COPYAREA
888 select FB_CFB_IMAGEBLIT
890 This is the frame buffer device driver for the Creator, Creator3D,
891 and Elite3D graphics boards.
894 bool "TCX (SS4/SS5 only) support"
896 select FB_CFB_FILLRECT
897 select FB_CFB_COPYAREA
898 select FB_CFB_IMAGEBLIT
900 This is the frame buffer device driver for the TCX 24/8bit frame
904 bool "CGfourteen (SX) support"
906 select FB_CFB_FILLRECT
907 select FB_CFB_COPYAREA
908 select FB_CFB_IMAGEBLIT
910 This is the frame buffer device driver for the CGfourteen frame
911 buffer on Desktop SPARCsystems with the SX graphics option.
914 bool "P9100 (Sparcbook 3 only) support"
916 select FB_CFB_FILLRECT
917 select FB_CFB_COPYAREA
918 select FB_CFB_IMAGEBLIT
920 This is the frame buffer device driver for the P9100 card
921 supported on Sparcbook 3 machines.
924 bool "Leo (ZX) support"
926 select FB_CFB_FILLRECT
927 select FB_CFB_COPYAREA
928 select FB_CFB_IMAGEBLIT
930 This is the frame buffer device driver for the SBUS-based Sun ZX
931 (leo) frame buffer cards.
934 bool "IGA 168x display support"
935 depends on (FB = y) && SPARC32
936 select FB_CFB_FILLRECT
937 select FB_CFB_COPYAREA
938 select FB_CFB_IMAGEBLIT
940 This is the framebuffer device for the INTERGRAPHICS 1680 and
941 successor frame buffer cards.
944 bool "Sun XVR-500 3DLABS Wildcat support"
945 depends on (FB = y) && PCI && SPARC64
946 select FB_CFB_FILLRECT
947 select FB_CFB_COPYAREA
948 select FB_CFB_IMAGEBLIT
950 This is the framebuffer device for the Sun XVR-500 and similar
951 graphics cards based upon the 3DLABS Wildcat chipset. The driver
952 only works on sparc64 systems where the system firmware has
953 mostly initialized the card already. It is treated as a
954 completely dumb framebuffer device.
957 bool "Sun XVR-2500 3DLABS Wildcat support"
958 depends on (FB = y) && PCI && SPARC64
959 select FB_CFB_FILLRECT
960 select FB_CFB_COPYAREA
961 select FB_CFB_IMAGEBLIT
963 This is the framebuffer device for the Sun XVR-2500 and similar
964 graphics cards based upon the 3DLABS Wildcat chipset. The driver
965 only works on sparc64 systems where the system firmware has
966 mostly initialized the card already. It is treated as a
967 completely dumb framebuffer device.
970 bool "Sun XVR-1000 support"
971 depends on (FB = y) && SPARC64
972 select FB_CFB_FILLRECT
973 select FB_CFB_COPYAREA
974 select FB_CFB_IMAGEBLIT
976 This is the framebuffer device for the Sun XVR-1000 and similar
977 graphics cards. The driver only works on sparc64 systems where
978 the system firmware has mostly initialized the card already. It
979 is treated as a completely dumb framebuffer device.
982 tristate "NEC PowerVR 2 display support"
983 depends on FB && SH_DREAMCAST
984 select FB_CFB_FILLRECT
985 select FB_CFB_COPYAREA
986 select FB_CFB_IMAGEBLIT
988 Say Y here if you have a PowerVR 2 card in your box. If you plan to
989 run linux on your Dreamcast, you will have to say Y here.
990 This driver may or may not work on other PowerVR 2 cards, but is
991 totally untested. Use at your own risk. If unsure, say N.
993 To compile this driver as a module, choose M here: the
994 module will be called pvr2fb.
996 You can pass several parameters to the driver at boot time or at
997 module load time. The parameters look like "video=pvr2:XXX", where
998 the meaning of XXX can be found at the end of the main source file
999 (<file:drivers/video/pvr2fb.c>). Please see the file
1000 <file:Documentation/fb/pvr2fb.txt>.
1003 tristate "Epson S1D13XXX framebuffer support"
1005 select FB_CFB_FILLRECT
1006 select FB_CFB_COPYAREA
1007 select FB_CFB_IMAGEBLIT
1009 Support for S1D13XXX framebuffer device family (currently only
1010 working with S1D13806). Product specs at
1011 <http://vdc.epson.com/>
1014 tristate "AT91/AT32 LCD Controller support"
1015 depends on FB && HAVE_FB_ATMEL
1016 select FB_CFB_FILLRECT
1017 select FB_CFB_COPYAREA
1018 select FB_CFB_IMAGEBLIT
1020 This enables support for the AT91/AT32 LCD Controller.
1023 bool "Frame Buffer in internal SRAM"
1024 depends on FB_ATMEL && ARCH_AT91SAM9261
1026 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1027 to let frame buffer in external SDRAM.
1030 bool "Use a STN display with AT91/AT32 LCD Controller"
1031 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1034 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1035 Controller. Say N if you want to connect a TFT.
1040 tristate "nVidia Framebuffer Support"
1041 depends on FB && PCI
1042 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1043 select FB_MODE_HELPERS
1044 select FB_CFB_FILLRECT
1045 select FB_CFB_COPYAREA
1046 select FB_CFB_IMAGEBLIT
1050 This driver supports graphics boards with the nVidia chips, TNT
1051 and newer. For very old chipsets, such as the RIVA128, then use
1053 Say Y if you have such a graphics board.
1055 To compile this driver as a module, choose M here: the
1056 module will be called nvidiafb.
1058 config FB_NVIDIA_I2C
1059 bool "Enable DDC Support"
1060 depends on FB_NVIDIA
1063 This enables I2C support for nVidia Chipsets. This is used
1064 only for getting EDID information from the attached display
1065 allowing for robust video mode handling and switching.
1067 Because fbdev-2.6 requires that drivers must be able to
1068 independently validate video mode parameters, you should say Y
1071 config FB_NVIDIA_DEBUG
1072 bool "Lots of debug output"
1073 depends on FB_NVIDIA
1076 Say Y here if you want the nVidia driver to output all sorts
1077 of debugging information to provide to the maintainer when
1078 something goes wrong.
1080 config FB_NVIDIA_BACKLIGHT
1081 bool "Support for backlight control"
1082 depends on FB_NVIDIA
1085 Say Y here if you want to control the backlight of your display.
1088 tristate "nVidia Riva support"
1089 depends on FB && PCI
1090 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1091 select FB_MODE_HELPERS
1092 select FB_CFB_FILLRECT
1093 select FB_CFB_COPYAREA
1094 select FB_CFB_IMAGEBLIT
1098 This driver supports graphics boards with the nVidia Riva/Geforce
1100 Say Y if you have such a graphics board.
1102 To compile this driver as a module, choose M here: the
1103 module will be called rivafb.
1106 bool "Enable DDC Support"
1110 This enables I2C support for nVidia Chipsets. This is used
1111 only for getting EDID information from the attached display
1112 allowing for robust video mode handling and switching.
1114 Because fbdev-2.6 requires that drivers must be able to
1115 independently validate video mode parameters, you should say Y
1118 config FB_RIVA_DEBUG
1119 bool "Lots of debug output"
1123 Say Y here if you want the Riva driver to output all sorts
1124 of debugging information to provide to the maintainer when
1125 something goes wrong.
1127 config FB_RIVA_BACKLIGHT
1128 bool "Support for backlight control"
1132 Say Y here if you want to control the backlight of your display.
1135 tristate "Intel740 support"
1136 depends on FB && PCI
1137 select FB_MODE_HELPERS
1138 select FB_CFB_FILLRECT
1139 select FB_CFB_COPYAREA
1140 select FB_CFB_IMAGEBLIT
1144 This driver supports graphics cards based on Intel740 chip.
1147 tristate "Intel 810/815 support"
1148 depends on FB && PCI && X86_32 && AGP_INTEL
1149 select FB_MODE_HELPERS
1150 select FB_CFB_FILLRECT
1151 select FB_CFB_COPYAREA
1152 select FB_CFB_IMAGEBLIT
1155 This driver supports the on-board graphics built in to the Intel 810
1156 and 815 chipsets. Say Y if you have and plan to use such a board.
1158 To compile this driver as a module, choose M here: the
1159 module will be called i810fb.
1161 For more information, please read
1162 <file:Documentation/fb/intel810.txt>
1165 bool "use VESA Generalized Timing Formula"
1168 If you say Y, then the VESA standard, Generalized Timing Formula
1169 or GTF, will be used to calculate the required video timing values
1170 per video mode. Since the GTF allows nondiscrete timings
1171 (nondiscrete being a range of values as opposed to discrete being a
1172 set of values), you'll be able to use any combination of horizontal
1173 and vertical resolutions, and vertical refresh rates without having
1174 to specify your own timing parameters. This is especially useful
1175 to maximize the performance of an aging display, or if you just
1176 have a display with nonstandard dimensions. A VESA compliant
1177 monitor is recommended, but can still work with non-compliant ones.
1178 If you need or want this, then select this option. The timings may
1179 not be compliant with Intel's recommended values. Use at your own
1182 If you say N, the driver will revert to discrete video timings
1183 using a set recommended by Intel in their documentation.
1188 bool "Enable DDC Support"
1189 depends on FB_I810 && FB_I810_GTF
1194 tristate "Intel LE80578 (Vermilion) support"
1195 depends on FB && PCI && X86
1196 select FB_MODE_HELPERS
1197 select FB_CFB_FILLRECT
1198 select FB_CFB_COPYAREA
1199 select FB_CFB_IMAGEBLIT
1201 This driver supports the LE80578 (Vermilion Range) chipset
1203 config FB_CARILLO_RANCH
1204 tristate "Intel Carillo Ranch support"
1205 depends on FB_LE80578 && FB && PCI && X86
1207 This driver supports the LE80578 (Carillo Ranch) board
1210 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1211 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1212 select FB_MODE_HELPERS
1213 select FB_CFB_FILLRECT
1214 select FB_CFB_COPYAREA
1215 select FB_CFB_IMAGEBLIT
1216 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1217 depends on !DRM_I915
1219 This driver supports the on-board graphics built in to the Intel
1220 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1221 Say Y if you have and plan to use such a board.
1223 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1225 To compile this driver as a module, choose M here: the
1226 module will be called intelfb.
1228 For more information, please read <file:Documentation/fb/intelfb.txt>
1230 config FB_INTEL_DEBUG
1231 bool "Intel driver Debug Messages"
1234 Say Y here if you want the Intel driver to output all sorts
1235 of debugging information to provide to the maintainer when
1236 something goes wrong.
1239 bool "DDC/I2C for Intel framebuffer support"
1244 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1247 tristate "Matrox acceleration"
1248 depends on FB && PCI
1249 select FB_CFB_FILLRECT
1250 select FB_CFB_COPYAREA
1251 select FB_CFB_IMAGEBLIT
1252 select FB_TILEBLITTING
1253 select FB_MACMODES if PPC_PMAC
1255 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1256 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1257 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1258 Matrox G400, G450 or G550 card in your box.
1260 To compile this driver as a module, choose M here: the
1261 module will be called matroxfb.
1263 You can pass several parameters to the driver at boot time or at
1264 module load time. The parameters look like "video=matroxfb:XXX", and
1265 are described in <file:Documentation/fb/matroxfb.txt>.
1267 config FB_MATROX_MILLENIUM
1268 bool "Millennium I/II support"
1269 depends on FB_MATROX
1271 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1272 video card. If you select "Advanced lowlevel driver options" below,
1273 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1274 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1275 also use font widths different from 8.
1277 config FB_MATROX_MYSTIQUE
1278 bool "Mystique support"
1279 depends on FB_MATROX
1281 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1282 video card. If you select "Advanced lowlevel driver options" below,
1283 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1284 packed pixel and 32 bpp packed pixel. You can also use font widths
1288 bool "G100/G200/G400/G450/G550 support"
1289 depends on FB_MATROX
1291 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1292 video card. If you select "Advanced lowlevel driver options", you
1293 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1294 pixel and 32 bpp packed pixel. You can also use font widths
1297 If you need support for G400 secondary head, you must say Y to
1298 "Matrox I2C support" and "G400 second head support" right below.
1299 G450/G550 secondary head and digital output are supported without
1302 The driver starts in monitor mode. You must use the matroxset tool
1303 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1304 swap primary and secondary head outputs, or to change output mode.
1305 Secondary head driver always start in 640x480 resolution and you
1306 must use fbset to change it.
1308 Do not forget that second head supports only 16 and 32 bpp
1309 packed pixels, so it is a good idea to compile them into the kernel
1310 too. You can use only some font widths, as the driver uses generic
1311 painting procedures (the secondary head does not use acceleration
1314 G450/G550 hardware can display TV picture only from secondary CRTC,
1315 and it performs no scaling, so picture must have 525 or 625 lines.
1317 config FB_MATROX_I2C
1318 tristate "Matrox I2C support"
1319 depends on FB_MATROX
1322 This drivers creates I2C buses which are needed for accessing the
1323 DDC (I2C) bus present on all Matroxes, an I2C bus which
1324 interconnects Matrox optional devices, like MGA-TVO on G200 and
1325 G400, and the secondary head DDC bus, present on G400 only.
1327 You can say Y or M here if you want to experiment with monitor
1328 detection code. You must say Y or M here if you want to use either
1329 second head of G400 or MGA-TVO on G200 or G400.
1331 If you compile it as module, it will create a module named
1334 config FB_MATROX_MAVEN
1335 tristate "G400 second head support"
1336 depends on FB_MATROX_G && FB_MATROX_I2C
1338 WARNING !!! This support does not work with G450 !!!
1340 Say Y or M here if you want to use a secondary head (meaning two
1341 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1342 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1343 secondary head output is blanked while you are in X. With XFree
1344 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1345 the fbdev driver on first head and the fbdev driver on second head.
1347 If you compile it as module, two modules are created,
1348 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1349 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1350 also load i2c-matroxfb to get it to run.
1352 The driver starts in monitor mode and you must use the matroxset
1354 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1355 PAL or NTSC or to swap primary and secondary head outputs.
1356 Secondary head driver also always start in 640x480 resolution, you
1357 must use fbset to change it.
1359 Also do not forget that second head supports only 16 and 32 bpp
1360 packed pixels, so it is a good idea to compile them into the kernel
1361 too. You can use only some font widths, as the driver uses generic
1362 painting procedures (the secondary head does not use acceleration
1366 tristate "ATI Radeon display support"
1367 depends on FB && PCI
1368 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1369 select FB_MODE_HELPERS
1370 select FB_CFB_FILLRECT
1371 select FB_CFB_COPYAREA
1372 select FB_CFB_IMAGEBLIT
1373 select FB_MACMODES if PPC_OF
1375 Choose this option if you want to use an ATI Radeon graphics card as
1376 a framebuffer device. There are both PCI and AGP versions. You
1377 don't need to choose this to run the Radeon in plain VGA mode.
1379 There is a product page at
1380 http://products.amd.com/en-us/GraphicCardResult.aspx
1382 config FB_RADEON_I2C
1383 bool "DDC/I2C for ATI Radeon support"
1384 depends on FB_RADEON
1388 Say Y here if you want DDC/I2C support for your Radeon board.
1390 config FB_RADEON_BACKLIGHT
1391 bool "Support for backlight control"
1392 depends on FB_RADEON
1395 Say Y here if you want to control the backlight of your display.
1397 config FB_RADEON_DEBUG
1398 bool "Lots of debug output from Radeon driver"
1399 depends on FB_RADEON
1402 Say Y here if you want the Radeon driver to output all sorts
1403 of debugging information to provide to the maintainer when
1404 something goes wrong.
1407 tristate "ATI Rage128 display support"
1408 depends on FB && PCI
1409 select FB_CFB_FILLRECT
1410 select FB_CFB_COPYAREA
1411 select FB_CFB_IMAGEBLIT
1412 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1413 select FB_MACMODES if PPC_PMAC
1415 This driver supports graphics boards with the ATI Rage128 chips.
1416 Say Y if you have such a graphics board and read
1417 <file:Documentation/fb/aty128fb.txt>.
1419 To compile this driver as a module, choose M here: the
1420 module will be called aty128fb.
1422 config FB_ATY128_BACKLIGHT
1423 bool "Support for backlight control"
1424 depends on FB_ATY128
1427 Say Y here if you want to control the backlight of your display.
1430 tristate "ATI Mach64 display support" if PCI || ATARI
1431 depends on FB && !SPARC32
1432 select FB_CFB_FILLRECT
1433 select FB_CFB_COPYAREA
1434 select FB_CFB_IMAGEBLIT
1435 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1436 select FB_MACMODES if PPC
1438 This driver supports graphics boards with the ATI Mach64 chips.
1439 Say Y if you have such a graphics board.
1441 To compile this driver as a module, choose M here: the
1442 module will be called atyfb.
1445 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1446 depends on PCI && FB_ATY
1447 default y if SPARC64 && PCI
1449 Say Y here to support use of ATI's 64-bit Rage boards (or other
1450 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1451 framebuffer device. The ATI product support page for these boards
1452 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1454 config FB_ATY_GENERIC_LCD
1455 bool "Mach64 generic LCD support"
1456 depends on FB_ATY_CT
1458 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1459 Rage XC, or Rage XL chipset.
1462 bool "Mach64 GX support" if PCI
1466 Say Y here to support use of the ATI Mach64 Graphics Expression
1467 board (or other boards based on the Mach64 GX chipset) as a
1468 framebuffer device. The ATI product support page for these boards
1470 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1472 config FB_ATY_BACKLIGHT
1473 bool "Support for backlight control"
1477 Say Y here if you want to control the backlight of your display.
1480 tristate "S3 Trio/Virge support"
1481 depends on FB && PCI
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1485 select FB_TILEBLITTING
1488 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1490 Driver for graphics boards with S3 Trio / S3 Virge chip.
1493 bool "DDC for S3 support"
1498 Say Y here if you want DDC support for your S3 graphics card.
1501 tristate "S3 Savage support"
1502 depends on FB && PCI
1503 select FB_MODE_HELPERS
1504 select FB_CFB_FILLRECT
1505 select FB_CFB_COPYAREA
1506 select FB_CFB_IMAGEBLIT
1509 This driver supports notebooks and computers with S3 Savage PCI/AGP
1512 Say Y if you have such a graphics card.
1514 To compile this driver as a module, choose M here; the module
1515 will be called savagefb.
1517 config FB_SAVAGE_I2C
1518 bool "Enable DDC2 Support"
1519 depends on FB_SAVAGE
1522 This enables I2C support for S3 Savage Chipsets. This is used
1523 only for getting EDID information from the attached display
1524 allowing for robust video mode handling and switching.
1526 Because fbdev-2.6 requires that drivers must be able to
1527 independently validate video mode parameters, you should say Y
1530 config FB_SAVAGE_ACCEL
1531 bool "Enable Console Acceleration"
1532 depends on FB_SAVAGE
1535 This option will compile in console acceleration support. If
1536 the resulting framebuffer console has bothersome glitches, then
1540 tristate "SiS/XGI display support"
1541 depends on FB && PCI
1542 select FB_CFB_FILLRECT
1543 select FB_CFB_COPYAREA
1544 select FB_CFB_IMAGEBLIT
1545 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1547 This is the frame buffer device driver for the SiS 300, 315, 330
1548 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1549 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1551 To compile this driver as a module, choose M here; the module
1552 will be called sisfb.
1555 bool "SiS 300 series support"
1558 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1561 bool "SiS 315/330/340 series and XGI support"
1564 Say Y here to support use of the SiS 315, 330 and 340 series
1565 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1566 as XGI V3XT, V5, V8 and Z7.
1569 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1570 depends on FB && PCI && X86
1571 select FB_CFB_FILLRECT
1572 select FB_CFB_COPYAREA
1573 select FB_CFB_IMAGEBLIT
1578 This is the frame buffer device driver for Graphics chips of VIA
1579 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1580 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1582 Say Y if you have a VIA UniChrome graphics board.
1584 To compile this driver as a module, choose M here: the
1585 module will be called viafb.
1589 config FB_VIA_DIRECT_PROCFS
1590 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1594 Allow direct hardware access to some output registers via procfs.
1595 This is dangerous but may provide the only chance to get the
1596 correct output device configuration.
1597 Its use is strongly discouraged.
1599 config FB_VIA_X_COMPATIBILITY
1600 bool "X server compatibility"
1604 This option reduces the functionality (power saving, ...) of the
1605 framebuffer to avoid negative impact on the OpenChrome X server.
1606 If you use any X server other than fbdev you should enable this
1607 otherwise it should be safe to disable it and allow using all
1613 tristate "NeoMagic display support"
1614 depends on FB && PCI
1615 select FB_MODE_HELPERS
1616 select FB_CFB_FILLRECT
1617 select FB_CFB_COPYAREA
1618 select FB_CFB_IMAGEBLIT
1621 This driver supports notebooks with NeoMagic PCI chips.
1622 Say Y if you have such a graphics card.
1624 To compile this driver as a module, choose M here: the
1625 module will be called neofb.
1628 tristate "IMG Kyro support"
1629 depends on FB && PCI
1630 select FB_CFB_FILLRECT
1631 select FB_CFB_COPYAREA
1632 select FB_CFB_IMAGEBLIT
1634 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1637 To compile this driver as a module, choose M here: the
1638 module will be called kyrofb.
1641 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1642 depends on FB && PCI
1643 select FB_CFB_IMAGEBLIT
1644 select FB_CFB_FILLRECT
1645 select FB_CFB_COPYAREA
1646 select FB_MODE_HELPERS
1648 This driver supports graphics boards with the 3Dfx Banshee,
1649 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1650 such a graphics board.
1652 To compile this driver as a module, choose M here: the
1653 module will be called tdfxfb.
1655 config FB_3DFX_ACCEL
1656 bool "3Dfx Acceleration functions"
1659 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1660 device driver with acceleration functions.
1663 bool "Enable DDC/I2C support"
1668 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1671 tristate "3Dfx Voodoo Graphics (sst1) support"
1672 depends on FB && PCI
1673 select FB_CFB_FILLRECT
1674 select FB_CFB_COPYAREA
1675 select FB_CFB_IMAGEBLIT
1677 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1678 Voodoo2 (cvg) based graphics card.
1680 To compile this driver as a module, choose M here: the
1681 module will be called sstfb.
1683 WARNING: Do not use any application that uses the 3D engine
1684 (namely glide) while using this driver.
1685 Please read the <file:Documentation/fb/sstfb.txt> for supported
1686 options and other important info support.
1689 tristate "VIA VT8623 support"
1690 depends on FB && PCI
1691 select FB_CFB_FILLRECT
1692 select FB_CFB_COPYAREA
1693 select FB_CFB_IMAGEBLIT
1694 select FB_TILEBLITTING
1697 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1699 Driver for CastleRock integrated graphics core in the
1700 VIA VT8623 [Apollo CLE266] chipset.
1703 tristate "Trident/CyberXXX/CyberBlade support"
1704 depends on FB && PCI
1705 select FB_CFB_FILLRECT
1706 select FB_CFB_COPYAREA
1707 select FB_CFB_IMAGEBLIT
1709 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1710 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1712 There are also integrated versions of these chips called CyberXXXX,
1713 CyberImage or CyberBlade. These chips are mostly found in laptops
1714 but also on some motherboards including early VIA EPIA motherboards.
1715 For more information, read <file:Documentation/fb/tridentfb.txt>
1717 Say Y if you have such a graphics board.
1719 To compile this driver as a module, choose M here: the
1720 module will be called tridentfb.
1723 tristate "ARK 2000PV support"
1724 depends on FB && PCI
1725 select FB_CFB_FILLRECT
1726 select FB_CFB_COPYAREA
1727 select FB_CFB_IMAGEBLIT
1728 select FB_TILEBLITTING
1731 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1733 Driver for PCI graphics boards with ARK 2000PV chip
1734 and ICS 5342 RAMDAC.
1737 tristate "Permedia3 support"
1738 depends on FB && PCI
1739 select FB_CFB_FILLRECT
1740 select FB_CFB_COPYAREA
1741 select FB_CFB_IMAGEBLIT
1743 This is the frame buffer device driver for the 3DLabs Permedia3
1744 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1745 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1746 and maybe other boards.
1749 tristate "Fujitsu carmine frame buffer support"
1750 depends on FB && PCI
1751 select FB_CFB_FILLRECT
1752 select FB_CFB_COPYAREA
1753 select FB_CFB_IMAGEBLIT
1755 This is the frame buffer device driver for the Fujitsu Carmine chip.
1756 The driver provides two independent frame buffer devices.
1759 depends on FB_CARMINE
1760 prompt "DRAM timing"
1761 default FB_CARMINE_DRAM_EVAL
1763 config FB_CARMINE_DRAM_EVAL
1764 bool "Eval board timings"
1766 Use timings which work on the eval card.
1768 config CARMINE_DRAM_CUSTOM
1769 bool "Custom board timings"
1771 Use custom board timings.
1775 bool "Au1100 LCD Driver"
1776 depends on (FB = y) && MIPS_ALCHEMY
1777 select FB_CFB_FILLRECT
1778 select FB_CFB_COPYAREA
1779 select FB_CFB_IMAGEBLIT
1781 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1782 various panels and CRTs by passing in kernel cmd line option
1783 au1100fb:panel=<name>.
1786 bool "Au1200/Au1300 LCD Driver"
1787 depends on (FB = y) && MIPS_ALCHEMY
1788 select FB_SYS_FILLRECT
1789 select FB_SYS_COPYAREA
1790 select FB_SYS_IMAGEBLIT
1793 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1794 It can drive various panels and CRTs by passing in kernel cmd line
1795 option au1200fb:panel=<name>.
1798 bool "VIA VT8500 framebuffer support"
1799 depends on (FB = y) && ARM && ARCH_VT8500
1800 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1801 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1802 select FB_SYS_IMAGEBLIT
1803 select FB_MODE_HELPERS
1804 select VIDEOMODE_HELPERS
1806 This is the framebuffer driver for VIA VT8500 integrated LCD
1810 bool "Wondermedia WM8xxx-series frame buffer support"
1811 depends on (FB = y) && ARM && ARCH_VT8500
1812 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1813 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1814 select FB_SYS_IMAGEBLIT
1815 select FB_MODE_HELPERS
1816 select VIDEOMODE_HELPERS
1818 This is the framebuffer driver for WonderMedia WM8xxx-series
1819 integrated LCD controller. This driver covers the WM8505, WM8650
1822 config FB_WMT_GE_ROPS
1823 bool "VT8500/WM8xxx accelerated raster ops support"
1824 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1827 This adds support for accelerated raster operations on the
1828 VIA VT8500 and Wondermedia 85xx series SoCs.
1830 source "drivers/video/geode/Kconfig"
1833 tristate "HD64461 Frame Buffer support"
1834 depends on FB && HD64461
1835 select FB_CFB_FILLRECT
1836 select FB_CFB_COPYAREA
1837 select FB_CFB_IMAGEBLIT
1839 This is the frame buffer device driver for the Hitachi HD64461 LCD
1843 bool "PMAG-AA TURBOchannel framebuffer support"
1844 depends on (FB = y) && TC
1845 select FB_CFB_FILLRECT
1846 select FB_CFB_COPYAREA
1847 select FB_CFB_IMAGEBLIT
1849 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1850 used mainly in the MIPS-based DECstation series.
1853 tristate "PMAG-BA TURBOchannel framebuffer support"
1855 select FB_CFB_FILLRECT
1856 select FB_CFB_COPYAREA
1857 select FB_CFB_IMAGEBLIT
1859 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1860 used mainly in the MIPS-based DECstation series.
1863 tristate "PMAGB-B TURBOchannel framebuffer support"
1865 select FB_CFB_FILLRECT
1866 select FB_CFB_COPYAREA
1867 select FB_CFB_IMAGEBLIT
1869 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1870 in the MIPS-based DECstation series. The card is currently only
1871 supported in 1280x1024x8 mode.
1874 bool "Maxine (Personal DECstation) onboard framebuffer support"
1875 depends on (FB = y) && MACH_DECSTATION
1876 select FB_CFB_FILLRECT
1877 select FB_CFB_COPYAREA
1878 select FB_CFB_IMAGEBLIT
1880 Support for the onboard framebuffer (1024x768x8) in the Personal
1881 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1885 bool "G364 frame buffer support"
1886 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1887 select FB_CFB_FILLRECT
1888 select FB_CFB_COPYAREA
1889 select FB_CFB_IMAGEBLIT
1891 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1892 Olivetti M700-10 systems.
1895 bool "Motorola 68328 native frame buffer support"
1896 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1897 select FB_CFB_FILLRECT
1898 select FB_CFB_COPYAREA
1899 select FB_CFB_IMAGEBLIT
1901 Say Y here if you want to support the built-in frame buffer of
1902 the Motorola 68328 CPU family.
1905 tristate "PXA168/910 LCD framebuffer support"
1906 depends on FB && (CPU_PXA168 || CPU_PXA910)
1907 select FB_CFB_FILLRECT
1908 select FB_CFB_COPYAREA
1909 select FB_CFB_IMAGEBLIT
1911 Frame buffer driver for the built-in LCD controller in the Marvell
1915 tristate "PXA LCD framebuffer support"
1916 depends on FB && ARCH_PXA
1917 select FB_CFB_FILLRECT
1918 select FB_CFB_COPYAREA
1919 select FB_CFB_IMAGEBLIT
1921 Frame buffer driver for the built-in LCD controller in the Intel
1924 This driver is also available as a module ( = code which can be
1925 inserted and removed from the running kernel whenever you want). The
1926 module will be called pxafb. If you want to compile it as a module,
1927 say M here and read <file:Documentation/kbuild/modules.txt>.
1931 config FB_PXA_OVERLAY
1932 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1934 depends on FB_PXA && (PXA27x || PXA3xx)
1936 config FB_PXA_SMARTPANEL
1937 bool "PXA Smartpanel LCD support"
1941 config FB_PXA_PARAMETERS
1942 bool "PXA LCD command line parameters"
1946 Enable the use of kernel command line or module parameters
1947 to configure the physical properties of the LCD panel when
1948 using the PXA LCD driver.
1950 This option allows you to override the panel parameters
1951 supplied by the platform in order to support multiple
1952 different models of flatpanel. If you will only be using a
1953 single model of flatpanel then you can safely leave this
1956 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1959 tristate "PXA3xx 2D graphics accelerator driver"
1962 Kernelspace driver for the 2D graphics controller unit (GCU)
1963 found on PXA3xx processors. There is a counterpart driver in the
1964 DirectFB suite, see http://www.directfb.org/
1966 If you compile this as a module, it will be called pxa3xx_gcu.
1969 tristate "2700G LCD framebuffer support"
1970 depends on FB && ARCH_PXA
1971 select FB_CFB_FILLRECT
1972 select FB_CFB_COPYAREA
1973 select FB_CFB_IMAGEBLIT
1975 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1979 bool "Enable debugging info via debugfs"
1980 depends on FB_MBX && DEBUG_FS
1983 Enable this if you want debugging information using the debug
1984 filesystem (debugfs)
1989 tristate "Freescale DIU framebuffer support"
1990 depends on FB && FSL_SOC
1991 select FB_MODE_HELPERS
1992 select FB_CFB_FILLRECT
1993 select FB_CFB_COPYAREA
1994 select FB_CFB_IMAGEBLIT
1995 select PPC_LIB_RHEAP
1997 Framebuffer driver for the Freescale SoC DIU
2000 tristate "W100 frame buffer support"
2001 depends on FB && ARCH_PXA
2002 select FB_CFB_FILLRECT
2003 select FB_CFB_COPYAREA
2004 select FB_CFB_IMAGEBLIT
2006 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
2007 It can also drive the w3220 chip found on iPAQ hx4700.
2009 This driver is also available as a module ( = code which can be
2010 inserted and removed from the running kernel whenever you want). The
2011 module will be called w100fb. If you want to compile it as a module,
2012 say M here and read <file:Documentation/kbuild/modules.txt>.
2016 config FB_SH_MOBILE_LCDC
2017 tristate "SuperH Mobile LCDC framebuffer support"
2018 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
2019 select FB_SYS_FILLRECT
2020 select FB_SYS_COPYAREA
2021 select FB_SYS_IMAGEBLIT
2023 select FB_DEFERRED_IO
2025 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
2027 Frame buffer driver for the on-chip SH-Mobile LCD controller.
2029 config FB_SH_MOBILE_HDMI
2030 tristate "SuperH Mobile HDMI controller support"
2031 depends on FB_SH_MOBILE_LCDC
2032 select FB_MODE_HELPERS
2037 Driver for the on-chip SH-Mobile HDMI controller.
2040 tristate "Toshiba Mobile IO FrameBuffer support"
2041 depends on FB && MFD_CORE
2042 select FB_CFB_FILLRECT
2043 select FB_CFB_COPYAREA
2044 select FB_CFB_IMAGEBLIT
2046 Frame buffer driver for the Toshiba Mobile IO integrated as found
2047 on the Sharp SL-6000 series
2049 This driver is also available as a module ( = code which can be
2050 inserted and removed from the running kernel whenever you want). The
2051 module will be called tmiofb. If you want to compile it as a module,
2052 say M here and read <file:Documentation/kbuild/modules.txt>.
2056 config FB_TMIO_ACCELL
2057 bool "tmiofb acceleration"
2062 tristate "Samsung S3C framebuffer support"
2063 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2064 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2065 select FB_CFB_FILLRECT
2066 select FB_CFB_COPYAREA
2067 select FB_CFB_IMAGEBLIT
2069 Frame buffer driver for the built-in FB controller in the Samsung
2070 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2071 and the S3C64XX series such as the S3C6400 and S3C6410.
2073 These chips all have the same basic framebuffer design with the
2074 actual capabilities depending on the chip. For instance the S3C6400
2075 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2076 currently only have two.
2078 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2080 config FB_S3C_DEBUG_REGWRITE
2081 bool "Debug register writes"
2084 Show all register writes via pr_debug()
2087 tristate "S3C2410 LCD framebuffer support"
2088 depends on FB && ARCH_S3C24XX
2089 select FB_CFB_FILLRECT
2090 select FB_CFB_COPYAREA
2091 select FB_CFB_IMAGEBLIT
2093 Frame buffer driver for the built-in LCD controller in the Samsung
2096 This driver is also available as a module ( = code which can be
2097 inserted and removed from the running kernel whenever you want). The
2098 module will be called s3c2410fb. If you want to compile it as a module,
2099 say M here and read <file:Documentation/kbuild/modules.txt>.
2102 config FB_S3C2410_DEBUG
2103 bool "S3C2410 lcd debug messages"
2104 depends on FB_S3C2410
2106 Turn on debugging messages. Note that you can set/unset at run time
2110 bool "NUC900 LCD framebuffer support"
2111 depends on FB && ARCH_W90X900
2112 select FB_CFB_FILLRECT
2113 select FB_CFB_COPYAREA
2114 select FB_CFB_IMAGEBLIT
2116 Frame buffer driver for the built-in LCD controller in the Nuvoton
2119 config GPM1040A0_320X240
2120 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2121 depends on FB_NUC900
2123 config FB_NUC900_DEBUG
2124 bool "NUC900 lcd debug messages"
2125 depends on FB_NUC900
2127 Turn on debugging messages. Note that you can set/unset at run time
2131 tristate "Silicon Motion SM501 framebuffer support"
2132 depends on FB && MFD_SM501
2133 select FB_CFB_FILLRECT
2134 select FB_CFB_COPYAREA
2135 select FB_CFB_IMAGEBLIT
2137 Frame buffer driver for the CRT and LCD controllers in the Silicon
2140 This driver is also available as a module ( = code which can be
2141 inserted and removed from the running kernel whenever you want). The
2142 module will be called sm501fb. If you want to compile it as a module,
2143 say M here and read <file:Documentation/kbuild/modules.txt>.
2148 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2149 depends on FB && USB
2150 select FB_MODE_HELPERS
2151 select FB_SYS_FILLRECT
2152 select FB_SYS_COPYAREA
2153 select FB_SYS_IMAGEBLIT
2155 select FB_DEFERRED_IO
2157 This is a kernel framebuffer driver for SMSC UFX USB devices.
2158 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2159 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2161 To compile as a module, choose M here: the module name is smscufx.
2164 tristate "Displaylink USB Framebuffer support"
2165 depends on FB && USB
2166 select FB_MODE_HELPERS
2167 select FB_SYS_FILLRECT
2168 select FB_SYS_COPYAREA
2169 select FB_SYS_IMAGEBLIT
2171 select FB_DEFERRED_IO
2173 This is a kernel framebuffer driver for DisplayLink USB devices.
2174 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2175 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2176 To compile as a module, choose M here: the module name is udlfb.
2178 config FB_IBM_GXT4500
2179 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2180 depends on FB && PPC
2181 select FB_CFB_FILLRECT
2182 select FB_CFB_COPYAREA
2183 select FB_CFB_IMAGEBLIT
2185 Say Y here to enable support for the IBM GXT4000P/6000P and
2186 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2187 found on some IBM System P (pSeries) machines. This driver
2188 doesn't use Geometry Engine GT1000.
2191 tristate "PS3 GPU framebuffer driver"
2192 depends on FB && PS3_PS3AV
2193 select FB_SYS_FILLRECT
2194 select FB_SYS_COPYAREA
2195 select FB_SYS_IMAGEBLIT
2197 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2199 Include support for the virtual frame buffer in the PS3 platform.
2201 config FB_PS3_DEFAULT_SIZE_M
2202 int "PS3 default frame buffer size (in MiB)"
2206 This is the default size (in MiB) of the virtual frame buffer in
2208 The default value can be overridden on the kernel command line
2209 using the "ps3fb" option (e.g. "ps3fb=9M");
2212 tristate "Xilinx frame buffer support"
2213 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2214 select FB_CFB_FILLRECT
2215 select FB_CFB_COPYAREA
2216 select FB_CFB_IMAGEBLIT
2218 Include support for the Xilinx ML300/ML403 reference design
2219 framebuffer. ML300 carries a 640*480 LCD display on the board,
2220 ML403 uses a standard DB15 VGA connector.
2223 tristate "Goldfish Framebuffer"
2224 depends on FB && HAS_DMA
2225 select FB_CFB_FILLRECT
2226 select FB_CFB_COPYAREA
2227 select FB_CFB_IMAGEBLIT
2229 Framebuffer driver for Goldfish Virtual Platform
2232 tristate "Cobalt server LCD frame buffer support"
2233 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2236 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2237 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2238 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2239 select FB_CFB_FILLRECT
2240 select FB_CFB_COPYAREA
2241 select FB_CFB_IMAGEBLIT
2243 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2244 (D)STN/TFT LCD Controller.
2245 Supports display resolutions up to 1024x1024 pixel, grayscale and
2246 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2247 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2248 panels <= 320 pixel horizontal resolution.
2251 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2252 depends on FB && ARCH_DAVINCI_DA8XX
2253 select FB_CFB_FILLRECT
2254 select FB_CFB_COPYAREA
2255 select FB_CFB_IMAGEBLIT
2256 select FB_CFB_REV_PIXELS_IN_BYTE
2258 This is the frame buffer device driver for the TI LCD controller
2259 found on DA8xx/OMAP-L1xx SoCs.
2263 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2265 select FB_SYS_FILLRECT
2266 select FB_SYS_COPYAREA
2267 select FB_SYS_IMAGEBLIT
2270 This is a `virtual' frame buffer device. It operates on a chunk of
2271 unswappable kernel memory instead of on the memory of a graphics
2272 board. This means you cannot see any output sent to this frame
2273 buffer device, while it does consume precious memory. The main use
2274 of this frame buffer device is testing and debugging the frame
2275 buffer subsystem. Do NOT enable it for normal systems! To protect
2276 the innocent, it has to be enabled explicitly at boot time using the
2277 kernel option `video=vfb:'.
2279 To compile this driver as a module, choose M here: the
2280 module will be called vfb. In order to load it, you must use
2281 the vfb_enable=1 option.
2285 config XEN_FBDEV_FRONTEND
2286 tristate "Xen virtual frame buffer support"
2287 depends on FB && XEN
2288 select FB_SYS_FILLRECT
2289 select FB_SYS_COPYAREA
2290 select FB_SYS_IMAGEBLIT
2292 select FB_DEFERRED_IO
2293 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2294 select XEN_XENBUS_FRONTEND
2297 This driver implements the front-end of the Xen virtual
2298 frame buffer driver. It communicates with a back-end
2302 tristate "E-Ink Metronome/8track controller support"
2304 select FB_SYS_FILLRECT
2305 select FB_SYS_COPYAREA
2306 select FB_SYS_IMAGEBLIT
2308 select FB_DEFERRED_IO
2310 This driver implements support for the E-Ink Metronome
2311 controller. The pre-release name for this device was 8track
2312 and could also have been called by some vendors as PVI-nnnn.
2315 tristate "Fujitsu MB862xx GDC support"
2317 depends on PCI || (OF && PPC)
2318 select FB_CFB_FILLRECT
2319 select FB_CFB_COPYAREA
2320 select FB_CFB_IMAGEBLIT
2322 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2325 prompt "GDC variant"
2326 depends on FB_MB862XX
2328 config FB_MB862XX_PCI_GDC
2329 bool "Carmine/Coral-P(A) GDC"
2332 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2333 PCI graphics controller devices.
2335 config FB_MB862XX_LIME
2337 depends on OF && PPC
2338 select FB_FOREIGN_ENDIAN
2339 select FB_LITTLE_ENDIAN
2341 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2345 config FB_MB862XX_I2C
2346 bool "Support I2C bus on MB862XX GDC"
2347 depends on FB_MB862XX && I2C
2350 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2351 driver to support accessing I2C devices on controller's I2C bus.
2352 These are usually some video decoder chips.
2355 tristate "EP93XX frame buffer support"
2356 depends on FB && ARCH_EP93XX
2357 select FB_CFB_FILLRECT
2358 select FB_CFB_COPYAREA
2359 select FB_CFB_IMAGEBLIT
2361 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2362 This driver is also available as a module. The module will be called
2365 config FB_PRE_INIT_FB
2366 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2367 depends on FB && FB_MB862XX_LIME
2369 Select this option if display contents should be inherited as set by
2373 tristate "MSM Framebuffer support"
2374 depends on FB && ARCH_MSM
2375 select FB_CFB_FILLRECT
2376 select FB_CFB_COPYAREA
2377 select FB_CFB_IMAGEBLIT
2380 tristate "MX3 Framebuffer support"
2381 depends on FB && MX3_IPU
2382 select FB_CFB_FILLRECT
2383 select FB_CFB_COPYAREA
2384 select FB_CFB_IMAGEBLIT
2387 This is a framebuffer device for the i.MX31 LCD Controller. So
2388 far only synchronous displays are supported. If you plan to use
2389 an LCD display with your i.MX31 system, say Y here.
2391 config FB_BROADSHEET
2392 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2394 select FB_SYS_FILLRECT
2395 select FB_SYS_COPYAREA
2396 select FB_SYS_IMAGEBLIT
2398 select FB_DEFERRED_IO
2400 This driver implements support for the E-Ink Broadsheet
2401 controller. The release name for this device was Epson S1D13521
2402 and could also have been called by other names when coupled with
2406 tristate "AUO-K190X EPD controller support"
2408 select FB_SYS_FILLRECT
2409 select FB_SYS_COPYAREA
2410 select FB_SYS_IMAGEBLIT
2412 select FB_DEFERRED_IO
2414 Provides support for epaper controllers from the K190X series
2415 of AUO. These controllers can be used to drive epaper displays
2418 This option enables the common support, shared by the individual
2419 controller drivers. You will also have to enable the driver
2420 for the controller type used in your device.
2423 tristate "AUO-K1900 EPD controller support"
2424 depends on FB && FB_AUO_K190X
2426 This driver implements support for the AUO K1900 epd-controller.
2427 This controller can drive Sipix epaper displays but can only do
2428 serial updates, reducing the number of possible frames per second.
2431 tristate "AUO-K1901 EPD controller support"
2432 depends on FB && FB_AUO_K190X
2434 This driver implements support for the AUO K1901 epd-controller.
2435 This controller can drive Sipix epaper displays and supports
2436 concurrent updates, making higher frames per second possible.
2439 tristate "JZ4740 LCD framebuffer support"
2440 depends on FB && MACH_JZ4740
2441 select FB_SYS_FILLRECT
2442 select FB_SYS_COPYAREA
2443 select FB_SYS_IMAGEBLIT
2445 Framebuffer support for the JZ4740 SoC.
2448 tristate "MXS LCD framebuffer support"
2449 depends on FB && ARCH_MXS
2450 select FB_CFB_FILLRECT
2451 select FB_CFB_COPYAREA
2452 select FB_CFB_IMAGEBLIT
2453 select FB_MODE_HELPERS
2454 select VIDEOMODE_HELPERS
2456 Framebuffer support for the MXS SoC.
2458 config FB_PUV3_UNIGFX
2459 tristate "PKUnity v3 Unigfx framebuffer support"
2460 depends on FB && UNICORE32 && ARCH_PUV3
2461 select FB_SYS_FILLRECT
2462 select FB_SYS_COPYAREA
2463 select FB_SYS_IMAGEBLIT
2466 Choose this option if you want to use the Unigfx device as a
2467 framebuffer device. Without the support of PCI & AGP.
2470 tristate "Microsoft Hyper-V Synthetic Video support"
2471 depends on FB && HYPERV
2472 select FB_CFB_FILLRECT
2473 select FB_CFB_COPYAREA
2474 select FB_CFB_IMAGEBLIT
2476 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2479 bool "Simple framebuffer support"
2480 depends on (FB = y) && OF
2481 select FB_CFB_FILLRECT
2482 select FB_CFB_COPYAREA
2483 select FB_CFB_IMAGEBLIT
2485 Say Y if you want support for a simple frame-buffer.
2487 This driver assumes that the display hardware has been initialized
2488 before the kernel boots, and the kernel will simply render to the
2489 pre-allocated frame buffer surface.
2491 Configuration re: surface address, size, and format must be provided
2492 through device tree, or potentially plain old platform data in the
2495 source "drivers/video/omap/Kconfig"
2496 source "drivers/video/omap2/Kconfig"
2497 source "drivers/video/exynos/Kconfig"
2498 source "drivers/video/mmp/Kconfig"
2499 source "drivers/video/backlight/Kconfig"
2502 source "drivers/video/console/Kconfig"
2505 if FB || SGI_NEWPORT_CONSOLE
2506 source "drivers/video/logo/Kconfig"
2509 config FB_SH_MOBILE_MERAM
2510 tristate "SuperH Mobile MERAM read ahead support"
2511 depends on (SUPERH || ARCH_SHMOBILE)
2512 select GENERIC_ALLOCATOR
2514 Enable MERAM support for the SuperH controller.
2516 This will allow for caching of the framebuffer to provide more
2517 reliable access under heavy main memory bus traffic situations.
2518 Up to 4 memory channels can be configured, allowing 4 RGB or
2519 2 YCbCr framebuffers to be configured.
2522 tristate "Solomon SSD1307 framebuffer support"
2523 depends on FB && I2C
2527 select FB_SYS_FILLRECT
2528 select FB_SYS_COPYAREA
2529 select FB_SYS_IMAGEBLIT
2530 select FB_DEFERRED_IO
2533 This driver implements support for the Solomon SSD1307
2534 OLED controller over I2C.