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