| blob | 3f6ae833549bd7137d4cb3b44091d7c7dc14a252 |
1 #
2 # Video configuration
3 #
5 menu "Graphics support"
6 depends on HAS_IOMEM
8 source "drivers/char/agp/Kconfig"
10 source "drivers/char/drm/Kconfig"
12 config VGASTATE
13 tristate
14 default n
16 config VIDEO_OUTPUT_CONTROL
17 tristate "Lowlevel video output switch controls"
18 help
19 This framework adds support for low-level control of the video
20 output switch.
22 menuconfig FB
23 tristate "Support for frame buffer devices"
24 ---help---
25 The frame buffer device provides an abstraction for the graphics
26 hardware. It represents the frame buffer of some video hardware and
27 allows application software to access the graphics hardware through
28 a well-defined interface, so the software doesn't need to know
29 anything about the low-level (hardware register) stuff.
31 Frame buffer devices work identically across the different
32 architectures supported by Linux and make the implementation of
33 application programs easier and more portable; at this point, an X
34 server exists which uses the frame buffer device exclusively.
35 On several non-X86 architectures, the frame buffer device is the
36 only way to use the graphics hardware.
38 The device is accessed through special device nodes, usually located
39 in the /dev directory, i.e. /dev/fb*.
41 You need an utility program called fbset to make full use of frame
42 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
43 and the Framebuffer-HOWTO at
44 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
45 information.
47 Say Y here and to the driver for your graphics board below if you
48 are compiling a kernel for a non-x86 architecture.
50 If you are compiling for the x86 architecture, you can say Y if you
51 want to play with it, but it is not essential. Please note that
52 running graphical applications that directly touch the hardware
53 (e.g. an accelerated X server) and that are not frame buffer
54 device-aware may cause unexpected results. If unsure, say N.
56 config FIRMWARE_EDID
57 bool "Enable firmware EDID"
58 depends on FB
59 default n
60 ---help---
61 This enables access to the EDID transferred from the firmware.
62 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
63 transfers do not work for your driver and if you are using
64 nvidiafb, i810fb or savagefb.
66 In general, choosing Y for this option is safe. If you
67 experience extremely long delays while booting before you get
68 something on your display, try setting this to N. Matrox cards in
69 combination with certain motherboards and monitors are known to
70 suffer from this problem.
72 config FB_DDC
73 tristate
74 depends on FB
75 select I2C_ALGOBIT
76 select I2C
77 default n
79 config FB_CFB_FILLRECT
80 tristate
81 depends on FB
82 default n
83 ---help---
84 Include the cfb_fillrect function for generic software rectangle
85 filling. This is used by drivers that don't provide their own
86 (accelerated) version.
88 config FB_CFB_COPYAREA
89 tristate
90 depends on FB
91 default n
92 ---help---
93 Include the cfb_copyarea function for generic software area copying.
94 This is used by drivers that don't provide their own (accelerated)
95 version.
97 config FB_CFB_IMAGEBLIT
98 tristate
99 depends on FB
100 default n
101 ---help---
102 Include the cfb_imageblit function for generic software image
103 blitting. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_REV_PIXELS_IN_BYTE
107 bool
108 depends on FB
109 default n
110 ---help---
111 Allow generic frame-buffer functions to work on displays with 1, 2
112 and 4 bits per pixel depths which has opposite order of pixels in
113 byte order to bytes in long order.
115 config FB_SYS_FILLRECT
116 tristate
117 depends on FB
118 default n
119 ---help---
120 Include the sys_fillrect function for generic software rectangle
121 filling. This is used by drivers that don't provide their own
122 (accelerated) version and the framebuffer is in system RAM.
124 config FB_SYS_COPYAREA
125 tristate
126 depends on FB
127 default n
128 ---help---
129 Include the sys_copyarea function for generic software area copying.
130 This is used by drivers that don't provide their own (accelerated)
131 version and the framebuffer is in system RAM.
133 config FB_SYS_IMAGEBLIT
134 tristate
135 depends on FB
136 default n
137 ---help---
138 Include the sys_imageblit function for generic software image
139 blitting. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 config FB_SYS_FOPS
143 tristate
144 depends on FB
145 default n
147 config FB_DEFERRED_IO
148 bool
149 depends on FB
150 default y
152 config FB_SVGALIB
153 tristate
154 depends on FB
155 default n
156 ---help---
157 Common utility functions useful to fbdev drivers of VGA-based
158 cards.
160 config FB_MACMODES
161 tristate
162 depends on FB
163 default n
165 config FB_BACKLIGHT
166 bool
167 depends on FB
168 select BACKLIGHT_LCD_SUPPORT
169 select BACKLIGHT_CLASS_DEVICE
170 default n
172 config FB_MODE_HELPERS
173 bool "Enable Video Mode Handling Helpers"
174 depends on FB
175 default n
176 ---help---
177 This enables functions for handling video modes using the
178 Generalized Timing Formula and the EDID parser. A few drivers rely
179 on this feature such as the radeonfb, rivafb, and the i810fb. If
180 your driver does not take advantage of this feature, choosing Y will
181 just increase the kernel size by about 5K.
183 config FB_TILEBLITTING
184 bool "Enable Tile Blitting Support"
185 depends on FB
186 default n
187 ---help---
188 This enables tile blitting. Tile blitting is a drawing technique
189 where the screen is divided into rectangular sections (tiles), whereas
190 the standard blitting divides the screen into pixels. Because the
191 default drawing element is a tile, drawing functions will be passed
192 parameters in terms of number of tiles instead of number of pixels.
193 For example, to draw a single character, instead of using bitmaps,
194 an index to an array of bitmaps will be used. To clear or move a
195 rectangular section of a screen, the rectangle will be described in
196 terms of number of tiles in the x- and y-axis.
198 This is particularly important to one driver, matroxfb. If
199 unsure, say N.
201 comment "Frame buffer hardware drivers"
202 depends on FB
204 config FB_CIRRUS
205 tristate "Cirrus Logic support"
206 depends on FB && (ZORRO || PCI)
207 select FB_CFB_FILLRECT
208 select FB_CFB_COPYAREA
209 select FB_CFB_IMAGEBLIT
210 ---help---
211 This enables support for Cirrus Logic GD542x/543x based boards on
212 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
214 If you have a PCI-based system, this enables support for these
215 chips: GD-543x, GD-544x, GD-5480.
217 Please read the file <file:Documentation/fb/cirrusfb.txt>.
219 Say N unless you have such a graphics board or plan to get one
220 before you next recompile the kernel.
222 config FB_PM2
223 tristate "Permedia2 support"
224 depends on FB && ((AMIGA && BROKEN) || PCI)
225 select FB_CFB_FILLRECT
226 select FB_CFB_COPYAREA
227 select FB_CFB_IMAGEBLIT
228 help
229 This is the frame buffer device driver for the Permedia2 AGP frame
230 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
231 product page at
232 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
234 config FB_PM2_FIFO_DISCONNECT
235 bool "enable FIFO disconnect feature"
236 depends on FB_PM2 && PCI
237 help
238 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
240 config FB_ARMCLCD
241 tristate "ARM PrimeCell PL110 support"
242 depends on FB && ARM && ARM_AMBA
243 select FB_CFB_FILLRECT
244 select FB_CFB_COPYAREA
245 select FB_CFB_IMAGEBLIT
246 help
247 This framebuffer device driver is for the ARM PrimeCell PL110
248 Colour LCD controller. ARM PrimeCells provide the building
249 blocks for System on a Chip devices.
251 If you want to compile this as a module (=code which can be
252 inserted into and removed from the running kernel), say M
253 here and read <file:Documentation/kbuild/modules.txt>. The module
254 will be called amba-clcd.
256 choice
258 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
259 prompt "LCD Panel"
260 default FB_ARMCLCD_SHARP_LQ035Q7DB02
262 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
263 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
264 help
265 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
266 color QVGA, HRTFT panel. The LogicPD device includes
267 an integrated HRTFT controller IC.
268 The native resolution is 240x320.
270 config FB_ARMCLCD_SHARP_LQ057Q3DC02
271 bool "LogicPD LCD 5.7\" QVGA"
272 help
273 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
274 color QVGA, TFT panel. The LogicPD device includes an
275 The native resolution is 320x240.
277 config FB_ARMCLCD_SHARP_LQ64D343
278 bool "LogicPD LCD 6.4\" VGA"
279 help
280 This is an implementation of the Sharp LQ64D343, a 6.4"
281 color VGA, TFT panel. The LogicPD device includes an
282 The native resolution is 640x480.
284 config FB_ARMCLCD_SHARP_LQ10D368
285 bool "LogicPD LCD 10.4\" VGA"
286 help
287 This is an implementation of the Sharp LQ10D368, a 10.4"
288 color VGA, TFT panel. The LogicPD device includes an
289 The native resolution is 640x480.
292 config FB_ARMCLCD_SHARP_LQ121S1DG41
293 bool "LogicPD LCD 12.1\" SVGA"
294 help
295 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
296 color SVGA, TFT panel. The LogicPD device includes an
297 The native resolution is 800x600.
299 This panel requires a clock rate may be an integer fraction
300 of the base LCDCLK frequency. The driver will select the
301 highest frequency available that is lower than the maximum
302 allowed. The panel may flicker if the clock rate is
303 slower than the recommended minimum.
305 config FB_ARMCLCD_AUO_A070VW01_WIDE
306 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
307 help
308 This is an implementation of the AU Optronics, a 7.0"
309 WIDE Color. The native resolution is 234x480.
311 config FB_ARMCLCD_HITACHI
312 bool "Hitachi Wide Screen 800x480"
313 help
314 This is an implementation of the Hitachi 800x480.
316 endchoice
319 config FB_ACORN
320 bool "Acorn VIDC support"
321 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
322 select FB_CFB_FILLRECT
323 select FB_CFB_COPYAREA
324 select FB_CFB_IMAGEBLIT
325 help
326 This is the frame buffer device driver for the Acorn VIDC graphics
327 hardware found in Acorn RISC PCs and other ARM-based machines. If
328 unsure, say N.
330 config FB_CLPS711X
331 bool "CLPS711X LCD support"
332 depends on (FB = y) && ARM && ARCH_CLPS711X
333 select FB_CFB_FILLRECT
334 select FB_CFB_COPYAREA
335 select FB_CFB_IMAGEBLIT
336 help
337 Say Y to enable the Framebuffer driver for the CLPS7111 and
338 EP7212 processors.
340 config FB_SA1100
341 bool "SA-1100 LCD support"
342 depends on (FB = y) && ARM && ARCH_SA1100
343 select FB_CFB_FILLRECT
344 select FB_CFB_COPYAREA
345 select FB_CFB_IMAGEBLIT
346 help
347 This is a framebuffer device for the SA-1100 LCD Controller.
348 See <http://www.linux-fbdev.org/> for information on framebuffer
349 devices.
351 If you plan to use the LCD display with your SA-1100 system, say
352 Y here.
354 config FB_IMX
355 tristate "Motorola i.MX LCD support"
356 depends on FB && ARM && ARCH_IMX
357 select FB_CFB_FILLRECT
358 select FB_CFB_COPYAREA
359 select FB_CFB_IMAGEBLIT
361 config FB_CYBER2000
362 tristate "CyberPro 2000/2010/5000 support"
363 depends on FB && PCI && (BROKEN || !SPARC64)
364 select FB_CFB_FILLRECT
365 select FB_CFB_COPYAREA
366 select FB_CFB_IMAGEBLIT
367 help
368 This enables support for the Integraphics CyberPro 20x0 and 5000
369 VGA chips used in the Rebel.com Netwinder and other machines.
370 Say Y if you have a NetWinder or a graphics card containing this
371 device, otherwise say N.
373 config FB_APOLLO
374 bool
375 depends on (FB = y) && APOLLO
376 default y
377 select FB_CFB_FILLRECT
378 select FB_CFB_IMAGEBLIT
380 config FB_Q40
381 bool
382 depends on (FB = y) && Q40
383 default y
384 select FB_CFB_FILLRECT
385 select FB_CFB_COPYAREA
386 select FB_CFB_IMAGEBLIT
388 config FB_AMIGA
389 tristate "Amiga native chipset support"
390 depends on FB && AMIGA
391 help
392 This is the frame buffer device driver for the builtin graphics
393 chipset found in Amigas.
395 To compile this driver as a module, choose M here: the
396 module will be called amifb.
398 config FB_AMIGA_OCS
399 bool "Amiga OCS chipset support"
400 depends on FB_AMIGA
401 help
402 This enables support for the original Agnus and Denise video chips,
403 found in the Amiga 1000 and most A500's and A2000's. If you intend
404 to run Linux on any of these systems, say Y; otherwise say N.
406 config FB_AMIGA_ECS
407 bool "Amiga ECS chipset support"
408 depends on FB_AMIGA
409 help
410 This enables support for the Enhanced Chip Set, found in later
411 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
412 you intend to run Linux on any of these systems, say Y; otherwise
413 say N.
415 config FB_AMIGA_AGA
416 bool "Amiga AGA chipset support"
417 depends on FB_AMIGA
418 help
419 This enables support for the Advanced Graphics Architecture (also
420 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
421 and CD32. If you intend to run Linux on any of these systems, say Y;
422 otherwise say N.
424 config FB_FM2
425 bool "Amiga FrameMaster II/Rainbow II support"
426 depends on (FB = y) && ZORRO
427 select FB_CFB_FILLRECT
428 select FB_CFB_COPYAREA
429 select FB_CFB_IMAGEBLIT
430 help
431 This is the frame buffer device driver for the Amiga FrameMaster
432 card from BSC (exhibited 1992 but not shipped as a CBM product).
434 config FB_ARC
435 tristate "Arc Monochrome LCD board support"
436 depends on FB && X86
437 select FB_SYS_FILLRECT
438 select FB_SYS_COPYAREA
439 select FB_SYS_IMAGEBLIT
440 select FB_SYS_FOPS
441 help
442 This enables support for the Arc Monochrome LCD board. The board
443 is based on the KS-108 lcd controller and is typically a matrix
444 of 2*n chips. This driver was tested with a 128x64 panel. This
445 driver supports it for use with x86 SBCs through a 16 bit GPIO
446 interface (8 bit data, 8 bit control). If you anticipate using
447 this driver, say Y or M; otherwise say N. You must specify the
448 GPIO IO address to be used for setting control and data.
450 config FB_ATARI
451 bool "Atari native chipset support"
452 depends on (FB = y) && ATARI
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
456 help
457 This is the frame buffer device driver for the builtin graphics
458 chipset found in Ataris.
460 config FB_OF
461 bool "Open Firmware frame buffer device support"
462 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
466 select FB_MACMODES
467 help
468 Say Y if you want support with Open Firmware for your graphics
469 board.
471 config FB_CONTROL
472 bool "Apple \"control\" display support"
473 depends on (FB = y) && PPC_PMAC && PPC32
474 select FB_CFB_FILLRECT
475 select FB_CFB_COPYAREA
476 select FB_CFB_IMAGEBLIT
477 select FB_MACMODES
478 help
479 This driver supports a frame buffer for the graphics adapter in the
480 Power Macintosh 7300 and others.
482 config FB_PLATINUM
483 bool "Apple \"platinum\" display support"
484 depends on (FB = y) && PPC_PMAC && PPC32
485 select FB_CFB_FILLRECT
486 select FB_CFB_COPYAREA
487 select FB_CFB_IMAGEBLIT
488 select FB_MACMODES
489 help
490 This driver supports a frame buffer for the "platinum" graphics
491 adapter in some Power Macintoshes.
493 config FB_VALKYRIE
494 bool "Apple \"valkyrie\" display support"
495 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
496 select FB_CFB_FILLRECT
497 select FB_CFB_COPYAREA
498 select FB_CFB_IMAGEBLIT
499 select FB_MACMODES
500 help
501 This driver supports a frame buffer for the "valkyrie" graphics
502 adapter in some Power Macintoshes.
504 config FB_CT65550
505 bool "Chips 65550 display support"
506 depends on (FB = y) && PPC32 && PCI
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
510 help
511 This is the frame buffer device driver for the Chips & Technologies
512 65550 graphics chip in PowerBooks.
514 config FB_ASILIANT
515 bool "Asiliant (Chips) 69000 display support"
516 depends on (FB = y) && PCI
517 select FB_CFB_FILLRECT
518 select FB_CFB_COPYAREA
519 select FB_CFB_IMAGEBLIT
520 help
521 This is the frame buffer device driver for the Asiliant 69030 chipset
523 config FB_IMSTT
524 bool "IMS Twin Turbo display support"
525 depends on (FB = y) && PCI
526 select FB_CFB_IMAGEBLIT
527 select FB_MACMODES if PPC
528 help
529 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
530 many Macintosh and compatible computers.
532 config FB_VGA16
533 tristate "VGA 16-color graphics support"
534 depends on FB && (X86 || PPC)
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
538 select VGASTATE
539 select FONT_8x16 if FRAMEBUFFER_CONSOLE
540 help
541 This is the frame buffer device driver for VGA 16 color graphic
542 cards. Say Y if you have such a card.
544 To compile this driver as a module, choose M here: the
545 module will be called vga16fb.
547 config FB_BF54X_LQ043
548 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
549 depends on FB && (BF54x)
550 select FB_CFB_FILLRECT
551 select FB_CFB_COPYAREA
552 select FB_CFB_IMAGEBLIT
553 help
554 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
556 <<<<<<< HEAD:drivers/video/Kconfig
557 =======
558 config FB_BFIN_T350MCQB
559 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
560 depends on FB && BLACKFIN
561 select BFIN_GPTIMERS
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
565 help
566 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
567 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
568 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
571 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/video/Kconfig
572 config FB_STI
573 tristate "HP STI frame buffer device support"
574 depends on FB && PARISC
575 select FB_CFB_FILLRECT
576 select FB_CFB_COPYAREA
577 select FB_CFB_IMAGEBLIT
578 default y
579 ---help---
580 STI refers to the HP "Standard Text Interface" which is a set of
581 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
582 Enabling this option will implement the linux framebuffer device
583 using calls to the STI BIOS routines for initialisation.
585 If you enable this option, you will get a planar framebuffer device
586 /dev/fb which will work on the most common HP graphic cards of the
587 NGLE family, including the artist chips (in the 7xx and Bxxx series),
588 HCRX, HCRX24, CRX, CRX24 and VisEG series.
590 It is safe to enable this option, so you should probably say "Y".
592 config FB_MAC
593 bool "Generic Macintosh display support"
594 depends on (FB = y) && MAC
595 select FB_CFB_FILLRECT
596 select FB_CFB_COPYAREA
597 select FB_CFB_IMAGEBLIT
598 select FB_MACMODES
600 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
601 config FB_HP300
602 bool
603 depends on (FB = y) && HP300
604 select FB_CFB_FILLRECT
605 select FB_CFB_IMAGEBLIT
606 default y
608 config FB_TGA
609 tristate "TGA/SFB+ framebuffer support"
610 depends on FB && (ALPHA || TC)
611 select FB_CFB_FILLRECT
612 select FB_CFB_COPYAREA
613 select FB_CFB_IMAGEBLIT
614 select BITREVERSE
615 ---help---
616 This is the frame buffer device driver for generic TGA and SFB+
617 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
618 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
619 TURBOchannel cards, also known as PMAGD-A, -B and -C.
621 Due to hardware limitations ZLX-E2 and E3 cards are not supported
622 for DECstation 5000/200 systems. Additionally due to firmware
623 limitations these cards may cause troubles with booting DECstation
624 5000/240 and /260 systems, but are fully supported under Linux if
625 you manage to get it going. ;-)
627 Say Y if you have one of those.
629 config FB_UVESA
630 tristate "Userspace VESA VGA graphics support"
631 depends on FB && CONNECTOR
632 select FB_CFB_FILLRECT
633 select FB_CFB_COPYAREA
634 select FB_CFB_IMAGEBLIT
635 select FB_MODE_HELPERS
636 help
637 This is the frame buffer driver for generic VBE 2.0 compliant
638 graphic cards. It can also take advantage of VBE 3.0 features,
639 such as refresh rate adjustment.
641 This driver generally provides more features than vesafb but
642 requires a userspace helper application called 'v86d'. See
643 <file:Documentation/fb/uvesafb.txt> for more information.
645 If unsure, say N.
647 config FB_VESA
648 bool "VESA VGA graphics support"
649 depends on (FB = y) && X86
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
653 select VIDEO_SELECT
654 help
655 This is the frame buffer device driver for generic VESA 2.0
656 compliant graphic cards. The older VESA 1.2 cards are not supported.
657 You will get a boot time penguin logo at no additional cost. Please
658 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
660 config FB_EFI
661 bool "EFI-based Framebuffer Support"
662 depends on (FB = y) && X86
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
666 help
667 This is the EFI frame buffer device driver. If the firmware on
668 your platform is UEFI2.0, select Y to add support for
669 Graphics Output Protocol for early console messages to appear.
671 config FB_IMAC
672 bool "Intel-based Macintosh Framebuffer Support"
673 depends on (FB = y) && X86 && EFI
674 select FB_CFB_FILLRECT
675 select FB_CFB_COPYAREA
676 select FB_CFB_IMAGEBLIT
677 help
678 This is the frame buffer device driver for the Intel-based Macintosh
680 config FB_HECUBA
681 tristate "Hecuba board support"
682 depends on FB && X86 && MMU
683 select FB_SYS_FILLRECT
684 select FB_SYS_COPYAREA
685 select FB_SYS_IMAGEBLIT
686 select FB_SYS_FOPS
687 select FB_DEFERRED_IO
688 help
689 This enables support for the Hecuba board. This driver was tested
690 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
691 interface (8 bit data, 4 bit control). If you anticipate using
692 this driver, say Y or M; otherwise say N. You must specify the
693 GPIO IO address to be used for setting control and data.
695 config FB_HGA
696 tristate "Hercules mono graphics support"
697 depends on FB && X86
698 select FB_CFB_FILLRECT
699 select FB_CFB_COPYAREA
700 select FB_CFB_IMAGEBLIT
701 help
702 Say Y here if you have a Hercules mono graphics card.
704 To compile this driver as a module, choose M here: the
705 module will be called hgafb.
707 As this card technology is 15 years old, most people will answer N
708 here.
710 config FB_HGA_ACCEL
711 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
712 depends on FB_HGA && EXPERIMENTAL
713 ---help---
714 This will compile the Hercules mono graphics with
715 acceleration functions.
717 config FB_SGIVW
718 tristate "SGI Visual Workstation framebuffer support"
719 depends on FB && X86_VISWS
720 select FB_CFB_FILLRECT
721 select FB_CFB_COPYAREA
722 select FB_CFB_IMAGEBLIT
723 help
724 SGI Visual Workstation support for framebuffer graphics.
726 config FB_GBE
727 bool "SGI Graphics Backend frame buffer support"
728 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
729 select FB_CFB_FILLRECT
730 select FB_CFB_COPYAREA
731 select FB_CFB_IMAGEBLIT
732 help
733 This is the frame buffer device driver for SGI Graphics Backend.
734 This chip is used in SGI O2 and Visual Workstation 320/540.
736 config FB_GBE_MEM
737 int "Video memory size in MB"
738 depends on FB_GBE
739 default 4
740 help
741 This is the amount of memory reserved for the framebuffer,
742 which can be any value between 1MB and 8MB.
744 config FB_SBUS
745 bool "SBUS and UPA framebuffers"
746 depends on (FB = y) && SPARC
747 help
748 Say Y if you want support for SBUS or UPA based frame buffer device.
750 config FB_BW2
751 bool "BWtwo support"
752 depends on (FB = y) && (SPARC && FB_SBUS)
753 select FB_CFB_FILLRECT
754 select FB_CFB_COPYAREA
755 select FB_CFB_IMAGEBLIT
756 help
757 This is the frame buffer device driver for the BWtwo frame buffer.
759 config FB_CG3
760 bool "CGthree support"
761 depends on (FB = y) && (SPARC && FB_SBUS)
762 select FB_CFB_FILLRECT
763 select FB_CFB_COPYAREA
764 select FB_CFB_IMAGEBLIT
765 help
766 This is the frame buffer device driver for the CGthree frame buffer.
768 config FB_CG6
769 bool "CGsix (GX,TurboGX) support"
770 depends on (FB = y) && (SPARC && FB_SBUS)
771 select FB_CFB_COPYAREA
772 select FB_CFB_IMAGEBLIT
773 help
774 This is the frame buffer device driver for the CGsix (GX, TurboGX)
775 frame buffer.
777 config FB_FFB
778 bool "Creator/Creator3D/Elite3D support"
779 depends on FB_SBUS && SPARC64
780 select FB_CFB_COPYAREA
781 select FB_CFB_IMAGEBLIT
782 help
783 This is the frame buffer device driver for the Creator, Creator3D,
784 and Elite3D graphics boards.
786 config FB_TCX
787 bool "TCX (SS4/SS5 only) support"
788 depends on FB_SBUS
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
792 help
793 This is the frame buffer device driver for the TCX 24/8bit frame
794 buffer.
796 config FB_CG14
797 bool "CGfourteen (SX) support"
798 depends on FB_SBUS
799 select FB_CFB_FILLRECT
800 select FB_CFB_COPYAREA
801 select FB_CFB_IMAGEBLIT
802 help
803 This is the frame buffer device driver for the CGfourteen frame
804 buffer on Desktop SPARCsystems with the SX graphics option.
806 config FB_P9100
807 bool "P9100 (Sparcbook 3 only) support"
808 depends on FB_SBUS
809 select FB_CFB_FILLRECT
810 select FB_CFB_COPYAREA
811 select FB_CFB_IMAGEBLIT
812 help
813 This is the frame buffer device driver for the P9100 card
814 supported on Sparcbook 3 machines.
816 config FB_LEO
817 bool "Leo (ZX) support"
818 depends on FB_SBUS
819 select FB_CFB_FILLRECT
820 select FB_CFB_COPYAREA
821 select FB_CFB_IMAGEBLIT
822 help
823 This is the frame buffer device driver for the SBUS-based Sun ZX
824 (leo) frame buffer cards.
826 config FB_IGA
827 bool "IGA 168x display support"
828 depends on (FB = y) && SPARC32
829 select FB_CFB_FILLRECT
830 select FB_CFB_COPYAREA
831 select FB_CFB_IMAGEBLIT
832 help
833 This is the framebuffer device for the INTERGRAPHICS 1680 and
834 successor frame buffer cards.
836 config FB_XVR500
837 bool "Sun XVR-500 3DLABS Wildcat support"
838 depends on (FB = y) && PCI && SPARC64
839 select FB_CFB_FILLRECT
840 select FB_CFB_COPYAREA
841 select FB_CFB_IMAGEBLIT
842 help
843 This is the framebuffer device for the Sun XVR-500 and similar
844 graphics cards based upon the 3DLABS Wildcat chipset. The driver
845 only works on sparc64 systems where the system firmware has
846 mostly initialized the card already. It is treated as a
847 completely dumb framebuffer device.
849 config FB_XVR2500
850 bool "Sun XVR-2500 3DLABS Wildcat support"
851 depends on (FB = y) && PCI && SPARC64
852 select FB_CFB_FILLRECT
853 select FB_CFB_COPYAREA
854 select FB_CFB_IMAGEBLIT
855 help
856 This is the framebuffer device for the Sun XVR-2500 and similar
857 graphics cards based upon the 3DLABS Wildcat chipset. The driver
858 only works on sparc64 systems where the system firmware has
859 mostly initialized the card already. It is treated as a
860 completely dumb framebuffer device.
862 config FB_PVR2
863 tristate "NEC PowerVR 2 display support"
864 depends on FB && SH_DREAMCAST
865 select FB_CFB_FILLRECT
866 select FB_CFB_COPYAREA
867 select FB_CFB_IMAGEBLIT
868 ---help---
869 Say Y here if you have a PowerVR 2 card in your box. If you plan to
870 run linux on your Dreamcast, you will have to say Y here.
871 This driver may or may not work on other PowerVR 2 cards, but is
872 totally untested. Use at your own risk. If unsure, say N.
874 To compile this driver as a module, choose M here: the
875 module will be called pvr2fb.
877 You can pass several parameters to the driver at boot time or at
878 module load time. The parameters look like "video=pvr2:XXX", where
879 the meaning of XXX can be found at the end of the main source file
880 (<file:drivers/video/pvr2fb.c>). Please see the file
881 <file:Documentation/fb/pvr2fb.txt>.
883 config FB_EPSON1355
884 bool "Epson 1355 framebuffer support"
885 depends on (FB = y) && ARCH_CEIVA
886 select FB_CFB_FILLRECT
887 select FB_CFB_COPYAREA
888 select FB_CFB_IMAGEBLIT
889 help
890 Build in support for the SED1355 Epson Research Embedded RAMDAC
891 LCD/CRT Controller (since redesignated as the S1D13505) as a
892 framebuffer. Product specs at
893 <http://www.erd.epson.com/vdc/html/products.htm>.
895 config FB_S1D13XXX
896 tristate "Epson S1D13XXX framebuffer support"
897 depends on FB
898 select FB_CFB_FILLRECT
899 select FB_CFB_COPYAREA
900 select FB_CFB_IMAGEBLIT
901 help
902 Support for S1D13XXX framebuffer device family (currently only
903 working with S1D13806). Product specs at
904 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
906 config FB_ATMEL
907 tristate "AT91/AT32 LCD Controller support"
908 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 || AVR32)
909 select FB_CFB_FILLRECT
910 select FB_CFB_COPYAREA
911 select FB_CFB_IMAGEBLIT
912 help
913 This enables support for the AT91/AT32 LCD Controller.
915 config FB_INTSRAM
916 bool "Frame Buffer in internal SRAM"
917 depends on FB_ATMEL && ARCH_AT91SAM9261
918 help
919 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
920 to let frame buffer in external SDRAM.
922 config FB_ATMEL_STN
923 bool "Use a STN display with AT91/AT32 LCD Controller"
924 depends on FB_ATMEL && MACH_AT91SAM9261EK
925 default n
926 help
927 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
928 Controller. Say N if you want to connect a TFT.
930 If unsure, say N.
932 config FB_NVIDIA
933 tristate "nVidia Framebuffer Support"
934 depends on FB && PCI
935 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
936 select FB_MODE_HELPERS
937 select FB_CFB_FILLRECT
938 select FB_CFB_COPYAREA
939 select FB_CFB_IMAGEBLIT
940 select BITREVERSE
941 select VGASTATE
942 help
943 This driver supports graphics boards with the nVidia chips, TNT
944 and newer. For very old chipsets, such as the RIVA128, then use
945 the rivafb.
946 Say Y if you have such a graphics board.
948 To compile this driver as a module, choose M here: the
949 module will be called nvidiafb.
951 config FB_NVIDIA_I2C
952 bool "Enable DDC Support"
953 depends on FB_NVIDIA
954 select FB_DDC
955 help
956 This enables I2C support for nVidia Chipsets. This is used
957 only for getting EDID information from the attached display
958 allowing for robust video mode handling and switching.
960 Because fbdev-2.6 requires that drivers must be able to
961 independently validate video mode parameters, you should say Y
962 here.
964 config FB_NVIDIA_DEBUG
965 bool "Lots of debug output"
966 depends on FB_NVIDIA
967 default n
968 help
969 Say Y here if you want the nVidia driver to output all sorts
970 of debugging information to provide to the maintainer when
971 something goes wrong.
973 config FB_NVIDIA_BACKLIGHT
974 bool "Support for backlight control"
975 depends on FB_NVIDIA
976 default y
977 help
978 Say Y here if you want to control the backlight of your display.
980 config FB_RIVA
981 tristate "nVidia Riva support"
982 depends on FB && PCI
983 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
984 select FB_MODE_HELPERS
985 select FB_CFB_FILLRECT
986 select FB_CFB_COPYAREA
987 select FB_CFB_IMAGEBLIT
988 select BITREVERSE
989 select VGASTATE
990 help
991 This driver supports graphics boards with the nVidia Riva/Geforce
992 chips.
993 Say Y if you have such a graphics board.
995 To compile this driver as a module, choose M here: the
996 module will be called rivafb.
998 config FB_RIVA_I2C
999 bool "Enable DDC Support"
1000 depends on FB_RIVA
1001 select FB_DDC
1002 help
1003 This enables I2C support for nVidia Chipsets. This is used
1004 only for getting EDID information from the attached display
1005 allowing for robust video mode handling and switching.
1007 Because fbdev-2.6 requires that drivers must be able to
1008 independently validate video mode parameters, you should say Y
1009 here.
1011 config FB_RIVA_DEBUG
1012 bool "Lots of debug output"
1013 depends on FB_RIVA
1014 default n
1015 help
1016 Say Y here if you want the Riva driver to output all sorts
1017 of debugging information to provide to the maintainer when
1018 something goes wrong.
1020 config FB_RIVA_BACKLIGHT
1021 bool "Support for backlight control"
1022 depends on FB_RIVA
1023 default y
1024 help
1025 Say Y here if you want to control the backlight of your display.
1027 config FB_I810
1028 tristate "Intel 810/815 support (EXPERIMENTAL)"
1029 depends on FB && EXPERIMENTAL && PCI && X86_32
1030 select AGP
1031 select AGP_INTEL
1032 select FB_MODE_HELPERS
1033 select FB_CFB_FILLRECT
1034 select FB_CFB_COPYAREA
1035 select FB_CFB_IMAGEBLIT
1036 select VGASTATE
1037 help
1038 This driver supports the on-board graphics built in to the Intel 810
1039 and 815 chipsets. Say Y if you have and plan to use such a board.
1041 To compile this driver as a module, choose M here: the
1042 module will be called i810fb.
1044 For more information, please read
1045 <file:Documentation/fb/intel810.txt>
1047 config FB_I810_GTF
1048 bool "use VESA Generalized Timing Formula"
1049 depends on FB_I810
1050 help
1051 If you say Y, then the VESA standard, Generalized Timing Formula
1052 or GTF, will be used to calculate the required video timing values
1053 per video mode. Since the GTF allows nondiscrete timings
1054 (nondiscrete being a range of values as opposed to discrete being a
1055 set of values), you'll be able to use any combination of horizontal
1056 and vertical resolutions, and vertical refresh rates without having
1057 to specify your own timing parameters. This is especially useful
1058 to maximize the performance of an aging display, or if you just
1059 have a display with nonstandard dimensions. A VESA compliant
1060 monitor is recommended, but can still work with non-compliant ones.
1061 If you need or want this, then select this option. The timings may
1062 not be compliant with Intel's recommended values. Use at your own
1063 risk.
1065 If you say N, the driver will revert to discrete video timings
1066 using a set recommended by Intel in their documentation.
1068 If unsure, say N.
1070 config FB_I810_I2C
1071 bool "Enable DDC Support"
1072 depends on FB_I810 && FB_I810_GTF
1073 select FB_DDC
1074 help
1076 config FB_LE80578
1077 tristate "Intel LE80578 (Vermilion) support"
1078 depends on FB && PCI && X86
1079 select FB_MODE_HELPERS
1080 select FB_CFB_FILLRECT
1081 select FB_CFB_COPYAREA
1082 select FB_CFB_IMAGEBLIT
1083 help
1084 This driver supports the LE80578 (Vermilion Range) chipset
1086 config FB_CARILLO_RANCH
1087 tristate "Intel Carillo Ranch support"
1088 depends on FB_LE80578 && FB && PCI && X86
1089 help
1090 This driver supports the LE80578 (Carillo Ranch) board
1092 config FB_INTEL
1093 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
1094 depends on FB && EXPERIMENTAL && PCI && X86
1095 select AGP
1096 select AGP_INTEL
1097 select FB_MODE_HELPERS
1098 select FB_CFB_FILLRECT
1099 select FB_CFB_COPYAREA
1100 select FB_CFB_IMAGEBLIT
1101 help
1102 This driver supports the on-board graphics built in to the Intel
1103 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
1104 Say Y if you have and plan to use such a board.
1106 If you say Y here and want DDC/I2C support you must first say Y to
1107 "I2C support" and "I2C bit-banging support" in the character devices
1108 section.
1110 If you say M here then "I2C support" and "I2C bit-banging support"
1111 can be build either as modules or built-in.
1113 To compile this driver as a module, choose M here: the
1114 module will be called intelfb.
1116 For more information, please read <file:Documentation/fb/intelfb.txt>
1118 config FB_INTEL_DEBUG
1119 bool "Intel driver Debug Messages"
1120 depends on FB_INTEL
1121 ---help---
1122 Say Y here if you want the Intel driver to output all sorts
1123 of debugging information to provide to the maintainer when
1124 something goes wrong.
1126 config FB_INTEL_I2C
1127 bool "DDC/I2C for Intel framebuffer support"
1128 depends on FB_INTEL
1129 select FB_DDC
1130 default y
1131 help
1132 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1134 config FB_MATROX
1135 tristate "Matrox acceleration"
1136 depends on FB && PCI
1137 select FB_CFB_FILLRECT
1138 select FB_CFB_COPYAREA
1139 select FB_CFB_IMAGEBLIT
1140 select FB_TILEBLITTING
1141 select FB_MACMODES if PPC_PMAC
1142 ---help---
1143 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1144 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1145 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1146 Matrox G400, G450 or G550 card in your box.
1148 To compile this driver as a module, choose M here: the
1149 module will be called matroxfb.
1151 You can pass several parameters to the driver at boot time or at
1152 module load time. The parameters look like "video=matrox:XXX", and
1153 are described in <file:Documentation/fb/matroxfb.txt>.
1155 config FB_MATROX_MILLENIUM
1156 bool "Millennium I/II support"
1157 depends on FB_MATROX
1158 help
1159 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1160 video card. If you select "Advanced lowlevel driver options" below,
1161 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1162 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1163 also use font widths different from 8.
1165 config FB_MATROX_MYSTIQUE
1166 bool "Mystique support"
1167 depends on FB_MATROX
1168 help
1169 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1170 video card. If you select "Advanced lowlevel driver options" below,
1171 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1172 packed pixel and 32 bpp packed pixel. You can also use font widths
1173 different from 8.
1175 config FB_MATROX_G
1176 bool "G100/G200/G400/G450/G550 support"
1177 depends on FB_MATROX
1178 ---help---
1179 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1180 video card. If you select "Advanced lowlevel driver options", you
1181 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1182 pixel and 32 bpp packed pixel. You can also use font widths
1183 different from 8.
1185 If you need support for G400 secondary head, you must first say Y to
1186 "I2C support" in the character devices section, and then to
1187 "Matrox I2C support" and "G400 second head support" here in the
1188 framebuffer section. G450/G550 secondary head and digital output
1189 are supported without additional modules.
1191 The driver starts in monitor mode. You must use the matroxset tool
1192 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1193 swap primary and secondary head outputs, or to change output mode.
1194 Secondary head driver always start in 640x480 resolution and you
1195 must use fbset to change it.
1197 Do not forget that second head supports only 16 and 32 bpp
1198 packed pixels, so it is a good idea to compile them into the kernel
1199 too. You can use only some font widths, as the driver uses generic
1200 painting procedures (the secondary head does not use acceleration
1201 engine).
1203 G450/G550 hardware can display TV picture only from secondary CRTC,
1204 and it performs no scaling, so picture must have 525 or 625 lines.
1206 config FB_MATROX_I2C
1207 tristate "Matrox I2C support"
1208 depends on FB_MATROX
1209 select FB_DDC
1210 ---help---
1211 This drivers creates I2C buses which are needed for accessing the
1212 DDC (I2C) bus present on all Matroxes, an I2C bus which
1213 interconnects Matrox optional devices, like MGA-TVO on G200 and
1214 G400, and the secondary head DDC bus, present on G400 only.
1216 You can say Y or M here if you want to experiment with monitor
1217 detection code. You must say Y or M here if you want to use either
1218 second head of G400 or MGA-TVO on G200 or G400.
1220 If you compile it as module, it will create a module named
1221 i2c-matroxfb.
1223 config FB_MATROX_MAVEN
1224 tristate "G400 second head support"
1225 depends on FB_MATROX_G && FB_MATROX_I2C
1226 ---help---
1227 WARNING !!! This support does not work with G450 !!!
1229 Say Y or M here if you want to use a secondary head (meaning two
1230 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1231 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1232 secondary head output is blanked while you are in X. With XFree
1233 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1234 the fbdev driver on first head and the fbdev driver on second head.
1236 If you compile it as module, two modules are created,
1237 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1238 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1239 also load i2c-matroxfb to get it to run.
1241 The driver starts in monitor mode and you must use the matroxset
1242 tool (available at
1243 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1244 PAL or NTSC or to swap primary and secondary head outputs.
1245 Secondary head driver also always start in 640x480 resolution, you
1246 must use fbset to change it.
1248 Also do not forget that second head supports only 16 and 32 bpp
1249 packed pixels, so it is a good idea to compile them into the kernel
1250 too. You can use only some font widths, as the driver uses generic
1251 painting procedures (the secondary head does not use acceleration
1252 engine).
1254 config FB_MATROX_MULTIHEAD
1255 bool "Multihead support"
1256 depends on FB_MATROX
1257 ---help---
1258 Say Y here if you have more than one (supported) Matrox device in
1259 your computer and you want to use all of them for different monitors
1260 ("multihead"). If you have only one device, you should say N because
1261 the driver compiled with Y is larger and a bit slower, especially on
1262 ia32 (ix86).
1264 If you said M to "Matrox unified accelerated driver" and N here, you
1265 will still be able to use several Matrox devices simultaneously:
1266 insert several instances of the module matroxfb into the kernel
1267 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1268 for the different Matrox devices. This method is slightly faster but
1269 uses 40 KB of kernel memory per Matrox card.
1271 There is no need for enabling 'Matrox multihead support' if you have
1272 only one Matrox card in the box.
1274 config FB_RADEON
1275 tristate "ATI Radeon display support"
1276 depends on FB && PCI
1277 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1278 select FB_MODE_HELPERS
1279 select FB_CFB_FILLRECT
1280 select FB_CFB_COPYAREA
1281 select FB_CFB_IMAGEBLIT
1282 select FB_MACMODES if PPC_OF
1283 help
1284 Choose this option if you want to use an ATI Radeon graphics card as
1285 a framebuffer device. There are both PCI and AGP versions. You
1286 don't need to choose this to run the Radeon in plain VGA mode.
1288 If you say Y here and want DDC/I2C support you must first say Y to
1289 "I2C support" and "I2C bit-banging support" in the character devices
1290 section.
1292 If you say M here then "I2C support" and "I2C bit-banging support"
1293 can be build either as modules or built-in.
1295 There is a product page at
1296 http://apps.ati.com/ATIcompare/
1298 config FB_RADEON_I2C
1299 bool "DDC/I2C for ATI Radeon support"
1300 depends on FB_RADEON
1301 select FB_DDC
1302 default y
1303 help
1304 Say Y here if you want DDC/I2C support for your Radeon board.
1306 config FB_RADEON_BACKLIGHT
1307 bool "Support for backlight control"
1308 depends on FB_RADEON
1309 default y
1310 help
1311 Say Y here if you want to control the backlight of your display.
1313 config FB_RADEON_DEBUG
1314 bool "Lots of debug output from Radeon driver"
1315 depends on FB_RADEON
1316 default n
1317 help
1318 Say Y here if you want the Radeon driver to output all sorts
1319 of debugging information to provide to the maintainer when
1320 something goes wrong.
1322 config FB_ATY128
1323 tristate "ATI Rage128 display support"
1324 depends on FB && PCI
1325 select FB_CFB_FILLRECT
1326 select FB_CFB_COPYAREA
1327 select FB_CFB_IMAGEBLIT
1328 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1329 select FB_MACMODES if PPC_PMAC
1330 help
1331 This driver supports graphics boards with the ATI Rage128 chips.
1332 Say Y if you have such a graphics board and read
1333 <file:Documentation/fb/aty128fb.txt>.
1335 To compile this driver as a module, choose M here: the
1336 module will be called aty128fb.
1338 config FB_ATY128_BACKLIGHT
1339 bool "Support for backlight control"
1340 depends on FB_ATY128
1341 default y
1342 help
1343 Say Y here if you want to control the backlight of your display.
1345 config FB_ATY
1346 tristate "ATI Mach64 display support" if PCI || ATARI
1347 depends on FB && !SPARC32
1348 select FB_CFB_FILLRECT
1349 select FB_CFB_COPYAREA
1350 select FB_CFB_IMAGEBLIT
1351 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1352 select FB_MACMODES if PPC
1353 help
1354 This driver supports graphics boards with the ATI Mach64 chips.
1355 Say Y if you have such a graphics board.
1357 To compile this driver as a module, choose M here: the
1358 module will be called atyfb.
1360 config FB_ATY_CT
1361 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1362 depends on PCI && FB_ATY
1363 default y if SPARC64 && PCI
1364 help
1365 Say Y here to support use of ATI's 64-bit Rage boards (or other
1366 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1367 framebuffer device. The ATI product support page for these boards
1368 is at <http://support.ati.com/products/pc/mach64/>.
1370 config FB_ATY_GENERIC_LCD
1371 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1372 depends on FB_ATY_CT
1373 help
1374 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1375 Rage XC, or Rage XL chipset.
1377 config FB_ATY_GX
1378 bool "Mach64 GX support" if PCI
1379 depends on FB_ATY
1380 default y if ATARI
1381 help
1382 Say Y here to support use of the ATI Mach64 Graphics Expression
1383 board (or other boards based on the Mach64 GX chipset) as a
1384 framebuffer device. The ATI product support page for these boards
1385 is at
1386 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1388 config FB_ATY_BACKLIGHT
1389 bool "Support for backlight control"
1390 depends on FB_ATY
1391 default y
1392 help
1393 Say Y here if you want to control the backlight of your display.
1395 config FB_S3
1396 tristate "S3 Trio/Virge support"
1397 depends on FB && PCI
1398 select FB_CFB_FILLRECT
1399 select FB_CFB_COPYAREA
1400 select FB_CFB_IMAGEBLIT
1401 select FB_TILEBLITTING
1402 select FB_SVGALIB
1403 select VGASTATE
1404 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1405 ---help---
1406 Driver for graphics boards with S3 Trio / S3 Virge chip.
1408 config FB_SAVAGE
1409 tristate "S3 Savage support"
1410 depends on FB && PCI && EXPERIMENTAL
1411 select FB_MODE_HELPERS
1412 select FB_CFB_FILLRECT
1413 select FB_CFB_COPYAREA
1414 select FB_CFB_IMAGEBLIT
1415 select VGASTATE
1416 help
1417 This driver supports notebooks and computers with S3 Savage PCI/AGP
1418 chips.
1420 Say Y if you have such a graphics card.
1422 To compile this driver as a module, choose M here; the module
1423 will be called savagefb.
1425 config FB_SAVAGE_I2C
1426 bool "Enable DDC2 Support"
1427 depends on FB_SAVAGE
1428 select FB_DDC
1429 help
1430 This enables I2C support for S3 Savage Chipsets. This is used
1431 only for getting EDID information from the attached display
1432 allowing for robust video mode handling and switching.
1434 Because fbdev-2.6 requires that drivers must be able to
1435 independently validate video mode parameters, you should say Y
1436 here.
1438 config FB_SAVAGE_ACCEL
1439 bool "Enable Console Acceleration"
1440 depends on FB_SAVAGE
1441 default n
1442 help
1443 This option will compile in console acceleration support. If
1444 the resulting framebuffer console has bothersome glitches, then
1445 choose N here.
1447 config FB_SIS
1448 tristate "SiS/XGI display support"
1449 depends on FB && PCI
1450 select FB_CFB_FILLRECT
1451 select FB_CFB_COPYAREA
1452 select FB_CFB_IMAGEBLIT
1453 help
1454 This is the frame buffer device driver for the SiS 300, 315, 330
1455 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1456 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1458 To compile this driver as a module, choose M here; the module
1459 will be called sisfb.
1461 config FB_SIS_300
1462 bool "SiS 300 series support"
1463 depends on FB_SIS
1464 help
1465 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1467 config FB_SIS_315
1468 bool "SiS 315/330/340 series and XGI support"
1469 depends on FB_SIS
1470 help
1471 Say Y here to support use of the SiS 315, 330 and 340 series
1472 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1473 as XGI V3XT, V5, V8 and Z7.
1475 config FB_NEOMAGIC
1476 tristate "NeoMagic display support"
1477 depends on FB && PCI
1478 select FB_MODE_HELPERS
1479 select FB_CFB_FILLRECT
1480 select FB_CFB_COPYAREA
1481 select FB_CFB_IMAGEBLIT
1482 select VGASTATE
1483 help
1484 This driver supports notebooks with NeoMagic PCI chips.
1485 Say Y if you have such a graphics card.
1487 To compile this driver as a module, choose M here: the
1488 module will be called neofb.
1490 config FB_KYRO
1491 tristate "IMG Kyro support"
1492 depends on FB && PCI
1493 select FB_CFB_FILLRECT
1494 select FB_CFB_COPYAREA
1495 select FB_CFB_IMAGEBLIT
1496 help
1497 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1498 graphics board.
1500 To compile this driver as a module, choose M here: the
1501 module will be called kyrofb.
1503 config FB_3DFX
1504 tristate "3Dfx Banshee/Voodoo3 display support"
1505 depends on FB && PCI
1506 select FB_CFB_IMAGEBLIT
1507 select FB_CFB_FILLRECT
1508 select FB_CFB_COPYAREA
1509 help
1510 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1511 chips. Say Y if you have such a graphics board.
1513 To compile this driver as a module, choose M here: the
1514 module will be called tdfxfb.
1516 config FB_3DFX_ACCEL
1517 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1518 depends on FB_3DFX && EXPERIMENTAL
1519 ---help---
1520 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1521 with acceleration functions.
1524 config FB_VOODOO1
1525 tristate "3Dfx Voodoo Graphics (sst1) support"
1526 depends on FB && PCI
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1529 select FB_CFB_IMAGEBLIT
1530 ---help---
1531 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1532 Voodoo2 (cvg) based graphics card.
1534 To compile this driver as a module, choose M here: the
1535 module will be called sstfb.
1537 WARNING: Do not use any application that uses the 3D engine
1538 (namely glide) while using this driver.
1539 Please read the <file:Documentation/fb/sstfb.txt> for supported
1540 options and other important info support.
1542 config FB_VT8623
1543 tristate "VIA VT8623 support"
1544 depends on FB && PCI
1545 select FB_CFB_FILLRECT
1546 select FB_CFB_COPYAREA
1547 select FB_CFB_IMAGEBLIT
1548 select FB_TILEBLITTING
1549 select FB_SVGALIB
1550 select VGASTATE
1551 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1552 ---help---
1553 Driver for CastleRock integrated graphics core in the
1554 VIA VT8623 [Apollo CLE266] chipset.
1556 config FB_CYBLA
1557 tristate "Cyberblade/i1 support"
1558 depends on FB && PCI && X86_32 && !64BIT
1559 select FB_CFB_IMAGEBLIT
1560 select VIDEO_SELECT
1561 ---help---
1562 This driver is supposed to support the Trident Cyberblade/i1
1563 graphics core integrated in the VIA VT8601A North Bridge,
1564 also known as VIA Apollo PLE133.
1566 Status:
1567 - Developed, tested and working on EPIA 5000 and EPIA 800.
1568 - Does work reliable on all systems with CRT/LCD connected to
1569 normal VGA ports.
1570 - Should work on systems that do use the internal LCD port, but
1571 this is absolutely not tested.
1573 Character imageblit, copyarea and rectangle fill are hw accelerated,
1574 ypan scrolling is used by default.
1576 Please do read <file:Documentation/fb/cyblafb/*>.
1578 To compile this driver as a module, choose M here: the
1579 module will be called cyblafb.
1581 config FB_TRIDENT
1582 tristate "Trident support"
1583 depends on FB && PCI
1584 select FB_CFB_FILLRECT
1585 select FB_CFB_COPYAREA
1586 select FB_CFB_IMAGEBLIT
1587 ---help---
1588 This driver is supposed to support graphics boards with the
1589 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1590 but also on some motherboards. For more information, read
1591 <file:Documentation/fb/tridentfb.txt>
1593 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1594 instead.
1596 Say Y if you have such a graphics board.
1599 To compile this driver as a module, choose M here: the
1600 module will be called tridentfb.
1602 config FB_TRIDENT_ACCEL
1603 bool "Trident Acceleration functions (EXPERIMENTAL)"
1604 depends on FB_TRIDENT && EXPERIMENTAL
1605 ---help---
1606 This will compile the Trident frame buffer device with
1607 acceleration functions.
1609 config FB_ARK
1610 tristate "ARK 2000PV support"
1611 depends on FB && PCI
1612 select FB_CFB_FILLRECT
1613 select FB_CFB_COPYAREA
1614 select FB_CFB_IMAGEBLIT
1615 select FB_TILEBLITTING
1616 select FB_SVGALIB
1617 select VGASTATE
1618 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1619 ---help---
1620 Driver for PCI graphics boards with ARK 2000PV chip
1621 and ICS 5342 RAMDAC.
1623 config FB_PM3
1624 tristate "Permedia3 support (EXPERIMENTAL)"
1625 depends on FB && PCI && EXPERIMENTAL
1626 select FB_CFB_FILLRECT
1627 select FB_CFB_COPYAREA
1628 select FB_CFB_IMAGEBLIT
1629 help
1630 This is the frame buffer device driver for the 3DLabs Permedia3
1631 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1632 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1633 and maybe other boards.
1635 config FB_AU1100
1636 bool "Au1100 LCD Driver"
1637 depends on (FB = y) && MIPS && SOC_AU1100
1638 select FB_CFB_FILLRECT
1639 select FB_CFB_COPYAREA
1640 select FB_CFB_IMAGEBLIT
1641 help
1642 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1643 various panels and CRTs by passing in kernel cmd line option
1644 au1100fb:panel=<name>.
1646 config FB_AU1200
1647 bool "Au1200 LCD Driver"
1648 depends on (FB = y) && MIPS && SOC_AU1200
1649 select FB_CFB_FILLRECT
1650 select FB_CFB_COPYAREA
1651 select FB_CFB_IMAGEBLIT
1652 help
1653 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1654 various panels and CRTs by passing in kernel cmd line option
1655 au1200fb:panel=<name>.
1657 source "drivers/video/geode/Kconfig"
1659 config FB_HIT
1660 tristate "HD64461 Frame Buffer support"
1661 depends on FB && HD64461
1662 select FB_CFB_FILLRECT
1663 select FB_CFB_COPYAREA
1664 select FB_CFB_IMAGEBLIT
1665 help
1666 This is the frame buffer device driver for the Hitachi HD64461 LCD
1667 frame buffer card.
1669 config FB_PMAG_AA
1670 bool "PMAG-AA TURBOchannel framebuffer support"
1671 depends on (FB = y) && TC
1672 select FB_CFB_FILLRECT
1673 select FB_CFB_COPYAREA
1674 select FB_CFB_IMAGEBLIT
1675 help
1676 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1677 used mainly in the MIPS-based DECstation series.
1679 config FB_PMAG_BA
1680 tristate "PMAG-BA TURBOchannel framebuffer support"
1681 depends on FB && TC
1682 select FB_CFB_FILLRECT
1683 select FB_CFB_COPYAREA
1684 select FB_CFB_IMAGEBLIT
1685 help
1686 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1687 used mainly in the MIPS-based DECstation series.
1689 config FB_PMAGB_B
1690 tristate "PMAGB-B TURBOchannel framebuffer support"
1691 depends on FB && TC
1692 select FB_CFB_FILLRECT
1693 select FB_CFB_COPYAREA
1694 select FB_CFB_IMAGEBLIT
1695 help
1696 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1697 in the MIPS-based DECstation series. The card is currently only
1698 supported in 1280x1024x8 mode.
1700 config FB_MAXINE
1701 bool "Maxine (Personal DECstation) onboard framebuffer support"
1702 depends on (FB = y) && MACH_DECSTATION
1703 select FB_CFB_FILLRECT
1704 select FB_CFB_COPYAREA
1705 select FB_CFB_IMAGEBLIT
1706 help
1707 Support for the onboard framebuffer (1024x768x8) in the Personal
1708 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1709 Codename "Maxine").
1711 config FB_G364
1712 bool "G364 frame buffer support"
1713 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1714 select FB_CFB_FILLRECT
1715 select FB_CFB_COPYAREA
1716 select FB_CFB_IMAGEBLIT
1717 help
1718 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1719 Olivetti M700-10 systems.
1721 config FB_68328
1722 bool "Motorola 68328 native frame buffer support"
1723 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1727 help
1728 Say Y here if you want to support the built-in frame buffer of
1729 the Motorola 68328 CPU family.
1731 config FB_PXA
1732 tristate "PXA LCD framebuffer support"
1733 depends on FB && ARCH_PXA
1734 select FB_CFB_FILLRECT
1735 select FB_CFB_COPYAREA
1736 select FB_CFB_IMAGEBLIT
1737 ---help---
1738 Frame buffer driver for the built-in LCD controller in the Intel
1739 PXA2x0 processor.
1741 This driver is also available as a module ( = code which can be
1742 inserted and removed from the running kernel whenever you want). The
1743 module will be called pxafb. If you want to compile it as a module,
1744 say M here and read <file:Documentation/kbuild/modules.txt>.
1746 If unsure, say N.
1748 config FB_PXA_PARAMETERS
1749 bool "PXA LCD command line parameters"
1750 default n
1751 depends on FB_PXA
1752 ---help---
1753 Enable the use of kernel command line or module parameters
1754 to configure the physical properties of the LCD panel when
1755 using the PXA LCD driver.
1757 This option allows you to override the panel parameters
1758 supplied by the platform in order to support multiple
1759 different models of flatpanel. If you will only be using a
1760 single model of flatpanel then you can safely leave this
1761 option disabled.
1763 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1765 config FB_MBX
1766 tristate "2700G LCD framebuffer support"
1767 depends on FB && ARCH_PXA
1768 select FB_CFB_FILLRECT
1769 select FB_CFB_COPYAREA
1770 select FB_CFB_IMAGEBLIT
1771 ---help---
1772 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1773 Accelerator
1775 config FB_MBX_DEBUG
1776 bool "Enable debugging info via debugfs"
1777 depends on FB_MBX && DEBUG_FS
1778 default n
1779 ---help---
1780 Enable this if you want debugging information using the debug
1781 filesystem (debugfs)
1783 If unsure, say N.
1785 config FB_W100
1786 tristate "W100 frame buffer support"
1787 depends on FB && PXA_SHARPSL
1788 select FB_CFB_FILLRECT
1789 select FB_CFB_COPYAREA
1790 select FB_CFB_IMAGEBLIT
1791 ---help---
1792 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1794 This driver is also available as a module ( = code which can be
1795 inserted and removed from the running kernel whenever you want). The
1796 module will be called w100fb. If you want to compile it as a module,
1797 say M here and read <file:Documentation/kbuild/modules.txt>.
1799 If unsure, say N.
1801 config FB_S3C2410
1802 tristate "S3C2410 LCD framebuffer support"
1803 depends on FB && ARCH_S3C2410
1804 select FB_CFB_FILLRECT
1805 select FB_CFB_COPYAREA
1806 select FB_CFB_IMAGEBLIT
1807 ---help---
1808 Frame buffer driver for the built-in LCD controller in the Samsung
1809 S3C2410 processor.
1811 This driver is also available as a module ( = code which can be
1812 inserted and removed from the running kernel whenever you want). The
1813 module will be called s3c2410fb. If you want to compile it as a module,
1814 say M here and read <file:Documentation/kbuild/modules.txt>.
1816 If unsure, say N.
1817 config FB_S3C2410_DEBUG
1818 bool "S3C2410 lcd debug messages"
1819 depends on FB_S3C2410
1820 help
1821 Turn on debugging messages. Note that you can set/unset at run time
1822 through sysfs
1824 config FB_SM501
1825 tristate "Silicon Motion SM501 framebuffer support"
1826 depends on FB && MFD_SM501
1827 select FB_CFB_FILLRECT
1828 select FB_CFB_COPYAREA
1829 select FB_CFB_IMAGEBLIT
1830 ---help---
1831 Frame buffer driver for the CRT and LCD controllers in the Silicon
1832 Motion SM501.
1834 This driver is also available as a module ( = code which can be
1835 inserted and removed from the running kernel whenever you want). The
1836 module will be called sm501fb. If you want to compile it as a module,
1837 say M here and read <file:Documentation/kbuild/modules.txt>.
1839 If unsure, say N.
1842 config FB_PNX4008_DUM
1843 tristate "Display Update Module support on Philips PNX4008 board"
1844 depends on FB && ARCH_PNX4008
1845 ---help---
1846 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1848 config FB_PNX4008_DUM_RGB
1849 tristate "RGB Framebuffer support on Philips PNX4008 board"
1850 depends on FB_PNX4008_DUM
1851 select FB_CFB_FILLRECT
1852 select FB_CFB_COPYAREA
1853 select FB_CFB_IMAGEBLIT
1854 ---help---
1855 Say Y here to enable support for PNX4008 RGB Framebuffer
1857 config FB_IBM_GXT4500
1858 tristate "Framebuffer support for IBM GXT4500P adaptor"
1859 depends on FB && PPC
1860 select FB_CFB_FILLRECT
1861 select FB_CFB_COPYAREA
1862 select FB_CFB_IMAGEBLIT
1863 ---help---
1864 Say Y here to enable support for the IBM GXT4500P display
1865 adaptor, found on some IBM System P (pSeries) machines.
1867 config FB_PS3
1868 tristate "PS3 GPU framebuffer driver"
1869 depends on FB && PS3_PS3AV
1870 select FB_SYS_FILLRECT
1871 select FB_SYS_COPYAREA
1872 select FB_SYS_IMAGEBLIT
1873 select FB_SYS_FOPS
1874 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1875 ---help---
1876 Include support for the virtual frame buffer in the PS3 platform.
1878 config FB_PS3_DEFAULT_SIZE_M
1879 int "PS3 default frame buffer size (in MiB)"
1880 depends on FB_PS3
1881 default 9
1882 ---help---
1883 This is the default size (in MiB) of the virtual frame buffer in
1884 the PS3.
1885 The default value can be overridden on the kernel command line
1886 using the "ps3fb" option (e.g. "ps3fb=9M");
1888 config FB_XILINX
1889 tristate "Xilinx frame buffer support"
1890 depends on FB && XILINX_VIRTEX
1891 select FB_CFB_FILLRECT
1892 select FB_CFB_COPYAREA
1893 select FB_CFB_IMAGEBLIT
1894 ---help---
1895 Include support for the Xilinx ML300/ML403 reference design
1896 framebuffer. ML300 carries a 640*480 LCD display on the board,
1897 ML403 uses a standard DB15 VGA connector.
1899 config FB_VIRTUAL
1900 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1901 depends on FB
1902 select FB_SYS_FILLRECT
1903 select FB_SYS_COPYAREA
1904 select FB_SYS_IMAGEBLIT
1905 select FB_SYS_FOPS
1906 ---help---
1907 This is a `virtual' frame buffer device. It operates on a chunk of
1908 unswappable kernel memory instead of on the memory of a graphics
1909 board. This means you cannot see any output sent to this frame
1910 buffer device, while it does consume precious memory. The main use
1911 of this frame buffer device is testing and debugging the frame
1912 buffer subsystem. Do NOT enable it for normal systems! To protect
1913 the innocent, it has to be enabled explicitly at boot time using the
1914 kernel option `video=vfb:'.
1916 To compile this driver as a module, choose M here: the
1917 module will be called vfb. In order to load it, you must use
1918 the vfb_enable=1 option.
1920 If unsure, say N.
1922 source "drivers/video/omap/Kconfig"
1924 source "drivers/video/backlight/Kconfig"
1925 source "drivers/video/display/Kconfig"
1927 if VT
1928 source "drivers/video/console/Kconfig"
1929 endif
1931 if FB || SGI_NEWPORT_CONSOLE
1932 source "drivers/video/logo/Kconfig"
1933 endif
1935 endmenu