5 menu "Graphics support"
8 bool "Enable firmware EDID"
11 This enables access to the EDID transferred from the firmware.
12 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
13 transfers do not work for your driver and if you are using
14 nvidiafb, i810fb or savagefb.
16 In general, choosing Y for this option is safe. If you
17 experience extremely long delays while booting before you get
18 something on your display, try setting this to N. Matrox cards in
19 combination with certain motherboards and monitors are known to
20 suffer from this problem.
23 tristate "Support for frame buffer devices"
25 The frame buffer device provides an abstraction for the graphics
26 hardware. It represents the frame buffer of some video hardware and
27 allows application software to access the graphics hardware through
28 a well-defined interface, so the software doesn't need to know
29 anything about the low-level (hardware register) stuff.
31 Frame buffer devices work identically across the different
32 architectures supported by Linux and make the implementation of
33 application programs easier and more portable; at this point, an X
34 server exists which uses the frame buffer device exclusively.
35 On several non-X86 architectures, the frame buffer device is the
36 only way to use the graphics hardware.
38 The device is accessed through special device nodes, usually located
39 in the /dev directory, i.e. /dev/fb*.
41 You need an utility program called fbset to make full use of frame
42 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
43 and the Framebuffer-HOWTO at
44 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
47 Say Y here and to the driver for your graphics board below if you
48 are compiling a kernel for a non-x86 architecture.
50 If you are compiling for the x86 architecture, you can say Y if you
51 want to play with it, but it is not essential. Please note that
52 running graphical applications that directly touch the hardware
53 (e.g. an accelerated X server) and that are not frame buffer
54 device-aware may cause unexpected results. If unsure, say N.
58 depends on FB && I2C && I2C_ALGOBIT
61 config FB_CFB_FILLRECT
66 Include the cfb_fillrect function for generic software rectangle
67 filling. This is used by drivers that don't provide their own
68 (accelerated) version.
70 config FB_CFB_COPYAREA
75 Include the cfb_copyarea function for generic software area copying.
76 This is used by drivers that don't provide their own (accelerated)
79 config FB_CFB_IMAGEBLIT
84 Include the cfb_imageblit function for generic software image
85 blitting. This is used by drivers that don't provide their own
86 (accelerated) version.
93 Common utility functions useful to fbdev drivers of VGA-based
104 select BACKLIGHT_LCD_SUPPORT
105 select BACKLIGHT_CLASS_DEVICE
108 config FB_MODE_HELPERS
109 bool "Enable Video Mode Handling Helpers"
113 This enables functions for handling video modes using the
114 Generalized Timing Formula and the EDID parser. A few drivers rely
115 on this feature such as the radeonfb, rivafb, and the i810fb. If
116 your driver does not take advantage of this feature, choosing Y will
117 just increase the kernel size by about 5K.
119 config FB_TILEBLITTING
120 bool "Enable Tile Blitting Support"
124 This enables tile blitting. Tile blitting is a drawing technique
125 where the screen is divided into rectangular sections (tiles), whereas
126 the standard blitting divides the screen into pixels. Because the
127 default drawing element is a tile, drawing functions will be passed
128 parameters in terms of number of tiles instead of number of pixels.
129 For example, to draw a single character, instead of using bitmaps,
130 an index to an array of bitmaps will be used. To clear or move a
131 rectangular section of a screen, the rectangle will be described in
132 terms of number of tiles in the x- and y-axis.
134 This is particularly important to one driver, matroxfb. If
138 tristate "Cirrus Logic support"
139 depends on FB && (ZORRO || PCI)
140 select FB_CFB_FILLRECT
141 select FB_CFB_COPYAREA
142 select FB_CFB_IMAGEBLIT
144 This enables support for Cirrus Logic GD542x/543x based boards on
145 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
147 If you have a PCI-based system, this enables support for these
148 chips: GD-543x, GD-544x, GD-5480.
150 Please read the file <file:Documentation/fb/cirrusfb.txt>.
152 Say N unless you have such a graphics board or plan to get one
153 before you next recompile the kernel.
156 tristate "Permedia2 support"
157 depends on FB && ((AMIGA && BROKEN) || PCI)
158 select FB_CFB_FILLRECT
159 select FB_CFB_COPYAREA
160 select FB_CFB_IMAGEBLIT
162 This is the frame buffer device driver for the Permedia2 AGP frame
163 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
165 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
167 config FB_PM2_FIFO_DISCONNECT
168 bool "enable FIFO disconnect feature"
169 depends on FB_PM2 && PCI
171 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
174 tristate "ARM PrimeCell PL110 support"
175 depends on FB && ARM && ARM_AMBA
176 select FB_CFB_FILLRECT
177 select FB_CFB_COPYAREA
178 select FB_CFB_IMAGEBLIT
180 This framebuffer device driver is for the ARM PrimeCell PL110
181 Colour LCD controller. ARM PrimeCells provide the building
182 blocks for System on a Chip devices.
184 If you want to compile this as a module (=code which can be
185 inserted into and removed from the running kernel), say M
186 here and read <file:Documentation/modules.txt>. The module
187 will be called amba-clcd.
191 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
193 default FB_ARMCLCD_SHARP_LQ035Q7DB02
195 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
196 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
198 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
199 color QVGA, HRTFT panel. The LogicPD device includes
200 an integrated HRTFT controller IC.
201 The native resolution is 240x320.
203 config FB_ARMCLCD_SHARP_LQ057Q3DC02
204 bool "LogicPD LCD 5.7\" QVGA"
206 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
207 color QVGA, TFT panel. The LogicPD device includes an
208 The native resolution is 320x240.
210 config FB_ARMCLCD_SHARP_LQ64D343
211 bool "LogicPD LCD 6.4\" VGA"
213 This is an implementation of the Sharp LQ64D343, a 6.4"
214 color VGA, TFT panel. The LogicPD device includes an
215 The native resolution is 640x480.
217 config FB_ARMCLCD_SHARP_LQ10D368
218 bool "LogicPD LCD 10.4\" VGA"
220 This is an implementation of the Sharp LQ10D368, a 10.4"
221 color VGA, TFT panel. The LogicPD device includes an
222 The native resolution is 640x480.
225 config FB_ARMCLCD_SHARP_LQ121S1DG41
226 bool "LogicPD LCD 12.1\" SVGA"
228 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
229 color SVGA, TFT panel. The LogicPD device includes an
230 The native resolution is 800x600.
232 This panel requires a clock rate may be an integer fraction
233 of the base LCDCLK frequency. The driver will select the
234 highest frequency available that is lower than the maximum
235 allowed. The panel may flicker if the clock rate is
236 slower than the recommended minimum.
238 config FB_ARMCLCD_AUO_A070VW01_WIDE
239 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
241 This is an implementation of the AU Optronics, a 7.0"
242 WIDE Color. The native resolution is 234x480.
244 config FB_ARMCLCD_HITACHI
245 bool "Hitachi Wide Screen 800x480"
247 This is an implementation of the Hitachi 800x480.
253 bool "Acorn VIDC support"
254 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
255 select FB_CFB_FILLRECT
256 select FB_CFB_COPYAREA
257 select FB_CFB_IMAGEBLIT
259 This is the frame buffer device driver for the Acorn VIDC graphics
260 hardware found in Acorn RISC PCs and other ARM-based machines. If
264 bool "CLPS711X LCD support"
265 depends on (FB = y) && ARM && ARCH_CLPS711X
266 select FB_CFB_FILLRECT
267 select FB_CFB_COPYAREA
268 select FB_CFB_IMAGEBLIT
270 Say Y to enable the Framebuffer driver for the CLPS7111 and
274 bool "SA-1100 LCD support"
275 depends on (FB = y) && ARM && ARCH_SA1100
276 select FB_CFB_FILLRECT
277 select FB_CFB_COPYAREA
278 select FB_CFB_IMAGEBLIT
280 This is a framebuffer device for the SA-1100 LCD Controller.
281 See <http://www.linux-fbdev.org/> for information on framebuffer
284 If you plan to use the LCD display with your SA-1100 system, say
288 tristate "Motorola i.MX LCD support"
289 depends on FB && ARM && ARCH_IMX
290 select FB_CFB_FILLRECT
291 select FB_CFB_COPYAREA
292 select FB_CFB_IMAGEBLIT
295 tristate "CyberPro 2000/2010/5000 support"
296 depends on FB && PCI && (BROKEN || !SPARC64)
297 select FB_CFB_FILLRECT
298 select FB_CFB_COPYAREA
299 select FB_CFB_IMAGEBLIT
301 This enables support for the Integraphics CyberPro 20x0 and 5000
302 VGA chips used in the Rebel.com Netwinder and other machines.
303 Say Y if you have a NetWinder or a graphics card containing this
304 device, otherwise say N.
308 depends on (FB = y) && APOLLO
310 select FB_CFB_FILLRECT
311 select FB_CFB_IMAGEBLIT
315 depends on (FB = y) && Q40
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
322 tristate "Amiga native chipset support"
323 depends on FB && AMIGA
325 This is the frame buffer device driver for the builtin graphics
326 chipset found in Amigas.
328 To compile this driver as a module, choose M here: the
329 module will be called amifb.
332 bool "Amiga OCS chipset support"
335 This enables support for the original Agnus and Denise video chips,
336 found in the Amiga 1000 and most A500's and A2000's. If you intend
337 to run Linux on any of these systems, say Y; otherwise say N.
340 bool "Amiga ECS chipset support"
343 This enables support for the Enhanced Chip Set, found in later
344 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
345 you intend to run Linux on any of these systems, say Y; otherwise
349 bool "Amiga AGA chipset support"
352 This enables support for the Advanced Graphics Architecture (also
353 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
354 and CD32. If you intend to run Linux on any of these systems, say Y;
358 bool "Amiga FrameMaster II/Rainbow II support"
359 depends on (FB = y) && ZORRO
360 select FB_CFB_FILLRECT
361 select FB_CFB_COPYAREA
362 select FB_CFB_IMAGEBLIT
364 This is the frame buffer device driver for the Amiga FrameMaster
365 card from BSC (exhibited 1992 but not shipped as a CBM product).
368 tristate "Arc Monochrome LCD board support"
370 select FB_CFB_FILLRECT
371 select FB_CFB_COPYAREA
372 select FB_CFB_IMAGEBLIT
374 This enables support for the Arc Monochrome LCD board. The board
375 is based on the KS-108 lcd controller and is typically a matrix
376 of 2*n chips. This driver was tested with a 128x64 panel. This
377 driver supports it for use with x86 SBCs through a 16 bit GPIO
378 interface (8 bit data, 8 bit control). If you anticipate using
379 this driver, say Y or M; otherwise say N. You must specify the
380 GPIO IO address to be used for setting control and data.
383 bool "Atari native chipset support"
384 depends on (FB = y) && ATARI && BROKEN
386 This is the frame buffer device driver for the builtin graphics
387 chipset found in Ataris.
390 bool "Open Firmware frame buffer device support"
391 depends on (FB = y) && (PPC64 || PPC_OF)
392 select FB_CFB_FILLRECT
393 select FB_CFB_COPYAREA
394 select FB_CFB_IMAGEBLIT
397 Say Y if you want support with Open Firmware for your graphics
401 bool "Apple \"control\" display support"
402 depends on (FB = y) && PPC_PMAC && PPC32
403 select FB_CFB_FILLRECT
404 select FB_CFB_COPYAREA
405 select FB_CFB_IMAGEBLIT
408 This driver supports a frame buffer for the graphics adapter in the
409 Power Macintosh 7300 and others.
412 bool "Apple \"platinum\" display support"
413 depends on (FB = y) && PPC_PMAC && PPC32
414 select FB_CFB_FILLRECT
415 select FB_CFB_COPYAREA
416 select FB_CFB_IMAGEBLIT
419 This driver supports a frame buffer for the "platinum" graphics
420 adapter in some Power Macintoshes.
423 bool "Apple \"valkyrie\" display support"
424 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
425 select FB_CFB_FILLRECT
426 select FB_CFB_COPYAREA
427 select FB_CFB_IMAGEBLIT
430 This driver supports a frame buffer for the "valkyrie" graphics
431 adapter in some Power Macintoshes.
434 bool "Chips 65550 display support"
435 depends on (FB = y) && PPC32
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 Chips & Technologies
441 65550 graphics chip in PowerBooks.
444 bool "Asiliant (Chips) 69000 display support"
445 depends on (FB = y) && PCI
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 Asiliant 69030 chipset
453 bool "IMS Twin Turbo display support"
454 depends on (FB = y) && PCI
455 select FB_CFB_IMAGEBLIT
456 select FB_MACMODES if PPC
458 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
459 many Macintosh and compatible computers.
462 tristate "VGA 16-color graphics support"
463 depends on FB && (X86 || PPC)
464 select FB_CFB_FILLRECT
465 select FB_CFB_COPYAREA
466 select FB_CFB_IMAGEBLIT
468 This is the frame buffer device driver for VGA 16 color graphic
469 cards. Say Y if you have such a card.
471 To compile this driver as a module, choose M here: the
472 module will be called vga16fb.
475 tristate "HP STI frame buffer device support"
476 depends on FB && PARISC
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
482 STI refers to the HP "Standard Text Interface" which is a set of
483 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
484 Enabling this option will implement the linux framebuffer device
485 using calls to the STI BIOS routines for initialisation.
487 If you enable this option, you will get a planar framebuffer device
488 /dev/fb which will work on the most common HP graphic cards of the
489 NGLE family, including the artist chips (in the 7xx and Bxxx series),
490 HCRX, HCRX24, CRX, CRX24 and VisEG series.
492 It is safe to enable this option, so you should probably say "Y".
495 bool "Generic Macintosh display support"
496 depends on (FB = y) && MAC
497 select FB_CFB_FILLRECT
498 select FB_CFB_COPYAREA
499 select FB_CFB_IMAGEBLIT
502 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
505 depends on (FB = y) && HP300
506 select FB_CFB_FILLRECT
507 select FB_CFB_IMAGEBLIT
511 tristate "TGA framebuffer support"
512 depends on FB && ALPHA
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
518 This is the frame buffer device driver for generic TGA graphic
519 cards. Say Y if you have one of those.
522 bool "VESA VGA graphics support"
523 depends on (FB = y) && X86
524 select FB_CFB_FILLRECT
525 select FB_CFB_COPYAREA
526 select FB_CFB_IMAGEBLIT
529 This is the frame buffer device driver for generic VESA 2.0
530 compliant graphic cards. The older VESA 1.2 cards are not supported.
531 You will get a boot time penguin logo at no additional cost. Please
532 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
535 bool "Intel-based Macintosh Framebuffer Support"
536 depends on (FB = y) && X86 && EFI
537 select FB_CFB_FILLRECT
538 select FB_CFB_COPYAREA
539 select FB_CFB_IMAGEBLIT
541 This is the frame buffer device driver for the Intel-based Macintosh
544 tristate "Hercules mono graphics support"
546 select FB_CFB_FILLRECT
547 select FB_CFB_COPYAREA
548 select FB_CFB_IMAGEBLIT
550 Say Y here if you have a Hercules mono graphics card.
552 To compile this driver as a module, choose M here: the
553 module will be called hgafb.
555 As this card technology is 15 years old, most people will answer N
559 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
560 depends on FB_HGA && EXPERIMENTAL
562 This will compile the Hercules mono graphics with
563 acceleration functions.
566 tristate "SGI Visual Workstation framebuffer support"
567 depends on FB && X86_VISWS
568 select FB_CFB_FILLRECT
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
572 SGI Visual Workstation support for framebuffer graphics.
575 bool "SGI Graphics Backend frame buffer support"
576 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
577 select FB_CFB_FILLRECT
578 select FB_CFB_COPYAREA
579 select FB_CFB_IMAGEBLIT
581 This is the frame buffer device driver for SGI Graphics Backend.
582 This chip is used in SGI O2 and Visual Workstation 320/540.
585 int "Video memory size in MB"
589 This is the amount of memory reserved for the framebuffer,
590 which can be any value between 1MB and 8MB.
593 bool "SBUS and UPA framebuffers"
594 depends on (FB = y) && SPARC
596 Say Y if you want support for SBUS or UPA based frame buffer device.
600 depends on (FB = y) && (SPARC && FB_SBUS)
601 select FB_CFB_FILLRECT
602 select FB_CFB_COPYAREA
603 select FB_CFB_IMAGEBLIT
605 This is the frame buffer device driver for the BWtwo frame buffer.
608 bool "CGthree support"
609 depends on (FB = y) && (SPARC && FB_SBUS)
610 select FB_CFB_FILLRECT
611 select FB_CFB_COPYAREA
612 select FB_CFB_IMAGEBLIT
614 This is the frame buffer device driver for the CGthree frame buffer.
617 bool "CGsix (GX,TurboGX) support"
618 depends on (FB = y) && (SPARC && FB_SBUS)
619 select FB_CFB_COPYAREA
620 select FB_CFB_IMAGEBLIT
622 This is the frame buffer device driver for the CGsix (GX, TurboGX)
626 tristate "NEC PowerVR 2 display support"
627 depends on FB && SH_DREAMCAST
628 select FB_CFB_FILLRECT
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
632 Say Y here if you have a PowerVR 2 card in your box. If you plan to
633 run linux on your Dreamcast, you will have to say Y here.
634 This driver may or may not work on other PowerVR 2 cards, but is
635 totally untested. Use at your own risk. If unsure, say N.
637 To compile this driver as a module, choose M here: the
638 module will be called pvr2fb.
640 You can pass several parameters to the driver at boot time or at
641 module load time. The parameters look like "video=pvr2:XXX", where
642 the meaning of XXX can be found at the end of the main source file
643 (<file:drivers/video/pvr2fb.c>). Please see the file
644 <file:Documentation/fb/pvr2fb.txt>.
647 bool "Epson 1355 framebuffer support"
648 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
653 Build in support for the SED1355 Epson Research Embedded RAMDAC
654 LCD/CRT Controller (since redesignated as the S1D13505) as a
655 framebuffer. Product specs at
656 <http://www.erd.epson.com/vdc/html/products.htm>.
659 tristate "Epson S1D13XXX framebuffer support"
661 select FB_CFB_FILLRECT
662 select FB_CFB_COPYAREA
663 select FB_CFB_IMAGEBLIT
665 Support for S1D13XXX framebuffer device family (currently only
666 working with S1D13806). Product specs at
667 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
670 tristate "nVidia Framebuffer Support"
672 select I2C_ALGOBIT if FB_NVIDIA_I2C
673 select I2C if FB_NVIDIA_I2C
674 select FB_MODE_HELPERS
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
680 This driver supports graphics boards with the nVidia chips, TNT
681 and newer. For very old chipsets, such as the RIVA128, then use
683 Say Y if you have such a graphics board.
685 To compile this driver as a module, choose M here: the
686 module will be called nvidiafb.
689 bool "Enable DDC Support"
692 This enables I2C support for nVidia Chipsets. This is used
693 only for getting EDID information from the attached display
694 allowing for robust video mode handling and switching.
696 Because fbdev-2.6 requires that drivers must be able to
697 independently validate video mode parameters, you should say Y
700 config FB_NVIDIA_BACKLIGHT
701 bool "Support for backlight control"
702 depends on FB_NVIDIA && PMAC_BACKLIGHT
706 Say Y here if you want to control the backlight of your display.
709 tristate "nVidia Riva support"
711 select I2C_ALGOBIT if FB_RIVA_I2C
712 select I2C if FB_RIVA_I2C
713 select FB_DDC if FB_RIVA_I2C
714 select FB_MODE_HELPERS
715 select FB_CFB_FILLRECT
716 select FB_CFB_COPYAREA
717 select FB_CFB_IMAGEBLIT
720 This driver supports graphics boards with the nVidia Riva/Geforce
722 Say Y if you have such a graphics board.
724 To compile this driver as a module, choose M here: the
725 module will be called rivafb.
728 bool "Enable DDC Support"
731 This enables I2C support for nVidia Chipsets. This is used
732 only for getting EDID information from the attached display
733 allowing for robust video mode handling and switching.
735 Because fbdev-2.6 requires that drivers must be able to
736 independently validate video mode parameters, you should say Y
740 bool "Lots of debug output from Riva(nVidia) driver"
744 Say Y here if you want the Riva driver to output all sorts
745 of debugging information to provide to the maintainer when
746 something goes wrong.
748 config FB_RIVA_BACKLIGHT
749 bool "Support for backlight control"
750 depends on FB_RIVA && PMAC_BACKLIGHT
754 Say Y here if you want to control the backlight of your display.
757 tristate "Intel 810/815 support (EXPERIMENTAL)"
758 depends on FB && EXPERIMENTAL && PCI && X86_32
761 select FB_MODE_HELPERS
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
766 This driver supports the on-board graphics built in to the Intel 810
767 and 815 chipsets. Say Y if you have and plan to use such a board.
769 To compile this driver as a module, choose M here: the
770 module will be called i810fb.
772 For more information, please read
773 <file:Documentation/fb/intel810.txt>
776 bool "use VESA Generalized Timing Formula"
779 If you say Y, then the VESA standard, Generalized Timing Formula
780 or GTF, will be used to calculate the required video timing values
781 per video mode. Since the GTF allows nondiscrete timings
782 (nondiscrete being a range of values as opposed to discrete being a
783 set of values), you'll be able to use any combination of horizontal
784 and vertical resolutions, and vertical refresh rates without having
785 to specify your own timing parameters. This is especially useful
786 to maximize the performance of an aging display, or if you just
787 have a display with nonstandard dimensions. A VESA compliant
788 monitor is recommended, but can still work with non-compliant ones.
789 If you need or want this, then select this option. The timings may
790 not be compliant with Intel's recommended values. Use at your own
793 If you say N, the driver will revert to discrete video timings
794 using a set recommended by Intel in their documentation.
799 bool "Enable DDC Support"
800 depends on FB_I810 && FB_I810_GTF
807 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
808 depends on FB && EXPERIMENTAL && PCI && X86
811 select I2C_ALGOBIT if FB_INTEL_I2C
812 select I2C if FB_INTEL_I2C
813 select FB_MODE_HELPERS
814 select FB_CFB_FILLRECT
815 select FB_CFB_COPYAREA
816 select FB_CFB_IMAGEBLIT
818 This driver supports the on-board graphics built in to the Intel
819 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
820 Say Y if you have and plan to use such a board.
822 If you say Y here and want DDC/I2C support you must first say Y to
823 "I2C support" and "I2C bit-banging support" in the character devices
826 If you say M here then "I2C support" and "I2C bit-banging support"
827 can be build either as modules or built-in.
829 To compile this driver as a module, choose M here: the
830 module will be called intelfb.
832 For more information, please read <file:Documentation/fb/intelfb.txt>
834 config FB_INTEL_DEBUG
835 bool "Intel driver Debug Messages"
838 Say Y here if you want the Intel driver to output all sorts
839 of debugging information to provide to the maintainer when
840 something goes wrong.
843 bool "DDC/I2C for Intel framebuffer support"
847 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
850 tristate "Matrox acceleration"
852 select FB_CFB_FILLRECT
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
855 select FB_TILEBLITTING
856 select FB_MACMODES if PPC_PMAC
858 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
859 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
860 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
861 Matrox G400, G450 or G550 card in your box.
863 To compile this driver as a module, choose M here: the
864 module will be called matroxfb.
866 You can pass several parameters to the driver at boot time or at
867 module load time. The parameters look like "video=matrox:XXX", and
868 are described in <file:Documentation/fb/matroxfb.txt>.
870 config FB_MATROX_MILLENIUM
871 bool "Millennium I/II support"
874 Say Y here if you have a Matrox Millennium or Matrox Millennium II
875 video card. If you select "Advanced lowlevel driver options" below,
876 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
877 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
878 also use font widths different from 8.
880 config FB_MATROX_MYSTIQUE
881 bool "Mystique support"
884 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
885 video card. If you select "Advanced lowlevel driver options" below,
886 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
887 packed pixel and 32 bpp packed pixel. You can also use font widths
891 bool "G100/G200/G400/G450/G550 support"
894 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
895 video card. If you select "Advanced lowlevel driver options", you
896 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
897 pixel and 32 bpp packed pixel. You can also use font widths
900 If you need support for G400 secondary head, you must first say Y to
901 "I2C support" in the character devices section, and then to
902 "Matrox I2C support" and "G400 second head support" here in the
903 framebuffer section. G450/G550 secondary head and digital output
904 are supported without additional modules.
906 The driver starts in monitor mode. You must use the matroxset tool
907 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
908 swap primary and secondary head outputs, or to change output mode.
909 Secondary head driver always start in 640x480 resolution and you
910 must use fbset to change it.
912 Do not forget that second head supports only 16 and 32 bpp
913 packed pixels, so it is a good idea to compile them into the kernel
914 too. You can use only some font widths, as the driver uses generic
915 painting procedures (the secondary head does not use acceleration
918 G450/G550 hardware can display TV picture only from secondary CRTC,
919 and it performs no scaling, so picture must have 525 or 625 lines.
922 tristate "Matrox I2C support"
923 depends on FB_MATROX && I2C
926 This drivers creates I2C buses which are needed for accessing the
927 DDC (I2C) bus present on all Matroxes, an I2C bus which
928 interconnects Matrox optional devices, like MGA-TVO on G200 and
929 G400, and the secondary head DDC bus, present on G400 only.
931 You can say Y or M here if you want to experiment with monitor
932 detection code. You must say Y or M here if you want to use either
933 second head of G400 or MGA-TVO on G200 or G400.
935 If you compile it as module, it will create a module named
938 config FB_MATROX_MAVEN
939 tristate "G400 second head support"
940 depends on FB_MATROX_G && FB_MATROX_I2C
942 WARNING !!! This support does not work with G450 !!!
944 Say Y or M here if you want to use a secondary head (meaning two
945 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
946 head is not compatible with accelerated XFree 3.3.x SVGA servers -
947 secondary head output is blanked while you are in X. With XFree
948 3.9.17 preview you can use both heads if you use SVGA over fbdev or
949 the fbdev driver on first head and the fbdev driver on second head.
951 If you compile it as module, two modules are created,
952 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
953 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
954 also load i2c-matroxfb to get it to run.
956 The driver starts in monitor mode and you must use the matroxset
958 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
959 PAL or NTSC or to swap primary and secondary head outputs.
960 Secondary head driver also always start in 640x480 resolution, you
961 must use fbset to change it.
963 Also do not forget that second head supports only 16 and 32 bpp
964 packed pixels, so it is a good idea to compile them into the kernel
965 too. You can use only some font widths, as the driver uses generic
966 painting procedures (the secondary head does not use acceleration
969 config FB_MATROX_MULTIHEAD
970 bool "Multihead support"
973 Say Y here if you have more than one (supported) Matrox device in
974 your computer and you want to use all of them for different monitors
975 ("multihead"). If you have only one device, you should say N because
976 the driver compiled with Y is larger and a bit slower, especially on
979 If you said M to "Matrox unified accelerated driver" and N here, you
980 will still be able to use several Matrox devices simultaneously:
981 insert several instances of the module matroxfb into the kernel
982 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
983 for the different Matrox devices. This method is slightly faster but
984 uses 40 KB of kernel memory per Matrox card.
986 There is no need for enabling 'Matrox multihead support' if you have
987 only one Matrox card in the box.
990 tristate "ATI Radeon display support"
992 select I2C_ALGOBIT if FB_RADEON_I2C
993 select I2C if FB_RADEON_I2C
994 select FB_DDC if FB_RADEON_I2C
995 select FB_MODE_HELPERS
996 select FB_CFB_FILLRECT
997 select FB_CFB_COPYAREA
998 select FB_CFB_IMAGEBLIT
999 select FB_MACMODES if PPC_OF
1001 Choose this option if you want to use an ATI Radeon graphics card as
1002 a framebuffer device. There are both PCI and AGP versions. You
1003 don't need to choose this to run the Radeon in plain VGA mode.
1005 If you say Y here and want DDC/I2C support you must first say Y to
1006 "I2C support" and "I2C bit-banging support" in the character devices
1009 If you say M here then "I2C support" and "I2C bit-banging support"
1010 can be build either as modules or built-in.
1012 There is a product page at
1013 http://apps.ati.com/ATIcompare/
1015 config FB_RADEON_I2C
1016 bool "DDC/I2C for ATI Radeon support"
1017 depends on FB_RADEON
1020 Say Y here if you want DDC/I2C support for your Radeon board.
1022 config FB_RADEON_BACKLIGHT
1023 bool "Support for backlight control"
1024 depends on FB_RADEON && PMAC_BACKLIGHT
1028 Say Y here if you want to control the backlight of your display.
1030 config FB_RADEON_DEBUG
1031 bool "Lots of debug output from Radeon driver"
1032 depends on FB_RADEON
1035 Say Y here if you want the Radeon driver to output all sorts
1036 of debugging information to provide to the maintainer when
1037 something goes wrong.
1040 tristate "ATI Rage128 display support"
1041 depends on FB && PCI
1042 select FB_CFB_FILLRECT
1043 select FB_CFB_COPYAREA
1044 select FB_CFB_IMAGEBLIT
1045 select FB_MACMODES if PPC_PMAC
1047 This driver supports graphics boards with the ATI Rage128 chips.
1048 Say Y if you have such a graphics board and read
1049 <file:Documentation/fb/aty128fb.txt>.
1051 To compile this driver as a module, choose M here: the
1052 module will be called aty128fb.
1054 config FB_ATY128_BACKLIGHT
1055 bool "Support for backlight control"
1056 depends on FB_ATY128 && PMAC_BACKLIGHT
1060 Say Y here if you want to control the backlight of your display.
1063 tristate "ATI Mach64 display support" if PCI || ATARI
1064 depends on FB && !SPARC32
1065 select FB_CFB_FILLRECT
1066 select FB_CFB_COPYAREA
1067 select FB_CFB_IMAGEBLIT
1068 select FB_MACMODES if PPC
1070 This driver supports graphics boards with the ATI Mach64 chips.
1071 Say Y if you have such a graphics board.
1073 To compile this driver as a module, choose M here: the
1074 module will be called atyfb.
1077 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1078 depends on PCI && FB_ATY
1079 default y if SPARC64 && FB_PCI
1081 Say Y here to support use of ATI's 64-bit Rage boards (or other
1082 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1083 framebuffer device. The ATI product support page for these boards
1084 is at <http://support.ati.com/products/pc/mach64/>.
1086 config FB_ATY_GENERIC_LCD
1087 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1088 depends on FB_ATY_CT
1090 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1091 Rage XC, or Rage XL chipset.
1094 bool "Mach64 GX support" if PCI
1098 Say Y here to support use of the ATI Mach64 Graphics Expression
1099 board (or other boards based on the Mach64 GX chipset) as a
1100 framebuffer device. The ATI product support page for these boards
1102 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1104 config FB_ATY_BACKLIGHT
1105 bool "Support for backlight control"
1106 depends on FB_ATY && PMAC_BACKLIGHT
1110 Say Y here if you want to control the backlight of your display.
1113 tristate "S3 Trio/Virge support"
1114 depends on FB && PCI
1115 select FB_CFB_FILLRECT
1116 select FB_CFB_COPYAREA
1117 select FB_CFB_IMAGEBLIT
1118 select FB_TILEBLITTING
1121 Driver for graphics boards with S3 Trio / S3 Virge chip.
1124 tristate "S3 Savage support"
1125 depends on FB && PCI && EXPERIMENTAL
1126 select I2C_ALGOBIT if FB_SAVAGE_I2C
1127 select I2C if FB_SAVAGE_I2C
1128 select FB_DDC if FB_SAVAGE_I2C
1129 select FB_MODE_HELPERS
1130 select FB_CFB_FILLRECT
1131 select FB_CFB_COPYAREA
1132 select FB_CFB_IMAGEBLIT
1134 This driver supports notebooks and computers with S3 Savage PCI/AGP
1137 Say Y if you have such a graphics card.
1139 To compile this driver as a module, choose M here; the module
1140 will be called savagefb.
1142 config FB_SAVAGE_I2C
1143 bool "Enable DDC2 Support"
1144 depends on FB_SAVAGE
1146 This enables I2C support for S3 Savage Chipsets. This is used
1147 only for getting EDID information from the attached display
1148 allowing for robust video mode handling and switching.
1150 Because fbdev-2.6 requires that drivers must be able to
1151 independently validate video mode parameters, you should say Y
1154 config FB_SAVAGE_ACCEL
1155 bool "Enable Console Acceleration"
1156 depends on FB_SAVAGE
1159 This option will compile in console acceleration support. If
1160 the resulting framebuffer console has bothersome glitches, then
1164 tristate "SiS/XGI display support"
1165 depends on FB && PCI
1166 select FB_CFB_FILLRECT
1167 select FB_CFB_COPYAREA
1168 select FB_CFB_IMAGEBLIT
1170 This is the frame buffer device driver for the SiS 300, 315, 330
1171 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1172 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1174 To compile this driver as a module, choose M here; the module
1175 will be called sisfb.
1178 bool "SiS 300 series support"
1181 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1184 bool "SiS 315/330/340 series and XGI support"
1187 Say Y here to support use of the SiS 315, 330 and 340 series
1188 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1189 as XGI V3XT, V5, V8 and Z7.
1192 tristate "NeoMagic display support"
1193 depends on FB && PCI
1194 select FB_MODE_HELPERS
1195 select FB_CFB_FILLRECT
1196 select FB_CFB_COPYAREA
1197 select FB_CFB_IMAGEBLIT
1199 This driver supports notebooks with NeoMagic PCI chips.
1200 Say Y if you have such a graphics card.
1202 To compile this driver as a module, choose M here: the
1203 module will be called neofb.
1206 tristate "IMG Kyro support"
1207 depends on FB && PCI
1208 select FB_CFB_FILLRECT
1209 select FB_CFB_COPYAREA
1210 select FB_CFB_IMAGEBLIT
1212 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1215 To compile this driver as a module, choose M here: the
1216 module will be called kyrofb.
1219 tristate "3Dfx Banshee/Voodoo3 display support"
1220 depends on FB && PCI
1221 select FB_CFB_IMAGEBLIT
1222 select FB_CFB_FILLRECT
1223 select FB_CFB_COPYAREA
1225 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1226 chips. Say Y if you have such a graphics board.
1228 To compile this driver as a module, choose M here: the
1229 module will be called tdfxfb.
1231 config FB_3DFX_ACCEL
1232 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1233 depends on FB_3DFX && EXPERIMENTAL
1235 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1236 with acceleration functions.
1240 tristate "3Dfx Voodoo Graphics (sst1) support"
1241 depends on FB && PCI
1242 select FB_CFB_FILLRECT
1243 select FB_CFB_COPYAREA
1244 select FB_CFB_IMAGEBLIT
1246 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1247 Voodoo2 (cvg) based graphics card.
1249 To compile this driver as a module, choose M here: the
1250 module will be called sstfb.
1252 WARNING: Do not use any application that uses the 3D engine
1253 (namely glide) while using this driver.
1254 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1255 options and other important info support.
1258 tristate "Cyberblade/i1 support"
1259 depends on FB && PCI && X86_32 && !64BIT
1260 select FB_CFB_IMAGEBLIT
1263 This driver is supposed to support the Trident Cyberblade/i1
1264 graphics core integrated in the VIA VT8601A North Bridge,
1265 also known as VIA Apollo PLE133.
1268 - Developed, tested and working on EPIA 5000 and EPIA 800.
1269 - Does work reliable on all systems with CRT/LCD connected to
1271 - Should work on systems that do use the internal LCD port, but
1272 this is absolutely not tested.
1274 Character imageblit, copyarea and rectangle fill are hw accelerated,
1275 ypan scrolling is used by default.
1277 Please do read <file:Documentation/fb/cyblafb/*>.
1279 To compile this driver as a module, choose M here: the
1280 module will be called cyblafb.
1283 tristate "Trident support"
1284 depends on FB && PCI
1285 select FB_CFB_FILLRECT
1286 select FB_CFB_COPYAREA
1287 select FB_CFB_IMAGEBLIT
1289 This driver is supposed to support graphics boards with the
1290 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1291 but also on some motherboards. For more information, read
1292 <file:Documentation/fb/tridentfb.txt>
1294 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1297 Say Y if you have such a graphics board.
1300 To compile this driver as a module, choose M here: the
1301 module will be called tridentfb.
1303 config FB_TRIDENT_ACCEL
1304 bool "Trident Acceleration functions (EXPERIMENTAL)"
1305 depends on FB_TRIDENT && EXPERIMENTAL
1307 This will compile the Trident frame buffer device with
1308 acceleration functions.
1311 tristate "Permedia3 support"
1312 depends on FB && PCI && BROKEN
1314 This is the frame buffer device driver for the 3DLabs Permedia3
1315 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1316 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1317 and maybe other boards.
1320 bool "Au1100 LCD Driver"
1321 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1324 bool "Au1200 LCD Driver"
1325 depends on FB && MIPS && SOC_AU1200
1326 select FB_CFB_FILLRECT
1327 select FB_CFB_COPYAREA
1328 select FB_CFB_IMAGEBLIT
1330 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1331 various panels and CRTs by passing in kernel cmd line option
1332 au1200fb:panel=<name>.
1334 source "drivers/video/geode/Kconfig"
1337 bool "Creator/Creator3D/Elite3D support"
1338 depends on FB_SBUS && SPARC64
1339 select FB_CFB_COPYAREA
1340 select FB_CFB_IMAGEBLIT
1342 This is the frame buffer device driver for the Creator, Creator3D,
1343 and Elite3D graphics boards.
1346 bool "TCX (SS4/SS5 only) support"
1348 select FB_CFB_FILLRECT
1349 select FB_CFB_COPYAREA
1350 select FB_CFB_IMAGEBLIT
1352 This is the frame buffer device driver for the TCX 24/8bit frame
1356 bool "CGfourteen (SX) support"
1358 select FB_CFB_FILLRECT
1359 select FB_CFB_COPYAREA
1360 select FB_CFB_IMAGEBLIT
1362 This is the frame buffer device driver for the CGfourteen frame
1363 buffer on Desktop SPARCsystems with the SX graphics option.
1366 bool "P9100 (Sparcbook 3 only) support"
1368 select FB_CFB_FILLRECT
1369 select FB_CFB_COPYAREA
1370 select FB_CFB_IMAGEBLIT
1372 This is the frame buffer device driver for the P9100 card
1373 supported on Sparcbook 3 machines.
1376 bool "Leo (ZX) support"
1378 select FB_CFB_FILLRECT
1379 select FB_CFB_COPYAREA
1380 select FB_CFB_IMAGEBLIT
1382 This is the frame buffer device driver for the SBUS-based Sun ZX
1383 (leo) frame buffer cards.
1386 bool "PCI framebuffers"
1387 depends on (FB = y) && PCI && SPARC
1390 bool "IGA 168x display support"
1391 depends on SPARC32 && FB_PCI
1392 select FB_CFB_FILLRECT
1393 select FB_CFB_COPYAREA
1394 select FB_CFB_IMAGEBLIT
1396 This is the framebuffer device for the INTERGRAPHICS 1680 and
1397 successor frame buffer cards.
1400 tristate "HD64461 Frame Buffer support"
1401 depends on FB && HD64461
1402 select FB_CFB_FILLRECT
1403 select FB_CFB_COPYAREA
1404 select FB_CFB_IMAGEBLIT
1406 This is the frame buffer device driver for the Hitachi HD64461 LCD
1410 bool "PMAG-AA TURBOchannel framebuffer support"
1411 depends on (FB = y) && TC
1412 select FB_CFB_FILLRECT
1413 select FB_CFB_COPYAREA
1414 select FB_CFB_IMAGEBLIT
1416 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1417 used mainly in the MIPS-based DECstation series.
1420 tristate "PMAG-BA TURBOchannel framebuffer support"
1422 select FB_CFB_FILLRECT
1423 select FB_CFB_COPYAREA
1424 select FB_CFB_IMAGEBLIT
1426 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1427 used mainly in the MIPS-based DECstation series.
1430 tristate "PMAGB-B TURBOchannel framebuffer support"
1432 select FB_CFB_FILLRECT
1433 select FB_CFB_COPYAREA
1434 select FB_CFB_IMAGEBLIT
1436 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1437 in the MIPS-based DECstation series. The card is currently only
1438 supported in 1280x1024x8 mode.
1441 bool "Maxine (Personal DECstation) onboard framebuffer support"
1442 depends on (FB = y) && MACH_DECSTATION
1443 select FB_CFB_FILLRECT
1444 select FB_CFB_COPYAREA
1445 select FB_CFB_IMAGEBLIT
1447 Support for the onboard framebuffer (1024x768x8) in the Personal
1448 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1452 bool "TMPTX3912/PR31700 frame buffer support"
1453 depends on (FB = y) && NINO
1454 select FB_CFB_FILLRECT
1455 select FB_CFB_COPYAREA
1456 select FB_CFB_IMAGEBLIT
1458 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1459 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1461 Say Y here to enable kernel support for the on-board framebuffer.
1464 bool "G364 frame buffer support"
1465 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1470 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1471 Olivetti M700-10 systems.
1474 bool "Motorola 68328 native frame buffer support"
1475 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1476 select FB_CFB_FILLRECT
1477 select FB_CFB_COPYAREA
1478 select FB_CFB_IMAGEBLIT
1480 Say Y here if you want to support the built-in frame buffer of
1481 the Motorola 68328 CPU family.
1484 tristate "PXA LCD framebuffer support"
1485 depends on FB && ARCH_PXA
1486 select FB_CFB_FILLRECT
1487 select FB_CFB_COPYAREA
1488 select FB_CFB_IMAGEBLIT
1490 Frame buffer driver for the built-in LCD controller in the Intel
1493 This driver is also available as a module ( = code which can be
1494 inserted and removed from the running kernel whenever you want). The
1495 module will be called pxafb. If you want to compile it as a module,
1496 say M here and read <file:Documentation/modules.txt>.
1500 config FB_PXA_PARAMETERS
1501 bool "PXA LCD command line parameters"
1505 Enable the use of kernel command line or module parameters
1506 to configure the physical properties of the LCD panel when
1507 using the PXA LCD driver.
1509 This option allows you to override the panel parameters
1510 supplied by the platform in order to support multiple
1511 different models of flatpanel. If you will only be using a
1512 single model of flatpanel then you can safely leave this
1515 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1518 tristate "2700G LCD framebuffer support"
1519 depends on FB && ARCH_PXA
1520 select FB_CFB_FILLRECT
1521 select FB_CFB_COPYAREA
1522 select FB_CFB_IMAGEBLIT
1524 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1528 bool "Enable debugging info via debugfs"
1529 depends on FB_MBX && DEBUG_FS
1532 Enable this if you want debugging information using the debug
1533 filesystem (debugfs)
1538 tristate "W100 frame buffer support"
1539 depends on FB && PXA_SHARPSL
1540 select FB_CFB_FILLRECT
1541 select FB_CFB_COPYAREA
1542 select FB_CFB_IMAGEBLIT
1544 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1546 This driver is also available as a module ( = code which can be
1547 inserted and removed from the running kernel whenever you want). The
1548 module will be called w100fb. If you want to compile it as a module,
1549 say M here and read <file:Documentation/modules.txt>.
1554 tristate "S3C2410 LCD framebuffer support"
1555 depends on FB && ARCH_S3C2410
1556 select FB_CFB_FILLRECT
1557 select FB_CFB_COPYAREA
1558 select FB_CFB_IMAGEBLIT
1560 Frame buffer driver for the built-in LCD controller in the Samsung
1563 This driver is also available as a module ( = code which can be
1564 inserted and removed from the running kernel whenever you want). The
1565 module will be called s3c2410fb. If you want to compile it as a module,
1566 say M here and read <file:Documentation/modules.txt>.
1569 config FB_S3C2410_DEBUG
1570 bool "S3C2410 lcd debug messages"
1571 depends on FB_S3C2410
1573 Turn on debugging messages. Note that you can set/unset at run time
1576 config FB_PNX4008_DUM
1577 tristate "Display Update Module support on Philips PNX4008 board"
1578 depends on FB && ARCH_PNX4008
1580 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1582 config FB_PNX4008_DUM_RGB
1583 tristate "RGB Framebuffer support on Philips PNX4008 board"
1584 depends on FB_PNX4008_DUM
1585 select FB_CFB_FILLRECT
1586 select FB_CFB_COPYAREA
1587 select FB_CFB_IMAGEBLIT
1589 Say Y here to enable support for PNX4008 RGB Framebuffer
1591 config FB_IBM_GXT4500
1592 tristate "Framebuffer support for IBM GXT4500P adaptor"
1594 select FB_CFB_FILLRECT
1595 select FB_CFB_COPYAREA
1596 select FB_CFB_IMAGEBLIT
1598 Say Y here to enable support for the IBM GXT4500P display
1599 adaptor, found on some IBM System P (pSeries) machines.
1602 bool "PS3 GPU framebuffer driver"
1603 depends on FB && PPC_PS3
1605 select FB_CFB_FILLRECT
1606 select FB_CFB_COPYAREA
1607 select FB_CFB_IMAGEBLIT
1609 Include support for the virtual frame buffer in the PS3 platform.
1611 config FB_PS3_DEFAULT_SIZE_M
1612 int "PS3 default frame buffer size (in MiB)"
1616 This is the default size (in MiB) of the virtual frame buffer in
1618 The default value can be overridden on the kernel command line
1619 using the "ps3fb" option (e.g. "ps3fb=9M");
1622 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1624 select FB_CFB_FILLRECT
1625 select FB_CFB_COPYAREA
1626 select FB_CFB_IMAGEBLIT
1628 This is a `virtual' frame buffer device. It operates on a chunk of
1629 unswappable kernel memory instead of on the memory of a graphics
1630 board. This means you cannot see any output sent to this frame
1631 buffer device, while it does consume precious memory. The main use
1632 of this frame buffer device is testing and debugging the frame
1633 buffer subsystem. Do NOT enable it for normal systems! To protect
1634 the innocent, it has to be enabled explicitly at boot time using the
1635 kernel option `video=vfb:'.
1637 To compile this driver as a module, choose M here: the
1638 module will be called vfb. In order to load it, you must use
1639 the vfb_enable=1 option.
1643 source "drivers/video/console/Kconfig"
1646 if FB || SGI_NEWPORT_CONSOLE
1647 source "drivers/video/logo/Kconfig"
1651 source "drivers/video/backlight/Kconfig"