Lines Matching +full:ati +full:- +full:mode
1 # SPDX-License-Identifier: GPL-2.0-only
20 a well-defined interface, so the software doesn't need to know
21 anything about the low-level (hardware register) stuff.
27 On several non-X86 architectures, the frame buffer device is the
35 and the Framebuffer-HOWTO at
36 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
40 are compiling a kernel for a non-x86 architecture.
46 device-aware may cause unexpected results. If unsure, say N.
104 Allow generic frame-buffer functions to work on displays with 1, 2
136 Allow generic frame-buffer to provide get_fb_unmapped_area
144 non-native endianness (e.g. Little-Endian framebuffer on a
145 Big-Endian machine). Most probably you don't have such hardware,
153 bool "Support for Big- and Little-Endian framebuffers"
156 bool "Support for Big-Endian framebuffers only"
159 bool "Support for Little-Endian framebuffers only"
180 Common utility functions useful to fbdev drivers of VGA-based
193 bool "Enable Video Mode Handling Helpers"
214 terms of number of tiles in the x- and y-axis.
241 If you have a PCI-based system, this enables support for these
242 chips: GD-543x, GD-544x, GD-5480.
263 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
293 will be called amba-clcd.
303 hardware found in Acorn RISC PCs and other ARM-based machines. If
320 bool "SA-1100 LCD support"
326 This is a framebuffer device for the SA-1100 LCD Controller.
327 See <http://www.linux-fbdev.org/> for information on framebuffer
330 If you plan to use the LCD display with your SA-1100 system, say
445 is based on the KS-108 lcd controller and is typically a matrix
531 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
535 tristate "VGA 16-color graphics support"
558 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
592 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
593 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
594 TURBOchannel cards, also known as PMAGD-A, -B and -C.
596 Due to hardware limitations ZLX-E2 and E3 cards are not supported
600 you manage to get it going. ;-)
636 bool "EFI-based Framebuffer Support"
770 This is the frame buffer device driver for the SBUS-based Sun ZX
774 bool "Sun XVR-500 3DLABS Wildcat support"
780 This is the framebuffer device for the Sun XVR-500 and similar
787 bool "Sun XVR-2500 3DLABS Wildcat support"
793 This is the framebuffer device for the Sun XVR-2500 and similar
800 bool "Sun XVR-1000 support"
806 This is the framebuffer device for the Sun XVR-1000 and similar
899 allowing for robust video mode handling and switching.
901 Because fbdev-2.6 requires that drivers must be able to
902 independently validate video mode parameters, you should say Y
945 allowing for robust video mode handling and switching.
947 Because fbdev-2.6 requires that drivers must be able to
948 independently validate video mode parameters, you should say Y
987 This driver supports the on-board graphics built in to the Intel 810
1002 per video mode. Since the GTF allows nondiscrete timings
1009 monitor is recommended, but can still work with non-compliant ones.
1055 This driver supports the on-board graphics built in to the Intel
1080 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1138 The driver starts in monitor mode. You must use the matroxset tool
1139 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1140 swap primary and secondary head outputs, or to change output mode.
1160 interconnects Matrox optional devices, like MGA-TVO on G200 and
1165 second head of G400 or MGA-TVO on G200 or G400.
1168 i2c-matroxfb.
1177 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1178 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1186 also load i2c-matroxfb to get it to run.
1188 The driver starts in monitor mode and you must use the matroxset
1190 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1202 tristate "ATI Radeon display support"
1211 Choose this option if you want to use an ATI Radeon graphics card as
1213 don't need to choose this to run the Radeon in plain VGA mode.
1216 https://products.amd.com/en-us/GraphicCardResult.aspx
1219 bool "DDC/I2C for ATI Radeon support"
1242 tristate "ATI Rage128 display support"
1250 This driver supports graphics boards with the ATI Rage128 chips.
1265 tristate "ATI Mach64 display support" if PCI || ATARI
1273 This driver supports graphics boards with the ATI Mach64 chips.
1284 Say Y here to support use of ATI's 64-bit Rage boards (or other
1286 framebuffer device. The ATI product support page for these boards
1287 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1293 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1301 Say Y here to support use of the ATI Mach64 Graphics Expression
1303 framebuffer device. The ATI product support page for these boards
1305 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1359 allowing for robust video mode handling and switching.
1361 Because fbdev-2.6 requires that drivers must be able to
1362 independently validate video mode parameters, you should say Y
1478 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1488 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1641 bool "Wondermedia WM8xxx-series frame buffer support"
1649 This is the framebuffer driver for WonderMedia WM8xxx-series
1673 tristate "PMAG-AA TURBOchannel framebuffer support"
1679 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1680 used mainly in the MIPS-based DECstation series.
1683 tristate "PMAG-BA TURBOchannel framebuffer support"
1689 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1690 used mainly in the MIPS-based DECstation series.
1693 tristate "PMAGB-B TURBOchannel framebuffer support"
1699 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1700 in the MIPS-based DECstation series. The card is currently only
1701 supported in 1280x1024x8 mode.
1722 Olivetti M700-10 systems.
1731 Say Y here if you want to support the built-in frame buffer of
1742 Frame buffer driver for the built-in LCD controller in the Marvell
1754 Frame buffer driver for the built-in LCD controller in the Intel
1816 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1837 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1847 on the Sharp SL-6000 series
1869 Frame buffer driver for the built-in FB controller in the Samsung
1893 Frame buffer driver for the built-in LCD controller in the Samsung
1937 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1938 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1953 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1954 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
2031 tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
2042 found on DA8xx/OMAP-L1xx/AM335x SoCs.
2079 This driver implements the front-end of the Xen virtual
2080 frame buffer driver. It communicates with a back-end
2084 tristate "E-Ink Metronome/8track controller support"
2092 This driver implements support for the E-Ink Metronome
2093 controller. The pre-release name for this device was 8track
2094 and could also have been called by some vendors as PVI-nnnn.
2104 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2111 bool "Carmine/Coral-P(A) GDC"
2114 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2133 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2146 ep93xx-fb.
2169 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2177 This driver implements support for the E-Ink Broadsheet
2183 tristate "Microsoft Hyper-V Synthetic Video support"
2191 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
2200 Say Y if you want support for a simple frame-buffer.
2204 pre-allocated frame buffer surface.