5 menu "Graphics support"
16 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
18 config SH_LCD_MIPI_DSI
21 source "drivers/char/agp/Kconfig"
23 source "drivers/gpu/vga/Kconfig"
25 source "drivers/gpu/drm/Kconfig"
27 source "drivers/gpu/stub/Kconfig"
33 config VIDEO_OUTPUT_CONTROL
34 tristate "Lowlevel video output switch controls"
36 This framework adds support for low-level control of the video
40 tristate "Support for frame buffer devices"
42 The frame buffer device provides an abstraction for the graphics
43 hardware. It represents the frame buffer of some video hardware and
44 allows application software to access the graphics hardware through
45 a well-defined interface, so the software doesn't need to know
46 anything about the low-level (hardware register) stuff.
48 Frame buffer devices work identically across the different
49 architectures supported by Linux and make the implementation of
50 application programs easier and more portable; at this point, an X
51 server exists which uses the frame buffer device exclusively.
52 On several non-X86 architectures, the frame buffer device is the
53 only way to use the graphics hardware.
55 The device is accessed through special device nodes, usually located
56 in the /dev directory, i.e. /dev/fb*.
58 You need an utility program called fbset to make full use of frame
59 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
60 and the Framebuffer-HOWTO at
61 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
64 Say Y here and to the driver for your graphics board below if you
65 are compiling a kernel for a non-x86 architecture.
67 If you are compiling for the x86 architecture, you can say Y if you
68 want to play with it, but it is not essential. Please note that
69 running graphical applications that directly touch the hardware
70 (e.g. an accelerated X server) and that are not frame buffer
71 device-aware may cause unexpected results. If unsure, say N.
74 bool "Enable firmware EDID"
78 This enables access to the EDID transferred from the firmware.
79 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
80 transfers do not work for your driver and if you are using
81 nvidiafb, i810fb or savagefb.
83 In general, choosing Y for this option is safe. If you
84 experience extremely long delays while booting before you get
85 something on your display, try setting this to N. Matrox cards in
86 combination with certain motherboards and monitors are known to
87 suffer from this problem.
96 config FB_BOOT_VESA_SUPPORT
101 If true, at least one selected framebuffer driver can take advantage
102 of VESA video modes set at an early boot stage via the vga= parameter.
104 config FB_CFB_FILLRECT
109 Include the cfb_fillrect function for generic software rectangle
110 filling. This is used by drivers that don't provide their own
111 (accelerated) version.
113 config FB_CFB_COPYAREA
118 Include the cfb_copyarea function for generic software area copying.
119 This is used by drivers that don't provide their own (accelerated)
122 config FB_CFB_IMAGEBLIT
127 Include the cfb_imageblit function for generic software image
128 blitting. This is used by drivers that don't provide their own
129 (accelerated) version.
131 config FB_CFB_REV_PIXELS_IN_BYTE
136 Allow generic frame-buffer functions to work on displays with 1, 2
137 and 4 bits per pixel depths which has opposite order of pixels in
138 byte order to bytes in long order.
140 config FB_SYS_FILLRECT
145 Include the sys_fillrect function for generic software rectangle
146 filling. This is used by drivers that don't provide their own
147 (accelerated) version and the framebuffer is in system RAM.
149 config FB_SYS_COPYAREA
154 Include the sys_copyarea function for generic software area copying.
155 This is used by drivers that don't provide their own (accelerated)
156 version and the framebuffer is in system RAM.
158 config FB_SYS_IMAGEBLIT
163 Include the sys_imageblit function for generic software image
164 blitting. This is used by drivers that don't provide their own
165 (accelerated) version and the framebuffer is in system RAM.
167 menuconfig FB_FOREIGN_ENDIAN
168 bool "Framebuffer foreign endianness support"
171 This menu will let you enable support for the framebuffers with
172 non-native endianness (e.g. Little-Endian framebuffer on a
173 Big-Endian machine). Most probably you don't have such hardware,
174 so it's safe to say "n" here.
177 prompt "Choice endianness support"
178 depends on FB_FOREIGN_ENDIAN
180 config FB_BOTH_ENDIAN
181 bool "Support for Big- and Little-Endian framebuffers"
184 bool "Support for Big-Endian framebuffers only"
186 config FB_LITTLE_ENDIAN
187 bool "Support for Little-Endian framebuffers only"
196 config FB_WMT_GE_ROPS
201 Include functions for accelerated rectangle filling and area
202 copying using WonderMedia Graphics Engine operations.
204 config FB_DEFERRED_IO
211 depends on FB_DEFERRED_IO
218 Common utility functions useful to fbdev drivers of VGA-based
229 select BACKLIGHT_LCD_SUPPORT
230 select BACKLIGHT_CLASS_DEVICE
233 config FB_MODE_HELPERS
234 bool "Enable Video Mode Handling Helpers"
238 This enables functions for handling video modes using the
239 Generalized Timing Formula and the EDID parser. A few drivers rely
240 on this feature such as the radeonfb, rivafb, and the i810fb. If
241 your driver does not take advantage of this feature, choosing Y will
242 just increase the kernel size by about 5K.
244 config FB_TILEBLITTING
245 bool "Enable Tile Blitting Support"
249 This enables tile blitting. Tile blitting is a drawing technique
250 where the screen is divided into rectangular sections (tiles), whereas
251 the standard blitting divides the screen into pixels. Because the
252 default drawing element is a tile, drawing functions will be passed
253 parameters in terms of number of tiles instead of number of pixels.
254 For example, to draw a single character, instead of using bitmaps,
255 an index to an array of bitmaps will be used. To clear or move a
256 rectangular section of a screen, the rectangle will be described in
257 terms of number of tiles in the x- and y-axis.
259 This is particularly important to one driver, matroxfb. If
262 comment "Frame buffer hardware drivers"
266 tristate "Cirrus Logic support"
267 depends on FB && (ZORRO || PCI)
268 select FB_CFB_FILLRECT
269 select FB_CFB_COPYAREA
270 select FB_CFB_IMAGEBLIT
272 This enables support for Cirrus Logic GD542x/543x based boards on
273 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
275 If you have a PCI-based system, this enables support for these
276 chips: GD-543x, GD-544x, GD-5480.
278 Please read the file <file:Documentation/fb/cirrusfb.txt>.
280 Say N unless you have such a graphics board or plan to get one
281 before you next recompile the kernel.
284 tristate "Permedia2 support"
285 depends on FB && ((AMIGA && BROKEN) || PCI)
286 select FB_CFB_FILLRECT
287 select FB_CFB_COPYAREA
288 select FB_CFB_IMAGEBLIT
290 This is the frame buffer device driver for cards based on
291 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
292 The driver was tested on the following cards:
293 Diamond FireGL 1000 PRO AGP
294 ELSA Gloria Synergy PCI
295 Appian Jeronimo PRO (both heads) PCI
296 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
297 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
298 ASK Graphic Blaster Exxtreme AGP
300 To compile this driver as a module, choose M here: the
301 module will be called pm2fb.
303 config FB_PM2_FIFO_DISCONNECT
304 bool "enable FIFO disconnect feature"
305 depends on FB_PM2 && PCI
307 Support the Permedia2 FIFO disconnect feature.
310 tristate "ARM PrimeCell PL110 support"
311 depends on FB && ARM && ARM_AMBA
312 select FB_CFB_FILLRECT
313 select FB_CFB_COPYAREA
314 select FB_CFB_IMAGEBLIT
316 This framebuffer device driver is for the ARM PrimeCell PL110
317 Colour LCD controller. ARM PrimeCells provide the building
318 blocks for System on a Chip devices.
320 If you want to compile this as a module (=code which can be
321 inserted into and removed from the running kernel), say M
322 here and read <file:Documentation/kbuild/modules.txt>. The module
323 will be called amba-clcd.
326 bool "Acorn VIDC support"
327 depends on (FB = y) && ARM && ARCH_ACORN
328 select FB_CFB_FILLRECT
329 select FB_CFB_COPYAREA
330 select FB_CFB_IMAGEBLIT
332 This is the frame buffer device driver for the Acorn VIDC graphics
333 hardware found in Acorn RISC PCs and other ARM-based machines. If
337 bool "CLPS711X LCD support"
338 depends on (FB = y) && ARM && ARCH_CLPS711X
339 select FB_CFB_FILLRECT
340 select FB_CFB_COPYAREA
341 select FB_CFB_IMAGEBLIT
343 Say Y to enable the Framebuffer driver for the CLPS7111 and
347 bool "SA-1100 LCD support"
348 depends on (FB = y) && ARM && ARCH_SA1100
349 select FB_CFB_FILLRECT
350 select FB_CFB_COPYAREA
351 select FB_CFB_IMAGEBLIT
353 This is a framebuffer device for the SA-1100 LCD Controller.
354 See <http://www.linux-fbdev.org/> for information on framebuffer
357 If you plan to use the LCD display with your SA-1100 system, say
361 tristate "Freescale i.MX LCD support"
362 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
363 select FB_CFB_FILLRECT
364 select FB_CFB_COPYAREA
365 select FB_CFB_IMAGEBLIT
368 tristate "CyberPro 2000/2010/5000 support"
369 depends on FB && PCI && (BROKEN || !SPARC64)
370 select FB_CFB_FILLRECT
371 select FB_CFB_COPYAREA
372 select FB_CFB_IMAGEBLIT
374 This enables support for the Integraphics CyberPro 20x0 and 5000
375 VGA chips used in the Rebel.com Netwinder and other machines.
376 Say Y if you have a NetWinder or a graphics card containing this
377 device, otherwise say N.
381 depends on (FB = y) && APOLLO
383 select FB_CFB_FILLRECT
384 select FB_CFB_IMAGEBLIT
388 depends on (FB = y) && Q40
390 select FB_CFB_FILLRECT
391 select FB_CFB_COPYAREA
392 select FB_CFB_IMAGEBLIT
395 tristate "Amiga native chipset support"
396 depends on FB && AMIGA
398 This is the frame buffer device driver for the builtin graphics
399 chipset found in Amigas.
401 To compile this driver as a module, choose M here: the
402 module will be called amifb.
405 bool "Amiga OCS chipset support"
408 This enables support for the original Agnus and Denise video chips,
409 found in the Amiga 1000 and most A500's and A2000's. If you intend
410 to run Linux on any of these systems, say Y; otherwise say N.
413 bool "Amiga ECS chipset support"
416 This enables support for the Enhanced Chip Set, found in later
417 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
418 you intend to run Linux on any of these systems, say Y; otherwise
422 bool "Amiga AGA chipset support"
425 This enables support for the Advanced Graphics Architecture (also
426 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
427 and CD32. If you intend to run Linux on any of these systems, say Y;
431 bool "Amiga FrameMaster II/Rainbow II support"
432 depends on (FB = y) && ZORRO
433 select FB_CFB_FILLRECT
434 select FB_CFB_COPYAREA
435 select FB_CFB_IMAGEBLIT
437 This is the frame buffer device driver for the Amiga FrameMaster
438 card from BSC (exhibited 1992 but not shipped as a CBM product).
441 tristate "Arc Monochrome LCD board support"
443 select FB_SYS_FILLRECT
444 select FB_SYS_COPYAREA
445 select FB_SYS_IMAGEBLIT
448 This enables support for the Arc Monochrome LCD board. The board
449 is based on the KS-108 lcd controller and is typically a matrix
450 of 2*n chips. This driver was tested with a 128x64 panel. This
451 driver supports it for use with x86 SBCs through a 16 bit GPIO
452 interface (8 bit data, 8 bit control). If you anticipate using
453 this driver, say Y or M; otherwise say N. You must specify the
454 GPIO IO address to be used for setting control and data.
457 bool "Atari native chipset support"
458 depends on (FB = y) && ATARI
459 select FB_CFB_FILLRECT
460 select FB_CFB_COPYAREA
461 select FB_CFB_IMAGEBLIT
463 This is the frame buffer device driver for the builtin graphics
464 chipset found in Ataris.
467 bool "Open Firmware frame buffer device support"
468 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
469 select FB_CFB_FILLRECT
470 select FB_CFB_COPYAREA
471 select FB_CFB_IMAGEBLIT
474 Say Y if you want support with Open Firmware for your graphics
478 bool "Apple \"control\" display support"
479 depends on (FB = y) && PPC_PMAC && PPC32
480 select FB_CFB_FILLRECT
481 select FB_CFB_COPYAREA
482 select FB_CFB_IMAGEBLIT
485 This driver supports a frame buffer for the graphics adapter in the
486 Power Macintosh 7300 and others.
489 bool "Apple \"platinum\" display support"
490 depends on (FB = y) && PPC_PMAC && PPC32
491 select FB_CFB_FILLRECT
492 select FB_CFB_COPYAREA
493 select FB_CFB_IMAGEBLIT
496 This driver supports a frame buffer for the "platinum" graphics
497 adapter in some Power Macintoshes.
500 bool "Apple \"valkyrie\" display support"
501 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
502 select FB_CFB_FILLRECT
503 select FB_CFB_COPYAREA
504 select FB_CFB_IMAGEBLIT
507 This driver supports a frame buffer for the "valkyrie" graphics
508 adapter in some Power Macintoshes.
511 bool "Chips 65550 display support"
512 depends on (FB = y) && PPC32 && PCI
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
517 This is the frame buffer device driver for the Chips & Technologies
518 65550 graphics chip in PowerBooks.
521 bool "Asiliant (Chips) 69000 display support"
522 depends on (FB = y) && PCI
523 select FB_CFB_FILLRECT
524 select FB_CFB_COPYAREA
525 select FB_CFB_IMAGEBLIT
527 This is the frame buffer device driver for the Asiliant 69030 chipset
530 bool "IMS Twin Turbo display support"
531 depends on (FB = y) && PCI
532 select FB_CFB_IMAGEBLIT
533 select FB_MACMODES if PPC
535 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
536 many Macintosh and compatible computers.
539 tristate "VGA 16-color graphics support"
540 depends on FB && (X86 || PPC)
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
545 select FONT_8x16 if FRAMEBUFFER_CONSOLE
547 This is the frame buffer device driver for VGA 16 color graphic
548 cards. Say Y if you have such a card.
550 To compile this driver as a module, choose M here: the
551 module will be called vga16fb.
553 config FB_BF54X_LQ043
554 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
555 depends on FB && (BF54x) && !BF542
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
562 config FB_BFIN_T350MCQB
563 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
564 depends on FB && BLACKFIN
566 select FB_CFB_FILLRECT
567 select FB_CFB_COPYAREA
568 select FB_CFB_IMAGEBLIT
570 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
571 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
572 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
574 config FB_BFIN_LQ035Q1
575 tristate "SHARP LQ035Q1DH02 TFT LCD"
576 depends on FB && BLACKFIN && SPI
577 select FB_CFB_FILLRECT
578 select FB_CFB_COPYAREA
579 select FB_CFB_IMAGEBLIT
582 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
583 the Blackfin Landscape LCD EZ-Extender Card.
584 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
585 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
587 To compile this driver as a module, choose M here: the
588 module will be called bfin-lq035q1-fb.
590 config FB_BF537_LQ035
591 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
592 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
593 select FB_CFB_FILLRECT
594 select FB_CFB_COPYAREA
595 select FB_CFB_IMAGEBLIT
598 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
601 To compile this driver as a module, choose M here: the
602 module will be called bf537-lq035.
605 tristate "Blackfin ADV7393 Video encoder"
606 depends on FB && BLACKFIN
608 select FB_CFB_FILLRECT
609 select FB_CFB_COPYAREA
610 select FB_CFB_IMAGEBLIT
612 This is the framebuffer device for a ADV7393 video encoder
613 attached to a Blackfin on the PPI port.
614 If your Blackfin board has a ADV7393 select Y.
616 To compile this driver as a module, choose M here: the
617 module will be called bfin_adv7393fb.
620 prompt "Video mode support"
621 depends on FB_BFIN_7393
631 bool 'NTSC 640x480 (Experimental)'
634 bool 'PAL 640x480 (Experimental)'
637 bool 'NTSC 720x480 YCbCR input'
640 bool 'PAL 720x576 YCbCR input'
645 prompt "Size of ADV7393 frame buffer memory Single/Double Size"
646 depends on (FB_BFIN_7393)
647 default ADV7393_1XMEM
657 tristate "HP STI frame buffer device support"
658 depends on FB && PARISC
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
666 STI refers to the HP "Standard Text Interface" which is a set of
667 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
668 Enabling this option will implement the linux framebuffer device
669 using calls to the STI BIOS routines for initialisation.
671 If you enable this option, you will get a planar framebuffer device
672 /dev/fb which will work on the most common HP graphic cards of the
673 NGLE family, including the artist chips (in the 7xx and Bxxx series),
674 HCRX, HCRX24, CRX, CRX24 and VisEG series.
676 It is safe to enable this option, so you should probably say "Y".
679 bool "Generic Macintosh display support"
680 depends on (FB = y) && MAC
681 select FB_CFB_FILLRECT
682 select FB_CFB_COPYAREA
683 select FB_CFB_IMAGEBLIT
688 depends on (FB = y) && DIO
689 select FB_CFB_IMAGEBLIT
693 tristate "TGA/SFB+ framebuffer support"
694 depends on FB && (ALPHA || TC)
695 select FB_CFB_FILLRECT
696 select FB_CFB_COPYAREA
697 select FB_CFB_IMAGEBLIT
700 This is the frame buffer device driver for generic TGA and SFB+
701 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
702 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
703 TURBOchannel cards, also known as PMAGD-A, -B and -C.
705 Due to hardware limitations ZLX-E2 and E3 cards are not supported
706 for DECstation 5000/200 systems. Additionally due to firmware
707 limitations these cards may cause troubles with booting DECstation
708 5000/240 and /260 systems, but are fully supported under Linux if
709 you manage to get it going. ;-)
711 Say Y if you have one of those.
714 tristate "Userspace VESA VGA graphics support"
715 depends on FB && CONNECTOR
716 select FB_CFB_FILLRECT
717 select FB_CFB_COPYAREA
718 select FB_CFB_IMAGEBLIT
719 select FB_MODE_HELPERS
721 This is the frame buffer driver for generic VBE 2.0 compliant
722 graphic cards. It can also take advantage of VBE 3.0 features,
723 such as refresh rate adjustment.
725 This driver generally provides more features than vesafb but
726 requires a userspace helper application called 'v86d'. See
727 <file:Documentation/fb/uvesafb.txt> for more information.
732 bool "VESA VGA graphics support"
733 depends on (FB = y) && X86
734 select FB_CFB_FILLRECT
735 select FB_CFB_COPYAREA
736 select FB_CFB_IMAGEBLIT
737 select FB_BOOT_VESA_SUPPORT
739 This is the frame buffer device driver for generic VESA 2.0
740 compliant graphic cards. The older VESA 1.2 cards are not supported.
741 You will get a boot time penguin logo at no additional cost. Please
742 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
745 bool "EFI-based Framebuffer Support"
746 depends on (FB = y) && X86 && EFI
747 select FB_CFB_FILLRECT
748 select FB_CFB_COPYAREA
749 select FB_CFB_IMAGEBLIT
751 This is the EFI frame buffer device driver. If the firmware on
752 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
753 using the EFI framebuffer as your console.
756 tristate "N411 Apollo/Hecuba devkit support"
757 depends on FB && X86 && MMU
758 select FB_SYS_FILLRECT
759 select FB_SYS_COPYAREA
760 select FB_SYS_IMAGEBLIT
762 select FB_DEFERRED_IO
765 This enables support for the Apollo display controller in its
766 Hecuba form using the n411 devkit.
769 tristate "Hercules mono graphics support"
772 Say Y here if you have a Hercules mono graphics card.
774 To compile this driver as a module, choose M here: the
775 module will be called hgafb.
777 As this card technology is at least 25 years old,
778 most people will answer N here.
781 tristate "SGI Visual Workstation framebuffer support"
782 depends on FB && X86_VISWS
783 select FB_CFB_FILLRECT
784 select FB_CFB_COPYAREA
785 select FB_CFB_IMAGEBLIT
787 SGI Visual Workstation support for framebuffer graphics.
790 bool "SGI Graphics Backend frame buffer support"
791 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
792 select FB_CFB_FILLRECT
793 select FB_CFB_COPYAREA
794 select FB_CFB_IMAGEBLIT
796 This is the frame buffer device driver for SGI Graphics Backend.
797 This chip is used in SGI O2 and Visual Workstation 320/540.
800 int "Video memory size in MB"
804 This is the amount of memory reserved for the framebuffer,
805 which can be any value between 1MB and 8MB.
808 bool "SBUS and UPA framebuffers"
809 depends on (FB = y) && SPARC
811 Say Y if you want support for SBUS or UPA based frame buffer device.
815 depends on (FB = y) && (SPARC && FB_SBUS)
816 select FB_CFB_FILLRECT
817 select FB_CFB_COPYAREA
818 select FB_CFB_IMAGEBLIT
820 This is the frame buffer device driver for the BWtwo frame buffer.
823 bool "CGthree support"
824 depends on (FB = y) && (SPARC && FB_SBUS)
825 select FB_CFB_FILLRECT
826 select FB_CFB_COPYAREA
827 select FB_CFB_IMAGEBLIT
829 This is the frame buffer device driver for the CGthree frame buffer.
832 bool "CGsix (GX,TurboGX) support"
833 depends on (FB = y) && (SPARC && FB_SBUS)
834 select FB_CFB_COPYAREA
835 select FB_CFB_IMAGEBLIT
837 This is the frame buffer device driver for the CGsix (GX, TurboGX)
841 bool "Creator/Creator3D/Elite3D support"
842 depends on FB_SBUS && SPARC64
843 select FB_CFB_COPYAREA
844 select FB_CFB_IMAGEBLIT
846 This is the frame buffer device driver for the Creator, Creator3D,
847 and Elite3D graphics boards.
850 bool "TCX (SS4/SS5 only) support"
852 select FB_CFB_FILLRECT
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
856 This is the frame buffer device driver for the TCX 24/8bit frame
860 bool "CGfourteen (SX) support"
862 select FB_CFB_FILLRECT
863 select FB_CFB_COPYAREA
864 select FB_CFB_IMAGEBLIT
866 This is the frame buffer device driver for the CGfourteen frame
867 buffer on Desktop SPARCsystems with the SX graphics option.
870 bool "P9100 (Sparcbook 3 only) support"
872 select FB_CFB_FILLRECT
873 select FB_CFB_COPYAREA
874 select FB_CFB_IMAGEBLIT
876 This is the frame buffer device driver for the P9100 card
877 supported on Sparcbook 3 machines.
880 bool "Leo (ZX) support"
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This is the frame buffer device driver for the SBUS-based Sun ZX
887 (leo) frame buffer cards.
890 bool "IGA 168x display support"
891 depends on (FB = y) && SPARC32
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
896 This is the framebuffer device for the INTERGRAPHICS 1680 and
897 successor frame buffer cards.
900 bool "Sun XVR-500 3DLABS Wildcat support"
901 depends on (FB = y) && PCI && SPARC64
902 select FB_CFB_FILLRECT
903 select FB_CFB_COPYAREA
904 select FB_CFB_IMAGEBLIT
906 This is the framebuffer device for the Sun XVR-500 and similar
907 graphics cards based upon the 3DLABS Wildcat chipset. The driver
908 only works on sparc64 systems where the system firmware has
909 mostly initialized the card already. It is treated as a
910 completely dumb framebuffer device.
913 bool "Sun XVR-2500 3DLABS Wildcat support"
914 depends on (FB = y) && PCI && SPARC64
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
919 This is the framebuffer device for the Sun XVR-2500 and similar
920 graphics cards based upon the 3DLABS Wildcat chipset. The driver
921 only works on sparc64 systems where the system firmware has
922 mostly initialized the card already. It is treated as a
923 completely dumb framebuffer device.
926 bool "Sun XVR-1000 support"
927 depends on (FB = y) && SPARC64
928 select FB_CFB_FILLRECT
929 select FB_CFB_COPYAREA
930 select FB_CFB_IMAGEBLIT
932 This is the framebuffer device for the Sun XVR-1000 and similar
933 graphics cards. The driver only works on sparc64 systems where
934 the system firmware has mostly initialized the card already. It
935 is treated as a completely dumb framebuffer device.
938 tristate "NEC PowerVR 2 display support"
939 depends on FB && SH_DREAMCAST
940 select FB_CFB_FILLRECT
941 select FB_CFB_COPYAREA
942 select FB_CFB_IMAGEBLIT
944 Say Y here if you have a PowerVR 2 card in your box. If you plan to
945 run linux on your Dreamcast, you will have to say Y here.
946 This driver may or may not work on other PowerVR 2 cards, but is
947 totally untested. Use at your own risk. If unsure, say N.
949 To compile this driver as a module, choose M here: the
950 module will be called pvr2fb.
952 You can pass several parameters to the driver at boot time or at
953 module load time. The parameters look like "video=pvr2:XXX", where
954 the meaning of XXX can be found at the end of the main source file
955 (<file:drivers/video/pvr2fb.c>). Please see the file
956 <file:Documentation/fb/pvr2fb.txt>.
959 bool "Epson 1355 framebuffer support"
960 depends on (FB = y) && ARCH_CEIVA
961 select FB_CFB_FILLRECT
962 select FB_CFB_COPYAREA
963 select FB_CFB_IMAGEBLIT
965 Build in support for the SED1355 Epson Research Embedded RAMDAC
966 LCD/CRT Controller (since redesignated as the S1D13505) as a
967 framebuffer. Product specs at
968 <http://vdc.epson.com/>.
971 tristate "Epson S1D13XXX framebuffer support"
973 select FB_CFB_FILLRECT
974 select FB_CFB_COPYAREA
975 select FB_CFB_IMAGEBLIT
977 Support for S1D13XXX framebuffer device family (currently only
978 working with S1D13806). Product specs at
979 <http://vdc.epson.com/>
982 tristate "AT91/AT32 LCD Controller support"
983 depends on FB && HAVE_FB_ATMEL
984 select FB_CFB_FILLRECT
985 select FB_CFB_COPYAREA
986 select FB_CFB_IMAGEBLIT
988 This enables support for the AT91/AT32 LCD Controller.
991 bool "Frame Buffer in internal SRAM"
992 depends on FB_ATMEL && ARCH_AT91SAM9261
994 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
995 to let frame buffer in external SDRAM.
998 bool "Use a STN display with AT91/AT32 LCD Controller"
999 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1002 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1003 Controller. Say N if you want to connect a TFT.
1008 tristate "nVidia Framebuffer Support"
1009 depends on FB && PCI
1010 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1011 select FB_MODE_HELPERS
1012 select FB_CFB_FILLRECT
1013 select FB_CFB_COPYAREA
1014 select FB_CFB_IMAGEBLIT
1018 This driver supports graphics boards with the nVidia chips, TNT
1019 and newer. For very old chipsets, such as the RIVA128, then use
1021 Say Y if you have such a graphics board.
1023 To compile this driver as a module, choose M here: the
1024 module will be called nvidiafb.
1026 config FB_NVIDIA_I2C
1027 bool "Enable DDC Support"
1028 depends on FB_NVIDIA
1031 This enables I2C support for nVidia Chipsets. This is used
1032 only for getting EDID information from the attached display
1033 allowing for robust video mode handling and switching.
1035 Because fbdev-2.6 requires that drivers must be able to
1036 independently validate video mode parameters, you should say Y
1039 config FB_NVIDIA_DEBUG
1040 bool "Lots of debug output"
1041 depends on FB_NVIDIA
1044 Say Y here if you want the nVidia driver to output all sorts
1045 of debugging information to provide to the maintainer when
1046 something goes wrong.
1048 config FB_NVIDIA_BACKLIGHT
1049 bool "Support for backlight control"
1050 depends on FB_NVIDIA
1053 Say Y here if you want to control the backlight of your display.
1056 tristate "nVidia Riva support"
1057 depends on FB && PCI
1058 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1059 select FB_MODE_HELPERS
1060 select FB_CFB_FILLRECT
1061 select FB_CFB_COPYAREA
1062 select FB_CFB_IMAGEBLIT
1066 This driver supports graphics boards with the nVidia Riva/Geforce
1068 Say Y if you have such a graphics board.
1070 To compile this driver as a module, choose M here: the
1071 module will be called rivafb.
1074 bool "Enable DDC Support"
1078 This enables I2C support for nVidia Chipsets. This is used
1079 only for getting EDID information from the attached display
1080 allowing for robust video mode handling and switching.
1082 Because fbdev-2.6 requires that drivers must be able to
1083 independently validate video mode parameters, you should say Y
1086 config FB_RIVA_DEBUG
1087 bool "Lots of debug output"
1091 Say Y here if you want the Riva driver to output all sorts
1092 of debugging information to provide to the maintainer when
1093 something goes wrong.
1095 config FB_RIVA_BACKLIGHT
1096 bool "Support for backlight control"
1100 Say Y here if you want to control the backlight of your display.
1103 tristate "Intel 810/815 support (EXPERIMENTAL)"
1104 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1105 select FB_MODE_HELPERS
1106 select FB_CFB_FILLRECT
1107 select FB_CFB_COPYAREA
1108 select FB_CFB_IMAGEBLIT
1111 This driver supports the on-board graphics built in to the Intel 810
1112 and 815 chipsets. Say Y if you have and plan to use such a board.
1114 To compile this driver as a module, choose M here: the
1115 module will be called i810fb.
1117 For more information, please read
1118 <file:Documentation/fb/intel810.txt>
1121 bool "use VESA Generalized Timing Formula"
1124 If you say Y, then the VESA standard, Generalized Timing Formula
1125 or GTF, will be used to calculate the required video timing values
1126 per video mode. Since the GTF allows nondiscrete timings
1127 (nondiscrete being a range of values as opposed to discrete being a
1128 set of values), you'll be able to use any combination of horizontal
1129 and vertical resolutions, and vertical refresh rates without having
1130 to specify your own timing parameters. This is especially useful
1131 to maximize the performance of an aging display, or if you just
1132 have a display with nonstandard dimensions. A VESA compliant
1133 monitor is recommended, but can still work with non-compliant ones.
1134 If you need or want this, then select this option. The timings may
1135 not be compliant with Intel's recommended values. Use at your own
1138 If you say N, the driver will revert to discrete video timings
1139 using a set recommended by Intel in their documentation.
1144 bool "Enable DDC Support"
1145 depends on FB_I810 && FB_I810_GTF
1150 tristate "Intel LE80578 (Vermilion) support"
1151 depends on FB && PCI && X86
1152 select FB_MODE_HELPERS
1153 select FB_CFB_FILLRECT
1154 select FB_CFB_COPYAREA
1155 select FB_CFB_IMAGEBLIT
1157 This driver supports the LE80578 (Vermilion Range) chipset
1159 config FB_CARILLO_RANCH
1160 tristate "Intel Carillo Ranch support"
1161 depends on FB_LE80578 && FB && PCI && X86
1163 This driver supports the LE80578 (Carillo Ranch) board
1166 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1167 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EXPERT
1168 select FB_MODE_HELPERS
1169 select FB_CFB_FILLRECT
1170 select FB_CFB_COPYAREA
1171 select FB_CFB_IMAGEBLIT
1172 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1173 depends on !DRM_I915
1175 This driver supports the on-board graphics built in to the Intel
1176 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1177 Say Y if you have and plan to use such a board.
1179 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1181 To compile this driver as a module, choose M here: the
1182 module will be called intelfb.
1184 For more information, please read <file:Documentation/fb/intelfb.txt>
1186 config FB_INTEL_DEBUG
1187 bool "Intel driver Debug Messages"
1190 Say Y here if you want the Intel driver to output all sorts
1191 of debugging information to provide to the maintainer when
1192 something goes wrong.
1195 bool "DDC/I2C for Intel framebuffer support"
1200 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1203 tristate "Matrox acceleration"
1204 depends on FB && PCI
1205 select FB_CFB_FILLRECT
1206 select FB_CFB_COPYAREA
1207 select FB_CFB_IMAGEBLIT
1208 select FB_TILEBLITTING
1209 select FB_MACMODES if PPC_PMAC
1211 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1212 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1213 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1214 Matrox G400, G450 or G550 card in your box.
1216 To compile this driver as a module, choose M here: the
1217 module will be called matroxfb.
1219 You can pass several parameters to the driver at boot time or at
1220 module load time. The parameters look like "video=matroxfb:XXX", and
1221 are described in <file:Documentation/fb/matroxfb.txt>.
1223 config FB_MATROX_MILLENIUM
1224 bool "Millennium I/II support"
1225 depends on FB_MATROX
1227 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1228 video card. If you select "Advanced lowlevel driver options" below,
1229 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1230 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1231 also use font widths different from 8.
1233 config FB_MATROX_MYSTIQUE
1234 bool "Mystique support"
1235 depends on FB_MATROX
1237 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1238 video card. If you select "Advanced lowlevel driver options" below,
1239 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1240 packed pixel and 32 bpp packed pixel. You can also use font widths
1244 bool "G100/G200/G400/G450/G550 support"
1245 depends on FB_MATROX
1247 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1248 video card. If you select "Advanced lowlevel driver options", you
1249 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1250 pixel and 32 bpp packed pixel. You can also use font widths
1253 If you need support for G400 secondary head, you must say Y to
1254 "Matrox I2C support" and "G400 second head support" right below.
1255 G450/G550 secondary head and digital output are supported without
1258 The driver starts in monitor mode. You must use the matroxset tool
1259 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1260 swap primary and secondary head outputs, or to change output mode.
1261 Secondary head driver always start in 640x480 resolution and you
1262 must use fbset to change it.
1264 Do not forget that second head supports only 16 and 32 bpp
1265 packed pixels, so it is a good idea to compile them into the kernel
1266 too. You can use only some font widths, as the driver uses generic
1267 painting procedures (the secondary head does not use acceleration
1270 G450/G550 hardware can display TV picture only from secondary CRTC,
1271 and it performs no scaling, so picture must have 525 or 625 lines.
1273 config FB_MATROX_I2C
1274 tristate "Matrox I2C support"
1275 depends on FB_MATROX
1278 This drivers creates I2C buses which are needed for accessing the
1279 DDC (I2C) bus present on all Matroxes, an I2C bus which
1280 interconnects Matrox optional devices, like MGA-TVO on G200 and
1281 G400, and the secondary head DDC bus, present on G400 only.
1283 You can say Y or M here if you want to experiment with monitor
1284 detection code. You must say Y or M here if you want to use either
1285 second head of G400 or MGA-TVO on G200 or G400.
1287 If you compile it as module, it will create a module named
1290 config FB_MATROX_MAVEN
1291 tristate "G400 second head support"
1292 depends on FB_MATROX_G && FB_MATROX_I2C
1294 WARNING !!! This support does not work with G450 !!!
1296 Say Y or M here if you want to use a secondary head (meaning two
1297 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1298 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1299 secondary head output is blanked while you are in X. With XFree
1300 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1301 the fbdev driver on first head and the fbdev driver on second head.
1303 If you compile it as module, two modules are created,
1304 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1305 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1306 also load i2c-matroxfb to get it to run.
1308 The driver starts in monitor mode and you must use the matroxset
1310 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1311 PAL or NTSC or to swap primary and secondary head outputs.
1312 Secondary head driver also always start in 640x480 resolution, you
1313 must use fbset to change it.
1315 Also do not forget that second head supports only 16 and 32 bpp
1316 packed pixels, so it is a good idea to compile them into the kernel
1317 too. You can use only some font widths, as the driver uses generic
1318 painting procedures (the secondary head does not use acceleration
1322 tristate "ATI Radeon display support"
1323 depends on FB && PCI
1324 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1325 select FB_MODE_HELPERS
1326 select FB_CFB_FILLRECT
1327 select FB_CFB_COPYAREA
1328 select FB_CFB_IMAGEBLIT
1329 select FB_MACMODES if PPC_OF
1331 Choose this option if you want to use an ATI Radeon graphics card as
1332 a framebuffer device. There are both PCI and AGP versions. You
1333 don't need to choose this to run the Radeon in plain VGA mode.
1335 There is a product page at
1336 http://products.amd.com/en-us/GraphicCardResult.aspx
1338 config FB_RADEON_I2C
1339 bool "DDC/I2C for ATI Radeon support"
1340 depends on FB_RADEON
1344 Say Y here if you want DDC/I2C support for your Radeon board.
1346 config FB_RADEON_BACKLIGHT
1347 bool "Support for backlight control"
1348 depends on FB_RADEON
1351 Say Y here if you want to control the backlight of your display.
1353 config FB_RADEON_DEBUG
1354 bool "Lots of debug output from Radeon driver"
1355 depends on FB_RADEON
1358 Say Y here if you want the Radeon driver to output all sorts
1359 of debugging information to provide to the maintainer when
1360 something goes wrong.
1363 tristate "ATI Rage128 display support"
1364 depends on FB && PCI
1365 select FB_CFB_FILLRECT
1366 select FB_CFB_COPYAREA
1367 select FB_CFB_IMAGEBLIT
1368 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1369 select FB_MACMODES if PPC_PMAC
1371 This driver supports graphics boards with the ATI Rage128 chips.
1372 Say Y if you have such a graphics board and read
1373 <file:Documentation/fb/aty128fb.txt>.
1375 To compile this driver as a module, choose M here: the
1376 module will be called aty128fb.
1378 config FB_ATY128_BACKLIGHT
1379 bool "Support for backlight control"
1380 depends on FB_ATY128
1383 Say Y here if you want to control the backlight of your display.
1386 tristate "ATI Mach64 display support" if PCI || ATARI
1387 depends on FB && !SPARC32
1388 select FB_CFB_FILLRECT
1389 select FB_CFB_COPYAREA
1390 select FB_CFB_IMAGEBLIT
1391 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1392 select FB_MACMODES if PPC
1394 This driver supports graphics boards with the ATI Mach64 chips.
1395 Say Y if you have such a graphics board.
1397 To compile this driver as a module, choose M here: the
1398 module will be called atyfb.
1401 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1402 depends on PCI && FB_ATY
1403 default y if SPARC64 && PCI
1405 Say Y here to support use of ATI's 64-bit Rage boards (or other
1406 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1407 framebuffer device. The ATI product support page for these boards
1408 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1410 config FB_ATY_GENERIC_LCD
1411 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1412 depends on FB_ATY_CT
1414 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1415 Rage XC, or Rage XL chipset.
1418 bool "Mach64 GX support" if PCI
1422 Say Y here to support use of the ATI Mach64 Graphics Expression
1423 board (or other boards based on the Mach64 GX chipset) as a
1424 framebuffer device. The ATI product support page for these boards
1426 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1428 config FB_ATY_BACKLIGHT
1429 bool "Support for backlight control"
1433 Say Y here if you want to control the backlight of your display.
1436 tristate "S3 Trio/Virge support"
1437 depends on FB && PCI
1438 select FB_CFB_FILLRECT
1439 select FB_CFB_COPYAREA
1440 select FB_CFB_IMAGEBLIT
1441 select FB_TILEBLITTING
1444 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1446 Driver for graphics boards with S3 Trio / S3 Virge chip.
1449 tristate "S3 Savage support"
1450 depends on FB && PCI && EXPERIMENTAL
1451 select FB_MODE_HELPERS
1452 select FB_CFB_FILLRECT
1453 select FB_CFB_COPYAREA
1454 select FB_CFB_IMAGEBLIT
1457 This driver supports notebooks and computers with S3 Savage PCI/AGP
1460 Say Y if you have such a graphics card.
1462 To compile this driver as a module, choose M here; the module
1463 will be called savagefb.
1465 config FB_SAVAGE_I2C
1466 bool "Enable DDC2 Support"
1467 depends on FB_SAVAGE
1470 This enables I2C support for S3 Savage Chipsets. This is used
1471 only for getting EDID information from the attached display
1472 allowing for robust video mode handling and switching.
1474 Because fbdev-2.6 requires that drivers must be able to
1475 independently validate video mode parameters, you should say Y
1478 config FB_SAVAGE_ACCEL
1479 bool "Enable Console Acceleration"
1480 depends on FB_SAVAGE
1483 This option will compile in console acceleration support. If
1484 the resulting framebuffer console has bothersome glitches, then
1488 tristate "SiS/XGI display support"
1489 depends on FB && PCI
1490 select FB_CFB_FILLRECT
1491 select FB_CFB_COPYAREA
1492 select FB_CFB_IMAGEBLIT
1493 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1495 This is the frame buffer device driver for the SiS 300, 315, 330
1496 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1497 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1499 To compile this driver as a module, choose M here; the module
1500 will be called sisfb.
1503 bool "SiS 300 series support"
1506 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1509 bool "SiS 315/330/340 series and XGI support"
1512 Say Y here to support use of the SiS 315, 330 and 340 series
1513 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1514 as XGI V3XT, V5, V8 and Z7.
1517 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1518 depends on FB && PCI && X86
1519 select FB_CFB_FILLRECT
1520 select FB_CFB_COPYAREA
1521 select FB_CFB_IMAGEBLIT
1526 This is the frame buffer device driver for Graphics chips of VIA
1527 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1528 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1530 Say Y if you have a VIA UniChrome graphics board.
1532 To compile this driver as a module, choose M here: the
1533 module will be called viafb.
1537 config FB_VIA_DIRECT_PROCFS
1538 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1542 Allow direct hardware access to some output registers via procfs.
1543 This is dangerous but may provide the only chance to get the
1544 correct output device configuration.
1545 Its use is strongly discouraged.
1550 tristate "NeoMagic display support"
1551 depends on FB && PCI
1552 select FB_MODE_HELPERS
1553 select FB_CFB_FILLRECT
1554 select FB_CFB_COPYAREA
1555 select FB_CFB_IMAGEBLIT
1558 This driver supports notebooks with NeoMagic PCI chips.
1559 Say Y if you have such a graphics card.
1561 To compile this driver as a module, choose M here: the
1562 module will be called neofb.
1565 tristate "IMG Kyro support"
1566 depends on FB && PCI
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1571 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1574 To compile this driver as a module, choose M here: the
1575 module will be called kyrofb.
1578 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1579 depends on FB && PCI
1580 select FB_CFB_IMAGEBLIT
1581 select FB_CFB_FILLRECT
1582 select FB_CFB_COPYAREA
1583 select FB_MODE_HELPERS
1585 This driver supports graphics boards with the 3Dfx Banshee,
1586 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1587 such a graphics board.
1589 To compile this driver as a module, choose M here: the
1590 module will be called tdfxfb.
1592 config FB_3DFX_ACCEL
1593 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1594 depends on FB_3DFX && EXPERIMENTAL
1596 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1597 device driver with acceleration functions.
1600 bool "Enable DDC/I2C support"
1601 depends on FB_3DFX && EXPERIMENTAL
1605 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1608 tristate "3Dfx Voodoo Graphics (sst1) support"
1609 depends on FB && PCI
1610 select FB_CFB_FILLRECT
1611 select FB_CFB_COPYAREA
1612 select FB_CFB_IMAGEBLIT
1614 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1615 Voodoo2 (cvg) based graphics card.
1617 To compile this driver as a module, choose M here: the
1618 module will be called sstfb.
1620 WARNING: Do not use any application that uses the 3D engine
1621 (namely glide) while using this driver.
1622 Please read the <file:Documentation/fb/sstfb.txt> for supported
1623 options and other important info support.
1626 tristate "VIA VT8623 support"
1627 depends on FB && PCI
1628 select FB_CFB_FILLRECT
1629 select FB_CFB_COPYAREA
1630 select FB_CFB_IMAGEBLIT
1631 select FB_TILEBLITTING
1634 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1636 Driver for CastleRock integrated graphics core in the
1637 VIA VT8623 [Apollo CLE266] chipset.
1640 tristate "Trident/CyberXXX/CyberBlade support"
1641 depends on FB && PCI
1642 select FB_CFB_FILLRECT
1643 select FB_CFB_COPYAREA
1644 select FB_CFB_IMAGEBLIT
1646 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1647 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1649 There are also integrated versions of these chips called CyberXXXX,
1650 CyberImage or CyberBlade. These chips are mostly found in laptops
1651 but also on some motherboards including early VIA EPIA motherboards.
1652 For more information, read <file:Documentation/fb/tridentfb.txt>
1654 Say Y if you have such a graphics board.
1656 To compile this driver as a module, choose M here: the
1657 module will be called tridentfb.
1660 tristate "ARK 2000PV support"
1661 depends on FB && PCI
1662 select FB_CFB_FILLRECT
1663 select FB_CFB_COPYAREA
1664 select FB_CFB_IMAGEBLIT
1665 select FB_TILEBLITTING
1668 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1670 Driver for PCI graphics boards with ARK 2000PV chip
1671 and ICS 5342 RAMDAC.
1674 tristate "Permedia3 support (EXPERIMENTAL)"
1675 depends on FB && PCI && EXPERIMENTAL
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1680 This is the frame buffer device driver for the 3DLabs Permedia3
1681 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1682 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1683 and maybe other boards.
1686 tristate "Fujitsu carmine frame buffer support"
1687 depends on FB && PCI
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1692 This is the frame buffer device driver for the Fujitsu Carmine chip.
1693 The driver provides two independent frame buffer devices.
1696 depends on FB_CARMINE
1697 prompt "DRAM timing"
1698 default FB_CARMINE_DRAM_EVAL
1700 config FB_CARMINE_DRAM_EVAL
1701 bool "Eval board timings"
1703 Use timings which work on the eval card.
1705 config CARMINE_DRAM_CUSTOM
1706 bool "Custom board timings"
1708 Use custom board timings.
1712 bool "Au1100 LCD Driver"
1713 depends on (FB = y) && MIPS && SOC_AU1100
1714 select FB_CFB_FILLRECT
1715 select FB_CFB_COPYAREA
1716 select FB_CFB_IMAGEBLIT
1718 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1719 various panels and CRTs by passing in kernel cmd line option
1720 au1100fb:panel=<name>.
1723 bool "Au1200 LCD Driver"
1724 depends on (FB = y) && MIPS && SOC_AU1200
1725 select FB_CFB_FILLRECT
1726 select FB_CFB_COPYAREA
1727 select FB_CFB_IMAGEBLIT
1729 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1730 various panels and CRTs by passing in kernel cmd line option
1731 au1200fb:panel=<name>.
1734 bool "VT8500 LCD Driver"
1735 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1736 select FB_WMT_GE_ROPS
1737 select FB_SYS_IMAGEBLIT
1739 This is the framebuffer driver for VIA VT8500 integrated LCD
1743 bool "WM8505 frame buffer support"
1744 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1745 select FB_WMT_GE_ROPS
1746 select FB_SYS_IMAGEBLIT
1748 This is the framebuffer driver for WonderMedia WM8505
1749 integrated LCD controller.
1751 source "drivers/video/geode/Kconfig"
1754 tristate "HD64461 Frame Buffer support"
1755 depends on FB && HD64461
1756 select FB_CFB_FILLRECT
1757 select FB_CFB_COPYAREA
1758 select FB_CFB_IMAGEBLIT
1760 This is the frame buffer device driver for the Hitachi HD64461 LCD
1764 bool "PMAG-AA TURBOchannel framebuffer support"
1765 depends on (FB = y) && TC
1766 select FB_CFB_FILLRECT
1767 select FB_CFB_COPYAREA
1768 select FB_CFB_IMAGEBLIT
1770 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1771 used mainly in the MIPS-based DECstation series.
1774 tristate "PMAG-BA TURBOchannel framebuffer support"
1776 select FB_CFB_FILLRECT
1777 select FB_CFB_COPYAREA
1778 select FB_CFB_IMAGEBLIT
1780 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1781 used mainly in the MIPS-based DECstation series.
1784 tristate "PMAGB-B TURBOchannel framebuffer support"
1786 select FB_CFB_FILLRECT
1787 select FB_CFB_COPYAREA
1788 select FB_CFB_IMAGEBLIT
1790 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1791 in the MIPS-based DECstation series. The card is currently only
1792 supported in 1280x1024x8 mode.
1795 bool "Maxine (Personal DECstation) onboard framebuffer support"
1796 depends on (FB = y) && MACH_DECSTATION
1797 select FB_CFB_FILLRECT
1798 select FB_CFB_COPYAREA
1799 select FB_CFB_IMAGEBLIT
1801 Support for the onboard framebuffer (1024x768x8) in the Personal
1802 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1806 bool "G364 frame buffer support"
1807 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1808 select FB_CFB_FILLRECT
1809 select FB_CFB_COPYAREA
1810 select FB_CFB_IMAGEBLIT
1812 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1813 Olivetti M700-10 systems.
1816 bool "Motorola 68328 native frame buffer support"
1817 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1818 select FB_CFB_FILLRECT
1819 select FB_CFB_COPYAREA
1820 select FB_CFB_IMAGEBLIT
1822 Say Y here if you want to support the built-in frame buffer of
1823 the Motorola 68328 CPU family.
1826 tristate "PXA168/910 LCD framebuffer support"
1827 depends on FB && (CPU_PXA168 || CPU_PXA910)
1828 select FB_CFB_FILLRECT
1829 select FB_CFB_COPYAREA
1830 select FB_CFB_IMAGEBLIT
1832 Frame buffer driver for the built-in LCD controller in the Marvell
1836 tristate "PXA LCD framebuffer support"
1837 depends on FB && ARCH_PXA
1838 select FB_CFB_FILLRECT
1839 select FB_CFB_COPYAREA
1840 select FB_CFB_IMAGEBLIT
1842 Frame buffer driver for the built-in LCD controller in the Intel
1845 This driver is also available as a module ( = code which can be
1846 inserted and removed from the running kernel whenever you want). The
1847 module will be called pxafb. If you want to compile it as a module,
1848 say M here and read <file:Documentation/kbuild/modules.txt>.
1852 config FB_PXA_OVERLAY
1853 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1855 depends on FB_PXA && (PXA27x || PXA3xx)
1857 config FB_PXA_SMARTPANEL
1858 bool "PXA Smartpanel LCD support"
1862 config FB_PXA_PARAMETERS
1863 bool "PXA LCD command line parameters"
1867 Enable the use of kernel command line or module parameters
1868 to configure the physical properties of the LCD panel when
1869 using the PXA LCD driver.
1871 This option allows you to override the panel parameters
1872 supplied by the platform in order to support multiple
1873 different models of flatpanel. If you will only be using a
1874 single model of flatpanel then you can safely leave this
1877 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1880 tristate "PXA3xx 2D graphics accelerator driver"
1883 Kernelspace driver for the 2D graphics controller unit (GCU)
1884 found on PXA3xx processors. There is a counterpart driver in the
1885 DirectFB suite, see http://www.directfb.org/
1887 If you compile this as a module, it will be called pxa3xx_gcu.
1890 tristate "2700G LCD framebuffer support"
1891 depends on FB && ARCH_PXA
1892 select FB_CFB_FILLRECT
1893 select FB_CFB_COPYAREA
1894 select FB_CFB_IMAGEBLIT
1896 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1900 bool "Enable debugging info via debugfs"
1901 depends on FB_MBX && DEBUG_FS
1904 Enable this if you want debugging information using the debug
1905 filesystem (debugfs)
1910 tristate "Freescale DIU framebuffer support"
1911 depends on FB && FSL_SOC
1912 select FB_MODE_HELPERS
1913 select FB_CFB_FILLRECT
1914 select FB_CFB_COPYAREA
1915 select FB_CFB_IMAGEBLIT
1916 select PPC_LIB_RHEAP
1918 Framebuffer driver for the Freescale SoC DIU
1921 tristate "W100 frame buffer support"
1922 depends on FB && ARCH_PXA
1923 select FB_CFB_FILLRECT
1924 select FB_CFB_COPYAREA
1925 select FB_CFB_IMAGEBLIT
1927 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1928 It can also drive the w3220 chip found on iPAQ hx4700.
1930 This driver is also available as a module ( = code which can be
1931 inserted and removed from the running kernel whenever you want). The
1932 module will be called w100fb. If you want to compile it as a module,
1933 say M here and read <file:Documentation/kbuild/modules.txt>.
1937 config FB_SH_MOBILE_LCDC
1938 tristate "SuperH Mobile LCDC framebuffer support"
1939 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1940 select FB_SYS_FILLRECT
1941 select FB_SYS_COPYAREA
1942 select FB_SYS_IMAGEBLIT
1944 select FB_DEFERRED_IO
1946 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1948 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1950 config FB_SH_MOBILE_HDMI
1951 tristate "SuperH Mobile HDMI controller support"
1952 depends on FB_SH_MOBILE_LCDC
1953 select FB_MODE_HELPERS
1958 Driver for the on-chip SH-Mobile HDMI controller.
1961 tristate "Toshiba Mobile IO FrameBuffer support"
1962 depends on FB && MFD_CORE
1963 select FB_CFB_FILLRECT
1964 select FB_CFB_COPYAREA
1965 select FB_CFB_IMAGEBLIT
1967 Frame buffer driver for the Toshiba Mobile IO integrated as found
1968 on the Sharp SL-6000 series
1970 This driver is also available as a module ( = code which can be
1971 inserted and removed from the running kernel whenever you want). The
1972 module will be called tmiofb. If you want to compile it as a module,
1973 say M here and read <file:Documentation/kbuild/modules.txt>.
1977 config FB_TMIO_ACCELL
1978 bool "tmiofb acceleration"
1983 tristate "Samsung S3C framebuffer support"
1984 depends on FB && S3C_DEV_FB
1985 select FB_CFB_FILLRECT
1986 select FB_CFB_COPYAREA
1987 select FB_CFB_IMAGEBLIT
1989 Frame buffer driver for the built-in FB controller in the Samsung
1990 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1991 and the S3C64XX series such as the S3C6400 and S3C6410.
1993 These chips all have the same basic framebuffer design with the
1994 actual capabilities depending on the chip. For instance the S3C6400
1995 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1996 currently only have two.
1998 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2000 config FB_S3C_DEBUG_REGWRITE
2001 bool "Debug register writes"
2004 Show all register writes via printk(KERN_DEBUG)
2007 tristate "S3C2410 LCD framebuffer support"
2008 depends on FB && ARCH_S3C2410
2009 select FB_CFB_FILLRECT
2010 select FB_CFB_COPYAREA
2011 select FB_CFB_IMAGEBLIT
2013 Frame buffer driver for the built-in LCD controller in the Samsung
2016 This driver is also available as a module ( = code which can be
2017 inserted and removed from the running kernel whenever you want). The
2018 module will be called s3c2410fb. If you want to compile it as a module,
2019 say M here and read <file:Documentation/kbuild/modules.txt>.
2022 config FB_S3C2410_DEBUG
2023 bool "S3C2410 lcd debug messages"
2024 depends on FB_S3C2410
2026 Turn on debugging messages. Note that you can set/unset at run time
2030 bool "NUC900 LCD framebuffer support"
2031 depends on FB && ARCH_W90X900
2032 select FB_CFB_FILLRECT
2033 select FB_CFB_COPYAREA
2034 select FB_CFB_IMAGEBLIT
2036 Frame buffer driver for the built-in LCD controller in the Nuvoton
2039 config GPM1040A0_320X240
2040 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2041 depends on FB_NUC900
2043 config FB_NUC900_DEBUG
2044 bool "NUC900 lcd debug messages"
2045 depends on FB_NUC900
2047 Turn on debugging messages. Note that you can set/unset at run time
2051 tristate "Silicon Motion SM501 framebuffer support"
2052 depends on FB && MFD_SM501
2053 select FB_CFB_FILLRECT
2054 select FB_CFB_COPYAREA
2055 select FB_CFB_IMAGEBLIT
2057 Frame buffer driver for the CRT and LCD controllers in the Silicon
2060 This driver is also available as a module ( = code which can be
2061 inserted and removed from the running kernel whenever you want). The
2062 module will be called sm501fb. If you want to compile it as a module,
2063 say M here and read <file:Documentation/kbuild/modules.txt>.
2068 tristate "Displaylink USB Framebuffer support"
2069 depends on FB && USB
2070 select FB_MODE_HELPERS
2071 select FB_SYS_FILLRECT
2072 select FB_SYS_COPYAREA
2073 select FB_SYS_IMAGEBLIT
2075 select FB_DEFERRED_IO
2077 This is a kernel framebuffer driver for DisplayLink USB devices.
2078 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
2079 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2080 To compile as a module, choose M here: the module name is udlfb.
2082 config FB_PNX4008_DUM
2083 tristate "Display Update Module support on Philips PNX4008 board"
2084 depends on FB && ARCH_PNX4008
2086 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2088 config FB_PNX4008_DUM_RGB
2089 tristate "RGB Framebuffer support on Philips PNX4008 board"
2090 depends on FB_PNX4008_DUM
2091 select FB_CFB_FILLRECT
2092 select FB_CFB_COPYAREA
2093 select FB_CFB_IMAGEBLIT
2095 Say Y here to enable support for PNX4008 RGB Framebuffer
2097 config FB_IBM_GXT4500
2098 tristate "Framebuffer support for IBM GXT4500P adaptor"
2099 depends on FB && PPC
2100 select FB_CFB_FILLRECT
2101 select FB_CFB_COPYAREA
2102 select FB_CFB_IMAGEBLIT
2104 Say Y here to enable support for the IBM GXT4500P display
2105 adaptor, found on some IBM System P (pSeries) machines.
2108 tristate "PS3 GPU framebuffer driver"
2109 depends on FB && PS3_PS3AV
2110 select FB_SYS_FILLRECT
2111 select FB_SYS_COPYAREA
2112 select FB_SYS_IMAGEBLIT
2114 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2116 Include support for the virtual frame buffer in the PS3 platform.
2118 config FB_PS3_DEFAULT_SIZE_M
2119 int "PS3 default frame buffer size (in MiB)"
2123 This is the default size (in MiB) of the virtual frame buffer in
2125 The default value can be overridden on the kernel command line
2126 using the "ps3fb" option (e.g. "ps3fb=9M");
2129 tristate "Xilinx frame buffer support"
2130 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2131 select FB_CFB_FILLRECT
2132 select FB_CFB_COPYAREA
2133 select FB_CFB_IMAGEBLIT
2135 Include support for the Xilinx ML300/ML403 reference design
2136 framebuffer. ML300 carries a 640*480 LCD display on the board,
2137 ML403 uses a standard DB15 VGA connector.
2140 tristate "Cobalt server LCD frame buffer support"
2141 depends on FB && MIPS_COBALT
2144 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2145 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2146 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2147 select FB_CFB_FILLRECT
2148 select FB_CFB_COPYAREA
2149 select FB_CFB_IMAGEBLIT
2151 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2152 (D)STN/TFT LCD Controller.
2153 Supports display resolutions up to 1024x1024 pixel, grayscale and
2154 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2155 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2156 panels <= 320 pixel horizontal resolution.
2159 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2160 depends on FB && ARCH_DAVINCI_DA8XX
2161 select FB_CFB_FILLRECT
2162 select FB_CFB_COPYAREA
2163 select FB_CFB_IMAGEBLIT
2165 This is the frame buffer device driver for the TI LCD controller
2166 found on DA8xx/OMAP-L1xx SoCs.
2170 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2172 select FB_SYS_FILLRECT
2173 select FB_SYS_COPYAREA
2174 select FB_SYS_IMAGEBLIT
2177 This is a `virtual' frame buffer device. It operates on a chunk of
2178 unswappable kernel memory instead of on the memory of a graphics
2179 board. This means you cannot see any output sent to this frame
2180 buffer device, while it does consume precious memory. The main use
2181 of this frame buffer device is testing and debugging the frame
2182 buffer subsystem. Do NOT enable it for normal systems! To protect
2183 the innocent, it has to be enabled explicitly at boot time using the
2184 kernel option `video=vfb:'.
2186 To compile this driver as a module, choose M here: the
2187 module will be called vfb. In order to load it, you must use
2188 the vfb_enable=1 option.
2192 config XEN_FBDEV_FRONTEND
2193 tristate "Xen virtual frame buffer support"
2194 depends on FB && XEN
2195 select FB_SYS_FILLRECT
2196 select FB_SYS_COPYAREA
2197 select FB_SYS_IMAGEBLIT
2199 select FB_DEFERRED_IO
2200 select XEN_XENBUS_FRONTEND
2203 This driver implements the front-end of the Xen virtual
2204 frame buffer driver. It communicates with a back-end
2208 tristate "E-Ink Metronome/8track controller support"
2210 select FB_SYS_FILLRECT
2211 select FB_SYS_COPYAREA
2212 select FB_SYS_IMAGEBLIT
2214 select FB_DEFERRED_IO
2216 This driver implements support for the E-Ink Metronome
2217 controller. The pre-release name for this device was 8track
2218 and could also have been called by some vendors as PVI-nnnn.
2221 tristate "Fujitsu MB862xx GDC support"
2223 select FB_CFB_FILLRECT
2224 select FB_CFB_COPYAREA
2225 select FB_CFB_IMAGEBLIT
2227 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2229 config FB_MB862XX_PCI_GDC
2230 bool "Carmine/Coral-P(A) GDC"
2231 depends on PCI && FB_MB862XX
2233 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2234 PCI graphics controller devices.
2236 config FB_MB862XX_LIME
2238 depends on FB_MB862XX
2239 depends on OF && !FB_MB862XX_PCI_GDC
2241 select FB_FOREIGN_ENDIAN
2242 select FB_LITTLE_ENDIAN
2244 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2247 tristate "EP93XX frame buffer support"
2248 depends on FB && ARCH_EP93XX
2249 select FB_CFB_FILLRECT
2250 select FB_CFB_COPYAREA
2251 select FB_CFB_IMAGEBLIT
2253 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2254 This driver is also available as a module. The module will be called
2257 config FB_PRE_INIT_FB
2258 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2259 depends on FB && FB_MB862XX_LIME
2261 Select this option if display contents should be inherited as set by
2265 tristate "MSM Framebuffer support"
2266 depends on FB && ARCH_MSM
2267 select FB_CFB_FILLRECT
2268 select FB_CFB_COPYAREA
2269 select FB_CFB_IMAGEBLIT
2272 tristate "MX3 Framebuffer support"
2273 depends on FB && MX3_IPU
2274 select FB_CFB_FILLRECT
2275 select FB_CFB_COPYAREA
2276 select FB_CFB_IMAGEBLIT
2279 This is a framebuffer device for the i.MX31 LCD Controller. So
2280 far only synchronous displays are supported. If you plan to use
2281 an LCD display with your i.MX31 system, say Y here.
2283 config FB_BROADSHEET
2284 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2286 select FB_SYS_FILLRECT
2287 select FB_SYS_COPYAREA
2288 select FB_SYS_IMAGEBLIT
2290 select FB_DEFERRED_IO
2292 This driver implements support for the E-Ink Broadsheet
2293 controller. The release name for this device was Epson S1D13521
2294 and could also have been called by other names when coupled with
2298 tristate "JZ4740 LCD framebuffer support"
2299 depends on FB && MACH_JZ4740
2300 select FB_SYS_FILLRECT
2301 select FB_SYS_COPYAREA
2302 select FB_SYS_IMAGEBLIT
2304 Framebuffer support for the JZ4740 SoC.
2306 config FB_PUV3_UNIGFX
2307 tristate "PKUnity v3 Unigfx framebuffer support"
2308 depends on FB && UNICORE32 && ARCH_PUV3
2309 select FB_SYS_FILLRECT
2310 select FB_SYS_COPYAREA
2311 select FB_SYS_IMAGEBLIT
2314 Choose this option if you want to use the Unigfx device as a
2315 framebuffer device. Without the support of PCI & AGP.
2317 source "drivers/video/omap/Kconfig"
2318 source "drivers/video/omap2/Kconfig"
2320 source "drivers/video/backlight/Kconfig"
2321 source "drivers/video/display/Kconfig"
2324 source "drivers/video/console/Kconfig"
2327 if FB || SGI_NEWPORT_CONSOLE
2328 source "drivers/video/logo/Kconfig"