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