5 menu "Graphics support"
8 bool "Enable firmware EDID"
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.
23 tristate "Support for frame buffer devices"
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
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.
58 depends on FB && I2C && I2C_ALGOBIT
61 config FB_CFB_FILLRECT
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
75 Include the cfb_copyarea function for generic software area copying.
76 This is used by drivers that don't provide their own (accelerated)
79 config FB_CFB_IMAGEBLIT
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.
96 select BACKLIGHT_LCD_SUPPORT
97 select BACKLIGHT_CLASS_DEVICE
100 config FB_MODE_HELPERS
101 bool "Enable Video Mode Handling Helpers"
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"
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
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
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.
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
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
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
163 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
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
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.
183 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
185 default FB_ARMCLCD_SHARP_LQ035Q7DB02
187 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
188 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
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"
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"
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"
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"
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"
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"
239 This is an implementation of the Hitachi 800x480.
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
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
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
262 Say Y to enable the Framebuffer driver for the CLPS7111 and
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
272 This is a framebuffer device for the SA-1100 LCD Controller.
273 See <http://www.linux-fbdev.org/> for information on framebuffer
276 If you plan to use the LCD display with your SA-1100 system, say
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
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
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.
300 depends on (FB = y) && APOLLO
302 select FB_CFB_FILLRECT
303 select FB_CFB_IMAGEBLIT
307 depends on (FB = y) && Q40
309 select FB_CFB_FILLRECT
310 select FB_CFB_COPYAREA
311 select FB_CFB_IMAGEBLIT
314 tristate "Amiga native chipset support"
315 depends on FB && AMIGA
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.
324 bool "Amiga OCS chipset support"
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.
332 bool "Amiga ECS chipset support"
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
341 bool "Amiga AGA chipset support"
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;
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
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.
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
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.
378 tristate "Amiga Retina Z3 support"
379 depends on (FB = y) && ZORRO && BROKEN
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
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
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).
396 tristate "Arc Monochrome LCD board support"
398 select FB_CFB_FILLRECT
399 select FB_CFB_COPYAREA
400 select FB_CFB_IMAGEBLIT
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.
411 bool "Atari native chipset support"
412 depends on (FB = y) && ATARI && BROKEN
414 This is the frame buffer device driver for the builtin graphics
415 chipset found in Ataris.
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
425 Say Y if you want support with Open Firmware for your graphics
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
436 This driver supports a frame buffer for the graphics adapter in the
437 Power Macintosh 7300 and others.
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
447 This driver supports a frame buffer for the "platinum" graphics
448 adapter in some Power Macintoshes.
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
458 This driver supports a frame buffer for the "valkyrie" graphics
459 adapter in some Power Macintoshes.
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
468 This is the frame buffer device driver for the Chips & Technologies
469 65550 graphics chip in PowerBooks.
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
478 This is the frame buffer device driver for the Asiliant 69030 chipset
481 bool "IMS Twin Turbo display support"
482 depends on (FB = y) && PCI
483 select FB_CFB_IMAGEBLIT
484 select FB_MACMODES if PPC
486 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
487 many Macintosh and compatible computers.
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
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.
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
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".
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
530 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
533 depends on (FB = y) && HP300
534 select FB_CFB_FILLRECT
535 select FB_CFB_IMAGEBLIT
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
546 This is the frame buffer device driver for generic TGA graphic
547 cards. Say Y if you have one of those.
550 bool "VESA VGA graphics support"
551 depends on (FB = y) && X86
552 select FB_CFB_FILLRECT
553 select FB_CFB_COPYAREA
554 select FB_CFB_IMAGEBLIT
557 This is the frame buffer device driver for generic VESA 2.0
558 compliant graphic cards. The older VESA 1.2 cards are not supported.
559 You will get a boot time penguin logo at no additional cost. Please
560 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
563 bool "Intel-based Macintosh Framebuffer Support"
564 depends on (FB = y) && X86 && EFI
565 select FB_CFB_FILLRECT
566 select FB_CFB_COPYAREA
567 select FB_CFB_IMAGEBLIT
569 This is the frame buffer device driver for the Intel-based Macintosh
572 tristate "Hercules mono graphics support"
574 select FB_CFB_FILLRECT
575 select FB_CFB_COPYAREA
576 select FB_CFB_IMAGEBLIT
578 Say Y here if you have a Hercules mono graphics card.
580 To compile this driver as a module, choose M here: the
581 module will be called hgafb.
583 As this card technology is 15 years old, most people will answer N
587 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
588 depends on FB_HGA && EXPERIMENTAL
590 This will compile the Hercules mono graphics with
591 acceleration functions.
594 tristate "SGI Visual Workstation framebuffer support"
595 depends on FB && X86_VISWS
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 SGI Visual Workstation support for framebuffer graphics.
603 bool "SGI Graphics Backend frame buffer support"
604 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
605 select FB_CFB_FILLRECT
606 select FB_CFB_COPYAREA
607 select FB_CFB_IMAGEBLIT
609 This is the frame buffer device driver for SGI Graphics Backend.
610 This chip is used in SGI O2 and Visual Workstation 320/540.
613 int "Video memory size in MB"
617 This is the amount of memory reserved for the framebuffer,
618 which can be any value between 1MB and 8MB.
621 bool "Sun3 framebuffer support"
622 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
625 bool "SBUS and UPA framebuffers"
626 depends on (FB = y) && SPARC
628 Say Y if you want support for SBUS or UPA based frame buffer device.
632 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
637 This is the frame buffer device driver for the BWtwo frame buffer.
640 bool "CGthree support"
641 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
642 select FB_CFB_FILLRECT
643 select FB_CFB_COPYAREA
644 select FB_CFB_IMAGEBLIT
646 This is the frame buffer device driver for the CGthree frame buffer.
649 bool "CGsix (GX,TurboGX) support"
650 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
654 This is the frame buffer device driver for the CGsix (GX, TurboGX)
658 tristate "NEC PowerVR 2 display support"
659 depends on FB && SH_DREAMCAST
660 select FB_CFB_FILLRECT
661 select FB_CFB_COPYAREA
662 select FB_CFB_IMAGEBLIT
664 Say Y here if you have a PowerVR 2 card in your box. If you plan to
665 run linux on your Dreamcast, you will have to say Y here.
666 This driver may or may not work on other PowerVR 2 cards, but is
667 totally untested. Use at your own risk. If unsure, say N.
669 To compile this driver as a module, choose M here: the
670 module will be called pvr2fb.
672 You can pass several parameters to the driver at boot time or at
673 module load time. The parameters look like "video=pvr2:XXX", where
674 the meaning of XXX can be found at the end of the main source file
675 (<file:drivers/video/pvr2fb.c>). Please see the file
676 <file:Documentation/fb/pvr2fb.txt>.
679 bool "Epson 1355 framebuffer support"
680 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
681 select FB_CFB_FILLRECT
682 select FB_CFB_COPYAREA
683 select FB_CFB_IMAGEBLIT
685 Build in support for the SED1355 Epson Research Embedded RAMDAC
686 LCD/CRT Controller (since redesignated as the S1D13505) as a
687 framebuffer. Product specs at
688 <http://www.erd.epson.com/vdc/html/products.htm>.
691 tristate "Epson S1D13XXX framebuffer support"
693 select FB_CFB_FILLRECT
694 select FB_CFB_COPYAREA
695 select FB_CFB_IMAGEBLIT
697 Support for S1D13XXX framebuffer device family (currently only
698 working with S1D13806). Product specs at
699 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
702 tristate "nVidia Framebuffer Support"
704 select I2C_ALGOBIT if FB_NVIDIA_I2C
705 select I2C if FB_NVIDIA_I2C
706 select FB_MODE_HELPERS
707 select FB_CFB_FILLRECT
708 select FB_CFB_COPYAREA
709 select FB_CFB_IMAGEBLIT
712 This driver supports graphics boards with the nVidia chips, TNT
713 and newer. For very old chipsets, such as the RIVA128, then use
715 Say Y if you have such a graphics board.
717 To compile this driver as a module, choose M here: the
718 module will be called nvidiafb.
721 bool "Enable DDC Support"
724 This enables I2C support for nVidia Chipsets. This is used
725 only for getting EDID information from the attached display
726 allowing for robust video mode handling and switching.
728 Because fbdev-2.6 requires that drivers must be able to
729 independently validate video mode parameters, you should say Y
732 config FB_NVIDIA_BACKLIGHT
733 bool "Support for backlight control"
734 depends on FB_NVIDIA && PMAC_BACKLIGHT
738 Say Y here if you want to control the backlight of your display.
741 tristate "nVidia Riva support"
743 select I2C_ALGOBIT if FB_RIVA_I2C
744 select I2C if FB_RIVA_I2C
745 select FB_DDC if FB_RIVA_I2C
746 select FB_MODE_HELPERS
747 select FB_CFB_FILLRECT
748 select FB_CFB_COPYAREA
749 select FB_CFB_IMAGEBLIT
752 This driver supports graphics boards with the nVidia Riva/Geforce
754 Say Y if you have such a graphics board.
756 To compile this driver as a module, choose M here: the
757 module will be called rivafb.
760 bool "Enable DDC Support"
763 This enables I2C support for nVidia Chipsets. This is used
764 only for getting EDID information from the attached display
765 allowing for robust video mode handling and switching.
767 Because fbdev-2.6 requires that drivers must be able to
768 independently validate video mode parameters, you should say Y
772 bool "Lots of debug output from Riva(nVidia) driver"
776 Say Y here if you want the Riva driver to output all sorts
777 of debugging information to provide to the maintainer when
778 something goes wrong.
780 config FB_RIVA_BACKLIGHT
781 bool "Support for backlight control"
782 depends on FB_RIVA && PMAC_BACKLIGHT
786 Say Y here if you want to control the backlight of your display.
789 tristate "Intel 810/815 support (EXPERIMENTAL)"
790 depends on FB && EXPERIMENTAL && PCI && X86_32
793 select FB_MODE_HELPERS
794 select FB_CFB_FILLRECT
795 select FB_CFB_COPYAREA
796 select FB_CFB_IMAGEBLIT
798 This driver supports the on-board graphics built in to the Intel 810
799 and 815 chipsets. Say Y if you have and plan to use such a board.
801 To compile this driver as a module, choose M here: the
802 module will be called i810fb.
804 For more information, please read
805 <file:Documentation/fb/intel810.txt>
808 bool "use VESA Generalized Timing Formula"
811 If you say Y, then the VESA standard, Generalized Timing Formula
812 or GTF, will be used to calculate the required video timing values
813 per video mode. Since the GTF allows nondiscrete timings
814 (nondiscrete being a range of values as opposed to discrete being a
815 set of values), you'll be able to use any combination of horizontal
816 and vertical resolutions, and vertical refresh rates without having
817 to specify your own timing parameters. This is especially useful
818 to maximize the performance of an aging display, or if you just
819 have a display with nonstandard dimensions. A VESA compliant
820 monitor is recommended, but can still work with non-compliant ones.
821 If you need or want this, then select this option. The timings may
822 not be compliant with Intel's recommended values. Use at your own
825 If you say N, the driver will revert to discrete video timings
826 using a set recommended by Intel in their documentation.
831 bool "Enable DDC Support"
832 depends on FB_I810 && FB_I810_GTF
839 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
840 depends on FB && EXPERIMENTAL && PCI && X86
843 select I2C_ALGOBIT if FB_INTEL_I2C
844 select I2C if FB_INTEL_I2C
845 select FB_MODE_HELPERS
846 select FB_CFB_FILLRECT
847 select FB_CFB_COPYAREA
848 select FB_CFB_IMAGEBLIT
850 This driver supports the on-board graphics built in to the Intel
851 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
852 Say Y if you have and plan to use such a board.
854 If you say Y here and want DDC/I2C support you must first say Y to
855 "I2C support" and "I2C bit-banging support" in the character devices
858 If you say M here then "I2C support" and "I2C bit-banging support"
859 can be build either as modules or built-in.
861 To compile this driver as a module, choose M here: the
862 module will be called intelfb.
864 For more information, please read <file:Documentation/fb/intelfb.txt>
866 config FB_INTEL_DEBUG
867 bool "Intel driver Debug Messages"
870 Say Y here if you want the Intel driver to output all sorts
871 of debugging information to provide to the maintainer when
872 something goes wrong.
875 bool "DDC/I2C for Intel framebuffer support"
879 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
882 tristate "Matrox acceleration"
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
887 select FB_TILEBLITTING
888 select FB_MACMODES if PPC_PMAC
890 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
891 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
892 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
893 Matrox G400, G450 or G550 card in your box.
895 To compile this driver as a module, choose M here: the
896 module will be called matroxfb.
898 You can pass several parameters to the driver at boot time or at
899 module load time. The parameters look like "video=matrox:XXX", and
900 are described in <file:Documentation/fb/matroxfb.txt>.
902 config FB_MATROX_MILLENIUM
903 bool "Millennium I/II support"
906 Say Y here if you have a Matrox Millennium or Matrox Millennium II
907 video card. If you select "Advanced lowlevel driver options" below,
908 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
909 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
910 also use font widths different from 8.
912 config FB_MATROX_MYSTIQUE
913 bool "Mystique support"
916 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
917 video card. If you select "Advanced lowlevel driver options" below,
918 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
919 packed pixel and 32 bpp packed pixel. You can also use font widths
923 bool "G100/G200/G400/G450/G550 support"
926 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
927 video card. If you select "Advanced lowlevel driver options", you
928 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
929 pixel and 32 bpp packed pixel. You can also use font widths
932 If you need support for G400 secondary head, you must first say Y to
933 "I2C support" in the character devices section, and then to
934 "Matrox I2C support" and "G400 second head support" here in the
935 framebuffer section. G450/G550 secondary head and digital output
936 are supported without additional modules.
938 The driver starts in monitor mode. You must use the matroxset tool
939 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
940 swap primary and secondary head outputs, or to change output mode.
941 Secondary head driver always start in 640x480 resolution and you
942 must use fbset to change it.
944 Do not forget that second head supports only 16 and 32 bpp
945 packed pixels, so it is a good idea to compile them into the kernel
946 too. You can use only some font widths, as the driver uses generic
947 painting procedures (the secondary head does not use acceleration
950 G450/G550 hardware can display TV picture only from secondary CRTC,
951 and it performs no scaling, so picture must have 525 or 625 lines.
954 tristate "Matrox I2C support"
955 depends on FB_MATROX && I2C
958 This drivers creates I2C buses which are needed for accessing the
959 DDC (I2C) bus present on all Matroxes, an I2C bus which
960 interconnects Matrox optional devices, like MGA-TVO on G200 and
961 G400, and the secondary head DDC bus, present on G400 only.
963 You can say Y or M here if you want to experiment with monitor
964 detection code. You must say Y or M here if you want to use either
965 second head of G400 or MGA-TVO on G200 or G400.
967 If you compile it as module, it will create a module named
970 config FB_MATROX_MAVEN
971 tristate "G400 second head support"
972 depends on FB_MATROX_G && FB_MATROX_I2C
974 WARNING !!! This support does not work with G450 !!!
976 Say Y or M here if you want to use a secondary head (meaning two
977 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
978 head is not compatible with accelerated XFree 3.3.x SVGA servers -
979 secondary head output is blanked while you are in X. With XFree
980 3.9.17 preview you can use both heads if you use SVGA over fbdev or
981 the fbdev driver on first head and the fbdev driver on second head.
983 If you compile it as module, two modules are created,
984 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
985 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
986 also load i2c-matroxfb to get it to run.
988 The driver starts in monitor mode and you must use the matroxset
990 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
991 PAL or NTSC or to swap primary and secondary head outputs.
992 Secondary head driver also always start in 640x480 resolution, you
993 must use fbset to change it.
995 Also do not forget that second head supports only 16 and 32 bpp
996 packed pixels, so it is a good idea to compile them into the kernel
997 too. You can use only some font widths, as the driver uses generic
998 painting procedures (the secondary head does not use acceleration
1001 config FB_MATROX_MULTIHEAD
1002 bool "Multihead support"
1003 depends on FB_MATROX
1005 Say Y here if you have more than one (supported) Matrox device in
1006 your computer and you want to use all of them for different monitors
1007 ("multihead"). If you have only one device, you should say N because
1008 the driver compiled with Y is larger and a bit slower, especially on
1011 If you said M to "Matrox unified accelerated driver" and N here, you
1012 will still be able to use several Matrox devices simultaneously:
1013 insert several instances of the module matroxfb into the kernel
1014 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1015 for the different Matrox devices. This method is slightly faster but
1016 uses 40 KB of kernel memory per Matrox card.
1018 There is no need for enabling 'Matrox multihead support' if you have
1019 only one Matrox card in the box.
1022 tristate "ATI Radeon display support"
1023 depends on FB && PCI
1024 select I2C_ALGOBIT if FB_RADEON_I2C
1025 select I2C if FB_RADEON_I2C
1026 select FB_DDC if FB_RADEON_I2C
1027 select FB_MODE_HELPERS
1028 select FB_CFB_FILLRECT
1029 select FB_CFB_COPYAREA
1030 select FB_CFB_IMAGEBLIT
1031 select FB_MACMODES if PPC_OF
1033 Choose this option if you want to use an ATI Radeon graphics card as
1034 a framebuffer device. There are both PCI and AGP versions. You
1035 don't need to choose this to run the Radeon in plain VGA mode.
1037 If you say Y here and want DDC/I2C support you must first say Y to
1038 "I2C support" and "I2C bit-banging support" in the character devices
1041 If you say M here then "I2C support" and "I2C bit-banging support"
1042 can be build either as modules or built-in.
1044 There is a product page at
1045 http://apps.ati.com/ATIcompare/
1047 config FB_RADEON_I2C
1048 bool "DDC/I2C for ATI Radeon support"
1049 depends on FB_RADEON
1052 Say Y here if you want DDC/I2C support for your Radeon board.
1054 config FB_RADEON_BACKLIGHT
1055 bool "Support for backlight control"
1056 depends on FB_RADEON && PMAC_BACKLIGHT
1060 Say Y here if you want to control the backlight of your display.
1062 config FB_RADEON_DEBUG
1063 bool "Lots of debug output from Radeon driver"
1064 depends on FB_RADEON
1067 Say Y here if you want the Radeon driver to output all sorts
1068 of debugging information to provide to the maintainer when
1069 something goes wrong.
1072 tristate "ATI Rage128 display support"
1073 depends on FB && PCI
1074 select FB_CFB_FILLRECT
1075 select FB_CFB_COPYAREA
1076 select FB_CFB_IMAGEBLIT
1077 select FB_MACMODES if PPC_PMAC
1079 This driver supports graphics boards with the ATI Rage128 chips.
1080 Say Y if you have such a graphics board and read
1081 <file:Documentation/fb/aty128fb.txt>.
1083 To compile this driver as a module, choose M here: the
1084 module will be called aty128fb.
1086 config FB_ATY128_BACKLIGHT
1087 bool "Support for backlight control"
1088 depends on FB_ATY128 && PMAC_BACKLIGHT
1092 Say Y here if you want to control the backlight of your display.
1095 tristate "ATI Mach64 display support" if PCI || ATARI
1096 depends on FB && !SPARC32
1097 select FB_CFB_FILLRECT
1098 select FB_CFB_COPYAREA
1099 select FB_CFB_IMAGEBLIT
1100 select FB_MACMODES if PPC
1102 This driver supports graphics boards with the ATI Mach64 chips.
1103 Say Y if you have such a graphics board.
1105 To compile this driver as a module, choose M here: the
1106 module will be called atyfb.
1109 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1110 depends on PCI && FB_ATY
1111 default y if SPARC64 && FB_PCI
1113 Say Y here to support use of ATI's 64-bit Rage boards (or other
1114 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1115 framebuffer device. The ATI product support page for these boards
1116 is at <http://support.ati.com/products/pc/mach64/>.
1118 config FB_ATY_GENERIC_LCD
1119 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1120 depends on FB_ATY_CT
1122 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1123 Rage XC, or Rage XL chipset.
1126 bool "Mach64 GX support" if PCI
1130 Say Y here to support use of the ATI Mach64 Graphics Expression
1131 board (or other boards based on the Mach64 GX chipset) as a
1132 framebuffer device. The ATI product support page for these boards
1134 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1136 config FB_ATY_BACKLIGHT
1137 bool "Support for backlight control"
1138 depends on FB_ATY && PMAC_BACKLIGHT
1142 Say Y here if you want to control the backlight of your display.
1145 bool "S3 Trio display support"
1146 depends on (FB = y) && PPC && BROKEN
1148 If you have a S3 Trio say Y. Say N for S3 Virge.
1151 tristate "S3 Savage support"
1152 depends on FB && PCI && EXPERIMENTAL
1153 select I2C_ALGOBIT if FB_SAVAGE_I2C
1154 select I2C if FB_SAVAGE_I2C
1155 select FB_DDC if FB_SAVAGE_I2C
1156 select FB_MODE_HELPERS
1157 select FB_CFB_FILLRECT
1158 select FB_CFB_COPYAREA
1159 select FB_CFB_IMAGEBLIT
1161 This driver supports notebooks and computers with S3 Savage PCI/AGP
1164 Say Y if you have such a graphics card.
1166 To compile this driver as a module, choose M here; the module
1167 will be called savagefb.
1169 config FB_SAVAGE_I2C
1170 bool "Enable DDC2 Support"
1171 depends on FB_SAVAGE
1173 This enables I2C support for S3 Savage Chipsets. This is used
1174 only for getting EDID information from the attached display
1175 allowing for robust video mode handling and switching.
1177 Because fbdev-2.6 requires that drivers must be able to
1178 independently validate video mode parameters, you should say Y
1181 config FB_SAVAGE_ACCEL
1182 bool "Enable Console Acceleration"
1183 depends on FB_SAVAGE
1186 This option will compile in console acceleration support. If
1187 the resulting framebuffer console has bothersome glitches, then
1191 tristate "SiS/XGI display support"
1192 depends on FB && PCI
1193 select FB_CFB_FILLRECT
1194 select FB_CFB_COPYAREA
1195 select FB_CFB_IMAGEBLIT
1197 This is the frame buffer device driver for the SiS 300, 315, 330
1198 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1199 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1201 To compile this driver as a module, choose M here; the module
1202 will be called sisfb.
1205 bool "SiS 300 series support"
1208 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1211 bool "SiS 315/330/340 series and XGI support"
1214 Say Y here to support use of the SiS 315, 330 and 340 series
1215 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1216 as XGI V3XT, V5, V8 and Z7.
1219 tristate "NeoMagic display support"
1220 depends on FB && PCI
1221 select FB_MODE_HELPERS
1222 select FB_CFB_FILLRECT
1223 select FB_CFB_COPYAREA
1224 select FB_CFB_IMAGEBLIT
1226 This driver supports notebooks with NeoMagic PCI chips.
1227 Say Y if you have such a graphics card.
1229 To compile this driver as a module, choose M here: the
1230 module will be called neofb.
1233 tristate "IMG Kyro support"
1234 depends on FB && PCI
1235 select FB_CFB_FILLRECT
1236 select FB_CFB_COPYAREA
1237 select FB_CFB_IMAGEBLIT
1239 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1242 To compile this driver as a module, choose M here: the
1243 module will be called kyrofb.
1246 tristate "3Dfx Banshee/Voodoo3 display support"
1247 depends on FB && PCI
1248 select FB_CFB_IMAGEBLIT
1249 select FB_CFB_FILLRECT
1250 select FB_CFB_COPYAREA
1252 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1253 chips. Say Y if you have such a graphics board.
1255 To compile this driver as a module, choose M here: the
1256 module will be called tdfxfb.
1258 config FB_3DFX_ACCEL
1259 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1260 depends on FB_3DFX && EXPERIMENTAL
1262 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1263 with acceleration functions.
1267 tristate "3Dfx Voodoo Graphics (sst1) support"
1268 depends on FB && PCI
1269 select FB_CFB_FILLRECT
1270 select FB_CFB_COPYAREA
1271 select FB_CFB_IMAGEBLIT
1273 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1274 Voodoo2 (cvg) based graphics card.
1276 To compile this driver as a module, choose M here: the
1277 module will be called sstfb.
1279 WARNING: Do not use any application that uses the 3D engine
1280 (namely glide) while using this driver.
1281 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1282 options and other important info support.
1285 tristate "Cyberblade/i1 support"
1286 depends on FB && PCI && X86_32 && !64BIT
1287 select FB_CFB_IMAGEBLIT
1290 This driver is supposed to support the Trident Cyberblade/i1
1291 graphics core integrated in the VIA VT8601A North Bridge,
1292 also known as VIA Apollo PLE133.
1295 - Developed, tested and working on EPIA 5000 and EPIA 800.
1296 - Does work reliable on all systems with CRT/LCD connected to
1298 - Should work on systems that do use the internal LCD port, but
1299 this is absolutely not tested.
1301 Character imageblit, copyarea and rectangle fill are hw accelerated,
1302 ypan scrolling is used by default.
1304 Please do read <file:Documentation/fb/cyblafb/*>.
1306 To compile this driver as a module, choose M here: the
1307 module will be called cyblafb.
1310 tristate "Trident support"
1311 depends on FB && PCI
1312 select FB_CFB_FILLRECT
1313 select FB_CFB_COPYAREA
1314 select FB_CFB_IMAGEBLIT
1316 This driver is supposed to support graphics boards with the
1317 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1318 but also on some motherboards. For more information, read
1319 <file:Documentation/fb/tridentfb.txt>
1321 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1324 Say Y if you have such a graphics board.
1327 To compile this driver as a module, choose M here: the
1328 module will be called tridentfb.
1330 config FB_TRIDENT_ACCEL
1331 bool "Trident Acceleration functions (EXPERIMENTAL)"
1332 depends on FB_TRIDENT && EXPERIMENTAL
1334 This will compile the Trident frame buffer device with
1335 acceleration functions.
1338 tristate "Permedia3 support"
1339 depends on FB && PCI && BROKEN
1341 This is the frame buffer device driver for the 3DLabs Permedia3
1342 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1343 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1344 and maybe other boards.
1347 bool "Au1100 LCD Driver"
1348 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1351 bool "Au1200 LCD Driver"
1352 depends on FB && MIPS && SOC_AU1200
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1357 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1358 various panels and CRTs by passing in kernel cmd line option
1359 au1200fb:panel=<name>.
1361 source "drivers/video/geode/Kconfig"
1364 bool "Creator/Creator3D/Elite3D support"
1365 depends on FB_SBUS && SPARC64
1366 select FB_CFB_COPYAREA
1367 select FB_CFB_IMAGEBLIT
1369 This is the frame buffer device driver for the Creator, Creator3D,
1370 and Elite3D graphics boards.
1373 bool "TCX (SS4/SS5 only) support"
1375 select FB_CFB_FILLRECT
1376 select FB_CFB_COPYAREA
1377 select FB_CFB_IMAGEBLIT
1379 This is the frame buffer device driver for the TCX 24/8bit frame
1383 bool "CGfourteen (SX) support"
1385 select FB_CFB_FILLRECT
1386 select FB_CFB_COPYAREA
1387 select FB_CFB_IMAGEBLIT
1389 This is the frame buffer device driver for the CGfourteen frame
1390 buffer on Desktop SPARCsystems with the SX graphics option.
1393 bool "P9100 (Sparcbook 3 only) support"
1395 select FB_CFB_FILLRECT
1396 select FB_CFB_COPYAREA
1397 select FB_CFB_IMAGEBLIT
1399 This is the frame buffer device driver for the P9100 card
1400 supported on Sparcbook 3 machines.
1403 bool "Leo (ZX) support"
1405 select FB_CFB_FILLRECT
1406 select FB_CFB_COPYAREA
1407 select FB_CFB_IMAGEBLIT
1409 This is the frame buffer device driver for the SBUS-based Sun ZX
1410 (leo) frame buffer cards.
1413 bool "PCI framebuffers"
1414 depends on (FB = y) && PCI && SPARC
1417 bool "IGA 168x display support"
1418 depends on SPARC32 && FB_PCI
1419 select FB_CFB_FILLRECT
1420 select FB_CFB_COPYAREA
1421 select FB_CFB_IMAGEBLIT
1423 This is the framebuffer device for the INTERGRAPHICS 1680 and
1424 successor frame buffer cards.
1427 tristate "HD64461 Frame Buffer support"
1428 depends on FB && HD64461
1429 select FB_CFB_FILLRECT
1430 select FB_CFB_COPYAREA
1431 select FB_CFB_IMAGEBLIT
1433 This is the frame buffer device driver for the Hitachi HD64461 LCD
1437 bool "PMAG-AA TURBOchannel framebuffer support"
1438 depends on (FB = y) && TC
1439 select FB_CFB_FILLRECT
1440 select FB_CFB_COPYAREA
1441 select FB_CFB_IMAGEBLIT
1443 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1444 used mainly in the MIPS-based DECstation series.
1447 bool "PMAG-BA TURBOchannel framebuffer support"
1448 depends on (FB = y) && TC
1449 select FB_CFB_FILLRECT
1450 select FB_CFB_COPYAREA
1451 select FB_CFB_IMAGEBLIT
1453 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1454 used mainly in the MIPS-based DECstation series.
1457 bool "PMAGB-B TURBOchannel framebuffer support"
1458 depends on (FB = y) && TC
1459 select FB_CFB_FILLRECT
1460 select FB_CFB_COPYAREA
1461 select FB_CFB_IMAGEBLIT
1463 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1464 in the MIPS-based DECstation series. The card is currently only
1465 supported in 1280x1024x8 mode.
1468 bool "Maxine (Personal DECstation) onboard framebuffer support"
1469 depends on (FB = y) && MACH_DECSTATION
1470 select FB_CFB_FILLRECT
1471 select FB_CFB_COPYAREA
1472 select FB_CFB_IMAGEBLIT
1474 Support for the onboard framebuffer (1024x768x8) in the Personal
1475 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1479 bool "TMPTX3912/PR31700 frame buffer support"
1480 depends on (FB = y) && NINO
1481 select FB_CFB_FILLRECT
1482 select FB_CFB_COPYAREA
1483 select FB_CFB_IMAGEBLIT
1485 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1486 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1488 Say Y here to enable kernel support for the on-board framebuffer.
1491 bool "G364 frame buffer support"
1492 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1493 select FB_CFB_FILLRECT
1494 select FB_CFB_COPYAREA
1495 select FB_CFB_IMAGEBLIT
1497 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1498 Olivetti M700-10 systems.
1501 bool "Motorola 68328 native frame buffer support"
1502 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1503 select FB_CFB_FILLRECT
1504 select FB_CFB_COPYAREA
1505 select FB_CFB_IMAGEBLIT
1507 Say Y here if you want to support the built-in frame buffer of
1508 the Motorola 68328 CPU family.
1511 tristate "PXA LCD framebuffer support"
1512 depends on FB && ARCH_PXA
1513 select FB_CFB_FILLRECT
1514 select FB_CFB_COPYAREA
1515 select FB_CFB_IMAGEBLIT
1517 Frame buffer driver for the built-in LCD controller in the Intel
1520 This driver is also available as a module ( = code which can be
1521 inserted and removed from the running kernel whenever you want). The
1522 module will be called pxafb. If you want to compile it as a module,
1523 say M here and read <file:Documentation/modules.txt>.
1527 config FB_PXA_PARAMETERS
1528 bool "PXA LCD command line parameters"
1532 Enable the use of kernel command line or module parameters
1533 to configure the physical properties of the LCD panel when
1534 using the PXA LCD driver.
1536 This option allows you to override the panel parameters
1537 supplied by the platform in order to support multiple
1538 different models of flatpanel. If you will only be using a
1539 single model of flatpanel then you can safely leave this
1542 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1545 tristate "2700G LCD framebuffer support"
1546 depends on FB && ARCH_PXA
1547 select FB_CFB_FILLRECT
1548 select FB_CFB_COPYAREA
1549 select FB_CFB_IMAGEBLIT
1551 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1555 bool "Enable debugging info via debugfs"
1556 depends on FB_MBX && DEBUG_FS
1559 Enable this if you want debugging information using the debug
1560 filesystem (debugfs)
1565 tristate "W100 frame buffer support"
1566 depends on FB && PXA_SHARPSL
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1571 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1573 This driver is also available as a module ( = code which can be
1574 inserted and removed from the running kernel whenever you want). The
1575 module will be called w100fb. If you want to compile it as a module,
1576 say M here and read <file:Documentation/modules.txt>.
1581 tristate "S3C2410 LCD framebuffer support"
1582 depends on FB && ARCH_S3C2410
1583 select FB_CFB_FILLRECT
1584 select FB_CFB_COPYAREA
1585 select FB_CFB_IMAGEBLIT
1587 Frame buffer driver for the built-in LCD controller in the Samsung
1590 This driver is also available as a module ( = code which can be
1591 inserted and removed from the running kernel whenever you want). The
1592 module will be called s3c2410fb. If you want to compile it as a module,
1593 say M here and read <file:Documentation/modules.txt>.
1596 config FB_S3C2410_DEBUG
1597 bool "S3C2410 lcd debug messages"
1598 depends on FB_S3C2410
1600 Turn on debugging messages. Note that you can set/unset at run time
1603 config FB_PNX4008_DUM
1604 tristate "Display Update Module support on Philips PNX4008 board"
1605 depends on FB && ARCH_PNX4008
1607 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1609 config FB_PNX4008_DUM_RGB
1610 tristate "RGB Framebuffer support on Philips PNX4008 board"
1611 depends on FB_PNX4008_DUM
1612 select FB_CFB_FILLRECT
1613 select FB_CFB_COPYAREA
1614 select FB_CFB_IMAGEBLIT
1616 Say Y here to enable support for PNX4008 RGB Framebuffer
1618 config FB_IBM_GXT4500
1619 tristate "Framebuffer support for IBM GXT4500P adaptor"
1621 select FB_CFB_FILLRECT
1622 select FB_CFB_COPYAREA
1623 select FB_CFB_IMAGEBLIT
1625 Say Y here to enable support for the IBM GXT4500P display
1626 adaptor, found on some IBM System P (pSeries) machines.
1629 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1631 select FB_CFB_FILLRECT
1632 select FB_CFB_COPYAREA
1633 select FB_CFB_IMAGEBLIT
1635 This is a `virtual' frame buffer device. It operates on a chunk of
1636 unswappable kernel memory instead of on the memory of a graphics
1637 board. This means you cannot see any output sent to this frame
1638 buffer device, while it does consume precious memory. The main use
1639 of this frame buffer device is testing and debugging the frame
1640 buffer subsystem. Do NOT enable it for normal systems! To protect
1641 the innocent, it has to be enabled explicitly at boot time using the
1642 kernel option `video=vfb:'.
1644 To compile this driver as a module, choose M here: the
1645 module will be called vfb. In order to load it, you must use
1646 the vfb_enable=1 option.
1650 source "drivers/video/console/Kconfig"
1653 if FB || SGI_NEWPORT_CONSOLE
1654 source "drivers/video/logo/Kconfig"
1658 source "drivers/video/backlight/Kconfig"