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