|
|
Line 1: |
Line 1: |
− | = Support for frame buffer devices =
| |
| | | |
− | <pre>
| |
− | 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.2.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.
| |
− |
| |
− |
| |
− | FIRMWARE_EDID
| |
− | Enable firmware EDID
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_BOOT_VESA_SUPPORT
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_CFB_FILLRECT
| |
− |
| |
− | Include the cfb_fillrect function for generic software rectangle
| |
− | filling. This is used by drivers that don't provide their own
| |
− | (accelerated) version.
| |
− |
| |
− |
| |
− | FB_CFB_COPYAREA
| |
− |
| |
− | Include the cfb_copyarea function for generic software area copying.
| |
− | This is used by drivers that don't provide their own (accelerated)
| |
− | version.
| |
− |
| |
− |
| |
− | FB_CFB_IMAGEBLIT
| |
− |
| |
− | Include the cfb_imageblit function for generic software image
| |
− | blitting. This is used by drivers that don't provide their own
| |
− | (accelerated) version.
| |
− |
| |
− |
| |
− | FB_CFB_REV_PIXELS_IN_BYTE
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SYS_FILLRECT
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SYS_COPYAREA
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SYS_IMAGEBLIT
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_FOREIGN_ENDIAN
| |
− | Framebuffer foreign endianness support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SVGALIB
| |
− |
| |
− | Common utility functions useful to fbdev drivers of VGA-based
| |
− | cards.
| |
− |
| |
− |
| |
− | FB_MODE_HELPERS
| |
− | Enable Video Mode Handling Helpers
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_TILEBLITTING
| |
− | Enable Tile Blitting Support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | Frame buffer hardware drivers
| |
− | FB_CIRRUS
| |
− | Cirrus Logic support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_PM2
| |
− | Permedia2 support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_PM2_FIFO_DISCONNECT
| |
− | enable FIFO disconnect feature
| |
− |
| |
− | Support the Permedia2 FIFO disconnect feature.
| |
− |
| |
− |
| |
− | FB_ARMCLCD
| |
− | ARM PrimeCell PL110 support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
| |
− | LogicPD LCD 3.5\" QVGA w/HRTFT IC
| |
− |
| |
− | This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
| |
− | color QVGA, HRTFT panel. The LogicPD device includes
| |
− | an integrated HRTFT controller IC.
| |
− | The native resolution is 240x320.
| |
− |
| |
− |
| |
− | FB_ARMCLCD_SHARP_LQ057Q3DC02
| |
− | LogicPD LCD 5.7\" QVGA
| |
− |
| |
− | This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
| |
− | color QVGA, TFT panel. The LogicPD device includes an
| |
− | The native resolution is 320x240.
| |
− |
| |
− |
| |
− | FB_ARMCLCD_SHARP_LQ64D343
| |
− | LogicPD LCD 6.4\" VGA
| |
− |
| |
− | This is an implementation of the Sharp LQ64D343, a 6.4"
| |
− | color VGA, TFT panel. The LogicPD device includes an
| |
− | The native resolution is 640x480.
| |
− |
| |
− |
| |
− | FB_ARMCLCD_SHARP_LQ10D368
| |
− | LogicPD LCD 10.4\" VGA
| |
− |
| |
− | This is an implementation of the Sharp LQ10D368, a 10.4"
| |
− | color VGA, TFT panel. The LogicPD device includes an
| |
− | The native resolution is 640x480.
| |
− |
| |
− |
| |
− |
| |
− | FB_ARMCLCD_SHARP_LQ121S1DG41
| |
− | LogicPD LCD 12.1\" SVGA
| |
− |
| |
− | This is an implementation of the Sharp LQ121S1DG41, a 12.1"
| |
− | color SVGA, TFT panel. The LogicPD device includes an
| |
− | The native resolution is 800x600.
| |
− |
| |
− | This panel requires a clock rate may be an integer fraction
| |
− | of the base LCDCLK frequency. The driver will select the
| |
− | highest frequency available that is lower than the maximum
| |
− | allowed. The panel may flicker if the clock rate is
| |
− | slower than the recommended minimum.
| |
− |
| |
− |
| |
− | FB_ARMCLCD_AUO_A070VW01_WIDE
| |
− | AU Optronics A070VW01 LCD 7.0\" WIDE
| |
− |
| |
− | This is an implementation of the AU Optronics, a 7.0"
| |
− | WIDE Color. The native resolution is 234x480.
| |
− |
| |
− |
| |
− | FB_ARMCLCD_HITACHI
| |
− | Hitachi Wide Screen 800x480
| |
− |
| |
− | This is an implementation of the Hitachi 800x480.
| |
− |
| |
− |
| |
− | FB_ACORN
| |
− | Acorn VIDC support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_CLPS711X
| |
− | CLPS711X LCD support
| |
− |
| |
− | Say Y to enable the Framebuffer driver for the CLPS7111 and
| |
− | EP7212 processors.
| |
− |
| |
− |
| |
− | FB_SA1100
| |
− | SA-1100 LCD support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_CYBER2000
| |
− | CyberPro 2000/2010/5000 support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_AMIGA
| |
− | Amiga native chipset support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_AMIGA_OCS
| |
− | Amiga OCS chipset support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_AMIGA_ECS
| |
− | Amiga ECS chipset support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_AMIGA_AGA
| |
− | Amiga AGA chipset support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_FM2
| |
− | Amiga FrameMaster II/Rainbow II support
| |
− |
| |
− | This is the frame buffer device driver for the Amiga FrameMaster
| |
− | card from BSC (exhibited 1992 but not shipped as a CBM product).
| |
− |
| |
− |
| |
− | FB_ARC
| |
− | Arc Monochrome LCD board support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_ATARI
| |
− | Atari native chipset support
| |
− |
| |
− | This is the frame buffer device driver for the builtin graphics
| |
− | chipset found in Ataris.
| |
− |
| |
− |
| |
− | FB_OF
| |
− | Open Firmware frame buffer device support
| |
− |
| |
− | Say Y if you want support with Open Firmware for your graphics
| |
− | board.
| |
− |
| |
− |
| |
− | FB_CONTROL
| |
− | Apple \"control\" display support
| |
− |
| |
− | This driver supports a frame buffer for the graphics adapter in the
| |
− | Power Macintosh 7300 and others.
| |
− |
| |
− |
| |
− | FB_PLATINUM
| |
− | Apple \"platinum\" display support
| |
− |
| |
− | This driver supports a frame buffer for the "platinum" graphics
| |
− | adapter in some Power Macintoshes.
| |
− |
| |
− |
| |
− | FB_VALKYRIE
| |
− | Apple \"valkyrie\" display support
| |
− |
| |
− | This driver supports a frame buffer for the "valkyrie" graphics
| |
− | adapter in some Power Macintoshes.
| |
− |
| |
− |
| |
− | FB_CT65550
| |
− | Chips 65550 display support
| |
− |
| |
− | This is the frame buffer device driver for the Chips & Technologies
| |
− | 65550 graphics chip in PowerBooks.
| |
− |
| |
− |
| |
− | FB_ASILIANT
| |
− | Asiliant (Chips) 69000 display support
| |
− |
| |
− | This is the frame buffer device driver for the Asiliant 69030 chipset
| |
− |
| |
− |
| |
− | FB_IMSTT
| |
− | IMS Twin Turbo display support
| |
− |
| |
− | The IMS Twin Turbo is a PCI-based frame buffer card bundled with
| |
− | many Macintosh and compatible computers.
| |
− |
| |
− |
| |
− | FB_VGA16
| |
− | VGA 16-color graphics support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_BF54X_LQ043
| |
− | SHARP LQ043 TFT LCD (BF548 EZKIT)
| |
− |
| |
− | This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
| |
− |
| |
− |
| |
− | FB_BFIN_T350MCQB
| |
− | Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− |
| |
− | FB_STI
| |
− | HP STI frame buffer device support
| |
− |
| |
− | 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".
| |
− |
| |
− |
| |
− | FB_TGA
| |
− | TGA/SFB+ framebuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_UVESA
| |
− | Userspace VESA VGA graphics support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_VESA
| |
− | VESA VGA graphics support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_EFI
| |
− | EFI-based Framebuffer Support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_N411
| |
− | N411 Apollo/Hecuba devkit support
| |
− |
| |
− | This enables support for the Apollo display controller in its
| |
− | Hecuba form using the n411 devkit.
| |
− |
| |
− |
| |
− | FB_HGA
| |
− | Hercules mono graphics support
| |
− |
| |
− | 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 15 years old, most people will answer N
| |
− | here.
| |
− |
| |
− |
| |
− | FB_HGA_ACCEL
| |
− | Hercules mono Acceleration functions (EXPERIMENTAL)
| |
− |
| |
− | This will compile the Hercules mono graphics with
| |
− | acceleration functions.
| |
− |
| |
− |
| |
− | FB_SGIVW
| |
− | SGI Visual Workstation framebuffer support
| |
− |
| |
− | SGI Visual Workstation support for framebuffer graphics.
| |
− |
| |
− |
| |
− | FB_GBE
| |
− | SGI Graphics Backend frame buffer support
| |
− |
| |
− | This is the frame buffer device driver for SGI Graphics Backend.
| |
− | This chip is used in SGI O2 and Visual Workstation 320/540.
| |
− |
| |
− |
| |
− | FB_GBE_MEM
| |
− | Video memory size in MB
| |
− |
| |
− | This is the amount of memory reserved for the framebuffer,
| |
− | which can be any value between 1MB and 8MB.
| |
− |
| |
− |
| |
− | FB_SBUS
| |
− | SBUS and UPA framebuffers
| |
− |
| |
− | Say Y if you want support for SBUS or UPA based frame buffer device.
| |
− |
| |
− |
| |
− | FB_BW2
| |
− | BWtwo support
| |
− |
| |
− | This is the frame buffer device driver for the BWtwo frame buffer.
| |
− |
| |
− |
| |
− | FB_CG3
| |
− | CGthree support
| |
− |
| |
− | This is the frame buffer device driver for the CGthree frame buffer.
| |
− |
| |
− |
| |
− | FB_CG6
| |
− | CGsix (GX,TurboGX) support
| |
− |
| |
− | This is the frame buffer device driver for the CGsix (GX, TurboGX)
| |
− | frame buffer.
| |
− |
| |
− |
| |
− | FB_FFB
| |
− | Creator/Creator3D/Elite3D support
| |
− |
| |
− | This is the frame buffer device driver for the Creator, Creator3D,
| |
− | and Elite3D graphics boards.
| |
− |
| |
− |
| |
− | FB_TCX
| |
− | TCX (SS4/SS5 only) support
| |
− |
| |
− | This is the frame buffer device driver for the TCX 24/8bit frame
| |
− | buffer.
| |
− |
| |
− |
| |
− | FB_CG14
| |
− | CGfourteen (SX) support
| |
− |
| |
− | This is the frame buffer device driver for the CGfourteen frame
| |
− | buffer on Desktop SPARCsystems with the SX graphics option.
| |
− |
| |
− |
| |
− | FB_P9100
| |
− | P9100 (Sparcbook 3 only) support
| |
− |
| |
− | This is the frame buffer device driver for the P9100 card
| |
− | supported on Sparcbook 3 machines.
| |
− |
| |
− |
| |
− | FB_LEO
| |
− | Leo (ZX) support
| |
− |
| |
− | This is the frame buffer device driver for the SBUS-based Sun ZX
| |
− | (leo) frame buffer cards.
| |
− |
| |
− |
| |
− | FB_IGA
| |
− | IGA 168x display support
| |
− |
| |
− | This is the framebuffer device for the INTERGRAPHICS 1680 and
| |
− | successor frame buffer cards.
| |
− |
| |
− |
| |
− | FB_XVR500
| |
− | Sun XVR-500 3DLABS Wildcat support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_XVR2500
| |
− | Sun XVR-2500 3DLABS Wildcat support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_PVR2
| |
− | NEC PowerVR 2 display support
| |
− |
| |
− | 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>.
| |
− |
| |
− |
| |
− | FB_EPSON1355
| |
− | Epson 1355 framebuffer support
| |
− |
| |
− | 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>.
| |
− |
| |
− |
| |
− | FB_S1D13XXX
| |
− | Epson S1D13XXX framebuffer support
| |
− |
| |
− | Support for S1D13XXX framebuffer device family (currently only
| |
− | working with S1D13806). Product specs at
| |
− | <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
| |
− |
| |
− | FB_ATMEL
| |
− | AT91/AT32 LCD Controller support
| |
− |
| |
− | This enables support for the AT91/AT32 LCD Controller.
| |
− |
| |
− |
| |
− | FB_INTSRAM
| |
− | Frame Buffer in internal SRAM
| |
− |
| |
− | Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
| |
− | to let frame buffer in external SDRAM.
| |
− |
| |
− |
| |
− | FB_ATMEL_STN
| |
− | Use a STN display with AT91/AT32 LCD Controller
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_NVIDIA
| |
− | nVidia Framebuffer Support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_NVIDIA_I2C
| |
− | Enable DDC Support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_NVIDIA_DEBUG
| |
− | Lots of debug output
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_NVIDIA_BACKLIGHT
| |
− | Support for backlight control
| |
− |
| |
− | Say Y here if you want to control the backlight of your display.
| |
− |
| |
− |
| |
− | FB_RIVA
| |
− | nVidia Riva support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_RIVA_I2C
| |
− | Enable DDC Support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_RIVA_DEBUG
| |
− | Lots of debug output
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_RIVA_BACKLIGHT
| |
− | Support for backlight control
| |
− |
| |
− | Say Y here if you want to control the backlight of your display.
| |
− |
| |
− |
| |
− | FB_I810
| |
− | Intel 810/815 support (EXPERIMENTAL)
| |
− |
| |
− | 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>
| |
− |
| |
− | FB_I810_GTF
| |
− | use VESA Generalized Timing Formula
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_I810_I2C
| |
− | Enable DDC Support
| |
− |
| |
− | FB_LE80578
| |
− | Intel LE80578 (Vermilion) support
| |
− |
| |
− | This driver supports the LE80578 (Vermilion Range) chipset
| |
− |
| |
− |
| |
− | FB_CARILLO_RANCH
| |
− | Intel Carillo Ranch support
| |
− |
| |
− | This driver supports the LE80578 (Carillo Ranch) board
| |
− |
| |
− |
| |
− | FB_INTEL
| |
− | Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)
| |
− |
| |
− | 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.
| |
− |
| |
− | 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.
| |
− |
| |
− | 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>
| |
− |
| |
− | FB_INTEL_DEBUG
| |
− | Intel driver Debug Messages
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_INTEL_I2C
| |
− | DDC/I2C for Intel framebuffer support
| |
− |
| |
− | Say Y here if you want DDC/I2C support for your on-board Intel graphics.
| |
− |
| |
− |
| |
− | FB_MATROX
| |
− | Matrox acceleration
| |
− |
| |
− | 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>.
| |
− |
| |
− |
| |
− | FB_MATROX_MILLENIUM
| |
− | Millennium I/II support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_MATROX_MYSTIQUE
| |
− | Mystique support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_MATROX_G
| |
− | G100/G200/G400/G450/G550 support
| |
− |
| |
− | 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" 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.
| |
− |
| |
− |
| |
− | FB_MATROX_I2C
| |
− | Matrox I2C support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_MATROX_MAVEN
| |
− | G400 second head support
| |
− |
| |
− | 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).
| |
− |
| |
− |
| |
− | FB_MATROX_MULTIHEAD
| |
− | Multihead support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_RADEON
| |
− | ATI Radeon display support
| |
− |
| |
− | 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://apps.ati.com/ATIcompare/
| |
− |
| |
− |
| |
− | FB_RADEON_I2C
| |
− | DDC/I2C for ATI Radeon support
| |
− |
| |
− | Say Y here if you want DDC/I2C support for your Radeon board.
| |
− |
| |
− |
| |
− | FB_RADEON_BACKLIGHT
| |
− | Support for backlight control
| |
− |
| |
− | Say Y here if you want to control the backlight of your display.
| |
− |
| |
− |
| |
− | FB_RADEON_DEBUG
| |
− | Lots of debug output from Radeon driver
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_ATY128
| |
− | ATI Rage128 display support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_ATY128_BACKLIGHT
| |
− | Support for backlight control
| |
− |
| |
− | Say Y here if you want to control the backlight of your display.
| |
− |
| |
− |
| |
− | FB_ATY
| |
− | ATI Mach64 display support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_ATY_CT
| |
− | Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
| |
− |
| |
− | 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/>.
| |
− |
| |
− |
| |
− | FB_ATY_GENERIC_LCD
| |
− | Mach64 generic LCD support (EXPERIMENTAL)
| |
− |
| |
− | Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
| |
− | Rage XC, or Rage XL chipset.
| |
− |
| |
− |
| |
− | FB_ATY_GX
| |
− | Mach64 GX support
| |
− |
| |
− | 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>.
| |
− |
| |
− |
| |
− | FB_ATY_BACKLIGHT
| |
− | Support for backlight control
| |
− |
| |
− | Say Y here if you want to control the backlight of your display.
| |
− |
| |
− |
| |
− | FB_S3
| |
− | S3 Trio/Virge support
| |
− |
| |
− | Driver for graphics boards with S3 Trio / S3 Virge chip.
| |
− |
| |
− |
| |
− | FB_SAVAGE
| |
− | S3 Savage 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.
| |
− |
| |
− |
| |
− | FB_SAVAGE_I2C
| |
− | Enable DDC2 Support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SAVAGE_ACCEL
| |
− | Enable Console Acceleration
| |
− |
| |
− | This option will compile in console acceleration support. If
| |
− | the resulting framebuffer console has bothersome glitches, then
| |
− | choose N here.
| |
− |
| |
− |
| |
− | FB_SIS
| |
− | SiS/XGI display support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SIS_300
| |
− | SiS 300 series support
| |
− |
| |
− | Say Y here to support use of the SiS 300/305, 540, 630 and 730.
| |
− |
| |
− |
| |
− | FB_SIS_315
| |
− | SiS 315/330/340 series and XGI support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_VIA
| |
− | VIA UniChrome (Pro) and Chrome9 display support
| |
− |
| |
− | 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.
| |
− |
| |
− | FB_NEOMAGIC
| |
− | NeoMagic display support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_KYRO
| |
− | IMG Kyro support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_3DFX
| |
− | 3Dfx Banshee/Voodoo3/Voodoo5 display support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_3DFX_ACCEL
| |
− | 3Dfx Acceleration functions (EXPERIMENTAL)
| |
− |
| |
− | This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
| |
− | device driver with acceleration functions.
| |
− |
| |
− |
| |
− | FB_VOODOO1
| |
− | 3Dfx Voodoo Graphics (sst1) support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_VT8623
| |
− | VIA VT8623 support
| |
− |
| |
− | Driver for CastleRock integrated graphics core in the
| |
− | VIA VT8623 [Apollo CLE266] chipset.
| |
− |
| |
− |
| |
− | FB_CYBLA
| |
− | Cyberblade/i1 support
| |
− |
| |
− | This driver is supposed to support the Trident Cyberblade/i1
| |
− | graphics core integrated in the VIA VT8601A North Bridge,
| |
− | also known as VIA Apollo PLE133.
| |
− |
| |
− | Status:
| |
− | - Developed, tested and working on EPIA 5000 and EPIA 800.
| |
− | - Does work reliable on all systems with CRT/LCD connected to
| |
− | normal VGA ports.
| |
− | - Should work on systems that do use the internal LCD port, but
| |
− | this is absolutely not tested.
| |
− |
| |
− | Character imageblit, copyarea and rectangle fill are hw accelerated,
| |
− | ypan scrolling is used by default.
| |
− |
| |
− | Please do read <file:Documentation/fb/cyblafb/*>.
| |
− |
| |
− | To compile this driver as a module, choose M here: the
| |
− | module will be called cyblafb.
| |
− |
| |
− |
| |
− | FB_TRIDENT
| |
− | Trident support
| |
− |
| |
− | 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. 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.
| |
− |
| |
− |
| |
− | FB_TRIDENT_ACCEL
| |
− | Trident Acceleration functions (EXPERIMENTAL)
| |
− |
| |
− | This will compile the Trident frame buffer device with
| |
− | acceleration functions.
| |
− |
| |
− |
| |
− | FB_ARK
| |
− | ARK 2000PV support
| |
− |
| |
− | Driver for PCI graphics boards with ARK 2000PV chip
| |
− | and ICS 5342 RAMDAC.
| |
− |
| |
− |
| |
− | FB_PM3
| |
− | Permedia3 support (EXPERIMENTAL)
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_CARMINE
| |
− | Fujitsu carmine frame buffer support
| |
− |
| |
− | This is the frame buffer device driver for the Fujitsu Carmine chip.
| |
− | The driver provides two independent frame buffer devices.
| |
− |
| |
− |
| |
− | FB_CARMINE_DRAM_EVAL
| |
− | Eval board timings
| |
− |
| |
− | Use timings which work on the eval card.
| |
− |
| |
− |
| |
− | CARMINE_DRAM_CUSTOM
| |
− | Custom board timings
| |
− |
| |
− | Use custom board timings.
| |
− |
| |
− | FB_AU1100
| |
− | Au1100 LCD Driver
| |
− |
| |
− | 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>.
| |
− |
| |
− |
| |
− | FB_AU1200
| |
− | Au1200 LCD Driver
| |
− |
| |
− | 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>.
| |
− |
| |
− |
| |
− | /home/landley/www/kdocs/menuconfig/drivers-video-geode-Kconfig.html
| |
− | FB_HIT
| |
− | HD64461 Frame Buffer support
| |
− |
| |
− | This is the frame buffer device driver for the Hitachi HD64461 LCD
| |
− | frame buffer card.
| |
− |
| |
− |
| |
− | FB_PMAG_AA
| |
− | PMAG-AA TURBOchannel framebuffer support
| |
− |
| |
− | Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
| |
− | used mainly in the MIPS-based DECstation series.
| |
− |
| |
− |
| |
− | FB_PMAG_BA
| |
− | PMAG-BA TURBOchannel framebuffer support
| |
− |
| |
− | Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
| |
− | used mainly in the MIPS-based DECstation series.
| |
− |
| |
− |
| |
− | FB_PMAGB_B
| |
− | PMAGB-B TURBOchannel framebuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_MAXINE
| |
− | Maxine (Personal DECstation) onboard framebuffer support
| |
− |
| |
− | Support for the onboard framebuffer (1024x768x8) in the Personal
| |
− | DECstation series (Personal DECstation 5000/20, /25, /33, /50,
| |
− | Codename "Maxine").
| |
− |
| |
− |
| |
− | FB_G364
| |
− | G364 frame buffer support
| |
− |
| |
− | The G364 driver is the framebuffer used in MIPS Magnum 4000 and
| |
− | Olivetti M700-10 systems.
| |
− |
| |
− |
| |
− | FB_68328
| |
− | Motorola 68328 native frame buffer support
| |
− |
| |
− | Say Y here if you want to support the built-in frame buffer of
| |
− | the Motorola 68328 CPU family.
| |
− |
| |
− |
| |
− | FB_PXA
| |
− | PXA LCD framebuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_PXA_PARAMETERS
| |
− | PXA LCD command line parameters
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_MBX
| |
− | 2700G LCD framebuffer support
| |
− |
| |
− | Framebuffer driver for the Intel 2700G (Marathon) Graphics
| |
− | Accelerator
| |
− |
| |
− |
| |
− | FB_MBX_DEBUG
| |
− | Enable debugging info via debugfs
| |
− |
| |
− | Enable this if you want debugging information using the debug
| |
− | filesystem (debugfs)
| |
− |
| |
− | If unsure, say N.
| |
− |
| |
− |
| |
− | FB_FSL_DIU
| |
− | Freescale DIU framebuffer support
| |
− |
| |
− | Framebuffer driver for the Freescale SoC DIU
| |
− |
| |
− |
| |
− | FB_W100
| |
− | W100 frame buffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SH_MOBILE_LCDC
| |
− | SuperH Mobile LCDC framebuffer support
| |
− |
| |
− | Frame buffer driver for the on-chip SH-Mobile LCD controller.
| |
− |
| |
− |
| |
− | FB_TMIO
| |
− | Toshiba Mobile IO FrameBuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_S3C2410
| |
− | S3C2410 LCD framebuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− | FB_S3C2410_DEBUG
| |
− | S3C2410 lcd debug messages
| |
− |
| |
− | Turn on debugging messages. Note that you can set/unset at run time
| |
− | through sysfs
| |
− |
| |
− |
| |
− | FB_SM501
| |
− | Silicon Motion SM501 framebuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− |
| |
− | FB_PNX4008_DUM
| |
− | Display Update Module support on Philips PNX4008 board
| |
− |
| |
− | Say Y here to enable support for PNX4008 Display Update Module (DUM)
| |
− |
| |
− |
| |
− | FB_PNX4008_DUM_RGB
| |
− | RGB Framebuffer support on Philips PNX4008 board
| |
− |
| |
− | Say Y here to enable support for PNX4008 RGB Framebuffer
| |
− |
| |
− |
| |
− | FB_IBM_GXT4500
| |
− | Framebuffer support for IBM GXT4500P adaptor
| |
− |
| |
− | Say Y here to enable support for the IBM GXT4500P display
| |
− | adaptor, found on some IBM System P (pSeries) machines.
| |
− |
| |
− |
| |
− | FB_PS3
| |
− | PS3 GPU framebuffer driver
| |
− |
| |
− | Include support for the virtual frame buffer in the PS3 platform.
| |
− |
| |
− |
| |
− | FB_PS3_DEFAULT_SIZE_M
| |
− | PS3 default frame buffer size (in MiB)
| |
− |
| |
− | 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");
| |
− |
| |
− |
| |
− | FB_XILINX
| |
− | Xilinx frame buffer support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_SH7760
| |
− | SH7760/SH7763/SH7720/SH7721 LCDC support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_VIRTUAL
| |
− | Virtual Frame Buffer support (ONLY FOR TESTING!)
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | XEN_FBDEV_FRONTEND
| |
− | Xen virtual frame buffer support
| |
− |
| |
− | This driver implements the front-end of the Xen virtual
| |
− | frame buffer driver. It communicates with a back-end
| |
− | in another domain.
| |
− |
| |
− |
| |
− | FB_METRONOME
| |
− | E-Ink Metronome/8track controller support
| |
− |
| |
− | 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.
| |
− |
| |
− |
| |
− | FB_MB862XX
| |
− | Fujitsu MB862xx GDC support
| |
− |
| |
− | Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
| |
− |
| |
− |
| |
− | FB_MB862XX_PCI_GDC
| |
− | Carmine/Coral-P(A) GDC
| |
− |
| |
− | This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
| |
− | PCI graphics controller devices.
| |
− |
| |
− |
| |
− | FB_MB862XX_LIME
| |
− | Lime GDC
| |
− |
| |
− | Framebuffer support for Fujitsu Lime GDC on host CPU bus.
| |
− |
| |
− |
| |
− | FB_PRE_INIT_FB
| |
− | Don't reinitialize, use bootloader's GDC/Display configuration
| |
− |
| |
− | Select this option if display contents should be inherited as set by
| |
− | the bootloader.
| |
− |
| |
− |
| |
− | FB_MX3
| |
− | MX3 Framebuffer support
| |
− |
| |
− | 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.
| |
− |
| |
− | </pre>
| |
− |
| |
− | [[Category:Flameman]]
| |
− | [[Category:Kernel]]
| |