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