5 menu "Graphics support"
7 source "drivers/video/backlight/Kconfig"
8 source "drivers/video/display/Kconfig"
11 tristate "Support for frame buffer devices"
13 The frame buffer device provides an abstraction for the graphics
14 hardware. It represents the frame buffer of some video hardware and
15 allows application software to access the graphics hardware through
16 a well-defined interface, so the software doesn't need to know
17 anything about the low-level (hardware register) stuff.
19 Frame buffer devices work identically across the different
20 architectures supported by Linux and make the implementation of
21 application programs easier and more portable; at this point, an X
22 server exists which uses the frame buffer device exclusively.
23 On several non-X86 architectures, the frame buffer device is the
24 only way to use the graphics hardware.
26 The device is accessed through special device nodes, usually located
27 in the /dev directory, i.e. /dev/fb*.
29 You need an utility program called fbset to make full use of frame
30 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
31 and the Framebuffer-HOWTO at
32 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
35 Say Y here and to the driver for your graphics board below if you
36 are compiling a kernel for a non-x86 architecture.
38 If you are compiling for the x86 architecture, you can say Y if you
39 want to play with it, but it is not essential. Please note that
40 running graphical applications that directly touch the hardware
41 (e.g. an accelerated X server) and that are not frame buffer
42 device-aware may cause unexpected results. If unsure, say N.
45 bool "Enable firmware EDID"
49 This enables access to the EDID transferred from the firmware.
50 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
51 transfers do not work for your driver and if you are using
52 nvidiafb, i810fb or savagefb.
54 In general, choosing Y for this option is safe. If you
55 experience extremely long delays while booting before you get
56 something on your display, try setting this to N. Matrox cards in
57 combination with certain motherboards and monitors are known to
58 suffer from this problem.
67 config FB_CFB_FILLRECT
72 Include the cfb_fillrect function for generic software rectangle
73 filling. This is used by drivers that don't provide their own
74 (accelerated) version.
76 config FB_CFB_COPYAREA
81 Include the cfb_copyarea function for generic software area copying.
82 This is used by drivers that don't provide their own (accelerated)
85 config FB_CFB_IMAGEBLIT
90 Include the cfb_imageblit function for generic software image
91 blitting. This is used by drivers that don't provide their own
92 (accelerated) version.
104 Common utility functions useful to fbdev drivers of VGA-based
115 select BACKLIGHT_LCD_SUPPORT
116 select BACKLIGHT_CLASS_DEVICE
119 config FB_MODE_HELPERS
120 bool "Enable Video Mode Handling Helpers"
124 This enables functions for handling video modes using the
125 Generalized Timing Formula and the EDID parser. A few drivers rely
126 on this feature such as the radeonfb, rivafb, and the i810fb. If
127 your driver does not take advantage of this feature, choosing Y will
128 just increase the kernel size by about 5K.
130 config FB_TILEBLITTING
131 bool "Enable Tile Blitting Support"
135 This enables tile blitting. Tile blitting is a drawing technique
136 where the screen is divided into rectangular sections (tiles), whereas
137 the standard blitting divides the screen into pixels. Because the
138 default drawing element is a tile, drawing functions will be passed
139 parameters in terms of number of tiles instead of number of pixels.
140 For example, to draw a single character, instead of using bitmaps,
141 an index to an array of bitmaps will be used. To clear or move a
142 rectangular section of a screen, the rectangle will be described in
143 terms of number of tiles in the x- and y-axis.
145 This is particularly important to one driver, matroxfb. If
148 comment "Frame buffer hardware drivers"
152 tristate "Cirrus Logic support"
153 depends on FB && (ZORRO || PCI)
154 select FB_CFB_FILLRECT
155 select FB_CFB_COPYAREA
156 select FB_CFB_IMAGEBLIT
158 This enables support for Cirrus Logic GD542x/543x based boards on
159 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
161 If you have a PCI-based system, this enables support for these
162 chips: GD-543x, GD-544x, GD-5480.
164 Please read the file <file:Documentation/fb/cirrusfb.txt>.
166 Say N unless you have such a graphics board or plan to get one
167 before you next recompile the kernel.
170 tristate "Permedia2 support"
171 depends on FB && ((AMIGA && BROKEN) || PCI)
172 select FB_CFB_FILLRECT
173 select FB_CFB_COPYAREA
174 select FB_CFB_IMAGEBLIT
176 This is the frame buffer device driver for the Permedia2 AGP frame
177 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
179 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
181 config FB_PM2_FIFO_DISCONNECT
182 bool "enable FIFO disconnect feature"
183 depends on FB_PM2 && PCI
185 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
188 tristate "ARM PrimeCell PL110 support"
189 depends on FB && ARM && ARM_AMBA
190 select FB_CFB_FILLRECT
191 select FB_CFB_COPYAREA
192 select FB_CFB_IMAGEBLIT
194 This framebuffer device driver is for the ARM PrimeCell PL110
195 Colour LCD controller. ARM PrimeCells provide the building
196 blocks for System on a Chip devices.
198 If you want to compile this as a module (=code which can be
199 inserted into and removed from the running kernel), say M
200 here and read <file:Documentation/kbuild/modules.txt>. The module
201 will be called amba-clcd.
205 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
207 default FB_ARMCLCD_SHARP_LQ035Q7DB02
209 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
210 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
212 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
213 color QVGA, HRTFT panel. The LogicPD device includes
214 an integrated HRTFT controller IC.
215 The native resolution is 240x320.
217 config FB_ARMCLCD_SHARP_LQ057Q3DC02
218 bool "LogicPD LCD 5.7\" QVGA"
220 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
221 color QVGA, TFT panel. The LogicPD device includes an
222 The native resolution is 320x240.
224 config FB_ARMCLCD_SHARP_LQ64D343
225 bool "LogicPD LCD 6.4\" VGA"
227 This is an implementation of the Sharp LQ64D343, a 6.4"
228 color VGA, TFT panel. The LogicPD device includes an
229 The native resolution is 640x480.
231 config FB_ARMCLCD_SHARP_LQ10D368
232 bool "LogicPD LCD 10.4\" VGA"
234 This is an implementation of the Sharp LQ10D368, a 10.4"
235 color VGA, TFT panel. The LogicPD device includes an
236 The native resolution is 640x480.
239 config FB_ARMCLCD_SHARP_LQ121S1DG41
240 bool "LogicPD LCD 12.1\" SVGA"
242 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
243 color SVGA, TFT panel. The LogicPD device includes an
244 The native resolution is 800x600.
246 This panel requires a clock rate may be an integer fraction
247 of the base LCDCLK frequency. The driver will select the
248 highest frequency available that is lower than the maximum
249 allowed. The panel may flicker if the clock rate is
250 slower than the recommended minimum.
252 config FB_ARMCLCD_AUO_A070VW01_WIDE
253 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
255 This is an implementation of the AU Optronics, a 7.0"
256 WIDE Color. The native resolution is 234x480.
258 config FB_ARMCLCD_HITACHI
259 bool "Hitachi Wide Screen 800x480"
261 This is an implementation of the Hitachi 800x480.
267 bool "Acorn VIDC support"
268 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
269 select FB_CFB_FILLRECT
270 select FB_CFB_COPYAREA
271 select FB_CFB_IMAGEBLIT
273 This is the frame buffer device driver for the Acorn VIDC graphics
274 hardware found in Acorn RISC PCs and other ARM-based machines. If
278 bool "CLPS711X LCD support"
279 depends on (FB = y) && ARM && ARCH_CLPS711X
280 select FB_CFB_FILLRECT
281 select FB_CFB_COPYAREA
282 select FB_CFB_IMAGEBLIT
284 Say Y to enable the Framebuffer driver for the CLPS7111 and
288 bool "SA-1100 LCD support"
289 depends on (FB = y) && ARM && ARCH_SA1100
290 select FB_CFB_FILLRECT
291 select FB_CFB_COPYAREA
292 select FB_CFB_IMAGEBLIT
294 This is a framebuffer device for the SA-1100 LCD Controller.
295 See <http://www.linux-fbdev.org/> for information on framebuffer
298 If you plan to use the LCD display with your SA-1100 system, say
302 tristate "Motorola i.MX LCD support"
303 depends on FB && ARM && ARCH_IMX
304 select FB_CFB_FILLRECT
305 select FB_CFB_COPYAREA
306 select FB_CFB_IMAGEBLIT
309 tristate "CyberPro 2000/2010/5000 support"
310 depends on FB && PCI && (BROKEN || !SPARC64)
311 select FB_CFB_FILLRECT
312 select FB_CFB_COPYAREA
313 select FB_CFB_IMAGEBLIT
315 This enables support for the Integraphics CyberPro 20x0 and 5000
316 VGA chips used in the Rebel.com Netwinder and other machines.
317 Say Y if you have a NetWinder or a graphics card containing this
318 device, otherwise say N.
322 depends on (FB = y) && APOLLO
324 select FB_CFB_FILLRECT
325 select FB_CFB_IMAGEBLIT
329 depends on (FB = y) && Q40
331 select FB_CFB_FILLRECT
332 select FB_CFB_COPYAREA
333 select FB_CFB_IMAGEBLIT
336 tristate "Amiga native chipset support"
337 depends on FB && AMIGA
339 This is the frame buffer device driver for the builtin graphics
340 chipset found in Amigas.
342 To compile this driver as a module, choose M here: the
343 module will be called amifb.
346 bool "Amiga OCS chipset support"
349 This enables support for the original Agnus and Denise video chips,
350 found in the Amiga 1000 and most A500's and A2000's. If you intend
351 to run Linux on any of these systems, say Y; otherwise say N.
354 bool "Amiga ECS chipset support"
357 This enables support for the Enhanced Chip Set, found in later
358 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
359 you intend to run Linux on any of these systems, say Y; otherwise
363 bool "Amiga AGA chipset support"
366 This enables support for the Advanced Graphics Architecture (also
367 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
368 and CD32. If you intend to run Linux on any of these systems, say Y;
372 bool "Amiga FrameMaster II/Rainbow II support"
373 depends on (FB = y) && ZORRO
374 select FB_CFB_FILLRECT
375 select FB_CFB_COPYAREA
376 select FB_CFB_IMAGEBLIT
378 This is the frame buffer device driver for the Amiga FrameMaster
379 card from BSC (exhibited 1992 but not shipped as a CBM product).
382 tristate "Arc Monochrome LCD board support"
384 select FB_CFB_FILLRECT
385 select FB_CFB_COPYAREA
386 select FB_CFB_IMAGEBLIT
388 This enables support for the Arc Monochrome LCD board. The board
389 is based on the KS-108 lcd controller and is typically a matrix
390 of 2*n chips. This driver was tested with a 128x64 panel. This
391 driver supports it for use with x86 SBCs through a 16 bit GPIO
392 interface (8 bit data, 8 bit control). If you anticipate using
393 this driver, say Y or M; otherwise say N. You must specify the
394 GPIO IO address to be used for setting control and data.
397 bool "Atari native chipset support"
398 depends on (FB = y) && ATARI
399 select FB_CFB_FILLRECT
400 select FB_CFB_COPYAREA
401 select FB_CFB_IMAGEBLIT
403 This is the frame buffer device driver for the builtin graphics
404 chipset found in Ataris.
407 bool "Open Firmware frame buffer device support"
408 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
409 select FB_CFB_FILLRECT
410 select FB_CFB_COPYAREA
411 select FB_CFB_IMAGEBLIT
414 Say Y if you want support with Open Firmware for your graphics
418 bool "Apple \"control\" display support"
419 depends on (FB = y) && PPC_PMAC && PPC32
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
425 This driver supports a frame buffer for the graphics adapter in the
426 Power Macintosh 7300 and others.
429 bool "Apple \"platinum\" display support"
430 depends on (FB = y) && PPC_PMAC && PPC32
431 select FB_CFB_FILLRECT
432 select FB_CFB_COPYAREA
433 select FB_CFB_IMAGEBLIT
436 This driver supports a frame buffer for the "platinum" graphics
437 adapter in some Power Macintoshes.
440 bool "Apple \"valkyrie\" display support"
441 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
442 select FB_CFB_FILLRECT
443 select FB_CFB_COPYAREA
444 select FB_CFB_IMAGEBLIT
447 This driver supports a frame buffer for the "valkyrie" graphics
448 adapter in some Power Macintoshes.
451 bool "Chips 65550 display support"
452 depends on (FB = y) && PPC32
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
457 This is the frame buffer device driver for the Chips & Technologies
458 65550 graphics chip in PowerBooks.
461 bool "Asiliant (Chips) 69000 display support"
462 depends on (FB = y) && PCI
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
467 This is the frame buffer device driver for the Asiliant 69030 chipset
470 bool "IMS Twin Turbo display support"
471 depends on (FB = y) && PCI
472 select FB_CFB_IMAGEBLIT
473 select FB_MACMODES if PPC
475 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
476 many Macintosh and compatible computers.
479 tristate "VGA 16-color graphics support"
480 depends on FB && (X86 || PPC)
481 select FB_CFB_FILLRECT
482 select FB_CFB_COPYAREA
483 select FB_CFB_IMAGEBLIT
485 This is the frame buffer device driver for VGA 16 color graphic
486 cards. Say Y if you have such a card.
488 To compile this driver as a module, choose M here: the
489 module will be called vga16fb.
492 tristate "HP STI frame buffer device support"
493 depends on FB && PARISC
494 select FB_CFB_FILLRECT
495 select FB_CFB_COPYAREA
496 select FB_CFB_IMAGEBLIT
499 STI refers to the HP "Standard Text Interface" which is a set of
500 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
501 Enabling this option will implement the linux framebuffer device
502 using calls to the STI BIOS routines for initialisation.
504 If you enable this option, you will get a planar framebuffer device
505 /dev/fb which will work on the most common HP graphic cards of the
506 NGLE family, including the artist chips (in the 7xx and Bxxx series),
507 HCRX, HCRX24, CRX, CRX24 and VisEG series.
509 It is safe to enable this option, so you should probably say "Y".
512 bool "Generic Macintosh display support"
513 depends on (FB = y) && MAC
514 select FB_CFB_FILLRECT
515 select FB_CFB_COPYAREA
516 select FB_CFB_IMAGEBLIT
519 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
522 depends on (FB = y) && HP300
523 select FB_CFB_FILLRECT
524 select FB_CFB_IMAGEBLIT
528 tristate "TGA framebuffer support"
529 depends on FB && ALPHA
530 select FB_CFB_FILLRECT
531 select FB_CFB_COPYAREA
532 select FB_CFB_IMAGEBLIT
535 This is the frame buffer device driver for generic TGA graphic
536 cards. Say Y if you have one of those.
539 bool "VESA VGA graphics support"
540 depends on (FB = y) && X86
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
546 This is the frame buffer device driver for generic VESA 2.0
547 compliant graphic cards. The older VESA 1.2 cards are not supported.
548 You will get a boot time penguin logo at no additional cost. Please
549 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
552 bool "Intel-based Macintosh Framebuffer Support"
553 depends on (FB = y) && X86 && EFI
554 select FB_CFB_FILLRECT
555 select FB_CFB_COPYAREA
556 select FB_CFB_IMAGEBLIT
558 This is the frame buffer device driver for the Intel-based Macintosh
561 tristate "Hecuba board support"
562 depends on FB && X86 && MMU
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
566 select FB_DEFERRED_IO
568 This enables support for the Hecuba board. This driver was tested
569 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
570 interface (8 bit data, 4 bit control). If you anticpate using
571 this driver, say Y or M; otherwise say N. You must specify the
572 GPIO IO address to be used for setting control and data.
575 tristate "Hercules mono graphics support"
577 select FB_CFB_FILLRECT
578 select FB_CFB_COPYAREA
579 select FB_CFB_IMAGEBLIT
581 Say Y here if you have a Hercules mono graphics card.
583 To compile this driver as a module, choose M here: the
584 module will be called hgafb.
586 As this card technology is 15 years old, most people will answer N
590 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
591 depends on FB_HGA && EXPERIMENTAL
593 This will compile the Hercules mono graphics with
594 acceleration functions.
597 tristate "SGI Visual Workstation framebuffer support"
598 depends on FB && X86_VISWS
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
603 SGI Visual Workstation support for framebuffer graphics.
606 bool "SGI Graphics Backend frame buffer support"
607 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
608 select FB_CFB_FILLRECT
609 select FB_CFB_COPYAREA
610 select FB_CFB_IMAGEBLIT
612 This is the frame buffer device driver for SGI Graphics Backend.
613 This chip is used in SGI O2 and Visual Workstation 320/540.
616 int "Video memory size in MB"
620 This is the amount of memory reserved for the framebuffer,
621 which can be any value between 1MB and 8MB.
624 bool "SBUS and UPA framebuffers"
625 depends on (FB = y) && SPARC
627 Say Y if you want support for SBUS or UPA based frame buffer device.
631 depends on (FB = y) && (SPARC && FB_SBUS)
632 select FB_CFB_FILLRECT
633 select FB_CFB_COPYAREA
634 select FB_CFB_IMAGEBLIT
636 This is the frame buffer device driver for the BWtwo frame buffer.
639 bool "CGthree support"
640 depends on (FB = y) && (SPARC && FB_SBUS)
641 select FB_CFB_FILLRECT
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
645 This is the frame buffer device driver for the CGthree frame buffer.
648 bool "CGsix (GX,TurboGX) support"
649 depends on (FB = y) && (SPARC && FB_SBUS)
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
653 This is the frame buffer device driver for the CGsix (GX, TurboGX)
657 tristate "NEC PowerVR 2 display support"
658 depends on FB && SH_DREAMCAST
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
663 Say Y here if you have a PowerVR 2 card in your box. If you plan to
664 run linux on your Dreamcast, you will have to say Y here.
665 This driver may or may not work on other PowerVR 2 cards, but is
666 totally untested. Use at your own risk. If unsure, say N.
668 To compile this driver as a module, choose M here: the
669 module will be called pvr2fb.
671 You can pass several parameters to the driver at boot time or at
672 module load time. The parameters look like "video=pvr2:XXX", where
673 the meaning of XXX can be found at the end of the main source file
674 (<file:drivers/video/pvr2fb.c>). Please see the file
675 <file:Documentation/fb/pvr2fb.txt>.
678 bool "Epson 1355 framebuffer support"
679 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
680 select FB_CFB_FILLRECT
681 select FB_CFB_COPYAREA
682 select FB_CFB_IMAGEBLIT
684 Build in support for the SED1355 Epson Research Embedded RAMDAC
685 LCD/CRT Controller (since redesignated as the S1D13505) as a
686 framebuffer. Product specs at
687 <http://www.erd.epson.com/vdc/html/products.htm>.
690 tristate "Epson S1D13XXX framebuffer support"
692 select FB_CFB_FILLRECT
693 select FB_CFB_COPYAREA
694 select FB_CFB_IMAGEBLIT
696 Support for S1D13XXX framebuffer device family (currently only
697 working with S1D13806). Product specs at
698 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
701 tristate "nVidia Framebuffer Support"
703 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
704 select FB_MODE_HELPERS
705 select FB_CFB_FILLRECT
706 select FB_CFB_COPYAREA
707 select FB_CFB_IMAGEBLIT
710 This driver supports graphics boards with the nVidia chips, TNT
711 and newer. For very old chipsets, such as the RIVA128, then use
713 Say Y if you have such a graphics board.
715 To compile this driver as a module, choose M here: the
716 module will be called nvidiafb.
719 bool "Enable DDC Support"
723 This enables I2C support for nVidia Chipsets. This is used
724 only for getting EDID information from the attached display
725 allowing for robust video mode handling and switching.
727 Because fbdev-2.6 requires that drivers must be able to
728 independently validate video mode parameters, you should say Y
731 config FB_NVIDIA_BACKLIGHT
732 bool "Support for backlight control"
736 Say Y here if you want to control the backlight of your display.
739 tristate "nVidia Riva support"
741 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
742 select FB_MODE_HELPERS
743 select FB_CFB_FILLRECT
744 select FB_CFB_COPYAREA
745 select FB_CFB_IMAGEBLIT
748 This driver supports graphics boards with the nVidia Riva/Geforce
750 Say Y if you have such a graphics board.
752 To compile this driver as a module, choose M here: the
753 module will be called rivafb.
756 bool "Enable DDC Support"
760 This enables I2C support for nVidia Chipsets. This is used
761 only for getting EDID information from the attached display
762 allowing for robust video mode handling and switching.
764 Because fbdev-2.6 requires that drivers must be able to
765 independently validate video mode parameters, you should say Y
769 bool "Lots of debug output from Riva(nVidia) driver"
773 Say Y here if you want the Riva driver to output all sorts
774 of debugging information to provide to the maintainer when
775 something goes wrong.
777 config FB_RIVA_BACKLIGHT
778 bool "Support for backlight control"
782 Say Y here if you want to control the backlight of your display.
785 tristate "Intel 810/815 support (EXPERIMENTAL)"
786 depends on FB && EXPERIMENTAL && PCI && X86_32
789 select FB_MODE_HELPERS
790 select FB_CFB_FILLRECT
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
794 This driver supports the on-board graphics built in to the Intel 810
795 and 815 chipsets. Say Y if you have and plan to use such a board.
797 To compile this driver as a module, choose M here: the
798 module will be called i810fb.
800 For more information, please read
801 <file:Documentation/fb/intel810.txt>
804 bool "use VESA Generalized Timing Formula"
807 If you say Y, then the VESA standard, Generalized Timing Formula
808 or GTF, will be used to calculate the required video timing values
809 per video mode. Since the GTF allows nondiscrete timings
810 (nondiscrete being a range of values as opposed to discrete being a
811 set of values), you'll be able to use any combination of horizontal
812 and vertical resolutions, and vertical refresh rates without having
813 to specify your own timing parameters. This is especially useful
814 to maximize the performance of an aging display, or if you just
815 have a display with nonstandard dimensions. A VESA compliant
816 monitor is recommended, but can still work with non-compliant ones.
817 If you need or want this, then select this option. The timings may
818 not be compliant with Intel's recommended values. Use at your own
821 If you say N, the driver will revert to discrete video timings
822 using a set recommended by Intel in their documentation.
827 bool "Enable DDC Support"
828 depends on FB_I810 && FB_I810_GTF
833 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
834 depends on FB && EXPERIMENTAL && PCI && X86
837 select FB_MODE_HELPERS
838 select FB_CFB_FILLRECT
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 This driver supports the on-board graphics built in to the Intel
843 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
844 Say Y if you have and plan to use such a board.
846 If you say Y here and want DDC/I2C support you must first say Y to
847 "I2C support" and "I2C bit-banging support" in the character devices
850 If you say M here then "I2C support" and "I2C bit-banging support"
851 can be build either as modules or built-in.
853 To compile this driver as a module, choose M here: the
854 module will be called intelfb.
856 For more information, please read <file:Documentation/fb/intelfb.txt>
858 config FB_INTEL_DEBUG
859 bool "Intel driver Debug Messages"
862 Say Y here if you want the Intel driver to output all sorts
863 of debugging information to provide to the maintainer when
864 something goes wrong.
867 bool "DDC/I2C for Intel framebuffer support"
872 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
875 tristate "Matrox acceleration"
877 select FB_CFB_FILLRECT
878 select FB_CFB_COPYAREA
879 select FB_CFB_IMAGEBLIT
880 select FB_TILEBLITTING
881 select FB_MACMODES if PPC_PMAC
883 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
884 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
885 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
886 Matrox G400, G450 or G550 card in your box.
888 To compile this driver as a module, choose M here: the
889 module will be called matroxfb.
891 You can pass several parameters to the driver at boot time or at
892 module load time. The parameters look like "video=matrox:XXX", and
893 are described in <file:Documentation/fb/matroxfb.txt>.
895 config FB_MATROX_MILLENIUM
896 bool "Millennium I/II support"
899 Say Y here if you have a Matrox Millennium or Matrox Millennium II
900 video card. If you select "Advanced lowlevel driver options" below,
901 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
902 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
903 also use font widths different from 8.
905 config FB_MATROX_MYSTIQUE
906 bool "Mystique support"
909 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
910 video card. If you select "Advanced lowlevel driver options" below,
911 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
912 packed pixel and 32 bpp packed pixel. You can also use font widths
916 bool "G100/G200/G400/G450/G550 support"
919 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
920 video card. If you select "Advanced lowlevel driver options", you
921 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
922 pixel and 32 bpp packed pixel. You can also use font widths
925 If you need support for G400 secondary head, you must first say Y to
926 "I2C support" in the character devices section, and then to
927 "Matrox I2C support" and "G400 second head support" here in the
928 framebuffer section. G450/G550 secondary head and digital output
929 are supported without additional modules.
931 The driver starts in monitor mode. You must use the matroxset tool
932 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
933 swap primary and secondary head outputs, or to change output mode.
934 Secondary head driver always start in 640x480 resolution and you
935 must use fbset to change it.
937 Do not forget that second head supports only 16 and 32 bpp
938 packed pixels, so it is a good idea to compile them into the kernel
939 too. You can use only some font widths, as the driver uses generic
940 painting procedures (the secondary head does not use acceleration
943 G450/G550 hardware can display TV picture only from secondary CRTC,
944 and it performs no scaling, so picture must have 525 or 625 lines.
947 tristate "Matrox I2C support"
951 This drivers creates I2C buses which are needed for accessing the
952 DDC (I2C) bus present on all Matroxes, an I2C bus which
953 interconnects Matrox optional devices, like MGA-TVO on G200 and
954 G400, and the secondary head DDC bus, present on G400 only.
956 You can say Y or M here if you want to experiment with monitor
957 detection code. You must say Y or M here if you want to use either
958 second head of G400 or MGA-TVO on G200 or G400.
960 If you compile it as module, it will create a module named
963 config FB_MATROX_MAVEN
964 tristate "G400 second head support"
965 depends on FB_MATROX_G && FB_MATROX_I2C
967 WARNING !!! This support does not work with G450 !!!
969 Say Y or M here if you want to use a secondary head (meaning two
970 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
971 head is not compatible with accelerated XFree 3.3.x SVGA servers -
972 secondary head output is blanked while you are in X. With XFree
973 3.9.17 preview you can use both heads if you use SVGA over fbdev or
974 the fbdev driver on first head and the fbdev driver on second head.
976 If you compile it as module, two modules are created,
977 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
978 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
979 also load i2c-matroxfb to get it to run.
981 The driver starts in monitor mode and you must use the matroxset
983 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
984 PAL or NTSC or to swap primary and secondary head outputs.
985 Secondary head driver also always start in 640x480 resolution, you
986 must use fbset to change it.
988 Also do not forget that second head supports only 16 and 32 bpp
989 packed pixels, so it is a good idea to compile them into the kernel
990 too. You can use only some font widths, as the driver uses generic
991 painting procedures (the secondary head does not use acceleration
994 config FB_MATROX_MULTIHEAD
995 bool "Multihead support"
998 Say Y here if you have more than one (supported) Matrox device in
999 your computer and you want to use all of them for different monitors
1000 ("multihead"). If you have only one device, you should say N because
1001 the driver compiled with Y is larger and a bit slower, especially on
1004 If you said M to "Matrox unified accelerated driver" and N here, you
1005 will still be able to use several Matrox devices simultaneously:
1006 insert several instances of the module matroxfb into the kernel
1007 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1008 for the different Matrox devices. This method is slightly faster but
1009 uses 40 KB of kernel memory per Matrox card.
1011 There is no need for enabling 'Matrox multihead support' if you have
1012 only one Matrox card in the box.
1015 tristate "ATI Radeon display support"
1016 depends on FB && PCI
1017 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1018 select FB_MODE_HELPERS
1019 select FB_CFB_FILLRECT
1020 select FB_CFB_COPYAREA
1021 select FB_CFB_IMAGEBLIT
1022 select FB_MACMODES if PPC_OF
1024 Choose this option if you want to use an ATI Radeon graphics card as
1025 a framebuffer device. There are both PCI and AGP versions. You
1026 don't need to choose this to run the Radeon in plain VGA mode.
1028 If you say Y here and want DDC/I2C support you must first say Y to
1029 "I2C support" and "I2C bit-banging support" in the character devices
1032 If you say M here then "I2C support" and "I2C bit-banging support"
1033 can be build either as modules or built-in.
1035 There is a product page at
1036 http://apps.ati.com/ATIcompare/
1038 config FB_RADEON_I2C
1039 bool "DDC/I2C for ATI Radeon support"
1040 depends on FB_RADEON
1044 Say Y here if you want DDC/I2C support for your Radeon board.
1046 config FB_RADEON_BACKLIGHT
1047 bool "Support for backlight control"
1048 depends on FB_RADEON
1051 Say Y here if you want to control the backlight of your display.
1053 config FB_RADEON_DEBUG
1054 bool "Lots of debug output from Radeon driver"
1055 depends on FB_RADEON
1058 Say Y here if you want the Radeon driver to output all sorts
1059 of debugging information to provide to the maintainer when
1060 something goes wrong.
1063 tristate "ATI Rage128 display support"
1064 depends on FB && PCI
1065 select FB_CFB_FILLRECT
1066 select FB_CFB_COPYAREA
1067 select FB_CFB_IMAGEBLIT
1068 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1069 select FB_MACMODES if PPC_PMAC
1071 This driver supports graphics boards with the ATI Rage128 chips.
1072 Say Y if you have such a graphics board and read
1073 <file:Documentation/fb/aty128fb.txt>.
1075 To compile this driver as a module, choose M here: the
1076 module will be called aty128fb.
1078 config FB_ATY128_BACKLIGHT
1079 bool "Support for backlight control"
1080 depends on FB_ATY128
1083 Say Y here if you want to control the backlight of your display.
1086 tristate "ATI Mach64 display support" if PCI || ATARI
1087 depends on FB && !SPARC32
1088 select FB_CFB_FILLRECT
1089 select FB_CFB_COPYAREA
1090 select FB_CFB_IMAGEBLIT
1091 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1092 select FB_MACMODES if PPC
1094 This driver supports graphics boards with the ATI Mach64 chips.
1095 Say Y if you have such a graphics board.
1097 To compile this driver as a module, choose M here: the
1098 module will be called atyfb.
1101 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1102 depends on PCI && FB_ATY
1103 default y if SPARC64 && FB_PCI
1105 Say Y here to support use of ATI's 64-bit Rage boards (or other
1106 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1107 framebuffer device. The ATI product support page for these boards
1108 is at <http://support.ati.com/products/pc/mach64/>.
1110 config FB_ATY_GENERIC_LCD
1111 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1112 depends on FB_ATY_CT
1114 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1115 Rage XC, or Rage XL chipset.
1118 bool "Mach64 GX support" if PCI
1122 Say Y here to support use of the ATI Mach64 Graphics Expression
1123 board (or other boards based on the Mach64 GX chipset) as a
1124 framebuffer device. The ATI product support page for these boards
1126 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1128 config FB_ATY_BACKLIGHT
1129 bool "Support for backlight control"
1133 Say Y here if you want to control the backlight of your display.
1136 tristate "S3 Trio/Virge support"
1137 depends on FB && PCI
1138 select FB_CFB_FILLRECT
1139 select FB_CFB_COPYAREA
1140 select FB_CFB_IMAGEBLIT
1141 select FB_TILEBLITTING
1144 Driver for graphics boards with S3 Trio / S3 Virge chip.
1147 tristate "S3 Savage support"
1148 depends on FB && PCI && EXPERIMENTAL
1149 select FB_MODE_HELPERS
1150 select FB_CFB_FILLRECT
1151 select FB_CFB_COPYAREA
1152 select FB_CFB_IMAGEBLIT
1154 This driver supports notebooks and computers with S3 Savage PCI/AGP
1157 Say Y if you have such a graphics card.
1159 To compile this driver as a module, choose M here; the module
1160 will be called savagefb.
1162 config FB_SAVAGE_I2C
1163 bool "Enable DDC2 Support"
1164 depends on FB_SAVAGE
1167 This enables I2C support for S3 Savage Chipsets. This is used
1168 only for getting EDID information from the attached display
1169 allowing for robust video mode handling and switching.
1171 Because fbdev-2.6 requires that drivers must be able to
1172 independently validate video mode parameters, you should say Y
1175 config FB_SAVAGE_ACCEL
1176 bool "Enable Console Acceleration"
1177 depends on FB_SAVAGE
1180 This option will compile in console acceleration support. If
1181 the resulting framebuffer console has bothersome glitches, then
1185 tristate "SiS/XGI display support"
1186 depends on FB && PCI
1187 select FB_CFB_FILLRECT
1188 select FB_CFB_COPYAREA
1189 select FB_CFB_IMAGEBLIT
1191 This is the frame buffer device driver for the SiS 300, 315, 330
1192 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1193 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1195 To compile this driver as a module, choose M here; the module
1196 will be called sisfb.
1199 bool "SiS 300 series support"
1202 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1205 bool "SiS 315/330/340 series and XGI support"
1208 Say Y here to support use of the SiS 315, 330 and 340 series
1209 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1210 as XGI V3XT, V5, V8 and Z7.
1213 tristate "NeoMagic display support"
1214 depends on FB && PCI
1215 select FB_MODE_HELPERS
1216 select FB_CFB_FILLRECT
1217 select FB_CFB_COPYAREA
1218 select FB_CFB_IMAGEBLIT
1220 This driver supports notebooks with NeoMagic PCI chips.
1221 Say Y if you have such a graphics card.
1223 To compile this driver as a module, choose M here: the
1224 module will be called neofb.
1227 tristate "IMG Kyro support"
1228 depends on FB && PCI
1229 select FB_CFB_FILLRECT
1230 select FB_CFB_COPYAREA
1231 select FB_CFB_IMAGEBLIT
1233 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1236 To compile this driver as a module, choose M here: the
1237 module will be called kyrofb.
1240 tristate "3Dfx Banshee/Voodoo3 display support"
1241 depends on FB && PCI
1242 select FB_CFB_IMAGEBLIT
1243 select FB_CFB_FILLRECT
1244 select FB_CFB_COPYAREA
1246 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1247 chips. Say Y if you have such a graphics board.
1249 To compile this driver as a module, choose M here: the
1250 module will be called tdfxfb.
1252 config FB_3DFX_ACCEL
1253 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1254 depends on FB_3DFX && EXPERIMENTAL
1256 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1257 with acceleration functions.
1261 tristate "3Dfx Voodoo Graphics (sst1) support"
1262 depends on FB && PCI
1263 select FB_CFB_FILLRECT
1264 select FB_CFB_COPYAREA
1265 select FB_CFB_IMAGEBLIT
1267 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1268 Voodoo2 (cvg) based graphics card.
1270 To compile this driver as a module, choose M here: the
1271 module will be called sstfb.
1273 WARNING: Do not use any application that uses the 3D engine
1274 (namely glide) while using this driver.
1275 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1276 options and other important info support.
1279 tristate "Cyberblade/i1 support"
1280 depends on FB && PCI && X86_32 && !64BIT
1281 select FB_CFB_IMAGEBLIT
1284 This driver is supposed to support the Trident Cyberblade/i1
1285 graphics core integrated in the VIA VT8601A North Bridge,
1286 also known as VIA Apollo PLE133.
1289 - Developed, tested and working on EPIA 5000 and EPIA 800.
1290 - Does work reliable on all systems with CRT/LCD connected to
1292 - Should work on systems that do use the internal LCD port, but
1293 this is absolutely not tested.
1295 Character imageblit, copyarea and rectangle fill are hw accelerated,
1296 ypan scrolling is used by default.
1298 Please do read <file:Documentation/fb/cyblafb/*>.
1300 To compile this driver as a module, choose M here: the
1301 module will be called cyblafb.
1304 tristate "Trident support"
1305 depends on FB && PCI
1306 select FB_CFB_FILLRECT
1307 select FB_CFB_COPYAREA
1308 select FB_CFB_IMAGEBLIT
1310 This driver is supposed to support graphics boards with the
1311 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1312 but also on some motherboards. For more information, read
1313 <file:Documentation/fb/tridentfb.txt>
1315 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1318 Say Y if you have such a graphics board.
1321 To compile this driver as a module, choose M here: the
1322 module will be called tridentfb.
1324 config FB_TRIDENT_ACCEL
1325 bool "Trident Acceleration functions (EXPERIMENTAL)"
1326 depends on FB_TRIDENT && EXPERIMENTAL
1328 This will compile the Trident frame buffer device with
1329 acceleration functions.
1332 tristate "Permedia3 support"
1333 depends on FB && PCI && BROKEN
1335 This is the frame buffer device driver for the 3DLabs Permedia3
1336 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1337 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1338 and maybe other boards.
1341 bool "Au1100 LCD Driver"
1342 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1345 bool "Au1200 LCD Driver"
1346 depends on (FB = y) && MIPS && SOC_AU1200
1347 select FB_CFB_FILLRECT
1348 select FB_CFB_COPYAREA
1349 select FB_CFB_IMAGEBLIT
1351 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1352 various panels and CRTs by passing in kernel cmd line option
1353 au1200fb:panel=<name>.
1355 source "drivers/video/geode/Kconfig"
1358 bool "Creator/Creator3D/Elite3D support"
1359 depends on FB_SBUS && SPARC64
1360 select FB_CFB_COPYAREA
1361 select FB_CFB_IMAGEBLIT
1363 This is the frame buffer device driver for the Creator, Creator3D,
1364 and Elite3D graphics boards.
1367 bool "TCX (SS4/SS5 only) support"
1369 select FB_CFB_FILLRECT
1370 select FB_CFB_COPYAREA
1371 select FB_CFB_IMAGEBLIT
1373 This is the frame buffer device driver for the TCX 24/8bit frame
1377 bool "CGfourteen (SX) support"
1379 select FB_CFB_FILLRECT
1380 select FB_CFB_COPYAREA
1381 select FB_CFB_IMAGEBLIT
1383 This is the frame buffer device driver for the CGfourteen frame
1384 buffer on Desktop SPARCsystems with the SX graphics option.
1387 bool "P9100 (Sparcbook 3 only) support"
1389 select FB_CFB_FILLRECT
1390 select FB_CFB_COPYAREA
1391 select FB_CFB_IMAGEBLIT
1393 This is the frame buffer device driver for the P9100 card
1394 supported on Sparcbook 3 machines.
1397 bool "Leo (ZX) support"
1399 select FB_CFB_FILLRECT
1400 select FB_CFB_COPYAREA
1401 select FB_CFB_IMAGEBLIT
1403 This is the frame buffer device driver for the SBUS-based Sun ZX
1404 (leo) frame buffer cards.
1407 bool "Sun XVR-500 3DLABS Wildcat support"
1408 depends on FB && PCI && SPARC64
1409 select FB_CFB_FILLRECT
1410 select FB_CFB_COPYAREA
1411 select FB_CFB_IMAGEBLIT
1413 This is the framebuffer device for the Sun XVR-500 and similar
1414 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1415 only works on sparc64 systems where the system firwmare has
1416 mostly initialized the card already. It is treated as a
1417 completely dumb framebuffer device.
1420 bool "Sun XVR-2500 3DLABS Wildcat support"
1421 depends on FB && PCI && SPARC64
1422 select FB_CFB_FILLRECT
1423 select FB_CFB_COPYAREA
1424 select FB_CFB_IMAGEBLIT
1426 This is the framebuffer device for the Sun XVR-2500 and similar
1427 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1428 only works on sparc64 systems where the system firwmare has
1429 mostly initialized the card already. It is treated as a
1430 completely dumb framebuffer device.
1433 bool "PCI framebuffers"
1434 depends on (FB = y) && PCI && SPARC
1437 bool "IGA 168x display support"
1438 depends on SPARC32 && FB_PCI
1439 select FB_CFB_FILLRECT
1440 select FB_CFB_COPYAREA
1441 select FB_CFB_IMAGEBLIT
1443 This is the framebuffer device for the INTERGRAPHICS 1680 and
1444 successor frame buffer cards.
1447 tristate "HD64461 Frame Buffer support"
1448 depends on FB && HD64461
1449 select FB_CFB_FILLRECT
1450 select FB_CFB_COPYAREA
1451 select FB_CFB_IMAGEBLIT
1453 This is the frame buffer device driver for the Hitachi HD64461 LCD
1457 bool "PMAG-AA TURBOchannel framebuffer support"
1458 depends on (FB = y) && TC
1459 select FB_CFB_FILLRECT
1460 select FB_CFB_COPYAREA
1461 select FB_CFB_IMAGEBLIT
1463 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1464 used mainly in the MIPS-based DECstation series.
1467 tristate "PMAG-BA TURBOchannel framebuffer support"
1469 select FB_CFB_FILLRECT
1470 select FB_CFB_COPYAREA
1471 select FB_CFB_IMAGEBLIT
1473 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1474 used mainly in the MIPS-based DECstation series.
1477 tristate "PMAGB-B TURBOchannel framebuffer support"
1479 select FB_CFB_FILLRECT
1480 select FB_CFB_COPYAREA
1481 select FB_CFB_IMAGEBLIT
1483 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1484 in the MIPS-based DECstation series. The card is currently only
1485 supported in 1280x1024x8 mode.
1488 bool "Maxine (Personal DECstation) onboard framebuffer support"
1489 depends on (FB = y) && MACH_DECSTATION
1490 select FB_CFB_FILLRECT
1491 select FB_CFB_COPYAREA
1492 select FB_CFB_IMAGEBLIT
1494 Support for the onboard framebuffer (1024x768x8) in the Personal
1495 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1499 bool "TMPTX3912/PR31700 frame buffer support"
1500 depends on (FB = y) && NINO
1501 select FB_CFB_FILLRECT
1502 select FB_CFB_COPYAREA
1503 select FB_CFB_IMAGEBLIT
1505 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1506 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1508 Say Y here to enable kernel support for the on-board framebuffer.
1511 bool "G364 frame buffer support"
1512 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1513 select FB_CFB_FILLRECT
1514 select FB_CFB_COPYAREA
1515 select FB_CFB_IMAGEBLIT
1517 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1518 Olivetti M700-10 systems.
1521 bool "Motorola 68328 native frame buffer support"
1522 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1523 select FB_CFB_FILLRECT
1524 select FB_CFB_COPYAREA
1525 select FB_CFB_IMAGEBLIT
1527 Say Y here if you want to support the built-in frame buffer of
1528 the Motorola 68328 CPU family.
1531 tristate "PXA LCD framebuffer support"
1532 depends on FB && ARCH_PXA
1533 select FB_CFB_FILLRECT
1534 select FB_CFB_COPYAREA
1535 select FB_CFB_IMAGEBLIT
1537 Frame buffer driver for the built-in LCD controller in the Intel
1540 This driver is also available as a module ( = code which can be
1541 inserted and removed from the running kernel whenever you want). The
1542 module will be called pxafb. If you want to compile it as a module,
1543 say M here and read <file:Documentation/kbuild/modules.txt>.
1547 config FB_PXA_PARAMETERS
1548 bool "PXA LCD command line parameters"
1552 Enable the use of kernel command line or module parameters
1553 to configure the physical properties of the LCD panel when
1554 using the PXA LCD driver.
1556 This option allows you to override the panel parameters
1557 supplied by the platform in order to support multiple
1558 different models of flatpanel. If you will only be using a
1559 single model of flatpanel then you can safely leave this
1562 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1565 tristate "2700G LCD framebuffer support"
1566 depends on FB && ARCH_PXA
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1571 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1575 bool "Enable debugging info via debugfs"
1576 depends on FB_MBX && DEBUG_FS
1579 Enable this if you want debugging information using the debug
1580 filesystem (debugfs)
1585 tristate "W100 frame buffer support"
1586 depends on FB && PXA_SHARPSL
1587 select FB_CFB_FILLRECT
1588 select FB_CFB_COPYAREA
1589 select FB_CFB_IMAGEBLIT
1591 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1593 This driver is also available as a module ( = code which can be
1594 inserted and removed from the running kernel whenever you want). The
1595 module will be called w100fb. If you want to compile it as a module,
1596 say M here and read <file:Documentation/kbuild/modules.txt>.
1601 tristate "S3C2410 LCD framebuffer support"
1602 depends on FB && ARCH_S3C2410
1603 select FB_CFB_FILLRECT
1604 select FB_CFB_COPYAREA
1605 select FB_CFB_IMAGEBLIT
1607 Frame buffer driver for the built-in LCD controller in the Samsung
1610 This driver is also available as a module ( = code which can be
1611 inserted and removed from the running kernel whenever you want). The
1612 module will be called s3c2410fb. If you want to compile it as a module,
1613 say M here and read <file:Documentation/kbuild/modules.txt>.
1616 config FB_S3C2410_DEBUG
1617 bool "S3C2410 lcd debug messages"
1618 depends on FB_S3C2410
1620 Turn on debugging messages. Note that you can set/unset at run time
1624 tristate "Silicon Motion SM501 framebuffer support"
1625 depends on FB && MFD_SM501
1626 select FB_CFB_FILLRECT
1627 select FB_CFB_COPYAREA
1628 select FB_CFB_IMAGEBLIT
1630 Frame buffer driver for the CRT and LCD controllers in the Silicon
1633 This driver is also available as a module ( = code which can be
1634 inserted and removed from the running kernel whenever you want). The
1635 module will be called sm501fb. If you want to compile it as a module,
1636 say M here and read <file:Documentation/modules.txt>.
1641 config FB_PNX4008_DUM
1642 tristate "Display Update Module support on Philips PNX4008 board"
1643 depends on FB && ARCH_PNX4008
1645 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1647 config FB_PNX4008_DUM_RGB
1648 tristate "RGB Framebuffer support on Philips PNX4008 board"
1649 depends on FB_PNX4008_DUM
1650 select FB_CFB_FILLRECT
1651 select FB_CFB_COPYAREA
1652 select FB_CFB_IMAGEBLIT
1654 Say Y here to enable support for PNX4008 RGB Framebuffer
1656 config FB_IBM_GXT4500
1657 tristate "Framebuffer support for IBM GXT4500P adaptor"
1659 select FB_CFB_FILLRECT
1660 select FB_CFB_COPYAREA
1661 select FB_CFB_IMAGEBLIT
1663 Say Y here to enable support for the IBM GXT4500P display
1664 adaptor, found on some IBM System P (pSeries) machines.
1667 bool "PS3 GPU framebuffer driver"
1668 depends on (FB = y) && PS3_PS3AV
1669 select FB_CFB_FILLRECT
1670 select FB_CFB_COPYAREA
1671 select FB_CFB_IMAGEBLIT
1673 Include support for the virtual frame buffer in the PS3 platform.
1675 config FB_PS3_DEFAULT_SIZE_M
1676 int "PS3 default frame buffer size (in MiB)"
1680 This is the default size (in MiB) of the virtual frame buffer in
1682 The default value can be overridden on the kernel command line
1683 using the "ps3fb" option (e.g. "ps3fb=9M");
1686 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1692 This is a `virtual' frame buffer device. It operates on a chunk of
1693 unswappable kernel memory instead of on the memory of a graphics
1694 board. This means you cannot see any output sent to this frame
1695 buffer device, while it does consume precious memory. The main use
1696 of this frame buffer device is testing and debugging the frame
1697 buffer subsystem. Do NOT enable it for normal systems! To protect
1698 the innocent, it has to be enabled explicitly at boot time using the
1699 kernel option `video=vfb:'.
1701 To compile this driver as a module, choose M here: the
1702 module will be called vfb. In order to load it, you must use
1703 the vfb_enable=1 option.
1708 source "drivers/video/console/Kconfig"
1711 if FB || SGI_NEWPORT_CONSOLE
1712 source "drivers/video/logo/Kconfig"