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