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