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 || PCI) && BROKEN
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 FIFOI disconnect feature (see CONFIG_FB_PM2).
72 bool "generic Permedia2 PCI board support"
73 depends on FB_PM2 && PCI
75 Say Y to enable support for Permedia2 AGP frame buffer card from
76 3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
79 bool "Phase5 CVisionPPC/BVisionPPC support"
80 depends on FB_PM2 && AMIGA
82 Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
83 framebuffer cards. Phase 5 is no longer with us, alas.
86 bool "Acorn VIDC support"
87 depends on FB && ARM && ARCH_ACORN
89 This is the frame buffer device driver for the Acorn VIDC graphics
90 hardware found in Acorn RISC PCs and other ARM-based machines. If
94 bool "Anakin LCD support"
95 depends on FB && ARM && ARCH_ANAKIN
98 bool "CLPS711X LCD support"
99 depends on FB && ARM && ARCH_CLPS711X
102 bool "SA-1100 LCD support"
103 depends on FB && ARM && ARCH_SA1100
105 This is a framebuffer device for the SA-1100 LCD Controller.
106 See <http://www.linux-fbdev.org/> for information on framebuffer
109 If you plan to use the LCD display with your SA-1100 system, say
113 prompt "CerfBoard LCD Display Size"
114 depends on FB_SA1100 && SA1100_CERF
115 default CERF_LCD_57_A
131 config SA1100_CERF_LCD_BACKLIGHT
132 bool "Cerfboard Backlight (CerfPDA)"
133 depends on FB_SA1100 && SA1100_CERF_CPLD
136 tristate "CyberPro 2000/2010/5000 support"
139 This enables support for the Integraphics CyberPro 20x0 and 5000
140 VGA chips used in the Rebel.com Netwinder and other machines.
141 Say Y if you have a NetWinder or a graphics card containing this
142 device, otherwise say N.
146 depends on FB && APOLLO
155 tristate "Amiga native chipset support"
156 depends on FB && AMIGA
158 This is the frame buffer device driver for the builtin graphics
159 chipset found in Amigas.
161 To compile this driver as a module, choose M here: the
162 module will be called amifb.
165 bool "Amiga OCS chipset support"
168 This enables support for the original Agnus and Denise video chips,
169 found in the Amiga 1000 and most A500's and A2000's. If you intend
170 to run Linux on any of these systems, say Y; otherwise say N.
173 bool "Amiga ECS chipset support"
176 This enables support for the Enhanced Chip Set, found in later
177 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
178 you intend to run Linux on any of these systems, say Y; otherwise
182 bool "Amiga AGA chipset support"
185 This enables support for the Advanced Graphics Architecture (also
186 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
187 and CD32. If you intend to run Linux on any of these systems, say Y;
191 tristate "Amiga CyberVision 64 support"
192 depends on FB && ZORRO && BROKEN
194 This enables support for the Cybervision 64 graphics card from
195 Phase5. Please note that its use is not all that intuitive (i.e. if
196 you have any questions, be sure to ask!). Say N unless you have a
197 Cybervision 64 or plan to get one before you next recompile the
198 kernel. Please note that this driver DOES NOT support the
199 Cybervision 64/3D card, as they use incompatible video chips.
202 bool "Amiga CyberVision 64/3D support "
203 depends on FB && ZORRO && BROKEN
205 This enables support for the Cybervision 64/3D graphics card from
206 Phase5. Please note that its use is not all that intuitive (i.e. if
207 you have any questions, be sure to ask!). Say N unless you have a
208 Cybervision 64/3D or plan to get one before you next recompile the
209 kernel. Please note that this driver DOES NOT support the older
210 Cybervision 64 card, as they use incompatible video chips.
213 tristate "Amiga Retina Z3 support"
214 depends on FB && ZORRO && BROKEN
216 This enables support for the Retina Z3 graphics card. Say N unless
217 you have a Retina Z3 or plan to get one before you next recompile
221 bool "Amiga FrameMaster II/Rainbow II support"
222 depends on FB && ZORRO
224 This is the frame buffer device driver for the Amiga FrameMaster
225 card from BSC (exhibited 1992 but not shipped as a CBM product).
228 bool "Atari native chipset support"
229 depends on FB && ATARI && BROKEN
231 This is the frame buffer device driver for the builtin graphics
232 chipset found in Ataris.
235 bool "Open Firmware frame buffer device support"
236 depends on FB && (PPC64 || PPC_OF)
238 Say Y if you want support with Open Firmware for your graphics
242 bool "Apple \"control\" display support"
243 depends on FB && PPC_PMAC
245 This driver supports a frame buffer for the graphics adapter in the
246 Power Macintosh 7300 and others.
249 bool "Apple \"platinum\" display support"
250 depends on FB && PPC_PMAC
252 This driver supports a frame buffer for the "platinum" graphics
253 adapter in some Power Macintoshes.
256 bool "Apple \"valkyrie\" display support"
257 depends on FB && (MAC || PPC_PMAC)
259 This driver supports a frame buffer for the "valkyrie" graphics
260 adapter in some Power Macintoshes.
263 bool "Chips 65550 display support"
266 This is the frame buffer device driver for the Chips & Technologies
267 65550 graphics chip in PowerBooks.
270 bool "IMS Twin Turbo display support"
273 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
274 many Macintosh and compatible computers.
277 bool "S3 Trio display support"
280 If you have a S3 Trio say Y. Say N for S3 Virge.
283 tristate "VGA 16-color graphics support"
284 depends on FB && (X86 || PPC)
286 This is the frame buffer device driver for VGA 16 color graphic
287 cards. Say Y if you have such a card.
289 To compile this driver as a module, choose M here: the
290 module will be called vga16fb.
293 tristate "HP STI frame buffer device support"
294 depends on FB && PARISC
297 STI refers to the HP "Standard Text Interface" which is a set of
298 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
299 Enabling this option will implement the linux framebuffer device
300 using calls to the STI BIOS routines for initialisation.
302 If you enable this option, you will get a planar framebuffer device
303 /dev/fb which will work on the most common HP graphic cards of the
304 NGLE family, including the artist chips (in the 7xx and Bxxx series),
305 HCRX, HCRX24, CRX, CRX24 and VisEG series.
307 It is safe to enable this option, so you should probably say "Y".
310 bool "Generic Macintosh display support"
313 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
316 depends on FB && HP300
320 tristate "TGA framebuffer support"
321 depends on FB && ALPHA
323 This is the frame buffer device driver for generic TGA graphic
324 cards. Say Y if you have one of those.
327 bool "VESA VGA graphics support"
328 depends on FB && (X86 || X86_64)
330 This is the frame buffer device driver for generic VESA 2.0
331 compliant graphic cards. The older VESA 1.2 cards are not supported.
332 You will get a boot time penguin logo at no additional cost. Please
333 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
341 tristate "Hercules mono graphics support"
344 Say Y here if you have a Hercules mono graphics card.
346 To compile this driver as a module, choose M here: the
347 module will be called hgafb.
349 As this card technology is 15 years old, most people will answer N
358 tristate "SGI Visual Workstation framebuffer support"
359 depends on FB && X86_VISWS
361 SGI Visual Workstation support for framebuffer graphics.
365 depends on FB && VISWS
369 bool "Sun3 framebuffer support"
370 depends on FB && (SUN3 || SUN3X) && BROKEN
374 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
376 This is the frame buffer device driver for the BWtwo frame buffer.
379 bool "CGthree support"
380 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
382 This is the frame buffer device driver for the CGthree frame buffer.
385 bool "CGsix (GX,TurboGX) support"
386 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
388 This is the frame buffer device driver for the CGsix (GX, TurboGX)
392 tristate "NEC PowerVR 2 display support"
393 depends on FB && SH_DREAMCAST
395 Say Y here if you have a PowerVR 2 card in your box. If you plan to
396 run linux on your Dreamcast, you will have to say Y here.
397 This driver may or may not work on other PowerVR 2 cards, but is
398 totally untested. Use at your own risk. If unsure, say N.
400 To compile this driver as a module, choose M here: the
401 module will be called pvr2fb.
403 You can pass several parameters to the driver at boot time or at
404 module load time. The parameters look like "video=pvr2:XXX", where
405 the meaning of XXX can be found at the end of the main source file
406 (<file:drivers/video/pvr2fb.c>). Please see the file
407 <file:Documentation/fb/pvr2fb.txt>.
413 Say Y here if you wish for the pvr2fb driver to print out debugging
414 messages. Most people will want to say N here. If unsure, you will
418 bool "Epson 1355 framebuffer support"
419 depends on FB && SUPERH
421 Build in support for the SED1355 Epson Research Embedded RAMDAC
422 LCD/CRT Controller (since redesignated as the S1D13505) as a
423 framebuffer. Product specs at
424 <http://www.erd.epson.com/vdc/html/products.htm>.
426 config E1355_REG_BASE
427 hex "Register Base Address"
431 Epson SED1355/S1D13505 LCD/CRT controller register base address.
433 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
437 hex "Framebuffer Base Address"
441 Epson SED1355/S1D13505 LCD/CRT controller memory base address. See
443 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
447 tristate "nVidia Riva support"
450 This driver supports graphics boards with the nVidia Riva/Geforce
452 Say Y if you have such a graphics board.
454 To compile this driver as a module, choose M here: the
455 module will be called rivafb.
458 tristate "Intel 810/815 support (EXPERIMENTAL)"
459 depends on FB && AGP && AGP_INTEL && EXPERIMENTAL && PCI
461 This driver supports the on-board graphics built in to the Intel 810
462 and 815 chipsets. Say Y if you have and plan to use such a board.
464 To compile this driver as a module, choose M here: the
465 module will be called i810fb.
467 For more information, please read
468 <file:Documentation/fb/intel810.txt>
471 bool "use VESA Generalized Timing Formula"
474 If you say Y, then the VESA standard, Generalized Timing Formula
475 or GTF, will be used to calculate the required video timing values
476 per video mode. Since the GTF allows nondiscrete timings
477 (nondiscrete being a range of values as opposed to discrete being a
478 set of values), you'll be able to use any combination of horizontal
479 and vertical resolutions, and vertical refresh rates without having
480 to specify your own timing parameters. This is especially useful
481 to maximize the performance of an aging display, or if you just
482 have a display with nonstandard dimensions. A VESA compliant
483 monitor is recommended, but can still work with non-compliant ones.
484 If you need or want this, then select this option. The timings may
485 not be compliant with Intel's recommended values. Use at your own
488 If you say N, the driver will revert to discrete video timings
489 using a set recommended by Intel in their documentation.
494 tristate "Matrox acceleration"
497 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
498 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
499 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
500 Matrox G400, G450 or G550 card in your box.
502 To compile this driver as a module, choose M here: the
503 module will be called matroxfb.
505 You can pass several parameters to the driver at boot time or at
506 module load time. The parameters look like "video=matrox:XXX", and
507 are described in <file:Documentation/fb/matroxfb.txt>.
509 config FB_MATROX_MILLENIUM
510 bool "Millennium I/II support"
513 Say Y here if you have a Matrox Millennium or Matrox Millennium II
514 video card. If you select "Advanced lowlevel driver options" below,
515 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
516 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
517 also use font widths different from 8.
519 config FB_MATROX_MYSTIQUE
520 bool "Mystique support"
523 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
524 video card. If you select "Advanced lowlevel driver options" below,
525 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
526 packed pixel and 32 bpp packed pixel. You can also use font widths
529 config FB_MATROX_G450
530 bool "G100/G200/G400/G450/G550 support"
533 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
534 video card. If you select "Advanced lowlevel driver options", you
535 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
536 pixel and 32 bpp packed pixel. You can also use font widths
539 If you need support for G400 secondary head, you must first say Y to
540 "I2C support" and "I2C bit-banging support" in the character devices
541 section, and then to "Matrox I2C support" and "G400 second head
542 support" here in the framebuffer section. G450/G550 secondary head
543 and digital output are supported without additional modules.
545 The driver starts in monitor mode. You must use the matroxset tool
546 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
547 swap primary and secondary head outputs, or to change output mode.
548 Secondary head driver always start in 640x480 resolution and you
549 must use fbset to change it.
551 Do not forget that second head supports only 16 and 32 bpp
552 packed pixels, so it is a good idea to compile them into the kernel
553 too. You can use only some font widths, as the driver uses generic
554 painting procedures (the secondary head does not use acceleration
557 G450/G550 hardware can display TV picture only from secondary CRTC,
558 and it performs no scaling, so picture must have 525 or 625 lines.
560 config FB_MATROX_G100A
561 bool "G100/G200/G400 support"
562 depends on FB_MATROX && !FB_MATROX_G450
564 Say Y here if you have a Matrox G100, G200 or G400 based
565 video card. If you select "Advanced lowlevel driver options", you
566 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
567 pixel and 32 bpp packed pixel. You can also use font widths
570 If you need support for G400 secondary head, you must first say Y to
571 "I2C support" and "I2C bit-banging support" in the character devices
572 section, and then to "Matrox I2C support" and "G400 second head
573 support" here in the framebuffer section.
575 config FB_MATROX_G100
577 depends on FB_MATROX && (FB_MATROX_G450 || FB_MATROX_G100A)
581 tristate "Matrox I2C support"
582 depends on FB_MATROX && I2C_ALGOBIT
584 This drivers creates I2C buses which are needed for accessing the
585 DDC (I2C) bus present on all Matroxes, an I2C bus which
586 interconnects Matrox optional devices, like MGA-TVO on G200 and
587 G400, and the secondary head DDC bus, present on G400 only.
589 You can say Y or M here if you want to experiment with monitor
590 detection code. You must say Y or M here if you want to use either
591 second head of G400 or MGA-TVO on G200 or G400.
593 If you compile it as module, it will create a module named
596 config FB_MATROX_MAVEN
597 tristate "G400 second head support"
598 depends on FB_MATROX_G100 && FB_MATROX_I2C
600 WARNING !!! This support does not work with G450 !!!
602 Say Y or M here if you want to use a secondary head (meaning two
603 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
604 head is not compatible with accelerated XFree 3.3.x SVGA servers -
605 secondary head output is blanked while you are in X. With XFree
606 3.9.17 preview you can use both heads if you use SVGA over fbdev or
607 the fbdev driver on first head and the fbdev driver on second head.
609 If you compile it as module, two modules are created,
610 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
611 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
612 also load i2c-matroxfb to get it to run.
614 The driver starts in monitor mode and you must use the matroxset
616 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
617 PAL or NTSC or to swap primary and secondary head outputs.
618 Secondary head driver also always start in 640x480 resolution, you
619 must use fbset to change it.
621 Also do not forget that second head supports only 16 and 32 bpp
622 packed pixels, so it is a good idea to compile them into the kernel
623 too. You can use only some font widths, as the driver uses generic
624 painting procedures (the secondary head does not use acceleration
627 config FB_MATROX_MULTIHEAD
628 bool "Multihead support"
631 Say Y here if you have more than one (supported) Matrox device in
632 your computer and you want to use all of them for different monitors
633 ("multihead"). If you have only one device, you should say N because
634 the driver compiled with Y is larger and a bit slower, especially on
637 If you said M to "Matrox unified accelerated driver" and N here, you
638 will still be able to use several Matrox devices simultaneously:
639 insert several instances of the module matroxfb into the kernel
640 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
641 for the different Matrox devices. This method is slightly faster but
642 uses 40 KB of kernel memory per Matrox card.
644 There is no need for enabling 'Matrox multihead support' if you have
645 only one Matrox card in the box.
648 tristate "ATI Radeon display support"
651 Choose this option if you want to use an ATI Radeon graphics card as
652 a framebuffer device. There are both PCI and AGP versions. You
653 don't need to choose this to run the Radeon in plain VGA mode.
654 There is a product page at
655 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
658 tristate "ATI Rage128 display support"
661 This driver supports graphics boards with the ATI Rage128 chips.
662 Say Y if you have such a graphics board and read
663 <file:Documentation/fb/aty128fb.txt>.
665 To compile this driver as a module, choose M here: the
666 module will be called aty128fb.
669 tristate "ATI Mach64 display support" if PCI || ATARI
672 This driver supports graphics boards with the ATI Mach64 chips.
673 Say Y if you have such a graphics board.
675 To compile this driver as a module, choose M here: the
676 module will be called atyfb.
679 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
680 depends on PCI && FB_ATY
681 default y if SPARC64 && FB_PCI
683 Say Y here to support use of ATI's 64-bit Rage boards (or other
684 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
685 framebuffer device. The ATI product support page for these boards
686 is at <http://support.ati.com/products/pc/mach64/>.
689 bool "Mach64 GX support" if PCI
693 Say Y here to support use of the ATI Mach64 Graphics Expression
694 board (or other boards based on the Mach64 GX chipset) as a
695 framebuffer device. The ATI product support page for these boards
697 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
699 config FB_ATY_XL_INIT
700 bool " Rage XL No-BIOS Init support" if FB_ATY_CT
703 Say Y here to support booting a Rage XL without BIOS support.
706 tristate "SIS acceleration"
709 This is the frame buffer device driver for the SiS 630 and 640 Super
710 Socket 7 UMA cards. Specs available at <http://www.sis.com.tw/>.
713 bool "SIS 630/540/730 support"
716 This is the frame buffer device driver for the SiS 630 and related
717 Super Socket 7 UMA cards. Specs available at
718 <http://www.sis.com.tw/>.
721 bool "SIS 315H/315 support"
724 This is the frame buffer device driver for the SiS 315 graphics
725 card. Specs available at <http://www.sis.com.tw/>.
728 tristate "NeoMagic display support"
731 This driver supports notebooks with NeoMagic PCI chips.
732 Say Y if you have such a graphics card.
734 To compile this driver as a module, choose M here: the
735 module will be called neofb.
738 tristate "3Dfx Banshee/Voodoo3 display support"
741 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
742 chips. Say Y if you have such a graphics board.
744 To compile this driver as a module, choose M here: the
745 module will be called tdfxfb.
748 tristate "3Dfx Voodoo Graphics (sst1) support"
751 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
752 Voodoo2 (cvg) based graphics card.
754 To compile this driver as a module, choose M here: the
755 module will be called sstfb.
757 WARNING: Do not use any application that uses the 3D engine
758 (namely glide) while using this driver.
759 Please read the file Documentation/fb/README-sstfb.txt for supported
760 options and other important info support.
763 tristate "Trident support"
766 This driver is supposed to support graphics boards with the
767 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
768 but also on some motherboards. For more information, read
769 <file:Documentation/fb/tridentfb.txt>
771 Say Y if you have such a graphics board.
773 To compile this driver as a module, choose M here: the
774 module will be called tridentfb.
777 tristate "Permedia3 support"
778 depends on FB && PCI && BROKEN
780 This is the frame buffer device driver for the 3DLabs Permedia3
781 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
782 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
783 and maybe other boards.
786 bool "SBUS and UPA framebuffers"
787 depends on FB && (SPARC32 || SPARC64)
789 Say Y if you want support for SBUS or UPA based frame buffer device.
792 bool "Creator/Creator3D/Elite3D support"
793 depends on FB_SBUS && SPARC64
795 This is the frame buffer device driver for the Creator, Creator3D,
796 and Elite3D graphics boards.
799 bool "TCX (SS4/SS5 only) support"
802 This is the frame buffer device driver for the TCX 24/8bit frame
806 bool "CGfourteen (SX) support"
809 This is the frame buffer device driver for the CGfourteen frame
810 buffer on Desktop SPARCsystems with the SX graphics option.
813 bool "P9100 (Sparcbook 3 only) support"
816 This is the frame buffer device driver for the P9100 card
817 supported on Sparcbook 3 machines.
820 bool "Leo (ZX) support"
823 This is the frame buffer device driver for the SBUS-based Sun ZX
824 (leo) frame buffer cards.
827 bool "PCI framebuffers"
828 depends on FB && PCI && (SPARC64 || SPARC32)
831 bool "IGA 168x display support"
832 depends on SPARC32 && FB_PCI
834 This is the framebuffer device for the INTERGRAPHICS 1680 and
835 successor frame buffer cards.
838 tristate "HD64461 Frame Buffer support"
839 depends on FB && HD64461
841 This is the frame buffer device driver for the Hitachi HD64461 LCD
845 bool "PMAG-BA TURBOchannel framebuffer support"
846 depends on FB && DECSTATION && TC
848 Say Y here to directly support the on-board PMAG-BA framebuffer in
849 the 5000/1xx versions of the DECstation. There is a page dedicated
850 to Linux on DECstations at <http://decstation.unix-ag.org/>.
853 bool "PMAGB-B TURBOchannel framebuffer spport"
854 depends on FB && DECSTATION && TC
856 Say Y here to directly support the on-board PMAGB-B framebuffer in
857 the 5000/1xx versions of the DECstation. There is a page dedicated
858 to Linux on DECstations at <http://decstation.unix-ag.org/>.
861 bool "Maxine (Personal DECstation) onboard framebuffer spport"
862 depends on FB && DECSTATION && TC
864 Say Y here to directly support the on-board framebuffer in the
865 Maxine (5000/20, /25, /33) version of the DECstation. There is a
866 page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
869 bool "TMPTX3912/PR31700 frame buffer support"
870 depends on FB && NINO
872 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
873 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
875 Say Y here to enable kernel support for the on-board framebuffer.
878 bool "Motorola 68328 native frame buffer support"
879 depends on (M68328 || M68EZ328 || M68VZ328)
881 Say Y here if you want to support the built-in frame buffer of
882 the Motorola 68328 CPU family.
885 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
888 This is a `virtual' frame buffer device. It operates on a chunk of
889 unswappable kernel memory instead of on the memory of a graphics
890 board. This means you cannot see any output sent to this frame
891 buffer device, while it does consume precious memory. The main use
892 of this frame buffer device is testing and debugging the frame
893 buffer subsystem. Do NOT enable it for normal systems! To protect
894 the innocent, it has to be enabled explicitly at boot time using the
895 kernel option `video=vfb:'.
897 To compile this driver as a module, choose M here: the
898 module will be called vfb.
902 source "drivers/video/console/Kconfig"
905 if FB || SGI_NEWPORT_CONSOLE
906 source "drivers/video/logo/Kconfig"