5 menu "Graphics support"
14 source "drivers/char/agp/Kconfig"
16 source "drivers/gpu/vga/Kconfig"
18 source "drivers/gpu/drm/Kconfig"
24 config VIDEO_OUTPUT_CONTROL
25 tristate "Lowlevel video output switch controls"
27 This framework adds support for low-level control of the video
31 tristate "Support for frame buffer devices"
33 The frame buffer device provides an abstraction for the graphics
34 hardware. It represents the frame buffer of some video hardware and
35 allows application software to access the graphics hardware through
36 a well-defined interface, so the software doesn't need to know
37 anything about the low-level (hardware register) stuff.
39 Frame buffer devices work identically across the different
40 architectures supported by Linux and make the implementation of
41 application programs easier and more portable; at this point, an X
42 server exists which uses the frame buffer device exclusively.
43 On several non-X86 architectures, the frame buffer device is the
44 only way to use the graphics hardware.
46 The device is accessed through special device nodes, usually located
47 in the /dev directory, i.e. /dev/fb*.
49 You need an utility program called fbset to make full use of frame
50 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
51 and the Framebuffer-HOWTO at
52 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more
55 Say Y here and to the driver for your graphics board below if you
56 are compiling a kernel for a non-x86 architecture.
58 If you are compiling for the x86 architecture, you can say Y if you
59 want to play with it, but it is not essential. Please note that
60 running graphical applications that directly touch the hardware
61 (e.g. an accelerated X server) and that are not frame buffer
62 device-aware may cause unexpected results. If unsure, say N.
65 bool "Enable firmware EDID"
69 This enables access to the EDID transferred from the firmware.
70 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
71 transfers do not work for your driver and if you are using
72 nvidiafb, i810fb or savagefb.
74 In general, choosing Y for this option is safe. If you
75 experience extremely long delays while booting before you get
76 something on your display, try setting this to N. Matrox cards in
77 combination with certain motherboards and monitors are known to
78 suffer from this problem.
87 config FB_BOOT_VESA_SUPPORT
92 If true, at least one selected framebuffer driver can take advantage
93 of VESA video modes set at an early boot stage via the vga= parameter.
95 config FB_CFB_FILLRECT
100 Include the cfb_fillrect function for generic software rectangle
101 filling. This is used by drivers that don't provide their own
102 (accelerated) version.
104 config FB_CFB_COPYAREA
109 Include the cfb_copyarea function for generic software area copying.
110 This is used by drivers that don't provide their own (accelerated)
113 config FB_CFB_IMAGEBLIT
118 Include the cfb_imageblit function for generic software image
119 blitting. This is used by drivers that don't provide their own
120 (accelerated) version.
122 config FB_CFB_REV_PIXELS_IN_BYTE
127 Allow generic frame-buffer functions to work on displays with 1, 2
128 and 4 bits per pixel depths which has opposite order of pixels in
129 byte order to bytes in long order.
131 config FB_SYS_FILLRECT
136 Include the sys_fillrect function for generic software rectangle
137 filling. This is used by drivers that don't provide their own
138 (accelerated) version and the framebuffer is in system RAM.
140 config FB_SYS_COPYAREA
145 Include the sys_copyarea function for generic software area copying.
146 This is used by drivers that don't provide their own (accelerated)
147 version and the framebuffer is in system RAM.
149 config FB_SYS_IMAGEBLIT
154 Include the sys_imageblit function for generic software image
155 blitting. This is used by drivers that don't provide their own
156 (accelerated) version and the framebuffer is in system RAM.
159 tristate "Font drawing support"
163 draw text on framebuffer.
166 tristate "Log panic/oops to framebuffer"
168 This enables panic and oops messages to be logged to framebuffer.
170 menuconfig FB_FOREIGN_ENDIAN
171 bool "Framebuffer foreign endianness support"
174 This menu will let you enable support for the framebuffers with
175 non-native endianness (e.g. Little-Endian framebuffer on a
176 Big-Endian machine). Most probably you don't have such hardware,
177 so it's safe to say "n" here.
180 prompt "Choice endianness support"
181 depends on FB_FOREIGN_ENDIAN
183 config FB_BOTH_ENDIAN
184 bool "Support for Big- and Little-Endian framebuffers"
187 bool "Support for Big-Endian framebuffers only"
189 config FB_LITTLE_ENDIAN
190 bool "Support for Little-Endian framebuffers only"
199 config FB_DEFERRED_IO
206 depends on FB_DEFERRED_IO
213 Common utility functions useful to fbdev drivers of VGA-based
224 select BACKLIGHT_LCD_SUPPORT
225 select BACKLIGHT_CLASS_DEVICE
228 config FB_MODE_HELPERS
229 bool "Enable Video Mode Handling Helpers"
233 This enables functions for handling video modes using the
234 Generalized Timing Formula and the EDID parser. A few drivers rely
235 on this feature such as the radeonfb, rivafb, and the i810fb. If
236 your driver does not take advantage of this feature, choosing Y will
237 just increase the kernel size by about 5K.
239 config FB_TILEBLITTING
240 bool "Enable Tile Blitting Support"
244 This enables tile blitting. Tile blitting is a drawing technique
245 where the screen is divided into rectangular sections (tiles), whereas
246 the standard blitting divides the screen into pixels. Because the
247 default drawing element is a tile, drawing functions will be passed
248 parameters in terms of number of tiles instead of number of pixels.
249 For example, to draw a single character, instead of using bitmaps,
250 an index to an array of bitmaps will be used. To clear or move a
251 rectangular section of a screen, the rectangle will be described in
252 terms of number of tiles in the x- and y-axis.
254 This is particularly important to one driver, matroxfb. If
257 comment "Frame buffer hardware drivers"
260 source "drivers/video/samsung/Kconfig"
263 tristate "Cirrus Logic support"
264 depends on FB && (ZORRO || PCI)
265 select FB_CFB_FILLRECT
266 select FB_CFB_COPYAREA
267 select FB_CFB_IMAGEBLIT
269 This enables support for Cirrus Logic GD542x/543x based boards on
270 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
272 If you have a PCI-based system, this enables support for these
273 chips: GD-543x, GD-544x, GD-5480.
275 Please read the file <file:Documentation/fb/cirrusfb.txt>.
277 Say N unless you have such a graphics board or plan to get one
278 before you next recompile the kernel.
281 tristate "Permedia2 support"
282 depends on FB && ((AMIGA && BROKEN) || PCI)
283 select FB_CFB_FILLRECT
284 select FB_CFB_COPYAREA
285 select FB_CFB_IMAGEBLIT
287 This is the frame buffer device driver for cards based on
288 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
289 The driver was tested on the following cards:
290 Diamond FireGL 1000 PRO AGP
291 ELSA Gloria Synergy PCI
292 Appian Jeronimo PRO (both heads) PCI
293 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
294 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
295 ASK Graphic Blaster Exxtreme AGP
297 To compile this driver as a module, choose M here: the
298 module will be called pm2fb.
300 config FB_PM2_FIFO_DISCONNECT
301 bool "enable FIFO disconnect feature"
302 depends on FB_PM2 && PCI
304 Support the Permedia2 FIFO disconnect feature.
307 tristate "ARM PrimeCell PL110 support"
308 depends on FB && ARM && ARM_AMBA
309 select FB_CFB_FILLRECT
310 select FB_CFB_COPYAREA
311 select FB_CFB_IMAGEBLIT
313 This framebuffer device driver is for the ARM PrimeCell PL110
314 Colour LCD controller. ARM PrimeCells provide the building
315 blocks for System on a Chip devices.
317 If you want to compile this as a module (=code which can be
318 inserted into and removed from the running kernel), say M
319 here and read <file:Documentation/kbuild/modules.txt>. The module
320 will be called amba-clcd.
324 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
326 default FB_ARMCLCD_SHARP_LQ035Q7DB02
328 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
329 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
331 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
332 color QVGA, HRTFT panel. The LogicPD device includes
333 an integrated HRTFT controller IC.
334 The native resolution is 240x320.
336 config FB_ARMCLCD_SHARP_LQ057Q3DC02
337 bool "LogicPD LCD 5.7\" QVGA"
339 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
340 color QVGA, TFT panel. The LogicPD device includes an
341 The native resolution is 320x240.
343 config FB_ARMCLCD_SHARP_LQ64D343
344 bool "LogicPD LCD 6.4\" VGA"
346 This is an implementation of the Sharp LQ64D343, a 6.4"
347 color VGA, TFT panel. The LogicPD device includes an
348 The native resolution is 640x480.
350 config FB_ARMCLCD_SHARP_LQ10D368
351 bool "LogicPD LCD 10.4\" VGA"
353 This is an implementation of the Sharp LQ10D368, a 10.4"
354 color VGA, TFT panel. The LogicPD device includes an
355 The native resolution is 640x480.
358 config FB_ARMCLCD_SHARP_LQ121S1DG41
359 bool "LogicPD LCD 12.1\" SVGA"
361 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
362 color SVGA, TFT panel. The LogicPD device includes an
363 The native resolution is 800x600.
365 This panel requires a clock rate may be an integer fraction
366 of the base LCDCLK frequency. The driver will select the
367 highest frequency available that is lower than the maximum
368 allowed. The panel may flicker if the clock rate is
369 slower than the recommended minimum.
371 config FB_ARMCLCD_AUO_A070VW01_WIDE
372 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
374 This is an implementation of the AU Optronics, a 7.0"
375 WIDE Color. The native resolution is 234x480.
377 config FB_ARMCLCD_HITACHI
378 bool "Hitachi Wide Screen 800x480"
380 This is an implementation of the Hitachi 800x480.
386 bool "Acorn VIDC support"
387 depends on (FB = y) && ARM && ARCH_ACORN
388 select FB_CFB_FILLRECT
389 select FB_CFB_COPYAREA
390 select FB_CFB_IMAGEBLIT
392 This is the frame buffer device driver for the Acorn VIDC graphics
393 hardware found in Acorn RISC PCs and other ARM-based machines. If
397 bool "CLPS711X LCD support"
398 depends on (FB = y) && ARM && ARCH_CLPS711X
399 select FB_CFB_FILLRECT
400 select FB_CFB_COPYAREA
401 select FB_CFB_IMAGEBLIT
403 Say Y to enable the Framebuffer driver for the CLPS7111 and
407 bool "SA-1100 LCD support"
408 depends on (FB = y) && ARM && ARCH_SA1100
409 select FB_CFB_FILLRECT
410 select FB_CFB_COPYAREA
411 select FB_CFB_IMAGEBLIT
413 This is a framebuffer device for the SA-1100 LCD Controller.
414 See <http://www.linux-fbdev.org/> for information on framebuffer
417 If you plan to use the LCD display with your SA-1100 system, say
421 tristate "Motorola i.MX LCD support"
422 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
423 select FB_CFB_FILLRECT
424 select FB_CFB_COPYAREA
425 select FB_CFB_IMAGEBLIT
428 tristate "CyberPro 2000/2010/5000 support"
429 depends on FB && PCI && (BROKEN || !SPARC64)
430 select FB_CFB_FILLRECT
431 select FB_CFB_COPYAREA
432 select FB_CFB_IMAGEBLIT
434 This enables support for the Integraphics CyberPro 20x0 and 5000
435 VGA chips used in the Rebel.com Netwinder and other machines.
436 Say Y if you have a NetWinder or a graphics card containing this
437 device, otherwise say N.
441 depends on (FB = y) && APOLLO
443 select FB_CFB_FILLRECT
444 select FB_CFB_IMAGEBLIT
448 depends on (FB = y) && Q40
450 select FB_CFB_FILLRECT
451 select FB_CFB_COPYAREA
452 select FB_CFB_IMAGEBLIT
455 tristate "Amiga native chipset support"
456 depends on FB && AMIGA
458 This is the frame buffer device driver for the builtin graphics
459 chipset found in Amigas.
461 To compile this driver as a module, choose M here: the
462 module will be called amifb.
465 bool "Amiga OCS chipset support"
468 This enables support for the original Agnus and Denise video chips,
469 found in the Amiga 1000 and most A500's and A2000's. If you intend
470 to run Linux on any of these systems, say Y; otherwise say N.
473 bool "Amiga ECS chipset support"
476 This enables support for the Enhanced Chip Set, found in later
477 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
478 you intend to run Linux on any of these systems, say Y; otherwise
482 bool "Amiga AGA chipset support"
485 This enables support for the Advanced Graphics Architecture (also
486 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
487 and CD32. If you intend to run Linux on any of these systems, say Y;
491 bool "Amiga FrameMaster II/Rainbow II support"
492 depends on (FB = y) && ZORRO
493 select FB_CFB_FILLRECT
494 select FB_CFB_COPYAREA
495 select FB_CFB_IMAGEBLIT
497 This is the frame buffer device driver for the Amiga FrameMaster
498 card from BSC (exhibited 1992 but not shipped as a CBM product).
501 tristate "Arc Monochrome LCD board support"
503 select FB_SYS_FILLRECT
504 select FB_SYS_COPYAREA
505 select FB_SYS_IMAGEBLIT
508 This enables support for the Arc Monochrome LCD board. The board
509 is based on the KS-108 lcd controller and is typically a matrix
510 of 2*n chips. This driver was tested with a 128x64 panel. This
511 driver supports it for use with x86 SBCs through a 16 bit GPIO
512 interface (8 bit data, 8 bit control). If you anticipate using
513 this driver, say Y or M; otherwise say N. You must specify the
514 GPIO IO address to be used for setting control and data.
517 bool "Atari native chipset support"
518 depends on (FB = y) && ATARI
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
523 This is the frame buffer device driver for the builtin graphics
524 chipset found in Ataris.
527 bool "Open Firmware frame buffer device support"
528 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
529 select FB_CFB_FILLRECT
530 select FB_CFB_COPYAREA
531 select FB_CFB_IMAGEBLIT
534 Say Y if you want support with Open Firmware for your graphics
538 bool "Apple \"control\" display support"
539 depends on (FB = y) && PPC_PMAC && PPC32
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
545 This driver supports a frame buffer for the graphics adapter in the
546 Power Macintosh 7300 and others.
549 bool "Apple \"platinum\" display support"
550 depends on (FB = y) && PPC_PMAC && PPC32
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
556 This driver supports a frame buffer for the "platinum" graphics
557 adapter in some Power Macintoshes.
560 bool "Apple \"valkyrie\" display support"
561 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
567 This driver supports a frame buffer for the "valkyrie" graphics
568 adapter in some Power Macintoshes.
571 bool "Chips 65550 display support"
572 depends on (FB = y) && PPC32 && PCI
573 select FB_CFB_FILLRECT
574 select FB_CFB_COPYAREA
575 select FB_CFB_IMAGEBLIT
577 This is the frame buffer device driver for the Chips & Technologies
578 65550 graphics chip in PowerBooks.
581 bool "Asiliant (Chips) 69000 display support"
582 depends on (FB = y) && PCI
583 select FB_CFB_FILLRECT
584 select FB_CFB_COPYAREA
585 select FB_CFB_IMAGEBLIT
587 This is the frame buffer device driver for the Asiliant 69030 chipset
590 bool "IMS Twin Turbo display support"
591 depends on (FB = y) && PCI
592 select FB_CFB_IMAGEBLIT
593 select FB_MACMODES if PPC
595 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
596 many Macintosh and compatible computers.
599 tristate "VGA 16-color graphics support"
600 depends on FB && (X86 || PPC)
601 select FB_CFB_FILLRECT
602 select FB_CFB_COPYAREA
603 select FB_CFB_IMAGEBLIT
605 select FONT_8x16 if FRAMEBUFFER_CONSOLE
607 This is the frame buffer device driver for VGA 16 color graphic
608 cards. Say Y if you have such a card.
610 To compile this driver as a module, choose M here: the
611 module will be called vga16fb.
613 config FB_BF54X_LQ043
614 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
615 depends on FB && (BF54x) && !BF542
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
620 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
622 config FB_BFIN_T350MCQB
623 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
624 depends on FB && BLACKFIN
626 select FB_CFB_FILLRECT
627 select FB_CFB_COPYAREA
628 select FB_CFB_IMAGEBLIT
630 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
631 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
632 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
634 config FB_BFIN_LQ035Q1
635 tristate "SHARP LQ035Q1DH02 TFT LCD"
636 depends on FB && BLACKFIN && SPI
637 select FB_CFB_FILLRECT
638 select FB_CFB_COPYAREA
639 select FB_CFB_IMAGEBLIT
642 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
643 the Blackfin Landscape LCD EZ-Extender Card.
644 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
645 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
647 To compile this driver as a module, choose M here: the
648 module will be called bfin-lq035q1-fb.
651 tristate "HP STI frame buffer device support"
652 depends on FB && PARISC
653 select FB_CFB_FILLRECT
654 select FB_CFB_COPYAREA
655 select FB_CFB_IMAGEBLIT
660 STI refers to the HP "Standard Text Interface" which is a set of
661 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
662 Enabling this option will implement the linux framebuffer device
663 using calls to the STI BIOS routines for initialisation.
665 If you enable this option, you will get a planar framebuffer device
666 /dev/fb which will work on the most common HP graphic cards of the
667 NGLE family, including the artist chips (in the 7xx and Bxxx series),
668 HCRX, HCRX24, CRX, CRX24 and VisEG series.
670 It is safe to enable this option, so you should probably say "Y".
673 bool "Generic Macintosh display support"
674 depends on (FB = y) && MAC
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
682 depends on (FB = y) && DIO
683 select FB_CFB_IMAGEBLIT
687 tristate "TGA/SFB+ framebuffer support"
688 depends on FB && (ALPHA || TC)
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
694 This is the frame buffer device driver for generic TGA and SFB+
695 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
696 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
697 TURBOchannel cards, also known as PMAGD-A, -B and -C.
699 Due to hardware limitations ZLX-E2 and E3 cards are not supported
700 for DECstation 5000/200 systems. Additionally due to firmware
701 limitations these cards may cause troubles with booting DECstation
702 5000/240 and /260 systems, but are fully supported under Linux if
703 you manage to get it going. ;-)
705 Say Y if you have one of those.
708 tristate "Userspace VESA VGA graphics support"
709 depends on FB && CONNECTOR
710 select FB_CFB_FILLRECT
711 select FB_CFB_COPYAREA
712 select FB_CFB_IMAGEBLIT
713 select FB_MODE_HELPERS
715 This is the frame buffer driver for generic VBE 2.0 compliant
716 graphic cards. It can also take advantage of VBE 3.0 features,
717 such as refresh rate adjustment.
719 This driver generally provides more features than vesafb but
720 requires a userspace helper application called 'v86d'. See
721 <file:Documentation/fb/uvesafb.txt> for more information.
726 bool "VESA VGA graphics support"
727 depends on (FB = y) && X86
728 select FB_CFB_FILLRECT
729 select FB_CFB_COPYAREA
730 select FB_CFB_IMAGEBLIT
731 select FB_BOOT_VESA_SUPPORT
733 This is the frame buffer device driver for generic VESA 2.0
734 compliant graphic cards. The older VESA 1.2 cards are not supported.
735 You will get a boot time penguin logo at no additional cost. Please
736 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
739 bool "EFI-based Framebuffer Support"
740 depends on (FB = y) && X86 && EFI
741 select FB_CFB_FILLRECT
742 select FB_CFB_COPYAREA
743 select FB_CFB_IMAGEBLIT
745 This is the EFI frame buffer device driver. If the firmware on
746 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
747 using the EFI framebuffer as your console.
750 tristate "N411 Apollo/Hecuba devkit support"
751 depends on FB && X86 && MMU
752 select FB_SYS_FILLRECT
753 select FB_SYS_COPYAREA
754 select FB_SYS_IMAGEBLIT
756 select FB_DEFERRED_IO
759 This enables support for the Apollo display controller in its
760 Hecuba form using the n411 devkit.
763 tristate "Hercules mono graphics support"
765 select FB_CFB_FILLRECT
766 select FB_CFB_COPYAREA
767 select FB_CFB_IMAGEBLIT
769 Say Y here if you have a Hercules mono graphics card.
771 To compile this driver as a module, choose M here: the
772 module will be called hgafb.
774 As this card technology is 15 years old, most people will answer N
778 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
779 depends on FB_HGA && EXPERIMENTAL
781 This will compile the Hercules mono graphics with
782 acceleration functions.
785 tristate "SGI Visual Workstation framebuffer support"
786 depends on FB && X86_VISWS
787 select FB_CFB_FILLRECT
788 select FB_CFB_COPYAREA
789 select FB_CFB_IMAGEBLIT
791 SGI Visual Workstation support for framebuffer graphics.
794 bool "SGI Graphics Backend frame buffer support"
795 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
796 select FB_CFB_FILLRECT
797 select FB_CFB_COPYAREA
798 select FB_CFB_IMAGEBLIT
800 This is the frame buffer device driver for SGI Graphics Backend.
801 This chip is used in SGI O2 and Visual Workstation 320/540.
804 int "Video memory size in MB"
808 This is the amount of memory reserved for the framebuffer,
809 which can be any value between 1MB and 8MB.
812 bool "SBUS and UPA framebuffers"
813 depends on (FB = y) && SPARC
815 Say Y if you want support for SBUS or UPA based frame buffer device.
819 depends on (FB = y) && (SPARC && FB_SBUS)
820 select FB_CFB_FILLRECT
821 select FB_CFB_COPYAREA
822 select FB_CFB_IMAGEBLIT
824 This is the frame buffer device driver for the BWtwo frame buffer.
827 bool "CGthree support"
828 depends on (FB = y) && (SPARC && FB_SBUS)
829 select FB_CFB_FILLRECT
830 select FB_CFB_COPYAREA
831 select FB_CFB_IMAGEBLIT
833 This is the frame buffer device driver for the CGthree frame buffer.
836 bool "CGsix (GX,TurboGX) support"
837 depends on (FB = y) && (SPARC && FB_SBUS)
838 select FB_CFB_COPYAREA
839 select FB_CFB_IMAGEBLIT
841 This is the frame buffer device driver for the CGsix (GX, TurboGX)
845 bool "Creator/Creator3D/Elite3D support"
846 depends on FB_SBUS && SPARC64
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This is the frame buffer device driver for the Creator, Creator3D,
851 and Elite3D graphics boards.
854 bool "TCX (SS4/SS5 only) support"
856 select FB_CFB_FILLRECT
857 select FB_CFB_COPYAREA
858 select FB_CFB_IMAGEBLIT
860 This is the frame buffer device driver for the TCX 24/8bit frame
864 bool "CGfourteen (SX) 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 CGfourteen frame
871 buffer on Desktop SPARCsystems with the SX graphics option.
874 bool "P9100 (Sparcbook 3 only) 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 P9100 card
881 supported on Sparcbook 3 machines.
884 bool "Leo (ZX) 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 SBUS-based Sun ZX
891 (leo) frame buffer cards.
894 bool "IGA 168x display support"
895 depends on (FB = y) && SPARC32
896 select FB_CFB_FILLRECT
897 select FB_CFB_COPYAREA
898 select FB_CFB_IMAGEBLIT
900 This is the framebuffer device for the INTERGRAPHICS 1680 and
901 successor frame buffer cards.
904 bool "Sun XVR-500 3DLABS Wildcat support"
905 depends on (FB = y) && PCI && SPARC64
906 select FB_CFB_FILLRECT
907 select FB_CFB_COPYAREA
908 select FB_CFB_IMAGEBLIT
910 This is the framebuffer device for the Sun XVR-500 and similar
911 graphics cards based upon the 3DLABS Wildcat chipset. The driver
912 only works on sparc64 systems where the system firmware has
913 mostly initialized the card already. It is treated as a
914 completely dumb framebuffer device.
917 bool "Sun XVR-2500 3DLABS Wildcat support"
918 depends on (FB = y) && PCI && SPARC64
919 select FB_CFB_FILLRECT
920 select FB_CFB_COPYAREA
921 select FB_CFB_IMAGEBLIT
923 This is the framebuffer device for the Sun XVR-2500 and similar
924 graphics cards based upon the 3DLABS Wildcat chipset. The driver
925 only works on sparc64 systems where the system firmware has
926 mostly initialized the card already. It is treated as a
927 completely dumb framebuffer device.
930 bool "Sun XVR-1000 support"
931 depends on (FB = y) && SPARC64
932 select FB_CFB_FILLRECT
933 select FB_CFB_COPYAREA
934 select FB_CFB_IMAGEBLIT
936 This is the framebuffer device for the Sun XVR-1000 and similar
937 graphics cards. The driver only works on sparc64 systems where
938 the system firmware has mostly initialized the card already. It
939 is treated as a completely dumb framebuffer device.
942 tristate "NEC PowerVR 2 display support"
943 depends on FB && SH_DREAMCAST
944 select FB_CFB_FILLRECT
945 select FB_CFB_COPYAREA
946 select FB_CFB_IMAGEBLIT
948 Say Y here if you have a PowerVR 2 card in your box. If you plan to
949 run linux on your Dreamcast, you will have to say Y here.
950 This driver may or may not work on other PowerVR 2 cards, but is
951 totally untested. Use at your own risk. If unsure, say N.
953 To compile this driver as a module, choose M here: the
954 module will be called pvr2fb.
956 You can pass several parameters to the driver at boot time or at
957 module load time. The parameters look like "video=pvr2:XXX", where
958 the meaning of XXX can be found at the end of the main source file
959 (<file:drivers/video/pvr2fb.c>). Please see the file
960 <file:Documentation/fb/pvr2fb.txt>.
963 bool "Epson 1355 framebuffer support"
964 depends on (FB = y) && ARCH_CEIVA
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
969 Build in support for the SED1355 Epson Research Embedded RAMDAC
970 LCD/CRT Controller (since redesignated as the S1D13505) as a
971 framebuffer. Product specs at
972 <http://www.erd.epson.com/vdc/html/products.htm>.
975 tristate "Epson S1D13XXX framebuffer support"
977 select FB_CFB_FILLRECT
978 select FB_CFB_COPYAREA
979 select FB_CFB_IMAGEBLIT
981 Support for S1D13XXX framebuffer device family (currently only
982 working with S1D13806). Product specs at
983 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
986 tristate "AT91/AT32 LCD Controller support"
987 depends on FB && HAVE_FB_ATMEL
988 select FB_CFB_FILLRECT
989 select FB_CFB_COPYAREA
990 select FB_CFB_IMAGEBLIT
992 This enables support for the AT91/AT32 LCD Controller.
995 bool "Frame Buffer in internal SRAM"
996 depends on FB_ATMEL && ARCH_AT91SAM9261
998 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
999 to let frame buffer in external SDRAM.
1002 bool "Use a STN display with AT91/AT32 LCD Controller"
1003 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
1006 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
1007 Controller. Say N if you want to connect a TFT.
1012 tristate "nVidia Framebuffer Support"
1013 depends on FB && PCI
1014 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1015 select FB_MODE_HELPERS
1016 select FB_CFB_FILLRECT
1017 select FB_CFB_COPYAREA
1018 select FB_CFB_IMAGEBLIT
1022 This driver supports graphics boards with the nVidia chips, TNT
1023 and newer. For very old chipsets, such as the RIVA128, then use
1025 Say Y if you have such a graphics board.
1027 To compile this driver as a module, choose M here: the
1028 module will be called nvidiafb.
1030 config FB_NVIDIA_I2C
1031 bool "Enable DDC Support"
1032 depends on FB_NVIDIA
1035 This enables I2C support for nVidia Chipsets. This is used
1036 only for getting EDID information from the attached display
1037 allowing for robust video mode handling and switching.
1039 Because fbdev-2.6 requires that drivers must be able to
1040 independently validate video mode parameters, you should say Y
1043 config FB_NVIDIA_DEBUG
1044 bool "Lots of debug output"
1045 depends on FB_NVIDIA
1048 Say Y here if you want the nVidia driver to output all sorts
1049 of debugging information to provide to the maintainer when
1050 something goes wrong.
1052 config FB_NVIDIA_BACKLIGHT
1053 bool "Support for backlight control"
1054 depends on FB_NVIDIA
1057 Say Y here if you want to control the backlight of your display.
1060 tristate "nVidia Riva support"
1061 depends on FB && PCI
1062 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1063 select FB_MODE_HELPERS
1064 select FB_CFB_FILLRECT
1065 select FB_CFB_COPYAREA
1066 select FB_CFB_IMAGEBLIT
1070 This driver supports graphics boards with the nVidia Riva/Geforce
1072 Say Y if you have such a graphics board.
1074 To compile this driver as a module, choose M here: the
1075 module will be called rivafb.
1078 bool "Enable DDC Support"
1082 This enables I2C support for nVidia Chipsets. This is used
1083 only for getting EDID information from the attached display
1084 allowing for robust video mode handling and switching.
1086 Because fbdev-2.6 requires that drivers must be able to
1087 independently validate video mode parameters, you should say Y
1090 config FB_RIVA_DEBUG
1091 bool "Lots of debug output"
1095 Say Y here if you want the Riva driver to output all sorts
1096 of debugging information to provide to the maintainer when
1097 something goes wrong.
1099 config FB_RIVA_BACKLIGHT
1100 bool "Support for backlight control"
1104 Say Y here if you want to control the backlight of your display.
1107 tristate "Intel 810/815 support (EXPERIMENTAL)"
1108 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1109 select FB_MODE_HELPERS
1110 select FB_CFB_FILLRECT
1111 select FB_CFB_COPYAREA
1112 select FB_CFB_IMAGEBLIT
1115 This driver supports the on-board graphics built in to the Intel 810
1116 and 815 chipsets. Say Y if you have and plan to use such a board.
1118 To compile this driver as a module, choose M here: the
1119 module will be called i810fb.
1121 For more information, please read
1122 <file:Documentation/fb/intel810.txt>
1125 bool "use VESA Generalized Timing Formula"
1128 If you say Y, then the VESA standard, Generalized Timing Formula
1129 or GTF, will be used to calculate the required video timing values
1130 per video mode. Since the GTF allows nondiscrete timings
1131 (nondiscrete being a range of values as opposed to discrete being a
1132 set of values), you'll be able to use any combination of horizontal
1133 and vertical resolutions, and vertical refresh rates without having
1134 to specify your own timing parameters. This is especially useful
1135 to maximize the performance of an aging display, or if you just
1136 have a display with nonstandard dimensions. A VESA compliant
1137 monitor is recommended, but can still work with non-compliant ones.
1138 If you need or want this, then select this option. The timings may
1139 not be compliant with Intel's recommended values. Use at your own
1142 If you say N, the driver will revert to discrete video timings
1143 using a set recommended by Intel in their documentation.
1148 bool "Enable DDC Support"
1149 depends on FB_I810 && FB_I810_GTF
1154 tristate "Intel LE80578 (Vermilion) support"
1155 depends on FB && PCI && X86
1156 select FB_MODE_HELPERS
1157 select FB_CFB_FILLRECT
1158 select FB_CFB_COPYAREA
1159 select FB_CFB_IMAGEBLIT
1161 This driver supports the LE80578 (Vermilion Range) chipset
1163 config FB_CARILLO_RANCH
1164 tristate "Intel Carillo Ranch support"
1165 depends on FB_LE80578 && FB && PCI && X86
1167 This driver supports the LE80578 (Carillo Ranch) board
1170 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1171 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1172 select FB_MODE_HELPERS
1173 select FB_CFB_FILLRECT
1174 select FB_CFB_COPYAREA
1175 select FB_CFB_IMAGEBLIT
1176 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1177 depends on !DRM_I915
1179 This driver supports the on-board graphics built in to the Intel
1180 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1181 Say Y if you have and plan to use such a board.
1183 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1185 To compile this driver as a module, choose M here: the
1186 module will be called intelfb.
1188 For more information, please read <file:Documentation/fb/intelfb.txt>
1190 config FB_INTEL_DEBUG
1191 bool "Intel driver Debug Messages"
1194 Say Y here if you want the Intel driver to output all sorts
1195 of debugging information to provide to the maintainer when
1196 something goes wrong.
1199 bool "DDC/I2C for Intel framebuffer support"
1204 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1207 tristate "Matrox acceleration"
1208 depends on FB && PCI
1209 select FB_CFB_FILLRECT
1210 select FB_CFB_COPYAREA
1211 select FB_CFB_IMAGEBLIT
1212 select FB_TILEBLITTING
1213 select FB_MACMODES if PPC_PMAC
1215 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1216 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1217 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1218 Matrox G400, G450 or G550 card in your box.
1220 To compile this driver as a module, choose M here: the
1221 module will be called matroxfb.
1223 You can pass several parameters to the driver at boot time or at
1224 module load time. The parameters look like "video=matrox:XXX", and
1225 are described in <file:Documentation/fb/matroxfb.txt>.
1227 config FB_MATROX_MILLENIUM
1228 bool "Millennium I/II support"
1229 depends on FB_MATROX
1231 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1232 video card. If you select "Advanced lowlevel driver options" below,
1233 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1234 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1235 also use font widths different from 8.
1237 config FB_MATROX_MYSTIQUE
1238 bool "Mystique support"
1239 depends on FB_MATROX
1241 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1242 video card. If you select "Advanced lowlevel driver options" below,
1243 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1244 packed pixel and 32 bpp packed pixel. You can also use font widths
1248 bool "G100/G200/G400/G450/G550 support"
1249 depends on FB_MATROX
1251 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1252 video card. If you select "Advanced lowlevel driver options", you
1253 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1254 pixel and 32 bpp packed pixel. You can also use font widths
1257 If you need support for G400 secondary head, you must say Y to
1258 "Matrox I2C support" and "G400 second head support" right below.
1259 G450/G550 secondary head and digital output are supported without
1262 The driver starts in monitor mode. You must use the matroxset tool
1263 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1264 swap primary and secondary head outputs, or to change output mode.
1265 Secondary head driver always start in 640x480 resolution and you
1266 must use fbset to change it.
1268 Do not forget that second head supports only 16 and 32 bpp
1269 packed pixels, so it is a good idea to compile them into the kernel
1270 too. You can use only some font widths, as the driver uses generic
1271 painting procedures (the secondary head does not use acceleration
1274 G450/G550 hardware can display TV picture only from secondary CRTC,
1275 and it performs no scaling, so picture must have 525 or 625 lines.
1277 config FB_MATROX_I2C
1278 tristate "Matrox I2C support"
1279 depends on FB_MATROX
1282 This drivers creates I2C buses which are needed for accessing the
1283 DDC (I2C) bus present on all Matroxes, an I2C bus which
1284 interconnects Matrox optional devices, like MGA-TVO on G200 and
1285 G400, and the secondary head DDC bus, present on G400 only.
1287 You can say Y or M here if you want to experiment with monitor
1288 detection code. You must say Y or M here if you want to use either
1289 second head of G400 or MGA-TVO on G200 or G400.
1291 If you compile it as module, it will create a module named
1294 config FB_MATROX_MAVEN
1295 tristate "G400 second head support"
1296 depends on FB_MATROX_G && FB_MATROX_I2C
1298 WARNING !!! This support does not work with G450 !!!
1300 Say Y or M here if you want to use a secondary head (meaning two
1301 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1302 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1303 secondary head output is blanked while you are in X. With XFree
1304 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1305 the fbdev driver on first head and the fbdev driver on second head.
1307 If you compile it as module, two modules are created,
1308 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1309 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1310 also load i2c-matroxfb to get it to run.
1312 The driver starts in monitor mode and you must use the matroxset
1314 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1315 PAL or NTSC or to swap primary and secondary head outputs.
1316 Secondary head driver also always start in 640x480 resolution, you
1317 must use fbset to change it.
1319 Also do not forget that second head supports only 16 and 32 bpp
1320 packed pixels, so it is a good idea to compile them into the kernel
1321 too. You can use only some font widths, as the driver uses generic
1322 painting procedures (the secondary head does not use acceleration
1326 tristate "ATI Radeon display support"
1327 depends on FB && PCI
1328 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1329 select FB_MODE_HELPERS
1330 select FB_CFB_FILLRECT
1331 select FB_CFB_COPYAREA
1332 select FB_CFB_IMAGEBLIT
1333 select FB_MACMODES if PPC_OF
1335 Choose this option if you want to use an ATI Radeon graphics card as
1336 a framebuffer device. There are both PCI and AGP versions. You
1337 don't need to choose this to run the Radeon in plain VGA mode.
1339 There is a product page at
1340 http://apps.ati.com/ATIcompare/
1342 config FB_RADEON_I2C
1343 bool "DDC/I2C for ATI Radeon support"
1344 depends on FB_RADEON
1348 Say Y here if you want DDC/I2C support for your Radeon board.
1350 config FB_RADEON_BACKLIGHT
1351 bool "Support for backlight control"
1352 depends on FB_RADEON
1355 Say Y here if you want to control the backlight of your display.
1357 config FB_RADEON_DEBUG
1358 bool "Lots of debug output from Radeon driver"
1359 depends on FB_RADEON
1362 Say Y here if you want the Radeon driver to output all sorts
1363 of debugging information to provide to the maintainer when
1364 something goes wrong.
1367 tristate "ATI Rage128 display support"
1368 depends on FB && PCI
1369 select FB_CFB_FILLRECT
1370 select FB_CFB_COPYAREA
1371 select FB_CFB_IMAGEBLIT
1372 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1373 select FB_MACMODES if PPC_PMAC
1375 This driver supports graphics boards with the ATI Rage128 chips.
1376 Say Y if you have such a graphics board and read
1377 <file:Documentation/fb/aty128fb.txt>.
1379 To compile this driver as a module, choose M here: the
1380 module will be called aty128fb.
1382 config FB_ATY128_BACKLIGHT
1383 bool "Support for backlight control"
1384 depends on FB_ATY128
1387 Say Y here if you want to control the backlight of your display.
1390 tristate "ATI Mach64 display support" if PCI || ATARI
1391 depends on FB && !SPARC32
1392 select FB_CFB_FILLRECT
1393 select FB_CFB_COPYAREA
1394 select FB_CFB_IMAGEBLIT
1395 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1396 select FB_MACMODES if PPC
1398 This driver supports graphics boards with the ATI Mach64 chips.
1399 Say Y if you have such a graphics board.
1401 To compile this driver as a module, choose M here: the
1402 module will be called atyfb.
1405 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1406 depends on PCI && FB_ATY
1407 default y if SPARC64 && PCI
1409 Say Y here to support use of ATI's 64-bit Rage boards (or other
1410 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1411 framebuffer device. The ATI product support page for these boards
1412 is at <http://support.ati.com/products/pc/mach64/>.
1414 config FB_ATY_GENERIC_LCD
1415 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1416 depends on FB_ATY_CT
1418 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1419 Rage XC, or Rage XL chipset.
1422 bool "Mach64 GX support" if PCI
1426 Say Y here to support use of the ATI Mach64 Graphics Expression
1427 board (or other boards based on the Mach64 GX chipset) as a
1428 framebuffer device. The ATI product support page for these boards
1430 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1432 config FB_ATY_BACKLIGHT
1433 bool "Support for backlight control"
1437 Say Y here if you want to control the backlight of your display.
1440 tristate "S3 Trio/Virge support"
1441 depends on FB && PCI
1442 select FB_CFB_FILLRECT
1443 select FB_CFB_COPYAREA
1444 select FB_CFB_IMAGEBLIT
1445 select FB_TILEBLITTING
1448 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1450 Driver for graphics boards with S3 Trio / S3 Virge chip.
1453 tristate "S3 Savage support"
1454 depends on FB && PCI && EXPERIMENTAL
1455 select FB_MODE_HELPERS
1456 select FB_CFB_FILLRECT
1457 select FB_CFB_COPYAREA
1458 select FB_CFB_IMAGEBLIT
1461 This driver supports notebooks and computers with S3 Savage PCI/AGP
1464 Say Y if you have such a graphics card.
1466 To compile this driver as a module, choose M here; the module
1467 will be called savagefb.
1469 config FB_SAVAGE_I2C
1470 bool "Enable DDC2 Support"
1471 depends on FB_SAVAGE
1474 This enables I2C support for S3 Savage Chipsets. This is used
1475 only for getting EDID information from the attached display
1476 allowing for robust video mode handling and switching.
1478 Because fbdev-2.6 requires that drivers must be able to
1479 independently validate video mode parameters, you should say Y
1482 config FB_SAVAGE_ACCEL
1483 bool "Enable Console Acceleration"
1484 depends on FB_SAVAGE
1487 This option will compile in console acceleration support. If
1488 the resulting framebuffer console has bothersome glitches, then
1492 tristate "SiS/XGI display support"
1493 depends on FB && PCI
1494 select FB_CFB_FILLRECT
1495 select FB_CFB_COPYAREA
1496 select FB_CFB_IMAGEBLIT
1497 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1499 This is the frame buffer device driver for the SiS 300, 315, 330
1500 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1501 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1503 To compile this driver as a module, choose M here; the module
1504 will be called sisfb.
1507 bool "SiS 300 series support"
1510 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1513 bool "SiS 315/330/340 series and XGI support"
1516 Say Y here to support use of the SiS 315, 330 and 340 series
1517 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1518 as XGI V3XT, V5, V8 and Z7.
1521 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1522 depends on FB && PCI && X86
1523 select FB_CFB_FILLRECT
1524 select FB_CFB_COPYAREA
1525 select FB_CFB_IMAGEBLIT
1530 This is the frame buffer device driver for Graphics chips of VIA
1531 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1532 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1534 Say Y if you have a VIA UniChrome graphics board.
1536 To compile this driver as a module, choose M here: the
1537 module will be called viafb.
1541 config FB_VIA_DIRECT_PROCFS
1542 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1546 Allow direct hardware access to some output registers via procfs.
1547 This is dangerous but may provide the only chance to get the
1548 correct output device configuration.
1549 Its use is strongly discouraged.
1554 tristate "NeoMagic display support"
1555 depends on FB && PCI
1556 select FB_MODE_HELPERS
1557 select FB_CFB_FILLRECT
1558 select FB_CFB_COPYAREA
1559 select FB_CFB_IMAGEBLIT
1562 This driver supports notebooks with NeoMagic PCI chips.
1563 Say Y if you have such a graphics card.
1565 To compile this driver as a module, choose M here: the
1566 module will be called neofb.
1569 tristate "IMG Kyro support"
1570 depends on FB && PCI
1571 select FB_CFB_FILLRECT
1572 select FB_CFB_COPYAREA
1573 select FB_CFB_IMAGEBLIT
1575 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1578 To compile this driver as a module, choose M here: the
1579 module will be called kyrofb.
1582 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1583 depends on FB && PCI
1584 select FB_CFB_IMAGEBLIT
1585 select FB_CFB_FILLRECT
1586 select FB_CFB_COPYAREA
1587 select FB_MODE_HELPERS
1589 This driver supports graphics boards with the 3Dfx Banshee,
1590 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1591 such a graphics board.
1593 To compile this driver as a module, choose M here: the
1594 module will be called tdfxfb.
1596 config FB_3DFX_ACCEL
1597 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1598 depends on FB_3DFX && EXPERIMENTAL
1600 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1601 device driver with acceleration functions.
1604 bool "Enable DDC/I2C support"
1605 depends on FB_3DFX && EXPERIMENTAL
1609 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1612 tristate "3Dfx Voodoo Graphics (sst1) support"
1613 depends on FB && PCI
1614 select FB_CFB_FILLRECT
1615 select FB_CFB_COPYAREA
1616 select FB_CFB_IMAGEBLIT
1618 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1619 Voodoo2 (cvg) based graphics card.
1621 To compile this driver as a module, choose M here: the
1622 module will be called sstfb.
1624 WARNING: Do not use any application that uses the 3D engine
1625 (namely glide) while using this driver.
1626 Please read the <file:Documentation/fb/sstfb.txt> for supported
1627 options and other important info support.
1630 tristate "VIA VT8623 support"
1631 depends on FB && PCI
1632 select FB_CFB_FILLRECT
1633 select FB_CFB_COPYAREA
1634 select FB_CFB_IMAGEBLIT
1635 select FB_TILEBLITTING
1638 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1640 Driver for CastleRock integrated graphics core in the
1641 VIA VT8623 [Apollo CLE266] chipset.
1644 tristate "Trident/CyberXXX/CyberBlade support"
1645 depends on FB && PCI
1646 select FB_CFB_FILLRECT
1647 select FB_CFB_COPYAREA
1648 select FB_CFB_IMAGEBLIT
1650 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1651 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1653 There are also integrated versions of these chips called CyberXXXX,
1654 CyberImage or CyberBlade. These chips are mostly found in laptops
1655 but also on some motherboards including early VIA EPIA motherboards.
1656 For more information, read <file:Documentation/fb/tridentfb.txt>
1658 Say Y if you have such a graphics board.
1660 To compile this driver as a module, choose M here: the
1661 module will be called tridentfb.
1664 tristate "ARK 2000PV support"
1665 depends on FB && PCI
1666 select FB_CFB_FILLRECT
1667 select FB_CFB_COPYAREA
1668 select FB_CFB_IMAGEBLIT
1669 select FB_TILEBLITTING
1672 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1674 Driver for PCI graphics boards with ARK 2000PV chip
1675 and ICS 5342 RAMDAC.
1678 tristate "Permedia3 support (EXPERIMENTAL)"
1679 depends on FB && PCI && EXPERIMENTAL
1680 select FB_CFB_FILLRECT
1681 select FB_CFB_COPYAREA
1682 select FB_CFB_IMAGEBLIT
1684 This is the frame buffer device driver for the 3DLabs Permedia3
1685 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1686 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1687 and maybe other boards.
1690 tristate "Fujitsu carmine frame buffer support"
1691 depends on FB && PCI
1692 select FB_CFB_FILLRECT
1693 select FB_CFB_COPYAREA
1694 select FB_CFB_IMAGEBLIT
1696 This is the frame buffer device driver for the Fujitsu Carmine chip.
1697 The driver provides two independent frame buffer devices.
1700 depends on FB_CARMINE
1701 prompt "DRAM timing"
1702 default FB_CARMINE_DRAM_EVAL
1704 config FB_CARMINE_DRAM_EVAL
1705 bool "Eval board timings"
1707 Use timings which work on the eval card.
1709 config CARMINE_DRAM_CUSTOM
1710 bool "Custom board timings"
1712 Use custom board timings.
1716 bool "Au1100 LCD Driver"
1717 depends on (FB = y) && MIPS && SOC_AU1100
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1722 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1723 various panels and CRTs by passing in kernel cmd line option
1724 au1100fb:panel=<name>.
1727 bool "Au1200 LCD Driver"
1728 depends on (FB = y) && MIPS && SOC_AU1200
1729 select FB_CFB_FILLRECT
1730 select FB_CFB_COPYAREA
1731 select FB_CFB_IMAGEBLIT
1733 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1734 various panels and CRTs by passing in kernel cmd line option
1735 au1200fb:panel=<name>.
1737 source "drivers/video/geode/Kconfig"
1740 tristate "HD64461 Frame Buffer support"
1741 depends on FB && HD64461
1742 select FB_CFB_FILLRECT
1743 select FB_CFB_COPYAREA
1744 select FB_CFB_IMAGEBLIT
1746 This is the frame buffer device driver for the Hitachi HD64461 LCD
1750 bool "PMAG-AA TURBOchannel framebuffer support"
1751 depends on (FB = y) && TC
1752 select FB_CFB_FILLRECT
1753 select FB_CFB_COPYAREA
1754 select FB_CFB_IMAGEBLIT
1756 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1757 used mainly in the MIPS-based DECstation series.
1760 tristate "PMAG-BA TURBOchannel framebuffer support"
1762 select FB_CFB_FILLRECT
1763 select FB_CFB_COPYAREA
1764 select FB_CFB_IMAGEBLIT
1766 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1767 used mainly in the MIPS-based DECstation series.
1770 tristate "PMAGB-B TURBOchannel framebuffer support"
1772 select FB_CFB_FILLRECT
1773 select FB_CFB_COPYAREA
1774 select FB_CFB_IMAGEBLIT
1776 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1777 in the MIPS-based DECstation series. The card is currently only
1778 supported in 1280x1024x8 mode.
1781 bool "Maxine (Personal DECstation) onboard framebuffer support"
1782 depends on (FB = y) && MACH_DECSTATION
1783 select FB_CFB_FILLRECT
1784 select FB_CFB_COPYAREA
1785 select FB_CFB_IMAGEBLIT
1787 Support for the onboard framebuffer (1024x768x8) in the Personal
1788 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1792 bool "G364 frame buffer support"
1793 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1794 select FB_CFB_FILLRECT
1795 select FB_CFB_COPYAREA
1796 select FB_CFB_IMAGEBLIT
1798 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1799 Olivetti M700-10 systems.
1802 bool "Motorola 68328 native frame buffer support"
1803 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1804 select FB_CFB_FILLRECT
1805 select FB_CFB_COPYAREA
1806 select FB_CFB_IMAGEBLIT
1808 Say Y here if you want to support the built-in frame buffer of
1809 the Motorola 68328 CPU family.
1812 tristate "PXA168/910 LCD framebuffer support"
1813 depends on FB && (CPU_PXA168 || CPU_PXA910)
1814 select FB_CFB_FILLRECT
1815 select FB_CFB_COPYAREA
1816 select FB_CFB_IMAGEBLIT
1818 Frame buffer driver for the built-in LCD controller in the Marvell
1822 tristate "PXA LCD framebuffer support"
1823 depends on FB && ARCH_PXA
1824 select FB_CFB_FILLRECT
1825 select FB_CFB_COPYAREA
1826 select FB_CFB_IMAGEBLIT
1828 Frame buffer driver for the built-in LCD controller in the Intel
1831 This driver is also available as a module ( = code which can be
1832 inserted and removed from the running kernel whenever you want). The
1833 module will be called pxafb. If you want to compile it as a module,
1834 say M here and read <file:Documentation/kbuild/modules.txt>.
1838 config FB_PXA_OVERLAY
1839 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1841 depends on FB_PXA && (PXA27x || PXA3xx)
1843 config FB_PXA_SMARTPANEL
1844 bool "PXA Smartpanel LCD support"
1848 config FB_PXA_PARAMETERS
1849 bool "PXA LCD command line parameters"
1853 Enable the use of kernel command line or module parameters
1854 to configure the physical properties of the LCD panel when
1855 using the PXA LCD driver.
1857 This option allows you to override the panel parameters
1858 supplied by the platform in order to support multiple
1859 different models of flatpanel. If you will only be using a
1860 single model of flatpanel then you can safely leave this
1863 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1866 tristate "2700G LCD framebuffer support"
1867 depends on FB && ARCH_PXA
1868 select FB_CFB_FILLRECT
1869 select FB_CFB_COPYAREA
1870 select FB_CFB_IMAGEBLIT
1872 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1876 bool "Enable debugging info via debugfs"
1877 depends on FB_MBX && DEBUG_FS
1880 Enable this if you want debugging information using the debug
1881 filesystem (debugfs)
1886 tristate "Freescale DIU framebuffer support"
1887 depends on FB && FSL_SOC
1888 select FB_MODE_HELPERS
1889 select FB_CFB_FILLRECT
1890 select FB_CFB_COPYAREA
1891 select FB_CFB_IMAGEBLIT
1892 select PPC_LIB_RHEAP
1894 Framebuffer driver for the Freescale SoC DIU
1897 tristate "W100 frame buffer support"
1898 depends on FB && ARCH_PXA
1899 select FB_CFB_FILLRECT
1900 select FB_CFB_COPYAREA
1901 select FB_CFB_IMAGEBLIT
1903 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1904 It can also drive the w3220 chip found on iPAQ hx4700.
1906 This driver is also available as a module ( = code which can be
1907 inserted and removed from the running kernel whenever you want). The
1908 module will be called w100fb. If you want to compile it as a module,
1909 say M here and read <file:Documentation/kbuild/modules.txt>.
1915 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1917 config SH_LCD_MIPI_DSI
1920 config FB_SH_MOBILE_LCDC
1921 tristate "SuperH Mobile LCDC framebuffer support"
1922 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1923 select FB_SYS_FILLRECT
1924 select FB_SYS_COPYAREA
1925 select FB_SYS_IMAGEBLIT
1927 select FB_DEFERRED_IO
1928 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1930 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1932 config FB_SH_MOBILE_HDMI
1933 tristate "SuperH Mobile HDMI controller support"
1934 depends on FB_SH_MOBILE_LCDC
1935 select FB_MODE_HELPERS
1937 Driver for the on-chip SH-Mobile HDMI controller.
1940 tristate "Toshiba Mobile IO FrameBuffer support"
1941 depends on FB && MFD_CORE
1942 select FB_CFB_FILLRECT
1943 select FB_CFB_COPYAREA
1944 select FB_CFB_IMAGEBLIT
1946 Frame buffer driver for the Toshiba Mobile IO integrated as found
1947 on the Sharp SL-6000 series
1949 This driver is also available as a module ( = code which can be
1950 inserted and removed from the running kernel whenever you want). The
1951 module will be called tmiofb. If you want to compile it as a module,
1952 say M here and read <file:Documentation/kbuild/modules.txt>.
1956 config FB_TMIO_ACCELL
1957 bool "tmiofb acceleration"
1962 tristate "Samsung S3C framebuffer support"
1963 depends on FB && ARCH_S3C64XX
1964 select FB_CFB_FILLRECT
1965 select FB_CFB_COPYAREA
1966 select FB_CFB_IMAGEBLIT
1968 Frame buffer driver for the built-in FB controller in the Samsung
1969 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1970 and the S3C64XX series such as the S3C6400 and S3C6410.
1972 These chips all have the same basic framebuffer design with the
1973 actual capabilities depending on the chip. For instance the S3C6400
1974 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1975 currently only have two.
1977 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1979 config FB_S3C_DEBUG_REGWRITE
1980 bool "Debug register writes"
1983 Show all register writes via printk(KERN_DEBUG)
1986 tristate "S3C2410 LCD framebuffer support"
1987 depends on FB && ARCH_S3C2410
1988 select FB_CFB_FILLRECT
1989 select FB_CFB_COPYAREA
1990 select FB_CFB_IMAGEBLIT
1992 Frame buffer driver for the built-in LCD controller in the Samsung
1995 This driver is also available as a module ( = code which can be
1996 inserted and removed from the running kernel whenever you want). The
1997 module will be called s3c2410fb. If you want to compile it as a module,
1998 say M here and read <file:Documentation/kbuild/modules.txt>.
2001 config FB_S3C2410_DEBUG
2002 bool "S3C2410 lcd debug messages"
2003 depends on FB_S3C2410
2005 Turn on debugging messages. Note that you can set/unset at run time
2009 tristate "Samsung SoC MIPI-DSI support."
2010 depends on FB_S3C && (ARCH_S5PV210 || ARCH_S5PV310)
2013 This enables support for MIPI-DSI device.
2016 bool "NUC900 LCD framebuffer support"
2017 depends on FB && ARCH_W90X900
2018 select FB_CFB_FILLRECT
2019 select FB_CFB_COPYAREA
2020 select FB_CFB_IMAGEBLIT
2022 Frame buffer driver for the built-in LCD controller in the Nuvoton
2025 config GPM1040A0_320X240
2026 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2027 depends on FB_NUC900
2029 config FB_NUC900_DEBUG
2030 bool "NUC900 lcd debug messages"
2031 depends on FB_NUC900
2033 Turn on debugging messages. Note that you can set/unset at run time
2037 tristate "Silicon Motion SM501 framebuffer support"
2038 depends on FB && MFD_SM501
2039 select FB_CFB_FILLRECT
2040 select FB_CFB_COPYAREA
2041 select FB_CFB_IMAGEBLIT
2043 Frame buffer driver for the CRT and LCD controllers in the Silicon
2046 This driver is also available as a module ( = code which can be
2047 inserted and removed from the running kernel whenever you want). The
2048 module will be called sm501fb. If you want to compile it as a module,
2049 say M here and read <file:Documentation/kbuild/modules.txt>.
2054 config FB_PNX4008_DUM
2055 tristate "Display Update Module support on Philips PNX4008 board"
2056 depends on FB && ARCH_PNX4008
2058 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2060 config FB_PNX4008_DUM_RGB
2061 tristate "RGB Framebuffer support on Philips PNX4008 board"
2062 depends on FB_PNX4008_DUM
2063 select FB_CFB_FILLRECT
2064 select FB_CFB_COPYAREA
2065 select FB_CFB_IMAGEBLIT
2067 Say Y here to enable support for PNX4008 RGB Framebuffer
2069 config FB_IBM_GXT4500
2070 tristate "Framebuffer support for IBM GXT4500P adaptor"
2071 depends on FB && PPC
2072 select FB_CFB_FILLRECT
2073 select FB_CFB_COPYAREA
2074 select FB_CFB_IMAGEBLIT
2076 Say Y here to enable support for the IBM GXT4500P display
2077 adaptor, found on some IBM System P (pSeries) machines.
2080 tristate "PS3 GPU framebuffer driver"
2081 depends on FB && PS3_PS3AV
2082 select FB_SYS_FILLRECT
2083 select FB_SYS_COPYAREA
2084 select FB_SYS_IMAGEBLIT
2086 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2088 Include support for the virtual frame buffer in the PS3 platform.
2090 config FB_PS3_DEFAULT_SIZE_M
2091 int "PS3 default frame buffer size (in MiB)"
2095 This is the default size (in MiB) of the virtual frame buffer in
2097 The default value can be overridden on the kernel command line
2098 using the "ps3fb" option (e.g. "ps3fb=9M");
2101 tristate "Xilinx frame buffer support"
2102 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2103 select FB_CFB_FILLRECT
2104 select FB_CFB_COPYAREA
2105 select FB_CFB_IMAGEBLIT
2107 Include support for the Xilinx ML300/ML403 reference design
2108 framebuffer. ML300 carries a 640*480 LCD display on the board,
2109 ML403 uses a standard DB15 VGA connector.
2112 tristate "Cobalt server LCD frame buffer support"
2113 depends on FB && MIPS_COBALT
2116 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2117 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2118 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2119 select FB_CFB_FILLRECT
2120 select FB_CFB_COPYAREA
2121 select FB_CFB_IMAGEBLIT
2123 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2124 (D)STN/TFT LCD Controller.
2125 Supports display resolutions up to 1024x1024 pixel, grayscale and
2126 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2127 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2128 panels <= 320 pixel horizontal resolution.
2131 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2132 depends on FB && ARCH_DAVINCI_DA8XX
2133 select FB_CFB_FILLRECT
2134 select FB_CFB_COPYAREA
2135 select FB_CFB_IMAGEBLIT
2137 This is the frame buffer device driver for the TI LCD controller
2138 found on DA8xx/OMAP-L1xx SoCs.
2142 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2144 select FB_SYS_FILLRECT
2145 select FB_SYS_COPYAREA
2146 select FB_SYS_IMAGEBLIT
2149 This is a `virtual' frame buffer device. It operates on a chunk of
2150 unswappable kernel memory instead of on the memory of a graphics
2151 board. This means you cannot see any output sent to this frame
2152 buffer device, while it does consume precious memory. The main use
2153 of this frame buffer device is testing and debugging the frame
2154 buffer subsystem. Do NOT enable it for normal systems! To protect
2155 the innocent, it has to be enabled explicitly at boot time using the
2156 kernel option `video=vfb:'.
2158 To compile this driver as a module, choose M here: the
2159 module will be called vfb. In order to load it, you must use
2160 the vfb_enable=1 option.
2164 config XEN_FBDEV_FRONTEND
2165 tristate "Xen virtual frame buffer support"
2166 depends on FB && XEN
2167 select FB_SYS_FILLRECT
2168 select FB_SYS_COPYAREA
2169 select FB_SYS_IMAGEBLIT
2171 select FB_DEFERRED_IO
2172 select XEN_XENBUS_FRONTEND
2175 This driver implements the front-end of the Xen virtual
2176 frame buffer driver. It communicates with a back-end
2180 tristate "E-Ink Metronome/8track controller support"
2182 select FB_SYS_FILLRECT
2183 select FB_SYS_COPYAREA
2184 select FB_SYS_IMAGEBLIT
2186 select FB_DEFERRED_IO
2188 This driver implements support for the E-Ink Metronome
2189 controller. The pre-release name for this device was 8track
2190 and could also have been called by some vendors as PVI-nnnn.
2193 tristate "Fujitsu MB862xx GDC support"
2195 select FB_CFB_FILLRECT
2196 select FB_CFB_COPYAREA
2197 select FB_CFB_IMAGEBLIT
2199 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2201 config FB_MB862XX_PCI_GDC
2202 bool "Carmine/Coral-P(A) GDC"
2203 depends on PCI && FB_MB862XX
2205 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2206 PCI graphics controller devices.
2208 config FB_MB862XX_LIME
2210 depends on FB_MB862XX
2211 depends on OF && !FB_MB862XX_PCI_GDC
2213 select FB_FOREIGN_ENDIAN
2214 select FB_LITTLE_ENDIAN
2216 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2219 tristate "EP93XX frame buffer support"
2220 depends on FB && ARCH_EP93XX
2221 select FB_CFB_FILLRECT
2222 select FB_CFB_COPYAREA
2223 select FB_CFB_IMAGEBLIT
2225 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2226 This driver is also available as a module. The module will be called
2229 config FB_PRE_INIT_FB
2230 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2231 depends on FB && FB_MB862XX_LIME
2233 Select this option if display contents should be inherited as set by
2237 tristate "MSM Framebuffer support"
2238 depends on FB && ARCH_MSM
2239 select FB_CFB_FILLRECT
2240 select FB_CFB_COPYAREA
2241 select FB_CFB_IMAGEBLIT
2244 tristate "MX3 Framebuffer support"
2245 depends on FB && MX3_IPU
2246 select FB_CFB_FILLRECT
2247 select FB_CFB_COPYAREA
2248 select FB_CFB_IMAGEBLIT
2251 This is a framebuffer device for the i.MX31 LCD Controller. So
2252 far only synchronous displays are supported. If you plan to use
2253 an LCD display with your i.MX31 system, say Y here.
2255 config FB_BROADSHEET
2256 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2258 select FB_SYS_FILLRECT
2259 select FB_SYS_COPYAREA
2260 select FB_SYS_IMAGEBLIT
2262 select FB_DEFERRED_IO
2264 This driver implements support for the E-Ink Broadsheet
2265 controller. The release name for this device was Epson S1D13521
2266 and could also have been called by other names when coupled with
2270 tristate "JZ4740 LCD framebuffer support"
2271 depends on FB && MACH_JZ4740
2272 select FB_SYS_FILLRECT
2273 select FB_SYS_COPYAREA
2274 select FB_SYS_IMAGEBLIT
2276 Framebuffer support for the JZ4740 SoC.
2278 source "drivers/video/omap/Kconfig"
2279 source "drivers/video/omap2/Kconfig"
2281 source "drivers/video/backlight/Kconfig"
2282 source "drivers/video/display/Kconfig"
2285 source "drivers/video/console/Kconfig"
2288 if FB || SGI_NEWPORT_CONSOLE
2289 source "drivers/video/logo/Kconfig"