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.
130 config FB_DEFERRED_IO
140 Common utility functions useful to fbdev drivers of VGA-based
151 select BACKLIGHT_LCD_SUPPORT
152 select BACKLIGHT_CLASS_DEVICE
155 config FB_MODE_HELPERS
156 bool "Enable Video Mode Handling Helpers"
160 This enables functions for handling video modes using the
161 Generalized Timing Formula and the EDID parser. A few drivers rely
162 on this feature such as the radeonfb, rivafb, and the i810fb. If
163 your driver does not take advantage of this feature, choosing Y will
164 just increase the kernel size by about 5K.
166 config FB_TILEBLITTING
167 bool "Enable Tile Blitting Support"
171 This enables tile blitting. Tile blitting is a drawing technique
172 where the screen is divided into rectangular sections (tiles), whereas
173 the standard blitting divides the screen into pixels. Because the
174 default drawing element is a tile, drawing functions will be passed
175 parameters in terms of number of tiles instead of number of pixels.
176 For example, to draw a single character, instead of using bitmaps,
177 an index to an array of bitmaps will be used. To clear or move a
178 rectangular section of a screen, the rectangle will be described in
179 terms of number of tiles in the x- and y-axis.
181 This is particularly important to one driver, matroxfb. If
184 comment "Frame buffer hardware drivers"
188 tristate "Cirrus Logic support"
189 depends on FB && (ZORRO || PCI)
190 select FB_CFB_FILLRECT
191 select FB_CFB_COPYAREA
192 select FB_CFB_IMAGEBLIT
194 This enables support for Cirrus Logic GD542x/543x based boards on
195 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
197 If you have a PCI-based system, this enables support for these
198 chips: GD-543x, GD-544x, GD-5480.
200 Please read the file <file:Documentation/fb/cirrusfb.txt>.
202 Say N unless you have such a graphics board or plan to get one
203 before you next recompile the kernel.
206 tristate "Permedia2 support"
207 depends on FB && ((AMIGA && BROKEN) || PCI)
208 select FB_CFB_FILLRECT
209 select FB_CFB_COPYAREA
210 select FB_CFB_IMAGEBLIT
212 This is the frame buffer device driver for the Permedia2 AGP frame
213 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
215 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
217 config FB_PM2_FIFO_DISCONNECT
218 bool "enable FIFO disconnect feature"
219 depends on FB_PM2 && PCI
221 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
224 tristate "ARM PrimeCell PL110 support"
225 depends on FB && ARM && ARM_AMBA
226 select FB_CFB_FILLRECT
227 select FB_CFB_COPYAREA
228 select FB_CFB_IMAGEBLIT
230 This framebuffer device driver is for the ARM PrimeCell PL110
231 Colour LCD controller. ARM PrimeCells provide the building
232 blocks for System on a Chip devices.
234 If you want to compile this as a module (=code which can be
235 inserted into and removed from the running kernel), say M
236 here and read <file:Documentation/kbuild/modules.txt>. The module
237 will be called amba-clcd.
241 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
243 default FB_ARMCLCD_SHARP_LQ035Q7DB02
245 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
246 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
248 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
249 color QVGA, HRTFT panel. The LogicPD device includes
250 an integrated HRTFT controller IC.
251 The native resolution is 240x320.
253 config FB_ARMCLCD_SHARP_LQ057Q3DC02
254 bool "LogicPD LCD 5.7\" QVGA"
256 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
257 color QVGA, TFT panel. The LogicPD device includes an
258 The native resolution is 320x240.
260 config FB_ARMCLCD_SHARP_LQ64D343
261 bool "LogicPD LCD 6.4\" VGA"
263 This is an implementation of the Sharp LQ64D343, a 6.4"
264 color VGA, TFT panel. The LogicPD device includes an
265 The native resolution is 640x480.
267 config FB_ARMCLCD_SHARP_LQ10D368
268 bool "LogicPD LCD 10.4\" VGA"
270 This is an implementation of the Sharp LQ10D368, a 10.4"
271 color VGA, TFT panel. The LogicPD device includes an
272 The native resolution is 640x480.
275 config FB_ARMCLCD_SHARP_LQ121S1DG41
276 bool "LogicPD LCD 12.1\" SVGA"
278 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
279 color SVGA, TFT panel. The LogicPD device includes an
280 The native resolution is 800x600.
282 This panel requires a clock rate may be an integer fraction
283 of the base LCDCLK frequency. The driver will select the
284 highest frequency available that is lower than the maximum
285 allowed. The panel may flicker if the clock rate is
286 slower than the recommended minimum.
288 config FB_ARMCLCD_AUO_A070VW01_WIDE
289 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
291 This is an implementation of the AU Optronics, a 7.0"
292 WIDE Color. The native resolution is 234x480.
294 config FB_ARMCLCD_HITACHI
295 bool "Hitachi Wide Screen 800x480"
297 This is an implementation of the Hitachi 800x480.
303 bool "Acorn VIDC support"
304 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
305 select FB_CFB_FILLRECT
306 select FB_CFB_COPYAREA
307 select FB_CFB_IMAGEBLIT
309 This is the frame buffer device driver for the Acorn VIDC graphics
310 hardware found in Acorn RISC PCs and other ARM-based machines. If
314 bool "CLPS711X LCD support"
315 depends on (FB = y) && ARM && ARCH_CLPS711X
316 select FB_CFB_FILLRECT
317 select FB_CFB_COPYAREA
318 select FB_CFB_IMAGEBLIT
320 Say Y to enable the Framebuffer driver for the CLPS7111 and
324 bool "SA-1100 LCD support"
325 depends on (FB = y) && ARM && ARCH_SA1100
326 select FB_CFB_FILLRECT
327 select FB_CFB_COPYAREA
328 select FB_CFB_IMAGEBLIT
330 This is a framebuffer device for the SA-1100 LCD Controller.
331 See <http://www.linux-fbdev.org/> for information on framebuffer
334 If you plan to use the LCD display with your SA-1100 system, say
338 tristate "Motorola i.MX LCD support"
339 depends on FB && ARM && ARCH_IMX
340 select FB_CFB_FILLRECT
341 select FB_CFB_COPYAREA
342 select FB_CFB_IMAGEBLIT
345 tristate "CyberPro 2000/2010/5000 support"
346 depends on FB && PCI && (BROKEN || !SPARC64)
347 select FB_CFB_FILLRECT
348 select FB_CFB_COPYAREA
349 select FB_CFB_IMAGEBLIT
351 This enables support for the Integraphics CyberPro 20x0 and 5000
352 VGA chips used in the Rebel.com Netwinder and other machines.
353 Say Y if you have a NetWinder or a graphics card containing this
354 device, otherwise say N.
358 depends on (FB = y) && APOLLO
360 select FB_CFB_FILLRECT
361 select FB_CFB_IMAGEBLIT
365 depends on (FB = y) && Q40
367 select FB_CFB_FILLRECT
368 select FB_CFB_COPYAREA
369 select FB_CFB_IMAGEBLIT
372 tristate "Amiga native chipset support"
373 depends on FB && AMIGA
375 This is the frame buffer device driver for the builtin graphics
376 chipset found in Amigas.
378 To compile this driver as a module, choose M here: the
379 module will be called amifb.
382 bool "Amiga OCS chipset support"
385 This enables support for the original Agnus and Denise video chips,
386 found in the Amiga 1000 and most A500's and A2000's. If you intend
387 to run Linux on any of these systems, say Y; otherwise say N.
390 bool "Amiga ECS chipset support"
393 This enables support for the Enhanced Chip Set, found in later
394 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
395 you intend to run Linux on any of these systems, say Y; otherwise
399 bool "Amiga AGA chipset support"
402 This enables support for the Advanced Graphics Architecture (also
403 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
404 and CD32. If you intend to run Linux on any of these systems, say Y;
408 bool "Amiga FrameMaster II/Rainbow II support"
409 depends on (FB = y) && ZORRO
410 select FB_CFB_FILLRECT
411 select FB_CFB_COPYAREA
412 select FB_CFB_IMAGEBLIT
414 This is the frame buffer device driver for the Amiga FrameMaster
415 card from BSC (exhibited 1992 but not shipped as a CBM product).
418 tristate "Arc Monochrome LCD board support"
420 select FB_SYS_FILLRECT
421 select FB_SYS_COPYAREA
422 select FB_SYS_IMAGEBLIT
425 This enables support for the Arc Monochrome LCD board. The board
426 is based on the KS-108 lcd controller and is typically a matrix
427 of 2*n chips. This driver was tested with a 128x64 panel. This
428 driver supports it for use with x86 SBCs through a 16 bit GPIO
429 interface (8 bit data, 8 bit control). If you anticipate using
430 this driver, say Y or M; otherwise say N. You must specify the
431 GPIO IO address to be used for setting control and data.
434 bool "Atari native chipset support"
435 depends on (FB = y) && ATARI
436 select FB_CFB_FILLRECT
437 select FB_CFB_COPYAREA
438 select FB_CFB_IMAGEBLIT
440 This is the frame buffer device driver for the builtin graphics
441 chipset found in Ataris.
444 bool "Open Firmware frame buffer device support"
445 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
446 select FB_CFB_FILLRECT
447 select FB_CFB_COPYAREA
448 select FB_CFB_IMAGEBLIT
451 Say Y if you want support with Open Firmware for your graphics
455 bool "Apple \"control\" display support"
456 depends on (FB = y) && PPC_PMAC && PPC32
457 select FB_CFB_FILLRECT
458 select FB_CFB_COPYAREA
459 select FB_CFB_IMAGEBLIT
462 This driver supports a frame buffer for the graphics adapter in the
463 Power Macintosh 7300 and others.
466 bool "Apple \"platinum\" display support"
467 depends on (FB = y) && PPC_PMAC && PPC32
468 select FB_CFB_FILLRECT
469 select FB_CFB_COPYAREA
470 select FB_CFB_IMAGEBLIT
473 This driver supports a frame buffer for the "platinum" graphics
474 adapter in some Power Macintoshes.
477 bool "Apple \"valkyrie\" display support"
478 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
479 select FB_CFB_FILLRECT
480 select FB_CFB_COPYAREA
481 select FB_CFB_IMAGEBLIT
484 This driver supports a frame buffer for the "valkyrie" graphics
485 adapter in some Power Macintoshes.
488 bool "Chips 65550 display support"
489 depends on (FB = y) && PPC32
490 select FB_CFB_FILLRECT
491 select FB_CFB_COPYAREA
492 select FB_CFB_IMAGEBLIT
494 This is the frame buffer device driver for the Chips & Technologies
495 65550 graphics chip in PowerBooks.
498 bool "Asiliant (Chips) 69000 display support"
499 depends on (FB = y) && PCI
500 select FB_CFB_FILLRECT
501 select FB_CFB_COPYAREA
502 select FB_CFB_IMAGEBLIT
504 This is the frame buffer device driver for the Asiliant 69030 chipset
507 bool "IMS Twin Turbo display support"
508 depends on (FB = y) && PCI
509 select FB_CFB_IMAGEBLIT
510 select FB_MACMODES if PPC
512 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
513 many Macintosh and compatible computers.
516 tristate "VGA 16-color graphics support"
517 depends on FB && (X86 || PPC)
518 select FB_CFB_FILLRECT
519 select FB_CFB_COPYAREA
520 select FB_CFB_IMAGEBLIT
523 This is the frame buffer device driver for VGA 16 color graphic
524 cards. Say Y if you have such a card.
526 To compile this driver as a module, choose M here: the
527 module will be called vga16fb.
530 tristate "HP STI frame buffer device support"
531 depends on FB && PARISC
532 select FB_CFB_FILLRECT
533 select FB_CFB_COPYAREA
534 select FB_CFB_IMAGEBLIT
537 STI refers to the HP "Standard Text Interface" which is a set of
538 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
539 Enabling this option will implement the linux framebuffer device
540 using calls to the STI BIOS routines for initialisation.
542 If you enable this option, you will get a planar framebuffer device
543 /dev/fb which will work on the most common HP graphic cards of the
544 NGLE family, including the artist chips (in the 7xx and Bxxx series),
545 HCRX, HCRX24, CRX, CRX24 and VisEG series.
547 It is safe to enable this option, so you should probably say "Y".
550 bool "Generic Macintosh display support"
551 depends on (FB = y) && MAC
552 select FB_CFB_FILLRECT
553 select FB_CFB_COPYAREA
554 select FB_CFB_IMAGEBLIT
557 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
560 depends on (FB = y) && HP300
561 select FB_CFB_FILLRECT
562 select FB_CFB_IMAGEBLIT
566 tristate "TGA/SFB+ framebuffer support"
567 depends on FB && (ALPHA || TC)
568 select FB_CFB_FILLRECT
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
573 This is the frame buffer device driver for generic TGA and SFB+
574 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
575 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
576 TURBOchannel cards, also known as PMAGD-A, -B and -C.
578 Due to hardware limitations ZLX-E2 and E3 cards are not supported
579 for DECstation 5000/200 systems. Additionally due to firmware
580 limitations these cards may cause troubles with booting DECstation
581 5000/240 and /260 systems, but are fully supported under Linux if
582 you manage to get it going. ;-)
584 Say Y if you have one of those.
587 bool "VESA VGA graphics support"
588 depends on (FB = y) && X86
589 select FB_CFB_FILLRECT
590 select FB_CFB_COPYAREA
591 select FB_CFB_IMAGEBLIT
594 This is the frame buffer device driver for generic VESA 2.0
595 compliant graphic cards. The older VESA 1.2 cards are not supported.
596 You will get a boot time penguin logo at no additional cost. Please
597 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
600 bool "Intel-based Macintosh Framebuffer Support"
601 depends on (FB = y) && X86 && EFI
602 select FB_CFB_FILLRECT
603 select FB_CFB_COPYAREA
604 select FB_CFB_IMAGEBLIT
606 This is the frame buffer device driver for the Intel-based Macintosh
609 tristate "Hecuba board support"
610 depends on FB && X86 && MMU
611 select FB_SYS_FILLRECT
612 select FB_SYS_COPYAREA
613 select FB_SYS_IMAGEBLIT
614 select FB_DEFERRED_IO
616 This enables support for the Hecuba board. This driver was tested
617 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
618 interface (8 bit data, 4 bit control). If you anticpate using
619 this driver, say Y or M; otherwise say N. You must specify the
620 GPIO IO address to be used for setting control and data.
623 tristate "Hercules mono graphics support"
625 select FB_CFB_FILLRECT
626 select FB_CFB_COPYAREA
627 select FB_CFB_IMAGEBLIT
629 Say Y here if you have a Hercules mono graphics card.
631 To compile this driver as a module, choose M here: the
632 module will be called hgafb.
634 As this card technology is 15 years old, most people will answer N
638 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
639 depends on FB_HGA && EXPERIMENTAL
641 This will compile the Hercules mono graphics with
642 acceleration functions.
645 tristate "SGI Visual Workstation framebuffer support"
646 depends on FB && X86_VISWS
647 select FB_CFB_FILLRECT
648 select FB_CFB_COPYAREA
649 select FB_CFB_IMAGEBLIT
651 SGI Visual Workstation support for framebuffer graphics.
654 bool "SGI Graphics Backend frame buffer support"
655 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
656 select FB_CFB_FILLRECT
657 select FB_CFB_COPYAREA
658 select FB_CFB_IMAGEBLIT
660 This is the frame buffer device driver for SGI Graphics Backend.
661 This chip is used in SGI O2 and Visual Workstation 320/540.
664 int "Video memory size in MB"
668 This is the amount of memory reserved for the framebuffer,
669 which can be any value between 1MB and 8MB.
672 bool "SBUS and UPA framebuffers"
673 depends on (FB = y) && SPARC
675 Say Y if you want support for SBUS or UPA based frame buffer device.
679 depends on (FB = y) && (SPARC && FB_SBUS)
680 select FB_CFB_FILLRECT
681 select FB_CFB_COPYAREA
682 select FB_CFB_IMAGEBLIT
684 This is the frame buffer device driver for the BWtwo frame buffer.
687 bool "CGthree support"
688 depends on (FB = y) && (SPARC && FB_SBUS)
689 select FB_CFB_FILLRECT
690 select FB_CFB_COPYAREA
691 select FB_CFB_IMAGEBLIT
693 This is the frame buffer device driver for the CGthree frame buffer.
696 bool "CGsix (GX,TurboGX) support"
697 depends on (FB = y) && (SPARC && FB_SBUS)
698 select FB_CFB_COPYAREA
699 select FB_CFB_IMAGEBLIT
701 This is the frame buffer device driver for the CGsix (GX, TurboGX)
705 tristate "NEC PowerVR 2 display support"
706 depends on FB && SH_DREAMCAST
707 select FB_CFB_FILLRECT
708 select FB_CFB_COPYAREA
709 select FB_CFB_IMAGEBLIT
711 Say Y here if you have a PowerVR 2 card in your box. If you plan to
712 run linux on your Dreamcast, you will have to say Y here.
713 This driver may or may not work on other PowerVR 2 cards, but is
714 totally untested. Use at your own risk. If unsure, say N.
716 To compile this driver as a module, choose M here: the
717 module will be called pvr2fb.
719 You can pass several parameters to the driver at boot time or at
720 module load time. The parameters look like "video=pvr2:XXX", where
721 the meaning of XXX can be found at the end of the main source file
722 (<file:drivers/video/pvr2fb.c>). Please see the file
723 <file:Documentation/fb/pvr2fb.txt>.
726 bool "Epson 1355 framebuffer support"
727 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
728 select FB_CFB_FILLRECT
729 select FB_CFB_COPYAREA
730 select FB_CFB_IMAGEBLIT
732 Build in support for the SED1355 Epson Research Embedded RAMDAC
733 LCD/CRT Controller (since redesignated as the S1D13505) as a
734 framebuffer. Product specs at
735 <http://www.erd.epson.com/vdc/html/products.htm>.
738 tristate "Epson S1D13XXX framebuffer support"
740 select FB_CFB_FILLRECT
741 select FB_CFB_COPYAREA
742 select FB_CFB_IMAGEBLIT
744 Support for S1D13XXX framebuffer device family (currently only
745 working with S1D13806). Product specs at
746 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
749 tristate "nVidia Framebuffer Support"
751 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
752 select FB_MODE_HELPERS
753 select FB_CFB_FILLRECT
754 select FB_CFB_COPYAREA
755 select FB_CFB_IMAGEBLIT
759 This driver supports graphics boards with the nVidia chips, TNT
760 and newer. For very old chipsets, such as the RIVA128, then use
762 Say Y if you have such a graphics board.
764 To compile this driver as a module, choose M here: the
765 module will be called nvidiafb.
768 bool "Enable DDC Support"
772 This enables I2C support for nVidia Chipsets. This is used
773 only for getting EDID information from the attached display
774 allowing for robust video mode handling and switching.
776 Because fbdev-2.6 requires that drivers must be able to
777 independently validate video mode parameters, you should say Y
780 config FB_NVIDIA_BACKLIGHT
781 bool "Support for backlight control"
785 Say Y here if you want to control the backlight of your display.
788 tristate "nVidia Riva support"
790 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
791 select FB_MODE_HELPERS
792 select FB_CFB_FILLRECT
793 select FB_CFB_COPYAREA
794 select FB_CFB_IMAGEBLIT
798 This driver supports graphics boards with the nVidia Riva/Geforce
800 Say Y if you have such a graphics board.
802 To compile this driver as a module, choose M here: the
803 module will be called rivafb.
806 bool "Enable DDC Support"
810 This enables I2C support for nVidia Chipsets. This is used
811 only for getting EDID information from the attached display
812 allowing for robust video mode handling and switching.
814 Because fbdev-2.6 requires that drivers must be able to
815 independently validate video mode parameters, you should say Y
819 bool "Lots of debug output from Riva(nVidia) driver"
823 Say Y here if you want the Riva driver to output all sorts
824 of debugging information to provide to the maintainer when
825 something goes wrong.
827 config FB_RIVA_BACKLIGHT
828 bool "Support for backlight control"
832 Say Y here if you want to control the backlight of your display.
835 tristate "Intel 810/815 support (EXPERIMENTAL)"
836 depends on FB && EXPERIMENTAL && PCI && X86_32
839 select FB_MODE_HELPERS
840 select FB_CFB_FILLRECT
841 select FB_CFB_COPYAREA
842 select FB_CFB_IMAGEBLIT
845 This driver supports the on-board graphics built in to the Intel 810
846 and 815 chipsets. Say Y if you have and plan to use such a board.
848 To compile this driver as a module, choose M here: the
849 module will be called i810fb.
851 For more information, please read
852 <file:Documentation/fb/intel810.txt>
855 bool "use VESA Generalized Timing Formula"
858 If you say Y, then the VESA standard, Generalized Timing Formula
859 or GTF, will be used to calculate the required video timing values
860 per video mode. Since the GTF allows nondiscrete timings
861 (nondiscrete being a range of values as opposed to discrete being a
862 set of values), you'll be able to use any combination of horizontal
863 and vertical resolutions, and vertical refresh rates without having
864 to specify your own timing parameters. This is especially useful
865 to maximize the performance of an aging display, or if you just
866 have a display with nonstandard dimensions. A VESA compliant
867 monitor is recommended, but can still work with non-compliant ones.
868 If you need or want this, then select this option. The timings may
869 not be compliant with Intel's recommended values. Use at your own
872 If you say N, the driver will revert to discrete video timings
873 using a set recommended by Intel in their documentation.
878 bool "Enable DDC Support"
879 depends on FB_I810 && FB_I810_GTF
884 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
885 depends on FB && EXPERIMENTAL && PCI && X86
888 select FB_MODE_HELPERS
889 select FB_CFB_FILLRECT
890 select FB_CFB_COPYAREA
891 select FB_CFB_IMAGEBLIT
893 This driver supports the on-board graphics built in to the Intel
894 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
895 Say Y if you have and plan to use such a board.
897 If you say Y here and want DDC/I2C support you must first say Y to
898 "I2C support" and "I2C bit-banging support" in the character devices
901 If you say M here then "I2C support" and "I2C bit-banging support"
902 can be build either as modules or built-in.
904 To compile this driver as a module, choose M here: the
905 module will be called intelfb.
907 For more information, please read <file:Documentation/fb/intelfb.txt>
909 config FB_INTEL_DEBUG
910 bool "Intel driver Debug Messages"
913 Say Y here if you want the Intel driver to output all sorts
914 of debugging information to provide to the maintainer when
915 something goes wrong.
918 bool "DDC/I2C for Intel framebuffer support"
923 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
926 tristate "Matrox acceleration"
928 select FB_CFB_FILLRECT
929 select FB_CFB_COPYAREA
930 select FB_CFB_IMAGEBLIT
931 select FB_TILEBLITTING
932 select FB_MACMODES if PPC_PMAC
934 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
935 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
936 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
937 Matrox G400, G450 or G550 card in your box.
939 To compile this driver as a module, choose M here: the
940 module will be called matroxfb.
942 You can pass several parameters to the driver at boot time or at
943 module load time. The parameters look like "video=matrox:XXX", and
944 are described in <file:Documentation/fb/matroxfb.txt>.
946 config FB_MATROX_MILLENIUM
947 bool "Millennium I/II support"
950 Say Y here if you have a Matrox Millennium or Matrox Millennium II
951 video card. If you select "Advanced lowlevel driver options" below,
952 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
953 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
954 also use font widths different from 8.
956 config FB_MATROX_MYSTIQUE
957 bool "Mystique support"
960 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
961 video card. If you select "Advanced lowlevel driver options" below,
962 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
963 packed pixel and 32 bpp packed pixel. You can also use font widths
967 bool "G100/G200/G400/G450/G550 support"
970 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
971 video card. If you select "Advanced lowlevel driver options", you
972 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
973 pixel and 32 bpp packed pixel. You can also use font widths
976 If you need support for G400 secondary head, you must first say Y to
977 "I2C support" in the character devices section, and then to
978 "Matrox I2C support" and "G400 second head support" here in the
979 framebuffer section. G450/G550 secondary head and digital output
980 are supported without additional modules.
982 The driver starts in monitor mode. You must use the matroxset tool
983 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
984 swap primary and secondary head outputs, or to change output mode.
985 Secondary head driver always start in 640x480 resolution and you
986 must use fbset to change it.
988 Do not forget that second head supports only 16 and 32 bpp
989 packed pixels, so it is a good idea to compile them into the kernel
990 too. You can use only some font widths, as the driver uses generic
991 painting procedures (the secondary head does not use acceleration
994 G450/G550 hardware can display TV picture only from secondary CRTC,
995 and it performs no scaling, so picture must have 525 or 625 lines.
998 tristate "Matrox I2C support"
1002 This drivers creates I2C buses which are needed for accessing the
1003 DDC (I2C) bus present on all Matroxes, an I2C bus which
1004 interconnects Matrox optional devices, like MGA-TVO on G200 and
1005 G400, and the secondary head DDC bus, present on G400 only.
1007 You can say Y or M here if you want to experiment with monitor
1008 detection code. You must say Y or M here if you want to use either
1009 second head of G400 or MGA-TVO on G200 or G400.
1011 If you compile it as module, it will create a module named
1014 config FB_MATROX_MAVEN
1015 tristate "G400 second head support"
1016 depends on FB_MATROX_G && FB_MATROX_I2C
1018 WARNING !!! This support does not work with G450 !!!
1020 Say Y or M here if you want to use a secondary head (meaning two
1021 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1022 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1023 secondary head output is blanked while you are in X. With XFree
1024 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1025 the fbdev driver on first head and the fbdev driver on second head.
1027 If you compile it as module, two modules are created,
1028 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1029 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1030 also load i2c-matroxfb to get it to run.
1032 The driver starts in monitor mode and you must use the matroxset
1034 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1035 PAL or NTSC or to swap primary and secondary head outputs.
1036 Secondary head driver also always start in 640x480 resolution, you
1037 must use fbset to change it.
1039 Also do not forget that second head supports only 16 and 32 bpp
1040 packed pixels, so it is a good idea to compile them into the kernel
1041 too. You can use only some font widths, as the driver uses generic
1042 painting procedures (the secondary head does not use acceleration
1045 config FB_MATROX_MULTIHEAD
1046 bool "Multihead support"
1047 depends on FB_MATROX
1049 Say Y here if you have more than one (supported) Matrox device in
1050 your computer and you want to use all of them for different monitors
1051 ("multihead"). If you have only one device, you should say N because
1052 the driver compiled with Y is larger and a bit slower, especially on
1055 If you said M to "Matrox unified accelerated driver" and N here, you
1056 will still be able to use several Matrox devices simultaneously:
1057 insert several instances of the module matroxfb into the kernel
1058 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1059 for the different Matrox devices. This method is slightly faster but
1060 uses 40 KB of kernel memory per Matrox card.
1062 There is no need for enabling 'Matrox multihead support' if you have
1063 only one Matrox card in the box.
1066 tristate "ATI Radeon display support"
1067 depends on FB && PCI
1068 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1069 select FB_MODE_HELPERS
1070 select FB_CFB_FILLRECT
1071 select FB_CFB_COPYAREA
1072 select FB_CFB_IMAGEBLIT
1073 select FB_MACMODES if PPC_OF
1075 Choose this option if you want to use an ATI Radeon graphics card as
1076 a framebuffer device. There are both PCI and AGP versions. You
1077 don't need to choose this to run the Radeon in plain VGA mode.
1079 If you say Y here and want DDC/I2C support you must first say Y to
1080 "I2C support" and "I2C bit-banging support" in the character devices
1083 If you say M here then "I2C support" and "I2C bit-banging support"
1084 can be build either as modules or built-in.
1086 There is a product page at
1087 http://apps.ati.com/ATIcompare/
1089 config FB_RADEON_I2C
1090 bool "DDC/I2C for ATI Radeon support"
1091 depends on FB_RADEON
1095 Say Y here if you want DDC/I2C support for your Radeon board.
1097 config FB_RADEON_BACKLIGHT
1098 bool "Support for backlight control"
1099 depends on FB_RADEON
1102 Say Y here if you want to control the backlight of your display.
1104 config FB_RADEON_DEBUG
1105 bool "Lots of debug output from Radeon driver"
1106 depends on FB_RADEON
1109 Say Y here if you want the Radeon driver to output all sorts
1110 of debugging information to provide to the maintainer when
1111 something goes wrong.
1114 tristate "ATI Rage128 display support"
1115 depends on FB && PCI
1116 select FB_CFB_FILLRECT
1117 select FB_CFB_COPYAREA
1118 select FB_CFB_IMAGEBLIT
1119 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1120 select FB_MACMODES if PPC_PMAC
1122 This driver supports graphics boards with the ATI Rage128 chips.
1123 Say Y if you have such a graphics board and read
1124 <file:Documentation/fb/aty128fb.txt>.
1126 To compile this driver as a module, choose M here: the
1127 module will be called aty128fb.
1129 config FB_ATY128_BACKLIGHT
1130 bool "Support for backlight control"
1131 depends on FB_ATY128
1134 Say Y here if you want to control the backlight of your display.
1137 tristate "ATI Mach64 display support" if PCI || ATARI
1138 depends on FB && !SPARC32
1139 select FB_CFB_FILLRECT
1140 select FB_CFB_COPYAREA
1141 select FB_CFB_IMAGEBLIT
1142 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1143 select FB_MACMODES if PPC
1145 This driver supports graphics boards with the ATI Mach64 chips.
1146 Say Y if you have such a graphics board.
1148 To compile this driver as a module, choose M here: the
1149 module will be called atyfb.
1152 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1153 depends on PCI && FB_ATY
1154 default y if SPARC64 && FB_PCI
1156 Say Y here to support use of ATI's 64-bit Rage boards (or other
1157 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1158 framebuffer device. The ATI product support page for these boards
1159 is at <http://support.ati.com/products/pc/mach64/>.
1161 config FB_ATY_GENERIC_LCD
1162 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1163 depends on FB_ATY_CT
1165 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1166 Rage XC, or Rage XL chipset.
1169 bool "Mach64 GX support" if PCI
1173 Say Y here to support use of the ATI Mach64 Graphics Expression
1174 board (or other boards based on the Mach64 GX chipset) as a
1175 framebuffer device. The ATI product support page for these boards
1177 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1179 config FB_ATY_BACKLIGHT
1180 bool "Support for backlight control"
1184 Say Y here if you want to control the backlight of your display.
1187 tristate "S3 Trio/Virge support"
1188 depends on FB && PCI
1189 select FB_CFB_FILLRECT
1190 select FB_CFB_COPYAREA
1191 select FB_CFB_IMAGEBLIT
1192 select FB_TILEBLITTING
1196 Driver for graphics boards with S3 Trio / S3 Virge chip.
1199 tristate "S3 Savage support"
1200 depends on FB && PCI && EXPERIMENTAL
1201 select FB_MODE_HELPERS
1202 select FB_CFB_FILLRECT
1203 select FB_CFB_COPYAREA
1204 select FB_CFB_IMAGEBLIT
1207 This driver supports notebooks and computers with S3 Savage PCI/AGP
1210 Say Y if you have such a graphics card.
1212 To compile this driver as a module, choose M here; the module
1213 will be called savagefb.
1215 config FB_SAVAGE_I2C
1216 bool "Enable DDC2 Support"
1217 depends on FB_SAVAGE
1220 This enables I2C support for S3 Savage Chipsets. This is used
1221 only for getting EDID information from the attached display
1222 allowing for robust video mode handling and switching.
1224 Because fbdev-2.6 requires that drivers must be able to
1225 independently validate video mode parameters, you should say Y
1228 config FB_SAVAGE_ACCEL
1229 bool "Enable Console Acceleration"
1230 depends on FB_SAVAGE
1233 This option will compile in console acceleration support. If
1234 the resulting framebuffer console has bothersome glitches, then
1238 tristate "SiS/XGI display support"
1239 depends on FB && PCI
1240 select FB_CFB_FILLRECT
1241 select FB_CFB_COPYAREA
1242 select FB_CFB_IMAGEBLIT
1244 This is the frame buffer device driver for the SiS 300, 315, 330
1245 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1246 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1248 To compile this driver as a module, choose M here; the module
1249 will be called sisfb.
1252 bool "SiS 300 series support"
1255 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1258 bool "SiS 315/330/340 series and XGI support"
1261 Say Y here to support use of the SiS 315, 330 and 340 series
1262 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1263 as XGI V3XT, V5, V8 and Z7.
1266 tristate "NeoMagic display support"
1267 depends on FB && PCI
1268 select FB_MODE_HELPERS
1269 select FB_CFB_FILLRECT
1270 select FB_CFB_COPYAREA
1271 select FB_CFB_IMAGEBLIT
1274 This driver supports notebooks with NeoMagic PCI chips.
1275 Say Y if you have such a graphics card.
1277 To compile this driver as a module, choose M here: the
1278 module will be called neofb.
1281 tristate "IMG Kyro support"
1282 depends on FB && PCI
1283 select FB_CFB_FILLRECT
1284 select FB_CFB_COPYAREA
1285 select FB_CFB_IMAGEBLIT
1287 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1290 To compile this driver as a module, choose M here: the
1291 module will be called kyrofb.
1294 tristate "3Dfx Banshee/Voodoo3 display support"
1295 depends on FB && PCI
1296 select FB_CFB_IMAGEBLIT
1297 select FB_CFB_FILLRECT
1298 select FB_CFB_COPYAREA
1300 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1301 chips. Say Y if you have such a graphics board.
1303 To compile this driver as a module, choose M here: the
1304 module will be called tdfxfb.
1306 config FB_3DFX_ACCEL
1307 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1308 depends on FB_3DFX && EXPERIMENTAL
1310 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1311 with acceleration functions.
1315 tristate "3Dfx Voodoo Graphics (sst1) support"
1316 depends on FB && PCI
1317 select FB_CFB_FILLRECT
1318 select FB_CFB_COPYAREA
1319 select FB_CFB_IMAGEBLIT
1321 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1322 Voodoo2 (cvg) based graphics card.
1324 To compile this driver as a module, choose M here: the
1325 module will be called sstfb.
1327 WARNING: Do not use any application that uses the 3D engine
1328 (namely glide) while using this driver.
1329 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1330 options and other important info support.
1333 tristate "Cyberblade/i1 support"
1334 depends on FB && PCI && X86_32 && !64BIT
1335 select FB_CFB_IMAGEBLIT
1338 This driver is supposed to support the Trident Cyberblade/i1
1339 graphics core integrated in the VIA VT8601A North Bridge,
1340 also known as VIA Apollo PLE133.
1343 - Developed, tested and working on EPIA 5000 and EPIA 800.
1344 - Does work reliable on all systems with CRT/LCD connected to
1346 - Should work on systems that do use the internal LCD port, but
1347 this is absolutely not tested.
1349 Character imageblit, copyarea and rectangle fill are hw accelerated,
1350 ypan scrolling is used by default.
1352 Please do read <file:Documentation/fb/cyblafb/*>.
1354 To compile this driver as a module, choose M here: the
1355 module will be called cyblafb.
1358 tristate "Trident support"
1359 depends on FB && PCI
1360 select FB_CFB_FILLRECT
1361 select FB_CFB_COPYAREA
1362 select FB_CFB_IMAGEBLIT
1364 This driver is supposed to support graphics boards with the
1365 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1366 but also on some motherboards. For more information, read
1367 <file:Documentation/fb/tridentfb.txt>
1369 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1372 Say Y if you have such a graphics board.
1375 To compile this driver as a module, choose M here: the
1376 module will be called tridentfb.
1378 config FB_TRIDENT_ACCEL
1379 bool "Trident Acceleration functions (EXPERIMENTAL)"
1380 depends on FB_TRIDENT && EXPERIMENTAL
1382 This will compile the Trident frame buffer device with
1383 acceleration functions.
1386 tristate "Permedia3 support"
1387 depends on FB && PCI && BROKEN
1389 This is the frame buffer device driver for the 3DLabs Permedia3
1390 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1391 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1392 and maybe other boards.
1395 bool "Au1100 LCD Driver"
1396 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1399 bool "Au1200 LCD Driver"
1400 depends on (FB = y) && MIPS && SOC_AU1200
1401 select FB_CFB_FILLRECT
1402 select FB_CFB_COPYAREA
1403 select FB_CFB_IMAGEBLIT
1405 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1406 various panels and CRTs by passing in kernel cmd line option
1407 au1200fb:panel=<name>.
1409 source "drivers/video/geode/Kconfig"
1412 bool "Creator/Creator3D/Elite3D support"
1413 depends on FB_SBUS && SPARC64
1414 select FB_CFB_COPYAREA
1415 select FB_CFB_IMAGEBLIT
1417 This is the frame buffer device driver for the Creator, Creator3D,
1418 and Elite3D graphics boards.
1421 bool "TCX (SS4/SS5 only) support"
1423 select FB_CFB_FILLRECT
1424 select FB_CFB_COPYAREA
1425 select FB_CFB_IMAGEBLIT
1427 This is the frame buffer device driver for the TCX 24/8bit frame
1431 bool "CGfourteen (SX) support"
1433 select FB_CFB_FILLRECT
1434 select FB_CFB_COPYAREA
1435 select FB_CFB_IMAGEBLIT
1437 This is the frame buffer device driver for the CGfourteen frame
1438 buffer on Desktop SPARCsystems with the SX graphics option.
1441 bool "P9100 (Sparcbook 3 only) support"
1443 select FB_CFB_FILLRECT
1444 select FB_CFB_COPYAREA
1445 select FB_CFB_IMAGEBLIT
1447 This is the frame buffer device driver for the P9100 card
1448 supported on Sparcbook 3 machines.
1451 bool "Leo (ZX) support"
1453 select FB_CFB_FILLRECT
1454 select FB_CFB_COPYAREA
1455 select FB_CFB_IMAGEBLIT
1457 This is the frame buffer device driver for the SBUS-based Sun ZX
1458 (leo) frame buffer cards.
1461 bool "Sun XVR-500 3DLABS Wildcat support"
1462 depends on FB && PCI && SPARC64
1463 select FB_CFB_FILLRECT
1464 select FB_CFB_COPYAREA
1465 select FB_CFB_IMAGEBLIT
1467 This is the framebuffer device for the Sun XVR-500 and similar
1468 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1469 only works on sparc64 systems where the system firwmare has
1470 mostly initialized the card already. It is treated as a
1471 completely dumb framebuffer device.
1474 bool "Sun XVR-2500 3DLABS Wildcat support"
1475 depends on FB && PCI && SPARC64
1476 select FB_CFB_FILLRECT
1477 select FB_CFB_COPYAREA
1478 select FB_CFB_IMAGEBLIT
1480 This is the framebuffer device for the Sun XVR-2500 and similar
1481 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1482 only works on sparc64 systems where the system firwmare has
1483 mostly initialized the card already. It is treated as a
1484 completely dumb framebuffer device.
1487 bool "PCI framebuffers"
1488 depends on (FB = y) && PCI && SPARC
1491 bool "IGA 168x display support"
1492 depends on SPARC32 && FB_PCI
1493 select FB_CFB_FILLRECT
1494 select FB_CFB_COPYAREA
1495 select FB_CFB_IMAGEBLIT
1497 This is the framebuffer device for the INTERGRAPHICS 1680 and
1498 successor frame buffer cards.
1501 tristate "HD64461 Frame Buffer support"
1502 depends on FB && HD64461
1503 select FB_CFB_FILLRECT
1504 select FB_CFB_COPYAREA
1505 select FB_CFB_IMAGEBLIT
1507 This is the frame buffer device driver for the Hitachi HD64461 LCD
1511 bool "PMAG-AA TURBOchannel framebuffer support"
1512 depends on (FB = y) && TC
1513 select FB_CFB_FILLRECT
1514 select FB_CFB_COPYAREA
1515 select FB_CFB_IMAGEBLIT
1517 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1518 used mainly in the MIPS-based DECstation series.
1521 tristate "PMAG-BA TURBOchannel framebuffer support"
1523 select FB_CFB_FILLRECT
1524 select FB_CFB_COPYAREA
1525 select FB_CFB_IMAGEBLIT
1527 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1528 used mainly in the MIPS-based DECstation series.
1531 tristate "PMAGB-B TURBOchannel framebuffer support"
1533 select FB_CFB_FILLRECT
1534 select FB_CFB_COPYAREA
1535 select FB_CFB_IMAGEBLIT
1537 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1538 in the MIPS-based DECstation series. The card is currently only
1539 supported in 1280x1024x8 mode.
1542 bool "Maxine (Personal DECstation) onboard framebuffer support"
1543 depends on (FB = y) && MACH_DECSTATION
1544 select FB_CFB_FILLRECT
1545 select FB_CFB_COPYAREA
1546 select FB_CFB_IMAGEBLIT
1548 Support for the onboard framebuffer (1024x768x8) in the Personal
1549 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1553 bool "TMPTX3912/PR31700 frame buffer support"
1554 depends on (FB = y) && NINO
1555 select FB_CFB_FILLRECT
1556 select FB_CFB_COPYAREA
1557 select FB_CFB_IMAGEBLIT
1559 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1560 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1562 Say Y here to enable kernel support for the on-board framebuffer.
1565 bool "G364 frame buffer support"
1566 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1567 select FB_CFB_FILLRECT
1568 select FB_CFB_COPYAREA
1569 select FB_CFB_IMAGEBLIT
1571 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1572 Olivetti M700-10 systems.
1575 bool "Motorola 68328 native frame buffer support"
1576 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1577 select FB_CFB_FILLRECT
1578 select FB_CFB_COPYAREA
1579 select FB_CFB_IMAGEBLIT
1581 Say Y here if you want to support the built-in frame buffer of
1582 the Motorola 68328 CPU family.
1585 tristate "PXA LCD framebuffer support"
1586 depends on FB && ARCH_PXA
1587 select FB_CFB_FILLRECT
1588 select FB_CFB_COPYAREA
1589 select FB_CFB_IMAGEBLIT
1591 Frame buffer driver for the built-in LCD controller in the Intel
1594 This driver is also available as a module ( = code which can be
1595 inserted and removed from the running kernel whenever you want). The
1596 module will be called pxafb. If you want to compile it as a module,
1597 say M here and read <file:Documentation/kbuild/modules.txt>.
1601 config FB_PXA_PARAMETERS
1602 bool "PXA LCD command line parameters"
1606 Enable the use of kernel command line or module parameters
1607 to configure the physical properties of the LCD panel when
1608 using the PXA LCD driver.
1610 This option allows you to override the panel parameters
1611 supplied by the platform in order to support multiple
1612 different models of flatpanel. If you will only be using a
1613 single model of flatpanel then you can safely leave this
1616 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1619 tristate "2700G LCD framebuffer support"
1620 depends on FB && ARCH_PXA
1621 select FB_CFB_FILLRECT
1622 select FB_CFB_COPYAREA
1623 select FB_CFB_IMAGEBLIT
1625 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1629 bool "Enable debugging info via debugfs"
1630 depends on FB_MBX && DEBUG_FS
1633 Enable this if you want debugging information using the debug
1634 filesystem (debugfs)
1639 tristate "W100 frame buffer support"
1640 depends on FB && PXA_SHARPSL
1641 select FB_CFB_FILLRECT
1642 select FB_CFB_COPYAREA
1643 select FB_CFB_IMAGEBLIT
1645 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1647 This driver is also available as a module ( = code which can be
1648 inserted and removed from the running kernel whenever you want). The
1649 module will be called w100fb. If you want to compile it as a module,
1650 say M here and read <file:Documentation/kbuild/modules.txt>.
1655 tristate "S3C2410 LCD framebuffer support"
1656 depends on FB && ARCH_S3C2410
1657 select FB_CFB_FILLRECT
1658 select FB_CFB_COPYAREA
1659 select FB_CFB_IMAGEBLIT
1661 Frame buffer driver for the built-in LCD controller in the Samsung
1664 This driver is also available as a module ( = code which can be
1665 inserted and removed from the running kernel whenever you want). The
1666 module will be called s3c2410fb. If you want to compile it as a module,
1667 say M here and read <file:Documentation/kbuild/modules.txt>.
1670 config FB_S3C2410_DEBUG
1671 bool "S3C2410 lcd debug messages"
1672 depends on FB_S3C2410
1674 Turn on debugging messages. Note that you can set/unset at run time
1678 tristate "Silicon Motion SM501 framebuffer support"
1679 depends on FB && MFD_SM501
1680 select FB_CFB_FILLRECT
1681 select FB_CFB_COPYAREA
1682 select FB_CFB_IMAGEBLIT
1684 Frame buffer driver for the CRT and LCD controllers in the Silicon
1687 This driver is also available as a module ( = code which can be
1688 inserted and removed from the running kernel whenever you want). The
1689 module will be called sm501fb. If you want to compile it as a module,
1690 say M here and read <file:Documentation/modules.txt>.
1695 config FB_PNX4008_DUM
1696 tristate "Display Update Module support on Philips PNX4008 board"
1697 depends on FB && ARCH_PNX4008
1699 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1701 config FB_PNX4008_DUM_RGB
1702 tristate "RGB Framebuffer support on Philips PNX4008 board"
1703 depends on FB_PNX4008_DUM
1704 select FB_CFB_FILLRECT
1705 select FB_CFB_COPYAREA
1706 select FB_CFB_IMAGEBLIT
1708 Say Y here to enable support for PNX4008 RGB Framebuffer
1710 config FB_IBM_GXT4500
1711 tristate "Framebuffer support for IBM GXT4500P adaptor"
1713 select FB_CFB_FILLRECT
1714 select FB_CFB_COPYAREA
1715 select FB_CFB_IMAGEBLIT
1717 Say Y here to enable support for the IBM GXT4500P display
1718 adaptor, found on some IBM System P (pSeries) machines.
1721 bool "PS3 GPU framebuffer driver"
1722 depends on (FB = y) && PS3_PS3AV
1723 select FB_CFB_FILLRECT
1724 select FB_CFB_COPYAREA
1725 select FB_CFB_IMAGEBLIT
1727 Include support for the virtual frame buffer in the PS3 platform.
1729 config FB_PS3_DEFAULT_SIZE_M
1730 int "PS3 default frame buffer size (in MiB)"
1734 This is the default size (in MiB) of the virtual frame buffer in
1736 The default value can be overridden on the kernel command line
1737 using the "ps3fb" option (e.g. "ps3fb=9M");
1740 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1742 select FB_SYS_FILLRECT
1743 select FB_SYS_COPYAREA
1744 select FB_SYS_IMAGEBLIT
1746 This is a `virtual' frame buffer device. It operates on a chunk of
1747 unswappable kernel memory instead of on the memory of a graphics
1748 board. This means you cannot see any output sent to this frame
1749 buffer device, while it does consume precious memory. The main use
1750 of this frame buffer device is testing and debugging the frame
1751 buffer subsystem. Do NOT enable it for normal systems! To protect
1752 the innocent, it has to be enabled explicitly at boot time using the
1753 kernel option `video=vfb:'.
1755 To compile this driver as a module, choose M here: the
1756 module will be called vfb. In order to load it, you must use
1757 the vfb_enable=1 option.
1762 source "drivers/video/console/Kconfig"
1765 if FB || SGI_NEWPORT_CONSOLE
1766 source "drivers/video/logo/Kconfig"