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