vserver 1.9.5.x5

[linux-2.6.git] / drivers / video / Kconfig

diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
index ab23abe..eaa557b 100644 (file)
--- a/drivers/video/Kconfig
+++ b/drivers/video/Kconfig
@@ -41,7 +41,7 @@ config FB
 config FB_MODE_HELPERS
         bool "Enable Video Mode Handling Helpers"
         depends on FB
 config FB_MODE_HELPERS
         bool "Enable Video Mode Handling Helpers"
         depends on FB

-       default y
+       default n

        ---help---
          This enables functions for handling video modes using the
          Generalized Timing Formula and the EDID parser. A few drivers rely
        ---help---
          This enables functions for handling video modes using the
          Generalized Timing Formula and the EDID parser. A few drivers rely


@@ -49,6 +49,24 @@ config FB_MODE_HELPERS
          your driver does not take advantage of this feature, choosing Y will
          just increase the kernel size by about 5K.
 
          your driver does not take advantage of this feature, choosing Y will
          just increase the kernel size by about 5K.
 

+config FB_TILEBLITTING
+       bool "Enable Tile Blitting Support"
+       depends on FB
+       default n
+       ---help---
+         This enables tile blitting.  Tile blitting is a drawing technique
+        where the screen is divided into rectangular sections (tiles), whereas
+        the standard blitting divides the screen into pixels. Because the
+        default drawing element is a tile, drawing functions will be passed
+        parameters in terms of number of tiles instead of number of pixels.
+        For example, to draw a single character, instead of using bitmaps,
+        an index to an array of bitmaps will be used.  To clear or move a
+        rectangular section of a screen, the rectangle will be described in
+        terms of number of tiles in the x- and y-axis.
+
+        This is particularly important to one driver, matroxfb.  If
+        unsure, say N.
+

 config FB_CIRRUS
        tristate "Cirrus Logic support"
        depends on FB && (ZORRO || PCI)
 config FB_CIRRUS
        tristate "Cirrus Logic support"
        depends on FB && (ZORRO || PCI)


@@ -499,6 +517,27 @@ config FB_I810_GTF
   
           If unsure, say N.
 
   
           If unsure, say N.
 

+config FB_INTEL
+       tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
+       depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
+       select AGP
+       select AGP_INTEL
+       help
+         This driver supports the on-board graphics built in to the Intel
+          830M/845G/852GM/855GM/865G chipsets.
+          Say Y if you have and plan to use such a board.
+
+          To compile this driver as a module, choose M here: the
+         module will be called intelfb.
+
+config FB_INTEL_DEBUG
+        bool "Intel driver Debug Messages"
+       depends on FB_INTEL
+       ---help---
+         Say Y here if you want the Intel driver to output all sorts
+         of debugging informations to provide to the maintainer when
+         something goes wrong.
+

 config FB_MATROX
        tristate "Matrox acceleration"
        depends on FB && PCI
 config FB_MATROX
        tristate "Matrox acceleration"
        depends on FB && PCI


@@ -535,7 +574,7 @@ config FB_MATROX_MYSTIQUE
          packed pixel and 32 bpp packed pixel. You can also use font widths
          different from 8.
 
          packed pixel and 32 bpp packed pixel. You can also use font widths
          different from 8.
 

-config FB_MATROX_G450
+config FB_MATROX_G

        bool "G100/G200/G400/G450/G550 support"
        depends on FB_MATROX
        ---help---
        bool "G100/G200/G400/G450/G550 support"
        depends on FB_MATROX
        ---help---


@@ -546,10 +585,10 @@ config FB_MATROX_G450
          different from 8.
 
          If you need support for G400 secondary head, you must first say Y to
          different from 8.
 
          If you need support for G400 secondary head, you must first say Y to

