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