Lines Matching +full:secondary +full:- +full:device
1 # SPDX-License-Identifier: GPL-2.0-only
7 tristate "Support for frame buffer device drivers"
11 The frame buffer device provides an abstraction for the graphics
14 a well-defined interface, so the software doesn't need to know
15 anything about the low-level (hardware register) stuff.
20 server exists which uses the frame buffer device exclusively.
21 On several non-X86 architectures, the frame buffer device is the
24 The device is accessed through special device nodes, usually located
29 and the Framebuffer-HOWTO at
30 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
33 This enables support for native frame buffer device (fbdev) drivers.
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.
98 This is the frame buffer device driver for cards based on
105 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
122 This is the frame buffer device driver for the Acorn VIDC graphics
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
166 device, otherwise say N.
206 This is the frame buffer device driver for the builtin graphics
243 This is the frame buffer device driver for the Amiga FrameMaster
252 is based on the KS-108 lcd controller and is typically a matrix
267 This is the frame buffer device driver for the builtin graphics
271 tristate "Open Firmware frame buffer device support"
313 This is the frame buffer device driver for the Chips & Technologies
321 This is the frame buffer device driver for the Asiliant 69030 chipset
330 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
334 tristate "VGA 16-color graphics support"
344 This is the frame buffer device driver for VGA 16 color graphic
351 tristate "HP STI frame buffer device support"
360 Enabling this option will implement the linux framebuffer device
363 If you enable this option, you will get a planar framebuffer device
394 This is the frame buffer device driver for generic TGA and SFB+
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. ;-)
431 This is the frame buffer device driver for generic VESA 2.0
437 bool "EFI-based Framebuffer Support"
444 This is the EFI frame buffer device driver. If the firmware on
475 This is the frame buffer device driver for SGI Graphics Backend.
490 Say Y if you want support for SBUS or UPA based frame buffer device.
504 This is the frame buffer device driver for the BWtwo frame buffer.
511 This is the frame buffer device driver for the CGthree frame buffer.
520 This is the frame buffer device driver for the CGsix (GX, TurboGX)
530 This is the frame buffer device driver for the Creator, Creator3D,
538 This is the frame buffer device driver for the TCX 24/8bit frame
546 This is the frame buffer device driver for the CGfourteen frame
554 This is the frame buffer device driver for the P9100 card
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
577 completely dumb framebuffer device.
580 bool "Sun XVR-2500 3DLABS Wildcat support"
584 This is the framebuffer device for the Sun XVR-2500 and similar
588 completely dumb framebuffer device.
591 bool "Sun XVR-1000 support"
595 This is the framebuffer device for the Sun XVR-1000 and similar
598 is treated as a completely dumb framebuffer device.
645 Support for S1D13XXX framebuffer device family (currently only
688 Because fbdev-2.6 requires that drivers must be able to
736 Because fbdev-2.6 requires that drivers must be able to
774 This driver supports the on-board graphics built in to the Intel 810
796 monitor is recommended, but can still work with non-compliant ones.
868 If you need support for G400 secondary head, you must say Y to
870 G450/G550 secondary head and digital output are supported without
874 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
875 swap primary and secondary head outputs, or to change output mode.
876 Secondary head driver always start in 640x480 resolution and you
882 painting procedures (the secondary head does not use acceleration
885 G450/G550 hardware can display TV picture only from secondary CRTC,
895 interconnects Matrox optional devices, like MGA-TVO on G200 and
896 G400, and the secondary head DDC bus, present on G400 only.
900 second head of G400 or MGA-TVO on G200 or G400.
903 i2c-matroxfb.
912 Say Y or M here if you want to use a secondary head (meaning two
913 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
914 head is not compatible with accelerated XFree 3.3.x SVGA servers -
915 secondary head output is blanked while you are in X. With XFree
922 also load i2c-matroxfb to get it to run.
926 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
927 PAL or NTSC or to swap primary and secondary head outputs.
928 Secondary head driver also always start in 640x480 resolution, you
934 painting procedures (the secondary head does not use acceleration
948 a framebuffer device. There are both PCI and AGP versions. You
952 https://products.amd.com/en-us/GraphicCardResult.aspx
1021 Say Y here to support use of ATI's 64-bit Rage boards (or other
1023 framebuffer device. The ATI product support page for these boards
1040 framebuffer device. The ATI product support page for these boards
1102 Because fbdev-2.6 requires that drivers must be able to
1124 This is the frame buffer device driver for the SiS 300, 315, 330
1154 This is the frame buffer device driver for Graphics chips of VIA
1170 correct output device configuration.
1221 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1231 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1232 device driver with acceleration functions.
1283 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1319 This is the frame buffer device driver for the 3DLabs Permedia3
1329 This is the frame buffer device driver for the Fujitsu Carmine chip.
1380 bool "Wondermedia WM8xxx-series frame buffer support"
1390 This is the framebuffer driver for WonderMedia WM8xxx-series
1410 This is the frame buffer device driver for the Hitachi HD64461 LCD
1414 tristate "PMAG-AA TURBOchannel framebuffer support"
1418 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1419 used mainly in the MIPS-based DECstation series.
1422 tristate "PMAG-BA TURBOchannel framebuffer support"
1426 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1427 used mainly in the MIPS-based DECstation series.
1430 tristate "PMAGB-B TURBOchannel framebuffer support"
1434 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1435 in the MIPS-based DECstation series. The card is currently only
1453 Olivetti M700-10 systems.
1460 Say Y here if you want to support the built-in frame buffer of
1469 Frame buffer driver for the built-in LCD controller in the Marvell
1479 Frame buffer driver for the built-in LCD controller in the Intel
1542 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1550 Frame buffer driver for the built-in FB controller in the Samsung
1590 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1591 mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1603 Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1604 mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1675 This is a `virtual' frame buffer device. It operates on a chunk of
1678 buffer device, while it does consume precious memory. The main use
1679 of this frame buffer device is testing and debugging the frame
1697 This driver implements the front-end of the Xen virtual
1698 frame buffer driver. It communicates with a back-end
1702 tristate "E-Ink Metronome/8track controller support"
1706 This driver implements support for the E-Ink Metronome
1707 controller. The pre-release name for this device was 8track
1708 and could also have been called by some vendors as PVI-nnnn.
1716 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
1723 bool "Carmine/Coral-P(A) GDC"
1726 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
1745 Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
1756 ep93xx-fb.
1766 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
1770 This driver implements support for the E-Ink Broadsheet
1771 controller. The release name for this device was Epson S1D13521
1776 tristate "Microsoft Hyper-V Synthetic Video support"
1781 This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
1790 Say Y if you want support for a simple frame-buffer.
1794 pre-allocated frame buffer surface.
1797 through device tree, or plain old platform data.