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.
56 config FB_CFB_FILLRECT
61 Include the cfb_fillrect function for generic software rectangle
62 filling. This is used by drivers that don't provide their own
63 (accelerated) version.
65 config FB_CFB_COPYAREA
70 Include the cfb_copyarea function for generic software area copying.
71 This is used by drivers that don't provide their own (accelerated)
74 config FB_CFB_IMAGEBLIT
79 Include the cfb_imageblit function for generic software image
80 blitting. This is used by drivers that don't provide their own
81 (accelerated) version.
93 config FB_MODE_HELPERS
94 bool "Enable Video Mode Handling Helpers"
98 This enables functions for handling video modes using the
99 Generalized Timing Formula and the EDID parser. A few drivers rely
100 on this feature such as the radeonfb, rivafb, and the i810fb. If
101 your driver does not take advantage of this feature, choosing Y will
102 just increase the kernel size by about 5K.
104 config FB_TILEBLITTING
105 bool "Enable Tile Blitting Support"
109 This enables tile blitting. Tile blitting is a drawing technique
110 where the screen is divided into rectangular sections (tiles), whereas
111 the standard blitting divides the screen into pixels. Because the
112 default drawing element is a tile, drawing functions will be passed
113 parameters in terms of number of tiles instead of number of pixels.
114 For example, to draw a single character, instead of using bitmaps,
115 an index to an array of bitmaps will be used. To clear or move a
116 rectangular section of a screen, the rectangle will be described in
117 terms of number of tiles in the x- and y-axis.
119 This is particularly important to one driver, matroxfb. If
123 tristate "Cirrus Logic support"
124 depends on FB && (ZORRO || PCI)
125 select FB_CFB_FILLRECT
126 select FB_CFB_COPYAREA
127 select FB_CFB_IMAGEBLIT
129 This enables support for Cirrus Logic GD542x/543x based boards on
130 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
132 If you have a PCI-based system, this enables support for these
133 chips: GD-543x, GD-544x, GD-5480.
135 Please read the file <file:Documentation/fb/cirrusfb.txt>.
137 Say N unless you have such a graphics board or plan to get one
138 before you next recompile the kernel.
141 tristate "Permedia2 support"
142 depends on FB && ((AMIGA && BROKEN) || PCI)
143 select FB_CFB_FILLRECT
144 select FB_CFB_COPYAREA
145 select FB_CFB_IMAGEBLIT
147 This is the frame buffer device driver for the Permedia2 AGP frame
148 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
150 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
152 config FB_PM2_FIFO_DISCONNECT
153 bool "enable FIFO disconnect feature"
154 depends on FB_PM2 && PCI
156 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
159 tristate "ARM PrimeCell PL110 support"
160 depends on FB && ARM && ARM_AMBA
161 select FB_CFB_FILLRECT
162 select FB_CFB_COPYAREA
163 select FB_CFB_IMAGEBLIT
165 This framebuffer device driver is for the ARM PrimeCell PL110
166 Colour LCD controller. ARM PrimeCells provide the building
167 blocks for System on a Chip devices.
169 If you want to compile this as a module (=code which can be
170 inserted into and removed from the running kernel), say M
171 here and read <file:Documentation/modules.txt>. The module
172 will be called amba-clcd.
176 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
178 default FB_ARMCLCD_SHARP_LQ035Q7DB02
180 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
181 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
183 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
184 color QVGA, HRTFT panel. The LogicPD device includes an
185 an integrated HRTFT controller IC.
186 The native resolution is 240x320.
188 config FB_ARMCLCD_SHARP_LQ057Q3DC02
189 bool "LogicPD LCD 5.7\" QVGA"
191 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
192 color QVGA, TFT panel. The LogicPD device includes an
193 The native resolution is 320x240.
195 config FB_ARMCLCD_SHARP_LQ64D343
196 bool "LogicPD LCD 6.4\" VGA"
198 This is an implementation of the Sharp LQ64D343, a 6.4"
199 color VGA, TFT panel. The LogicPD device includes an
200 The native resolution is 640x480.
202 config FB_ARMCLCD_SHARP_LQ10D368
203 bool "LogicPD LCD 10.4\" VGA"
205 This is an implementation of the Sharp LQ10D368, a 10.4"
206 color VGA, TFT panel. The LogicPD device includes an
207 The native resolution is 640x480.
210 config FB_ARMCLCD_SHARP_LQ121S1DG41
211 bool "LogicPD LCD 12.1\" SVGA"
213 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
214 color SVGA, TFT panel. The LogicPD device includes an
215 The native resolution is 800x600.
217 This panel requires a clock rate may be an integer fraction
218 of the base LCDCLK frequency. The driver will select the
219 highest frequency available that is lower than the maximum
220 allowed. The panel may flicker if the clock rate is
221 slower than the recommended minimum.
223 config FB_ARMCLCD_AUO_A070VW01_WIDE
224 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
226 This is an implementation of the AU Optronics, a 7.0"
227 WIDE Color. The native resolution is 234x480.
229 config FB_ARMCLCD_HITACHI
230 bool "Hitachi Wide Screen 800x480"
232 This is an implementation of the Hitachi 800x480.
238 bool "Acorn VIDC support"
239 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
240 select FB_CFB_FILLRECT
241 select FB_CFB_COPYAREA
242 select FB_CFB_IMAGEBLIT
244 This is the frame buffer device driver for the Acorn VIDC graphics
245 hardware found in Acorn RISC PCs and other ARM-based machines. If
249 bool "CLPS711X LCD support"
250 depends on (FB = y) && ARM && ARCH_CLPS711X
251 select FB_CFB_FILLRECT
252 select FB_CFB_COPYAREA
253 select FB_CFB_IMAGEBLIT
255 Say Y to enable the Framebuffer driver for the CLPS7111 and
259 bool "SA-1100 LCD support"
260 depends on (FB = y) && ARM && ARCH_SA1100
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This is a framebuffer device for the SA-1100 LCD Controller.
266 See <http://www.linux-fbdev.org/> for information on framebuffer
269 If you plan to use the LCD display with your SA-1100 system, say
273 tristate "Motorola i.MX LCD support"
274 depends on FB && ARM && ARCH_IMX
275 select FB_CFB_FILLRECT
276 select FB_CFB_COPYAREA
277 select FB_CFB_IMAGEBLIT
280 tristate "CyberPro 2000/2010/5000 support"
281 depends on FB && PCI && (BROKEN || !SPARC64)
282 select FB_CFB_FILLRECT
283 select FB_CFB_COPYAREA
284 select FB_CFB_IMAGEBLIT
286 This enables support for the Integraphics CyberPro 20x0 and 5000
287 VGA chips used in the Rebel.com Netwinder and other machines.
288 Say Y if you have a NetWinder or a graphics card containing this
289 device, otherwise say N.
293 depends on (FB = y) && APOLLO
295 select FB_CFB_FILLRECT
296 select FB_CFB_IMAGEBLIT
300 depends on (FB = y) && Q40
302 select FB_CFB_FILLRECT
303 select FB_CFB_COPYAREA
304 select FB_CFB_IMAGEBLIT
307 tristate "Amiga native chipset support"
308 depends on FB && AMIGA
310 This is the frame buffer device driver for the builtin graphics
311 chipset found in Amigas.
313 To compile this driver as a module, choose M here: the
314 module will be called amifb.
317 bool "Amiga OCS chipset support"
320 This enables support for the original Agnus and Denise video chips,
321 found in the Amiga 1000 and most A500's and A2000's. If you intend
322 to run Linux on any of these systems, say Y; otherwise say N.
325 bool "Amiga ECS chipset support"
328 This enables support for the Enhanced Chip Set, found in later
329 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
330 you intend to run Linux on any of these systems, say Y; otherwise
334 bool "Amiga AGA chipset support"
337 This enables support for the Advanced Graphics Architecture (also
338 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
339 and CD32. If you intend to run Linux on any of these systems, say Y;
343 tristate "Amiga CyberVision 64 support"
344 depends on FB && ZORRO && BROKEN
345 select FB_CFB_FILLRECT
346 select FB_CFB_COPYAREA
347 select FB_CFB_IMAGEBLIT
349 This enables support for the Cybervision 64 graphics card from
350 Phase5. Please note that its use is not all that intuitive (i.e. if
351 you have any questions, be sure to ask!). Say N unless you have a
352 Cybervision 64 or plan to get one before you next recompile the
353 kernel. Please note that this driver DOES NOT support the
354 Cybervision 64/3D card, as they use incompatible video chips.
357 bool "Amiga CyberVision 64/3D support "
358 depends on (FB = y) && ZORRO && BROKEN
359 select FB_CFB_FILLRECT
360 select FB_CFB_COPYAREA
361 select FB_CFB_IMAGEBLIT
363 This enables support for the Cybervision 64/3D graphics card from
364 Phase5. Please note that its use is not all that intuitive (i.e. if
365 you have any questions, be sure to ask!). Say N unless you have a
366 Cybervision 64/3D or plan to get one before you next recompile the
367 kernel. Please note that this driver DOES NOT support the older
368 Cybervision 64 card, as they use incompatible video chips.
371 tristate "Amiga Retina Z3 support"
372 depends on (FB = y) && ZORRO && BROKEN
374 This enables support for the Retina Z3 graphics card. Say N unless
375 you have a Retina Z3 or plan to get one before you next recompile
379 bool "Amiga FrameMaster II/Rainbow II support"
380 depends on (FB = y) && ZORRO
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
385 This is the frame buffer device driver for the Amiga FrameMaster
386 card from BSC (exhibited 1992 but not shipped as a CBM product).
389 tristate "Arc Monochrome LCD board support"
391 select FB_CFB_FILLRECT
392 select FB_CFB_COPYAREA
393 select FB_CFB_IMAGEBLIT
395 This enables support for the Arc Monochrome LCD board. The board
396 is based on the KS-108 lcd controller and is typically a matrix
397 of 2*n chips. This driver was tested with a 128x64 panel. This
398 driver supports it for use with x86 SBCs through a 16 bit GPIO
399 interface (8 bit data, 8 bit control). If you anticpate using
400 this driver, say Y or M; otherwise say N. You must specify the
401 GPIO IO address to be used for setting control and data.
404 bool "Atari native chipset support"
405 depends on (FB = y) && ATARI && BROKEN
407 This is the frame buffer device driver for the builtin graphics
408 chipset found in Ataris.
411 bool "Open Firmware frame buffer device support"
412 depends on (FB = y) && (PPC64 || PPC_OF)
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
418 Say Y if you want support with Open Firmware for your graphics
422 bool "Apple \"control\" display support"
423 depends on (FB = y) && PPC_PMAC
424 select FB_CFB_FILLRECT
425 select FB_CFB_COPYAREA
426 select FB_CFB_IMAGEBLIT
429 This driver supports a frame buffer for the graphics adapter in the
430 Power Macintosh 7300 and others.
433 bool "Apple \"platinum\" display support"
434 depends on (FB = y) && PPC_PMAC
435 select FB_CFB_FILLRECT
436 select FB_CFB_COPYAREA
437 select FB_CFB_IMAGEBLIT
440 This driver supports a frame buffer for the "platinum" graphics
441 adapter in some Power Macintoshes.
444 bool "Apple \"valkyrie\" display support"
445 depends on (FB = y) && (MAC || PPC_PMAC)
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
451 This driver supports a frame buffer for the "valkyrie" graphics
452 adapter in some Power Macintoshes.
455 bool "Chips 65550 display support"
456 depends on (FB = y) && PPC
457 select FB_CFB_FILLRECT
458 select FB_CFB_COPYAREA
459 select FB_CFB_IMAGEBLIT
461 This is the frame buffer device driver for the Chips & Technologies
462 65550 graphics chip in PowerBooks.
465 bool "Asiliant (Chips) 69000 display support"
466 depends on (FB = y) && PCI
467 select FB_CFB_FILLRECT
468 select FB_CFB_COPYAREA
469 select FB_CFB_IMAGEBLIT
471 This is the frame buffer device driver for the Asiliant 69030 chipset
474 bool "IMS Twin Turbo display support"
475 depends on (FB = y) && PCI
476 select FB_CFB_IMAGEBLIT
477 select FB_MACMODES if PPC
479 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
480 many Macintosh and compatible computers.
483 tristate "VGA 16-color graphics support"
484 depends on FB && (X86 || PPC)
485 select FB_CFB_FILLRECT
486 select FB_CFB_COPYAREA
487 select FB_CFB_IMAGEBLIT
489 This is the frame buffer device driver for VGA 16 color graphic
490 cards. Say Y if you have such a card.
492 To compile this driver as a module, choose M here: the
493 module will be called vga16fb.
496 tristate "HP STI frame buffer device support"
497 depends on FB && PARISC
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
503 STI refers to the HP "Standard Text Interface" which is a set of
504 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
505 Enabling this option will implement the linux framebuffer device
506 using calls to the STI BIOS routines for initialisation.
508 If you enable this option, you will get a planar framebuffer device
509 /dev/fb which will work on the most common HP graphic cards of the
510 NGLE family, including the artist chips (in the 7xx and Bxxx series),
511 HCRX, HCRX24, CRX, CRX24 and VisEG series.
513 It is safe to enable this option, so you should probably say "Y".
516 bool "Generic Macintosh display support"
517 depends on (FB = y) && MAC
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
526 depends on (FB = y) && HP300
527 select FB_CFB_FILLRECT
528 select FB_CFB_IMAGEBLIT
532 tristate "TGA framebuffer support"
533 depends on FB && ALPHA
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
538 This is the frame buffer device driver for generic TGA graphic
539 cards. Say Y if you have one of those.
542 bool "VESA VGA graphics support"
543 depends on (FB = y) && X86
544 select FB_CFB_FILLRECT
545 select FB_CFB_COPYAREA
546 select FB_CFB_IMAGEBLIT
548 This is the frame buffer device driver for generic VESA 2.0
549 compliant graphic cards. The older VESA 1.2 cards are not supported.
550 You will get a boot time penguin logo at no additional cost. Please
551 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
554 bool "Intel-based Macintosh Framebuffer Support"
555 depends on (FB = y) && X86
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 This is the frame buffer device driver for the Intel-based Macintosh
563 tristate "Hercules mono graphics support"
565 select FB_CFB_FILLRECT
566 select FB_CFB_COPYAREA
567 select FB_CFB_IMAGEBLIT
569 Say Y here if you have a Hercules mono graphics card.
571 To compile this driver as a module, choose M here: the
572 module will be called hgafb.
574 As this card technology is 15 years old, most people will answer N
578 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
579 depends on FB_HGA && EXPERIMENTAL
581 This will compile the Hercules mono graphics with
582 acceleration functions.
585 tristate "SGI Visual Workstation framebuffer support"
586 depends on FB && X86_VISWS
587 select FB_CFB_FILLRECT
588 select FB_CFB_COPYAREA
589 select FB_CFB_IMAGEBLIT
591 SGI Visual Workstation support for framebuffer graphics.
594 bool "SGI Graphics Backend frame buffer support"
595 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the frame buffer device driver for SGI Graphics Backend.
601 This chip is used in SGI O2 and Visual Workstation 320/540.
604 int "Video memory size in MB"
608 This is the amount of memory reserved for the framebuffer,
609 which can be any value between 1MB and 8MB.
612 bool "Sun3 framebuffer support"
613 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
616 bool "SBUS and UPA framebuffers"
617 depends on (FB = y) && SPARC
619 Say Y if you want support for SBUS or UPA based frame buffer device.
623 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
624 select FB_CFB_FILLRECT
625 select FB_CFB_COPYAREA
626 select FB_CFB_IMAGEBLIT
628 This is the frame buffer device driver for the BWtwo frame buffer.
631 bool "CGthree support"
632 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
637 This is the frame buffer device driver for the CGthree frame buffer.
640 bool "CGsix (GX,TurboGX) support"
641 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
645 This is the frame buffer device driver for the CGsix (GX, TurboGX)
649 tristate "NEC PowerVR 2 display support"
650 depends on FB && SH_DREAMCAST
651 select FB_CFB_FILLRECT
652 select FB_CFB_COPYAREA
653 select FB_CFB_IMAGEBLIT
655 Say Y here if you have a PowerVR 2 card in your box. If you plan to
656 run linux on your Dreamcast, you will have to say Y here.
657 This driver may or may not work on other PowerVR 2 cards, but is
658 totally untested. Use at your own risk. If unsure, say N.
660 To compile this driver as a module, choose M here: the
661 module will be called pvr2fb.
663 You can pass several parameters to the driver at boot time or at
664 module load time. The parameters look like "video=pvr2:XXX", where
665 the meaning of XXX can be found at the end of the main source file
666 (<file:drivers/video/pvr2fb.c>). Please see the file
667 <file:Documentation/fb/pvr2fb.txt>.
670 bool "Epson 1355 framebuffer support"
671 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
672 select FB_CFB_FILLRECT
673 select FB_CFB_COPYAREA
674 select FB_CFB_IMAGEBLIT
676 Build in support for the SED1355 Epson Research Embedded RAMDAC
677 LCD/CRT Controller (since redesignated as the S1D13505) as a
678 framebuffer. Product specs at
679 <http://www.erd.epson.com/vdc/html/products.htm>.
682 tristate "Epson S1D13XXX framebuffer support"
684 select FB_CFB_FILLRECT
685 select FB_CFB_COPYAREA
686 select FB_CFB_IMAGEBLIT
688 Support for S1D13XXX framebuffer device family (currently only
689 working with S1D13806). Product specs at
690 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
693 tristate "nVidia Framebuffer Support"
695 select I2C_ALGOBIT if FB_NVIDIA_I2C
696 select I2C if FB_NVIDIA_I2C
697 select FB_MODE_HELPERS
698 select FB_CFB_FILLRECT
699 select FB_CFB_COPYAREA
700 select FB_CFB_IMAGEBLIT
702 This driver supports graphics boards with the nVidia chips, TNT
703 and newer. For very old chipsets, such as the RIVA128, then use
705 Say Y if you have such a graphics board.
707 To compile this driver as a module, choose M here: the
708 module will be called nvidiafb.
711 bool "Enable DDC Support"
714 This enables I2C support for nVidia Chipsets. This is used
715 only for getting EDID information from the attached display
716 allowing for robust video mode handling and switching.
718 Because fbdev-2.6 requires that drivers must be able to
719 independently validate video mode parameters, you should say Y
722 config FB_NVIDIA_BACKLIGHT
723 bool "Support for backlight control"
724 depends on FB_NVIDIA && PPC_PMAC
726 select BACKLIGHT_LCD_SUPPORT
727 select BACKLIGHT_CLASS_DEVICE
730 Say Y here if you want to control the backlight of your display.
733 tristate "nVidia Riva support"
735 select I2C_ALGOBIT if FB_RIVA_I2C
736 select I2C if FB_RIVA_I2C
737 select FB_MODE_HELPERS
738 select FB_CFB_FILLRECT
739 select FB_CFB_COPYAREA
740 select FB_CFB_IMAGEBLIT
742 This driver supports graphics boards with the nVidia Riva/Geforce
744 Say Y if you have such a graphics board.
746 To compile this driver as a module, choose M here: the
747 module will be called rivafb.
750 bool "Enable DDC Support"
753 This enables I2C support for nVidia Chipsets. This is used
754 only for getting EDID information from the attached display
755 allowing for robust video mode handling and switching.
757 Because fbdev-2.6 requires that drivers must be able to
758 independently validate video mode parameters, you should say Y
762 bool "Lots of debug output from Riva(nVidia) driver"
766 Say Y here if you want the Riva driver to output all sorts
767 of debugging informations to provide to the maintainer when
768 something goes wrong.
770 config FB_RIVA_BACKLIGHT
771 bool "Support for backlight control"
772 depends on FB_RIVA && PPC_PMAC
774 select BACKLIGHT_LCD_SUPPORT
775 select BACKLIGHT_CLASS_DEVICE
778 Say Y here if you want to control the backlight of your display.
781 tristate "Intel 810/815 support (EXPERIMENTAL)"
782 depends on FB && EXPERIMENTAL && PCI && X86_32
785 select FB_MODE_HELPERS
786 select FB_CFB_FILLRECT
787 select FB_CFB_COPYAREA
788 select FB_CFB_IMAGEBLIT
790 This driver supports the on-board graphics built in to the Intel 810
791 and 815 chipsets. Say Y if you have and plan to use such a board.
793 To compile this driver as a module, choose M here: the
794 module will be called i810fb.
796 For more information, please read
797 <file:Documentation/fb/intel810.txt>
800 bool "use VESA Generalized Timing Formula"
803 If you say Y, then the VESA standard, Generalized Timing Formula
804 or GTF, will be used to calculate the required video timing values
805 per video mode. Since the GTF allows nondiscrete timings
806 (nondiscrete being a range of values as opposed to discrete being a
807 set of values), you'll be able to use any combination of horizontal
808 and vertical resolutions, and vertical refresh rates without having
809 to specify your own timing parameters. This is especially useful
810 to maximize the performance of an aging display, or if you just
811 have a display with nonstandard dimensions. A VESA compliant
812 monitor is recommended, but can still work with non-compliant ones.
813 If you need or want this, then select this option. The timings may
814 not be compliant with Intel's recommended values. Use at your own
817 If you say N, the driver will revert to discrete video timings
818 using a set recommended by Intel in their documentation.
823 bool "Enable DDC Support"
824 depends on FB_I810 && FB_I810_GTF
830 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
831 depends on FB && EXPERIMENTAL && PCI && X86
834 select FB_MODE_HELPERS
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
839 This driver supports the on-board graphics built in to the Intel
840 830M/845G/852GM/855GM/865G chipsets.
841 Say Y if you have and plan to use such a board.
843 To compile this driver as a module, choose M here: the
844 module will be called intelfb.
846 config FB_INTEL_DEBUG
847 bool "Intel driver Debug Messages"
850 Say Y here if you want the Intel driver to output all sorts
851 of debugging informations to provide to the maintainer when
852 something goes wrong.
855 tristate "Matrox acceleration"
857 select FB_CFB_FILLRECT
858 select FB_CFB_COPYAREA
859 select FB_CFB_IMAGEBLIT
860 select FB_TILEBLITTING
861 select FB_MACMODES if PPC_PMAC
863 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
864 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
865 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
866 Matrox G400, G450 or G550 card in your box.
868 To compile this driver as a module, choose M here: the
869 module will be called matroxfb.
871 You can pass several parameters to the driver at boot time or at
872 module load time. The parameters look like "video=matrox:XXX", and
873 are described in <file:Documentation/fb/matroxfb.txt>.
875 config FB_MATROX_MILLENIUM
876 bool "Millennium I/II support"
879 Say Y here if you have a Matrox Millennium or Matrox Millennium II
880 video card. If you select "Advanced lowlevel driver options" below,
881 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
882 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
883 also use font widths different from 8.
885 config FB_MATROX_MYSTIQUE
886 bool "Mystique support"
889 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
890 video card. If you select "Advanced lowlevel driver options" below,
891 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
892 packed pixel and 32 bpp packed pixel. You can also use font widths
896 bool "G100/G200/G400/G450/G550 support"
899 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
900 video card. If you select "Advanced lowlevel driver options", you
901 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
902 pixel and 32 bpp packed pixel. You can also use font widths
905 If you need support for G400 secondary head, you must first say Y to
906 "I2C support" in the character devices section, and then to
907 "Matrox I2C support" and "G400 second head support" here in the
908 framebuffer section. G450/G550 secondary head and digital output
909 are supported without additional modules.
911 The driver starts in monitor mode. You must use the matroxset tool
912 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
913 swap primary and secondary head outputs, or to change output mode.
914 Secondary head driver always start in 640x480 resolution and you
915 must use fbset to change it.
917 Do not forget that second head supports only 16 and 32 bpp
918 packed pixels, so it is a good idea to compile them into the kernel
919 too. You can use only some font widths, as the driver uses generic
920 painting procedures (the secondary head does not use acceleration
923 G450/G550 hardware can display TV picture only from secondary CRTC,
924 and it performs no scaling, so picture must have 525 or 625 lines.
927 tristate "Matrox I2C support"
928 depends on FB_MATROX && I2C
931 This drivers creates I2C buses which are needed for accessing the
932 DDC (I2C) bus present on all Matroxes, an I2C bus which
933 interconnects Matrox optional devices, like MGA-TVO on G200 and
934 G400, and the secondary head DDC bus, present on G400 only.
936 You can say Y or M here if you want to experiment with monitor
937 detection code. You must say Y or M here if you want to use either
938 second head of G400 or MGA-TVO on G200 or G400.
940 If you compile it as module, it will create a module named
943 config FB_MATROX_MAVEN
944 tristate "G400 second head support"
945 depends on FB_MATROX_G && FB_MATROX_I2C
947 WARNING !!! This support does not work with G450 !!!
949 Say Y or M here if you want to use a secondary head (meaning two
950 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
951 head is not compatible with accelerated XFree 3.3.x SVGA servers -
952 secondary head output is blanked while you are in X. With XFree
953 3.9.17 preview you can use both heads if you use SVGA over fbdev or
954 the fbdev driver on first head and the fbdev driver on second head.
956 If you compile it as module, two modules are created,
957 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
958 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
959 also load i2c-matroxfb to get it to run.
961 The driver starts in monitor mode and you must use the matroxset
963 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
964 PAL or NTSC or to swap primary and secondary head outputs.
965 Secondary head driver also always start in 640x480 resolution, you
966 must use fbset to change it.
968 Also do not forget that second head supports only 16 and 32 bpp
969 packed pixels, so it is a good idea to compile them into the kernel
970 too. You can use only some font widths, as the driver uses generic
971 painting procedures (the secondary head does not use acceleration
974 config FB_MATROX_MULTIHEAD
975 bool "Multihead support"
978 Say Y here if you have more than one (supported) Matrox device in
979 your computer and you want to use all of them for different monitors
980 ("multihead"). If you have only one device, you should say N because
981 the driver compiled with Y is larger and a bit slower, especially on
984 If you said M to "Matrox unified accelerated driver" and N here, you
985 will still be able to use several Matrox devices simultaneously:
986 insert several instances of the module matroxfb into the kernel
987 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
988 for the different Matrox devices. This method is slightly faster but
989 uses 40 KB of kernel memory per Matrox card.
991 There is no need for enabling 'Matrox multihead support' if you have
992 only one Matrox card in the box.
995 tristate "ATI Radeon display support"
997 select I2C_ALGOBIT if FB_RADEON_I2C
998 select I2C if FB_RADEON_I2C
999 select FB_MODE_HELPERS
1000 select FB_CFB_FILLRECT
1001 select FB_CFB_COPYAREA
1002 select FB_CFB_IMAGEBLIT
1003 select FB_MACMODES if PPC_OF
1005 Choose this option if you want to use an ATI Radeon graphics card as
1006 a framebuffer device. There are both PCI and AGP versions. You
1007 don't need to choose this to run the Radeon in plain VGA mode.
1009 If you say Y here and want DDC/I2C support you must first say Y to
1010 "I2C support" and "I2C bit-banging support" in the character devices
1013 If you say M here then "I2C support" and "I2C bit-banging support"
1014 can be build either as modules or built-in.
1016 There is a product page at
1017 http://apps.ati.com/ATIcompare/
1019 config FB_RADEON_I2C
1020 bool "DDC/I2C for ATI Radeon support"
1021 depends on FB_RADEON
1024 Say Y here if you want DDC/I2C support for your Radeon board.
1026 config FB_RADEON_BACKLIGHT
1027 bool "Support for backlight control"
1028 depends on FB_RADEON && PPC_PMAC
1030 select BACKLIGHT_LCD_SUPPORT
1031 select BACKLIGHT_CLASS_DEVICE
1034 Say Y here if you want to control the backlight of your display.
1036 config FB_RADEON_DEBUG
1037 bool "Lots of debug output from Radeon driver"
1038 depends on FB_RADEON
1041 Say Y here if you want the Radeon driver to output all sorts
1042 of debugging informations to provide to the maintainer when
1043 something goes wrong.
1046 tristate "ATI Rage128 display support"
1047 depends on FB && PCI
1048 select FB_CFB_FILLRECT
1049 select FB_CFB_COPYAREA
1050 select FB_CFB_IMAGEBLIT
1051 select FB_MACMODES if PPC_PMAC
1053 This driver supports graphics boards with the ATI Rage128 chips.
1054 Say Y if you have such a graphics board and read
1055 <file:Documentation/fb/aty128fb.txt>.
1057 To compile this driver as a module, choose M here: the
1058 module will be called aty128fb.
1060 config FB_ATY128_BACKLIGHT
1061 bool "Support for backlight control"
1062 depends on FB_ATY128 && PPC_PMAC
1064 select BACKLIGHT_LCD_SUPPORT
1065 select BACKLIGHT_CLASS_DEVICE
1068 Say Y here if you want to control the backlight of your display.
1071 tristate "ATI Mach64 display support" if PCI || ATARI
1072 depends on FB && !SPARC32
1073 select FB_CFB_FILLRECT
1074 select FB_CFB_COPYAREA
1075 select FB_CFB_IMAGEBLIT
1076 select FB_MACMODES if PPC
1078 This driver supports graphics boards with the ATI Mach64 chips.
1079 Say Y if you have such a graphics board.
1081 To compile this driver as a module, choose M here: the
1082 module will be called atyfb.
1085 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1086 depends on PCI && FB_ATY
1087 default y if SPARC64 && FB_PCI
1089 Say Y here to support use of ATI's 64-bit Rage boards (or other
1090 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1091 framebuffer device. The ATI product support page for these boards
1092 is at <http://support.ati.com/products/pc/mach64/>.
1094 config FB_ATY_GENERIC_LCD
1095 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1096 depends on FB_ATY_CT
1098 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1099 Rage XC, or Rage XL chipset.
1102 bool "Mach64 GX support" if PCI
1106 Say Y here to support use of the ATI Mach64 Graphics Expression
1107 board (or other boards based on the Mach64 GX chipset) as a
1108 framebuffer device. The ATI product support page for these boards
1110 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1112 config FB_ATY_BACKLIGHT
1113 bool "Support for backlight control"
1114 depends on FB_ATY && PPC_PMAC
1116 select BACKLIGHT_LCD_SUPPORT
1117 select BACKLIGHT_CLASS_DEVICE
1120 Say Y here if you want to control the backlight of your display.
1123 bool "S3 Trio display support"
1124 depends on (FB = y) && PPC && BROKEN
1126 If you have a S3 Trio say Y. Say N for S3 Virge.
1129 tristate "S3 Savage support"
1130 depends on FB && PCI && EXPERIMENTAL
1131 select I2C_ALGOBIT if FB_SAVAGE_I2C
1132 select I2C if FB_SAVAGE_I2C
1133 select FB_MODE_HELPERS
1134 select FB_CFB_FILLRECT
1135 select FB_CFB_COPYAREA
1136 select FB_CFB_IMAGEBLIT
1138 This driver supports notebooks and computers with S3 Savage PCI/AGP
1141 Say Y if you have such a graphics card.
1143 To compile this driver as a module, choose M here; the module
1144 will be called savagefb.
1146 config FB_SAVAGE_I2C
1147 bool "Enable DDC2 Support"
1148 depends on FB_SAVAGE
1150 This enables I2C support for S3 Savage Chipsets. This is used
1151 only for getting EDID information from the attached display
1152 allowing for robust video mode handling and switching.
1154 Because fbdev-2.6 requires that drivers must be able to
1155 independently validate video mode parameters, you should say Y
1158 config FB_SAVAGE_ACCEL
1159 bool "Enable Console Acceleration"
1160 depends on FB_SAVAGE
1163 This option will compile in console acceleration support. If
1164 the resulting framebuffer console has bothersome glitches, then
1168 tristate "SiS/XGI display support"
1169 depends on FB && PCI
1170 select FB_CFB_FILLRECT
1171 select FB_CFB_COPYAREA
1172 select FB_CFB_IMAGEBLIT
1174 This is the frame buffer device driver for the SiS 300, 315, 330
1175 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1176 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1178 To compile this driver as a module, choose M here; the module
1179 will be called sisfb.
1182 bool "SiS 300 series support"
1185 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1188 bool "SiS 315/330/340 series and XGI support"
1191 Say Y here to support use of the SiS 315, 330 and 340 series
1192 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1193 as XGI V3XT, V5, V8 and Z7.
1196 tristate "NeoMagic display support"
1197 depends on FB && PCI
1198 select FB_MODE_HELPERS
1199 select FB_CFB_FILLRECT
1200 select FB_CFB_COPYAREA
1201 select FB_CFB_IMAGEBLIT
1203 This driver supports notebooks with NeoMagic PCI chips.
1204 Say Y if you have such a graphics card.
1206 To compile this driver as a module, choose M here: the
1207 module will be called neofb.
1210 tristate "IMG Kyro support"
1211 depends on FB && PCI
1212 select FB_CFB_FILLRECT
1213 select FB_CFB_COPYAREA
1214 select FB_CFB_IMAGEBLIT
1216 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1219 To compile this driver as a module, choose M here: the
1220 module will be called kyrofb.
1223 tristate "3Dfx Banshee/Voodoo3 display support"
1224 depends on FB && PCI
1225 select FB_CFB_IMAGEBLIT
1226 select FB_CFB_FILLRECT
1227 select FB_CFB_COPYAREA
1229 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1230 chips. Say Y if you have such a graphics board.
1232 To compile this driver as a module, choose M here: the
1233 module will be called tdfxfb.
1235 config FB_3DFX_ACCEL
1236 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1237 depends on FB_3DFX && EXPERIMENTAL
1239 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1240 with acceleration functions.
1244 tristate "3Dfx Voodoo Graphics (sst1) support"
1245 depends on FB && PCI
1246 select FB_CFB_FILLRECT
1247 select FB_CFB_COPYAREA
1248 select FB_CFB_IMAGEBLIT
1250 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1251 Voodoo2 (cvg) based graphics card.
1253 To compile this driver as a module, choose M here: the
1254 module will be called sstfb.
1256 WARNING: Do not use any application that uses the 3D engine
1257 (namely glide) while using this driver.
1258 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1259 options and other important info support.
1262 tristate "Cyberblade/i1 support"
1263 depends on FB && PCI && X86_32 && !64BIT
1264 select FB_CFB_IMAGEBLIT
1267 This driver is supposed to support the Trident Cyberblade/i1
1268 graphics core integrated in the VIA VT8601A North Bridge,
1269 also known as VIA Apollo PLE133.
1272 - Developed, tested and working on EPIA 5000 and EPIA 800.
1273 - Does work reliable on all systems with CRT/LCD connected to
1275 - Should work on systems that do use the internal LCD port, but
1276 this is absolutely not tested.
1278 Character imageblit, copyarea and rectangle fill are hw accelerated,
1279 ypan scrolling is used by default.
1281 Please do read <file:Documentation/fb/cyblafb/*>.
1283 To compile this driver as a module, choose M here: the
1284 module will be called cyblafb.
1287 tristate "Trident support"
1288 depends on FB && PCI
1289 select FB_CFB_FILLRECT
1290 select FB_CFB_COPYAREA
1291 select FB_CFB_IMAGEBLIT
1293 This driver is supposed to support graphics boards with the
1294 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1295 but also on some motherboards. For more information, read
1296 <file:Documentation/fb/tridentfb.txt>
1298 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1301 Say Y if you have such a graphics board.
1304 To compile this driver as a module, choose M here: the
1305 module will be called tridentfb.
1307 config FB_TRIDENT_ACCEL
1308 bool "Trident Acceleration functions (EXPERIMENTAL)"
1309 depends on FB_TRIDENT && EXPERIMENTAL
1311 This will compile the Trident frame buffer device with
1312 acceleration functions.
1315 tristate "Permedia3 support"
1316 depends on FB && PCI && BROKEN
1318 This is the frame buffer device driver for the 3DLabs Permedia3
1319 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1320 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1321 and maybe other boards.
1324 bool "Au1100 LCD Driver"
1325 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1328 bool "Au1200 LCD Driver"
1329 depends on FB && MIPS && SOC_AU1200
1330 select FB_CFB_FILLRECT
1331 select FB_CFB_COPYAREA
1332 select FB_CFB_IMAGEBLIT
1334 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1335 various panels and CRTs by passing in kernel cmd line option
1336 au1200fb:panel=<name>.
1338 source "drivers/video/geode/Kconfig"
1341 bool "Creator/Creator3D/Elite3D support"
1342 depends on FB_SBUS && SPARC64
1343 select FB_CFB_COPYAREA
1344 select FB_CFB_IMAGEBLIT
1346 This is the frame buffer device driver for the Creator, Creator3D,
1347 and Elite3D graphics boards.
1350 bool "TCX (SS4/SS5 only) support"
1352 select FB_CFB_FILLRECT
1353 select FB_CFB_COPYAREA
1354 select FB_CFB_IMAGEBLIT
1356 This is the frame buffer device driver for the TCX 24/8bit frame
1360 bool "CGfourteen (SX) support"
1362 select FB_CFB_FILLRECT
1363 select FB_CFB_COPYAREA
1364 select FB_CFB_IMAGEBLIT
1366 This is the frame buffer device driver for the CGfourteen frame
1367 buffer on Desktop SPARCsystems with the SX graphics option.
1370 bool "P9100 (Sparcbook 3 only) support"
1372 select FB_CFB_FILLRECT
1373 select FB_CFB_COPYAREA
1374 select FB_CFB_IMAGEBLIT
1376 This is the frame buffer device driver for the P9100 card
1377 supported on Sparcbook 3 machines.
1380 bool "Leo (ZX) support"
1382 select FB_CFB_FILLRECT
1383 select FB_CFB_COPYAREA
1384 select FB_CFB_IMAGEBLIT
1386 This is the frame buffer device driver for the SBUS-based Sun ZX
1387 (leo) frame buffer cards.
1390 bool "PCI framebuffers"
1391 depends on (FB = y) && PCI && SPARC
1394 bool "IGA 168x display support"
1395 depends on SPARC32 && FB_PCI
1396 select FB_CFB_FILLRECT
1397 select FB_CFB_COPYAREA
1398 select FB_CFB_IMAGEBLIT
1400 This is the framebuffer device for the INTERGRAPHICS 1680 and
1401 successor frame buffer cards.
1404 tristate "HD64461 Frame Buffer support"
1405 depends on FB && HD64461
1406 select FB_CFB_FILLRECT
1407 select FB_CFB_COPYAREA
1408 select FB_CFB_IMAGEBLIT
1410 This is the frame buffer device driver for the Hitachi HD64461 LCD
1414 bool "PMAG-AA TURBOchannel framebuffer support"
1415 depends on (FB = y) && TC
1416 select FB_CFB_FILLRECT
1417 select FB_CFB_COPYAREA
1418 select FB_CFB_IMAGEBLIT
1420 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1421 used mainly in the MIPS-based DECstation series.
1424 bool "PMAG-BA TURBOchannel framebuffer support"
1425 depends on (FB = y) && TC
1426 select FB_CFB_FILLRECT
1427 select FB_CFB_COPYAREA
1428 select FB_CFB_IMAGEBLIT
1430 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1431 used mainly in the MIPS-based DECstation series.
1434 bool "PMAGB-B TURBOchannel framebuffer support"
1435 depends on (FB = y) && TC
1436 select FB_CFB_FILLRECT
1437 select FB_CFB_COPYAREA
1438 select FB_CFB_IMAGEBLIT
1440 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1441 in the MIPS-based DECstation series. The card is currently only
1442 supported in 1280x1024x8 mode.
1445 bool "Maxine (Personal DECstation) onboard framebuffer support"
1446 depends on (FB = y) && MACH_DECSTATION
1447 select FB_CFB_FILLRECT
1448 select FB_CFB_COPYAREA
1449 select FB_CFB_IMAGEBLIT
1451 Support for the onboard framebuffer (1024x768x8) in the Personal
1452 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1456 bool "TMPTX3912/PR31700 frame buffer support"
1457 depends on (FB = y) && NINO
1458 select FB_CFB_FILLRECT
1459 select FB_CFB_COPYAREA
1460 select FB_CFB_IMAGEBLIT
1462 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1463 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1465 Say Y here to enable kernel support for the on-board framebuffer.
1468 bool "G364 frame buffer support"
1469 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1470 select FB_CFB_FILLRECT
1471 select FB_CFB_COPYAREA
1472 select FB_CFB_IMAGEBLIT
1474 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1475 Olivetti M700-10 systems.
1478 bool "Motorola 68328 native frame buffer support"
1479 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1482 select FB_CFB_IMAGEBLIT
1484 Say Y here if you want to support the built-in frame buffer of
1485 the Motorola 68328 CPU family.
1488 tristate "PXA LCD framebuffer support"
1489 depends on FB && ARCH_PXA
1490 select FB_CFB_FILLRECT
1491 select FB_CFB_COPYAREA
1492 select FB_CFB_IMAGEBLIT
1494 Frame buffer driver for the built-in LCD controller in the Intel
1497 This driver is also available as a module ( = code which can be
1498 inserted and removed from the running kernel whenever you want). The
1499 module will be called pxafb. If you want to compile it as a module,
1500 say M here and read <file:Documentation/modules.txt>.
1504 config FB_PXA_PARAMETERS
1505 bool "PXA LCD command line parameters"
1509 Enable the use of kernel command line or module parameters
1510 to configure the physical properties of the LCD panel when
1511 using the PXA LCD driver.
1513 This option allows you to override the panel parameters
1514 supplied by the platform in order to support multiple
1515 different models of flatpanel. If you will only be using a
1516 single model of flatpanel then you can safely leave this
1519 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1522 tristate "W100 frame buffer support"
1523 depends on FB && PXA_SHARPSL
1524 select FB_CFB_FILLRECT
1525 select FB_CFB_COPYAREA
1526 select FB_CFB_IMAGEBLIT
1528 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1530 This driver is also available as a module ( = code which can be
1531 inserted and removed from the running kernel whenever you want). The
1532 module will be called w100fb. If you want to compile it as a module,
1533 say M here and read <file:Documentation/modules.txt>.
1538 tristate "S3C2410 LCD framebuffer support"
1539 depends on FB && ARCH_S3C2410
1540 select FB_CFB_FILLRECT
1541 select FB_CFB_COPYAREA
1542 select FB_CFB_IMAGEBLIT
1544 Frame buffer driver for the built-in LCD controller in the Samsung
1547 This driver is also available as a module ( = code which can be
1548 inserted and removed from the running kernel whenever you want). The
1549 module will be called s3c2410fb. If you want to compile it as a module,
1550 say M here and read <file:Documentation/modules.txt>.
1553 config FB_S3C2410_DEBUG
1554 bool "S3C2410 lcd debug messages"
1555 depends on FB_S3C2410
1557 Turn on debugging messages. Note that you can set/unset at run time
1561 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1563 select FB_CFB_FILLRECT
1564 select FB_CFB_COPYAREA
1565 select FB_CFB_IMAGEBLIT
1567 This is a `virtual' frame buffer device. It operates on a chunk of
1568 unswappable kernel memory instead of on the memory of a graphics
1569 board. This means you cannot see any output sent to this frame
1570 buffer device, while it does consume precious memory. The main use
1571 of this frame buffer device is testing and debugging the frame
1572 buffer subsystem. Do NOT enable it for normal systems! To protect
1573 the innocent, it has to be enabled explicitly at boot time using the
1574 kernel option `video=vfb:'.
1576 To compile this driver as a module, choose M here: the
1577 module will be called vfb.
1581 source "drivers/video/console/Kconfig"
1584 if FB || SGI_NEWPORT_CONSOLE
1585 source "drivers/video/logo/Kconfig"
1589 source "drivers/video/backlight/Kconfig"