2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/config-language.txt.
6 mainmenu "uClinux/h8300 (w/o MMU) Kernel Configuration"
24 config RWSEM_GENERIC_SPINLOCK
28 config RWSEM_XCHGADD_ALGORITHM
32 config GENERIC_CALIBRATE_DELAY
46 source "arch/h8300/Kconfig.cpu"
48 menu "Executable file formats"
50 source "fs/Kconfig.binfmt"
56 source "drivers/base/Kconfig"
58 source "drivers/mtd/Kconfig"
60 source "drivers/block/Kconfig"
62 source "drivers/ide/Kconfig"
64 source "arch/h8300/Kconfig.ide"
66 source "drivers/net/Kconfig"
69 # input - input/joystick depends on it. As does USB.
71 source "drivers/input/Kconfig"
73 menu "Character devices"
76 bool "Virtual terminal"
78 If you say Y here, you will get support for terminal devices with
79 display and keyboard devices. These are called "virtual" because you
80 can run several virtual terminals (also called virtual consoles) on
81 one physical terminal. This is rather useful, for example one
82 virtual terminal can collect system messages and warnings, another
83 one can be used for a text-mode user session, and a third could run
84 an X session, all in parallel. Switching between virtual terminals
85 is done with certain key combinations, usually Alt-<function key>.
87 The setterm command ("man setterm") can be used to change the
88 properties (such as colors or beeping) of a virtual terminal. The
89 man page console_codes(4) ("man console_codes") contains the special
90 character sequences that can be used to change those properties
91 directly. The fonts used on virtual terminals can be changed with
92 the setfont ("man setfont") command and the key bindings are defined
93 with the loadkeys ("man loadkeys") command.
95 You need at least one virtual terminal device in order to make use
96 of your keyboard and monitor. Therefore, only people configuring an
97 embedded system would want to say N here in order to save some
98 memory; the only way to log into such a system is then via a serial
99 or network connection.
101 If unsure, say Y, or else you won't be able to do much with your new
102 shiny Linux system :-)
105 bool "Support for console on virtual terminal"
108 The system console is the device which receives all kernel messages
109 and warnings and which allows logins in single user mode. If you
110 answer Y here, a virtual terminal (the device used to interact with
111 a physical terminal) can be used as system console. This is the most
112 common mode of operations, so you should say Y here unless you want
113 the kernel messages be output only to a serial port (in which case
114 you should say Y to "Console on serial port", below).
116 If you do say Y here, by default the currently visible virtual
117 terminal (/dev/tty0) will be used as system console. You can change
118 that with a kernel command line option such as "console=tty3" which
119 would use the third virtual terminal as system console. (Try "man
120 bootparam" or see the documentation of your boot loader (lilo or
121 loadlin) about how to pass options to the kernel at boot time.)
127 depends on VT && !S390 && !UM
130 comment "Unix98 PTY support"
133 bool "Unix98 PTY support"
135 A pseudo terminal (PTY) is a software device consisting of two
136 halves: a master and a slave. The slave device behaves identical to
137 a physical terminal; the master device is used by a process to
138 read data from and write data to the slave, thereby emulating a
139 terminal. Typical programs for the master side are telnet servers
142 Linux has traditionally used the BSD-like names /dev/ptyxx for
143 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
144 has a number of problems. The GNU C library glibc 2.1 and later,
145 however, supports the Unix98 naming standard: in order to acquire a
146 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
147 terminal is then made available to the process and the pseudo
148 terminal slave can be accessed as /dev/pts/<number>. What was
149 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
151 The entries in /dev/pts/ are created on the fly by a virtual
152 file system; therefore, if you say Y here you should say Y to
153 "/dev/pts file system for Unix98 PTYs" as well.
155 If you want to say Y here, you need to have the C library glibc 2.1
156 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
157 Read the instructions in <file:Documentation/Changes> pertaining to
158 pseudo terminals. It's safe to say N.
160 config UNIX98_PTY_COUNT
161 int "Maximum number of Unix98 PTYs in use (0-2048)"
162 depends on UNIX98_PTYS
165 The maximum number of Unix98 PTYs that can be used at any one time.
166 The default is 256, and should be enough for desktop systems. Server
167 machines which support incoming telnet/rlogin/ssh connections and/or
168 serve several X terminals may want to increase this: every incoming
169 connection and every xterm uses up one PTY.
171 When not in use, each additional set of 256 PTYs occupy
172 approximately 8 KB of kernel memory on 32-bit architectures.
174 source "drivers/char/pcmcia/Kconfig"
176 source "drivers/serial/Kconfig"
178 source "drivers/i2c/Kconfig"
180 source "drivers/hwmon/Kconfig"
182 source "drivers/usb/Kconfig"
188 source "arch/h8300/Kconfig.debug"
190 source "security/Kconfig"
192 source "crypto/Kconfig"