| blob | 5a2840aeb547d26170557c03f531e592391e3091 |
1 #
2 # Video configuration
3 #
5 menu "Graphics support"
7 config FB
8 tristate "Support for frame buffer devices"
9 ---help---
10 The frame buffer device provides an abstraction for the graphics
11 hardware. It represents the frame buffer of some video hardware and
12 allows application software to access the graphics hardware through
13 a well-defined interface, so the software doesn't need to know
14 anything about the low-level (hardware register) stuff.
16 Frame buffer devices work identically across the different
17 architectures supported by Linux and make the implementation of
18 application programs easier and more portable; at this point, an X
19 server exists which uses the frame buffer device exclusively.
20 On several non-X86 architectures, the frame buffer device is the
21 only way to use the graphics hardware.
23 The device is accessed through special device nodes, usually located
24 in the /dev directory, i.e. /dev/fb*.
26 You need an utility program called fbset to make full use of frame
27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
28 and the Framebuffer-HOWTO at
29 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
30 information.
32 Say Y here and to the driver for your graphics board below if you
33 are compiling a kernel for a non-x86 architecture.
35 If you are compiling for the x86 architecture, you can say Y if you
36 want to play with it, but it is not essential. Please note that
37 running graphical applications that directly touch the hardware
38 (e.g. an accelerated X server) and that are not frame buffer
39 device-aware may cause unexpected results. If unsure, say N.
41 config FB_CFB_FILLRECT
42 tristate
43 depends on FB
44 default n
45 ---help---
46 Include the cfb_fillrect function for generic software rectangle
47 filling. This is used by drivers that don't provide their own
48 (accelerated) version.
50 config FB_CFB_COPYAREA
51 tristate
52 depends on FB
53 default n
54 ---help---
55 Include the cfb_copyarea function for generic software area copying.
56 This is used by drivers that don't provide their own (accelerated)
57 version.
59 config FB_CFB_IMAGEBLIT
60 tristate
61 depends on FB
62 default n
63 ---help---
64 Include the cfb_imageblit function for generic software image
65 blitting. This is used by drivers that don't provide their own
66 (accelerated) version.
68 config FB_MACMODES
69 tristate
70 depends on FB
71 default n
73 config FB_FIRMWARE_EDID
74 bool "Enable firmware EDID"
75 depends on FB
76 default y
77 ---help---
78 This enables access to the EDID transferred from the firmware.
79 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
80 transfers do not work for your driver and if you are using
81 nvidiafb, i810fb or savagefb.
83 In general, choosing Y for this option is safe. If you
84 experience extremely long delays while booting before you get
85 something on your display, try setting this to N. Matrox cards in
86 combination with certain motherboards and monitors are known to
87 suffer from this problem.
89 config FB_MODE_HELPERS
90 bool "Enable Video Mode Handling Helpers"
91 depends on FB
92 default n
93 ---help---
94 This enables functions for handling video modes using the
95 Generalized Timing Formula and the EDID parser. A few drivers rely
96 on this feature such as the radeonfb, rivafb, and the i810fb. If
97 your driver does not take advantage of this feature, choosing Y will
98 just increase the kernel size by about 5K.
100 config FB_TILEBLITTING
101 bool "Enable Tile Blitting Support"
102 depends on FB
103 default n
104 ---help---
105 This enables tile blitting. Tile blitting is a drawing technique
106 where the screen is divided into rectangular sections (tiles), whereas
107 the standard blitting divides the screen into pixels. Because the
108 default drawing element is a tile, drawing functions will be passed
109 parameters in terms of number of tiles instead of number of pixels.
110 For example, to draw a single character, instead of using bitmaps,
111 an index to an array of bitmaps will be used. To clear or move a
112 rectangular section of a screen, the rectangle will be described in
113 terms of number of tiles in the x- and y-axis.
115 This is particularly important to one driver, matroxfb. If
116 unsure, say N.
118 config FB_CIRRUS
119 tristate "Cirrus Logic support"
120 depends on FB && (ZORRO || PCI)
121 select FB_CFB_FILLRECT
122 select FB_CFB_COPYAREA
123 select FB_CFB_IMAGEBLIT
124 ---help---
125 This enables support for Cirrus Logic GD542x/543x based boards on
126 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
128 If you have a PCI-based system, this enables support for these
129 chips: GD-543x, GD-544x, GD-5480.
131 Please read the file <file:Documentation/fb/cirrusfb.txt>.
133 Say N unless you have such a graphics board or plan to get one
134 before you next recompile the kernel.
136 config FB_PM2
137 tristate "Permedia2 support"
138 depends on FB && ((AMIGA && BROKEN) || PCI)
139 select FB_CFB_FILLRECT
140 select FB_CFB_COPYAREA
141 select FB_CFB_IMAGEBLIT
142 help
143 This is the frame buffer device driver for the Permedia2 AGP frame
144 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
145 product page at
146 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
148 config FB_PM2_FIFO_DISCONNECT
149 bool "enable FIFO disconnect feature"
150 depends on FB_PM2 && PCI
151 help
152 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
154 config FB_ARMCLCD
155 tristate "ARM PrimeCell PL110 support"
156 depends on FB && ARM && ARM_AMBA
157 select FB_CFB_FILLRECT
158 select FB_CFB_COPYAREA
159 select FB_CFB_IMAGEBLIT
160 help
161 This framebuffer device driver is for the ARM PrimeCell PL110
162 Colour LCD controller. ARM PrimeCells provide the building
163 blocks for System on a Chip devices.
165 If you want to compile this as a module (=code which can be
166 inserted into and removed from the running kernel), say M
167 here and read <file:Documentation/modules.txt>. The module
168 will be called amba-clcd.
170 choice
172 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
173 prompt "LCD Panel"
174 default FB_ARMCLCD_SHARP_LQ035Q7DB02
176 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
177 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
178 help
179 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
180 color QVGA, HRTFT panel. The LogicPD device includes an
181 an integrated HRTFT controller IC.
182 The native resolution is 240x320.
184 config FB_ARMCLCD_SHARP_LQ057Q3DC02
185 bool "LogicPD LCD 5.7\" QVGA"
186 help
187 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
188 color QVGA, TFT panel. The LogicPD device includes an
189 The native resolution is 320x240.
191 config FB_ARMCLCD_SHARP_LQ64D343
192 bool "LogicPD LCD 6.4\" VGA"
193 help
194 This is an implementation of the Sharp LQ64D343, a 6.4"
195 color VGA, TFT panel. The LogicPD device includes an
196 The native resolution is 640x480.
198 config FB_ARMCLCD_SHARP_LQ10D368
199 bool "LogicPD LCD 10.4\" VGA"
200 help
201 This is an implementation of the Sharp LQ10D368, a 10.4"
202 color VGA, TFT panel. The LogicPD device includes an
203 The native resolution is 640x480.
206 config FB_ARMCLCD_SHARP_LQ121S1DG41
207 bool "LogicPD LCD 12.1\" SVGA"
208 help
209 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
210 color SVGA, TFT panel. The LogicPD device includes an
211 The native resolution is 800x600.
213 This panel requires a clock rate may be an integer fraction
214 of the base LCDCLK frequency. The driver will select the
215 highest frequency available that is lower than the maximum
216 allowed. The panel may flicker if the clock rate is
217 slower than the recommended minimum.
219 config FB_ARMCLCD_AUO_A070VW01_WIDE
220 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
221 help
222 This is an implementation of the AU Optronics, a 7.0"
223 WIDE Color. The native resolution is 234x480.
225 config FB_ARMCLCD_HITACHI
226 bool "Hitachi Wide Screen 800x480"
227 help
228 This is an implementation of the Hitachi 800x480.
230 endchoice
233 config FB_ACORN
234 bool "Acorn VIDC support"
235 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
236 select FB_CFB_FILLRECT
237 select FB_CFB_COPYAREA
238 select FB_CFB_IMAGEBLIT
239 help
240 This is the frame buffer device driver for the Acorn VIDC graphics
241 hardware found in Acorn RISC PCs and other ARM-based machines. If
242 unsure, say N.
244 config FB_CLPS711X
245 bool "CLPS711X LCD support"
246 depends on (FB = y) && ARM && ARCH_CLPS711X
247 select FB_CFB_FILLRECT
248 select FB_CFB_COPYAREA
249 select FB_CFB_IMAGEBLIT
250 help
251 Say Y to enable the Framebuffer driver for the CLPS7111 and
252 EP7212 processors.
254 config FB_SA1100
255 bool "SA-1100 LCD support"
256 depends on (FB = y) && ARM && ARCH_SA1100
257 select FB_CFB_FILLRECT
258 select FB_CFB_COPYAREA
259 select FB_CFB_IMAGEBLIT
260 help
261 This is a framebuffer device for the SA-1100 LCD Controller.
262 See <http://www.linux-fbdev.org/> for information on framebuffer
263 devices.
265 If you plan to use the LCD display with your SA-1100 system, say
266 Y here.
268 config FB_IMX
269 tristate "Motorola i.MX LCD support"
270 depends on FB && ARM && ARCH_IMX
271 select FB_CFB_FILLRECT
272 select FB_CFB_COPYAREA
273 select FB_CFB_IMAGEBLIT
275 config FB_CYBER2000
276 tristate "CyberPro 2000/2010/5000 support"
277 depends on FB && PCI && (BROKEN || !SPARC64)
278 select FB_CFB_FILLRECT
279 select FB_CFB_COPYAREA
280 select FB_CFB_IMAGEBLIT
281 help
282 This enables support for the Integraphics CyberPro 20x0 and 5000
283 VGA chips used in the Rebel.com Netwinder and other machines.
284 Say Y if you have a NetWinder or a graphics card containing this
285 device, otherwise say N.
287 config FB_APOLLO
288 bool
289 depends on (FB = y) && APOLLO
290 default y
291 select FB_CFB_FILLRECT
292 select FB_CFB_IMAGEBLIT
294 config FB_Q40
295 bool
296 depends on (FB = y) && Q40
297 default y
298 select FB_CFB_FILLRECT
299 select FB_CFB_COPYAREA
300 select FB_CFB_IMAGEBLIT
302 config FB_AMIGA
303 tristate "Amiga native chipset support"
304 depends on FB && AMIGA
305 help
306 This is the frame buffer device driver for the builtin graphics
307 chipset found in Amigas.
309 To compile this driver as a module, choose M here: the
310 module will be called amifb.
312 config FB_AMIGA_OCS
313 bool "Amiga OCS chipset support"
314 depends on FB_AMIGA
315 help
316 This enables support for the original Agnus and Denise video chips,
317 found in the Amiga 1000 and most A500's and A2000's. If you intend
318 to run Linux on any of these systems, say Y; otherwise say N.
320 config FB_AMIGA_ECS
321 bool "Amiga ECS chipset support"
322 depends on FB_AMIGA
323 help
324 This enables support for the Enhanced Chip Set, found in later
325 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
326 you intend to run Linux on any of these systems, say Y; otherwise
327 say N.
329 config FB_AMIGA_AGA
330 bool "Amiga AGA chipset support"
331 depends on FB_AMIGA
332 help
333 This enables support for the Advanced Graphics Architecture (also
334 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
335 and CD32. If you intend to run Linux on any of these systems, say Y;
336 otherwise say N.
338 config FB_CYBER
339 tristate "Amiga CyberVision 64 support"
340 depends on FB && ZORRO && BROKEN
341 select FB_CFB_FILLRECT
342 select FB_CFB_COPYAREA
343 select FB_CFB_IMAGEBLIT
344 help
345 This enables support for the Cybervision 64 graphics card from
346 Phase5. Please note that its use is not all that intuitive (i.e. if
347 you have any questions, be sure to ask!). Say N unless you have a
348 Cybervision 64 or plan to get one before you next recompile the
349 kernel. Please note that this driver DOES NOT support the
350 Cybervision 64/3D card, as they use incompatible video chips.
352 config FB_VIRGE
353 bool "Amiga CyberVision 64/3D support "
354 depends on (FB = y) && ZORRO && BROKEN
355 select FB_CFB_FILLRECT
356 select FB_CFB_COPYAREA
357 select FB_CFB_IMAGEBLIT
358 help
359 This enables support for the Cybervision 64/3D graphics card from
360 Phase5. Please note that its use is not all that intuitive (i.e. if
361 you have any questions, be sure to ask!). Say N unless you have a
362 Cybervision 64/3D or plan to get one before you next recompile the
363 kernel. Please note that this driver DOES NOT support the older
364 Cybervision 64 card, as they use incompatible video chips.
366 config FB_RETINAZ3
367 tristate "Amiga Retina Z3 support"
368 depends on (FB = y) && ZORRO && BROKEN
369 help
370 This enables support for the Retina Z3 graphics card. Say N unless
371 you have a Retina Z3 or plan to get one before you next recompile
372 the kernel.
374 config FB_FM2
375 bool "Amiga FrameMaster II/Rainbow II support"
376 depends on (FB = y) && ZORRO
377 select FB_CFB_FILLRECT
378 select FB_CFB_COPYAREA
379 select FB_CFB_IMAGEBLIT
380 help
381 This is the frame buffer device driver for the Amiga FrameMaster
382 card from BSC (exhibited 1992 but not shipped as a CBM product).
384 config FB_ARC
385 tristate "Arc Monochrome LCD board support"
386 depends on FB && X86
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
390 help
391 This enables support for the Arc Monochrome LCD board. The board
392 is based on the KS-108 lcd controller and is typically a matrix
393 of 2*n chips. This driver was tested with a 128x64 panel. This
394 driver supports it for use with x86 SBCs through a 16 bit GPIO
395 interface (8 bit data, 8 bit control). If you anticpate using
396 this driver, say Y or M; otherwise say N. You must specify the
397 GPIO IO address to be used for setting control and data.
399 config FB_ATARI
400 bool "Atari native chipset support"
401 depends on (FB = y) && ATARI && BROKEN
402 help
403 This is the frame buffer device driver for the builtin graphics
404 chipset found in Ataris.
406 config FB_OF
407 bool "Open Firmware frame buffer device support"
408 depends on (FB = y) && (PPC64 || PPC_OF)
409 select FB_CFB_FILLRECT
410 select FB_CFB_COPYAREA
411 select FB_CFB_IMAGEBLIT
412 select FB_MACMODES
413 help
414 Say Y if you want support with Open Firmware for your graphics
415 board.
417 config FB_CONTROL
418 bool "Apple \"control\" display support"
419 depends on (FB = y) && PPC_PMAC
420 select FB_CFB_FILLRECT
421 select FB_CFB_COPYAREA
422 select FB_CFB_IMAGEBLIT
423 select FB_MACMODES
424 help
425 This driver supports a frame buffer for the graphics adapter in the
426 Power Macintosh 7300 and others.
428 config FB_PLATINUM
429 bool "Apple \"platinum\" display support"
430 depends on (FB = y) && PPC_PMAC
431 select FB_CFB_FILLRECT
432 select FB_CFB_COPYAREA
433 select FB_CFB_IMAGEBLIT
434 select FB_MACMODES
435 help
436 This driver supports a frame buffer for the "platinum" graphics
437 adapter in some Power Macintoshes.
439 config FB_VALKYRIE
440 bool "Apple \"valkyrie\" display support"
441 depends on (FB = y) && (MAC || PPC_PMAC)
442 select FB_CFB_FILLRECT
443 select FB_CFB_COPYAREA
444 select FB_CFB_IMAGEBLIT
445 select FB_MACMODES
446 help
447 This driver supports a frame buffer for the "valkyrie" graphics
448 adapter in some Power Macintoshes.
450 config FB_CT65550
451 bool "Chips 65550 display support"
452 depends on (FB = y) && PPC
453 select FB_CFB_FILLRECT
454 select FB_CFB_COPYAREA
455 select FB_CFB_IMAGEBLIT
456 help
457 This is the frame buffer device driver for the Chips & Technologies
458 65550 graphics chip in PowerBooks.
460 config FB_ASILIANT
461 bool "Asiliant (Chips) 69000 display support"
462 depends on (FB = y) && PCI
463 select FB_CFB_FILLRECT
464 select FB_CFB_COPYAREA
465 select FB_CFB_IMAGEBLIT
466 help
467 This is the frame buffer device driver for the Asiliant 69030 chipset
469 config FB_IMSTT
470 bool "IMS Twin Turbo display support"
471 depends on (FB = y) && PCI
472 select FB_CFB_IMAGEBLIT
473 select FB_MACMODES if PPC
474 help
475 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
476 many Macintosh and compatible computers.
478 config FB_VGA16
479 tristate "VGA 16-color graphics support"
480 depends on FB && (X86 || PPC)
481 select FB_CFB_FILLRECT
482 select FB_CFB_COPYAREA
483 select FB_CFB_IMAGEBLIT
484 help
485 This is the frame buffer device driver for VGA 16 color graphic
486 cards. Say Y if you have such a card.
488 To compile this driver as a module, choose M here: the
489 module will be called vga16fb.
491 config FB_STI
492 tristate "HP STI frame buffer device support"
493 depends on FB && PARISC
494 select FB_CFB_FILLRECT
495 select FB_CFB_COPYAREA
496 select FB_CFB_IMAGEBLIT
497 default y
498 ---help---
499 STI refers to the HP "Standard Text Interface" which is a set of
500 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
501 Enabling this option will implement the linux framebuffer device
502 using calls to the STI BIOS routines for initialisation.
504 If you enable this option, you will get a planar framebuffer device
505 /dev/fb which will work on the most common HP graphic cards of the
506 NGLE family, including the artist chips (in the 7xx and Bxxx series),
507 HCRX, HCRX24, CRX, CRX24 and VisEG series.
509 It is safe to enable this option, so you should probably say "Y".
511 config FB_MAC
512 bool "Generic Macintosh display support"
513 depends on (FB = y) && MAC
514 select FB_CFB_FILLRECT
515 select FB_CFB_COPYAREA
516 select FB_CFB_IMAGEBLIT
517 select FB_MACMODES
519 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
520 config FB_HP300
521 bool
522 depends on (FB = y) && HP300
523 select FB_CFB_FILLRECT
524 select FB_CFB_IMAGEBLIT
525 default y
527 config FB_TGA
528 tristate "TGA framebuffer support"
529 depends on FB && ALPHA
530 select FB_CFB_FILLRECT
531 select FB_CFB_COPYAREA
532 select FB_CFB_IMAGEBLIT
533 help
534 This is the frame buffer device driver for generic TGA graphic
535 cards. Say Y if you have one of those.
537 config FB_VESA
538 bool "VESA VGA graphics support"
539 depends on (FB = y) && X86
540 select FB_CFB_FILLRECT
541 select FB_CFB_COPYAREA
542 select FB_CFB_IMAGEBLIT
543 help
544 This is the frame buffer device driver for generic VESA 2.0
545 compliant graphic cards. The older VESA 1.2 cards are not supported.
546 You will get a boot time penguin logo at no additional cost. Please
547 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
549 config VIDEO_SELECT
550 bool
551 depends on FB_VESA
552 default y
554 config FB_HGA
555 tristate "Hercules mono graphics support"
556 depends on FB && X86
557 select FB_CFB_FILLRECT
558 select FB_CFB_COPYAREA
559 select FB_CFB_IMAGEBLIT
560 help
561 Say Y here if you have a Hercules mono graphics card.
563 To compile this driver as a module, choose M here: the
564 module will be called hgafb.
566 As this card technology is 15 years old, most people will answer N
567 here.
569 config FB_HGA_ACCEL
570 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
571 depends on FB_HGA && EXPERIMENTAL
572 ---help---
573 This will compile the Hercules mono graphics with
574 acceleration functions.
577 config VIDEO_SELECT
578 bool
579 depends on (FB = y) && X86
580 default y
582 config FB_SGIVW
583 tristate "SGI Visual Workstation framebuffer support"
584 depends on FB && X86_VISWS
585 select FB_CFB_FILLRECT
586 select FB_CFB_COPYAREA
587 select FB_CFB_IMAGEBLIT
588 help
589 SGI Visual Workstation support for framebuffer graphics.
591 config FB_GBE
592 bool "SGI Graphics Backend frame buffer support"
593 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
597 help
598 This is the frame buffer device driver for SGI Graphics Backend.
599 This chip is used in SGI O2 and Visual Workstation 320/540.
601 config FB_GBE_MEM
602 int "Video memory size in MB"
603 depends on FB_GBE
604 default 4
605 help
606 This is the amount of memory reserved for the framebuffer,
607 which can be any value between 1MB and 8MB.
609 config FB_SUN3
610 bool "Sun3 framebuffer support"
611 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
613 config FB_SBUS
614 bool "SBUS and UPA framebuffers"
615 depends on (FB = y) && SPARC
616 help
617 Say Y if you want support for SBUS or UPA based frame buffer device.
619 config FB_BW2
620 bool "BWtwo support"
621 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
622 select FB_CFB_FILLRECT
623 select FB_CFB_COPYAREA
624 select FB_CFB_IMAGEBLIT
625 help
626 This is the frame buffer device driver for the BWtwo frame buffer.
628 config FB_CG3
629 bool "CGthree support"
630 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
631 select FB_CFB_FILLRECT
632 select FB_CFB_COPYAREA
633 select FB_CFB_IMAGEBLIT
634 help
635 This is the frame buffer device driver for the CGthree frame buffer.
637 config FB_CG6
638 bool "CGsix (GX,TurboGX) support"
639 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
640 select FB_CFB_COPYAREA
641 select FB_CFB_IMAGEBLIT
642 help
643 This is the frame buffer device driver for the CGsix (GX, TurboGX)
644 frame buffer.
646 config FB_PVR2
647 tristate "NEC PowerVR 2 display support"
648 depends on FB && SH_DREAMCAST
649 select FB_CFB_FILLRECT
650 select FB_CFB_COPYAREA
651 select FB_CFB_IMAGEBLIT
652 ---help---
653 Say Y here if you have a PowerVR 2 card in your box. If you plan to
654 run linux on your Dreamcast, you will have to say Y here.
655 This driver may or may not work on other PowerVR 2 cards, but is
656 totally untested. Use at your own risk. If unsure, say N.
658 To compile this driver as a module, choose M here: the
659 module will be called pvr2fb.
661 You can pass several parameters to the driver at boot time or at
662 module load time. The parameters look like "video=pvr2:XXX", where
663 the meaning of XXX can be found at the end of the main source file
664 (<file:drivers/video/pvr2fb.c>). Please see the file
665 <file:Documentation/fb/pvr2fb.txt>.
667 config FB_EPSON1355
668 bool "Epson 1355 framebuffer support"
669 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
670 select FB_CFB_FILLRECT
671 select FB_CFB_COPYAREA
672 select FB_CFB_IMAGEBLIT
673 help
674 Build in support for the SED1355 Epson Research Embedded RAMDAC
675 LCD/CRT Controller (since redesignated as the S1D13505) as a
676 framebuffer. Product specs at
677 <http://www.erd.epson.com/vdc/html/products.htm>.
679 config FB_S1D13XXX
680 tristate "Epson S1D13XXX framebuffer support"
681 depends on FB
682 select FB_CFB_FILLRECT
683 select FB_CFB_COPYAREA
684 select FB_CFB_IMAGEBLIT
685 help
686 Support for S1D13XXX framebuffer device family (currently only
687 working with S1D13806). Product specs at
688 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
690 config FB_NVIDIA
691 tristate "nVidia Framebuffer Support"
692 depends on FB && PCI
693 select I2C_ALGOBIT if FB_NVIDIA_I2C
694 select I2C if FB_NVIDIA_I2C
695 select FB_MODE_HELPERS
696 select FB_CFB_FILLRECT
697 select FB_CFB_COPYAREA
698 select FB_CFB_IMAGEBLIT
699 help
700 This driver supports graphics boards with the nVidia chips, TNT
701 and newer. For very old chipsets, such as the RIVA128, then use
702 the rivafb.
703 Say Y if you have such a graphics board.
705 To compile this driver as a module, choose M here: the
706 module will be called nvidiafb.
708 config FB_NVIDIA_I2C
709 bool "Enable DDC Support"
710 depends on FB_NVIDIA
711 help
712 This enables I2C support for nVidia Chipsets. This is used
713 only for getting EDID information from the attached display
714 allowing for robust video mode handling and switching.
716 Because fbdev-2.6 requires that drivers must be able to
717 independently validate video mode parameters, you should say Y
718 here.
720 config FB_RIVA
721 tristate "nVidia Riva support"
722 depends on FB && PCI
723 select I2C_ALGOBIT if FB_RIVA_I2C
724 select I2C if FB_RIVA_I2C
725 select FB_MODE_HELPERS
726 select FB_CFB_FILLRECT
727 select FB_CFB_COPYAREA
728 select FB_CFB_IMAGEBLIT
729 help
730 This driver supports graphics boards with the nVidia Riva/Geforce
731 chips.
732 Say Y if you have such a graphics board.
734 To compile this driver as a module, choose M here: the
735 module will be called rivafb.
737 config FB_RIVA_I2C
738 bool "Enable DDC Support"
739 depends on FB_RIVA
740 help
741 This enables I2C support for nVidia Chipsets. This is used
742 only for getting EDID information from the attached display
743 allowing for robust video mode handling and switching.
745 Because fbdev-2.6 requires that drivers must be able to
746 independently validate video mode parameters, you should say Y
747 here.
749 config FB_RIVA_DEBUG
750 bool "Lots of debug output from Riva(nVidia) driver"
751 depends on FB_RIVA
752 default n
753 help
754 Say Y here if you want the Riva driver to output all sorts
755 of debugging informations to provide to the maintainer when
756 something goes wrong.
758 config FB_I810
759 tristate "Intel 810/815 support (EXPERIMENTAL)"
760 depends on FB && EXPERIMENTAL && PCI && X86_32
761 select AGP
762 select AGP_INTEL
763 select FB_MODE_HELPERS
764 select FB_CFB_FILLRECT
765 select FB_CFB_COPYAREA
766 select FB_CFB_IMAGEBLIT
767 help
768 This driver supports the on-board graphics built in to the Intel 810
769 and 815 chipsets. Say Y if you have and plan to use such a board.
771 To compile this driver as a module, choose M here: the
772 module will be called i810fb.
774 For more information, please read
775 <file:Documentation/fb/intel810.txt>
777 config FB_I810_GTF
778 bool "use VESA Generalized Timing Formula"
779 depends on FB_I810
780 help
781 If you say Y, then the VESA standard, Generalized Timing Formula
782 or GTF, will be used to calculate the required video timing values
783 per video mode. Since the GTF allows nondiscrete timings
784 (nondiscrete being a range of values as opposed to discrete being a
785 set of values), you'll be able to use any combination of horizontal
786 and vertical resolutions, and vertical refresh rates without having
787 to specify your own timing parameters. This is especially useful
788 to maximize the performance of an aging display, or if you just
789 have a display with nonstandard dimensions. A VESA compliant
790 monitor is recommended, but can still work with non-compliant ones.
791 If you need or want this, then select this option. The timings may
792 not be compliant with Intel's recommended values. Use at your own
793 risk.
795 If you say N, the driver will revert to discrete video timings
796 using a set recommended by Intel in their documentation.
798 If unsure, say N.
800 config FB_I810_I2C
801 bool "Enable DDC Support"
802 depends on FB_I810 && FB_I810_GTF
803 select I2C
804 select I2C_ALGOBIT
805 help
807 config FB_INTEL
808 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
809 depends on FB && EXPERIMENTAL && PCI && X86
810 select AGP
811 select AGP_INTEL
812 select FB_MODE_HELPERS
813 select FB_CFB_FILLRECT
814 select FB_CFB_COPYAREA
815 select FB_CFB_IMAGEBLIT
816 help
817 This driver supports the on-board graphics built in to the Intel
818 830M/845G/852GM/855GM/865G chipsets.
819 Say Y if you have and plan to use such a board.
821 To compile this driver as a module, choose M here: the
822 module will be called intelfb.
824 config FB_INTEL_DEBUG
825 bool "Intel driver Debug Messages"
826 depends on FB_INTEL
827 ---help---
828 Say Y here if you want the Intel driver to output all sorts
829 of debugging informations to provide to the maintainer when
830 something goes wrong.
832 config FB_MATROX
833 tristate "Matrox acceleration"
834 depends on FB && PCI
835 select FB_CFB_FILLRECT
836 select FB_CFB_COPYAREA
837 select FB_CFB_IMAGEBLIT
838 select FB_TILEBLITTING
839 select FB_MACMODES if PPC_PMAC
840 ---help---
841 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
842 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
843 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
844 Matrox G400, G450 or G550 card in your box.
846 To compile this driver as a module, choose M here: the
847 module will be called matroxfb.
849 You can pass several parameters to the driver at boot time or at
850 module load time. The parameters look like "video=matrox:XXX", and
851 are described in <file:Documentation/fb/matroxfb.txt>.
853 config FB_MATROX_MILLENIUM
854 bool "Millennium I/II support"
855 depends on FB_MATROX
856 help
857 Say Y here if you have a Matrox Millennium or Matrox Millennium II
858 video card. If you select "Advanced lowlevel driver options" below,
859 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
860 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
861 also use font widths different from 8.
863 config FB_MATROX_MYSTIQUE
864 bool "Mystique support"
865 depends on FB_MATROX
866 help
867 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
868 video card. If you select "Advanced lowlevel driver options" below,
869 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
870 packed pixel and 32 bpp packed pixel. You can also use font widths
871 different from 8.
873 config FB_MATROX_G
874 bool "G100/G200/G400/G450/G550 support"
875 depends on FB_MATROX
876 ---help---
877 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
878 video card. If you select "Advanced lowlevel driver options", you
879 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
880 pixel and 32 bpp packed pixel. You can also use font widths
881 different from 8.
883 If you need support for G400 secondary head, you must first say Y to
884 "I2C support" in the character devices section, and then to
885 "Matrox I2C support" and "G400 second head support" here in the
886 framebuffer section. G450/G550 secondary head and digital output
887 are supported without additional modules.
889 The driver starts in monitor mode. You must use the matroxset tool
890 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
891 swap primary and secondary head outputs, or to change output mode.
892 Secondary head driver always start in 640x480 resolution and you
893 must use fbset to change it.
895 Do not forget that second head supports only 16 and 32 bpp
896 packed pixels, so it is a good idea to compile them into the kernel
897 too. You can use only some font widths, as the driver uses generic
898 painting procedures (the secondary head does not use acceleration
899 engine).
901 G450/G550 hardware can display TV picture only from secondary CRTC,
902 and it performs no scaling, so picture must have 525 or 625 lines.
904 config FB_MATROX_I2C
905 tristate "Matrox I2C support"
906 depends on FB_MATROX && I2C
907 select I2C_ALGOBIT
908 ---help---
909 This drivers creates I2C buses which are needed for accessing the
910 DDC (I2C) bus present on all Matroxes, an I2C bus which
911 interconnects Matrox optional devices, like MGA-TVO on G200 and
912 G400, and the secondary head DDC bus, present on G400 only.
914 You can say Y or M here if you want to experiment with monitor
915 detection code. You must say Y or M here if you want to use either
916 second head of G400 or MGA-TVO on G200 or G400.
918 If you compile it as module, it will create a module named
919 i2c-matroxfb.
921 config FB_MATROX_MAVEN
922 tristate "G400 second head support"
923 depends on FB_MATROX_G && FB_MATROX_I2C
924 ---help---
925 WARNING !!! This support does not work with G450 !!!
927 Say Y or M here if you want to use a secondary head (meaning two
928 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
929 head is not compatible with accelerated XFree 3.3.x SVGA servers -
930 secondary head output is blanked while you are in X. With XFree
931 3.9.17 preview you can use both heads if you use SVGA over fbdev or
932 the fbdev driver on first head and the fbdev driver on second head.
934 If you compile it as module, two modules are created,
935 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
936 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
937 also load i2c-matroxfb to get it to run.
939 The driver starts in monitor mode and you must use the matroxset
940 tool (available at
941 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
942 PAL or NTSC or to swap primary and secondary head outputs.
943 Secondary head driver also always start in 640x480 resolution, you
944 must use fbset to change it.
946 Also do not forget that second head supports only 16 and 32 bpp
947 packed pixels, so it is a good idea to compile them into the kernel
948 too. You can use only some font widths, as the driver uses generic
949 painting procedures (the secondary head does not use acceleration
950 engine).
952 config FB_MATROX_MULTIHEAD
953 bool "Multihead support"
954 depends on FB_MATROX
955 ---help---
956 Say Y here if you have more than one (supported) Matrox device in
957 your computer and you want to use all of them for different monitors
958 ("multihead"). If you have only one device, you should say N because
959 the driver compiled with Y is larger and a bit slower, especially on
960 ia32 (ix86).
962 If you said M to "Matrox unified accelerated driver" and N here, you
963 will still be able to use several Matrox devices simultaneously:
964 insert several instances of the module matroxfb into the kernel
965 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
966 for the different Matrox devices. This method is slightly faster but
967 uses 40 KB of kernel memory per Matrox card.
969 There is no need for enabling 'Matrox multihead support' if you have
970 only one Matrox card in the box.
972 config FB_RADEON
973 tristate "ATI Radeon display support"
974 depends on FB && PCI
975 select I2C_ALGOBIT if FB_RADEON_I2C
976 select I2C if FB_RADEON_I2C
977 select FB_MODE_HELPERS
978 select FB_CFB_FILLRECT
979 select FB_CFB_COPYAREA
980 select FB_CFB_IMAGEBLIT
981 select FB_MACMODES if PPC_OF
982 help
983 Choose this option if you want to use an ATI Radeon graphics card as
984 a framebuffer device. There are both PCI and AGP versions. You
985 don't need to choose this to run the Radeon in plain VGA mode.
987 If you say Y here and want DDC/I2C support you must first say Y to
988 "I2C support" and "I2C bit-banging support" in the character devices
989 section.
991 If you say M here then "I2C support" and "I2C bit-banging support"
992 can be build either as modules or built-in.
994 There is a product page at
995 http://apps.ati.com/ATIcompare/
996 config FB_RADEON_I2C
997 bool "DDC/I2C for ATI Radeon support"
998 depends on FB_RADEON
999 default y
1000 help
1001 Say Y here if you want DDC/I2C support for your Radeon board.
1003 config FB_RADEON_DEBUG
1004 bool "Lots of debug output from Radeon driver"
1005 depends on FB_RADEON
1006 default n
1007 help
1008 Say Y here if you want the Radeon driver to output all sorts
1009 of debugging informations to provide to the maintainer when
1010 something goes wrong.
1012 config FB_ATY128
1013 tristate "ATI Rage128 display support"
1014 depends on FB && PCI
1015 select FB_CFB_FILLRECT
1016 select FB_CFB_COPYAREA
1017 select FB_CFB_IMAGEBLIT
1018 select FB_MACMODES if PPC_PMAC
1019 help
1020 This driver supports graphics boards with the ATI Rage128 chips.
1021 Say Y if you have such a graphics board and read
1022 <file:Documentation/fb/aty128fb.txt>.
1024 To compile this driver as a module, choose M here: the
1025 module will be called aty128fb.
1027 config FB_ATY
1028 tristate "ATI Mach64 display support" if PCI || ATARI
1029 depends on FB && !SPARC32
1030 select FB_CFB_FILLRECT
1031 select FB_CFB_COPYAREA
1032 select FB_CFB_IMAGEBLIT
1033 select FB_MACMODES if PPC
1034 help
1035 This driver supports graphics boards with the ATI Mach64 chips.
1036 Say Y if you have such a graphics board.
1038 To compile this driver as a module, choose M here: the
1039 module will be called atyfb.
1041 config FB_ATY_CT
1042 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1043 depends on PCI && FB_ATY
1044 default y if SPARC64 && FB_PCI
1045 help
1046 Say Y here to support use of ATI's 64-bit Rage boards (or other
1047 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1048 framebuffer device. The ATI product support page for these boards
1049 is at <http://support.ati.com/products/pc/mach64/>.
1051 config FB_ATY_GENERIC_LCD
1052 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1053 depends on FB_ATY_CT
1054 help
1055 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1056 Rage XC, or Rage XL chipset.
1058 config FB_ATY_GX
1059 bool "Mach64 GX support" if PCI
1060 depends on FB_ATY
1061 default y if ATARI
1062 help
1063 Say Y here to support use of the ATI Mach64 Graphics Expression
1064 board (or other boards based on the Mach64 GX chipset) as a
1065 framebuffer device. The ATI product support page for these boards
1066 is at
1067 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1069 config FB_S3TRIO
1070 bool "S3 Trio display support"
1071 depends on (FB = y) && PPC && BROKEN
1072 help
1073 If you have a S3 Trio say Y. Say N for S3 Virge.
1075 config FB_SAVAGE
1076 tristate "S3 Savage support"
1077 depends on FB && PCI && EXPERIMENTAL
1078 select I2C_ALGOBIT if FB_SAVAGE_I2C
1079 select I2C if FB_SAVAGE_I2C
1080 select FB_MODE_HELPERS
1081 select FB_CFB_FILLRECT
1082 select FB_CFB_COPYAREA
1083 select FB_CFB_IMAGEBLIT
1084 help
1085 This driver supports notebooks and computers with S3 Savage PCI/AGP
1086 chips.
1088 Say Y if you have such a graphics card.
1090 To compile this driver as a module, choose M here; the module
1091 will be called savagefb.
1093 config FB_SAVAGE_I2C
1094 bool "Enable DDC2 Support"
1095 depends on FB_SAVAGE
1096 help
1097 This enables I2C support for S3 Savage Chipsets. This is used
1098 only for getting EDID information from the attached display
1099 allowing for robust video mode handling and switching.
1101 Because fbdev-2.6 requires that drivers must be able to
1102 independently validate video mode parameters, you should say Y
1103 here.
1105 config FB_SAVAGE_ACCEL
1106 bool "Enable Console Acceleration"
1107 depends on FB_SAVAGE
1108 default n
1109 help
1110 This option will compile in console acceleration support. If
1111 the resulting framebuffer console has bothersome glitches, then
1112 choose N here.
1114 config FB_SIS
1115 tristate "SiS/XGI display support"
1116 depends on FB && PCI
1117 select FB_CFB_FILLRECT
1118 select FB_CFB_COPYAREA
1119 select FB_CFB_IMAGEBLIT
1120 help
1121 This is the frame buffer device driver for the SiS 300, 315, 330
1122 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1123 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1125 To compile this driver as a module, choose M here; the module
1126 will be called sisfb.
1128 config FB_SIS_300
1129 bool "SiS 300 series support"
1130 depends on FB_SIS
1131 help
1132 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1134 config FB_SIS_315
1135 bool "SiS 315/330/340 series and XGI support"
1136 depends on FB_SIS
1137 help
1138 Say Y here to support use of the SiS 315, 330 and 340 series
1139 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1140 as XGI V3XT, V5, V8 and Z7.
1142 config FB_NEOMAGIC
1143 tristate "NeoMagic display support"
1144 depends on FB && PCI
1145 select FB_MODE_HELPERS
1146 select FB_CFB_FILLRECT
1147 select FB_CFB_COPYAREA
1148 select FB_CFB_IMAGEBLIT
1149 help
1150 This driver supports notebooks with NeoMagic PCI chips.
1151 Say Y if you have such a graphics card.
1153 To compile this driver as a module, choose M here: the
1154 module will be called neofb.
1156 config FB_KYRO
1157 tristate "IMG Kyro support"
1158 depends on FB && PCI
1159 select FB_CFB_FILLRECT
1160 select FB_CFB_COPYAREA
1161 select FB_CFB_IMAGEBLIT
1162 help
1163 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1164 graphics board.
1166 To compile this driver as a module, choose M here: the
1167 module will be called kyrofb.
1169 config FB_3DFX
1170 tristate "3Dfx Banshee/Voodoo3 display support"
1171 depends on FB && PCI
1172 select FB_CFB_IMAGEBLIT
1173 select FB_CFB_FILLRECT
1174 select FB_CFB_COPYAREA
1175 help
1176 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1177 chips. Say Y if you have such a graphics board.
1179 To compile this driver as a module, choose M here: the
1180 module will be called tdfxfb.
1182 config FB_3DFX_ACCEL
1183 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1184 depends on FB_3DFX && EXPERIMENTAL
1185 ---help---
1186 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1187 with acceleration functions.
1190 config FB_VOODOO1
1191 tristate "3Dfx Voodoo Graphics (sst1) support"
1192 depends on FB && PCI
1193 select FB_CFB_FILLRECT
1194 select FB_CFB_COPYAREA
1195 select FB_CFB_IMAGEBLIT
1196 ---help---
1197 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1198 Voodoo2 (cvg) based graphics card.
1200 To compile this driver as a module, choose M here: the
1201 module will be called sstfb.
1203 WARNING: Do not use any application that uses the 3D engine
1204 (namely glide) while using this driver.
1205 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1206 options and other important info support.
1208 config FB_CYBLA
1209 tristate "Cyberblade/i1 support"
1210 depends on FB && PCI && X86_32 && !64BIT
1211 select FB_CFB_IMAGEBLIT
1212 select VIDEO_SELECT
1213 ---help---
1214 This driver is supposed to support the Trident Cyberblade/i1
1215 graphics core integrated in the VIA VT8601A North Bridge,
1216 also known as VIA Apollo PLE133.
1218 Status:
1219 - Developed, tested and working on EPIA 5000 and EPIA 800.
1220 - Does work reliable on all systems with CRT/LCD connected to
1221 normal VGA ports.
1222 - Should work on systems that do use the internal LCD port, but
1223 this is absolutely not tested.
1225 Character imageblit, copyarea and rectangle fill are hw accelerated,
1226 ypan scrolling is used by default.
1228 Please do read <file:Documentation/fb/cyblafb/*>.
1230 To compile this driver as a module, choose M here: the
1231 module will be called cyblafb.
1233 config FB_TRIDENT
1234 tristate "Trident support"
1235 depends on FB && PCI
1236 select FB_CFB_FILLRECT
1237 select FB_CFB_COPYAREA
1238 select FB_CFB_IMAGEBLIT
1239 ---help---
1240 This driver is supposed to support graphics boards with the
1241 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1242 but also on some motherboards. For more information, read
1243 <file:Documentation/fb/tridentfb.txt>
1245 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1246 instead.
1248 Say Y if you have such a graphics board.
1251 To compile this driver as a module, choose M here: the
1252 module will be called tridentfb.
1254 config FB_TRIDENT_ACCEL
1255 bool "Trident Acceleration functions (EXPERIMENTAL)"
1256 depends on FB_TRIDENT && EXPERIMENTAL
1257 ---help---
1258 This will compile the Trident frame buffer device with
1259 acceleration functions.
1261 config FB_PM3
1262 tristate "Permedia3 support"
1263 depends on FB && PCI && BROKEN
1264 help
1265 This is the frame buffer device driver for the 3DLabs Permedia3
1266 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1267 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1268 and maybe other boards.
1270 config FB_AU1100
1271 bool "Au1100 LCD Driver"
1272 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1274 config FB_AU1200
1275 bool "Au1200 LCD Driver"
1276 depends on FB && MIPS && SOC_AU1200
1277 select FB_CFB_FILLRECT
1278 select FB_CFB_COPYAREA
1279 select FB_CFB_IMAGEBLIT
1280 help
1281 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1282 various panels and CRTs by passing in kernel cmd line option
1283 au1200fb:panel=<name>.
1285 source "drivers/video/geode/Kconfig"
1287 config FB_FFB
1288 bool "Creator/Creator3D/Elite3D support"
1289 depends on FB_SBUS && SPARC64
1290 select FB_CFB_COPYAREA
1291 select FB_CFB_IMAGEBLIT
1292 help
1293 This is the frame buffer device driver for the Creator, Creator3D,
1294 and Elite3D graphics boards.
1296 config FB_TCX
1297 bool "TCX (SS4/SS5 only) support"
1298 depends on FB_SBUS
1299 select FB_CFB_FILLRECT
1300 select FB_CFB_COPYAREA
1301 select FB_CFB_IMAGEBLIT
1302 help
1303 This is the frame buffer device driver for the TCX 24/8bit frame
1304 buffer.
1306 config FB_CG14
1307 bool "CGfourteen (SX) support"
1308 depends on FB_SBUS
1309 select FB_CFB_FILLRECT
1310 select FB_CFB_COPYAREA
1311 select FB_CFB_IMAGEBLIT
1312 help
1313 This is the frame buffer device driver for the CGfourteen frame
1314 buffer on Desktop SPARCsystems with the SX graphics option.
1316 config FB_P9100
1317 bool "P9100 (Sparcbook 3 only) support"
1318 depends on FB_SBUS
1319 select FB_CFB_FILLRECT
1320 select FB_CFB_COPYAREA
1321 select FB_CFB_IMAGEBLIT
1322 help
1323 This is the frame buffer device driver for the P9100 card
1324 supported on Sparcbook 3 machines.
1326 config FB_LEO
1327 bool "Leo (ZX) support"
1328 depends on FB_SBUS
1329 select FB_CFB_FILLRECT
1330 select FB_CFB_COPYAREA
1331 select FB_CFB_IMAGEBLIT
1332 help
1333 This is the frame buffer device driver for the SBUS-based Sun ZX
1334 (leo) frame buffer cards.
1336 config FB_PCI
1337 bool "PCI framebuffers"
1338 depends on (FB = y) && PCI && SPARC
1340 config FB_IGA
1341 bool "IGA 168x display support"
1342 depends on SPARC32 && FB_PCI
1343 select FB_CFB_FILLRECT
1344 select FB_CFB_COPYAREA
1345 select FB_CFB_IMAGEBLIT
1346 help
1347 This is the framebuffer device for the INTERGRAPHICS 1680 and
1348 successor frame buffer cards.
1350 config FB_HIT
1351 tristate "HD64461 Frame Buffer support"
1352 depends on FB && HD64461
1353 select FB_CFB_FILLRECT
1354 select FB_CFB_COPYAREA
1355 select FB_CFB_IMAGEBLIT
1356 help
1357 This is the frame buffer device driver for the Hitachi HD64461 LCD
1358 frame buffer card.
1360 config FB_PMAG_AA
1361 bool "PMAG-AA TURBOchannel framebuffer support"
1362 depends on (FB = y) && TC
1363 select FB_CFB_FILLRECT
1364 select FB_CFB_COPYAREA
1365 select FB_CFB_IMAGEBLIT
1366 help
1367 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1368 used mainly in the MIPS-based DECstation series.
1370 config FB_PMAG_BA
1371 bool "PMAG-BA TURBOchannel framebuffer support"
1372 depends on (FB = y) && TC
1373 select FB_CFB_FILLRECT
1374 select FB_CFB_COPYAREA
1375 select FB_CFB_IMAGEBLIT
1376 help
1377 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1378 used mainly in the MIPS-based DECstation series.
1380 config FB_PMAGB_B
1381 bool "PMAGB-B TURBOchannel framebuffer support"
1382 depends on (FB = y) && TC
1383 select FB_CFB_FILLRECT
1384 select FB_CFB_COPYAREA
1385 select FB_CFB_IMAGEBLIT
1386 help
1387 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1388 in the MIPS-based DECstation series. The card is currently only
1389 supported in 1280x1024x8 mode.
1391 config FB_MAXINE
1392 bool "Maxine (Personal DECstation) onboard framebuffer support"
1393 depends on (FB = y) && MACH_DECSTATION
1394 select FB_CFB_FILLRECT
1395 select FB_CFB_COPYAREA
1396 select FB_CFB_IMAGEBLIT
1397 help
1398 Support for the onboard framebuffer (1024x768x8) in the Personal
1399 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1400 Codename "Maxine").
1402 config FB_TX3912
1403 bool "TMPTX3912/PR31700 frame buffer support"
1404 depends on (FB = y) && NINO
1405 select FB_CFB_FILLRECT
1406 select FB_CFB_COPYAREA
1407 select FB_CFB_IMAGEBLIT
1408 help
1409 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1410 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1412 Say Y here to enable kernel support for the on-board framebuffer.
1414 config FB_G364
1415 bool "G364 frame buffer support"
1416 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1417 select FB_CFB_FILLRECT
1418 select FB_CFB_COPYAREA
1419 select FB_CFB_IMAGEBLIT
1420 help
1421 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1422 Olivetti M700-10 systems.
1424 config FB_68328
1425 bool "Motorola 68328 native frame buffer support"
1426 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1427 select FB_CFB_FILLRECT
1428 select FB_CFB_COPYAREA
1429 select FB_CFB_IMAGEBLIT
1430 help
1431 Say Y here if you want to support the built-in frame buffer of
1432 the Motorola 68328 CPU family.
1434 config FB_PXA
1435 tristate "PXA LCD framebuffer support"
1436 depends on FB && ARCH_PXA
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1439 select FB_CFB_IMAGEBLIT
1440 ---help---
1441 Frame buffer driver for the built-in LCD controller in the Intel
1442 PXA2x0 processor.
1444 This driver is also available as a module ( = code which can be
1445 inserted and removed from the running kernel whenever you want). The
1446 module will be called pxafb. If you want to compile it as a module,
1447 say M here and read <file:Documentation/modules.txt>.
1449 If unsure, say N.
1451 config FB_PXA_PARAMETERS
1452 bool "PXA LCD command line parameters"
1453 default n
1454 depends on FB_PXA
1455 ---help---
1456 Enable the use of kernel command line or module parameters
1457 to configure the physical properties of the LCD panel when
1458 using the PXA LCD driver.
1460 This option allows you to override the panel parameters
1461 supplied by the platform in order to support multiple
1462 different models of flatpanel. If you will only be using a
1463 single model of flatpanel then you can safely leave this
1464 option disabled.
1466 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1468 config FB_W100
1469 tristate "W100 frame buffer support"
1470 depends on FB && PXA_SHARPSL
1471 select FB_CFB_FILLRECT
1472 select FB_CFB_COPYAREA
1473 select FB_CFB_IMAGEBLIT
1474 ---help---
1475 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1477 This driver is also available as a module ( = code which can be
1478 inserted and removed from the running kernel whenever you want). The
1479 module will be called w100fb. If you want to compile it as a module,
1480 say M here and read <file:Documentation/modules.txt>.
1482 If unsure, say N.
1484 config FB_S3C2410
1485 tristate "S3C2410 LCD framebuffer support"
1486 depends on FB && ARCH_S3C2410
1487 select FB_CFB_FILLRECT
1488 select FB_CFB_COPYAREA
1489 select FB_CFB_IMAGEBLIT
1490 ---help---
1491 Frame buffer driver for the built-in LCD controller in the Samsung
1492 S3C2410 processor.
1494 This driver is also available as a module ( = code which can be
1495 inserted and removed from the running kernel whenever you want). The
1496 module will be called s3c2410fb. If you want to compile it as a module,
1497 say M here and read <file:Documentation/modules.txt>.
1499 If unsure, say N.
1500 config FB_S3C2410_DEBUG
1501 bool "S3C2410 lcd debug messages"
1502 depends on FB_S3C2410
1503 help
1504 Turn on debugging messages. Note that you can set/unset at run time
1505 through sysfs
1507 config FB_VIRTUAL
1508 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1509 depends on FB
1510 select FB_CFB_FILLRECT
1511 select FB_CFB_COPYAREA
1512 select FB_CFB_IMAGEBLIT
1513 ---help---
1514 This is a `virtual' frame buffer device. It operates on a chunk of
1515 unswappable kernel memory instead of on the memory of a graphics
1516 board. This means you cannot see any output sent to this frame
1517 buffer device, while it does consume precious memory. The main use
1518 of this frame buffer device is testing and debugging the frame
1519 buffer subsystem. Do NOT enable it for normal systems! To protect
1520 the innocent, it has to be enabled explicitly at boot time using the
1521 kernel option `video=vfb:'.
1523 To compile this driver as a module, choose M here: the
1524 module will be called vfb.
1526 If unsure, say N.
1527 if VT
1528 source "drivers/video/console/Kconfig"
1529 endif
1531 if FB || SGI_NEWPORT_CONSOLE
1532 source "drivers/video/logo/Kconfig"
1533 endif
1535 if FB && SYSFS
1536 source "drivers/video/backlight/Kconfig"
1537 endif
1539 endmenu