Root/drivers/video/Kconfig

1#
2# Video configuration
3#
4
5menu "Graphics support"
6    depends on HAS_IOMEM
7
8source "drivers/char/agp/Kconfig"
9
10source "drivers/gpu/vga/Kconfig"
11
12source "drivers/gpu/drm/Kconfig"
13
14config VGASTATE
15       tristate
16       default n
17
18config VIDEO_OUTPUT_CONTROL
19    tristate "Lowlevel video output switch controls"
20    help
21      This framework adds support for low-level control of the video
22      output switch.
23
24menuconfig FB
25    tristate "Support for frame buffer devices"
26    ---help---
27      The frame buffer device provides an abstraction for the graphics
28      hardware. It represents the frame buffer of some video hardware and
29      allows application software to access the graphics hardware through
30      a well-defined interface, so the software doesn't need to know
31      anything about the low-level (hardware register) stuff.
32
33      Frame buffer devices work identically across the different
34      architectures supported by Linux and make the implementation of
35      application programs easier and more portable; at this point, an X
36      server exists which uses the frame buffer device exclusively.
37      On several non-X86 architectures, the frame buffer device is the
38      only way to use the graphics hardware.
39
40      The device is accessed through special device nodes, usually located
41      in the /dev directory, i.e. /dev/fb*.
42
43      You need an utility program called fbset to make full use of frame
44      buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
45      and the Framebuffer-HOWTO at
46      <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.2.html> for more
47      information.
48
49      Say Y here and to the driver for your graphics board below if you
50      are compiling a kernel for a non-x86 architecture.
51
52      If you are compiling for the x86 architecture, you can say Y if you
53      want to play with it, but it is not essential. Please note that
54      running graphical applications that directly touch the hardware
55      (e.g. an accelerated X server) and that are not frame buffer
56      device-aware may cause unexpected results. If unsure, say N.
57
58config FIRMWARE_EDID
59       bool "Enable firmware EDID"
60       depends on FB
61       default n
62       ---help---
63         This enables access to the EDID transferred from the firmware.
64     On the i386, this is from the Video BIOS. Enable this if DDC/I2C
65     transfers do not work for your driver and if you are using
66     nvidiafb, i810fb or savagefb.
67
68     In general, choosing Y for this option is safe. If you
69     experience extremely long delays while booting before you get
70     something on your display, try setting this to N. Matrox cards in
71     combination with certain motherboards and monitors are known to
72     suffer from this problem.
73
74config FB_DDC
75       tristate
76       depends on FB
77       select I2C_ALGOBIT
78       select I2C
79       default n
80
81config FB_BOOT_VESA_SUPPORT
82    bool
83    depends on FB
84    default n
85    ---help---
86      If true, at least one selected framebuffer driver can take advantage
87      of VESA video modes set at an early boot stage via the vga= parameter.
88
89config FB_CFB_FILLRECT
90    tristate
91    depends on FB
92    default n
93    ---help---
94      Include the cfb_fillrect function for generic software rectangle
95      filling. This is used by drivers that don't provide their own
96      (accelerated) version.
97
98config FB_CFB_COPYAREA
99    tristate
100    depends on FB
101    default n
102    ---help---
103      Include the cfb_copyarea function for generic software area copying.
104      This is used by drivers that don't provide their own (accelerated)
105      version.
106
107config FB_CFB_IMAGEBLIT
108    tristate
109    depends on FB
110    default n
111    ---help---
112      Include the cfb_imageblit function for generic software image
113      blitting. This is used by drivers that don't provide their own
114      (accelerated) version.
115
116config FB_CFB_REV_PIXELS_IN_BYTE
117    bool
118    depends on FB
119    default n
120    ---help---
121      Allow generic frame-buffer functions to work on displays with 1, 2
122      and 4 bits per pixel depths which has opposite order of pixels in
123      byte order to bytes in long order.
124
125config FB_SYS_FILLRECT
126    tristate
127    depends on FB
128    default n
129    ---help---
130      Include the sys_fillrect function for generic software rectangle
131      filling. This is used by drivers that don't provide their own
132      (accelerated) version and the framebuffer is in system RAM.
133
134config FB_SYS_COPYAREA
135    tristate
136    depends on FB
137    default n
138    ---help---
139      Include the sys_copyarea function for generic software area copying.
140      This is used by drivers that don't provide their own (accelerated)
141      version and the framebuffer is in system RAM.
142
143config FB_SYS_IMAGEBLIT
144    tristate
145    depends on FB
146    default n
147    ---help---
148      Include the sys_imageblit function for generic software image
149      blitting. This is used by drivers that don't provide their own
150      (accelerated) version and the framebuffer is in system RAM.
151
152menuconfig FB_FOREIGN_ENDIAN
153    bool "Framebuffer foreign endianness support"
154    depends on FB
155    ---help---
156      This menu will let you enable support for the framebuffers with
157      non-native endianness (e.g. Little-Endian framebuffer on a
158      Big-Endian machine). Most probably you don't have such hardware,
159      so it's safe to say "n" here.
160
161choice
162    prompt "Choice endianness support"
163    depends on FB_FOREIGN_ENDIAN
164
165config FB_BOTH_ENDIAN
166    bool "Support for Big- and Little-Endian framebuffers"
167
168config FB_BIG_ENDIAN
169    bool "Support for Big-Endian framebuffers only"
170
171config FB_LITTLE_ENDIAN
172    bool "Support for Little-Endian framebuffers only"
173
174endchoice
175
176config FB_SYS_FOPS
177       tristate
178       depends on FB
179       default n
180
181config FB_DEFERRED_IO
182    bool
183    depends on FB
184
185config FB_HECUBA
186    tristate
187    depends on FB
188    depends on FB_DEFERRED_IO
189
190config FB_SVGALIB
191    tristate
192    depends on FB
193    default n
194    ---help---
195      Common utility functions useful to fbdev drivers of VGA-based
196      cards.
197
198config FB_MACMODES
199       tristate
200       depends on FB
201       default n
202
203config FB_BACKLIGHT
204    bool
205    depends on FB
206    select BACKLIGHT_LCD_SUPPORT
207    select BACKLIGHT_CLASS_DEVICE
208    default n
209
210config FB_MODE_HELPERS
211        bool "Enable Video Mode Handling Helpers"
212        depends on FB
213    default n
214    ---help---
215      This enables functions for handling video modes using the
216      Generalized Timing Formula and the EDID parser. A few drivers rely
217          on this feature such as the radeonfb, rivafb, and the i810fb. If
218      your driver does not take advantage of this feature, choosing Y will
219      just increase the kernel size by about 5K.
220
221config FB_TILEBLITTING
222       bool "Enable Tile Blitting Support"
223       depends on FB
224       default n
225       ---help---
226         This enables tile blitting. Tile blitting is a drawing technique
227     where the screen is divided into rectangular sections (tiles), whereas
228     the standard blitting divides the screen into pixels. Because the
229     default drawing element is a tile, drawing functions will be passed
230     parameters in terms of number of tiles instead of number of pixels.
231     For example, to draw a single character, instead of using bitmaps,
232     an index to an array of bitmaps will be used. To clear or move a
233     rectangular section of a screen, the rectangle will be described in
234     terms of number of tiles in the x- and y-axis.
235
236     This is particularly important to one driver, matroxfb. If
237     unsure, say N.
238
239comment "Frame buffer hardware drivers"
240    depends on FB
241
242config FB_CIRRUS
243    tristate "Cirrus Logic support"
244    depends on FB && (ZORRO || PCI)
245    select FB_CFB_FILLRECT
246    select FB_CFB_COPYAREA
247    select FB_CFB_IMAGEBLIT
248    ---help---
249      This enables support for Cirrus Logic GD542x/543x based boards on
250      Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
251
252      If you have a PCI-based system, this enables support for these
253      chips: GD-543x, GD-544x, GD-5480.
254
255      Please read the file <file:Documentation/fb/cirrusfb.txt>.
256
257      Say N unless you have such a graphics board or plan to get one
258      before you next recompile the kernel.
259
260config FB_PM2
261    tristate "Permedia2 support"
262    depends on FB && ((AMIGA && BROKEN) || PCI)
263    select FB_CFB_FILLRECT
264    select FB_CFB_COPYAREA
265    select FB_CFB_IMAGEBLIT
266    help
267      This is the frame buffer device driver for cards based on
268      the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
269      The driver was tested on the following cards:
270        Diamond FireGL 1000 PRO AGP
271        ELSA Gloria Synergy PCI
272        Appian Jeronimo PRO (both heads) PCI
273        3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
274        Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
275        ASK Graphic Blaster Exxtreme AGP
276
277      To compile this driver as a module, choose M here: the
278      module will be called pm2fb.
279
280config FB_PM2_FIFO_DISCONNECT
281    bool "enable FIFO disconnect feature"
282    depends on FB_PM2 && PCI
283    help
284      Support the Permedia2 FIFO disconnect feature.
285
286config FB_ARMCLCD
287    tristate "ARM PrimeCell PL110 support"
288    depends on FB && ARM && ARM_AMBA
289    select FB_CFB_FILLRECT
290    select FB_CFB_COPYAREA
291    select FB_CFB_IMAGEBLIT
292    help
293      This framebuffer device driver is for the ARM PrimeCell PL110
294      Colour LCD controller. ARM PrimeCells provide the building
295      blocks for System on a Chip devices.
296
297      If you want to compile this as a module (=code which can be
298      inserted into and removed from the running kernel), say M
299      here and read <file:Documentation/kbuild/modules.txt>. The module
300      will be called amba-clcd.
301
302choice
303
304    depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
305    prompt "LCD Panel"
306    default FB_ARMCLCD_SHARP_LQ035Q7DB02
307
308config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
309    bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
310    help
311      This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
312      color QVGA, HRTFT panel. The LogicPD device includes
313      an integrated HRTFT controller IC.
314      The native resolution is 240x320.
315
316config FB_ARMCLCD_SHARP_LQ057Q3DC02
317    bool "LogicPD LCD 5.7\" QVGA"
318    help
319      This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
320      color QVGA, TFT panel. The LogicPD device includes an
321      The native resolution is 320x240.
322
323config FB_ARMCLCD_SHARP_LQ64D343
324    bool "LogicPD LCD 6.4\" VGA"
325    help
326      This is an implementation of the Sharp LQ64D343, a 6.4"
327      color VGA, TFT panel. The LogicPD device includes an
328      The native resolution is 640x480.
329
330config FB_ARMCLCD_SHARP_LQ10D368
331    bool "LogicPD LCD 10.4\" VGA"
332    help
333      This is an implementation of the Sharp LQ10D368, a 10.4"
334      color VGA, TFT panel. The LogicPD device includes an
335      The native resolution is 640x480.
336
337
338config FB_ARMCLCD_SHARP_LQ121S1DG41
339    bool "LogicPD LCD 12.1\" SVGA"
340    help
341      This is an implementation of the Sharp LQ121S1DG41, a 12.1"
342      color SVGA, TFT panel. The LogicPD device includes an
343      The native resolution is 800x600.
344
345      This panel requires a clock rate may be an integer fraction
346      of the base LCDCLK frequency. The driver will select the
347      highest frequency available that is lower than the maximum
348      allowed. The panel may flicker if the clock rate is
349      slower than the recommended minimum.
350
351config FB_ARMCLCD_AUO_A070VW01_WIDE
352    bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
353    help
354      This is an implementation of the AU Optronics, a 7.0"
355      WIDE Color. The native resolution is 234x480.
356
357config FB_ARMCLCD_HITACHI
358    bool "Hitachi Wide Screen 800x480"
359    help
360      This is an implementation of the Hitachi 800x480.
361
362endchoice
363
364
365config FB_ACORN
366    bool "Acorn VIDC support"
367    depends on (FB = y) && ARM && ARCH_ACORN
368    select FB_CFB_FILLRECT
369    select FB_CFB_COPYAREA
370    select FB_CFB_IMAGEBLIT
371    help
372      This is the frame buffer device driver for the Acorn VIDC graphics
373      hardware found in Acorn RISC PCs and other ARM-based machines. If
374      unsure, say N.
375
376config FB_CLPS711X
377    bool "CLPS711X LCD support"
378    depends on (FB = y) && ARM && ARCH_CLPS711X
379    select FB_CFB_FILLRECT
380    select FB_CFB_COPYAREA
381    select FB_CFB_IMAGEBLIT
382    help
383      Say Y to enable the Framebuffer driver for the CLPS7111 and
384      EP7212 processors.
385
386config FB_SA1100
387    bool "SA-1100 LCD support"
388    depends on (FB = y) && ARM && ARCH_SA1100
389    select FB_CFB_FILLRECT
390    select FB_CFB_COPYAREA
391    select FB_CFB_IMAGEBLIT
392    help
393      This is a framebuffer device for the SA-1100 LCD Controller.
394      See <http://www.linux-fbdev.org/> for information on framebuffer
395      devices.
396
397      If you plan to use the LCD display with your SA-1100 system, say
398      Y here.
399
400config FB_IMX
401    tristate "Motorola i.MX LCD support"
402    depends on FB && (ARCH_MX1 || ARCH_MX2)
403    select FB_CFB_FILLRECT
404    select FB_CFB_COPYAREA
405    select FB_CFB_IMAGEBLIT
406
407config FB_CYBER2000
408    tristate "CyberPro 2000/2010/5000 support"
409    depends on FB && PCI && (BROKEN || !SPARC64)
410    select FB_CFB_FILLRECT
411    select FB_CFB_COPYAREA
412    select FB_CFB_IMAGEBLIT
413    help
414      This enables support for the Integraphics CyberPro 20x0 and 5000
415      VGA chips used in the Rebel.com Netwinder and other machines.
416      Say Y if you have a NetWinder or a graphics card containing this
417      device, otherwise say N.
418
419config FB_APOLLO
420    bool
421    depends on (FB = y) && APOLLO
422    default y
423    select FB_CFB_FILLRECT
424    select FB_CFB_IMAGEBLIT
425
426config FB_Q40
427    bool
428    depends on (FB = y) && Q40
429    default y
430    select FB_CFB_FILLRECT
431    select FB_CFB_COPYAREA
432    select FB_CFB_IMAGEBLIT
433
434config FB_AMIGA
435    tristate "Amiga native chipset support"
436    depends on FB && AMIGA
437    help
438      This is the frame buffer device driver for the builtin graphics
439      chipset found in Amigas.
440
441      To compile this driver as a module, choose M here: the
442      module will be called amifb.
443
444config FB_AMIGA_OCS
445    bool "Amiga OCS chipset support"
446    depends on FB_AMIGA
447    help
448      This enables support for the original Agnus and Denise video chips,
449      found in the Amiga 1000 and most A500's and A2000's. If you intend
450      to run Linux on any of these systems, say Y; otherwise say N.
451
452config FB_AMIGA_ECS
453    bool "Amiga ECS chipset support"
454    depends on FB_AMIGA
455    help
456      This enables support for the Enhanced Chip Set, found in later
457      A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
458      you intend to run Linux on any of these systems, say Y; otherwise
459      say N.
460
461config FB_AMIGA_AGA
462    bool "Amiga AGA chipset support"
463    depends on FB_AMIGA
464    help
465      This enables support for the Advanced Graphics Architecture (also
466      known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
467      and CD32. If you intend to run Linux on any of these systems, say Y;
468      otherwise say N.
469
470config FB_FM2
471    bool "Amiga FrameMaster II/Rainbow II support"
472    depends on (FB = y) && ZORRO
473    select FB_CFB_FILLRECT
474    select FB_CFB_COPYAREA
475    select FB_CFB_IMAGEBLIT
476    help
477      This is the frame buffer device driver for the Amiga FrameMaster
478      card from BSC (exhibited 1992 but not shipped as a CBM product).
479
480config FB_ARC
481    tristate "Arc Monochrome LCD board support"
482    depends on FB && X86
483    select FB_SYS_FILLRECT
484    select FB_SYS_COPYAREA
485    select FB_SYS_IMAGEBLIT
486    select FB_SYS_FOPS
487    help
488      This enables support for the Arc Monochrome LCD board. The board
489      is based on the KS-108 lcd controller and is typically a matrix
490      of 2*n chips. This driver was tested with a 128x64 panel. This
491      driver supports it for use with x86 SBCs through a 16 bit GPIO
492      interface (8 bit data, 8 bit control). If you anticipate using
493      this driver, say Y or M; otherwise say N. You must specify the
494      GPIO IO address to be used for setting control and data.
495
496config FB_ATARI
497    bool "Atari native chipset support"
498    depends on (FB = y) && ATARI
499    select FB_CFB_FILLRECT
500    select FB_CFB_COPYAREA
501    select FB_CFB_IMAGEBLIT
502    help
503      This is the frame buffer device driver for the builtin graphics
504      chipset found in Ataris.
505
506config FB_OF
507    bool "Open Firmware frame buffer device support"
508    depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
509    select FB_CFB_FILLRECT
510    select FB_CFB_COPYAREA
511    select FB_CFB_IMAGEBLIT
512    select FB_MACMODES
513    help
514      Say Y if you want support with Open Firmware for your graphics
515      board.
516
517config FB_CONTROL
518    bool "Apple \"control\" display support"
519    depends on (FB = y) && PPC_PMAC && PPC32
520    select FB_CFB_FILLRECT
521    select FB_CFB_COPYAREA
522    select FB_CFB_IMAGEBLIT
523    select FB_MACMODES
524    help
525      This driver supports a frame buffer for the graphics adapter in the
526      Power Macintosh 7300 and others.
527
528config FB_PLATINUM
529    bool "Apple \"platinum\" display support"
530    depends on (FB = y) && PPC_PMAC && PPC32
531    select FB_CFB_FILLRECT
532    select FB_CFB_COPYAREA
533    select FB_CFB_IMAGEBLIT
534    select FB_MACMODES
535    help
536      This driver supports a frame buffer for the "platinum" graphics
537      adapter in some Power Macintoshes.
538
539config FB_VALKYRIE
540    bool "Apple \"valkyrie\" display support"
541    depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
542    select FB_CFB_FILLRECT
543    select FB_CFB_COPYAREA
544    select FB_CFB_IMAGEBLIT
545    select FB_MACMODES
546    help
547      This driver supports a frame buffer for the "valkyrie" graphics
548      adapter in some Power Macintoshes.
549
550config FB_CT65550
551    bool "Chips 65550 display support"
552    depends on (FB = y) && PPC32 && PCI
553    select FB_CFB_FILLRECT
554    select FB_CFB_COPYAREA
555    select FB_CFB_IMAGEBLIT
556    help
557      This is the frame buffer device driver for the Chips & Technologies
558      65550 graphics chip in PowerBooks.
559
560config FB_ASILIANT
561    bool "Asiliant (Chips) 69000 display support"
562    depends on (FB = y) && PCI
563    select FB_CFB_FILLRECT
564    select FB_CFB_COPYAREA
565    select FB_CFB_IMAGEBLIT
566    help
567      This is the frame buffer device driver for the Asiliant 69030 chipset
568
569config FB_IMSTT
570    bool "IMS Twin Turbo display support"
571    depends on (FB = y) && PCI
572    select FB_CFB_IMAGEBLIT
573    select FB_MACMODES if PPC
574    help
575      The IMS Twin Turbo is a PCI-based frame buffer card bundled with
576      many Macintosh and compatible computers.
577
578config FB_VGA16
579    tristate "VGA 16-color graphics support"
580    depends on FB && (X86 || PPC)
581    select FB_CFB_FILLRECT
582    select FB_CFB_COPYAREA
583    select FB_CFB_IMAGEBLIT
584    select VGASTATE
585    select FONT_8x16 if FRAMEBUFFER_CONSOLE
586    help
587      This is the frame buffer device driver for VGA 16 color graphic
588      cards. Say Y if you have such a card.
589
590      To compile this driver as a module, choose M here: the
591      module will be called vga16fb.
592
593config FB_BF54X_LQ043
594    tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
595    depends on FB && (BF54x) && !BF542
596    select FB_CFB_FILLRECT
597    select FB_CFB_COPYAREA
598    select FB_CFB_IMAGEBLIT
599    help
600     This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
601
602config FB_BFIN_T350MCQB
603    tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
604    depends on FB && BLACKFIN
605    select BFIN_GPTIMERS
606    select FB_CFB_FILLRECT
607    select FB_CFB_COPYAREA
608    select FB_CFB_IMAGEBLIT
609    help
610     This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
611     This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
612     It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
613
614
615config FB_STI
616    tristate "HP STI frame buffer device support"
617    depends on FB && PARISC
618    select FB_CFB_FILLRECT
619    select FB_CFB_COPYAREA
620    select FB_CFB_IMAGEBLIT
621    select STI_CONSOLE
622    select VT
623    default y
624    ---help---
625      STI refers to the HP "Standard Text Interface" which is a set of
626      BIOS routines contained in a ROM chip in HP PA-RISC based machines.
627      Enabling this option will implement the linux framebuffer device
628      using calls to the STI BIOS routines for initialisation.
629    
630      If you enable this option, you will get a planar framebuffer device
631      /dev/fb which will work on the most common HP graphic cards of the
632      NGLE family, including the artist chips (in the 7xx and Bxxx series),
633      HCRX, HCRX24, CRX, CRX24 and VisEG series.
634
635      It is safe to enable this option, so you should probably say "Y".
636
637config FB_MAC
638    bool "Generic Macintosh display support"
639    depends on (FB = y) && MAC
640    select FB_CFB_FILLRECT
641    select FB_CFB_COPYAREA
642    select FB_CFB_IMAGEBLIT
643    select FB_MACMODES
644
645config FB_HP300
646    bool
647    depends on (FB = y) && DIO
648    select FB_CFB_IMAGEBLIT
649    default y
650
651config FB_TGA
652    tristate "TGA/SFB+ framebuffer support"
653    depends on FB && (ALPHA || TC)
654    select FB_CFB_FILLRECT
655    select FB_CFB_COPYAREA
656    select FB_CFB_IMAGEBLIT
657    select BITREVERSE
658    ---help---
659      This is the frame buffer device driver for generic TGA and SFB+
660      graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
661      also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
662      TURBOchannel cards, also known as PMAGD-A, -B and -C.
663
664      Due to hardware limitations ZLX-E2 and E3 cards are not supported
665      for DECstation 5000/200 systems. Additionally due to firmware
666      limitations these cards may cause troubles with booting DECstation
667      5000/240 and /260 systems, but are fully supported under Linux if
668      you manage to get it going. ;-)
669
670      Say Y if you have one of those.
671
672config FB_UVESA
673    tristate "Userspace VESA VGA graphics support"
674    depends on FB && CONNECTOR
675    select FB_CFB_FILLRECT
676    select FB_CFB_COPYAREA
677    select FB_CFB_IMAGEBLIT
678    select FB_MODE_HELPERS
679    help
680      This is the frame buffer driver for generic VBE 2.0 compliant
681      graphic cards. It can also take advantage of VBE 3.0 features,
682      such as refresh rate adjustment.
683
684      This driver generally provides more features than vesafb but
685      requires a userspace helper application called 'v86d'. See
686      <file:Documentation/fb/uvesafb.txt> for more information.
687
688      If unsure, say N.
689
690config FB_VESA
691    bool "VESA VGA graphics support"
692    depends on (FB = y) && X86
693    select FB_CFB_FILLRECT
694    select FB_CFB_COPYAREA
695    select FB_CFB_IMAGEBLIT
696    select FB_BOOT_VESA_SUPPORT
697    help
698      This is the frame buffer device driver for generic VESA 2.0
699      compliant graphic cards. The older VESA 1.2 cards are not supported.
700      You will get a boot time penguin logo at no additional cost. Please
701      read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
702
703config FB_EFI
704    bool "EFI-based Framebuffer Support"
705    depends on (FB = y) && X86 && EFI
706    select FB_CFB_FILLRECT
707    select FB_CFB_COPYAREA
708    select FB_CFB_IMAGEBLIT
709    help
710      This is the EFI frame buffer device driver. If the firmware on
711      your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
712      using the EFI framebuffer as your console.
713
714config FB_N411
715       tristate "N411 Apollo/Hecuba devkit support"
716       depends on FB && X86 && MMU
717       select FB_SYS_FILLRECT
718       select FB_SYS_COPYAREA
719       select FB_SYS_IMAGEBLIT
720       select FB_SYS_FOPS
721       select FB_DEFERRED_IO
722       select FB_HECUBA
723       help
724         This enables support for the Apollo display controller in its
725         Hecuba form using the n411 devkit.
726
727config FB_HGA
728    tristate "Hercules mono graphics support"
729    depends on FB && X86
730    select FB_CFB_FILLRECT
731    select FB_CFB_COPYAREA
732    select FB_CFB_IMAGEBLIT
733    help
734      Say Y here if you have a Hercules mono graphics card.
735
736      To compile this driver as a module, choose M here: the
737      module will be called hgafb.
738
739      As this card technology is 15 years old, most people will answer N
740      here.
741
742config FB_HGA_ACCEL
743    bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
744    depends on FB_HGA && EXPERIMENTAL
745    ---help---
746    This will compile the Hercules mono graphics with
747    acceleration functions.
748
749config FB_SGIVW
750    tristate "SGI Visual Workstation framebuffer support"
751    depends on FB && X86_VISWS
752    select FB_CFB_FILLRECT
753    select FB_CFB_COPYAREA
754    select FB_CFB_IMAGEBLIT
755    help
756      SGI Visual Workstation support for framebuffer graphics.
757
758config FB_GBE
759    bool "SGI Graphics Backend frame buffer support"
760    depends on (FB = y) && (SGI_IP32 || X86_VISWS)
761    select FB_CFB_FILLRECT
762    select FB_CFB_COPYAREA
763    select FB_CFB_IMAGEBLIT
764     help
765      This is the frame buffer device driver for SGI Graphics Backend.
766      This chip is used in SGI O2 and Visual Workstation 320/540.
767
768config FB_GBE_MEM
769    int "Video memory size in MB"
770    depends on FB_GBE
771    default 4
772    help
773      This is the amount of memory reserved for the framebuffer,
774      which can be any value between 1MB and 8MB.
775
776config FB_SBUS
777    bool "SBUS and UPA framebuffers"
778    depends on (FB = y) && SPARC
779    help
780      Say Y if you want support for SBUS or UPA based frame buffer device.
781
782config FB_BW2
783    bool "BWtwo support"
784    depends on (FB = y) && (SPARC && FB_SBUS)
785    select FB_CFB_FILLRECT
786    select FB_CFB_COPYAREA
787    select FB_CFB_IMAGEBLIT
788    help
789      This is the frame buffer device driver for the BWtwo frame buffer.
790
791config FB_CG3
792    bool "CGthree support"
793    depends on (FB = y) && (SPARC && FB_SBUS)
794    select FB_CFB_FILLRECT
795    select FB_CFB_COPYAREA
796    select FB_CFB_IMAGEBLIT
797    help
798      This is the frame buffer device driver for the CGthree frame buffer.
799
800config FB_CG6
801    bool "CGsix (GX,TurboGX) support"
802    depends on (FB = y) && (SPARC && FB_SBUS)
803    select FB_CFB_COPYAREA
804    select FB_CFB_IMAGEBLIT
805    help
806      This is the frame buffer device driver for the CGsix (GX, TurboGX)
807      frame buffer.
808
809config FB_FFB
810    bool "Creator/Creator3D/Elite3D support"
811    depends on FB_SBUS && SPARC64
812    select FB_CFB_COPYAREA
813    select FB_CFB_IMAGEBLIT
814    help
815      This is the frame buffer device driver for the Creator, Creator3D,
816      and Elite3D graphics boards.
817
818config FB_TCX
819    bool "TCX (SS4/SS5 only) support"
820    depends on FB_SBUS
821    select FB_CFB_FILLRECT
822    select FB_CFB_COPYAREA
823    select FB_CFB_IMAGEBLIT
824    help
825      This is the frame buffer device driver for the TCX 24/8bit frame
826      buffer.
827
828config FB_CG14
829    bool "CGfourteen (SX) support"
830    depends on FB_SBUS
831    select FB_CFB_FILLRECT
832    select FB_CFB_COPYAREA
833    select FB_CFB_IMAGEBLIT
834    help
835      This is the frame buffer device driver for the CGfourteen frame
836      buffer on Desktop SPARCsystems with the SX graphics option.
837
838config FB_P9100
839    bool "P9100 (Sparcbook 3 only) support"
840    depends on FB_SBUS
841    select FB_CFB_FILLRECT
842    select FB_CFB_COPYAREA
843    select FB_CFB_IMAGEBLIT
844    help
845      This is the frame buffer device driver for the P9100 card
846      supported on Sparcbook 3 machines.
847
848config FB_LEO
849    bool "Leo (ZX) support"
850    depends on FB_SBUS
851    select FB_CFB_FILLRECT
852    select FB_CFB_COPYAREA
853    select FB_CFB_IMAGEBLIT
854    help
855      This is the frame buffer device driver for the SBUS-based Sun ZX
856      (leo) frame buffer cards.
857
858config FB_IGA
859    bool "IGA 168x display support"
860    depends on (FB = y) && SPARC32
861    select FB_CFB_FILLRECT
862    select FB_CFB_COPYAREA
863    select FB_CFB_IMAGEBLIT
864    help
865      This is the framebuffer device for the INTERGRAPHICS 1680 and
866      successor frame buffer cards.
867
868config FB_XVR500
869    bool "Sun XVR-500 3DLABS Wildcat support"
870    depends on (FB = y) && PCI && SPARC64
871    select FB_CFB_FILLRECT
872    select FB_CFB_COPYAREA
873    select FB_CFB_IMAGEBLIT
874    help
875      This is the framebuffer device for the Sun XVR-500 and similar
876      graphics cards based upon the 3DLABS Wildcat chipset. The driver
877      only works on sparc64 systems where the system firmware has
878      mostly initialized the card already. It is treated as a
879      completely dumb framebuffer device.
880
881config FB_XVR2500
882    bool "Sun XVR-2500 3DLABS Wildcat support"
883    depends on (FB = y) && PCI && SPARC64
884    select FB_CFB_FILLRECT
885    select FB_CFB_COPYAREA
886    select FB_CFB_IMAGEBLIT
887    help
888      This is the framebuffer device for the Sun XVR-2500 and similar
889      graphics cards based upon the 3DLABS Wildcat chipset. The driver
890      only works on sparc64 systems where the system firmware has
891      mostly initialized the card already. It is treated as a
892      completely dumb framebuffer device.
893
894config FB_PVR2
895    tristate "NEC PowerVR 2 display support"
896    depends on FB && SH_DREAMCAST
897    select FB_CFB_FILLRECT
898    select FB_CFB_COPYAREA
899    select FB_CFB_IMAGEBLIT
900    ---help---
901      Say Y here if you have a PowerVR 2 card in your box. If you plan to
902      run linux on your Dreamcast, you will have to say Y here.
903      This driver may or may not work on other PowerVR 2 cards, but is
904      totally untested. Use at your own risk. If unsure, say N.
905
906      To compile this driver as a module, choose M here: the
907      module will be called pvr2fb.
908
909      You can pass several parameters to the driver at boot time or at
910      module load time. The parameters look like "video=pvr2:XXX", where
911      the meaning of XXX can be found at the end of the main source file
912      (<file:drivers/video/pvr2fb.c>). Please see the file
913      <file:Documentation/fb/pvr2fb.txt>.
914
915config FB_EPSON1355
916    bool "Epson 1355 framebuffer support"
917    depends on (FB = y) && ARCH_CEIVA
918    select FB_CFB_FILLRECT
919    select FB_CFB_COPYAREA
920    select FB_CFB_IMAGEBLIT
921    help
922      Build in support for the SED1355 Epson Research Embedded RAMDAC
923      LCD/CRT Controller (since redesignated as the S1D13505) as a
924      framebuffer. Product specs at
925      <http://www.erd.epson.com/vdc/html/products.htm>.
926
927config FB_S1D13XXX
928    tristate "Epson S1D13XXX framebuffer support"
929    depends on FB
930    select FB_CFB_FILLRECT
931    select FB_CFB_COPYAREA
932    select FB_CFB_IMAGEBLIT
933    help
934      Support for S1D13XXX framebuffer device family (currently only
935      working with S1D13806). Product specs at
936      <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
937
938config FB_ATMEL
939    tristate "AT91/AT32 LCD Controller support"
940    depends on FB && (ARCH_AT91SAM9261 || ARCH_AT91SAM9G10 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 || ARCH_AT91CAP9 || AVR32)
941    select FB_CFB_FILLRECT
942    select FB_CFB_COPYAREA
943    select FB_CFB_IMAGEBLIT
944    help
945      This enables support for the AT91/AT32 LCD Controller.
946
947config FB_INTSRAM
948    bool "Frame Buffer in internal SRAM"
949    depends on FB_ATMEL && ARCH_AT91SAM9261
950    help
951      Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
952      to let frame buffer in external SDRAM.
953
954config FB_ATMEL_STN
955    bool "Use a STN display with AT91/AT32 LCD Controller"
956    depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
957    default n
958    help
959      Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
960      Controller. Say N if you want to connect a TFT.
961
962      If unsure, say N.
963
964config FB_NVIDIA
965    tristate "nVidia Framebuffer Support"
966    depends on FB && PCI
967    select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
968    select FB_MODE_HELPERS
969    select FB_CFB_FILLRECT
970    select FB_CFB_COPYAREA
971    select FB_CFB_IMAGEBLIT
972    select BITREVERSE
973    select VGASTATE
974    help
975      This driver supports graphics boards with the nVidia chips, TNT
976      and newer. For very old chipsets, such as the RIVA128, then use
977      the rivafb.
978      Say Y if you have such a graphics board.
979
980      To compile this driver as a module, choose M here: the
981      module will be called nvidiafb.
982
983config FB_NVIDIA_I2C
984       bool "Enable DDC Support"
985       depends on FB_NVIDIA
986       select FB_DDC
987       help
988      This enables I2C support for nVidia Chipsets. This is used
989      only for getting EDID information from the attached display
990      allowing for robust video mode handling and switching.
991
992      Because fbdev-2.6 requires that drivers must be able to
993      independently validate video mode parameters, you should say Y
994      here.
995
996config FB_NVIDIA_DEBUG
997    bool "Lots of debug output"
998    depends on FB_NVIDIA
999    default n
1000    help
1001      Say Y here if you want the nVidia driver to output all sorts
1002      of debugging information to provide to the maintainer when
1003      something goes wrong.
1004
1005config FB_NVIDIA_BACKLIGHT
1006    bool "Support for backlight control"
1007    depends on FB_NVIDIA
1008    default y
1009    help
1010      Say Y here if you want to control the backlight of your display.
1011
1012config FB_RIVA
1013    tristate "nVidia Riva support"
1014    depends on FB && PCI
1015    select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1016    select FB_MODE_HELPERS
1017    select FB_CFB_FILLRECT
1018    select FB_CFB_COPYAREA
1019    select FB_CFB_IMAGEBLIT
1020    select BITREVERSE
1021    select VGASTATE
1022    help
1023      This driver supports graphics boards with the nVidia Riva/Geforce
1024      chips.
1025      Say Y if you have such a graphics board.
1026
1027      To compile this driver as a module, choose M here: the
1028      module will be called rivafb.
1029
1030config FB_RIVA_I2C
1031       bool "Enable DDC Support"
1032       depends on FB_RIVA
1033       select FB_DDC
1034       help
1035      This enables I2C support for nVidia Chipsets. This is used
1036      only for getting EDID information from the attached display
1037      allowing for robust video mode handling and switching.
1038
1039      Because fbdev-2.6 requires that drivers must be able to
1040      independently validate video mode parameters, you should say Y
1041      here.
1042
1043config FB_RIVA_DEBUG
1044    bool "Lots of debug output"
1045    depends on FB_RIVA
1046    default n
1047    help
1048      Say Y here if you want the Riva driver to output all sorts
1049      of debugging information to provide to the maintainer when
1050      something goes wrong.
1051
1052config FB_RIVA_BACKLIGHT
1053    bool "Support for backlight control"
1054    depends on FB_RIVA
1055    default y
1056    help
1057      Say Y here if you want to control the backlight of your display.
1058
1059config FB_I810
1060    tristate "Intel 810/815 support (EXPERIMENTAL)"
1061    depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1062    select FB_MODE_HELPERS
1063    select FB_CFB_FILLRECT
1064    select FB_CFB_COPYAREA
1065    select FB_CFB_IMAGEBLIT
1066    select VGASTATE
1067    help
1068      This driver supports the on-board graphics built in to the Intel 810
1069          and 815 chipsets. Say Y if you have and plan to use such a board.
1070
1071          To compile this driver as a module, choose M here: the
1072      module will be called i810fb.
1073
1074          For more information, please read
1075      <file:Documentation/fb/intel810.txt>
1076
1077config FB_I810_GTF
1078    bool "use VESA Generalized Timing Formula"
1079    depends on FB_I810
1080    help
1081      If you say Y, then the VESA standard, Generalized Timing Formula
1082          or GTF, will be used to calculate the required video timing values
1083      per video mode. Since the GTF allows nondiscrete timings
1084          (nondiscrete being a range of values as opposed to discrete being a
1085          set of values), you'll be able to use any combination of horizontal
1086      and vertical resolutions, and vertical refresh rates without having
1087      to specify your own timing parameters. This is especially useful
1088      to maximize the performance of an aging display, or if you just
1089          have a display with nonstandard dimensions. A VESA compliant
1090      monitor is recommended, but can still work with non-compliant ones.
1091      If you need or want this, then select this option. The timings may
1092      not be compliant with Intel's recommended values. Use at your own
1093      risk.
1094
1095          If you say N, the driver will revert to discrete video timings
1096      using a set recommended by Intel in their documentation.
1097  
1098          If unsure, say N.
1099
1100config FB_I810_I2C
1101    bool "Enable DDC Support"
1102    depends on FB_I810 && FB_I810_GTF
1103    select FB_DDC
1104    help
1105
1106config FB_LE80578
1107    tristate "Intel LE80578 (Vermilion) support"
1108    depends on FB && PCI && X86
1109    select FB_MODE_HELPERS
1110    select FB_CFB_FILLRECT
1111    select FB_CFB_COPYAREA
1112    select FB_CFB_IMAGEBLIT
1113    help
1114      This driver supports the LE80578 (Vermilion Range) chipset
1115
1116config FB_CARILLO_RANCH
1117    tristate "Intel Carillo Ranch support"
1118    depends on FB_LE80578 && FB && PCI && X86
1119    help
1120      This driver supports the LE80578 (Carillo Ranch) board
1121
1122config FB_INTEL
1123    tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1124    depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1125    select FB_MODE_HELPERS
1126    select FB_CFB_FILLRECT
1127    select FB_CFB_COPYAREA
1128    select FB_CFB_IMAGEBLIT
1129    select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1130    depends on !DRM_I915
1131    help
1132      This driver supports the on-board graphics built in to the Intel
1133          830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1134          Say Y if you have and plan to use such a board.
1135
1136      To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1137
1138      To compile this driver as a module, choose M here: the
1139      module will be called intelfb.
1140
1141      For more information, please read <file:Documentation/fb/intelfb.txt>
1142
1143config FB_INTEL_DEBUG
1144    bool "Intel driver Debug Messages"
1145    depends on FB_INTEL
1146    ---help---
1147      Say Y here if you want the Intel driver to output all sorts
1148      of debugging information to provide to the maintainer when
1149      something goes wrong.
1150
1151config FB_INTEL_I2C
1152    bool "DDC/I2C for Intel framebuffer support"
1153    depends on FB_INTEL
1154    select FB_DDC
1155    default y
1156    help
1157      Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1158
1159config FB_MATROX
1160    tristate "Matrox acceleration"
1161    depends on FB && PCI
1162    select FB_CFB_FILLRECT
1163    select FB_CFB_COPYAREA
1164    select FB_CFB_IMAGEBLIT
1165    select FB_TILEBLITTING
1166    select FB_MACMODES if PPC_PMAC
1167    ---help---
1168      Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1169      Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1170      Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1171      Matrox G400, G450 or G550 card in your box.
1172
1173      To compile this driver as a module, choose M here: the
1174      module will be called matroxfb.
1175
1176      You can pass several parameters to the driver at boot time or at
1177      module load time. The parameters look like "video=matrox:XXX", and
1178      are described in <file:Documentation/fb/matroxfb.txt>.
1179
1180config FB_MATROX_MILLENIUM
1181    bool "Millennium I/II support"
1182    depends on FB_MATROX
1183    help
1184      Say Y here if you have a Matrox Millennium or Matrox Millennium II
1185      video card. If you select "Advanced lowlevel driver options" below,
1186      you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1187      packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1188      also use font widths different from 8.
1189
1190config FB_MATROX_MYSTIQUE
1191    bool "Mystique support"
1192    depends on FB_MATROX
1193    help
1194      Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1195      video card. If you select "Advanced lowlevel driver options" below,
1196      you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1197      packed pixel and 32 bpp packed pixel. You can also use font widths
1198      different from 8.
1199
1200config FB_MATROX_G
1201    bool "G100/G200/G400/G450/G550 support"
1202    depends on FB_MATROX
1203    ---help---
1204      Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1205      video card. If you select "Advanced lowlevel driver options", you
1206      should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1207      pixel and 32 bpp packed pixel. You can also use font widths
1208      different from 8.
1209
1210      If you need support for G400 secondary head, you must say Y to
1211      "Matrox I2C support" and "G400 second head support" right below.
1212      G450/G550 secondary head and digital output are supported without
1213      additional modules.
1214
1215      The driver starts in monitor mode. You must use the matroxset tool
1216      (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1217      swap primary and secondary head outputs, or to change output mode.
1218      Secondary head driver always start in 640x480 resolution and you
1219      must use fbset to change it.
1220
1221      Do not forget that second head supports only 16 and 32 bpp
1222      packed pixels, so it is a good idea to compile them into the kernel
1223      too. You can use only some font widths, as the driver uses generic
1224      painting procedures (the secondary head does not use acceleration
1225      engine).
1226
1227      G450/G550 hardware can display TV picture only from secondary CRTC,
1228      and it performs no scaling, so picture must have 525 or 625 lines.
1229
1230config FB_MATROX_I2C
1231    tristate "Matrox I2C support"
1232    depends on FB_MATROX
1233    select FB_DDC
1234    ---help---
1235      This drivers creates I2C buses which are needed for accessing the
1236      DDC (I2C) bus present on all Matroxes, an I2C bus which
1237      interconnects Matrox optional devices, like MGA-TVO on G200 and
1238      G400, and the secondary head DDC bus, present on G400 only.
1239
1240      You can say Y or M here if you want to experiment with monitor
1241      detection code. You must say Y or M here if you want to use either
1242      second head of G400 or MGA-TVO on G200 or G400.
1243
1244      If you compile it as module, it will create a module named
1245      i2c-matroxfb.
1246
1247config FB_MATROX_MAVEN
1248    tristate "G400 second head support"
1249    depends on FB_MATROX_G && FB_MATROX_I2C
1250    ---help---
1251      WARNING !!! This support does not work with G450 !!!
1252
1253      Say Y or M here if you want to use a secondary head (meaning two
1254      monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1255      head is not compatible with accelerated XFree 3.3.x SVGA servers -
1256      secondary head output is blanked while you are in X. With XFree
1257      3.9.17 preview you can use both heads if you use SVGA over fbdev or
1258      the fbdev driver on first head and the fbdev driver on second head.
1259
1260      If you compile it as module, two modules are created,
1261      matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1262      both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1263      also load i2c-matroxfb to get it to run.
1264
1265      The driver starts in monitor mode and you must use the matroxset
1266      tool (available at
1267      <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1268      PAL or NTSC or to swap primary and secondary head outputs.
1269      Secondary head driver also always start in 640x480 resolution, you
1270      must use fbset to change it.
1271
1272      Also do not forget that second head supports only 16 and 32 bpp
1273      packed pixels, so it is a good idea to compile them into the kernel
1274      too. You can use only some font widths, as the driver uses generic
1275      painting procedures (the secondary head does not use acceleration
1276      engine).
1277
1278config FB_RADEON
1279    tristate "ATI Radeon display support"
1280    depends on FB && PCI
1281    select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1282    select FB_MODE_HELPERS
1283    select FB_CFB_FILLRECT
1284    select FB_CFB_COPYAREA
1285    select FB_CFB_IMAGEBLIT
1286    select FB_MACMODES if PPC_OF
1287    help
1288      Choose this option if you want to use an ATI Radeon graphics card as
1289      a framebuffer device. There are both PCI and AGP versions. You
1290      don't need to choose this to run the Radeon in plain VGA mode.
1291
1292      There is a product page at
1293      http://apps.ati.com/ATIcompare/
1294
1295config FB_RADEON_I2C
1296    bool "DDC/I2C for ATI Radeon support"
1297    depends on FB_RADEON
1298    select FB_DDC
1299    default y
1300    help
1301      Say Y here if you want DDC/I2C support for your Radeon board.
1302
1303config FB_RADEON_BACKLIGHT
1304    bool "Support for backlight control"
1305    depends on FB_RADEON
1306    default y
1307    help
1308      Say Y here if you want to control the backlight of your display.
1309
1310config FB_RADEON_DEBUG
1311    bool "Lots of debug output from Radeon driver"
1312    depends on FB_RADEON
1313    default n
1314    help
1315      Say Y here if you want the Radeon driver to output all sorts
1316      of debugging information to provide to the maintainer when
1317      something goes wrong.
1318
1319config FB_ATY128
1320    tristate "ATI Rage128 display support"
1321    depends on FB && PCI
1322    select FB_CFB_FILLRECT
1323    select FB_CFB_COPYAREA
1324    select FB_CFB_IMAGEBLIT
1325    select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1326    select FB_MACMODES if PPC_PMAC
1327    help
1328      This driver supports graphics boards with the ATI Rage128 chips.
1329      Say Y if you have such a graphics board and read
1330      <file:Documentation/fb/aty128fb.txt>.
1331
1332      To compile this driver as a module, choose M here: the
1333      module will be called aty128fb.
1334
1335config FB_ATY128_BACKLIGHT
1336    bool "Support for backlight control"
1337    depends on FB_ATY128
1338    default y
1339    help
1340      Say Y here if you want to control the backlight of your display.
1341
1342config FB_ATY
1343    tristate "ATI Mach64 display support" if PCI || ATARI
1344    depends on FB && !SPARC32
1345    select FB_CFB_FILLRECT
1346    select FB_CFB_COPYAREA
1347    select FB_CFB_IMAGEBLIT
1348    select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1349    select FB_MACMODES if PPC
1350    help
1351      This driver supports graphics boards with the ATI Mach64 chips.
1352      Say Y if you have such a graphics board.
1353
1354      To compile this driver as a module, choose M here: the
1355      module will be called atyfb.
1356
1357config FB_ATY_CT
1358    bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1359    depends on PCI && FB_ATY
1360    default y if SPARC64 && PCI
1361    help
1362      Say Y here to support use of ATI's 64-bit Rage boards (or other
1363      boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1364      framebuffer device. The ATI product support page for these boards
1365      is at <http://support.ati.com/products/pc/mach64/>.
1366
1367config FB_ATY_GENERIC_LCD
1368    bool "Mach64 generic LCD support (EXPERIMENTAL)"
1369    depends on FB_ATY_CT
1370    help
1371      Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1372      Rage XC, or Rage XL chipset.
1373
1374config FB_ATY_GX
1375    bool "Mach64 GX support" if PCI
1376    depends on FB_ATY
1377    default y if ATARI
1378    help
1379      Say Y here to support use of the ATI Mach64 Graphics Expression
1380      board (or other boards based on the Mach64 GX chipset) as a
1381      framebuffer device. The ATI product support page for these boards
1382      is at
1383      <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1384
1385config FB_ATY_BACKLIGHT
1386    bool "Support for backlight control"
1387    depends on FB_ATY
1388    default y
1389    help
1390      Say Y here if you want to control the backlight of your display.
1391
1392config FB_S3
1393    tristate "S3 Trio/Virge support"
1394    depends on FB && PCI
1395    select FB_CFB_FILLRECT
1396    select FB_CFB_COPYAREA
1397    select FB_CFB_IMAGEBLIT
1398    select FB_TILEBLITTING
1399    select FB_SVGALIB
1400    select VGASTATE
1401    select FONT_8x16 if FRAMEBUFFER_CONSOLE
1402    ---help---
1403      Driver for graphics boards with S3 Trio / S3 Virge chip.
1404
1405config FB_SAVAGE
1406    tristate "S3 Savage support"
1407    depends on FB && PCI && EXPERIMENTAL
1408    select FB_MODE_HELPERS
1409    select FB_CFB_FILLRECT
1410    select FB_CFB_COPYAREA
1411    select FB_CFB_IMAGEBLIT
1412    select VGASTATE
1413    help
1414      This driver supports notebooks and computers with S3 Savage PCI/AGP
1415      chips.
1416
1417      Say Y if you have such a graphics card.
1418
1419      To compile this driver as a module, choose M here; the module
1420      will be called savagefb.
1421
1422config FB_SAVAGE_I2C
1423       bool "Enable DDC2 Support"
1424       depends on FB_SAVAGE
1425       select FB_DDC
1426       help
1427      This enables I2C support for S3 Savage Chipsets. This is used
1428      only for getting EDID information from the attached display
1429      allowing for robust video mode handling and switching.
1430
1431      Because fbdev-2.6 requires that drivers must be able to
1432      independently validate video mode parameters, you should say Y
1433      here.
1434
1435config FB_SAVAGE_ACCEL
1436       bool "Enable Console Acceleration"
1437       depends on FB_SAVAGE
1438       default n
1439       help
1440          This option will compile in console acceleration support. If
1441          the resulting framebuffer console has bothersome glitches, then
1442          choose N here.
1443
1444config FB_SIS
1445    tristate "SiS/XGI display support"
1446    depends on FB && PCI
1447    select FB_CFB_FILLRECT
1448    select FB_CFB_COPYAREA
1449    select FB_CFB_IMAGEBLIT
1450    select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1451    help
1452      This is the frame buffer device driver for the SiS 300, 315, 330
1453      and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1454      Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1455
1456      To compile this driver as a module, choose M here; the module
1457      will be called sisfb.
1458
1459config FB_SIS_300
1460    bool "SiS 300 series support"
1461    depends on FB_SIS
1462    help
1463      Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1464
1465config FB_SIS_315
1466    bool "SiS 315/330/340 series and XGI support"
1467    depends on FB_SIS
1468    help
1469      Say Y here to support use of the SiS 315, 330 and 340 series
1470      (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1471      as XGI V3XT, V5, V8 and Z7.
1472
1473config FB_VIA
1474       tristate "VIA UniChrome (Pro) and Chrome9 display support"
1475       depends on FB && PCI
1476       select FB_CFB_FILLRECT
1477       select FB_CFB_COPYAREA
1478       select FB_CFB_IMAGEBLIT
1479       select FB_SOFT_CURSOR
1480       select I2C_ALGOBIT
1481       select I2C
1482       help
1483      This is the frame buffer device driver for Graphics chips of VIA
1484      UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1485      CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1486       /P4M900,VX800)
1487      Say Y if you have a VIA UniChrome graphics board.
1488
1489      To compile this driver as a module, choose M here: the
1490      module will be called viafb.
1491config FB_NEOMAGIC
1492    tristate "NeoMagic display support"
1493    depends on FB && PCI
1494    select FB_MODE_HELPERS
1495    select FB_CFB_FILLRECT
1496    select FB_CFB_COPYAREA
1497    select FB_CFB_IMAGEBLIT
1498    select VGASTATE
1499    help
1500      This driver supports notebooks with NeoMagic PCI chips.
1501      Say Y if you have such a graphics card.
1502
1503      To compile this driver as a module, choose M here: the
1504      module will be called neofb.
1505
1506config FB_KYRO
1507    tristate "IMG Kyro support"
1508    depends on FB && PCI
1509    select FB_CFB_FILLRECT
1510    select FB_CFB_COPYAREA
1511    select FB_CFB_IMAGEBLIT
1512    help
1513      Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1514      graphics board.
1515
1516      To compile this driver as a module, choose M here: the
1517      module will be called kyrofb.
1518
1519config FB_3DFX
1520    tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1521    depends on FB && PCI
1522    select FB_CFB_IMAGEBLIT
1523    select FB_CFB_FILLRECT
1524    select FB_CFB_COPYAREA
1525    select FB_MODE_HELPERS
1526    help
1527      This driver supports graphics boards with the 3Dfx Banshee,
1528      Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1529      such a graphics board.
1530
1531      To compile this driver as a module, choose M here: the
1532      module will be called tdfxfb.
1533
1534config FB_3DFX_ACCEL
1535    bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1536    depends on FB_3DFX && EXPERIMENTAL
1537    ---help---
1538    This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1539    device driver with acceleration functions.
1540
1541config FB_3DFX_I2C
1542    bool "Enable DDC/I2C support"
1543    depends on FB_3DFX && EXPERIMENTAL
1544    select FB_DDC
1545    default y
1546    help
1547      Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1548
1549config FB_VOODOO1
1550    tristate "3Dfx Voodoo Graphics (sst1) support"
1551    depends on FB && PCI
1552    select FB_CFB_FILLRECT
1553    select FB_CFB_COPYAREA
1554    select FB_CFB_IMAGEBLIT
1555    ---help---
1556      Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1557      Voodoo2 (cvg) based graphics card.
1558
1559      To compile this driver as a module, choose M here: the
1560      module will be called sstfb.
1561
1562      WARNING: Do not use any application that uses the 3D engine
1563      (namely glide) while using this driver.
1564      Please read the <file:Documentation/fb/sstfb.txt> for supported
1565      options and other important info support.
1566
1567config FB_VT8623
1568    tristate "VIA VT8623 support"
1569    depends on FB && PCI
1570    select FB_CFB_FILLRECT
1571    select FB_CFB_COPYAREA
1572    select FB_CFB_IMAGEBLIT
1573    select FB_TILEBLITTING
1574    select FB_SVGALIB
1575    select VGASTATE
1576    select FONT_8x16 if FRAMEBUFFER_CONSOLE
1577    ---help---
1578      Driver for CastleRock integrated graphics core in the
1579      VIA VT8623 [Apollo CLE266] chipset.
1580
1581config FB_TRIDENT
1582    tristate "Trident/CyberXXX/CyberBlade support"
1583    depends on FB && PCI
1584    select FB_CFB_FILLRECT
1585    select FB_CFB_COPYAREA
1586    select FB_CFB_IMAGEBLIT
1587    ---help---
1588      This is the frame buffer device driver for Trident PCI/AGP chipsets.
1589      Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1590      and Blade XP.
1591      There are also integrated versions of these chips called CyberXXXX,
1592      CyberImage or CyberBlade. These chips are mostly found in laptops
1593      but also on some motherboards including early VIA EPIA motherboards.
1594      For more information, read <file:Documentation/fb/tridentfb.txt>
1595
1596      Say Y if you have such a graphics board.
1597
1598      To compile this driver as a module, choose M here: the
1599      module will be called tridentfb.
1600
1601config FB_ARK
1602    tristate "ARK 2000PV support"
1603    depends on FB && PCI
1604    select FB_CFB_FILLRECT
1605    select FB_CFB_COPYAREA
1606    select FB_CFB_IMAGEBLIT
1607    select FB_TILEBLITTING
1608    select FB_SVGALIB
1609    select VGASTATE
1610    select FONT_8x16 if FRAMEBUFFER_CONSOLE
1611    ---help---
1612      Driver for PCI graphics boards with ARK 2000PV chip
1613      and ICS 5342 RAMDAC.
1614
1615config FB_PM3
1616    tristate "Permedia3 support (EXPERIMENTAL)"
1617    depends on FB && PCI && EXPERIMENTAL
1618    select FB_CFB_FILLRECT
1619    select FB_CFB_COPYAREA
1620    select FB_CFB_IMAGEBLIT
1621    help
1622      This is the frame buffer device driver for the 3DLabs Permedia3
1623      chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1624      similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1625      and maybe other boards.
1626
1627config FB_CARMINE
1628    tristate "Fujitsu carmine frame buffer support"
1629    depends on FB && PCI
1630    select FB_CFB_FILLRECT
1631    select FB_CFB_COPYAREA
1632    select FB_CFB_IMAGEBLIT
1633    help
1634      This is the frame buffer device driver for the Fujitsu Carmine chip.
1635      The driver provides two independent frame buffer devices.
1636
1637choice
1638    depends on FB_CARMINE
1639    prompt "DRAM timing"
1640    default FB_CARMINE_DRAM_EVAL
1641
1642config FB_CARMINE_DRAM_EVAL
1643    bool "Eval board timings"
1644    help
1645      Use timings which work on the eval card.
1646
1647config CARMINE_DRAM_CUSTOM
1648    bool "Custom board timings"
1649    help
1650      Use custom board timings.
1651endchoice
1652
1653config FB_AU1100
1654    bool "Au1100 LCD Driver"
1655    depends on (FB = y) && MIPS && SOC_AU1100
1656    select FB_CFB_FILLRECT
1657    select FB_CFB_COPYAREA
1658    select FB_CFB_IMAGEBLIT
1659    help
1660      This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1661      various panels and CRTs by passing in kernel cmd line option
1662      au1100fb:panel=<name>.
1663
1664config FB_AU1200
1665    bool "Au1200 LCD Driver"
1666    depends on (FB = y) && MIPS && SOC_AU1200
1667    select FB_CFB_FILLRECT
1668    select FB_CFB_COPYAREA
1669    select FB_CFB_IMAGEBLIT
1670    help
1671      This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1672      various panels and CRTs by passing in kernel cmd line option
1673      au1200fb:panel=<name>.
1674
1675source "drivers/video/geode/Kconfig"
1676
1677config FB_HIT
1678    tristate "HD64461 Frame Buffer support"
1679    depends on FB && HD64461
1680    select FB_CFB_FILLRECT
1681    select FB_CFB_COPYAREA
1682    select FB_CFB_IMAGEBLIT
1683    help
1684      This is the frame buffer device driver for the Hitachi HD64461 LCD
1685      frame buffer card.
1686
1687config FB_PMAG_AA
1688    bool "PMAG-AA TURBOchannel framebuffer support"
1689    depends on (FB = y) && TC
1690     select FB_CFB_FILLRECT
1691     select FB_CFB_COPYAREA
1692     select FB_CFB_IMAGEBLIT
1693    help
1694      Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1695      used mainly in the MIPS-based DECstation series.
1696
1697config FB_PMAG_BA
1698    tristate "PMAG-BA TURBOchannel framebuffer support"
1699    depends on FB && TC
1700     select FB_CFB_FILLRECT
1701     select FB_CFB_COPYAREA
1702     select FB_CFB_IMAGEBLIT
1703    help
1704      Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1705      used mainly in the MIPS-based DECstation series.
1706
1707config FB_PMAGB_B
1708    tristate "PMAGB-B TURBOchannel framebuffer support"
1709    depends on FB && TC
1710     select FB_CFB_FILLRECT
1711     select FB_CFB_COPYAREA
1712     select FB_CFB_IMAGEBLIT
1713    help
1714      Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1715      in the MIPS-based DECstation series. The card is currently only
1716      supported in 1280x1024x8 mode.
1717
1718config FB_MAXINE
1719    bool "Maxine (Personal DECstation) onboard framebuffer support"
1720    depends on (FB = y) && MACH_DECSTATION
1721     select FB_CFB_FILLRECT
1722     select FB_CFB_COPYAREA
1723     select FB_CFB_IMAGEBLIT
1724    help
1725      Support for the onboard framebuffer (1024x768x8) in the Personal
1726      DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1727      Codename "Maxine").
1728
1729config FB_G364
1730    bool "G364 frame buffer support"
1731    depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1732     select FB_CFB_FILLRECT
1733     select FB_CFB_COPYAREA
1734     select FB_CFB_IMAGEBLIT
1735    help
1736      The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1737      Olivetti M700-10 systems.
1738
1739config FB_68328
1740    bool "Motorola 68328 native frame buffer support"
1741    depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1742     select FB_CFB_FILLRECT
1743     select FB_CFB_COPYAREA
1744     select FB_CFB_IMAGEBLIT
1745    help
1746      Say Y here if you want to support the built-in frame buffer of
1747      the Motorola 68328 CPU family.
1748
1749config FB_PXA168
1750    tristate "PXA168/910 LCD framebuffer support"
1751    depends on FB && (CPU_PXA168 || CPU_PXA910)
1752    select FB_CFB_FILLRECT
1753    select FB_CFB_COPYAREA
1754    select FB_CFB_IMAGEBLIT
1755    ---help---
1756      Frame buffer driver for the built-in LCD controller in the Marvell
1757      MMP processor.
1758
1759config FB_PXA
1760    tristate "PXA LCD framebuffer support"
1761    depends on FB && ARCH_PXA
1762    select FB_CFB_FILLRECT
1763    select FB_CFB_COPYAREA
1764    select FB_CFB_IMAGEBLIT
1765    ---help---
1766      Frame buffer driver for the built-in LCD controller in the Intel
1767      PXA2x0 processor.
1768
1769      This driver is also available as a module ( = code which can be
1770      inserted and removed from the running kernel whenever you want). The
1771      module will be called pxafb. If you want to compile it as a module,
1772      say M here and read <file:Documentation/kbuild/modules.txt>.
1773
1774      If unsure, say N.
1775
1776config FB_PXA_OVERLAY
1777    bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1778    default n
1779    depends on FB_PXA && (PXA27x || PXA3xx)
1780
1781config FB_PXA_SMARTPANEL
1782    bool "PXA Smartpanel LCD support"
1783    default n
1784    depends on FB_PXA
1785
1786config FB_PXA_PARAMETERS
1787    bool "PXA LCD command line parameters"
1788    default n
1789    depends on FB_PXA
1790    ---help---
1791      Enable the use of kernel command line or module parameters
1792      to configure the physical properties of the LCD panel when
1793      using the PXA LCD driver.
1794
1795      This option allows you to override the panel parameters
1796      supplied by the platform in order to support multiple
1797      different models of flatpanel. If you will only be using a
1798      single model of flatpanel then you can safely leave this
1799      option disabled.
1800
1801      <file:Documentation/fb/pxafb.txt> describes the available parameters.
1802
1803config FB_MBX
1804    tristate "2700G LCD framebuffer support"
1805    depends on FB && ARCH_PXA
1806    select FB_CFB_FILLRECT
1807    select FB_CFB_COPYAREA
1808    select FB_CFB_IMAGEBLIT
1809    ---help---
1810      Framebuffer driver for the Intel 2700G (Marathon) Graphics
1811      Accelerator
1812
1813config FB_MBX_DEBUG
1814       bool "Enable debugging info via debugfs"
1815       depends on FB_MBX && DEBUG_FS
1816       default n
1817       ---help---
1818         Enable this if you want debugging information using the debug
1819         filesystem (debugfs)
1820
1821         If unsure, say N.
1822
1823config FB_FSL_DIU
1824    tristate "Freescale DIU framebuffer support"
1825    depends on FB && FSL_SOC
1826    select FB_CFB_FILLRECT
1827    select FB_CFB_COPYAREA
1828    select FB_CFB_IMAGEBLIT
1829    select PPC_LIB_RHEAP
1830    ---help---
1831      Framebuffer driver for the Freescale SoC DIU
1832
1833config FB_W100
1834    tristate "W100 frame buffer support"
1835    depends on FB && ARCH_PXA
1836     select FB_CFB_FILLRECT
1837     select FB_CFB_COPYAREA
1838     select FB_CFB_IMAGEBLIT
1839    ---help---
1840      Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1841      It can also drive the w3220 chip found on iPAQ hx4700.
1842
1843      This driver is also available as a module ( = code which can be
1844      inserted and removed from the running kernel whenever you want). The
1845      module will be called w100fb. If you want to compile it as a module,
1846      say M here and read <file:Documentation/kbuild/modules.txt>.
1847
1848      If unsure, say N.
1849
1850config FB_SH_MOBILE_LCDC
1851    tristate "SuperH Mobile LCDC framebuffer support"
1852    depends on FB && SUPERH && HAVE_CLK
1853    select FB_SYS_FILLRECT
1854    select FB_SYS_COPYAREA
1855    select FB_SYS_IMAGEBLIT
1856    select FB_SYS_FOPS
1857    select FB_DEFERRED_IO
1858    ---help---
1859      Frame buffer driver for the on-chip SH-Mobile LCD controller.
1860
1861config FB_TMIO
1862    tristate "Toshiba Mobile IO FrameBuffer support"
1863    depends on FB && MFD_CORE
1864    select FB_CFB_FILLRECT
1865    select FB_CFB_COPYAREA
1866    select FB_CFB_IMAGEBLIT
1867    ---help---
1868      Frame buffer driver for the Toshiba Mobile IO integrated as found
1869      on the Sharp SL-6000 series
1870
1871      This driver is also available as a module ( = code which can be
1872      inserted and removed from the running kernel whenever you want). The
1873      module will be called tmiofb. If you want to compile it as a module,
1874      say M here and read <file:Documentation/kbuild/modules.txt>.
1875
1876      If unsure, say N.
1877
1878config FB_TMIO_ACCELL
1879    bool "tmiofb acceleration"
1880    depends on FB_TMIO
1881    default y
1882
1883config FB_S3C
1884    tristate "Samsung S3C framebuffer support"
1885    depends on FB && ARCH_S3C64XX
1886    select FB_CFB_FILLRECT
1887    select FB_CFB_COPYAREA
1888    select FB_CFB_IMAGEBLIT
1889    ---help---
1890      Frame buffer driver for the built-in FB controller in the Samsung
1891      SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1892      and the S3C64XX series such as the S3C6400 and S3C6410.
1893
1894      These chips all have the same basic framebuffer design with the
1895      actual capabilities depending on the chip. For instance the S3C6400
1896      and S3C6410 support 4 hardware windows whereas the S3C24XX series
1897      currently only have two.
1898
1899      Currently the support is only for the S3C6400 and S3C6410 SoCs.
1900
1901config FB_S3C_DEBUG_REGWRITE
1902       bool "Debug register writes"
1903       depends on FB_S3C
1904       ---help---
1905         Show all register writes via printk(KERN_DEBUG)
1906
1907config FB_S3C2410
1908    tristate "S3C2410 LCD framebuffer support"
1909    depends on FB && ARCH_S3C2410
1910    select FB_CFB_FILLRECT
1911    select FB_CFB_COPYAREA
1912    select FB_CFB_IMAGEBLIT
1913    ---help---
1914      Frame buffer driver for the built-in LCD controller in the Samsung
1915      S3C2410 processor.
1916
1917      This driver is also available as a module ( = code which can be
1918      inserted and removed from the running kernel whenever you want). The
1919      module will be called s3c2410fb. If you want to compile it as a module,
1920      say M here and read <file:Documentation/kbuild/modules.txt>.
1921
1922      If unsure, say N.
1923config FB_S3C2410_DEBUG
1924    bool "S3C2410 lcd debug messages"
1925    depends on FB_S3C2410
1926    help
1927      Turn on debugging messages. Note that you can set/unset at run time
1928      through sysfs
1929
1930config FB_SM501
1931    tristate "Silicon Motion SM501 framebuffer support"
1932    depends on FB && MFD_SM501
1933    select FB_CFB_FILLRECT
1934    select FB_CFB_COPYAREA
1935    select FB_CFB_IMAGEBLIT
1936    ---help---
1937      Frame buffer driver for the CRT and LCD controllers in the Silicon
1938      Motion SM501.
1939
1940      This driver is also available as a module ( = code which can be
1941      inserted and removed from the running kernel whenever you want). The
1942      module will be called sm501fb. If you want to compile it as a module,
1943      say M here and read <file:Documentation/kbuild/modules.txt>.
1944
1945      If unsure, say N.
1946
1947
1948config FB_PNX4008_DUM
1949    tristate "Display Update Module support on Philips PNX4008 board"
1950    depends on FB && ARCH_PNX4008
1951    ---help---
1952      Say Y here to enable support for PNX4008 Display Update Module (DUM)
1953
1954config FB_PNX4008_DUM_RGB
1955    tristate "RGB Framebuffer support on Philips PNX4008 board"
1956    depends on FB_PNX4008_DUM
1957    select FB_CFB_FILLRECT
1958    select FB_CFB_COPYAREA
1959    select FB_CFB_IMAGEBLIT
1960    ---help---
1961      Say Y here to enable support for PNX4008 RGB Framebuffer
1962
1963config FB_IBM_GXT4500
1964    tristate "Framebuffer support for IBM GXT4500P adaptor"
1965    depends on FB && PPC
1966    select FB_CFB_FILLRECT
1967    select FB_CFB_COPYAREA
1968    select FB_CFB_IMAGEBLIT
1969    ---help---
1970      Say Y here to enable support for the IBM GXT4500P display
1971      adaptor, found on some IBM System P (pSeries) machines.
1972
1973config FB_PS3
1974    tristate "PS3 GPU framebuffer driver"
1975    depends on FB && PS3_PS3AV
1976    select FB_SYS_FILLRECT
1977    select FB_SYS_COPYAREA
1978    select FB_SYS_IMAGEBLIT
1979    select FB_SYS_FOPS
1980    select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
1981    ---help---
1982      Include support for the virtual frame buffer in the PS3 platform.
1983
1984config FB_PS3_DEFAULT_SIZE_M
1985    int "PS3 default frame buffer size (in MiB)"
1986    depends on FB_PS3
1987    default 9
1988    ---help---
1989      This is the default size (in MiB) of the virtual frame buffer in
1990      the PS3.
1991      The default value can be overridden on the kernel command line
1992      using the "ps3fb" option (e.g. "ps3fb=9M");
1993
1994config FB_XILINX
1995    tristate "Xilinx frame buffer support"
1996    depends on FB && (XILINX_VIRTEX || MICROBLAZE)
1997    select FB_CFB_FILLRECT
1998    select FB_CFB_COPYAREA
1999    select FB_CFB_IMAGEBLIT
2000    ---help---
2001      Include support for the Xilinx ML300/ML403 reference design
2002      framebuffer. ML300 carries a 640*480 LCD display on the board,
2003      ML403 uses a standard DB15 VGA connector.
2004
2005config FB_COBALT
2006    tristate "Cobalt server LCD frame buffer support"
2007    depends on FB && MIPS_COBALT
2008
2009config FB_SH7760
2010    bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2011    depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2012        || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2013    select FB_CFB_FILLRECT
2014    select FB_CFB_COPYAREA
2015    select FB_CFB_IMAGEBLIT
2016    ---help---
2017      Support for the SH7760/SH7763/SH7720/SH7721 integrated
2018      (D)STN/TFT LCD Controller.
2019      Supports display resolutions up to 1024x1024 pixel, grayscale and
2020      color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2021      and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2022      panels <= 320 pixel horizontal resolution.
2023
2024config FB_DA8XX
2025    tristate "DA8xx/OMAP-L1xx Framebuffer support"
2026    depends on FB && ARCH_DAVINCI_DA8XX
2027    select FB_CFB_FILLRECT
2028    select FB_CFB_COPYAREA
2029    select FB_CFB_IMAGEBLIT
2030    ---help---
2031      This is the frame buffer device driver for the TI LCD controller
2032      found on DA8xx/OMAP-L1xx SoCs.
2033      If unsure, say N.
2034
2035config FB_VIRTUAL
2036    tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2037    depends on FB
2038    select FB_SYS_FILLRECT
2039    select FB_SYS_COPYAREA
2040    select FB_SYS_IMAGEBLIT
2041    select FB_SYS_FOPS
2042    ---help---
2043      This is a `virtual' frame buffer device. It operates on a chunk of
2044      unswappable kernel memory instead of on the memory of a graphics
2045      board. This means you cannot see any output sent to this frame
2046      buffer device, while it does consume precious memory. The main use
2047      of this frame buffer device is testing and debugging the frame
2048      buffer subsystem. Do NOT enable it for normal systems! To protect
2049      the innocent, it has to be enabled explicitly at boot time using the
2050      kernel option `video=vfb:'.
2051
2052      To compile this driver as a module, choose M here: the
2053      module will be called vfb. In order to load it, you must use
2054      the vfb_enable=1 option.
2055
2056      If unsure, say N.
2057
2058config XEN_FBDEV_FRONTEND
2059    tristate "Xen virtual frame buffer support"
2060    depends on FB && XEN
2061    select FB_SYS_FILLRECT
2062    select FB_SYS_COPYAREA
2063    select FB_SYS_IMAGEBLIT
2064    select FB_SYS_FOPS
2065    select FB_DEFERRED_IO
2066    default y
2067    help
2068      This driver implements the front-end of the Xen virtual
2069      frame buffer driver. It communicates with a back-end
2070      in another domain.
2071
2072config FB_METRONOME
2073    tristate "E-Ink Metronome/8track controller support"
2074    depends on FB
2075    select FB_SYS_FILLRECT
2076    select FB_SYS_COPYAREA
2077    select FB_SYS_IMAGEBLIT
2078    select FB_SYS_FOPS
2079    select FB_DEFERRED_IO
2080    help
2081      This driver implements support for the E-Ink Metronome
2082      controller. The pre-release name for this device was 8track
2083      and could also have been called by some vendors as PVI-nnnn.
2084
2085config FB_MB862XX
2086    tristate "Fujitsu MB862xx GDC support"
2087    depends on FB
2088    select FB_CFB_FILLRECT
2089    select FB_CFB_COPYAREA
2090    select FB_CFB_IMAGEBLIT
2091    ---help---
2092      Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2093
2094config FB_MB862XX_PCI_GDC
2095    bool "Carmine/Coral-P(A) GDC"
2096    depends on PCI && FB_MB862XX
2097    ---help---
2098      This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2099      PCI graphics controller devices.
2100
2101config FB_MB862XX_LIME
2102    bool "Lime GDC"
2103    depends on FB_MB862XX
2104    depends on OF && !FB_MB862XX_PCI_GDC
2105    depends on PPC
2106    select FB_FOREIGN_ENDIAN
2107    select FB_LITTLE_ENDIAN
2108    ---help---
2109      Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2110
2111config FB_EP93XX
2112    tristate "EP93XX frame buffer support"
2113    depends on FB && ARCH_EP93XX
2114    select FB_CFB_FILLRECT
2115    select FB_CFB_COPYAREA
2116    select FB_CFB_IMAGEBLIT
2117    ---help---
2118      Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2119      This driver is also available as a module. The module will be called
2120      ep93xx-fb.
2121
2122config FB_PRE_INIT_FB
2123    bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2124    depends on FB && FB_MB862XX_LIME
2125    ---help---
2126      Select this option if display contents should be inherited as set by
2127      the bootloader.
2128
2129config FB_MSM
2130    tristate
2131    depends on FB && ARCH_MSM
2132    select FB_CFB_FILLRECT
2133    select FB_CFB_COPYAREA
2134    select FB_CFB_IMAGEBLIT
2135    default y
2136
2137config FB_MX3
2138    tristate "MX3 Framebuffer support"
2139    depends on FB && MX3_IPU
2140    select FB_CFB_FILLRECT
2141    select FB_CFB_COPYAREA
2142    select FB_CFB_IMAGEBLIT
2143    default y
2144    help
2145      This is a framebuffer device for the i.MX31 LCD Controller. So
2146      far only synchronous displays are supported. If you plan to use
2147      an LCD display with your i.MX31 system, say Y here.
2148
2149config FB_BROADSHEET
2150    tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2151    depends on FB
2152    select FB_SYS_FILLRECT
2153    select FB_SYS_COPYAREA
2154    select FB_SYS_IMAGEBLIT
2155    select FB_SYS_FOPS
2156    select FB_DEFERRED_IO
2157    help
2158      This driver implements support for the E-Ink Broadsheet
2159      controller. The release name for this device was Epson S1D13521
2160      and could also have been called by other names when coupled with
2161      a bridge adapter.
2162
2163config FB_JZ4740
2164    tristate "JZ47420/JZ4740 LCD framebuffer support"
2165    depends on FB
2166    select FB_SYS_FILLRECT
2167    select FB_SYS_COPYAREA
2168    select FB_SYS_IMAGEBLIT
2169    help
2170      Framebuffer support for the JZ4720 and JZ4740 SoC.
2171
2172source "drivers/video/omap/Kconfig"
2173
2174source "drivers/video/backlight/Kconfig"
2175source "drivers/video/display/Kconfig"
2176
2177if VT
2178    source "drivers/video/console/Kconfig"
2179endif
2180
2181if FB || SGI_NEWPORT_CONSOLE
2182    source "drivers/video/logo/Kconfig"
2183endif
2184
2185endmenu
2186

Archive Download this file



interactive