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.
41 config FB_MODE_HELPERS
42 bool "Enable Video Mode Handling Helpers"
46 This enables functions for handling video modes using the
47 Generalized Timing Formula and the EDID parser. A few drivers rely
48 on this feature such as the radeonfb, rivafb, and the i810fb. If
49 your driver does not take advantage of this feature, choosing Y will
50 just increase the kernel size by about 5K.
52 config FB_TILEBLITTING
53 bool "Enable Tile Blitting Support"
57 This enables tile blitting. Tile blitting is a drawing technique
58 where the screen is divided into rectangular sections (tiles), whereas
59 the standard blitting divides the screen into pixels. Because the
60 default drawing element is a tile, drawing functions will be passed
61 parameters in terms of number of tiles instead of number of pixels.
62 For example, to draw a single character, instead of using bitmaps,
63 an index to an array of bitmaps will be used. To clear or move a
64 rectangular section of a screen, the rectangle will be described in
65 terms of number of tiles in the x- and y-axis.
67 This is particularly important to one driver, matroxfb. If
71 tristate "Cirrus Logic support"
72 depends on FB && (ZORRO || PCI)
74 This enables support for Cirrus Logic GD542x/543x based boards on
75 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
77 If you have a PCI-based system, this enables support for these
78 chips: GD-543x, GD-544x, GD-5480.
80 Please read the file <file:Documentation/fb/cirrusfb.txt>.
82 Say N unless you have such a graphics board or plan to get one
83 before you next recompile the kernel.
86 tristate "Permedia2 support"
87 depends on FB && ((AMIGA && BROKEN) || PCI)
89 This is the frame buffer device driver for the Permedia2 AGP frame
90 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
92 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
94 config FB_PM2_FIFO_DISCONNECT
95 bool "enable FIFO disconnect feature"
96 depends on FB_PM2 && PCI
98 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
101 tristate "ARM PrimeCell PL110 support"
102 depends on FB && ARM && ARM_AMBA
104 This framebuffer device driver is for the ARM PrimeCell PL110
105 Colour LCD controller. ARM PrimeCells provide the building
106 blocks for System on a Chip devices.
108 If you want to compile this as a module (=code which can be
109 inserted into and removed from the running kernel), say M
110 here and read <file:Documentation/modules.txt>. The module
111 will be called amba-clcd.
114 bool "Acorn VIDC support"
115 depends on FB && ARM && ARCH_ACORN
117 This is the frame buffer device driver for the Acorn VIDC graphics
118 hardware found in Acorn RISC PCs and other ARM-based machines. If
122 bool "CLPS711X LCD support"
123 depends on FB && ARM && ARCH_CLPS711X
126 bool "SA-1100 LCD support"
127 depends on FB && ARM && ARCH_SA1100
129 This is a framebuffer device for the SA-1100 LCD Controller.
130 See <http://www.linux-fbdev.org/> for information on framebuffer
133 If you plan to use the LCD display with your SA-1100 system, say
137 tristate "CyberPro 2000/2010/5000 support"
138 depends on FB && PCI && (BROKEN || !SPARC64)
140 This enables support for the Integraphics CyberPro 20x0 and 5000
141 VGA chips used in the Rebel.com Netwinder and other machines.
142 Say Y if you have a NetWinder or a graphics card containing this
143 device, otherwise say N.
147 depends on FB && APOLLO
156 tristate "Amiga native chipset support"
157 depends on FB && AMIGA
159 This is the frame buffer device driver for the builtin graphics
160 chipset found in Amigas.
162 To compile this driver as a module, choose M here: the
163 module will be called amifb.
166 bool "Amiga OCS chipset support"
169 This enables support for the original Agnus and Denise video chips,
170 found in the Amiga 1000 and most A500's and A2000's. If you intend
171 to run Linux on any of these systems, say Y; otherwise say N.
174 bool "Amiga ECS chipset support"
177 This enables support for the Enhanced Chip Set, found in later
178 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
179 you intend to run Linux on any of these systems, say Y; otherwise
183 bool "Amiga AGA chipset support"
186 This enables support for the Advanced Graphics Architecture (also
187 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
188 and CD32. If you intend to run Linux on any of these systems, say Y;
192 tristate "Amiga CyberVision 64 support"
193 depends on FB && ZORRO && BROKEN
195 This enables support for the Cybervision 64 graphics card from
196 Phase5. Please note that its use is not all that intuitive (i.e. if
197 you have any questions, be sure to ask!). Say N unless you have a
198 Cybervision 64 or plan to get one before you next recompile the
199 kernel. Please note that this driver DOES NOT support the
200 Cybervision 64/3D card, as they use incompatible video chips.
203 bool "Amiga CyberVision 64/3D support "
204 depends on FB && ZORRO && BROKEN
206 This enables support for the Cybervision 64/3D graphics card from
207 Phase5. Please note that its use is not all that intuitive (i.e. if
208 you have any questions, be sure to ask!). Say N unless you have a
209 Cybervision 64/3D or plan to get one before you next recompile the
210 kernel. Please note that this driver DOES NOT support the older
211 Cybervision 64 card, as they use incompatible video chips.
214 tristate "Amiga Retina Z3 support"
215 depends on FB && ZORRO && BROKEN
217 This enables support for the Retina Z3 graphics card. Say N unless
218 you have a Retina Z3 or plan to get one before you next recompile
222 bool "Amiga FrameMaster II/Rainbow II support"
223 depends on FB && ZORRO
225 This is the frame buffer device driver for the Amiga FrameMaster
226 card from BSC (exhibited 1992 but not shipped as a CBM product).
229 bool "Atari native chipset support"
230 depends on FB && ATARI && BROKEN
232 This is the frame buffer device driver for the builtin graphics
233 chipset found in Ataris.
236 bool "Open Firmware frame buffer device support"
237 depends on FB && (PPC64 || PPC_OF)
239 Say Y if you want support with Open Firmware for your graphics
243 bool "Apple \"control\" display support"
244 depends on FB && PPC_PMAC
246 This driver supports a frame buffer for the graphics adapter in the
247 Power Macintosh 7300 and others.
250 bool "Apple \"platinum\" display support"
251 depends on FB && PPC_PMAC
253 This driver supports a frame buffer for the "platinum" graphics
254 adapter in some Power Macintoshes.
257 bool "Apple \"valkyrie\" display support"
258 depends on FB && (MAC || PPC_PMAC)
260 This driver supports a frame buffer for the "valkyrie" graphics
261 adapter in some Power Macintoshes.
264 bool "Chips 65550 display support"
267 This is the frame buffer device driver for the Chips & Technologies
268 65550 graphics chip in PowerBooks.
271 bool "Chips 69000 display support"
275 bool "IMS Twin Turbo display support"
278 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
279 many Macintosh and compatible computers.
282 bool "S3 Trio display support"
283 depends on FB && PPC && BROKEN
285 If you have a S3 Trio say Y. Say N for S3 Virge.
288 tristate "VGA 16-color graphics support"
289 depends on FB && (X86 || PPC)
291 This is the frame buffer device driver for VGA 16 color graphic
292 cards. Say Y if you have such a card.
294 To compile this driver as a module, choose M here: the
295 module will be called vga16fb.
298 tristate "HP STI frame buffer device support"
299 depends on FB && PARISC
302 STI refers to the HP "Standard Text Interface" which is a set of
303 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
304 Enabling this option will implement the linux framebuffer device
305 using calls to the STI BIOS routines for initialisation.
307 If you enable this option, you will get a planar framebuffer device
308 /dev/fb which will work on the most common HP graphic cards of the
309 NGLE family, including the artist chips (in the 7xx and Bxxx series),
310 HCRX, HCRX24, CRX, CRX24 and VisEG series.
312 It is safe to enable this option, so you should probably say "Y".
315 bool "Generic Macintosh display support"
318 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
321 depends on FB && HP300
325 tristate "TGA framebuffer support"
326 depends on FB && ALPHA
328 This is the frame buffer device driver for generic TGA graphic
329 cards. Say Y if you have one of those.
332 bool "VESA VGA graphics support"
333 depends on FB && (X86 || X86_64)
335 This is the frame buffer device driver for generic VESA 2.0
336 compliant graphic cards. The older VESA 1.2 cards are not supported.
337 You will get a boot time penguin logo at no additional cost. Please
338 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
346 tristate "Hercules mono graphics support"
349 Say Y here if you have a Hercules mono graphics card.
351 To compile this driver as a module, choose M here: the
352 module will be called hgafb.
354 As this card technology is 15 years old, most people will answer N
358 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
359 depends on FB_HGA && EXPERIMENTAL
361 This will compile the Hercules mono graphics with
362 acceleration functions.
371 tristate "SGI Visual Workstation framebuffer support"
372 depends on FB && X86_VISWS
374 SGI Visual Workstation support for framebuffer graphics.
377 bool "SGI Graphics Backend frame buffer support"
378 depends on FB && (SGI_IP32 || X86_VISWS)
380 This is the frame buffer device driver for SGI Graphics Backend.
381 This chip is used in SGI O2 and Visual Workstation 320/540.
384 int "Video memory size in MB"
388 This is the amount of memory reserved for the framebuffer,
389 which can be any value between 1MB and 8MB.
393 depends on FB && VISWS
397 bool "Sun3 framebuffer support"
398 depends on FB && (SUN3 || SUN3X) && BROKEN
402 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
404 This is the frame buffer device driver for the BWtwo frame buffer.
407 bool "CGthree support"
408 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
410 This is the frame buffer device driver for the CGthree frame buffer.
413 bool "CGsix (GX,TurboGX) support"
414 depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
416 This is the frame buffer device driver for the CGsix (GX, TurboGX)
420 tristate "NEC PowerVR 2 display support"
421 depends on FB && SH_DREAMCAST
423 Say Y here if you have a PowerVR 2 card in your box. If you plan to
424 run linux on your Dreamcast, you will have to say Y here.
425 This driver may or may not work on other PowerVR 2 cards, but is
426 totally untested. Use at your own risk. If unsure, say N.
428 To compile this driver as a module, choose M here: the
429 module will be called pvr2fb.
431 You can pass several parameters to the driver at boot time or at
432 module load time. The parameters look like "video=pvr2:XXX", where
433 the meaning of XXX can be found at the end of the main source file
434 (<file:drivers/video/pvr2fb.c>). Please see the file
435 <file:Documentation/fb/pvr2fb.txt>.
438 bool "Epson 1355 framebuffer support"
439 depends on FB && (SUPERH || ARCH_CEIVA)
441 Build in support for the SED1355 Epson Research Embedded RAMDAC
442 LCD/CRT Controller (since redesignated as the S1D13505) as a
443 framebuffer. Product specs at
444 <http://www.erd.epson.com/vdc/html/products.htm>.
447 tristate "nVidia Riva support"
449 select I2C_ALGOBIT if FB_RIVA_I2C
450 select I2C if FB_RIVA_I2C
451 select FB_MODE_HELPERS
453 This driver supports graphics boards with the nVidia Riva/Geforce
455 Say Y if you have such a graphics board.
457 To compile this driver as a module, choose M here: the
458 module will be called rivafb.
461 bool "Enable DDC Support"
464 This enables I2C support for nVidia Chipsets. This is used
465 only for getting EDID information from the attached display
466 allowing for robust video mode handling and switching.
468 Because fbdev-2.6 requires that drivers must be able to
469 independently validate video mode parameters, you should say Y
473 bool "Lots of debug output from Riva(nVidia) driver"
477 Say Y here if you want the Riva driver to output all sorts
478 of debugging informations to provide to the maintainer when
479 something goes wrong.
482 tristate "Intel 810/815 support (EXPERIMENTAL)"
483 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
486 select FB_MODE_HELPERS
488 This driver supports the on-board graphics built in to the Intel 810
489 and 815 chipsets. Say Y if you have and plan to use such a board.
491 To compile this driver as a module, choose M here: the
492 module will be called i810fb.
494 For more information, please read
495 <file:Documentation/fb/intel810.txt>
498 bool "use VESA Generalized Timing Formula"
501 If you say Y, then the VESA standard, Generalized Timing Formula
502 or GTF, will be used to calculate the required video timing values
503 per video mode. Since the GTF allows nondiscrete timings
504 (nondiscrete being a range of values as opposed to discrete being a
505 set of values), you'll be able to use any combination of horizontal
506 and vertical resolutions, and vertical refresh rates without having
507 to specify your own timing parameters. This is especially useful
508 to maximize the performance of an aging display, or if you just
509 have a display with nonstandard dimensions. A VESA compliant
510 monitor is recommended, but can still work with non-compliant ones.
511 If you need or want this, then select this option. The timings may
512 not be compliant with Intel's recommended values. Use at your own
515 If you say N, the driver will revert to discrete video timings
516 using a set recommended by Intel in their documentation.
521 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
522 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
526 This driver supports the on-board graphics built in to the Intel
527 830M/845G/852GM/855GM/865G chipsets.
528 Say Y if you have and plan to use such a board.
530 To compile this driver as a module, choose M here: the
531 module will be called intelfb.
533 config FB_INTEL_DEBUG
534 bool "Intel driver Debug Messages"
537 Say Y here if you want the Intel driver to output all sorts
538 of debugging informations to provide to the maintainer when
539 something goes wrong.
542 tristate "Matrox acceleration"
545 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
546 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
547 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
548 Matrox G400, G450 or G550 card in your box.
550 To compile this driver as a module, choose M here: the
551 module will be called matroxfb.
553 You can pass several parameters to the driver at boot time or at
554 module load time. The parameters look like "video=matrox:XXX", and
555 are described in <file:Documentation/fb/matroxfb.txt>.
557 config FB_MATROX_MILLENIUM
558 bool "Millennium I/II support"
561 Say Y here if you have a Matrox Millennium or Matrox Millennium II
562 video card. If you select "Advanced lowlevel driver options" below,
563 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
564 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
565 also use font widths different from 8.
567 config FB_MATROX_MYSTIQUE
568 bool "Mystique support"
571 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
572 video card. If you select "Advanced lowlevel driver options" below,
573 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
574 packed pixel and 32 bpp packed pixel. You can also use font widths
578 bool "G100/G200/G400/G450/G550 support"
581 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
582 video card. If you select "Advanced lowlevel driver options", you
583 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
584 pixel and 32 bpp packed pixel. You can also use font widths
587 If you need support for G400 secondary head, you must first say Y to
588 "I2C support" in the character devices section, and then to
589 "Matrox I2C support" and "G400 second head support" here in the
590 framebuffer section. G450/G550 secondary head and digital output
591 are supported without additional modules.
593 The driver starts in monitor mode. You must use the matroxset tool
594 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
595 swap primary and secondary head outputs, or to change output mode.
596 Secondary head driver always start in 640x480 resolution and you
597 must use fbset to change it.
599 Do not forget that second head supports only 16 and 32 bpp
600 packed pixels, so it is a good idea to compile them into the kernel
601 too. You can use only some font widths, as the driver uses generic
602 painting procedures (the secondary head does not use acceleration
605 G450/G550 hardware can display TV picture only from secondary CRTC,
606 and it performs no scaling, so picture must have 525 or 625 lines.
609 tristate "Matrox I2C support"
610 depends on FB_MATROX && I2C
613 This drivers creates I2C buses which are needed for accessing the
614 DDC (I2C) bus present on all Matroxes, an I2C bus which
615 interconnects Matrox optional devices, like MGA-TVO on G200 and
616 G400, and the secondary head DDC bus, present on G400 only.
618 You can say Y or M here if you want to experiment with monitor
619 detection code. You must say Y or M here if you want to use either
620 second head of G400 or MGA-TVO on G200 or G400.
622 If you compile it as module, it will create a module named
625 config FB_MATROX_MAVEN
626 tristate "G400 second head support"
627 depends on FB_MATROX_G && FB_MATROX_I2C
629 WARNING !!! This support does not work with G450 !!!
631 Say Y or M here if you want to use a secondary head (meaning two
632 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
633 head is not compatible with accelerated XFree 3.3.x SVGA servers -
634 secondary head output is blanked while you are in X. With XFree
635 3.9.17 preview you can use both heads if you use SVGA over fbdev or
636 the fbdev driver on first head and the fbdev driver on second head.
638 If you compile it as module, two modules are created,
639 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
640 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
641 also load i2c-matroxfb to get it to run.
643 The driver starts in monitor mode and you must use the matroxset
645 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
646 PAL or NTSC or to swap primary and secondary head outputs.
647 Secondary head driver also always start in 640x480 resolution, you
648 must use fbset to change it.
650 Also do not forget that second head supports only 16 and 32 bpp
651 packed pixels, so it is a good idea to compile them into the kernel
652 too. You can use only some font widths, as the driver uses generic
653 painting procedures (the secondary head does not use acceleration
656 config FB_MATROX_MULTIHEAD
657 bool "Multihead support"
660 Say Y here if you have more than one (supported) Matrox device in
661 your computer and you want to use all of them for different monitors
662 ("multihead"). If you have only one device, you should say N because
663 the driver compiled with Y is larger and a bit slower, especially on
666 If you said M to "Matrox unified accelerated driver" and N here, you
667 will still be able to use several Matrox devices simultaneously:
668 insert several instances of the module matroxfb into the kernel
669 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
670 for the different Matrox devices. This method is slightly faster but
671 uses 40 KB of kernel memory per Matrox card.
673 There is no need for enabling 'Matrox multihead support' if you have
674 only one Matrox card in the box.
677 tristate "ATI Radeon display support (Old driver)"
680 Choose this option if you want to use an ATI Radeon graphics card as
681 a framebuffer device. There are both PCI and AGP versions. You
682 don't need to choose this to run the Radeon in plain VGA mode.
683 There is a product page at
684 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
687 tristate "ATI Radeon display support"
689 select I2C_ALGOBIT if FB_RADEON_I2C
690 select I2C if FB_RADEON_I2C
691 select FB_MODE_HELPERS
693 Choose this option if you want to use an ATI Radeon graphics card as
694 a framebuffer device. There are both PCI and AGP versions. You
695 don't need to choose this to run the Radeon in plain VGA mode.
697 If you say Y here and want DDC/I2C support you must first say Y to
698 "I2C support" and "I2C bit-banging support" in the character devices
701 If you say M here then "I2C support" and "I2C bit-banging support"
702 can be build either as modules or built-in.
704 There is a product page at
705 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
708 bool "DDC/I2C for ATI Radeon support"
712 Say Y here if you want DDC/I2C support for your Radeon board.
714 config FB_RADEON_DEBUG
715 bool "Lots of debug output from Radeon driver"
719 Say Y here if you want the Radeon driver to output all sorts
720 of debugging informations to provide to the maintainer when
721 something goes wrong.
724 tristate "ATI Rage128 display support"
727 This driver supports graphics boards with the ATI Rage128 chips.
728 Say Y if you have such a graphics board and read
729 <file:Documentation/fb/aty128fb.txt>.
731 To compile this driver as a module, choose M here: the
732 module will be called aty128fb.
735 tristate "ATI Mach64 display support" if PCI || ATARI
738 This driver supports graphics boards with the ATI Mach64 chips.
739 Say Y if you have such a graphics board.
741 To compile this driver as a module, choose M here: the
742 module will be called atyfb.
745 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
746 depends on PCI && FB_ATY
747 default y if SPARC64 && FB_PCI
749 Say Y here to support use of ATI's 64-bit Rage boards (or other
750 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
751 framebuffer device. The ATI product support page for these boards
752 is at <http://support.ati.com/products/pc/mach64/>.
754 config FB_ATY_GENERIC_LCD
755 bool "Mach64 generic LCD support (EXPERIMENTAL)"
758 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
759 Rage XC, or Rage XL chipset.
761 config FB_ATY_XL_INIT
762 bool "Rage XL No-BIOS Init support"
765 Say Y here to support booting a Rage XL without BIOS support.
768 bool "Mach64 GX support" if PCI
772 Say Y here to support use of the ATI Mach64 Graphics Expression
773 board (or other boards based on the Mach64 GX chipset) as a
774 framebuffer device. The ATI product support page for these boards
776 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
779 tristate "S3 Savage support"
780 depends on FB && PCI && EXPERIMENTAL
781 select I2C_ALGOBIT if FB_SAVAGE_I2C
782 select I2C if FB_SAVAGE_I2C
783 select FB_MODE_HELPERS
785 This driver supports notebooks and computers with S3 Savage PCI/AGP
788 Say Y if you have such a graphics card.
790 To compile this driver as a module, choose M here; the module
791 will be called savagefb.
794 tristate "Enable DDC2 Support"
797 This enables I2C support for S3 Savage Chipsets. This is used
798 only for getting EDID information from the attached display
799 allowing for robust video mode handling and switching.
801 Because fbdev-2.6 requires that drivers must be able to
802 independently validate video mode parameters, you should say Y
805 config FB_SAVAGE_ACCEL
806 tristate "Enable Console Acceleration"
810 This option will compile in console acceleration support. If
811 the resulting framebuffer console has bothersome glitches, then
815 tristate "SiS acceleration"
818 This is the frame buffer device driver for the SiS 300, 315 and
819 330 series VGA chipsets. Specs available at <http://www.sis.com>
821 To compile this driver as a module, choose M here; the module
822 will be called sisfb.
825 bool "SiS 300 series support"
828 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
831 bool "SiS 315/330 series support"
834 Say Y here to support use of the SiS 315 and 330 series
835 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760).
838 tristate "NeoMagic display support"
840 select FB_MODE_HELPERS
842 This driver supports notebooks with NeoMagic PCI chips.
843 Say Y if you have such a graphics card.
845 To compile this driver as a module, choose M here: the
846 module will be called neofb.
849 tristate "IMG Kyro support"
852 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
855 To compile this driver as a module, choose M here: the
856 module will be called kyrofb.
859 tristate "3Dfx Banshee/Voodoo3 display support"
862 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
863 chips. Say Y if you have such a graphics board.
865 To compile this driver as a module, choose M here: the
866 module will be called tdfxfb.
869 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
870 depends on FB_3DFX && EXPERIMENTAL
872 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
873 with acceleration functions.
877 tristate "3Dfx Voodoo Graphics (sst1) support"
880 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
881 Voodoo2 (cvg) based graphics card.
883 To compile this driver as a module, choose M here: the
884 module will be called sstfb.
886 WARNING: Do not use any application that uses the 3D engine
887 (namely glide) while using this driver.
888 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
889 options and other important info support.
892 tristate "Trident support"
895 This driver is supposed to support graphics boards with the
896 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
897 but also on some motherboards. For more information, read
898 <file:Documentation/fb/tridentfb.txt>
900 Say Y if you have such a graphics board.
902 To compile this driver as a module, choose M here: the
903 module will be called tridentfb.
905 config FB_TRIDENT_ACCEL
906 bool "Trident Acceleration functions (EXPERIMENTAL)"
907 depends on FB_TRIDENT && EXPERIMENTAL
909 This will compile the Trident frame buffer device with
910 acceleration functions.
914 tristate "Permedia3 support"
915 depends on FB && PCI && BROKEN
917 This is the frame buffer device driver for the 3DLabs Permedia3
918 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
919 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
920 and maybe other boards.
923 tristate "Epson SED1356 framebuffer support"
924 depends on FB && EXPERIMENTAL && PCI && MIPS
927 bool "Use CRT on Pb1000 (J65)"
928 depends on MIPS_PB1000=y && FB_E1356
931 bool "Use Compsite NTSC on Pb1000 (J63)"
932 depends on MIPS_PB1000=y && FB_E1356
935 bool "Use TFT Panel on Pb1000 (J64)"
936 depends on MIPS_PB1000=y && FB_E1356
939 bool "Use CRT on Pb1500 " if MIPS_PB1500=y
943 prompt "Use CRT on Pb1100 "
944 depends on FB_E1356 && MIPS_PB1100=y
947 bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y
951 prompt "Use TFT Panel on Pb1100 "
952 depends on FB_E1356 && MIPS_PB1100=y
955 bool "Au1100 LCD Driver"
956 depends on FB && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
959 bool "SBUS and UPA framebuffers"
960 depends on FB && (SPARC32 || SPARC64)
962 Say Y if you want support for SBUS or UPA based frame buffer device.
965 bool "Creator/Creator3D/Elite3D support"
966 depends on FB_SBUS && SPARC64
968 This is the frame buffer device driver for the Creator, Creator3D,
969 and Elite3D graphics boards.
972 bool "TCX (SS4/SS5 only) support"
975 This is the frame buffer device driver for the TCX 24/8bit frame
979 bool "CGfourteen (SX) support"
982 This is the frame buffer device driver for the CGfourteen frame
983 buffer on Desktop SPARCsystems with the SX graphics option.
986 bool "P9100 (Sparcbook 3 only) support"
989 This is the frame buffer device driver for the P9100 card
990 supported on Sparcbook 3 machines.
993 bool "Leo (ZX) support"
996 This is the frame buffer device driver for the SBUS-based Sun ZX
997 (leo) frame buffer cards.
1000 bool "PCI framebuffers"
1001 depends on FB && PCI && (SPARC64 || SPARC32)
1004 bool "IGA 168x display support"
1005 depends on SPARC32 && FB_PCI
1007 This is the framebuffer device for the INTERGRAPHICS 1680 and
1008 successor frame buffer cards.
1011 tristate "HD64461 Frame Buffer support"
1012 depends on FB && HD64461
1014 This is the frame buffer device driver for the Hitachi HD64461 LCD
1018 bool "PMAG-AA TURBOchannel framebuffer support"
1019 depends on FB && MACH_DECSTATION && TC
1021 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1022 used mainly in the MIPS-based DECstation series.
1025 bool "PMAG-BA TURBOchannel framebuffer support"
1026 depends on FB && MACH_DECSTATION && TC
1028 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1029 used mainly in the MIPS-based DECstation series.
1032 bool "PMAGB-B TURBOchannel framebuffer support"
1033 depends on FB && MACH_DECSTATION && TC
1035 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1036 in the MIPS-based DECstation series. The card is currently only
1037 supported in 1280x1024x8 mode.
1040 bool "Maxine (Personal DECstation) onboard framebuffer support"
1041 depends on FB && MACH_DECSTATION && TC
1043 Support for the onboard framebuffer (1024x768x8) in the Personal
1044 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1048 bool "TMPTX3912/PR31700 frame buffer support"
1049 depends on FB && NINO
1051 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1052 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1054 Say Y here to enable kernel support for the on-board framebuffer.
1058 depends on MIPS_MAGNUM_4000 || OLIVETTI_M700
1060 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1061 Olivetti M700-10 systems.
1064 bool "Motorola 68328 native frame buffer support"
1065 depends on (M68328 || M68EZ328 || M68VZ328)
1067 Say Y here if you want to support the built-in frame buffer of
1068 the Motorola 68328 CPU family.
1071 tristate "PXA LCD framebuffer support"
1072 depends on FB && ARCH_PXA
1074 Frame buffer driver for the built-in LCD controller in the Intel
1077 This driver is also available as a module ( = code which can be
1078 inserted and removed from the running kernel whenever you want). The
1079 module will be called vfb. If you want to compile it as a module,
1080 say M here and read <file:Documentation/modules.txt>.
1085 tristate "W100 frame buffer support"
1086 depends on FB && PXA_SHARPSL
1088 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1090 This driver is also available as a module ( = code which can be
1091 inserted and removed from the running kernel whenever you want). The
1092 module will be called vfb. If you want to compile it as a module,
1093 say M here and read <file:Documentation/modules.txt>.
1097 config FB_PXA_PARAMETERS
1098 bool "PXA LCD command line parameters"
1102 Enable the use of kernel command line or module parameters
1103 to configure the physical properties of the LCD panel when
1104 using the PXA LCD driver.
1106 This option allows you to override the panel parameters
1107 supplied by the platform in order to support multiple
1108 different models of flatpanel. If you will only be using a
1109 single model of flatpanel then you can safely leave this
1112 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1115 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1118 This is a `virtual' frame buffer device. It operates on a chunk of
1119 unswappable kernel memory instead of on the memory of a graphics
1120 board. This means you cannot see any output sent to this frame
1121 buffer device, while it does consume precious memory. The main use
1122 of this frame buffer device is testing and debugging the frame
1123 buffer subsystem. Do NOT enable it for normal systems! To protect
1124 the innocent, it has to be enabled explicitly at boot time using the
1125 kernel option `video=vfb:'.
1127 To compile this driver as a module, choose M here: the
1128 module will be called vfb.
1132 source "drivers/video/console/Kconfig"
1135 if FB || SGI_NEWPORT_CONSOLE
1136 source "drivers/video/logo/Kconfig"
1140 source "drivers/video/backlight/Kconfig"