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 && (AMIGA || PCI) && BROKEN
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"
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 "IMS Twin Turbo display support"
232 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
233 many Macintosh and compatible computers.
236 bool "S3 Trio display support"
239 If you have a S3 Trio say Y. Say N for S3 Virge.
242 tristate "VGA 16-color graphics support"
243 depends on FB && (X86 || PPC)
245 This is the frame buffer device driver for VGA 16 color graphic
246 cards. Say Y if you have such a card.
248 To compile this driver as a module, choose M here: the
249 module will be called vga16fb.
252 tristate "HP STI frame buffer device support"
253 depends on FB && PARISC
256 STI refers to the HP "Standard Text Interface" which is a set of
257 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
258 Enabling this option will implement the linux framebuffer device
259 using calls to the STI BIOS routines for initialisation.
261 If you enable this option, you will get a planar framebuffer device
262 /dev/fb which will work on the most common HP graphic cards of the
263 NGLE family, including the artist chips (in the 7xx and Bxxx series),
264 HCRX, HCRX24, CRX, CRX24 and VisEG series.
266 It is safe to enable this option, so you should probably say "Y".
269 bool "Generic Macintosh display support"
272 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
275 depends on FB && HP300
279 tristate "TGA framebuffer support"
280 depends on FB && ALPHA
282 This is the frame buffer device driver for generic TGA graphic
283 cards. Say Y if you have one of those.
286 bool "VESA VGA graphics support"
287 depends on FB && (X86 || X86_64)
289 This is the frame buffer device driver for generic VESA 2.0
290 compliant graphic cards. The older VESA 1.2 cards are not supported.
291 You will get a boot time penguin logo at no additional cost. Please
292 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
300 tristate "Hercules mono graphics support"
303 Say Y here if you have a Hercules mono graphics card.
305 To compile this driver as a module, choose M here: the
306 module will be called hgafb.
308 As this card technology is 15 years old, most people will answer N
317 tristate "SGI Visual Workstation framebuffer support"
318 depends on FB && X86_VISWS
320 SGI Visual Workstation support for framebuffer graphics.
324 depends on FB && VISWS
328 bool "Sun3 framebuffer support"
329 depends on FB && (SUN3 || SUN3X) && BROKEN
333 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
335 This is the frame buffer device driver for the BWtwo frame buffer.
338 bool "CGthree support"
339 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
341 This is the frame buffer device driver for the CGthree frame buffer.
344 bool "CGsix (GX,TurboGX) support"
345 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
347 This is the frame buffer device driver for the CGsix (GX, TurboGX)
351 tristate "NEC PowerVR 2 display support"
352 depends on FB && SH_DREAMCAST
354 Say Y here if you have a PowerVR 2 card in your box. If you plan to
355 run linux on your Dreamcast, you will have to say Y here.
356 This driver may or may not work on other PowerVR 2 cards, but is
357 totally untested. Use at your own risk. If unsure, say N.
359 To compile this driver as a module, choose M here: the
360 module will be called pvr2fb.
362 You can pass several parameters to the driver at boot time or at
363 module load time. The parameters look like "video=pvr2:XXX", where
364 the meaning of XXX can be found at the end of the main source file
365 (<file:drivers/video/pvr2fb.c>). Please see the file
366 <file:Documentation/fb/pvr2fb.txt>.
369 bool "Epson 1355 framebuffer support"
370 depends on FB && SUPERH
372 Build in support for the SED1355 Epson Research Embedded RAMDAC
373 LCD/CRT Controller (since redesignated as the S1D13505) as a
374 framebuffer. Product specs at
375 <http://www.erd.epson.com/vdc/html/products.htm>.
377 config E1355_REG_BASE
378 hex "Register Base Address"
382 Epson SED1355/S1D13505 LCD/CRT controller register base address.
384 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
388 hex "Framebuffer Base Address"
392 Epson SED1355/S1D13505 LCD/CRT controller memory base address. See
394 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
398 tristate "nVidia Riva support"
401 This driver supports graphics boards with the nVidia Riva/Geforce
403 Say Y if you have such a graphics board.
405 To compile this driver as a module, choose M here: the
406 module will be called rivafb.
409 tristate "Intel 810/815 support (EXPERIMENTAL)"
410 depends on FB && AGP && AGP_INTEL && EXPERIMENTAL && PCI
412 This driver supports the on-board graphics built in to the Intel 810
413 and 815 chipsets. Say Y if you have and plan to use such a board.
415 To compile this driver as a module, choose M here: the
416 module will be called i810fb.
418 For more information, please read
419 <file:Documentation/fb/intel810.txt>
422 bool "use VESA Generalized Timing Formula"
425 If you say Y, then the VESA standard, Generalized Timing Formula
426 or GTF, will be used to calculate the required video timing values
427 per video mode. Since the GTF allows nondiscrete timings
428 (nondiscrete being a range of values as opposed to discrete being a
429 set of values), you'll be able to use any combination of horizontal
430 and vertical resolutions, and vertical refresh rates without having
431 to specify your own timing parameters. This is especially useful
432 to maximize the performance of an aging display, or if you just
433 have a display with nonstandard dimensions. A VESA compliant
434 monitor is recommended, but can still work with non-compliant ones.
435 If you need or want this, then select this option. The timings may
436 not be compliant with Intel's recommended values. Use at your own
439 If you say N, the driver will revert to discrete video timings
440 using a set recommended by Intel in their documentation.
445 tristate "Matrox acceleration"
448 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
449 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
450 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
451 Matrox G400, G450 or G550 card in your box.
453 To compile this driver as a module, choose M here: the
454 module will be called matroxfb.
456 You can pass several parameters to the driver at boot time or at
457 module load time. The parameters look like "video=matrox:XXX", and
458 are described in <file:Documentation/fb/matroxfb.txt>.
460 config FB_MATROX_MILLENIUM
461 bool "Millennium I/II support"
464 Say Y here if you have a Matrox Millennium or Matrox Millennium II
465 video card. If you select "Advanced lowlevel driver options" below,
466 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
467 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
468 also use font widths different from 8.
470 config FB_MATROX_MYSTIQUE
471 bool "Mystique support"
474 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
475 video card. If you select "Advanced lowlevel driver options" below,
476 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
477 packed pixel and 32 bpp packed pixel. You can also use font widths
480 config FB_MATROX_G450
481 bool "G100/G200/G400/G450/G550 support"
484 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
485 video card. If you select "Advanced lowlevel driver options", you
486 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
487 pixel and 32 bpp packed pixel. You can also use font widths
490 If you need support for G400 secondary head, you must first say Y to
491 "I2C support" and "I2C bit-banging support" in the character devices
492 section, and then to "Matrox I2C support" and "G400 second head
493 support" here in the framebuffer section. G450/G550 secondary head
494 and digital output are supported without additional modules.
496 The driver starts in monitor mode. You must use the matroxset tool
497 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
498 swap primary and secondary head outputs, or to change output mode.
499 Secondary head driver always start in 640x480 resolution and you
500 must use fbset to change it.
502 Do not forget that second head supports only 16 and 32 bpp
503 packed pixels, so it is a good idea to compile them into the kernel
504 too. You can use only some font widths, as the driver uses generic
505 painting procedures (the secondary head does not use acceleration
508 G450/G550 hardware can display TV picture only from secondary CRTC,
509 and it performs no scaling, so picture must have 525 or 625 lines.
511 config FB_MATROX_G100A
512 bool "G100/G200/G400 support"
513 depends on FB_MATROX && !FB_MATROX_G450
515 Say Y here if you have a Matrox G100, G200 or G400 based
516 video card. If you select "Advanced lowlevel driver options", you
517 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
518 pixel and 32 bpp packed pixel. You can also use font widths
521 If you need support for G400 secondary head, you must first say Y to
522 "I2C support" and "I2C bit-banging support" in the character devices
523 section, and then to "Matrox I2C support" and "G400 second head
524 support" here in the framebuffer section.
526 config FB_MATROX_G100
528 depends on FB_MATROX && (FB_MATROX_G450 || FB_MATROX_G100A)
532 tristate "Matrox I2C support"
533 depends on FB_MATROX && I2C
536 This drivers creates I2C buses which are needed for accessing the
537 DDC (I2C) bus present on all Matroxes, an I2C bus which
538 interconnects Matrox optional devices, like MGA-TVO on G200 and
539 G400, and the secondary head DDC bus, present on G400 only.
541 You can say Y or M here if you want to experiment with monitor
542 detection code. You must say Y or M here if you want to use either
543 second head of G400 or MGA-TVO on G200 or G400.
545 If you compile it as module, it will create a module named
548 config FB_MATROX_MAVEN
549 tristate "G400 second head support"
550 depends on FB_MATROX_G100 && FB_MATROX_I2C
552 WARNING !!! This support does not work with G450 !!!
554 Say Y or M here if you want to use a secondary head (meaning two
555 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
556 head is not compatible with accelerated XFree 3.3.x SVGA servers -
557 secondary head output is blanked while you are in X. With XFree
558 3.9.17 preview you can use both heads if you use SVGA over fbdev or
559 the fbdev driver on first head and the fbdev driver on second head.
561 If you compile it as module, two modules are created,
562 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
563 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
564 also load i2c-matroxfb to get it to run.
566 The driver starts in monitor mode and you must use the matroxset
568 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
569 PAL or NTSC or to swap primary and secondary head outputs.
570 Secondary head driver also always start in 640x480 resolution, you
571 must use fbset to change it.
573 Also do not forget that second head supports only 16 and 32 bpp
574 packed pixels, so it is a good idea to compile them into the kernel
575 too. You can use only some font widths, as the driver uses generic
576 painting procedures (the secondary head does not use acceleration
579 config FB_MATROX_MULTIHEAD
580 bool "Multihead support"
583 Say Y here if you have more than one (supported) Matrox device in
584 your computer and you want to use all of them for different monitors
585 ("multihead"). If you have only one device, you should say N because
586 the driver compiled with Y is larger and a bit slower, especially on
589 If you said M to "Matrox unified accelerated driver" and N here, you
590 will still be able to use several Matrox devices simultaneously:
591 insert several instances of the module matroxfb into the kernel
592 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
593 for the different Matrox devices. This method is slightly faster but
594 uses 40 KB of kernel memory per Matrox card.
596 There is no need for enabling 'Matrox multihead support' if you have
597 only one Matrox card in the box.
600 tristate "ATI Radeon display support (Old driver)"
603 Choose this option if you want to use an ATI Radeon graphics card as
604 a framebuffer device. There are both PCI and AGP versions. You
605 don't need to choose this to run the Radeon in plain VGA mode.
606 There is a product page at
607 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
610 tristate "ATI Radeon display support"
612 select I2C_ALGOBIT if FB_RADEON_I2C
613 select I2C if FB_RADEON_I2C
615 Choose this option if you want to use an ATI Radeon graphics card as
616 a framebuffer device. There are both PCI and AGP versions. You
617 don't need to choose this to run the Radeon in plain VGA mode.
619 If you say Y here and want DDC/I2C support you must first say Y to
620 "I2C support" and "I2C bit-banging support" in the character devices
623 If you say M here then "I2C support" and "I2C bit-banging support"
624 can be build either as modules or built-in.
626 There is a product page at
627 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
630 bool "DDC/I2C for ATI Radeon support"
634 Say Y here if you want DDC/I2C support for your Radeon board.
636 config FB_RADEON_DEBUG
637 bool "Lots of debug output from Radeon driver"
641 Say Y here if you want the Radeon driver to output all sorts
642 of debugging informations to provide to the maintainer when
643 something goes wrong.
646 tristate "ATI Rage128 display support"
649 This driver supports graphics boards with the ATI Rage128 chips.
650 Say Y if you have such a graphics board and read
651 <file:Documentation/fb/aty128fb.txt>.
653 To compile this driver as a module, choose M here: the
654 module will be called aty128fb.
657 tristate "ATI Mach64 display support" if PCI || ATARI
660 This driver supports graphics boards with the ATI Mach64 chips.
661 Say Y if you have such a graphics board.
663 To compile this driver as a module, choose M here: the
664 module will be called atyfb.
667 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
668 depends on PCI && FB_ATY
669 default y if SPARC64 && FB_PCI
671 Say Y here to support use of ATI's 64-bit Rage boards (or other
672 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
673 framebuffer device. The ATI product support page for these boards
674 is at <http://support.ati.com/products/pc/mach64/>.
677 bool "Mach64 GX support" if PCI
681 Say Y here to support use of the ATI Mach64 Graphics Expression
682 board (or other boards based on the Mach64 GX chipset) as a
683 framebuffer device. The ATI product support page for these boards
685 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
687 config FB_ATY_XL_INIT
688 bool " Rage XL No-BIOS Init support" if FB_ATY_CT
691 Say Y here to support booting a Rage XL without BIOS support.
694 tristate "SiS acceleration"
697 This is the frame buffer device driver for the SiS 300, 315 and
698 330 series VGA chipsets. Specs available at http://www.sis.com
700 To compile this driver as a module, choose M here; the module
701 will be called sisfb.
704 bool "SiS 300 series support"
707 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
710 bool "SiS 315/330 series support"
713 Say Y here to support use of the SiS 315 and 330 series
714 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760).
717 tristate "NeoMagic display support"
720 This driver supports notebooks with NeoMagic PCI chips.
721 Say Y if you have such a graphics card.
723 To compile this driver as a module, choose M here: the
724 module will be called neofb.
727 tristate "IMG Kyro support"
730 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
733 To compile this driver as a module, choose M here: the
734 module will be called kyrofb.
737 tristate "3Dfx Banshee/Voodoo3 display support"
740 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
741 chips. Say Y if you have such a graphics board.
743 To compile this driver as a module, choose M here: the
744 module will be called tdfxfb.
747 tristate "3Dfx Voodoo Graphics (sst1) support"
750 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
751 Voodoo2 (cvg) based graphics card.
753 To compile this driver as a module, choose M here: the
754 module will be called sstfb.
756 WARNING: Do not use any application that uses the 3D engine
757 (namely glide) while using this driver.
758 Please read the file Documentation/fb/README-sstfb.txt for supported
759 options and other important info support.
762 tristate "Trident support"
765 This driver is supposed to support graphics boards with the
766 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
767 but also on some motherboards. For more information, read
768 <file:Documentation/fb/tridentfb.txt>
770 Say Y if you have such a graphics board.
772 To compile this driver as a module, choose M here: the
773 module will be called tridentfb.
776 tristate "Permedia3 support"
777 depends on FB && PCI && BROKEN
779 This is the frame buffer device driver for the 3DLabs Permedia3
780 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
781 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
782 and maybe other boards.
785 bool "SBUS and UPA framebuffers"
786 depends on FB && (SPARC32 || SPARC64)
788 Say Y if you want support for SBUS or UPA based frame buffer device.
791 bool "Creator/Creator3D/Elite3D support"
792 depends on FB_SBUS && SPARC64
794 This is the frame buffer device driver for the Creator, Creator3D,
795 and Elite3D graphics boards.
798 bool "TCX (SS4/SS5 only) support"
801 This is the frame buffer device driver for the TCX 24/8bit frame
805 bool "CGfourteen (SX) support"
808 This is the frame buffer device driver for the CGfourteen frame
809 buffer on Desktop SPARCsystems with the SX graphics option.
812 bool "P9100 (Sparcbook 3 only) support"
815 This is the frame buffer device driver for the P9100 card
816 supported on Sparcbook 3 machines.
819 bool "Leo (ZX) support"
822 This is the frame buffer device driver for the SBUS-based Sun ZX
823 (leo) frame buffer cards.
826 bool "PCI framebuffers"
827 depends on FB && PCI && (SPARC64 || SPARC32)
830 bool "IGA 168x display support"
831 depends on SPARC32 && FB_PCI
833 This is the framebuffer device for the INTERGRAPHICS 1680 and
834 successor frame buffer cards.
837 tristate "HD64461 Frame Buffer support"
838 depends on FB && HD64461
840 This is the frame buffer device driver for the Hitachi HD64461 LCD
844 bool "PMAG-BA TURBOchannel framebuffer support"
845 depends on FB && DECSTATION && TC
847 Say Y here to directly support the on-board PMAG-BA framebuffer in
848 the 5000/1xx versions of the DECstation. There is a page dedicated
849 to Linux on DECstations at <http://decstation.unix-ag.org/>.
852 bool "PMAGB-B TURBOchannel framebuffer spport"
853 depends on FB && DECSTATION && TC
855 Say Y here to directly support the on-board PMAGB-B framebuffer in
856 the 5000/1xx versions of the DECstation. There is a page dedicated
857 to Linux on DECstations at <http://decstation.unix-ag.org/>.
860 bool "Maxine (Personal DECstation) onboard framebuffer spport"
861 depends on FB && DECSTATION && TC
863 Say Y here to directly support the on-board framebuffer in the
864 Maxine (5000/20, /25, /33) version of the DECstation. There is a
865 page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
868 bool "TMPTX3912/PR31700 frame buffer support"
869 depends on FB && NINO
871 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
872 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
874 Say Y here to enable kernel support for the on-board framebuffer.
877 bool "Motorola 68328 native frame buffer support"
878 depends on (M68328 || M68EZ328 || M68VZ328)
880 Say Y here if you want to support the built-in frame buffer of
881 the Motorola 68328 CPU family.
884 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
887 This is a `virtual' frame buffer device. It operates on a chunk of
888 unswappable kernel memory instead of on the memory of a graphics
889 board. This means you cannot see any output sent to this frame
890 buffer device, while it does consume precious memory. The main use
891 of this frame buffer device is testing and debugging the frame
892 buffer subsystem. Do NOT enable it for normal systems! To protect
893 the innocent, it has to be enabled explicitly at boot time using the
894 kernel option `video=vfb:'.
896 To compile this driver as a module, choose M here: the
897 module will be called vfb.
901 source "drivers/video/console/Kconfig"
904 if FB || SGI_NEWPORT_CONSOLE
905 source "drivers/video/logo/Kconfig"