2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "uClinux/h8300 (w/o MMU) Kernel Configuration"
29 config RWSEM_GENERIC_SPINLOCK
33 config RWSEM_XCHGADD_ALGORITHM
37 config ARCH_HAS_ILOG2_U32
41 config ARCH_HAS_ILOG2_U64
45 config GENERIC_FIND_NEXT_BIT
49 config GENERIC_HWEIGHT
53 config GENERIC_HARDIRQS
57 config GENERIC_CALIBRATE_DELAY
69 config ARCH_SUPPORTS_AOUT
92 source "arch/h8300/Kconfig.cpu"
94 menu "Executable file formats"
96 source "fs/Kconfig.binfmt"
102 source "drivers/base/Kconfig"
104 source "drivers/mtd/Kconfig"
106 source "drivers/block/Kconfig"
108 source "drivers/ide/Kconfig"
110 source "arch/h8300/Kconfig.ide"
112 source "drivers/net/Kconfig"
115 # input - input/joystick depends on it. As does USB.
117 source "drivers/input/Kconfig"
119 menu "Character devices"
122 bool "Virtual terminal"
124 If you say Y here, you will get support for terminal devices with
125 display and keyboard devices. These are called "virtual" because you
126 can run several virtual terminals (also called virtual consoles) on
127 one physical terminal. This is rather useful, for example one
128 virtual terminal can collect system messages and warnings, another
129 one can be used for a text-mode user session, and a third could run
130 an X session, all in parallel. Switching between virtual terminals
131 is done with certain key combinations, usually Alt-<function key>.
133 The setterm command ("man setterm") can be used to change the
134 properties (such as colors or beeping) of a virtual terminal. The
135 man page console_codes(4) ("man console_codes") contains the special
136 character sequences that can be used to change those properties
137 directly. The fonts used on virtual terminals can be changed with
138 the setfont ("man setfont") command and the key bindings are defined
139 with the loadkeys ("man loadkeys") command.
141 You need at least one virtual terminal device in order to make use
142 of your keyboard and monitor. Therefore, only people configuring an
143 embedded system would want to say N here in order to save some
144 memory; the only way to log into such a system is then via a serial
145 or network connection.
147 If unsure, say Y, or else you won't be able to do much with your new
148 shiny Linux system :-)
151 bool "Support for console on virtual terminal"
154 The system console is the device which receives all kernel messages
155 and warnings and which allows logins in single user mode. If you
156 answer Y here, a virtual terminal (the device used to interact with
157 a physical terminal) can be used as system console. This is the most
158 common mode of operations, so you should say Y here unless you want
159 the kernel messages be output only to a serial port (in which case
160 you should say Y to "Console on serial port", below).
162 If you do say Y here, by default the currently visible virtual
163 terminal (/dev/tty0) will be used as system console. You can change
164 that with a kernel command line option such as "console=tty3" which
165 would use the third virtual terminal as system console. (Try "man
166 bootparam" or see the documentation of your boot loader (lilo or
167 loadlin) about how to pass options to the kernel at boot time.)
173 depends on VT && !S390 && !UM
176 comment "Unix98 PTY support"
179 bool "Unix98 PTY support"
181 A pseudo terminal (PTY) is a software device consisting of two
182 halves: a master and a slave. The slave device behaves identical to
183 a physical terminal; the master device is used by a process to
184 read data from and write data to the slave, thereby emulating a
185 terminal. Typical programs for the master side are telnet servers
188 Linux has traditionally used the BSD-like names /dev/ptyxx for
189 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
190 has a number of problems. The GNU C library glibc 2.1 and later,
191 however, supports the Unix98 naming standard: in order to acquire a
192 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
193 terminal is then made available to the process and the pseudo
194 terminal slave can be accessed as /dev/pts/<number>. What was
195 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
197 The entries in /dev/pts/ are created on the fly by a virtual
198 file system; therefore, if you say Y here you should say Y to
199 "/dev/pts file system for Unix98 PTYs" as well.
201 If you want to say Y here, you need to have the C library glibc 2.1
202 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
203 Read the instructions in <file:Documentation/Changes> pertaining to
204 pseudo terminals. It's safe to say N.
206 config UNIX98_PTY_COUNT
207 int "Maximum number of Unix98 PTYs in use (0-2048)"
208 depends on UNIX98_PTYS
211 The maximum number of Unix98 PTYs that can be used at any one time.
212 The default is 256, and should be enough for desktop systems. Server
213 machines which support incoming telnet/rlogin/ssh connections and/or
214 serve several X terminals may want to increase this: every incoming
215 connection and every xterm uses up one PTY.
217 When not in use, each additional set of 256 PTYs occupy
218 approximately 8 KB of kernel memory on 32-bit architectures.
220 source "drivers/char/pcmcia/Kconfig"
222 source "drivers/serial/Kconfig"
224 source "drivers/i2c/Kconfig"
226 source "drivers/hwmon/Kconfig"
228 source "drivers/usb/Kconfig"
234 source "arch/h8300/Kconfig.debug"
236 source "security/Kconfig"
238 source "crypto/Kconfig"