📄 kconfig
字号:
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 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.config FB_SIS_300 bool "SiS 300 series support" depends on FB_SIS help Say Y here to support use of the SiS 300/305, 540, 630 and 730.config FB_SIS_315 bool "SiS 315/330 series support" depends on FB_SIS help Say Y here to support use of the SiS 315 and 330 series (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760).config FB_NEOMAGIC tristate "NeoMagic display support" depends on FB && PCI select FB_MODE_HELPERS help This driver supports notebooks with NeoMagic PCI 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 neofb.config FB_KYRO tristate "IMG Kyro support" depends on FB && PCI help Say Y here if you have a STG4000 / Kyro / PowerVR 3 based graphics board. To compile this driver as a module, choose M here: the module will be called kyrofb.config FB_3DFX tristate "3Dfx Banshee/Voodoo3 display support" depends on FB && PCI help This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 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 tdfxfb.config FB_3DFX_ACCEL bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)" depends on FB_3DFX && EXPERIMENTAL ---help--- This will compile the 3Dfx Banshee/Voodoo3 frame buffer device with acceleration functions.config FB_VOODOO1 tristate "3Dfx Voodoo Graphics (sst1) support" depends on FB && PCI ---help--- Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or Voodoo2 (cvg) based graphics card. To compile this driver as a module, choose M here: the module will be called sstfb. 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 options and other important info support.config FB_TRIDENT tristate "Trident support" depends on FB && PCI ---help--- This driver is supposed to support graphics boards with the Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops but also on some motherboards. For more information, read <file:Documentation/fb/tridentfb.txt> Say Y if you have such a graphics board. To compile this driver as a module, choose M here: the module will be called tridentfb.config FB_TRIDENT_ACCEL bool "Trident Acceleration functions (EXPERIMENTAL)" depends on FB_TRIDENT && EXPERIMENTAL ---help--- This will compile the Trident frame buffer device with acceleration functions.config FB_PM3 tristate "Permedia3 support" depends on FB && PCI && BROKEN help This is the frame buffer device driver for the 3DLabs Permedia3 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & 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 && MIPSconfig PB1000_CRT bool "Use CRT on Pb1000 (J65)" depends on MIPS_PB1000=y && FB_E1356config PB1000_NTSC bool "Use Compsite NTSC on Pb1000 (J63)" depends on MIPS_PB1000=y && FB_E1356config PB1000_TFT bool "Use TFT Panel on Pb1000 (J64)" depends on MIPS_PB1000=y && FB_E1356config PB1500_CRT bool "Use CRT on Pb1500 " if MIPS_PB1500=y depends on FB_E1356config PB1500_CRT prompt "Use CRT on Pb1100 " depends on FB_E1356 && MIPS_PB1100=yconfig PB1500_TFT bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y depends on FB_E1356config PB1500_TFT prompt "Use TFT Panel on Pb1100 " depends on FB_E1356 && MIPS_PB1100=yconfig FB_AU1100 bool "Au1100 LCD Driver" depends on FB && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=yconfig FB_AU1200 bool "Au1200 LCD Driver" depends on FB && MIPS && SOC_AU1200 help This is the framebuffer driver for the AMD Au1200 SOC. It can drive various panels and CRTs by passing in kernel cmd line option au1200fb:panel=<name>.config FB_SBUS bool "SBUS and UPA framebuffers" depends on FB && (SPARC32 || SPARC64) help Say Y if you want support for SBUS or UPA based frame buffer device.config FB_FFB bool "Creator/Creator3D/Elite3D support" depends on FB_SBUS && SPARC64 help This is the frame buffer device driver for the Creator, Creator3D, and Elite3D graphics boards.config FB_TCX bool "TCX (SS4/SS5 only) support" depends on FB_SBUS help This is the frame buffer device driver for the TCX 24/8bit frame buffer.config FB_CG14 bool "CGfourteen (SX) support" depends on FB_SBUS help This is the frame buffer device driver for the CGfourteen frame buffer on Desktop SPARCsystems with the SX graphics option.config FB_P9100 bool "P9100 (Sparcbook 3 only) support" depends on FB_SBUS help This is the frame buffer device driver for the P9100 card supported on Sparcbook 3 machines.config FB_LEO bool "Leo (ZX) support" depends on FB_SBUS help This is the frame buffer device driver for the SBUS-based Sun ZX (leo) frame buffer cards.config FB_PCI bool "PCI framebuffers" depends on FB && PCI && (SPARC64 || SPARC32)config FB_IGA bool "IGA 168x display support" depends on SPARC32 && FB_PCI help This is the framebuffer device for the INTERGRAPHICS 1680 and successor frame buffer cards.config FB_HIT tristate "HD64461 Frame Buffer support" depends on FB && HD64461 help 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" depends on FB && MACH_DECSTATION && TC help Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) used mainly in the MIPS-based DECstation series.config FB_PMAGB_B bool "PMAGB-B TURBOchannel framebuffer support" depends on FB && MACH_DECSTATION && TC help 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 bool "Maxine (Personal DECstation) onboard framebuffer support" depends on FB && MACH_DECSTATION && TC help 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" depends on FB && NINO help The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>. 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) help Say Y here if you want to support the built-in frame buffer of the Motorola 68328 CPU family.config FB_PXA tristate "PXA LCD framebuffer support" depends on FB && ARCH_PXA ---help--- Frame buffer driver for the built-in LCD controller in the Intel PXA2x0 processor. 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 depends on FB_PXA ---help--- Enable the use of kernel command line or module parameters to configure the physical properties of the LCD panel when using the PXA LCD driver. This option allows you to override the panel parameters supplied by the platform in order to support multiple different models of flatpanel. If you will only be using a single model of flatpanel then you can safely leave this option disabled. Documentation/fb/pxafb.txt describes the available parameters.config FB_OMAP tristate "OMAP frame buffer support (EXPERIMENTAL)" depends on FB && ARCH_OMAP help This is the new frame buffer device driver with 2D acceleration for OMAP boards.config FB_OMAP_INTERNAL_LCDC bool "OMAP internal LCD controller support" depends on FB_OMAP default y help Say Y here, if you want to have support for the internal OMAP LCD controller. If unsure, say Y.config FB_OMAP_EXTERNAL_LCDC bool "OMAP external LCD controller support" depends on FB_OMAP help Say Y here, if you want to have support for boards with an external LCD controller connected to the SoSSI interface.config FB_OMAP_MANUAL_UPDATE bool "Default to manual update mode" depends on FB_OMAP_EXTERNAL_LCDC help Say Y here, if your user-space applications are capable of notifying the frame buffer driver when a change has occured in the frame buffer content and thus a reload of the image data is required. If unsure, say N.config FB_OMAP_DMA_TUNE bool "Set DMA SDRAM access priority high" depends on FB_OMAP help On systems in which video memory is in system memory (SDRAM) this will speed up graphics DMA operations. If you have such a system and want to use rotation answer yes. Answer no if you have a dedicated video memory, or don't use any of the accelerated features.config FB_XILINX tristate "Xilinx frame buffer support" depends on FB && XILINX_VIRTEX help Xilinx frame buffer support. This includes the LCD display found on Xilinx ML300 board, and VGA output found on Xilinx ML40x.config FB_XILINX_ROTATE bool " Rotate display" depends on FB_XILINXconfig FB_DAVINCI bool "Davinci Framebuffer support" depends on FB && ARCH_DAVINCI help This is the frame buffer device driver for the DAVINCI graphics hardware found on the TI DAVINCI EVM. If unsure, say N.config FB_VIRTUAL tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)" depends on FB ---help--- This is a `virtual' frame buffer device. It operates on a chunk of unswappable kernel memory instead of on the memory of a graphics board. This means you cannot see any output sent to this frame buffer device, while it does consume precious memory. The main use of this frame buffer device is testing and debugging the frame buffer subsystem. Do NOT enable it for normal systems! To protect the innocent, it has to be enabled explicitly at boot time using the kernel option `video=vfb:'. To compile this driver as a module, choose M here: the module will be called vfb. If unsure, say N.if VT source "drivers/video/console/Kconfig"endifif FB || SGI_NEWPORT_CONSOLE source "drivers/video/logo/Kconfig"endifendmenu
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -