Context Navigation

Kconfig @ 34

Last change on this file since 34 was 34, checked in by hartmans, 18 years ago
Add xen and xen-common
File size: 50.6 KB

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

Note: See TracBrowser for help on using the repository browser.

Download in other formats:

Original Format