This framework adds support for low-level control of the video output switch.
The frame buffer device provides an abstraction for the graphics hardware. It represents the frame buffer of some video hardware and allows application software to access the graphics hardware through a well-defined interface, so the software doesn't need to know anything about the low-level (hardware register) stuff. Frame buffer devices work identically across the different architectures supported by Linux and make the implementation of application programs easier and more portable; at this point, an X server exists which uses the frame buffer device exclusively. On several non-X86 architectures, the frame buffer device is the only way to use the graphics hardware. The device is accessed through special device nodes, usually located in the /dev directory, i.e. /dev/fb*. You need an utility program called fbset to make full use of frame buffer devices. Please read <file:Documentation/fb/framebuffer.txt> and the Framebuffer-HOWTO at <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more information. Say Y here and to the driver for your graphics board below if you are compiling a kernel for a non-x86 architecture. If you are compiling for the x86 architecture, you can say Y if you want to play with it, but it is not essential. Please note that running graphical applications that directly touch the hardware (e.g. an accelerated X server) and that are not frame buffer device-aware may cause unexpected results. If unsure, say N.
This enables access to the EDID transferred from the firmware. On the i386, this is from the Video BIOS. Enable this if DDC/I2C transfers do not work for your driver and if you are using nvidiafb, i810fb or savagefb. In general, choosing Y for this option is safe. If you experience extremely long delays while booting before you get something on your display, try setting this to N. Matrox cards in combination with certain motherboards and monitors are known to suffer from this problem.
If true, at least one selected framebuffer driver can take advantage of VESA video modes set at an early boot stage via the vga= parameter.
Include the cfb_fillrect function for generic software rectangle filling. This is used by drivers that don't provide their own (accelerated) version.
Include the cfb_copyarea function for generic software area copying. This is used by drivers that don't provide their own (accelerated) version.
Include the cfb_imageblit function for generic software image blitting. This is used by drivers that don't provide their own (accelerated) version.
Allow generic frame-buffer functions to work on displays with 1, 2 and 4 bits per pixel depths which has opposite order of pixels in byte order to bytes in long order.
Include the sys_fillrect function for generic software rectangle filling. This is used by drivers that don't provide their own (accelerated) version and the framebuffer is in system RAM.
Include the sys_copyarea function for generic software area copying. This is used by drivers that don't provide their own (accelerated) version and the framebuffer is in system RAM.
Include the sys_imageblit function for generic software image blitting. This is used by drivers that don't provide their own (accelerated) version and the framebuffer is in system RAM.
This menu will let you enable support for the framebuffers with non-native endianness (e.g. Little-Endian framebuffer on a Big-Endian machine). Most probably you don't have such hardware, so it's safe to say "n" here.
Include functions for accelerated rectangle filling and area copying using WonderMedia Graphics Engine operations.
Common utility functions useful to fbdev drivers of VGA-based cards.
This enables functions for handling video modes using the Generalized Timing Formula and the EDID parser. A few drivers rely on this feature such as the radeonfb, rivafb, and the i810fb. If your driver does not take advantage of this feature, choosing Y will just increase the kernel size by about 5K.
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.
This enables support for Cirrus Logic GD542x/543x based boards on Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum. If you have a PCI-based system, this enables support for these chips: GD-543x, GD-544x, GD-5480. Please read the file <file:Documentation/fb/cirrusfb.txt>. Say N unless you have such a graphics board or plan to get one before you next recompile the kernel.
This is the frame buffer device driver for cards based on the 3D Labs Permedia, Permedia 2 and Permedia 2V chips. The driver was tested on the following cards: Diamond FireGL 1000 PRO AGP ELSA Gloria Synergy PCI Appian Jeronimo PRO (both heads) PCI 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC ASK Graphic Blaster Exxtreme AGP To compile this driver as a module, choose M here: the module will be called pm2fb.
Support the Permedia2 FIFO disconnect feature.
This framebuffer device driver is for the ARM PrimeCell PL110 Colour LCD controller. ARM PrimeCells provide the building blocks for System on a Chip devices. If you want to compile this as a module (=code which can be inserted into and removed from the running kernel), say M here and read <file:Documentation/kbuild/modules.txt>. The module will be called amba-clcd.
This is the frame buffer device driver for the Acorn VIDC graphics hardware found in Acorn RISC PCs and other ARM-based machines. If unsure, say N.
Say Y to enable the Framebuffer driver for the CLPS7111 and EP7212 processors.
This is a framebuffer device for the SA-1100 LCD Controller. See <http://www.linux-fbdev.org/> for information on framebuffer devices. If you plan to use the LCD display with your SA-1100 system, say Y here.
This enables support for the Integraphics CyberPro 20x0 and 5000 VGA chips used in the Rebel.com Netwinder and other machines. Say Y if you have a NetWinder or a graphics card containing this device, otherwise say N.
Say Y here if you want DDC support for your CyberPro graphics card. This is only I2C bus support, driver does not use EDID.
Enable support for the I2C video decoder interface on the Integraphics CyberPro 20x0 and 5000 VGA chips. This is used on the Netwinder machines for the SAA7111 video capture.
This is the frame buffer device driver for the builtin graphics chipset found in Amigas. To compile this driver as a module, choose M here: the module will be called amifb.
This enables support for the original Agnus and Denise video chips, found in the Amiga 1000 and most A500's and A2000's. If you intend to run Linux on any of these systems, say Y; otherwise say N.
This enables support for the Enhanced Chip Set, found in later A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If you intend to run Linux on any of these systems, say Y; otherwise say N.
This enables support for the Advanced Graphics Architecture (also known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T and CD32. If you intend to run Linux on any of these systems, say Y; otherwise say N.
This is the frame buffer device driver for the Amiga FrameMaster card from BSC (exhibited 1992 but not shipped as a CBM product).
This enables support for the Arc Monochrome LCD board. The board is based on the KS-108 lcd controller and is typically a matrix of 2*n chips. This driver was tested with a 128x64 panel. This driver supports it for use with x86 SBCs through a 16 bit GPIO interface (8 bit data, 8 bit control). If you anticipate using this driver, say Y or M; otherwise say N. You must specify the GPIO IO address to be used for setting control and data.
This is the frame buffer device driver for the builtin graphics chipset found in Ataris.
Say Y if you want support with Open Firmware for your graphics board.
This driver supports a frame buffer for the graphics adapter in the Power Macintosh 7300 and others.
This driver supports a frame buffer for the "platinum" graphics adapter in some Power Macintoshes.
This driver supports a frame buffer for the "valkyrie" graphics adapter in some Power Macintoshes.
This is the frame buffer device driver for the Chips & Technologies 65550 graphics chip in PowerBooks.
This is the frame buffer device driver for the Asiliant 69030 chipset
The IMS Twin Turbo is a PCI-based frame buffer card bundled with many Macintosh and compatible computers.
This is the frame buffer device driver for VGA 16 color graphic cards. Say Y if you have such a card. To compile this driver as a module, choose M here: the module will be called vga16fb.
This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on the Blackfin Landscape LCD EZ-Extender Card. This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK. To compile this driver as a module, choose M here: the module will be called bfin-lq035q1-fb.
This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD attached to a BF537. To compile this driver as a module, choose M here: the module will be called bf537-lq035.
This is the framebuffer device for a ADV7393 video encoder attached to a Blackfin on the PPI port. If your Blackfin board has a ADV7393 select Y. To compile this driver as a module, choose M here: the module will be called bfin_adv7393fb.
STI refers to the HP "Standard Text Interface" which is a set of BIOS routines contained in a ROM chip in HP PA-RISC based machines. Enabling this option will implement the linux framebuffer device using calls to the STI BIOS routines for initialisation. If you enable this option, you will get a planar framebuffer device /dev/fb which will work on the most common HP graphic cards of the NGLE family, including the artist chips (in the 7xx and Bxxx series), HCRX, HCRX24, CRX, CRX24 and VisEG series. It is safe to enable this option, so you should probably say "Y".
This is the frame buffer device driver for generic TGA and SFB+ graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards, also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3 TURBOchannel cards, also known as PMAGD-A, -B and -C. Due to hardware limitations ZLX-E2 and E3 cards are not supported for DECstation 5000/200 systems. Additionally due to firmware limitations these cards may cause troubles with booting DECstation 5000/240 and /260 systems, but are fully supported under Linux if you manage to get it going. ;-) Say Y if you have one of those.
This is the frame buffer driver for generic VBE 2.0 compliant graphic cards. It can also take advantage of VBE 3.0 features, such as refresh rate adjustment. This driver generally provides more features than vesafb but requires a userspace helper application called 'v86d'. See <file:Documentation/fb/uvesafb.txt> for more information. If unsure, say N.
This is the frame buffer device driver for generic VESA 2.0 compliant graphic cards. The older VESA 1.2 cards are not supported. You will get a boot time penguin logo at no additional cost. Please read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
This is the EFI frame buffer device driver. If the firmware on your platform is EFI 1.10 or UEFI 2.0, select Y to add support for using the EFI framebuffer as your console.
This enables support for the Apollo display controller in its Hecuba form using the n411 devkit.
Say Y here if you have a Hercules mono graphics card. To compile this driver as a module, choose M here: the module will be called hgafb. As this card technology is at least 25 years old, most people will answer N here.
SGI Visual Workstation support for framebuffer graphics.
This is the frame buffer device driver for SGI Graphics Backend. This chip is used in SGI O2 and Visual Workstation 320/540.
This is the amount of memory reserved for the framebuffer, which can be any value between 1MB and 8MB.
Say Y if you want support for SBUS or UPA based frame buffer device.
This is the frame buffer device driver for the BWtwo frame buffer.
This is the frame buffer device driver for the CGthree frame buffer.
This is the frame buffer device driver for the CGsix (GX, TurboGX) frame buffer.
This is the frame buffer device driver for the Creator, Creator3D, and Elite3D graphics boards.
This is the frame buffer device driver for the TCX 24/8bit frame buffer.
This is the frame buffer device driver for the CGfourteen frame buffer on Desktop SPARCsystems with the SX graphics option.
This is the frame buffer device driver for the P9100 card supported on Sparcbook 3 machines.
This is the frame buffer device driver for the SBUS-based Sun ZX (leo) frame buffer cards.
This is the framebuffer device for the INTERGRAPHICS 1680 and successor frame buffer cards.
This is the framebuffer device for the Sun XVR-500 and similar graphics cards based upon the 3DLABS Wildcat chipset. The driver only works on sparc64 systems where the system firmware has mostly initialized the card already. It is treated as a completely dumb framebuffer device.
This is the framebuffer device for the Sun XVR-2500 and similar graphics cards based upon the 3DLABS Wildcat chipset. The driver only works on sparc64 systems where the system firmware has mostly initialized the card already. It is treated as a completely dumb framebuffer device.
This is the framebuffer device for the Sun XVR-1000 and similar graphics cards. The driver only works on sparc64 systems where the system firmware has mostly initialized the card already. It is treated as a completely dumb framebuffer device.
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>.
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://vdc.epson.com/>.
Support for S1D13XXX framebuffer device family (currently only working with S1D13806). Product specs at <http://vdc.epson.com/>
This enables support for the AT91/AT32 LCD Controller.
Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want to let frame buffer in external SDRAM.
Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD Controller. Say N if you want to connect a TFT. If unsure, say N.
This driver supports graphics boards with the nVidia chips, TNT and newer. For very old chipsets, such as the RIVA128, then use the rivafb. Say Y if you have such a graphics board. To compile this driver as a module, choose M here: the module will be called nvidiafb.
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.
Say Y here if you want the nVidia driver to output all sorts of debugging information to provide to the maintainer when something goes wrong.
Say Y here if you want to control the backlight of your display.
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.
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.
Say Y here if you want the Riva driver to output all sorts of debugging information to provide to the maintainer when something goes wrong.
Say Y here if you want to control the backlight of your display.
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>
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.
This driver supports the LE80578 (Vermilion Range) chipset
This driver supports the LE80578 (Carillo Ranch) board
This driver supports the on-board graphics built in to the Intel 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets. Say Y if you have and plan to use such a board. To make FB_INTELFB=Y work you need to say AGP_INTEL=y too. To compile this driver as a module, choose M here: the module will be called intelfb. For more information, please read <file:Documentation/fb/intelfb.txt>
Say Y here if you want the Intel driver to output all sorts of debugging information to provide to the maintainer when something goes wrong.
Say Y here if you want DDC/I2C support for your on-board Intel graphics.
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=matroxfb:XXX", and are described in <file:Documentation/fb/matroxfb.txt>.
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.
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.
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 say Y to "Matrox I2C support" and "G400 second head support" right below. 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.
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.
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).
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://products.amd.com/en-us/GraphicCardResult.aspx
Say Y here if you want DDC/I2C support for your Radeon board.
Say Y here if you want to control the backlight of your display.
Say Y here if you want the Radeon driver to output all sorts of debugging information to provide to the maintainer when something goes wrong.
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.
Say Y here if you want to control the backlight of your display.
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.
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/mach64.html>.
Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility, Rage XC, or Rage XL chipset.
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>.
Say Y here if you want to control the backlight of your display.
Driver for graphics boards with S3 Trio / S3 Virge chip.
Say Y here if you want DDC support for your S3 graphics card.
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.
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.
This option will compile in console acceleration support. If the resulting framebuffer console has bothersome glitches, then choose N here.
This is the frame buffer device driver for the SiS 300, 315, 330 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets. Specs available at <http://www.sis.com> and <http://www.xgitech.com>. To compile this driver as a module, choose M here; the module will be called sisfb.
Say Y here to support use of the SiS 300/305, 540, 630 and 730.
Say Y here to support use of the SiS 315, 330 and 340 series (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well as XGI V3XT, V5, V8 and Z7.
This is the frame buffer device driver for Graphics chips of VIA UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/ CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896 /P4M900,VX800) Say Y if you have a VIA UniChrome graphics board. To compile this driver as a module, choose M here: the module will be called viafb.
Allow direct hardware access to some output registers via procfs. This is dangerous but may provide the only chance to get the correct output device configuration. Its use is strongly discouraged.
This option reduces the functionality (power saving, ...) of the framebuffer to avoid negative impact on the OpenChrome X server. If you use any X server other than fbdev you should enable this otherwise it should be safe to disable it and allow using all features.
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.
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.
This driver supports graphics boards with the 3Dfx Banshee, Voodoo3 or VSA-100 (aka Voodoo4/5) 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.
This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer device driver with acceleration functions.
Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
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/sstfb.txt> for supported options and other important info support.
Driver for CastleRock integrated graphics core in the VIA VT8623 [Apollo CLE266] chipset.
This is the frame buffer device driver for Trident PCI/AGP chipsets. Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D and Blade XP. There are also integrated versions of these chips called CyberXXXX, CyberImage or CyberBlade. These chips are mostly found in laptops but also on some motherboards including early VIA EPIA 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.
Driver for PCI graphics boards with ARK 2000PV chip and ICS 5342 RAMDAC.
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.
This is the frame buffer device driver for the Fujitsu Carmine chip. The driver provides two independent frame buffer devices.
Use timings which work on the eval card.
Use custom board timings.
This is the framebuffer driver for the AMD Au1100 SOC. It can drive various panels and CRTs by passing in kernel cmd line option au1100fb:panel=<name>.
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>.
This is the framebuffer driver for VIA VT8500 integrated LCD controller.
This is the framebuffer driver for WonderMedia WM8505 integrated LCD controller.
This is the frame buffer device driver for the Hitachi HD64461 LCD frame buffer card.
Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1) used mainly in the MIPS-based DECstation series.
Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) used mainly in the MIPS-based DECstation series.
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.
Support for the onboard framebuffer (1024x768x8) in the Personal DECstation series (Personal DECstation 5000/20, /25, /33, /50, Codename "Maxine").
The G364 driver is the framebuffer used in MIPS Magnum 4000 and Olivetti M700-10 systems.
Say Y here if you want to support the built-in frame buffer of the Motorola 68328 CPU family.
Frame buffer driver for the built-in LCD controller in the Marvell MMP processor.
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 pxafb. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>. If unsure, say N.
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. <file:Documentation/fb/pxafb.txt> describes the available parameters.
Kernelspace driver for the 2D graphics controller unit (GCU) found on PXA3xx processors. There is a counterpart driver in the DirectFB suite, see http://www.directfb.org/ If you compile this as a module, it will be called pxa3xx_gcu.
Framebuffer driver for the Intel 2700G (Marathon) Graphics Accelerator
Enable this if you want debugging information using the debug filesystem (debugfs) If unsure, say N.
Framebuffer driver for the Freescale SoC DIU
Frame buffer driver for the w100 as found on the Sharp SL-Cxx series. It can also drive the w3220 chip found on iPAQ hx4700. 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 w100fb. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>. If unsure, say N.
Frame buffer driver for the on-chip SH-Mobile LCD controller.
Driver for the on-chip SH-Mobile HDMI controller.
Enable MERAM support for the SH-Mobile LCD controller. This will allow for caching of the framebuffer to provide more reliable access under heavy main memory bus traffic situations. Up to 4 memory channels can be configured, allowing 4 RGB or 2 YCbCr framebuffers to be configured.
Frame buffer driver for the Toshiba Mobile IO integrated as found on the Sharp SL-6000 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 tmiofb. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>. If unsure, say N.
Frame buffer driver for the built-in FB controller in the Samsung SoC line from the S3C2443 onwards, including the S3C2416, S3C2450, and the S3C64XX series such as the S3C6400 and S3C6410. These chips all have the same basic framebuffer design with the actual capabilities depending on the chip. For instance the S3C6400 and S3C6410 support 4 hardware windows whereas the S3C24XX series currently only have two. Currently the support is only for the S3C6400 and S3C6410 SoCs.
Show all register writes via printk(KERN_DEBUG)
Frame buffer driver for the built-in LCD controller in the Samsung S3C2410 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 s3c2410fb. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>. If unsure, say N.
Turn on debugging messages. Note that you can set/unset at run time through sysfs
Frame buffer driver for the built-in LCD controller in the Nuvoton NUC900 processor
Turn on debugging messages. Note that you can set/unset at run time through sysfs
Frame buffer driver for the CRT and LCD controllers in the Silicon Motion SM501. 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 sm501fb. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>. If unsure, say N.
This is a kernel framebuffer driver for DisplayLink USB devices. Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices. To compile as a module, choose M here: the module name is udlfb.
Say Y here to enable support for PNX4008 Display Update Module (DUM)
Say Y here to enable support for PNX4008 RGB Framebuffer
Say Y here to enable support for the IBM GXT4500P display adaptor, found on some IBM System P (pSeries) machines.
Include support for the virtual frame buffer in the PS3 platform.
This is the default size (in MiB) of the virtual frame buffer in the PS3. The default value can be overridden on the kernel command line using the "ps3fb" option (e.g. "ps3fb=9M");
Include support for the Xilinx ML300/ML403 reference design framebuffer. ML300 carries a 640*480 LCD display on the board, ML403 uses a standard DB15 VGA connector.
Support for the SH7760/SH7763/SH7720/SH7721 integrated (D)STN/TFT LCD Controller. Supports display resolutions up to 1024x1024 pixel, grayscale and color operation, with depths ranging from 1 bpp to 8 bpp monochrome and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for panels <= 320 pixel horizontal resolution.
This is the frame buffer device driver for the TI LCD controller found on DA8xx/OMAP-L1xx SoCs. If unsure, say N.
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. In order to load it, you must use the vfb_enable=1 option. If unsure, say N.
This driver implements the front-end of the Xen virtual frame buffer driver. It communicates with a back-end in another domain.
This driver implements support for the E-Ink Metronome controller. The pre-release name for this device was 8track and could also have been called by some vendors as PVI-nnnn.
Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
This enables framebuffer support for Fujitsu Carmine/Coral-P(A) PCI graphics controller devices.
Framebuffer support for Fujitsu Lime GDC on host CPU bus.
Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter driver to support accessing I2C devices on controller's I2C bus. These are usually some video decoder chips.
Framebuffer driver for the Cirrus Logic EP93XX series of processors. This driver is also available as a module. The module will be called ep93xx-fb.
Select this option if display contents should be inherited as set by the bootloader.
This is a framebuffer device for the i.MX31 LCD Controller. So far only synchronous displays are supported. If you plan to use an LCD display with your i.MX31 system, say Y here.
This driver implements support for the E-Ink Broadsheet controller. The release name for this device was Epson S1D13521 and could also have been called by other names when coupled with a bridge adapter.
Framebuffer support for the JZ4740 SoC.
Framebuffer support for the MXS SoC.
Choose this option if you want to use the Unigfx device as a framebuffer device. Without the support of PCI & AGP.