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.
56 config FB_CFB_FILLRECT
61 Include the cfb_fillrect function for generic software rectangle
62 filling. This is used by drivers that don't provide their own
63 (accelerated) version.
65 config FB_CFB_COPYAREA
70 Include the cfb_copyarea function for generic software area copying.
71 This is used by drivers that don't provide their own (accelerated)
74 config FB_CFB_IMAGEBLIT
79 Include the cfb_imageblit function for generic software image
80 blitting. This is used by drivers that don't provide their own
81 (accelerated) version.
93 config FB_MODE_HELPERS
94 bool "Enable Video Mode Handling Helpers"
98 This enables functions for handling video modes using the
99 Generalized Timing Formula and the EDID parser. A few drivers rely
100 on this feature such as the radeonfb, rivafb, and the i810fb. If
101 your driver does not take advantage of this feature, choosing Y will
102 just increase the kernel size by about 5K.
104 config FB_TILEBLITTING
105 bool "Enable Tile Blitting Support"
109 This enables tile blitting. Tile blitting is a drawing technique
110 where the screen is divided into rectangular sections (tiles), whereas
111 the standard blitting divides the screen into pixels. Because the
112 default drawing element is a tile, drawing functions will be passed
113 parameters in terms of number of tiles instead of number of pixels.
114 For example, to draw a single character, instead of using bitmaps,
115 an index to an array of bitmaps will be used. To clear or move a
116 rectangular section of a screen, the rectangle will be described in
117 terms of number of tiles in the x- and y-axis.
119 This is particularly important to one driver, matroxfb. If
123 tristate "Cirrus Logic support"
124 depends on FB && (ZORRO || PCI)
125 select FB_CFB_FILLRECT
126 select FB_CFB_COPYAREA
127 select FB_CFB_IMAGEBLIT
129 This enables support for Cirrus Logic GD542x/543x based boards on
130 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
132 If you have a PCI-based system, this enables support for these
133 chips: GD-543x, GD-544x, GD-5480.
135 Please read the file <file:Documentation/fb/cirrusfb.txt>.
137 Say N unless you have such a graphics board or plan to get one
138 before you next recompile the kernel.
141 tristate "Permedia2 support"
142 depends on FB && ((AMIGA && BROKEN) || PCI)
143 select FB_CFB_FILLRECT
144 select FB_CFB_COPYAREA
145 select FB_CFB_IMAGEBLIT
147 This is the frame buffer device driver for the Permedia2 AGP frame
148 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
150 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
152 config FB_PM2_FIFO_DISCONNECT
153 bool "enable FIFO disconnect feature"
154 depends on FB_PM2 && PCI
156 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
159 tristate "ARM PrimeCell PL110 support"
160 depends on FB && ARM && ARM_AMBA
161 select FB_CFB_FILLRECT
162 select FB_CFB_COPYAREA
163 select FB_CFB_IMAGEBLIT
165 This framebuffer device driver is for the ARM PrimeCell PL110
166 Colour LCD controller. ARM PrimeCells provide the building
167 blocks for System on a Chip devices.
169 If you want to compile this as a module (=code which can be
170 inserted into and removed from the running kernel), say M
171 here and read <file:Documentation/modules.txt>. The module
172 will be called amba-clcd.
176 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
178 default FB_ARMCLCD_SHARP_LQ035Q7DB02
180 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
181 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
183 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
184 color QVGA, HRTFT panel. The LogicPD device includes an
185 an integrated HRTFT controller IC.
186 The native resolution is 240x320.
188 config FB_ARMCLCD_SHARP_LQ057Q3DC02
189 bool "LogicPD LCD 5.7\" QVGA"
191 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
192 color QVGA, TFT panel. The LogicPD device includes an
193 The native resolution is 320x240.
195 config FB_ARMCLCD_SHARP_LQ64D343
196 bool "LogicPD LCD 6.4\" VGA"
198 This is an implementation of the Sharp LQ64D343, a 6.4"
199 color VGA, TFT panel. The LogicPD device includes an
200 The native resolution is 640x480.
202 config FB_ARMCLCD_SHARP_LQ10D368
203 bool "LogicPD LCD 10.4\" VGA"
205 This is an implementation of the Sharp LQ10D368, a 10.4"
206 color VGA, TFT panel. The LogicPD device includes an
207 The native resolution is 640x480.
210 config FB_ARMCLCD_SHARP_LQ121S1DG41
211 bool "LogicPD LCD 12.1\" SVGA"
213 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
214 color SVGA, TFT panel. The LogicPD device includes an
215 The native resolution is 800x600.
217 This panel requires a clock rate may be an integer fraction
218 of the base LCDCLK frequency. The driver will select the
219 highest frequency available that is lower than the maximum
220 allowed. The panel may flicker if the clock rate is
221 slower than the recommended minimum.
223 config FB_ARMCLCD_AUO_A070VW01_WIDE
224 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
226 This is an implementation of the AU Optronics, a 7.0"
227 WIDE Color. The native resolution is 234x480.
229 config FB_ARMCLCD_HITACHI
230 bool "Hitachi Wide Screen 800x480"
232 This is an implementation of the Hitachi 800x480.
238 bool "Acorn VIDC support"
239 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
240 select FB_CFB_FILLRECT
241 select FB_CFB_COPYAREA
242 select FB_CFB_IMAGEBLIT
244 This is the frame buffer device driver for the Acorn VIDC graphics
245 hardware found in Acorn RISC PCs and other ARM-based machines. If
249 bool "CLPS711X LCD support"
250 depends on (FB = y) && ARM && ARCH_CLPS711X
251 select FB_CFB_FILLRECT
252 select FB_CFB_COPYAREA
253 select FB_CFB_IMAGEBLIT
255 Say Y to enable the Framebuffer driver for the CLPS7111 and
259 bool "SA-1100 LCD support"
260 depends on (FB = y) && ARM && ARCH_SA1100
261 select FB_CFB_FILLRECT
262 select FB_CFB_COPYAREA
263 select FB_CFB_IMAGEBLIT
265 This is a framebuffer device for the SA-1100 LCD Controller.
266 See <http://www.linux-fbdev.org/> for information on framebuffer
269 If you plan to use the LCD display with your SA-1100 system, say
273 tristate "Motorola i.MX LCD support"
274 depends on FB && ARM && ARCH_IMX
275 select FB_CFB_FILLRECT
276 select FB_CFB_COPYAREA
277 select FB_CFB_IMAGEBLIT
280 tristate "CyberPro 2000/2010/5000 support"
281 depends on FB && PCI && (BROKEN || !SPARC64)
282 select FB_CFB_FILLRECT
283 select FB_CFB_COPYAREA
284 select FB_CFB_IMAGEBLIT
286 This enables support for the Integraphics CyberPro 20x0 and 5000
287 VGA chips used in the Rebel.com Netwinder and other machines.
288 Say Y if you have a NetWinder or a graphics card containing this
289 device, otherwise say N.
293 depends on (FB = y) && APOLLO
295 select FB_CFB_FILLRECT
296 select FB_CFB_IMAGEBLIT
300 depends on (FB = y) && Q40
302 select FB_CFB_FILLRECT
303 select FB_CFB_COPYAREA
304 select FB_CFB_IMAGEBLIT
307 tristate "Amiga native chipset support"
308 depends on FB && AMIGA
310 This is the frame buffer device driver for the builtin graphics
311 chipset found in Amigas.
313 To compile this driver as a module, choose M here: the
314 module will be called amifb.
317 bool "Amiga OCS chipset support"
320 This enables support for the original Agnus and Denise video chips,
321 found in the Amiga 1000 and most A500's and A2000's. If you intend
322 to run Linux on any of these systems, say Y; otherwise say N.
325 bool "Amiga ECS chipset support"
328 This enables support for the Enhanced Chip Set, found in later
329 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
330 you intend to run Linux on any of these systems, say Y; otherwise
334 bool "Amiga AGA chipset support"
337 This enables support for the Advanced Graphics Architecture (also
338 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
339 and CD32. If you intend to run Linux on any of these systems, say Y;
343 tristate "Amiga CyberVision 64 support"
344 depends on FB && ZORRO && BROKEN
345 select FB_CFB_FILLRECT
346 select FB_CFB_COPYAREA
347 select FB_CFB_IMAGEBLIT
349 This enables support for the Cybervision 64 graphics card from
350 Phase5. Please note that its use is not all that intuitive (i.e. if
351 you have any questions, be sure to ask!). Say N unless you have a
352 Cybervision 64 or plan to get one before you next recompile the
353 kernel. Please note that this driver DOES NOT support the
354 Cybervision 64/3D card, as they use incompatible video chips.
357 bool "Amiga CyberVision 64/3D support "
358 depends on (FB = y) && ZORRO && BROKEN
359 select FB_CFB_FILLRECT
360 select FB_CFB_COPYAREA
361 select FB_CFB_IMAGEBLIT
363 This enables support for the Cybervision 64/3D graphics card from
364 Phase5. Please note that its use is not all that intuitive (i.e. if
365 you have any questions, be sure to ask!). Say N unless you have a
366 Cybervision 64/3D or plan to get one before you next recompile the
367 kernel. Please note that this driver DOES NOT support the older
368 Cybervision 64 card, as they use incompatible video chips.
371 tristate "Amiga Retina Z3 support"
372 depends on (FB = y) && ZORRO && BROKEN
374 This enables support for the Retina Z3 graphics card. Say N unless
375 you have a Retina Z3 or plan to get one before you next recompile
379 bool "Amiga FrameMaster II/Rainbow II support"
380 depends on (FB = y) && ZORRO
381 select FB_CFB_FILLRECT
382 select FB_CFB_COPYAREA
383 select FB_CFB_IMAGEBLIT
385 This is the frame buffer device driver for the Amiga FrameMaster
386 card from BSC (exhibited 1992 but not shipped as a CBM product).
389 tristate "Arc Monochrome LCD board support"
391 select FB_CFB_FILLRECT
392 select FB_CFB_COPYAREA
393 select FB_CFB_IMAGEBLIT
395 This enables support for the Arc Monochrome LCD board. The board
396 is based on the KS-108 lcd controller and is typically a matrix
397 of 2*n chips. This driver was tested with a 128x64 panel. This
398 driver supports it for use with x86 SBCs through a 16 bit GPIO
399 interface (8 bit data, 8 bit control). If you anticpate using
400 this driver, say Y or M; otherwise say N. You must specify the
401 GPIO IO address to be used for setting control and data.
404 bool "Atari native chipset support"
405 depends on (FB = y) && ATARI && BROKEN
407 This is the frame buffer device driver for the builtin graphics
408 chipset found in Ataris.
411 bool "Open Firmware frame buffer device support"
412 depends on (FB = y) && (PPC64 || PPC_OF)
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
418 Say Y if you want support with Open Firmware for your graphics
422 bool "Apple \"control\" display support"
423 depends on (FB = y) && PPC_PMAC
424 select FB_CFB_FILLRECT
425 select FB_CFB_COPYAREA
426 select FB_CFB_IMAGEBLIT
429 This driver supports a frame buffer for the graphics adapter in the
430 Power Macintosh 7300 and others.
433 bool "Apple \"platinum\" display support"
434 depends on (FB = y) && PPC_PMAC
435 select FB_CFB_FILLRECT
436 select FB_CFB_COPYAREA
437 select FB_CFB_IMAGEBLIT
440 This driver supports a frame buffer for the "platinum" graphics
441 adapter in some Power Macintoshes.
444 bool "Apple \"valkyrie\" display support"
445 depends on (FB = y) && (MAC || PPC_PMAC)
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
451 This driver supports a frame buffer for the "valkyrie" graphics
452 adapter in some Power Macintoshes.
455 bool "Chips 65550 display support"
456 depends on (FB = y) && PPC
457 select FB_CFB_FILLRECT
458 select FB_CFB_COPYAREA
459 select FB_CFB_IMAGEBLIT
461 This is the frame buffer device driver for the Chips & Technologies
462 65550 graphics chip in PowerBooks.
465 bool "Asiliant (Chips) 69000 display support"
466 depends on (FB = y) && PCI
467 select FB_CFB_FILLRECT
468 select FB_CFB_COPYAREA
469 select FB_CFB_IMAGEBLIT
471 This is the frame buffer device driver for the Asiliant 69030 chipset
474 bool "IMS Twin Turbo display support"
475 depends on (FB = y) && PCI
476 select FB_CFB_IMAGEBLIT
477 select FB_MACMODES if PPC
479 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
480 many Macintosh and compatible computers.
483 tristate "VGA 16-color graphics support"
484 depends on FB && (X86 || PPC)
485 select FB_CFB_FILLRECT
486 select FB_CFB_COPYAREA
487 select FB_CFB_IMAGEBLIT
489 This is the frame buffer device driver for VGA 16 color graphic
490 cards. Say Y if you have such a card.
492 To compile this driver as a module, choose M here: the
493 module will be called vga16fb.
496 tristate "HP STI frame buffer device support"
497 depends on FB && PARISC
498 select FB_CFB_FILLRECT
499 select FB_CFB_COPYAREA
500 select FB_CFB_IMAGEBLIT
503 STI refers to the HP "Standard Text Interface" which is a set of
504 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
505 Enabling this option will implement the linux framebuffer device
506 using calls to the STI BIOS routines for initialisation.
508 If you enable this option, you will get a planar framebuffer device
509 /dev/fb which will work on the most common HP graphic cards of the
510 NGLE family, including the artist chips (in the 7xx and Bxxx series),
511 HCRX, HCRX24, CRX, CRX24 and VisEG series.
513 It is safe to enable this option, so you should probably say "Y".
516 bool "Generic Macintosh display support"
517 depends on (FB = y) && MAC
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
526 depends on (FB = y) && HP300
527 select FB_CFB_FILLRECT
528 select FB_CFB_IMAGEBLIT
532 tristate "TGA framebuffer support"
533 depends on FB && ALPHA
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
538 This is the frame buffer device driver for generic TGA graphic
539 cards. Say Y if you have one of those.
542 bool "VESA VGA graphics support"
543 depends on (FB = y) && X86
544 select FB_CFB_FILLRECT
545 select FB_CFB_COPYAREA
546 select FB_CFB_IMAGEBLIT
548 This is the frame buffer device driver for generic VESA 2.0
549 compliant graphic cards. The older VESA 1.2 cards are not supported.
550 You will get a boot time penguin logo at no additional cost. Please
551 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
554 tristate "Hercules mono graphics support"
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
560 Say Y here if you have a Hercules mono graphics card.
562 To compile this driver as a module, choose M here: the
563 module will be called hgafb.
565 As this card technology is 15 years old, most people will answer N
569 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
570 depends on FB_HGA && EXPERIMENTAL
572 This will compile the Hercules mono graphics with
573 acceleration functions.
576 tristate "SGI Visual Workstation framebuffer support"
577 depends on FB && X86_VISWS
578 select FB_CFB_FILLRECT
579 select FB_CFB_COPYAREA
580 select FB_CFB_IMAGEBLIT
582 SGI Visual Workstation support for framebuffer graphics.
585 bool "SGI Graphics Backend frame buffer support"
586 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
587 select FB_CFB_FILLRECT
588 select FB_CFB_COPYAREA
589 select FB_CFB_IMAGEBLIT
591 This is the frame buffer device driver for SGI Graphics Backend.
592 This chip is used in SGI O2 and Visual Workstation 320/540.
595 int "Video memory size in MB"
599 This is the amount of memory reserved for the framebuffer,
600 which can be any value between 1MB and 8MB.
603 bool "Sun3 framebuffer support"
604 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
607 bool "SBUS and UPA framebuffers"
608 depends on (FB = y) && SPARC
610 Say Y if you want support for SBUS or UPA based frame buffer device.
614 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
615 select FB_CFB_FILLRECT
616 select FB_CFB_COPYAREA
617 select FB_CFB_IMAGEBLIT
619 This is the frame buffer device driver for the BWtwo frame buffer.
622 bool "CGthree support"
623 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
624 select FB_CFB_FILLRECT
625 select FB_CFB_COPYAREA
626 select FB_CFB_IMAGEBLIT
628 This is the frame buffer device driver for the CGthree frame buffer.
631 bool "CGsix (GX,TurboGX) support"
632 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
633 select FB_CFB_COPYAREA
634 select FB_CFB_IMAGEBLIT
636 This is the frame buffer device driver for the CGsix (GX, TurboGX)
640 tristate "NEC PowerVR 2 display support"
641 depends on FB && SH_DREAMCAST
642 select FB_CFB_FILLRECT
643 select FB_CFB_COPYAREA
644 select FB_CFB_IMAGEBLIT
646 Say Y here if you have a PowerVR 2 card in your box. If you plan to
647 run linux on your Dreamcast, you will have to say Y here.
648 This driver may or may not work on other PowerVR 2 cards, but is
649 totally untested. Use at your own risk. If unsure, say N.
651 To compile this driver as a module, choose M here: the
652 module will be called pvr2fb.
654 You can pass several parameters to the driver at boot time or at
655 module load time. The parameters look like "video=pvr2:XXX", where
656 the meaning of XXX can be found at the end of the main source file
657 (<file:drivers/video/pvr2fb.c>). Please see the file
658 <file:Documentation/fb/pvr2fb.txt>.
661 bool "Epson 1355 framebuffer support"
662 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
667 Build in support for the SED1355 Epson Research Embedded RAMDAC
668 LCD/CRT Controller (since redesignated as the S1D13505) as a
669 framebuffer. Product specs at
670 <http://www.erd.epson.com/vdc/html/products.htm>.
673 tristate "Epson S1D13XXX framebuffer support"
675 select FB_CFB_FILLRECT
676 select FB_CFB_COPYAREA
677 select FB_CFB_IMAGEBLIT
679 Support for S1D13XXX framebuffer device family (currently only
680 working with S1D13806). Product specs at
681 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
684 tristate "nVidia Framebuffer Support"
686 select I2C_ALGOBIT if FB_NVIDIA_I2C
687 select I2C if FB_NVIDIA_I2C
688 select FB_MODE_HELPERS
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
693 This driver supports graphics boards with the nVidia chips, TNT
694 and newer. For very old chipsets, such as the RIVA128, then use
696 Say Y if you have such a graphics board.
698 To compile this driver as a module, choose M here: the
699 module will be called nvidiafb.
702 bool "Enable DDC Support"
705 This enables I2C support for nVidia Chipsets. This is used
706 only for getting EDID information from the attached display
707 allowing for robust video mode handling and switching.
709 Because fbdev-2.6 requires that drivers must be able to
710 independently validate video mode parameters, you should say Y
713 config FB_NVIDIA_BACKLIGHT
714 bool "Support for backlight control"
715 depends on FB_NVIDIA && PPC_PMAC
717 select BACKLIGHT_LCD_SUPPORT
718 select BACKLIGHT_CLASS_DEVICE
721 Say Y here if you want to control the backlight of your display.
724 tristate "nVidia Riva support"
726 select I2C_ALGOBIT if FB_RIVA_I2C
727 select I2C if FB_RIVA_I2C
728 select FB_MODE_HELPERS
729 select FB_CFB_FILLRECT
730 select FB_CFB_COPYAREA
731 select FB_CFB_IMAGEBLIT
733 This driver supports graphics boards with the nVidia Riva/Geforce
735 Say Y if you have such a graphics board.
737 To compile this driver as a module, choose M here: the
738 module will be called rivafb.
741 bool "Enable DDC Support"
744 This enables I2C support for nVidia Chipsets. This is used
745 only for getting EDID information from the attached display
746 allowing for robust video mode handling and switching.
748 Because fbdev-2.6 requires that drivers must be able to
749 independently validate video mode parameters, you should say Y
753 bool "Lots of debug output from Riva(nVidia) driver"
757 Say Y here if you want the Riva driver to output all sorts
758 of debugging informations to provide to the maintainer when
759 something goes wrong.
761 config FB_RIVA_BACKLIGHT
762 bool "Support for backlight control"
763 depends on FB_RIVA && PPC_PMAC
765 select BACKLIGHT_LCD_SUPPORT
766 select BACKLIGHT_CLASS_DEVICE
769 Say Y here if you want to control the backlight of your display.
772 tristate "Intel 810/815 support (EXPERIMENTAL)"
773 depends on FB && EXPERIMENTAL && PCI && X86_32
776 select FB_MODE_HELPERS
777 select FB_CFB_FILLRECT
778 select FB_CFB_COPYAREA
779 select FB_CFB_IMAGEBLIT
781 This driver supports the on-board graphics built in to the Intel 810
782 and 815 chipsets. Say Y if you have and plan to use such a board.
784 To compile this driver as a module, choose M here: the
785 module will be called i810fb.
787 For more information, please read
788 <file:Documentation/fb/intel810.txt>
791 bool "use VESA Generalized Timing Formula"
794 If you say Y, then the VESA standard, Generalized Timing Formula
795 or GTF, will be used to calculate the required video timing values
796 per video mode. Since the GTF allows nondiscrete timings
797 (nondiscrete being a range of values as opposed to discrete being a
798 set of values), you'll be able to use any combination of horizontal
799 and vertical resolutions, and vertical refresh rates without having
800 to specify your own timing parameters. This is especially useful
801 to maximize the performance of an aging display, or if you just
802 have a display with nonstandard dimensions. A VESA compliant
803 monitor is recommended, but can still work with non-compliant ones.
804 If you need or want this, then select this option. The timings may
805 not be compliant with Intel's recommended values. Use at your own
808 If you say N, the driver will revert to discrete video timings
809 using a set recommended by Intel in their documentation.
814 bool "Enable DDC Support"
815 depends on FB_I810 && FB_I810_GTF
821 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
822 depends on FB && EXPERIMENTAL && PCI && X86
825 select FB_MODE_HELPERS
826 select FB_CFB_FILLRECT
827 select FB_CFB_COPYAREA
828 select FB_CFB_IMAGEBLIT
830 This driver supports the on-board graphics built in to the Intel
831 830M/845G/852GM/855GM/865G chipsets.
832 Say Y if you have and plan to use such a board.
834 To compile this driver as a module, choose M here: the
835 module will be called intelfb.
837 config FB_INTEL_DEBUG
838 bool "Intel driver Debug Messages"
841 Say Y here if you want the Intel driver to output all sorts
842 of debugging informations to provide to the maintainer when
843 something goes wrong.
846 tristate "Matrox acceleration"
848 select FB_CFB_FILLRECT
849 select FB_CFB_COPYAREA
850 select FB_CFB_IMAGEBLIT
851 select FB_TILEBLITTING
852 select FB_MACMODES if PPC_PMAC
854 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
855 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
856 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
857 Matrox G400, G450 or G550 card in your box.
859 To compile this driver as a module, choose M here: the
860 module will be called matroxfb.
862 You can pass several parameters to the driver at boot time or at
863 module load time. The parameters look like "video=matrox:XXX", and
864 are described in <file:Documentation/fb/matroxfb.txt>.
866 config FB_MATROX_MILLENIUM
867 bool "Millennium I/II support"
870 Say Y here if you have a Matrox Millennium or Matrox Millennium II
871 video card. If you select "Advanced lowlevel driver options" below,
872 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
873 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
874 also use font widths different from 8.
876 config FB_MATROX_MYSTIQUE
877 bool "Mystique support"
880 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
881 video card. If you select "Advanced lowlevel driver options" below,
882 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
883 packed pixel and 32 bpp packed pixel. You can also use font widths
887 bool "G100/G200/G400/G450/G550 support"
890 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
891 video card. If you select "Advanced lowlevel driver options", you
892 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
893 pixel and 32 bpp packed pixel. You can also use font widths
896 If you need support for G400 secondary head, you must first say Y to
897 "I2C support" in the character devices section, and then to
898 "Matrox I2C support" and "G400 second head support" here in the
899 framebuffer section. G450/G550 secondary head and digital output
900 are supported without additional modules.
902 The driver starts in monitor mode. You must use the matroxset tool
903 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
904 swap primary and secondary head outputs, or to change output mode.
905 Secondary head driver always start in 640x480 resolution and you
906 must use fbset to change it.
908 Do not forget that second head supports only 16 and 32 bpp
909 packed pixels, so it is a good idea to compile them into the kernel
910 too. You can use only some font widths, as the driver uses generic
911 painting procedures (the secondary head does not use acceleration
914 G450/G550 hardware can display TV picture only from secondary CRTC,
915 and it performs no scaling, so picture must have 525 or 625 lines.
918 tristate "Matrox I2C support"
919 depends on FB_MATROX && I2C
922 This drivers creates I2C buses which are needed for accessing the
923 DDC (I2C) bus present on all Matroxes, an I2C bus which
924 interconnects Matrox optional devices, like MGA-TVO on G200 and
925 G400, and the secondary head DDC bus, present on G400 only.
927 You can say Y or M here if you want to experiment with monitor
928 detection code. You must say Y or M here if you want to use either
929 second head of G400 or MGA-TVO on G200 or G400.
931 If you compile it as module, it will create a module named
934 config FB_MATROX_MAVEN
935 tristate "G400 second head support"
936 depends on FB_MATROX_G && FB_MATROX_I2C
938 WARNING !!! This support does not work with G450 !!!
940 Say Y or M here if you want to use a secondary head (meaning two
941 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
942 head is not compatible with accelerated XFree 3.3.x SVGA servers -
943 secondary head output is blanked while you are in X. With XFree
944 3.9.17 preview you can use both heads if you use SVGA over fbdev or
945 the fbdev driver on first head and the fbdev driver on second head.
947 If you compile it as module, two modules are created,
948 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
949 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
950 also load i2c-matroxfb to get it to run.
952 The driver starts in monitor mode and you must use the matroxset
954 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
955 PAL or NTSC or to swap primary and secondary head outputs.
956 Secondary head driver also always start in 640x480 resolution, you
957 must use fbset to change it.
959 Also do not forget that second head supports only 16 and 32 bpp
960 packed pixels, so it is a good idea to compile them into the kernel
961 too. You can use only some font widths, as the driver uses generic
962 painting procedures (the secondary head does not use acceleration
965 config FB_MATROX_MULTIHEAD
966 bool "Multihead support"
969 Say Y here if you have more than one (supported) Matrox device in
970 your computer and you want to use all of them for different monitors
971 ("multihead"). If you have only one device, you should say N because
972 the driver compiled with Y is larger and a bit slower, especially on
975 If you said M to "Matrox unified accelerated driver" and N here, you
976 will still be able to use several Matrox devices simultaneously:
977 insert several instances of the module matroxfb into the kernel
978 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
979 for the different Matrox devices. This method is slightly faster but
980 uses 40 KB of kernel memory per Matrox card.
982 There is no need for enabling 'Matrox multihead support' if you have
983 only one Matrox card in the box.
986 tristate "ATI Radeon display support"
988 select I2C_ALGOBIT if FB_RADEON_I2C
989 select I2C if FB_RADEON_I2C
990 select FB_MODE_HELPERS
991 select FB_CFB_FILLRECT
992 select FB_CFB_COPYAREA
993 select FB_CFB_IMAGEBLIT
994 select FB_MACMODES if PPC_OF
996 Choose this option if you want to use an ATI Radeon graphics card as
997 a framebuffer device. There are both PCI and AGP versions. You
998 don't need to choose this to run the Radeon in plain VGA mode.
1000 If you say Y here and want DDC/I2C support you must first say Y to
1001 "I2C support" and "I2C bit-banging support" in the character devices
1004 If you say M here then "I2C support" and "I2C bit-banging support"
1005 can be build either as modules or built-in.
1007 There is a product page at
1008 http://apps.ati.com/ATIcompare/
1010 config FB_RADEON_I2C
1011 bool "DDC/I2C for ATI Radeon support"
1012 depends on FB_RADEON
1015 Say Y here if you want DDC/I2C support for your Radeon board.
1017 config FB_RADEON_BACKLIGHT
1018 bool "Support for backlight control"
1019 depends on FB_RADEON && PPC_PMAC
1021 select BACKLIGHT_LCD_SUPPORT
1022 select BACKLIGHT_CLASS_DEVICE
1025 Say Y here if you want to control the backlight of your display.
1027 config FB_RADEON_DEBUG
1028 bool "Lots of debug output from Radeon driver"
1029 depends on FB_RADEON
1032 Say Y here if you want the Radeon driver to output all sorts
1033 of debugging informations to provide to the maintainer when
1034 something goes wrong.
1037 tristate "ATI Rage128 display support"
1038 depends on FB && PCI
1039 select FB_CFB_FILLRECT
1040 select FB_CFB_COPYAREA
1041 select FB_CFB_IMAGEBLIT
1042 select FB_MACMODES if PPC_PMAC
1044 This driver supports graphics boards with the ATI Rage128 chips.
1045 Say Y if you have such a graphics board and read
1046 <file:Documentation/fb/aty128fb.txt>.
1048 To compile this driver as a module, choose M here: the
1049 module will be called aty128fb.
1051 config FB_ATY128_BACKLIGHT
1052 bool "Support for backlight control"
1053 depends on FB_ATY128 && PPC_PMAC
1055 select BACKLIGHT_LCD_SUPPORT
1056 select BACKLIGHT_CLASS_DEVICE
1059 Say Y here if you want to control the backlight of your display.
1062 tristate "ATI Mach64 display support" if PCI || ATARI
1063 depends on FB && !SPARC32
1064 select FB_CFB_FILLRECT
1065 select FB_CFB_COPYAREA
1066 select FB_CFB_IMAGEBLIT
1067 select FB_MACMODES if PPC
1069 This driver supports graphics boards with the ATI Mach64 chips.
1070 Say Y if you have such a graphics board.
1072 To compile this driver as a module, choose M here: the
1073 module will be called atyfb.
1076 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1077 depends on PCI && FB_ATY
1078 default y if SPARC64 && FB_PCI
1080 Say Y here to support use of ATI's 64-bit Rage boards (or other
1081 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1082 framebuffer device. The ATI product support page for these boards
1083 is at <http://support.ati.com/products/pc/mach64/>.
1085 config FB_ATY_GENERIC_LCD
1086 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1087 depends on FB_ATY_CT
1089 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1090 Rage XC, or Rage XL chipset.
1093 bool "Mach64 GX support" if PCI
1097 Say Y here to support use of the ATI Mach64 Graphics Expression
1098 board (or other boards based on the Mach64 GX chipset) as a
1099 framebuffer device. The ATI product support page for these boards
1101 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1103 config FB_ATY_BACKLIGHT
1104 bool "Support for backlight control"
1105 depends on FB_ATY && PPC_PMAC
1107 select BACKLIGHT_LCD_SUPPORT
1108 select BACKLIGHT_CLASS_DEVICE
1111 Say Y here if you want to control the backlight of your display.
1114 bool "S3 Trio display support"
1115 depends on (FB = y) && PPC && BROKEN
1117 If you have a S3 Trio say Y. Say N for S3 Virge.
1120 tristate "S3 Savage support"
1121 depends on FB && PCI && EXPERIMENTAL
1122 select I2C_ALGOBIT if FB_SAVAGE_I2C
1123 select I2C if FB_SAVAGE_I2C
1124 select FB_MODE_HELPERS
1125 select FB_CFB_FILLRECT
1126 select FB_CFB_COPYAREA
1127 select FB_CFB_IMAGEBLIT
1129 This driver supports notebooks and computers with S3 Savage PCI/AGP
1132 Say Y if you have such a graphics card.
1134 To compile this driver as a module, choose M here; the module
1135 will be called savagefb.
1137 config FB_SAVAGE_I2C
1138 bool "Enable DDC2 Support"
1139 depends on FB_SAVAGE
1141 This enables I2C support for S3 Savage Chipsets. This is used
1142 only for getting EDID information from the attached display
1143 allowing for robust video mode handling and switching.
1145 Because fbdev-2.6 requires that drivers must be able to
1146 independently validate video mode parameters, you should say Y
1149 config FB_SAVAGE_ACCEL
1150 bool "Enable Console Acceleration"
1151 depends on FB_SAVAGE
1154 This option will compile in console acceleration support. If
1155 the resulting framebuffer console has bothersome glitches, then
1159 tristate "SiS/XGI display support"
1160 depends on FB && PCI
1161 select FB_CFB_FILLRECT
1162 select FB_CFB_COPYAREA
1163 select FB_CFB_IMAGEBLIT
1165 This is the frame buffer device driver for the SiS 300, 315, 330
1166 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1167 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1169 To compile this driver as a module, choose M here; the module
1170 will be called sisfb.
1173 bool "SiS 300 series support"
1176 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1179 bool "SiS 315/330/340 series and XGI support"
1182 Say Y here to support use of the SiS 315, 330 and 340 series
1183 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1184 as XGI V3XT, V5, V8 and Z7.
1187 tristate "NeoMagic display support"
1188 depends on FB && PCI
1189 select FB_MODE_HELPERS
1190 select FB_CFB_FILLRECT
1191 select FB_CFB_COPYAREA
1192 select FB_CFB_IMAGEBLIT
1194 This driver supports notebooks with NeoMagic PCI chips.
1195 Say Y if you have such a graphics card.
1197 To compile this driver as a module, choose M here: the
1198 module will be called neofb.
1201 tristate "IMG Kyro support"
1202 depends on FB && PCI
1203 select FB_CFB_FILLRECT
1204 select FB_CFB_COPYAREA
1205 select FB_CFB_IMAGEBLIT
1207 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1210 To compile this driver as a module, choose M here: the
1211 module will be called kyrofb.
1214 tristate "3Dfx Banshee/Voodoo3 display support"
1215 depends on FB && PCI
1216 select FB_CFB_IMAGEBLIT
1217 select FB_CFB_FILLRECT
1218 select FB_CFB_COPYAREA
1220 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1221 chips. Say Y if you have such a graphics board.
1223 To compile this driver as a module, choose M here: the
1224 module will be called tdfxfb.
1226 config FB_3DFX_ACCEL
1227 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1228 depends on FB_3DFX && EXPERIMENTAL
1230 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1231 with acceleration functions.
1235 tristate "3Dfx Voodoo Graphics (sst1) support"
1236 depends on FB && PCI
1237 select FB_CFB_FILLRECT
1238 select FB_CFB_COPYAREA
1239 select FB_CFB_IMAGEBLIT
1241 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1242 Voodoo2 (cvg) based graphics card.
1244 To compile this driver as a module, choose M here: the
1245 module will be called sstfb.
1247 WARNING: Do not use any application that uses the 3D engine
1248 (namely glide) while using this driver.
1249 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1250 options and other important info support.
1253 tristate "Cyberblade/i1 support"
1254 depends on FB && PCI && X86_32 && !64BIT
1255 select FB_CFB_IMAGEBLIT
1258 This driver is supposed to support the Trident Cyberblade/i1
1259 graphics core integrated in the VIA VT8601A North Bridge,
1260 also known as VIA Apollo PLE133.
1263 - Developed, tested and working on EPIA 5000 and EPIA 800.
1264 - Does work reliable on all systems with CRT/LCD connected to
1266 - Should work on systems that do use the internal LCD port, but
1267 this is absolutely not tested.
1269 Character imageblit, copyarea and rectangle fill are hw accelerated,
1270 ypan scrolling is used by default.
1272 Please do read <file:Documentation/fb/cyblafb/*>.
1274 To compile this driver as a module, choose M here: the
1275 module will be called cyblafb.
1278 tristate "Trident support"
1279 depends on FB && PCI
1280 select FB_CFB_FILLRECT
1281 select FB_CFB_COPYAREA
1282 select FB_CFB_IMAGEBLIT
1284 This driver is supposed to support graphics boards with the
1285 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1286 but also on some motherboards. For more information, read
1287 <file:Documentation/fb/tridentfb.txt>
1289 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1292 Say Y if you have such a graphics board.
1295 To compile this driver as a module, choose M here: the
1296 module will be called tridentfb.
1298 config FB_TRIDENT_ACCEL
1299 bool "Trident Acceleration functions (EXPERIMENTAL)"
1300 depends on FB_TRIDENT && EXPERIMENTAL
1302 This will compile the Trident frame buffer device with
1303 acceleration functions.
1306 tristate "Permedia3 support"
1307 depends on FB && PCI && BROKEN
1309 This is the frame buffer device driver for the 3DLabs Permedia3
1310 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1311 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1312 and maybe other boards.
1315 bool "Au1100 LCD Driver"
1316 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1319 bool "Au1200 LCD Driver"
1320 depends on FB && MIPS && SOC_AU1200
1321 select FB_CFB_FILLRECT
1322 select FB_CFB_COPYAREA
1323 select FB_CFB_IMAGEBLIT
1325 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1326 various panels and CRTs by passing in kernel cmd line option
1327 au1200fb:panel=<name>.
1329 source "drivers/video/geode/Kconfig"
1332 bool "Creator/Creator3D/Elite3D support"
1333 depends on FB_SBUS && SPARC64
1334 select FB_CFB_COPYAREA
1335 select FB_CFB_IMAGEBLIT
1337 This is the frame buffer device driver for the Creator, Creator3D,
1338 and Elite3D graphics boards.
1341 bool "TCX (SS4/SS5 only) support"
1343 select FB_CFB_FILLRECT
1344 select FB_CFB_COPYAREA
1345 select FB_CFB_IMAGEBLIT
1347 This is the frame buffer device driver for the TCX 24/8bit frame
1351 bool "CGfourteen (SX) support"
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1357 This is the frame buffer device driver for the CGfourteen frame
1358 buffer on Desktop SPARCsystems with the SX graphics option.
1361 bool "P9100 (Sparcbook 3 only) support"
1363 select FB_CFB_FILLRECT
1364 select FB_CFB_COPYAREA
1365 select FB_CFB_IMAGEBLIT
1367 This is the frame buffer device driver for the P9100 card
1368 supported on Sparcbook 3 machines.
1371 bool "Leo (ZX) support"
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1377 This is the frame buffer device driver for the SBUS-based Sun ZX
1378 (leo) frame buffer cards.
1381 bool "PCI framebuffers"
1382 depends on (FB = y) && PCI && SPARC
1385 bool "IGA 168x display support"
1386 depends on SPARC32 && FB_PCI
1387 select FB_CFB_FILLRECT
1388 select FB_CFB_COPYAREA
1389 select FB_CFB_IMAGEBLIT
1391 This is the framebuffer device for the INTERGRAPHICS 1680 and
1392 successor frame buffer cards.
1395 tristate "HD64461 Frame Buffer support"
1396 depends on FB && HD64461
1397 select FB_CFB_FILLRECT
1398 select FB_CFB_COPYAREA
1399 select FB_CFB_IMAGEBLIT
1401 This is the frame buffer device driver for the Hitachi HD64461 LCD
1405 bool "PMAG-AA TURBOchannel framebuffer support"
1406 depends on (FB = y) && TC
1407 select FB_CFB_FILLRECT
1408 select FB_CFB_COPYAREA
1409 select FB_CFB_IMAGEBLIT
1411 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1412 used mainly in the MIPS-based DECstation series.
1415 bool "PMAG-BA TURBOchannel framebuffer support"
1416 depends on (FB = y) && TC
1417 select FB_CFB_FILLRECT
1418 select FB_CFB_COPYAREA
1419 select FB_CFB_IMAGEBLIT
1421 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1422 used mainly in the MIPS-based DECstation series.
1425 bool "PMAGB-B TURBOchannel framebuffer support"
1426 depends on (FB = y) && TC
1427 select FB_CFB_FILLRECT
1428 select FB_CFB_COPYAREA
1429 select FB_CFB_IMAGEBLIT
1431 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1432 in the MIPS-based DECstation series. The card is currently only
1433 supported in 1280x1024x8 mode.
1436 bool "Maxine (Personal DECstation) onboard framebuffer support"
1437 depends on (FB = y) && MACH_DECSTATION
1438 select FB_CFB_FILLRECT
1439 select FB_CFB_COPYAREA
1440 select FB_CFB_IMAGEBLIT
1442 Support for the onboard framebuffer (1024x768x8) in the Personal
1443 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1447 bool "TMPTX3912/PR31700 frame buffer support"
1448 depends on (FB = y) && NINO
1449 select FB_CFB_FILLRECT
1450 select FB_CFB_COPYAREA
1451 select FB_CFB_IMAGEBLIT
1453 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1454 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1456 Say Y here to enable kernel support for the on-board framebuffer.
1459 bool "G364 frame buffer support"
1460 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1461 select FB_CFB_FILLRECT
1462 select FB_CFB_COPYAREA
1463 select FB_CFB_IMAGEBLIT
1465 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1466 Olivetti M700-10 systems.
1469 bool "Motorola 68328 native frame buffer support"
1470 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1471 select FB_CFB_FILLRECT
1472 select FB_CFB_COPYAREA
1473 select FB_CFB_IMAGEBLIT
1475 Say Y here if you want to support the built-in frame buffer of
1476 the Motorola 68328 CPU family.
1479 tristate "PXA LCD framebuffer support"
1480 depends on FB && ARCH_PXA
1481 select FB_CFB_FILLRECT
1482 select FB_CFB_COPYAREA
1483 select FB_CFB_IMAGEBLIT
1485 Frame buffer driver for the built-in LCD controller in the Intel
1488 This driver is also available as a module ( = code which can be
1489 inserted and removed from the running kernel whenever you want). The
1490 module will be called pxafb. If you want to compile it as a module,
1491 say M here and read <file:Documentation/modules.txt>.
1495 config FB_PXA_PARAMETERS
1496 bool "PXA LCD command line parameters"
1500 Enable the use of kernel command line or module parameters
1501 to configure the physical properties of the LCD panel when
1502 using the PXA LCD driver.
1504 This option allows you to override the panel parameters
1505 supplied by the platform in order to support multiple
1506 different models of flatpanel. If you will only be using a
1507 single model of flatpanel then you can safely leave this
1510 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1513 tristate "W100 frame buffer support"
1514 depends on FB && PXA_SHARPSL
1515 select FB_CFB_FILLRECT
1516 select FB_CFB_COPYAREA
1517 select FB_CFB_IMAGEBLIT
1519 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1521 This driver is also available as a module ( = code which can be
1522 inserted and removed from the running kernel whenever you want). The
1523 module will be called w100fb. If you want to compile it as a module,
1524 say M here and read <file:Documentation/modules.txt>.
1529 tristate "S3C2410 LCD framebuffer support"
1530 depends on FB && ARCH_S3C2410
1531 select FB_CFB_FILLRECT
1532 select FB_CFB_COPYAREA
1533 select FB_CFB_IMAGEBLIT
1535 Frame buffer driver for the built-in LCD controller in the Samsung
1538 This driver is also available as a module ( = code which can be
1539 inserted and removed from the running kernel whenever you want). The
1540 module will be called s3c2410fb. If you want to compile it as a module,
1541 say M here and read <file:Documentation/modules.txt>.
1544 config FB_S3C2410_DEBUG
1545 bool "S3C2410 lcd debug messages"
1546 depends on FB_S3C2410
1548 Turn on debugging messages. Note that you can set/unset at run time
1552 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1554 select FB_CFB_FILLRECT
1555 select FB_CFB_COPYAREA
1556 select FB_CFB_IMAGEBLIT
1558 This is a `virtual' frame buffer device. It operates on a chunk of
1559 unswappable kernel memory instead of on the memory of a graphics
1560 board. This means you cannot see any output sent to this frame
1561 buffer device, while it does consume precious memory. The main use
1562 of this frame buffer device is testing and debugging the frame
1563 buffer subsystem. Do NOT enable it for normal systems! To protect
1564 the innocent, it has to be enabled explicitly at boot time using the
1565 kernel option `video=vfb:'.
1567 To compile this driver as a module, choose M here: the
1568 module will be called vfb.
1572 source "drivers/video/console/Kconfig"
1575 if FB || SGI_NEWPORT_CONSOLE
1576 source "drivers/video/logo/Kconfig"
1580 source "drivers/video/backlight/Kconfig"