2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
17 config RWSEM_GENERIC_SPINLOCK
21 config RWSEM_XCHGADD_ALGORITHM
25 mainmenu "Linux/68k Kernel Configuration"
30 menu "Platform dependent setup"
35 The Extended Industry Standard Architecture (EISA) bus was
36 developed as an open alternative to the IBM MicroChannel bus.
38 The EISA bus provided some of the features of the IBM MicroChannel
39 bus while maintaining backward compatibility with cards made for
40 the older ISA bus. The EISA bus saw limited use between 1988 and
41 1995 when it was made obsolete by the PCI bus.
43 Say Y here if you are building a kernel for an EISA-based machine.
50 MicroChannel Architecture is found in some IBM PS/2 machines and
51 laptops. It is a bus system similar to PCI or ISA. See
52 <file:Documentation/mca.txt> (and especially the web page given
53 there) before attempting to build an MCA bus kernel.
58 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
59 computer. These are credit-card size devices such as network cards,
60 modems or hard drives often used with laptops computers. There are
61 actually two varieties of these cards: the older 16 bit PCMCIA cards
62 and the newer 32 bit CardBus cards. If you want to use CardBus
63 cards, you need to say Y here and also to "CardBus support" below.
65 To use your PC-cards, you will need supporting software from David
66 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
67 for location). Please also read the PCMCIA-HOWTO, available from
68 <http://www.tldp.org/docs.html#howto>.
70 This driver is also available as a module ( = code which can be
71 inserted in and removed from the running kernel whenever you want).
72 When compiled this way, there will be modules called pcmcia_core
73 and ds. If you want to compile it as a module, say M here and
74 read <file:Documentation/modules.txt>.
79 This option enables support for the Amiga series of computers. If
80 you plan to use this kernel on an Amiga, say Y here and browse the
81 material available in <file:Documentation/m68k>; otherwise say N.
86 This option enables support for the 68000-based Atari series of
87 computers (including the TT, Falcon and Medusa). If you plan to use
88 this kernel on an Atari, say Y here and browse the material
89 available in <file:Documentation/m68k>; otherwise say N.
95 This option enables support for the Hades Atari clone. If you plan
96 to use this kernel on a Hades, say Y here; otherwise say N.
103 Find out whether you have a PCI motherboard. PCI is the name of a
104 bus system, i.e. the way the CPU talks to the other stuff inside
105 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
106 VESA. If you have PCI, say Y, otherwise N.
108 The PCI-HOWTO, available from
109 <http://www.tldp.org/docs.html#howto>, contains valuable
110 information about which PCI hardware does work under Linux and which
114 bool "Macintosh support"
116 This option enables support for the Apple Macintosh series of
117 computers (yes, there is experimental support now, at least for part
120 Say N unless you're willing to code the remaining necessary support.
134 bool "Apollo support"
136 Say Y here if you want to run Linux on an MC680x0-based Apollo
137 Domain workstation such as the DN3500.
140 bool "VME (Motorola and BVM) support"
142 Say Y here if you want to build a kernel for a 680x0 based VME
143 board. Boards currently supported include Motorola boards MVME147,
144 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
145 BVME6000 boards from BVM Ltd are also supported.
148 bool "MVME147 support"
151 Say Y to include support for early Motorola VME boards. This will
152 build a kernel which can run on MVME147 single-board computers. If
153 you select this option you will have to select the appropriate
154 drivers for SCSI, Ethernet and serial ports later on.
157 bool "MVME162, 166 and 167 support"
160 Say Y to include support for Motorola VME boards. This will build a
161 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
162 MVME177 boards. If you select this option you will have to select
163 the appropriate drivers for SCSI, Ethernet and serial ports later
167 bool "BVME4000 and BVME6000 support"
170 Say Y to include support for VME boards from BVM Ltd. This will
171 build a kernel which can run on BVME4000 and BVME6000 boards. If
172 you select this option you will have to select the appropriate
173 drivers for SCSI, Ethernet and serial ports later on.
176 bool "HP9000/300 support"
178 This option enables support for the HP9000/300 series of
179 workstations. Support for these machines is still very experimental.
180 If you plan to try to use the kernel on such a machine say Y here.
181 Everybody else says N.
184 bool "DIO bus support"
187 Say Y here to enable support for the "DIO" expansion bus used in
188 HP300 machines. If you are using such a system you almost certainly
194 This option enables support for the Sun 3x series of workstations.
195 Be warned that this support is very experimental. You will also want
196 to say Y to 68030 support and N to the other processors below.
197 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
198 General Linux information on the Sun 3x series (now discontinued)
199 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
201 If you don't want to compile a kernel for a Sun 3x, say N.
206 This option enables support for the Sun 3 series of workstations
207 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
208 that all other hardware types must be disabled, as Sun 3 kernels
209 are incompatible with all other m68k targets (including Sun 3x!).
210 Also, you will want to say Y to 68020 support and N to the other
213 If you don't want to compile a kernel exclusively for a Sun 3, say N.
216 bool "Q40/Q60 support"
218 The Q40 is a Motorola 68040-based successor to the Sinclair QL
219 manufactured in Germany. There is an official Q40 home page at
220 <http://www.q40.de/>. This option enables support for the Q40 and
221 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
224 comment "Processor type"
229 If you anticipate running this kernel on a computer with a MC68020
230 processor, say Y. Otherwise, say N. Note that the 68020 requires a
231 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
232 Sun 3, which provides its own version.
237 If you anticipate running this kernel on a computer with a MC68030
238 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
239 work, as it does not include an MMU (Memory Management Unit).
244 If you anticipate running this kernel on a computer with a MC68LC040
245 or MC68040 processor, say Y. Otherwise, say N. Note that an
246 MC68EC040 will not work, as it does not include an MMU (Memory
252 If you anticipate running this kernel on a computer with a MC68060
253 processor, say Y. Otherwise, say N.
256 bool "Math emulation support (EXPERIMENTAL)"
257 depends on EXPERIMENTAL
259 At some point in the future, this will cause floating-point math
260 instructions to be emulated by the kernel on machines that lack a
261 floating-point math coprocessor. Thrill-seekers and chronically
262 sleep-deprived psychotic hacker types can say Y now, everyone else
263 should probably wait a while.
265 config M68KFPU_EMU_EXTRAPREC
266 bool "Math emulation extra precision"
267 depends on M68KFPU_EMU
269 The fpu uses normally a few bit more during calculations for
270 correct rounding, the emulator can (often) do the same but this
271 extra calculation can cost quite some time, so you can disable
272 it here. The emulator will then "only" calculate with a 64 bit
273 mantissa and round slightly incorrect, what is more then enough
276 config M68KFPU_EMU_ONLY
277 bool "Math emulation only kernel"
278 depends on M68KFPU_EMU
280 This option prevents any floating-point instructions from being
281 compiled into the kernel, thereby the kernel doesn't save any
282 floating point context anymore during task switches, so this
283 kernel will only be usable on machines without a floating-point
284 math coprocessor. This makes the kernel a bit faster as no tests
285 needs to be executed whether a floating-point instruction in the
286 kernel should be executed or not.
289 bool "Advanced configuration options"
291 This gives you access to some advanced options for the CPU. The
292 defaults should be fine for most users, but these options may make
293 it possible for you to improve performance somewhat if you know what
296 Note that the answer to this question won't directly affect the
297 kernel: saying N will just cause the configurator to skip all
298 the questions about these options.
300 Most users should say N to this question.
303 bool "Use read-modify-write instructions"
306 This allows to use certain instructions that work with indivisible
307 read-modify-write bus cycles. While this is faster than the
308 workaround of disabling interrupts, it can conflict with DMA
309 ( = direct memory access) on many Amiga systems, and it is also said
310 to destabilize other machines. It is very likely that this will
311 cause serious problems on any Amiga or Atari Medusa if set. The only
312 configuration where it should work are 68030-based Ataris, where it
313 apparently improves performance. But you've been warned! Unless you
314 really know what you are doing, say N. Try Y only if you're quite
317 config SINGLE_MEMORY_CHUNK
318 bool "Use one physical chunk of memory only"
319 depends on ADVANCED && !SUN3
321 Ignore all but the first contiguous chunk of physical memory for VM
322 purposes. This will save a few bytes kernel size and may speed up
323 some operations. Say N if not sure.
325 config 060_WRITETHROUGH
326 bool "Use write-through caching for 68060 supervisor accesses"
327 depends on ADVANCED && M68060
329 The 68060 generally uses copyback caching of recently accessed data.
330 Copyback caching means that memory writes will be held in an on-chip
331 cache and only written back to memory some time later. Saying Y
332 here will force supervisor (kernel) accesses to use writethrough
333 caching. Writethrough caching means that data is written to memory
334 straight away, so that cache and memory data always agree.
335 Writethrough caching is less efficient, but is needed for some
336 drivers on 68060 based systems where the 68060 bus snooping signal
337 is hardwired on. The 53c710 SCSI driver is known to suffer from
346 prompt "Kernel core (/proc/kcore) format"
353 If you enabled support for /proc file system then the file
354 /proc/kcore will contain the kernel core image. This can be used
357 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
359 You have two choices here: ELF and A.OUT. Selecting ELF will make
360 /proc/kcore appear in ELF core format as defined by the Executable
361 and Linking Format specification. Selecting A.OUT will choose the
362 old "a.out" format which may be necessary for some old versions
363 of binutils or on some architectures.
365 This is especially useful if you have compiled the kernel with the
366 "-g" option to preserve debugging information. It is mainly used
367 for examining kernel data structures on the live kernel so if you
368 don't understand what this means or are not a kernel hacker, just
369 leave it at its default value ELF.
374 Not necessary unless you're using a very out-of-date binutils
375 version. You probably want KCORE_ELF.
380 tristate "Kernel support for a.out binaries"
382 A.out (Assembler.OUTput) is a set of formats for libraries and
383 executables used in the earliest versions of UNIX. Linux used the
384 a.out formats QMAGIC and ZMAGIC until they were replaced with the
387 As more and more programs are converted to ELF, the use for a.out
388 will gradually diminish. If you disable this option it will reduce
389 your kernel by one page. This is not much and by itself does not
390 warrant removing support. However its removal is a good idea if you
391 wish to ensure that absolutely none of your programs will use this
392 older executable format. If you don't know what to answer at this
393 point then answer Y. If someone told you "You need a kernel with
394 QMAGIC support" then you'll have to say Y here. You may answer M to
395 compile a.out support as a module and later load the module when you
396 want to use a program or library in a.out format. The module will be
397 called binfmt_aout. Saying M or N here is dangerous though,
398 because some crucial programs on your system might still be in A.OUT
402 tristate "Kernel support for ELF binaries"
404 ELF (Executable and Linkable Format) is a format for libraries and
405 executables used across different architectures and operating
406 systems. Saying Y here will enable your kernel to run ELF binaries
407 and enlarge it by about 13 KB. ELF support under Linux has now all
408 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
409 because it is portable (this does *not* mean that you will be able
410 to run executables from different architectures or operating systems
411 however) and makes building run-time libraries very easy. Many new
412 executables are distributed solely in ELF format. You definitely
415 Information about ELF is contained in the ELF HOWTO available from
416 <http://www.tldp.org/docs.html#howto>.
418 If you find that after upgrading from Linux kernel 1.2 and saying Y
419 here, you still can't run any ELF binaries (they just crash), then
420 you'll have to install the newest ELF runtime libraries, including
421 ld.so (check the file <file:Documentation/Changes> for location and
424 If you want to compile this as a module ( = code which can be
425 inserted in and removed from the running kernel whenever you want),
426 say M here and read <file:Documentation/modules.txt>. The module
427 will be called binfmt_elf. Saying M or N here is dangerous because
428 some crucial programs on your system might be in ELF format.
431 tristate "Kernel support for MISC binaries"
433 If you say Y here, it will be possible to plug wrapper-driven binary
434 formats into the kernel. You will like this especially when you use
435 programs that need an interpreter to run like Java, Python or
436 Emacs-Lisp. It's also useful if you often run DOS executables under
437 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
438 <http://www.tldp.org/docs.html#howto>). Once you have
439 registered such a binary class with the kernel, you can start one of
440 those programs simply by typing in its name at a shell prompt; Linux
441 will automatically feed it to the correct interpreter.
443 You can do other nice things, too. Read the file
444 <file:Documentation/binfmt_misc.txt> to learn how to use this
445 feature, and <file:Documentation/java.txt> for information about how
446 to include Java support.
448 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
449 use this part of the kernel.
451 You may say M here for module support and later load the module when
452 you have use for it; the module is called binfmt_misc. If you
453 don't know what to answer at this point, say Y.
456 bool "Amiga Zorro (AutoConfig) bus support"
459 This enables support for the Zorro bus in the Amiga. If you have
460 expansion cards in your Amiga that conform to the Amiga
461 AutoConfig(tm) specification, say Y, otherwise N. Note that even
462 expansion cards that do not fit in the Zorro slots but fit in e.g.
463 the CPU slot may fall in this category, so you have to say Y to let
467 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
468 depends on AMIGA && EXPERIMENTAL
470 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
471 600. If you intend to use pcmcia cards say Y; otherwise say N.
474 bool "Support for ST-RAM as swap space"
477 Some Atari 68k macines (including the 520STF and 1020STE) divide
478 their addressible memory into ST and TT sections. The TT section
479 (up to 512MB) is the main memory; the ST section (up to 4MB) is
480 accessible to the built-in graphics board, runs slower, and is
481 present mainly for backward compatibility with older machines.
483 This enables support for using (parts of) ST-RAM as swap space,
484 instead of as normal system memory. This can first enhance system
485 performance if you have lots of alternate RAM (compared to the size
486 of ST-RAM), because executable code always will reside in faster
487 memory. ST-RAM will remain as ultra-fast swap space. On the other
488 hand, it allows much improved dynamic allocations of ST-RAM buffers
489 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
490 sound). The probability that such allocations at module load time
491 fail is drastically reduced.
494 bool "ST-RAM statistics in /proc"
497 Say Y here to report ST-RAM usage statistics in /proc/stram. See
498 the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its
502 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
503 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
505 Use the power-on LED on your machine as a load meter. The exact
506 behavior is platform-dependent, but normally the flash frequency is
507 a hyperbolic function of the 5-minute load average.
509 # We have a dedicated heartbeat LED. :-)
511 bool "/proc/hardware support"
513 Say Y here to support the /proc/hardware file, which gives you
514 access to information about the machine you're running on,
515 including the model, CPU, MMU, clock speed, BogoMIPS rating,
519 tristate "Parallel port support (EXPERIMENTAL)"
520 depends on EXPERIMENTAL
522 If you want to use devices connected to your machine's parallel port
523 (the connector at the computer with 25 holes), e.g. printer, ZIP
524 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
525 create a mini network by connecting the parallel ports of two local
526 machines) etc., then you need to say Y here; please read
527 <file:Documentation/parport.txt> and
528 <file:drivers/parport/BUGS-parport>.
530 For extensive information about drivers for many devices attaching
531 to the parallel port see <http://www.torque.net/linux-pp.html> on
534 It is possible to share a single parallel port among several devices
535 and it is safe to compile all the corresponding drivers into the
536 kernel. If you want to compile parallel port support as a module
537 ( = code which can be inserted in and removed from the running
538 kernel whenever you want), say M here and read
539 <file:Documentation/modules.txt>. The module will be called
540 parport. If you have more than one parallel port and want to
541 specify which port and IRQ to be used by this driver at module load
542 time, take a look at <file:Documentation/parport.txt>.
547 tristate "Amiga builtin port"
548 depends on AMIGA && PARPORT
550 Say Y here if you need support for the parallel port hardware on
551 Amiga machines. This code is also available as a module (say M),
552 called parport_amiga. If in doubt, saying N is the safe plan.
555 tristate "Multiface III parallel port"
556 depends on ZORRO && PARPORT
558 Say Y here if you need parallel port support for the MFC3 card.
559 This code is also available as a module (say M), called
560 parport_mfc3. If in doubt, saying N is the safe plan.
564 depends on Q40 && PARPORT
567 You should say Y here if you have a PC-style parallel port. All IBM
568 PC compatible computers and some Alphas have PC-style parallel
571 This code is also available as a module. If you want to compile it
572 as a module ( = code which can be inserted in and removed from the
573 running kernel whenever you want), say M here and read
574 <file:Documentation/modules.txt>. The module will be called
580 tristate "Atari builtin port"
581 depends on ATARI && PARPORT
583 Say Y here if you need support for the parallel port hardware on
584 Atari machines. This code is also available as a module (say M),
585 called parport_atari. If in doubt, saying N is the safe plan.
588 tristate "Parallel printer support"
591 If you intend to attach a printer to the parallel port of your Linux
592 box (as opposed to using a serial printer; if the connector at the
593 printer has 9 or 25 holes ["female"], then it's serial), say Y.
594 Also read the Printing-HOWTO, available from
595 <http://www.tldp.org/docs.html#howto>.
597 It is possible to share one parallel port among several devices
598 (e.g. printer and ZIP drive) and it is safe to compile the
599 corresponding drivers into the kernel. If you want to compile this
600 driver as a module however ( = code which can be inserted in and
601 removed from the running kernel whenever you want), say M here and
602 read <file:Documentation/modules.txt> and
603 <file:Documentation/parport.txt>. The module will be called lp.
605 If you have several parallel ports, you can specify which ports to
606 use with the "lp" kernel command line option. (Try "man bootparam"
607 or see the documentation of your boot loader (lilo or loadlin) about
608 how to pass options to the kernel at boot time.) The syntax of the
609 "lp" command line option can be found in <file:drivers/char/lp.c>.
611 If you have more than 8 printers, you need to increase the LP_NO
612 macro in lp.c and the PARPORT_MAX macro in parport.h.
615 bool "IEEE 1284 transfer modes"
618 If you have a printer that supports status readback or device ID, or
619 want to use a device that uses enhanced parallel port transfer modes
620 such as EPP and ECP, say Y here to enable advanced IEEE 1284
621 transfer modes. Also say Y if you want device ID information to
622 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
626 depends on Q40 || AMIGA_PCMCIA || GG2
629 Find out whether you have ISA slots on your motherboard. ISA is the
630 name of a bus system, i.e. the way the CPU talks to the other stuff
631 inside your box. Other bus systems are PCI, EISA, MicroChannel
632 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
633 newer boards don't support it. If you have ISA, say Y, otherwise N.
635 config GENERIC_ISA_DMA
637 depends on Q40 || AMIGA_PCMCIA || GG2
640 source "drivers/pci/Kconfig"
642 source "drivers/zorro/Kconfig"
645 source "drivers/pnp/Kconfig"
650 source "drivers/mtd/Kconfig"
652 source "drivers/block/Kconfig"
654 source "drivers/md/Kconfig"
656 source "drivers/input/Kconfig"
659 menu "ATA/ATAPI/MFM/RLL device support"
662 tristate "ATA/ATAPI/MFM/RLL device support"
664 If you say Y here, your kernel will be able to manage low cost mass
665 storage units such as ATA/(E)IDE and ATAPI units. The most common
666 cases are IDE hard drives and ATAPI CD-ROM drives.
668 If your system is pure SCSI and doesn't use these interfaces, you
671 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
672 for mass storage units such as hard disks. It was designed by
673 Western Digital and Compaq Computer in 1984. It was then named
674 ST506. Quite a number of disks use the IDE interface.
676 AT Attachment (ATA) is the superset of the IDE specifications.
677 ST506 was also called ATA-1.
679 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
680 ATA-3. It provides support for larger disks (up to 8.4GB by means of
681 the LBA standard), more disks (4 instead of 2) and for other mass
682 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
683 ATA-4 and provides faster (and more CPU friendly) transfer modes
684 than previous PIO (Programmed processor Input/Output) from previous
685 ATA/IDE standards by means of fast DMA controllers.
687 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
688 CD-ROM drives, similar in many respects to the SCSI protocol.
690 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
691 designed in order to prevent data corruption and disk crash by
692 detecting pre hardware failure conditions (heat, access time, and
693 the like...). Disks built since June 1995 may follow this standard.
694 The kernel itself don't manage this; however there are quite a
695 number of user programs such as smart that can query the status of
696 SMART parameters disk.
698 If you want to compile this driver as a module ( = code which can be
699 inserted in and removed from the running kernel whenever you want),
700 say M here and read <file:Documentation/modules.txt>. The module
703 For further information, please read <file:Documentation/ide.txt>.
707 source "drivers/ide/Kconfig"
712 menu "SCSI device support"
715 tristate "SCSI device support"
717 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
718 any other SCSI device under Linux, say Y and make sure that you know
719 the name of your SCSI host adapter (the card inside your computer
720 that "speaks" the SCSI protocol, also called SCSI controller),
721 because you will be asked for it.
723 You also need to say Y here if you want support for the parallel
724 port version of the 100 MB IOMEGA ZIP drive.
726 This driver is also available as a module ( = code which can be
727 inserted in and removed from the running kernel whenever you want).
728 The module will be called scsi_mod. If you want to compile it as
729 a module, say M here and read <file:Documentation/modules.txt> and
730 <file:Documentation/scsi/scsi.txt>. However, do not compile this as a
731 module if your root file system (the one containing the directory /)
732 is located on a SCSI device.
734 comment "SCSI support type (disk, tape, CD-ROM)"
738 tristate "SCSI disk support"
741 If you want to use a SCSI hard disk or the SCSI or parallel port
742 version of the IOMEGA ZIP drive under Linux, say Y and read the
743 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
744 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
747 This driver is also available as a module ( = code which can be
748 inserted in and removed from the running kernel whenever you want).
749 The module will be called sd_mod. If you want to compile it as a
750 module, say M here and read <file:Documentation/modules.txt> and
751 <file:Documentation/scsi/scsi.txt>. Do not compile this driver as a
752 module if your root file system (the one containing the directory /)
753 is located on a SCSI disk. In this case, do not compile the driver
754 for your SCSI host adapter (below) as a module either.
757 int "Maximum number of SCSI disks that can be loaded as modules"
758 depends on BLK_DEV_SD
761 This controls the amount of additional space allocated in tables for
762 drivers that are loaded as modules after the kernel is booted. In
763 the event that the SCSI core itself was loaded as a module, this
764 value is the number of additional disks that can be loaded after the
765 first host driver is loaded.
767 Admittedly this isn't pretty, but there are tons of race conditions
768 involved with resizing the internal arrays on the fly. Someday this
769 flag will go away, and everything will work automatically.
771 If you don't understand what's going on, go with the default.
774 tristate "SCSI tape support"
777 If you want to use a SCSI tape drive under Linux, say Y and read the
778 SCSI-HOWTO, available from
779 <http://www.tldp.org/docs.html#howto>, and
780 <file:Documentation/scsi/st.txt> in the kernel source. This is NOT for
783 This driver is also available as a module ( = code which can be
784 inserted in and removed from the running kernel whenever you want).
785 The module will be called st. If you want to compile it as a
786 module, say M here and read <file:Documentation/modules.txt> and
787 <file:Documentation/scsi/scsi.txt>.
790 int "Maximum number of SCSI tapes that can be loaded as modules"
791 depends on CHR_DEV_ST
794 This controls the amount of additional space allocated in tables for
795 drivers that are loaded as modules after the kernel is booted. In
796 the event that the SCSI core itself was loaded as a module, this
797 value is the number of additional tapes that can be loaded after the
798 first host driver is loaded.
800 Admittedly this isn't pretty, but there are tons of race conditions
801 involved with resizing the internal arrays on the fly. Someday this
802 flag will go away, and everything will work automatically.
804 If you don't understand what's going on, go with the default.
807 tristate "SCSI CDROM support"
810 If you want to use a SCSI CD-ROM under Linux, say Y and read the
811 SCSI-HOWTO and the CD-ROM-HOWTO at
812 <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
813 or M to "ISO 9660 CD-ROM file system support" later.
815 This driver is also available as a module ( = code which can be
816 inserted in and removed from the running kernel whenever you want).
817 The module will be called sr_mod. If you want to compile it as a
818 module, say M here and read <file:Documentation/modules.txt> and
819 <file:Documentation/scsi/scsi.txt>.
821 config BLK_DEV_SR_VENDOR
822 bool "Enable vendor-specific extensions (for SCSI CDROM)"
823 depends on BLK_DEV_SR
825 This enables the usage of vendor specific SCSI commands. This is
826 required to support multisession CDs with old NEC/TOSHIBA cdrom
827 drives (and HP Writers). If you have such a drive and get the first
828 session only, try saying Y here; everybody else says N.
831 int "Maximum number of CDROM devices that can be loaded as modules"
832 depends on BLK_DEV_SR
835 This controls the amount of additional space allocated in tables for
836 drivers that are loaded as modules after the kernel is booted. In
837 the event that the SCSI core itself was loaded as a module, this
838 value is the number of additional CD-ROMs that can be loaded after
839 the first host driver is loaded.
841 Admittedly this isn't pretty, but there are tons of race conditions
842 involved with resizing the internal arrays on the fly. Someday this
843 flag will go away, and everything will work automatically.
845 If you don't understand what's going on, go with the default.
848 tristate "SCSI generic support"
851 If you want to use SCSI scanners, synthesizers or CD-writers or just
852 about anything having "SCSI" in its name other than hard disks,
853 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
854 directly, so you need some additional software which knows how to
855 talk to these devices using the SCSI protocol:
857 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
858 writer software look at Cdrtools
859 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
860 and for burning a "disk at once": CDRDAO
861 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
862 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
863 For other devices, it's possible that you'll have to write the
864 driver software yourself. Please read the file
865 <file:Documentation/scsi/scsi-generic.txt> for more information.
867 If you want to compile this as a module ( = code which can be
868 inserted in and removed from the running kernel whenever you want),
869 say M here and read <file:Documentation/modules.txt> and
870 <file:Documentation/scsi/scsi.txt>. The module will be called sg.
873 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
876 config SCSI_MULTI_LUN
877 bool "Probe all LUNs on each SCSI device"
880 If you have a SCSI device that supports more than one LUN (Logical
881 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
882 can say Y here to force the SCSI driver to probe for multiple LUNs.
883 A SCSI device with multiple LUNs acts logically like multiple SCSI
884 devices. The vast majority of SCSI devices have only one LUN, and
885 so most people can say N here and should in fact do so, because it
888 config SCSI_CONSTANTS
889 bool "Verbose SCSI error reporting (kernel size +=12K)"
892 The error messages regarding your SCSI hardware will be easier to
893 understand if you say Y here; it will enlarge your kernel by about
894 12 KB. If in doubt, say Y.
897 bool "SCSI logging facility"
900 This turns on a logging facility that can be used to debug a number
901 of SCSI related problems.
903 If you say Y here, no logging output will appear by default, but you
904 can enable logging by saying Y to "/proc file system support" and
905 "Sysctl support" below and executing the command
907 echo "scsi log token [level]" > /proc/scsi/scsi
909 at boot time after the /proc file system has been mounted.
911 There are a number of things that can be used for 'token' (you can
912 find them in the source: <file:drivers/scsi/scsi.c>), and this
913 allows you to select the types of information you want, and the
914 level allows you to select the level of verbosity.
916 If you say N here, it may be harder to track down some types of SCSI
917 problems. If you say Y here your kernel will be somewhat larger, but
918 there should be no noticeable performance impact as long as you have
922 menu "SCSI low-level drivers"
926 tristate "A3000 WD33C93A support"
927 depends on AMIGA && SCSI
929 If you have an Amiga 3000 and have SCSI devices connected to the
930 built-in SCSI controller, say Y. Otherwise, say N. This driver is
931 also available as a module ( = code which can be inserted in and
932 removed from the running kernel whenever you want). The module is
933 called wd33c93. If you want to compile it as a module, say M here
934 and read <file:Documentation/modules.txt>.
937 bool "A4000T SCSI support (EXPERIMENTAL)"
938 depends on AMIGA && EXPERIMENTAL
940 Support for the NCR53C710 SCSI controller on the Amiga 4000T.
943 tristate "A2091 WD33C93A support"
944 depends on ZORRO && SCSI
946 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
947 say N. This driver is also available as a module ( = code which can
948 be inserted in and removed from the running kernel whenever you
949 want). The module is called wd33c93. If you want to compile it as
950 a module, say M here and read <file:Documentation/modules.txt>.
953 tristate "GVP Series II WD33C93A support"
954 depends on ZORRO && SCSI
956 If you have a Great Valley Products Series II SCSI controller,
957 answer Y. Also say Y if you have a later model of GVP SCSI
958 controller (such as the GVP A4008 or a Combo board). Otherwise,
959 answer N. This driver does NOT work for the T-Rex series of
960 accelerators from TekMagic and GVP-M.
962 This driver is also available as a module ( = code which can be
963 inserted in and removed from the running kernel whenever you
964 want). The module will be called gvp11. If you want to compile it
965 as a module, say M here and read <file:Documentation/modules.txt>.
967 config CYBERSTORM_SCSI
968 tristate "CyberStorm SCSI support"
969 depends on ZORRO && SCSI
971 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
972 accelerator board and the optional Cyberstorm SCSI controller,
973 answer Y. Otherwise, say N.
975 config CYBERSTORMII_SCSI
976 tristate "CyberStorm Mk II SCSI support"
977 depends on ZORRO && SCSI
979 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
980 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
984 tristate "Blizzard 2060 SCSI support"
985 depends on ZORRO && SCSI
987 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
988 and want to use the onboard SCSI controller, say Y. Otherwise,
992 tristate "Blizzard 1230IV/1260 SCSI support"
993 depends on ZORRO && SCSI
995 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
996 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
1000 tristate "Fastlane SCSI support"
1001 depends on ZORRO && SCSI
1003 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
1004 one in the near future, say Y to this question. Otherwise, say N.
1007 bool "A4091 SCSI support (EXPERIMENTAL)"
1008 depends on ZORRO && EXPERIMENTAL
1010 Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller
1011 (1993). Very obscure -- the 4091 was part of an Amiga 4000 upgrade
1012 plan at the time the Amiga business was sold to DKB.
1014 config WARPENGINE_SCSI
1015 bool "WarpEngine SCSI support (EXPERIMENTAL)"
1016 depends on ZORRO && EXPERIMENTAL
1018 Support for MacroSystem Development's WarpEngine Amiga SCSI-2
1020 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
1022 config BLZ603EPLUS_SCSI
1023 bool "Blizzard PowerUP 603e+ SCSI (EXPERIMENTAL)"
1024 depends on ZORRO && EXPERIMENTAL
1026 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
1027 accelerator, say Y. Otherwise, say N.
1030 tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
1031 depends on ZORRO && EXPERIMENTAL && SCSI
1033 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
1034 Y to this question. If you're in doubt about whether you have one,
1036 <http://amiga.multigraph.com/photos/oktagon.html>.
1038 # bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
1039 # bool 'GVP Turbo 040/060 SCSI support (EXPERIMENTAL)' CONFIG_GVP_TURBO_SCSI
1041 tristate "Atari native SCSI support"
1042 depends on ATARI && SCSI
1044 If you have an Atari with built-in NCR5380 SCSI controller (TT,
1045 Falcon, ...) say Y to get it supported. Of course also, if you have
1046 a compatible SCSI controller (e.g. for Medusa). This driver is also
1047 available as a module ( = code which can be inserted in and removed
1048 from the running kernel whenever you want). The module is called
1049 atari_scsi. If you want to compile it as a module, say M here and
1050 read <file:Documentation/modules.txt>. This driver supports both
1051 styles of NCR integration into the system: the TT style (separate
1052 DMA), and the Falcon style (via ST-DMA, replacing ACSI). It does
1053 NOT support other schemes, like in the Hades (without DMA).
1055 config ATARI_SCSI_TOSHIBA_DELAY
1056 bool "Long delays for Toshiba CD-ROMs"
1057 depends on ATARI_SCSI
1059 This option increases the delay after a SCSI arbitration to
1060 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
1061 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
1062 would impact performance a bit, so say N.
1064 config ATARI_SCSI_RESET_BOOT
1065 bool "Reset SCSI-devices at boottime"
1066 depends on ATARI_SCSI
1068 Reset the devices on your Atari whenever it boots. This makes the
1069 boot process fractionally longer but may assist recovery from errors
1070 that leave the devices with SCSI operations partway completed.
1073 bool "Hades SCSI DMA emulator"
1074 depends on ATARI_SCSI && HADES
1076 This option enables code which emulates the TT SCSI DMA chip on the
1077 Hades. This increases the SCSI transfer rates at least ten times
1078 compared to PIO transfers.
1081 bool "Macintosh NCR5380 SCSI"
1084 This is the NCR 5380 SCSI controller included on most of the 68030
1085 based Macintoshes. If you have one of these say Y and read the
1086 SCSI-HOWTO, available from
1087 <http://www.tldp.org/docs.html#howto>.
1090 tristate "Macintosh NCR53c9[46] SCSI"
1091 depends on MAC && SCSI
1093 This is the NCR 53c9x SCSI controller found on most of the 68040
1094 based Macintoshes. If you have one of these say Y and read the
1095 SCSI-HOWTO, available from
1096 <http://www.tldp.org/docs.html#howto>.
1098 This driver is also available as a module ( = code which can be
1099 inserted in and removed from the running kernel whenever you want).
1100 The module will be called mac_esp. If you want to compile it as
1101 a module, say M here and read <file:Documentation/modules.txt>.
1103 # dep_tristate 'SCSI debugging host adapter' CONFIG_SCSI_DEBUG $CONFIG_SCSI
1105 bool "WD33C93 SCSI driver for MVME147"
1108 Support for the on-board SCSI controller on the Motorola MVME147
1109 single-board computer.
1112 bool "NCR53C710 SCSI driver for MVME16x"
1115 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
1116 SCSI controller chip. Almost everyone using one of these boards
1117 will want to say Y to this question.
1119 config BVME6000_SCSI
1120 bool "NCR53C710 SCSI driver for BVME6000"
1123 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
1124 SCSI controller chip. Almost everyone using one of these boards
1125 will want to say Y to this question.
1128 tristate "Sun3 NCR5380 SCSI"
1129 depends on SUN3 && SCSI
1131 This option will enable support for the OBIO (onboard io) NCR5380
1132 SCSI controller found in the Sun 3/50 and 3/60, as well as for
1133 "Sun3" type VME scsi controllers also based on the NCR5380.
1134 General Linux information on the Sun 3 series (now discontinued)
1135 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
1138 bool "Sun3x ESP SCSI"
1141 The ESP was an on-board SCSI controller used on Sun 3/80
1142 machines. Say Y here to compile in support for it.
1148 source "net/Kconfig"
1151 menu "Character devices"
1154 tristate "Q40 Standard/generic serial support" if Q40
1155 default DN_SERIAL if APOLLO
1157 This selects whether you want to include the driver for the standard
1158 serial ports. The standard answer is Y. People who might say N
1159 here are those that are setting up dedicated Ethernet WWW/FTP
1160 servers, or users that have one of the various bus mice instead of a
1161 serial mouse and don't intend to use their machine's standard serial
1162 port for anything. (Note that the Cyclades and Stallion multi
1163 serial port drivers do not need this driver built in for them to
1166 If you want to compile this driver as a module, say M here and read
1167 <file:Documentation/modules.txt>. The module will be called
1169 [WARNING: Do not compile this driver as a module if you are using
1170 non-standard serial ports, since the configuration information will
1171 be lost when the driver is unloaded. This limitation may be lifted
1174 BTW1: If you have a mouseman serial mouse which is not recognized by
1175 the X window system, try running gpm first.
1177 BTW2: If you intend to use a software modem (also called Winmodem)
1178 under Linux, forget it. These modems are crippled and require
1179 proprietary drivers which are only available under Windows.
1181 Most people will say Y or M here, so that they can use serial mice,
1182 modems and similar devices connecting to the standard serial ports.
1184 config SERIAL_EXTENDED
1185 bool "Extended dumb serial driver options"
1188 If you wish to use any non-standard features of the standard "dumb"
1189 driver, say Y here. This includes HUB6 support, shared serial
1190 interrupts, special multiport support, support for more than the
1191 four COM 1/2/3/4 boards, etc.
1193 Note that the answer to this question won't directly affect the
1194 kernel: saying N will just cause the configurator to skip all
1195 the questions about serial driver options. If unsure, say N.
1197 config SERIAL_MANY_PORTS
1198 bool "Support more than 4 serial ports"
1199 depends on SERIAL_EXTENDED
1201 Say Y here if you have dumb serial boards other than the four
1202 standard COM 1/2/3/4 ports. This may happen if you have an AST
1203 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
1204 from <http://www.tldp.org/docs.html#howto>), or other custom
1205 serial port hardware which acts similar to standard serial port
1206 hardware. If you only use the standard COM 1/2/3/4 ports, you can
1207 say N here to save some memory. You can also say Y if you have an
1208 "intelligent" multiport card such as Cyclades, Digiboards, etc.
1210 config SERIAL_SHARE_IRQ
1211 bool "Support for sharing serial interrupts"
1212 depends on SERIAL_EXTENDED
1214 Some serial boards have hardware support which allows multiple dumb
1215 serial ports on the same board to share a single IRQ. To enable
1216 support for this in the serial driver, say Y here.
1218 config SERIAL_MULTIPORT
1219 bool "Support special multiport boards"
1220 depends on SERIAL_EXTENDED
1222 Some multiport serial ports have special ports which are used to
1223 signal when there are any serial ports on the board which need
1224 servicing. Say Y here to enable the serial driver to take advantage
1225 of those special I/O ports.
1228 bool "Support the Bell Technologies HUB6 card"
1229 depends on SERIAL_EXTENDED
1231 Say Y here to enable support in the dumb serial driver to support
1235 bool "Virtual terminal"
1237 If you say Y here, you will get support for terminal devices with
1238 display and keyboard devices. These are called "virtual" because you
1239 can run several virtual terminals (also called virtual consoles) on
1240 one physical terminal. This is rather useful, for example one
1241 virtual terminal can collect system messages and warnings, another
1242 one can be used for a text-mode user session, and a third could run
1243 an X session, all in parallel. Switching between virtual terminals
1244 is done with certain key combinations, usually Alt-<function key>.
1246 The setterm command ("man setterm") can be used to change the
1247 properties (such as colors or beeping) of a virtual terminal. The
1248 man page console_codes(4) ("man console_codes") contains the special
1249 character sequences that can be used to change those properties
1250 directly. The fonts used on virtual terminals can be changed with
1251 the setfont ("man setfont") command and the key bindings are defined
1252 with the loadkeys ("man loadkeys") command.
1254 You need at least one virtual terminal device in order to make use
1255 of your keyboard and monitor. Therefore, only people configuring an
1256 embedded system would want to say N here in order to save some
1257 memory; the only way to log into such a system is then via a serial
1258 or network connection.
1260 If unsure, say Y, or else you won't be able to do much with your new
1261 shiny Linux system :-)
1264 bool "Support for console on virtual terminal"
1267 The system console is the device which receives all kernel messages
1268 and warnings and which allows logins in single user mode. If you
1269 answer Y here, a virtual terminal (the device used to interact with
1270 a physical terminal) can be used as system console. This is the most
1271 common mode of operations, so you should say Y here unless you want
1272 the kernel messages be output only to a serial port (in which case
1273 you should say Y to "Console on serial port", below).
1275 If you do say Y here, by default the currently visible virtual
1276 terminal (/dev/tty0) will be used as system console. You can change
1277 that with a kernel command line option such as "console=tty3" which
1278 would use the third virtual terminal as system console. (Try "man
1279 bootparam" or see the documentation of your boot loader (lilo or
1280 loadlin) about how to pass options to the kernel at boot time.)
1294 If you say Y here and create a character special file /dev/nvram
1295 with major number 10 and minor number 144 using mknod ("man mknod"),
1296 you get read and write access to the 50 bytes of non-volatile memory
1297 in the real time clock (RTC), which is contained in every PC and
1300 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
1301 on Ataris. /dev/nvram may be used to view settings there, or to
1302 change them (with some utility). It could also be used to frequently
1303 save a few bits of very important data that may not be lost over
1304 power-off and for which writing to disk is too insecure. Note
1305 however that most NVRAM space in a PC belongs to the BIOS and you
1306 should NEVER idly tamper with it. See Ralf Brown's interrupt list
1307 for a guide to the use of CMOS bytes by your BIOS.
1309 On Atari machines, /dev/nvram is always configured and does not need
1312 This driver is also available as a module ( = code which can be
1313 inserted in and removed from the running kernel whenever you want).
1314 The module will be called nvram. If you want to compile it as a
1315 module, say M here and read <file:Documentation/modules.txt>.
1318 tristate "Atari MFP serial support"
1321 If you like to use the MFP serial ports ("Modem1", "Serial1") under
1322 Linux, say Y. The driver equally supports all kinds of MFP serial
1323 ports and automatically detects whether Serial1 is available.
1325 This driver is also available as a module ( = code which can be
1326 inserted in and removed from the running kernel whenever you want).
1327 If you want to compile it as a module, say M here and read
1328 <file:Documentation/modules.txt>.
1330 Note for Falcon users: You also have an MFP port, it's just not
1331 wired to the outside... But you could use the port under Linux.
1334 tristate "Atari SCC serial support"
1337 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
1338 LAN) and like to use them under Linux, say Y. All built-in SCC's are
1339 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
1340 two connectors for channel A (Serial2 and LAN), they are visible as
1341 two separate devices.
1343 This driver is also available as a module ( = code which can be
1344 inserted in and removed from the running kernel whenever you want).
1345 If you want to compile it as a module, say M here and read
1346 <file:Documentation/modules.txt>.
1348 config ATARI_SCC_DMA
1349 bool "Atari SCC serial DMA support"
1350 depends on ATARI_SCC
1352 This enables DMA support for receiving data on channel A of the SCC.
1353 If you have a TT you may say Y here and read
1354 drivers/char/atari_SCC.README. All other users should say N here,
1355 because only the TT has SCC-DMA, even if your machine keeps claiming
1359 tristate "Atari MIDI serial support"
1362 If you want to use your Atari's MIDI port in Linux, say Y.
1364 This driver is also available as a module ( = code which can be
1365 inserted in and removed from the running kernel whenever you
1366 want). If you want to compile it as a module, say M here and read
1367 <file:Documentation/modules.txt>.
1370 tristate "Atari DSP56k support (EXPERIMENTAL)"
1371 depends on ATARI && EXPERIMENTAL
1373 If you want to be able to use the DSP56001 in Falcons, say Y. This
1374 driver is still experimental, and if you don't know what it is, or
1375 if you don't have this processor, just say N.
1377 This driver is also available as a module ( = code which can be
1378 inserted in and removed from the running kernel whenever you want).
1379 If you want to compile it as a module, say M here and read
1380 <file:Documentation/modules.txt>.
1382 config AMIGA_BUILTIN_SERIAL
1383 tristate "Amiga builtin serial support"
1386 If you want to use your Amiga's built-in serial port in Linux,
1389 This driver is also available as a module ( = code which can be
1390 inserted in and removed from the running kernel whenever you
1391 want). If you want to compile it as a module, say M here and read
1392 <file:Documentation/modules.txt>.
1394 config WHIPPET_SERIAL
1395 tristate "Hisoft Whippet PCMCIA serial support"
1396 depends on AMIGA_PCMCIA
1398 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
1399 is no listing for the Whippet in their Amiga section.
1401 config MULTIFACE_III_TTY
1402 tristate "Multiface Card III serial support"
1405 If you want to use a Multiface III card's serial port in Linux,
1408 This driver is also available as a module ( = code which can be
1409 inserted in and removed from the running kernel whenever you want).
1410 If you want to compile it as a module, say M here and read
1411 <file:Documentation/modules.txt>.
1414 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
1415 depends on AMIGA && EXPERIMENTAL
1417 This option supports the 2232 7-port serial card shipped with the
1418 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
1419 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
1420 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
1421 ports were connected with 8 pin DIN connectors on the card bracket,
1422 for which 8 pin to DB25 adapters were supplied. The card also had
1423 jumpers internally to toggle various pinning configurations.
1425 This driver can be built as a module; but then "generic_serial"
1426 will also be built as a module. This has to be loaded before
1427 "ser_a2232". If you want to do this, answer M here and read
1428 "<file:Documentation/modules.txt>".
1431 tristate "GVP IO-Extender support"
1432 depends on PARPORT=n && ZORRO
1434 If you want to use a GVP IO-Extender serial card in Linux, say Y.
1438 tristate "GVP IO-Extender parallel printer support"
1441 Say Y to enable driving a printer from the parallel port on your
1442 GVP IO-Extender card, N otherwise.
1444 config GVPIOEXT_PLIP
1445 tristate "GVP IO-Extender PLIP support"
1448 Say Y to enable doing IP over the parallel port on your GVP
1449 IO-Extender card, N otherwise.
1452 tristate "Macintosh serial support"
1456 bool "Apple Desktop Bus (ADB) support"
1459 Apple Desktop Bus (ADB) support is for support of devices which
1460 are connected to an ADB port. ADB devices tend to have 4 pins.
1461 If you have an Apple Macintosh prior to the iMac, or a
1462 "Blue and White G3", you probably want to say Y here. Otherwise
1466 bool "Include Mac II ADB driver"
1469 Say Y here if want your kernel to support Macintosh systems that use
1470 the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
1471 Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
1475 bool "Include Mac IIsi ADB driver"
1478 Say Y here if want your kernel to support Macintosh systems that use
1479 the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
1480 II, LC, LC II, LC III, Performa 460, and the Performa 600.
1483 bool "Include CUDA ADB driver"
1486 This provides support for CUDA based Power Macintosh systems. This
1487 includes most OldWorld PowerMacs, the first generation iMacs, the
1488 Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
1489 should use CONFIG_ADB_PMU instead.
1494 bool "Include IOP (IIfx/Quadra 9x0) ADB driver"
1497 The I/O Processor (IOP) is an Apple custom IC designed to provide
1498 intelligent support for I/O controllers. It is described at
1499 <http://www.angelfire.com/ca2/dev68k/iopdesc.html> to enable direct
1500 support for it, say 'Y' here.
1503 bool "Include PMU (Powerbook) ADB driver"
1506 Say Y here if want your kernel to support the m68k based Powerbooks.
1507 This includes the PowerBook 140, PowerBook 145, PowerBook 150,
1508 PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
1509 PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
1510 PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
1511 PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
1514 bool "Use input layer for ADB devices"
1515 depends on MAC && INPUT=y
1517 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
1518 such as keyboards, mice, joysticks, or graphic tablets handled by
1519 the input layer. If you say Y here, make sure to say Y to the
1520 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
1521 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
1522 support" (CONFIG_INPUT_EVDEV) as well.
1524 If you say N here, you still have the option of using the old ADB
1525 keyboard and mouse drivers.
1531 depends on INPUT_ADBHID
1534 config MAC_ADBKEYCODES
1535 bool "Support for ADB raw keycodes"
1536 depends on INPUT_ADBHID
1538 This provides support for sending raw ADB keycodes to console
1539 devices. This is the default up to 2.4.0, but in future this may be
1540 phased out in favor of generic Linux keycodes. If you say Y here,
1541 you can dynamically switch via the
1542 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
1543 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
1546 If unsure, say Y here.
1548 config MAC_EMUMOUSEBTN
1549 bool "Support for mouse button 2+3 emulation"
1550 depends on INPUT_ADBHID
1552 This provides generic support for emulating the 2nd and 3rd mouse
1553 button with keypresses. If you say Y here, the emulation is still
1554 disabled by default. The emulation is controlled by these sysctl
1556 /proc/sys/dev/mac_hid/mouse_button_emulation
1557 /proc/sys/dev/mac_hid/mouse_button2_keycode
1558 /proc/sys/dev/mac_hid/mouse_button3_keycode
1561 bool "Support for ADB keyboard (old driver)"
1562 depends on MAC && !INPUT_ADBHID
1564 This option allows you to use an ADB keyboard attached to your
1565 machine. Note that this disables any other (ie. PS/2) keyboard
1566 support, even if your machine is physically capable of using both at
1569 If you use an ADB keyboard (4 pin connector), say Y here.
1570 If you use a PS/2 keyboard (6 pin connector), say N here.
1573 tristate "HP DCA serial support"
1576 If you want to use the internal "DCA" serial ports on an HP300
1577 machine, say Y here.
1580 bool "SCC support for MVME147 serial ports"
1583 This is the driver for the serial ports on the Motorola MVME147
1584 boards. Everyone using one of these boards should say Y here.
1587 bool "CD2401 support for MVME166/7 serial ports"
1590 This is the driver for the serial ports on the Motorola MVME166,
1591 167, and 172 boards. Everyone using one of these boards should say
1595 bool "SCC support for MVME162 serial ports"
1598 This is the driver for the serial ports on the Motorola MVME162 and
1599 172 boards. Everyone using one of these boards should say Y here.
1602 bool "SCC support for BVME6000 serial ports"
1605 This is the driver for the serial ports on the BVME4000 and BVME6000
1606 boards from BVM Ltd. Everyone using one of these boards should say
1610 bool "Support for DN serial port (dummy)"
1613 config SERIAL_CONSOLE
1614 bool "Support for serial port console"
1615 depends on (AMIGA || ATARI || MAC || HP300 || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_SCC=y || ATARI_MIDI=y || MAC_SCC=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || HPDCA=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
1617 If you say Y here, it will be possible to use a serial port as the
1618 system console (the system console is the device which receives all
1619 kernel messages and warnings and which allows logins in single user
1620 mode). This could be useful if some terminal or printer is connected
1621 to that serial port.
1623 Even if you say Y here, the currently visible virtual console
1624 (/dev/tty0) will still be used as the system console by default, but
1625 you can alter that using a kernel command line option such as
1626 "console=ttyS1". (Try "man bootparam" or see the documentation of
1627 your boot loader (lilo or loadlin) about how to pass options to the
1628 kernel at boot time.)
1630 If you don't have a VGA card installed and you say Y here, the
1631 kernel will automatically use the first serial line, /dev/ttyS0, as
1637 bool "Support for user serial device modules"
1640 bool "Watchdog Timer Support"
1642 If you say Y here (and to one of the following options) and create a
1643 character special file /dev/watchdog with major number 10 and minor
1644 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
1645 subsequently opening the file and then failing to write to it for
1646 longer than 1 minute will result in rebooting the machine. This
1647 could be useful for a networked machine that needs to come back
1648 online as fast as possible after a lock-up. There's both a watchdog
1649 implementation entirely in software (which can sometimes fail to
1650 reboot the machine) and a driver for hardware watchdog boards, which
1651 are more robust and can also keep track of the temperature inside
1652 your computer. For details, read <file:Documentation/watchdog.txt>
1653 in the kernel source.
1655 The watchdog is usually used together with the watchdog daemon
1656 which is available from
1657 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
1658 also monitor NFS connections and can reboot the machine when the process
1663 config WATCHDOG_NOWAYOUT
1664 bool "Disable watchdog shutdown on close"
1667 The default watchdog behaviour (which you get if you say N here) is
1668 to stop the timer if the process managing it closes the file
1669 /dev/watchdog. It's always remotely possible that this process might
1670 get killed. If you say Y here, the watchdog cannot be stopped once
1671 it has been started.
1673 config SOFT_WATCHDOG
1674 bool "Software watchdog"
1677 A software monitoring watchdog. This will fail to reboot your system
1678 from some situations that the hardware watchdog will recover
1679 from. Equally it's a lot cheaper to install.
1681 This driver is also available as a module ( = code which can be
1682 inserted in and removed from the running kernel whenever you want).
1683 If you want to compile it as a module, say M here and read
1684 <file:Documentation/modules.txt>. The module will be called
1688 bool "Enhanced Real Time Clock Support"
1691 If you say Y here and create a character special file /dev/rtc with
1692 major number 10 and minor number 135 using mknod ("man mknod"), you
1693 will get access to the real time clock (or hardware clock) built
1696 Every PC has such a clock built in. It can be used to generate
1697 signals from as low as 1Hz up to 8192Hz, and can also be used
1698 as a 24 hour alarm. It reports status information via the file
1699 /proc/driver/rtc and its behaviour is set by various ioctls on
1702 If you run Linux on a multiprocessor machine and said Y to
1703 "Symmetric Multi Processing" above, you should say Y here to read
1704 and set the RTC in an SMP compatible fashion.
1706 If you think you have a use for such a device (such as periodic data
1707 sampling), then say Y here, and read <file:Documentation/rtc.txt>
1710 This driver is also available as a module ( = code which can be
1711 inserted in and removed from the running kernel whenever you want).
1712 The module is called rtc. If you want to compile it as a module,
1713 say M here and read <file:Documentation/modules.txt>.
1716 tristate "Generic /dev/rtc emulation" if !SUN3
1720 If you say Y here and create a character special file /dev/rtc with
1721 major number 10 and minor number 135 using mknod ("man mknod"), you
1722 will get access to the real time clock (or hardware clock) built
1725 It reports status information via the file /proc/driver/rtc and its
1726 behaviour is set by various ioctls on /dev/rtc. If you enable the
1727 "extended RTC operation" below it will also provide an emulation
1728 for RTC_UIE which is required by some programs and may improve
1729 precision in some cases.
1731 This driver is also available as a module ( = code which can be
1732 inserted in and removed from the running kernel whenever you want).
1733 The module is called genrtc. If you want to compile it as a module,
1734 say M here and read <file:Documentation/modules.txt>. To load the
1735 module automatically add 'alias char-major-10-135 genrtc' to your
1739 bool "Extended RTC operation"
1742 Provides an emulation for RTC_UIE which is required by some programs
1743 and may improve precision of the generic RTC support in some cases.
1746 bool "Unix98 PTY support"
1748 A pseudo terminal (PTY) is a software device consisting of two
1749 halves: a master and a slave. The slave device behaves identical to
1750 a physical terminal; the master device is used by a process to
1751 read data from and write data to the slave, thereby emulating a
1752 terminal. Typical programs for the master side are telnet servers
1755 Linux has traditionally used the BSD-like names /dev/ptyxx for
1756 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
1757 has a number of problems. The GNU C library glibc 2.1 and later,
1758 however, supports the Unix98 naming standard: in order to acquire a
1759 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
1760 terminal is then made available to the process and the pseudo
1761 terminal slave can be accessed as /dev/pts/<number>. What was
1762 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
1764 The entries in /dev/pts/ are created on the fly by a virtual
1765 file system; therefore, if you say Y here you should say Y to
1766 "/dev/pts file system for Unix98 PTYs" as well.
1768 If you want to say Y here, you need to have the C library glibc 2.1
1769 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
1770 Read the instructions in <file:Documentation/Changes> pertaining to
1771 pseudo terminals. It's safe to say N.
1773 config UNIX98_PTY_COUNT
1774 int "Maximum number of Unix98 PTYs in use (0-2048)"
1775 depends on UNIX98_PTYS
1778 The maximum number of Unix98 PTYs that can be used at any one time.
1779 The default is 256, and should be enough for desktop systems. Server
1780 machines which support incoming telnet/rlogin/ssh connections and/or
1781 serve several X terminals may want to increase this: every incoming
1782 connection and every xterm uses up one PTY.
1784 When not in use, each additional set of 256 PTYs occupy
1785 approximately 8 KB of kernel memory on 32-bit architectures.
1790 menu "Sound support"
1793 tristate "Sound card support"
1795 source "sound/oss/dmasound/Kconfig"
1801 source "drivers/video/Kconfig"
1803 menu "Kernel hacking"
1806 bool "Kernel debugging"
1809 bool "Magic SysRq key"
1810 depends on DEBUG_KERNEL
1812 If you say Y here, you will have some control over the system even
1813 if the system crashes for example during kernel debugging (e.g., you
1814 will be able to flush the buffer cache to disk, reboot the system
1815 immediately or dump some status information). This is accomplished
1816 by pressing various keys while holding SysRq (Alt+PrintScreen). It
1817 also works on a serial console (on PC hardware at least), if you
1818 send a BREAK and then within 5 seconds a command keypress. The
1819 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
1820 unless you really know what this hack does.
1823 bool "Debug memory allocations"
1824 depends on DEBUG_KERNEL
1826 config DEBUG_BUGVERBOSE
1827 bool "Verbose BUG() reporting"
1828 depends on DEBUG_KERNEL
1832 source "security/Kconfig"
1834 source "crypto/Kconfig"
1836 source "lib/Kconfig"
projects / linux-flexiantxendom0-3.2.10.git / blob