| blob | 4587087d777ab6a69edb66fd4f661b5017b08404 |
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 config FB_ACORN
171 bool "Acorn VIDC support"
172 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
173 select FB_CFB_FILLRECT
174 select FB_CFB_COPYAREA
175 select FB_CFB_IMAGEBLIT
176 help
177 This is the frame buffer device driver for the Acorn VIDC graphics
178 hardware found in Acorn RISC PCs and other ARM-based machines. If
179 unsure, say N.
181 config FB_CLPS711X
182 bool "CLPS711X LCD support"
183 depends on (FB = y) && ARM && ARCH_CLPS711X
184 select FB_CFB_FILLRECT
185 select FB_CFB_COPYAREA
186 select FB_CFB_IMAGEBLIT
187 help
188 Say Y to enable the Framebuffer driver for the CLPS7111 and
189 EP7212 processors.
191 config FB_SA1100
192 bool "SA-1100 LCD support"
193 depends on (FB = y) && ARM && ARCH_SA1100
194 select FB_CFB_FILLRECT
195 select FB_CFB_COPYAREA
196 select FB_CFB_IMAGEBLIT
197 help
198 This is a framebuffer device for the SA-1100 LCD Controller.
199 See <http://www.linux-fbdev.org/> for information on framebuffer
200 devices.
202 If you plan to use the LCD display with your SA-1100 system, say
203 Y here.
205 config FB_IMX
206 tristate "Motorola i.MX LCD support"
207 depends on FB && ARM && ARCH_IMX
208 select FB_CFB_FILLRECT
209 select FB_CFB_COPYAREA
210 select FB_CFB_IMAGEBLIT
212 config FB_CYBER2000
213 tristate "CyberPro 2000/2010/5000 support"
214 depends on FB && PCI && (BROKEN || !SPARC64)
215 select FB_CFB_FILLRECT
216 select FB_CFB_COPYAREA
217 select FB_CFB_IMAGEBLIT
218 help
219 This enables support for the Integraphics CyberPro 20x0 and 5000
220 VGA chips used in the Rebel.com Netwinder and other machines.
221 Say Y if you have a NetWinder or a graphics card containing this
222 device, otherwise say N.
224 config FB_APOLLO
225 bool
226 depends on (FB = y) && APOLLO
227 default y
228 select FB_CFB_FILLRECT
229 select FB_CFB_IMAGEBLIT
231 config FB_Q40
232 bool
233 depends on (FB = y) && Q40
234 default y
235 select FB_CFB_FILLRECT
236 select FB_CFB_COPYAREA
237 select FB_CFB_IMAGEBLIT
239 config FB_AMIGA
240 tristate "Amiga native chipset support"
241 depends on FB && AMIGA
242 help
243 This is the frame buffer device driver for the builtin graphics
244 chipset found in Amigas.
246 To compile this driver as a module, choose M here: the
247 module will be called amifb.
249 config FB_AMIGA_OCS
250 bool "Amiga OCS chipset support"
251 depends on FB_AMIGA
252 help
253 This enables support for the original Agnus and Denise video chips,
254 found in the Amiga 1000 and most A500's and A2000's. If you intend
255 to run Linux on any of these systems, say Y; otherwise say N.
257 config FB_AMIGA_ECS
258 bool "Amiga ECS chipset support"
259 depends on FB_AMIGA
260 help
261 This enables support for the Enhanced Chip Set, found in later
262 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
263 you intend to run Linux on any of these systems, say Y; otherwise
264 say N.
266 config FB_AMIGA_AGA
267 bool "Amiga AGA chipset support"
268 depends on FB_AMIGA
269 help
270 This enables support for the Advanced Graphics Architecture (also
271 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
272 and CD32. If you intend to run Linux on any of these systems, say Y;
273 otherwise say N.
275 config FB_CYBER
276 tristate "Amiga CyberVision 64 support"
277 depends on FB && ZORRO && BROKEN
278 select FB_CFB_FILLRECT
279 select FB_CFB_COPYAREA
280 select FB_CFB_IMAGEBLIT
281 help
282 This enables support for the Cybervision 64 graphics card from
283 Phase5. Please note that its use is not all that intuitive (i.e. if
284 you have any questions, be sure to ask!). Say N unless you have a
285 Cybervision 64 or plan to get one before you next recompile the
286 kernel. Please note that this driver DOES NOT support the
287 Cybervision 64/3D card, as they use incompatible video chips.
289 config FB_VIRGE
290 bool "Amiga CyberVision 64/3D support "
291 depends on (FB = y) && ZORRO && BROKEN
292 select FB_CFB_FILLRECT
293 select FB_CFB_COPYAREA
294 select FB_CFB_IMAGEBLIT
295 help
296 This enables support for the Cybervision 64/3D graphics card from
297 Phase5. Please note that its use is not all that intuitive (i.e. if
298 you have any questions, be sure to ask!). Say N unless you have a
299 Cybervision 64/3D or plan to get one before you next recompile the
300 kernel. Please note that this driver DOES NOT support the older
301 Cybervision 64 card, as they use incompatible video chips.
303 config FB_RETINAZ3
304 tristate "Amiga Retina Z3 support"
305 depends on (FB = y) && ZORRO && BROKEN
306 help
307 This enables support for the Retina Z3 graphics card. Say N unless
308 you have a Retina Z3 or plan to get one before you next recompile
309 the kernel.
311 config FB_FM2
312 bool "Amiga FrameMaster II/Rainbow II support"
313 depends on (FB = y) && ZORRO
314 select FB_CFB_FILLRECT
315 select FB_CFB_COPYAREA
316 select FB_CFB_IMAGEBLIT
317 help
318 This is the frame buffer device driver for the Amiga FrameMaster
319 card from BSC (exhibited 1992 but not shipped as a CBM product).
321 config FB_ARC
322 tristate "Arc Monochrome LCD board support"
323 depends on FB && X86
324 select FB_CFB_FILLRECT
325 select FB_CFB_COPYAREA
326 select FB_CFB_IMAGEBLIT
327 help
328 This enables support for the Arc Monochrome LCD board. The board
329 is based on the KS-108 lcd controller and is typically a matrix
330 of 2*n chips. This driver was tested with a 128x64 panel. This
331 driver supports it for use with x86 SBCs through a 16 bit GPIO
332 interface (8 bit data, 8 bit control). If you anticpate using
333 this driver, say Y or M; otherwise say N. You must specify the
334 GPIO IO address to be used for setting control and data.
336 config FB_ATARI
337 bool "Atari native chipset support"
338 depends on (FB = y) && ATARI && BROKEN
339 help
340 This is the frame buffer device driver for the builtin graphics
341 chipset found in Ataris.
343 config FB_OF
344 bool "Open Firmware frame buffer device support"
345 depends on (FB = y) && (PPC64 || PPC_OF)
346 select FB_CFB_FILLRECT
347 select FB_CFB_COPYAREA
348 select FB_CFB_IMAGEBLIT
349 select FB_MACMODES
350 help
351 Say Y if you want support with Open Firmware for your graphics
352 board.
354 config FB_CONTROL
355 bool "Apple \"control\" display support"
356 depends on (FB = y) && PPC_PMAC
357 select FB_CFB_FILLRECT
358 select FB_CFB_COPYAREA
359 select FB_CFB_IMAGEBLIT
360 select FB_MACMODES
361 help
362 This driver supports a frame buffer for the graphics adapter in the
363 Power Macintosh 7300 and others.
365 config FB_PLATINUM
366 bool "Apple \"platinum\" display support"
367 depends on (FB = y) && PPC_PMAC
368 select FB_CFB_FILLRECT
369 select FB_CFB_COPYAREA
370 select FB_CFB_IMAGEBLIT
371 select FB_MACMODES
372 help
373 This driver supports a frame buffer for the "platinum" graphics
374 adapter in some Power Macintoshes.
376 config FB_VALKYRIE
377 bool "Apple \"valkyrie\" display support"
378 depends on (FB = y) && (MAC || PPC_PMAC)
379 select FB_CFB_FILLRECT
380 select FB_CFB_COPYAREA
381 select FB_CFB_IMAGEBLIT
382 select FB_MACMODES
383 help
384 This driver supports a frame buffer for the "valkyrie" graphics
385 adapter in some Power Macintoshes.
387 config FB_CT65550
388 bool "Chips 65550 display support"
389 depends on (FB = y) && PPC
390 select FB_CFB_FILLRECT
391 select FB_CFB_COPYAREA
392 select FB_CFB_IMAGEBLIT
393 help
394 This is the frame buffer device driver for the Chips & Technologies
395 65550 graphics chip in PowerBooks.
397 config FB_ASILIANT
398 bool "Asiliant (Chips) 69000 display support"
399 depends on (FB = y) && PCI
400 select FB_CFB_FILLRECT
401 select FB_CFB_COPYAREA
402 select FB_CFB_IMAGEBLIT
403 help
404 This is the frame buffer device driver for the Asiliant 69030 chipset
406 config FB_IMSTT
407 bool "IMS Twin Turbo display support"
408 depends on (FB = y) && PCI
409 select FB_CFB_IMAGEBLIT
410 select FB_MACMODES if PPC
411 help
412 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
413 many Macintosh and compatible computers.
415 config FB_VGA16
416 tristate "VGA 16-color graphics support"
417 depends on FB && (X86 || PPC)
418 select FB_CFB_FILLRECT
419 select FB_CFB_COPYAREA
420 select FB_CFB_IMAGEBLIT
421 help
422 This is the frame buffer device driver for VGA 16 color graphic
423 cards. Say Y if you have such a card.
425 To compile this driver as a module, choose M here: the
426 module will be called vga16fb.
428 config FB_STI
429 tristate "HP STI frame buffer device support"
430 depends on FB && PARISC
431 select FB_CFB_FILLRECT
432 select FB_CFB_COPYAREA
433 select FB_CFB_IMAGEBLIT
434 default y
435 ---help---
436 STI refers to the HP "Standard Text Interface" which is a set of
437 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
438 Enabling this option will implement the linux framebuffer device
439 using calls to the STI BIOS routines for initialisation.
441 If you enable this option, you will get a planar framebuffer device
442 /dev/fb which will work on the most common HP graphic cards of the
443 NGLE family, including the artist chips (in the 7xx and Bxxx series),
444 HCRX, HCRX24, CRX, CRX24 and VisEG series.
446 It is safe to enable this option, so you should probably say "Y".
448 config FB_MAC
449 bool "Generic Macintosh display support"
450 depends on (FB = y) && MAC
451 select FB_CFB_FILLRECT
452 select FB_CFB_COPYAREA
453 select FB_CFB_IMAGEBLIT
454 select FB_MACMODES
456 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
457 config FB_HP300
458 bool
459 depends on (FB = y) && HP300
460 select FB_CFB_FILLRECT
461 select FB_CFB_IMAGEBLIT
462 default y
464 config FB_TGA
465 tristate "TGA framebuffer support"
466 depends on FB && ALPHA
467 select FB_CFB_FILLRECT
468 select FB_CFB_COPYAREA
469 select FB_CFB_IMAGEBLIT
470 help
471 This is the frame buffer device driver for generic TGA graphic
472 cards. Say Y if you have one of those.
474 config FB_VESA
475 bool "VESA VGA graphics support"
476 depends on (FB = y) && X86
477 select FB_CFB_FILLRECT
478 select FB_CFB_COPYAREA
479 select FB_CFB_IMAGEBLIT
480 help
481 This is the frame buffer device driver for generic VESA 2.0
482 compliant graphic cards. The older VESA 1.2 cards are not supported.
483 You will get a boot time penguin logo at no additional cost. Please
484 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
486 config VIDEO_SELECT
487 bool
488 depends on FB_VESA
489 default y
491 config FB_HGA
492 tristate "Hercules mono graphics support"
493 depends on FB && X86
494 select FB_CFB_FILLRECT
495 select FB_CFB_COPYAREA
496 select FB_CFB_IMAGEBLIT
497 help
498 Say Y here if you have a Hercules mono graphics card.
500 To compile this driver as a module, choose M here: the
501 module will be called hgafb.
503 As this card technology is 15 years old, most people will answer N
504 here.
506 config FB_HGA_ACCEL
507 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
508 depends on FB_HGA && EXPERIMENTAL
509 ---help---
510 This will compile the Hercules mono graphics with
511 acceleration functions.
514 config VIDEO_SELECT
515 bool
516 depends on (FB = y) && X86
517 default y
519 config FB_SGIVW
520 tristate "SGI Visual Workstation framebuffer support"
521 depends on FB && X86_VISWS
522 select FB_CFB_FILLRECT
523 select FB_CFB_COPYAREA
524 select FB_CFB_IMAGEBLIT
525 help
526 SGI Visual Workstation support for framebuffer graphics.
528 config FB_GBE
529 bool "SGI Graphics Backend frame buffer support"
530 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
531 select FB_CFB_FILLRECT
532 select FB_CFB_COPYAREA
533 select FB_CFB_IMAGEBLIT
534 help
535 This is the frame buffer device driver for SGI Graphics Backend.
536 This chip is used in SGI O2 and Visual Workstation 320/540.
538 config FB_GBE_MEM
539 int "Video memory size in MB"
540 depends on FB_GBE
541 default 4
542 help
543 This is the amount of memory reserved for the framebuffer,
544 which can be any value between 1MB and 8MB.
546 config FB_SUN3
547 bool "Sun3 framebuffer support"
548 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
550 config FB_SBUS
551 bool "SBUS and UPA framebuffers"
552 depends on (FB = y) && SPARC
553 help
554 Say Y if you want support for SBUS or UPA based frame buffer device.
556 config FB_BW2
557 bool "BWtwo support"
558 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
559 select FB_CFB_FILLRECT
560 select FB_CFB_COPYAREA
561 select FB_CFB_IMAGEBLIT
562 help
563 This is the frame buffer device driver for the BWtwo frame buffer.
565 config FB_CG3
566 bool "CGthree support"
567 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
568 select FB_CFB_FILLRECT
569 select FB_CFB_COPYAREA
570 select FB_CFB_IMAGEBLIT
571 help
572 This is the frame buffer device driver for the CGthree frame buffer.
574 config FB_CG6
575 bool "CGsix (GX,TurboGX) support"
576 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
577 select FB_CFB_COPYAREA
578 select FB_CFB_IMAGEBLIT
579 help
580 This is the frame buffer device driver for the CGsix (GX, TurboGX)
581 frame buffer.
583 config FB_PVR2
584 tristate "NEC PowerVR 2 display support"
585 depends on FB && SH_DREAMCAST
586 select FB_CFB_FILLRECT
587 select FB_CFB_COPYAREA
588 select FB_CFB_IMAGEBLIT
589 ---help---
590 Say Y here if you have a PowerVR 2 card in your box. If you plan to
591 run linux on your Dreamcast, you will have to say Y here.
592 This driver may or may not work on other PowerVR 2 cards, but is
593 totally untested. Use at your own risk. If unsure, say N.
595 To compile this driver as a module, choose M here: the
596 module will be called pvr2fb.
598 You can pass several parameters to the driver at boot time or at
599 module load time. The parameters look like "video=pvr2:XXX", where
600 the meaning of XXX can be found at the end of the main source file
601 (<file:drivers/video/pvr2fb.c>). Please see the file
602 <file:Documentation/fb/pvr2fb.txt>.
604 config FB_EPSON1355
605 bool "Epson 1355 framebuffer support"
606 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
607 select FB_CFB_FILLRECT
608 select FB_CFB_COPYAREA
609 select FB_CFB_IMAGEBLIT
610 help
611 Build in support for the SED1355 Epson Research Embedded RAMDAC
612 LCD/CRT Controller (since redesignated as the S1D13505) as a
613 framebuffer. Product specs at
614 <http://www.erd.epson.com/vdc/html/products.htm>.
616 config FB_S1D13XXX
617 tristate "Epson S1D13XXX framebuffer support"
618 depends on FB
619 select FB_CFB_FILLRECT
620 select FB_CFB_COPYAREA
621 select FB_CFB_IMAGEBLIT
622 help
623 Support for S1D13XXX framebuffer device family (currently only
624 working with S1D13806). Product specs at
625 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
627 config FB_NVIDIA
628 tristate "nVidia Framebuffer Support"
629 depends on FB && PCI
630 select I2C_ALGOBIT if FB_NVIDIA_I2C
631 select I2C if FB_NVIDIA_I2C
632 select FB_MODE_HELPERS
633 select FB_CFB_FILLRECT
634 select FB_CFB_COPYAREA
635 select FB_CFB_IMAGEBLIT
636 help
637 This driver supports graphics boards with the nVidia chips, TNT
638 and newer. For very old chipsets, such as the RIVA128, then use
639 the rivafb.
640 Say Y if you have such a graphics board.
642 To compile this driver as a module, choose M here: the
643 module will be called nvidiafb.
645 config FB_NVIDIA_I2C
646 bool "Enable DDC Support"
647 depends on FB_NVIDIA
648 help
649 This enables I2C support for nVidia Chipsets. This is used
650 only for getting EDID information from the attached display
651 allowing for robust video mode handling and switching.
653 Because fbdev-2.6 requires that drivers must be able to
654 independently validate video mode parameters, you should say Y
655 here.
657 config FB_RIVA
658 tristate "nVidia Riva support"
659 depends on FB && PCI
660 select I2C_ALGOBIT if FB_RIVA_I2C
661 select I2C if FB_RIVA_I2C
662 select FB_MODE_HELPERS
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
666 help
667 This driver supports graphics boards with the nVidia Riva/Geforce
668 chips.
669 Say Y if you have such a graphics board.
671 To compile this driver as a module, choose M here: the
672 module will be called rivafb.
674 config FB_RIVA_I2C
675 bool "Enable DDC Support"
676 depends on FB_RIVA
677 help
678 This enables I2C support for nVidia Chipsets. This is used
679 only for getting EDID information from the attached display
680 allowing for robust video mode handling and switching.
682 Because fbdev-2.6 requires that drivers must be able to
683 independently validate video mode parameters, you should say Y
684 here.
686 config FB_RIVA_DEBUG
687 bool "Lots of debug output from Riva(nVidia) driver"
688 depends on FB_RIVA
689 default n
690 help
691 Say Y here if you want the Riva driver to output all sorts
692 of debugging informations to provide to the maintainer when
693 something goes wrong.
695 config FB_I810
696 tristate "Intel 810/815 support (EXPERIMENTAL)"
697 depends on FB && EXPERIMENTAL && PCI && X86_32
698 select AGP
699 select AGP_INTEL
700 select FB_MODE_HELPERS
701 select FB_CFB_FILLRECT
702 select FB_CFB_COPYAREA
703 select FB_CFB_IMAGEBLIT
704 help
705 This driver supports the on-board graphics built in to the Intel 810
706 and 815 chipsets. Say Y if you have and plan to use such a board.
708 To compile this driver as a module, choose M here: the
709 module will be called i810fb.
711 For more information, please read
712 <file:Documentation/fb/intel810.txt>
714 config FB_I810_GTF
715 bool "use VESA Generalized Timing Formula"
716 depends on FB_I810
717 help
718 If you say Y, then the VESA standard, Generalized Timing Formula
719 or GTF, will be used to calculate the required video timing values
720 per video mode. Since the GTF allows nondiscrete timings
721 (nondiscrete being a range of values as opposed to discrete being a
722 set of values), you'll be able to use any combination of horizontal
723 and vertical resolutions, and vertical refresh rates without having
724 to specify your own timing parameters. This is especially useful
725 to maximize the performance of an aging display, or if you just
726 have a display with nonstandard dimensions. A VESA compliant
727 monitor is recommended, but can still work with non-compliant ones.
728 If you need or want this, then select this option. The timings may
729 not be compliant with Intel's recommended values. Use at your own
730 risk.
732 If you say N, the driver will revert to discrete video timings
733 using a set recommended by Intel in their documentation.
735 If unsure, say N.
737 config FB_I810_I2C
738 bool "Enable DDC Support"
739 depends on FB_I810 && FB_I810_GTF
740 select I2C
741 select I2C_ALGOBIT
742 help
744 config FB_INTEL
745 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
746 depends on FB && EXPERIMENTAL && PCI && X86_32
747 select AGP
748 select AGP_INTEL
749 select FB_MODE_HELPERS
750 select FB_CFB_FILLRECT
751 select FB_CFB_COPYAREA
752 select FB_CFB_IMAGEBLIT
753 help
754 This driver supports the on-board graphics built in to the Intel
755 830M/845G/852GM/855GM/865G chipsets.
756 Say Y if you have and plan to use such a board.
758 To compile this driver as a module, choose M here: the
759 module will be called intelfb.
761 config FB_INTEL_DEBUG
762 bool "Intel driver Debug Messages"
763 depends on FB_INTEL
764 ---help---
765 Say Y here if you want the Intel driver to output all sorts
766 of debugging informations to provide to the maintainer when
767 something goes wrong.
769 config FB_MATROX
770 tristate "Matrox acceleration"
771 depends on FB && PCI
772 select FB_CFB_FILLRECT
773 select FB_CFB_COPYAREA
774 select FB_CFB_IMAGEBLIT
775 select FB_TILEBLITTING
776 select FB_MACMODES if PPC_PMAC
777 ---help---
778 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
779 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
780 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
781 Matrox G400, G450 or G550 card in your box.
783 To compile this driver as a module, choose M here: the
784 module will be called matroxfb.
786 You can pass several parameters to the driver at boot time or at
787 module load time. The parameters look like "video=matrox:XXX", and
788 are described in <file:Documentation/fb/matroxfb.txt>.
790 config FB_MATROX_MILLENIUM
791 bool "Millennium I/II support"
792 depends on FB_MATROX
793 help
794 Say Y here if you have a Matrox Millennium or Matrox Millennium II
795 video card. If you select "Advanced lowlevel driver options" below,
796 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
797 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
798 also use font widths different from 8.
800 config FB_MATROX_MYSTIQUE
801 bool "Mystique support"
802 depends on FB_MATROX
803 help
804 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
805 video card. If you select "Advanced lowlevel driver options" below,
806 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
807 packed pixel and 32 bpp packed pixel. You can also use font widths
808 different from 8.
810 config FB_MATROX_G
811 bool "G100/G200/G400/G450/G550 support"
812 depends on FB_MATROX
813 ---help---
814 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
815 video card. If you select "Advanced lowlevel driver options", you
816 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
817 pixel and 32 bpp packed pixel. You can also use font widths
818 different from 8.
820 If you need support for G400 secondary head, you must first say Y to
821 "I2C support" in the character devices section, and then to
822 "Matrox I2C support" and "G400 second head support" here in the
823 framebuffer section. G450/G550 secondary head and digital output
824 are supported without additional modules.
826 The driver starts in monitor mode. You must use the matroxset tool
827 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
828 swap primary and secondary head outputs, or to change output mode.
829 Secondary head driver always start in 640x480 resolution and you
830 must use fbset to change it.
832 Do not forget that second head supports only 16 and 32 bpp
833 packed pixels, so it is a good idea to compile them into the kernel
834 too. You can use only some font widths, as the driver uses generic
835 painting procedures (the secondary head does not use acceleration
836 engine).
838 G450/G550 hardware can display TV picture only from secondary CRTC,
839 and it performs no scaling, so picture must have 525 or 625 lines.
841 config FB_MATROX_I2C
842 tristate "Matrox I2C support"
843 depends on FB_MATROX && I2C
844 select I2C_ALGOBIT
845 ---help---
846 This drivers creates I2C buses which are needed for accessing the
847 DDC (I2C) bus present on all Matroxes, an I2C bus which
848 interconnects Matrox optional devices, like MGA-TVO on G200 and
849 G400, and the secondary head DDC bus, present on G400 only.
851 You can say Y or M here if you want to experiment with monitor
852 detection code. You must say Y or M here if you want to use either
853 second head of G400 or MGA-TVO on G200 or G400.
855 If you compile it as module, it will create a module named
856 i2c-matroxfb.
858 config FB_MATROX_MAVEN
859 tristate "G400 second head support"
860 depends on FB_MATROX_G && FB_MATROX_I2C
861 ---help---
862 WARNING !!! This support does not work with G450 !!!
864 Say Y or M here if you want to use a secondary head (meaning two
865 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
866 head is not compatible with accelerated XFree 3.3.x SVGA servers -
867 secondary head output is blanked while you are in X. With XFree
868 3.9.17 preview you can use both heads if you use SVGA over fbdev or
869 the fbdev driver on first head and the fbdev driver on second head.
871 If you compile it as module, two modules are created,
872 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
873 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
874 also load i2c-matroxfb to get it to run.
876 The driver starts in monitor mode and you must use the matroxset
877 tool (available at
878 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
879 PAL or NTSC or to swap primary and secondary head outputs.
880 Secondary head driver also always start in 640x480 resolution, you
881 must use fbset to change it.
883 Also do not forget that second head supports only 16 and 32 bpp
884 packed pixels, so it is a good idea to compile them into the kernel
885 too. You can use only some font widths, as the driver uses generic
886 painting procedures (the secondary head does not use acceleration
887 engine).
889 config FB_MATROX_MULTIHEAD
890 bool "Multihead support"
891 depends on FB_MATROX
892 ---help---
893 Say Y here if you have more than one (supported) Matrox device in
894 your computer and you want to use all of them for different monitors
895 ("multihead"). If you have only one device, you should say N because
896 the driver compiled with Y is larger and a bit slower, especially on
897 ia32 (ix86).
899 If you said M to "Matrox unified accelerated driver" and N here, you
900 will still be able to use several Matrox devices simultaneously:
901 insert several instances of the module matroxfb into the kernel
902 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
903 for the different Matrox devices. This method is slightly faster but
904 uses 40 KB of kernel memory per Matrox card.
906 There is no need for enabling 'Matrox multihead support' if you have
907 only one Matrox card in the box.
909 config FB_RADEON
910 tristate "ATI Radeon display support"
911 depends on FB && PCI
912 select I2C_ALGOBIT if FB_RADEON_I2C
913 select I2C if FB_RADEON_I2C
914 select FB_MODE_HELPERS
915 select FB_CFB_FILLRECT
916 select FB_CFB_COPYAREA
917 select FB_CFB_IMAGEBLIT
918 select FB_MACMODES if PPC_OF
919 help
920 Choose this option if you want to use an ATI Radeon graphics card as
921 a framebuffer device. There are both PCI and AGP versions. You
922 don't need to choose this to run the Radeon in plain VGA mode.
924 If you say Y here and want DDC/I2C support you must first say Y to
925 "I2C support" and "I2C bit-banging support" in the character devices
926 section.
928 If you say M here then "I2C support" and "I2C bit-banging support"
929 can be build either as modules or built-in.
931 There is a product page at
932 http://apps.ati.com/ATIcompare/
933 config FB_RADEON_I2C
934 bool "DDC/I2C for ATI Radeon support"
935 depends on FB_RADEON
936 default y
937 help
938 Say Y here if you want DDC/I2C support for your Radeon board.
940 config FB_RADEON_DEBUG
941 bool "Lots of debug output from Radeon driver"
942 depends on FB_RADEON
943 default n
944 help
945 Say Y here if you want the Radeon driver to output all sorts
946 of debugging informations to provide to the maintainer when
947 something goes wrong.
949 config FB_ATY128
950 tristate "ATI Rage128 display support"
951 depends on FB && PCI
952 select FB_CFB_FILLRECT
953 select FB_CFB_COPYAREA
954 select FB_CFB_IMAGEBLIT
955 select FB_MACMODES if PPC_PMAC
956 help
957 This driver supports graphics boards with the ATI Rage128 chips.
958 Say Y if you have such a graphics board and read
959 <file:Documentation/fb/aty128fb.txt>.
961 To compile this driver as a module, choose M here: the
962 module will be called aty128fb.
964 config FB_ATY
965 tristate "ATI Mach64 display support" if PCI || ATARI
966 depends on FB && !SPARC32
967 select FB_CFB_FILLRECT
968 select FB_CFB_COPYAREA
969 select FB_CFB_IMAGEBLIT
970 select FB_MACMODES if PPC
971 help
972 This driver supports graphics boards with the ATI Mach64 chips.
973 Say Y if you have such a graphics board.
975 To compile this driver as a module, choose M here: the
976 module will be called atyfb.
978 config FB_ATY_CT
979 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
980 depends on PCI && FB_ATY
981 default y if SPARC64 && FB_PCI
982 help
983 Say Y here to support use of ATI's 64-bit Rage boards (or other
984 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
985 framebuffer device. The ATI product support page for these boards
986 is at <http://support.ati.com/products/pc/mach64/>.
988 config FB_ATY_GENERIC_LCD
989 bool "Mach64 generic LCD support (EXPERIMENTAL)"
990 depends on FB_ATY_CT
991 help
992 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
993 Rage XC, or Rage XL chipset.
995 config FB_ATY_GX
996 bool "Mach64 GX support" if PCI
997 depends on FB_ATY
998 default y if ATARI
999 help
1000 Say Y here to support use of the ATI Mach64 Graphics Expression
1001 board (or other boards based on the Mach64 GX chipset) as a
1002 framebuffer device. The ATI product support page for these boards
1003 is at
1004 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1006 config FB_S3TRIO
1007 bool "S3 Trio display support"
1008 depends on (FB = y) && PPC && BROKEN
1009 help
1010 If you have a S3 Trio say Y. Say N for S3 Virge.
1012 config FB_SAVAGE
1013 tristate "S3 Savage support"
1014 depends on FB && PCI && EXPERIMENTAL
1015 select I2C_ALGOBIT if FB_SAVAGE_I2C
1016 select I2C if FB_SAVAGE_I2C
1017 select FB_MODE_HELPERS
1018 select FB_CFB_FILLRECT
1019 select FB_CFB_COPYAREA
1020 select FB_CFB_IMAGEBLIT
1021 help
1022 This driver supports notebooks and computers with S3 Savage PCI/AGP
1023 chips.
1025 Say Y if you have such a graphics card.
1027 To compile this driver as a module, choose M here; the module
1028 will be called savagefb.
1030 config FB_SAVAGE_I2C
1031 bool "Enable DDC2 Support"
1032 depends on FB_SAVAGE
1033 help
1034 This enables I2C support for S3 Savage Chipsets. This is used
1035 only for getting EDID information from the attached display
1036 allowing for robust video mode handling and switching.
1038 Because fbdev-2.6 requires that drivers must be able to
1039 independently validate video mode parameters, you should say Y
1040 here.
1042 config FB_SAVAGE_ACCEL
1043 bool "Enable Console Acceleration"
1044 depends on FB_SAVAGE
1045 default n
1046 help
1047 This option will compile in console acceleration support. If
1048 the resulting framebuffer console has bothersome glitches, then
1049 choose N here.
1051 config FB_SIS
1052 tristate "SiS/XGI display support"
1053 depends on FB && PCI
1054 select FB_CFB_FILLRECT
1055 select FB_CFB_COPYAREA
1056 select FB_CFB_IMAGEBLIT
1057 help
1058 This is the frame buffer device driver for the SiS 300, 315, 330
1059 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1060 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1062 To compile this driver as a module, choose M here; the module
1063 will be called sisfb.
1065 config FB_SIS_300
1066 bool "SiS 300 series support"
1067 depends on FB_SIS
1068 help
1069 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1071 config FB_SIS_315
1072 bool "SiS 315/330/340 series and XGI support"
1073 depends on FB_SIS
1074 help
1075 Say Y here to support use of the SiS 315, 330 and 340 series
1076 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1077 as XGI V3XT, V5, V8 and Z7.
1079 config FB_NEOMAGIC
1080 tristate "NeoMagic display support"
1081 depends on FB && PCI
1082 select FB_MODE_HELPERS
1083 select FB_CFB_FILLRECT
1084 select FB_CFB_COPYAREA
1085 select FB_CFB_IMAGEBLIT
1086 help
1087 This driver supports notebooks with NeoMagic PCI chips.
1088 Say Y if you have such a graphics card.
1090 To compile this driver as a module, choose M here: the
1091 module will be called neofb.
1093 config FB_KYRO
1094 tristate "IMG Kyro support"
1095 depends on FB && PCI
1096 select FB_CFB_FILLRECT
1097 select FB_CFB_COPYAREA
1098 select FB_CFB_IMAGEBLIT
1099 help
1100 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1101 graphics board.
1103 To compile this driver as a module, choose M here: the
1104 module will be called kyrofb.
1106 config FB_3DFX
1107 tristate "3Dfx Banshee/Voodoo3 display support"
1108 depends on FB && PCI
1109 select FB_CFB_IMAGEBLIT
1110 select FB_CFB_FILLRECT
1111 select FB_CFB_COPYAREA
1112 help
1113 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1114 chips. Say Y if you have such a graphics board.
1116 To compile this driver as a module, choose M here: the
1117 module will be called tdfxfb.
1119 config FB_3DFX_ACCEL
1120 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1121 depends on FB_3DFX && EXPERIMENTAL
1122 ---help---
1123 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1124 with acceleration functions.
1127 config FB_VOODOO1
1128 tristate "3Dfx Voodoo Graphics (sst1) support"
1129 depends on FB && PCI
1130 select FB_CFB_FILLRECT
1131 select FB_CFB_COPYAREA
1132 select FB_CFB_IMAGEBLIT
1133 ---help---
1134 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1135 Voodoo2 (cvg) based graphics card.
1137 To compile this driver as a module, choose M here: the
1138 module will be called sstfb.
1140 WARNING: Do not use any application that uses the 3D engine
1141 (namely glide) while using this driver.
1142 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1143 options and other important info support.
1145 config FB_CYBLA
1146 tristate "Cyberblade/i1 support"
1147 depends on FB && PCI && X86_32 && !64BIT
1148 select FB_CFB_IMAGEBLIT
1149 select VIDEO_SELECT
1150 ---help---
1151 This driver is supposed to support the Trident Cyberblade/i1
1152 graphics core integrated in the VIA VT8601A North Bridge,
1153 also known as VIA Apollo PLE133.
1155 Status:
1156 - Developed, tested and working on EPIA 5000 and EPIA 800.
1157 - Does work reliable on all systems with CRT/LCD connected to
1158 normal VGA ports.
1159 - Should work on systems that do use the internal LCD port, but
1160 this is absolutely not tested.
1162 Character imageblit, copyarea and rectangle fill are hw accelerated,
1163 ypan scrolling is used by default.
1165 Please do read <file:Documentation/fb/cyblafb/*>.
1167 To compile this driver as a module, choose M here: the
1168 module will be called cyblafb.
1170 config FB_TRIDENT
1171 tristate "Trident support"
1172 depends on FB && PCI
1173 select FB_CFB_FILLRECT
1174 select FB_CFB_COPYAREA
1175 select FB_CFB_IMAGEBLIT
1176 ---help---
1177 This driver is supposed to support graphics boards with the
1178 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1179 but also on some motherboards. For more information, read
1180 <file:Documentation/fb/tridentfb.txt>
1182 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1183 instead.
1185 Say Y if you have such a graphics board.
1188 To compile this driver as a module, choose M here: the
1189 module will be called tridentfb.
1191 config FB_TRIDENT_ACCEL
1192 bool "Trident Acceleration functions (EXPERIMENTAL)"
1193 depends on FB_TRIDENT && EXPERIMENTAL
1194 ---help---
1195 This will compile the Trident frame buffer device with
1196 acceleration functions.
1198 config FB_PM3
1199 tristate "Permedia3 support"
1200 depends on FB && PCI && BROKEN
1201 help
1202 This is the frame buffer device driver for the 3DLabs Permedia3
1203 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1204 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1205 and maybe other boards.
1207 config FB_AU1100
1208 bool "Au1100 LCD Driver"
1209 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1211 config FB_AU1200
1212 bool "Au1200 LCD Driver"
1213 depends on FB && MIPS && SOC_AU1200
1214 select FB_CFB_FILLRECT
1215 select FB_CFB_COPYAREA
1216 select FB_CFB_IMAGEBLIT
1217 help
1218 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1219 various panels and CRTs by passing in kernel cmd line option
1220 au1200fb:panel=<name>.
1222 source "drivers/video/geode/Kconfig"
1224 config FB_FFB
1225 bool "Creator/Creator3D/Elite3D support"
1226 depends on FB_SBUS && SPARC64
1227 select FB_CFB_COPYAREA
1228 select FB_CFB_IMAGEBLIT
1229 help
1230 This is the frame buffer device driver for the Creator, Creator3D,
1231 and Elite3D graphics boards.
1233 config FB_TCX
1234 bool "TCX (SS4/SS5 only) support"
1235 depends on FB_SBUS
1236 select FB_CFB_FILLRECT
1237 select FB_CFB_COPYAREA
1238 select FB_CFB_IMAGEBLIT
1239 help
1240 This is the frame buffer device driver for the TCX 24/8bit frame
1241 buffer.
1243 config FB_CG14
1244 bool "CGfourteen (SX) support"
1245 depends on FB_SBUS
1246 select FB_CFB_FILLRECT
1247 select FB_CFB_COPYAREA
1248 select FB_CFB_IMAGEBLIT
1249 help
1250 This is the frame buffer device driver for the CGfourteen frame
1251 buffer on Desktop SPARCsystems with the SX graphics option.
1253 config FB_P9100
1254 bool "P9100 (Sparcbook 3 only) support"
1255 depends on FB_SBUS
1256 select FB_CFB_FILLRECT
1257 select FB_CFB_COPYAREA
1258 select FB_CFB_IMAGEBLIT
1259 help
1260 This is the frame buffer device driver for the P9100 card
1261 supported on Sparcbook 3 machines.
1263 config FB_LEO
1264 bool "Leo (ZX) support"
1265 depends on FB_SBUS
1266 select FB_CFB_FILLRECT
1267 select FB_CFB_COPYAREA
1268 select FB_CFB_IMAGEBLIT
1269 help
1270 This is the frame buffer device driver for the SBUS-based Sun ZX
1271 (leo) frame buffer cards.
1273 config FB_PCI
1274 bool "PCI framebuffers"
1275 depends on (FB = y) && PCI && SPARC
1277 config FB_IGA
1278 bool "IGA 168x display support"
1279 depends on SPARC32 && FB_PCI
1280 select FB_CFB_FILLRECT
1281 select FB_CFB_COPYAREA
1282 select FB_CFB_IMAGEBLIT
1283 help
1284 This is the framebuffer device for the INTERGRAPHICS 1680 and
1285 successor frame buffer cards.
1287 config FB_HIT
1288 tristate "HD64461 Frame Buffer support"
1289 depends on FB && HD64461
1290 select FB_CFB_FILLRECT
1291 select FB_CFB_COPYAREA
1292 select FB_CFB_IMAGEBLIT
1293 help
1294 This is the frame buffer device driver for the Hitachi HD64461 LCD
1295 frame buffer card.
1297 config FB_PMAG_AA
1298 bool "PMAG-AA TURBOchannel framebuffer support"
1299 depends on (FB = y) && TC
1300 select FB_CFB_FILLRECT
1301 select FB_CFB_COPYAREA
1302 select FB_CFB_IMAGEBLIT
1303 help
1304 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1305 used mainly in the MIPS-based DECstation series.
1307 config FB_PMAG_BA
1308 bool "PMAG-BA TURBOchannel framebuffer support"
1309 depends on (FB = y) && TC
1310 select FB_CFB_FILLRECT
1311 select FB_CFB_COPYAREA
1312 select FB_CFB_IMAGEBLIT
1313 help
1314 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1315 used mainly in the MIPS-based DECstation series.
1317 config FB_PMAGB_B
1318 bool "PMAGB-B TURBOchannel framebuffer support"
1319 depends on (FB = y) && TC
1320 select FB_CFB_FILLRECT
1321 select FB_CFB_COPYAREA
1322 select FB_CFB_IMAGEBLIT
1323 help
1324 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1325 in the MIPS-based DECstation series. The card is currently only
1326 supported in 1280x1024x8 mode.
1328 config FB_MAXINE
1329 bool "Maxine (Personal DECstation) onboard framebuffer support"
1330 depends on (FB = y) && MACH_DECSTATION
1331 select FB_CFB_FILLRECT
1332 select FB_CFB_COPYAREA
1333 select FB_CFB_IMAGEBLIT
1334 help
1335 Support for the onboard framebuffer (1024x768x8) in the Personal
1336 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1337 Codename "Maxine").
1339 config FB_TX3912
1340 bool "TMPTX3912/PR31700 frame buffer support"
1341 depends on (FB = y) && NINO
1342 select FB_CFB_FILLRECT
1343 select FB_CFB_COPYAREA
1344 select FB_CFB_IMAGEBLIT
1345 help
1346 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1347 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1349 Say Y here to enable kernel support for the on-board framebuffer.
1351 config FB_G364
1352 bool "G364 frame buffer support"
1353 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1354 select FB_CFB_FILLRECT
1355 select FB_CFB_COPYAREA
1356 select FB_CFB_IMAGEBLIT
1357 help
1358 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1359 Olivetti M700-10 systems.
1361 config FB_68328
1362 bool "Motorola 68328 native frame buffer support"
1363 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1364 select FB_CFB_FILLRECT
1365 select FB_CFB_COPYAREA
1366 select FB_CFB_IMAGEBLIT
1367 help
1368 Say Y here if you want to support the built-in frame buffer of
1369 the Motorola 68328 CPU family.
1371 config FB_PXA
1372 tristate "PXA LCD framebuffer support"
1373 depends on FB && ARCH_PXA
1374 select FB_CFB_FILLRECT
1375 select FB_CFB_COPYAREA
1376 select FB_CFB_IMAGEBLIT
1377 ---help---
1378 Frame buffer driver for the built-in LCD controller in the Intel
1379 PXA2x0 processor.
1381 This driver is also available as a module ( = code which can be
1382 inserted and removed from the running kernel whenever you want). The
1383 module will be called pxafb. If you want to compile it as a module,
1384 say M here and read <file:Documentation/modules.txt>.
1386 If unsure, say N.
1388 config FB_PXA_PARAMETERS
1389 bool "PXA LCD command line parameters"
1390 default n
1391 depends on FB_PXA
1392 ---help---
1393 Enable the use of kernel command line or module parameters
1394 to configure the physical properties of the LCD panel when
1395 using the PXA LCD driver.
1397 This option allows you to override the panel parameters
1398 supplied by the platform in order to support multiple
1399 different models of flatpanel. If you will only be using a
1400 single model of flatpanel then you can safely leave this
1401 option disabled.
1403 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1405 config FB_W100
1406 tristate "W100 frame buffer support"
1407 depends on FB && PXA_SHARPSL
1408 select FB_CFB_FILLRECT
1409 select FB_CFB_COPYAREA
1410 select FB_CFB_IMAGEBLIT
1411 ---help---
1412 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1414 This driver is also available as a module ( = code which can be
1415 inserted and removed from the running kernel whenever you want). The
1416 module will be called w100fb. If you want to compile it as a module,
1417 say M here and read <file:Documentation/modules.txt>.
1419 If unsure, say N.
1421 config FB_S3C2410
1422 tristate "S3C2410 LCD framebuffer support"
1423 depends on FB && ARCH_S3C2410
1424 select FB_CFB_FILLRECT
1425 select FB_CFB_COPYAREA
1426 select FB_CFB_IMAGEBLIT
1427 ---help---
1428 Frame buffer driver for the built-in LCD controller in the Samsung
1429 S3C2410 processor.
1431 This driver is also available as a module ( = code which can be
1432 inserted and removed from the running kernel whenever you want). The
1433 module will be called s3c2410fb. If you want to compile it as a module,
1434 say M here and read <file:Documentation/modules.txt>.
1436 If unsure, say N.
1437 config FB_S3C2410_DEBUG
1438 bool "S3C2410 lcd debug messages"
1439 depends on FB_S3C2410
1440 help
1441 Turn on debugging messages. Note that you can set/unset at run time
1442 through sysfs
1444 config FB_VIRTUAL
1445 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1446 depends on FB
1447 select FB_CFB_FILLRECT
1448 select FB_CFB_COPYAREA
1449 select FB_CFB_IMAGEBLIT
1450 ---help---
1451 This is a `virtual' frame buffer device. It operates on a chunk of
1452 unswappable kernel memory instead of on the memory of a graphics
1453 board. This means you cannot see any output sent to this frame
1454 buffer device, while it does consume precious memory. The main use
1455 of this frame buffer device is testing and debugging the frame
1456 buffer subsystem. Do NOT enable it for normal systems! To protect
1457 the innocent, it has to be enabled explicitly at boot time using the
1458 kernel option `video=vfb:'.
1460 To compile this driver as a module, choose M here: the
1461 module will be called vfb.
1463 If unsure, say N.
1464 if VT
1465 source "drivers/video/console/Kconfig"
1466 endif
1468 if FB || SGI_NEWPORT_CONSOLE
1469 source "drivers/video/logo/Kconfig"
1470 endif
1472 if FB && SYSFS
1473 source "drivers/video/backlight/Kconfig"
1474 endif
1476 endmenu