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