5 menu "Graphics support"
8 source "drivers/char/agp/Kconfig"
10 source "drivers/char/drm/Kconfig"
16 config VIDEO_OUTPUT_CONTROL
17 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_CFB_REV_PIXELS_IN_BYTE
111 Allow generic frame-buffer functions to work on displays with 1, 2
112 and 4 bits per pixel depths which has opposite order of pixels in
113 byte order to bytes in long order.
115 config FB_SYS_FILLRECT
120 Include the sys_fillrect function for generic software rectangle
121 filling. This is used by drivers that don't provide their own
122 (accelerated) version and the framebuffer is in system RAM.
124 config FB_SYS_COPYAREA
129 Include the sys_copyarea function for generic software area copying.
130 This is used by drivers that don't provide their own (accelerated)
131 version and the framebuffer is in system RAM.
133 config FB_SYS_IMAGEBLIT
138 Include the sys_imageblit function for generic software image
139 blitting. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
147 config FB_DEFERRED_IO
157 Common utility functions useful to fbdev drivers of VGA-based
168 select BACKLIGHT_LCD_SUPPORT
169 select BACKLIGHT_CLASS_DEVICE
172 config FB_MODE_HELPERS
173 bool "Enable Video Mode Handling Helpers"
177 This enables functions for handling video modes using the
178 Generalized Timing Formula and the EDID parser. A few drivers rely
179 on this feature such as the radeonfb, rivafb, and the i810fb. If
180 your driver does not take advantage of this feature, choosing Y will
181 just increase the kernel size by about 5K.
183 config FB_TILEBLITTING
184 bool "Enable Tile Blitting Support"
188 This enables tile blitting. Tile blitting is a drawing technique
189 where the screen is divided into rectangular sections (tiles), whereas
190 the standard blitting divides the screen into pixels. Because the
191 default drawing element is a tile, drawing functions will be passed
192 parameters in terms of number of tiles instead of number of pixels.
193 For example, to draw a single character, instead of using bitmaps,
194 an index to an array of bitmaps will be used. To clear or move a
195 rectangular section of a screen, the rectangle will be described in
196 terms of number of tiles in the x- and y-axis.
198 This is particularly important to one driver, matroxfb. If
201 comment "Frame buffer hardware drivers"
205 tristate "Cirrus Logic support"
206 depends on FB && (ZORRO || PCI)
207 select FB_CFB_FILLRECT
208 select FB_CFB_COPYAREA
209 select FB_CFB_IMAGEBLIT
211 This enables support for Cirrus Logic GD542x/543x based boards on
212 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
214 If you have a PCI-based system, this enables support for these
215 chips: GD-543x, GD-544x, GD-5480.
217 Please read the file <file:Documentation/fb/cirrusfb.txt>.
219 Say N unless you have such a graphics board or plan to get one
220 before you next recompile the kernel.
223 tristate "Permedia2 support"
224 depends on FB && ((AMIGA && BROKEN) || PCI)
225 select FB_CFB_FILLRECT
226 select FB_CFB_COPYAREA
227 select FB_CFB_IMAGEBLIT
229 This is the frame buffer device driver for the Permedia2 AGP frame
230 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
232 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
234 config FB_PM2_FIFO_DISCONNECT
235 bool "enable FIFO disconnect feature"
236 depends on FB_PM2 && PCI
238 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
241 tristate "ARM PrimeCell PL110 support"
242 depends on FB && ARM && ARM_AMBA
243 select FB_CFB_FILLRECT
244 select FB_CFB_COPYAREA
245 select FB_CFB_IMAGEBLIT
247 This framebuffer device driver is for the ARM PrimeCell PL110
248 Colour LCD controller. ARM PrimeCells provide the building
249 blocks for System on a Chip devices.
251 If you want to compile this as a module (=code which can be
252 inserted into and removed from the running kernel), say M
253 here and read <file:Documentation/kbuild/modules.txt>. The module
254 will be called amba-clcd.
258 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
260 default FB_ARMCLCD_SHARP_LQ035Q7DB02
262 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
263 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
265 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
266 color QVGA, HRTFT panel. The LogicPD device includes
267 an integrated HRTFT controller IC.
268 The native resolution is 240x320.
270 config FB_ARMCLCD_SHARP_LQ057Q3DC02
271 bool "LogicPD LCD 5.7\" QVGA"
273 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
274 color QVGA, TFT panel. The LogicPD device includes an
275 The native resolution is 320x240.
277 config FB_ARMCLCD_SHARP_LQ64D343
278 bool "LogicPD LCD 6.4\" VGA"
280 This is an implementation of the Sharp LQ64D343, a 6.4"
281 color VGA, TFT panel. The LogicPD device includes an
282 The native resolution is 640x480.
284 config FB_ARMCLCD_SHARP_LQ10D368
285 bool "LogicPD LCD 10.4\" VGA"
287 This is an implementation of the Sharp LQ10D368, a 10.4"
288 color VGA, TFT panel. The LogicPD device includes an
289 The native resolution is 640x480.
292 config FB_ARMCLCD_SHARP_LQ121S1DG41
293 bool "LogicPD LCD 12.1\" SVGA"
295 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
296 color SVGA, TFT panel. The LogicPD device includes an
297 The native resolution is 800x600.
299 This panel requires a clock rate may be an integer fraction
300 of the base LCDCLK frequency. The driver will select the
301 highest frequency available that is lower than the maximum
302 allowed. The panel may flicker if the clock rate is
303 slower than the recommended minimum.
305 config FB_ARMCLCD_AUO_A070VW01_WIDE
306 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
308 This is an implementation of the AU Optronics, a 7.0"
309 WIDE Color. The native resolution is 234x480.
311 config FB_ARMCLCD_HITACHI
312 bool "Hitachi Wide Screen 800x480"
314 This is an implementation of the Hitachi 800x480.
320 bool "Acorn VIDC support"
321 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
322 select FB_CFB_FILLRECT
323 select FB_CFB_COPYAREA
324 select FB_CFB_IMAGEBLIT
326 This is the frame buffer device driver for the Acorn VIDC graphics
327 hardware found in Acorn RISC PCs and other ARM-based machines. If
331 bool "CLPS711X LCD support"
332 depends on (FB = y) && ARM && ARCH_CLPS711X
333 select FB_CFB_FILLRECT
334 select FB_CFB_COPYAREA
335 select FB_CFB_IMAGEBLIT
337 Say Y to enable the Framebuffer driver for the CLPS7111 and
341 bool "SA-1100 LCD support"
342 depends on (FB = y) && ARM && ARCH_SA1100
343 select FB_CFB_FILLRECT
344 select FB_CFB_COPYAREA
345 select FB_CFB_IMAGEBLIT
347 This is a framebuffer device for the SA-1100 LCD Controller.
348 See <http://www.linux-fbdev.org/> for information on framebuffer
351 If you plan to use the LCD display with your SA-1100 system, say
355 tristate "Motorola i.MX LCD support"
356 depends on FB && ARM && ARCH_IMX
357 select FB_CFB_FILLRECT
358 select FB_CFB_COPYAREA
359 select FB_CFB_IMAGEBLIT
362 tristate "CyberPro 2000/2010/5000 support"
363 depends on FB && PCI && (BROKEN || !SPARC64)
364 select FB_CFB_FILLRECT
365 select FB_CFB_COPYAREA
366 select FB_CFB_IMAGEBLIT
368 This enables support for the Integraphics CyberPro 20x0 and 5000
369 VGA chips used in the Rebel.com Netwinder and other machines.
370 Say Y if you have a NetWinder or a graphics card containing this
371 device, otherwise say N.
375 depends on (FB = y) && APOLLO
377 select FB_CFB_FILLRECT
378 select FB_CFB_IMAGEBLIT
382 depends on (FB = y) && Q40
384 select FB_CFB_FILLRECT
385 select FB_CFB_COPYAREA
386 select FB_CFB_IMAGEBLIT
389 tristate "Amiga native chipset support"
390 depends on FB && AMIGA
392 This is the frame buffer device driver for the builtin graphics
393 chipset found in Amigas.
395 To compile this driver as a module, choose M here: the
396 module will be called amifb.
399 bool "Amiga OCS chipset support"
402 This enables support for the original Agnus and Denise video chips,
403 found in the Amiga 1000 and most A500's and A2000's. If you intend
404 to run Linux on any of these systems, say Y; otherwise say N.
407 bool "Amiga ECS chipset support"
410 This enables support for the Enhanced Chip Set, found in later
411 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
412 you intend to run Linux on any of these systems, say Y; otherwise
416 bool "Amiga AGA chipset support"
419 This enables support for the Advanced Graphics Architecture (also
420 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
421 and CD32. If you intend to run Linux on any of these systems, say Y;
425 bool "Amiga FrameMaster II/Rainbow II support"
426 depends on (FB = y) && ZORRO
427 select FB_CFB_FILLRECT
428 select FB_CFB_COPYAREA
429 select FB_CFB_IMAGEBLIT
431 This is the frame buffer device driver for the Amiga FrameMaster
432 card from BSC (exhibited 1992 but not shipped as a CBM product).
435 tristate "Arc Monochrome LCD board support"
437 select FB_SYS_FILLRECT
438 select FB_SYS_COPYAREA
439 select FB_SYS_IMAGEBLIT
442 This enables support for the Arc Monochrome LCD board. The board
443 is based on the KS-108 lcd controller and is typically a matrix
444 of 2*n chips. This driver was tested with a 128x64 panel. This
445 driver supports it for use with x86 SBCs through a 16 bit GPIO
446 interface (8 bit data, 8 bit control). If you anticipate using
447 this driver, say Y or M; otherwise say N. You must specify the
448 GPIO IO address to be used for setting control and data.
451 bool "Atari native chipset support"
452 depends on (FB = y) && ATARI
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
457 This is the frame buffer device driver for the builtin graphics
458 chipset found in Ataris.
461 bool "Open Firmware frame buffer device support"
462 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
468 Say Y if you want support with Open Firmware for your graphics
472 bool "Apple \"control\" display support"
473 depends on (FB = y) && PPC_PMAC && PPC32
474 select FB_CFB_FILLRECT
475 select FB_CFB_COPYAREA
476 select FB_CFB_IMAGEBLIT
479 This driver supports a frame buffer for the graphics adapter in the
480 Power Macintosh 7300 and others.
483 bool "Apple \"platinum\" display support"
484 depends on (FB = y) && PPC_PMAC && PPC32
485 select FB_CFB_FILLRECT
486 select FB_CFB_COPYAREA
487 select FB_CFB_IMAGEBLIT
490 This driver supports a frame buffer for the "platinum" graphics
491 adapter in some Power Macintoshes.
494 bool "Apple \"valkyrie\" display support"
495 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
496 select FB_CFB_FILLRECT
497 select FB_CFB_COPYAREA
498 select FB_CFB_IMAGEBLIT
501 This driver supports a frame buffer for the "valkyrie" graphics
502 adapter in some Power Macintoshes.
505 bool "Chips 65550 display support"
506 depends on (FB = y) && PPC32 && PCI
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
511 This is the frame buffer device driver for the Chips & Technologies
512 65550 graphics chip in PowerBooks.
515 bool "Asiliant (Chips) 69000 display support"
516 depends on (FB = y) && PCI
517 select FB_CFB_FILLRECT
518 select FB_CFB_COPYAREA
519 select FB_CFB_IMAGEBLIT
521 This is the frame buffer device driver for the Asiliant 69030 chipset
524 bool "IMS Twin Turbo display support"
525 depends on (FB = y) && PCI
526 select FB_CFB_IMAGEBLIT
527 select FB_MACMODES if PPC
529 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
530 many Macintosh and compatible computers.
533 tristate "VGA 16-color graphics support"
534 depends on FB && (X86 || PPC)
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
539 select FONT_8x16 if FRAMEBUFFER_CONSOLE
541 This is the frame buffer device driver for VGA 16 color graphic
542 cards. Say Y if you have such a card.
544 To compile this driver as a module, choose M here: the
545 module will be called vga16fb.
547 config FB_BF54X_LQ043
548 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
549 depends on FB && (BF54x)
550 select FB_CFB_FILLRECT
551 select FB_CFB_COPYAREA
552 select FB_CFB_IMAGEBLIT
554 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
557 tristate "HP STI frame buffer device support"
558 depends on FB && PARISC
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
564 STI refers to the HP "Standard Text Interface" which is a set of
565 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
566 Enabling this option will implement the linux framebuffer device
567 using calls to the STI BIOS routines for initialisation.
569 If you enable this option, you will get a planar framebuffer device
570 /dev/fb which will work on the most common HP graphic cards of the
571 NGLE family, including the artist chips (in the 7xx and Bxxx series),
572 HCRX, HCRX24, CRX, CRX24 and VisEG series.
574 It is safe to enable this option, so you should probably say "Y".
577 bool "Generic Macintosh display support"
578 depends on (FB = y) && MAC
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
584 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
587 depends on (FB = y) && HP300
588 select FB_CFB_FILLRECT
589 select FB_CFB_IMAGEBLIT
593 tristate "TGA/SFB+ framebuffer support"
594 depends on FB && (ALPHA || TC)
595 select FB_CFB_FILLRECT
596 select FB_CFB_COPYAREA
597 select FB_CFB_IMAGEBLIT
600 This is the frame buffer device driver for generic TGA and SFB+
601 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
602 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
603 TURBOchannel cards, also known as PMAGD-A, -B and -C.
605 Due to hardware limitations ZLX-E2 and E3 cards are not supported
606 for DECstation 5000/200 systems. Additionally due to firmware
607 limitations these cards may cause troubles with booting DECstation
608 5000/240 and /260 systems, but are fully supported under Linux if
609 you manage to get it going. ;-)
611 Say Y if you have one of those.
614 tristate "Userspace VESA VGA graphics support"
615 depends on FB && CONNECTOR
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
619 select FB_MODE_HELPERS
621 This is the frame buffer driver for generic VBE 2.0 compliant
622 graphic cards. It can also take advantage of VBE 3.0 features,
623 such as refresh rate adjustment.
625 This driver generally provides more features than vesafb but
626 requires a userspace helper application called 'v86d'. See
627 <file:Documentation/fb/uvesafb.txt> for more information.
632 bool "VESA VGA graphics support"
633 depends on (FB = y) && X86
634 select FB_CFB_FILLRECT
635 select FB_CFB_COPYAREA
636 select FB_CFB_IMAGEBLIT
639 This is the frame buffer device driver for generic VESA 2.0
640 compliant graphic cards. The older VESA 1.2 cards are not supported.
641 You will get a boot time penguin logo at no additional cost. Please
642 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
645 bool "Intel-based Macintosh Framebuffer Support"
646 depends on (FB = y) && X86 && EFI
647 select FB_CFB_FILLRECT
648 select FB_CFB_COPYAREA
649 select FB_CFB_IMAGEBLIT
651 This is the frame buffer device driver for the Intel-based Macintosh
654 tristate "Hecuba board support"
655 depends on FB && X86 && MMU
656 select FB_SYS_FILLRECT
657 select FB_SYS_COPYAREA
658 select FB_SYS_IMAGEBLIT
660 select FB_DEFERRED_IO
662 This enables support for the Hecuba board. This driver was tested
663 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
664 interface (8 bit data, 4 bit control). If you anticipate using
665 this driver, say Y or M; otherwise say N. You must specify the
666 GPIO IO address to be used for setting control and data.
669 tristate "Hercules mono graphics support"
671 select FB_CFB_FILLRECT
672 select FB_CFB_COPYAREA
673 select FB_CFB_IMAGEBLIT
675 Say Y here if you have a Hercules mono graphics card.
677 To compile this driver as a module, choose M here: the
678 module will be called hgafb.
680 As this card technology is 15 years old, most people will answer N
684 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
685 depends on FB_HGA && EXPERIMENTAL
687 This will compile the Hercules mono graphics with
688 acceleration functions.
691 tristate "SGI Visual Workstation framebuffer support"
692 depends on FB && X86_VISWS
693 select FB_CFB_FILLRECT
694 select FB_CFB_COPYAREA
695 select FB_CFB_IMAGEBLIT
697 SGI Visual Workstation support for framebuffer graphics.
700 bool "SGI Graphics Backend frame buffer support"
701 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
702 select FB_CFB_FILLRECT
703 select FB_CFB_COPYAREA
704 select FB_CFB_IMAGEBLIT
706 This is the frame buffer device driver for SGI Graphics Backend.
707 This chip is used in SGI O2 and Visual Workstation 320/540.
710 int "Video memory size in MB"
714 This is the amount of memory reserved for the framebuffer,
715 which can be any value between 1MB and 8MB.
718 bool "SBUS and UPA framebuffers"
719 depends on (FB = y) && SPARC
721 Say Y if you want support for SBUS or UPA based frame buffer device.
725 depends on (FB = y) && (SPARC && FB_SBUS)
726 select FB_CFB_FILLRECT
727 select FB_CFB_COPYAREA
728 select FB_CFB_IMAGEBLIT
730 This is the frame buffer device driver for the BWtwo frame buffer.
733 bool "CGthree support"
734 depends on (FB = y) && (SPARC && FB_SBUS)
735 select FB_CFB_FILLRECT
736 select FB_CFB_COPYAREA
737 select FB_CFB_IMAGEBLIT
739 This is the frame buffer device driver for the CGthree frame buffer.
742 bool "CGsix (GX,TurboGX) support"
743 depends on (FB = y) && (SPARC && FB_SBUS)
744 select FB_CFB_COPYAREA
745 select FB_CFB_IMAGEBLIT
747 This is the frame buffer device driver for the CGsix (GX, TurboGX)
751 bool "Creator/Creator3D/Elite3D support"
752 depends on FB_SBUS && SPARC64
753 select FB_CFB_COPYAREA
754 select FB_CFB_IMAGEBLIT
756 This is the frame buffer device driver for the Creator, Creator3D,
757 and Elite3D graphics boards.
760 bool "TCX (SS4/SS5 only) support"
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
766 This is the frame buffer device driver for the TCX 24/8bit frame
770 bool "CGfourteen (SX) support"
772 select FB_CFB_FILLRECT
773 select FB_CFB_COPYAREA
774 select FB_CFB_IMAGEBLIT
776 This is the frame buffer device driver for the CGfourteen frame
777 buffer on Desktop SPARCsystems with the SX graphics option.
780 bool "P9100 (Sparcbook 3 only) support"
782 select FB_CFB_FILLRECT
783 select FB_CFB_COPYAREA
784 select FB_CFB_IMAGEBLIT
786 This is the frame buffer device driver for the P9100 card
787 supported on Sparcbook 3 machines.
790 bool "Leo (ZX) support"
792 select FB_CFB_FILLRECT
793 select FB_CFB_COPYAREA
794 select FB_CFB_IMAGEBLIT
796 This is the frame buffer device driver for the SBUS-based Sun ZX
797 (leo) frame buffer cards.
800 bool "IGA 168x display support"
801 depends on (FB = y) && SPARC32
802 select FB_CFB_FILLRECT
803 select FB_CFB_COPYAREA
804 select FB_CFB_IMAGEBLIT
806 This is the framebuffer device for the INTERGRAPHICS 1680 and
807 successor frame buffer cards.
810 bool "Sun XVR-500 3DLABS Wildcat support"
811 depends on (FB = y) && PCI && SPARC64
812 select FB_CFB_FILLRECT
813 select FB_CFB_COPYAREA
814 select FB_CFB_IMAGEBLIT
816 This is the framebuffer device for the Sun XVR-500 and similar
817 graphics cards based upon the 3DLABS Wildcat chipset. The driver
818 only works on sparc64 systems where the system firmware has
819 mostly initialized the card already. It is treated as a
820 completely dumb framebuffer device.
823 bool "Sun XVR-2500 3DLABS Wildcat support"
824 depends on (FB = y) && PCI && SPARC64
825 select FB_CFB_FILLRECT
826 select FB_CFB_COPYAREA
827 select FB_CFB_IMAGEBLIT
829 This is the framebuffer device for the Sun XVR-2500 and similar
830 graphics cards based upon the 3DLABS Wildcat chipset. The driver
831 only works on sparc64 systems where the system firmware has
832 mostly initialized the card already. It is treated as a
833 completely dumb framebuffer device.
836 tristate "NEC PowerVR 2 display support"
837 depends on FB && SH_DREAMCAST
838 select FB_CFB_FILLRECT
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 Say Y here if you have a PowerVR 2 card in your box. If you plan to
843 run linux on your Dreamcast, you will have to say Y here.
844 This driver may or may not work on other PowerVR 2 cards, but is
845 totally untested. Use at your own risk. If unsure, say N.
847 To compile this driver as a module, choose M here: the
848 module will be called pvr2fb.
850 You can pass several parameters to the driver at boot time or at
851 module load time. The parameters look like "video=pvr2:XXX", where
852 the meaning of XXX can be found at the end of the main source file
853 (<file:drivers/video/pvr2fb.c>). Please see the file
854 <file:Documentation/fb/pvr2fb.txt>.
857 bool "Epson 1355 framebuffer support"
858 depends on (FB = y) && ARCH_CEIVA
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
863 Build in support for the SED1355 Epson Research Embedded RAMDAC
864 LCD/CRT Controller (since redesignated as the S1D13505) as a
865 framebuffer. Product specs at
866 <http://www.erd.epson.com/vdc/html/products.htm>.
869 tristate "Epson S1D13XXX framebuffer support"
871 select FB_CFB_FILLRECT
872 select FB_CFB_COPYAREA
873 select FB_CFB_IMAGEBLIT
875 Support for S1D13XXX framebuffer device family (currently only
876 working with S1D13806). Product specs at
877 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
880 tristate "AT91/AT32 LCD Controller support"
881 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || AVR32)
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
886 This enables support for the AT91/AT32 LCD Controller.
889 bool "Frame Buffer in internal SRAM"
890 depends on FB_ATMEL && ARCH_AT91SAM9261
892 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
893 to let frame buffer in external SDRAM.
896 bool "Use a STN display with AT91/AT32 LCD Controller"
897 depends on FB_ATMEL && MACH_AT91SAM9261EK
900 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
901 Controller. Say N if you want to connect a TFT.
906 tristate "nVidia Framebuffer Support"
908 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
909 select FB_MODE_HELPERS
910 select FB_CFB_FILLRECT
911 select FB_CFB_COPYAREA
912 select FB_CFB_IMAGEBLIT
916 This driver supports graphics boards with the nVidia chips, TNT
917 and newer. For very old chipsets, such as the RIVA128, then use
919 Say Y if you have such a graphics board.
921 To compile this driver as a module, choose M here: the
922 module will be called nvidiafb.
925 bool "Enable DDC Support"
929 This enables I2C support for nVidia Chipsets. This is used
930 only for getting EDID information from the attached display
931 allowing for robust video mode handling and switching.
933 Because fbdev-2.6 requires that drivers must be able to
934 independently validate video mode parameters, you should say Y
937 config FB_NVIDIA_DEBUG
938 bool "Lots of debug output"
942 Say Y here if you want the nVidia driver to output all sorts
943 of debugging information to provide to the maintainer when
944 something goes wrong.
946 config FB_NVIDIA_BACKLIGHT
947 bool "Support for backlight control"
951 Say Y here if you want to control the backlight of your display.
954 tristate "nVidia Riva support"
956 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
957 select FB_MODE_HELPERS
958 select FB_CFB_FILLRECT
959 select FB_CFB_COPYAREA
960 select FB_CFB_IMAGEBLIT
964 This driver supports graphics boards with the nVidia Riva/Geforce
966 Say Y if you have such a graphics board.
968 To compile this driver as a module, choose M here: the
969 module will be called rivafb.
972 bool "Enable DDC Support"
976 This enables I2C support for nVidia Chipsets. This is used
977 only for getting EDID information from the attached display
978 allowing for robust video mode handling and switching.
980 Because fbdev-2.6 requires that drivers must be able to
981 independently validate video mode parameters, you should say Y
985 bool "Lots of debug output"
989 Say Y here if you want the Riva driver to output all sorts
990 of debugging information to provide to the maintainer when
991 something goes wrong.
993 config FB_RIVA_BACKLIGHT
994 bool "Support for backlight control"
998 Say Y here if you want to control the backlight of your display.
1001 tristate "Intel 810/815 support (EXPERIMENTAL)"
1002 depends on FB && EXPERIMENTAL && PCI && X86_32
1005 select FB_MODE_HELPERS
1006 select FB_CFB_FILLRECT
1007 select FB_CFB_COPYAREA
1008 select FB_CFB_IMAGEBLIT
1011 This driver supports the on-board graphics built in to the Intel 810
1012 and 815 chipsets. Say Y if you have and plan to use such a board.
1014 To compile this driver as a module, choose M here: the
1015 module will be called i810fb.
1017 For more information, please read
1018 <file:Documentation/fb/intel810.txt>
1021 bool "use VESA Generalized Timing Formula"
1024 If you say Y, then the VESA standard, Generalized Timing Formula
1025 or GTF, will be used to calculate the required video timing values
1026 per video mode. Since the GTF allows nondiscrete timings
1027 (nondiscrete being a range of values as opposed to discrete being a
1028 set of values), you'll be able to use any combination of horizontal
1029 and vertical resolutions, and vertical refresh rates without having
1030 to specify your own timing parameters. This is especially useful
1031 to maximize the performance of an aging display, or if you just
1032 have a display with nonstandard dimensions. A VESA compliant
1033 monitor is recommended, but can still work with non-compliant ones.
1034 If you need or want this, then select this option. The timings may
1035 not be compliant with Intel's recommended values. Use at your own
1038 If you say N, the driver will revert to discrete video timings
1039 using a set recommended by Intel in their documentation.
1044 bool "Enable DDC Support"
1045 depends on FB_I810 && FB_I810_GTF
1050 tristate "Intel LE80578 (Vermilion) support"
1051 depends on FB && 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 LE80578 (Vermilion Range) chipset
1059 config FB_CARILLO_RANCH
1060 tristate "Intel Carillo Ranch support"
1061 depends on FB_LE80578 && FB && PCI && X86
1063 This driver supports the LE80578 (Carillo Ranch) board
1066 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
1067 depends on FB && EXPERIMENTAL && PCI && X86
1070 select FB_MODE_HELPERS
1071 select FB_CFB_FILLRECT
1072 select FB_CFB_COPYAREA
1073 select FB_CFB_IMAGEBLIT
1075 This driver supports the on-board graphics built in to the Intel
1076 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
1077 Say Y if you have and plan to use such a board.
1079 If you say Y here and want DDC/I2C support you must first say Y to
1080 "I2C support" and "I2C bit-banging support" in the character devices
1083 If you say M here then "I2C support" and "I2C bit-banging support"
1084 can be build either as modules or built-in.
1086 To compile this driver as a module, choose M here: the
1087 module will be called intelfb.
1089 For more information, please read <file:Documentation/fb/intelfb.txt>
1091 config FB_INTEL_DEBUG
1092 bool "Intel driver Debug Messages"
1095 Say Y here if you want the Intel driver to output all sorts
1096 of debugging information to provide to the maintainer when
1097 something goes wrong.
1100 bool "DDC/I2C for Intel framebuffer support"
1105 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1108 tristate "Matrox acceleration"
1109 depends on FB && PCI
1110 select FB_CFB_FILLRECT
1111 select FB_CFB_COPYAREA
1112 select FB_CFB_IMAGEBLIT
1113 select FB_TILEBLITTING
1114 select FB_MACMODES if PPC_PMAC
1116 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1117 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1118 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1119 Matrox G400, G450 or G550 card in your box.
1121 To compile this driver as a module, choose M here: the
1122 module will be called matroxfb.
1124 You can pass several parameters to the driver at boot time or at
1125 module load time. The parameters look like "video=matrox:XXX", and
1126 are described in <file:Documentation/fb/matroxfb.txt>.
1128 config FB_MATROX_MILLENIUM
1129 bool "Millennium I/II support"
1130 depends on FB_MATROX
1132 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1133 video card. If you select "Advanced lowlevel driver options" below,
1134 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1135 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1136 also use font widths different from 8.
1138 config FB_MATROX_MYSTIQUE
1139 bool "Mystique support"
1140 depends on FB_MATROX
1142 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1143 video card. If you select "Advanced lowlevel driver options" below,
1144 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1145 packed pixel and 32 bpp packed pixel. You can also use font widths
1149 bool "G100/G200/G400/G450/G550 support"
1150 depends on FB_MATROX
1152 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1153 video card. If you select "Advanced lowlevel driver options", you
1154 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1155 pixel and 32 bpp packed pixel. You can also use font widths
1158 If you need support for G400 secondary head, you must first say Y to
1159 "I2C support" in the character devices section, and then to
1160 "Matrox I2C support" and "G400 second head support" here in the
1161 framebuffer section. G450/G550 secondary head and digital output
1162 are supported without additional modules.
1164 The driver starts in monitor mode. You must use the matroxset tool
1165 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1166 swap primary and secondary head outputs, or to change output mode.
1167 Secondary head driver always start in 640x480 resolution and you
1168 must use fbset to change it.
1170 Do not forget that second head supports only 16 and 32 bpp
1171 packed pixels, so it is a good idea to compile them into the kernel
1172 too. You can use only some font widths, as the driver uses generic
1173 painting procedures (the secondary head does not use acceleration
1176 G450/G550 hardware can display TV picture only from secondary CRTC,
1177 and it performs no scaling, so picture must have 525 or 625 lines.
1179 config FB_MATROX_I2C
1180 tristate "Matrox I2C support"
1181 depends on FB_MATROX
1184 This drivers creates I2C buses which are needed for accessing the
1185 DDC (I2C) bus present on all Matroxes, an I2C bus which
1186 interconnects Matrox optional devices, like MGA-TVO on G200 and
1187 G400, and the secondary head DDC bus, present on G400 only.
1189 You can say Y or M here if you want to experiment with monitor
1190 detection code. You must say Y or M here if you want to use either
1191 second head of G400 or MGA-TVO on G200 or G400.
1193 If you compile it as module, it will create a module named
1196 config FB_MATROX_MAVEN
1197 tristate "G400 second head support"
1198 depends on FB_MATROX_G && FB_MATROX_I2C
1200 WARNING !!! This support does not work with G450 !!!
1202 Say Y or M here if you want to use a secondary head (meaning two
1203 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1204 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1205 secondary head output is blanked while you are in X. With XFree
1206 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1207 the fbdev driver on first head and the fbdev driver on second head.
1209 If you compile it as module, two modules are created,
1210 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1211 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1212 also load i2c-matroxfb to get it to run.
1214 The driver starts in monitor mode and you must use the matroxset
1216 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1217 PAL or NTSC or to swap primary and secondary head outputs.
1218 Secondary head driver also always start in 640x480 resolution, you
1219 must use fbset to change it.
1221 Also do not forget that second head supports only 16 and 32 bpp
1222 packed pixels, so it is a good idea to compile them into the kernel
1223 too. You can use only some font widths, as the driver uses generic
1224 painting procedures (the secondary head does not use acceleration
1227 config FB_MATROX_MULTIHEAD
1228 bool "Multihead support"
1229 depends on FB_MATROX
1231 Say Y here if you have more than one (supported) Matrox device in
1232 your computer and you want to use all of them for different monitors
1233 ("multihead"). If you have only one device, you should say N because
1234 the driver compiled with Y is larger and a bit slower, especially on
1237 If you said M to "Matrox unified accelerated driver" and N here, you
1238 will still be able to use several Matrox devices simultaneously:
1239 insert several instances of the module matroxfb into the kernel
1240 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1241 for the different Matrox devices. This method is slightly faster but
1242 uses 40 KB of kernel memory per Matrox card.
1244 There is no need for enabling 'Matrox multihead support' if you have
1245 only one Matrox card in the box.
1248 tristate "ATI Radeon display support"
1249 depends on FB && PCI
1250 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1251 select FB_MODE_HELPERS
1252 select FB_CFB_FILLRECT
1253 select FB_CFB_COPYAREA
1254 select FB_CFB_IMAGEBLIT
1255 select FB_MACMODES if PPC_OF
1257 Choose this option if you want to use an ATI Radeon graphics card as
1258 a framebuffer device. There are both PCI and AGP versions. You
1259 don't need to choose this to run the Radeon in plain VGA mode.
1261 If you say Y here and want DDC/I2C support you must first say Y to
1262 "I2C support" and "I2C bit-banging support" in the character devices
1265 If you say M here then "I2C support" and "I2C bit-banging support"
1266 can be build either as modules or built-in.
1268 There is a product page at
1269 http://apps.ati.com/ATIcompare/
1271 config FB_RADEON_I2C
1272 bool "DDC/I2C for ATI Radeon support"
1273 depends on FB_RADEON
1277 Say Y here if you want DDC/I2C support for your Radeon board.
1279 config FB_RADEON_BACKLIGHT
1280 bool "Support for backlight control"
1281 depends on FB_RADEON
1284 Say Y here if you want to control the backlight of your display.
1286 config FB_RADEON_DEBUG
1287 bool "Lots of debug output from Radeon driver"
1288 depends on FB_RADEON
1291 Say Y here if you want the Radeon driver to output all sorts
1292 of debugging information to provide to the maintainer when
1293 something goes wrong.
1296 tristate "ATI Rage128 display support"
1297 depends on FB && PCI
1298 select FB_CFB_FILLRECT
1299 select FB_CFB_COPYAREA
1300 select FB_CFB_IMAGEBLIT
1301 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1302 select FB_MACMODES if PPC_PMAC
1304 This driver supports graphics boards with the ATI Rage128 chips.
1305 Say Y if you have such a graphics board and read
1306 <file:Documentation/fb/aty128fb.txt>.
1308 To compile this driver as a module, choose M here: the
1309 module will be called aty128fb.
1311 config FB_ATY128_BACKLIGHT
1312 bool "Support for backlight control"
1313 depends on FB_ATY128
1316 Say Y here if you want to control the backlight of your display.
1319 tristate "ATI Mach64 display support" if PCI || ATARI
1320 depends on FB && !SPARC32
1321 select FB_CFB_FILLRECT
1322 select FB_CFB_COPYAREA
1323 select FB_CFB_IMAGEBLIT
1324 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1325 select FB_MACMODES if PPC
1327 This driver supports graphics boards with the ATI Mach64 chips.
1328 Say Y if you have such a graphics board.
1330 To compile this driver as a module, choose M here: the
1331 module will be called atyfb.
1334 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1335 depends on PCI && FB_ATY
1336 default y if SPARC64 && PCI
1338 Say Y here to support use of ATI's 64-bit Rage boards (or other
1339 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1340 framebuffer device. The ATI product support page for these boards
1341 is at <http://support.ati.com/products/pc/mach64/>.
1343 config FB_ATY_GENERIC_LCD
1344 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1345 depends on FB_ATY_CT
1347 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1348 Rage XC, or Rage XL chipset.
1351 bool "Mach64 GX support" if PCI
1355 Say Y here to support use of the ATI Mach64 Graphics Expression
1356 board (or other boards based on the Mach64 GX chipset) as a
1357 framebuffer device. The ATI product support page for these boards
1359 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1361 config FB_ATY_BACKLIGHT
1362 bool "Support for backlight control"
1366 Say Y here if you want to control the backlight of your display.
1369 tristate "S3 Trio/Virge support"
1370 depends on FB && PCI
1371 select FB_CFB_FILLRECT
1372 select FB_CFB_COPYAREA
1373 select FB_CFB_IMAGEBLIT
1374 select FB_TILEBLITTING
1377 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1379 Driver for graphics boards with S3 Trio / S3 Virge chip.
1382 tristate "S3 Savage support"
1383 depends on FB && PCI && EXPERIMENTAL
1384 select FB_MODE_HELPERS
1385 select FB_CFB_FILLRECT
1386 select FB_CFB_COPYAREA
1387 select FB_CFB_IMAGEBLIT
1390 This driver supports notebooks and computers with S3 Savage PCI/AGP
1393 Say Y if you have such a graphics card.
1395 To compile this driver as a module, choose M here; the module
1396 will be called savagefb.
1398 config FB_SAVAGE_I2C
1399 bool "Enable DDC2 Support"
1400 depends on FB_SAVAGE
1403 This enables I2C support for S3 Savage Chipsets. This is used
1404 only for getting EDID information from the attached display
1405 allowing for robust video mode handling and switching.
1407 Because fbdev-2.6 requires that drivers must be able to
1408 independently validate video mode parameters, you should say Y
1411 config FB_SAVAGE_ACCEL
1412 bool "Enable Console Acceleration"
1413 depends on FB_SAVAGE
1416 This option will compile in console acceleration support. If
1417 the resulting framebuffer console has bothersome glitches, then
1421 tristate "SiS/XGI display support"
1422 depends on FB && PCI
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1427 This is the frame buffer device driver for the SiS 300, 315, 330
1428 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1429 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1431 To compile this driver as a module, choose M here; the module
1432 will be called sisfb.
1435 bool "SiS 300 series support"
1438 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1441 bool "SiS 315/330/340 series and XGI support"
1444 Say Y here to support use of the SiS 315, 330 and 340 series
1445 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1446 as XGI V3XT, V5, V8 and Z7.
1449 tristate "NeoMagic display support"
1450 depends on FB && PCI
1451 select FB_MODE_HELPERS
1452 select FB_CFB_FILLRECT
1453 select FB_CFB_COPYAREA
1454 select FB_CFB_IMAGEBLIT
1457 This driver supports notebooks with NeoMagic PCI chips.
1458 Say Y if you have such a graphics card.
1460 To compile this driver as a module, choose M here: the
1461 module will be called neofb.
1464 tristate "IMG Kyro support"
1465 depends on FB && PCI
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1470 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1473 To compile this driver as a module, choose M here: the
1474 module will be called kyrofb.
1477 tristate "3Dfx Banshee/Voodoo3 display support"
1478 depends on FB && PCI
1479 select FB_CFB_IMAGEBLIT
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1483 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1484 chips. Say Y if you have such a graphics board.
1486 To compile this driver as a module, choose M here: the
1487 module will be called tdfxfb.
1489 config FB_3DFX_ACCEL
1490 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1491 depends on FB_3DFX && EXPERIMENTAL
1493 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1494 with acceleration functions.
1498 tristate "3Dfx Voodoo Graphics (sst1) support"
1499 depends on FB && PCI
1500 select FB_CFB_FILLRECT
1501 select FB_CFB_COPYAREA
1502 select FB_CFB_IMAGEBLIT
1504 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1505 Voodoo2 (cvg) based graphics card.
1507 To compile this driver as a module, choose M here: the
1508 module will be called sstfb.
1510 WARNING: Do not use any application that uses the 3D engine
1511 (namely glide) while using this driver.
1512 Please read the <file:Documentation/fb/sstfb.txt> for supported
1513 options and other important info support.
1516 tristate "VIA VT8623 support"
1517 depends on FB && PCI
1518 select FB_CFB_FILLRECT
1519 select FB_CFB_COPYAREA
1520 select FB_CFB_IMAGEBLIT
1521 select FB_TILEBLITTING
1524 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1526 Driver for CastleRock integrated graphics core in the
1527 VIA VT8623 [Apollo CLE266] chipset.
1530 tristate "Cyberblade/i1 support"
1531 depends on FB && PCI && X86_32 && !64BIT
1532 select FB_CFB_IMAGEBLIT
1535 This driver is supposed to support the Trident Cyberblade/i1
1536 graphics core integrated in the VIA VT8601A North Bridge,
1537 also known as VIA Apollo PLE133.
1540 - Developed, tested and working on EPIA 5000 and EPIA 800.
1541 - Does work reliable on all systems with CRT/LCD connected to
1543 - Should work on systems that do use the internal LCD port, but
1544 this is absolutely not tested.
1546 Character imageblit, copyarea and rectangle fill are hw accelerated,
1547 ypan scrolling is used by default.
1549 Please do read <file:Documentation/fb/cyblafb/*>.
1551 To compile this driver as a module, choose M here: the
1552 module will be called cyblafb.
1555 tristate "Trident support"
1556 depends on FB && PCI
1557 select FB_CFB_FILLRECT
1558 select FB_CFB_COPYAREA
1559 select FB_CFB_IMAGEBLIT
1561 This driver is supposed to support graphics boards with the
1562 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1563 but also on some motherboards. For more information, read
1564 <file:Documentation/fb/tridentfb.txt>
1566 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1569 Say Y if you have such a graphics board.
1572 To compile this driver as a module, choose M here: the
1573 module will be called tridentfb.
1575 config FB_TRIDENT_ACCEL
1576 bool "Trident Acceleration functions (EXPERIMENTAL)"
1577 depends on FB_TRIDENT && EXPERIMENTAL
1579 This will compile the Trident frame buffer device with
1580 acceleration functions.
1583 tristate "ARK 2000PV support"
1584 depends on FB && PCI
1585 select FB_CFB_FILLRECT
1586 select FB_CFB_COPYAREA
1587 select FB_CFB_IMAGEBLIT
1588 select FB_TILEBLITTING
1591 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1593 Driver for PCI graphics boards with ARK 2000PV chip
1594 and ICS 5342 RAMDAC.
1597 tristate "Permedia3 support (EXPERIMENTAL)"
1598 depends on FB && PCI && EXPERIMENTAL
1599 select FB_CFB_FILLRECT
1600 select FB_CFB_COPYAREA
1601 select FB_CFB_IMAGEBLIT
1603 This is the frame buffer device driver for the 3DLabs Permedia3
1604 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1605 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1606 and maybe other boards.
1609 bool "Au1100 LCD Driver"
1610 depends on (FB = y) && MIPS && SOC_AU1100
1611 select FB_CFB_FILLRECT
1612 select FB_CFB_COPYAREA
1613 select FB_CFB_IMAGEBLIT
1615 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1616 various panels and CRTs by passing in kernel cmd line option
1617 au1100fb:panel=<name>.
1620 bool "Au1200 LCD Driver"
1621 depends on (FB = y) && MIPS && SOC_AU1200
1622 select FB_CFB_FILLRECT
1623 select FB_CFB_COPYAREA
1624 select FB_CFB_IMAGEBLIT
1626 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1627 various panels and CRTs by passing in kernel cmd line option
1628 au1200fb:panel=<name>.
1630 source "drivers/video/geode/Kconfig"
1633 tristate "HD64461 Frame Buffer support"
1634 depends on FB && HD64461
1635 select FB_CFB_FILLRECT
1636 select FB_CFB_COPYAREA
1637 select FB_CFB_IMAGEBLIT
1639 This is the frame buffer device driver for the Hitachi HD64461 LCD
1643 bool "PMAG-AA TURBOchannel framebuffer support"
1644 depends on (FB = y) && TC
1645 select FB_CFB_FILLRECT
1646 select FB_CFB_COPYAREA
1647 select FB_CFB_IMAGEBLIT
1649 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1650 used mainly in the MIPS-based DECstation series.
1653 tristate "PMAG-BA TURBOchannel framebuffer support"
1655 select FB_CFB_FILLRECT
1656 select FB_CFB_COPYAREA
1657 select FB_CFB_IMAGEBLIT
1659 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1660 used mainly in the MIPS-based DECstation series.
1663 tristate "PMAGB-B TURBOchannel framebuffer support"
1665 select FB_CFB_FILLRECT
1666 select FB_CFB_COPYAREA
1667 select FB_CFB_IMAGEBLIT
1669 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1670 in the MIPS-based DECstation series. The card is currently only
1671 supported in 1280x1024x8 mode.
1674 bool "Maxine (Personal DECstation) onboard framebuffer support"
1675 depends on (FB = y) && MACH_DECSTATION
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1680 Support for the onboard framebuffer (1024x768x8) in the Personal
1681 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1685 bool "G364 frame buffer support"
1686 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1687 select FB_CFB_FILLRECT
1688 select FB_CFB_COPYAREA
1689 select FB_CFB_IMAGEBLIT
1691 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1692 Olivetti M700-10 systems.
1695 bool "Motorola 68328 native frame buffer support"
1696 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1697 select FB_CFB_FILLRECT
1698 select FB_CFB_COPYAREA
1699 select FB_CFB_IMAGEBLIT
1701 Say Y here if you want to support the built-in frame buffer of
1702 the Motorola 68328 CPU family.
1705 tristate "PXA LCD framebuffer support"
1706 depends on FB && ARCH_PXA
1707 select FB_CFB_FILLRECT
1708 select FB_CFB_COPYAREA
1709 select FB_CFB_IMAGEBLIT
1711 Frame buffer driver for the built-in LCD controller in the Intel
1714 This driver is also available as a module ( = code which can be
1715 inserted and removed from the running kernel whenever you want). The
1716 module will be called pxafb. If you want to compile it as a module,
1717 say M here and read <file:Documentation/kbuild/modules.txt>.
1721 config FB_PXA_PARAMETERS
1722 bool "PXA LCD command line parameters"
1726 Enable the use of kernel command line or module parameters
1727 to configure the physical properties of the LCD panel when
1728 using the PXA LCD driver.
1730 This option allows you to override the panel parameters
1731 supplied by the platform in order to support multiple
1732 different models of flatpanel. If you will only be using a
1733 single model of flatpanel then you can safely leave this
1736 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1739 tristate "2700G LCD framebuffer support"
1740 depends on FB && ARCH_PXA
1741 select FB_CFB_FILLRECT
1742 select FB_CFB_COPYAREA
1743 select FB_CFB_IMAGEBLIT
1745 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1749 bool "Enable debugging info via debugfs"
1750 depends on FB_MBX && DEBUG_FS
1753 Enable this if you want debugging information using the debug
1754 filesystem (debugfs)
1759 tristate "W100 frame buffer support"
1760 depends on FB && PXA_SHARPSL
1761 select FB_CFB_FILLRECT
1762 select FB_CFB_COPYAREA
1763 select FB_CFB_IMAGEBLIT
1765 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1767 This driver is also available as a module ( = code which can be
1768 inserted and removed from the running kernel whenever you want). The
1769 module will be called w100fb. If you want to compile it as a module,
1770 say M here and read <file:Documentation/kbuild/modules.txt>.
1775 tristate "S3C2410 LCD framebuffer support"
1776 depends on FB && ARCH_S3C2410
1777 select FB_CFB_FILLRECT
1778 select FB_CFB_COPYAREA
1779 select FB_CFB_IMAGEBLIT
1781 Frame buffer driver for the built-in LCD controller in the Samsung
1784 This driver is also available as a module ( = code which can be
1785 inserted and removed from the running kernel whenever you want). The
1786 module will be called s3c2410fb. If you want to compile it as a module,
1787 say M here and read <file:Documentation/kbuild/modules.txt>.
1790 config FB_S3C2410_DEBUG
1791 bool "S3C2410 lcd debug messages"
1792 depends on FB_S3C2410
1794 Turn on debugging messages. Note that you can set/unset at run time
1798 tristate "Silicon Motion SM501 framebuffer support"
1799 depends on FB && MFD_SM501
1800 select FB_CFB_FILLRECT
1801 select FB_CFB_COPYAREA
1802 select FB_CFB_IMAGEBLIT
1804 Frame buffer driver for the CRT and LCD controllers in the Silicon
1807 This driver is also available as a module ( = code which can be
1808 inserted and removed from the running kernel whenever you want). The
1809 module will be called sm501fb. If you want to compile it as a module,
1810 say M here and read <file:Documentation/kbuild/modules.txt>.
1815 config FB_PNX4008_DUM
1816 tristate "Display Update Module support on Philips PNX4008 board"
1817 depends on FB && ARCH_PNX4008
1819 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1821 config FB_PNX4008_DUM_RGB
1822 tristate "RGB Framebuffer support on Philips PNX4008 board"
1823 depends on FB_PNX4008_DUM
1824 select FB_CFB_FILLRECT
1825 select FB_CFB_COPYAREA
1826 select FB_CFB_IMAGEBLIT
1828 Say Y here to enable support for PNX4008 RGB Framebuffer
1830 config FB_IBM_GXT4500
1831 tristate "Framebuffer support for IBM GXT4500P adaptor"
1832 depends on FB && PPC
1833 select FB_CFB_FILLRECT
1834 select FB_CFB_COPYAREA
1835 select FB_CFB_IMAGEBLIT
1837 Say Y here to enable support for the IBM GXT4500P display
1838 adaptor, found on some IBM System P (pSeries) machines.
1841 tristate "PS3 GPU framebuffer driver"
1842 depends on FB && PS3_PS3AV
1843 select FB_SYS_FILLRECT
1844 select FB_SYS_COPYAREA
1845 select FB_SYS_IMAGEBLIT
1847 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1849 Include support for the virtual frame buffer in the PS3 platform.
1851 config FB_PS3_DEFAULT_SIZE_M
1852 int "PS3 default frame buffer size (in MiB)"
1856 This is the default size (in MiB) of the virtual frame buffer in
1858 The default value can be overridden on the kernel command line
1859 using the "ps3fb" option (e.g. "ps3fb=9M");
1862 tristate "Xilinx frame buffer support"
1863 depends on FB && XILINX_VIRTEX
1864 select FB_CFB_FILLRECT
1865 select FB_CFB_COPYAREA
1866 select FB_CFB_IMAGEBLIT
1868 Include support for the Xilinx ML300/ML403 reference design
1869 framebuffer. ML300 carries a 640*480 LCD display on the board,
1870 ML403 uses a standard DB15 VGA connector.
1873 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1875 select FB_SYS_FILLRECT
1876 select FB_SYS_COPYAREA
1877 select FB_SYS_IMAGEBLIT
1880 This is a `virtual' frame buffer device. It operates on a chunk of
1881 unswappable kernel memory instead of on the memory of a graphics
1882 board. This means you cannot see any output sent to this frame
1883 buffer device, while it does consume precious memory. The main use
1884 of this frame buffer device is testing and debugging the frame
1885 buffer subsystem. Do NOT enable it for normal systems! To protect
1886 the innocent, it has to be enabled explicitly at boot time using the
1887 kernel option `video=vfb:'.
1889 To compile this driver as a module, choose M here: the
1890 module will be called vfb. In order to load it, you must use
1891 the vfb_enable=1 option.
1895 source "drivers/video/omap/Kconfig"
1897 source "drivers/video/backlight/Kconfig"
1898 source "drivers/video/display/Kconfig"
1901 source "drivers/video/console/Kconfig"
1904 if FB || SGI_NEWPORT_CONSOLE
1905 source "drivers/video/logo/Kconfig"