ia64/xen-unstable

view linux-2.6-xen-sparse/drivers/video/Kconfig @ 13348:761f695043ff

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