diff options
Diffstat (limited to 'drivers/video/fbdev/Kconfig')
-rw-r--r-- | drivers/video/fbdev/Kconfig | 2474 |
1 files changed, 2474 insertions, 0 deletions
diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig new file mode 100644 index 000000000000..e1f47272fdea --- /dev/null +++ b/drivers/video/fbdev/Kconfig | |||
@@ -0,0 +1,2474 @@ | |||
1 | # | ||
2 | # fbdev configuration | ||
3 | # | ||
4 | |||
5 | menuconfig FB | ||
6 | tristate "Support for frame buffer devices" | ||
7 | ---help--- | ||
8 | The frame buffer device provides an abstraction for the graphics | ||
9 | hardware. It represents the frame buffer of some video hardware and | ||
10 | allows application software to access the graphics hardware through | ||
11 | a well-defined interface, so the software doesn't need to know | ||
12 | anything about the low-level (hardware register) stuff. | ||
13 | |||
14 | Frame buffer devices work identically across the different | ||
15 | architectures supported by Linux and make the implementation of | ||
16 | application programs easier and more portable; at this point, an X | ||
17 | server exists which uses the frame buffer device exclusively. | ||
18 | On several non-X86 architectures, the frame buffer device is the | ||
19 | only way to use the graphics hardware. | ||
20 | |||
21 | The device is accessed through special device nodes, usually located | ||
22 | in the /dev directory, i.e. /dev/fb*. | ||
23 | |||
24 | You need an utility program called fbset to make full use of frame | ||
25 | buffer devices. Please read <file:Documentation/fb/framebuffer.txt> | ||
26 | and the Framebuffer-HOWTO at | ||
27 | <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more | ||
28 | information. | ||
29 | |||
30 | Say Y here and to the driver for your graphics board below if you | ||
31 | are compiling a kernel for a non-x86 architecture. | ||
32 | |||
33 | If you are compiling for the x86 architecture, you can say Y if you | ||
34 | want to play with it, but it is not essential. Please note that | ||
35 | running graphical applications that directly touch the hardware | ||
36 | (e.g. an accelerated X server) and that are not frame buffer | ||
37 | device-aware may cause unexpected results. If unsure, say N. | ||
38 | |||
39 | config FIRMWARE_EDID | ||
40 | bool "Enable firmware EDID" | ||
41 | depends on FB | ||
42 | default n | ||
43 | ---help--- | ||
44 | This enables access to the EDID transferred from the firmware. | ||
45 | On the i386, this is from the Video BIOS. Enable this if DDC/I2C | ||
46 | transfers do not work for your driver and if you are using | ||
47 | nvidiafb, i810fb or savagefb. | ||
48 | |||
49 | In general, choosing Y for this option is safe. If you | ||
50 | experience extremely long delays while booting before you get | ||
51 | something on your display, try setting this to N. Matrox cards in | ||
52 | combination with certain motherboards and monitors are known to | ||
53 | suffer from this problem. | ||
54 | |||
55 | config FB_DDC | ||
56 | tristate | ||
57 | depends on FB | ||
58 | select I2C_ALGOBIT | ||
59 | select I2C | ||
60 | default n | ||
61 | |||
62 | config FB_BOOT_VESA_SUPPORT | ||
63 | bool | ||
64 | depends on FB | ||
65 | default n | ||
66 | ---help--- | ||
67 | If true, at least one selected framebuffer driver can take advantage | ||
68 | of VESA video modes set at an early boot stage via the vga= parameter. | ||
69 | |||
70 | config FB_CFB_FILLRECT | ||
71 | tristate | ||
72 | depends on FB | ||
73 | default n | ||
74 | ---help--- | ||
75 | Include the cfb_fillrect function for generic software rectangle | ||
76 | filling. This is used by drivers that don't provide their own | ||
77 | (accelerated) version. | ||
78 | |||
79 | config FB_CFB_COPYAREA | ||
80 | tristate | ||
81 | depends on FB | ||
82 | default n | ||
83 | ---help--- | ||
84 | Include the cfb_copyarea function for generic software area copying. | ||
85 | This is used by drivers that don't provide their own (accelerated) | ||
86 | version. | ||
87 | |||
88 | config FB_CFB_IMAGEBLIT | ||
89 | tristate | ||
90 | depends on FB | ||
91 | default n | ||
92 | ---help--- | ||
93 | Include the cfb_imageblit function for generic software image | ||
94 | blitting. This is used by drivers that don't provide their own | ||
95 | (accelerated) version. | ||
96 | |||
97 | config FB_CFB_REV_PIXELS_IN_BYTE | ||
98 | bool | ||
99 | depends on FB | ||
100 | default n | ||
101 | ---help--- | ||
102 | Allow generic frame-buffer functions to work on displays with 1, 2 | ||
103 | and 4 bits per pixel depths which has opposite order of pixels in | ||
104 | byte order to bytes in long order. | ||
105 | |||
106 | config FB_SYS_FILLRECT | ||
107 | tristate | ||
108 | depends on FB | ||
109 | default n | ||
110 | ---help--- | ||
111 | Include the sys_fillrect function for generic software rectangle | ||
112 | filling. This is used by drivers that don't provide their own | ||
113 | (accelerated) version and the framebuffer is in system RAM. | ||
114 | |||
115 | config FB_SYS_COPYAREA | ||
116 | tristate | ||
117 | depends on FB | ||
118 | default n | ||
119 | ---help--- | ||
120 | Include the sys_copyarea function for generic software area copying. | ||
121 | This is used by drivers that don't provide their own (accelerated) | ||
122 | version and the framebuffer is in system RAM. | ||
123 | |||
124 | config FB_SYS_IMAGEBLIT | ||
125 | tristate | ||
126 | depends on FB | ||
127 | default n | ||
128 | ---help--- | ||
129 | Include the sys_imageblit function for generic software image | ||
130 | blitting. This is used by drivers that don't provide their own | ||
131 | (accelerated) version and the framebuffer is in system RAM. | ||
132 | |||
133 | menuconfig FB_FOREIGN_ENDIAN | ||
134 | bool "Framebuffer foreign endianness support" | ||
135 | depends on FB | ||
136 | ---help--- | ||
137 | This menu will let you enable support for the framebuffers with | ||
138 | non-native endianness (e.g. Little-Endian framebuffer on a | ||
139 | Big-Endian machine). Most probably you don't have such hardware, | ||
140 | so it's safe to say "n" here. | ||
141 | |||
142 | choice | ||
143 | prompt "Choice endianness support" | ||
144 | depends on FB_FOREIGN_ENDIAN | ||
145 | |||
146 | config FB_BOTH_ENDIAN | ||
147 | bool "Support for Big- and Little-Endian framebuffers" | ||
148 | |||
149 | config FB_BIG_ENDIAN | ||
150 | bool "Support for Big-Endian framebuffers only" | ||
151 | |||
152 | config FB_LITTLE_ENDIAN | ||
153 | bool "Support for Little-Endian framebuffers only" | ||
154 | |||
155 | endchoice | ||
156 | |||
157 | config FB_SYS_FOPS | ||
158 | tristate | ||
159 | depends on FB | ||
160 | default n | ||
161 | |||
162 | config FB_DEFERRED_IO | ||
163 | bool | ||
164 | depends on FB | ||
165 | |||
166 | config FB_HECUBA | ||
167 | tristate | ||
168 | depends on FB | ||
169 | depends on FB_DEFERRED_IO | ||
170 | |||
171 | config FB_SVGALIB | ||
172 | tristate | ||
173 | depends on FB | ||
174 | default n | ||
175 | ---help--- | ||
176 | Common utility functions useful to fbdev drivers of VGA-based | ||
177 | cards. | ||
178 | |||
179 | config FB_MACMODES | ||
180 | tristate | ||
181 | depends on FB | ||
182 | default n | ||
183 | |||
184 | config FB_BACKLIGHT | ||
185 | bool | ||
186 | depends on FB | ||
187 | select BACKLIGHT_LCD_SUPPORT | ||
188 | select BACKLIGHT_CLASS_DEVICE | ||
189 | default n | ||
190 | |||
191 | config FB_MODE_HELPERS | ||
192 | bool "Enable Video Mode Handling Helpers" | ||
193 | depends on FB | ||
194 | default n | ||
195 | ---help--- | ||
196 | This enables functions for handling video modes using the | ||
197 | Generalized Timing Formula and the EDID parser. A few drivers rely | ||
198 | on this feature such as the radeonfb, rivafb, and the i810fb. If | ||
199 | your driver does not take advantage of this feature, choosing Y will | ||
200 | just increase the kernel size by about 5K. | ||
201 | |||
202 | config FB_TILEBLITTING | ||
203 | bool "Enable Tile Blitting Support" | ||
204 | depends on FB | ||
205 | default n | ||
206 | ---help--- | ||
207 | This enables tile blitting. Tile blitting is a drawing technique | ||
208 | where the screen is divided into rectangular sections (tiles), whereas | ||
209 | the standard blitting divides the screen into pixels. Because the | ||
210 | default drawing element is a tile, drawing functions will be passed | ||
211 | parameters in terms of number of tiles instead of number of pixels. | ||
212 | For example, to draw a single character, instead of using bitmaps, | ||
213 | an index to an array of bitmaps will be used. To clear or move a | ||
214 | rectangular section of a screen, the rectangle will be described in | ||
215 | terms of number of tiles in the x- and y-axis. | ||
216 | |||
217 | This is particularly important to one driver, matroxfb. If | ||
218 | unsure, say N. | ||
219 | |||
220 | comment "Frame buffer hardware drivers" | ||
221 | depends on FB | ||
222 | |||
223 | config FB_GRVGA | ||
224 | tristate "Aeroflex Gaisler framebuffer support" | ||
225 | depends on FB && SPARC | ||
226 | select FB_CFB_FILLRECT | ||
227 | select FB_CFB_COPYAREA | ||
228 | select FB_CFB_IMAGEBLIT | ||
229 | ---help--- | ||
230 | This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler. | ||
231 | |||
232 | config FB_CIRRUS | ||
233 | tristate "Cirrus Logic support" | ||
234 | depends on FB && (ZORRO || PCI) | ||
235 | select FB_CFB_FILLRECT | ||
236 | select FB_CFB_COPYAREA | ||
237 | select FB_CFB_IMAGEBLIT | ||
238 | ---help--- | ||
239 | This enables support for Cirrus Logic GD542x/543x based boards on | ||
240 | Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum. | ||
241 | |||
242 | If you have a PCI-based system, this enables support for these | ||
243 | chips: GD-543x, GD-544x, GD-5480. | ||
244 | |||
245 | Please read the file <file:Documentation/fb/cirrusfb.txt>. | ||
246 | |||
247 | Say N unless you have such a graphics board or plan to get one | ||
248 | before you next recompile the kernel. | ||
249 | |||
250 | config FB_PM2 | ||
251 | tristate "Permedia2 support" | ||
252 | depends on FB && ((AMIGA && BROKEN) || PCI) | ||
253 | select FB_CFB_FILLRECT | ||
254 | select FB_CFB_COPYAREA | ||
255 | select FB_CFB_IMAGEBLIT | ||
256 | help | ||
257 | This is the frame buffer device driver for cards based on | ||
258 | the 3D Labs Permedia, Permedia 2 and Permedia 2V chips. | ||
259 | The driver was tested on the following cards: | ||
260 | Diamond FireGL 1000 PRO AGP | ||
261 | ELSA Gloria Synergy PCI | ||
262 | Appian Jeronimo PRO (both heads) PCI | ||
263 | 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI | ||
264 | Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC | ||
265 | ASK Graphic Blaster Exxtreme AGP | ||
266 | |||
267 | To compile this driver as a module, choose M here: the | ||
268 | module will be called pm2fb. | ||
269 | |||
270 | config FB_PM2_FIFO_DISCONNECT | ||
271 | bool "enable FIFO disconnect feature" | ||
272 | depends on FB_PM2 && PCI | ||
273 | help | ||
274 | Support the Permedia2 FIFO disconnect feature. | ||
275 | |||
276 | config FB_ARMCLCD | ||
277 | tristate "ARM PrimeCell PL110 support" | ||
278 | depends on ARM || ARM64 || COMPILE_TEST | ||
279 | depends on FB && ARM_AMBA | ||
280 | select FB_CFB_FILLRECT | ||
281 | select FB_CFB_COPYAREA | ||
282 | select FB_CFB_IMAGEBLIT | ||
283 | help | ||
284 | This framebuffer device driver is for the ARM PrimeCell PL110 | ||
285 | Colour LCD controller. ARM PrimeCells provide the building | ||
286 | blocks for System on a Chip devices. | ||
287 | |||
288 | If you want to compile this as a module (=code which can be | ||
289 | inserted into and removed from the running kernel), say M | ||
290 | here and read <file:Documentation/kbuild/modules.txt>. The module | ||
291 | will be called amba-clcd. | ||
292 | |||
293 | config FB_ACORN | ||
294 | bool "Acorn VIDC support" | ||
295 | depends on (FB = y) && ARM && ARCH_ACORN | ||
296 | select FB_CFB_FILLRECT | ||
297 | select FB_CFB_COPYAREA | ||
298 | select FB_CFB_IMAGEBLIT | ||
299 | help | ||
300 | This is the frame buffer device driver for the Acorn VIDC graphics | ||
301 | hardware found in Acorn RISC PCs and other ARM-based machines. If | ||
302 | unsure, say N. | ||
303 | |||
304 | config FB_CLPS711X | ||
305 | bool "CLPS711X LCD support" | ||
306 | depends on (FB = y) && ARM && ARCH_CLPS711X | ||
307 | select FB_CFB_FILLRECT | ||
308 | select FB_CFB_COPYAREA | ||
309 | select FB_CFB_IMAGEBLIT | ||
310 | help | ||
311 | Say Y to enable the Framebuffer driver for the CLPS7111 and | ||
312 | EP7212 processors. | ||
313 | |||
314 | config FB_SA1100 | ||
315 | bool "SA-1100 LCD support" | ||
316 | depends on (FB = y) && ARM && ARCH_SA1100 | ||
317 | select FB_CFB_FILLRECT | ||
318 | select FB_CFB_COPYAREA | ||
319 | select FB_CFB_IMAGEBLIT | ||
320 | help | ||
321 | This is a framebuffer device for the SA-1100 LCD Controller. | ||
322 | See <http://www.linux-fbdev.org/> for information on framebuffer | ||
323 | devices. | ||
324 | |||
325 | If you plan to use the LCD display with your SA-1100 system, say | ||
326 | Y here. | ||
327 | |||
328 | config FB_IMX | ||
329 | tristate "Freescale i.MX1/21/25/27 LCD support" | ||
330 | depends on FB && ARCH_MXC | ||
331 | select BACKLIGHT_LCD_SUPPORT | ||
332 | select LCD_CLASS_DEVICE | ||
333 | select FB_CFB_FILLRECT | ||
334 | select FB_CFB_COPYAREA | ||
335 | select FB_CFB_IMAGEBLIT | ||
336 | select FB_MODE_HELPERS | ||
337 | select VIDEOMODE_HELPERS | ||
338 | |||
339 | config FB_CYBER2000 | ||
340 | tristate "CyberPro 2000/2010/5000 support" | ||
341 | depends on FB && PCI && (BROKEN || !SPARC64) | ||
342 | select FB_CFB_FILLRECT | ||
343 | select FB_CFB_COPYAREA | ||
344 | select FB_CFB_IMAGEBLIT | ||
345 | help | ||
346 | This enables support for the Integraphics CyberPro 20x0 and 5000 | ||
347 | VGA chips used in the Rebel.com Netwinder and other machines. | ||
348 | Say Y if you have a NetWinder or a graphics card containing this | ||
349 | device, otherwise say N. | ||
350 | |||
351 | config FB_CYBER2000_DDC | ||
352 | bool "DDC for CyberPro support" | ||
353 | depends on FB_CYBER2000 | ||
354 | select FB_DDC | ||
355 | default y | ||
356 | help | ||
357 | Say Y here if you want DDC support for your CyberPro graphics | ||
358 | card. This is only I2C bus support, driver does not use EDID. | ||
359 | |||
360 | config FB_CYBER2000_I2C | ||
361 | bool "CyberPro 2000/2010/5000 I2C support" | ||
362 | depends on FB_CYBER2000 && I2C && ARCH_NETWINDER | ||
363 | select I2C_ALGOBIT | ||
364 | help | ||
365 | Enable support for the I2C video decoder interface on the | ||
366 | Integraphics CyberPro 20x0 and 5000 VGA chips. This is used | ||
367 | on the Netwinder machines for the SAA7111 video capture. | ||
368 | |||
369 | config FB_APOLLO | ||
370 | bool | ||
371 | depends on (FB = y) && APOLLO | ||
372 | default y | ||
373 | select FB_CFB_FILLRECT | ||
374 | select FB_CFB_IMAGEBLIT | ||
375 | |||
376 | config FB_Q40 | ||
377 | bool | ||
378 | depends on (FB = y) && Q40 | ||
379 | default y | ||
380 | select FB_CFB_FILLRECT | ||
381 | select FB_CFB_COPYAREA | ||
382 | select FB_CFB_IMAGEBLIT | ||
383 | |||
384 | config FB_AMIGA | ||
385 | tristate "Amiga native chipset support" | ||
386 | depends on FB && AMIGA | ||
387 | help | ||
388 | This is the frame buffer device driver for the builtin graphics | ||
389 | chipset found in Amigas. | ||
390 | |||
391 | To compile this driver as a module, choose M here: the | ||
392 | module will be called amifb. | ||
393 | |||
394 | config FB_AMIGA_OCS | ||
395 | bool "Amiga OCS chipset support" | ||
396 | depends on FB_AMIGA | ||
397 | help | ||
398 | This enables support for the original Agnus and Denise video chips, | ||
399 | found in the Amiga 1000 and most A500's and A2000's. If you intend | ||
400 | to run Linux on any of these systems, say Y; otherwise say N. | ||
401 | |||
402 | config FB_AMIGA_ECS | ||
403 | bool "Amiga ECS chipset support" | ||
404 | depends on FB_AMIGA | ||
405 | help | ||
406 | This enables support for the Enhanced Chip Set, found in later | ||
407 | A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If | ||
408 | you intend to run Linux on any of these systems, say Y; otherwise | ||
409 | say N. | ||
410 | |||
411 | config FB_AMIGA_AGA | ||
412 | bool "Amiga AGA chipset support" | ||
413 | depends on FB_AMIGA | ||
414 | help | ||
415 | This enables support for the Advanced Graphics Architecture (also | ||
416 | known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T | ||
417 | and CD32. If you intend to run Linux on any of these systems, say Y; | ||
418 | otherwise say N. | ||
419 | |||
420 | config FB_FM2 | ||
421 | bool "Amiga FrameMaster II/Rainbow II support" | ||
422 | depends on (FB = y) && ZORRO | ||
423 | select FB_CFB_FILLRECT | ||
424 | select FB_CFB_COPYAREA | ||
425 | select FB_CFB_IMAGEBLIT | ||
426 | help | ||
427 | This is the frame buffer device driver for the Amiga FrameMaster | ||
428 | card from BSC (exhibited 1992 but not shipped as a CBM product). | ||
429 | |||
430 | config FB_ARC | ||
431 | tristate "Arc Monochrome LCD board support" | ||
432 | depends on FB && X86 | ||
433 | select FB_SYS_FILLRECT | ||
434 | select FB_SYS_COPYAREA | ||
435 | select FB_SYS_IMAGEBLIT | ||
436 | select FB_SYS_FOPS | ||
437 | help | ||
438 | This enables support for the Arc Monochrome LCD board. The board | ||
439 | is based on the KS-108 lcd controller and is typically a matrix | ||
440 | of 2*n chips. This driver was tested with a 128x64 panel. This | ||
441 | driver supports it for use with x86 SBCs through a 16 bit GPIO | ||
442 | interface (8 bit data, 8 bit control). If you anticipate using | ||
443 | this driver, say Y or M; otherwise say N. You must specify the | ||
444 | GPIO IO address to be used for setting control and data. | ||
445 | |||
446 | config FB_ATARI | ||
447 | bool "Atari native chipset support" | ||
448 | depends on (FB = y) && ATARI | ||
449 | select FB_CFB_FILLRECT | ||
450 | select FB_CFB_COPYAREA | ||
451 | select FB_CFB_IMAGEBLIT | ||
452 | help | ||
453 | This is the frame buffer device driver for the builtin graphics | ||
454 | chipset found in Ataris. | ||
455 | |||
456 | config FB_OF | ||
457 | bool "Open Firmware frame buffer device support" | ||
458 | depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI) | ||
459 | select FB_CFB_FILLRECT | ||
460 | select FB_CFB_COPYAREA | ||
461 | select FB_CFB_IMAGEBLIT | ||
462 | select FB_MACMODES | ||
463 | help | ||
464 | Say Y if you want support with Open Firmware for your graphics | ||
465 | board. | ||
466 | |||
467 | config FB_CONTROL | ||
468 | bool "Apple \"control\" display support" | ||
469 | depends on (FB = y) && PPC_PMAC && PPC32 | ||
470 | select FB_CFB_FILLRECT | ||
471 | select FB_CFB_COPYAREA | ||
472 | select FB_CFB_IMAGEBLIT | ||
473 | select FB_MACMODES | ||
474 | help | ||
475 | This driver supports a frame buffer for the graphics adapter in the | ||
476 | Power Macintosh 7300 and others. | ||
477 | |||
478 | config FB_PLATINUM | ||
479 | bool "Apple \"platinum\" display support" | ||
480 | depends on (FB = y) && PPC_PMAC && PPC32 | ||
481 | select FB_CFB_FILLRECT | ||
482 | select FB_CFB_COPYAREA | ||
483 | select FB_CFB_IMAGEBLIT | ||
484 | select FB_MACMODES | ||
485 | help | ||
486 | This driver supports a frame buffer for the "platinum" graphics | ||
487 | adapter in some Power Macintoshes. | ||
488 | |||
489 | config FB_VALKYRIE | ||
490 | bool "Apple \"valkyrie\" display support" | ||
491 | depends on (FB = y) && (MAC || (PPC_PMAC && PPC32)) | ||
492 | select FB_CFB_FILLRECT | ||
493 | select FB_CFB_COPYAREA | ||
494 | select FB_CFB_IMAGEBLIT | ||
495 | select FB_MACMODES | ||
496 | help | ||
497 | This driver supports a frame buffer for the "valkyrie" graphics | ||
498 | adapter in some Power Macintoshes. | ||
499 | |||
500 | config FB_CT65550 | ||
501 | bool "Chips 65550 display support" | ||
502 | depends on (FB = y) && PPC32 && PCI | ||
503 | select FB_CFB_FILLRECT | ||
504 | select FB_CFB_COPYAREA | ||
505 | select FB_CFB_IMAGEBLIT | ||
506 | help | ||
507 | This is the frame buffer device driver for the Chips & Technologies | ||
508 | 65550 graphics chip in PowerBooks. | ||
509 | |||
510 | config FB_ASILIANT | ||
511 | bool "Asiliant (Chips) 69000 display support" | ||
512 | depends on (FB = y) && PCI | ||
513 | select FB_CFB_FILLRECT | ||
514 | select FB_CFB_COPYAREA | ||
515 | select FB_CFB_IMAGEBLIT | ||
516 | help | ||
517 | This is the frame buffer device driver for the Asiliant 69030 chipset | ||
518 | |||
519 | config FB_IMSTT | ||
520 | bool "IMS Twin Turbo display support" | ||
521 | depends on (FB = y) && PCI | ||
522 | select FB_CFB_IMAGEBLIT | ||
523 | select FB_MACMODES if PPC | ||
524 | help | ||
525 | The IMS Twin Turbo is a PCI-based frame buffer card bundled with | ||
526 | many Macintosh and compatible computers. | ||
527 | |||
528 | config FB_VGA16 | ||
529 | tristate "VGA 16-color graphics support" | ||
530 | depends on FB && (X86 || PPC) | ||
531 | select FB_CFB_FILLRECT | ||
532 | select FB_CFB_COPYAREA | ||
533 | select FB_CFB_IMAGEBLIT | ||
534 | select VGASTATE | ||
535 | select FONT_8x16 if FRAMEBUFFER_CONSOLE | ||
536 | help | ||
537 | This is the frame buffer device driver for VGA 16 color graphic | ||
538 | cards. Say Y if you have such a card. | ||
539 | |||
540 | To compile this driver as a module, choose M here: the | ||
541 | module will be called vga16fb. | ||
542 | |||
543 | config FB_BF54X_LQ043 | ||
544 | tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)" | ||
545 | depends on FB && (BF54x) && !BF542 | ||
546 | select FB_CFB_FILLRECT | ||
547 | select FB_CFB_COPYAREA | ||
548 | select FB_CFB_IMAGEBLIT | ||
549 | help | ||
550 | This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD | ||
551 | |||
552 | config FB_BFIN_T350MCQB | ||
553 | tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)" | ||
554 | depends on FB && BLACKFIN | ||
555 | select BFIN_GPTIMERS | ||
556 | select FB_CFB_FILLRECT | ||
557 | select FB_CFB_COPYAREA | ||
558 | select FB_CFB_IMAGEBLIT | ||
559 | help | ||
560 | This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD | ||
561 | This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI | ||
562 | It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK. | ||
563 | |||
564 | config FB_BFIN_LQ035Q1 | ||
565 | tristate "SHARP LQ035Q1DH02 TFT LCD" | ||
566 | depends on FB && BLACKFIN && SPI | ||
567 | select FB_CFB_FILLRECT | ||
568 | select FB_CFB_COPYAREA | ||
569 | select FB_CFB_IMAGEBLIT | ||
570 | select BFIN_GPTIMERS | ||
571 | help | ||
572 | This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on | ||
573 | the Blackfin Landscape LCD EZ-Extender Card. | ||
574 | This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI | ||
575 | It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK. | ||
576 | |||
577 | To compile this driver as a module, choose M here: the | ||
578 | module will be called bfin-lq035q1-fb. | ||
579 | |||
580 | config FB_BF537_LQ035 | ||
581 | tristate "SHARP LQ035 TFT LCD (BF537 STAMP)" | ||
582 | depends on FB && (BF534 || BF536 || BF537) && I2C_BLACKFIN_TWI | ||
583 | select FB_CFB_FILLRECT | ||
584 | select FB_CFB_COPYAREA | ||
585 | select FB_CFB_IMAGEBLIT | ||
586 | select BFIN_GPTIMERS | ||
587 | help | ||
588 | This is the framebuffer device for a SHARP LQ035Q7DB03 TFT LCD | ||
589 | attached to a BF537. | ||
590 | |||
591 | To compile this driver as a module, choose M here: the | ||
592 | module will be called bf537-lq035. | ||
593 | |||
594 | config FB_BFIN_7393 | ||
595 | tristate "Blackfin ADV7393 Video encoder" | ||
596 | depends on FB && BLACKFIN | ||
597 | select I2C | ||
598 | select FB_CFB_FILLRECT | ||
599 | select FB_CFB_COPYAREA | ||
600 | select FB_CFB_IMAGEBLIT | ||
601 | help | ||
602 | This is the framebuffer device for a ADV7393 video encoder | ||
603 | attached to a Blackfin on the PPI port. | ||
604 | If your Blackfin board has a ADV7393 select Y. | ||
605 | |||
606 | To compile this driver as a module, choose M here: the | ||
607 | module will be called bfin_adv7393fb. | ||
608 | |||
609 | choice | ||
610 | prompt "Video mode support" | ||
611 | depends on FB_BFIN_7393 | ||
612 | default NTSC | ||
613 | |||
614 | config NTSC | ||
615 | bool 'NTSC 720x480' | ||
616 | |||
617 | config PAL | ||
618 | bool 'PAL 720x576' | ||
619 | |||
620 | config NTSC_640x480 | ||
621 | bool 'NTSC 640x480 (Experimental)' | ||
622 | |||
623 | config PAL_640x480 | ||
624 | bool 'PAL 640x480 (Experimental)' | ||
625 | |||
626 | config NTSC_YCBCR | ||
627 | bool 'NTSC 720x480 YCbCR input' | ||
628 | |||
629 | config PAL_YCBCR | ||
630 | bool 'PAL 720x576 YCbCR input' | ||
631 | |||
632 | endchoice | ||
633 | |||
634 | choice | ||
635 | prompt "Size of ADV7393 frame buffer memory Single/Double Size" | ||
636 | depends on (FB_BFIN_7393) | ||
637 | default ADV7393_1XMEM | ||
638 | |||
639 | config ADV7393_1XMEM | ||
640 | bool 'Single' | ||
641 | |||
642 | config ADV7393_2XMEM | ||
643 | bool 'Double' | ||
644 | endchoice | ||
645 | |||
646 | config FB_STI | ||
647 | tristate "HP STI frame buffer device support" | ||
648 | depends on FB && PARISC | ||
649 | select FB_CFB_FILLRECT | ||
650 | select FB_CFB_COPYAREA | ||
651 | select FB_CFB_IMAGEBLIT | ||
652 | select STI_CONSOLE | ||
653 | select VT | ||
654 | default y | ||
655 | ---help--- | ||
656 | STI refers to the HP "Standard Text Interface" which is a set of | ||
657 | BIOS routines contained in a ROM chip in HP PA-RISC based machines. | ||
658 | Enabling this option will implement the linux framebuffer device | ||
659 | using calls to the STI BIOS routines for initialisation. | ||
660 | |||
661 | If you enable this option, you will get a planar framebuffer device | ||
662 | /dev/fb which will work on the most common HP graphic cards of the | ||
663 | NGLE family, including the artist chips (in the 7xx and Bxxx series), | ||
664 | HCRX, HCRX24, CRX, CRX24 and VisEG series. | ||
665 | |||
666 | It is safe to enable this option, so you should probably say "Y". | ||
667 | |||
668 | config FB_MAC | ||
669 | bool "Generic Macintosh display support" | ||
670 | depends on (FB = y) && MAC | ||
671 | select FB_CFB_FILLRECT | ||
672 | select FB_CFB_COPYAREA | ||
673 | select FB_CFB_IMAGEBLIT | ||
674 | select FB_MACMODES | ||
675 | |||
676 | config FB_HP300 | ||
677 | bool | ||
678 | depends on (FB = y) && DIO | ||
679 | select FB_CFB_IMAGEBLIT | ||
680 | default y | ||
681 | |||
682 | config FB_TGA | ||
683 | tristate "TGA/SFB+ framebuffer support" | ||
684 | depends on FB && (ALPHA || TC) | ||
685 | select FB_CFB_FILLRECT | ||
686 | select FB_CFB_COPYAREA | ||
687 | select FB_CFB_IMAGEBLIT | ||
688 | select BITREVERSE | ||
689 | ---help--- | ||
690 | This is the frame buffer device driver for generic TGA and SFB+ | ||
691 | graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards, | ||
692 | also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3 | ||
693 | TURBOchannel cards, also known as PMAGD-A, -B and -C. | ||
694 | |||
695 | Due to hardware limitations ZLX-E2 and E3 cards are not supported | ||
696 | for DECstation 5000/200 systems. Additionally due to firmware | ||
697 | limitations these cards may cause troubles with booting DECstation | ||
698 | 5000/240 and /260 systems, but are fully supported under Linux if | ||
699 | you manage to get it going. ;-) | ||
700 | |||
701 | Say Y if you have one of those. | ||
702 | |||
703 | config FB_UVESA | ||
704 | tristate "Userspace VESA VGA graphics support" | ||
705 | depends on FB && CONNECTOR | ||
706 | select FB_CFB_FILLRECT | ||
707 | select FB_CFB_COPYAREA | ||
708 | select FB_CFB_IMAGEBLIT | ||
709 | select FB_MODE_HELPERS | ||
710 | help | ||
711 | This is the frame buffer driver for generic VBE 2.0 compliant | ||
712 | graphic cards. It can also take advantage of VBE 3.0 features, | ||
713 | such as refresh rate adjustment. | ||
714 | |||
715 | This driver generally provides more features than vesafb but | ||
716 | requires a userspace helper application called 'v86d'. See | ||
717 | <file:Documentation/fb/uvesafb.txt> for more information. | ||
718 | |||
719 | If unsure, say N. | ||
720 | |||
721 | config FB_VESA | ||
722 | bool "VESA VGA graphics support" | ||
723 | depends on (FB = y) && X86 | ||
724 | select FB_CFB_FILLRECT | ||
725 | select FB_CFB_COPYAREA | ||
726 | select FB_CFB_IMAGEBLIT | ||
727 | select FB_BOOT_VESA_SUPPORT | ||
728 | help | ||
729 | This is the frame buffer device driver for generic VESA 2.0 | ||
730 | compliant graphic cards. The older VESA 1.2 cards are not supported. | ||
731 | You will get a boot time penguin logo at no additional cost. Please | ||
732 | read <file:Documentation/fb/vesafb.txt>. If unsure, say Y. | ||
733 | |||
734 | config FB_EFI | ||
735 | bool "EFI-based Framebuffer Support" | ||
736 | depends on (FB = y) && X86 && EFI | ||
737 | select FB_CFB_FILLRECT | ||
738 | select FB_CFB_COPYAREA | ||
739 | select FB_CFB_IMAGEBLIT | ||
740 | help | ||
741 | This is the EFI frame buffer device driver. If the firmware on | ||
742 | your platform is EFI 1.10 or UEFI 2.0, select Y to add support for | ||
743 | using the EFI framebuffer as your console. | ||
744 | |||
745 | config FB_N411 | ||
746 | tristate "N411 Apollo/Hecuba devkit support" | ||
747 | depends on FB && X86 && MMU | ||
748 | select FB_SYS_FILLRECT | ||
749 | select FB_SYS_COPYAREA | ||
750 | select FB_SYS_IMAGEBLIT | ||
751 | select FB_SYS_FOPS | ||
752 | select FB_DEFERRED_IO | ||
753 | select FB_HECUBA | ||
754 | help | ||
755 | This enables support for the Apollo display controller in its | ||
756 | Hecuba form using the n411 devkit. | ||
757 | |||
758 | config FB_HGA | ||
759 | tristate "Hercules mono graphics support" | ||
760 | depends on FB && X86 | ||
761 | help | ||
762 | Say Y here if you have a Hercules mono graphics card. | ||
763 | |||
764 | To compile this driver as a module, choose M here: the | ||
765 | module will be called hgafb. | ||
766 | |||
767 | As this card technology is at least 25 years old, | ||
768 | most people will answer N here. | ||
769 | |||
770 | config FB_GBE | ||
771 | bool "SGI Graphics Backend frame buffer support" | ||
772 | depends on (FB = y) && SGI_IP32 | ||
773 | select FB_CFB_FILLRECT | ||
774 | select FB_CFB_COPYAREA | ||
775 | select FB_CFB_IMAGEBLIT | ||
776 | help | ||
777 | This is the frame buffer device driver for SGI Graphics Backend. | ||
778 | This chip is used in SGI O2 and Visual Workstation 320/540. | ||
779 | |||
780 | config FB_GBE_MEM | ||
781 | int "Video memory size in MB" | ||
782 | depends on FB_GBE | ||
783 | default 4 | ||
784 | help | ||
785 | This is the amount of memory reserved for the framebuffer, | ||
786 | which can be any value between 1MB and 8MB. | ||
787 | |||
788 | config FB_SBUS | ||
789 | bool "SBUS and UPA framebuffers" | ||
790 | depends on (FB = y) && SPARC | ||
791 | help | ||
792 | Say Y if you want support for SBUS or UPA based frame buffer device. | ||
793 | |||
794 | config FB_BW2 | ||
795 | bool "BWtwo support" | ||
796 | depends on (FB = y) && (SPARC && FB_SBUS) | ||
797 | select FB_CFB_FILLRECT | ||
798 | select FB_CFB_COPYAREA | ||
799 | select FB_CFB_IMAGEBLIT | ||
800 | help | ||
801 | This is the frame buffer device driver for the BWtwo frame buffer. | ||
802 | |||
803 | config FB_CG3 | ||
804 | bool "CGthree support" | ||
805 | depends on (FB = y) && (SPARC && FB_SBUS) | ||
806 | select FB_CFB_FILLRECT | ||
807 | select FB_CFB_COPYAREA | ||
808 | select FB_CFB_IMAGEBLIT | ||
809 | help | ||
810 | This is the frame buffer device driver for the CGthree frame buffer. | ||
811 | |||
812 | config FB_CG6 | ||
813 | bool "CGsix (GX,TurboGX) support" | ||
814 | depends on (FB = y) && (SPARC && FB_SBUS) | ||
815 | select FB_CFB_COPYAREA | ||
816 | select FB_CFB_IMAGEBLIT | ||
817 | help | ||
818 | This is the frame buffer device driver for the CGsix (GX, TurboGX) | ||
819 | frame buffer. | ||
820 | |||
821 | config FB_FFB | ||
822 | bool "Creator/Creator3D/Elite3D support" | ||
823 | depends on FB_SBUS && SPARC64 | ||
824 | select FB_CFB_COPYAREA | ||
825 | select FB_CFB_IMAGEBLIT | ||
826 | help | ||
827 | This is the frame buffer device driver for the Creator, Creator3D, | ||
828 | and Elite3D graphics boards. | ||
829 | |||
830 | config FB_TCX | ||
831 | bool "TCX (SS4/SS5 only) support" | ||
832 | depends on FB_SBUS | ||
833 | select FB_CFB_FILLRECT | ||
834 | select FB_CFB_COPYAREA | ||
835 | select FB_CFB_IMAGEBLIT | ||
836 | help | ||
837 | This is the frame buffer device driver for the TCX 24/8bit frame | ||
838 | buffer. | ||
839 | |||
840 | config FB_CG14 | ||
841 | bool "CGfourteen (SX) support" | ||
842 | depends on FB_SBUS | ||
843 | select FB_CFB_FILLRECT | ||
844 | select FB_CFB_COPYAREA | ||
845 | select FB_CFB_IMAGEBLIT | ||
846 | help | ||
847 | This is the frame buffer device driver for the CGfourteen frame | ||
848 | buffer on Desktop SPARCsystems with the SX graphics option. | ||
849 | |||
850 | config FB_P9100 | ||
851 | bool "P9100 (Sparcbook 3 only) support" | ||
852 | depends on FB_SBUS | ||
853 | select FB_CFB_FILLRECT | ||
854 | select FB_CFB_COPYAREA | ||
855 | select FB_CFB_IMAGEBLIT | ||
856 | help | ||
857 | This is the frame buffer device driver for the P9100 card | ||
858 | supported on Sparcbook 3 machines. | ||
859 | |||
860 | config FB_LEO | ||
861 | bool "Leo (ZX) support" | ||
862 | depends on FB_SBUS | ||
863 | select FB_CFB_FILLRECT | ||
864 | select FB_CFB_COPYAREA | ||
865 | select FB_CFB_IMAGEBLIT | ||
866 | help | ||
867 | This is the frame buffer device driver for the SBUS-based Sun ZX | ||
868 | (leo) frame buffer cards. | ||
869 | |||
870 | config FB_IGA | ||
871 | bool "IGA 168x display support" | ||
872 | depends on (FB = y) && SPARC32 | ||
873 | select FB_CFB_FILLRECT | ||
874 | select FB_CFB_COPYAREA | ||
875 | select FB_CFB_IMAGEBLIT | ||
876 | help | ||
877 | This is the framebuffer device for the INTERGRAPHICS 1680 and | ||
878 | successor frame buffer cards. | ||
879 | |||
880 | config FB_XVR500 | ||
881 | bool "Sun XVR-500 3DLABS Wildcat support" | ||
882 | depends on (FB = y) && PCI && SPARC64 | ||
883 | select FB_CFB_FILLRECT | ||
884 | select FB_CFB_COPYAREA | ||
885 | select FB_CFB_IMAGEBLIT | ||
886 | help | ||
887 | This is the framebuffer device for the Sun XVR-500 and similar | ||
888 | graphics cards based upon the 3DLABS Wildcat chipset. The driver | ||
889 | only works on sparc64 systems where the system firmware has | ||
890 | mostly initialized the card already. It is treated as a | ||
891 | completely dumb framebuffer device. | ||
892 | |||
893 | config FB_XVR2500 | ||
894 | bool "Sun XVR-2500 3DLABS Wildcat support" | ||
895 | depends on (FB = y) && PCI && SPARC64 | ||
896 | select FB_CFB_FILLRECT | ||
897 | select FB_CFB_COPYAREA | ||
898 | select FB_CFB_IMAGEBLIT | ||
899 | help | ||
900 | This is the framebuffer device for the Sun XVR-2500 and similar | ||
901 | graphics cards based upon the 3DLABS Wildcat chipset. The driver | ||
902 | only works on sparc64 systems where the system firmware has | ||
903 | mostly initialized the card already. It is treated as a | ||
904 | completely dumb framebuffer device. | ||
905 | |||
906 | config FB_XVR1000 | ||
907 | bool "Sun XVR-1000 support" | ||
908 | depends on (FB = y) && SPARC64 | ||
909 | select FB_CFB_FILLRECT | ||
910 | select FB_CFB_COPYAREA | ||
911 | select FB_CFB_IMAGEBLIT | ||
912 | help | ||
913 | This is the framebuffer device for the Sun XVR-1000 and similar | ||
914 | graphics cards. The driver only works on sparc64 systems where | ||
915 | the system firmware has mostly initialized the card already. It | ||
916 | is treated as a completely dumb framebuffer device. | ||
917 | |||
918 | config FB_PVR2 | ||
919 | tristate "NEC PowerVR 2 display support" | ||
920 | depends on FB && SH_DREAMCAST | ||
921 | select FB_CFB_FILLRECT | ||
922 | select FB_CFB_COPYAREA | ||
923 | select FB_CFB_IMAGEBLIT | ||
924 | ---help--- | ||
925 | Say Y here if you have a PowerVR 2 card in your box. If you plan to | ||
926 | run linux on your Dreamcast, you will have to say Y here. | ||
927 | This driver may or may not work on other PowerVR 2 cards, but is | ||
928 | totally untested. Use at your own risk. If unsure, say N. | ||
929 | |||
930 | To compile this driver as a module, choose M here: the | ||
931 | module will be called pvr2fb. | ||
932 | |||
933 | You can pass several parameters to the driver at boot time or at | ||
934 | module load time. The parameters look like "video=pvr2:XXX", where | ||
935 | the meaning of XXX can be found at the end of the main source file | ||
936 | (<file:drivers/video/pvr2fb.c>). Please see the file | ||
937 | <file:Documentation/fb/pvr2fb.txt>. | ||
938 | |||
939 | config FB_OPENCORES | ||
940 | tristate "OpenCores VGA/LCD core 2.0 framebuffer support" | ||
941 | depends on FB && HAS_DMA | ||
942 | select FB_CFB_FILLRECT | ||
943 | select FB_CFB_COPYAREA | ||
944 | select FB_CFB_IMAGEBLIT | ||
945 | help | ||
946 | This enables support for the OpenCores VGA/LCD core. | ||
947 | |||
948 | The OpenCores VGA/LCD core is typically used together with | ||
949 | softcore CPUs (e.g. OpenRISC or Microblaze) or hard processor | ||
950 | systems (e.g. Altera socfpga or Xilinx Zynq) on FPGAs. | ||
951 | |||
952 | The source code and specification for the core is available at | ||
953 | <http://opencores.org/project,vga_lcd> | ||
954 | |||
955 | config FB_S1D13XXX | ||
956 | tristate "Epson S1D13XXX framebuffer support" | ||
957 | depends on FB | ||
958 | select FB_CFB_FILLRECT | ||
959 | select FB_CFB_COPYAREA | ||
960 | select FB_CFB_IMAGEBLIT | ||
961 | help | ||
962 | Support for S1D13XXX framebuffer device family (currently only | ||
963 | working with S1D13806). Product specs at | ||
964 | <http://vdc.epson.com/> | ||
965 | |||
966 | config FB_ATMEL | ||
967 | tristate "AT91/AT32 LCD Controller support" | ||
968 | depends on FB && HAVE_FB_ATMEL | ||
969 | select FB_CFB_FILLRECT | ||
970 | select FB_CFB_COPYAREA | ||
971 | select FB_CFB_IMAGEBLIT | ||
972 | select FB_MODE_HELPERS | ||
973 | select VIDEOMODE_HELPERS | ||
974 | help | ||
975 | This enables support for the AT91/AT32 LCD Controller. | ||
976 | |||
977 | config FB_INTSRAM | ||
978 | bool "Frame Buffer in internal SRAM" | ||
979 | depends on FB_ATMEL && ARCH_AT91SAM9261 | ||
980 | help | ||
981 | Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want | ||
982 | to let frame buffer in external SDRAM. | ||
983 | |||
984 | config FB_ATMEL_STN | ||
985 | bool "Use a STN display with AT91/AT32 LCD Controller" | ||
986 | depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK) | ||
987 | default n | ||
988 | help | ||
989 | Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD | ||
990 | Controller. Say N if you want to connect a TFT. | ||
991 | |||
992 | If unsure, say N. | ||
993 | |||
994 | config FB_NVIDIA | ||
995 | tristate "nVidia Framebuffer Support" | ||
996 | depends on FB && PCI | ||
997 | select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT | ||
998 | select FB_MODE_HELPERS | ||
999 | select FB_CFB_FILLRECT | ||
1000 | select FB_CFB_COPYAREA | ||
1001 | select FB_CFB_IMAGEBLIT | ||
1002 | select BITREVERSE | ||
1003 | select VGASTATE | ||
1004 | help | ||
1005 | This driver supports graphics boards with the nVidia chips, TNT | ||
1006 | and newer. For very old chipsets, such as the RIVA128, then use | ||
1007 | the rivafb. | ||
1008 | Say Y if you have such a graphics board. | ||
1009 | |||
1010 | To compile this driver as a module, choose M here: the | ||
1011 | module will be called nvidiafb. | ||
1012 | |||
1013 | config FB_NVIDIA_I2C | ||
1014 | bool "Enable DDC Support" | ||
1015 | depends on FB_NVIDIA | ||
1016 | select FB_DDC | ||
1017 | help | ||
1018 | This enables I2C support for nVidia Chipsets. This is used | ||
1019 | only for getting EDID information from the attached display | ||
1020 | allowing for robust video mode handling and switching. | ||
1021 | |||
1022 | Because fbdev-2.6 requires that drivers must be able to | ||
1023 | independently validate video mode parameters, you should say Y | ||
1024 | here. | ||
1025 | |||
1026 | config FB_NVIDIA_DEBUG | ||
1027 | bool "Lots of debug output" | ||
1028 | depends on FB_NVIDIA | ||
1029 | default n | ||
1030 | help | ||
1031 | Say Y here if you want the nVidia driver to output all sorts | ||
1032 | of debugging information to provide to the maintainer when | ||
1033 | something goes wrong. | ||
1034 | |||
1035 | config FB_NVIDIA_BACKLIGHT | ||
1036 | bool "Support for backlight control" | ||
1037 | depends on FB_NVIDIA | ||
1038 | default y | ||
1039 | help | ||
1040 | Say Y here if you want to control the backlight of your display. | ||
1041 | |||
1042 | config FB_RIVA | ||
1043 | tristate "nVidia Riva support" | ||
1044 | depends on FB && PCI | ||
1045 | select FB_BACKLIGHT if FB_RIVA_BACKLIGHT | ||
1046 | select FB_MODE_HELPERS | ||
1047 | select FB_CFB_FILLRECT | ||
1048 | select FB_CFB_COPYAREA | ||
1049 | select FB_CFB_IMAGEBLIT | ||
1050 | select BITREVERSE | ||
1051 | select VGASTATE | ||
1052 | help | ||
1053 | This driver supports graphics boards with the nVidia Riva/Geforce | ||
1054 | chips. | ||
1055 | Say Y if you have such a graphics board. | ||
1056 | |||
1057 | To compile this driver as a module, choose M here: the | ||
1058 | module will be called rivafb. | ||
1059 | |||
1060 | config FB_RIVA_I2C | ||
1061 | bool "Enable DDC Support" | ||
1062 | depends on FB_RIVA | ||
1063 | select FB_DDC | ||
1064 | help | ||
1065 | This enables I2C support for nVidia Chipsets. This is used | ||
1066 | only for getting EDID information from the attached display | ||
1067 | allowing for robust video mode handling and switching. | ||
1068 | |||
1069 | Because fbdev-2.6 requires that drivers must be able to | ||
1070 | independently validate video mode parameters, you should say Y | ||
1071 | here. | ||
1072 | |||
1073 | config FB_RIVA_DEBUG | ||
1074 | bool "Lots of debug output" | ||
1075 | depends on FB_RIVA | ||
1076 | default n | ||
1077 | help | ||
1078 | Say Y here if you want the Riva driver to output all sorts | ||
1079 | of debugging information to provide to the maintainer when | ||
1080 | something goes wrong. | ||
1081 | |||
1082 | config FB_RIVA_BACKLIGHT | ||
1083 | bool "Support for backlight control" | ||
1084 | depends on FB_RIVA | ||
1085 | default y | ||
1086 | help | ||
1087 | Say Y here if you want to control the backlight of your display. | ||
1088 | |||
1089 | config FB_I740 | ||
1090 | tristate "Intel740 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 | select VGASTATE | ||
1097 | select FB_DDC | ||
1098 | help | ||
1099 | This driver supports graphics cards based on Intel740 chip. | ||
1100 | |||
1101 | config FB_I810 | ||
1102 | tristate "Intel 810/815 support" | ||
1103 | depends on FB && PCI && X86_32 && AGP_INTEL | ||
1104 | select FB_MODE_HELPERS | ||
1105 | select FB_CFB_FILLRECT | ||
1106 | select FB_CFB_COPYAREA | ||
1107 | select FB_CFB_IMAGEBLIT | ||
1108 | select VGASTATE | ||
1109 | help | ||
1110 | This driver supports the on-board graphics built in to the Intel 810 | ||
1111 | and 815 chipsets. Say Y if you have and plan to use such a board. | ||
1112 | |||
1113 | To compile this driver as a module, choose M here: the | ||
1114 | module will be called i810fb. | ||
1115 | |||
1116 | For more information, please read | ||
1117 | <file:Documentation/fb/intel810.txt> | ||
1118 | |||
1119 | config FB_I810_GTF | ||
1120 | bool "use VESA Generalized Timing Formula" | ||
1121 | depends on FB_I810 | ||
1122 | help | ||
1123 | If you say Y, then the VESA standard, Generalized Timing Formula | ||
1124 | or GTF, will be used to calculate the required video timing values | ||
1125 | per video mode. Since the GTF allows nondiscrete timings | ||
1126 | (nondiscrete being a range of values as opposed to discrete being a | ||
1127 | set of values), you'll be able to use any combination of horizontal | ||
1128 | and vertical resolutions, and vertical refresh rates without having | ||
1129 | to specify your own timing parameters. This is especially useful | ||
1130 | to maximize the performance of an aging display, or if you just | ||
1131 | have a display with nonstandard dimensions. A VESA compliant | ||
1132 | monitor is recommended, but can still work with non-compliant ones. | ||
1133 | If you need or want this, then select this option. The timings may | ||
1134 | not be compliant with Intel's recommended values. Use at your own | ||
1135 | risk. | ||
1136 | |||
1137 | If you say N, the driver will revert to discrete video timings | ||
1138 | using a set recommended by Intel in their documentation. | ||
1139 | |||
1140 | If unsure, say N. | ||
1141 | |||
1142 | config FB_I810_I2C | ||
1143 | bool "Enable DDC Support" | ||
1144 | depends on FB_I810 && FB_I810_GTF | ||
1145 | select FB_DDC | ||
1146 | help | ||
1147 | |||
1148 | config FB_LE80578 | ||
1149 | tristate "Intel LE80578 (Vermilion) support" | ||
1150 | depends on FB && PCI && X86 | ||
1151 | select FB_MODE_HELPERS | ||
1152 | select FB_CFB_FILLRECT | ||
1153 | select FB_CFB_COPYAREA | ||
1154 | select FB_CFB_IMAGEBLIT | ||
1155 | help | ||
1156 | This driver supports the LE80578 (Vermilion Range) chipset | ||
1157 | |||
1158 | config FB_CARILLO_RANCH | ||
1159 | tristate "Intel Carillo Ranch support" | ||
1160 | depends on FB_LE80578 && FB && PCI && X86 | ||
1161 | help | ||
1162 | This driver supports the LE80578 (Carillo Ranch) board | ||
1163 | |||
1164 | config FB_INTEL | ||
1165 | tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support" | ||
1166 | depends on FB && PCI && X86 && AGP_INTEL && EXPERT | ||
1167 | select FB_MODE_HELPERS | ||
1168 | select FB_CFB_FILLRECT | ||
1169 | select FB_CFB_COPYAREA | ||
1170 | select FB_CFB_IMAGEBLIT | ||
1171 | select FB_BOOT_VESA_SUPPORT if FB_INTEL = y | ||
1172 | depends on !DRM_I915 | ||
1173 | help | ||
1174 | This driver supports the on-board graphics built in to the Intel | ||
1175 | 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets. | ||
1176 | Say Y if you have and plan to use such a board. | ||
1177 | |||
1178 | To make FB_INTELFB=Y work you need to say AGP_INTEL=y too. | ||
1179 | |||
1180 | To compile this driver as a module, choose M here: the | ||
1181 | module will be called intelfb. | ||
1182 | |||
1183 | For more information, please read <file:Documentation/fb/intelfb.txt> | ||
1184 | |||
1185 | config FB_INTEL_DEBUG | ||
1186 | bool "Intel driver Debug Messages" | ||
1187 | depends on FB_INTEL | ||
1188 | ---help--- | ||
1189 | Say Y here if you want the Intel driver to output all sorts | ||
1190 | of debugging information to provide to the maintainer when | ||
1191 | something goes wrong. | ||
1192 | |||
1193 | config FB_INTEL_I2C | ||
1194 | bool "DDC/I2C for Intel framebuffer support" | ||
1195 | depends on FB_INTEL | ||
1196 | select FB_DDC | ||
1197 | default y | ||
1198 | help | ||
1199 | Say Y here if you want DDC/I2C support for your on-board Intel graphics. | ||
1200 | |||
1201 | config FB_MATROX | ||
1202 | tristate "Matrox acceleration" | ||
1203 | depends on FB && PCI | ||
1204 | select FB_CFB_FILLRECT | ||
1205 | select FB_CFB_COPYAREA | ||
1206 | select FB_CFB_IMAGEBLIT | ||
1207 | select FB_TILEBLITTING | ||
1208 | select FB_MACMODES if PPC_PMAC | ||
1209 | ---help--- | ||
1210 | Say Y here if you have a Matrox Millennium, Matrox Millennium II, | ||
1211 | Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox | ||
1212 | Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video, | ||
1213 | Matrox G400, G450 or G550 card in your box. | ||
1214 | |||
1215 | To compile this driver as a module, choose M here: the | ||
1216 | module will be called matroxfb. | ||
1217 | |||
1218 | You can pass several parameters to the driver at boot time or at | ||
1219 | module load time. The parameters look like "video=matroxfb:XXX", and | ||
1220 | are described in <file:Documentation/fb/matroxfb.txt>. | ||
1221 | |||
1222 | config FB_MATROX_MILLENIUM | ||
1223 | bool "Millennium I/II support" | ||
1224 | depends on FB_MATROX | ||
1225 | help | ||
1226 | Say Y here if you have a Matrox Millennium or Matrox Millennium II | ||
1227 | video card. If you select "Advanced lowlevel driver options" below, | ||
1228 | you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp | ||
1229 | packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can | ||
1230 | also use font widths different from 8. | ||
1231 | |||
1232 | config FB_MATROX_MYSTIQUE | ||
1233 | bool "Mystique support" | ||
1234 | depends on FB_MATROX | ||
1235 | help | ||
1236 | Say Y here if you have a Matrox Mystique or Matrox Mystique 220 | ||
1237 | video card. If you select "Advanced lowlevel driver options" below, | ||
1238 | you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp | ||
1239 | packed pixel and 32 bpp packed pixel. You can also use font widths | ||
1240 | different from 8. | ||
1241 | |||
1242 | config FB_MATROX_G | ||
1243 | bool "G100/G200/G400/G450/G550 support" | ||
1244 | depends on FB_MATROX | ||
1245 | ---help--- | ||
1246 | Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based | ||
1247 | video card. If you select "Advanced lowlevel driver options", you | ||
1248 | should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed | ||
1249 | pixel and 32 bpp packed pixel. You can also use font widths | ||
1250 | different from 8. | ||
1251 | |||
1252 | If you need support for G400 secondary head, you must say Y to | ||
1253 | "Matrox I2C support" and "G400 second head support" right below. | ||
1254 | G450/G550 secondary head and digital output are supported without | ||
1255 | additional modules. | ||
1256 | |||
1257 | The driver starts in monitor mode. You must use the matroxset tool | ||
1258 | (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to | ||
1259 | swap primary and secondary head outputs, or to change output mode. | ||
1260 | Secondary head driver always start in 640x480 resolution and you | ||
1261 | must use fbset to change it. | ||
1262 | |||
1263 | Do not forget that second head supports only 16 and 32 bpp | ||
1264 | packed pixels, so it is a good idea to compile them into the kernel | ||
1265 | too. You can use only some font widths, as the driver uses generic | ||
1266 | painting procedures (the secondary head does not use acceleration | ||
1267 | engine). | ||
1268 | |||
1269 | G450/G550 hardware can display TV picture only from secondary CRTC, | ||
1270 | and it performs no scaling, so picture must have 525 or 625 lines. | ||
1271 | |||
1272 | config FB_MATROX_I2C | ||
1273 | tristate "Matrox I2C support" | ||
1274 | depends on FB_MATROX | ||
1275 | select FB_DDC | ||
1276 | ---help--- | ||
1277 | This drivers creates I2C buses which are needed for accessing the | ||
1278 | DDC (I2C) bus present on all Matroxes, an I2C bus which | ||
1279 | interconnects Matrox optional devices, like MGA-TVO on G200 and | ||
1280 | G400, and the secondary head DDC bus, present on G400 only. | ||
1281 | |||
1282 | You can say Y or M here if you want to experiment with monitor | ||
1283 | detection code. You must say Y or M here if you want to use either | ||
1284 | second head of G400 or MGA-TVO on G200 or G400. | ||
1285 | |||
1286 | If you compile it as module, it will create a module named | ||
1287 | i2c-matroxfb. | ||
1288 | |||
1289 | config FB_MATROX_MAVEN | ||
1290 | tristate "G400 second head support" | ||
1291 | depends on FB_MATROX_G && FB_MATROX_I2C | ||
1292 | ---help--- | ||
1293 | WARNING !!! This support does not work with G450 !!! | ||
1294 | |||
1295 | Say Y or M here if you want to use a secondary head (meaning two | ||
1296 | monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary | ||
1297 | head is not compatible with accelerated XFree 3.3.x SVGA servers - | ||
1298 | secondary head output is blanked while you are in X. With XFree | ||
1299 | 3.9.17 preview you can use both heads if you use SVGA over fbdev or | ||
1300 | the fbdev driver on first head and the fbdev driver on second head. | ||
1301 | |||
1302 | If you compile it as module, two modules are created, | ||
1303 | matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for | ||
1304 | both G200 and G400, matroxfb_crtc2 is needed only by G400. You must | ||
1305 | also load i2c-matroxfb to get it to run. | ||
1306 | |||
1307 | The driver starts in monitor mode and you must use the matroxset | ||
1308 | tool (available at | ||
1309 | <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to | ||
1310 | PAL or NTSC or to swap primary and secondary head outputs. | ||
1311 | Secondary head driver also always start in 640x480 resolution, you | ||
1312 | must use fbset to change it. | ||
1313 | |||
1314 | Also do not forget that second head supports only 16 and 32 bpp | ||
1315 | packed pixels, so it is a good idea to compile them into the kernel | ||
1316 | too. You can use only some font widths, as the driver uses generic | ||
1317 | painting procedures (the secondary head does not use acceleration | ||
1318 | engine). | ||
1319 | |||
1320 | config FB_RADEON | ||
1321 | tristate "ATI Radeon display support" | ||
1322 | depends on FB && PCI | ||
1323 | select FB_BACKLIGHT if FB_RADEON_BACKLIGHT | ||
1324 | select FB_MODE_HELPERS | ||
1325 | select FB_CFB_FILLRECT | ||
1326 | select FB_CFB_COPYAREA | ||
1327 | select FB_CFB_IMAGEBLIT | ||
1328 | select FB_MACMODES if PPC_OF | ||
1329 | help | ||
1330 | Choose this option if you want to use an ATI Radeon graphics card as | ||
1331 | a framebuffer device. There are both PCI and AGP versions. You | ||
1332 | don't need to choose this to run the Radeon in plain VGA mode. | ||
1333 | |||
1334 | There is a product page at | ||
1335 | http://products.amd.com/en-us/GraphicCardResult.aspx | ||
1336 | |||
1337 | config FB_RADEON_I2C | ||
1338 | bool "DDC/I2C for ATI Radeon support" | ||
1339 | depends on FB_RADEON | ||
1340 | select FB_DDC | ||
1341 | default y | ||
1342 | help | ||
1343 | Say Y here if you want DDC/I2C support for your Radeon board. | ||
1344 | |||
1345 | config FB_RADEON_BACKLIGHT | ||
1346 | bool "Support for backlight control" | ||
1347 | depends on FB_RADEON | ||
1348 | default y | ||
1349 | help | ||
1350 | Say Y here if you want to control the backlight of your display. | ||
1351 | |||
1352 | config FB_RADEON_DEBUG | ||
1353 | bool "Lots of debug output from Radeon driver" | ||
1354 | depends on FB_RADEON | ||
1355 | default n | ||
1356 | help | ||
1357 | Say Y here if you want the Radeon driver to output all sorts | ||
1358 | of debugging information to provide to the maintainer when | ||
1359 | something goes wrong. | ||
1360 | |||
1361 | config FB_ATY128 | ||
1362 | tristate "ATI Rage128 display support" | ||
1363 | depends on FB && PCI | ||
1364 | select FB_CFB_FILLRECT | ||
1365 | select FB_CFB_COPYAREA | ||
1366 | select FB_CFB_IMAGEBLIT | ||
1367 | select FB_BACKLIGHT if FB_ATY128_BACKLIGHT | ||
1368 | select FB_MACMODES if PPC_PMAC | ||
1369 | help | ||
1370 | This driver supports graphics boards with the ATI Rage128 chips. | ||
1371 | Say Y if you have such a graphics board and read | ||
1372 | <file:Documentation/fb/aty128fb.txt>. | ||
1373 | |||
1374 | To compile this driver as a module, choose M here: the | ||
1375 | module will be called aty128fb. | ||
1376 | |||
1377 | config FB_ATY128_BACKLIGHT | ||
1378 | bool "Support for backlight control" | ||
1379 | depends on FB_ATY128 | ||
1380 | default y | ||
1381 | help | ||
1382 | Say Y here if you want to control the backlight of your display. | ||
1383 | |||
1384 | config FB_ATY | ||
1385 | tristate "ATI Mach64 display support" if PCI || ATARI | ||
1386 | depends on FB && !SPARC32 | ||
1387 | select FB_CFB_FILLRECT | ||
1388 | select FB_CFB_COPYAREA | ||
1389 | select FB_CFB_IMAGEBLIT | ||
1390 | select FB_BACKLIGHT if FB_ATY_BACKLIGHT | ||
1391 | select FB_MACMODES if PPC | ||
1392 | help | ||
1393 | This driver supports graphics boards with the ATI Mach64 chips. | ||
1394 | Say Y if you have such a graphics board. | ||
1395 | |||
1396 | To compile this driver as a module, choose M here: the | ||
1397 | module will be called atyfb. | ||
1398 | |||
1399 | config FB_ATY_CT | ||
1400 | bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support" | ||
1401 | depends on PCI && FB_ATY | ||
1402 | default y if SPARC64 && PCI | ||
1403 | help | ||
1404 | Say Y here to support use of ATI's 64-bit Rage boards (or other | ||
1405 | boards based on the Mach64 CT, VT, GT, and LT chipsets) as a | ||
1406 | framebuffer device. The ATI product support page for these boards | ||
1407 | is at <http://support.ati.com/products/pc/mach64/mach64.html>. | ||
1408 | |||
1409 | config FB_ATY_GENERIC_LCD | ||
1410 | bool "Mach64 generic LCD support" | ||
1411 | depends on FB_ATY_CT | ||
1412 | help | ||
1413 | Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility, | ||
1414 | Rage XC, or Rage XL chipset. | ||
1415 | |||
1416 | config FB_ATY_GX | ||
1417 | bool "Mach64 GX support" if PCI | ||
1418 | depends on FB_ATY | ||
1419 | default y if ATARI | ||
1420 | help | ||
1421 | Say Y here to support use of the ATI Mach64 Graphics Expression | ||
1422 | board (or other boards based on the Mach64 GX chipset) as a | ||
1423 | framebuffer device. The ATI product support page for these boards | ||
1424 | is at | ||
1425 | <http://support.ati.com/products/pc/mach64/graphics_xpression.html>. | ||
1426 | |||
1427 | config FB_ATY_BACKLIGHT | ||
1428 | bool "Support for backlight control" | ||
1429 | depends on FB_ATY | ||
1430 | default y | ||
1431 | help | ||
1432 | Say Y here if you want to control the backlight of your display. | ||
1433 | |||
1434 | config FB_S3 | ||
1435 | tristate "S3 Trio/Virge support" | ||
1436 | depends on FB && PCI | ||
1437 | select FB_CFB_FILLRECT | ||
1438 | select FB_CFB_COPYAREA | ||
1439 | select FB_CFB_IMAGEBLIT | ||
1440 | select FB_TILEBLITTING | ||
1441 | select FB_SVGALIB | ||
1442 | select VGASTATE | ||
1443 | select FONT_8x16 if FRAMEBUFFER_CONSOLE | ||
1444 | ---help--- | ||
1445 | Driver for graphics boards with S3 Trio / S3 Virge chip. | ||
1446 | |||
1447 | config FB_S3_DDC | ||
1448 | bool "DDC for S3 support" | ||
1449 | depends on FB_S3 | ||
1450 | select FB_DDC | ||
1451 | default y | ||
1452 | help | ||
1453 | Say Y here if you want DDC support for your S3 graphics card. | ||
1454 | |||
1455 | config FB_SAVAGE | ||
1456 | tristate "S3 Savage support" | ||
1457 | depends on FB && PCI | ||
1458 | select FB_MODE_HELPERS | ||
1459 | select FB_CFB_FILLRECT | ||
1460 | select FB_CFB_COPYAREA | ||
1461 | select FB_CFB_IMAGEBLIT | ||
1462 | select VGASTATE | ||
1463 | help | ||
1464 | This driver supports notebooks and computers with S3 Savage PCI/AGP | ||
1465 | chips. | ||
1466 | |||
1467 | Say Y if you have such a graphics card. | ||
1468 | |||
1469 | To compile this driver as a module, choose M here; the module | ||
1470 | will be called savagefb. | ||
1471 | |||
1472 | config FB_SAVAGE_I2C | ||
1473 | bool "Enable DDC2 Support" | ||
1474 | depends on FB_SAVAGE | ||
1475 | select FB_DDC | ||
1476 | help | ||
1477 | This enables I2C support for S3 Savage Chipsets. This is used | ||
1478 | only for getting EDID information from the attached display | ||
1479 | allowing for robust video mode handling and switching. | ||
1480 | |||
1481 | Because fbdev-2.6 requires that drivers must be able to | ||
1482 | independently validate video mode parameters, you should say Y | ||
1483 | here. | ||
1484 | |||
1485 | config FB_SAVAGE_ACCEL | ||
1486 | bool "Enable Console Acceleration" | ||
1487 | depends on FB_SAVAGE | ||
1488 | default n | ||
1489 | help | ||
1490 | This option will compile in console acceleration support. If | ||
1491 | the resulting framebuffer console has bothersome glitches, then | ||
1492 | choose N here. | ||
1493 | |||
1494 | config FB_SIS | ||
1495 | tristate "SiS/XGI display support" | ||
1496 | depends on FB && PCI | ||
1497 | select FB_CFB_FILLRECT | ||
1498 | select FB_CFB_COPYAREA | ||
1499 | select FB_CFB_IMAGEBLIT | ||
1500 | select FB_BOOT_VESA_SUPPORT if FB_SIS = y | ||
1501 | help | ||
1502 | This is the frame buffer device driver for the SiS 300, 315, 330 | ||
1503 | and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets. | ||
1504 | Specs available at <http://www.sis.com> and <http://www.xgitech.com>. | ||
1505 | |||
1506 | To compile this driver as a module, choose M here; the module | ||
1507 | will be called sisfb. | ||
1508 | |||
1509 | config FB_SIS_300 | ||
1510 | bool "SiS 300 series support" | ||
1511 | depends on FB_SIS | ||
1512 | help | ||
1513 | Say Y here to support use of the SiS 300/305, 540, 630 and 730. | ||
1514 | |||
1515 | config FB_SIS_315 | ||
1516 | bool "SiS 315/330/340 series and XGI support" | ||
1517 | depends on FB_SIS | ||
1518 | help | ||
1519 | Say Y here to support use of the SiS 315, 330 and 340 series | ||
1520 | (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well | ||
1521 | as XGI V3XT, V5, V8 and Z7. | ||
1522 | |||
1523 | config FB_VIA | ||
1524 | tristate "VIA UniChrome (Pro) and Chrome9 display support" | ||
1525 | depends on FB && PCI && X86 | ||
1526 | select FB_CFB_FILLRECT | ||
1527 | select FB_CFB_COPYAREA | ||
1528 | select FB_CFB_IMAGEBLIT | ||
1529 | select I2C_ALGOBIT | ||
1530 | select I2C | ||
1531 | select GPIOLIB | ||
1532 | help | ||
1533 | This is the frame buffer device driver for Graphics chips of VIA | ||
1534 | UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/ | ||
1535 | CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896 | ||
1536 | /P4M900,VX800) | ||
1537 | Say Y if you have a VIA UniChrome graphics board. | ||
1538 | |||
1539 | To compile this driver as a module, choose M here: the | ||
1540 | module will be called viafb. | ||
1541 | |||
1542 | if FB_VIA | ||
1543 | |||
1544 | config FB_VIA_DIRECT_PROCFS | ||
1545 | bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)" | ||
1546 | depends on FB_VIA | ||
1547 | default n | ||
1548 | help | ||
1549 | Allow direct hardware access to some output registers via procfs. | ||
1550 | This is dangerous but may provide the only chance to get the | ||
1551 | correct output device configuration. | ||
1552 | Its use is strongly discouraged. | ||
1553 | |||
1554 | config FB_VIA_X_COMPATIBILITY | ||
1555 | bool "X server compatibility" | ||
1556 | depends on FB_VIA | ||
1557 | default n | ||
1558 | help | ||
1559 | This option reduces the functionality (power saving, ...) of the | ||
1560 | framebuffer to avoid negative impact on the OpenChrome X server. | ||
1561 | If you use any X server other than fbdev you should enable this | ||
1562 | otherwise it should be safe to disable it and allow using all | ||
1563 | features. | ||
1564 | |||
1565 | endif | ||
1566 | |||
1567 | config FB_NEOMAGIC | ||
1568 | tristate "NeoMagic display support" | ||
1569 | depends on FB && PCI | ||
1570 | select FB_MODE_HELPERS | ||
1571 | select FB_CFB_FILLRECT | ||
1572 | select FB_CFB_COPYAREA | ||
1573 | select FB_CFB_IMAGEBLIT | ||
1574 | select VGASTATE | ||
1575 | help | ||
1576 | This driver supports notebooks with NeoMagic PCI chips. | ||
1577 | Say Y if you have such a graphics card. | ||
1578 | |||
1579 | To compile this driver as a module, choose M here: the | ||
1580 | module will be called neofb. | ||
1581 | |||
1582 | config FB_KYRO | ||
1583 | tristate "IMG Kyro support" | ||
1584 | depends on FB && PCI | ||
1585 | select FB_CFB_FILLRECT | ||
1586 | select FB_CFB_COPYAREA | ||
1587 | select FB_CFB_IMAGEBLIT | ||
1588 | help | ||
1589 | Say Y here if you have a STG4000 / Kyro / PowerVR 3 based | ||
1590 | graphics board. | ||
1591 | |||
1592 | To compile this driver as a module, choose M here: the | ||
1593 | module will be called kyrofb. | ||
1594 | |||
1595 | config FB_3DFX | ||
1596 | tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support" | ||
1597 | depends on FB && PCI | ||
1598 | select FB_CFB_IMAGEBLIT | ||
1599 | select FB_CFB_FILLRECT | ||
1600 | select FB_CFB_COPYAREA | ||
1601 | select FB_MODE_HELPERS | ||
1602 | help | ||
1603 | This driver supports graphics boards with the 3Dfx Banshee, | ||
1604 | Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have | ||
1605 | such a graphics board. | ||
1606 | |||
1607 | To compile this driver as a module, choose M here: the | ||
1608 | module will be called tdfxfb. | ||
1609 | |||
1610 | config FB_3DFX_ACCEL | ||
1611 | bool "3Dfx Acceleration functions" | ||
1612 | depends on FB_3DFX | ||
1613 | ---help--- | ||
1614 | This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer | ||
1615 | device driver with acceleration functions. | ||
1616 | |||
1617 | config FB_3DFX_I2C | ||
1618 | bool "Enable DDC/I2C support" | ||
1619 | depends on FB_3DFX | ||
1620 | select FB_DDC | ||
1621 | default y | ||
1622 | help | ||
1623 | Say Y here if you want DDC/I2C support for your 3dfx Voodoo3. | ||
1624 | |||
1625 | config FB_VOODOO1 | ||
1626 | tristate "3Dfx Voodoo Graphics (sst1) support" | ||
1627 | depends on FB && PCI | ||
1628 | select FB_CFB_FILLRECT | ||
1629 | select FB_CFB_COPYAREA | ||
1630 | select FB_CFB_IMAGEBLIT | ||
1631 | ---help--- | ||
1632 | Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or | ||
1633 | Voodoo2 (cvg) based graphics card. | ||
1634 | |||
1635 | To compile this driver as a module, choose M here: the | ||
1636 | module will be called sstfb. | ||
1637 | |||
1638 | WARNING: Do not use any application that uses the 3D engine | ||
1639 | (namely glide) while using this driver. | ||
1640 | Please read the <file:Documentation/fb/sstfb.txt> for supported | ||
1641 | options and other important info support. | ||
1642 | |||
1643 | config FB_VT8623 | ||
1644 | tristate "VIA VT8623 support" | ||
1645 | depends on FB && PCI | ||
1646 | select FB_CFB_FILLRECT | ||
1647 | select FB_CFB_COPYAREA | ||
1648 | select FB_CFB_IMAGEBLIT | ||
1649 | select FB_TILEBLITTING | ||
1650 | select FB_SVGALIB | ||
1651 | select VGASTATE | ||
1652 | select FONT_8x16 if FRAMEBUFFER_CONSOLE | ||
1653 | ---help--- | ||
1654 | Driver for CastleRock integrated graphics core in the | ||
1655 | VIA VT8623 [Apollo CLE266] chipset. | ||
1656 | |||
1657 | config FB_TRIDENT | ||
1658 | tristate "Trident/CyberXXX/CyberBlade support" | ||
1659 | depends on FB && PCI | ||
1660 | select FB_CFB_FILLRECT | ||
1661 | select FB_CFB_COPYAREA | ||
1662 | select FB_CFB_IMAGEBLIT | ||
1663 | ---help--- | ||
1664 | This is the frame buffer device driver for Trident PCI/AGP chipsets. | ||
1665 | Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D | ||
1666 | and Blade XP. | ||
1667 | There are also integrated versions of these chips called CyberXXXX, | ||
1668 | CyberImage or CyberBlade. These chips are mostly found in laptops | ||
1669 | but also on some motherboards including early VIA EPIA motherboards. | ||
1670 | For more information, read <file:Documentation/fb/tridentfb.txt> | ||
1671 | |||
1672 | Say Y if you have such a graphics board. | ||
1673 | |||
1674 | To compile this driver as a module, choose M here: the | ||
1675 | module will be called tridentfb. | ||
1676 | |||
1677 | config FB_ARK | ||
1678 | tristate "ARK 2000PV support" | ||
1679 | depends on FB && PCI | ||
1680 | select FB_CFB_FILLRECT | ||
1681 | select FB_CFB_COPYAREA | ||
1682 | select FB_CFB_IMAGEBLIT | ||
1683 | select FB_TILEBLITTING | ||
1684 | select FB_SVGALIB | ||
1685 | select VGASTATE | ||
1686 | select FONT_8x16 if FRAMEBUFFER_CONSOLE | ||
1687 | ---help--- | ||
1688 | Driver for PCI graphics boards with ARK 2000PV chip | ||
1689 | and ICS 5342 RAMDAC. | ||
1690 | |||
1691 | config FB_PM3 | ||
1692 | tristate "Permedia3 support" | ||
1693 | depends on FB && PCI | ||
1694 | select FB_CFB_FILLRECT | ||
1695 | select FB_CFB_COPYAREA | ||
1696 | select FB_CFB_IMAGEBLIT | ||
1697 | help | ||
1698 | This is the frame buffer device driver for the 3DLabs Permedia3 | ||
1699 | chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & | ||
1700 | similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000 | ||
1701 | and maybe other boards. | ||
1702 | |||
1703 | config FB_CARMINE | ||
1704 | tristate "Fujitsu carmine frame buffer support" | ||
1705 | depends on FB && PCI | ||
1706 | select FB_CFB_FILLRECT | ||
1707 | select FB_CFB_COPYAREA | ||
1708 | select FB_CFB_IMAGEBLIT | ||
1709 | help | ||
1710 | This is the frame buffer device driver for the Fujitsu Carmine chip. | ||
1711 | The driver provides two independent frame buffer devices. | ||
1712 | |||
1713 | choice | ||
1714 | depends on FB_CARMINE | ||
1715 | prompt "DRAM timing" | ||
1716 | default FB_CARMINE_DRAM_EVAL | ||
1717 | |||
1718 | config FB_CARMINE_DRAM_EVAL | ||
1719 | bool "Eval board timings" | ||
1720 | help | ||
1721 | Use timings which work on the eval card. | ||
1722 | |||
1723 | config CARMINE_DRAM_CUSTOM | ||
1724 | bool "Custom board timings" | ||
1725 | help | ||
1726 | Use custom board timings. | ||
1727 | endchoice | ||
1728 | |||
1729 | config FB_AU1100 | ||
1730 | bool "Au1100 LCD Driver" | ||
1731 | depends on (FB = y) && MIPS_ALCHEMY | ||
1732 | select FB_CFB_FILLRECT | ||
1733 | select FB_CFB_COPYAREA | ||
1734 | select FB_CFB_IMAGEBLIT | ||
1735 | help | ||
1736 | This is the framebuffer driver for the AMD Au1100 SOC. It can drive | ||
1737 | various panels and CRTs by passing in kernel cmd line option | ||
1738 | au1100fb:panel=<name>. | ||
1739 | |||
1740 | config FB_AU1200 | ||
1741 | bool "Au1200/Au1300 LCD Driver" | ||
1742 | depends on (FB = y) && MIPS_ALCHEMY | ||
1743 | select FB_SYS_FILLRECT | ||
1744 | select FB_SYS_COPYAREA | ||
1745 | select FB_SYS_IMAGEBLIT | ||
1746 | select FB_SYS_FOPS | ||
1747 | help | ||
1748 | This is the framebuffer driver for the Au1200/Au1300 SOCs. | ||
1749 | It can drive various panels and CRTs by passing in kernel cmd line | ||
1750 | option au1200fb:panel=<name>. | ||
1751 | |||
1752 | config FB_VT8500 | ||
1753 | bool "VIA VT8500 framebuffer support" | ||
1754 | depends on (FB = y) && ARM && ARCH_VT8500 | ||
1755 | select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS) | ||
1756 | select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS) | ||
1757 | select FB_SYS_IMAGEBLIT | ||
1758 | select FB_MODE_HELPERS | ||
1759 | select VIDEOMODE_HELPERS | ||
1760 | help | ||
1761 | This is the framebuffer driver for VIA VT8500 integrated LCD | ||
1762 | controller. | ||
1763 | |||
1764 | config FB_WM8505 | ||
1765 | bool "Wondermedia WM8xxx-series frame buffer support" | ||
1766 | depends on (FB = y) && ARM && ARCH_VT8500 | ||
1767 | select FB_SYS_FILLRECT if (!FB_WMT_GE_ROPS) | ||
1768 | select FB_SYS_COPYAREA if (!FB_WMT_GE_ROPS) | ||
1769 | select FB_SYS_IMAGEBLIT | ||
1770 | select FB_MODE_HELPERS | ||
1771 | select VIDEOMODE_HELPERS | ||
1772 | help | ||
1773 | This is the framebuffer driver for WonderMedia WM8xxx-series | ||
1774 | integrated LCD controller. This driver covers the WM8505, WM8650 | ||
1775 | and WM8850 SoCs. | ||
1776 | |||
1777 | config FB_WMT_GE_ROPS | ||
1778 | bool "VT8500/WM8xxx accelerated raster ops support" | ||
1779 | depends on (FB = y) && (FB_VT8500 || FB_WM8505) | ||
1780 | default n | ||
1781 | help | ||
1782 | This adds support for accelerated raster operations on the | ||
1783 | VIA VT8500 and Wondermedia 85xx series SoCs. | ||
1784 | |||
1785 | source "drivers/video/fbdev/geode/Kconfig" | ||
1786 | |||
1787 | config FB_HIT | ||
1788 | tristate "HD64461 Frame Buffer support" | ||
1789 | depends on FB && HD64461 | ||
1790 | select FB_CFB_FILLRECT | ||
1791 | select FB_CFB_COPYAREA | ||
1792 | select FB_CFB_IMAGEBLIT | ||
1793 | help | ||
1794 | This is the frame buffer device driver for the Hitachi HD64461 LCD | ||
1795 | frame buffer card. | ||
1796 | |||
1797 | config FB_PMAG_AA | ||
1798 | bool "PMAG-AA TURBOchannel framebuffer support" | ||
1799 | depends on (FB = y) && TC | ||
1800 | select FB_CFB_FILLRECT | ||
1801 | select FB_CFB_COPYAREA | ||
1802 | select FB_CFB_IMAGEBLIT | ||
1803 | help | ||
1804 | Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1) | ||
1805 | used mainly in the MIPS-based DECstation series. | ||
1806 | |||
1807 | config FB_PMAG_BA | ||
1808 | tristate "PMAG-BA TURBOchannel framebuffer support" | ||
1809 | depends on FB && TC | ||
1810 | select FB_CFB_FILLRECT | ||
1811 | select FB_CFB_COPYAREA | ||
1812 | select FB_CFB_IMAGEBLIT | ||
1813 | help | ||
1814 | Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) | ||
1815 | used mainly in the MIPS-based DECstation series. | ||
1816 | |||
1817 | config FB_PMAGB_B | ||
1818 | tristate "PMAGB-B TURBOchannel framebuffer support" | ||
1819 | depends on FB && TC | ||
1820 | select FB_CFB_FILLRECT | ||
1821 | select FB_CFB_COPYAREA | ||
1822 | select FB_CFB_IMAGEBLIT | ||
1823 | help | ||
1824 | Support for the PMAGB-B TURBOchannel framebuffer card used mainly | ||
1825 | in the MIPS-based DECstation series. The card is currently only | ||
1826 | supported in 1280x1024x8 mode. | ||
1827 | |||
1828 | config FB_MAXINE | ||
1829 | bool "Maxine (Personal DECstation) onboard framebuffer support" | ||
1830 | depends on (FB = y) && MACH_DECSTATION | ||
1831 | select FB_CFB_FILLRECT | ||
1832 | select FB_CFB_COPYAREA | ||
1833 | select FB_CFB_IMAGEBLIT | ||
1834 | help | ||
1835 | Support for the onboard framebuffer (1024x768x8) in the Personal | ||
1836 | DECstation series (Personal DECstation 5000/20, /25, /33, /50, | ||
1837 | Codename "Maxine"). | ||
1838 | |||
1839 | config FB_G364 | ||
1840 | bool "G364 frame buffer support" | ||
1841 | depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700) | ||
1842 | select FB_CFB_FILLRECT | ||
1843 | select FB_CFB_COPYAREA | ||
1844 | select FB_CFB_IMAGEBLIT | ||
1845 | help | ||
1846 | The G364 driver is the framebuffer used in MIPS Magnum 4000 and | ||
1847 | Olivetti M700-10 systems. | ||
1848 | |||
1849 | config FB_68328 | ||
1850 | bool "Motorola 68328 native frame buffer support" | ||
1851 | depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328) | ||
1852 | select FB_CFB_FILLRECT | ||
1853 | select FB_CFB_COPYAREA | ||
1854 | select FB_CFB_IMAGEBLIT | ||
1855 | help | ||
1856 | Say Y here if you want to support the built-in frame buffer of | ||
1857 | the Motorola 68328 CPU family. | ||
1858 | |||
1859 | config FB_PXA168 | ||
1860 | tristate "PXA168/910 LCD framebuffer support" | ||
1861 | depends on FB && (CPU_PXA168 || CPU_PXA910) | ||
1862 | select FB_CFB_FILLRECT | ||
1863 | select FB_CFB_COPYAREA | ||
1864 | select FB_CFB_IMAGEBLIT | ||
1865 | ---help--- | ||
1866 | Frame buffer driver for the built-in LCD controller in the Marvell | ||
1867 | MMP processor. | ||
1868 | |||
1869 | config FB_PXA | ||
1870 | tristate "PXA LCD framebuffer support" | ||
1871 | depends on FB && ARCH_PXA | ||
1872 | select FB_CFB_FILLRECT | ||
1873 | select FB_CFB_COPYAREA | ||
1874 | select FB_CFB_IMAGEBLIT | ||
1875 | ---help--- | ||
1876 | Frame buffer driver for the built-in LCD controller in the Intel | ||
1877 | PXA2x0 processor. | ||
1878 | |||
1879 | This driver is also available as a module ( = code which can be | ||
1880 | inserted and removed from the running kernel whenever you want). The | ||
1881 | module will be called pxafb. If you want to compile it as a module, | ||
1882 | say M here and read <file:Documentation/kbuild/modules.txt>. | ||
1883 | |||
1884 | If unsure, say N. | ||
1885 | |||
1886 | config FB_PXA_OVERLAY | ||
1887 | bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer" | ||
1888 | default n | ||
1889 | depends on FB_PXA && (PXA27x || PXA3xx) | ||
1890 | |||
1891 | config FB_PXA_SMARTPANEL | ||
1892 | bool "PXA Smartpanel LCD support" | ||
1893 | default n | ||
1894 | depends on FB_PXA | ||
1895 | |||
1896 | config FB_PXA_PARAMETERS | ||
1897 | bool "PXA LCD command line parameters" | ||
1898 | default n | ||
1899 | depends on FB_PXA | ||
1900 | ---help--- | ||
1901 | Enable the use of kernel command line or module parameters | ||
1902 | to configure the physical properties of the LCD panel when | ||
1903 | using the PXA LCD driver. | ||
1904 | |||
1905 | This option allows you to override the panel parameters | ||
1906 | supplied by the platform in order to support multiple | ||
1907 | different models of flatpanel. If you will only be using a | ||
1908 | single model of flatpanel then you can safely leave this | ||
1909 | option disabled. | ||
1910 | |||
1911 | <file:Documentation/fb/pxafb.txt> describes the available parameters. | ||
1912 | |||
1913 | config PXA3XX_GCU | ||
1914 | tristate "PXA3xx 2D graphics accelerator driver" | ||
1915 | depends on FB_PXA | ||
1916 | help | ||
1917 | Kernelspace driver for the 2D graphics controller unit (GCU) | ||
1918 | found on PXA3xx processors. There is a counterpart driver in the | ||
1919 | DirectFB suite, see http://www.directfb.org/ | ||
1920 | |||
1921 | If you compile this as a module, it will be called pxa3xx_gcu. | ||
1922 | |||
1923 | config FB_MBX | ||
1924 | tristate "2700G LCD framebuffer support" | ||
1925 | depends on FB && ARCH_PXA | ||
1926 | select FB_CFB_FILLRECT | ||
1927 | select FB_CFB_COPYAREA | ||
1928 | select FB_CFB_IMAGEBLIT | ||
1929 | ---help--- | ||
1930 | Framebuffer driver for the Intel 2700G (Marathon) Graphics | ||
1931 | Accelerator | ||
1932 | |||
1933 | config FB_MBX_DEBUG | ||
1934 | bool "Enable debugging info via debugfs" | ||
1935 | depends on FB_MBX && DEBUG_FS | ||
1936 | default n | ||
1937 | ---help--- | ||
1938 | Enable this if you want debugging information using the debug | ||
1939 | filesystem (debugfs) | ||
1940 | |||
1941 | If unsure, say N. | ||
1942 | |||
1943 | config FB_FSL_DIU | ||
1944 | tristate "Freescale DIU framebuffer support" | ||
1945 | depends on FB && FSL_SOC | ||
1946 | select FB_MODE_HELPERS | ||
1947 | select FB_CFB_FILLRECT | ||
1948 | select FB_CFB_COPYAREA | ||
1949 | select FB_CFB_IMAGEBLIT | ||
1950 | select PPC_LIB_RHEAP | ||
1951 | ---help--- | ||
1952 | Framebuffer driver for the Freescale SoC DIU | ||
1953 | |||
1954 | config FB_W100 | ||
1955 | tristate "W100 frame buffer support" | ||
1956 | depends on FB && ARCH_PXA | ||
1957 | select FB_CFB_FILLRECT | ||
1958 | select FB_CFB_COPYAREA | ||
1959 | select FB_CFB_IMAGEBLIT | ||
1960 | ---help--- | ||
1961 | Frame buffer driver for the w100 as found on the Sharp SL-Cxx series. | ||
1962 | It can also drive the w3220 chip found on iPAQ hx4700. | ||
1963 | |||
1964 | This driver is also available as a module ( = code which can be | ||
1965 | inserted and removed from the running kernel whenever you want). The | ||
1966 | module will be called w100fb. If you want to compile it as a module, | ||
1967 | say M here and read <file:Documentation/kbuild/modules.txt>. | ||
1968 | |||
1969 | If unsure, say N. | ||
1970 | |||
1971 | config FB_SH_MOBILE_LCDC | ||
1972 | tristate "SuperH Mobile LCDC framebuffer support" | ||
1973 | depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK | ||
1974 | select FB_SYS_FILLRECT | ||
1975 | select FB_SYS_COPYAREA | ||
1976 | select FB_SYS_IMAGEBLIT | ||
1977 | select FB_SYS_FOPS | ||
1978 | select FB_DEFERRED_IO | ||
1979 | select FB_BACKLIGHT | ||
1980 | select SH_MIPI_DSI if SH_LCD_MIPI_DSI | ||
1981 | ---help--- | ||
1982 | Frame buffer driver for the on-chip SH-Mobile LCD controller. | ||
1983 | |||
1984 | config FB_SH_MOBILE_HDMI | ||
1985 | tristate "SuperH Mobile HDMI controller support" | ||
1986 | depends on FB_SH_MOBILE_LCDC | ||
1987 | select FB_MODE_HELPERS | ||
1988 | select SOUND | ||
1989 | select SND | ||
1990 | select SND_SOC | ||
1991 | ---help--- | ||
1992 | Driver for the on-chip SH-Mobile HDMI controller. | ||
1993 | |||
1994 | config FB_TMIO | ||
1995 | tristate "Toshiba Mobile IO FrameBuffer support" | ||
1996 | depends on FB && MFD_CORE | ||
1997 | select FB_CFB_FILLRECT | ||
1998 | select FB_CFB_COPYAREA | ||
1999 | select FB_CFB_IMAGEBLIT | ||
2000 | ---help--- | ||
2001 | Frame buffer driver for the Toshiba Mobile IO integrated as found | ||
2002 | on the Sharp SL-6000 series | ||
2003 | |||
2004 | This driver is also available as a module ( = code which can be | ||
2005 | inserted and removed from the running kernel whenever you want). The | ||
2006 | module will be called tmiofb. If you want to compile it as a module, | ||
2007 | say M here and read <file:Documentation/kbuild/modules.txt>. | ||
2008 | |||
2009 | If unsure, say N. | ||
2010 | |||
2011 | config FB_TMIO_ACCELL | ||
2012 | bool "tmiofb acceleration" | ||
2013 | depends on FB_TMIO | ||
2014 | default y | ||
2015 | |||
2016 | config FB_S3C | ||
2017 | tristate "Samsung S3C framebuffer support" | ||
2018 | depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || ARCH_S5P64X0 || \ | ||
2019 | ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS) | ||
2020 | select FB_CFB_FILLRECT | ||
2021 | select FB_CFB_COPYAREA | ||
2022 | select FB_CFB_IMAGEBLIT | ||
2023 | ---help--- | ||
2024 | Frame buffer driver for the built-in FB controller in the Samsung | ||
2025 | SoC line from the S3C2443 onwards, including the S3C2416, S3C2450, | ||
2026 | and the S3C64XX series such as the S3C6400 and S3C6410. | ||
2027 | |||
2028 | These chips all have the same basic framebuffer design with the | ||
2029 | actual capabilities depending on the chip. For instance the S3C6400 | ||
2030 | and S3C6410 support 4 hardware windows whereas the S3C24XX series | ||
2031 | currently only have two. | ||
2032 | |||
2033 | Currently the support is only for the S3C6400 and S3C6410 SoCs. | ||
2034 | |||
2035 | config FB_S3C_DEBUG_REGWRITE | ||
2036 | bool "Debug register writes" | ||
2037 | depends on FB_S3C | ||
2038 | ---help--- | ||
2039 | Show all register writes via pr_debug() | ||
2040 | |||
2041 | config FB_S3C2410 | ||
2042 | tristate "S3C2410 LCD framebuffer support" | ||
2043 | depends on FB && ARCH_S3C24XX | ||
2044 | select FB_CFB_FILLRECT | ||
2045 | select FB_CFB_COPYAREA | ||
2046 | select FB_CFB_IMAGEBLIT | ||
2047 | ---help--- | ||
2048 | Frame buffer driver for the built-in LCD controller in the Samsung | ||
2049 | S3C2410 processor. | ||
2050 | |||
2051 | This driver is also available as a module ( = code which can be | ||
2052 | inserted and removed from the running kernel whenever you want). The | ||
2053 | module will be called s3c2410fb. If you want to compile it as a module, | ||
2054 | say M here and read <file:Documentation/kbuild/modules.txt>. | ||
2055 | |||
2056 | If unsure, say N. | ||
2057 | config FB_S3C2410_DEBUG | ||
2058 | bool "S3C2410 lcd debug messages" | ||
2059 | depends on FB_S3C2410 | ||
2060 | help | ||
2061 | Turn on debugging messages. Note that you can set/unset at run time | ||
2062 | through sysfs | ||
2063 | |||
2064 | config FB_NUC900 | ||
2065 | bool "NUC900 LCD framebuffer support" | ||
2066 | depends on FB && ARCH_W90X900 | ||
2067 | select FB_CFB_FILLRECT | ||
2068 | select FB_CFB_COPYAREA | ||
2069 | select FB_CFB_IMAGEBLIT | ||
2070 | ---help--- | ||
2071 | Frame buffer driver for the built-in LCD controller in the Nuvoton | ||
2072 | NUC900 processor | ||
2073 | |||
2074 | config GPM1040A0_320X240 | ||
2075 | bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD" | ||
2076 | depends on FB_NUC900 | ||
2077 | |||
2078 | config FB_SM501 | ||
2079 | tristate "Silicon Motion SM501 framebuffer support" | ||
2080 | depends on FB && MFD_SM501 | ||
2081 | select FB_CFB_FILLRECT | ||
2082 | select FB_CFB_COPYAREA | ||
2083 | select FB_CFB_IMAGEBLIT | ||
2084 | ---help--- | ||
2085 | Frame buffer driver for the CRT and LCD controllers in the Silicon | ||
2086 | Motion SM501. | ||
2087 | |||
2088 | This driver is also available as a module ( = code which can be | ||
2089 | inserted and removed from the running kernel whenever you want). The | ||
2090 | module will be called sm501fb. If you want to compile it as a module, | ||
2091 | say M here and read <file:Documentation/kbuild/modules.txt>. | ||
2092 | |||
2093 | If unsure, say N. | ||
2094 | |||
2095 | config FB_SMSCUFX | ||
2096 | tristate "SMSC UFX6000/7000 USB Framebuffer support" | ||
2097 | depends on FB && USB | ||
2098 | select FB_MODE_HELPERS | ||
2099 | select FB_SYS_FILLRECT | ||
2100 | select FB_SYS_COPYAREA | ||
2101 | select FB_SYS_IMAGEBLIT | ||
2102 | select FB_SYS_FOPS | ||
2103 | select FB_DEFERRED_IO | ||
2104 | ---help--- | ||
2105 | This is a kernel framebuffer driver for SMSC UFX USB devices. | ||
2106 | Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and | ||
2107 | mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000 | ||
2108 | (USB 3.0) devices. | ||
2109 | To compile as a module, choose M here: the module name is smscufx. | ||
2110 | |||
2111 | config FB_UDL | ||
2112 | tristate "Displaylink USB Framebuffer support" | ||
2113 | depends on FB && USB | ||
2114 | select FB_MODE_HELPERS | ||
2115 | select FB_SYS_FILLRECT | ||
2116 | select FB_SYS_COPYAREA | ||
2117 | select FB_SYS_IMAGEBLIT | ||
2118 | select FB_SYS_FOPS | ||
2119 | select FB_DEFERRED_IO | ||
2120 | ---help--- | ||
2121 | This is a kernel framebuffer driver for DisplayLink USB devices. | ||
2122 | Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and | ||
2123 | mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices. | ||
2124 | To compile as a module, choose M here: the module name is udlfb. | ||
2125 | |||
2126 | config FB_IBM_GXT4500 | ||
2127 | tristate "Framebuffer support for IBM GXT4000P/4500P/6000P/6500P adaptors" | ||
2128 | depends on FB && PPC | ||
2129 | select FB_CFB_FILLRECT | ||
2130 | select FB_CFB_COPYAREA | ||
2131 | select FB_CFB_IMAGEBLIT | ||
2132 | ---help--- | ||
2133 | Say Y here to enable support for the IBM GXT4000P/6000P and | ||
2134 | GXT4500P/6500P display adaptor based on Raster Engine RC1000, | ||
2135 | found on some IBM System P (pSeries) machines. This driver | ||
2136 | doesn't use Geometry Engine GT1000. | ||
2137 | |||
2138 | config FB_PS3 | ||
2139 | tristate "PS3 GPU framebuffer driver" | ||
2140 | depends on FB && PS3_PS3AV | ||
2141 | select FB_SYS_FILLRECT | ||
2142 | select FB_SYS_COPYAREA | ||
2143 | select FB_SYS_IMAGEBLIT | ||
2144 | select FB_SYS_FOPS | ||
2145 | select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE | ||
2146 | ---help--- | ||
2147 | Include support for the virtual frame buffer in the PS3 platform. | ||
2148 | |||
2149 | config FB_PS3_DEFAULT_SIZE_M | ||
2150 | int "PS3 default frame buffer size (in MiB)" | ||
2151 | depends on FB_PS3 | ||
2152 | default 9 | ||
2153 | ---help--- | ||
2154 | This is the default size (in MiB) of the virtual frame buffer in | ||
2155 | the PS3. | ||
2156 | The default value can be overridden on the kernel command line | ||
2157 | using the "ps3fb" option (e.g. "ps3fb=9M"); | ||
2158 | |||
2159 | config FB_XILINX | ||
2160 | tristate "Xilinx frame buffer support" | ||
2161 | depends on FB && (XILINX_VIRTEX || MICROBLAZE || ARCH_ZYNQ) | ||
2162 | select FB_CFB_FILLRECT | ||
2163 | select FB_CFB_COPYAREA | ||
2164 | select FB_CFB_IMAGEBLIT | ||
2165 | ---help--- | ||
2166 | Include support for the Xilinx ML300/ML403 reference design | ||
2167 | framebuffer. ML300 carries a 640*480 LCD display on the board, | ||
2168 | ML403 uses a standard DB15 VGA connector. | ||
2169 | |||
2170 | config FB_GOLDFISH | ||
2171 | tristate "Goldfish Framebuffer" | ||
2172 | depends on FB && HAS_DMA | ||
2173 | select FB_CFB_FILLRECT | ||
2174 | select FB_CFB_COPYAREA | ||
2175 | select FB_CFB_IMAGEBLIT | ||
2176 | ---help--- | ||
2177 | Framebuffer driver for Goldfish Virtual Platform | ||
2178 | |||
2179 | config FB_COBALT | ||
2180 | tristate "Cobalt server LCD frame buffer support" | ||
2181 | depends on FB && (MIPS_COBALT || MIPS_SEAD3) | ||
2182 | |||
2183 | config FB_SH7760 | ||
2184 | bool "SH7760/SH7763/SH7720/SH7721 LCDC support" | ||
2185 | depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \ | ||
2186 | || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721) | ||
2187 | select FB_CFB_FILLRECT | ||
2188 | select FB_CFB_COPYAREA | ||
2189 | select FB_CFB_IMAGEBLIT | ||
2190 | ---help--- | ||
2191 | Support for the SH7760/SH7763/SH7720/SH7721 integrated | ||
2192 | (D)STN/TFT LCD Controller. | ||
2193 | Supports display resolutions up to 1024x1024 pixel, grayscale and | ||
2194 | color operation, with depths ranging from 1 bpp to 8 bpp monochrome | ||
2195 | and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for | ||
2196 | panels <= 320 pixel horizontal resolution. | ||
2197 | |||
2198 | config FB_DA8XX | ||
2199 | tristate "DA8xx/OMAP-L1xx/AM335x Framebuffer support" | ||
2200 | depends on FB && (ARCH_DAVINCI_DA8XX || SOC_AM33XX) | ||
2201 | select FB_CFB_FILLRECT | ||
2202 | select FB_CFB_COPYAREA | ||
2203 | select FB_CFB_IMAGEBLIT | ||
2204 | select FB_CFB_REV_PIXELS_IN_BYTE | ||
2205 | select FB_MODE_HELPERS | ||
2206 | select VIDEOMODE_HELPERS | ||
2207 | ---help--- | ||
2208 | This is the frame buffer device driver for the TI LCD controller | ||
2209 | found on DA8xx/OMAP-L1xx/AM335x SoCs. | ||
2210 | If unsure, say N. | ||
2211 | |||
2212 | config FB_VIRTUAL | ||
2213 | tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)" | ||
2214 | depends on FB | ||
2215 | select FB_SYS_FILLRECT | ||
2216 | select FB_SYS_COPYAREA | ||
2217 | select FB_SYS_IMAGEBLIT | ||
2218 | select FB_SYS_FOPS | ||
2219 | ---help--- | ||
2220 | This is a `virtual' frame buffer device. It operates on a chunk of | ||
2221 | unswappable kernel memory instead of on the memory of a graphics | ||
2222 | board. This means you cannot see any output sent to this frame | ||
2223 | buffer device, while it does consume precious memory. The main use | ||
2224 | of this frame buffer device is testing and debugging the frame | ||
2225 | buffer subsystem. Do NOT enable it for normal systems! To protect | ||
2226 | the innocent, it has to be enabled explicitly at boot time using the | ||
2227 | kernel option `video=vfb:'. | ||
2228 | |||
2229 | To compile this driver as a module, choose M here: the | ||
2230 | module will be called vfb. In order to load it, you must use | ||
2231 | the vfb_enable=1 option. | ||
2232 | |||
2233 | If unsure, say N. | ||
2234 | |||
2235 | config XEN_FBDEV_FRONTEND | ||
2236 | tristate "Xen virtual frame buffer support" | ||
2237 | depends on FB && XEN | ||
2238 | select FB_SYS_FILLRECT | ||
2239 | select FB_SYS_COPYAREA | ||
2240 | select FB_SYS_IMAGEBLIT | ||
2241 | select FB_SYS_FOPS | ||
2242 | select FB_DEFERRED_IO | ||
2243 | select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC | ||
2244 | select XEN_XENBUS_FRONTEND | ||
2245 | default y | ||
2246 | help | ||
2247 | This driver implements the front-end of the Xen virtual | ||
2248 | frame buffer driver. It communicates with a back-end | ||
2249 | in another domain. | ||
2250 | |||
2251 | config FB_METRONOME | ||
2252 | tristate "E-Ink Metronome/8track controller support" | ||
2253 | depends on FB | ||
2254 | select FB_SYS_FILLRECT | ||
2255 | select FB_SYS_COPYAREA | ||
2256 | select FB_SYS_IMAGEBLIT | ||
2257 | select FB_SYS_FOPS | ||
2258 | select FB_DEFERRED_IO | ||
2259 | help | ||
2260 | This driver implements support for the E-Ink Metronome | ||
2261 | controller. The pre-release name for this device was 8track | ||
2262 | and could also have been called by some vendors as PVI-nnnn. | ||
2263 | |||
2264 | config FB_MB862XX | ||
2265 | tristate "Fujitsu MB862xx GDC support" | ||
2266 | depends on FB | ||
2267 | depends on PCI || (OF && PPC) | ||
2268 | select FB_CFB_FILLRECT | ||
2269 | select FB_CFB_COPYAREA | ||
2270 | select FB_CFB_IMAGEBLIT | ||
2271 | ---help--- | ||
2272 | Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers. | ||
2273 | |||
2274 | choice | ||
2275 | prompt "GDC variant" | ||
2276 | depends on FB_MB862XX | ||
2277 | |||
2278 | config FB_MB862XX_PCI_GDC | ||
2279 | bool "Carmine/Coral-P(A) GDC" | ||
2280 | depends on PCI | ||
2281 | ---help--- | ||
2282 | This enables framebuffer support for Fujitsu Carmine/Coral-P(A) | ||
2283 | PCI graphics controller devices. | ||
2284 | |||
2285 | config FB_MB862XX_LIME | ||
2286 | bool "Lime GDC" | ||
2287 | depends on OF && PPC | ||
2288 | select FB_FOREIGN_ENDIAN | ||
2289 | select FB_LITTLE_ENDIAN | ||
2290 | ---help--- | ||
2291 | Framebuffer support for Fujitsu Lime GDC on host CPU bus. | ||
2292 | |||
2293 | endchoice | ||
2294 | |||
2295 | config FB_MB862XX_I2C | ||
2296 | bool "Support I2C bus on MB862XX GDC" | ||
2297 | depends on FB_MB862XX && I2C | ||
2298 | default y | ||
2299 | help | ||
2300 | Selecting this option adds Coral-P(A)/Lime GDC I2C bus adapter | ||
2301 | driver to support accessing I2C devices on controller's I2C bus. | ||
2302 | These are usually some video decoder chips. | ||
2303 | |||
2304 | config FB_EP93XX | ||
2305 | tristate "EP93XX frame buffer support" | ||
2306 | depends on FB && ARCH_EP93XX | ||
2307 | select FB_CFB_FILLRECT | ||
2308 | select FB_CFB_COPYAREA | ||
2309 | select FB_CFB_IMAGEBLIT | ||
2310 | ---help--- | ||
2311 | Framebuffer driver for the Cirrus Logic EP93XX series of processors. | ||
2312 | This driver is also available as a module. The module will be called | ||
2313 | ep93xx-fb. | ||
2314 | |||
2315 | config FB_PRE_INIT_FB | ||
2316 | bool "Don't reinitialize, use bootloader's GDC/Display configuration" | ||
2317 | depends on FB && FB_MB862XX_LIME | ||
2318 | ---help--- | ||
2319 | Select this option if display contents should be inherited as set by | ||
2320 | the bootloader. | ||
2321 | |||
2322 | config FB_MSM | ||
2323 | tristate "MSM Framebuffer support" | ||
2324 | depends on FB && ARCH_MSM | ||
2325 | select FB_CFB_FILLRECT | ||
2326 | select FB_CFB_COPYAREA | ||
2327 | select FB_CFB_IMAGEBLIT | ||
2328 | |||
2329 | config FB_MX3 | ||
2330 | tristate "MX3 Framebuffer support" | ||
2331 | depends on FB && MX3_IPU | ||
2332 | select FB_CFB_FILLRECT | ||
2333 | select FB_CFB_COPYAREA | ||
2334 | select FB_CFB_IMAGEBLIT | ||
2335 | default y | ||
2336 | help | ||
2337 | This is a framebuffer device for the i.MX31 LCD Controller. So | ||
2338 | far only synchronous displays are supported. If you plan to use | ||
2339 | an LCD display with your i.MX31 system, say Y here. | ||
2340 | |||
2341 | config FB_BROADSHEET | ||
2342 | tristate "E-Ink Broadsheet/Epson S1D13521 controller support" | ||
2343 | depends on FB | ||
2344 | select FB_SYS_FILLRECT | ||
2345 | select FB_SYS_COPYAREA | ||
2346 | select FB_SYS_IMAGEBLIT | ||
2347 | select FB_SYS_FOPS | ||
2348 | select FB_DEFERRED_IO | ||
2349 | help | ||
2350 | This driver implements support for the E-Ink Broadsheet | ||
2351 | controller. The release name for this device was Epson S1D13521 | ||
2352 | and could also have been called by other names when coupled with | ||
2353 | a bridge adapter. | ||
2354 | |||
2355 | config FB_AUO_K190X | ||
2356 | tristate "AUO-K190X EPD controller support" | ||
2357 | depends on FB | ||
2358 | select FB_SYS_FILLRECT | ||
2359 | select FB_SYS_COPYAREA | ||
2360 | select FB_SYS_IMAGEBLIT | ||
2361 | select FB_SYS_FOPS | ||
2362 | select FB_DEFERRED_IO | ||
2363 | help | ||
2364 | Provides support for epaper controllers from the K190X series | ||
2365 | of AUO. These controllers can be used to drive epaper displays | ||
2366 | from Sipix. | ||
2367 | |||
2368 | This option enables the common support, shared by the individual | ||
2369 | controller drivers. You will also have to enable the driver | ||
2370 | for the controller type used in your device. | ||
2371 | |||
2372 | config FB_AUO_K1900 | ||
2373 | tristate "AUO-K1900 EPD controller support" | ||
2374 | depends on FB && FB_AUO_K190X | ||
2375 | help | ||
2376 | This driver implements support for the AUO K1900 epd-controller. | ||
2377 | This controller can drive Sipix epaper displays but can only do | ||
2378 | serial updates, reducing the number of possible frames per second. | ||
2379 | |||
2380 | config FB_AUO_K1901 | ||
2381 | tristate "AUO-K1901 EPD controller support" | ||
2382 | depends on FB && FB_AUO_K190X | ||
2383 | help | ||
2384 | This driver implements support for the AUO K1901 epd-controller. | ||
2385 | This controller can drive Sipix epaper displays and supports | ||
2386 | concurrent updates, making higher frames per second possible. | ||
2387 | |||
2388 | config FB_JZ4740 | ||
2389 | tristate "JZ4740 LCD framebuffer support" | ||
2390 | depends on FB && MACH_JZ4740 | ||
2391 | select FB_SYS_FILLRECT | ||
2392 | select FB_SYS_COPYAREA | ||
2393 | select FB_SYS_IMAGEBLIT | ||
2394 | help | ||
2395 | Framebuffer support for the JZ4740 SoC. | ||
2396 | |||
2397 | config FB_MXS | ||
2398 | tristate "MXS LCD framebuffer support" | ||
2399 | depends on FB && ARCH_MXS | ||
2400 | select FB_CFB_FILLRECT | ||
2401 | select FB_CFB_COPYAREA | ||
2402 | select FB_CFB_IMAGEBLIT | ||
2403 | select FB_MODE_HELPERS | ||
2404 | select VIDEOMODE_HELPERS | ||
2405 | help | ||
2406 | Framebuffer support for the MXS SoC. | ||
2407 | |||
2408 | config FB_PUV3_UNIGFX | ||
2409 | tristate "PKUnity v3 Unigfx framebuffer support" | ||
2410 | depends on FB && UNICORE32 && ARCH_PUV3 | ||
2411 | select FB_SYS_FILLRECT | ||
2412 | select FB_SYS_COPYAREA | ||
2413 | select FB_SYS_IMAGEBLIT | ||
2414 | select FB_SYS_FOPS | ||
2415 | help | ||
2416 | Choose this option if you want to use the Unigfx device as a | ||
2417 | framebuffer device. Without the support of PCI & AGP. | ||
2418 | |||
2419 | config FB_HYPERV | ||
2420 | tristate "Microsoft Hyper-V Synthetic Video support" | ||
2421 | depends on FB && HYPERV | ||
2422 | select FB_CFB_FILLRECT | ||
2423 | select FB_CFB_COPYAREA | ||
2424 | select FB_CFB_IMAGEBLIT | ||
2425 | help | ||
2426 | This framebuffer driver supports Microsoft Hyper-V Synthetic Video. | ||
2427 | |||
2428 | config FB_SIMPLE | ||
2429 | bool "Simple framebuffer support" | ||
2430 | depends on (FB = y) | ||
2431 | select FB_CFB_FILLRECT | ||
2432 | select FB_CFB_COPYAREA | ||
2433 | select FB_CFB_IMAGEBLIT | ||
2434 | help | ||
2435 | Say Y if you want support for a simple frame-buffer. | ||
2436 | |||
2437 | This driver assumes that the display hardware has been initialized | ||
2438 | before the kernel boots, and the kernel will simply render to the | ||
2439 | pre-allocated frame buffer surface. | ||
2440 | |||
2441 | Configuration re: surface address, size, and format must be provided | ||
2442 | through device tree, or plain old platform data. | ||
2443 | |||
2444 | source "drivers/video/fbdev/omap/Kconfig" | ||
2445 | source "drivers/video/fbdev/omap2/Kconfig" | ||
2446 | source "drivers/video/fbdev/exynos/Kconfig" | ||
2447 | source "drivers/video/fbdev/mmp/Kconfig" | ||
2448 | |||
2449 | config FB_SH_MOBILE_MERAM | ||
2450 | tristate "SuperH Mobile MERAM read ahead support" | ||
2451 | depends on (SUPERH || ARCH_SHMOBILE) | ||
2452 | select GENERIC_ALLOCATOR | ||
2453 | ---help--- | ||
2454 | Enable MERAM support for the SuperH controller. | ||
2455 | |||
2456 | This will allow for caching of the framebuffer to provide more | ||
2457 | reliable access under heavy main memory bus traffic situations. | ||
2458 | Up to 4 memory channels can be configured, allowing 4 RGB or | ||
2459 | 2 YCbCr framebuffers to be configured. | ||
2460 | |||
2461 | config FB_SSD1307 | ||
2462 | tristate "Solomon SSD1307 framebuffer support" | ||
2463 | depends on FB && I2C | ||
2464 | depends on OF | ||
2465 | depends on GPIOLIB | ||
2466 | select FB_SYS_FOPS | ||
2467 | select FB_SYS_FILLRECT | ||
2468 | select FB_SYS_COPYAREA | ||
2469 | select FB_SYS_IMAGEBLIT | ||
2470 | select FB_DEFERRED_IO | ||
2471 | select PWM | ||
2472 | help | ||
2473 | This driver implements support for the Solomon SSD1307 | ||
2474 | OLED controller over I2C. | ||