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