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