5 menu "Graphics support"
7 source "drivers/video/backlight/Kconfig"
8 source "drivers/video/display/Kconfig"
15 tristate "Support for frame buffer devices"
17 The frame buffer device provides an abstraction for the graphics
18 hardware. It represents the frame buffer of some video hardware and
19 allows application software to access the graphics hardware through
20 a well-defined interface, so the software doesn't need to know
21 anything about the low-level (hardware register) stuff.
23 Frame buffer devices work identically across the different
24 architectures supported by Linux and make the implementation of
25 application programs easier and more portable; at this point, an X
26 server exists which uses the frame buffer device exclusively.
27 On several non-X86 architectures, the frame buffer device is the
28 only way to use the graphics hardware.
30 The device is accessed through special device nodes, usually located
31 in the /dev directory, i.e. /dev/fb*.
33 You need an utility program called fbset to make full use of frame
34 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
35 and the Framebuffer-HOWTO at
36 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
39 Say Y here and to the driver for your graphics board below if you
40 are compiling a kernel for a non-x86 architecture.
42 If you are compiling for the x86 architecture, you can say Y if you
43 want to play with it, but it is not essential. Please note that
44 running graphical applications that directly touch the hardware
45 (e.g. an accelerated X server) and that are not frame buffer
46 device-aware may cause unexpected results. If unsure, say N.
49 bool "Enable firmware EDID"
53 This enables access to the EDID transferred from the firmware.
54 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
55 transfers do not work for your driver and if you are using
56 nvidiafb, i810fb or savagefb.
58 In general, choosing Y for this option is safe. If you
59 experience extremely long delays while booting before you get
60 something on your display, try setting this to N. Matrox cards in
61 combination with certain motherboards and monitors are known to
62 suffer from this problem.
71 config FB_CFB_FILLRECT
76 Include the cfb_fillrect function for generic software rectangle
77 filling. This is used by drivers that don't provide their own
78 (accelerated) version.
80 config FB_CFB_COPYAREA
85 Include the cfb_copyarea function for generic software area copying.
86 This is used by drivers that don't provide their own (accelerated)
89 config FB_CFB_IMAGEBLIT
94 Include the cfb_imageblit function for generic software image
95 blitting. This is used by drivers that don't provide their own
96 (accelerated) version.
98 config FB_SYS_FILLRECT
103 Include the sys_fillrect function for generic software rectangle
104 filling. This is used by drivers that don't provide their own
105 (accelerated) version and the framebuffer is in system RAM.
107 config FB_SYS_COPYAREA
112 Include the sys_copyarea function for generic software area copying.
113 This is used by drivers that don't provide their own (accelerated)
114 version and the framebuffer is in system RAM.
116 config FB_SYS_IMAGEBLIT
121 Include the sys_imageblit function for generic software image
122 blitting. This is used by drivers that don't provide their own
123 (accelerated) version and the framebuffer is in system RAM.
130 config FB_DEFERRED_IO
140 Common utility functions useful to fbdev drivers of VGA-based
151 select BACKLIGHT_LCD_SUPPORT
152 select BACKLIGHT_CLASS_DEVICE
155 config FB_MODE_HELPERS
156 bool "Enable Video Mode Handling Helpers"
160 This enables functions for handling video modes using the
161 Generalized Timing Formula and the EDID parser. A few drivers rely
162 on this feature such as the radeonfb, rivafb, and the i810fb. If
163 your driver does not take advantage of this feature, choosing Y will
164 just increase the kernel size by about 5K.
166 config FB_TILEBLITTING
167 bool "Enable Tile Blitting Support"
171 This enables tile blitting. Tile blitting is a drawing technique
172 where the screen is divided into rectangular sections (tiles), whereas
173 the standard blitting divides the screen into pixels. Because the
174 default drawing element is a tile, drawing functions will be passed
175 parameters in terms of number of tiles instead of number of pixels.
176 For example, to draw a single character, instead of using bitmaps,
177 an index to an array of bitmaps will be used. To clear or move a
178 rectangular section of a screen, the rectangle will be described in
179 terms of number of tiles in the x- and y-axis.
181 This is particularly important to one driver, matroxfb. If
184 comment "Frame buffer hardware drivers"
188 tristate "Cirrus Logic support"
189 depends on FB && (ZORRO || PCI)
190 select FB_CFB_FILLRECT
191 select FB_CFB_COPYAREA
192 select FB_CFB_IMAGEBLIT
194 This enables support for Cirrus Logic GD542x/543x based boards on
195 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
197 If you have a PCI-based system, this enables support for these
198 chips: GD-543x, GD-544x, GD-5480.
200 Please read the file <file:Documentation/fb/cirrusfb.txt>.
202 Say N unless you have such a graphics board or plan to get one
203 before you next recompile the kernel.
206 tristate "Permedia2 support"
207 depends on FB && ((AMIGA && BROKEN) || PCI)
208 select FB_CFB_FILLRECT
209 select FB_CFB_COPYAREA
210 select FB_CFB_IMAGEBLIT
212 This is the frame buffer device driver for the Permedia2 AGP frame
213 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
215 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
217 config FB_PM2_FIFO_DISCONNECT
218 bool "enable FIFO disconnect feature"
219 depends on FB_PM2 && PCI
221 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
224 tristate "ARM PrimeCell PL110 support"
225 depends on FB && ARM && ARM_AMBA
226 select FB_CFB_FILLRECT
227 select FB_CFB_COPYAREA
228 select FB_CFB_IMAGEBLIT
230 This framebuffer device driver is for the ARM PrimeCell PL110
231 Colour LCD controller. ARM PrimeCells provide the building
232 blocks for System on a Chip devices.
234 If you want to compile this as a module (=code which can be
235 inserted into and removed from the running kernel), say M
236 here and read <file:Documentation/kbuild/modules.txt>. The module
237 will be called amba-clcd.
241 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
243 default FB_ARMCLCD_SHARP_LQ035Q7DB02
245 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
246 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
248 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
249 color QVGA, HRTFT panel. The LogicPD device includes
250 an integrated HRTFT controller IC.
251 The native resolution is 240x320.
253 config FB_ARMCLCD_SHARP_LQ057Q3DC02
254 bool "LogicPD LCD 5.7\" QVGA"
256 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
257 color QVGA, TFT panel. The LogicPD device includes an
258 The native resolution is 320x240.
260 config FB_ARMCLCD_SHARP_LQ64D343
261 bool "LogicPD LCD 6.4\" VGA"
263 This is an implementation of the Sharp LQ64D343, a 6.4"
264 color VGA, TFT panel. The LogicPD device includes an
265 The native resolution is 640x480.
267 config FB_ARMCLCD_SHARP_LQ10D368
268 bool "LogicPD LCD 10.4\" VGA"
270 This is an implementation of the Sharp LQ10D368, a 10.4"
271 color VGA, TFT panel. The LogicPD device includes an
272 The native resolution is 640x480.
275 config FB_ARMCLCD_SHARP_LQ121S1DG41
276 bool "LogicPD LCD 12.1\" SVGA"
278 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
279 color SVGA, TFT panel. The LogicPD device includes an
280 The native resolution is 800x600.
282 This panel requires a clock rate may be an integer fraction
283 of the base LCDCLK frequency. The driver will select the
284 highest frequency available that is lower than the maximum
285 allowed. The panel may flicker if the clock rate is
286 slower than the recommended minimum.
288 config FB_ARMCLCD_AUO_A070VW01_WIDE
289 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
291 This is an implementation of the AU Optronics, a 7.0"
292 WIDE Color. The native resolution is 234x480.
294 config FB_ARMCLCD_HITACHI
295 bool "Hitachi Wide Screen 800x480"
297 This is an implementation of the Hitachi 800x480.
303 bool "Acorn VIDC support"
304 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
305 select FB_CFB_FILLRECT
306 select FB_CFB_COPYAREA
307 select FB_CFB_IMAGEBLIT
309 This is the frame buffer device driver for the Acorn VIDC graphics
310 hardware found in Acorn RISC PCs and other ARM-based machines. If
314 bool "CLPS711X LCD support"
315 depends on (FB = y) && ARM && ARCH_CLPS711X
316 select FB_CFB_FILLRECT
317 select FB_CFB_COPYAREA
318 select FB_CFB_IMAGEBLIT
320 Say Y to enable the Framebuffer driver for the CLPS7111 and
324 bool "SA-1100 LCD support"
325 depends on (FB = y) && ARM && ARCH_SA1100
326 select FB_CFB_FILLRECT
327 select FB_CFB_COPYAREA
328 select FB_CFB_IMAGEBLIT
330 This is a framebuffer device for the SA-1100 LCD Controller.
331 See <http://www.linux-fbdev.org/> for information on framebuffer
334 If you plan to use the LCD display with your SA-1100 system, say
338 tristate "Motorola i.MX LCD support"
339 depends on FB && ARM && ARCH_IMX
340 select FB_CFB_FILLRECT
341 select FB_CFB_COPYAREA
342 select FB_CFB_IMAGEBLIT
345 tristate "CyberPro 2000/2010/5000 support"
346 depends on FB && PCI && (BROKEN || !SPARC64)
347 select FB_CFB_FILLRECT
348 select FB_CFB_COPYAREA
349 select FB_CFB_IMAGEBLIT
351 This enables support for the Integraphics CyberPro 20x0 and 5000
352 VGA chips used in the Rebel.com Netwinder and other machines.
353 Say Y if you have a NetWinder or a graphics card containing this
354 device, otherwise say N.
358 depends on (FB = y) && APOLLO
360 select FB_CFB_FILLRECT
361 select FB_CFB_IMAGEBLIT
365 depends on (FB = y) && Q40
367 select FB_CFB_FILLRECT
368 select FB_CFB_COPYAREA
369 select FB_CFB_IMAGEBLIT
372 tristate "Amiga native chipset support"
373 depends on FB && AMIGA
375 This is the frame buffer device driver for the builtin graphics
376 chipset found in Amigas.
378 To compile this driver as a module, choose M here: the
379 module will be called amifb.
382 bool "Amiga OCS chipset support"
385 This enables support for the original Agnus and Denise video chips,
386 found in the Amiga 1000 and most A500's and A2000's. If you intend
387 to run Linux on any of these systems, say Y; otherwise say N.
390 bool "Amiga ECS chipset support"
393 This enables support for the Enhanced Chip Set, found in later
394 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
395 you intend to run Linux on any of these systems, say Y; otherwise
399 bool "Amiga AGA chipset support"
402 This enables support for the Advanced Graphics Architecture (also
403 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
404 and CD32. If you intend to run Linux on any of these systems, say Y;
408 bool "Amiga FrameMaster II/Rainbow II support"
409 depends on (FB = y) && ZORRO
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
414 This is the frame buffer device driver for the Amiga FrameMaster
415 card from BSC (exhibited 1992 but not shipped as a CBM product).
418 tristate "Arc Monochrome LCD board support"
420 select FB_SYS_FILLRECT
421 select FB_SYS_COPYAREA
422 select FB_SYS_IMAGEBLIT
424 This enables support for the Arc Monochrome LCD board. The board
425 is based on the KS-108 lcd controller and is typically a matrix
426 of 2*n chips. This driver was tested with a 128x64 panel. This
427 driver supports it for use with x86 SBCs through a 16 bit GPIO
428 interface (8 bit data, 8 bit control). If you anticipate using
429 this driver, say Y or M; otherwise say N. You must specify the
430 GPIO IO address to be used for setting control and data.
433 bool "Atari native chipset support"
434 depends on (FB = y) && ATARI
435 select FB_CFB_FILLRECT
436 select FB_CFB_COPYAREA
437 select FB_CFB_IMAGEBLIT
439 This is the frame buffer device driver for the builtin graphics
440 chipset found in Ataris.
443 bool "Open Firmware frame buffer device support"
444 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
445 select FB_CFB_FILLRECT
446 select FB_CFB_COPYAREA
447 select FB_CFB_IMAGEBLIT
450 Say Y if you want support with Open Firmware for your graphics
454 bool "Apple \"control\" display support"
455 depends on (FB = y) && PPC_PMAC && PPC32
456 select FB_CFB_FILLRECT
457 select FB_CFB_COPYAREA
458 select FB_CFB_IMAGEBLIT
461 This driver supports a frame buffer for the graphics adapter in the
462 Power Macintosh 7300 and others.
465 bool "Apple \"platinum\" display support"
466 depends on (FB = y) && PPC_PMAC && PPC32
467 select FB_CFB_FILLRECT
468 select FB_CFB_COPYAREA
469 select FB_CFB_IMAGEBLIT
472 This driver supports a frame buffer for the "platinum" graphics
473 adapter in some Power Macintoshes.
476 bool "Apple \"valkyrie\" display support"
477 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
478 select FB_CFB_FILLRECT
479 select FB_CFB_COPYAREA
480 select FB_CFB_IMAGEBLIT
483 This driver supports a frame buffer for the "valkyrie" graphics
484 adapter in some Power Macintoshes.
487 bool "Chips 65550 display support"
488 depends on (FB = y) && PPC32
489 select FB_CFB_FILLRECT
490 select FB_CFB_COPYAREA
491 select FB_CFB_IMAGEBLIT
493 This is the frame buffer device driver for the Chips & Technologies
494 65550 graphics chip in PowerBooks.
497 bool "Asiliant (Chips) 69000 display support"
498 depends on (FB = y) && PCI
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
503 This is the frame buffer device driver for the Asiliant 69030 chipset
506 bool "IMS Twin Turbo display support"
507 depends on (FB = y) && PCI
508 select FB_CFB_IMAGEBLIT
509 select FB_MACMODES if PPC
511 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
512 many Macintosh and compatible computers.
515 tristate "VGA 16-color graphics support"
516 depends on FB && (X86 || PPC)
517 select FB_CFB_FILLRECT
518 select FB_CFB_COPYAREA
519 select FB_CFB_IMAGEBLIT
522 This is the frame buffer device driver for VGA 16 color graphic
523 cards. Say Y if you have such a card.
525 To compile this driver as a module, choose M here: the
526 module will be called vga16fb.
529 tristate "HP STI frame buffer device support"
530 depends on FB && PARISC
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
536 STI refers to the HP "Standard Text Interface" which is a set of
537 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
538 Enabling this option will implement the linux framebuffer device
539 using calls to the STI BIOS routines for initialisation.
541 If you enable this option, you will get a planar framebuffer device
542 /dev/fb which will work on the most common HP graphic cards of the
543 NGLE family, including the artist chips (in the 7xx and Bxxx series),
544 HCRX, HCRX24, CRX, CRX24 and VisEG series.
546 It is safe to enable this option, so you should probably say "Y".
549 bool "Generic Macintosh display support"
550 depends on (FB = y) && MAC
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
556 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
559 depends on (FB = y) && HP300
560 select FB_CFB_FILLRECT
561 select FB_CFB_IMAGEBLIT
565 tristate "TGA/SFB+ framebuffer support"
566 depends on FB && (ALPHA || TC)
567 select FB_CFB_FILLRECT
568 select FB_CFB_COPYAREA
569 select FB_CFB_IMAGEBLIT
572 This is the frame buffer device driver for generic TGA and SFB+
573 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
574 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
575 TURBOchannel cards, also known as PMAGD-A, -B and -C.
577 Due to hardware limitations ZLX-E2 and E3 cards are not supported
578 for DECstation 5000/200 systems. Additionally due to firmware
579 limitations these cards may cause troubles with booting DECstation
580 5000/240 and /260 systems, but are fully supported under Linux if
581 you manage to get it going. ;-)
583 Say Y if you have one of those.
586 bool "VESA VGA graphics support"
587 depends on (FB = y) && X86
588 select FB_CFB_FILLRECT
589 select FB_CFB_COPYAREA
590 select FB_CFB_IMAGEBLIT
593 This is the frame buffer device driver for generic VESA 2.0
594 compliant graphic cards. The older VESA 1.2 cards are not supported.
595 You will get a boot time penguin logo at no additional cost. Please
596 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
599 bool "Intel-based Macintosh Framebuffer Support"
600 depends on (FB = y) && X86 && EFI
601 select FB_CFB_FILLRECT
602 select FB_CFB_COPYAREA
603 select FB_CFB_IMAGEBLIT
605 This is the frame buffer device driver for the Intel-based Macintosh
608 tristate "Hecuba board support"
609 depends on FB && X86 && MMU
610 select FB_SYS_FILLRECT
611 select FB_SYS_COPYAREA
612 select FB_SYS_IMAGEBLIT
613 select FB_DEFERRED_IO
615 This enables support for the Hecuba board. This driver was tested
616 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
617 interface (8 bit data, 4 bit control). If you anticpate using
618 this driver, say Y or M; otherwise say N. You must specify the
619 GPIO IO address to be used for setting control and data.
622 tristate "Hercules mono graphics support"
624 select FB_CFB_FILLRECT
625 select FB_CFB_COPYAREA
626 select FB_CFB_IMAGEBLIT
628 Say Y here if you have a Hercules mono graphics card.
630 To compile this driver as a module, choose M here: the
631 module will be called hgafb.
633 As this card technology is 15 years old, most people will answer N
637 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
638 depends on FB_HGA && EXPERIMENTAL
640 This will compile the Hercules mono graphics with
641 acceleration functions.
644 tristate "SGI Visual Workstation framebuffer support"
645 depends on FB && X86_VISWS
646 select FB_CFB_FILLRECT
647 select FB_CFB_COPYAREA
648 select FB_CFB_IMAGEBLIT
650 SGI Visual Workstation support for framebuffer graphics.
653 bool "SGI Graphics Backend frame buffer support"
654 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
655 select FB_CFB_FILLRECT
656 select FB_CFB_COPYAREA
657 select FB_CFB_IMAGEBLIT
659 This is the frame buffer device driver for SGI Graphics Backend.
660 This chip is used in SGI O2 and Visual Workstation 320/540.
663 int "Video memory size in MB"
667 This is the amount of memory reserved for the framebuffer,
668 which can be any value between 1MB and 8MB.
671 bool "SBUS and UPA framebuffers"
672 depends on (FB = y) && SPARC
674 Say Y if you want support for SBUS or UPA based frame buffer device.
678 depends on (FB = y) && (SPARC && FB_SBUS)
679 select FB_CFB_FILLRECT
680 select FB_CFB_COPYAREA
681 select FB_CFB_IMAGEBLIT
683 This is the frame buffer device driver for the BWtwo frame buffer.
686 bool "CGthree support"
687 depends on (FB = y) && (SPARC && FB_SBUS)
688 select FB_CFB_FILLRECT
689 select FB_CFB_COPYAREA
690 select FB_CFB_IMAGEBLIT
692 This is the frame buffer device driver for the CGthree frame buffer.
695 bool "CGsix (GX,TurboGX) support"
696 depends on (FB = y) && (SPARC && FB_SBUS)
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
700 This is the frame buffer device driver for the CGsix (GX, TurboGX)
704 tristate "NEC PowerVR 2 display support"
705 depends on FB && SH_DREAMCAST
706 select FB_CFB_FILLRECT
707 select FB_CFB_COPYAREA
708 select FB_CFB_IMAGEBLIT
710 Say Y here if you have a PowerVR 2 card in your box. If you plan to
711 run linux on your Dreamcast, you will have to say Y here.
712 This driver may or may not work on other PowerVR 2 cards, but is
713 totally untested. Use at your own risk. If unsure, say N.
715 To compile this driver as a module, choose M here: the
716 module will be called pvr2fb.
718 You can pass several parameters to the driver at boot time or at
719 module load time. The parameters look like "video=pvr2:XXX", where
720 the meaning of XXX can be found at the end of the main source file
721 (<file:drivers/video/pvr2fb.c>). Please see the file
722 <file:Documentation/fb/pvr2fb.txt>.
725 bool "Epson 1355 framebuffer support"
726 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
727 select FB_CFB_FILLRECT
728 select FB_CFB_COPYAREA
729 select FB_CFB_IMAGEBLIT
731 Build in support for the SED1355 Epson Research Embedded RAMDAC
732 LCD/CRT Controller (since redesignated as the S1D13505) as a
733 framebuffer. Product specs at
734 <http://www.erd.epson.com/vdc/html/products.htm>.
737 tristate "Epson S1D13XXX framebuffer support"
739 select FB_CFB_FILLRECT
740 select FB_CFB_COPYAREA
741 select FB_CFB_IMAGEBLIT
743 Support for S1D13XXX framebuffer device family (currently only
744 working with S1D13806). Product specs at
745 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
748 tristate "nVidia Framebuffer Support"
750 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
751 select FB_MODE_HELPERS
752 select FB_CFB_FILLRECT
753 select FB_CFB_COPYAREA
754 select FB_CFB_IMAGEBLIT
758 This driver supports graphics boards with the nVidia chips, TNT
759 and newer. For very old chipsets, such as the RIVA128, then use
761 Say Y if you have such a graphics board.
763 To compile this driver as a module, choose M here: the
764 module will be called nvidiafb.
767 bool "Enable DDC Support"
771 This enables I2C support for nVidia Chipsets. This is used
772 only for getting EDID information from the attached display
773 allowing for robust video mode handling and switching.
775 Because fbdev-2.6 requires that drivers must be able to
776 independently validate video mode parameters, you should say Y
779 config FB_NVIDIA_BACKLIGHT
780 bool "Support for backlight control"
784 Say Y here if you want to control the backlight of your display.
787 tristate "nVidia Riva support"
789 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
790 select FB_MODE_HELPERS
791 select FB_CFB_FILLRECT
792 select FB_CFB_COPYAREA
793 select FB_CFB_IMAGEBLIT
797 This driver supports graphics boards with the nVidia Riva/Geforce
799 Say Y if you have such a graphics board.
801 To compile this driver as a module, choose M here: the
802 module will be called rivafb.
805 bool "Enable DDC Support"
809 This enables I2C support for nVidia Chipsets. This is used
810 only for getting EDID information from the attached display
811 allowing for robust video mode handling and switching.
813 Because fbdev-2.6 requires that drivers must be able to
814 independently validate video mode parameters, you should say Y
818 bool "Lots of debug output from Riva(nVidia) driver"
822 Say Y here if you want the Riva driver to output all sorts
823 of debugging information to provide to the maintainer when
824 something goes wrong.
826 config FB_RIVA_BACKLIGHT
827 bool "Support for backlight control"
831 Say Y here if you want to control the backlight of your display.
834 tristate "Intel 810/815 support (EXPERIMENTAL)"
835 depends on FB && EXPERIMENTAL && PCI && X86_32
838 select FB_MODE_HELPERS
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
844 This driver supports the on-board graphics built in to the Intel 810
845 and 815 chipsets. Say Y if you have and plan to use such a board.
847 To compile this driver as a module, choose M here: the
848 module will be called i810fb.
850 For more information, please read
851 <file:Documentation/fb/intel810.txt>
854 bool "use VESA Generalized Timing Formula"
857 If you say Y, then the VESA standard, Generalized Timing Formula
858 or GTF, will be used to calculate the required video timing values
859 per video mode. Since the GTF allows nondiscrete timings
860 (nondiscrete being a range of values as opposed to discrete being a
861 set of values), you'll be able to use any combination of horizontal
862 and vertical resolutions, and vertical refresh rates without having
863 to specify your own timing parameters. This is especially useful
864 to maximize the performance of an aging display, or if you just
865 have a display with nonstandard dimensions. A VESA compliant
866 monitor is recommended, but can still work with non-compliant ones.
867 If you need or want this, then select this option. The timings may
868 not be compliant with Intel's recommended values. Use at your own
871 If you say N, the driver will revert to discrete video timings
872 using a set recommended by Intel in their documentation.
877 bool "Enable DDC Support"
878 depends on FB_I810 && FB_I810_GTF
883 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
884 depends on FB && EXPERIMENTAL && PCI && X86
887 select FB_MODE_HELPERS
888 select FB_CFB_FILLRECT
889 select FB_CFB_COPYAREA
890 select FB_CFB_IMAGEBLIT
892 This driver supports the on-board graphics built in to the Intel
893 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
894 Say Y if you have and plan to use such a board.
896 If you say Y here and want DDC/I2C support you must first say Y to
897 "I2C support" and "I2C bit-banging support" in the character devices
900 If you say M here then "I2C support" and "I2C bit-banging support"
901 can be build either as modules or built-in.
903 To compile this driver as a module, choose M here: the
904 module will be called intelfb.
906 For more information, please read <file:Documentation/fb/intelfb.txt>
908 config FB_INTEL_DEBUG
909 bool "Intel driver Debug Messages"
912 Say Y here if you want the Intel driver to output all sorts
913 of debugging information to provide to the maintainer when
914 something goes wrong.
917 bool "DDC/I2C for Intel framebuffer support"
922 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
925 tristate "Matrox acceleration"
927 select FB_CFB_FILLRECT
928 select FB_CFB_COPYAREA
929 select FB_CFB_IMAGEBLIT
930 select FB_TILEBLITTING
931 select FB_MACMODES if PPC_PMAC
933 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
934 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
935 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
936 Matrox G400, G450 or G550 card in your box.
938 To compile this driver as a module, choose M here: the
939 module will be called matroxfb.
941 You can pass several parameters to the driver at boot time or at
942 module load time. The parameters look like "video=matrox:XXX", and
943 are described in <file:Documentation/fb/matroxfb.txt>.
945 config FB_MATROX_MILLENIUM
946 bool "Millennium I/II support"
949 Say Y here if you have a Matrox Millennium or Matrox Millennium II
950 video card. If you select "Advanced lowlevel driver options" below,
951 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
952 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
953 also use font widths different from 8.
955 config FB_MATROX_MYSTIQUE
956 bool "Mystique support"
959 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
960 video card. If you select "Advanced lowlevel driver options" below,
961 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
962 packed pixel and 32 bpp packed pixel. You can also use font widths
966 bool "G100/G200/G400/G450/G550 support"
969 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
970 video card. If you select "Advanced lowlevel driver options", you
971 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
972 pixel and 32 bpp packed pixel. You can also use font widths
975 If you need support for G400 secondary head, you must first say Y to
976 "I2C support" in the character devices section, and then to
977 "Matrox I2C support" and "G400 second head support" here in the
978 framebuffer section. G450/G550 secondary head and digital output
979 are supported without additional modules.
981 The driver starts in monitor mode. You must use the matroxset tool
982 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
983 swap primary and secondary head outputs, or to change output mode.
984 Secondary head driver always start in 640x480 resolution and you
985 must use fbset to change it.
987 Do not forget that second head supports only 16 and 32 bpp
988 packed pixels, so it is a good idea to compile them into the kernel
989 too. You can use only some font widths, as the driver uses generic
990 painting procedures (the secondary head does not use acceleration
993 G450/G550 hardware can display TV picture only from secondary CRTC,
994 and it performs no scaling, so picture must have 525 or 625 lines.
997 tristate "Matrox I2C support"
1001 This drivers creates I2C buses which are needed for accessing the
1002 DDC (I2C) bus present on all Matroxes, an I2C bus which
1003 interconnects Matrox optional devices, like MGA-TVO on G200 and
1004 G400, and the secondary head DDC bus, present on G400 only.
1006 You can say Y or M here if you want to experiment with monitor
1007 detection code. You must say Y or M here if you want to use either
1008 second head of G400 or MGA-TVO on G200 or G400.
1010 If you compile it as module, it will create a module named
1013 config FB_MATROX_MAVEN
1014 tristate "G400 second head support"
1015 depends on FB_MATROX_G && FB_MATROX_I2C
1017 WARNING !!! This support does not work with G450 !!!
1019 Say Y or M here if you want to use a secondary head (meaning two
1020 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1021 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1022 secondary head output is blanked while you are in X. With XFree
1023 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1024 the fbdev driver on first head and the fbdev driver on second head.
1026 If you compile it as module, two modules are created,
1027 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1028 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1029 also load i2c-matroxfb to get it to run.
1031 The driver starts in monitor mode and you must use the matroxset
1033 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1034 PAL or NTSC or to swap primary and secondary head outputs.
1035 Secondary head driver also always start in 640x480 resolution, you
1036 must use fbset to change it.
1038 Also do not forget that second head supports only 16 and 32 bpp
1039 packed pixels, so it is a good idea to compile them into the kernel
1040 too. You can use only some font widths, as the driver uses generic
1041 painting procedures (the secondary head does not use acceleration
1044 config FB_MATROX_MULTIHEAD
1045 bool "Multihead support"
1046 depends on FB_MATROX
1048 Say Y here if you have more than one (supported) Matrox device in
1049 your computer and you want to use all of them for different monitors
1050 ("multihead"). If you have only one device, you should say N because
1051 the driver compiled with Y is larger and a bit slower, especially on
1054 If you said M to "Matrox unified accelerated driver" and N here, you
1055 will still be able to use several Matrox devices simultaneously:
1056 insert several instances of the module matroxfb into the kernel
1057 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1058 for the different Matrox devices. This method is slightly faster but
1059 uses 40 KB of kernel memory per Matrox card.
1061 There is no need for enabling 'Matrox multihead support' if you have
1062 only one Matrox card in the box.
1065 tristate "ATI Radeon display support"
1066 depends on FB && PCI
1067 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1068 select FB_MODE_HELPERS
1069 select FB_CFB_FILLRECT
1070 select FB_CFB_COPYAREA
1071 select FB_CFB_IMAGEBLIT
1072 select FB_MACMODES if PPC_OF
1074 Choose this option if you want to use an ATI Radeon graphics card as
1075 a framebuffer device. There are both PCI and AGP versions. You
1076 don't need to choose this to run the Radeon in plain VGA mode.
1078 If you say Y here and want DDC/I2C support you must first say Y to
1079 "I2C support" and "I2C bit-banging support" in the character devices
1082 If you say M here then "I2C support" and "I2C bit-banging support"
1083 can be build either as modules or built-in.
1085 There is a product page at
1086 http://apps.ati.com/ATIcompare/
1088 config FB_RADEON_I2C
1089 bool "DDC/I2C for ATI Radeon support"
1090 depends on FB_RADEON
1094 Say Y here if you want DDC/I2C support for your Radeon board.
1096 config FB_RADEON_BACKLIGHT
1097 bool "Support for backlight control"
1098 depends on FB_RADEON
1101 Say Y here if you want to control the backlight of your display.
1103 config FB_RADEON_DEBUG
1104 bool "Lots of debug output from Radeon driver"
1105 depends on FB_RADEON
1108 Say Y here if you want the Radeon driver to output all sorts
1109 of debugging information to provide to the maintainer when
1110 something goes wrong.
1113 tristate "ATI Rage128 display support"
1114 depends on FB && PCI
1115 select FB_CFB_FILLRECT
1116 select FB_CFB_COPYAREA
1117 select FB_CFB_IMAGEBLIT
1118 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1119 select FB_MACMODES if PPC_PMAC
1121 This driver supports graphics boards with the ATI Rage128 chips.
1122 Say Y if you have such a graphics board and read
1123 <file:Documentation/fb/aty128fb.txt>.
1125 To compile this driver as a module, choose M here: the
1126 module will be called aty128fb.
1128 config FB_ATY128_BACKLIGHT
1129 bool "Support for backlight control"
1130 depends on FB_ATY128
1133 Say Y here if you want to control the backlight of your display.
1136 tristate "ATI Mach64 display support" if PCI || ATARI
1137 depends on FB && !SPARC32
1138 select FB_CFB_FILLRECT
1139 select FB_CFB_COPYAREA
1140 select FB_CFB_IMAGEBLIT
1141 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1142 select FB_MACMODES if PPC
1144 This driver supports graphics boards with the ATI Mach64 chips.
1145 Say Y if you have such a graphics board.
1147 To compile this driver as a module, choose M here: the
1148 module will be called atyfb.
1151 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1152 depends on PCI && FB_ATY
1153 default y if SPARC64 && FB_PCI
1155 Say Y here to support use of ATI's 64-bit Rage boards (or other
1156 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1157 framebuffer device. The ATI product support page for these boards
1158 is at <http://support.ati.com/products/pc/mach64/>.
1160 config FB_ATY_GENERIC_LCD
1161 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1162 depends on FB_ATY_CT
1164 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1165 Rage XC, or Rage XL chipset.
1168 bool "Mach64 GX support" if PCI
1172 Say Y here to support use of the ATI Mach64 Graphics Expression
1173 board (or other boards based on the Mach64 GX chipset) as a
1174 framebuffer device. The ATI product support page for these boards
1176 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1178 config FB_ATY_BACKLIGHT
1179 bool "Support for backlight control"
1183 Say Y here if you want to control the backlight of your display.
1186 tristate "S3 Trio/Virge support"
1187 depends on FB && PCI
1188 select FB_CFB_FILLRECT
1189 select FB_CFB_COPYAREA
1190 select FB_CFB_IMAGEBLIT
1191 select FB_TILEBLITTING
1195 Driver for graphics boards with S3 Trio / S3 Virge chip.
1198 tristate "S3 Savage support"
1199 depends on FB && PCI && EXPERIMENTAL
1200 select FB_MODE_HELPERS
1201 select FB_CFB_FILLRECT
1202 select FB_CFB_COPYAREA
1203 select FB_CFB_IMAGEBLIT
1206 This driver supports notebooks and computers with S3 Savage PCI/AGP
1209 Say Y if you have such a graphics card.
1211 To compile this driver as a module, choose M here; the module
1212 will be called savagefb.
1214 config FB_SAVAGE_I2C
1215 bool "Enable DDC2 Support"
1216 depends on FB_SAVAGE
1219 This enables I2C support for S3 Savage Chipsets. This is used
1220 only for getting EDID information from the attached display
1221 allowing for robust video mode handling and switching.
1223 Because fbdev-2.6 requires that drivers must be able to
1224 independently validate video mode parameters, you should say Y
1227 config FB_SAVAGE_ACCEL
1228 bool "Enable Console Acceleration"
1229 depends on FB_SAVAGE
1232 This option will compile in console acceleration support. If
1233 the resulting framebuffer console has bothersome glitches, then
1237 tristate "SiS/XGI display support"
1238 depends on FB && PCI
1239 select FB_CFB_FILLRECT
1240 select FB_CFB_COPYAREA
1241 select FB_CFB_IMAGEBLIT
1243 This is the frame buffer device driver for the SiS 300, 315, 330
1244 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1245 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1247 To compile this driver as a module, choose M here; the module
1248 will be called sisfb.
1251 bool "SiS 300 series support"
1254 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1257 bool "SiS 315/330/340 series and XGI support"
1260 Say Y here to support use of the SiS 315, 330 and 340 series
1261 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1262 as XGI V3XT, V5, V8 and Z7.
1265 tristate "NeoMagic display support"
1266 depends on FB && PCI
1267 select FB_MODE_HELPERS
1268 select FB_CFB_FILLRECT
1269 select FB_CFB_COPYAREA
1270 select FB_CFB_IMAGEBLIT
1273 This driver supports notebooks with NeoMagic PCI chips.
1274 Say Y if you have such a graphics card.
1276 To compile this driver as a module, choose M here: the
1277 module will be called neofb.
1280 tristate "IMG Kyro support"
1281 depends on FB && PCI
1282 select FB_CFB_FILLRECT
1283 select FB_CFB_COPYAREA
1284 select FB_CFB_IMAGEBLIT
1286 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1289 To compile this driver as a module, choose M here: the
1290 module will be called kyrofb.
1293 tristate "3Dfx Banshee/Voodoo3 display support"
1294 depends on FB && PCI
1295 select FB_CFB_IMAGEBLIT
1296 select FB_CFB_FILLRECT
1297 select FB_CFB_COPYAREA
1299 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1300 chips. Say Y if you have such a graphics board.
1302 To compile this driver as a module, choose M here: the
1303 module will be called tdfxfb.
1305 config FB_3DFX_ACCEL
1306 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1307 depends on FB_3DFX && EXPERIMENTAL
1309 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1310 with acceleration functions.
1314 tristate "3Dfx Voodoo Graphics (sst1) support"
1315 depends on FB && PCI
1316 select FB_CFB_FILLRECT
1317 select FB_CFB_COPYAREA
1318 select FB_CFB_IMAGEBLIT
1320 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1321 Voodoo2 (cvg) based graphics card.
1323 To compile this driver as a module, choose M here: the
1324 module will be called sstfb.
1326 WARNING: Do not use any application that uses the 3D engine
1327 (namely glide) while using this driver.
1328 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1329 options and other important info support.
1332 tristate "Cyberblade/i1 support"
1333 depends on FB && PCI && X86_32 && !64BIT
1334 select FB_CFB_IMAGEBLIT
1337 This driver is supposed to support the Trident Cyberblade/i1
1338 graphics core integrated in the VIA VT8601A North Bridge,
1339 also known as VIA Apollo PLE133.
1342 - Developed, tested and working on EPIA 5000 and EPIA 800.
1343 - Does work reliable on all systems with CRT/LCD connected to
1345 - Should work on systems that do use the internal LCD port, but
1346 this is absolutely not tested.
1348 Character imageblit, copyarea and rectangle fill are hw accelerated,
1349 ypan scrolling is used by default.
1351 Please do read <file:Documentation/fb/cyblafb/*>.
1353 To compile this driver as a module, choose M here: the
1354 module will be called cyblafb.
1357 tristate "Trident support"
1358 depends on FB && PCI
1359 select FB_CFB_FILLRECT
1360 select FB_CFB_COPYAREA
1361 select FB_CFB_IMAGEBLIT
1363 This driver is supposed to support graphics boards with the
1364 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1365 but also on some motherboards. For more information, read
1366 <file:Documentation/fb/tridentfb.txt>
1368 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1371 Say Y if you have such a graphics board.
1374 To compile this driver as a module, choose M here: the
1375 module will be called tridentfb.
1377 config FB_TRIDENT_ACCEL
1378 bool "Trident Acceleration functions (EXPERIMENTAL)"
1379 depends on FB_TRIDENT && EXPERIMENTAL
1381 This will compile the Trident frame buffer device with
1382 acceleration functions.
1385 tristate "Permedia3 support"
1386 depends on FB && PCI && BROKEN
1388 This is the frame buffer device driver for the 3DLabs Permedia3
1389 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1390 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1391 and maybe other boards.
1394 bool "Au1100 LCD Driver"
1395 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1398 bool "Au1200 LCD Driver"
1399 depends on (FB = y) && MIPS && SOC_AU1200
1400 select FB_CFB_FILLRECT
1401 select FB_CFB_COPYAREA
1402 select FB_CFB_IMAGEBLIT
1404 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1405 various panels and CRTs by passing in kernel cmd line option
1406 au1200fb:panel=<name>.
1408 source "drivers/video/geode/Kconfig"
1411 bool "Creator/Creator3D/Elite3D support"
1412 depends on FB_SBUS && SPARC64
1413 select FB_CFB_COPYAREA
1414 select FB_CFB_IMAGEBLIT
1416 This is the frame buffer device driver for the Creator, Creator3D,
1417 and Elite3D graphics boards.
1420 bool "TCX (SS4/SS5 only) support"
1422 select FB_CFB_FILLRECT
1423 select FB_CFB_COPYAREA
1424 select FB_CFB_IMAGEBLIT
1426 This is the frame buffer device driver for the TCX 24/8bit frame
1430 bool "CGfourteen (SX) support"
1432 select FB_CFB_FILLRECT
1433 select FB_CFB_COPYAREA
1434 select FB_CFB_IMAGEBLIT
1436 This is the frame buffer device driver for the CGfourteen frame
1437 buffer on Desktop SPARCsystems with the SX graphics option.
1440 bool "P9100 (Sparcbook 3 only) support"
1442 select FB_CFB_FILLRECT
1443 select FB_CFB_COPYAREA
1444 select FB_CFB_IMAGEBLIT
1446 This is the frame buffer device driver for the P9100 card
1447 supported on Sparcbook 3 machines.
1450 bool "Leo (ZX) support"
1452 select FB_CFB_FILLRECT
1453 select FB_CFB_COPYAREA
1454 select FB_CFB_IMAGEBLIT
1456 This is the frame buffer device driver for the SBUS-based Sun ZX
1457 (leo) frame buffer cards.
1460 bool "Sun XVR-500 3DLABS Wildcat support"
1461 depends on FB && PCI && SPARC64
1462 select FB_CFB_FILLRECT
1463 select FB_CFB_COPYAREA
1464 select FB_CFB_IMAGEBLIT
1466 This is the framebuffer device for the Sun XVR-500 and similar
1467 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1468 only works on sparc64 systems where the system firwmare has
1469 mostly initialized the card already. It is treated as a
1470 completely dumb framebuffer device.
1473 bool "Sun XVR-2500 3DLABS Wildcat support"
1474 depends on FB && PCI && SPARC64
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1479 This is the framebuffer device for the Sun XVR-2500 and similar
1480 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1481 only works on sparc64 systems where the system firwmare has
1482 mostly initialized the card already. It is treated as a
1483 completely dumb framebuffer device.
1486 bool "PCI framebuffers"
1487 depends on (FB = y) && PCI && SPARC
1490 bool "IGA 168x display support"
1491 depends on SPARC32 && FB_PCI
1492 select FB_CFB_FILLRECT
1493 select FB_CFB_COPYAREA
1494 select FB_CFB_IMAGEBLIT
1496 This is the framebuffer device for the INTERGRAPHICS 1680 and
1497 successor frame buffer cards.
1500 tristate "HD64461 Frame Buffer support"
1501 depends on FB && HD64461
1502 select FB_CFB_FILLRECT
1503 select FB_CFB_COPYAREA
1504 select FB_CFB_IMAGEBLIT
1506 This is the frame buffer device driver for the Hitachi HD64461 LCD
1510 bool "PMAG-AA TURBOchannel framebuffer support"
1511 depends on (FB = y) && TC
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1516 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1517 used mainly in the MIPS-based DECstation series.
1520 tristate "PMAG-BA TURBOchannel framebuffer support"
1522 select FB_CFB_FILLRECT
1523 select FB_CFB_COPYAREA
1524 select FB_CFB_IMAGEBLIT
1526 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1527 used mainly in the MIPS-based DECstation series.
1530 tristate "PMAGB-B TURBOchannel framebuffer support"
1532 select FB_CFB_FILLRECT
1533 select FB_CFB_COPYAREA
1534 select FB_CFB_IMAGEBLIT
1536 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1537 in the MIPS-based DECstation series. The card is currently only
1538 supported in 1280x1024x8 mode.
1541 bool "Maxine (Personal DECstation) onboard framebuffer support"
1542 depends on (FB = y) && MACH_DECSTATION
1543 select FB_CFB_FILLRECT
1544 select FB_CFB_COPYAREA
1545 select FB_CFB_IMAGEBLIT
1547 Support for the onboard framebuffer (1024x768x8) in the Personal
1548 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1552 bool "TMPTX3912/PR31700 frame buffer support"
1553 depends on (FB = y) && NINO
1554 select FB_CFB_FILLRECT
1555 select FB_CFB_COPYAREA
1556 select FB_CFB_IMAGEBLIT
1558 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1559 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1561 Say Y here to enable kernel support for the on-board framebuffer.
1564 bool "G364 frame buffer support"
1565 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1566 select FB_CFB_FILLRECT
1567 select FB_CFB_COPYAREA
1568 select FB_CFB_IMAGEBLIT
1570 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1571 Olivetti M700-10 systems.
1574 bool "Motorola 68328 native frame buffer support"
1575 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1576 select FB_CFB_FILLRECT
1577 select FB_CFB_COPYAREA
1578 select FB_CFB_IMAGEBLIT
1580 Say Y here if you want to support the built-in frame buffer of
1581 the Motorola 68328 CPU family.
1584 tristate "PXA LCD framebuffer support"
1585 depends on FB && ARCH_PXA
1586 select FB_CFB_FILLRECT
1587 select FB_CFB_COPYAREA
1588 select FB_CFB_IMAGEBLIT
1590 Frame buffer driver for the built-in LCD controller in the Intel
1593 This driver is also available as a module ( = code which can be
1594 inserted and removed from the running kernel whenever you want). The
1595 module will be called pxafb. If you want to compile it as a module,
1596 say M here and read <file:Documentation/kbuild/modules.txt>.
1600 config FB_PXA_PARAMETERS
1601 bool "PXA LCD command line parameters"
1605 Enable the use of kernel command line or module parameters
1606 to configure the physical properties of the LCD panel when
1607 using the PXA LCD driver.
1609 This option allows you to override the panel parameters
1610 supplied by the platform in order to support multiple
1611 different models of flatpanel. If you will only be using a
1612 single model of flatpanel then you can safely leave this
1615 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1618 tristate "2700G LCD framebuffer support"
1619 depends on FB && ARCH_PXA
1620 select FB_CFB_FILLRECT
1621 select FB_CFB_COPYAREA
1622 select FB_CFB_IMAGEBLIT
1624 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1628 bool "Enable debugging info via debugfs"
1629 depends on FB_MBX && DEBUG_FS
1632 Enable this if you want debugging information using the debug
1633 filesystem (debugfs)
1638 tristate "W100 frame buffer support"
1639 depends on FB && PXA_SHARPSL
1640 select FB_CFB_FILLRECT
1641 select FB_CFB_COPYAREA
1642 select FB_CFB_IMAGEBLIT
1644 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1646 This driver is also available as a module ( = code which can be
1647 inserted and removed from the running kernel whenever you want). The
1648 module will be called w100fb. If you want to compile it as a module,
1649 say M here and read <file:Documentation/kbuild/modules.txt>.
1654 tristate "S3C2410 LCD framebuffer support"
1655 depends on FB && ARCH_S3C2410
1656 select FB_CFB_FILLRECT
1657 select FB_CFB_COPYAREA
1658 select FB_CFB_IMAGEBLIT
1660 Frame buffer driver for the built-in LCD controller in the Samsung
1663 This driver is also available as a module ( = code which can be
1664 inserted and removed from the running kernel whenever you want). The
1665 module will be called s3c2410fb. If you want to compile it as a module,
1666 say M here and read <file:Documentation/kbuild/modules.txt>.
1669 config FB_S3C2410_DEBUG
1670 bool "S3C2410 lcd debug messages"
1671 depends on FB_S3C2410
1673 Turn on debugging messages. Note that you can set/unset at run time
1677 tristate "Silicon Motion SM501 framebuffer support"
1678 depends on FB && MFD_SM501
1679 select FB_CFB_FILLRECT
1680 select FB_CFB_COPYAREA
1681 select FB_CFB_IMAGEBLIT
1683 Frame buffer driver for the CRT and LCD controllers in the Silicon
1686 This driver is also available as a module ( = code which can be
1687 inserted and removed from the running kernel whenever you want). The
1688 module will be called sm501fb. If you want to compile it as a module,
1689 say M here and read <file:Documentation/modules.txt>.
1694 config FB_PNX4008_DUM
1695 tristate "Display Update Module support on Philips PNX4008 board"
1696 depends on FB && ARCH_PNX4008
1698 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1700 config FB_PNX4008_DUM_RGB
1701 tristate "RGB Framebuffer support on Philips PNX4008 board"
1702 depends on FB_PNX4008_DUM
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1707 Say Y here to enable support for PNX4008 RGB Framebuffer
1709 config FB_IBM_GXT4500
1710 tristate "Framebuffer support for IBM GXT4500P adaptor"
1712 select FB_CFB_FILLRECT
1713 select FB_CFB_COPYAREA
1714 select FB_CFB_IMAGEBLIT
1716 Say Y here to enable support for the IBM GXT4500P display
1717 adaptor, found on some IBM System P (pSeries) machines.
1720 bool "PS3 GPU framebuffer driver"
1721 depends on (FB = y) && PS3_PS3AV
1722 select FB_CFB_FILLRECT
1723 select FB_CFB_COPYAREA
1724 select FB_CFB_IMAGEBLIT
1726 Include support for the virtual frame buffer in the PS3 platform.
1728 config FB_PS3_DEFAULT_SIZE_M
1729 int "PS3 default frame buffer size (in MiB)"
1733 This is the default size (in MiB) of the virtual frame buffer in
1735 The default value can be overridden on the kernel command line
1736 using the "ps3fb" option (e.g. "ps3fb=9M");
1739 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1741 select FB_SYS_FILLRECT
1742 select FB_SYS_COPYAREA
1743 select FB_SYS_IMAGEBLIT
1745 This is a `virtual' frame buffer device. It operates on a chunk of
1746 unswappable kernel memory instead of on the memory of a graphics
1747 board. This means you cannot see any output sent to this frame
1748 buffer device, while it does consume precious memory. The main use
1749 of this frame buffer device is testing and debugging the frame
1750 buffer subsystem. Do NOT enable it for normal systems! To protect
1751 the innocent, it has to be enabled explicitly at boot time using the
1752 kernel option `video=vfb:'.
1754 To compile this driver as a module, choose M here: the
1755 module will be called vfb. In order to load it, you must use
1756 the vfb_enable=1 option.
1761 source "drivers/video/console/Kconfig"
1764 if FB || SGI_NEWPORT_CONSOLE
1765 source "drivers/video/logo/Kconfig"