| blob | 3e153d313bb01457cc54401925f78aad88da734c |
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_MODE_HELPERS
74 bool "Enable Video Mode Handling Helpers"
75 depends on FB
76 default n
77 ---help---
78 This enables functions for handling video modes using the
79 Generalized Timing Formula and the EDID parser. A few drivers rely
80 on this feature such as the radeonfb, rivafb, and the i810fb. If
81 your driver does not take advantage of this feature, choosing Y will
82 just increase the kernel size by about 5K.
84 config FB_TILEBLITTING
85 bool "Enable Tile Blitting Support"
86 depends on FB
87 default n
88 ---help---
89 This enables tile blitting. Tile blitting is a drawing technique
90 where the screen is divided into rectangular sections (tiles), whereas
91 the standard blitting divides the screen into pixels. Because the
92 default drawing element is a tile, drawing functions will be passed
93 parameters in terms of number of tiles instead of number of pixels.
94 For example, to draw a single character, instead of using bitmaps,
95 an index to an array of bitmaps will be used. To clear or move a
96 rectangular section of a screen, the rectangle will be described in
97 terms of number of tiles in the x- and y-axis.
99 This is particularly important to one driver, matroxfb. If
100 unsure, say N.
102 config FB_CIRRUS
103 tristate "Cirrus Logic support"
104 depends on FB && (ZORRO || PCI)
105 select FB_CFB_FILLRECT
106 select FB_CFB_COPYAREA
107 select FB_CFB_IMAGEBLIT
108 ---help---
109 This enables support for Cirrus Logic GD542x/543x based boards on
110 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
112 If you have a PCI-based system, this enables support for these
113 chips: GD-543x, GD-544x, GD-5480.
115 Please read the file <file:Documentation/fb/cirrusfb.txt>.
117 Say N unless you have such a graphics board or plan to get one
118 before you next recompile the kernel.
120 config FB_PM2
121 tristate "Permedia2 support"
122 depends on FB && ((AMIGA && BROKEN) || PCI)
123 select FB_CFB_FILLRECT
124 select FB_CFB_COPYAREA
125 select FB_CFB_IMAGEBLIT
126 help
127 This is the frame buffer device driver for the Permedia2 AGP frame
128 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
129 product page at
130 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
132 config FB_PM2_FIFO_DISCONNECT
133 bool "enable FIFO disconnect feature"
134 depends on FB_PM2 && PCI
135 help
136 Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
138 config FB_ARMCLCD
139 tristate "ARM PrimeCell PL110 support"
140 depends on FB && ARM && ARM_AMBA
141 select FB_CFB_FILLRECT
142 select FB_CFB_COPYAREA
143 select FB_CFB_IMAGEBLIT
144 help
145 This framebuffer device driver is for the ARM PrimeCell PL110
146 Colour LCD controller. ARM PrimeCells provide the building
147 blocks for System on a Chip devices.
149 If you want to compile this as a module (=code which can be
150 inserted into and removed from the running kernel), say M
151 here and read <file:Documentation/modules.txt>. The module
152 will be called amba-clcd.
154 config FB_ACORN
155 bool "Acorn VIDC support"
156 depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
157 select FB_CFB_FILLRECT
158 select FB_CFB_COPYAREA
159 select FB_CFB_IMAGEBLIT
160 help
161 This is the frame buffer device driver for the Acorn VIDC graphics
162 hardware found in Acorn RISC PCs and other ARM-based machines. If
163 unsure, say N.
165 config FB_CLPS711X
166 bool "CLPS711X LCD support"
167 depends on (FB = y) && ARM && ARCH_CLPS711X
168 select FB_CFB_FILLRECT
169 select FB_CFB_COPYAREA
170 select FB_CFB_IMAGEBLIT
171 help
172 Say Y to enable the Framebuffer driver for the CLPS7111 and
173 EP7212 processors.
175 config FB_SA1100
176 bool "SA-1100 LCD support"
177 depends on (FB = y) && ARM && ARCH_SA1100
178 select FB_CFB_FILLRECT
179 select FB_CFB_COPYAREA
180 select FB_CFB_IMAGEBLIT
181 help
182 This is a framebuffer device for the SA-1100 LCD Controller.
183 See <http://www.linux-fbdev.org/> for information on framebuffer
184 devices.
186 If you plan to use the LCD display with your SA-1100 system, say
187 Y here.
189 config FB_IMX
190 tristate "Motorola i.MX LCD support"
191 depends on FB && ARM && ARCH_IMX
192 select FB_CFB_FILLRECT
193 select FB_CFB_COPYAREA
194 select FB_CFB_IMAGEBLIT
196 config FB_CYBER2000
197 tristate "CyberPro 2000/2010/5000 support"
198 depends on FB && PCI && (BROKEN || !SPARC64)
199 select FB_CFB_FILLRECT
200 select FB_CFB_COPYAREA
201 select FB_CFB_IMAGEBLIT
202 help
203 This enables support for the Integraphics CyberPro 20x0 and 5000
204 VGA chips used in the Rebel.com Netwinder and other machines.
205 Say Y if you have a NetWinder or a graphics card containing this
206 device, otherwise say N.
208 config FB_APOLLO
209 bool
210 depends on (FB = y) && APOLLO
211 default y
212 select FB_CFB_FILLRECT
213 select FB_CFB_IMAGEBLIT
215 config FB_Q40
216 bool
217 depends on (FB = y) && Q40
218 default y
219 select FB_CFB_FILLRECT
220 select FB_CFB_COPYAREA
221 select FB_CFB_IMAGEBLIT
223 config FB_AMIGA
224 tristate "Amiga native chipset support"
225 depends on FB && AMIGA
226 help
227 This is the frame buffer device driver for the builtin graphics
228 chipset found in Amigas.
230 To compile this driver as a module, choose M here: the
231 module will be called amifb.
233 config FB_AMIGA_OCS
234 bool "Amiga OCS chipset support"
235 depends on FB_AMIGA
236 help
237 This enables support for the original Agnus and Denise video chips,
238 found in the Amiga 1000 and most A500's and A2000's. If you intend
239 to run Linux on any of these systems, say Y; otherwise say N.
241 config FB_AMIGA_ECS
242 bool "Amiga ECS chipset support"
243 depends on FB_AMIGA
244 help
245 This enables support for the Enhanced Chip Set, found in later
246 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
247 you intend to run Linux on any of these systems, say Y; otherwise
248 say N.
250 config FB_AMIGA_AGA
251 bool "Amiga AGA chipset support"
252 depends on FB_AMIGA
253 help
254 This enables support for the Advanced Graphics Architecture (also
255 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
256 and CD32. If you intend to run Linux on any of these systems, say Y;
257 otherwise say N.
259 config FB_CYBER
260 tristate "Amiga CyberVision 64 support"
261 depends on FB && ZORRO && BROKEN
262 select FB_CFB_FILLRECT
263 select FB_CFB_COPYAREA
264 select FB_CFB_IMAGEBLIT
265 help
266 This enables support for the Cybervision 64 graphics card from
267 Phase5. Please note that its use is not all that intuitive (i.e. if
268 you have any questions, be sure to ask!). Say N unless you have a
269 Cybervision 64 or plan to get one before you next recompile the
270 kernel. Please note that this driver DOES NOT support the
271 Cybervision 64/3D card, as they use incompatible video chips.
273 config FB_VIRGE
274 bool "Amiga CyberVision 64/3D support "
275 depends on (FB = y) && ZORRO && BROKEN
276 select FB_CFB_FILLRECT
277 select FB_CFB_COPYAREA
278 select FB_CFB_IMAGEBLIT
279 help
280 This enables support for the Cybervision 64/3D graphics card from
281 Phase5. Please note that its use is not all that intuitive (i.e. if
282 you have any questions, be sure to ask!). Say N unless you have a
283 Cybervision 64/3D or plan to get one before you next recompile the
284 kernel. Please note that this driver DOES NOT support the older
285 Cybervision 64 card, as they use incompatible video chips.
287 config FB_RETINAZ3
288 tristate "Amiga Retina Z3 support"
289 depends on (FB = y) && ZORRO && BROKEN
290 help
291 This enables support for the Retina Z3 graphics card. Say N unless
292 you have a Retina Z3 or plan to get one before you next recompile
293 the kernel.
295 config FB_FM2
296 bool "Amiga FrameMaster II/Rainbow II support"
297 depends on (FB = y) && ZORRO
298 select FB_CFB_FILLRECT
299 select FB_CFB_COPYAREA
300 select FB_CFB_IMAGEBLIT
301 help
302 This is the frame buffer device driver for the Amiga FrameMaster
303 card from BSC (exhibited 1992 but not shipped as a CBM product).
305 config FB_ARC
306 tristate "Arc Monochrome LCD board support"
307 depends on FB && X86
308 select FB_CFB_FILLRECT
309 select FB_CFB_COPYAREA
310 select FB_CFB_IMAGEBLIT
311 help
312 This enables support for the Arc Monochrome LCD board. The board
313 is based on the KS-108 lcd controller and is typically a matrix
314 of 2*n chips. This driver was tested with a 128x64 panel. This
315 driver supports it for use with x86 SBCs through a 16 bit GPIO
316 interface (8 bit data, 8 bit control). If you anticpate using
317 this driver, say Y or M; otherwise say N. You must specify the
318 GPIO IO address to be used for setting control and data.
320 config FB_ATARI
321 bool "Atari native chipset support"
322 depends on (FB = y) && ATARI && BROKEN
323 help
324 This is the frame buffer device driver for the builtin graphics
325 chipset found in Ataris.
327 config FB_OF
328 bool "Open Firmware frame buffer device support"
329 depends on (FB = y) && (PPC64 || PPC_OF)
330 select FB_CFB_FILLRECT
331 select FB_CFB_COPYAREA
332 select FB_CFB_IMAGEBLIT
333 select FB_MACMODES
334 help
335 Say Y if you want support with Open Firmware for your graphics
336 board.
338 config FB_CONTROL
339 bool "Apple \"control\" display support"
340 depends on (FB = y) && PPC_PMAC
341 select FB_CFB_FILLRECT
342 select FB_CFB_COPYAREA
343 select FB_CFB_IMAGEBLIT
344 select FB_MACMODES
345 help
346 This driver supports a frame buffer for the graphics adapter in the
347 Power Macintosh 7300 and others.
349 config FB_PLATINUM
350 bool "Apple \"platinum\" display support"
351 depends on (FB = y) && PPC_PMAC
352 select FB_CFB_FILLRECT
353 select FB_CFB_COPYAREA
354 select FB_CFB_IMAGEBLIT
355 select FB_MACMODES
356 help
357 This driver supports a frame buffer for the "platinum" graphics
358 adapter in some Power Macintoshes.
360 config FB_VALKYRIE
361 bool "Apple \"valkyrie\" display support"
362 depends on (FB = y) && (MAC || PPC_PMAC)
363 select FB_CFB_FILLRECT
364 select FB_CFB_COPYAREA
365 select FB_CFB_IMAGEBLIT
366 select FB_MACMODES
367 help
368 This driver supports a frame buffer for the "valkyrie" graphics
369 adapter in some Power Macintoshes.
371 config FB_CT65550
372 bool "Chips 65550 display support"
373 depends on (FB = y) && PPC
374 select FB_CFB_FILLRECT
375 select FB_CFB_COPYAREA
376 select FB_CFB_IMAGEBLIT
377 help
378 This is the frame buffer device driver for the Chips & Technologies
379 65550 graphics chip in PowerBooks.
381 config FB_ASILIANT
382 bool "Asiliant (Chips) 69000 display support"
383 depends on (FB = y) && PCI
384 select FB_CFB_FILLRECT
385 select FB_CFB_COPYAREA
386 select FB_CFB_IMAGEBLIT
388 config FB_IMSTT
389 bool "IMS Twin Turbo display support"
390 depends on (FB = y) && PCI
391 select FB_CFB_IMAGEBLIT
392 select FB_MACMODES if PPC
393 help
394 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
395 many Macintosh and compatible computers.
397 config FB_VGA16
398 tristate "VGA 16-color graphics support"
399 depends on FB && (X86 || PPC)
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 VGA 16 color graphic
405 cards. Say Y if you have such a card.
407 To compile this driver as a module, choose M here: the
408 module will be called vga16fb.
410 config FB_STI
411 tristate "HP STI frame buffer device support"
412 depends on FB && PARISC
413 select FB_CFB_FILLRECT
414 select FB_CFB_COPYAREA
415 select FB_CFB_IMAGEBLIT
416 default y
417 ---help---
418 STI refers to the HP "Standard Text Interface" which is a set of
419 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
420 Enabling this option will implement the linux framebuffer device
421 using calls to the STI BIOS routines for initialisation.
423 If you enable this option, you will get a planar framebuffer device
424 /dev/fb which will work on the most common HP graphic cards of the
425 NGLE family, including the artist chips (in the 7xx and Bxxx series),
426 HCRX, HCRX24, CRX, CRX24 and VisEG series.
428 It is safe to enable this option, so you should probably say "Y".
430 config FB_MAC
431 bool "Generic Macintosh display support"
432 depends on (FB = y) && MAC
433 select FB_CFB_FILLRECT
434 select FB_CFB_COPYAREA
435 select FB_CFB_IMAGEBLIT
436 select FB_MACMODES
438 # bool ' Apple DAFB display support' CONFIG_FB_DAFB
439 config FB_HP300
440 bool
441 depends on (FB = y) && HP300
442 select FB_CFB_FILLRECT
443 select FB_CFB_IMAGEBLIT
444 default y
446 config FB_TGA
447 tristate "TGA framebuffer support"
448 depends on FB && ALPHA
449 select FB_CFB_FILLRECT
450 select FB_CFB_COPYAREA
451 select FB_CFB_IMAGEBLIT
452 help
453 This is the frame buffer device driver for generic TGA graphic
454 cards. Say Y if you have one of those.
456 config FB_VESA
457 bool "VESA VGA graphics support"
458 depends on (FB = y) && X86
459 select FB_CFB_FILLRECT
460 select FB_CFB_COPYAREA
461 select FB_CFB_IMAGEBLIT
462 help
463 This is the frame buffer device driver for generic VESA 2.0
464 compliant graphic cards. The older VESA 1.2 cards are not supported.
465 You will get a boot time penguin logo at no additional cost. Please
466 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
468 config VIDEO_SELECT
469 bool
470 depends on FB_VESA
471 default y
473 config FB_HGA
474 tristate "Hercules mono graphics support"
475 depends on FB && X86
476 select FB_CFB_FILLRECT
477 select FB_CFB_COPYAREA
478 select FB_CFB_IMAGEBLIT
479 help
480 Say Y here if you have a Hercules mono graphics card.
482 To compile this driver as a module, choose M here: the
483 module will be called hgafb.
485 As this card technology is 15 years old, most people will answer N
486 here.
488 config FB_HGA_ACCEL
489 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
490 depends on FB_HGA && EXPERIMENTAL
491 ---help---
492 This will compile the Hercules mono graphics with
493 acceleration functions.
496 config VIDEO_SELECT
497 bool
498 depends on (FB = y) && X86
499 default y
501 config FB_SGIVW
502 tristate "SGI Visual Workstation framebuffer support"
503 depends on FB && X86_VISWS
504 select FB_CFB_FILLRECT
505 select FB_CFB_COPYAREA
506 select FB_CFB_IMAGEBLIT
507 help
508 SGI Visual Workstation support for framebuffer graphics.
510 config FB_GBE
511 bool "SGI Graphics Backend frame buffer support"
512 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
513 select FB_CFB_FILLRECT
514 select FB_CFB_COPYAREA
515 select FB_CFB_IMAGEBLIT
516 help
517 This is the frame buffer device driver for SGI Graphics Backend.
518 This chip is used in SGI O2 and Visual Workstation 320/540.
520 config FB_GBE_MEM
521 int "Video memory size in MB"
522 depends on FB_GBE
523 default 8
524 help
525 This is the amount of memory reserved for the framebuffer,
526 which can be any value between 1MB and 8MB.
528 config BUS_I2C
529 bool
530 depends on (FB = y) && VISWS
531 default y
533 config FB_SUN3
534 bool "Sun3 framebuffer support"
535 depends on (FB = y) && (SUN3 || SUN3X) && BROKEN
537 config FB_SBUS
538 bool "SBUS and UPA framebuffers"
539 depends on (FB = y) && SPARC
540 help
541 Say Y if you want support for SBUS or UPA based frame buffer device.
543 config FB_BW2
544 bool "BWtwo support"
545 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
546 select FB_CFB_FILLRECT
547 select FB_CFB_COPYAREA
548 select FB_CFB_IMAGEBLIT
549 help
550 This is the frame buffer device driver for the BWtwo frame buffer.
552 config FB_CG3
553 bool "CGthree support"
554 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
555 select FB_CFB_FILLRECT
556 select FB_CFB_COPYAREA
557 select FB_CFB_IMAGEBLIT
558 help
559 This is the frame buffer device driver for the CGthree frame buffer.
561 config FB_CG6
562 bool "CGsix (GX,TurboGX) support"
563 depends on (FB = y) && (SPARC && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
564 select FB_CFB_COPYAREA
565 select FB_CFB_IMAGEBLIT
566 help
567 This is the frame buffer device driver for the CGsix (GX, TurboGX)
568 frame buffer.
570 config FB_PVR2
571 tristate "NEC PowerVR 2 display support"
572 depends on FB && SH_DREAMCAST
573 select FB_CFB_FILLRECT
574 select FB_CFB_COPYAREA
575 select FB_CFB_IMAGEBLIT
576 ---help---
577 Say Y here if you have a PowerVR 2 card in your box. If you plan to
578 run linux on your Dreamcast, you will have to say Y here.
579 This driver may or may not work on other PowerVR 2 cards, but is
580 totally untested. Use at your own risk. If unsure, say N.
582 To compile this driver as a module, choose M here: the
583 module will be called pvr2fb.
585 You can pass several parameters to the driver at boot time or at
586 module load time. The parameters look like "video=pvr2:XXX", where
587 the meaning of XXX can be found at the end of the main source file
588 (<file:drivers/video/pvr2fb.c>). Please see the file
589 <file:Documentation/fb/pvr2fb.txt>.
591 config FB_EPSON1355
592 bool "Epson 1355 framebuffer support"
593 depends on (FB = y) && (SUPERH || ARCH_CEIVA)
594 select FB_CFB_FILLRECT
595 select FB_CFB_COPYAREA
596 select FB_CFB_IMAGEBLIT
597 help
598 Build in support for the SED1355 Epson Research Embedded RAMDAC
599 LCD/CRT Controller (since redesignated as the S1D13505) as a
600 framebuffer. Product specs at
601 <http://www.erd.epson.com/vdc/html/products.htm>.
603 config FB_S1D13XXX
604 tristate "Epson S1D13XXX framebuffer support"
605 depends on FB
606 select FB_CFB_FILLRECT
607 select FB_CFB_COPYAREA
608 select FB_CFB_IMAGEBLIT
609 help
610 Support for S1D13XXX framebuffer device family (currently only
611 working with S1D13806). Product specs at
612 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
614 config FB_NVIDIA
615 tristate "nVidia Framebuffer Support"
616 depends on FB && PCI
617 select I2C_ALGOBIT if FB_NVIDIA_I2C
618 select I2C if FB_NVIDIA_I2C
619 select FB_MODE_HELPERS
620 select FB_CFB_FILLRECT
621 select FB_CFB_COPYAREA
622 select FB_CFB_IMAGEBLIT
623 help
624 This driver supports graphics boards with the nVidia chips, TNT
625 and newer. For very old chipsets, such as the RIVA128, then use
626 the rivafb.
627 Say Y if you have such a graphics board.
629 To compile this driver as a module, choose M here: the
630 module will be called nvidiafb.
632 config FB_NVIDIA_I2C
633 bool "Enable DDC Support"
634 depends on FB_NVIDIA
635 help
636 This enables I2C support for nVidia Chipsets. This is used
637 only for getting EDID information from the attached display
638 allowing for robust video mode handling and switching.
640 Because fbdev-2.6 requires that drivers must be able to
641 independently validate video mode parameters, you should say Y
642 here.
644 config FB_RIVA
645 tristate "nVidia Riva support"
646 depends on FB && PCI
647 select I2C_ALGOBIT if FB_RIVA_I2C
648 select I2C if FB_RIVA_I2C
649 select FB_MODE_HELPERS
650 select FB_CFB_FILLRECT
651 select FB_CFB_COPYAREA
652 select FB_CFB_IMAGEBLIT
653 help
654 This driver supports graphics boards with the nVidia Riva/Geforce
655 chips.
656 Say Y if you have such a graphics board.
658 To compile this driver as a module, choose M here: the
659 module will be called rivafb.
661 config FB_RIVA_I2C
662 bool "Enable DDC Support"
663 depends on FB_RIVA
664 help
665 This enables I2C support for nVidia Chipsets. This is used
666 only for getting EDID information from the attached display
667 allowing for robust video mode handling and switching.
669 Because fbdev-2.6 requires that drivers must be able to
670 independently validate video mode parameters, you should say Y
671 here.
673 config FB_RIVA_DEBUG
674 bool "Lots of debug output from Riva(nVidia) driver"
675 depends on FB_RIVA
676 default n
677 help
678 Say Y here if you want the Riva driver to output all sorts
679 of debugging informations to provide to the maintainer when
680 something goes wrong.
682 config FB_I810
683 tristate "Intel 810/815 support (EXPERIMENTAL)"
684 depends on FB && EXPERIMENTAL && PCI && X86_32
685 select AGP
686 select AGP_INTEL
687 select FB_MODE_HELPERS
688 select FB_CFB_FILLRECT
689 select FB_CFB_COPYAREA
690 select FB_CFB_IMAGEBLIT
691 help
692 This driver supports the on-board graphics built in to the Intel 810
693 and 815 chipsets. Say Y if you have and plan to use such a board.
695 To compile this driver as a module, choose M here: the
696 module will be called i810fb.
698 For more information, please read
699 <file:Documentation/fb/intel810.txt>
701 config FB_I810_GTF
702 bool "use VESA Generalized Timing Formula"
703 depends on FB_I810
704 help
705 If you say Y, then the VESA standard, Generalized Timing Formula
706 or GTF, will be used to calculate the required video timing values
707 per video mode. Since the GTF allows nondiscrete timings
708 (nondiscrete being a range of values as opposed to discrete being a
709 set of values), you'll be able to use any combination of horizontal
710 and vertical resolutions, and vertical refresh rates without having
711 to specify your own timing parameters. This is especially useful
712 to maximize the performance of an aging display, or if you just
713 have a display with nonstandard dimensions. A VESA compliant
714 monitor is recommended, but can still work with non-compliant ones.
715 If you need or want this, then select this option. The timings may
716 not be compliant with Intel's recommended values. Use at your own
717 risk.
719 If you say N, the driver will revert to discrete video timings
720 using a set recommended by Intel in their documentation.
722 If unsure, say N.
724 config FB_I810_I2C
725 bool "Enable DDC Support"
726 depends on FB_I810 && FB_I810_GTF
727 select I2C
728 select I2C_ALGOBIT
729 help
731 config FB_INTEL
732 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
733 depends on FB && EXPERIMENTAL && PCI && X86_32
734 select AGP
735 select AGP_INTEL
736 select FB_MODE_HELPERS
737 select FB_CFB_FILLRECT
738 select FB_CFB_COPYAREA
739 select FB_CFB_IMAGEBLIT
740 help
741 This driver supports the on-board graphics built in to the Intel
742 830M/845G/852GM/855GM/865G chipsets.
743 Say Y if you have and plan to use such a board.
745 To compile this driver as a module, choose M here: the
746 module will be called intelfb.
748 config FB_INTEL_DEBUG
749 bool "Intel driver Debug Messages"
750 depends on FB_INTEL
751 ---help---
752 Say Y here if you want the Intel driver to output all sorts
753 of debugging informations to provide to the maintainer when
754 something goes wrong.
756 config FB_MATROX
757 tristate "Matrox acceleration"
758 depends on FB && PCI
759 select FB_CFB_FILLRECT
760 select FB_CFB_COPYAREA
761 select FB_CFB_IMAGEBLIT
762 select FB_TILEBLITTING
763 select FB_MACMODES if PPC_PMAC
764 ---help---
765 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
766 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
767 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
768 Matrox G400, G450 or G550 card in your box.
770 To compile this driver as a module, choose M here: the
771 module will be called matroxfb.
773 You can pass several parameters to the driver at boot time or at
774 module load time. The parameters look like "video=matrox:XXX", and
775 are described in <file:Documentation/fb/matroxfb.txt>.
777 config FB_MATROX_MILLENIUM
778 bool "Millennium I/II support"
779 depends on FB_MATROX
780 help
781 Say Y here if you have a Matrox Millennium or Matrox Millennium II
782 video card. If you select "Advanced lowlevel driver options" below,
783 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
784 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
785 also use font widths different from 8.
787 config FB_MATROX_MYSTIQUE
788 bool "Mystique support"
789 depends on FB_MATROX
790 help
791 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
792 video card. If you select "Advanced lowlevel driver options" below,
793 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
794 packed pixel and 32 bpp packed pixel. You can also use font widths
795 different from 8.
797 config FB_MATROX_G
798 bool "G100/G200/G400/G450/G550 support"
799 depends on FB_MATROX
800 ---help---
801 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
802 video card. If you select "Advanced lowlevel driver options", you
803 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
804 pixel and 32 bpp packed pixel. You can also use font widths
805 different from 8.
807 If you need support for G400 secondary head, you must first say Y to
808 "I2C support" in the character devices section, and then to
809 "Matrox I2C support" and "G400 second head support" here in the
810 framebuffer section. G450/G550 secondary head and digital output
811 are supported without additional modules.
813 The driver starts in monitor mode. You must use the matroxset tool
814 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
815 swap primary and secondary head outputs, or to change output mode.
816 Secondary head driver always start in 640x480 resolution and you
817 must use fbset to change it.
819 Do not forget that second head supports only 16 and 32 bpp
820 packed pixels, so it is a good idea to compile them into the kernel
821 too. You can use only some font widths, as the driver uses generic
822 painting procedures (the secondary head does not use acceleration
823 engine).
825 G450/G550 hardware can display TV picture only from secondary CRTC,
826 and it performs no scaling, so picture must have 525 or 625 lines.
828 config FB_MATROX_I2C
829 tristate "Matrox I2C support"
830 depends on FB_MATROX && I2C
831 select I2C_ALGOBIT
832 ---help---
833 This drivers creates I2C buses which are needed for accessing the
834 DDC (I2C) bus present on all Matroxes, an I2C bus which
835 interconnects Matrox optional devices, like MGA-TVO on G200 and
836 G400, and the secondary head DDC bus, present on G400 only.
838 You can say Y or M here if you want to experiment with monitor
839 detection code. You must say Y or M here if you want to use either
840 second head of G400 or MGA-TVO on G200 or G400.
842 If you compile it as module, it will create a module named
843 i2c-matroxfb.
845 config FB_MATROX_MAVEN
846 tristate "G400 second head support"
847 depends on FB_MATROX_G && FB_MATROX_I2C
848 ---help---
849 WARNING !!! This support does not work with G450 !!!
851 Say Y or M here if you want to use a secondary head (meaning two
852 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
853 head is not compatible with accelerated XFree 3.3.x SVGA servers -
854 secondary head output is blanked while you are in X. With XFree
855 3.9.17 preview you can use both heads if you use SVGA over fbdev or
856 the fbdev driver on first head and the fbdev driver on second head.
858 If you compile it as module, two modules are created,
859 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
860 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
861 also load i2c-matroxfb to get it to run.
863 The driver starts in monitor mode and you must use the matroxset
864 tool (available at
865 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
866 PAL or NTSC or to swap primary and secondary head outputs.
867 Secondary head driver also always start in 640x480 resolution, you
868 must use fbset to change it.
870 Also do not forget that second head supports only 16 and 32 bpp
871 packed pixels, so it is a good idea to compile them into the kernel
872 too. You can use only some font widths, as the driver uses generic
873 painting procedures (the secondary head does not use acceleration
874 engine).
876 config FB_MATROX_MULTIHEAD
877 bool "Multihead support"
878 depends on FB_MATROX
879 ---help---
880 Say Y here if you have more than one (supported) Matrox device in
881 your computer and you want to use all of them for different monitors
882 ("multihead"). If you have only one device, you should say N because
883 the driver compiled with Y is larger and a bit slower, especially on
884 ia32 (ix86).
886 If you said M to "Matrox unified accelerated driver" and N here, you
887 will still be able to use several Matrox devices simultaneously:
888 insert several instances of the module matroxfb into the kernel
889 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
890 for the different Matrox devices. This method is slightly faster but
891 uses 40 KB of kernel memory per Matrox card.
893 There is no need for enabling 'Matrox multihead support' if you have
894 only one Matrox card in the box.
896 config FB_RADEON_OLD
897 tristate "ATI Radeon display support (Old driver)"
898 depends on FB && PCI
899 select FB_CFB_FILLRECT
900 select FB_CFB_COPYAREA
901 select FB_CFB_IMAGEBLIT
902 select FB_MACMODES if PPC
903 help
904 Choose this option if you want to use an ATI Radeon graphics card as
905 a framebuffer device. There are both PCI and AGP versions. You
906 don't need to choose this to run the Radeon in plain VGA mode.
907 There is a product page at
908 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
910 config FB_RADEON
911 tristate "ATI Radeon display support"
912 depends on FB && PCI
913 select I2C_ALGOBIT if FB_RADEON_I2C
914 select I2C if FB_RADEON_I2C
915 select FB_MODE_HELPERS
916 select FB_CFB_FILLRECT
917 select FB_CFB_COPYAREA
918 select FB_CFB_IMAGEBLIT
919 select FB_MACMODES if PPC_OF
920 help
921 Choose this option if you want to use an ATI Radeon graphics card as
922 a framebuffer device. There are both PCI and AGP versions. You
923 don't need to choose this to run the Radeon in plain VGA mode.
925 If you say Y here and want DDC/I2C support you must first say Y to
926 "I2C support" and "I2C bit-banging support" in the character devices
927 section.
929 If you say M here then "I2C support" and "I2C bit-banging support"
930 can be build either as modules or built-in.
932 There is a product page at
933 http://apps.ati.com/ATIcompare/
934 config FB_RADEON_I2C
935 bool "DDC/I2C for ATI Radeon support"
936 depends on FB_RADEON
937 default y
938 help
939 Say Y here if you want DDC/I2C support for your Radeon board.
941 config FB_RADEON_DEBUG
942 bool "Lots of debug output from Radeon driver"
943 depends on FB_RADEON
944 default n
945 help
946 Say Y here if you want the Radeon driver to output all sorts
947 of debugging informations to provide to the maintainer when
948 something goes wrong.
950 config FB_ATY128
951 tristate "ATI Rage128 display support"
952 depends on FB && PCI
953 select FB_CFB_FILLRECT
954 select FB_CFB_COPYAREA
955 select FB_CFB_IMAGEBLIT
956 select FB_MACMODES if PPC_PMAC
957 help
958 This driver supports graphics boards with the ATI Rage128 chips.
959 Say Y if you have such a graphics board and read
960 <file:Documentation/fb/aty128fb.txt>.
962 To compile this driver as a module, choose M here: the
963 module will be called aty128fb.
965 config FB_ATY
966 tristate "ATI Mach64 display support" if PCI || ATARI
967 depends on FB
968 select FB_CFB_FILLRECT
969 select FB_CFB_COPYAREA
970 select FB_CFB_IMAGEBLIT
971 select FB_MACMODES if PPC
972 help
973 This driver supports graphics boards with the ATI Mach64 chips.
974 Say Y if you have such a graphics board.
976 To compile this driver as a module, choose M here: the
977 module will be called atyfb.
979 config FB_ATY_CT
980 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
981 depends on PCI && FB_ATY
982 default y if SPARC64 && FB_PCI
983 help
984 Say Y here to support use of ATI's 64-bit Rage boards (or other
985 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
986 framebuffer device. The ATI product support page for these boards
987 is at <http://support.ati.com/products/pc/mach64/>.
989 config FB_ATY_GENERIC_LCD
990 bool "Mach64 generic LCD support (EXPERIMENTAL)"
991 depends on FB_ATY_CT
992 help
993 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
994 Rage XC, or Rage XL chipset.
996 config FB_ATY_GX
997 bool "Mach64 GX support" if PCI
998 depends on FB_ATY
999 default y if ATARI
1000 help
1001 Say Y here to support use of the ATI Mach64 Graphics Expression
1002 board (or other boards based on the Mach64 GX chipset) as a
1003 framebuffer device. The ATI product support page for these boards
1004 is at
1005 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1007 config FB_S3TRIO
1008 bool "S3 Trio display support"
1009 depends on (FB = y) && PPC && BROKEN
1010 help
1011 If you have a S3 Trio say Y. Say N for S3 Virge.
1013 config FB_SAVAGE
1014 tristate "S3 Savage support"
1015 depends on FB && PCI && EXPERIMENTAL
1016 select I2C_ALGOBIT if FB_SAVAGE_I2C
1017 select I2C if FB_SAVAGE_I2C
1018 select FB_MODE_HELPERS
1019 select FB_CFB_FILLRECT
1020 select FB_CFB_COPYAREA
1021 select FB_CFB_IMAGEBLIT
1022 help
1023 This driver supports notebooks and computers with S3 Savage PCI/AGP
1024 chips.
1026 Say Y if you have such a graphics card.
1028 To compile this driver as a module, choose M here; the module
1029 will be called savagefb.
1031 config FB_SAVAGE_I2C
1032 bool "Enable DDC2 Support"
1033 depends on FB_SAVAGE
1034 help
1035 This enables I2C support for S3 Savage Chipsets. This is used
1036 only for getting EDID information from the attached display
1037 allowing for robust video mode handling and switching.
1039 Because fbdev-2.6 requires that drivers must be able to
1040 independently validate video mode parameters, you should say Y
1041 here.
1043 config FB_SAVAGE_ACCEL
1044 bool "Enable Console Acceleration"
1045 depends on FB_SAVAGE
1046 default n
1047 help
1048 This option will compile in console acceleration support. If
1049 the resulting framebuffer console has bothersome glitches, then
1050 choose N here.
1052 config FB_SIS
1053 tristate "SiS/XGI display support"
1054 depends on FB && PCI
1055 select FB_CFB_FILLRECT
1056 select FB_CFB_COPYAREA
1057 select FB_CFB_IMAGEBLIT
1058 help
1059 This is the frame buffer device driver for the SiS 300, 315, 330
1060 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1061 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1063 To compile this driver as a module, choose M here; the module
1064 will be called sisfb.
1066 config FB_SIS_300
1067 bool "SiS 300 series support"
1068 depends on FB_SIS
1069 help
1070 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1072 config FB_SIS_315
1073 bool "SiS 315/330/340 series and XGI support"
1074 depends on FB_SIS
1075 help
1076 Say Y here to support use of the SiS 315, 330 and 340 series
1077 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1078 as XGI V3XT, V5, V8 and Z7.
1080 config FB_NEOMAGIC
1081 tristate "NeoMagic display support"
1082 depends on FB && PCI
1083 select FB_MODE_HELPERS
1084 select FB_CFB_FILLRECT
1085 select FB_CFB_COPYAREA
1086 select FB_CFB_IMAGEBLIT
1087 help
1088 This driver supports notebooks with NeoMagic PCI chips.
1089 Say Y if you have such a graphics card.
1091 To compile this driver as a module, choose M here: the
1092 module will be called neofb.
1094 config FB_KYRO
1095 tristate "IMG Kyro support"
1096 depends on FB && PCI
1097 select FB_CFB_FILLRECT
1098 select FB_CFB_COPYAREA
1099 select FB_CFB_IMAGEBLIT
1100 help
1101 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1102 graphics board.
1104 To compile this driver as a module, choose M here: the
1105 module will be called kyrofb.
1107 config FB_3DFX
1108 tristate "3Dfx Banshee/Voodoo3 display support"
1109 depends on FB && PCI
1110 select FB_CFB_IMAGEBLIT
1111 select FB_CFB_FILLRECT
1112 select FB_CFB_COPYAREA
1113 help
1114 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
1115 chips. Say Y if you have such a graphics board.
1117 To compile this driver as a module, choose M here: the
1118 module will be called tdfxfb.
1120 config FB_3DFX_ACCEL
1121 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
1122 depends on FB_3DFX && EXPERIMENTAL
1123 ---help---
1124 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
1125 with acceleration functions.
1128 config FB_VOODOO1
1129 tristate "3Dfx Voodoo Graphics (sst1) support"
1130 depends on FB && PCI
1131 select FB_CFB_FILLRECT
1132 select FB_CFB_COPYAREA
1133 select FB_CFB_IMAGEBLIT
1134 ---help---
1135 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1136 Voodoo2 (cvg) based graphics card.
1138 To compile this driver as a module, choose M here: the
1139 module will be called sstfb.
1141 WARNING: Do not use any application that uses the 3D engine
1142 (namely glide) while using this driver.
1143 Please read the <file:Documentation/fb/README-sstfb.txt> for supported
1144 options and other important info support.
1146 config FB_CYBLA
1147 tristate "Cyberblade/i1 support"
1148 depends on FB && PCI && X86_32 && !64BIT
1149 select FB_CFB_IMAGEBLIT
1150 select VIDEO_SELECT
1151 ---help---
1152 This driver is supposed to support the Trident Cyberblade/i1
1153 graphics core integrated in the VIA VT8601A North Bridge,
1154 also known as VIA Apollo PLE133.
1156 Status:
1157 - Developed, tested and working on EPIA 5000 and EPIA 800.
1158 - Does work reliable on all systems with CRT/LCD connected to
1159 normal VGA ports.
1160 - Should work on systems that do use the internal LCD port, but
1161 this is absolutely not tested.
1163 Character imageblit, copyarea and rectangle fill are hw accelerated,
1164 ypan scrolling is used by default.
1166 Please do read <file:Documentation/fb/cyblafb/*>.
1168 To compile this driver as a module, choose M here: the
1169 module will be called cyblafb.
1171 config FB_TRIDENT
1172 tristate "Trident support"
1173 depends on FB && PCI
1174 select FB_CFB_FILLRECT
1175 select FB_CFB_COPYAREA
1176 select FB_CFB_IMAGEBLIT
1177 ---help---
1178 This driver is supposed to support graphics boards with the
1179 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
1180 but also on some motherboards. For more information, read
1181 <file:Documentation/fb/tridentfb.txt>
1183 Cyberblade/i1 support will be removed soon, use the cyblafb driver
1184 instead.
1186 Say Y if you have such a graphics board.
1189 To compile this driver as a module, choose M here: the
1190 module will be called tridentfb.
1192 config FB_TRIDENT_ACCEL
1193 bool "Trident Acceleration functions (EXPERIMENTAL)"
1194 depends on FB_TRIDENT && EXPERIMENTAL
1195 ---help---
1196 This will compile the Trident frame buffer device with
1197 acceleration functions.
1199 config FB_PM3
1200 tristate "Permedia3 support"
1201 depends on FB && PCI && BROKEN
1202 help
1203 This is the frame buffer device driver for the 3DLabs Permedia3
1204 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1205 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1206 and maybe other boards.
1208 config FB_AU1100
1209 bool "Au1100 LCD Driver"
1210 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
1212 source "drivers/video/geode/Kconfig"
1214 config FB_FFB
1215 bool "Creator/Creator3D/Elite3D support"
1216 depends on FB_SBUS && SPARC64
1217 select FB_CFB_COPYAREA
1218 select FB_CFB_IMAGEBLIT
1219 help
1220 This is the frame buffer device driver for the Creator, Creator3D,
1221 and Elite3D graphics boards.
1223 config FB_TCX
1224 bool "TCX (SS4/SS5 only) support"
1225 depends on FB_SBUS
1226 select FB_CFB_FILLRECT
1227 select FB_CFB_COPYAREA
1228 select FB_CFB_IMAGEBLIT
1229 help
1230 This is the frame buffer device driver for the TCX 24/8bit frame
1231 buffer.
1233 config FB_CG14
1234 bool "CGfourteen (SX) 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 CGfourteen frame
1241 buffer on Desktop SPARCsystems with the SX graphics option.
1243 config FB_P9100
1244 bool "P9100 (Sparcbook 3 only) 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 P9100 card
1251 supported on Sparcbook 3 machines.
1253 config FB_LEO
1254 bool "Leo (ZX) 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 SBUS-based Sun ZX
1261 (leo) frame buffer cards.
1263 config FB_PCI
1264 bool "PCI framebuffers"
1265 depends on (FB = y) && PCI && SPARC
1267 config FB_IGA
1268 bool "IGA 168x display support"
1269 depends on SPARC32 && FB_PCI
1270 select FB_CFB_FILLRECT
1271 select FB_CFB_COPYAREA
1272 select FB_CFB_IMAGEBLIT
1273 help
1274 This is the framebuffer device for the INTERGRAPHICS 1680 and
1275 successor frame buffer cards.
1277 config FB_HIT
1278 tristate "HD64461 Frame Buffer support"
1279 depends on FB && HD64461
1280 select FB_CFB_FILLRECT
1281 select FB_CFB_COPYAREA
1282 select FB_CFB_IMAGEBLIT
1283 help
1284 This is the frame buffer device driver for the Hitachi HD64461 LCD
1285 frame buffer card.
1287 config FB_PMAG_AA
1288 bool "PMAG-AA TURBOchannel framebuffer support"
1289 depends on (FB = y) && TC
1290 select FB_CFB_FILLRECT
1291 select FB_CFB_COPYAREA
1292 select FB_CFB_IMAGEBLIT
1293 help
1294 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1295 used mainly in the MIPS-based DECstation series.
1297 config FB_PMAG_BA
1298 bool "PMAG-BA 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-BA TURBOchannel framebuffer card (1024x864x8)
1305 used mainly in the MIPS-based DECstation series.
1307 config FB_PMAGB_B
1308 bool "PMAGB-B 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 PMAGB-B TURBOchannel framebuffer card used mainly
1315 in the MIPS-based DECstation series. The card is currently only
1316 supported in 1280x1024x8 mode.
1318 config FB_MAXINE
1319 bool "Maxine (Personal DECstation) onboard framebuffer support"
1320 depends on (FB = y) && MACH_DECSTATION
1321 select FB_CFB_FILLRECT
1322 select FB_CFB_COPYAREA
1323 select FB_CFB_IMAGEBLIT
1324 help
1325 Support for the onboard framebuffer (1024x768x8) in the Personal
1326 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1327 Codename "Maxine").
1329 config FB_TX3912
1330 bool "TMPTX3912/PR31700 frame buffer support"
1331 depends on (FB = y) && NINO
1332 select FB_CFB_FILLRECT
1333 select FB_CFB_COPYAREA
1334 select FB_CFB_IMAGEBLIT
1335 help
1336 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
1337 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
1339 Say Y here to enable kernel support for the on-board framebuffer.
1341 config FB_G364
1342 bool "G364 frame buffer support"
1343 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1344 select FB_CFB_FILLRECT
1345 select FB_CFB_COPYAREA
1346 select FB_CFB_IMAGEBLIT
1347 help
1348 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1349 Olivetti M700-10 systems.
1351 config FB_68328
1352 bool "Motorola 68328 native frame buffer support"
1353 depends on FB && (M68328 || M68EZ328 || M68VZ328)
1354 select FB_CFB_FILLRECT
1355 select FB_CFB_COPYAREA
1356 select FB_CFB_IMAGEBLIT
1357 help
1358 Say Y here if you want to support the built-in frame buffer of
1359 the Motorola 68328 CPU family.
1361 config FB_PXA
1362 tristate "PXA LCD framebuffer support"
1363 depends on FB && ARCH_PXA
1364 select FB_CFB_FILLRECT
1365 select FB_CFB_COPYAREA
1366 select FB_CFB_IMAGEBLIT
1367 ---help---
1368 Frame buffer driver for the built-in LCD controller in the Intel
1369 PXA2x0 processor.
1371 This driver is also available as a module ( = code which can be
1372 inserted and removed from the running kernel whenever you want). The
1373 module will be called pxafb. If you want to compile it as a module,
1374 say M here and read <file:Documentation/modules.txt>.
1376 If unsure, say N.
1378 config FB_PXA_PARAMETERS
1379 bool "PXA LCD command line parameters"
1380 default n
1381 depends on FB_PXA
1382 ---help---
1383 Enable the use of kernel command line or module parameters
1384 to configure the physical properties of the LCD panel when
1385 using the PXA LCD driver.
1387 This option allows you to override the panel parameters
1388 supplied by the platform in order to support multiple
1389 different models of flatpanel. If you will only be using a
1390 single model of flatpanel then you can safely leave this
1391 option disabled.
1393 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1395 config FB_W100
1396 tristate "W100 frame buffer support"
1397 depends on FB && PXA_SHARPSL
1398 select FB_CFB_FILLRECT
1399 select FB_CFB_COPYAREA
1400 select FB_CFB_IMAGEBLIT
1401 ---help---
1402 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1404 This driver is also available as a module ( = code which can be
1405 inserted and removed from the running kernel whenever you want). The
1406 module will be called w100fb. If you want to compile it as a module,
1407 say M here and read <file:Documentation/modules.txt>.
1409 If unsure, say N.
1411 config FB_S3C2410
1412 tristate "S3C2410 LCD framebuffer support"
1413 depends on FB && ARCH_S3C2410
1414 select FB_CFB_FILLRECT
1415 select FB_CFB_COPYAREA
1416 select FB_CFB_IMAGEBLIT
1417 ---help---
1418 Frame buffer driver for the built-in LCD controller in the Samsung
1419 S3C2410 processor.
1421 This driver is also available as a module ( = code which can be
1422 inserted and removed from the running kernel whenever you want). The
1423 module will be called s3c2410fb. If you want to compile it as a module,
1424 say M here and read <file:Documentation/modules.txt>.
1426 If unsure, say N.
1427 config FB_S3C2410_DEBUG
1428 bool "S3C2410 lcd debug messages"
1429 depends on FB_S3C2410
1430 help
1431 Turn on debugging messages. Note that you can set/unset at run time
1432 through sysfs
1434 config FB_VIRTUAL
1435 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
1436 depends on FB
1437 select FB_CFB_FILLRECT
1438 select FB_CFB_COPYAREA
1439 select FB_CFB_IMAGEBLIT
1440 ---help---
1441 This is a `virtual' frame buffer device. It operates on a chunk of
1442 unswappable kernel memory instead of on the memory of a graphics
1443 board. This means you cannot see any output sent to this frame
1444 buffer device, while it does consume precious memory. The main use
1445 of this frame buffer device is testing and debugging the frame
1446 buffer subsystem. Do NOT enable it for normal systems! To protect
1447 the innocent, it has to be enabled explicitly at boot time using the
1448 kernel option `video=vfb:'.
1450 To compile this driver as a module, choose M here: the
1451 module will be called vfb.
1453 If unsure, say N.
1454 if VT
1455 source "drivers/video/console/Kconfig"
1456 endif
1458 if FB || SGI_NEWPORT_CONSOLE
1459 source "drivers/video/logo/Kconfig"
1460 endif
1462 if FB && SYSFS
1463 source "drivers/video/backlight/Kconfig"
1464 endif
1466 endmenu