6 tristate "Support for frame buffer devices"
8 The frame buffer device provides an abstraction for the graphics
9 hardware. It represents the frame buffer of some video hardware and
10 allows application software to access the graphics hardware through
11 a well-defined interface, so the software doesn't need to know
12 anything about the low-level (hardware register) stuff.
14 Frame buffer devices work identically across the different
15 architectures supported by Linux and make the implementation of
16 application programs easier and more portable; at this point, an X
17 server exists which uses the frame buffer device exclusively.
18 On several non-X86 architectures, the frame buffer device is the
19 only way to use the graphics hardware.
21 The device is accessed through special device nodes, usually located
22 in the /dev directory, i.e. /dev/fb*.
24 You need an utility program called fbset to make full use of frame
25 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
26 and the Framebuffer-HOWTO at
27 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
30 Say Y here and to the driver for your graphics board below if you
31 are compiling a kernel for a non-x86 architecture.
33 If you are compiling for the x86 architecture, you can say Y if you
34 want to play with it, but it is not essential. Please note that
35 running graphical applications that directly touch the hardware
36 (e.g. an accelerated X server) and that are not frame buffer
37 device-aware may cause unexpected results. If unsure, say N.
40 bool "Enable firmware EDID"
44 This enables access to the EDID transferred from the firmware.
45 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
46 transfers do not work for your driver and if you are using
47 nvidiafb, i810fb or savagefb.
49 In general, choosing Y for this option is safe. If you
50 experience extremely long delays while booting before you get
51 something on your display, try setting this to N. Matrox cards in
52 combination with certain motherboards and monitors are known to
53 suffer from this problem.
62 config FB_BOOT_VESA_SUPPORT
67 If true, at least one selected framebuffer driver can take advantage
68 of VESA video modes set at an early boot stage via the vga= parameter.
70 config FB_CFB_FILLRECT
75 Include the cfb_fillrect function for generic software rectangle
76 filling. This is used by drivers that don't provide their own
77 (accelerated) version.
79 config FB_CFB_COPYAREA
84 Include the cfb_copyarea function for generic software area copying.
85 This is used by drivers that don't provide their own (accelerated)
88 config FB_CFB_IMAGEBLIT
93 Include the cfb_imageblit function for generic software image
94 blitting. This is used by drivers that don't provide their own
95 (accelerated) version.
97 config FB_CFB_REV_PIXELS_IN_BYTE
102 Allow generic frame-buffer functions to work on displays with 1, 2
103 and 4 bits per pixel depths which has opposite order of pixels in
104 byte order to bytes in long order.
106 config FB_SYS_FILLRECT
111 Include the sys_fillrect function for generic software rectangle
112 filling. This is used by drivers that don't provide their own
113 (accelerated) version and the framebuffer is in system RAM.
115 config FB_SYS_COPYAREA
120 Include the sys_copyarea function for generic software area copying.
121 This is used by drivers that don't provide their own (accelerated)
122 version and the framebuffer is in system RAM.
124 config FB_SYS_IMAGEBLIT
129 Include the sys_imageblit function for generic software image
130 blitting. This is used by drivers that don't provide their own
131 (accelerated) version and the framebuffer is in system RAM.
133 menuconfig FB_FOREIGN_ENDIAN
134 bool "Framebuffer foreign endianness support"
137 This menu will let you enable support for the framebuffers with
138 non-native endianness (e.g. Little-Endian framebuffer on a
139 Big-Endian machine). Most probably you don't have such hardware,
140 so it's safe to say "n" here.
143 prompt "Choice endianness support"
144 depends on FB_FOREIGN_ENDIAN
146 config FB_BOTH_ENDIAN
147 bool "Support for Big- and Little-Endian framebuffers"
150 bool "Support for Big-Endian framebuffers only"
152 config FB_LITTLE_ENDIAN
153 bool "Support for Little-Endian framebuffers only"
162 config FB_DEFERRED_IO
169 depends on FB_DEFERRED_IO
176 Common utility functions useful to fbdev drivers of VGA-based
187 select BACKLIGHT_LCD_SUPPORT
188 select BACKLIGHT_CLASS_DEVICE
191 config FB_MODE_HELPERS
192 bool "Enable Video Mode Handling Helpers"
196 This enables functions for handling video modes using the
197 Generalized Timing Formula and the EDID parser. A few drivers rely
198 on this feature such as the radeonfb, rivafb, and the i810fb. If
199 your driver does not take advantage of this feature, choosing Y will
200 just increase the kernel size by about 5K.
202 config FB_TILEBLITTING
203 bool "Enable Tile Blitting Support"
207 This enables tile blitting. Tile blitting is a drawing technique
208 where the screen is divided into rectangular sections (tiles), whereas
209 the standard blitting divides the screen into pixels. Because the
210 default drawing element is a tile, drawing functions will be passed
211 parameters in terms of number of tiles instead of number of pixels.
212 For example, to draw a single character, instead of using bitmaps,
213 an index to an array of bitmaps will be used. To clear or move a
214 rectangular section of a screen, the rectangle will be described in
215 terms of number of tiles in the x- and y-axis.
217 This is particularly important to one driver, matroxfb. If
220 comment "Frame buffer hardware drivers"
224 tristate "Aeroflex Gaisler framebuffer support"
225 depends on FB && SPARC
226 select FB_CFB_FILLRECT
227 select FB_CFB_COPYAREA
228 select FB_CFB_IMAGEBLIT
230 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
233 tristate "Cirrus Logic support"
234 depends on FB && (ZORRO || PCI)
235 select FB_CFB_FILLRECT
236 select FB_CFB_COPYAREA
237 select FB_CFB_IMAGEBLIT
239 This enables support for Cirrus Logic GD542x/543x based boards on
240 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
242 If you have a PCI-based system, this enables support for these
243 chips: GD-543x, GD-544x, GD-5480.
245 Please read the file <file:Documentation/fb/cirrusfb.txt>.
247 Say N unless you have such a graphics board or plan to get one
248 before you next recompile the kernel.
251 tristate "Permedia2 support"
252 depends on FB && ((AMIGA && BROKEN) || PCI)
253 select FB_CFB_FILLRECT
254 select FB_CFB_COPYAREA
255 select FB_CFB_IMAGEBLIT
257 This is the frame buffer device driver for cards based on
258 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
259 The driver was tested on the following cards:
260 Diamond FireGL 1000 PRO AGP
261 ELSA Gloria Synergy PCI
262 Appian Jeronimo PRO (both heads) PCI
263 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
264 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
265 ASK Graphic Blaster Exxtreme AGP
267 To compile this driver as a module, choose M here: the
268 module will be called pm2fb.
270 config FB_PM2_FIFO_DISCONNECT
271 bool "enable FIFO disconnect feature"
272 depends on FB_PM2 && PCI
274 Support the Permedia2 FIFO disconnect feature.
277 tristate "ARM PrimeCell PL110 support"
278 depends on ARM || ARM64 || COMPILE_TEST
279 depends on FB && ARM_AMBA
280 select FB_CFB_FILLRECT
281 select FB_CFB_COPYAREA
282 select FB_CFB_IMAGEBLIT
284 This framebuffer device driver is for the ARM PrimeCell PL110
285 Colour LCD controller. ARM PrimeCells provide the building
286 blocks for System on a Chip devices.
288 If you want to compile this as a module (=code which can be
289 inserted into and removed from the running kernel), say M
290 here and read <file:Documentation/kbuild/modules.txt>. The module
291 will be called amba-clcd.
294 bool "Acorn VIDC support"
295 depends on (FB = y) && ARM && ARCH_ACORN
296 select FB_CFB_FILLRECT
297 select FB_CFB_COPYAREA
298 select FB_CFB_IMAGEBLIT
300 This is the frame buffer device driver for the Acorn VIDC graphics
301 hardware found in Acorn RISC PCs and other ARM-based machines. If
305 bool "CLPS711X LCD support"
306 depends on (FB = y) && ARM && ARCH_CLPS711X
307 select FB_CFB_FILLRECT
308 select FB_CFB_COPYAREA
309 select FB_CFB_IMAGEBLIT
311 Say Y to enable the Framebuffer driver for the CLPS7111 and
315 bool "SA-1100 LCD support"
316 depends on (FB = y) && ARM && ARCH_SA1100
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
321 This is a framebuffer device for the SA-1100 LCD Controller.
322 See <http://www.linux-fbdev.org/> for information on framebuffer
325 If you plan to use the LCD display with your SA-1100 system, say
329 tristate "Freescale i.MX1/21/25/27 LCD support"
330 depends on FB && ARCH_MXC
331 select BACKLIGHT_LCD_SUPPORT
332 select LCD_CLASS_DEVICE
333 select FB_CFB_FILLRECT
334 select FB_CFB_COPYAREA
335 select FB_CFB_IMAGEBLIT
336 select FB_MODE_HELPERS
337 select VIDEOMODE_HELPERS
340 tristate "CyberPro 2000/2010/5000 support"
341 depends on FB && PCI && (BROKEN || !SPARC64)
342 select FB_CFB_FILLRECT
343 select FB_CFB_COPYAREA
344 select FB_CFB_IMAGEBLIT
346 This enables support for the Integraphics CyberPro 20x0 and 5000
347 VGA chips used in the Rebel.com Netwinder and other machines.
348 Say Y if you have a NetWinder or a graphics card containing this
349 device, otherwise say N.
351 config FB_CYBER2000_DDC
352 bool "DDC for CyberPro support"
353 depends on FB_CYBER2000
357 Say Y here if you want DDC support for your CyberPro graphics
358 card. This is only I2C bus support, driver does not use EDID.
360 config FB_CYBER2000_I2C
361 bool "CyberPro 2000/2010/5000 I2C support"
362 depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
363 depends on I2C=y || FB_CYBER2000=m
366 Enable support for the I2C video decoder interface on the
367 Integraphics CyberPro 20x0 and 5000 VGA chips. This is used
368 on the Netwinder machines for the SAA7111 video capture.
372 depends on (FB = y) && APOLLO
374 select FB_CFB_FILLRECT
375 select FB_CFB_IMAGEBLIT
379 depends on (FB = y) && Q40
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
386 tristate "Amiga native chipset support"
387 depends on FB && AMIGA
389 This is the frame buffer device driver for the builtin graphics
390 chipset found in Amigas.
392 To compile this driver as a module, choose M here: the
393 module will be called amifb.
396 bool "Amiga OCS chipset support"
399 This enables support for the original Agnus and Denise video chips,
400 found in the Amiga 1000 and most A500's and A2000's. If you intend
401 to run Linux on any of these systems, say Y; otherwise say N.
404 bool "Amiga ECS chipset support"
407 This enables support for the Enhanced Chip Set, found in later
408 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
409 you intend to run Linux on any of these systems, say Y; otherwise
413 bool "Amiga AGA chipset support"
416 This enables support for the Advanced Graphics Architecture (also
417 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
418 and CD32. If you intend to run Linux on any of these systems, say Y;
422 bool "Amiga FrameMaster II/Rainbow II support"
423 depends on (FB = y) && ZORRO
424 select FB_CFB_FILLRECT
425 select FB_CFB_COPYAREA
426 select FB_CFB_IMAGEBLIT
428 This is the frame buffer device driver for the Amiga FrameMaster
429 card from BSC (exhibited 1992 but not shipped as a CBM product).
432 tristate "Arc Monochrome LCD board support"
434 select FB_SYS_FILLRECT
435 select FB_SYS_COPYAREA
436 select FB_SYS_IMAGEBLIT
439 This enables support for the Arc Monochrome LCD board. The board
440 is based on the KS-108 lcd controller and is typically a matrix
441 of 2*n chips. This driver was tested with a 128x64 panel. This
442 driver supports it for use with x86 SBCs through a 16 bit GPIO
443 interface (8 bit data, 8 bit control). If you anticipate using
444 this driver, say Y or M; otherwise say N. You must specify the
445 GPIO IO address to be used for setting control and data.
448 bool "Atari native chipset support"
449 depends on (FB = y) && ATARI
450 select FB_CFB_FILLRECT
451 select FB_CFB_COPYAREA
452 select FB_CFB_IMAGEBLIT
454 This is the frame buffer device driver for the builtin graphics
455 chipset found in Ataris.
458 bool "Open Firmware frame buffer device support"
459 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
460 select FB_CFB_FILLRECT
461 select FB_CFB_COPYAREA
462 select FB_CFB_IMAGEBLIT
465 Say Y if you want support with Open Firmware for your graphics
469 bool "Apple \"control\" display support"
470 depends on (FB = y) && PPC_PMAC && PPC32
471 select FB_CFB_FILLRECT
472 select FB_CFB_COPYAREA
473 select FB_CFB_IMAGEBLIT
476 This driver supports a frame buffer for the graphics adapter in the
477 Power Macintosh 7300 and others.
480 bool "Apple \"platinum\" display support"
481 depends on (FB = y) && PPC_PMAC && PPC32
482 select FB_CFB_FILLRECT
483 select FB_CFB_COPYAREA
484 select FB_CFB_IMAGEBLIT
487 This driver supports a frame buffer for the "platinum" graphics
488 adapter in some Power Macintoshes.
491 bool "Apple \"valkyrie\" display support"
492 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
493 select FB_CFB_FILLRECT
494 select FB_CFB_COPYAREA
495 select FB_CFB_IMAGEBLIT
498 This driver supports a frame buffer for the "valkyrie" graphics
499 adapter in some Power Macintoshes.
502 bool "Chips 65550 display support"
503 depends on (FB = y) && PPC32 && PCI
504 select FB_CFB_FILLRECT
505 select FB_CFB_COPYAREA
506 select FB_CFB_IMAGEBLIT
508 This is the frame buffer device driver for the Chips & Technologies
509 65550 graphics chip in PowerBooks.
512 bool "Asiliant (Chips) 69000 display support"
513 depends on (FB = y) && PCI
514 select FB_CFB_FILLRECT
515 select FB_CFB_COPYAREA
516 select FB_CFB_IMAGEBLIT
518 This is the frame buffer device driver for the Asiliant 69030 chipset
521 bool "IMS Twin Turbo display support"
522 depends on (FB = y) && PCI
523 select FB_CFB_IMAGEBLIT
524 select FB_MACMODES if PPC
526 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
527 many Macintosh and compatible computers.
530 tristate "VGA 16-color graphics support"
531 depends on FB && (X86 || PPC)
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
536 select FONT_8x16 if FRAMEBUFFER_CONSOLE
538 This is the frame buffer device driver for VGA 16 color graphic
539 cards. Say Y if you have such a card.
541 To compile this driver as a module, choose M here: the
542 module will be called vga16fb.
544 config FB_BF54X_LQ043
545 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
546 depends on FB && (BF54x) && !BF542
547 select FB_CFB_FILLRECT
548 select FB_CFB_COPYAREA
549 select FB_CFB_IMAGEBLIT
551 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
553 config FB_BFIN_T350MCQB
554 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
555 depends on FB && BLACKFIN
557 select FB_CFB_FILLRECT
558 select FB_CFB_COPYAREA
559 select FB_CFB_IMAGEBLIT
561 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
562 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
563 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
565 config FB_BFIN_LQ035Q1
566 tristate "SHARP LQ035Q1DH02 TFT LCD"
567 depends on FB && BLACKFIN && SPI
568 select FB_CFB_FILLRECT
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
573 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
574 the Blackfin Landscape LCD EZ-Extender Card.
575 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
576 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
578 To compile this driver as a module, choose M here: the
579 module will be called bfin-lq035q1-fb.
581 config FB_BF537_LQ035
582 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
583 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
584 select FB_CFB_FILLRECT
585 select FB_CFB_COPYAREA
586 select FB_CFB_IMAGEBLIT
589 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
592 To compile this driver as a module, choose M here: the
593 module will be called bf537-lq035.
596 tristate "Blackfin ADV7393 Video encoder"
597 depends on FB && BLACKFIN
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
603 This is the framebuffer device for a ADV7393 video encoder
604 attached to a Blackfin on the PPI port.
605 If your Blackfin board has a ADV7393 select Y.
607 To compile this driver as a module, choose M here: the
608 module will be called bfin_adv7393fb.
611 prompt "Video mode support"
612 depends on FB_BFIN_7393
622 bool 'NTSC 640x480 (Experimental)'
625 bool 'PAL 640x480 (Experimental)'
628 bool 'NTSC 720x480 YCbCR input'
631 bool 'PAL 720x576 YCbCR input'
636 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
637 depends on (FB_BFIN_7393)
638 default ADV7393_1XMEM
648 tristate "HP STI frame buffer device support"
649 depends on FB && PARISC
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
657 STI refers to the HP "Standard Text Interface" which is a set of
658 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
659 Enabling this option will implement the linux framebuffer device
660 using calls to the STI BIOS routines for initialisation.
662 If you enable this option, you will get a planar framebuffer device
663 /dev/fb which will work on the most common HP graphic cards of the
664 NGLE family, including the artist chips (in the 7xx and Bxxx series),
665 HCRX, HCRX24, CRX, CRX24 and VisEG series.
667 It is safe to enable this option, so you should probably say "Y".
670 bool "Generic Macintosh display support"
671 depends on (FB = y) && MAC
672 select FB_CFB_FILLRECT
673 select FB_CFB_COPYAREA
674 select FB_CFB_IMAGEBLIT
679 depends on (FB = y) && DIO
680 select FB_CFB_IMAGEBLIT
684 tristate "TGA/SFB+ framebuffer support"
685 depends on FB && (ALPHA || TC)
686 select FB_CFB_FILLRECT
687 select FB_CFB_COPYAREA
688 select FB_CFB_IMAGEBLIT
691 This is the frame buffer device driver for generic TGA and SFB+
692 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
693 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
694 TURBOchannel cards, also known as PMAGD-A, -B and -C.
696 Due to hardware limitations ZLX-E2 and E3 cards are not supported
697 for DECstation 5000/200 systems. Additionally due to firmware
698 limitations these cards may cause troubles with booting DECstation
699 5000/240 and /260 systems, but are fully supported under Linux if
700 you manage to get it going. ;-)
702 Say Y if you have one of those.
705 tristate "Userspace VESA VGA graphics support"
706 depends on FB && CONNECTOR
707 select FB_CFB_FILLRECT
708 select FB_CFB_COPYAREA
709 select FB_CFB_IMAGEBLIT
710 select FB_MODE_HELPERS
712 This is the frame buffer driver for generic VBE 2.0 compliant
713 graphic cards. It can also take advantage of VBE 3.0 features,
714 such as refresh rate adjustment.
716 This driver generally provides more features than vesafb but
717 requires a userspace helper application called 'v86d'. See
718 <file:Documentation/fb/uvesafb.txt> for more information.
723 bool "VESA VGA graphics support"
724 depends on (FB = y) && X86
725 select FB_CFB_FILLRECT
726 select FB_CFB_COPYAREA
727 select FB_CFB_IMAGEBLIT
728 select FB_BOOT_VESA_SUPPORT
730 This is the frame buffer device driver for generic VESA 2.0
731 compliant graphic cards. The older VESA 1.2 cards are not supported.
732 You will get a boot time penguin logo at no additional cost. Please
733 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
736 bool "EFI-based Framebuffer Support"
737 depends on (FB = y) && X86 && EFI
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
742 This is the EFI frame buffer device driver. If the firmware on
743 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
744 using the EFI framebuffer as your console.
747 tristate "N411 Apollo/Hecuba devkit support"
748 depends on FB && X86 && MMU
749 select FB_SYS_FILLRECT
750 select FB_SYS_COPYAREA
751 select FB_SYS_IMAGEBLIT
753 select FB_DEFERRED_IO
756 This enables support for the Apollo display controller in its
757 Hecuba form using the n411 devkit.
760 tristate "Hercules mono graphics support"
763 Say Y here if you have a Hercules mono graphics card.
765 To compile this driver as a module, choose M here: the
766 module will be called hgafb.
768 As this card technology is at least 25 years old,
769 most people will answer N here.
772 bool "SGI Graphics Backend frame buffer support"
773 depends on (FB = y) && SGI_IP32
774 select FB_CFB_FILLRECT
775 select FB_CFB_COPYAREA
776 select FB_CFB_IMAGEBLIT
778 This is the frame buffer device driver for SGI Graphics Backend.
779 This chip is used in SGI O2 and Visual Workstation 320/540.
782 int "Video memory size in MB"
786 This is the amount of memory reserved for the framebuffer,
787 which can be any value between 1MB and 8MB.
790 bool "SBUS and UPA framebuffers"
791 depends on (FB = y) && SPARC
793 Say Y if you want support for SBUS or UPA based frame buffer device.
797 depends on (FB = y) && (SPARC && FB_SBUS)
798 select FB_CFB_FILLRECT
799 select FB_CFB_COPYAREA
800 select FB_CFB_IMAGEBLIT
802 This is the frame buffer device driver for the BWtwo frame buffer.
805 bool "CGthree support"
806 depends on (FB = y) && (SPARC && FB_SBUS)
807 select FB_CFB_FILLRECT
808 select FB_CFB_COPYAREA
809 select FB_CFB_IMAGEBLIT
811 This is the frame buffer device driver for the CGthree frame buffer.
814 bool "CGsix (GX,TurboGX) support"
815 depends on (FB = y) && (SPARC && FB_SBUS)
816 select FB_CFB_COPYAREA
817 select FB_CFB_IMAGEBLIT
819 This is the frame buffer device driver for the CGsix (GX, TurboGX)
823 bool "Creator/Creator3D/Elite3D support"
824 depends on FB_SBUS && SPARC64
825 select FB_CFB_COPYAREA
826 select FB_CFB_IMAGEBLIT
828 This is the frame buffer device driver for the Creator, Creator3D,
829 and Elite3D graphics boards.
832 bool "TCX (SS4/SS5 only) support"
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 This is the frame buffer device driver for the TCX 24/8bit frame
842 bool "CGfourteen (SX) support"
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This is the frame buffer device driver for the CGfourteen frame
849 buffer on Desktop SPARCsystems with the SX graphics option.
852 bool "P9100 (Sparcbook 3 only) support"
854 select FB_CFB_FILLRECT
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the frame buffer device driver for the P9100 card
859 supported on Sparcbook 3 machines.
862 bool "Leo (ZX) support"
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This is the frame buffer device driver for the SBUS-based Sun ZX
869 (leo) frame buffer cards.
872 bool "IGA 168x display support"
873 depends on (FB = y) && SPARC32
874 select FB_CFB_FILLRECT
875 select FB_CFB_COPYAREA
876 select FB_CFB_IMAGEBLIT
878 This is the framebuffer device for the INTERGRAPHICS 1680 and
879 successor frame buffer cards.
882 bool "Sun XVR-500 3DLABS Wildcat support"
883 depends on (FB = y) && PCI && SPARC64
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 This is the framebuffer device for the Sun XVR-500 and similar
889 graphics cards based upon the 3DLABS Wildcat chipset. The driver
890 only works on sparc64 systems where the system firmware has
891 mostly initialized the card already. It is treated as a
892 completely dumb framebuffer device.
895 bool "Sun XVR-2500 3DLABS Wildcat support"
896 depends on (FB = y) && PCI && SPARC64
897 select FB_CFB_FILLRECT
898 select FB_CFB_COPYAREA
899 select FB_CFB_IMAGEBLIT
901 This is the framebuffer device for the Sun XVR-2500 and similar
902 graphics cards based upon the 3DLABS Wildcat chipset. The driver
903 only works on sparc64 systems where the system firmware has
904 mostly initialized the card already. It is treated as a
905 completely dumb framebuffer device.
908 bool "Sun XVR-1000 support"
909 depends on (FB = y) && SPARC64
910 select FB_CFB_FILLRECT
911 select FB_CFB_COPYAREA
912 select FB_CFB_IMAGEBLIT
914 This is the framebuffer device for the Sun XVR-1000 and similar
915 graphics cards. The driver only works on sparc64 systems where
916 the system firmware has mostly initialized the card already. It
917 is treated as a completely dumb framebuffer device.
920 tristate "NEC PowerVR 2 display support"
921 depends on FB && SH_DREAMCAST
922 select FB_CFB_FILLRECT
923 select FB_CFB_COPYAREA
924 select FB_CFB_IMAGEBLIT
926 Say Y here if you have a PowerVR 2 card in your box. If you plan to
927 run linux on your Dreamcast, you will have to say Y here.
928 This driver may or may not work on other PowerVR 2 cards, but is
929 totally untested. Use at your own risk. If unsure, say N.
931 To compile this driver as a module, choose M here: the
932 module will be called pvr2fb.
934 You can pass several parameters to the driver at boot time or at
935 module load time. The parameters look like "video=pvr2:XXX", where
936 the meaning of XXX can be found at the end of the main source file
937 (<file:drivers/video/pvr2fb.c>). Please see the file
938 <file:Documentation/fb/pvr2fb.txt>.
941 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
942 depends on FB && HAS_DMA
943 select FB_CFB_FILLRECT
944 select FB_CFB_COPYAREA
945 select FB_CFB_IMAGEBLIT
947 This enables support for the OpenCores VGA/LCD core.
949 The OpenCores VGA/LCD core is typically used together with
950 softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
951 systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
953 The source code and specification for the core is available at
954 <http://opencores.org/project,vga_lcd>
957 tristate "Epson S1D13XXX framebuffer support"
959 select FB_CFB_FILLRECT
960 select FB_CFB_COPYAREA
961 select FB_CFB_IMAGEBLIT
963 Support for S1D13XXX framebuffer device family (currently only
964 working with S1D13806). Product specs at
965 <http://vdc.epson.com/>
968 tristate "AT91/AT32 LCD Controller support"
969 depends on FB && HAVE_FB_ATMEL
971 select FB_CFB_FILLRECT
972 select FB_CFB_COPYAREA
973 select FB_CFB_IMAGEBLIT
974 select FB_MODE_HELPERS
975 select VIDEOMODE_HELPERS
977 This enables support for the AT91/AT32 LCD Controller.
980 bool "Frame Buffer in internal SRAM"
981 depends on FB_ATMEL && ARCH_AT91SAM9261
983 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
984 to let frame buffer in external SDRAM.
987 bool "Use a STN display with AT91/AT32 LCD Controller"
988 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
991 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
992 Controller. Say N if you want to connect a TFT.
997 tristate "nVidia Framebuffer Support"
999 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1000 select FB_MODE_HELPERS
1001 select FB_CFB_FILLRECT
1002 select FB_CFB_COPYAREA
1003 select FB_CFB_IMAGEBLIT
1007 This driver supports graphics boards with the nVidia chips, TNT
1008 and newer. For very old chipsets, such as the RIVA128, then use
1010 Say Y if you have such a graphics board.
1012 To compile this driver as a module, choose M here: the
1013 module will be called nvidiafb.
1015 config FB_NVIDIA_I2C
1016 bool "Enable DDC Support"
1017 depends on FB_NVIDIA
1020 This enables I2C support for nVidia Chipsets. This is used
1021 only for getting EDID information from the attached display
1022 allowing for robust video mode handling and switching.
1024 Because fbdev-2.6 requires that drivers must be able to
1025 independently validate video mode parameters, you should say Y
1028 config FB_NVIDIA_DEBUG
1029 bool "Lots of debug output"
1030 depends on FB_NVIDIA
1033 Say Y here if you want the nVidia driver to output all sorts
1034 of debugging information to provide to the maintainer when
1035 something goes wrong.
1037 config FB_NVIDIA_BACKLIGHT
1038 bool "Support for backlight control"
1039 depends on FB_NVIDIA
1042 Say Y here if you want to control the backlight of your display.
1045 tristate "nVidia Riva support"
1046 depends on FB && PCI
1047 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1048 select FB_MODE_HELPERS
1049 select FB_CFB_FILLRECT
1050 select FB_CFB_COPYAREA
1051 select FB_CFB_IMAGEBLIT
1055 This driver supports graphics boards with the nVidia Riva/Geforce
1057 Say Y if you have such a graphics board.
1059 To compile this driver as a module, choose M here: the
1060 module will be called rivafb.
1063 bool "Enable DDC Support"
1067 This enables I2C support for nVidia Chipsets. This is used
1068 only for getting EDID information from the attached display
1069 allowing for robust video mode handling and switching.
1071 Because fbdev-2.6 requires that drivers must be able to
1072 independently validate video mode parameters, you should say Y
1075 config FB_RIVA_DEBUG
1076 bool "Lots of debug output"
1080 Say Y here if you want the Riva driver to output all sorts
1081 of debugging information to provide to the maintainer when
1082 something goes wrong.
1084 config FB_RIVA_BACKLIGHT
1085 bool "Support for backlight control"
1089 Say Y here if you want to control the backlight of your display.
1092 tristate "Intel740 support"
1093 depends on FB && PCI
1094 select FB_MODE_HELPERS
1095 select FB_CFB_FILLRECT
1096 select FB_CFB_COPYAREA
1097 select FB_CFB_IMAGEBLIT
1101 This driver supports graphics cards based on Intel740 chip.
1104 tristate "Intel 810/815 support"
1105 depends on FB && PCI && X86_32 && AGP_INTEL
1106 select FB_MODE_HELPERS
1107 select FB_CFB_FILLRECT
1108 select FB_CFB_COPYAREA
1109 select FB_CFB_IMAGEBLIT
1112 This driver supports the on-board graphics built in to the Intel 810
1113 and 815 chipsets. Say Y if you have and plan to use such a board.
1115 To compile this driver as a module, choose M here: the
1116 module will be called i810fb.
1118 For more information, please read
1119 <file:Documentation/fb/intel810.txt>
1122 bool "use VESA Generalized Timing Formula"
1125 If you say Y, then the VESA standard, Generalized Timing Formula
1126 or GTF, will be used to calculate the required video timing values
1127 per video mode. Since the GTF allows nondiscrete timings
1128 (nondiscrete being a range of values as opposed to discrete being a
1129 set of values), you'll be able to use any combination of horizontal
1130 and vertical resolutions, and vertical refresh rates without having
1131 to specify your own timing parameters. This is especially useful
1132 to maximize the performance of an aging display, or if you just
1133 have a display with nonstandard dimensions. A VESA compliant
1134 monitor is recommended, but can still work with non-compliant ones.
1135 If you need or want this, then select this option. The timings may
1136 not be compliant with Intel's recommended values. Use at your own
1139 If you say N, the driver will revert to discrete video timings
1140 using a set recommended by Intel in their documentation.
1145 bool "Enable DDC Support"
1146 depends on FB_I810 && FB_I810_GTF
1151 tristate "Intel LE80578 (Vermilion) support"
1152 depends on FB && PCI && X86
1153 select FB_MODE_HELPERS
1154 select FB_CFB_FILLRECT
1155 select FB_CFB_COPYAREA
1156 select FB_CFB_IMAGEBLIT
1158 This driver supports the LE80578 (Vermilion Range) chipset
1160 config FB_CARILLO_RANCH
1161 tristate "Intel Carillo Ranch support"
1162 depends on FB_LE80578 && FB && PCI && X86
1164 This driver supports the LE80578 (Carillo Ranch) board
1167 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
1168 depends on FB && PCI && X86 && AGP_INTEL && EXPERT
1169 select FB_MODE_HELPERS
1170 select FB_CFB_FILLRECT
1171 select FB_CFB_COPYAREA
1172 select FB_CFB_IMAGEBLIT
1173 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1174 depends on !DRM_I915
1176 This driver supports the on-board graphics built in to the Intel
1177 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1178 Say Y if you have and plan to use such a board.
1180 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1182 To compile this driver as a module, choose M here: the
1183 module will be called intelfb.
1185 For more information, please read <file:Documentation/fb/intelfb.txt>
1187 config FB_INTEL_DEBUG
1188 bool "Intel driver Debug Messages"
1191 Say Y here if you want the Intel driver to output all sorts
1192 of debugging information to provide to the maintainer when
1193 something goes wrong.
1196 bool "DDC/I2C for Intel framebuffer support"
1201 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1204 tristate "Matrox acceleration"
1205 depends on FB && PCI
1206 select FB_CFB_FILLRECT
1207 select FB_CFB_COPYAREA
1208 select FB_CFB_IMAGEBLIT
1209 select FB_TILEBLITTING
1210 select FB_MACMODES if PPC_PMAC
1212 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1213 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1214 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1215 Matrox G400, G450 or G550 card in your box.
1217 To compile this driver as a module, choose M here: the
1218 module will be called matroxfb.
1220 You can pass several parameters to the driver at boot time or at
1221 module load time. The parameters look like "video=matroxfb:XXX", and
1222 are described in <file:Documentation/fb/matroxfb.txt>.
1224 config FB_MATROX_MILLENIUM
1225 bool "Millennium I/II support"
1226 depends on FB_MATROX
1228 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1229 video card. If you select "Advanced lowlevel driver options" below,
1230 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1231 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1232 also use font widths different from 8.
1234 config FB_MATROX_MYSTIQUE
1235 bool "Mystique support"
1236 depends on FB_MATROX
1238 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1239 video card. If you select "Advanced lowlevel driver options" below,
1240 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1241 packed pixel and 32 bpp packed pixel. You can also use font widths
1245 bool "G100/G200/G400/G450/G550 support"
1246 depends on FB_MATROX
1248 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1249 video card. If you select "Advanced lowlevel driver options", you
1250 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1251 pixel and 32 bpp packed pixel. You can also use font widths
1254 If you need support for G400 secondary head, you must say Y to
1255 "Matrox I2C support" and "G400 second head support" right below.
1256 G450/G550 secondary head and digital output are supported without
1259 The driver starts in monitor mode. You must use the matroxset tool
1260 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1261 swap primary and secondary head outputs, or to change output mode.
1262 Secondary head driver always start in 640x480 resolution and you
1263 must use fbset to change it.
1265 Do not forget that second head supports only 16 and 32 bpp
1266 packed pixels, so it is a good idea to compile them into the kernel
1267 too. You can use only some font widths, as the driver uses generic
1268 painting procedures (the secondary head does not use acceleration
1271 G450/G550 hardware can display TV picture only from secondary CRTC,
1272 and it performs no scaling, so picture must have 525 or 625 lines.
1274 config FB_MATROX_I2C
1275 tristate "Matrox I2C support"
1276 depends on FB_MATROX
1279 This drivers creates I2C buses which are needed for accessing the
1280 DDC (I2C) bus present on all Matroxes, an I2C bus which
1281 interconnects Matrox optional devices, like MGA-TVO on G200 and
1282 G400, and the secondary head DDC bus, present on G400 only.
1284 You can say Y or M here if you want to experiment with monitor
1285 detection code. You must say Y or M here if you want to use either
1286 second head of G400 or MGA-TVO on G200 or G400.
1288 If you compile it as module, it will create a module named
1291 config FB_MATROX_MAVEN
1292 tristate "G400 second head support"
1293 depends on FB_MATROX_G && FB_MATROX_I2C
1295 WARNING !!! This support does not work with G450 !!!
1297 Say Y or M here if you want to use a secondary head (meaning two
1298 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1299 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1300 secondary head output is blanked while you are in X. With XFree
1301 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1302 the fbdev driver on first head and the fbdev driver on second head.
1304 If you compile it as module, two modules are created,
1305 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1306 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1307 also load i2c-matroxfb to get it to run.
1309 The driver starts in monitor mode and you must use the matroxset
1311 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1312 PAL or NTSC or to swap primary and secondary head outputs.
1313 Secondary head driver also always start in 640x480 resolution, you
1314 must use fbset to change it.
1316 Also do not forget that second head supports only 16 and 32 bpp
1317 packed pixels, so it is a good idea to compile them into the kernel
1318 too. You can use only some font widths, as the driver uses generic
1319 painting procedures (the secondary head does not use acceleration
1323 tristate "ATI Radeon display support"
1324 depends on FB && PCI
1325 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1326 select FB_MODE_HELPERS
1327 select FB_CFB_FILLRECT
1328 select FB_CFB_COPYAREA
1329 select FB_CFB_IMAGEBLIT
1330 select FB_MACMODES if PPC_OF
1332 Choose this option if you want to use an ATI Radeon graphics card as
1333 a framebuffer device. There are both PCI and AGP versions. You
1334 don't need to choose this to run the Radeon in plain VGA mode.
1336 There is a product page at
1337 http://products.amd.com/en-us/GraphicCardResult.aspx
1339 config FB_RADEON_I2C
1340 bool "DDC/I2C for ATI Radeon support"
1341 depends on FB_RADEON
1345 Say Y here if you want DDC/I2C support for your Radeon board.
1347 config FB_RADEON_BACKLIGHT
1348 bool "Support for backlight control"
1349 depends on FB_RADEON
1352 Say Y here if you want to control the backlight of your display.
1354 config FB_RADEON_DEBUG
1355 bool "Lots of debug output from Radeon driver"
1356 depends on FB_RADEON
1359 Say Y here if you want the Radeon driver to output all sorts
1360 of debugging information to provide to the maintainer when
1361 something goes wrong.
1364 tristate "ATI Rage128 display support"
1365 depends on FB && PCI
1366 select FB_CFB_FILLRECT
1367 select FB_CFB_COPYAREA
1368 select FB_CFB_IMAGEBLIT
1369 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1370 select FB_MACMODES if PPC_PMAC
1372 This driver supports graphics boards with the ATI Rage128 chips.
1373 Say Y if you have such a graphics board and read
1374 <file:Documentation/fb/aty128fb.txt>.
1376 To compile this driver as a module, choose M here: the
1377 module will be called aty128fb.
1379 config FB_ATY128_BACKLIGHT
1380 bool "Support for backlight control"
1381 depends on FB_ATY128
1384 Say Y here if you want to control the backlight of your display.
1387 tristate "ATI Mach64 display support" if PCI || ATARI
1388 depends on FB && !SPARC32
1389 select FB_CFB_FILLRECT
1390 select FB_CFB_COPYAREA
1391 select FB_CFB_IMAGEBLIT
1392 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1393 select FB_MACMODES if PPC
1395 This driver supports graphics boards with the ATI Mach64 chips.
1396 Say Y if you have such a graphics board.
1398 To compile this driver as a module, choose M here: the
1399 module will be called atyfb.
1402 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1403 depends on PCI && FB_ATY
1404 default y if SPARC64 && PCI
1406 Say Y here to support use of ATI's 64-bit Rage boards (or other
1407 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1408 framebuffer device. The ATI product support page for these boards
1409 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1411 config FB_ATY_GENERIC_LCD
1412 bool "Mach64 generic LCD support"
1413 depends on FB_ATY_CT
1415 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1416 Rage XC, or Rage XL chipset.
1419 bool "Mach64 GX support" if PCI
1423 Say Y here to support use of the ATI Mach64 Graphics Expression
1424 board (or other boards based on the Mach64 GX chipset) as a
1425 framebuffer device. The ATI product support page for these boards
1427 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1429 config FB_ATY_BACKLIGHT
1430 bool "Support for backlight control"
1434 Say Y here if you want to control the backlight of your display.
1437 tristate "S3 Trio/Virge support"
1438 depends on FB && PCI
1439 select FB_CFB_FILLRECT
1440 select FB_CFB_COPYAREA
1441 select FB_CFB_IMAGEBLIT
1442 select FB_TILEBLITTING
1445 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1447 Driver for graphics boards with S3 Trio / S3 Virge chip.
1450 bool "DDC for S3 support"
1455 Say Y here if you want DDC support for your S3 graphics card.
1458 tristate "S3 Savage support"
1459 depends on FB && PCI
1460 select FB_MODE_HELPERS
1461 select FB_CFB_FILLRECT
1462 select FB_CFB_COPYAREA
1463 select FB_CFB_IMAGEBLIT
1466 This driver supports notebooks and computers with S3 Savage PCI/AGP
1469 Say Y if you have such a graphics card.
1471 To compile this driver as a module, choose M here; the module
1472 will be called savagefb.
1474 config FB_SAVAGE_I2C
1475 bool "Enable DDC2 Support"
1476 depends on FB_SAVAGE
1479 This enables I2C support for S3 Savage Chipsets. This is used
1480 only for getting EDID information from the attached display
1481 allowing for robust video mode handling and switching.
1483 Because fbdev-2.6 requires that drivers must be able to
1484 independently validate video mode parameters, you should say Y
1487 config FB_SAVAGE_ACCEL
1488 bool "Enable Console Acceleration"
1489 depends on FB_SAVAGE
1492 This option will compile in console acceleration support. If
1493 the resulting framebuffer console has bothersome glitches, then
1497 tristate "SiS/XGI display support"
1498 depends on FB && PCI
1499 select FB_CFB_FILLRECT
1500 select FB_CFB_COPYAREA
1501 select FB_CFB_IMAGEBLIT
1502 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1504 This is the frame buffer device driver for the SiS 300, 315, 330
1505 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1506 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1508 To compile this driver as a module, choose M here; the module
1509 will be called sisfb.
1512 bool "SiS 300 series support"
1515 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1518 bool "SiS 315/330/340 series and XGI support"
1521 Say Y here to support use of the SiS 315, 330 and 340 series
1522 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1523 as XGI V3XT, V5, V8 and Z7.
1526 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1527 depends on FB && PCI && X86
1528 select FB_CFB_FILLRECT
1529 select FB_CFB_COPYAREA
1530 select FB_CFB_IMAGEBLIT
1535 This is the frame buffer device driver for Graphics chips of VIA
1536 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1537 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1539 Say Y if you have a VIA UniChrome graphics board.
1541 To compile this driver as a module, choose M here: the
1542 module will be called viafb.
1546 config FB_VIA_DIRECT_PROCFS
1547 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1551 Allow direct hardware access to some output registers via procfs.
1552 This is dangerous but may provide the only chance to get the
1553 correct output device configuration.
1554 Its use is strongly discouraged.
1556 config FB_VIA_X_COMPATIBILITY
1557 bool "X server compatibility"
1561 This option reduces the functionality (power saving, ...) of the
1562 framebuffer to avoid negative impact on the OpenChrome X server.
1563 If you use any X server other than fbdev you should enable this
1564 otherwise it should be safe to disable it and allow using all
1570 tristate "NeoMagic display support"
1571 depends on FB && PCI
1572 select FB_MODE_HELPERS
1573 select FB_CFB_FILLRECT
1574 select FB_CFB_COPYAREA
1575 select FB_CFB_IMAGEBLIT
1578 This driver supports notebooks with NeoMagic PCI chips.
1579 Say Y if you have such a graphics card.
1581 To compile this driver as a module, choose M here: the
1582 module will be called neofb.
1585 tristate "IMG Kyro support"
1586 depends on FB && PCI
1587 select FB_CFB_FILLRECT
1588 select FB_CFB_COPYAREA
1589 select FB_CFB_IMAGEBLIT
1591 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1594 To compile this driver as a module, choose M here: the
1595 module will be called kyrofb.
1598 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1599 depends on FB && PCI
1600 select FB_CFB_IMAGEBLIT
1601 select FB_CFB_FILLRECT
1602 select FB_CFB_COPYAREA
1603 select FB_MODE_HELPERS
1605 This driver supports graphics boards with the 3Dfx Banshee,
1606 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1607 such a graphics board.
1609 To compile this driver as a module, choose M here: the
1610 module will be called tdfxfb.
1612 config FB_3DFX_ACCEL
1613 bool "3Dfx Acceleration functions"
1616 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1617 device driver with acceleration functions.
1620 bool "Enable DDC/I2C support"
1625 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1628 tristate "3Dfx Voodoo Graphics (sst1) 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 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1635 Voodoo2 (cvg) based graphics card.
1637 To compile this driver as a module, choose M here: the
1638 module will be called sstfb.
1640 WARNING: Do not use any application that uses the 3D engine
1641 (namely glide) while using this driver.
1642 Please read the <file:Documentation/fb/sstfb.txt> for supported
1643 options and other important info support.
1646 tristate "VIA VT8623 support"
1647 depends on FB && PCI
1648 select FB_CFB_FILLRECT
1649 select FB_CFB_COPYAREA
1650 select FB_CFB_IMAGEBLIT
1651 select FB_TILEBLITTING
1654 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1656 Driver for CastleRock integrated graphics core in the
1657 VIA VT8623 [Apollo CLE266] chipset.
1660 tristate "Trident/CyberXXX/CyberBlade support"
1661 depends on FB && PCI
1662 select FB_CFB_FILLRECT
1663 select FB_CFB_COPYAREA
1664 select FB_CFB_IMAGEBLIT
1666 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1667 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1669 There are also integrated versions of these chips called CyberXXXX,
1670 CyberImage or CyberBlade. These chips are mostly found in laptops
1671 but also on some motherboards including early VIA EPIA motherboards.
1672 For more information, read <file:Documentation/fb/tridentfb.txt>
1674 Say Y if you have such a graphics board.
1676 To compile this driver as a module, choose M here: the
1677 module will be called tridentfb.
1680 tristate "ARK 2000PV support"
1681 depends on FB && PCI
1682 select FB_CFB_FILLRECT
1683 select FB_CFB_COPYAREA
1684 select FB_CFB_IMAGEBLIT
1685 select FB_TILEBLITTING
1688 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1690 Driver for PCI graphics boards with ARK 2000PV chip
1691 and ICS 5342 RAMDAC.
1694 tristate "Permedia3 support"
1695 depends on FB && PCI
1696 select FB_CFB_FILLRECT
1697 select FB_CFB_COPYAREA
1698 select FB_CFB_IMAGEBLIT
1700 This is the frame buffer device driver for the 3DLabs Permedia3
1701 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1702 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1703 and maybe other boards.
1706 tristate "Fujitsu carmine frame buffer support"
1707 depends on FB && PCI
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 This is the frame buffer device driver for the Fujitsu Carmine chip.
1713 The driver provides two independent frame buffer devices.
1716 depends on FB_CARMINE
1717 prompt "DRAM timing"
1718 default FB_CARMINE_DRAM_EVAL
1720 config FB_CARMINE_DRAM_EVAL
1721 bool "Eval board timings"
1723 Use timings which work on the eval card.
1725 config CARMINE_DRAM_CUSTOM
1726 bool "Custom board timings"
1728 Use custom board timings.
1732 bool "Au1100 LCD Driver"
1733 depends on (FB = y) && MIPS_ALCHEMY
1734 select FB_CFB_FILLRECT
1735 select FB_CFB_COPYAREA
1736 select FB_CFB_IMAGEBLIT
1738 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1739 various panels and CRTs by passing in kernel cmd line option
1740 au1100fb:panel=<name>.
1743 bool "Au1200/Au1300 LCD Driver"
1744 depends on (FB = y) && MIPS_ALCHEMY
1745 select FB_SYS_FILLRECT
1746 select FB_SYS_COPYAREA
1747 select FB_SYS_IMAGEBLIT
1750 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1751 It can drive various panels and CRTs by passing in kernel cmd line
1752 option au1200fb:panel=<name>.
1755 bool "VIA VT8500 framebuffer support"
1756 depends on (FB = y) && ARM && ARCH_VT8500
1757 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1758 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1759 select FB_SYS_IMAGEBLIT
1760 select FB_MODE_HELPERS
1761 select VIDEOMODE_HELPERS
1763 This is the framebuffer driver for VIA VT8500 integrated LCD
1767 bool "Wondermedia WM8xxx-series frame buffer support"
1768 depends on (FB = y) && ARM && ARCH_VT8500
1769 select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1770 select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1771 select FB_SYS_IMAGEBLIT
1772 select FB_MODE_HELPERS
1773 select VIDEOMODE_HELPERS
1775 This is the framebuffer driver for WonderMedia WM8xxx-series
1776 integrated LCD controller. This driver covers the WM8505, WM8650
1779 config FB_WMT_GE_ROPS
1780 bool "VT8500/WM8xxx accelerated raster ops support"
1781 depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1784 This adds support for accelerated raster operations on the
1785 VIA VT8500 and Wondermedia 85xx series SoCs.
1787 source "drivers/video/fbdev/geode/Kconfig"
1790 tristate "HD64461 Frame Buffer support"
1791 depends on FB && HD64461
1792 select FB_CFB_FILLRECT
1793 select FB_CFB_COPYAREA
1794 select FB_CFB_IMAGEBLIT
1796 This is the frame buffer device driver for the Hitachi HD64461 LCD
1800 bool "PMAG-AA TURBOchannel framebuffer support"
1801 depends on (FB = y) && TC
1802 select FB_CFB_FILLRECT
1803 select FB_CFB_COPYAREA
1804 select FB_CFB_IMAGEBLIT
1806 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1807 used mainly in the MIPS-based DECstation series.
1810 tristate "PMAG-BA TURBOchannel framebuffer support"
1812 select FB_CFB_FILLRECT
1813 select FB_CFB_COPYAREA
1814 select FB_CFB_IMAGEBLIT
1816 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1817 used mainly in the MIPS-based DECstation series.
1820 tristate "PMAGB-B TURBOchannel framebuffer support"
1822 select FB_CFB_FILLRECT
1823 select FB_CFB_COPYAREA
1824 select FB_CFB_IMAGEBLIT
1826 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1827 in the MIPS-based DECstation series. The card is currently only
1828 supported in 1280x1024x8 mode.
1831 bool "Maxine (Personal DECstation) onboard framebuffer support"
1832 depends on (FB = y) && MACH_DECSTATION
1833 select FB_CFB_FILLRECT
1834 select FB_CFB_COPYAREA
1835 select FB_CFB_IMAGEBLIT
1837 Support for the onboard framebuffer (1024x768x8) in the Personal
1838 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1842 bool "G364 frame buffer support"
1843 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1848 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1849 Olivetti M700-10 systems.
1852 bool "Motorola 68328 native frame buffer support"
1853 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1854 select FB_CFB_FILLRECT
1855 select FB_CFB_COPYAREA
1856 select FB_CFB_IMAGEBLIT
1858 Say Y here if you want to support the built-in frame buffer of
1859 the Motorola 68328 CPU family.
1862 tristate "PXA168/910 LCD framebuffer support"
1863 depends on FB && (CPU_PXA168 || CPU_PXA910)
1864 select FB_CFB_FILLRECT
1865 select FB_CFB_COPYAREA
1866 select FB_CFB_IMAGEBLIT
1868 Frame buffer driver for the built-in LCD controller in the Marvell
1872 tristate "PXA LCD framebuffer support"
1873 depends on FB && ARCH_PXA
1874 select FB_CFB_FILLRECT
1875 select FB_CFB_COPYAREA
1876 select FB_CFB_IMAGEBLIT
1878 Frame buffer driver for the built-in LCD controller in the Intel
1881 This driver is also available as a module ( = code which can be
1882 inserted and removed from the running kernel whenever you want). The
1883 module will be called pxafb. If you want to compile it as a module,
1884 say M here and read <file:Documentation/kbuild/modules.txt>.
1888 config FB_PXA_OVERLAY
1889 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1891 depends on FB_PXA && (PXA27x || PXA3xx)
1893 config FB_PXA_SMARTPANEL
1894 bool "PXA Smartpanel LCD support"
1898 config FB_PXA_PARAMETERS
1899 bool "PXA LCD command line parameters"
1903 Enable the use of kernel command line or module parameters
1904 to configure the physical properties of the LCD panel when
1905 using the PXA LCD driver.
1907 This option allows you to override the panel parameters
1908 supplied by the platform in order to support multiple
1909 different models of flatpanel. If you will only be using a
1910 single model of flatpanel then you can safely leave this
1913 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1916 tristate "PXA3xx 2D graphics accelerator driver"
1919 Kernelspace driver for the 2D graphics controller unit (GCU)
1920 found on PXA3xx processors. There is a counterpart driver in the
1921 DirectFB suite, see http://www.directfb.org/
1923 If you compile this as a module, it will be called pxa3xx_gcu.
1926 tristate "2700G LCD framebuffer support"
1927 depends on FB && ARCH_PXA
1928 select FB_CFB_FILLRECT
1929 select FB_CFB_COPYAREA
1930 select FB_CFB_IMAGEBLIT
1932 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1936 bool "Enable debugging info via debugfs"
1937 depends on FB_MBX && DEBUG_FS
1940 Enable this if you want debugging information using the debug
1941 filesystem (debugfs)
1946 tristate "Freescale DIU framebuffer support"
1947 depends on FB && FSL_SOC
1948 select FB_MODE_HELPERS
1949 select FB_CFB_FILLRECT
1950 select FB_CFB_COPYAREA
1951 select FB_CFB_IMAGEBLIT
1952 select PPC_LIB_RHEAP
1954 Framebuffer driver for the Freescale SoC DIU
1957 tristate "W100 frame buffer support"
1958 depends on FB && ARCH_PXA
1959 select FB_CFB_FILLRECT
1960 select FB_CFB_COPYAREA
1961 select FB_CFB_IMAGEBLIT
1963 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1964 It can also drive the w3220 chip found on iPAQ hx4700.
1966 This driver is also available as a module ( = code which can be
1967 inserted and removed from the running kernel whenever you want). The
1968 module will be called w100fb. If you want to compile it as a module,
1969 say M here and read <file:Documentation/kbuild/modules.txt>.
1973 config FB_SH_MOBILE_LCDC
1974 tristate "SuperH Mobile LCDC framebuffer support"
1975 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1976 depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM
1977 select FB_SYS_FILLRECT
1978 select FB_SYS_COPYAREA
1979 select FB_SYS_IMAGEBLIT
1981 select FB_DEFERRED_IO
1983 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1985 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1987 config FB_SH_MOBILE_HDMI
1988 tristate "SuperH Mobile HDMI controller support"
1989 depends on FB_SH_MOBILE_LCDC
1990 select FB_MODE_HELPERS
1995 Driver for the on-chip SH-Mobile HDMI controller.
1998 tristate "Toshiba Mobile IO FrameBuffer support"
1999 depends on FB && (MFD_TMIO || COMPILE_TEST)
2000 select FB_CFB_FILLRECT
2001 select FB_CFB_COPYAREA
2002 select FB_CFB_IMAGEBLIT
2004 Frame buffer driver for the Toshiba Mobile IO integrated as found
2005 on the Sharp SL-6000 series
2007 This driver is also available as a module ( = code which can be
2008 inserted and removed from the running kernel whenever you want). The
2009 module will be called tmiofb. If you want to compile it as a module,
2010 say M here and read <file:Documentation/kbuild/modules.txt>.
2014 config FB_TMIO_ACCELL
2015 bool "tmiofb acceleration"
2020 tristate "Samsung S3C framebuffer support"
2021 depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \
2022 ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
2023 select FB_CFB_FILLRECT
2024 select FB_CFB_COPYAREA
2025 select FB_CFB_IMAGEBLIT
2027 Frame buffer driver for the built-in FB controller in the Samsung
2028 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2029 and the S3C64XX series such as the S3C6400 and S3C6410.
2031 These chips all have the same basic framebuffer design with the
2032 actual capabilities depending on the chip. For instance the S3C6400
2033 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2034 currently only have two.
2036 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2038 config FB_S3C_DEBUG_REGWRITE
2039 bool "Debug register writes"
2042 Show all register writes via pr_debug()
2045 tristate "S3C2410 LCD framebuffer support"
2046 depends on FB && ARCH_S3C24XX
2047 select FB_CFB_FILLRECT
2048 select FB_CFB_COPYAREA
2049 select FB_CFB_IMAGEBLIT
2051 Frame buffer driver for the built-in LCD controller in the Samsung
2054 This driver is also available as a module ( = code which can be
2055 inserted and removed from the running kernel whenever you want). The
2056 module will be called s3c2410fb. If you want to compile it as a module,
2057 say M here and read <file:Documentation/kbuild/modules.txt>.
2060 config FB_S3C2410_DEBUG
2061 bool "S3C2410 lcd debug messages"
2062 depends on FB_S3C2410
2064 Turn on debugging messages. Note that you can set/unset at run time
2068 tristate "NUC900 LCD framebuffer support"
2069 depends on FB && ARCH_W90X900
2070 select FB_CFB_FILLRECT
2071 select FB_CFB_COPYAREA
2072 select FB_CFB_IMAGEBLIT
2074 Frame buffer driver for the built-in LCD controller in the Nuvoton
2077 config GPM1040A0_320X240
2078 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2079 depends on FB_NUC900
2082 tristate "Silicon Motion SM501 framebuffer support"
2083 depends on FB && MFD_SM501
2084 select FB_CFB_FILLRECT
2085 select FB_CFB_COPYAREA
2086 select FB_CFB_IMAGEBLIT
2088 Frame buffer driver for the CRT and LCD controllers in the Silicon
2091 This driver is also available as a module ( = code which can be
2092 inserted and removed from the running kernel whenever you want). The
2093 module will be called sm501fb. If you want to compile it as a module,
2094 say M here and read <file:Documentation/kbuild/modules.txt>.
2099 tristate "SMSC UFX6000/7000 USB Framebuffer support"
2100 depends on FB && USB
2101 select FB_MODE_HELPERS
2102 select FB_SYS_FILLRECT
2103 select FB_SYS_COPYAREA
2104 select FB_SYS_IMAGEBLIT
2106 select FB_DEFERRED_IO
2108 This is a kernel framebuffer driver for SMSC UFX USB devices.
2109 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2110 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
2112 To compile as a module, choose M here: the module name is smscufx.
2115 tristate "Displaylink USB Framebuffer support"
2116 depends on FB && USB
2117 select FB_MODE_HELPERS
2118 select FB_SYS_FILLRECT
2119 select FB_SYS_COPYAREA
2120 select FB_SYS_IMAGEBLIT
2122 select FB_DEFERRED_IO
2124 This is a kernel framebuffer driver for DisplayLink USB devices.
2125 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2126 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2127 To compile as a module, choose M here: the module name is udlfb.
2129 config FB_IBM_GXT4500
2130 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
2131 depends on FB && PPC
2132 select FB_CFB_FILLRECT
2133 select FB_CFB_COPYAREA
2134 select FB_CFB_IMAGEBLIT
2136 Say Y here to enable support for the IBM GXT4000P/6000P and
2137 GXT4500P/6500P display adaptor based on Raster Engine RC1000,
2138 found on some IBM System P (pSeries) machines. This driver
2139 doesn't use Geometry Engine GT1000.
2142 tristate "PS3 GPU framebuffer driver"
2143 depends on FB && PS3_PS3AV
2144 select FB_SYS_FILLRECT
2145 select FB_SYS_COPYAREA
2146 select FB_SYS_IMAGEBLIT
2148 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2150 Include support for the virtual frame buffer in the PS3 platform.
2152 config FB_PS3_DEFAULT_SIZE_M
2153 int "PS3 default frame buffer size (in MiB)"
2157 This is the default size (in MiB) of the virtual frame buffer in
2159 The default value can be overridden on the kernel command line
2160 using the "ps3fb" option (e.g. "ps3fb=9M");
2163 tristate "Xilinx frame buffer support"
2164 depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ)
2165 select FB_CFB_FILLRECT
2166 select FB_CFB_COPYAREA
2167 select FB_CFB_IMAGEBLIT
2169 Include support for the Xilinx ML300/ML403 reference design
2170 framebuffer. ML300 carries a 640*480 LCD display on the board,
2171 ML403 uses a standard DB15 VGA connector.
2174 tristate "Goldfish Framebuffer"
2175 depends on FB && HAS_DMA && (GOLDFISH || COMPILE_TEST)
2176 select FB_CFB_FILLRECT
2177 select FB_CFB_COPYAREA
2178 select FB_CFB_IMAGEBLIT
2180 Framebuffer driver for Goldfish Virtual Platform
2183 tristate "Cobalt server LCD frame buffer support"
2184 depends on FB && (MIPS_COBALT || MIPS_SEAD3)
2187 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2188 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2189 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2190 select FB_CFB_FILLRECT
2191 select FB_CFB_COPYAREA
2192 select FB_CFB_IMAGEBLIT
2194 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2195 (D)STN/TFT LCD Controller.
2196 Supports display resolutions up to 1024x1024 pixel, grayscale and
2197 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2198 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2199 panels <= 320 pixel horizontal resolution.
2202 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2203 depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX)
2204 select FB_CFB_FILLRECT
2205 select FB_CFB_COPYAREA
2206 select FB_CFB_IMAGEBLIT
2207 select FB_CFB_REV_PIXELS_IN_BYTE
2208 select FB_MODE_HELPERS
2209 select VIDEOMODE_HELPERS
2211 This is the frame buffer device driver for the TI LCD controller
2212 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2216 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2218 select FB_SYS_FILLRECT
2219 select FB_SYS_COPYAREA
2220 select FB_SYS_IMAGEBLIT
2223 This is a `virtual' frame buffer device. It operates on a chunk of
2224 unswappable kernel memory instead of on the memory of a graphics
2225 board. This means you cannot see any output sent to this frame
2226 buffer device, while it does consume precious memory. The main use
2227 of this frame buffer device is testing and debugging the frame
2228 buffer subsystem. Do NOT enable it for normal systems! To protect
2229 the innocent, it has to be enabled explicitly at boot time using the
2230 kernel option `video=vfb:'.
2232 To compile this driver as a module, choose M here: the
2233 module will be called vfb. In order to load it, you must use
2234 the vfb_enable=1 option.
2238 config XEN_FBDEV_FRONTEND
2239 tristate "Xen virtual frame buffer support"
2240 depends on FB && XEN
2241 select FB_SYS_FILLRECT
2242 select FB_SYS_COPYAREA
2243 select FB_SYS_IMAGEBLIT
2245 select FB_DEFERRED_IO
2246 select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC
2247 select XEN_XENBUS_FRONTEND
2250 This driver implements the front-end of the Xen virtual
2251 frame buffer driver. It communicates with a back-end
2255 tristate "E-Ink Metronome/8track controller support"
2257 select FB_SYS_FILLRECT
2258 select FB_SYS_COPYAREA
2259 select FB_SYS_IMAGEBLIT
2261 select FB_DEFERRED_IO
2263 This driver implements support for the E-Ink Metronome
2264 controller. The pre-release name for this device was 8track
2265 and could also have been called by some vendors as PVI-nnnn.
2268 tristate "Fujitsu MB862xx GDC support"
2270 depends on PCI || (OF && PPC)
2271 select FB_CFB_FILLRECT
2272 select FB_CFB_COPYAREA
2273 select FB_CFB_IMAGEBLIT
2275 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2278 prompt "GDC variant"
2279 depends on FB_MB862XX
2281 config FB_MB862XX_PCI_GDC
2282 bool "Carmine/Coral-P(A) GDC"
2285 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2286 PCI graphics controller devices.
2288 config FB_MB862XX_LIME
2290 depends on OF && PPC
2291 select FB_FOREIGN_ENDIAN
2292 select FB_LITTLE_ENDIAN
2294 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2298 config FB_MB862XX_I2C
2299 bool "Support I2C bus on MB862XX GDC"
2300 depends on FB_MB862XX && I2C
2301 depends on FB_MB862XX=m || I2C=y
2304 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2305 driver to support accessing I2C devices on controller's I2C bus.
2306 These are usually some video decoder chips.
2309 tristate "EP93XX frame buffer support"
2310 depends on FB && ARCH_EP93XX
2311 select FB_CFB_FILLRECT
2312 select FB_CFB_COPYAREA
2313 select FB_CFB_IMAGEBLIT
2315 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2316 This driver is also available as a module. The module will be called
2319 config FB_PRE_INIT_FB
2320 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2321 depends on FB && FB_MB862XX_LIME
2323 Select this option if display contents should be inherited as set by
2327 tristate "MSM Framebuffer support"
2328 depends on FB && ARCH_MSM
2329 select FB_CFB_FILLRECT
2330 select FB_CFB_COPYAREA
2331 select FB_CFB_IMAGEBLIT
2334 tristate "MX3 Framebuffer support"
2335 depends on FB && MX3_IPU
2336 select FB_CFB_FILLRECT
2337 select FB_CFB_COPYAREA
2338 select FB_CFB_IMAGEBLIT
2339 select BACKLIGHT_CLASS_DEVICE
2342 This is a framebuffer device for the i.MX31 LCD Controller. So
2343 far only synchronous displays are supported. If you plan to use
2344 an LCD display with your i.MX31 system, say Y here.
2346 config FB_BROADSHEET
2347 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2349 select FB_SYS_FILLRECT
2350 select FB_SYS_COPYAREA
2351 select FB_SYS_IMAGEBLIT
2353 select FB_DEFERRED_IO
2355 This driver implements support for the E-Ink Broadsheet
2356 controller. The release name for this device was Epson S1D13521
2357 and could also have been called by other names when coupled with
2361 tristate "AUO-K190X EPD controller support"
2363 select FB_SYS_FILLRECT
2364 select FB_SYS_COPYAREA
2365 select FB_SYS_IMAGEBLIT
2367 select FB_DEFERRED_IO
2369 Provides support for epaper controllers from the K190X series
2370 of AUO. These controllers can be used to drive epaper displays
2373 This option enables the common support, shared by the individual
2374 controller drivers. You will also have to enable the driver
2375 for the controller type used in your device.
2378 tristate "AUO-K1900 EPD controller support"
2379 depends on FB && FB_AUO_K190X
2381 This driver implements support for the AUO K1900 epd-controller.
2382 This controller can drive Sipix epaper displays but can only do
2383 serial updates, reducing the number of possible frames per second.
2386 tristate "AUO-K1901 EPD controller support"
2387 depends on FB && FB_AUO_K190X
2389 This driver implements support for the AUO K1901 epd-controller.
2390 This controller can drive Sipix epaper displays and supports
2391 concurrent updates, making higher frames per second possible.
2394 tristate "JZ4740 LCD framebuffer support"
2395 depends on FB && MACH_JZ4740
2396 select FB_SYS_FILLRECT
2397 select FB_SYS_COPYAREA
2398 select FB_SYS_IMAGEBLIT
2400 Framebuffer support for the JZ4740 SoC.
2403 tristate "MXS LCD framebuffer support"
2404 depends on FB && ARCH_MXS
2405 select FB_CFB_FILLRECT
2406 select FB_CFB_COPYAREA
2407 select FB_CFB_IMAGEBLIT
2408 select FB_MODE_HELPERS
2409 select VIDEOMODE_HELPERS
2411 Framebuffer support for the MXS SoC.
2413 config FB_PUV3_UNIGFX
2414 tristate "PKUnity v3 Unigfx framebuffer support"
2415 depends on FB && UNICORE32 && ARCH_PUV3
2416 select FB_SYS_FILLRECT
2417 select FB_SYS_COPYAREA
2418 select FB_SYS_IMAGEBLIT
2421 Choose this option if you want to use the Unigfx device as a
2422 framebuffer device. Without the support of PCI & AGP.
2425 tristate "Microsoft Hyper-V Synthetic Video support"
2426 depends on FB && HYPERV
2427 select FB_CFB_FILLRECT
2428 select FB_CFB_COPYAREA
2429 select FB_CFB_IMAGEBLIT
2431 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2434 bool "Simple framebuffer support"
2436 select FB_CFB_FILLRECT
2437 select FB_CFB_COPYAREA
2438 select FB_CFB_IMAGEBLIT
2440 Say Y if you want support for a simple frame-buffer.
2442 This driver assumes that the display hardware has been initialized
2443 before the kernel boots, and the kernel will simply render to the
2444 pre-allocated frame buffer surface.
2446 Configuration re: surface address, size, and format must be provided
2447 through device tree, or plain old platform data.
2449 source "drivers/video/fbdev/omap/Kconfig"
2450 source "drivers/video/fbdev/omap2/Kconfig"
2451 source "drivers/video/fbdev/exynos/Kconfig"
2452 source "drivers/video/fbdev/mmp/Kconfig"
2454 config FB_SH_MOBILE_MERAM
2455 tristate "SuperH Mobile MERAM read ahead support"
2456 depends on (SUPERH || ARCH_SHMOBILE)
2457 select GENERIC_ALLOCATOR
2459 Enable MERAM support for the SuperH controller.
2461 This will allow for caching of the framebuffer to provide more
2462 reliable access under heavy main memory bus traffic situations.
2463 Up to 4 memory channels can be configured, allowing 4 RGB or
2464 2 YCbCr framebuffers to be configured.
2467 tristate "Solomon SSD1307 framebuffer support"
2468 depends on FB && I2C
2472 select FB_SYS_FILLRECT
2473 select FB_SYS_COPYAREA
2474 select FB_SYS_IMAGEBLIT
2475 select FB_DEFERRED_IO
2478 This driver implements support for the Solomon SSD1307
2479 OLED controller over I2C.