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