]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # $Id: config.in,v 1.158 2002/01/24 22:14:44 davem Exp $ |
2 | # For a description of the syntax of this configuration file, | |
3 | # see the Configure script. | |
4 | # | |
5 | ||
6 | mainmenu "Linux/UltraSPARC Kernel Configuration" | |
7 | ||
8 | config 64BIT | |
9 | def_bool y | |
10 | ||
11 | config MMU | |
12 | bool | |
13 | default y | |
14 | ||
15 | config TIME_INTERPOLATION | |
16 | bool | |
17 | default y | |
18 | ||
19 | choice | |
20 | prompt "Kernel page size" | |
21 | default SPARC64_PAGE_SIZE_8KB | |
22 | ||
23 | config SPARC64_PAGE_SIZE_8KB | |
24 | bool "8KB" | |
25 | help | |
26 | This lets you select the page size of the kernel. | |
27 | ||
28 | 8KB and 64KB work quite well, since Sparc ELF sections | |
29 | provide for up to 64KB alignment. | |
30 | ||
31 | Therefore, 512KB and 4MB are for expert hackers only. | |
32 | ||
33 | If you don't know what to do, choose 8KB. | |
34 | ||
35 | config SPARC64_PAGE_SIZE_64KB | |
36 | bool "64KB" | |
37 | ||
38 | config SPARC64_PAGE_SIZE_512KB | |
39 | bool "512KB" | |
40 | ||
41 | config SPARC64_PAGE_SIZE_4MB | |
42 | bool "4MB" | |
43 | ||
44 | endchoice | |
45 | ||
a6524813 DM |
46 | source kernel/Kconfig.hz |
47 | ||
1da177e4 LT |
48 | source "init/Kconfig" |
49 | ||
50 | config SYSVIPC_COMPAT | |
51 | bool | |
52 | depends on COMPAT && SYSVIPC | |
53 | default y | |
54 | ||
55 | menu "General machine setup" | |
56 | ||
57 | config BBC_I2C | |
58 | tristate "UltraSPARC-III bootbus i2c controller driver" | |
59 | depends on PCI | |
60 | help | |
61 | The BBC devices on the UltraSPARC III have two I2C controllers. The | |
62 | first I2C controller connects mainly to configuration PROMs (NVRAM, | |
63 | CPU configuration, DIMM types, etc.). The second I2C controller | |
64 | connects to environmental control devices such as fans and | |
65 | temperature sensors. The second controller also connects to the | |
66 | smartcard reader, if present. Say Y to enable support for these. | |
67 | ||
68 | config VT | |
69 | bool "Virtual terminal" if EMBEDDED | |
70 | select INPUT | |
71 | default y | |
72 | ---help--- | |
73 | If you say Y here, you will get support for terminal devices with | |
74 | display and keyboard devices. These are called "virtual" because you | |
75 | can run several virtual terminals (also called virtual consoles) on | |
76 | one physical terminal. This is rather useful, for example one | |
77 | virtual terminal can collect system messages and warnings, another | |
78 | one can be used for a text-mode user session, and a third could run | |
79 | an X session, all in parallel. Switching between virtual terminals | |
80 | is done with certain key combinations, usually Alt-<function key>. | |
81 | ||
82 | The setterm command ("man setterm") can be used to change the | |
83 | properties (such as colors or beeping) of a virtual terminal. The | |
84 | man page console_codes(4) ("man console_codes") contains the special | |
85 | character sequences that can be used to change those properties | |
86 | directly. The fonts used on virtual terminals can be changed with | |
87 | the setfont ("man setfont") command and the key bindings are defined | |
88 | with the loadkeys ("man loadkeys") command. | |
89 | ||
90 | You need at least one virtual terminal device in order to make use | |
91 | of your keyboard and monitor. Therefore, only people configuring an | |
92 | embedded system would want to say N here in order to save some | |
93 | memory; the only way to log into such a system is then via a serial | |
94 | or network connection. | |
95 | ||
96 | If unsure, say Y, or else you won't be able to do much with your new | |
97 | shiny Linux system :-) | |
98 | ||
99 | config VT_CONSOLE | |
100 | bool "Support for console on virtual terminal" if EMBEDDED | |
101 | depends on VT | |
102 | default y | |
103 | ---help--- | |
104 | The system console is the device which receives all kernel messages | |
105 | and warnings and which allows logins in single user mode. If you | |
106 | answer Y here, a virtual terminal (the device used to interact with | |
107 | a physical terminal) can be used as system console. This is the most | |
108 | common mode of operations, so you should say Y here unless you want | |
109 | the kernel messages be output only to a serial port (in which case | |
110 | you should say Y to "Console on serial port", below). | |
111 | ||
112 | If you do say Y here, by default the currently visible virtual | |
113 | terminal (/dev/tty0) will be used as system console. You can change | |
114 | that with a kernel command line option such as "console=tty3" which | |
115 | would use the third virtual terminal as system console. (Try "man | |
116 | bootparam" or see the documentation of your boot loader (lilo or | |
117 | loadlin) about how to pass options to the kernel at boot time.) | |
118 | ||
119 | If unsure, say Y. | |
120 | ||
121 | config HW_CONSOLE | |
122 | bool | |
e3b9ab1a | 123 | depends on VT |
1da177e4 LT |
124 | default y |
125 | ||
126 | config SMP | |
127 | bool "Symmetric multi-processing support" | |
128 | ---help--- | |
129 | This enables support for systems with more than one CPU. If you have | |
130 | a system with only one CPU, say N. If you have a system with more than | |
131 | one CPU, say Y. | |
132 | ||
133 | If you say N here, the kernel will run on single and multiprocessor | |
134 | machines, but will use only one CPU of a multiprocessor machine. If | |
135 | you say Y here, the kernel will run on many, but not all, | |
136 | singleprocessor machines. On a singleprocessor machine, the kernel | |
137 | will run faster if you say N here. | |
138 | ||
139 | People using multiprocessor machines who say Y here should also say | |
140 | Y to "Enhanced Real Time Clock Support", below. The "Advanced Power | |
141 | Management" code will be disabled if you say Y here. | |
142 | ||
143 | See also the <file:Documentation/smp.txt>, | |
144 | <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at | |
145 | <http://www.tldp.org/docs.html#howto>. | |
146 | ||
147 | If you don't know what to do here, say N. | |
148 | ||
149 | config PREEMPT | |
150 | bool "Preemptible Kernel" | |
151 | help | |
152 | This option reduces the latency of the kernel when reacting to | |
153 | real-time or interactive events by allowing a low priority process to | |
154 | be preempted even if it is in kernel mode executing a system call. | |
155 | This allows applications to run more reliably even when the system is | |
156 | under load. | |
157 | ||
158 | Say Y here if you are building a kernel for a desktop, embedded | |
159 | or real-time system. Say N if you are unsure. | |
160 | ||
161 | config NR_CPUS | |
162 | int "Maximum number of CPUs (2-64)" | |
163 | range 2 64 | |
164 | depends on SMP | |
165 | default "32" | |
166 | ||
167 | source "drivers/cpufreq/Kconfig" | |
168 | ||
169 | config US3_FREQ | |
170 | tristate "UltraSPARC-III CPU Frequency driver" | |
171 | depends on CPU_FREQ | |
172 | select CPU_FREQ_TABLE | |
173 | help | |
174 | This adds the CPUFreq driver for UltraSPARC-III processors. | |
175 | ||
176 | For details, take a look at <file:Documentation/cpu-freq>. | |
177 | ||
178 | If in doubt, say N. | |
179 | ||
180 | config US2E_FREQ | |
181 | tristate "UltraSPARC-IIe CPU Frequency driver" | |
182 | depends on CPU_FREQ | |
183 | select CPU_FREQ_TABLE | |
184 | help | |
185 | This adds the CPUFreq driver for UltraSPARC-IIe processors. | |
186 | ||
187 | For details, take a look at <file:Documentation/cpu-freq>. | |
188 | ||
189 | If in doubt, say N. | |
190 | ||
191 | # Identify this as a Sparc64 build | |
192 | config SPARC64 | |
193 | bool | |
194 | default y | |
195 | help | |
196 | SPARC is a family of RISC microprocessors designed and marketed by | |
197 | Sun Microsystems, incorporated. This port covers the newer 64-bit | |
198 | UltraSPARC. The UltraLinux project maintains both the SPARC32 and | |
199 | SPARC64 ports; its web page is available at | |
200 | <http://www.ultralinux.org/>. | |
201 | ||
202 | # Global things across all Sun machines. | |
203 | config RWSEM_GENERIC_SPINLOCK | |
204 | bool | |
205 | ||
206 | config RWSEM_XCHGADD_ALGORITHM | |
207 | bool | |
208 | default y | |
209 | ||
210 | config GENERIC_CALIBRATE_DELAY | |
211 | bool | |
212 | default y | |
213 | ||
214 | choice | |
215 | prompt "SPARC64 Huge TLB Page Size" | |
216 | depends on HUGETLB_PAGE | |
217 | default HUGETLB_PAGE_SIZE_4MB | |
218 | ||
219 | config HUGETLB_PAGE_SIZE_4MB | |
220 | bool "4MB" | |
221 | ||
222 | config HUGETLB_PAGE_SIZE_512K | |
223 | depends on !SPARC64_PAGE_SIZE_4MB | |
224 | bool "512K" | |
225 | ||
226 | config HUGETLB_PAGE_SIZE_64K | |
227 | depends on !SPARC64_PAGE_SIZE_4MB && !SPARC64_PAGE_SIZE_512K | |
228 | bool "64K" | |
229 | ||
230 | endchoice | |
231 | ||
232 | config GENERIC_ISA_DMA | |
233 | bool | |
234 | default y | |
235 | ||
236 | config ISA | |
237 | bool | |
238 | help | |
239 | Find out whether you have ISA slots on your motherboard. ISA is the | |
240 | name of a bus system, i.e. the way the CPU talks to the other stuff | |
241 | inside your box. Other bus systems are PCI, EISA, MicroChannel | |
242 | (MCA) or VESA. ISA is an older system, now being displaced by PCI; | |
243 | newer boards don't support it. If you have ISA, say Y, otherwise N. | |
244 | ||
245 | config ISAPNP | |
246 | bool | |
247 | help | |
248 | Say Y here if you would like support for ISA Plug and Play devices. | |
249 | Some information is in <file:Documentation/isapnp.txt>. | |
250 | ||
251 | To compile this driver as a module, choose M here: the | |
252 | module will be called isapnp. | |
253 | ||
254 | If unsure, say Y. | |
255 | ||
256 | config EISA | |
257 | bool | |
258 | ---help--- | |
259 | The Extended Industry Standard Architecture (EISA) bus was | |
260 | developed as an open alternative to the IBM MicroChannel bus. | |
261 | ||
262 | The EISA bus provided some of the features of the IBM MicroChannel | |
263 | bus while maintaining backward compatibility with cards made for | |
264 | the older ISA bus. The EISA bus saw limited use between 1988 and | |
265 | 1995 when it was made obsolete by the PCI bus. | |
266 | ||
267 | Say Y here if you are building a kernel for an EISA-based machine. | |
268 | ||
269 | Otherwise, say N. | |
270 | ||
271 | config MCA | |
272 | bool | |
273 | help | |
274 | MicroChannel Architecture is found in some IBM PS/2 machines and | |
275 | laptops. It is a bus system similar to PCI or ISA. See | |
276 | <file:Documentation/mca.txt> (and especially the web page given | |
277 | there) before attempting to build an MCA bus kernel. | |
278 | ||
279 | config PCMCIA | |
280 | tristate | |
281 | ---help--- | |
282 | Say Y here if you want to attach PCMCIA- or PC-cards to your Linux | |
283 | computer. These are credit-card size devices such as network cards, | |
284 | modems or hard drives often used with laptops computers. There are | |
285 | actually two varieties of these cards: the older 16 bit PCMCIA cards | |
286 | and the newer 32 bit CardBus cards. If you want to use CardBus | |
287 | cards, you need to say Y here and also to "CardBus support" below. | |
288 | ||
289 | To use your PC-cards, you will need supporting software from David | |
290 | Hinds' pcmcia-cs package (see the file <file:Documentation/Changes> | |
291 | for location). Please also read the PCMCIA-HOWTO, available from | |
292 | <http://www.tldp.org/docs.html#howto>. | |
293 | ||
294 | To compile this driver as modules, choose M here: the | |
295 | modules will be called pcmcia_core and ds. | |
296 | ||
297 | config SBUS | |
298 | bool | |
299 | default y | |
300 | ||
301 | config SBUSCHAR | |
302 | bool | |
303 | default y | |
304 | ||
305 | config SUN_AUXIO | |
306 | bool | |
307 | default y | |
308 | ||
309 | config SUN_IO | |
310 | bool | |
311 | default y | |
312 | ||
313 | config PCI | |
314 | bool "PCI support" | |
315 | help | |
316 | Find out whether you have a PCI motherboard. PCI is the name of a | |
317 | bus system, i.e. the way the CPU talks to the other stuff inside | |
318 | your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or | |
319 | VESA. If you have PCI, say Y, otherwise N. | |
320 | ||
321 | The PCI-HOWTO, available from | |
322 | <http://www.tldp.org/docs.html#howto>, contains valuable | |
323 | information about which PCI hardware does work under Linux and which | |
324 | doesn't. | |
325 | ||
326 | config PCI_DOMAINS | |
327 | bool | |
328 | default PCI | |
329 | ||
330 | config RTC | |
331 | tristate | |
332 | depends on PCI | |
333 | default y | |
334 | ---help--- | |
335 | If you say Y here and create a character special file /dev/rtc with | |
336 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
337 | will get access to the real time clock (or hardware clock) built | |
338 | into your computer. | |
339 | ||
340 | Every PC has such a clock built in. It can be used to generate | |
341 | signals from as low as 1Hz up to 8192Hz, and can also be used | |
342 | as a 24 hour alarm. It reports status information via the file | |
343 | /proc/driver/rtc and its behaviour is set by various ioctls on | |
344 | /dev/rtc. | |
345 | ||
346 | If you run Linux on a multiprocessor machine and said Y to | |
347 | "Symmetric Multi Processing" above, you should say Y here to read | |
348 | and set the RTC in an SMP compatible fashion. | |
349 | ||
350 | If you think you have a use for such a device (such as periodic data | |
351 | sampling), then say Y here, and read <file:Documentation/rtc.txt> | |
352 | for details. | |
353 | ||
354 | To compile this driver as a module, choose M here: the | |
355 | module will be called rtc. | |
356 | ||
357 | source "drivers/pci/Kconfig" | |
358 | ||
359 | config SUN_OPENPROMFS | |
360 | tristate "Openprom tree appears in /proc/openprom" | |
361 | help | |
362 | If you say Y, the OpenPROM device tree will be available as a | |
363 | virtual file system, which you can mount to /proc/openprom by "mount | |
364 | -t openpromfs none /proc/openprom". | |
365 | ||
366 | To compile the /proc/openprom support as a module, choose M here: the | |
367 | module will be called openpromfs. If unsure, choose M. | |
368 | ||
369 | config SPARC32_COMPAT | |
370 | bool "Kernel support for Linux/Sparc 32bit binary compatibility" | |
371 | help | |
372 | This allows you to run 32-bit binaries on your Ultra. | |
373 | Everybody wants this; say Y. | |
374 | ||
375 | config COMPAT | |
376 | bool | |
377 | depends on SPARC32_COMPAT | |
378 | default y | |
379 | ||
380 | config UID16 | |
381 | bool | |
382 | depends on SPARC32_COMPAT | |
383 | default y | |
384 | ||
385 | config BINFMT_ELF32 | |
386 | tristate "Kernel support for 32-bit ELF binaries" | |
387 | depends on SPARC32_COMPAT | |
388 | help | |
389 | This allows you to run 32-bit Linux/ELF binaries on your Ultra. | |
390 | Everybody wants this; say Y. | |
391 | ||
392 | config BINFMT_AOUT32 | |
393 | bool "Kernel support for 32-bit (ie. SunOS) a.out binaries" | |
394 | depends on SPARC32_COMPAT | |
395 | help | |
396 | This allows you to run 32-bit a.out format binaries on your Ultra. | |
397 | If you want to run SunOS binaries (see SunOS binary emulation below) | |
398 | or other a.out binaries, say Y. If unsure, say N. | |
399 | ||
400 | source "fs/Kconfig.binfmt" | |
401 | ||
402 | config SUNOS_EMUL | |
403 | bool "SunOS binary emulation" | |
404 | depends on BINFMT_AOUT32 | |
405 | help | |
406 | This allows you to run most SunOS binaries. If you want to do this, | |
407 | say Y here and place appropriate files in /usr/gnemul/sunos. See | |
408 | <http://www.ultralinux.org/faq.html> for more information. If you | |
409 | want to run SunOS binaries on an Ultra you must also say Y to | |
410 | "Kernel support for 32-bit a.out binaries" above. | |
411 | ||
412 | config SOLARIS_EMUL | |
413 | tristate "Solaris binary emulation (EXPERIMENTAL)" | |
414 | depends on SPARC32_COMPAT && EXPERIMENTAL | |
415 | help | |
416 | This is experimental code which will enable you to run (many) | |
417 | Solaris binaries on your SPARC Linux machine. | |
418 | ||
419 | To compile this code as a module, choose M here: the | |
420 | module will be called solaris. | |
421 | ||
422 | source "drivers/parport/Kconfig" | |
423 | ||
424 | config PRINTER | |
425 | tristate "Parallel printer support" | |
426 | depends on PARPORT | |
427 | ---help--- | |
428 | If you intend to attach a printer to the parallel port of your Linux | |
429 | box (as opposed to using a serial printer; if the connector at the | |
430 | printer has 9 or 25 holes ["female"], then it's serial), say Y. | |
431 | Also read the Printing-HOWTO, available from | |
432 | <http://www.tldp.org/docs.html#howto>. | |
433 | ||
434 | It is possible to share one parallel port among several devices | |
435 | (e.g. printer and ZIP drive) and it is safe to compile the | |
436 | corresponding drivers into the kernel. | |
437 | To compile this driver as a module, choose M here and read | |
438 | <file:Documentation/parport.txt>. The module will be called lp. | |
439 | ||
440 | If you have several parallel ports, you can specify which ports to | |
441 | use with the "lp" kernel command line option. (Try "man bootparam" | |
442 | or see the documentation of your boot loader (lilo or loadlin) about | |
443 | how to pass options to the kernel at boot time.) The syntax of the | |
444 | "lp" command line option can be found in <file:drivers/char/lp.c>. | |
445 | ||
446 | If you have more than 8 printers, you need to increase the LP_NO | |
447 | macro in lp.c and the PARPORT_MAX macro in parport.h. | |
448 | ||
e7270dec RA |
449 | config PPDEV |
450 | tristate "Support for user-space parallel port device drivers" | |
451 | depends on PARPORT | |
452 | ---help--- | |
453 | Saying Y to this adds support for /dev/parport device nodes. This | |
454 | is needed for programs that want portable access to the parallel | |
455 | port, for instance deviceid (which displays Plug-and-Play device | |
456 | IDs). | |
457 | ||
458 | This is the parallel port equivalent of SCSI generic support (sg). | |
459 | It is safe to say N to this -- it is not needed for normal printing | |
460 | or parallel port CD-ROM/disk support. | |
461 | ||
462 | To compile this driver as a module, choose M here: the | |
463 | module will be called ppdev. | |
464 | ||
465 | If unsure, say N. | |
466 | ||
1da177e4 LT |
467 | config ENVCTRL |
468 | tristate "SUNW, envctrl support" | |
469 | depends on PCI | |
470 | help | |
471 | Kernel support for temperature and fan monitoring on Sun SME | |
472 | machines. | |
473 | ||
474 | To compile this driver as a module, choose M here: the | |
475 | module will be called envctrl. | |
476 | ||
477 | config DISPLAY7SEG | |
478 | tristate "7-Segment Display support" | |
479 | depends on PCI | |
480 | ---help--- | |
481 | This is the driver for the 7-segment display and LED present on | |
482 | Sun Microsystems CompactPCI models CP1400 and CP1500. | |
483 | ||
484 | To compile this driver as a module, choose M here: the | |
485 | module will be called display7seg. | |
486 | ||
487 | If you do not have a CompactPCI model CP1400 or CP1500, or | |
488 | another UltraSPARC-IIi-cEngine boardset with a 7-segment display, | |
489 | you should say N to this option. | |
490 | ||
491 | config CMDLINE_BOOL | |
492 | bool "Default bootloader kernel arguments" | |
493 | ||
494 | config CMDLINE | |
495 | string "Initial kernel command string" | |
496 | depends on CMDLINE_BOOL | |
497 | default "console=ttyS0,9600 root=/dev/sda1" | |
498 | help | |
499 | Say Y here if you want to be able to pass default arguments to | |
500 | the kernel. This will be overridden by the bootloader, if you | |
501 | use one (such as SILO). This is most useful if you want to boot | |
502 | a kernel from TFTP, and want default options to be available | |
503 | with having them passed on the command line. | |
504 | ||
505 | NOTE: This option WILL override the PROM bootargs setting! | |
506 | ||
3f22ab27 DH |
507 | source "mm/Kconfig" |
508 | ||
1da177e4 LT |
509 | endmenu |
510 | ||
511 | source "drivers/base/Kconfig" | |
512 | ||
513 | source "drivers/video/Kconfig" | |
514 | ||
515 | source "drivers/serial/Kconfig" | |
516 | ||
517 | source "drivers/sbus/char/Kconfig" | |
518 | ||
519 | source "drivers/mtd/Kconfig" | |
520 | ||
521 | source "drivers/block/Kconfig" | |
522 | ||
523 | source "drivers/ide/Kconfig" | |
524 | ||
525 | source "drivers/scsi/Kconfig" | |
526 | ||
527 | source "drivers/fc4/Kconfig" | |
528 | ||
529 | source "drivers/md/Kconfig" | |
530 | ||
531 | if PCI | |
532 | source "drivers/message/fusion/Kconfig" | |
533 | endif | |
534 | ||
535 | source "drivers/ieee1394/Kconfig" | |
536 | ||
537 | source "net/Kconfig" | |
538 | ||
539 | source "drivers/isdn/Kconfig" | |
540 | ||
541 | source "drivers/telephony/Kconfig" | |
542 | ||
543 | # This one must be before the filesystem configs. -DaveM | |
544 | ||
545 | menu "Unix98 PTY support" | |
546 | ||
547 | config UNIX98_PTYS | |
548 | bool "Unix98 PTY support" | |
549 | ---help--- | |
550 | A pseudo terminal (PTY) is a software device consisting of two | |
551 | halves: a master and a slave. The slave device behaves identical to | |
552 | a physical terminal; the master device is used by a process to | |
553 | read data from and write data to the slave, thereby emulating a | |
554 | terminal. Typical programs for the master side are telnet servers | |
555 | and xterms. | |
556 | ||
557 | Linux has traditionally used the BSD-like names /dev/ptyxx for | |
558 | masters and /dev/ttyxx for slaves of pseudo terminals. This scheme | |
559 | has a number of problems. The GNU C library glibc 2.1 and later, | |
560 | however, supports the Unix98 naming standard: in order to acquire a | |
561 | pseudo terminal, a process opens /dev/ptmx; the number of the pseudo | |
562 | terminal is then made available to the process and the pseudo | |
563 | terminal slave can be accessed as /dev/pts/<number>. What was | |
564 | traditionally /dev/ttyp2 will then be /dev/pts/2, for example. | |
565 | ||
566 | The entries in /dev/pts/ are created on the fly by a virtual | |
567 | file system; therefore, if you say Y here you should say Y to | |
568 | "/dev/pts file system for Unix98 PTYs" as well. | |
569 | ||
570 | If you want to say Y here, you need to have the C library glibc 2.1 | |
571 | or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*"). | |
572 | Read the instructions in <file:Documentation/Changes> pertaining to | |
573 | pseudo terminals. It's safe to say N. | |
574 | ||
575 | config UNIX98_PTY_COUNT | |
576 | int "Maximum number of Unix98 PTYs in use (0-2048)" | |
577 | depends on UNIX98_PTYS | |
578 | default "256" | |
579 | help | |
580 | The maximum number of Unix98 PTYs that can be used at any one time. | |
581 | The default is 256, and should be enough for desktop systems. Server | |
582 | machines which support incoming telnet/rlogin/ssh connections and/or | |
583 | serve several X terminals may want to increase this: every incoming | |
584 | connection and every xterm uses up one PTY. | |
585 | ||
586 | When not in use, each additional set of 256 PTYs occupy | |
587 | approximately 8 KB of kernel memory on 32-bit architectures. | |
588 | ||
589 | endmenu | |
590 | ||
591 | menu "XFree86 DRI support" | |
592 | ||
593 | config DRM | |
594 | bool "Direct Rendering Manager (XFree86 DRI support)" | |
595 | help | |
596 | Kernel-level support for the Direct Rendering Infrastructure (DRI) | |
597 | introduced in XFree86 4.0. If you say Y here, you need to select | |
598 | the module that's right for your graphics card from the list below. | |
599 | These modules provide support for synchronization, security, and | |
600 | DMA transfers. Please see <http://dri.sourceforge.net/> for more | |
601 | details. You should also select and configure AGP | |
602 | (/dev/agpgart) support. | |
603 | ||
604 | config DRM_FFB | |
605 | tristate "Creator/Creator3D" | |
606 | depends on DRM && BROKEN | |
607 | help | |
608 | Choose this option if you have one of Sun's Creator3D-based graphics | |
609 | and frame buffer cards. Product page at | |
610 | <http://www.sun.com/desktop/products/Graphics/creator3d.html>. | |
611 | ||
612 | config DRM_TDFX | |
613 | tristate "3dfx Banshee/Voodoo3+" | |
614 | depends on DRM | |
615 | help | |
616 | Choose this option if you have a 3dfx Banshee or Voodoo3 (or later), | |
617 | graphics card. If M is selected, the module will be called tdfx. | |
618 | ||
619 | config DRM_R128 | |
620 | tristate "ATI Rage 128" | |
621 | depends on DRM | |
622 | help | |
623 | Choose this option if you have an ATI Rage 128 graphics card. If M | |
624 | is selected, the module will be called r128. AGP support for | |
625 | this card is strongly suggested (unless you have a PCI version). | |
626 | ||
627 | endmenu | |
628 | ||
629 | source "drivers/input/Kconfig" | |
630 | ||
631 | source "drivers/i2c/Kconfig" | |
632 | ||
633 | source "fs/Kconfig" | |
634 | ||
635 | source "drivers/media/Kconfig" | |
636 | ||
637 | source "sound/Kconfig" | |
638 | ||
639 | source "drivers/usb/Kconfig" | |
640 | ||
641 | source "drivers/infiniband/Kconfig" | |
642 | ||
643 | source "drivers/char/watchdog/Kconfig" | |
644 | ||
645 | source "arch/sparc64/oprofile/Kconfig" | |
646 | ||
647 | source "arch/sparc64/Kconfig.debug" | |
648 | ||
649 | source "security/Kconfig" | |
650 | ||
651 | source "crypto/Kconfig" | |
652 | ||
653 | source "lib/Kconfig" |