| blob | 5b3dbcfcda48e6794f71a32d130002229b08c794 |
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 config FB_STI
557 tristate "HP STI frame buffer device support"
558 depends on FB && PARISC
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
562 default y
563 ---help---
564 STI refers to the HP "Standard Text Interface" which is a set of
565 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
566 Enabling this option will implement the linux framebuffer device
567 using calls to the STI BIOS routines for initialisation.
569 If you enable this option, you will get a planar framebuffer device
570 /dev/fb which will work on the most common HP graphic cards of the
571 NGLE family, including the artist chips (in the 7xx and Bxxx series),
572 HCRX, HCRX24, CRX, CRX24 and VisEG series.
574 It is safe to enable this option, so you should probably say "Y".
576 config FB_MAC
577 bool "Generic Macintosh display support"
578 depends on (FB = y) && MAC
579 select FB_CFB_FILLRECT
580 select FB_CFB_COPYAREA
581 select FB_CFB_IMAGEBLIT
582 select FB_MACMODES
584 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
585 config FB_HP300
586 bool
587 depends on (FB = y) && HP300
588 select FB_CFB_FILLRECT
589 select FB_CFB_IMAGEBLIT
590 default y
592 config FB_TGA
593 tristate "TGA/SFB+ framebuffer support"
594 depends on FB && (ALPHA || TC)
595 select FB_CFB_FILLRECT
596 select FB_CFB_COPYAREA
597 select FB_CFB_IMAGEBLIT
598 select BITREVERSE
599 ---help---
600 This is the frame buffer device driver for generic TGA and SFB+
601 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
602 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
603 TURBOchannel cards, also known as PMAGD-A, -B and -C.
605 Due to hardware limitations ZLX-E2 and E3 cards are not supported
606 for DECstation 5000/200 systems. Additionally due to firmware
607 limitations these cards may cause troubles with booting DECstation
608 5000/240 and /260 systems, but are fully supported under Linux if
609 you manage to get it going. ;-)
611 Say Y if you have one of those.
613 config FB_UVESA
614 tristate "Userspace VESA VGA graphics support"
615 depends on FB && CONNECTOR
616 select FB_CFB_FILLRECT
617 select FB_CFB_COPYAREA
618 select FB_CFB_IMAGEBLIT
619 select FB_MODE_HELPERS
620 help
621 This is the frame buffer driver for generic VBE 2.0 compliant
622 graphic cards. It can also take advantage of VBE 3.0 features,
623 such as refresh rate adjustment.
625 This driver generally provides more features than vesafb but
626 requires a userspace helper application called 'v86d'. See
627 <file:Documentation/fb/uvesafb.txt> for more information.
629 If unsure, say N.
631 config FB_VESA
632 bool "VESA VGA graphics support"
633 depends on (FB = y) && X86
634 select FB_CFB_FILLRECT
635 select FB_CFB_COPYAREA
636 select FB_CFB_IMAGEBLIT
637 select VIDEO_SELECT
638 help
639 This is the frame buffer device driver for generic VESA 2.0
640 compliant graphic cards. The older VESA 1.2 cards are not supported.
641 You will get a boot time penguin logo at no additional cost. Please
642 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
644 config FB_EFI
645 bool "EFI-based Framebuffer Support"
646 depends on (FB = y) && X86
647 select FB_CFB_FILLRECT
648 select FB_CFB_COPYAREA
649 select FB_CFB_IMAGEBLIT
650 help
651 This is the EFI frame buffer device driver. If the firmware on
652 your platform is UEFI2.0, select Y to add support for
653 Graphics Output Protocol for early console messages to appear.
655 config FB_IMAC
656 bool "Intel-based Macintosh Framebuffer Support"
657 depends on (FB = y) && X86 && EFI
658 select FB_CFB_FILLRECT
659 select FB_CFB_COPYAREA
660 select FB_CFB_IMAGEBLIT
661 help
662 This is the frame buffer device driver for the Intel-based Macintosh
664 config FB_HECUBA
665 tristate "Hecuba board support"
666 depends on FB && X86 && MMU
667 select FB_SYS_FILLRECT
668 select FB_SYS_COPYAREA
669 select FB_SYS_IMAGEBLIT
670 select FB_SYS_FOPS
671 select FB_DEFERRED_IO
672 help
673 This enables support for the Hecuba board. This driver was tested
674 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
675 interface (8 bit data, 4 bit control). If you anticipate using
676 this driver, say Y or M; otherwise say N. You must specify the
677 GPIO IO address to be used for setting control and data.
679 config FB_HGA
680 tristate "Hercules mono graphics support"
681 depends on FB && X86
682 select FB_CFB_FILLRECT
683 select FB_CFB_COPYAREA
684 select FB_CFB_IMAGEBLIT
685 help
686 Say Y here if you have a Hercules mono graphics card.
688 To compile this driver as a module, choose M here: the
689 module will be called hgafb.
691 As this card technology is 15 years old, most people will answer N
692 here.
694 config FB_HGA_ACCEL
695 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
696 depends on FB_HGA && EXPERIMENTAL
697 ---help---
698 This will compile the Hercules mono graphics with
699 acceleration functions.
701 config FB_SGIVW
702 tristate "SGI Visual Workstation framebuffer support"
703 depends on FB && X86_VISWS
704 select FB_CFB_FILLRECT
705 select FB_CFB_COPYAREA
706 select FB_CFB_IMAGEBLIT
707 help
708 SGI Visual Workstation support for framebuffer graphics.
710 config FB_GBE
711 bool "SGI Graphics Backend frame buffer support"
712 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
713 select FB_CFB_FILLRECT
714 select FB_CFB_COPYAREA
715 select FB_CFB_IMAGEBLIT
716 help
717 This is the frame buffer device driver for SGI Graphics Backend.
718 This chip is used in SGI O2 and Visual Workstation 320/540.
720 config FB_GBE_MEM
721 int "Video memory size in MB"
722 depends on FB_GBE
723 default 4
724 help
725 This is the amount of memory reserved for the framebuffer,
726 which can be any value between 1MB and 8MB.
728 config FB_SBUS
729 bool "SBUS and UPA framebuffers"
730 depends on (FB = y) && SPARC
731 help
732 Say Y if you want support for SBUS or UPA based frame buffer device.
734 config FB_BW2
735 bool "BWtwo support"
736 depends on (FB = y) && (SPARC && FB_SBUS)
737 select FB_CFB_FILLRECT
738 select FB_CFB_COPYAREA
739 select FB_CFB_IMAGEBLIT
740 help
741 This is the frame buffer device driver for the BWtwo frame buffer.
743 config FB_CG3
744 bool "CGthree support"
745 depends on (FB = y) && (SPARC && FB_SBUS)
746 select FB_CFB_FILLRECT
747 select FB_CFB_COPYAREA
748 select FB_CFB_IMAGEBLIT
749 help
750 This is the frame buffer device driver for the CGthree frame buffer.
752 config FB_CG6
753 bool "CGsix (GX,TurboGX) support"
754 depends on (FB = y) && (SPARC && FB_SBUS)
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
757 help
758 This is the frame buffer device driver for the CGsix (GX, TurboGX)
759 frame buffer.
761 config FB_FFB
762 bool "Creator/Creator3D/Elite3D support"
763 depends on FB_SBUS && SPARC64
764 select FB_CFB_COPYAREA
765 select FB_CFB_IMAGEBLIT
766 help
767 This is the frame buffer device driver for the Creator, Creator3D,
768 and Elite3D graphics boards.
770 config FB_TCX
771 bool "TCX (SS4/SS5 only) support"
772 depends on FB_SBUS
773 select FB_CFB_FILLRECT
774 select FB_CFB_COPYAREA
775 select FB_CFB_IMAGEBLIT
776 help
777 This is the frame buffer device driver for the TCX 24/8bit frame
778 buffer.
780 config FB_CG14
781 bool "CGfourteen (SX) support"
782 depends on FB_SBUS
783 select FB_CFB_FILLRECT
784 select FB_CFB_COPYAREA
785 select FB_CFB_IMAGEBLIT
786 help
787 This is the frame buffer device driver for the CGfourteen frame
788 buffer on Desktop SPARCsystems with the SX graphics option.
790 config FB_P9100
791 bool "P9100 (Sparcbook 3 only) support"
792 depends on FB_SBUS
793 select FB_CFB_FILLRECT
794 select FB_CFB_COPYAREA
795 select FB_CFB_IMAGEBLIT
796 help
797 This is the frame buffer device driver for the P9100 card
798 supported on Sparcbook 3 machines.
800 config FB_LEO
801 bool "Leo (ZX) support"
802 depends on FB_SBUS
803 select FB_CFB_FILLRECT
804 select FB_CFB_COPYAREA
805 select FB_CFB_IMAGEBLIT
806 help
807 This is the frame buffer device driver for the SBUS-based Sun ZX
808 (leo) frame buffer cards.
810 config FB_IGA
811 bool "IGA 168x display support"
812 depends on (FB = y) && SPARC32
813 select FB_CFB_FILLRECT
814 select FB_CFB_COPYAREA
815 select FB_CFB_IMAGEBLIT
816 help
817 This is the framebuffer device for the INTERGRAPHICS 1680 and
818 successor frame buffer cards.
820 config FB_XVR500
821 bool "Sun XVR-500 3DLABS Wildcat support"
822 depends on (FB = y) && PCI && SPARC64
823 select FB_CFB_FILLRECT
824 select FB_CFB_COPYAREA
825 select FB_CFB_IMAGEBLIT
826 help
827 This is the framebuffer device for the Sun XVR-500 and similar
828 graphics cards based upon the 3DLABS Wildcat chipset. The driver
829 only works on sparc64 systems where the system firmware has
830 mostly initialized the card already. It is treated as a
831 completely dumb framebuffer device.
833 config FB_XVR2500
834 bool "Sun XVR-2500 3DLABS Wildcat support"
835 depends on (FB = y) && PCI && SPARC64
836 select FB_CFB_FILLRECT
837 select FB_CFB_COPYAREA
838 select FB_CFB_IMAGEBLIT
839 help
840 This is the framebuffer device for the Sun XVR-2500 and similar
841 graphics cards based upon the 3DLABS Wildcat chipset. The driver
842 only works on sparc64 systems where the system firmware has
843 mostly initialized the card already. It is treated as a
844 completely dumb framebuffer device.
846 config FB_PVR2
847 tristate "NEC PowerVR 2 display support"
848 depends on FB && SH_DREAMCAST
849 select FB_CFB_FILLRECT
850 select FB_CFB_COPYAREA
851 select FB_CFB_IMAGEBLIT
852 ---help---
853 Say Y here if you have a PowerVR 2 card in your box. If you plan to
854 run linux on your Dreamcast, you will have to say Y here.
855 This driver may or may not work on other PowerVR 2 cards, but is
856 totally untested. Use at your own risk. If unsure, say N.
858 To compile this driver as a module, choose M here: the
859 module will be called pvr2fb.
861 You can pass several parameters to the driver at boot time or at
862 module load time. The parameters look like "video=pvr2:XXX", where
863 the meaning of XXX can be found at the end of the main source file
864 (<file:drivers/video/pvr2fb.c>). Please see the file
865 <file:Documentation/fb/pvr2fb.txt>.
867 config FB_EPSON1355
868 bool "Epson 1355 framebuffer support"
869 depends on (FB = y) && ARCH_CEIVA
870 select FB_CFB_FILLRECT
871 select FB_CFB_COPYAREA
872 select FB_CFB_IMAGEBLIT
873 help
874 Build in support for the SED1355 Epson Research Embedded RAMDAC
875 LCD/CRT Controller (since redesignated as the S1D13505) as a
876 framebuffer. Product specs at
877 <http://www.erd.epson.com/vdc/html/products.htm>.
879 config FB_S1D13XXX
880 tristate "Epson S1D13XXX framebuffer support"
881 depends on FB
882 select FB_CFB_FILLRECT
883 select FB_CFB_COPYAREA
884 select FB_CFB_IMAGEBLIT
885 help
886 Support for S1D13XXX framebuffer device family (currently only
887 working with S1D13806). Product specs at
888 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
890 config FB_ATMEL
891 tristate "AT91/AT32 LCD Controller support"
892 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || AVR32)
893 select FB_CFB_FILLRECT
894 select FB_CFB_COPYAREA
895 select FB_CFB_IMAGEBLIT
896 help
897 This enables support for the AT91/AT32 LCD Controller.
899 config FB_INTSRAM
900 bool "Frame Buffer in internal SRAM"
901 depends on FB_ATMEL && ARCH_AT91SAM9261
902 help
903 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
904 to let frame buffer in external SDRAM.
906 config FB_ATMEL_STN
907 bool "Use a STN display with AT91/AT32 LCD Controller"
908 depends on FB_ATMEL && MACH_AT91SAM9261EK
909 default n
910 help
911 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
912 Controller. Say N if you want to connect a TFT.
914 If unsure, say N.
916 config FB_NVIDIA
917 tristate "nVidia Framebuffer Support"
918 depends on FB && PCI
919 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
920 select FB_MODE_HELPERS
921 select FB_CFB_FILLRECT
922 select FB_CFB_COPYAREA
923 select FB_CFB_IMAGEBLIT
924 select BITREVERSE
925 select VGASTATE
926 help
927 This driver supports graphics boards with the nVidia chips, TNT
928 and newer. For very old chipsets, such as the RIVA128, then use
929 the rivafb.
930 Say Y if you have such a graphics board.
932 To compile this driver as a module, choose M here: the
933 module will be called nvidiafb.
935 config FB_NVIDIA_I2C
936 bool "Enable DDC Support"
937 depends on FB_NVIDIA
938 select FB_DDC
939 help
940 This enables I2C support for nVidia Chipsets. This is used
941 only for getting EDID information from the attached display
942 allowing for robust video mode handling and switching.
944 Because fbdev-2.6 requires that drivers must be able to
945 independently validate video mode parameters, you should say Y
946 here.
948 config FB_NVIDIA_DEBUG
949 bool "Lots of debug output"
950 depends on FB_NVIDIA
951 default n
952 help
953 Say Y here if you want the nVidia driver to output all sorts
954 of debugging information to provide to the maintainer when
955 something goes wrong.
957 config FB_NVIDIA_BACKLIGHT
958 bool "Support for backlight control"
959 depends on FB_NVIDIA
960 default y
961 help
962 Say Y here if you want to control the backlight of your display.
964 config FB_RIVA
965 tristate "nVidia Riva support"
966 depends on FB && PCI
967 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
968 select FB_MODE_HELPERS
969 select FB_CFB_FILLRECT
970 select FB_CFB_COPYAREA
971 select FB_CFB_IMAGEBLIT
972 select BITREVERSE
973 select VGASTATE
974 help
975 This driver supports graphics boards with the nVidia Riva/Geforce
976 chips.
977 Say Y if you have such a graphics board.
979 To compile this driver as a module, choose M here: the
980 module will be called rivafb.
982 config FB_RIVA_I2C
983 bool "Enable DDC Support"
984 depends on FB_RIVA
985 select FB_DDC
986 help
987 This enables I2C support for nVidia Chipsets. This is used
988 only for getting EDID information from the attached display
989 allowing for robust video mode handling and switching.
991 Because fbdev-2.6 requires that drivers must be able to
992 independently validate video mode parameters, you should say Y
993 here.
995 config FB_RIVA_DEBUG
996 bool "Lots of debug output"
997 depends on FB_RIVA
998 default n
999 help
1000 Say Y here if you want the Riva driver to output all sorts
1001 of debugging information to provide to the maintainer when
1002 something goes wrong.
1004 config FB_RIVA_BACKLIGHT
1005 bool "Support for backlight control"
1006 depends on FB_RIVA
1007 default y
1008 help
1009 Say Y here if you want to control the backlight of your display.
1011 config FB_I810
1012 tristate "Intel 810/815 support (EXPERIMENTAL)"
1013 depends on FB && EXPERIMENTAL && PCI && X86_32
1014 select AGP
1015 select AGP_INTEL
1016 select FB_MODE_HELPERS
1017 select FB_CFB_FILLRECT
1018 select FB_CFB_COPYAREA
1019 select FB_CFB_IMAGEBLIT
1020 select VGASTATE
1021 help
1022 This driver supports the on-board graphics built in to the Intel 810
1023 and 815 chipsets. Say Y if you have and plan to use such a board.
1025 To compile this driver as a module, choose M here: the
1026 module will be called i810fb.
1028 For more information, please read
1029 <file:Documentation/fb/intel810.txt>
1031 config FB_I810_GTF
1032 bool "use VESA Generalized Timing Formula"
1033 depends on FB_I810
1034 help
1035 If you say Y, then the VESA standard, Generalized Timing Formula
1036 or GTF, will be used to calculate the required video timing values
1037 per video mode. Since the GTF allows nondiscrete timings
1038 (nondiscrete being a range of values as opposed to discrete being a
1039 set of values), you'll be able to use any combination of horizontal
1040 and vertical resolutions, and vertical refresh rates without having
1041 to specify your own timing parameters. This is especially useful
1042 to maximize the performance of an aging display, or if you just
1043 have a display with nonstandard dimensions. A VESA compliant
1044 monitor is recommended, but can still work with non-compliant ones.
1045 If you need or want this, then select this option. The timings may
1046 not be compliant with Intel's recommended values. Use at your own
1047 risk.
1049 If you say N, the driver will revert to discrete video timings
1050 using a set recommended by Intel in their documentation.
1052 If unsure, say N.
1054 config FB_I810_I2C
1055 bool "Enable DDC Support"
1056 depends on FB_I810 && FB_I810_GTF
1057 select FB_DDC
1058 help
1060 config FB_LE80578
1061 tristate "Intel LE80578 (Vermilion) support"
1062 depends on FB && PCI && X86
1063 select FB_MODE_HELPERS
1064 select FB_CFB_FILLRECT
1065 select FB_CFB_COPYAREA
1066 select FB_CFB_IMAGEBLIT
1067 help
1068 This driver supports the LE80578 (Vermilion Range) chipset
1070 config FB_CARILLO_RANCH
1071 tristate "Intel Carillo Ranch support"
1072 depends on FB_LE80578 && FB && PCI && X86
1073 help
1074 This driver supports the LE80578 (Carillo Ranch) board
1076 config FB_INTEL
1077 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
1078 depends on FB && EXPERIMENTAL && PCI && X86
1079 select AGP
1080 select AGP_INTEL
1081 select FB_MODE_HELPERS
1082 select FB_CFB_FILLRECT
1083 select FB_CFB_COPYAREA
1084 select FB_CFB_IMAGEBLIT
1085 help
1086 This driver supports the on-board graphics built in to the Intel
1087 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
1088 Say Y if you have and plan to use such a board.
1090 If you say Y here and want DDC/I2C support you must first say Y to
1091 "I2C support" and "I2C bit-banging support" in the character devices
1092 section.
1094 If you say M here then "I2C support" and "I2C bit-banging support"
1095 can be build either as modules or built-in.
1097 To compile this driver as a module, choose M here: the
1098 module will be called intelfb.
1100 For more information, please read <file:Documentation/fb/intelfb.txt>
1102 config FB_INTEL_DEBUG
1103 bool "Intel driver Debug Messages"
1104 depends on FB_INTEL
1105 ---help---
1106 Say Y here if you want the Intel driver to output all sorts
1107 of debugging information to provide to the maintainer when
1108 something goes wrong.
1110 config FB_INTEL_I2C
1111 bool "DDC/I2C for Intel framebuffer support"
1112 depends on FB_INTEL
1113 select FB_DDC
1114 default y
1115 help
1116 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1118 config FB_MATROX
1119 tristate "Matrox acceleration"
1120 depends on FB && PCI
1121 select FB_CFB_FILLRECT
1122 select FB_CFB_COPYAREA
1123 select FB_CFB_IMAGEBLIT
1124 select FB_TILEBLITTING
1125 select FB_MACMODES if PPC_PMAC
1126 ---help---
1127 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1128 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1129 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1130 Matrox G400, G450 or G550 card in your box.
1132 To compile this driver as a module, choose M here: the
1133 module will be called matroxfb.
1135 You can pass several parameters to the driver at boot time or at
1136 module load time. The parameters look like "video=matrox:XXX", and
1137 are described in <file:Documentation/fb/matroxfb.txt>.
1139 config FB_MATROX_MILLENIUM
1140 bool "Millennium I/II support"
1141 depends on FB_MATROX
1142 help
1143 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1144 video card. If you select "Advanced lowlevel driver options" below,
1145 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1146 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1147 also use font widths different from 8.
1149 config FB_MATROX_MYSTIQUE
1150 bool "Mystique support"
1151 depends on FB_MATROX
1152 help
1153 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1154 video card. If you select "Advanced lowlevel driver options" below,
1155 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1156 packed pixel and 32 bpp packed pixel. You can also use font widths
1157 different from 8.
1159 config FB_MATROX_G
1160 bool "G100/G200/G400/G450/G550 support"
1161 depends on FB_MATROX
1162 ---help---
1163 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1164 video card. If you select "Advanced lowlevel driver options", you
1165 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1166 pixel and 32 bpp packed pixel. You can also use font widths
1167 different from 8.
1169 If you need support for G400 secondary head, you must first say Y to
1170 "I2C support" in the character devices section, and then to
1171 "Matrox I2C support" and "G400 second head support" here in the
1172 framebuffer section. G450/G550 secondary head and digital output
1173 are supported without additional modules.
1175 The driver starts in monitor mode. You must use the matroxset tool
1176 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1177 swap primary and secondary head outputs, or to change output mode.
1178 Secondary head driver always start in 640x480 resolution and you
1179 must use fbset to change it.
1181 Do not forget that second head supports only 16 and 32 bpp
1182 packed pixels, so it is a good idea to compile them into the kernel
1183 too. You can use only some font widths, as the driver uses generic
1184 painting procedures (the secondary head does not use acceleration
1185 engine).
1187 G450/G550 hardware can display TV picture only from secondary CRTC,
1188 and it performs no scaling, so picture must have 525 or 625 lines.
1190 config FB_MATROX_I2C
1191 tristate "Matrox I2C support"
1192 depends on FB_MATROX
1193 select FB_DDC
1194 ---help---
1195 This drivers creates I2C buses which are needed for accessing the
1196 DDC (I2C) bus present on all Matroxes, an I2C bus which
1197 interconnects Matrox optional devices, like MGA-TVO on G200 and
1198 G400, and the secondary head DDC bus, present on G400 only.
1200 You can say Y or M here if you want to experiment with monitor
1201 detection code. You must say Y or M here if you want to use either
1202 second head of G400 or MGA-TVO on G200 or G400.
1204 If you compile it as module, it will create a module named
1205 i2c-matroxfb.
1207 config FB_MATROX_MAVEN
1208 tristate "G400 second head support"
1209 depends on FB_MATROX_G && FB_MATROX_I2C
1210 ---help---
1211 WARNING !!! This support does not work with G450 !!!
1213 Say Y or M here if you want to use a secondary head (meaning two
1214 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1215 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1216 secondary head output is blanked while you are in X. With XFree
1217 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1218 the fbdev driver on first head and the fbdev driver on second head.
1220 If you compile it as module, two modules are created,
1221 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1222 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1223 also load i2c-matroxfb to get it to run.
1225 The driver starts in monitor mode and you must use the matroxset
1226 tool (available at
1227 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1228 PAL or NTSC or to swap primary and secondary head outputs.
1229 Secondary head driver also always start in 640x480 resolution, you
1230 must use fbset to change it.
1232 Also do not forget that second head supports only 16 and 32 bpp
1233 packed pixels, so it is a good idea to compile them into the kernel
1234 too. You can use only some font widths, as the driver uses generic
1235 painting procedures (the secondary head does not use acceleration
1236 engine).
1238 config FB_MATROX_MULTIHEAD
1239 bool "Multihead support"
1240 depends on FB_MATROX
1241 ---help---
1242 Say Y here if you have more than one (supported) Matrox device in
1243 your computer and you want to use all of them for different monitors
1244 ("multihead"). If you have only one device, you should say N because
1245 the driver compiled with Y is larger and a bit slower, especially on
1246 ia32 (ix86).
1248 If you said M to "Matrox unified accelerated driver" and N here, you
1249 will still be able to use several Matrox devices simultaneously:
1250 insert several instances of the module matroxfb into the kernel
1251 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1252 for the different Matrox devices. This method is slightly faster but
1253 uses 40 KB of kernel memory per Matrox card.
1255 There is no need for enabling 'Matrox multihead support' if you have
1256 only one Matrox card in the box.
1258 config FB_RADEON
1259 tristate "ATI Radeon display support"
1260 depends on FB && PCI
1261 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1262 select FB_MODE_HELPERS
1263 select FB_CFB_FILLRECT
1264 select FB_CFB_COPYAREA
1265 select FB_CFB_IMAGEBLIT
1266 select FB_MACMODES if PPC_OF
1267 help
1268 Choose this option if you want to use an ATI Radeon graphics card as
1269 a framebuffer device. There are both PCI and AGP versions. You
1270 don't need to choose this to run the Radeon in plain VGA mode.
1272 If you say Y here and want DDC/I2C support you must first say Y to
1273 "I2C support" and "I2C bit-banging support" in the character devices
1274 section.
1276 If you say M here then "I2C support" and "I2C bit-banging support"
1277 can be build either as modules or built-in.
1279 There is a product page at
1280 http://apps.ati.com/ATIcompare/
1282 config FB_RADEON_I2C
1283 bool "DDC/I2C for ATI Radeon support"
1284 depends on FB_RADEON
1285 select FB_DDC
1286 default y
1287 help
1288 Say Y here if you want DDC/I2C support for your Radeon board.
1290 config FB_RADEON_BACKLIGHT
1291 bool "Support for backlight control"
1292 depends on FB_RADEON
1293 default y
1294 help
1295 Say Y here if you want to control the backlight of your display.
1297 config FB_RADEON_DEBUG
1298 bool "Lots of debug output from Radeon driver"
1299 depends on FB_RADEON
1300 default n
1301 help
1302 Say Y here if you want the Radeon driver to output all sorts
1303 of debugging information to provide to the maintainer when
1304 something goes wrong.
1306 config FB_ATY128
1307 tristate "ATI Rage128 display support"
1308 depends on FB && PCI
1309 select FB_CFB_FILLRECT
1310 select FB_CFB_COPYAREA
1311 select FB_CFB_IMAGEBLIT
1312 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1313 select FB_MACMODES if PPC_PMAC
1314 help
1315 This driver supports graphics boards with the ATI Rage128 chips.
1316 Say Y if you have such a graphics board and read
1317 <file:Documentation/fb/aty128fb.txt>.
1319 To compile this driver as a module, choose M here: the
1320 module will be called aty128fb.
1322 config FB_ATY128_BACKLIGHT
1323 bool "Support for backlight control"
1324 depends on FB_ATY128
1325 default y
1326 help
1327 Say Y here if you want to control the backlight of your display.
1329 config FB_ATY
1330 tristate "ATI Mach64 display support" if PCI || ATARI
1331 depends on FB && !SPARC32
1332 select FB_CFB_FILLRECT
1333 select FB_CFB_COPYAREA
1334 select FB_CFB_IMAGEBLIT
1335 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1336 select FB_MACMODES if PPC
1337 help
1338 This driver supports graphics boards with the ATI Mach64 chips.
1339 Say Y if you have such a graphics board.
1341 To compile this driver as a module, choose M here: the
1342 module will be called atyfb.
1344 config FB_ATY_CT
1345 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1346 depends on PCI && FB_ATY
1347 default y if SPARC64 && PCI
1348 help
1349 Say Y here to support use of ATI's 64-bit Rage boards (or other
1350 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1351 framebuffer device. The ATI product support page for these boards
1352 is at <http://support.ati.com/products/pc/mach64/>.
1354 config FB_ATY_GENERIC_LCD
1355 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1356 depends on FB_ATY_CT
1357 help
1358 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1359 Rage XC, or Rage XL chipset.
1361 config FB_ATY_GX
1362 bool "Mach64 GX support" if PCI
1363 depends on FB_ATY
1364 default y if ATARI
1365 help
1366 Say Y here to support use of the ATI Mach64 Graphics Expression
1367 board (or other boards based on the Mach64 GX chipset) as a
1368 framebuffer device. The ATI product support page for these boards
1369 is at
1370 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1372 config FB_ATY_BACKLIGHT
1373 bool "Support for backlight control"
1374 depends on FB_ATY
1375 default y
1376 help
1377 Say Y here if you want to control the backlight of your display.
1379 config FB_S3
1380 tristate "S3 Trio/Virge support"
1381 depends on FB && PCI
1382 select FB_CFB_FILLRECT
1383 select FB_CFB_COPYAREA
1384 select FB_CFB_IMAGEBLIT
1385 select FB_TILEBLITTING
1386 select FB_SVGALIB
1387 select VGASTATE
1388 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1389 ---help---
1390 Driver for graphics boards with S3 Trio / S3 Virge chip.
1392 config FB_SAVAGE
1393 tristate "S3 Savage support"
1394 depends on FB && PCI && EXPERIMENTAL
1395 select FB_MODE_HELPERS
1396 select FB_CFB_FILLRECT
1397 select FB_CFB_COPYAREA
1398 select FB_CFB_IMAGEBLIT
1399 select VGASTATE
1400 help
1401 This driver supports notebooks and computers with S3 Savage PCI/AGP
1402 chips.
1404 Say Y if you have such a graphics card.
1406 To compile this driver as a module, choose M here; the module
1407 will be called savagefb.
1409 config FB_SAVAGE_I2C
1410 bool "Enable DDC2 Support"
1411 depends on FB_SAVAGE
1412 select FB_DDC
1413 help
1414 This enables I2C support for S3 Savage Chipsets. This is used
1415 only for getting EDID information from the attached display
1416 allowing for robust video mode handling and switching.
1418 Because fbdev-2.6 requires that drivers must be able to
1419 independently validate video mode parameters, you should say Y
1420 here.
1422 config FB_SAVAGE_ACCEL
1423 bool "Enable Console Acceleration"
1424 depends on FB_SAVAGE
1425 default n
1426 help
1427 This option will compile in console acceleration support. If
1428 the resulting framebuffer console has bothersome glitches, then
1429 choose N here.
1431 config FB_SIS
1432 tristate "SiS/XGI display support"
1433 depends on FB && PCI
1434 select FB_CFB_FILLRECT
1435 select FB_CFB_COPYAREA
1436 select FB_CFB_IMAGEBLIT
1437 help
1438 This is the frame buffer device driver for the SiS 300, 315, 330
1439 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1440 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1442 To compile this driver as a module, choose M here; the module
1443 will be called sisfb.
1445 config FB_SIS_300
1446 bool "SiS 300 series support"
1447 depends on FB_SIS
1448 help
1449 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1451 config FB_SIS_315
1452 bool "SiS 315/330/340 series and XGI support"
1453 depends on FB_SIS
1454 help
1455 Say Y here to support use of the SiS 315, 330 and 340 series
1456 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1457 as XGI V3XT, V5, V8 and Z7.
1459 config FB_NEOMAGIC
1460 tristate "NeoMagic display support"
1461 depends on FB && PCI
1462 select FB_MODE_HELPERS
1463 select FB_CFB_FILLRECT
1464 select FB_CFB_COPYAREA
1465 select FB_CFB_IMAGEBLIT
1466 select VGASTATE
1467 help
1468 This driver supports notebooks with NeoMagic PCI chips.
1469 Say Y if you have such a graphics card.
1471 To compile this driver as a module, choose M here: the
1472 module will be called neofb.
1474 config FB_KYRO
1475 tristate "IMG Kyro support"
1476 depends on FB && PCI
1477 select FB_CFB_FILLRECT
1478 select FB_CFB_COPYAREA
1479 select FB_CFB_IMAGEBLIT
1480 help
1481 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1482 graphics board.
1484 To compile this driver as a module, choose M here: the
1485 module will be called kyrofb.
1487 config FB_3DFX
1488 tristate "3Dfx Banshee/Voodoo3 display support"
1489 depends on FB && PCI
1490 select FB_CFB_IMAGEBLIT
1491 select FB_CFB_FILLRECT
1492 select FB_CFB_COPYAREA
1493 help
1494 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1495 chips. Say Y if you have such a graphics board.
1497 To compile this driver as a module, choose M here: the
1498 module will be called tdfxfb.
1500 config FB_3DFX_ACCEL
1501 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1502 depends on FB_3DFX && EXPERIMENTAL
1503 ---help---
1504 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1505 with acceleration functions.
1508 config FB_VOODOO1
1509 tristate "3Dfx Voodoo Graphics (sst1) support"
1510 depends on FB && PCI
1511 select FB_CFB_FILLRECT
1512 select FB_CFB_COPYAREA
1513 select FB_CFB_IMAGEBLIT
1514 ---help---
1515 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1516 Voodoo2 (cvg) based graphics card.
1518 To compile this driver as a module, choose M here: the
1519 module will be called sstfb.
1521 WARNING: Do not use any application that uses the 3D engine
1522 (namely glide) while using this driver.
1523 Please read the <file:Documentation/fb/sstfb.txt> for supported
1524 options and other important info support.
1526 config FB_VT8623
1527 tristate "VIA VT8623 support"
1528 depends on FB && PCI
1529 select FB_CFB_FILLRECT
1530 select FB_CFB_COPYAREA
1531 select FB_CFB_IMAGEBLIT
1532 select FB_TILEBLITTING
1533 select FB_SVGALIB
1534 select VGASTATE
1535 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1536 ---help---
1537 Driver for CastleRock integrated graphics core in the
1538 VIA VT8623 [Apollo CLE266] chipset.
1540 config FB_CYBLA
1541 tristate "Cyberblade/i1 support"
1542 depends on FB && PCI && X86_32 && !64BIT
1543 select FB_CFB_IMAGEBLIT
1544 select VIDEO_SELECT
1545 ---help---
1546 This driver is supposed to support the Trident Cyberblade/i1
1547 graphics core integrated in the VIA VT8601A North Bridge,
1548 also known as VIA Apollo PLE133.
1550 Status:
1551 - Developed, tested and working on EPIA 5000 and EPIA 800.
1552 - Does work reliable on all systems with CRT/LCD connected to
1553 normal VGA ports.
1554 - Should work on systems that do use the internal LCD port, but
1555 this is absolutely not tested.
1557 Character imageblit, copyarea and rectangle fill are hw accelerated,
1558 ypan scrolling is used by default.
1560 Please do read <file:Documentation/fb/cyblafb/*>.
1562 To compile this driver as a module, choose M here: the
1563 module will be called cyblafb.
1565 config FB_TRIDENT
1566 tristate "Trident support"
1567 depends on FB && PCI
1568 select FB_CFB_FILLRECT
1569 select FB_CFB_COPYAREA
1570 select FB_CFB_IMAGEBLIT
1571 ---help---
1572 This driver is supposed to support graphics boards with the
1573 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1574 but also on some motherboards. For more information, read
1575 <file:Documentation/fb/tridentfb.txt>
1577 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1578 instead.
1580 Say Y if you have such a graphics board.
1583 To compile this driver as a module, choose M here: the
1584 module will be called tridentfb.
1586 config FB_TRIDENT_ACCEL
1587 bool "Trident Acceleration functions (EXPERIMENTAL)"
1588 depends on FB_TRIDENT && EXPERIMENTAL
1589 ---help---
1590 This will compile the Trident frame buffer device with
1591 acceleration functions.
1593 config FB_ARK
1594 tristate "ARK 2000PV support"
1595 depends on FB && PCI
1596 select FB_CFB_FILLRECT
1597 select FB_CFB_COPYAREA
1598 select FB_CFB_IMAGEBLIT
1599 select FB_TILEBLITTING
1600 select FB_SVGALIB
1601 select VGASTATE
1602 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1603 ---help---
1604 Driver for PCI graphics boards with ARK 2000PV chip
1605 and ICS 5342 RAMDAC.
1607 config FB_PM3
1608 tristate "Permedia3 support (EXPERIMENTAL)"
1609 depends on FB && PCI && EXPERIMENTAL
1610 select FB_CFB_FILLRECT
1611 select FB_CFB_COPYAREA
1612 select FB_CFB_IMAGEBLIT
1613 help
1614 This is the frame buffer device driver for the 3DLabs Permedia3
1615 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1616 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1617 and maybe other boards.
1619 config FB_AU1100
1620 bool "Au1100 LCD Driver"
1621 depends on (FB = y) && MIPS && SOC_AU1100
1622 select FB_CFB_FILLRECT
1623 select FB_CFB_COPYAREA
1624 select FB_CFB_IMAGEBLIT
1625 help
1626 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1627 various panels and CRTs by passing in kernel cmd line option
1628 au1100fb:panel=<name>.
1630 config FB_AU1200
1631 bool "Au1200 LCD Driver"
1632 depends on (FB = y) && MIPS && SOC_AU1200
1633 select FB_CFB_FILLRECT
1634 select FB_CFB_COPYAREA
1635 select FB_CFB_IMAGEBLIT
1636 help
1637 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1638 various panels and CRTs by passing in kernel cmd line option
1639 au1200fb:panel=<name>.
1641 source "drivers/video/geode/Kconfig"
1643 config FB_HIT
1644 tristate "HD64461 Frame Buffer support"
1645 depends on FB && HD64461
1646 select FB_CFB_FILLRECT
1647 select FB_CFB_COPYAREA
1648 select FB_CFB_IMAGEBLIT
1649 help
1650 This is the frame buffer device driver for the Hitachi HD64461 LCD
1651 frame buffer card.
1653 config FB_PMAG_AA
1654 bool "PMAG-AA TURBOchannel framebuffer support"
1655 depends on (FB = y) && TC
1656 select FB_CFB_FILLRECT
1657 select FB_CFB_COPYAREA
1658 select FB_CFB_IMAGEBLIT
1659 help
1660 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1661 used mainly in the MIPS-based DECstation series.
1663 config FB_PMAG_BA
1664 tristate "PMAG-BA TURBOchannel framebuffer support"
1665 depends on FB && TC
1666 select FB_CFB_FILLRECT
1667 select FB_CFB_COPYAREA
1668 select FB_CFB_IMAGEBLIT
1669 help
1670 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1671 used mainly in the MIPS-based DECstation series.
1673 config FB_PMAGB_B
1674 tristate "PMAGB-B TURBOchannel framebuffer support"
1675 depends on FB && TC
1676 select FB_CFB_FILLRECT
1677 select FB_CFB_COPYAREA
1678 select FB_CFB_IMAGEBLIT
1679 help
1680 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1681 in the MIPS-based DECstation series. The card is currently only
1682 supported in 1280x1024x8 mode.
1684 config FB_MAXINE
1685 bool "Maxine (Personal DECstation) onboard framebuffer support"
1686 depends on (FB = y) && MACH_DECSTATION
1687 select FB_CFB_FILLRECT
1688 select FB_CFB_COPYAREA
1689 select FB_CFB_IMAGEBLIT
1690 help
1691 Support for the onboard framebuffer (1024x768x8) in the Personal
1692 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1693 Codename "Maxine").
1695 config FB_G364
1696 bool "G364 frame buffer support"
1697 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1701 help
1702 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1703 Olivetti M700-10 systems.
1705 config FB_68328
1706 bool "Motorola 68328 native frame buffer support"
1707 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1711 help
1712 Say Y here if you want to support the built-in frame buffer of
1713 the Motorola 68328 CPU family.
1715 config FB_PXA
1716 tristate "PXA LCD framebuffer support"
1717 depends on FB && ARCH_PXA
1718 select FB_CFB_FILLRECT
1719 select FB_CFB_COPYAREA
1720 select FB_CFB_IMAGEBLIT
1721 ---help---
1722 Frame buffer driver for the built-in LCD controller in the Intel
1723 PXA2x0 processor.
1725 This driver is also available as a module ( = code which can be
1726 inserted and removed from the running kernel whenever you want). The
1727 module will be called pxafb. If you want to compile it as a module,
1728 say M here and read <file:Documentation/kbuild/modules.txt>.
1730 If unsure, say N.
1732 config FB_PXA_PARAMETERS
1733 bool "PXA LCD command line parameters"
1734 default n
1735 depends on FB_PXA
1736 ---help---
1737 Enable the use of kernel command line or module parameters
1738 to configure the physical properties of the LCD panel when
1739 using the PXA LCD driver.
1741 This option allows you to override the panel parameters
1742 supplied by the platform in order to support multiple
1743 different models of flatpanel. If you will only be using a
1744 single model of flatpanel then you can safely leave this
1745 option disabled.
1747 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1749 config FB_MBX
1750 tristate "2700G LCD framebuffer support"
1751 depends on FB && ARCH_PXA
1752 select FB_CFB_FILLRECT
1753 select FB_CFB_COPYAREA
1754 select FB_CFB_IMAGEBLIT
1755 ---help---
1756 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1757 Accelerator
1759 config FB_MBX_DEBUG
1760 bool "Enable debugging info via debugfs"
1761 depends on FB_MBX && DEBUG_FS
1762 default n
1763 ---help---
1764 Enable this if you want debugging information using the debug
1765 filesystem (debugfs)
1767 If unsure, say N.
1769 config FB_W100
1770 tristate "W100 frame buffer support"
1771 depends on FB && PXA_SHARPSL
1772 select FB_CFB_FILLRECT
1773 select FB_CFB_COPYAREA
1774 select FB_CFB_IMAGEBLIT
1775 ---help---
1776 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1778 This driver is also available as a module ( = code which can be
1779 inserted and removed from the running kernel whenever you want). The
1780 module will be called w100fb. If you want to compile it as a module,
1781 say M here and read <file:Documentation/kbuild/modules.txt>.
1783 If unsure, say N.
1785 config FB_S3C2410
1786 tristate "S3C2410 LCD framebuffer support"
1787 depends on FB && ARCH_S3C2410
1788 select FB_CFB_FILLRECT
1789 select FB_CFB_COPYAREA
1790 select FB_CFB_IMAGEBLIT
1791 ---help---
1792 Frame buffer driver for the built-in LCD controller in the Samsung
1793 S3C2410 processor.
1795 This driver is also available as a module ( = code which can be
1796 inserted and removed from the running kernel whenever you want). The
1797 module will be called s3c2410fb. If you want to compile it as a module,
1798 say M here and read <file:Documentation/kbuild/modules.txt>.
1800 If unsure, say N.
1801 config FB_S3C2410_DEBUG
1802 bool "S3C2410 lcd debug messages"
1803 depends on FB_S3C2410
1804 help
1805 Turn on debugging messages. Note that you can set/unset at run time
1806 through sysfs
1808 config FB_SM501
1809 tristate "Silicon Motion SM501 framebuffer support"
1810 depends on FB && MFD_SM501
1811 select FB_CFB_FILLRECT
1812 select FB_CFB_COPYAREA
1813 select FB_CFB_IMAGEBLIT
1814 ---help---
1815 Frame buffer driver for the CRT and LCD controllers in the Silicon
1816 Motion SM501.
1818 This driver is also available as a module ( = code which can be
1819 inserted and removed from the running kernel whenever you want). The
1820 module will be called sm501fb. If you want to compile it as a module,
1821 say M here and read <file:Documentation/kbuild/modules.txt>.
1823 If unsure, say N.
1826 config FB_PNX4008_DUM
1827 tristate "Display Update Module support on Philips PNX4008 board"
1828 depends on FB && ARCH_PNX4008
1829 ---help---
1830 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1832 config FB_PNX4008_DUM_RGB
1833 tristate "RGB Framebuffer support on Philips PNX4008 board"
1834 depends on FB_PNX4008_DUM
1835 select FB_CFB_FILLRECT
1836 select FB_CFB_COPYAREA
1837 select FB_CFB_IMAGEBLIT
1838 ---help---
1839 Say Y here to enable support for PNX4008 RGB Framebuffer
1841 config FB_IBM_GXT4500
1842 tristate "Framebuffer support for IBM GXT4500P adaptor"
1843 depends on FB && PPC
1844 select FB_CFB_FILLRECT
1845 select FB_CFB_COPYAREA
1846 select FB_CFB_IMAGEBLIT
1847 ---help---
1848 Say Y here to enable support for the IBM GXT4500P display
1849 adaptor, found on some IBM System P (pSeries) machines.
1851 config FB_PS3
1852 tristate "PS3 GPU framebuffer driver"
1853 depends on FB && PS3_PS3AV
1854 select FB_SYS_FILLRECT
1855 select FB_SYS_COPYAREA
1856 select FB_SYS_IMAGEBLIT
1857 select FB_SYS_FOPS
1858 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1859 ---help---
1860 Include support for the virtual frame buffer in the PS3 platform.
1862 config FB_PS3_DEFAULT_SIZE_M
1863 int "PS3 default frame buffer size (in MiB)"
1864 depends on FB_PS3
1865 default 9
1866 ---help---
1867 This is the default size (in MiB) of the virtual frame buffer in
1868 the PS3.
1869 The default value can be overridden on the kernel command line
1870 using the "ps3fb" option (e.g. "ps3fb=9M");
1872 config FB_XILINX
1873 tristate "Xilinx frame buffer support"
1874 depends on FB && XILINX_VIRTEX
1875 select FB_CFB_FILLRECT
1876 select FB_CFB_COPYAREA
1877 select FB_CFB_IMAGEBLIT
1878 ---help---
1879 Include support for the Xilinx ML300/ML403 reference design
1880 framebuffer. ML300 carries a 640*480 LCD display on the board,
1881 ML403 uses a standard DB15 VGA connector.
1883 config FB_VIRTUAL
1884 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1885 depends on FB
1886 select FB_SYS_FILLRECT
1887 select FB_SYS_COPYAREA
1888 select FB_SYS_IMAGEBLIT
1889 select FB_SYS_FOPS
1890 ---help---
1891 This is a `virtual' frame buffer device. It operates on a chunk of
1892 unswappable kernel memory instead of on the memory of a graphics
1893 board. This means you cannot see any output sent to this frame
1894 buffer device, while it does consume precious memory. The main use
1895 of this frame buffer device is testing and debugging the frame
1896 buffer subsystem. Do NOT enable it for normal systems! To protect
1897 the innocent, it has to be enabled explicitly at boot time using the
1898 kernel option `video=vfb:'.
1900 To compile this driver as a module, choose M here: the
1901 module will be called vfb. In order to load it, you must use
1902 the vfb_enable=1 option.
1904 If unsure, say N.
1906 source "drivers/video/omap/Kconfig"
1908 source "drivers/video/backlight/Kconfig"
1909 source "drivers/video/display/Kconfig"
1911 if VT
1912 source "drivers/video/console/Kconfig"
1913 endif
1915 if FB || SGI_NEWPORT_CONSOLE
1916 source "drivers/video/logo/Kconfig"
1917 endif
1919 endmenu