5 menu "Graphics support"
8 tristate "Support for frame buffer devices"
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
41 config FB_CFB_FILLRECT
46 Include the cfb_fillrect function for generic software rectangle
47 filling. This is used by drivers that don't provide their own
48 (accelerated) version.
50 config FB_CFB_COPYAREA
55 Include the cfb_copyarea function for generic software area copying.
56 This is used by drivers that don't provide their own (accelerated)
59 config FB_CFB_IMAGEBLIT
64 Include the cfb_imageblit function for generic software image
65 blitting. This is used by drivers that don't provide their own
66 (accelerated) version.
73 config FB_FIRMWARE_EDID
74 bool "Enable firmware EDID"
78 This enables access to the EDID transferred from the firmware.
79 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
80 transfers do not work for your driver and if you are using
81 nvidiafb, i810fb or savagefb.
83 In general, choosing Y for this option is safe. If you
84 experience extremely long delays while booting before you get
85 something on your display, try setting this to N. Matrox cards in
86 combination with certain motherboards and monitors are known to
87 suffer from this problem.
94 config FB_MODE_HELPERS
95 bool "Enable Video Mode Handling Helpers"
99 This enables functions for handling video modes using the
100 Generalized Timing Formula and the EDID parser. A few drivers rely
101 on this feature such as the radeonfb, rivafb, and the i810fb. If
102 your driver does not take advantage of this feature, choosing Y will
103 just increase the kernel size by about 5K.
105 config FB_TILEBLITTING
106 bool "Enable Tile Blitting Support"
110 This enables tile blitting. Tile blitting is a drawing technique
111 where the screen is divided into rectangular sections (tiles), whereas
112 the standard blitting divides the screen into pixels. Because the
113 default drawing element is a tile, drawing functions will be passed
114 parameters in terms of number of tiles instead of number of pixels.
115 For example, to draw a single character, instead of using bitmaps,
116 an index to an array of bitmaps will be used. To clear or move a
117 rectangular section of a screen, the rectangle will be described in
118 terms of number of tiles in the x- and y-axis.
120 This is particularly important to one driver, matroxfb. If
124 tristate "Cirrus Logic support"
125 depends on FB && (ZORRO || PCI)
126 select FB_CFB_FILLRECT
127 select FB_CFB_COPYAREA
128 select FB_CFB_IMAGEBLIT
130 This enables support for Cirrus Logic GD542x/543x based boards on
131 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
133 If you have a PCI-based system, this enables support for these
134 chips: GD-543x, GD-544x, GD-5480.
136 Please read the file <file:Documentation/fb/cirrusfb.txt>.
138 Say N unless you have such a graphics board or plan to get one
139 before you next recompile the kernel.
142 tristate "Permedia2 support"
143 depends on FB && ((AMIGA && BROKEN) || PCI)
144 select FB_CFB_FILLRECT
145 select FB_CFB_COPYAREA
146 select FB_CFB_IMAGEBLIT
148 This is the frame buffer device driver for the Permedia2 AGP frame
149 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
151 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
153 config FB_PM2_FIFO_DISCONNECT
154 bool "enable FIFO disconnect feature"
155 depends on FB_PM2 && PCI
157 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
160 tristate "ARM PrimeCell PL110 support"
161 depends on FB && ARM && ARM_AMBA
162 select FB_CFB_FILLRECT
163 select FB_CFB_COPYAREA
164 select FB_CFB_IMAGEBLIT
166 This framebuffer device driver is for the ARM PrimeCell PL110
167 Colour LCD controller. ARM PrimeCells provide the building
168 blocks for System on a Chip devices.
170 If you want to compile this as a module (=code which can be
171 inserted into and removed from the running kernel), say M
172 here and read <file:Documentation/modules.txt>. The module
173 will be called amba-clcd.
177 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
179 default FB_ARMCLCD_SHARP_LQ035Q7DB02
181 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
182 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
184 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
185 color QVGA, HRTFT panel. The LogicPD device includes an
186 an integrated HRTFT controller IC.
187 The native resolution is 240x320.
189 config FB_ARMCLCD_SHARP_LQ057Q3DC02
190 bool "LogicPD LCD 5.7\" QVGA"
192 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
193 color QVGA, TFT panel. The LogicPD device includes an
194 The native resolution is 320x240.
196 config FB_ARMCLCD_SHARP_LQ64D343
197 bool "LogicPD LCD 6.4\" VGA"
199 This is an implementation of the Sharp LQ64D343, a 6.4"
200 color VGA, TFT panel. The LogicPD device includes an
201 The native resolution is 640x480.
203 config FB_ARMCLCD_SHARP_LQ10D368
204 bool "LogicPD LCD 10.4\" VGA"
206 This is an implementation of the Sharp LQ10D368, a 10.4"
207 color VGA, TFT panel. The LogicPD device includes an
208 The native resolution is 640x480.
211 config FB_ARMCLCD_SHARP_LQ121S1DG41
212 bool "LogicPD LCD 12.1\" SVGA"
214 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
215 color SVGA, TFT panel. The LogicPD device includes an
216 The native resolution is 800x600.
218 This panel requires a clock rate may be an integer fraction
219 of the base LCDCLK frequency. The driver will select the
220 highest frequency available that is lower than the maximum
221 allowed. The panel may flicker if the clock rate is
222 slower than the recommended minimum.
224 config FB_ARMCLCD_AUO_A070VW01_WIDE
225 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
227 This is an implementation of the AU Optronics, a 7.0"
228 WIDE Color. The native resolution is 234x480.
230 config FB_ARMCLCD_HITACHI
231 bool "Hitachi Wide Screen 800x480"
233 This is an implementation of the Hitachi 800x480.
239 bool "Acorn VIDC support"
240 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
241 select FB_CFB_FILLRECT
242 select FB_CFB_COPYAREA
243 select FB_CFB_IMAGEBLIT
245 This is the frame buffer device driver for the Acorn VIDC graphics
246 hardware found in Acorn RISC PCs and other ARM-based machines. If
250 bool "CLPS711X LCD support"
251 depends on (FB = y) && ARM && ARCH_CLPS711X
252 select FB_CFB_FILLRECT
253 select FB_CFB_COPYAREA
254 select FB_CFB_IMAGEBLIT
256 Say Y to enable the Framebuffer driver for the CLPS7111 and
260 bool "SA-1100 LCD support"
261 depends on (FB = y) && ARM && ARCH_SA1100
262 select FB_CFB_FILLRECT
263 select FB_CFB_COPYAREA
264 select FB_CFB_IMAGEBLIT
266 This is a framebuffer device for the SA-1100 LCD Controller.
267 See <http://www.linux-fbdev.org/> for information on framebuffer
270 If you plan to use the LCD display with your SA-1100 system, say
274 tristate "Motorola i.MX LCD support"
275 depends on FB && ARM && ARCH_IMX
276 select FB_CFB_FILLRECT
277 select FB_CFB_COPYAREA
278 select FB_CFB_IMAGEBLIT
281 tristate "CyberPro 2000/2010/5000 support"
282 depends on FB && PCI && (BROKEN || !SPARC64)
283 select FB_CFB_FILLRECT
284 select FB_CFB_COPYAREA
285 select FB_CFB_IMAGEBLIT
287 This enables support for the Integraphics CyberPro 20x0 and 5000
288 VGA chips used in the Rebel.com Netwinder and other machines.
289 Say Y if you have a NetWinder or a graphics card containing this
290 device, otherwise say N.
294 depends on (FB = y) && APOLLO
296 select FB_CFB_FILLRECT
297 select FB_CFB_IMAGEBLIT
301 depends on (FB = y) && Q40
303 select FB_CFB_FILLRECT
304 select FB_CFB_COPYAREA
305 select FB_CFB_IMAGEBLIT
308 tristate "Amiga native chipset support"
309 depends on FB && AMIGA
311 This is the frame buffer device driver for the builtin graphics
312 chipset found in Amigas.
314 To compile this driver as a module, choose M here: the
315 module will be called amifb.
318 bool "Amiga OCS chipset support"
321 This enables support for the original Agnus and Denise video chips,
322 found in the Amiga 1000 and most A500's and A2000's. If you intend
323 to run Linux on any of these systems, say Y; otherwise say N.
326 bool "Amiga ECS chipset support"
329 This enables support for the Enhanced Chip Set, found in later
330 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
331 you intend to run Linux on any of these systems, say Y; otherwise
335 bool "Amiga AGA chipset support"
338 This enables support for the Advanced Graphics Architecture (also
339 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
340 and CD32. If you intend to run Linux on any of these systems, say Y;
344 tristate "Amiga CyberVision 64 support"
345 depends on FB && ZORRO && BROKEN
346 select FB_CFB_FILLRECT
347 select FB_CFB_COPYAREA
348 select FB_CFB_IMAGEBLIT
350 This enables support for the Cybervision 64 graphics card from
351 Phase5. Please note that its use is not all that intuitive (i.e. if
352 you have any questions, be sure to ask!). Say N unless you have a
353 Cybervision 64 or plan to get one before you next recompile the
354 kernel. Please note that this driver DOES NOT support the
355 Cybervision 64/3D card, as they use incompatible video chips.
358 bool "Amiga CyberVision 64/3D support "
359 depends on (FB = y) && ZORRO && BROKEN
360 select FB_CFB_FILLRECT
361 select FB_CFB_COPYAREA
362 select FB_CFB_IMAGEBLIT
364 This enables support for the Cybervision 64/3D graphics card from
365 Phase5. Please note that its use is not all that intuitive (i.e. if
366 you have any questions, be sure to ask!). Say N unless you have a
367 Cybervision 64/3D or plan to get one before you next recompile the
368 kernel. Please note that this driver DOES NOT support the older
369 Cybervision 64 card, as they use incompatible video chips.
372 tristate "Amiga Retina Z3 support"
373 depends on (FB = y) && ZORRO && BROKEN
375 This enables support for the Retina Z3 graphics card. Say N unless
376 you have a Retina Z3 or plan to get one before you next recompile
380 bool "Amiga FrameMaster II/Rainbow II support"
381 depends on (FB = y) && ZORRO
382 select FB_CFB_FILLRECT
383 select FB_CFB_COPYAREA
384 select FB_CFB_IMAGEBLIT
386 This is the frame buffer device driver for the Amiga FrameMaster
387 card from BSC (exhibited 1992 but not shipped as a CBM product).
390 tristate "Arc Monochrome LCD board support"
392 select FB_CFB_FILLRECT
393 select FB_CFB_COPYAREA
394 select FB_CFB_IMAGEBLIT
396 This enables support for the Arc Monochrome LCD board. The board
397 is based on the KS-108 lcd controller and is typically a matrix
398 of 2*n chips. This driver was tested with a 128x64 panel. This
399 driver supports it for use with x86 SBCs through a 16 bit GPIO
400 interface (8 bit data, 8 bit control). If you anticpate using
401 this driver, say Y or M; otherwise say N. You must specify the
402 GPIO IO address to be used for setting control and data.
405 bool "Atari native chipset support"
406 depends on (FB = y) && ATARI && BROKEN
408 This is the frame buffer device driver for the builtin graphics
409 chipset found in Ataris.
412 bool "Open Firmware frame buffer device support"
413 depends on (FB = y) && (PPC64 || PPC_OF)
414 select FB_CFB_FILLRECT
415 select FB_CFB_COPYAREA
416 select FB_CFB_IMAGEBLIT
419 Say Y if you want support with Open Firmware for your graphics
423 bool "Apple \"control\" display support"
424 depends on (FB = y) && PPC_PMAC
425 select FB_CFB_FILLRECT
426 select FB_CFB_COPYAREA
427 select FB_CFB_IMAGEBLIT
430 This driver supports a frame buffer for the graphics adapter in the
431 Power Macintosh 7300 and others.
434 bool "Apple \"platinum\" display support"
435 depends on (FB = y) && PPC_PMAC
436 select FB_CFB_FILLRECT
437 select FB_CFB_COPYAREA
438 select FB_CFB_IMAGEBLIT
441 This driver supports a frame buffer for the "platinum" graphics
442 adapter in some Power Macintoshes.
445 bool "Apple \"valkyrie\" display support"
446 depends on (FB = y) && (MAC || PPC_PMAC)
447 select FB_CFB_FILLRECT
448 select FB_CFB_COPYAREA
449 select FB_CFB_IMAGEBLIT
452 This driver supports a frame buffer for the "valkyrie" graphics
453 adapter in some Power Macintoshes.
456 bool "Chips 65550 display support"
457 depends on (FB = y) && PPC
458 select FB_CFB_FILLRECT
459 select FB_CFB_COPYAREA
460 select FB_CFB_IMAGEBLIT
462 This is the frame buffer device driver for the Chips & Technologies
463 65550 graphics chip in PowerBooks.
466 bool "Asiliant (Chips) 69000 display support"
467 depends on (FB = y) && PCI
468 select FB_CFB_FILLRECT
469 select FB_CFB_COPYAREA
470 select FB_CFB_IMAGEBLIT
472 This is the frame buffer device driver for the Asiliant 69030 chipset
475 bool "IMS Twin Turbo display support"
476 depends on (FB = y) && PCI
477 select FB_CFB_IMAGEBLIT
478 select FB_MACMODES if PPC
480 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
481 many Macintosh and compatible computers.
484 tristate "VGA 16-color graphics support"
485 depends on FB && (X86 || PPC)
486 select FB_CFB_FILLRECT
487 select FB_CFB_COPYAREA
488 select FB_CFB_IMAGEBLIT
490 This is the frame buffer device driver for VGA 16 color graphic
491 cards. Say Y if you have such a card.
493 To compile this driver as a module, choose M here: the
494 module will be called vga16fb.
497 tristate "HP STI frame buffer device support"
498 depends on FB && PARISC
499 select FB_CFB_FILLRECT
500 select FB_CFB_COPYAREA
501 select FB_CFB_IMAGEBLIT
504 STI refers to the HP "Standard Text Interface" which is a set of
505 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
506 Enabling this option will implement the linux framebuffer device
507 using calls to the STI BIOS routines for initialisation.
509 If you enable this option, you will get a planar framebuffer device
510 /dev/fb which will work on the most common HP graphic cards of the
511 NGLE family, including the artist chips (in the 7xx and Bxxx series),
512 HCRX, HCRX24, CRX, CRX24 and VisEG series.
514 It is safe to enable this option, so you should probably say "Y".
517 bool "Generic Macintosh display support"
518 depends on (FB = y) && MAC
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
524 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
527 depends on (FB = y) && HP300
528 select FB_CFB_FILLRECT
529 select FB_CFB_IMAGEBLIT
533 tristate "TGA framebuffer support"
534 depends on FB && ALPHA
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
539 This is the frame buffer device driver for generic TGA graphic
540 cards. Say Y if you have one of those.
543 bool "VESA VGA graphics support"
544 depends on (FB = y) && X86
545 select FB_CFB_FILLRECT
546 select FB_CFB_COPYAREA
547 select FB_CFB_IMAGEBLIT
549 This is the frame buffer device driver for generic VESA 2.0
550 compliant graphic cards. The older VESA 1.2 cards are not supported.
551 You will get a boot time penguin logo at no additional cost. Please
552 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
560 tristate "Hercules mono graphics support"
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
566 Say Y here if you have a Hercules mono graphics card.
568 To compile this driver as a module, choose M here: the
569 module will be called hgafb.
571 As this card technology is 15 years old, most people will answer N
575 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
576 depends on FB_HGA && EXPERIMENTAL
578 This will compile the Hercules mono graphics with
579 acceleration functions.
584 depends on (FB = y) && X86
588 tristate "SGI Visual Workstation framebuffer support"
589 depends on FB && X86_VISWS
590 select FB_CFB_FILLRECT
591 select FB_CFB_COPYAREA
592 select FB_CFB_IMAGEBLIT
594 SGI Visual Workstation support for framebuffer graphics.
597 bool "SGI Graphics Backend frame buffer support"
598 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
599 select FB_CFB_FILLRECT
600 select FB_CFB_COPYAREA
601 select FB_CFB_IMAGEBLIT
603 This is the frame buffer device driver for SGI Graphics Backend.
604 This chip is used in SGI O2 and Visual Workstation 320/540.
607 int "Video memory size in MB"
611 This is the amount of memory reserved for the framebuffer,
612 which can be any value between 1MB and 8MB.
615 bool "Sun3 framebuffer support"
616 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
619 bool "SBUS and UPA framebuffers"
620 depends on (FB = y) && SPARC
622 Say Y if you want support for SBUS or UPA based frame buffer device.
626 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
627 select FB_CFB_FILLRECT
628 select FB_CFB_COPYAREA
629 select FB_CFB_IMAGEBLIT
631 This is the frame buffer device driver for the BWtwo frame buffer.
634 bool "CGthree support"
635 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
636 select FB_CFB_FILLRECT
637 select FB_CFB_COPYAREA
638 select FB_CFB_IMAGEBLIT
640 This is the frame buffer device driver for the CGthree frame buffer.
643 bool "CGsix (GX,TurboGX) support"
644 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
645 select FB_CFB_COPYAREA
646 select FB_CFB_IMAGEBLIT
648 This is the frame buffer device driver for the CGsix (GX, TurboGX)
652 tristate "NEC PowerVR 2 display support"
653 depends on FB && SH_DREAMCAST
654 select FB_CFB_FILLRECT
655 select FB_CFB_COPYAREA
656 select FB_CFB_IMAGEBLIT
658 Say Y here if you have a PowerVR 2 card in your box. If you plan to
659 run linux on your Dreamcast, you will have to say Y here.
660 This driver may or may not work on other PowerVR 2 cards, but is
661 totally untested. Use at your own risk. If unsure, say N.
663 To compile this driver as a module, choose M here: the
664 module will be called pvr2fb.
666 You can pass several parameters to the driver at boot time or at
667 module load time. The parameters look like "video=pvr2:XXX", where
668 the meaning of XXX can be found at the end of the main source file
669 (<file:drivers/video/pvr2fb.c>). Please see the file
670 <file:Documentation/fb/pvr2fb.txt>.
673 bool "Epson 1355 framebuffer support"
674 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
679 Build in support for the SED1355 Epson Research Embedded RAMDAC
680 LCD/CRT Controller (since redesignated as the S1D13505) as a
681 framebuffer. Product specs at
682 <http://www.erd.epson.com/vdc/html/products.htm>.
685 tristate "Epson S1D13XXX framebuffer support"
687 select FB_CFB_FILLRECT
688 select FB_CFB_COPYAREA
689 select FB_CFB_IMAGEBLIT
691 Support for S1D13XXX framebuffer device family (currently only
692 working with S1D13806). Product specs at
693 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
696 tristate "nVidia Framebuffer Support"
698 select I2C_ALGOBIT if FB_NVIDIA_I2C
699 select I2C if FB_NVIDIA_I2C
700 select FB_MODE_HELPERS
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
705 This driver supports graphics boards with the nVidia chips, TNT
706 and newer. For very old chipsets, such as the RIVA128, then use
708 Say Y if you have such a graphics board.
710 To compile this driver as a module, choose M here: the
711 module will be called nvidiafb.
714 bool "Enable DDC Support"
717 This enables I2C support for nVidia Chipsets. This is used
718 only for getting EDID information from the attached display
719 allowing for robust video mode handling and switching.
721 Because fbdev-2.6 requires that drivers must be able to
722 independently validate video mode parameters, you should say Y
725 config FB_NVIDIA_BACKLIGHT
726 bool "Support for backlight control"
727 depends on FB_NVIDIA && PPC_PMAC
729 select BACKLIGHT_LCD_SUPPORT
730 select BACKLIGHT_CLASS_DEVICE
733 Say Y here if you want to control the backlight of your display.
736 tristate "nVidia Riva support"
738 select I2C_ALGOBIT if FB_RIVA_I2C
739 select I2C if FB_RIVA_I2C
740 select FB_MODE_HELPERS
741 select FB_CFB_FILLRECT
742 select FB_CFB_COPYAREA
743 select FB_CFB_IMAGEBLIT
745 This driver supports graphics boards with the nVidia Riva/Geforce
747 Say Y if you have such a graphics board.
749 To compile this driver as a module, choose M here: the
750 module will be called rivafb.
753 bool "Enable DDC Support"
756 This enables I2C support for nVidia Chipsets. This is used
757 only for getting EDID information from the attached display
758 allowing for robust video mode handling and switching.
760 Because fbdev-2.6 requires that drivers must be able to
761 independently validate video mode parameters, you should say Y
765 bool "Lots of debug output from Riva(nVidia) driver"
769 Say Y here if you want the Riva driver to output all sorts
770 of debugging informations to provide to the maintainer when
771 something goes wrong.
773 config FB_RIVA_BACKLIGHT
774 bool "Support for backlight control"
775 depends on FB_RIVA && PPC_PMAC
777 select BACKLIGHT_LCD_SUPPORT
778 select BACKLIGHT_CLASS_DEVICE
781 Say Y here if you want to control the backlight of your display.
784 tristate "Intel 810/815 support (EXPERIMENTAL)"
785 depends on FB && EXPERIMENTAL && PCI && X86_32
788 select FB_MODE_HELPERS
789 select FB_CFB_FILLRECT
790 select FB_CFB_COPYAREA
791 select FB_CFB_IMAGEBLIT
793 This driver supports the on-board graphics built in to the Intel 810
794 and 815 chipsets. Say Y if you have and plan to use such a board.
796 To compile this driver as a module, choose M here: the
797 module will be called i810fb.
799 For more information, please read
800 <file:Documentation/fb/intel810.txt>
803 bool "use VESA Generalized Timing Formula"
806 If you say Y, then the VESA standard, Generalized Timing Formula
807 or GTF, will be used to calculate the required video timing values
808 per video mode. Since the GTF allows nondiscrete timings
809 (nondiscrete being a range of values as opposed to discrete being a
810 set of values), you'll be able to use any combination of horizontal
811 and vertical resolutions, and vertical refresh rates without having
812 to specify your own timing parameters. This is especially useful
813 to maximize the performance of an aging display, or if you just
814 have a display with nonstandard dimensions. A VESA compliant
815 monitor is recommended, but can still work with non-compliant ones.
816 If you need or want this, then select this option. The timings may
817 not be compliant with Intel's recommended values. Use at your own
820 If you say N, the driver will revert to discrete video timings
821 using a set recommended by Intel in their documentation.
826 bool "Enable DDC Support"
827 depends on FB_I810 && FB_I810_GTF
833 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
834 depends on FB && EXPERIMENTAL && PCI && X86
837 select FB_MODE_HELPERS
838 select FB_CFB_FILLRECT
839 select FB_CFB_COPYAREA
840 select FB_CFB_IMAGEBLIT
842 This driver supports the on-board graphics built in to the Intel
843 830M/845G/852GM/855GM/865G chipsets.
844 Say Y if you have and plan to use such a board.
846 To compile this driver as a module, choose M here: the
847 module will be called intelfb.
849 config FB_INTEL_DEBUG
850 bool "Intel driver Debug Messages"
853 Say Y here if you want the Intel driver to output all sorts
854 of debugging informations to provide to the maintainer when
855 something goes wrong.
858 tristate "Matrox acceleration"
860 select FB_CFB_FILLRECT
861 select FB_CFB_COPYAREA
862 select FB_CFB_IMAGEBLIT
863 select FB_TILEBLITTING
864 select FB_MACMODES if PPC_PMAC
866 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
867 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
868 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
869 Matrox G400, G450 or G550 card in your box.
871 To compile this driver as a module, choose M here: the
872 module will be called matroxfb.
874 You can pass several parameters to the driver at boot time or at
875 module load time. The parameters look like "video=matrox:XXX", and
876 are described in <file:Documentation/fb/matroxfb.txt>.
878 config FB_MATROX_MILLENIUM
879 bool "Millennium I/II support"
882 Say Y here if you have a Matrox Millennium or Matrox Millennium II
883 video card. If you select "Advanced lowlevel driver options" below,
884 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
885 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
886 also use font widths different from 8.
888 config FB_MATROX_MYSTIQUE
889 bool "Mystique support"
892 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
893 video card. If you select "Advanced lowlevel driver options" below,
894 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
895 packed pixel and 32 bpp packed pixel. You can also use font widths
899 bool "G100/G200/G400/G450/G550 support"
902 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
903 video card. If you select "Advanced lowlevel driver options", you
904 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
905 pixel and 32 bpp packed pixel. You can also use font widths
908 If you need support for G400 secondary head, you must first say Y to
909 "I2C support" in the character devices section, and then to
910 "Matrox I2C support" and "G400 second head support" here in the
911 framebuffer section. G450/G550 secondary head and digital output
912 are supported without additional modules.
914 The driver starts in monitor mode. You must use the matroxset tool
915 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
916 swap primary and secondary head outputs, or to change output mode.
917 Secondary head driver always start in 640x480 resolution and you
918 must use fbset to change it.
920 Do not forget that second head supports only 16 and 32 bpp
921 packed pixels, so it is a good idea to compile them into the kernel
922 too. You can use only some font widths, as the driver uses generic
923 painting procedures (the secondary head does not use acceleration
926 G450/G550 hardware can display TV picture only from secondary CRTC,
927 and it performs no scaling, so picture must have 525 or 625 lines.
930 tristate "Matrox I2C support"
931 depends on FB_MATROX && I2C
934 This drivers creates I2C buses which are needed for accessing the
935 DDC (I2C) bus present on all Matroxes, an I2C bus which
936 interconnects Matrox optional devices, like MGA-TVO on G200 and
937 G400, and the secondary head DDC bus, present on G400 only.
939 You can say Y or M here if you want to experiment with monitor
940 detection code. You must say Y or M here if you want to use either
941 second head of G400 or MGA-TVO on G200 or G400.
943 If you compile it as module, it will create a module named
946 config FB_MATROX_MAVEN
947 tristate "G400 second head support"
948 depends on FB_MATROX_G && FB_MATROX_I2C
950 WARNING !!! This support does not work with G450 !!!
952 Say Y or M here if you want to use a secondary head (meaning two
953 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
954 head is not compatible with accelerated XFree 3.3.x SVGA servers -
955 secondary head output is blanked while you are in X. With XFree
956 3.9.17 preview you can use both heads if you use SVGA over fbdev or
957 the fbdev driver on first head and the fbdev driver on second head.
959 If you compile it as module, two modules are created,
960 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
961 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
962 also load i2c-matroxfb to get it to run.
964 The driver starts in monitor mode and you must use the matroxset
966 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
967 PAL or NTSC or to swap primary and secondary head outputs.
968 Secondary head driver also always start in 640x480 resolution, you
969 must use fbset to change it.
971 Also do not forget that second head supports only 16 and 32 bpp
972 packed pixels, so it is a good idea to compile them into the kernel
973 too. You can use only some font widths, as the driver uses generic
974 painting procedures (the secondary head does not use acceleration
977 config FB_MATROX_MULTIHEAD
978 bool "Multihead support"
981 Say Y here if you have more than one (supported) Matrox device in
982 your computer and you want to use all of them for different monitors
983 ("multihead"). If you have only one device, you should say N because
984 the driver compiled with Y is larger and a bit slower, especially on
987 If you said M to "Matrox unified accelerated driver" and N here, you
988 will still be able to use several Matrox devices simultaneously:
989 insert several instances of the module matroxfb into the kernel
990 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
991 for the different Matrox devices. This method is slightly faster but
992 uses 40 KB of kernel memory per Matrox card.
994 There is no need for enabling 'Matrox multihead support' if you have
995 only one Matrox card in the box.
998 tristate "ATI Radeon display support"
1000 select I2C_ALGOBIT if FB_RADEON_I2C
1001 select I2C if FB_RADEON_I2C
1002 select FB_MODE_HELPERS
1003 select FB_CFB_FILLRECT
1004 select FB_CFB_COPYAREA
1005 select FB_CFB_IMAGEBLIT
1006 select FB_MACMODES if PPC_OF
1008 Choose this option if you want to use an ATI Radeon graphics card as
1009 a framebuffer device. There are both PCI and AGP versions. You
1010 don't need to choose this to run the Radeon in plain VGA mode.
1012 If you say Y here and want DDC/I2C support you must first say Y to
1013 "I2C support" and "I2C bit-banging support" in the character devices
1016 If you say M here then "I2C support" and "I2C bit-banging support"
1017 can be build either as modules or built-in.
1019 There is a product page at
1020 http://apps.ati.com/ATIcompare/
1022 config FB_RADEON_I2C
1023 bool "DDC/I2C for ATI Radeon support"
1024 depends on FB_RADEON
1027 Say Y here if you want DDC/I2C support for your Radeon board.
1029 config FB_RADEON_BACKLIGHT
1030 bool "Support for backlight control"
1031 depends on FB_RADEON && PPC_PMAC
1033 select BACKLIGHT_LCD_SUPPORT
1034 select BACKLIGHT_CLASS_DEVICE
1037 Say Y here if you want to control the backlight of your display.
1039 config FB_RADEON_DEBUG
1040 bool "Lots of debug output from Radeon driver"
1041 depends on FB_RADEON
1044 Say Y here if you want the Radeon driver to output all sorts
1045 of debugging informations to provide to the maintainer when
1046 something goes wrong.
1049 tristate "ATI Rage128 display support"
1050 depends on FB && PCI
1051 select FB_CFB_FILLRECT
1052 select FB_CFB_COPYAREA
1053 select FB_CFB_IMAGEBLIT
1054 select FB_MACMODES if PPC_PMAC
1056 This driver supports graphics boards with the ATI Rage128 chips.
1057 Say Y if you have such a graphics board and read
1058 <file:Documentation/fb/aty128fb.txt>.
1060 To compile this driver as a module, choose M here: the
1061 module will be called aty128fb.
1063 config FB_ATY128_BACKLIGHT
1064 bool "Support for backlight control"
1065 depends on FB_ATY128 && PPC_PMAC
1067 select BACKLIGHT_LCD_SUPPORT
1068 select BACKLIGHT_CLASS_DEVICE
1071 Say Y here if you want to control the backlight of your display.
1074 tristate "ATI Mach64 display support" if PCI || ATARI
1075 depends on FB && !SPARC32
1076 select FB_CFB_FILLRECT
1077 select FB_CFB_COPYAREA
1078 select FB_CFB_IMAGEBLIT
1079 select FB_MACMODES if PPC
1081 This driver supports graphics boards with the ATI Mach64 chips.
1082 Say Y if you have such a graphics board.
1084 To compile this driver as a module, choose M here: the
1085 module will be called atyfb.
1088 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1089 depends on PCI && FB_ATY
1090 default y if SPARC64 && FB_PCI
1092 Say Y here to support use of ATI's 64-bit Rage boards (or other
1093 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1094 framebuffer device. The ATI product support page for these boards
1095 is at <http://support.ati.com/products/pc/mach64/>.
1097 config FB_ATY_GENERIC_LCD
1098 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1099 depends on FB_ATY_CT
1101 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1102 Rage XC, or Rage XL chipset.
1105 bool "Mach64 GX support" if PCI
1109 Say Y here to support use of the ATI Mach64 Graphics Expression
1110 board (or other boards based on the Mach64 GX chipset) as a
1111 framebuffer device. The ATI product support page for these boards
1113 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1115 config FB_ATY_BACKLIGHT
1116 bool "Support for backlight control"
1117 depends on FB_ATY && PPC_PMAC
1119 select BACKLIGHT_LCD_SUPPORT
1120 select BACKLIGHT_CLASS_DEVICE
1123 Say Y here if you want to control the backlight of your display.
1126 bool "S3 Trio display support"
1127 depends on (FB = y) && PPC && BROKEN
1129 If you have a S3 Trio say Y. Say N for S3 Virge.
1132 tristate "S3 Savage support"
1133 depends on FB && PCI && EXPERIMENTAL
1134 select I2C_ALGOBIT if FB_SAVAGE_I2C
1135 select I2C if FB_SAVAGE_I2C
1136 select FB_MODE_HELPERS
1137 select FB_CFB_FILLRECT
1138 select FB_CFB_COPYAREA
1139 select FB_CFB_IMAGEBLIT
1141 This driver supports notebooks and computers with S3 Savage PCI/AGP
1144 Say Y if you have such a graphics card.
1146 To compile this driver as a module, choose M here; the module
1147 will be called savagefb.
1149 config FB_SAVAGE_I2C
1150 bool "Enable DDC2 Support"
1151 depends on FB_SAVAGE
1153 This enables I2C support for S3 Savage Chipsets. This is used
1154 only for getting EDID information from the attached display
1155 allowing for robust video mode handling and switching.
1157 Because fbdev-2.6 requires that drivers must be able to
1158 independently validate video mode parameters, you should say Y
1161 config FB_SAVAGE_ACCEL
1162 bool "Enable Console Acceleration"
1163 depends on FB_SAVAGE
1166 This option will compile in console acceleration support. If
1167 the resulting framebuffer console has bothersome glitches, then
1171 tristate "SiS/XGI display support"
1172 depends on FB && PCI
1173 select FB_CFB_FILLRECT
1174 select FB_CFB_COPYAREA
1175 select FB_CFB_IMAGEBLIT
1177 This is the frame buffer device driver for the SiS 300, 315, 330
1178 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1179 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1181 To compile this driver as a module, choose M here; the module
1182 will be called sisfb.
1185 bool "SiS 300 series support"
1188 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1191 bool "SiS 315/330/340 series and XGI support"
1194 Say Y here to support use of the SiS 315, 330 and 340 series
1195 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1196 as XGI V3XT, V5, V8 and Z7.
1199 tristate "NeoMagic display support"
1200 depends on FB && PCI
1201 select FB_MODE_HELPERS
1202 select FB_CFB_FILLRECT
1203 select FB_CFB_COPYAREA
1204 select FB_CFB_IMAGEBLIT
1206 This driver supports notebooks with NeoMagic PCI chips.
1207 Say Y if you have such a graphics card.
1209 To compile this driver as a module, choose M here: the
1210 module will be called neofb.
1213 tristate "IMG Kyro support"
1214 depends on FB && PCI
1215 select FB_CFB_FILLRECT
1216 select FB_CFB_COPYAREA
1217 select FB_CFB_IMAGEBLIT
1219 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1222 To compile this driver as a module, choose M here: the
1223 module will be called kyrofb.
1226 tristate "3Dfx Banshee/Voodoo3 display support"
1227 depends on FB && PCI
1228 select FB_CFB_IMAGEBLIT
1229 select FB_CFB_FILLRECT
1230 select FB_CFB_COPYAREA
1232 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1233 chips. Say Y if you have such a graphics board.
1235 To compile this driver as a module, choose M here: the
1236 module will be called tdfxfb.
1238 config FB_3DFX_ACCEL
1239 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1240 depends on FB_3DFX && EXPERIMENTAL
1242 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1243 with acceleration functions.
1247 tristate "3Dfx Voodoo Graphics (sst1) support"
1248 depends on FB && PCI
1249 select FB_CFB_FILLRECT
1250 select FB_CFB_COPYAREA
1251 select FB_CFB_IMAGEBLIT
1253 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1254 Voodoo2 (cvg) based graphics card.
1256 To compile this driver as a module, choose M here: the
1257 module will be called sstfb.
1259 WARNING: Do not use any application that uses the 3D engine
1260 (namely glide) while using this driver.
1261 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1262 options and other important info support.
1265 tristate "Cyberblade/i1 support"
1266 depends on FB && PCI && X86_32 && !64BIT
1267 select FB_CFB_IMAGEBLIT
1270 This driver is supposed to support the Trident Cyberblade/i1
1271 graphics core integrated in the VIA VT8601A North Bridge,
1272 also known as VIA Apollo PLE133.
1275 - Developed, tested and working on EPIA 5000 and EPIA 800.
1276 - Does work reliable on all systems with CRT/LCD connected to
1278 - Should work on systems that do use the internal LCD port, but
1279 this is absolutely not tested.
1281 Character imageblit, copyarea and rectangle fill are hw accelerated,
1282 ypan scrolling is used by default.
1284 Please do read <file:Documentation/fb/cyblafb/*>.
1286 To compile this driver as a module, choose M here: the
1287 module will be called cyblafb.
1290 tristate "Trident support"
1291 depends on FB && PCI
1292 select FB_CFB_FILLRECT
1293 select FB_CFB_COPYAREA
1294 select FB_CFB_IMAGEBLIT
1296 This driver is supposed to support graphics boards with the
1297 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1298 but also on some motherboards. For more information, read
1299 <file:Documentation/fb/tridentfb.txt>
1301 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1304 Say Y if you have such a graphics board.
1307 To compile this driver as a module, choose M here: the
1308 module will be called tridentfb.
1310 config FB_TRIDENT_ACCEL
1311 bool "Trident Acceleration functions (EXPERIMENTAL)"
1312 depends on FB_TRIDENT && EXPERIMENTAL
1314 This will compile the Trident frame buffer device with
1315 acceleration functions.
1318 tristate "Permedia3 support"
1319 depends on FB && PCI && BROKEN
1321 This is the frame buffer device driver for the 3DLabs Permedia3
1322 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1323 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1324 and maybe other boards.
1327 bool "Au1100 LCD Driver"
1328 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1331 bool "Au1200 LCD Driver"
1332 depends on FB && MIPS && SOC_AU1200
1333 select FB_CFB_FILLRECT
1334 select FB_CFB_COPYAREA
1335 select FB_CFB_IMAGEBLIT
1337 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1338 various panels and CRTs by passing in kernel cmd line option
1339 au1200fb:panel=<name>.
1341 source "drivers/video/geode/Kconfig"
1344 bool "Creator/Creator3D/Elite3D support"
1345 depends on FB_SBUS && SPARC64
1346 select FB_CFB_COPYAREA
1347 select FB_CFB_IMAGEBLIT
1349 This is the frame buffer device driver for the Creator, Creator3D,
1350 and Elite3D graphics boards.
1353 bool "TCX (SS4/SS5 only) support"
1355 select FB_CFB_FILLRECT
1356 select FB_CFB_COPYAREA
1357 select FB_CFB_IMAGEBLIT
1359 This is the frame buffer device driver for the TCX 24/8bit frame
1363 bool "CGfourteen (SX) support"
1365 select FB_CFB_FILLRECT
1366 select FB_CFB_COPYAREA
1367 select FB_CFB_IMAGEBLIT
1369 This is the frame buffer device driver for the CGfourteen frame
1370 buffer on Desktop SPARCsystems with the SX graphics option.
1373 bool "P9100 (Sparcbook 3 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 P9100 card
1380 supported on Sparcbook 3 machines.
1383 bool "Leo (ZX) 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 SBUS-based Sun ZX
1390 (leo) frame buffer cards.
1393 bool "PCI framebuffers"
1394 depends on (FB = y) && PCI && SPARC
1397 bool "IGA 168x display support"
1398 depends on SPARC32 && FB_PCI
1399 select FB_CFB_FILLRECT
1400 select FB_CFB_COPYAREA
1401 select FB_CFB_IMAGEBLIT
1403 This is the framebuffer device for the INTERGRAPHICS 1680 and
1404 successor frame buffer cards.
1407 tristate "HD64461 Frame Buffer support"
1408 depends on FB && HD64461
1409 select FB_CFB_FILLRECT
1410 select FB_CFB_COPYAREA
1411 select FB_CFB_IMAGEBLIT
1413 This is the frame buffer device driver for the Hitachi HD64461 LCD
1417 bool "PMAG-AA TURBOchannel framebuffer support"
1418 depends on (FB = y) && TC
1419 select FB_CFB_FILLRECT
1420 select FB_CFB_COPYAREA
1421 select FB_CFB_IMAGEBLIT
1423 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1424 used mainly in the MIPS-based DECstation series.
1427 bool "PMAG-BA TURBOchannel framebuffer support"
1428 depends on (FB = y) && TC
1429 select FB_CFB_FILLRECT
1430 select FB_CFB_COPYAREA
1431 select FB_CFB_IMAGEBLIT
1433 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1434 used mainly in the MIPS-based DECstation series.
1437 bool "PMAGB-B 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 PMAGB-B TURBOchannel framebuffer card used mainly
1444 in the MIPS-based DECstation series. The card is currently only
1445 supported in 1280x1024x8 mode.
1448 bool "Maxine (Personal DECstation) onboard framebuffer support"
1449 depends on (FB = y) && MACH_DECSTATION
1450 select FB_CFB_FILLRECT
1451 select FB_CFB_COPYAREA
1452 select FB_CFB_IMAGEBLIT
1454 Support for the onboard framebuffer (1024x768x8) in the Personal
1455 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1459 bool "TMPTX3912/PR31700 frame buffer support"
1460 depends on (FB = y) && NINO
1461 select FB_CFB_FILLRECT
1462 select FB_CFB_COPYAREA
1463 select FB_CFB_IMAGEBLIT
1465 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1466 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1468 Say Y here to enable kernel support for the on-board framebuffer.
1471 bool "G364 frame buffer support"
1472 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1473 select FB_CFB_FILLRECT
1474 select FB_CFB_COPYAREA
1475 select FB_CFB_IMAGEBLIT
1477 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1478 Olivetti M700-10 systems.
1481 bool "Motorola 68328 native frame buffer support"
1482 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1483 select FB_CFB_FILLRECT
1484 select FB_CFB_COPYAREA
1485 select FB_CFB_IMAGEBLIT
1487 Say Y here if you want to support the built-in frame buffer of
1488 the Motorola 68328 CPU family.
1491 tristate "PXA LCD framebuffer support"
1492 depends on FB && ARCH_PXA
1493 select FB_CFB_FILLRECT
1494 select FB_CFB_COPYAREA
1495 select FB_CFB_IMAGEBLIT
1497 Frame buffer driver for the built-in LCD controller in the Intel
1500 This driver is also available as a module ( = code which can be
1501 inserted and removed from the running kernel whenever you want). The
1502 module will be called pxafb. If you want to compile it as a module,
1503 say M here and read <file:Documentation/modules.txt>.
1507 config FB_PXA_PARAMETERS
1508 bool "PXA LCD command line parameters"
1512 Enable the use of kernel command line or module parameters
1513 to configure the physical properties of the LCD panel when
1514 using the PXA LCD driver.
1516 This option allows you to override the panel parameters
1517 supplied by the platform in order to support multiple
1518 different models of flatpanel. If you will only be using a
1519 single model of flatpanel then you can safely leave this
1522 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1525 tristate "W100 frame buffer support"
1526 depends on FB && PXA_SHARPSL
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1529 select FB_CFB_IMAGEBLIT
1531 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1533 This driver is also available as a module ( = code which can be
1534 inserted and removed from the running kernel whenever you want). The
1535 module will be called w100fb. If you want to compile it as a module,
1536 say M here and read <file:Documentation/modules.txt>.
1541 tristate "S3C2410 LCD framebuffer support"
1542 depends on FB && ARCH_S3C2410
1543 select FB_CFB_FILLRECT
1544 select FB_CFB_COPYAREA
1545 select FB_CFB_IMAGEBLIT
1547 Frame buffer driver for the built-in LCD controller in the Samsung
1550 This driver is also available as a module ( = code which can be
1551 inserted and removed from the running kernel whenever you want). The
1552 module will be called s3c2410fb. If you want to compile it as a module,
1553 say M here and read <file:Documentation/modules.txt>.
1556 config FB_S3C2410_DEBUG
1557 bool "S3C2410 lcd debug messages"
1558 depends on FB_S3C2410
1560 Turn on debugging messages. Note that you can set/unset at run time
1564 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1566 select FB_CFB_FILLRECT
1567 select FB_CFB_COPYAREA
1568 select FB_CFB_IMAGEBLIT
1570 This is a `virtual' frame buffer device. It operates on a chunk of
1571 unswappable kernel memory instead of on the memory of a graphics
1572 board. This means you cannot see any output sent to this frame
1573 buffer device, while it does consume precious memory. The main use
1574 of this frame buffer device is testing and debugging the frame
1575 buffer subsystem. Do NOT enable it for normal systems! To protect
1576 the innocent, it has to be enabled explicitly at boot time using the
1577 kernel option `video=vfb:'.
1579 To compile this driver as a module, choose M here: the
1580 module will be called vfb.
1584 source "drivers/video/console/Kconfig"
1587 if FB || SGI_NEWPORT_CONSOLE
1588 source "drivers/video/logo/Kconfig"
1592 source "drivers/video/backlight/Kconfig"