5 menu "Graphics support"
8 source "drivers/video/backlight/Kconfig"
9 source "drivers/video/display/Kconfig"
15 config VIDEO_OUTPUT_CONTROL
16 tristate "Lowlevel video output switch controls"
19 This framework adds support for low-level control of the video
23 tristate "Support for frame buffer devices"
25 The frame buffer device provides an abstraction for the graphics
26 hardware. It represents the frame buffer of some video hardware and
27 allows application software to access the graphics hardware through
28 a well-defined interface, so the software doesn't need to know
29 anything about the low-level (hardware register) stuff.
31 Frame buffer devices work identically across the different
32 architectures supported by Linux and make the implementation of
33 application programs easier and more portable; at this point, an X
34 server exists which uses the frame buffer device exclusively.
35 On several non-X86 architectures, the frame buffer device is the
36 only way to use the graphics hardware.
38 The device is accessed through special device nodes, usually located
39 in the /dev directory, i.e. /dev/fb*.
41 You need an utility program called fbset to make full use of frame
42 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
43 and the Framebuffer-HOWTO at
44 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
47 Say Y here and to the driver for your graphics board below if you
48 are compiling a kernel for a non-x86 architecture.
50 If you are compiling for the x86 architecture, you can say Y if you
51 want to play with it, but it is not essential. Please note that
52 running graphical applications that directly touch the hardware
53 (e.g. an accelerated X server) and that are not frame buffer
54 device-aware may cause unexpected results. If unsure, say N.
57 bool "Enable firmware EDID"
61 This enables access to the EDID transferred from the firmware.
62 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
63 transfers do not work for your driver and if you are using
64 nvidiafb, i810fb or savagefb.
66 In general, choosing Y for this option is safe. If you
67 experience extremely long delays while booting before you get
68 something on your display, try setting this to N. Matrox cards in
69 combination with certain motherboards and monitors are known to
70 suffer from this problem.
79 config FB_CFB_FILLRECT
84 Include the cfb_fillrect function for generic software rectangle
85 filling. This is used by drivers that don't provide their own
86 (accelerated) version.
88 config FB_CFB_COPYAREA
93 Include the cfb_copyarea function for generic software area copying.
94 This is used by drivers that don't provide their own (accelerated)
97 config FB_CFB_IMAGEBLIT
102 Include the cfb_imageblit function for generic software image
103 blitting. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_SYS_FILLRECT
111 Include the sys_fillrect function for generic software rectangle
112 filling. This is used by drivers that don't provide their own
113 (accelerated) version and the framebuffer is in system RAM.
115 config FB_SYS_COPYAREA
120 Include the sys_copyarea function for generic software area copying.
121 This is used by drivers that don't provide their own (accelerated)
122 version and the framebuffer is in system RAM.
124 config FB_SYS_IMAGEBLIT
129 Include the sys_imageblit function for generic software image
130 blitting. This is used by drivers that don't provide their own
131 (accelerated) version and the framebuffer is in system RAM.
138 config FB_DEFERRED_IO
148 Common utility functions useful to fbdev drivers of VGA-based
159 select BACKLIGHT_LCD_SUPPORT
160 select BACKLIGHT_CLASS_DEVICE
163 config FB_MODE_HELPERS
164 bool "Enable Video Mode Handling Helpers"
168 This enables functions for handling video modes using the
169 Generalized Timing Formula and the EDID parser. A few drivers rely
170 on this feature such as the radeonfb, rivafb, and the i810fb. If
171 your driver does not take advantage of this feature, choosing Y will
172 just increase the kernel size by about 5K.
174 config FB_TILEBLITTING
175 bool "Enable Tile Blitting Support"
179 This enables tile blitting. Tile blitting is a drawing technique
180 where the screen is divided into rectangular sections (tiles), whereas
181 the standard blitting divides the screen into pixels. Because the
182 default drawing element is a tile, drawing functions will be passed
183 parameters in terms of number of tiles instead of number of pixels.
184 For example, to draw a single character, instead of using bitmaps,
185 an index to an array of bitmaps will be used. To clear or move a
186 rectangular section of a screen, the rectangle will be described in
187 terms of number of tiles in the x- and y-axis.
189 This is particularly important to one driver, matroxfb. If
192 comment "Frame buffer hardware drivers"
196 tristate "Cirrus Logic support"
197 depends on FB && (ZORRO || PCI)
198 select FB_CFB_FILLRECT
199 select FB_CFB_COPYAREA
200 select FB_CFB_IMAGEBLIT
202 This enables support for Cirrus Logic GD542x/543x based boards on
203 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
205 If you have a PCI-based system, this enables support for these
206 chips: GD-543x, GD-544x, GD-5480.
208 Please read the file <file:Documentation/fb/cirrusfb.txt>.
210 Say N unless you have such a graphics board or plan to get one
211 before you next recompile the kernel.
214 tristate "Permedia2 support"
215 depends on FB && ((AMIGA && BROKEN) || PCI)
216 select FB_CFB_FILLRECT
217 select FB_CFB_COPYAREA
218 select FB_CFB_IMAGEBLIT
220 This is the frame buffer device driver for the Permedia2 AGP frame
221 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
223 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
225 config FB_PM2_FIFO_DISCONNECT
226 bool "enable FIFO disconnect feature"
227 depends on FB_PM2 && PCI
229 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
232 tristate "ARM PrimeCell PL110 support"
233 depends on FB && ARM && ARM_AMBA
234 select FB_CFB_FILLRECT
235 select FB_CFB_COPYAREA
236 select FB_CFB_IMAGEBLIT
238 This framebuffer device driver is for the ARM PrimeCell PL110
239 Colour LCD controller. ARM PrimeCells provide the building
240 blocks for System on a Chip devices.
242 If you want to compile this as a module (=code which can be
243 inserted into and removed from the running kernel), say M
244 here and read <file:Documentation/kbuild/modules.txt>. The module
245 will be called amba-clcd.
249 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
251 default FB_ARMCLCD_SHARP_LQ035Q7DB02
253 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
254 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
256 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
257 color QVGA, HRTFT panel. The LogicPD device includes
258 an integrated HRTFT controller IC.
259 The native resolution is 240x320.
261 config FB_ARMCLCD_SHARP_LQ057Q3DC02
262 bool "LogicPD LCD 5.7\" QVGA"
264 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
265 color QVGA, TFT panel. The LogicPD device includes an
266 The native resolution is 320x240.
268 config FB_ARMCLCD_SHARP_LQ64D343
269 bool "LogicPD LCD 6.4\" VGA"
271 This is an implementation of the Sharp LQ64D343, a 6.4"
272 color VGA, TFT panel. The LogicPD device includes an
273 The native resolution is 640x480.
275 config FB_ARMCLCD_SHARP_LQ10D368
276 bool "LogicPD LCD 10.4\" VGA"
278 This is an implementation of the Sharp LQ10D368, a 10.4"
279 color VGA, TFT panel. The LogicPD device includes an
280 The native resolution is 640x480.
283 config FB_ARMCLCD_SHARP_LQ121S1DG41
284 bool "LogicPD LCD 12.1\" SVGA"
286 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
287 color SVGA, TFT panel. The LogicPD device includes an
288 The native resolution is 800x600.
290 This panel requires a clock rate may be an integer fraction
291 of the base LCDCLK frequency. The driver will select the
292 highest frequency available that is lower than the maximum
293 allowed. The panel may flicker if the clock rate is
294 slower than the recommended minimum.
296 config FB_ARMCLCD_AUO_A070VW01_WIDE
297 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
299 This is an implementation of the AU Optronics, a 7.0"
300 WIDE Color. The native resolution is 234x480.
302 config FB_ARMCLCD_HITACHI
303 bool "Hitachi Wide Screen 800x480"
305 This is an implementation of the Hitachi 800x480.
311 bool "Acorn VIDC support"
312 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
313 select FB_CFB_FILLRECT
314 select FB_CFB_COPYAREA
315 select FB_CFB_IMAGEBLIT
317 This is the frame buffer device driver for the Acorn VIDC graphics
318 hardware found in Acorn RISC PCs and other ARM-based machines. If
322 bool "CLPS711X LCD support"
323 depends on (FB = y) && ARM && ARCH_CLPS711X
324 select FB_CFB_FILLRECT
325 select FB_CFB_COPYAREA
326 select FB_CFB_IMAGEBLIT
328 Say Y to enable the Framebuffer driver for the CLPS7111 and
332 bool "SA-1100 LCD support"
333 depends on (FB = y) && ARM && ARCH_SA1100
334 select FB_CFB_FILLRECT
335 select FB_CFB_COPYAREA
336 select FB_CFB_IMAGEBLIT
338 This is a framebuffer device for the SA-1100 LCD Controller.
339 See <http://www.linux-fbdev.org/> for information on framebuffer
342 If you plan to use the LCD display with your SA-1100 system, say
346 tristate "Motorola i.MX LCD support"
347 depends on FB && ARM && ARCH_IMX
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
353 tristate "CyberPro 2000/2010/5000 support"
354 depends on FB && PCI && (BROKEN || !SPARC64)
355 select FB_CFB_FILLRECT
356 select FB_CFB_COPYAREA
357 select FB_CFB_IMAGEBLIT
359 This enables support for the Integraphics CyberPro 20x0 and 5000
360 VGA chips used in the Rebel.com Netwinder and other machines.
361 Say Y if you have a NetWinder or a graphics card containing this
362 device, otherwise say N.
366 depends on (FB = y) && APOLLO
368 select FB_CFB_FILLRECT
369 select FB_CFB_IMAGEBLIT
373 depends on (FB = y) && Q40
375 select FB_CFB_FILLRECT
376 select FB_CFB_COPYAREA
377 select FB_CFB_IMAGEBLIT
380 tristate "Amiga native chipset support"
381 depends on FB && AMIGA
383 This is the frame buffer device driver for the builtin graphics
384 chipset found in Amigas.
386 To compile this driver as a module, choose M here: the
387 module will be called amifb.
390 bool "Amiga OCS chipset support"
393 This enables support for the original Agnus and Denise video chips,
394 found in the Amiga 1000 and most A500's and A2000's. If you intend
395 to run Linux on any of these systems, say Y; otherwise say N.
398 bool "Amiga ECS chipset support"
401 This enables support for the Enhanced Chip Set, found in later
402 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
403 you intend to run Linux on any of these systems, say Y; otherwise
407 bool "Amiga AGA chipset support"
410 This enables support for the Advanced Graphics Architecture (also
411 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
412 and CD32. If you intend to run Linux on any of these systems, say Y;
416 bool "Amiga FrameMaster II/Rainbow II support"
417 depends on (FB = y) && ZORRO
418 select FB_CFB_FILLRECT
419 select FB_CFB_COPYAREA
420 select FB_CFB_IMAGEBLIT
422 This is the frame buffer device driver for the Amiga FrameMaster
423 card from BSC (exhibited 1992 but not shipped as a CBM product).
426 tristate "Arc Monochrome LCD board support"
428 select FB_SYS_FILLRECT
429 select FB_SYS_COPYAREA
430 select FB_SYS_IMAGEBLIT
433 This enables support for the Arc Monochrome LCD board. The board
434 is based on the KS-108 lcd controller and is typically a matrix
435 of 2*n chips. This driver was tested with a 128x64 panel. This
436 driver supports it for use with x86 SBCs through a 16 bit GPIO
437 interface (8 bit data, 8 bit control). If you anticipate using
438 this driver, say Y or M; otherwise say N. You must specify the
439 GPIO IO address to be used for setting control and data.
442 bool "Atari native chipset support"
443 depends on (FB = y) && ATARI
444 select FB_CFB_FILLRECT
445 select FB_CFB_COPYAREA
446 select FB_CFB_IMAGEBLIT
448 This is the frame buffer device driver for the builtin graphics
449 chipset found in Ataris.
452 bool "Open Firmware frame buffer device support"
453 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
454 select FB_CFB_FILLRECT
455 select FB_CFB_COPYAREA
456 select FB_CFB_IMAGEBLIT
459 Say Y if you want support with Open Firmware for your graphics
463 bool "Apple \"control\" display support"
464 depends on (FB = y) && PPC_PMAC && PPC32
465 select FB_CFB_FILLRECT
466 select FB_CFB_COPYAREA
467 select FB_CFB_IMAGEBLIT
470 This driver supports a frame buffer for the graphics adapter in the
471 Power Macintosh 7300 and others.
474 bool "Apple \"platinum\" display support"
475 depends on (FB = y) && PPC_PMAC && PPC32
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
481 This driver supports a frame buffer for the "platinum" graphics
482 adapter in some Power Macintoshes.
485 bool "Apple \"valkyrie\" display support"
486 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
492 This driver supports a frame buffer for the "valkyrie" graphics
493 adapter in some Power Macintoshes.
496 bool "Chips 65550 display support"
497 depends on (FB = y) && PPC32
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
502 This is the frame buffer device driver for the Chips & Technologies
503 65550 graphics chip in PowerBooks.
506 bool "Asiliant (Chips) 69000 display support"
507 depends on (FB = y) && PCI
508 select FB_CFB_FILLRECT
509 select FB_CFB_COPYAREA
510 select FB_CFB_IMAGEBLIT
512 This is the frame buffer device driver for the Asiliant 69030 chipset
515 bool "IMS Twin Turbo display support"
516 depends on (FB = y) && PCI
517 select FB_CFB_IMAGEBLIT
518 select FB_MACMODES if PPC
520 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
521 many Macintosh and compatible computers.
524 tristate "VGA 16-color graphics support"
525 depends on FB && (X86 || PPC)
526 select FB_CFB_FILLRECT
527 select FB_CFB_COPYAREA
528 select FB_CFB_IMAGEBLIT
530 select FONT_8x16 if FRAMEBUFFER_CONSOLE
532 This is the frame buffer device driver for VGA 16 color graphic
533 cards. Say Y if you have such a card.
535 To compile this driver as a module, choose M here: the
536 module will be called vga16fb.
539 tristate "HP STI frame buffer device support"
540 depends on FB && PARISC
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
546 STI refers to the HP "Standard Text Interface" which is a set of
547 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
548 Enabling this option will implement the linux framebuffer device
549 using calls to the STI BIOS routines for initialisation.
551 If you enable this option, you will get a planar framebuffer device
552 /dev/fb which will work on the most common HP graphic cards of the
553 NGLE family, including the artist chips (in the 7xx and Bxxx series),
554 HCRX, HCRX24, CRX, CRX24 and VisEG series.
556 It is safe to enable this option, so you should probably say "Y".
559 bool "Generic Macintosh display support"
560 depends on (FB = y) && MAC
561 select FB_CFB_FILLRECT
562 select FB_CFB_COPYAREA
563 select FB_CFB_IMAGEBLIT
566 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
569 depends on (FB = y) && HP300
570 select FB_CFB_FILLRECT
571 select FB_CFB_IMAGEBLIT
575 tristate "TGA/SFB+ framebuffer support"
576 depends on FB && (ALPHA || TC)
577 select FB_CFB_FILLRECT
578 select FB_CFB_COPYAREA
579 select FB_CFB_IMAGEBLIT
582 This is the frame buffer device driver for generic TGA and SFB+
583 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
584 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
585 TURBOchannel cards, also known as PMAGD-A, -B and -C.
587 Due to hardware limitations ZLX-E2 and E3 cards are not supported
588 for DECstation 5000/200 systems. Additionally due to firmware
589 limitations these cards may cause troubles with booting DECstation
590 5000/240 and /260 systems, but are fully supported under Linux if
591 you manage to get it going. ;-)
593 Say Y if you have one of those.
596 tristate "Userspace VESA VGA graphics support"
597 depends on FB && CONNECTOR
598 select FB_CFB_FILLRECT
599 select FB_CFB_COPYAREA
600 select FB_CFB_IMAGEBLIT
601 select FB_MODE_HELPERS
603 This is the frame buffer driver for generic VBE 2.0 compliant
604 graphic cards. It can also take advantage of VBE 3.0 features,
605 such as refresh rate adjustment.
607 This driver generally provides more features than vesafb but
608 requires a userspace helper application called 'v86d'. See
609 <file:Documentation/fb/uvesafb.txt> for more information.
614 bool "VESA VGA graphics support"
615 depends on (FB = y) && X86
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
621 This is the frame buffer device driver for generic VESA 2.0
622 compliant graphic cards. The older VESA 1.2 cards are not supported.
623 You will get a boot time penguin logo at no additional cost. Please
624 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
627 bool "Intel-based Macintosh Framebuffer Support"
628 depends on (FB = y) && X86 && EFI
629 select FB_CFB_FILLRECT
630 select FB_CFB_COPYAREA
631 select FB_CFB_IMAGEBLIT
633 This is the frame buffer device driver for the Intel-based Macintosh
636 tristate "Hecuba board support"
637 depends on FB && X86 && MMU
638 select FB_SYS_FILLRECT
639 select FB_SYS_COPYAREA
640 select FB_SYS_IMAGEBLIT
642 select FB_DEFERRED_IO
644 This enables support for the Hecuba board. This driver was tested
645 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
646 interface (8 bit data, 4 bit control). If you anticpate using
647 this driver, say Y or M; otherwise say N. You must specify the
648 GPIO IO address to be used for setting control and data.
651 tristate "Hercules mono graphics support"
653 select FB_CFB_FILLRECT
654 select FB_CFB_COPYAREA
655 select FB_CFB_IMAGEBLIT
657 Say Y here if you have a Hercules mono graphics card.
659 To compile this driver as a module, choose M here: the
660 module will be called hgafb.
662 As this card technology is 15 years old, most people will answer N
666 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
667 depends on FB_HGA && EXPERIMENTAL
669 This will compile the Hercules mono graphics with
670 acceleration functions.
673 tristate "SGI Visual Workstation framebuffer support"
674 depends on FB && X86_VISWS
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
679 SGI Visual Workstation support for framebuffer graphics.
682 bool "SGI Graphics Backend frame buffer support"
683 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
684 select FB_CFB_FILLRECT
685 select FB_CFB_COPYAREA
686 select FB_CFB_IMAGEBLIT
688 This is the frame buffer device driver for SGI Graphics Backend.
689 This chip is used in SGI O2 and Visual Workstation 320/540.
692 int "Video memory size in MB"
696 This is the amount of memory reserved for the framebuffer,
697 which can be any value between 1MB and 8MB.
700 bool "SBUS and UPA framebuffers"
701 depends on (FB = y) && SPARC
703 Say Y if you want support for SBUS or UPA based frame buffer device.
707 depends on (FB = y) && (SPARC && FB_SBUS)
708 select FB_CFB_FILLRECT
709 select FB_CFB_COPYAREA
710 select FB_CFB_IMAGEBLIT
712 This is the frame buffer device driver for the BWtwo frame buffer.
715 bool "CGthree support"
716 depends on (FB = y) && (SPARC && FB_SBUS)
717 select FB_CFB_FILLRECT
718 select FB_CFB_COPYAREA
719 select FB_CFB_IMAGEBLIT
721 This is the frame buffer device driver for the CGthree frame buffer.
724 bool "CGsix (GX,TurboGX) support"
725 depends on (FB = y) && (SPARC && FB_SBUS)
726 select FB_CFB_COPYAREA
727 select FB_CFB_IMAGEBLIT
729 This is the frame buffer device driver for the CGsix (GX, TurboGX)
733 bool "Creator/Creator3D/Elite3D support"
734 depends on FB_SBUS && SPARC64
735 select FB_CFB_COPYAREA
736 select FB_CFB_IMAGEBLIT
738 This is the frame buffer device driver for the Creator, Creator3D,
739 and Elite3D graphics boards.
742 bool "TCX (SS4/SS5 only) support"
744 select FB_CFB_FILLRECT
745 select FB_CFB_COPYAREA
746 select FB_CFB_IMAGEBLIT
748 This is the frame buffer device driver for the TCX 24/8bit frame
752 bool "CGfourteen (SX) support"
754 select FB_CFB_FILLRECT
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
758 This is the frame buffer device driver for the CGfourteen frame
759 buffer on Desktop SPARCsystems with the SX graphics option.
762 bool "P9100 (Sparcbook 3 only) support"
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
768 This is the frame buffer device driver for the P9100 card
769 supported on Sparcbook 3 machines.
772 bool "Leo (ZX) support"
774 select FB_CFB_FILLRECT
775 select FB_CFB_COPYAREA
776 select FB_CFB_IMAGEBLIT
778 This is the frame buffer device driver for the SBUS-based Sun ZX
779 (leo) frame buffer cards.
782 bool "IGA 168x display support"
783 depends on (FB = y) && SPARC32
784 select FB_CFB_FILLRECT
785 select FB_CFB_COPYAREA
786 select FB_CFB_IMAGEBLIT
788 This is the framebuffer device for the INTERGRAPHICS 1680 and
789 successor frame buffer cards.
792 bool "Sun XVR-500 3DLABS Wildcat support"
793 depends on (FB = y) && PCI && SPARC64
794 select FB_CFB_FILLRECT
795 select FB_CFB_COPYAREA
796 select FB_CFB_IMAGEBLIT
798 This is the framebuffer device for the Sun XVR-500 and similar
799 graphics cards based upon the 3DLABS Wildcat chipset. The driver
800 only works on sparc64 systems where the system firwmare has
801 mostly initialized the card already. It is treated as a
802 completely dumb framebuffer device.
805 bool "Sun XVR-2500 3DLABS Wildcat support"
806 depends on (FB = y) && PCI && SPARC64
807 select FB_CFB_FILLRECT
808 select FB_CFB_COPYAREA
809 select FB_CFB_IMAGEBLIT
811 This is the framebuffer device for the Sun XVR-2500 and similar
812 graphics cards based upon the 3DLABS Wildcat chipset. The driver
813 only works on sparc64 systems where the system firwmare has
814 mostly initialized the card already. It is treated as a
815 completely dumb framebuffer device.
818 tristate "NEC PowerVR 2 display support"
819 depends on FB && SH_DREAMCAST
820 select FB_CFB_FILLRECT
821 select FB_CFB_COPYAREA
822 select FB_CFB_IMAGEBLIT
824 Say Y here if you have a PowerVR 2 card in your box. If you plan to
825 run linux on your Dreamcast, you will have to say Y here.
826 This driver may or may not work on other PowerVR 2 cards, but is
827 totally untested. Use at your own risk. If unsure, say N.
829 To compile this driver as a module, choose M here: the
830 module will be called pvr2fb.
832 You can pass several parameters to the driver at boot time or at
833 module load time. The parameters look like "video=pvr2:XXX", where
834 the meaning of XXX can be found at the end of the main source file
835 (<file:drivers/video/pvr2fb.c>). Please see the file
836 <file:Documentation/fb/pvr2fb.txt>.
839 bool "Epson 1355 framebuffer support"
840 depends on (FB = y) && ARCH_CEIVA
841 select FB_CFB_FILLRECT
842 select FB_CFB_COPYAREA
843 select FB_CFB_IMAGEBLIT
845 Build in support for the SED1355 Epson Research Embedded RAMDAC
846 LCD/CRT Controller (since redesignated as the S1D13505) as a
847 framebuffer. Product specs at
848 <http://www.erd.epson.com/vdc/html/products.htm>.
851 tristate "Epson S1D13XXX framebuffer support"
853 select FB_CFB_FILLRECT
854 select FB_CFB_COPYAREA
855 select FB_CFB_IMAGEBLIT
857 Support for S1D13XXX framebuffer device family (currently only
858 working with S1D13806). Product specs at
859 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
862 tristate "AT91/AT32 LCD Controller support"
863 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || AVR32)
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This enables support for the AT91/AT32 LCD Controller.
871 bool "Frame Buffer in internal SRAM"
872 depends on FB_ATMEL && ARCH_AT91SAM9261
874 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
875 to let frame buffer in external SDRAM.
878 bool "Use a STN display with AT91/AT32 LCD Controller"
879 depends on FB_ATMEL && MACH_AT91SAM9261EK
882 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
883 Controller. Say N if you want to connect a TFT.
888 tristate "nVidia Framebuffer Support"
890 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
891 select FB_MODE_HELPERS
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
898 This driver supports graphics boards with the nVidia chips, TNT
899 and newer. For very old chipsets, such as the RIVA128, then use
901 Say Y if you have such a graphics board.
903 To compile this driver as a module, choose M here: the
904 module will be called nvidiafb.
907 bool "Enable DDC Support"
911 This enables I2C support for nVidia Chipsets. This is used
912 only for getting EDID information from the attached display
913 allowing for robust video mode handling and switching.
915 Because fbdev-2.6 requires that drivers must be able to
916 independently validate video mode parameters, you should say Y
919 config FB_NVIDIA_DEBUG
920 bool "Lots of debug output"
924 Say Y here if you want the nVidia driver to output all sorts
925 of debugging information to provide to the maintainer when
926 something goes wrong.
928 config FB_NVIDIA_BACKLIGHT
929 bool "Support for backlight control"
933 Say Y here if you want to control the backlight of your display.
936 tristate "nVidia Riva support"
938 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
939 select FB_MODE_HELPERS
940 select FB_CFB_FILLRECT
941 select FB_CFB_COPYAREA
942 select FB_CFB_IMAGEBLIT
946 This driver supports graphics boards with the nVidia Riva/Geforce
948 Say Y if you have such a graphics board.
950 To compile this driver as a module, choose M here: the
951 module will be called rivafb.
954 bool "Enable DDC Support"
958 This enables I2C support for nVidia Chipsets. This is used
959 only for getting EDID information from the attached display
960 allowing for robust video mode handling and switching.
962 Because fbdev-2.6 requires that drivers must be able to
963 independently validate video mode parameters, you should say Y
967 bool "Lots of debug output"
971 Say Y here if you want the Riva driver to output all sorts
972 of debugging information to provide to the maintainer when
973 something goes wrong.
975 config FB_RIVA_BACKLIGHT
976 bool "Support for backlight control"
980 Say Y here if you want to control the backlight of your display.
983 tristate "Intel 810/815 support (EXPERIMENTAL)"
984 depends on FB && EXPERIMENTAL && PCI && X86_32
987 select FB_MODE_HELPERS
988 select FB_CFB_FILLRECT
989 select FB_CFB_COPYAREA
990 select FB_CFB_IMAGEBLIT
993 This driver supports the on-board graphics built in to the Intel 810
994 and 815 chipsets. Say Y if you have and plan to use such a board.
996 To compile this driver as a module, choose M here: the
997 module will be called i810fb.
999 For more information, please read
1000 <file:Documentation/fb/intel810.txt>
1003 bool "use VESA Generalized Timing Formula"
1006 If you say Y, then the VESA standard, Generalized Timing Formula
1007 or GTF, will be used to calculate the required video timing values
1008 per video mode. Since the GTF allows nondiscrete timings
1009 (nondiscrete being a range of values as opposed to discrete being a
1010 set of values), you'll be able to use any combination of horizontal
1011 and vertical resolutions, and vertical refresh rates without having
1012 to specify your own timing parameters. This is especially useful
1013 to maximize the performance of an aging display, or if you just
1014 have a display with nonstandard dimensions. A VESA compliant
1015 monitor is recommended, but can still work with non-compliant ones.
1016 If you need or want this, then select this option. The timings may
1017 not be compliant with Intel's recommended values. Use at your own
1020 If you say N, the driver will revert to discrete video timings
1021 using a set recommended by Intel in their documentation.
1026 bool "Enable DDC Support"
1027 depends on FB_I810 && FB_I810_GTF
1032 tristate "Intel LE80578 (Vermilion) support"
1033 depends on FB && PCI && X86
1034 select FB_MODE_HELPERS
1035 select FB_CFB_FILLRECT
1036 select FB_CFB_COPYAREA
1037 select FB_CFB_IMAGEBLIT
1039 This driver supports the LE80578 (Vermilion Range) chipset
1041 config FB_CARILLO_RANCH
1042 tristate "Intel Carillo Ranch support"
1043 depends on FB_LE80578 && FB && PCI && X86
1045 This driver supports the LE80578 (Carillo Ranch) board
1048 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
1049 depends on FB && EXPERIMENTAL && PCI && X86
1052 select FB_MODE_HELPERS
1053 select FB_CFB_FILLRECT
1054 select FB_CFB_COPYAREA
1055 select FB_CFB_IMAGEBLIT
1057 This driver supports the on-board graphics built in to the Intel
1058 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
1059 Say Y if you have and plan to use such a board.
1061 If you say Y here and want DDC/I2C support you must first say Y to
1062 "I2C support" and "I2C bit-banging support" in the character devices
1065 If you say M here then "I2C support" and "I2C bit-banging support"
1066 can be build either as modules or built-in.
1068 To compile this driver as a module, choose M here: the
1069 module will be called intelfb.
1071 For more information, please read <file:Documentation/fb/intelfb.txt>
1073 config FB_INTEL_DEBUG
1074 bool "Intel driver Debug Messages"
1077 Say Y here if you want the Intel driver to output all sorts
1078 of debugging information to provide to the maintainer when
1079 something goes wrong.
1082 bool "DDC/I2C for Intel framebuffer support"
1087 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1090 tristate "Matrox acceleration"
1091 depends on FB && PCI
1092 select FB_CFB_FILLRECT
1093 select FB_CFB_COPYAREA
1094 select FB_CFB_IMAGEBLIT
1095 select FB_TILEBLITTING
1096 select FB_MACMODES if PPC_PMAC
1098 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1099 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1100 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1101 Matrox G400, G450 or G550 card in your box.
1103 To compile this driver as a module, choose M here: the
1104 module will be called matroxfb.
1106 You can pass several parameters to the driver at boot time or at
1107 module load time. The parameters look like "video=matrox:XXX", and
1108 are described in <file:Documentation/fb/matroxfb.txt>.
1110 config FB_MATROX_MILLENIUM
1111 bool "Millennium I/II support"
1112 depends on FB_MATROX
1114 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1115 video card. If you select "Advanced lowlevel driver options" below,
1116 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1117 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1118 also use font widths different from 8.
1120 config FB_MATROX_MYSTIQUE
1121 bool "Mystique support"
1122 depends on FB_MATROX
1124 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1125 video card. If you select "Advanced lowlevel driver options" below,
1126 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1127 packed pixel and 32 bpp packed pixel. You can also use font widths
1131 bool "G100/G200/G400/G450/G550 support"
1132 depends on FB_MATROX
1134 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1135 video card. If you select "Advanced lowlevel driver options", you
1136 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1137 pixel and 32 bpp packed pixel. You can also use font widths
1140 If you need support for G400 secondary head, you must first say Y to
1141 "I2C support" in the character devices section, and then to
1142 "Matrox I2C support" and "G400 second head support" here in the
1143 framebuffer section. G450/G550 secondary head and digital output
1144 are supported without additional modules.
1146 The driver starts in monitor mode. You must use the matroxset tool
1147 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1148 swap primary and secondary head outputs, or to change output mode.
1149 Secondary head driver always start in 640x480 resolution and you
1150 must use fbset to change it.
1152 Do not forget that second head supports only 16 and 32 bpp
1153 packed pixels, so it is a good idea to compile them into the kernel
1154 too. You can use only some font widths, as the driver uses generic
1155 painting procedures (the secondary head does not use acceleration
1158 G450/G550 hardware can display TV picture only from secondary CRTC,
1159 and it performs no scaling, so picture must have 525 or 625 lines.
1161 config FB_MATROX_I2C
1162 tristate "Matrox I2C support"
1163 depends on FB_MATROX
1166 This drivers creates I2C buses which are needed for accessing the
1167 DDC (I2C) bus present on all Matroxes, an I2C bus which
1168 interconnects Matrox optional devices, like MGA-TVO on G200 and
1169 G400, and the secondary head DDC bus, present on G400 only.
1171 You can say Y or M here if you want to experiment with monitor
1172 detection code. You must say Y or M here if you want to use either
1173 second head of G400 or MGA-TVO on G200 or G400.
1175 If you compile it as module, it will create a module named
1178 config FB_MATROX_MAVEN
1179 tristate "G400 second head support"
1180 depends on FB_MATROX_G && FB_MATROX_I2C
1182 WARNING !!! This support does not work with G450 !!!
1184 Say Y or M here if you want to use a secondary head (meaning two
1185 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1186 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1187 secondary head output is blanked while you are in X. With XFree
1188 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1189 the fbdev driver on first head and the fbdev driver on second head.
1191 If you compile it as module, two modules are created,
1192 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1193 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1194 also load i2c-matroxfb to get it to run.
1196 The driver starts in monitor mode and you must use the matroxset
1198 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1199 PAL or NTSC or to swap primary and secondary head outputs.
1200 Secondary head driver also always start in 640x480 resolution, you
1201 must use fbset to change it.
1203 Also do not forget that second head supports only 16 and 32 bpp
1204 packed pixels, so it is a good idea to compile them into the kernel
1205 too. You can use only some font widths, as the driver uses generic
1206 painting procedures (the secondary head does not use acceleration
1209 config FB_MATROX_MULTIHEAD
1210 bool "Multihead support"
1211 depends on FB_MATROX
1213 Say Y here if you have more than one (supported) Matrox device in
1214 your computer and you want to use all of them for different monitors
1215 ("multihead"). If you have only one device, you should say N because
1216 the driver compiled with Y is larger and a bit slower, especially on
1219 If you said M to "Matrox unified accelerated driver" and N here, you
1220 will still be able to use several Matrox devices simultaneously:
1221 insert several instances of the module matroxfb into the kernel
1222 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1223 for the different Matrox devices. This method is slightly faster but
1224 uses 40 KB of kernel memory per Matrox card.
1226 There is no need for enabling 'Matrox multihead support' if you have
1227 only one Matrox card in the box.
1230 tristate "ATI Radeon display support"
1231 depends on FB && PCI
1232 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1233 select FB_MODE_HELPERS
1234 select FB_CFB_FILLRECT
1235 select FB_CFB_COPYAREA
1236 select FB_CFB_IMAGEBLIT
1237 select FB_MACMODES if PPC_OF
1239 Choose this option if you want to use an ATI Radeon graphics card as
1240 a framebuffer device. There are both PCI and AGP versions. You
1241 don't need to choose this to run the Radeon in plain VGA mode.
1243 If you say Y here and want DDC/I2C support you must first say Y to
1244 "I2C support" and "I2C bit-banging support" in the character devices
1247 If you say M here then "I2C support" and "I2C bit-banging support"
1248 can be build either as modules or built-in.
1250 There is a product page at
1251 http://apps.ati.com/ATIcompare/
1253 config FB_RADEON_I2C
1254 bool "DDC/I2C for ATI Radeon support"
1255 depends on FB_RADEON
1259 Say Y here if you want DDC/I2C support for your Radeon board.
1261 config FB_RADEON_BACKLIGHT
1262 bool "Support for backlight control"
1263 depends on FB_RADEON
1266 Say Y here if you want to control the backlight of your display.
1268 config FB_RADEON_DEBUG
1269 bool "Lots of debug output from Radeon driver"
1270 depends on FB_RADEON
1273 Say Y here if you want the Radeon driver to output all sorts
1274 of debugging information to provide to the maintainer when
1275 something goes wrong.
1278 tristate "ATI Rage128 display support"
1279 depends on FB && PCI
1280 select FB_CFB_FILLRECT
1281 select FB_CFB_COPYAREA
1282 select FB_CFB_IMAGEBLIT
1283 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1284 select FB_MACMODES if PPC_PMAC
1286 This driver supports graphics boards with the ATI Rage128 chips.
1287 Say Y if you have such a graphics board and read
1288 <file:Documentation/fb/aty128fb.txt>.
1290 To compile this driver as a module, choose M here: the
1291 module will be called aty128fb.
1293 config FB_ATY128_BACKLIGHT
1294 bool "Support for backlight control"
1295 depends on FB_ATY128
1298 Say Y here if you want to control the backlight of your display.
1301 tristate "ATI Mach64 display support" if PCI || ATARI
1302 depends on FB && !SPARC32
1303 select FB_CFB_FILLRECT
1304 select FB_CFB_COPYAREA
1305 select FB_CFB_IMAGEBLIT
1306 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1307 select FB_MACMODES if PPC
1309 This driver supports graphics boards with the ATI Mach64 chips.
1310 Say Y if you have such a graphics board.
1312 To compile this driver as a module, choose M here: the
1313 module will be called atyfb.
1316 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1317 depends on PCI && FB_ATY
1318 default y if SPARC64 && PCI
1320 Say Y here to support use of ATI's 64-bit Rage boards (or other
1321 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1322 framebuffer device. The ATI product support page for these boards
1323 is at <http://support.ati.com/products/pc/mach64/>.
1325 config FB_ATY_GENERIC_LCD
1326 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1327 depends on FB_ATY_CT
1329 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1330 Rage XC, or Rage XL chipset.
1333 bool "Mach64 GX support" if PCI
1337 Say Y here to support use of the ATI Mach64 Graphics Expression
1338 board (or other boards based on the Mach64 GX chipset) as a
1339 framebuffer device. The ATI product support page for these boards
1341 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1343 config FB_ATY_BACKLIGHT
1344 bool "Support for backlight control"
1348 Say Y here if you want to control the backlight of your display.
1351 tristate "S3 Trio/Virge support"
1352 depends on FB && PCI
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1356 select FB_TILEBLITTING
1359 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1361 Driver for graphics boards with S3 Trio / S3 Virge chip.
1364 tristate "S3 Savage support"
1365 depends on FB && PCI && EXPERIMENTAL
1366 select FB_MODE_HELPERS
1367 select FB_CFB_FILLRECT
1368 select FB_CFB_COPYAREA
1369 select FB_CFB_IMAGEBLIT
1372 This driver supports notebooks and computers with S3 Savage PCI/AGP
1375 Say Y if you have such a graphics card.
1377 To compile this driver as a module, choose M here; the module
1378 will be called savagefb.
1380 config FB_SAVAGE_I2C
1381 bool "Enable DDC2 Support"
1382 depends on FB_SAVAGE
1385 This enables I2C support for S3 Savage Chipsets. This is used
1386 only for getting EDID information from the attached display
1387 allowing for robust video mode handling and switching.
1389 Because fbdev-2.6 requires that drivers must be able to
1390 independently validate video mode parameters, you should say Y
1393 config FB_SAVAGE_ACCEL
1394 bool "Enable Console Acceleration"
1395 depends on FB_SAVAGE
1398 This option will compile in console acceleration support. If
1399 the resulting framebuffer console has bothersome glitches, then
1403 tristate "SiS/XGI display support"
1404 depends on FB && PCI
1405 select FB_CFB_FILLRECT
1406 select FB_CFB_COPYAREA
1407 select FB_CFB_IMAGEBLIT
1409 This is the frame buffer device driver for the SiS 300, 315, 330
1410 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1411 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1413 To compile this driver as a module, choose M here; the module
1414 will be called sisfb.
1417 bool "SiS 300 series support"
1420 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1423 bool "SiS 315/330/340 series and XGI support"
1426 Say Y here to support use of the SiS 315, 330 and 340 series
1427 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1428 as XGI V3XT, V5, V8 and Z7.
1431 tristate "NeoMagic display support"
1432 depends on FB && PCI
1433 select FB_MODE_HELPERS
1434 select FB_CFB_FILLRECT
1435 select FB_CFB_COPYAREA
1436 select FB_CFB_IMAGEBLIT
1439 This driver supports notebooks with NeoMagic PCI chips.
1440 Say Y if you have such a graphics card.
1442 To compile this driver as a module, choose M here: the
1443 module will be called neofb.
1446 tristate "IMG Kyro support"
1447 depends on FB && PCI
1448 select FB_CFB_FILLRECT
1449 select FB_CFB_COPYAREA
1450 select FB_CFB_IMAGEBLIT
1452 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1455 To compile this driver as a module, choose M here: the
1456 module will be called kyrofb.
1459 tristate "3Dfx Banshee/Voodoo3 display support"
1460 depends on FB && PCI
1461 select FB_CFB_IMAGEBLIT
1462 select FB_CFB_FILLRECT
1463 select FB_CFB_COPYAREA
1465 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1466 chips. Say Y if you have such a graphics board.
1468 To compile this driver as a module, choose M here: the
1469 module will be called tdfxfb.
1471 config FB_3DFX_ACCEL
1472 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1473 depends on FB_3DFX && EXPERIMENTAL
1475 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1476 with acceleration functions.
1480 tristate "3Dfx Voodoo Graphics (sst1) support"
1481 depends on FB && PCI
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1486 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1487 Voodoo2 (cvg) based graphics card.
1489 To compile this driver as a module, choose M here: the
1490 module will be called sstfb.
1492 WARNING: Do not use any application that uses the 3D engine
1493 (namely glide) while using this driver.
1494 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1495 options and other important info support.
1498 tristate "VIA VT8623 support"
1499 depends on FB && PCI
1500 select FB_CFB_FILLRECT
1501 select FB_CFB_COPYAREA
1502 select FB_CFB_IMAGEBLIT
1503 select FB_TILEBLITTING
1506 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1508 Driver for CastleRock integrated graphics core in the
1509 VIA VT8623 [Apollo CLE266] chipset.
1512 tristate "Cyberblade/i1 support"
1513 depends on FB && PCI && X86_32 && !64BIT
1514 select FB_CFB_IMAGEBLIT
1517 This driver is supposed to support the Trident Cyberblade/i1
1518 graphics core integrated in the VIA VT8601A North Bridge,
1519 also known as VIA Apollo PLE133.
1522 - Developed, tested and working on EPIA 5000 and EPIA 800.
1523 - Does work reliable on all systems with CRT/LCD connected to
1525 - Should work on systems that do use the internal LCD port, but
1526 this is absolutely not tested.
1528 Character imageblit, copyarea and rectangle fill are hw accelerated,
1529 ypan scrolling is used by default.
1531 Please do read <file:Documentation/fb/cyblafb/*>.
1533 To compile this driver as a module, choose M here: the
1534 module will be called cyblafb.
1537 tristate "Trident support"
1538 depends on FB && PCI
1539 select FB_CFB_FILLRECT
1540 select FB_CFB_COPYAREA
1541 select FB_CFB_IMAGEBLIT
1543 This driver is supposed to support graphics boards with the
1544 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1545 but also on some motherboards. For more information, read
1546 <file:Documentation/fb/tridentfb.txt>
1548 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1551 Say Y if you have such a graphics board.
1554 To compile this driver as a module, choose M here: the
1555 module will be called tridentfb.
1557 config FB_TRIDENT_ACCEL
1558 bool "Trident Acceleration functions (EXPERIMENTAL)"
1559 depends on FB_TRIDENT && EXPERIMENTAL
1561 This will compile the Trident frame buffer device with
1562 acceleration functions.
1565 tristate "ARK 2000PV support"
1566 depends on FB && PCI
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1570 select FB_TILEBLITTING
1573 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1575 Driver for PCI graphics boards with ARK 2000PV chip
1576 and ICS 5342 RAMDAC.
1579 tristate "Permedia3 support (EXPERIMENTAL)"
1580 depends on FB && PCI && EXPERIMENTAL
1581 select FB_CFB_FILLRECT
1582 select FB_CFB_COPYAREA
1583 select FB_CFB_IMAGEBLIT
1585 This is the frame buffer device driver for the 3DLabs Permedia3
1586 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1587 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1588 and maybe other boards.
1591 bool "Au1100 LCD Driver"
1592 depends on (FB = y) && MIPS && SOC_AU1100
1593 select FB_CFB_FILLRECT
1594 select FB_CFB_COPYAREA
1595 select FB_CFB_IMAGEBLIT
1597 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1598 various panels and CRTs by passing in kernel cmd line option
1599 au1100fb:panel=<name>.
1602 bool "Au1200 LCD Driver"
1603 depends on (FB = y) && MIPS && SOC_AU1200
1604 select FB_CFB_FILLRECT
1605 select FB_CFB_COPYAREA
1606 select FB_CFB_IMAGEBLIT
1608 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1609 various panels and CRTs by passing in kernel cmd line option
1610 au1200fb:panel=<name>.
1612 source "drivers/video/geode/Kconfig"
1615 tristate "HD64461 Frame Buffer support"
1616 depends on FB && HD64461
1617 select FB_CFB_FILLRECT
1618 select FB_CFB_COPYAREA
1619 select FB_CFB_IMAGEBLIT
1621 This is the frame buffer device driver for the Hitachi HD64461 LCD
1625 bool "PMAG-AA TURBOchannel framebuffer support"
1626 depends on (FB = y) && TC
1627 select FB_CFB_FILLRECT
1628 select FB_CFB_COPYAREA
1629 select FB_CFB_IMAGEBLIT
1631 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1632 used mainly in the MIPS-based DECstation series.
1635 tristate "PMAG-BA TURBOchannel framebuffer support"
1637 select FB_CFB_FILLRECT
1638 select FB_CFB_COPYAREA
1639 select FB_CFB_IMAGEBLIT
1641 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1642 used mainly in the MIPS-based DECstation series.
1645 tristate "PMAGB-B TURBOchannel framebuffer support"
1647 select FB_CFB_FILLRECT
1648 select FB_CFB_COPYAREA
1649 select FB_CFB_IMAGEBLIT
1651 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1652 in the MIPS-based DECstation series. The card is currently only
1653 supported in 1280x1024x8 mode.
1656 bool "Maxine (Personal DECstation) onboard framebuffer support"
1657 depends on (FB = y) && MACH_DECSTATION
1658 select FB_CFB_FILLRECT
1659 select FB_CFB_COPYAREA
1660 select FB_CFB_IMAGEBLIT
1662 Support for the onboard framebuffer (1024x768x8) in the Personal
1663 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1667 bool "G364 frame buffer support"
1668 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1669 select FB_CFB_FILLRECT
1670 select FB_CFB_COPYAREA
1671 select FB_CFB_IMAGEBLIT
1673 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1674 Olivetti M700-10 systems.
1677 bool "Motorola 68328 native frame buffer support"
1678 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1679 select FB_CFB_FILLRECT
1680 select FB_CFB_COPYAREA
1681 select FB_CFB_IMAGEBLIT
1683 Say Y here if you want to support the built-in frame buffer of
1684 the Motorola 68328 CPU family.
1687 tristate "PXA LCD framebuffer support"
1688 depends on FB && ARCH_PXA
1689 select FB_CFB_FILLRECT
1690 select FB_CFB_COPYAREA
1691 select FB_CFB_IMAGEBLIT
1693 Frame buffer driver for the built-in LCD controller in the Intel
1696 This driver is also available as a module ( = code which can be
1697 inserted and removed from the running kernel whenever you want). The
1698 module will be called pxafb. If you want to compile it as a module,
1699 say M here and read <file:Documentation/kbuild/modules.txt>.
1703 config FB_PXA_PARAMETERS
1704 bool "PXA LCD command line parameters"
1708 Enable the use of kernel command line or module parameters
1709 to configure the physical properties of the LCD panel when
1710 using the PXA LCD driver.
1712 This option allows you to override the panel parameters
1713 supplied by the platform in order to support multiple
1714 different models of flatpanel. If you will only be using a
1715 single model of flatpanel then you can safely leave this
1718 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1721 tristate "2700G LCD framebuffer support"
1722 depends on FB && ARCH_PXA
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1731 bool "Enable debugging info via debugfs"
1732 depends on FB_MBX && DEBUG_FS
1735 Enable this if you want debugging information using the debug
1736 filesystem (debugfs)
1741 tristate "W100 frame buffer support"
1742 depends on FB && PXA_SHARPSL
1743 select FB_CFB_FILLRECT
1744 select FB_CFB_COPYAREA
1745 select FB_CFB_IMAGEBLIT
1747 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1749 This driver is also available as a module ( = code which can be
1750 inserted and removed from the running kernel whenever you want). The
1751 module will be called w100fb. If you want to compile it as a module,
1752 say M here and read <file:Documentation/kbuild/modules.txt>.
1757 tristate "S3C2410 LCD framebuffer support"
1758 depends on FB && ARCH_S3C2410
1759 select FB_CFB_FILLRECT
1760 select FB_CFB_COPYAREA
1761 select FB_CFB_IMAGEBLIT
1763 Frame buffer driver for the built-in LCD controller in the Samsung
1766 This driver is also available as a module ( = code which can be
1767 inserted and removed from the running kernel whenever you want). The
1768 module will be called s3c2410fb. If you want to compile it as a module,
1769 say M here and read <file:Documentation/kbuild/modules.txt>.
1772 config FB_S3C2410_DEBUG
1773 bool "S3C2410 lcd debug messages"
1774 depends on FB_S3C2410
1776 Turn on debugging messages. Note that you can set/unset at run time
1780 tristate "Silicon Motion SM501 framebuffer support"
1781 depends on FB && MFD_SM501
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1786 Frame buffer driver for the CRT and LCD controllers in the Silicon
1789 This driver is also available as a module ( = code which can be
1790 inserted and removed from the running kernel whenever you want). The
1791 module will be called sm501fb. If you want to compile it as a module,
1792 say M here and read <file:Documentation/modules.txt>.
1797 config FB_PNX4008_DUM
1798 tristate "Display Update Module support on Philips PNX4008 board"
1799 depends on FB && ARCH_PNX4008
1801 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1803 config FB_PNX4008_DUM_RGB
1804 tristate "RGB Framebuffer support on Philips PNX4008 board"
1805 depends on FB_PNX4008_DUM
1806 select FB_CFB_FILLRECT
1807 select FB_CFB_COPYAREA
1808 select FB_CFB_IMAGEBLIT
1810 Say Y here to enable support for PNX4008 RGB Framebuffer
1812 config FB_IBM_GXT4500
1813 tristate "Framebuffer support for IBM GXT4500P adaptor"
1815 select FB_CFB_FILLRECT
1816 select FB_CFB_COPYAREA
1817 select FB_CFB_IMAGEBLIT
1819 Say Y here to enable support for the IBM GXT4500P display
1820 adaptor, found on some IBM System P (pSeries) machines.
1823 tristate "PS3 GPU framebuffer driver"
1824 depends on FB && PS3_PS3AV
1825 select FB_SYS_FILLRECT
1826 select FB_SYS_COPYAREA
1827 select FB_SYS_IMAGEBLIT
1829 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1831 Include support for the virtual frame buffer in the PS3 platform.
1833 config FB_PS3_DEFAULT_SIZE_M
1834 int "PS3 default frame buffer size (in MiB)"
1838 This is the default size (in MiB) of the virtual frame buffer in
1840 The default value can be overridden on the kernel command line
1841 using the "ps3fb" option (e.g. "ps3fb=9M");
1844 tristate "Xilinx frame buffer support"
1845 depends on FB && XILINX_VIRTEX
1846 select FB_CFB_FILLRECT
1847 select FB_CFB_COPYAREA
1848 select FB_CFB_IMAGEBLIT
1850 Include support for the Xilinx ML300/ML403 reference design
1851 framebuffer. ML300 carries a 640*480 LCD display on the board,
1852 ML403 uses a standard DB15 VGA connector.
1855 source "drivers/video/omap/Kconfig"
1859 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1861 select FB_SYS_FILLRECT
1862 select FB_SYS_COPYAREA
1863 select FB_SYS_IMAGEBLIT
1866 This is a `virtual' frame buffer device. It operates on a chunk of
1867 unswappable kernel memory instead of on the memory of a graphics
1868 board. This means you cannot see any output sent to this frame
1869 buffer device, while it does consume precious memory. The main use
1870 of this frame buffer device is testing and debugging the frame
1871 buffer subsystem. Do NOT enable it for normal systems! To protect
1872 the innocent, it has to be enabled explicitly at boot time using the
1873 kernel option `video=vfb:'.
1875 To compile this driver as a module, choose M here: the
1876 module will be called vfb. In order to load it, you must use
1877 the vfb_enable=1 option.
1882 source "drivers/video/console/Kconfig"
1885 if FB || SGI_NEWPORT_CONSOLE
1886 source "drivers/video/logo/Kconfig"