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