5 menu "Graphics support"
8 bool "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.
42 tristate "Cirrus Logic support"
43 depends on FB && (ZORRO || PCI)
45 This enables support for Cirrus Logic GD542x/543x based boards on
46 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
48 If you have a PCI-based system, this enables support for these
49 chips: GD-543x, GD-544x, GD-5480.
51 Please read the file <file:Documentation/fb/cirrusfb.txt>.
53 Say N unless you have such a graphics board or plan to get one
54 before you next recompile the kernel.
57 tristate "Permedia2 support"
58 depends on FB && ((AMIGA && BROKEN) || PCI)
60 This is the frame buffer device driver for the Permedia2 AGP frame
61 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
63 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
65 config FB_PM2_FIFO_DISCONNECT
66 bool "enable FIFO disconnect feature"
67 depends on FB_PM2 && PCI
69 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
72 bool "Acorn VIDC support"
73 depends on FB && ARM && ARCH_ACORN
75 This is the frame buffer device driver for the Acorn VIDC graphics
76 hardware found in Acorn RISC PCs and other ARM-based machines. If
80 bool "CLPS711X LCD support"
81 depends on FB && ARM && ARCH_CLPS711X
84 bool "SA-1100 LCD support"
85 depends on FB && ARM && ARCH_SA1100
87 This is a framebuffer device for the SA-1100 LCD Controller.
88 See <http://www.linux-fbdev.org/> for information on framebuffer
91 If you plan to use the LCD display with your SA-1100 system, say
95 tristate "CyberPro 2000/2010/5000 support"
96 depends on FB && PCI && (BROKEN || !SPARC64)
98 This enables support for the Integraphics CyberPro 20x0 and 5000
99 VGA chips used in the Rebel.com Netwinder and other machines.
100 Say Y if you have a NetWinder or a graphics card containing this
101 device, otherwise say N.
105 depends on FB && APOLLO
114 tristate "Amiga native chipset support"
115 depends on FB && AMIGA
117 This is the frame buffer device driver for the builtin graphics
118 chipset found in Amigas.
120 To compile this driver as a module, choose M here: the
121 module will be called amifb.
124 bool "Amiga OCS chipset support"
127 This enables support for the original Agnus and Denise video chips,
128 found in the Amiga 1000 and most A500's and A2000's. If you intend
129 to run Linux on any of these systems, say Y; otherwise say N.
132 bool "Amiga ECS chipset support"
135 This enables support for the Enhanced Chip Set, found in later
136 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
137 you intend to run Linux on any of these systems, say Y; otherwise
141 bool "Amiga AGA chipset support"
144 This enables support for the Advanced Graphics Architecture (also
145 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
146 and CD32. If you intend to run Linux on any of these systems, say Y;
150 tristate "Amiga CyberVision 64 support"
151 depends on FB && ZORRO && BROKEN
153 This enables support for the Cybervision 64 graphics card from
154 Phase5. Please note that its use is not all that intuitive (i.e. if
155 you have any questions, be sure to ask!). Say N unless you have a
156 Cybervision 64 or plan to get one before you next recompile the
157 kernel. Please note that this driver DOES NOT support the
158 Cybervision 64/3D card, as they use incompatible video chips.
161 bool "Amiga CyberVision 64/3D support "
162 depends on FB && ZORRO && BROKEN
164 This enables support for the Cybervision 64/3D graphics card from
165 Phase5. Please note that its use is not all that intuitive (i.e. if
166 you have any questions, be sure to ask!). Say N unless you have a
167 Cybervision 64/3D or plan to get one before you next recompile the
168 kernel. Please note that this driver DOES NOT support the older
169 Cybervision 64 card, as they use incompatible video chips.
172 tristate "Amiga Retina Z3 support"
173 depends on FB && ZORRO && BROKEN
175 This enables support for the Retina Z3 graphics card. Say N unless
176 you have a Retina Z3 or plan to get one before you next recompile
180 bool "Amiga FrameMaster II/Rainbow II support"
181 depends on FB && ZORRO
183 This is the frame buffer device driver for the Amiga FrameMaster
184 card from BSC (exhibited 1992 but not shipped as a CBM product).
187 bool "Atari native chipset support"
188 depends on FB && ATARI && BROKEN
190 This is the frame buffer device driver for the builtin graphics
191 chipset found in Ataris.
194 bool "Open Firmware frame buffer device support"
195 depends on FB && (PPC64 || PPC_OF)
197 Say Y if you want support with Open Firmware for your graphics
201 bool "Apple \"control\" display support"
202 depends on FB && PPC_PMAC
204 This driver supports a frame buffer for the graphics adapter in the
205 Power Macintosh 7300 and others.
208 bool "Apple \"platinum\" display support"
209 depends on FB && PPC_PMAC
211 This driver supports a frame buffer for the "platinum" graphics
212 adapter in some Power Macintoshes.
215 bool "Apple \"valkyrie\" display support"
216 depends on FB && (MAC || PPC_PMAC)
218 This driver supports a frame buffer for the "valkyrie" graphics
219 adapter in some Power Macintoshes.
222 bool "Chips 65550 display support"
225 This is the frame buffer device driver for the Chips & Technologies
226 65550 graphics chip in PowerBooks.
229 bool "Chips 69000 display support"
233 bool "IMS Twin Turbo display support"
236 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
237 many Macintosh and compatible computers.
240 bool "S3 Trio display support"
241 depends on FB && PPC && BROKEN
243 If you have a S3 Trio say Y. Say N for S3 Virge.
246 tristate "VGA 16-color graphics support"
247 depends on FB && (X86 || PPC)
249 This is the frame buffer device driver for VGA 16 color graphic
250 cards. Say Y if you have such a card.
252 To compile this driver as a module, choose M here: the
253 module will be called vga16fb.
256 tristate "HP STI frame buffer device support"
257 depends on FB && PARISC
260 STI refers to the HP "Standard Text Interface" which is a set of
261 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
262 Enabling this option will implement the linux framebuffer device
263 using calls to the STI BIOS routines for initialisation.
265 If you enable this option, you will get a planar framebuffer device
266 /dev/fb which will work on the most common HP graphic cards of the
267 NGLE family, including the artist chips (in the 7xx and Bxxx series),
268 HCRX, HCRX24, CRX, CRX24 and VisEG series.
270 It is safe to enable this option, so you should probably say "Y".
273 bool "Generic Macintosh display support"
276 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
279 depends on FB && HP300
283 tristate "TGA framebuffer support"
284 depends on FB && ALPHA
286 This is the frame buffer device driver for generic TGA graphic
287 cards. Say Y if you have one of those.
290 bool "VESA VGA graphics support"
291 depends on FB && (X86 || X86_64)
293 This is the frame buffer device driver for generic VESA 2.0
294 compliant graphic cards. The older VESA 1.2 cards are not supported.
295 You will get a boot time penguin logo at no additional cost. Please
296 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
304 tristate "Hercules mono graphics support"
307 Say Y here if you have a Hercules mono graphics card.
309 To compile this driver as a module, choose M here: the
310 module will be called hgafb.
312 As this card technology is 15 years old, most people will answer N
316 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
317 depends on FB_HGA && EXPERIMENTAL
319 This will compile the Hercules mono graphics with
320 acceleration functions.
329 tristate "SGI Visual Workstation framebuffer support"
330 depends on FB && X86_VISWS
332 SGI Visual Workstation support for framebuffer graphics.
335 bool "SGI Graphics Backend frame buffer support"
336 depends on FB && (SGI_IP32 || X86_VISWS)
338 This is the frame buffer device driver for SGI Graphics Backend.
339 This chip is used in SGI O2 and Visual Workstation 320/540.
342 int "Video memory size in MB"
346 This is the amount of memory reserved for the framebuffer,
347 which can be any value between 1MB and 8MB.
351 depends on FB && VISWS
355 bool "Sun3 framebuffer support"
356 depends on FB && (SUN3 || SUN3X) && BROKEN
360 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
362 This is the frame buffer device driver for the BWtwo frame buffer.
365 bool "CGthree support"
366 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
368 This is the frame buffer device driver for the CGthree frame buffer.
371 bool "CGsix (GX,TurboGX) support"
372 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
374 This is the frame buffer device driver for the CGsix (GX, TurboGX)
378 tristate "NEC PowerVR 2 display support"
379 depends on FB && SH_DREAMCAST
381 Say Y here if you have a PowerVR 2 card in your box. If you plan to
382 run linux on your Dreamcast, you will have to say Y here.
383 This driver may or may not work on other PowerVR 2 cards, but is
384 totally untested. Use at your own risk. If unsure, say N.
386 To compile this driver as a module, choose M here: the
387 module will be called pvr2fb.
389 You can pass several parameters to the driver at boot time or at
390 module load time. The parameters look like "video=pvr2:XXX", where
391 the meaning of XXX can be found at the end of the main source file
392 (<file:drivers/video/pvr2fb.c>). Please see the file
393 <file:Documentation/fb/pvr2fb.txt>.
396 bool "Epson 1355 framebuffer support"
397 depends on FB && SUPERH
399 Build in support for the SED1355 Epson Research Embedded RAMDAC
400 LCD/CRT Controller (since redesignated as the S1D13505) as a
401 framebuffer. Product specs at
402 <http://www.erd.epson.com/vdc/html/products.htm>.
404 config E1355_REG_BASE
405 hex "Register Base Address"
409 Epson SED1355/S1D13505 LCD/CRT controller register base address.
411 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
415 hex "Framebuffer Base Address"
419 Epson SED1355/S1D13505 LCD/CRT controller memory base address. See
421 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
425 tristate "nVidia Riva support"
427 select I2C_ALGOBIT if FB_RIVA_I2C
428 select I2C if FB_RIVA_I2C
430 This driver supports graphics boards with the nVidia Riva/Geforce
432 Say Y if you have such a graphics board.
434 To compile this driver as a module, choose M here: the
435 module will be called rivafb.
438 bool "Enable DDC Support"
441 This enables I2C support for nVidia Chipsets. This is used
442 only for getting EDID information from the attached display
443 allowing for robust video mode handling and switching.
445 Because fbdev-2.6 requires that drivers must be able to
446 independently validate video mode parameters, you should say Y
450 bool "Lots of debug output from Riva(nVidia) driver"
454 Say Y here if you want the Riva driver to output all sorts
455 of debugging informations to provide to the maintainer when
456 something goes wrong.
459 tristate "Intel 810/815 support (EXPERIMENTAL)"
460 depends on FB && AGP && AGP_INTEL && EXPERIMENTAL && PCI
462 This driver supports the on-board graphics built in to the Intel 810
463 and 815 chipsets. Say Y if you have and plan to use such a board.
465 To compile this driver as a module, choose M here: the
466 module will be called i810fb.
468 For more information, please read
469 <file:Documentation/fb/intel810.txt>
472 bool "use VESA Generalized Timing Formula"
475 If you say Y, then the VESA standard, Generalized Timing Formula
476 or GTF, will be used to calculate the required video timing values
477 per video mode. Since the GTF allows nondiscrete timings
478 (nondiscrete being a range of values as opposed to discrete being a
479 set of values), you'll be able to use any combination of horizontal
480 and vertical resolutions, and vertical refresh rates without having
481 to specify your own timing parameters. This is especially useful
482 to maximize the performance of an aging display, or if you just
483 have a display with nonstandard dimensions. A VESA compliant
484 monitor is recommended, but can still work with non-compliant ones.
485 If you need or want this, then select this option. The timings may
486 not be compliant with Intel's recommended values. Use at your own
489 If you say N, the driver will revert to discrete video timings
490 using a set recommended by Intel in their documentation.
495 tristate "Matrox acceleration"
498 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
499 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
500 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
501 Matrox G400, G450 or G550 card in your box.
503 To compile this driver as a module, choose M here: the
504 module will be called matroxfb.
506 You can pass several parameters to the driver at boot time or at
507 module load time. The parameters look like "video=matrox:XXX", and
508 are described in <file:Documentation/fb/matroxfb.txt>.
510 config FB_MATROX_MILLENIUM
511 bool "Millennium I/II support"
514 Say Y here if you have a Matrox Millennium or Matrox Millennium II
515 video card. If you select "Advanced lowlevel driver options" below,
516 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
517 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
518 also use font widths different from 8.
520 config FB_MATROX_MYSTIQUE
521 bool "Mystique support"
524 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
525 video card. If you select "Advanced lowlevel driver options" below,
526 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
527 packed pixel and 32 bpp packed pixel. You can also use font widths
530 config FB_MATROX_G450
531 bool "G100/G200/G400/G450/G550 support"
534 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
535 video card. If you select "Advanced lowlevel driver options", you
536 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
537 pixel and 32 bpp packed pixel. You can also use font widths
540 If you need support for G400 secondary head, you must first say Y to
541 "I2C support" and "I2C bit-banging support" in the character devices
542 section, and then to "Matrox I2C support" and "G400 second head
543 support" here in the framebuffer section. G450/G550 secondary head
544 and digital output are supported without additional modules.
546 The driver starts in monitor mode. You must use the matroxset tool
547 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
548 swap primary and secondary head outputs, or to change output mode.
549 Secondary head driver always start in 640x480 resolution and you
550 must use fbset to change it.
552 Do not forget that second head supports only 16 and 32 bpp
553 packed pixels, so it is a good idea to compile them into the kernel
554 too. You can use only some font widths, as the driver uses generic
555 painting procedures (the secondary head does not use acceleration
558 G450/G550 hardware can display TV picture only from secondary CRTC,
559 and it performs no scaling, so picture must have 525 or 625 lines.
561 config FB_MATROX_G100A
562 bool "G100/G200/G400 support"
563 depends on FB_MATROX && !FB_MATROX_G450
565 Say Y here if you have a Matrox G100, G200 or G400 based
566 video card. If you select "Advanced lowlevel driver options", you
567 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
568 pixel and 32 bpp packed pixel. You can also use font widths
571 If you need support for G400 secondary head, you must first say Y to
572 "I2C support" and "I2C bit-banging support" in the character devices
573 section, and then to "Matrox I2C support" and "G400 second head
574 support" here in the framebuffer section.
576 config FB_MATROX_G100
578 depends on FB_MATROX && (FB_MATROX_G450 || FB_MATROX_G100A)
582 tristate "Matrox I2C support"
583 depends on FB_MATROX && I2C
586 This drivers creates I2C buses which are needed for accessing the
587 DDC (I2C) bus present on all Matroxes, an I2C bus which
588 interconnects Matrox optional devices, like MGA-TVO on G200 and
589 G400, and the secondary head DDC bus, present on G400 only.
591 You can say Y or M here if you want to experiment with monitor
592 detection code. You must say Y or M here if you want to use either
593 second head of G400 or MGA-TVO on G200 or G400.
595 If you compile it as module, it will create a module named
598 config FB_MATROX_MAVEN
599 tristate "G400 second head support"
600 depends on FB_MATROX_G100 && FB_MATROX_I2C
602 WARNING !!! This support does not work with G450 !!!
604 Say Y or M here if you want to use a secondary head (meaning two
605 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
606 head is not compatible with accelerated XFree 3.3.x SVGA servers -
607 secondary head output is blanked while you are in X. With XFree
608 3.9.17 preview you can use both heads if you use SVGA over fbdev or
609 the fbdev driver on first head and the fbdev driver on second head.
611 If you compile it as module, two modules are created,
612 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
613 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
614 also load i2c-matroxfb to get it to run.
616 The driver starts in monitor mode and you must use the matroxset
618 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
619 PAL or NTSC or to swap primary and secondary head outputs.
620 Secondary head driver also always start in 640x480 resolution, you
621 must use fbset to change it.
623 Also do not forget that second head supports only 16 and 32 bpp
624 packed pixels, so it is a good idea to compile them into the kernel
625 too. You can use only some font widths, as the driver uses generic
626 painting procedures (the secondary head does not use acceleration
629 config FB_MATROX_MULTIHEAD
630 bool "Multihead support"
633 Say Y here if you have more than one (supported) Matrox device in
634 your computer and you want to use all of them for different monitors
635 ("multihead"). If you have only one device, you should say N because
636 the driver compiled with Y is larger and a bit slower, especially on
639 If you said M to "Matrox unified accelerated driver" and N here, you
640 will still be able to use several Matrox devices simultaneously:
641 insert several instances of the module matroxfb into the kernel
642 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
643 for the different Matrox devices. This method is slightly faster but
644 uses 40 KB of kernel memory per Matrox card.
646 There is no need for enabling 'Matrox multihead support' if you have
647 only one Matrox card in the box.
650 tristate "ATI Radeon display support (Old driver)"
653 Choose this option if you want to use an ATI Radeon graphics card as
654 a framebuffer device. There are both PCI and AGP versions. You
655 don't need to choose this to run the Radeon in plain VGA mode.
656 There is a product page at
657 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
660 tristate "ATI Radeon display support"
662 select I2C_ALGOBIT if FB_RADEON_I2C
663 select I2C if FB_RADEON_I2C
665 Choose this option if you want to use an ATI Radeon graphics card as
666 a framebuffer device. There are both PCI and AGP versions. You
667 don't need to choose this to run the Radeon in plain VGA mode.
669 If you say Y here and want DDC/I2C support you must first say Y to
670 "I2C support" and "I2C bit-banging support" in the character devices
673 If you say M here then "I2C support" and "I2C bit-banging support"
674 can be build either as modules or built-in.
676 There is a product page at
677 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
680 bool "DDC/I2C for ATI Radeon support"
684 Say Y here if you want DDC/I2C support for your Radeon board.
686 config FB_RADEON_DEBUG
687 bool "Lots of debug output from Radeon driver"
691 Say Y here if you want the Radeon driver to output all sorts
692 of debugging informations to provide to the maintainer when
693 something goes wrong.
696 tristate "ATI Rage128 display support"
699 This driver supports graphics boards with the ATI Rage128 chips.
700 Say Y if you have such a graphics board and read
701 <file:Documentation/fb/aty128fb.txt>.
703 To compile this driver as a module, choose M here: the
704 module will be called aty128fb.
707 tristate "ATI Mach64 display support" if PCI || ATARI
710 This driver supports graphics boards with the ATI Mach64 chips.
711 Say Y if you have such a graphics board.
713 To compile this driver as a module, choose M here: the
714 module will be called atyfb.
717 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
718 depends on PCI && FB_ATY
719 default y if SPARC64 && FB_PCI
721 Say Y here to support use of ATI's 64-bit Rage boards (or other
722 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
723 framebuffer device. The ATI product support page for these boards
724 is at <http://support.ati.com/products/pc/mach64/>.
727 bool "Mach64 GX support" if PCI
731 Say Y here to support use of the ATI Mach64 Graphics Expression
732 board (or other boards based on the Mach64 GX chipset) as a
733 framebuffer device. The ATI product support page for these boards
735 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
737 config FB_ATY_XL_INIT
738 bool " Rage XL No-BIOS Init support" if FB_ATY_CT
741 Say Y here to support booting a Rage XL without BIOS support.
744 tristate "SiS acceleration"
747 This is the frame buffer device driver for the SiS 300, 315 and
748 330 series VGA chipsets. Specs available at http://www.sis.com
750 To compile this driver as a module, choose M here; the module
751 will be called sisfb.
754 bool "SiS 300 series support"
757 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
760 bool "SiS 315/330 series support"
763 Say Y here to support use of the SiS 315 and 330 series
764 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760).
767 tristate "NeoMagic display support"
770 This driver supports notebooks with NeoMagic PCI chips.
771 Say Y if you have such a graphics card.
773 To compile this driver as a module, choose M here: the
774 module will be called neofb.
777 tristate "IMG Kyro support"
780 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
783 To compile this driver as a module, choose M here: the
784 module will be called kyrofb.
787 tristate "3Dfx Banshee/Voodoo3 display support"
790 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
791 chips. Say Y if you have such a graphics board.
793 To compile this driver as a module, choose M here: the
794 module will be called tdfxfb.
797 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
798 depends on FB_3DFX && EXPERIMENTAL
800 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
801 with acceleration functions.
805 tristate "3Dfx Voodoo Graphics (sst1) support"
808 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
809 Voodoo2 (cvg) based graphics card.
811 To compile this driver as a module, choose M here: the
812 module will be called sstfb.
814 WARNING: Do not use any application that uses the 3D engine
815 (namely glide) while using this driver.
816 Please read the file Documentation/fb/README-sstfb.txt for supported
817 options and other important info support.
820 tristate "Trident support"
823 This driver is supposed to support graphics boards with the
824 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
825 but also on some motherboards. For more information, read
826 <file:Documentation/fb/tridentfb.txt>
828 Say Y if you have such a graphics board.
830 To compile this driver as a module, choose M here: the
831 module will be called tridentfb.
833 config FB_TRIDENT_ACCEL
834 bool "Trident Acceleration functions (EXPERIMENTAL)"
835 depends on FB_TRIDENT && EXPERIMENTAL
837 This will compile the Trident frame buffer device with
838 acceleration functions.
842 tristate "Permedia3 support"
843 depends on FB && PCI && BROKEN
845 This is the frame buffer device driver for the 3DLabs Permedia3
846 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
847 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
848 and maybe other boards.
851 bool "SBUS and UPA framebuffers"
852 depends on FB && (SPARC32 || SPARC64)
854 Say Y if you want support for SBUS or UPA based frame buffer device.
857 bool "Creator/Creator3D/Elite3D support"
858 depends on FB_SBUS && SPARC64
860 This is the frame buffer device driver for the Creator, Creator3D,
861 and Elite3D graphics boards.
864 bool "TCX (SS4/SS5 only) support"
867 This is the frame buffer device driver for the TCX 24/8bit frame
871 bool "CGfourteen (SX) support"
874 This is the frame buffer device driver for the CGfourteen frame
875 buffer on Desktop SPARCsystems with the SX graphics option.
878 bool "P9100 (Sparcbook 3 only) support"
881 This is the frame buffer device driver for the P9100 card
882 supported on Sparcbook 3 machines.
885 bool "Leo (ZX) support"
888 This is the frame buffer device driver for the SBUS-based Sun ZX
889 (leo) frame buffer cards.
892 bool "PCI framebuffers"
893 depends on FB && PCI && (SPARC64 || SPARC32)
896 bool "IGA 168x display support"
897 depends on SPARC32 && FB_PCI
899 This is the framebuffer device for the INTERGRAPHICS 1680 and
900 successor frame buffer cards.
903 tristate "HD64461 Frame Buffer support"
904 depends on FB && HD64461
906 This is the frame buffer device driver for the Hitachi HD64461 LCD
910 bool "PMAG-BA TURBOchannel framebuffer support"
911 depends on FB && DECSTATION && TC
913 Say Y here to directly support the on-board PMAG-BA framebuffer in
914 the 5000/1xx versions of the DECstation. There is a page dedicated
915 to Linux on DECstations at <http://decstation.unix-ag.org/>.
918 bool "PMAGB-B TURBOchannel framebuffer spport"
919 depends on FB && DECSTATION && TC
921 Say Y here to directly support the on-board PMAGB-B framebuffer in
922 the 5000/1xx versions of the DECstation. There is a page dedicated
923 to Linux on DECstations at <http://decstation.unix-ag.org/>.
926 bool "Maxine (Personal DECstation) onboard framebuffer spport"
927 depends on FB && DECSTATION && TC
929 Say Y here to directly support the on-board framebuffer in the
930 Maxine (5000/20, /25, /33) version of the DECstation. There is a
931 page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
934 bool "TMPTX3912/PR31700 frame buffer support"
935 depends on FB && NINO
937 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
938 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
940 Say Y here to enable kernel support for the on-board framebuffer.
943 bool "Motorola 68328 native frame buffer support"
944 depends on (M68328 || M68EZ328 || M68VZ328)
946 Say Y here if you want to support the built-in frame buffer of
947 the Motorola 68328 CPU family.
950 tristate "PXA LCD framebuffer support"
951 depends on FB && ARCH_PXA
953 Frame buffer driver for the built-in LCD controller in the Intel
956 This driver is also available as a module ( = code which can be
957 inserted and removed from the running kernel whenever you want). The
958 module will be called vfb. If you want to compile it as a module,
959 say M here and read <file:Documentation/modules.txt>.
963 config FB_PXA_PARAMETERS
964 bool "PXA LCD command line parameters"
968 Enable the use of kernel command line or module parameters
969 to configure the physical properties of the LCD panel when
970 using the PXA LCD driver.
972 This option allows you to override the panel parameters
973 supplied by the platform in order to support multiple
974 different models of flatpanel. If you will only be using a
975 single model of flatpanel then you can safely leave this
978 Documentation/fb/pxafb.txt describes the available parameters.
981 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
984 This is a `virtual' frame buffer device. It operates on a chunk of
985 unswappable kernel memory instead of on the memory of a graphics
986 board. This means you cannot see any output sent to this frame
987 buffer device, while it does consume precious memory. The main use
988 of this frame buffer device is testing and debugging the frame
989 buffer subsystem. Do NOT enable it for normal systems! To protect
990 the innocent, it has to be enabled explicitly at boot time using the
991 kernel option `video=vfb:'.
993 To compile this driver as a module, choose M here: the
994 module will be called vfb.
998 source "drivers/video/console/Kconfig"
1001 if FB || SGI_NEWPORT_CONSOLE
1002 source "drivers/video/logo/Kconfig"