xref: /openbmc/linux/drivers/video/Kconfig (revision e868d61272caa648214046a096e5a6bfc068dc8c)
1#
2# Video configuration
3#
4
5menu "Graphics support"
6	depends on HAS_IOMEM
7
8source "drivers/video/backlight/Kconfig"
9source "drivers/video/display/Kconfig"
10
11config VGASTATE
12       tristate
13       default n
14
15config FB
16	tristate "Support for frame buffer devices"
17	---help---
18	  The frame buffer device provides an abstraction for the graphics
19	  hardware. It represents the frame buffer of some video hardware and
20	  allows application software to access the graphics hardware through
21	  a well-defined interface, so the software doesn't need to know
22	  anything about the low-level (hardware register) stuff.
23
24	  Frame buffer devices work identically across the different
25	  architectures supported by Linux and make the implementation of
26	  application programs easier and more portable; at this point, an X
27	  server exists which uses the frame buffer device exclusively.
28	  On several non-X86 architectures, the frame buffer device is the
29	  only way to use the graphics hardware.
30
31	  The device is accessed through special device nodes, usually located
32	  in the /dev directory, i.e. /dev/fb*.
33
34	  You need an utility program called fbset to make full use of frame
35	  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
36	  and the Framebuffer-HOWTO at
37	  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
38	  information.
39
40	  Say Y here and to the driver for your graphics board below if you
41	  are compiling a kernel for a non-x86 architecture.
42
43	  If you are compiling for the x86 architecture, you can say Y if you
44	  want to play with it, but it is not essential. Please note that
45	  running graphical applications that directly touch the hardware
46	  (e.g. an accelerated X server) and that are not frame buffer
47	  device-aware may cause unexpected results. If unsure, say N.
48
49config FIRMWARE_EDID
50       bool "Enable firmware EDID"
51       depends on FB
52       default n
53       ---help---
54         This enables access to the EDID transferred from the firmware.
55	 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
56	 transfers do not work for your driver and if you are using
57	 nvidiafb, i810fb or savagefb.
58
59	 In general, choosing Y for this option is safe.  If you
60	 experience extremely long delays while booting before you get
61	 something on your display, try setting this to N.  Matrox cards in
62	 combination with certain motherboards and monitors are known to
63	 suffer from this problem.
64
65config FB_DDC
66       tristate
67       depends on FB
68       select I2C_ALGOBIT
69       select I2C
70       default n
71
72config FB_CFB_FILLRECT
73	tristate
74	depends on FB
75	default n
76	---help---
77	  Include the cfb_fillrect function for generic software rectangle
78	  filling. This is used by drivers that don't provide their own
79	  (accelerated) version.
80
81config FB_CFB_COPYAREA
82	tristate
83	depends on FB
84	default n
85	---help---
86	  Include the cfb_copyarea function for generic software area copying.
87	  This is used by drivers that don't provide their own (accelerated)
88	  version.
89
90config FB_CFB_IMAGEBLIT
91	tristate
92	depends on FB
93	default n
94	---help---
95	  Include the cfb_imageblit function for generic software image
96	  blitting. This is used by drivers that don't provide their own
97	  (accelerated) version.
98
99config FB_SYS_FILLRECT
100	tristate
101	depends on FB
102	default n
103	---help---
104	  Include the sys_fillrect function for generic software rectangle
105	  filling. This is used by drivers that don't provide their own
106	  (accelerated) version and the framebuffer is in system RAM.
107
108config FB_SYS_COPYAREA
109	tristate
110	depends on FB
111	default n
112	---help---
113	  Include the sys_copyarea function for generic software area copying.
114	  This is used by drivers that don't provide their own (accelerated)
115	  version and the framebuffer is in system RAM.
116
117config FB_SYS_IMAGEBLIT
118	tristate
119	depends on FB
120	default n
121	---help---
122	  Include the sys_imageblit function for generic software image
123	  blitting. This is used by drivers that don't provide their own
124	  (accelerated) version and the framebuffer is in system RAM.
125
126config FB_SYS_FOPS
127       tristate
128       depends on FB
129       default n
130
131config FB_DEFERRED_IO
132	bool
133	depends on FB
134	default y
135
136config FB_SVGALIB
137	tristate
138	depends on FB
139	default n
140	---help---
141	  Common utility functions useful to fbdev drivers of VGA-based
142	  cards.
143
144config FB_MACMODES
145       tristate
146       depends on FB
147       default n
148
149config FB_BACKLIGHT
150	bool
151	depends on FB
152	select BACKLIGHT_LCD_SUPPORT
153	select BACKLIGHT_CLASS_DEVICE
154	default n
155
156config FB_MODE_HELPERS
157        bool "Enable Video Mode Handling Helpers"
158        depends on FB
159	default n
160	---help---
161	  This enables functions for handling video modes using the
162	  Generalized Timing Formula and the EDID parser. A few drivers rely
163          on this feature such as the radeonfb, rivafb, and the i810fb. If
164	  your driver does not take advantage of this feature, choosing Y will
165	  just increase the kernel size by about 5K.
166
167config FB_TILEBLITTING
168       bool "Enable Tile Blitting Support"
169       depends on FB
170       default n
171       ---help---
172         This enables tile blitting.  Tile blitting is a drawing technique
173	 where the screen is divided into rectangular sections (tiles), whereas
174	 the standard blitting divides the screen into pixels. Because the
175	 default drawing element is a tile, drawing functions will be passed
176	 parameters in terms of number of tiles instead of number of pixels.
177	 For example, to draw a single character, instead of using bitmaps,
178	 an index to an array of bitmaps will be used.  To clear or move a
179	 rectangular section of a screen, the rectangle will be described in
180	 terms of number of tiles in the x- and y-axis.
181
182	 This is particularly important to one driver, matroxfb.  If
183	 unsure, say N.
184
185comment "Frame buffer hardware drivers"
186	depends on FB
187
188config FB_CIRRUS
189	tristate "Cirrus Logic support"
190	depends on FB && (ZORRO || PCI)
191	select FB_CFB_FILLRECT
192	select FB_CFB_COPYAREA
193	select FB_CFB_IMAGEBLIT
194	---help---
195	  This enables support for Cirrus Logic GD542x/543x based boards on
196	  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
197
198	  If you have a PCI-based system, this enables support for these
199	  chips: GD-543x, GD-544x, GD-5480.
200
201	  Please read the file <file:Documentation/fb/cirrusfb.txt>.
202
203	  Say N unless you have such a graphics board or plan to get one
204	  before you next recompile the kernel.
205
206config FB_PM2
207	tristate "Permedia2 support"
208	depends on FB && ((AMIGA && BROKEN) || PCI)
209	select FB_CFB_FILLRECT
210	select FB_CFB_COPYAREA
211	select FB_CFB_IMAGEBLIT
212	help
213	  This is the frame buffer device driver for the Permedia2 AGP frame
214	  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
215	  product page at
216	  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
217
218config FB_PM2_FIFO_DISCONNECT
219	bool "enable FIFO disconnect feature"
220	depends on FB_PM2 && PCI
221	help
222	  Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
223
224config FB_ARMCLCD
225	tristate "ARM PrimeCell PL110 support"
226	depends on FB && ARM && ARM_AMBA
227	select FB_CFB_FILLRECT
228	select FB_CFB_COPYAREA
229	select FB_CFB_IMAGEBLIT
230	help
231	  This framebuffer device driver is for the ARM PrimeCell PL110
232	  Colour LCD controller.  ARM PrimeCells provide the building
233	  blocks for System on a Chip devices.
234
235	  If you want to compile this as a module (=code which can be
236	  inserted into and removed from the running kernel), say M
237	  here and read <file:Documentation/kbuild/modules.txt>.  The module
238	  will be called amba-clcd.
239
240choice
241
242	depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
243	prompt "LCD Panel"
244	default FB_ARMCLCD_SHARP_LQ035Q7DB02
245
246config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
247	bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
248	help
249	  This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
250	  color QVGA, HRTFT panel.  The LogicPD device includes
251	  an integrated HRTFT controller IC.
252	  The native resolution is 240x320.
253
254config FB_ARMCLCD_SHARP_LQ057Q3DC02
255	bool "LogicPD LCD 5.7\" QVGA"
256	help
257	  This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
258	  color QVGA, TFT panel.  The LogicPD device includes an
259	  The native resolution is 320x240.
260
261config FB_ARMCLCD_SHARP_LQ64D343
262	bool "LogicPD LCD 6.4\" VGA"
263	help
264	  This is an implementation of the Sharp LQ64D343, a 6.4"
265	  color VGA, TFT panel.  The LogicPD device includes an
266	  The native resolution is 640x480.
267
268config FB_ARMCLCD_SHARP_LQ10D368
269	bool "LogicPD LCD 10.4\" VGA"
270	help
271	  This is an implementation of the Sharp LQ10D368, a 10.4"
272	  color VGA, TFT panel.  The LogicPD device includes an
273	  The native resolution is 640x480.
274
275
276config FB_ARMCLCD_SHARP_LQ121S1DG41
277	bool "LogicPD LCD 12.1\" SVGA"
278	help
279	  This is an implementation of the Sharp LQ121S1DG41, a 12.1"
280	  color SVGA, TFT panel.  The LogicPD device includes an
281	  The native resolution is 800x600.
282
283	  This panel requires a clock rate may be an integer fraction
284	  of the base LCDCLK frequency.  The driver will select the
285	  highest frequency available that is lower than the maximum
286	  allowed.  The panel may flicker if the clock rate is
287	  slower than the recommended minimum.
288
289config FB_ARMCLCD_AUO_A070VW01_WIDE
290	bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
291	help
292	  This is an implementation of the AU Optronics, a 7.0"
293	  WIDE Color.  The native resolution is 234x480.
294
295config FB_ARMCLCD_HITACHI
296	bool "Hitachi Wide Screen 800x480"
297	help
298	  This is an implementation of the Hitachi 800x480.
299
300endchoice
301
302
303config FB_ACORN
304	bool "Acorn VIDC support"
305	depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
306	select FB_CFB_FILLRECT
307	select FB_CFB_COPYAREA
308	select FB_CFB_IMAGEBLIT
309	help
310	  This is the frame buffer device driver for the Acorn VIDC graphics
311	  hardware found in Acorn RISC PCs and other ARM-based machines.  If
312	  unsure, say N.
313
314config FB_CLPS711X
315	bool "CLPS711X LCD support"
316	depends on (FB = y) && ARM && ARCH_CLPS711X
317	select FB_CFB_FILLRECT
318	select FB_CFB_COPYAREA
319	select FB_CFB_IMAGEBLIT
320	help
321	  Say Y to enable the Framebuffer driver for the CLPS7111 and
322	  EP7212 processors.
323
324config FB_SA1100
325	bool "SA-1100 LCD support"
326	depends on (FB = y) && ARM && ARCH_SA1100
327	select FB_CFB_FILLRECT
328	select FB_CFB_COPYAREA
329	select FB_CFB_IMAGEBLIT
330	help
331	  This is a framebuffer device for the SA-1100 LCD Controller.
332	  See <http://www.linux-fbdev.org/> for information on framebuffer
333	  devices.
334
335	  If you plan to use the LCD display with your SA-1100 system, say
336	  Y here.
337
338config FB_IMX
339	tristate "Motorola i.MX LCD support"
340	depends on FB && ARM && ARCH_IMX
341	select FB_CFB_FILLRECT
342	select FB_CFB_COPYAREA
343	select FB_CFB_IMAGEBLIT
344
345config FB_CYBER2000
346	tristate "CyberPro 2000/2010/5000 support"
347	depends on FB && PCI && (BROKEN || !SPARC64)
348	select FB_CFB_FILLRECT
349	select FB_CFB_COPYAREA
350	select FB_CFB_IMAGEBLIT
351	help
352	  This enables support for the Integraphics CyberPro 20x0 and 5000
353	  VGA chips used in the Rebel.com Netwinder and other machines.
354	  Say Y if you have a NetWinder or a graphics card containing this
355	  device, otherwise say N.
356
357config FB_APOLLO
358	bool
359	depends on (FB = y) && APOLLO
360	default y
361	select FB_CFB_FILLRECT
362	select FB_CFB_IMAGEBLIT
363
364config FB_Q40
365	bool
366	depends on (FB = y) && Q40
367	default y
368	select FB_CFB_FILLRECT
369	select FB_CFB_COPYAREA
370	select FB_CFB_IMAGEBLIT
371
372config FB_AMIGA
373	tristate "Amiga native chipset support"
374	depends on FB && AMIGA
375	help
376	  This is the frame buffer device driver for the builtin graphics
377	  chipset found in Amigas.
378
379	  To compile this driver as a module, choose M here: the
380	  module will be called amifb.
381
382config FB_AMIGA_OCS
383	bool "Amiga OCS chipset support"
384	depends on FB_AMIGA
385	help
386	  This enables support for the original Agnus and Denise video chips,
387	  found in the Amiga 1000 and most A500's and A2000's. If you intend
388	  to run Linux on any of these systems, say Y; otherwise say N.
389
390config FB_AMIGA_ECS
391	bool "Amiga ECS chipset support"
392	depends on FB_AMIGA
393	help
394	  This enables support for the Enhanced Chip Set, found in later
395	  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
396	  you intend to run Linux on any of these systems, say Y; otherwise
397	  say N.
398
399config FB_AMIGA_AGA
400	bool "Amiga AGA chipset support"
401	depends on FB_AMIGA
402	help
403	  This enables support for the Advanced Graphics Architecture (also
404	  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
405	  and CD32. If you intend to run Linux on any of these systems, say Y;
406	  otherwise say N.
407
408config FB_FM2
409	bool "Amiga FrameMaster II/Rainbow II support"
410	depends on (FB = y) && ZORRO
411	select FB_CFB_FILLRECT
412	select FB_CFB_COPYAREA
413	select FB_CFB_IMAGEBLIT
414	help
415	  This is the frame buffer device driver for the Amiga FrameMaster
416	  card from BSC (exhibited 1992 but not shipped as a CBM product).
417
418config FB_ARC
419	tristate "Arc Monochrome LCD board support"
420	depends on FB && X86
421	select FB_SYS_FILLRECT
422	select FB_SYS_COPYAREA
423	select FB_SYS_IMAGEBLIT
424	select FB_SYS_FOPS
425	help
426	  This enables support for the Arc Monochrome LCD board. The board
427	  is based on the KS-108 lcd controller and is typically a matrix
428	  of 2*n chips. This driver was tested with a 128x64 panel. This
429	  driver supports it for use with x86 SBCs through a 16 bit GPIO
430	  interface (8 bit data, 8 bit control). If you anticipate using
431	  this driver, say Y or M; otherwise say N. You must specify the
432	  GPIO IO address to be used for setting control and data.
433
434config FB_ATARI
435	bool "Atari native chipset support"
436	depends on (FB = y) && ATARI
437	select FB_CFB_FILLRECT
438	select FB_CFB_COPYAREA
439	select FB_CFB_IMAGEBLIT
440	help
441	  This is the frame buffer device driver for the builtin graphics
442	  chipset found in Ataris.
443
444config FB_OF
445	bool "Open Firmware frame buffer device support"
446	depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
447	select FB_CFB_FILLRECT
448	select FB_CFB_COPYAREA
449	select FB_CFB_IMAGEBLIT
450	select FB_MACMODES
451	help
452	  Say Y if you want support with Open Firmware for your graphics
453	  board.
454
455config FB_CONTROL
456	bool "Apple \"control\" display support"
457	depends on (FB = y) && PPC_PMAC && PPC32
458	select FB_CFB_FILLRECT
459	select FB_CFB_COPYAREA
460	select FB_CFB_IMAGEBLIT
461	select FB_MACMODES
462	help
463	  This driver supports a frame buffer for the graphics adapter in the
464	  Power Macintosh 7300 and others.
465
466config FB_PLATINUM
467	bool "Apple \"platinum\" display support"
468	depends on (FB = y) && PPC_PMAC && PPC32
469	select FB_CFB_FILLRECT
470	select FB_CFB_COPYAREA
471	select FB_CFB_IMAGEBLIT
472	select FB_MACMODES
473	help
474	  This driver supports a frame buffer for the "platinum" graphics
475	  adapter in some Power Macintoshes.
476
477config FB_VALKYRIE
478	bool "Apple \"valkyrie\" display support"
479	depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
480	select FB_CFB_FILLRECT
481	select FB_CFB_COPYAREA
482	select FB_CFB_IMAGEBLIT
483	select FB_MACMODES
484	help
485	  This driver supports a frame buffer for the "valkyrie" graphics
486	  adapter in some Power Macintoshes.
487
488config FB_CT65550
489	bool "Chips 65550 display support"
490	depends on (FB = y) && PPC32
491	select FB_CFB_FILLRECT
492	select FB_CFB_COPYAREA
493	select FB_CFB_IMAGEBLIT
494	help
495	  This is the frame buffer device driver for the Chips & Technologies
496	  65550 graphics chip in PowerBooks.
497
498config FB_ASILIANT
499	bool "Asiliant (Chips) 69000 display support"
500	depends on (FB = y) && PCI
501	select FB_CFB_FILLRECT
502	select FB_CFB_COPYAREA
503	select FB_CFB_IMAGEBLIT
504	help
505	  This is the frame buffer device driver for the Asiliant 69030 chipset
506
507config FB_IMSTT
508	bool "IMS Twin Turbo display support"
509	depends on (FB = y) && PCI
510	select FB_CFB_IMAGEBLIT
511	select FB_MACMODES if PPC
512	help
513	  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
514	  many Macintosh and compatible computers.
515
516config FB_VGA16
517	tristate "VGA 16-color graphics support"
518	depends on FB && (X86 || PPC)
519	select FB_CFB_FILLRECT
520	select FB_CFB_COPYAREA
521	select FB_CFB_IMAGEBLIT
522	select VGASTATE
523	select FONT_8x16 if FRAMEBUFFER_CONSOLE
524	help
525	  This is the frame buffer device driver for VGA 16 color graphic
526	  cards. Say Y if you have such a card.
527
528	  To compile this driver as a module, choose M here: the
529	  module will be called vga16fb.
530
531config FB_STI
532	tristate "HP STI frame buffer device support"
533	depends on FB && PARISC
534	select FB_CFB_FILLRECT
535	select FB_CFB_COPYAREA
536	select FB_CFB_IMAGEBLIT
537	default y
538	---help---
539	  STI refers to the HP "Standard Text Interface" which is a set of
540	  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
541	  Enabling this option will implement the linux framebuffer device
542	  using calls to the STI BIOS routines for initialisation.
543
544	  If you enable this option, you will get a planar framebuffer device
545	  /dev/fb which will work on the most common HP graphic cards of the
546	  NGLE family, including the artist chips (in the 7xx and Bxxx series),
547	  HCRX, HCRX24, CRX, CRX24 and VisEG series.
548
549	  It is safe to enable this option, so you should probably say "Y".
550
551config FB_MAC
552	bool "Generic Macintosh display support"
553	depends on (FB = y) && MAC
554	select FB_CFB_FILLRECT
555	select FB_CFB_COPYAREA
556	select FB_CFB_IMAGEBLIT
557	select FB_MACMODES
558
559#      bool '  Apple DAFB display support' CONFIG_FB_DAFB
560config FB_HP300
561	bool
562	depends on (FB = y) && HP300
563	select FB_CFB_FILLRECT
564	select FB_CFB_IMAGEBLIT
565	default y
566
567config FB_TGA
568	tristate "TGA/SFB+ framebuffer support"
569	depends on FB && (ALPHA || TC)
570	select FB_CFB_FILLRECT
571	select FB_CFB_COPYAREA
572	select FB_CFB_IMAGEBLIT
573	select BITREVERSE
574	---help---
575	  This is the frame buffer device driver for generic TGA and SFB+
576	  graphic cards.  These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
577	  also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
578	  TURBOchannel cards, also known as PMAGD-A, -B and -C.
579
580	  Due to hardware limitations ZLX-E2 and E3 cards are not supported
581	  for DECstation 5000/200 systems.  Additionally due to firmware
582	  limitations these cards may cause troubles with booting DECstation
583	  5000/240 and /260 systems, but are fully supported under Linux if
584	  you manage to get it going. ;-)
585
586	  Say Y if you have one of those.
587
588config FB_VESA
589	bool "VESA VGA graphics support"
590	depends on (FB = y) && X86
591	select FB_CFB_FILLRECT
592	select FB_CFB_COPYAREA
593	select FB_CFB_IMAGEBLIT
594	select VIDEO_SELECT
595	help
596	  This is the frame buffer device driver for generic VESA 2.0
597	  compliant graphic cards. The older VESA 1.2 cards are not supported.
598	  You will get a boot time penguin logo at no additional cost. Please
599	  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
600
601config FB_IMAC
602	bool "Intel-based Macintosh Framebuffer Support"
603	depends on (FB = y) && X86 && EFI
604	select FB_CFB_FILLRECT
605	select FB_CFB_COPYAREA
606	select FB_CFB_IMAGEBLIT
607	help
608	  This is the frame buffer device driver for the Intel-based Macintosh
609
610config FB_HECUBA
611       tristate "Hecuba board support"
612       depends on FB && X86 && MMU
613       select FB_SYS_FILLRECT
614       select FB_SYS_COPYAREA
615       select FB_SYS_IMAGEBLIT
616       select FB_SYS_FOPS
617       select FB_DEFERRED_IO
618       help
619         This enables support for the Hecuba board. This driver was tested
620         with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
621         interface (8 bit data, 4 bit control). If you anticpate using
622         this driver, say Y or M; otherwise say N. You must specify the
623         GPIO IO address to be used for setting control and data.
624
625config FB_HGA
626	tristate "Hercules mono graphics support"
627	depends on FB && X86
628	select FB_CFB_FILLRECT
629	select FB_CFB_COPYAREA
630	select FB_CFB_IMAGEBLIT
631	help
632	  Say Y here if you have a Hercules mono graphics card.
633
634	  To compile this driver as a module, choose M here: the
635	  module will be called hgafb.
636
637	  As this card technology is 15 years old, most people will answer N
638	  here.
639
640config FB_HGA_ACCEL
641	bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
642	depends on FB_HGA && EXPERIMENTAL
643	---help---
644	This will compile the Hercules mono graphics with
645	acceleration functions.
646
647config FB_SGIVW
648	tristate "SGI Visual Workstation framebuffer support"
649	depends on FB && X86_VISWS
650	select FB_CFB_FILLRECT
651	select FB_CFB_COPYAREA
652	select FB_CFB_IMAGEBLIT
653	help
654	  SGI Visual Workstation support for framebuffer graphics.
655
656config FB_GBE
657	bool "SGI Graphics Backend frame buffer support"
658	depends on (FB = y) && (SGI_IP32 || X86_VISWS)
659	select FB_CFB_FILLRECT
660	select FB_CFB_COPYAREA
661	select FB_CFB_IMAGEBLIT
662 	help
663	  This is the frame buffer device driver for SGI Graphics Backend.
664	  This chip is used in SGI O2 and Visual Workstation 320/540.
665
666config FB_GBE_MEM
667	int "Video memory size in MB"
668	depends on FB_GBE
669	default 4
670	help
671	  This is the amount of memory reserved for the framebuffer,
672	  which can be any value between 1MB and 8MB.
673
674config FB_SBUS
675	bool "SBUS and UPA framebuffers"
676	depends on (FB = y) && SPARC
677	help
678	  Say Y if you want support for SBUS or UPA based frame buffer device.
679
680config FB_BW2
681	bool "BWtwo support"
682	depends on (FB = y) && (SPARC && FB_SBUS)
683	select FB_CFB_FILLRECT
684	select FB_CFB_COPYAREA
685	select FB_CFB_IMAGEBLIT
686	help
687	  This is the frame buffer device driver for the BWtwo frame buffer.
688
689config FB_CG3
690	bool "CGthree support"
691	depends on (FB = y) && (SPARC && FB_SBUS)
692	select FB_CFB_FILLRECT
693	select FB_CFB_COPYAREA
694	select FB_CFB_IMAGEBLIT
695	help
696	  This is the frame buffer device driver for the CGthree frame buffer.
697
698config FB_CG6
699	bool "CGsix (GX,TurboGX) support"
700	depends on (FB = y) && (SPARC && FB_SBUS)
701	select FB_CFB_COPYAREA
702	select FB_CFB_IMAGEBLIT
703	help
704	  This is the frame buffer device driver for the CGsix (GX, TurboGX)
705	  frame buffer.
706
707config FB_PVR2
708	tristate "NEC PowerVR 2 display support"
709	depends on FB && SH_DREAMCAST
710	select FB_CFB_FILLRECT
711	select FB_CFB_COPYAREA
712	select FB_CFB_IMAGEBLIT
713	---help---
714	  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
715	  run linux on your Dreamcast, you will have to say Y here.
716	  This driver may or may not work on other PowerVR 2 cards, but is
717	  totally untested.  Use at your own risk.  If unsure, say N.
718
719	  To compile this driver as a module, choose M here: the
720	  module will be called pvr2fb.
721
722	  You can pass several parameters to the driver at boot time or at
723	  module load time.  The parameters look like "video=pvr2:XXX", where
724	  the meaning of XXX can be found at the end of the main source file
725	  (<file:drivers/video/pvr2fb.c>). Please see the file
726	  <file:Documentation/fb/pvr2fb.txt>.
727
728config FB_EPSON1355
729	bool "Epson 1355 framebuffer support"
730	depends on (FB = y) && (SUPERH || ARCH_CEIVA)
731	select FB_CFB_FILLRECT
732	select FB_CFB_COPYAREA
733	select FB_CFB_IMAGEBLIT
734	help
735	  Build in support for the SED1355 Epson Research Embedded RAMDAC
736	  LCD/CRT Controller (since redesignated as the S1D13505) as a
737	  framebuffer.  Product specs at
738	  <http://www.erd.epson.com/vdc/html/products.htm>.
739
740config FB_S1D13XXX
741	tristate "Epson S1D13XXX framebuffer support"
742	depends on FB
743	select FB_CFB_FILLRECT
744	select FB_CFB_COPYAREA
745	select FB_CFB_IMAGEBLIT
746	help
747	  Support for S1D13XXX framebuffer device family (currently only
748	  working with S1D13806). Product specs at
749	  <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
750
751config FB_ATMEL
752	tristate "AT91/AT32 LCD Controller support"
753	depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || AVR32)
754	select FB_CFB_FILLRECT
755	select FB_CFB_COPYAREA
756	select FB_CFB_IMAGEBLIT
757	help
758	  This enables support for the AT91/AT32 LCD Controller.
759
760config FB_INTSRAM
761	bool "Frame Buffer in internal SRAM"
762	depends on FB_ATMEL && ARCH_AT91SAM9261
763	help
764	  Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
765	  to let frame buffer in external SDRAM.
766
767config FB_NVIDIA
768	tristate "nVidia Framebuffer Support"
769	depends on FB && PCI
770	select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
771	select FB_MODE_HELPERS
772	select FB_CFB_FILLRECT
773	select FB_CFB_COPYAREA
774	select FB_CFB_IMAGEBLIT
775	select BITREVERSE
776	select VGASTATE
777	help
778	  This driver supports graphics boards with the nVidia chips, TNT
779	  and newer. For very old chipsets, such as the RIVA128, then use
780	  the rivafb.
781	  Say Y if you have such a graphics board.
782
783	  To compile this driver as a module, choose M here: the
784	  module will be called nvidiafb.
785
786config FB_NVIDIA_I2C
787       bool "Enable DDC Support"
788       depends on FB_NVIDIA
789       select FB_DDC
790       help
791	  This enables I2C support for nVidia Chipsets.  This is used
792	  only for getting EDID information from the attached display
793	  allowing for robust video mode handling and switching.
794
795	  Because fbdev-2.6 requires that drivers must be able to
796	  independently validate video mode parameters, you should say Y
797	  here.
798
799config FB_NVIDIA_DEBUG
800	bool "Lots of debug output"
801	depends on FB_NVIDIA
802	default n
803	help
804	  Say Y here if you want the nVidia driver to output all sorts
805	  of debugging information to provide to the maintainer when
806	  something goes wrong.
807
808config FB_NVIDIA_BACKLIGHT
809	bool "Support for backlight control"
810	depends on FB_NVIDIA
811	default y
812	help
813	  Say Y here if you want to control the backlight of your display.
814
815config FB_RIVA
816	tristate "nVidia Riva support"
817	depends on FB && PCI
818	select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
819	select FB_MODE_HELPERS
820	select FB_CFB_FILLRECT
821	select FB_CFB_COPYAREA
822	select FB_CFB_IMAGEBLIT
823	select BITREVERSE
824	select VGASTATE
825	help
826	  This driver supports graphics boards with the nVidia Riva/Geforce
827	  chips.
828	  Say Y if you have such a graphics board.
829
830	  To compile this driver as a module, choose M here: the
831	  module will be called rivafb.
832
833config FB_RIVA_I2C
834       bool "Enable DDC Support"
835       depends on FB_RIVA
836       select FB_DDC
837       help
838	  This enables I2C support for nVidia Chipsets.  This is used
839	  only for getting EDID information from the attached display
840	  allowing for robust video mode handling and switching.
841
842	  Because fbdev-2.6 requires that drivers must be able to
843	  independently validate video mode parameters, you should say Y
844	  here.
845
846config FB_RIVA_DEBUG
847	bool "Lots of debug output"
848	depends on FB_RIVA
849	default n
850	help
851	  Say Y here if you want the Riva driver to output all sorts
852	  of debugging information to provide to the maintainer when
853	  something goes wrong.
854
855config FB_RIVA_BACKLIGHT
856	bool "Support for backlight control"
857	depends on FB_RIVA
858	default y
859	help
860	  Say Y here if you want to control the backlight of your display.
861
862config FB_I810
863	tristate "Intel 810/815 support (EXPERIMENTAL)"
864	depends on FB && EXPERIMENTAL && PCI && X86_32
865	select AGP
866	select AGP_INTEL
867	select FB_MODE_HELPERS
868	select FB_CFB_FILLRECT
869	select FB_CFB_COPYAREA
870	select FB_CFB_IMAGEBLIT
871	select VGASTATE
872	help
873	  This driver supports the on-board graphics built in to the Intel 810
874          and 815 chipsets.  Say Y if you have and plan to use such a board.
875
876          To compile this driver as a module, choose M here: the
877	  module will be called i810fb.
878
879          For more information, please read
880	  <file:Documentation/fb/intel810.txt>
881
882config FB_I810_GTF
883	bool "use VESA Generalized Timing Formula"
884	depends on FB_I810
885	help
886	  If you say Y, then the VESA standard, Generalized Timing Formula
887          or GTF, will be used to calculate the required video timing values
888	  per video mode.  Since the GTF allows nondiscrete timings
889          (nondiscrete being a range of values as opposed to discrete being a
890          set of values), you'll be able to use any combination of horizontal
891	  and vertical resolutions, and vertical refresh rates without having
892	  to specify your own timing parameters.  This is especially useful
893	  to maximize the performance of an aging display, or if you just
894          have a display with nonstandard dimensions. A VESA compliant
895	  monitor is recommended, but can still work with non-compliant ones.
896	  If you need or want this, then select this option. The timings may
897	  not be compliant with Intel's recommended values. Use at your own
898	  risk.
899
900          If you say N, the driver will revert to discrete video timings
901	  using a set recommended by Intel in their documentation.
902
903          If unsure, say N.
904
905config FB_I810_I2C
906	bool "Enable DDC Support"
907	depends on FB_I810 && FB_I810_GTF
908	select FB_DDC
909	help
910
911config FB_LE80578
912	tristate "Intel LE80578 (Vermilion) support"
913	depends on FB && PCI && X86
914	select FB_MODE_HELPERS
915	select FB_CFB_FILLRECT
916	select FB_CFB_COPYAREA
917	select FB_CFB_IMAGEBLIT
918	help
919	  This driver supports the LE80578 (Vermilion Range) chipset
920
921config FB_CARILLO_RANCH
922	tristate "Intel Carillo Ranch support"
923	depends on FB_LE80578 && FB && PCI && X86
924	help
925	  This driver supports the LE80578 (Carillo Ranch) board
926
927config FB_INTEL
928	tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
929	depends on FB && EXPERIMENTAL && PCI && X86
930	select AGP
931	select AGP_INTEL
932	select FB_MODE_HELPERS
933	select FB_CFB_FILLRECT
934	select FB_CFB_COPYAREA
935	select FB_CFB_IMAGEBLIT
936	help
937	  This driver supports the on-board graphics built in to the Intel
938          830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
939          Say Y if you have and plan to use such a board.
940
941	  If you say Y here and want DDC/I2C support you must first say Y to
942	  "I2C support" and "I2C bit-banging support" in the character devices
943	  section.
944
945	  If you say M here then "I2C support" and "I2C bit-banging support"
946	  can be build either as modules or built-in.
947
948	  To compile this driver as a module, choose M here: the
949	  module will be called intelfb.
950
951	  For more information, please read <file:Documentation/fb/intelfb.txt>
952
953config FB_INTEL_DEBUG
954	bool "Intel driver Debug Messages"
955	depends on FB_INTEL
956	---help---
957	  Say Y here if you want the Intel driver to output all sorts
958	  of debugging information to provide to the maintainer when
959	  something goes wrong.
960
961config FB_INTEL_I2C
962	bool "DDC/I2C for Intel framebuffer support"
963	depends on FB_INTEL
964	select FB_DDC
965	default y
966	help
967	  Say Y here if you want DDC/I2C support for your on-board Intel graphics.
968
969config FB_MATROX
970	tristate "Matrox acceleration"
971	depends on FB && PCI
972	select FB_CFB_FILLRECT
973	select FB_CFB_COPYAREA
974	select FB_CFB_IMAGEBLIT
975	select FB_TILEBLITTING
976	select FB_MACMODES if PPC_PMAC
977	---help---
978	  Say Y here if you have a Matrox Millennium, Matrox Millennium II,
979	  Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
980	  Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
981	  Matrox G400, G450 or G550 card in your box.
982
983	  To compile this driver as a module, choose M here: the
984	  module will be called matroxfb.
985
986	  You can pass several parameters to the driver at boot time or at
987	  module load time. The parameters look like "video=matrox:XXX", and
988	  are described in <file:Documentation/fb/matroxfb.txt>.
989
990config FB_MATROX_MILLENIUM
991	bool "Millennium I/II support"
992	depends on FB_MATROX
993	help
994	  Say Y here if you have a Matrox Millennium or Matrox Millennium II
995	  video card. If you select "Advanced lowlevel driver options" below,
996	  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
997	  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
998	  also use font widths different from 8.
999
1000config FB_MATROX_MYSTIQUE
1001	bool "Mystique support"
1002	depends on FB_MATROX
1003	help
1004	  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1005	  video card. If you select "Advanced lowlevel driver options" below,
1006	  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1007	  packed pixel and 32 bpp packed pixel. You can also use font widths
1008	  different from 8.
1009
1010config FB_MATROX_G
1011	bool "G100/G200/G400/G450/G550 support"
1012	depends on FB_MATROX
1013	---help---
1014	  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1015	  video card. If you select "Advanced lowlevel driver options", you
1016	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1017	  pixel and 32 bpp packed pixel. You can also use font widths
1018	  different from 8.
1019
1020	  If you need support for G400 secondary head, you must first say Y to
1021	  "I2C support" in the character devices section, and then to
1022	  "Matrox I2C support" and "G400 second head support" here in the
1023	  framebuffer section. G450/G550 secondary head and digital output
1024	  are supported without additional modules.
1025
1026	  The driver starts in monitor mode. You must use the matroxset tool
1027	  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1028	  swap primary and secondary head outputs, or to change output mode.
1029	  Secondary head driver always start in 640x480 resolution and you
1030	  must use fbset to change it.
1031
1032	  Do not forget that second head supports only 16 and 32 bpp
1033	  packed pixels, so it is a good idea to compile them into the kernel
1034	  too. You can use only some font widths, as the driver uses generic
1035	  painting procedures (the secondary head does not use acceleration
1036	  engine).
1037
1038	  G450/G550 hardware can display TV picture only from secondary CRTC,
1039	  and it performs no scaling, so picture must have 525 or 625 lines.
1040
1041config FB_MATROX_I2C
1042	tristate "Matrox I2C support"
1043	depends on FB_MATROX
1044	select FB_DDC
1045	---help---
1046	  This drivers creates I2C buses which are needed for accessing the
1047	  DDC (I2C) bus present on all Matroxes, an I2C bus which
1048	  interconnects Matrox optional devices, like MGA-TVO on G200 and
1049	  G400, and the secondary head DDC bus, present on G400 only.
1050
1051	  You can say Y or M here if you want to experiment with monitor
1052	  detection code. You must say Y or M here if you want to use either
1053	  second head of G400 or MGA-TVO on G200 or G400.
1054
1055	  If you compile it as module, it will create a module named
1056	  i2c-matroxfb.
1057
1058config FB_MATROX_MAVEN
1059	tristate "G400 second head support"
1060	depends on FB_MATROX_G && FB_MATROX_I2C
1061	---help---
1062	  WARNING !!! This support does not work with G450 !!!
1063
1064	  Say Y or M here if you want to use a secondary head (meaning two
1065	  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1066	  head is not compatible with accelerated XFree 3.3.x SVGA servers -
1067	  secondary head output is blanked while you are in X. With XFree
1068	  3.9.17 preview you can use both heads if you use SVGA over fbdev or
1069	  the fbdev driver on first head and the fbdev driver on second head.
1070
1071	  If you compile it as module, two modules are created,
1072	  matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1073	  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1074	  also load i2c-matroxfb to get it to run.
1075
1076	  The driver starts in monitor mode and you must use the matroxset
1077	  tool (available at
1078	  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1079	  PAL or NTSC or to swap primary and secondary head outputs.
1080	  Secondary head driver also always start in 640x480 resolution, you
1081	  must use fbset to change it.
1082
1083	  Also do not forget that second head supports only 16 and 32 bpp
1084	  packed pixels, so it is a good idea to compile them into the kernel
1085	  too.  You can use only some font widths, as the driver uses generic
1086	  painting procedures (the secondary head does not use acceleration
1087	  engine).
1088
1089config FB_MATROX_MULTIHEAD
1090	bool "Multihead support"
1091	depends on FB_MATROX
1092	---help---
1093	  Say Y here if you have more than one (supported) Matrox device in
1094	  your computer and you want to use all of them for different monitors
1095	  ("multihead"). If you have only one device, you should say N because
1096	  the driver compiled with Y is larger and a bit slower, especially on
1097	  ia32 (ix86).
1098
1099	  If you said M to "Matrox unified accelerated driver" and N here, you
1100	  will still be able to use several Matrox devices simultaneously:
1101	  insert several instances of the module matroxfb into the kernel
1102	  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1103	  for the different Matrox devices. This method is slightly faster but
1104	  uses 40 KB of kernel memory per Matrox card.
1105
1106	  There is no need for enabling 'Matrox multihead support' if you have
1107	  only one Matrox card in the box.
1108
1109config FB_RADEON
1110	tristate "ATI Radeon display support"
1111	depends on FB && PCI
1112	select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1113	select FB_MODE_HELPERS
1114	select FB_CFB_FILLRECT
1115	select FB_CFB_COPYAREA
1116	select FB_CFB_IMAGEBLIT
1117	select FB_MACMODES if PPC_OF
1118	help
1119	  Choose this option if you want to use an ATI Radeon graphics card as
1120	  a framebuffer device.  There are both PCI and AGP versions.  You
1121	  don't need to choose this to run the Radeon in plain VGA mode.
1122
1123	  If you say Y here and want DDC/I2C support you must first say Y to
1124	  "I2C support" and "I2C bit-banging support" in the character devices
1125	  section.
1126
1127	  If you say M here then "I2C support" and "I2C bit-banging support"
1128	  can be build either as modules or built-in.
1129
1130	  There is a product page at
1131	  http://apps.ati.com/ATIcompare/
1132
1133config FB_RADEON_I2C
1134	bool "DDC/I2C for ATI Radeon support"
1135	depends on FB_RADEON
1136	select FB_DDC
1137	default y
1138	help
1139	  Say Y here if you want DDC/I2C support for your Radeon board.
1140
1141config FB_RADEON_BACKLIGHT
1142	bool "Support for backlight control"
1143	depends on FB_RADEON
1144	default y
1145	help
1146	  Say Y here if you want to control the backlight of your display.
1147
1148config FB_RADEON_DEBUG
1149	bool "Lots of debug output from Radeon driver"
1150	depends on FB_RADEON
1151	default n
1152	help
1153	  Say Y here if you want the Radeon driver to output all sorts
1154	  of debugging information to provide to the maintainer when
1155	  something goes wrong.
1156
1157config FB_ATY128
1158	tristate "ATI Rage128 display support"
1159	depends on FB && PCI
1160	select FB_CFB_FILLRECT
1161	select FB_CFB_COPYAREA
1162	select FB_CFB_IMAGEBLIT
1163	select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1164	select FB_MACMODES if PPC_PMAC
1165	help
1166	  This driver supports graphics boards with the ATI Rage128 chips.
1167	  Say Y if you have such a graphics board and read
1168	  <file:Documentation/fb/aty128fb.txt>.
1169
1170	  To compile this driver as a module, choose M here: the
1171	  module will be called aty128fb.
1172
1173config FB_ATY128_BACKLIGHT
1174	bool "Support for backlight control"
1175	depends on FB_ATY128
1176	default y
1177	help
1178	  Say Y here if you want to control the backlight of your display.
1179
1180config FB_ATY
1181	tristate "ATI Mach64 display support" if PCI || ATARI
1182	depends on FB && !SPARC32
1183	select FB_CFB_FILLRECT
1184	select FB_CFB_COPYAREA
1185	select FB_CFB_IMAGEBLIT
1186	select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1187	select FB_MACMODES if PPC
1188	help
1189	  This driver supports graphics boards with the ATI Mach64 chips.
1190	  Say Y if you have such a graphics board.
1191
1192	  To compile this driver as a module, choose M here: the
1193	  module will be called atyfb.
1194
1195config FB_ATY_CT
1196	bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1197	depends on PCI && FB_ATY
1198	default y if SPARC64 && FB_PCI
1199	help
1200	  Say Y here to support use of ATI's 64-bit Rage boards (or other
1201	  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1202	  framebuffer device.  The ATI product support page for these boards
1203	  is at <http://support.ati.com/products/pc/mach64/>.
1204
1205config FB_ATY_GENERIC_LCD
1206	bool "Mach64 generic LCD support (EXPERIMENTAL)"
1207	depends on FB_ATY_CT
1208	help
1209	  Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1210	  Rage XC, or Rage XL chipset.
1211
1212config FB_ATY_GX
1213	bool "Mach64 GX support" if PCI
1214	depends on FB_ATY
1215	default y if ATARI
1216	help
1217	  Say Y here to support use of the ATI Mach64 Graphics Expression
1218	  board (or other boards based on the Mach64 GX chipset) as a
1219	  framebuffer device.  The ATI product support page for these boards
1220	  is at
1221	  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1222
1223config FB_ATY_BACKLIGHT
1224	bool "Support for backlight control"
1225	depends on FB_ATY
1226	default y
1227	help
1228	  Say Y here if you want to control the backlight of your display.
1229
1230config FB_S3
1231	tristate "S3 Trio/Virge support"
1232	depends on FB && PCI
1233	select FB_CFB_FILLRECT
1234	select FB_CFB_COPYAREA
1235	select FB_CFB_IMAGEBLIT
1236	select FB_TILEBLITTING
1237	select FB_SVGALIB
1238	select VGASTATE
1239	select FONT_8x16 if FRAMEBUFFER_CONSOLE
1240	---help---
1241	  Driver for graphics boards with S3 Trio / S3 Virge chip.
1242
1243config FB_SAVAGE
1244	tristate "S3 Savage support"
1245	depends on FB && PCI && EXPERIMENTAL
1246	select FB_MODE_HELPERS
1247	select FB_CFB_FILLRECT
1248	select FB_CFB_COPYAREA
1249	select FB_CFB_IMAGEBLIT
1250	select VGASTATE
1251	help
1252	  This driver supports notebooks and computers with S3 Savage PCI/AGP
1253	  chips.
1254
1255	  Say Y if you have such a graphics card.
1256
1257	  To compile this driver as a module, choose M here; the module
1258	  will be called savagefb.
1259
1260config FB_SAVAGE_I2C
1261       bool "Enable DDC2 Support"
1262       depends on FB_SAVAGE
1263       select FB_DDC
1264       help
1265	  This enables I2C support for S3 Savage Chipsets.  This is used
1266	  only for getting EDID information from the attached display
1267	  allowing for robust video mode handling and switching.
1268
1269	  Because fbdev-2.6 requires that drivers must be able to
1270	  independently validate video mode parameters, you should say Y
1271	  here.
1272
1273config FB_SAVAGE_ACCEL
1274       bool "Enable Console Acceleration"
1275       depends on FB_SAVAGE
1276       default n
1277       help
1278          This option will compile in console acceleration support. If
1279          the resulting framebuffer console has bothersome glitches, then
1280          choose N here.
1281
1282config FB_SIS
1283	tristate "SiS/XGI display support"
1284	depends on FB && PCI
1285	select FB_CFB_FILLRECT
1286	select FB_CFB_COPYAREA
1287	select FB_CFB_IMAGEBLIT
1288	help
1289	  This is the frame buffer device driver for the SiS 300, 315, 330
1290	  and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1291	  Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1292
1293	  To compile this driver as a module, choose M here; the module
1294	  will be called sisfb.
1295
1296config FB_SIS_300
1297	bool "SiS 300 series support"
1298	depends on FB_SIS
1299	help
1300	  Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1301
1302config FB_SIS_315
1303	bool "SiS 315/330/340 series and XGI support"
1304	depends on FB_SIS
1305	help
1306	  Say Y here to support use of the SiS 315, 330 and 340 series
1307	  (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1308	  as XGI V3XT, V5, V8 and Z7.
1309
1310config FB_NEOMAGIC
1311	tristate "NeoMagic display support"
1312	depends on FB && PCI
1313	select FB_MODE_HELPERS
1314	select FB_CFB_FILLRECT
1315	select FB_CFB_COPYAREA
1316	select FB_CFB_IMAGEBLIT
1317	select VGASTATE
1318	help
1319	  This driver supports notebooks with NeoMagic PCI chips.
1320	  Say Y if you have such a graphics card.
1321
1322	  To compile this driver as a module, choose M here: the
1323	  module will be called neofb.
1324
1325config FB_KYRO
1326	tristate "IMG Kyro support"
1327	depends on FB && PCI
1328	select FB_CFB_FILLRECT
1329	select FB_CFB_COPYAREA
1330	select FB_CFB_IMAGEBLIT
1331	help
1332	  Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1333	  graphics board.
1334
1335	  To compile this driver as a module, choose M here: the
1336	  module will be called kyrofb.
1337
1338config FB_3DFX
1339	tristate "3Dfx Banshee/Voodoo3 display support"
1340	depends on FB && PCI
1341	select FB_CFB_IMAGEBLIT
1342	select FB_CFB_FILLRECT
1343	select FB_CFB_COPYAREA
1344	help
1345	  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1346	  chips. Say Y if you have such a graphics board.
1347
1348	  To compile this driver as a module, choose M here: the
1349	  module will be called tdfxfb.
1350
1351config FB_3DFX_ACCEL
1352	bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1353	depends on FB_3DFX && EXPERIMENTAL
1354	---help---
1355	This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1356	with acceleration functions.
1357
1358
1359config FB_VOODOO1
1360	tristate "3Dfx Voodoo Graphics (sst1) support"
1361	depends on FB && PCI
1362	select FB_CFB_FILLRECT
1363	select FB_CFB_COPYAREA
1364	select FB_CFB_IMAGEBLIT
1365	---help---
1366	  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1367	  Voodoo2 (cvg) based graphics card.
1368
1369	  To compile this driver as a module, choose M here: the
1370	  module will be called sstfb.
1371
1372	  WARNING: Do not use any application that uses the 3D engine
1373	  (namely glide) while using this driver.
1374	  Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1375	  options and other important info  support.
1376
1377config FB_VT8623
1378	tristate "VIA VT8623 support"
1379	depends on FB && PCI
1380	select FB_CFB_FILLRECT
1381	select FB_CFB_COPYAREA
1382	select FB_CFB_IMAGEBLIT
1383	select FB_TILEBLITTING
1384	select FB_SVGALIB
1385	select VGASTATE
1386	select FONT_8x16 if FRAMEBUFFER_CONSOLE
1387	---help---
1388	  Driver for CastleRock integrated graphics core in the
1389	  VIA VT8623 [Apollo CLE266] chipset.
1390
1391config FB_CYBLA
1392	tristate "Cyberblade/i1 support"
1393	depends on FB && PCI && X86_32 && !64BIT
1394	select FB_CFB_IMAGEBLIT
1395	select VIDEO_SELECT
1396	---help---
1397	  This driver is supposed to support the Trident Cyberblade/i1
1398	  graphics core integrated in the VIA VT8601A North Bridge,
1399	  also known as VIA Apollo PLE133.
1400
1401	  Status:
1402	   - Developed, tested and working on EPIA 5000 and EPIA 800.
1403	   - Does work reliable on all systems with CRT/LCD connected to
1404	     normal VGA ports.
1405	   - Should work on systems that do use the internal LCD port, but
1406	     this is absolutely not tested.
1407
1408	  Character imageblit, copyarea and rectangle fill are hw accelerated,
1409	  ypan scrolling is used by default.
1410
1411	  Please do read <file:Documentation/fb/cyblafb/*>.
1412
1413	  To compile this driver as a module, choose M here: the
1414	  module will be called cyblafb.
1415
1416config FB_TRIDENT
1417	tristate "Trident support"
1418	depends on FB && PCI
1419	select FB_CFB_FILLRECT
1420	select FB_CFB_COPYAREA
1421	select FB_CFB_IMAGEBLIT
1422	---help---
1423	  This driver is supposed to support graphics boards with the
1424	  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1425	  but also on some motherboards. For more information, read
1426	  <file:Documentation/fb/tridentfb.txt>
1427
1428	  Cyberblade/i1 support will be removed soon, use the cyblafb driver
1429	  instead.
1430
1431	  Say Y if you have such a graphics board.
1432
1433
1434	  To compile this driver as a module, choose M here: the
1435	  module will be called tridentfb.
1436
1437config FB_TRIDENT_ACCEL
1438	bool "Trident Acceleration functions (EXPERIMENTAL)"
1439	depends on FB_TRIDENT && EXPERIMENTAL
1440	---help---
1441	This will compile the Trident frame buffer device with
1442	acceleration functions.
1443
1444config FB_ARK
1445	tristate "ARK 2000PV support"
1446	depends on FB && PCI
1447	select FB_CFB_FILLRECT
1448	select FB_CFB_COPYAREA
1449	select FB_CFB_IMAGEBLIT
1450	select FB_TILEBLITTING
1451	select FB_SVGALIB
1452	select VGASTATE
1453	select FONT_8x16 if FRAMEBUFFER_CONSOLE
1454	---help---
1455	  Driver for PCI graphics boards with ARK 2000PV chip
1456	  and ICS 5342 RAMDAC.
1457
1458config FB_PM3
1459	tristate "Permedia3 support (EXPERIMENTAL)"
1460	depends on FB && PCI && EXPERIMENTAL
1461	select FB_CFB_FILLRECT
1462	select FB_CFB_COPYAREA
1463	select FB_CFB_IMAGEBLIT
1464	help
1465	  This is the frame buffer device driver for the 3DLabs Permedia3
1466	  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1467	  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1468	  and maybe other boards.
1469
1470config FB_AU1100
1471	bool "Au1100 LCD Driver"
1472	depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1473
1474config FB_AU1200
1475	bool "Au1200 LCD Driver"
1476	depends on (FB = y) && MIPS && SOC_AU1200
1477	select FB_CFB_FILLRECT
1478	select FB_CFB_COPYAREA
1479	select FB_CFB_IMAGEBLIT
1480	help
1481	  This is the framebuffer driver for the AMD Au1200 SOC.  It can drive
1482	  various panels and CRTs by passing in kernel cmd line option
1483	  au1200fb:panel=<name>.
1484
1485source "drivers/video/geode/Kconfig"
1486
1487config FB_FFB
1488	bool "Creator/Creator3D/Elite3D support"
1489	depends on FB_SBUS && SPARC64
1490	select FB_CFB_COPYAREA
1491	select FB_CFB_IMAGEBLIT
1492	help
1493	  This is the frame buffer device driver for the Creator, Creator3D,
1494	  and Elite3D graphics boards.
1495
1496config FB_TCX
1497	bool "TCX (SS4/SS5 only) support"
1498	depends on FB_SBUS
1499	select FB_CFB_FILLRECT
1500	select FB_CFB_COPYAREA
1501	select FB_CFB_IMAGEBLIT
1502	help
1503	  This is the frame buffer device driver for the TCX 24/8bit frame
1504	  buffer.
1505
1506config FB_CG14
1507	bool "CGfourteen (SX) support"
1508	depends on FB_SBUS
1509	select FB_CFB_FILLRECT
1510	select FB_CFB_COPYAREA
1511	select FB_CFB_IMAGEBLIT
1512	help
1513	  This is the frame buffer device driver for the CGfourteen frame
1514	  buffer on Desktop SPARCsystems with the SX graphics option.
1515
1516config FB_P9100
1517	bool "P9100 (Sparcbook 3 only) support"
1518	depends on FB_SBUS
1519	select FB_CFB_FILLRECT
1520	select FB_CFB_COPYAREA
1521	select FB_CFB_IMAGEBLIT
1522	help
1523	  This is the frame buffer device driver for the P9100 card
1524	  supported on Sparcbook 3 machines.
1525
1526config FB_LEO
1527	bool "Leo (ZX) support"
1528	depends on FB_SBUS
1529	select FB_CFB_FILLRECT
1530	select FB_CFB_COPYAREA
1531	select FB_CFB_IMAGEBLIT
1532	help
1533	  This is the frame buffer device driver for the SBUS-based Sun ZX
1534	  (leo) frame buffer cards.
1535
1536config FB_XVR500
1537	bool "Sun XVR-500 3DLABS Wildcat support"
1538	depends on FB && PCI && SPARC64
1539	select FB_CFB_FILLRECT
1540	select FB_CFB_COPYAREA
1541	select FB_CFB_IMAGEBLIT
1542	help
1543	  This is the framebuffer device for the Sun XVR-500 and similar
1544	  graphics cards based upon the 3DLABS Wildcat chipset.  The driver
1545	  only works on sparc64 systems where the system firwmare has
1546	  mostly initialized the card already.  It is treated as a
1547	  completely dumb framebuffer device.
1548
1549config FB_XVR2500
1550	bool "Sun XVR-2500 3DLABS Wildcat support"
1551	depends on FB && PCI && SPARC64
1552	select FB_CFB_FILLRECT
1553	select FB_CFB_COPYAREA
1554	select FB_CFB_IMAGEBLIT
1555	help
1556	  This is the framebuffer device for the Sun XVR-2500 and similar
1557	  graphics cards based upon the 3DLABS Wildcat chipset.  The driver
1558	  only works on sparc64 systems where the system firwmare has
1559	  mostly initialized the card already.  It is treated as a
1560	  completely dumb framebuffer device.
1561
1562config FB_PCI
1563	bool "PCI framebuffers"
1564	depends on (FB = y) && PCI && SPARC
1565
1566config FB_IGA
1567	bool "IGA 168x display support"
1568	depends on SPARC32 && FB_PCI
1569	select FB_CFB_FILLRECT
1570	select FB_CFB_COPYAREA
1571	select FB_CFB_IMAGEBLIT
1572	help
1573	  This is the framebuffer device for the INTERGRAPHICS 1680 and
1574	  successor frame buffer cards.
1575
1576config FB_HIT
1577	tristate "HD64461 Frame Buffer support"
1578	depends on FB && HD64461
1579	select FB_CFB_FILLRECT
1580	select FB_CFB_COPYAREA
1581	select FB_CFB_IMAGEBLIT
1582	help
1583	  This is the frame buffer device driver for the Hitachi HD64461 LCD
1584	  frame buffer card.
1585
1586config FB_PMAG_AA
1587	bool "PMAG-AA TURBOchannel framebuffer support"
1588	depends on (FB = y) && TC
1589 	select FB_CFB_FILLRECT
1590 	select FB_CFB_COPYAREA
1591 	select FB_CFB_IMAGEBLIT
1592	help
1593	  Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1594	  used mainly in the MIPS-based DECstation series.
1595
1596config FB_PMAG_BA
1597	tristate "PMAG-BA TURBOchannel framebuffer support"
1598	depends on FB && TC
1599 	select FB_CFB_FILLRECT
1600 	select FB_CFB_COPYAREA
1601 	select FB_CFB_IMAGEBLIT
1602	help
1603	  Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1604	  used mainly in the MIPS-based DECstation series.
1605
1606config FB_PMAGB_B
1607	tristate "PMAGB-B TURBOchannel framebuffer support"
1608	depends on TC
1609 	select FB_CFB_FILLRECT
1610 	select FB_CFB_COPYAREA
1611 	select FB_CFB_IMAGEBLIT
1612	help
1613	  Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1614	  in the MIPS-based DECstation series. The card is currently only
1615	  supported in 1280x1024x8 mode.
1616
1617config FB_MAXINE
1618	bool "Maxine (Personal DECstation) onboard framebuffer support"
1619	depends on (FB = y) && MACH_DECSTATION
1620 	select FB_CFB_FILLRECT
1621 	select FB_CFB_COPYAREA
1622 	select FB_CFB_IMAGEBLIT
1623	help
1624	  Support for the onboard framebuffer (1024x768x8) in the Personal
1625	  DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1626	  Codename "Maxine").
1627
1628config FB_TX3912
1629	bool "TMPTX3912/PR31700 frame buffer support"
1630	depends on (FB = y) && NINO
1631	select FB_CFB_FILLRECT
1632	select FB_CFB_COPYAREA
1633	select FB_CFB_IMAGEBLIT
1634	help
1635	  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1636	  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1637
1638	  Say Y here to enable kernel support for the on-board framebuffer.
1639
1640config FB_G364
1641	bool "G364 frame buffer support"
1642	depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1643 	select FB_CFB_FILLRECT
1644 	select FB_CFB_COPYAREA
1645 	select FB_CFB_IMAGEBLIT
1646	help
1647	  The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1648	  Olivetti M700-10 systems.
1649
1650config FB_68328
1651	bool "Motorola 68328 native frame buffer support"
1652	depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1653 	select FB_CFB_FILLRECT
1654 	select FB_CFB_COPYAREA
1655 	select FB_CFB_IMAGEBLIT
1656	help
1657	  Say Y here if you want to support the built-in frame buffer of
1658	  the Motorola 68328 CPU family.
1659
1660config FB_PXA
1661	tristate "PXA LCD framebuffer support"
1662	depends on FB && ARCH_PXA
1663	select FB_CFB_FILLRECT
1664	select FB_CFB_COPYAREA
1665	select FB_CFB_IMAGEBLIT
1666	---help---
1667	  Frame buffer driver for the built-in LCD controller in the Intel
1668	  PXA2x0 processor.
1669
1670	  This driver is also available as a module ( = code which can be
1671	  inserted and removed from the running kernel whenever you want). The
1672	  module will be called pxafb. If you want to compile it as a module,
1673	  say M here and read <file:Documentation/kbuild/modules.txt>.
1674
1675	  If unsure, say N.
1676
1677config FB_PXA_PARAMETERS
1678	bool "PXA LCD command line parameters"
1679	default n
1680	depends on FB_PXA
1681	---help---
1682	  Enable the use of kernel command line or module parameters
1683	  to configure the physical properties of the LCD panel when
1684	  using the PXA LCD driver.
1685
1686	  This option allows you to override the panel parameters
1687	  supplied by the platform in order to support multiple
1688	  different models of flatpanel. If you will only be using a
1689	  single model of flatpanel then you can safely leave this
1690	  option disabled.
1691
1692	  <file:Documentation/fb/pxafb.txt> describes the available parameters.
1693
1694config FB_MBX
1695	tristate "2700G LCD framebuffer support"
1696	depends on FB && ARCH_PXA
1697	select FB_CFB_FILLRECT
1698	select FB_CFB_COPYAREA
1699	select FB_CFB_IMAGEBLIT
1700	---help---
1701	  Framebuffer driver for the Intel 2700G (Marathon) Graphics
1702	  Accelerator
1703
1704config FB_MBX_DEBUG
1705       bool "Enable debugging info via debugfs"
1706       depends on FB_MBX && DEBUG_FS
1707       default n
1708       ---help---
1709         Enable this if you want debugging information using the debug
1710         filesystem (debugfs)
1711
1712         If unsure, say N.
1713
1714config FB_W100
1715	tristate "W100 frame buffer support"
1716	depends on FB && PXA_SHARPSL
1717 	select FB_CFB_FILLRECT
1718 	select FB_CFB_COPYAREA
1719 	select FB_CFB_IMAGEBLIT
1720	---help---
1721	  Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1722
1723	  This driver is also available as a module ( = code which can be
1724	  inserted and removed from the running kernel whenever you want). The
1725	  module will be called w100fb. If you want to compile it as a module,
1726	  say M here and read <file:Documentation/kbuild/modules.txt>.
1727
1728	  If unsure, say N.
1729
1730config FB_S3C2410
1731	tristate "S3C2410 LCD framebuffer support"
1732	depends on FB && ARCH_S3C2410
1733	select FB_CFB_FILLRECT
1734	select FB_CFB_COPYAREA
1735	select FB_CFB_IMAGEBLIT
1736	---help---
1737	  Frame buffer driver for the built-in LCD controller in the Samsung
1738	  S3C2410 processor.
1739
1740	  This driver is also available as a module ( = code which can be
1741	  inserted and removed from the running kernel whenever you want). The
1742	  module will be called s3c2410fb. If you want to compile it as a module,
1743	  say M here and read <file:Documentation/kbuild/modules.txt>.
1744
1745	  If unsure, say N.
1746config FB_S3C2410_DEBUG
1747	bool "S3C2410 lcd debug messages"
1748	depends on FB_S3C2410
1749	help
1750	  Turn on debugging messages. Note that you can set/unset at run time
1751	  through sysfs
1752
1753config FB_SM501
1754	tristate "Silicon Motion SM501 framebuffer support"
1755	depends on FB && MFD_SM501
1756	select FB_CFB_FILLRECT
1757	select FB_CFB_COPYAREA
1758	select FB_CFB_IMAGEBLIT
1759	---help---
1760	  Frame buffer driver for the CRT and LCD controllers in the Silicon
1761	  Motion SM501.
1762
1763	  This driver is also available as a module ( = code which can be
1764	  inserted and removed from the running kernel whenever you want). The
1765	  module will be called sm501fb. If you want to compile it as a module,
1766	  say M here and read <file:Documentation/modules.txt>.
1767
1768	  If unsure, say N.
1769
1770
1771config FB_PNX4008_DUM
1772	tristate "Display Update Module support on Philips PNX4008 board"
1773	depends on FB && ARCH_PNX4008
1774	---help---
1775	  Say Y here to enable support for PNX4008 Display Update Module (DUM)
1776
1777config FB_PNX4008_DUM_RGB
1778	tristate "RGB Framebuffer support on Philips PNX4008 board"
1779	depends on FB_PNX4008_DUM
1780	select FB_CFB_FILLRECT
1781	select FB_CFB_COPYAREA
1782	select FB_CFB_IMAGEBLIT
1783	---help---
1784	  Say Y here to enable support for PNX4008 RGB Framebuffer
1785
1786config FB_IBM_GXT4500
1787	tristate "Framebuffer support for IBM GXT4500P adaptor"
1788	depends on PPC
1789	select FB_CFB_FILLRECT
1790	select FB_CFB_COPYAREA
1791	select FB_CFB_IMAGEBLIT
1792	---help---
1793	  Say Y here to enable support for the IBM GXT4500P display
1794	  adaptor, found on some IBM System P (pSeries) machines.
1795
1796config FB_PS3
1797	bool "PS3 GPU framebuffer driver"
1798	depends on (FB = y) && PS3_PS3AV
1799	select FB_CFB_FILLRECT
1800	select FB_CFB_COPYAREA
1801	select FB_CFB_IMAGEBLIT
1802	---help---
1803	  Include support for the virtual frame buffer in the PS3 platform.
1804
1805config FB_PS3_DEFAULT_SIZE_M
1806	int "PS3 default frame buffer size (in MiB)"
1807	depends on FB_PS3
1808	default 18
1809	---help---
1810	  This is the default size (in MiB) of the virtual frame buffer in
1811	  the PS3.
1812	  The default value can be overridden on the kernel command line
1813	  using the "ps3fb" option (e.g. "ps3fb=9M");
1814
1815config FB_XILINX
1816	tristate "Xilinx frame buffer support"
1817	depends on FB && XILINX_VIRTEX
1818	select FB_CFB_FILLRECT
1819	select FB_CFB_COPYAREA
1820	select FB_CFB_IMAGEBLIT
1821	---help---
1822	  Include support for the Xilinx ML300/ML403 reference design
1823	  framebuffer. ML300 carries a 640*480 LCD display on the board,
1824	  ML403 uses a standard DB15 VGA connector.
1825
1826config FB_VIRTUAL
1827	tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1828	depends on FB
1829	select FB_SYS_FILLRECT
1830	select FB_SYS_COPYAREA
1831	select FB_SYS_IMAGEBLIT
1832	select FB_SYS_FOPS
1833	---help---
1834	  This is a `virtual' frame buffer device. It operates on a chunk of
1835	  unswappable kernel memory instead of on the memory of a graphics
1836	  board. This means you cannot see any output sent to this frame
1837	  buffer device, while it does consume precious memory. The main use
1838	  of this frame buffer device is testing and debugging the frame
1839	  buffer subsystem. Do NOT enable it for normal systems! To protect
1840	  the innocent, it has to be enabled explicitly at boot time using the
1841	  kernel option `video=vfb:'.
1842
1843	  To compile this driver as a module, choose M here: the
1844	  module will be called vfb. In order to load it, you must use
1845	  the vfb_enable=1 option.
1846
1847	  If unsure, say N.
1848
1849if VT
1850	source "drivers/video/console/Kconfig"
1851endif
1852
1853if FB || SGI_NEWPORT_CONSOLE
1854	source "drivers/video/logo/Kconfig"
1855endif
1856
1857endmenu
1858
1859