5 menu "Graphics support"
14 source "drivers/char/agp/Kconfig"
16 source "drivers/gpu/vga/Kconfig"
18 source "drivers/gpu/drm/Kconfig"
20 source "drivers/gpu/stub/Kconfig"
26 config VIDEO_OUTPUT_CONTROL
27 tristate "Lowlevel video output switch controls"
29 This framework adds support for low-level control of the video
33 tristate "Support for frame buffer devices"
35 The frame buffer device provides an abstraction for the graphics
36 hardware. It represents the frame buffer of some video hardware and
37 allows application software to access the graphics hardware through
38 a well-defined interface, so the software doesn't need to know
39 anything about the low-level (hardware register) stuff.
41 Frame buffer devices work identically across the different
42 architectures supported by Linux and make the implementation of
43 application programs easier and more portable; at this point, an X
44 server exists which uses the frame buffer device exclusively.
45 On several non-X86 architectures, the frame buffer device is the
46 only way to use the graphics hardware.
48 The device is accessed through special device nodes, usually located
49 in the /dev directory, i.e. /dev/fb*.
51 You need an utility program called fbset to make full use of frame
52 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
53 and the Framebuffer-HOWTO at
54 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
57 Say Y here and to the driver for your graphics board below if you
58 are compiling a kernel for a non-x86 architecture.
60 If you are compiling for the x86 architecture, you can say Y if you
61 want to play with it, but it is not essential. Please note that
62 running graphical applications that directly touch the hardware
63 (e.g. an accelerated X server) and that are not frame buffer
64 device-aware may cause unexpected results. If unsure, say N.
67 bool "Enable firmware EDID"
71 This enables access to the EDID transferred from the firmware.
72 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
73 transfers do not work for your driver and if you are using
74 nvidiafb, i810fb or savagefb.
76 In general, choosing Y for this option is safe. If you
77 experience extremely long delays while booting before you get
78 something on your display, try setting this to N. Matrox cards in
79 combination with certain motherboards and monitors are known to
80 suffer from this problem.
89 config FB_BOOT_VESA_SUPPORT
94 If true, at least one selected framebuffer driver can take advantage
95 of VESA video modes set at an early boot stage via the vga= parameter.
97 config FB_CFB_FILLRECT
102 Include the cfb_fillrect function for generic software rectangle
103 filling. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_COPYAREA
111 Include the cfb_copyarea function for generic software area copying.
112 This is used by drivers that don't provide their own (accelerated)
115 config FB_CFB_IMAGEBLIT
120 Include the cfb_imageblit function for generic software image
121 blitting. This is used by drivers that don't provide their own
122 (accelerated) version.
124 config FB_CFB_REV_PIXELS_IN_BYTE
129 Allow generic frame-buffer functions to work on displays with 1, 2
130 and 4 bits per pixel depths which has opposite order of pixels in
131 byte order to bytes in long order.
133 config FB_SYS_FILLRECT
138 Include the sys_fillrect function for generic software rectangle
139 filling. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 config FB_SYS_COPYAREA
147 Include the sys_copyarea function for generic software area copying.
148 This is used by drivers that don't provide their own (accelerated)
149 version and the framebuffer is in system RAM.
151 config FB_SYS_IMAGEBLIT
156 Include the sys_imageblit function for generic software image
157 blitting. This is used by drivers that don't provide their own
158 (accelerated) version and the framebuffer is in system RAM.
160 menuconfig FB_FOREIGN_ENDIAN
161 bool "Framebuffer foreign endianness support"
164 This menu will let you enable support for the framebuffers with
165 non-native endianness (e.g. Little-Endian framebuffer on a
166 Big-Endian machine). Most probably you don't have such hardware,
167 so it's safe to say "n" here.
170 prompt "Choice endianness support"
171 depends on FB_FOREIGN_ENDIAN
173 config FB_BOTH_ENDIAN
174 bool "Support for Big- and Little-Endian framebuffers"
177 bool "Support for Big-Endian framebuffers only"
179 config FB_LITTLE_ENDIAN
180 bool "Support for Little-Endian framebuffers only"
189 config FB_WMT_GE_ROPS
194 Include functions for accelerated rectangle filling and area
195 copying using WonderMedia Graphics Engine operations.
197 config FB_DEFERRED_IO
204 depends on FB_DEFERRED_IO
211 Common utility functions useful to fbdev drivers of VGA-based
222 select BACKLIGHT_LCD_SUPPORT
223 select BACKLIGHT_CLASS_DEVICE
226 config FB_MODE_HELPERS
227 bool "Enable Video Mode Handling Helpers"
231 This enables functions for handling video modes using the
232 Generalized Timing Formula and the EDID parser. A few drivers rely
233 on this feature such as the radeonfb, rivafb, and the i810fb. If
234 your driver does not take advantage of this feature, choosing Y will
235 just increase the kernel size by about 5K.
237 config FB_TILEBLITTING
238 bool "Enable Tile Blitting Support"
242 This enables tile blitting. Tile blitting is a drawing technique
243 where the screen is divided into rectangular sections (tiles), whereas
244 the standard blitting divides the screen into pixels. Because the
245 default drawing element is a tile, drawing functions will be passed
246 parameters in terms of number of tiles instead of number of pixels.
247 For example, to draw a single character, instead of using bitmaps,
248 an index to an array of bitmaps will be used. To clear or move a
249 rectangular section of a screen, the rectangle will be described in
250 terms of number of tiles in the x- and y-axis.
252 This is particularly important to one driver, matroxfb. If
255 comment "Frame buffer hardware drivers"
259 tristate "Cirrus Logic support"
260 depends on FB && (ZORRO || PCI)
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This enables support for Cirrus Logic GD542x/543x based boards on
266 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
268 If you have a PCI-based system, this enables support for these
269 chips: GD-543x, GD-544x, GD-5480.
271 Please read the file <file:Documentation/fb/cirrusfb.txt>.
273 Say N unless you have such a graphics board or plan to get one
274 before you next recompile the kernel.
277 tristate "Permedia2 support"
278 depends on FB && ((AMIGA && BROKEN) || PCI)
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
283 This is the frame buffer device driver for cards based on
284 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
285 The driver was tested on the following cards:
286 Diamond FireGL 1000 PRO AGP
287 ELSA Gloria Synergy PCI
288 Appian Jeronimo PRO (both heads) PCI
289 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
290 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
291 ASK Graphic Blaster Exxtreme AGP
293 To compile this driver as a module, choose M here: the
294 module will be called pm2fb.
296 config FB_PM2_FIFO_DISCONNECT
297 bool "enable FIFO disconnect feature"
298 depends on FB_PM2 && PCI
300 Support the Permedia2 FIFO disconnect feature.
303 tristate "ARM PrimeCell PL110 support"
304 depends on FB && ARM && ARM_AMBA
305 select FB_CFB_FILLRECT
306 select FB_CFB_COPYAREA
307 select FB_CFB_IMAGEBLIT
309 This framebuffer device driver is for the ARM PrimeCell PL110
310 Colour LCD controller. ARM PrimeCells provide the building
311 blocks for System on a Chip devices.
313 If you want to compile this as a module (=code which can be
314 inserted into and removed from the running kernel), say M
315 here and read <file:Documentation/kbuild/modules.txt>. The module
316 will be called amba-clcd.
320 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
322 default FB_ARMCLCD_SHARP_LQ035Q7DB02
324 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
325 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
327 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
328 color QVGA, HRTFT panel. The LogicPD device includes
329 an integrated HRTFT controller IC.
330 The native resolution is 240x320.
332 config FB_ARMCLCD_SHARP_LQ057Q3DC02
333 bool "LogicPD LCD 5.7\" QVGA"
335 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
336 color QVGA, TFT panel. The LogicPD device includes an
337 The native resolution is 320x240.
339 config FB_ARMCLCD_SHARP_LQ64D343
340 bool "LogicPD LCD 6.4\" VGA"
342 This is an implementation of the Sharp LQ64D343, a 6.4"
343 color VGA, TFT panel. The LogicPD device includes an
344 The native resolution is 640x480.
346 config FB_ARMCLCD_SHARP_LQ10D368
347 bool "LogicPD LCD 10.4\" VGA"
349 This is an implementation of the Sharp LQ10D368, a 10.4"
350 color VGA, TFT panel. The LogicPD device includes an
351 The native resolution is 640x480.
354 config FB_ARMCLCD_SHARP_LQ121S1DG41
355 bool "LogicPD LCD 12.1\" SVGA"
357 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
358 color SVGA, TFT panel. The LogicPD device includes an
359 The native resolution is 800x600.
361 This panel requires a clock rate may be an integer fraction
362 of the base LCDCLK frequency. The driver will select the
363 highest frequency available that is lower than the maximum
364 allowed. The panel may flicker if the clock rate is
365 slower than the recommended minimum.
367 config FB_ARMCLCD_AUO_A070VW01_WIDE
368 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
370 This is an implementation of the AU Optronics, a 7.0"
371 WIDE Color. The native resolution is 234x480.
373 config FB_ARMCLCD_HITACHI
374 bool "Hitachi Wide Screen 800x480"
376 This is an implementation of the Hitachi 800x480.
382 bool "Acorn VIDC support"
383 depends on (FB = y) && ARM && ARCH_ACORN
384 select FB_CFB_FILLRECT
385 select FB_CFB_COPYAREA
386 select FB_CFB_IMAGEBLIT
388 This is the frame buffer device driver for the Acorn VIDC graphics
389 hardware found in Acorn RISC PCs and other ARM-based machines. If
393 bool "CLPS711X LCD support"
394 depends on (FB = y) && ARM && ARCH_CLPS711X
395 select FB_CFB_FILLRECT
396 select FB_CFB_COPYAREA
397 select FB_CFB_IMAGEBLIT
399 Say Y to enable the Framebuffer driver for the CLPS7111 and
403 bool "SA-1100 LCD support"
404 depends on (FB = y) && ARM && ARCH_SA1100
405 select FB_CFB_FILLRECT
406 select FB_CFB_COPYAREA
407 select FB_CFB_IMAGEBLIT
409 This is a framebuffer device for the SA-1100 LCD Controller.
410 See <http://www.linux-fbdev.org/> for information on framebuffer
413 If you plan to use the LCD display with your SA-1100 system, say
417 tristate "Motorola i.MX LCD support"
418 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
419 select FB_CFB_FILLRECT
420 select FB_CFB_COPYAREA
421 select FB_CFB_IMAGEBLIT
424 tristate "CyberPro 2000/2010/5000 support"
425 depends on FB && PCI && (BROKEN || !SPARC64)
426 select FB_CFB_FILLRECT
427 select FB_CFB_COPYAREA
428 select FB_CFB_IMAGEBLIT
430 This enables support for the Integraphics CyberPro 20x0 and 5000
431 VGA chips used in the Rebel.com Netwinder and other machines.
432 Say Y if you have a NetWinder or a graphics card containing this
433 device, otherwise say N.
437 depends on (FB = y) && APOLLO
439 select FB_CFB_FILLRECT
440 select FB_CFB_IMAGEBLIT
444 depends on (FB = y) && Q40
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
451 tristate "Amiga native chipset support"
452 depends on FB && AMIGA
454 This is the frame buffer device driver for the builtin graphics
455 chipset found in Amigas.
457 To compile this driver as a module, choose M here: the
458 module will be called amifb.
461 bool "Amiga OCS chipset support"
464 This enables support for the original Agnus and Denise video chips,
465 found in the Amiga 1000 and most A500's and A2000's. If you intend
466 to run Linux on any of these systems, say Y; otherwise say N.
469 bool "Amiga ECS chipset support"
472 This enables support for the Enhanced Chip Set, found in later
473 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
474 you intend to run Linux on any of these systems, say Y; otherwise
478 bool "Amiga AGA chipset support"
481 This enables support for the Advanced Graphics Architecture (also
482 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
483 and CD32. If you intend to run Linux on any of these systems, say Y;
487 bool "Amiga FrameMaster II/Rainbow II support"
488 depends on (FB = y) && ZORRO
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the Amiga FrameMaster
494 card from BSC (exhibited 1992 but not shipped as a CBM product).
497 tristate "Arc Monochrome LCD board support"
499 select FB_SYS_FILLRECT
500 select FB_SYS_COPYAREA
501 select FB_SYS_IMAGEBLIT
504 This enables support for the Arc Monochrome LCD board. The board
505 is based on the KS-108 lcd controller and is typically a matrix
506 of 2*n chips. This driver was tested with a 128x64 panel. This
507 driver supports it for use with x86 SBCs through a 16 bit GPIO
508 interface (8 bit data, 8 bit control). If you anticipate using
509 this driver, say Y or M; otherwise say N. You must specify the
510 GPIO IO address to be used for setting control and data.
513 bool "Atari native chipset support"
514 depends on (FB = y) && ATARI
515 select FB_CFB_FILLRECT
516 select FB_CFB_COPYAREA
517 select FB_CFB_IMAGEBLIT
519 This is the frame buffer device driver for the builtin graphics
520 chipset found in Ataris.
523 bool "Open Firmware frame buffer device support"
524 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
525 select FB_CFB_FILLRECT
526 select FB_CFB_COPYAREA
527 select FB_CFB_IMAGEBLIT
530 Say Y if you want support with Open Firmware for your graphics
534 bool "Apple \"control\" display support"
535 depends on (FB = y) && PPC_PMAC && PPC32
536 select FB_CFB_FILLRECT
537 select FB_CFB_COPYAREA
538 select FB_CFB_IMAGEBLIT
541 This driver supports a frame buffer for the graphics adapter in the
542 Power Macintosh 7300 and others.
545 bool "Apple \"platinum\" display support"
546 depends on (FB = y) && PPC_PMAC && PPC32
547 select FB_CFB_FILLRECT
548 select FB_CFB_COPYAREA
549 select FB_CFB_IMAGEBLIT
552 This driver supports a frame buffer for the "platinum" graphics
553 adapter in some Power Macintoshes.
556 bool "Apple \"valkyrie\" display support"
557 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
558 select FB_CFB_FILLRECT
559 select FB_CFB_COPYAREA
560 select FB_CFB_IMAGEBLIT
563 This driver supports a frame buffer for the "valkyrie" graphics
564 adapter in some Power Macintoshes.
567 bool "Chips 65550 display support"
568 depends on (FB = y) && PPC32 && PCI
569 select FB_CFB_FILLRECT
570 select FB_CFB_COPYAREA
571 select FB_CFB_IMAGEBLIT
573 This is the frame buffer device driver for the Chips & Technologies
574 65550 graphics chip in PowerBooks.
577 bool "Asiliant (Chips) 69000 display support"
578 depends on (FB = y) && PCI
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
583 This is the frame buffer device driver for the Asiliant 69030 chipset
586 bool "IMS Twin Turbo display support"
587 depends on (FB = y) && PCI
588 select FB_CFB_IMAGEBLIT
589 select FB_MACMODES if PPC
591 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
592 many Macintosh and compatible computers.
595 tristate "VGA 16-color graphics support"
596 depends on FB && (X86 || PPC)
597 select FB_CFB_FILLRECT
598 select FB_CFB_COPYAREA
599 select FB_CFB_IMAGEBLIT
601 select FONT_8x16 if FRAMEBUFFER_CONSOLE
603 This is the frame buffer device driver for VGA 16 color graphic
604 cards. Say Y if you have such a card.
606 To compile this driver as a module, choose M here: the
607 module will be called vga16fb.
609 config FB_BF54X_LQ043
610 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
611 depends on FB && (BF54x) && !BF542
612 select FB_CFB_FILLRECT
613 select FB_CFB_COPYAREA
614 select FB_CFB_IMAGEBLIT
616 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
618 config FB_BFIN_T350MCQB
619 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
620 depends on FB && BLACKFIN
622 select FB_CFB_FILLRECT
623 select FB_CFB_COPYAREA
624 select FB_CFB_IMAGEBLIT
626 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
627 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
628 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
630 config FB_BFIN_LQ035Q1
631 tristate "SHARP LQ035Q1DH02 TFT LCD"
632 depends on FB && BLACKFIN && SPI
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
638 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
639 the Blackfin Landscape LCD EZ-Extender Card.
640 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
641 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
643 To compile this driver as a module, choose M here: the
644 module will be called bfin-lq035q1-fb.
646 config FB_BF537_LQ035
647 tristate "SHARP LQ035 TFT LCD (BF537 STAMP)"
648 depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
654 This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD
657 To compile this driver as a module, choose M here: the
658 module will be called bf537-lq035.
661 tristate "HP STI frame buffer device support"
662 depends on FB && PARISC
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
670 STI refers to the HP "Standard Text Interface" which is a set of
671 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
672 Enabling this option will implement the linux framebuffer device
673 using calls to the STI BIOS routines for initialisation.
675 If you enable this option, you will get a planar framebuffer device
676 /dev/fb which will work on the most common HP graphic cards of the
677 NGLE family, including the artist chips (in the 7xx and Bxxx series),
678 HCRX, HCRX24, CRX, CRX24 and VisEG series.
680 It is safe to enable this option, so you should probably say "Y".
683 bool "Generic Macintosh display support"
684 depends on (FB = y) && MAC
685 select FB_CFB_FILLRECT
686 select FB_CFB_COPYAREA
687 select FB_CFB_IMAGEBLIT
692 depends on (FB = y) && DIO
693 select FB_CFB_IMAGEBLIT
697 tristate "TGA/SFB+ framebuffer support"
698 depends on FB && (ALPHA || TC)
699 select FB_CFB_FILLRECT
700 select FB_CFB_COPYAREA
701 select FB_CFB_IMAGEBLIT
704 This is the frame buffer device driver for generic TGA and SFB+
705 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
706 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
707 TURBOchannel cards, also known as PMAGD-A, -B and -C.
709 Due to hardware limitations ZLX-E2 and E3 cards are not supported
710 for DECstation 5000/200 systems. Additionally due to firmware
711 limitations these cards may cause troubles with booting DECstation
712 5000/240 and /260 systems, but are fully supported under Linux if
713 you manage to get it going. ;-)
715 Say Y if you have one of those.
718 tristate "Userspace VESA VGA graphics support"
719 depends on FB && CONNECTOR
720 select FB_CFB_FILLRECT
721 select FB_CFB_COPYAREA
722 select FB_CFB_IMAGEBLIT
723 select FB_MODE_HELPERS
725 This is the frame buffer driver for generic VBE 2.0 compliant
726 graphic cards. It can also take advantage of VBE 3.0 features,
727 such as refresh rate adjustment.
729 This driver generally provides more features than vesafb but
730 requires a userspace helper application called 'v86d'. See
731 <file:Documentation/fb/uvesafb.txt> for more information.
736 bool "VESA VGA graphics support"
737 depends on (FB = y) && X86
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
741 select FB_BOOT_VESA_SUPPORT
743 This is the frame buffer device driver for generic VESA 2.0
744 compliant graphic cards. The older VESA 1.2 cards are not supported.
745 You will get a boot time penguin logo at no additional cost. Please
746 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
749 bool "EFI-based Framebuffer Support"
750 depends on (FB = y) && X86 && EFI
751 select FB_CFB_FILLRECT
752 select FB_CFB_COPYAREA
753 select FB_CFB_IMAGEBLIT
755 This is the EFI frame buffer device driver. If the firmware on
756 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
757 using the EFI framebuffer as your console.
760 tristate "N411 Apollo/Hecuba devkit support"
761 depends on FB && X86 && MMU
762 select FB_SYS_FILLRECT
763 select FB_SYS_COPYAREA
764 select FB_SYS_IMAGEBLIT
766 select FB_DEFERRED_IO
769 This enables support for the Apollo display controller in its
770 Hecuba form using the n411 devkit.
773 tristate "Hercules mono graphics support"
775 select FB_CFB_FILLRECT
776 select FB_CFB_COPYAREA
777 select FB_CFB_IMAGEBLIT
779 Say Y here if you have a Hercules mono graphics card.
781 To compile this driver as a module, choose M here: the
782 module will be called hgafb.
784 As this card technology is 15 years old, most people will answer N
788 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
789 depends on FB_HGA && EXPERIMENTAL
791 This will compile the Hercules mono graphics with
792 acceleration functions.
795 tristate "SGI Visual Workstation framebuffer support"
796 depends on FB && X86_VISWS
797 select FB_CFB_FILLRECT
798 select FB_CFB_COPYAREA
799 select FB_CFB_IMAGEBLIT
801 SGI Visual Workstation support for framebuffer graphics.
804 bool "SGI Graphics Backend frame buffer support"
805 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
806 select FB_CFB_FILLRECT
807 select FB_CFB_COPYAREA
808 select FB_CFB_IMAGEBLIT
810 This is the frame buffer device driver for SGI Graphics Backend.
811 This chip is used in SGI O2 and Visual Workstation 320/540.
814 int "Video memory size in MB"
818 This is the amount of memory reserved for the framebuffer,
819 which can be any value between 1MB and 8MB.
822 bool "SBUS and UPA framebuffers"
823 depends on (FB = y) && SPARC
825 Say Y if you want support for SBUS or UPA based frame buffer device.
829 depends on (FB = y) && (SPARC && FB_SBUS)
830 select FB_CFB_FILLRECT
831 select FB_CFB_COPYAREA
832 select FB_CFB_IMAGEBLIT
834 This is the frame buffer device driver for the BWtwo frame buffer.
837 bool "CGthree support"
838 depends on (FB = y) && (SPARC && FB_SBUS)
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This is the frame buffer device driver for the CGthree frame buffer.
846 bool "CGsix (GX,TurboGX) support"
847 depends on (FB = y) && (SPARC && FB_SBUS)
848 select FB_CFB_COPYAREA
849 select FB_CFB_IMAGEBLIT
851 This is the frame buffer device driver for the CGsix (GX, TurboGX)
855 bool "Creator/Creator3D/Elite3D support"
856 depends on FB_SBUS && SPARC64
857 select FB_CFB_COPYAREA
858 select FB_CFB_IMAGEBLIT
860 This is the frame buffer device driver for the Creator, Creator3D,
861 and Elite3D graphics boards.
864 bool "TCX (SS4/SS5 only) support"
866 select FB_CFB_FILLRECT
867 select FB_CFB_COPYAREA
868 select FB_CFB_IMAGEBLIT
870 This is the frame buffer device driver for the TCX 24/8bit frame
874 bool "CGfourteen (SX) support"
876 select FB_CFB_FILLRECT
877 select FB_CFB_COPYAREA
878 select FB_CFB_IMAGEBLIT
880 This is the frame buffer device driver for the CGfourteen frame
881 buffer on Desktop SPARCsystems with the SX graphics option.
884 bool "P9100 (Sparcbook 3 only) support"
886 select FB_CFB_FILLRECT
887 select FB_CFB_COPYAREA
888 select FB_CFB_IMAGEBLIT
890 This is the frame buffer device driver for the P9100 card
891 supported on Sparcbook 3 machines.
894 bool "Leo (ZX) support"
896 select FB_CFB_FILLRECT
897 select FB_CFB_COPYAREA
898 select FB_CFB_IMAGEBLIT
900 This is the frame buffer device driver for the SBUS-based Sun ZX
901 (leo) frame buffer cards.
904 bool "IGA 168x display support"
905 depends on (FB = y) && SPARC32
906 select FB_CFB_FILLRECT
907 select FB_CFB_COPYAREA
908 select FB_CFB_IMAGEBLIT
910 This is the framebuffer device for the INTERGRAPHICS 1680 and
911 successor frame buffer cards.
914 bool "Sun XVR-500 3DLABS Wildcat support"
915 depends on (FB = y) && PCI && SPARC64
916 select FB_CFB_FILLRECT
917 select FB_CFB_COPYAREA
918 select FB_CFB_IMAGEBLIT
920 This is the framebuffer device for the Sun XVR-500 and similar
921 graphics cards based upon the 3DLABS Wildcat chipset. The driver
922 only works on sparc64 systems where the system firmware has
923 mostly initialized the card already. It is treated as a
924 completely dumb framebuffer device.
927 bool "Sun XVR-2500 3DLABS Wildcat support"
928 depends on (FB = y) && PCI && SPARC64
929 select FB_CFB_FILLRECT
930 select FB_CFB_COPYAREA
931 select FB_CFB_IMAGEBLIT
933 This is the framebuffer device for the Sun XVR-2500 and similar
934 graphics cards based upon the 3DLABS Wildcat chipset. The driver
935 only works on sparc64 systems where the system firmware has
936 mostly initialized the card already. It is treated as a
937 completely dumb framebuffer device.
940 bool "Sun XVR-1000 support"
941 depends on (FB = y) && SPARC64
942 select FB_CFB_FILLRECT
943 select FB_CFB_COPYAREA
944 select FB_CFB_IMAGEBLIT
946 This is the framebuffer device for the Sun XVR-1000 and similar
947 graphics cards. The driver only works on sparc64 systems where
948 the system firmware has mostly initialized the card already. It
949 is treated as a completely dumb framebuffer device.
952 tristate "NEC PowerVR 2 display support"
953 depends on FB && SH_DREAMCAST
954 select FB_CFB_FILLRECT
955 select FB_CFB_COPYAREA
956 select FB_CFB_IMAGEBLIT
958 Say Y here if you have a PowerVR 2 card in your box. If you plan to
959 run linux on your Dreamcast, you will have to say Y here.
960 This driver may or may not work on other PowerVR 2 cards, but is
961 totally untested. Use at your own risk. If unsure, say N.
963 To compile this driver as a module, choose M here: the
964 module will be called pvr2fb.
966 You can pass several parameters to the driver at boot time or at
967 module load time. The parameters look like "video=pvr2:XXX", where
968 the meaning of XXX can be found at the end of the main source file
969 (<file:drivers/video/pvr2fb.c>). Please see the file
970 <file:Documentation/fb/pvr2fb.txt>.
973 bool "Epson 1355 framebuffer support"
974 depends on (FB = y) && ARCH_CEIVA
975 select FB_CFB_FILLRECT
976 select FB_CFB_COPYAREA
977 select FB_CFB_IMAGEBLIT
979 Build in support for the SED1355 Epson Research Embedded RAMDAC
980 LCD/CRT Controller (since redesignated as the S1D13505) as a
981 framebuffer. Product specs at
982 <http://vdc.epson.com/>.
985 tristate "Epson S1D13XXX framebuffer support"
987 select FB_CFB_FILLRECT
988 select FB_CFB_COPYAREA
989 select FB_CFB_IMAGEBLIT
991 Support for S1D13XXX framebuffer device family (currently only
992 working with S1D13806). Product specs at
993 <http://vdc.epson.com/>
996 tristate "AT91/AT32 LCD Controller support"
997 depends on FB && HAVE_FB_ATMEL
998 select FB_CFB_FILLRECT
999 select FB_CFB_COPYAREA
1000 select FB_CFB_IMAGEBLIT
1002 This enables support for the AT91/AT32 LCD Controller.
1005 bool "Frame Buffer in internal SRAM"
1006 depends on FB_ATMEL && ARCH_AT91SAM9261
1008 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
1009 to let frame buffer in external SDRAM.
1012 bool "Use a STN display with AT91/AT32 LCD Controller"
1013 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1016 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1017 Controller. Say N if you want to connect a TFT.
1022 tristate "nVidia Framebuffer Support"
1023 depends on FB && PCI
1024 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1025 select FB_MODE_HELPERS
1026 select FB_CFB_FILLRECT
1027 select FB_CFB_COPYAREA
1028 select FB_CFB_IMAGEBLIT
1032 This driver supports graphics boards with the nVidia chips, TNT
1033 and newer. For very old chipsets, such as the RIVA128, then use
1035 Say Y if you have such a graphics board.
1037 To compile this driver as a module, choose M here: the
1038 module will be called nvidiafb.
1040 config FB_NVIDIA_I2C
1041 bool "Enable DDC Support"
1042 depends on FB_NVIDIA
1045 This enables I2C support for nVidia Chipsets. This is used
1046 only for getting EDID information from the attached display
1047 allowing for robust video mode handling and switching.
1049 Because fbdev-2.6 requires that drivers must be able to
1050 independently validate video mode parameters, you should say Y
1053 config FB_NVIDIA_DEBUG
1054 bool "Lots of debug output"
1055 depends on FB_NVIDIA
1058 Say Y here if you want the nVidia driver to output all sorts
1059 of debugging information to provide to the maintainer when
1060 something goes wrong.
1062 config FB_NVIDIA_BACKLIGHT
1063 bool "Support for backlight control"
1064 depends on FB_NVIDIA
1067 Say Y here if you want to control the backlight of your display.
1070 tristate "nVidia Riva support"
1071 depends on FB && PCI
1072 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1073 select FB_MODE_HELPERS
1074 select FB_CFB_FILLRECT
1075 select FB_CFB_COPYAREA
1076 select FB_CFB_IMAGEBLIT
1080 This driver supports graphics boards with the nVidia Riva/Geforce
1082 Say Y if you have such a graphics board.
1084 To compile this driver as a module, choose M here: the
1085 module will be called rivafb.
1088 bool "Enable DDC Support"
1092 This enables I2C support for nVidia Chipsets. This is used
1093 only for getting EDID information from the attached display
1094 allowing for robust video mode handling and switching.
1096 Because fbdev-2.6 requires that drivers must be able to
1097 independently validate video mode parameters, you should say Y
1100 config FB_RIVA_DEBUG
1101 bool "Lots of debug output"
1105 Say Y here if you want the Riva driver to output all sorts
1106 of debugging information to provide to the maintainer when
1107 something goes wrong.
1109 config FB_RIVA_BACKLIGHT
1110 bool "Support for backlight control"
1114 Say Y here if you want to control the backlight of your display.
1117 tristate "Intel 810/815 support (EXPERIMENTAL)"
1118 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1119 select FB_MODE_HELPERS
1120 select FB_CFB_FILLRECT
1121 select FB_CFB_COPYAREA
1122 select FB_CFB_IMAGEBLIT
1125 This driver supports the on-board graphics built in to the Intel 810
1126 and 815 chipsets. Say Y if you have and plan to use such a board.
1128 To compile this driver as a module, choose M here: the
1129 module will be called i810fb.
1131 For more information, please read
1132 <file:Documentation/fb/intel810.txt>
1135 bool "use VESA Generalized Timing Formula"
1138 If you say Y, then the VESA standard, Generalized Timing Formula
1139 or GTF, will be used to calculate the required video timing values
1140 per video mode. Since the GTF allows nondiscrete timings
1141 (nondiscrete being a range of values as opposed to discrete being a
1142 set of values), you'll be able to use any combination of horizontal
1143 and vertical resolutions, and vertical refresh rates without having
1144 to specify your own timing parameters. This is especially useful
1145 to maximize the performance of an aging display, or if you just
1146 have a display with nonstandard dimensions. A VESA compliant
1147 monitor is recommended, but can still work with non-compliant ones.
1148 If you need or want this, then select this option. The timings may
1149 not be compliant with Intel's recommended values. Use at your own
1152 If you say N, the driver will revert to discrete video timings
1153 using a set recommended by Intel in their documentation.
1158 bool "Enable DDC Support"
1159 depends on FB_I810 && FB_I810_GTF
1164 tristate "Intel LE80578 (Vermilion) support"
1165 depends on FB && PCI && X86
1166 select FB_MODE_HELPERS
1167 select FB_CFB_FILLRECT
1168 select FB_CFB_COPYAREA
1169 select FB_CFB_IMAGEBLIT
1171 This driver supports the LE80578 (Vermilion Range) chipset
1173 config FB_CARILLO_RANCH
1174 tristate "Intel Carillo Ranch support"
1175 depends on FB_LE80578 && FB && PCI && X86
1177 This driver supports the LE80578 (Carillo Ranch) board
1180 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1181 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1182 select FB_MODE_HELPERS
1183 select FB_CFB_FILLRECT
1184 select FB_CFB_COPYAREA
1185 select FB_CFB_IMAGEBLIT
1186 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1187 depends on !DRM_I915
1189 This driver supports the on-board graphics built in to the Intel
1190 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1191 Say Y if you have and plan to use such a board.
1193 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1195 To compile this driver as a module, choose M here: the
1196 module will be called intelfb.
1198 For more information, please read <file:Documentation/fb/intelfb.txt>
1200 config FB_INTEL_DEBUG
1201 bool "Intel driver Debug Messages"
1204 Say Y here if you want the Intel driver to output all sorts
1205 of debugging information to provide to the maintainer when
1206 something goes wrong.
1209 bool "DDC/I2C for Intel framebuffer support"
1214 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1217 tristate "Matrox acceleration"
1218 depends on FB && PCI
1219 select FB_CFB_FILLRECT
1220 select FB_CFB_COPYAREA
1221 select FB_CFB_IMAGEBLIT
1222 select FB_TILEBLITTING
1223 select FB_MACMODES if PPC_PMAC
1225 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1226 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1227 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1228 Matrox G400, G450 or G550 card in your box.
1230 To compile this driver as a module, choose M here: the
1231 module will be called matroxfb.
1233 You can pass several parameters to the driver at boot time or at
1234 module load time. The parameters look like "video=matrox:XXX", and
1235 are described in <file:Documentation/fb/matroxfb.txt>.
1237 config FB_MATROX_MILLENIUM
1238 bool "Millennium I/II support"
1239 depends on FB_MATROX
1241 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1242 video card. If you select "Advanced lowlevel driver options" below,
1243 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1244 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1245 also use font widths different from 8.
1247 config FB_MATROX_MYSTIQUE
1248 bool "Mystique support"
1249 depends on FB_MATROX
1251 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1252 video card. If you select "Advanced lowlevel driver options" below,
1253 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1254 packed pixel and 32 bpp packed pixel. You can also use font widths
1258 bool "G100/G200/G400/G450/G550 support"
1259 depends on FB_MATROX
1261 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1262 video card. If you select "Advanced lowlevel driver options", you
1263 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1264 pixel and 32 bpp packed pixel. You can also use font widths
1267 If you need support for G400 secondary head, you must say Y to
1268 "Matrox I2C support" and "G400 second head support" right below.
1269 G450/G550 secondary head and digital output are supported without
1272 The driver starts in monitor mode. You must use the matroxset tool
1273 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1274 swap primary and secondary head outputs, or to change output mode.
1275 Secondary head driver always start in 640x480 resolution and you
1276 must use fbset to change it.
1278 Do not forget that second head supports only 16 and 32 bpp
1279 packed pixels, so it is a good idea to compile them into the kernel
1280 too. You can use only some font widths, as the driver uses generic
1281 painting procedures (the secondary head does not use acceleration
1284 G450/G550 hardware can display TV picture only from secondary CRTC,
1285 and it performs no scaling, so picture must have 525 or 625 lines.
1287 config FB_MATROX_I2C
1288 tristate "Matrox I2C support"
1289 depends on FB_MATROX
1292 This drivers creates I2C buses which are needed for accessing the
1293 DDC (I2C) bus present on all Matroxes, an I2C bus which
1294 interconnects Matrox optional devices, like MGA-TVO on G200 and
1295 G400, and the secondary head DDC bus, present on G400 only.
1297 You can say Y or M here if you want to experiment with monitor
1298 detection code. You must say Y or M here if you want to use either
1299 second head of G400 or MGA-TVO on G200 or G400.
1301 If you compile it as module, it will create a module named
1304 config FB_MATROX_MAVEN
1305 tristate "G400 second head support"
1306 depends on FB_MATROX_G && FB_MATROX_I2C
1308 WARNING !!! This support does not work with G450 !!!
1310 Say Y or M here if you want to use a secondary head (meaning two
1311 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1312 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1313 secondary head output is blanked while you are in X. With XFree
1314 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1315 the fbdev driver on first head and the fbdev driver on second head.
1317 If you compile it as module, two modules are created,
1318 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1319 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1320 also load i2c-matroxfb to get it to run.
1322 The driver starts in monitor mode and you must use the matroxset
1324 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1325 PAL or NTSC or to swap primary and secondary head outputs.
1326 Secondary head driver also always start in 640x480 resolution, you
1327 must use fbset to change it.
1329 Also do not forget that second head supports only 16 and 32 bpp
1330 packed pixels, so it is a good idea to compile them into the kernel
1331 too. You can use only some font widths, as the driver uses generic
1332 painting procedures (the secondary head does not use acceleration
1336 tristate "ATI Radeon display support"
1337 depends on FB && PCI
1338 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1339 select FB_MODE_HELPERS
1340 select FB_CFB_FILLRECT
1341 select FB_CFB_COPYAREA
1342 select FB_CFB_IMAGEBLIT
1343 select FB_MACMODES if PPC_OF
1345 Choose this option if you want to use an ATI Radeon graphics card as
1346 a framebuffer device. There are both PCI and AGP versions. You
1347 don't need to choose this to run the Radeon in plain VGA mode.
1349 There is a product page at
1350 http://products.amd.com/en-us/GraphicCardResult.aspx
1352 config FB_RADEON_I2C
1353 bool "DDC/I2C for ATI Radeon support"
1354 depends on FB_RADEON
1358 Say Y here if you want DDC/I2C support for your Radeon board.
1360 config FB_RADEON_BACKLIGHT
1361 bool "Support for backlight control"
1362 depends on FB_RADEON
1365 Say Y here if you want to control the backlight of your display.
1367 config FB_RADEON_DEBUG
1368 bool "Lots of debug output from Radeon driver"
1369 depends on FB_RADEON
1372 Say Y here if you want the Radeon driver to output all sorts
1373 of debugging information to provide to the maintainer when
1374 something goes wrong.
1377 tristate "ATI Rage128 display support"
1378 depends on FB && PCI
1379 select FB_CFB_FILLRECT
1380 select FB_CFB_COPYAREA
1381 select FB_CFB_IMAGEBLIT
1382 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1383 select FB_MACMODES if PPC_PMAC
1385 This driver supports graphics boards with the ATI Rage128 chips.
1386 Say Y if you have such a graphics board and read
1387 <file:Documentation/fb/aty128fb.txt>.
1389 To compile this driver as a module, choose M here: the
1390 module will be called aty128fb.
1392 config FB_ATY128_BACKLIGHT
1393 bool "Support for backlight control"
1394 depends on FB_ATY128
1397 Say Y here if you want to control the backlight of your display.
1400 tristate "ATI Mach64 display support" if PCI || ATARI
1401 depends on FB && !SPARC32
1402 select FB_CFB_FILLRECT
1403 select FB_CFB_COPYAREA
1404 select FB_CFB_IMAGEBLIT
1405 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1406 select FB_MACMODES if PPC
1408 This driver supports graphics boards with the ATI Mach64 chips.
1409 Say Y if you have such a graphics board.
1411 To compile this driver as a module, choose M here: the
1412 module will be called atyfb.
1415 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1416 depends on PCI && FB_ATY
1417 default y if SPARC64 && PCI
1419 Say Y here to support use of ATI's 64-bit Rage boards (or other
1420 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1421 framebuffer device. The ATI product support page for these boards
1422 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1424 config FB_ATY_GENERIC_LCD
1425 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1426 depends on FB_ATY_CT
1428 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1429 Rage XC, or Rage XL chipset.
1432 bool "Mach64 GX support" if PCI
1436 Say Y here to support use of the ATI Mach64 Graphics Expression
1437 board (or other boards based on the Mach64 GX chipset) as a
1438 framebuffer device. The ATI product support page for these boards
1440 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1442 config FB_ATY_BACKLIGHT
1443 bool "Support for backlight control"
1447 Say Y here if you want to control the backlight of your display.
1450 tristate "S3 Trio/Virge support"
1451 depends on FB && PCI
1452 select FB_CFB_FILLRECT
1453 select FB_CFB_COPYAREA
1454 select FB_CFB_IMAGEBLIT
1455 select FB_TILEBLITTING
1458 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1460 Driver for graphics boards with S3 Trio / S3 Virge chip.
1463 tristate "S3 Savage support"
1464 depends on FB && PCI && EXPERIMENTAL
1465 select FB_MODE_HELPERS
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1471 This driver supports notebooks and computers with S3 Savage PCI/AGP
1474 Say Y if you have such a graphics card.
1476 To compile this driver as a module, choose M here; the module
1477 will be called savagefb.
1479 config FB_SAVAGE_I2C
1480 bool "Enable DDC2 Support"
1481 depends on FB_SAVAGE
1484 This enables I2C support for S3 Savage Chipsets. This is used
1485 only for getting EDID information from the attached display
1486 allowing for robust video mode handling and switching.
1488 Because fbdev-2.6 requires that drivers must be able to
1489 independently validate video mode parameters, you should say Y
1492 config FB_SAVAGE_ACCEL
1493 bool "Enable Console Acceleration"
1494 depends on FB_SAVAGE
1497 This option will compile in console acceleration support. If
1498 the resulting framebuffer console has bothersome glitches, then
1502 tristate "SiS/XGI display support"
1503 depends on FB && PCI
1504 select FB_CFB_FILLRECT
1505 select FB_CFB_COPYAREA
1506 select FB_CFB_IMAGEBLIT
1507 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1509 This is the frame buffer device driver for the SiS 300, 315, 330
1510 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1511 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1513 To compile this driver as a module, choose M here; the module
1514 will be called sisfb.
1517 bool "SiS 300 series support"
1520 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1523 bool "SiS 315/330/340 series and XGI support"
1526 Say Y here to support use of the SiS 315, 330 and 340 series
1527 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1528 as XGI V3XT, V5, V8 and Z7.
1531 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1532 depends on FB && PCI && X86
1533 select FB_CFB_FILLRECT
1534 select FB_CFB_COPYAREA
1535 select FB_CFB_IMAGEBLIT
1540 This is the frame buffer device driver for Graphics chips of VIA
1541 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1542 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1544 Say Y if you have a VIA UniChrome graphics board.
1546 To compile this driver as a module, choose M here: the
1547 module will be called viafb.
1551 config FB_VIA_DIRECT_PROCFS
1552 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1556 Allow direct hardware access to some output registers via procfs.
1557 This is dangerous but may provide the only chance to get the
1558 correct output device configuration.
1559 Its use is strongly discouraged.
1564 tristate "NeoMagic display support"
1565 depends on FB && PCI
1566 select FB_MODE_HELPERS
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1572 This driver supports notebooks with NeoMagic PCI chips.
1573 Say Y if you have such a graphics card.
1575 To compile this driver as a module, choose M here: the
1576 module will be called neofb.
1579 tristate "IMG Kyro support"
1580 depends on FB && PCI
1581 select FB_CFB_FILLRECT
1582 select FB_CFB_COPYAREA
1583 select FB_CFB_IMAGEBLIT
1585 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1588 To compile this driver as a module, choose M here: the
1589 module will be called kyrofb.
1592 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1593 depends on FB && PCI
1594 select FB_CFB_IMAGEBLIT
1595 select FB_CFB_FILLRECT
1596 select FB_CFB_COPYAREA
1597 select FB_MODE_HELPERS
1599 This driver supports graphics boards with the 3Dfx Banshee,
1600 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1601 such a graphics board.
1603 To compile this driver as a module, choose M here: the
1604 module will be called tdfxfb.
1606 config FB_3DFX_ACCEL
1607 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1608 depends on FB_3DFX && EXPERIMENTAL
1610 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1611 device driver with acceleration functions.
1614 bool "Enable DDC/I2C support"
1615 depends on FB_3DFX && EXPERIMENTAL
1619 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1622 tristate "3Dfx Voodoo Graphics (sst1) support"
1623 depends on FB && PCI
1624 select FB_CFB_FILLRECT
1625 select FB_CFB_COPYAREA
1626 select FB_CFB_IMAGEBLIT
1628 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1629 Voodoo2 (cvg) based graphics card.
1631 To compile this driver as a module, choose M here: the
1632 module will be called sstfb.
1634 WARNING: Do not use any application that uses the 3D engine
1635 (namely glide) while using this driver.
1636 Please read the <file:Documentation/fb/sstfb.txt> for supported
1637 options and other important info support.
1640 tristate "VIA VT8623 support"
1641 depends on FB && PCI
1642 select FB_CFB_FILLRECT
1643 select FB_CFB_COPYAREA
1644 select FB_CFB_IMAGEBLIT
1645 select FB_TILEBLITTING
1648 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1650 Driver for CastleRock integrated graphics core in the
1651 VIA VT8623 [Apollo CLE266] chipset.
1654 tristate "Trident/CyberXXX/CyberBlade support"
1655 depends on FB && PCI
1656 select FB_CFB_FILLRECT
1657 select FB_CFB_COPYAREA
1658 select FB_CFB_IMAGEBLIT
1660 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1661 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1663 There are also integrated versions of these chips called CyberXXXX,
1664 CyberImage or CyberBlade. These chips are mostly found in laptops
1665 but also on some motherboards including early VIA EPIA motherboards.
1666 For more information, read <file:Documentation/fb/tridentfb.txt>
1668 Say Y if you have such a graphics board.
1670 To compile this driver as a module, choose M here: the
1671 module will be called tridentfb.
1674 tristate "ARK 2000PV support"
1675 depends on FB && PCI
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1679 select FB_TILEBLITTING
1682 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1684 Driver for PCI graphics boards with ARK 2000PV chip
1685 and ICS 5342 RAMDAC.
1688 tristate "Permedia3 support (EXPERIMENTAL)"
1689 depends on FB && PCI && EXPERIMENTAL
1690 select FB_CFB_FILLRECT
1691 select FB_CFB_COPYAREA
1692 select FB_CFB_IMAGEBLIT
1694 This is the frame buffer device driver for the 3DLabs Permedia3
1695 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1696 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1697 and maybe other boards.
1700 tristate "Fujitsu carmine frame buffer support"
1701 depends on FB && PCI
1702 select FB_CFB_FILLRECT
1703 select FB_CFB_COPYAREA
1704 select FB_CFB_IMAGEBLIT
1706 This is the frame buffer device driver for the Fujitsu Carmine chip.
1707 The driver provides two independent frame buffer devices.
1710 depends on FB_CARMINE
1711 prompt "DRAM timing"
1712 default FB_CARMINE_DRAM_EVAL
1714 config FB_CARMINE_DRAM_EVAL
1715 bool "Eval board timings"
1717 Use timings which work on the eval card.
1719 config CARMINE_DRAM_CUSTOM
1720 bool "Custom board timings"
1722 Use custom board timings.
1726 bool "Au1100 LCD Driver"
1727 depends on (FB = y) && MIPS && SOC_AU1100
1728 select FB_CFB_FILLRECT
1729 select FB_CFB_COPYAREA
1730 select FB_CFB_IMAGEBLIT
1732 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1733 various panels and CRTs by passing in kernel cmd line option
1734 au1100fb:panel=<name>.
1737 bool "Au1200 LCD Driver"
1738 depends on (FB = y) && MIPS && SOC_AU1200
1739 select FB_CFB_FILLRECT
1740 select FB_CFB_COPYAREA
1741 select FB_CFB_IMAGEBLIT
1743 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1744 various panels and CRTs by passing in kernel cmd line option
1745 au1200fb:panel=<name>.
1748 bool "VT8500 LCD Driver"
1749 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_VT8500
1750 select FB_WMT_GE_ROPS
1751 select FB_SYS_IMAGEBLIT
1753 This is the framebuffer driver for VIA VT8500 integrated LCD
1757 bool "WM8505 frame buffer support"
1758 depends on (FB = y) && ARM && ARCH_VT8500 && VTWM_VERSION_WM8505
1759 select FB_WMT_GE_ROPS
1760 select FB_SYS_IMAGEBLIT
1762 This is the framebuffer driver for WonderMedia WM8505
1763 integrated LCD controller.
1765 source "drivers/video/geode/Kconfig"
1768 tristate "HD64461 Frame Buffer support"
1769 depends on FB && HD64461
1770 select FB_CFB_FILLRECT
1771 select FB_CFB_COPYAREA
1772 select FB_CFB_IMAGEBLIT
1774 This is the frame buffer device driver for the Hitachi HD64461 LCD
1778 bool "PMAG-AA TURBOchannel framebuffer support"
1779 depends on (FB = y) && TC
1780 select FB_CFB_FILLRECT
1781 select FB_CFB_COPYAREA
1782 select FB_CFB_IMAGEBLIT
1784 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1785 used mainly in the MIPS-based DECstation series.
1788 tristate "PMAG-BA TURBOchannel framebuffer support"
1790 select FB_CFB_FILLRECT
1791 select FB_CFB_COPYAREA
1792 select FB_CFB_IMAGEBLIT
1794 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1795 used mainly in the MIPS-based DECstation series.
1798 tristate "PMAGB-B TURBOchannel framebuffer support"
1800 select FB_CFB_FILLRECT
1801 select FB_CFB_COPYAREA
1802 select FB_CFB_IMAGEBLIT
1804 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1805 in the MIPS-based DECstation series. The card is currently only
1806 supported in 1280x1024x8 mode.
1809 bool "Maxine (Personal DECstation) onboard framebuffer support"
1810 depends on (FB = y) && MACH_DECSTATION
1811 select FB_CFB_FILLRECT
1812 select FB_CFB_COPYAREA
1813 select FB_CFB_IMAGEBLIT
1815 Support for the onboard framebuffer (1024x768x8) in the Personal
1816 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1820 bool "G364 frame buffer support"
1821 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1822 select FB_CFB_FILLRECT
1823 select FB_CFB_COPYAREA
1824 select FB_CFB_IMAGEBLIT
1826 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1827 Olivetti M700-10 systems.
1830 bool "Motorola 68328 native frame buffer support"
1831 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1832 select FB_CFB_FILLRECT
1833 select FB_CFB_COPYAREA
1834 select FB_CFB_IMAGEBLIT
1836 Say Y here if you want to support the built-in frame buffer of
1837 the Motorola 68328 CPU family.
1840 tristate "PXA168/910 LCD framebuffer support"
1841 depends on FB && (CPU_PXA168 || CPU_PXA910)
1842 select FB_CFB_FILLRECT
1843 select FB_CFB_COPYAREA
1844 select FB_CFB_IMAGEBLIT
1846 Frame buffer driver for the built-in LCD controller in the Marvell
1850 tristate "PXA LCD framebuffer support"
1851 depends on FB && ARCH_PXA
1852 select FB_CFB_FILLRECT
1853 select FB_CFB_COPYAREA
1854 select FB_CFB_IMAGEBLIT
1856 Frame buffer driver for the built-in LCD controller in the Intel
1859 This driver is also available as a module ( = code which can be
1860 inserted and removed from the running kernel whenever you want). The
1861 module will be called pxafb. If you want to compile it as a module,
1862 say M here and read <file:Documentation/kbuild/modules.txt>.
1866 config FB_PXA_OVERLAY
1867 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1869 depends on FB_PXA && (PXA27x || PXA3xx)
1871 config FB_PXA_SMARTPANEL
1872 bool "PXA Smartpanel LCD support"
1876 config FB_PXA_PARAMETERS
1877 bool "PXA LCD command line parameters"
1881 Enable the use of kernel command line or module parameters
1882 to configure the physical properties of the LCD panel when
1883 using the PXA LCD driver.
1885 This option allows you to override the panel parameters
1886 supplied by the platform in order to support multiple
1887 different models of flatpanel. If you will only be using a
1888 single model of flatpanel then you can safely leave this
1891 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1894 tristate "2700G LCD framebuffer support"
1895 depends on FB && ARCH_PXA
1896 select FB_CFB_FILLRECT
1897 select FB_CFB_COPYAREA
1898 select FB_CFB_IMAGEBLIT
1900 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1904 bool "Enable debugging info via debugfs"
1905 depends on FB_MBX && DEBUG_FS
1908 Enable this if you want debugging information using the debug
1909 filesystem (debugfs)
1914 tristate "Freescale DIU framebuffer support"
1915 depends on FB && FSL_SOC
1916 select FB_MODE_HELPERS
1917 select FB_CFB_FILLRECT
1918 select FB_CFB_COPYAREA
1919 select FB_CFB_IMAGEBLIT
1920 select PPC_LIB_RHEAP
1922 Framebuffer driver for the Freescale SoC DIU
1925 tristate "W100 frame buffer support"
1926 depends on FB && ARCH_PXA
1927 select FB_CFB_FILLRECT
1928 select FB_CFB_COPYAREA
1929 select FB_CFB_IMAGEBLIT
1931 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1932 It can also drive the w3220 chip found on iPAQ hx4700.
1934 This driver is also available as a module ( = code which can be
1935 inserted and removed from the running kernel whenever you want). The
1936 module will be called w100fb. If you want to compile it as a module,
1937 say M here and read <file:Documentation/kbuild/modules.txt>.
1943 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1945 config SH_LCD_MIPI_DSI
1948 config FB_SH_MOBILE_LCDC
1949 tristate "SuperH Mobile LCDC framebuffer support"
1950 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1951 select FB_SYS_FILLRECT
1952 select FB_SYS_COPYAREA
1953 select FB_SYS_IMAGEBLIT
1955 select FB_DEFERRED_IO
1956 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1958 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1960 config FB_SH_MOBILE_HDMI
1961 tristate "SuperH Mobile HDMI controller support"
1962 depends on FB_SH_MOBILE_LCDC
1963 select FB_MODE_HELPERS
1968 Driver for the on-chip SH-Mobile HDMI controller.
1971 tristate "Toshiba Mobile IO FrameBuffer support"
1972 depends on FB && MFD_CORE
1973 select FB_CFB_FILLRECT
1974 select FB_CFB_COPYAREA
1975 select FB_CFB_IMAGEBLIT
1977 Frame buffer driver for the Toshiba Mobile IO integrated as found
1978 on the Sharp SL-6000 series
1980 This driver is also available as a module ( = code which can be
1981 inserted and removed from the running kernel whenever you want). The
1982 module will be called tmiofb. If you want to compile it as a module,
1983 say M here and read <file:Documentation/kbuild/modules.txt>.
1987 config FB_TMIO_ACCELL
1988 bool "tmiofb acceleration"
1993 tristate "Samsung S3C framebuffer support"
1994 depends on FB && S3C_DEV_FB
1995 select FB_CFB_FILLRECT
1996 select FB_CFB_COPYAREA
1997 select FB_CFB_IMAGEBLIT
1999 Frame buffer driver for the built-in FB controller in the Samsung
2000 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
2001 and the S3C64XX series such as the S3C6400 and S3C6410.
2003 These chips all have the same basic framebuffer design with the
2004 actual capabilities depending on the chip. For instance the S3C6400
2005 and S3C6410 support 4 hardware windows whereas the S3C24XX series
2006 currently only have two.
2008 Currently the support is only for the S3C6400 and S3C6410 SoCs.
2010 config FB_S3C_DEBUG_REGWRITE
2011 bool "Debug register writes"
2014 Show all register writes via printk(KERN_DEBUG)
2017 tristate "S3C2410 LCD framebuffer support"
2018 depends on FB && ARCH_S3C2410
2019 select FB_CFB_FILLRECT
2020 select FB_CFB_COPYAREA
2021 select FB_CFB_IMAGEBLIT
2023 Frame buffer driver for the built-in LCD controller in the Samsung
2026 This driver is also available as a module ( = code which can be
2027 inserted and removed from the running kernel whenever you want). The
2028 module will be called s3c2410fb. If you want to compile it as a module,
2029 say M here and read <file:Documentation/kbuild/modules.txt>.
2032 config FB_S3C2410_DEBUG
2033 bool "S3C2410 lcd debug messages"
2034 depends on FB_S3C2410
2036 Turn on debugging messages. Note that you can set/unset at run time
2040 bool "NUC900 LCD framebuffer support"
2041 depends on FB && ARCH_W90X900
2042 select FB_CFB_FILLRECT
2043 select FB_CFB_COPYAREA
2044 select FB_CFB_IMAGEBLIT
2046 Frame buffer driver for the built-in LCD controller in the Nuvoton
2049 config GPM1040A0_320X240
2050 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2051 depends on FB_NUC900
2053 config FB_NUC900_DEBUG
2054 bool "NUC900 lcd debug messages"
2055 depends on FB_NUC900
2057 Turn on debugging messages. Note that you can set/unset at run time
2061 tristate "Silicon Motion SM501 framebuffer support"
2062 depends on FB && MFD_SM501
2063 select FB_CFB_FILLRECT
2064 select FB_CFB_COPYAREA
2065 select FB_CFB_IMAGEBLIT
2067 Frame buffer driver for the CRT and LCD controllers in the Silicon
2070 This driver is also available as a module ( = code which can be
2071 inserted and removed from the running kernel whenever you want). The
2072 module will be called sm501fb. If you want to compile it as a module,
2073 say M here and read <file:Documentation/kbuild/modules.txt>.
2078 config FB_PNX4008_DUM
2079 tristate "Display Update Module support on Philips PNX4008 board"
2080 depends on FB && ARCH_PNX4008
2082 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2084 config FB_PNX4008_DUM_RGB
2085 tristate "RGB Framebuffer support on Philips PNX4008 board"
2086 depends on FB_PNX4008_DUM
2087 select FB_CFB_FILLRECT
2088 select FB_CFB_COPYAREA
2089 select FB_CFB_IMAGEBLIT
2091 Say Y here to enable support for PNX4008 RGB Framebuffer
2093 config FB_IBM_GXT4500
2094 tristate "Framebuffer support for IBM GXT4500P adaptor"
2095 depends on FB && PPC
2096 select FB_CFB_FILLRECT
2097 select FB_CFB_COPYAREA
2098 select FB_CFB_IMAGEBLIT
2100 Say Y here to enable support for the IBM GXT4500P display
2101 adaptor, found on some IBM System P (pSeries) machines.
2104 tristate "PS3 GPU framebuffer driver"
2105 depends on FB && PS3_PS3AV
2106 select FB_SYS_FILLRECT
2107 select FB_SYS_COPYAREA
2108 select FB_SYS_IMAGEBLIT
2110 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2112 Include support for the virtual frame buffer in the PS3 platform.
2114 config FB_PS3_DEFAULT_SIZE_M
2115 int "PS3 default frame buffer size (in MiB)"
2119 This is the default size (in MiB) of the virtual frame buffer in
2121 The default value can be overridden on the kernel command line
2122 using the "ps3fb" option (e.g. "ps3fb=9M");
2125 tristate "Xilinx frame buffer support"
2126 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2127 select FB_CFB_FILLRECT
2128 select FB_CFB_COPYAREA
2129 select FB_CFB_IMAGEBLIT
2131 Include support for the Xilinx ML300/ML403 reference design
2132 framebuffer. ML300 carries a 640*480 LCD display on the board,
2133 ML403 uses a standard DB15 VGA connector.
2136 tristate "Cobalt server LCD frame buffer support"
2137 depends on FB && MIPS_COBALT
2140 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2141 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2142 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2143 select FB_CFB_FILLRECT
2144 select FB_CFB_COPYAREA
2145 select FB_CFB_IMAGEBLIT
2147 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2148 (D)STN/TFT LCD Controller.
2149 Supports display resolutions up to 1024x1024 pixel, grayscale and
2150 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2151 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2152 panels <= 320 pixel horizontal resolution.
2155 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2156 depends on FB && ARCH_DAVINCI_DA8XX
2157 select FB_CFB_FILLRECT
2158 select FB_CFB_COPYAREA
2159 select FB_CFB_IMAGEBLIT
2161 This is the frame buffer device driver for the TI LCD controller
2162 found on DA8xx/OMAP-L1xx SoCs.
2166 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2168 select FB_SYS_FILLRECT
2169 select FB_SYS_COPYAREA
2170 select FB_SYS_IMAGEBLIT
2173 This is a `virtual' frame buffer device. It operates on a chunk of
2174 unswappable kernel memory instead of on the memory of a graphics
2175 board. This means you cannot see any output sent to this frame
2176 buffer device, while it does consume precious memory. The main use
2177 of this frame buffer device is testing and debugging the frame
2178 buffer subsystem. Do NOT enable it for normal systems! To protect
2179 the innocent, it has to be enabled explicitly at boot time using the
2180 kernel option `video=vfb:'.
2182 To compile this driver as a module, choose M here: the
2183 module will be called vfb. In order to load it, you must use
2184 the vfb_enable=1 option.
2188 config XEN_FBDEV_FRONTEND
2189 tristate "Xen virtual frame buffer support"
2190 depends on FB && XEN
2191 select FB_SYS_FILLRECT
2192 select FB_SYS_COPYAREA
2193 select FB_SYS_IMAGEBLIT
2195 select FB_DEFERRED_IO
2196 select XEN_XENBUS_FRONTEND
2199 This driver implements the front-end of the Xen virtual
2200 frame buffer driver. It communicates with a back-end
2204 tristate "E-Ink Metronome/8track controller support"
2206 select FB_SYS_FILLRECT
2207 select FB_SYS_COPYAREA
2208 select FB_SYS_IMAGEBLIT
2210 select FB_DEFERRED_IO
2212 This driver implements support for the E-Ink Metronome
2213 controller. The pre-release name for this device was 8track
2214 and could also have been called by some vendors as PVI-nnnn.
2217 tristate "Fujitsu MB862xx GDC support"
2219 select FB_CFB_FILLRECT
2220 select FB_CFB_COPYAREA
2221 select FB_CFB_IMAGEBLIT
2223 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2225 config FB_MB862XX_PCI_GDC
2226 bool "Carmine/Coral-P(A) GDC"
2227 depends on PCI && FB_MB862XX
2229 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2230 PCI graphics controller devices.
2232 config FB_MB862XX_LIME
2234 depends on FB_MB862XX
2235 depends on OF && !FB_MB862XX_PCI_GDC
2237 select FB_FOREIGN_ENDIAN
2238 select FB_LITTLE_ENDIAN
2240 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2243 tristate "EP93XX frame buffer support"
2244 depends on FB && ARCH_EP93XX
2245 select FB_CFB_FILLRECT
2246 select FB_CFB_COPYAREA
2247 select FB_CFB_IMAGEBLIT
2249 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2250 This driver is also available as a module. The module will be called
2253 config FB_PRE_INIT_FB
2254 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2255 depends on FB && FB_MB862XX_LIME
2257 Select this option if display contents should be inherited as set by
2261 tristate "MSM Framebuffer support"
2262 depends on FB && ARCH_MSM
2263 select FB_CFB_FILLRECT
2264 select FB_CFB_COPYAREA
2265 select FB_CFB_IMAGEBLIT
2268 tristate "MX3 Framebuffer support"
2269 depends on FB && MX3_IPU
2270 select FB_CFB_FILLRECT
2271 select FB_CFB_COPYAREA
2272 select FB_CFB_IMAGEBLIT
2275 This is a framebuffer device for the i.MX31 LCD Controller. So
2276 far only synchronous displays are supported. If you plan to use
2277 an LCD display with your i.MX31 system, say Y here.
2279 config FB_BROADSHEET
2280 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2282 select FB_SYS_FILLRECT
2283 select FB_SYS_COPYAREA
2284 select FB_SYS_IMAGEBLIT
2286 select FB_DEFERRED_IO
2288 This driver implements support for the E-Ink Broadsheet
2289 controller. The release name for this device was Epson S1D13521
2290 and could also have been called by other names when coupled with
2294 tristate "JZ4740 LCD framebuffer support"
2295 depends on FB && MACH_JZ4740
2296 select FB_SYS_FILLRECT
2297 select FB_SYS_COPYAREA
2298 select FB_SYS_IMAGEBLIT
2300 Framebuffer support for the JZ4740 SoC.
2302 source "drivers/video/omap/Kconfig"
2303 source "drivers/video/omap2/Kconfig"
2305 source "drivers/video/backlight/Kconfig"
2306 source "drivers/video/display/Kconfig"
2309 source "drivers/video/console/Kconfig"
2312 if FB || SGI_NEWPORT_CONSOLE
2313 source "drivers/video/logo/Kconfig"