5 menu "Graphics support"
8 tristate "Support for frame buffer devices"
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
41 config FB_CFB_FILLRECT
46 Include the cfb_fillrect function for generic software rectangle
47 filling. This is used by drivers that don't provide their own
48 (accelerated) version.
50 config FB_CFB_COPYAREA
55 Include the cfb_copyarea function for generic software area copying.
56 This is used by drivers that don't provide their own (accelerated)
59 config FB_CFB_IMAGEBLIT
64 Include the cfb_imageblit function for generic software image
65 blitting. This is used by drivers that don't provide their own
66 (accelerated) version.
73 Include the soft_cursor function for generic software cursor support.
74 This is used by drivers that don't provide their own (accelerated)
82 config FB_MODE_HELPERS
83 bool "Enable Video Mode Handling Helpers"
87 This enables functions for handling video modes using the
88 Generalized Timing Formula and the EDID parser. A few drivers rely
89 on this feature such as the radeonfb, rivafb, and the i810fb. If
90 your driver does not take advantage of this feature, choosing Y will
91 just increase the kernel size by about 5K.
93 config FB_TILEBLITTING
94 bool "Enable Tile Blitting Support"
98 This enables tile blitting. Tile blitting is a drawing technique
99 where the screen is divided into rectangular sections (tiles), whereas
100 the standard blitting divides the screen into pixels. Because the
101 default drawing element is a tile, drawing functions will be passed
102 parameters in terms of number of tiles instead of number of pixels.
103 For example, to draw a single character, instead of using bitmaps,
104 an index to an array of bitmaps will be used. To clear or move a
105 rectangular section of a screen, the rectangle will be described in
106 terms of number of tiles in the x- and y-axis.
108 This is particularly important to one driver, matroxfb. If
112 tristate "Cirrus Logic support"
113 depends on FB && (ZORRO || PCI)
114 select FB_CFB_FILLRECT
115 select FB_CFB_COPYAREA
116 select FB_CFB_IMAGEBLIT
117 select FB_SOFT_CURSOR
119 This enables support for Cirrus Logic GD542x/543x based boards on
120 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
122 If you have a PCI-based system, this enables support for these
123 chips: GD-543x, GD-544x, GD-5480.
125 Please read the file <file:Documentation/fb/cirrusfb.txt>.
127 Say N unless you have such a graphics board or plan to get one
128 before you next recompile the kernel.
131 tristate "Permedia2 support"
132 depends on FB && ((AMIGA && BROKEN) || PCI)
133 select FB_CFB_FILLRECT
134 select FB_CFB_COPYAREA
135 select FB_CFB_IMAGEBLIT
136 select FB_SOFT_CURSOR
138 This is the frame buffer device driver for the Permedia2 AGP frame
139 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
141 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
143 config FB_PM2_FIFO_DISCONNECT
144 bool "enable FIFO disconnect feature"
145 depends on FB_PM2 && PCI
147 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
150 tristate "ARM PrimeCell PL110 support"
151 depends on FB && ARM && ARM_AMBA
152 select FB_CFB_FILLRECT
153 select FB_CFB_COPYAREA
154 select FB_CFB_IMAGEBLIT
155 select FB_SOFT_CURSOR
157 This framebuffer device driver is for the ARM PrimeCell PL110
158 Colour LCD controller. ARM PrimeCells provide the building
159 blocks for System on a Chip devices.
161 If you want to compile this as a module (=code which can be
162 inserted into and removed from the running kernel), say M
163 here and read <file:Documentation/modules.txt>. The module
164 will be called amba-clcd.
167 bool "Acorn VIDC support"
168 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
169 select FB_CFB_FILLRECT
170 select FB_CFB_COPYAREA
171 select FB_CFB_IMAGEBLIT
172 select FB_SOFT_CURSOR
174 This is the frame buffer device driver for the Acorn VIDC graphics
175 hardware found in Acorn RISC PCs and other ARM-based machines. If
179 bool "CLPS711X LCD support"
180 depends on (FB = y) && ARM && ARCH_CLPS711X
181 select FB_CFB_FILLRECT
182 select FB_CFB_COPYAREA
183 select FB_CFB_IMAGEBLIT
184 select FB_SOFT_CURSOR
186 Say Y to enable the Framebuffer driver for the CLPS7111 and
190 bool "SA-1100 LCD support"
191 depends on (FB = y) && ARM && ARCH_SA1100
192 select FB_CFB_FILLRECT
193 select FB_CFB_COPYAREA
194 select FB_CFB_IMAGEBLIT
195 select FB_SOFT_CURSOR
197 This is a framebuffer device for the SA-1100 LCD Controller.
198 See <http://www.linux-fbdev.org/> for information on framebuffer
201 If you plan to use the LCD display with your SA-1100 system, say
205 tristate "Motorola i.MX LCD support"
206 depends on FB && ARM && ARCH_IMX
207 select FB_CFB_FILLRECT
208 select FB_CFB_COPYAREA
209 select FB_CFB_IMAGEBLIT
210 select FB_SOFT_CURSOR
213 tristate "CyberPro 2000/2010/5000 support"
214 depends on FB && PCI && (BROKEN || !SPARC64)
215 select FB_CFB_FILLRECT
216 select FB_CFB_COPYAREA
217 select FB_CFB_IMAGEBLIT
218 select FB_SOFT_CURSOR
220 This enables support for the Integraphics CyberPro 20x0 and 5000
221 VGA chips used in the Rebel.com Netwinder and other machines.
222 Say Y if you have a NetWinder or a graphics card containing this
223 device, otherwise say N.
227 depends on (FB = y) && APOLLO
229 select FB_CFB_FILLRECT
230 select FB_CFB_IMAGEBLIT
231 select FB_SOFT_CURSOR
235 depends on (FB = y) && Q40
237 select FB_CFB_FILLRECT
238 select FB_CFB_COPYAREA
239 select FB_CFB_IMAGEBLIT
240 select FB_SOFT_CURSOR
243 tristate "Amiga native chipset support"
244 depends on FB && AMIGA
245 select FB_SOFT_CURSOR
247 This is the frame buffer device driver for the builtin graphics
248 chipset found in Amigas.
250 To compile this driver as a module, choose M here: the
251 module will be called amifb.
254 bool "Amiga OCS chipset support"
257 This enables support for the original Agnus and Denise video chips,
258 found in the Amiga 1000 and most A500's and A2000's. If you intend
259 to run Linux on any of these systems, say Y; otherwise say N.
262 bool "Amiga ECS chipset support"
265 This enables support for the Enhanced Chip Set, found in later
266 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
267 you intend to run Linux on any of these systems, say Y; otherwise
271 bool "Amiga AGA chipset support"
274 This enables support for the Advanced Graphics Architecture (also
275 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
276 and CD32. If you intend to run Linux on any of these systems, say Y;
280 tristate "Amiga CyberVision 64 support"
281 depends on FB && ZORRO && BROKEN
282 select FB_CFB_FILLRECT
283 select FB_CFB_COPYAREA
284 select FB_CFB_IMAGEBLIT
285 select FB_SOFT_CURSOR
287 This enables support for the Cybervision 64 graphics card from
288 Phase5. Please note that its use is not all that intuitive (i.e. if
289 you have any questions, be sure to ask!). Say N unless you have a
290 Cybervision 64 or plan to get one before you next recompile the
291 kernel. Please note that this driver DOES NOT support the
292 Cybervision 64/3D card, as they use incompatible video chips.
295 bool "Amiga CyberVision 64/3D support "
296 depends on (FB = y) && ZORRO && BROKEN
297 select FB_CFB_FILLRECT
298 select FB_CFB_COPYAREA
299 select FB_CFB_IMAGEBLIT
300 select FB_SOFT_CURSOR
302 This enables support for the Cybervision 64/3D graphics card from
303 Phase5. Please note that its use is not all that intuitive (i.e. if
304 you have any questions, be sure to ask!). Say N unless you have a
305 Cybervision 64/3D or plan to get one before you next recompile the
306 kernel. Please note that this driver DOES NOT support the older
307 Cybervision 64 card, as they use incompatible video chips.
310 tristate "Amiga Retina Z3 support"
311 depends on (FB = y) && ZORRO && BROKEN
313 This enables support for the Retina Z3 graphics card. Say N unless
314 you have a Retina Z3 or plan to get one before you next recompile
318 bool "Amiga FrameMaster II/Rainbow II support"
319 depends on (FB = y) && ZORRO
320 select FB_CFB_FILLRECT
321 select FB_CFB_COPYAREA
322 select FB_CFB_IMAGEBLIT
323 select FB_SOFT_CURSOR
325 This is the frame buffer device driver for the Amiga FrameMaster
326 card from BSC (exhibited 1992 but not shipped as a CBM product).
329 tristate "Arc Monochrome LCD board support"
331 select FB_CFB_FILLRECT
332 select FB_CFB_COPYAREA
333 select FB_CFB_IMAGEBLIT
334 select FB_SOFT_CURSOR
336 This enables support for the Arc Monochrome LCD board. The board
337 is based on the KS-108 lcd controller and is typically a matrix
338 of 2*n chips. This driver was tested with a 128x64 panel. This
339 driver supports it for use with x86 SBCs through a 16 bit GPIO
340 interface (8 bit data, 8 bit control). If you anticpate using
341 this driver, say Y or M; otherwise say N. You must specify the
342 GPIO IO address to be used for setting control and data.
345 bool "Atari native chipset support"
346 depends on (FB = y) && ATARI && BROKEN
348 This is the frame buffer device driver for the builtin graphics
349 chipset found in Ataris.
352 bool "Open Firmware frame buffer device support"
353 depends on (FB = y) && (PPC64 || PPC_OF)
354 select FB_CFB_FILLRECT
355 select FB_CFB_COPYAREA
356 select FB_CFB_IMAGEBLIT
357 select FB_SOFT_CURSOR
360 Say Y if you want support with Open Firmware for your graphics
364 bool "Apple \"control\" display support"
365 depends on (FB = y) && PPC_PMAC
366 select FB_CFB_FILLRECT
367 select FB_CFB_COPYAREA
368 select FB_CFB_IMAGEBLIT
369 select FB_SOFT_CURSOR
372 This driver supports a frame buffer for the graphics adapter in the
373 Power Macintosh 7300 and others.
376 bool "Apple \"platinum\" display support"
377 depends on (FB = y) && PPC_PMAC
378 select FB_CFB_FILLRECT
379 select FB_CFB_COPYAREA
380 select FB_CFB_IMAGEBLIT
381 select FB_SOFT_CURSOR
384 This driver supports a frame buffer for the "platinum" graphics
385 adapter in some Power Macintoshes.
388 bool "Apple \"valkyrie\" display support"
389 depends on (FB = y) && (MAC || PPC_PMAC)
390 select FB_CFB_FILLRECT
391 select FB_CFB_COPYAREA
392 select FB_CFB_IMAGEBLIT
393 select FB_SOFT_CURSOR
396 This driver supports a frame buffer for the "valkyrie" graphics
397 adapter in some Power Macintoshes.
400 bool "Chips 65550 display support"
401 depends on (FB = y) && PPC
402 select FB_CFB_FILLRECT
403 select FB_CFB_COPYAREA
404 select FB_CFB_IMAGEBLIT
405 select FB_SOFT_CURSOR
407 This is the frame buffer device driver for the Chips & Technologies
408 65550 graphics chip in PowerBooks.
411 bool "Asiliant (Chips) 69000 display support"
412 depends on (FB = y) && PCI
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
416 select FB_SOFT_CURSOR
419 bool "IMS Twin Turbo display support"
420 depends on (FB = y) && PCI
421 select FB_CFB_IMAGEBLIT
422 select FB_SOFT_CURSOR
423 select FB_MACMODES if PPC
425 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
426 many Macintosh and compatible computers.
429 tristate "VGA 16-color graphics support"
430 depends on FB && (X86 || PPC)
431 select FB_CFB_FILLRECT
432 select FB_CFB_COPYAREA
433 select FB_CFB_IMAGEBLIT
434 select FB_SOFT_CURSOR
436 This is the frame buffer device driver for VGA 16 color graphic
437 cards. Say Y if you have such a card.
439 To compile this driver as a module, choose M here: the
440 module will be called vga16fb.
443 tristate "HP STI frame buffer device support"
444 depends on FB && PARISC
445 select FB_CFB_FILLRECT
446 select FB_CFB_COPYAREA
447 select FB_CFB_IMAGEBLIT
448 select FB_SOFT_CURSOR
451 STI refers to the HP "Standard Text Interface" which is a set of
452 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
453 Enabling this option will implement the linux framebuffer device
454 using calls to the STI BIOS routines for initialisation.
456 If you enable this option, you will get a planar framebuffer device
457 /dev/fb which will work on the most common HP graphic cards of the
458 NGLE family, including the artist chips (in the 7xx and Bxxx series),
459 HCRX, HCRX24, CRX, CRX24 and VisEG series.
461 It is safe to enable this option, so you should probably say "Y".
464 bool "Generic Macintosh display support"
465 depends on (FB = y) && MAC
466 select FB_CFB_FILLRECT
467 select FB_CFB_COPYAREA
468 select FB_CFB_IMAGEBLIT
469 select FB_SOFT_CURSOR
472 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
475 depends on (FB = y) && HP300
476 select FB_CFB_FILLRECT
477 select FB_CFB_IMAGEBLIT
478 select FB_SOFT_CURSOR
482 tristate "TGA framebuffer support"
483 depends on FB && ALPHA
484 select FB_CFB_FILLRECT
485 select FB_CFB_COPYAREA
486 select FB_CFB_IMAGEBLIT
487 select FB_SOFT_CURSOR
489 This is the frame buffer device driver for generic TGA graphic
490 cards. Say Y if you have one of those.
493 bool "VESA VGA graphics support"
494 depends on (FB = y) && X86
495 select FB_CFB_FILLRECT
496 select FB_CFB_COPYAREA
497 select FB_CFB_IMAGEBLIT
498 select FB_SOFT_CURSOR
500 This is the frame buffer device driver for generic VESA 2.0
501 compliant graphic cards. The older VESA 1.2 cards are not supported.
502 You will get a boot time penguin logo at no additional cost. Please
503 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
511 tristate "Hercules mono graphics support"
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
516 select FB_SOFT_CURSOR
518 Say Y here if you have a Hercules mono graphics card.
520 To compile this driver as a module, choose M here: the
521 module will be called hgafb.
523 As this card technology is 15 years old, most people will answer N
527 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
528 depends on FB_HGA && EXPERIMENTAL
530 This will compile the Hercules mono graphics with
531 acceleration functions.
536 depends on (FB = y) && X86
540 tristate "SGI Visual Workstation framebuffer support"
541 depends on FB && X86_VISWS
542 select FB_CFB_FILLRECT
543 select FB_CFB_COPYAREA
544 select FB_CFB_IMAGEBLIT
545 select FB_SOFT_CURSOR
547 SGI Visual Workstation support for framebuffer graphics.
550 bool "SGI Graphics Backend frame buffer support"
551 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
552 select FB_CFB_FILLRECT
553 select FB_CFB_COPYAREA
554 select FB_CFB_IMAGEBLIT
555 select FB_SOFT_CURSOR
557 This is the frame buffer device driver for SGI Graphics Backend.
558 This chip is used in SGI O2 and Visual Workstation 320/540.
561 int "Video memory size in MB"
565 This is the amount of memory reserved for the framebuffer,
566 which can be any value between 1MB and 8MB.
570 depends on (FB = y) && VISWS
574 bool "Sun3 framebuffer support"
575 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
579 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
580 select FB_CFB_FILLRECT
581 select FB_CFB_COPYAREA
582 select FB_CFB_IMAGEBLIT
583 select FB_SOFT_CURSOR
585 This is the frame buffer device driver for the BWtwo frame buffer.
588 bool "CGthree support"
589 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
590 select FB_CFB_COPYAREA
591 select FB_CFB_IMAGEBLIT
592 select FB_SOFT_CURSOR
594 This is the frame buffer device driver for the CGthree frame buffer.
597 bool "CGsix (GX,TurboGX) support"
598 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
599 select FB_CFB_COPYAREA
600 select FB_CFB_IMAGEBLIT
601 select FB_SOFT_CURSOR
603 This is the frame buffer device driver for the CGsix (GX, TurboGX)
607 tristate "NEC PowerVR 2 display support"
608 depends on FB && SH_DREAMCAST
609 select FB_CFB_FILLRECT
610 select FB_CFB_COPYAREA
611 select FB_CFB_IMAGEBLIT
612 select FB_SOFT_CURSOR
614 Say Y here if you have a PowerVR 2 card in your box. If you plan to
615 run linux on your Dreamcast, you will have to say Y here.
616 This driver may or may not work on other PowerVR 2 cards, but is
617 totally untested. Use at your own risk. If unsure, say N.
619 To compile this driver as a module, choose M here: the
620 module will be called pvr2fb.
622 You can pass several parameters to the driver at boot time or at
623 module load time. The parameters look like "video=pvr2:XXX", where
624 the meaning of XXX can be found at the end of the main source file
625 (<file:drivers/video/pvr2fb.c>). Please see the file
626 <file:Documentation/fb/pvr2fb.txt>.
629 bool "Epson 1355 framebuffer support"
630 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
631 select FB_CFB_FILLRECT
632 select FB_CFB_COPYAREA
633 select FB_CFB_IMAGEBLIT
634 select FB_SOFT_CURSOR
636 Build in support for the SED1355 Epson Research Embedded RAMDAC
637 LCD/CRT Controller (since redesignated as the S1D13505) as a
638 framebuffer. Product specs at
639 <http://www.erd.epson.com/vdc/html/products.htm>.
642 tristate "nVidia Framebuffer Support"
644 select I2C_ALGOBIT if FB_NVIDIA_I2C
645 select I2C if FB_NVIDIA_I2C
646 select FB_MODE_HELPERS
647 select FB_CFB_FILLRECT
648 select FB_CFB_COPYAREA
649 select FB_CFB_IMAGEBLIT
650 select FB_SOFT_CURSOR
652 This driver supports graphics boards with the nVidia chips, TNT
653 and newer. For very old chipsets, such as the RIVA128, then use
655 Say Y if you have such a graphics board.
657 To compile this driver as a module, choose M here: the
658 module will be called nvidiafb.
661 bool "Enable DDC Support"
662 depends on FB_NVIDIA && !PPC_OF
664 This enables I2C support for nVidia Chipsets. This is used
665 only for getting EDID information from the attached display
666 allowing for robust video mode handling and switching.
668 Because fbdev-2.6 requires that drivers must be able to
669 independently validate video mode parameters, you should say Y
673 tristate "nVidia Riva support"
675 select I2C_ALGOBIT if FB_RIVA_I2C
676 select I2C if FB_RIVA_I2C
677 select FB_MODE_HELPERS
678 select FB_CFB_FILLRECT
679 select FB_CFB_COPYAREA
680 select FB_CFB_IMAGEBLIT
682 This driver supports graphics boards with the nVidia Riva/Geforce
684 Say Y if you have such a graphics board.
686 To compile this driver as a module, choose M here: the
687 module will be called rivafb.
690 bool "Enable DDC Support"
693 This enables I2C support for nVidia Chipsets. This is used
694 only for getting EDID information from the attached display
695 allowing for robust video mode handling and switching.
697 Because fbdev-2.6 requires that drivers must be able to
698 independently validate video mode parameters, you should say Y
702 bool "Lots of debug output from Riva(nVidia) driver"
706 Say Y here if you want the Riva driver to output all sorts
707 of debugging informations to provide to the maintainer when
708 something goes wrong.
711 tristate "Intel 810/815 support (EXPERIMENTAL)"
712 depends on FB && EXPERIMENTAL && PCI && X86_32
715 select FB_MODE_HELPERS
716 select FB_CFB_FILLRECT
717 select FB_CFB_COPYAREA
718 select FB_CFB_IMAGEBLIT
720 This driver supports the on-board graphics built in to the Intel 810
721 and 815 chipsets. Say Y if you have and plan to use such a board.
723 To compile this driver as a module, choose M here: the
724 module will be called i810fb.
726 For more information, please read
727 <file:Documentation/fb/intel810.txt>
730 bool "use VESA Generalized Timing Formula"
733 If you say Y, then the VESA standard, Generalized Timing Formula
734 or GTF, will be used to calculate the required video timing values
735 per video mode. Since the GTF allows nondiscrete timings
736 (nondiscrete being a range of values as opposed to discrete being a
737 set of values), you'll be able to use any combination of horizontal
738 and vertical resolutions, and vertical refresh rates without having
739 to specify your own timing parameters. This is especially useful
740 to maximize the performance of an aging display, or if you just
741 have a display with nonstandard dimensions. A VESA compliant
742 monitor is recommended, but can still work with non-compliant ones.
743 If you need or want this, then select this option. The timings may
744 not be compliant with Intel's recommended values. Use at your own
747 If you say N, the driver will revert to discrete video timings
748 using a set recommended by Intel in their documentation.
753 bool "Enable DDC Support"
754 depends on FB_I810 && FB_I810_GTF
760 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
761 depends on FB && EXPERIMENTAL && PCI && X86_32
764 select FB_MODE_HELPERS
765 select FB_CFB_FILLRECT
766 select FB_CFB_COPYAREA
767 select FB_CFB_IMAGEBLIT
768 select FB_SOFT_CURSOR
770 This driver supports the on-board graphics built in to the Intel
771 830M/845G/852GM/855GM/865G chipsets.
772 Say Y if you have and plan to use such a board.
774 To compile this driver as a module, choose M here: the
775 module will be called intelfb.
777 config FB_INTEL_DEBUG
778 bool "Intel driver Debug Messages"
781 Say Y here if you want the Intel driver to output all sorts
782 of debugging informations to provide to the maintainer when
783 something goes wrong.
786 tristate "Matrox acceleration"
788 select FB_CFB_FILLRECT
789 select FB_CFB_COPYAREA
790 select FB_CFB_IMAGEBLIT
791 select FB_SOFT_CURSOR
792 select FB_TILEBLITTING
793 select FB_MACMODES if PPC_PMAC
795 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
796 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
797 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
798 Matrox G400, G450 or G550 card in your box.
800 To compile this driver as a module, choose M here: the
801 module will be called matroxfb.
803 You can pass several parameters to the driver at boot time or at
804 module load time. The parameters look like "video=matrox:XXX", and
805 are described in <file:Documentation/fb/matroxfb.txt>.
807 config FB_MATROX_MILLENIUM
808 bool "Millennium I/II support"
811 Say Y here if you have a Matrox Millennium or Matrox Millennium II
812 video card. If you select "Advanced lowlevel driver options" below,
813 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
814 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
815 also use font widths different from 8.
817 config FB_MATROX_MYSTIQUE
818 bool "Mystique support"
821 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
822 video card. If you select "Advanced lowlevel driver options" below,
823 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
824 packed pixel and 32 bpp packed pixel. You can also use font widths
828 bool "G100/G200/G400/G450/G550 support"
831 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
832 video card. If you select "Advanced lowlevel driver options", you
833 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
834 pixel and 32 bpp packed pixel. You can also use font widths
837 If you need support for G400 secondary head, you must first say Y to
838 "I2C support" in the character devices section, and then to
839 "Matrox I2C support" and "G400 second head support" here in the
840 framebuffer section. G450/G550 secondary head and digital output
841 are supported without additional modules.
843 The driver starts in monitor mode. You must use the matroxset tool
844 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
845 swap primary and secondary head outputs, or to change output mode.
846 Secondary head driver always start in 640x480 resolution and you
847 must use fbset to change it.
849 Do not forget that second head supports only 16 and 32 bpp
850 packed pixels, so it is a good idea to compile them into the kernel
851 too. You can use only some font widths, as the driver uses generic
852 painting procedures (the secondary head does not use acceleration
855 G450/G550 hardware can display TV picture only from secondary CRTC,
856 and it performs no scaling, so picture must have 525 or 625 lines.
859 tristate "Matrox I2C support"
860 depends on FB_MATROX && I2C
863 This drivers creates I2C buses which are needed for accessing the
864 DDC (I2C) bus present on all Matroxes, an I2C bus which
865 interconnects Matrox optional devices, like MGA-TVO on G200 and
866 G400, and the secondary head DDC bus, present on G400 only.
868 You can say Y or M here if you want to experiment with monitor
869 detection code. You must say Y or M here if you want to use either
870 second head of G400 or MGA-TVO on G200 or G400.
872 If you compile it as module, it will create a module named
875 config FB_MATROX_MAVEN
876 tristate "G400 second head support"
877 depends on FB_MATROX_G && FB_MATROX_I2C
879 WARNING !!! This support does not work with G450 !!!
881 Say Y or M here if you want to use a secondary head (meaning two
882 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
883 head is not compatible with accelerated XFree 3.3.x SVGA servers -
884 secondary head output is blanked while you are in X. With XFree
885 3.9.17 preview you can use both heads if you use SVGA over fbdev or
886 the fbdev driver on first head and the fbdev driver on second head.
888 If you compile it as module, two modules are created,
889 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
890 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
891 also load i2c-matroxfb to get it to run.
893 The driver starts in monitor mode and you must use the matroxset
895 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
896 PAL or NTSC or to swap primary and secondary head outputs.
897 Secondary head driver also always start in 640x480 resolution, you
898 must use fbset to change it.
900 Also do not forget that second head supports only 16 and 32 bpp
901 packed pixels, so it is a good idea to compile them into the kernel
902 too. You can use only some font widths, as the driver uses generic
903 painting procedures (the secondary head does not use acceleration
906 config FB_MATROX_MULTIHEAD
907 bool "Multihead support"
910 Say Y here if you have more than one (supported) Matrox device in
911 your computer and you want to use all of them for different monitors
912 ("multihead"). If you have only one device, you should say N because
913 the driver compiled with Y is larger and a bit slower, especially on
916 If you said M to "Matrox unified accelerated driver" and N here, you
917 will still be able to use several Matrox devices simultaneously:
918 insert several instances of the module matroxfb into the kernel
919 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
920 for the different Matrox devices. This method is slightly faster but
921 uses 40 KB of kernel memory per Matrox card.
923 There is no need for enabling 'Matrox multihead support' if you have
924 only one Matrox card in the box.
927 tristate "ATI Radeon display support (Old driver)"
929 select FB_CFB_FILLRECT
930 select FB_CFB_COPYAREA
931 select FB_CFB_IMAGEBLIT
932 select FB_SOFT_CURSOR
933 select FB_MACMODES if PPC
935 Choose this option if you want to use an ATI Radeon graphics card as
936 a framebuffer device. There are both PCI and AGP versions. You
937 don't need to choose this to run the Radeon in plain VGA mode.
938 There is a product page at
939 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
942 tristate "ATI Radeon display support"
944 select I2C_ALGOBIT if FB_RADEON_I2C
945 select I2C if FB_RADEON_I2C
946 select FB_MODE_HELPERS
947 select FB_CFB_FILLRECT
948 select FB_CFB_COPYAREA
949 select FB_CFB_IMAGEBLIT
950 select FB_SOFT_CURSOR
951 select FB_MACMODES if PPC_OF
953 Choose this option if you want to use an ATI Radeon graphics card as
954 a framebuffer device. There are both PCI and AGP versions. You
955 don't need to choose this to run the Radeon in plain VGA mode.
957 If you say Y here and want DDC/I2C support you must first say Y to
958 "I2C support" and "I2C bit-banging support" in the character devices
961 If you say M here then "I2C support" and "I2C bit-banging support"
962 can be build either as modules or built-in.
964 There is a product page at
965 http://apps.ati.com/ATIcompare/
967 bool "DDC/I2C for ATI Radeon support"
971 Say Y here if you want DDC/I2C support for your Radeon board.
973 config FB_RADEON_DEBUG
974 bool "Lots of debug output from Radeon driver"
978 Say Y here if you want the Radeon driver to output all sorts
979 of debugging informations to provide to the maintainer when
980 something goes wrong.
983 tristate "ATI Rage128 display support"
985 select FB_CFB_FILLRECT
986 select FB_CFB_COPYAREA
987 select FB_CFB_IMAGEBLIT
988 select FB_SOFT_CURSOR
989 select FB_MACMODES if PPC_PMAC
991 This driver supports graphics boards with the ATI Rage128 chips.
992 Say Y if you have such a graphics board and read
993 <file:Documentation/fb/aty128fb.txt>.
995 To compile this driver as a module, choose M here: the
996 module will be called aty128fb.
999 tristate "ATI Mach64 display support" if PCI || ATARI
1001 select FB_CFB_FILLRECT
1002 select FB_CFB_COPYAREA
1003 select FB_CFB_IMAGEBLIT
1004 select FB_SOFT_CURSOR
1005 select FB_MACMODES if PPC
1007 This driver supports graphics boards with the ATI Mach64 chips.
1008 Say Y if you have such a graphics board.
1010 To compile this driver as a module, choose M here: the
1011 module will be called atyfb.
1014 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1015 depends on PCI && FB_ATY
1016 default y if SPARC64 && FB_PCI
1018 Say Y here to support use of ATI's 64-bit Rage boards (or other
1019 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1020 framebuffer device. The ATI product support page for these boards
1021 is at <http://support.ati.com/products/pc/mach64/>.
1023 config FB_ATY_GENERIC_LCD
1024 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1025 depends on FB_ATY_CT
1027 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1028 Rage XC, or Rage XL chipset.
1030 config FB_ATY_XL_INIT
1031 bool "Rage XL No-BIOS Init support"
1032 depends on FB_ATY_CT
1034 Say Y here to support booting a Rage XL without BIOS support.
1037 bool "Mach64 GX support" if PCI
1041 Say Y here to support use of the ATI Mach64 Graphics Expression
1042 board (or other boards based on the Mach64 GX chipset) as a
1043 framebuffer device. The ATI product support page for these boards
1045 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1048 bool "S3 Trio display support"
1049 depends on (FB = y) && PPC && BROKEN
1051 If you have a S3 Trio say Y. Say N for S3 Virge.
1054 tristate "S3 Savage support"
1055 depends on FB && PCI && EXPERIMENTAL
1056 select I2C_ALGOBIT if FB_SAVAGE_I2C
1057 select I2C if FB_SAVAGE_I2C
1058 select FB_MODE_HELPERS
1059 select FB_CFB_FILLRECT
1060 select FB_CFB_COPYAREA
1061 select FB_CFB_IMAGEBLIT
1062 select FB_SOFT_CURSOR
1064 This driver supports notebooks and computers with S3 Savage PCI/AGP
1067 Say Y if you have such a graphics card.
1069 To compile this driver as a module, choose M here; the module
1070 will be called savagefb.
1072 config FB_SAVAGE_I2C
1073 bool "Enable DDC2 Support"
1074 depends on FB_SAVAGE
1076 This enables I2C support for S3 Savage Chipsets. This is used
1077 only for getting EDID information from the attached display
1078 allowing for robust video mode handling and switching.
1080 Because fbdev-2.6 requires that drivers must be able to
1081 independently validate video mode parameters, you should say Y
1084 config FB_SAVAGE_ACCEL
1085 bool "Enable Console Acceleration"
1086 depends on FB_SAVAGE
1089 This option will compile in console acceleration support. If
1090 the resulting framebuffer console has bothersome glitches, then
1094 tristate "SiS/XGI display support"
1095 depends on FB && PCI
1096 select FB_CFB_FILLRECT
1097 select FB_CFB_COPYAREA
1098 select FB_CFB_IMAGEBLIT
1099 select FB_SOFT_CURSOR
1101 This is the frame buffer device driver for the SiS 300, 315, 330
1102 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1103 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1105 To compile this driver as a module, choose M here; the module
1106 will be called sisfb.
1109 bool "SiS 300 series support"
1112 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1115 bool "SiS 315/330/340 series and XGI support"
1118 Say Y here to support use of the SiS 315, 330 and 340 series
1119 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1120 as XGI V3XT, V5, V8 and Z7.
1123 tristate "NeoMagic display support"
1124 depends on FB && PCI
1125 select FB_MODE_HELPERS
1126 select FB_CFB_FILLRECT
1127 select FB_CFB_COPYAREA
1128 select FB_CFB_IMAGEBLIT
1129 select FB_SOFT_CURSOR
1131 This driver supports notebooks with NeoMagic PCI chips.
1132 Say Y if you have such a graphics card.
1134 To compile this driver as a module, choose M here: the
1135 module will be called neofb.
1138 tristate "IMG Kyro support"
1139 depends on FB && PCI
1140 select FB_CFB_FILLRECT
1141 select FB_CFB_COPYAREA
1142 select FB_CFB_IMAGEBLIT
1143 select FB_SOFT_CURSOR
1145 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1148 To compile this driver as a module, choose M here: the
1149 module will be called kyrofb.
1152 tristate "3Dfx Banshee/Voodoo3 display support"
1153 depends on FB && PCI
1154 select FB_CFB_IMAGEBLIT
1155 select FB_CFB_FILLRECT
1156 select FB_CFB_COPYAREA
1157 select FB_SOFT_CURSOR
1159 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1160 chips. Say Y if you have such a graphics board.
1162 To compile this driver as a module, choose M here: the
1163 module will be called tdfxfb.
1165 config FB_3DFX_ACCEL
1166 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1167 depends on FB_3DFX && EXPERIMENTAL
1169 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1170 with acceleration functions.
1174 tristate "3Dfx Voodoo Graphics (sst1) support"
1175 depends on FB && PCI
1176 select FB_CFB_FILLRECT
1177 select FB_CFB_COPYAREA
1178 select FB_CFB_IMAGEBLIT
1179 select FB_SOFT_CURSOR
1181 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1182 Voodoo2 (cvg) based graphics card.
1184 To compile this driver as a module, choose M here: the
1185 module will be called sstfb.
1187 WARNING: Do not use any application that uses the 3D engine
1188 (namely glide) while using this driver.
1189 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1190 options and other important info support.
1193 tristate "Cyberblade/i1 support"
1194 depends on FB && PCI
1195 select FB_CFB_IMAGEBLIT
1196 select FB_SOFT_CURSOR
1199 This driver is supposed to support the Trident Cyberblade/i1
1200 graphics core integrated in the VIA VT8601A North Bridge,
1201 also known as VIA Apollo PLE133.
1204 - Developed, tested and working on EPIA 5000 and EPIA 800.
1205 - Does work reliable on all systems with CRT/LCD connected to
1207 - Should work on systems that do use the internal LCD port, but
1208 this is absolutely not tested.
1210 Character imageblit, copyarea and rectangle fill are hw accelerated,
1211 ypan scrolling is used by default.
1213 Please do read <file:Documentation/fb/cyblafb/*>.
1215 To compile this driver as a module, choose M here: the
1216 module will be called cyblafb.
1219 tristate "Trident support"
1220 depends on FB && PCI
1221 select FB_CFB_FILLRECT
1222 select FB_CFB_COPYAREA
1223 select FB_CFB_IMAGEBLIT
1224 select FB_SOFT_CURSOR
1226 This driver is supposed to support graphics boards with the
1227 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1228 but also on some motherboards. For more information, read
1229 <file:Documentation/fb/tridentfb.txt>
1231 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1234 Say Y if you have such a graphics board.
1237 To compile this driver as a module, choose M here: the
1238 module will be called tridentfb.
1240 config FB_TRIDENT_ACCEL
1241 bool "Trident Acceleration functions (EXPERIMENTAL)"
1242 depends on FB_TRIDENT && EXPERIMENTAL
1244 This will compile the Trident frame buffer device with
1245 acceleration functions.
1248 tristate "Permedia3 support"
1249 depends on FB && PCI && BROKEN
1251 This is the frame buffer device driver for the 3DLabs Permedia3
1252 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1253 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1254 and maybe other boards.
1257 tristate "Epson SED1356 framebuffer support"
1258 depends on FB && EXPERIMENTAL && PCI && MIPS
1261 bool "Use CRT on Pb1000 (J65)"
1262 depends on MIPS_PB1000=y && FB_E1356
1265 bool "Use Compsite NTSC on Pb1000 (J63)"
1266 depends on MIPS_PB1000=y && FB_E1356
1269 bool "Use TFT Panel on Pb1000 (J64)"
1270 depends on MIPS_PB1000=y && FB_E1356
1273 bool "Use CRT on Pb1500 " if MIPS_PB1500=y
1277 prompt "Use CRT on Pb1100 "
1278 depends on FB_E1356 && MIPS_PB1100=y
1281 bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y
1285 prompt "Use TFT Panel on Pb1100 "
1286 depends on FB_E1356 && MIPS_PB1100=y
1289 bool "Au1100 LCD Driver"
1290 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1292 source "drivers/video/geode/Kconfig"
1295 bool "SBUS and UPA framebuffers"
1296 depends on (FB = y) && (SPARC32 || SPARC64)
1298 Say Y if you want support for SBUS or UPA based frame buffer device.
1301 bool "Creator/Creator3D/Elite3D support"
1302 depends on FB_SBUS && SPARC64
1303 select FB_CFB_COPYAREA
1304 select FB_CFB_IMAGEBLIT
1305 select FB_SOFT_CURSOR
1307 This is the frame buffer device driver for the Creator, Creator3D,
1308 and Elite3D graphics boards.
1311 bool "TCX (SS4/SS5 only) support"
1313 select FB_CFB_FILLRECT
1314 select FB_CFB_COPYAREA
1315 select FB_CFB_IMAGEBLIT
1316 select FB_SOFT_CURSOR
1318 This is the frame buffer device driver for the TCX 24/8bit frame
1322 bool "CGfourteen (SX) support"
1324 select FB_CFB_FILLRECT
1325 select FB_CFB_COPYAREA
1326 select FB_CFB_IMAGEBLIT
1327 select FB_SOFT_CURSOR
1329 This is the frame buffer device driver for the CGfourteen frame
1330 buffer on Desktop SPARCsystems with the SX graphics option.
1333 bool "P9100 (Sparcbook 3 only) support"
1335 select FB_CFB_FILLRECT
1336 select FB_CFB_COPYAREA
1337 select FB_CFB_IMAGEBLIT
1338 select FB_SOFT_CURSOR
1340 This is the frame buffer device driver for the P9100 card
1341 supported on Sparcbook 3 machines.
1344 bool "Leo (ZX) support"
1346 select FB_CFB_FILLRECT
1347 select FB_CFB_COPYAREA
1348 select FB_CFB_IMAGEBLIT
1349 select FB_SOFT_CURSOR
1351 This is the frame buffer device driver for the SBUS-based Sun ZX
1352 (leo) frame buffer cards.
1355 bool "PCI framebuffers"
1356 depends on (FB = y) && PCI && (SPARC64 || SPARC32)
1359 bool "IGA 168x display support"
1360 depends on SPARC32 && FB_PCI
1361 select FB_CFB_FILLRECT
1362 select FB_CFB_COPYAREA
1363 select FB_CFB_IMAGEBLIT
1364 select FB_SOFT_CURSOR
1366 This is the framebuffer device for the INTERGRAPHICS 1680 and
1367 successor frame buffer cards.
1370 tristate "HD64461 Frame Buffer support"
1371 depends on FB && HD64461
1372 select FB_CFB_FILLRECT
1373 select FB_CFB_COPYAREA
1374 select FB_CFB_IMAGEBLIT
1375 select FB_SOFT_CURSOR
1377 This is the frame buffer device driver for the Hitachi HD64461 LCD
1381 bool "PMAG-AA TURBOchannel framebuffer support"
1382 depends on (FB = y) && TC
1383 select FB_CFB_FILLRECT
1384 select FB_CFB_COPYAREA
1385 select FB_CFB_IMAGEBLIT
1386 select FB_SOFT_CURSOR
1388 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1389 used mainly in the MIPS-based DECstation series.
1392 bool "PMAG-BA TURBOchannel framebuffer support"
1393 depends on (FB = y) && TC
1394 select FB_CFB_FILLRECT
1395 select FB_CFB_COPYAREA
1396 select FB_CFB_IMAGEBLIT
1397 select FB_SOFT_CURSOR
1399 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1400 used mainly in the MIPS-based DECstation series.
1403 bool "PMAGB-B TURBOchannel framebuffer support"
1404 depends on (FB = y) && TC
1405 select FB_CFB_FILLRECT
1406 select FB_CFB_COPYAREA
1407 select FB_CFB_IMAGEBLIT
1408 select FB_SOFT_CURSOR
1410 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1411 in the MIPS-based DECstation series. The card is currently only
1412 supported in 1280x1024x8 mode.
1415 bool "Maxine (Personal DECstation) onboard framebuffer support"
1416 depends on (FB = y) && MACH_DECSTATION
1417 select FB_CFB_FILLRECT
1418 select FB_CFB_COPYAREA
1419 select FB_CFB_IMAGEBLIT
1420 select FB_SOFT_CURSOR
1422 Support for the onboard framebuffer (1024x768x8) in the Personal
1423 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1427 bool "TMPTX3912/PR31700 frame buffer support"
1428 depends on (FB = y) && NINO
1429 select FB_CFB_FILLRECT
1430 select FB_CFB_COPYAREA
1431 select FB_CFB_IMAGEBLIT
1432 select FB_SOFT_CURSOR
1434 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1435 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1437 Say Y here to enable kernel support for the on-board framebuffer.
1440 bool "G364 frame buffer support"
1441 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1442 select FB_CFB_FILLRECT
1443 select FB_CFB_COPYAREA
1444 select FB_CFB_IMAGEBLIT
1445 select FB_SOFT_CURSOR
1447 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1448 Olivetti M700-10 systems.
1451 bool "Motorola 68328 native frame buffer support"
1452 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1453 select FB_CFB_FILLRECT
1454 select FB_CFB_COPYAREA
1455 select FB_CFB_IMAGEBLIT
1456 select FB_SOFT_CURSOR
1458 Say Y here if you want to support the built-in frame buffer of
1459 the Motorola 68328 CPU family.
1462 tristate "PXA LCD framebuffer support"
1463 depends on FB && ARCH_PXA
1464 select FB_CFB_FILLRECT
1465 select FB_CFB_COPYAREA
1466 select FB_CFB_IMAGEBLIT
1467 select FB_SOFT_CURSOR
1469 Frame buffer driver for the built-in LCD controller in the Intel
1472 This driver is also available as a module ( = code which can be
1473 inserted and removed from the running kernel whenever you want). The
1474 module will be called vfb. If you want to compile it as a module,
1475 say M here and read <file:Documentation/modules.txt>.
1480 tristate "W100 frame buffer support"
1481 depends on FB && PXA_SHARPSL
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1485 select FB_SOFT_CURSOR
1487 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1489 This driver is also available as a module ( = code which can be
1490 inserted and removed from the running kernel whenever you want). The
1491 module will be called vfb. If you want to compile it as a module,
1492 say M here and read <file:Documentation/modules.txt>.
1496 config FB_PXA_PARAMETERS
1497 bool "PXA LCD command line parameters"
1501 Enable the use of kernel command line or module parameters
1502 to configure the physical properties of the LCD panel when
1503 using the PXA LCD driver.
1505 This option allows you to override the panel parameters
1506 supplied by the platform in order to support multiple
1507 different models of flatpanel. If you will only be using a
1508 single model of flatpanel then you can safely leave this
1511 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1514 tristate "Epson S1D13XXX framebuffer support"
1516 select FB_CFB_FILLRECT
1517 select FB_CFB_COPYAREA
1518 select FB_CFB_IMAGEBLIT
1519 select FB_SOFT_CURSOR
1521 Support for S1D13XXX framebuffer device family (currently only
1522 working with S1D13806). Product specs at
1523 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
1526 tristate "S3C2410 LCD framebuffer support"
1527 depends on FB && ARCH_S3C2410
1528 select FB_CFB_FILLRECT
1529 select FB_CFB_COPYAREA
1530 select FB_CFB_IMAGEBLIT
1531 select FB_SOFT_CURSOR
1533 Frame buffer driver for the built-in LCD controller in the Samsung
1536 This driver is also available as a module ( = code which can be
1537 inserted and removed from the running kernel whenever you want). The
1538 module will be called s3c2410fb. If you want to compile it as a module,
1539 say M here and read <file:Documentation/modules.txt>.
1542 config FB_S3C2410_DEBUG
1543 bool "S3C2410 lcd debug messages"
1544 depends on FB_S3C2410
1546 Turn on debugging messages. Note that you can set/unset at run time
1550 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1552 select FB_CFB_FILLRECT
1553 select FB_CFB_COPYAREA
1554 select FB_CFB_IMAGEBLIT
1555 select FB_SOFT_CURSOR
1557 This is a `virtual' frame buffer device. It operates on a chunk of
1558 unswappable kernel memory instead of on the memory of a graphics
1559 board. This means you cannot see any output sent to this frame
1560 buffer device, while it does consume precious memory. The main use
1561 of this frame buffer device is testing and debugging the frame
1562 buffer subsystem. Do NOT enable it for normal systems! To protect
1563 the innocent, it has to be enabled explicitly at boot time using the
1564 kernel option `video=vfb:'.
1566 To compile this driver as a module, choose M here: the
1567 module will be called vfb.
1571 source "drivers/video/console/Kconfig"
1574 if FB || SGI_NEWPORT_CONSOLE
1575 source "drivers/video/logo/Kconfig"
1579 source "drivers/video/backlight/Kconfig"