5 menu "Graphics support"
8 source "drivers/video/backlight/Kconfig"
12 tristate "Support for frame buffer devices"
14 The frame buffer device provides an abstraction for the graphics
15 hardware. It represents the frame buffer of some video hardware and
16 allows application software to access the graphics hardware through
17 a well-defined interface, so the software doesn't need to know
18 anything about the low-level (hardware register) stuff.
20 Frame buffer devices work identically across the different
21 architectures supported by Linux and make the implementation of
22 application programs easier and more portable; at this point, an X
23 server exists which uses the frame buffer device exclusively.
24 On several non-X86 architectures, the frame buffer device is the
25 only way to use the graphics hardware.
27 The device is accessed through special device nodes, usually located
28 in the /dev directory, i.e. /dev/fb*.
30 You need an utility program called fbset to make full use of frame
31 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
32 and the Framebuffer-HOWTO at
33 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
36 Say Y here and to the driver for your graphics board below if you
37 are compiling a kernel for a non-x86 architecture.
39 If you are compiling for the x86 architecture, you can say Y if you
40 want to play with it, but it is not essential. Please note that
41 running graphical applications that directly touch the hardware
42 (e.g. an accelerated X server) and that are not frame buffer
43 device-aware may cause unexpected results. If unsure, say N.
46 bool "Enable firmware EDID"
50 This enables access to the EDID transferred from the firmware.
51 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
52 transfers do not work for your driver and if you are using
53 nvidiafb, i810fb or savagefb.
55 In general, choosing Y for this option is safe. If you
56 experience extremely long delays while booting before you get
57 something on your display, try setting this to N. Matrox cards in
58 combination with certain motherboards and monitors are known to
59 suffer from this problem.
68 config FB_CFB_FILLRECT
73 Include the cfb_fillrect function for generic software rectangle
74 filling. This is used by drivers that don't provide their own
75 (accelerated) version.
77 config FB_CFB_COPYAREA
82 Include the cfb_copyarea function for generic software area copying.
83 This is used by drivers that don't provide their own (accelerated)
86 config FB_CFB_IMAGEBLIT
91 Include the cfb_imageblit function for generic software image
92 blitting. This is used by drivers that don't provide their own
93 (accelerated) version.
100 Common utility functions useful to fbdev drivers of VGA-based
111 select BACKLIGHT_LCD_SUPPORT
112 select BACKLIGHT_CLASS_DEVICE
115 config FB_MODE_HELPERS
116 bool "Enable Video Mode Handling Helpers"
120 This enables functions for handling video modes using the
121 Generalized Timing Formula and the EDID parser. A few drivers rely
122 on this feature such as the radeonfb, rivafb, and the i810fb. If
123 your driver does not take advantage of this feature, choosing Y will
124 just increase the kernel size by about 5K.
126 config FB_TILEBLITTING
127 bool "Enable Tile Blitting Support"
131 This enables tile blitting. Tile blitting is a drawing technique
132 where the screen is divided into rectangular sections (tiles), whereas
133 the standard blitting divides the screen into pixels. Because the
134 default drawing element is a tile, drawing functions will be passed
135 parameters in terms of number of tiles instead of number of pixels.
136 For example, to draw a single character, instead of using bitmaps,
137 an index to an array of bitmaps will be used. To clear or move a
138 rectangular section of a screen, the rectangle will be described in
139 terms of number of tiles in the x- and y-axis.
141 This is particularly important to one driver, matroxfb. If
144 comment "Frambuffer hardware drivers"
148 tristate "Cirrus Logic support"
149 depends on FB && (ZORRO || PCI)
150 select FB_CFB_FILLRECT
151 select FB_CFB_COPYAREA
152 select FB_CFB_IMAGEBLIT
154 This enables support for Cirrus Logic GD542x/543x based boards on
155 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
157 If you have a PCI-based system, this enables support for these
158 chips: GD-543x, GD-544x, GD-5480.
160 Please read the file <file:Documentation/fb/cirrusfb.txt>.
162 Say N unless you have such a graphics board or plan to get one
163 before you next recompile the kernel.
166 tristate "Permedia2 support"
167 depends on FB && ((AMIGA && BROKEN) || PCI)
168 select FB_CFB_FILLRECT
169 select FB_CFB_COPYAREA
170 select FB_CFB_IMAGEBLIT
172 This is the frame buffer device driver for the Permedia2 AGP frame
173 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
175 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
177 config FB_PM2_FIFO_DISCONNECT
178 bool "enable FIFO disconnect feature"
179 depends on FB_PM2 && PCI
181 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
184 tristate "ARM PrimeCell PL110 support"
185 depends on FB && ARM && ARM_AMBA
186 select FB_CFB_FILLRECT
187 select FB_CFB_COPYAREA
188 select FB_CFB_IMAGEBLIT
190 This framebuffer device driver is for the ARM PrimeCell PL110
191 Colour LCD controller. ARM PrimeCells provide the building
192 blocks for System on a Chip devices.
194 If you want to compile this as a module (=code which can be
195 inserted into and removed from the running kernel), say M
196 here and read <file:Documentation/modules.txt>. The module
197 will be called amba-clcd.
201 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
203 default FB_ARMCLCD_SHARP_LQ035Q7DB02
205 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
206 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
208 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
209 color QVGA, HRTFT panel. The LogicPD device includes
210 an integrated HRTFT controller IC.
211 The native resolution is 240x320.
213 config FB_ARMCLCD_SHARP_LQ057Q3DC02
214 bool "LogicPD LCD 5.7\" QVGA"
216 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
217 color QVGA, TFT panel. The LogicPD device includes an
218 The native resolution is 320x240.
220 config FB_ARMCLCD_SHARP_LQ64D343
221 bool "LogicPD LCD 6.4\" VGA"
223 This is an implementation of the Sharp LQ64D343, a 6.4"
224 color VGA, TFT panel. The LogicPD device includes an
225 The native resolution is 640x480.
227 config FB_ARMCLCD_SHARP_LQ10D368
228 bool "LogicPD LCD 10.4\" VGA"
230 This is an implementation of the Sharp LQ10D368, a 10.4"
231 color VGA, TFT panel. The LogicPD device includes an
232 The native resolution is 640x480.
235 config FB_ARMCLCD_SHARP_LQ121S1DG41
236 bool "LogicPD LCD 12.1\" SVGA"
238 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
239 color SVGA, TFT panel. The LogicPD device includes an
240 The native resolution is 800x600.
242 This panel requires a clock rate may be an integer fraction
243 of the base LCDCLK frequency. The driver will select the
244 highest frequency available that is lower than the maximum
245 allowed. The panel may flicker if the clock rate is
246 slower than the recommended minimum.
248 config FB_ARMCLCD_AUO_A070VW01_WIDE
249 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
251 This is an implementation of the AU Optronics, a 7.0"
252 WIDE Color. The native resolution is 234x480.
254 config FB_ARMCLCD_HITACHI
255 bool "Hitachi Wide Screen 800x480"
257 This is an implementation of the Hitachi 800x480.
263 bool "Acorn VIDC support"
264 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
265 select FB_CFB_FILLRECT
266 select FB_CFB_COPYAREA
267 select FB_CFB_IMAGEBLIT
269 This is the frame buffer device driver for the Acorn VIDC graphics
270 hardware found in Acorn RISC PCs and other ARM-based machines. If
274 bool "CLPS711X LCD support"
275 depends on (FB = y) && ARM && ARCH_CLPS711X
276 select FB_CFB_FILLRECT
277 select FB_CFB_COPYAREA
278 select FB_CFB_IMAGEBLIT
280 Say Y to enable the Framebuffer driver for the CLPS7111 and
284 bool "SA-1100 LCD support"
285 depends on (FB = y) && ARM && ARCH_SA1100
286 select FB_CFB_FILLRECT
287 select FB_CFB_COPYAREA
288 select FB_CFB_IMAGEBLIT
290 This is a framebuffer device for the SA-1100 LCD Controller.
291 See <http://www.linux-fbdev.org/> for information on framebuffer
294 If you plan to use the LCD display with your SA-1100 system, say
298 tristate "Motorola i.MX LCD support"
299 depends on FB && ARM && ARCH_IMX
300 select FB_CFB_FILLRECT
301 select FB_CFB_COPYAREA
302 select FB_CFB_IMAGEBLIT
305 tristate "CyberPro 2000/2010/5000 support"
306 depends on FB && PCI && (BROKEN || !SPARC64)
307 select FB_CFB_FILLRECT
308 select FB_CFB_COPYAREA
309 select FB_CFB_IMAGEBLIT
311 This enables support for the Integraphics CyberPro 20x0 and 5000
312 VGA chips used in the Rebel.com Netwinder and other machines.
313 Say Y if you have a NetWinder or a graphics card containing this
314 device, otherwise say N.
318 depends on (FB = y) && APOLLO
320 select FB_CFB_FILLRECT
321 select FB_CFB_IMAGEBLIT
325 depends on (FB = y) && Q40
327 select FB_CFB_FILLRECT
328 select FB_CFB_COPYAREA
329 select FB_CFB_IMAGEBLIT
332 tristate "Amiga native chipset support"
333 depends on FB && AMIGA
335 This is the frame buffer device driver for the builtin graphics
336 chipset found in Amigas.
338 To compile this driver as a module, choose M here: the
339 module will be called amifb.
342 bool "Amiga OCS chipset support"
345 This enables support for the original Agnus and Denise video chips,
346 found in the Amiga 1000 and most A500's and A2000's. If you intend
347 to run Linux on any of these systems, say Y; otherwise say N.
350 bool "Amiga ECS chipset support"
353 This enables support for the Enhanced Chip Set, found in later
354 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
355 you intend to run Linux on any of these systems, say Y; otherwise
359 bool "Amiga AGA chipset support"
362 This enables support for the Advanced Graphics Architecture (also
363 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
364 and CD32. If you intend to run Linux on any of these systems, say Y;
368 bool "Amiga FrameMaster II/Rainbow II support"
369 depends on (FB = y) && ZORRO
370 select FB_CFB_FILLRECT
371 select FB_CFB_COPYAREA
372 select FB_CFB_IMAGEBLIT
374 This is the frame buffer device driver for the Amiga FrameMaster
375 card from BSC (exhibited 1992 but not shipped as a CBM product).
378 tristate "Arc Monochrome LCD board support"
380 select FB_CFB_FILLRECT
381 select FB_CFB_COPYAREA
382 select FB_CFB_IMAGEBLIT
384 This enables support for the Arc Monochrome LCD board. The board
385 is based on the KS-108 lcd controller and is typically a matrix
386 of 2*n chips. This driver was tested with a 128x64 panel. This
387 driver supports it for use with x86 SBCs through a 16 bit GPIO
388 interface (8 bit data, 8 bit control). If you anticipate using
389 this driver, say Y or M; otherwise say N. You must specify the
390 GPIO IO address to be used for setting control and data.
393 bool "Atari native chipset support"
394 depends on (FB = y) && ATARI && BROKEN
396 This is the frame buffer device driver for the builtin graphics
397 chipset found in Ataris.
400 bool "Open Firmware frame buffer device support"
401 depends on (FB = y) && (PPC64 || PPC_OF)
402 select FB_CFB_FILLRECT
403 select FB_CFB_COPYAREA
404 select FB_CFB_IMAGEBLIT
407 Say Y if you want support with Open Firmware for your graphics
411 bool "Apple \"control\" display support"
412 depends on (FB = y) && PPC_PMAC && PPC32
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
418 This driver supports a frame buffer for the graphics adapter in the
419 Power Macintosh 7300 and others.
422 bool "Apple \"platinum\" display support"
423 depends on (FB = y) && PPC_PMAC && PPC32
424 select FB_CFB_FILLRECT
425 select FB_CFB_COPYAREA
426 select FB_CFB_IMAGEBLIT
429 This driver supports a frame buffer for the "platinum" graphics
430 adapter in some Power Macintoshes.
433 bool "Apple \"valkyrie\" display support"
434 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
435 select FB_CFB_FILLRECT
436 select FB_CFB_COPYAREA
437 select FB_CFB_IMAGEBLIT
440 This driver supports a frame buffer for the "valkyrie" graphics
441 adapter in some Power Macintoshes.
444 bool "Chips 65550 display support"
445 depends on (FB = y) && PPC32
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
450 This is the frame buffer device driver for the Chips & Technologies
451 65550 graphics chip in PowerBooks.
454 bool "Asiliant (Chips) 69000 display support"
455 depends on (FB = y) && PCI
456 select FB_CFB_FILLRECT
457 select FB_CFB_COPYAREA
458 select FB_CFB_IMAGEBLIT
460 This is the frame buffer device driver for the Asiliant 69030 chipset
463 bool "IMS Twin Turbo display support"
464 depends on (FB = y) && PCI
465 select FB_CFB_IMAGEBLIT
466 select FB_MACMODES if PPC
468 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
469 many Macintosh and compatible computers.
472 tristate "VGA 16-color graphics support"
473 depends on FB && (X86 || PPC)
474 select FB_CFB_FILLRECT
475 select FB_CFB_COPYAREA
476 select FB_CFB_IMAGEBLIT
478 This is the frame buffer device driver for VGA 16 color graphic
479 cards. Say Y if you have such a card.
481 To compile this driver as a module, choose M here: the
482 module will be called vga16fb.
485 tristate "HP STI frame buffer device support"
486 depends on FB && PARISC
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
492 STI refers to the HP "Standard Text Interface" which is a set of
493 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
494 Enabling this option will implement the linux framebuffer device
495 using calls to the STI BIOS routines for initialisation.
497 If you enable this option, you will get a planar framebuffer device
498 /dev/fb which will work on the most common HP graphic cards of the
499 NGLE family, including the artist chips (in the 7xx and Bxxx series),
500 HCRX, HCRX24, CRX, CRX24 and VisEG series.
502 It is safe to enable this option, so you should probably say "Y".
505 bool "Generic Macintosh display support"
506 depends on (FB = y) && MAC
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
512 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
515 depends on (FB = y) && HP300
516 select FB_CFB_FILLRECT
517 select FB_CFB_IMAGEBLIT
521 tristate "TGA framebuffer support"
522 depends on FB && ALPHA
523 select FB_CFB_FILLRECT
524 select FB_CFB_COPYAREA
525 select FB_CFB_IMAGEBLIT
528 This is the frame buffer device driver for generic TGA graphic
529 cards. Say Y if you have one of those.
532 bool "VESA VGA graphics support"
533 depends on (FB = y) && X86
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
539 This is the frame buffer device driver for generic VESA 2.0
540 compliant graphic cards. The older VESA 1.2 cards are not supported.
541 You will get a boot time penguin logo at no additional cost. Please
542 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
545 bool "Intel-based Macintosh Framebuffer Support"
546 depends on (FB = y) && X86 && EFI
547 select FB_CFB_FILLRECT
548 select FB_CFB_COPYAREA
549 select FB_CFB_IMAGEBLIT
551 This is the frame buffer device driver for the Intel-based Macintosh
554 tristate "Hercules mono graphics support"
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 Say Y here if you have a Hercules mono graphics card.
562 To compile this driver as a module, choose M here: the
563 module will be called hgafb.
565 As this card technology is 15 years old, most people will answer N
569 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
570 depends on FB_HGA && EXPERIMENTAL
572 This will compile the Hercules mono graphics with
573 acceleration functions.
576 tristate "SGI Visual Workstation framebuffer support"
577 depends on FB && X86_VISWS
578 select FB_CFB_FILLRECT
579 select FB_CFB_COPYAREA
580 select FB_CFB_IMAGEBLIT
582 SGI Visual Workstation support for framebuffer graphics.
585 bool "SGI Graphics Backend frame buffer support"
586 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
587 select FB_CFB_FILLRECT
588 select FB_CFB_COPYAREA
589 select FB_CFB_IMAGEBLIT
591 This is the frame buffer device driver for SGI Graphics Backend.
592 This chip is used in SGI O2 and Visual Workstation 320/540.
595 int "Video memory size in MB"
599 This is the amount of memory reserved for the framebuffer,
600 which can be any value between 1MB and 8MB.
603 bool "SBUS and UPA framebuffers"
604 depends on (FB = y) && SPARC
606 Say Y if you want support for SBUS or UPA based frame buffer device.
610 depends on (FB = y) && (SPARC && FB_SBUS)
611 select FB_CFB_FILLRECT
612 select FB_CFB_COPYAREA
613 select FB_CFB_IMAGEBLIT
615 This is the frame buffer device driver for the BWtwo frame buffer.
618 bool "CGthree support"
619 depends on (FB = y) && (SPARC && FB_SBUS)
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
624 This is the frame buffer device driver for the CGthree frame buffer.
627 bool "CGsix (GX,TurboGX) support"
628 depends on (FB = y) && (SPARC && FB_SBUS)
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
632 This is the frame buffer device driver for the CGsix (GX, TurboGX)
636 tristate "NEC PowerVR 2 display support"
637 depends on FB && SH_DREAMCAST
638 select FB_CFB_FILLRECT
639 select FB_CFB_COPYAREA
640 select FB_CFB_IMAGEBLIT
642 Say Y here if you have a PowerVR 2 card in your box. If you plan to
643 run linux on your Dreamcast, you will have to say Y here.
644 This driver may or may not work on other PowerVR 2 cards, but is
645 totally untested. Use at your own risk. If unsure, say N.
647 To compile this driver as a module, choose M here: the
648 module will be called pvr2fb.
650 You can pass several parameters to the driver at boot time or at
651 module load time. The parameters look like "video=pvr2:XXX", where
652 the meaning of XXX can be found at the end of the main source file
653 (<file:drivers/video/pvr2fb.c>). Please see the file
654 <file:Documentation/fb/pvr2fb.txt>.
657 bool "Epson 1355 framebuffer support"
658 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
663 Build in support for the SED1355 Epson Research Embedded RAMDAC
664 LCD/CRT Controller (since redesignated as the S1D13505) as a
665 framebuffer. Product specs at
666 <http://www.erd.epson.com/vdc/html/products.htm>.
669 tristate "Epson S1D13XXX framebuffer support"
671 select FB_CFB_FILLRECT
672 select FB_CFB_COPYAREA
673 select FB_CFB_IMAGEBLIT
675 Support for S1D13XXX framebuffer device family (currently only
676 working with S1D13806). Product specs at
677 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
680 tristate "nVidia Framebuffer Support"
682 select I2C_ALGOBIT if FB_NVIDIA_I2C
683 select I2C if FB_NVIDIA_I2C
684 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
685 select FB_MODE_HELPERS
686 select FB_CFB_FILLRECT
687 select FB_CFB_COPYAREA
688 select FB_CFB_IMAGEBLIT
691 This driver supports graphics boards with the nVidia chips, TNT
692 and newer. For very old chipsets, such as the RIVA128, then use
694 Say Y if you have such a graphics board.
696 To compile this driver as a module, choose M here: the
697 module will be called nvidiafb.
700 bool "Enable DDC Support"
703 This enables I2C support for nVidia Chipsets. This is used
704 only for getting EDID information from the attached display
705 allowing for robust video mode handling and switching.
707 Because fbdev-2.6 requires that drivers must be able to
708 independently validate video mode parameters, you should say Y
711 config FB_NVIDIA_BACKLIGHT
712 bool "Support for backlight control"
716 Say Y here if you want to control the backlight of your display.
719 tristate "nVidia Riva support"
721 select FB_DDC if FB_RIVA_I2C
722 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
723 select FB_MODE_HELPERS
724 select FB_CFB_FILLRECT
725 select FB_CFB_COPYAREA
726 select FB_CFB_IMAGEBLIT
729 This driver supports graphics boards with the nVidia Riva/Geforce
731 Say Y if you have such a graphics board.
733 To compile this driver as a module, choose M here: the
734 module will be called rivafb.
737 bool "Enable DDC Support"
740 This enables I2C support for nVidia Chipsets. This is used
741 only for getting EDID information from the attached display
742 allowing for robust video mode handling and switching.
744 Because fbdev-2.6 requires that drivers must be able to
745 independently validate video mode parameters, you should say Y
749 bool "Lots of debug output from Riva(nVidia) driver"
753 Say Y here if you want the Riva driver to output all sorts
754 of debugging information to provide to the maintainer when
755 something goes wrong.
757 config FB_RIVA_BACKLIGHT
758 bool "Support for backlight control"
762 Say Y here if you want to control the backlight of your display.
765 tristate "Intel 810/815 support (EXPERIMENTAL)"
766 depends on FB && EXPERIMENTAL && PCI && X86_32
769 select FB_MODE_HELPERS
770 select FB_CFB_FILLRECT
771 select FB_CFB_COPYAREA
772 select FB_CFB_IMAGEBLIT
774 This driver supports the on-board graphics built in to the Intel 810
775 and 815 chipsets. Say Y if you have and plan to use such a board.
777 To compile this driver as a module, choose M here: the
778 module will be called i810fb.
780 For more information, please read
781 <file:Documentation/fb/intel810.txt>
784 bool "use VESA Generalized Timing Formula"
787 If you say Y, then the VESA standard, Generalized Timing Formula
788 or GTF, will be used to calculate the required video timing values
789 per video mode. Since the GTF allows nondiscrete timings
790 (nondiscrete being a range of values as opposed to discrete being a
791 set of values), you'll be able to use any combination of horizontal
792 and vertical resolutions, and vertical refresh rates without having
793 to specify your own timing parameters. This is especially useful
794 to maximize the performance of an aging display, or if you just
795 have a display with nonstandard dimensions. A VESA compliant
796 monitor is recommended, but can still work with non-compliant ones.
797 If you need or want this, then select this option. The timings may
798 not be compliant with Intel's recommended values. Use at your own
801 If you say N, the driver will revert to discrete video timings
802 using a set recommended by Intel in their documentation.
807 bool "Enable DDC Support"
808 depends on FB_I810 && FB_I810_GTF
813 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
814 depends on FB && EXPERIMENTAL && PCI && X86
817 select I2C_ALGOBIT if FB_INTEL_I2C
818 select I2C if FB_INTEL_I2C
819 select FB_MODE_HELPERS
820 select FB_CFB_FILLRECT
821 select FB_CFB_COPYAREA
822 select FB_CFB_IMAGEBLIT
824 This driver supports the on-board graphics built in to the Intel
825 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
826 Say Y if you have and plan to use such a board.
828 If you say Y here and want DDC/I2C support you must first say Y to
829 "I2C support" and "I2C bit-banging support" in the character devices
832 If you say M here then "I2C support" and "I2C bit-banging support"
833 can be build either as modules or built-in.
835 To compile this driver as a module, choose M here: the
836 module will be called intelfb.
838 For more information, please read <file:Documentation/fb/intelfb.txt>
840 config FB_INTEL_DEBUG
841 bool "Intel driver Debug Messages"
844 Say Y here if you want the Intel driver to output all sorts
845 of debugging information to provide to the maintainer when
846 something goes wrong.
849 bool "DDC/I2C for Intel framebuffer support"
853 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
856 tristate "Matrox acceleration"
858 select FB_CFB_FILLRECT
859 select FB_CFB_COPYAREA
860 select FB_CFB_IMAGEBLIT
861 select FB_TILEBLITTING
862 select FB_MACMODES if PPC_PMAC
864 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
865 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
866 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
867 Matrox G400, G450 or G550 card in your box.
869 To compile this driver as a module, choose M here: the
870 module will be called matroxfb.
872 You can pass several parameters to the driver at boot time or at
873 module load time. The parameters look like "video=matrox:XXX", and
874 are described in <file:Documentation/fb/matroxfb.txt>.
876 config FB_MATROX_MILLENIUM
877 bool "Millennium I/II support"
880 Say Y here if you have a Matrox Millennium or Matrox Millennium II
881 video card. If you select "Advanced lowlevel driver options" below,
882 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
883 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
884 also use font widths different from 8.
886 config FB_MATROX_MYSTIQUE
887 bool "Mystique support"
890 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
891 video card. If you select "Advanced lowlevel driver options" below,
892 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
893 packed pixel and 32 bpp packed pixel. You can also use font widths
897 bool "G100/G200/G400/G450/G550 support"
900 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
901 video card. If you select "Advanced lowlevel driver options", you
902 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
903 pixel and 32 bpp packed pixel. You can also use font widths
906 If you need support for G400 secondary head, you must first say Y to
907 "I2C support" in the character devices section, and then to
908 "Matrox I2C support" and "G400 second head support" here in the
909 framebuffer section. G450/G550 secondary head and digital output
910 are supported without additional modules.
912 The driver starts in monitor mode. You must use the matroxset tool
913 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
914 swap primary and secondary head outputs, or to change output mode.
915 Secondary head driver always start in 640x480 resolution and you
916 must use fbset to change it.
918 Do not forget that second head supports only 16 and 32 bpp
919 packed pixels, so it is a good idea to compile them into the kernel
920 too. You can use only some font widths, as the driver uses generic
921 painting procedures (the secondary head does not use acceleration
924 G450/G550 hardware can display TV picture only from secondary CRTC,
925 and it performs no scaling, so picture must have 525 or 625 lines.
928 tristate "Matrox I2C support"
929 depends on FB_MATROX && I2C
932 This drivers creates I2C buses which are needed for accessing the
933 DDC (I2C) bus present on all Matroxes, an I2C bus which
934 interconnects Matrox optional devices, like MGA-TVO on G200 and
935 G400, and the secondary head DDC bus, present on G400 only.
937 You can say Y or M here if you want to experiment with monitor
938 detection code. You must say Y or M here if you want to use either
939 second head of G400 or MGA-TVO on G200 or G400.
941 If you compile it as module, it will create a module named
944 config FB_MATROX_MAVEN
945 tristate "G400 second head support"
946 depends on FB_MATROX_G && FB_MATROX_I2C
948 WARNING !!! This support does not work with G450 !!!
950 Say Y or M here if you want to use a secondary head (meaning two
951 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
952 head is not compatible with accelerated XFree 3.3.x SVGA servers -
953 secondary head output is blanked while you are in X. With XFree
954 3.9.17 preview you can use both heads if you use SVGA over fbdev or
955 the fbdev driver on first head and the fbdev driver on second head.
957 If you compile it as module, two modules are created,
958 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
959 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
960 also load i2c-matroxfb to get it to run.
962 The driver starts in monitor mode and you must use the matroxset
964 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
965 PAL or NTSC or to swap primary and secondary head outputs.
966 Secondary head driver also always start in 640x480 resolution, you
967 must use fbset to change it.
969 Also do not forget that second head supports only 16 and 32 bpp
970 packed pixels, so it is a good idea to compile them into the kernel
971 too. You can use only some font widths, as the driver uses generic
972 painting procedures (the secondary head does not use acceleration
975 config FB_MATROX_MULTIHEAD
976 bool "Multihead support"
979 Say Y here if you have more than one (supported) Matrox device in
980 your computer and you want to use all of them for different monitors
981 ("multihead"). If you have only one device, you should say N because
982 the driver compiled with Y is larger and a bit slower, especially on
985 If you said M to "Matrox unified accelerated driver" and N here, you
986 will still be able to use several Matrox devices simultaneously:
987 insert several instances of the module matroxfb into the kernel
988 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
989 for the different Matrox devices. This method is slightly faster but
990 uses 40 KB of kernel memory per Matrox card.
992 There is no need for enabling 'Matrox multihead support' if you have
993 only one Matrox card in the box.
996 tristate "ATI Radeon display support"
998 select FB_DDC if FB_RADEON_I2C
999 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1000 select FB_MODE_HELPERS
1001 select FB_CFB_FILLRECT
1002 select FB_CFB_COPYAREA
1003 select FB_CFB_IMAGEBLIT
1004 select FB_MACMODES if PPC_OF
1006 Choose this option if you want to use an ATI Radeon graphics card as
1007 a framebuffer device. There are both PCI and AGP versions. You
1008 don't need to choose this to run the Radeon in plain VGA mode.
1010 If you say Y here and want DDC/I2C support you must first say Y to
1011 "I2C support" and "I2C bit-banging support" in the character devices
1014 If you say M here then "I2C support" and "I2C bit-banging support"
1015 can be build either as modules or built-in.
1017 There is a product page at
1018 http://apps.ati.com/ATIcompare/
1020 config FB_RADEON_I2C
1021 bool "DDC/I2C for ATI Radeon support"
1022 depends on FB_RADEON
1025 Say Y here if you want DDC/I2C support for your Radeon board.
1027 config FB_RADEON_BACKLIGHT
1028 bool "Support for backlight control"
1029 depends on FB_RADEON
1032 Say Y here if you want to control the backlight of your display.
1034 config FB_RADEON_DEBUG
1035 bool "Lots of debug output from Radeon driver"
1036 depends on FB_RADEON
1039 Say Y here if you want the Radeon driver to output all sorts
1040 of debugging information to provide to the maintainer when
1041 something goes wrong.
1044 tristate "ATI Rage128 display support"
1045 depends on FB && PCI
1046 select FB_CFB_FILLRECT
1047 select FB_CFB_COPYAREA
1048 select FB_CFB_IMAGEBLIT
1049 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1050 select FB_MACMODES if PPC_PMAC
1052 This driver supports graphics boards with the ATI Rage128 chips.
1053 Say Y if you have such a graphics board and read
1054 <file:Documentation/fb/aty128fb.txt>.
1056 To compile this driver as a module, choose M here: the
1057 module will be called aty128fb.
1059 config FB_ATY128_BACKLIGHT
1060 bool "Support for backlight control"
1061 depends on FB_ATY128
1064 Say Y here if you want to control the backlight of your display.
1067 tristate "ATI Mach64 display support" if PCI || ATARI
1068 depends on FB && !SPARC32
1069 select FB_CFB_FILLRECT
1070 select FB_CFB_COPYAREA
1071 select FB_CFB_IMAGEBLIT
1072 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1073 select FB_MACMODES if PPC
1075 This driver supports graphics boards with the ATI Mach64 chips.
1076 Say Y if you have such a graphics board.
1078 To compile this driver as a module, choose M here: the
1079 module will be called atyfb.
1082 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1083 depends on PCI && FB_ATY
1084 default y if SPARC64 && FB_PCI
1086 Say Y here to support use of ATI's 64-bit Rage boards (or other
1087 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1088 framebuffer device. The ATI product support page for these boards
1089 is at <http://support.ati.com/products/pc/mach64/>.
1091 config FB_ATY_GENERIC_LCD
1092 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1093 depends on FB_ATY_CT
1095 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1096 Rage XC, or Rage XL chipset.
1099 bool "Mach64 GX support" if PCI
1103 Say Y here to support use of the ATI Mach64 Graphics Expression
1104 board (or other boards based on the Mach64 GX chipset) as a
1105 framebuffer device. The ATI product support page for these boards
1107 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1109 config FB_ATY_BACKLIGHT
1110 bool "Support for backlight control"
1114 Say Y here if you want to control the backlight of your display.
1117 tristate "S3 Trio/Virge support"
1118 depends on FB && PCI
1119 select FB_CFB_FILLRECT
1120 select FB_CFB_COPYAREA
1121 select FB_CFB_IMAGEBLIT
1122 select FB_TILEBLITTING
1125 Driver for graphics boards with S3 Trio / S3 Virge chip.
1128 tristate "S3 Savage support"
1129 depends on FB && PCI && EXPERIMENTAL
1130 select FB_DDC if FB_SAVAGE_I2C
1131 select FB_MODE_HELPERS
1132 select FB_CFB_FILLRECT
1133 select FB_CFB_COPYAREA
1134 select FB_CFB_IMAGEBLIT
1136 This driver supports notebooks and computers with S3 Savage PCI/AGP
1139 Say Y if you have such a graphics card.
1141 To compile this driver as a module, choose M here; the module
1142 will be called savagefb.
1144 config FB_SAVAGE_I2C
1145 bool "Enable DDC2 Support"
1146 depends on FB_SAVAGE
1148 This enables I2C support for S3 Savage Chipsets. This is used
1149 only for getting EDID information from the attached display
1150 allowing for robust video mode handling and switching.
1152 Because fbdev-2.6 requires that drivers must be able to
1153 independently validate video mode parameters, you should say Y
1156 config FB_SAVAGE_ACCEL
1157 bool "Enable Console Acceleration"
1158 depends on FB_SAVAGE
1161 This option will compile in console acceleration support. If
1162 the resulting framebuffer console has bothersome glitches, then
1166 tristate "SiS/XGI display support"
1167 depends on FB && PCI
1168 select FB_CFB_FILLRECT
1169 select FB_CFB_COPYAREA
1170 select FB_CFB_IMAGEBLIT
1172 This is the frame buffer device driver for the SiS 300, 315, 330
1173 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1174 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1176 To compile this driver as a module, choose M here; the module
1177 will be called sisfb.
1180 bool "SiS 300 series support"
1183 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1186 bool "SiS 315/330/340 series and XGI support"
1189 Say Y here to support use of the SiS 315, 330 and 340 series
1190 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1191 as XGI V3XT, V5, V8 and Z7.
1194 tristate "NeoMagic display support"
1195 depends on FB && PCI
1196 select FB_MODE_HELPERS
1197 select FB_CFB_FILLRECT
1198 select FB_CFB_COPYAREA
1199 select FB_CFB_IMAGEBLIT
1201 This driver supports notebooks with NeoMagic PCI chips.
1202 Say Y if you have such a graphics card.
1204 To compile this driver as a module, choose M here: the
1205 module will be called neofb.
1208 tristate "IMG Kyro support"
1209 depends on FB && PCI
1210 select FB_CFB_FILLRECT
1211 select FB_CFB_COPYAREA
1212 select FB_CFB_IMAGEBLIT
1214 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1217 To compile this driver as a module, choose M here: the
1218 module will be called kyrofb.
1221 tristate "3Dfx Banshee/Voodoo3 display support"
1222 depends on FB && PCI
1223 select FB_CFB_IMAGEBLIT
1224 select FB_CFB_FILLRECT
1225 select FB_CFB_COPYAREA
1227 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1228 chips. Say Y if you have such a graphics board.
1230 To compile this driver as a module, choose M here: the
1231 module will be called tdfxfb.
1233 config FB_3DFX_ACCEL
1234 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1235 depends on FB_3DFX && EXPERIMENTAL
1237 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1238 with acceleration functions.
1242 tristate "3Dfx Voodoo Graphics (sst1) support"
1243 depends on FB && PCI
1244 select FB_CFB_FILLRECT
1245 select FB_CFB_COPYAREA
1246 select FB_CFB_IMAGEBLIT
1248 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1249 Voodoo2 (cvg) based graphics card.
1251 To compile this driver as a module, choose M here: the
1252 module will be called sstfb.
1254 WARNING: Do not use any application that uses the 3D engine
1255 (namely glide) while using this driver.
1256 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1257 options and other important info support.
1260 tristate "Cyberblade/i1 support"
1261 depends on FB && PCI && X86_32 && !64BIT
1262 select FB_CFB_IMAGEBLIT
1265 This driver is supposed to support the Trident Cyberblade/i1
1266 graphics core integrated in the VIA VT8601A North Bridge,
1267 also known as VIA Apollo PLE133.
1270 - Developed, tested and working on EPIA 5000 and EPIA 800.
1271 - Does work reliable on all systems with CRT/LCD connected to
1273 - Should work on systems that do use the internal LCD port, but
1274 this is absolutely not tested.
1276 Character imageblit, copyarea and rectangle fill are hw accelerated,
1277 ypan scrolling is used by default.
1279 Please do read <file:Documentation/fb/cyblafb/*>.
1281 To compile this driver as a module, choose M here: the
1282 module will be called cyblafb.
1285 tristate "Trident support"
1286 depends on FB && PCI
1287 select FB_CFB_FILLRECT
1288 select FB_CFB_COPYAREA
1289 select FB_CFB_IMAGEBLIT
1291 This driver is supposed to support graphics boards with the
1292 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1293 but also on some motherboards. For more information, read
1294 <file:Documentation/fb/tridentfb.txt>
1296 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1299 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 tridentfb.
1305 config FB_TRIDENT_ACCEL
1306 bool "Trident Acceleration functions (EXPERIMENTAL)"
1307 depends on FB_TRIDENT && EXPERIMENTAL
1309 This will compile the Trident frame buffer device with
1310 acceleration functions.
1313 tristate "Permedia3 support"
1314 depends on FB && PCI && BROKEN
1316 This is the frame buffer device driver for the 3DLabs Permedia3
1317 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1318 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1319 and maybe other boards.
1322 bool "Au1100 LCD Driver"
1323 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1326 bool "Au1200 LCD Driver"
1327 depends on FB && MIPS && SOC_AU1200
1328 select FB_CFB_FILLRECT
1329 select FB_CFB_COPYAREA
1330 select FB_CFB_IMAGEBLIT
1332 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1333 various panels and CRTs by passing in kernel cmd line option
1334 au1200fb:panel=<name>.
1336 source "drivers/video/geode/Kconfig"
1339 bool "Creator/Creator3D/Elite3D support"
1340 depends on FB_SBUS && SPARC64
1341 select FB_CFB_COPYAREA
1342 select FB_CFB_IMAGEBLIT
1344 This is the frame buffer device driver for the Creator, Creator3D,
1345 and Elite3D graphics boards.
1348 bool "TCX (SS4/SS5 only) support"
1350 select FB_CFB_FILLRECT
1351 select FB_CFB_COPYAREA
1352 select FB_CFB_IMAGEBLIT
1354 This is the frame buffer device driver for the TCX 24/8bit frame
1358 bool "CGfourteen (SX) support"
1360 select FB_CFB_FILLRECT
1361 select FB_CFB_COPYAREA
1362 select FB_CFB_IMAGEBLIT
1364 This is the frame buffer device driver for the CGfourteen frame
1365 buffer on Desktop SPARCsystems with the SX graphics option.
1368 bool "P9100 (Sparcbook 3 only) support"
1370 select FB_CFB_FILLRECT
1371 select FB_CFB_COPYAREA
1372 select FB_CFB_IMAGEBLIT
1374 This is the frame buffer device driver for the P9100 card
1375 supported on Sparcbook 3 machines.
1378 bool "Leo (ZX) support"
1380 select FB_CFB_FILLRECT
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1384 This is the frame buffer device driver for the SBUS-based Sun ZX
1385 (leo) frame buffer cards.
1388 bool "PCI framebuffers"
1389 depends on (FB = y) && PCI && SPARC
1392 bool "IGA 168x display support"
1393 depends on SPARC32 && FB_PCI
1394 select FB_CFB_FILLRECT
1395 select FB_CFB_COPYAREA
1396 select FB_CFB_IMAGEBLIT
1398 This is the framebuffer device for the INTERGRAPHICS 1680 and
1399 successor frame buffer cards.
1402 tristate "HD64461 Frame Buffer support"
1403 depends on FB && HD64461
1404 select FB_CFB_FILLRECT
1405 select FB_CFB_COPYAREA
1406 select FB_CFB_IMAGEBLIT
1408 This is the frame buffer device driver for the Hitachi HD64461 LCD
1412 bool "PMAG-AA TURBOchannel framebuffer support"
1413 depends on (FB = y) && TC
1414 select FB_CFB_FILLRECT
1415 select FB_CFB_COPYAREA
1416 select FB_CFB_IMAGEBLIT
1418 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1419 used mainly in the MIPS-based DECstation series.
1422 tristate "PMAG-BA TURBOchannel framebuffer support"
1424 select FB_CFB_FILLRECT
1425 select FB_CFB_COPYAREA
1426 select FB_CFB_IMAGEBLIT
1428 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1429 used mainly in the MIPS-based DECstation series.
1432 tristate "PMAGB-B TURBOchannel framebuffer support"
1434 select FB_CFB_FILLRECT
1435 select FB_CFB_COPYAREA
1436 select FB_CFB_IMAGEBLIT
1438 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1439 in the MIPS-based DECstation series. The card is currently only
1440 supported in 1280x1024x8 mode.
1443 bool "Maxine (Personal DECstation) onboard framebuffer support"
1444 depends on (FB = y) && MACH_DECSTATION
1445 select FB_CFB_FILLRECT
1446 select FB_CFB_COPYAREA
1447 select FB_CFB_IMAGEBLIT
1449 Support for the onboard framebuffer (1024x768x8) in the Personal
1450 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1454 bool "TMPTX3912/PR31700 frame buffer support"
1455 depends on (FB = y) && NINO
1456 select FB_CFB_FILLRECT
1457 select FB_CFB_COPYAREA
1458 select FB_CFB_IMAGEBLIT
1460 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1461 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1463 Say Y here to enable kernel support for the on-board framebuffer.
1466 bool "G364 frame buffer support"
1467 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1468 select FB_CFB_FILLRECT
1469 select FB_CFB_COPYAREA
1470 select FB_CFB_IMAGEBLIT
1472 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1473 Olivetti M700-10 systems.
1476 bool "Motorola 68328 native frame buffer support"
1477 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1478 select FB_CFB_FILLRECT
1479 select FB_CFB_COPYAREA
1480 select FB_CFB_IMAGEBLIT
1482 Say Y here if you want to support the built-in frame buffer of
1483 the Motorola 68328 CPU family.
1486 tristate "PXA LCD framebuffer support"
1487 depends on FB && ARCH_PXA
1488 select FB_CFB_FILLRECT
1489 select FB_CFB_COPYAREA
1490 select FB_CFB_IMAGEBLIT
1492 Frame buffer driver for the built-in LCD controller in the Intel
1495 This driver is also available as a module ( = code which can be
1496 inserted and removed from the running kernel whenever you want). The
1497 module will be called pxafb. If you want to compile it as a module,
1498 say M here and read <file:Documentation/modules.txt>.
1502 config FB_PXA_PARAMETERS
1503 bool "PXA LCD command line parameters"
1507 Enable the use of kernel command line or module parameters
1508 to configure the physical properties of the LCD panel when
1509 using the PXA LCD driver.
1511 This option allows you to override the panel parameters
1512 supplied by the platform in order to support multiple
1513 different models of flatpanel. If you will only be using a
1514 single model of flatpanel then you can safely leave this
1517 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1520 tristate "2700G LCD framebuffer support"
1521 depends on FB && ARCH_PXA
1522 select FB_CFB_FILLRECT
1523 select FB_CFB_COPYAREA
1524 select FB_CFB_IMAGEBLIT
1526 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1530 bool "Enable debugging info via debugfs"
1531 depends on FB_MBX && DEBUG_FS
1534 Enable this if you want debugging information using the debug
1535 filesystem (debugfs)
1540 tristate "W100 frame buffer support"
1541 depends on FB && PXA_SHARPSL
1542 select FB_CFB_FILLRECT
1543 select FB_CFB_COPYAREA
1544 select FB_CFB_IMAGEBLIT
1546 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1548 This driver is also available as a module ( = code which can be
1549 inserted and removed from the running kernel whenever you want). The
1550 module will be called w100fb. If you want to compile it as a module,
1551 say M here and read <file:Documentation/modules.txt>.
1556 tristate "S3C2410 LCD framebuffer support"
1557 depends on FB && ARCH_S3C2410
1558 select FB_CFB_FILLRECT
1559 select FB_CFB_COPYAREA
1560 select FB_CFB_IMAGEBLIT
1562 Frame buffer driver for the built-in LCD controller in the Samsung
1565 This driver is also available as a module ( = code which can be
1566 inserted and removed from the running kernel whenever you want). The
1567 module will be called s3c2410fb. If you want to compile it as a module,
1568 say M here and read <file:Documentation/modules.txt>.
1571 config FB_S3C2410_DEBUG
1572 bool "S3C2410 lcd debug messages"
1573 depends on FB_S3C2410
1575 Turn on debugging messages. Note that you can set/unset at run time
1578 config FB_PNX4008_DUM
1579 tristate "Display Update Module support on Philips PNX4008 board"
1580 depends on FB && ARCH_PNX4008
1582 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1584 config FB_PNX4008_DUM_RGB
1585 tristate "RGB Framebuffer support on Philips PNX4008 board"
1586 depends on FB_PNX4008_DUM
1587 select FB_CFB_FILLRECT
1588 select FB_CFB_COPYAREA
1589 select FB_CFB_IMAGEBLIT
1591 Say Y here to enable support for PNX4008 RGB Framebuffer
1593 config FB_IBM_GXT4500
1594 tristate "Framebuffer support for IBM GXT4500P adaptor"
1596 select FB_CFB_FILLRECT
1597 select FB_CFB_COPYAREA
1598 select FB_CFB_IMAGEBLIT
1600 Say Y here to enable support for the IBM GXT4500P display
1601 adaptor, found on some IBM System P (pSeries) machines.
1604 bool "PS3 GPU framebuffer driver"
1605 depends on FB && PPC_PS3
1607 select FB_CFB_FILLRECT
1608 select FB_CFB_COPYAREA
1609 select FB_CFB_IMAGEBLIT
1611 Include support for the virtual frame buffer in the PS3 platform.
1613 config FB_PS3_DEFAULT_SIZE_M
1614 int "PS3 default frame buffer size (in MiB)"
1618 This is the default size (in MiB) of the virtual frame buffer in
1620 The default value can be overridden on the kernel command line
1621 using the "ps3fb" option (e.g. "ps3fb=9M");
1624 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1626 select FB_CFB_FILLRECT
1627 select FB_CFB_COPYAREA
1628 select FB_CFB_IMAGEBLIT
1630 This is a `virtual' frame buffer device. It operates on a chunk of
1631 unswappable kernel memory instead of on the memory of a graphics
1632 board. This means you cannot see any output sent to this frame
1633 buffer device, while it does consume precious memory. The main use
1634 of this frame buffer device is testing and debugging the frame
1635 buffer subsystem. Do NOT enable it for normal systems! To protect
1636 the innocent, it has to be enabled explicitly at boot time using the
1637 kernel option `video=vfb:'.
1639 To compile this driver as a module, choose M here: the
1640 module will be called vfb. In order to load it, you must use
1641 the vfb_enable=1 option.
1646 source "drivers/video/console/Kconfig"
1649 if FB || SGI_NEWPORT_CONSOLE
1650 source "drivers/video/logo/Kconfig"