5 menu "Graphics support"
7 source "drivers/video/backlight/Kconfig"
8 source "drivers/video/display/Kconfig"
15 tristate "Support for frame buffer devices"
17 The frame buffer device provides an abstraction for the graphics
18 hardware. It represents the frame buffer of some video hardware and
19 allows application software to access the graphics hardware through
20 a well-defined interface, so the software doesn't need to know
21 anything about the low-level (hardware register) stuff.
23 Frame buffer devices work identically across the different
24 architectures supported by Linux and make the implementation of
25 application programs easier and more portable; at this point, an X
26 server exists which uses the frame buffer device exclusively.
27 On several non-X86 architectures, the frame buffer device is the
28 only way to use the graphics hardware.
30 The device is accessed through special device nodes, usually located
31 in the /dev directory, i.e. /dev/fb*.
33 You need an utility program called fbset to make full use of frame
34 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
35 and the Framebuffer-HOWTO at
36 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
39 Say Y here and to the driver for your graphics board below if you
40 are compiling a kernel for a non-x86 architecture.
42 If you are compiling for the x86 architecture, you can say Y if you
43 want to play with it, but it is not essential. Please note that
44 running graphical applications that directly touch the hardware
45 (e.g. an accelerated X server) and that are not frame buffer
46 device-aware may cause unexpected results. If unsure, say N.
49 bool "Enable firmware EDID"
53 This enables access to the EDID transferred from the firmware.
54 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
55 transfers do not work for your driver and if you are using
56 nvidiafb, i810fb or savagefb.
58 In general, choosing Y for this option is safe. If you
59 experience extremely long delays while booting before you get
60 something on your display, try setting this to N. Matrox cards in
61 combination with certain motherboards and monitors are known to
62 suffer from this problem.
71 config FB_CFB_FILLRECT
76 Include the cfb_fillrect function for generic software rectangle
77 filling. This is used by drivers that don't provide their own
78 (accelerated) version.
80 config FB_CFB_COPYAREA
85 Include the cfb_copyarea function for generic software area copying.
86 This is used by drivers that don't provide their own (accelerated)
89 config FB_CFB_IMAGEBLIT
94 Include the cfb_imageblit function for generic software image
95 blitting. This is used by drivers that don't provide their own
96 (accelerated) version.
108 Common utility functions useful to fbdev drivers of VGA-based
119 select BACKLIGHT_LCD_SUPPORT
120 select BACKLIGHT_CLASS_DEVICE
123 config FB_MODE_HELPERS
124 bool "Enable Video Mode Handling Helpers"
128 This enables functions for handling video modes using the
129 Generalized Timing Formula and the EDID parser. A few drivers rely
130 on this feature such as the radeonfb, rivafb, and the i810fb. If
131 your driver does not take advantage of this feature, choosing Y will
132 just increase the kernel size by about 5K.
134 config FB_TILEBLITTING
135 bool "Enable Tile Blitting Support"
139 This enables tile blitting. Tile blitting is a drawing technique
140 where the screen is divided into rectangular sections (tiles), whereas
141 the standard blitting divides the screen into pixels. Because the
142 default drawing element is a tile, drawing functions will be passed
143 parameters in terms of number of tiles instead of number of pixels.
144 For example, to draw a single character, instead of using bitmaps,
145 an index to an array of bitmaps will be used. To clear or move a
146 rectangular section of a screen, the rectangle will be described in
147 terms of number of tiles in the x- and y-axis.
149 This is particularly important to one driver, matroxfb. If
152 comment "Frame buffer hardware drivers"
156 tristate "Cirrus Logic support"
157 depends on FB && (ZORRO || PCI)
158 select FB_CFB_FILLRECT
159 select FB_CFB_COPYAREA
160 select FB_CFB_IMAGEBLIT
162 This enables support for Cirrus Logic GD542x/543x based boards on
163 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
165 If you have a PCI-based system, this enables support for these
166 chips: GD-543x, GD-544x, GD-5480.
168 Please read the file <file:Documentation/fb/cirrusfb.txt>.
170 Say N unless you have such a graphics board or plan to get one
171 before you next recompile the kernel.
174 tristate "Permedia2 support"
175 depends on FB && ((AMIGA && BROKEN) || PCI)
176 select FB_CFB_FILLRECT
177 select FB_CFB_COPYAREA
178 select FB_CFB_IMAGEBLIT
180 This is the frame buffer device driver for the Permedia2 AGP frame
181 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
183 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
185 config FB_PM2_FIFO_DISCONNECT
186 bool "enable FIFO disconnect feature"
187 depends on FB_PM2 && PCI
189 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
192 tristate "ARM PrimeCell PL110 support"
193 depends on FB && ARM && ARM_AMBA
194 select FB_CFB_FILLRECT
195 select FB_CFB_COPYAREA
196 select FB_CFB_IMAGEBLIT
198 This framebuffer device driver is for the ARM PrimeCell PL110
199 Colour LCD controller. ARM PrimeCells provide the building
200 blocks for System on a Chip devices.
202 If you want to compile this as a module (=code which can be
203 inserted into and removed from the running kernel), say M
204 here and read <file:Documentation/kbuild/modules.txt>. The module
205 will be called amba-clcd.
209 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
211 default FB_ARMCLCD_SHARP_LQ035Q7DB02
213 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
214 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
216 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
217 color QVGA, HRTFT panel. The LogicPD device includes
218 an integrated HRTFT controller IC.
219 The native resolution is 240x320.
221 config FB_ARMCLCD_SHARP_LQ057Q3DC02
222 bool "LogicPD LCD 5.7\" QVGA"
224 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
225 color QVGA, TFT panel. The LogicPD device includes an
226 The native resolution is 320x240.
228 config FB_ARMCLCD_SHARP_LQ64D343
229 bool "LogicPD LCD 6.4\" VGA"
231 This is an implementation of the Sharp LQ64D343, a 6.4"
232 color VGA, TFT panel. The LogicPD device includes an
233 The native resolution is 640x480.
235 config FB_ARMCLCD_SHARP_LQ10D368
236 bool "LogicPD LCD 10.4\" VGA"
238 This is an implementation of the Sharp LQ10D368, a 10.4"
239 color VGA, TFT panel. The LogicPD device includes an
240 The native resolution is 640x480.
243 config FB_ARMCLCD_SHARP_LQ121S1DG41
244 bool "LogicPD LCD 12.1\" SVGA"
246 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
247 color SVGA, TFT panel. The LogicPD device includes an
248 The native resolution is 800x600.
250 This panel requires a clock rate may be an integer fraction
251 of the base LCDCLK frequency. The driver will select the
252 highest frequency available that is lower than the maximum
253 allowed. The panel may flicker if the clock rate is
254 slower than the recommended minimum.
256 config FB_ARMCLCD_AUO_A070VW01_WIDE
257 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
259 This is an implementation of the AU Optronics, a 7.0"
260 WIDE Color. The native resolution is 234x480.
262 config FB_ARMCLCD_HITACHI
263 bool "Hitachi Wide Screen 800x480"
265 This is an implementation of the Hitachi 800x480.
271 bool "Acorn VIDC support"
272 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
273 select FB_CFB_FILLRECT
274 select FB_CFB_COPYAREA
275 select FB_CFB_IMAGEBLIT
277 This is the frame buffer device driver for the Acorn VIDC graphics
278 hardware found in Acorn RISC PCs and other ARM-based machines. If
282 bool "CLPS711X LCD support"
283 depends on (FB = y) && ARM && ARCH_CLPS711X
284 select FB_CFB_FILLRECT
285 select FB_CFB_COPYAREA
286 select FB_CFB_IMAGEBLIT
288 Say Y to enable the Framebuffer driver for the CLPS7111 and
292 bool "SA-1100 LCD support"
293 depends on (FB = y) && ARM && ARCH_SA1100
294 select FB_CFB_FILLRECT
295 select FB_CFB_COPYAREA
296 select FB_CFB_IMAGEBLIT
298 This is a framebuffer device for the SA-1100 LCD Controller.
299 See <http://www.linux-fbdev.org/> for information on framebuffer
302 If you plan to use the LCD display with your SA-1100 system, say
306 tristate "Motorola i.MX LCD support"
307 depends on FB && ARM && ARCH_IMX
308 select FB_CFB_FILLRECT
309 select FB_CFB_COPYAREA
310 select FB_CFB_IMAGEBLIT
313 tristate "CyberPro 2000/2010/5000 support"
314 depends on FB && PCI && (BROKEN || !SPARC64)
315 select FB_CFB_FILLRECT
316 select FB_CFB_COPYAREA
317 select FB_CFB_IMAGEBLIT
319 This enables support for the Integraphics CyberPro 20x0 and 5000
320 VGA chips used in the Rebel.com Netwinder and other machines.
321 Say Y if you have a NetWinder or a graphics card containing this
322 device, otherwise say N.
326 depends on (FB = y) && APOLLO
328 select FB_CFB_FILLRECT
329 select FB_CFB_IMAGEBLIT
333 depends on (FB = y) && Q40
335 select FB_CFB_FILLRECT
336 select FB_CFB_COPYAREA
337 select FB_CFB_IMAGEBLIT
340 tristate "Amiga native chipset support"
341 depends on FB && AMIGA
343 This is the frame buffer device driver for the builtin graphics
344 chipset found in Amigas.
346 To compile this driver as a module, choose M here: the
347 module will be called amifb.
350 bool "Amiga OCS chipset support"
353 This enables support for the original Agnus and Denise video chips,
354 found in the Amiga 1000 and most A500's and A2000's. If you intend
355 to run Linux on any of these systems, say Y; otherwise say N.
358 bool "Amiga ECS chipset support"
361 This enables support for the Enhanced Chip Set, found in later
362 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
363 you intend to run Linux on any of these systems, say Y; otherwise
367 bool "Amiga AGA chipset support"
370 This enables support for the Advanced Graphics Architecture (also
371 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
372 and CD32. If you intend to run Linux on any of these systems, say Y;
376 bool "Amiga FrameMaster II/Rainbow II support"
377 depends on (FB = y) && ZORRO
378 select FB_CFB_FILLRECT
379 select FB_CFB_COPYAREA
380 select FB_CFB_IMAGEBLIT
382 This is the frame buffer device driver for the Amiga FrameMaster
383 card from BSC (exhibited 1992 but not shipped as a CBM product).
386 tristate "Arc Monochrome LCD board support"
388 select FB_CFB_FILLRECT
389 select FB_CFB_COPYAREA
390 select FB_CFB_IMAGEBLIT
392 This enables support for the Arc Monochrome LCD board. The board
393 is based on the KS-108 lcd controller and is typically a matrix
394 of 2*n chips. This driver was tested with a 128x64 panel. This
395 driver supports it for use with x86 SBCs through a 16 bit GPIO
396 interface (8 bit data, 8 bit control). If you anticipate using
397 this driver, say Y or M; otherwise say N. You must specify the
398 GPIO IO address to be used for setting control and data.
401 bool "Atari native chipset support"
402 depends on (FB = y) && ATARI
403 select FB_CFB_FILLRECT
404 select FB_CFB_COPYAREA
405 select FB_CFB_IMAGEBLIT
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) && (!PPC_PSERIES || PCI)
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 && PPC32
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 && PPC32
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 && PPC32))
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) && PPC32
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
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/SFB+ framebuffer support"
534 depends on FB && (ALPHA || TC)
535 select FB_CFB_FILLRECT
536 select FB_CFB_COPYAREA
537 select FB_CFB_IMAGEBLIT
540 This is the frame buffer device driver for generic TGA and SFB+
541 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
542 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
543 TURBOchannel cards, also known as PMAGD-A, -B and -C.
545 Due to hardware limitations ZLX-E2 and E3 cards are not supported
546 for DECstation 5000/200 systems. Additionally due to firmware
547 limitations these cards may cause troubles with booting DECstation
548 5000/240 and /260 systems, but are fully supported under Linux if
549 you manage to get it going. ;-)
551 Say Y if you have one of those.
554 bool "VESA VGA graphics support"
555 depends on (FB = y) && X86
556 select FB_CFB_FILLRECT
557 select FB_CFB_COPYAREA
558 select FB_CFB_IMAGEBLIT
561 This is the frame buffer device driver for generic VESA 2.0
562 compliant graphic cards. The older VESA 1.2 cards are not supported.
563 You will get a boot time penguin logo at no additional cost. Please
564 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
567 bool "Intel-based Macintosh Framebuffer Support"
568 depends on (FB = y) && X86 && EFI
569 select FB_CFB_FILLRECT
570 select FB_CFB_COPYAREA
571 select FB_CFB_IMAGEBLIT
573 This is the frame buffer device driver for the Intel-based Macintosh
576 tristate "Hecuba board support"
577 depends on FB && X86 && MMU
578 select FB_CFB_FILLRECT
579 select FB_CFB_COPYAREA
580 select FB_CFB_IMAGEBLIT
581 select FB_DEFERRED_IO
583 This enables support for the Hecuba board. This driver was tested
584 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
585 interface (8 bit data, 4 bit control). If you anticpate using
586 this driver, say Y or M; otherwise say N. You must specify the
587 GPIO IO address to be used for setting control and data.
590 tristate "Hercules mono graphics support"
592 select FB_CFB_FILLRECT
593 select FB_CFB_COPYAREA
594 select FB_CFB_IMAGEBLIT
596 Say Y here if you have a Hercules mono graphics card.
598 To compile this driver as a module, choose M here: the
599 module will be called hgafb.
601 As this card technology is 15 years old, most people will answer N
605 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
606 depends on FB_HGA && EXPERIMENTAL
608 This will compile the Hercules mono graphics with
609 acceleration functions.
612 tristate "SGI Visual Workstation framebuffer support"
613 depends on FB && X86_VISWS
614 select FB_CFB_FILLRECT
615 select FB_CFB_COPYAREA
616 select FB_CFB_IMAGEBLIT
618 SGI Visual Workstation support for framebuffer graphics.
621 bool "SGI Graphics Backend frame buffer support"
622 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
623 select FB_CFB_FILLRECT
624 select FB_CFB_COPYAREA
625 select FB_CFB_IMAGEBLIT
627 This is the frame buffer device driver for SGI Graphics Backend.
628 This chip is used in SGI O2 and Visual Workstation 320/540.
631 int "Video memory size in MB"
635 This is the amount of memory reserved for the framebuffer,
636 which can be any value between 1MB and 8MB.
639 bool "SBUS and UPA framebuffers"
640 depends on (FB = y) && SPARC
642 Say Y if you want support for SBUS or UPA based frame buffer device.
646 depends on (FB = y) && (SPARC && FB_SBUS)
647 select FB_CFB_FILLRECT
648 select FB_CFB_COPYAREA
649 select FB_CFB_IMAGEBLIT
651 This is the frame buffer device driver for the BWtwo frame buffer.
654 bool "CGthree support"
655 depends on (FB = y) && (SPARC && FB_SBUS)
656 select FB_CFB_FILLRECT
657 select FB_CFB_COPYAREA
658 select FB_CFB_IMAGEBLIT
660 This is the frame buffer device driver for the CGthree frame buffer.
663 bool "CGsix (GX,TurboGX) support"
664 depends on (FB = y) && (SPARC && FB_SBUS)
665 select FB_CFB_COPYAREA
666 select FB_CFB_IMAGEBLIT
668 This is the frame buffer device driver for the CGsix (GX, TurboGX)
672 tristate "NEC PowerVR 2 display support"
673 depends on FB && SH_DREAMCAST
674 select FB_CFB_FILLRECT
675 select FB_CFB_COPYAREA
676 select FB_CFB_IMAGEBLIT
678 Say Y here if you have a PowerVR 2 card in your box. If you plan to
679 run linux on your Dreamcast, you will have to say Y here.
680 This driver may or may not work on other PowerVR 2 cards, but is
681 totally untested. Use at your own risk. If unsure, say N.
683 To compile this driver as a module, choose M here: the
684 module will be called pvr2fb.
686 You can pass several parameters to the driver at boot time or at
687 module load time. The parameters look like "video=pvr2:XXX", where
688 the meaning of XXX can be found at the end of the main source file
689 (<file:drivers/video/pvr2fb.c>). Please see the file
690 <file:Documentation/fb/pvr2fb.txt>.
693 bool "Epson 1355 framebuffer support"
694 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
695 select FB_CFB_FILLRECT
696 select FB_CFB_COPYAREA
697 select FB_CFB_IMAGEBLIT
699 Build in support for the SED1355 Epson Research Embedded RAMDAC
700 LCD/CRT Controller (since redesignated as the S1D13505) as a
701 framebuffer. Product specs at
702 <http://www.erd.epson.com/vdc/html/products.htm>.
705 tristate "Epson S1D13XXX framebuffer support"
707 select FB_CFB_FILLRECT
708 select FB_CFB_COPYAREA
709 select FB_CFB_IMAGEBLIT
711 Support for S1D13XXX framebuffer device family (currently only
712 working with S1D13806). Product specs at
713 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
716 tristate "nVidia Framebuffer Support"
718 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
719 select FB_MODE_HELPERS
720 select FB_CFB_FILLRECT
721 select FB_CFB_COPYAREA
722 select FB_CFB_IMAGEBLIT
726 This driver supports graphics boards with the nVidia chips, TNT
727 and newer. For very old chipsets, such as the RIVA128, then use
729 Say Y if you have such a graphics board.
731 To compile this driver as a module, choose M here: the
732 module will be called nvidiafb.
735 bool "Enable DDC Support"
739 This enables I2C support for nVidia Chipsets. This is used
740 only for getting EDID information from the attached display
741 allowing for robust video mode handling and switching.
743 Because fbdev-2.6 requires that drivers must be able to
744 independently validate video mode parameters, you should say Y
747 config FB_NVIDIA_BACKLIGHT
748 bool "Support for backlight control"
752 Say Y here if you want to control the backlight of your display.
755 tristate "nVidia Riva support"
757 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
758 select FB_MODE_HELPERS
759 select FB_CFB_FILLRECT
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
765 This driver supports graphics boards with the nVidia Riva/Geforce
767 Say Y if you have such a graphics board.
769 To compile this driver as a module, choose M here: the
770 module will be called rivafb.
773 bool "Enable DDC Support"
777 This enables I2C support for nVidia Chipsets. This is used
778 only for getting EDID information from the attached display
779 allowing for robust video mode handling and switching.
781 Because fbdev-2.6 requires that drivers must be able to
782 independently validate video mode parameters, you should say Y
786 bool "Lots of debug output from Riva(nVidia) driver"
790 Say Y here if you want the Riva driver to output all sorts
791 of debugging information to provide to the maintainer when
792 something goes wrong.
794 config FB_RIVA_BACKLIGHT
795 bool "Support for backlight control"
799 Say Y here if you want to control the backlight of your display.
802 tristate "Intel 810/815 support (EXPERIMENTAL)"
803 depends on FB && EXPERIMENTAL && PCI && X86_32
806 select FB_MODE_HELPERS
807 select FB_CFB_FILLRECT
808 select FB_CFB_COPYAREA
809 select FB_CFB_IMAGEBLIT
812 This driver supports the on-board graphics built in to the Intel 810
813 and 815 chipsets. Say Y if you have and plan to use such a board.
815 To compile this driver as a module, choose M here: the
816 module will be called i810fb.
818 For more information, please read
819 <file:Documentation/fb/intel810.txt>
822 bool "use VESA Generalized Timing Formula"
825 If you say Y, then the VESA standard, Generalized Timing Formula
826 or GTF, will be used to calculate the required video timing values
827 per video mode. Since the GTF allows nondiscrete timings
828 (nondiscrete being a range of values as opposed to discrete being a
829 set of values), you'll be able to use any combination of horizontal
830 and vertical resolutions, and vertical refresh rates without having
831 to specify your own timing parameters. This is especially useful
832 to maximize the performance of an aging display, or if you just
833 have a display with nonstandard dimensions. A VESA compliant
834 monitor is recommended, but can still work with non-compliant ones.
835 If you need or want this, then select this option. The timings may
836 not be compliant with Intel's recommended values. Use at your own
839 If you say N, the driver will revert to discrete video timings
840 using a set recommended by Intel in their documentation.
845 bool "Enable DDC Support"
846 depends on FB_I810 && FB_I810_GTF
851 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
852 depends on FB && EXPERIMENTAL && PCI && X86
855 select FB_MODE_HELPERS
856 select FB_CFB_FILLRECT
857 select FB_CFB_COPYAREA
858 select FB_CFB_IMAGEBLIT
860 This driver supports the on-board graphics built in to the Intel
861 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
862 Say Y if you have and plan to use such a board.
864 If you say Y here and want DDC/I2C support you must first say Y to
865 "I2C support" and "I2C bit-banging support" in the character devices
868 If you say M here then "I2C support" and "I2C bit-banging support"
869 can be build either as modules or built-in.
871 To compile this driver as a module, choose M here: the
872 module will be called intelfb.
874 For more information, please read <file:Documentation/fb/intelfb.txt>
876 config FB_INTEL_DEBUG
877 bool "Intel driver Debug Messages"
880 Say Y here if you want the Intel driver to output all sorts
881 of debugging information to provide to the maintainer when
882 something goes wrong.
885 bool "DDC/I2C for Intel framebuffer support"
890 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
893 tristate "Matrox acceleration"
895 select FB_CFB_FILLRECT
896 select FB_CFB_COPYAREA
897 select FB_CFB_IMAGEBLIT
898 select FB_TILEBLITTING
899 select FB_MACMODES if PPC_PMAC
901 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
902 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
903 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
904 Matrox G400, G450 or G550 card in your box.
906 To compile this driver as a module, choose M here: the
907 module will be called matroxfb.
909 You can pass several parameters to the driver at boot time or at
910 module load time. The parameters look like "video=matrox:XXX", and
911 are described in <file:Documentation/fb/matroxfb.txt>.
913 config FB_MATROX_MILLENIUM
914 bool "Millennium I/II support"
917 Say Y here if you have a Matrox Millennium or Matrox Millennium II
918 video card. If you select "Advanced lowlevel driver options" below,
919 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
920 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
921 also use font widths different from 8.
923 config FB_MATROX_MYSTIQUE
924 bool "Mystique support"
927 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
928 video card. If you select "Advanced lowlevel driver options" below,
929 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
930 packed pixel and 32 bpp packed pixel. You can also use font widths
934 bool "G100/G200/G400/G450/G550 support"
937 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
938 video card. If you select "Advanced lowlevel driver options", you
939 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
940 pixel and 32 bpp packed pixel. You can also use font widths
943 If you need support for G400 secondary head, you must first say Y to
944 "I2C support" in the character devices section, and then to
945 "Matrox I2C support" and "G400 second head support" here in the
946 framebuffer section. G450/G550 secondary head and digital output
947 are supported without additional modules.
949 The driver starts in monitor mode. You must use the matroxset tool
950 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
951 swap primary and secondary head outputs, or to change output mode.
952 Secondary head driver always start in 640x480 resolution and you
953 must use fbset to change it.
955 Do not forget that second head supports only 16 and 32 bpp
956 packed pixels, so it is a good idea to compile them into the kernel
957 too. You can use only some font widths, as the driver uses generic
958 painting procedures (the secondary head does not use acceleration
961 G450/G550 hardware can display TV picture only from secondary CRTC,
962 and it performs no scaling, so picture must have 525 or 625 lines.
965 tristate "Matrox I2C support"
969 This drivers creates I2C buses which are needed for accessing the
970 DDC (I2C) bus present on all Matroxes, an I2C bus which
971 interconnects Matrox optional devices, like MGA-TVO on G200 and
972 G400, and the secondary head DDC bus, present on G400 only.
974 You can say Y or M here if you want to experiment with monitor
975 detection code. You must say Y or M here if you want to use either
976 second head of G400 or MGA-TVO on G200 or G400.
978 If you compile it as module, it will create a module named
981 config FB_MATROX_MAVEN
982 tristate "G400 second head support"
983 depends on FB_MATROX_G && FB_MATROX_I2C
985 WARNING !!! This support does not work with G450 !!!
987 Say Y or M here if you want to use a secondary head (meaning two
988 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
989 head is not compatible with accelerated XFree 3.3.x SVGA servers -
990 secondary head output is blanked while you are in X. With XFree
991 3.9.17 preview you can use both heads if you use SVGA over fbdev or
992 the fbdev driver on first head and the fbdev driver on second head.
994 If you compile it as module, two modules are created,
995 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
996 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
997 also load i2c-matroxfb to get it to run.
999 The driver starts in monitor mode and you must use the matroxset
1001 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1002 PAL or NTSC or to swap primary and secondary head outputs.
1003 Secondary head driver also always start in 640x480 resolution, you
1004 must use fbset to change it.
1006 Also do not forget that second head supports only 16 and 32 bpp
1007 packed pixels, so it is a good idea to compile them into the kernel
1008 too. You can use only some font widths, as the driver uses generic
1009 painting procedures (the secondary head does not use acceleration
1012 config FB_MATROX_MULTIHEAD
1013 bool "Multihead support"
1014 depends on FB_MATROX
1016 Say Y here if you have more than one (supported) Matrox device in
1017 your computer and you want to use all of them for different monitors
1018 ("multihead"). If you have only one device, you should say N because
1019 the driver compiled with Y is larger and a bit slower, especially on
1022 If you said M to "Matrox unified accelerated driver" and N here, you
1023 will still be able to use several Matrox devices simultaneously:
1024 insert several instances of the module matroxfb into the kernel
1025 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1026 for the different Matrox devices. This method is slightly faster but
1027 uses 40 KB of kernel memory per Matrox card.
1029 There is no need for enabling 'Matrox multihead support' if you have
1030 only one Matrox card in the box.
1033 tristate "ATI Radeon display support"
1034 depends on FB && PCI
1035 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1036 select FB_MODE_HELPERS
1037 select FB_CFB_FILLRECT
1038 select FB_CFB_COPYAREA
1039 select FB_CFB_IMAGEBLIT
1040 select FB_MACMODES if PPC_OF
1042 Choose this option if you want to use an ATI Radeon graphics card as
1043 a framebuffer device. There are both PCI and AGP versions. You
1044 don't need to choose this to run the Radeon in plain VGA mode.
1046 If you say Y here and want DDC/I2C support you must first say Y to
1047 "I2C support" and "I2C bit-banging support" in the character devices
1050 If you say M here then "I2C support" and "I2C bit-banging support"
1051 can be build either as modules or built-in.
1053 There is a product page at
1054 http://apps.ati.com/ATIcompare/
1056 config FB_RADEON_I2C
1057 bool "DDC/I2C for ATI Radeon support"
1058 depends on FB_RADEON
1062 Say Y here if you want DDC/I2C support for your Radeon board.
1064 config FB_RADEON_BACKLIGHT
1065 bool "Support for backlight control"
1066 depends on FB_RADEON
1069 Say Y here if you want to control the backlight of your display.
1071 config FB_RADEON_DEBUG
1072 bool "Lots of debug output from Radeon driver"
1073 depends on FB_RADEON
1076 Say Y here if you want the Radeon driver to output all sorts
1077 of debugging information to provide to the maintainer when
1078 something goes wrong.
1081 tristate "ATI Rage128 display support"
1082 depends on FB && PCI
1083 select FB_CFB_FILLRECT
1084 select FB_CFB_COPYAREA
1085 select FB_CFB_IMAGEBLIT
1086 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1087 select FB_MACMODES if PPC_PMAC
1089 This driver supports graphics boards with the ATI Rage128 chips.
1090 Say Y if you have such a graphics board and read
1091 <file:Documentation/fb/aty128fb.txt>.
1093 To compile this driver as a module, choose M here: the
1094 module will be called aty128fb.
1096 config FB_ATY128_BACKLIGHT
1097 bool "Support for backlight control"
1098 depends on FB_ATY128
1101 Say Y here if you want to control the backlight of your display.
1104 tristate "ATI Mach64 display support" if PCI || ATARI
1105 depends on FB && !SPARC32
1106 select FB_CFB_FILLRECT
1107 select FB_CFB_COPYAREA
1108 select FB_CFB_IMAGEBLIT
1109 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1110 select FB_MACMODES if PPC
1112 This driver supports graphics boards with the ATI Mach64 chips.
1113 Say Y if you have such a graphics board.
1115 To compile this driver as a module, choose M here: the
1116 module will be called atyfb.
1119 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1120 depends on PCI && FB_ATY
1121 default y if SPARC64 && FB_PCI
1123 Say Y here to support use of ATI's 64-bit Rage boards (or other
1124 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1125 framebuffer device. The ATI product support page for these boards
1126 is at <http://support.ati.com/products/pc/mach64/>.
1128 config FB_ATY_GENERIC_LCD
1129 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1130 depends on FB_ATY_CT
1132 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1133 Rage XC, or Rage XL chipset.
1136 bool "Mach64 GX support" if PCI
1140 Say Y here to support use of the ATI Mach64 Graphics Expression
1141 board (or other boards based on the Mach64 GX chipset) as a
1142 framebuffer device. The ATI product support page for these boards
1144 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1146 config FB_ATY_BACKLIGHT
1147 bool "Support for backlight control"
1151 Say Y here if you want to control the backlight of your display.
1154 tristate "S3 Trio/Virge support"
1155 depends on FB && PCI
1156 select FB_CFB_FILLRECT
1157 select FB_CFB_COPYAREA
1158 select FB_CFB_IMAGEBLIT
1159 select FB_TILEBLITTING
1163 Driver for graphics boards with S3 Trio / S3 Virge chip.
1166 tristate "S3 Savage support"
1167 depends on FB && PCI && EXPERIMENTAL
1168 select FB_MODE_HELPERS
1169 select FB_CFB_FILLRECT
1170 select FB_CFB_COPYAREA
1171 select FB_CFB_IMAGEBLIT
1174 This driver supports notebooks and computers with S3 Savage PCI/AGP
1177 Say Y if you have such a graphics card.
1179 To compile this driver as a module, choose M here; the module
1180 will be called savagefb.
1182 config FB_SAVAGE_I2C
1183 bool "Enable DDC2 Support"
1184 depends on FB_SAVAGE
1187 This enables I2C support for S3 Savage Chipsets. This is used
1188 only for getting EDID information from the attached display
1189 allowing for robust video mode handling and switching.
1191 Because fbdev-2.6 requires that drivers must be able to
1192 independently validate video mode parameters, you should say Y
1195 config FB_SAVAGE_ACCEL
1196 bool "Enable Console Acceleration"
1197 depends on FB_SAVAGE
1200 This option will compile in console acceleration support. If
1201 the resulting framebuffer console has bothersome glitches, then
1205 tristate "SiS/XGI display support"
1206 depends on FB && PCI
1207 select FB_CFB_FILLRECT
1208 select FB_CFB_COPYAREA
1209 select FB_CFB_IMAGEBLIT
1211 This is the frame buffer device driver for the SiS 300, 315, 330
1212 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1213 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1215 To compile this driver as a module, choose M here; the module
1216 will be called sisfb.
1219 bool "SiS 300 series support"
1222 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1225 bool "SiS 315/330/340 series and XGI support"
1228 Say Y here to support use of the SiS 315, 330 and 340 series
1229 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1230 as XGI V3XT, V5, V8 and Z7.
1233 tristate "NeoMagic display support"
1234 depends on FB && PCI
1235 select FB_MODE_HELPERS
1236 select FB_CFB_FILLRECT
1237 select FB_CFB_COPYAREA
1238 select FB_CFB_IMAGEBLIT
1241 This driver supports notebooks with NeoMagic PCI chips.
1242 Say Y if you have such a graphics card.
1244 To compile this driver as a module, choose M here: the
1245 module will be called neofb.
1248 tristate "IMG Kyro support"
1249 depends on FB && PCI
1250 select FB_CFB_FILLRECT
1251 select FB_CFB_COPYAREA
1252 select FB_CFB_IMAGEBLIT
1254 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1257 To compile this driver as a module, choose M here: the
1258 module will be called kyrofb.
1261 tristate "3Dfx Banshee/Voodoo3 display support"
1262 depends on FB && PCI
1263 select FB_CFB_IMAGEBLIT
1264 select FB_CFB_FILLRECT
1265 select FB_CFB_COPYAREA
1267 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1268 chips. Say Y if you have such a graphics board.
1270 To compile this driver as a module, choose M here: the
1271 module will be called tdfxfb.
1273 config FB_3DFX_ACCEL
1274 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1275 depends on FB_3DFX && EXPERIMENTAL
1277 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1278 with acceleration functions.
1282 tristate "3Dfx Voodoo Graphics (sst1) support"
1283 depends on FB && PCI
1284 select FB_CFB_FILLRECT
1285 select FB_CFB_COPYAREA
1286 select FB_CFB_IMAGEBLIT
1288 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1289 Voodoo2 (cvg) based graphics card.
1291 To compile this driver as a module, choose M here: the
1292 module will be called sstfb.
1294 WARNING: Do not use any application that uses the 3D engine
1295 (namely glide) while using this driver.
1296 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1297 options and other important info support.
1300 tristate "Cyberblade/i1 support"
1301 depends on FB && PCI && X86_32 && !64BIT
1302 select FB_CFB_IMAGEBLIT
1305 This driver is supposed to support the Trident Cyberblade/i1
1306 graphics core integrated in the VIA VT8601A North Bridge,
1307 also known as VIA Apollo PLE133.
1310 - Developed, tested and working on EPIA 5000 and EPIA 800.
1311 - Does work reliable on all systems with CRT/LCD connected to
1313 - Should work on systems that do use the internal LCD port, but
1314 this is absolutely not tested.
1316 Character imageblit, copyarea and rectangle fill are hw accelerated,
1317 ypan scrolling is used by default.
1319 Please do read <file:Documentation/fb/cyblafb/*>.
1321 To compile this driver as a module, choose M here: the
1322 module will be called cyblafb.
1325 tristate "Trident support"
1326 depends on FB && PCI
1327 select FB_CFB_FILLRECT
1328 select FB_CFB_COPYAREA
1329 select FB_CFB_IMAGEBLIT
1331 This driver is supposed to support graphics boards with the
1332 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1333 but also on some motherboards. For more information, read
1334 <file:Documentation/fb/tridentfb.txt>
1336 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1339 Say Y if you have such a graphics board.
1342 To compile this driver as a module, choose M here: the
1343 module will be called tridentfb.
1345 config FB_TRIDENT_ACCEL
1346 bool "Trident Acceleration functions (EXPERIMENTAL)"
1347 depends on FB_TRIDENT && EXPERIMENTAL
1349 This will compile the Trident frame buffer device with
1350 acceleration functions.
1353 tristate "Permedia3 support"
1354 depends on FB && PCI && BROKEN
1356 This is the frame buffer device driver for the 3DLabs Permedia3
1357 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1358 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1359 and maybe other boards.
1362 bool "Au1100 LCD Driver"
1363 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1366 bool "Au1200 LCD Driver"
1367 depends on (FB = y) && MIPS && SOC_AU1200
1368 select FB_CFB_FILLRECT
1369 select FB_CFB_COPYAREA
1370 select FB_CFB_IMAGEBLIT
1372 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1373 various panels and CRTs by passing in kernel cmd line option
1374 au1200fb:panel=<name>.
1376 source "drivers/video/geode/Kconfig"
1379 bool "Creator/Creator3D/Elite3D support"
1380 depends on FB_SBUS && SPARC64
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1384 This is the frame buffer device driver for the Creator, Creator3D,
1385 and Elite3D graphics boards.
1388 bool "TCX (SS4/SS5 only) support"
1390 select FB_CFB_FILLRECT
1391 select FB_CFB_COPYAREA
1392 select FB_CFB_IMAGEBLIT
1394 This is the frame buffer device driver for the TCX 24/8bit frame
1398 bool "CGfourteen (SX) support"
1400 select FB_CFB_FILLRECT
1401 select FB_CFB_COPYAREA
1402 select FB_CFB_IMAGEBLIT
1404 This is the frame buffer device driver for the CGfourteen frame
1405 buffer on Desktop SPARCsystems with the SX graphics option.
1408 bool "P9100 (Sparcbook 3 only) support"
1410 select FB_CFB_FILLRECT
1411 select FB_CFB_COPYAREA
1412 select FB_CFB_IMAGEBLIT
1414 This is the frame buffer device driver for the P9100 card
1415 supported on Sparcbook 3 machines.
1418 bool "Leo (ZX) support"
1420 select FB_CFB_FILLRECT
1421 select FB_CFB_COPYAREA
1422 select FB_CFB_IMAGEBLIT
1424 This is the frame buffer device driver for the SBUS-based Sun ZX
1425 (leo) frame buffer cards.
1428 bool "Sun XVR-500 3DLABS Wildcat support"
1429 depends on FB && PCI && SPARC64
1430 select FB_CFB_FILLRECT
1431 select FB_CFB_COPYAREA
1432 select FB_CFB_IMAGEBLIT
1434 This is the framebuffer device for the Sun XVR-500 and similar
1435 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1436 only works on sparc64 systems where the system firwmare has
1437 mostly initialized the card already. It is treated as a
1438 completely dumb framebuffer device.
1441 bool "Sun XVR-2500 3DLABS Wildcat support"
1442 depends on FB && PCI && SPARC64
1443 select FB_CFB_FILLRECT
1444 select FB_CFB_COPYAREA
1445 select FB_CFB_IMAGEBLIT
1447 This is the framebuffer device for the Sun XVR-2500 and similar
1448 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1449 only works on sparc64 systems where the system firwmare has
1450 mostly initialized the card already. It is treated as a
1451 completely dumb framebuffer device.
1454 bool "PCI framebuffers"
1455 depends on (FB = y) && PCI && SPARC
1458 bool "IGA 168x display support"
1459 depends on SPARC32 && FB_PCI
1460 select FB_CFB_FILLRECT
1461 select FB_CFB_COPYAREA
1462 select FB_CFB_IMAGEBLIT
1464 This is the framebuffer device for the INTERGRAPHICS 1680 and
1465 successor frame buffer cards.
1468 tristate "HD64461 Frame Buffer support"
1469 depends on FB && HD64461
1470 select FB_CFB_FILLRECT
1471 select FB_CFB_COPYAREA
1472 select FB_CFB_IMAGEBLIT
1474 This is the frame buffer device driver for the Hitachi HD64461 LCD
1478 bool "PMAG-AA TURBOchannel framebuffer support"
1479 depends on (FB = y) && TC
1480 select FB_CFB_FILLRECT
1481 select FB_CFB_COPYAREA
1482 select FB_CFB_IMAGEBLIT
1484 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1485 used mainly in the MIPS-based DECstation series.
1488 tristate "PMAG-BA TURBOchannel framebuffer support"
1490 select FB_CFB_FILLRECT
1491 select FB_CFB_COPYAREA
1492 select FB_CFB_IMAGEBLIT
1494 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1495 used mainly in the MIPS-based DECstation series.
1498 tristate "PMAGB-B TURBOchannel framebuffer support"
1500 select FB_CFB_FILLRECT
1501 select FB_CFB_COPYAREA
1502 select FB_CFB_IMAGEBLIT
1504 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1505 in the MIPS-based DECstation series. The card is currently only
1506 supported in 1280x1024x8 mode.
1509 bool "Maxine (Personal DECstation) onboard framebuffer support"
1510 depends on (FB = y) && MACH_DECSTATION
1511 select FB_CFB_FILLRECT
1512 select FB_CFB_COPYAREA
1513 select FB_CFB_IMAGEBLIT
1515 Support for the onboard framebuffer (1024x768x8) in the Personal
1516 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1520 bool "TMPTX3912/PR31700 frame buffer support"
1521 depends on (FB = y) && NINO
1522 select FB_CFB_FILLRECT
1523 select FB_CFB_COPYAREA
1524 select FB_CFB_IMAGEBLIT
1526 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1527 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1529 Say Y here to enable kernel support for the on-board framebuffer.
1532 bool "G364 frame buffer support"
1533 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1534 select FB_CFB_FILLRECT
1535 select FB_CFB_COPYAREA
1536 select FB_CFB_IMAGEBLIT
1538 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1539 Olivetti M700-10 systems.
1542 bool "Motorola 68328 native frame buffer support"
1543 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1544 select FB_CFB_FILLRECT
1545 select FB_CFB_COPYAREA
1546 select FB_CFB_IMAGEBLIT
1548 Say Y here if you want to support the built-in frame buffer of
1549 the Motorola 68328 CPU family.
1552 tristate "PXA LCD framebuffer support"
1553 depends on FB && ARCH_PXA
1554 select FB_CFB_FILLRECT
1555 select FB_CFB_COPYAREA
1556 select FB_CFB_IMAGEBLIT
1558 Frame buffer driver for the built-in LCD controller in the Intel
1561 This driver is also available as a module ( = code which can be
1562 inserted and removed from the running kernel whenever you want). The
1563 module will be called pxafb. If you want to compile it as a module,
1564 say M here and read <file:Documentation/kbuild/modules.txt>.
1568 config FB_PXA_PARAMETERS
1569 bool "PXA LCD command line parameters"
1573 Enable the use of kernel command line or module parameters
1574 to configure the physical properties of the LCD panel when
1575 using the PXA LCD driver.
1577 This option allows you to override the panel parameters
1578 supplied by the platform in order to support multiple
1579 different models of flatpanel. If you will only be using a
1580 single model of flatpanel then you can safely leave this
1583 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1586 tristate "2700G LCD framebuffer support"
1587 depends on FB && ARCH_PXA
1588 select FB_CFB_FILLRECT
1589 select FB_CFB_COPYAREA
1590 select FB_CFB_IMAGEBLIT
1592 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1596 bool "Enable debugging info via debugfs"
1597 depends on FB_MBX && DEBUG_FS
1600 Enable this if you want debugging information using the debug
1601 filesystem (debugfs)
1606 tristate "W100 frame buffer support"
1607 depends on FB && PXA_SHARPSL
1608 select FB_CFB_FILLRECT
1609 select FB_CFB_COPYAREA
1610 select FB_CFB_IMAGEBLIT
1612 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1614 This driver is also available as a module ( = code which can be
1615 inserted and removed from the running kernel whenever you want). The
1616 module will be called w100fb. If you want to compile it as a module,
1617 say M here and read <file:Documentation/kbuild/modules.txt>.
1622 tristate "S3C2410 LCD framebuffer support"
1623 depends on FB && ARCH_S3C2410
1624 select FB_CFB_FILLRECT
1625 select FB_CFB_COPYAREA
1626 select FB_CFB_IMAGEBLIT
1628 Frame buffer driver for the built-in LCD controller in the Samsung
1631 This driver is also available as a module ( = code which can be
1632 inserted and removed from the running kernel whenever you want). The
1633 module will be called s3c2410fb. If you want to compile it as a module,
1634 say M here and read <file:Documentation/kbuild/modules.txt>.
1637 config FB_S3C2410_DEBUG
1638 bool "S3C2410 lcd debug messages"
1639 depends on FB_S3C2410
1641 Turn on debugging messages. Note that you can set/unset at run time
1645 tristate "Silicon Motion SM501 framebuffer support"
1646 depends on FB && MFD_SM501
1647 select FB_CFB_FILLRECT
1648 select FB_CFB_COPYAREA
1649 select FB_CFB_IMAGEBLIT
1651 Frame buffer driver for the CRT and LCD controllers in the Silicon
1654 This driver is also available as a module ( = code which can be
1655 inserted and removed from the running kernel whenever you want). The
1656 module will be called sm501fb. If you want to compile it as a module,
1657 say M here and read <file:Documentation/modules.txt>.
1662 config FB_PNX4008_DUM
1663 tristate "Display Update Module support on Philips PNX4008 board"
1664 depends on FB && ARCH_PNX4008
1666 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1668 config FB_PNX4008_DUM_RGB
1669 tristate "RGB Framebuffer support on Philips PNX4008 board"
1670 depends on FB_PNX4008_DUM
1671 select FB_CFB_FILLRECT
1672 select FB_CFB_COPYAREA
1673 select FB_CFB_IMAGEBLIT
1675 Say Y here to enable support for PNX4008 RGB Framebuffer
1677 config FB_IBM_GXT4500
1678 tristate "Framebuffer support for IBM GXT4500P adaptor"
1680 select FB_CFB_FILLRECT
1681 select FB_CFB_COPYAREA
1682 select FB_CFB_IMAGEBLIT
1684 Say Y here to enable support for the IBM GXT4500P display
1685 adaptor, found on some IBM System P (pSeries) machines.
1688 bool "PS3 GPU framebuffer driver"
1689 depends on (FB = y) && PS3_PS3AV
1690 select FB_CFB_FILLRECT
1691 select FB_CFB_COPYAREA
1692 select FB_CFB_IMAGEBLIT
1694 Include support for the virtual frame buffer in the PS3 platform.
1696 config FB_PS3_DEFAULT_SIZE_M
1697 int "PS3 default frame buffer size (in MiB)"
1701 This is the default size (in MiB) of the virtual frame buffer in
1703 The default value can be overridden on the kernel command line
1704 using the "ps3fb" option (e.g. "ps3fb=9M");
1707 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1709 select FB_CFB_FILLRECT
1710 select FB_CFB_COPYAREA
1711 select FB_CFB_IMAGEBLIT
1713 This is a `virtual' frame buffer device. It operates on a chunk of
1714 unswappable kernel memory instead of on the memory of a graphics
1715 board. This means you cannot see any output sent to this frame
1716 buffer device, while it does consume precious memory. The main use
1717 of this frame buffer device is testing and debugging the frame
1718 buffer subsystem. Do NOT enable it for normal systems! To protect
1719 the innocent, it has to be enabled explicitly at boot time using the
1720 kernel option `video=vfb:'.
1722 To compile this driver as a module, choose M here: the
1723 module will be called vfb. In order to load it, you must use
1724 the vfb_enable=1 option.
1729 source "drivers/video/console/Kconfig"
1732 if FB || SGI_NEWPORT_CONSOLE
1733 source "drivers/video/logo/Kconfig"