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