xref: /linux-6.15/drivers/video/fbdev/Kconfig (revision d9f25b59)
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# fbdev configuration
4#
5
6menuconfig FB
7	tristate "Support for frame buffer device drivers"
8	select FB_CORE
9	select FB_NOTIFY
10	help
11	  The frame buffer device provides an abstraction for the graphics
12	  hardware. It represents the frame buffer of some video hardware and
13	  allows application software to access the graphics hardware through
14	  a well-defined interface, so the software doesn't need to know
15	  anything about the low-level (hardware register) stuff.
16
17	  Frame buffer devices work identically across the different
18	  architectures supported by Linux and make the implementation of
19	  application programs easier and more portable; at this point, an X
20	  server exists which uses the frame buffer device exclusively.
21	  On several non-X86 architectures, the frame buffer device is the
22	  only way to use the graphics hardware.
23
24	  The device is accessed through special device nodes, usually located
25	  in the /dev directory, i.e. /dev/fb*.
26
27	  You need an utility program called fbset to make full use of frame
28	  buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
29	  and the Framebuffer-HOWTO at
30	  <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
31	  information.
32
33	  This enables support for native frame buffer device (fbdev) drivers.
34
35	  The DRM subsystem provides support for emulated frame buffer devices
36	  on top of KMS drivers, but this option allows legacy fbdev drivers to
37	  be enabled as well.
38
39	  Say Y here and to the driver for your graphics board below if you
40	  are compiling a kernel for a non-x86 architecture.
41
42	  If you are compiling for the x86 architecture, you can say Y if you
43	  want to play with it, but it is not essential. Please note that
44	  running graphical applications that directly touch the hardware
45	  (e.g. an accelerated X server) and that are not frame buffer
46	  device-aware may cause unexpected results. If unsure, say N.
47
48config FB_HECUBA
49	tristate
50	depends on FB
51	select FB_SYSMEM_HELPERS_DEFERRED
52
53config FB_SVGALIB
54	tristate
55	depends on FB
56	help
57	  Common utility functions useful to fbdev drivers of VGA-based
58	  cards.
59
60config FB_MACMODES
61	tristate
62	depends on FB
63
64config FB_GRVGA
65	tristate "Aeroflex Gaisler framebuffer support"
66	depends on FB && SPARC
67	select FB_IOMEM_HELPERS
68	help
69	  This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
70
71config FB_CIRRUS
72	tristate "Cirrus Logic support"
73	depends on FB && (ZORRO || PCI)
74	select FB_CFB_FILLRECT
75	select FB_CFB_COPYAREA
76	select FB_CFB_IMAGEBLIT
77	select FB_IOMEM_FOPS
78	select VIDEO_NOMODESET
79	help
80	  This enables support for Cirrus Logic GD542x/543x based boards on
81	  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
82
83	  If you have a PCI-based system, this enables support for these
84	  chips: GD-543x, GD-544x, GD-5480.
85
86	  Please read the file <file:Documentation/fb/cirrusfb.rst>.
87
88	  Say N unless you have such a graphics board or plan to get one
89	  before you next recompile the kernel.
90
91config FB_PM2
92	tristate "Permedia2 support"
93	depends on FB && ((AMIGA && BROKEN) || PCI)
94	select FB_CFB_FILLRECT
95	select FB_CFB_COPYAREA
96	select FB_CFB_IMAGEBLIT
97	select FB_IOMEM_FOPS
98	select VIDEO_NOMODESET
99	help
100	  This is the frame buffer device driver for cards based on
101	  the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
102	  The driver was tested on the following cards:
103		Diamond FireGL 1000 PRO AGP
104		ELSA Gloria Synergy PCI
105		Appian Jeronimo PRO (both heads) PCI
106		3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
107		Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
108		ASK Graphic Blaster Exxtreme AGP
109
110	  To compile this driver as a module, choose M here: the
111	  module will be called pm2fb.
112
113config FB_PM2_FIFO_DISCONNECT
114	bool "enable FIFO disconnect feature"
115	depends on FB_PM2 && PCI
116	help
117	  Support the Permedia2 FIFO disconnect feature.
118
119config FB_ARMCLCD
120	tristate "ARM PrimeCell PL110 support"
121	depends on ARM || ARM64 || COMPILE_TEST
122	depends on FB && ARM_AMBA && HAS_IOMEM
123	select FB_IOMEM_HELPERS
124	select FB_MODE_HELPERS if OF
125	select VIDEOMODE_HELPERS if OF
126	select BACKLIGHT_CLASS_DEVICE if OF
127	help
128	  This framebuffer device driver is for the ARM PrimeCell PL110
129	  Colour LCD controller.  ARM PrimeCells provide the building
130	  blocks for System on a Chip devices.
131
132	  If you want to compile this as a module (=code which can be
133	  inserted into and removed from the running kernel), say M
134	  here and read <file:Documentation/kbuild/modules.rst>.  The module
135	  will be called amba-clcd.
136
137config FB_ACORN
138	bool "Acorn VIDC support"
139	depends on (FB = y) && ARM && ARCH_ACORN
140	select FB_IOMEM_HELPERS
141	help
142	  This is the frame buffer device driver for the Acorn VIDC graphics
143	  hardware found in Acorn RISC PCs and other ARM-based machines.  If
144	  unsure, say N.
145
146config FB_CLPS711X
147	tristate "CLPS711X LCD support"
148	depends on FB && (ARCH_CLPS711X || COMPILE_TEST)
149	select FB_MODE_HELPERS
150	select FB_SYS_FILLRECT
151	select FB_SYS_COPYAREA
152	select FB_SYS_IMAGEBLIT
153	select LCD_CLASS_DEVICE
154	select VIDEOMODE_HELPERS
155	help
156	  Say Y to enable the Framebuffer driver for the Cirrus Logic
157	  CLPS711X CPUs.
158
159config FB_SA1100
160	bool "SA-1100 LCD support"
161	depends on (FB = y) && ARM && ARCH_SA1100
162	select FB_IOMEM_HELPERS
163	help
164	  This is a framebuffer device for the SA-1100 LCD Controller.
165	  See <http://www.linux-fbdev.org/> for information on framebuffer
166	  devices.
167
168	  If you plan to use the LCD display with your SA-1100 system, say
169	  Y here.
170
171config FB_IMX
172	tristate "Freescale i.MX1/21/25/27 LCD support"
173	depends on FB && HAVE_CLK && HAS_IOMEM
174	depends on ARCH_MXC || COMPILE_TEST
175	select LCD_CLASS_DEVICE
176	select FB_IOMEM_HELPERS
177	select FB_MODE_HELPERS
178	select VIDEOMODE_HELPERS
179
180config FB_CYBER2000
181	tristate "CyberPro 2000/2010/5000 support"
182	depends on FB && PCI && (BROKEN || !SPARC64)
183	select FB_CFB_FILLRECT
184	select FB_CFB_COPYAREA
185	select FB_CFB_IMAGEBLIT
186	select FB_IOMEM_FOPS
187	select VIDEO_NOMODESET
188	help
189	  This enables support for the Integraphics CyberPro 20x0 and 5000
190	  VGA chips used in the Rebel.com Netwinder and other machines.
191	  Say Y if you have a NetWinder or a graphics card containing this
192	  device, otherwise say N.
193
194config FB_CYBER2000_DDC
195	bool "DDC for CyberPro support"
196	depends on FB_CYBER2000
197	select FB_DDC
198	default y
199	help
200	  Say Y here if you want DDC support for your CyberPro graphics
201	  card. This is only I2C bus support, driver does not use EDID.
202
203config FB_CYBER2000_I2C
204	bool "CyberPro 2000/2010/5000 I2C support"
205	depends on FB_CYBER2000 && I2C && ARCH_NETWINDER
206	depends on I2C=y || FB_CYBER2000=m
207	select I2C_ALGOBIT
208	help
209	  Enable support for the I2C video decoder interface on the
210	  Integraphics CyberPro 20x0 and 5000 VGA chips.  This is used
211	  on the Netwinder machines for the SAA7111 video capture.
212
213config FB_APOLLO
214	bool
215	depends on (FB = y) && APOLLO
216	default y
217	select FB_CFB_FILLRECT
218	select FB_CFB_IMAGEBLIT
219	select FB_IOMEM_FOPS
220
221config FB_Q40
222	bool
223	depends on (FB = y) && Q40
224	default y
225	select FB_IOMEM_HELPERS
226
227config FB_AMIGA
228	tristate "Amiga native chipset support"
229	depends on FB && AMIGA
230	select FB_IOMEM_FOPS
231	help
232	  This is the frame buffer device driver for the builtin graphics
233	  chipset found in Amigas.
234
235	  To compile this driver as a module, choose M here: the
236	  module will be called amifb.
237
238config FB_AMIGA_OCS
239	bool "Amiga OCS chipset support"
240	depends on FB_AMIGA
241	help
242	  This enables support for the original Agnus and Denise video chips,
243	  found in the Amiga 1000 and most A500's and A2000's. If you intend
244	  to run Linux on any of these systems, say Y; otherwise say N.
245
246config FB_AMIGA_ECS
247	bool "Amiga ECS chipset support"
248	depends on FB_AMIGA
249	help
250	  This enables support for the Enhanced Chip Set, found in later
251	  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
252	  you intend to run Linux on any of these systems, say Y; otherwise
253	  say N.
254
255config FB_AMIGA_AGA
256	bool "Amiga AGA chipset support"
257	depends on FB_AMIGA
258	help
259	  This enables support for the Advanced Graphics Architecture (also
260	  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
261	  and CD32. If you intend to run Linux on any of these systems, say Y;
262	  otherwise say N.
263
264config FB_FM2
265	bool "Amiga FrameMaster II/Rainbow II support"
266	depends on (FB = y) && ZORRO
267	select FB_IOMEM_HELPERS
268	help
269	  This is the frame buffer device driver for the Amiga FrameMaster
270	  card from BSC (exhibited 1992 but not shipped as a CBM product).
271
272config FB_ARC
273	tristate "Arc Monochrome LCD board support"
274	depends on FB && (X86 || COMPILE_TEST)
275	select FB_SYS_FILLRECT
276	select FB_SYS_COPYAREA
277	select FB_SYS_IMAGEBLIT
278	select FB_SYS_FOPS
279	help
280	  This enables support for the Arc Monochrome LCD board. The board
281	  is based on the KS-108 lcd controller and is typically a matrix
282	  of 2*n chips. This driver was tested with a 128x64 panel. This
283	  driver supports it for use with x86 SBCs through a 16 bit GPIO
284	  interface (8 bit data, 8 bit control). If you anticipate using
285	  this driver, say Y or M; otherwise say N. You must specify the
286	  GPIO IO address to be used for setting control and data.
287
288config FB_ATARI
289	bool "Atari native chipset support"
290	depends on (FB = y) && ATARI
291	select FB_CFB_FILLRECT
292	select FB_CFB_COPYAREA
293	select FB_CFB_IMAGEBLIT
294	select FB_IOMEM_FOPS
295	help
296	  This is the frame buffer device driver for the builtin graphics
297	  chipset found in Ataris.
298
299config FB_OF
300	tristate "Open Firmware frame buffer device support"
301	depends on FB && PPC && (!PPC_PSERIES || PCI)
302	depends on !DRM_OFDRM
303	select APERTURE_HELPERS
304	select FB_IOMEM_HELPERS
305	select FB_MACMODES
306	help
307	  Say Y if you want support with Open Firmware for your graphics
308	  board.
309
310config FB_CONTROL
311	bool "Apple \"control\" display support"
312	depends on (FB = y) && ((PPC_PMAC && PPC32) || COMPILE_TEST)
313	select FB_IOMEM_HELPERS
314	select FB_MACMODES
315	help
316	  This driver supports a frame buffer for the graphics adapter in the
317	  Power Macintosh 7300 and others.
318
319config FB_PLATINUM
320	bool "Apple \"platinum\" display support"
321	depends on (FB = y) && PPC_PMAC && PPC32
322	select FB_IOMEM_HELPERS
323	select FB_MACMODES
324	help
325	  This driver supports a frame buffer for the "platinum" graphics
326	  adapter in some Power Macintoshes.
327
328config FB_VALKYRIE
329	bool "Apple \"valkyrie\" display support"
330	depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
331	select FB_IOMEM_HELPERS
332	select FB_MACMODES
333	help
334	  This driver supports a frame buffer for the "valkyrie" graphics
335	  adapter in some Power Macintoshes.
336
337config FB_CT65550
338	bool "Chips 65550 display support"
339	depends on (FB = y) && PPC32 && PCI
340	select FB_IOMEM_HELPERS
341	select VIDEO_NOMODESET
342	help
343	  This is the frame buffer device driver for the Chips & Technologies
344	  65550 graphics chip in PowerBooks.
345
346config FB_ASILIANT
347	bool "Asiliant (Chips) 69000 display support"
348	depends on (FB = y) && PCI
349	select FB_IOMEM_HELPERS
350	select VIDEO_NOMODESET
351	help
352	  This is the frame buffer device driver for the Asiliant 69030 chipset
353
354config FB_IMSTT
355	bool "IMS Twin Turbo display support"
356	depends on (FB = y) && PCI
357	select FB_CFB_IMAGEBLIT
358	select FB_IOMEM_FOPS
359	select FB_MACMODES if PPC_PMAC
360	select VIDEO_NOMODESET
361	help
362	  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
363	  many Macintosh and compatible computers.
364
365config FB_VGA16
366	tristate "VGA 16-color graphics support"
367	depends on FB && X86
368	select APERTURE_HELPERS
369	select FB_CFB_FILLRECT
370	select FB_CFB_COPYAREA
371	select FB_CFB_IMAGEBLIT
372	select FB_IOMEM_FOPS
373	select VGASTATE
374	select FONT_8x16 if FRAMEBUFFER_CONSOLE
375	help
376	  This is the frame buffer device driver for VGA 16 color graphic
377	  cards. Say Y if you have such a card.
378
379	  To compile this driver as a module, choose M here: the
380	  module will be called vga16fb.
381
382config FB_STI
383	tristate "HP STI frame buffer device support"
384	depends on FB && PARISC
385	select FB_CFB_FILLRECT
386	select FB_CFB_COPYAREA
387	select FB_CFB_IMAGEBLIT
388	select FB_IOMEM_FOPS
389	select STI_CORE
390	default y
391	help
392	  Enabling this option will implement the linux framebuffer device
393	  using calls to the STI BIOS routines for initialisation.
394
395	  If you enable this option, you will get a planar framebuffer device
396	  /dev/fb which will work on the most common HP graphic cards of the
397	  NGLE family, including the artist chips (in the 7xx and Bxxx series),
398	  HCRX, HCRX24, CRX, CRX24 and VisEG series.
399
400	  It is safe to enable this option, so you should probably say "Y".
401
402config FB_MAC
403	bool "Generic Macintosh display support"
404	depends on (FB = y) && MAC
405	select FB_IOMEM_HELPERS
406	select FB_MACMODES
407
408config FB_HP300
409	bool
410	depends on (FB = y) && DIO
411	select FB_CFB_IMAGEBLIT
412	select FB_IOMEM_FOPS
413	default y
414
415config FB_TGA
416	tristate "TGA/SFB+ framebuffer support"
417	depends on FB
418	depends on PCI || TC
419	depends on ALPHA || TC
420	select BITREVERSE
421	select FB_CFB_FILLRECT
422	select FB_CFB_COPYAREA
423	select FB_CFB_IMAGEBLIT
424	select FB_IOMEM_FOPS
425	select VIDEO_NOMODESET
426	help
427	  This is the frame buffer device driver for generic TGA and SFB+
428	  graphic cards.  These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
429	  also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
430	  TURBOchannel cards, also known as PMAGD-A, -B and -C.
431
432	  Due to hardware limitations ZLX-E2 and E3 cards are not supported
433	  for DECstation 5000/200 systems.  Additionally due to firmware
434	  limitations these cards may cause troubles with booting DECstation
435	  5000/240 and /260 systems, but are fully supported under Linux if
436	  you manage to get it going. ;-)
437
438	  Say Y if you have one of those.
439
440config FB_UVESA
441	tristate "Userspace VESA VGA graphics support"
442	depends on FB && CONNECTOR
443	depends on !UML
444	select FB_IOMEM_HELPERS
445	select FB_MODE_HELPERS
446	help
447	  This is the frame buffer driver for generic VBE 2.0 compliant
448	  graphic cards. It can also take advantage of VBE 3.0 features,
449	  such as refresh rate adjustment.
450
451	  This driver generally provides more features than vesafb but
452	  requires a userspace helper application called 'v86d'. See
453	  <file:Documentation/fb/uvesafb.rst> for more information.
454
455	  If unsure, say N.
456
457config FB_VESA
458	bool "VESA VGA graphics support"
459	depends on (FB = y) && X86
460	select APERTURE_HELPERS
461	select FB_IOMEM_HELPERS
462	select SYSFB
463	help
464	  This is the frame buffer device driver for generic VESA 2.0
465	  compliant graphic cards. The older VESA 1.2 cards are not supported.
466	  You will get a boot time penguin logo at no additional cost. Please
467	  read <file:Documentation/fb/vesafb.rst>. If unsure, say Y.
468
469config FB_EFI
470	bool "EFI-based Framebuffer Support"
471	depends on (FB = y) && EFI
472	select APERTURE_HELPERS
473	select DRM_PANEL_ORIENTATION_QUIRKS
474	select FB_IOMEM_HELPERS
475	select SYSFB
476	help
477	  This is the EFI frame buffer device driver. If the firmware on
478	  your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
479	  using the EFI framebuffer as your console.
480
481config FB_N411
482	tristate "N411 Apollo/Hecuba devkit support"
483	depends on FB && X86 && MMU
484	select FB_HECUBA
485	help
486	  This enables support for the Apollo display controller in its
487	  Hecuba form using the n411 devkit.
488
489config FB_HGA
490	tristate "Hercules mono graphics support"
491	depends on FB && X86
492	select FB_IOMEM_FOPS
493	help
494	  Say Y here if you have a Hercules mono graphics card.
495
496	  To compile this driver as a module, choose M here: the
497	  module will be called hgafb.
498
499	  As this card technology is at least 25 years old,
500	  most people will answer N here.
501
502config FB_GBE
503	bool "SGI Graphics Backend frame buffer support"
504	depends on (FB = y) && HAS_IOMEM
505	depends on SGI_IP32 || COMPILE_TEST
506	select FB_IOMEM_HELPERS
507	help
508	  This is the frame buffer device driver for SGI Graphics Backend.
509	  This chip is used in SGI O2 and Visual Workstation 320/540.
510
511config FB_GBE_MEM
512	int "Video memory size in MB"
513	depends on FB_GBE
514	default 4
515	help
516	  This is the amount of memory reserved for the framebuffer,
517	  which can be any value between 1MB and 8MB.
518
519config FB_SBUS
520	bool "SBUS and UPA framebuffers"
521	depends on (FB = y) && SPARC
522	help
523	  Say Y if you want support for SBUS or UPA based frame buffer device.
524
525config FB_SBUS_HELPERS
526	bool
527	select FB_CFB_COPYAREA
528	select FB_CFB_FILLRECT
529	select FB_CFB_IMAGEBLIT
530
531config FB_BW2
532	bool "BWtwo support"
533	depends on (FB = y) && (SPARC && FB_SBUS)
534	select FB_SBUS_HELPERS
535	help
536	  This is the frame buffer device driver for the BWtwo frame buffer.
537
538config FB_CG3
539	bool "CGthree support"
540	depends on (FB = y) && (SPARC && FB_SBUS)
541	select FB_SBUS_HELPERS
542	help
543	  This is the frame buffer device driver for the CGthree frame buffer.
544
545config FB_CG6
546	bool "CGsix (GX,TurboGX) support"
547	depends on (FB = y) && (SPARC && FB_SBUS)
548	select FB_CFB_COPYAREA
549	select FB_CFB_IMAGEBLIT
550	help
551	  This is the frame buffer device driver for the CGsix (GX, TurboGX)
552	  frame buffer.
553
554config FB_FFB
555	bool "Creator/Creator3D/Elite3D support"
556	depends on FB_SBUS && SPARC64
557	select FB_CFB_COPYAREA
558	select FB_CFB_IMAGEBLIT
559	help
560	  This is the frame buffer device driver for the Creator, Creator3D,
561	  and Elite3D graphics boards.
562
563config FB_TCX
564	bool "TCX (SS4/SS5 only) support"
565	depends on FB_SBUS
566	select FB_SBUS_HELPERS
567	help
568	  This is the frame buffer device driver for the TCX 24/8bit frame
569	  buffer.
570
571config FB_CG14
572	bool "CGfourteen (SX) support"
573	depends on FB_SBUS
574	select FB_SBUS_HELPERS
575	help
576	  This is the frame buffer device driver for the CGfourteen frame
577	  buffer on Desktop SPARCsystems with the SX graphics option.
578
579config FB_P9100
580	bool "P9100 (Sparcbook 3 only) support"
581	depends on FB_SBUS
582	select FB_SBUS_HELPERS
583	help
584	  This is the frame buffer device driver for the P9100 card
585	  supported on Sparcbook 3 machines.
586
587config FB_LEO
588	bool "Leo (ZX) support"
589	depends on FB_SBUS
590	select FB_SBUS_HELPERS
591	help
592	  This is the frame buffer device driver for the SBUS-based Sun ZX
593	  (leo) frame buffer cards.
594
595config FB_XVR500
596	bool "Sun XVR-500 3DLABS Wildcat support"
597	depends on (FB = y) && PCI && SPARC64
598	select FB_CFB_FILLRECT
599	select FB_CFB_COPYAREA
600	select FB_CFB_IMAGEBLIT
601	select FB_IOMEM_FOPS
602	select VIDEO_NOMODESET
603	help
604	  This is the framebuffer device for the Sun XVR-500 and similar
605	  graphics cards based upon the 3DLABS Wildcat chipset.  The driver
606	  only works on sparc64 systems where the system firmware has
607	  mostly initialized the card already.  It is treated as a
608	  completely dumb framebuffer device.
609
610config FB_XVR2500
611	bool "Sun XVR-2500 3DLABS Wildcat support"
612	depends on (FB = y) && PCI && SPARC64
613	select FB_IOMEM_HELPERS
614	select VIDEO_NOMODESET
615	help
616	  This is the framebuffer device for the Sun XVR-2500 and similar
617	  graphics cards based upon the 3DLABS Wildcat chipset.  The driver
618	  only works on sparc64 systems where the system firmware has
619	  mostly initialized the card already.  It is treated as a
620	  completely dumb framebuffer device.
621
622config FB_XVR1000
623	bool "Sun XVR-1000 support"
624	depends on (FB = y) && SPARC64
625	select FB_IOMEM_HELPERS
626	help
627	  This is the framebuffer device for the Sun XVR-1000 and similar
628	  graphics cards.  The driver only works on sparc64 systems where
629	  the system firmware has mostly initialized the card already.  It
630	  is treated as a completely dumb framebuffer device.
631
632config FB_PVR2
633	tristate "NEC PowerVR 2 display support"
634	depends on FB && HAS_IOMEM
635	depends on SH_DREAMCAST || COMPILE_TEST
636	select FB_CFB_FILLRECT
637	select FB_CFB_COPYAREA
638	select FB_CFB_IMAGEBLIT
639	select FB_IOMEM_FOPS
640	select VIDEO_NOMODESET
641	help
642	  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
643	  run linux on your Dreamcast, you will have to say Y here.
644	  This driver may or may not work on other PowerVR 2 cards, but is
645	  totally untested.  Use at your own risk.  If unsure, say N.
646
647	  To compile this driver as a module, choose M here: the
648	  module will be called pvr2fb.
649
650	  You can pass several parameters to the driver at boot time or at
651	  module load time.  The parameters look like "video=pvr2:XXX", where
652	  the meaning of XXX can be found at the end of the main source file
653	  (<file:drivers/video/fbdev/pvr2fb.c>). Please see the file
654	  <file:Documentation/fb/pvr2fb.rst>.
655
656config FB_OPENCORES
657	tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
658	depends on FB && HAS_DMA
659	select FB_IOMEM_HELPERS
660	help
661	  This enables support for the OpenCores VGA/LCD core.
662
663	  The OpenCores VGA/LCD core is typically used together with
664	  softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor
665	  systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs.
666
667	  The source code and specification for the core is available at
668	  <https://opencores.org/project,vga_lcd>
669
670config FB_S1D13XXX
671	tristate "Epson S1D13XXX framebuffer support"
672	depends on FB
673	select FB_CFB_FILLRECT
674	select FB_CFB_COPYAREA
675	select FB_CFB_IMAGEBLIT
676	select FB_IOMEM_FOPS
677	help
678	  Support for S1D13XXX framebuffer device family (currently only
679	  working with S1D13806). Product specs at
680	  <https://vdc.epson.com/>
681
682config FB_ATMEL
683	tristate "AT91 LCD Controller support"
684	depends on FB && OF && HAVE_CLK && HAS_IOMEM
685	depends on HAVE_FB_ATMEL || COMPILE_TEST
686	select FB_BACKLIGHT
687	select FB_IOMEM_HELPERS
688	select FB_MODE_HELPERS
689	select VIDEOMODE_HELPERS
690	help
691	  This enables support for the AT91 LCD Controller.
692
693config FB_NVIDIA
694	tristate "nVidia Framebuffer Support"
695	depends on FB && PCI
696	select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
697	select FB_CFB_FILLRECT
698	select FB_CFB_COPYAREA
699	select FB_CFB_IMAGEBLIT
700	select FB_IOMEM_FOPS
701	select BITREVERSE
702	select VGASTATE
703	select VIDEO_NOMODESET
704	help
705	  This driver supports graphics boards with the nVidia chips, TNT
706	  and newer. For very old chipsets, such as the RIVA128, then use
707	  the rivafb.
708	  Say Y if you have such a graphics board.
709
710	  To compile this driver as a module, choose M here: the
711	  module will be called nvidiafb.
712
713config FB_NVIDIA_I2C
714	bool "Enable DDC Support"
715	depends on FB_NVIDIA
716	select FB_DDC
717	help
718	  This enables I2C support for nVidia Chipsets.  This is used
719	  only for getting EDID information from the attached display
720	  allowing for robust video mode handling and switching.
721
722	  Because fbdev-2.6 requires that drivers must be able to
723	  independently validate video mode parameters, you should say Y
724	  here.
725
726config FB_NVIDIA_DEBUG
727	bool "Lots of debug output"
728	depends on FB_NVIDIA
729	help
730	  Say Y here if you want the nVidia driver to output all sorts
731	  of debugging information to provide to the maintainer when
732	  something goes wrong.
733
734config FB_NVIDIA_BACKLIGHT
735	bool "Support for backlight control"
736	depends on FB_NVIDIA
737	default y
738	help
739	  Say Y here if you want to control the backlight of your display.
740
741config FB_RIVA
742	tristate "nVidia Riva support"
743	depends on FB && PCI
744	select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
745	select FB_CFB_FILLRECT
746	select FB_CFB_COPYAREA
747	select FB_CFB_IMAGEBLIT
748	select FB_IOMEM_FOPS
749	select FB_MODE_HELPERS
750	select BITREVERSE
751	select VGASTATE
752	select VIDEO_NOMODESET
753	help
754	  This driver supports graphics boards with the nVidia Riva/Geforce
755	  chips.
756	  Say Y if you have such a graphics board.
757
758	  To compile this driver as a module, choose M here: the
759	  module will be called rivafb.
760
761config FB_RIVA_I2C
762	bool "Enable DDC Support"
763	depends on FB_RIVA
764	select FB_DDC
765	help
766	  This enables I2C support for nVidia Chipsets.  This is used
767	  only for getting EDID information from the attached display
768	  allowing for robust video mode handling and switching.
769
770	  Because fbdev-2.6 requires that drivers must be able to
771	  independently validate video mode parameters, you should say Y
772	  here.
773
774config FB_RIVA_DEBUG
775	bool "Lots of debug output"
776	depends on FB_RIVA
777	help
778	  Say Y here if you want the Riva driver to output all sorts
779	  of debugging information to provide to the maintainer when
780	  something goes wrong.
781
782config FB_RIVA_BACKLIGHT
783	bool "Support for backlight control"
784	depends on FB_RIVA
785	default y
786	help
787	  Say Y here if you want to control the backlight of your display.
788
789config FB_I740
790	tristate "Intel740 support"
791	depends on FB && PCI
792	select FB_IOMEM_HELPERS
793	select FB_MODE_HELPERS
794	select VGASTATE
795	select VIDEO_NOMODESET
796	select FB_DDC
797	help
798	  This driver supports graphics cards based on Intel740 chip.
799
800config FB_I810
801	tristate "Intel 810/815 support"
802	depends on FB && PCI && X86_32 && AGP_INTEL
803	select FB_IOMEM_FOPS
804	select FB_MODE_HELPERS
805	select VGASTATE
806	select VIDEO_NOMODESET
807	help
808	  This driver supports the on-board graphics built in to the Intel 810
809	  and 815 chipsets.  Say Y if you have and plan to use such a board.
810
811	  To compile this driver as a module, choose M here: the
812	  module will be called i810fb.
813
814	  For more information, please read
815	  <file:Documentation/fb/intel810.rst>
816
817config FB_I810_GTF
818	bool "use VESA Generalized Timing Formula"
819	depends on FB_I810
820	help
821	  If you say Y, then the VESA standard, Generalized Timing Formula
822	  or GTF, will be used to calculate the required video timing values
823	  per video mode.  Since the GTF allows nondiscrete timings
824	  (nondiscrete being a range of values as opposed to discrete being a
825	  set of values), you'll be able to use any combination of horizontal
826	  and vertical resolutions, and vertical refresh rates without having
827	  to specify your own timing parameters.  This is especially useful
828	  to maximize the performance of an aging display, or if you just
829	  have a display with nonstandard dimensions. A VESA compliant
830	  monitor is recommended, but can still work with non-compliant ones.
831	  If you need or want this, then select this option. The timings may
832	  not be compliant with Intel's recommended values. Use at your own
833	  risk.
834
835	  If you say N, the driver will revert to discrete video timings
836	  using a set recommended by Intel in their documentation.
837
838	  If unsure, say N.
839
840config FB_I810_I2C
841	bool "Enable DDC Support"
842	depends on FB_I810 && FB_I810_GTF
843	select FB_DDC
844	help
845	  Add DDC/I2C support for i810fb.  This will allow the driver to get
846	  display information, especially for monitors with fickle timings.
847
848	  If unsure, say Y.
849
850config FB_INTEL
851	tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support"
852	depends on FB && PCI && X86 && AGP_INTEL && EXPERT
853	select FB_CFB_FILLRECT
854	select FB_CFB_COPYAREA
855	select FB_CFB_IMAGEBLIT
856	select FB_IOMEM_FOPS
857	select FB_MODE_HELPERS
858	select BOOT_VESA_SUPPORT if FB_INTEL = y
859	select VIDEO_NOMODESET
860	depends on !DRM_I915
861	help
862	  This driver supports the on-board graphics built in to the Intel
863	  830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
864	  Say Y if you have and plan to use such a board.
865
866	  To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
867
868	  To compile this driver as a module, choose M here: the
869	  module will be called intelfb.
870
871	  For more information, please read <file:Documentation/fb/intelfb.rst>
872
873config FB_INTEL_DEBUG
874	bool "Intel driver Debug Messages"
875	depends on FB_INTEL
876	help
877	  Say Y here if you want the Intel driver to output all sorts
878	  of debugging information to provide to the maintainer when
879	  something goes wrong.
880
881config FB_INTEL_I2C
882	bool "DDC/I2C for Intel framebuffer support"
883	depends on FB_INTEL
884	select FB_DDC
885	default y
886	help
887	  Say Y here if you want DDC/I2C support for your on-board Intel graphics.
888
889config FB_MATROX
890	tristate "Matrox acceleration"
891	depends on FB && PCI
892	select FB_CFB_FILLRECT
893	select FB_CFB_COPYAREA
894	select FB_CFB_IMAGEBLIT
895	select FB_IOMEM_FOPS
896	select FB_TILEBLITTING
897	select FB_MACMODES if PPC_PMAC
898	select VIDEO_NOMODESET
899	help
900	  Say Y here if you have a Matrox Millennium, Matrox Millennium II,
901	  Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
902	  Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
903	  Matrox G400, G450 or G550 card in your box.
904
905	  To compile this driver as a module, choose M here: the
906	  module will be called matroxfb.
907
908	  You can pass several parameters to the driver at boot time or at
909	  module load time. The parameters look like "video=matroxfb:XXX", and
910	  are described in <file:Documentation/fb/matroxfb.rst>.
911
912config FB_MATROX_MILLENIUM
913	bool "Millennium I/II support"
914	depends on FB_MATROX
915	help
916	  Say Y here if you have a Matrox Millennium or Matrox Millennium II
917	  video card. If you select "Advanced lowlevel driver options" below,
918	  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
919	  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
920	  also use font widths different from 8.
921
922config FB_MATROX_MYSTIQUE
923	bool "Mystique support"
924	depends on FB_MATROX
925	help
926	  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
927	  video card. If you select "Advanced lowlevel driver options" below,
928	  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
929	  packed pixel and 32 bpp packed pixel. You can also use font widths
930	  different from 8.
931
932config FB_MATROX_G
933	bool "G100/G200/G400/G450/G550 support"
934	depends on FB_MATROX
935	help
936	  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
937	  video card. If you select "Advanced lowlevel driver options", you
938	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
939	  pixel and 32 bpp packed pixel. You can also use font widths
940	  different from 8.
941
942	  If you need support for G400 secondary head, you must say Y to
943	  "Matrox I2C support" and "G400 second head support" right below.
944	  G450/G550 secondary head and digital output are supported without
945	  additional modules.
946
947	  The driver starts in monitor mode. You must use the matroxset tool
948	  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
949	  swap primary and secondary head outputs, or to change output mode.
950	  Secondary head driver always start in 640x480 resolution and you
951	  must use fbset to change it.
952
953	  Do not forget that second head supports only 16 and 32 bpp
954	  packed pixels, so it is a good idea to compile them into the kernel
955	  too. You can use only some font widths, as the driver uses generic
956	  painting procedures (the secondary head does not use acceleration
957	  engine).
958
959	  G450/G550 hardware can display TV picture only from secondary CRTC,
960	  and it performs no scaling, so picture must have 525 or 625 lines.
961
962config FB_MATROX_I2C
963	tristate "Matrox I2C support"
964	depends on FB_MATROX
965	select FB_DDC
966	help
967	  This drivers creates I2C buses which are needed for accessing the
968	  DDC (I2C) bus present on all Matroxes, an I2C bus which
969	  interconnects Matrox optional devices, like MGA-TVO on G200 and
970	  G400, and the secondary head DDC bus, present on G400 only.
971
972	  You can say Y or M here if you want to experiment with monitor
973	  detection code. You must say Y or M here if you want to use either
974	  second head of G400 or MGA-TVO on G200 or G400.
975
976	  If you compile it as module, it will create a module named
977	  i2c-matroxfb.
978
979config FB_MATROX_MAVEN
980	tristate "G400 second head support"
981	depends on FB_MATROX_G && FB_MATROX_I2C
982	select FB_IOMEM_HELPERS
983	help
984	  WARNING !!! This support does not work with G450 !!!
985
986	  Say Y or M here if you want to use a secondary head (meaning two
987	  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
988	  head is not compatible with accelerated XFree 3.3.x SVGA servers -
989	  secondary head output is blanked while you are in X. With XFree
990	  3.9.17 preview you can use both heads if you use SVGA over fbdev or
991	  the fbdev driver on first head and the fbdev driver on second head.
992
993	  If you compile it as module, two modules are created,
994	  matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
995	  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
996	  also load i2c-matroxfb to get it to run.
997
998	  The driver starts in monitor mode and you must use the matroxset
999	  tool (available at
1000	  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1001	  PAL or NTSC or to swap primary and secondary head outputs.
1002	  Secondary head driver also always start in 640x480 resolution, you
1003	  must use fbset to change it.
1004
1005	  Also do not forget that second head supports only 16 and 32 bpp
1006	  packed pixels, so it is a good idea to compile them into the kernel
1007	  too.  You can use only some font widths, as the driver uses generic
1008	  painting procedures (the secondary head does not use acceleration
1009	  engine).
1010
1011config FB_RADEON
1012	tristate "ATI Radeon display support"
1013	depends on FB && PCI
1014	select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1015	select FB_CFB_FILLRECT
1016	select FB_CFB_COPYAREA
1017	select FB_CFB_IMAGEBLIT
1018	select FB_IOMEM_FOPS
1019	select FB_MACMODES if PPC
1020	select FB_MODE_HELPERS
1021	select VIDEO_NOMODESET
1022	help
1023	  Choose this option if you want to use an ATI Radeon graphics card as
1024	  a framebuffer device.  There are both PCI and AGP versions.  You
1025	  don't need to choose this to run the Radeon in plain VGA mode.
1026
1027	  There is a product page at
1028	  https://products.amd.com/en-us/GraphicCardResult.aspx
1029
1030config FB_RADEON_I2C
1031	bool "DDC/I2C for ATI Radeon support"
1032	depends on FB_RADEON
1033	select FB_DDC
1034	default y
1035	help
1036	  Say Y here if you want DDC/I2C support for your Radeon board.
1037
1038config FB_RADEON_BACKLIGHT
1039	bool "Support for backlight control"
1040	depends on FB_RADEON
1041	default y
1042	help
1043	  Say Y here if you want to control the backlight of your display.
1044
1045config FB_RADEON_DEBUG
1046	bool "Lots of debug output from Radeon driver"
1047	depends on FB_RADEON
1048	help
1049	  Say Y here if you want the Radeon driver to output all sorts
1050	  of debugging information to provide to the maintainer when
1051	  something goes wrong.
1052
1053config FB_ATY128
1054	tristate "ATI Rage128 display support"
1055	depends on FB && PCI
1056	select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1057	select FB_IOMEM_HELPERS
1058	select FB_MACMODES if PPC_PMAC
1059	select VIDEO_NOMODESET
1060	help
1061	  This driver supports graphics boards with the ATI Rage128 chips.
1062	  Say Y if you have such a graphics board and read
1063	  <file:Documentation/fb/aty128fb.rst>.
1064
1065	  To compile this driver as a module, choose M here: the
1066	  module will be called aty128fb.
1067
1068config FB_ATY128_BACKLIGHT
1069	bool "Support for backlight control"
1070	depends on FB_ATY128
1071	default y
1072	help
1073	  Say Y here if you want to control the backlight of your display.
1074
1075config FB_ATY
1076	tristate "ATI Mach64 display support" if PCI || ATARI
1077	depends on FB && !SPARC32
1078	select FB_CFB_FILLRECT
1079	select FB_CFB_COPYAREA
1080	select FB_CFB_IMAGEBLIT
1081	select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1082	select FB_IOMEM_FOPS
1083	select FB_MACMODES if PPC
1084	select FB_ATY_CT if SPARC64 && PCI
1085	select VIDEO_NOMODESET
1086	help
1087	  This driver supports graphics boards with the ATI Mach64 chips.
1088	  Say Y if you have such a graphics board.
1089
1090	  To compile this driver as a module, choose M here: the
1091	  module will be called atyfb.
1092
1093config FB_ATY_CT
1094	bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1095	depends on PCI && FB_ATY
1096	help
1097	  Say Y here to support use of ATI's 64-bit Rage boards (or other
1098	  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1099	  framebuffer device.  The ATI product support page for these boards
1100	  is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1101
1102config FB_ATY_GENERIC_LCD
1103	bool "Mach64 generic LCD support"
1104	depends on FB_ATY_CT
1105	help
1106	  Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1107	  Rage XC, or Rage XL chipset.
1108
1109config FB_ATY_GX
1110	bool "Mach64 GX support" if PCI
1111	depends on FB_ATY
1112	default y if ATARI
1113	help
1114	  Say Y here to support use of the ATI Mach64 Graphics Expression
1115	  board (or other boards based on the Mach64 GX chipset) as a
1116	  framebuffer device.  The ATI product support page for these boards
1117	  is at
1118	  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1119
1120config FB_ATY_BACKLIGHT
1121	bool "Support for backlight control"
1122	depends on FB_ATY
1123	default y
1124	help
1125	  Say Y here if you want to control the backlight of your display.
1126
1127config FB_S3
1128	tristate "S3 Trio/Virge support"
1129	depends on FB && PCI
1130	select FB_CFB_FILLRECT
1131	select FB_CFB_COPYAREA
1132	select FB_CFB_IMAGEBLIT
1133	select FB_IOMEM_FOPS
1134	select FB_TILEBLITTING
1135	select FB_SVGALIB
1136	select VGASTATE
1137	select VIDEO_NOMODESET
1138	select FONT_8x16 if FRAMEBUFFER_CONSOLE
1139	help
1140	  Driver for graphics boards with S3 Trio / S3 Virge chip.
1141
1142config FB_S3_DDC
1143	bool "DDC for S3 support"
1144	depends on FB_S3
1145	select FB_DDC
1146	default y
1147	help
1148	  Say Y here if you want DDC support for your S3 graphics card.
1149
1150config FB_SAVAGE
1151	tristate "S3 Savage support"
1152	depends on FB && PCI
1153	select FB_CFB_FILLRECT
1154	select FB_CFB_COPYAREA
1155	select FB_CFB_IMAGEBLIT
1156	select FB_IOMEM_FOPS
1157	select FB_MODE_HELPERS
1158	select VGASTATE
1159	select VIDEO_NOMODESET
1160	help
1161	  This driver supports notebooks and computers with S3 Savage PCI/AGP
1162	  chips.
1163
1164	  Say Y if you have such a graphics card.
1165
1166	  To compile this driver as a module, choose M here; the module
1167	  will be called savagefb.
1168
1169config FB_SAVAGE_I2C
1170	bool "Enable DDC2 Support"
1171	depends on FB_SAVAGE
1172	select FB_DDC
1173	help
1174	  This enables I2C support for S3 Savage Chipsets.  This is used
1175	  only for getting EDID information from the attached display
1176	  allowing for robust video mode handling and switching.
1177
1178	  Because fbdev-2.6 requires that drivers must be able to
1179	  independently validate video mode parameters, you should say Y
1180	  here.
1181
1182config FB_SAVAGE_ACCEL
1183	bool "Enable Console Acceleration"
1184	depends on FB_SAVAGE
1185	help
1186	  This option will compile in console acceleration support. If
1187	  the resulting framebuffer console has bothersome glitches, then
1188	  choose N here.
1189
1190config FB_SIS
1191	tristate "SiS/XGI display support"
1192	depends on FB && PCI
1193	select BOOT_VESA_SUPPORT if FB_SIS = y
1194	select FB_CFB_FILLRECT
1195	select FB_CFB_COPYAREA
1196	select FB_CFB_IMAGEBLIT
1197	select FB_IOMEM_FOPS
1198	select FB_SIS_300 if !FB_SIS_315
1199	select VIDEO_NOMODESET
1200	help
1201	  This is the frame buffer device driver for the SiS 300, 315, 330
1202	  and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1203	  Specs available at <https://www.sis.com> and <http://www.xgitech.com>.
1204
1205	  To compile this driver as a module, choose M here; the module
1206	  will be called sisfb.
1207
1208config FB_SIS_300
1209	bool "SiS 300 series support"
1210	depends on FB_SIS
1211	help
1212	  Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1213
1214config FB_SIS_315
1215	bool "SiS 315/330/340 series and XGI support"
1216	depends on FB_SIS
1217	help
1218	  Say Y here to support use of the SiS 315, 330 and 340 series
1219	  (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1220	  as XGI V3XT, V5, V8 and Z7.
1221
1222config FB_VIA
1223	tristate "VIA UniChrome (Pro) and Chrome9 display support"
1224	depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST)
1225	select FB_CFB_FILLRECT
1226	select FB_CFB_COPYAREA
1227	select FB_CFB_IMAGEBLIT
1228	select FB_IOMEM_FOPS
1229	select I2C_ALGOBIT
1230	select VIDEO_NOMODESET
1231	help
1232	  This is the frame buffer device driver for Graphics chips of VIA
1233	  UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1234	  CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1235	  /P4M900,VX800)
1236	  Say Y if you have a VIA UniChrome graphics board.
1237
1238	  To compile this driver as a module, choose M here: the
1239	  module will be called viafb.
1240
1241if FB_VIA
1242
1243config FB_VIA_DIRECT_PROCFS
1244	bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1245	help
1246	  Allow direct hardware access to some output registers via procfs.
1247	  This is dangerous but may provide the only chance to get the
1248	  correct output device configuration.
1249	  Its use is strongly discouraged.
1250
1251config FB_VIA_X_COMPATIBILITY
1252	bool "X server compatibility"
1253	help
1254	  This option reduces the functionality (power saving, ...) of the
1255	  framebuffer to avoid negative impact on the OpenChrome X server.
1256	  If you use any X server other than fbdev you should enable this
1257	  otherwise it should be safe to disable it and allow using all
1258	  features.
1259
1260endif
1261
1262config FB_NEOMAGIC
1263	tristate "NeoMagic display support"
1264	depends on FB && PCI
1265	select FB_CFB_FILLRECT
1266	select FB_CFB_COPYAREA
1267	select FB_CFB_IMAGEBLIT
1268	select FB_IOMEM_FOPS
1269	select FB_MODE_HELPERS
1270	select VGASTATE
1271	select VIDEO_NOMODESET
1272	help
1273	  This driver supports notebooks with NeoMagic PCI chips.
1274	  Say Y if you have such a graphics card.
1275
1276	  To compile this driver as a module, choose M here: the
1277	  module will be called neofb.
1278
1279config FB_KYRO
1280	tristate "IMG Kyro support"
1281	depends on FB && PCI
1282	select FB_IOMEM_HELPERS
1283	select VIDEO_NOMODESET
1284	help
1285	  Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1286	  graphics board.
1287
1288	  To compile this driver as a module, choose M here: the
1289	  module will be called kyrofb.
1290
1291config FB_3DFX
1292	tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1293	depends on FB && PCI
1294	select FB_CFB_FILLRECT
1295	select FB_CFB_COPYAREA
1296	select FB_CFB_IMAGEBLIT
1297	select FB_IOMEM_FOPS
1298	select FB_MODE_HELPERS
1299	select VIDEO_NOMODESET
1300	help
1301	  This driver supports graphics boards with the 3Dfx Banshee,
1302	  Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1303	  such a graphics board.
1304
1305	  To compile this driver as a module, choose M here: the
1306	  module will be called tdfxfb.
1307
1308config FB_3DFX_ACCEL
1309	bool "3Dfx Acceleration functions"
1310	depends on FB_3DFX
1311	help
1312	This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1313	device driver with acceleration functions.
1314
1315config FB_3DFX_I2C
1316	bool "Enable DDC/I2C support"
1317	depends on FB_3DFX
1318	select FB_DDC
1319	default y
1320	help
1321	  Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1322
1323config FB_VOODOO1
1324	tristate "3Dfx Voodoo Graphics (sst1) support"
1325	depends on FB && PCI
1326	depends on FB_DEVICE
1327	select FB_IOMEM_HELPERS
1328	select VIDEO_NOMODESET
1329	help
1330	  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1331	  Voodoo2 (cvg) based graphics card.
1332
1333	  To compile this driver as a module, choose M here: the
1334	  module will be called sstfb.
1335
1336	  WARNING: Do not use any application that uses the 3D engine
1337	  (namely glide) while using this driver.
1338	  Please read the <file:Documentation/fb/sstfb.rst> for supported
1339	  options and other important info  support.
1340
1341config FB_VT8623
1342	tristate "VIA VT8623 support"
1343	depends on FB && PCI
1344	select FB_CFB_FILLRECT
1345	select FB_CFB_COPYAREA
1346	select FB_CFB_IMAGEBLIT
1347	select FB_IOMEM_FOPS
1348	select FB_TILEBLITTING
1349	select FB_SVGALIB
1350	select VGASTATE
1351	select VIDEO_NOMODESET
1352	select FONT_8x16 if FRAMEBUFFER_CONSOLE
1353	help
1354	  Driver for CastleRock integrated graphics core in the
1355	  VIA VT8623 [Apollo CLE266] chipset.
1356
1357config FB_TRIDENT
1358	tristate "Trident/CyberXXX/CyberBlade support"
1359	depends on FB && PCI
1360	select FB_CFB_FILLRECT
1361	select FB_CFB_COPYAREA
1362	select FB_CFB_IMAGEBLIT
1363	select FB_DDC
1364	select FB_IOMEM_FOPS
1365	select FB_MODE_HELPERS
1366	select VIDEO_NOMODESET
1367	help
1368	  This is the frame buffer device driver for Trident PCI/AGP chipsets.
1369	  Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1370	  and Blade XP.
1371	  There are also integrated versions of these chips called CyberXXXX,
1372	  CyberImage or CyberBlade. These chips are mostly found in laptops
1373	  but also on some motherboards including early VIA EPIA motherboards.
1374	  For more information, read <file:Documentation/fb/tridentfb.rst>
1375
1376	  Say Y if you have such a graphics board.
1377
1378	  To compile this driver as a module, choose M here: the
1379	  module will be called tridentfb.
1380
1381config FB_ARK
1382	tristate "ARK 2000PV support"
1383	depends on FB && PCI
1384	select FB_CFB_FILLRECT
1385	select FB_CFB_COPYAREA
1386	select FB_CFB_IMAGEBLIT
1387	select FB_IOMEM_FOPS
1388	select FB_TILEBLITTING
1389	select FB_SVGALIB
1390	select VGASTATE
1391	select VIDEO_NOMODESET
1392	select FONT_8x16 if FRAMEBUFFER_CONSOLE
1393	help
1394	  Driver for PCI graphics boards with ARK 2000PV chip
1395	  and ICS 5342 RAMDAC.
1396
1397config FB_PM3
1398	tristate "Permedia3 support"
1399	depends on FB && PCI
1400	select FB_CFB_FILLRECT
1401	select FB_CFB_COPYAREA
1402	select FB_CFB_IMAGEBLIT
1403	select FB_IOMEM_FOPS
1404	select VIDEO_NOMODESET
1405	help
1406	  This is the frame buffer device driver for the 3DLabs Permedia3
1407	  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1408	  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1409	  and maybe other boards.
1410
1411config FB_CARMINE
1412	tristate "Fujitsu carmine frame buffer support"
1413	depends on FB && PCI
1414	select FB_IOMEM_HELPERS
1415	select VIDEO_NOMODESET
1416	help
1417	  This is the frame buffer device driver for the Fujitsu Carmine chip.
1418	  The driver provides two independent frame buffer devices.
1419
1420choice
1421	depends on FB_CARMINE
1422	prompt "DRAM timing"
1423	default FB_CARMINE_DRAM_EVAL
1424
1425config FB_CARMINE_DRAM_EVAL
1426	bool "Eval board timings"
1427	help
1428	  Use timings which work on the eval card.
1429
1430config CARMINE_DRAM_CUSTOM
1431	bool "Custom board timings"
1432	help
1433	  Use custom board timings.
1434endchoice
1435
1436config FB_AU1100
1437	bool "Au1100 LCD Driver"
1438	depends on (FB = y) && MIPS_ALCHEMY
1439	select FB_IOMEM_HELPERS
1440	help
1441	  This is the framebuffer driver for the AMD Au1100 SOC.  It can drive
1442	  various panels and CRTs by passing in kernel cmd line option
1443	  au1100fb:panel=<name>.
1444
1445config FB_AU1200
1446	bool "Au1200/Au1300 LCD Driver"
1447	depends on (FB = y) && MIPS_ALCHEMY
1448	select FB_SYS_FILLRECT
1449	select FB_SYS_COPYAREA
1450	select FB_SYS_IMAGEBLIT
1451	select FB_SYS_FOPS
1452	help
1453	  This is the framebuffer driver for the Au1200/Au1300 SOCs.
1454	  It can drive various panels and CRTs by passing in kernel cmd line
1455	  option au1200fb:panel=<name>.
1456
1457config FB_VT8500
1458	bool "VIA VT8500 framebuffer support"
1459	depends on (FB = y) && ARM && ARCH_VT8500
1460	select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1461	select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1462	select FB_SYS_IMAGEBLIT
1463	select FB_MODE_HELPERS
1464	select VIDEOMODE_HELPERS
1465	help
1466	  This is the framebuffer driver for VIA VT8500 integrated LCD
1467	  controller.
1468
1469config FB_WM8505
1470	bool "Wondermedia WM8xxx-series frame buffer support"
1471	depends on (FB = y) && HAS_IOMEM && (ARCH_VT8500 || COMPILE_TEST)
1472	select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS)
1473	select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS)
1474	select FB_SYS_IMAGEBLIT
1475	select FB_MODE_HELPERS
1476	select VIDEOMODE_HELPERS
1477	help
1478	  This is the framebuffer driver for WonderMedia WM8xxx-series
1479	  integrated LCD controller. This driver covers the WM8505, WM8650
1480	  and WM8850 SoCs.
1481
1482config FB_WMT_GE_ROPS
1483	bool "VT8500/WM8xxx accelerated raster ops support"
1484	depends on (FB = y) && (FB_VT8500 || FB_WM8505)
1485	help
1486	  This adds support for accelerated raster operations on the
1487	  VIA VT8500 and Wondermedia 85xx series SoCs.
1488
1489source "drivers/video/fbdev/geode/Kconfig"
1490
1491config FB_HIT
1492	tristate "HD64461 Frame Buffer support"
1493	depends on FB && HD64461
1494	select FB_CFB_FILLRECT
1495	select FB_CFB_IMAGEBLIT
1496	select FB_IOMEM_FOPS
1497	help
1498	  This is the frame buffer device driver for the Hitachi HD64461 LCD
1499	  frame buffer card.
1500
1501config FB_PMAG_AA
1502	tristate "PMAG-AA TURBOchannel framebuffer support"
1503	depends on FB && TC
1504	select FB_IOMEM_HELPERS
1505	help
1506	  Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1507	  used mainly in the MIPS-based DECstation series.
1508
1509config FB_PMAG_BA
1510	tristate "PMAG-BA TURBOchannel framebuffer support"
1511	depends on FB && TC
1512	select FB_IOMEM_HELPERS
1513	help
1514	  Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1515	  used mainly in the MIPS-based DECstation series.
1516
1517config FB_PMAGB_B
1518	tristate "PMAGB-B TURBOchannel framebuffer support"
1519	depends on FB && TC
1520	select FB_IOMEM_HELPERS
1521	help
1522	  Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1523	  in the MIPS-based DECstation series. The card is currently only
1524	  supported in 1280x1024x8 mode.
1525
1526config FB_MAXINE
1527	bool "Maxine (Personal DECstation) onboard framebuffer support"
1528	depends on (FB = y) && MACH_DECSTATION
1529	select FB_IOMEM_HELPERS
1530	help
1531	  Support for the onboard framebuffer (1024x768x8) in the Personal
1532	  DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1533	  Codename "Maxine").
1534
1535config FB_G364
1536	bool "G364 frame buffer support"
1537	depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1538	select FB_IOMEM_HELPERS
1539	help
1540	  The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1541	  Olivetti M700-10 systems.
1542
1543config FB_68328
1544	bool "Motorola 68328 native frame buffer support"
1545	depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1546	select FB_IOMEM_HELPERS
1547	help
1548	  Say Y here if you want to support the built-in frame buffer of
1549	  the Motorola 68328 CPU family.
1550
1551config FB_PXA168
1552	tristate "PXA168/910 LCD framebuffer support"
1553	depends on FB && HAVE_CLK && HAS_IOMEM
1554	depends on CPU_PXA168 || CPU_PXA910 || COMPILE_TEST
1555	select FB_IOMEM_HELPERS
1556	help
1557	  Frame buffer driver for the built-in LCD controller in the Marvell
1558	  MMP processor.
1559
1560config FB_PXA
1561	tristate "PXA LCD framebuffer support"
1562	depends on FB && ARCH_PXA
1563	select FB_IOMEM_HELPERS
1564	select VIDEOMODE_HELPERS if OF
1565	select FB_MODE_HELPERS if OF
1566	help
1567	  Frame buffer driver for the built-in LCD controller in the Intel
1568	  PXA2x0 processor.
1569
1570	  This driver is also available as a module ( = code which can be
1571	  inserted and removed from the running kernel whenever you want). The
1572	  module will be called pxafb. If you want to compile it as a module,
1573	  say M here and read <file:Documentation/kbuild/modules.rst>.
1574
1575	  If unsure, say N.
1576
1577config FB_PXA_OVERLAY
1578	bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1579	depends on FB_PXA && (PXA27x || PXA3xx)
1580
1581config FB_PXA_SMARTPANEL
1582	bool "PXA Smartpanel LCD support"
1583	depends on FB_PXA
1584
1585config FB_PXA_PARAMETERS
1586	bool "PXA LCD command line parameters"
1587	depends on FB_PXA
1588	help
1589	  Enable the use of kernel command line or module parameters
1590	  to configure the physical properties of the LCD panel when
1591	  using the PXA LCD driver.
1592
1593	  This option allows you to override the panel parameters
1594	  supplied by the platform in order to support multiple
1595	  different models of flatpanel. If you will only be using a
1596	  single model of flatpanel then you can safely leave this
1597	  option disabled.
1598
1599	  <file:Documentation/fb/pxafb.rst> describes the available parameters.
1600
1601config PXA3XX_GCU
1602	tristate "PXA3xx 2D graphics accelerator driver"
1603	depends on FB_PXA
1604	help
1605	  Kernelspace driver for the 2D graphics controller unit (GCU)
1606	  found on PXA3xx processors. There is a counterpart driver in the
1607	  DirectFB suite, see http://www.directfb.org/
1608
1609	  If you compile this as a module, it will be called pxa3xx_gcu.
1610
1611config FB_FSL_DIU
1612	tristate "Freescale DIU framebuffer support"
1613	depends on FB && FSL_SOC
1614	select FB_IOMEM_HELPERS
1615	select FB_MODE_HELPERS
1616	select PPC_LIB_RHEAP
1617	help
1618	  Framebuffer driver for the Freescale SoC DIU
1619
1620config FB_SH_MOBILE_LCDC
1621	tristate "SuperH Mobile LCDC framebuffer support"
1622	depends on FB && HAVE_CLK && HAS_IOMEM
1623	depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
1624	depends on FB_DEVICE
1625	select FB_SYS_FILLRECT
1626	select FB_SYS_COPYAREA
1627	select FB_SYS_IMAGEBLIT
1628	select FB_SYS_FOPS
1629	select FB_DEFERRED_IO
1630	select FB_BACKLIGHT
1631	help
1632	  Frame buffer driver for the on-chip SH-Mobile LCD controller.
1633
1634config FB_S3C
1635	tristate "Samsung S3C framebuffer support"
1636	depends on FB && HAVE_CLK && HAS_IOMEM
1637	depends on ARCH_S3C64XX || COMPILE_TEST
1638	select FB_IOMEM_HELPERS
1639	help
1640	  Frame buffer driver for the built-in FB controller in the Samsung
1641	  SoC line such as the S3C6400 and S3C6410.
1642
1643	  These chips all have the same basic framebuffer design with the
1644	  actual capabilities depending on the chip. The S3C6400
1645	  and S3C6410 support 4 hardware windows.
1646
1647	  Currently the support is only for the S3C6400 and S3C6410 SoCs.
1648
1649config FB_S3C_DEBUG_REGWRITE
1650	bool "Debug register writes"
1651	depends on FB_S3C
1652	help
1653	  Show all register writes via pr_debug()
1654
1655config FB_SM501
1656	tristate "Silicon Motion SM501 framebuffer support"
1657	depends on FB && MFD_SM501
1658	select FB_CFB_FILLRECT
1659	select FB_CFB_COPYAREA
1660	select FB_CFB_IMAGEBLIT
1661	select FB_IOMEM_FOPS
1662	help
1663	  Frame buffer driver for the CRT and LCD controllers in the Silicon
1664	  Motion SM501.
1665
1666	  This driver is also available as a module ( = code which can be
1667	  inserted and removed from the running kernel whenever you want). The
1668	  module will be called sm501fb. If you want to compile it as a module,
1669	  say M here and read <file:Documentation/kbuild/modules.rst>.
1670
1671	  If unsure, say N.
1672
1673config FB_SMSCUFX
1674	tristate "SMSC UFX6000/7000 USB Framebuffer support"
1675	depends on FB && USB
1676	select FB_MODE_HELPERS
1677	select FB_SYS_FILLRECT
1678	select FB_SYS_COPYAREA
1679	select FB_SYS_IMAGEBLIT
1680	select FB_SYS_FOPS
1681	select FB_DEFERRED_IO
1682	help
1683	  This is a kernel framebuffer driver for SMSC UFX USB devices.
1684	  Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1685	  mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000
1686	  (USB 3.0) devices.
1687	  To compile as a module, choose M here: the module name is smscufx.
1688
1689config FB_UDL
1690	tristate "Displaylink USB Framebuffer support"
1691	depends on FB && USB
1692	depends on FB_DEVICE
1693	select FB_MODE_HELPERS
1694	select FB_SYS_FILLRECT
1695	select FB_SYS_COPYAREA
1696	select FB_SYS_IMAGEBLIT
1697	select FB_SYS_FOPS
1698	select FB_DEFERRED_IO
1699	help
1700	  This is a kernel framebuffer driver for DisplayLink USB devices.
1701	  Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and
1702	  mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices.
1703	  To compile as a module, choose M here: the module name is udlfb.
1704
1705config FB_IBM_GXT4500
1706	tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors"
1707	depends on FB
1708	select FB_IOMEM_HELPERS
1709	select VIDEO_NOMODESET
1710	help
1711	  Say Y here to enable support for the IBM GXT4000P/6000P and
1712	  GXT4500P/6500P display adaptor based on Raster Engine RC1000,
1713	  found on some IBM System P (pSeries) machines. This driver
1714	  doesn't use Geometry Engine GT1000. This driver also supports
1715	  AGP Fire GL2/3/4 cards on x86.
1716
1717config FB_PS3
1718	tristate "PS3 GPU framebuffer driver"
1719	depends on FB && PS3_PS3AV
1720	select FB_SYS_FILLRECT
1721	select FB_SYS_COPYAREA
1722	select FB_SYS_IMAGEBLIT
1723	select FB_SYS_FOPS
1724	help
1725	  Include support for the virtual frame buffer in the PS3 platform.
1726
1727config FB_PS3_DEFAULT_SIZE_M
1728	int "PS3 default frame buffer size (in MiB)"
1729	depends on FB_PS3
1730	default 9
1731	help
1732	  This is the default size (in MiB) of the virtual frame buffer in
1733	  the PS3.
1734	  The default value can be overridden on the kernel command line
1735	  using the "ps3fb" option (e.g. "ps3fb=9M");
1736
1737config FB_XILINX
1738	tristate "Xilinx frame buffer support"
1739	depends on FB && (MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP)
1740	select FB_IOMEM_HELPERS
1741	help
1742	  Include support for the Xilinx ML300/ML403 reference design
1743	  framebuffer. ML300 carries a 640*480 LCD display on the board,
1744	  ML403 uses a standard DB15 VGA connector.
1745
1746config FB_GOLDFISH
1747	tristate "Goldfish Framebuffer"
1748	depends on FB
1749	depends on GOLDFISH || COMPILE_TEST
1750	select FB_IOMEM_HELPERS
1751	help
1752	  Framebuffer driver for Goldfish Virtual Platform
1753
1754config FB_COBALT
1755	tristate "Cobalt server LCD frame buffer support"
1756	depends on FB && MIPS_COBALT
1757	select FB_IOMEM_HELPERS
1758
1759config FB_SH7760
1760	bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
1761	depends on FB=y && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
1762		|| CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
1763	select FB_IOMEM_HELPERS
1764	help
1765	  Support for the SH7760/SH7763/SH7720/SH7721 integrated
1766	  (D)STN/TFT LCD Controller.
1767	  Supports display resolutions up to 1024x1024 pixel, grayscale and
1768	  color operation, with depths ranging from 1 bpp to 8 bpp monochrome
1769	  and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
1770	  panels <= 320 pixel horizontal resolution.
1771
1772config FB_DA8XX
1773	tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support"
1774	depends on FB && HAVE_CLK && HAS_IOMEM
1775	depends on ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST
1776	select FB_CFB_REV_PIXELS_IN_BYTE
1777	select FB_IOMEM_HELPERS
1778	select FB_MODE_HELPERS
1779	select VIDEOMODE_HELPERS
1780	help
1781	  This is the frame buffer device driver for the TI LCD controller
1782	  found on DA8xx/OMAP-L1xx/AM335x SoCs.
1783	  If unsure, say N.
1784
1785config FB_VIRTUAL
1786	tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1787	depends on FB
1788	select FB_SYS_FILLRECT
1789	select FB_SYS_COPYAREA
1790	select FB_SYS_IMAGEBLIT
1791	select FB_SYS_FOPS
1792	help
1793	  This is a `virtual' frame buffer device. It operates on a chunk of
1794	  unswappable kernel memory instead of on the memory of a graphics
1795	  board. This means you cannot see any output sent to this frame
1796	  buffer device, while it does consume precious memory. The main use
1797	  of this frame buffer device is testing and debugging the frame
1798	  buffer subsystem. Do NOT enable it for normal systems! To protect
1799	  the innocent, it has to be enabled explicitly at boot time using the
1800	  kernel option `video=vfb:'.
1801
1802	  To compile this driver as a module, choose M here: the
1803	  module will be called vfb. In order to load it, you must use
1804	  the vfb_enable=1 option.
1805
1806	  If unsure, say N.
1807
1808config XEN_FBDEV_FRONTEND
1809	tristate "Xen virtual frame buffer support"
1810	depends on FB && XEN
1811	select FB_SYSMEM_HELPERS_DEFERRED
1812	select XEN_XENBUS_FRONTEND
1813	default y
1814	help
1815	  This driver implements the front-end of the Xen virtual
1816	  frame buffer driver.  It communicates with a back-end
1817	  in another domain.
1818
1819config FB_METRONOME
1820	tristate "E-Ink Metronome/8track controller support"
1821	depends on FB
1822	select FB_SYSMEM_HELPERS_DEFERRED
1823	help
1824	  This driver implements support for the E-Ink Metronome
1825	  controller. The pre-release name for this device was 8track
1826	  and could also have been called by some vendors as PVI-nnnn.
1827
1828config FB_MB862XX
1829	tristate "Fujitsu MB862xx GDC support"
1830	depends on FB
1831	depends on PCI || (OF && PPC)
1832	select FB_IOMEM_HELPERS
1833	select VIDEO_NOMODESET
1834	help
1835	  Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
1836
1837choice
1838	prompt "GDC variant"
1839	depends on FB_MB862XX
1840
1841config FB_MB862XX_PCI_GDC
1842	bool "Carmine/Coral-P(A) GDC"
1843	depends on PCI
1844	help
1845	  This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
1846	  PCI graphics controller devices.
1847
1848config FB_MB862XX_LIME
1849	bool "Lime GDC"
1850	depends on OF && PPC
1851	select FB_FOREIGN_ENDIAN
1852	select FB_LITTLE_ENDIAN
1853	help
1854	  Framebuffer support for Fujitsu Lime GDC on host CPU bus.
1855
1856endchoice
1857
1858config FB_MB862XX_I2C
1859	bool "Support I2C bus on MB862XX GDC"
1860	depends on FB_MB862XX && I2C
1861	depends on FB_MB862XX=m || I2C=y
1862	default y
1863	help
1864	  Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter
1865	  driver to support accessing I2C devices on controller's I2C bus.
1866	  These are usually some video decoder chips.
1867
1868config FB_EP93XX
1869	tristate "EP93XX frame buffer support"
1870	depends on FB && ARCH_EP93XX
1871	select FB_IOMEM_HELPERS
1872	help
1873	  Framebuffer driver for the Cirrus Logic EP93XX series of processors.
1874	  This driver is also available as a module. The module will be called
1875	  ep93xx-fb.
1876
1877config FB_PRE_INIT_FB
1878	bool "Don't reinitialize, use bootloader's GDC/Display configuration"
1879	depends on FB && FB_MB862XX_LIME
1880	help
1881	  Select this option if display contents should be inherited as set by
1882	  the bootloader.
1883
1884config FB_BROADSHEET
1885	tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
1886	depends on FB && (ARCH_PXA || COMPILE_TEST)
1887	select FB_SYSMEM_HELPERS_DEFERRED
1888	help
1889	  This driver implements support for the E-Ink Broadsheet
1890	  controller. The release name for this device was Epson S1D13521
1891	  and could also have been called by other names when coupled with
1892	  a bridge adapter.
1893
1894config FB_HYPERV
1895	tristate "Microsoft Hyper-V Synthetic Video support"
1896	depends on FB && HYPERV
1897	select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA
1898	select FB_IOMEM_HELPERS_DEFERRED
1899	select VIDEO_NOMODESET
1900	help
1901	  This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
1902
1903config FB_SIMPLE
1904	tristate "Simple framebuffer support"
1905	depends on FB
1906	depends on !DRM_SIMPLEDRM
1907	select APERTURE_HELPERS
1908	select FB_IOMEM_HELPERS
1909	help
1910	  Say Y if you want support for a simple frame-buffer.
1911
1912	  This driver assumes that the display hardware has been initialized
1913	  before the kernel boots, and the kernel will simply render to the
1914	  pre-allocated frame buffer surface.
1915
1916	  Configuration re: surface address, size, and format must be provided
1917	  through device tree, or plain old platform data.
1918
1919config FB_SSD1307
1920	tristate "Solomon SSD1307 framebuffer support"
1921	depends on FB && I2C
1922	depends on GPIOLIB || COMPILE_TEST
1923	select FB_BACKLIGHT
1924	select FB_SYSMEM_HELPERS_DEFERRED
1925	help
1926	  This driver implements support for the Solomon SSD1307
1927	  OLED controller over I2C.
1928
1929config FB_SM712
1930	tristate "Silicon Motion SM712 framebuffer support"
1931	depends on FB && PCI
1932	select FB_IOMEM_HELPERS
1933	select VIDEO_NOMODESET
1934	help
1935	  Frame buffer driver for the Silicon Motion SM710, SM712, SM721
1936	  and SM722 chips.
1937
1938	  This driver is also available as a module. The module will be
1939	  called sm712fb. If you want to compile it as a module, say M
1940	  here and read <file:Documentation/kbuild/modules.rst>.
1941
1942source "drivers/video/fbdev/omap/Kconfig"
1943source "drivers/video/fbdev/omap2/Kconfig"
1944source "drivers/video/fbdev/mmp/Kconfig"
1945
1946source "drivers/video/fbdev/core/Kconfig"
1947