📄 kconfig
字号:
bool "CGsix (GX,TurboGX) support" depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3) help This is the frame buffer device driver for the CGsix (GX, TurboGX) frame buffer.config FB_PVR2 tristate "NEC PowerVR 2 display support" depends on FB && SH_DREAMCAST ---help--- Say Y here if you have a PowerVR 2 card in your box. If you plan to run linux on your Dreamcast, you will have to say Y here. This driver may or may not work on other PowerVR 2 cards, but is totally untested. Use at your own risk. If unsure, say N. To compile this driver as a module, choose M here: the module will be called pvr2fb. You can pass several parameters to the driver at boot time or at module load time. The parameters look like "video=pvr2:XXX", where the meaning of XXX can be found at the end of the main source file (<file:drivers/video/pvr2fb.c>). Please see the file <file:Documentation/fb/pvr2fb.txt>.config FB_EPSON1355 bool "Epson 1355 framebuffer support" depends on FB && (SUPERH || ARCH_CEIVA) help Build in support for the SED1355 Epson Research Embedded RAMDAC LCD/CRT Controller (since redesignated as the S1D13505) as a framebuffer. Product specs at <http://www.erd.epson.com/vdc/html/products.htm>.config FB_RIVA tristate "nVidia Riva support" depends on FB && PCI select I2C_ALGOBIT if FB_RIVA_I2C select I2C if FB_RIVA_I2C select FB_MODE_HELPERS help This driver supports graphics boards with the nVidia Riva/Geforce chips. Say Y if you have such a graphics board. To compile this driver as a module, choose M here: the module will be called rivafb.config FB_RIVA_I2C bool "Enable DDC Support" depends on FB_RIVA help This enables I2C support for nVidia 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_RIVA_DEBUG bool "Lots of debug output from Riva(nVidia) driver" depends on FB_RIVA default n help Say Y here if you want the Riva driver to output all sorts of debugging informations to provide to the maintainer when something goes wrong.config FB_I810 tristate "Intel 810/815 support (EXPERIMENTAL)" depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64 select AGP select AGP_INTEL select FB_MODE_HELPERS help This driver supports the on-board graphics built in to the Intel 810 and 815 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 i810fb. For more information, please read <file:Documentation/fb/intel810.txt>config FB_I810_GTF bool "use VESA Generalized Timing Formula" depends on FB_I810 help If you say Y, then the VESA standard, Generalized Timing Formula or GTF, will be used to calculate the required video timing values per video mode. Since the GTF allows nondiscrete timings (nondiscrete being a range of values as opposed to discrete being a set of values), you'll be able to use any combination of horizontal and vertical resolutions, and vertical refresh rates without having to specify your own timing parameters. This is especially useful to maximize the performance of an aging display, or if you just have a display with nonstandard dimensions. A VESA compliant monitor is recommended, but can still work with non-compliant ones. If you need or want this, then select this option. The timings may not be compliant with Intel's recommended values. Use at your own risk. If you say N, the driver will revert to discrete video timings using a set recommended by Intel in their documentation. 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 ---help--- Say Y here if you have a Matrox Millennium, Matrox Millennium II, Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video, Matrox G400, G450 or G550 card in your box. To compile this driver as a module, choose M here: the module will be called matroxfb. You can pass several parameters to the driver at boot time or at module load time. The parameters look like "video=matrox:XXX", and are described in <file:Documentation/fb/matroxfb.txt>.config FB_MATROX_MILLENIUM bool "Millennium I/II support" depends on FB_MATROX help Say Y here if you have a Matrox Millennium or Matrox Millennium II video card. If you select "Advanced lowlevel driver options" below, you should check 4 bpp packed pixel, 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.config FB_MATROX_MYSTIQUE bool "Mystique support" depends on FB_MATROX help Say Y here if you have a Matrox Mystique or Matrox Mystique 220 video card. If you select "Advanced lowlevel driver options" below, 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.config FB_MATROX_G450 bool "G100/G200/G400/G450/G550 support" depends on FB_MATROX ---help--- Say Y here if you have a Matrox G100, G200, G400, G450 or G550 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. 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 swap primary and secondary head outputs, or to change output mode. Secondary head driver always start in 640x480 resolution and you must use fbset to change it. Do not forget that second head supports only 16 and 32 bpp packed pixels, so it is a good idea to compile them into the kernel too. You can use only some font widths, as the driver uses generic painting procedures (the secondary head does not use acceleration engine). 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 yconfig FB_MATROX_I2C tristate "Matrox I2C support" depends on FB_MATROX && I2C select I2C_ALGOBIT ---help--- This drivers creates I2C buses which are needed for accessing the DDC (I2C) bus present on all Matroxes, an I2C bus which interconnects Matrox optional devices, like MGA-TVO on G200 and G400, and the secondary head DDC bus, present on G400 only. You can say Y or M here if you want to experiment with monitor detection code. You must say Y or M here if you want to use either second head of G400 or MGA-TVO on G200 or G400. If you compile it as module, it will create a module named i2c-matroxfb.config FB_MATROX_MAVEN tristate "G400 second head support" depends on FB_MATROX_G100 && FB_MATROX_I2C ---help--- WARNING !!! This support does not work with G450 !!! Say Y or M here if you want to use a secondary head (meaning two monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary head is not compatible with accelerated XFree 3.3.x SVGA servers - secondary head output is blanked while you are in X. With XFree 3.9.17 preview you can use both heads if you use SVGA over fbdev or the fbdev driver on first head and the fbdev driver on second head. If you compile it as module, two modules are created, matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for both G200 and G400, matroxfb_crtc2 is needed only by G400. You must also load i2c-matroxfb to get it to run. The driver starts in monitor mode and you must use the matroxset tool (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to PAL or NTSC or to swap primary and secondary head outputs. Secondary head driver also always start in 640x480 resolution, you must use fbset to change it. Also do not forget that second head supports only 16 and 32 bpp packed pixels, so it is a good idea to compile them into the kernel too. You can use only some font widths, as the driver uses generic painting procedures (the secondary head does not use acceleration engine).config FB_MATROX_MULTIHEAD bool "Multihead support" depends on FB_MATROX ---help--- Say Y here if you have more than one (supported) Matrox device in your computer and you want to use all of them for different monitors ("multihead"). If you have only one device, you should say N because the driver compiled with Y is larger and a bit slower, especially on ia32 (ix86). If you said M to "Matrox unified accelerated driver" and N here, you will still be able to use several Matrox devices simultaneously: insert several instances of the module matroxfb into the kernel with insmod, supplying the parameter "dev=N" where N is 0, 1, etc. for the different Matrox devices. This method is slightly faster but uses 40 KB of kernel memory per Matrox card. There is no need for enabling 'Matrox multihead support' if you have only one Matrox card in the box.config FB_RADEON_OLD tristate "ATI Radeon display support (Old driver)" depends on FB && PCI help Choose this option if you want to use an ATI Radeon graphics card as a framebuffer device. There are both PCI and AGP versions. You don't need to choose this to run the Radeon in plain VGA mode. There is a product page at <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.config FB_RADEON tristate "ATI Radeon display support" depends on FB && PCI select I2C_ALGOBIT if FB_RADEON_I2C select I2C if FB_RADEON_I2C select FB_MODE_HELPERS help Choose this option if you want to use an ATI Radeon graphics card as a framebuffer device. There are both PCI and AGP versions. You don't need to choose this to run the Radeon in plain VGA mode. If you say Y here and want DDC/I2C support you must first say Y to "I2C support" and "I2C bit-banging support" in the character devices section. If you say M here then "I2C support" and "I2C bit-banging support" can be build either as modules or built-in. There is a product page at <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.config FB_RADEON_I2C bool "DDC/I2C for ATI Radeon support" depends on FB_RADEON default y help Say Y here if you want DDC/I2C support for your Radeon board. config FB_RADEON_DEBUG bool "Lots of debug output from Radeon driver" depends on FB_RADEON default n help Say Y here if you want the Radeon driver to output all sorts of debugging informations to provide to the maintainer when something goes wrong.config FB_ATY128 tristate "ATI Rage128 display support" depends on FB && PCI help This driver supports graphics boards with the ATI Rage128 chips. Say Y if you have such a graphics board and read <file:Documentation/fb/aty128fb.txt>. To compile this driver as a module, choose M here: the module will be called aty128fb.config FB_ATY tristate "ATI Mach64 display support" if PCI || ATARI depends on FB help This driver supports graphics boards with the ATI Mach64 chips. Say Y if you have such a graphics board. To compile this driver as a module, choose M here: the module will be called atyfb.config FB_ATY_CT bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support" depends on PCI && FB_ATY default y if SPARC64 && FB_PCI help Say Y here to support use of ATI's 64-bit Rage boards (or other boards based on the Mach64 CT, VT, GT, and LT chipsets) as a 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 default y if ATARI help Say Y here to support use of the ATI Mach64 Graphics Expression board (or other boards based on the Mach64 GX chipset) as a framebuffer device. The ATI product support page for these boards is at <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.config FB_SM tristate "Silicon Motion SM722 support" depends on FB && PCI help SM722choice prompt "Display size" depends on FB_SM default DISPLAY_640x480config DISPLAY_640x480 bool "640x480"config DISPLAY_1024x768 bool "1024x768"endchoiceconfig 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 This driver supports notebooks and computers with S3 Savage PCI/AGP⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -