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 tristate "Amiga CyberVision 64 support"
359 depends on FB && ZORRO && BROKEN
360 select FB_CFB_FILLRECT
361 select FB_CFB_COPYAREA
362 select FB_CFB_IMAGEBLIT
364 This enables support for the Cybervision 64 graphics card from
365 Phase5. Please note that its use is not all that intuitive (i.e. if
366 you have any questions, be sure to ask!). Say N unless you have a
367 Cybervision 64 or plan to get one before you next recompile the
368 kernel. Please note that this driver DOES NOT support the
369 Cybervision 64/3D card, as they use incompatible video chips.
372 bool "Amiga CyberVision 64/3D support "
373 depends on (FB = y) && ZORRO && BROKEN
374 select FB_CFB_FILLRECT
375 select FB_CFB_COPYAREA
376 select FB_CFB_IMAGEBLIT
378 This enables support for the Cybervision 64/3D graphics card from
379 Phase5. Please note that its use is not all that intuitive (i.e. if
380 you have any questions, be sure to ask!). Say N unless you have a
381 Cybervision 64/3D or plan to get one before you next recompile the
382 kernel. Please note that this driver DOES NOT support the older
383 Cybervision 64 card, as they use incompatible video chips.
386 tristate "Amiga Retina Z3 support"
387 depends on (FB = y) && ZORRO && BROKEN
389 This enables support for the Retina Z3 graphics card. Say N unless
390 you have a Retina Z3 or plan to get one before you next recompile
394 bool "Amiga FrameMaster II/Rainbow II support"
395 depends on (FB = y) && ZORRO
396 select FB_CFB_FILLRECT
397 select FB_CFB_COPYAREA
398 select FB_CFB_IMAGEBLIT
400 This is the frame buffer device driver for the Amiga FrameMaster
401 card from BSC (exhibited 1992 but not shipped as a CBM product).
404 tristate "Arc Monochrome LCD board support"
406 select FB_CFB_FILLRECT
407 select FB_CFB_COPYAREA
408 select FB_CFB_IMAGEBLIT
410 This enables support for the Arc Monochrome LCD board. The board
411 is based on the KS-108 lcd controller and is typically a matrix
412 of 2*n chips. This driver was tested with a 128x64 panel. This
413 driver supports it for use with x86 SBCs through a 16 bit GPIO
414 interface (8 bit data, 8 bit control). If you anticipate using
415 this driver, say Y or M; otherwise say N. You must specify the
416 GPIO IO address to be used for setting control and data.
419 bool "Atari native chipset support"
420 depends on (FB = y) && ATARI && BROKEN
422 This is the frame buffer device driver for the builtin graphics
423 chipset found in Ataris.
426 bool "Open Firmware frame buffer device support"
427 depends on (FB = y) && (PPC64 || PPC_OF)
428 select FB_CFB_FILLRECT
429 select FB_CFB_COPYAREA
430 select FB_CFB_IMAGEBLIT
433 Say Y if you want support with Open Firmware for your graphics
437 bool "Apple \"control\" display support"
438 depends on (FB = y) && PPC_PMAC && PPC32
439 select FB_CFB_FILLRECT
440 select FB_CFB_COPYAREA
441 select FB_CFB_IMAGEBLIT
444 This driver supports a frame buffer for the graphics adapter in the
445 Power Macintosh 7300 and others.
448 bool "Apple \"platinum\" display support"
449 depends on (FB = y) && PPC_PMAC && PPC32
450 select FB_CFB_FILLRECT
451 select FB_CFB_COPYAREA
452 select FB_CFB_IMAGEBLIT
455 This driver supports a frame buffer for the "platinum" graphics
456 adapter in some Power Macintoshes.
459 bool "Apple \"valkyrie\" display support"
460 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
461 select FB_CFB_FILLRECT
462 select FB_CFB_COPYAREA
463 select FB_CFB_IMAGEBLIT
466 This driver supports a frame buffer for the "valkyrie" graphics
467 adapter in some Power Macintoshes.
470 bool "Chips 65550 display support"
471 depends on (FB = y) && PPC32
472 select FB_CFB_FILLRECT
473 select FB_CFB_COPYAREA
474 select FB_CFB_IMAGEBLIT
476 This is the frame buffer device driver for the Chips & Technologies
477 65550 graphics chip in PowerBooks.
480 bool "Asiliant (Chips) 69000 display support"
481 depends on (FB = y) && PCI
482 select FB_CFB_FILLRECT
483 select FB_CFB_COPYAREA
484 select FB_CFB_IMAGEBLIT
486 This is the frame buffer device driver for the Asiliant 69030 chipset
489 bool "IMS Twin Turbo display support"
490 depends on (FB = y) && PCI
491 select FB_CFB_IMAGEBLIT
492 select FB_MACMODES if PPC
494 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
495 many Macintosh and compatible computers.
498 tristate "VGA 16-color graphics support"
499 depends on FB && (X86 || PPC)
500 select FB_CFB_FILLRECT
501 select FB_CFB_COPYAREA
502 select FB_CFB_IMAGEBLIT
504 This is the frame buffer device driver for VGA 16 color graphic
505 cards. Say Y if you have such a card.
507 To compile this driver as a module, choose M here: the
508 module will be called vga16fb.
511 tristate "HP STI frame buffer device support"
512 depends on FB && PARISC
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
518 STI refers to the HP "Standard Text Interface" which is a set of
519 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
520 Enabling this option will implement the linux framebuffer device
521 using calls to the STI BIOS routines for initialisation.
523 If you enable this option, you will get a planar framebuffer device
524 /dev/fb which will work on the most common HP graphic cards of the
525 NGLE family, including the artist chips (in the 7xx and Bxxx series),
526 HCRX, HCRX24, CRX, CRX24 and VisEG series.
528 It is safe to enable this option, so you should probably say "Y".
531 bool "Generic Macintosh display support"
532 depends on (FB = y) && MAC
533 select FB_CFB_FILLRECT
534 select FB_CFB_COPYAREA
535 select FB_CFB_IMAGEBLIT
538 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
541 depends on (FB = y) && HP300
542 select FB_CFB_FILLRECT
543 select FB_CFB_IMAGEBLIT
547 tristate "TGA framebuffer support"
548 depends on FB && ALPHA
549 select FB_CFB_FILLRECT
550 select FB_CFB_COPYAREA
551 select FB_CFB_IMAGEBLIT
554 This is the frame buffer device driver for generic TGA graphic
555 cards. Say Y if you have one of those.
558 bool "VESA VGA graphics support"
559 depends on (FB = y) && X86
560 select FB_CFB_FILLRECT
561 select FB_CFB_COPYAREA
562 select FB_CFB_IMAGEBLIT
565 This is the frame buffer device driver for generic VESA 2.0
566 compliant graphic cards. The older VESA 1.2 cards are not supported.
567 You will get a boot time penguin logo at no additional cost. Please
568 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
571 bool "Intel-based Macintosh Framebuffer Support"
572 depends on (FB = y) && X86 && EFI
573 select FB_CFB_FILLRECT
574 select FB_CFB_COPYAREA
575 select FB_CFB_IMAGEBLIT
577 This is the frame buffer device driver for the Intel-based Macintosh
580 tristate "Hercules mono graphics support"
582 select FB_CFB_FILLRECT
583 select FB_CFB_COPYAREA
584 select FB_CFB_IMAGEBLIT
586 Say Y here if you have a Hercules mono graphics card.
588 To compile this driver as a module, choose M here: the
589 module will be called hgafb.
591 As this card technology is 15 years old, most people will answer N
595 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
596 depends on FB_HGA && EXPERIMENTAL
598 This will compile the Hercules mono graphics with
599 acceleration functions.
602 tristate "SGI Visual Workstation framebuffer support"
603 depends on FB && X86_VISWS
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 SGI Visual Workstation support for framebuffer graphics.
611 bool "SGI Graphics Backend frame buffer support"
612 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
613 select FB_CFB_FILLRECT
614 select FB_CFB_COPYAREA
615 select FB_CFB_IMAGEBLIT
617 This is the frame buffer device driver for SGI Graphics Backend.
618 This chip is used in SGI O2 and Visual Workstation 320/540.
621 int "Video memory size in MB"
625 This is the amount of memory reserved for the framebuffer,
626 which can be any value between 1MB and 8MB.
629 bool "Sun3 framebuffer support"
630 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
633 bool "SBUS and UPA framebuffers"
634 depends on (FB = y) && SPARC
636 Say Y if you want support for SBUS or UPA based frame buffer device.
640 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
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 BWtwo frame buffer.
648 bool "CGthree support"
649 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
654 This is the frame buffer device driver for the CGthree frame buffer.
657 bool "CGsix (GX,TurboGX) support"
658 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
659 select FB_CFB_COPYAREA
660 select FB_CFB_IMAGEBLIT
662 This is the frame buffer device driver for the CGsix (GX, TurboGX)
666 tristate "NEC PowerVR 2 display support"
667 depends on FB && SH_DREAMCAST
668 select FB_CFB_FILLRECT
669 select FB_CFB_COPYAREA
670 select FB_CFB_IMAGEBLIT
672 Say Y here if you have a PowerVR 2 card in your box. If you plan to
673 run linux on your Dreamcast, you will have to say Y here.
674 This driver may or may not work on other PowerVR 2 cards, but is
675 totally untested. Use at your own risk. If unsure, say N.
677 To compile this driver as a module, choose M here: the
678 module will be called pvr2fb.
680 You can pass several parameters to the driver at boot time or at
681 module load time. The parameters look like "video=pvr2:XXX", where
682 the meaning of XXX can be found at the end of the main source file
683 (<file:drivers/video/pvr2fb.c>). Please see the file
684 <file:Documentation/fb/pvr2fb.txt>.
687 bool "Epson 1355 framebuffer support"
688 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
693 Build in support for the SED1355 Epson Research Embedded RAMDAC
694 LCD/CRT Controller (since redesignated as the S1D13505) as a
695 framebuffer. Product specs at
696 <http://www.erd.epson.com/vdc/html/products.htm>.
699 tristate "Epson S1D13XXX framebuffer support"
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
705 Support for S1D13XXX framebuffer device family (currently only
706 working with S1D13806). Product specs at
707 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
710 tristate "nVidia Framebuffer Support"
712 select I2C_ALGOBIT if FB_NVIDIA_I2C
713 select I2C if FB_NVIDIA_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 chips, TNT
721 and newer. For very old chipsets, such as the RIVA128, then use
723 Say Y if you have such a graphics board.
725 To compile this driver as a module, choose M here: the
726 module will be called nvidiafb.
729 bool "Enable DDC Support"
732 This enables I2C support for nVidia Chipsets. This is used
733 only for getting EDID information from the attached display
734 allowing for robust video mode handling and switching.
736 Because fbdev-2.6 requires that drivers must be able to
737 independently validate video mode parameters, you should say Y
740 config FB_NVIDIA_BACKLIGHT
741 bool "Support for backlight control"
742 depends on FB_NVIDIA && PMAC_BACKLIGHT
746 Say Y here if you want to control the backlight of your display.
749 tristate "nVidia Riva support"
751 select I2C_ALGOBIT if FB_RIVA_I2C
752 select I2C if FB_RIVA_I2C
753 select FB_DDC if FB_RIVA_I2C
754 select FB_MODE_HELPERS
755 select FB_CFB_FILLRECT
756 select FB_CFB_COPYAREA
757 select FB_CFB_IMAGEBLIT
760 This driver supports graphics boards with the nVidia Riva/Geforce
762 Say Y if you have such a graphics board.
764 To compile this driver as a module, choose M here: the
765 module will be called rivafb.
768 bool "Enable DDC Support"
771 This enables I2C support for nVidia Chipsets. This is used
772 only for getting EDID information from the attached display
773 allowing for robust video mode handling and switching.
775 Because fbdev-2.6 requires that drivers must be able to
776 independently validate video mode parameters, you should say Y
780 bool "Lots of debug output from Riva(nVidia) driver"
784 Say Y here if you want the Riva driver to output all sorts
785 of debugging information to provide to the maintainer when
786 something goes wrong.
788 config FB_RIVA_BACKLIGHT
789 bool "Support for backlight control"
790 depends on FB_RIVA && PMAC_BACKLIGHT
794 Say Y here if you want to control the backlight of your display.
797 tristate "Intel 810/815 support (EXPERIMENTAL)"
798 depends on FB && EXPERIMENTAL && PCI && X86_32
801 select FB_MODE_HELPERS
802 select FB_CFB_FILLRECT
803 select FB_CFB_COPYAREA
804 select FB_CFB_IMAGEBLIT
806 This driver supports the on-board graphics built in to the Intel 810
807 and 815 chipsets. Say Y if you have and plan to use such a board.
809 To compile this driver as a module, choose M here: the
810 module will be called i810fb.
812 For more information, please read
813 <file:Documentation/fb/intel810.txt>
816 bool "use VESA Generalized Timing Formula"
819 If you say Y, then the VESA standard, Generalized Timing Formula
820 or GTF, will be used to calculate the required video timing values
821 per video mode. Since the GTF allows nondiscrete timings
822 (nondiscrete being a range of values as opposed to discrete being a
823 set of values), you'll be able to use any combination of horizontal
824 and vertical resolutions, and vertical refresh rates without having
825 to specify your own timing parameters. This is especially useful
826 to maximize the performance of an aging display, or if you just
827 have a display with nonstandard dimensions. A VESA compliant
828 monitor is recommended, but can still work with non-compliant ones.
829 If you need or want this, then select this option. The timings may
830 not be compliant with Intel's recommended values. Use at your own
833 If you say N, the driver will revert to discrete video timings
834 using a set recommended by Intel in their documentation.
839 bool "Enable DDC Support"
840 depends on FB_I810 && FB_I810_GTF
847 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
848 depends on FB && EXPERIMENTAL && PCI && X86
851 select I2C_ALGOBIT if FB_INTEL_I2C
852 select I2C if FB_INTEL_I2C
853 select FB_MODE_HELPERS
854 select FB_CFB_FILLRECT
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This driver supports the on-board graphics built in to the Intel
859 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
860 Say Y if you have and plan to use such a board.
862 If you say Y here and want DDC/I2C support you must first say Y to
863 "I2C support" and "I2C bit-banging support" in the character devices
866 If you say M here then "I2C support" and "I2C bit-banging support"
867 can be build either as modules or built-in.
869 To compile this driver as a module, choose M here: the
870 module will be called intelfb.
872 For more information, please read <file:Documentation/fb/intelfb.txt>
874 config FB_INTEL_DEBUG
875 bool "Intel driver Debug Messages"
878 Say Y here if you want the Intel driver to output all sorts
879 of debugging information to provide to the maintainer when
880 something goes wrong.
883 bool "DDC/I2C for Intel framebuffer support"
887 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
890 tristate "Matrox acceleration"
892 select FB_CFB_FILLRECT
893 select FB_CFB_COPYAREA
894 select FB_CFB_IMAGEBLIT
895 select FB_TILEBLITTING
896 select FB_MACMODES if PPC_PMAC
898 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
899 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
900 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
901 Matrox G400, G450 or G550 card in your box.
903 To compile this driver as a module, choose M here: the
904 module will be called matroxfb.
906 You can pass several parameters to the driver at boot time or at
907 module load time. The parameters look like "video=matrox:XXX", and
908 are described in <file:Documentation/fb/matroxfb.txt>.
910 config FB_MATROX_MILLENIUM
911 bool "Millennium I/II support"
914 Say Y here if you have a Matrox Millennium or Matrox Millennium II
915 video card. If you select "Advanced lowlevel driver options" below,
916 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
917 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
918 also use font widths different from 8.
920 config FB_MATROX_MYSTIQUE
921 bool "Mystique support"
924 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
925 video card. If you select "Advanced lowlevel driver options" below,
926 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
927 packed pixel and 32 bpp packed pixel. You can also use font widths
931 bool "G100/G200/G400/G450/G550 support"
934 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
935 video card. If you select "Advanced lowlevel driver options", you
936 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
937 pixel and 32 bpp packed pixel. You can also use font widths
940 If you need support for G400 secondary head, you must first say Y to
941 "I2C support" in the character devices section, and then to
942 "Matrox I2C support" and "G400 second head support" here in the
943 framebuffer section. G450/G550 secondary head and digital output
944 are supported without additional modules.
946 The driver starts in monitor mode. You must use the matroxset tool
947 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
948 swap primary and secondary head outputs, or to change output mode.
949 Secondary head driver always start in 640x480 resolution and you
950 must use fbset to change it.
952 Do not forget that second head supports only 16 and 32 bpp
953 packed pixels, so it is a good idea to compile them into the kernel
954 too. You can use only some font widths, as the driver uses generic
955 painting procedures (the secondary head does not use acceleration
958 G450/G550 hardware can display TV picture only from secondary CRTC,
959 and it performs no scaling, so picture must have 525 or 625 lines.
962 tristate "Matrox I2C support"
963 depends on FB_MATROX && I2C
966 This drivers creates I2C buses which are needed for accessing the
967 DDC (I2C) bus present on all Matroxes, an I2C bus which
968 interconnects Matrox optional devices, like MGA-TVO on G200 and
969 G400, and the secondary head DDC bus, present on G400 only.
971 You can say Y or M here if you want to experiment with monitor
972 detection code. You must say Y or M here if you want to use either
973 second head of G400 or MGA-TVO on G200 or G400.
975 If you compile it as module, it will create a module named
978 config FB_MATROX_MAVEN
979 tristate "G400 second head support"
980 depends on FB_MATROX_G && FB_MATROX_I2C
982 WARNING !!! This support does not work with G450 !!!
984 Say Y or M here if you want to use a secondary head (meaning two
985 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
986 head is not compatible with accelerated XFree 3.3.x SVGA servers -
987 secondary head output is blanked while you are in X. With XFree
988 3.9.17 preview you can use both heads if you use SVGA over fbdev or
989 the fbdev driver on first head and the fbdev driver on second head.
991 If you compile it as module, two modules are created,
992 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
993 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
994 also load i2c-matroxfb to get it to run.
996 The driver starts in monitor mode and you must use the matroxset
998 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
999 PAL or NTSC or to swap primary and secondary head outputs.
1000 Secondary head driver also always start in 640x480 resolution, you
1001 must use fbset to change it.
1003 Also do not forget that second head supports only 16 and 32 bpp
1004 packed pixels, so it is a good idea to compile them into the kernel
1005 too. You can use only some font widths, as the driver uses generic
1006 painting procedures (the secondary head does not use acceleration
1009 config FB_MATROX_MULTIHEAD
1010 bool "Multihead support"
1011 depends on FB_MATROX
1013 Say Y here if you have more than one (supported) Matrox device in
1014 your computer and you want to use all of them for different monitors
1015 ("multihead"). If you have only one device, you should say N because
1016 the driver compiled with Y is larger and a bit slower, especially on
1019 If you said M to "Matrox unified accelerated driver" and N here, you
1020 will still be able to use several Matrox devices simultaneously:
1021 insert several instances of the module matroxfb into the kernel
1022 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1023 for the different Matrox devices. This method is slightly faster but
1024 uses 40 KB of kernel memory per Matrox card.
1026 There is no need for enabling 'Matrox multihead support' if you have
1027 only one Matrox card in the box.
1030 tristate "ATI Radeon display support"
1031 depends on FB && PCI
1032 select I2C_ALGOBIT if FB_RADEON_I2C
1033 select I2C if FB_RADEON_I2C
1034 select FB_DDC if FB_RADEON_I2C
1035 select FB_MODE_HELPERS
1036 select FB_CFB_FILLRECT
1037 select FB_CFB_COPYAREA
1038 select FB_CFB_IMAGEBLIT
1039 select FB_MACMODES if PPC_OF
1041 Choose this option if you want to use an ATI Radeon graphics card as
1042 a framebuffer device. There are both PCI and AGP versions. You
1043 don't need to choose this to run the Radeon in plain VGA mode.
1045 If you say Y here and want DDC/I2C support you must first say Y to
1046 "I2C support" and "I2C bit-banging support" in the character devices
1049 If you say M here then "I2C support" and "I2C bit-banging support"
1050 can be build either as modules or built-in.
1052 There is a product page at
1053 http://apps.ati.com/ATIcompare/
1055 config FB_RADEON_I2C
1056 bool "DDC/I2C for ATI Radeon support"
1057 depends on FB_RADEON
1060 Say Y here if you want DDC/I2C support for your Radeon board.
1062 config FB_RADEON_BACKLIGHT
1063 bool "Support for backlight control"
1064 depends on FB_RADEON && PMAC_BACKLIGHT
1068 Say Y here if you want to control the backlight of your display.
1070 config FB_RADEON_DEBUG
1071 bool "Lots of debug output from Radeon driver"
1072 depends on FB_RADEON
1075 Say Y here if you want the Radeon driver to output all sorts
1076 of debugging information to provide to the maintainer when
1077 something goes wrong.
1080 tristate "ATI Rage128 display support"
1081 depends on FB && PCI
1082 select FB_CFB_FILLRECT
1083 select FB_CFB_COPYAREA
1084 select FB_CFB_IMAGEBLIT
1085 select FB_MACMODES if PPC_PMAC
1087 This driver supports graphics boards with the ATI Rage128 chips.
1088 Say Y if you have such a graphics board and read
1089 <file:Documentation/fb/aty128fb.txt>.
1091 To compile this driver as a module, choose M here: the
1092 module will be called aty128fb.
1094 config FB_ATY128_BACKLIGHT
1095 bool "Support for backlight control"
1096 depends on FB_ATY128 && PMAC_BACKLIGHT
1100 Say Y here if you want to control the backlight of your display.
1103 tristate "ATI Mach64 display support" if PCI || ATARI
1104 depends on FB && !SPARC32
1105 select FB_CFB_FILLRECT
1106 select FB_CFB_COPYAREA
1107 select FB_CFB_IMAGEBLIT
1108 select FB_MACMODES if PPC
1110 This driver supports graphics boards with the ATI Mach64 chips.
1111 Say Y if you have such a graphics board.
1113 To compile this driver as a module, choose M here: the
1114 module will be called atyfb.
1117 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1118 depends on PCI && FB_ATY
1119 default y if SPARC64 && FB_PCI
1121 Say Y here to support use of ATI's 64-bit Rage boards (or other
1122 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1123 framebuffer device. The ATI product support page for these boards
1124 is at <http://support.ati.com/products/pc/mach64/>.
1126 config FB_ATY_GENERIC_LCD
1127 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1128 depends on FB_ATY_CT
1130 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1131 Rage XC, or Rage XL chipset.
1134 bool "Mach64 GX support" if PCI
1138 Say Y here to support use of the ATI Mach64 Graphics Expression
1139 board (or other boards based on the Mach64 GX chipset) as a
1140 framebuffer device. The ATI product support page for these boards
1142 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1144 config FB_ATY_BACKLIGHT
1145 bool "Support for backlight control"
1146 depends on FB_ATY && PMAC_BACKLIGHT
1150 Say Y here if you want to control the backlight of your display.
1153 bool "S3 Trio display support"
1154 depends on (FB = y) && PPC && BROKEN
1156 If you have a S3 Trio say Y. Say N for S3 Virge.
1159 tristate "S3 Trio/Virge support"
1160 depends on FB && PCI
1161 select FB_CFB_FILLRECT
1162 select FB_CFB_COPYAREA
1163 select FB_CFB_IMAGEBLIT
1164 select FB_TILEBLITTING
1167 Driver for graphics boards with S3 Trio / S3 Virge chip.
1170 tristate "S3 Savage support"
1171 depends on FB && PCI && EXPERIMENTAL
1172 select I2C_ALGOBIT if FB_SAVAGE_I2C
1173 select I2C if FB_SAVAGE_I2C
1174 select FB_DDC if FB_SAVAGE_I2C
1175 select FB_MODE_HELPERS
1176 select FB_CFB_FILLRECT
1177 select FB_CFB_COPYAREA
1178 select FB_CFB_IMAGEBLIT
1180 This driver supports notebooks and computers with S3 Savage PCI/AGP
1183 Say Y if you have such a graphics card.
1185 To compile this driver as a module, choose M here; the module
1186 will be called savagefb.
1188 config FB_SAVAGE_I2C
1189 bool "Enable DDC2 Support"
1190 depends on FB_SAVAGE
1192 This enables I2C support for S3 Savage Chipsets. This is used
1193 only for getting EDID information from the attached display
1194 allowing for robust video mode handling and switching.
1196 Because fbdev-2.6 requires that drivers must be able to
1197 independently validate video mode parameters, you should say Y
1200 config FB_SAVAGE_ACCEL
1201 bool "Enable Console Acceleration"
1202 depends on FB_SAVAGE
1205 This option will compile in console acceleration support. If
1206 the resulting framebuffer console has bothersome glitches, then
1210 tristate "SiS/XGI display support"
1211 depends on FB && PCI
1212 select FB_CFB_FILLRECT
1213 select FB_CFB_COPYAREA
1214 select FB_CFB_IMAGEBLIT
1216 This is the frame buffer device driver for the SiS 300, 315, 330
1217 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1218 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1220 To compile this driver as a module, choose M here; the module
1221 will be called sisfb.
1224 bool "SiS 300 series support"
1227 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1230 bool "SiS 315/330/340 series and XGI support"
1233 Say Y here to support use of the SiS 315, 330 and 340 series
1234 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1235 as XGI V3XT, V5, V8 and Z7.
1238 tristate "NeoMagic display support"
1239 depends on FB && PCI
1240 select FB_MODE_HELPERS
1241 select FB_CFB_FILLRECT
1242 select FB_CFB_COPYAREA
1243 select FB_CFB_IMAGEBLIT
1245 This driver supports notebooks with NeoMagic PCI chips.
1246 Say Y if you have such a graphics card.
1248 To compile this driver as a module, choose M here: the
1249 module will be called neofb.
1252 tristate "IMG Kyro support"
1253 depends on FB && PCI
1254 select FB_CFB_FILLRECT
1255 select FB_CFB_COPYAREA
1256 select FB_CFB_IMAGEBLIT
1258 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1261 To compile this driver as a module, choose M here: the
1262 module will be called kyrofb.
1265 tristate "3Dfx Banshee/Voodoo3 display support"
1266 depends on FB && PCI
1267 select FB_CFB_IMAGEBLIT
1268 select FB_CFB_FILLRECT
1269 select FB_CFB_COPYAREA
1271 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1272 chips. Say Y if you have such a graphics board.
1274 To compile this driver as a module, choose M here: the
1275 module will be called tdfxfb.
1277 config FB_3DFX_ACCEL
1278 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1279 depends on FB_3DFX && EXPERIMENTAL
1281 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1282 with acceleration functions.
1286 tristate "3Dfx Voodoo Graphics (sst1) support"
1287 depends on FB && PCI
1288 select FB_CFB_FILLRECT
1289 select FB_CFB_COPYAREA
1290 select FB_CFB_IMAGEBLIT
1292 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1293 Voodoo2 (cvg) based graphics card.
1295 To compile this driver as a module, choose M here: the
1296 module will be called sstfb.
1298 WARNING: Do not use any application that uses the 3D engine
1299 (namely glide) while using this driver.
1300 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1301 options and other important info support.
1304 tristate "Cyberblade/i1 support"
1305 depends on FB && PCI && X86_32 && !64BIT
1306 select FB_CFB_IMAGEBLIT
1309 This driver is supposed to support the Trident Cyberblade/i1
1310 graphics core integrated in the VIA VT8601A North Bridge,
1311 also known as VIA Apollo PLE133.
1314 - Developed, tested and working on EPIA 5000 and EPIA 800.
1315 - Does work reliable on all systems with CRT/LCD connected to
1317 - Should work on systems that do use the internal LCD port, but
1318 this is absolutely not tested.
1320 Character imageblit, copyarea and rectangle fill are hw accelerated,
1321 ypan scrolling is used by default.
1323 Please do read <file:Documentation/fb/cyblafb/*>.
1325 To compile this driver as a module, choose M here: the
1326 module will be called cyblafb.
1329 tristate "Trident support"
1330 depends on FB && PCI
1331 select FB_CFB_FILLRECT
1332 select FB_CFB_COPYAREA
1333 select FB_CFB_IMAGEBLIT
1335 This driver is supposed to support graphics boards with the
1336 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1337 but also on some motherboards. For more information, read
1338 <file:Documentation/fb/tridentfb.txt>
1340 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1343 Say Y if you have such a graphics board.
1346 To compile this driver as a module, choose M here: the
1347 module will be called tridentfb.
1349 config FB_TRIDENT_ACCEL
1350 bool "Trident Acceleration functions (EXPERIMENTAL)"
1351 depends on FB_TRIDENT && EXPERIMENTAL
1353 This will compile the Trident frame buffer device with
1354 acceleration functions.
1357 tristate "Permedia3 support"
1358 depends on FB && PCI && BROKEN
1360 This is the frame buffer device driver for the 3DLabs Permedia3
1361 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1362 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1363 and maybe other boards.
1366 bool "Au1100 LCD Driver"
1367 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1370 bool "Au1200 LCD Driver"
1371 depends on FB && MIPS && SOC_AU1200
1372 select FB_CFB_FILLRECT
1373 select FB_CFB_COPYAREA
1374 select FB_CFB_IMAGEBLIT
1376 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1377 various panels and CRTs by passing in kernel cmd line option
1378 au1200fb:panel=<name>.
1380 source "drivers/video/geode/Kconfig"
1383 bool "Creator/Creator3D/Elite3D support"
1384 depends on FB_SBUS && SPARC64
1385 select FB_CFB_COPYAREA
1386 select FB_CFB_IMAGEBLIT
1388 This is the frame buffer device driver for the Creator, Creator3D,
1389 and Elite3D graphics boards.
1392 bool "TCX (SS4/SS5 only) support"
1394 select FB_CFB_FILLRECT
1395 select FB_CFB_COPYAREA
1396 select FB_CFB_IMAGEBLIT
1398 This is the frame buffer device driver for the TCX 24/8bit frame
1402 bool "CGfourteen (SX) support"
1404 select FB_CFB_FILLRECT
1405 select FB_CFB_COPYAREA
1406 select FB_CFB_IMAGEBLIT
1408 This is the frame buffer device driver for the CGfourteen frame
1409 buffer on Desktop SPARCsystems with the SX graphics option.
1412 bool "P9100 (Sparcbook 3 only) support"
1414 select FB_CFB_FILLRECT
1415 select FB_CFB_COPYAREA
1416 select FB_CFB_IMAGEBLIT
1418 This is the frame buffer device driver for the P9100 card
1419 supported on Sparcbook 3 machines.
1422 bool "Leo (ZX) support"
1424 select FB_CFB_FILLRECT
1425 select FB_CFB_COPYAREA
1426 select FB_CFB_IMAGEBLIT
1428 This is the frame buffer device driver for the SBUS-based Sun ZX
1429 (leo) frame buffer cards.
1432 bool "PCI framebuffers"
1433 depends on (FB = y) && PCI && SPARC
1436 bool "IGA 168x display support"
1437 depends on SPARC32 && FB_PCI
1438 select FB_CFB_FILLRECT
1439 select FB_CFB_COPYAREA
1440 select FB_CFB_IMAGEBLIT
1442 This is the framebuffer device for the INTERGRAPHICS 1680 and
1443 successor frame buffer cards.
1446 tristate "HD64461 Frame Buffer support"
1447 depends on FB && HD64461
1448 select FB_CFB_FILLRECT
1449 select FB_CFB_COPYAREA
1450 select FB_CFB_IMAGEBLIT
1452 This is the frame buffer device driver for the Hitachi HD64461 LCD
1456 bool "PMAG-AA TURBOchannel framebuffer support"
1457 depends on (FB = y) && TC
1458 select FB_CFB_FILLRECT
1459 select FB_CFB_COPYAREA
1460 select FB_CFB_IMAGEBLIT
1462 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1463 used mainly in the MIPS-based DECstation series.
1466 tristate "PMAG-BA TURBOchannel framebuffer support"
1468 select FB_CFB_FILLRECT
1469 select FB_CFB_COPYAREA
1470 select FB_CFB_IMAGEBLIT
1472 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1473 used mainly in the MIPS-based DECstation series.
1476 tristate "PMAGB-B TURBOchannel framebuffer support"
1478 select FB_CFB_FILLRECT
1479 select FB_CFB_COPYAREA
1480 select FB_CFB_IMAGEBLIT
1482 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1483 in the MIPS-based DECstation series. The card is currently only
1484 supported in 1280x1024x8 mode.
1487 bool "Maxine (Personal DECstation) onboard framebuffer support"
1488 depends on (FB = y) && MACH_DECSTATION
1489 select FB_CFB_FILLRECT
1490 select FB_CFB_COPYAREA
1491 select FB_CFB_IMAGEBLIT
1493 Support for the onboard framebuffer (1024x768x8) in the Personal
1494 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1498 bool "TMPTX3912/PR31700 frame buffer support"
1499 depends on (FB = y) && NINO
1500 select FB_CFB_FILLRECT
1501 select FB_CFB_COPYAREA
1502 select FB_CFB_IMAGEBLIT
1504 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1505 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1507 Say Y here to enable kernel support for the on-board framebuffer.
1510 bool "G364 frame buffer support"
1511 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1516 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1517 Olivetti M700-10 systems.
1520 bool "Motorola 68328 native frame buffer support"
1521 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1522 select FB_CFB_FILLRECT
1523 select FB_CFB_COPYAREA
1524 select FB_CFB_IMAGEBLIT
1526 Say Y here if you want to support the built-in frame buffer of
1527 the Motorola 68328 CPU family.
1530 tristate "PXA LCD framebuffer support"
1531 depends on FB && ARCH_PXA
1532 select FB_CFB_FILLRECT
1533 select FB_CFB_COPYAREA
1534 select FB_CFB_IMAGEBLIT
1536 Frame buffer driver for the built-in LCD controller in the Intel
1539 This driver is also available as a module ( = code which can be
1540 inserted and removed from the running kernel whenever you want). The
1541 module will be called pxafb. If you want to compile it as a module,
1542 say M here and read <file:Documentation/modules.txt>.
1546 config FB_PXA_PARAMETERS
1547 bool "PXA LCD command line parameters"
1551 Enable the use of kernel command line or module parameters
1552 to configure the physical properties of the LCD panel when
1553 using the PXA LCD driver.
1555 This option allows you to override the panel parameters
1556 supplied by the platform in order to support multiple
1557 different models of flatpanel. If you will only be using a
1558 single model of flatpanel then you can safely leave this
1561 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1564 tristate "2700G LCD framebuffer support"
1565 depends on FB && ARCH_PXA
1566 select FB_CFB_FILLRECT
1567 select FB_CFB_COPYAREA
1568 select FB_CFB_IMAGEBLIT
1570 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1574 bool "Enable debugging info via debugfs"
1575 depends on FB_MBX && DEBUG_FS
1578 Enable this if you want debugging information using the debug
1579 filesystem (debugfs)
1584 tristate "W100 frame buffer support"
1585 depends on FB && PXA_SHARPSL
1586 select FB_CFB_FILLRECT
1587 select FB_CFB_COPYAREA
1588 select FB_CFB_IMAGEBLIT
1590 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1592 This driver is also available as a module ( = code which can be
1593 inserted and removed from the running kernel whenever you want). The
1594 module will be called w100fb. If you want to compile it as a module,
1595 say M here and read <file:Documentation/modules.txt>.
1600 tristate "S3C2410 LCD framebuffer support"
1601 depends on FB && ARCH_S3C2410
1602 select FB_CFB_FILLRECT
1603 select FB_CFB_COPYAREA
1604 select FB_CFB_IMAGEBLIT
1606 Frame buffer driver for the built-in LCD controller in the Samsung
1609 This driver is also available as a module ( = code which can be
1610 inserted and removed from the running kernel whenever you want). The
1611 module will be called s3c2410fb. If you want to compile it as a module,
1612 say M here and read <file:Documentation/modules.txt>.
1615 config FB_S3C2410_DEBUG
1616 bool "S3C2410 lcd debug messages"
1617 depends on FB_S3C2410
1619 Turn on debugging messages. Note that you can set/unset at run time
1622 config FB_PNX4008_DUM
1623 tristate "Display Update Module support on Philips PNX4008 board"
1624 depends on FB && ARCH_PNX4008
1626 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1628 config FB_PNX4008_DUM_RGB
1629 tristate "RGB Framebuffer support on Philips PNX4008 board"
1630 depends on FB_PNX4008_DUM
1631 select FB_CFB_FILLRECT
1632 select FB_CFB_COPYAREA
1633 select FB_CFB_IMAGEBLIT
1635 Say Y here to enable support for PNX4008 RGB Framebuffer
1637 config FB_IBM_GXT4500
1638 tristate "Framebuffer support for IBM GXT4500P adaptor"
1640 select FB_CFB_FILLRECT
1641 select FB_CFB_COPYAREA
1642 select FB_CFB_IMAGEBLIT
1644 Say Y here to enable support for the IBM GXT4500P display
1645 adaptor, found on some IBM System P (pSeries) machines.
1648 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1650 select FB_CFB_FILLRECT
1651 select FB_CFB_COPYAREA
1652 select FB_CFB_IMAGEBLIT
1654 This is a `virtual' frame buffer device. It operates on a chunk of
1655 unswappable kernel memory instead of on the memory of a graphics
1656 board. This means you cannot see any output sent to this frame
1657 buffer device, while it does consume precious memory. The main use
1658 of this frame buffer device is testing and debugging the frame
1659 buffer subsystem. Do NOT enable it for normal systems! To protect
1660 the innocent, it has to be enabled explicitly at boot time using the
1661 kernel option `video=vfb:'.
1663 To compile this driver as a module, choose M here: the
1664 module will be called vfb. In order to load it, you must use
1665 the vfb_enable=1 option.
1669 source "drivers/video/console/Kconfig"
1672 if FB || SGI_NEWPORT_CONSOLE
1673 source "drivers/video/logo/Kconfig"
1677 source "drivers/video/backlight/Kconfig"