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
425 This enables support for the Arc Monochrome LCD board. The board
426 is based on the KS-108 lcd controller and is typically a matrix
427 of 2*n chips. This driver was tested with a 128x64 panel. This
428 driver supports it for use with x86 SBCs through a 16 bit GPIO
429 interface (8 bit data, 8 bit control). If you anticipate using
430 this driver, say Y or M; otherwise say N. You must specify the
431 GPIO IO address to be used for setting control and data.
434 bool "Atari native chipset support"
435 depends on (FB = y) && ATARI
436 select FB_CFB_FILLRECT
437 select FB_CFB_COPYAREA
438 select FB_CFB_IMAGEBLIT
440 This is the frame buffer device driver for the builtin graphics
441 chipset found in Ataris.
444 bool "Open Firmware frame buffer device support"
445 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
451 Say Y if you want support with Open Firmware for your graphics
455 bool "Apple \"control\" display support"
456 depends on (FB = y) && PPC_PMAC && PPC32
457 select FB_CFB_FILLRECT
458 select FB_CFB_COPYAREA
459 select FB_CFB_IMAGEBLIT
462 This driver supports a frame buffer for the graphics adapter in the
463 Power Macintosh 7300 and others.
466 bool "Apple \"platinum\" display support"
467 depends on (FB = y) && PPC_PMAC && PPC32
468 select FB_CFB_FILLRECT
469 select FB_CFB_COPYAREA
470 select FB_CFB_IMAGEBLIT
473 This driver supports a frame buffer for the "platinum" graphics
474 adapter in some Power Macintoshes.
477 bool "Apple \"valkyrie\" display support"
478 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
479 select FB_CFB_FILLRECT
480 select FB_CFB_COPYAREA
481 select FB_CFB_IMAGEBLIT
484 This driver supports a frame buffer for the "valkyrie" graphics
485 adapter in some Power Macintoshes.
488 bool "Chips 65550 display support"
489 depends on (FB = y) && PPC32
490 select FB_CFB_FILLRECT
491 select FB_CFB_COPYAREA
492 select FB_CFB_IMAGEBLIT
494 This is the frame buffer device driver for the Chips & Technologies
495 65550 graphics chip in PowerBooks.
498 bool "Asiliant (Chips) 69000 display support"
499 depends on (FB = y) && PCI
500 select FB_CFB_FILLRECT
501 select FB_CFB_COPYAREA
502 select FB_CFB_IMAGEBLIT
504 This is the frame buffer device driver for the Asiliant 69030 chipset
507 bool "IMS Twin Turbo display support"
508 depends on (FB = y) && PCI
509 select FB_CFB_IMAGEBLIT
510 select FB_MACMODES if PPC
512 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
513 many Macintosh and compatible computers.
516 tristate "VGA 16-color graphics support"
517 depends on FB && (X86 || PPC)
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
522 select FONT_8x16 if FRAMEBUFFER_CONSOLE
524 This is the frame buffer device driver for VGA 16 color graphic
525 cards. Say Y if you have such a card.
527 To compile this driver as a module, choose M here: the
528 module will be called vga16fb.
531 tristate "HP STI frame buffer device support"
532 depends on FB && PARISC
533 select FB_CFB_FILLRECT
534 select FB_CFB_COPYAREA
535 select FB_CFB_IMAGEBLIT
538 STI refers to the HP "Standard Text Interface" which is a set of
539 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
540 Enabling this option will implement the linux framebuffer device
541 using calls to the STI BIOS routines for initialisation.
543 If you enable this option, you will get a planar framebuffer device
544 /dev/fb which will work on the most common HP graphic cards of the
545 NGLE family, including the artist chips (in the 7xx and Bxxx series),
546 HCRX, HCRX24, CRX, CRX24 and VisEG series.
548 It is safe to enable this option, so you should probably say "Y".
551 bool "Generic Macintosh display support"
552 depends on (FB = y) && MAC
553 select FB_CFB_FILLRECT
554 select FB_CFB_COPYAREA
555 select FB_CFB_IMAGEBLIT
558 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
561 depends on (FB = y) && HP300
562 select FB_CFB_FILLRECT
563 select FB_CFB_IMAGEBLIT
567 tristate "TGA/SFB+ framebuffer support"
568 depends on FB && (ALPHA || TC)
569 select FB_CFB_FILLRECT
570 select FB_CFB_COPYAREA
571 select FB_CFB_IMAGEBLIT
574 This is the frame buffer device driver for generic TGA and SFB+
575 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
576 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
577 TURBOchannel cards, also known as PMAGD-A, -B and -C.
579 Due to hardware limitations ZLX-E2 and E3 cards are not supported
580 for DECstation 5000/200 systems. Additionally due to firmware
581 limitations these cards may cause troubles with booting DECstation
582 5000/240 and /260 systems, but are fully supported under Linux if
583 you manage to get it going. ;-)
585 Say Y if you have one of those.
588 bool "VESA VGA graphics support"
589 depends on (FB = y) && X86
590 select FB_CFB_FILLRECT
591 select FB_CFB_COPYAREA
592 select FB_CFB_IMAGEBLIT
595 This is the frame buffer device driver for generic VESA 2.0
596 compliant graphic cards. The older VESA 1.2 cards are not supported.
597 You will get a boot time penguin logo at no additional cost. Please
598 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
601 bool "Intel-based Macintosh Framebuffer Support"
602 depends on (FB = y) && X86 && EFI
603 select FB_CFB_FILLRECT
604 select FB_CFB_COPYAREA
605 select FB_CFB_IMAGEBLIT
607 This is the frame buffer device driver for the Intel-based Macintosh
610 tristate "Hecuba board support"
611 depends on FB && X86 && MMU
612 select FB_SYS_FILLRECT
613 select FB_SYS_COPYAREA
614 select FB_SYS_IMAGEBLIT
616 select FB_DEFERRED_IO
618 This enables support for the Hecuba board. This driver was tested
619 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
620 interface (8 bit data, 4 bit control). If you anticpate using
621 this driver, say Y or M; otherwise say N. You must specify the
622 GPIO IO address to be used for setting control and data.
625 tristate "Hercules mono graphics support"
627 select FB_CFB_FILLRECT
628 select FB_CFB_COPYAREA
629 select FB_CFB_IMAGEBLIT
631 Say Y here if you have a Hercules mono graphics card.
633 To compile this driver as a module, choose M here: the
634 module will be called hgafb.
636 As this card technology is 15 years old, most people will answer N
640 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
641 depends on FB_HGA && EXPERIMENTAL
643 This will compile the Hercules mono graphics with
644 acceleration functions.
647 tristate "SGI Visual Workstation framebuffer support"
648 depends on FB && X86_VISWS
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
653 SGI Visual Workstation support for framebuffer graphics.
656 bool "SGI Graphics Backend frame buffer support"
657 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
658 select FB_CFB_FILLRECT
659 select FB_CFB_COPYAREA
660 select FB_CFB_IMAGEBLIT
662 This is the frame buffer device driver for SGI Graphics Backend.
663 This chip is used in SGI O2 and Visual Workstation 320/540.
666 int "Video memory size in MB"
670 This is the amount of memory reserved for the framebuffer,
671 which can be any value between 1MB and 8MB.
674 bool "SBUS and UPA framebuffers"
675 depends on (FB = y) && SPARC
677 Say Y if you want support for SBUS or UPA based frame buffer device.
681 depends on (FB = y) && (SPARC && FB_SBUS)
682 select FB_CFB_FILLRECT
683 select FB_CFB_COPYAREA
684 select FB_CFB_IMAGEBLIT
686 This is the frame buffer device driver for the BWtwo frame buffer.
689 bool "CGthree support"
690 depends on (FB = y) && (SPARC && FB_SBUS)
691 select FB_CFB_FILLRECT
692 select FB_CFB_COPYAREA
693 select FB_CFB_IMAGEBLIT
695 This is the frame buffer device driver for the CGthree frame buffer.
698 bool "CGsix (GX,TurboGX) support"
699 depends on (FB = y) && (SPARC && FB_SBUS)
700 select FB_CFB_COPYAREA
701 select FB_CFB_IMAGEBLIT
703 This is the frame buffer device driver for the CGsix (GX, TurboGX)
707 tristate "NEC PowerVR 2 display support"
708 depends on FB && SH_DREAMCAST
709 select FB_CFB_FILLRECT
710 select FB_CFB_COPYAREA
711 select FB_CFB_IMAGEBLIT
713 Say Y here if you have a PowerVR 2 card in your box. If you plan to
714 run linux on your Dreamcast, you will have to say Y here.
715 This driver may or may not work on other PowerVR 2 cards, but is
716 totally untested. Use at your own risk. If unsure, say N.
718 To compile this driver as a module, choose M here: the
719 module will be called pvr2fb.
721 You can pass several parameters to the driver at boot time or at
722 module load time. The parameters look like "video=pvr2:XXX", where
723 the meaning of XXX can be found at the end of the main source file
724 (<file:drivers/video/pvr2fb.c>). Please see the file
725 <file:Documentation/fb/pvr2fb.txt>.
728 bool "Epson 1355 framebuffer support"
729 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
730 select FB_CFB_FILLRECT
731 select FB_CFB_COPYAREA
732 select FB_CFB_IMAGEBLIT
734 Build in support for the SED1355 Epson Research Embedded RAMDAC
735 LCD/CRT Controller (since redesignated as the S1D13505) as a
736 framebuffer. Product specs at
737 <http://www.erd.epson.com/vdc/html/products.htm>.
740 tristate "Epson S1D13XXX framebuffer support"
742 select FB_CFB_FILLRECT
743 select FB_CFB_COPYAREA
744 select FB_CFB_IMAGEBLIT
746 Support for S1D13XXX framebuffer device family (currently only
747 working with S1D13806). Product specs at
748 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
751 tristate "nVidia Framebuffer Support"
753 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
754 select FB_MODE_HELPERS
755 select FB_CFB_FILLRECT
756 select FB_CFB_COPYAREA
757 select FB_CFB_IMAGEBLIT
761 This driver supports graphics boards with the nVidia chips, TNT
762 and newer. For very old chipsets, such as the RIVA128, then use
764 Say Y if you have such a graphics board.
766 To compile this driver as a module, choose M here: the
767 module will be called nvidiafb.
770 bool "Enable DDC Support"
774 This enables I2C support for nVidia Chipsets. This is used
775 only for getting EDID information from the attached display
776 allowing for robust video mode handling and switching.
778 Because fbdev-2.6 requires that drivers must be able to
779 independently validate video mode parameters, you should say Y
782 config FB_NVIDIA_BACKLIGHT
783 bool "Support for backlight control"
787 Say Y here if you want to control the backlight of your display.
790 tristate "nVidia Riva support"
792 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
793 select FB_MODE_HELPERS
794 select FB_CFB_FILLRECT
795 select FB_CFB_COPYAREA
796 select FB_CFB_IMAGEBLIT
800 This driver supports graphics boards with the nVidia Riva/Geforce
802 Say Y if you have such a graphics board.
804 To compile this driver as a module, choose M here: the
805 module will be called rivafb.
808 bool "Enable DDC Support"
812 This enables I2C support for nVidia Chipsets. This is used
813 only for getting EDID information from the attached display
814 allowing for robust video mode handling and switching.
816 Because fbdev-2.6 requires that drivers must be able to
817 independently validate video mode parameters, you should say Y
821 bool "Lots of debug output from Riva(nVidia) driver"
825 Say Y here if you want the Riva driver to output all sorts
826 of debugging information to provide to the maintainer when
827 something goes wrong.
829 config FB_RIVA_BACKLIGHT
830 bool "Support for backlight control"
834 Say Y here if you want to control the backlight of your display.
837 tristate "Intel 810/815 support (EXPERIMENTAL)"
838 depends on FB && EXPERIMENTAL && PCI && X86_32
841 select FB_MODE_HELPERS
842 select FB_CFB_FILLRECT
843 select FB_CFB_COPYAREA
844 select FB_CFB_IMAGEBLIT
847 This driver supports the on-board graphics built in to the Intel 810
848 and 815 chipsets. Say Y if you have and plan to use such a board.
850 To compile this driver as a module, choose M here: the
851 module will be called i810fb.
853 For more information, please read
854 <file:Documentation/fb/intel810.txt>
857 bool "use VESA Generalized Timing Formula"
860 If you say Y, then the VESA standard, Generalized Timing Formula
861 or GTF, will be used to calculate the required video timing values
862 per video mode. Since the GTF allows nondiscrete timings
863 (nondiscrete being a range of values as opposed to discrete being a
864 set of values), you'll be able to use any combination of horizontal
865 and vertical resolutions, and vertical refresh rates without having
866 to specify your own timing parameters. This is especially useful
867 to maximize the performance of an aging display, or if you just
868 have a display with nonstandard dimensions. A VESA compliant
869 monitor is recommended, but can still work with non-compliant ones.
870 If you need or want this, then select this option. The timings may
871 not be compliant with Intel's recommended values. Use at your own
874 If you say N, the driver will revert to discrete video timings
875 using a set recommended by Intel in their documentation.
880 bool "Enable DDC Support"
881 depends on FB_I810 && FB_I810_GTF
886 tristate "Intel LE80578 (Vermilion) support"
887 depends on FB && PCI && X86
888 select FB_MODE_HELPERS
889 select FB_CFB_FILLRECT
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This driver supports the LE80578 (Vermilion Range) chipset
895 config FB_CARILLO_RANCH
896 tristate "Intel Carillo Ranch support"
897 depends on FB_LE80578 && FB && PCI && X86
899 This driver supports the LE80578 (Carillo Ranch) board
902 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
903 depends on FB && EXPERIMENTAL && PCI && X86
906 select FB_MODE_HELPERS
907 select FB_CFB_FILLRECT
908 select FB_CFB_COPYAREA
909 select FB_CFB_IMAGEBLIT
911 This driver supports the on-board graphics built in to the Intel
912 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
913 Say Y if you have and plan to use such a board.
915 If you say Y here and want DDC/I2C support you must first say Y to
916 "I2C support" and "I2C bit-banging support" in the character devices
919 If you say M here then "I2C support" and "I2C bit-banging support"
920 can be build either as modules or built-in.
922 To compile this driver as a module, choose M here: the
923 module will be called intelfb.
925 For more information, please read <file:Documentation/fb/intelfb.txt>
927 config FB_INTEL_DEBUG
928 bool "Intel driver Debug Messages"
931 Say Y here if you want the Intel driver to output all sorts
932 of debugging information to provide to the maintainer when
933 something goes wrong.
936 bool "DDC/I2C for Intel framebuffer support"
941 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
944 tristate "Matrox acceleration"
946 select FB_CFB_FILLRECT
947 select FB_CFB_COPYAREA
948 select FB_CFB_IMAGEBLIT
949 select FB_TILEBLITTING
950 select FB_MACMODES if PPC_PMAC
952 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
953 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
954 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
955 Matrox G400, G450 or G550 card in your box.
957 To compile this driver as a module, choose M here: the
958 module will be called matroxfb.
960 You can pass several parameters to the driver at boot time or at
961 module load time. The parameters look like "video=matrox:XXX", and
962 are described in <file:Documentation/fb/matroxfb.txt>.
964 config FB_MATROX_MILLENIUM
965 bool "Millennium I/II support"
968 Say Y here if you have a Matrox Millennium or Matrox Millennium II
969 video card. If you select "Advanced lowlevel driver options" below,
970 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
971 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
972 also use font widths different from 8.
974 config FB_MATROX_MYSTIQUE
975 bool "Mystique support"
978 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
979 video card. If you select "Advanced lowlevel driver options" below,
980 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
981 packed pixel and 32 bpp packed pixel. You can also use font widths
985 bool "G100/G200/G400/G450/G550 support"
988 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
989 video card. If you select "Advanced lowlevel driver options", you
990 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
991 pixel and 32 bpp packed pixel. You can also use font widths
994 If you need support for G400 secondary head, you must first say Y to
995 "I2C support" in the character devices section, and then to
996 "Matrox I2C support" and "G400 second head support" here in the
997 framebuffer section. G450/G550 secondary head and digital output
998 are supported without additional modules.
1000 The driver starts in monitor mode. You must use the matroxset tool
1001 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1002 swap primary and secondary head outputs, or to change output mode.
1003 Secondary head driver always start in 640x480 resolution and you
1004 must use fbset to change it.
1006 Do not forget that second head supports only 16 and 32 bpp
1007 packed pixels, so it is a good idea to compile them into the kernel
1008 too. You can use only some font widths, as the driver uses generic
1009 painting procedures (the secondary head does not use acceleration
1012 G450/G550 hardware can display TV picture only from secondary CRTC,
1013 and it performs no scaling, so picture must have 525 or 625 lines.
1015 config FB_MATROX_I2C
1016 tristate "Matrox I2C support"
1017 depends on FB_MATROX
1020 This drivers creates I2C buses which are needed for accessing the
1021 DDC (I2C) bus present on all Matroxes, an I2C bus which
1022 interconnects Matrox optional devices, like MGA-TVO on G200 and
1023 G400, and the secondary head DDC bus, present on G400 only.
1025 You can say Y or M here if you want to experiment with monitor
1026 detection code. You must say Y or M here if you want to use either
1027 second head of G400 or MGA-TVO on G200 or G400.
1029 If you compile it as module, it will create a module named
1032 config FB_MATROX_MAVEN
1033 tristate "G400 second head support"
1034 depends on FB_MATROX_G && FB_MATROX_I2C
1036 WARNING !!! This support does not work with G450 !!!
1038 Say Y or M here if you want to use a secondary head (meaning two
1039 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1040 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1041 secondary head output is blanked while you are in X. With XFree
1042 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1043 the fbdev driver on first head and the fbdev driver on second head.
1045 If you compile it as module, two modules are created,
1046 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1047 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1048 also load i2c-matroxfb to get it to run.
1050 The driver starts in monitor mode and you must use the matroxset
1052 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1053 PAL or NTSC or to swap primary and secondary head outputs.
1054 Secondary head driver also always start in 640x480 resolution, you
1055 must use fbset to change it.
1057 Also do not forget that second head supports only 16 and 32 bpp
1058 packed pixels, so it is a good idea to compile them into the kernel
1059 too. You can use only some font widths, as the driver uses generic
1060 painting procedures (the secondary head does not use acceleration
1063 config FB_MATROX_MULTIHEAD
1064 bool "Multihead support"
1065 depends on FB_MATROX
1067 Say Y here if you have more than one (supported) Matrox device in
1068 your computer and you want to use all of them for different monitors
1069 ("multihead"). If you have only one device, you should say N because
1070 the driver compiled with Y is larger and a bit slower, especially on
1073 If you said M to "Matrox unified accelerated driver" and N here, you
1074 will still be able to use several Matrox devices simultaneously:
1075 insert several instances of the module matroxfb into the kernel
1076 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1077 for the different Matrox devices. This method is slightly faster but
1078 uses 40 KB of kernel memory per Matrox card.
1080 There is no need for enabling 'Matrox multihead support' if you have
1081 only one Matrox card in the box.
1084 tristate "ATI Radeon display support"
1085 depends on FB && PCI
1086 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1087 select FB_MODE_HELPERS
1088 select FB_CFB_FILLRECT
1089 select FB_CFB_COPYAREA
1090 select FB_CFB_IMAGEBLIT
1091 select FB_MACMODES if PPC_OF
1093 Choose this option if you want to use an ATI Radeon graphics card as
1094 a framebuffer device. There are both PCI and AGP versions. You
1095 don't need to choose this to run the Radeon in plain VGA mode.
1097 If you say Y here and want DDC/I2C support you must first say Y to
1098 "I2C support" and "I2C bit-banging support" in the character devices
1101 If you say M here then "I2C support" and "I2C bit-banging support"
1102 can be build either as modules or built-in.
1104 There is a product page at
1105 http://apps.ati.com/ATIcompare/
1107 config FB_RADEON_I2C
1108 bool "DDC/I2C for ATI Radeon support"
1109 depends on FB_RADEON
1113 Say Y here if you want DDC/I2C support for your Radeon board.
1115 config FB_RADEON_BACKLIGHT
1116 bool "Support for backlight control"
1117 depends on FB_RADEON
1120 Say Y here if you want to control the backlight of your display.
1122 config FB_RADEON_DEBUG
1123 bool "Lots of debug output from Radeon driver"
1124 depends on FB_RADEON
1127 Say Y here if you want the Radeon driver to output all sorts
1128 of debugging information to provide to the maintainer when
1129 something goes wrong.
1132 tristate "ATI Rage128 display support"
1133 depends on FB && PCI
1134 select FB_CFB_FILLRECT
1135 select FB_CFB_COPYAREA
1136 select FB_CFB_IMAGEBLIT
1137 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1138 select FB_MACMODES if PPC_PMAC
1140 This driver supports graphics boards with the ATI Rage128 chips.
1141 Say Y if you have such a graphics board and read
1142 <file:Documentation/fb/aty128fb.txt>.
1144 To compile this driver as a module, choose M here: the
1145 module will be called aty128fb.
1147 config FB_ATY128_BACKLIGHT
1148 bool "Support for backlight control"
1149 depends on FB_ATY128
1152 Say Y here if you want to control the backlight of your display.
1155 tristate "ATI Mach64 display support" if PCI || ATARI
1156 depends on FB && !SPARC32
1157 select FB_CFB_FILLRECT
1158 select FB_CFB_COPYAREA
1159 select FB_CFB_IMAGEBLIT
1160 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1161 select FB_MACMODES if PPC
1163 This driver supports graphics boards with the ATI Mach64 chips.
1164 Say Y if you have such a graphics board.
1166 To compile this driver as a module, choose M here: the
1167 module will be called atyfb.
1170 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1171 depends on PCI && FB_ATY
1172 default y if SPARC64 && FB_PCI
1174 Say Y here to support use of ATI's 64-bit Rage boards (or other
1175 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1176 framebuffer device. The ATI product support page for these boards
1177 is at <http://support.ati.com/products/pc/mach64/>.
1179 config FB_ATY_GENERIC_LCD
1180 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1181 depends on FB_ATY_CT
1183 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1184 Rage XC, or Rage XL chipset.
1187 bool "Mach64 GX support" if PCI
1191 Say Y here to support use of the ATI Mach64 Graphics Expression
1192 board (or other boards based on the Mach64 GX chipset) as a
1193 framebuffer device. The ATI product support page for these boards
1195 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1197 config FB_ATY_BACKLIGHT
1198 bool "Support for backlight control"
1202 Say Y here if you want to control the backlight of your display.
1205 tristate "S3 Trio/Virge support"
1206 depends on FB && PCI
1207 select FB_CFB_FILLRECT
1208 select FB_CFB_COPYAREA
1209 select FB_CFB_IMAGEBLIT
1210 select FB_TILEBLITTING
1213 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1215 Driver for graphics boards with S3 Trio / S3 Virge chip.
1218 tristate "S3 Savage support"
1219 depends on FB && PCI && EXPERIMENTAL
1220 select FB_MODE_HELPERS
1221 select FB_CFB_FILLRECT
1222 select FB_CFB_COPYAREA
1223 select FB_CFB_IMAGEBLIT
1226 This driver supports notebooks and computers with S3 Savage PCI/AGP
1229 Say Y if you have such a graphics card.
1231 To compile this driver as a module, choose M here; the module
1232 will be called savagefb.
1234 config FB_SAVAGE_I2C
1235 bool "Enable DDC2 Support"
1236 depends on FB_SAVAGE
1239 This enables I2C support for S3 Savage Chipsets. This is used
1240 only for getting EDID information from the attached display
1241 allowing for robust video mode handling and switching.
1243 Because fbdev-2.6 requires that drivers must be able to
1244 independently validate video mode parameters, you should say Y
1247 config FB_SAVAGE_ACCEL
1248 bool "Enable Console Acceleration"
1249 depends on FB_SAVAGE
1252 This option will compile in console acceleration support. If
1253 the resulting framebuffer console has bothersome glitches, then
1257 tristate "SiS/XGI display support"
1258 depends on FB && PCI
1259 select FB_CFB_FILLRECT
1260 select FB_CFB_COPYAREA
1261 select FB_CFB_IMAGEBLIT
1263 This is the frame buffer device driver for the SiS 300, 315, 330
1264 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1265 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1267 To compile this driver as a module, choose M here; the module
1268 will be called sisfb.
1271 bool "SiS 300 series support"
1274 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1277 bool "SiS 315/330/340 series and XGI support"
1280 Say Y here to support use of the SiS 315, 330 and 340 series
1281 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1282 as XGI V3XT, V5, V8 and Z7.
1285 tristate "NeoMagic display support"
1286 depends on FB && PCI
1287 select FB_MODE_HELPERS
1288 select FB_CFB_FILLRECT
1289 select FB_CFB_COPYAREA
1290 select FB_CFB_IMAGEBLIT
1293 This driver supports notebooks with NeoMagic PCI chips.
1294 Say Y if you have such a graphics card.
1296 To compile this driver as a module, choose M here: the
1297 module will be called neofb.
1300 tristate "IMG Kyro support"
1301 depends on FB && PCI
1302 select FB_CFB_FILLRECT
1303 select FB_CFB_COPYAREA
1304 select FB_CFB_IMAGEBLIT
1306 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1309 To compile this driver as a module, choose M here: the
1310 module will be called kyrofb.
1313 tristate "3Dfx Banshee/Voodoo3 display support"
1314 depends on FB && PCI
1315 select FB_CFB_IMAGEBLIT
1316 select FB_CFB_FILLRECT
1317 select FB_CFB_COPYAREA
1319 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1320 chips. Say Y if you have such a graphics board.
1322 To compile this driver as a module, choose M here: the
1323 module will be called tdfxfb.
1325 config FB_3DFX_ACCEL
1326 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1327 depends on FB_3DFX && EXPERIMENTAL
1329 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1330 with acceleration functions.
1334 tristate "3Dfx Voodoo Graphics (sst1) support"
1335 depends on FB && PCI
1336 select FB_CFB_FILLRECT
1337 select FB_CFB_COPYAREA
1338 select FB_CFB_IMAGEBLIT
1340 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1341 Voodoo2 (cvg) based graphics card.
1343 To compile this driver as a module, choose M here: the
1344 module will be called sstfb.
1346 WARNING: Do not use any application that uses the 3D engine
1347 (namely glide) while using this driver.
1348 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1349 options and other important info support.
1352 tristate "Cyberblade/i1 support"
1353 depends on FB && PCI && X86_32 && !64BIT
1354 select FB_CFB_IMAGEBLIT
1357 This driver is supposed to support the Trident Cyberblade/i1
1358 graphics core integrated in the VIA VT8601A North Bridge,
1359 also known as VIA Apollo PLE133.
1362 - Developed, tested and working on EPIA 5000 and EPIA 800.
1363 - Does work reliable on all systems with CRT/LCD connected to
1365 - Should work on systems that do use the internal LCD port, but
1366 this is absolutely not tested.
1368 Character imageblit, copyarea and rectangle fill are hw accelerated,
1369 ypan scrolling is used by default.
1371 Please do read <file:Documentation/fb/cyblafb/*>.
1373 To compile this driver as a module, choose M here: the
1374 module will be called cyblafb.
1377 tristate "Trident support"
1378 depends on FB && PCI
1379 select FB_CFB_FILLRECT
1380 select FB_CFB_COPYAREA
1381 select FB_CFB_IMAGEBLIT
1383 This driver is supposed to support graphics boards with the
1384 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1385 but also on some motherboards. For more information, read
1386 <file:Documentation/fb/tridentfb.txt>
1388 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1391 Say Y if you have such a graphics board.
1394 To compile this driver as a module, choose M here: the
1395 module will be called tridentfb.
1397 config FB_TRIDENT_ACCEL
1398 bool "Trident Acceleration functions (EXPERIMENTAL)"
1399 depends on FB_TRIDENT && EXPERIMENTAL
1401 This will compile the Trident frame buffer device with
1402 acceleration functions.
1405 tristate "Permedia3 support"
1406 depends on FB && PCI && BROKEN
1408 This is the frame buffer device driver for the 3DLabs Permedia3
1409 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1410 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1411 and maybe other boards.
1414 bool "Au1100 LCD Driver"
1415 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1418 bool "Au1200 LCD Driver"
1419 depends on (FB = y) && MIPS && SOC_AU1200
1420 select FB_CFB_FILLRECT
1421 select FB_CFB_COPYAREA
1422 select FB_CFB_IMAGEBLIT
1424 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1425 various panels and CRTs by passing in kernel cmd line option
1426 au1200fb:panel=<name>.
1428 source "drivers/video/geode/Kconfig"
1431 bool "Creator/Creator3D/Elite3D support"
1432 depends on FB_SBUS && SPARC64
1433 select FB_CFB_COPYAREA
1434 select FB_CFB_IMAGEBLIT
1436 This is the frame buffer device driver for the Creator, Creator3D,
1437 and Elite3D graphics boards.
1440 bool "TCX (SS4/SS5 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 TCX 24/8bit frame
1450 bool "CGfourteen (SX) 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 CGfourteen frame
1457 buffer on Desktop SPARCsystems with the SX graphics option.
1460 bool "P9100 (Sparcbook 3 only) support"
1462 select FB_CFB_FILLRECT
1463 select FB_CFB_COPYAREA
1464 select FB_CFB_IMAGEBLIT
1466 This is the frame buffer device driver for the P9100 card
1467 supported on Sparcbook 3 machines.
1470 bool "Leo (ZX) support"
1472 select FB_CFB_FILLRECT
1473 select FB_CFB_COPYAREA
1474 select FB_CFB_IMAGEBLIT
1476 This is the frame buffer device driver for the SBUS-based Sun ZX
1477 (leo) frame buffer cards.
1480 bool "Sun XVR-500 3DLABS Wildcat support"
1481 depends on FB && PCI && SPARC64
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1486 This is the framebuffer device for the Sun XVR-500 and similar
1487 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1488 only works on sparc64 systems where the system firwmare has
1489 mostly initialized the card already. It is treated as a
1490 completely dumb framebuffer device.
1493 bool "Sun XVR-2500 3DLABS Wildcat support"
1494 depends on FB && PCI && SPARC64
1495 select FB_CFB_FILLRECT
1496 select FB_CFB_COPYAREA
1497 select FB_CFB_IMAGEBLIT
1499 This is the framebuffer device for the Sun XVR-2500 and similar
1500 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1501 only works on sparc64 systems where the system firwmare has
1502 mostly initialized the card already. It is treated as a
1503 completely dumb framebuffer device.
1506 bool "PCI framebuffers"
1507 depends on (FB = y) && PCI && SPARC
1510 bool "IGA 168x display support"
1511 depends on SPARC32 && FB_PCI
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1516 This is the framebuffer device for the INTERGRAPHICS 1680 and
1517 successor frame buffer cards.
1520 tristate "HD64461 Frame Buffer support"
1521 depends on FB && HD64461
1522 select FB_CFB_FILLRECT
1523 select FB_CFB_COPYAREA
1524 select FB_CFB_IMAGEBLIT
1526 This is the frame buffer device driver for the Hitachi HD64461 LCD
1530 bool "PMAG-AA TURBOchannel framebuffer support"
1531 depends on (FB = y) && TC
1532 select FB_CFB_FILLRECT
1533 select FB_CFB_COPYAREA
1534 select FB_CFB_IMAGEBLIT
1536 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1537 used mainly in the MIPS-based DECstation series.
1540 tristate "PMAG-BA TURBOchannel framebuffer support"
1542 select FB_CFB_FILLRECT
1543 select FB_CFB_COPYAREA
1544 select FB_CFB_IMAGEBLIT
1546 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1547 used mainly in the MIPS-based DECstation series.
1550 tristate "PMAGB-B TURBOchannel framebuffer support"
1552 select FB_CFB_FILLRECT
1553 select FB_CFB_COPYAREA
1554 select FB_CFB_IMAGEBLIT
1556 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1557 in the MIPS-based DECstation series. The card is currently only
1558 supported in 1280x1024x8 mode.
1561 bool "Maxine (Personal DECstation) onboard framebuffer support"
1562 depends on (FB = y) && MACH_DECSTATION
1563 select FB_CFB_FILLRECT
1564 select FB_CFB_COPYAREA
1565 select FB_CFB_IMAGEBLIT
1567 Support for the onboard framebuffer (1024x768x8) in the Personal
1568 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1572 bool "TMPTX3912/PR31700 frame buffer support"
1573 depends on (FB = y) && NINO
1574 select FB_CFB_FILLRECT
1575 select FB_CFB_COPYAREA
1576 select FB_CFB_IMAGEBLIT
1578 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1579 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1581 Say Y here to enable kernel support for the on-board framebuffer.
1584 bool "G364 frame buffer support"
1585 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1586 select FB_CFB_FILLRECT
1587 select FB_CFB_COPYAREA
1588 select FB_CFB_IMAGEBLIT
1590 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1591 Olivetti M700-10 systems.
1594 bool "Motorola 68328 native frame buffer support"
1595 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1596 select FB_CFB_FILLRECT
1597 select FB_CFB_COPYAREA
1598 select FB_CFB_IMAGEBLIT
1600 Say Y here if you want to support the built-in frame buffer of
1601 the Motorola 68328 CPU family.
1604 tristate "PXA LCD framebuffer support"
1605 depends on FB && ARCH_PXA
1606 select FB_CFB_FILLRECT
1607 select FB_CFB_COPYAREA
1608 select FB_CFB_IMAGEBLIT
1610 Frame buffer driver for the built-in LCD controller in the Intel
1613 This driver is also available as a module ( = code which can be
1614 inserted and removed from the running kernel whenever you want). The
1615 module will be called pxafb. If you want to compile it as a module,
1616 say M here and read <file:Documentation/kbuild/modules.txt>.
1620 config FB_PXA_PARAMETERS
1621 bool "PXA LCD command line parameters"
1625 Enable the use of kernel command line or module parameters
1626 to configure the physical properties of the LCD panel when
1627 using the PXA LCD driver.
1629 This option allows you to override the panel parameters
1630 supplied by the platform in order to support multiple
1631 different models of flatpanel. If you will only be using a
1632 single model of flatpanel then you can safely leave this
1635 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1638 tristate "2700G LCD framebuffer support"
1639 depends on FB && ARCH_PXA
1640 select FB_CFB_FILLRECT
1641 select FB_CFB_COPYAREA
1642 select FB_CFB_IMAGEBLIT
1644 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1648 bool "Enable debugging info via debugfs"
1649 depends on FB_MBX && DEBUG_FS
1652 Enable this if you want debugging information using the debug
1653 filesystem (debugfs)
1658 tristate "W100 frame buffer support"
1659 depends on FB && PXA_SHARPSL
1660 select FB_CFB_FILLRECT
1661 select FB_CFB_COPYAREA
1662 select FB_CFB_IMAGEBLIT
1664 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1666 This driver is also available as a module ( = code which can be
1667 inserted and removed from the running kernel whenever you want). The
1668 module will be called w100fb. If you want to compile it as a module,
1669 say M here and read <file:Documentation/kbuild/modules.txt>.
1674 tristate "S3C2410 LCD framebuffer support"
1675 depends on FB && ARCH_S3C2410
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1680 Frame buffer driver for the built-in LCD controller in the Samsung
1683 This driver is also available as a module ( = code which can be
1684 inserted and removed from the running kernel whenever you want). The
1685 module will be called s3c2410fb. If you want to compile it as a module,
1686 say M here and read <file:Documentation/kbuild/modules.txt>.
1689 config FB_S3C2410_DEBUG
1690 bool "S3C2410 lcd debug messages"
1691 depends on FB_S3C2410
1693 Turn on debugging messages. Note that you can set/unset at run time
1697 tristate "Silicon Motion SM501 framebuffer support"
1698 depends on FB && MFD_SM501
1699 select FB_CFB_FILLRECT
1700 select FB_CFB_COPYAREA
1701 select FB_CFB_IMAGEBLIT
1703 Frame buffer driver for the CRT and LCD controllers in the Silicon
1706 This driver is also available as a module ( = code which can be
1707 inserted and removed from the running kernel whenever you want). The
1708 module will be called sm501fb. If you want to compile it as a module,
1709 say M here and read <file:Documentation/modules.txt>.
1714 config FB_PNX4008_DUM
1715 tristate "Display Update Module support on Philips PNX4008 board"
1716 depends on FB && ARCH_PNX4008
1718 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1720 config FB_PNX4008_DUM_RGB
1721 tristate "RGB Framebuffer support on Philips PNX4008 board"
1722 depends on FB_PNX4008_DUM
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 Say Y here to enable support for PNX4008 RGB Framebuffer
1729 config FB_IBM_GXT4500
1730 tristate "Framebuffer support for IBM GXT4500P adaptor"
1732 select FB_CFB_FILLRECT
1733 select FB_CFB_COPYAREA
1734 select FB_CFB_IMAGEBLIT
1736 Say Y here to enable support for the IBM GXT4500P display
1737 adaptor, found on some IBM System P (pSeries) machines.
1740 bool "PS3 GPU framebuffer driver"
1741 depends on (FB = y) && PS3_PS3AV
1742 select FB_CFB_FILLRECT
1743 select FB_CFB_COPYAREA
1744 select FB_CFB_IMAGEBLIT
1746 Include support for the virtual frame buffer in the PS3 platform.
1748 config FB_PS3_DEFAULT_SIZE_M
1749 int "PS3 default frame buffer size (in MiB)"
1753 This is the default size (in MiB) of the virtual frame buffer in
1755 The default value can be overridden on the kernel command line
1756 using the "ps3fb" option (e.g. "ps3fb=9M");
1759 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1761 select FB_SYS_FILLRECT
1762 select FB_SYS_COPYAREA
1763 select FB_SYS_IMAGEBLIT
1766 This is a `virtual' frame buffer device. It operates on a chunk of
1767 unswappable kernel memory instead of on the memory of a graphics
1768 board. This means you cannot see any output sent to this frame
1769 buffer device, while it does consume precious memory. The main use
1770 of this frame buffer device is testing and debugging the frame
1771 buffer subsystem. Do NOT enable it for normal systems! To protect
1772 the innocent, it has to be enabled explicitly at boot time using the
1773 kernel option `video=vfb:'.
1775 To compile this driver as a module, choose M here: the
1776 module will be called vfb. In order to load it, you must use
1777 the vfb_enable=1 option.
1782 source "drivers/video/console/Kconfig"
1785 if FB || SGI_NEWPORT_CONSOLE
1786 source "drivers/video/logo/Kconfig"