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