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