5 menu "Graphics support"
8 source "drivers/video/backlight/Kconfig"
9 source "drivers/video/display/Kconfig"
16 tristate "Support for frame buffer devices"
18 The frame buffer device provides an abstraction for the graphics
19 hardware. It represents the frame buffer of some video hardware and
20 allows application software to access the graphics hardware through
21 a well-defined interface, so the software doesn't need to know
22 anything about the low-level (hardware register) stuff.
24 Frame buffer devices work identically across the different
25 architectures supported by Linux and make the implementation of
26 application programs easier and more portable; at this point, an X
27 server exists which uses the frame buffer device exclusively.
28 On several non-X86 architectures, the frame buffer device is the
29 only way to use the graphics hardware.
31 The device is accessed through special device nodes, usually located
32 in the /dev directory, i.e. /dev/fb*.
34 You need an utility program called fbset to make full use of frame
35 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
36 and the Framebuffer-HOWTO at
37 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
40 Say Y here and to the driver for your graphics board below if you
41 are compiling a kernel for a non-x86 architecture.
43 If you are compiling for the x86 architecture, you can say Y if you
44 want to play with it, but it is not essential. Please note that
45 running graphical applications that directly touch the hardware
46 (e.g. an accelerated X server) and that are not frame buffer
47 device-aware may cause unexpected results. If unsure, say N.
50 bool "Enable firmware EDID"
54 This enables access to the EDID transferred from the firmware.
55 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
56 transfers do not work for your driver and if you are using
57 nvidiafb, i810fb or savagefb.
59 In general, choosing Y for this option is safe. If you
60 experience extremely long delays while booting before you get
61 something on your display, try setting this to N. Matrox cards in
62 combination with certain motherboards and monitors are known to
63 suffer from this problem.
72 config FB_CFB_FILLRECT
77 Include the cfb_fillrect function for generic software rectangle
78 filling. This is used by drivers that don't provide their own
79 (accelerated) version.
81 config FB_CFB_COPYAREA
86 Include the cfb_copyarea function for generic software area copying.
87 This is used by drivers that don't provide their own (accelerated)
90 config FB_CFB_IMAGEBLIT
95 Include the cfb_imageblit function for generic software image
96 blitting. This is used by drivers that don't provide their own
97 (accelerated) version.
99 config FB_SYS_FILLRECT
104 Include the sys_fillrect function for generic software rectangle
105 filling. This is used by drivers that don't provide their own
106 (accelerated) version and the framebuffer is in system RAM.
108 config FB_SYS_COPYAREA
113 Include the sys_copyarea function for generic software area copying.
114 This is used by drivers that don't provide their own (accelerated)
115 version and the framebuffer is in system RAM.
117 config FB_SYS_IMAGEBLIT
122 Include the sys_imageblit function for generic software image
123 blitting. This is used by drivers that don't provide their own
124 (accelerated) version and the framebuffer is in system RAM.
131 config FB_DEFERRED_IO
141 Common utility functions useful to fbdev drivers of VGA-based
152 select BACKLIGHT_LCD_SUPPORT
153 select BACKLIGHT_CLASS_DEVICE
156 config FB_MODE_HELPERS
157 bool "Enable Video Mode Handling Helpers"
161 This enables functions for handling video modes using the
162 Generalized Timing Formula and the EDID parser. A few drivers rely
163 on this feature such as the radeonfb, rivafb, and the i810fb. If
164 your driver does not take advantage of this feature, choosing Y will
165 just increase the kernel size by about 5K.
167 config FB_TILEBLITTING
168 bool "Enable Tile Blitting Support"
172 This enables tile blitting. Tile blitting is a drawing technique
173 where the screen is divided into rectangular sections (tiles), whereas
174 the standard blitting divides the screen into pixels. Because the
175 default drawing element is a tile, drawing functions will be passed
176 parameters in terms of number of tiles instead of number of pixels.
177 For example, to draw a single character, instead of using bitmaps,
178 an index to an array of bitmaps will be used. To clear or move a
179 rectangular section of a screen, the rectangle will be described in
180 terms of number of tiles in the x- and y-axis.
182 This is particularly important to one driver, matroxfb. If
185 comment "Frame buffer hardware drivers"
189 tristate "Cirrus Logic support"
190 depends on FB && (ZORRO || PCI)
191 select FB_CFB_FILLRECT
192 select FB_CFB_COPYAREA
193 select FB_CFB_IMAGEBLIT
195 This enables support for Cirrus Logic GD542x/543x based boards on
196 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
198 If you have a PCI-based system, this enables support for these
199 chips: GD-543x, GD-544x, GD-5480.
201 Please read the file <file:Documentation/fb/cirrusfb.txt>.
203 Say N unless you have such a graphics board or plan to get one
204 before you next recompile the kernel.
207 tristate "Permedia2 support"
208 depends on FB && ((AMIGA && BROKEN) || PCI)
209 select FB_CFB_FILLRECT
210 select FB_CFB_COPYAREA
211 select FB_CFB_IMAGEBLIT
213 This is the frame buffer device driver for the Permedia2 AGP frame
214 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
216 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
218 config FB_PM2_FIFO_DISCONNECT
219 bool "enable FIFO disconnect feature"
220 depends on FB_PM2 && PCI
222 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
225 tristate "ARM PrimeCell PL110 support"
226 depends on FB && ARM && ARM_AMBA
227 select FB_CFB_FILLRECT
228 select FB_CFB_COPYAREA
229 select FB_CFB_IMAGEBLIT
231 This framebuffer device driver is for the ARM PrimeCell PL110
232 Colour LCD controller. ARM PrimeCells provide the building
233 blocks for System on a Chip devices.
235 If you want to compile this as a module (=code which can be
236 inserted into and removed from the running kernel), say M
237 here and read <file:Documentation/kbuild/modules.txt>. The module
238 will be called amba-clcd.
242 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
244 default FB_ARMCLCD_SHARP_LQ035Q7DB02
246 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
247 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
249 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
250 color QVGA, HRTFT panel. The LogicPD device includes
251 an integrated HRTFT controller IC.
252 The native resolution is 240x320.
254 config FB_ARMCLCD_SHARP_LQ057Q3DC02
255 bool "LogicPD LCD 5.7\" QVGA"
257 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
258 color QVGA, TFT panel. The LogicPD device includes an
259 The native resolution is 320x240.
261 config FB_ARMCLCD_SHARP_LQ64D343
262 bool "LogicPD LCD 6.4\" VGA"
264 This is an implementation of the Sharp LQ64D343, a 6.4"
265 color VGA, TFT panel. The LogicPD device includes an
266 The native resolution is 640x480.
268 config FB_ARMCLCD_SHARP_LQ10D368
269 bool "LogicPD LCD 10.4\" VGA"
271 This is an implementation of the Sharp LQ10D368, a 10.4"
272 color VGA, TFT panel. The LogicPD device includes an
273 The native resolution is 640x480.
276 config FB_ARMCLCD_SHARP_LQ121S1DG41
277 bool "LogicPD LCD 12.1\" SVGA"
279 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
280 color SVGA, TFT panel. The LogicPD device includes an
281 The native resolution is 800x600.
283 This panel requires a clock rate may be an integer fraction
284 of the base LCDCLK frequency. The driver will select the
285 highest frequency available that is lower than the maximum
286 allowed. The panel may flicker if the clock rate is
287 slower than the recommended minimum.
289 config FB_ARMCLCD_AUO_A070VW01_WIDE
290 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
292 This is an implementation of the AU Optronics, a 7.0"
293 WIDE Color. The native resolution is 234x480.
295 config FB_ARMCLCD_HITACHI
296 bool "Hitachi Wide Screen 800x480"
298 This is an implementation of the Hitachi 800x480.
304 bool "Acorn VIDC support"
305 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
306 select FB_CFB_FILLRECT
307 select FB_CFB_COPYAREA
308 select FB_CFB_IMAGEBLIT
310 This is the frame buffer device driver for the Acorn VIDC graphics
311 hardware found in Acorn RISC PCs and other ARM-based machines. If
315 bool "CLPS711X LCD support"
316 depends on (FB = y) && ARM && ARCH_CLPS711X
317 select FB_CFB_FILLRECT
318 select FB_CFB_COPYAREA
319 select FB_CFB_IMAGEBLIT
321 Say Y to enable the Framebuffer driver for the CLPS7111 and
325 bool "SA-1100 LCD support"
326 depends on (FB = y) && ARM && ARCH_SA1100
327 select FB_CFB_FILLRECT
328 select FB_CFB_COPYAREA
329 select FB_CFB_IMAGEBLIT
331 This is a framebuffer device for the SA-1100 LCD Controller.
332 See <http://www.linux-fbdev.org/> for information on framebuffer
335 If you plan to use the LCD display with your SA-1100 system, say
339 tristate "Motorola i.MX LCD support"
340 depends on FB && ARM && ARCH_IMX
341 select FB_CFB_FILLRECT
342 select FB_CFB_COPYAREA
343 select FB_CFB_IMAGEBLIT
346 tristate "CyberPro 2000/2010/5000 support"
347 depends on FB && PCI && (BROKEN || !SPARC64)
348 select FB_CFB_FILLRECT
349 select FB_CFB_COPYAREA
350 select FB_CFB_IMAGEBLIT
352 This enables support for the Integraphics CyberPro 20x0 and 5000
353 VGA chips used in the Rebel.com Netwinder and other machines.
354 Say Y if you have a NetWinder or a graphics card containing this
355 device, otherwise say N.
359 depends on (FB = y) && APOLLO
361 select FB_CFB_FILLRECT
362 select FB_CFB_IMAGEBLIT
366 depends on (FB = y) && Q40
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
373 tristate "Amiga native chipset support"
374 depends on FB && AMIGA
376 This is the frame buffer device driver for the builtin graphics
377 chipset found in Amigas.
379 To compile this driver as a module, choose M here: the
380 module will be called amifb.
383 bool "Amiga OCS chipset support"
386 This enables support for the original Agnus and Denise video chips,
387 found in the Amiga 1000 and most A500's and A2000's. If you intend
388 to run Linux on any of these systems, say Y; otherwise say N.
391 bool "Amiga ECS chipset support"
394 This enables support for the Enhanced Chip Set, found in later
395 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
396 you intend to run Linux on any of these systems, say Y; otherwise
400 bool "Amiga AGA chipset support"
403 This enables support for the Advanced Graphics Architecture (also
404 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
405 and CD32. If you intend to run Linux on any of these systems, say Y;
409 bool "Amiga FrameMaster II/Rainbow II support"
410 depends on (FB = y) && ZORRO
411 select FB_CFB_FILLRECT
412 select FB_CFB_COPYAREA
413 select FB_CFB_IMAGEBLIT
415 This is the frame buffer device driver for the Amiga FrameMaster
416 card from BSC (exhibited 1992 but not shipped as a CBM product).
419 tristate "Arc Monochrome LCD board support"
421 select FB_SYS_FILLRECT
422 select FB_SYS_COPYAREA
423 select FB_SYS_IMAGEBLIT
426 This enables support for the Arc Monochrome LCD board. The board
427 is based on the KS-108 lcd controller and is typically a matrix
428 of 2*n chips. This driver was tested with a 128x64 panel. This
429 driver supports it for use with x86 SBCs through a 16 bit GPIO
430 interface (8 bit data, 8 bit control). If you anticipate using
431 this driver, say Y or M; otherwise say N. You must specify the
432 GPIO IO address to be used for setting control and data.
435 bool "Atari native chipset support"
436 depends on (FB = y) && ATARI
437 select FB_CFB_FILLRECT
438 select FB_CFB_COPYAREA
439 select FB_CFB_IMAGEBLIT
441 This is the frame buffer device driver for the builtin graphics
442 chipset found in Ataris.
445 bool "Open Firmware frame buffer device support"
446 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
447 select FB_CFB_FILLRECT
448 select FB_CFB_COPYAREA
449 select FB_CFB_IMAGEBLIT
452 Say Y if you want support with Open Firmware for your graphics
456 bool "Apple \"control\" display support"
457 depends on (FB = y) && PPC_PMAC && PPC32
458 select FB_CFB_FILLRECT
459 select FB_CFB_COPYAREA
460 select FB_CFB_IMAGEBLIT
463 This driver supports a frame buffer for the graphics adapter in the
464 Power Macintosh 7300 and others.
467 bool "Apple \"platinum\" display support"
468 depends on (FB = y) && PPC_PMAC && PPC32
469 select FB_CFB_FILLRECT
470 select FB_CFB_COPYAREA
471 select FB_CFB_IMAGEBLIT
474 This driver supports a frame buffer for the "platinum" graphics
475 adapter in some Power Macintoshes.
478 bool "Apple \"valkyrie\" display support"
479 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
480 select FB_CFB_FILLRECT
481 select FB_CFB_COPYAREA
482 select FB_CFB_IMAGEBLIT
485 This driver supports a frame buffer for the "valkyrie" graphics
486 adapter in some Power Macintoshes.
489 bool "Chips 65550 display support"
490 depends on (FB = y) && PPC32
491 select FB_CFB_FILLRECT
492 select FB_CFB_COPYAREA
493 select FB_CFB_IMAGEBLIT
495 This is the frame buffer device driver for the Chips & Technologies
496 65550 graphics chip in PowerBooks.
499 bool "Asiliant (Chips) 69000 display support"
500 depends on (FB = y) && PCI
501 select FB_CFB_FILLRECT
502 select FB_CFB_COPYAREA
503 select FB_CFB_IMAGEBLIT
505 This is the frame buffer device driver for the Asiliant 69030 chipset
508 bool "IMS Twin Turbo display support"
509 depends on (FB = y) && PCI
510 select FB_CFB_IMAGEBLIT
511 select FB_MACMODES if PPC
513 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
514 many Macintosh and compatible computers.
517 tristate "VGA 16-color graphics support"
518 depends on FB && (X86 || PPC)
519 select FB_CFB_FILLRECT
520 select FB_CFB_COPYAREA
521 select FB_CFB_IMAGEBLIT
523 select FONT_8x16 if FRAMEBUFFER_CONSOLE
525 This is the frame buffer device driver for VGA 16 color graphic
526 cards. Say Y if you have such a card.
528 To compile this driver as a module, choose M here: the
529 module will be called vga16fb.
532 tristate "HP STI frame buffer device support"
533 depends on FB && PARISC
534 select FB_CFB_FILLRECT
535 select FB_CFB_COPYAREA
536 select FB_CFB_IMAGEBLIT
539 STI refers to the HP "Standard Text Interface" which is a set of
540 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
541 Enabling this option will implement the linux framebuffer device
542 using calls to the STI BIOS routines for initialisation.
544 If you enable this option, you will get a planar framebuffer device
545 /dev/fb which will work on the most common HP graphic cards of the
546 NGLE family, including the artist chips (in the 7xx and Bxxx series),
547 HCRX, HCRX24, CRX, CRX24 and VisEG series.
549 It is safe to enable this option, so you should probably say "Y".
552 bool "Generic Macintosh display support"
553 depends on (FB = y) && MAC
554 select FB_CFB_FILLRECT
555 select FB_CFB_COPYAREA
556 select FB_CFB_IMAGEBLIT
559 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
562 depends on (FB = y) && HP300
563 select FB_CFB_FILLRECT
564 select FB_CFB_IMAGEBLIT
568 tristate "TGA/SFB+ framebuffer support"
569 depends on FB && (ALPHA || TC)
570 select FB_CFB_FILLRECT
571 select FB_CFB_COPYAREA
572 select FB_CFB_IMAGEBLIT
575 This is the frame buffer device driver for generic TGA and SFB+
576 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
577 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
578 TURBOchannel cards, also known as PMAGD-A, -B and -C.
580 Due to hardware limitations ZLX-E2 and E3 cards are not supported
581 for DECstation 5000/200 systems. Additionally due to firmware
582 limitations these cards may cause troubles with booting DECstation
583 5000/240 and /260 systems, but are fully supported under Linux if
584 you manage to get it going. ;-)
586 Say Y if you have one of those.
589 bool "VESA VGA graphics support"
590 depends on (FB = y) && X86
591 select FB_CFB_FILLRECT
592 select FB_CFB_COPYAREA
593 select FB_CFB_IMAGEBLIT
596 This is the frame buffer device driver for generic VESA 2.0
597 compliant graphic cards. The older VESA 1.2 cards are not supported.
598 You will get a boot time penguin logo at no additional cost. Please
599 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
602 bool "Intel-based Macintosh Framebuffer Support"
603 depends on (FB = y) && X86 && EFI
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the frame buffer device driver for the Intel-based Macintosh
611 tristate "Hecuba board support"
612 depends on FB && X86 && MMU
613 select FB_SYS_FILLRECT
614 select FB_SYS_COPYAREA
615 select FB_SYS_IMAGEBLIT
617 select FB_DEFERRED_IO
619 This enables support for the Hecuba board. This driver was tested
620 with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
621 interface (8 bit data, 4 bit control). If you anticpate using
622 this driver, say Y or M; otherwise say N. You must specify the
623 GPIO IO address to be used for setting control and data.
626 tristate "Hercules mono graphics support"
628 select FB_CFB_FILLRECT
629 select FB_CFB_COPYAREA
630 select FB_CFB_IMAGEBLIT
632 Say Y here if you have a Hercules mono graphics card.
634 To compile this driver as a module, choose M here: the
635 module will be called hgafb.
637 As this card technology is 15 years old, most people will answer N
641 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
642 depends on FB_HGA && EXPERIMENTAL
644 This will compile the Hercules mono graphics with
645 acceleration functions.
648 tristate "SGI Visual Workstation framebuffer support"
649 depends on FB && X86_VISWS
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
654 SGI Visual Workstation support for framebuffer graphics.
657 bool "SGI Graphics Backend frame buffer support"
658 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
659 select FB_CFB_FILLRECT
660 select FB_CFB_COPYAREA
661 select FB_CFB_IMAGEBLIT
663 This is the frame buffer device driver for SGI Graphics Backend.
664 This chip is used in SGI O2 and Visual Workstation 320/540.
667 int "Video memory size in MB"
671 This is the amount of memory reserved for the framebuffer,
672 which can be any value between 1MB and 8MB.
675 bool "SBUS and UPA framebuffers"
676 depends on (FB = y) && SPARC
678 Say Y if you want support for SBUS or UPA based frame buffer device.
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 BWtwo frame buffer.
690 bool "CGthree support"
691 depends on (FB = y) && (SPARC && FB_SBUS)
692 select FB_CFB_FILLRECT
693 select FB_CFB_COPYAREA
694 select FB_CFB_IMAGEBLIT
696 This is the frame buffer device driver for the CGthree frame buffer.
699 bool "CGsix (GX,TurboGX) support"
700 depends on (FB = y) && (SPARC && FB_SBUS)
701 select FB_CFB_COPYAREA
702 select FB_CFB_IMAGEBLIT
704 This is the frame buffer device driver for the CGsix (GX, TurboGX)
708 tristate "NEC PowerVR 2 display support"
709 depends on FB && SH_DREAMCAST
710 select FB_CFB_FILLRECT
711 select FB_CFB_COPYAREA
712 select FB_CFB_IMAGEBLIT
714 Say Y here if you have a PowerVR 2 card in your box. If you plan to
715 run linux on your Dreamcast, you will have to say Y here.
716 This driver may or may not work on other PowerVR 2 cards, but is
717 totally untested. Use at your own risk. If unsure, say N.
719 To compile this driver as a module, choose M here: the
720 module will be called pvr2fb.
722 You can pass several parameters to the driver at boot time or at
723 module load time. The parameters look like "video=pvr2:XXX", where
724 the meaning of XXX can be found at the end of the main source file
725 (<file:drivers/video/pvr2fb.c>). Please see the file
726 <file:Documentation/fb/pvr2fb.txt>.
729 bool "Epson 1355 framebuffer support"
730 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
731 select FB_CFB_FILLRECT
732 select FB_CFB_COPYAREA
733 select FB_CFB_IMAGEBLIT
735 Build in support for the SED1355 Epson Research Embedded RAMDAC
736 LCD/CRT Controller (since redesignated as the S1D13505) as a
737 framebuffer. Product specs at
738 <http://www.erd.epson.com/vdc/html/products.htm>.
741 tristate "Epson S1D13XXX framebuffer support"
743 select FB_CFB_FILLRECT
744 select FB_CFB_COPYAREA
745 select FB_CFB_IMAGEBLIT
747 Support for S1D13XXX framebuffer device family (currently only
748 working with S1D13806). Product specs at
749 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
752 tristate "AT91/AT32 LCD Controller support"
753 depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9263 || AVR32)
754 select FB_CFB_FILLRECT
755 select FB_CFB_COPYAREA
756 select FB_CFB_IMAGEBLIT
758 This enables support for the AT91/AT32 LCD Controller.
761 bool "Frame Buffer in internal SRAM"
762 depends on FB_ATMEL && ARCH_AT91SAM9261
764 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
765 to let frame buffer in external SDRAM.
768 tristate "nVidia Framebuffer Support"
770 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
771 select FB_MODE_HELPERS
772 select FB_CFB_FILLRECT
773 select FB_CFB_COPYAREA
774 select FB_CFB_IMAGEBLIT
778 This driver supports graphics boards with the nVidia chips, TNT
779 and newer. For very old chipsets, such as the RIVA128, then use
781 Say Y if you have such a graphics board.
783 To compile this driver as a module, choose M here: the
784 module will be called nvidiafb.
787 bool "Enable DDC Support"
791 This enables I2C support for nVidia Chipsets. This is used
792 only for getting EDID information from the attached display
793 allowing for robust video mode handling and switching.
795 Because fbdev-2.6 requires that drivers must be able to
796 independently validate video mode parameters, you should say Y
799 config FB_NVIDIA_BACKLIGHT
800 bool "Support for backlight control"
804 Say Y here if you want to control the backlight of your display.
807 tristate "nVidia Riva support"
809 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
810 select FB_MODE_HELPERS
811 select FB_CFB_FILLRECT
812 select FB_CFB_COPYAREA
813 select FB_CFB_IMAGEBLIT
817 This driver supports graphics boards with the nVidia Riva/Geforce
819 Say Y if you have such a graphics board.
821 To compile this driver as a module, choose M here: the
822 module will be called rivafb.
825 bool "Enable DDC Support"
829 This enables I2C support for nVidia Chipsets. This is used
830 only for getting EDID information from the attached display
831 allowing for robust video mode handling and switching.
833 Because fbdev-2.6 requires that drivers must be able to
834 independently validate video mode parameters, you should say Y
838 bool "Lots of debug output from Riva(nVidia) driver"
842 Say Y here if you want the Riva driver to output all sorts
843 of debugging information to provide to the maintainer when
844 something goes wrong.
846 config FB_RIVA_BACKLIGHT
847 bool "Support for backlight control"
851 Say Y here if you want to control the backlight of your display.
854 tristate "Intel 810/815 support (EXPERIMENTAL)"
855 depends on FB && EXPERIMENTAL && PCI && X86_32
858 select FB_MODE_HELPERS
859 select FB_CFB_FILLRECT
860 select FB_CFB_COPYAREA
861 select FB_CFB_IMAGEBLIT
864 This driver supports the on-board graphics built in to the Intel 810
865 and 815 chipsets. Say Y if you have and plan to use such a board.
867 To compile this driver as a module, choose M here: the
868 module will be called i810fb.
870 For more information, please read
871 <file:Documentation/fb/intel810.txt>
874 bool "use VESA Generalized Timing Formula"
877 If you say Y, then the VESA standard, Generalized Timing Formula
878 or GTF, will be used to calculate the required video timing values
879 per video mode. Since the GTF allows nondiscrete timings
880 (nondiscrete being a range of values as opposed to discrete being a
881 set of values), you'll be able to use any combination of horizontal
882 and vertical resolutions, and vertical refresh rates without having
883 to specify your own timing parameters. This is especially useful
884 to maximize the performance of an aging display, or if you just
885 have a display with nonstandard dimensions. A VESA compliant
886 monitor is recommended, but can still work with non-compliant ones.
887 If you need or want this, then select this option. The timings may
888 not be compliant with Intel's recommended values. Use at your own
891 If you say N, the driver will revert to discrete video timings
892 using a set recommended by Intel in their documentation.
897 bool "Enable DDC Support"
898 depends on FB_I810 && FB_I810_GTF
903 tristate "Intel LE80578 (Vermilion) support"
904 depends on FB && PCI && X86
905 select FB_MODE_HELPERS
906 select FB_CFB_FILLRECT
907 select FB_CFB_COPYAREA
908 select FB_CFB_IMAGEBLIT
910 This driver supports the LE80578 (Vermilion Range) chipset
912 config FB_CARILLO_RANCH
913 tristate "Intel Carillo Ranch support"
914 depends on FB_LE80578 && FB && PCI && X86
916 This driver supports the LE80578 (Carillo Ranch) board
919 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
920 depends on FB && EXPERIMENTAL && PCI && X86
923 select FB_MODE_HELPERS
924 select FB_CFB_FILLRECT
925 select FB_CFB_COPYAREA
926 select FB_CFB_IMAGEBLIT
928 This driver supports the on-board graphics built in to the Intel
929 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
930 Say Y if you have and plan to use such a board.
932 If you say Y here and want DDC/I2C support you must first say Y to
933 "I2C support" and "I2C bit-banging support" in the character devices
936 If you say M here then "I2C support" and "I2C bit-banging support"
937 can be build either as modules or built-in.
939 To compile this driver as a module, choose M here: the
940 module will be called intelfb.
942 For more information, please read <file:Documentation/fb/intelfb.txt>
944 config FB_INTEL_DEBUG
945 bool "Intel driver Debug Messages"
948 Say Y here if you want the Intel driver to output all sorts
949 of debugging information to provide to the maintainer when
950 something goes wrong.
953 bool "DDC/I2C for Intel framebuffer support"
958 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
961 tristate "Matrox acceleration"
963 select FB_CFB_FILLRECT
964 select FB_CFB_COPYAREA
965 select FB_CFB_IMAGEBLIT
966 select FB_TILEBLITTING
967 select FB_MACMODES if PPC_PMAC
969 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
970 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
971 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
972 Matrox G400, G450 or G550 card in your box.
974 To compile this driver as a module, choose M here: the
975 module will be called matroxfb.
977 You can pass several parameters to the driver at boot time or at
978 module load time. The parameters look like "video=matrox:XXX", and
979 are described in <file:Documentation/fb/matroxfb.txt>.
981 config FB_MATROX_MILLENIUM
982 bool "Millennium I/II support"
985 Say Y here if you have a Matrox Millennium or Matrox Millennium II
986 video card. If you select "Advanced lowlevel driver options" below,
987 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
988 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
989 also use font widths different from 8.
991 config FB_MATROX_MYSTIQUE
992 bool "Mystique support"
995 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
996 video card. If you select "Advanced lowlevel driver options" below,
997 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
998 packed pixel and 32 bpp packed pixel. You can also use font widths
1002 bool "G100/G200/G400/G450/G550 support"
1003 depends on FB_MATROX
1005 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1006 video card. If you select "Advanced lowlevel driver options", you
1007 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1008 pixel and 32 bpp packed pixel. You can also use font widths
1011 If you need support for G400 secondary head, you must first say Y to
1012 "I2C support" in the character devices section, and then to
1013 "Matrox I2C support" and "G400 second head support" here in the
1014 framebuffer section. G450/G550 secondary head and digital output
1015 are supported without additional modules.
1017 The driver starts in monitor mode. You must use the matroxset tool
1018 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1019 swap primary and secondary head outputs, or to change output mode.
1020 Secondary head driver always start in 640x480 resolution and you
1021 must use fbset to change it.
1023 Do not forget that second head supports only 16 and 32 bpp
1024 packed pixels, so it is a good idea to compile them into the kernel
1025 too. You can use only some font widths, as the driver uses generic
1026 painting procedures (the secondary head does not use acceleration
1029 G450/G550 hardware can display TV picture only from secondary CRTC,
1030 and it performs no scaling, so picture must have 525 or 625 lines.
1032 config FB_MATROX_I2C
1033 tristate "Matrox I2C support"
1034 depends on FB_MATROX
1037 This drivers creates I2C buses which are needed for accessing the
1038 DDC (I2C) bus present on all Matroxes, an I2C bus which
1039 interconnects Matrox optional devices, like MGA-TVO on G200 and
1040 G400, and the secondary head DDC bus, present on G400 only.
1042 You can say Y or M here if you want to experiment with monitor
1043 detection code. You must say Y or M here if you want to use either
1044 second head of G400 or MGA-TVO on G200 or G400.
1046 If you compile it as module, it will create a module named
1049 config FB_MATROX_MAVEN
1050 tristate "G400 second head support"
1051 depends on FB_MATROX_G && FB_MATROX_I2C
1053 WARNING !!! This support does not work with G450 !!!
1055 Say Y or M here if you want to use a secondary head (meaning two
1056 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1057 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1058 secondary head output is blanked while you are in X. With XFree
1059 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1060 the fbdev driver on first head and the fbdev driver on second head.
1062 If you compile it as module, two modules are created,
1063 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1064 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1065 also load i2c-matroxfb to get it to run.
1067 The driver starts in monitor mode and you must use the matroxset
1069 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1070 PAL or NTSC or to swap primary and secondary head outputs.
1071 Secondary head driver also always start in 640x480 resolution, you
1072 must use fbset to change it.
1074 Also do not forget that second head supports only 16 and 32 bpp
1075 packed pixels, so it is a good idea to compile them into the kernel
1076 too. You can use only some font widths, as the driver uses generic
1077 painting procedures (the secondary head does not use acceleration
1080 config FB_MATROX_MULTIHEAD
1081 bool "Multihead support"
1082 depends on FB_MATROX
1084 Say Y here if you have more than one (supported) Matrox device in
1085 your computer and you want to use all of them for different monitors
1086 ("multihead"). If you have only one device, you should say N because
1087 the driver compiled with Y is larger and a bit slower, especially on
1090 If you said M to "Matrox unified accelerated driver" and N here, you
1091 will still be able to use several Matrox devices simultaneously:
1092 insert several instances of the module matroxfb into the kernel
1093 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
1094 for the different Matrox devices. This method is slightly faster but
1095 uses 40 KB of kernel memory per Matrox card.
1097 There is no need for enabling 'Matrox multihead support' if you have
1098 only one Matrox card in the box.
1101 tristate "ATI Radeon display support"
1102 depends on FB && PCI
1103 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1104 select FB_MODE_HELPERS
1105 select FB_CFB_FILLRECT
1106 select FB_CFB_COPYAREA
1107 select FB_CFB_IMAGEBLIT
1108 select FB_MACMODES if PPC_OF
1110 Choose this option if you want to use an ATI Radeon graphics card as
1111 a framebuffer device. There are both PCI and AGP versions. You
1112 don't need to choose this to run the Radeon in plain VGA mode.
1114 If you say Y here and want DDC/I2C support you must first say Y to
1115 "I2C support" and "I2C bit-banging support" in the character devices
1118 If you say M here then "I2C support" and "I2C bit-banging support"
1119 can be build either as modules or built-in.
1121 There is a product page at
1122 http://apps.ati.com/ATIcompare/
1124 config FB_RADEON_I2C
1125 bool "DDC/I2C for ATI Radeon support"
1126 depends on FB_RADEON
1130 Say Y here if you want DDC/I2C support for your Radeon board.
1132 config FB_RADEON_BACKLIGHT
1133 bool "Support for backlight control"
1134 depends on FB_RADEON
1137 Say Y here if you want to control the backlight of your display.
1139 config FB_RADEON_DEBUG
1140 bool "Lots of debug output from Radeon driver"
1141 depends on FB_RADEON
1144 Say Y here if you want the Radeon driver to output all sorts
1145 of debugging information to provide to the maintainer when
1146 something goes wrong.
1149 tristate "ATI Rage128 display support"
1150 depends on FB && PCI
1151 select FB_CFB_FILLRECT
1152 select FB_CFB_COPYAREA
1153 select FB_CFB_IMAGEBLIT
1154 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1155 select FB_MACMODES if PPC_PMAC
1157 This driver supports graphics boards with the ATI Rage128 chips.
1158 Say Y if you have such a graphics board and read
1159 <file:Documentation/fb/aty128fb.txt>.
1161 To compile this driver as a module, choose M here: the
1162 module will be called aty128fb.
1164 config FB_ATY128_BACKLIGHT
1165 bool "Support for backlight control"
1166 depends on FB_ATY128
1169 Say Y here if you want to control the backlight of your display.
1172 tristate "ATI Mach64 display support" if PCI || ATARI
1173 depends on FB && !SPARC32
1174 select FB_CFB_FILLRECT
1175 select FB_CFB_COPYAREA
1176 select FB_CFB_IMAGEBLIT
1177 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1178 select FB_MACMODES if PPC
1180 This driver supports graphics boards with the ATI Mach64 chips.
1181 Say Y if you have such a graphics board.
1183 To compile this driver as a module, choose M here: the
1184 module will be called atyfb.
1187 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1188 depends on PCI && FB_ATY
1189 default y if SPARC64 && FB_PCI
1191 Say Y here to support use of ATI's 64-bit Rage boards (or other
1192 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1193 framebuffer device. The ATI product support page for these boards
1194 is at <http://support.ati.com/products/pc/mach64/>.
1196 config FB_ATY_GENERIC_LCD
1197 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1198 depends on FB_ATY_CT
1200 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1201 Rage XC, or Rage XL chipset.
1204 bool "Mach64 GX support" if PCI
1208 Say Y here to support use of the ATI Mach64 Graphics Expression
1209 board (or other boards based on the Mach64 GX chipset) as a
1210 framebuffer device. The ATI product support page for these boards
1212 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1214 config FB_ATY_BACKLIGHT
1215 bool "Support for backlight control"
1219 Say Y here if you want to control the backlight of your display.
1222 tristate "S3 Trio/Virge support"
1223 depends on FB && PCI
1224 select FB_CFB_FILLRECT
1225 select FB_CFB_COPYAREA
1226 select FB_CFB_IMAGEBLIT
1227 select FB_TILEBLITTING
1230 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1232 Driver for graphics boards with S3 Trio / S3 Virge chip.
1235 tristate "S3 Savage support"
1236 depends on FB && PCI && EXPERIMENTAL
1237 select FB_MODE_HELPERS
1238 select FB_CFB_FILLRECT
1239 select FB_CFB_COPYAREA
1240 select FB_CFB_IMAGEBLIT
1243 This driver supports notebooks and computers with S3 Savage PCI/AGP
1246 Say Y if you have such a graphics card.
1248 To compile this driver as a module, choose M here; the module
1249 will be called savagefb.
1251 config FB_SAVAGE_I2C
1252 bool "Enable DDC2 Support"
1253 depends on FB_SAVAGE
1256 This enables I2C support for S3 Savage Chipsets. This is used
1257 only for getting EDID information from the attached display
1258 allowing for robust video mode handling and switching.
1260 Because fbdev-2.6 requires that drivers must be able to
1261 independently validate video mode parameters, you should say Y
1264 config FB_SAVAGE_ACCEL
1265 bool "Enable Console Acceleration"
1266 depends on FB_SAVAGE
1269 This option will compile in console acceleration support. If
1270 the resulting framebuffer console has bothersome glitches, then
1274 tristate "SiS/XGI display support"
1275 depends on FB && PCI
1276 select FB_CFB_FILLRECT
1277 select FB_CFB_COPYAREA
1278 select FB_CFB_IMAGEBLIT
1280 This is the frame buffer device driver for the SiS 300, 315, 330
1281 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1282 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1284 To compile this driver as a module, choose M here; the module
1285 will be called sisfb.
1288 bool "SiS 300 series support"
1291 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1294 bool "SiS 315/330/340 series and XGI support"
1297 Say Y here to support use of the SiS 315, 330 and 340 series
1298 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1299 as XGI V3XT, V5, V8 and Z7.
1302 tristate "NeoMagic display support"
1303 depends on FB && PCI
1304 select FB_MODE_HELPERS
1305 select FB_CFB_FILLRECT
1306 select FB_CFB_COPYAREA
1307 select FB_CFB_IMAGEBLIT
1310 This driver supports notebooks with NeoMagic PCI chips.
1311 Say Y if you have such a graphics card.
1313 To compile this driver as a module, choose M here: the
1314 module will be called neofb.
1317 tristate "IMG Kyro support"
1318 depends on FB && PCI
1319 select FB_CFB_FILLRECT
1320 select FB_CFB_COPYAREA
1321 select FB_CFB_IMAGEBLIT
1323 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1326 To compile this driver as a module, choose M here: the
1327 module will be called kyrofb.
1330 tristate "3Dfx Banshee/Voodoo3 display support"
1331 depends on FB && PCI
1332 select FB_CFB_IMAGEBLIT
1333 select FB_CFB_FILLRECT
1334 select FB_CFB_COPYAREA
1336 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1337 chips. Say Y if you have such a graphics board.
1339 To compile this driver as a module, choose M here: the
1340 module will be called tdfxfb.
1342 config FB_3DFX_ACCEL
1343 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1344 depends on FB_3DFX && EXPERIMENTAL
1346 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1347 with acceleration functions.
1351 tristate "3Dfx Voodoo Graphics (sst1) support"
1352 depends on FB && PCI
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1357 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1358 Voodoo2 (cvg) based graphics card.
1360 To compile this driver as a module, choose M here: the
1361 module will be called sstfb.
1363 WARNING: Do not use any application that uses the 3D engine
1364 (namely glide) while using this driver.
1365 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1366 options and other important info support.
1369 tristate "VIA VT8623 support"
1370 depends on FB && PCI
1371 select FB_CFB_FILLRECT
1372 select FB_CFB_COPYAREA
1373 select FB_CFB_IMAGEBLIT
1374 select FB_TILEBLITTING
1377 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1379 Driver for CastleRock integrated graphics core in the
1380 VIA VT8623 [Apollo CLE266] chipset.
1383 tristate "Cyberblade/i1 support"
1384 depends on FB && PCI && X86_32 && !64BIT
1385 select FB_CFB_IMAGEBLIT
1388 This driver is supposed to support the Trident Cyberblade/i1
1389 graphics core integrated in the VIA VT8601A North Bridge,
1390 also known as VIA Apollo PLE133.
1393 - Developed, tested and working on EPIA 5000 and EPIA 800.
1394 - Does work reliable on all systems with CRT/LCD connected to
1396 - Should work on systems that do use the internal LCD port, but
1397 this is absolutely not tested.
1399 Character imageblit, copyarea and rectangle fill are hw accelerated,
1400 ypan scrolling is used by default.
1402 Please do read <file:Documentation/fb/cyblafb/*>.
1404 To compile this driver as a module, choose M here: the
1405 module will be called cyblafb.
1408 tristate "Trident support"
1409 depends on FB && PCI
1410 select FB_CFB_FILLRECT
1411 select FB_CFB_COPYAREA
1412 select FB_CFB_IMAGEBLIT
1414 This driver is supposed to support graphics boards with the
1415 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1416 but also on some motherboards. For more information, read
1417 <file:Documentation/fb/tridentfb.txt>
1419 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1422 Say Y if you have such a graphics board.
1425 To compile this driver as a module, choose M here: the
1426 module will be called tridentfb.
1428 config FB_TRIDENT_ACCEL
1429 bool "Trident Acceleration functions (EXPERIMENTAL)"
1430 depends on FB_TRIDENT && EXPERIMENTAL
1432 This will compile the Trident frame buffer device with
1433 acceleration functions.
1436 tristate "ARK 2000PV support"
1437 depends on FB && PCI
1438 select FB_CFB_FILLRECT
1439 select FB_CFB_COPYAREA
1440 select FB_CFB_IMAGEBLIT
1441 select FB_TILEBLITTING
1444 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1446 Driver for PCI graphics boards with ARK 2000PV chip
1447 and ICS 5342 RAMDAC.
1450 tristate "Permedia3 support (EXPERIMENTAL)"
1451 depends on FB && PCI && EXPERIMENTAL
1452 select FB_CFB_FILLRECT
1453 select FB_CFB_COPYAREA
1454 select FB_CFB_IMAGEBLIT
1456 This is the frame buffer device driver for the 3DLabs Permedia3
1457 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1458 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1459 and maybe other boards.
1462 bool "Au1100 LCD Driver"
1463 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1466 bool "Au1200 LCD Driver"
1467 depends on (FB = y) && MIPS && SOC_AU1200
1468 select FB_CFB_FILLRECT
1469 select FB_CFB_COPYAREA
1470 select FB_CFB_IMAGEBLIT
1472 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1473 various panels and CRTs by passing in kernel cmd line option
1474 au1200fb:panel=<name>.
1476 source "drivers/video/geode/Kconfig"
1479 bool "Creator/Creator3D/Elite3D support"
1480 depends on FB_SBUS && SPARC64
1481 select FB_CFB_COPYAREA
1482 select FB_CFB_IMAGEBLIT
1484 This is the frame buffer device driver for the Creator, Creator3D,
1485 and Elite3D graphics boards.
1488 bool "TCX (SS4/SS5 only) support"
1490 select FB_CFB_FILLRECT
1491 select FB_CFB_COPYAREA
1492 select FB_CFB_IMAGEBLIT
1494 This is the frame buffer device driver for the TCX 24/8bit frame
1498 bool "CGfourteen (SX) support"
1500 select FB_CFB_FILLRECT
1501 select FB_CFB_COPYAREA
1502 select FB_CFB_IMAGEBLIT
1504 This is the frame buffer device driver for the CGfourteen frame
1505 buffer on Desktop SPARCsystems with the SX graphics option.
1508 bool "P9100 (Sparcbook 3 only) support"
1510 select FB_CFB_FILLRECT
1511 select FB_CFB_COPYAREA
1512 select FB_CFB_IMAGEBLIT
1514 This is the frame buffer device driver for the P9100 card
1515 supported on Sparcbook 3 machines.
1518 bool "Leo (ZX) support"
1520 select FB_CFB_FILLRECT
1521 select FB_CFB_COPYAREA
1522 select FB_CFB_IMAGEBLIT
1524 This is the frame buffer device driver for the SBUS-based Sun ZX
1525 (leo) frame buffer cards.
1528 bool "Sun XVR-500 3DLABS Wildcat support"
1529 depends on FB && PCI && SPARC64
1530 select FB_CFB_FILLRECT
1531 select FB_CFB_COPYAREA
1532 select FB_CFB_IMAGEBLIT
1534 This is the framebuffer device for the Sun XVR-500 and similar
1535 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1536 only works on sparc64 systems where the system firwmare has
1537 mostly initialized the card already. It is treated as a
1538 completely dumb framebuffer device.
1541 bool "Sun XVR-2500 3DLABS Wildcat support"
1542 depends on FB && PCI && SPARC64
1543 select FB_CFB_FILLRECT
1544 select FB_CFB_COPYAREA
1545 select FB_CFB_IMAGEBLIT
1547 This is the framebuffer device for the Sun XVR-2500 and similar
1548 graphics cards based upon the 3DLABS Wildcat chipset. The driver
1549 only works on sparc64 systems where the system firwmare has
1550 mostly initialized the card already. It is treated as a
1551 completely dumb framebuffer device.
1554 bool "PCI framebuffers"
1555 depends on (FB = y) && PCI && SPARC
1558 bool "IGA 168x display support"
1559 depends on SPARC32 && FB_PCI
1560 select FB_CFB_FILLRECT
1561 select FB_CFB_COPYAREA
1562 select FB_CFB_IMAGEBLIT
1564 This is the framebuffer device for the INTERGRAPHICS 1680 and
1565 successor frame buffer cards.
1568 tristate "HD64461 Frame Buffer support"
1569 depends on FB && HD64461
1570 select FB_CFB_FILLRECT
1571 select FB_CFB_COPYAREA
1572 select FB_CFB_IMAGEBLIT
1574 This is the frame buffer device driver for the Hitachi HD64461 LCD
1578 bool "PMAG-AA TURBOchannel framebuffer support"
1579 depends on (FB = y) && TC
1580 select FB_CFB_FILLRECT
1581 select FB_CFB_COPYAREA
1582 select FB_CFB_IMAGEBLIT
1584 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1585 used mainly in the MIPS-based DECstation series.
1588 tristate "PMAG-BA TURBOchannel framebuffer support"
1590 select FB_CFB_FILLRECT
1591 select FB_CFB_COPYAREA
1592 select FB_CFB_IMAGEBLIT
1594 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1595 used mainly in the MIPS-based DECstation series.
1598 tristate "PMAGB-B TURBOchannel framebuffer support"
1600 select FB_CFB_FILLRECT
1601 select FB_CFB_COPYAREA
1602 select FB_CFB_IMAGEBLIT
1604 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1605 in the MIPS-based DECstation series. The card is currently only
1606 supported in 1280x1024x8 mode.
1609 bool "Maxine (Personal DECstation) onboard framebuffer support"
1610 depends on (FB = y) && MACH_DECSTATION
1611 select FB_CFB_FILLRECT
1612 select FB_CFB_COPYAREA
1613 select FB_CFB_IMAGEBLIT
1615 Support for the onboard framebuffer (1024x768x8) in the Personal
1616 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1620 bool "TMPTX3912/PR31700 frame buffer support"
1621 depends on (FB = y) && NINO
1622 select FB_CFB_FILLRECT
1623 select FB_CFB_COPYAREA
1624 select FB_CFB_IMAGEBLIT
1626 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1627 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1629 Say Y here to enable kernel support for the on-board framebuffer.
1632 bool "G364 frame buffer support"
1633 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1634 select FB_CFB_FILLRECT
1635 select FB_CFB_COPYAREA
1636 select FB_CFB_IMAGEBLIT
1638 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1639 Olivetti M700-10 systems.
1642 bool "Motorola 68328 native frame buffer support"
1643 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1644 select FB_CFB_FILLRECT
1645 select FB_CFB_COPYAREA
1646 select FB_CFB_IMAGEBLIT
1648 Say Y here if you want to support the built-in frame buffer of
1649 the Motorola 68328 CPU family.
1652 tristate "PXA LCD framebuffer support"
1653 depends on FB && ARCH_PXA
1654 select FB_CFB_FILLRECT
1655 select FB_CFB_COPYAREA
1656 select FB_CFB_IMAGEBLIT
1658 Frame buffer driver for the built-in LCD controller in the Intel
1661 This driver is also available as a module ( = code which can be
1662 inserted and removed from the running kernel whenever you want). The
1663 module will be called pxafb. If you want to compile it as a module,
1664 say M here and read <file:Documentation/kbuild/modules.txt>.
1668 config FB_PXA_PARAMETERS
1669 bool "PXA LCD command line parameters"
1673 Enable the use of kernel command line or module parameters
1674 to configure the physical properties of the LCD panel when
1675 using the PXA LCD driver.
1677 This option allows you to override the panel parameters
1678 supplied by the platform in order to support multiple
1679 different models of flatpanel. If you will only be using a
1680 single model of flatpanel then you can safely leave this
1683 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1686 tristate "2700G LCD framebuffer support"
1687 depends on FB && ARCH_PXA
1688 select FB_CFB_FILLRECT
1689 select FB_CFB_COPYAREA
1690 select FB_CFB_IMAGEBLIT
1692 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1696 bool "Enable debugging info via debugfs"
1697 depends on FB_MBX && DEBUG_FS
1700 Enable this if you want debugging information using the debug
1701 filesystem (debugfs)
1706 tristate "W100 frame buffer support"
1707 depends on FB && PXA_SHARPSL
1708 select FB_CFB_FILLRECT
1709 select FB_CFB_COPYAREA
1710 select FB_CFB_IMAGEBLIT
1712 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1714 This driver is also available as a module ( = code which can be
1715 inserted and removed from the running kernel whenever you want). The
1716 module will be called w100fb. If you want to compile it as a module,
1717 say M here and read <file:Documentation/kbuild/modules.txt>.
1722 tristate "S3C2410 LCD framebuffer support"
1723 depends on FB && ARCH_S3C2410
1724 select FB_CFB_FILLRECT
1725 select FB_CFB_COPYAREA
1726 select FB_CFB_IMAGEBLIT
1728 Frame buffer driver for the built-in LCD controller in the Samsung
1731 This driver is also available as a module ( = code which can be
1732 inserted and removed from the running kernel whenever you want). The
1733 module will be called s3c2410fb. If you want to compile it as a module,
1734 say M here and read <file:Documentation/kbuild/modules.txt>.
1737 config FB_S3C2410_DEBUG
1738 bool "S3C2410 lcd debug messages"
1739 depends on FB_S3C2410
1741 Turn on debugging messages. Note that you can set/unset at run time
1745 tristate "Silicon Motion SM501 framebuffer support"
1746 depends on FB && MFD_SM501
1747 select FB_CFB_FILLRECT
1748 select FB_CFB_COPYAREA
1749 select FB_CFB_IMAGEBLIT
1751 Frame buffer driver for the CRT and LCD controllers in the Silicon
1754 This driver is also available as a module ( = code which can be
1755 inserted and removed from the running kernel whenever you want). The
1756 module will be called sm501fb. If you want to compile it as a module,
1757 say M here and read <file:Documentation/modules.txt>.
1762 config FB_PNX4008_DUM
1763 tristate "Display Update Module support on Philips PNX4008 board"
1764 depends on FB && ARCH_PNX4008
1766 Say Y here to enable support for PNX4008 Display Update Module (DUM)
1768 config FB_PNX4008_DUM_RGB
1769 tristate "RGB Framebuffer support on Philips PNX4008 board"
1770 depends on FB_PNX4008_DUM
1771 select FB_CFB_FILLRECT
1772 select FB_CFB_COPYAREA
1773 select FB_CFB_IMAGEBLIT
1775 Say Y here to enable support for PNX4008 RGB Framebuffer
1777 config FB_IBM_GXT4500
1778 tristate "Framebuffer support for IBM GXT4500P adaptor"
1780 select FB_CFB_FILLRECT
1781 select FB_CFB_COPYAREA
1782 select FB_CFB_IMAGEBLIT
1784 Say Y here to enable support for the IBM GXT4500P display
1785 adaptor, found on some IBM System P (pSeries) machines.
1788 bool "PS3 GPU framebuffer driver"
1789 depends on (FB = y) && PS3_PS3AV
1790 select FB_CFB_FILLRECT
1791 select FB_CFB_COPYAREA
1792 select FB_CFB_IMAGEBLIT
1794 Include support for the virtual frame buffer in the PS3 platform.
1796 config FB_PS3_DEFAULT_SIZE_M
1797 int "PS3 default frame buffer size (in MiB)"
1801 This is the default size (in MiB) of the virtual frame buffer in
1803 The default value can be overridden on the kernel command line
1804 using the "ps3fb" option (e.g. "ps3fb=9M");
1807 tristate "Xilinx frame buffer support"
1808 depends on FB && XILINX_VIRTEX
1809 select FB_CFB_FILLRECT
1810 select FB_CFB_COPYAREA
1811 select FB_CFB_IMAGEBLIT
1813 Include support for the Xilinx ML300/ML403 reference design
1814 framebuffer. ML300 carries a 640*480 LCD display on the board,
1815 ML403 uses a standard DB15 VGA connector.
1818 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1820 select FB_SYS_FILLRECT
1821 select FB_SYS_COPYAREA
1822 select FB_SYS_IMAGEBLIT
1825 This is a `virtual' frame buffer device. It operates on a chunk of
1826 unswappable kernel memory instead of on the memory of a graphics
1827 board. This means you cannot see any output sent to this frame
1828 buffer device, while it does consume precious memory. The main use
1829 of this frame buffer device is testing and debugging the frame
1830 buffer subsystem. Do NOT enable it for normal systems! To protect
1831 the innocent, it has to be enabled explicitly at boot time using the
1832 kernel option `video=vfb:'.
1834 To compile this driver as a module, choose M here: the
1835 module will be called vfb. In order to load it, you must use
1836 the vfb_enable=1 option.
1841 source "drivers/video/console/Kconfig"
1844 if FB || SGI_NEWPORT_CONSOLE
1845 source "drivers/video/logo/Kconfig"