Lines Matching +full:simple +full:- +full:framebuffer

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
34 buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
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.
73 If true, at least one selected framebuffer driver can take advantage
104 Allow generic frame-buffer functions to work on displays with 1, 2
114 (accelerated) version and the framebuffer is in system RAM.
122 version and the framebuffer is in system RAM.
130 (accelerated) version and the framebuffer is in system RAM.
136 Allow generic frame-buffer to provide get_fb_unmapped_area
140 bool "Framebuffer foreign endianness support"
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
214 terms of number of tiles in the x- and y-axis.
223 tristate "Aeroflex Gaisler framebuffer support"
229 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
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
286 This framebuffer device driver is for the ARM PrimeCell PL110
293 will be called amba-clcd.
303 hardware found in Acorn RISC PCs and other ARM-based machines. If
316 Say Y to enable the Framebuffer driver for the Cirrus Logic
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.
559 Enabling this option will implement the linux framebuffer device
562 If you enable this option, you will get a planar framebuffer device
584 tristate "TGA/SFB+ framebuffer support"
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"
645 using the EFI framebuffer as your console.
688 This is the amount of memory reserved for the framebuffer,
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
784 completely dumb framebuffer device.
787 bool "Sun XVR-2500 3DLABS Wildcat support"
793 This is the framebuffer device for the Sun XVR-2500 and similar
797 completely dumb framebuffer device.
800 bool "Sun XVR-1000 support"
806 This is the framebuffer device for the Sun XVR-1000 and similar
809 is treated as a completely dumb framebuffer device.
834 tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
850 tristate "Epson S1D13XXX framebuffer support"
856 Support for S1D13XXX framebuffer device family (currently only
874 tristate "nVidia Framebuffer Support"
901 Because fbdev-2.6 requires that drivers must be able to
947 Because fbdev-2.6 requires that drivers must be able to
987 This driver supports the on-board graphics built in to the Intel 810
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
1075 bool "DDC/I2C for Intel framebuffer support"
1080 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1139 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
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.
1190 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1212 a framebuffer device. There are both PCI and AGP versions. You
1216 https://products.amd.com/en-us/GraphicCardResult.aspx
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
1303 framebuffer device. The ATI product support page for these boards
1361 Because fbdev-2.6 requires that drivers must be able to
1370 the resulting framebuffer console has bothersome glitches, then
1434 framebuffer to avoid negative impact on the OpenChrome X server.
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
1612 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1624 This is the framebuffer driver for the Au1200/Au1300 SOCs.
1629 bool "VIA VT8500 framebuffer support"
1637 This is the framebuffer driver for VIA VT8500 integrated LCD
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
1704 bool "Maxine (Personal DECstation) onboard framebuffer support"
1710 Support for the onboard framebuffer (1024x768x8) in the Personal
1721 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1722 Olivetti M700-10 systems.
1731 Say Y here if you want to support the built-in frame buffer of
1735 tristate "PXA168/910 LCD framebuffer support"
1742 Frame buffer driver for the built-in LCD controller in the Marvell
1746 tristate "PXA LCD framebuffer support"
1754 Frame buffer driver for the built-in LCD controller in the Intel
1765 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1799 tristate "Freescale DIU framebuffer support"
1807 Framebuffer driver for the Freescale SoC DIU
1816 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1827 tristate "SuperH Mobile LCDC framebuffer support"
1837 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1840 tristate "Toshiba Mobile IO FrameBuffer support"
1847 on the Sharp SL-6000 series
1862 tristate "Samsung S3C framebuffer support"
1869 Frame buffer driver for the built-in FB controller in the Samsung
1873 These chips all have the same basic framebuffer design with the
1887 tristate "S3C2410 LCD framebuffer support"
1893 Frame buffer driver for the built-in LCD controller in the Samsung
1910 tristate "Silicon Motion SM501 framebuffer support"
1927 tristate "SMSC UFX6000/7000 USB Framebuffer support"
1936 This is a kernel framebuffer driver for SMSC UFX USB devices.
1937 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1938 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1943 tristate "Displaylink USB Framebuffer support"
1952 This is a kernel framebuffer driver for DisplayLink USB devices.
1953 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1954 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1958 tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
1971 tristate "PS3 GPU framebuffer driver"
1998 framebuffer. ML300 carries a 640*480 LCD display on the board,
2002 tristate "Goldfish Framebuffer"
2009 Framebuffer driver for Goldfish Virtual Platform
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)
2123 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2133 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
2144 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2146 ep93xx-fb.
2156 tristate "MX3 Framebuffer support"
2164 This is a framebuffer device for the i.MX31 LCD Controller. So
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.
2194 bool "Simple framebuffer support"
2200 Say Y if you want support for a simple frame-buffer.
2204 pre-allocated frame buffer surface.
2210 tristate "Solomon SSD1307 framebuffer support"
2226 tristate "Silicon Motion SM712 framebuffer support"