-         "I2C support" and "I2C bit-banging support" in the character devices
-         section, and then to "Matrox I2C support" and "G400 second head
-         support" here in the framebuffer section. G450/G550 secondary head
-         and digital output are supported without additional modules.
+         "I2C support" in the character devices section, and then to
+         "Matrox I2C support" and "G400 second head support" here in the
+         framebuffer section. G450/G550 secondary head and digital output
+         are supported without additional modules.

 
          The driver starts in monitor mode. You must use the matroxset tool 
          (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 
 
          The driver starts in monitor mode. You must use the matroxset tool 
          (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 


@@ -566,26 +605,6 @@ config FB_MATROX_G450
          G450/G550 hardware can display TV picture only from secondary CRTC,
          and it performs no scaling, so picture must have 525 or 625 lines.
 
          G450/G550 hardware can display TV picture only from secondary CRTC,
          and it performs no scaling, so picture must have 525 or 625 lines.
 

-config FB_MATROX_G100A
-       bool "G100/G200/G400 support"
-       depends on FB_MATROX && !FB_MATROX_G450
-       ---help---
-         Say Y here if you have a Matrox G100, G200 or G400 based
-         video card. If you select "Advanced lowlevel driver options", you
-         should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
-         pixel and 32 bpp packed pixel. You can also use font widths
-         different from 8.
-
-         If you need support for G400 secondary head, you must first say Y to
-         "I2C support" and "I2C bit-banging support" in the character devices
-         section, and then to "Matrox I2C support" and "G400 second head
-         support" here in the framebuffer section.
-
-config FB_MATROX_G100
-       bool
-       depends on FB_MATROX && (FB_MATROX_G450 || FB_MATROX_G100A)
-       default y
-

 config FB_MATROX_I2C
        tristate "Matrox I2C support"
        depends on FB_MATROX && I2C
 config FB_MATROX_I2C
        tristate "Matrox I2C support"
        depends on FB_MATROX && I2C


@@ -605,7 +624,7 @@ config FB_MATROX_I2C
 
 config FB_MATROX_MAVEN
        tristate "G400 second head support"
 
 config FB_MATROX_MAVEN
        tristate "G400 second head support"

-       depends on FB_MATROX_G100 && FB_MATROX_I2C
+       depends on FB_MATROX_G && FB_MATROX_I2C

        ---help---
          WARNING !!! This support does not work with G450 !!!
 
        ---help---
          WARNING !!! This support does not work with G450 !!!
 


@@ -732,6 +751,19 @@ config FB_ATY_CT
          framebuffer device.  The ATI product support page for these boards
          is at <http://support.ati.com/products/pc/mach64/>.
 
          framebuffer device.  The ATI product support page for these boards
          is at <http://support.ati.com/products/pc/mach64/>.
 

+config FB_ATY_GENERIC_LCD
+       bool "Mach64 generic LCD support (EXPERIMENTAL)"
+       depends on FB_ATY_CT
+       help
+         Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
+         Rage XC, or Rage XL chipset.
+
+config FB_ATY_XL_INIT
+       bool "Rage XL No-BIOS Init support"
+       depends on FB_ATY_CT
+       help
+         Say Y here to support booting a Rage XL without BIOS support.
+

 config FB_ATY_GX
        bool "Mach64 GX support" if PCI
        depends on FB_ATY
 config FB_ATY_GX
        bool "Mach64 GX support" if PCI
        depends on FB_ATY


@@ -743,18 +775,48 @@ config FB_ATY_GX
          is at
          <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
 
          is at
          <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
 

-config FB_ATY_XL_INIT
-       bool "  Rage XL No-BIOS Init support" if FB_ATY_CT
-       depends on FB_ATY
+config FB_SAVAGE
+       tristate "S3 Savage support"
+       depends on FB && PCI && EXPERIMENTAL
+       select I2C_ALGOBIT if FB_SAVAGE_I2C
+       select I2C if FB_SAVAGE_I2C
+       select FB_MODE_HELPERS

        help
        help

-         Say Y here to support booting a Rage XL without BIOS support.
+         This driver supports notebooks and computers with S3 Savage PCI/AGP
+         chips.
+
+         Say Y if you have such a graphics card.
+
+         To compile this driver as a module, choose M here; the module
+         will be called savagefb.
+
+config FB_SAVAGE_I2C
+       tristate "Enable DDC2 Support"
+       depends on FB_SAVAGE
+       help
+         This enables I2C support for S3 Savage Chipsets.  This is used
+         only for getting EDID information from the attached display
+         allowing for robust video mode handling and switching.
+
+         Because fbdev-2.6 requires that drivers must be able to
+         independently validate video mode parameters, you should say Y
+         here.
+
+config FB_SAVAGE_ACCEL
+       tristate "Enable Console Acceleration"
+       depends on FB_SAVAGE
+       default n
+       help
+          This option will compile in console acceleration support. If
+          the resulting framebuffer console has bothersome glitches, then
+          choose N here.

 
 config FB_SIS
        tristate "SiS acceleration"
        depends on FB && PCI
        help
          This is the frame buffer device driver for the SiS 300, 315 and
 
 config FB_SIS
        tristate "SiS acceleration"
        depends on FB && PCI
        help
          This is the frame buffer device driver for the SiS 300, 315 and

-         330 series VGA chipsets. Specs available at http://www.sis.com
+         330 series VGA chipsets. Specs available at <http://www.sis.com>

 
          To compile this driver as a module, choose M here; the module
          will be called sisfb.
 
          To compile this driver as a module, choose M here; the module
          will be called sisfb.


@@ -823,7 +885,7 @@ config FB_VOODOO1
 
          WARNING: Do not use any application that uses the 3D engine
          (namely glide) while using this driver.
 
          WARNING: Do not use any application that uses the 3D engine
          (namely glide) while using this driver.

-         Please read the file Documentation/fb/README-sstfb.txt for supported
+         Please read the <file:Documentation/fb/README-sstfb.txt> for supported

          options and other important info  support.
 
 config FB_TRIDENT
          options and other important info  support.
 
 config FB_TRIDENT


@@ -857,6 +919,42 @@ config FB_PM3
          similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
          and maybe other boards.
 
          similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
          and maybe other boards.
 

+config FB_E1356
+       tristate "Epson SED1356 framebuffer support"
+       depends on FB && EXPERIMENTAL && PCI && MIPS
+
+config PB1000_CRT
+       bool "Use CRT on Pb1000 (J65)"
+       depends on MIPS_PB1000=y && FB_E1356
+
+config PB1000_NTSC
+       bool "Use Compsite NTSC on Pb1000 (J63)"
+       depends on MIPS_PB1000=y && FB_E1356
+
+config PB1000_TFT
+       bool "Use TFT Panel on Pb1000 (J64)"
+       depends on MIPS_PB1000=y && FB_E1356
+
+config PB1500_CRT
+       bool "Use CRT on Pb1500 " if MIPS_PB1500=y
+       depends on FB_E1356
+
+config PB1500_CRT
+       prompt "Use CRT on Pb1100 "
+       depends on FB_E1356 && MIPS_PB1100=y
+
+config PB1500_TFT
+       bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y
+       depends on FB_E1356
+
+config PB1500_TFT
+       prompt "Use TFT Panel on Pb1100 "
+       depends on FB_E1356 && MIPS_PB1100=y
+
+config FB_AU1100
+       bool "Au1100 LCD Driver"
+       depends on FB && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
+

 config FB_SBUS
        bool "SBUS and UPA framebuffers"
        depends on FB && (SPARC32 || SPARC64)
 config FB_SBUS
        bool "SBUS and UPA framebuffers"
        depends on FB && (SPARC32 || SPARC64)


@@ -916,29 +1014,35 @@ config FB_HIT
          This is the frame buffer device driver for the Hitachi HD64461 LCD
          frame buffer card.
 
          This is the frame buffer device driver for the Hitachi HD64461 LCD
          frame buffer card.
 

+config FB_PMAG_AA
+       bool "PMAG-AA TURBOchannel framebuffer support"
+       depends on FB && MACH_DECSTATION && TC
+       help
+         Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
+         used mainly in the MIPS-based DECstation series.
+

 config FB_PMAG_BA
        bool "PMAG-BA TURBOchannel framebuffer support"
 config FB_PMAG_BA
        bool "PMAG-BA TURBOchannel framebuffer support"

-       depends on FB && DECSTATION && TC
+       depends on FB && MACH_DECSTATION && TC

        help
        help

-         Say Y here to directly support the on-board PMAG-BA framebuffer in
-         the 5000/1xx versions of the DECstation.  There is a page dedicated
-         to Linux on DECstations at <http://decstation.unix-ag.org/>.
+         Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
+         used mainly in the MIPS-based DECstation series.

 
 config FB_PMAGB_B
 
 config FB_PMAGB_B

-       bool "PMAGB-B TURBOchannel framebuffer spport"
-       depends on FB && DECSTATION && TC
+       bool "PMAGB-B TURBOchannel framebuffer support"
+       depends on FB && MACH_DECSTATION && TC

        help
        help

-         Say Y here to directly support the on-board PMAGB-B framebuffer in
-         the 5000/1xx versions of the DECstation.  There is a page dedicated
-         to Linux on DECstations at <http://decstation.unix-ag.org/>.
+         Support for the PMAGB-B TURBOchannel framebuffer card used mainly
+         in the MIPS-based DECstation series. The card is currently only
+         supported in 1280x1024x8 mode.

 
 config FB_MAXINE
 
 config FB_MAXINE

-       bool "Maxine (Personal DECstation) onboard framebuffer spport"
-       depends on FB && DECSTATION && TC
+       bool "Maxine (Personal DECstation) onboard framebuffer support"
+       depends on FB && MACH_DECSTATION && TC

        help
        help

-         Say Y here to directly support the on-board framebuffer in the
-         Maxine (5000/20, /25, /33) version of the DECstation.  There is a
-         page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
+         Support for the onboard framebuffer (1024x768x8) in the Personal
+         DECstation series (Personal DECstation 5000/20, /25, /33, /50,
+         Codename "Maxine").

 
 config FB_TX3912
        bool "TMPTX3912/PR31700 frame buffer support"
 
 config FB_TX3912
        bool "TMPTX3912/PR31700 frame buffer support"


@@ -949,6 +1053,13 @@ config FB_TX3912
 
          Say Y here to enable kernel support for the on-board framebuffer.
 
 
          Say Y here to enable kernel support for the on-board framebuffer.
 

+config FB_G364
+       bool
+       depends on MIPS_MAGNUM_4000 || OLIVETTI_M700
+       help
+         The G364 driver is the framebuffer used in MIPS Magnum 4000 and
+         Olivetti M700-10 systems.
+

 config FB_68328
        bool "Motorola 68328 native frame buffer support"
        depends on (M68328 || M68EZ328 || M68VZ328)
 config FB_68328
        bool "Motorola 68328 native frame buffer support"
        depends on (M68328 || M68EZ328 || M68VZ328)


@@ -970,6 +1081,19 @@ config FB_PXA
 
          If unsure, say N.
 
 
          If unsure, say N.
 

+config FB_W100
+       tristate "W100 frame buffer support"
+       depends on FB && PXA_SHARPSL
+       ---help---
+         Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
+
+         This driver is also available as a module ( = code which can be
+         inserted and removed from the running kernel whenever you want). The
+         module will be called vfb. If you want to compile it as a module,
+         say M here and read <file:Documentation/modules.txt>.
+
+         If unsure, say N.
+

 config FB_PXA_PARAMETERS
        bool "PXA LCD command line parameters"
        default n
 config FB_PXA_PARAMETERS
        bool "PXA LCD command line parameters"
        default n


@@ -985,7 +1109,7 @@ config FB_PXA_PARAMETERS
          single model of flatpanel then you can safely leave this
          option disabled.
 
          single model of flatpanel then you can safely leave this
          option disabled.
 

-         Documentation/fb/pxafb.txt describes the available parameters.
+         <file:Documentation/fb/pxafb.txt> describes the available parameters.

 
 config FB_VIRTUAL
        tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
 
 config FB_VIRTUAL
        tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"


@@ -1012,5 +1136,9 @@ if FB || SGI_NEWPORT_CONSOLE
        source "drivers/video/logo/Kconfig"
 endif
 
        source "drivers/video/logo/Kconfig"
 endif
 

+if FB && SYSFS
+       source "drivers/video/backlight/Kconfig"
+endif
+

 endmenu
 
 endmenu