Lines Matching +full:ati +full:- +full:mode

1 # SPDX-License-Identifier: GPL-2.0-only
14 a well-defined interface, so the software doesn't need to know
15 anything about the low-level (hardware register) stuff.
21 On several non-X86 architectures, the frame buffer device is the
29 and the Framebuffer-HOWTO at
30 <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.
57 Common utility functions useful to fbdev drivers of VGA-based
82 If you have a PCI-based system, this enables support for these
83 chips: GD-543x, GD-544x, GD-5480.
105 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
123 hardware found in Acorn RISC PCs and other ARM-based machines. If
138 bool "SA-1100 LCD support"
142 This is a framebuffer device for the SA-1100 LCD Controller.
143 See <http://www.linux-fbdev.org/> for information on framebuffer
146 If you plan to use the LCD display with your SA-1100 system, say
252 is based on the KS-108 lcd controller and is typically a matrix
330 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
334 tristate "VGA 16-color graphics support"
395 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
396 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
397 TURBOchannel cards, also known as PMAGD-A, -B and -C.
399 Due to hardware limitations ZLX-E2 and E3 cards are not supported
403 you manage to get it going. ;-)
437 bool "EFI-based Framebuffer Support"
562 This is the frame buffer device driver for the SBUS-based Sun ZX
566 bool "Sun XVR-500 3DLABS Wildcat support"
573 This is the framebuffer device for the Sun XVR-500 and similar
580 bool "Sun XVR-2500 3DLABS Wildcat support"
584 This is the framebuffer device for the Sun XVR-2500 and similar
591 bool "Sun XVR-1000 support"
595 This is the framebuffer device for the Sun XVR-1000 and similar
686 allowing for robust video mode handling and switching.
688 Because fbdev-2.6 requires that drivers must be able to
689 independently validate video mode parameters, you should say Y
733 allowing for robust video mode handling and switching.
735 Because fbdev-2.6 requires that drivers must be able to
736 independently validate video mode parameters, you should say Y
771 This driver supports the on-board graphics built in to the Intel 810
786 per video mode. Since the GTF allows nondiscrete timings
793 monitor is recommended, but can still work with non-compliant ones.
870 The driver starts in monitor mode. You must use the matroxset tool
871 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
872 swap primary and secondary head outputs, or to change output mode.
892 interconnects Matrox optional devices, like MGA-TVO on G200 and
897 second head of G400 or MGA-TVO on G200 or G400.
900 i2c-matroxfb.
910 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
911 head is not compatible with accelerated XFree 3.3.x SVGA servers -
919 also load i2c-matroxfb to get it to run.
921 The driver starts in monitor mode and you must use the matroxset
923 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
935 tristate "ATI Radeon display support"
945 Choose this option if you want to use an ATI Radeon graphics card as
947 don't need to choose this to run the Radeon in plain VGA mode.
950 https://products.amd.com/en-us/GraphicCardResult.aspx
953 bool "DDC/I2C for ATI Radeon support"
976 tristate "ATI Rage128 display support"
982 This driver supports graphics boards with the ATI Rage128 chips.
997 tristate "ATI Mach64 display support" if PCI || ATARI
1007 This driver supports graphics boards with the ATI Mach64 chips.
1017 Say Y here to support use of ATI's 64-bit Rage boards (or other
1019 framebuffer device. The ATI product support page for these boards
1020 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1026 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1034 Say Y here to support use of the ATI Mach64 Graphics Expression
1036 framebuffer device. The ATI product support page for these boards
1038 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1094 allowing for robust video mode handling and switching.
1096 Because fbdev-2.6 requires that drivers must be able to
1097 independently validate video mode parameters, you should say Y
1215 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1225 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1374 bool "Wondermedia WM8xxx-series frame buffer support"
1384 This is the framebuffer driver for WonderMedia WM8xxx-series
1408 tristate "PMAG-AA TURBOchannel framebuffer support"
1412 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1413 used mainly in the MIPS-based DECstation series.
1416 tristate "PMAG-BA TURBOchannel framebuffer support"
1420 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1421 used mainly in the MIPS-based DECstation series.
1424 tristate "PMAGB-B TURBOchannel framebuffer support"
1428 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1429 in the MIPS-based DECstation series. The card is currently only
1430 supported in 1280x1024x8 mode.
1447 Olivetti M700-10 systems.
1454 Say Y here if you want to support the built-in frame buffer of
1463 Frame buffer driver for the built-in LCD controller in the Marvell
1473 Frame buffer driver for the built-in LCD controller in the Intel
1535 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1543 Frame buffer driver for the built-in FB controller in the Samsung
1583 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1584 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1596 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1597 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1690 This driver implements the front-end of the Xen virtual
1691 frame buffer driver. It communicates with a back-end
1695 tristate "E-Ink Metronome/8track controller support"
1699 This driver implements support for the E-Ink Metronome
1700 controller. The pre-release name for this device was 8track
1701 and could also have been called by some vendors as PVI-nnnn.
1709 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
1716 bool "Carmine/Coral-P(A) GDC"
1719 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
1738 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
1749 ep93xx-fb.
1759 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
1763 This driver implements support for the E-Ink Broadsheet
1769 tristate "Microsoft Hyper-V Synthetic Video support"
1774 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
1783 Say Y if you want support for a simple frame-buffer.
1787 pre-allocated frame buffer surface.