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.
96 select BACKLIGHT_LCD_SUPPORT
97 select BACKLIGHT_CLASS_DEVICE
100 config FB_MODE_HELPERS
101 bool "Enable Video Mode Handling Helpers"
105 This enables functions for handling video modes using the
106 Generalized Timing Formula and the EDID parser. A few drivers rely
107 on this feature such as the radeonfb, rivafb, and the i810fb. If
108 your driver does not take advantage of this feature, choosing Y will
109 just increase the kernel size by about 5K.
111 config FB_TILEBLITTING
112 bool "Enable Tile Blitting Support"
116 This enables tile blitting. Tile blitting is a drawing technique
117 where the screen is divided into rectangular sections (tiles), whereas
118 the standard blitting divides the screen into pixels. Because the
119 default drawing element is a tile, drawing functions will be passed
120 parameters in terms of number of tiles instead of number of pixels.
121 For example, to draw a single character, instead of using bitmaps,
122 an index to an array of bitmaps will be used. To clear or move a
123 rectangular section of a screen, the rectangle will be described in
124 terms of number of tiles in the x- and y-axis.
126 This is particularly important to one driver, matroxfb. If
130 tristate "Cirrus Logic support"
131 depends on FB && (ZORRO || PCI)
132 select FB_CFB_FILLRECT
133 select FB_CFB_COPYAREA
134 select FB_CFB_IMAGEBLIT
136 This enables support for Cirrus Logic GD542x/543x based boards on
137 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
139 If you have a PCI-based system, this enables support for these
140 chips: GD-543x, GD-544x, GD-5480.
142 Please read the file <file:Documentation/fb/cirrusfb.txt>.
144 Say N unless you have such a graphics board or plan to get one
145 before you next recompile the kernel.
148 tristate "Permedia2 support"
149 depends on FB && ((AMIGA && BROKEN) || PCI)
150 select FB_CFB_FILLRECT
151 select FB_CFB_COPYAREA
152 select FB_CFB_IMAGEBLIT
154 This is the frame buffer device driver for the Permedia2 AGP frame
155 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
157 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
159 config FB_PM2_FIFO_DISCONNECT
160 bool "enable FIFO disconnect feature"
161 depends on FB_PM2 && PCI
163 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
166 tristate "ARM PrimeCell PL110 support"
167 depends on FB && ARM && ARM_AMBA
168 select FB_CFB_FILLRECT
169 select FB_CFB_COPYAREA
170 select FB_CFB_IMAGEBLIT
172 This framebuffer device driver is for the ARM PrimeCell PL110
173 Colour LCD controller. ARM PrimeCells provide the building
174 blocks for System on a Chip devices.
176 If you want to compile this as a module (=code which can be
177 inserted into and removed from the running kernel), say M
178 here and read <file:Documentation/modules.txt>. The module
179 will be called amba-clcd.
183 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
185 default FB_ARMCLCD_SHARP_LQ035Q7DB02
187 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
188 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
190 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
191 color QVGA, HRTFT panel. The LogicPD device includes an
192 an integrated HRTFT controller IC.
193 The native resolution is 240x320.
195 config FB_ARMCLCD_SHARP_LQ057Q3DC02
196 bool "LogicPD LCD 5.7\" QVGA"
198 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
199 color QVGA, TFT panel. The LogicPD device includes an
200 The native resolution is 320x240.
202 config FB_ARMCLCD_SHARP_LQ64D343
203 bool "LogicPD LCD 6.4\" VGA"
205 This is an implementation of the Sharp LQ64D343, a 6.4"
206 color VGA, TFT panel. The LogicPD device includes an
207 The native resolution is 640x480.
209 config FB_ARMCLCD_SHARP_LQ10D368
210 bool "LogicPD LCD 10.4\" VGA"
212 This is an implementation of the Sharp LQ10D368, a 10.4"
213 color VGA, TFT panel. The LogicPD device includes an
214 The native resolution is 640x480.
217 config FB_ARMCLCD_SHARP_LQ121S1DG41
218 bool "LogicPD LCD 12.1\" SVGA"
220 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
221 color SVGA, TFT panel. The LogicPD device includes an
222 The native resolution is 800x600.
224 This panel requires a clock rate may be an integer fraction
225 of the base LCDCLK frequency. The driver will select the
226 highest frequency available that is lower than the maximum
227 allowed. The panel may flicker if the clock rate is
228 slower than the recommended minimum.
230 config FB_ARMCLCD_AUO_A070VW01_WIDE
231 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
233 This is an implementation of the AU Optronics, a 7.0"
234 WIDE Color. The native resolution is 234x480.
236 config FB_ARMCLCD_HITACHI
237 bool "Hitachi Wide Screen 800x480"
239 This is an implementation of the Hitachi 800x480.
245 bool "Acorn VIDC support"
246 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
247 select FB_CFB_FILLRECT
248 select FB_CFB_COPYAREA
249 select FB_CFB_IMAGEBLIT
251 This is the frame buffer device driver for the Acorn VIDC graphics
252 hardware found in Acorn RISC PCs and other ARM-based machines. If
256 bool "CLPS711X LCD support"
257 depends on (FB = y) && ARM && ARCH_CLPS711X
258 select FB_CFB_FILLRECT
259 select FB_CFB_COPYAREA
260 select FB_CFB_IMAGEBLIT
262 Say Y to enable the Framebuffer driver for the CLPS7111 and
266 bool "SA-1100 LCD support"
267 depends on (FB = y) && ARM && ARCH_SA1100
268 select FB_CFB_FILLRECT
269 select FB_CFB_COPYAREA
270 select FB_CFB_IMAGEBLIT
272 This is a framebuffer device for the SA-1100 LCD Controller.
273 See <http://www.linux-fbdev.org/> for information on framebuffer
276 If you plan to use the LCD display with your SA-1100 system, say
280 tristate "Motorola i.MX LCD support"
281 depends on FB && ARM && ARCH_IMX
282 select FB_CFB_FILLRECT
283 select FB_CFB_COPYAREA
284 select FB_CFB_IMAGEBLIT
287 tristate "CyberPro 2000/2010/5000 support"
288 depends on FB && PCI && (BROKEN || !SPARC64)
289 select FB_CFB_FILLRECT
290 select FB_CFB_COPYAREA
291 select FB_CFB_IMAGEBLIT
293 This enables support for the Integraphics CyberPro 20x0 and 5000
294 VGA chips used in the Rebel.com Netwinder and other machines.
295 Say Y if you have a NetWinder or a graphics card containing this
296 device, otherwise say N.
300 depends on (FB = y) && APOLLO
302 select FB_CFB_FILLRECT
303 select FB_CFB_IMAGEBLIT
307 depends on (FB = y) && Q40
309 select FB_CFB_FILLRECT
310 select FB_CFB_COPYAREA
311 select FB_CFB_IMAGEBLIT
314 tristate "Amiga native chipset support"
315 depends on FB && AMIGA
317 This is the frame buffer device driver for the builtin graphics
318 chipset found in Amigas.
320 To compile this driver as a module, choose M here: the
321 module will be called amifb.
324 bool "Amiga OCS chipset support"
327 This enables support for the original Agnus and Denise video chips,
328 found in the Amiga 1000 and most A500's and A2000's. If you intend
329 to run Linux on any of these systems, say Y; otherwise say N.
332 bool "Amiga ECS chipset support"
335 This enables support for the Enhanced Chip Set, found in later
336 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
337 you intend to run Linux on any of these systems, say Y; otherwise
341 bool "Amiga AGA chipset support"
344 This enables support for the Advanced Graphics Architecture (also
345 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
346 and CD32. If you intend to run Linux on any of these systems, say Y;
350 tristate "Amiga CyberVision 64 support"
351 depends on FB && ZORRO && BROKEN
352 select FB_CFB_FILLRECT
353 select FB_CFB_COPYAREA
354 select FB_CFB_IMAGEBLIT
356 This enables support for the Cybervision 64 graphics card from
357 Phase5. Please note that its use is not all that intuitive (i.e. if
358 you have any questions, be sure to ask!). Say N unless you have a
359 Cybervision 64 or plan to get one before you next recompile the
360 kernel. Please note that this driver DOES NOT support the
361 Cybervision 64/3D card, as they use incompatible video chips.
364 bool "Amiga CyberVision 64/3D support "
365 depends on (FB = y) && ZORRO && BROKEN
366 select FB_CFB_FILLRECT
367 select FB_CFB_COPYAREA
368 select FB_CFB_IMAGEBLIT
370 This enables support for the Cybervision 64/3D graphics card from
371 Phase5. Please note that its use is not all that intuitive (i.e. if
372 you have any questions, be sure to ask!). Say N unless you have a
373 Cybervision 64/3D or plan to get one before you next recompile the
374 kernel. Please note that this driver DOES NOT support the older
375 Cybervision 64 card, as they use incompatible video chips.
378 tristate "Amiga Retina Z3 support"
379 depends on (FB = y) && ZORRO && BROKEN
381 This enables support for the Retina Z3 graphics card. Say N unless
382 you have a Retina Z3 or plan to get one before you next recompile
386 bool "Amiga FrameMaster II/Rainbow II support"
387 depends on (FB = y) && ZORRO
388 select FB_CFB_FILLRECT
389 select FB_CFB_COPYAREA
390 select FB_CFB_IMAGEBLIT
392 This is the frame buffer device driver for the Amiga FrameMaster
393 card from BSC (exhibited 1992 but not shipped as a CBM product).
396 tristate "Arc Monochrome LCD board support"
398 select FB_CFB_FILLRECT
399 select FB_CFB_COPYAREA
400 select FB_CFB_IMAGEBLIT
402 This enables support for the Arc Monochrome LCD board. The board
403 is based on the KS-108 lcd controller and is typically a matrix
404 of 2*n chips. This driver was tested with a 128x64 panel. This
405 driver supports it for use with x86 SBCs through a 16 bit GPIO
406 interface (8 bit data, 8 bit control). If you anticpate using
407 this driver, say Y or M; otherwise say N. You must specify the
408 GPIO IO address to be used for setting control and data.
411 bool "Atari native chipset support"
412 depends on (FB = y) && ATARI && BROKEN
414 This is the frame buffer device driver for the builtin graphics
415 chipset found in Ataris.
418 bool "Open Firmware frame buffer device support"
419 depends on (FB = y) && (PPC64 || PPC_OF)
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
425 Say Y if you want support with Open Firmware for your graphics
429 bool "Apple \"control\" 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 graphics adapter in the
437 Power Macintosh 7300 and others.
440 bool "Apple \"platinum\" display support"
441 depends on (FB = y) && 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 "platinum" graphics
448 adapter in some Power Macintoshes.
451 bool "Apple \"valkyrie\" display support"
452 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
458 This driver supports a frame buffer for the "valkyrie" graphics
459 adapter in some Power Macintoshes.
462 bool "Chips 65550 display support"
463 depends on (FB = y) && PPC32
464 select FB_CFB_FILLRECT
465 select FB_CFB_COPYAREA
466 select FB_CFB_IMAGEBLIT
468 This is the frame buffer device driver for the Chips & Technologies
469 65550 graphics chip in PowerBooks.
472 bool "Asiliant (Chips) 69000 display support"
473 depends on (FB = y) && PCI
474 select FB_CFB_FILLRECT
475 select FB_CFB_COPYAREA
476 select FB_CFB_IMAGEBLIT
478 This is the frame buffer device driver for the Asiliant 69030 chipset
481 bool "IMS Twin Turbo display support"
482 depends on (FB = y) && PCI
483 select FB_CFB_IMAGEBLIT
484 select FB_MACMODES if PPC
486 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
487 many Macintosh and compatible computers.
490 tristate "VGA 16-color graphics support"
491 depends on FB && (X86 || PPC)
492 select FB_CFB_FILLRECT
493 select FB_CFB_COPYAREA
494 select FB_CFB_IMAGEBLIT
496 This is the frame buffer device driver for VGA 16 color graphic
497 cards. Say Y if you have such a card.
499 To compile this driver as a module, choose M here: the
500 module will be called vga16fb.
503 tristate "HP STI frame buffer device support"
504 depends on FB && PARISC
505 select FB_CFB_FILLRECT
506 select FB_CFB_COPYAREA
507 select FB_CFB_IMAGEBLIT
510 STI refers to the HP "Standard Text Interface" which is a set of
511 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
512 Enabling this option will implement the linux framebuffer device
513 using calls to the STI BIOS routines for initialisation.
515 If you enable this option, you will get a planar framebuffer device
516 /dev/fb which will work on the most common HP graphic cards of the
517 NGLE family, including the artist chips (in the 7xx and Bxxx series),
518 HCRX, HCRX24, CRX, CRX24 and VisEG series.
520 It is safe to enable this option, so you should probably say "Y".
523 bool "Generic Macintosh display support"
524 depends on (FB = y) && MAC
525 select FB_CFB_FILLRECT
526 select FB_CFB_COPYAREA
527 select FB_CFB_IMAGEBLIT
530 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
533 depends on (FB = y) && HP300
534 select FB_CFB_FILLRECT
535 select FB_CFB_IMAGEBLIT
539 tristate "TGA framebuffer support"
540 depends on FB && ALPHA
541 select FB_CFB_FILLRECT
542 select FB_CFB_COPYAREA
543 select FB_CFB_IMAGEBLIT
545 This is the frame buffer device driver for generic TGA graphic
546 cards. Say Y if you have one of those.
549 bool "VESA VGA graphics support"
550 depends on (FB = y) && X86
551 select FB_CFB_FILLRECT
552 select FB_CFB_COPYAREA
553 select FB_CFB_IMAGEBLIT
555 This is the frame buffer device driver for generic VESA 2.0
556 compliant graphic cards. The older VESA 1.2 cards are not supported.
557 You will get a boot time penguin logo at no additional cost. Please
558 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
561 bool "Intel-based Macintosh Framebuffer Support"
562 depends on (FB = y) && X86 && EFI
563 select FB_CFB_FILLRECT
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
567 This is the frame buffer device driver for the Intel-based Macintosh
570 tristate "Hercules mono graphics support"
572 select FB_CFB_FILLRECT
573 select FB_CFB_COPYAREA
574 select FB_CFB_IMAGEBLIT
576 Say Y here if you have a Hercules mono graphics card.
578 To compile this driver as a module, choose M here: the
579 module will be called hgafb.
581 As this card technology is 15 years old, most people will answer N
585 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
586 depends on FB_HGA && EXPERIMENTAL
588 This will compile the Hercules mono graphics with
589 acceleration functions.
592 tristate "SGI Visual Workstation framebuffer support"
593 depends on FB && X86_VISWS
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
598 SGI Visual Workstation support for framebuffer graphics.
601 bool "SGI Graphics Backend frame buffer support"
602 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
603 select FB_CFB_FILLRECT
604 select FB_CFB_COPYAREA
605 select FB_CFB_IMAGEBLIT
607 This is the frame buffer device driver for SGI Graphics Backend.
608 This chip is used in SGI O2 and Visual Workstation 320/540.
611 int "Video memory size in MB"
615 This is the amount of memory reserved for the framebuffer,
616 which can be any value between 1MB and 8MB.
619 bool "Sun3 framebuffer support"
620 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
623 bool "SBUS and UPA framebuffers"
624 depends on (FB = y) && SPARC
626 Say Y if you want support for SBUS or UPA based frame buffer device.
630 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
631 select FB_CFB_FILLRECT
632 select FB_CFB_COPYAREA
633 select FB_CFB_IMAGEBLIT
635 This is the frame buffer device driver for the BWtwo frame buffer.
638 bool "CGthree support"
639 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
640 select FB_CFB_FILLRECT
641 select FB_CFB_COPYAREA
642 select FB_CFB_IMAGEBLIT
644 This is the frame buffer device driver for the CGthree frame buffer.
647 bool "CGsix (GX,TurboGX) support"
648 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
649 select FB_CFB_COPYAREA
650 select FB_CFB_IMAGEBLIT
652 This is the frame buffer device driver for the CGsix (GX, TurboGX)
656 tristate "NEC PowerVR 2 display support"
657 depends on FB && SH_DREAMCAST
658 select FB_CFB_FILLRECT
659 select FB_CFB_COPYAREA
660 select FB_CFB_IMAGEBLIT
662 Say Y here if you have a PowerVR 2 card in your box. If you plan to
663 run linux on your Dreamcast, you will have to say Y here.
664 This driver may or may not work on other PowerVR 2 cards, but is
665 totally untested. Use at your own risk. If unsure, say N.
667 To compile this driver as a module, choose M here: the
668 module will be called pvr2fb.
670 You can pass several parameters to the driver at boot time or at
671 module load time. The parameters look like "video=pvr2:XXX", where
672 the meaning of XXX can be found at the end of the main source file
673 (<file:drivers/video/pvr2fb.c>). Please see the file
674 <file:Documentation/fb/pvr2fb.txt>.
677 bool "Epson 1355 framebuffer support"
678 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
679 select FB_CFB_FILLRECT
680 select FB_CFB_COPYAREA
681 select FB_CFB_IMAGEBLIT
683 Build in support for the SED1355 Epson Research Embedded RAMDAC
684 LCD/CRT Controller (since redesignated as the S1D13505) as a
685 framebuffer. Product specs at
686 <http://www.erd.epson.com/vdc/html/products.htm>.
689 tristate "Epson S1D13XXX framebuffer support"
691 select FB_CFB_FILLRECT
692 select FB_CFB_COPYAREA
693 select FB_CFB_IMAGEBLIT
695 Support for S1D13XXX framebuffer device family (currently only
696 working with S1D13806). Product specs at
697 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
700 tristate "nVidia Framebuffer Support"
702 select I2C_ALGOBIT if FB_NVIDIA_I2C
703 select I2C if FB_NVIDIA_I2C
704 select FB_DDC if FB_NVIDIA_I2C
705 select FB_MODE_HELPERS
706 select FB_CFB_FILLRECT
707 select FB_CFB_COPYAREA
708 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"
722 This enables I2C support for nVidia Chipsets. This is used
723 only for getting EDID information from the attached display
724 allowing for robust video mode handling and switching.
726 Because fbdev-2.6 requires that drivers must be able to
727 independently validate video mode parameters, you should say Y
730 config FB_NVIDIA_BACKLIGHT
731 bool "Support for backlight control"
732 depends on FB_NVIDIA && PMAC_BACKLIGHT
736 Say Y here if you want to control the backlight of your display.
739 tristate "nVidia Riva support"
741 select I2C_ALGOBIT if FB_RIVA_I2C
742 select I2C if FB_RIVA_I2C
743 select FB_DDC if FB_RIVA_I2C
744 select FB_MODE_HELPERS
745 select FB_CFB_FILLRECT
746 select FB_CFB_COPYAREA
747 select FB_CFB_IMAGEBLIT
749 This driver supports graphics boards with the nVidia Riva/Geforce
751 Say Y if you have such a graphics board.
753 To compile this driver as a module, choose M here: the
754 module will be called rivafb.
757 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 informations to provide to the maintainer when
775 something goes wrong.
777 config FB_RIVA_BACKLIGHT
778 bool "Support for backlight control"
779 depends on FB_RIVA && PMAC_BACKLIGHT
783 Say Y here if you want to control the backlight of your display.
786 tristate "Intel 810/815 support (EXPERIMENTAL)"
787 depends on FB && EXPERIMENTAL && PCI && X86_32
790 select FB_MODE_HELPERS
791 select FB_CFB_FILLRECT
792 select FB_CFB_COPYAREA
793 select FB_CFB_IMAGEBLIT
795 This driver supports the on-board graphics built in to the Intel 810
796 and 815 chipsets. Say Y if you have and plan to use such a board.
798 To compile this driver as a module, choose M here: the
799 module will be called i810fb.
801 For more information, please read
802 <file:Documentation/fb/intel810.txt>
805 bool "use VESA Generalized Timing Formula"
808 If you say Y, then the VESA standard, Generalized Timing Formula
809 or GTF, will be used to calculate the required video timing values
810 per video mode. Since the GTF allows nondiscrete timings
811 (nondiscrete being a range of values as opposed to discrete being a
812 set of values), you'll be able to use any combination of horizontal
813 and vertical resolutions, and vertical refresh rates without having
814 to specify your own timing parameters. This is especially useful
815 to maximize the performance of an aging display, or if you just
816 have a display with nonstandard dimensions. A VESA compliant
817 monitor is recommended, but can still work with non-compliant ones.
818 If you need or want this, then select this option. The timings may
819 not be compliant with Intel's recommended values. Use at your own
822 If you say N, the driver will revert to discrete video timings
823 using a set recommended by Intel in their documentation.
828 bool "Enable DDC Support"
829 depends on FB_I810 && FB_I810_GTF
835 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
836 depends on FB && EXPERIMENTAL && PCI && X86
839 select I2C_ALGOBIT if FB_INTEL_I2C
840 select I2C if FB_INTEL_I2C
841 select FB_MODE_HELPERS
842 select FB_CFB_FILLRECT
843 select FB_CFB_COPYAREA
844 select FB_CFB_IMAGEBLIT
846 This driver supports the on-board graphics built in to the Intel
847 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
848 Say Y if you have and plan to use such a board.
850 If you say Y here and want DDC/I2C support you must first say Y to
851 "I2C support" and "I2C bit-banging support" in the character devices
854 If you say M here then "I2C support" and "I2C bit-banging support"
855 can be build either as modules or built-in.
857 To compile this driver as a module, choose M here: the
858 module will be called intelfb.
860 For more information, please read <file:Documentation/fb/intelfb.txt>
862 config FB_INTEL_DEBUG
863 bool "Intel driver Debug Messages"
866 Say Y here if you want the Intel driver to output all sorts
867 of debugging informations to provide to the maintainer when
868 something goes wrong.
871 bool "DDC/I2C for Intel framebuffer support"
875 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
878 tristate "Matrox acceleration"
880 select FB_CFB_FILLRECT
881 select FB_CFB_COPYAREA
882 select FB_CFB_IMAGEBLIT
883 select FB_TILEBLITTING
884 select FB_MACMODES if PPC_PMAC
886 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
887 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
888 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
889 Matrox G400, G450 or G550 card in your box.
891 To compile this driver as a module, choose M here: the
892 module will be called matroxfb.
894 You can pass several parameters to the driver at boot time or at
895 module load time. The parameters look like "video=matrox:XXX", and
896 are described in <file:Documentation/fb/matroxfb.txt>.
898 config FB_MATROX_MILLENIUM
899 bool "Millennium I/II support"
902 Say Y here if you have a Matrox Millennium or Matrox Millennium II
903 video card. If you select "Advanced lowlevel driver options" below,
904 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
905 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
906 also use font widths different from 8.
908 config FB_MATROX_MYSTIQUE
909 bool "Mystique support"
912 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
913 video card. If you select "Advanced lowlevel driver options" below,
914 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
915 packed pixel and 32 bpp packed pixel. You can also use font widths
919 bool "G100/G200/G400/G450/G550 support"
922 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
923 video card. If you select "Advanced lowlevel driver options", you
924 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
925 pixel and 32 bpp packed pixel. You can also use font widths
928 If you need support for G400 secondary head, you must first say Y to
929 "I2C support" in the character devices section, and then to
930 "Matrox I2C support" and "G400 second head support" here in the
931 framebuffer section. G450/G550 secondary head and digital output
932 are supported without additional modules.
934 The driver starts in monitor mode. You must use the matroxset tool
935 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
936 swap primary and secondary head outputs, or to change output mode.
937 Secondary head driver always start in 640x480 resolution and you
938 must use fbset to change it.
940 Do not forget that second head supports only 16 and 32 bpp
941 packed pixels, so it is a good idea to compile them into the kernel
942 too. You can use only some font widths, as the driver uses generic
943 painting procedures (the secondary head does not use acceleration
946 G450/G550 hardware can display TV picture only from secondary CRTC,
947 and it performs no scaling, so picture must have 525 or 625 lines.
950 tristate "Matrox I2C support"
951 depends on FB_MATROX && I2C
954 This drivers creates I2C buses which are needed for accessing the
955 DDC (I2C) bus present on all Matroxes, an I2C bus which
956 interconnects Matrox optional devices, like MGA-TVO on G200 and
957 G400, and the secondary head DDC bus, present on G400 only.
959 You can say Y or M here if you want to experiment with monitor
960 detection code. You must say Y or M here if you want to use either
961 second head of G400 or MGA-TVO on G200 or G400.
963 If you compile it as module, it will create a module named
966 config FB_MATROX_MAVEN
967 tristate "G400 second head support"
968 depends on FB_MATROX_G && FB_MATROX_I2C
970 WARNING !!! This support does not work with G450 !!!
972 Say Y or M here if you want to use a secondary head (meaning two
973 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
974 head is not compatible with accelerated XFree 3.3.x SVGA servers -
975 secondary head output is blanked while you are in X. With XFree
976 3.9.17 preview you can use both heads if you use SVGA over fbdev or
977 the fbdev driver on first head and the fbdev driver on second head.
979 If you compile it as module, two modules are created,
980 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
981 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
982 also load i2c-matroxfb to get it to run.
984 The driver starts in monitor mode and you must use the matroxset
986 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
987 PAL or NTSC or to swap primary and secondary head outputs.
988 Secondary head driver also always start in 640x480 resolution, you
989 must use fbset to change it.
991 Also do not forget that second head supports only 16 and 32 bpp
992 packed pixels, so it is a good idea to compile them into the kernel
993 too. You can use only some font widths, as the driver uses generic
994 painting procedures (the secondary head does not use acceleration
997 config FB_MATROX_MULTIHEAD
998 bool "Multihead support"
1001 Say Y here if you have more than one (supported) Matrox device in
1002 your computer and you want to use all of them for different monitors
1003 ("multihead"). If you have only one device, you should say N because
1004 the driver compiled with Y is larger and a bit slower, especially on
1007 If you said M to "Matrox unified accelerated driver" and N here, you
1008 will still be able to use several Matrox devices simultaneously:
1009 insert several instances of the module matroxfb into the kernel
1010 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1011 for the different Matrox devices. This method is slightly faster but
1012 uses 40 KB of kernel memory per Matrox card.
1014 There is no need for enabling 'Matrox multihead support' if you have
1015 only one Matrox card in the box.
1018 tristate "ATI Radeon display support"
1019 depends on FB && PCI
1020 select I2C_ALGOBIT if FB_RADEON_I2C
1021 select I2C if FB_RADEON_I2C
1022 select FB_MODE_HELPERS
1023 select FB_CFB_FILLRECT
1024 select FB_CFB_COPYAREA
1025 select FB_CFB_IMAGEBLIT
1026 select FB_MACMODES if PPC_OF
1028 Choose this option if you want to use an ATI Radeon graphics card as
1029 a framebuffer device. There are both PCI and AGP versions. You
1030 don't need to choose this to run the Radeon in plain VGA mode.
1032 If you say Y here and want DDC/I2C support you must first say Y to
1033 "I2C support" and "I2C bit-banging support" in the character devices
1036 If you say M here then "I2C support" and "I2C bit-banging support"
1037 can be build either as modules or built-in.
1039 There is a product page at
1040 http://apps.ati.com/ATIcompare/
1042 config FB_RADEON_I2C
1043 bool "DDC/I2C for ATI Radeon support"
1044 depends on FB_RADEON
1047 Say Y here if you want DDC/I2C support for your Radeon board.
1049 config FB_RADEON_BACKLIGHT
1050 bool "Support for backlight control"
1051 depends on FB_RADEON && PMAC_BACKLIGHT
1055 Say Y here if you want to control the backlight of your display.
1057 config FB_RADEON_DEBUG
1058 bool "Lots of debug output from Radeon driver"
1059 depends on FB_RADEON
1062 Say Y here if you want the Radeon driver to output all sorts
1063 of debugging informations to provide to the maintainer when
1064 something goes wrong.
1067 tristate "ATI Rage128 display support"
1068 depends on FB && PCI
1069 select FB_CFB_FILLRECT
1070 select FB_CFB_COPYAREA
1071 select FB_CFB_IMAGEBLIT
1072 select FB_MACMODES if PPC_PMAC
1074 This driver supports graphics boards with the ATI Rage128 chips.
1075 Say Y if you have such a graphics board and read
1076 <file:Documentation/fb/aty128fb.txt>.
1078 To compile this driver as a module, choose M here: the
1079 module will be called aty128fb.
1081 config FB_ATY128_BACKLIGHT
1082 bool "Support for backlight control"
1083 depends on FB_ATY128 && PMAC_BACKLIGHT
1087 Say Y here if you want to control the backlight of your display.
1090 tristate "ATI Mach64 display support" if PCI || ATARI
1091 depends on FB && !SPARC32
1092 select FB_CFB_FILLRECT
1093 select FB_CFB_COPYAREA
1094 select FB_CFB_IMAGEBLIT
1095 select FB_MACMODES if PPC
1097 This driver supports graphics boards with the ATI Mach64 chips.
1098 Say Y if you have such a graphics board.
1100 To compile this driver as a module, choose M here: the
1101 module will be called atyfb.
1104 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1105 depends on PCI && FB_ATY
1106 default y if SPARC64 && FB_PCI
1108 Say Y here to support use of ATI's 64-bit Rage boards (or other
1109 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1110 framebuffer device. The ATI product support page for these boards
1111 is at <http://support.ati.com/products/pc/mach64/>.
1113 config FB_ATY_GENERIC_LCD
1114 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1115 depends on FB_ATY_CT
1117 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1118 Rage XC, or Rage XL chipset.
1121 bool "Mach64 GX support" if PCI
1125 Say Y here to support use of the ATI Mach64 Graphics Expression
1126 board (or other boards based on the Mach64 GX chipset) as a
1127 framebuffer device. The ATI product support page for these boards
1129 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1131 config FB_ATY_BACKLIGHT
1132 bool "Support for backlight control"
1133 depends on FB_ATY && PMAC_BACKLIGHT
1137 Say Y here if you want to control the backlight of your display.
1140 bool "S3 Trio display support"
1141 depends on (FB = y) && PPC && BROKEN
1143 If you have a S3 Trio say Y. Say N for S3 Virge.
1146 tristate "S3 Savage support"
1147 depends on FB && PCI && EXPERIMENTAL
1148 select I2C_ALGOBIT if FB_SAVAGE_I2C
1149 select I2C if FB_SAVAGE_I2C
1150 select FB_MODE_HELPERS
1151 select FB_CFB_FILLRECT
1152 select FB_CFB_COPYAREA
1153 select FB_CFB_IMAGEBLIT
1155 This driver supports notebooks and computers with S3 Savage PCI/AGP
1158 Say Y if you have such a graphics card.
1160 To compile this driver as a module, choose M here; the module
1161 will be called savagefb.
1163 config FB_SAVAGE_I2C
1164 bool "Enable DDC2 Support"
1165 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 && 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 "PCI framebuffers"
1408 depends on (FB = y) && PCI && SPARC
1411 bool "IGA 168x display support"
1412 depends on SPARC32 && FB_PCI
1413 select FB_CFB_FILLRECT
1414 select FB_CFB_COPYAREA
1415 select FB_CFB_IMAGEBLIT
1417 This is the framebuffer device for the INTERGRAPHICS 1680 and
1418 successor frame buffer cards.
1421 tristate "HD64461 Frame Buffer support"
1422 depends on FB && HD64461
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1427 This is the frame buffer device driver for the Hitachi HD64461 LCD
1431 bool "PMAG-AA TURBOchannel framebuffer support"
1432 depends on (FB = y) && TC
1433 select FB_CFB_FILLRECT
1434 select FB_CFB_COPYAREA
1435 select FB_CFB_IMAGEBLIT
1437 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1438 used mainly in the MIPS-based DECstation series.
1441 bool "PMAG-BA TURBOchannel framebuffer support"
1442 depends on (FB = y) && TC
1443 select FB_CFB_FILLRECT
1444 select FB_CFB_COPYAREA
1445 select FB_CFB_IMAGEBLIT
1447 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1448 used mainly in the MIPS-based DECstation series.
1451 bool "PMAGB-B TURBOchannel framebuffer support"
1452 depends on (FB = y) && TC
1453 select FB_CFB_FILLRECT
1454 select FB_CFB_COPYAREA
1455 select FB_CFB_IMAGEBLIT
1457 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1458 in the MIPS-based DECstation series. The card is currently only
1459 supported in 1280x1024x8 mode.
1462 bool "Maxine (Personal DECstation) onboard framebuffer support"
1463 depends on (FB = y) && MACH_DECSTATION
1464 select FB_CFB_FILLRECT
1465 select FB_CFB_COPYAREA
1466 select FB_CFB_IMAGEBLIT
1468 Support for the onboard framebuffer (1024x768x8) in the Personal
1469 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1473 bool "TMPTX3912/PR31700 frame buffer support"
1474 depends on (FB = y) && NINO
1475 select FB_CFB_FILLRECT
1476 select FB_CFB_COPYAREA
1477 select FB_CFB_IMAGEBLIT
1479 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1480 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1482 Say Y here to enable kernel support for the on-board framebuffer.
1485 bool "G364 frame buffer support"
1486 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1487 select FB_CFB_FILLRECT
1488 select FB_CFB_COPYAREA
1489 select FB_CFB_IMAGEBLIT
1491 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1492 Olivetti M700-10 systems.
1495 bool "Motorola 68328 native frame buffer support"
1496 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1497 select FB_CFB_FILLRECT
1498 select FB_CFB_COPYAREA
1499 select FB_CFB_IMAGEBLIT
1501 Say Y here if you want to support the built-in frame buffer of
1502 the Motorola 68328 CPU family.
1505 tristate "PXA LCD framebuffer support"
1506 depends on FB && ARCH_PXA
1507 select FB_CFB_FILLRECT
1508 select FB_CFB_COPYAREA
1509 select FB_CFB_IMAGEBLIT
1511 Frame buffer driver for the built-in LCD controller in the Intel
1514 This driver is also available as a module ( = code which can be
1515 inserted and removed from the running kernel whenever you want). The
1516 module will be called pxafb. If you want to compile it as a module,
1517 say M here and read <file:Documentation/modules.txt>.
1521 config FB_PXA_PARAMETERS
1522 bool "PXA LCD command line parameters"
1526 Enable the use of kernel command line or module parameters
1527 to configure the physical properties of the LCD panel when
1528 using the PXA LCD driver.
1530 This option allows you to override the panel parameters
1531 supplied by the platform in order to support multiple
1532 different models of flatpanel. If you will only be using a
1533 single model of flatpanel then you can safely leave this
1536 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1539 tristate "2700G LCD framebuffer support"
1540 depends on FB && ARCH_PXA
1541 select FB_CFB_FILLRECT
1542 select FB_CFB_COPYAREA
1543 select FB_CFB_IMAGEBLIT
1545 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1549 bool "Enable debugging info via debugfs"
1550 depends on FB_MBX && DEBUG_FS
1553 Enable this if you want debugging information using the debug
1554 filesystem (debugfs)
1559 tristate "W100 frame buffer support"
1560 depends on FB && PXA_SHARPSL
1561 select FB_CFB_FILLRECT
1562 select FB_CFB_COPYAREA
1563 select FB_CFB_IMAGEBLIT
1565 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1567 This driver is also available as a module ( = code which can be
1568 inserted and removed from the running kernel whenever you want). The
1569 module will be called w100fb. If you want to compile it as a module,
1570 say M here and read <file:Documentation/modules.txt>.
1575 tristate "S3C2410 LCD framebuffer support"
1576 depends on FB && ARCH_S3C2410
1577 select FB_CFB_FILLRECT
1578 select FB_CFB_COPYAREA
1579 select FB_CFB_IMAGEBLIT
1581 Frame buffer driver for the built-in LCD controller in the Samsung
1584 This driver is also available as a module ( = code which can be
1585 inserted and removed from the running kernel whenever you want). The
1586 module will be called s3c2410fb. If you want to compile it as a module,
1587 say M here and read <file:Documentation/modules.txt>.
1590 config FB_S3C2410_DEBUG
1591 bool "S3C2410 lcd debug messages"
1592 depends on FB_S3C2410
1594 Turn on debugging messages. Note that you can set/unset at run time
1597 config FB_PNX4008_DUM
1598 tristate "Display Update Module support on Philips PNX4008 board"
1599 depends on FB && ARCH_PNX4008
1601 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1603 config FB_PNX4008_DUM_RGB
1604 tristate "RGB Framebuffer support on Philips PNX4008 board"
1605 depends on FB_PNX4008_DUM
1606 select FB_CFB_FILLRECT
1607 select FB_CFB_COPYAREA
1608 select FB_CFB_IMAGEBLIT
1610 Say Y here to enable support for PNX4008 RGB Framebuffer
1613 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1615 select FB_CFB_FILLRECT
1616 select FB_CFB_COPYAREA
1617 select FB_CFB_IMAGEBLIT
1619 This is a `virtual' frame buffer device. It operates on a chunk of
1620 unswappable kernel memory instead of on the memory of a graphics
1621 board. This means you cannot see any output sent to this frame
1622 buffer device, while it does consume precious memory. The main use
1623 of this frame buffer device is testing and debugging the frame
1624 buffer subsystem. Do NOT enable it for normal systems! To protect
1625 the innocent, it has to be enabled explicitly at boot time using the
1626 kernel option `video=vfb:'.
1628 To compile this driver as a module, choose M here: the
1629 module will be called vfb. In order to load it, you must use
1630 the vfb_enable=1 option.
1634 source "drivers/video/console/Kconfig"
1637 if FB || SGI_NEWPORT_CONSOLE
1638 source "drivers/video/logo/Kconfig"
1642 source "drivers/video/backlight/Kconfig"