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
187 bool "SA-1100 LCD support"
188 depends on (FB = y) && ARM && ARCH_SA1100
189 select FB_CFB_FILLRECT
190 select FB_CFB_COPYAREA
191 select FB_CFB_IMAGEBLIT
192 select FB_SOFT_CURSOR
194 This is a framebuffer device for the SA-1100 LCD Controller.
195 See <http://www.linux-fbdev.org/> for information on framebuffer
198 If you plan to use the LCD display with your SA-1100 system, say
202 tristate "Motorola i.MX LCD support"
203 depends on FB && ARM && ARCH_IMX
204 select FB_CFB_FILLRECT
205 select FB_CFB_COPYAREA
206 select FB_CFB_IMAGEBLIT
207 select FB_SOFT_CURSOR
210 tristate "CyberPro 2000/2010/5000 support"
211 depends on FB && PCI && (BROKEN || !SPARC64)
212 select FB_CFB_FILLRECT
213 select FB_CFB_COPYAREA
214 select FB_CFB_IMAGEBLIT
215 select FB_SOFT_CURSOR
217 This enables support for the Integraphics CyberPro 20x0 and 5000
218 VGA chips used in the Rebel.com Netwinder and other machines.
219 Say Y if you have a NetWinder or a graphics card containing this
220 device, otherwise say N.
224 depends on (FB = y) && APOLLO
226 select FB_CFB_FILLRECT
227 select FB_CFB_IMAGEBLIT
228 select FB_SOFT_CURSOR
232 depends on (FB = y) && Q40
234 select FB_CFB_FILLRECT
235 select FB_CFB_COPYAREA
236 select FB_CFB_IMAGEBLIT
237 select FB_SOFT_CURSOR
240 tristate "Amiga native chipset support"
241 depends on FB && AMIGA
242 select FB_SOFT_CURSOR
244 This is the frame buffer device driver for the builtin graphics
245 chipset found in Amigas.
247 To compile this driver as a module, choose M here: the
248 module will be called amifb.
251 bool "Amiga OCS chipset support"
254 This enables support for the original Agnus and Denise video chips,
255 found in the Amiga 1000 and most A500's and A2000's. If you intend
256 to run Linux on any of these systems, say Y; otherwise say N.
259 bool "Amiga ECS chipset support"
262 This enables support for the Enhanced Chip Set, found in later
263 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
264 you intend to run Linux on any of these systems, say Y; otherwise
268 bool "Amiga AGA chipset support"
271 This enables support for the Advanced Graphics Architecture (also
272 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
273 and CD32. If you intend to run Linux on any of these systems, say Y;
277 tristate "Amiga CyberVision 64 support"
278 depends on FB && ZORRO && BROKEN
279 select FB_CFB_FILLRECT
280 select FB_CFB_COPYAREA
281 select FB_CFB_IMAGEBLIT
282 select FB_SOFT_CURSOR
284 This enables support for the Cybervision 64 graphics card from
285 Phase5. Please note that its use is not all that intuitive (i.e. if
286 you have any questions, be sure to ask!). Say N unless you have a
287 Cybervision 64 or plan to get one before you next recompile the
288 kernel. Please note that this driver DOES NOT support the
289 Cybervision 64/3D card, as they use incompatible video chips.
292 bool "Amiga CyberVision 64/3D support "
293 depends on (FB = y) && ZORRO && BROKEN
294 select FB_CFB_FILLRECT
295 select FB_CFB_COPYAREA
296 select FB_CFB_IMAGEBLIT
297 select FB_SOFT_CURSOR
299 This enables support for the Cybervision 64/3D graphics card from
300 Phase5. Please note that its use is not all that intuitive (i.e. if
301 you have any questions, be sure to ask!). Say N unless you have a
302 Cybervision 64/3D or plan to get one before you next recompile the
303 kernel. Please note that this driver DOES NOT support the older
304 Cybervision 64 card, as they use incompatible video chips.
307 tristate "Amiga Retina Z3 support"
308 depends on (FB = y) && ZORRO && BROKEN
310 This enables support for the Retina Z3 graphics card. Say N unless
311 you have a Retina Z3 or plan to get one before you next recompile
315 bool "Amiga FrameMaster II/Rainbow II support"
316 depends on (FB = y) && ZORRO
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
320 select FB_SOFT_CURSOR
322 This is the frame buffer device driver for the Amiga FrameMaster
323 card from BSC (exhibited 1992 but not shipped as a CBM product).
326 tristate "Arc Monochrome LCD board support"
328 select FB_CFB_FILLRECT
329 select FB_CFB_COPYAREA
330 select FB_CFB_IMAGEBLIT
331 select FB_SOFT_CURSOR
333 This enables support for the Arc Monochrome LCD board. The board
334 is based on the KS-108 lcd controller and is typically a matrix
335 of 2*n chips. This driver was tested with a 128x64 panel. This
336 driver supports it for use with x86 SBCs through a 16 bit GPIO
337 interface (8 bit data, 8 bit control). If you anticpate using
338 this driver, say Y or M; otherwise say N. You must specify the
339 GPIO IO address to be used for setting control and data.
342 bool "Atari native chipset support"
343 depends on (FB = y) && ATARI && BROKEN
345 This is the frame buffer device driver for the builtin graphics
346 chipset found in Ataris.
349 bool "Open Firmware frame buffer device support"
350 depends on (FB = y) && (PPC64 || PPC_OF)
351 select FB_CFB_FILLRECT
352 select FB_CFB_COPYAREA
353 select FB_CFB_IMAGEBLIT
354 select FB_SOFT_CURSOR
357 Say Y if you want support with Open Firmware for your graphics
361 bool "Apple \"control\" display support"
362 depends on (FB = y) && PPC_PMAC
363 select FB_CFB_FILLRECT
364 select FB_CFB_COPYAREA
365 select FB_CFB_IMAGEBLIT
366 select FB_SOFT_CURSOR
369 This driver supports a frame buffer for the graphics adapter in the
370 Power Macintosh 7300 and others.
373 bool "Apple \"platinum\" display support"
374 depends on (FB = y) && PPC_PMAC
375 select FB_CFB_FILLRECT
376 select FB_CFB_COPYAREA
377 select FB_CFB_IMAGEBLIT
378 select FB_SOFT_CURSOR
381 This driver supports a frame buffer for the "platinum" graphics
382 adapter in some Power Macintoshes.
385 bool "Apple \"valkyrie\" display support"
386 depends on (FB = y) && (MAC || PPC_PMAC)
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
390 select FB_SOFT_CURSOR
393 This driver supports a frame buffer for the "valkyrie" graphics
394 adapter in some Power Macintoshes.
397 bool "Chips 65550 display support"
398 depends on (FB = y) && PPC
399 select FB_CFB_FILLRECT
400 select FB_CFB_COPYAREA
401 select FB_CFB_IMAGEBLIT
402 select FB_SOFT_CURSOR
404 This is the frame buffer device driver for the Chips & Technologies
405 65550 graphics chip in PowerBooks.
408 bool "Chips 69000 display support"
409 depends on (FB = y) && PCI
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
413 select FB_SOFT_CURSOR
416 bool "IMS Twin Turbo display support"
417 depends on (FB = y) && PCI
418 select FB_CFB_IMAGEBLIT
419 select FB_SOFT_CURSOR
420 select FB_MACMODES if PPC
422 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
423 many Macintosh and compatible computers.
426 bool "S3 Trio display support"
427 depends on (FB = y) && PPC && BROKEN
429 If you have a S3 Trio say Y. Say N for S3 Virge.
432 tristate "VGA 16-color graphics support"
433 depends on FB && (X86 || PPC)
434 select FB_CFB_FILLRECT
435 select FB_CFB_COPYAREA
436 select FB_CFB_IMAGEBLIT
437 select FB_SOFT_CURSOR
439 This is the frame buffer device driver for VGA 16 color graphic
440 cards. Say Y if you have such a card.
442 To compile this driver as a module, choose M here: the
443 module will be called vga16fb.
446 tristate "HP STI frame buffer device support"
447 depends on FB && PARISC
448 select FB_CFB_FILLRECT
449 select FB_CFB_COPYAREA
450 select FB_CFB_IMAGEBLIT
451 select FB_SOFT_CURSOR
454 STI refers to the HP "Standard Text Interface" which is a set of
455 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
456 Enabling this option will implement the linux framebuffer device
457 using calls to the STI BIOS routines for initialisation.
459 If you enable this option, you will get a planar framebuffer device
460 /dev/fb which will work on the most common HP graphic cards of the
461 NGLE family, including the artist chips (in the 7xx and Bxxx series),
462 HCRX, HCRX24, CRX, CRX24 and VisEG series.
464 It is safe to enable this option, so you should probably say "Y".
467 bool "Generic Macintosh display support"
468 depends on (FB = y) && MAC
469 select FB_CFB_FILLRECT
470 select FB_CFB_COPYAREA
471 select FB_CFB_IMAGEBLIT
472 select FB_SOFT_CURSOR
475 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
478 depends on (FB = y) && HP300
479 select FB_CFB_FILLRECT
480 select FB_CFB_IMAGEBLIT
481 select FB_SOFT_CURSOR
485 tristate "TGA framebuffer support"
486 depends on FB && ALPHA
487 select FB_CFB_FILLRECT
488 select FB_CFB_COPYAREA
489 select FB_CFB_IMAGEBLIT
490 select FB_SOFT_CURSOR
492 This is the frame buffer device driver for generic TGA graphic
493 cards. Say Y if you have one of those.
496 bool "VESA VGA graphics support"
497 depends on (FB = y) && (X86 || X86_64)
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
501 select FB_SOFT_CURSOR
503 This is the frame buffer device driver for generic VESA 2.0
504 compliant graphic cards. The older VESA 1.2 cards are not supported.
505 You will get a boot time penguin logo at no additional cost. Please
506 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
514 tristate "Hercules mono graphics support"
516 select FB_CFB_FILLRECT
517 select FB_CFB_COPYAREA
518 select FB_CFB_IMAGEBLIT
519 select FB_SOFT_CURSOR
521 Say Y here if you have a Hercules mono graphics card.
523 To compile this driver as a module, choose M here: the
524 module will be called hgafb.
526 As this card technology is 15 years old, most people will answer N
530 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
531 depends on FB_HGA && EXPERIMENTAL
533 This will compile the Hercules mono graphics with
534 acceleration functions.
539 depends on (FB = y) && X86
543 tristate "SGI Visual Workstation framebuffer support"
544 depends on FB && X86_VISWS
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
548 select FB_SOFT_CURSOR
550 SGI Visual Workstation support for framebuffer graphics.
553 bool "SGI Graphics Backend frame buffer support"
554 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
555 select FB_CFB_FILLRECT
556 select FB_CFB_COPYAREA
557 select FB_CFB_IMAGEBLIT
558 select FB_SOFT_CURSOR
560 This is the frame buffer device driver for SGI Graphics Backend.
561 This chip is used in SGI O2 and Visual Workstation 320/540.
564 int "Video memory size in MB"
568 This is the amount of memory reserved for the framebuffer,
569 which can be any value between 1MB and 8MB.
573 depends on (FB = y) && VISWS
577 bool "Sun3 framebuffer support"
578 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
582 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
583 select FB_CFB_FILLRECT
584 select FB_CFB_COPYAREA
585 select FB_CFB_IMAGEBLIT
586 select FB_SOFT_CURSOR
588 This is the frame buffer device driver for the BWtwo frame buffer.
591 bool "CGthree support"
592 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
593 select FB_CFB_COPYAREA
594 select FB_CFB_IMAGEBLIT
595 select FB_SOFT_CURSOR
597 This is the frame buffer device driver for the CGthree frame buffer.
600 bool "CGsix (GX,TurboGX) support"
601 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
602 select FB_CFB_COPYAREA
603 select FB_CFB_IMAGEBLIT
604 select FB_SOFT_CURSOR
606 This is the frame buffer device driver for the CGsix (GX, TurboGX)
610 tristate "NEC PowerVR 2 display support"
611 depends on FB && SH_DREAMCAST
612 select FB_CFB_FILLRECT
613 select FB_CFB_COPYAREA
614 select FB_CFB_IMAGEBLIT
615 select FB_SOFT_CURSOR
617 Say Y here if you have a PowerVR 2 card in your box. If you plan to
618 run linux on your Dreamcast, you will have to say Y here.
619 This driver may or may not work on other PowerVR 2 cards, but is
620 totally untested. Use at your own risk. If unsure, say N.
622 To compile this driver as a module, choose M here: the
623 module will be called pvr2fb.
625 You can pass several parameters to the driver at boot time or at
626 module load time. The parameters look like "video=pvr2:XXX", where
627 the meaning of XXX can be found at the end of the main source file
628 (<file:drivers/video/pvr2fb.c>). Please see the file
629 <file:Documentation/fb/pvr2fb.txt>.
632 bool "Epson 1355 framebuffer support"
633 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
634 select FB_CFB_FILLRECT
635 select FB_CFB_COPYAREA
636 select FB_CFB_IMAGEBLIT
637 select FB_SOFT_CURSOR
639 Build in support for the SED1355 Epson Research Embedded RAMDAC
640 LCD/CRT Controller (since redesignated as the S1D13505) as a
641 framebuffer. Product specs at
642 <http://www.erd.epson.com/vdc/html/products.htm>.
645 tristate "nVidia Framebuffer Support"
647 select I2C_ALGOBIT if FB_NVIDIA_I2C
648 select I2C if FB_NVIDIA_I2C
649 select FB_MODE_HELPERS
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
653 select FB_SOFT_CURSOR
655 This driver supports graphics boards with the nVidia chips, TNT
656 and newer. For very old chipsets, such as the RIVA128, then use
658 Say Y if you have such a graphics board.
660 To compile this driver as a module, choose M here: the
661 module will be called nvidiafb.
664 bool "Enable DDC Support"
665 depends on FB_NVIDIA && !PPC_OF
667 This enables I2C support for nVidia Chipsets. This is used
668 only for getting EDID information from the attached display
669 allowing for robust video mode handling and switching.
671 Because fbdev-2.6 requires that drivers must be able to
672 independently validate video mode parameters, you should say Y
676 tristate "nVidia Riva support"
678 select I2C_ALGOBIT if FB_RIVA_I2C
679 select I2C if FB_RIVA_I2C
680 select FB_MODE_HELPERS
681 select FB_CFB_FILLRECT
682 select FB_CFB_COPYAREA
683 select FB_CFB_IMAGEBLIT
685 This driver supports graphics boards with the nVidia Riva/Geforce
687 Say Y if you have such a graphics board.
689 To compile this driver as a module, choose M here: the
690 module will be called rivafb.
693 bool "Enable DDC Support"
696 This enables I2C support for nVidia Chipsets. This is used
697 only for getting EDID information from the attached display
698 allowing for robust video mode handling and switching.
700 Because fbdev-2.6 requires that drivers must be able to
701 independently validate video mode parameters, you should say Y
705 bool "Lots of debug output from Riva(nVidia) driver"
709 Say Y here if you want the Riva driver to output all sorts
710 of debugging informations to provide to the maintainer when
711 something goes wrong.
714 tristate "Intel 810/815 support (EXPERIMENTAL)"
715 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
718 select FB_MODE_HELPERS
719 select FB_CFB_FILLRECT
720 select FB_CFB_COPYAREA
721 select FB_CFB_IMAGEBLIT
723 This driver supports the on-board graphics built in to the Intel 810
724 and 815 chipsets. Say Y if you have and plan to use such a board.
726 To compile this driver as a module, choose M here: the
727 module will be called i810fb.
729 For more information, please read
730 <file:Documentation/fb/intel810.txt>
733 bool "use VESA Generalized Timing Formula"
736 If you say Y, then the VESA standard, Generalized Timing Formula
737 or GTF, will be used to calculate the required video timing values
738 per video mode. Since the GTF allows nondiscrete timings
739 (nondiscrete being a range of values as opposed to discrete being a
740 set of values), you'll be able to use any combination of horizontal
741 and vertical resolutions, and vertical refresh rates without having
742 to specify your own timing parameters. This is especially useful
743 to maximize the performance of an aging display, or if you just
744 have a display with nonstandard dimensions. A VESA compliant
745 monitor is recommended, but can still work with non-compliant ones.
746 If you need or want this, then select this option. The timings may
747 not be compliant with Intel's recommended values. Use at your own
750 If you say N, the driver will revert to discrete video timings
751 using a set recommended by Intel in their documentation.
756 bool "Enable DDC Support"
757 depends on FB_I810 && FB_I810_GTF
763 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
764 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
767 select FB_MODE_HELPERS
768 select FB_CFB_FILLRECT
769 select FB_CFB_COPYAREA
770 select FB_CFB_IMAGEBLIT
772 This driver supports the on-board graphics built in to the Intel
773 830M/845G/852GM/855GM/865G chipsets.
774 Say Y if you have and plan to use such a board.
776 To compile this driver as a module, choose M here: the
777 module will be called intelfb.
779 config FB_INTEL_DEBUG
780 bool "Intel driver Debug Messages"
783 Say Y here if you want the Intel driver to output all sorts
784 of debugging informations to provide to the maintainer when
785 something goes wrong.
788 tristate "Matrox acceleration"
790 select FB_CFB_FILLRECT
791 select FB_CFB_COPYAREA
792 select FB_CFB_IMAGEBLIT
793 select FB_SOFT_CURSOR
794 select FB_TILEBLITTING
795 select FB_MACMODES if PPC_PMAC
797 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
798 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
799 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
800 Matrox G400, G450 or G550 card in your box.
802 To compile this driver as a module, choose M here: the
803 module will be called matroxfb.
805 You can pass several parameters to the driver at boot time or at
806 module load time. The parameters look like "video=matrox:XXX", and
807 are described in <file:Documentation/fb/matroxfb.txt>.
809 config FB_MATROX_MILLENIUM
810 bool "Millennium I/II support"
813 Say Y here if you have a Matrox Millennium or Matrox Millennium II
814 video card. If you select "Advanced lowlevel driver options" below,
815 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
816 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
817 also use font widths different from 8.
819 config FB_MATROX_MYSTIQUE
820 bool "Mystique support"
823 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
824 video card. If you select "Advanced lowlevel driver options" below,
825 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
826 packed pixel and 32 bpp packed pixel. You can also use font widths
830 bool "G100/G200/G400/G450/G550 support"
833 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
834 video card. If you select "Advanced lowlevel driver options", you
835 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
836 pixel and 32 bpp packed pixel. You can also use font widths
839 If you need support for G400 secondary head, you must first say Y to
840 "I2C support" in the character devices section, and then to
841 "Matrox I2C support" and "G400 second head support" here in the
842 framebuffer section. G450/G550 secondary head and digital output
843 are supported without additional modules.
845 The driver starts in monitor mode. You must use the matroxset tool
846 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
847 swap primary and secondary head outputs, or to change output mode.
848 Secondary head driver always start in 640x480 resolution and you
849 must use fbset to change it.
851 Do not forget that second head supports only 16 and 32 bpp
852 packed pixels, so it is a good idea to compile them into the kernel
853 too. You can use only some font widths, as the driver uses generic
854 painting procedures (the secondary head does not use acceleration
857 G450/G550 hardware can display TV picture only from secondary CRTC,
858 and it performs no scaling, so picture must have 525 or 625 lines.
861 tristate "Matrox I2C support"
862 depends on FB_MATROX && I2C
865 This drivers creates I2C buses which are needed for accessing the
866 DDC (I2C) bus present on all Matroxes, an I2C bus which
867 interconnects Matrox optional devices, like MGA-TVO on G200 and
868 G400, and the secondary head DDC bus, present on G400 only.
870 You can say Y or M here if you want to experiment with monitor
871 detection code. You must say Y or M here if you want to use either
872 second head of G400 or MGA-TVO on G200 or G400.
874 If you compile it as module, it will create a module named
877 config FB_MATROX_MAVEN
878 tristate "G400 second head support"
879 depends on FB_MATROX_G && FB_MATROX_I2C
881 WARNING !!! This support does not work with G450 !!!
883 Say Y or M here if you want to use a secondary head (meaning two
884 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
885 head is not compatible with accelerated XFree 3.3.x SVGA servers -
886 secondary head output is blanked while you are in X. With XFree
887 3.9.17 preview you can use both heads if you use SVGA over fbdev or
888 the fbdev driver on first head and the fbdev driver on second head.
890 If you compile it as module, two modules are created,
891 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
892 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
893 also load i2c-matroxfb to get it to run.
895 The driver starts in monitor mode and you must use the matroxset
897 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
898 PAL or NTSC or to swap primary and secondary head outputs.
899 Secondary head driver also always start in 640x480 resolution, you
900 must use fbset to change it.
902 Also do not forget that second head supports only 16 and 32 bpp
903 packed pixels, so it is a good idea to compile them into the kernel
904 too. You can use only some font widths, as the driver uses generic
905 painting procedures (the secondary head does not use acceleration
908 config FB_MATROX_MULTIHEAD
909 bool "Multihead support"
912 Say Y here if you have more than one (supported) Matrox device in
913 your computer and you want to use all of them for different monitors
914 ("multihead"). If you have only one device, you should say N because
915 the driver compiled with Y is larger and a bit slower, especially on
918 If you said M to "Matrox unified accelerated driver" and N here, you
919 will still be able to use several Matrox devices simultaneously:
920 insert several instances of the module matroxfb into the kernel
921 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
922 for the different Matrox devices. This method is slightly faster but
923 uses 40 KB of kernel memory per Matrox card.
925 There is no need for enabling 'Matrox multihead support' if you have
926 only one Matrox card in the box.
929 tristate "ATI Radeon display support (Old driver)"
931 select FB_CFB_FILLRECT
932 select FB_CFB_COPYAREA
933 select FB_CFB_IMAGEBLIT
934 select FB_SOFT_CURSOR
935 select FB_MACMODES if PPC
937 Choose this option if you want to use an ATI Radeon graphics card as
938 a framebuffer device. There are both PCI and AGP versions. You
939 don't need to choose this to run the Radeon in plain VGA mode.
940 There is a product page at
941 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
944 tristate "ATI Radeon display support"
946 select I2C_ALGOBIT if FB_RADEON_I2C
947 select I2C if FB_RADEON_I2C
948 select FB_MODE_HELPERS
949 select FB_CFB_FILLRECT
950 select FB_CFB_COPYAREA
951 select FB_CFB_IMAGEBLIT
952 select FB_SOFT_CURSOR
953 select FB_MACMODES if PPC_OF
955 Choose this option if you want to use an ATI Radeon graphics card as
956 a framebuffer device. There are both PCI and AGP versions. You
957 don't need to choose this to run the Radeon in plain VGA mode.
959 If you say Y here and want DDC/I2C support you must first say Y to
960 "I2C support" and "I2C bit-banging support" in the character devices
963 If you say M here then "I2C support" and "I2C bit-banging support"
964 can be build either as modules or built-in.
966 There is a product page at
967 http://apps.ati.com/ATIcompare/
969 bool "DDC/I2C for ATI Radeon support"
973 Say Y here if you want DDC/I2C support for your Radeon board.
975 config FB_RADEON_DEBUG
976 bool "Lots of debug output from Radeon driver"
980 Say Y here if you want the Radeon driver to output all sorts
981 of debugging informations to provide to the maintainer when
982 something goes wrong.
985 tristate "ATI Rage128 display support"
987 select FB_CFB_FILLRECT
988 select FB_CFB_COPYAREA
989 select FB_CFB_IMAGEBLIT
990 select FB_SOFT_CURSOR
991 select FB_MACMODES if PPC_PMAC
993 This driver supports graphics boards with the ATI Rage128 chips.
994 Say Y if you have such a graphics board and read
995 <file:Documentation/fb/aty128fb.txt>.
997 To compile this driver as a module, choose M here: the
998 module will be called aty128fb.
1001 tristate "ATI Mach64 display support" if PCI || ATARI
1003 select FB_CFB_FILLRECT
1004 select FB_CFB_COPYAREA
1005 select FB_CFB_IMAGEBLIT
1006 select FB_SOFT_CURSOR
1007 select FB_MACMODES if PPC
1009 This driver supports graphics boards with the ATI Mach64 chips.
1010 Say Y if you have such a graphics board.
1012 To compile this driver as a module, choose M here: the
1013 module will be called atyfb.
1016 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1017 depends on PCI && FB_ATY
1018 default y if SPARC64 && FB_PCI
1020 Say Y here to support use of ATI's 64-bit Rage boards (or other
1021 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1022 framebuffer device. The ATI product support page for these boards
1023 is at <http://support.ati.com/products/pc/mach64/>.
1025 config FB_ATY_GENERIC_LCD
1026 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1027 depends on FB_ATY_CT
1029 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1030 Rage XC, or Rage XL chipset.
1032 config FB_ATY_XL_INIT
1033 bool "Rage XL No-BIOS Init support"
1034 depends on FB_ATY_CT
1036 Say Y here to support booting a Rage XL without BIOS support.
1039 bool "Mach64 GX support" if PCI
1043 Say Y here to support use of the ATI Mach64 Graphics Expression
1044 board (or other boards based on the Mach64 GX chipset) as a
1045 framebuffer device. The ATI product support page for these boards
1047 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1050 tristate "S3 Savage support"
1051 depends on FB && PCI && EXPERIMENTAL
1052 select I2C_ALGOBIT if FB_SAVAGE_I2C
1053 select I2C if FB_SAVAGE_I2C
1054 select FB_MODE_HELPERS
1055 select FB_CFB_FILLRECT
1056 select FB_CFB_COPYAREA
1057 select FB_CFB_IMAGEBLIT
1058 select FB_SOFT_CURSOR
1060 This driver supports notebooks and computers with S3 Savage PCI/AGP
1063 Say Y if you have such a graphics card.
1065 To compile this driver as a module, choose M here; the module
1066 will be called savagefb.
1068 config FB_SAVAGE_I2C
1069 bool "Enable DDC2 Support"
1070 depends on FB_SAVAGE
1072 This enables I2C support for S3 Savage Chipsets. This is used
1073 only for getting EDID information from the attached display
1074 allowing for robust video mode handling and switching.
1076 Because fbdev-2.6 requires that drivers must be able to
1077 independently validate video mode parameters, you should say Y
1080 config FB_SAVAGE_ACCEL
1081 bool "Enable Console Acceleration"
1082 depends on FB_SAVAGE
1085 This option will compile in console acceleration support. If
1086 the resulting framebuffer console has bothersome glitches, then
1090 tristate "SiS/XGI display support"
1091 depends on FB && PCI
1092 select FB_CFB_FILLRECT
1093 select FB_CFB_COPYAREA
1094 select FB_CFB_IMAGEBLIT
1095 select FB_SOFT_CURSOR
1097 This is the frame buffer device driver for the SiS 300, 315, 330
1098 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1099 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1101 To compile this driver as a module, choose M here; the module
1102 will be called sisfb.
1105 bool "SiS 300 series support"
1108 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1111 bool "SiS 315/330/340 series and XGI support"
1114 Say Y here to support use of the SiS 315, 330 and 340 series
1115 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1116 as XGI V3XT, V5, V8 and Z7.
1119 tristate "NeoMagic display support"
1120 depends on FB && PCI
1121 select FB_MODE_HELPERS
1122 select FB_CFB_FILLRECT
1123 select FB_CFB_COPYAREA
1124 select FB_CFB_IMAGEBLIT
1125 select FB_SOFT_CURSOR
1127 This driver supports notebooks with NeoMagic PCI chips.
1128 Say Y if you have such a graphics card.
1130 To compile this driver as a module, choose M here: the
1131 module will be called neofb.
1134 tristate "IMG Kyro support"
1135 depends on FB && PCI
1136 select FB_CFB_FILLRECT
1137 select FB_CFB_COPYAREA
1138 select FB_CFB_IMAGEBLIT
1139 select FB_SOFT_CURSOR
1141 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1144 To compile this driver as a module, choose M here: the
1145 module will be called kyrofb.
1148 tristate "3Dfx Banshee/Voodoo3 display support"
1149 depends on FB && PCI
1150 select FB_CFB_IMAGEBLIT
1151 select FB_CFB_FILLRECT
1152 select FB_CFB_COPYAREA
1153 select FB_SOFT_CURSOR
1155 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1156 chips. Say Y if you have such a graphics board.
1158 To compile this driver as a module, choose M here: the
1159 module will be called tdfxfb.
1161 config FB_3DFX_ACCEL
1162 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1163 depends on FB_3DFX && EXPERIMENTAL
1165 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1166 with acceleration functions.
1170 tristate "3Dfx Voodoo Graphics (sst1) support"
1171 depends on FB && PCI
1172 select FB_CFB_FILLRECT
1173 select FB_CFB_COPYAREA
1174 select FB_CFB_IMAGEBLIT
1175 select FB_SOFT_CURSOR
1177 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1178 Voodoo2 (cvg) based graphics card.
1180 To compile this driver as a module, choose M here: the
1181 module will be called sstfb.
1183 WARNING: Do not use any application that uses the 3D engine
1184 (namely glide) while using this driver.
1185 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1186 options and other important info support.
1189 tristate "Cyberblade/i1 support"
1190 depends on FB && PCI
1191 select FB_CFB_IMAGEBLIT
1192 select FB_SOFT_CURSOR
1195 This driver is supposed to support the Trident Cyberblade/i1
1196 graphics core integrated in the VIA VT8601A North Bridge,
1197 also known as VIA Apollo PLE133.
1200 - Developed, tested and working on EPIA 5000 and EPIA 800.
1201 - Does work reliable on all systems with CRT/LCD connected to
1203 - Should work on systems that do use the internal LCD port, but
1204 this is absolutely not tested.
1206 Character imageblit, copyarea and rectangle fill are hw accelerated,
1207 ypan scrolling is used by default.
1209 Please do read <file:Documentation/fb/cyblafb/*>.
1211 To compile this driver as a module, choose M here: the
1212 module will be called cyblafb.
1215 tristate "Trident support"
1216 depends on FB && PCI
1217 select FB_CFB_FILLRECT
1218 select FB_CFB_COPYAREA
1219 select FB_CFB_IMAGEBLIT
1220 select FB_SOFT_CURSOR
1222 This driver is supposed to support graphics boards with the
1223 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1224 but also on some motherboards. For more information, read
1225 <file:Documentation/fb/tridentfb.txt>
1227 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1230 Say Y if you have such a graphics board.
1233 To compile this driver as a module, choose M here: the
1234 module will be called tridentfb.
1236 config FB_TRIDENT_ACCEL
1237 bool "Trident Acceleration functions (EXPERIMENTAL)"
1238 depends on FB_TRIDENT && EXPERIMENTAL
1240 This will compile the Trident frame buffer device with
1241 acceleration functions.
1244 tristate "Permedia3 support"
1245 depends on FB && PCI && BROKEN
1247 This is the frame buffer device driver for the 3DLabs Permedia3
1248 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1249 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1250 and maybe other boards.
1253 tristate "Epson SED1356 framebuffer support"
1254 depends on FB && EXPERIMENTAL && PCI && MIPS
1257 bool "Use CRT on Pb1000 (J65)"
1258 depends on MIPS_PB1000=y && FB_E1356
1261 bool "Use Compsite NTSC on Pb1000 (J63)"
1262 depends on MIPS_PB1000=y && FB_E1356
1265 bool "Use TFT Panel on Pb1000 (J64)"
1266 depends on MIPS_PB1000=y && FB_E1356
1269 bool "Use CRT on Pb1500 " if MIPS_PB1500=y
1273 prompt "Use CRT on Pb1100 "
1274 depends on FB_E1356 && MIPS_PB1100=y
1277 bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y
1281 prompt "Use TFT Panel on Pb1100 "
1282 depends on FB_E1356 && MIPS_PB1100=y
1285 bool "Au1100 LCD Driver"
1286 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1288 source "drivers/video/geode/Kconfig"
1291 bool "SBUS and UPA framebuffers"
1292 depends on (FB = y) && (SPARC32 || SPARC64)
1294 Say Y if you want support for SBUS or UPA based frame buffer device.
1297 bool "Creator/Creator3D/Elite3D support"
1298 depends on FB_SBUS && SPARC64
1299 select FB_CFB_COPYAREA
1300 select FB_CFB_IMAGEBLIT
1301 select FB_SOFT_CURSOR
1303 This is the frame buffer device driver for the Creator, Creator3D,
1304 and Elite3D graphics boards.
1307 bool "TCX (SS4/SS5 only) support"
1309 select FB_CFB_FILLRECT
1310 select FB_CFB_COPYAREA
1311 select FB_CFB_IMAGEBLIT
1312 select FB_SOFT_CURSOR
1314 This is the frame buffer device driver for the TCX 24/8bit frame
1318 bool "CGfourteen (SX) support"
1320 select FB_CFB_FILLRECT
1321 select FB_CFB_COPYAREA
1322 select FB_CFB_IMAGEBLIT
1323 select FB_SOFT_CURSOR
1325 This is the frame buffer device driver for the CGfourteen frame
1326 buffer on Desktop SPARCsystems with the SX graphics option.
1329 bool "P9100 (Sparcbook 3 only) support"
1331 select FB_CFB_FILLRECT
1332 select FB_CFB_COPYAREA
1333 select FB_CFB_IMAGEBLIT
1334 select FB_SOFT_CURSOR
1336 This is the frame buffer device driver for the P9100 card
1337 supported on Sparcbook 3 machines.
1340 bool "Leo (ZX) support"
1342 select FB_CFB_FILLRECT
1343 select FB_CFB_COPYAREA
1344 select FB_CFB_IMAGEBLIT
1345 select FB_SOFT_CURSOR
1347 This is the frame buffer device driver for the SBUS-based Sun ZX
1348 (leo) frame buffer cards.
1351 bool "PCI framebuffers"
1352 depends on (FB = y) && PCI && (SPARC64 || SPARC32)
1355 bool "IGA 168x display support"
1356 depends on SPARC32 && FB_PCI
1357 select FB_CFB_FILLRECT
1358 select FB_CFB_COPYAREA
1359 select FB_CFB_IMAGEBLIT
1360 select FB_SOFT_CURSOR
1362 This is the framebuffer device for the INTERGRAPHICS 1680 and
1363 successor frame buffer cards.
1366 tristate "HD64461 Frame Buffer support"
1367 depends on FB && HD64461
1368 select FB_CFB_FILLRECT
1369 select FB_CFB_COPYAREA
1370 select FB_CFB_IMAGEBLIT
1371 select FB_SOFT_CURSOR
1373 This is the frame buffer device driver for the Hitachi HD64461 LCD
1377 bool "PMAG-AA TURBOchannel framebuffer support"
1378 depends on (FB = y) && MACH_DECSTATION && TC
1379 select FB_CFB_FILLRECT
1380 select FB_CFB_COPYAREA
1381 select FB_CFB_IMAGEBLIT
1382 select FB_SOFT_CURSOR
1384 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1385 used mainly in the MIPS-based DECstation series.
1388 bool "PMAG-BA TURBOchannel framebuffer support"
1389 depends on (FB = y) && MACH_DECSTATION && TC
1390 select FB_CFB_FILLRECT
1391 select FB_CFB_COPYAREA
1392 select FB_CFB_IMAGEBLIT
1393 select FB_SOFT_CURSOR
1395 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1396 used mainly in the MIPS-based DECstation series.
1399 bool "PMAGB-B TURBOchannel framebuffer support"
1400 depends on (FB = y) && MACH_DECSTATION && TC
1401 select FB_CFB_FILLRECT
1402 select FB_CFB_COPYAREA
1403 select FB_CFB_IMAGEBLIT
1404 select FB_SOFT_CURSOR
1406 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1407 in the MIPS-based DECstation series. The card is currently only
1408 supported in 1280x1024x8 mode.
1411 bool "Maxine (Personal DECstation) onboard framebuffer support"
1412 depends on (FB = y) && MACH_DECSTATION && TC
1413 select FB_CFB_FILLRECT
1414 select FB_CFB_COPYAREA
1415 select FB_CFB_IMAGEBLIT
1416 select FB_SOFT_CURSOR
1418 Support for the onboard framebuffer (1024x768x8) in the Personal
1419 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1423 bool "TMPTX3912/PR31700 frame buffer support"
1424 depends on (FB = y) && NINO
1425 select FB_CFB_FILLRECT
1426 select FB_CFB_COPYAREA
1427 select FB_CFB_IMAGEBLIT
1428 select FB_SOFT_CURSOR
1430 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1431 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1433 Say Y here to enable kernel support for the on-board framebuffer.
1436 bool "G364 frame buffer support"
1437 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1438 select FB_CFB_FILLRECT
1439 select FB_CFB_COPYAREA
1440 select FB_CFB_IMAGEBLIT
1441 select FB_SOFT_CURSOR
1443 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1444 Olivetti M700-10 systems.
1447 bool "Motorola 68328 native frame buffer support"
1448 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1449 select FB_CFB_FILLRECT
1450 select FB_CFB_COPYAREA
1451 select FB_CFB_IMAGEBLIT
1452 select FB_SOFT_CURSOR
1454 Say Y here if you want to support the built-in frame buffer of
1455 the Motorola 68328 CPU family.
1458 tristate "PXA LCD framebuffer support"
1459 depends on FB && ARCH_PXA
1460 select FB_CFB_FILLRECT
1461 select FB_CFB_COPYAREA
1462 select FB_CFB_IMAGEBLIT
1463 select FB_SOFT_CURSOR
1465 Frame buffer driver for the built-in LCD controller in the Intel
1468 This driver is also available as a module ( = code which can be
1469 inserted and removed from the running kernel whenever you want). The
1470 module will be called vfb. If you want to compile it as a module,
1471 say M here and read <file:Documentation/modules.txt>.
1476 tristate "W100 frame buffer support"
1477 depends on FB && PXA_SHARPSL
1478 select FB_CFB_FILLRECT
1479 select FB_CFB_COPYAREA
1480 select FB_CFB_IMAGEBLIT
1481 select FB_SOFT_CURSOR
1483 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1485 This driver is also available as a module ( = code which can be
1486 inserted and removed from the running kernel whenever you want). The
1487 module will be called vfb. If you want to compile it as a module,
1488 say M here and read <file:Documentation/modules.txt>.
1492 config FB_PXA_PARAMETERS
1493 bool "PXA LCD command line parameters"
1497 Enable the use of kernel command line or module parameters
1498 to configure the physical properties of the LCD panel when
1499 using the PXA LCD driver.
1501 This option allows you to override the panel parameters
1502 supplied by the platform in order to support multiple
1503 different models of flatpanel. If you will only be using a
1504 single model of flatpanel then you can safely leave this
1507 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1510 tristate "Epson S1D13XXX framebuffer support"
1512 select FB_CFB_FILLRECT
1513 select FB_CFB_COPYAREA
1514 select FB_CFB_IMAGEBLIT
1515 select FB_SOFT_CURSOR
1517 Support for S1D13XXX framebuffer device family (currently only
1518 working with S1D13806). Product specs at
1519 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
1522 tristate "S3C2410 LCD framebuffer support"
1523 depends on FB && ARCH_S3C2410
1524 select FB_CFB_FILLRECT
1525 select FB_CFB_COPYAREA
1526 select FB_CFB_IMAGEBLIT
1527 select FB_SOFT_CURSOR
1529 Frame buffer driver for the built-in LCD controller in the Samsung
1532 This driver is also available as a module ( = code which can be
1533 inserted and removed from the running kernel whenever you want). The
1534 module will be called s3c2410fb. If you want to compile it as a module,
1535 say M here and read <file:Documentation/modules.txt>.
1538 config FB_S3C2410_DEBUG
1539 bool "S3C2410 lcd debug messages"
1540 depends on FB_S3C2410
1542 Turn on debugging messages. Note that you can set/unset at run time
1546 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1548 select FB_CFB_FILLRECT
1549 select FB_CFB_COPYAREA
1550 select FB_CFB_IMAGEBLIT
1551 select FB_SOFT_CURSOR
1553 This is a `virtual' frame buffer device. It operates on a chunk of
1554 unswappable kernel memory instead of on the memory of a graphics
1555 board. This means you cannot see any output sent to this frame
1556 buffer device, while it does consume precious memory. The main use
1557 of this frame buffer device is testing and debugging the frame
1558 buffer subsystem. Do NOT enable it for normal systems! To protect
1559 the innocent, it has to be enabled explicitly at boot time using the
1560 kernel option `video=vfb:'.
1562 To compile this driver as a module, choose M here: the
1563 module will be called vfb.
1567 source "drivers/video/console/Kconfig"
1570 if FB || SGI_NEWPORT_CONSOLE
1571 source "drivers/video/logo/Kconfig"
1575 source "drivers/video/backlight/Kconfig"