## Video configuration#menu "Graphics support"	depends on HAS_IOMEMsource "drivers/char/agp/Kconfig"source "drivers/gpu/drm/Kconfig"config VGASTATE       tristate       default nconfig VIDEO_OUTPUT_CONTROL	tristate "Lowlevel video output switch controls"	help	  This framework adds support for low-level control of the video 	  output switch.menuconfig FB	tristate "Support for frame buffer devices"	---help---	  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.config FIRMWARE_EDID       bool "Enable firmware EDID"       depends on FB       default n       ---help---         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.config FB_DDC       tristate       depends on FB       select I2C_ALGOBIT       select I2C       default nconfig FB_BOOT_VESA_SUPPORT	bool	depends on FB	default n	---help---	  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.config FB_CFB_FILLRECT	tristate	depends on FB	default n	---help---	  Include the cfb_fillrect function for generic software rectangle	  filling. This is used by drivers that don't provide their own	  (accelerated) version.config FB_CFB_COPYAREA	tristate	depends on FB	default n	---help---	  Include the cfb_copyarea function for generic software area copying.	  This is used by drivers that don't provide their own (accelerated)	  version.config FB_CFB_IMAGEBLIT	tristate	depends on FB	default n	---help---	  Include the cfb_imageblit function for generic software image	  blitting. This is used by drivers that don't provide their own	  (accelerated) version.config FB_CFB_REV_PIXELS_IN_BYTE	bool	depends on FB	default n	---help---	  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.config FB_SYS_FILLRECT	tristate	depends on FB	default n	---help---	  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.config FB_SYS_COPYAREA	tristate	depends on FB	default n	---help---	  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.config FB_SYS_IMAGEBLIT	tristate	depends on FB	default n	---help---	  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.menuconfig FB_FOREIGN_ENDIAN	bool "Framebuffer foreign endianness support"	depends on FB	---help---	  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.choice	prompt "Choice endianness support"	depends on FB_FOREIGN_ENDIANconfig FB_BOTH_ENDIAN	bool "Support for Big- and Little-Endian framebuffers"config FB_BIG_ENDIAN	bool "Support for Big-Endian framebuffers only"config FB_LITTLE_ENDIAN	bool "Support for Little-Endian framebuffers only"endchoiceconfig FB_SYS_FOPS       tristate       depends on FB       default nconfig FB_DEFERRED_IO	bool	depends on FBconfig FB_HECUBA	tristate	depends on FB	depends on FB_DEFERRED_IOconfig FB_SVGALIB	tristate	depends on FB	default n	---help---	  Common utility functions useful to fbdev drivers of VGA-based	  cards.config FB_MACMODES       tristate       depends on FB       default nconfig FB_BACKLIGHT	bool	depends on FB	select BACKLIGHT_LCD_SUPPORT	select BACKLIGHT_CLASS_DEVICE	default nconfig FB_MODE_HELPERS        bool "Enable Video Mode Handling Helpers"        depends on FB	default n	---help---	  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.config FB_TILEBLITTING       bool "Enable Tile Blitting Support"       depends on FB       default n       ---help---         This enables tile blitting.  Tile blitting is a drawing technique	 where the screen is divided into rectangular sections (tiles), whereas	 the standard blitting divides the screen into pixels. Because the	 default drawing element is a tile, drawing functions will be passed	 parameters in terms of number of tiles instead of number of pixels.	 For example, to draw a single character, instead of using bitmaps,	 an index to an array of bitmaps will be used.  To clear or move a	 rectangular section of a screen, the rectangle will be described in	 terms of number of tiles in the x- and y-axis.	 This is particularly important to one driver, matroxfb.  If	 unsure, say N.comment "Frame buffer hardware drivers"	depends on FBconfig FB_CIRRUS	tristate "Cirrus Logic support"	depends on FB && (ZORRO || PCI)	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	---help---	  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.config FB_PM2	tristate "Permedia2 support"	depends on FB && ((AMIGA && BROKEN) || PCI)	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.config FB_PM2_FIFO_DISCONNECT	bool "enable FIFO disconnect feature"	depends on FB_PM2 && PCI	help	  Support the Permedia2 FIFO disconnect feature.config FB_ARMCLCD	tristate "ARM PrimeCell PL110 support"	depends on FB && ARM && ARM_AMBA	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.choice	depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)	prompt "LCD Panel"	default FB_ARMCLCD_SHARP_LQ035Q7DB02config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT	bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"	help	  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.config FB_ARMCLCD_SHARP_LQ057Q3DC02	bool "LogicPD LCD 5.7\" QVGA"	help	  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.config FB_ARMCLCD_SHARP_LQ64D343	bool "LogicPD LCD 6.4\" VGA"	help	  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.config FB_ARMCLCD_SHARP_LQ10D368	bool "LogicPD LCD 10.4\" VGA"	help	  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.config FB_ARMCLCD_SHARP_LQ121S1DG41	bool "LogicPD LCD 12.1\" SVGA"	help	  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.config FB_ARMCLCD_AUO_A070VW01_WIDE	bool "AU Optronics A070VW01 LCD 7.0\" WIDE"	help	  This is an implementation of the AU Optronics, a 7.0"	  WIDE Color.  The native resolution is 234x480.config FB_ARMCLCD_HITACHI	bool "Hitachi Wide Screen 800x480"	help	  This is an implementation of the Hitachi 800x480.endchoiceconfig FB_ACORN	bool "Acorn VIDC support"	depends on (FB = y) && ARM && ARCH_ACORN	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.config FB_CLPS711X	bool "CLPS711X LCD support"	depends on (FB = y) && ARM && ARCH_CLPS711X	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  Say Y to enable the Framebuffer driver for the CLPS7111 and	  EP7212 processors.config FB_SA1100	bool "SA-1100 LCD support"	depends on (FB = y) && ARM && ARCH_SA1100	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.config FB_IMX	tristate "Motorola i.MX LCD support"	depends on FB && ARM && ARCH_IMX	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLITconfig FB_CYBER2000	tristate "CyberPro 2000/2010/5000 support"	depends on FB && PCI && (BROKEN || !SPARC64)	select FB_CFB_FILLRECT	select FB_CFB_COPYAREA	select FB_CFB_IMAGEBLIT	help	  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.config FB_APOLLO	bool	depends on (FB = y) && APOLLO	default y