aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/video/Kconfig
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
commit1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch)
tree0bba044c4ce775e45a88a51686b5d9f90697ea9d /drivers/video/Kconfig
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
Diffstat (limited to 'drivers/video/Kconfig')
-rw-r--r--drivers/video/Kconfig1497
1 files changed, 1497 insertions, 0 deletions
diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
new file mode 100644
index 000000000000..2a1c5965de22
--- /dev/null
+++ b/drivers/video/Kconfig
@@ -0,0 +1,1497 @@
1#
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
201config FB_CYBER2000
202 tristate "CyberPro 2000/2010/5000 support"
203 depends on FB && PCI && (BROKEN || !SPARC64)
204 select FB_CFB_FILLRECT
205 select FB_CFB_COPYAREA
206 select FB_CFB_IMAGEBLIT
207 select FB_SOFT_CURSOR
208 help
209 This enables support for the Integraphics CyberPro 20x0 and 5000
210 VGA chips used in the Rebel.com Netwinder and other machines.
211 Say Y if you have a NetWinder or a graphics card containing this
212 device, otherwise say N.
213
214config FB_APOLLO
215 bool
216 depends on (FB = y) && APOLLO
217 default y
218 select FB_CFB_FILLRECT
219 select FB_CFB_IMAGEBLIT
220 select FB_SOFT_CURSOR
221
222config FB_Q40
223 bool
224 depends on (FB = y) && Q40
225 default y
226 select FB_CFB_FILLRECT
227 select FB_CFB_COPYAREA
228 select FB_CFB_IMAGEBLIT
229 select FB_SOFT_CURSOR
230
231config FB_AMIGA
232 tristate "Amiga native chipset support"
233 depends on FB && AMIGA
234 select FB_SOFT_CURSOR
235 help
236 This is the frame buffer device driver for the builtin graphics
237 chipset found in Amigas.
238
239 To compile this driver as a module, choose M here: the
240 module will be called amifb.
241
242config FB_AMIGA_OCS
243 bool "Amiga OCS chipset support"
244 depends on FB_AMIGA
245 help
246 This enables support for the original Agnus and Denise video chips,
247 found in the Amiga 1000 and most A500's and A2000's. If you intend
248 to run Linux on any of these systems, say Y; otherwise say N.
249
250config FB_AMIGA_ECS
251 bool "Amiga ECS chipset support"
252 depends on FB_AMIGA
253 help
254 This enables support for the Enhanced Chip Set, found in later
255 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
256 you intend to run Linux on any of these systems, say Y; otherwise
257 say N.
258
259config FB_AMIGA_AGA
260 bool "Amiga AGA chipset support"
261 depends on FB_AMIGA
262 help
263 This enables support for the Advanced Graphics Architecture (also
264 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
265 and CD32. If you intend to run Linux on any of these systems, say Y;
266 otherwise say N.
267
268config FB_CYBER
269 tristate "Amiga CyberVision 64 support"
270 depends on FB && ZORRO && BROKEN
271 select FB_CFB_FILLRECT
272 select FB_CFB_COPYAREA
273 select FB_CFB_IMAGEBLIT
274 select FB_SOFT_CURSOR
275 help
276 This enables support for the Cybervision 64 graphics card from
277 Phase5. Please note that its use is not all that intuitive (i.e. if
278 you have any questions, be sure to ask!). Say N unless you have a
279 Cybervision 64 or plan to get one before you next recompile the
280 kernel. Please note that this driver DOES NOT support the
281 Cybervision 64/3D card, as they use incompatible video chips.
282
283config FB_VIRGE
284 bool "Amiga CyberVision 64/3D support "
285 depends on (FB = y) && ZORRO && BROKEN
286 select FB_CFB_FILLRECT
287 select FB_CFB_COPYAREA
288 select FB_CFB_IMAGEBLIT
289 select FB_SOFT_CURSOR
290 help
291 This enables support for the Cybervision 64/3D graphics card from
292 Phase5. Please note that its use is not all that intuitive (i.e. if
293 you have any questions, be sure to ask!). Say N unless you have a
294 Cybervision 64/3D or plan to get one before you next recompile the
295 kernel. Please note that this driver DOES NOT support the older
296 Cybervision 64 card, as they use incompatible video chips.
297
298config FB_RETINAZ3
299 tristate "Amiga Retina Z3 support"
300 depends on (FB = y) && ZORRO && BROKEN
301 help
302 This enables support for the Retina Z3 graphics card. Say N unless
303 you have a Retina Z3 or plan to get one before you next recompile
304 the kernel.
305
306config FB_FM2
307 bool "Amiga FrameMaster II/Rainbow II support"
308 depends on (FB = y) && ZORRO
309 select FB_CFB_FILLRECT
310 select FB_CFB_COPYAREA
311 select FB_CFB_IMAGEBLIT
312 select FB_SOFT_CURSOR
313 help
314 This is the frame buffer device driver for the Amiga FrameMaster
315 card from BSC (exhibited 1992 but not shipped as a CBM product).
316
317config FB_ATARI
318 bool "Atari native chipset support"
319 depends on (FB = y) && ATARI && BROKEN
320 help
321 This is the frame buffer device driver for the builtin graphics
322 chipset found in Ataris.
323
324config FB_OF
325 bool "Open Firmware frame buffer device support"
326 depends on (FB = y) && (PPC64 || PPC_OF)
327 select FB_CFB_FILLRECT
328 select FB_CFB_COPYAREA
329 select FB_CFB_IMAGEBLIT
330 select FB_SOFT_CURSOR
331 select FB_MACMODES
332 help
333 Say Y if you want support with Open Firmware for your graphics
334 board.
335
336config FB_CONTROL
337 bool "Apple \"control\" display support"
338 depends on (FB = y) && PPC_PMAC
339 select FB_CFB_FILLRECT
340 select FB_CFB_COPYAREA
341 select FB_CFB_IMAGEBLIT
342 select FB_SOFT_CURSOR
343 select FB_MACMODES
344 help
345 This driver supports a frame buffer for the graphics adapter in the
346 Power Macintosh 7300 and others.
347
348config FB_PLATINUM
349 bool "Apple \"platinum\" display support"
350 depends on (FB = y) && PPC_PMAC
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 This driver supports a frame buffer for the "platinum" graphics
358 adapter in some Power Macintoshes.
359
360config FB_VALKYRIE
361 bool "Apple \"valkyrie\" display support"
362 depends on (FB = y) && (MAC || 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 "valkyrie" graphics
370 adapter in some Power Macintoshes.
371
372config FB_CT65550
373 bool "Chips 65550 display support"
374 depends on (FB = y) && PPC
375 select FB_CFB_FILLRECT
376 select FB_CFB_COPYAREA
377 select FB_CFB_IMAGEBLIT
378 select FB_SOFT_CURSOR
379 help
380 This is the frame buffer device driver for the Chips & Technologies
381 65550 graphics chip in PowerBooks.
382
383config FB_ASILIANT
384 bool "Chips 69000 display support"
385 depends on (FB = y) && PCI
386 select FB_CFB_FILLRECT
387 select FB_CFB_COPYAREA
388 select FB_CFB_IMAGEBLIT
389 select FB_SOFT_CURSOR
390
391config FB_IMSTT
392 bool "IMS Twin Turbo display support"
393 depends on (FB = y) && PCI
394 select FB_CFB_IMAGEBLIT
395 select FB_SOFT_CURSOR
396 select FB_MACMODES if PPC
397 help
398 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
399 many Macintosh and compatible computers.
400
401config FB_S3TRIO
402 bool "S3 Trio display support"
403 depends on (FB = y) && PPC && BROKEN
404 help
405 If you have a S3 Trio say Y. Say N for S3 Virge.
406
407config FB_VGA16
408 tristate "VGA 16-color graphics support"
409 depends on FB && (X86 || PPC)
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
413 select FB_SOFT_CURSOR
414 help
415 This is the frame buffer device driver for VGA 16 color graphic
416 cards. Say Y if you have such a card.
417
418 To compile this driver as a module, choose M here: the
419 module will be called vga16fb.
420
421config FB_STI
422 tristate "HP STI frame buffer device support"
423 depends on FB && PARISC
424 select FB_CFB_FILLRECT
425 select FB_CFB_COPYAREA
426 select FB_CFB_IMAGEBLIT
427 select FB_SOFT_CURSOR
428 default y
429 ---help---
430 STI refers to the HP "Standard Text Interface" which is a set of
431 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
432 Enabling this option will implement the linux framebuffer device
433 using calls to the STI BIOS routines for initialisation.
434
435 If you enable this option, you will get a planar framebuffer device
436 /dev/fb which will work on the most common HP graphic cards of the
437 NGLE family, including the artist chips (in the 7xx and Bxxx series),
438 HCRX, HCRX24, CRX, CRX24 and VisEG series.
439
440 It is safe to enable this option, so you should probably say "Y".
441
442config FB_MAC
443 bool "Generic Macintosh display support"
444 depends on (FB = y) && MAC
445 select FB_CFB_FILLRECT
446 select FB_CFB_COPYAREA
447 select FB_CFB_IMAGEBLIT
448 select FB_SOFT_CURSOR
449 select FB_MACMODES
450
451# bool ' Apple DAFB display support' CONFIG_FB_DAFB
452config FB_HP300
453 bool
454 depends on (FB = y) && HP300
455 select FB_CFB_FILLRECT
456 select FB_CFB_IMAGEBLIT
457 select FB_SOFT_CURSOR
458 default y
459
460config FB_TGA
461 tristate "TGA framebuffer support"
462 depends on FB && ALPHA
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
466 select FB_SOFT_CURSOR
467 help
468 This is the frame buffer device driver for generic TGA graphic
469 cards. Say Y if you have one of those.
470
471config FB_VESA
472 bool "VESA VGA graphics support"
473 depends on (FB = y) && (X86 || X86_64)
474 select FB_CFB_FILLRECT
475 select FB_CFB_COPYAREA
476 select FB_CFB_IMAGEBLIT
477 select FB_SOFT_CURSOR
478 help
479 This is the frame buffer device driver for generic VESA 2.0
480 compliant graphic cards. The older VESA 1.2 cards are not supported.
481 You will get a boot time penguin logo at no additional cost. Please
482 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
483
484config VIDEO_SELECT
485 bool
486 depends on FB_VESA
487 default y
488
489config FB_HGA
490 tristate "Hercules mono graphics support"
491 depends on FB && X86
492 select FB_CFB_FILLRECT
493 select FB_CFB_COPYAREA
494 select FB_CFB_IMAGEBLIT
495 select FB_SOFT_CURSOR
496 help
497 Say Y here if you have a Hercules mono graphics card.
498
499 To compile this driver as a module, choose M here: the
500 module will be called hgafb.
501
502 As this card technology is 15 years old, most people will answer N
503 here.
504
505config FB_HGA_ACCEL
506 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
507 depends on FB_HGA && EXPERIMENTAL
508 ---help---
509 This will compile the Hercules mono graphics with
510 acceleration functions.
511
512
513config VIDEO_SELECT
514 bool
515 depends on (FB = y) && X86
516 default y
517
518config FB_SGIVW
519 tristate "SGI Visual Workstation framebuffer support"
520 depends on FB && X86_VISWS
521 select FB_CFB_FILLRECT
522 select FB_CFB_COPYAREA
523 select FB_CFB_IMAGEBLIT
524 select FB_SOFT_CURSOR
525 help
526 SGI Visual Workstation support for framebuffer graphics.
527
528config FB_GBE
529 bool "SGI Graphics Backend frame buffer support"
530 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
534 select FB_SOFT_CURSOR
535 help
536 This is the frame buffer device driver for SGI Graphics Backend.
537 This chip is used in SGI O2 and Visual Workstation 320/540.
538
539config FB_GBE_MEM
540 int "Video memory size in MB"
541 depends on FB_GBE
542 default 8
543 help
544 This is the amount of memory reserved for the framebuffer,
545 which can be any value between 1MB and 8MB.
546
547config BUS_I2C
548 bool
549 depends on (FB = y) && VISWS
550 default y
551
552config FB_SUN3
553 bool "Sun3 framebuffer support"
554 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
555
556config FB_BW2
557 bool "BWtwo support"
558 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
562 select FB_SOFT_CURSOR
563 help
564 This is the frame buffer device driver for the BWtwo frame buffer.
565
566config FB_CG3
567 bool "CGthree support"
568 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
571 select FB_SOFT_CURSOR
572 help
573 This is the frame buffer device driver for the CGthree frame buffer.
574
575config FB_CG6
576 bool "CGsix (GX,TurboGX) support"
577 depends on (FB = y) && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
578 select FB_CFB_COPYAREA
579 select FB_CFB_IMAGEBLIT
580 select FB_SOFT_CURSOR
581 help
582 This is the frame buffer device driver for the CGsix (GX, TurboGX)
583 frame buffer.
584
585config FB_PVR2
586 tristate "NEC PowerVR 2 display support"
587 depends on FB && SH_DREAMCAST
588 select FB_CFB_FILLRECT
589 select FB_CFB_COPYAREA
590 select FB_CFB_IMAGEBLIT
591 select FB_SOFT_CURSOR
592 ---help---
593 Say Y here if you have a PowerVR 2 card in your box. If you plan to
594 run linux on your Dreamcast, you will have to say Y here.
595 This driver may or may not work on other PowerVR 2 cards, but is
596 totally untested. Use at your own risk. If unsure, say N.
597
598 To compile this driver as a module, choose M here: the
599 module will be called pvr2fb.
600
601 You can pass several parameters to the driver at boot time or at
602 module load time. The parameters look like "video=pvr2:XXX", where
603 the meaning of XXX can be found at the end of the main source file
604 (<file:drivers/video/pvr2fb.c>). Please see the file
605 <file:Documentation/fb/pvr2fb.txt>.
606
607config FB_EPSON1355
608 bool "Epson 1355 framebuffer support"
609 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
610 select FB_CFB_FILLRECT
611 select FB_CFB_COPYAREA
612 select FB_CFB_IMAGEBLIT
613 select FB_SOFT_CURSOR
614 help
615 Build in support for the SED1355 Epson Research Embedded RAMDAC
616 LCD/CRT Controller (since redesignated as the S1D13505) as a
617 framebuffer. Product specs at
618 <http://www.erd.epson.com/vdc/html/products.htm>.
619
620config FB_NVIDIA
621 tristate "nVidia Framebuffer Support"
622 depends on FB && PCI
623 select I2C_ALGOBIT if FB_NVIDIA_I2C
624 select I2C if FB_NVIDIA_I2C
625 select FB_MODE_HELPERS
626 select FB_CFB_FILLRECT
627 select FB_CFB_COPYAREA
628 select FB_CFB_IMAGEBLIT
629 select FB_SOFT_CURSOR
630 help
631 This driver supports graphics boards with the nVidia chips, TNT
632 and newer. For very old chipsets, such as the RIVA128, then use
633 the rivafb.
634 Say Y if you have such a graphics board.
635
636 To compile this driver as a module, choose M here: the
637 module will be called nvidiafb.
638
639config FB_NVIDIA_I2C
640 bool "Enable DDC Support"
641 depends on FB_NVIDIA && !PPC_OF
642 help
643 This enables I2C support for nVidia Chipsets. This is used
644 only for getting EDID information from the attached display
645 allowing for robust video mode handling and switching.
646
647 Because fbdev-2.6 requires that drivers must be able to
648 independently validate video mode parameters, you should say Y
649 here.
650
651config FB_RIVA
652 tristate "nVidia Riva support"
653 depends on FB && PCI
654 select I2C_ALGOBIT if FB_RIVA_I2C
655 select I2C if FB_RIVA_I2C
656 select FB_MODE_HELPERS
657 select FB_CFB_FILLRECT
658 select FB_CFB_COPYAREA
659 select FB_CFB_IMAGEBLIT
660 select FB_SOFT_CURSOR
661 help
662 This driver supports graphics boards with the nVidia Riva/Geforce
663 chips.
664 Say Y if you have such a graphics board.
665
666 To compile this driver as a module, choose M here: the
667 module will be called rivafb.
668
669config FB_RIVA_I2C
670 bool "Enable DDC Support"
671 depends on FB_RIVA
672 help
673 This enables I2C support for nVidia Chipsets. This is used
674 only for getting EDID information from the attached display
675 allowing for robust video mode handling and switching.
676
677 Because fbdev-2.6 requires that drivers must be able to
678 independently validate video mode parameters, you should say Y
679 here.
680
681config FB_RIVA_DEBUG
682 bool "Lots of debug output from Riva(nVidia) driver"
683 depends on FB_RIVA
684 default n
685 help
686 Say Y here if you want the Riva driver to output all sorts
687 of debugging informations to provide to the maintainer when
688 something goes wrong.
689
690config FB_I810
691 tristate "Intel 810/815 support (EXPERIMENTAL)"
692 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
693 select AGP
694 select AGP_INTEL
695 select FB_MODE_HELPERS
696 select FB_CFB_FILLRECT
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
699 select FB_SOFT_CURSOR
700 help
701 This driver supports the on-board graphics built in to the Intel 810
702 and 815 chipsets. Say Y if you have and plan to use such a board.
703
704 To compile this driver as a module, choose M here: the
705 module will be called i810fb.
706
707 For more information, please read
708 <file:Documentation/fb/intel810.txt>
709
710config FB_I810_GTF
711 bool "use VESA Generalized Timing Formula"
712 depends on FB_I810
713 help
714 If you say Y, then the VESA standard, Generalized Timing Formula
715 or GTF, will be used to calculate the required video timing values
716 per video mode. Since the GTF allows nondiscrete timings
717 (nondiscrete being a range of values as opposed to discrete being a
718 set of values), you'll be able to use any combination of horizontal
719 and vertical resolutions, and vertical refresh rates without having
720 to specify your own timing parameters. This is especially useful
721 to maximize the performance of an aging display, or if you just
722 have a display with nonstandard dimensions. A VESA compliant
723 monitor is recommended, but can still work with non-compliant ones.
724 If you need or want this, then select this option. The timings may
725 not be compliant with Intel's recommended values. Use at your own
726 risk.
727
728 If you say N, the driver will revert to discrete video timings
729 using a set recommended by Intel in their documentation.
730
731 If unsure, say N.
732
733config FB_INTEL
734 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
735 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
736 select AGP
737 select AGP_INTEL
738 select FB_MODE_HELPERS
739 select FB_CFB_FILLRECT
740 select FB_CFB_COPYAREA
741 select FB_CFB_IMAGEBLIT
742 select FB_SOFT_CURSOR
743 help
744 This driver supports the on-board graphics built in to the Intel
745 830M/845G/852GM/855GM/865G chipsets.
746 Say Y if you have and plan to use such a board.
747
748 To compile this driver as a module, choose M here: the
749 module will be called intelfb.
750
751config FB_INTEL_DEBUG
752 bool "Intel driver Debug Messages"
753 depends on FB_INTEL
754 ---help---
755 Say Y here if you want the Intel driver to output all sorts
756 of debugging informations to provide to the maintainer when
757 something goes wrong.
758
759config FB_MATROX
760 tristate "Matrox acceleration"
761 depends on FB && PCI
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
765 select FB_SOFT_CURSOR
766 select FB_TILEBLITTING
767 select FB_MACMODES if PPC_PMAC
768 ---help---
769 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
770 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
771 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
772 Matrox G400, G450 or G550 card in your box.
773
774 To compile this driver as a module, choose M here: the
775 module will be called matroxfb.
776
777 You can pass several parameters to the driver at boot time or at
778 module load time. The parameters look like "video=matrox:XXX", and
779 are described in <file:Documentation/fb/matroxfb.txt>.
780
781config FB_MATROX_MILLENIUM
782 bool "Millennium I/II support"
783 depends on FB_MATROX
784 help
785 Say Y here if you have a Matrox Millennium or Matrox Millennium II
786 video card. If you select "Advanced lowlevel driver options" below,
787 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
788 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
789 also use font widths different from 8.
790
791config FB_MATROX_MYSTIQUE
792 bool "Mystique support"
793 depends on FB_MATROX
794 help
795 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
796 video card. If you select "Advanced lowlevel driver options" below,
797 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
798 packed pixel and 32 bpp packed pixel. You can also use font widths
799 different from 8.
800
801config FB_MATROX_G
802 bool "G100/G200/G400/G450/G550 support"
803 depends on FB_MATROX
804 ---help---
805 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
806 video card. If you select "Advanced lowlevel driver options", you
807 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
808 pixel and 32 bpp packed pixel. You can also use font widths
809 different from 8.
810
811 If you need support for G400 secondary head, you must first say Y to
812 "I2C support" in the character devices section, and then to
813 "Matrox I2C support" and "G400 second head support" here in the
814 framebuffer section. G450/G550 secondary head and digital output
815 are supported without additional modules.
816
817 The driver starts in monitor mode. You must use the matroxset tool
818 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
819 swap primary and secondary head outputs, or to change output mode.
820 Secondary head driver always start in 640x480 resolution and you
821 must use fbset to change it.
822
823 Do not forget that second head supports only 16 and 32 bpp
824 packed pixels, so it is a good idea to compile them into the kernel
825 too. You can use only some font widths, as the driver uses generic
826 painting procedures (the secondary head does not use acceleration
827 engine).
828
829 G450/G550 hardware can display TV picture only from secondary CRTC,
830 and it performs no scaling, so picture must have 525 or 625 lines.
831
832config FB_MATROX_I2C
833 tristate "Matrox I2C support"
834 depends on FB_MATROX && I2C
835 select I2C_ALGOBIT
836 ---help---
837 This drivers creates I2C buses which are needed for accessing the
838 DDC (I2C) bus present on all Matroxes, an I2C bus which
839 interconnects Matrox optional devices, like MGA-TVO on G200 and
840 G400, and the secondary head DDC bus, present on G400 only.
841
842 You can say Y or M here if you want to experiment with monitor
843 detection code. You must say Y or M here if you want to use either
844 second head of G400 or MGA-TVO on G200 or G400.
845
846 If you compile it as module, it will create a module named
847 i2c-matroxfb.
848
849config FB_MATROX_MAVEN
850 tristate "G400 second head support"
851 depends on FB_MATROX_G && FB_MATROX_I2C
852 ---help---
853 WARNING !!! This support does not work with G450 !!!
854
855 Say Y or M here if you want to use a secondary head (meaning two
856 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
857 head is not compatible with accelerated XFree 3.3.x SVGA servers -
858 secondary head output is blanked while you are in X. With XFree
859 3.9.17 preview you can use both heads if you use SVGA over fbdev or
860 the fbdev driver on first head and the fbdev driver on second head.
861
862 If you compile it as module, two modules are created,
863 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
864 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
865 also load i2c-matroxfb to get it to run.
866
867 The driver starts in monitor mode and you must use the matroxset
868 tool (available at
869 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
870 PAL or NTSC or to swap primary and secondary head outputs.
871 Secondary head driver also always start in 640x480 resolution, you
872 must use fbset to change it.
873
874 Also do not forget that second head supports only 16 and 32 bpp
875 packed pixels, so it is a good idea to compile them into the kernel
876 too. You can use only some font widths, as the driver uses generic
877 painting procedures (the secondary head does not use acceleration
878 engine).
879
880config FB_MATROX_MULTIHEAD
881 bool "Multihead support"
882 depends on FB_MATROX
883 ---help---
884 Say Y here if you have more than one (supported) Matrox device in
885 your computer and you want to use all of them for different monitors
886 ("multihead"). If you have only one device, you should say N because
887 the driver compiled with Y is larger and a bit slower, especially on
888 ia32 (ix86).
889
890 If you said M to "Matrox unified accelerated driver" and N here, you
891 will still be able to use several Matrox devices simultaneously:
892 insert several instances of the module matroxfb into the kernel
893 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
894 for the different Matrox devices. This method is slightly faster but
895 uses 40 KB of kernel memory per Matrox card.
896
897 There is no need for enabling 'Matrox multihead support' if you have
898 only one Matrox card in the box.
899
900config FB_RADEON_OLD
901 tristate "ATI Radeon display support (Old driver)"
902 depends on FB && PCI
903 select FB_CFB_FILLRECT
904 select FB_CFB_COPYAREA
905 select FB_CFB_IMAGEBLIT
906 select FB_SOFT_CURSOR
907 select FB_MACMODES if PPC
908 help
909 Choose this option if you want to use an ATI Radeon graphics card as
910 a framebuffer device. There are both PCI and AGP versions. You
911 don't need to choose this to run the Radeon in plain VGA mode.
912 There is a product page at
913 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
914
915config FB_RADEON
916 tristate "ATI Radeon display support"
917 depends on FB && PCI
918 select I2C_ALGOBIT if FB_RADEON_I2C
919 select I2C if FB_RADEON_I2C
920 select FB_MODE_HELPERS
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
924 select FB_SOFT_CURSOR
925 select FB_MACMODES if PPC_OF
926 help
927 Choose this option if you want to use an ATI Radeon graphics card as
928 a framebuffer device. There are both PCI and AGP versions. You
929 don't need to choose this to run the Radeon in plain VGA mode.
930
931 If you say Y here and want DDC/I2C support you must first say Y to
932 "I2C support" and "I2C bit-banging support" in the character devices
933 section.
934
935 If you say M here then "I2C support" and "I2C bit-banging support"
936 can be build either as modules or built-in.
937
938 There is a product page at
939 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
940
941config FB_RADEON_I2C
942 bool "DDC/I2C for ATI Radeon support"
943 depends on FB_RADEON
944 default y
945 help
946 Say Y here if you want DDC/I2C support for your Radeon board.
947
948config FB_RADEON_DEBUG
949 bool "Lots of debug output from Radeon driver"
950 depends on FB_RADEON
951 default n
952 help
953 Say Y here if you want the Radeon driver to output all sorts
954 of debugging informations to provide to the maintainer when
955 something goes wrong.
956
957config FB_ATY128
958 tristate "ATI Rage128 display support"
959 depends on FB && PCI
960 select FB_CFB_FILLRECT
961 select FB_CFB_COPYAREA
962 select FB_CFB_IMAGEBLIT
963 select FB_SOFT_CURSOR
964 select FB_MACMODES if PPC_PMAC
965 help
966 This driver supports graphics boards with the ATI Rage128 chips.
967 Say Y if you have such a graphics board and read
968 <file:Documentation/fb/aty128fb.txt>.
969
970 To compile this driver as a module, choose M here: the
971 module will be called aty128fb.
972
973config FB_ATY
974 tristate "ATI Mach64 display support" if PCI || ATARI
975 depends on FB
976 select FB_CFB_FILLRECT
977 select FB_CFB_COPYAREA
978 select FB_CFB_IMAGEBLIT
979 select FB_SOFT_CURSOR
980 select FB_MACMODES if PPC
981 help
982 This driver supports graphics boards with the ATI Mach64 chips.
983 Say Y if you have such a graphics board.
984
985 To compile this driver as a module, choose M here: the
986 module will be called atyfb.
987
988config FB_ATY_CT
989 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
990 depends on PCI && FB_ATY
991 default y if SPARC64 && FB_PCI
992 help
993 Say Y here to support use of ATI's 64-bit Rage boards (or other
994 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
995 framebuffer device. The ATI product support page for these boards
996 is at <http://support.ati.com/products/pc/mach64/>.
997
998config FB_ATY_GENERIC_LCD
999 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1000 depends on FB_ATY_CT
1001 help
1002 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1003 Rage XC, or Rage XL chipset.
1004
1005config FB_ATY_XL_INIT
1006 bool "Rage XL No-BIOS Init support"
1007 depends on FB_ATY_CT
1008 help
1009 Say Y here to support booting a Rage XL without BIOS support.
1010
1011config FB_ATY_GX
1012 bool "Mach64 GX support" if PCI
1013 depends on FB_ATY
1014 default y if ATARI
1015 help
1016 Say Y here to support use of the ATI Mach64 Graphics Expression
1017 board (or other boards based on the Mach64 GX chipset) as a
1018 framebuffer device. The ATI product support page for these boards
1019 is at
1020 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1021
1022config FB_SAVAGE
1023 tristate "S3 Savage support"
1024 depends on FB && PCI && EXPERIMENTAL
1025 select I2C_ALGOBIT if FB_SAVAGE_I2C
1026 select I2C if FB_SAVAGE_I2C
1027 select FB_MODE_HELPERS
1028 select FB_CFB_FILLRECT
1029 select FB_CFB_COPYAREA
1030 select FB_CFB_IMAGEBLIT
1031 select FB_SOFT_CURSOR
1032 help
1033 This driver supports notebooks and computers with S3 Savage PCI/AGP
1034 chips.
1035
1036 Say Y if you have such a graphics card.
1037
1038 To compile this driver as a module, choose M here; the module
1039 will be called savagefb.
1040
1041config FB_SAVAGE_I2C
1042 bool "Enable DDC2 Support"
1043 depends on FB_SAVAGE
1044 help
1045 This enables I2C support for S3 Savage Chipsets. This is used
1046 only for getting EDID information from the attached display
1047 allowing for robust video mode handling and switching.
1048
1049 Because fbdev-2.6 requires that drivers must be able to
1050 independently validate video mode parameters, you should say Y
1051 here.
1052
1053config FB_SAVAGE_ACCEL
1054 bool "Enable Console Acceleration"
1055 depends on FB_SAVAGE
1056 default n
1057 help
1058 This option will compile in console acceleration support. If
1059 the resulting framebuffer console has bothersome glitches, then
1060 choose N here.
1061
1062config FB_SIS
1063 tristate "SiS acceleration"
1064 depends on FB && PCI
1065 select FB_CFB_FILLRECT
1066 select FB_CFB_COPYAREA
1067 select FB_CFB_IMAGEBLIT
1068 select FB_SOFT_CURSOR
1069 help
1070 This is the frame buffer device driver for the SiS 300, 315 and
1071 330 series VGA chipsets. Specs available at <http://www.sis.com>
1072
1073 To compile this driver as a module, choose M here; the module
1074 will be called sisfb.
1075
1076config FB_SIS_300
1077 bool "SiS 300 series support"
1078 depends on FB_SIS
1079 help
1080 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1081
1082config FB_SIS_315
1083 bool "SiS 315/330 series support"
1084 depends on FB_SIS
1085 help
1086 Say Y here to support use of the SiS 315 and 330 series
1087 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760).
1088
1089config FB_NEOMAGIC
1090 tristate "NeoMagic display support"
1091 depends on FB && PCI
1092 select FB_MODE_HELPERS
1093 select FB_CFB_FILLRECT
1094 select FB_CFB_COPYAREA
1095 select FB_CFB_IMAGEBLIT
1096 select FB_SOFT_CURSOR
1097 help
1098 This driver supports notebooks with NeoMagic PCI chips.
1099 Say Y if you have such a graphics card.
1100
1101 To compile this driver as a module, choose M here: the
1102 module will be called neofb.
1103
1104config FB_KYRO
1105 tristate "IMG Kyro support"
1106 depends on FB && PCI
1107 select FB_CFB_FILLRECT
1108 select FB_CFB_COPYAREA
1109 select FB_CFB_IMAGEBLIT
1110 select FB_SOFT_CURSOR
1111 help
1112 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1113 graphics board.
1114
1115 To compile this driver as a module, choose M here: the
1116 module will be called kyrofb.
1117
1118config FB_3DFX
1119 tristate "3Dfx Banshee/Voodoo3 display support"
1120 depends on FB && PCI
1121 select FB_CFB_IMAGEBLIT
1122 select FB_CFB_FILLRECT
1123 select FB_CFB_COPYAREA
1124 select FB_SOFT_CURSOR
1125 help
1126 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1127 chips. Say Y if you have such a graphics board.
1128
1129 To compile this driver as a module, choose M here: the
1130 module will be called tdfxfb.
1131
1132config FB_3DFX_ACCEL
1133 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1134 depends on FB_3DFX && EXPERIMENTAL
1135 ---help---
1136 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1137 with acceleration functions.
1138
1139
1140config FB_VOODOO1
1141 tristate "3Dfx Voodoo Graphics (sst1) support"
1142 depends on FB && PCI
1143 select FB_CFB_FILLRECT
1144 select FB_CFB_COPYAREA
1145 select FB_CFB_IMAGEBLIT
1146 select FB_SOFT_CURSOR
1147 ---help---
1148 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1149 Voodoo2 (cvg) based graphics card.
1150
1151 To compile this driver as a module, choose M here: the
1152 module will be called sstfb.
1153
1154 WARNING: Do not use any application that uses the 3D engine
1155 (namely glide) while using this driver.
1156 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1157 options and other important info support.
1158
1159config FB_TRIDENT
1160 tristate "Trident support"
1161 depends on FB && PCI
1162 select FB_CFB_FILLRECT
1163 select FB_CFB_COPYAREA
1164 select FB_CFB_IMAGEBLIT
1165 select FB_SOFT_CURSOR
1166 ---help---
1167 This driver is supposed to support graphics boards with the
1168 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1169 but also on some motherboards. For more information, read
1170 <file:Documentation/fb/tridentfb.txt>
1171
1172 Say Y if you have such a graphics board.
1173
1174 To compile this driver as a module, choose M here: the
1175 module will be called tridentfb.
1176
1177config FB_TRIDENT_ACCEL
1178 bool "Trident Acceleration functions (EXPERIMENTAL)"
1179 depends on FB_TRIDENT && EXPERIMENTAL
1180 ---help---
1181 This will compile the Trident frame buffer device with
1182 acceleration functions.
1183
1184
1185config FB_PM3
1186 tristate "Permedia3 support"
1187 depends on FB && PCI && BROKEN
1188 help
1189 This is the frame buffer device driver for the 3DLabs Permedia3
1190 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1191 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1192 and maybe other boards.
1193
1194config FB_E1356
1195 tristate "Epson SED1356 framebuffer support"
1196 depends on FB && EXPERIMENTAL && PCI && MIPS
1197
1198config PB1000_CRT
1199 bool "Use CRT on Pb1000 (J65)"
1200 depends on MIPS_PB1000=y && FB_E1356
1201
1202config PB1000_NTSC
1203 bool "Use Compsite NTSC on Pb1000 (J63)"
1204 depends on MIPS_PB1000=y && FB_E1356
1205
1206config PB1000_TFT
1207 bool "Use TFT Panel on Pb1000 (J64)"
1208 depends on MIPS_PB1000=y && FB_E1356
1209
1210config PB1500_CRT
1211 bool "Use CRT on Pb1500 " if MIPS_PB1500=y
1212 depends on FB_E1356
1213
1214config PB1500_CRT
1215 prompt "Use CRT on Pb1100 "
1216 depends on FB_E1356 && MIPS_PB1100=y
1217
1218config PB1500_TFT
1219 bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y
1220 depends on FB_E1356
1221
1222config PB1500_TFT
1223 prompt "Use TFT Panel on Pb1100 "
1224 depends on FB_E1356 && MIPS_PB1100=y
1225
1226config FB_AU1100
1227 bool "Au1100 LCD Driver"
1228 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1229
1230source "drivers/video/geode/Kconfig"
1231
1232config FB_SBUS
1233 bool "SBUS and UPA framebuffers"
1234 depends on (FB = y) && (SPARC32 || SPARC64)
1235 help
1236 Say Y if you want support for SBUS or UPA based frame buffer device.
1237
1238config FB_FFB
1239 bool "Creator/Creator3D/Elite3D support"
1240 depends on FB_SBUS && SPARC64
1241 select FB_CFB_COPYAREA
1242 select FB_CFB_IMAGEBLIT
1243 select FB_SOFT_CURSOR
1244 help
1245 This is the frame buffer device driver for the Creator, Creator3D,
1246 and Elite3D graphics boards.
1247
1248config FB_TCX
1249 bool "TCX (SS4/SS5 only) support"
1250 depends on FB_SBUS
1251 select FB_CFB_FILLRECT
1252 select FB_CFB_COPYAREA
1253 select FB_CFB_IMAGEBLIT
1254 select FB_SOFT_CURSOR
1255 help
1256 This is the frame buffer device driver for the TCX 24/8bit frame
1257 buffer.
1258
1259config FB_CG14
1260 bool "CGfourteen (SX) support"
1261 depends on FB_SBUS
1262 select FB_CFB_FILLRECT
1263 select FB_CFB_COPYAREA
1264 select FB_CFB_IMAGEBLIT
1265 select FB_SOFT_CURSOR
1266 help
1267 This is the frame buffer device driver for the CGfourteen frame
1268 buffer on Desktop SPARCsystems with the SX graphics option.
1269
1270config FB_P9100
1271 bool "P9100 (Sparcbook 3 only) support"
1272 depends on FB_SBUS
1273 select FB_CFB_FILLRECT
1274 select FB_CFB_COPYAREA
1275 select FB_CFB_IMAGEBLIT
1276 select FB_SOFT_CURSOR
1277 help
1278 This is the frame buffer device driver for the P9100 card
1279 supported on Sparcbook 3 machines.
1280
1281config FB_LEO
1282 bool "Leo (ZX) support"
1283 depends on FB_SBUS
1284 select FB_CFB_FILLRECT
1285 select FB_CFB_COPYAREA
1286 select FB_CFB_IMAGEBLIT
1287 select FB_SOFT_CURSOR
1288 help
1289 This is the frame buffer device driver for the SBUS-based Sun ZX
1290 (leo) frame buffer cards.
1291
1292config FB_PCI
1293 bool "PCI framebuffers"
1294 depends on (FB = y) && PCI && (SPARC64 || SPARC32)
1295
1296config FB_IGA
1297 bool "IGA 168x display support"
1298 depends on SPARC32 && FB_PCI
1299 select FB_CFB_FILLRECT
1300 select FB_CFB_COPYAREA
1301 select FB_CFB_IMAGEBLIT
1302 select FB_SOFT_CURSOR
1303 help
1304 This is the framebuffer device for the INTERGRAPHICS 1680 and
1305 successor frame buffer cards.
1306
1307config FB_HIT
1308 tristate "HD64461 Frame Buffer support"
1309 depends on FB && HD64461
1310 select FB_CFB_FILLRECT
1311 select FB_CFB_COPYAREA
1312 select FB_CFB_IMAGEBLIT
1313 select FB_SOFT_CURSOR
1314 help
1315 This is the frame buffer device driver for the Hitachi HD64461 LCD
1316 frame buffer card.
1317
1318config FB_PMAG_AA
1319 bool "PMAG-AA TURBOchannel framebuffer support"
1320 depends on (FB = y) && MACH_DECSTATION && TC
1321 select FB_CFB_FILLRECT
1322 select FB_CFB_COPYAREA
1323 select FB_CFB_IMAGEBLIT
1324 select FB_SOFT_CURSOR
1325 help
1326 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1327 used mainly in the MIPS-based DECstation series.
1328
1329config FB_PMAG_BA
1330 bool "PMAG-BA TURBOchannel framebuffer support"
1331 depends on (FB = y) && MACH_DECSTATION && TC
1332 select FB_CFB_FILLRECT
1333 select FB_CFB_COPYAREA
1334 select FB_CFB_IMAGEBLIT
1335 select FB_SOFT_CURSOR
1336 help
1337 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1338 used mainly in the MIPS-based DECstation series.
1339
1340config FB_PMAGB_B
1341 bool "PMAGB-B TURBOchannel framebuffer support"
1342 depends on (FB = y) && MACH_DECSTATION && TC
1343 select FB_CFB_FILLRECT
1344 select FB_CFB_COPYAREA
1345 select FB_CFB_IMAGEBLIT
1346 select FB_SOFT_CURSOR
1347 help
1348 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1349 in the MIPS-based DECstation series. The card is currently only
1350 supported in 1280x1024x8 mode.
1351
1352config FB_MAXINE
1353 bool "Maxine (Personal DECstation) onboard framebuffer support"
1354 depends on (FB = y) && MACH_DECSTATION && TC
1355 select FB_CFB_FILLRECT
1356 select FB_CFB_COPYAREA
1357 select FB_CFB_IMAGEBLIT
1358 select FB_SOFT_CURSOR
1359 help
1360 Support for the onboard framebuffer (1024x768x8) in the Personal
1361 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1362 Codename "Maxine").
1363
1364config FB_TX3912
1365 bool "TMPTX3912/PR31700 frame buffer support"
1366 depends on (FB = y) && NINO
1367 select FB_CFB_FILLRECT
1368 select FB_CFB_COPYAREA
1369 select FB_CFB_IMAGEBLIT
1370 select FB_SOFT_CURSOR
1371 help
1372 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1373 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1374
1375 Say Y here to enable kernel support for the on-board framebuffer.
1376
1377config FB_G364
1378 bool
1379 depends on MIPS_MAGNUM_4000 || OLIVETTI_M700
1380 select FB_CFB_FILLRECT
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1383 select FB_SOFT_CURSOR
1384 help
1385 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1386 Olivetti M700-10 systems.
1387
1388config FB_68328
1389 bool "Motorola 68328 native frame buffer support"
1390 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1391 select FB_CFB_FILLRECT
1392 select FB_CFB_COPYAREA
1393 select FB_CFB_IMAGEBLIT
1394 select FB_SOFT_CURSOR
1395 help
1396 Say Y here if you want to support the built-in frame buffer of
1397 the Motorola 68328 CPU family.
1398
1399config FB_PXA
1400 tristate "PXA LCD framebuffer support"
1401 depends on FB && ARCH_PXA
1402 select FB_CFB_FILLRECT
1403 select FB_CFB_COPYAREA
1404 select FB_CFB_IMAGEBLIT
1405 select FB_SOFT_CURSOR
1406 ---help---
1407 Frame buffer driver for the built-in LCD controller in the Intel
1408 PXA2x0 processor.
1409
1410 This driver is also available as a module ( = code which can be
1411 inserted and removed from the running kernel whenever you want). The
1412 module will be called vfb. If you want to compile it as a module,
1413 say M here and read <file:Documentation/modules.txt>.
1414
1415 If unsure, say N.
1416
1417config FB_W100
1418 tristate "W100 frame buffer support"
1419 depends on FB && PXA_SHARPSL
1420 select FB_CFB_FILLRECT
1421 select FB_CFB_COPYAREA
1422 select FB_CFB_IMAGEBLIT
1423 select FB_SOFT_CURSOR
1424 ---help---
1425 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1426
1427 This driver is also available as a module ( = code which can be
1428 inserted and removed from the running kernel whenever you want). The
1429 module will be called vfb. If you want to compile it as a module,
1430 say M here and read <file:Documentation/modules.txt>.
1431
1432 If unsure, say N.
1433
1434config FB_PXA_PARAMETERS
1435 bool "PXA LCD command line parameters"
1436 default n
1437 depends on FB_PXA
1438 ---help---
1439 Enable the use of kernel command line or module parameters
1440 to configure the physical properties of the LCD panel when
1441 using the PXA LCD driver.
1442
1443 This option allows you to override the panel parameters
1444 supplied by the platform in order to support multiple
1445 different models of flatpanel. If you will only be using a
1446 single model of flatpanel then you can safely leave this
1447 option disabled.
1448
1449 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1450
1451config FB_S1D13XXX
1452 tristate "Epson S1D13XXX framebuffer support"
1453 depends on FB
1454 select FB_CFB_FILLRECT
1455 select FB_CFB_COPYAREA
1456 select FB_CFB_IMAGEBLIT
1457 select FB_SOFT_CURSOR
1458 help
1459 Support for S1D13XXX framebuffer device family (currently only
1460 working with S1D13806). Product specs at
1461 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
1462
1463config FB_VIRTUAL
1464 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1465 depends on FB
1466 select FB_CFB_FILLRECT
1467 select FB_CFB_COPYAREA
1468 select FB_CFB_IMAGEBLIT
1469 select FB_SOFT_CURSOR
1470 ---help---
1471 This is a `virtual' frame buffer device. It operates on a chunk of
1472 unswappable kernel memory instead of on the memory of a graphics
1473 board. This means you cannot see any output sent to this frame
1474 buffer device, while it does consume precious memory. The main use
1475 of this frame buffer device is testing and debugging the frame
1476 buffer subsystem. Do NOT enable it for normal systems! To protect
1477 the innocent, it has to be enabled explicitly at boot time using the
1478 kernel option `video=vfb:'.
1479
1480 To compile this driver as a module, choose M here: the
1481 module will be called vfb.
1482
1483 If unsure, say N.
1484if VT
1485 source "drivers/video/console/Kconfig"
1486endif
1487
1488if FB || SGI_NEWPORT_CONSOLE
1489 source "drivers/video/logo/Kconfig"
1490endif
1491
1492if FB && SYSFS
1493 source "drivers/video/backlight/Kconfig"
1494endif
1495
1496endmenu
1497
generated by cgit v1.2.2 (git 2.25.0) at 2024-11-08 17:14:51 -0500