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 || X86_64) 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 select FB_SOFT_CURSOR 685 help 686 This driver supports graphics boards with the nVidia Riva/Geforce 687 chips. 688 Say Y if you have such a graphics board. 689 690 To compile this driver as a module, choose M here: the 691 module will be called rivafb. 692 693config FB_RIVA_I2C 694 bool "Enable DDC Support" 695 depends on FB_RIVA 696 help 697 This enables I2C support for nVidia Chipsets. This is used 698 only for getting EDID information from the attached display 699 allowing for robust video mode handling and switching. 700 701 Because fbdev-2.6 requires that drivers must be able to 702 independently validate video mode parameters, you should say Y 703 here. 704 705config FB_RIVA_DEBUG 706 bool "Lots of debug output from Riva(nVidia) driver" 707 depends on FB_RIVA 708 default n 709 help 710 Say Y here if you want the Riva driver to output all sorts 711 of debugging informations to provide to the maintainer when 712 something goes wrong. 713 714config FB_I810 715 tristate "Intel 810/815 support (EXPERIMENTAL)" 716 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64 717 select AGP 718 select AGP_INTEL 719 select FB_MODE_HELPERS 720 select FB_CFB_FILLRECT 721 select FB_CFB_COPYAREA 722 select FB_CFB_IMAGEBLIT 723 select FB_SOFT_CURSOR 724 help 725 This driver supports the on-board graphics built in to the Intel 810 726 and 815 chipsets. Say Y if you have and plan to use such a board. 727 728 To compile this driver as a module, choose M here: the 729 module will be called i810fb. 730 731 For more information, please read 732 <file:Documentation/fb/intel810.txt> 733 734config FB_I810_GTF 735 bool "use VESA Generalized Timing Formula" 736 depends on FB_I810 737 help 738 If you say Y, then the VESA standard, Generalized Timing Formula 739 or GTF, will be used to calculate the required video timing values 740 per video mode. Since the GTF allows nondiscrete timings 741 (nondiscrete being a range of values as opposed to discrete being a 742 set of values), you'll be able to use any combination of horizontal 743 and vertical resolutions, and vertical refresh rates without having 744 to specify your own timing parameters. This is especially useful 745 to maximize the performance of an aging display, or if you just 746 have a display with nonstandard dimensions. A VESA compliant 747 monitor is recommended, but can still work with non-compliant ones. 748 If you need or want this, then select this option. The timings may 749 not be compliant with Intel's recommended values. Use at your own 750 risk. 751 752 If you say N, the driver will revert to discrete video timings 753 using a set recommended by Intel in their documentation. 754 755 If unsure, say N. 756 757config FB_INTEL 758 tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)" 759 depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64 760 select AGP 761 select AGP_INTEL 762 select FB_MODE_HELPERS 763 select FB_CFB_FILLRECT 764 select FB_CFB_COPYAREA 765 select FB_CFB_IMAGEBLIT 766 select FB_SOFT_CURSOR 767 help 768 This driver supports the on-board graphics built in to the Intel 769 830M/845G/852GM/855GM/865G chipsets. 770 Say Y if you have and plan to use such a board. 771 772 To compile this driver as a module, choose M here: the 773 module will be called intelfb. 774 775config FB_INTEL_DEBUG 776 bool "Intel driver Debug Messages" 777 depends on FB_INTEL 778 ---help--- 779 Say Y here if you want the Intel driver to output all sorts 780 of debugging informations to provide to the maintainer when 781 something goes wrong. 782 783config FB_MATROX 784 tristate "Matrox acceleration" 785 depends on FB && PCI 786 select FB_CFB_FILLRECT 787 select FB_CFB_COPYAREA 788 select FB_CFB_IMAGEBLIT 789 select FB_SOFT_CURSOR 790 select FB_TILEBLITTING 791 select FB_MACMODES if PPC_PMAC 792 ---help--- 793 Say Y here if you have a Matrox Millennium, Matrox Millennium II, 794 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox 795 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video, 796 Matrox G400, G450 or G550 card in your box. 797 798 To compile this driver as a module, choose M here: the 799 module will be called matroxfb. 800 801 You can pass several parameters to the driver at boot time or at 802 module load time. The parameters look like "video=matrox:XXX", and 803 are described in <file:Documentation/fb/matroxfb.txt>. 804 805config FB_MATROX_MILLENIUM 806 bool "Millennium I/II support" 807 depends on FB_MATROX 808 help 809 Say Y here if you have a Matrox Millennium or Matrox Millennium II 810 video card. If you select "Advanced lowlevel driver options" below, 811 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp 812 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can 813 also use font widths different from 8. 814 815config FB_MATROX_MYSTIQUE 816 bool "Mystique support" 817 depends on FB_MATROX 818 help 819 Say Y here if you have a Matrox Mystique or Matrox Mystique 220 820 video card. If you select "Advanced lowlevel driver options" below, 821 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp 822 packed pixel and 32 bpp packed pixel. You can also use font widths 823 different from 8. 824 825config FB_MATROX_G 826 bool "G100/G200/G400/G450/G550 support" 827 depends on FB_MATROX 828 ---help--- 829 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based 830 video card. If you select "Advanced lowlevel driver options", you 831 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed 832 pixel and 32 bpp packed pixel. You can also use font widths 833 different from 8. 834 835 If you need support for G400 secondary head, you must first say Y to 836 "I2C support" in the character devices section, and then to 837 "Matrox I2C support" and "G400 second head support" here in the 838 framebuffer section. G450/G550 secondary head and digital output 839 are supported without additional modules. 840 841 The driver starts in monitor mode. You must use the matroxset tool 842 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 843 swap primary and secondary head outputs, or to change output mode. 844 Secondary head driver always start in 640x480 resolution and you 845 must use fbset to change it. 846 847 Do not forget that second head supports only 16 and 32 bpp 848 packed pixels, so it is a good idea to compile them into the kernel 849 too. You can use only some font widths, as the driver uses generic 850 painting procedures (the secondary head does not use acceleration 851 engine). 852 853 G450/G550 hardware can display TV picture only from secondary CRTC, 854 and it performs no scaling, so picture must have 525 or 625 lines. 855 856config FB_MATROX_I2C 857 tristate "Matrox I2C support" 858 depends on FB_MATROX && I2C 859 select I2C_ALGOBIT 860 ---help--- 861 This drivers creates I2C buses which are needed for accessing the 862 DDC (I2C) bus present on all Matroxes, an I2C bus which 863 interconnects Matrox optional devices, like MGA-TVO on G200 and 864 G400, and the secondary head DDC bus, present on G400 only. 865 866 You can say Y or M here if you want to experiment with monitor 867 detection code. You must say Y or M here if you want to use either 868 second head of G400 or MGA-TVO on G200 or G400. 869 870 If you compile it as module, it will create a module named 871 i2c-matroxfb. 872 873config FB_MATROX_MAVEN 874 tristate "G400 second head support" 875 depends on FB_MATROX_G && FB_MATROX_I2C 876 ---help--- 877 WARNING !!! This support does not work with G450 !!! 878 879 Say Y or M here if you want to use a secondary head (meaning two 880 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary 881 head is not compatible with accelerated XFree 3.3.x SVGA servers - 882 secondary head output is blanked while you are in X. With XFree 883 3.9.17 preview you can use both heads if you use SVGA over fbdev or 884 the fbdev driver on first head and the fbdev driver on second head. 885 886 If you compile it as module, two modules are created, 887 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for 888 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must 889 also load i2c-matroxfb to get it to run. 890 891 The driver starts in monitor mode and you must use the matroxset 892 tool (available at 893 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to 894 PAL or NTSC or to swap primary and secondary head outputs. 895 Secondary head driver also always start in 640x480 resolution, you 896 must use fbset to change it. 897 898 Also do not forget that second head supports only 16 and 32 bpp 899 packed pixels, so it is a good idea to compile them into the kernel 900 too. You can use only some font widths, as the driver uses generic 901 painting procedures (the secondary head does not use acceleration 902 engine). 903 904config FB_MATROX_MULTIHEAD 905 bool "Multihead support" 906 depends on FB_MATROX 907 ---help--- 908 Say Y here if you have more than one (supported) Matrox device in 909 your computer and you want to use all of them for different monitors 910 ("multihead"). If you have only one device, you should say N because 911 the driver compiled with Y is larger and a bit slower, especially on 912 ia32 (ix86). 913 914 If you said M to "Matrox unified accelerated driver" and N here, you 915 will still be able to use several Matrox devices simultaneously: 916 insert several instances of the module matroxfb into the kernel 917 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc. 918 for the different Matrox devices. This method is slightly faster but 919 uses 40 KB of kernel memory per Matrox card. 920 921 There is no need for enabling 'Matrox multihead support' if you have 922 only one Matrox card in the box. 923 924config FB_RADEON_OLD 925 tristate "ATI Radeon display support (Old driver)" 926 depends on FB && PCI 927 select FB_CFB_FILLRECT 928 select FB_CFB_COPYAREA 929 select FB_CFB_IMAGEBLIT 930 select FB_SOFT_CURSOR 931 select FB_MACMODES if PPC 932 help 933 Choose this option if you want to use an ATI Radeon graphics card as 934 a framebuffer device. There are both PCI and AGP versions. You 935 don't need to choose this to run the Radeon in plain VGA mode. 936 There is a product page at 937 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>. 938 939config FB_RADEON 940 tristate "ATI Radeon display support" 941 depends on FB && PCI 942 select I2C_ALGOBIT if FB_RADEON_I2C 943 select I2C if FB_RADEON_I2C 944 select FB_MODE_HELPERS 945 select FB_CFB_FILLRECT 946 select FB_CFB_COPYAREA 947 select FB_CFB_IMAGEBLIT 948 select FB_SOFT_CURSOR 949 select FB_MACMODES if PPC_OF 950 help 951 Choose this option if you want to use an ATI Radeon graphics card as 952 a framebuffer device. There are both PCI and AGP versions. You 953 don't need to choose this to run the Radeon in plain VGA mode. 954 955 If you say Y here and want DDC/I2C support you must first say Y to 956 "I2C support" and "I2C bit-banging support" in the character devices 957 section. 958 959 If you say M here then "I2C support" and "I2C bit-banging support" 960 can be build either as modules or built-in. 961 962 There is a product page at 963 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>. 964 965config FB_RADEON_I2C 966 bool "DDC/I2C for ATI Radeon support" 967 depends on FB_RADEON 968 default y 969 help 970 Say Y here if you want DDC/I2C support for your Radeon board. 971 972config FB_RADEON_DEBUG 973 bool "Lots of debug output from Radeon driver" 974 depends on FB_RADEON 975 default n 976 help 977 Say Y here if you want the Radeon driver to output all sorts 978 of debugging informations to provide to the maintainer when 979 something goes wrong. 980 981config FB_ATY128 982 tristate "ATI Rage128 display support" 983 depends on FB && PCI 984 select FB_CFB_FILLRECT 985 select FB_CFB_COPYAREA 986 select FB_CFB_IMAGEBLIT 987 select FB_SOFT_CURSOR 988 select FB_MACMODES if PPC_PMAC 989 help 990 This driver supports graphics boards with the ATI Rage128 chips. 991 Say Y if you have such a graphics board and read 992 <file:Documentation/fb/aty128fb.txt>. 993 994 To compile this driver as a module, choose M here: the 995 module will be called aty128fb. 996 997config FB_ATY 998 tristate "ATI Mach64 display support" if PCI || ATARI 999 depends on FB 1000 select FB_CFB_FILLRECT 1001 select FB_CFB_COPYAREA 1002 select FB_CFB_IMAGEBLIT 1003 select FB_SOFT_CURSOR 1004 select FB_MACMODES if PPC 1005 help 1006 This driver supports graphics boards with the ATI Mach64 chips. 1007 Say Y if you have such a graphics board. 1008 1009 To compile this driver as a module, choose M here: the 1010 module will be called atyfb. 1011 1012config FB_ATY_CT 1013 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support" 1014 depends on PCI && FB_ATY 1015 default y if SPARC64 && FB_PCI 1016 help 1017 Say Y here to support use of ATI's 64-bit Rage boards (or other 1018 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a 1019 framebuffer device. The ATI product support page for these boards 1020 is at <http://support.ati.com/products/pc/mach64/>. 1021 1022config FB_ATY_GENERIC_LCD 1023 bool "Mach64 generic LCD support (EXPERIMENTAL)" 1024 depends on FB_ATY_CT 1025 help 1026 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility, 1027 Rage XC, or Rage XL chipset. 1028 1029config FB_ATY_XL_INIT 1030 bool "Rage XL No-BIOS Init support" 1031 depends on FB_ATY_CT 1032 help 1033 Say Y here to support booting a Rage XL without BIOS support. 1034 1035config FB_ATY_GX 1036 bool "Mach64 GX support" if PCI 1037 depends on FB_ATY 1038 default y if ATARI 1039 help 1040 Say Y here to support use of the ATI Mach64 Graphics Expression 1041 board (or other boards based on the Mach64 GX chipset) as a 1042 framebuffer device. The ATI product support page for these boards 1043 is at 1044 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>. 1045 1046config FB_SAVAGE 1047 tristate "S3 Savage support" 1048 depends on FB && PCI && EXPERIMENTAL 1049 select I2C_ALGOBIT if FB_SAVAGE_I2C 1050 select I2C if FB_SAVAGE_I2C 1051 select FB_MODE_HELPERS 1052 select FB_CFB_FILLRECT 1053 select FB_CFB_COPYAREA 1054 select FB_CFB_IMAGEBLIT 1055 select FB_SOFT_CURSOR 1056 help 1057 This driver supports notebooks and computers with S3 Savage PCI/AGP 1058 chips. 1059 1060 Say Y if you have such a graphics card. 1061 1062 To compile this driver as a module, choose M here; the module 1063 will be called savagefb. 1064 1065config FB_SAVAGE_I2C 1066 bool "Enable DDC2 Support" 1067 depends on FB_SAVAGE 1068 help 1069 This enables I2C support for S3 Savage Chipsets. This is used 1070 only for getting EDID information from the attached display 1071 allowing for robust video mode handling and switching. 1072 1073 Because fbdev-2.6 requires that drivers must be able to 1074 independently validate video mode parameters, you should say Y 1075 here. 1076 1077config FB_SAVAGE_ACCEL 1078 bool "Enable Console Acceleration" 1079 depends on FB_SAVAGE 1080 default n 1081 help 1082 This option will compile in console acceleration support. If 1083 the resulting framebuffer console has bothersome glitches, then 1084 choose N here. 1085 1086config FB_SIS 1087 tristate "SiS acceleration" 1088 depends on FB && PCI 1089 select FB_CFB_FILLRECT 1090 select FB_CFB_COPYAREA 1091 select FB_CFB_IMAGEBLIT 1092 select FB_SOFT_CURSOR 1093 help 1094 This is the frame buffer device driver for the SiS 300, 315 and 1095 330 series VGA chipsets. Specs available at <http://www.sis.com> 1096 1097 To compile this driver as a module, choose M here; the module 1098 will be called sisfb. 1099 1100config FB_SIS_300 1101 bool "SiS 300 series support" 1102 depends on FB_SIS 1103 help 1104 Say Y here to support use of the SiS 300/305, 540, 630 and 730. 1105 1106config FB_SIS_315 1107 bool "SiS 315/330 series support" 1108 depends on FB_SIS 1109 help 1110 Say Y here to support use of the SiS 315 and 330 series 1111 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760). 1112 1113config FB_NEOMAGIC 1114 tristate "NeoMagic display support" 1115 depends on FB && PCI 1116 select FB_MODE_HELPERS 1117 select FB_CFB_FILLRECT 1118 select FB_CFB_COPYAREA 1119 select FB_CFB_IMAGEBLIT 1120 select FB_SOFT_CURSOR 1121 help 1122 This driver supports notebooks with NeoMagic PCI chips. 1123 Say Y if you have such a graphics card. 1124 1125 To compile this driver as a module, choose M here: the 1126 module will be called neofb. 1127 1128config FB_KYRO 1129 tristate "IMG Kyro support" 1130 depends on FB && PCI 1131 select FB_CFB_FILLRECT 1132 select FB_CFB_COPYAREA 1133 select FB_CFB_IMAGEBLIT 1134 select FB_SOFT_CURSOR 1135 help 1136 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based 1137 graphics board. 1138 1139 To compile this driver as a module, choose M here: the 1140 module will be called kyrofb. 1141 1142config FB_3DFX 1143 tristate "3Dfx Banshee/Voodoo3 display support" 1144 depends on FB && PCI 1145 select FB_CFB_IMAGEBLIT 1146 select FB_CFB_FILLRECT 1147 select FB_CFB_COPYAREA 1148 select FB_SOFT_CURSOR 1149 help 1150 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 1151 chips. Say Y if you have such a graphics board. 1152 1153 To compile this driver as a module, choose M here: the 1154 module will be called tdfxfb. 1155 1156config FB_3DFX_ACCEL 1157 bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)" 1158 depends on FB_3DFX && EXPERIMENTAL 1159 ---help--- 1160 This will compile the 3Dfx Banshee/Voodoo3 frame buffer device 1161 with acceleration functions. 1162 1163 1164config FB_VOODOO1 1165 tristate "3Dfx Voodoo Graphics (sst1) support" 1166 depends on FB && PCI 1167 select FB_CFB_FILLRECT 1168 select FB_CFB_COPYAREA 1169 select FB_CFB_IMAGEBLIT 1170 select FB_SOFT_CURSOR 1171 ---help--- 1172 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 1173 Voodoo2 (cvg) based graphics card. 1174 1175 To compile this driver as a module, choose M here: the 1176 module will be called sstfb. 1177 1178 WARNING: Do not use any application that uses the 3D engine 1179 (namely glide) while using this driver. 1180 Please read the <file:Documentation/fb/README-sstfb.txt> for supported 1181 options and other important info support. 1182 1183config FB_TRIDENT 1184 tristate "Trident support" 1185 depends on FB && PCI 1186 select FB_CFB_FILLRECT 1187 select FB_CFB_COPYAREA 1188 select FB_CFB_IMAGEBLIT 1189 select FB_SOFT_CURSOR 1190 ---help--- 1191 This driver is supposed to support graphics boards with the 1192 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops 1193 but also on some motherboards. For more information, read 1194 <file:Documentation/fb/tridentfb.txt> 1195 1196 Say Y if you have such a graphics board. 1197 1198 To compile this driver as a module, choose M here: the 1199 module will be called tridentfb. 1200 1201config FB_TRIDENT_ACCEL 1202 bool "Trident Acceleration functions (EXPERIMENTAL)" 1203 depends on FB_TRIDENT && EXPERIMENTAL 1204 ---help--- 1205 This will compile the Trident frame buffer device with 1206 acceleration functions. 1207 1208 1209config FB_PM3 1210 tristate "Permedia3 support" 1211 depends on FB && PCI && BROKEN 1212 help 1213 This is the frame buffer device driver for the 3DLabs Permedia3 1214 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & 1215 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000 1216 and maybe other boards. 1217 1218config FB_E1356 1219 tristate "Epson SED1356 framebuffer support" 1220 depends on FB && EXPERIMENTAL && PCI && MIPS 1221 1222config PB1000_CRT 1223 bool "Use CRT on Pb1000 (J65)" 1224 depends on MIPS_PB1000=y && FB_E1356 1225 1226config PB1000_NTSC 1227 bool "Use Compsite NTSC on Pb1000 (J63)" 1228 depends on MIPS_PB1000=y && FB_E1356 1229 1230config PB1000_TFT 1231 bool "Use TFT Panel on Pb1000 (J64)" 1232 depends on MIPS_PB1000=y && FB_E1356 1233 1234config PB1500_CRT 1235 bool "Use CRT on Pb1500 " if MIPS_PB1500=y 1236 depends on FB_E1356 1237 1238config PB1500_CRT 1239 prompt "Use CRT on Pb1100 " 1240 depends on FB_E1356 && MIPS_PB1100=y 1241 1242config PB1500_TFT 1243 bool "Use TFT Panel on Pb1500 " if MIPS_PB1500=y 1244 depends on FB_E1356 1245 1246config PB1500_TFT 1247 prompt "Use TFT Panel on Pb1100 " 1248 depends on FB_E1356 && MIPS_PB1100=y 1249 1250config FB_AU1100 1251 bool "Au1100 LCD Driver" 1252 depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y 1253 1254source "drivers/video/geode/Kconfig" 1255 1256config FB_SBUS 1257 bool "SBUS and UPA framebuffers" 1258 depends on (FB = y) && (SPARC32 || SPARC64) 1259 help 1260 Say Y if you want support for SBUS or UPA based frame buffer device. 1261 1262config FB_FFB 1263 bool "Creator/Creator3D/Elite3D support" 1264 depends on FB_SBUS && SPARC64 1265 select FB_CFB_COPYAREA 1266 select FB_CFB_IMAGEBLIT 1267 select FB_SOFT_CURSOR 1268 help 1269 This is the frame buffer device driver for the Creator, Creator3D, 1270 and Elite3D graphics boards. 1271 1272config FB_TCX 1273 bool "TCX (SS4/SS5 only) support" 1274 depends on FB_SBUS 1275 select FB_CFB_FILLRECT 1276 select FB_CFB_COPYAREA 1277 select FB_CFB_IMAGEBLIT 1278 select FB_SOFT_CURSOR 1279 help 1280 This is the frame buffer device driver for the TCX 24/8bit frame 1281 buffer. 1282 1283config FB_CG14 1284 bool "CGfourteen (SX) support" 1285 depends on FB_SBUS 1286 select FB_CFB_FILLRECT 1287 select FB_CFB_COPYAREA 1288 select FB_CFB_IMAGEBLIT 1289 select FB_SOFT_CURSOR 1290 help 1291 This is the frame buffer device driver for the CGfourteen frame 1292 buffer on Desktop SPARCsystems with the SX graphics option. 1293 1294config FB_P9100 1295 bool "P9100 (Sparcbook 3 only) support" 1296 depends on FB_SBUS 1297 select FB_CFB_FILLRECT 1298 select FB_CFB_COPYAREA 1299 select FB_CFB_IMAGEBLIT 1300 select FB_SOFT_CURSOR 1301 help 1302 This is the frame buffer device driver for the P9100 card 1303 supported on Sparcbook 3 machines. 1304 1305config FB_LEO 1306 bool "Leo (ZX) support" 1307 depends on FB_SBUS 1308 select FB_CFB_FILLRECT 1309 select FB_CFB_COPYAREA 1310 select FB_CFB_IMAGEBLIT 1311 select FB_SOFT_CURSOR 1312 help 1313 This is the frame buffer device driver for the SBUS-based Sun ZX 1314 (leo) frame buffer cards. 1315 1316config FB_PCI 1317 bool "PCI framebuffers" 1318 depends on (FB = y) && PCI && (SPARC64 || SPARC32) 1319 1320config FB_IGA 1321 bool "IGA 168x display support" 1322 depends on SPARC32 && FB_PCI 1323 select FB_CFB_FILLRECT 1324 select FB_CFB_COPYAREA 1325 select FB_CFB_IMAGEBLIT 1326 select FB_SOFT_CURSOR 1327 help 1328 This is the framebuffer device for the INTERGRAPHICS 1680 and 1329 successor frame buffer cards. 1330 1331config FB_HIT 1332 tristate "HD64461 Frame Buffer support" 1333 depends on FB && HD64461 1334 select FB_CFB_FILLRECT 1335 select FB_CFB_COPYAREA 1336 select FB_CFB_IMAGEBLIT 1337 select FB_SOFT_CURSOR 1338 help 1339 This is the frame buffer device driver for the Hitachi HD64461 LCD 1340 frame buffer card. 1341 1342config FB_PMAG_AA 1343 bool "PMAG-AA TURBOchannel framebuffer support" 1344 depends on (FB = y) && MACH_DECSTATION && TC 1345 select FB_CFB_FILLRECT 1346 select FB_CFB_COPYAREA 1347 select FB_CFB_IMAGEBLIT 1348 select FB_SOFT_CURSOR 1349 help 1350 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1) 1351 used mainly in the MIPS-based DECstation series. 1352 1353config FB_PMAG_BA 1354 bool "PMAG-BA TURBOchannel framebuffer support" 1355 depends on (FB = y) && MACH_DECSTATION && TC 1356 select FB_CFB_FILLRECT 1357 select FB_CFB_COPYAREA 1358 select FB_CFB_IMAGEBLIT 1359 select FB_SOFT_CURSOR 1360 help 1361 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) 1362 used mainly in the MIPS-based DECstation series. 1363 1364config FB_PMAGB_B 1365 bool "PMAGB-B TURBOchannel framebuffer support" 1366 depends on (FB = y) && MACH_DECSTATION && TC 1367 select FB_CFB_FILLRECT 1368 select FB_CFB_COPYAREA 1369 select FB_CFB_IMAGEBLIT 1370 select FB_SOFT_CURSOR 1371 help 1372 Support for the PMAGB-B TURBOchannel framebuffer card used mainly 1373 in the MIPS-based DECstation series. The card is currently only 1374 supported in 1280x1024x8 mode. 1375 1376config FB_MAXINE 1377 bool "Maxine (Personal DECstation) onboard framebuffer support" 1378 depends on (FB = y) && MACH_DECSTATION && TC 1379 select FB_CFB_FILLRECT 1380 select FB_CFB_COPYAREA 1381 select FB_CFB_IMAGEBLIT 1382 select FB_SOFT_CURSOR 1383 help 1384 Support for the onboard framebuffer (1024x768x8) in the Personal 1385 DECstation series (Personal DECstation 5000/20, /25, /33, /50, 1386 Codename "Maxine"). 1387 1388config FB_TX3912 1389 bool "TMPTX3912/PR31700 frame buffer support" 1390 depends on (FB = y) && NINO 1391 select FB_CFB_FILLRECT 1392 select FB_CFB_COPYAREA 1393 select FB_CFB_IMAGEBLIT 1394 select FB_SOFT_CURSOR 1395 help 1396 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core 1397 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>. 1398 1399 Say Y here to enable kernel support for the on-board framebuffer. 1400 1401config FB_G364 1402 bool 1403 depends on MIPS_MAGNUM_4000 || OLIVETTI_M700 1404 select FB_CFB_FILLRECT 1405 select FB_CFB_COPYAREA 1406 select FB_CFB_IMAGEBLIT 1407 select FB_SOFT_CURSOR 1408 help 1409 The G364 driver is the framebuffer used in MIPS Magnum 4000 and 1410 Olivetti M700-10 systems. 1411 1412config FB_68328 1413 bool "Motorola 68328 native frame buffer support" 1414 depends on FB && (M68328 || M68EZ328 || M68VZ328) 1415 select FB_CFB_FILLRECT 1416 select FB_CFB_COPYAREA 1417 select FB_CFB_IMAGEBLIT 1418 select FB_SOFT_CURSOR 1419 help 1420 Say Y here if you want to support the built-in frame buffer of 1421 the Motorola 68328 CPU family. 1422 1423config FB_PXA 1424 tristate "PXA LCD framebuffer support" 1425 depends on FB && ARCH_PXA 1426 select FB_CFB_FILLRECT 1427 select FB_CFB_COPYAREA 1428 select FB_CFB_IMAGEBLIT 1429 select FB_SOFT_CURSOR 1430 ---help--- 1431 Frame buffer driver for the built-in LCD controller in the Intel 1432 PXA2x0 processor. 1433 1434 This driver is also available as a module ( = code which can be 1435 inserted and removed from the running kernel whenever you want). The 1436 module will be called vfb. If you want to compile it as a module, 1437 say M here and read <file:Documentation/modules.txt>. 1438 1439 If unsure, say N. 1440 1441config FB_W100 1442 tristate "W100 frame buffer support" 1443 depends on FB && PXA_SHARPSL 1444 select FB_CFB_FILLRECT 1445 select FB_CFB_COPYAREA 1446 select FB_CFB_IMAGEBLIT 1447 select FB_SOFT_CURSOR 1448 ---help--- 1449 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series. 1450 1451 This driver is also available as a module ( = code which can be 1452 inserted and removed from the running kernel whenever you want). The 1453 module will be called vfb. If you want to compile it as a module, 1454 say M here and read <file:Documentation/modules.txt>. 1455 1456 If unsure, say N. 1457 1458config FB_PXA_PARAMETERS 1459 bool "PXA LCD command line parameters" 1460 default n 1461 depends on FB_PXA 1462 ---help--- 1463 Enable the use of kernel command line or module parameters 1464 to configure the physical properties of the LCD panel when 1465 using the PXA LCD driver. 1466 1467 This option allows you to override the panel parameters 1468 supplied by the platform in order to support multiple 1469 different models of flatpanel. If you will only be using a 1470 single model of flatpanel then you can safely leave this 1471 option disabled. 1472 1473 <file:Documentation/fb/pxafb.txt> describes the available parameters. 1474 1475config FB_S1D13XXX 1476 tristate "Epson S1D13XXX framebuffer support" 1477 depends on FB 1478 select FB_CFB_FILLRECT 1479 select FB_CFB_COPYAREA 1480 select FB_CFB_IMAGEBLIT 1481 select FB_SOFT_CURSOR 1482 help 1483 Support for S1D13XXX framebuffer device family (currently only 1484 working with S1D13806). Product specs at 1485 <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm> 1486 1487config FB_VIRTUAL 1488 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)" 1489 depends on FB 1490 select FB_CFB_FILLRECT 1491 select FB_CFB_COPYAREA 1492 select FB_CFB_IMAGEBLIT 1493 select FB_SOFT_CURSOR 1494 ---help--- 1495 This is a `virtual' frame buffer device. It operates on a chunk of 1496 unswappable kernel memory instead of on the memory of a graphics 1497 board. This means you cannot see any output sent to this frame 1498 buffer device, while it does consume precious memory. The main use 1499 of this frame buffer device is testing and debugging the frame 1500 buffer subsystem. Do NOT enable it for normal systems! To protect 1501 the innocent, it has to be enabled explicitly at boot time using the 1502 kernel option `video=vfb:'. 1503 1504 To compile this driver as a module, choose M here: the 1505 module will be called vfb. 1506 1507 If unsure, say N. 1508if VT 1509 source "drivers/video/console/Kconfig" 1510endif 1511 1512if FB || SGI_NEWPORT_CONSOLE 1513 source "drivers/video/logo/Kconfig" 1514endif 1515 1516if FB && SYSFS 1517 source "drivers/video/backlight/Kconfig" 1518endif 1519 1520endmenu 1521 1522