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.
98 config FB_SYS_FILLRECT
103 Include the sys_fillrect function for generic software rectangle
104 filling. This is used by drivers that don't provide their own
105 (accelerated) version and the framebuffer is in system RAM.
107 config FB_SYS_COPYAREA
112 Include the sys_copyarea function for generic software area copying.
113 This is used by drivers that don't provide their own (accelerated)
114 version and the framebuffer is in system RAM.
116 config FB_SYS_IMAGEBLIT
121 Include the sys_imageblit function for generic software image
122 blitting. This is used by drivers that don't provide their own
123 (accelerated) version and the framebuffer is in system RAM.
125 config FB_DEFERRED_IO
135 Common utility functions useful to fbdev drivers of VGA-based
146 select BACKLIGHT_LCD_SUPPORT
147 select BACKLIGHT_CLASS_DEVICE
150 config FB_MODE_HELPERS
151 bool "Enable Video Mode Handling Helpers"
155 This enables functions for handling video modes using the
156 Generalized Timing Formula and the EDID parser. A few drivers rely
157 on this feature such as the radeonfb, rivafb, and the i810fb. If
158 your driver does not take advantage of this feature, choosing Y will
159 just increase the kernel size by about 5K.
161 config FB_TILEBLITTING
162 bool "Enable Tile Blitting Support"
166 This enables tile blitting. Tile blitting is a drawing technique
167 where the screen is divided into rectangular sections (tiles), whereas
168 the standard blitting divides the screen into pixels. Because the
169 default drawing element is a tile, drawing functions will be passed
170 parameters in terms of number of tiles instead of number of pixels.
171 For example, to draw a single character, instead of using bitmaps,
172 an index to an array of bitmaps will be used. To clear or move a
173 rectangular section of a screen, the rectangle will be described in
174 terms of number of tiles in the x- and y-axis.
176 This is particularly important to one driver, matroxfb. If
179 comment "Frame buffer hardware drivers"
183 tristate "Cirrus Logic support"
184 depends on FB && (ZORRO || PCI)
185 select FB_CFB_FILLRECT
186 select FB_CFB_COPYAREA
187 select FB_CFB_IMAGEBLIT
189 This enables support for Cirrus Logic GD542x/543x based boards on
190 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
192 If you have a PCI-based system, this enables support for these
193 chips: GD-543x, GD-544x, GD-5480.
195 Please read the file <file:Documentation/fb/cirrusfb.txt>.
197 Say N unless you have such a graphics board or plan to get one
198 before you next recompile the kernel.
201 tristate "Permedia2 support"
202 depends on FB && ((AMIGA && BROKEN) || PCI)
203 select FB_CFB_FILLRECT
204 select FB_CFB_COPYAREA
205 select FB_CFB_IMAGEBLIT
207 This is the frame buffer device driver for the Permedia2 AGP frame
208 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
210 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
212 config FB_PM2_FIFO_DISCONNECT
213 bool "enable FIFO disconnect feature"
214 depends on FB_PM2 && PCI
216 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
219 tristate "ARM PrimeCell PL110 support"
220 depends on FB && ARM && ARM_AMBA
221 select FB_CFB_FILLRECT
222 select FB_CFB_COPYAREA
223 select FB_CFB_IMAGEBLIT
225 This framebuffer device driver is for the ARM PrimeCell PL110
226 Colour LCD controller. ARM PrimeCells provide the building
227 blocks for System on a Chip devices.
229 If you want to compile this as a module (=code which can be
230 inserted into and removed from the running kernel), say M
231 here and read <file:Documentation/kbuild/modules.txt>. The module
232 will be called amba-clcd.
236 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
238 default FB_ARMCLCD_SHARP_LQ035Q7DB02
240 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
241 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
243 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
244 color QVGA, HRTFT panel. The LogicPD device includes
245 an integrated HRTFT controller IC.
246 The native resolution is 240x320.
248 config FB_ARMCLCD_SHARP_LQ057Q3DC02
249 bool "LogicPD LCD 5.7\" QVGA"
251 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
252 color QVGA, TFT panel. The LogicPD device includes an
253 The native resolution is 320x240.
255 config FB_ARMCLCD_SHARP_LQ64D343
256 bool "LogicPD LCD 6.4\" VGA"
258 This is an implementation of the Sharp LQ64D343, a 6.4"
259 color VGA, TFT panel. The LogicPD device includes an
260 The native resolution is 640x480.
262 config FB_ARMCLCD_SHARP_LQ10D368
263 bool "LogicPD LCD 10.4\" VGA"
265 This is an implementation of the Sharp LQ10D368, a 10.4"
266 color VGA, TFT panel. The LogicPD device includes an
267 The native resolution is 640x480.
270 config FB_ARMCLCD_SHARP_LQ121S1DG41
271 bool "LogicPD LCD 12.1\" SVGA"
273 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
274 color SVGA, TFT panel. The LogicPD device includes an
275 The native resolution is 800x600.
277 This panel requires a clock rate may be an integer fraction
278 of the base LCDCLK frequency. The driver will select the
279 highest frequency available that is lower than the maximum
280 allowed. The panel may flicker if the clock rate is
281 slower than the recommended minimum.
283 config FB_ARMCLCD_AUO_A070VW01_WIDE
284 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
286 This is an implementation of the AU Optronics, a 7.0"
287 WIDE Color. The native resolution is 234x480.
289 config FB_ARMCLCD_HITACHI
290 bool "Hitachi Wide Screen 800x480"
292 This is an implementation of the Hitachi 800x480.
298 bool "Acorn VIDC support"
299 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
300 select FB_CFB_FILLRECT
301 select FB_CFB_COPYAREA
302 select FB_CFB_IMAGEBLIT
304 This is the frame buffer device driver for the Acorn VIDC graphics
305 hardware found in Acorn RISC PCs and other ARM-based machines. If
309 bool "CLPS711X LCD support"
310 depends on (FB = y) && ARM && ARCH_CLPS711X
311 select FB_CFB_FILLRECT
312 select FB_CFB_COPYAREA
313 select FB_CFB_IMAGEBLIT
315 Say Y to enable the Framebuffer driver for the CLPS7111 and
319 bool "SA-1100 LCD support"
320 depends on (FB = y) && ARM && ARCH_SA1100
321 select FB_CFB_FILLRECT
322 select FB_CFB_COPYAREA
323 select FB_CFB_IMAGEBLIT
325 This is a framebuffer device for the SA-1100 LCD Controller.
326 See <http://www.linux-fbdev.org/> for information on framebuffer
329 If you plan to use the LCD display with your SA-1100 system, say
333 tristate "Motorola i.MX LCD support"
334 depends on FB && ARM && ARCH_IMX
335 select FB_CFB_FILLRECT
336 select FB_CFB_COPYAREA
337 select FB_CFB_IMAGEBLIT
340 tristate "CyberPro 2000/2010/5000 support"
341 depends on FB && PCI && (BROKEN || !SPARC64)
342 select FB_CFB_FILLRECT
343 select FB_CFB_COPYAREA
344 select FB_CFB_IMAGEBLIT
346 This enables support for the Integraphics CyberPro 20x0 and 5000
347 VGA chips used in the Rebel.com Netwinder and other machines.
348 Say Y if you have a NetWinder or a graphics card containing this
349 device, otherwise say N.
353 depends on (FB = y) && APOLLO
355 select FB_CFB_FILLRECT
356 select FB_CFB_IMAGEBLIT
360 depends on (FB = y) && Q40
362 select FB_CFB_FILLRECT
363 select FB_CFB_COPYAREA
364 select FB_CFB_IMAGEBLIT
367 tristate "Amiga native chipset support"
368 depends on FB && AMIGA
370 This is the frame buffer device driver for the builtin graphics
371 chipset found in Amigas.
373 To compile this driver as a module, choose M here: the
374 module will be called amifb.
377 bool "Amiga OCS chipset support"
380 This enables support for the original Agnus and Denise video chips,
381 found in the Amiga 1000 and most A500's and A2000's. If you intend
382 to run Linux on any of these systems, say Y; otherwise say N.
385 bool "Amiga ECS chipset support"
388 This enables support for the Enhanced Chip Set, found in later
389 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
390 you intend to run Linux on any of these systems, say Y; otherwise
394 bool "Amiga AGA chipset support"
397 This enables support for the Advanced Graphics Architecture (also
398 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
399 and CD32. If you intend to run Linux on any of these systems, say Y;
403 bool "Amiga FrameMaster II/Rainbow II support"
404 depends on (FB = y) && ZORRO
405 select FB_CFB_FILLRECT
406 select FB_CFB_COPYAREA
407 select FB_CFB_IMAGEBLIT
409 This is the frame buffer device driver for the Amiga FrameMaster
410 card from BSC (exhibited 1992 but not shipped as a CBM product).
413 tristate "Arc Monochrome LCD board support"
415 select FB_SYS_FILLRECT
416 select FB_SYS_COPYAREA
417 select FB_SYS_IMAGEBLIT
419 This enables support for the Arc Monochrome LCD board. The board
420 is based on the KS-108 lcd controller and is typically a matrix
421 of 2*n chips. This driver was tested with a 128x64 panel. This
422 driver supports it for use with x86 SBCs through a 16 bit GPIO
423 interface (8 bit data, 8 bit control). If you anticipate using
424 this driver, say Y or M; otherwise say N. You must specify the
425 GPIO IO address to be used for setting control and data.
428 bool "Atari native chipset support"
429 depends on (FB = y) && ATARI
430 select FB_CFB_FILLRECT
431 select FB_CFB_COPYAREA
432 select FB_CFB_IMAGEBLIT
434 This is the frame buffer device driver for the builtin graphics
435 chipset found in Ataris.
438 bool "Open Firmware frame buffer device support"
439 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
440 select FB_CFB_FILLRECT
441 select FB_CFB_COPYAREA
442 select FB_CFB_IMAGEBLIT
445 Say Y if you want support with Open Firmware for your graphics
449 bool "Apple \"control\" display support"
450 depends on (FB = y) && PPC_PMAC && PPC32
451 select FB_CFB_FILLRECT
452 select FB_CFB_COPYAREA
453 select FB_CFB_IMAGEBLIT
456 This driver supports a frame buffer for the graphics adapter in the
457 Power Macintosh 7300 and others.
460 bool "Apple \"platinum\" display support"
461 depends on (FB = y) && PPC_PMAC && PPC32
462 select FB_CFB_FILLRECT
463 select FB_CFB_COPYAREA
464 select FB_CFB_IMAGEBLIT
467 This driver supports a frame buffer for the "platinum" graphics
468 adapter in some Power Macintoshes.
471 bool "Apple \"valkyrie\" display support"
472 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
473 select FB_CFB_FILLRECT
474 select FB_CFB_COPYAREA
475 select FB_CFB_IMAGEBLIT
478 This driver supports a frame buffer for the "valkyrie" graphics
479 adapter in some Power Macintoshes.
482 bool "Chips 65550 display support"
483 depends on (FB = y) && PPC32
484 select FB_CFB_FILLRECT
485 select FB_CFB_COPYAREA
486 select FB_CFB_IMAGEBLIT
488 This is the frame buffer device driver for the Chips & Technologies
489 65550 graphics chip in PowerBooks.
492 bool "Asiliant (Chips) 69000 display support"
493 depends on (FB = y) && PCI
494 select FB_CFB_FILLRECT
495 select FB_CFB_COPYAREA
496 select FB_CFB_IMAGEBLIT
498 This is the frame buffer device driver for the Asiliant 69030 chipset
501 bool "IMS Twin Turbo display support"
502 depends on (FB = y) && PCI
503 select FB_CFB_IMAGEBLIT
504 select FB_MACMODES if PPC
506 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
507 many Macintosh and compatible computers.
510 tristate "VGA 16-color graphics support"
511 depends on FB && (X86 || PPC)
512 select FB_CFB_FILLRECT
513 select FB_CFB_COPYAREA
514 select FB_CFB_IMAGEBLIT
517 This is the frame buffer device driver for VGA 16 color graphic
518 cards. Say Y if you have such a card.
520 To compile this driver as a module, choose M here: the
521 module will be called vga16fb.
524 tristate "HP STI frame buffer device support"
525 depends on FB && PARISC
526 select FB_CFB_FILLRECT
527 select FB_CFB_COPYAREA
528 select FB_CFB_IMAGEBLIT
531 STI refers to the HP "Standard Text Interface" which is a set of
532 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
533 Enabling this option will implement the linux framebuffer device
534 using calls to the STI BIOS routines for initialisation.
536 If you enable this option, you will get a planar framebuffer device
537 /dev/fb which will work on the most common HP graphic cards of the
538 NGLE family, including the artist chips (in the 7xx and Bxxx series),
539 HCRX, HCRX24, CRX, CRX24 and VisEG series.
541 It is safe to enable this option, so you should probably say "Y".
544 bool "Generic Macintosh display support"
545 depends on (FB = y) && MAC
546 select FB_CFB_FILLRECT
547 select FB_CFB_COPYAREA
548 select FB_CFB_IMAGEBLIT
551 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
554 depends on (FB = y) && HP300
555 select FB_CFB_FILLRECT
556 select FB_CFB_IMAGEBLIT
560 tristate "TGA/SFB+ framebuffer support"
561 depends on FB && (ALPHA || TC)
562 select FB_CFB_FILLRECT
563 select FB_CFB_COPYAREA
564 select FB_CFB_IMAGEBLIT
567 This is the frame buffer device driver for generic TGA and SFB+
568 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
569 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
570 TURBOchannel cards, also known as PMAGD-A, -B and -C.
572 Due to hardware limitations ZLX-E2 and E3 cards are not supported
573 for DECstation 5000/200 systems. Additionally due to firmware
574 limitations these cards may cause troubles with booting DECstation
575 5000/240 and /260 systems, but are fully supported under Linux if
576 you manage to get it going. ;-)
578 Say Y if you have one of those.
581 bool "VESA VGA graphics support"
582 depends on (FB = y) && X86
583 select FB_CFB_FILLRECT
584 select FB_CFB_COPYAREA
585 select FB_CFB_IMAGEBLIT
588 This is the frame buffer device driver for generic VESA 2.0
589 compliant graphic cards. The older VESA 1.2 cards are not supported.
590 You will get a boot time penguin logo at no additional cost. Please
591 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
594 bool "Intel-based Macintosh Framebuffer Support"
595 depends on (FB = y) && X86 && EFI
596 select FB_CFB_FILLRECT
597 select FB_CFB_COPYAREA
598 select FB_CFB_IMAGEBLIT
600 This is the frame buffer device driver for the Intel-based Macintosh
603 tristate "Hecuba board support"
604 depends on FB && X86 && MMU
605 select FB_SYS_FILLRECT
606 select FB_SYS_COPYAREA
607 select FB_SYS_IMAGEBLIT
608 select FB_DEFERRED_IO
610 This enables support for the Hecuba board. This driver was tested
611 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
612 interface (8 bit data, 4 bit control). If you anticpate using
613 this driver, say Y or M; otherwise say N. You must specify the
614 GPIO IO address to be used for setting control and data.
617 tristate "Hercules mono graphics support"
619 select FB_CFB_FILLRECT
620 select FB_CFB_COPYAREA
621 select FB_CFB_IMAGEBLIT
623 Say Y here if you have a Hercules mono graphics card.
625 To compile this driver as a module, choose M here: the
626 module will be called hgafb.
628 As this card technology is 15 years old, most people will answer N
632 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
633 depends on FB_HGA && EXPERIMENTAL
635 This will compile the Hercules mono graphics with
636 acceleration functions.
639 tristate "SGI Visual Workstation framebuffer support"
640 depends on FB && X86_VISWS
641 select FB_CFB_FILLRECT
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
645 SGI Visual Workstation support for framebuffer graphics.
648 bool "SGI Graphics Backend frame buffer support"
649 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
654 This is the frame buffer device driver for SGI Graphics Backend.
655 This chip is used in SGI O2 and Visual Workstation 320/540.
658 int "Video memory size in MB"
662 This is the amount of memory reserved for the framebuffer,
663 which can be any value between 1MB and 8MB.
666 bool "SBUS and UPA framebuffers"
667 depends on (FB = y) && SPARC
669 Say Y if you want support for SBUS or UPA based frame buffer device.
673 depends on (FB = y) && (SPARC && FB_SBUS)
674 select FB_CFB_FILLRECT
675 select FB_CFB_COPYAREA
676 select FB_CFB_IMAGEBLIT
678 This is the frame buffer device driver for the BWtwo frame buffer.
681 bool "CGthree support"
682 depends on (FB = y) && (SPARC && FB_SBUS)
683 select FB_CFB_FILLRECT
684 select FB_CFB_COPYAREA
685 select FB_CFB_IMAGEBLIT
687 This is the frame buffer device driver for the CGthree frame buffer.
690 bool "CGsix (GX,TurboGX) support"
691 depends on (FB = y) && (SPARC && FB_SBUS)
692 select FB_CFB_COPYAREA
693 select FB_CFB_IMAGEBLIT
695 This is the frame buffer device driver for the CGsix (GX, TurboGX)
699 tristate "NEC PowerVR 2 display support"
700 depends on FB && SH_DREAMCAST
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
705 Say Y here if you have a PowerVR 2 card in your box. If you plan to
706 run linux on your Dreamcast, you will have to say Y here.
707 This driver may or may not work on other PowerVR 2 cards, but is
708 totally untested. Use at your own risk. If unsure, say N.
710 To compile this driver as a module, choose M here: the
711 module will be called pvr2fb.
713 You can pass several parameters to the driver at boot time or at
714 module load time. The parameters look like "video=pvr2:XXX", where
715 the meaning of XXX can be found at the end of the main source file
716 (<file:drivers/video/pvr2fb.c>). Please see the file
717 <file:Documentation/fb/pvr2fb.txt>.
720 bool "Epson 1355 framebuffer support"
721 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
722 select FB_CFB_FILLRECT
723 select FB_CFB_COPYAREA
724 select FB_CFB_IMAGEBLIT
726 Build in support for the SED1355 Epson Research Embedded RAMDAC
727 LCD/CRT Controller (since redesignated as the S1D13505) as a
728 framebuffer. Product specs at
729 <http://www.erd.epson.com/vdc/html/products.htm>.
732 tristate "Epson S1D13XXX framebuffer support"
734 select FB_CFB_FILLRECT
735 select FB_CFB_COPYAREA
736 select FB_CFB_IMAGEBLIT
738 Support for S1D13XXX framebuffer device family (currently only
739 working with S1D13806). Product specs at
740 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
743 tristate "nVidia Framebuffer Support"
745 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
746 select FB_MODE_HELPERS
747 select FB_CFB_FILLRECT
748 select FB_CFB_COPYAREA
749 select FB_CFB_IMAGEBLIT
753 This driver supports graphics boards with the nVidia chips, TNT
754 and newer. For very old chipsets, such as the RIVA128, then use
756 Say Y if you have such a graphics board.
758 To compile this driver as a module, choose M here: the
759 module will be called nvidiafb.
762 bool "Enable DDC Support"
766 This enables I2C support for nVidia Chipsets. This is used
767 only for getting EDID information from the attached display
768 allowing for robust video mode handling and switching.
770 Because fbdev-2.6 requires that drivers must be able to
771 independently validate video mode parameters, you should say Y
774 config FB_NVIDIA_BACKLIGHT
775 bool "Support for backlight control"
779 Say Y here if you want to control the backlight of your display.
782 tristate "nVidia Riva support"
784 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
785 select FB_MODE_HELPERS
786 select FB_CFB_FILLRECT
787 select FB_CFB_COPYAREA
788 select FB_CFB_IMAGEBLIT
792 This driver supports graphics boards with the nVidia Riva/Geforce
794 Say Y if you have such a graphics board.
796 To compile this driver as a module, choose M here: the
797 module will be called rivafb.
800 bool "Enable DDC Support"
804 This enables I2C support for nVidia Chipsets. This is used
805 only for getting EDID information from the attached display
806 allowing for robust video mode handling and switching.
808 Because fbdev-2.6 requires that drivers must be able to
809 independently validate video mode parameters, you should say Y
813 bool "Lots of debug output from Riva(nVidia) driver"
817 Say Y here if you want the Riva driver to output all sorts
818 of debugging information to provide to the maintainer when
819 something goes wrong.
821 config FB_RIVA_BACKLIGHT
822 bool "Support for backlight control"
826 Say Y here if you want to control the backlight of your display.
829 tristate "Intel 810/815 support (EXPERIMENTAL)"
830 depends on FB && EXPERIMENTAL && PCI && X86_32
833 select FB_MODE_HELPERS
834 select FB_CFB_FILLRECT
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
839 This driver supports the on-board graphics built in to the Intel 810
840 and 815 chipsets. Say Y if you have and plan to use such a board.
842 To compile this driver as a module, choose M here: the
843 module will be called i810fb.
845 For more information, please read
846 <file:Documentation/fb/intel810.txt>
849 bool "use VESA Generalized Timing Formula"
852 If you say Y, then the VESA standard, Generalized Timing Formula
853 or GTF, will be used to calculate the required video timing values
854 per video mode. Since the GTF allows nondiscrete timings
855 (nondiscrete being a range of values as opposed to discrete being a
856 set of values), you'll be able to use any combination of horizontal
857 and vertical resolutions, and vertical refresh rates without having
858 to specify your own timing parameters. This is especially useful
859 to maximize the performance of an aging display, or if you just
860 have a display with nonstandard dimensions. A VESA compliant
861 monitor is recommended, but can still work with non-compliant ones.
862 If you need or want this, then select this option. The timings may
863 not be compliant with Intel's recommended values. Use at your own
866 If you say N, the driver will revert to discrete video timings
867 using a set recommended by Intel in their documentation.
872 bool "Enable DDC Support"
873 depends on FB_I810 && FB_I810_GTF
878 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
879 depends on FB && EXPERIMENTAL && PCI && X86
882 select FB_MODE_HELPERS
883 select FB_CFB_FILLRECT
884 select FB_CFB_COPYAREA
885 select FB_CFB_IMAGEBLIT
887 This driver supports the on-board graphics built in to the Intel
888 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
889 Say Y if you have and plan to use such a board.
891 If you say Y here and want DDC/I2C support you must first say Y to
892 "I2C support" and "I2C bit-banging support" in the character devices
895 If you say M here then "I2C support" and "I2C bit-banging support"
896 can be build either as modules or built-in.
898 To compile this driver as a module, choose M here: the
899 module will be called intelfb.
901 For more information, please read <file:Documentation/fb/intelfb.txt>
903 config FB_INTEL_DEBUG
904 bool "Intel driver Debug Messages"
907 Say Y here if you want the Intel driver to output all sorts
908 of debugging information to provide to the maintainer when
909 something goes wrong.
912 bool "DDC/I2C for Intel framebuffer support"
917 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
920 tristate "Matrox acceleration"
922 select FB_CFB_FILLRECT
923 select FB_CFB_COPYAREA
924 select FB_CFB_IMAGEBLIT
925 select FB_TILEBLITTING
926 select FB_MACMODES if PPC_PMAC
928 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
929 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
930 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
931 Matrox G400, G450 or G550 card in your box.
933 To compile this driver as a module, choose M here: the
934 module will be called matroxfb.
936 You can pass several parameters to the driver at boot time or at
937 module load time. The parameters look like "video=matrox:XXX", and
938 are described in <file:Documentation/fb/matroxfb.txt>.
940 config FB_MATROX_MILLENIUM
941 bool "Millennium I/II support"
944 Say Y here if you have a Matrox Millennium or Matrox Millennium II
945 video card. If you select "Advanced lowlevel driver options" below,
946 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
947 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
948 also use font widths different from 8.
950 config FB_MATROX_MYSTIQUE
951 bool "Mystique support"
954 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
955 video card. If you select "Advanced lowlevel driver options" below,
956 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
957 packed pixel and 32 bpp packed pixel. You can also use font widths
961 bool "G100/G200/G400/G450/G550 support"
964 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
965 video card. If you select "Advanced lowlevel driver options", you
966 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
967 pixel and 32 bpp packed pixel. You can also use font widths
970 If you need support for G400 secondary head, you must first say Y to
971 "I2C support" in the character devices section, and then to
972 "Matrox I2C support" and "G400 second head support" here in the
973 framebuffer section. G450/G550 secondary head and digital output
974 are supported without additional modules.
976 The driver starts in monitor mode. You must use the matroxset tool
977 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
978 swap primary and secondary head outputs, or to change output mode.
979 Secondary head driver always start in 640x480 resolution and you
980 must use fbset to change it.
982 Do not forget that second head supports only 16 and 32 bpp
983 packed pixels, so it is a good idea to compile them into the kernel
984 too. You can use only some font widths, as the driver uses generic
985 painting procedures (the secondary head does not use acceleration
988 G450/G550 hardware can display TV picture only from secondary CRTC,
989 and it performs no scaling, so picture must have 525 or 625 lines.
992 tristate "Matrox I2C support"
996 This drivers creates I2C buses which are needed for accessing the
997 DDC (I2C) bus present on all Matroxes, an I2C bus which
998 interconnects Matrox optional devices, like MGA-TVO on G200 and
999 G400, and the secondary head DDC bus, present on G400 only.
1001 You can say Y or M here if you want to experiment with monitor
1002 detection code. You must say Y or M here if you want to use either
1003 second head of G400 or MGA-TVO on G200 or G400.
1005 If you compile it as module, it will create a module named
1008 config FB_MATROX_MAVEN
1009 tristate "G400 second head support"
1010 depends on FB_MATROX_G && FB_MATROX_I2C
1012 WARNING !!! This support does not work with G450 !!!
1014 Say Y or M here if you want to use a secondary head (meaning two
1015 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1016 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1017 secondary head output is blanked while you are in X. With XFree
1018 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1019 the fbdev driver on first head and the fbdev driver on second head.
1021 If you compile it as module, two modules are created,
1022 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1023 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1024 also load i2c-matroxfb to get it to run.
1026 The driver starts in monitor mode and you must use the matroxset
1028 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1029 PAL or NTSC or to swap primary and secondary head outputs.
1030 Secondary head driver also always start in 640x480 resolution, you
1031 must use fbset to change it.
1033 Also do not forget that second head supports only 16 and 32 bpp
1034 packed pixels, so it is a good idea to compile them into the kernel
1035 too. You can use only some font widths, as the driver uses generic
1036 painting procedures (the secondary head does not use acceleration
1039 config FB_MATROX_MULTIHEAD
1040 bool "Multihead support"
1041 depends on FB_MATROX
1043 Say Y here if you have more than one (supported) Matrox device in
1044 your computer and you want to use all of them for different monitors
1045 ("multihead"). If you have only one device, you should say N because
1046 the driver compiled with Y is larger and a bit slower, especially on
1049 If you said M to "Matrox unified accelerated driver" and N here, you
1050 will still be able to use several Matrox devices simultaneously:
1051 insert several instances of the module matroxfb into the kernel
1052 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1053 for the different Matrox devices. This method is slightly faster but
1054 uses 40 KB of kernel memory per Matrox card.
1056 There is no need for enabling 'Matrox multihead support' if you have
1057 only one Matrox card in the box.
1060 tristate "ATI Radeon display support"
1061 depends on FB && PCI
1062 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1063 select FB_MODE_HELPERS
1064 select FB_CFB_FILLRECT
1065 select FB_CFB_COPYAREA
1066 select FB_CFB_IMAGEBLIT
1067 select FB_MACMODES if PPC_OF
1069 Choose this option if you want to use an ATI Radeon graphics card as
1070 a framebuffer device. There are both PCI and AGP versions. You
1071 don't need to choose this to run the Radeon in plain VGA mode.
1073 If you say Y here and want DDC/I2C support you must first say Y to
1074 "I2C support" and "I2C bit-banging support" in the character devices
1077 If you say M here then "I2C support" and "I2C bit-banging support"
1078 can be build either as modules or built-in.
1080 There is a product page at
1081 http://apps.ati.com/ATIcompare/
1083 config FB_RADEON_I2C
1084 bool "DDC/I2C for ATI Radeon support"
1085 depends on FB_RADEON
1089 Say Y here if you want DDC/I2C support for your Radeon board.
1091 config FB_RADEON_BACKLIGHT
1092 bool "Support for backlight control"
1093 depends on FB_RADEON
1096 Say Y here if you want to control the backlight of your display.
1098 config FB_RADEON_DEBUG
1099 bool "Lots of debug output from Radeon driver"
1100 depends on FB_RADEON
1103 Say Y here if you want the Radeon driver to output all sorts
1104 of debugging information to provide to the maintainer when
1105 something goes wrong.
1108 tristate "ATI Rage128 display support"
1109 depends on FB && PCI
1110 select FB_CFB_FILLRECT
1111 select FB_CFB_COPYAREA
1112 select FB_CFB_IMAGEBLIT
1113 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1114 select FB_MACMODES if PPC_PMAC
1116 This driver supports graphics boards with the ATI Rage128 chips.
1117 Say Y if you have such a graphics board and read
1118 <file:Documentation/fb/aty128fb.txt>.
1120 To compile this driver as a module, choose M here: the
1121 module will be called aty128fb.
1123 config FB_ATY128_BACKLIGHT
1124 bool "Support for backlight control"
1125 depends on FB_ATY128
1128 Say Y here if you want to control the backlight of your display.
1131 tristate "ATI Mach64 display support" if PCI || ATARI
1132 depends on FB && !SPARC32
1133 select FB_CFB_FILLRECT
1134 select FB_CFB_COPYAREA
1135 select FB_CFB_IMAGEBLIT
1136 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1137 select FB_MACMODES if PPC
1139 This driver supports graphics boards with the ATI Mach64 chips.
1140 Say Y if you have such a graphics board.
1142 To compile this driver as a module, choose M here: the
1143 module will be called atyfb.
1146 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1147 depends on PCI && FB_ATY
1148 default y if SPARC64 && FB_PCI
1150 Say Y here to support use of ATI's 64-bit Rage boards (or other
1151 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1152 framebuffer device. The ATI product support page for these boards
1153 is at <http://support.ati.com/products/pc/mach64/>.
1155 config FB_ATY_GENERIC_LCD
1156 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1157 depends on FB_ATY_CT
1159 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1160 Rage XC, or Rage XL chipset.
1163 bool "Mach64 GX support" if PCI
1167 Say Y here to support use of the ATI Mach64 Graphics Expression
1168 board (or other boards based on the Mach64 GX chipset) as a
1169 framebuffer device. The ATI product support page for these boards
1171 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1173 config FB_ATY_BACKLIGHT
1174 bool "Support for backlight control"
1178 Say Y here if you want to control the backlight of your display.
1181 tristate "S3 Trio/Virge support"
1182 depends on FB && PCI
1183 select FB_CFB_FILLRECT
1184 select FB_CFB_COPYAREA
1185 select FB_CFB_IMAGEBLIT
1186 select FB_TILEBLITTING
1190 Driver for graphics boards with S3 Trio / S3 Virge chip.
1193 tristate "S3 Savage support"
1194 depends on FB && PCI && EXPERIMENTAL
1195 select FB_MODE_HELPERS
1196 select FB_CFB_FILLRECT
1197 select FB_CFB_COPYAREA
1198 select FB_CFB_IMAGEBLIT
1201 This driver supports notebooks and computers with S3 Savage PCI/AGP
1204 Say Y if you have such a graphics card.
1206 To compile this driver as a module, choose M here; the module
1207 will be called savagefb.
1209 config FB_SAVAGE_I2C
1210 bool "Enable DDC2 Support"
1211 depends on FB_SAVAGE
1214 This enables I2C support for S3 Savage Chipsets. This is used
1215 only for getting EDID information from the attached display
1216 allowing for robust video mode handling and switching.
1218 Because fbdev-2.6 requires that drivers must be able to
1219 independently validate video mode parameters, you should say Y
1222 config FB_SAVAGE_ACCEL
1223 bool "Enable Console Acceleration"
1224 depends on FB_SAVAGE
1227 This option will compile in console acceleration support. If
1228 the resulting framebuffer console has bothersome glitches, then
1232 tristate "SiS/XGI display support"
1233 depends on FB && PCI
1234 select FB_CFB_FILLRECT
1235 select FB_CFB_COPYAREA
1236 select FB_CFB_IMAGEBLIT
1238 This is the frame buffer device driver for the SiS 300, 315, 330
1239 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1240 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1242 To compile this driver as a module, choose M here; the module
1243 will be called sisfb.
1246 bool "SiS 300 series support"
1249 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1252 bool "SiS 315/330/340 series and XGI support"
1255 Say Y here to support use of the SiS 315, 330 and 340 series
1256 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1257 as XGI V3XT, V5, V8 and Z7.
1260 tristate "NeoMagic display support"
1261 depends on FB && PCI
1262 select FB_MODE_HELPERS
1263 select FB_CFB_FILLRECT
1264 select FB_CFB_COPYAREA
1265 select FB_CFB_IMAGEBLIT
1268 This driver supports notebooks with NeoMagic PCI chips.
1269 Say Y if you have such a graphics card.
1271 To compile this driver as a module, choose M here: the
1272 module will be called neofb.
1275 tristate "IMG Kyro support"
1276 depends on FB && PCI
1277 select FB_CFB_FILLRECT
1278 select FB_CFB_COPYAREA
1279 select FB_CFB_IMAGEBLIT
1281 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1284 To compile this driver as a module, choose M here: the
1285 module will be called kyrofb.
1288 tristate "3Dfx Banshee/Voodoo3 display support"
1289 depends on FB && PCI
1290 select FB_CFB_IMAGEBLIT
1291 select FB_CFB_FILLRECT
1292 select FB_CFB_COPYAREA
1294 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1295 chips. Say Y if you have such a graphics board.
1297 To compile this driver as a module, choose M here: the
1298 module will be called tdfxfb.
1300 config FB_3DFX_ACCEL
1301 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1302 depends on FB_3DFX && EXPERIMENTAL
1304 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1305 with acceleration functions.
1309 tristate "3Dfx Voodoo Graphics (sst1) support"
1310 depends on FB && PCI
1311 select FB_CFB_FILLRECT
1312 select FB_CFB_COPYAREA
1313 select FB_CFB_IMAGEBLIT
1315 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1316 Voodoo2 (cvg) based graphics card.
1318 To compile this driver as a module, choose M here: the
1319 module will be called sstfb.
1321 WARNING: Do not use any application that uses the 3D engine
1322 (namely glide) while using this driver.
1323 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1324 options and other important info support.
1327 tristate "Cyberblade/i1 support"
1328 depends on FB && PCI && X86_32 && !64BIT
1329 select FB_CFB_IMAGEBLIT
1332 This driver is supposed to support the Trident Cyberblade/i1
1333 graphics core integrated in the VIA VT8601A North Bridge,
1334 also known as VIA Apollo PLE133.
1337 - Developed, tested and working on EPIA 5000 and EPIA 800.
1338 - Does work reliable on all systems with CRT/LCD connected to
1340 - Should work on systems that do use the internal LCD port, but
1341 this is absolutely not tested.
1343 Character imageblit, copyarea and rectangle fill are hw accelerated,
1344 ypan scrolling is used by default.
1346 Please do read <file:Documentation/fb/cyblafb/*>.
1348 To compile this driver as a module, choose M here: the
1349 module will be called cyblafb.
1352 tristate "Trident support"
1353 depends on FB && PCI
1354 select FB_CFB_FILLRECT
1355 select FB_CFB_COPYAREA
1356 select FB_CFB_IMAGEBLIT
1358 This driver is supposed to support graphics boards with the
1359 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1360 but also on some motherboards. For more information, read
1361 <file:Documentation/fb/tridentfb.txt>
1363 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1366 Say Y if you have such a graphics board.
1369 To compile this driver as a module, choose M here: the
1370 module will be called tridentfb.
1372 config FB_TRIDENT_ACCEL
1373 bool "Trident Acceleration functions (EXPERIMENTAL)"
1374 depends on FB_TRIDENT && EXPERIMENTAL
1376 This will compile the Trident frame buffer device with
1377 acceleration functions.
1380 tristate "Permedia3 support"
1381 depends on FB && PCI && BROKEN
1383 This is the frame buffer device driver for the 3DLabs Permedia3
1384 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1385 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1386 and maybe other boards.
1389 bool "Au1100 LCD Driver"
1390 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1393 bool "Au1200 LCD Driver"
1394 depends on (FB = y) && MIPS && SOC_AU1200
1395 select FB_CFB_FILLRECT
1396 select FB_CFB_COPYAREA
1397 select FB_CFB_IMAGEBLIT
1399 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1400 various panels and CRTs by passing in kernel cmd line option
1401 au1200fb:panel=<name>.
1403 source "drivers/video/geode/Kconfig"
1406 bool "Creator/Creator3D/Elite3D support"
1407 depends on FB_SBUS && SPARC64
1408 select FB_CFB_COPYAREA
1409 select FB_CFB_IMAGEBLIT
1411 This is the frame buffer device driver for the Creator, Creator3D,
1412 and Elite3D graphics boards.
1415 bool "TCX (SS4/SS5 only) support"
1417 select FB_CFB_FILLRECT
1418 select FB_CFB_COPYAREA
1419 select FB_CFB_IMAGEBLIT
1421 This is the frame buffer device driver for the TCX 24/8bit frame
1425 bool "CGfourteen (SX) support"
1427 select FB_CFB_FILLRECT
1428 select FB_CFB_COPYAREA
1429 select FB_CFB_IMAGEBLIT
1431 This is the frame buffer device driver for the CGfourteen frame
1432 buffer on Desktop SPARCsystems with the SX graphics option.
1435 bool "P9100 (Sparcbook 3 only) support"
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1439 select FB_CFB_IMAGEBLIT
1441 This is the frame buffer device driver for the P9100 card
1442 supported on Sparcbook 3 machines.
1445 bool "Leo (ZX) support"
1447 select FB_CFB_FILLRECT
1448 select FB_CFB_COPYAREA
1449 select FB_CFB_IMAGEBLIT
1451 This is the frame buffer device driver for the SBUS-based Sun ZX
1452 (leo) frame buffer cards.
1455 bool "Sun XVR-500 3DLABS Wildcat support"
1456 depends on FB && PCI && SPARC64
1457 select FB_CFB_FILLRECT
1458 select FB_CFB_COPYAREA
1459 select FB_CFB_IMAGEBLIT
1461 This is the framebuffer device for the Sun XVR-500 and similar
1462 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1463 only works on sparc64 systems where the system firwmare has
1464 mostly initialized the card already. It is treated as a
1465 completely dumb framebuffer device.
1468 bool "Sun XVR-2500 3DLABS Wildcat support"
1469 depends on FB && PCI && SPARC64
1470 select FB_CFB_FILLRECT
1471 select FB_CFB_COPYAREA
1472 select FB_CFB_IMAGEBLIT
1474 This is the framebuffer device for the Sun XVR-2500 and similar
1475 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1476 only works on sparc64 systems where the system firwmare has
1477 mostly initialized the card already. It is treated as a
1478 completely dumb framebuffer device.
1481 bool "PCI framebuffers"
1482 depends on (FB = y) && PCI && SPARC
1485 bool "IGA 168x display support"
1486 depends on SPARC32 && FB_PCI
1487 select FB_CFB_FILLRECT
1488 select FB_CFB_COPYAREA
1489 select FB_CFB_IMAGEBLIT
1491 This is the framebuffer device for the INTERGRAPHICS 1680 and
1492 successor frame buffer cards.
1495 tristate "HD64461 Frame Buffer support"
1496 depends on FB && HD64461
1497 select FB_CFB_FILLRECT
1498 select FB_CFB_COPYAREA
1499 select FB_CFB_IMAGEBLIT
1501 This is the frame buffer device driver for the Hitachi HD64461 LCD
1505 bool "PMAG-AA TURBOchannel framebuffer support"
1506 depends on (FB = y) && TC
1507 select FB_CFB_FILLRECT
1508 select FB_CFB_COPYAREA
1509 select FB_CFB_IMAGEBLIT
1511 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1512 used mainly in the MIPS-based DECstation series.
1515 tristate "PMAG-BA TURBOchannel framebuffer support"
1517 select FB_CFB_FILLRECT
1518 select FB_CFB_COPYAREA
1519 select FB_CFB_IMAGEBLIT
1521 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1522 used mainly in the MIPS-based DECstation series.
1525 tristate "PMAGB-B TURBOchannel framebuffer support"
1527 select FB_CFB_FILLRECT
1528 select FB_CFB_COPYAREA
1529 select FB_CFB_IMAGEBLIT
1531 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1532 in the MIPS-based DECstation series. The card is currently only
1533 supported in 1280x1024x8 mode.
1536 bool "Maxine (Personal DECstation) onboard framebuffer support"
1537 depends on (FB = y) && MACH_DECSTATION
1538 select FB_CFB_FILLRECT
1539 select FB_CFB_COPYAREA
1540 select FB_CFB_IMAGEBLIT
1542 Support for the onboard framebuffer (1024x768x8) in the Personal
1543 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1547 bool "TMPTX3912/PR31700 frame buffer support"
1548 depends on (FB = y) && NINO
1549 select FB_CFB_FILLRECT
1550 select FB_CFB_COPYAREA
1551 select FB_CFB_IMAGEBLIT
1553 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1554 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1556 Say Y here to enable kernel support for the on-board framebuffer.
1559 bool "G364 frame buffer support"
1560 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1561 select FB_CFB_FILLRECT
1562 select FB_CFB_COPYAREA
1563 select FB_CFB_IMAGEBLIT
1565 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1566 Olivetti M700-10 systems.
1569 bool "Motorola 68328 native frame buffer support"
1570 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1571 select FB_CFB_FILLRECT
1572 select FB_CFB_COPYAREA
1573 select FB_CFB_IMAGEBLIT
1575 Say Y here if you want to support the built-in frame buffer of
1576 the Motorola 68328 CPU family.
1579 tristate "PXA LCD framebuffer support"
1580 depends on FB && ARCH_PXA
1581 select FB_CFB_FILLRECT
1582 select FB_CFB_COPYAREA
1583 select FB_CFB_IMAGEBLIT
1585 Frame buffer driver for the built-in LCD controller in the Intel
1588 This driver is also available as a module ( = code which can be
1589 inserted and removed from the running kernel whenever you want). The
1590 module will be called pxafb. If you want to compile it as a module,
1591 say M here and read <file:Documentation/kbuild/modules.txt>.
1595 config FB_PXA_PARAMETERS
1596 bool "PXA LCD command line parameters"
1600 Enable the use of kernel command line or module parameters
1601 to configure the physical properties of the LCD panel when
1602 using the PXA LCD driver.
1604 This option allows you to override the panel parameters
1605 supplied by the platform in order to support multiple
1606 different models of flatpanel. If you will only be using a
1607 single model of flatpanel then you can safely leave this
1610 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1613 tristate "2700G LCD framebuffer support"
1614 depends on FB && ARCH_PXA
1615 select FB_CFB_FILLRECT
1616 select FB_CFB_COPYAREA
1617 select FB_CFB_IMAGEBLIT
1619 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1623 bool "Enable debugging info via debugfs"
1624 depends on FB_MBX && DEBUG_FS
1627 Enable this if you want debugging information using the debug
1628 filesystem (debugfs)
1633 tristate "W100 frame buffer support"
1634 depends on FB && PXA_SHARPSL
1635 select FB_CFB_FILLRECT
1636 select FB_CFB_COPYAREA
1637 select FB_CFB_IMAGEBLIT
1639 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1641 This driver is also available as a module ( = code which can be
1642 inserted and removed from the running kernel whenever you want). The
1643 module will be called w100fb. If you want to compile it as a module,
1644 say M here and read <file:Documentation/kbuild/modules.txt>.
1649 tristate "S3C2410 LCD framebuffer support"
1650 depends on FB && ARCH_S3C2410
1651 select FB_CFB_FILLRECT
1652 select FB_CFB_COPYAREA
1653 select FB_CFB_IMAGEBLIT
1655 Frame buffer driver for the built-in LCD controller in the Samsung
1658 This driver is also available as a module ( = code which can be
1659 inserted and removed from the running kernel whenever you want). The
1660 module will be called s3c2410fb. If you want to compile it as a module,
1661 say M here and read <file:Documentation/kbuild/modules.txt>.
1664 config FB_S3C2410_DEBUG
1665 bool "S3C2410 lcd debug messages"
1666 depends on FB_S3C2410
1668 Turn on debugging messages. Note that you can set/unset at run time
1672 tristate "Silicon Motion SM501 framebuffer support"
1673 depends on FB && MFD_SM501
1674 select FB_CFB_FILLRECT
1675 select FB_CFB_COPYAREA
1676 select FB_CFB_IMAGEBLIT
1678 Frame buffer driver for the CRT and LCD controllers in the Silicon
1681 This driver is also available as a module ( = code which can be
1682 inserted and removed from the running kernel whenever you want). The
1683 module will be called sm501fb. If you want to compile it as a module,
1684 say M here and read <file:Documentation/modules.txt>.
1689 config FB_PNX4008_DUM
1690 tristate "Display Update Module support on Philips PNX4008 board"
1691 depends on FB && ARCH_PNX4008
1693 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1695 config FB_PNX4008_DUM_RGB
1696 tristate "RGB Framebuffer support on Philips PNX4008 board"
1697 depends on FB_PNX4008_DUM
1698 select FB_CFB_FILLRECT
1699 select FB_CFB_COPYAREA
1700 select FB_CFB_IMAGEBLIT
1702 Say Y here to enable support for PNX4008 RGB Framebuffer
1704 config FB_IBM_GXT4500
1705 tristate "Framebuffer support for IBM GXT4500P adaptor"
1707 select FB_CFB_FILLRECT
1708 select FB_CFB_COPYAREA
1709 select FB_CFB_IMAGEBLIT
1711 Say Y here to enable support for the IBM GXT4500P display
1712 adaptor, found on some IBM System P (pSeries) machines.
1715 bool "PS3 GPU framebuffer driver"
1716 depends on (FB = y) && PS3_PS3AV
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1721 Include support for the virtual frame buffer in the PS3 platform.
1723 config FB_PS3_DEFAULT_SIZE_M
1724 int "PS3 default frame buffer size (in MiB)"
1728 This is the default size (in MiB) of the virtual frame buffer in
1730 The default value can be overridden on the kernel command line
1731 using the "ps3fb" option (e.g. "ps3fb=9M");
1734 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1736 select FB_CFB_FILLRECT
1737 select FB_CFB_COPYAREA
1738 select FB_CFB_IMAGEBLIT
1740 This is a `virtual' frame buffer device. It operates on a chunk of
1741 unswappable kernel memory instead of on the memory of a graphics
1742 board. This means you cannot see any output sent to this frame
1743 buffer device, while it does consume precious memory. The main use
1744 of this frame buffer device is testing and debugging the frame
1745 buffer subsystem. Do NOT enable it for normal systems! To protect
1746 the innocent, it has to be enabled explicitly at boot time using the
1747 kernel option `video=vfb:'.
1749 To compile this driver as a module, choose M here: the
1750 module will be called vfb. In order to load it, you must use
1751 the vfb_enable=1 option.
1756 source "drivers/video/console/Kconfig"
1759 if FB || SGI_NEWPORT_CONSOLE
1760 source "drivers/video/logo/Kconfig"