Kconfig 5.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/config-language.txt.
  4. #
  5. mainmenu "uClinux/h8300 (w/o MMU) Kernel Configuration"
  6. config H8300
  7. bool
  8. default y
  9. config MMU
  10. bool
  11. default n
  12. config SWAP
  13. bool
  14. default n
  15. config FPU
  16. bool
  17. default n
  18. config UID16
  19. bool
  20. default y
  21. config RWSEM_GENERIC_SPINLOCK
  22. bool
  23. default y
  24. config RWSEM_XCHGADD_ALGORITHM
  25. bool
  26. default n
  27. config GENERIC_CALIBRATE_DELAY
  28. bool
  29. default y
  30. config ISA
  31. bool
  32. default y
  33. config PCI
  34. bool
  35. default n
  36. source "init/Kconfig"
  37. source "arch/h8300/Kconfig.cpu"
  38. menu "Executable file formats"
  39. source "fs/Kconfig.binfmt"
  40. endmenu
  41. source "drivers/base/Kconfig"
  42. source "drivers/mtd/Kconfig"
  43. source "drivers/block/Kconfig"
  44. source "drivers/ide/Kconfig"
  45. source "arch/h8300/Kconfig.ide"
  46. source "net/Kconfig"
  47. #
  48. # input - input/joystick depends on it. As does USB.
  49. #
  50. source "drivers/input/Kconfig"
  51. menu "Character devices"
  52. config VT
  53. bool "Virtual terminal"
  54. ---help---
  55. If you say Y here, you will get support for terminal devices with
  56. display and keyboard devices. These are called "virtual" because you
  57. can run several virtual terminals (also called virtual consoles) on
  58. one physical terminal. This is rather useful, for example one
  59. virtual terminal can collect system messages and warnings, another
  60. one can be used for a text-mode user session, and a third could run
  61. an X session, all in parallel. Switching between virtual terminals
  62. is done with certain key combinations, usually Alt-<function key>.
  63. The setterm command ("man setterm") can be used to change the
  64. properties (such as colors or beeping) of a virtual terminal. The
  65. man page console_codes(4) ("man console_codes") contains the special
  66. character sequences that can be used to change those properties
  67. directly. The fonts used on virtual terminals can be changed with
  68. the setfont ("man setfont") command and the key bindings are defined
  69. with the loadkeys ("man loadkeys") command.
  70. You need at least one virtual terminal device in order to make use
  71. of your keyboard and monitor. Therefore, only people configuring an
  72. embedded system would want to say N here in order to save some
  73. memory; the only way to log into such a system is then via a serial
  74. or network connection.
  75. If unsure, say Y, or else you won't be able to do much with your new
  76. shiny Linux system :-)
  77. config VT_CONSOLE
  78. bool "Support for console on virtual terminal"
  79. depends on VT
  80. ---help---
  81. The system console is the device which receives all kernel messages
  82. and warnings and which allows logins in single user mode. If you
  83. answer Y here, a virtual terminal (the device used to interact with
  84. a physical terminal) can be used as system console. This is the most
  85. common mode of operations, so you should say Y here unless you want
  86. the kernel messages be output only to a serial port (in which case
  87. you should say Y to "Console on serial port", below).
  88. If you do say Y here, by default the currently visible virtual
  89. terminal (/dev/tty0) will be used as system console. You can change
  90. that with a kernel command line option such as "console=tty3" which
  91. would use the third virtual terminal as system console. (Try "man
  92. bootparam" or see the documentation of your boot loader (lilo or
  93. loadlin) about how to pass options to the kernel at boot time.)
  94. If unsure, say Y.
  95. config HW_CONSOLE
  96. bool
  97. depends on VT && !S390 && !UM
  98. default y
  99. comment "Unix98 PTY support"
  100. config UNIX98_PTYS
  101. bool "Unix98 PTY support"
  102. ---help---
  103. A pseudo terminal (PTY) is a software device consisting of two
  104. halves: a master and a slave. The slave device behaves identical to
  105. a physical terminal; the master device is used by a process to
  106. read data from and write data to the slave, thereby emulating a
  107. terminal. Typical programs for the master side are telnet servers
  108. and xterms.
  109. Linux has traditionally used the BSD-like names /dev/ptyxx for
  110. masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
  111. has a number of problems. The GNU C library glibc 2.1 and later,
  112. however, supports the Unix98 naming standard: in order to acquire a
  113. pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
  114. terminal is then made available to the process and the pseudo
  115. terminal slave can be accessed as /dev/pts/<number>. What was
  116. traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
  117. The entries in /dev/pts/ are created on the fly by a virtual
  118. file system; therefore, if you say Y here you should say Y to
  119. "/dev/pts file system for Unix98 PTYs" as well.
  120. If you want to say Y here, you need to have the C library glibc 2.1
  121. or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
  122. Read the instructions in <file:Documentation/Changes> pertaining to
  123. pseudo terminals. It's safe to say N.
  124. config UNIX98_PTY_COUNT
  125. int "Maximum number of Unix98 PTYs in use (0-2048)"
  126. depends on UNIX98_PTYS
  127. default "256"
  128. help
  129. The maximum number of Unix98 PTYs that can be used at any one time.
  130. The default is 256, and should be enough for desktop systems. Server
  131. machines which support incoming telnet/rlogin/ssh connections and/or
  132. serve several X terminals may want to increase this: every incoming
  133. connection and every xterm uses up one PTY.
  134. When not in use, each additional set of 256 PTYs occupy
  135. approximately 8 KB of kernel memory on 32-bit architectures.
  136. source "drivers/char/pcmcia/Kconfig"
  137. source "drivers/serial/Kconfig"
  138. source "drivers/i2c/Kconfig"
  139. source "drivers/usb/Kconfig"
  140. endmenu
  141. source "fs/Kconfig"
  142. source "arch/h8300/Kconfig.debug"
  143. source "security/Kconfig"
  144. source "crypto/Kconfig"
  145. source "lib/Kconfig"