5 menu "Graphics support"
8 source "drivers/video/backlight/Kconfig"
9 source "drivers/video/display/Kconfig"
16 tristate "Support for frame buffer devices"
18 The frame buffer device provides an abstraction for the graphics
19 hardware. It represents the frame buffer of some video hardware and
20 allows application software to access the graphics hardware through
21 a well-defined interface, so the software doesn't need to know
22 anything about the low-level (hardware register) stuff.
24 Frame buffer devices work identically across the different
25 architectures supported by Linux and make the implementation of
26 application programs easier and more portable; at this point, an X
27 server exists which uses the frame buffer device exclusively.
28 On several non-X86 architectures, the frame buffer device is the
29 only way to use the graphics hardware.
31 The device is accessed through special device nodes, usually located
32 in the /dev directory, i.e. /dev/fb*.
34 You need an utility program called fbset to make full use of frame
35 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
36 and the Framebuffer-HOWTO at
37 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
40 Say Y here and to the driver for your graphics board below if you
41 are compiling a kernel for a non-x86 architecture.
43 If you are compiling for the x86 architecture, you can say Y if you
44 want to play with it, but it is not essential. Please note that
45 running graphical applications that directly touch the hardware
46 (e.g. an accelerated X server) and that are not frame buffer
47 device-aware may cause unexpected results. If unsure, say N.
50 bool "Enable firmware EDID"
54 This enables access to the EDID transferred from the firmware.
55 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
56 transfers do not work for your driver and if you are using
57 nvidiafb, i810fb or savagefb.
59 In general, choosing Y for this option is safe. If you
60 experience extremely long delays while booting before you get
61 something on your display, try setting this to N. Matrox cards in
62 combination with certain motherboards and monitors are known to
63 suffer from this problem.
72 config FB_CFB_FILLRECT
77 Include the cfb_fillrect function for generic software rectangle
78 filling. This is used by drivers that don't provide their own
79 (accelerated) version.
81 config FB_CFB_COPYAREA
86 Include the cfb_copyarea function for generic software area copying.
87 This is used by drivers that don't provide their own (accelerated)
90 config FB_CFB_IMAGEBLIT
95 Include the cfb_imageblit function for generic software image
96 blitting. This is used by drivers that don't provide their own
97 (accelerated) version.
99 config FB_SYS_FILLRECT
104 Include the sys_fillrect function for generic software rectangle
105 filling. This is used by drivers that don't provide their own
106 (accelerated) version and the framebuffer is in system RAM.
108 config FB_SYS_COPYAREA
113 Include the sys_copyarea function for generic software area copying.
114 This is used by drivers that don't provide their own (accelerated)
115 version and the framebuffer is in system RAM.
117 config FB_SYS_IMAGEBLIT
122 Include the sys_imageblit function for generic software image
123 blitting. This is used by drivers that don't provide their own
124 (accelerated) version and the framebuffer is in system RAM.
131 config FB_DEFERRED_IO
141 Common utility functions useful to fbdev drivers of VGA-based
152 select BACKLIGHT_LCD_SUPPORT
153 select BACKLIGHT_CLASS_DEVICE
156 config FB_MODE_HELPERS
157 bool "Enable Video Mode Handling Helpers"
161 This enables functions for handling video modes using the
162 Generalized Timing Formula and the EDID parser. A few drivers rely
163 on this feature such as the radeonfb, rivafb, and the i810fb. If
164 your driver does not take advantage of this feature, choosing Y will
165 just increase the kernel size by about 5K.
167 config FB_TILEBLITTING
168 bool "Enable Tile Blitting Support"
172 This enables tile blitting. Tile blitting is a drawing technique
173 where the screen is divided into rectangular sections (tiles), whereas
174 the standard blitting divides the screen into pixels. Because the
175 default drawing element is a tile, drawing functions will be passed
176 parameters in terms of number of tiles instead of number of pixels.
177 For example, to draw a single character, instead of using bitmaps,
178 an index to an array of bitmaps will be used. To clear or move a
179 rectangular section of a screen, the rectangle will be described in
180 terms of number of tiles in the x- and y-axis.
182 This is particularly important to one driver, matroxfb. If
185 comment "Frame buffer hardware drivers"
189 tristate "Cirrus Logic support"
190 depends on FB && (ZORRO || PCI)
191 select FB_CFB_FILLRECT
192 select FB_CFB_COPYAREA
193 select FB_CFB_IMAGEBLIT
195 This enables support for Cirrus Logic GD542x/543x based boards on
196 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
198 If you have a PCI-based system, this enables support for these
199 chips: GD-543x, GD-544x, GD-5480.
201 Please read the file <file:Documentation/fb/cirrusfb.txt>.
203 Say N unless you have such a graphics board or plan to get one
204 before you next recompile the kernel.
207 tristate "Permedia2 support"
208 depends on FB && ((AMIGA && BROKEN) || PCI)
209 select FB_CFB_FILLRECT
210 select FB_CFB_COPYAREA
211 select FB_CFB_IMAGEBLIT
213 This is the frame buffer device driver for the Permedia2 AGP frame
214 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
216 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
218 config FB_PM2_FIFO_DISCONNECT
219 bool "enable FIFO disconnect feature"
220 depends on FB_PM2 && PCI
222 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
225 tristate "ARM PrimeCell PL110 support"
226 depends on FB && ARM && ARM_AMBA
227 select FB_CFB_FILLRECT
228 select FB_CFB_COPYAREA
229 select FB_CFB_IMAGEBLIT
231 This framebuffer device driver is for the ARM PrimeCell PL110
232 Colour LCD controller. ARM PrimeCells provide the building
233 blocks for System on a Chip devices.
235 If you want to compile this as a module (=code which can be
236 inserted into and removed from the running kernel), say M
237 here and read <file:Documentation/kbuild/modules.txt>. The module
238 will be called amba-clcd.
242 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
244 default FB_ARMCLCD_SHARP_LQ035Q7DB02
246 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
247 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
249 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
250 color QVGA, HRTFT panel. The LogicPD device includes
251 an integrated HRTFT controller IC.
252 The native resolution is 240x320.
254 config FB_ARMCLCD_SHARP_LQ057Q3DC02
255 bool "LogicPD LCD 5.7\" QVGA"
257 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
258 color QVGA, TFT panel. The LogicPD device includes an
259 The native resolution is 320x240.
261 config FB_ARMCLCD_SHARP_LQ64D343
262 bool "LogicPD LCD 6.4\" VGA"
264 This is an implementation of the Sharp LQ64D343, a 6.4"
265 color VGA, TFT panel. The LogicPD device includes an
266 The native resolution is 640x480.
268 config FB_ARMCLCD_SHARP_LQ10D368
269 bool "LogicPD LCD 10.4\" VGA"
271 This is an implementation of the Sharp LQ10D368, a 10.4"
272 color VGA, TFT panel. The LogicPD device includes an
273 The native resolution is 640x480.
276 config FB_ARMCLCD_SHARP_LQ121S1DG41
277 bool "LogicPD LCD 12.1\" SVGA"
279 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
280 color SVGA, TFT panel. The LogicPD device includes an
281 The native resolution is 800x600.
283 This panel requires a clock rate may be an integer fraction
284 of the base LCDCLK frequency. The driver will select the
285 highest frequency available that is lower than the maximum
286 allowed. The panel may flicker if the clock rate is
287 slower than the recommended minimum.
289 config FB_ARMCLCD_AUO_A070VW01_WIDE
290 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
292 This is an implementation of the AU Optronics, a 7.0"
293 WIDE Color. The native resolution is 234x480.
295 config FB_ARMCLCD_HITACHI
296 bool "Hitachi Wide Screen 800x480"
298 This is an implementation of the Hitachi 800x480.
304 bool "Acorn VIDC support"
305 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
306 select FB_CFB_FILLRECT
307 select FB_CFB_COPYAREA
308 select FB_CFB_IMAGEBLIT
310 This is the frame buffer device driver for the Acorn VIDC graphics
311 hardware found in Acorn RISC PCs and other ARM-based machines. If
315 bool "CLPS711X LCD support"
316 depends on (FB = y) && ARM && ARCH_CLPS711X
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
321 Say Y to enable the Framebuffer driver for the CLPS7111 and
325 bool "SA-1100 LCD support"
326 depends on (FB = y) && ARM && ARCH_SA1100
327 select FB_CFB_FILLRECT
328 select FB_CFB_COPYAREA
329 select FB_CFB_IMAGEBLIT
331 This is a framebuffer device for the SA-1100 LCD Controller.
332 See <http://www.linux-fbdev.org/> for information on framebuffer
335 If you plan to use the LCD display with your SA-1100 system, say
339 tristate "Motorola i.MX LCD support"
340 depends on FB && ARM && ARCH_IMX
341 select FB_CFB_FILLRECT
342 select FB_CFB_COPYAREA
343 select FB_CFB_IMAGEBLIT
346 tristate "CyberPro 2000/2010/5000 support"
347 depends on FB && PCI && (BROKEN || !SPARC64)
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This enables support for the Integraphics CyberPro 20x0 and 5000
353 VGA chips used in the Rebel.com Netwinder and other machines.
354 Say Y if you have a NetWinder or a graphics card containing this
355 device, otherwise say N.
359 depends on (FB = y) && APOLLO
361 select FB_CFB_FILLRECT
362 select FB_CFB_IMAGEBLIT
366 depends on (FB = y) && Q40
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
373 tristate "Amiga native chipset support"
374 depends on FB && AMIGA
376 This is the frame buffer device driver for the builtin graphics
377 chipset found in Amigas.
379 To compile this driver as a module, choose M here: the
380 module will be called amifb.
383 bool "Amiga OCS chipset support"
386 This enables support for the original Agnus and Denise video chips,
387 found in the Amiga 1000 and most A500's and A2000's. If you intend
388 to run Linux on any of these systems, say Y; otherwise say N.
391 bool "Amiga ECS chipset support"
394 This enables support for the Enhanced Chip Set, found in later
395 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
396 you intend to run Linux on any of these systems, say Y; otherwise
400 bool "Amiga AGA chipset support"
403 This enables support for the Advanced Graphics Architecture (also
404 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
405 and CD32. If you intend to run Linux on any of these systems, say Y;
409 bool "Amiga FrameMaster II/Rainbow II support"
410 depends on (FB = y) && ZORRO
411 select FB_CFB_FILLRECT
412 select FB_CFB_COPYAREA
413 select FB_CFB_IMAGEBLIT
415 This is the frame buffer device driver for the Amiga FrameMaster
416 card from BSC (exhibited 1992 but not shipped as a CBM product).
419 tristate "Arc Monochrome LCD board support"
421 select FB_SYS_FILLRECT
422 select FB_SYS_COPYAREA
423 select FB_SYS_IMAGEBLIT
426 This enables support for the Arc Monochrome LCD board. The board
427 is based on the KS-108 lcd controller and is typically a matrix
428 of 2*n chips. This driver was tested with a 128x64 panel. This
429 driver supports it for use with x86 SBCs through a 16 bit GPIO
430 interface (8 bit data, 8 bit control). If you anticipate using
431 this driver, say Y or M; otherwise say N. You must specify the
432 GPIO IO address to be used for setting control and data.
435 bool "Atari native chipset support"
436 depends on (FB = y) && ATARI
437 select FB_CFB_FILLRECT
438 select FB_CFB_COPYAREA
439 select FB_CFB_IMAGEBLIT
441 This is the frame buffer device driver for the builtin graphics
442 chipset found in Ataris.
445 bool "Open Firmware frame buffer device support"
446 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
447 select FB_CFB_FILLRECT
448 select FB_CFB_COPYAREA
449 select FB_CFB_IMAGEBLIT
452 Say Y if you want support with Open Firmware for your graphics
456 bool "Apple \"control\" display support"
457 depends on (FB = y) && PPC_PMAC && PPC32
458 select FB_CFB_FILLRECT
459 select FB_CFB_COPYAREA
460 select FB_CFB_IMAGEBLIT
463 This driver supports a frame buffer for the graphics adapter in the
464 Power Macintosh 7300 and others.
467 bool "Apple \"platinum\" display support"
468 depends on (FB = y) && PPC_PMAC && PPC32
469 select FB_CFB_FILLRECT
470 select FB_CFB_COPYAREA
471 select FB_CFB_IMAGEBLIT
474 This driver supports a frame buffer for the "platinum" graphics
475 adapter in some Power Macintoshes.
478 bool "Apple \"valkyrie\" display support"
479 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
480 select FB_CFB_FILLRECT
481 select FB_CFB_COPYAREA
482 select FB_CFB_IMAGEBLIT
485 This driver supports a frame buffer for the "valkyrie" graphics
486 adapter in some Power Macintoshes.
489 bool "Chips 65550 display support"
490 depends on (FB = y) && PPC32
491 select FB_CFB_FILLRECT
492 select FB_CFB_COPYAREA
493 select FB_CFB_IMAGEBLIT
495 This is the frame buffer device driver for the Chips & Technologies
496 65550 graphics chip in PowerBooks.
499 bool "Asiliant (Chips) 69000 display support"
500 depends on (FB = y) && PCI
501 select FB_CFB_FILLRECT
502 select FB_CFB_COPYAREA
503 select FB_CFB_IMAGEBLIT
505 This is the frame buffer device driver for the Asiliant 69030 chipset
508 bool "IMS Twin Turbo display support"
509 depends on (FB = y) && PCI
510 select FB_CFB_IMAGEBLIT
511 select FB_MACMODES if PPC
513 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
514 many Macintosh and compatible computers.
517 tristate "VGA 16-color graphics support"
518 depends on FB && (X86 || PPC)
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
523 select FONT_8x16 if FRAMEBUFFER_CONSOLE
525 This is the frame buffer device driver for VGA 16 color graphic
526 cards. Say Y if you have such a card.
528 To compile this driver as a module, choose M here: the
529 module will be called vga16fb.
532 tristate "HP STI frame buffer device support"
533 depends on FB && PARISC
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
539 STI refers to the HP "Standard Text Interface" which is a set of
540 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
541 Enabling this option will implement the linux framebuffer device
542 using calls to the STI BIOS routines for initialisation.
544 If you enable this option, you will get a planar framebuffer device
545 /dev/fb which will work on the most common HP graphic cards of the
546 NGLE family, including the artist chips (in the 7xx and Bxxx series),
547 HCRX, HCRX24, CRX, CRX24 and VisEG series.
549 It is safe to enable this option, so you should probably say "Y".
552 bool "Generic Macintosh display support"
553 depends on (FB = y) && MAC
554 select FB_CFB_FILLRECT
555 select FB_CFB_COPYAREA
556 select FB_CFB_IMAGEBLIT
559 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
562 depends on (FB = y) && HP300
563 select FB_CFB_FILLRECT
564 select FB_CFB_IMAGEBLIT
568 tristate "TGA/SFB+ framebuffer support"
569 depends on FB && (ALPHA || TC)
570 select FB_CFB_FILLRECT
571 select FB_CFB_COPYAREA
572 select FB_CFB_IMAGEBLIT
575 This is the frame buffer device driver for generic TGA and SFB+
576 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
577 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
578 TURBOchannel cards, also known as PMAGD-A, -B and -C.
580 Due to hardware limitations ZLX-E2 and E3 cards are not supported
581 for DECstation 5000/200 systems. Additionally due to firmware
582 limitations these cards may cause troubles with booting DECstation
583 5000/240 and /260 systems, but are fully supported under Linux if
584 you manage to get it going. ;-)
586 Say Y if you have one of those.
589 bool "VESA VGA graphics support"
590 depends on (FB = y) && X86
591 select FB_CFB_FILLRECT
592 select FB_CFB_COPYAREA
593 select FB_CFB_IMAGEBLIT
596 This is the frame buffer device driver for generic VESA 2.0
597 compliant graphic cards. The older VESA 1.2 cards are not supported.
598 You will get a boot time penguin logo at no additional cost. Please
599 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
602 bool "Intel-based Macintosh Framebuffer Support"
603 depends on (FB = y) && X86 && EFI
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the frame buffer device driver for the Intel-based Macintosh
611 tristate "Hecuba board support"
612 depends on FB && X86 && MMU
613 select FB_SYS_FILLRECT
614 select FB_SYS_COPYAREA
615 select FB_SYS_IMAGEBLIT
617 select FB_DEFERRED_IO
619 This enables support for the Hecuba board. This driver was tested
620 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
621 interface (8 bit data, 4 bit control). If you anticpate using
622 this driver, say Y or M; otherwise say N. You must specify the
623 GPIO IO address to be used for setting control and data.
626 tristate "Hercules mono graphics support"
628 select FB_CFB_FILLRECT
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
632 Say Y here if you have a Hercules mono graphics card.
634 To compile this driver as a module, choose M here: the
635 module will be called hgafb.
637 As this card technology is 15 years old, most people will answer N
641 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
642 depends on FB_HGA && EXPERIMENTAL
644 This will compile the Hercules mono graphics with
645 acceleration functions.
648 tristate "SGI Visual Workstation framebuffer support"
649 depends on FB && X86_VISWS
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
654 SGI Visual Workstation support for framebuffer graphics.
657 bool "SGI Graphics Backend frame buffer support"
658 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
663 This is the frame buffer device driver for SGI Graphics Backend.
664 This chip is used in SGI O2 and Visual Workstation 320/540.
667 int "Video memory size in MB"
671 This is the amount of memory reserved for the framebuffer,
672 which can be any value between 1MB and 8MB.
675 bool "SBUS and UPA framebuffers"
676 depends on (FB = y) && SPARC
678 Say Y if you want support for SBUS or UPA based frame buffer device.
682 depends on (FB = y) && (SPARC && FB_SBUS)
683 select FB_CFB_FILLRECT
684 select FB_CFB_COPYAREA
685 select FB_CFB_IMAGEBLIT
687 This is the frame buffer device driver for the BWtwo frame buffer.
690 bool "CGthree support"
691 depends on (FB = y) && (SPARC && FB_SBUS)
692 select FB_CFB_FILLRECT
693 select FB_CFB_COPYAREA
694 select FB_CFB_IMAGEBLIT
696 This is the frame buffer device driver for the CGthree frame buffer.
699 bool "CGsix (GX,TurboGX) support"
700 depends on (FB = y) && (SPARC && FB_SBUS)
701 select FB_CFB_COPYAREA
702 select FB_CFB_IMAGEBLIT
704 This is the frame buffer device driver for the CGsix (GX, TurboGX)
708 bool "Creator/Creator3D/Elite3D support"
709 depends on FB_SBUS && SPARC64
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
713 This is the frame buffer device driver for the Creator, Creator3D,
714 and Elite3D graphics boards.
717 bool "TCX (SS4/SS5 only) support"
719 select FB_CFB_FILLRECT
720 select FB_CFB_COPYAREA
721 select FB_CFB_IMAGEBLIT
723 This is the frame buffer device driver for the TCX 24/8bit frame
727 bool "CGfourteen (SX) support"
729 select FB_CFB_FILLRECT
730 select FB_CFB_COPYAREA
731 select FB_CFB_IMAGEBLIT
733 This is the frame buffer device driver for the CGfourteen frame
734 buffer on Desktop SPARCsystems with the SX graphics option.
737 bool "P9100 (Sparcbook 3 only) support"
739 select FB_CFB_FILLRECT
740 select FB_CFB_COPYAREA
741 select FB_CFB_IMAGEBLIT
743 This is the frame buffer device driver for the P9100 card
744 supported on Sparcbook 3 machines.
747 bool "Leo (ZX) support"
749 select FB_CFB_FILLRECT
750 select FB_CFB_COPYAREA
751 select FB_CFB_IMAGEBLIT
753 This is the frame buffer device driver for the SBUS-based Sun ZX
754 (leo) frame buffer cards.
757 bool "IGA 168x display support"
758 depends on (FB = y) && SPARC32
759 select FB_CFB_FILLRECT
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
763 This is the framebuffer device for the INTERGRAPHICS 1680 and
764 successor frame buffer cards.
767 bool "Sun XVR-500 3DLABS Wildcat support"
768 depends on (FB = y) && PCI && SPARC64
769 select FB_CFB_FILLRECT
770 select FB_CFB_COPYAREA
771 select FB_CFB_IMAGEBLIT
773 This is the framebuffer device for the Sun XVR-500 and similar
774 graphics cards based upon the 3DLABS Wildcat chipset. The driver
775 only works on sparc64 systems where the system firwmare has
776 mostly initialized the card already. It is treated as a
777 completely dumb framebuffer device.
780 bool "Sun XVR-2500 3DLABS Wildcat support"
781 depends on (FB = y) && PCI && SPARC64
782 select FB_CFB_FILLRECT
783 select FB_CFB_COPYAREA
784 select FB_CFB_IMAGEBLIT
786 This is the framebuffer device for the Sun XVR-2500 and similar
787 graphics cards based upon the 3DLABS Wildcat chipset. The driver
788 only works on sparc64 systems where the system firwmare has
789 mostly initialized the card already. It is treated as a
790 completely dumb framebuffer device.
793 tristate "NEC PowerVR 2 display support"
794 depends on FB && SH_DREAMCAST
795 select FB_CFB_FILLRECT
796 select FB_CFB_COPYAREA
797 select FB_CFB_IMAGEBLIT
799 Say Y here if you have a PowerVR 2 card in your box. If you plan to
800 run linux on your Dreamcast, you will have to say Y here.
801 This driver may or may not work on other PowerVR 2 cards, but is
802 totally untested. Use at your own risk. If unsure, say N.
804 To compile this driver as a module, choose M here: the
805 module will be called pvr2fb.
807 You can pass several parameters to the driver at boot time or at
808 module load time. The parameters look like "video=pvr2:XXX", where
809 the meaning of XXX can be found at the end of the main source file
810 (<file:drivers/video/pvr2fb.c>). Please see the file
811 <file:Documentation/fb/pvr2fb.txt>.
814 bool "Epson 1355 framebuffer support"
815 depends on (FB = y) && ARCH_CEIVA
816 select FB_CFB_FILLRECT
817 select FB_CFB_COPYAREA
818 select FB_CFB_IMAGEBLIT
820 Build in support for the SED1355 Epson Research Embedded RAMDAC
821 LCD/CRT Controller (since redesignated as the S1D13505) as a
822 framebuffer. Product specs at
823 <http://www.erd.epson.com/vdc/html/products.htm>.
826 tristate "Epson S1D13XXX framebuffer support"
828 select FB_CFB_FILLRECT
829 select FB_CFB_COPYAREA
830 select FB_CFB_IMAGEBLIT
832 Support for S1D13XXX framebuffer device family (currently only
833 working with S1D13806). Product specs at
834 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
837 tristate "AT91/AT32 LCD Controller support"
838 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || AVR32)
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
843 This enables support for the AT91/AT32 LCD Controller.
846 bool "Frame Buffer in internal SRAM"
847 depends on FB_ATMEL && ARCH_AT91SAM9261
849 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
850 to let frame buffer in external SDRAM.
853 bool "Use a STN display with AT91/AT32 LCD Controller"
854 depends on FB_ATMEL && MACH_AT91SAM9261EK
857 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
858 Controller. Say N if you want to connect a TFT.
863 tristate "nVidia Framebuffer Support"
865 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
866 select FB_MODE_HELPERS
867 select FB_CFB_FILLRECT
868 select FB_CFB_COPYAREA
869 select FB_CFB_IMAGEBLIT
873 This driver supports graphics boards with the nVidia chips, TNT
874 and newer. For very old chipsets, such as the RIVA128, then use
876 Say Y if you have such a graphics board.
878 To compile this driver as a module, choose M here: the
879 module will be called nvidiafb.
882 bool "Enable DDC Support"
886 This enables I2C support for nVidia Chipsets. This is used
887 only for getting EDID information from the attached display
888 allowing for robust video mode handling and switching.
890 Because fbdev-2.6 requires that drivers must be able to
891 independently validate video mode parameters, you should say Y
894 config FB_NVIDIA_DEBUG
895 bool "Lots of debug output"
899 Say Y here if you want the nVidia driver to output all sorts
900 of debugging information to provide to the maintainer when
901 something goes wrong.
903 config FB_NVIDIA_BACKLIGHT
904 bool "Support for backlight control"
908 Say Y here if you want to control the backlight of your display.
911 tristate "nVidia Riva support"
913 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
914 select FB_MODE_HELPERS
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
921 This driver supports graphics boards with the nVidia Riva/Geforce
923 Say Y if you have such a graphics board.
925 To compile this driver as a module, choose M here: the
926 module will be called rivafb.
929 bool "Enable DDC Support"
933 This enables I2C support for nVidia Chipsets. This is used
934 only for getting EDID information from the attached display
935 allowing for robust video mode handling and switching.
937 Because fbdev-2.6 requires that drivers must be able to
938 independently validate video mode parameters, you should say Y
942 bool "Lots of debug output"
946 Say Y here if you want the Riva driver to output all sorts
947 of debugging information to provide to the maintainer when
948 something goes wrong.
950 config FB_RIVA_BACKLIGHT
951 bool "Support for backlight control"
955 Say Y here if you want to control the backlight of your display.
958 tristate "Intel 810/815 support (EXPERIMENTAL)"
959 depends on FB && EXPERIMENTAL && PCI && X86_32
962 select FB_MODE_HELPERS
963 select FB_CFB_FILLRECT
964 select FB_CFB_COPYAREA
965 select FB_CFB_IMAGEBLIT
968 This driver supports the on-board graphics built in to the Intel 810
969 and 815 chipsets. Say Y if you have and plan to use such a board.
971 To compile this driver as a module, choose M here: the
972 module will be called i810fb.
974 For more information, please read
975 <file:Documentation/fb/intel810.txt>
978 bool "use VESA Generalized Timing Formula"
981 If you say Y, then the VESA standard, Generalized Timing Formula
982 or GTF, will be used to calculate the required video timing values
983 per video mode. Since the GTF allows nondiscrete timings
984 (nondiscrete being a range of values as opposed to discrete being a
985 set of values), you'll be able to use any combination of horizontal
986 and vertical resolutions, and vertical refresh rates without having
987 to specify your own timing parameters. This is especially useful
988 to maximize the performance of an aging display, or if you just
989 have a display with nonstandard dimensions. A VESA compliant
990 monitor is recommended, but can still work with non-compliant ones.
991 If you need or want this, then select this option. The timings may
992 not be compliant with Intel's recommended values. Use at your own
995 If you say N, the driver will revert to discrete video timings
996 using a set recommended by Intel in their documentation.
1001 bool "Enable DDC Support"
1002 depends on FB_I810 && FB_I810_GTF
1007 tristate "Intel LE80578 (Vermilion) support"
1008 depends on FB && PCI && X86
1009 select FB_MODE_HELPERS
1010 select FB_CFB_FILLRECT
1011 select FB_CFB_COPYAREA
1012 select FB_CFB_IMAGEBLIT
1014 This driver supports the LE80578 (Vermilion Range) chipset
1016 config FB_CARILLO_RANCH
1017 tristate "Intel Carillo Ranch support"
1018 depends on FB_LE80578 && FB && PCI && X86
1020 This driver supports the LE80578 (Carillo Ranch) board
1023 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
1024 depends on FB && EXPERIMENTAL && PCI && X86
1027 select FB_MODE_HELPERS
1028 select FB_CFB_FILLRECT
1029 select FB_CFB_COPYAREA
1030 select FB_CFB_IMAGEBLIT
1032 This driver supports the on-board graphics built in to the Intel
1033 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
1034 Say Y if you have and plan to use such a board.
1036 If you say Y here and want DDC/I2C support you must first say Y to
1037 "I2C support" and "I2C bit-banging support" in the character devices
1040 If you say M here then "I2C support" and "I2C bit-banging support"
1041 can be build either as modules or built-in.
1043 To compile this driver as a module, choose M here: the
1044 module will be called intelfb.
1046 For more information, please read <file:Documentation/fb/intelfb.txt>
1048 config FB_INTEL_DEBUG
1049 bool "Intel driver Debug Messages"
1052 Say Y here if you want the Intel driver to output all sorts
1053 of debugging information to provide to the maintainer when
1054 something goes wrong.
1057 bool "DDC/I2C for Intel framebuffer support"
1062 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1065 tristate "Matrox acceleration"
1066 depends on FB && PCI
1067 select FB_CFB_FILLRECT
1068 select FB_CFB_COPYAREA
1069 select FB_CFB_IMAGEBLIT
1070 select FB_TILEBLITTING
1071 select FB_MACMODES if PPC_PMAC
1073 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1074 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1075 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1076 Matrox G400, G450 or G550 card in your box.
1078 To compile this driver as a module, choose M here: the
1079 module will be called matroxfb.
1081 You can pass several parameters to the driver at boot time or at
1082 module load time. The parameters look like "video=matrox:XXX", and
1083 are described in <file:Documentation/fb/matroxfb.txt>.
1085 config FB_MATROX_MILLENIUM
1086 bool "Millennium I/II support"
1087 depends on FB_MATROX
1089 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1090 video card. If you select "Advanced lowlevel driver options" below,
1091 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1092 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1093 also use font widths different from 8.
1095 config FB_MATROX_MYSTIQUE
1096 bool "Mystique support"
1097 depends on FB_MATROX
1099 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1100 video card. If you select "Advanced lowlevel driver options" below,
1101 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1102 packed pixel and 32 bpp packed pixel. You can also use font widths
1106 bool "G100/G200/G400/G450/G550 support"
1107 depends on FB_MATROX
1109 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1110 video card. If you select "Advanced lowlevel driver options", you
1111 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1112 pixel and 32 bpp packed pixel. You can also use font widths
1115 If you need support for G400 secondary head, you must first say Y to
1116 "I2C support" in the character devices section, and then to
1117 "Matrox I2C support" and "G400 second head support" here in the
1118 framebuffer section. G450/G550 secondary head and digital output
1119 are supported without additional modules.
1121 The driver starts in monitor mode. You must use the matroxset tool
1122 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1123 swap primary and secondary head outputs, or to change output mode.
1124 Secondary head driver always start in 640x480 resolution and you
1125 must use fbset to change it.
1127 Do not forget that second head supports only 16 and 32 bpp
1128 packed pixels, so it is a good idea to compile them into the kernel
1129 too. You can use only some font widths, as the driver uses generic
1130 painting procedures (the secondary head does not use acceleration
1133 G450/G550 hardware can display TV picture only from secondary CRTC,
1134 and it performs no scaling, so picture must have 525 or 625 lines.
1136 config FB_MATROX_I2C
1137 tristate "Matrox I2C support"
1138 depends on FB_MATROX
1141 This drivers creates I2C buses which are needed for accessing the
1142 DDC (I2C) bus present on all Matroxes, an I2C bus which
1143 interconnects Matrox optional devices, like MGA-TVO on G200 and
1144 G400, and the secondary head DDC bus, present on G400 only.
1146 You can say Y or M here if you want to experiment with monitor
1147 detection code. You must say Y or M here if you want to use either
1148 second head of G400 or MGA-TVO on G200 or G400.
1150 If you compile it as module, it will create a module named
1153 config FB_MATROX_MAVEN
1154 tristate "G400 second head support"
1155 depends on FB_MATROX_G && FB_MATROX_I2C
1157 WARNING !!! This support does not work with G450 !!!
1159 Say Y or M here if you want to use a secondary head (meaning two
1160 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1161 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1162 secondary head output is blanked while you are in X. With XFree
1163 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1164 the fbdev driver on first head and the fbdev driver on second head.
1166 If you compile it as module, two modules are created,
1167 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1168 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1169 also load i2c-matroxfb to get it to run.
1171 The driver starts in monitor mode and you must use the matroxset
1173 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1174 PAL or NTSC or to swap primary and secondary head outputs.
1175 Secondary head driver also always start in 640x480 resolution, you
1176 must use fbset to change it.
1178 Also do not forget that second head supports only 16 and 32 bpp
1179 packed pixels, so it is a good idea to compile them into the kernel
1180 too. You can use only some font widths, as the driver uses generic
1181 painting procedures (the secondary head does not use acceleration
1184 config FB_MATROX_MULTIHEAD
1185 bool "Multihead support"
1186 depends on FB_MATROX
1188 Say Y here if you have more than one (supported) Matrox device in
1189 your computer and you want to use all of them for different monitors
1190 ("multihead"). If you have only one device, you should say N because
1191 the driver compiled with Y is larger and a bit slower, especially on
1194 If you said M to "Matrox unified accelerated driver" and N here, you
1195 will still be able to use several Matrox devices simultaneously:
1196 insert several instances of the module matroxfb into the kernel
1197 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1198 for the different Matrox devices. This method is slightly faster but
1199 uses 40 KB of kernel memory per Matrox card.
1201 There is no need for enabling 'Matrox multihead support' if you have
1202 only one Matrox card in the box.
1205 tristate "ATI Radeon display support"
1206 depends on FB && PCI
1207 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1208 select FB_MODE_HELPERS
1209 select FB_CFB_FILLRECT
1210 select FB_CFB_COPYAREA
1211 select FB_CFB_IMAGEBLIT
1212 select FB_MACMODES if PPC_OF
1214 Choose this option if you want to use an ATI Radeon graphics card as
1215 a framebuffer device. There are both PCI and AGP versions. You
1216 don't need to choose this to run the Radeon in plain VGA mode.
1218 If you say Y here and want DDC/I2C support you must first say Y to
1219 "I2C support" and "I2C bit-banging support" in the character devices
1222 If you say M here then "I2C support" and "I2C bit-banging support"
1223 can be build either as modules or built-in.
1225 There is a product page at
1226 http://apps.ati.com/ATIcompare/
1228 config FB_RADEON_I2C
1229 bool "DDC/I2C for ATI Radeon support"
1230 depends on FB_RADEON
1234 Say Y here if you want DDC/I2C support for your Radeon board.
1236 config FB_RADEON_BACKLIGHT
1237 bool "Support for backlight control"
1238 depends on FB_RADEON
1241 Say Y here if you want to control the backlight of your display.
1243 config FB_RADEON_DEBUG
1244 bool "Lots of debug output from Radeon driver"
1245 depends on FB_RADEON
1248 Say Y here if you want the Radeon driver to output all sorts
1249 of debugging information to provide to the maintainer when
1250 something goes wrong.
1253 tristate "ATI Rage128 display support"
1254 depends on FB && PCI
1255 select FB_CFB_FILLRECT
1256 select FB_CFB_COPYAREA
1257 select FB_CFB_IMAGEBLIT
1258 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1259 select FB_MACMODES if PPC_PMAC
1261 This driver supports graphics boards with the ATI Rage128 chips.
1262 Say Y if you have such a graphics board and read
1263 <file:Documentation/fb/aty128fb.txt>.
1265 To compile this driver as a module, choose M here: the
1266 module will be called aty128fb.
1268 config FB_ATY128_BACKLIGHT
1269 bool "Support for backlight control"
1270 depends on FB_ATY128
1273 Say Y here if you want to control the backlight of your display.
1276 tristate "ATI Mach64 display support" if PCI || ATARI
1277 depends on FB && !SPARC32
1278 select FB_CFB_FILLRECT
1279 select FB_CFB_COPYAREA
1280 select FB_CFB_IMAGEBLIT
1281 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1282 select FB_MACMODES if PPC
1284 This driver supports graphics boards with the ATI Mach64 chips.
1285 Say Y if you have such a graphics board.
1287 To compile this driver as a module, choose M here: the
1288 module will be called atyfb.
1291 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1292 depends on PCI && FB_ATY
1293 default y if SPARC64 && PCI
1295 Say Y here to support use of ATI's 64-bit Rage boards (or other
1296 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1297 framebuffer device. The ATI product support page for these boards
1298 is at <http://support.ati.com/products/pc/mach64/>.
1300 config FB_ATY_GENERIC_LCD
1301 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1302 depends on FB_ATY_CT
1304 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1305 Rage XC, or Rage XL chipset.
1308 bool "Mach64 GX support" if PCI
1312 Say Y here to support use of the ATI Mach64 Graphics Expression
1313 board (or other boards based on the Mach64 GX chipset) as a
1314 framebuffer device. The ATI product support page for these boards
1316 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1318 config FB_ATY_BACKLIGHT
1319 bool "Support for backlight control"
1323 Say Y here if you want to control the backlight of your display.
1326 tristate "S3 Trio/Virge support"
1327 depends on FB && PCI
1328 select FB_CFB_FILLRECT
1329 select FB_CFB_COPYAREA
1330 select FB_CFB_IMAGEBLIT
1331 select FB_TILEBLITTING
1334 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1336 Driver for graphics boards with S3 Trio / S3 Virge chip.
1339 tristate "S3 Savage support"
1340 depends on FB && PCI && EXPERIMENTAL
1341 select FB_MODE_HELPERS
1342 select FB_CFB_FILLRECT
1343 select FB_CFB_COPYAREA
1344 select FB_CFB_IMAGEBLIT
1347 This driver supports notebooks and computers with S3 Savage PCI/AGP
1350 Say Y if you have such a graphics card.
1352 To compile this driver as a module, choose M here; the module
1353 will be called savagefb.
1355 config FB_SAVAGE_I2C
1356 bool "Enable DDC2 Support"
1357 depends on FB_SAVAGE
1360 This enables I2C support for S3 Savage Chipsets. This is used
1361 only for getting EDID information from the attached display
1362 allowing for robust video mode handling and switching.
1364 Because fbdev-2.6 requires that drivers must be able to
1365 independently validate video mode parameters, you should say Y
1368 config FB_SAVAGE_ACCEL
1369 bool "Enable Console Acceleration"
1370 depends on FB_SAVAGE
1373 This option will compile in console acceleration support. If
1374 the resulting framebuffer console has bothersome glitches, then
1378 tristate "SiS/XGI display support"
1379 depends on FB && PCI
1380 select FB_CFB_FILLRECT
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1384 This is the frame buffer device driver for the SiS 300, 315, 330
1385 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1386 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1388 To compile this driver as a module, choose M here; the module
1389 will be called sisfb.
1392 bool "SiS 300 series support"
1395 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1398 bool "SiS 315/330/340 series and XGI support"
1401 Say Y here to support use of the SiS 315, 330 and 340 series
1402 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1403 as XGI V3XT, V5, V8 and Z7.
1406 tristate "NeoMagic display support"
1407 depends on FB && PCI
1408 select FB_MODE_HELPERS
1409 select FB_CFB_FILLRECT
1410 select FB_CFB_COPYAREA
1411 select FB_CFB_IMAGEBLIT
1414 This driver supports notebooks with NeoMagic PCI chips.
1415 Say Y if you have such a graphics card.
1417 To compile this driver as a module, choose M here: the
1418 module will be called neofb.
1421 tristate "IMG Kyro support"
1422 depends on FB && PCI
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1427 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1430 To compile this driver as a module, choose M here: the
1431 module will be called kyrofb.
1434 tristate "3Dfx Banshee/Voodoo3 display support"
1435 depends on FB && PCI
1436 select FB_CFB_IMAGEBLIT
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1440 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1441 chips. Say Y if you have such a graphics board.
1443 To compile this driver as a module, choose M here: the
1444 module will be called tdfxfb.
1446 config FB_3DFX_ACCEL
1447 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1448 depends on FB_3DFX && EXPERIMENTAL
1450 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1451 with acceleration functions.
1455 tristate "3Dfx Voodoo Graphics (sst1) support"
1456 depends on FB && PCI
1457 select FB_CFB_FILLRECT
1458 select FB_CFB_COPYAREA
1459 select FB_CFB_IMAGEBLIT
1461 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1462 Voodoo2 (cvg) based graphics card.
1464 To compile this driver as a module, choose M here: the
1465 module will be called sstfb.
1467 WARNING: Do not use any application that uses the 3D engine
1468 (namely glide) while using this driver.
1469 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1470 options and other important info support.
1473 tristate "VIA VT8623 support"
1474 depends on FB && PCI
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1478 select FB_TILEBLITTING
1481 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1483 Driver for CastleRock integrated graphics core in the
1484 VIA VT8623 [Apollo CLE266] chipset.
1487 tristate "Cyberblade/i1 support"
1488 depends on FB && PCI && X86_32 && !64BIT
1489 select FB_CFB_IMAGEBLIT
1492 This driver is supposed to support the Trident Cyberblade/i1
1493 graphics core integrated in the VIA VT8601A North Bridge,
1494 also known as VIA Apollo PLE133.
1497 - Developed, tested and working on EPIA 5000 and EPIA 800.
1498 - Does work reliable on all systems with CRT/LCD connected to
1500 - Should work on systems that do use the internal LCD port, but
1501 this is absolutely not tested.
1503 Character imageblit, copyarea and rectangle fill are hw accelerated,
1504 ypan scrolling is used by default.
1506 Please do read <file:Documentation/fb/cyblafb/*>.
1508 To compile this driver as a module, choose M here: the
1509 module will be called cyblafb.
1512 tristate "Trident support"
1513 depends on FB && PCI
1514 select FB_CFB_FILLRECT
1515 select FB_CFB_COPYAREA
1516 select FB_CFB_IMAGEBLIT
1518 This driver is supposed to support graphics boards with the
1519 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1520 but also on some motherboards. For more information, read
1521 <file:Documentation/fb/tridentfb.txt>
1523 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1526 Say Y if you have such a graphics board.
1529 To compile this driver as a module, choose M here: the
1530 module will be called tridentfb.
1532 config FB_TRIDENT_ACCEL
1533 bool "Trident Acceleration functions (EXPERIMENTAL)"
1534 depends on FB_TRIDENT && EXPERIMENTAL
1536 This will compile the Trident frame buffer device with
1537 acceleration functions.
1540 tristate "ARK 2000PV support"
1541 depends on FB && PCI
1542 select FB_CFB_FILLRECT
1543 select FB_CFB_COPYAREA
1544 select FB_CFB_IMAGEBLIT
1545 select FB_TILEBLITTING
1548 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1550 Driver for PCI graphics boards with ARK 2000PV chip
1551 and ICS 5342 RAMDAC.
1554 tristate "Permedia3 support (EXPERIMENTAL)"
1555 depends on FB && PCI && EXPERIMENTAL
1556 select FB_CFB_FILLRECT
1557 select FB_CFB_COPYAREA
1558 select FB_CFB_IMAGEBLIT
1560 This is the frame buffer device driver for the 3DLabs Permedia3
1561 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1562 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1563 and maybe other boards.
1566 bool "Au1100 LCD Driver"
1567 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1570 bool "Au1200 LCD Driver"
1571 depends on (FB = y) && MIPS && SOC_AU1200
1572 select FB_CFB_FILLRECT
1573 select FB_CFB_COPYAREA
1574 select FB_CFB_IMAGEBLIT
1576 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1577 various panels and CRTs by passing in kernel cmd line option
1578 au1200fb:panel=<name>.
1580 source "drivers/video/geode/Kconfig"
1583 tristate "HD64461 Frame Buffer support"
1584 depends on FB && HD64461
1585 select FB_CFB_FILLRECT
1586 select FB_CFB_COPYAREA
1587 select FB_CFB_IMAGEBLIT
1589 This is the frame buffer device driver for the Hitachi HD64461 LCD
1593 bool "PMAG-AA TURBOchannel framebuffer support"
1594 depends on (FB = y) && TC
1595 select FB_CFB_FILLRECT
1596 select FB_CFB_COPYAREA
1597 select FB_CFB_IMAGEBLIT
1599 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1600 used mainly in the MIPS-based DECstation series.
1603 tristate "PMAG-BA TURBOchannel framebuffer support"
1605 select FB_CFB_FILLRECT
1606 select FB_CFB_COPYAREA
1607 select FB_CFB_IMAGEBLIT
1609 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1610 used mainly in the MIPS-based DECstation series.
1613 tristate "PMAGB-B TURBOchannel framebuffer support"
1615 select FB_CFB_FILLRECT
1616 select FB_CFB_COPYAREA
1617 select FB_CFB_IMAGEBLIT
1619 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1620 in the MIPS-based DECstation series. The card is currently only
1621 supported in 1280x1024x8 mode.
1624 bool "Maxine (Personal DECstation) onboard framebuffer support"
1625 depends on (FB = y) && MACH_DECSTATION
1626 select FB_CFB_FILLRECT
1627 select FB_CFB_COPYAREA
1628 select FB_CFB_IMAGEBLIT
1630 Support for the onboard framebuffer (1024x768x8) in the Personal
1631 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1635 bool "TMPTX3912/PR31700 frame buffer support"
1636 depends on (FB = y) && NINO
1637 select FB_CFB_FILLRECT
1638 select FB_CFB_COPYAREA
1639 select FB_CFB_IMAGEBLIT
1641 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1642 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1644 Say Y here to enable kernel support for the on-board framebuffer.
1647 bool "G364 frame buffer support"
1648 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1649 select FB_CFB_FILLRECT
1650 select FB_CFB_COPYAREA
1651 select FB_CFB_IMAGEBLIT
1653 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1654 Olivetti M700-10 systems.
1657 bool "Motorola 68328 native frame buffer support"
1658 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1659 select FB_CFB_FILLRECT
1660 select FB_CFB_COPYAREA
1661 select FB_CFB_IMAGEBLIT
1663 Say Y here if you want to support the built-in frame buffer of
1664 the Motorola 68328 CPU family.
1667 tristate "PXA LCD framebuffer support"
1668 depends on FB && ARCH_PXA
1669 select FB_CFB_FILLRECT
1670 select FB_CFB_COPYAREA
1671 select FB_CFB_IMAGEBLIT
1673 Frame buffer driver for the built-in LCD controller in the Intel
1676 This driver is also available as a module ( = code which can be
1677 inserted and removed from the running kernel whenever you want). The
1678 module will be called pxafb. If you want to compile it as a module,
1679 say M here and read <file:Documentation/kbuild/modules.txt>.
1683 config FB_PXA_PARAMETERS
1684 bool "PXA LCD command line parameters"
1688 Enable the use of kernel command line or module parameters
1689 to configure the physical properties of the LCD panel when
1690 using the PXA LCD driver.
1692 This option allows you to override the panel parameters
1693 supplied by the platform in order to support multiple
1694 different models of flatpanel. If you will only be using a
1695 single model of flatpanel then you can safely leave this
1698 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1701 tristate "2700G LCD framebuffer support"
1702 depends on FB && ARCH_PXA
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1711 bool "Enable debugging info via debugfs"
1712 depends on FB_MBX && DEBUG_FS
1715 Enable this if you want debugging information using the debug
1716 filesystem (debugfs)
1721 tristate "W100 frame buffer support"
1722 depends on FB && PXA_SHARPSL
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1729 This driver is also available as a module ( = code which can be
1730 inserted and removed from the running kernel whenever you want). The
1731 module will be called w100fb. If you want to compile it as a module,
1732 say M here and read <file:Documentation/kbuild/modules.txt>.
1737 tristate "S3C2410 LCD framebuffer support"
1738 depends on FB && ARCH_S3C2410
1739 select FB_CFB_FILLRECT
1740 select FB_CFB_COPYAREA
1741 select FB_CFB_IMAGEBLIT
1743 Frame buffer driver for the built-in LCD controller in the Samsung
1746 This driver is also available as a module ( = code which can be
1747 inserted and removed from the running kernel whenever you want). The
1748 module will be called s3c2410fb. If you want to compile it as a module,
1749 say M here and read <file:Documentation/kbuild/modules.txt>.
1752 config FB_S3C2410_DEBUG
1753 bool "S3C2410 lcd debug messages"
1754 depends on FB_S3C2410
1756 Turn on debugging messages. Note that you can set/unset at run time
1760 tristate "Silicon Motion SM501 framebuffer support"
1761 depends on FB && MFD_SM501
1762 select FB_CFB_FILLRECT
1763 select FB_CFB_COPYAREA
1764 select FB_CFB_IMAGEBLIT
1766 Frame buffer driver for the CRT and LCD controllers in the Silicon
1769 This driver is also available as a module ( = code which can be
1770 inserted and removed from the running kernel whenever you want). The
1771 module will be called sm501fb. If you want to compile it as a module,
1772 say M here and read <file:Documentation/modules.txt>.
1777 config FB_PNX4008_DUM
1778 tristate "Display Update Module support on Philips PNX4008 board"
1779 depends on FB && ARCH_PNX4008
1781 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1783 config FB_PNX4008_DUM_RGB
1784 tristate "RGB Framebuffer support on Philips PNX4008 board"
1785 depends on FB_PNX4008_DUM
1786 select FB_CFB_FILLRECT
1787 select FB_CFB_COPYAREA
1788 select FB_CFB_IMAGEBLIT
1790 Say Y here to enable support for PNX4008 RGB Framebuffer
1792 config FB_IBM_GXT4500
1793 tristate "Framebuffer support for IBM GXT4500P adaptor"
1795 select FB_CFB_FILLRECT
1796 select FB_CFB_COPYAREA
1797 select FB_CFB_IMAGEBLIT
1799 Say Y here to enable support for the IBM GXT4500P display
1800 adaptor, found on some IBM System P (pSeries) machines.
1803 tristate "PS3 GPU framebuffer driver"
1804 depends on FB && PS3_PS3AV
1805 select FB_SYS_FILLRECT
1806 select FB_SYS_COPYAREA
1807 select FB_SYS_IMAGEBLIT
1809 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1811 Include support for the virtual frame buffer in the PS3 platform.
1813 config FB_PS3_DEFAULT_SIZE_M
1814 int "PS3 default frame buffer size (in MiB)"
1818 This is the default size (in MiB) of the virtual frame buffer in
1820 The default value can be overridden on the kernel command line
1821 using the "ps3fb" option (e.g. "ps3fb=9M");
1824 tristate "Xilinx frame buffer support"
1825 depends on FB && XILINX_VIRTEX
1826 select FB_CFB_FILLRECT
1827 select FB_CFB_COPYAREA
1828 select FB_CFB_IMAGEBLIT
1830 Include support for the Xilinx ML300/ML403 reference design
1831 framebuffer. ML300 carries a 640*480 LCD display on the board,
1832 ML403 uses a standard DB15 VGA connector.
1835 source "drivers/video/omap/Kconfig"
1839 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1841 select FB_SYS_FILLRECT
1842 select FB_SYS_COPYAREA
1843 select FB_SYS_IMAGEBLIT
1846 This is a `virtual' frame buffer device. It operates on a chunk of
1847 unswappable kernel memory instead of on the memory of a graphics
1848 board. This means you cannot see any output sent to this frame
1849 buffer device, while it does consume precious memory. The main use
1850 of this frame buffer device is testing and debugging the frame
1851 buffer subsystem. Do NOT enable it for normal systems! To protect
1852 the innocent, it has to be enabled explicitly at boot time using the
1853 kernel option `video=vfb:'.
1855 To compile this driver as a module, choose M here: the
1856 module will be called vfb. In order to load it, you must use
1857 the vfb_enable=1 option.
1862 source "drivers/video/console/Kconfig"
1865 if FB || SGI_NEWPORT_CONSOLE
1866 source "drivers/video/logo/Kconfig"